Related
TWRP
6 June 2014 [v2.7.1.0] md5sum: ce3dace05b3994a18d5ef327509edd97
Recovery for flashing in Odin [DOWNLOAD] md5sum: cb3dda4cb604a523c09fe8da7d13e2d8
Source
Credits:
TeamWin
Dees-Troy
CWM
CWM 6.0.5.0 md5sum: 4bfb28bcf29dc04243df246860f24940
Recovery for flashing in Odin CWM 6.0.5.0 md5sum: b5856bd395248af1c74dac8b92cd258e
For Odin: select the ops file, enable one package in options, then load the md5 file with the One Package button[1]
Install Directions:
Download to sdcard
Reboot into existing recovery
Install zip
Reboot recovery
Upgrades
Same as install directions above
Older TWRP Recoveries
17 Mar. 2014 [v2.7.0.0] md5sum: 43d156bfc38476239eeb9728b6130b00
Recovery for flashing in Odin [DOWNLOAD] md5sum: 6d7a708ddf70a8c73f41d66fe79cf883
* Flash pre-kitkat roms
* Use model number, rather than serial number. Rename back-up directory to SGH-T679
Note: v2.6.3.0 will only work with KitKat.
18 Feb. 2014 [DOWNLOAD] md5sum: 4e1625e2021c1ed13d396a3d263252a1
Recovery for flashing in Odin [DOWNLOAD] md5sum: 7fb9d25fe4f1c97136566f2847851cde
* Changes
25 Jan. 2014 md5sum: 2bd3bf72741279b5b3ea7747a977573a
Recovery for flashing in Odin md5sum: 52094a40ecd01512018d613de7ba15ab
* Add usb mount
5 Jan. 2014 [DOWNLOAD]
TWRP 2.6.3.0 md5sum: 2bd0281efe5edb83fa0a42f43f621b2b
* Fixed backwards compatibility, thanks to @meekrawb
* For those that renamed backup folder from serial no. to model no. with 12/27 build will need to rename it back to serial no.
27 Dec. 2013
TWRP 2.6.3.0 md5sum: 931c00589311cd0ffdd8c6a085c82a15
Removed for backwards compatibility
Older CWM Recoveries
CWM 6.0.4.8 md5sum: 6a149c09f7711eb2b3c6c038fa65e012
Recovery for flashing in Odin CWM 6.0.4.8 md5sum: 7dfa121c83a7e5b5d9e198e65829dc04
CWM 6.0.4.7 md5sum: 0d41e83332600f5e9b3ee7eda9f28014
Recovery for flashing in Odin CWM 6.0.4.7 md5sum: be428304f6b11982068edb24b1820d86
CWM 6.0.4.6 md5sum: ad7478be7a07aa86a2d472496a701c9b
CWM 6.0.4.5 md5sum: 576630dac0959cb2d2620a0ab9f2e799
Recovery for flashing in Odin CWM 6.0.4.5 md5sum: 34a2fec6089968e382cf9cfd19737ce4
* For Odin: select the ops file, enable one package in options, then load the md5 file with the One Package button[1]
Does adb work for you? Was working for me with the old TWRP 2.5.1 built by smartguy44 if I remember correctly... but doesn't work with this one. (Didn't try today's update though.)
aaopt said:
Does adb work for you? Was working for me with the old TWRP 2.5.1 built by smartguy44 if I remember correctly... but doesn't work with this one. (Didn't try today's update though.)
Click to expand...
Click to collapse
Just tried it with linux and adb doesn't recognize it. I currently don't have anything for android on windows, so not sure if it's a driver issue or with twrp. I'll try on windows later and get back with you.
edit: Do you think this would work? Reversing the secondary_storage points in ramdisk does not mount sdcard1 in twrp. I have to compile twrp with them bound in the original order for it to mount sdcard1.
jfbs said:
Just tried it with linux and adb doesn't recognize it. I currently don't have anything for android on windows, so not sure if it's a driver issue or with twrp. I'll try on windows later and get back with you.
edit: Do you think this would work? Reversing the secondary_storage points in ramdisk does not mount sdcard1 in twrp. I have to compile twrp with them bound in the original order for it to mount sdcard1.
Click to expand...
Click to collapse
I don't think the mount points are related to my TWRP adb problem. Phone just doesn't show up at all for me in "adb devices" when booted to TWRP. Does it show up there for you?
And don't go to any trouble with Windows on my account -- this laptop runs Ubuntu Saucy 99% of the time, and only boots to Windows on rare occasions.
aaopt said:
I don't think the mount points are related to my TWRP adb problem. Phone just doesn't show up at all for me in "adb devices" when booted to TWRP. Does it show up there for you?
And don't go to any trouble with Windows on my account -- this laptop runs Ubuntu Saucy 99% of the time, and only boots to Windows on rare occasions.
Click to expand...
Click to collapse
No, it doesn't connect for me either. Looking for a solution.
edit: does anything from here stand out to you?
Will this work for the SGH-T759?
How do I get this on my device if so? I've rooted, custom recovery and flashed countless roms on many devices but this one has me stuck. Keep finding what I think is for the t759 but then all this t679 stuff pops up.
Any help would be great! Thank you!
noriyori said:
Will this work for the SGH-T759?
How do I get this on my device if so? I've rooted, custom recovery and flashed countless roms on many devices but this one has me stuck. Keep finding what I think is for the t759 but then all this t679 stuff pops up.
Any help would be great! Thank you!
Click to expand...
Click to collapse
no
jfbs said:
5 Jan. 2014 [DOWNLOAD]
TWRP 2.6.3.0 md5sum: 2bd0281efe5edb83fa0a42f43f621b2b
Fixed backwards compatibility, thanks to @meekrawb
For those that renamed backup folder from serial no. to model no. with 12/27 build will need to rename it back to serial no. Otherwise, there isn't any difference with this build.
27 Dec. 2013
TWRP 2.6.3.0 md5sum: 931c00589311cd0ffdd8c6a085c82a15
Removed for backwards compatibility
Issues:
Restore paths use model no. instead of serail no. for those on 12/27 version. See post #2.
USB Storage Mounting deprecated - looking for a fix
ADB sideload isn't connecting
Click to expand...
Click to collapse
The new TWRP went on, no problem!!! Thanks so much for tweaking it.
Edit: And it works great. Thank you for this update!
how to install?
Can someone please provide exact installation instructions for this?
download file, put on sd card, boot into recovery and then flash like you would a rom
smartguy044 said:
download file, put on sd card, boot into recovery and then flash like you would a rom
Click to expand...
Click to collapse
Thanks for the quick response! The link kept giving me a spam redirect like 20 times...then it finally worked.
Tried the newest build from OP. Mounting usb storage didn't quite work. Plus while trying to install a ROM I got the same mount error mentioned by someone in the CM11 thread. Went back to the 27-Dec build of TWRP (I think-- downloaded it when it was still in the CM11 thread) and the same ROM installed without issues.
aaopt said:
Tried the newest build from OP. Mounting usb storage didn't quite work. Plus while trying to install a ROM I got the same mount error mentioned by someone in the CM11 thread. Went back to the 27-Dec build of TWRP (I think-- downloaded it when it was still in the CM11 thread) and the same ROM installed without issues.
Click to expand...
Click to collapse
Internal and external storage mount on this device in recovery with win 8.1 quickly. Latest twrp installs rom's fine as well on mine.
Edit: Just to be sure, again, I wiped everything in twrp and installed 1/31 without any issues in less than 3 minutes.
jfbs said:
Internal and external storage mount on this device in recovery with win 8.1 quickly. Latest twrp installs rom's fine as well on mine.
Edit: Just to be sure, again, I wiped everything in twrp and installed 1/31 without any issues in less than 3 minutes.
Click to expand...
Click to collapse
I hope you'll forgive me if I don't find "it works for me" to be a convincing argument, based on the /data-and-kernel-related issues in your CM11 thread that affected some people's devices and not others.
But the good news is, now that your CM11 includes a kernel more friendly to the other set of devices, rebuilding TWRP seems to have included that kernel too. In other words, your 2630e build installed the 0220 CM11 build for me without complaining about the /data partition... and the 0220 ROM also booted without complaints. Thanks for keeping at it.
USB mount and adb are still not working for me with Ubuntu 13.10. But I can live without them, though they are nice to have.
Flashable from Stock Recovery
Are the recoveries flashable from Stock Recovery?
does it work
Does it work on SGH-T599N
g7755725 said:
Does it work on SGH-T599N
Click to expand...
Click to collapse
No, this is for the SGH-T679 only
Does anyone have a copy of the TWRP for flashing through odin? The links in this thread don't work.
Q&A for [RECOVERY][i9300] TWRP 2.8.0.1 touch recovery [2014-09-12]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
ext sdcard ext4 ?
Hi,
I have a gt-i9300 with official Rom ( Android 4.3 ). Rooted and twrp 2.8.0.1 installed, I buy it for support the team.
I have a ext sdcard 64Gb exFat ( Formatting initialy with the smartphone ).
I can't restore with twrp. It's a problem FS. Can i have a ext4 FS with this Rom ? the card are mount automatically ?
How to format ? with a Linux for example ? or an Apps on playstore ??
Thanks for this Site.
problem with TWRP2 !!
Whenever i boot my device it boots to recovery by default :/
But i can choose to "boot system" from twrp
The Q : how can i change it back to boot system by default ?
I'll be very thankful if someone helped me ^^"
help with backup and restore
Hello, i backup my data from my nexus 5 using twrp recovery backup and restore...when i restored it, music, videos and pdf files were not restored...my download folder also was blank...i backed up data on my otg pendrive...i examined the files on the otg from pc, i find 2 large data files data.ext4.win000 and data.ext.4win001....how do i retrieve data from these 2 files? Help please
strange76 said:
Hi,
How to format ? with a Linux for example ? or an Apps on playstore ??
Thanks for this Site.
Click to expand...
Click to collapse
AParted on the play store will format for you. Backup first!
Not sure about the ROM though... keep googling?
---------- Post added at 02:04 PM ---------- Previous post was at 01:59 PM ----------
Which model is this thread for?
The header is confusing:
Forum Home xda-developers Samsung Galaxy S III I9300, I9305 Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & Troubleshooting [Q&A] [RECOVERY][i9300] TWRP 2.8.0.1 touch recovery [2014-09-12]
Illuvitar said:
AParted on the play store will format for you. Backup first!
Not sure about the ROM though... keep googling?
---------- Post added at 02:04 PM ---------- Previous post was at 01:59 PM ----------
Which model is this thread for?
The header is confusing:
Forum Home xda-developers Samsung Galaxy S III I9300, I9305 Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & Troubleshooting [Q&A] [RECOVERY][i9300] TWRP 2.8.0.1 touch recovery [2014-09-12]
Click to expand...
Click to collapse
Thanks for the reponse.
My solution : Format ext sdcard 64Gb Fat32. I make this with gparted.
Official Rom not suported with ext4.
All works for twrp now.
Now, my Rom is : OmniRom 4.4 i wait for the android 5 ( i hope )
USB OTG Storage
Hello, I currently use Philz recovery on my i9300 and I can mount my USB flash drive through USB OTG, however I cant mount my flash drive in TWRP.
I have tried everything, formating flash drive to fat32, rebooting,using different types of flash drives.
USB OTG works fine,since the mouse works perfectly.
What can I do, because to me it is the most important feature to have in recovery?
Awesome
nice
Twrp 2830 OTG Drive?
Hi I'am new to twpr recovery, I wanted to use a OTG drive to flash roms, but when in recovery there is no option for usb format or mount. My OTG drive is fat32 formatted. The sd card is shown and internal storage but nothing else? can you please help.
plz solve
sorry for bad English
downloading problem downlod after 75% downloading stop why????
TWRP 2.8.3.0 touch recovery
from this site
For Flashable ZIP.
can i ask something?
This flashable zip is working on STOCK RECOVERY of S3 i9300 too?
---------- Post added at 10:57 AM ---------- Previous post was at 10:52 AM ----------
Adeelkamal said:
sorry for bad English
downloading problem downlod after 75% downloading stop why????
TWRP 2.8.3.0 touch recovery
from this site
Click to expand...
Click to collapse
same problem as of mine is 99%
CM12
Does this recovery support CM12? Thank you!
How compatible are backups between cwm and twrp?
Ricky_Karmator said:
Does this recovery support CM12? Thank you!
Click to expand...
Click to collapse
Backup&restore of LP-ROMs are working fine.
_narcolepsy_ said:
How compatible are backups between cwm and twrp?
Click to expand...
Click to collapse
Not. If you want to transfer old CWM-backups to TWRP-format, use Phillz-recovery (restore CWM and backup as TWRP afterwards).
updated from 2.8.5.0 with odin, but has swiped base band details from phone, have been using cm12 rom. how can I get base band back please.
can you tell me how to flash modem have lost data.
Twrp stuck after reset my i9300 (5.1.1. weekly)
Hello! I cannot exit twrp recovery which is stuck, after factory reseting my phone from inside CM12.1.
How can I restore my phone, and exit this twrp loop?
If anybody knows , please help!
Thanks
eurih70 said:
Hello! I cannot exit twrp recovery which is stuck, after factory reseting my phone from inside CM12.1.
How can I restore my phone, and exit this twrp loop?
If anybody knows , please help!
Thanks
Click to expand...
Click to collapse
I'm in the same position. I flashed the Galaxy project ROM using twrp and it keeps booting to TWRP recovery. I tried using the terminal command 'dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota' but it states 'no such directory' Really need help on this one please
TWRP Manager does not work for i9300 (m0).
TWRP Manager did not work when I tried to use it to update TWRP.
I've been told by the developer of TWRP Manager that it does not support the i9300 (M0).
Perhaps then a Zip of the latest version of TWRP should be the preferred way to upgrade from earlier (< v2.8.4.0) versions which cannot self-update using an IMG file?
factory reset on cm12.1 caused twrp bootloop
I am running unofficial cm 12.1 from this thread, together with TWRP 2.8.6.1.
Yesterday I did a factory reset inside cm. Upon reboot, I have a bootloop on twrp. The twrp splash screen pops up, stays on for 2-3 seconds, and the device reboots. This goes on and on.
Unfortunately my device charges fine on usb, but is not reconized on PC. For reference, here is what I see in dmesg output:
Code:
[20871.522790] usb 2-1.1: new full-speed USB device number 93 using ehci-pci
[20871.930703] usb 2-1.1: device not accepting address 93, error -32
[20872.002752] usb 2-1.1: new full-speed USB device number 94 using ehci-pci
[20872.410811] usb 2-1.1: device not accepting address 94, error -32
[20872.410979] usb 2-1-port1: unable to enumerate USB device
So I have not been able to reflash recovery with heimdall.
Does anyone have a suggestion on breaking this bootloop? Is there any way of loading an update or recovery on external sdcard?
Pedro
Hello
This is TWRP v 2.8.1.0 for the S4 Mini. It works for the I9195 - I do not know if it works for similar devices.
The problem was that TWRP after version 2.7.1.0 did not boot up - the phone tried to enter recovery mode but eventually booted into android.
This is because of commit https://gerrit.omnirom.org/#/c/8471/ which does not seem to work nice with the S4 Mini.
DISCLAIMER : You apply this recovery at your own risk - if something breaks or bricks I am not responsible
IMPORTANT NOTE :
a) The attached file is NOT a flashable ZIP and I will not provide one. You have to unpack the attached file and use heimdall or dd. If someone wants to provide a flashable zip - I am fine with that.
b) There is no F2FS support.
c) I do not know if there are still problems with the recovery sometimes not booting up - I tried it a couple of times and it worked every time. Tell us if you experience booting problems.
d) I am no coder - so I cannot help with things like encryption, luks or similar wishes.
How to install:
a) Boot your phone to download mode
b) Connect phone to PC
c) Get root on your PC
d) Unzip attached ZIP file
e) Check md5sum
f) heimdall flash --RECOVERY recovery.img --no-reboot (dd should work as well - take care of the right partition)
Thanks goes to:
Teamwin
OliverG96
_that
Additional information:
If you want to build this by yourself from sources open file twrp-functions.cpp and search for line:
Code:
int TWFunc::Set_Brightness(std::string brightness_value)
You can change it like that:
Code:
int TWFunc::Set_Brightness(std::string brightness_value)
{
return 0;
std::string brightness_file = DataManager::GetStrValue("tw_brightness_file");;
This should fix the problem. According to one of the developers there should also be a flag for specifying a brightness file that one can probably set to /nobrightness.
It works great on my I9195 !
From your recovery, i created the Odin version and flashed it.
Thank you very much.
I attach the Odin version of your recovery (Instructions: unzip the .zip file, and flash the .tar.md5 file with Odin 3.09 into AP field)
Recovery flashable ZIP version of TWRP 2.8.1.0 attached.
Mounting both (Internal and External) doesnt work
mike_san said:
Mounting both (Internal and External) doesnt work
Click to expand...
Click to collapse
What do you mean? Mounting works for me - I can mount System and Micro SDCard and I can access the files there with the TWRP File Manager. So no problem here. Works also with adb - I got access to the full file system. Might be a problem with your phone/setup.
thomson.aa said:
What do you mean? Mounting works for me - I can mount System and Micro SDCard and I can access the files there with the TWRP File Manager. So no problem here. Works also with adb - I got access to the full file system. Might be a problem with your phone/setup.
Click to expand...
Click to collapse
I confirm this.
I tried to mount and unmount System, Data and micro Sdcard... all ok.
Will it work with f4k kernel ?
lars85destroyer: both CM 12 and f4k work fine with or. As the recovery used isn't kernel dependent anyway, it's not an issue.
Works great so far, noticed only one (minor) issue:
I need to use encryption for my phone and for its backups as well (I'm a sysadmin and my phone is fully equipped to access my datacenter). When using keyboard to type encryption/decryption passwords, somethimes I hit one key and completely another key gets pressed, can't be due to fat fingers because wrong key that gets pressed is usually very far from the original one. This was very iritating sometimes since I needed to type passwords for 3-4 times in a row for them to work. Figured out how to prevent this, I look at whole keyboard carefully on every keystroke and I'm usually able to see when it gets buggy and hits wrong key (keystroke animation is trigerred), but this isn't very fast or comfortable...
I think I had the same problem with early versions of TWRP 2.7 posted here but it has been resolved in newer ones. Otherwise, works as a charm, if someone added full F2FS support it would be totally perfect
PS If my memory serves me well, fix was build.prop related.
ericlnu said:
lars85destroyer: both CM 12 and f4k work fine with or. As the recovery used isn't kernel dependent anyway, it's not an issue.
Click to expand...
Click to collapse
works fine on aicp, Thanks
s.basketbuild.com/devs/F4k/twrp/serranoltexx
this one have F2FS
CTR Recovery for Galaxy A5
Hi all,
I've ported CTR Recovery from the developer carliv (now bluefirebird) on our Galaxy A5.
This recovery is based on the old CWM, by koush, with some features you can find in the original post HERE, so if you are tired of the TWRP recovery and u are looking for something similar to the old CWM, don't hesitate to download this
NOTE: It should work in any A500 variant, but it's tested only on SM-A500FU variant, so flash on other variants at your own risk!
Desclaimer:
Code:
echo "I'm not responsable for bricked phones, overheat phones, for global warming, for phones that want to suicide without a reason and for imminent explosions"
DOWNLOADS: You can download the recovery here: https://www.androidfilehost.com/?w=files&flid=82499
HOW TO FLASH:
ON WINDOWS (Odin method)
1) Download Odin
2) Download the recovery (with .tar extension)
3) Go in download mode by pressing Power Button + Vol - + Home Button
4) Connect your smartphone to the PC
5) Open odin version 3.9 or 3.10
6) Select AP button and open the recovery file
7) Press start
8) Enjoy
ON LINUX (Heimdall method):
1) Extract tar file with:
$ tar xvf recovery_file.tar
You will find a recovery.img file
2) Open Heimdall Frontend
3) Select pit file (you can find it on sammobile)
4) Select recovery partition
5) Load the recovery.img file and flash
6 Enjoy
ON ANDROID (Need Root)
1) Download flashify or rashr
2) Extract recovery file with apps such as zArchiver and you will find a recovery.img file
3) Open flashify or rashr and select recovery file
4) Flash it
5) Enjoy
ON RECOVERY
IF YOU ARE ON TWRP:
1) Extract recovery file with apps such as zArchiver and you will find a recovery.img file
2) Reboot to recovery
3) Go to install zip menu
4) Select "Install Image" box
5) Select recovery.img file and flash in recovery partition
6) Reboot to recovery
6) Enjoy
ON TERMINAL
If you are on Android (any rom, TWRP, or CTR) (Need Root)
1) Open terminal. If you are on CTR you need Aroma FileManager
2) run:
$ dd if=/path/to/recovery.img of=/dev/block/bootdevice/by-name/recovery
If you are on adb run:
$ adb shell dd=/path/to/recovery.img (inside the phone, not the path of the recovery.img stored in the pc) of=/dev/block/bootdevice/by/name/recovery
3) Enjoy
[NEW] CTR with CWM graphics section
Well, since CWM support ended with cm-11.0, and no one resurrected it, I've decided to give my contributo to the best recovery (in my opinion) which written the begin of android customization, for flashing zip roms, take nandroid backups... So, as I said, since no one resurrected it, I've decided to modify ctr sources, which are based on CWM recovery and which are compilable in cm-12.1 and cm-13.0, for creating a recovery which has, CTR features, but which really like the old CWM.
-So, what does this version offer?
~If you want to know what does it include, please see read this (green highlighted text)
NOTE: If you want to compile with cwm recovery you need my fork which you can find here:
https://github.com/DeadSquirrel01/carliv_touch_recovery_new only cm-12.1 branch for the moment
Then you need to add in BoardConfig.mk (in the device tree) the following flag:
USE_CWM_GRAPHICS := true
otherwise it will compile standard CTR
Flashing instuctions:
Look at "HOW TO FLASH" section
Download Link: Same as CTR recovery link, but you have to download the ones wich have a name which begins with "[CWM]"
OTHER NOTE: Since I've compiled CTR with CWM graphich with an half crapped cm-12.1 source tree, and adb doesn't work (except in sideload), I couldn't take screenshot, so, I've uploaded some photos, instead, which are taken with my ~4 years ago Samsung Galaxy Pocket, so don't flame me for bad quality , and since I tried to upload in attachments, but it doen't show the photo when clicking on the attachment, I've upload a zip with 4 screenshots
HERE (Google Drive Link)
Credits:
@bluefirebird for recovery sources
@TheWhisp for device tree
Me (DeadSquirrel01) for porting the recovery , adding CWM graphics, editing images and adding some cwm features
Sources:
Device Tree: https://github.com/DeadSquirrel01/android_device_samsung_a5-common
CTR: https://github.com/carliv/carliv_touch_recovery_new
CTR with CWM graphics: https://github.com/DeadSquirrel01/carliv_touch_recovery_new branch cm-12.1 only for the moment and you need to add "USE_CWM_GRAPHICS := true" in BoardConfig.mk
Changelog
03/09/2016 (update N2):
_ Add menu color change: you can now change highligh+text color to 3 different colors: blue (default), green or orange.
See my github commit for info, I wrote some awesome comments
06/10/2017 (Update N3):
_Save menu color setting to /sdcard/clockworkmod/cwm_config, so that it's not lost on reboot, resulting a recovery which has always the blue color, even if the user has chosen orange or green.
Thanks for this contribution, try it just have time. For now, I walk with your version of TWRP working well. This CTR Recovery is compatible for install ROMs Marshmallow (Base Stock and CM13 Based)? Cheers.
Thank you DeadSquirrel01 it works perfectly on my A500G running stock marshmallow 6.0.1. Great work
oss_mosis said:
Thanks for this contribution, try it just have time. For now, I walk with your version of TWRP working well. This CTR Recovery is compatible for install ROMs Marshmallow (Base Stock and CM13 Based)? Cheers.
Click to expand...
Click to collapse
Yes you can install roms
meemb said:
Thank you DeadSquirrel01 it works perfectly on my A500G running stock marshmallow 6.0.1. Great work
Click to expand...
Click to collapse
Thanks for the support
you welcome brother
DeadSquirrel01 said:
Yes you can install roms
Thanks bro, unfortunately I have not been able to prove that the screen of my Galaxy A5 is broken and the phone is unusable for now, but I have already shared this Post on Facebook Group so that other users go testing, any news will be reporting here.
A hug. :good:
Click to expand...
Click to collapse
DeadSquirrel01 said:
Yes you can install roms
Thanks bro, unfortunately I have not been able to prove that the screen of my Galaxy A5 is broken and the phone is unusable for now, but I have already shared this Post on Facebook Group so that other users go testing, any news will be reporting here.
A hug. :good:
Click to expand...
Click to collapse
Thanks bro
Nice Recovery.. Succesfully rooted my stock 6.0.1 by flashing supersu (you can flash this file to root on any android which have custom recoveries) on this recovery. It is like stock recovery but with a lot of features.
@DeadSquirrel01 works well on A500F (Duos). Also i tried to get stuck in recovery mode with no succes . So i can say it`s better than twrp. I was waiting for this moment since i got the phone . Many many thanks! Cheers!
LE: Wait a second... So how this recovery has almost 3 months and isn`t that known?
LE2: Some feedback - mount usb storage doesn`t do anything (yes i have sdcard). Also no adb support. So is kinda impossible to push files into phone while it`s in recovery...
corsicanu said:
@DeadSquirrel01 works well on A500F (Duos). Also i tried to get stuck in recovery mode with no succes . So i can say it`s better than twrp. I was waiting for this moment since i got the phone . Many many thanks! Cheers!
LE: Wait a second... So how this recovery has almost 3 months and isn`t that known?
LE2: Some feedback - mount usb storage doesn`t do anything (yes i have sdcard). Also no adb support. So is kinda impossible to push files into phone while it`s in recovery...
Click to expand...
Click to collapse
You can only use sideload regarding adb and i think it isn't known coz everyone use only twrp now
DeadSquirrel01 said:
You can only use sideload regarding adb and i think it isn't known coz everyone use only twrp now
Click to expand...
Click to collapse
Personally i`m more with CWM.. Simple and yet so complex. TWRP is a bit more polished on the UI side, but that bug that keeps me in the recovery drives me crazy [emoji35] . This CTR recovery it`s able to reset the flag and push the device out of recovery... So it`s better IMO.
Anyway i read here and there that Nougat based roms can be flashed in CWM 6.0.5.x so i`ll try to port Philz latest recovery on our device, since i had it for years on my retired devices. Thanks for all your work and for the source!
LE: Sideload doesn`t work since adb isn`t enabled on the recovery..
corsicanu said:
Personally i`m more with CWM.. Simple and yet so complex. TWRP is a bit more polished on the UI side, but that bug that keeps me in the recovery drives me crazy [emoji35] . This CTR recovery it`s able to reset the flag and push the device out of recovery... So it`s better IMO.
Anyway i read here and there that Nougat based roms can be flashed in CWM 6.0.5.x so i`ll try to port Philz latest recovery on our device, since i had it for years on my retired devices. Thanks for all your work and for the source!
LE: Sideload doesn`t work since adb isn`t enabled on the recovery..
Click to expand...
Click to collapse
Windows adb? With linux adb works perfectly but with windows adb not ¯\_(ツ)_/¯
And... good luck with your philz port
DeadSquirrel01 said:
Windows adb? With linux adb works perfectly but with windows adb not ¯\_(ツ)_/¯
And... good luck with your philz port
Click to expand...
Click to collapse
Thanks... It`s on my todo list but i don`t have enough time to do anything now. About the adb - shouldn`t be same thing? What`s the difference between adb in linux and windows? Wait to switch linux to test. Could also be something specific to my device since you made the recovery for FU and i have F.. Cheers!
So i rebooted in linux and here`s the output:
Code:
[email protected] ~ $ adb devices
List of devices attached
???????????? no permissions
[email protected] ~ $ adb shell
error: insufficient permissions for device
And when tryin` to Mount USB Mass storage this is the output:
Code:
Error mounting /dev/sr1 at /media/hades/671D-12F5: Command-line `mount -t "vfat" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,shortname=mixed,utf8=1,showexec,flush" "/dev/sr1" "/media/hades/671D-12F5"' exited with non-zero exit status 32: mount: /dev/sr1 is write-protected, mounting read-only
mount: /dev/sr1: can't read superblock
I have 32gb class 10 sdcard formatted as fat32.. And from what i see it tries to mount as vfat, this for sure is from the fstab..
Any ideas?
corsicanu said:
Thanks... It`s on my todo list but i don`t have enough time to do anything now. About the adb - shouldn`t be same thing? What`s the difference between adb in linux and windows? Wait to switch linux to test. Could also be something specific to my device since you made the recovery for FU and i have F.. Will edit this post in a minute. Cheers!
Click to expand...
Click to collapse
Since it's a recovery it works with any a500xx variant (same chipset ) and also it's the same thing with roms for example on my pac-rom rom noone said it doesn't boot on a500xx. Regarding adb, bad drivers i think
I don't know how much i can thank you, when i use TWRP my phone won't boot into the system but it works perfectly with this recovery
Qcraft said:
I don't know how much i can thank you, when i use TWRP my phone won't boot into the system but it works perfectly with this recovery
Click to expand...
Click to collapse
So use thiz
What I like in it is while I am in this recovery and my phone is charging, and I select reboot, it boot to the system unlike other recovery.
I had installled custom ROMs, Flashed kernel image, and used ADB sideload so far
akil777 said:
What I like in it is while I am in this recovery and my phone is charging, and I select reboot, it boot to the system unlike other recovery.
I had installled custom ROMs, Flashed kernel image, and used ADB sideload so far
Click to expand...
Click to collapse
anyway if in twrp it doesn't reboot you can run $ reboot in advanced->terminal
DeadSquirrel01 said:
anyway if in twrp it doesn't reboot you can run $ reboot in advanced->terminal
Click to expand...
Click to collapse
Yep.. this terminal has commands nearly or exactly like linux ubuntu.
akil777 said:
Yep.. this terminal has commands nearly or exactly like linux ubuntu.
Click to expand...
Click to collapse
Yes, the commands of any linux distro, but they are less... only indispensable commands
All TWRP version is not compatible with the OneUI3.1 update samsung has released a few days ago. So in order to be able to flash custom ROMs or other things you need to use this recovery instead.
Notes:
- You can only flash files from USB thumb drive (OTG drive), from an external sdcard or using adb sideload
- Only FAT32 thumb driver (OTG drive) are supported. So make sure you formate your drive to FAT32 before using it with lineage recovery, otherwise, it won't be able to read your drive
- this recovery version only supports latest ADB version so make sure you're using it
Installation:
1. Reboot to download mode
2. Flash the file using odin
Download:
LineageOs-18.1 Recovery
ADB and fastboot
Bugs:
- Data decryption doesn't work
- Fastbootd
- Can't flash file from device internal storage
Change Log:
16th of March 2021
- Initial Release
F.A.Q:
How to flash files using adb side load?
1. Reboot to recovery
2. Select apply update then adb
3. plug your device using usb cable to your phone
4. open a new terminal/cmd in the same folder the file you want to flash
5. Type " adb sideload file_name.zip "
#reserved 3
Does VoLTE and proximity sensor work in this ROM?
msurg said:
Does VoLTE and proximity sensor work in this ROM?
Click to expand...
Click to collapse
This is not a ROM. It's lineage-18.1 recovery.
Please, read the title carefully
LahKeda said:
F.A.Q:
How to flash files using adb side load?
1. Reboot to recovery
2. Select apply update then adb
3. plug your device using usb cable to your phone
4. open a new terminal/cmd in the same folder the file you want to flash
5. Type " adb sideload file_name.zip "
Click to expand...
Click to collapse
please can you explain more , because i am beginner in this subject . my experience since note 2 , and now i buy galaxy m51 , please answer me.
M H N said:
please can you explain more , because i am beginner in this subject . my experience since note 2 , and now i buy galaxy m51 , please answer me.
Click to expand...
Click to collapse
This recovery is kind of abandoned. use TWRP 3.5.1 if you're on one ui3.1 or twrp 3.4 if you're on oneui 2.5
LahKeda said:
This is not a ROM. It's lineage-18.1 recovery.
Please, read the title carefully
Click to expand...
Click to collapse
My mistake. Apology.
@LehKeda I have a general question: am I right that LOS 18.1 recovery *in general* does not have native USB OTG support, but that you added it manually into your edition?
RootedLee said:
@LehKeda I have a general question: am I right that LOS 18.1 recovery *in general* does not have native USB OTG support, but that you added it manually into your edition?
Click to expand...
Click to collapse
it supports it, but sometimes you need your device usb.init.rc file to initialize USB and OTG stuff
Hi @LehKeda Aha. I'm having compatibility/ reliability issues with another device's USB OTG sometimes working and sometimes not in TWRP regardless if it was flashed the recommended way into the existing LOS 18.1 boot as RamDisk (via the new "Flash Current TWRP") or if it was flashed to boot directly to boot instead system.
Regarding LOS 18.1 recovery, just now this second I finally see the LED lid up on my flash drive connected via USB cable.
All this is intermittent, and I tend to need to go through several hoops to finally have USB OTG working. To make things even more convoluted, it's definitely worse with the latest LOS 18.1 recovery/ boot I just applied yesterday, then TWRP added (again as RamDisk). I do not know if TWRP uses its own USB OTG drivers if run flashed to RamDisk, or if it relies on whatever is present in the LOS section of the boot partition after repackaging by TWRP.
I don't want to hijack this thread, so let me detail the issue in the other thread. I'll post the link shortly. I'm sure it's just a few files missing like the one you mentioned, or a 100% correct config inside such a file.
I appreciate your expertise and will be back shortly
@LehKeda here: Nokia 6.1 TWRP 3.6.0/ 3.4.0 USB OTG Instructions
The TWRP in question: from the TWRP for DRG_sprout page, the latest official 3.6.0
LOS recovery/ boot images from Builds for PL2. The recovery I've been having best results with as base for TWRP is lineage-18.1-20220118-recovery-PL2.img.
I'm aware the Nokia 6.1 (my phone) and the 6.1 Plus (the one that TWRP was developed for) aren't exactly the same, but with everything else working, I doubt that the slight model differences are the cause for the USB OTG being unreliable; plus TWRP 3.4.0 [UNofficial] for the Nokia 6.1 has the same issue..
Maybe you have an idea over there how this can be stabilized
[EDIT]: I'll be offline now for around 24 hrs, so there will be a delay in response from my side, just that you know