Database Info

[DISCUSSION] rishabh.raj37's Guide on How To Port Different ROMS to Your Device

I tried to port a couple of ROMs from GSII and from Nexus S to our device using the following thread
But I'm always getting a status 7 error while flashing it.
This error is related to the updater script and I tried few changes here and there but without success.
Used Adam's CM10 as base and in the updater script the following lines seemed extra from the others ROMs' updater scripts.
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
set_perm(0, 0, 0644, "/tmp/backuptool.functions");
run_program("/tmp/backuptool.sh", "backup");
tried with and without these lines and still got status 7 error.
The original thread is filled with questions for their own devices and hardly any useful answer from the author.
I'm guessing many of you would have tried this guide before and so wanted to discuss here within ourselves.
I could have PMed our great devs here, but thy are all busy in "actual dev" work and so do not want to disturb them.
They might post here when they have time.
So guys, please give suggestions and your hiccups when you tried this method. Let us try to "port" some ROMs

Take a look to the recovery log

Just replace the update script from CM 10 and try it should work...

Grarak said:
Take a look to the recovery log
Click to expand...
Click to collapse
umm.. i should have thought this. thanks Garak.
mj.vikram said:
Just replace the update script from CM 10 and try it should work...
Click to expand...
Click to collapse
ok, let me try the original update script from our cm10 build.
as soon as i get the mobile back from my dad.

All the Best Buddy :good:, Waiting for some Good ROM from you ....

I do not have my Galaxy R with me and so am trying this method on GNex for now to see if im able to boot the ported ROM.
I left the updater-script untouched and the CWM flash went through without the status 7 error.
but gets stuck after boot animation forever and never moves ahead.
In what way I should go about troubleshooting this issue, I mean what kind of log would help for this "stuck in boot anim issue"

sarun_biotech said:
I do not have my Galaxy R with me and so am trying this method on GNex for now to see if im able to boot the ported ROM.
I left the updater-script untouched and the CWM flash went through without the status 7 error.
but gets stuck after boot animation forever and never moves ahead.
In what way I should go about troubleshooting this issue, I mean what kind of log would help for this "stuck in boot anim issue"
Click to expand...
Click to collapse
Copy the libandroid_runtime.so, libandroid_servers.so and libmedia_jni.so from Ported ROM to Base ROM and see if solves the issue. Try taking a adb logcat to check what's causing the issue.

selva.simple said:
Copy the libandroid_runtime.so, libandroid_servers.so and libmedia_jni.so from Ported ROM to Base ROM and see if solves the issue. Try taking a adb logcat to check what's causing the issue.
Click to expand...
Click to collapse
yes. did that too Selva. still stuck at boot anim.
actually, when should i take the logcat. coz, during the boot anim phase, i cant connect using adb from pc and if i restore to old rom, the logcat is only for the new one.
correct me if im worng.
EDIT : connected to usb in cwm mode and i was able to run adb commands. but after the flash and reboot, the command always says waiting for device. even during the boot anim time.

sarun_biotech said:
yes. did that too Selva. still stuck at boot anim.
actually, when should i take the logcat. coz, during the boot anim phase, i cant connect using adb from pc and if i restore to old rom, the logcat is only for the new one.
correct me if im worng.
Click to expand...
Click to collapse
Switch off ur mobile...connect to pc...give adb logcat..it will wait for the device to show up...now switch on ur pc..it will rec ur device and start preparing the logcat....now chk the log

You cannot normally get an adb connection from a device that hasn't even booted up, because from ICS (or HC), this method was changed. Fortunately, this can be bypassed quite easily. Unpack the boot.img with Adi_Pat's tools or dsixda's kitchen, find 'service adbd' in init.rc and remove the option 'disabled'. You will get adb connection.
Regarding replacing native binaries and libraries: Always know what you do! Native code not supportes by our CPU will just spam the logcat with SIGILL errors.
Sent from my CM10-powered GT-I9103

