[Q] Both volume buttons on MIUI - Huawei Ideos X5 U8800

MIUI version:2.3.23_R3 from this thread
My phone does something strange on both volume button pressing. Looks like it's start to do something, because everything starts to lag. After that strange activity there's 3 short vibrations and everything ends. What it should be?

It is in the init.qcom.sh (maybe init.huawei.rc) in the boot.img from memory. It is related to the rom generating a debug log on pushing both volume keys. Huawei leaves it in for testing but it does not function without root. When we root, it starts to function again!
This is from another rom of mine, but had to be changed in one of retarts miui's as well.
Inside init.huawei.rc look for these rows:
Original:
# bugreport is triggered by the KEY_VOLUMEUP and KEY_VOLUMEDOWN keycodes or triggered by projectmenu
service bugreport /system/bin/dumpstate -d -v -o /sdcard/bugreports/bugreport
user root
disabled
oneshot
keycodes 115 114
Modded:
# bugreport is triggered by projectmenu
service bugreport /system/bin/dumpstate -d -v -o /sdcard/bugreports/bugreport
user root
disabled
oneshot
If Terramino does not see this, I will look tonight and see if I can put up a modded boot.img from his rom.
---------- Post added at 06:48 PM ---------- Previous post was at 06:42 PM ----------
Oops, just checked your link, its sbasils rom. Which one did you flash? the r5g or r5u? I will check in the them and see what needs to be patched.

Thank you very much for your post. I've modded init.huawei.rc as you described and that reaction on both volume pressing gone. I've used R3 version. There were no UNN's kernel version for that time. Now i'm downloading R5G and gonna check it.
UPD: Hmm... with R5G situation is different. It restores every reboot original init.huawei.rc with "keycode 114 115" line in it.
What should i do? Can you say about this in android development section (i think every rommaker should know about this)? Can't do it by myself - doesn't have enough posts

As it is in the boot.img it will restore at every boot. You need to open and change the boot.img to make it work. Will talk to sbasil and see what I can do, then will make a post about when I have investigated more.

Here is the fixed boot.img in the dev thread:
http://forum.xda-developers.com/showthread.php?p=24138036#post24138036
Backup everything and replace boot.img in the r5g rom zip then flash again. Please backup first as I am still on .32 kernel so can't test this, but it has worked before and is only changing one line leaving everything else the same.

Just replaced boot.img with yours on my phone via pink screen. No need to re-flash rom. Looks like everything is fine. Thank you again

great, glad it worked

Moved To Q&A​
Please post questions in the Q&A section​

Related

(for tereg) NoRecovery custom recovery

