[DEV] CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1 - Samsung Galaxy 5 I5500

Main thread + Features + Dev support
http://forum.xda-developers.com/showthread.php?t=2201860
CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1​
PhilZ Recovery is a CWM Advanced Edition that adds all the features you could ever miss in CWM.
It is a well proven recovery for many phones.
Please give your feedback, what works, and any bug you could encounter.
Read the features at the Main thread, and check if you are missing something.
To take a screen shot, just slide left!
And don't forget to read about powerful aroma file manager integration and double-tap shortcut (in FAQs).
How to install recovery?
From download link below, you'll get a 'recovery.img' file. Put that recovery.img file at root directory of your
sdcard. (means not in any folder)
Now, go to terminal emulator.
Give command:
Code:
su
You'll be asked to grant superuser permissions, grant it.
Now, give the following command:
Code:
flash_image recoveryonly /sdcard/recovery.img
Wait until it executes the command (4-5 seconds), it is installing the recovery.
Now, normally reboot to recovery and enjoy new recovery!
Download links
Latest version can be found here:
recovery.img (v6.40.1)
https://drive.google.com/uc?id=0B5c3gpyMBJusSGlpMW9UenZORW8&export=download
aromafm_galaxy5.zip (v1.91)
http://www.mediafire.com/?p5pdelpib6w8px
Click to expand...
Click to collapse
Special thanks to:
@Phil3759 : For this awesome open source recovery.
@chraso: For hosting and compatible flags.
AndroidARMv6 Team: For keeping this device alive.
Cyanogenmod Team: For making all these possible.

:FAQs:​
Q: Wanna know about Aroma File manager?
Visit the aroma file manager main thread for more info---> Aroma file manager main thread
Aroma file manager is a touch file manager which can be used while in recovery. It has options for copy, paste, delete,
change permissions and many others. Also, it has a Terminal inside. So, if you forgot to give correct permissions to any
file you can do that directly from recovery. This file manager has got many themes, font, icons, etc. options and it's UI
is fully customizable.
Q: How to start this File manager in Recovery?
Rename the downloaded file to 'aromafm.zip'.
Create a folder 'aromafm' inside 'Clockworkmod' folder on your sdcard.
Now, move that 'aromafm.zip' file to the 'aromafm' folder.
We're ready now, when you want to use it in recovery just double tap anywhere OR go to "philz Settings" and select
"Aroma File Manager" and it will start up.
If you also want to browse /data, /system and /sd-ext then mount them in the "mounts & storage" option in recovery.
Q: Problems with Aroma file manager startup?
After doble-tapping OR selecting 'Aroma file Manager' option under 'philz settings' if recovery gives error: 'aromafm.zip
not found at /clockworkmod/aromafm' then, wait for 4-5 seconds and again select 'Aroma file Manager', because it maybe
busy mounting sdcard.
If still doesn't work, you've made mistakes in steps mentioned in first post, please do again carefully.
Q: Does your phone every time reboots to recovery?
This happens very rare when you flash the recovery using any bad app or via any wrong (not proper) method. What you can do
is:
-If you've made a backup of your current ROM then just restore only it's "boot" and then select 'reboot to system'.
OR
-You don't have a backup? Then just flash the ROM which you are using currently again and wipe 'dalvik-cache'. Then reboot
to system. Booting process will take time.
SCREENSHOTS:
Main menu and PhilZ Settings
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
GUI Preferences: all is applied live (no reboot). Up to 14 menu height settings, scroll sensitivity, touch accuracy...
27 color settings + 5 alpha transparency levels for every GUI element
Change background image with a custom png (of your device resolution), a solid color (27 presets) or revert to original
cwm image
User configurable touch gestures (feel free to request for new actions)
Setup your time-zone + 30mn offset, super wipe option to install a new ROM
Backup and Restore any partition in a complete freedom, include modem (.img + .bin) and efs (.img + .tar)
Custom backups can also be restored by original CWM Advanced Restore Menu
TWRP Backup and Restore Support + md5 + single/multivolume format
Support multi-cpu compression, md5 check toggle and custom .android_secure path
Choose ors backup volume target
Flash multiple zip files in a raw
Aroma File Manager + Terminal Emulator: launch with a gesture action (double tap is default)
Full Wipe to Install a new ROM (sdcard is preserved)
Free Browse Mode to install zip files: select a default folder to start with and browse up to the root
XDA:DevDB Information
PhilZ Touch Recovery : galaxy5, Tool/Utility for the Samsung Galaxy 5 I5500
Contributors
Bhargav97, chraso, Phil3759
Version Information
Status: Stable
Current Stable Version: 6.40.1
Stable Release Date: 2014-05-07
Created 2014-07-12
Last Updated 2014-07-12

Very good recovery. :good:
Everyone should check it out.
I haven't found any bugs as of now.

UPDATE:
Changelog:
-Updated PhilZ sources to 6.23.8 (26.03.2014).
-Updated androidarmv6 sources. So, you'll be able to flash cm-ota without any Signature Verification error.
Below is the recovery.img file, flash using Terminal Emulator method:
recovery.img
Need feedback. If everything is fine, I'll add it to first post.

Will work on g900t t-mobile s5
Sent from my SM-G900T using XDA Premium 4 mobile app

jpeps said:
Will work on g900t t-mobile s5
Sent from my SM-G900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Don't try it until the developer says so!

MAJOR UPDATE:
PhilZ Recovery updated to 6.27.9.
PhilZ Recovery FULL VERSION now enabled (Touch, GUI options and everything!).
CWM updated to 6.0.4.8.
Ready for official support!
I seriously want feedback on this version. If it is working, we can now get our phone in "officially supported devices" list.
Download link:
https://drive.google.com/uc?id=0B5c3gpyMBJusSGlpMW9UenZORW8&export=download

Doesn't flash for me from terminal... on i5500. Just says "flash_image not found"?

RobsX2 said:
Doesn't flash for me from terminal... on i5500. Just says "flash_image not found"?
Click to expand...
Click to collapse
Yes. Sorry to say that this method (of terminal emulator) doesn't work on Stock ROMs.
What you can do is:
-Download my recovery.img
-Search google: Make an odin flashable .tar for recovery.img
-There are many tools out there. Get one and make an odin flashable tar.
-Now flash that tar using odin and enjoy the recovery.

