Develop Bugs

.dll Request

Can anyone extract shellres.dll, browsres.dll and outres.dll from the WM6 ROM and post 'em here?
TIA
--Mal

I'd love if someone posted the entire rom extract I tried but couldn't get any of the tools around here to extract and image-ify the nb files from the T-Mobile distribution.

I tried to extract those files for Malatesta but had no luck. Does anyone know what tools will work with the Excalibur?

g-funkster said:
I'd love if someone posted the entire rom extract I tried but couldn't get any of the tools around here to extract and image-ify the nb files from the T-Mobile distribution.
Click to expand...
Click to collapse
Curses! lol
Yeah there's still a bunch of little things we can take out of WM6 for WM5 devices...hopefully something will be figured out.
And thanks curtislanham for trying too.
Anyone else have any input?

I think I have successfully dumped my ROM. I have never done it before. I am using the official WM6 ROM released by T-Mobile on 5/4/07....the contents of the dump folder are 113MB in size.....does this seem reasonable? Malatesta I do have the files you are looking for but am unable to attach them here. If you can give me your email I will send them to you.

curtislanham said:
I think I have successfully dumped my ROM.
Click to expand...
Click to collapse
Please can you explain how you did that?
I need the tapres.dll in Windows folder.
Could you please post it (or PM over the board)?
Thanx alot

Keep in mind I am new to smartphones and Windows Mobile for that matter. I ran the Dash update posted on T-Mobile's website (Dash_Software_Update_1.22.531.4.exe). I used psdread to create an img file on my hard drive. Then I used prepare_imgfs and view_imgfs to extract the contents of the img file. The only thing is that the directory structure is not intact. Each file that was extracted resides in it's own folder, accompanied by an imageinfo.txt file, and S000, S001, S002. S003 files.

curtislanham said:
I think I have successfully dumped my ROM. I have never done it before. I am using the official WM6 ROM released by T-Mobile on 5/4/07....the contents of the dump folder are 113MB in size.....does this seem reasonable? Malatesta I do have the files you are looking for but am unable to attach them here. If you can give me your email I will send them to you.
Click to expand...
Click to collapse
Sweet! just go to http://www.rapidshare.de and upload it, and then post the resulting URL here and we'll take it from there. literally!

I will post it as soon as I get home and post the link here. Rapidshare is blocked here at work.

Damn.
I can't get those files registered in my system.
They're suppose to be the system icons (for those who are wondering) but my system just hangs after I replace them.
I've tried notsignedoff.cab and regsrvce.exe to no avail (and I don't have regasm.exe to work with).
Hmmm....I think I need to kill off the .dlls first before I replace/sign them but I'm not sure how to do that as they don't show up in my Processes viewer.
Calling g-funk! lol

Ok all you hackers and developers, tell me if this is what you have been waiting for......
http://rapidshare.com/files/31884903/T-Mobile_Dash_WM6__Official_Release__ROM_Dump.zip

malatesta said:
Damn.
They're suppose to be the system icons (for those who are wondering) but my system just hangs after I replace them.
Click to expand...
Click to collapse
I think we had similar ideas
The tapres.dll holds the image of the Windows-Flag in the Start-button, which I wanted to change to an apple (for iPhone Homescreens) or a penguin or whatever.
I hope you can get the changed .dll's accepted by the phone.
Just an idea:
With CeleTask you can see what processes use this dll's. Maybe you could kill these processes and then change the .dll.
With my tabres.dll I had no luck because there are six processes which use it and the phone freezes after killing the last of them...
BTW: Thx to curtislanham for the work

r0p3 said:
I think we had similar ideas
The tapres.dll holds the image of the Windows-Flag in the Start-button, which I wanted to change to an apple (for iPhone Homescreens) or a penguin or whatever.
I hope you can get the changed .dll's accepted by the phone.
Just an idea:
With CeleTask you can see what processes use this dll's. Maybe you could kill these processes and then change the .dll.
With my tabres.dll I had no luck because there are six processes which use it and the phone freezes after killing the last of them...
BTW: Thx to curtislanham for the work
Click to expand...
Click to collapse
indeed we did have the same idea!
Funny thing is I tried CeleTask too (great program) but it only showed .exe files (even the hidden ones) but I couldn't see any .dlls. Searching for a program to bring up the .dlls lead to nowhere.
I know people have gotten this to work on the non-landscape devices, usually without too much hassel. Guess we'll have to wait till some of the more expert people take a gander at the files...
and thanks curtislanham, hopefully now we can start ripping part WM6 and posting it piecemeal, lol.

I found a wm6 version of shellres.dll on another site and I was able to overwrite mine on the Q. I didn't try any of the other files. First boot after I overwrote, it worked and my icons for a lot of things changed, many look Great though the IE looks a bit weird against a white background and the messaging icon, I'm no big fan of either.
Note: Upon booting, my Q made a serious of Alert sounds, I pressed the left softkey and was allowed to confirm the first-run alert for the dll.
I tried copying over the version of shellres posted here, but it just would not let me overwrite the new version I already have

curtislanham said:
Ok all you hackers and developers, tell me if this is what you have been waiting for......
http://rapidshare.com/files/31884903/T-Mobile_Dash_WM6__Official_Release__ROM_Dump.zip
Click to expand...
Click to collapse
thank you so much!

malatesta said:
indeed we did have the same idea!
Funny thing is I tried CeleTask too (great program) but it only showed .exe files (even the hidden ones) but I couldn't see any .dlls. Searching for a program to bring up the .dlls lead to nowhere.
I know people have gotten this to work on the non-landscape devices, usually without too much hassel. Guess we'll have to wait till some of the more expert people take a gander at the files...
and thanks curtislanham, hopefully now we can start ripping part WM6 and posting it piecemeal, lol.
Click to expand...
Click to collapse
When you go in CeleTask to the "Process" Page you'll find your running .exe's.
Simply "click" on any and you see what dll's this exe is using.
Go through all (also hidden ones) and you have the exe's you have to kill.
Maybe you can overwrite when the dll isn't in use anymore.
But when I read g-funkster's post I am sure there is an easier (and also "cleaner") way to get the dll's changed.
I believe the answers might already be found here in another (PPC)-forum/wiki and our issue is just "noob-stuff"

g-funkster said:
I found a wm6 version of shellres.dll on another site and I was able to overwrite mine on the Q. I didn't try any of the other files. First boot after I overwrote, it worked and my icons for a lot of things changed, many look Great though the IE looks a bit weird against a white background and the messaging icon, I'm no big fan of either.
Note: Upon booting, my Q made a serious of Alert sounds, I pressed the left softkey and was allowed to confirm the first-run alert for the dll.
I tried copying over the version of shellres posted here, but it just would not let me overwrite the new version I already have
Click to expand...
Click to collapse
I take it it's the one from a certain Chinese site like PxDx...? B/c I have that one but haven't tried it (I thought there was a warning about using it on landscape devices). If not, could you post it here?
Also, I assume besides the initial boot up alert/sounds it runs fine now?
[b/]r0p3[/b], good to know...next time I might try that, although I need a day to recover from all the hard-resets, lol.