selva.simple said:
Switch off ur mobile...connect to pc...give adb logcat..it will wait for the device to show up...now switch on ur pc..it will rec ur device and start preparing the logcat....now chk the log
Click to expand...
Click to collapse
didnt work out bro.
Adam77Root said:
You cannot normally get an adb connection from a device that hasn't even booted up, because from ICS (or HC), this method was changed. Fortunately, this can be bypassed quite easily. Unpack the boot.img with Adi_Pat's tools or dsixda's kitchen, find 'service adbd' in init.rc and remove the option 'disabled'. You will get adb connection.
Regarding replacing native binaries and libraries: Always know what you do! Native code not supportes by our CPU will just spam the logcat with SIGILL errors.
Sent from my CM10-powered GT-I9103
Click to expand...
Click to collapse
thanks Adam. will try tmrw. and thanks for the heads up regdng libs. will study more.

ViperX install failed

ok well i followed the steps and looked into a tutorial and was able to download the zip file and save it to the computer and to the phone. when i flashed the boot.img it went fine. but when i went into fastboot and bootloader and went into recovery to install the file it did not work. i was able to find the file in recovery and do the steps to install but it would get stuck on the identification of the device and i found a thread here saying to delete the first line that makes it go thorough this process. So i went again and it did not go through this process but now it only goes through the first batch of column of code and it goes to wipe the memory and then it just stops right after it prints "Writting Data" and one of the two "ext4 EEMC" lines.After that the installation ends no more code is run and finish button appears and that is all that happens and once i restart it it goes back to how it was? Anyone have any idea? I have printed the first part of the code of the "writing data" part and following code after that maybe there is something there that is preventing it from going any further? Thanks
##########################Installation##########################
show_progress(0.07, 9);
ui_print("@>>> Writing Data");
mount("ext4", "EMMC", "/dev/block/mmcblk0p15", "/data");
package_extract_dir("data", "/data");
show_progress(0.7,1380);
format("ext4", "EMMC", "/dev/block/mmcblk0p12");
ui_print("@>>> Writing System");
mount("ext4", "EMMC", "/dev/block/mmcblk0p12", "/system");
package_extract_dir("system", "/system");
set_progress(0.9);
##############################AROMA#############################
##############################Mods##############################
if
file_getprop("/tmp/aroma-data/customize.prop","item.1.1") == "1"
then
ui_print("@>>> Flashing Exchange Mod");
package_extract_dir("additions/exchange", "/system");
endif;
if
file_getprop("/tmp/aroma-data/customize.prop","item.2.1") == "1"
then
ui_print("@>>> Flashing Viper Theme");
package_extract_dir("additions/theme", "/system");
package_extract_file("additions/theme/theme.sh", "/tmp/theme.sh");
set_perm(0, 0, 0777, "/tmp/theme.sh");
run_program("/tmp/theme.sh");
delete("/system/theme.sh");
endif;
if
file_getprop("/tmp/aroma-data/customize.prop","item.3.1") == "1"
then
ui_print(">>> Removing HTC Sense");
delete("/system/app/Htc3DRichNotesWidget.apk");
delete("/system/app/HtcAutoRotateWidget.apk");
delete("/system/app/HtcBackgroundDataWidget.apk");
delete("/system/app/HtcCalendarWidgets.apk");
delete("/system/app/HtcClockWidget.apk");
delete("/system/app/HtcContactWidgets.apk");
delete("/system/app/HtcDataRoamingWidget.apk");
delete("/system/app/HtcDataStripWidget.apk");
delete("/system/app/HtcFMRadioWidget.apk");
delete("/system/app/HtcFriendStreamWidget_3D.apk");
delete("/system/app/HtcMailWidgets.apk");
delete("/system/app/HtcMsgWidgets.apk");
delete("/system/app/HtcPhotoWidget.apk");
delete("/system/app/HtcPowerStripWidget.apk");
delete("/system/app/HtcProfilesWidget.apk");
delete("/system/app/HtcScreenBrightnessWidget.apk");
delete("/system/app/HtcScreenTimeoutWidget.apk");
delete("/system/app/HtcSettingWidgets.apk");
delete("/system/app/HtcStoreWidget.apk");
delete("/system/app/HtcSyncWidget.apk");
delete("/system/app/HtcTrendsWidget_3D.apk");
delete("/system/app/HtcTwitterWidget_3D.apk");
delete("/system/app/HTC_Widget_Locations.apk");
delete("/system/app/HTC_Widget_Navigate.apk");
delete("/system/app/HTC_Widget_Trip.apk");
delete("/system/app/HTC_Widget_Watch_3D.apk");
delete("/system/app/MyTaskWidget.apk");
delete("/system/app/StockWidget.apk");
delete("/system/app/WeatherWidget.apk");
delete("/system/app/Rosie.apk");
endif;
if
file_getprop("/tmp/aroma-data/launcher.prop","selected") == "1"
then
ui_print(">>> Adding Nova Launcher");
package_extract_file("additions/desense/Nova.apk", "/system/app/Nova.apk");
endif;
if
file_getprop("/tmp/aroma-data/launcher.prop","selected") == "2"
then
ui_print(">>> Adding Apex Launcher");
package_extract_file("additions/desense/Apex.apk", "/system/app/Apex.apk");
endif;
##########################User Removal##########################
if
file_getprop("/tmp/aroma-data/remove.prop","item.1.1") == "1"
then
ui_print(">>> Removing Adobe Reader");
delete("/data/app/com.adobe.reader-1.apk");
endif;
if
file_getprop("/tmp/aroma-data/remove.prop","item.1.2") == "1"
then
ui_print(">>> Removing Adobe Flash Player");
delete("/data/app/com.adobe.flashplayer-1.apk");
endif;
if
file_getpro

