Database Info

[App] Root Toolkit for Android™

.
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

[Pre Rooted Stock]No wipe,No flash counter raise + Guide How to make Prerooted ROM

Pre Rooted Stock ROM
Here is complete stock Pre rooted ROM
( MUST READ THIS before flashing DMF2/ME6 or any newer )
July13
N7100XXDMG1_N7100ODDDMG1_N7100DDDMG1- Deodexed - India - Download - Detail here
N7100XXDMG1_N7100ODDDMG1_N7100DDDMG1- Odexed - India - Download
June13
N7100XXDMF2_N7100OLBDMD2_XME - Malaysia - Download - - - Mirror
SuperSu updated to latest 1.34
Package have addition mod zip file which is optional, If you want to install that mod, instead using packed one use this
April 2013
N7100XXDMC3_N7100ODDDMD1_N7100DDDLK6 (INU) -India - Download
March 2013
N7100XXDMC3_N7100OXXDMC2_N7100XXDLK7 (XEO) - Poland - Download
Installation Instruction
- Download ROM and extract to ***.tar.md5 (unzip tool)
- Make sure you have installed Kies OR Samsung USB driver
- Open up the S/W Installation Program by executing the Odin3 v3.04.exe
1. Enable the check mark by click on the following options(default Option)
- Auto Reboot, and F. Reset Time
- Check PDA, and point to ROM file you have extracted
{
"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"
}
File name shown in above image is for demo purpose, you have to select according ROM you have download
2. Now switch off device and Enter into Download Mode
- Enter into Download Mode by pressing Volume Down button, Home Key and
Power Button simultaneously. And then, press Volume UP button in Warning Page to enter the Download Mode.
3. Connect the device to PC via Data Cable.
Make sure that the one of communication port [ID:COM] box is highlighted in
light blue. The device is now connected with the PC and ready to download the
binary file into the device.
4. Start downloading binary file into the device by clicking Start Button on the screen.
the green colored "PASS!" sign will appear on the upper-left box if the binary file has been successfully downloaded into the device.
5. Disconnect the device from the Data cable.
6. Once the device boots up, you can check the version of the binary file or name
by pressing the following code in sequence;
*#1234#
After flashing your device will have SuperSU in application drawer. If you want to unroot it, open SuperSu - settings - Full unroot.
First thing I do recommend after rooting device is
EFS Backup
Why so?
EFS folder contains some important and some basic info related to our device identity like Wi-Fi address, Bluetooth MAC address and the very main IMEI address (nv_data.bin).
Now if this EFS partition accidently corrupted then your phone’s IMEI no. will erased and you can not make voice call further. This kind of damage is often not accepted by the service center of your respected handset’s company.
Here your backup can only be savior for you.
-This is pure samsung stock ROM as it is + Root
-Non wipe
-Won't raise flash counter.
- Non Hotfile link
Again to make it clear, there is no any additional changes except pushing superSU (busybox added to April 2013 and onward), so there won't be have any difference from stock ROM, but you will not need to Root / reset counter. Just note that, flashing prerooted ROM doesn't reset counter, If your flash counter already raised flashing this ROM doesn't reset it, but you can use triangle away to reset counter after flashing this ROM. later you can uninstall triangle away.
Rooting is not difficult but still many users scare from it, this will come handy to them.
There is no plan to make every release Pre rooted, when there will be major update and myself update device that time will make that ROM pre rooted.
There is already thread in dev section by as i9000, which also have deodexed version and many other ROMs with multi CSC and regularly updating too. This thread will update only ROMs which i am using, as well basic aim is to write tutorial abiut how to make pre rooted ROM.
There are two other MB6 and DMB2 India are ready but really finding difficulty to upload. still i will try my best to upload it.
- Password to unzip - when there is any password to unzip, file name itself will have it.
- difference in file size from sammobile stock rom size is just due to different compression method, once you extract it will be same.
How to make prerooted stock ROM.
Requirements :
Ubuntu and login as Root user.
Ext4_utils - extract to home directory
Root files (su and Superuser.apk) - copy to home directory
busybox - copy to home directory (optional)
Procedure :
1.Download ROM you need to preroot and rename stock.tar.md5 (just to make command line input easy)
2.Extract ROM
Code:
tar xvf stock.tar.md5
3.convert system.img to ext4 so we can mount it.
Code:
./simg2img system.img newsys.img
4.delete system.img
Code:
rm -f system.img
5.Create temp folder and mount it
Code:
mkdir temp
mount -o loop newsys.img temp
6.Push root and busybox file to system and change permission
Code:
cp su temp/xbin/su
chmod 06755 temp/xbin/su
Code:
cp Superuser.apk temp/app/Superuser.apk
chmod 0644 temp/app/Superuser.apk
Code:
cp busybox temp/xbin/busybox
chmod 04755 temp/xbin/busybox
7.Conver newsys img to samsung system.img format
Code:
./mkuserimg.sh -s temp system.img ext4 tempdir 2048M
8.unmount and delete temp folder
Code:
umount temp
rmdir temp
9.create odin flashable tar file (here file names depends on files you have got by extracting ROM)
Code:
tar cvf prerooted.tar boot.img cache.img hidden.img modem.bin recovery.img sboot.bin system.img tz.img
10. add md5 checksum
Code:
md5sum -t prerooted.tar >> prerooted.tar
mv prerooted.tar prerooted.tar.md5
Now Flash prerooted.tar.md5 with odin.
Delete following files from home directory to make it clean
stock.tar.md5
newsys.img
and all files extracted while unpacking tar in step 1.
Credits :
Chainfire for his SuperSu
Phil3759
Credits to following user for referring their works on different forum
jazzor, rizdroid, das7982, faria

