I've ran into similar issues before with cyanogenmod involving a "getprop" error but I am now receiving the error for any AOSP rom I attempt to install including AOKP and Hellybean. Samsung base roms are installing fine for some reason though. As far as Cyanogenmod is concerned I thought the issue may have been the kernel/ recovery... I have tried everything I know to do and to no avail. In past times I received this error installing CM so I used ODIN to return to stock but I would rather not have to do that if not neccesary. Thanks for reading.
Hammersuit said:
I've ran into similar issues before with cyanogenmod involving a "getprop" error but I am now receiving the error for any AOSP rom I attempt to install including AOKP and Hellybean. Samsung base roms are installing fine for some reason though. As far as Cyanogenmod is concerned I thought the issue may have been the kernel/ recovery... I have tried everything I know to do and to no avail. In past times I received this error installing CM so I used ODIN to return to stock but I would rather not have to do that if not neccesary. Thanks for reading.
Click to expand...
Click to collapse
Did you try flashing ktoonsez's siyah 4.3.3? That usually fixes the getprop error (otherwise known as status 7)
Sent from my Zanpakuto using Getsuga Tensho!
Nick281051 said:
Did you try flashing ktoonsez's siyah 4.3.3? That usually fixes the getprop error (otherwise known as status 7)
Sent from my Zanpakuto using Getsuga Tensho!
Click to expand...
Click to collapse
No, I haven't and I was unaware of that. Thank you though, I will try that now.
I am still receiving a status 7 error when I attempt to install CM10.1 (latest build) with Siyah kernel installed. Is there anything I am missing?
edit* Latest Task's AOKP successfully installed, however under no circumstances will CM10 install....
Hammersuit said:
I am still receiving a status 7 error when I attempt to install CM10.1 (latest build) with Siyah kernel installed. Is there anything I am missing?
edit* Latest Task's AOKP successfully installed, however under no circumstances will CM10 install....
Click to expand...
Click to collapse
necessary flash the stock after ODIN, then flash the kernel Siyah and not using flash Triangle avaey!-flash what you want!!!
good luck!
AlmasSD said:
necessary flash the stock after ODIN, then flash the kernel Siyah and not using flash Triangle avaey!-flash what you want!!!
good luck!
Click to expand...
Click to collapse
Unless you're going to give the right advice please don't give people advice.
Sent from my Zanpakuto using Getsuga Tensho!
Nick281051 said:
Unless you're going to give the right advice please don't give people advice.
Sent from my Zanpakuto using Getsuga Tensho!
Click to expand...
Click to collapse
This. Also maybe make it a little easier to understand haha.
I wish I had a little more input myself to describe what i've done but i'm a bit of a flashaholic and i've had so many roms I can't remember.... but I will say that once I reinstalled to AOKP I downloaded CWM-based recovery (most recent) from ROM manager (yes I know its garbage) because I thought that having that recovery would allow for the install, but to no avail. I currently have AOKP installed now (latest task release) but I really would prefer CM10...
Also, when I installed CWM-base recovery from rom manger I noticed that from my available recovery list it mentioned TWRP... is there any chance that TWRP remnants could remain from a previous rom install? (I full wipe every install)
Easiest is to just modify the buildprop and you wont have that issue of status 7
lilbigdude1 said:
Easiest is to just modify the buildprop and you wont have that issue of status 7
Click to expand...
Click to collapse
I've tried to do that and I could not save the changes... Can I do that using ES file explorer? or is there a better alternative?
Hammersuit said:
I've tried to do that and I could not save the changes... Can I do that using ES file explorer? or is there a better alternative?
Click to expand...
Click to collapse
You probably didn't enable the root option . Which you would need to make changes to the system.
Hammersuit said:
I've tried to do that and I could not save the changes... Can I do that using ES file explorer? or is there a better alternative?
Click to expand...
Click to collapse
I use root explorer
---------- Post added at 01:07 PM ---------- Previous post was at 01:05 PM ----------
Hammersuit said:
I've tried to do that and I could not save the changes... Can I do that using ES file explorer? or is there a better alternative?
Click to expand...
Click to collapse
Also make sure you use the editor and not the viewer
Ahh thank you all, I appreciate your replies, i'll try and edit the build.prop as mention .. I had completely forgotten about root helper!
I have attempted to rename the ro.product.device. and the ro.device.name (i believe they are called) to "SGH-i777" and simply "i777" but to avail... I still cannot get CM10.1 to install....
Hammersuit said:
I have attempted to rename the ro.product.device. and the ro.device.name (i believe they are called) to "SGH-i777" and simply "i777" but to avail... I still cannot get CM10.1 to install....
Click to expand...
Click to collapse
When I get this error, I just open the updater-script in the ROM zip and edit it. Delete the asserts for get.prop and you're good.
I777(S2)
Captivating M3
UCLE5
AJK 1.49
Shawn said:
When I get this error, I just open the updater-script in the ROM zip and edit it. Delete the asserts for get.prop and you're good.
I777(S2)
Captivating M3
UCLE5
AJK 1.49
Click to expand...
Click to collapse
Is the updater script you're referring to a different file aside from the build.prop? If so what is the file directory?
Hammersuit said:
Is the updater script you're referring to a different file aside from the build.prop? If so what is the file directory?
Click to expand...
Click to collapse
It's in META-INF\com\google\android. Then just open the updater-script file and delete the assert for get.prop lines and save.
Hammersuit said:
Is the updater script you're referring to a different file aside from the build.prop? If so what is the file directory?
Click to expand...
Click to collapse
Artm03 gave you the correct information you need!!!! I will add it it will be better if you have the zip file on your computer and edit it then move it to your phone. Just open the zip (don't extract it) edit the updater script as artm03 told you. Make sure you delete all 3 lines, so your first line will start with "mount"...... GL
snipe2nite said:
Artm03 gave you the correct information you need!!!! I will add it it will be better if you have the zip file on your computer and edit it then move it to your phone. Just open the zip (don't extract it) edit the updater script as artm03 told you. Make sure you delete all 3 lines, so your first line will start with "mount"...... GL
Click to expand...
Click to collapse
If a computer is not available, one could use the app "Total Commander" from the Play Store to edit and repack the updater script all on the phone.
Just navigate to the script inside the zip file, long press it, and select "unzip+edit". Open it up, and remove the assert lines as stated above. Hit save, then the back button and you'll be prompted to "repack" the changed file back into the zip file. It will take around half a minute to repack, then is ready for flashing.
BE CAREFUL to flash the correct zip for the i777, as the script assert that prevents this from happening is what this process removes.
Thank you all for your replies! I haven't been able to install yet because i've been very busy, I will be sure to confirm whether or not i've succeeded tonight though. Just out of curiosity, does anyone know why I would only have this issue installing Cyanogenmod? (I also could not install hellybean, but I know it is built from CM sources as well) I have had this problem many times before (bought this phone the day it came out) with Jellybean, Icecream Sandwich and even Gingerbread builds of CM, but as I stated earlier I was able to use ODIN to restore to stock, reinstall custom recovery, and install from there. This of course is a much longer and tedious process that includes the need for TriangleAway as well because your custom binary count increases...
Related
I'm using nightly 123. The program seems to work just like it's suppose to, no errors, but after I run the program I use Show me my IMEI and it still doesn't show that I have an IMEI no. I'm using ADB wireless to update the EMEI. The program runs and and reboots my nook afterwards.
I don't know what else to do, and i can't post in the developer's thread yet so I thought I'd ask here. Hope someone can tell me what I'm doing wrong. Thx
Well I still can't post in the right forum, does anyone have any ideas what I'm doing wrong? Thx
Sorry... didn't see this thread....
If you are using in-place... as it seem you are by the reboot... check to see if you have a /framework/framework.jar.bak present... you might also look at /rom and see if a file called imei is created there...
I'd say you have to have the framework.jar.bak file or you'd get the error that it had issues updating your device.
Since you are on CM7... go to phone app and dial *#06# and see what it tells you for IMEI.
Lastly... you can update the rom zip file... and flash the rom "-IMEI.zip" file.
Sorry... but this is the first report I've seen of it not working... and it may be the app you're using to show it... thus try the phone app thing.
Did not workforce me either. Using the dialer to check returns no number. I do have a framework.jar.Bak though. I'd really like this to work so that I could use the xda app with out it fcing. What file were u saying to flash DD? Thanks.
If you are using in-place... as it seem you are by the reboot... check to see if you have a /framework/framework.jar.bak present... you might also look at /rom and see if a file called imei is created there...
I'd say you have to have the framework.jar.bak file or you'd get the error that it had issues updating your device.
Since you are on CM7... go to phone app and dial *#06# and see what it tells you for IMEI.
Lastly... you can update the rom zip file... and flash the rom "-IMEI.zip" file.
Sorry... but this is the first report I've seen of it not working... and it may be the app you're using to show it... thus try the phone app thing.
__________________
Always remember...
1. I have the framework.jar.bak file
2. In the /Rom folder there isn't an imei file, but there is one in the /rom/devconf folder
3. When I dial the command in the phone app it comes back with a box that says imei then an OK button. There is no number if thats what you wanted to know.
4. I'm not exactly sure on the steps to update the rom zip file.
Thanks alot for answering my post.
OK... and I did mean the bak file should be in /rom/devconf... sorry bout that... was responding from work and in a hurry....
To update the rom... just tell it no to in place... and then yes to updating a ROM zip file...
After it finishes patching the zip file... flash the ROM "-IMEI.zip" and any OC kernel you're using.
I'll look into what's going on... it could be the newer rom update is missing symlinks and busybox is not working correctly... researching the cause.
DizzyDen said:
OK... and I did mean the bak file should be in /rom/devconf... sorry bout that... was responding from work and in a hurry....
To update the rom... just tell it no to in place... and then yes to updating a ROM zip file...
After it finishes patching the zip file... flash the ROM "-IMEI.zip" and any OC kernel you're using.
I'll look into what's going on... it could be the newer rom update is missing symlinks and busybox is not working correctly... researching the cause.
Click to expand...
Click to collapse
Will try it After work. I'm assuming it prompts u for the path to a zipped rom, and then creates one with imei added in the name. Then flash like n e other rom. Thanx.
Thx for the quick reply's. I updated the rom.zip file like you said. I think I'll wait to try it to see if you can figure out how to get the in-place update to work. I just updated the recent nightly and hate to start over again . If I have to I will though. Thx alot for your help.
newellj79 said:
Will try it After work. I'm assuming it prompts u for the path to a zipped rom, and then creates one with imei added in the name. Then flash like n e other rom. Thanx.
Click to expand...
Click to collapse
If it finds zip files in current directory... it will attempt to locate the newest (by filename) and prompts you if it is the correct one... if you click no... it opens a windows open dialog to browse to the zip file you want to update... the "-IEMI.zip will be placed in the same folder as the rom.zip.
lemdaddy said:
Thx for the quick reply's. I updated the rom.zip file like you said. I think I'll wait to try it to see if you can figure out how to get the in-place update to work. I just updated the recent nightly and hate to start over again . If I have to I will though. Thx alot for your help.
Click to expand...
Click to collapse
If you flash the update... you don't have to start over... it retains your data... just like any other update. You just have to make sure you install the OC kernel also... it is the same process as updating any nightly... the only difference is you run the IMEI generator on it prior to flashing it so you will have the patched framework.jar as soon as you flash it.
I just flashed the file your program created and I still have no imei no. when running the phone app or with the program Show me my Imie. I don't know if I'm doing something wrong or not, but everything seemed to work as it was suppose to except getting an Imei no. Thx.
lemdaddy said:
I just flashed the file your program created and I still have no imei no. when running the phone app or with the program Show me my Imie. I don't know if I'm doing something wrong or not, but everything seemed to work as it was suppose to except getting an Imei no. Thx.
Click to expand...
Click to collapse
hmmmm.... trying to see what the issue could be.... if you flashed the "-IEMI.zip" file the patched framework.jar file should be the one it installed... so it SHOULD work just fine.
Try running fix permissions and try in-place again... it could be that your permissions are preventing /system/framework/framework.jar being overwritten.
You can open the "-IMEI.zip" file in a zip file manager (winzip, 7zip, winrar) and see if the /system/framework/framework.jar file has a different date than the rest of the files.
In the rom zip file your program made the date of the framework jar was modified to today's date. I ran rom manager and fix permissions and rebooted then ran in place from your program. I still don't get a number with either phone or show me my emei. I also don't get any errors while running your program.
lemdaddy said:
In the rom zip file your program made the date of the framework jar was modified to today's date. I ran rom manager and fix permissions and rebooted then ran in place from your program, all appears to be good, no errors.
I still don't get a number with either phone or show me my emei.
Click to expand...
Click to collapse
This is just crazy... if the zip had the framework.jar file with today's date... it should be the one installed.. and it should have the imei in it...
Do me a favor... extract framework.jar from your zip file... email it to me at [email protected] so I can look into it and ensure the edit to the file went as planned.... or wait and I'll give the option to not delete the TelephonyManager.smali so you can look at the file and ensure the edit took place.
try this...
adb shell ls -l /system/framework
See what the date and time on that file is.
Ok i sent the framework.jar file, thx alot for your help.
lemdaddy said:
Ok i sent the framework.jar file, thx alot for your help.
Click to expand...
Click to collapse
NP... I got the file... for some reason the patch seems to not be in the file... this is the framework.jar file from the -IMEI.zip file... right?
When you run the program... does it give you a pop up with your S/N, MAC and IMEI ?
yes it is from the updated emei.zip rom file. Yes it does show the numbers when i run your program after it pulls the file from my nook
lemdaddy said:
yes it is from the updated emei.zip rom file. Yes it does show the numbers when i run your program after it pulls the file from my nook
Click to expand...
Click to collapse
OK... check your pm... also if you will adb pull /rom/imei and email that... I will create a framework.jar for you until I can track down what is going on.
Phone call would probably be easiest to track down the issue... Gave you number in pm... or you can pm me your's if you'd rather me make the call.
I got it working by using the flash method. I'm finally able to use tthe xda app!
Sent from my NookColor using XDA App
I wish mine would have. Dizzy is looking into why mine still won't work. I'm glad yours is working. I appreciate all your help Dizzy
Lemdaddy... if we get a chance to make contact tomorrow... sat... I want to try a couple of things so we figure out why the smali isn't working on your computer...
Sorry, I know that this is very basic question, but honestly, I tried searching but couldn't find how to do it!
Basicly, how do I install this battery mod, and how do I know which one to choose?
http://forum.xda-developers.com/showthread.php?t=1064037
I recently updated to 2.3.5 and CFRoot'ed my SGS2 yesterday. No other mods (yet)
Go to settings-> about phone and see what version you have (build number) - KE7/KF1/KF3 whatever.
Download the correct version for your build and copy it to your phone (looks like there are 2 files needed unless you have a bulid number that there is a 'flashable zip' for).
If you rooted using a CFroot kernel then you should have the CWM app installed. Go in there, select install APK and select the files you downloaded (probably need to do one then the other).
It should be as easy as that.
If you have the correct build for one of the 'flashable zips', download that and select 'flash update' in CWM instead.
Okay. That CWM thing helped a lot. There is not KI8 (which is my build version) on the list, is it okay to pick up version for other build?
Not sure if it will work with another build, but you can always try (do a backup from CWM first).
use the updated thread which has the apk for Ki8 for the mod. scroll down to the bottom f the first post to find it.
http://forum.xda-developers.com/showthread.php?t=1197150
I just tried this using CWM and the install doesn't work, so I guess you need to use ADB.
edit: tried using adb and it knackered my phone and sent it into a bootloop. Probably because I used the KI3 version on KI4. I guess that means you need the right one!
Cosmic Blue said:
use the updated thread which has the apk for Ki8 for the mod. scroll down to the bottom f the first post to find it.
http://forum.xda-developers.com/showthread.php?t=1197150
Click to expand...
Click to collapse
I downloaded the "XWKI8 framework-res.apk for circle battery mod and CRT effect (/system/framework/)". Tried apk-installing with CWM, but it says "Application not installed". Also tried moving the .apk-file to /system/framework/ (don't know if has any effect) but Root Explorer says that it is write-only directory. I am now again out of ideas, what next?
e: Okay, i found some tips on Google. (http://www.brighthub.com/mobile/google-android/articles/37151.aspx) See the "Using the Android SDK", is that correct way to go? I am not at home at the moment, but I will give it a shot later.
e2: Yay, got it working Had to click the "Mount R/W" click on the top on Root Explorer. I pasted the .apk-file on /system/framework/, and now it's working I think I now learnt how to use these files, thanks all!
Hello guys,
I saw a lot of users (also me xD) that frequently have build.prop error when flashing a custom rom from another custom rom.
Well, i created a simple flashable .zip that contains the original build.prop, needed by custom roms like cm.
How to use that:
1. Flash this fix BEFORE installing any custom roms.
2. After it installed, reboot recovery for applying changes.
3. Install your custom rom.
4. Enjoy it!
​
Hope it helps some users sorry for my bad English
Wouldn't the build.prop be erased when installing a custom ROM as the system partition is formatted?
If that's not the case I'll download and keep this safe in case I have the same problem in the future lol. Thanks.
Sent from my R800i using xda premium
you have to format system partition before flashing this fix or you'll lose build.prop, and you need to reflash them
installing custom rom doesn't make you lose build.prop
sorry for my poor English
Ah.. Makes much more sense then lol...
Although some ROMs do format the system partition before install, so I'm assuming those wont work..
Also - Your English is pretty decent compared to a lot of people!
I think it will work also with that kind of roms, because for fully applying changes you need to reboot recovery, that otherwise views build.prop also if in your /system directory it doesn't exist
Spizzy01 said:
Ah.. Makes much more sense then lol...
Although some ROMs do format the system partition before install, so I'm assuming those wont work..
Also - Your English is pretty decent compared to a lot of people!
Click to expand...
Click to collapse
I hope you're leaving the American and English out of this comparison.
Anyway, nice patch! I'll try this if I run into this error!
Selim873 said:
Anyway, nice patch! I'll try this if I run into this error!
Click to expand...
Click to collapse
Thanks man
Selim873 said:
I hope you're leaving the American and English out of this comparison.
Anyway, nice patch! I'll try this if I run into this error!
Click to expand...
Click to collapse
In some cases.. You'd be surprised... xD
I don't think you know what a status 7 error is. It has NOTHING to do with the build.prop. Status 7 refers to updater-script found in the META-INF file. Delete the get product info lines or something similar to that. This is actually a waste of time to make some zip when it's simpler to delete three lines. Build your "thanks meter'" some other way. Oh, and by the way, changing your build.prop to some random one can really screw your phone up.
Some ROMs do an assert check or something. Does this flash the build.prop for this phone to allow flashing to take place?
That's a very good idea if so. It could be avoided by the build.prop check, but this will do.
Sent from my R800i using xda app-developers app
agraceful said:
I don't think you know what a status 7 error is. It has NOTHING to do with the build.prop. Status 7 refers to updater-script found in the META-INF file. Delete the get product info lines or something similar to that. This is actually a waste of time to make some zip when it's simpler to delete three lines. Build your "thanks meter'" some other way. Oh, and by the way, changing your build.prop to some random one can really screw your phone up.
Click to expand...
Click to collapse
did you try to delete that lines from updater script in roms based on jelly bean?
try and tell me if it's simple
@MilkyJoePD yeah, it allows you to install roms that do an assert check. you still can remove the getprop lines from updater script (the 1st 4 lines), but on jb roms there are some files with the same names especially in /system/etc/terminfo, and that's compromises the good re-zip of your rom. that's what "agraceful" doesn't know, because he never tryed yet
again sorry for my English
I was just gonna make this little tutorial to take some work off of The actual Dev for the Project(Beastmode) thanks again for your work brother
In his newest alpha release of safe strap we're able to replace the stock rom slot with a 4.3 Touchwiz ROM, I have seen people report that they have flashed certain roms without having to do any modification, but this is a safety precaution.
First you will need your rom of choice, in this tutorial I'm using N3BULA.
Download the rom and extract the contents to a folder on your pc or phone, PC is much easier, but you can edit on your phone as well
The files you need to edit are under META-INF/COM/GOOGLE/ANDROID that's actually the only files
Im using his modified files from the dev thread for comparison.
First we'll open the Aroma-Config
http://forum.xda-developers.com/attachment.php?attachmentid=2650078&stc=1&d=1395786107
Pardon the crude screen shot method but this will show you the changes and where they are.
Modified is on the left and Stock that came with the rom is on the right. Make the Changes and save
Next is Updater-Script
Same crude method of screen shot
http://forum.xda-developers.com/attachment.php?attachmentid=2650086&stc=1&d=1395786357
you can see where the two differ, so just edit that out as well.
Left is modified, Right is stock
Save Changes
Edit 3/26 you can also delete boot.img in zip
Make sure these files are on external sd card as well as the rom, boot into recovery, always make a nandroid backup, wipe and flash.\
This is the first time I have made a tutorial, so if its rough around the edges please excuse my forum newbness
if I missed anything definitely feel free to add, and once again A HUGE THANK YOU BEASTMODE.
Hopefully in a few hours or days these edits wont be needed.
how do we go about putting them into the rom zip file?
You edit them in the rom zip file... extract the rom and it moves as a zip, my case was it downloaded to storage sdcard (internal). I extracted it to ext sdcard and then went in and edited it. It still remains a zip
Sent from my SCH-I605 using Tapatalk
Easy way is to use 7 zip. Extract the ROM and make the changes. Now right click on original ROM and select open archive. From there u can place the modded files. Now the ROM.zip is still flashable.
Sent from my LG-VS980 using xda app-developers app
of course as soon as i posted it, i figured it out, unfortunately i can't get alliance to work afterwards, it installs but doesn't boot
I'm using alliance atm on safestrap. Don't mod anything. Just choose the stock kernel when you get to that point in the installer.
So glad to see you post that.!!! Been talking to a guy about it for about 2 hrs about it now, I actually told him it should work as long as agni wasn't chosen, thanks for clarification
Sent from my SCH-I605 using Tapatalk
I tried and unedited version of alliance and it tripped Knox and I had to odin anyone got an edited version with out kernel that they know works
Sent from my SCH-I605 using Tapatalk
In my nebula zip I have a file on the root called boot.img should I delete this file as well?
Sent from my SCH-I605 using Tapatalk
It wouldn't hurt. The script edits disregard it but just to be safe you can
Sent from my SCH-I605 using Tapatalk
I don't get it I edited the zips and then when i try to flash in recovery it just says failed? it doesn't give me a specific reason. This is for n3bula rom. But i extracted using winrar, deleted boot.img, changed the aroma config and updated zip using wordpad, zipped the rom and it doesn't seem to work. is there something i'm doing wrong?
HerroMoto said:
I don't get it I edited the zips and then when i try to flash in recovery it just says failed? it doesn't give me a specific reason. This is for n3bula rom. But i extracted using winrar, deleted boot.img, changed the aroma config and updated zip using wordpad, zipped the rom and it doesn't seem to work. is there something i'm doing wrong?
Click to expand...
Click to collapse
After you deleted the boot.img there is no point in editing the rest. I used 7zip to unzip and rezip and have not had any problems yet. Winrar might be causing problems for all i know as i never use it. I'm not around my pc for the most part atm but i haven't had any problems flashing 4 or 5 roms with just deleting the boot.img.
roflcoptersoisoi said:
After you deleted the boot.img there is no point in editing the rest. I used 7zip to unzip and rezip and have not had any problems yet. Winrar might be causing problems for all i know as i never use it. I'm not around my pc for the most part atm but i haven't had any problems flashing 4 or 5 roms with just deleting the boot.img.
Click to expand...
Click to collapse
I ended up fixing it. I tried doing it through winrar and from root explorer on my phone. The way I got it to work was actually downloading the aroma-config file and uodater-script file from the development thread that beast mode provided and changed those. He happened to use nebula as well so everything is working great
Sent from my SCH-I605 using Tapatalk
Ive tried n3bula alliance and jediwiz(?) And all have worked out for me need some time to work SS!! Lol
Sent from my SCH-I605 using Tapatalk
So I have to delete stuff in the updater script and the boot.img correct? I opened the updater script in notepad and it looked nothing like that..
trying to install Jett rom and im not sure what will happen when I delete that kernel line..
already deleted boot.img
Just delete the boot.img nothing else
Sent from my SCH-I605 using Tapatalk
hggadm3 said:
Just delete the boot.img nothing else
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Excellent. Thank you!!!
Sorry for the dumb question but what do I do if the rom of choice isn't showing up on the root of my extSD?
EDIT:
Nevermind, to anyone who saw my last post(s), I'm an idiot .
Ran through Odin, re-rooted, re-installed Safestrap, now installing N3bula Rom.
Hope all goes well. And sorry for any inconvenience!
Hope my donation helped out some Beastmode!
i have made rom for my s duos using xda kitchenn but i get status 1 error when i flash the rom
i have searched a lot but i can't find satisfied answer
can any one help me solve this error?
i'm using this guide
http://forum.xda-developers.com/showthread.php?t=1801690
Vaibhav Chauhan said:
i have made rom for my s duos using xda kitchenn but i get status 1 error when i flash the rom
i have searched a lot but i can't find satisfied answer
can any one help me solve this error?
i'm using this guide
http://forum.xda-developers.com/showthread.php?t=1801690
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2230733
Status 1 Error:
"Well this is one of the most rarest error that a person can get...but with my experience I came to know that this occurs because you don't have correct permissions set. Use correct perms in updater-script and done "
Grab another rom that is the same base you are using and look at the META-INF/com/google/android folder which contains the updater script and binary to use as your reference points. Compare and contrast yours with that one.
es0tericcha0s said:
http://forum.xda-developers.com/showthread.php?t=2230733
Status 1 Error:
"Well this is one of the most rarest error that a person can get...but with my experience I came to know that this occurs because you don't have correct permissions set. Use correct perms in updater-script and done "
Grab another rom that is the same base you are using and look at the META-INF/com/google/android folder which contains the updater script and binary to use as your reference points. Compare and contrast yours with that one.
Click to expand...
Click to collapse
can i use another rom's updater script in my rom which has same base??
Should be able to. Wouldn't hurt to look at the differences though so then you can understand what things affect the install to help build knowledge.
es0tericcha0s said:
Should be able to. Wouldn't hurt to look at the differences though so then you can understand what things affect the install to help build knowledge.
Click to expand...
Click to collapse
i tried to replace updater script but not working
i also have tried to compare set perms but i am unable to find fault in it
@es0tericcha0s
please tell me what to do??
Sorry, that was my main idea. Are you getting the same error code? Did you unzip and re-zip the rom? If so, you should use an archive manager like 7zip to move the update script into the zip without needing to unzip the whole thing, otherwise you'll break the signature on the rom and have to re-sign it.
es0tericcha0s said:
Sorry, that was my main idea. Are you getting the same error code? Did you unzip and re-zip the rom? If so, you should use an archive manager like 7zip to move the update script into the zip without needing to unzip the whole thing, otherwise you'll break the signature on the rom and have to re-sign it.
Click to expand...
Click to collapse
actually i am using android kitchen to make the rom
and when i use the cosmic rom's updater script in it the status 1 error was solved
but it stuck on boot animation
@es0tericcha0s
my stuck on bootloops can you tell me how to logcat?
Vaibhav Chauhan said:
@es0tericcha0s
my stuck on bootloops can you tell me how to logcat?
Click to expand...
Click to collapse
Not all phones have adb access while in a bootloop. But to do so you would need adb set up on your computer, change directories to the adb folder (or if it's enabled globally, then where ever), and type:
adb logcat
You'll want to save it somewhere like:
http://pastebin.com/
and upload the link.
I am not skilled at reading logcats, so not sure if I can be of any more help after that.
If you don't have adb set up already, then just use this one: http://forum.xda-developers.com/showthread.php?t=2317790