What device do you have? Are you trying to install ViperX or ViperXL?
Sent from my One XL using XDA Premium

timmaaa said:
What device do you have? Are you trying to install ViperX or ViperXL?
Sent from my One XL using XDA Premium
Click to expand...
Click to collapse
sorry i have the HTC One X with AT&T
im trying to install ViperX_2.6.0

jose619 said:
sorry i have the HTC One X with AT&T
im trying to install ViperX_2.6.0
Click to expand...
Click to collapse
Wrong Rom homie... The one you specified is for a different device. Take caution next time, as you could have potentionally turned your phone into a paperweight
Sent from my HTC One X using Tapatalk 2

InflatedTitan said:
Wrong Rom homie... The one you specified is for a different device. Take caution next time, as you could have potentionally turned your phone into a paperweight
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Damn. Thanks. By any chance do you know which one is the correct ViperX Rom?

This one:
http://forum.xda-developers.com/showthread.php?t=1868236
Sent from my One XL using XDA Premium

:\

mirGantrophy said:
:\
Click to expand...
Click to collapse
Lol. Yep.
Sent from my One XL using XDA Premium

A little research goes a long way.
AT&T HTC One X
Android 4.1.1
ViperXL 3.2.3

Do yourself a favor, and stick the the "AT&T" specific forum section: http://forum.xda-developers.com/forumdisplay.php?f=1538
The section titled simply "HTC One X" is for the quad core Tegra3 version (which is completely different hardware from the AT&T is dual core S4 version).
Also, you can use my Index, which is specific to the dual core version: http://forum.xda-developers.com/showthread.php?t=1671237

[GUIDE][FIX][AUTOMATION] Barclay's Mobile Banking Root Fix

