Database Users

[recovery hack] How to get back recovery 2e

Helo
I found a way to return to the recovery 2e
recovery 2e
Copying a file using the Root Explorer
# unzip and put archive contents in a folder called recovery2e on /sdcard/
# first mount -o remount,rw /system (important options in Root Explorer for do this)
# file recovery copy to /system/bin (and replace)
# xbi folder contents copy to /system/xbin/ (and replace)
Click to expand...
Click to collapse
Method by captive thanks buddy
# put archive contents in a folder called recovery2e on /sdcard/
# open a shell and get root (ADB or Terminal on Phone, type su and pres enter / accept )
# remount /system rw (busybox mount -o remount,rw /system)
# rename recovery in /system/bin to recovery3e (for backup purposes)
# copy "recovery" from /sdcard/recovery2e/ to /system/bin/ (cp /sdcard/recovery2e/recovery /system/bin/)
# copy the folder /sdcard/recovery2e/xbin/recovery to /system/xbin/ (cp -rr /sdcard/recovery2e/xbin/recovery /system/xbin/)
# enjoy!
Click to expand...
Click to collapse
Restart your phone

Isn't anyone going to comment on this?
Gurus: does it really work? That simple?
Thanks

Didn't work for me - used root explorer method. Now just hangs when I try to get recovery mode. Can get download mode ok still, and phone boots ok of course. Running JPM with root and voodoo5 3. Anything else to try?

Does not work on JPM....

it no works.
Phone: Doc's JP6 + voodoo pre3 + rooted
Method: Root explorer.
1, during copy the xbin folder to system, it shows "replace files" but after i check inside the system/xbin, the files are disappared??!! I did manually copy everything one after one from xbin to system/xbin, but i can't see where they are after copy.
2, anyway, i reboot the phone with 3b combo, the recovery mode still showing 3e.
so i say it no works. anyone tried the cable methed?

this thing work but it needs a little workaround as discussed by danzel. follow here: http://forum.xda-developers.com/showthread.php?t=774500&page=188

Could you please update the instruction for jp6 + voodoo pre4?
abd remount (don't know why) isn't working and /system is always ro so adb push and shell (adb shell works) cmd aren't working.
It is correct to remove su and busybox int the extracted folder since i have both already installed?

I was on JPM, followed the instructions.
Phone couldn't boot, lost ability to enter recovery. Luckily I could still enter Download mode, flashed to JPM, but being on voodoo kernel before that, didn't managed to disable lagfix before getting into this trouble - Couldn't revert back to RFS, and without ability to enter recovery to format.
Finally reverted back to Eclair firmware, could see my beloved recovery again. No way I'm going through the above again.
The above is just my own experience, for reference just in case someone is as unlucky as me.

This is the clear step on recovering the recovery2e
Recover recovery2 e
1. uncompress the downloaded file recovery 2e and copy the direcotry to sdcard and rename it to recovery2e
2. Using root explorer copy File recovery from recovery2e on sdcard to /system/bin
3. Using root explorer copy Folder recovery in xbin to /system/xbin
4. If did not work try copy xbin folder over /system/xbin folder

Ok, confirmed working for me on JPM+Voodoo.
I installed Rom Manager too, and CWM Recovery is fully working too!! TNX

xtrememorph said:
This is the clear step on recovering the recovery2e
Recover recovery2 e
1. uncompress the downloaded file recovery 2e and copy the direcotry to sdcard and rename it to recovery2e
2. Using root explorer copy File recovery from recovery2e on sdcard to /system/bin
3. Using root explorer Folder recovery in xbin to /system/xbin
Click to expand...
Click to collapse
Your method DO NOT work at all. I cannot enter recovery mode.
Fortunately download mode is still available.
JPM+Voodoo5 pre6

lagigia, what didn't work for you?
Here's what I did:
put archive contents in a folder called recovery2e on /sdcard/
open a shell and get root
remount /system rw (busybox mount -o remount,rw /system)
rename recovery in /system/bin to recovery3e (for backup purposes)
copy "recovery" from /sdcard/recovery2e/ to /system/bin/ (cp /sdcard/recovery2e/recovery /system/bin/)
copy the folder /sdcard/recovery2e/xbin/recovery to /system/xbin/ (cp -rr /sdcard/recovery2e/xbin/recovery /system/xbin/)
enjoy!

if using the root explorer method, copy xbin folder content, do not try to overwrite the entire dir on top.

mike.sw said:
if using the root explorer method, copy xbin folder content, do not try to overwrite the entire dir on top.
Click to expand...
Click to collapse
too late is there a way to solve it or get a step back?
thx!

i think u can just flash only the old kernel back and it will be fixed (only zimage).

captive said:
lagigia, what didn't work for you?
Here's what I did:
put archive contents in a folder called recovery2e on /sdcard/
open a shell and get root
remount /system rw (busybox mount -o remount,rw /system)
rename recovery in /system/bin to recovery3e (for backup purposes)
copy "recovery" from /sdcard/recovery2e/ to /system/bin/ (cp /sdcard/recovery2e/recovery /system/bin/)
copy the folder /sdcard/recovery2e/xbin/recovery to /system/xbin/ (cp -rr /sdcard/recovery2e/xbin/recovery /system/xbin/)
enjoy!
Click to expand...
Click to collapse
Thanks, works fine on JPM/JP6

Could we get a newbie friendly guide please. Get root. What does that mean and should i just type what you quoted. Thanks
Sent from my GT-I9000 using XDA App

Edited the first post and put the new, easy tutorial

Could i get some background on this, please?
Is it correct that:
1) recovery2e is the default samsung recovery?
2) new versions of recovery2e can't apply all the update.zip we were able to apply with the older versions? (unsigned, signed??)
3) This is why we need the old recovery2e to replace the new one?
4) Where did the issue started? Since Froyo releases?
5) Is this why we can't root Froyo FWs with an update.zip anymore like it was the case with Eclair?
I'm really sorry if this is kinda obvious but i never really saw any clear explanation about this. Hope someone could clear it up for me

