Related
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
See my previous post before in post#2
This is a simple batch file using ADB..
With this you can use ADB to manage your file or APK , Backup, Push Your File to device, or pull file from device..
ADB Work on Stand by Mode (Home Screen) or in Recovery Mode, just set it up..
Extract ADBTOOLSv1.0.1.zip and you will find :
command.bat : Windows Batch Command
_BACKUP_OUT : folder where your backup process done and made
_FLASHING_OUT:
folder for flashing your :
kernel (place your boot.img here)
recovery (place your recovery.img here),
modem (place your modem.bin here)--only for gt p7300
_MODDING_FILE: Folder where your file were created by PULL process
Folder where file for PUSH process should be here
_BATCH_INSTALL : place your APK here for batch install
tools: ADB.exe and busybox binary
success_APK : A folder created for All apk from _BATCH_INSTALL move here after instalation.
Click to expand...
Click to collapse
Notes:
ADB can access all file from device from CWM Recovery, especially CWMR 5.5.0.4
ALL you need to do is:
From Recovery menu, you need to mount /data and /system for ADB working..
THEN, From Command Prompt set ADB Mode to "recovery".(This Batch File set ADB mode to "Home Screen" by default)
So when you use ADB from Online device ( I mean a stand by device).. you dont need to change ADB Mode..
After you set up, you can use ADB as you like..
Code:
=============================================================================
:::: ADB TOOLS FOR GT P7300 and P7310 by suwandiapr
-----------------------------------------------------------------------------
| [*] Before use read this:
| --make sure you have installed adb drivers for your device
| --enable "USB DEBUGGING"
| from (Menu\Settings\Applications\Development)
| --enable "UNKNOWN SOURCES"
| from (Menu\Settings\Applications)
| --increase screen timeout to 10 minutes
| --connect USB cable to PHONE and then connect to PC
| --MAKE SURE YOU HAVE A ROOTED DEVICE AND BUSYBOX
| --Place the right file in the right folder
| --Some feature like Flashing need more tester..so please be aware
| --If you use adb recovery feature, set ADB Mode to recovery
| mount /data and /system from your device recovery
| --If you use adb from homescreen, set ADB Mode to HomeScreen
| --All you Do is your own Risk, use with carefull
-----------------------------------------------------------------------------
****Turn on the screen and allow superuser permission when asked!****
_____________________________________________________________________________
| Current MODDING FILE: NONE | ADB MODE :HomeScreen | sdcard path: /sdcard/|
=============================================================================
:::: ADB PULL ::::
=============================================================================
0 Pulling file from /data ( see result in _MODDING_FILE)
1 Pulling file from /system partition ( see result in _MODDING_FILE)
2 Pulling file from SDcard ( see result in _MODDING_FILE)
3 Backup recovery ( see result in _BACKUP_OUT)
4 Backup Kernel ( see result in _BACKUP_OUT)
5 Backup modem (for P7300 only-see result in _BACKUP_OUT)
6 Backup /system (tar format-see result in _BACKUP_OUT)
7 Backup /efs (tar and .img format-see result in _BACKUP_OUT)
8 Backup APK from /data/app (tar format-see result in _BACKUP_OUT)
=============================================================================
:::: ADB PUSH ::::
=============================================================================
9 Pushing file to /data ( from _MODDING_FILE to device)
10 Pushing file to /system ( from _MODDING_FILE to device)
11 Flashing recovery ( from _FLASHING_OUT to device)
12 Flashing Kernel ( from _FLASHING_OUT to device)
13 Flashing modem for GT P7300 ( from _FLASHING_OUT to device)
=============================================================================
:::: Setting ::::
=============================================================================
14 Set current working File ( for PUSH and PULL )
15 Install busybox on device (need root)
16 Set ADB mode (if you on recovery mode)
17 Install apk ( from _MODDING_FILE to device)
18 Install batch apk ( from _BATCH_INSTALL to device)
=============================================================================
:::: Reboot Menu ::::
=============================================================================
19 Reboot System
20 Boot Into Recovery
21 Reboot Bootloader
22 Quit
My previous post
inspiration from congox case
when you got a problem with bootlop and you forget make a nandroid backup
only have file from other ROM with flashable.zip and need to push the file from your computer to device
you have a recovery support with mount /system and mount /data (tested on CWM 5.5.0.4 and overcome CWM 5.1.2.6) and you can enter this menu while bootloop happen..
STEP 1 : MANUAL
Connect your device with computer
From device, Go to recovery - mounts and storage - mount /system and mount /data
From your computer go to adb terminal and type this
Code:
adb shell "ls /data/media/"
If you can see list of file from your device sdcard, so you make adb work for your device ..
Place your zip file on your path, says on C://backup.zip and you want to copy the file to /sdcard/download/ and type this code
Code:
adb push backup.zip /data/media/download/.
wait for copying progress done..
After you done with moving file to device sdcard, check content of your sdcard with this code
Code:
adb shell "ls /data/media/download/"
When you found your file from list, you can flash backup.zip from recovery
STEP 2 : WINDOWS BATCH FILE
I made a simple Batch File for windows (sorry i dont have MAC or LINUX distro) , this file will make a folder with name "emergency" in SDCARD and with your files inside that.
Extract the FLASHER.rar somewhere on your Local folder,example: on your " Desktop" Folder
in folder "FLASHER" you will find runme.bat and folder "files"
Rename your file ((flashable.zip files you want to send through ADB) to "backup.zip" and then Put your file into this path /FLASHER/files/myfiles/ (just replace the existing "backup.zip" with files from yours)
Connect your tab with Computer
Reboot into Recovery Menu from your device
From menu Mounts and Storage choose mount /system and /data
From your Computer go To Folder flasher and klik runme.bat
Follow the instruction on window untill copying process done and device reboot to recovery again (copying process will take a minutes depend on your file size)
Now you can flash a emergency ROM from recovery
Window instruction
Code:
-----------------------------------------------------------------------------
ADB EMERGENCY COPYING TOOL for TAB 8,9
created by SUWANDIAPR
-----------------------------------------------------------------------------
[*] This script will:
(1) COPY YOUR FILE FROM COMPUTER TO SDCARD/emergency/*
(2) CHECKING YOUR CONNECTED DEVICE DIRECTORY
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) make sure u have installed CWM 5.5.0.4 ON YOUR DEVICE
(3) connect USB cable to PHONE and then connect to PC
(4) Rename your Flashable .zip file with "backup.zip"
and place inside "myfiles" folder on your Computer
(5) from Recovery Menu, Choose "Mounts and storage" then
-mount /system and -mount /data
(6) CONNECT YOUR TAB WITH PC WHILE ON RECOVERY MENU
---------------------------------------------------------------
CONFIRM ALL ABOVE
Sorry for my Bad english, if there is somebody want to correct every words i use , im very welcome and will change with the proper words and sentence..
Hope this help someone..
Nice guide, thanks!!
I needed some help with mounting the system using adb through a batch file.
I use this command
adb -d shell mount -o remount rw /system
But the mounting fails (I have a rooted phone )
pleas help me I know this is off topic
2 possible reasons for this command to fail:
- /default.prop (on the phone) contains the following line: "ro.secure=1". Then you need another boot.img (in fact just a modified ramdisk). look for "unpack-bootimg.pl" or "unpackbootimage" you may find a guide how to do this manually (not too easy). A rooted kernel would also do the trick.
you can check your default prob with this command "adb shell cat /default.prop".
- in some cases mount requires more parameters. try "adb shell mount" and look for the line containing "/system". In front of system is the "device-name". in my case the mount command would look like this:
mount -o remount,rw /block/dev/mmcblk0p24 /system
hope this helps and sorry for answering off-topic questions....
nail16 said:
I needed some help with mounting the system using adb through a batch file.
I use this command
adb -d shell mount -o remount rw /system
But the mounting fails (I have a rooted phone )
pleas help me I know this is off topic
Click to expand...
Click to collapse
you can use busybox and call the binary from the shell
i assume that your device in normal mode ( in home screen)..
here some example..
Code:
su
adb push busybox /tmp/.
adb shell "chmod 755 /tmp/busybox"
adb shell "tmp/busybox mount -o remount,rw /system"
after you type "su" superuser will prompt a request, choose "allow".
glitschi667 said:
2 possible reasons for this command to fail:
- /default.prop (on the phone) contains the following line: "ro.secure=1". Then you need another boot.img (in fact just a modified ramdisk). look for "unpack-bootimg.pl" or "unpackbootimage" you may find a guide how to do this manually (not too easy). A rooted kernel would also do the trick.
you can check your default prob with this command "adb shell cat /default.prop".
- in some cases mount requires more parameters. try "adb shell mount" and look for the line containing "/system". In front of system is the "device-name". in my case the mount command would look like this:
mount -o remount,rw /block/dev/mmcblk0p24 /system
hope this helps and sorry for answering off-topic questions....
Click to expand...
Click to collapse
yes you right glistchi, samsung lock adb root on new firmware on my SG- Note..
And make me flash an older firmware for rooting..
new update
Never mind, got it to work
i want to push same file in data system (/data/data) but my tab is not root. can i??
if from cwm recovery, yes you can.. if from stand by mode (home screen) the answer is no... you need root to make it happen..
i got this error
please help
Hi all,
I have managed to deodex and zipalign my rooted I8190XXALL2_I8190OXXALL1 ROM in my smartphone, so thought i would share it here.
Follow all the instructions carefully. I will not be held responsible in any manner if your smartphone doesn’t boot up or gets bricked due to not following the instructions.
Please make sure -
1. Your smartphone is already rooted (flash one of the rooted rom's founded here)
2. Download and install Busybox Installer latest version.
3. Make sure you already have Java SE Development Kit and Android SDK installed on your computer.
Install them to the default choice on the C: drive.
4. You should also have a basic knowledge of ADB.
Required Downloads -
1. xUltimate version 2.4.2 – Link. You may have to Google for the correct version to download. Extract it to C:\xUltimate-v2.4.2.
Instructions –
1. Connect your smartphone to your computer. (Make sure you have selected USB debugging in Settings>Applications>Development)
2. Open a command prompt as administrator. Wait for Window to appear.
3. Change Directory to C:\xUltimate-v2.4.2
4. Launch main.exe.
5. If everything goes well xUltimate should recognize the smartphone and make a connection. You should now see a list of options.
6. Select option (1) pull /system/app. Wait until it completes.
7. Select option (2) pull /system/framework. Wait until it completes.
8. Then select option (3) Deodex /system/app. Wait until it complete.
[If encounter any error. Find out which .odex file is it. Then remove .odex file from folder origi_app in xUltimate folder.
If you encounter the error “ ‘java’ is not recognized as an internal or external command, operable or batch file” see Note below.]
9. Then select option (4) Deodex /system/framework. Wait until it complete.
10. Now Exit from xUltimate.
11. Disconnect and connect your smartphone. Your PC should open a Window for you to view your files.
12. Go to C:\xUltimate-v2.4.2 folder and copy “done_frame”, and “done_app”, and move them to the root of the internal sdcard. Don’t copy them to your external sdcard
14. Now safely eject your smartphone from the PC.
15. Click on My Computer and find the directory where Android SDK is installed (on my PC it is in C:\Program Files (x86)\Android\android-sdk\. Then go to the ‘platform-tools’ folder in it. Right click on any free space in folder while pressing shift key. Select ‘open command prompt here’.
16. Reconnect the smartphone to your PC in USB debugging mode.
17. Now enter the following commands (if you are using adb shell in su for the first time, keep smartphone screen on).
adb shell (this should recognize your device)
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/done_app/* /system/app/
rm /system/app/*.odex
cp /sdcard/done_frame/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
18. Your smartphone will reboot and perform an automatic Android update. You have now deodexed/zipaligned the ROM on your smartphone.
NOTE
I only tried this on my I8190 with ROM I8190XXALL2 - I8190XXALL1 BTU Rooted.
At Step 8, (running Option 3), if you encounter the error “ ‘java’ is not recognized as an internal or external command, operable or batch file” then xUltimate can’t find the PATH to your ‘java’ command.
To add the location of Java to your PATH do this:
Right-click on ‘My Computer’ (or Computer for Vista) and choose ‘Properties’.
Navigate to the ‘Advanced’ tab (or for Vista/7/8, click 'Advanced System Settings’ on the left, then find the ‘Advanced’ tab)
Click ‘Environment Variables’
Under System Variables, find 'Path' and click Edit...
DO NOT ERASE OR REPLACE THE CONTENTS OF THIS. YOU ARE SIMPLY GOING TO ADD TO IT.
At the very end of the text field, add a semicolon [ ; ] and add the location of java.exe.
On my Windows 64-bit system this is in “c:\program files\java\jdk1.7.0_06\bin” . For others it might be "c:\program files\java\jre7\bin". I seem to have java.exe in both locations but only the first one worked for the batch file in xUltimate.
Then ‘Okay’ that to save the addition and come out of ‘Properties’
Batch files will now be able to find java.exe without you modifying the batch file.
*************************************************************************************
If for some reason you can't deodex and zipalign apps and framework with xUltimate, ive uploaded them for your use:
done_app
done_frame
They were deoxeded and zipaligned from ROM I8190XXALL2 - I8190XXALL1 BTU Rooted
*************************************************************************************
I followed the above and it works. I used Root Explorer to check my smartphone and all the .odex files have gone, i have more memory available, and smartphone seems faster!
infected_
Well you'll get more ram and deode xing opens a whole new of theming possibilities but it won't be as fast as odexed rom even though zipaligned !
nikufellow said:
Well you'll get more ram and deode xing opens a whole new of theming possibilities but it won't be as fast as odexed rom even thigh zipaligned !
Click to expand...
Click to collapse
I get more RAM thats what i like and more space..! i dont care about theming... but i guaranty that the phone seems faster deoxed and zipaligned...
infected_ said:
I get more RAM thats what i like and more space..! i dont care about theming... but i guaranty that the phone seems faster deoxed and zipaligned...
Click to expand...
Click to collapse
I do not doubt you mate i just posted what i knew from my experience ! Stay with deodexed Rom for few more days/weeks and then temporarily try coming back to odexed stock and you'll know the difference
Sent from a hybrid phablet !
i just didn't find a way no recompile system.img in windows.... or else i had made a pretty cool rom and fast whit android kitchen 0.208... :silly:
Don't give up we need Roms
Sent from a hybrid phablet !
i can compile cm or aokp if u want
Yes please.
Sent from my GT-I8190 using xda premium
Shapeshift said:
i can compile cm or aokp if u want
Click to expand...
Click to collapse
can you decompile system.img from this latest 4.1.1 rooted rom I8190XXALL2_I8190OXXALL1_BTU and replace /system/app/* and /system/framework/* with the deodexed and zipaligned apk's:
done_app
done_frame
and then compile into odin flashable *.tar.md5 ?!
infected_ said:
Hi all,
I have managed to deodex and zipalign my rooted I8190XXALL2_I8190OXXALL1 ROM in my smartphone, so thought i would share it here.
Follow all the instructions carefully. I will not be held responsible in any manner if your smartphone doesn’t boot up or gets bricked due to not following the instructions.
Please make sure -
1. Your smartphone is already rooted (flash one of the rooted rom's founded here)
2. Download and install Busybox Installer latest version.
3. Make sure you already have Java SE Development Kit and Android SDK installed on your computer.
Install them to the default choice on the C: drive.
4. You should also have a basic knowledge of ADB.
Required Downloads -
1. xUltimate version 2.4.2 – Link. You may have to Google for the correct version to download. Extract it to C:\xUltimate-v2.4.2.
Instructions –
1. Connect your smartphone to your computer. (Make sure you have selected USB debugging in Settings>Applications>Development)
2. Open a command prompt as administrator. Wait for Window to appear.
3. Change Directory to C:\xUltimate-v2.4.2
4. Launch main.exe.
5. If everything goes well xUltimate should recognize the smartphone and make a connection. You should now see a list of options.
6. Select option (1) pull /system/app. Wait until it completes.
7. Select option (2) pull /system/framework. Wait until it completes.
8. Then select option (3) Deodex /system/app. Wait until it complete.
[If encounter any error. Find out which .odex file is it. Then remove .odex file from folder origi_app in xUltimate folder.
If you encounter the error “ ‘java’ is not recognized as an internal or external command, operable or batch file” see Note below.]
9. Then select option (4) Deodex /system/framework. Wait until it complete.
10. Now Exit from xUltimate.
11. Disconnect and connect your smartphone. Your PC should open a Window for you to view your files.
12. Go to C:\xUltimate-v2.4.2 folder and copy “done_frame”, and “done_app”, and move them to the root of the internal sdcard. Don’t copy them to your external sdcard
14. Now safely eject your smartphone from the PC.
15. Click on My Computer and find the directory where Android SDK is installed (on my PC it is in C:\Program Files (x86)\Android\android-sdk\. Then go to the ‘platform-tools’ folder in it. Right click on any free space in folder while pressing shift key. Select ‘open command prompt here’.
16. Reconnect the smartphone to your PC in USB debugging mode.
17. Now enter the following commands (if you are using adb shell in su for the first time, keep smartphone screen on).
adb shell (this should recognize your device)
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/done_app/* /system/app/
rm /system/app/*.odex
cp /sdcard/done_frame/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
18. Your smartphone will reboot and perform an automatic Android update. You have now deodexed/zipaligned the ROM on your smartphone.
NOTE
I only tried this on my I8190 with ROM I8190XXALL2 - I8190XXALL1 BTU Rooted.
At Step 8, (running Option 3), if you encounter the error “ ‘java’ is not recognized as an internal or external command, operable or batch file” then xUltimate can’t find the PATH to your ‘java’ command.
To add the location of Java to your PATH do this:
Right-click on ‘My Computer’ (or Computer for Vista) and choose ‘Properties’.
Navigate to the ‘Advanced’ tab (or for Vista/7/8, click 'Advanced System Settings’ on the left, then find the ‘Advanced’ tab)
Click ‘Environment Variables’
Under System Variables, find 'Path' and click Edit...
DO NOT ERASE OR REPLACE THE CONTENTS OF THIS. YOU ARE SIMPLY GOING TO ADD TO IT.
At the very end of the text field, add a semicolon [ ; ] and add the location of java.exe.
On my Windows 64-bit system this is in “c:\program files\java\jdk1.7.0_06\bin” . For others it might be "c:\program files\java\jre7\bin". I seem to have java.exe in both locations but only the first one worked for the batch file in xUltimate.
Then ‘Okay’ that to save the addition and come out of ‘Properties’
Batch files will now be able to find java.exe without you modifying the batch file.
*************************************************************************************
If for some reason you can't deodex and zipalign apps and framework with xUltimate, ive uploaded them for your use:
done_app
done_frame
They were deoxeded and zipaligned from ROM I8190XXALL2 - I8190XXALL1 BTU Rooted
*************************************************************************************
I followed the above and it works. I used Root Explorer to check my smartphone and all the .odex files have gone, i have more memory available, and smartphone seems faster!
infected_
Click to expand...
Click to collapse
Make it for pll or rename the thread "INFO OR HOWTO"
Great info thx m8
Sent from my GT-I8190 using XDA Premium App
The done_app link is broken..
JoFury said:
The done_app link is broken..
Click to expand...
Click to collapse
just tried it now... its working.
https://dl.dropbox.com/u/17735355/done_app.rar
https://dl.dropbox.com/u/17735355/done_frame.rar
Is this SIII Mini specific or Any phone and any rom?? THAN-Q.
NHS2008 said:
Is this SIII Mini specific or Any phone and any rom?? THAN-Q.
Click to expand...
Click to collapse
any device running on an odexed Rom
why fix it if it ain't broken ?
nikufellow said:
any device running on an odexed Rom
why fix it if it ain't broken ?
Click to expand...
Click to collapse
Thank you for the answer...
Sent from infected_ s3 mini i8190
nikufellow said:
any device running on an odexed Rom
why fix it if it ain't broken ?
Click to expand...
Click to collapse
Even the L version?
i have a 4.1.2 Faria ROM in my S3 galaxy mini. I can do this?
generalriden said:
i have a 4.1.2 Faria ROM in my S3 galaxy mini. I can do this?
Click to expand...
Click to collapse
I don't advise you... faria's rom is already zipaligned.
infected_ said:
I don't advise you... faria's rom is already zipaligned.
Click to expand...
Click to collapse
I have problem from
mount -o rw,remount /system/ /system/
cp /sdcard/done_app/* /system/app/
rm /system/app/*.odex
cp /sdcard/done_frame/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
Click to expand...
Click to collapse
and after searche on Google find another thread like this and i see diferant methode can you pleas see and explain i try with this http://forum.xda-developers.com/showthread.php?t=1688211 method this night and feed if worked but if you see we have diferant commande now i know need to change
from
#mount -o remount,rw /dev/block/mmcblk0p9 /system
to
#mount -o remount,rw /dev/block/mmcblk0p22 /system
i try and feed if worked later
thank for tut
hi, need some help. when i try to deodex, i got error "Error occured while loading boot class path files. Aborting. bla bla bla"
please help me
GOT TROUBLE WHILE INSTALLING A RECOVERY? GET A WORKING TWRP RECOVERY AFTER 2 MINUTES ON YOUR XPERIA Z2 D6503/D6502:
Instructions:
open any root explorer app like ES FILE MANAGER
Delete /system/etc/mm_twrp_recovery folder
Go to /system/bin/ folder
Look for the "chargemon.stock" file - If it's present, delete this one: chargemon - and now, rename the chargemon.stock to chargemon
Look for the "taimport.stock" file - If it's present, delete this one: taimport - and now, rename the taimport.stock to taimport
Reboot
download "recovery fix.zip" from mega.nz
extract the file and run "adbrecoveryfix.exe" the .exe file will install some needed files (normally into C:\Minimal ADB and Fastboot\ )
copy the files from the folder "RECOVERY FILES" into the "Minimal ADB and Fastboot" Folder
connect your xperia with the pc
open the "Minimal ADB and Fastboot" folder and then SHIFT+RIGHT CLICK to open a command window
now type:
adb shell
su root
mount -o remount,rw /system
exit
exit
install.bat
Click to expand...
Click to collapse
don´t forget to press enter after "adb shell", "su root" and so on!
now your recovery will install again without any errors!
DOWNLOAD:
https://mega.nz/#!NoVSlK5T!CPJDueW8nXiHEv-jjqo7U-CrrEa1nE2JTE8mWjn3NEs
YOU HAVEN`T INSTALL ANDROID MARSHMALLOW YET BECAUSE YOU WANT TO KEEP ROOT RIGHT, XPOSED AND THE RECOVERY?
THEN CHECK OUT THIS THREAT
http://forum.xda-developers.com/xper...7#post66513485
Another simple Method: thanks @meer_mortal
Deleted folders and rename chargemon etc
Plugged phone into computer with dev settings, debugging etc
Open root explorer to make / -RW
Run install.bat with CMD
Boom! MM with TWRP
To get in into recovery reboot press down after green LED
Click to expand...
Click to collapse
THIS IS A REPOST BECAUSE THE OTHER THREAD WAS CLOSED, SORRY ABOUT THAT.
open the "m a a d" folder and then SHIFT+RIGHT CLICK to open a command window
where is the ''m a a d'' folder?
EDIT:I've done it with the second method
vladimirospaok said:
open the "m a a d" folder and then SHIFT+RIGHT CLICK to open a command window
where is the ''m a a d'' folder?
EDIT:I've done it with the second method
Click to expand...
Click to collapse
sorry forget to explain that...
it means
"Minimal ADB and Fastboot"
can u add twrp on a higher version?
Hi guys!
I need to remove magisk, root and lock the booloader for my device. How can I do it?
Thanks
Download the Magisk uninstall zip (same site where you load the Magisk zip file or see the how to root threads) and flash it with twrp (same way as you flashed the Magisk zip or see the how to root threads).
Next do the same as you did to unlock the bootloader, change the command from unlock to lock.
That should do it.
Sent from my OnePlus6T using XDA Labs
-MrMM- said:
Download the Magisk uninstall zip (same site where you load the Magisk zip file or see the how to root threads) and flash it with twrp (same way as you flashed the Magisk zip or see the how to root threads).
Next do the same as you did to unlock the bootloader, change the command from unlock to lock.
That should do it.
Sent from my OnePlus6T using XDA Labs
Click to expand...
Click to collapse
so I don't need to flash strock rom?
thanks!
lele90 said:
so I don't need to flash strock rom?
thanks!
Click to expand...
Click to collapse
EDIT: I'm not able to unistall it due to: "I cannot access /data please uninstall with Magisk Manager"
Currently I did a factory reset, software install (from 6t settings) and lock bootloader...
I was not able to unistall magisk with ZIP
lele90 said:
Hi guys!
I need to remove magisk, root and lock the booloader for my device. How can I do it?
Thanks
Click to expand...
Click to collapse
If you cannot get the unroot/un-install for Magisk to work you can do it manually. Here is how using Linux, sorry not a windows user, so you need to find a utility to unzip the GZ file if this is the case, 7zip? The /data folder contains your backup and when you boot the device up normally you can pull the file down to your PC , then use fastboot to flash the un-=compressed boot image back to A or B (or both) sides.
1. adb shell to the rooted device and type $su to enter super user, $ cd /data to look at the data folder.
2. Locate the img.gz file with the long name such as stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz and copy it to your sdcard folder so you can pull it off the handset. Use $cp /data/stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz /sdcard/ . exit from the shell and back to the pc
3. de-compress the stock_boot file to boot.img. using $gunzip stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz
4. start the device in fastboot mode, using adb you can type $ adb reboot bootloader or hold power and vol-
5. $ fastboot flash boot_a stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img
This will restore your un-patched boot image
PulpoRojo said:
If you cannot get the unroot/un-install for Magisk to work you can do it manually. Here is how using Linux, sorry not a windows user, so you need to find a utility to unzip the GZ file if this is the case, 7zip? The /data folder contains your backup and when you boot the device up normally you can pull the file down to your PC , then use fastboot to flash the un-=compressed boot image back to A or B (or both) sides.
1. adb shell to the rooted device and type $su to enter super user, $ cd /data to look at the data folder.
2. Locate the img.gz file with the long name such as stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz and copy it to your sdcard folder so you can pull it off the handset. Use $cp /data/stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz /sdcard/ . exit from the shell and back to the pc
3. de-compress the stock_boot file to boot.img. using $gunzip stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz
4. start the device in fastboot mode, using adb you can type $ adb reboot bootloader or hold power and vol-
5. $ fastboot flash boot_a stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img
This will restore your un-patched boot image
Click to expand...
Click to collapse
MMM sorry I'm not a linux user...
But is enough to do a factory reset, restore the firmware (via software update in settings menu) ? Or I need to flash the stock firmware in that way: https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516 ?
lele90 said:
MMM sorry I'm not a linux user...
But is enough to do a factory reset, restore the firmware (via software update in settings menu) ? Or I need to flash the stock firmware in that way: https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516 ?
Click to expand...
Click to collapse
Try to flash the entire update file from OnePlus.com:
https://www.oneplus.com/support/softwareupgrade/details?code=9
Download the file, place it in your root internal storage (the parent dir of the Downloads folder), and flash it locally from the settings>system update>local upgrade menu.
ducted said:
Try to flash the entire update file from OnePlus.com:
https://www.oneplus.com/support/softwareupgrade/details?code=9
Download the file, place it in your root internal storage (the parent dir of the Downloads folder), and flash it locally from the settings>system update>local upgrade menu.
Click to expand...
Click to collapse
Already done and then locked my bootloader! Thanks
lele90 said:
Hi guys!
I need to remove magisk, root and lock the booloader for my device. How can I do it?
Thanks
Click to expand...
Click to collapse
Why do you want to do all that? You can prevent applications from detecting root access using magisk. Just saying...
papadi said:
Why do you want to do all that? You can prevent applications from detecting root access using magisk. Just saying...
Click to expand...
Click to collapse
It does not work for my Home banking app ... I need it!
PulpoRojo said:
If you cannot get the unroot/un-install for Magisk to work you can do it manually. Here is how using Linux, sorry not a windows user, so you need to find a utility to unzip the GZ file if this is the case, 7zip? The /data folder contains your backup and when you boot the device up normally you can pull the file down to your PC , then use fastboot to flash the un-=compressed boot image back to A or B (or both) sides.
1. adb shell to the rooted device and type $su to enter super user, $ cd /data to look at the data folder.
2. Locate the img.gz file with the long name such as stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz and copy it to your sdcard folder so you can pull it off the handset. Use $cp /data/stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz /sdcard/ . exit from the shell and back to the pc
3. de-compress the stock_boot file to boot.img. using $gunzip stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz
4. start the device in fastboot mode, using adb you can type $ adb reboot bootloader or hold power and vol-
5. $ fastboot flash boot_a stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img
This will restore your un-patched boot image
Click to expand...
Click to collapse
I tried this and now am stuck on the unlocked bootloader screen (where is says your boot loader is unlocked and software integrity cannot be guarenteed...), any ideas?
dipole said:
I tried this and now am stuck on the unlocked bootloader screen (where is says your boot loader is unlocked and software integrity cannot be guarenteed...), any ideas?
Click to expand...
Click to collapse
Did you press power off button? if yes, you stopped the boot...
PulpoRojo said:
If you cannot get the unroot/un-install for Magisk to work you can do it manually. Here is how using Linux, sorry not a windows user, so you need to find a utility to unzip the GZ file if this is the case, 7zip? The /data folder contains your backup and when you boot the device up normally you can pull the file down to your PC , then use fastboot to flash the un-=compressed boot image back to A or B (or both) sides.
1. adb shell to the rooted device and type $su to enter super user, $ cd /data to look at the data folder.
2. Locate the img.gz file with the long name such as stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz and copy it to your sdcard folder so you can pull it off the handset. Use $cp /data/stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz /sdcard/ . exit from the shell and back to the pc
3. de-compress the stock_boot file to boot.img. using $gunzip stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img.gz
4. start the device in fastboot mode, using adb you can type $ adb reboot bootloader or hold power and vol-
5. $ fastboot flash boot_a stock_boot_c875a8ab786c64b38c6e87ffc1911f4e7b274142.img
This will restore your un-patched boot image
Click to expand...
Click to collapse
lele90 said:
Did you press power off button? if yes, you stopped the boot...
Click to expand...
Click to collapse
I forgot the _a after boot (boot_a). i just rerooted to fix my issue so haven't tried with the correct boot_a.
Question though, shouldn't that be boot_a and boot_b? still trying to get my head around the two slots..
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img