This is a beautiful black and yellow theme based off of DBZ's Super Saiya Jin. I hope all you fans truly enjoy it. Theme confirmed compatible with twrp 2.5.0.0 to most recent release of 2.6.3.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How To install
1.Navigate to Internal Storage (if you are on a 4.3 rom it will be in "sdcard0) than open your TWRP Folder
2.Create a folder inside your TWRP folder named "theme" (do not capitalize the name of this folder or it wont work)
3.Paste UI.zip in your "theme" folder and reboot your recovery
Worked perfect, and looks great :good:
kopower said:
Worked perfect, and looks great :good:
Click to expand...
Click to collapse
glad you like it bud...still accepting requests for custom themes for free
REV3NT3CH said:
glad you like it bud...still accepting requests for custom themes for free
Click to expand...
Click to collapse
I'm looking forward to the htc beats guy.
Quantumrabbit said:
I'm looking forward to the htc beats guy.
Click to expand...
Click to collapse
HTC Beats theme done...just gonna make a few preview images for it and ill have it uploaded by tonight
I installed this theme and everything worked fine, however I wanted to try your raven theme so I removed the theme from the theme folder and I'm stuck in a bootloop. The phone phone starts to boot then goes back to the white HTC screen and just keep looping that screen. I've uninstalled trwp 2.6.3 and still the same thing. I can get into bootloader as well as recovery I can flash zips and preform back ups but all with the same outcome. Any suggestion???? thanks in advance.
ghostt021 said:
I installed this theme and everything worked fine, however I wanted to try your raven theme so I removed the theme from the theme folder and I'm stuck in a bootloop. The phone phone starts to boot then goes back to the white HTC screen and just keep looping that screen. I've uninstalled trwp 2.6.3 and still the same thing. I can get into bootloader as well as recovery I can flash zips and preform back ups but all with the same outcome. Any suggestion???? thanks in advance.
Click to expand...
Click to collapse
Are you s-on? If so try fastboot flashing your ROMs boot.img. I don't think it is theme error. Did you dumlock to recovery and forget to restore boot? If so, the fastboot flash will fix it.
Reason I suggest that is I have done that a few times before I finally just s-offed
Sent from my DNA using my mind.
Uzephi said:
Are you s-on? If so try fastboot flashing your ROMs boot.img. I don't think it is theme error. Did you dumlock to recovery and forget to restore boot? If so, the fastboot flash will fix it.
Reason I suggest that is I have done that a few times before I finally just s-offed
Sent from my DNA using my mind.
Click to expand...
Click to collapse
Yes I am s-on, I'll give that a try. Thanks
ghostt021 said:
Yes I am s-on, I'll give that a try. Thanks
Click to expand...
Click to collapse
i also agree deleting or adding a twrp theme will and should not do this...its not flashing anything at all as its just overlapping images from the ui.zip really....i do also suggest if s-on flashing the boot image of your roms kernel...the only way i se anything messing up is an accidental deletion of the wrong file...only thing that should be removed is the ui file as posted in this or my other threads
REV3NT3CH said:
i also agree deleting or adding a twrp theme will and should not do this...its not flashing anything at all as its just overlapping images from the ui.zip really....i do also suggest if s-on flashing the boot image of your roms kernel...the only way i se anything messing up is an accidental deletion of the wrong file...only thing that should be removed is the ui file as posted in this or my other threads
Click to expand...
Click to collapse
Thanks, I don't think it's the theme either been reading post of people having same problem might just be the phone. Oh well I was planning on moving on to the moto x dev anyway:good::good::good: thanks
Hey REV3NT3CH, I finally got around to playing with this TWRP theming and, if you would be so kind, I have a question or two about the process... please. I have a pretty good grasp on the methodology -but- have you gotten the "curtain" splash image to work? I have looked around and tested some but with my first attempt, I keep getting the stock TWRP splash image. Maybe this is baked in by the TeamWin folks? Also, looking into your UI.zip. are some of the images "working images" that are not explicitly used? I know that some of the themes use the dual row larger square buttons and some use the single row more rectangular ones. Thanks for the thoughts! I am still learning as I go!
rgnicholas said:
Hey REV3NT3CH, I finally got around to playing with this TWRP theming and, if you would be so kind, I have a question or two about the process... please. I have a pretty good grasp on the methodology -but- have you gotten the "curtain" splash image to work? I have looked around and tested some but with my first attempt, I keep getting the stock TWRP splash image. Maybe this is baked in by the TeamWin folks? Also, looking into your UI.zip. are some of the images "working images" that are not explicitly used? I know that some of the themes use the dual row larger square buttons and some use the single row more rectangular ones. Thanks for the thoughts! I am still learning as I go!
Click to expand...
Click to collapse
i believe the curtain image is baked in...ive tried changing it via the ui.zip and just didnt work....all other images assign itself to somewhere except the preview image (shows what the theme looks like stock)....if youd like i can look into the curtain image a little more again
With curtain image you have to decompile than replace the image and recompile. I've also tried gif animation but gifs don't work lol
I could throw you one together if you want
Sent from my ADR6425LVW using xda app-developers app
bunchies said:
With curtain image you have to decompile than replace the image and recompile. I've also tried gif animation but gifs don't work lol
I could throw you one together if you want
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
your talking about the whole recovery itself right?
REV3NT3CH said:
your talking about the whole recovery itself right?
Click to expand...
Click to collapse
yeah. you have to take the recoery image than decompile it
EDIT: im gunna build a decompile and compile script right now
bunchies said:
yeah. you have to take the recoery image than decompile it
EDIT: im gunna build a decompile and compile script right now
Click to expand...
Click to collapse
thats what i thought....anybody have requests then i may do some soon
REV3NT3CH said:
i believe the curtain image is baked in...ive tried changing it via the ui.zip and just didnt work....all other images assign itself to somewhere except the preview image (shows what the theme looks like stock)....if youd like i can look into the curtain image a little more again
Click to expand...
Click to collapse
Thanks... you to bunchies! Don't worry about it. I just hoped that was a possibility. Yet, if you find a secret to make it work in an easy fashion, let me know. I appreciate your thoughts and I hope you don't mind if I use your xml file as a template
rgnicholas said:
Thanks... you to bunchies! Don't worry about it. I just hoped that was a possibility. Yet, if you find a secret to make it work in an easy fashion, let me know. I appreciate your thoughts and I hope you don't mind if I use your xml file as a template
Click to expand...
Click to collapse
im a high believer in what is open source should stay and remain open source just as long as the credibility is there....go ahead and have fun with it bud....if you need help you can pm me or hangouts me..... [email protected]
REV3NT3CH said:
im a high believer in what is open source should stay and remain open source just as long as the credibility is there....go ahead and have fun with it bud....if you need help you can pm me or hangouts me..... [email protected]
Click to expand...
Click to collapse
exactly.. also just threw this together for ya :good: this is how i edit recovery images.
Heres the tools - http://d-h.st/xJL
extract it to your ubuntu desktop and place the recovery.img you want to edit to the base of the new recovery folder
than open terminal and..
cd Desktop/Recovery
./unmkbootimg recovery.img > output.txt
mkdir ramdisk
cd ramdisk
gunzip -c ../initramfs.cpio.gz | cpio -i
Click to expand...
Click to collapse
hit enter in the terminal to execute the last line
Do Not Exit the terminal
than use your file explorer and go into ramdisk/res/images and delete the curtain.jpg and paste in the new curtain.xxx (i use a png image)
than go back to the terminal window and..
cd ..
tools/mkbootfs ramdisk | gzip > ramdisk-new.gz
./mkbootimg --kernel zImage --ramdisk ramdisk-new.gz --cmdline "console=ttyHSL3 androidboot.hardware=vigor no_console_suspend=1" --base 0x48800000 --pagesize 2048 -o recovery-new.img
Click to expand...
Click to collapse
hit enter in the terminal to execute the last line
and than flash the recovery-new.img in fastboot :angel:
bunchies said:
exactly.. also just threw this together for ya :good: this is how i edit recovery images.
Heres the tools - http://d-h.st/xJL
extract it to your ubuntu desktop and place the recovery.img you want to edit to the base of the new recovery folder
than open terminal and..
hit enter in the terminal to execute the last line
Do Not Exit the terminal
than use your file explorer and go into ramdisk/res/images and delete the curtain.jpg and paste in the new curtain.xxx (i use a png image)
than go back to the terminal window and..
hit enter in the terminal to execute the last line
and than flash the recovery-new.img in fastboot :angel:
Click to expand...
Click to collapse
thanks will definately be doing some stuff with this
Related
Here are some splash images that can be flashed to the htc evo view. It should work on the flyer but I don't have one to test on.
** Credits go to the original creators of these images. Unfortunately I don't know who they are **
splash-hand.img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
splash-android.img
splash-androidpissonapple.img
splash-droideatingapple.img
godzson.zip
GODZSON said:
I designed these 2 (View/Flyer) clean and simple splash images today, Feel free to use in custom roms, or personal usage..
Click to expand...
Click to collapse
** Your device must be s-off (nand unlocked) in order to flash/install this image **
Installation instructions:
1. Download nameofsplash.img
2. Reboot your device to bootloader.
3. In a command/terminal prompt enter
Code:
fastboot flash splash1 nameofsplash.img
4. Reboot your device and enjoy your new splash screen.
=================================================
-- Instructions to make your own splash image for flyer/view --
-- For windows --
1. Create an image with the dimensions 1024 height 600 width. Save your image as splash.extension (splash.bmp for example, png works, jpg may but I haven't tested it).
2. Rotate your image 90 degrees counterclockwise (windows image viewer is the easiest/fastest).
3. Download splash.zip and extract to a location of your choice.
4. Open new-splash.txt and edit "splash.png" to reflect your image extension (splash.bmp for example).
5. Save the file as new-splash.bat.
6. Move your image (from step 1) into the directory with the .bat and ffmpeg files.
7. Double click new-splash.bat. You should now have a file in the same directory named splash.img
8. Flash the image via fastboot and enjoy!
** Some Notes **
You will notice two files called pull-480x800.txt and pull-1024x600.txt.
These two files are essentially the same except for the size dimensions.
You will want to save these files as .bat (just like in step 5) after editing the size dimensions and image output extension (bmp instead of png) inside the text file.
After pulling you will have a file named splash.extension in the same directory.
The files use the name splash.extension (splash.img, splash.png, etc.) when pulling/creating
When creating a splash.img, the .bat file will look for an image named splash.extension (where extension is what you specified in step 4)
When pulling an image from splash.img, the .bat file will look for splash.img, rename it to splash-orig.img, and output the image according to the size dimensions and extension specified.
I hope this little writeup was easy to follow. If not please feel free to ask any questions!
Heh.... Cool! Just wish I had a View right now....
Is it works with flyer 3G too???
rrk said:
Is it works with flyer 3G too???
Click to expand...
Click to collapse
The device doesn't matter - the fact that the Flyer is displaying "evo view" is the problem.
ikingblack said:
The device doesn't matter - the fact that the Flyer is displaying "evo view" is the problem.
Click to expand...
Click to collapse
I can make the .img files if you provide the image you want. I'm not the best graphic artist but I can make the splash.img with no effort.
I stated evo view because that's the device I have and test on.
Can you make this an .img file for me?
MagicalSandwich said:
Can you make this an .img file for me?
Click to expand...
Click to collapse
See op for link.
Can you make this into splash for me
Can you make these into splash for me? would be much appretiated. are you using photoshop or what to create the .img file?
EDIT:
FYI the splash-android.img file won't download in your link
Bubbled said:
FYI the splash-android.img file won't download in your link
Click to expand...
Click to collapse
I just downloaded it now from the link. Works fine.
Edit: running behind in everything. I will try to have them up before this weekend is up. Sorry
Bubbled said:
Can you make these into splash for me? would be much appretiated. are you using photoshop or what to create the .img file?
EDIT:
FYI the splash-android.img file won't download in your link
Click to expand...
Click to collapse
OP updated. Enjoy!
lovethyEVO said:
I can make the .img files if you provide the image you want.
Click to expand...
Click to collapse
can you replace the HTC EVO 4G with HTC Flyer in the first image? I would like to install on my flyer. Thanks in advance
ovigt71 said:
can you replace the HTC EVO 4G with HTC Flyer in the first image? I would like to install on my flyer. Thanks in advance
Click to expand...
Click to collapse
I'm not the best graphic artist. If you can find someone who is a photoshop pro to edit the image I can make the splash. Sorry .
Can I ask how you made these? What tool did you use? What size image?
I've been using nbimg.exe to make these for all of my devices, but everything I make for my Flyer looks completely distorted when I flash. I've successfully flashed all of the .imgs you've created, so I know it's not my device.
here's a good tutorial -
Edit: link broke
You can also use any of the splash screens or boot animations from the Nook Color and there are a bundle of them out there if you do a search. The Nook color and HTC flyer /View screen are the same size.
I will try to have a write up by the end of the week of how I make the splashs as well as the files I used for anybody who wants to try their hand at making splash screens for this device or any other device.
lovethyEVO said:
I will try to have a write up by the end of the week of how I make the splashs as well as the files I used for anybody who wants to try their hand at making splash screens for this device or any other device.
Click to expand...
Click to collapse
Cool.
Also, I have a question. The splash screen is the HTC screen right? Once the quietly brilliant comes on it is just boot animation.zip correct?
So those who use fast boot this won't work.
ikingblack said:
Cool.
Also, I have a question. The splash screen is the HTC screen right? Once the quietly brilliant comes on it is just boot animation.zip correct?
So those who use fast boot this won't work.
Click to expand...
Click to collapse
You are correct. Whenever you shutdown the tablet completely the splash screen is the first image you see when it powers on. For people like me it's nice to change it since I don't use fastboot in the event I need to get into recovery or bootloader.
lovethyEVO said:
You are correct. Whenever you shutdown the tablet completely the splash screen is the first image you see when it powers on. For people like me it's nice to change it since I don't use fastboot in the event I need to get into recovery or bootloader.
Click to expand...
Click to collapse
Once I get a really good splash I will stop using fast boot then.
lovethyEVO said:
I will try to have a write up by the end of the week of how I make the splashs as well as the files I used for anybody who wants to try their hand at making splash screens for this device or any other device.
Click to expand...
Click to collapse
Can you tell me if this is the method you're using..?
Create image 600 pixels wide and 1024 high.
Save it as a 24 bit bmp file called splash1 (any name works)
Put the bmp in the nbimg tool directory.
Open cmd and cd to that directory then run command:
Code:
nbimg -F splash1.bmp -w 600 -h 1024
Take the output file and change the extension to .img
Make sure device is in fastboot and run command:
Code:
fastboot flash splash1 C:\nbimg\splash1.img
Thanks in advance.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi everyone, I wrote this simple little program to help with flashing kernels on S-ON HTC devices. The program is pretty simple and contains all of the needed files to flash your boot.img and push the necessary kernel modules, either while the phone is booted into Android or if you are stuck in a bootloop and can only get into the bootloader. The program is configured to flash a near-stock boot.img from the 2.13 base (only added init.d support) and the kernel modules for the kernel. In theory, you can replace the boot.img and modules from other kernels and flash through this program as well (more info in 3rd post)
Click to expand...
Click to collapse
Download:
v1.2.1 - For JB ONLY! https://dl.dropbox.com/u/6621763/boot-img-flasher-v1.2.1-jb.zip
v1.2.1 - For ICS ONLY! http://bit.ly/OGAGgn
Click to expand...
Click to collapse
Credits:
Morto_jeffrey for some code from Venom Flasher
patensas for the icon
Click to expand...
Click to collapse
Changelog
v1.2.1 JB RELEASE- 12.18.12
Updated boot.img and kernel modules from 3.15.651.6 RUU
v1.2.1 - 10.5.12
Fix default debug mode
Fix first time run procedure
Open log.txt on exit if debug enable
v1.2 - 10.4.12
Fixed version number not showing in program or log
Download - http://bit.ly/SzWucs
v1.1 - 10.2.12
Fix code when pushing files
Added logging to diagnose issues
Don't automatically detect when in fastboot, wait for user input
Download - http://bit.ly/T0d5T1
v1 - 10.2.12
Initial Release
Download - http://bit.ly/QooZHR
Click to expand...
Click to collapse
Info
How it works:
This program flashes whatever boot.img is placed in the "files" folder and moves whatever modules are in the "files\modules" to /system/lib/modules on your phone.
Click to expand...
Click to collapse
How to use:
Use the main menu to flash your boot.img to your phone. For most people, this will be the option they need to use. If you cannot boot (bootloop) then you need to get into the bootloader by pressing and holding power and volume down. This may take 10-15 seconds and you may see the bottom LEDs flashing in the process. In this case, please use the advanced menu to flash the boot.img (this way removes the adb steps to automatically boot into recovery, since you can't use adb if you're in a bootloop)
Click to expand...
Click to collapse
Flashing a different kernel than what is included with the program:
If you want to use this program to flash a different kernel than the stock 2.13.651.1 kernel, place the custom kernel boot.img in the "files" folder and also take the new modules for the kernel you want to flash, delete all the files in the "modules" folder, and put the new modules into the "modules" folder.
Click to expand...
Click to collapse
I'll test it out and report back.
---------- Post added at 04:36 PM ---------- Previous post was at 04:14 PM ----------
Usage instructions:
Open the zip file and extract the boot-img-flasher.exe and the files directory somewhere on your computer.
Boot your phone into bootloader/fastboot.
In the 'files' directory (example: C:\Flasher\Files) put the boot.img from your selected kernel.
In the modules directory (C:\Flasher\Files) put whatever modules come with your kernel.
Run boot-img-flasher.exe
Select option 1 (if flashing the stock kernel it comes with). Phone will reboot into bootloader and flash the kernel. Follow the directions.
Viper needs to make a few changes so it's not quite ready for prime time yet, but it should work. I'd wait for the next version, but if you're impatient, light it up and give it a shot
smw6180 said:
I'll test it out and report back.
---------- Post added at 04:36 PM ---------- Previous post was at 04:14 PM ----------
Usage instructions:
Open the zip file and extract the boot-img-flasher.exe and the files directory somewhere on your computer.
Boot your phone into bootloader/fastboot.
In the 'files' directory (example: C:\Flasher\Files) put the boot.img from your selected kernel.
In the modules directory (C:\Flasher\Files) put whatever modules come with your kernel.
Run boot-img-flasher.exe
Select option 1 (if flashing the stock kernel it comes with). Phone will reboot into bootloader and flash the kernel. Follow the directions.
Viper needs to make a few changes so it's not quite ready for prime time yet, but it should work. I'd wait for the next version, but if you're impatient, light it up and give it a shot
Click to expand...
Click to collapse
Thanks Steve, as always.
If you need to use this right away, boot into bootloader the go into the advanced menu and flash from there. You may see an Adb error when its rebooting, I will fix all this in about an hour or so.
Sent from my EVO using Tapatalk 2
-viperboy- said:
Thanks Steve, as always.
If you need to use this right away, boot into bootloader the go into the advanced menu and flash from there. You may see an Adb error when its rebooting, I will fix all this in about an hour or so.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
No sweat. It's what I do.
Always at it viper :thumbup:
When I saw thread title, I thought it was gonna be something that could be done from the phone, but I guess that's what flashIMGGUI is for, or am I wrong?
from my flying AOKP'd Evo LTE and xda premium
scottspa74 said:
Always at it viper :thumbup:
When I saw thread title, I thought it was gonna be something that could be done from the phone, but I guess that's what flashIMGGUI is for, or am I wrong?
from my flying AOKP'd Evo LTE and xda premium
Click to expand...
Click to collapse
Yeah, this will be from the computer Would be hard to have an app run on your phone that is bootlooping, now wouldn't it? :silly: Almost done with v1.1. Actually, it is done - someone is just whipping me up a kick ass icon
This is pretty cool. Thanks for the tool.
via eVo.
Blackcircle said:
This is pretty cool. Thanks for the tool.
via eVo.
Click to expand...
Click to collapse
Wait for the next one.
New version is up, works flawless. I DARE you to try an break it :silly: Still need to update the first few posts when I get back from the gym.
Enjoy!
-viperboy- said:
New version is up, works flawless. I DARE you to try an break it :silly: Still need to update the first few posts when I get back from the gym.
Enjoy!
Click to expand...
Click to collapse
Don't ever dare me to break something.
Could I please have some feedback on this program?
Sent from my EVO using Tapatalk 2
-viperboy- said:
Could I please have some feedback on this program?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
It works. Happy?
smw6180 said:
It works. Happy?
Click to expand...
Click to collapse
Fuuuuuuuuuu
Sent from my EVO using Tapatalk 2
-viperboy- said:
Fuuuuuuuuuu
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
lol
Nice good lookin out
This program saved my life yesterday. Thank you viper, thank you for your hard work.
Is it ok if we post this in other threads to help each other out of trouble?
bigdaddy619 said:
Is it ok if we post this in other threads to help each other out of trouble?
Click to expand...
Click to collapse
Of course
Sent from my EVO using Tapatalk 2
Want to port your own TWRP Theme?
So, if you don't know then I will share it here and inform the masses who read this .
I wrote two scripts, TWRPUI and TWRPIMAGE, that will port a TWRP theme from one resolution to another. I'm continuously looking for ways to improve it but for now it works VERY good.
It is best to grab a TWRP theme which is based on a higher resolution and port it to your lower resolution and for good reasons too. Enlarging the theme from a small resolution to a larger resolution could cause wear and tear on the theme by making it not appear as crisp and clean as it should.
Anyways, I will keep it short, but please note that GraphicsMagick is required in order to use TWRPIMAGE. I have compiled it for ARM devices and it can be found in my repo called, gm.
In addition, both scripts require the use of busybox.
Feel free to play around with it and if you come up with an idea for either of the scripts please feel free to share your insights with me.
Remember, the only stupid question or idea is the one which is not shared or expressed .
https://github.com/ModdingMyMind/TWRP_IMAGE_PORTER
A. To use the TWRP Theme:
You must go to /sdcard/TWRP on your device and create another folder named, theme.
Then take the zip and rename it to ui.zip.
Place the ui.zip inside of the theme folder.
Reboot in to your custom recovery and enjoy.
If you wish to not use it anymore, then just delete the zip file.
If you enjoy these themes, then a simple click on the thanks button will suffice. Please be sure to go and give thanks to the original author as well.
Credit goes to @z31s1g for the following themes. He has these available across many forums for many devices with close to or similar resolutions. You can check out his signature for further details. You can get a glimpse of his work here. The shared thread link for his themes are used as my base for porting them over from 720x1280 to 480x800.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
[COLOR="Red"][B]HOW TO USE AROMA FM with Holofied Themes:[/B][/COLOR]
[LIST=1]
[*]Download holofied_aromafm_191.zip.
[*]Flash the zip in recovery.
It will copy the flashable Aroma FM package to sdcard\TWRP\[B]aromafm\aromafm.zip[/B]
[*]Go to "settings" in TWRP and tick the option to use Aroma FM.
[*]Go back to main screen and select, File Manager
[*]Profit!
[/LIST]
Holofied Black (Ported) - By Modding.MyMind
Holofied Dark (Ported) - By Modding.MyMind
Holofied Light (Ported) - By Modding.MyMind
Holofied Play (Ported) - By Modding.MyMind : Credits for testing and feedback - @lordvincent 90
Holofied XDA (Ported) - By Modding.MyMind
Click to expand...
Click to collapse
Thanks bro.:victory: tested twrp 2.6.3.0 jb version and working correctly all functions
kenow said:
Thanks bro.:victory: tested twrp 2.6.3.0 jb version and working correctly all functions
Click to expand...
Click to collapse
Once I finish Light and XDA, there will be an update to all of them. The update will be specific to TWRP 2.7 due to new features that the TWRP offers within the ramdisk. Also added options and a different feel to them as well, thanks to z31s1g's hard work.
Sent from my C525c using Tapatalk
Modding.MyMind said:
Once I finish Light and XDA, there will be an update to all of them. The update will be specific to TWRP 2.7 due to new features that the TWRP offers within the ramdisk. Also added options and a different feel to them as well, thanks to z31s1g's hard work.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
We don't have TWRP 2.7 yet, only TWRP 2.6.3.0 which is working for some people and 2.5.0.0 which is working for most people. So it would be great if the themes are compatible with that older versions as well.
dansou901 said:
We don't have TWRP 2.7 yet, only TWRP 2.6.3.0 which is working for some people and 2.5.0.0 which is working for most people. So it would be great if the themes are compatible with that older versions as well.
Click to expand...
Click to collapse
No you don't have 2.7, you have 2.7.0.1 http://techerrata.com/file/twrp2/protou/openrecovery-twrp-2.7.0.1-protou.img
xpirt
2.5 here...btw thanks...
xpirt said:
No you don't have 2.7, you have 2.7.0.1 http://techerrata.com/file/twrp2/protou/openrecovery-twrp-2.7.0.1-protou.img
xpirt
Click to expand...
Click to collapse
Yeah, but those are unstable, built from an old abandoned tree.
Well, regardless of yalls current twrp issues, I plan to still share it, and when the time is ready, yall will be able to use them . Maybe, @xpirt, could take a closer look at the "abandoned tree"?
Sent from my C525c using Tapatalk
He's right:
- TeamWin's used tree: https://github.com/TeamWin/android_device_htc_protou/commits/master
- neXusPrime's updated tree: https://github.com/ProtoU/device_protou_recovery/commits/twrp2.7
There are some new fixes, cleanup and updates made. @neXus PRIME or others should tell TeamWin to update the tree to get latest version of TWRP.
xpirt
@dansou901, I'm curious to know exactly what kind of issues the latest TWRP has, if you can recall any of them?
Sent from my C525c using Tapatalk
Modding.MyMind said:
@dansou901, I'm curious to know exactly what kind of issues the latest TWRP has, if you can recall any of them?
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
I don't know much about those recovery but for example, I can see the recovery.fstab inside those recovery (e.g 2.5.0.0 & 2.7.0.1) is for ICS not JB.
As most of us are on JB, those recovery is no use for people with JB ROM.
2.7.0.1, ADB in recovery doesn't work .. even though it is easy to fix that, but I believe there are more issues other than wrong mountpoint and ADB.
ckpv5 said:
I don't know much about those recovery but for example, I can see the recovery.fstab inside those recovery (e.g 2.5.0.0 & 2.7.0.1) is for ICS not JB.
As most of us are on JB, those recovery is no use for people with JB ROM.
2.7.0.1, ADB in recovery doesn't work .. even though it is easy to fix that, but I believe there are more issues other than wrong mountpoint and ADB.
Click to expand...
Click to collapse
Yea, I was looking at both githubs that xpirt shared in his previous post. Any reason why those mount points were erroneous and or if correct at that time, then changed later? Been reviewing the commits and scratching my head asking myself, "why do that", lol.
Sent from my C525c using Tapatalk
Were there changes made to yalls partitions and such when upgraded? I'm more in less just curious
The themes that I will be providing in the future which work mainly off of TWRP 2.7 should also work on 2.6 and 2.5, however, there will be missing features that will only be applicable for 2.7 and so therefore any previous versions won't exactly be able to use nor have the full experience. The current themes I am porting will work for you guys though without any issues and the updates I will be providing shall be kept separate within the OP and attachments. Whoever is yalls current/active recovery developer - contact him or her and have that person reach out to teamwin. Hopefully this can be resolved :-/. If I had this device I would assist but unfortunately, I do not.
Sent from my C525c using Tapatalk
Future ports are on hold right now. Currently putting themes on to my github so I can keep track of changes. The main hold up was due to me tracking down apps to use on my device so I may be able to work on these when not by my pc - which I finally found two of them. This will also allow me to make branches so I can leave the master project alone and if working properly then merge the branches later on. This will be extremey useful so I don't have to keep making backups upon backups on my pc which can be tedious and hard to keep track of.
Also, this will allow me to commit any changes so I may provide it here to the public to review for ease and comfort that those who do use the themes can know that such changes have been made, and as well, know that solutions to problems are being implemented.
With that said, I will be adding the current themes I have shared on this thread to my github and once everything is good, I will continue my work on porting these themes. I just need time to set up my "work station". Thanks and enjoy.
My github
Sent from my C525c using Tapatalk
I fixed the minor error where the dividers for 'restart' and 'wipe cache & dalvik' were in the wrong places. They have been relocated. Op has been updated with the Holo Dark Theme. See attachments to download the latest version.
To see the changes made to the theme which resolved the issue then click here to review the commit on my Github.
Many thanks to @xpirt for letting me know about it.
Sent from my C525c using Tapatalk
This has been put on hold. Click here to see why.
Sent from my C525c using Tapatalk
I was just stopping by to say I'm going to try this theme out on my Supersonic, and wanted to know if it was possible for you to port just the curtain.jpg from the Black Holo theme. But if this is on hold, I guess I'll have to wait .
Thanks for porting this, though. I can now use this theme on 3 out of 4 of my devices
Captain_Throwback said:
I was just stopping by to say I'm going to try this theme out on my Supersonic, and wanted to know if it was possible for you to port just the curtain.jpg from the Black Holo theme. But if this is on hold, I guess I'll have to wait .
Thanks for porting this, though. I can now use this theme on 3 out of 4 of my devices
Click to expand...
Click to collapse
Sorry, been busy with working on some binaries, building a vrTheme, and also starting on a launcher APK theme.
I haven't abandoned this project, just got to fit it in to my free time lol.
Also, these themes will work just as long as your device resolution is 480x800. As for the curtain image. That is found within the actual TWRP recovery itself. Has nothing to do with the ui. In order to change the curtain you will need to unpack the ramdisk within your TWRP recovery and then replace the curtain. Afterwards, repack the TWRP recovery and flash to your recovery partition.
Sent from my C525c using Tapatalk
If anyone notices anything off with these themes please speak up about it so I can fix it really quick. I only have two eyes with a busy schedule .
Sent from my C525c using Tapatalk
Modding.MyMind said:
Sorry, been busy with working on some binaries, building a vrTheme, and also starting on a launcher APK theme.
I haven't abandoned this project, just got to fit it in to my free time lol.
Also, these themes will work just as long as your device resolution is 480x800. As for the curtain image. That is found within the actual TWRP recovery itself. Has nothing to do with the ui. In order to change the curtain you will need to unpack the ramdisk within your TWRP recovery and then replace the curtain. Afterwards, repack the TWRP recovery and flash to your recovery partition.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
This I know.
I was just hoping you could port one for this resolution. I'll replace it in my Omni/TWRP repo so I have it going forward . If not, that's fine, but I figured I'd ask. If you need a copy of the jpg I can upload it for you.
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Built from CM-11.0 sources with Mirage kernel
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
To take a screen shot, just slide left.
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut.
Download links
Last version can be found here:
Basketbuild.com
GOO.IM
Install instructions:
1.With fastboot:
Code:
fasboot flash recovery philz_touch_*.*.*_shooteru.img
2.With Rashr - Flash Tool:
Get Rashr - Flash Tool from play store : HERE
Download recovery image to sdcard, and flash it with the above app.
Known Issues:
Charging led not working
Off-mode charging is working ! (phone will boot to recovery and charge)
Should work on all HBOOTs
S-OFF REQUIRED !
XDA:DevDB Information
[RECOVERY] [SHOOTER] PhilZ Touch - 6.46.1 - Selinux support - 3.0 KERNEL, Tool/Utility for the HTC EVO 3D
Contributors
johnnyslt
Version Information
Status: Testing
Created 2014-06-30
Last Updated 2014-06-30
I made a recovery-flashable zip if you'd like it.
Thanks for the alternate recovery.
bigsupersquid said:
I made a recovery-flashable zip if you'd like it.
Thanks for the alternate recovery.
Click to expand...
Click to collapse
Sure! Give me the link and I'll add it to the OP.
md5sum 7d53b4453f1dbf975c334fefc4b103d3
//edit: this is now outdated, I would suggest using the newest from the OP.
i have been testing for a few days haven't had any problems as of yet besides when i first boot to recovery it just has a black screen for 5-10 sec before it comes up almost thought something was wrong. i use a 32g ultra sd card so it usually takes awhile to scan all the files since it is always full.
There's an update for Philz I don't know if its for all device tho also there seems to be a problem flashing virus venom aroma zips I will try and post a screenshot ..
This is what I get everytime I try and flash
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my PG86100 using Tapatalk 2
rrjskj said:
There's an update for Philz I don't know if its for all device tho also there seems to be a problem flashing virus venom aroma zips I will try and post a screenshot ..
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
That update if manly for f2fs additions.
I've build it anyway, because sd-ext wasn't working, so that's fixed now.
Recovery logs are located in /tmp
rrjskj said:
There's an update for Philz I don't know if its for all device tho also there seems to be a problem flashing virus venom aroma zips I will try and post a screenshot ..
This is what I get everytime I try and flash
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
Can you please try the attached one ?
johnnyslt said:
Can you please try the attached one ?
Click to expand...
Click to collapse
I'm on it ..
It's still a no go same message. I'm wondering if it the Rom because I can flash flashalot's recovery switcher with no problems but not this one
Sent from my PG86100 using Tapatalk 2
There's another update for philz by the way ..
Sent from my PG86100 using Tapatalk 2
rrjskj said:
There's an update for Philz I don't know if its for all device tho also there seems to be a problem flashing virus venom aroma zips I will try and post a screenshot ..
This is what I get everytime I try and flash
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
The flash is failing because it says you don't have a shooter or shooteru if your absolutely sure you do you can modify the updater script located in the aroma zip under Meta-inf/com/Google/android/updater-script just remove those first lines that look like your error to not check for the device name. Not all ROMs have that some check for boot loader versions others don't check anything at all just be careful once modified it can be flashed to any device and possibly brick it by flashing the wrong partitions. There could be something weird going on with the recovery if it works with other recoveries.
HideTheCookies said:
The flash is failing because it says you don't have a shooter or shooteru if your absolutely sure you do you can modify the updater script located in the aroma zip under Meta-inf/com/Google/android/updater-script just remove those first lines that look like your error to not check for the device name. Not all ROMs have that some check for boot loader versions others don't check anything at all just be careful once modified it can be flashed to any device and possibly brick it by flashing the wrong partitions. There could be something weird going on with the recovery if it works with other recoveries.
Click to expand...
Click to collapse
Yeah it don't work. Removing them few lines results in it not flashing period . thanks anyways ..
Sent from my PG86100 using Tapatalk 2
What a great recovery I use it on my note 2 and like it better than any recovery. Plus it will read and backup in both twrp and cwm styles.
Sent from my SPH-L900 using XDA Premium 4 mobile app
<*shameless plug*>
[TOOL]Flashable recovery zip template
to avoid fastboot or an app or adb in recovery.
//edit: it seems possibly inappropriate to post it here but I thought since the original flashable zip was accepted it'd be ok. I'll remove this from here if requested.
This seems to be working good so far but I get this bad boot error every time I boot into recovery.
You can see the error in the log on the screenshot.
I love this recovery btw.
Thanks for porting it for us.
linsalata28 said:
This seems to be working good so far but I get this bad boot error every time I boot into recovery.
You can see the error in the log on the screenshot.
I love this recovery btw.
Thanks for porting it for us.
View attachment 2790015
Click to expand...
Click to collapse
Can you get me the recovery.log from /tmp ?
I need to see the whole error message.
johnnyslt said:
Can you get me the recovery.log from /tmp ?
I need to see the whole error message.
Click to expand...
Click to collapse
I got this from cache/recovery/last_log
Not sure where to find tmp. I've seen it before but for some reason I can't for the life of me find those logs.
Here is a link to that log last_log I think it says the same thing but if you can give me the path to tmp I'll post that also.
Thanks again.
linsalata28 said:
I got this from cache/recovery/last_log
Not sure where to find tmp. I've seen it before but for some reason I can't for the life of me find those logs.
Here is a link to that log last_log I think it says the same thing but if you can give me the path to tmp I'll post that also.
Thanks again.
Click to expand...
Click to collapse
That log has what I need.
I think I know what the problem is, and I'll try to fix it.
Is there a way to fix permissions from within this recovery? If so I can't figure out how.
If not does anyone have a flashable script that will only fix permissions?
TIA
linsalata28 said:
Is there a way to fix permissions from within this recovery? If so I can't figure out how.
If not does anyone have a flashable script that will only fix permissions?
TIA
Click to expand...
Click to collapse
that function has been removed from newer versions of CWM this post has what your looking for http://forum.xda-developers.com/showthread.php?t=2398339
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
attached is recovery log sir
Er. Aditya said:
attached is recovery log sir
Click to expand...
Click to collapse
The error you see in recovery is one we have seen already and I don't know how to fix it or why it's broken. I think it has something to do with Windows though. It seems the config directory in the rom is not getting extracted to /tmp. When it tries to run /tmp/configure.sh it does not exist. Then it tries to get info from /tmp/config which is also not there because configure.sh was never run to create it. The problem is that the zips appear to be the same with the same contents, same updater-script contents, etc. If built on Windows it does not work. If built on Linux it works. I am not a Windows guy (for these and many other reasons lol) so I have no idea what the difference is. If you have any ideas please let me know. Has anyone built a working flashable zip on Windows using this kitchen?
SuperR. said:
sepolicy-inject is not available for windows currently. I should have removed the option for Windows, and will in the next update. Is this a feature that still needs to stick around? I am not sure if I can get it working in Windows due to the pre-compiled Linux libs in the source. I am also not sure if you can compile libsepol on Windows. If you can get this source compiled for Windows, I can add the feature
The error you see in recovery is one we have seen already and I don't know how to fix it or why it's broken. I think it has something to do with Windows though. It seems the config directory in the rom is not getting extracted to /tmp. When it tries to run /tmp/configure.sh it does not exist. Then it tries to get info from /tmp/config which is also not there because configure.sh was never run to create it. The problem is that the zips appear to be the same with the same contents, same updater-script contents, etc. If built on Windows it does not work. If built on Linux it works. I am not a Windows guy (for these and many other reasons lol) so I have no idea what the difference is. If you have any ideas please let me know. Has anyone built a working flashable zip on Windows using this kitchen?
Click to expand...
Click to collapse
U can surely remove that feature if u like hardly used ....
I am gonna make a rom on linux too and see if that flashes...u need anything to compare or check sir ?
I remember last time too i had issue for mounting when rom created on linux..let me try one now and report back
edit :\ @SuperR. dev check this screenshot
it shows mounting error still rom flashed and booted good
Er. Aditya said:
U can surely remove that feature if u like hardly used ....
I am gonna make a rom on linux too and see if that flashes...u need anything to compare or check sir ?
I remember last time too i had issue for mounting when rom created on linux..let me try one now and report back
edit :\ @SuperR. dev check this screenshot
it shows mounting error still rom flashed and booted good
Click to expand...
Click to collapse
It may have already been mounted so it gave an error. We can deal with that later since it flashed and booted. Now we need to find out what the difference is between the Linux created ROM and the Windows created ROM. Were they both created using the same kitchen version, same firmware, same procedure? The ONLY difference is Windows vs. Linux, right? If so, can you send the updater-script from both so I can compare?
Using Windows for building android is kinda looking like someone taking square wheels to a skatepark and expecting fluid motion.. [emoji23] [emoji23]
Sent from my N9515 using Tapatalk
bcrichster said:
Using Windows for building android is kinda looking like someone taking square wheels to a skatepark and expecting fluid motion.. [emoji23] [emoji23]
Sent from my N9515 using Tapatalk
Click to expand...
Click to collapse
These wheels are rolling faster each day. We will ride
SuperR. said:
These wheels are rolling faster each day. We will ride
Click to expand...
Click to collapse
Lmao. Right on! If anyone can get this right, it's You and these guys helping here @SuperR. [emoji41] Catching some air!
Sent from my N9515 using Tapatalk
SuperR. said:
It may have already been mounted so it gave an error. We can deal with that later since it flashed and booted. Now we need to find out what the difference is between the Linux created ROM and the Windows created ROM. Were they both created using the same kitchen version, same firmware, same procedure? The ONLY difference is Windows vs. Linux, right? If so, can you send the updater-script from both so I can compare?
Click to expand...
Click to collapse
yes both were created using latest kitchen 3.0.1.4 , same firmware and procedure
here are the scripts sir
SuperR. said:
v3.0.1.8
Changes:
Windows: Use 7-zip (included) to extract img files instead of Imgextractor.
Windows: Fixed missing symlinks in updater-script.
Windows: Fixed many file contexts not being set correctly.
Windows/Linux: Fixed system/SYSTEM on devices that use SYSTEM.
Linux: Do not create metadata lines for symlinks.
I think this will fix most of the flashing problems. Let me know how it goes
WINDOWS NOTE: It is important that the tools get updated. The updater should take care of it, but if you get errors that 7z is not found, go to Misc tools > Reset tools.
IMPORTANT: Start your rom fresh and extract from system.img again. Make sure you delete 00_project_files directory if you are reusing an existing project.
Click to expand...
Click to collapse
i still got the error 7 even i clean cloned kitchen sir
Er. Aditya said:
i still got the error 7 even i clean cloned kitchen sir
Click to expand...
Click to collapse
Can you send the updater-script and recovery.log?
There is still one problem I need to solve for sure... file capabilities in Windows. Currently there is a file with capabilities listed and it is checked when creating an updater-script in Windows. In the case of your ROM, it is not accurate. The only non-standard capability in your firmware is /system/bin/run-as which is correct in your updater-script. However, the rest should all be 0x0 and there are a few that are not. You could try changing them to 0x0 and zip the ROM back up.
It has also crossed my mind that there may be something strange about the zip itself in Windows. I am not sure of this at all but in my tests of kitchen v3.0.1.8 and your firmware, the updater-script comes out nearly identical in Linux and Windows with only the above mentioned capability differences. Maybe the compression level of the zip is too high or low? You could try manually zipping the ROM to find out if the zip process is causing an issue.
It seems that not a single working flashable zip has come out of this kitchen running Windows so far and I am running out of ideas about what is causing it
edit: Attached below is a modified updater-script for your firmware with the capabilities corrected
SuperR. said:
Can you send the updater-script and recovery.log?
There is still one problem I need to solve for sure... file capabilities in Windows. Currently there is a file with capabilities listed and it is checked when creating an updater-script in Windows. In the case of your ROM, it is not accurate. The only non-standard capability in your firmware is /system/bin/run-as which is correct in your updater-script. However, the rest should all be 0x0 and there are a few that are not. You could try changing them to 0x0 and zip the ROM back up.
It has also crossed my mind that there may be something strange about the zip itself in Windows. I am not sure of this at all but in my tests of kitchen v3.0.1.8 and your firmware, the updater-script comes out nearly identical in Linux and Windows with only the above mentioned capability differences. Maybe the compression level of the zip is too high or low? You could try manually zipping the ROM to find out if the zip process is causing an issue.
It seems that not a single working flashable zip has come out of this kitchen running Windows so far and I am running out of ideas about what is causing it
edit: Attached below is a modified updater-script for your firmware with the capabilities corrected
Click to expand...
Click to collapse
u have been a rock and we are so glad ur trying to get this to work sir i am attaching a working script and supeR script with recovery log
edit : the modified one again gave that error
OMJ said:
Fyi, I was able to build & successfully flash a rom via Windows kitchen on the latest update
Click to expand...
Click to collapse
Woo hoooo!!!! That is great news...but also confusing lol. Now we need to figure out why @Er. Aditya is getting this:
Code:
Checking config ...
minzip: Extracted 1 file(s)
about to run program [/tmp/configure.sh] with 1 args
run_program: execv failed: No such file or directory
OMJ said:
Fyi, I was able to build & successfully flash a rom via Windows kitchen on the latest update
Click to expand...
Click to collapse
samsung device ?
SuperR. said:
v3.0.1.9
Changes:
Windows: Fixed b key press not being recognized.
Added a Back option to the root method options.
Only allow key presses that correspond to menu options.
Fixed project name adding an extra superr_ when creating new project from the project selection menu.
Set permissions of configure.sh to 777 instead of /tmp to 755.
@Er. Aditya - This includes the change I sent you in the PM. No clue if it will work for you, but worth a try. No need to extract the system.img again if you extracted using v3.0.1.8. Just change perm types to something else and then back to set_metadata and it will update the updater-script for you.
Click to expand...
Click to collapse
sadly it still dint worked :'(
i clean cloned again so no old kitchen leftovers
SuperR. said:
Woo hoooo!!!! That is great news...but also confusing lol. Now we need to figure out why @Er. Aditya is getting this:
Code:
Checking config ...
minzip: Extracted 1 file(s)
about to run program [/tmp/configure.sh] with 1 args
run_program: execv failed: No such file or directory
Click to expand...
Click to collapse
another fyi---I was getting the same but I usually rip out the config folder & code from updater-script, no need for it on my ROMs
Er. Aditya said:
samsung device ?
Click to expand...
Click to collapse
HTC
Er. Aditya said:
sadly it still dint worked :'(
i clean cloned again so no old kitchen leftovers
Click to expand...
Click to collapse
Do ROMs flash properly when created in kitchen v2.x ? If so, I am clueless about what is going on. If not, I clearly need to change how we mount/format.
OMJ said:
another fyi---I was getting the same but I usually rip out the config folder & code from updater-script, no need for it on my ROMs
Click to expand...
Click to collapse
At least that narrows the issue down to configure.sh, unless you manually zip your ROMs. If so, then it still could be the zip process which is handled by the Python zip() module currently. I could switch this over to 7-zip in Windows if needed now that it is included anyway.
SuperR. said:
Do ROMs flash properly when created in kitchen v2.x ? If so, I am clueless about what is going on. If not, I clearly need to change how we mount/format.
At least that narrows the issue down to configure.sh, unless you manually zip your ROMs. If so, then it still could be the zip process which is handled by the Python zip() module currently.
Click to expand...
Click to collapse
i have been having issues since this config.sh has been introduced sir
Er. Aditya said:
i have been having issues since this config.sh has been introduced sir
Click to expand...
Click to collapse
That is actually good news believe it or not It means that probably the kitchen is now producing working roms in Windows...just not in your device lol. We can work on getting it working for your device too I will need to figure out if we can get configure.sh to run on your device. I will put together some small flashable zips for testing if you don't mind. They won't change anything, just print on the screen so we can see if it works.
SuperR. said:
That is actually good news believe it or not It means that probably the kitchen is now producing working roms in Windows...just not in your device lol. We can work on getting it working for your device too I will need to figure out if we can get configure.sh to run on your device. I will put together some small flashable zips for testing if you don't mind. They won't change anything, just print on the screen so we can see if it works.
Click to expand...
Click to collapse
[emoji23] [emoji23] Nice!! [emoji41] [emoji41]
Sent from my N9515 using Tapatalk
Er. Aditya said:
I am ready!
Click to expand...
Click to collapse
Here are 3 to try. I may come up with some others if they don't work. When you flash it, we want to see the by-name path on the screen and not get errors. Let me know how it goes