DO NOT USE THIS TUTORIAL WITHOUT MY PERMISSION, SITES HAVE COPIED THIS AND NOT GIVEN CREDIT TO ME OR LINKED THIS POST.
Hello well firstly i would like to say thanks to many people in this thread here http://forum.xda-developers.com/showthread.php?t=1823649
So be sure to thank the people who deserve it.
CURRENT METHODS PATCHED DUE TO BARCLAYS FORCING LATEST VERSION.
Click the "show" button below to see old methods that no longer work.
There are 3 Methods to getting this to work. The first method is extremely simple and automated should work for everyone but untested, The second method should work for everyone (hopefully) but is harder and more time consuming. The third method will only work for people who previous had the app working.
Method 1 (Xposed) (Credit to @HiddenRambler) NEW
http://forum.xda-developers.com/showpost.php?p=49296437&postcount=8
Method 2 (Semi-Automatic)
This will automatically patch the build.prop and install 1.3.3 barclays (make sure to not have barclays mobile banking installed before). Please show consideration by clicking thanks as this automated method took a little time as i was rusty on edify syntax.
1. Download and flash this zip file in CWM or TWRP recovery (cyanlabs.co.uk/Automated Barclays Root Fix 1.0.zip).
See source of above zip file.
Code:
ui_print("*********************");
ui_print("Barclays Mobile Banking 1.3.3 Automated Fix");
ui_print("Created By Fma965 @ XDA-Developers");
ui_print("*********************");
ui_print("- Mounting /system, /data and rootfs");
run_program("/sbin/busybox", "mount", "/system");
run_program("/sbin/busybox", "mount", "/data");
run_program("/sbin/busybox", "mount", "-o", "rw,remount", "/system", "/system");
run_program("/sbin/busybox", "mount", "-o", "rw,remount", "/", "/");
ui_print("- Removing old files");
delete("/system/bin/su");
delete("/system/xbin/su");
delete("/system/bin/.ext/.su");
delete("/system/app/Superuser.apk");
delete("/system/app/Superuser.odex");
delete("/system/app/SuperUser.apk");
delete("/system/app/SuperUser.odex");
delete("/system/app/superuser.apk");
delete("/system/app/superuser.odex");
delete("/system/app/Supersu.apk");
delete("/system/app/Supersu.odex");
delete("/system/app/SuperSU.apk");
delete("/system/app/SuperSU.odex");
delete("/system/app/supersu.apk");
delete("/system/app/supersu.odex");
run_program("/sbin/busybox", "rm", "/data/dalvik-cache/*com.noshufou.android.su*");
run_program("/sbin/busybox", "rm", "/data/dalvik-cache/*com.koushikdutta.superuser*");
run_program("/sbin/busybox", "rm", "/data/dalvik-cache/*Superuser.apk*");
run_program("/sbin/busybox", "rm", "/data/dalvik-cache/*SuperUser.apk*");
run_program("/sbin/busybox", "rm", "/data/dalvik-cache/*superuser.apk*");
run_program("/sbin/busybox", "rm", "/data/dalvik-cache/*eu.chainfire.supersu*");
run_program("/sbin/busybox", "rm", "/data/dalvik-cache/*Supersu.apk*");
run_program("/sbin/busybox", "rm", "/data/dalvik-cache/*SuperSU.apk*");
run_program("/sbin/busybox", "rm", "/data/dalvik-cache/*supersu.apk*");
ui_print("- Extracting files");
package_extract_dir("system", "/system");
package_extract_dir("data", "/data");
package_extract_file("buildprop.sh", "/tmp/buildprop.sh");
set_perm(0, 0, 0777, "/tmp/buildprop.sh");
ui_print("- Patching Build.prop");
run_program("/sbin/busybox", "sed", "-i", "s/ro.build.tags=test-keys/ro.build.tags=release-keys/g", "/system/build.prop");
ui_print("- Setting permissions");
set_perm(0, 0, 0777, "/system/bin/.ext");
set_perm(0, 0, 06755, "/system/bin/.ext/.su");
set_perm(0, 0, 06755, "/system/xbin/su");
set_perm(0, 0, 0644, "/system/build.prop");
set_perm(0, 0, 0644, "/data/app/SuperuserCWM.apk");
ui_print("- Unmounting /system and /data");
unmount("/system");
unmount("/data");
ui_print("- Done - Be Sure to click thanks on XDA!");
-----------------------------------------------------------
Method 3
1. Download Build Prop Editor, click "ro.build.tags" and change the "test-keys" to "release-keys" press "save"
2. Reboot to Recovery
3. Flash this file http://cyanlabs.co.uk/downloads/Other/Barclays_Root_Fix_v3.0.zip (if it doesn't work try this http://cyanlabs.co.uk/Barclays Root Fix v2.0.zip) using CWM or TWRP Recovery
4. Reboot
5. Download "Barclays Mobile Banking v1.3.3" (Thanks to gazza1988)
6. Go to Barclays in the Google Play store. Press the menu button and untick "Auto Update"
7. Setup mobile banking
*If you have 3 devices registered already you will need to contact Barclays to get your accounts reset.
DO NOT USE THIS TUTORIAL WITHOUT MY PERMISSION, SITES HAVE COPIED THIS AND NOT GIVEN CREDIT TO ME OR LINKED THIS POST.