1) Yes
2) Correct on recovery 2e you can't apply all the update.zip
4) Yes, New tutorial on fist post
4) The JPM ROM brings new recovery 3e
5) You can root phone by flash kernel with root by odni

[Q] How can I fix swype resolution on roto jme rom?

It doesn't fit the screen.. Pls help!
Sent from my GT-P1000 using Tapatalk

I bet there's already the solution somewhere on the forum, but Ill try to make it simple for u..
Basically u need to mount the factoryfs.rfs image of the JMK5 fw, on linux u can use the mount command tool, if on windows MagicISO would be the way to go. Once its mounted you need to copy the file Swype.apk from /app and libSwypeCore.so from /lib . Once you have them on ur computer all you have to do is to copy them into the Gtab, Ill post you the procedure step by step
Code:
adb shell
mount -o remount,rw -t rfs /dev/block/stl9 /system
chmod 777 /system/app
chmod 777 /system/lib
cd /system/app
mv Swype.apk Swype.apk.old
cd /system/lib
mv libSwypeCore.so libSwypeCore.so.old
exit
then from ur computer navigate to the folder where u have the files Swype.apk and libSwypeCore.so, then
adb push Swype.apk /system/app/
adb push libSwypeCore.so /system/lib/
adb reboot
Once it reboots you'll have the old nice Swype keyboard in replacement of the new small one...
To make it even easier I am uploading the files needed for the fix right below..
Enjoy ..

Nice! After I flashed Roto jme and discovered the swype issue, I reflashed the stock t-mo tom, grabbed those files, then reflashed Roto jme. Then I pushed those files and had the big keyboard back. Then I saw Mr. Roto made a v3b with the big keyboard! I could have been outside smoking a good cigar waiting for the upgrade!
So go get the v3b upgrade and flash that, unless you are looking for an adventure.
P.S. Reboot a few times if you do the file switching to make the changes take effect.

Well, unless you don't mind reflashing your tab and might lose apps and configurations this will take you few minutes. However I'm glad he has made a pre fixed keyboard version of the JME, defo easy way for everyone.
Sent from my GT-P1000 using XDA App

Segnale007 said:
To make it even easier I am uploading the files needed for the fix right below..
Enjoy ..
Click to expand...
Click to collapse
I suggest you take down those links before you get moderated!
See here.
Regards,
Dave

Segnale, you definitely want to remove those files from here. By the way the whole procedure can be done within the phone :
1. Download the files to your tab (before they are removed , ) using your browser
2. Use Androzip to unzip the files
3. Rename the original files of your tab with RootExplorer (just in case you want to reuse them)
4. Copy the downloaded unzipped files to their respective locations with RootExplorer
5. Reboot the system
P_

