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
Related
Someone who has done the whole DI01 update, please dump their system for me, or just the framework folder, apparently the one given to me had the stock android lockscreen patch applied to it lol.
Aside from that, the DI01 deodex works perfect, I opt_png'ed and zip_align'ed all the apk's, as well as the framework-res and twframework-res.
I will also need someone who knows how to sign updater-scripts to open the one attached, and just save it again properly and upload it for me. I am trying to get a flashable CW zip but the darn thing always gives me a status 6 error, which means the CW cannot read the updater script.
Sorry for the n00b question, but what benifit does deodexing provide? Also if there is another software update will I have to readd any .apk's to my /system folder?
Why not just flash your own system back to stock, then run the update, then dump /system? If you'd like an update script that doesn't update modem.bin, I already have one.
Assuming you're updating via CWM, why are you signing the zip? You don't need any signature, just zip the file up.
Is there anything involved in a dump besides just copying the files in /system?
namebrandon said:
Why not just flash your own system back to stock, then run the update, then dump /system? If you'd like an update script that doesn't update modem.bin, I already have one.
Assuming you're updating via CWM, why are you signing the zip? You don't need any signature, just zip the file up.
Click to expand...
Click to collapse
Because I am too lazy to go through all that.
I don't need it signed per say. More like opened, edited, and saved properly. It is said it is best to edit the update script in s Linux based environment which I don't have, but that notepad should suffice, yet when I save it with my notepad, I get the error of cw not being able to read it properly.
I have a fresh phone that just got the D101 update. Just need directions on what if anything is involved beyond just getting the /system directory via adb.
s44 said:
I have a fresh phone that just got the D101 update. Just need directions on what if anything is involved beyond just getting the /system directory via adb.
Click to expand...
Click to collapse
That is all I need. The only things I deodex are the contents of system/app and system/framework.
frostman89 said:
I don't need it signed per say. More like opened, edited, and saved properly. It is said it is best to edit the update script in s Linux based environment which I don't have, but that notepad should suffice, yet when I save it with my notepad, I get the error of cw not being able to read it properly.
Click to expand...
Click to collapse
Try a real editor, like bluefish or something.. Those scripts look like sh#! in notepad.
If no one has done it by tonight, just grab me on IRC and I'll do it under Linux for you.
Make sure you've got the file/directory structure right too.. You can't just throw a script in a zip file, but I'm sure you knew that. Myself and and a few others had the wrong directory structure at first, don't remember what error number that gave us though.. I think it just froze.
OK, how can I get it to you? I can't post links or (I think) files yet.
s44 said:
OK, how can I get it to you? I can't post links or (I think) files yet.
Click to expand...
Click to collapse
You can just zip it up and upload it to mediafire.com
Just splice up the link like WWW. Website. Com and I will just delete the spaces.
Mediafire upload just not working for some reason. Hm.
s44 said:
Mediafire upload just not working for some reason. Hm.
Click to expand...
Click to collapse
http://multiupload.com/
J1HDKEGYAR at multiupload
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...
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
So I was trying to package a rom and let the kitchen create the meta-inf folder along with the updater-script but the problem is that it's not using the specified mount points.
My phone isn't supported in the kitchen so I had to make a file in the edify_defs folder for my phone. I did all the right steps, I renamed the file to that of the ro.produc.device, used the template and made the necessary edits using notepad ++, and checked the file for any incorrect syntax yet after all that, the kitchen isn't using the mount points I put but instead uses the default value "mount("MTD", "system", "/system")".
Any help?
bump
Don't rely on kitchen's mount. Instead, use the update binary of a working zip for your device and edit the updater-script manually to make it work.
iZLeeP said:
Don't rely on kitchen's mount. Instead, use the update binary of a working zip for your device and edit the updater-script manually to make it work.
Click to expand...
Click to collapse
Yah, the thing is there are no roms for my device not even a stock rom. This is the reason why I'm trying to learn how to build a rom.
Anyways, I got the kitchen to detect the mount points. Turns out i had put the kitchen in the wrong directory. Made the zip flash correctly but now i encountered a new problem. After flashing the zip, the interface on my phone becomes really small. It's like my display went into tablet mode. Any idea on this?
black_fire21 said:
Yah, the thing is there are no roms for my device not even a stock rom. This is the reason why I'm trying to learn how to build a rom.
Anyways, I got the kitchen to detect the mount points. Turns out i had put the kitchen in the wrong directory. Made the zip flash correctly but now i encountered a new problem. After flashing the zip, the interface on my phone becomes really small. It's like my display went into tablet mode. Any idea on this?
Click to expand...
Click to collapse
What's your device and android version? Much better if you could post on your device's specific thread.
It's a local phone called starmobile quest, running jellybean. Sadly, there is absolutely no support for the device not even from the manufacturers. There are no developers either. The only thing we have is root and cwm.
@superr
I'm having some trouble with ROM builds for the pixel XL. I made a bone stock ROM. It boots but has Bluetooth share force close. I think it's due to not being able to use sparse for perms. Currently trying with may build. I'm on Linux mint 18.1
toknitup420 said:
@superr
I'm having some trouble with ROM builds for the pixel XL. I made a bone stock ROM. It boots but has Bluetooth share force close. I think it's due to not being able to use sparse for perms. Currently trying with may build. I'm on Linux mint 18.1
Click to expand...
Click to collapse
It could be missing metadata. Are you starting with this fimware? I can unpack it and locate the files with unique permissions. It may help figure out what is missing. Not using sparse dat is not your issue. set_metadata will work once we track down the problem.
SuperR. said:
It could be missing metadata. Which firmware are you starting with? I can unpack it and locate the files with unique permissions. It may help figure out what is missing. Not using sparse dat is not your issue. set_metadata will work once we track down the problem.
Click to expand...
Click to collapse
Do you want a copy of the current project I have in kitchen. I can upload it to my drive. I just used the zip from the may factory image.
Edit
Wow I just realized that was a link lol. I totally misread lol. Yes I'm using that firmware.
toknitup420 said:
Do you want a copy of the current project I have in kitchen. I can upload it to my drive. I just used the zip from the may factory image.
Edit
Wow I just realized that was a link lol. I totally misread lol. Yes I'm using that firmware.
Click to expand...
Click to collapse
You did not misread, i changed it I will check it out when I get a chance. No need to upload your project.
toknitup420 said:
@superr
I'm having some trouble with ROM builds for the pixel XL. I made a bone stock ROM. It boots but has Bluetooth share force close. I think it's due to not being able to use sparse for perms. Currently trying with may build. I'm on Linux mint 18.1
Click to expand...
Click to collapse
Can you try this updater-script to see if it fixes the issue? There are actually 2 attached, with_vendor and no_vendor in case you extracted vendor too. If you replace it in the kitchen, make sure you zip the ROM manually because the kitchen will change it before zipping based on the files you have.
SuperR. said:
Can you try this updater-script to see if it fixes the issue? There are actually 2 attached, with_vendor and no_vendor in case you extracted vendor too. If you replace it in the kitchen, make sure you zip the ROM manually because the kitchen will change it before zipping based on the files you have.
Click to expand...
Click to collapse
so i cant zip manually because i dont have perms for one file in system. heres a pic. ill just add the script into an existing zip i built from kitchen.was
update
so i was able to move the script into the correct location and zip up the file. however when it flashes the updater script is somehow becoming merged with the original instead of just the new script. it still shows the original script text when flashing.
toknitup420 said:
so i cant zip manually because i dont have perms for one file in system. heres a pic. ill just add the script into an existing zip i built from kitchen.was
update
so i was able to move the script into the correct location and zip up the file. however when it flashes the updater script is somehow becoming merged with the original instead of just the new script. it still shows the original script text when flashing.
Click to expand...
Click to collapse
I will build a rom and upload for you to try. Are you building with vendor included or without?
SuperR. said:
I will build a rom and upload for you to try. Are you building with vendor included or without?
Click to expand...
Click to collapse
I built it without. Do you recommend to build it with vendor. Should that file be root like that. The one that's in that pic I sent.
toknitup420 said:
I built it without. Do you recommend to build it with vendor. Should that file be root like that. The one that's in that pic I sent.
Click to expand...
Click to collapse
Here is the marlin n2g47o test rom:
https://www.androidfilehost.com/?fid=817550096634774971
It is up to you about vendor. You must have matching vendor and system or the rom will not boot. If you inform users they must flash the corresponding vendor.img along with the rom you don't need to include it. The test rom does not include vendor so make sure you have the correct vendor flashed.
The root file you refer to is actually a directory symlink and should not be there at all. I have fixed this behavior locally and in this test rom. If all works, I will push the update.
SuperR. said:
Here is the marlin n2g47o test rom:
https://www.androidfilehost.com/?fid=817550096634774971
It is up to you about vendor. You must have matching vendor and system or the rom will not boot. If you inform users they must flash the corresponding vendor.img along with the rom you don't need to include it. The test rom does not include vendor so make sure you have the correct vendor flashed.
The root file you refer to is actually a directory symlink and should not be there at all. I have fixed this behavior locally and in this test rom. If all works, I will push the update.
Click to expand...
Click to collapse
OK I'll try it now. Good looks.
SuperR. said:
Here is the marlin n2g47o test rom:
https://www.androidfilehost.com/?fid=817550096634774971
It is up to you about vendor. You must have matching vendor and system or the rom will not boot. If you inform users they must flash the corresponding vendor.img along with the rom you don't need to include it. The test rom does not include vendor so make sure you have the correct vendor flashed.
The root file you refer to is actually a directory symlink and should not be there at all. I have fixed this behavior locally and in this test rom. If all works, I will push the update.
Click to expand...
Click to collapse
it flashes with no errors but it wont boot past splash screen.
toknitup420 said:
it flashes with no errors but it wont boot past splash screen.
Click to expand...
Click to collapse
Please try marlin n2g47o test rom 2:
https://www.androidfilehost.com/?fid=745425885120737663
SuperR. said:
Please try marlin n2g47o test rom 2:
https://www.androidfilehost.com/?fid=745425885120737663
Click to expand...
Click to collapse
flash went through without error but still boot looping at splash screen.
toknitup420 said:
flash went through without error but still boot looping at splash screen.
Click to expand...
Click to collapse
Moved to a dedicated thread as this issue is only about Pixel.
I will do more thinking on what could be causing it. I was pretty sure the last rom would fix it but clearly I was wrong lol
SuperR. said:
Moved to a dedicated thread as this issue is only about Pixel.
I will do more thinking on what could be causing it. I was pretty sure the last rom would fix it but clearly I was wrong lol
Click to expand...
Click to collapse
Lol good stuff. Keep me posted. I'll test whatever you throw at me.
toknitup420 said:
Lol good stuff. Keep me posted. I'll test whatever you throw at me.
Click to expand...
Click to collapse
Here is a new approach so I don't have to keep uploading full roms. Use the kitchen to extract the last rom I sent into a new project. In your file manager, navigate to your project directory and delete the 00_project_files directory. Extract the attached file into your project directory. Build rom with kitchen. Test rom.
Next time, you won't need to extract the rom zip again, just replace the 00_project_files directory.
edit: forgot to mention, after replacing the 00_project_files directory with the one in the zip, change perm types to something else, then back to set_metadata. Then build your rom
SuperR. said:
Here is a new approach so I don't have to keep uploading full roms. Use the kitchen to extract the last rom I sent into a new project. In your file manager, navigate to your project directory and delete the 00_project_files directory. Extract the attached file into your project directory. Build rom with kitchen. Test rom.
Next time, you won't need to extract the rom zip again, just replace the 00_project_files directory.
edit: forgot to mention, after replacing the 00_project_files directory with the one in the zip, change perm types to something else, then back to set_metadata. Then build your rom
Click to expand...
Click to collapse
flashing seemed to hang at setting perms. but it eventually went through. still looping at splash screen though.
toknitup420 said:
flashing seemed to hang at setting perms. but it eventually went through. still looping at splash screen though.
Click to expand...
Click to collapse
Can you send the original updater script that booted but did not have bluetooth?
SuperR. said:
Can you send the original updater script that booted but did not have bluetooth?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B4VEhClrJEWpNnJNVUJTRFV4ODQ/view?usp=sharing
https://drive.google.com/file/d/0B4VEhClrJEWpTmlYWC1CQ0s3LVE/view?usp=sharing
thats the binary and the script. i converted script to binary when i was building rom. this rom boots and runs ok other than bluetooth. its not completely stock though. i have my modded framework settings and system ui apks in there. but they are all signed so i dont think they would mess with anything.
toknitup420 said:
https://drive.google.com/file/d/0B4VEhClrJEWpNnJNVUJTRFV4ODQ/view?usp=sharing
https://drive.google.com/file/d/0B4VEhClrJEWpTmlYWC1CQ0s3LVE/view?usp=sharing
thats the binary and the script. i converted script to binary when i was building rom. this rom boots and runs ok other than bluetooth. its not completely stock though. i have my modded framework settings and system ui apks in there. but they are all signed so i dont think they would mess with anything.
Click to expand...
Click to collapse
Did you convert the new one you just tried after swapping 00_project_files to update-binary? If not, try it please. If so, try without please