BETA WARNING:
This version of CWM is now in beta testing.
I need user reports of what zips are compatable/not-compatable.
I will remove the beta tag once I have a fair idea of what update zips are/arnt compatable with CWM 6.0.
For any developers: I will be providing instructions/binaries to work with CWM 6.0 soon.
They will likely not be compatable with streakmod.
Once CWM is out of beta, I would strongly recommend everyone migrating off of streakmod.
Click to expand...
Click to collapse
How to use fastboot:
Setting up fastboot for Windows -XDA wiki
Installing a recovery - XDA wiki
Click to expand...
Click to collapse
Requirements:
Ability to enter fastboot mode
Basic understanding of the command line
Click to expand...
Click to collapse
Install instructions:
Download Clockwork mod recovery.img
streak5
streak5ex (link TBA)
streak5sd8 (link TBA)
Turn device off
Hold down Power and Camera Down
Flash the recovery with "fastboot flash recovery <path to recovery.img>"
Click to expand...
Click to collapse
What works:
Clearing caches
Factory resetting
Nandroid
Update zip flashing
USB mounting
Click to expand...
Click to collapse
Notice:
What to do if your nandroid freezes at /cache, /data, /datadata:
Flash update-CWMfixer-1.zip as an update zip and try again.
OR: Factory reset and manually restore data (Not recommended)
This is portrait only, unless someone is willing to give me code to rotate it 270 degrees it will remain as so
Removing the battery door while recovery is active will cause it to exit (this is intentional, it is also part of the stock 407 kernal)
Streakmod nandroids are not compatable with CWM. You may be able to get it to work by copying the contents of "rom_backup" to "clockworkmod", but this is not supported
If you get errors about not being able to mount your SD card, power the device off and remove the battery for a moment, then try again
Notes about sd-ext:
If you get the error message while nandroid: "sd-ext.img not found. Skipping restore of /sd-ext." This is normal, as sd-ext is an optional partition.
If you get the error message while formatting: "E: format_volume: make_ext4fs failed on /dev/block/mmcblk0p2", same as above
Click to expand...
Click to collapse
Controls:
Vol Up: Scroll up
Vol Down: Scroll down
Camera: Select item
Back: Go back
Click to expand...
Click to collapse
Changelog:
Sep 09 2012: Updated to 6.0.1.2
Aug 21 2012: Removed beta tag, added workaround for nandroid issues
Aug 07 2012: Updated to 6.0.1.1
Jul 21 2012: Updated to 6.0.1.0 - entered beta phase
Jul 20 2012: Updated to 6.0.0.9
Jul 18 2012: Initial release
Click to expand...
Click to collapse
2char
glad to hear this
i am trying
So is this the touch version?
it displays nothing when moving up (or down)
and show back when moving for the second time
not just display ,
if you want to select the 2nd (4th ,6th ... )item
you must moving up and down till it shows "BACK menu button enabled" or "BACK menu button disabled"
and is there anying new in CWM6007?
i had posted CWM5027 chinese version
most functions are working well
what about change it back to english version?
and i had seen a special version of CWM4010
it has a new function “advanced backup”
i think it's very useful
http://bbs.anzhi.com/thread-3182311-1-1.html
the Attach File is for ZTE X876
it is NOT for streak
Crinos512 said:
So is this the touch version?
Click to expand...
Click to collapse
no
If by advanced backup you mean selective backing up of partitions.
I had considered that many months ago, but I didnt add it because it wouldnt matter. (I never had a fully working CWM previously)
CWM never liked booting on the S5 for whatever reasons.
Adding in selective backups shouldnt be terribly difficult, but I'm not really interestested in modding CWM, (excluding the S5) all my devices have working CWM 6.0.0.x and the source code is available for anyone interested.
I'm trying to modify CWM as little as possible to make it easier for future changes. CWM 6.0 was only released a couple days ago and we're already at 6.0.0.7+
The biggest change in 6.0 is "dedupe" where nandroids are base + delta so if you constantly nandroid, the deltas become very small.
Besides the screen I would assume everything works and it would be ready to replace streakmod, but the screen issue is very annoying.
Also to note: I will attempt to port TWRP later, as it DOES support RGB_565 displays still, and since we have an ICS kernel, it might just work.
somewhere from CWM 5.5 -> 6.0 RGB_565 displays took a back seat to RGBX_8888/BGRA_8888 displays and I guess wasnt really fixed.
Edit: The other major feature is that I dont have to make multiple versions of every update zip.
Currently it's S5/V and S7 and nothing for the S10.
Streakmod doesnt have much in /sbin, CWM has busybox, and a bunch of filesystem utils.
so instead of needing:
Code:
mount("MTD", "system", "/system"); (for the S5/V)
mount("ext4", "/dev/block/mmcblk3p3", "/system"); (for the S7)
mount("ext4", "/dev/block/mmcblk0p3", "/system"); (for the S10)
Or make a new one for each specific device I'm gonna support
I can do
Code:
run_program("/sbin/busybox", "mount", "/system");
and that will work with any device with any device with a recent enough recovery
Edit2:
If and when I get CWM 6.0 working on the S5, I will be making all future update zips "generic" as in they should be able to install on any device (assuming they're relevent for that device)
Examples of such are: Superuser.zip, Gapps
Edit3:
After doing a test zip, I can in fact use the same mount script on all 4 devices instead of needing 3 seperate ones.
Unfortunately like previously mentioned they simply dont work on streakmod as it doesnt have busybox.
Edit4:
I will be internally using CM6.0 now, regardless of if I can fix the framebuffer issue.
Any future S5-specific update zips will be deemed "legacy update" zips
I will be updating to CWM 6.0.0.9 as soon as it's available.
Also: I have no idea of older update zips (from whoever) will work on CWM 6.0, there's many changes to the scripting from 1.8 -> 6.0 (streakmod is based on a very old CWM) and even edify based update.zips may not work if they're using an old enough binary.
Updated to 6.0.0.9 now,
there's no changes specific to the S5 though, so everything prevous still applies
TheManii said:
Updated to 6.0.0.9 now,
there's no changes specific to the S5 though, so everything prevous still applies
Click to expand...
Click to collapse
maybe this will help people to test new recovery without PC
just flash it in recovery as ROMs
2 files?
I assume recovery6009a.zip is the CWM recovery...what is the other one?
The other one is likely streakmod from the version number
I think I got it
Edit: I am in the middle of testing it, but I think I will be able to release a full version soon
CWM 6.0.1.0 is now released an in the beta phase!
What I need tester reports of:
flashing recent roms
flashing random (things you would normally expect to flash in streakmod) zips
fac resetting
I believe nandroids are already reliable, but any reports to re-confirm/deny would be welcomed.
USB mounting works fine
I will be migrating all my utilities to be CWM compatable and marking streakmod-compatable versions as "legacy"
ALL HAIL TheManii!!!
Dude, you are god! THANK YOU!
what are the odds of a flashable Zip version? Can't wait to try this out too!
Crinos512 said:
2 files?
I assume recovery6009a.zip is the CWM recovery...what is the other one?
Click to expand...
Click to collapse
these two could be used to flash recovery to clockwork mod recovery 6.0.0.9 or to streakmod 0.3.2.8these are zip flash ,without PC
Controls:
•Vol Up: Scroll up
•Vol Down: Scroll down
•Power: Select item
•Back: Go back
Click to expand...
Click to collapse
1. the key to select item is camere ,not power
2. i think using back or home to select item will be better
then we can only use "back \ menu \home"
3. could you please add utf-8 support then i can translate it to chinese version
manics said:
1. the key to select item is camere ,not power
2. i think using back or home to select item will be better
then we can only use "back \ menu \home"
3. could you please add utf-8 support then i can translate it to chinese version
Click to expand...
Click to collapse
Is this the flashable zip via streakmod recovery?
manics said:
1. the key to select item is camere ,not power
2. i think using back or home to select item will be better
then we can only use "back \ menu \home"
3. could you please add utf-8 support then i can translate it to chinese version
Click to expand...
Click to collapse
i dont like using the touch key for CWM coz sometime it thinks u pressed it twise, like a double tap.. it gets very annoying
sinan33 said:
Is this the flashable zip via streakmod recovery?
Click to expand...
Click to collapse
yes,
not only streakmod but also clockwork mod
Related
Here is a CWM-Based Recovery built from source for use with either Honeycomb or Gingerbread hboot.
Thanks to Team Revolutionary for their CWM4 Recovery and DooMLoRD for his Custom CWM-Based Touch Recovery 5.0.2.7 which I used to set up the board config and makefiles.
To install place the recovery.img in your fastboot directory and type the following commands into a terminal;
Code:
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
Flyer CWM-Based Recovery 6.0.1.1 GB.zip - 4.92 MB
MD5: 5f8bc34e44eaeccaf320f89cecca5e52 (for .img not .zip)
Flyer CWM-Based Recovery 6.0.1.1 HC.zip - 5.02 MB
MD5: 30b5bf5952ceba8fbab02f54b39da4df (for .img not .zip)
Click to expand...
Click to collapse
Koushik Dutta said:
New ClockworkMod Backup Format
TL;DR:
ClockworkMod Recovery now deduplicates files between builds. This results in way smaller backups.
Don't delete /sdcard/clockworkmod/blobs
Overview
I've gotten a few questions about how this works, so I figured I'd make a post on it.
Basically, here's what happens:
The files being backed up are hashed (sha256, not that it matters). Then it checks for a file with the name of the hash in
/sdcard/clockworkmod/blobs
So, if the hash of the file was c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed, it looks for /sdcard/clockworkmod/blobs/c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed
If the hash file is found, it continues on to the next file. Otherwise, it copies the file to the blobs directory with the file name being the hash.
ROMs and user data, for the most part, do not change too much between builds and backups. So, your APKs, system files, etc, are generally only stored once. This saves a ton of space. Especially between incremental backups.
Some of you may be thinking "well, how do I delete a backup?".
First, never delete the blobs directory. This would actually delete all your backups by rendering them unusable.
Simply delete the usual backup directory, and the next time you run a backup, all the unused hash files will be automatically delete (a process known as garbage collection). The recovery will show "Freeing space..." while this is happening.
Click to expand...
Click to collapse
Thanks, I couldn't get if that is touch enabled or not.
teorouge said:
Thanks, I couldn't get if that is touch enabled or not.
Click to expand...
Click to collapse
I dont have access to the touch based repos as they're closed at the moment so I'm afraid for now this recovery is old school. The "change log" Koushik posted on his Google+ was enticing enough to try it out though!
Koushik Dutta said:
Backups are much faster. 4-5x faster. (Bug fix due to excessive status updates of the UI and new backup technique)
Incremental backups are smaller. Way way smaller. Only 15-20MB each for each additional backup of a ROM. This is done using a new tool I wrote to dedupe the files between incremental backups to eliminate duplicates.
Click to expand...
Click to collapse
a quick note for those who wonder.
Aroma installer does not work with touch, without the touch enabled and ntrigd running in recovery. but thats just so you know.
so thats key controlled too.
Can someone make a flashable zip?
Dexter_nlb said:
a quick note for those who wonder.
Aroma installer does not work with touch, without the touch enabled and ntrigd running in recovery. but thats just so you know.
so thats key controlled too.
Click to expand...
Click to collapse
Just to clarify, Aroma will still work manually with the volume keys and power button I assume? Thanks for the heads up.
lekhwani said:
Can someone make a flashable zip?
Click to expand...
Click to collapse
I'll check that out now.
What do i gain with flashing this ower ver. 5.?
Thx!
jprednik said:
What do i gain with flashing this ower ver. 5.?
Thx!
Click to expand...
Click to collapse
5.0.2.8 is the most up to date recovery version on the gingerbread branch at the moment. These 6.0.0.x versions are from the ics and jellybean branches. To my knowledge I don't think Koushik posts "changelogs" on the various recovery updates but he's made a few posts talking about version 6 of ClockworkMod Recovery here and here.
I have Gingerbread.
So Work well with GB ? --- >HTC Flyer - CWM-Based Recovery 6.0.0.7 - GB.zip - 4.92 MB
What are the improvements.
Thanks
No offense but what is the point of this ?!.
lekhwani said:
Can someone make a flashable zip?
Click to expand...
Click to collapse
There is no touch support when flashed and Power button actually switched the screen OFF, so it is pretty useless. The DormLord touch -based CWN is just perfect as it is. There is no serious ICS ROM to flash anyway, so I do not understand why cripple this CWN when there is no real value here.
Max128 said:
I have Gingerbread.
So Work well with GB ? --- >HTC Flyer - CWM-Based Recovery 6.0.0.7 - GB.zip - 4.92 MB
What are the improvements.
Thanks
Click to expand...
Click to collapse
The GB version will work with the Gingerbread hboot. Check out the previous posts to read up on the changes.
fteo_viking said:
There is no touch support when flashed and Power button actually switched the screen OFF, so it is pretty useless. The DormLord touch -based CWN is just perfect as it is. There is no serious ICS ROM to flash anyway, so I do not understand why cripple this CWN when there is no real value here.
Click to expand...
Click to collapse
Flash the recovery.img manually through fastboot if you're having problems. If you look at the ClockworkMod site a lot of devices don't have ClockworkMod Recovery 6 or a Touch supported version at all. The Flyer has never had an officially supported ClockworkMod Recovery anyway. I wanted to check out version 6 myself and put these up in case anyone else wanted to as well. It's not for everyone as there won't be a ClockworkMod Touch Recovery without an ICS kernel or until DooMLoRD and Team UtterChaos port their Touch UI to the ics branch. If you don't want to use it don't.
I have a WiFi + 3g Flyer and with recovery 6.0.1.0 the power button doesn't work, so I'm not able to use it...
nikoan89 said:
I have a WiFi + 3g Flyer and with recovery 6.0.1.0 the power button doesn't work, so I'm not able to use it...
Click to expand...
Click to collapse
If the text options disappear when you press the power button press it again so they return then press volume-up and volume-down at the same time to toggle between "Back menu button disabled." and "Back menu button enabled."
revert back to 4.0.1.4
I tried this and had problems with selecting an option with the powere button so I want to revert to 4.0.1.4. I flash 4.0.1.4 to recovery via fastboot but then it hangs on the HCT logo when I try to get to Recovery.
Any ideas?
UPDATE: I ended up changing to Doomlords 5.0.2.7 and it works great.
nikoan89 said:
I don't have this kind of issue, mine is that power button in recovery mode simply doesn't work, all the text options still on screen, I'm only able to navigate with the volume buttons but I'm not able to select them.
EDIT: I've fix it holding the power button and pressing repeatedly the vol down button, now it seems to work
Click to expand...
Click to collapse
Work for me with this method. Thinks.
mkintop said:
I tried this and had problems with selecting an option with the powere button so I want to revert to 4.0.1.4. I flash 4.0.1.4 to recovery via fastboot but then it hangs on the HCT logo when I try to get to Recovery.
Any ideas?
UPDATE: I ended up changing to Doomlords 5.0.2.7 and it works great.
Click to expand...
Click to collapse
I had the same problem, took me several hours to figure out how to re-flash to 5.8.3.1.
This one is not good.
nikoan89 said:
I don't have this kind of issue, mine is that power button in recovery mode simply doesn't work, all the text options still on screen, I'm only able to navigate with the volume buttons but I'm not able to select them.
Click to expand...
Click to collapse
mkintop said:
I tried this and had problems with selecting an option with the powere button so I want to revert to 4.0.1.4. I flash 4.0.1.4 to recovery via fastboot but then it hangs on the HCT logo when I try to get to Recovery. Any ideas?
Click to expand...
Click to collapse
oushouseki said:
I had the same problem, took me several hours to figure out how to re-flash to 5.8.3.1.
This one is not good.
Click to expand...
Click to collapse
I enabled the "BOARD_HAS_NO_SELECT_BUTTON" flag in BoardConfig.mk and now the power button works as soon as recovery boots. No need to toggle between "Back menu button disabled" and "Back menu button enabled" anymore.
If the recovery doesn't boot properly and hangs at the splash screen use "fastboot erase cache". Similarly, if you want to flash any other recovery use the commands in the OP.
Code:
adb reboot bootloader
fastboot flash recovery nameofrecovery.img
fastboot erase cache
fastboot reboot
Can someone make a flashable zip?
THX
I would like that too...
i am a hardcore noob so bear with me.
What is a terminal and how and where to i type that?
can somebody please explain!
Notice:
I do not own a SPro, this is a somewhat blind port.
I can only confirm that it boots and nandroids seem to work, but I cannot test it thoroughly without a device.
I will need feedback for all future builds, otherwise I have no idea what works/breaks in future releases!
It does not back up the /flex partition, so nandroids are not perfect, I do not think I will fix it.
(there is no easy way to tell CWM to back up additional partition without changing code, I dont want to change code)
Click to expand...
Click to collapse
Requirements:
Ability to enter fastboot mode
Basic understanding of the command line
ADB and fastboot set up
Click to expand...
Click to collapse
Install instructions:
Download Clockwork mod recovery.img
Turn device off
Put device in fastboot mode
Flash the recovery with "fastboot flash recovery <path to recovery.img>"
Click to expand...
Click to collapse
What works:
Clearing caches
Factory resetting
Nandroid
USB mounting
Update zip flashing
Click to expand...
Click to collapse
Notice:
What to do if your nandroid freezes at /cache, /data, /datadata:
Flash update-CWMfixer-1.zip as an update zip and try again.
OR: Factory reset and manually restore data (Not recommended)
If you get errors about not being able to mount your SD card, power the device off and remove the battery for a moment, then try again
Notes about sd-ext:
If you get the error message while nandroid: "sd-ext.img not found. Skipping restore of /sd-ext." This is normal, as sd-ext is an optional partition.
If you get the error message while formatting: "E: format_volume: make_ext4fs failed on /dev/block/mmcblk0p2", same as above
/flex is not backed up in nandroids, you must keep this in mind when switching roms
Click to expand...
Click to collapse
Controls:
Vol Up: Scroll up
Vol Down: Scroll down
Power: Select item
Back: Go back
Click to expand...
Click to collapse
Changelog:
Sep 09 2012: Updated to 6.0.1.2
Aug 21 2012: Removed beta tag, added workaround for nandroid issues
Aug 07 2012: Updated to 6.0.1.1 - first public beta
Aug 06 2012: Initial private beta
Click to expand...
Click to collapse
Credits:
Hatoya for testing and dumping 068
"101DL" for testing and dumping 080
Click to expand...
Click to collapse
2char
Removed beta tag, added workaround for nandroid issues
Updated to 6.0.1.2
Team Win Recovery Project 3.0.0.x ONLY For MS01LTE SM-G7105
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
TWRP 3.0.0-0 is out now for all currently supported devices.
What’s new in 3.0.0-0:
Completely new theme - Much more modern and much nicer looking (by z31s1g)
True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
SuperSU prompt will no longer display if a Marshmallow ROM is installed
Update exfat, exfat fuse, dosfstools (by mdmower)
Update AOSP base to 6.0
A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
DOWNLOAD:
ON post #2
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Downloads
TWRP 3.0.0
Note - Im not having this device so im not sure that this will work but you can test and report
ODIN (Tar file)- coming soon
Recovery flashable zip - coming soon
Recovery image - Here
Nice job perfectly working in 7102.
Bro how can I flash this recovery???????
Thanks a lot for helping ms01lte???
Sanjay8787 said:
Nice job perfectly working in 7102.
Click to expand...
Click to collapse
This is only for Lte
Yuen.Jason22 said:
Bro how can I flash this recovery?������������
Thanks a lot for helping ms01lte������
Click to expand...
Click to collapse
No u need to use flashify to flash this
What will happen if there is a failure in flashing?? I can't brick my phone in this period before I get a new one
Yuen.Jason22 said:
What will happen if there is a failure in flashing?�� I can't brick my phone in this period before I get a new one
Click to expand...
Click to collapse
If this wont work then u can flash another recovery from odin it will repair
how to install
adityaupreti said:
Downloads
TWRP 3.0.0
Note - Im not having this device so im not sure that this will work but you can test and report
ODIN (Tar file)- coming soon
Recovery flashable zip - coming soon
Recovery image - Here
Click to expand...
Click to collapse
İ'm on motion rom v17.my 7105 allways open download mod when i flash with flashify.
SM-G800H cihazımdan Tapatalk kullanılarak gönderildi
hey friends
diid it work for samsung galaxy grand 2 duos g7102?
plz reply fast:crying:
Hi guys.
Been trying for 3 days now to install this recovery on my Galaxy Grand 2 SM-7105, but to no avail. Here's what I did:
1- Using Odin I root the device using "CF-Auto-Root-ms01lte-ms01ltexx-smg7105" . I got PASS in Odin, (is this an indicator that the root is successful? Because if I entered Android after that, it seems unrooted).
2- Then after rooting (I understand that I can't install the recovery without root first), and without rebooting OR after rebooting the device, I run Odin again, and in download mode I flash the TWRP 3.0.0 recovery.
3- Disconnect USB cable, remove battery, then boot into recovery, but I keep getting the message:
Could not do normal boot .
Odin mode
Current Binary: custom
System status: custom
No matter how many times I tried and how many method and Odin versions I used, the same result.
What could be wrong? How can I be sure that it is a problem in the installation of the root, and not in the installation of the recovery, or vice versa?
Appreciate your feedback !
mouadk said:
Hi guys.
Been trying for 3 days now to install this recovery on my Galaxy Grand 2 SM-7105, but to no avail. Here's what I did:
1- Using Odin I flashed root rom "CF-Auto-Root-ms01lte-ms01ltexx-smg7105" . I got PASS in Odin, (is this an indicator that the root is successful? Because if I entered Android after that, it seems unrooted).
2- Without rebooting OR after rebooting the device, I run Odin again, and in download mode I flash the TWRP recover.
3- Disconnect USB cable, remove battery, then boot into recovery, but I keep getting the message:
Could not do normal boot .
Odin mode
Current Binary: custom
System status: custom
No matter how many times I tried and how many method and Odin versions I used, the same result.
What could be wrong? How can I be sure that it is a problem in the installation of the root, and not in the installation of the recovery, or vice versa?
Appreciate your feedback !
Click to expand...
Click to collapse
This twrp dosen't work for g7105 use my twrp 3.0.0 shoud work fine
SoUnd001 said:
This twrp dosen't work for g7105 use my twrp 3.0.0 shoud work fine
Click to expand...
Click to collapse
Thanks man. But that's actually the TWRP recovery I've been trying to flash, and that's what i mentioned.
If you were referring to the "CF-Auto-Root-ms01lte-ms01ltexx-smg7105" , my understanding is that that's not the recovery, but the root rom, which I must flash first before the TWRP 3.00 recovery.
No ?
mouadk said:
Thanks man. But that's actually the TWRP recovery I've been trying to flash, and that's what i mentioned.
If you were referring to the "CF-Auto-Root-ms01lte-ms01ltexx-smg7105" , my understanding is that that's not the recovery, but the root rom, which I must flash first before the TWRP 3.00 recovery.
No ?
Click to expand...
Click to collapse
You are on kitkat firmware right?
---------- Post added at 04:59 PM ---------- Previous post was at 04:51 PM ----------
And if you want easy root flash my twrp go to recovery mode and flash update supersu
SoUnd001 said:
You are on kitkat firmware right?
---------- Post added at 04:59 PM ---------- Previous post was at 04:51 PM ----------
And if you want easy root flash my twrp go to recovery mode and flash update supersu
Click to expand...
Click to collapse
No not Kitkat, Jelly Bean (4.3).
And sorry not sure I understood your last sentence. I can only access the stock recovery. So what do you mean by "flash update supersu", and how does that help ?
mouadk said:
No not Kitkat, Jelly Bean (4.3).
And sorry not sure I understood your last sentence. I can only access the stock recovery. So what do you mean by "flash update supersu", and how does that help ?
Click to expand...
Click to collapse
You need to flash kitkat firmware with odin
SoUnd001 said:
You need to flash kitkat firmware with odin
Click to expand...
Click to collapse
Well, the author of this post (who posted the WTRP) didn't say one must have Kitkat before flashing this recovery. So are you sure of it?
Also, can I flash Kitkat via Odin if the phone is not rooted?
If yes, where can I get the kitkat for this phone ?
mouadk said:
Well, the author of this post (who posted the WTRP) didn't say one must have Kitkat before flashing this recovery. So are you sure of it?
Also, can I flash Kitkat via Odin if the phone is not rooted?
If yes, where can I get the kitkat for this phone ?
Click to expand...
Click to collapse
Any recovery or rom needs kitkat firmware you can get kitkat by just going to setting and check for updates
SoUnd001 said:
Any recovery or rom needs kitkat firmware you can get kitkat by just going to setting and check for updates
Click to expand...
Click to collapse
Thank you. Unfortunately there are no updates, says "your device has the latest updated" !
It seems my cell provider decided they don't want to upgrade it.
Samsung Galaxy S8 (Snapdragon)
PLEASE READ READ READENTIRE OP
"ALL MAJOR WORK DONE BY HASHCODE SO GO GIVE HIM SOM THANKS.DO NOT POST ANY BUG OR ISSUE COUSED BY THIS RECOVERY IN ORIGINAL THREAD BY HASHCODE, POST HERE AND I WILL HELP YOU."
CURRENT PROJECT STATUS:
BETA v4.09-B01 [Nougat:7.0]
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 3.3.0 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots for flashing ROMs. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
[Safestrap pre V4.07] Requirement: busybox. Grab "Busybox" from the Play Store and run the installer.
APK install:
Once installed, open up the Safestrap application, Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
Flashable zip:
Flash using Safestrap recovery or FlashFire.
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting (or the hard button underneath each option).
HOW DO I UPGRADE SAFESTRAP?
APK:
Push the APK up to your sdcard.
Boot back into the "stock" rom-slot.
Open your old Safestrap app and use the "Uninstall Recovery" button
Browse to where you pushed the APK
Click on it and install like normal
Once installed, open the APK, Grant SU access, Use the "Install Recovery" button.
Flashable zip:
Flash using Safestrap recovery or FlashFire.
KNOWN ISSUES:
- Sometimes the installation doesn't work correctly. If you don't see the splashscreen after a rebooting. Install Safestrap again.
DOWNLOADS:
CONFIRM THAT YOU ARE USING A SAMSUNG GALAXY S8 (Snapdragon) [Nougat:7.0]
LATEST ZIP: Safestrap-4.09-B01-DREAMQLTE-SS-FF-flashable.zip
LATEST APK: Safestrap-4.09-B01-DREAMQLTE.apk
androidfilehost
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
Special Thanks To
@Hashcode, DeesTroy & TeamWin for all their hard work making TWRP such a fantastic recovery.
@jrkruse for pointing me that S8 has permissive root. @partcyborg for getting root on S8.
CHANGELOG:
4.09-B01 [2019-04-19]
- TWRP updated to 3.3.0.
- Fix reboot function
- Add reboot to safestrap button in reboot menu
- Add Edl button in reboot menu
- Move Boot Options to advanced menu items.
- Safestrap app: Update topjohnwu's libsu to 2.4.0.
- Safestrap app: Update install recovery function.
4.08-B01 [2019-03-01]
- TWRP updated to 3.2.3.
- Fix datamedia mount.
- Add hijack-backup during image flashing.
- Major code clean up.
4.07-B01 [2018-07-16]
- Fix CHARGER_BOOT detection.
- TWRP updated to 3.2.2.
- Update safestrap portrait theme.
- Update safestrap app to use topjohnwu's libsu & internal busybox (busybox app not needed anymore).
4.06-B02 [2018-04-10]
- Fix taskset cpus to 8 cores (thanks to Hashcode).
- Add exfat support for recovery (ext-sdcard fix).
- Fix MTP (thanks to me2151).
4.06-B01 [2018-04-03]
- Initial release.
BUGS:
- ROM-slots not working for now.
Mine
dang never been first to reply to a thread lol.....anyways been looking at this and waiting for it to release, downloading and going to give it a whirl nice job to all involved:good::highfive::good:
Has this been tested on s8+ g55u.?
So far install goes as planned boots up tried flashing a zip that I have that works with flash fire it goes thru the motions of flashing but upon reboot my mods have not been applied, i did go into the mount option first and ticked system. So so far no flashing zips but that could be user error ill be so stoked once i get it figured out going to way cooler than using flashfire(got love that app it has been a blessing to us s8 owners) also will this run aroma scripts as well i love making me some aroma installers lol:good::highfive::good:
MysticFTW said:
Has this been tested on s8+ g55u.?
Click to expand...
Click to collapse
Its almost the same, but here you go Galaxy S8 SM-G955U (dream2qlte)
sawixso81 said:
So far install goes as planned boots up tried flashing a zip that I have that works with flash fire it goes thru the motions of flashing but upon reboot my mods have not been applied, i did go into the mount option first and ticked system. So so far no flashing zips but that could be user error ill be so stoked once i get it figured out going to way cooler than using flashfire(got love that app it has been a blessing to us s8 owners) also will this run aroma scripts as well i love making me some aroma installers lol:good::highfive::good:
Click to expand...
Click to collapse
Recovey uses different mount point, recovery log can help.
Thank you
If the main OS becomes unbootable due to a bootloop or something of that sort, is it possible to get back to SS? What does it take to convert Odin-flashable firmware into TWRP/SS flashable firmware?
afaneh92 said:
Its almost the same, but here you go Galaxy S8 SM-G955U (dream2qlte)
Recovey uses different mount point, recovery log can help.
Click to expand...
Click to collapse
Thanks a bunch for this bad a#$ tool/utility this makes my life as an avid modder so much easier when flashing and modding system files awesome work and yes I did have to change the mount points to get my zip to flash and aroma is working as well!!!!!!!!! :good::highfive::good:
Dang Ive been busy all stinkin day and just come across it.
Nice......
Whoa, this is awesome! So this isn't exactly unlocking the bootloader, right? It's just one of the first custom recoveries working on Snapdragon? This is super cool, thank you!
SirSoviet said:
If the main OS becomes unbootable due to a bootloop or something of that sort, is it possible to get back to SS? What does it take to convert Odin-flashable firmware into TWRP/SS flashable firmware?
Click to expand...
Click to collapse
Just wait, I will start working on new ROM soon.
Also stock odin flashable including SS and ROOT (flashing ENG boot to enable them).
Damn, I never thought I'd see the day So I the battery is still locked to 80% right? Anyway good job and best of luck in future developments man!
Confirmed working on G950W. Great job! One nitpick I have about is that scrolling is incredibly laggy/stuttery, otherwise the whole package works fine other than the rom slots.
SirSoviet said:
Confirmed working on G950W. Great job! One nitpick I have about is that scrolling is incredibly laggy/stuttery, otherwise the whole package works fine other than the rom slots.
Click to expand...
Click to collapse
Will try to fix lag issue soon.
Does this work for all snapdragon S8s, or only the unlocked variants? I have the Tmobile version and would love this.
Also, any ROMs that come from this, will they still have the 80% battery life issues if the custom ROM doesn't use root (I'm not sure if all custom ROMs require root or not). Do the ROMs still have to be based on stock samsung, or could we see AOSP style ROMs with this?
DXander1337 said:
Does this work for all snapdragon S8s, or only the unlocked variants? I have the Tmobile version and would love this.
Also, any ROMs that come from this, will they still have the 80% battery life issues if the custom ROM doesn't use root (I'm not sure if all custom ROMs require root or not). Do the ROMs still have to be based on stock samsung, or could we see AOSP style ROMs with this?
Click to expand...
Click to collapse
Support all snapdragon variants of S8. Unless they has different partition layout.
How does this affect things like knox flag and safetynet? Do we have access to system and kernel?
kekistaneerefugee said:
How does this affect things like knox flag and safetynet? Do we have access to system and kernel?
Click to expand...
Click to collapse
Bootloaders still locked. So Knox isn't tripped but as you have to be rooted to do this is say safety nets broke
Samsung Galaxy S8 Active (Snapdragon)
PLEASE READ READ READENTIRE OP
"ALL MAJOR WORK DONE BY HASHCODE SO GO GIVE HIM SOM THANKS.DO NOT POST ANY BUG OR ISSUE COUSED BY THIS RECOVERY IN ORIGINAL THREAD BY HASHCODE, POST HERE AND I WILL HELP YOU."
CURRENT PROJECT STATUS:
BETA v4.11-B01 [Nougat:7.0]
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 3.3.0 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots for flashing ROMs. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
APK install:
Once installed, open up the Safestrap application, Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
Flashable zip:
Flash using Safestrap recovery or FlashFire.
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting (or the hard button underneath each option).
HOW DO I UPGRADE SAFESTRAP?
APK:
Push the APK up to your sdcard.
Boot back into the "stock" rom-slot.
Open your old Safestrap app and use the "Uninstall Recovery" button
Browse to where you pushed the APK
Click on it and install like normal
Once installed, open the APK, Grant SU access, Use the "Install Recovery" button.
Flashable zip:
Flash using Safestrap recovery or FlashFire.
KNOWN ISSUES:
- Sometimes the installation doesn't work correctly. If you don't see the splashscreen after a rebooting. Install Safestrap again.
DOWNLOADS:
CONFIRM THAT YOU ARE USING A SAMSUNG GALAXY S8 Active G892U (Snapdragon) [Nougat:7.0]
LATEST ZIP: Safestrap-4.11-B01-CRUISERLTE-SS-FF-flashable.zip
LATEST APK: Safestrap-4.09-B01-CRUISERLTE.apk
androidfilehost
CONFIRM THAT YOU ARE USING A SAMSUNG GALAXY S8 Active G892A (Snapdragon) [Nougat:7.0]
LATEST ZIP: Safestrap-4.11-B01-CRUISERLTEATT-SS-FF-flashable.zip
LATEST APK: None
androidfilehost
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
Special Thanks To
@Hashcode, DeesTroy & TeamWin for all their hard work making TWRP such a fantastic recovery.
@jrkruse for pointing me that S8 has permissive root. @partcyborg for getting root on S8.
CHANGELOG:
4.11-B01 [2019-04-19]
- TWRP updated to 3.3.1.
- Add proper G892A device support.
- Clean up hijack.
- Fix datamedia mount.
- Enhanced Safestrap logo.
- More stuff I forgot, lol
4.09-B01 [2019-04-19]
- TWRP updated to 3.3.0.
- Fix reboot function
- Add reboot to safestrap button in reboot menu
- Add Edl button in reboot menu
- Move Boot Options to advanced menu items.
- Safestrap app: Update topjohnwu's libsu to 2.4.0.
- Safestrap app: Update install recovery function.
4.08-B01 [2019-03-01]
- TWRP updated to 3.2.3.
- Fix datamedia mount.
- Add hijack-backup during image flashing.
- Major code clean up
- Initial release.
BUGS:
- ROM-slots not working for now.
Great job. I will try to flash stock oreo and this safestrap via this safestrap. So i review to keep it on stock oreo.
After test, it works fine. But I can't keep it with stock oreo.
Can you enable adbd insecure on twrp? Thanks.
quanqw said:
Can you enable adbd insecure on twrp? Thanks.
Click to expand...
Click to collapse
Not sure.
does it work on s8 sc-02j docomo it just say safestrap is disabled recovery and continue but when i choose recovery its still TWRP
epiphany74721 said:
does it work on s8 sc-02j docomo it just say safestrap is disabled recovery and continue but when i choose recovery its still TWRP
Click to expand...
Click to collapse
That's normal click recovery to go-to safestrap. Bte this is supposed to be for US variants kinda lucky you didn't brick as the model it's for is listed in the title
epiphany74721 said:
does it work on s8 sc-02j docomo it just say safestrap is disabled recovery and continue but when i choose recovery its still TWRP
Click to expand...
Click to collapse
You device is unlocked right? why you need safestrap?
afaneh92 said:
You device is unlocked right? why you need safestrap?
Click to expand...
Click to collapse
i got data mount issue on twrp cant install rom i want to replace it with safestrap recovery
epiphany74721 said:
i got data mount issue on twrp cant install rom i want to replace it with safestrap recovery
Click to expand...
Click to collapse
Type this in terminal or in twrp terminal then copy output or take screen shot.
"ls -al /dev/block/platform/soc/1da4000.ufshc/by-name"
I will make twrp for you.
afaneh92 said:
Type this in terminal or in twrp terminal then copy output or take screen shot.
"ls -al /dev/block/platform/soc/1da4000.ufshc/by-name"
I will make twrp for you.
Click to expand...
Click to collapse
here sorry for the late reply a little busy ang my imei is corrupted also cant install s8 docomo 8.0 all corrupted in samfirm wont install oreo also
epiphany74721 said:
here sorry for the late reply a little busy ang my imei is corrupted also cant install s8 docomo 8.0 all corrupted in samfirm wont install oreo also
Click to expand...
Click to collapse
First safestrap not working on oreo/pie without permissive kernel. Try this
https://www.google.com/amp/s/forum....rnel-permissive-patcher-android-t3506338/amp/
I will make you twrp soon. Will pm you when its ready.
Edit: no need to build new twrp for your device, data encrypted on oreo/pie.
After booting in TWRP download and flash no-verity-opt-encrypt-6.0 zip to disable data partition encryption
afaneh92 said:
First safestrap not working on oreo/pie without permissive kernel. Try this
https://www.google.com/amp/s/forum....rnel-permissive-patcher-android-t3506338/amp/
I will make you twrp soon. Will pm you when its ready.
Edit: no need to build new twrp for your device, data encrypted on oreo/pie.
After booting in TWRP download and flash no-verity-opt-encrypt-6.0 zip to disable data partition encryption
Click to expand...
Click to collapse
I switched to s8 dual g9500. It has twrp from @jesen but it has an issue. Can you fix it?
https://forum.xda-developers.com/ga...ecovery-twrp-galaxy-s8-s8-snapdragon-t3636718
quanqw said:
I switched to s8 dual g9500. It has twrp from @jesen but it has an issue. Can you fix it?
https://forum.xda-developers.com/ga...ecovery-twrp-galaxy-s8-s8-snapdragon-t3636718
Click to expand...
Click to collapse
You should ask in that thread
4.09-B01 is up
- TWRP updated to 3.3.0.
- Fix reboot function.
- Add reboot to safestrap button in reboot menu.
- Add Edl button in reboot menu.
- Move Boot Options to advanced menu items.
- Safestrap app: Update topjohnwu's libsu to 2.4.0.
- Safestrap app: Update install recovery function.
Damn, needs root. I misread the post at first so ignore my previous question.
Hi,
I just installed this on my g892a, however it fails to mount /data. It looks like it's trying to mount /dev/block/sda24, however, on my phone it's actually /dev/block/sda23:
I tried changing the partition in /etc/safestrap/ss.config but that didn't do anything
Is there anything I can do to get it to mount, or do you need to recompile twrp?
Thanks!
cd109876 said:
Hi,
I just installed this on my g892a, however it fails to mount /data. It looks like it's trying to mount /dev/block/sda24, however, on my phone it's actually /dev/block/sda23:
I tried changing the partition in /etc/safestrap/ss.config but that didn't do anything
Is there anything I can do to get it to mount, or do you need to recompile twrp?
Thanks!
Click to expand...
Click to collapse
You need to edit twrp.fstab and ss.config in twrp recovery too.
I will try to add support for G892A in the next build.
afaneh92 said:
You need to edit twrp.fstab and ss.config in twrp recovery too.
I will try to add support for G892A in the next build.
Click to expand...
Click to collapse
Alright, I haven't built twrp / safestrap before so I'm having some trouble figuring it out, but I don't want to bug you with that. I do have a question though - when i get this working, could i flash a rom (to the stock rom slot) like a stock oreo rom with the same bootloader revision and keep safestrap installed? And then if I wanted to I could restore the backup of the nougat rooted rom? It looks like it can be done with the regular s8, but I'm confused as to whether it would work here or what I would need to do.
cd109876 said:
Alright, I haven't built twrp / safestrap before so I'm having some trouble figuring it out, but I don't want to bug you with that. I do have a question though - when i get this working, could i flash a rom (to the stock rom slot) like a stock oreo rom with the same bootloader revision and keep safestrap installed? And then if I wanted to I could restore the backup of the nougat rooted rom? It looks like it can be done with the regular s8, but I'm confused as to whether it would work here or what I would need to do.
Click to expand...
Click to collapse
Rom slot is broken on arm64 devices.
You can use stock slot only.