Or just flash the latest "update" from Rotohammer as it fixes the issue.

knightnz said:
Or just flash the latest "update" from Rotohammer as it fixes the issue.
Click to expand...
Click to collapse
But brings another one for us European users as his Swype only contains English & Spanish keyboards
Thanks a lot mate you saved my day.

some one help me pls?

can you help me with this module ??
make zip file who will work when i install in xrecovery?
Im noob and i dont know how to do it
http://forum.xda-developers.com/showthread.php?t=1135965

just follow the instruction, there's nothing complicated...

??
- push ax8mt.ko to /system/lib/modules
how to do it. ??

just cut/paste it there using root explorer, or whatever file manager ur using.

What I do is rename x8gesture.ko to x8gesture.bak from /system/lib/modules and then rename ax8mt.ko to x8gesture.ko and copy it to /system/lib/modules , reboot and it work like a charm, no push, pull or adb shell commands, GL!!!

Hmm well renaming will also work since x8gesture.ko is already ismoded in hwconfig, but this is not advisable.
Well ill explain it to you so that you will not have to rename any other modules in the future.
- push ax8mt.ko to /system/lib/modules - push means to move, copy or paste.
- run the following command phone terminal or adb on pc
Code:
insmod /system/lib/modules/ax8mt.ko - command to put the module in the system.
In your hwconfig.sh there is a line
insmod /system/lib/modules/x8gesture.ko that's why it works when you renamed ax8mt.ko

[***Guide***] Deodexing and Create your own custom rom and share it!