Hi tereg,
[SIZE=-1](If you are not tereg, you can stop reading this. I didn't PM because I needed to ship an attachment)[/SIZE]
Have a look at the attached (custom) recovery (pick it apart and diff it against the leak-V3/RUU recovery.img) using split_bootimg.pl and the gunzip | cpio pipeline.
You can flash it to your recovery partition and run it if you like, it doesn't do anything dangerous. Basically, it is the same thing as the Leak-V3(=RUU = OTA-2.1) recovery, with two major changes:
- /sbin/recovery service is turned off so this doesn't run automatically (and as a result you won't see the splash screen change from the 3 skating droids). You can run it manually, though, from the adb shell - just wait 8-10 seconds and adbd will come up.
- I added the shell (sh) and a few of the diagnostic tools (dmesg, dumpstate, logcat... and supporting dynamic link libraries, the linker, etc), and dropped in there both /system/bin/toolbox (HTC) and /system/xbin/busybox and created some of the symlinks so that an adb shell has a useful set of tools available. (Oh yeah, I added an /etc/fstab as a convenience for /system/xbin/mount. Note the system mtd partition mounts at /os-system so it won't cover up all the installed tools underneath /system in the boot image)
- I altered the init.rc (and default.prop) so that adbd will always come alive - not just when a race is won.
The base of this image (kernel, bootscripts, /sbin), is the leak-V3 recovery.img; everything else such as dynamicly linked executables and supporting dynamic libraries comes from Jcase's Plain Jane, which in turn comes from Leak-V3/OTA/RUU, so, essentially everything in this bootable recovery comes from HTC except the version of busybox in /system/xbin and mods to the init scripts and default.prop
Note that the NAND flash partition in the mtd device for the recovery is only something like 5.2 MB - I would have added more, but was starting to get tight on space.
If you want it to run as close as possible to the timing of the HTC leak-V3 recovery.img, what I would do would be the following:
- defer all the symlinking in init.rc (except for the "sh" and "ln", of course) and package that up into a shell script that you can run after the recovery has booted
- uncomment (re-enable) the "recovery" service (/sbin/recovery)
- maybe experiment and see if you can get the complete kernel boot sequence from dmesg without starting logcat as the first service (that's not done in the normal recovery).
The only other useful piece of info that I can think of at the moment is that you need to use the ---base option with mkbootimg with an address that starts with something like 0x11208000..... (I can't recall and my machine is down - crap.) You can discover the value of the kernel base address load offset for the Eris by snooping through a hexdump of the beginning of any valid Eris bootable image
cheers
bftb0
MD5s
5801babcdf4e6e5d51e5f775aad0a09e ErisNoRecovery-recovery-v0.9.0.img.zip
4d280b367be75e7e75563a6357575ea7 ErisNoRecovery-recovery-v0.9.0.img
Sent via my nearly dead crap Pentium II booted from a 2003 version of Knoppix - 256 megs of EDO RAM - woot!
Sorry, here's the attachment
I read it anyway.
Suck it.
Hungry Man said:
I read it anyway.
Suck it.
Click to expand...
Click to collapse
Same Here Brosidon,
Well, actually i attempted to read it. Then I got confused and went and got some beef jerkey.
mmm beef jerky. i read it to maybe there will be a fresh recovery menu for the eris.
i read somones got beef jerkey and not sharing *waves fist* four messin up kid
j/k
it would be nice if we got an updated recovery. especially now learning that we won't need/be able to format our sdcards using FroYo.
Actually, I don't mind if anybody reads or uses that - it just gets me off the hook when somone asks
"But what is this for?"
Now someone will ask, LOL
bftb0
bftb0 said:
Actually, I don't mind if anybody reads or uses that - it just gets me off the hook when somone asks
"But what is this for?"
Now someone will ask, LOL
bftb0
Click to expand...
Click to collapse
but what is this for??? can i root my eris 2.1 v3 leak??? can it make pizza out of code? jk jk lol,
Thank you, I got it now.
I will definitely be experimenting with this. I'll let you know if I have further questions.
Tereg, I'll be online tonight and can help with testing.

[Q] how can re-root the offical update?

hi.. after following the instructions on how to downgrade my phone, and obtain root, i have, and after i had my foryo rooted, i downloaded RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2 because my original intent was to have a rooted gingerbread and it didn't make much sense to have roms provided by htc itself.
but now i see i don't have root, so oops, i guess i was wrong.
so do i have to go though the whole kaka procedure again, and then find a custom rom, because my end game, is to have as close as possible a rooted gingerbread as close as possible to the original HTC rom. where can i get one?
oh, and what's the difference between the asia and wwe? does any of them handle hebrew bidi writing correctly (without applying the patch?)
I think there is a way to root gingerbread, or you have to downgrade. At either rate, you want to get to a place where you can flash your own ROM. Having clockworkmod installed would be just fine.
Then you would take the stock gingerbread, extract and unzip it, add Superuser and su, make the boot insecure, repack it for flashing, flash via CWM, and presto- rooted stock gingerbread. If you want to build in hebrew bidi writing, you can add that too.
There might be a few rooted stock gingerbread roms out there, but it seems that the trend is toward cooked up versions, rather than stock.
AFAIK i don't there's a way to root gingerbreak, it's un-rootable, that's why i downgraded in the first place. i think i can do it again, question is:
where do i find the stock gingerbread rom? is it in the RUU exe? if so, how get it out from there, without installing it
second, how on earth would i do all the things you said (add su,make boot insecure,repack,flash cwm).
is there a guide out there for all there above?
I think there is a some software for windows that will allow you to extract the rom from the RUU. I don't use windows, so I don't know anything about it. I've seen some posts about it, so I can say it seems to involve using the RUU to almost install the ROM, but at the last minute, just stop and the ROM will be extracted into one of the temp directories. You just use the RUU to extract the rom, not install it.
As far as all those other steps, I think all the information is scattered about xda.
Here's some information about the insecure boot image. It's for the transformer, but it's essentially the same thing, except for the blob parts. You'll have to use something like splitbootimg or bootunpack, and mkbootimg (search for them) instead of blobunpack.
http://forum.xda-developers.com/showthread.php?t=1193737
This might be more helpful:
http://forum.xda-developers.com/showthread.php?t=1100189
As for the other parts, you can use some of the other updates and zip files as a guide to figure out how to unpack, mod them, and repack them. I think there might be a rom kitchen script that will do this too, but I can't speak to that either.
Sorry if this sounds so complex- it's not that bad once you've done it once. I have a rooted stock GB that I made this way from the GB update, but it's the US version. Let me know when you have the WWE version extracted.
ok, let's take it one step at a time, (maybe we'll make a guide out of it
i activated the but i never continued instead i used process explorer to find out which files it's holds, so i got the temp directory and extracted rom.zip a 260 mg file (containing various img files)
now what?
btw is this relavent? http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
yea, i've seen it is, but one issue is that where do i get the cpio and makebootfs, (if i need to compile stuff, this is where i stop, i allready downloaded the perl scripts, as well as GZIP
ok, so far so good.
That link is exactly what you need. You can use that info to unpack the boot.img and make it insecure "ro.secure=0" by editing the default.prop file in the ramdisk.
I think some of the links to the tools might not work, but these will work instead - https://github.com/AndroidRoot/BootTools
Use the guides to mod and then repack the ramdisk
put the kernel and the modded ramdisk back together with makebootimg. There might be some specific command lines and kernel addresses- the hdrboot tool will show you want they should be from the original boot.img
Also, could you upload the zip file or PM me a link? This would be a perfect project for a guide.
ok wait, which tools am i missing? i have a windows machine (ultimate 7 64 bit) and the boottools needs to be compiled, (i don't have developer studio installed just eclipse)
so far i have the following tools:
repack-bootimg.pl
unpack-bootimg.pl
split-bootimg.pl
cpio for windows
gzip
what zip file?
(i'm going to sleep now as i'm in israel,i will "boot" in 6 hrs, luckily i have a vacation tommorow, so i hope we'll have time to finish this.
I think you might need gunzip to extract the ramdisk. unzip might work, but I'm not sure with Windows.
The zip is the rom.zip which has the rom.
I seem to recall there being at least 2 rooted stock ROMs in the dev forum. I think the one I've used was posted by either suilmagic (may be siulmagic), or rmk40. Xboarder56 posted one some time ago, but he started stripping things out that I used, like QuickOffice. If nothing else, this finally drove me to use Titanium backup...
Sent from my HTC Vision using Tapatalk
Yeah, I guess a search would take some of the fun out of it....
http://forum.xda-developers.com/showthread.php?t=1169004
actually i DID google "rooted stock rom desire z"
but i could find anything for sure, that's why i posted this, is this rom appear in the developer list of roms linked in the downgrade wiki? because i couldn't find it there either, would be nice if it was added.
No worries- I didn't actually search for it- I just paged through some of the dev sections.
I think you'll have flash it using CWM recovery.
great, i'm assuming CWM is Clockwork something?
Yup- look for the 3.x version. There was a 5.x, but i think it has some issues.
ok, so now, i must re-downgrade, root,
http://forum.xda-developers.com/wiki/ClockworkMod_Recovery
get rom manager, and ah... wait, what's the update.zip? is that actual image i need to place on the sdcard?
That wiki seems kinda old- I don't think the stock recovery will flash the update.zip
This is more up to date and specific for the G2/DZ:
http://forum.xda-developers.com/wiki/HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
yea i've read that one (that's how i rooted in the first place.
isn't there a way to short ciruit this somehow and instead of pc10img have the update itself installed ? or is it because it's a an OTA, i have to do the whole thing?
looking at the image, i think i'm missing someting it looks like i can somehow use the scripts inside the image when i get temp_root (meaning i won't have to update the original image. am i wrong?
ok i've gone through the motions over and over, finally rooted it, have rom manager, clicked flash recovery, copied the zip file for rom i wanted to the root of sdcard, selected it rom manager, rebooted, now i selected apply update from sdcard,
now i see the hat signal and nothing happens, (i also selected backup rom and wipe cache and data)
i also noticed that i have install zip from sdcard, but i didnt' select it, how long should it take?
ok i FINALLY managed to install (it actually i pressed power button again and immdietly returned the cwm main menu, from then on, i chose reboot, i think it's moved on.
problem is, some things looked odd, for example the phone bar on the buttom, looks distorted, when i click on the application list i can only see half the list (meaning half the screen shows the list although i can scroll up and down the buttom half remains blank..
never mind it's ok now after re-boot..
btw i tried creating a batch file like so:
adb shell cat /dev/msm_rotator
rem expected output
rem /dev/msm_rotator: invalid length
pause
rem temp_root
rem adb push fre3vo /data/local/tmp
rem adb shell chmod 777 /data/local/tmp/fre3vo
rem adb shell /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
echo wait for device to reconnect
pause
adb push misc_version /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/misc_version -s 1.00.000.0
adb shell sync
adb shell dd if=/dev/block/mmcblk0p17 bs=1 skip=160 count=10
rem expected output is:
rem 1.00.000.010+0 records in
rem 10+0 records out
rem 10 bytes transferred in 0.001 secs (10000 bytes/sec)
pause
rem downgrade
rem wget http://www59.multiupload.com:81/fil...118187CA1236F3BA6767A7/1.34.405.5_PC10IMG.zip
adb push 1.34.405.5_PC10IMG.zip /sdcard/PC10IMG.zip
adb reboot bootloader
but it didn't workout so much, don't know why it said something about it couldn't write recovery img file
Umm if you already rooted via the xda wiki then you should've had a bootloader that was engineering s-off right? Just saying because you could've flashed a custom rooted rom through bootloader and not had to re-root, that is unless the ruu applied an updated bootloader with s-on. Maybe boot into bootloader and see if the top line says PVT ENG S-OFF, worth a look anyway, could save you some headache
Sent from my Bulletproof G2
actually i'm haveing another headache a couple actually, for some reason, during the restore, it failed to download google maps among the gailion apps i downloaded, now i can't download no matter, i tried installing it manually, and it worked, but i can't see in the market.
the market on the web site says the application is not compatible.
also when i tried using anysoft keyboard and use the hebrew fonts, even though it installed i still couldn't get the keyboard.
right not i have no idea what's the state of my phone.

[GUIDE] The Ace Xperia Play Setup 1.2! ~ Dalvik Tunning!

Ace Xperia Play​Hello Guys! , after scavenging the whole of the Xperia Play Forums I present to u the best Xperia play Setup in my opinion (and some others...)
First off i Wanna Give some Quick Thanx to:
ozzmanj1 - He Convinced me Heavily about the Stock Rom + A Working Odex Script!
TLRTheory - He convinced ozzmanj1 who convinced me,
Wedgess - A real developer!
DoomLord - Where would we be without him?
juwe11 - The Great Ramscript
LENAROX - The Unique and Amazing Pro-Tunned ADJ
Ryuinferno - Uni Init.d
Zepplinrox - Sclean
Bakisha - Telling me about Odexing!
CosmicDan - Dalvik Dexopt Flags
NOTE! You Must do these in order for the Best Stuffs, Also Please Read Everything
So Lets start shall we?
Oh wait no, Get some Coffee or another Beverage and get ur xP and Hook it up to ur PC,
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Backing Up!
First of were going to need some backups incase Anything goes wrong, So Go Ahead and:
-Reboot into CWM Recovary > Make a CWM Backup
-Reboot back into ROM > Download Titanium Backup and Run a Backup of All User Apps
-Power off you Device > Put it to Charge > (While waiting for Charge) Pull out the SD-Card and Manually mount into PC (Otherwise just do it normally with Android on, NOTE! it will take much longer) Now Cut Everything into a Secure location onto your PC
2. Preping
Just some things u need to be able to go to the next step:
-A Fully Charged Battery
-An Empty SD-Card
-Some more Coffee
now to continue we need to wipe all old things:
-Reboot into CWM > Wipe:
--System
--Data
--Cache
--Dalvik Cache
--SD-Card
--Battery Stats
now power off the device and keep it hooked up to power
Download the Following:
Xperia Play 52 Enhanced v3 Firmware
Flashtool
Lupus GB v12 LagFixed Edition
Now install Flashtool and copy the Xperia Play 52 Enhanced v3 Firmware to the flashtool firmwares folder
3. Flashing
Time fore the main moment,
-Run Flashtool (NOTE! if u have 64-bit, run the 64bit, also sometimes u have to like 6 times click it to open...)
-Disconnect your Device
-Connect the device in Flashmode (Will promt how to)
-Let it do its work (NOTE! If it asks to install drivers, go to the flashtool subfolder names drivers, run the .exe and select the list with xperia play in and select flashmode, then reboot)
-Now disconnect the device AND DONT BOOT UP
-flash Lupus GB v12 LagFixed Edition
-Now Gracefully boot up the device knowing you have the cleanest xp in existent,
4.Restoring
Now u can copy ur SD Card back, Advice : enable msc for faster transfer
U can also restore all apps via Titanium Backup, just download the app and restore
5. Root
When rebooting allow lupus gb to root
then go to playstore and install superuser and update the su binary
6. Fine-Tunning
This is the good stuff,
so we need to get performance and battery TOP NOTCH!
First off i recommend fine tunning the Android native settings, so adjust ur ringtones and etc... anothing thing is Leave animations on,
Then delete all apps u can from data/app, eg hotshots, fb and the rest of the sony junk
Now off to tweaking!, download:
Uni-Init.d
AutoMagical Debloater
Key for AutoMagical Debloater: JzzTXhl0MJlkga6fbLy5OXI2-FwXAXI_ZMU3MkRxE9I
Now download:
Root Browser
So first off reboot into recovary, and flash the Uni-Init.d zip
Now Flash Debloater.zip then Reboot x2
Open Root Browser and navigate to /system/app and here i cant help much, this is ur brain and eyes, manually compare whats in the zip i provided and the /app folder and remove stuff so ur devices apps are equal, now u may get some FC's but its nothing to dangerous to worry about,
Reboot now!
Some more debloating:
Navigate to system/etc, press search and type *.apk u should find some apk files, of their Verizon/Sony related, delete them!
Their is also another thing we can do called Odexing, be aware that doing this will result in you not being able to mod any framework files
Download the Odex Zip First, Flash it in CWM then Wipe Cache and Dalvik Cache and reboot x2 Then:
- open terminal emulator (will be installed automaticaly)
- type su to obtain root permission
- type dexo -h to show possible commands for your phone
- type dexo -one of the option that you have decided
I & Ozzmanj1 recommend Odexing Everything - all
7. Tweaking
Suprisingly enough, All tweaks existent on android SUCK, (Joking) basically what im saying is we only need 3 tweaks
first off open root browser, go to /system and open build.prop, now allow editing:
Input the following for everyday use and generally amazing performance in eveything
Code:
# Pro-Tuned ADJ 1.2 by LENAROX.
ro.FOREGROUND_APP_ADJ=0
ro.VISIBLE_APP_ADJ=4
ro.PERCEPTIBLE_APP_ADJ=3
ro.HEAVY_WEIGHT_APP_ADJ=2
ro.SECONDARY_SERVER_ADJ=1
ro.BACKUP_APP_ADJ=5
ro.HOME_APP_ADJ=6
ro.HIDDEN_APP_MIN_ADJ=7
ro.EMPTY_APP_ADJ=15
#ultimate assassin mode.
#ro.SECONDARY_SERVER_ADJ=15
#ro.HIDDEN_APP_MIN_ADJ=3
or if ur extreme and want amazing games and pretty much no multitasking then this:
Code:
# Pro-Tuned ADJ 1.2 by LENAROX.
ro.FOREGROUND_APP_ADJ=0
ro.VISIBLE_APP_ADJ=4
ro.PERCEPTIBLE_APP_ADJ=3
ro.HEAVY_WEIGHT_APP_ADJ=2
ro.SECONDARY_SERVER_ADJ=15
ro.BACKUP_APP_ADJ=5
ro.HOME_APP_ADJ=6
ro.HIDDEN_APP_MIN_ADJ=3
ro.EMPTY_APP_ADJ=15
#ultimate assassin mode enabled.
save and exit, now reboot or cary on to next tweak and then reboot after that
Next up were going to optimize dalvik verification and optimization, to do this were going to navigate to /system/build.prop and open it and start editing, look for something like this:
Code:
dalvik.vm.dexopt-flags=m=y
after lots of reasearch i came across a thread where CosmicDan Explained how dalvik vm worked with this and etc, and acording to him setting the dalvik vm to this parameter will increase performance all over the board
So replace with this:
Code:
dalvik.vm.dexopt-flags=m=y,v=n,o=v,u=n
Done, now reboot 2 times, then continue on to the next tweak!
Now Init.d Tweaks, We only need 1, So open up root browser and navigate to /system/etc/init.d (this is long text, so i recommend save as file then in android cp and paste, if ur going to do this paste it into notepad++ and then save as .sh and then rename and remove .sh extension, we save as .sh to get the linux formatting so no bootloops or inactive scripts r their...) and make a new file called "97ramscript", Within the script input the following:
Code:
#!/system/bin/sh
# Copyright© 2011 Juwe11
if [ -e /sys/module/lowmemorykiller/parameters/minfree ]; then
echo "2560,4096,6144,12288,14336,18432" > /sys/module/lowmemorykiller/parameters/minfree
fi
if [ -e /proc/sys/vm/swappiness ]; then
echo "20" > /proc/sys/vm/swappiness
fi
if [ -e /proc/sys/vm/vfs_cache_pressure ]; then
echo "70" > /proc/sys/vm/vfs_cache_pressure
fi
if [ -e /proc/sys/vm/dirty_expire_centisecs ]; then
echo "3000" > /proc/sys/vm/dirty_expire_centisecs
fi
if [ -e /proc/sys/vm/dirty_writeback_centisecs ]; then
echo "500" > /proc/sys/vm/dirty_writeback_centisecs
fi
if [ -e /proc/sys/vm/dirty_ratio ]; then
echo "15" > /proc/sys/vm/dirty_ratio
fi
if [ -e /proc/sys/vm/dirty_backgroud_ratio ]; then
echo "3" > /proc/sys/vm/dirty_backgroud_ratio
fi
then save,now long press and set permissions to all of them (basically tick all 9 boxs)
now reboot
8. Keepin it Clean
Now we have everything done and our xPlay is Top notch but we need to keep it top notch!
so download:
Clean Master , And clean caches and empty folders regulary, HOWEVER please dont use TASK KILLERS, their terrible and ruin performance!!!
next up, install Busybox, Download this:
Super Cleany and open root browser and copy Super Cleany to /system/xbin, then set permissions to all (basically tick all 9 boxs), then Open Busybox and install it using the smart install, just use all defualt settings, once installed uninstall the app
Now download Terminal Emulator and type "su -c sclean" but only do this every like 2-3 weeks or when u feel ur device is extremely laggy, what it does? this cleans the device thoroughly and then reboots!
next thing is to disable startup programs, Download ES Task Manager and run the startup apps, click optimize then u can disable the following manually:
Google Play Store
Messaging
u can also disable anything u know of, eg titanium backup!
thats it, everything else leave it, Word for the wise: Dont disable anything u dont know,
Also just a general tip, dont install useless apps, eg Facebook as u can use it thru the browser!
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
That's it! I hope u liked it!
Also please gimme a tnx I spent ages typing this,
Hey pizza_dox don't thank me for pushing the whole "stock". Thank TLRtheory. I PMd him about his setup as he was always talking about the performance of stock. So he's the one who convinced me. However I do appreciate you thanking me. And I would like to thank you for your work. You are always updating your roms and scripts and posting guides or setups. It goes a long way. So thank you
Sent from my R800i using xda premium
---------- Post added at 09:50 PM ---------- Previous post was at 09:41 PM ----------
Also remember all the extra junk you mentioned to me in the system folders such as apps and files thar weren't necessary but left by Sony. Even after you delete the apps some of the files remain. You gave me another 35-40mb of storage.
Sent from my R800i using xda premium
Oh ok, still...
Oh yea forgot those apps, well I was sorta in a rush, will update now,
Edit
Thanx, also I updated but I'm slowly finding stupid typos ans random grammar errors...
(was in a rush...)
Sent from my R800i using xda app-developers app
Is the kernel from Lupus with Lagfix is that the same as Lupus v12.5?
Someone should do a comparison video showing off stock debloated and OCed on games and some emulators. Is it really better for gaming?
Fenrir007 said:
Someone should do a comparison video showing off stock debloated and OCed on games and some emulators. Is it really better for gaming?
Click to expand...
Click to collapse
When I switched from CDMA to the GSM model back in Feb of this year, I tried all sorts of custom roms. What made me really notice the difference was MC4. I could never get past 26fps on a number of custom ROMS. I then flashed the .79 ftf and deblaoted the hell out of it. Big difference. I ran a FPS meter and was getting 40-42fps on stock debloated no V6 supercharger scripts. No nothing. I was overclocked to 1.1ghz on performance and SIO. Ran smooth as silk.....
Dont this the wrong way, I am extremely appreciative of everyone who assists and participates on the XP forum with custom roms however I simply will not go back to a custom rom. Now that being said I did take the systemui.apk form the NXT Rom and replaced it over the stock systemui.apk and I have working toggles on a stock rom.
ozzmanj1 said:
When I switched from CDMA to the GSM model back in Feb of this year, I tried all sorts of custom roms. What made me really notice the difference was MC4. I could never get past 26fps on a number of custom ROMS. I then flashed the .79 ftf and deblaoted the hell out of it. Big difference. I ran a FPS meter and was getting 40-42fps on stock debloated no V6 supercharger scripts. No nothing. I was overclocked to 1.1ghz on performance and SIO. Ran smooth as silk.....
Dont this the wrong way, I am extremely appreciative of everyone who assists and participates on the XP forum with custom roms however I simply will not go back to a custom rom. Now that being said I did take the systemui.apk form the NXT Rom and replaced it over the stock systemui.apk and I have working toggles on a stock rom.
Click to expand...
Click to collapse
Did you notice any difference in emulators? Oh, and I remember trying MC4 on Auroraplay and it was pretty smooth, but I'm not sure about the fps. Might check that next time.
I only use emu up to n64 and everything runs great.
Sent from my R800i using xda premium
Nice guide. Maybe to add odexing script at the end, when it's debloated, to save data space..
I also switched to .79 recently as daily driver. Debloated, odexed, installed new systemui and smartsearch dialer, and it's flying...
Antutu score is around 5500, on stock speed, and i didn't see any lag in games, not even MC4.
ozzmanj1 said:
Is the kernel from Lupus with Lagfix is that the same as Lupus v12.5?
Click to expand...
Click to collapse
Yep,
Bakisha said:
Nice guide. Maybe to add odexing script at the end, when it's debloated, to save data space..
I also switched to .79 recently as daily driver. Debloated, odexed, installed new systemui and smartsearch dialer, and it's flying...
Antutu score is around 5500, on stock speed, and i didn't see any lag in games, not even MC4.
Click to expand...
Click to collapse
Well i aimed to save battery & Performance, forgot about odex, , but generally i see no difference in odex
Pizza_Dox said:
Well i aimed to save battery & Performance, forgot about odex, , but generally i see no difference in odex
Click to expand...
Click to collapse
Not much difference is speed, but it can save around 50-60MB from data partition. And debloadet GB rom have a lot of spare space in /system partition.
Ofcorse, not needed for most users with lupus kernel, and is highly optional.
Bakisha said:
Not much difference is speed, but it can save around 50-60MB from data partition. And debloadet GB rom have a lot of spare space in /system partition.
Ofcorse, not needed for most users with lupus kernel, and is highly optional.
Click to expand...
Click to collapse
Okai, , Well where can i find the Odex Script,
Pizza_Dox said:
Okai, , Well where can i find the Odex Script,
Click to expand...
Click to collapse
I can't recall did i download it somewhere, but i know that Aurora ROM have odexing script in it
EDIt: X-game rom thread have odexing script separate. It's in end of first post
Bakisha said:
I can't recall did i download it somewhere, but i know that Aurora ROM have odexing script in it
EDIt: X-game rom thread have odexing script separate. It's in end of first post
Click to expand...
Click to collapse
tnx will add to op,
The odex file gives me an error when attempting to flash in in recovery. CWM
Oh OK... Well I'm on ICS now (ICS browsing is not good...), just Google it,
Sent from my R800i using xda app-developers app
Pizza_Dox said:
Oh OK... Well I'm on ICS now (ICS browsing is not good...), just Google it,
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
Yeah, I was already on it. Just wanted to let you and everyone know first. Soon as I find an odex file I will post a link here or embed it here.
---------- Post added at 07:38 PM ---------- Previous post was at 07:34 PM ----------
Here is a download link, its from GS4 but it says it works on everything from Froyo+
Thank to: MatrixDJ96 (XDA user who provided link) for him posting this:
Source:
http://forum.xda-developers.com/showthread.php?t=2400342
Download Link:
UniversalOdexScriptV62.zip
Link: https://googledrive.com/host/0B2ftBoBlBHTIWVZITGRMenpQeWM/
ozzmanj1 said:
Yeah, I was already on it. Just wanted to let you and everyone know first. Soon as I find an odex file I will post a link here or embed it here.
---------- Post added at 07:38 PM ---------- Previous post was at 07:34 PM ----------
Here is a download link, its from GS4 but it says it works on everything from Froyo+
Thank to: MatrixDJ96 (XDA user who provided link) for him posting this:
Source:
http://forum.xda-developers.com/showthread.php?t=2400342
Download Link:
UniversalOdexScriptV62.zip
Link: https://googledrive.com/host/0B2ftBoBlBHTIWVZITGRMenpQeWM/
Click to expand...
Click to collapse
Tnx alot, , Updated OP,
ozzmanj1 said:
Yeah, I was already on it. Just wanted to let you and everyone know first. Soon as I find an odex file I will post a link here or embed it here.
---------- Post added at 07:38 PM ---------- Previous post was at 07:34 PM ----------
Here is a download link, its from GS4 but it says it works on everything from Froyo+
Thank to: MatrixDJ96 (XDA user who provided link) for him posting this:
Source:
http://forum.xda-developers.com/showthread.php?t=2400342
Download Link:
UniversalOdexScriptV62.zip
Link: https://googledrive.com/host/0B2ftBoBlBHTIWVZITGRMenpQeWM/
Click to expand...
Click to collapse
Forgot to add this important stuff in order to use the odex script, sorry ya'll.
How to odex:
- download file
- go to recovery
- install zip
- reboot
- open terminal emulator (will be installed automaticaly)
- type su to obtain room permission
- type dexo -h to show possible commands for your phone
- type dexo -one of the option that you have decided
Pizza_dox can you add to your OP. Thanks
---------- Post added at 08:57 PM ---------- Previous post was at 08:16 PM ----------
Just a tip. I typed in SU in the terminal emulator that is installed from the script.
Then type in dexo -h and it gives you a list of options. If you want to odex your whole rom type in:
dexo -all
Then hit enter give it a minute, then it will reboot and you are done.

[MOD][SCRIPT] Get More Storage by Relocating Dalvik Cache!

DISCLAIMER: YOU AGREE TO TAKE FULL RESPONSIBILITY FOR YOUR DEVICE IF YOU PROCEED.
The original thread (http://forum.xda-developers.com/moto-g/general/mod-save-data-space-cache-partition-t2942765) was getting to cluttered up with development and testing so I decided to start a new thread with the "finished" product. The original thread will be renamed to Q&A/Development. We might even ask for the old thread to be closed down. (up to @Bert98, the thread's creator.)
Moto G's internal eMMC card has a ~600Mb partition called /cache, which is not used since the apps' cache is stored in /data, so the latter fills up and the first one stays empty.
Owning a 8Gb model, having 600Mb not available for storage really bugged me, because my phone's memory (/data partition) was always full because it's a 5.7Gb space shared between apps and microSD files.
Now, it may not work for you if:
a) you have A LOT of apps installed.
And by "a lot", I mean more than 90-100 apps, but if you have a 8Gb model, you probably don't
b) you're running ART (this is default in lollipop and newer)
Since ART uses a lot more space than dalvik, the space in the /cache partition probably won't be enough. When I was running ART, it used 1Gb more than dalvik.
Original post by @Bert98
Click to expand...
Click to collapse
This was tested on my moto g 16GB which is running RetailUS_4.4.4 kitkat with CWM recovery. The custom ROM procedure was tested on the same phone but with cm11 Nightly installed.
Prerequisites:
1. You must have "adb root" functioning. If you don't head to this thread: http://forum.xda-developers.com/showthread.php?t=1687590 and there is a free download link at the bottom of the post.
Download and install the apk on your phone. Open up adbd insecure (the new app) and grant it superuser rights PERMANENTLY. Check the box that says "enable insecure binary" and make sure to check the box
that says "enable at boot."
2. You must have a recovery that can accept adb shell commands.
3. Root Access Duh?!
4. A windows machine capable of running batch files.
5. A decent text editor, notepad will work but notepad++ is strongly recommended. (Only needed if you are using STOCK ROM procedure)
Please, please make a nandroid backup before you continue!!!!
Stock ROM procedure:
Read the directions very carefully and then read them again, before continuing.
1. Download the cachemover_v1.3.zip from: LINK REMOVED DUE TO SCRIPT ISSUES.
2. Extract the contents.
3. Connect device to PC and navigate to the extracted folder.
4. Double click/Run the cachemover_Stock.bat
5. Follow the onscreen instructions until you get to the part where it says to edit a file.
6. About halfway through the script it will pull a file called "init.qcom.post_boot.sh" to the folder.
7. Open it with a TEXT editor and navigate to about line 487 (Might be different for 8gb model). Look here for a better understanding: https://www.dropbox.com/s/jr5lyl5s5i2jtpg/where to paste code.PNG?dl=0
8. Start a new line and paste this code in the file: (Refer to the image above for help)
Code:
chmod 655 /cache
chmod 655 /cache/dalvik-cache
chmod 655 /cache/dalvik-cache/*
9. Make sure to save the file in the same folder as the cachemover_Stock.bat
10. Press any key to continue on the script and let it do its thing.
11. It will reboot several times and land you on the home screen/lock screen.
12. If the script hangs after a reboot, you need to unlock the device to reestablish a connection with your computer.
13. There might be one or two force closes but once you close the notifications they will not come back.
Custom ROM procedure:
USE THIS FOR ROMS THAT DO NOT REMOUNT OR CHANGE PERMISSIONS OF /CACHE ON BOOT
1. Download the cachemover_v1.3.zip from: https://www.dropbox.com/s/bzj34g4q1s61ojz/cachemover_v1.3.zip?dl=0
2. Extract the contents.
3. Connect device to PC and navigate to the extracted folder.
4. Double click/Run the cachemover.bat
5. Follow the onscreen instructions.
If anything goes wrong:
Go to recovery, wipe cache, then wipe dalvik-cache and reboot. This should get your device back to how it was.
(If you used STOCK ROM procedure)
The script made a backup of the "init.qcom.post_boot.sh" file to /sdcard/init_backup
You can restore the shell script to /system/etc/ via shell commands or by using a root browser. To restore permissions:
Code:
chmod 740 /system/etc/init.qcom.post_boot.sh
chown root:root /system/etc/init.qcom.post_boot.sh
Custom ROM procedure already has a restore script!
I am currently working on an auto restore script for stock and that will be relased soon, hopefully! :good:
Changelog:
v1.0 - First stable release. Does not work on STOCK ROM.
v1.1 - Added a restore script.
v1.3 - Added support for STOCK ROM. There are still a few bugs.
How it works?!?!
Coming soon...
Huge thanks to @Bert98 and @dd043
Hit the thanks button if it worked! I went through about 50 factory resets, and reflashed the ROM about 25 times, and put about 10 hours of work into this script! Really motivates me for future projects. :laugh:
Thanks for your help man and effort.
I encountered a problem, everything works up until my device boots in CWM to fix permissions, then just sits there doing not alot I don't even see the option in my CWM.
Any ideas? cheers
Sent from my XT1032 using XDA Free mobile app
When it reboots to cwm unplug the cable and replug it, if it hangs just type these commands manually from a command window.
chmod 655 /cache
chmod 655 /cache/dalvik-cache
chmod 655 /cache/dalvik-cache/*
reboot
If this does not work you may ned to go into mounts & storage in the cwm menu and click mount /cache. Then try the commands again.
I'm having some issues on stock.
I thought 0655 fixed everything but no, I can't install any app after moving the dalvik-cache to /cache. I tried chmoding 0777 on the new cache folder, on /cache itself, to no avail.
Code:
E/dexopt cannot open '/data/dalvik-cache/[email protected]' for output
Anyone can confirm it's not only my device? And/or can help find a fix?
Also does someone knows how to execute commands on a particular init step? Real init.rc scripts can do:
Code:
on post-fs-data
mount -o bind /cache/dalvik /data/dalvik-cache
It there was a way to achieve the same from post_boot/init.d we could mount -o bind /cache/dalvik /data/dalvik-cache and all permissions issues would disappear as well as the need for symlink.
You have a typo in the threads title. Just a heads up.
Vuciz said:
You have a typo in the threads title. Just a heads up.
Click to expand...
Click to collapse
Thanks for letting me know!
dd043 said:
I'm having some issues on stock.
I thought 0655 fixed everything but no, I can't install any app after moving the dalvik-cache to /cache. I tried chmoding 0777 on the new cache folder, on /cache itself, to no avail.
Code:
E/dexopt cannot open '/data/dalvik-cache/[email protected]' for output
Anyone can confirm it's not only my device? And/or can help find a fix?
Also does someone knows how to execute commands on a particular init step? Real init.rc scripts can do:
Code:
on post-fs-data
mount -o bind /cache/dalvik /data/dalvik-cache
It there was a way to achieve the same from post_boot/init.d we could mount -o bind /cache/dalvik /data/dalvik-cache and all permissions issues would disappear as well as the need for symlink.
Click to expand...
Click to collapse
Let me try and do that right now... Ill get back to you if it does!
My script works on stock btw... But the mount way seems a bit easier and might cause less errors than my way.
Try it please.
skyguy126 said:
Let me try and do that right now... Ill get back to you if it does!
My script works on stock btw... But the mount way seems a bit easier and might cause less errors than my way.
Try it please.
Click to expand...
Click to collapse
Yes I've tried your script, all went well but the result is the same. The script itself works nicely btw
Applications present before moving cache work perfectly, but I can't install anything new. I suspect it might be my device but before wiping everything I'd prefer feedback from others :fingers-crossed:.
I cannot install new apps as well. The mount command you showed me has the same effect too. I honestly don't know anymore, the sym link did not allow the install of new apps nor did the mount command you sent me. Correct me if I am wrong.
Edit: Going through all the init files on my phone to see which one remounts /cache at boot.
Why does the init.rc get overwritten at boot. Is it because the kernel (boot.img) is the one that copies it over? I have found by changing the perms/locations in this file and init.target.rc you can achieve what this mod is trying to acomplish.
I don't see the mount cache command in CWM strange
I've managed to get back to normal, thanks for everyone's help though, I will keep and eye on the thread
Sent from my XT1032 using XDA Free mobile app
non-windows version?
Thanks for this tool. It's a great idea and our Motos really need it.
However, I have a problem - I do not own a windows license (os x and ubuntu user) and I would prefer not to spend $120 just to use it for this script. Pirating is out of the question for me.
I was wondering if there is any chance of having this script written for linux and/or mac. If impossible, is there a LEGAL way of running windows in a virtual machine? Something like a trial or similar?
If you know how just convert it to shell script for osx and Linux. I give you permission to do this but you may not take credit or rehost your creation.
Ok so I have the kernel extracted and we could modify and flash that, but I believe that it's not really necessary. There are a lot of risks to flashing kernels and I am not willing to take it. So is there a way we can modify dalvik so it creates it's cache in /cache instead.
skyguy126 said:
Why does the init.rc get overwritten at boot. Is it because the kernel (boot.img) is the one that copies it over? I have found by changing the perms/locations in this file and init.target.rc you can achieve what this mod is trying to acomplish.
Click to expand...
Click to collapse
Yes the init.rc is in the boot ramdisk. I don't think it would be worth the trouble to rebuild a boot.img. The moto g is fairly unbrickable but it's quite a lot of work to setup an environment to rebuild an image :/.
Too bad for the mount command, I was sure it was working but maybe I had changed something else and don't quite remember the steps to reproduce
We could possibly implement a shell script toggler for when we need to install new apps, but I'm afraid it'd become annoying fairly quickly: I noticed the issue initially because google play services decided to update itself, failed, and broke all google apps. As far as I know this autoupate can't be disabled.
Thanks for trying!
dd043 said:
Yes the init.rc is in the boot ramdisk. I don't think it would be worth the trouble to rebuild a boot.img. The moto g is fairly unbrickable but it's quite a lot of work to setup an environment to rebuild an image :/.
Too bad for the mount command, I was sure it was working but maybe I had changed something else and don't quite remember the steps to reproduce
We could possibly implement a shell script toggler for when we need to install new apps, but I'm afraid it'd become annoying fairly quickly: I noticed the issue initially because google play services decided to update itself, failed, and broke all google apps. As far as I know this autoupate can't be disabled.
Thanks for trying!
Click to expand...
Click to collapse
How about making a simple apk that toggles this feature. Something like when you click the icon it doesn't even open but gives a little notification of success. Something like that. I myself am not experienced with apks but I can put together a shell script for the apk.
skyguy126 said:
Ok so I have the kernel extracted and we could modify and flash that, but I believe that it's not really necessary. There are a lot of risks to flashing kernels and I am not willing to take it. So is there a way we can modify dalvik so it creates it's cache in /cache instead.
Click to expand...
Click to collapse
Patching dalvik itself sounds promising. It can probably be done with in a batch script with a command line hex editor.
The path is defined in frameworks/base/cmds/installd/installd.h
Code:
#define DALVIK_CACHE_PREFIX "/data/dalvik-cache/"
Not sure if there is another mention in the source tree.
But there's nothing to say we wouldn't face the same issue, the error message in the logcat is pretty generic
dd043 said:
Patching dalvik itself sounds promising. It can probably be done with in a batch script with a command line hex editor.
The path is defined in frameworks/base/cmds/installd/installd.h
Code:
#define DALVIK_CACHE_PREFIX "/data/dalvik-cache/"
Not sure if there is another mention in the source tree.
But there's nothing to say we wouldn't face the same issue, the error message in the logcat is pretty generic
Click to expand...
Click to collapse
Ill try it. I don't mind doing a bunch of resets because I am using my moto g as a test bench anyway. My daily driver is the OnePlus One
dd043 said:
Patching dalvik itself sounds promising. It can probably be done with in a batch script with a command line hex editor.
The path is defined in frameworks/base/cmds/installd/installd.h
Code:
#define DALVIK_CACHE_PREFIX "/data/dalvik-cache/"
Not sure if there is another mention in the source tree.
But there's nothing to say we wouldn't face the same issue, the error message in the logcat is pretty generic
Click to expand...
Click to collapse
EDIT: Unfortunately it didn't work. I don't know if I modified the installd file correctly. The program I used is HxD.
Is there a way we can force dalvik to start after the directories are created. And change dalvik to create it in /cache.

Fingerprint on Coolpad Note 3/Lite

Hello people,
Here is the procedure on how to use the following patch.
patch link
Firstly, paste the files their respective folders.
Then the following changes have to be done in init.mt6753.rc so as this patch would work.
1) init.trustonic.rc file in ramdisk
2) import init.trustonic.rc at the start of init.mt6753.rc
#add for fingerprint
chown system system /sys/bus/platform/devices/fpc_interrupt/irq
chown system system /sys/bus/platform/devices/fpc_interrupt/clk_enable
chown system system /sys/bus/platform/devices/fpc_interrupt/do_wakeup
chown system system /sys/bus/platform/devices/fpc_interrupt/wakeup_enable
#add for fingerprint
service fingerprintd /system/bin/fingerprintd
class late_start
class main
user system
service fastmmi /system/bin/fctd
socket fctd stream 666 root root
service mtk_fctd /system/bin/mtk_fctd.sh
oneshot
These, i found in init.rc and factory_init.rc of ramdisk, then flash the new bootimage.
wipe cache and data.
Now the fingerprint will work
Thanks to :
Dhruv Madaan for giving me the device
Shripal Jain for supporting me.
Hit thanks if you like my work.
Reserved.
Elaborate the instructions a lil more .
Hi firstly thanks for making this work . Can you please make instructions a lil more clear if possible with screen shots. Coz it's difficult to understand for me as am not from a software development background . Thank you you for the help
didnt understand ?
plz make video tutorial of this ,
cant understand
Nice work bro....Now we have got the most painful bug fix....I understood your guide easily....But here are many people who could not understand your guide as they just download the rom in ready to flash form and flash it....So u should edit your post and write that the people who didn't understand the guide should not do anything until and unless any rom with fp comes....
Thanks
I have a question, in the video 5 folders are shown in patch folder. But the downloaded one just has 4 and the "etc" folder is missing. Can someone help?
---------- Post added at 10:57 AM ---------- Previous post was at 10:50 AM ----------
AWEEEEEEEEEEEEEEEEEEEEEEEEESOME!!!!!!!!!!!!!!!!!!!!
Thank you thank you thank you thank you so very much.
After so many days now i can try out custom ROMS and finally get to nougat. It worked like a charm.
I am so much indebted by you.
Hats off Dev.
Bro where do this things has to be copied
In rom file or in root directory
Qnd also is this patch compatable with rr nougut
Fingerprint is working fine now with custom roms.

Categories

Resources