Yep, that's the site
lol you listen to those guys?! yes that was the site, those ppl don't make sense most of the time so, meh, Sprite Backup if anything.
See the attached images, the majority of icons are improved, for instance, the non-icon icon (see the AE.png for Internet Explorer) is much prettier and the majority of icons for everything else are nice.
But yeah, the icon for IE is off, or maybe I'm picky. you be the judge. Also, I can't seem to get rid of the shellres once its installed. And yes, it works fine after the alerts and confirm.
{
"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"
}

g-funkster said:
lol you listen to those guys?! yes that was the site, those ppl don't make sense most of the time so, meh, Sprite Backup if anything.
Click to expand...
Click to collapse
lol, guess I shouldn't listen to them! I was just worried. Then again I had to hard-reset numerous times myself soo...
I put a post up at ppcgeeks about this for others. I like the look a lot better, plus it's simple to do.

[Theme] LithiumMod Blueberry port (v.8)

First off I need to give credit where credit is due. Fisha21 blazed the trail with the first themed Uruk framework and did the hardwork of figuring out the steps to make it happen. Secondly, the themed pieces in this framework came mostly from JRummy16's blueberry LithiumMod so I claim absolutely no credit for that. There are other pieces picked up here and there, but I apologize for not knowing where they all came from.
This is mostly a complete work, but there is always room for improvement so I don't want to call it a 1.0. See the screenshots below for a small sample of what has been done, but there are many other tweaked images (something like 200-ish).
This is my first release to the public - normally I'd tweak things for my own personal use and never spread it around, but since there isn't a huge theme library for the Archos I thought I'd share for anybody that's interested. Constructive criticism is appreciated; if you find something that needs fixing please let me know and I can adjust it. I in no way think this work is perfect, but it's not too shabby in my opinion.
{
"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"
}
This will work on Uruk running off the SD or from the internal storage. Follow Fisha21's install steps:
"How to install
Needless to say, only attempt this if you are comfortable modifying system files. As we are using the SDE for this, the potential risk of bricking/ irreversible damage is low, but you should still have some idea what you're doing!
Just to clarify, I am using this on an UrukDroid 0.5 rooted Archos 101. I don't see any reason why it shouldn't work on any previous UrukDroid version, or other device sizes, but I haven't tested on any other configuration.
I know there are other (semi-permanent) root methods out there, and I know some people have UrukDroid running from their internal SD. I don't know how/if this will work with those setups, and I can't offer any advice/help for anyone wanting to try it in those setups. PROCEED CAREFULLY if you decide to try!
There are probably lots of other (neater) ways of doing this but this is the way I've found to work consistently for me.
All file manipulation on the device was done with Root Explorer.
1. Unzip the attached [bluep0rkframework-res.zip] to your SD card (the largest partition). Can be done directly on device, or over USB.
2. Find your original framework-res.apk (/system/framework) and back it up. I stored the backup in /system/framework.old, but its up to you - keep it safe! I would suggest keeping a copy on your computer also - you'll see why later!
3. Navigate to where you saved the new framework-res.apk, and change permissions to those shown in the screenshot below. I used the Root Explorer context menu, but those who prefer terminal commands, thats chmod 644.
4. Now MOVE (not copy) that .apk into the /system/framework folder. It will ask if you want to replace the existing file, just hit ok.
[p0rk burn: I'm not sure if my files will change color like Fisha's, but once you move it into the folder it should sit there for a while in RootExplorer - you will be able to scroll up and down but using the home key or any other buttons will not do anything - that means the new framework is loading, The rest of the setup should be like Fisha21 described: the screen will go black after a few minutes and sit for a little bit, before the homescreen loads back up.]
Now reboot the system.
The black screen after the UrukDroid screen may last a minute longer than normal, but just be patient. When it all comes back, you should see your new notification icons!
Once again, only do this if you are comfortable with editing system files. Though the risk of bricking is low, I can't offer any help if you do manage to kill your Archos!"
View attachment bluep0rkframework-res.zip
bluep0rk for Uruk .6 - View attachment bluep0rkframework-uruk6.zip

Reserved for the pants party

Nice work, looks good! I can't seem to resize the tickbox icons without them looking very untidy, so may have to borrow yours...

I love this theme so much. but it not work on my device (Archos-101).
My device root with this method http://forum.xda-developers.com/showthread.php?t=930197
every time that I had tried to replace /system/framework, after reboot my device I have found Loop Reboot problem.

jakkrith said:
I love this theme so much. but it not work on my device (Archos-101).
My device root with this method http://forum.xda-developers.com/showthread.php?t=930197
every time that I had tried to replace /system/framework, after reboot my device I have found Loop Reboot problem.
Click to expand...
Click to collapse
Out of curiosity, which firmware version are you on?

fisha21 said:
Out of curiosity, which firmware version are you on?
Click to expand...
Click to collapse
- Archos Firmware 2.1.04
- Archos SDE
- chulri's custom initramfs+kernel 2.1.04 (+rw)

jakkrith said:
- Archos Firmware 2.1.04
- Archos SDE
- chulri's custom initramfs+kernel 2.1.04 (+rw)
Click to expand...
Click to collapse
I had problems installing my own framework after updating to Uruk 0.6, which is also based in part on 2.1.04. Not sure if there was some change in the other contents of framework-res in the newer firmwares, but when I installed mine, I got into this loop where the soft buttons would appear on a black screen for a few seconds, disappear then reappear again. Is that what you experienced? I fixed mine by repacking my custom icons into a new framework-res extracted from the newest firmware.
Would you try installing my latest version from the theme forum, and see if that will work on your setup? I have also found a (hopefully) easier method, but it does require ADB.
Just to be clear, I'm not trying to hijack p0rn burn's thread or encourage people to use my framework over his. It would just be interesting to see if changing the base framework-res did make a difference, or if I unknowingly did something else to fix things. I have PM'd p0rk burn about my findings as well, so hopefully we can get both versions working!

The more help the better. Ill try to get a new framework up on monday for the new fw. Im on uruk .6 now so i need it too.

As promised, I have uploaded the blue themed framework for Uruk .6. It is attached to the first post for those of you that are interested. Please make sure you use the proper one, otherwise you will have to fix it before being able to boot back into Uruk.
This one has the modified progress_horizontal.xml so the volume bar and other progress indicators are properly themed.
If I feel motivated (or think people would actually care) I'll see about tweaking this a bit more and/or doing some more ports.

p0rk burn said:
As promised, I have uploaded the blue themed framework for Uruk .6. It is attached to the first post for those of you that are interested. Please make sure you use the proper one, otherwise you will have to fix it before being able to boot back into Uruk.
This one has the modified progress_horizontal.xml so the volume bar and other progress indicators are properly themed.
If I feel motivated (or think people would actually care) I'll see about tweaking this a bit more and/or doing some more ports.
Click to expand...
Click to collapse
runs for me (0.6 uruk and zImage from ardatdat, running on sd)
nitpicks:
- beautiful widgets take a long time to load
- power off/reboot ... menu from powerbutton sometimes not responsible (could be another reason too i guess)
will try it a few days to see if its stable
like the theme, thanks for your work

