.
Market link: Android Root Toolkit (free)
Root Toolkit for Android™
I wrote this little root utility for myself to help consolidate and automate some root functions that are available in various other apps, but nowhere all together.
Note: this utility does not root your Android device--it assumes that your device is already rooted.
If you are having problems or issues with it, please send me an email at [email protected] with as much detail as you can provide.
FEATURES:
display current root, /system and root (/) mount status, and root save status; will also display bootloader lock status for the Samsung Galaxy Nexus
reboot options (normal, recovery, bootloader)
power off device
remount rootfs (/) and/or /system in read-write or read-only mode; note: remount behavior changed in Android 4.2 and higher that causes remount effect to not be usable by apps other than the one that initiated the remount
save (protect) / restore root function; for 4.2 devices with ext2/3/4 /system partitons, a copy of su binary can be saved and later restored; for 4.3 devices, I've implemented Pau Oliva's 4.3+ "OTA rootkeeper" functionality (i.e., via keeproot.sh)
freeze (disable) or thaw (enable) an application (use caution when freezing a system app!); you can select showing user and/or system apps in the Freeze/Thaw Display Options in the Preferences/Settings menu
display system (getprop) property values
Galaxy Nexus and Nexus 7 (1st gen) only options:
flash a stock recovery
flash various custom recoveries
make recovery "stick" (keep stock recovery from overwriting your custom recovery)
identify currently installed recovery
bootloader lock, unlock, status (Galaxy Nexus only)
option to turn confirmation mode on / off (defaults to on)
option to turn "safe mode" on for the app to prevent any su or flashing operation from occurring
Warning / disclaimer: the author of this app is not responsible for any loss or damage caused by or related to its use.
If you are not comfortable with or knowledgeable about the proper use and functionality of this app, please discontinue its use and uninstall.
Click to expand...
Click to collapse
PERMISSIONS:
INTERNET - for downloading recoveries from the internet
WRITE_EXTERNAL_STORAGE - this is for the downloaded recoveries and work files used to identify which recovery is currently installed
ACCESS_SUPERUSER permission to support interaction with SuperSU
Keywords: root status, root checker, mount status, flash stock recovery, flash custom recovery, reboot recovery, reboot bootloader, power off device, remount system, make recovery stick, identify recovery, save root, restore root, freeze app, disable app, thaw app, enable app,
bootloader lock, bootloader unlock, bootloader status, getprop, system properties
Screen shots:
{
"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"
}
--------------------------------------
Android is a trademark of Google, Inc.
Version 1.3 just uploaded to the Market:
[version 1.3 - 22-April-2012]:
- support freezing (disabling) or thawing (enabling) applications
..(take care before deciding to freeze a system app)
These updates weren't as easy or straight-forward as I had imagined it would be--no wonder there's so few apps out there that have the freeze/thaw feature .
interesting and important tool
I am very interested in this tool and will have a try for sure. Number of questions:
1. Can your tool save current recovery as a blob, which is either cwm flashable or dd flasable(flash through "dd if=/sdcard/recovery_blob_backup of=/dev/block/mmcblk0p4"). My ASUS TF101 is rooted with stock recovery, I would like to try cwm recovery, but I want to save my stock recovery so that I can switch back to stock recovery when OTA is coming.
2. The most important features are those marked as "Galaxy Nexus only options". Is it harmful to try these on other devices such as ASUS transformer.
3. Does it work to use cwm recovery to flash official firmware package without any repacking. How about your tool?
Thanks in advance
---------- Post added at 03:51 PM ---------- Previous post was at 03:30 PM ----------
Two more questions:
4. The su backup made by Voodo rootkeeper is not "immutable", it can be revoced by "chattr -i" and then "rm". how about your backup?
5. If superuser.apk is removed or disabled, does your root protection tool
still work?
Thanks
e154037 said:
I am very interested in this tool and will have a try for sure. Number of questions:
1. Can your tool save current recovery as a blob, which is either cwm flashable or dd flasable(flash through "dd if=/sdcard/recovery_blob_backup of=/dev/block/mmcblk0p4"). My ASUS TF101 is rooted with stock recovery, I would like to try cwm recovery, but I want to save my stock recovery so that I can switch back to stock recovery when OTA is coming.
Click to expand...
Click to collapse
The app will not save a current recovery (not a currently implemented function).
I can tell you I tried copying the currently installed recovery on my GNex using exactly the process you described above. Unfortunately, the flash_image of that copy/backup does not appear to flash properly (and/or I got an error--I think I did get an error when doing the flash and ended-up trying several different versions of the flash_image utility to no avail). The resultant backup/copy of the recovery partition was usually about 12MB vs. approx. 5MB for a "normal" other recovery file that you would flash, so I don't know if its a size issue or limitation with the flash_image utility or not, but flashing a copy of the whole recovery partition did not work for me on the GNex.
I suppose "flashing" via the dd command might / would work, but I haven't yet tried that (dd is scary ).
2. The most important features are those marked as "Galaxy Nexus only options". Is it harmful to try these on other devices such as ASUS transformer.
Click to expand...
Click to collapse
I have product/device checks in the app that should keep those options from even being available to you on the main menu if its not a GNex device. The Setting / Preferences settings will still appear, but if you don't have a GNex, they should not appear on the actual main menu (I'd be very interested to know if they do ).
3. Does it work to use cwm recovery to flash official firmware package without any repacking. How about your tool?
Click to expand...
Click to collapse
My app uses the flash_image utility to flash its recoveries for the GNex. It does not use ROM Manager or ClockworkMod for any flashing operations that it undertakes.
4. The su backup made by Voodo rootkeeper is not "immutable", it can be revoced by "chattr -i" and then "rm". how about your backup?
Click to expand...
Click to collapse
Yep, works exactly the same .
The immutable property is apparently only supported on the ext2/3/4 type of filesystems (I think that's the right list)
5. If superuser.apk is removed or disabled, does your root protection tool
still work?
Click to expand...
Click to collapse
I never specifically tested removing Superuser.apk, but you should/would still be able to re-download that app from the Market and install it to complete the second half of root (the first being restoration of the su binary).
~ ~ ~
You should know that the GNex-only options that I support in the app were basically because I own a GNex and wanted to support some functions that I got tired of doing via other apps. Supporting devices other than the GNex is not currently in my plans since it these things are very device- and recovery-specific and I wasn't comfortable releasing features and functionality that I could not directly test and validate myself.
Cheers!
Thanks for the explanation. Where can I find the flash_image utility, is it device spacifilc? If it is not your self-made component, can you give me a copy of the utility.
e154037 said:
Thanks for the explanation. Where can I find the flash_image utility, is it device spacifilc? If it is not your self-made component, can you give me a copy of the utility.
Click to expand...
Click to collapse
Ah, there's a billion copies of it "out there", but you should be able to extract if from the .apk file of my app if you want.
Just make a copy of .apk file (its really just a .zip file, after all). Then use a file explorer or unzip utility and explore res/raw folder (I think that's where it is).
It should work on all Android devices (I've got/found multiple copies and versions of various ages and sizes that I'm sure are due to the different builds of Android).
The key thing you need to be careful of is making sure you've got the proper partition / area that you are going to be flashing to (i.e., the recovery partition is not located in the same place / name on every device and there's no way (that I'm aware of) to universally describe how to identify it (short of looking in the build code for your specific device)). Flashing a recovery to the boot partition is a quick and easy way to brick your device .
Also, making sure that you've verified that integrity of the file you are flashing (i.e., via and MD5 or SHA1 checksum) is always a good idea. There's no inherent checksum / integrity check done by the flash_image utility--it'll flash anything to anywhere you tell it (or at least try to).
All due caution and a current Nandroid backup is always your best friend .
Cheers!
Thanks.
Stupid me! I should have realized that the tool could be extracted from your apk or for ROM manager.
Question on image file used in flash_image:
Asus official firmware package's zip file contains a file "blob", unpack the blob one can find a number of images, including blob.SOS. This blob.SOS is the stock recovery image. To my knowledge, blob.SOS should be repacked when being flashed with dd.
Is this blob.SOS (witout any repack) the right one goes with flash_image (flash_image recovery /sdcard/blob.SOS)?
e154037 said:
Thanks.
Stupid me! I should have realized that the tool could be extracted from your apk or for ROM manager.
Question on image file used in flash_image:
Asus official firmware package's zip file contains a file "blob", unpack the blob one can find a number of images, including blob.SOS. This blob.SOS is the stock recovery image. To my knowledge, blob.SOS should be repacked when being flashed with dd.
Is this blob.SOS (witout any repack) the right one goes with flash_image (flash_image recovery /sdcard/blob.SOS)?
Click to expand...
Click to collapse
LOL, no worries! (I've had more than my share of those moments )
I'm not familiar with the Asus .zip package formats or the blobs.
But, I would think you could verify that you are talking apples-to-apples (so-to-speak) if you were to calculate the MD5 of a current blob recovery file with an extracted dd dump of the currently installed recovery's MD5 file (i.e., find the published blob that should match what you have installed; if they match, then you are on the right track, otherwise, you'll have to re-evaluate and dig a little deeper).
Cheers!
Says i dont have superuser.apk but i do ..
Sent from my VS910 4G using xda premium
motodroidfreak said:
Says i dont have superuser.apk but i do ..
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
Hmm, do you know where it's actually installed (i.e., the full file path)?
My app checks for "Superuser.apk" or "SuperUser.apk" in the /system/app directory.
Lemme know where yours is installed and I'll make a quick tweak .
Cheers and thanks!
Android Root Toolkit: updated to version 2.6
New version just published to the Play Market...thanks!
Here's the most recent change log items:
[version 2.6 - 08-December-2013]:
- support save root for 4.3+ devices (credit/thanks to Pau Oliva (poliva) and Chainfire)
- fix FC caused in some devices that return weird (non-standard) Android version information
- 2012 N7 only: support 4.3 (jwr66y) and 4.4 (krt16s) stock recoveries
- Samsung Galaxy Nexus only: support recent stock recoveries for international and Sprint versions
- address transitory mount behaviour that apparently started in Android 4.2 and up
- display warnings for keeping a pre-4.3 saved root present before installing a 4.4+ OTA
- lots of other minor tweaks, cleanups, and enhancements
Click to expand...
Click to collapse
Related
MutiTool - Swiss army knife - MUST have for Newbies. 17Menu >300 choices. believe it!
MutiTool Advaced - Swiss army knife - All in One Tool is on post#3
MutiTool Basic- Swiss army knife - MUST have tool for Newbies.
This is for N7100 only, N7105 user look here.
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
- Flash Recovery/Kernel/Modem from SD card (.img .bin)
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 : Click to Show Contents if you want to know How to flash CWM. If you have CWM installed then move to next step - MultiTool Intallation and features.
Step 1
Download Philz_touch_*n7100.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_* -n7100.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 DrKetan_MultiTool-AromaVxx.zip from end of this post 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 location.
- Select file you have copies DrKetan_MultiTool-AromaVxx.zip and hit Entre. (See image)
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 : Don't Flash this on New ROM ME6 and later otherwise you will lose IMEI
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.
10.Own Flashing
No more Flashable zip OR Tar needed to flash extracted recovery/kernel.img OR modem.bin
You can extract recovery.img or boot.img or modem.bin from stock ROM by simple unzip tool and put file on Int/Ext Sd card root directory then you can follow below mentioned task from aroma to flash that stuff.
A.Flash Kernel from IntSD
B.Flash Kernel from ExtSD
C.Flash modem from IntSD
D.Flash modem from ExtSD
E.Flash recovery from IntSD
F.Flash recovery from ExtSD
Download :
DrKetan_MutiTool_AromaV11 - Basic version
Dr.Ketan_MultiTool_Advanced
Old Version
DrKetan_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.
GoodLuck And Happy Flashing !
ChangeLog :
[15.09.13] DrKetan's MultiTool V10 -Initial release
[17.09.13] DrKetan's MultiTool V11 - two changes. A. Own Flashing - you can flash your recovery.img /boot.img /modem.bin. B.fixed issue on twrp using ExtSD option.
[21.09.13] DrKetan's MultiTool Advance V1 added. A. Aroma File Manager with Terminal. B. Odex remover C. Simplistic backup restore. D. System push
[29.09.13] DrKetan's MultiTool Advance V2 added. A.GPS Glonass fixer B. CSC Features C. build.propTweaks D. Bloat remover customized
Credits : @Phil3759 for his amazing recovery and busybox cleaning tool @Chainfire for his Superuser.apk and SU
I MutiTool Advanced
Ok friends glad to present advanced version of MultiTool. This is not much different from basic version but having some extra features and may not be comfortable to use by newbies. so releasing here as extra version and keeping basic vesion as it is.
Index
- Root
- Busybox
- Recovery changer
- Kernel changer
- Modem changer
- Backup/Restore System App & Framework folder/ EFS /Simplistic and mass bloatware remover
- Restore
- Odex remover
- Customized bloatware remover
- Customized CSC Features
- Tweaks - build.prop
- LockScreen Security bypass
- Push System Apks
- GPS Glonass Fixer
- Clean device to prepare for Triangle Away
This is advanced version and expecting no need to write guide about how to flash CWM and install multitool, still anyone have doubt please refer post #1.
Detail features
- Tool having some welcome screen, introduction, terms and condition, changelog, features list initially.
- After this is MainMenu. You can select either of one menu
A. MultiTool Utilities
B. Aroma File Manager with Terminal Console
C. System Information.
- Starting with Mutitool utilities, you will get following options
1. Root option : Inject root to device.
2. Busybox : Inject Busybox to device.
3. Recovery Flasher
Phillz recovery
TWRP recovery
Stock recovery
Recovery from SD card - You need to put desired recovery.img file on root directory of int SD card
Recovery from ExtSD card - You need to put desired recovery.img file on root directory of Ext SD card
Do Not change - To Keep your existing recovery
4. Modem Flasher
New MG1 flash - you can restore IMEI lost by downgrading ROM. I have removed option to flash old modem as it is not useful. still can flash any modem from SD card
Flash Modem from Ext SD - Put modem.bin file on root directory of ExtSD to flash
Flash Modem from Int SD - Put modem.bin file on root directory of IntSD to flash
Do Not change - To keep your existing modem
5. Kernel Flasher
Perseus Kernel
NEAK Kernel
RedPill Kernel (TW)
Adam Kernel
Stock Kernel (MG1)
Flash Kernel from ExtSD - Put boot.img file on root directory of ExtSD to flash
Flash Kernel from IntSD - Put boot.img file on root directory of IntSD to flash
Do not change - To keep existing kernel
6.Backup and Removel utility - This will be Menu page
There will be option to skip this OR to enter to customize backup/removal
EFS - A.Backup to IntSD B.Backup to ExtSD
Bloatware - A.Backup Bloatware (To bloatware folder in intSD)B.Bloatware Removal
System Backup A.Backup System/app folder to IntSD/DrKetanMod/app B.Backup System/framework folder to IntSD/Dr.KetanMod/framework
Simplistic Backup A.OdexB.Deodex If you want to try Simplictic framework. select according you are flashing version of simplistic. Incase simplistic doesn't work, you can restore your files.
7.Restore Utility - This will be menu page
There will be option to skip OR enter customiztion of restore.
All above option of backup will available here when you needs to restore.
EFS - A.Restore from IntSD B.Restore from ExtSD
Bloatware - Restore bloatware, if you have previously made backup
System Folder - A.Restore from DrKetanMod/app to System/app B. Restore from Dr.KetanMod/framework to System/framework
Simplistic - A.Odex B.Deodexed
8.Odex remover - This is Menu page
select skip OR enter to remove selected odex. This helpful when you flashing mod on odex rom doesn't have odex removal script
There is 19 common odex you can select any of it to remove
9.Customized bloatware remover
Now there is option to remove selected Bloatwares.
10.Customized CSC Features
You can have following CSC features. Thanks to @wesamothman and @MBariya for providing feature list. Just to add
-Backup is highly Recommended -Don't Use TRIGGER option first time -If you know your fetures file name is feature.cml and not others.xml then only select workaround option. - if first time regular flashing doesn't work, select only workaround option and flash. - still fail, select Trigger option + all requred feature and flash. - still fails select only workaround and flash - Still fails, Sorry hard luck, restore your backup.
11.Build Prop Tweaks
Following tweaks you can apply. Credits goes to original founder of tweaks, searched XDA for build.prop tweaked and selected some of it.
12.Lock Screen security bypass
You can use this if you forget PIN/Password/Pattern to remove it.
13.SystemPush - Push application to System folder
place apk and / or odex to sdcard/app folder to push system/app folder
place jar,apk and / or odex to sdcard/framework folder to push
system/framework folder
14.GPS/Glonass Fixer
Read This for more info, no need to download separately as it's included in tool.
15.Clean Device -
Use this to replace recovery with stock one, also remove old leftover of multiple superuser,su and busybox. still you will have root access to use triangle away
If your kernel is custom you have to use second option, as that will do above all plus replace custom kernel with stock one.
Will update screenshot later
Download
Dr.Ketan MultiTool Advance V2 [For 4.1.*]
Dr.Ketan MultiTool Advance V6 [For 4.3]
Older Vx
Dr.Ketan MultiTool Advance V1
Mirror
MultiTool V5 (For 4.3 OS) ---------- Mirror for V5 advance
Reserved one
Last one In case
Thanks a lot Doc for the tool and your entire contribution to the Note II comminity!! We sure will miss u! Just a request here: is it possible to work with another recovery, besides cwm? I'm using TWRP, hence the question. Thanks again!!
From the middle of nowhere to the center of everywhere!!
Yeah you can use CWM/TWRP
even you can change it from this tool only (without downloading).
chandoliasnikos said:
We sure will miss u!
Click to expand...
Click to collapse
How is that,did you bought other device doc???
I will go with Note3 once out.
May be this one last development for Note2 (unless change my mind )
Sad news for this section,where is the follow button????
I will supoort this section too but there will be little possibilities to develop without device. But sure still will be here for all newbies for their question on any of my thread.
I would like to try this out but I can't seem to find the link.
I guess host is still down. Will have to check after a few hours then. Thanks dr ketan.
We will miss dr ketan's apps and presence in note 2 forums.
Sorry for delay
Download link updated to OP
Finally good news for nOObs!
All in one toolbox by Dr.Ketan, waiting for few day for testing this tool.
Great Job Dr.Ketan. No need any extra zip files. only one file will do all things.
Will Miss your mods.
Can you please provide link for guide of Aroma installer. I have searched in xda forum but can't get proper result.
I have referred few, i will send you link tomorrow from office pc. But truly still not single guide there to explain everything. I have read a guide in note1 forum few days ago and I found it better than I referred.
Sent from my GT-N7100 using xda premium
I think one more utility we can add to this tool.
Flash own choice recovery kernel and modem. As many user still unable to manage flashable zip or tar from .img
So here you can put img file on sdcard and aroma can flash it.
Also looking forward to flash stock rom with aroma so no more prerooted rom you needs.
Sent from my GT-N7100 using xda premium
Hi dr ketan. I appreciate your hard work but your tool can't seem to save to my external sd card. The log says it is trying to create a directory in /external_sd but mine is /ExtSdCard. I think a rewrite of the code will solve the problem. I could send you the log file but I do not know how to attach it here.
Which ROM you have installed? and which recovery you have used ?
Next version have extra feature
- Flash your selected Recovery/modem/kernel from SDcard
You have to just keep your desired recovery.img/boot.img/modem.bin to Sd card.
No more need to have flashable zip OR tar.
STOCK ROM IMAGES BLU DASH 5.0 D410a V27-GENERIC Android Kitkat 4.4.2 MT6572 Chipset (no UBIFS)
PLEASE READ THE INSTRUCTIONS BEFORE FLASHING YOUR PHONE SO THAT YOU WON'T BRICK IT.
EDIT: 14 January 2015. Updated the TWRP 2.8.2.0 download link. Fixed the problem where ADB and MTP was not functioning in TWRP. Added backup support for a few other partitions including the Baseband.
EDIT: 19 January 2015. Changed method of rooting and added flashable zip with modified kernel to add init.d support (that was tested and is functioning properly.)
STEP 1
BACKUP YOUR MEDIATEK DEVICE
Prerequisites
All of the software is for Windows.
Download and Extract the MTK USB Drivers and the SP Flash Tool found closest to the top of the list at:
http://mtk2000.ucoz.ru/
Press the play button to the right of the file to start the download.
Download MTK Droid Root & Tools
Latest version can be found by following the link of the following post.
http://forum.xda-developers.com/showpost.php?p=38320254&postcount=1
Hint: Click the show content button to see the link to another forum with the download link
Direct Download Link of MTK Droid Root & Tools if you are having problems getting the link.
http://depositfiles.com/files/ne1gnposp
You will need Winrar to extract the files.
That can be downloaded from: http://www.rarlab.com/download.htm
READ HERE ON HOW TO BACKUP: http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
Thanks to @rua1 for the instructions and software.
NOTE: I WOULD RECOMMEND BACKUPING UP THE USRDATA PARTITION AS WELL TO DO THAT USE HEX "0X96B40000" AS THE LENGTH DURING READ BACK IN SP FLASH TOOL
To flash the DASH 5.0 you need to use the Preloader to do it.
STEP 2
Installing the Preloader Driver (READ this section entirely before trying)
Open Device Manager
Start -> Run
Type:
Code:
devmgmt.msc
Press Enter
Turn off the phone until it is completely shut down with nothing plugged in the USB port. You will see the screen go black and shortly afterwards it will vibrate.
With Device Manager open, connect the USB cable to the phone without turning it on.
You will see the MT65XX Preloader appear (see image)
{
"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"
}
Quickly double click MT65XX Preloader before it disappears, if it disappered, just unplug and plug back in the cable and try again.
Under the Driver tab, click Update Driver, click Browse my computer for driver software.
Using the Browse button find the MTKUSBAll folder you extracted and click on "New inst. win 7&8x64" and click OK
Click Next
If you get the message "Windows can't verify the publisher of this driver software", just click "Install this driver software anyway"
Click Close
Click Close
After the driver is installed you can unplug the phone.
STEP 3
Uploading the image files to the phone{/B}
WARNING: The BLU-DASH-5.0_141022_BLU-D410a-V27-GENERIC_FOR_SP_FLASH_TOOL.zip file has all of the necessary images but do not flash them unless you trying to recover from a brick.
DO NOT FLASH THE PRELOADER.BIN AS IT MAY BRICK YOUR PHONE.
THE ONLY FILES I HAVE PERSONALLY TESTED ARE boot.img, factory_NONmodified_recovery.img and system.img
Download BLU-DASH-5.0_141022_BLU-D410a-V27-GENERIC_FOR_SP_FLASH_TOOL.zip from here:
http://d-h.st/3L9G
See Step 5
Extract the SP Flash Tool.
Extract the system.img and MT6572_Android_scatter.txt (and/or boot.img and factory_NONmodified_recovery.img, if you wish)
Open the SP Flash Tool
Click the Download tab
Click the Scatter-loading button and select the MT6572_Android_scatter.txt file.
Click the location of ONLY the parition(s) you are going to flash: ANDROID = SYTEM partition (system.img), BOOTIMG = KERNEL (boot.img) and RECOVERY=RECOVERY (factory_NONmodified_recovery.img or custom recovery file)
Select the image file (e.g. system.img or system_rooted.img)
MAKE SURE ALL OTHERS ARE NOT TICKED
Click the Download button.
Plug in the phone or unplug and plug it back in to start flashing the images to the phone.
Note: This can also be done with the battery removed.
Your phone will have root.
STEP 4 - Adding TWRP
First we need to rename the file recovery-from-boot.p found in the /system folder.
Using a File Manager with root permissions rename
Code:
recovery-from-boot.p
to
Code:
recovery-from-boot.bak
OR
From an adb shell, rename the file
Code:
su
cd /system
mv recovery-from-boot.p recovery-from-boot.bak
Now turn off the phone and with SP Flash Tool flash TWRP 2.8.2.0. Download link below.
NOTE: Select only the RECOVERY partition to flash. TWRP themes are supported as well as the Aroma File Manager.
http://d-h.st/aQmt
STEP 5 - Rooting and adding init.d support
Go to http://download.chainfire.eu/supersu
Download the latest SuperSU.
Go to http://d-h.st/AJQ
Download the init.d support zip file.
Boot to TWRP while connected to a PC with adb tools run the command
Code:
adb reboot recovery[/url]
OR
Hold down the power select Reboot and hold down the volume up button until you see the TWRP logo.
Via the install menu, flash the SuperSU zip and inti.d support zip.
ALL DONE!
THANKS:
[user=631273]@Chainfire[/user] for SuperSU
[user=5119815]@rua1[/user] for MTK Droid Root & Tools and instructions on how to use SP Tools
[user=4478781]@yuweng[/user] for creating the tool to make TWRP for MediaTek devices
[user=912474]@Dees_Troy[/user] for TWRP
I will give a brief explanatoin and will elaborate more when I have the time.
For Root:
Thanks to @Chainfire
I basically mounted the system.img in a Linux OS and copied the files from the SuperSU v2.36 zip file and placed them in their relevant directories added the relevant permissions, etc.
For init.d scripts
Thanks to @alireza7991
See his thread: http://forum.xda-developers.com/showthread.php?t=2287540
I modified the kernel to boot and created a flashable zip that adds busybox to /system/xbin and creates the necessary folders then flashes the modified kernel.
For TWRP:
Thanks to @yuweng
I used Easy Magic TWRP Installer for MTK. See http://forum.xda-developers.com/showthread.php?p=53752834#post53752834
It worked but changed my partition information for some reason even though the size fit my paritition size. I wiped my phone and lost my baseband and recovered it. Posted a new thread on how to do that. See http://forum.xda-developers.com/android/software-hacking/restore-baseband-mt65xx-devices-t2967949
That is why I posted the image file so no one has to face that problem too. I tested it and it is functioning without any problems.
You can follow yuweng's thread to make it smaller if your partition size is smaller than 6MB for some phones, at a cost of course.
Anyone looking for baseband files can check http://forum.xda-developers.com/android/software-hacking/restore-baseband-mt65xx-devices-t2967949
For anyone wanting to use Link2SD on this, I have created a flashable zip to use with a custom recoveery that adds init.d support, installs Link2SD as a system app and adds a modified mount script that functions properly.
Requires root and a SD card with the second partition formatted as EXT4.
Download -> http://d-h.st/Dcgh
After flash this rom only get Blu screen, wipe and cache reset and the same, trun to V14 again and power on ok, this v 27 in the 2 variants, stock and rroted not start.
jorgefar said:
After flash this rom only get Blu screen, wipe and cache reset and the same, trun to V14 again and power on ok, this v 27 in the 2 variants, stock and rroted not start.
Click to expand...
Click to collapse
What procedure did you use to flash it?
SP_Flash_Tool_exe_windows_v5.1420.00
Scatter File from V27
selected only:
Recovery: non modified...
Boot: boot.img
Android : System.img or System Rooted
Flashed OK
Only Blu screen and restar...
Im currently on V14 Ok
jorgefar said:
SP_Flash_Tool_exe_windows_v5.1420.00
Scatter File from V27
selected only:
Recovery: non modified...
Boot: boot.img
Android : System.img or System Rooted
Flashed OK
Only Blu screen and restar...
Im currently on V14 Ok
Click to expand...
Click to collapse
Your phone is a BLU Dash 5.0 D410a and NOT the 5.0+ or 5.0 Studio right?
It sounds like your kernel (boot.img) is not booting the /system partition. Try flashing the /system and recovery partitions only for now and see what happens. Do not flash the boot.img
Thanks for you le answer! Thats right, is a Blu Dash 5.0 D410a, I try on Monday the suggested and post results!!!
Hi again, flashed system and recovery only, stuck on Blu screen again, try wipe and reset cache, stuck on screen Blu,any recomendation??
Added a flashable zip to add init.d and install LInk2SD with a modified mount script to run properly on this phone, BLU DASH 5.0 D420a running V27 Android 4.4.2.
See post #3
dechronic said:
Your phone is a BLU Dash 5.0 D410a and NOT the 5.0+ or 5.0 Studio right?
It sounds like your kernel (boot.img) is not booting the /system partition. Try flashing the /system and recovery partitions only for now and see what happens. Do not flash the boot.img
Click to expand...
Click to collapse
I'm having the same problem as Jorgefar. Mine is on v24 instead of v14 though after the factory update to 4.4.2. I rooted it with kingroot, but I would like to have twrp recovery. I've done everything you instructed him, but mine gets stuck in the bootloop as well. I thought i could just flash the recovery, and did the rename on the recovery file, but that didn't work still had factory recovery. After that I did the entire procedure and got the bootloop.
Sexyr said:
I'm having the same problem as Jorgefar. Mine is on v24 instead of v14 though after the factory update to 4.4.2. I rooted it with kingroot, but I would like to have twrp recovery. I've done everything you instructed him, but mine gets stuck in the bootloop as well. I thought i could just flash the recovery, and did the rename on the recovery file, but that didn't work still had factory recovery. After that I did the entire procedure and got the bootloop.
Click to expand...
Click to collapse
After installing TWRP you need boot into TWRP before booting into Android and install the latest SuperSU. The install-recovery.sh will replace TWRP with the stock recovery on the first boot if SuperSU is not installed, which renames it.
After flashing TWRP with the Smart Phone Flash Tool, disconnect the cable, press the power button and then hold the volume up button to enter TWRP.
dechronic said:
After installing TWRP you need boot into TWRP before booting into Android and install the latest SuperSU. The install-recovery.sh will replace TWRP with the stock recovery on the first boot if SuperSU is not installed, which renames it.
After flashing TWRP with the Smart Phone Flash Tool, disconnect the cable, press the power button and then hold the volume up button to enter TWRP.
Click to expand...
Click to collapse
Cool got it and am on v27 now. thanks..... now if ony there were other roms for it ah well, at least i'm rooted again with recovery.
can i flash this on BLU Dash 5.0 D400a
dechronic said:
Anyone looking for baseband files can check http://forum.xda-developers.com/android/software-hacking/restore-baseband-mt65xx-devices-t2967949
For anyone wanting to use Link2SD on this, I have created a flashable zip to use with a custom recoveery that adds init.d support, installs Link2SD as a system app and adds a modified mount script that functions properly.
Requires root and a SD card with the second partition formatted as EXT4.
Download -> http://d-h.st/Dcgh
Click to expand...
Click to collapse
This say file no longer available..could it be downloaded elsewhere?
Does this work on 5.0+?
Stiffymeister said:
Does this work on 5.0+?
Click to expand...
Click to collapse
Don't think so but I think I have a 5.0+ image. Anything in particular you looking for? I should be able to provide it tomorrow
i have tried everything as you said but after using the flash too and b4 installing recovery it says my phone is not rooted so it wont let me rename the recovery file. should i have a rooted system image in the scatter file cause i dont see one in the files i extracted. p.s. i downloaded all the files you linked so if im missing something can someone please point me in the right direction. thanks
blu dash 5.0 d410a v27
dlongnasty said:
i have tried everything as you said but after using the flash too and b4 installing recovery it says my phone is not rooted so it wont let me rename the recovery file. should i have a rooted system image in the scatter file cause i dont see one in the files i extracted. p.s. i downloaded all the files you linked so if im missing something can someone please point me in the right direction. thanks
blu dash 5.0 d410a v27
Click to expand...
Click to collapse
I probably need to redo the steps for a couple of the posts.
Download the TWRP at http://d-h.st/aQmt
Upload it to the phone. Make sure that only recovery is ticked in the Smart Phone Flash Tool (SP Flash Tool) and select the file you downloaded. You should be able to figure out the rest based on my instructions.
Flash SuperSU which can be downloaded from http://download.chainfire.eu/supersu
It will rename the file that would put back the original recovery.
That should be it.
got it working thanks. are their any custom roms for the d410a?
{
"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"
}
MultiROM is one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must NOT be encrypted (hint: if you don't know what it is, then it is encrypted).
To decrypt your device:
Backup ALL your data if you need to recover later (TWRP backup to USB or copy to your PC)
In fastboot mode:
Code:
fastboot format userdata
In TWRP: Flash Magisk (recommended) or SuperSU to avoid auto-encryption in next boot.
MultiROM has 2 parts you need to install:
Modified recovery (TWRP). Flash it as usual TWRP (fastboot flash recovery, or any flasher app if you're rooted).
MultiROM. Install it as usual zip from modded TWRP once flashed.
Go into TWRP MultiRom settings and be sure that "Enable No-KEXEC Workaround" is enabled (enabled by default)
Your current rom will not be erased by the installation.Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 6.x after first boot takes 900+mb of space.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
MIUI ROM as Secondary <--- Latest versions fix this, so you shouldn't need it anymore
Install MIUI as secondary via MultiROM settings in TWRP
Boot into your (rooted) primary
Edit fstab.qcom file in /storage/emulated/multirom/roms//boot/ and add /cache partition entries:
Code:
/dev/block/bootdevice/by-name/cache /cache f2fs nosuid,nodev,noatime,inline_xattr,flush_merge,data_flush wait,check,formattable
/dev/block/bootdevice/by-name/cache /cache ext4 nosuid,nodev,noatime,barrier=1 wait,check,formattable
Alternatively you can use attached file "fstab.qcom.txt" (rename to: fstab.qcom without .txt ). Be sure to set proper permissions (copy from original fstab.qcom, after renaming to fstab.qcom.bak, don't delete it...)
DON'T FORGET to flash Magisk / SuperSU after flashing to avoid re-encryption if you're flashing stock (not modded).
Known issues
You must wait a few seconds (3-5) before you get touch screen responsiveness in TWRP and MultiROM. (fixed by 2017.08.01 build) -- USUAL WHEN SWITCHING FROM MIUI
Some FCs on some secondary ROMs: Try using multiromfix.zip, thx to @Startrek852 (to disable sdcardfs support in that secondary) -- USE MAGISK 13.5+
Issues with TWRP to boot on 4GB/128GB model... (Working on troubleshooting...) -- PRELIMINARY FIX HERE
Reporting issues
As you surely understand, a simply "it does NOT work" is not enough... so please, report your issue describing scenario as much as you can, try following this (as much as possible information is welcome, it's very tiring for me asking what this, what that, etc...):
Issue description (what, how, when, etc...)
Device model : 4GB or 6GB RAM
Decrypted? /cache and /data FSs ? (We assume IS decrypted becaues you're using MultiROM, and EXT4 FS for /cache and /data if you don't know or manually formatted to F2FS)
TWRP version + MultiROM version
Primary ROM (name, better with version)
Firmware version
Secondary ROM (the one with the issue, name and better version)
Custom kernel ? (name and version if so) <--- In theory, we shouldn't support scenarios with custom kernels.... (they can touch system stuff that make things more complex)
Xposed ? <--- Sorry we DON'T support MultiROM if you use Xposed
Google Apps (name, better with version)
Magisk / SuperSU (version and if you use it in Primary and/or Secondary and version)
Logs <--- This would be amazing great and helpful !!!! (you can get them via adb shell, terminal or using any tool)
*Original post and example in this post, please:
Download
You can download all stuff from here, where you can find latest TWRP and MultiROM. If you need to uninstall MultiROM, you can use this uninstaller.
MultiROM Manager (apk) available here.
Source code
MultiROM - https://github.com/MultiROM-dev/multirom
Modified TWRP - https://github.com/multirom-dev/Team-Win-Recovery-Project
MultiROM device tree - https://github.com/BitOBSessiOn/android_device_xiaomi_lithium
Special thanks to:
@Tasssadar for creating this awesome utility
@nkk71 for the No-KEXEC workaround
@AdrianDC and all MultiROM guys involved in its development
@jcadduono for TWRP port
We will have to try soon... It's the perfect set up for flashaholics
Great news [emoji847][emoji847]
Envoyé de mon MIX en utilisant Tapatalk
I can't make it work
fil0s0f0 said:
I can't make it work
Click to expand...
Click to collapse
The MultiROM app from market is only for official devices (I haven't updated the Android app, imo it's not very useful), So you must follow OP steps.
If you have some issue, please, describe your problem and we will try to help.
Keep in mind that you must have unlocked bootloader, decrypted device, etc...
Device decrypted, bootloader unlocked, and well, there is no instructionbon op but, I figure out and I'll leave my feedback
fil0s0f0 said:
Device decrypted, bootloader unlocked, and well, there is no instructionbon op but, I figure out and I'll leave my feedback
Click to expand...
Click to collapse
Yes, there are, please, revise OP, and describe which steps have you followed to find out what's your issue. Thx
provided TWRP wont boot into it after flash. shows some scrambled image, shows animation with MultiRom image but wont enter recovery
also command: fastboot flash userdata
gives this output
Superb, I missed it in this great smarphone
acasmc said:
provided TWRP wont boot into it after flash. shows some scrambled image, shows animation with MultiRom image but wont enter recovery
also command: fastboot flash userdata
gives this output
Click to expand...
Click to collapse
Sorry:
fastboot format userdata
I correct OP.
The TWRP is tested... I will revise.
BitOBSessiOn said:
Sorry:
fastboot format userdata
I correct OP.
The TWRP is tested... I will revise.
Click to expand...
Click to collapse
could it be, that while I'm encrypted TWRP will not work? flashed it with Rashr and fia Fastboot method. didnt work either way.
acasmc said:
could it be, that while I'm encrypted TWRP will not work? flashed it with Rashr and fia Fastboot method. didnt work either way.
Click to expand...
Click to collapse
Too weird... I've just downloaded and flashed again with rashr and ok.
Which model do you own (128/256)? Primary rom...?
TWRP must work ok with encrypted /data (but you need decrypted for MultiROM).
I'm on latest Miui China Beta Developer ROM (7.7.20), model is 128Gb/4Gb
Mr.Raines TWRP is working fine for me.
acasmc said:
I'm on latest Miui China Beta Developer ROM (7.7.20), model is 128Gb/4Gb
Mr.Raines TWRP is working fine for me.
Click to expand...
Click to collapse
Can you try some of older versions in testing or backup folder in n AFH, please...?
Can you take a photo of error if it still occurs...?
there is only one TWRP in your folder. can you point me to another. I'll try no worries
acasmc said:
there is only one TWRP in your folder. can you point me to another. I'll try no worries
Click to expand...
Click to collapse
You can see /bak and /testing folders here:
https://www.androidfilehost.com/?w=files&flid=201564
Great mod, I was been using Dual boot patcher app to boot into multiple roms(currently 5 roms). Hopefully this mod makes the things easier than before lol. I may give it a go when i feel a fully clean start. Thanks for providing the mod[emoji106]
Konsstantine34 said:
Great mod, I was been using Dual boot patcher app to boot into multiple roms(currently 5 roms). Hopefully this mod makes the things easier than before lol. I may give it a go when i feel a fully clean start. Thanks for providing the mod[emoji106]
Click to expand...
Click to collapse
Usually I don't start to develop for a device before I can use MultiROM....
BitOBSessiOn said:
You can see /bak and /testing folders here:
https://www.androidfilehost.com/?w=files&flid=201564
Click to expand...
Click to collapse
tried other two that are on that link. still the same. sadly don't have another phone with me, to take a picture.
guess gonna have to wait for an update. :/
BitOBSessiOn said:
Note 1: Your device must NOT be encrypted (hint: if you don't know what it is, then it is encrypted).
Click to expand...
Click to collapse
About encrypting, Is it enough to flash the "no-verity-opt-encrypt-5.1".zip?, And if its not, Is there a guide of how to encrypt my device?
I rooted my HTC U11+ using Magisk without having TWRP installed. I can't find the link anymore, but I think it was through fastboot and if I remember correctly, I had to format /data after installing Magisk due to the device encryption. Everything is working fine.
Today I got a notification that a new firmware with the version number 1.24.401.2 is available (current version is 1.10.401.23). I'm pretty sure if I install it, i I will loose root and I would have to install Magisk again to gain root back which would require to format /data. I would like to prevent that since I've spend ages to configure and adjusting everything to my needs and I'm not keen to do that again.
Is there a way of installing the OTA update without loosing root and having to wipe /data?
midiwidi said:
I rooted my HTC U11+ using Magisk without having TWRP installed. I can't find the link anymore, but I think it was through fastboot and if I remember correctly, I had to format /data after installing Magisk due to the device encryption. Everything is working fine.
Today I got a notification that a new firmware with the version number 1.24.401.2 is available (current version is 1.10.401.23). I'm pretty sure if I install it, i I will loose root and I would have to install Magisk again to gain root back which would require to format /data. I would like to prevent that since I've spend ages to configure and adjusting everything to my needs and I'm not keen to do that again.
Is there a way of installing the OTA update without loosing root and having to wipe /data?
Click to expand...
Click to collapse
Would the following be helpful?
Haven't tried myself yet.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Thank you for the link DanteGR. It looks promising.
I'll have to find out if my HTC U11+ is supported by FlashFire. It most likely doesn't have two partitions (A/B).
So if somebody knows if the U11+ is working with FlashFire, please let me know!
Is there a way of backing everything up in case something goes wrong with with the OTA update using FlashFire? I'm not keen on loosing all the adjustments and settings I made in the last couple of weeks (I even modified files in /data/data to fix App issues). As far as i know Nandroid backups are not possible because the currently available TWRP recovery for the U11+ doesn't support data decryption. I have backups to Google Drive enabled (with all options including App data), but I don't know if that is enough to bring the system back into the current state afterwards.
midiwidi said:
Thank you for the link DanteGR. It looks promising.
I'll have to find out if my HTC U11+ is supported by FlashFire. It most likely doesn't have two partitions (A/B).
So if somebody knows if the U11+ is working with FlashFire, please let me know!
Is there a way of backing everything up in case something goes wrong with with the OTA update using FlashFire? I'm not keen on loosing all the adjustments and settings I made in the last couple of weeks (I even modified files in /data/data to fix App issues). As far as i know Nandroid backups are not possible because the currently available TWRP recovery for the U11+ doesn't support data decryption. I have backups to Google Drive enabled (with all options including App data), but I don't know if that is enough to bring the system back into the current state afterwards.
Click to expand...
Click to collapse
No problem.
AFAIK unfortunately there isn't a way for a full backup without a completely functioning TWRP.
If rooted, Titanium would be your best bet but not for everything obviously.
midiwidi said:
I rooted my HTC U11+ using Magisk without having TWRP installed. I can't find the link anymore, but I think it was through fastboot and if I remember correctly, I had to format /data after installing Magisk due to the device encryption. Everything is working fine.
Today I got a notification that a new firmware with the version number 1.24.401.2 is available (current version is 1.10.401.23). I'm pretty sure if I install it, i I will loose root and I would have to install Magisk again to gain root back which would require to format /data. I would like to prevent that since I've spend ages to configure and adjusting everything to my needs and I'm not keen to do that again.
Is there a way of installing the OTA update without loosing root and having to wipe /data?
Click to expand...
Click to collapse
As you, I have root but no TWRP installed. I did the OTA update and I didn't lost my data. I lost root during the process but it was very easy to install it back without loosing or wipe data.
If you have installed Magisk via patched boot.img, here is what I have done :
-Go in Magisk, choose uninstall and then "restore image"
-Then, go check for update on your phone and start it.
-At the same time, download stock RUU rom (the same as the OTA, here for European version : https://forum.xda-developers.com/htc-u11/development/htc-u11-stock-rom-ruu-t3741849) and extract boot.img from it with RUUdecrypttool (https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928). It can be long.
-When update is complete and you have extracted boot.img, put it in your phone and patch it with magisk : install, patch boot image. Then you will have a "patched_boot.img" in your magiskmanager folder. Copy this file on your PC.
-Go to download mode on your phone and flash patched_boot.img via Flashtool.
Root is back, no data lost :good:
Kidy973 said:
As you, I have root but no TWRP installed. I did the OTA update and I didn't lost my data. I lost root during the process but it was very easy to install it back without loosing or wipe data.
If you have installed Magisk via patched boot.img, here is what I have done :
-Go in Magisk, choose uninstall and then "restore image"
-Then, go check for update on your phone and start it.
-At the same time, download stock RUU rom (the same as the OTA, here for European version : https://forum.xda-developers.com/htc-u11/development/htc-u11-stock-rom-ruu-t3741849) and extract boot.img from it with RUUdecrypttool (https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928). It can be long.
-When update is complete and you have extracted boot.img, put it in your phone and patch it with magisk : install, patch boot image. Then you will have a "patched_boot.img" in your magiskmanager folder. Copy this file on your PC.
-Go to download mode on your phone and flash patched_boot.img via Flashtool.
Root is back, no data lost :good:
Click to expand...
Click to collapse
Just a heads up.
I think for OTAs only (NOT RUUs) you don't even have to use the decrypt tool.
The zip is already decrypted so just extract the boot.img.
EDIT: Not 100% sure though will try it out this evening.
DanteGR said:
Just a heads up.
I think for OTAs only (NOT RUUs) you don't even have to use the decrypt tool.
The zip is already decrypted so just extract the boot.img.
EDIT: Not 100% sure though will try it out this evening.
Click to expand...
Click to collapse
That is correct.
I have done it many times.
m3johan said:
That is correct.
I have done it many times.
Click to expand...
Click to collapse
Oh well.
Last night I downloaded a random OTA for the HK version and the firmware.zip inside it could not be opened I guess due to encryption.
Are you sure about that?
DanteGR said:
Oh well.
Last night I downloaded a random OTA for the HK version and the firmware.zip inside it could not be opened I guess due to encryption.
Are you sure about that?
Click to expand...
Click to collapse
I can not be 100% sure, but all I have unpacked including this 1.24.401.2 ota were no problem.
Can you give me the link to the HK-ota?
m3johan said:
I can not be 100% sure, but all I have unpacked including this 1.24.401.2 ota were no problem.
Can you give me the link to the HK-ota?
Click to expand...
Click to collapse
This is the one I tried to extract without success.
Just to make it clear. I had no problem extracting the actual OTA. The problem was trying to extract the firmware.zip inside it.
Thank you for your input.
https://www.androidfilehost.com/?fid=962187416754455026
DanteGR said:
This is the one I tried to extract without success.
Just to make it clear. I had no problem extracting the actual OTA. The problem was trying to extract the firmware.zip inside it.
Thank you for your input.
https://www.androidfilehost.com/?fid=962187416754455026
Click to expand...
Click to collapse
You are right. I could not unpack firmware from that one either.
Deleted
m3johan said:
You are right. I could not unpack firmware from that one either.
Click to expand...
Click to collapse
The decrypt tool doesn't seem too bad after all though.
I'll have to try it shortly.
For those who are using Taiwan model, what is your software number?
Mine is 1.23.709.9
RUU decrypt tool
DanteGR said:
The decrypt tool doesn't seem too bad after all though.
I'll have to try it shortly.
Click to expand...
Click to collapse
RUU_decrypt_tool works like a charm
the command on the command line is (in windows) RUU_decrypt_tool -f RUU file name (use TAB for name completion or rename to RUU.zip) (for firmware files) which gets you (see thumbnail)
The tool automatically has a output as "OUT" in the folder where it resides; I've put my RUU file in the ADB folder together wit the RUU_decrypt_tool
You'll find the RUU_decrypt_tool here
btw: I am 70 years young, so if I can do it most people can as well.....
If none of the required arguments are supplied a simple Yes/No interface will be presented.
Required arguments (and/or):
-s, --system extract the system.img and boot.img (for ROM)
-f, --firmware extract the firmware files
-z, --sdruuzip copy and rename rom.zip for SD-Card flashing
Note: this will create a duplicate if the input is already a rom.zip
Keyfile Updater arguments:
-o, --offline disable down/upload of keyfiles
--no-upload do not upload if a new keyfile is generated
--sync-keyfiles sync entire keyfile folder (download & upload)
when used without a RUU the tool will only synchronize the
keyfiles, otherwise it will download new keyfiles before decrypting
and upload only if a new keyfile is generated
Click to expand...
Click to collapse
When I used to have htc 10 s-on I could update the fw using a zip file(perhaps firmware. Zip) inside the OTA file for my cid and flash it in RUU mode, of course I had to use a custom rom based on the same fw to complete it
Finally, after a couple of month and being annoyed of the update message popping up all the time, I got some time to proceed with the update.
I found that what I've said in my first post isn't true. I had a non-official TWRP (without decryption support) installed and now remember that I have installed Magisk through that.
I've started the update procedure with clicking "uninstall" and "restore image" in the Magisk app. After downloading the OTA, I clicked on install now. My phone rebooted into recovery (TWRP) and prompted to enter my unlocking pattern. I entered it, but TWRP said something like can't mount, wrong password.
I thought it's because TWRP doesn't support decryption yet and I need to go back to the stock recovery to be able to apply the OTA. I extracted the recovery_signed.img from here (from the same software version I'm currently running 1.10.401.23) and flashed it using fastboot. If I boot into recovery now, I see it's the stock one, but it shows a red exclamation mark in a red triangle. I can press power button + volume up and get into the normal recovery menu. I've tried to wipe the cache there, but it didn't made a difference. I still get that red exclamation mark. If I download the OTA and click on install now, my phone restarts and shows the normal picture of applying the update until about 24% of progress and then it shows the red exclamation mark again. If I press power + volume up now, nothing happens.
If I manually boot into recovery and use power + volume up to get into the recovery menu, there are two options to apply an update. One using the sdcard and one using ADB. I have the hope that the red exclamation mark is gone once I installed the update manually.
The sdcard option doesn't work. The recovery shows the message can't mount /sdcard. The ADB sideload option causes problems too.
If I use a older version of ADB I get the error "cannot read OTA.zip" in my command window on the PC. I've tried it with a small text file and that worked. I read that it has something to do with the address space which is too small and that I should use the newest version from googles platform tools. I installed version 27.0.1 and used the contained ADB to do the sideload. This time I got an error message like "adb server version (31) doesn't match this client (36)", but it didn't say that it can't read the file.
I'm kind of stuck now. Has somebody a suggestion how to proceed, to get rid of the red exclamation mark so that I can normally apply the OTA update and gain root again afterwards by flashing a Magisk patched boot.img through fastboot?
midiwidi said:
...shows the normal picture of applying the update until about 24% of progress and then it shows the red exclamation mark again....
Click to expand...
Click to collapse
You have a modified /system partition. You will need to restore stock system partition of the version you are running to get past this.
You have a modified /system partition. You will need to restore stock system partition of the version you are running to get past this.
Click to expand...
Click to collapse
Thank you very much for this hint. I will do a
fastboot flash system system.img
tonight and let you know how it went.
I did flash the original system.img. Here the output of the command window
C:\Users\midiwidi\Downloads\HTC_U11+\Original_HTC_Firmware_Europe\OUT_2Q4D_1.10.401.23\system>fastboot.exe flash system system.img
sending 'system' (16384 KB)...
OKAY [ 1.651s]
writing 'system'...
(bootloader) HOSD CL#991677
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.461s]
finished. total time: 5.111s
Unfortunately that didn't change anything. I still get the red exclamation mark if I boot into recovery
{
"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"
}
.
Is there a log file or something similar to find out what the recovery is complaining about? This is the output after bypassing the red exclamation mark with power + volume up
.
Any other ideas how to proceed?
Unofficial release -TWRP recovery for the Galaxy J4 plus 2018 - SM-J415 MSM8917
{
"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"
}
TWRP 3.3.1-0 Released
May 22, 2019
TWRP 3.3.1-0 is out now for most currently supported devices.
What's new in 3.3.1-0:
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
Update - 17/8/2019
TWRP 3.3.1-1 OO/PP build released
Current status - Beta
Treble supported
Bugs: brightness slider
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
*****INSTALL INSTRUCTIONS:*****
Flash with ODIN in the AP slot.
1. Put your device in DOWNLOAD mode.
(Plug in the USB cable and then hold POWER + VOL DOWN + VOL UP)
2. Load the respective file below into the AP slot, uncheck Auto-reboot(not required for twrp_3.3.1-1) and hit start.
twrp_3.2.3-1_sm-j415f_30319
twrp_3.3.1-1_j415x_17819
3. After flashing and ODIN reports PASS immediately force reboot to recovery. (Not required for twrp_3.3.1-1 as it should auto reboot to recovery). You should now see TWRP recovery.
Do NOT let the device boot to the OS.
4. Flash the V3 RMM bypass zip
https://forum.xda-developers.com/showpost.php?p=79745844&postcount=627
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT AND BECOMING RMM LOCKED FOR 7 DAYS.
I ALSO SUGGEST BACKING UP ANYTHING YOU NEED ON INTERNAL STORAGE. AT SOME POINT YOU MAY EXPERIENCE A 'VERIFICATION FAILED MESSAGE' .
THIS IS NORMAL, BUT WILL REQUIRE THE DATA PARTITION TO BE FORMATTED IN TWRP.
5. Reboot to TWRP (Do not boot to the OS yet)
***** ROOT INSTRUCTIONS:*****
OREO ONLY
1. Flash the Forced encryption disabler patch. This is only required if you wish to have full functionality in TWRP.
Flashing this will disable Samsung's forced encryption. Disabling encryption will allow TWRP to mount the data partition.
After flashing the patch it is necessary to *FORMAT* (not wipe) the /DATA partition using the FORMAT DATA button under the wipe options.
PLEASE NOTE THIS WILL DELETE EVERYTHING ON INTERNAL STORAGE AND FACTORY RESET THE DEVICE, SO BACK UP ANYTHING YOU WISH TO KEEP.
J4+J6+_oreo_forced_encryption_disabler
2. To root I suggest installing the latest Magisk beta as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
(NOTE: The DEFEX patched Oreo kernel below may be needed for full root support if certain apps do not work with root):
https://androidfilehost.com/?fid=1395089523397921797
3. Enjoy your rooted device.
PIE ONLY
1. Due to some new securities in Samsung's latest Pie kernels, root will not work with the stock kernel. The patched kernel below is required to gain root on Pie.
Features:
Dmverity, proca, five and defex disabled.
OTG and NTFS file system support.
Selinux permissive switchable.
This kernel may require the U4 bootloader.
(NOTE: flashing a custom kernel on PIe breaks the lockscreen. Ensure NO lockscreen is enabled before installing the kernel.)
J415FXXU4BSF7_patched_boot_318919
2. To root I suggest installing the latest Magisk beta as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/app...mless-t3473445
3. If you wish to have access to internal storage /DATA in TWRP then encryption will need to be disabled. See step 1 of the Oreo root instructions then instead of installing the J4+J6+_oreo_forced_encryption_disabler install the zip below with TWRP:
Disable_Dm-Verity_ForceEncrypt_Quota_08.02.2019
3. Reboot.
The device will take a good 10 mins to boot first time.
Enjoy your rooted device.
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my tester @kapmino269 [MENTION=6037748]Zackptg5 for the DM-VERITY & FORCEENCRYPT DISABLER @teamwin, @corsicanu for RMM V3 bypass zip.
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
kapmino269 said:
Thank you very much for building twrp but there are bugs :
1- After I make steps all is done I power off it but when I open it isnot boot & i see a message All the words I understood that "you flash unauthornized boot.img & recovery img and return the phone to the company to fix the phone" and phone didnot boot I recognize that when I open internet in phone samsung detect the change in phone so i solved it by:
:good: I repeat the steps but after i connect to internet , i activate magisk and close wifi and download afwall on my sdcard from appkpure by pc and install the app an enable firewall and solved but there message that rules not apply but in fact it is applied and all is done . SOLVED
2-When I close phone and recharge it, it isnot recharged but it continue rebooting not to system but just recharge windows and poweroff and agian to recharge window And so on .
I coulding solve but I sure the error is in boot.img or in another . NOT SOLVED
Sorry for my english.................
Click to expand...
Click to collapse
Thanks for all the info, but does TWRP actually boot?
kapmino269 said:
Twrp is very very good and backup and restore and mount are good but there are bugs in system not in recovery addition the last:
3- the percentage of battery when charging,it isnot change . NOT SOLVED
What is the reason ?
Click to expand...
Click to collapse
Percentage doesn't change in twrp or when power off?
kapmino269 said:
SORRY MR ashyx there isn't bugs in system my charger was cut and it is the reason of rebooting to recovery. But bugs in recovery brightness control and backup encryption.
And your build is good ask twrp.me to make it official.
Click to expand...
Click to collapse
You will need to Format (not wipe) /data to remove encryption and mount the data partition. Samsung encryption isn't supported yet by TWRP.
Brightness isn't a deal breaker, but I'll look into it.
Could you do me a favour and post the recovery.log so I can check it over?
kapmino269 said:
And I forget said that all afwall versions above 2.9.9 doesn't work and Samsung will lock the phone and you should download afwall with date 5/2018
Click to expand...
Click to collapse
What do you need AFwall for?
kapmino269 said:
To prevent Samsung apps detect the change on the boot.img and recovery.img and so on and I told you at first that after flashing and activate magisk I set wifi on and when I power off the device and open it ,I couldn't open phone on any mode ,there is message apear to me told if I boot to system it said as I remember and I understand that "there is boot.img flash to phone by unauthorized way please return device to company or someone you buy the device from him to fix the phone " and replacing when reboot recovery boot.img by recovery. img and as I remember the screen was blue and the text was written in black and red. so I flash sammobile stock with Odin and repeat your twrp installing steps and activate magisk and close wifi and put afwall 2.9.9 (above versions didn't work ) and the error didn't appear again .
Click to expand...
Click to collapse
I don't think that you need AFwall. When you see that message boot to TWRP and format your device, install Magisk and the Oreo encryption disabler.
This should prevent this message appearing again.
Also disable securitylogagent apk.
Can this be used to flash GSI?
Jason Grewal said:
Can this be used to flash GSI?
Click to expand...
Click to collapse
As posted in the OP :
Update 8/12/2018
Current status - Beta (Tested working)
Treble supported
Bugs: brightness slider
Click to expand...
Click to collapse
kapmino269 said:
sorry I see another error in restore in TWRP .
all partitions restored but when I finish restore twrp said unable to mount /system and I couldn't reboot system
Click to expand...
Click to collapse
Have you tried backing up only system again then immediately restoring?
Also which media are you restoring from?
Also need the recovery log after failure.
kapmino269 said:
A1 :No , I will try backup system and system image only.
A2 :I restore from usb otg .
A3 :It success in restore efs boot vendor and others but system not mount and tried to return system again .
££i flash sammobile rom and install magisk as you tell and restore all phone partitions Except system and system image ££ The phone open again.
###I will try restore system again and i will sent you recovery.log BUT WHICH MEDIA I SHOULD USE USB OTG OR SDCARD ###
I am sorry for disturb.
Click to expand...
Click to collapse
Can you try backing up just system, not system image to internal storage then try restore?
kapmino269 said:
ok, I will try .
I would ask you about something else but sending you private message unanable I need to ask you but i couldnot because the question is about something else twrp for j415f how to send the issue to you
Click to expand...
Click to collapse
If it's related to this device then just post it. I don't accept pm's.
kapmino269 said:
A-Restoring system only and other partition is done and succeed and faster from internal storage but if i copy it to pc or sdcard Is all files will copied or not or Error will apper after copy (restoring again).
Thanks for your help .
1- it is related to j415f some apps like busybox and linux deploy and afwall(new version) grant root access but didnot run.
2- #
Another problem :
no,it isnot .it related to wlan monitor mode for gt-i9500 (internal (bcm4335 ) or external (TL-WN22N) ) , I tried linux deploy kali hunter nexmon others ,and please reply if you could help me or reach me to someone help me .
#
please reply me quickly about (2) to delete it
SORRY I havenot any way to reach you except this .
Click to expand...
Click to collapse
1. Isn't really related to twrp but magisk itself. Better posting in the magisk thread.
2. Unfortunately can't help you with this as I don't mess around too much with that kind of stuff.
I wouldnt dare to do anything on this before everything is 100% clear and failproof. This phone behaves like its about to collapse every second idk why but it feels like that
kapmino269 said:
Thank you very much for your help and your interest .
Please ,Can you fix restoring system from usb otg ? and all files you need from me i will send you it ,
you must make your twrp ideal and make it official in #twrp.me# like Alberto86(recognise developer) : make gt-i9500 twrp and ge officialty .
surendrajat(member ) : Make SM-J737S twrp it is in #twrpbuilder.github.io#
I think you should publish the recovery in this sites at the nearest time. I think also you should make video on youtube to make your project spread out faster ,because there are people donot know xda ,I tried to make video but my presentation was very bad so i delete it from youtube .
And Sorry for distrubt
Click to expand...
Click to collapse
I don't think there is anything to fix regarding the restorating of a backup from OTG.
It's just simply a case of some media is not suitable for backup and restore.
I've even seen reports of certain MicroSD cards causing issues with TWRP.
It's likely that if you try a different USB stick you won't have any issues.
As regarding making it official. I will consider it. However I have many, many builds of TWRP for a lot of other devices that are not official either.
This is due to the fact I do not like the convoluted system of getting it made official.
I have discussed this previously with teamwin and asked for a proper submissions page to no avail.
kapmino269 said:
Ok as you like but you can improve twrp .
I mean :
1 -Could you compress encryption disable and
rmm bybass and recovery in twrp.tar file to flash it by odin in one step wihout following install steps that you write , Steps may be difficult with others , With me I try serval times to success and i know some skills about android but others may donot know .
2 - Why your twrp depend on magisk install
,if magisk doesnot install phone doesnot reboot system , I think twrp should not be depend on root & If some one need twrp and doesnot need root.
3 - Busy box i cannot install it in my phone why ,?
Click to expand...
Click to collapse
No I cannot make an all in one to flash in ODIN.
Firstly because its not possible. Odin cannot run scripts, only recovery can.
Secondly if people cannot follow instructions then maybe they shouldn't be attempting to modify their device.
TWRP doesn't depend on Magisk, your device does.
Samsung incorporate many security hurdles to prevent hacking and modification.
These security blocks need to be patched or the device will not boot.
These blocks can be patched manually, however Magisk can patch most of these during the root process.
I have no idea why you cannot install busybox on your device as you have not provided any info of the issue.
In any case busybox is included with Magisk. To use it install the busybox module by osm0sis.
kapmino269 said:
picture
Click to expand...
Click to collapse
I see what your saying, however I will keep things as they are. I'd prefer people to have an understanding of what they are installing and I believe it's simple enough.
Unfortunately I can't help with the busybox issue. However as I stated you can use the busy module provided by osm0sis.
He keeps everything up to date and is highly recommended.
kapmino269 said:
I face issue :
I test j4+ snd s4 security in lookscreen :
1- In j4+ : if I delete /data/system/locksetting.db or all contain locksetting name in twrp buy terminal or file manager or script.
2 -add delete *.key on s4 .
Is there solution from system or twrp to prevent lock screen crack or it hash stolen to crack not tell me (chattr).
Thank you
Click to expand...
Click to collapse
If I'm reading it correctly you want a way of preventing the lockscreen credentials from being deleted.
The only way is to remove TWRP Tbh so no one had access to the file system.
Also this isn't really a twrp related issue and a little off topic.
However I have been looking at possible ways to password TWRP thus preventing access at all.
But even that could be circumvented by simply flashing another version of TWRP.
The only safe way is to remove twrp, unroot your device and disable OEM unlock.
kapmino269 said:
1 - I donot have any ways to reach you and you is the developer of twrp for j4+ and Know all about it and you donot accept pm , I could make
thread and you answer me in it but this issue in twrp so all is well .
2 - I want twrp and root ,Is there any solve ,I have idea may success sent me it may be sucess or not
it is
1- make data partition not mount or read only on twrp .
2- when I need to install something I will mount it by writing command in system terminal only (that command or script or program doesnot be found in twrp ) to be mounted in recovery mode .
3- I mean that data not mount in twrp without enable mounting in system and twrp doesnot have permission to mount data without system access .
but how this will acheive without you man .
another idea the same but replace mounting by read only
Click to expand...
Click to collapse
If you don't want data to be mounted in twrp then why not just leave it encrypted. Then only you have access to it via the OS?
Failing that just remove the mount entry for /data from the fstab.
This way data will only be available and mountable by using terminal commands.
The other way is to only install twrp when you need it.
For example you could use a script which you could run to flash twrp when booted to the OS each time you need it or if you prefer use something like flashify.
When you are done with twrp, simply use the restore option to restore the stock recovery.
This way only you have access to /data.
how to do this on galaxy J4?pls. help
i have a lock bootloader in download mode
Has anyone tried any gsi?
I tried havoc os 2.0 didn't work.