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
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...
Could someone please post a step by step on how to properly install the speedy Gonzales script for us less savvy people. Thanks in advance.
You have to be rooted with tenfars recovery and the init hack: http://forum.xda-developers.com/showthread.php?t=1223771
Download the .zip file that says flashable in the title, it located at the bottom of first post. Move it to sd card. This one: http://forum.xda-developers.com/attachment.php?attachmentid=704624&d=1314689490
Open the System Recovery app and select Recovery Mode (unsure plugged in).
Select choose zip from sd card. Navigate to the file and flash it.
What part is the issue, let me know where you have questions.
Ok I am rooted and have tenfars recovery. Do I still need the init hack installed or just go ahead and install new script through system recovery. Confused on first part.
Yes you need the init hack. Its the first link I posted. Its same thing. Download zip. Move to sd. Boot into recovery, flash. May be able to flash the speedy hack right after, but id reboot first just to make sure.
You need to go back into the /etc/init.d folder and delete the kickasskernel and S00tweaks once everything is successfully flashed.
One last question. I notice that there are 3 init.d hacks do you use all 3 or just one. That's the only think im not sure of.
Which ever one you want, but only one. Each is different and the description should describe that difference. I am on the first one. Battery saver or what ever its called.
So after I install the script using the flashable zip am I supposed to have the "zipalign-dataapp.log." in my /data file? Or is that only if you do it manually?
dust. said:
So after I install the script using the flashable zip am I supposed to have the "zipalign-dataapp.log." in my /data file? Or is that only if you do it manually?
Click to expand...
Click to collapse
That's what the instructions say in the original post for speedy.
You know what sucks is that the guy who made this got bashed so much he pulled the script and closed the thread...
This is supposed to be a community you ask and answer questions it gets to the point were people are afraid to ask anything without searching for 3-5 days for something i don't understand why people on these types of forums bash each others work so much its ridiculous...that sucks i feel really bad for the OP of this script he was just trying something and he got the crap kicked out of him....venting
im not gettintg the zipalign logfile he mentioned. hmmm
nitwit said:
im not gettintg the zipalign logfile he mentioned. hmmm
Click to expand...
Click to collapse
I didnt at first either, but I didnt follow directions proper and do the init.d thing first. after I did that I had the zip log thingy in /data
nitwit said:
im not gettintg the zipalign logfile he mentioned. hmmm
Click to expand...
Click to collapse
Same here.
Sandso9 said:
Same here.
Click to expand...
Click to collapse
Yeah you're not the first person to have this problem, it's because Naven's init hack uses the busybox applet run-parts which doesn't exist in all busybox releases. You definitely should have a zipalign log in /data.
I'll probably get flamed again for posting, but the following link is init-rehack, I created it for myself (original work by naven who discovered the hack!) when the initial hack from naven wasn't working.
http://www.sendspace.com/file/9g6ngz
Edit: Updated with new link.
Flash it in recovery and let me know if that works and you see the zipalign logs.
0vermind said:
Yeah you're not the first person to have this problem, it's because Naven's init hack uses the busybox applet run-parts which doesn't exist in all busybox releases. You definitely should have a zipalign log in /data.
I'll probably get flamed again for posting, but the following link is init-rehack, I created it for myself (original work by naven who discovered the hack!) when the initial hack from naven wasn't working.
http://www.sendspace.com/file/jmvpyf
Flash it in recovery and let me know if that works and you see the zipalign logs.
Click to expand...
Click to collapse
flash it over yours then? or before ?
Sandso9 said:
flash it over yours then?
Click to expand...
Click to collapse
Yeah. Let me know if it works or if it doesn't.
0vermind said:
Yeah. Let me know if it works or if it doesn't.
Click to expand...
Click to collapse
flashed this over yours and still no zip align log file in /data
Sandso9 said:
flashed this over yours and still no zip align log file in /data
Click to expand...
Click to collapse
Sorry, wrong link.
Blah blah blah blah, edit edit edit edit
http://www.sendspace.com/file/9g6ngz
Edit: Updated with new link.
Flashed the latest file and still no zipalign log in /data.
zetsumeikuro said:
Flashed the latest file and still no zipalign log in /data.
Click to expand...
Click to collapse
Lol same here
Sent from my OG Droid
Hi, I want to create my own custom rom, I've finish them, but I've a problem.
I don't know how to pack all the files in a flashable zip, I've make a zip with 7-zip but when I try to install it, recovery say "Installation Aborted".
Someone can explain to me how to create the zip? I've an good experience on android but I haven't already create a flashable zip...
Thanks!
Would not have a clue my friend but by reading the following threads your best bet is to go to the following links
http://forum.xda-developers.com/showthread.php?t=1227549
http://forum.xda-developers.com/showthread.php?t=1133846
Have a look at those links and those are the best options you have to create your own rom. Enjoy
It is possible to make a simple tutorial for me, I'm french and that's too hard to understand for me. I just need to pack in a zip file flashable. Thanks you .
Wouldn't there need to be a script to tell CW what to do with the files in the package/how to install them, etc ?
I wouldn't have a clue how to do this BTW, I'm just thinking logically around what I know about the way CW works so far as installing roms/kernels goes.
MistahBungle said:
Wouldn't there need to be a script to tell CW what to do with the files in the package/how to install them, etc ?
I wouldn't have a clue how to do this BTW, I'm just thinking logically around what I know about the way CW works so far as installing roms/kernels goes.
Click to expand...
Click to collapse
Thanks, but we can't pack a rom with cwm if that's what you want to say.
sangosnip69 said:
Thanks, but we can't pack a rom with cwm if that's what you want to say.
Click to expand...
Click to collapse
still check those links i gave you above. there must be a solution or guide to tell you how to pack a rom once you are finished putting everything together.my guess is that you do need an updater script and updater binary script something like that..check on those two links and have a look..or zip the rom using powerarchiver if you are on windows
just head over to http://perka.zapto.org and look for a empty system cwm.
Now you just have to make folders in this zip and add your files. example you want framework-res.apk and systemui.apk flashed.
So open the cwm zip and add a folders called app and a folder called framework.
The zip will be/system and so with the folders it creates /system/framework/framework-res.apk and system/app/SystemUI.apk.
You can just take the signatures from the zip and add them in your future zips or just keep copying this one.
The update script shows the screens on install so change text in there and it will show on install.
Or there is a guide to Edify Scripting here: http://forum.xda-developers.com/showthread.php?t=1265120
In case you want to do the actually OTA with your phone, and got some errors (dead android), you might want to check:
+ if you are using "CWM Recovery" (then uninstall it as in http://forum.xda-developers.com/showthread.php?t=2095825)
+ if you are using "Remove QSlide Apps from NotificationBar" (http://forum.xda-developers.com/showthread.php?t=2194423)
But don't use the QSlide revert file from above thread, it doesn't restore the exact matched file for OTA to work with (you can try if you want). To save you some trouble, I have attach the original files (LGSystemUI.apk and its odex). Unzip and overwrite them in the folder /system/app (use ES Explorer to remount /system RW first).
+ still not found the problem, check the few last lines of this file: /system/cache/recovery/last_log
It should say which file mismatches the checksum, and in the case of mine, it is LGSystemUI.apk, which I cannot find anything related searching google. And that's why I make the thread so people can search google and found it here.
chicguy said:
In case you want to do the actually OTA with your phone, and got some errors (dead android), you might want to check:
+ if you are using "CWM Recovery" (then uninstall it as in http://forum.xda-developers.com/showthread.php?t=2095825)
+ if you are using "Remove QSlide Apps from NotificationBar" (http://forum.xda-developers.com/showthread.php?t=2194423)
But don't use the QSlide revert file from above thread, it doesn't restore the exact matched file for OTA to work with (you can try if you want). To save you some trouble, I have attach the original files (LGSystemUI.apk and its odex). Unzip and overwrite them in the folder /system/app (use ES Explorer to remount /system RW first).
+ still not found the problem, check the few last lines of this file: /system/cache/recovery/last_log
It should say which file mismatches the checksum, and in the case of mine, it is LGSystemUI.apk, which I cannot find anything related searching google. And that's why I make the thread so people can search google and found it here.
Click to expand...
Click to collapse
Removed CWM and still get dead android red triangle icon.
My log also shows LGSYSTEMUI.APK ERROR
eSZee said:
Removed CWM and still get dead android red triangle icon.
My log also shows LGSYSTEMUI.APK ERROR
Click to expand...
Click to collapse
If you are rooted then all you need to do is find a nandroid backup of previous jb and flash it. Then you use the trick to force the OTA. If you are not rooted then the only thing I can say is download the kdz, flash it, and wait for the OTA.
there are a few things that manipulate the system: link2sd, overclocking, busybox, custom recovery. . .My thing was the busybox. I totally forgot that I downloaded it and my update didn't work at first. Good Luck
eSZee said:
Removed CWM and still get dead android red triangle icon.
My log also shows LGSYSTEMUI.APK ERROR
Click to expand...
Click to collapse
Go go page 9 of the forum link below. There is a Dropbox link of a factory rooted version of V20f for the 769 US version to flash if you have access to CWM on your phone.
http://forum.xda-developers.com/showthread.php?t=2359044
Sent from my LG-P769 using Tapatalk 2
TheCoutures said:
Go go page 9 of the forum link below. There is a Dropbox link of a factory rooted version of V20f for the 769 US version to flash if you have access to CWM on your phone.
http://forum.xda-developers.com/showthread.php?t=2359044
Sent from my LG-P769 using Tapatalk 2
Click to expand...
Click to collapse
Downloaded several times to make sure it wasn't a bad download. Went to apply zip, as soon as I pressed YES, INSTALL ABORTED.
I have no mods or edited system files or anything like that. All I ever did was CWM and root. Had qslide removed but reverted.
Make sure MD5 sum is correct. The other stuff doesn't matter. You are flashing a full backup not an OTA which requires all stock apps.
Sent from my LG-P769(20F) using the xda-developers app. If I helped you please hit the thanks button.
eSZee said:
Downloaded several times to make sure it wasn't a bad download. Went to apply zip, as soon as I pressed YES, INSTALL ABORTED.
I have no mods or edited system files or anything like that. All I ever did was CWM and root. Had qslide removed but reverted.
Click to expand...
Click to collapse
Wait you tried to install it as a zip
You are supposed to extract it and put the nandroid in the CWM backup directory.
sent from my locked rooted P769 v20D
I'm on YouTube (BioDesigner48)
I'm having the same issue, I do not have CWM or QSlide Remove installed, I've uninstalled all Root related apps and still encountering the same issue....
eSZee said:
Downloaded several times to make sure it wasn't a bad download. Went to apply zip, as soon as I pressed YES, INSTALL ABORTED.
I have no mods or edited system files or anything like that. All I ever did was CWM and root. Had qslide removed but reverted.
Click to expand...
Click to collapse
In my OP, I said "don't use the QSlide revert file from above thread, it doesn't restore the exact matched file for OTA to work with".
In case you still have trouble with the OTA, try to follow what I wrote: "To save you some trouble, I have attach the original files (LGSystemUI.apk and its odex). Unzip and overwrite them in the folder /system/app (use ES Explorer to remount /system RW first)."
Hope that helps!
For other people with problems, I suggest to use the Recovery Flashable Zip mentioned in one of the reply.
Or, if you are as paranoid as I am (who knows what people might put in those zip file ) (and somewhat technically knowledgeable), "check the few last lines of this file: /system/cache/recovery/last_log" to see what file got error, and try to get the original file from 20D (which should have the matched SHA1 checksum) and replace them.
chicguy said:
In my OP, I said "don't use the QSlide revert file from above thread, it doesn't restore the exact matched file for OTA to work with".
In case you still have trouble with the OTA, try to follow what I wrote: "To save you some trouble, I have attach the original files (LGSystemUI.apk and its odex). Unzip and overwrite them in the folder /system/app (use ES Explorer to remount /system RW first)."
Hope that helps!
For other people with problems, I suggest to use the Recovery Flashable Zip mentioned in one of the reply.
Or, if you are as paranoid as I am (who knows what people might put in those zip file ) (and somewhat technically knowledgeable), "check the few last lines of this file: /system/cache/recovery/last_log" to see what file got error, and try to get the original file from 20D (which should have the matched SHA1 checksum) and replace them.
Click to expand...
Click to collapse
Get the full P769BKv20f kdz file download here. Please be advised that this is just stock and if you flash this ROM then you WILL LOSE ROOT! But you can download and create a bin file to do the Lelus root method.
@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