fma965 said:
Hello well firstly i would like to say thanks to many people in this thread here http://forum.xda-developers.com/showthread.php?t=1823649
So be sure to thank the people who deserve it.
Right so now for the guide.
There are 2 Methods to getting this to work. The first method will work for everyone (hopefully), the second method will only work for people who previous had the app working.
Method 1
1. Download ES File Explorer
2. Enable root features of ES File Explorer
3. Edit /system/build.prop (mount as RW)
Remove these lines
Code:
ro.cm.version=
ro.modversion=
And change this line
Code:
ro.build.tags=test-keys
To
Code:
ro.build.tags=release-keys
4. Download "SuperSU" from PlayStore
5. Find "Full Unroot" in the settings. And do it.
5. Flash this file ( http://puu.sh/372bd.zip ) using CWM or TWRP Recovery
6. Reboot once file is flashed
7. Download "SuperSU" from PlayStore AGAIN!
8. Load SuperSu "update binary" (Do not move app to system)
9. Download "Barclays Mobile Banking v1.3.3" (Thanks to gazza1988)
10. Setup mobile banking (Do not update)
11. Congrats your done
Method 2
Click Here
Click to expand...
Click to collapse
RE method 1: I use ParanoidAndroid and so Superuser is built into the ROM. How would users like me make the app work?
Sent from ThePureHeart's I9300 Boss Edition

Doesn't paranoidandroid just use superuser.apk? if so all u need to do is follow the instructions above, "full unroot" will remove all existing superuser.apk's.

fma965 said:
Doesn't paranoidandroid just use superuser.apk? if so all u need to do is follow the instructions above, "full unroot" will remove all existing superuser.apk's.
Click to expand...
Click to collapse
Nope, it uses Koush's Superuser implementation. It's built into the ROM and doesn't come as a separate app.
I hope there is a way to get it working.
Sent from ThePureHeart's I9300 Boss Edition

ThePureHeart said:
Nope, it uses Koush's Superuser implementation. It's built into the ROM and doesn't come as a separate app.
I hope there is a way to get it working.
Sent from ThePureHeart's I9300 Boss Edition
Click to expand...
Click to collapse
from my research that seems like is just a alternative to superuser and still works as a app, Also have you tried ignoring those steps and just removing the mod and cm lines (if you have them) ?

Don't know if I would be comfortable using a custom banking app although it's very tempting!
Sent from my LT26i using xda premium

fma965 said:
from my research that seems like is just a alternative to superuser and still works as a app, Also have you tried ignoring those steps and just removing the mod and cm lines (if you have them) ?
Click to expand...
Click to collapse
Unfortunately that won't work since Barclays' apps check for root-level apps, superuser access, device id and all sorts.
I'm trying to get it working with XPrivacy, no luck as of yet. I'll keep trying and see what happens.
Sent from ThePureHeart's I9300 Boss Edition

Thanks
Enviado desde mi Xperia U usando Tapatalk 4 Beta

jleafe said:
Don't know if I would be comfortable using a custom banking app although it's very tempting!
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
Hi mate, I haven't customised the app. I wouldn't even know where to start to customise it.
All the updates previous to, and including, 1.3.3 you could get around the root check using various methods. So when the new update came out root users, including myself, updated but found that the methods don't work.
People were asking for the 1.3.3 version because that is the latest one that "works" for root users.
If you check my post history (more specifically threads started by me) you'll see I'm no Dev and very recently bought an s3. I've made numerous backups trying to find the perfect rom for me and in most of those backups was the 1.3.3 apk that people needed.
So I uploaded it to Dropbox and shared it.
I predict you knew most of that info and I don't mean to sound condescending (apologies if I am) just thought I'd try to alleviate any fears over the validity of the app I uploaded.
Sent from my GT-I9300 using xda premium

jleafe said:
Don't know if I would be comfortable using a custom banking app although it's very tempting!
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
Im a recognized contributor surely that means im trustworthy. (i am personally using the APK posted above and it works fine and doesn't do anything suspicious.
ThePureHeart said:
Unfortunately that won't work since Barclays' apps check for root-level apps, superuser access, device id and all sorts.
I'm trying to get it working with XPrivacy, no luck as of yet. I'll keep trying and see what happens.
Sent from ThePureHeart's I9300 Boss Edition
Click to expand...
Click to collapse
1.3.3 doesn't check for like anything except superuser.apk and certain build.prop lines. New versions do though
dore22 said:
Thanks
Enviado desde mi Xperia U usando Tapatalk 4 Beta
Click to expand...
Click to collapse
No problem don't forget to give credit to the people in the link at top
gazza1988 said:
Hi mate, I haven't customised the app. I wouldn't even know where to start to customise it.
All the updates previous to, and including, 1.3.3 you could get around the root check using various methods. So when the new update came out root users, including myself, updated but found that the methods don't work.
People were asking for the 1.3.3 version because that is the latest one that "works" for root users.
If you check my post history (more specifically threads started by me) you'll see I'm no Dev and very recently bought an s3. I've made numerous backups trying to find the perfect rom for me and in most of those backups was the 1.3.3 apk that people needed.
So I uploaded it to Dropbox and shared it.
I predict you knew most of that info and I don't mean to sound condescending (apologies if I am) just thought I'd try to alleviate any fears over the validity of the app I uploaded.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Yeah he seems fine, I will upload my own version when i find where i backed it up to , Just so it is from a RC but im 95% sure its fine, At the end of the day its up to the people to decide if they wanna "risk it".
Thanks gazza for uploading the file though
Also if you check permissions and monitor traffic you can see it doesn't do anything different from normal.

Also is it just me or is this root block by barclays pointless....
I mean you have already entered all your bank details in by the time it tells you have root and refuses to work... How stupid is that? if the phone really is "vulnerable" due to root then uh surely check before entering the details would be good.

fma965 said:
Also is it just me or is this root block by barclays pointless....
I mean you have already entered all your bank details in by the time it tells you have root and refuses to work... How stupid is that? if the phone really is "vulnerable" due to root then uh surely check before entering the details would be good.
Click to expand...
Click to collapse
... you're joking, right?
The only info you enter is your number, sort code/account number and your name. All of which - with the exception of your phone number - is public and not sensitive at all.
Sent from ThePureHeart's I9300 Boss Edition

ThePureHeart said:
... you're joking, right?
The only info you enter is your number, sort code/account number and your name. All of which - with the exception of your phone number - is public and not sensitive at all.
Sent from ThePureHeart's I9300 Boss Edition
Click to expand...
Click to collapse
yes n no, i know its public (sort off) but it still makes more sense to check root first so hackers dont get even that info.

fma965 said:
Im a recognized contributor surely that means im trustworthy. (i am personally using the APK posted above and it works fine and doesn't do anything suspicious.
Click to expand...
Click to collapse
Please don't take that personally and I thank your contributions. I was just saying, with banking apps you could potentially see the alarm bells rining? therefore simply take caution

jleafe said:
Please don't take that personally and I thank your contributions. I was just saying, with banking apps you could potentially see the alarm bells rining? therefore simply take caution
Click to expand...
Click to collapse
Yeah i know what you meant, Like i said if you don't feel confortable then don't do it. But i checked it out and from what i checked didn't see any suspicious ****, pretty sure the app wouldn't be easy to modify as if it was uh we wouldn't need to all the BS in OP

Added you a link to my post too, favour returned :thumbup:
As to these talking about security issues ideally 99.9 of people on Xda are good & the downloads "should" be trusted but like any downloads ether roms & apks there is always the chance of corruption? That's why "most" people only say download only from play store or xda.
If the security issue is a big deal do what I did & send barclays a email about why they blocked rooted users? I am still waiting for a reply from them, I also put the comment on there play store comment review LOL
sent from Tapatalk2 via my Supermodded S3 using UltimaRom v13 & running Boeffla v2.12 beta7 kernel

Method 1 worked on my i9505 running Foxhound 0.8. Got a RP029 error, so had to ring Barclays to get them to reset the devices on my account, just need my Pin Sentry to complete to process.
Many Thanks!

instig8 said:
Got a RP029 error
Click to expand...
Click to collapse
same

Method 1 working on Domination ROM 20130624. Thanks for this, I preferred having the ROM managing root but a working Barclays was worth the substitution for SuperSU. Two questions:
1. What did the flash file do?
2. Any version of Barclays Pingit working?
Sent from my GT-N7100 using xda premium

PingIT
I would also like to know if this work around also allows PingIT to work?

[Bootanimation] Me!Me!Me! - OnePlus v3.1 {SFW}

Meme dancing animation from the anime short Me!Me!Me!
If you've never seen it, it's a must watch, but probably for 18+.
The Bootanimation is from some of the more mild part of the short and I would consider SFW and... hmm, Ok.... for most ages. Wife/sig other may not care for it.
DOWNLOADS:
Flash w/ custom recovery - HERE
Or
Replace /system/media/bootanimation.zip - HERE
May be required to change permissions with a root exlporer: -rw-r--r--
CHANGES:
v2
- Fixed alignment issue
- Fixed hair from being cut off on sides(as if it was reaching edge of screen)
- Smoother animation
- Smaller OnePlus symbol and color change
- Re-rendered each frame in better detail(Get rid of the excess white spots)
v3
- Added transition from stock boot logo
- Fixed inaccurate colors on first frame
v3.1
- Removed android logo from transition
- Smoother transition animation
PREVIEW:
GIF​

excited to test this
Sent from my YU4711 using Tapatalk

Thanks, though looking now at it a bit closer I think a few of the frames may be misaligned - When I get a chance to get to my computer I'll take a closer look and probably redo them.
I can probably find a better fps but it was hit or miss on one's that would work

New version with some changes/fixes

I'm loving this. thanks!!

Romonster said:
I'm loving this. thanks!!
Click to expand...
Click to collapse
Glad to hear it

V3 out
Added a transition from the stock boot logo so the change from the logo to the animation isn't so abrupt.
So if you have changed your boot logo it may look a little odd but will still work fine.
Looking into maybe doing something else for the transition or just improving this one, don't know yet.

Awesome, thanks man!

Great, grande, thanks
Inviato dal mio ONE A2003 utilizzando Tapatalk

Great stuff!
Just a couple of suggestions for recovery installation script:
1) Mount can be done without busybox using internal command. For OPO/OP2 it reads as:
Code:
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system");
2) The permissions for newly copied file should be replaced from 0777 to 0664
Also if you will be able to make a finishing animation, that for example fade-out girl and make 1+ icon bright, it will be perfect.

spellbuilder said:
Great stuff!
Just a couple of suggestions for recovery installation script:
1) Mount can be done without busybox using internal command. For OPO/OP2 it reads as:
Code:
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system");
2) The permissions for newly copied file should be replaced from 0777 to 0664
Also if you will be able to make a finishing animation, that for example fade-out girl and make 1+ icon bright, it will be perfect.
Click to expand...
Click to collapse
Thanks for the info - the script is just a modified ZIPme script. Is there advantages to not using busybox. The permissions, you are correct. They were also what was set from ZIPme and I completely looked over it and I'll correct them.
Thanks for the suggestion for the closing animation as well, had briefly thought about doing something but just haven't gotten to it.