woti23 said:
runs for me (0.6 uruk and zImage from ardatdat, running on sd)
nitpicks:
- beautiful widgets take a long time to load
- power off/reboot ... menu from powerbutton sometimes not responsible (could be another reason too i guess)
will try it a few days to see if its stable
like the theme, thanks for your work
Click to expand...
Click to collapse
I'll try the widgets on my end but I haven't had any of those issues. My guess is it has to do with the zImage because I don't think changing out .pngs would cause those issues, but definitely something worth looking at.
Thanks for the feedback.

p0rk burn said:
I'll try the widgets on my end but I haven't had any of those issues. My guess is it has to do with the zImage because I don't think changing out .pngs would cause those issues, but definitely something worth looking at.
Thanks for the feedback.
Click to expand...
Click to collapse
you know, the blue market hack would fit perfectly to your theme ;-)

I know, I thought about throwing it in when I first started this but wanted to get a proof of concept first and then sort of forgot about it. With all the problems people have had with market installs on Uruk I was a little afraid to mess with it.
I'll see what I can do though.

p0rk burn said:
I know, I thought about throwing it in when I first started this but wanted to get a proof of concept first and then sort of forgot about it. With all the problems people have had with market installs on Uruk I was a little afraid to mess with it.
I'll see what I can do though.
Click to expand...
Click to collapse
hehe, i have the blue market (vs 2.3.3 from the xda thread) on the archos 101 now
i like the blue and its working
gonna see if it the blue and transparent market works too

Once again Fisha21 came through for the scene. If you want the blue market follow these steps. Should work with the other 2.3.3 markets, but I can't vouch for it personally. On the other hand, if you reached this point in tweaking your Archos fixing a botched vending mod probably doesn't scare you.
fisha21 said:
I just use Root Explorer to drop the modified Vending.apk into the /system/app folder (extract the apk from the zip installer file)
Can also confirm the blue neon/black market works well - and looks awesome! (A101, Uruk 0.7)
Got the modded market here:
http://forum.xda-developers.com/showthread.php?t=813946
Click to expand...
Click to collapse

i shrinked your originally 9MB framework-res.apk by simply making all included archos-backgrounds unicolor (mostly about 250k -> 4k).
and making 2 times default wallpaper unicolor. (blue)
now its 6MB. i dont get why archos did this black pattern backgrounds anyway.

p0rk burn I'v been trying to mod the framework-res.apk myself. but just out of curiosity what tools do you use and how do do the modifications.

i shrinked your originally 9MB framework-res.apk by simply making all included archos-backgrounds unicolor (mostly about 250k -> 4k).
and making 2 times default wallpaper unicolor. (blue)
now its 6MB. i dont get why archos did this black pattern backgrounds anyway.
Click to expand...
Click to collapse
would you be able to upload those modified wallpapers? wouldn't mind reducing the size of my own apk, seems a shame to duplicate your work!

fisha21 said:
would you be able to upload those modified wallpapers? wouldn't mind reducing the size of my own apk, seems a shame to duplicate your work!
Click to expand...
Click to collapse
im sorry if it was missleading but i altered p0rk burn's framwork-res.
anyway i mailed you the download link, should be useful for you mod too.

woti23 said:
im sorry if it was missleading but i altered p0rk burn's framwork-res.
anyway i mailed you the download link, should be useful for you mod too.
Click to expand...
Click to collapse
no, not misleading - I understood! Just got so many other pngs to edit, thought I'd benefit from your efforts on reducing the wallpaper file size.
Your files are already sitting in my framework version! Thanks

[MOD] Custom Boot Screen

Hi guys,
I picked up an I9100 SGS II the other day and decided to extend my development of the SGS boot screen MOD to it and was able to port it the same day as not much as changed in the way the param.lfs operates. I know this works just fine on the EURO I9100 SGS II in which the param.lfs calls for logo.jpg but if it fails, you can always re-flash a stock param.lfs to restore the boot screen which I have also included. I have written this for (I897, I9000, T959, T959V and now I9100). Per XDA's rules, I'll just attach the RAR package as an upload at the bottom of this post.
If you appreciate my work, just tap THANKS or DONATE me a drink or two if you are feeling generous. Here is the read me in case you don't want to open it with an additional text editor:
Code:
Brought to you by MOBILETECHVIDEOS.COM and CONNEXION2005 of XDA-Developers.COM
If the instructions below don't make sense to you,
JUST DON'T DO IT!
To change logo again, repeat the whole process!
=========================================================
| Instructions |
| ------------ |
| 1. Open Odin |
| 2. Boot Phone into Download Mode |
| 3. In Odin PDA select "SGS2_custom_param_lfs.tar" |
| 4. Click Start |
| 5. Boot Phone Normally and reconnect USB (dont mount) |
| You will have a logo draw fail! DONT WORRY! |
| 6. Rename the Picture you want to use to " logo.jpg " |
| 7. Run "MobileTV_SGS2_BootScreen.bat" from PC, follow |
| instructions. Keep phone screen ON, allow SU request. |
| 8. Reboot and Enjoy! |
=========================================================
NOTE about custom images!
480 x 800 and UNDER 100 kB
REMEMBER, THIS SCRIPT INSTALLS THE LATEST BUSYBOX INSTALLER, THIS MEANS IF YOU DIDN'T HAVE BUSYBOX INSTALLED, YOU MUST OPEN THAT INSTALLER AND ACTUALLY INSTALL BUSYBOX. IT INSTALLS AN APK TO USE TO INSTALL BUSYBOX, IT DOES NOT ACTUALLY INSTALL BUSYBOX ITSELF DURING THE SCRIPT.
ONLY USE THE LATEST BUSYBOX BY STERICSON TO ENSURE THIS WORKS BEST. IF YOU DON'T WANT TO USE THE SCRIPT FOR THE LATEST VERSION, BE SURE TO DOWNLOAD THE LATEST FREE INSTALLER OR DONATE VERSION IN THE MARKET BY STERICSON.
If the script doesn't work for you, it should if you have ADB installed, a rooted device plus the latest BusyBox (no offense but it's user error otherwise) just use root explorer to paste your logo.jpg in /mnt/.lfs AFTER running the custom param file via ODIN.

good job there mate !

does i9100 replacement logo.jpg also need to be less then 20kb?
also any other way to get out of soft crash except a jig(I dont have one)
and last request can you please also attach the original sgs2 boot screen plz?
thnx in advance..great work u r doing here bro..

THANKs
I followed all the steps , but without sucsess
I'm in Villain rom ... does it work with me ?

abumhmmd1 said:
THANKs
I followed all the steps , but without sucsess
I'm in Villain rom ... does it work with me ?
Click to expand...
Click to collapse
Does the script complete? Be sure logo.jpg is spelled in all lower case and make sure you don't accidentally have it named to logo.jpg.jpg

sumeshd said:
does i9100 replacement logo.jpg also need to be less then 20kb?
also any other way to get out of soft crash except a jig(I dont have one)
and last request can you please also attach the original sgs2 boot screen plz?
thnx in advance..great work u r doing here bro..
Click to expand...
Click to collapse
I've tested with files above 100k but recommend 100k or less. I'm not sure if the SGS II has the same issues with download mode in soft brick scenarios which require a jig. It doesn't hurt to have one just in case. To get the original screen back, simply flash the param.lfs from a regular i9100 ODIN package for your phone...