Where is it sir?
Sent from my GT-N7100 using xda premium

As I have said
What's your opinion?
Do I update rom
Or
You want guide, how to make it yourself.
Sent from my GT-N7100 using xda premium

My choice is 2
Please provide complete guide
Sent from my GT-N7100 using Tapatalk 2

Make a guide. That way, people learn more.
Sent from my GT-N7100 using xda premium

i thought it was just about placing su in xbin and supersu.apk in app -.-
yeah unpacking repacking and all can be a damn headache

No offense, leave the dev part to those who deserve this denomination and stick with the Guide Guru image that you have built for yourself and for which you get lots of credits and praise. I'd choose option 2.
Thanks for your excellent work of guiding noobs like me and troubleshoot their problems.
P_

))))))
That's the same there! And for a long time!
http://forum.xda-developers.com/showpost.php?p=32260125&postcount=1
:laugh:

2 with noobie detailed please
Sent from my GT-N7100 using xda app-developers app

UBUNTU needed for this)

alexyuh said:
UBUNTU needed for this)
Click to expand...
Click to collapse
+1
Sent from my GT-N7100 using xda app-developers app

alexyuh said:
UBUNTU needed for this)
Click to expand...
Click to collapse
Not with cygwin.
Sent from my GT-N7100 using xda premium

UtkarshGupta said:
Not with cygwin.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
There are some limitations in cygwin. Ubuntu is best for this.
Sent from my GT-N7100 using xda premium

Please post guide so that we'd learn ourselves
Sent from my GT-N7100 using xda premium
---------- Post added at 09:22 PM ---------- Previous post was at 09:15 PM ----------
sharjackmission said:
2 with noobie detailed please
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
+1
Sent from my GT-N7100 using xda premium

Ok,
So will make complete Guide with link to all needed utilities. But may take some time.
Meanwhile try to upload pre rooted rom too, and will add link in op. (I have made two roms mb6 and mc3)
But really difficult to upload every rom, or to make specific on request.
Whenever there is major update and if I will update my device, that time will make that rom pre rooted.
Thanks for patience.
Sent from my GT-N7100 using xda premium

dr.ketan said:
Ok,
So will make complete Guide with link to all needed utilities. But may take some time.
Meanwhile try to upload pre rooted rom too, and will add link in op. (I have made two roms mb6 and mc3)
But really difficult to upload every rom, or to make specific on request.
Whenever there is major update and if I will update my device, that time will make that rom pre rooted.
Thanks for patience.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
I can help

How?
Sent from my GT-N7100 using xda premium

Option 1

madhuranand007 said:
Option 1
Click to expand...
Click to collapse
Sure
Within 5 min updating OP

dr.ketan said:
How?
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Advice to you ladies
http://forum.xda-developers.com/showthread.php?p=39848357#post39848357
http://forum.xda-developers.com/showthread.php?p=39286842#post39286842
You have incorrectly assembled system img.The composition of the image.
No busybox.No su in bin)))
resolution:
Code:
cd app
chmod 0644 Superuser.apk
My version:
https://hotfile.com/dl/202764580/bcb9aa2/system.img.zip.html