spellbuilder said:
Great stuff!
Just a couple of suggestions for recovery installation script:
1) Mount can be done without busybox using internal command. For OPO/OP2 it reads as:
Code:
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system");
2) The permissions for newly copied file should be replaced from 0777 to 0664
Also if you will be able to make a finishing animation, that for example fade-out girl and make 1+ icon bright, it will be perfect.
Click to expand...
Click to collapse
About the above.
If you use the above mounting method then if /system/ has already been mounted, the installation will fail as permissions fail to set for an odd reason.
You can either unmount (which will do nothing if already unmounted) and then mount in that way or mount it the proper way using busybox.
Think (from memory - been a while since I used it, I just use the lazy method above for some reason) it goes like this:
Code:
run_program("/sbin/busybox", "mount", "/system");
2) You got a typo, you do mean 644. Won't matter anyway since recovery will automatically give the correct permission to the file as it replaces it and nowadays even Android itself is capable of fixing it's own permissions.
Sent from my ONE A2003 using Tapatalk

Yes, there was a typo and I mentioned 644. Currently there is line in installation script to specifically set permission to 0777, which cannot be correct under any circumstances.
And as for unmount you are also correct, and I indeed in my scripts first unmount stuff before mounting.

Sorry for resurrecting this threat, but I do like the animation and want to use it on my OP2.
For whatever reason, though, it refuses to display, instead only showing the logo, waiting, and then booting directly into the OS without showing any video at all.
I tried both the manual and the recovery approach, to no avail. Ideas?