Works well here, I've now got a starfield picture as my bootscreen.
Nice one. No issues at all other than the script complaining about the fact that busybox was already installed.
If the .jpg is corrupt or too big etc. will the boot fail, or will I just get the little green "logo.jpg load failed" message that I saw during the initial boot?
Cheers!

Ok had time to create the actual SGS II video and added it to the OP...

Hi Josh....like your presentation style on your vids (though I'm glad there's a rewind facilty on vids to replay what I've missed that you've just said...very rapid fire, but get most of what you're saying, lol)
Before I go'n flash a new boot animation ( I was always changing it on my last Desire...) Is there a way (or a need) to back up the existing Sammy one, or will it get re-written when flashing back to the custom ROM/FW should I need to send my phone back for warranty purposes?? (BTW....what's the latest with the 'hidden' binary counter that the jig isn't supposed to reset??...any more been discovered about it?)
I made a small donation for ya too btw....(1UE79898RF509935C) good work, and thanks for all your help for us 'numpties' who rely on you clever dudes
Cheers...

Works great thanks

Thanks a lot, worked like charm!

I took a starfield picture I found somewhere and stuck the swirly S with the "Galaxy II" text on it so it looks semi-official, although the quality isn't as high as the real thing would be
I like it though, so here you are.
Looks like being in the "Yellow triangle" state over-rides the custom picture as I mis-flashed a zimage and it went away, flashed back to original & then CWM and all is well again.
{
"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"
}

Worked for me - thanks.
I put my name, email address and home phone number on the screen. That way if it gets stolen it's fixed on the screen at startup.
As knightnz said, yellow triangle will override your image but it comes back if you get rid of the yellow triangle (i.e. proper kernel or samsung jig)

Stock param.lfs to flash through Odin
Worked for me,,thanks!
I created my own bootscreen with a Metallica logo and some text,, haha
Anyway, I've attached a stock param.lfs file(a tar file that is) to flash through Odin in case you want to return to the stock bootscreen...I've tested it and it works.
I thought, I'll share it with you guys to save you some time...
Grtz Dhanesh

How about getting Skyraider boot animation working on SGS-2?
Hi Josh, really appreciate the work you are doing there, making learn this all so easily with the help of all those videos and written instructions. I have a further question: -
Is it possible to get Skyraider boot animation work on my SGS-2 instead of stock boot animation "S"?? And also if 'Yes', then is there anyway to save the stock boot animation just in case if want to revert back to it?
Thanks
Update:
Got it done already, thanks to BMWpokerAce. Anybody interested go to:
http://forum.xda-developers.com/showthread.php?t=1150281

Hi, Thank you for the awesome video!
Even though the instructions are very clear, i still seem to have some trouble replace my bootscreen.
After running the SGS2_Custom_param_lfs.tar file in Odin (w/o any errors) i dont get the "logo.jpg draw failed" message that appears in your video, and i still got the same bootscreen as before.
Iam using [CF-Root v4.0] KE2/7/8, KF1/2/3/4 - su+bb+CWM4 with stock rom.
Thank you in advance!

RejjvarN said:
Hi, Thank you for the awesome video!
Even though the instructions are very clear, i still seem to have some trouble replace my bootscreen.
After running the SGS2_Custom_param_lfs.tar file in Odin (w/o any errors) i dont get the "logo.jpg draw failed" message that appears in your video, and i still got the same bootscreen as before.
Iam using [CF-Root v4.0] KE2/7/8, KF1/2/3/4 - su+bb+CWM4 with stock rom.
Thank you in advance!
Click to expand...
Click to collapse
Me too...
I experience the same problem...
May you've got a solution for this?
I'm running the Lite'nin Rom 1.5... (simply flashed with ODIN, no changes made... (kernel, busybox, ...))
Thanks a lot... =)

To both of you guys ^, I'd bet you have a variant of the SGS II that doesn't call the logo.jpg file and instead is calling some other file in the param.lfs. There are several logo files in that directory so my thoughts are that your variant calls for a different picture other than just logo.jpg. Especially if the script does not error out.

Thanks, you were right... =)
In my case the file is called logo_tel.jpg...
Now I'd need a SGS2_custom_param_lfs.tar, which "deletes" this file... (Or did you rename it?)
Is it possible for you to create one? Or could you explain how to do it myself? (I would love to know more about it... )
Thanks for your answer... =)
EDIT:
I just built a JIG for my galaxy s2, cause I thought I'd may need it some time... And when I tried if it works, I realized, that not only the phone boots into download-mode and resets the Custom Binary counter, but it also sets the source for the boot-logo to default... (in my case from logo_tel.jpg to logo.jpg)
So now I was able to change the bootlogo with your SGS2_custom_param_lfs.tar!
Maybe it also works for others... try it out... there's nothing to loose...

Havent had time to check if its the same scenario for me. But i´ll guess if your right, it prolly easier to create/buy a JIG then get a custom .tar file.. Thank you for sharing the information!
LichtiMC said:
Thanks, you were right... =)
In my case the file is called logo_tel.jpg...
Now I'd need a SGS2_custom_param_lfs.tar, which "deletes" this file... (Or did you rename it?)
Is it possible for you to create one? Or could you explain how to do it myself? (I would love to know more about it... )
Thanks for your answer... =)
EDIT:
I just built a JIG for my galaxy s2, cause I thought I'd may need it some time... And when I tried if it works, I realized, that not only the phone boots into download-mode and resets the Custom Binary counter, but it also sets the source for the boot-logo to default... (in my case from logo_tel.jpg to logo.jpg)
So now I was able to change the bootlogo with your SGS2_custom_param_lfs.tar!
Maybe it also works for others... try it out... there's nothing to loose...
Click to expand...
Click to collapse

Kingrow K1 eInk (8.1, MediaTek Helio P23 (MT6763))

Just learned about GIS. Still using a Galaxy S4 w/Lineage, but am a huge fan of eink everything and impulse pre-ordered this new black and white phone from new and unknown Chinese vendor. Alleged to ship in August.
Assumed I was just going to use it off line as an ebook reader (to replace my kobo mini), but GIS has given me hope that there is a chance for a (relatively) safe/unbloated life for this device beyond that.
I’m sure there will be some eink optimization in the official ROM, but am less concerned about that than I am mysterious Chinese software.
Would love to hear anyone’s thoughts. I am more than happy to contribute to the cost of a Getting a test device in capable hands if necessary.
As a privacy enthusiast would also appreciate thoughts on hardware security on random Chinese phone as well. This is the first time I’ve ever gone out on such a limb.
Kingrow K1 Specs
5.17-inch E Ink Carta display (1280 x 720 with 283 ppi).
Frontlight.
2.0GHz MediaTek Helio P23 (MT6763) octa-core processor.
16GB of storage space.
2GB of RAM.
MicroSD card slot with support up to 64GB.
3100 mAh battery.
8MP rear camera with LED flash and auto-focus.
Android 8.1 Oreo operating system.
Dual SIM.
USB-C port.
Dual speakers.
138 x 72 x 8.5mm.
Thanks in advance.

Just realized one particular hardware issue may be the front light (since screen is not backlit like an LCD) and the controls may not be identical to backlight controls. I hope it treats the screen brightness identically and that it won’t be an issue.

Bump. For this type of preocessor I’ve only seen one example of getting stock android running relatively easily, anybody have any insight on what I can expect in the attempt?