Bhargav97 said:
Yes. Sorry to say that this method (of terminal emulator) doesn't work on Stock ROMs.
What you can do is:
-Download my recovery.img
-Search google: Make an odin flashable .tar for recovery.img
-There are many tools out there. Get one and make an odin flashable tar.
-Now flash that tar using odin and enjoy the recovery.
Click to expand...
Click to collapse
Thank you for the fast reply.
I shall try that now and let you know how i get on.
Many thanks!
---------- Post added at 12:18 PM ---------- Previous post was at 12:00 PM ----------
Ok ive made a flashable .tar.
Tried flashing wih odin, everything went ok, but recovery does not boot.... I dont know if it worked.
I used "one package" in odin plus the ops file
EDIT: Recovery has flashed and does work. Thanks!

RobsX2 said:
Thank you for the fast reply.
I shall try that now and let you know how i get on.
Many thanks!
---------- Post added at 12:18 PM ---------- Previous post was at 12:00 PM ----------
Ok ive made a flashable .tar.
Tried flashing wih odin, everything went ok, but recovery does not boot.... I dont know if it worked.
I used "one package" in odin plus the ops file
Click to expand...
Click to collapse
Then there is another simple solution.
-Install any CWM recovery (through ODIN).
-Now download any zip file of cwm recovery (use madteam.co if you don't find at xda).
-Open the zip and replace the recovery.img inside with this (PhilZ Recovery) one.
-Now, flash this modified zip file with the current cwm recovery (which you installed using odin).

hi again
ok now ive just tried flashing bluedroidmod, went through the flash fine, clicked reboot. I know get a blac screen that just says "android" in the middle of the screen and nothing else happens.. Do you know what could have gone wrong?

RobsX2 said:
hi again
ok now ive just tried flashing bluedroidmod, went through the flash fine, clicked reboot. I know get a blac screen that just says "android" in the middle of the screen and nothing else happens.. Do you know what could have gone wrong?
Click to expand...
Click to collapse
Have you done all the wipes?

Vagelis1608 said:
Have you done all the wipes?
Click to expand...
Click to collapse
Yessir

RobsX2 said:
Yessir
Click to expand...
Click to collapse
Did you pulled the battery to turn the device off when it hunged (at the "Android" screen)?
Have you tried booting up again?
Also, contact me via PM so that I will help you fix the issue. Let's not spam this thread .

UPDATE:
Updated PhilZ Touch sources to 6.40.1.
Fixed the misbehaviour of hardware keys in the new full version recovery.
In this version, I especially need feedback on:
-Hardkeys. Test all of them if they are correctly working or not.
-Change the 'Menu Background' to 'PhilZ Default' and 'Koush Default' (from PhilZ Settings > GUI options > Menu Background) and tell me if which of them is working. (ofcourse, reboot recovery after changing the background)
Download link:
https://drive.google.com/file/d/0B5c3gpyMBJuseDJ5VDZBeTlmQ2M/edit?usp=sharing

deleted

Bhargav97 said:
UPDATE:
Updated PhilZ Touch sources to 6.40.1.
Fixed the misbehaviour of hardware keys in the new full version recovery.
In this version, I especially need feedback on:
-Hardkeys. Test all of them if they are correctly working or not.
-Change the 'Menu Background' to 'PhilZ Default' and 'Koush Default' (from PhilZ Settings > GUI options > Menu Background) and tell me if which of them is working. (ofcourse, reboot recovery after changing the background)
Download link:
https://drive.google.com/file/d/0B5c3gpyMBJuseDJ5VDZBeTlmQ2M/edit?usp=sharing
Click to expand...
Click to collapse
ALL HARDKEYS WOORK FINE!
I just have one doubt.
When i reset to "Koush default" it gave me a netted grey background..
Whereas :"Philz default" gave a complete black background..
Is this supposed to happen.

Maybe I am too stupid
But where is on goo.im the PhilzTouch for this little jewel called galaxy5?

wrong post

Related

[GUIDE/BUGLIST] AOSP 2.1 ROM Bugs and Fixes | Post questions here

AOSP 2.1 Bug List - by FreeX10 (jerpelea and zdzihu)
THE DEV THREAD IS NOT A DISCUSSION THREAD!!!
Because the main DEV thread has become so cluttered with useless posts, i will try to condense all the Bugs and Fixes into the one post here. The DEV thread is not a thread to discuss what you would like to see in the next version, or a thread to ask why something was not included in the ROM. I do not have anything to do with the development of these ROMS but am trying to make life easier for Jerpelea and Zdzihu. If you have questions, answers, bugs or fixes, this is the place to post them.
AOSP 2.1 Changelog (Features that are working, and when they were resolved)
Changelog is here - http://forum.xda-developers.com/attachment.php?attachmentid=464170&d=1292341044
Current Issues and the Corresponding ROM version
** 007a
- Rom is in final release and is quite stable. Few users reporting reboot issues but seem to be related to individual users settings.
- Left button unlocking screen when in lock mode - workaround is to enable pattern unlock feature
- unable to get straight back into xrecovery menu without reinstalling - some users reporting this (myself included) - Fix is to manually reinstall menu using zdzihu's instructions here => http://forum.xda-developers.com/showpost.php?p=9561575&postcount=1
-
** 007
- sorry, been a bit slack updating this list - PM me if you want anything listed.
** b006
- wifi not coming back after turning it off - http://forum.xda-developers.com/showpost.php?p=9707776&postcount=4291
- Launcher Pro Plus FC after removing ADW - http://forum.xda-developers.com/showpost.php?p=9708084&postcount=4296
- [FIX FOUND] Vignette image garbled - http://forum.xda-developers.com/showpost.php?p=9712316&postcount=4340
make sure you have latest version of Vignette installed - seems to work ok.
- 2G Connection is not constant - http://forum.xda-developers.com/showpost.php?p=9713159&postcount=4345
- [FIX FOUND]3G not connecting - no APN's - http://forum.xda-developers.com/showpost.php?p=9713110&postcount=4344 and http://forum.xda-developers.com/showpost.php?p=9782564&postcount=34
Some users are saying if you manually enter your APN details, it all works
This is a work in progress so please PM me with the problem or post the specific issue here. Over the next few days i will be attempting to compile a list of all the bugs for the various versions of 2.1 AOSP Roms.
Lets keep the dev thread for what it is supposed to be - where the Devs can bounce ideas and list fixes and version releases.
Tim.
Installation Guides
What do you need...
- X10
- Root access (can be obtained many ways - z4root is probably the easiest - download z4root from market)
- ROM file (see below)
- USB cable to connect phone to pc
- zdzihu's Recovery menu needs to be installed also, and for this you need to be on 2.1 - does not work with 1.6 - http://forum.xda-developers.com/showpost.php?p=9561575&postcount=1 or installation guide below.
- patience!
AOSP 2.1 - Black Freedom
- Download ROM file from here => http://hotfile.com/dl/89981020/d198ed1/BlackFreedom_signed_007a.rar.html
- connect phone to pc and mount the SD card.
- Within the .RAR file is a .ZIP file - extract this to your phones SD card and rename it to Update.zip
- reboot phone and enter recovery menu (repeatedly pressing BACK as soon as the Sony Ericsson logo appears)
- a good idea is to take a backup of your phone before going any further - Backup and Restore, and then choose Backup. This will create a folder on your SD Card called XRecovery/Backups and will create a sub-folder for each backup. I have tested renaming these sub-folders to something usefull with no issues!
- Once backup is complete, zdzihu recommends running a "full wipe" - make sure you choose the correct option here, it is on the main screen and says "Factory Reset (full wipe)" - THIS IS AN OPTIONAL STEP
- once wipe is complete, click "Install update.zip from SD Card" - this is why we renamed the .zip file earlier.
- phone will install rom and bring you back to menu when completed. simply reboot and it will launch the AOSP 2.1 ROM
Let me know if these steps are not clear and i will edit them. i did them in 5 minutes before leaving to go away for the weekend
Installation Guide for zdzihu's xrecovery menu
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There are 3 main ways to install this menu. The main method is via the .APK file that zoz33 created.
Other methods are a manual file copy using root explorer or using the old gscript file (outdated method).
I guess you could also ADB but i wont go into that method.
What you need...
- 2.1 ROM on your phone, this will not work with 1.6 Android.
- The files for the install are here - xRecovery 0.2-release
- Phone must have ROOT access and have busybox installed from the market (this is crucial)
Method 1 - APK File
1. Download the APK file and copy it to your phone (attached to this post)
2. Install the APK file and run it.
3. Click on the "Install xRecovery" button. In most cases, this will simply install the menu and you are done!
If you get errors, you may need to try the manual method below.
Method 2 - Manual installation
1. Download the APK file again and rename it to a .zip file (replace .apk with .zip)
2. open the new .zip file and extract the /res/raw folder inside. It should contain 3 files (chargemon, busybox, xrecovery.tar)
3. Using root explorer (and make sure R/W mode is enabled) copy the 3 files listed about directly into /system/bin
4. reboot phone and tap back button until recovery menu appears.
As usual, PM me or post a reply if the instructions are not clear.
Cheers.
Cannot Enter Service Menu
Tried At the lock screen, press home, back, back, home, back, home, home, back (both Home and Menu)
Service Menu.apk does not work, error message flashes to quick to read
I cant install the ASOP using the recovery menu. When I select "Install update.zip from SD Card"
It say " E:Cant open /sdcard/update.zip (No such file or directory)."
Do i have to extract the ERD79_Update_signed_b006.rar? or edit the name? Help needed ASAP!
gohwh1 said:
I cant install the ASOP using the recovery menu. When I select "Install update.zip from SD Card"
It say " E:Cant open /sdcard/update.zip (No such file or directory)."
Do i have to extract the ERD79_Update_signed_b006.rar? or edit the name? Help needed ASAP!
Click to expand...
Click to collapse
1. extract ERD79_Update_signed_b006.rar
youcan see 2 folder(apps and HTC_IME) and ERD79_Update_signed_b006.zip
2. copy ERD79_Update_signed_b006.zip to sdcard
3. reboot to recovery mode
4. select Install custom zip
5. select Choose custom zip from sdcard
6. find ERD79_Update_signed_b006.zip in sdcard
7. select ERD79_Update_signed_b006.zip
8. select - yes - install ERD79_Update_signed_b006.zip
9. Wait a few minutes
10. if done. go back to main menu
11. reboot your phone
sory for my english, i want to help.
_______________________________________________
x10i ROOTED JIT002
Great now it working! Really thanks. If I decide to go back to Original Sony ROM, how do I go back?
Titanium backup is not picking up root tried z4root but still not working.
i used ConvertTool Decrypted branded ROM list (For unroot or rebrand purpose) (flashtools method) to extract my Original ROM from C:\Program Files (x86)\Sony Ericsson\Update Service\db\13740270 (My os is windows 7 64bit)
and i used X10Flash-2.1 X10 Flash Tool - Always newest Version (14.11.2010) for recovery my x10 to original rom
KamalKhattak said:
Titanium backup is not picking up root tried z4root but still not working.
Click to expand...
Click to collapse
tried install busybox from market and run Titanium backup again
standvision said:
tried install busybox from market and run Titanium backup again
Click to expand...
Click to collapse
Did but no luck it force closes. Tried to issue su command in terminal emulator it said no root
May be you root again by z4root
and install busybox
Now my rom is original ROOTED+JIT
i can't solve your Problem
the build 2.1 b006 is not rooted just the su installed without the binary files ,but reroot with z4 is working without any problem
Tony_C said:
Tried At the lock screen, press home, back, back, home, back, home, home, back (both Home and Menu)
Service Menu.apk does not work, error message flashes to quick to read
Click to expand...
Click to collapse
Tony, what ROM are you using? Is anyone else having this issue?
gohwh1 said:
I cant install the ASOP using the recovery menu. When I select "Install update.zip from SD Card"
It say " E:Cant open /sdcard/update.zip (No such file or directory)."
Do i have to extract the ERD79_Update_signed_b006.rar? or edit the name? Help needed ASAP!
Click to expand...
Click to collapse
to help with these posts, i have included an installation guide in the 2nd post now. looks like you have it sorted already but it will help someone else.
original SE camera app?
Hi! i´m really impressed so far, but i love my camera too much.. is there any way we could use the original camera app for 2.1? if there is, that might solve the errors + give us better settings...
thanks
mrtim123 said:
Tony, what ROM are you using? Is anyone else having this issue?
Click to expand...
Click to collapse
ASOP 2.1 b006
I'm glad after redoing everything my contact list shows up. Man was it a hassle without it..
last installation it wouldn't appear on my screen. blah lol. All good
mrtim123 said:
to help with these posts, i have included an installation guide in the 2nd post now. looks like you have it sorted already but it will help someone else.
Click to expand...
Click to collapse
Thanks but after I backup my stuff, I just install the ASOP ROM without doing a full wipe, will it affect anything? I thought by installing new ROM, all stuff will automatically being wiped?
Now i install AOSP 2.1 build b006 again
i can't access internet 2g from gsm
how to setup for internet acces

[N7105]MutiTool - Swiss army knife - MUST have tool for Newbies

MutiTool - Swiss army knife - MUST have tool for Newbies.
Glad to announce a utility tool - MultiTool.
This is state of the art must have tool for all newcomers. You can manage following things with it.
- Root
- Busybox
- EFS Backup/Restore
- Recovery changer
- Kernel changer
- Modem changer
- Backup/Restore System App & Framework folder
- Bloatware Backup-Remove-Restore
- LockScreen Security bypass
- Clean device to prepare for Triangle Away
Details of features under Installation & Features
Installation and Features MUST READ BEFORE USING
So You must have CWM/TWRP Recovery Installed to use this tool. Here is detail guide to get CWM on your device.
Procedure to get CWM :
Step 1
Download Philz_touch_*n7105.tar.md5 Also you need to have Kies OR Samsung USB driver installed on PC.
1.Open Odin and select PDA tab (see image below) (Get Odin from here)
2.Point to recovery file you have downloaded philz_touch_* -n7105.tar.md5
3.Now switch off device and reboot in download mode
press Vol down + Home +Power, And then, press Volume UP button in Warning Page to enter the Download Mode
4.Connect device to PC and wait till device successfully added to com port (it will turn light blue) (see image below)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5.Hit ‘Start’ to flash
6.Once it flashed successfully, you can see 'PASS' in table above the ID :COM, you can disconnect device from PC (see image below)
[Note : normally, phone should auto-reboot into recovery.
If it reboots into android and your recovery remains stock, repeat above steps and untick "autoreboot" in odin. Once flash is done, keep pressing power button until it reboots (normally will go to recovery)
when in recovery, if you choose option "reboot system now" and you get "yes - disable flash recovery", select that option to avoid stock recovery overwriting cwm]
On successful flashing your recovery change to CWM, Now Next step How to use Multitool
Installation of Multitool and Detail features
- Download N7105_MultiTool-AromaVxx.zip and copy to SD card (Internal / Ext)
- Reboot device to Recovery (Vol Up +Power + Home).
- You will have recovery menu like this(see image below), Select Install zip
- Then select Int/Ext SD card depending on you have copied file.
- Select file you have copied N7105_MultiTool-AromaVxx.zip and hit Entre. (See image File name may be different)
This will Open Aroma Installer and you will have following Option to perform. Read every option in detail before proceeding.
1.Root
Here you will have two option.
A.Root : You can root your device with this option, Also this option cleans leftover of previously installed Superuser/SU of different superuser app.
In case your device is previously rooted and on reboot you can't see SuperSU app in drawer OR if you unable to update binary, simply update from Play store and it should work.
B.BusyBox - Routinely this doesn't needs and most of app needs root works without this too. Still any of your app demand this then you can select this option also you can do it later too.
2.EFS Backup If you are newbies and don't know why you need this then first read this thread. I recommend all user to make EFS backup if you still don't have.
A.EFS Backup : This will make EFS backup in format of raw imahe efs.img to int SD card MyEFS folder
B.EFS Restore : This will restore previously made backup in case you lose IMEI and need it.
3.Recovery - This is recovery changer tool.
You can switch to different recovery like
A.Philz touch CWM based recovery
B.TWRP
C.Stock Recovery- remember if you flash stock recovery, you will have to use odin to flash CWM/TWRP.
Here is Philz Recovery original thread
Here is TWRP official project website
4.Kernel - You can switch between kernel
Available kernels are
A.NEAK kernel B.Perseus Kenel C.Stock Kernel
Here is Neak kernel original thread if you have any queries for NEAK kernel Credit @simone201 for NEAK kernel.
Here is Perseus Kernel original Thread, in case you have any kernel related queries for Perseus Kernel. Credit @AndreiLux for Perseus Kernel
5.Modem
A.Old Modem LK6 : This will Break EFS if you have new ROM, so i have removed this option Accidental flashing this only show msg 'Flashing old modem Not supported to your device'
B.New Modem MG1 :If you downgrade ROM and lose your IMEI, flashing this new modem can restore your IMEI.
6.backup Restore general - Helpful before trying different MODs, if that doesn't work you can restore previous file wuth this.
A.Backup Framework folder - Will make backup of System/framework folder to IntSDcard/DrKetanMod/framework folder -Needs 100MB free space
B.Backup System Folder - will make backup of System/app folder to IntSdcard/DrKetanMod/app folder. it needs appr 700MB space.
C.Backup to ExtSD - will backup System/app + System/framework folder to ExtSDCard/DrKetanMod. Needs 800MB space.
For Restore select option according you have selected backup location.
D.Restore Framework folder from IntSD
E.Restore System/App folder from IntSD
F.Restore System app and framework folder from ExtSD
7.Bloatware
A.Backup Bloatware - Select this to backup bloatware before removing it so you can restore anytime you need it.
B.Remove Bloatware - You can remove batch bloatware with this. To remove selected bloatware use this tool
C.Restore Bloatware
8.LockScreen security bypass
A.Remove Password - If you forget your lockscreen password/Pin/Pattern, you can bypass security with this option. This will remove PIN/Password and you can reset new. In case you bypass Pattern then you may have pattern on reboot but you can unlock with any pattern and you can reset your new pattern.
9.Prepare device to use TriangleAway Newbies are not knowing about their recovery/kernel so this tool will help to reset stock.
A.Clean device - This will remove all left over of Super user app and SU, also remove Busybox and symlink of busybox. As well this will Replace CWM to Stock recovery. But still clean root access will remain present to use triangle away app. That can be unroot with SuperSU settings.
Again if device doesn't have SuperSU app OR fail to update binary then update it from play store.
Remember after selecting this option your recovery will be stock and if you need CWM, you have to use Odin again
B.Select This If you have stock kernel - If your kernel is custom and you want to make device clean you also have to select this option along with A. to use triangle away.
Download :
N7105_MutiTool_AromaV10
-------------------------------------------------------------------------------------------------------------------------------------------------------
Hope friends you will find this tool helpful to keep on your SD card so you can use it anytime. If Niewbies can't post here in dev section, use this thread instead.
I don't own N7105 so coudn't test this, but there is nothing needed to change in script just i have replaced recovery,kernel and modem file of N7105. Reports are highly appriciated.
GoodLuck And Happy Flashing !
Changelog :
[16.09.13]N7105_MultiTool_AromaV10 - Initial release
Credits : @Phil3759 for his amazing recovery and busybox cleaning tool @Chainfire for his Superuser.apk and SU
Reserved
Wow thanks, this looks interesting. Makes it easier for all the new people who want to root their device I guess. THUMBS UP to you Sir!
Not only for Root as for rooting there are other tool threads are there, But commonest reason to root for most of new comers are, EFS backup, Bloatware cleaning and trying some different kernels. so this tool will give privilege to do all under single roof.
Also helpful to use when user lose IMEI by downgrading ROM. Also it makes awareness of EFS backup if user read this tool while rooting.
Thanks for this mate! Going to download and keep just for reasons. Always good to have and looks very handy. Much appreciated!
Thanks dr.ketan, nice work
Quick question, is the option in your tool to backup EFS done differently for the n7105?
I know the IMEI is handled differently on the LTE n7105 and just wondered if your MultiTool accounts for the differences between the n7100 and the n7105?
It takes raw image backup without any interference in contents. And efs partition is same for both device on checking pit.
Can you elaborate what difference does it have?
Sent from my GT-N7100 using xda premium
Thanks
Great tool to have....and keep.....incase of emergency.....many thanks....
dr.ketan said:
It takes raw image backup without any interference in contents. And efs partition is same for both device on checking pit.
Can you elaborate what difference does it have?
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
On the n7105 we do not have nv_data.bin file...
Because of the different chipset, as far as I know, we need to use QPST
I remember seeing a post on here somewhere with instructions for the i9305 but as they both use qualcomm chipsets, I believe it is the same procedure for the n7105
[edit] here:
http://forum.xda-developers.com/showthread.php?t=1946915
But this method doesn't making backup of nv_data.bin it just backup raw image of EFS partition. Does it have some information to other partition too?
Though i will check it.
Someone have reported this method working, Read post#4 of this thread
http://forum.xda-developers.com/showthread.php?t=2175902
dr.ketan said:
But this method doesn't making backup of nv_data.bin it just backup raw image of EFS partition. Does it have some information to other partition too?
Though i will check it.
Someone have reported this method working, Read post#4 of this thread
http://forum.xda-developers.com/showthread.php?t=2175902
Click to expand...
Click to collapse
Thanks
I guess I'll just use both methods to be safe
Oh thank.
 @dr ketan, can you make a flashable zip for deodex a rom under 4.3 (JB) ?
XXUEMK5 N7105 NORDIC VERSION, ROOT, STOCK KERNEL
PLEAAAAAAASE :$ I'm Ready Pay you (sorry for my english ... very bad ...)
Thank in advance.
dr.ketan the download keeps failing. is there another location for N7105_MultiTool_AromaV10.zip?
regards

[RECOVERY] TWRP 2.8.3.0 for Galaxy Tab 4 8 inch

Support is discontinued. Between the 6 different variants that I made this recovery for, it has been downloaded less than 500 times total over a 2 month period. That tells me that this device is simply not popular enough for continued support.
Here is TWRP 2.8.3.0 (unofficial) for the Galaxy Tab 4, 8in (T330 & T331 & T335 & T337T & T360 & T365).
This has been briefly tested by @Rusell, but please be aware that there may be a few bugs still. I do not own this device, so please be very specific when reporting any bugs you may find.
This is not a "direct from source build" (I will eventually switch to that method), but instead, it is a port from my Tab 31x version using stock Tab 4 zImage and DT image.
NOTES:
The new MTP feature of TWRP may cause issues with ADB access while in recovery. You may need to toggle "Disable MTP" a from the "mounts" menu to get ADB access.
64gb sdcards are reported to not work in this TWRP
All versions of TWRP occasionally give the "can't mount /system" error. If you get this error, simply reboot recovery and try again.
Click HERE for the latest version.
Please report any bugs here in this thread and attach the recovery.log. Advanced --> Copy log to SDcard --> Then attach the log to your post.
Credits go to:
@Rusell for initial testing
and of course the Team Win group
Supplied in 3 formats:
Odin flashable tar.md5 (for first time installation)
Recovery flashable zip (requires a custom recovery to currently be installed)
.img file (for those who use Flashify or other direct methods).
Instructions for ODIN: (use the one with "tar" in the name)
Download ODIN on your computer.
Power off the device.
Restart in "Download Mode" by holding the "HOME" button, "Volume Down" and "Power" all at the same time (for about 5 seconds).
Hit the "Volume Up" to enter download mode.
Start the ODIN exe program. Un-check Auto Reboot. See notes about ODIN below.
Connect the device via USB to your computer. Verify the device shows as "Added" in the Message box. If it doesn't show then you need the Samsung USB drivers (just install KIES to get them).
Select "PDA" then choose the recovery file you want to flash.
Hit "START". Wait for Odin to finish (~10-15 seconds). The message area will display "RES OK" when finished.
Restart directly to recovery mode before rebooting into OS.(Hold POWER, Volume UP, and the HOME button all at the same time. When you see the Samsung Logo, let go of the POWER button, but keep holding the Volume UP and HOME until you see the recovery screen).
After you get the custom recovery working, you can flash the latest SuperSu zip to get root.
Notes about ODIN
--Make sure that "Re-Partition" is NOT checked.
--Auto Reboot can be un-checked if TWRP doesn't flash correctly on your device. Some have reported that un-checking Auto Reboot fixes this issue. If you un-check Auto Reboot, you will need to reboot the device yourself (refer back to step 9).
Flash at own risk!!!!
I take no responsibility for anything you do to your device. Flashing any custom recovery will trip KNOX.
+++++++++++++++++++++++++++++++
DOWNLOADS
Click HERE for the latest version.
-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
XDA:DevDB Information
[RECOVERY] TWRP 2.8.3.0 for Galaxy Tab 4 8 inch, Tool/Utility for the Samsung Galaxy Tab 4
Contributors
gr8nole, moonbutt74
Version Information
Status: Beta
Created 2014-12-22
Last Updated 2015-02-23
CHANGELOG
2.8.3.0
All versions - fixed color
See TWRP site for other changes
2.8.2.0
T330
v2 - Disabled screen timeout to prevent freeze ups. You may (or may not) still see the setting, but the screen will not timeout.
v1 - Initial release
======================
T331
test1 - Initial test -working
======================
T335
test1 - Initial test -working
======================
T365
test2 - WORKING
test1 - not working
-
Reserved
Other 8 inch Tab 4 variants.
If you want this for your tablet, you must post your stock recovery.img and test for me. It should be easy to make for T331, T335, etc... as long as your bootloader isn't locked.
-
:/
BUG:
When making a backup (Around 42%) The tablet just crashes for a second and shuts down.
Forgot to mention that my screen timeout is disabled....
Rusell said:
BUG:
When making a backup (Around 42%) The tablet just crashes for a second and shuts down.
Forgot to mention that my screen timeout is disabled....
Click to expand...
Click to collapse
I need recovery log.
Sent from my SM-N900V using Tapatalk
Thanks long time ago i seen you haha
gr8nole said:
I need recovery log.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Re-installed recovery now it is working well. However this time i am backing up on my external SD, maybe i didn't have enough space in my internal storage.
---------- Post added at 09:35 AM ---------- Previous post was at 09:31 AM ----------
BUG (Again )
When the screen times out, you can't wake up the device it just deep sleep. I'm going to try to pull out a recovery log.
Rusell said:
Re-installed recovery now it is working well. However this time i am backing up on my external SD, maybe i didn't have enough space in my internal storage.
---------- Post added at 09:35 AM ---------- Previous post was at 09:31 AM ----------
BUG (Again )
When the screen times out, you can't wake up the device it just deep sleep. I'm going to try to pull out a recovery log.
Click to expand...
Click to collapse
New v2 uploaded. http://d-h.st/bpb
I added a flag to disable the screen timeout. Let me know if it works.
gr8nole said:
New v2 uploaded. http://d-h.st/bpb
I added a flag to disable the screen timeout. Let me know if it works.
Click to expand...
Click to collapse
screen timeout is not disabled.but that's the only bug i found.
Who else owns this device other than me?
NVM in the settings it says it is set for 60 seconds but it never times out.
i beg you
can anyone please port a recovery to smt331
anyone i mean that should be custom like my favourite cwm
gr8nole said:
New v2 uploaded. http://d-h.st/bpb
I added a flag to disable the screen timeout. Let me know if it works.
Click to expand...
Click to collapse
gr8nole,
hi, in boardconfig
TW_NO_SCREEN_BLANK := <true or comment line with # or omit for false>
TW_NO_SCREEN_TIMEOUT := <true or comment line with # or omit for false>
to completely slay screen time-out and lock
m
moonbutt74 said:
gr8nole,
hi, in boardconfig
TW_NO_SCREEN_BLANK := <true or comment line with # or omit for false>
TW_NO_SCREEN_TIMEOUT := <true or comment line with # or omit for false>
to completely slay screen time-out and lock
m
Click to expand...
Click to collapse
That's what I used and it did work.
Dewang rocky said:
can anyone please port a recovery to smt331
anyone i mean that should be custom like my favourite cwm
Click to expand...
Click to collapse
If you will send me the T331 boot.img or recovery.img, I will do it. But, you have to test it for me.
Rusell said:
NVM in the settings it says it is set for 60 seconds but it never times out.
Click to expand...
Click to collapse
Ok, the reason you still see the screen timeout settings is because that info was saved in the TWRP settings file. This would only affect you because no-one else has flashed a version that had screen timeout. If you delete the TWRP/.twrps file from your internal storage, then you won't see the timeout settings anymore. That page will only show brightness control. Either way, the timeout is disabled and should cause no more problems. :good:
Thanks for testing!
Flashing TWRP recovery successful on sm-T330nu
I have successfully flashed TWRP recovery on my Tablet, sm-T330nu
using the easy instructions provided by the OP, gr8nole.
I tested this recovery by flashing the supersu 2.40 and did a backup of
the stock rom. This recovery is great and working fine.
I have not face any screen freeze up during this test.
When wiping cache/dalvik, it takes a bit long about 4 mins to finished.
Thank you gr8nole for your hard work and great TWRP.
The stock rom backup using this TWRP recovery
is 2.89gb large. This stock rom had many not needed
apps removed and only a few small games.
Is this backup size normal for a stock rom of
a samsung tablet T330nu ?
Antrobot200 said:
The stock rom backup using this TWRP recovery
is 2.89gb large. This stock rom had many not needed
apps removed and only a few small games.
Is this backup size normal for a stock rom of
a samsung tablet T330nu ?
Click to expand...
Click to collapse
That doesn't seem to be too big. Samsung roms are typically very big. Look into the backup folder and see what the size of the pieces of the backup are. It may be a lot of data.
Edit: On my Tab 3, my backup is about 3 gb with a mildly debloated Samsung rom.
Sent from my SM-T310 using Tapatalk
Thank you for your quick explaination about
the backup rom size. I am glad it is the normal
size for this tablet. This is my first samsung tablet
so I am still learning a lot about using it.
For some reason this won't install for me in odin. I go through the process and when I boot into recovery it takes me into stock recovery. I renamed the file T330.TWRP.2.8.2.0.v2.tar.md5.exe with .tar extension and it flashes but but when I go into recovery its stock recovery.
thanks
I will upload recovery.img and boot.img of my smt331

[Recovery][6633][twrp] Unofficial TWRP 3.0.2 for Z3 Dual D6633

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bismillahi Alrahmani Alraheem
(in the name of God the most gracious, the most merciful)
Finally Unoffoicial TWRP 3.0.2 is here for Dual sim version of XPERIA Z3 (D6633)!!
Introduction:​
Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
And much more...
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
Source Code:
GitHub - https://github.com/omnirom/android_bootable_recovery
Gerrit Instance - http://gerrit.omnirom.org
Notes About Sony Devices:
The Xperia devices have a recovery-in-boot arrangement. This means that the recovery is booted using the regular kernel / boot image in the device. Team Win has worked with the FreeXperia device maintainers to come up with a way to extract the ramdisk from the FOTAKernel partition and use the ramdisk from that partition instead of the recovery that is included in the boot image of your device. This means that if you install current CM nightlies and flash TWRP to the FOTAKernel partition, you will be able to use TWRP instead of the CWM or CM recovery that normally comes in a CM boot image. Other boot images including stock kernels can be repacked to include this extraction utility to allow you to use TWRP from the FOTAKernel partition. This setup allows you to choose what recovery you want to have installed and allows you to update your recovery more easily. Unfortunately this setup requires that the boot image that you have installed include the ramdisk extraction utility. The source for this utility is here:
https://github.com/Dees-Troy/extract_elf_ramdisk
This utility is designed to work in conjunction with the current methods that most AOSP ROMs use for the ramdisk and can also be used on stock kernels. This setup means that you must have a kernel or boot image installed that will use the FOTAKernel method. Most AOSP based ROMs like OmniROM or CyanogenMod will support this method. Some stock kernels may also support the FOTAKernel method.
What does all this mean? It means that TWRP may not work on your device unless you install other custom software as well. Check with your ROM developer to see what they support.
DOWNLOAD:​
Please notice that it won't work in stock based roms, only custom roms will run it
20160907 (img)
20160907 (zip)
Installation methods
TWRP Install (Requires TWRP 2.8.4 or higher already installed):​
Download the latest TWRP image file (.img) from the download link and boot TWRP. Go to install and find and select the Images... button. Browse to the image that you downloaded and select it. Choose recovery and swipe to flash.
dd Install Method (Requires Root):
Download the latest image file (.img) from the download link above. Place it in the root of your /sdcard folder and rename it to twrp.img. Run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/recovery-twrp-302-z3dual.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Fastboot method:
you should have fastboot in your pc (either downloaded separately or with android SDK)
fire up Terminal (Linux and OS X) or CMD window (MS Windows) in the folder you have the image on it and it is preferred to copy the image to the folder of fastboot so the following command work then type:
Code:
fastboot flash FOTAKernel recovery-twrp-302-z3dual.img
don't forget to put ./ before 'fastboot' if you are using OS X or linux (./fastboot)
ZIP method:
flash the zip using any recovery
Themes and colors:
HERE
(Read Post #2 in the link if you want to customize, I'll be making pre-made themes later on inshaaAllah (God willing) )
NOTE: You are free to repack it and even sharing it without taking my permission
Please Donate If you want me to support Z3 dual more and more, it is back to you ​
XDA:DevDB Information
TWRP 3.0.2 for Z3 Dual D6633, Tool/Utility for the Sony Xperia Z3
Contributors
Muhammad Ashraf
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Testing
Created 2016-06-25
Last Updated 2016-09-07
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
dquelal said:
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
Click to expand...
Click to collapse
sorry for the late reply, I am not sure why does it act like that
i'll try to make a zip file for that issue
dquelal said:
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
Click to expand...
Click to collapse
Oh, I am SOOOOOOOO Sorry, You have noticed me, By mistake I have uploaded Cyanogenmod Recovery instead of twrp
figuring that out now
I am sorry all of you
thanks man
EDIT: DONE
dquelal said:
Hi, one question, I choose the .img file from twrp but doesn't appear the "recovery" option to choose and swipe, only appears the "kernel" option, it is correct? Should I proceed with this option?
Click to expand...
Click to collapse
Unlocked or Locked bootloader?
(Does this require an unlocked bootloader?)
I cannot get to recovery mode using DD or fastboot
Command will go through but adb reboot or h/w combos wont get me recovery. How do I install recovery ? . I have a ROM that can only be installed via recovery pl help
I cannot get to recovery mode using DD or fastboot
FAILED (remote: Command not allowed)
it always says "FAILED (remote: Command not allowed)"
should the bootloader be unlocked ?!
what is the problem here?!
Hi, i flashed the .img using my twrp, the only option on "select partition" was kernel, i know i shouldn't have done it, but i did. Now the phone doesn't boot, it keeps on a black screen. I think i need to flash a new kernel, can someone help me? Thanks
edit
Locked bl
Excellent WORK +++++
Bismillahi Alrahmani Alraheem YOU are my god!
Well done. You are the man. Exellent work with this TWRP for my D6633 (z3 dual)
it saved my life!
bryantshurley said:
I cannot get to recovery mode using DD or fastboot
Click to expand...
Click to collapse
If you want to flash it with fastboot, type 'boot' instead of 'FOTAkernel', so the command goes like this: "fastboot flash boot recovery-twrp-302-z3dual.img". That way, you'll be able to boot into recovery using the volume rocker. A little late, but I hope I helped.
"fastboot flash boot recovery-twrp-302-z3dual.img" got me to a new recovery screen and can no longer boot the system.
rzepek2pl said:
If you want to flash it with fastboot, type 'boot' instead of 'FOTAkernel', so the command goes like this: "fastboot flash boot recovery-twrp-302-z3dual.img". That way, you'll be able to boot into recovery using the volume rocker. A little late, but I hope I helped.
Click to expand...
Click to collapse
That was a bad advice. Now I only have TWRP on my phone. Only boots into this!
Can it be saved? How?
Your 20160907.zip based on TWRP 3.0.2 was put into root & flashed with TWRP v2.8.7.0 which did not update, when re-launching recovery I was still on v2.8.7.0

[UNOFFICIAL][RECOVERY] TWRP 3.2.1-0 [EXYNOS][6/9]

Team Win Recovery Project​
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
Disclaimer: Your warranty is now void!! I won't be responsible if you flash this on another device besides the prescribed device mentioned..
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options, if its not there, you may have to wait for a few days to access that option, some users claim that its within 10 days before this option appears).
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However this may not affect you if your country, European Union for example, forces Samsung to provide hardware warranty regardless of software status.)
More Information from here
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. It is HIGHLY UNRECOMMENDED to purchase any access to any kind of private forums, ROMs or Kernels.
(DO NOT GET FOOLED.)
Download: https://github.com/zeroblade1984/samsung_exynos8895/releases/tag/TWRP
Sources: https://github.com/TeamWin
If you love the work you can rate the thread or spare me some beer
XDA:DevDB Information
TWRP, Tool/Utility for the Samsung Galaxy Note 8 (2017 Phone)
Contributors
kairi_zeroblade
Version Information
Status: Stable
Current Stable Version: Update 6/9
Stable Release Date: 2018-06-09
Created 2017-12-20
Last Updated 2018-06-09
Changelog
January 21, 2018
Fixes for touch/responsiveness
Faster Backup and Restore speeds
Should boot up faster than previous
December 20, 2017
Update TWRP base to 3.2.1-0
Use an upstream bringup(dirty) of kernel, credits to @jesec and @geiti94
Bugs: None
Flashing Instructions
Notes: It may wipe all your data including those in internal storage.
Part 1a - HOW-TO FLASH TWRP (for new devices w/o TWRP yet):
1. In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
2. Go to Settings -> Developer options and enable OEM Unlock option.
3. Download and Install Samsung Mobile Phones Drivers.
- Option 1: Download and Install Smart Switch for PC.
- Option 2: Download and Install standalone driver package.
4. Download and extract Odin (Samsung's Flash Tool) to your computer.
5. Download a .tar image of TWRP.
6. Reboot your device to download mode.
- Hold [VOLUME DOWN] + [BIXBY] + [POWER] for approx. 15 seconds.
- Read the warning carefully.
- If you agree, press [VOLUME UP] to get into Download mode. If you don't agree, STOP.
7. Open Odin and place that TWRP tar file in the [AP] slot.
8. Connect your phone.
9. Hold [VOLUME UP] + [BIXBY] + [POWER] on your phone and then press start on Odin.
10. Wait for the phone to reboot. DO NOT release [VOLUME UP] + [BIXBY] + [POWER] or you may not reboot into TWRP.
Part 1b - HOW-TO FLASH TWRP (for devices that already had an earlier build of TWRP):
1. Download the recovery.img from the download page.
2. Place the downloaded image file on your device's memory (internal or external storage or OTG may do).
3. reboot to TWRP either from your Custom ROM menu or by using the previous method where you hold [VOLUME UP] + [BIXBY] + [POWER] when your phone is completely OFF.
4. Go to Install->(locate the file you downloaded)->on the bottom part of TWRP menu you will see flash image, go press it->then you can now select the image file->then choose recovery if you are prompted to what partition you are going to flash->swipe to flash->Profit!!
5. It may be best to reboot to recovery once the procedure is done just to check if things went fine. :good:
Part 2 - HOW-TO INITIALIZE TWRP: (for new phones)
1. If you completed Part 1 successfully, you should be in TWRP now. At this point, you will reach the screen asking you if you want to allow system modifications.
2. Select "Keep /system RO". (Don't swipe right or you may not be able to boot into system if you failed to complete next steps. However, you can swipe right to allow modifications if you are confident that you can complete next steps.)
3. Go to "Wipe" menu of TWRP and you will find "Format Data". Press "Format Data" and type "yes" to continue.
4. Go to "Reboot" menu and Press "Recovery" to reboot TWRP.
5. Download the latest dm-verity and force encryption disabler zip on your computer.
6. Transfer the zip to your phone.
- Option 1: MTP: Connect your phone with computer and just copy the zip to internal storage. (similar to how you transfer files when in system.)
- Option 2: ADB: Connect your phone with computer and run command "adb push /path/to/zip /sdcard/".
- Option 3: External SD: Copy the zip to an external SD and then insert the card to your phone.
7. Go to "Install" menu of TWRP and flash the zip.
TWRP is initialized and fully functional at this stage. Now you can either reboot into system or root, flash custom ROMs via TWRP.
Part 3 - HOW-TO ROOT:
1. Download the flashable zip.
- Option 1: Magisk
- Option 2: SuperSU (untested)
2. Transfer the zip to your phone.
3. Go to "Install" menu of TWRP and flash the zip.
Part 3a - HOW-TO FLASH CUSTOM ROMS:
1. Download the flashable zip.
2. Transfer the zip to your phone.
3. Go to "Install" menu of TWRP and flash the zip.
Simple.
Thank you very much for your fine work.
I went to the download site, and the file TWRP-3.2.1.0-greatlte.tar does not seem to work with the latest Odin for some reason.
So I used the recovery.img via the older TWRP on the phone and all good.
Tnx team...got the .img and flashed...reboot in recovery...and working like a charm...realy appreciate the works ??
Sent from my SM-N950F using XDA-Developers Legacy app
Thanks for the work!
Enviado desde mi Galaxy Note 8 mediante Tapatalk
What's the difference between this and the original thread? Is this a newer version that's actively maintained? [emoji846] Thanks
white7561 said:
What's the difference between this and the original thread? Is this a newer version that's actively maintained? [emoji846] Thanks
Click to expand...
Click to collapse
This is the newest version. The other is a older version and i think from maintainer. No more Supports, because there are no new Updates since months
Sent from my Galaxy Note 8 using XDA Labs
white7561 said:
What's the difference between this and the original thread? Is this a newer version that's actively maintained? [emoji846] Thanks
Click to expand...
Click to collapse
Yes this is newer upstream (uses android-8.0 branch from Omni) and I will try my best to keep it up-to-date..
I am also looking for kernel testers as I, alone testing my work will be Bias (I do own both S8 and Note8)
kairi_zeroblade said:
Yes this is newer upstream (uses android-8.0 branch from Omni) and I will try my best to keep it up-to-date..
I am also looking for kernel testers as I, alone testing my work will be Bias (I do own both S8 and Note8)
Click to expand...
Click to collapse
So I could just flash this over the old twrp? Also. Any bugs? Thanks so much eh [emoji846][emoji16]
white7561 said:
So I could just flash this over the old twrp? Also. Any bugs? Thanks so much eh [emoji846][emoji16]
Click to expand...
Click to collapse
You can Either use Odin (I re-uploaded a new Tarball) or just flash the image via an earlier version of TWRP..so far this has no bugs, I tried ADB sideload, backup and restore and had no issues..
kairi_zeroblade said:
You can Either use Odin (I re-uploaded a new Tarball) or just flash the image via an earlier version of TWRP..so far this has no bugs, I tried ADB sideload, backup and restore and had no issues..
Click to expand...
Click to collapse
Done. Installed using twrp method. Worked fine. Anyway. Thanks
is it necessary to initialize (wipe/format data) when updating over old twrp?
Wow! I've been out of the Android game for 6 months and it feels damn good to be back, first stop, TWRP lmao!
Sent from my [device_name] using XDA-Developers Legacy app
Hi guys, sorry for the offtopic, what exactly "greatlte" means?
infrasonic13 said:
Hi guys, sorry for the offtopic, what exactly "greatlte" means?
Click to expand...
Click to collapse
Greatlte is the codename for Samsung Galaxy Note 8 Exynos edition. Powered with Samsung Exynos 8895 processor.
Sent from my SM-N950F using Tapatalk
Edit: Tried it a 2nd time and now it was working. The 1st time I flashed the recovery, rebooted into recovery and started the backup. Guess that this was the problem.
Hi,
I just installed the new TWRP 3.2.1.0 and tried to make a full backup.
But it was not finishing it. After more than 45min I canceld it.
Please find enclosed the log file which was created. Hope it helps
Best regards,
dingolino
I dont get it. Why make this thread when there already is a twrp thread ?
Zionator said:
I dont get it. Why make this thread when there already is a twrp thread ?
Click to expand...
Click to collapse
'Cause it's another maintainer
kevinblackwell said:
'Cause it's another maintainer
Click to expand...
Click to collapse
What do you mean?
What's the difference between this and the other ?

Categories

Resources