This is the thread for the TWRP 3.0 recovery for Samsung Galaxy Alpha (SM-G850F). The recovery uses a kernel built from the Samsung sources with root prevention disabled. It is fully working but still be careful and make backups!
DOWNLOAD
XDA:DevDB Information
recovery_twrp_slte, Tool/Utility for the Samsung Galaxy Alpha
Contributors
modpunk
Source Code: http://git.cryptomilk.org/projects/android/android_device_samsung_slte.git/
Version Information
Status: Stable
Current Stable Version: 3.1.1-2
Stable Release Date: 2017-11-30
Created 2014-11-06
Last Updated 2017-11-30
CHANGELOG
2017-01-26
Some bug fixes
Supports sltexx, slte and slteskt
2016-02-13
Update to version 3.0.0-0
Cleaned up device tree
Nicer fonts
2015-09-02
Set SELinux to permissive mode on boot
2015-09-01
MTP and ADB Support
Improved UI with better fonts
2014-11-10
USB OTG support (backup to external usb drive)
2014-11-06
Initial release
Thanks for your work. Glad to you in our device forum.
1 question, does your recovery include support for usb otg? In other words is it possible to backup/restore from usb flash drive?
neofral said:
Thanks for your work. Glad to you in our device forum.
1 question, does your recovery include support for usb otg? In other words is it possible to backup/restore from usb flash drive?
Click to expand...
Click to collapse
I haven't tested it. Does TWRP support this by default? If yes then we should get it working ...
P.S.: I've ordered a USB OTG cable now ...
modpunk said:
I haven't tested it. Does TWRP support this by default? If yes then we should get it working ...
P.S.: I've ordered a USB OTG cable now ...
Click to expand...
Click to collapse
officially yes. check it out here http://teamw.in/project/twrp2
neofral said:
officially yes. check it out here http://teamw.in/project/twrp2
Click to expand...
Click to collapse
OK. It doesn't work cause USB_OTG is not compiled in the kernel. The question is if the SoC has a USB OTG controller...
modpunk said:
Please try it. I will investigate once I got the USB OTG cable.
Click to expand...
Click to collapse
i just tried. the drive is listed as sd card. it has 0MB available even though my usb drive is an empty 32 gb drive formatted with fat32. when i select it for the backup, the selection goes dimm for couple of seconds and comes back back without it being selected and no error message.
by the way, is it possible to do a screenshot with TWRP?
neofral said:
i just tried. the drive is listed as sd card. it has 0MB available even though my usb drive is an empty 32 gb drive formatted with fat32. when i select it for the backup, the selection goes dimm for couple of seconds and comes back back without it being selected and no error message.
by the way, is it possible to do a screenshot with TWRP?
Click to expand...
Click to collapse
The /sdcard folder is normally pointing to /data/media/0.
modpunk said:
The /sdcard folder is normally pointing to /data/media/0.
Click to expand...
Click to collapse
can you change it to point to mnt/UsbDriveA?
this is the path where i see the usb drive via root explorer
EIDT: i have Xperia V device with latest TWRP, i did a backup and restore without any glitches
neofral said:
can you change it to point to mnt/UsbDriveA?
this is the path where i see the usb drive via root explorer
EIDT: i have Xperia V device with latest TWRP, i did a backup and restore without any glitches
Click to expand...
Click to collapse
Looking at the ROM it should be /storage/UsbDriveA maybe we need to create that folder first ...
Maybe you can test this. Boot into recovery, connect to it with 'adb shell' or use twrp terminal and create the directory "/storage/UsbDriveA". Then attach the usb drive.
modpunk said:
Looking at the ROM it should be /storage/UsbDriveA maybe we need to create that folder first ...
Maybe you can test this. Boot into recovery, connect to it with 'adb shell' or use twrp terminal and create the directory "/storage/UsbDriveA". Then attach the usb drive.
Click to expand...
Click to collapse
didn't work. couldn't connect with adb shell when on recovery (maybe not correct drivers insatlled). when creating /storage/UsbDriveA, attached usb drive and it's empty and doesn't list the drive in the storage options.
however, when browsing with root explorer a folder like that already exists
Will it work exynos varient of Galaxy alpha thats available in India with Model No. 850Y?
shranav said:
Will it work exynos varient of Galaxy alpha thats available in India with Model No. 850Y?
Click to expand...
Click to collapse
Try it and find out! I will probably not get a phone from India ....
Recovery with USB OTG support has been updated!
modpunk said:
Recovery with USB OTG support has been updated!
Click to expand...
Click to collapse
is it different from the one i tested couple of days ago (on 7th)? if it's the same, no need to flash for me. i'm happy to have USB OTG support and being able to backup/restore on usb. i have to admit, the internal storage is full already. that's why i needed this support. thank you for enabling this :good:
Is it the G-850FQ?
savasdok said:
Is it the G-850FQ?
Click to expand...
Click to collapse
this thread on the title it says it's for SM-G850F. it's also tested to run well on 850F.
if you want ot test on FQ, you're welcome. if you test, please post back and confirm if it works :good:
anybody have problems with download ,I rich 99% of file & downloading stop
I dont know is this happend to me only or is site problem!!
---------- Post added at 18:00 ---------- Previous post was at 17:55 ----------
Sorry,problem was on my download manager
neofral said:
this thread on the title it says it's for SM-G850F. it's also tested to run well on 850F.
if you want ot test on FQ, you're welcome. if you test, please post back and confirm if it works :good:
Click to expand...
Click to collapse
Got it, thanks.
Will this work with the 850A? Thanks
Related
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
HTC Droid DNA (dlx)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
Currently running this on my galaxy note and it works great, putting it on my dna now
is this CWm any faster than the ld one as far as backup and such
CM11 installing works?
thanks!!
How did you guys get this installed?
Just through command line or through another method?
Your help is appreciated
jcyoun33 said:
How did you guys get this installed?
Just through command line or through another method?
Your help is appreciated
Click to expand...
Click to collapse
Flash GUI app
Pretty colors and nice interface. Thanks for this. If you use Flash GUI it will ask you to rename it first. I changed it to "recovery.img" and it flashed no problem.
matteebee said:
Pretty colors and nice interface. Thanks for this. If you use Flash GUI it will ask you to rename it first. I changed it to "recovery.img" and it flashed no problem.
Click to expand...
Click to collapse
is it any faster than the older one ?
About the same as far as backups. I put .hideandroidprogress in clockworkmod folder and my 2.2 gb backup took about 4 mins. Appears to be packed with features I don't know how to use yet but will be quite handy to have.
Can you restore twrp backups or do you need to create new ones?
xlxcrossing said:
Can you restore twrp backups or do you need to create new ones?
Click to expand...
Click to collapse
I was able to restore a TWRP backup when I switched the settings to TWRP mode.
Glad to see this finally making its way to the DNA. Will flash it later today. :sly:
Tapatalked from my HTC Droid DNA
matteebee said:
About the same as far as backups. I put .hideandroidprogress in clockworkmod folder and my 2.2 gb backup took about 4 mins. Appears to be packed with features I don't know how to use yet but will be quite handy to have.
Click to expand...
Click to collapse
Can you link to how to add this mod? Thank you in advance.
nice looking UI, but I can't seem to do adb push blah.zip /sdcard/
not sure why though, because i tried it earlier before i wipe my phone and it worked to seem a small file, but does not work with a larger file size?
I tried it in the twrp beta and it works perfectly fine
this is by far my favorite recovery in all the years ive been a flashaholic.
-DroidIsDNA- said:
Flash GUI app
Click to expand...
Click to collapse
Thanks! Such a dope app!
CM Updater
For those of you that get hasty and install things without reading the FAQ.
Phil3759 said:
CMUpdater cannot flash downloaded files
If you get a /sdcard/0 error, it means you have /sdcard set as /data/media/0 in recovery
The reason is that CM app doesn't support /data/media/0 and is faking recovery with a /sdcard/0 implementation
You still can alter the setting and force it to /data/media in Advanced menu. This will give full compatibility with cwm, CM roms and CM Updater
Click to expand...
Click to collapse
Learn from my mistakes. Also the rude response I got in the 3 minutes before I edited my post in the Philz Recovery thread was the reason people hate this website.
Does this recovery not show up in adb when connected to the PC via USB?
rayjr13 said:
Does this recovery not show up in adb when connected to the PC via USB?
Click to expand...
Click to collapse
ADB works fine for me, make sure you have set the USB connection to Media Device (MTP) under the Menu in Storage
chooven said:
ADB works fine for me, make sure you have set the USB connection to Media Device (MTP) under the Menu in Storage
Click to expand...
Click to collapse
The phone list in adb devices when booted to the rom but in recovery I don't get any connection to it via adb.
MTP works well I used adb to move my backups when booted to the rom but in recovery I could not use adb or adb shell to tinker.
Gonna try the SDK manager to see if I'm out of date or something.
After a long time of trying to get things right, i finally got things right.
So here it is:
TWRP RECOVERY 3.2.1-0 FOR THE MOTO X FORCE (KINZIE)
This is an actual port and not a recompile of a different version for another device.
It is not yet official but i intend to submit my device tree, so it gets official.
It is probably never going to be official, but i'll try and provide frequent updates.
Everything *should* work, as far as i was able to test.
I am not sure about encryption though, as i have not encrypted my device, nor do i intend to do so atm.
Encryption should be ok now. (TWRP team has put a lot of effort in this).
Encrypted partitions cannot be read atm.
This would probably also work for the Droid 2 Turbo, if someone finds a way to unlock the BL.
I will try to maintain TWRP for this device, fixes may take a while though as i am not having a lot of time to work on this.
Installation:
1. Unlock your device
2. Download the image
3. Power off the phone
4. Boot to fastboot (VOL DN + POWER)
5. plug your usb cable install via fastboot:
Code:
fastboot flash recovery TWRP_3.2.1-0_Kinzie.img
If you want to keep OTA Update ability you can also temporary boot to TWRP. You would have to repeat this step everytime you want to go to TWRP then:
Code:
fastboot boot TWRP_3.2.1-0_Kinzie.img
Download here:
Version 3.2.1-0
http://www.mediafire.com/file/o6gcj4hhjahf936/TWRP_3.2.1-0_Kinzie.img
Version 3.1.1-0
http://www.mediafire.com/file/y2k08c6m5tazhbo/TWRP_3.1.1-0_Kinzie.img
Version 3.1.0-0
https://www.mediafire.com/?7h4u37ddiohwy45
Credits go out to the people of Teamwin Recovery project for creating this nice piece of software!
And credits go to @Arasthel, who is a great dev!
Official Changelog 3.2.1-0
Fixes for kinzie:
- USB OTG now working
- TWRP internal folder should be now accessible via /sdcard symlink
- cm updater is reporting device correctly now as kinzie
Amazing, the most beautiful and wanted TWRP version! Tested and working perfectly! Using it as my recovery, not boot only.
Enviado de meu XT1580 usando Tapatalk
Awesome! It's cool to have an actual port and to know that you will try to maintain it so we can have future updates .
I'm curious, though. What is the difference between this and clark recovery? Did you build it with the latest motorola kernel, which includes msm8994 support or make some BoardConfig changes? I mean, they share the same config and base kernel, at least, the basics that make TWRP work - wifi and other modules are a whole different story, but they are not needed for recovery.
Arasthel said:
Awesome! It's cool to have an actual port and to know that you will try to maintain it so we can have future updates .
I'm curious, though. What is the difference between this and clark recovery? Did you build it with the latest motorola kernel, which includes msm8994 support or make some BoardConfig changes? I mean, they share the same config and base kernel, at least, the basics that make TWRP work - wifi and other modules are a whole different story, but they are not needed for recovery.
Click to expand...
Click to collapse
To be honest, differences are marginal at this point, as of now we've got the fstabs by-name assignments there is almost no way of messing things up with partition assignments (which is kinda the no. 1 thing to do right in recovery). At the moment i am still using a prebuilt kernel and ramdisk i extracted from the device, because when i started building the device tree the kernel sources haven't been available. And when they finally were i decided to first fix the issues i already had, before introducing new ones. The whole graphics sub routines of TWRP (minuitwrp) recently had undergone a pretty big overhaul and so we've lost ability to flip screen on the way. I recently made a patch to fix this for overlay devices (which the kinzie is), and since then, TWRP is running fine on the native kinzie build. The overhaul also made the use of a custom graphics.c obsolete. (I suspect you had to use that?) I made the device tree mostly from scratch, only looking at similiarities at trees from hima and clark. (Hima has msm8994 too, clark has a different chipset as you know, but is a moto device).
You can have a look at it here. Please note that this is not absolute latest configuration (haven't uploaded it yet) and it still needs a little cleanup before submission. After that, i am going to throw in kernel sources from motorola and fetch the prebuilts necessary.
If you are interested in learning more you can contact me via PM.
Just flashed and working 100%. Moto X force BR version.
Thx a lot dude :good: just flashed and working.
no more upside/down issue :silly:
and nice theme btw
Thanks a lot mate! working as expected.
Perfect and beauty one! Thanks!
Xadro, just to let you know that the OTG is not working yet. Tried several things but no good yet. If you need some one to test some workarounds just let me know.
marzliak said:
Xadro, just to let you know that the OTG is not working yet. Tried several things but no good yet. If you need some one to test some workarounds just let me know.
Click to expand...
Click to collapse
I'll look into it as soon as I can. Might also be a general issue in twrp.
Thanks for this @Xadro . I just received my Moto X Force yesterday, it's great to see this available.
One thing I noticed is that the /sdcard/TWRP folder doesn't seem to be accessible (tried ES File Ex and Android terminal). Android Terminal displayed 'do not have permission' ls -al showed normal perms for the directory
fubofo said:
Thanks for this @Xadro . I just received my Moto X Force yesterday, it's great to see this available.
One thing I noticed is that the /sdcard/TWRP folder doesn't seem to be accessible (tried ES File Ex and Android terminal). Android Terminal displayed 'do not have permission' ls -al showed normal perms for the directory
Click to expand...
Click to collapse
Are you talking of the external sd card (sdcard1)? Or the internal emulated one?
Moderator Edit: @MuyKurioso - it is not necessary or desirable to quote the entire OP. Some users have limited bandwidth or are Mobile - this can affect page load times. Please consider this in the future. Thanks.
Are you currently trying to port CM to Kinzie? Or just waiting to help out someone? Just curious, and thanks for all your hard work in this recovery!
fubofo said:
Thanks for this @Xadro . I just received my Moto X Force yesterday, it's great to see this available.
One thing I noticed is that the /sdcard/TWRP folder doesn't seem to be accessible (tried ES File Ex and Android terminal). Android Terminal displayed 'do not have permission' ls -al showed normal perms for the directory
Click to expand...
Click to collapse
You need root to look inside that folder, you need to access through data/media/0/TWRP you probably did not give superuser permissions to your file manager.
Does this work for the turbo 2?
Xadro said:
Are you talking of the external sd card (sdcard1)? Or the internal emulated one?
Click to expand...
Click to collapse
I have backed up to the internal emulated sdcard.
I wanted to sync the folder and backup to my NAS
Sent from my XT1580 using Tapatalk
---------- Post added at 10:16 AM ---------- Previous post was at 10:13 AM ----------
AztekSoul said:
You need root to look inside that folder, you need to access through data/media/0/TWRP you probably did not give superuser permissions to your file manager.
Click to expand...
Click to collapse
It is accessible through TWRP file manager.
I did try with root permissions in ES File Explorer. Although i haven't tried that directory - is it a symlink?
Sent from my XT1580 using Tapatalk
fubofo said:
It is accessible through TWRP file manager.
I did try with root permissions in ES File Explorer. Although i haven't tried that directory - is it a symlink?
Click to expand...
Click to collapse
/sdcard is a symlink to /data/media/0/. The explanation why it isnt accessible in /sdcard is simple. The folder is not owned by media_rw.
To fix this, navigate to /data/media/0 in ES File Explorer. Then highlight TWRP folder by long touching it. Go to properties and change owner and group of the folder to media_rw. This should fix access rights when trying to access the folder via /sdcard symlink.
Xadro said:
/sdcard is a symlink to /data/media/0/. The explanation why it isnt accessible in /sdcard is simple. The folder is not owned by media_rw.
To fix this, navigate to /data/media/0 in ES File Explorer. Then highlight TWRP folder by long touching it. Go to properties and change owner and group of the folder to media_rw. This should fix access rights when trying to access the folder via /sdcard symlink.
Click to expand...
Click to collapse
Thanks, managed to chown the directory in terminal emulator. All works great now, thanks
Sent from my XT1580 using Tapatalk
Hello @Xadro!
I tested new Clark TWRP 3.0.0-1 version (twrp-3.0.0-1-clark.img) in my MOTO X FORCE and everything worked perfect (except MTP in my case). I believe this new version could be a good base for a Kinzie recovery. What do you think?
rodrigoger said:
Hello @Xadro!
I tested new Clark TWRP 3.0.0-1 version (twrp-3.0.0-1-clark.img) in my MOTO X FORCE and everything worked perfect (except MTP in my case). I believe this new version could be a good base for a Kinzie recovery. What do you think?
Click to expand...
Click to collapse
There is something for you in the OP
TWRP FOR SAMSUNG GALAXY J7 PRIME (SM-G610F/M)
*** Disclamer
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* or any other problems u face. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we aren't to be held reponsible.
Be sure to backup your data,contacts,apps,etc. as the internal storage may need to be wiped
Flashing Instructions
1. Download The Odin flashable Zip
2. Enable OEM unlock in your developer options.
3. Enter Download mode (Vol Down + Home Button + Power Button while switched off)
4. flash the twrp by placing downloaded zip in AP section and flash it while keeping auto reboot off.
5. Once it shows PASS... Press vol down + home + power..
6. when the phone turns off...immediately shift to volume up + home + power.
7. U Will boot to twrp...
8. If you just wanna root... just flash supersu using otg or sideload...
9.if you wanna mount internal ... flash the kernel provided below and Wipe internal... [WARNING : your device will be formatted...make a backup first]
10. Enjoy
FEATURES
1.touch Working
2. f2fs file system support (read, write, format, backup & restore)
3.exFAT file system support (read, write, format, backup & restore)
4.NTFS file system support (read, write, format)
5.ADB root
6.ADB Sideload
7.Full SELinux support
8.OTG support
9. Backup And Restore
10. MTP supported
ISSUES
1. Sdcard Doesnt mount
2. MTP doesnt work
3.Samsung encryption is not supported yet in TWRP 3 (see: https://gerrit.omnirom.org/#/c/17308/)
DOWNLOADS
TWRP - DOWNLOAD
MODDED KERNEL- HERE
CREDITS:
TWRP team..
Samsung
max35000 (for the kernel)
thank you bro..
gooooooooood job
---------- Post added at 03:02 PM ---------- Previous post was at 02:58 PM ----------
it works!!!!!!!Thank you very much brother
dacochir said:
thank you bro..
gooooooooood job
---------- Post added at 03:02 PM ---------- Previous post was at 02:58 PM ----------
it works!!!!!!!Thank you very much brother
Click to expand...
Click to collapse
np still...cant figure out sdcard mounting... but i think otg compensates for that
Varun hellboy said:
np still...cant figure out sdcard mounting... but i think otg compensates for that
Click to expand...
Click to collapse
Yes that's right. Otg cable was detected. There is no need to ADB. Thank you very much brother:good:
MTP fixed
hello, thanks for this one.
TWRP works well, touch screen works.
Since sdcard not detected, how to flash supersu.zip?
I tried method sideload but it doesn't work well.
Difficult to use cmd on windows xp
backup and restore not working
dafikjunior said:
hello, thanks for this one.
TWRP works well, touch screen works.
Since sdcard not detected, how to flash supersu.zip?
I tried method sideload but it doesn't work well.
Difficult to use cmd on windows xp
Click to expand...
Click to collapse
Use otg....or wipe internal...flash kernel and reboot...put supersu in internal and flash
dacochir said:
backup and restore not working
Click to expand...
Click to collapse
Working for me.... I must be doing something wrong.....see attachment for proof
Varun hellboy said:
Working for me.... I must be doing something wrong.....see attachment for proof
Click to expand...
Click to collapse
Should I use a kernel that you have introduced?
I am currently using the ROM DoomsDay I'm gonna get this ROM backup.
Should I install the kernel that you have introduced?
thank you very much brother...:good:
dacochir said:
Should I use a kernel that you have introduced?
I am currently using the ROM DoomsDay I'm gonna get this ROM backup.
Should I install the kernel that you have introduced?
thank you very much brother...:good:
Click to expand...
Click to collapse
yes....it is highly recommended.. use it
guys i have uploaded a new kernel based off latest stock rom....use that as a wifi lag is seen while using max's kernel on Roms like Doomsday....
Is the modded kernel has some features, or just modded to enable to mount the internal storage?
@Varun hellboy. Base on experience, Can u help me build a twrp recovery for j7109 (china version). I cant find out any twrp really working for it. May be it'snt international version. I can provide things as u need. Thank in advanced!
steviejrdn said:
Is the modded kernel has some features, or just modded to enable to mount the internal storage?
Click to expand...
Click to collapse
only allows mounting....i will make a feature packed kernel later..
kien_vip said:
@Varun hellboy. Base on experience, Can u help me build a twrp recovery for j7109 (china version). I cant find out any twrp really working for it. May be it'snt international version. I can provide things as u need. Thank in advanced!
Click to expand...
Click to collapse
Ask J700 guys..
Oh thanks. May be I'll ask guys with j7xxx series.
Is there anyway to backup without USB OTG? i hate to flash the modded kernel also, because it cause a trouble for my stock rom...
thanks
Not Working
not working for me.
Greetings!
I'd like to present a TWRP recovery for the single-sim Xperia X. This release works on Xperia X F5121 and F5122
DISCLAIMER:
I'm not responsible for any damage done to your device. You have been warned.
REQUIREMENTS
Unlocked bootloader
Working ADB and Fastboot (You can get the latest version through Android Studio or by visiting this site)
FEATURES
MTP support
ADB Sideload
Backups and restores almost every partition
Full SELinux support
Working encryption. You can access /data within recovery
NEEDS TESTING
USB-OTG
DOWNLOADS
INSTALLATION
Unlock the bootloader
Download the file
Put the following code in CMD/Terminal:
Code:
fastboot flash recovery twrp-3.1.1-suzu-*.img
//Replace * with the version you want to flash
Unplug the cable
Press Volume Down + Power to activate the recovery. When installed properly, the device should vibrate funnily, purple LED should appear and after a couple of seconds you should see the TWRP screen.
Enjoy!
BUILD
You need to sync the OmniROM and vendor blobs from DonkeyCoyote. You can find my sources on GitHub.
android_device_sony_loire_common
https://github.com/omnirom/android_bootable_recovery/commits/android-7.1
Thanks:
@grayleshy - for initial TWRP
@AndroPlus for some of his flags
OmniROM team for sources
If you find my work useful, consider buying me a cup of coffee
[TWRP] TWRP 3.1.0 for Xperia X
Old OP below:
Team Win Recovery Project 3.1.0
REQUIREMENT:
- Unlocked bootloader
FEATURES:
- MTP support
- USB OTG storage support
- Covers most partitions for nandroid backups
- ADB root
- Full SELinux support
- Support for partition decryption
Download: Dropbox
Installation via the bootloader (Platform-tools (adb & fastboot))
Code:
fastboot flash recovery recovery.img
Running TWRP: turn the phone off, wait 5 seconds, then pinch at the same time the power key and the volume down key until the device vibrates, release the keys. Recovery starts within 5-10 seconds.
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
Special thanks kistigun for testing recovery on the device.
Changelog: twrp.me
TWRP was going on OmniRom 7.1 sources and XperiaDeveloper.
SOURCEs: Suzu; loire; Common.
Nice work! Finally no more decryption problems on the X!
Working well, thanks!
One question ; is it possible to reboot the recovery via twrp reboot menu (or use an app like flashfire /flashify)? When I've tried the phone boots normally instead.
baddesthad said:
One question ; is it possible to reboot the recovery via twrp reboot menu (or use an app like flashfire /flashify)?
Click to expand...
Click to collapse
Unfortunately the reboot Recovery does not work from the specifics of the section, but in the future maybe will be fixed. If I don't find how to fix that button will be removed.
samavar89 said:
Unfortunately the reboot Recovery does not work from the specifics of the section, but in the future maybe will be fixed.
Click to expand...
Click to collapse
Good to know, thanks for clarifying
Is there a difference to the 3.1.0 TWRP recovery from the Poison thread?
Oel said:
Is there a difference to the 3.1.0 TWRP recovery from the Poison thread?
Click to expand...
Click to collapse
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
kistigun said:
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
Click to expand...
Click to collapse
Ah...
Ok, Thanks!
kistigun said:
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
Click to expand...
Click to collapse
No,
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
someone knows a recovery that finally works?
robby.pgn said:
No, don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
Click to expand...
Click to collapse
This problem is strange, please provide a log recovery.
I flashed this on my xperia x dual on nougat 7.0
I can go to recovery but when i try to turn on the phone normally it says "The phone is corrupt and cant be trusted bluh bluh..."
it says press power button to continue but when i press it screen turns off and nothings happens
what should i do?!
Kianush said:
I flashed this on my xperia x dual on nougat 7.0
I can go to recovery but when i try to turn on the phone normally it says "The phone is corrupt and cant be trusted bluh bluh..."
it says press power button to continue but when i press it screen turns off and nothings happens
what should i do?!
Click to expand...
Click to collapse
In Your kernel there is support for DM-Verity and Sony RIC?
it's stock kernel man, I unlocked bootloader and flashed stock nougat for xperia X dual sim
I just wanna root it, if there is any other way pls help me out
-----
btw after this problem i used flashtool to flash system and kernel from stock rom to be able to use my phone again
robby.pgn said:
No,
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
someone knows a recovery that finally works?
Click to expand...
Click to collapse
Kianush said:
it's stock kernel man, I unlocked bootloader and flashed stock nougat for xperia X dual sim
I just wanna root it, if there is any other way pls help me out
-----
btw after this problem i used flashtool to flash system and kernel from stock rom to be able to use my phone again
Click to expand...
Click to collapse
use this tool/guide to make a rooted kernel(and edit DM-Verity and Sony RIC): https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
grayleshy said:
Team Win Recovery Project 3.1.0
Click to expand...
Click to collapse
I've installed and tried this TWRP in my Xperia X with MM. Very nice that it can access the data partition! I did not try to install any zip yet.
Some problems I've seen:
dmesg.log: no output
recovery.log: https://pastebin.com/EwbtuC9q
What is interesting in the output:
Code:
I:cmd: /sbin/exfat-fuse -o big_writes,max_read=131072,max_write=131072 /dev/block/mmcblk1p1 /external_sd
CANNOT LINK EXECUTABLE "sh": cannot locate symbol "__fwrite_chk" referenced by "/sbin/busybox"...
I:exfat-fuse failed to mount with result '', trying vfat
I:Unable to mount '/external_sd'
I:Actual block device: '/dev/block/mmcblk1p1', current file system: 'vfat'
Looks like something is not right with the busybox in the image. Maybe it is that what is causing the external sdcard (in my case in exfat filesystem) not being mounted?
Thanks
robby.pgn said:
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup.
Click to expand...
Click to collapse
This problem is almost resolved, just need to test, but I don't have time to compile recovery. In the test version recovery without decryption, problem solved.
juliompinheiro said:
I've installed and tried this TWRP in my Xperia X with MM. Very nice that it can access the data partition! I did not try to install any zip yet.
Some problems I've seen:
dmesg.log: no output
recovery.log: https://pastebin.com/EwbtuC9q
What is interesting in the output:
Code:
I:cmd: /sbin/exfat-fuse -o big_writes,max_read=131072,max_write=131072 /dev/block/mmcblk1p1 /external_sd
CANNOT LINK EXECUTABLE "sh": cannot locate symbol "__fwrite_chk" referenced by "/sbin/busybox"...
I:exfat-fuse failed to mount with result '', trying vfat
I:Unable to mount '/external_sd'
I:Actual block device: '/dev/block/mmcblk1p1', current file system: 'vfat'
Looks like something is not right with the busybox in the image. Maybe it is that what is causing the external sdcard (in my case in exfat filesystem) not being mounted?
Click to expand...
Click to collapse
This issue failed to reproduce, and yet there is no solution. You the problem is not in Busybox, and something else.
grayleshy said:
Running TWRP: turn the phone off, wait 5 seconds, then pinch at the same time the power key and the volume down key until the device vibrates, release the keys. Recovery starts within 5-10 seconds.
Click to expand...
Click to collapse
For whatever reason I'm not able to boot into TWRP like I should be. I've used the poison version of TWRP before so I know what to do, and yet the phone will just boot normally despite holding volume down and power when off.
I know that TWRP is installed though as I am able to boot to it if I first boot to the bootloader using a USB cable but that is very cumbersome to do though.
grayleshy said:
This issue failed to reproduce, and yet there is no solution. You the problem is not in Busybox, and something else.
Click to expand...
Click to collapse
Clearly for the image available at your dropbox there are some libraries dependency errors, not only for the 'busybox', but also for other binaries that are in /sbin.
I do not know why this issue is only happening on my device since you said you can't reproduce this error. If there is anything I can do to help solve this strange behavior, count on me. I am an advanced linux user, but not too familiar with android specifics.
On latest 333 ROM for UK so that fingerprint scanner works on my Xperia X F5121.
I also modified by kernel/boot so that TWRP doesn't brick (actually boot loop) the device like it did the first time. After using these awesome instructions flashing TWRP recovery from here didn't kill the device any longer: https://forum.xda-developers.com/crossdevice-dev/sony/root-root-stock-firmware-modern-sony-t3558904
I was able to take an early nandroid backup before a bunch of Titanium restores, etc. Now I get stuck at "Backing up data" step and it literally doesn't move to the next file. Attaching an image of where I get stuck. FYI, I do use password encryption on the backup and I did disable MD5 creation... still just stuck.
Next tests are to:
see if the stall is on the same exact file number
try no encryption
do a check disk (fsck) type of repair just in case I have corruption --- on my brand new device
Any suggestions greatly appreciated!
UPDATED:
I only back up Boot, System & Data (the default)
On second attempt it stopped at file 18869 of 22065 --- so it does jump and not consistently stop at a certain file.
Warning !!! Use this module on your own risk !!! I can't be held responsible for any kind of damage or data loss !!!
Version 1.3 and higher requires my custom kernel 6.2.7.1_v3 or higher + Selinux magisk module from the kernel thread
Magisk 20.3 recommended
This module will add NTFS/F2FS/EXT4/exFAT read/write support to USB OTG.This means that the usb storage (usb stricks,external hard-drives,etc) will be mounted automatically
if one of the supported filesystem is detected.
**Note: F2FS support require a custom kernel,with F2FS support enabled** --> custom kernel thread
The module will also set external write permission for Kodi (this was required because Kodi doesn't support such permission or the request for it)
It also enables sys_fs read permission for Kodi, so it can read the CPU temperature without root permission.
Note 2: This was tested with Magisk v20,so i highly recommend you to use that version or higher !
Note 3: Some EXT4 drives may fail to mount,most likely this is because e2fsck it's failing to check for errors. In the next version i will try to add a newer version of e2fsck.However, formatting to EXT4 directly on the device will fix the issue.
Installation :
Install the module with Magisk Manager or TWRP
Reboot and insert the usb drive
Changelog
v1.0 - Initial release
v1.1 - Possible fix for the mount/unmount loop
v1.2 - Added custom kernel detection (with exFAT support) and updated some of the exFAT binaries
v1.3 - This version requires my custom kernel 6.2.7.1_v3 or higher + Selinux magisk module from the kernel thread
v1.4 - Major rework of the module ,now it workes with all Magisk 20.3 + version (tested up to 21.0 and canary builds)
v1.4.1 - Fixed binaries execute permission
VOLD sources - > Github
Thanks, much appreciated & I will try this soon. Maybe flashing with TWRP is a better idea as flashing modules through Magisk is known to cause problems.
So after following the steps in the topic to unlock and root, install Magisk first an then you package?
I tried to install you package with TWRP but it failed with an error.
---------- Post added at 01:22 AM ---------- Previous post was at 12:51 AM ----------
It installed after adding Magisk but when playing video from the harddrive it has an unexpected error and the drive seems to unmount and then remount.
Installed fine in magisk, just not supposed to update magisk itself in magisk, that you do in twrp. Magisk models themselves should be ok
DarkH2O said:
So after following the steps in the topic to unlock and root, install Magisk first an then you package?
I tried to install you package with TWRP but it failed with an error.
---------- Post added at 01:22 AM ---------- Previous post was at 12:51 AM ----------
It installed after adding Magisk but when playing video from the harddrive it has an unexpected error and the drive seems to unmount and then remount.
Click to expand...
Click to collapse
What kind of hard-drive you are using, it has external power? And what filesystem?
Pretoriano80 said:
What kind of hard-drive you are using, it has external power? And what filesystem?
Click to expand...
Click to collapse
NTFS, Its a WD Easystore and it does not have external power.
DarkH2O said:
NTFS, Its a WD Easystore and it does not have external power.
Click to expand...
Click to collapse
Probably that's the issue, i don't think the power supplied thru the FireTV charger is enough.
I only tested on a hard-drive with external power.
Pretoriano80 said:
Probably that's the issue, i don't think the power supplied thru the FireTV charger is enough.
I only tested on a hard-drive with external power.
Click to expand...
Click to collapse
Do you think a powered usb hub could help with that?
DarkH2O said:
Do you think a powered usb hub could help with that?
Click to expand...
Click to collapse
It might, but never tested personally. I'm planning to buy such a hub too.
Will there be a way to transfer/move or install apks to the external storage?
Not sure if it is working and mounting 100%. Might need some work, was able to link apps to usb but seems like some errors can cause the usb to amount at times. Good start for sure, hopefully you can get this working 100% when moving apps to the usb.
Leonidas87 said:
Not sure if it is working and mounting 100%. Might need some work, was able to link apps to usb but seems like some errors can cause the usb to amount at times. Good start for sure, hopefully you can get this working 100% when moving apps to the usb.
Click to expand...
Click to collapse
What do you mean with "link apps to usb"? That won't work and it's not recommended to use an OTG device as adoptable storage storage.
What kind of device you are using as OTG storage and the filesystem?!
Amazon modified the Android framework heavily, so adoptable storage it's a no go for now, to much hassle to spend time on that,a custom rom would a better solution.
However, without logs, it's hard to understand the reason why the drive disconnects/unmounts, it could be a power failure, corrupted fs or simply the unstable exfat/ntfs driver.
I managed to reproduce the unmounting/mounting issue with an EXT4 USB stick.
The are I/O Buffer issues, so i will have to investigate if this issue is caused by vold or something else.
Edit: OP udated with a new version,please test it and report back!
I'm not using it as adoptable storage, just able to move apk data to the usb drive and still load the apk. Seems like the usb drive would keep connecting and reconnecting.
Seems like you are aware of the connect/disconnect loop. If I'm not mistaken I am running exfat most likely.
Look your recent update is working better. Keep up the great work, all apk data is on the usb drive right now and loaded correctly on your latest
Once in a wile it messes up a bit, seems like heavy use can cause the usb to unmount
Leonidas87 said:
I'm not using it as adoptable storage, just able to move apk data to the usb drive and still load the apk. Seems like the usb drive would keep connecting and reconnecting.
Seems like you are aware of the connect/disconnect loop. If I'm not mistaken I am running exfat most likely.
Click to expand...
Click to collapse
That's why i pushed the new version, to fix that particular issue.
Leonidas87 said:
Once in a wile it messes up a bit, seems like heavy use can cause the usb to unmount
Click to expand...
Click to collapse
I've tested the new version with an USB Stick (ext4) and 2 external hard-drives (with external power supply) which have multiple EXT4 and NTFS partitions.I've tested them roughly, let them play two full movies and none of them failed (even if there was simultaneous read-write on them).
exFAT it's unstable and it was unstable with my initial testing too, probably less when i'm using my custom kernel with exfat (non-fuse) support.
There's a reason why it's still "staging" in linux kernel, i guess.
DarkH2O said:
NTFS, Its a WD Easystore and it does not have external power.
Click to expand...
Click to collapse
Have you tried the new version? If you do, please let me know if that hard disk works now!
Tried on tank : It stuck on FireTV logo how to remove (or zip to remove) ?
enestu said:
Tried on tank : It stuck on FireTV logo how to remove (or zip to remove) ?
Click to expand...
Click to collapse
It's for AFTV 4k (mantis) only, not for tank!
Reboot to TWRP and from Advanced -Terminal use this command :
rm - r /data/adb/modules/aftvotg
Then reboot to FireOS.