I waited with backing this project on Indiegogo, because of the lack of GMS. I hope that could be fixed through another rom. But I doubt there will be a big developer crowd for this device. Nevertheless its nice to see it here on XDA. Followed!

Hi, I just got my Kingrow K1 in the mail today. I've always wanted an e-ink smartphone for longer battery life + less distraction, so I'm pretty excited about this. Unfortunately, the preinstalled software looks rather clunky and, as you mention, it might include random Chinese bloat/spyware. I'm hoping somebody can root this thing and we can get a developer scene going for it.
Some of the work done for Barnes & Noble Nook devices might be relevant, as those are also e-ink devices running Android.
For future reference, here's a list of everything installed on the stock ROM. I'm still trying to sort out what it all is, I think all the MTK* stuff are alternatives to missing Google packages provided by MediaTek.
$ pm list packages -f
package:/system/priv-app/FMRadio/FMRadio.apk=com.android.fmradio
package:/system/app/Gba/Gba.apk=com.mediatek.gba
package:/system/priv-app/ImsService/ImsService.apk=com.mediatek.ims
package:/system/plugin/PrivacyProtectionLock/PrivacyProtectionLock.apk=com.mediatek.ppl
package:/system/priv-app/CtsShimPrivPrebuilt/CtsShimPrivPrebuilt.apk=com.android.cts.priv.ctsshim
package:/system/app/Uicc2Terminal/Uicc2Terminal.apk=org.simalliance.openmobileapi.uicc2terminal
package:/system/priv-app/MtkTelephonyProvider/MtkTelephonyProvider.apk=com.android.providers.telephony
package:/system/app/Camera/Camera.apk=com.mediatek.camera
package:/system/priv-app/MtkCalendarProvider/MtkCalendarProvider.apk=com.android.providers.calendar
package:/system/priv-app/MtkMediaProvider/MtkMediaProvider.apk=com.android.providers.media
package:/vendor/app/LPPeService/LPPeService.apk=com.mediatek.location.lppe.main
package:/system/priv-app/WallpaperCropper/WallpaperCropper.apk=com.android.wallpapercropper
package:/vendor/app/SchedulePowerOnOff/SchedulePowerOnOff.apk=com.mediatek.schpwronoff
package:/system/app/Protips/Protips.apk=com.android.protips
package:/system/app/SmartcardService/SmartcardService.apk=org.simalliance.openmobileapi.service
package:/system/priv-app/MtkDocumentsUI/MtkDocumentsUI.apk=com.android.documentsui
package:/vendor/overlay/framework-res__auto_generated_rro.apk=android.auto_generated_rro__
package:/system/priv-app/ExternalStorageProvider/ExternalStorageProvider.apk=com.android.externalstorage
package:/system/app/YGPS/YGPS.apk=com.mediatek.ygps
package:/system/priv-app/MtkSimProcessor/MtkSimProcessor.apk=com.mediatek.simprocessor
package:/system/app/HTMLViewer/HTMLViewer.apk=com.android.htmlviewer
package:/system/app/CompanionDeviceManager/CompanionDeviceManager.apk=com.android.companiondevicemanager
package:/system/app/QuickSearchBox/QuickSearchBox.apk=com.android.quicksearchbox
package:/system/priv-app/MtkMmsService/MtkMmsService.apk=com.android.mms.service
package:/system/priv-app/MtkDownloadProvider/MtkDownloadProvider.apk=com.android.providers.downloads
package:/system/app/EngineerMode/EngineerMode.apk=com.mediatek.engineermode
package:/system/priv-app/xxLauncher/xxLauncher.apk=com.android.xx.launcherink
package:/system/app/Omacp/Omacp.apk=com.mediatek.omacp
package:/system/app/MtkBrowser/MtkBrowser.apk=com.android.browser
package:/system/app/OP01SoundRecorder/OP01SoundRecorder.apk=com.android.soundrecorder
package:/system/priv-app/WfoService/WfoService.apk=com.mediatek.wfo.impl
package:/system/priv-app/DefaultContainerService/DefaultContainerService.apk=com.android.defcontainer
package:/system/app/RedStoneOta/RedStoneOta.apk=com.redstone.ota.ui
package:/system/app/MtkDownloadProviderUi/MtkDownloadProviderUi.apk=com.android.providers.downloads.ui
package:/system/app/PacProcessor/PacProcessor.apk=com.android.pacprocessor
package:/system/app/CertInstaller/CertInstaller.apk=com.android.certinstaller
package:/system/priv-app/MtkCarrierConfig/MtkCarrierConfig.apk=com.android.carrierconfig
package:/system/framework/framework-res.apk=android
package:/system/priv-app/MtkContacts/MtkContacts.apk=com.android.contacts
package:/vendor/app/EmCamera/EmCamera.apk=com.mediatek.emcamera
package:/system/app/EasterEgg/EasterEgg.apk=com.android.egg
package:/system/priv-app/MtkMms/MtkMms.apk=com.android.mms
package:/system/priv-app/MtpDocumentsProvider/MtpDocumentsProvider.apk=com.android.mtp
package:/system/app/NfcNci/NfcNci.apk=com.android.nfc
package:/system/priv-app/Stk1/Stk1.apk=com.android.stk
package:/system/priv-app/BackupRestoreConfirmation/BackupRestoreConfirmation.apk=com.android.backupconfirm
package:/system/plugin/PermissionControl/PermissionControl.apk=com.mediatek.security
package:/system/app/BtTool/BtTool.apk=com.mediatek.bluetooth.dtt
package:/system/priv-app/Provision/Provision.apk=com.android.provision
package:/system/priv-app/StatementService/StatementService.apk=com.android.statementservice
package:/system/app/MDMLSample/MDMLSample.apk=com.mediatek.mdmlsample
package:/system/app/MtkCalendar/MtkCalendar.apk=com.android.calendar
package:/system/app/DrmProvider/DrmProvider.apk=com.mediatek.providers.drm
package:/vendor/overlay/SysuiDarkTheme/SysuiDarkThemeOverlay.apk=com.android.systemui.theme.dark
package:/system/priv-app/MtkSettingsProvider/MtkSettingsProvider.apk=com.android.providers.settings
package:/system/priv-app/SharedStorageBackup/SharedStorageBackup.apk=com.android.sharedstoragebackup
package:/system/app/PrintSpooler/PrintSpooler.apk=com.android.printspooler
package:/system/app/Uicc1Terminal/Uicc1Terminal.apk=org.simalliance.openmobileapi.uicc1terminal
package:/system/app/BasicDreams/BasicDreams.apk=com.android.dreams.basic
package:/system/app/webview/webview.apk=com.android.webview
package:/system/priv-app/InputDevices/InputDevices.apk=com.android.inputdevices
package:/system/app/BuiltInPrintService/BuiltInPrintService.apk=com.android.bips
package:/system/framework/mediatek-res/mediatek-res.apk=com.mediatek
package:/vendor/app/AutoDialer/AutoDialer.apk=com.example
package:/system/priv-app/DuraSpeed/DuraSpeed.apk=com.mediatek.duraspeed
package:/system/priv-app/MusicFX/MusicFX.apk=com.android.musicfx
package:/system/app/ExtShared/ExtShared.apk=android.ext.shared
package:/system/priv-app/OneTimeInitializer/OneTimeInitializer.apk=com.android.onetimeinitializer
package:/vendor/app/NlpService/NlpService.apk=com.mediatek.nlpservice
package:/system/priv-app/MtkTelecom/MtkTelecom.apk=com.android.server.telecom
package:/system/app/KeyChain/KeyChain.apk=com.android.keychain
package:/system/app/PrintRecommendationService/PrintRecommendationService.apk=com.android.printservice.recommendation
package:/system/priv-app/MtkDialer/MtkDialer.apk=com.android.dialer
package:/system/app/MtkGallery2/MtkGallery2.apk=com.android.gallery3d
package:/system/app/GoogleTTS/GoogleTTS.apk=com.google.android.tts
package:/system/priv-app/ExtServices/ExtServices.apk=android.ext.services
package:/system/priv-app/CallLogBackup/CallLogBackup.apk=com.android.calllogbackup
package:/system/priv-app/MtkPackageInstaller/MtkPackageInstaller.apk=com.android.packageinstaller
package:/system/priv-app/ProxyHandler/ProxyHandler.apk=com.android.proxyhandler
package:/system/app/MtkLatinIME/MtkLatinIME.apk=com.android.inputmethod.latin
package:/system/priv-app/ManagedProvisioning/ManagedProvisioning.apk=com.android.managedprovisioning
package:/system/app/CalendarImporter/CalendarImporter.apk=com.mediatek.calendarimporter
package:/vendor/app/MTKThermalManager/MTKThermalManager.apk=com.mediatek.thermalmanager
package:/system/priv-app/CallRecorderService/CallRecorderService.apk=com.mediatek.callrecorder
package:/system/app/MtkWebView/MtkWebView.apk=com.mediatek.webview
package:/system/app/WAPPushManager/WAPPushManager.apk=com.android.smspush
package:/vendor/app/SimRecoveryTestTool/SimRecoveryTestTool.apk=com.mtk.telephony
package:/system/priv-app/Baidu_Location/Baidu_Location.apk=com.baidu.map.location
package:/system/priv-app/StorageManager/StorageManager.apk=com.android.storagemanager
package:/system/app/OpenWnn/OpenWnn.apk=jp.co.omronsoft.openwnn
package:/system/app/BookmarkProvider/BookmarkProvider.apk=com.android.bookmarkprovider
package:/system/priv-app/MtkSettings/MtkSettings.apk=com.android.settings
package:/system/app/MDMConfig/MDMConfig.apk=com.mediatek.mdmconfig
package:/system/app/ExactCalculator/ExactCalculator.apk=com.android.calculator2
package:/vendor/app/LocationEM2/LocationEM2.apk=com.mediatek.lbs.em2.ui
package:/system/app/CtsShimPrebuilt/CtsShimPrebuilt.apk=com.android.cts.ctsshim
package:/system/priv-app/VpnDialogs/VpnDialogs.apk=com.android.vpndialogs
package:/system/app/MtkEmail/MtkEmail.apk=com.android.email
package:/vendor/app/MusicBspPlus/MusicBspPlus.apk=com.android.music
package:/system/priv-app/MtkTeleService/MtkTeleService.apk=com.android.phone
package:/system/priv-app/Shell/Shell.apk=com.android.shell
package:/system/app/WallpaperBackup/WallpaperBackup.apk=com.android.wallpaperbackup
package:/system/priv-app/BlockedNumberProvider/BlockedNumberProvider.apk=com.android.providers.blockednumber
package:/system/app/UserDictionaryProvider/UserDictionaryProvider.apk=com.android.providers.userdictionary
package:/system/priv-app/MtkEmergencyInfo/MtkEmergencyInfo.apk=com.android.emergency
package:/system/priv-app/FusedLocation/FusedLocation.apk=com.android.location.fused
package:/system/app/FactoryTest/FactoryTest.apk=com.xthink.factorytest
package:/system/app/MtkDeskClock/MtkDeskClock.apk=com.android.deskclock
package:/system/priv-app/MtkSystemUI/MtkSystemUI.apk=com.android.systemui
package:/system/app/Exchange2/Exchange2.apk=com.android.exchange
package:/system/app/BluetoothMidiService/BluetoothMidiService.apk=com.android.bluetoothmidiservice
package:/system/app/MtkNlp/MtkNlp.apk=com.mediatek.location.mtknlp
package:/system/app/FileManager/FileManager.apk=com.mediatek.filemanager
package:/system/app/MTKLogger/MTKLogger.apk=com.mediatek.mtklogger
package:/system/app/SensorHub/SensorHub.apk=com.mediatek.sensorhub.ui
package:/system/app/MtkBluetooth/MtkBluetooth.apk=com.android.bluetooth
package:/system/app/MtkWallpaperPicker/MtkWallpaperPicker.apk=com.android.wallpaperpicker
package:/system/priv-app/MtkContactsProvider/MtkContactsProvider.apk=com.android.providers.contacts
package:/system/app/CaptivePortalLogin/CaptivePortalLogin.apk=com.android.captiveportallogin
package:/system/plugin/DataProtection/DataProtection.apk=com.mediatek.dataprotection
package:/vendor/app/WapiCertManager/WapiCertManager.apk=com.wapi.wapicertmanager
package:/system/app/kindlefc/kindlefc.apk=com.amazon.kindle
Click to expand...
Click to collapse