DEODEXING
must have all these
Download XUltimate
Busybox installed
Root
sdk tools
1. Connect tablet to computer
2. Start xUltimate, we will now get the required files from our phone to deodex and zipalign it which we will describe in the 3rd step.
3. On the main menu of xUltimate, type "deodex" in the main menu then choose option 5 (Pull and deodex all). Everything will be done for you here. Don't worry. You will see all your finished files in the folders 'done_app' and 'done_frame' which are located in the installation directory of xUltimate. If you have issues with the mobileprint.apk remove it and the mobileprint odex from /system/app/
4. move folders 'done_app' and 'done_frame' folders to your sdcard, you can find these folders in the directory of xUltimate as described in the previous step.
5. Make sure the sdcard is not mounted to pc anymore
6. Open Windows Command Prompt and type the following commands.
adb shell
su
stop
mount -o remount,rw /dev/block/stl12 /system
rm /system/app/*.odex
rm /system/framework/*.odex
busybox cp /sdcard/done_app/* /system/app/
busybox cp /sdcard/done_frame/* /system/framework/
chmod 644 /system/app/*
chmod 644 /system/framework/*
mount -o remount,ro /dev/block/stl12 /system
sync
reboot recovery
7. Now data and cache reset in the recovery menu...
8. reboot
Now How to Share and backup
1. download the backup script http://www.multiupload.com/OBLSBY5Z9E
2. extract the file and place in C:\Program Files\Android\android-sdk\platform-tools or where your sdk platform-tools folder is
3.open command prompt [run cmd prompt as administrator] type "cd C:\Program Files\Android\android-sdk\platform-tools" next press enter then type "backup" or where your platform-tools folder is [don't include ""]
4. the files for heimdall sharing will be in cd C:\Program Files\Android\android-sdk\platform-tools or where your platform-tools folder is also they will be on your sdcard
5. make sure when sharing you do a complete wipe you dont want to share your info
6.now lets get some roms posted!

Nice post, I was wondering how to do this just recently.

hi nice how to
i tried to download your backup script but the link is down.
can you please upload the backup script again
thanks

Wow thankss
Sent from my GT-P7500 using XDA Premium HD app

akenathon said:
Wow thankss
Sent from my GT-P7500 using XDA Premium HD app
Click to expand...
Click to collapse
CRC Studio | http://code.google.com/p/custom-rom-creator-studio/
The best rom cooking (windows) gui tool there is!
You can do this to with this gui tool and so much more...
Cheers

Thanks for the tips; but shouldn't this be in DEV or something..?
Well, that's where I would look to find such information... But I'm a noob.

Unable to deodex Phonesky.apk
as stated above, how to deodex Phonesky.apk?

I want to find way to create 3g with task v14 rom. Mybtab is gtab 10.1 3g p7500, but this rom doesnt support 3g.
Sent from my GT-P7510 using XDA Premium HD app

error msg
i try few times but always get this error, app`s is gove well and deodexed, from framework canot deodex following
android.policy
core
ext
framework
qcnvitems
services
Error occured while loading boot class path files. Aborting.
org.jf.dexlib.Util.ExceptionWithContext: Cannot locate boot class path file boun
cycastle.odex
at org.jf.dexlib.Code.Analysis.ClassPath.loadBootClassPath(ClassPath.jav
a:237)
at org.jf.dexlib.Code.Analysis.ClassPath.initClassPath(ClassPath.java:14
5)
at org.jf.dexlib.Code.Analysis.ClassPath.InitializeClassPathFromOdex(Cla
ssPath.java:110)
at org.jf.baksmali.baksmali.disassembleDexFile(baksmali.java:93)
at org.jf.baksmali.main.main(main.java:278)
The system cannot find the file specified.
any solutions? thanks in advance

[Guide] How to modify yourself system.img partition

Hi
in this thread i want to explain to everyone who want to modify (debloat, add app) to your system.img partition
First is necesary to:
-backup original system.img from your phone (make a copy to your hddpc, dvd, usb stick, disketes ... etc ... lool .. joking)
-injecting root to your system.img
this steps are explained here: http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
NOW: before copy and write the new rootedsystem.img image to your phone if you want to debloat or adding new app do this in your linux machine:
- mount again your new generated rootedsystem.img image
Code:
mount -o loop,rw -t ext4 rootedsystem.img operatingtable/
now browse mounted folder (operatingtable) and delete what you want from app or app-priv folder
if you want to delete startup phone sound delete from /media/audio/ui poweron.ogg and poweroff.ogg
in same mather you can add new app to app or app-priv folder but is necesary to chmod folders and files like this:
for new directories: chmod 0755 operatingtable/app/app-directory
for new files: chmod 0644 operatingtable/app/app-directory/app.apk
when you finish do this
Code:
umount operatingtable
and now you can copy and write to your phone rootedsystem.img image
as explained here: http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
PS: Of course this debloating could do directly from your phone after gained root with files managers ... but i think this method is easier.
PS2: If you debloated some apps (gapps ) ... Is necesary to restore factory settings because some updated apps are in /data/app folder ... or you can delete from there to.
Enjoy.

Is there a way to browse and edit an unrooted image? Does it have to be rooted to mount, browse and edit files? I'm asking because I am trying to edit build.prop only and I'm getting an error that says I'm not the owner. I copied the first command you posted, but I wasn't able to open the img. I had to drag the file into the terminal after the "ext4" to open the file, but I don't know what to do from there.
Sorry I"m a noob on linux

Hi, hope you're still active with this thread. I have a copy of system.img and I want to change a certain .apk inside /app. It is already mounted but when i try to chmod it says something like "changing permission is not permitted". Do you know how to fix this? Thanks!

aoprea said:
Hi
in this thread i want to explain to everyone who want to modify (debloat, add app) to your system.img partition
First is necesary to:
-backup original system.img from your phone (make a copy to your hddpc, dvd, usb stick, disketes ... etc ... lool .. joking)
-injecting root to your system.img
this steps are explained here: http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
NOW: before copy and write the new rootedsystem.img image to your phone if you want to debloat or adding new app do this in your linux machine:
- mount again your new generated rootedsystem.img image
Code:
mount -o loop,rw -t ext4 rootedsystem.img operatingtable/
now browse mounted folder (operatingtable) and delete what you want from app or app-priv folder
if you want to delete startup phone sound delete from /media/audio/ui poweron.ogg and poweroff.ogg
in same mather you can add new app to app or app-priv folder but is necesary to chmod folders and files like this:
for new directories: chmod 0755 operatingtable/app/app-directory
for new files: chmod 0644 operatingtable/app/app-directory/app.apk
when you finish do this
Code:
umount operatingtable
and now you can copy and write to your phone rootedsystem.img image
as explained here: http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
PS: Of course this debloating could do directly from your phone after gained root with files managers ... but i think this method is easier.
PS2: If you debloated some apps (gapps ) ... Is necesary to restore factory settings because some updated apps are in /data/app folder ... or you can delete from there to.
Enjoy.
Click to expand...
Click to collapse
Can i do this thing with xiaomi mi 5.