Now to find a NSFW version of this /s
Also wanted to know if there is a slower version of the animation, cause after like 2 seconds of dancing she starts dancing waaay too fast

I just put this in my Oneplus 5...love it. Thank you!

Ah, this one is gold

You are awesome. Great work.

Hatsune_Rox said:
Now to find a NSFW version of this /s
Also wanted to know if there is a slower version of the animation, cause after like 2 seconds of dancing she starts dancing waaay too fast
Click to expand...
Click to collapse
Made it slower myself by turning the framerate down to 17, sent it to you via PM, hope OP doesn't mind.

SelenRelas said:
Made it slower myself by turning the framerate down to 17, sent it to you via PM, hope OP doesn't mind.
Click to expand...
Click to collapse
Can I have one as well man?

Galaxy S Duos completely dead after flashing kernel via CWM

Hi everyone,
I'm having some trouble with my Galaxy S Duos. I've had PMP™ King ROM running on it, and everything worked fine, but I wanted to replace the kernel boot logo.
So I unpacked the boot.img from the ROM using Android Kitchen, used png2rle to convert my custom logo into rle-format, replaced the file initlogo.rle and repacked boot.img again with Android Kitchen.
To be able to flash the kernel via CWM I created an update zip-package and signed it with testsign.jar.
I included the update-binary from the PMP™ King ROM and my updater-script had the following lines in it:
Code:
ui_print("boot.img is being flashed...");
show_progress(0.1, 0);
assert(package_extract_file("boot.img", "/tmp/boot.img"),
ui_print("flashing boot.img...");
package_extract_file("boot.img", "/dev/block/mmcblk0p5");
ui_print("kernel imaged flashed");
ui_print(" ");
delete("/tmp/boot.img"));
show_progress(0.1, 10);
ui_print("you can reboot now");
Flashing the kernel worked without problems, but when I chose the option the reboot the device, it is completely dead since then. The screen stays dark, I can't enter download mode or recovery mode. The device isn't recognized on a PC (Linux and Windows). The battery had about 85% when I did the flashing, I put it in and out several times, tried to charge it, but still nothing happens.
I suppose I made a mistake in the updater-script. I think the line
Code:
package_extract_file("boot.img", "/dev/block/mmcblk0p5");
should have been
Code:
package_extract_file("boot.img", "/dev/block/mmcblk0p8");
Is there any chance to get back into download mode again and bring it back to life?