I've managed to get the device into fastboot mode. I'd like to flash a custom recovery like TWRP, but I don't know which one is compatible with this device. Any suggestions?

Bunyip123 said:
I've managed to get the device into fastboot mode. I'd like to flash a custom recovery like TWRP, but I don't know which one is compatible with this device. Any suggestions?
Click to expand...
Click to collapse
do you happen to have the stock firmware with the boot.IMG. i want to look at it and see if its similar to my device. i have a umidigi one max and it has the same chipset and it looks like alot of the same apps

th3d3ck3r said:
do you happen to have the stock firmware with the boot.IMG.
Click to expand...
Click to collapse
No, I don't have the stock firmware. If you can point me to some instructions, I'm happy to try to extract a copy of it and post it here.

Kingrow K1 doesn't let me log in to google services
Hi,
I'm not a developer, sorry for my lack of knowledgle, however I'm desparate to find a sollution, maybe you can help me here.
I've bought the Kingrow K1 only to find there's no way of signing in to google accounts, contacts, callendar etc. $%^&*()!~
I hope it's just a question of installing and configuring the missing pieces.
Can you please help me out?
Tom

Maybe flashing Gapps like on AOSP? ?

You could try flashing a gapps package like https://opengapps.org/ but I don't know if it will work without root.

Bunyip123 said:
You could try flashing a gapps package but I don't know if it will work without root.
Click to expand...
Click to collapse
Without TWRP
We even have no stock firmware. I see it's a first step to acquire it.

sandworm88 said:
Without TWRP
We even have no stock firmware. I see it's a first step to acquire it.
Click to expand...
Click to collapse
is it of any help the url that get called when a k1 fails to find a new OTA firmware?
It's using a server called
fota.redstone.net.cn
on the port 6100
and it's asking for service/request

