Recovery Question - Flipside General

How can I pull the recovery out of laidaxin's rom and install it so I can use that?
Sent from my MB508 using Tapatalk

Just extract the zip file and copy the relevant files over to your phone, it's pretty straightforward.

I tried that and now can no longer get into any recovery... the led light never lights up... did I miss something?
Sent from my MB508 using Tapatalk

Sounds like it... I used the 2nd_init installer, then copied over /system/bootmenu/* and /system/bin/boootmenu
There's an installer in /system/bin, you may want to run these commands:
rm -f /system/bin/logwrapper
rm -f /system/bin/logwrapper.bin
cp /system/bootmenu/binary/logwrapper.bin /system/bin/
ln -s /system/bin/bootmenu /system/bin/logwrapper

You never mentioned /system/bin/bootmenu
Sent from my MB508 using Tapatalk
Ok... I put everything in the directory it belongs in... and fixed the permissions to get it to run
However... if I don't boot to recovery... my phone gets hung up after the led light goes out and have to pull the battery... upon reboot it boots without going into recovery without giving me the option

Related

[EXPERIMENTAL]-PROJECT JIT-(Just in time)EXPERTS ONLY |Aug 13th|

New as of Saturday August 8th
I will update the files every time I find a problem​
WARNING PLEASE READ:
Project JIT is highly highly experimental! If you are to do this, MAKE A NANDROID BACKUP IN ROM MANAGER OR RECOVERY! There are always chances of something going wrong. I nor anyone else is responsible of what happens.
Experienced users please know the possible risks:
Boot Looping, requiring a restore
Constant FC's
Wiping everything
These are just the risks, please note it is not 100%​
JIT stands for Just in time compiler. It does not like Touchwiz, so download ADW.Launcher or LauncherPro before starting and set it as default.
This whole process is in ADB. If you dont know how, or what it is, DONT DO IT!
Things to do before you start:
-Download a different launcher than TouchWiz
-Make a backup in recovery or Rom Manager
-Did I mention DO A BACKUP!
-If you have an external SD card, pull it out
-Download the vmlibs file
What I expect you to know before you start:
-ADB
-What JIT is
-How this will effect the performance
-The risks
-How its not my fault if you screw your phone over
-How experimental this is
-How to make a nandroid backup
-How to make a nandroid restore
Remember, this is experimental and I cannot guarantee for it to completely work.
Download This- vmlibs.zip
Then follow these steps:
-Make a backup!!!
-Create 2 folders on your internal sdcard: “jit” & “dalbk”
-Extract the vmlibs.zip to the “jit” folder on your sdcard
-Using ADB pull your build.prop
Code:
adb remount
ADB pull /system/build.prop build.prop
-It will place the file in your c:/android/tools folder
-Edit this using notepad, text edit or similiar program.
-Add the following line to the end of the build.prop: dalvik.vm.execution-mode=int:jit
-Edit the following line:dalvik.vm.startheapsize=8m
to: dalvik.vm.startheapsize=12m
-Save the changes
-Push it back to your “jit” folder on the sdcard
Code:
ADB push build.prop /sdcard/jit/build.prop
This will back up your current files. So you can disable jit, but if your phone boot loops, thats why you have A BACKUP!
Code:
ADB shell
su
cp /system/build.prop /sdcard/dalbk/
cp /system/bin/dalvikvm /sdcard/dalbk/
cp /system/lib/libdvm.so /sdcard/dalbk/
cp /system/lib/libnativehelper.so /sdcard/dalbk/
This will enable jit on your phone.
Code:
cd /sdcard/jit/bin
cp -f dalvikvm /system/bin/
busybox chmod 755 /system/bin/dalvikvm
cd /sdcard/jit
cp -f libdvm.so /system/lib/
cp -f libnativehelper.so /system/lib/
cat build.prop >/system/build.prop
chmod 644 /system/lib/libdvm.so
chmod 644 /system/lib/libnativehelper.so
chmod 666 /system/build.prop
sync
reboot recovery
While in recovery, wipe the dalvik cache, this will prevent it from boot looping.
To Disable
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /sdcard/dalbk/
cat build.prop >/system/build.prop
cp -f dalvikvm /system/bin
busybox chmod 755 /system/bin/dalvikvm
cp -f libdvm.so /system/lib/
cp -f libnativehelper.so /system/lib/
chmod 644 /system/lib/libdvm.so
chmod 644 /system/lib/libnativehelper.so
chmod 666 /system/build.prop
sync
reboot
If that fails, that is why you have a backup. To restore, go to recovery, click on nandroid, and restore from your backup.
Reserved for future posting
Will this work with the sd card cache hack?
Sent from my SAMSUNG-SGH-I897 using XDA App
LGSilva said:
Will this work with the sd card cache hack?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
It didn't here. Not sure if that is due to other fsckup or the fact that I was running I9k rom with my kernel and sdcard hack...
Restoring to stock to give this a whirl
tommarow I will update the vmlibs file and see if it works better.
Oh, and tell me what your problems are
hansmrtn said:
tommarow I will update the vmlibs file and see if it works better.
Oh, and tell me what your problems are
Click to expand...
Click to collapse
Doesn't boot past the white at&t screen. Again, I was running I9k rom with custom kernel and ext hack, not exactly the cleanest test bed. Flashing stock to test now (can't get into recovery on this thing anyway it seems).
NukaCola said:
Doesn't boot past the white at&t screen. Again, I was running I9k rom with custom kernel and ext hack, not exactly the cleanest test bed. Flashing stock to test now (can't get into recovery on this thing anyway it seems).
Click to expand...
Click to collapse
Hold on. Before you do that, let me up the file.
EDIT:
Here is the updated one, its in the first post too
It should work better. I used it just now, and it works for me
hansmrtn said:
Hold on. Before you do that, let me up the file.
EDIT:
Here is the updated one, its in the first post too
It should work better. I used it just now, and it works for me
Click to expand...
Click to collapse
Too late
Same story with the stock rom and old file, just FYI. Flashing back and trying the new one.
NukaCola said:
Too late
Same story with the stock rom and old file, just FYI. Flashing back and trying the new one.
Click to expand...
Click to collapse
Yeah, thats why I had to fix some stuff lol. I noticed that it wouldnt go past the att screen. Now it should work correctly. The worst that could happen now is it boot loops on the Galaxy S screen
Haha I was just about to post the same problem, downloading new file and trying it again!
Zilch25 said:
Haha I was just about to post the same problem, downloading new file and trying it again!
Click to expand...
Click to collapse
Hey, when you edit the build.prop to add the dalvik vm line, can you look for the vm heap size and change it from 48 to 32? I am about to test doing that, and I would like more feedback
Doh, didn't read this until after applying it all... it's in the process of booting though- it got past the AT&T logo so that's progress!
Zilch25 said:
Doh, didn't read this until after applying it all... it's in the process of booting though- it got past the AT&T logo so that's progress!
Click to expand...
Click to collapse
Dont worry, I will try it
ATM I'm now stuck sitting at the GalaxyS logo, I'm going to give it a little more time, but I suspect it might be stuck.
Zilch25 said:
ATM I'm now stuck sitting at the GalaxyS logo, I'm going to give it a little more time, but I suspect it might be stuck.
Click to expand...
Click to collapse
Do you know how to run a logcat?
Its gonna take a while because its re writing the dalvik cache
That I do not, but I'm willing to try it if you can give me a quick crash course
Zilch25 said:
That I do not, but I'm willing to try it if you can give me a quick crash course
Click to expand...
Click to collapse
Well I am looking at my logcat now, and it is just repeating boot animation.
A logcat is useful, so how you do it is adb logcat.
I changed a couple things to test around with here is what I did-
I added all of this to the build.prop-
#JIT
dalvik.vm.execution-mode=int:jit
and changed:
dalvik.vm.heapsize=48m
to
dalvik.vm.heapsize=32m
Right now I am resorting to try the older vmlibs with the new settings
Ran logcat, it's also trapped at looping animation, and I didn't touch the heapsize
W/BootAnimationSEC< 2194: ms4631 - Repeat Loop Animation
Over and over and over, is there something else in the buffer you'd like me to look for?
Zilch25 said:
Ran logcat, it's also trapped at looping animation, and I didn't touch the heapsize
W/BootAnimationSEC< 2194: ms4631 - Repeat Loop Animation
Over and over and over, is there something else in the buffer you'd like me to look for?
Click to expand...
Click to collapse
No thanks for the feedback. Its only worked for me once, and then when I rebooted it got stuck in a boot loop.
Whats a device thats running android 2.1, and has a jit hack that is extremely similar to the Galaxy S series?

deodex file

Hi guys
I'd manage to manually deodex the app and framework file from my stock rom. The problem are I can't push them either thru adb nor update.zip. Been googling around but can't really get a correct adb command for sgs. I need to push these files so that I can install themes. Anybody who can guide please help. Thanks in advance.
You need super user permission to push things into read only memory. So you would need to go through adb shell, mount whatever folder framework is in to readable, etc.
snapper.fishes said:
You need super user permission to push things into read only memory. So you would need to go through adb shell, mount whatever folder framework is in to readable, etc.
Click to expand...
Click to collapse
Hi snapper.fishes
By the way, I got superuser permission. The only problem I don't know the correct command for the adb shell - su - mount etc, etc....
This are the command I got from Droid forum but it does not work for SGS I guest.
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Anybody got any idea?
Try this:
adb shell
su
mount -o rw,remount /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount /system
reboot
Sent from my GT-I9000 using XDA App
g00ndu said:
Try this:
adb shell
su
mount -o rw,remount /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount /system
reboot
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Thanks for the tips g00ndu. If I push those deodex file, they will overide and delete all the odex file right? Should I disable the universal lagfix first and is it safe pushing deodex file this way?
angiogram said:
Thanks for the tips g00ndu. If I push those deodex file, they will overide and delete all the odex file right? Should I disable the universal lagfix first and is it safe pushing deodex file this way?
Click to expand...
Click to collapse
I say remove the lagfix first. It's not necessary, but if you do screw up your phone you are going to have to reflash your phone, and the last thing you want to do is to flash your phone with lagfix on.
angiogram said:
Thanks for the tips g00ndu. If I push those deodex file, they will overide and delete all the odex file right? Should I disable the universal lagfix first and is it safe pushing deodex file this way?
Click to expand...
Click to collapse
It's been a long time since I pushed files this way. Right now I'm using update zips and flash it via ulfk. Reason: it is much more simpler and more effective. If I remember correctly, your apk files need to be deleted too before you can push your deodexed apks and jars files to the system folder if you do it via adb.
Besides, I would not advocate this method of pushing through adb, bcos, there is always chances that your /system, /data partitions may result in data corruption.
Try using update zip.
Sent from my GT-I9000 using XDA App
g00ndu said:
It's been a long time since I pushed files this way. Right now I'm using update zips and flash it via ulfk. Reason: it is much more simpler and more effective. If I remember correctly, your apk files need to be deleted too before you can push your deodexed apks and jars files to the system folder if you do it via adb.
Besides, I would not advocate this method of pushing through adb, bcos, there is always chances that your /system, /data partitions may result in data corruption.
Try using update zip.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Thanks for your reply g00ndu. I've already try that. But after the zip file updated nothing happen. Maybe the zip creator that I use is not compatible with sgs. Can you kindly link to the correct source for sgs. Or maybe you can post the file and tutorial here so that we can learn the correct method from you. Thank you so much for that.
Anybody can help?
Deodexing Your Device - Full Step By Step Tutorial
angiogram said:
Hi guys
I'd manage to manually deodex the app and framework file from my stock rom. The problem are I can't push them either thru adb nor update.zip. Been googling around but can't really get a correct adb command for sgs. I need to push these files so that I can install themes. Anybody who can guide please help. Thanks in advance.
Click to expand...
Click to collapse
angiogram said:
Thanks for your reply g00ndu. I've already try that. But after the zip file updated nothing happen. Maybe the zip creator that I use is not compatible with sgs. Can you kindly link to the correct source for sgs. Or maybe you can post the file and tutorial here so that we can learn the correct method from you. Thank you so much for that.
Anybody can help?
Click to expand...
Click to collapse
Hey angiogram... I'm not sure if this thread still has a pulse, but I came across this thread and feel confident I can offer you some great information.
g00udu was on the right track, only one small detail I would add is reverting the permissions back to the system files once returned to the system directory.
See this link http://forum.xda-developers.com/showthread.php?t=990238
for an extremely detailed step by step how to perform this process from beginning to end.
If this issue has been resolved, keep it for future reference or pass it on to someone who you believe it may help.
Peace-
Thanks Liv33vil.
Sent from my GT-I9000 using XDA Premium App

Help ADB Push to /System Folder

Hope this is the right place to post this.
My Atrix is rooted stock 1.83 .
I'm trying to "adb push" some OGG files to "/system/media/audio/" to add-to and replace some of the existing system sounds, especially that bloody annoying keypress (typewriter) sound, but I'm getting the following error (which makes sense):
Read-only file system
Tried using Root Explorer, same issue...again makes sense since its mounted as Read only on boot.
I tried booting into recovery mode, but I can't access the phone via ADB at all, even with USB Debug enabled. I also tried "adb remount" command, no luck either. I get an error "operation not permitted".
So, does anyone know the correct sequence of commands I need in ADB to remount the Atrix /system folder as RW??
What I have been doing is using adb push to the /sdcard then using adb shell then su then
mount -t rfs -o remount,rw /dev/stl5 /system
Then cp /sdcard/whatever /system/media
Sent from my MB860 using XDA App
EDIT: im at my computer now so I can write this easier to understand, lol
Lets say the file you want to change is called whatever.ogg
Code:
adb push whatever.ogg /sdcard/whatever.ogg
adb shell
su
mount -t rfs -o remount,rw /dev/stl5 /system
cp /sdcard/whatever.ogg /system/media/audio/notifications
when you access root explorer, does it let you know that it has been granted supervisor privilages? Does it give you the option to change from read to write? what did you use to root? I had to run the original Aroot three times before if finally gave me root.
You're the best, worked perfectly Can't believe that hideous typewriter sound is gone, it only took me 1.5 years as an Android user to finaly say enough is enough. Whomever thought it was a good idea to mimic the sound of an 1800's typewriter on a 21st century device needs to be fired.
Thanks again.
aver2one said:
What I have been doing is using adb push to the /sdcard then using adb shell then su then
mount -t rfs -o remount,rw /dev/stl5 /system
Then cp /sdcard/whatever /system/media
Sent from my MB860 using XDA App
EDIT: im at my computer now so I can write this easier to understand, lol
Lets say the file you want to change is called whatever.ogg
Code:
adb push whatever.ogg /sdcard/whatever.ogg
adb shell
su
mount -t rfs -o remount,rw /dev/stl5 /system
cp /sdcard/whatever.ogg /system/media/audio/notifications
Click to expand...
Click to collapse
i need help
im using a clone samsung galaxy tab2.tried to change the system font with root browser and it bricked.the phone dont have cwm so i didnt back up my rom.any command in adb that can be used to change the font folder
Obiechina said:
im using a clone samsung galaxy tab2.tried to change the system font with root browser and it bricked.the phone dont have cwm so i didnt back up my rom.any command in adb that can be used to change the font folder
Click to expand...
Click to collapse
Well congrats! that was the dumbest thing ever. NEVER attempt something like that unless you have CWM or equivalent installed, have a backup, and know what you are doing.
Have you tried to read your device's xda forum?
Please Help
Hahaha, can you help me?
i want to change my /system/framework folder by using the POWER and UP volume keys
i had a backup of my system/framework in my SD..
What should i do?

[MOD] [LG P500] CRT Screen Off for Optimus One

Hello All.
Here are the framework-res.apk and build.prop files for the Optimus One, Stock 2.3.3 firmware. All you need to do is replace those files and you will get the CRT ScreenOff effect
I used the post by Skynet28, modified a little to only use adb commands.
This was the first thing done after rooting the phone.
-NEEDED:
Rooted phone
.7Z file View attachment 949259
5 Minutes of your time
NOTE: YOU WILL MOST PROBABLY LOOSE YOUR PHONEBOOK, I DID WHILE DOING ALL THIS. PLEASE BACK THAT UP.
The procedure to install is as follows:
You must set the /system on the phone with RW permision
From a Command Prompt:
First we locate where /system is mounted
Code:
adb shell
su
cat /proc/mounts
Locate /system in the mount and write down the mountpoint (mtdblock1 or similar)
the type
Code:
mount -o rw,remount /dev/block/[I][COLOR="Purple"]MOUNTPOINT[/COLOR][/I] /system
exit
exit
Then we push both files to the phone with the folowing adb command
Code:
adb push framework-res.apk /system/framework
adb push build.prop /system
Finally we chmod those 2 files
Code:
adb shell
su
cd /system/framework
chmod 664 framework-res.apk
cd /system
chmod 664 build.prop
exit
exit
Thanks to this post
http://forum.xda-developers.com/showthread.php?t=1185231
If you like this post, buy me a beer!!
Does it workss ???????? Reply anyone
Do you lose contacts on phone or sim?
Kvidli said:
Do you lose contacts on phone or sim?
Click to expand...
Click to collapse
I Brickked my fone.. STUCK ON ANDROID LOGO !!
stupid post! not working..
chrisdf said:
Hello All.
Here are the framework-res.apk and build.prop files for the Optimus One, Stock 2.3.3 firmware. All you need to do is replace those files and you will get the CRT ScreenOff effect
I used the post by Skynet28, modified a little to only use adb commands.
This was the first thing done after rooting the phone.
-NEEDED:
Rooted phone
.7Z file View attachment 949259
5 Minutes of your time
NOTE: YOU WILL MOST PROBABLY LOOSE YOUR PHONEBOOK, I DID WHILE DOING ALL THIS. PLEASE BACK THAT UP.
The procedure to install is as follows:
You must set the /system on the phone with RW permision
From a Command Prompt:
First we locate where /system is mounted
Code:
adb shell
su
cat /proc/mounts
Locate /system in the mount and write down the mountpoint (mtdblock1 or similar)
the type
Code:
mount -o rw,remount /dev/block/[I][COLOR="Purple"]MOUNTPOINT[/COLOR][/I] /system
exit
exit
Then we push both files to the phone with the folowing adb command
Code:
adb push framework-res.apk /system/framework
adb push build.prop /system
Finally we chmod those 2 files
Code:
adb shell
su
cd /system/framework
chmod 664 framework-res.apk
cd /system
chmod 664 build.prop
exit
exit
Thanks to this post
http://forum.xda-developers.com/showthread.php?t=1185231
If you like this post, buy me a beer!!
Click to expand...
Click to collapse
You cant use this on anything but stock LG 2.3.3!
That means Cyanogenmod, AOSP, etc
kunnaliskinng said:
I Brickked my fone.. STUCK ON ANDROID LOGO !!
stupid post! not working..
Click to expand...
Click to collapse
Flash stock v20g using KDZ then root and do what this post says right away, i assure you it works.
This is only for STOCK 2.3.3
Kvidli said:
Do you lose contacts on phone or sim?
Click to expand...
Click to collapse
On your phone, but if you have it linked to your gmail account, when you sinc you will have them back.
you should still back up anyway, its safer that way
Only stock Rom
I want use on oxygen Rom .
Sent from my LG-P500 using Tapatalk 2
Are there any available screenies?
doesn't work for me..
kotobodj said:
Only stock Rom
I want use on oxygen Rom .
Sent from my LG-P500 using Tapatalk 2
Click to expand...
Click to collapse
If you want it on any GB Rom, follow the tutorial i followed, check at the end of the post there's a link.
kunnaliskinng said:
I Brickked my fone.. STUCK ON ANDROID LOGO !!
stupid post! not working..
Click to expand...
Click to collapse
i think nothing to angry for this. just read carefully before do anything :laugh:
)
cool!)

Better way ???

What is better way to unroot you S4 on MF3 Odin back to stock MF3 or by SU full unroot?
It'll somewhat depend on why you want to remove root. But I've always used odin. You will lose all your apps this easy though. I've never tried using unroot inside super su and don't know if it leaves somethings behind.
Personally, I like to make sure everything is completely gone by doing the following:
First remove Safestrap via ADB:
Code:
su
mount -o remount,rw /system
mv /system/etc/init.qcom.modem_links.sh.bin /system/etc/init.qcom.modem_links.sh
rm -rf /system/etc/safestrap
rm /system/etc/firmware/q6.mdt
ln -s /firmware/image/q6.mdt /system/etc/firmware/q6.mdt
mount -o remount,ro /system
Then, remove SU & Busybox via Root Explorer:
1. Navigate to /system/xbin
2. Delete busybox and SU
3. Naviate to /system/bin
4. Delete SU
5. Uninstall Superuser from the Applications Menu
Finally, nuke the entire thing by ODINing back to MF3 stock with this:
http://forum.xda-developers.com/showthread.php?t=2502003
You really only need to do the last step, but I always like to be extra safe.
jd1639 said:
It'll somewhat depend on why you want to remove root. But I've always used odin. You will lose all your apps this easy though. I've never tried using unroot inside super su and don't know if it leaves somethings behind.
Click to expand...
Click to collapse
One of my friends want to get back to stock with out root so he can push last update tru ADB. He is not using anything what required root but he rooted his phone..Also he want to keep his settings on phone.
jdisco1 said:
Personally, I like to make sure everything is completely gone by doing the following:
First remove Safestrap via ADB:
Code:
su
mount -o remount,rw /system
mv /system/etc/init.qcom.modem_links.sh.bin /system/etc/init.qcom.modem_links.sh
rm -rf /system/etc/safestrap
rm /system/etc/firmware/q6.mdt
ln -s /firmware/image/q6.mdt /system/etc/firmware/q6.mdt
mount -o remount,ro /system
Then, remove SU & Busybox via Root Explorer:
1. Navigate to /system/xbin
2. Delete busybox and SU
3. Naviate to /system/bin
4. Delete SU
5. Uninstall Superuser from the Applications Menu
Finally, nuke the entire thing by ODINing back to MF3 stock with this:
http://forum.xda-developers.com/showthread.php?t=2502003
You really only need to do the last step, but I always like to be extra safe.
Click to expand...
Click to collapse
Friend of mine don't have SafeStrip on his phone. BTW you can remove last version of SS with appication manager.
2nd step will remove will remove root and leave the rest of the OS intact. I think SU full unroot leaves busybox behind, and you cant delete it without root.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
jdisco1 said:
2nd step will remove will remove root and leave the rest of the OS intact. I think SU full unroot leaves busybox behind, and you cant delete it without root.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
cool thanks..

Categories

Resources