From Sammobile new 4.4.2 P5210XXUBNH1
Luxor said:
From Sammobile new 4.4.2 P5210XXUBNH1
Click to expand...
Click to collapse
http://samsung-updates.com/device/
there is the download link i am downloading it right now.
will it work on my dutch tab 3 10.1?
damian312 said:
http://samsung-updates.com/device
there is the download link i am downloading it right now.
will it work on my dutch tab 3 10.1?
Click to expand...
Click to collapse
downloading now too, please report!
Downloading.
nowo said:
downloading now too, please report!
Click to expand...
Click to collapse
I am a little afraid to test it.
Do i have to flash through odin?
hey,
if you guys are hesitant, i'll test it. give me a couple of hours to get it and do the usual
@Restl3ss - dude OP look !
m
moonbutt74 said:
hey,
if you guys are hesitant, i'll test it. give me a couple of hours to get it and do the usual
@Restl3ss - dude OP look !
m
Click to expand...
Click to collapse
You are the man.
i wait for it
dead link bud!
RoninTPD said:
dead link bud!
Click to expand...
Click to collapse
http://samsung-updates.com/device/
not that hard to fix it:good:
Installing. can't wait to pull it apart.
CAG-man said:
Installing. can't wait to pull it apart.
Click to expand...
Click to collapse
cag,
when you are go can you pull the /system/vendor directory and post it?
also /system/bin/toolbox ?
my download just started , i can't wait !!
m
M,
I will do so.
Holy crap, finally!
damian312 said:
http://samsung-updates.com/device/
not that hard to fix it:good:
Click to expand...
Click to collapse
thanks!!:good:
CAG-man said:
Installing. can't wait to pull it apart.
Click to expand...
Click to collapse
Does it work?
The firmware works, but two things are proving to be very difficult.
one is extracting system.img, i dont know what's different, but the method i used for the 4.2 firmwares just crashes now.
two, and this is a big one
rooting it..
working on it
edit: super SU 1.9.4 zip from chainfire worked. No other method works though, the superuser apk will install but the binary doesn't stick
edit 2: successfully extracted the system image
notes
hey,
if the update with the t211 was any indication, be sure to only write boot.img and system.img
i am making a flashable zip and will post after i get it right and debloated and get the script correct.
realistically, sometime tomorrow, will update.
@Restl3ss okay so iam laughing at myself right now becuase i can not get the damned thing to write. i don't use windows
so no odin. i have tried dd writing the images but on boot i hang at logo and with no adb i can't get a visual on the problem.
i have a .zip put together to do the same and get the same. i have another zip set up ota style but can't script worth a damn.
can you whip up a script and post it?
an interesting note- in /sbin is a binary file named partlink. thoughts?
Restl3ss
@Restl3ss
okay so this is the joke
i am too poor to upload a large file to devhost. :laugh:
solution - i going to upload the otapackge for the firmware WITHOUT the system folder.
the package has the modified to unsecure boot.img and the updater script which just happens to be the
same one i am using for cm11 :laugh: :victory:
these are the instructions for converting, mounting and pulling the system image into an cwm flashable zip
to convert and mount sparse .img in terminal
simg2img system.img system.img.ext4
mount -o loop system.img.ext4 /a/directory
then nav to that directory in file browser, copy the contents of /system and insert in to package.
there is also a second step to correct issues with symlinks in vendor. drop that package into ota second
sorry for the inconvenience. it's in your folder with the patches.
but hey, i'm poor.
m
i'm running it right now and it seems very kitkatty
If i flash 4.4 can i still flash back to 4.2.2?
moonbutt74 said:
@Restl3ss
okay so this is the joke
i am too poor to upload a large file to devhost. :laugh:
solution - i going to upload the otapackge for the firmware WITHOUT the system folder.
the package has the modified to unsecure boot.img and the updater script which just happens to be the
same one i am using for cm11 :laugh: :victory:
these are the instructions for converting, mounting and pulling the system image into an cwm flashable zip
to convert and mount sparse .img in terminal
simg2img system.img system.img.ext4
mount -o loop system.img.ext4 /a/directory
then nav to that directory in file browser, copy the contents of /system and insert in to package.
there is also a second step to correct issues with symlinks in vendor. drop that package into ota second
sorry for the inconvenience. it's in your folder with the patches.
but hey, i'm poor.
m
i'm running it right now and it seems very kitkatty
Click to expand...
Click to collapse
got it system folder is properly extracted and what not, trying to deodex. About 10 apks are failing on every deodex attempt, can't figure out why. Gonna upload a 100% stock to xda anyway, deodexed + rooted will just have to come a bit later.
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
Hi XDA,
I'm using dsixda's Kitchen, trying to edit a stock rom (LFB-i9300).
I got everything extracted, but I had to remove the .md5 extension of the stock rom and I had to rename system.img to factoryfs.img, else Kitchen wouldn't recognize the rom. I think something went wrong in this process of getting the rom recognized. I loaded the rom and I chose to add in root, busybox and I de-odexed the files (I chose Api level 14, this is the right one for 4.0.4, right?).
Then I build the rom, zipaligned and signed it and then I moved the zip to my i9300. Then I get this error when I'm trying to flash the rom:
*Installing update...*
E:Error in /emmc/m0_signed_071212_225202.zip (Status 0)
*Installation aborted.*
I know the i9300 isn't officially supported but I was told Kitchen would also work with the i9300.
Btw, when extracting factoryfs.img and the file for CSC, Kitchen said something about crc32 problems, it expected something different than it calculated.
I hope someone could help me solve this problem.
Regards,
dejong12
did you check updater-script file?
Yup, I checked it, but no errors were returned and I couldn't anything in the file itself.
dejong12 said:
Yup, I checked it, but no errors were returned and I couldn't anything in the file itself.
Click to expand...
Click to collapse
can you post updater-script file and the original update-script file please using pastebin
Here are update_script and updater_script.
I read I need an edify file, but does anyone have that premade? I don't know the mount points etc.
dejong12 said:
I read I need an edify file, but does anyone have that premade? I don't know the mount points etc.
Click to expand...
Click to collapse
this the correct updater scripts for gs3 , you need update binary as well
http://pastebin.com/C9ktKbXs
auras76 said:
this the correct updater scripts for gs3 , you need update binary as well
http://pastebin.com/C9ktKbXs
Click to expand...
Click to collapse
Where can I get the correct update binary?
I just have to paste this file into my current updater script?
dejong12 said:
Where can I get the correct update binary?
I just have to paste this file into my current updater script?
Click to expand...
Click to collapse
i will send you
---------- Post added at 11:41 PM ---------- Previous post was at 11:40 PM ----------
dejong12 said:
Where can I get the correct update binary?
I just have to paste this file into my current updater script?
Click to expand...
Click to collapse
https://hotfile.com/dl/163449391/6b7935c/update-binary.html
auras76 said:
i will send you
---------- Post added at 11:41 PM ---------- Previous post was at 11:40 PM ----------
https://hotfile.com/dl/163449391/6b7935c/update-binary.html
Click to expand...
Click to collapse
Thank you for the file! Btw, I don't think I can use this for every rom I want to create if I choose different options, or can I?
dejong12 said:
Thank you for the file! Btw, I don't think I can use this for every rom I want to create if I choose different options, or can I?
Click to expand...
Click to collapse
you can use for every rom for sg3
auras76 said:
you can use for every rom for sg3
Click to expand...
Click to collapse
I've replaced update-binary and updater-script in my finished zip but I'm getting an status 6 error now, could you tell me what I did wrong?
dejong12 said:
I've replaced update-binary and updater-script in my finished zip but I'm getting an status 6 error now, could you tell me what I did wrong?
Click to expand...
Click to collapse
Flash rom again.. after getting the error, go to advanced>report error..
Then reboot your device... you will find a recovery.log file in clockworkmod directory of your sdcard...
There you can spot the error...
adiles said:
Flash rom again.. after getting the error, go to advanced>report error..
Then reboot your device... you will find a recovery.log file in clockworkmod directory of your sdcard...
There you can spot the error...
Click to expand...
Click to collapse
Here's the error report: http://pastebin.com/Yt8BHvrf/
Some lines say ALE8, but that's not the version I'm trying to flash...
The error is here
line 1 col 29: syntax error, unexpected BAD
Upload your script.
I will help you.
Andersondj said:
The error is here
line 1 col 29: syntax error, unexpected BAD
Upload your script.
I will help you.
Click to expand...
Click to collapse
The script I used was posted a few posts ago in this thread.
dejong12 said:
I've replaced update-binary and updater-script in my finished zip but I'm getting an status 6 error now, could you tell me what I did wrong?
Click to expand...
Click to collapse
create a folder named (aur) to rom zip and put boot.img , modem.bin and this file
- https://hotfile.com/dl/163506889/899d8be/flash_image.html
auras76 said:
create a folder named (aur) to rom zip and put boot.img , modem.bin and this file
- https://hotfile.com/dl/163506889/899d8be/flash_image.html
Click to expand...
Click to collapse
This doesn't work for me, I still get that status 6 error.
dejong12 said:
This doesn't work for me, I still get that status 6 error.
Click to expand...
Click to collapse
this is bad zip
auras76 said:
this is bad zip
Click to expand...
Click to collapse
Ok, I tried to rebuild the zip, but I want to make sure, do I have to create that map in the root folder of the zip? And is the name with or without parenthesis?
i have been messing with init.d for rooted/stock rom t230/nu and i have come up with a modified version of this >> http://forum.xda-developers.com/showthread.php?t=1912504
INSTRUCTIONS:
Flash the attacthed zip in twrp and reboot...
HOW DO I KNOW IF IT WORKED?
in root browser goto /data/local/tmp/ and if there is a file 'init.d_log_test.txt' and inside is written the date, it worked.
if the file is not present something went wrong? please let me know if it went wrong for you an i will fix it..
dont forget to hit thanks and also credit the @jamesst20 in the above link...
Ill give it a go.
Sent from my SM-T230NU
BookCase said:
Ill give it a go.
Sent from my SM-T230NU
Click to expand...
Click to collapse
let me know how it goes as i have only tested on my device... thnx
This will work.....I have it baked into my ROM.
One thing....I'd rename the install-recovery.sh to install-recovery-2.sh as that will break root. SU daemon is called by install-recovery.sh on boot. just a heads up.
g_ding84 said:
This will work.....I have it baked into my ROM.
One thing....I'd rename the install-recovery.sh to install-recovery-2.sh as that will break root. SU daemon is called by install-recovery.sh on boot. just a heads up.
Click to expand...
Click to collapse
i am building a rom at the moment and could not get my head round why it was breaking root lol... cheers dude..
Inside 4ndroid said:
i am building a rom at the moment and could not get my head round why it was breaking root lol... cheers dude..
Click to expand...
Click to collapse
Let me if your still having trouble with root afterwards.
g_ding84 said:
Let me if your still having trouble with root afterwards.
Click to expand...
Click to collapse
oh and in your rom it seems we cant update the su binary and have to flash an updated binary seperetely from within recovery.. i found a work around and now when i flash my rom it says binary needs updating an now in my rom the normal method works and alakasm success
if you need me to explain further pm me an i will go through how i managed it..
In the rom that you're working on is based on CyanogenMod or this stock?
on the other hand just flash this file in Stock T230XXU0ANK3'll see that this is
If you want to enable init.d, you simply install busybox from playstore and download universal init.d, and verify ...
checks in the system / etc / init.d contained in the file 00test & 08setperm :good:
working on my phone 4 tab 7 "T231 :fingers-crossed: :fingers-crossed:
sorry for my bad english
riotaruna said:
If you want to enable init.d, you simply install busybox from playstore and download universal init.d, and verify ...
checks in the system / etc / init.d contained in the file 00test & 08setperm :good:
working on my phone 4 tab 7 "T231 :fingers-crossed: :fingers-crossed:
sorry for my bad english
Click to expand...
Click to collapse
or you could just simply flash the file file in the OP takes alot less time an is simple an staight forward lol..
File is gone
hello,
Can someone help me why i cant install my modded settings.apk to lollipop 5.1?
i did not mod any XML files but edited 2 images from res and signed the apk and tried to install. no positive result.
Someone told me that settings.apk should not be signed.
someone help in this thing.
Thanks in advance
Settings must be signed with the platform key.
MasterAwesome said:
Settings must be signed with the platform key.
Click to expand...
Click to collapse
Can you please detail the step by step.?
When i tried it by signapk.jar I'am getting error while signing the apk after creating .keystore. When i Google'd it i got an info that it is already signed. What should i do to sign and install?
shmshd12 said:
Can you please detail the step by step.?
When i tried it by signapk.jar I'am getting error while signing the apk after creating .keystore. When i Google'd it i got an info that it is already signed. What should i do to sign and install?
Click to expand...
Click to collapse
You don't sign it at all. And you can't install it. You have to flash it with a zip in recovery.
zelendel said:
You don't sign it at all. And you can't install it. You have to flash it with a zip in recovery.
Click to expand...
Click to collapse
When i flashed the zip file it installed well in recovery but when i came to the system from recovery i couldn't find the settings apk installed.
Can you create a working signed zip file to flash in recovery for the attached apk.
Thnaks in Advance
There are plenty of tuts on how to do it yourself. The mount points are very different for each device so you will have to get a zip for your device that works and then just add your apk.
zelendel said:
There are plenty of tuts on how to do it yourself. The mount points are very different for each device so you will have to get a zip for your device that works and then just add your apk.
Click to expand...
Click to collapse
Now im confused on 1 simple thing.
should i add the apk in system/priv-app/settings or system/app/settings ??
shmshd12 said:
Now im confused on 1 simple thing.
should i add the apk in system/priv-app/settings or system/app/settings ??
Click to expand...
Click to collapse
Send me the apk i'll sign it install it using
Bash:
adb push ../Settings.apk /sdcard/
adb shell
su
mount -o remount,rw /system
rm pathToSettings.apk
cp /sdcard/Settings.apk pathToSettings.apk
chmod 0644 pathToSettings.apk
reboot
MasterAwesome said:
Send me the apk i'll sign it install it using
Bash:
adb push ../Settings.apk /sdcard/
adb shell
su
mount -o remount,rw /system
rm pathToSettings.apk
cp /sdcard/Settings.apk pathToSettings.apk
chmod 0644 pathToSettings.apk
reboot
Click to expand...
Click to collapse
Bro, here is the apk
the above mentioned apk is the wrong one!!!
please find the right apk from below attachment
thanks a lot
note that this is the settings.apk for hammerhead running LP 5.1
shmshd12 said:
Bro, here is the apk
the above mentioned apk is the wrong one!!!
please find the right apk from below attachment
thanks a lot
note that this is the settings.apk for hammerhead running LP 5.1
Click to expand...
Click to collapse
Aosp?
MasterAwesome said:
Aosp?
Click to expand...
Click to collapse
YES...EXTRACTED FROM GROGG'S rom 5.1
@MasterAwesome
Waiting for your signed settings.apk !!!
when will i get it ?
shmshd12 said:
@MasterAwesome
Waiting for your signed settings.apk !!!
when will i get it ?
Click to expand...
Click to collapse
Crap, I totally forgot about it... I was building something else. I'll upload it soon
Can someone else sign this or make a flashable zip?
shmshd12 said:
Can someone else sign this or make a flashable zip?
Click to expand...
Click to collapse
Relax and give him time. You would have had it by now had you done your own research and docent yourself.
zelendel said:
Relax and give him time. You would have had it by now had you done your own research and docent yourself.
Click to expand...
Click to collapse
I google'd a lot and I'm tired!!
That's the reason i started thread!!
shmshd12 said:
I google'd a lot and I'm tired!!
That's the reason i started thread!!
Click to expand...
Click to collapse
I think you mistake this for a support site. If you searched then you really didnt look very hard
http://forum.xda-developers.com/gal...tutorial-making-flashable-zips-edify-t1611615
That gives you everything you need to know to make it.
zelendel said:
I think you mistake this for a support site. If you searched then you really didnt look very hard
http://forum.xda-developers.com/galaxy-nexus/themes-apps/tutorial-making-flashable-zips-edify-t1611615
That gives you everything you need to know to make it.
Click to expand...
Click to collapse
Parsing error occurs while installing!!
So i need to sign the apk right?
In the above mentioned thread it only shows how to create a flashable zip or signed zip!!! I need to sign the apk!!
shmshd12 said:
Parsing error occurs while installing!!
So i need to sign the apk right?
In the above mentioned thread it only shows how to create a flashable zip or signed zip!!! I need to sign the apk!!
Click to expand...
Click to collapse
First off. No you should never sign a system APK. If you do it will conflict with the system Sig that all system apps use.
I told you once already. You cant install the apk that way. It has to be flashed in recovery.
zelendel said:
First off. No you should never sign a system APK. If you do it will conflict with the system Sig that all system apps use.
I told you once already. You cant install the apk that way. It has to be flashed in recovery.
Click to expand...
Click to collapse
but @MasterAwesome said that Settings must be signed with the platform key in the second post!! so are you telling that he is wrong?
I did a flashable zip by ZipMe app from playstore and flashed it...still the settings apk was not found in the app drawer!!!
@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