_jet said:
is it of any help the url that get called when a k1 fails to find a new OTA firmware?
It's using a server called
fota.redstone.net.cn
on the port 6100
and it's asking for service/request
Click to expand...
Click to collapse
...i'm just asking, i don't know anything about how to retrieve (and keep) a firmware copy

Any updates on this? someone in Kingrow K1 eReader/Phone User Group on FB claims they got root:
{
"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"
}

Hello, I've worked on a MT6763 device before. You may be in luck because MTK devices have built-in flash mode you can access. This would mean you can dump partitions provided you locate their offsets (if you can get hands on a scatter file, that would help a lot). The flash mode also allows you to bypass any locked bootloader (though, you don't seem to face such issue, but nice to know it's possible) restrictions. You may also be able to dd the blocks and create a stock firmware dump for backup. A good chance TWRP can be ported without kernel sources by using a very similar device's port as a base and dropping your current recovery image's kernel and fstab values in it.
I do not own this device myself, but I am interested in any findings regarding this topic. Good luck.
EDIT:
_jet said:
...i'm just asking, i don't know anything about how to retrieve (and keep) a firmware copy
Click to expand...
Click to collapse
Can you tell me how your /dev/block structure looks like, (use ls). If you navigate deep enough, you will see "by-name" folder, you can then dd the "boot" partition as a boot.img file.
EDIT2:
Actually, I suggest just dd'ing your system partition to your PC. You can also flash GSIs using fastboot. By dd'ing your system partition, you essentially make a fallback in case the image fails.

Cernodile said:
Hello, I've worked on a MT6763 device before. You may be in luck because MTK devices have built-in flash mode you can access. This would mean you can dump partitions provided you locate their offsets (if you can get hands on a scatter file, that would help a lot). The flash mode also allows you to bypass any locked bootloader (though, you don't seem to face such issue, but nice to know it's possible) restrictions. You may also be able to dd the blocks and create a stock firmware dump for backup. A good chance TWRP can be ported without kernel sources by using a very similar device's port as a base and dropping your current recovery image's kernel and fstab values in it.
I do not own this device myself, but I am interested in any findings regarding this topic. Good luck.
EDIT:
Can you tell me how your /dev/block structure looks like, (use ls). If you navigate deep enough, you will see "by-name" folder, you can then dd the "boot" partition as a boot.img file.
EDIT2:
Actually, I suggest just dd'ing your system partition to your PC. You can also flash GSIs using fastboot. By dd'ing your system partition, you essentially make a fallback in case the image fails.
Click to expand...
Click to collapse
Thanks for you answer @Cernodile. I'm the guy Ti He who posted in the FB group.
I'm currently trying to port a TWRP to our device. First I did a full read with Miracle Box, so in case something goes wrong I can restore my device. I used a TWRP from Cubot King Kong 3 because it has the same SoC and GPU. I unpacked my stock recovery and the Cubot recovery and replaced files like recovery.img-kernel
recovery.img-kernel_offset
ramdisk/prop.default
ramdisk/init files
ramdisk/ueventd.rc
ramdisk/ect/recovery.fstab
I flashed the repacked recovery through fastboot and booted into TWRP. I assume that TWRP would have been booted, because I can do adb devices and see my phone in recovery. But the display only shows some black lines, so there must be something wrong. Do you have any idea where to look at? See attached the log from /cache/recovery/.
Regards - Timo

helnorsksvartmetall said:
Thanks for you answer @Cernodile
I'm currently trying to port a TWRP to our device. First I did a full read with Miracle Box, so in case something goes wrong I can restore my device. I used a TWRP from Cubot King Kong 3 because it has the same SoC and GPU. I unpacked my stock recovery and the Cubot recovery and replaced files like recovery.img-kernel
recovery.img-kernel_offset
ramdisk/prop.default
ramdisk/init files
ramdisk/ueventd.rc
ramdisk/ect/recovery.fstab
I flashed to repacked recovery through fastboot and booted into TWRP. I assume that TWRP would have been booted, because I can do adb devices and see my phone in recovery. But the display only shows some black lines, so there must be something wrong. Do you have any idea where to look at? See attached to log from /cache/recovery/.
Regards - Timo
Click to expand...
Click to collapse
That seems already quite promising! It seems like your device is trying to render some TWRP elements, perhaps you have wrong resolution set as suggested by "framebuffer: 3 (344 x 725)". What would assist me here greatly would be .prop files from stock and your TWRP port such as default.prop.

I also attached the Scatter file from my device on my last post.
See below the prop files from stock and port (Cubot King Row 3).
(I also tried with port TWRP from Umidigi One Max but with the same result)

helnorsksvartmetall said:
I also attached the Scatter file from my device on my last post.
See below the prop files from stock and port (Cubot King Row 3).
(I also tried with port TWRP from Umidigi One May but with the same result)
Click to expand...
Click to collapse
First inconsistencies I see:
This is in your stock, but not port.
Code:
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
dalvik.vm.isa.arm64.variant=cortex-a53
dalvik.vm.isa.arm64.features=default
dalvik.vm.isa.arm.variant=cortex-a53
Although, I don't think that is the cause. I'd keep looking for a device that has e ink patches for TWRP, you can use that as base, rebuild the similar device's TWRP and then do same port method.

[MOD][OP5/5T] Android 10 Boot Logo and Animation

Bring the new Android 10 Boot Logo and Animation to your OnePlus 5 or 5T
How to install:
Download the ZIPs from this thread
Install bootanimation module through Magisk (SAR version supports system-as-root and Android 10 Dark Mode)
Flash logo into TWRP recovery
Done!
How to revert back to stock:
Download the rollback ZIP
Flash it into TWRP recovery
Done!
Or
Flash a Pie version of OxygenOS
I'm not responsable of any brick or data loss
Thanks to Dirk for the bootanimation!
Enjoy!

Added to the OnePlus 5 Index Thread here.

I tried to port the bootanimation from 7 pro, but I don't know how to crop it. If someone knows how to do it, I will appreciate your help

PierreVicquery02 said:
I tried to port the bootanimation from 7 pro, but I don't know how to crop it. If someone knows how to do it, I will appreciate your help
Click to expand...
Click to collapse
The frames will need resizing down rather than cropping. 1440p vs 1080p, so 33%. If you want to test how a single frame looks on the OP5 simply resize it, use an image editor to center it on a 1080x1920 canvas and view it on the phone. If you resized it 33% down it should look the same proportion as the original looks on the 7Pro.
Faststone Photo Resizer is a great free tool to do batch operations like resize and crop.
The other thing you will need to tackle is the desc.txt. It will need to be altered to reflect the new reolution of your images. My guide will tell you how.
If you zip one of the frames and the desc.txt, and upload it here, i'll take a look if you want? Make sure to quote or @ mention me otherwise i won't know you've responded.
BTW. porting an existing Boot Animation is a great way to learn to how they work and a great place to begin if you plan to make your own. The guides i've written should cover every question you might have but i'm happy to help if you run into trouble.