WIP Experimental DIY [Deodexed-Xposed Galaxy S5 Neo dirty-version

Xposed has been achieved with some long testing back and forth for Galaxy S5 Neo. Without the need of custom build recovery :victory:
Code:
method public Disclaimer();
You're allowed to take my work and create your own rom, or do anything with it.
I (Laststandingdroid) provide these files as/is by no EULA or anything else.
I share this with the community and you [I][B]don't[/B][/I] need to ask for permission.
Your cat, dog, horse or even your baby is allowed to take these files and put it in your phone without questioning me.
All i do ask is that you put correct credits. however if you don't want to it isn't a must i won't die, nor get a heart attack. I know how the internet works. people will always copy and being willing to take credits for others work ;)
.end method
Note this recovery is experimental, it was used for my personal testing but it is now released here.
Requirements:
Rooted Device (or not mandatory i guess)
Busybox
PC with odin
Custom Modified Stock Recovery with insecure adb
stock recovery here: (Odin tar) https://mega.nz/#!DgomiZAQ!1m7aU5ojoU7PCw4L7E8hmk7mCFo2z0f_sYafJHzN7XE (NEE)
Modified recovery (Odin tar)
https://mega.nz/#!jogHWBTC!jozQXYAdnfzblZNiUmei4RLnzgoFzQg3WAdsi-LDMPA
Flash with Odin
Stock deodex-xposed Download:
https://mega.nz/#!r8BzXQKD!YCJsATrxuXRg7-tiHFtJWRKc6Mt3fTQAYElzPR01uSo
DIY (Do It yourself) Method
1/ First you need to go to sammobile to download last available generic firmware OR download the one related to your carrier.
2/ You need to decompress twice (first is the zip from sam, 2nd the tar.md5 file) with Universal Extractor.
3/ you will see many file (boot, recovery....and system the one which is necessary).
4/ now we need to decompress system.img but you can't currently. We need to convert this file to ext4 format. So time to download some necessary extra files. (https://1fichier.com/?bz9rmuuap4)
5/ Decompress this zip file in c:\deodex and put inside the system.img
6/ run 1MODEXT4.bat. This will create a temp.ext4 file in this folder.
7/ Now you can open the temp.ext4 file with ext2explore.exe which is in the folder.
8/ Create a folder on your PC named "system". Go on ext2explore, select "app", framework", "priv-app" folder and right click and make "save". Choose the folder system, you created.
9/ Now you have all the odexed files we need to deodex
10/ Run "SVADeodexerForArt.exe" and precise the system folder you created. Tick all boxes. Wait until it deodex. See if there is no errors in window
11/ Watch inside the "deodex" folder. you will see app, priv-app & framework folder. Here are the deodexed files.
Optional step:
12/ If you want before pushing the files you can debloat the rom. Or include xposed files too as LastStandingDroid
Pre Built Files
1.Download the zip and extract it on your pc.
2. Flash modified recovery trough Odin
Reboot to system
adb shell
mount - remount,rw /system
rm -rf /data/dalvik-cache
4. Reboot into recovery (don't be fooled by the stock recovery, it is modified to get system mounted as r/w trough adb
5. Plug your phone to PC, and wait for adb to initialize (this can take up to 20 seconds)
6. Type: adb remount
7. type: skip this for now now to 8.
8. Type adb push *drag and drop the extracted system folder to cmd/terminal window. /system/
In the terminal you should now have adb push /path/to/system /system/
8. Wait until all files has been pushed
9. Reboot the device, it will take time to boot since it will rebuild dalvik-cache
Optional is to recover stock recovery
Thanks @wanam for his modified xposed version which makes it compatible with Samsung variants for 5 1+ @Chainfire for his insecure adbd which is used to mount the system as read/write in recovery. Without this this wouldn't be possible
Special thanks @WILMANS2M for testing and reporting back. @bolme123 for testing and reporting back. @Dennziil testing and reporting @kaodd for being funny and being happy that we work on this
Sent from my SM-G903F using Tapatalk

Bugs: your original /sdcard path might be replaced this will not remove your files it will rather just kill the path.
You can access the internal sd files using /storage/emulated/0/
Settings might force close sometimes, this only seems to happen if you go to app info from recent. Not sure what gives
At least it might takes longer to load
Sent from my SM-G903F using Tapatalk

{
"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"
}
Sent from my SM-G903F using Tapatalk

Think im missing something, but don't know what.
C:\Users\Dennis>adb shell
[email protected]:/ $ dd if=/dev/block/platform/13540000.dwmmc0/by-name/RECOVERY of=/sdcard/stockrecovery.img
000.dwmmc0/by-name/RECOVERY of=/sdcard/stockrecovery.img <
dd: /dev/block/platform/13540000.dwmmc0/by-name/RECOVERY: Permission denied

So laststandingdroid, no need of a permissive kernel to do this right ?
Envoyé de mon K00F en utilisant Tapatalk

If you follow this will it trigger Knox or other bits and does it require root for it to work?
Thank you very much for your work

Dennziil said:
Think im missing something, but don't know what.
C:\Users\Dennis>adb shell
[email protected]:/ $ dd if=/dev/block/platform/13540000.dwmmc0/by-name/RECOVERY of=/sdcard/stockrecovery.img
000.dwmmc0/by-name/RECOVERY of=/sdcard/stockrecovery.img <
dd: /dev/block/platform/13540000.dwmmc0/by-name/RECOVERY: Permission denied
Click to expand...
Click to collapse
You need to write su first sorry
WILMANS2M said:
So laststandingdroid, no need of a permissive kernel to do this right ?
Envoyé de mon K00F en utilisant Tapatalk
Click to expand...
Click to collapse
Not quite sure I used permissive kernel might work. But I use permissive one to be able to use viper4android
Tepes4 said:
If you follow this will it trigger Knox or other bits and does it require root for it to work?
Thank you very much for your work
Click to expand...
Click to collapse
Yes know will be triggered and it requires root ofc [emoji14]
Sent from my SM-G903F using Tapatalk

So maybe first install permissive kernel, 2nd flash cfautoroot and 3rd your method
Envoyé de mon SM-G903F en utilisant Tapatalk

WILMANS2M said:
So maybe first install permissive kernel, 2nd flash cfautoroot and 3rd your method
Envoyé de mon SM-G903F en utilisant Tapatalk
Click to expand...
Click to collapse
No idea on permissive kernel
Root shouldn't be needed as recovery can remount as r/w but it's recommended since some apps requires root
Sorry I posted this tutorial in a rush.
Will clear it later.
Other galaxy s5 neo users if you want deodex send me your system framework and apps in order to get deodexed system
Sent from my SM-G903F using Tapatalk

I finally succeed deodexed last sgs5 neo rom file G903FXXU1AOI5_G903FXEF1AOI1_G903FXXU1AOI7.
64-bit Deodexer for Android Runtime (Version 3.5 ?? 20/07/2015) © Valery Studenikin, 2015
Path to stock /system directory: D:\Deodex\5.1.1\system
Android 5.1.1: SM-G903F, LMY47X.G903FXXU1AOI5, changelist 5560999, Tue Sep 15 19:31:20 KST 2015
Processor architecture: \arm\
Files deodexed succesfully: 355, with errors: 0. CPU time: 00:23:46 (1426,132 sec.)
List of originally deodexed (within stock firmware) files, are left as they were originally:
/system/framework/com.google.android.maps.jar
/system/framework/com.google.android.media.effects.jar
/system/framework/com.samsung.device.jar
/system/app/Bridge.apk
/system/app/minimode-res.apk
/system/app/RCPComponents.apk
/system/app/SecurityLogAgent.apk
/system/priv-app/ContextProvider.apk
/system/priv-app/HealthService.apk
/system/priv-app/intelligenceservice.apk
/system/priv-app/SPDClient.apk
LastStandingDroid i see in your zip file that some app were not deodexed as GMScore...Normal ?
I will try to push mine and try your method and will make a factory reset to see what's happening.

WILMANS2M said:
I finally succeed deodexed last sgs5 neo rom file G903FXXU1AOI5_G903FXEF1AOI1_G903FXXU1AOI7.
LastStandingDroid i see in your zip file that some app were not deodexed as GMScore...Normal ?
I will try to push mine and try your method and will make a factory reset to see what's happening.
Click to expand...
Click to collapse
Yes gms core failed I don't care about it since it isn't needed.
Edit shealth is broken download an update trough Samsung apps or download: https://mega.nz/#!3lwmEaKQ!f3iG_WQrK4hTXumHZbo0Jvs5DT9O0UC1TDlLRr4kH4s
Install as an update.
Sent from my SM-G903F using Tapatalk

Just 3 questions :
1/ Do we need to keep folders of apk. Can we put only apk in folder app or priv-app like xposed apk ?
2/ What do you add to the deodexed rom apart xposed file ?
3/ About xposed file :
in app : XposedInstaller.apk
in lib : all files
in framework : XposedBridge.jar
That's all we need ?
I really thank you.
Next step : The dirty flash

WILMANS2M said:
Just 3 questions :
1/ Do we need to keep folders of apk. Can we put only apk in folder app or priv-app like xposed apk ?
2/ What do you add to the deodexed rom apart xposed file ?
3/ About xposed file :
in app : XposedInstaller.apk
in lib : all files
in framework : XposedBridge.jar
That's all we need ?
I really thank you.
Click to expand...
Click to collapse
Depends on what you mean to keep folders?
There's only xposed added and needed files.
There's also files in system/bin app_process oat2dex patchoat and two more check the zip file xposed containing
Now it's ice fishing
Sent from my SM-G903F using Tapatalk

LastStandingDroid said:
Depends on what you mean to keep folders?
There's only xposed added and needed files.
There's also files in system/bin app_process oat2dex patchoat and two more check the zip file xposed containing
Now it's ice fishing
Sent from my SM-G903F using Tapatalk
Click to expand...
Click to collapse
For ex, for the folder "AccuweatherPhone2015" we have inside "AccuweatherPhone2015.apk"
I just wonder if we can just put "AccuweatherPhone2015.apk" inside "app" folder without the folder "AccuweatherPhone2015"

Feel like a noob now, but when i type (adb shell su) in cmd, it gets locked. :S

WILMANS2M said:
For ex, for the folder "AccuweatherPhone2015" we have inside "AccuweatherPhone2015.apk"
I just wonder if we can just put "AccuweatherPhone2015.apk" inside "app" folder without the folder "AccuweatherPhone2015"
Click to expand...
Click to collapse
No since apps requires lib folders and stuff in arm/lib
Dennziil said:
Feel like a noob now, but when i type (adb shell su) in cmd, it gets locked. :S
Click to expand...
Click to collapse
Where do you type it? While phone is on?
Anyway I'll upload a stock recovery and modified as Odin tar file
Modified recovery flash able trough Odin comes soon
Sent from my SM-G903F using Tapatalk

LastStandingDroid said:
No since apps requires lib folders and stuff in arm/lib
Where do you type it? While phone is on?
Anyway I'll upload a stock recovery and modified as Odin tar file
Modified recovery flash able trough Odin comes soon
Sent from my SM-G903F using Tapatalk
Click to expand...
Click to collapse
I hope! because I'm a little bit lost :crying::crying:
noob I am, noob I stay

LastStandingDroid said:
Anyway I'll upload a stock recovery and modified as Odin tar file
Modified recovery flash able trough Odin comes soon
Sent from my SM-G903F using Tapatalk
Click to expand...
Click to collapse
Great, then i'll just waint for the tar file insted Great work btw :good:

mmh i will try to delete all apk folder which does not have other file/folder inside than the apk one. In fact, only some folder have lib...folder inside. Most have only apk.
Will try.
As i said, will make a few test

androidissime said:
I hope! because I'm a little bit lost :crying::crying:
noob I am, noob I stay
Click to expand...
Click to collapse
Don't worry it comes in some minutes
Dennziil said:
Great, then i'll just waint for the tar file insted Great work btw :good:
Click to expand...
Click to collapse
Yeah I forgot about that
WILMANS2M said:
mmh i will try to delete all apk folder which does not have other file/folder inside than the apk one. In fact, only some folder have lib...folder inside. Most have only apk.
Will try.
As i said, will make a few test
Click to expand...
Click to collapse
Sure I don't recommend it since I see no reason to use it that way [emoji14]
Hopefully sooner or later I'll get a modified system.Img working there's no eta for that though. Since it yet doesn't flash in Odin.
Sent from my SM-G903F using Tapatalk

Extracting CSC from .tar.md5 file

Hello all, I love all the support from the developers who make our ROMs so great and was wondering the following question. Does anyone know how you can extract the CSC files from the .tar.md5 just so if a new one becomes available, I can just apply it immediately to that current ROM? I searched a few threads and found different methods like the s2toext4 method and that didn't work so anything would be most appreciated. I don't want to take anything from the developers and this will just be for my personal use.

Couldn't you just flash the CSC part of the ROM with ODIN?
Inside the .MD5 aren't any flashable files anyway other than a PIT file
{
"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"
}

*Detection* said:
Couldn't you just flash the CSC part of the ROM with ODIN?
Inside the .MD5 aren't any flashable files anyway other than a PIT file
Click to expand...
Click to collapse
I tried that as the file in Odin contains a cache.img and a hidden.img but when I boot the a custom ROM and check Phone Info, the CSC didn't change. I am just wondering how some developers extracted those .img files into the files we see into say the CSC changer.

Google and download ImgExtractor.exe and run it on cmd, e.g
Code:
D:\path\to\cache_img> ImgExtractor.exe cache.img
and you'll find the csc zip file under cache_\recovery .
Btw when you manually flash it through recovery, either stock or twrp, don't forget to mount /system first.

Andrw0830 said:
Hello all, I love all the support from the developers who make our ROMs so great and was wondering the following question. Does anyone know how you can extract the CSC files from the .tar.md5 just so if a new one becomes available, I can just apply it immediately to that current ROM? I searched a few threads and found different methods like the s2toext4 method and that didn't work so anything would be most appreciated. I don't want to take anything from the developers and this will just be for my personal use.
Click to expand...
Click to collapse
Not quite sure what you want to do, flash a stock (any) rom with you CSC ( home _ csc ) check this
Or change the CSC of your custom rom, if so check here

kykint said:
Google and download ImgExtractor.exe and run it on cmd, e.g
Code:
D:\path\to\cache_img> ImgExtractor.exe cache.img
and you'll find the csc zip file under cache_\recovery .
Btw when you manually flash it through recovery, either stock or twrp, don't forget to mount /system first.
Click to expand...
Click to collapse
Very useful post, thanks! Works like a charm.

kykint said:
Google and download ImgExtractor.exe and run it on cmd, e.g
Code:
D:\path\to\cache_img> ImgExtractor.exe cache.img
and you'll find the csc zip file under cache_\recovery .
Btw when you manually flash it through recovery, either stock or twrp, don't forget to mount /system first.
Click to expand...
Click to collapse
Yep thanks so much. That is what I wanted to accomplish!

Andrw0830 said:
Yep thanks so much. That is what I wanted to accomplish!
Click to expand...
Click to collapse
What if you modify inside the zip (change default region) and flash it back from recovery? Does it work? KNOX still 0x0?

viewdetails said:
What if you modify inside the zip (change default region) and flash it back from recovery? Does it work? KNOX still 0x0?
Click to expand...
Click to collapse
What I believe is if you flash stock Samsung packages from ODIN, your Knox stays at 0x0 but once you flash modified software like TWRP Recovery, then you lose Warranty. Your phone should detect default region anyways as was the case when I went back to stock so only if you change the package integrity or flash custom recovery is when you will trip KNOX unless someone corrects me. I'll keep this thread open for the useful post about extracting .tar.md5 files in case someone has the same question I had, but I may not reply to other questions as besides flashing ROMs am not too knowledgeable in customizing ROMs.

viewdetails said:
What if you modify inside the zip (change default region) and flash it back from recovery? Does it work? KNOX still 0x0?
Click to expand...
Click to collapse
@ viewdetails, did you try modifying the zip to change the default region and flash it back? Did it work?
I've recently bought an S7 whose region code I want to change to XFA, except it is still stock and unrooted, and XFA is part of a multi CSC only.
Not wanting to void the warranty by rooting just yet, I also had the idea of modifying the CSC tar.md5 file to make it work. Thing is I have not done something like this before and I don't know if doing so will set KNOX to 0x1 anyway.

When I download the repair firmware (4 pieces of ROM called repair software) for any device from the internet, the pit file is also available, but when I download the 4 pieces of pit file with SamFirm program, the pit file does not come out. When I extract the csc.tar.md5 file in the downloaded rom, I have the pit file in it. Is that the pit file I would choose in the Re-Partition section in the PIT file? In other words, do they retrieve the pit files in the repair firmware that are installed in the internete by extracting the file csc.tar.md5 like me?
---------- Post added at 10:05 PM ---------- Previous post was at 09:54 PM ----------
*Detection* said:
Couldn't you just flash the CSC part of the ROM with ODIN?
Inside the .MD5 aren't any flashable files anyway other than a PIT file
When you extract the file Csc.tar.md5, the pit file comes out. Odin is the pit file I would choose for Re-Partition?
Click to expand...
Click to collapse

Serifbilgin20 said:
When I download the repair firmware (4 pieces of ROM called repair software) for any device from the internet, the pit file is also available, but when I download the 4 pieces of pit file with SamFirm program, the pit file does not come out. When I extract the csc.tar.md5 file in the downloaded rom, I have the pit file in it. Is that the pit file I would choose in the Re-Partition section in the PIT file? In other words, do they retrieve the pit files in the repair firmware that are installed in the internete by extracting the file csc.tar.md5 like me?
---------- Post added at 10:05 PM ---------- Previous post was at 09:54 PM ----------
Click to expand...
Click to collapse
*Detection* said:
Couldn't you just flash the CSC part of the ROM with ODIN?
Inside the .MD5 aren't any flashable files anyway other than a PIT file
When you extract the file Csc.tar.md5, the pit file comes out. Odin is the pit file I would choose for Re-Partition?
Click to expand...
Click to collapse
You don't need to extract the PIT file, just check repartition, the CSC will do the rest as it contains the PIT anyway

I need a pit file for any device. The firmware file I downloaded for that device is csc.tar.md5 and the pit file that comes out of it is the file I am looking for ?

kykint said:
Google and download ImgExtractor.exe and run it on cmd, e.g
Code:
D:\path\to\cache_img> ImgExtractor.exe cache.img
and you'll find the csc zip file under cache_\recovery .
Btw when you manually flash it through recovery, either stock or twrp, don't forget to mount /system first.
Click to expand...
Click to collapse
What did you mean by this ? '' Btw when you manually flash it through recovery, either stock or twrp, don't forget to mount /system first.''

EmperorGsi said:
What did you mean by this ? '' Btw when you manually flash it through recovery, either stock or twrp, don't forget to mount /system first.''
Click to expand...
Click to collapse
A flashable zip file needs /system to be mounted in order to make modifications - including installing and removing files - under it, so most zip files automatically do the mount process first before they do anything. However sec_csc.zip lacks that process, so if you want to flash it, you have to manually mount /system under MOUNT options first.

kykint said:
Google and download ImgExtractor.exe and run it on cmd, e.g
Code:
D:\path\to\cache_img> ImgExtractor.exe cache.img
and you'll find the csc zip file under cache_\recovery .
Btw when you manually flash it through recovery, either stock or twrp, don't forget to mount /system first.
Click to expand...
Click to collapse
kykint said:
A flashable zip file needs /system to be mounted in order to make modifications - including installing and removing files - under it, so most zip files automatically do the mount process first before they do anything. However sec_csc.zip lacks that process, so if you want to flash it, you have to manually mount /system under MOUNT options first.
Click to expand...
Click to collapse
Oh got it thank you. i am trying to get sec_csc.zip from S8 Tur firmware but no recovery folder in cache.img. Do you have any ideas ?

EmperorGsi said:
Oh got it thank you. i am trying to get sec_csc.zip from S8 Tur firmware but no recovery folder in cache.img. Do you have any ideas ?
Click to expand...
Click to collapse
If you're trying to unpack an oreo firmware, looks like imgextractor cannot handle the cache.img properly. Instead you can follow the steps below:
1. Extract lz4 image
Code:
lz4 -d cache.img.lz4
2. Convert the extracted image with simg2img (you can compile one from AOSP source or grab from here)
Code:
simg2img cache.img cache.raw.img
3. Open cache.raw.img with a proper program like 7zip explorer, and you'll find recovery/sec_omc.zip.

I used the method from here.
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-extract-pixel-factory-t3563698
I changed cache.img to system.img
The program created a folder called system and copied there all the files
In system/recovery I found the file sec_csc.zip

[GUIDE]: How to flash CRB7 using Odin - S8

UPDATE (27TH FEB 2018): We now have Odin v3.13.1 which is compatible with the new .lz4 compressed files referred to below in the tutorial. All the steps below are only required now if you are using a version of Odin older than 3.13.1. It is recommended that you use this new version to save yourself the hassle.
Odin v3.13.1 - XDA Link
S8 G950F / G950FD (F ROMs work on the FD variants, there are no FD specific ROMs):
Mirror Link 1 (MEGA NZ) (WIPE) - Thanks @ciccio80
Mirror Link 2 (MEGA NZ) (NO WIPE) - Thanks @ciccio80
Mirror Link 3 (Google Drive) - Uploaded by me
Let me start of by saying, Samsung changed some things around with Oreo. I downloaded 'XXU1CRAP' using SamFirm today, tried with both TUR and DBT CSCs, to make sure it wasn't a bad download or anything, but Odin just wouldn't accept the file. It froze on the first step, sboot.bin.lz4.
I had never seen the .lz4 extension before, so I asked a couple of helpful lads in the Samsung Oreo Telegram group who were very helpful throughout this process.
For those of you who want to join:
http://t.me/sammyoreoclub
Samsung is using a new compression method for the Oreo ROMs, so all files within BL, AP, CP and CSC have the .lz4 extension which Odin has trouble reading, and so the flash will never go past the first step.
Note: THIS DOESN'T TRIP KNOX.
Pre-requisites:
-SamFirm to get the CRAP ROM - https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
-Windows PC
-This modded version of 7Zip which can open .lz4 files. Link - Github
-The ability to read the instructions below.
-Prince Comsy's modified Odin - Google Drive Link
-A Galaxy S8/S8+ (G950F / G950FD / G955F / G955FD) - I tested this on my own G955FD and it worked just fine.
-The XXU1CRB7 Oreo ROM for your device
-A decent amount of storage space on your PC
-Preferably some experience with flashing using Odin
DISCLAIMER: I AM NOT RESPONSIBLE FOR BRICKED DEVICES, FOLLOW TUTORIAL AT YOUR OWN RISK.
INTERNAL STORAGE WILL BE COMPLETELY WIPED CLEAN (IF YOU USE CSC_OXM), MAKE SURE YOU BACKUP BEFORE FLASHING.
IF YOUR INTERNAL STORAGE SHOWS AS '16 GB' AFTER FLASHING, DO A FACTORY RESET AND IT'LL RETURN TO NORMAL.
Steps below:
1. Extract the zip file for the 3.7 GB firmware file you just downloaded. Should contain 5 files, AP, BL, CP, CSC_OXM and HOME_CSC_OXM.
In the tutorial below, I will be using CSC_OXM, however that does wipe internal storage.
If you are coming from ZRA5 or just don't want to wipe your data, use HOME_CSC_OXM instead.
2. All the files will have ".tar.md5" extensions. Remove the .md5 part so they can be opened in either WinRAR or 7Zip.
AP will contain a folder called 'meta-data', userdata.img.lz4, system.img.lz4, recovery.img, boot.img.lz4
Extract all these files from AP into a new folder. Right click on each one, select the '7Zip Standard' menu and hit 'Extract Here'.
This will extract all the files within, without .lz4 extensions. So you'll have userdata, system, recovery and boot as plain IMG files.
Note: Repeat this for CP, BL and CSC_OXM.
3. Grab the original file names for the files you extracted earlier, copy paste them into notepad.
They should be in this format, make sure .md5 isn't added at the end of any filenames. Do keep in mind that the filenames for the S8 (G950F) will obviously be slightly different.
Code:
AP_G955FXXU1CRAP_CL12993656_QB16754780_REV00_user_low_ship_meta.tar
BL_G955FXXU1CRAP_CL12993656_QB16754780_REV00_user_low_ship.tar
CP_G955FXXU1CRAP_CP8821296_CL12993656_QB16754780_REV00_user_low_ship.tar
CSC_OXM_G955FOXM1CRAP_CL12993656_QB16754780_REV00_user_low_ship.tar
4. Select all the files you extracted for AP (including the meta-data folder), right click, scroll down to the '7Zip Standard' menu again and this time hit 'Add to Archive'. Copy-paste the filename for whichever file you're creating an archive for, AP, BL, CP or CSC, make sure archive format is set to .tar and leave everything else default and hit 'OK' at the bottom of the window.
Note: This too will be have to be done for CP, CSC and BL as well.
5. Once this is done, you should have 4 .tar files ready to be flashed. Open up Prince Comsy's Odin, add each file to it's respective field in Odin.
6. Connect your device in Download Mode, press Start, and wait for the flash to be completed and for Odin to show 'PASS' at the top of the window.
Your device will reboot automatically.
ALTERNATIVELY, you can watch this very crappy screen recording I made for a better idea on how to do it.
YouTube link: https://youtu.be/eyIh3_p8WBQ
Credits go to:
@FatalONEM8 and @me2151 for helping out.
Tino Reichardt (mcmilk) for the modified 7Zip
Prince Comsy for the modified Odin.
Samsung for making flashing more and more difficult every year.
----------------------------
For Linux/Ubuntu, @kernel.killer has created a script to unpack the .lz4 compressed firmwares without having to do all of the above manually.
See this post - Link

Delete this please, im a moron
also, worked like a charm for me

Odin stuck File Analysis

Worked like a charm. Thanks a lot dude

s
It works perfectly!, finally I have Oreo from a clean installation
{
"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"
}
I uploaded the files with the extraction process done (.lz4) in Google Drive but I can not publish it because I'm new, If someone wants it, you can ask for it through PM.

Works! Thank you so much!

WARNING TO ALL ROOTEED USERS!!!!!!! DONT FLASH CLEAN OREO DIRECTLY OR YOU CANT FLASH TWRP!!!!!! for reflash then twrp you need to stay 7 days on stock without reboot phone!!!!!!!!!!! so wait that someone makes a modded rom with some stuff disabled and that updates bl and modem or you will get a nice red screen when you boot fully stock oreo and then try to boot in twrp!!!!!!!
SAME IS FOR OREO INSTALLED OVER OTA!

Currently CRAP file is one and the same for the Nordic Countries, Spain, France, Germany, Turkey, Poland found on Sammobile.com ?
Tnx.
Trimis de pe al meu SM-G950F folosind Tapatalk

Thanks!! Finally my S8 is running Android Oreo.

Did anyone try with HOME_CSC? I'm currently in ZTO (brazil) CSC and I would like to flash without wiping data and still have access to Samsung Pay. Does it work?
Pavezi80 said:
Works! Thank you so much!
Click to expand...
Click to collapse
brenopapito said:
Thanks!! Finally my S8 is running Android Oreo.
Click to expand...
Click to collapse
Any of you guys try with Home_CSC?
Thanks!

geiti94 said:
WARNING TO ALL ROOTEED USERS!!!!!!! DONT FLASH CLEAN OREO DIRECTLY OR YOU CANT FLASH TWRP!!!!!! for reflash then twrp you need to stay 7 days on stock without reboot phone!!!!!!!!!!! so wait that someone makes a modded rom with some stuff disabled and that updates bl and modem or you will get a nice red screen when you boot fully stock oreo and then try to boot in twrp!!!!!!!
SAME IS FOR OREO INSTALLED OVER OTA!
Click to expand...
Click to collapse
can I use this guide to install CRAB when I have Renovate r44 (Oreo beta6) ?

Lucas_Skyline said:
Did anyone try with HOME_CSC? I'm currently in ZTO (brazil) CSC and I would like to flash without wiping data and still have access to Samsung Pay. Does it work?
Any of you guys try with Home_CSC?
Thanks!
Click to expand...
Click to collapse
I just tried with CSC_OXM file.

tomaasz said:
can I use this guide to install CRAB when I have Renovate r44 (Oreo beta6) ?
Click to expand...
Click to collapse
only when you dont let phone boot after flash in system and then you flash directly twrp and boot directly in twrp for mod build.prop so that vaultkeeper is set to 0 and flash magisk

Lucas_Skyline said:
Did anyone try with HOME_CSC? I'm currently in ZTO (brazil) CSC and I would like to flash without wiping data and still have access to Samsung Pay. Does it work?
Any of you guys try with Home_CSC?
Thanks!
Click to expand...
Click to collapse
You can use the normal CSC to format the S8. When installing, it will be ZTO / ZTO / ZTO because the Rom is multi-CSC (I downloaded the NEE)

It works! thanks!

Pavezi80 said:
You can use the normal CSC to format the S8. When installing, it will be ZTO / ZTO / ZTO because the Rom is multi-CSC (I downloaded the NEE)
Click to expand...
Click to collapse
That's the point, I'm going to travel tomorrow and I don't want to format at this moment
Just wondering if anyone tried with home_CSC from Nougat to Oreo directly to see if they found any issue.
Thanks!

worked here with HOME_CSC... will see if i will need to do it clean or if it will be ok with nowipe. i was on zre5, unoficial betatester

geiti94 said:
WARNING TO ALL ROOTEED USERS!!!!!!! DONT FLASH CLEAN OREO DIRECTLY OR YOU CANT FLASH TWRP!!!!!! for reflash then twrp you need to stay 7 days on stock without reboot phone!!!!!!!!!!! so wait that someone makes a modded rom with some stuff disabled and that updates bl and modem or you will get a nice red screen when you boot fully stock oreo and then try to boot in twrp!!!!!!!
SAME IS FOR OREO INSTALLED OVER OTA!
Click to expand...
Click to collapse
How to recover from this?

I made everything like in instruction but it stops at File analysis.... . What should i do ?

lumenit said:
I made everything like in instruction but it stops at File analysis.... . What should i do ?
Click to expand...
Click to collapse
Install with Prince Comsy's modified Odin