This is the biggest mistake, you flashed the kernel on a different partition. It's dead, JTAG is the only thing that can work now

forum.xda-developers.com/showpost.php?p=63949797&postcount=4
If you want to give this a try, keep a sd card that is class 10. Preferably a 4gb or 16gb card and try this.

Thanks for your reply, billysam.
First of all, I have to say you are right. I also made some further research on flashing kernels, and this was a stupid mistake from me. I've learned my lesson the hard way ...
I will try the debrick-image, but unfortunately I only have a 8gb class 10 card at the moment. I will get a 4gb card and give a report if it worked.

webbandro said:
Thanks for your reply, billysam.
First of all, I have to say you are right. I also made some further research on flashing kernels, and this was a stupid mistake from me. I've learned my lesson the hard way ...
I will try the debrick-image, but unfortunately I only have a 8gb class 10 card at the moment. I will get a 4gb card and give a report if it worked.
Click to expand...
Click to collapse
Well we all Learn here through hard ways, but that should not let you stop, anyways about the debrick method, It's a experimental process, it has only worked on sgs3. I still haven't heard from anyone who had success with that process with our device. Still there are chances it might work on us too. Plus I don't see any harm on our device because of trying that process, unless your device is same and already bricked. Anyways, do let us know, if it works.

Hi! How was the phone? Could you bring it back to life again?really eager to know.