Dirk said:
The frames will need resizing down rather than cropping. 1440p vs 1080p, so 33%. If you want to test how a single frame looks on the OP5 simply resize it, use an image editor to center it on a 1080x1920 canvas and view it on the phone. If you resized it 33% down it should look the same proportion as the original looks on the 7Pro.
Faststone Photo Resizer is a great free tool to do batch operations like resize and crop.
The other thing you will need to tackle is the desc.txt. It will need to be altered to reflect the new reolution of your images. My guide will tell you how.
If you zip one of the frames and the desc.txt, and upload it here, i'll take a look if you want? Make sure to quote or @ mention me otherwise i won't know you've responded.
BTW. porting an existing Boot Animation is a great way to learn to how they work and a great place to begin if you plan to make your own. The guides i've written should cover every question you might have but i'm happy to help if you run into trouble.
Click to expand...
Click to collapse
I tried to crop, but with a PNG 24bit output the bootanimation doesn't show up and it goes from the boot logo to the lock screen

PierreVicquery02 said:
I tried to crop, but with a PNG 24bit output the bootanimation doesn't show up and it goes from the boot logo to the lock screen
Click to expand...
Click to collapse
There are a few things that can trip you up if they're not correct. (All are covered in my guides). Editing the desc.txt correctly is essential, so if you think the images are correct in name and format, focus on that. For example, you have to begin a new empty line before saving the file otherwise it doesn't work. So in Notepad++ the lines of text are numbered down the left side. It might look something like:
1) 1080 1920 40
2) c 1 0 part0 #121411
3) c 0 0 part1 #121411
4) c 1 0 part2 #121411
5)
So in this example the fifth line needs to exist and be empty. Save the desc.txt as 'All Types', as below:
{
"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"
}
Another thing that can easily trip you up is creating the zip archive. Use WinRar as described in my guide. (The screenshot tells you everything you need to know).
Don't forget that you need to set permissions on the bootanimation.zip correctly if you are installing it manually. I suggest creating a flashable zip for installation. You can reverse engineer one of mine.
If you have any more issues, upload a frame from the original along with the desc.txt.

PierreVicquery02 said:
I tried to port the bootanimation from 7 pro, but I don't know how to crop it. If someone knows how to do it, I will appreciate your help
Click to expand...
Click to collapse
I took a look at the Boot Animation from the 7Pro. (From HERE). It's the same stock OOS Boot Animation they've been using for years. I extracted the bootanimation.zip from OOS 9.0.8 for the OP5 and put it in a flashable zip. (See attached).

Dirk said:
I took a look at the Boot Animation from the 7Pro. (From HERE). It's the same stock OOS Boot Animation they've been using for years. I extracted the bootanimation.zip from OOS 9.0.8 for the OP5 and put it in a flashable zip. (See attached).
Click to expand...
Click to collapse
No, the logo dimension at the beginning is not the same

PierreVicquery02 said:
No, the logo dimension at the beginning is not the same
Click to expand...
Click to collapse
Here's how it looks:
Left is Stock OOS Boot Animation on the OP5
Middle is Stock OOS Boot Animation on the OP7 Pro
Right is adjusted OOS Boot Animation on the OP5*
*After adjustment the Logo is about the same proportion on both devices. To acheive this, begin with the OP5 Stock OOS bootanimation.zip. Resize all frames to 530x663. Edit desc.txt to:
530 663 60
p 1 0 part0
c 0 0 part1
c 0 0 part2
Repack bootanimation.zip. Put in flashable zip. (See Attached)
You may of course still want to play with size/placement yourself. Feel free to alter as you wish, (and if you'd rather it wasn't here at all i will remove it).

Dirk said:
Here's how it looks:
Left is Stock OOS Boot Animation on the OP5
Middle is Stock OOS Boot Animation on the OP7 Pro
Right is adjusted OOS Boot Animation on the OP5*
*After adjustment the Logo is about the same proportion on both devices. To acheive this, begin with the OP5 Stock OOS bootanimation.zip. Resize all frames to 530x663. Edit desc.txt to:
530 663 60
p 1 0 part0
c 0 0 part1
c 0 0 part2
Repack bootanimation.zip. Put in flashable zip. (See Attached)
You may of course still want to play with size/placement yourself. Feel free to alter as you wish, (and if you'd rather it wasn't here at all i will remove it).
Click to expand...
Click to collapse
Your work is almost perfect! THANK YOU! It's a little bit under the real logo, but it's better than the original! I put the animation in a systemless magisk module, thank you again!

PierreVicquery02 said:
Your work is almost perfect! THANK YOU! It's a little bit under the real logo, but it's better than the original! I put the animation in a systemless magisk module, thank you again!
Click to expand...
Click to collapse
I think it looks too high on the OP7. They're really under-utilising all that vertical space with the Stock Animation.
If you do want to move the animation up a bit just add some Black canvas to the bottom of each frame. That would make each frame taller, so you would need to edit the desc.txt to match the final resolution of the frames.
Left is adjusted Animation as already posted.
Middle is the result if 100px of Black canvas added to Bottom of frames.
Right is the result if 200px of Black canvas added to Bottom of frames.
You can exptrapolate from there.
Edit: Remember, whatever you decide to do with the height placement, the proportion is only for 1080p devices. For larger resolutions you would need to create another module and resize the frames again to suit. (For 1440p devices you could just use the original 7Pro frames without resizing)

Perhaps we can call upon @strongst to wield his mod power to tidy up the thread for the OP? I'm sure Pierre would like to have a nice clean first page to post his work in and for further discussion of it. Everything from post # 3 down serves no more purpose now and could be removed. :good:

Dirk said:
Perhaps we can call upon @strongst to wield his mod power to tidy up the thread for the OP? I'm sure Pierre would like to have a nice clean first page to post his work in and for further discussion of it. Everything from post # 3 down serves no more purpose now and could be removed. :good:
Click to expand...
Click to collapse
On the contrary, I think those posts are very useful and serve as good reference points for someone wanting to do this on their own and wanting to learn. In my opinion, they definitely shouldn't be removed.

Dirk said:
Perhaps we can call upon @strongst to wield his mod power to tidy up the thread for the OP? I'm sure Pierre would like to have a nice clean first page to post his work in and for further discussion of it. Everything from post # 3 down serves no more purpose now and could be removed. :good:
Click to expand...
Click to collapse
Absolutely not! Your posts are very very very helpful to understand the structure of a bootanimation, and can be useful to some people. Please don't delete them

The team is always ready to clean a thread from whatever the OP deems to be off-topic. Just a brief report is needed. But it requires the OP to "complain" who can also provide guidance regarding off-topic in his OP.
However, everybody is requested to immediately report any post that violates the XDA Forum Rules. Please never reply to such a post.

@PierreVicquery02
dude send me .png file original 1080×1920 boot logo
request

jahidinbedod said:
@PierreVicquery02
dude send me .png file original 1080×1920 boot logo
request
Click to expand...
Click to collapse
You can download it from OP, click on the image and then download original

PierreVicquery02 said:
You can download it from OP, click on the image and then download original
Click to expand...
Click to collapse
it's you make png on logo.bin?
ok thanks dude

jahidinbedod said:
it's you make png on logo.bin?
Click to expand...
Click to collapse
PNGs in my mod are original from OnePlus, not made by me

@PierreVicquery02
First look at the Pixel 4 Boot Logo/Animation in this video: (4:00)
https://www.youtube.com/watch?v=ahVY2DJxCN8
Logo may be the same as in the Q Beta releases, (idk), but the Animation is new i think. There's something i haven't seen before just before setup begins. (Either the end of the Animation, or beginning of setup). What do you think?