Related
http://forum.xda-developers.com/xpe.../recovery-twrp-3-0-0-touch-recovery-t3309938/
This is deprecated.
In this thread I'll share the .img files of the latest TWRP available for our device, so you can flash them with Rashr/PhilZ/Cyanogen recovery.
Disclaimer:
you are responsible for what you do. If your device stops working after you follow this guide, it's not my fault. However, as usual, if you do things in a correct way, you won't face any problems.
Requirements:
any ROM with any kernel
unlocked bootloader
Don't flash it if you have got a locked bootloader!
Features:
up-to-date source
flashable signed zip
f2fs support
Changelog:
TWRP 2.8.7.0_8
- other cleanups
- startup now is not slow! It just takes 3 - 4 seconds!
- Reboot bug is fixed - maybe
TWRP 2.8.7.0_7
- optimizations and cleanups
TWRP 2.8.7.0_6
- f2fs for /system is supported (this is for Temasek users)
TWRP 2.8.7.0_5
- f2fs support improved
- minor optimizations
- less overheating
TWRP 2.8.7.0_4
- attempt to fix issues with reboot option
TWRP 2.8.7.0_3
- signed flashable zip added
TWRP 2.8.7.0_2
- f2fs bugs fixed
- fixed overheating
How to install:
flash the zip through any recovery (even Cyanogen recovery!)
Download from Android File Host:
[url]https://www.androidfilehost.com/?fid=24052804347826443[/URL]
Stock FOTAKernel to remove any recovery (included this one): [url]http://forum.xda-developers.com/xperia-sp/general/stock-components-flashable-zips-t3184111[/URL]
Be sure to select the right variant of your device!
Thanks to:
@[NUT]
@antr34
@TechnoSparks
This work in miui v6
Thanks a lot for this quick update :thumbup:
Working fine on AICP's official nightlies with stock kernel.
The TITAN has landed. Hide your works from this critic! The official maintainer of the XSP Lollipop and M Hub.
Rashr was not working for me. I got it to work with this command on the terminal (with root):
Code:
su
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Notice that you'd have to save the .img file on the proper directory prior to using the command.
You can find more details of my struggle here: http://forum.xda-developers.com/xpe...rnel-tangerine-kernel-v1-t3073297/page28#1379
Hope this helps someone with the same issue.
pilger said:
Rashr was not working for me. I got it to work with this command on the terminal (with root):
Code:
su
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Notice that you'd have to save the .img file on the proper directory prior to using the command.
You can find more details of my struggle here: http://forum.xda-developers.com/xpe...rnel-tangerine-kernel-v1-t3073297/page28#1379
Hope this helps someone with the same issue.
Click to expand...
Click to collapse
I use it and i cant flash nothing
Guizão BR said:
I use it and i cant flash nothing
Click to expand...
Click to collapse
What is the output of the command? Does it throw you an error or anything?
@pilger i'm here, what to do next?
Here's a more detailed description of what I did in order for this to be flashed on my FOTAKernel:
Booted into default Cyanogen Recovery;
Wiped Dalvik and everything else I could in order to flash a new ROM;
Flashed the UNOFFICIAL CM from July 26th;
Flashed Pico Gapps (I guess it doesn't matter which Gapps you install, though);
Booted into system and set up everything (accounts, wi-fi, etc.);
DID NOT install Rashr;
Plugged my device to PC using USB;
Transfered the twrp-2.8.7.0_huashan.img to the root of the internal storage;
Unplugged the device from the computer;
Enabled Developer options on Settings (by tapping like crazy on the build number);
On the Developer options, I turned on Terminal Command, and root access to both ADB and apps;
Opened the terminal and entered "su" command to get root;
Allowed root and set it to remember its choice;
Entered up the command:
Code:
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Rebooted on recovery mode;
TWRP 2.8.7.0 was functioning as expected.
pilger said:
Here's a more detailed description of what I did in order for this to be flashed on my FOTAKernel:
Booted into default Cyanogen Recovery;
Wiped Dalvik and everything else I could in order to flash a new ROM;
Flashed the UNOFFICIAL CM from July 26th;
Flashed Pico Gapps (I guess it doesn't matter which Gapps you install, though);
Booted into system and set up everything (accounts, wi-fi, etc.);
DID NOT install Rashr;
Plugged my device to PC using USB;
Transfered the twrp-2.8.7.0_huashan.img to the root of the internal storage;
Unplugged the device from the computer;
Enabled Developer options on Settings (by tapping like crazy on the build number);
On the Developer options, I turned on Terminal Command, and root access to both ADB and apps;
Opened the terminal and entered "su" command to get root;
Allowed root and set it to remember its choice;
Entered up the command:
Code:
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Rebooted on recovery mode;
TWRP 2.8.7.0 was functioning as expected.
Click to expand...
Click to collapse
I've got TWRP now, one question though, if I flash the next CM nightly, it wouldn't be overwrote by the cyanogen recovery?
J73 said:
I've got TWRP now, one question though, if I flash the next CM nightly, it wouldn't be overwrote by the cyanogen recovery?
Click to expand...
Click to collapse
Glad you got it to work, mate! Flashing CM shouldn't overwrite the recovery. I guess that's the purpose of having the recovery on FOTA.
I'm not an expert though. But I've tested a couple of times myself and TWRP is there after every flash.
pilger said:
Glad you got it to work, mate! Flashing CM shouldn't overwrite the recovery. I guess that's the purpose of having the recovery on FOTA.
I'm not an expert though. But I've tested a couple of times myself and TWRP is there after every flash.
Click to expand...
Click to collapse
Thanks to you! All's well now, I'm so glad to have TWRP again thank you!
pilger said:
What is the output of the command? Does it throw you an error or anything?
Click to expand...
Click to collapse
Sorry i Forgot to edit the play, this have more time to flash
There's a bug with f2fs, it will be fixed tomorrow. Thanks to @Adrian DC for pointing this out.
Tomoms said:
There's a bug with f2fs, it will be fixed tomorrow. Thanks to @Adrian DC for pointing this out.
Click to expand...
Click to collapse
Can you tell me about that bug cause I'm using f2fs for cache,data and media that's formatted through your recovery
Sent from my Xperia SP using Tapatalk
kunal9007 said:
Can you tell me about that bug cause I'm using f2fs for cache,data and media that's formatted through your recovery
Sent from my Xperia SP using Tapatalk
Click to expand...
Click to collapse
Are you using Tangerine? This bug is not present in Tangerine's TWRP.
Tomoms said:
Are you using Tangerine? This bug is not present in Tangerine's TWRP.
Click to expand...
Click to collapse
I'm using tangerine but I've flashed this TWRP first, and this recovery has fotakernel so i geuss it can't be overwritten
Sent from my XT1033 using Tapatalk
kunal9007 said:
I'm using tangerine but I've flashed this TWRP first, and this recovery has fotakernel so i geuss it can't be overwritten
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Well, strange. f2fs volumes couldn't be mounted.
Tangerine probably fixed the issue, same as my CM-12.1 boot image fixed the TWRP image.
The goal of the fix is to have F2FS working without the boot image flashed over TWRP to make clean installs.
Adrian DC said:
Tangerine probably fixed the issue, same as my CM-12.1 boot image fixed the TWRP image.
The goal of the fix is to have F2FS working without the boot image flashed over TWRP to make clean installs.
Click to expand...
Click to collapse
just realized that I didn't had tangerine installed i was on first build of official cm and then before flashing radium i formated to f2fs
Sent from my XT1033 using Tapatalk
---------- Post added at 09:00 PM ---------- Previous post was at 08:58 PM ----------
and i flashed tangerine after atleast 1 day use of stock kernel
Sent from my XT1033 using Tapatalk
Bevor you do something with your Device do a Backup of all your Data (Contacts, Pic´s ect.) outside of your Device (in a Cloud or on your PC)I'm not responsible for bricked devices, dead SD Cards, broken phone chargers etc.You do all at your own Risk!
If you are new, just work the first 3 steps from top to bottom.
Flash Root & Odin3:
At the https://autoroot.chainfire.eu/ site you can Download the the Root File for your Device (Link to A300FU). When you Downloaded the "CF-Auto-Root-xxx.zip" File unzip it. In this zip you will find the Odin3xxx.exe and the Root .tar.md5 File
You need this Odin3 tool also for TWRP and going Back to Stock Rom
For Root: Make sure your device is in ODIN download mode (you can get there by holding VolDown+Home+Power when the device is turned off), then start the included Odin3xxx.exe file, press the PDA/AP button, select the Root .tar.md5 file, and click Start, never interrupt this action! You can find more detailed instructions and assistance at [CENTRAL] CF-Auto-Root Thread
Flash TWRP:
You can Download the TWRP File at the [RECOVERY][ROOT][TWRP 3.0.2-1]Samsung Galaxy A3(2015) SM-A300F/FU/G/H/M Thread. I recommend the Build from Post 80 it has working MTP & OTG for the FU Device!
To Install Start download mode (you can get there by holding VolDown+Home+Power when the device is turned off), then start the Odin3xxx.exe file, press the PDA/AP button, select the TWRPxxx.tar file, and click Start, never interrupt this action! After Reboot you can get there by holding VolUp+Home+Power when the device is turned off.
There are also a TWRP 2.8.7.0 and a TWRP 3.0.0-0 but both have small bugs so i recommend TWRP 3.0.2-1 only if you have Problems try to downgrade
TWRP Bugs:
TWRP 2.8.7.0 Can only Install CM12.1 ROMs, it has no MTP & no OTG
TWRP 3.0.0-0 Can only Install CM13 ROM & it has no MTP but OTG is Working
TWRP 3.0.2-1 Can not install @cbolumar ROMs and the Build from Opening Post has no OTG
TWRP 3.1.0 Only tested with LineageOS, it still has no MTP!!!
Flash a Custom ROM:
You can Install a ROM now with TWRP you can enter TWRP by holding VolUp+Home+Power when the device is turned off.
In TWRP IT IS HIGHLY RECOMMEND TO DO FIRST A BACKUP! (I Recommend to placed at the SD Card)
Backup -> Storage : Micro SDcard -> Ok -> [x] Boot, [x] System, [x] Data, [x] Cache, [x] Recovery, [x] EFS, [x] MODEM, [x] APNHLOS -> Swipe to Backup
If anything goes wrong you can easy Restore your Device in TWRP without losing anything, so it's also recommended to Backup your Custom ROM
Now you need your Custom Rom, Google Apps like Opengapps for ARM and i recommend latest Magisk[/URL, OR (if you prefer) [URL="http://download.chainfire.eu/supersu"]SuperSU to Manage Root Access.
Place this zip Files at your Device (I Recommend to placed at the SD Card)
Now you enter TWRP and go to:
Wipe -> Advanced Wipe -> [x] Dalvik / ART Cache, [x] System, [x] Data, [x] Cache -> Swipe to Wipe
Now go back to main menu and select:
Install -> Storage : Micro SDcard -> Ok -> now choose your ROM zip first, you can "Add More Zips" and choose Gapps zip and if you want you can Add direct Magsik OR SuperSU zip as well -> Swipe to Confirm Flash
After placing files the Device need a Reboot, at the First Start it will Install your Rom, so be patiently at first start!
Flash Xposed:
Magisk user on Android M (6.x) or better follow this Thread [2018.5.6][Magisk] Systemless Xposed v89.3/v90.2-beta3 (SDK 21-27) by topjohnwu
SuperSU user on Android M (6.x) or better follow this Thread [OFFICIAL] Xposed for Lollipop/Marshmallow/Nougat/Oreo [v90-beta3, 2018/01/29]
info:
SDK 21: Android 5.0 | SDK 22: Android 5.1 | SDK 23: Android 6.0 | SDK 24: Android 7.0 | SDK 25: Android 7.1 | SDK 26: Android 8.0 | SDK 27: Android 8.1
at CM12.1 ROM's Offical Xposed works fine.
Download the "sdk22-arm" zip, and Install it with TWRP first start need a long time! be patient!
After the Framework is installed you install the "XposedInstaller" apk, done.
For stock rom you should visit [UNOFFICIAL] Xposed for Samsung Lollipop by arter97 but it´s for deodex'ed ROMs for this you should visit [Deodex][SM-A300] Deodex Thread for Samsung Galaxy A3
emtepe35 said:
Working only on MM touchwiz (tested by me on A300FU with TWRP 3.0.2-1)
How to install:
- Install this Xposed Installer App version http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
- Make a nandroid backup
- Copy the Xposed file and the uninstaller to your sdcard
- Flash "xposed-vxx.x-sdkxx-tw-armxx-custom-build-by-wanam-xxxxxxxx.zip" through a custom recovery (TWRP/CWM...)
- Reboot and Waiiiiiiiiit, it may take several minutes to boot up depending on your Rom size.
xposed.zip download (ARM SDK23)
https://www.androidfilehost.com/?fid=24591000424962808
Official thread link:
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
Click to expand...
Click to collapse
Flash Stock ROM:
Download your Firmware at Sammobile than i recommend you to Wipe all (Advanced Wipe) in TWRP except the SDcard!
Boot your Device in ODIN download mode (you can get there by holding VolDown+Home+Power when the device is turned off), then start the Odin3xxx.exe file, press the PDA/AP button, select the .tar.md5 file, and click Start, never interrupt this action!
After doing this you lose TWRP and Root so if you need it you have to install it new.
You should not try to Flash 4.x ROMs it could Brick your Device!
With a Stock Marshmallow ROM it is recommended to use a Custom Kernel
A300FU / A300Y Custom Kernel:
Kraken Kernel R1 from @bulgar
Will only work with at Stock Marshmallow (6.x) ROM
-soon- LineageOS Support
hadesKernel from @corsicanu
Will only work with at Stock Marshmallow (6.x) ROM
A300FU / A300Y Modification:
[MOD][Stock Rom] Enable More Quick Tiles on Touchwiz from @astrit1
Will only work with at Stock Lollipop (5.x) ROM
There are still the following Bugs:
No Bugs
[ROM][A300FU][6.0.1] [GS]Mod from @[GS]
There are still the following Bugs:
Private Mode Not Work
WHASISTROM We have a simple stock rom [A300FU/OL3/OJ5] from @nowheel Discontinued
nowheel said:
Bad news i abbandoned project.. after my hdd is broken with project and all whasistrom file, work document and other.
Click to expand...
Click to collapse
A300FU / A300Y Custom ROMs:
Check also in All Samsung Galaxy A3 (2015)'s ROMs Thread from @Falaysia
-Recommended-
LineageOS 15.1 Unofficial for Samsung Galaxy A3 (2015) from @vl_w
There are still the following Bugs:
* FM works only on headphones
* Unable to capture video in 1080p (only 720р works)
* Incorrectly work with secondary sim (incall sound issues)
* On FU and H doesn't adjusting flahlight brightness
* On H incorrectly detecting battery temperature
* Hardware keystore doesn't work (only software)
* NFC sometimes doesn't work
LineageOS 14.1 Unofficial for Samsung Galaxy A3 from @vl_w
There are still the following Bugs:
no Bugs
CyanogenMod 12.1 for Samsung Galaxy A3 from @evilracer123 Discontinued
Meizirkki said:
OP is no longer working on a300fu
Click to expand...
Click to collapse
In the Opening Post is not the latest Build!
This is the post with the last Build from 19th January 2016
evilracer123 said:
Here's the newest build:
https://mega.nz/#!OcJ0BKKQ!hkQN4SnzY-40tm9v79vzP_erZxIxtpa0_jPwMvLQaiU
Click to expand...
Click to collapse
There are still the following Bugs:
-SoD´s (can be Fixed for the most users by using CPU Awake - Wake Lock with Unlimited time & Activate on Reboot (Clean Master turns it off btw) or Wake Lock - PowerManager with "PARTIAL_WAKE_LOCK")
-Preview in stock camera (can be Fixed by change Resolution to 16:9 in Settings)
-FM Radio not Working (can be Fiexed by using Spirit2)
-Folders are not displayed correctly with LCD density 260 DPI (can be Fixed by changing it to 240 DPI)
-When screen is off touch buttons still working, at touch the phone vibrates.
-USB Conection adb only working MTP, PTP, OTG or UMS not Working (you can use MTP and OTG in TWRP 3.0.2-1 Recovery)
-for some users "com.qualcomm.timeservice" fc time to time (can be Fixed by disable the automatic services in Time settings)
-for some users gps are not Working
at my device:
-Cast screen is not Working
CyanogenMod 12.1 Resurrection Remix from @cbolumar Discontinued
garbanura said:
he switched to a5 and abandoned a3 for good, i know from first hand sorry.
Click to expand...
Click to collapse
There are still the following Bugs:
-SoD´s (can be Fixed for the most users by open integrated Kernel Adiutor and allow Root access)
-Preview in stock camera (can be Fixed by change Resolution to 16:9 in Settings)
-FM Radio not Working (can be Fiexed by using Spirit2)
-When screen is off touch buttons still working, at touch the phone vibrates.
-USB Conection adb only working MTP, PTP, OTG or UMS not Working (you can use MTP and OTG in TWRP 3.0.2-1 Recovery)
at my device:
-Cast screen is not Working
Note: can only installed with TWRP 2.8.7.0 after installing you can upgrade your Recovery to TWRP 3.0.2-1
CyanogenMod 12.1 from @cbolumar Discontinued
garbanura said:
he switched to a5 and abandoned a3 for good, i know from first hand sorry.
Click to expand...
Click to collapse
There are still the following Bugs:
-SoD´s (can be Fixed for the most users by using CPU Awake - Wake Lock with Unlimited time & Activate on Reboot (Clean Master turns it off btw) or Wake Lock - PowerManager with "PARTIAL_WAKE_LOCK")
-Preview in stock camera (can be Fixed by change Resolution to 16:9 in Settings)
-FM Radio not Working (can be Fiexed by using Spirit2)
-When screen is off touch buttons still working, at touch the phone vibrates.
-USB Conection adb only working MTP, PTP, OTG or UMS not Working (you can use MTP and OTG in TWRP 3.0.2-1 Recovery)
-for some users "com.qualcomm.timeservice" fc time to time (can be Fixed by disable the automatic services in Time settings)
at my device:
-Cast screen is not Working
Note: can only installed with TWRP 2.8.7.0 after installing you can upgrade your Recovery to TWRP 3.0.2-1
Hope this will Help to answering the most Questions
By the way i'm not a Dev, i'm only a regular user that wants to help!
You will also get Information and Help at the Everything Samsung a3 Thread :good:
Nice guide. Which one would you recommend between the CM12.1 and CM12.1 RR?
Also, for downgrading TWRP, you just need to flash the older version, right?
King-V said:
Nice guide. Which one would you recommend between the CM12.1 and CM12.1 RR?
Also, for downgrading TWRP, you just need to flash the older version, right?
Click to expand...
Click to collapse
Definitely CM12.1 RR!
Right just flash first TWRP 2.8.7.0 via Odin3 install the ROM and than Flash TWRP 3.0.2-1 via Odin3, btw. the Build from post 80 has a working MTP and OTG in TWRP (only in TWRP not at the ROM!)
And you can anytime time flash TWRP 2.8.7.0 again if you have to Install new
So only good ROM for daily driver will be @mygalaxya cm13?
emtepe35 said:
So only good ROM for daily driver will be @mygalaxya cm13?
Click to expand...
Click to collapse
This could need some time, i recommend to try CyanogenMod 12.1 Resurrection Remix, or a Stock MM with aresKernel :good:
Jonny_Hood said:
This could need some time, i recommend to try CyanogenMod 12.1 Resurrection Remix, or a Stock MM with aresKernel :good:
Click to expand...
Click to collapse
It's lot to do with RR to make it stable without SOD etc. (I really need normal usb connection for daily usage)
What's twrp should I use with stock mm to flash ares kernel and can I go back to lollipop via odin? (Mygalaxya's cm13 needs LP bootloader and modem)
emtepe35 said:
It's lot to do with RR to make it stable without SOD etc. (I really need normal usb connection for daily usage)
What's twrp should I use with stock mm to flash ares kernel and can I go back to lollipop via odin? (Mygalaxya's cm13 needs LP bootloader and modem)
Click to expand...
Click to collapse
Best is TWRP 3.0.2-1 and yes you can go back anytime via odin
Jonny_Hood said:
Best is TWRP 3.0.2-1 and yes you can go back anytime via odin
Click to expand...
Click to collapse
Thanks I tried this but I flashed wrong firmware and wifi was broken but I know how to repair it.
Tomorrow I'll try flash compatible firmware and try again.
After flash MM and reflash LP it was a bootloop in first boot. I went to download mode and flash twrp then restore backup and it boots up.
Thanks
emtepe35 said:
Thanks I tried this but I flashed wrong firmware and wifi was broken but I know how to repair it.
Tomorrow I'll try flash compatible firmware and try again.
After flash MM and reflash LP it was a bootloop in first boot. I went to download mode and flash twrp then restore backup and it boots up.
Thanks
Click to expand...
Click to collapse
This Bootloop thing happened at my Device sometimes too, if i flashed a stock ROM via Odin, thats why i started to Wipe all Partitions via TWRP before flashing, that works for me flawless
Than happy flashing tomorrow
Jonny_Hood said:
This Bootloop thing happened at my Device sometimes too, if i flashed a stock ROM via Odin, thats why i started to Wipe all Partitions via TWRP before flashing, that works for me flawless
Than happy flashing tomorrow
Click to expand...
Click to collapse
OK I've got one last question the wipe in twrp means it deleting it to zero and if I accidentally go to system and not to download I'll get hard brick? Or wipe means it restoring it to factory files? Wipe modem too?
Sorry for noob questoms but I want to be sure before do anything
emtepe35 said:
Wipe in twrp means it deleting it to zero?
Click to expand...
Click to collapse
Yes
emtepe35 said:
If I accidentally go to system and not to download I'll get hard brick?
Click to expand...
Click to collapse
No it will not brick, if you accidentally go to system it will stuck at A3 logo, than you can go to Download Mode with pressing "VolDown+Home+Power" for 30 Sec
emtepe35 said:
Or wipe means it restoring it to factory files? Wipe modem too?
Click to expand...
Click to collapse
Wipe -> Advanced Wipe -> [x] Dalvik / ART Cache, [x] System, [x] Data, [x] Internal Storage, [x] Cache -> Swipe to Wipe -> go back -> go back -> Format Data -> yes
Added to Sticky Roll-Up Thread
Cheers
Razvan
Forum Moderator
Razvan said:
Added to Sticky Roll-Up Thread
Cheers
Razvan
Forum Moderator
Click to expand...
Click to collapse
Thank you very much
What about stock marshmallow xposed?
Sorry I'm noob and I can't find it alone.
emtepe35 said:
What about stock marshmallow xposed?
Sorry I'm noob and I can't find it alone.
Click to expand...
Click to collapse
As far i know, it will not working with Stock MM.
Known issues:
- Bootloops on Samsung stock ROMs. That's due to Samsung's changes to ART. There are unofficial builds that work around this by deodexing and adjusting the ROM.
Jonny_Hood said:
As far i know, it will not working with Stock MM.
Known issues:
- Bootloops on Samsung stock ROMs. That's due to Samsung's changes to ART. There are unofficial builds that work around this by deodexing and adjusting the ROM.
Click to expand...
Click to collapse
I had a LP stock Samsung touch wiz and it was working. Some people tells they have MM xposed. I'll try to ask them
emtepe35 said:
I had a LP stock Samsung touch wiz and it was working. Some people tells they have MM xposed. I'll try to ask them
Click to expand...
Click to collapse
Let me know if and how it work
I'm happy with this.
Working only on MM touchwiz (tested by me on A300FU with TWRP 3.0.2-1)
How to install:
- Install this Xposed Installer App version http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
- Make a nandroid backup
- Copy the Xposed file and the uninstaller to your sdcard
- Flash "xposed-vxx.x-sdkxx-tw-armxx-custom-build-by-wanam-xxxxxxxx.zip" through a custom recovery (TWRP/CWM...)
- Reboot and Waiiiiiiiiit, it may take several minutes to boot up depending on your Rom size.
xposed.zip download (ARM SDK23)
https://www.androidfilehost.com/?fid=24591000424962808
Official thread link:
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
Hi, what I have to do to downgrade my A300FU to lollipop (Brand Italy Vodafone)?
InfamousMykol said:
Hi, what I have to do to downgrade my A300FU to lollipop (Brand Italy Vodafone)?
Click to expand...
Click to collapse
Stock ROM:
Download your Firmware at Sammobile than i recommend you to Wipe all (Advanced Wipe) in TWRP except the SDcard!
Boot your Device in ODIN download mode (you can get there by holding VolDown+Home+Power when the device is turned off), then start the Odin3xxx.exe file, press the PDA/AP button, select the .tar.md5 file, and click Start, never interrupt this action!
After doing this you lose TWRP and Root so if you need it you have to install it new.
No longer supported
Unofficial TWRP 3.1.1 w/F2FS
> For the Nexus 6 Shamu
This work is inspired by @The Flash's F2FS TWRP builds. I based this build off of the TWRP Minimal Repo.Features:
TWRP 3.1.1
F2FS Mounting and Formatting supported (En/Decryption not supported, however)
Built atop my kernel
Works
Changelog:
3.1.1-3
Updated sources to 7.1.2_r33, which includes updated f2fs-tools (1.8.0)
Minor GUI tweaks (splash screen, odd gap under "Advanced")
Bump to subversion 3
Installation:
You should know the drill of installing custom recoveries if you found this thread, but anyways:
Have an UNLOCKED Bootloader
Boot to fastboot/bootloader mode (Power + Vol Down from power off)
In adb (replace X with appropriate subversion):
Code:
fastboot flash recovery twrp-3.1.1_X-f2fs-unofficial-shamu.img
You can now reboot to your shiny, new TWRP!
How Do I convert to F2FS?
Backup important data to an EXTERNAL source; if formatting /data, entire internal sd will be wiped.
Ensure your kernel/kernel you will flash supports F2FS. You can use my kernel if you desire.
Reboot to this (or any other) F2FS supported TWRP
Go to -> Wipe -> Advanced Wipe
Tick the desired partition you want to format (ONLY do /data and/or /cache)
Select "Repair or Change Filesystem"
Select "Change File System"
Select "F2FS"
Swipe to Change
Done. Flash all your stuff!
Disclaimer:
I am not responsible for broken devices etc... Flash at your own risk. I am also not affiliated with the official TWRP crew nor Omni ROMs, so please don't complain to them about bugs unique to my own builds.
Sources:
Manifest
TWRP Recovery
Device Tree
Kernel
XDA:DevDB Information
Unofficial TWRP for Shamu w/F2FS, Tool/Utility for the Nexus 6
Contributors
Black_Hat01, Omni Rom, and the great devs of TWRP itself
Source Code: https://github.com/BlackHat01/
Version Information
Status: No Longer Updated
Current Stable Version: 3.1.1-3
Stable Release Date: 2017-09-26
Created 2017-06-27
Last Updated 2018-02-10
Downloads
Download Latest 09/26 Build - 3.1.1-3
How do i make it keep my settings. Every time i boot into twrp i have to swipe to allow modifications and need to set settings again. Also it does not see my backups i made with previous twrp 3.1.1-0
Thanks a lot for this. Does it properly decrypt F2FS data?
Neejay said:
Thanks a lot for this. Does it properly decrypt F2FS data?
Click to expand...
Click to collapse
I don't use encryption so I cannot say. If you can test it for me that would be appreciated
UPDATE:
TWRP Official 3.1.0 changelog states TWRP will try to mount both ext4 and f2fs on decrypt, so It should work.
TMG1961 said:
How do i make it keep my settings. Every time i boot into twrp i have to swipe to allow modifications and need to set settings again. Also it does not see my backups i made with previous twrp 3.1.1-0
Click to expand...
Click to collapse
It should not reset your settings every time you boot into recovery, unless there is something wrong with your /sdcard/TWRP folder. Can you send a recovery log (Advanced > Copy Log)?
Will do that after finishing the install of the rom i am doing now.
TMG1961 said:
Will do that after finishing the install of the rom i am doing now.
Click to expand...
Click to collapse
Thank you. I ask because I am not having that issue at all. Maybe also try re-flashing recovery via fastboot before everything too.
what i did was this. Booted into bootloader. erased recovery, flashd your recovery and booted into it. wiped to allow changes and made changges to settings. Then booted back into rom. The rom i tried it with was stock 7.1.1.
I just finished installing velocity rom and flashed your twrp, same result. I did copy the log. said in twrp that it was copied to /data/media/recovery.log but the log is no were to be found on the phone. Did search the whole phone with root explorer
---------- Post added at 20:00 ---------- Previous post was at 19:59 ----------
when i try to do a backup i get error unable to mount storage
---------- Post added at 20:10 ---------- Previous post was at 20:00 ----------
I think the problem is something else. Not sure but twrp does not see my storage
Black_Hat01 said:
I don't use encryption so I cannot say. If you can test it for me that would be appreciated
UPDATE:
TWRP Official 3.1.0 changelog states TWRP will try to mount both ext4 and f2fs on decrypt, so It should work.
Click to expand...
Click to collapse
Unfortunately, it doesn't work. It doesn't recognize my unlock pattern and won't decrypt. I had to go back to xanaxdroid's 3.0.2.0 twrp for it to work
I did flash the previous twrp and copied the log file. Not sure if that contains what you need ut adding it so you can have a look
Neejay said:
Unfortunately, it doesn't work. It doesn't recognize my unlock pattern and won't decrypt. I had to go back to xanaxdroid's 3.0.2.0 twrp for it to work
Click to expand...
Click to collapse
Thanks for the update. Will look into it.
Black_Hat01 said:
Thanks for the update. Will look into it.
Click to expand...
Click to collapse
No problem. I tried to look for his source, but couldn't find one for shamu directly. Here's where I downloaded his img (if it helps at all): https://forum.xda-developers.com/showpost.php?p=70452221&postcount=29
TMG1961 said:
I did flash the previous twrp and copied the log file. Not sure if that contains what you need ut adding it so you can have a look
Click to expand...
Click to collapse
Can you flash my twrp and send log please? It is the correct log. I just need to see what's going on with mine. Thanks.
i can but after flashing your twrp then flash the old one again and copy the log to the sdcard ? Cause yours says it copies the log but there is no log on the sdcard.
TMG1961 said:
i can but after flashing your twrp then flash the old one again and copy the log to the sdcard ? Cause yours says it copies the log but there is no log on the sdcard.
Click to expand...
Click to collapse
That's odd. I was on Flash's 3.1.0-4 F2FS build and flashed mine right over that build and everything works fine for me (log copying works, settings stick fine, etc..), so maybe try flashing his build, then mine. Without a log, I can't really do much, since I, and nobody else yet has experienced the same issues. I'm going to do some work on it today, and I'll try to get a new build out tonight.
Thanks for your time and help. I downloaded 3.1.0-4 F2FS and 3.1.1-6 F2FS but on both the same. All version dont show anything on the sdcard when i go to advanced/file manager in twrp. So no idea what is causing it but almost sure the problem is on my side.
TMG1961 said:
Thanks for your time and help. I downloaded 3.1.0-4 F2FS and 3.1.1-6 F2FS but on both the same. All version dont show anything on the sdcard when i go to advanced/file manager in twrp. So no idea what is causing it but almost sure the problem is on my side.
Click to expand...
Click to collapse
Perhaps it is just your device. Anyways, I uploaded a new build, maybe try this one out. If it does not, try reflashing stock twrp 3.1.1 and then coming back to an F2FS modified one. Hope the best.
Is there any difference between this and the TWRP F2FS builds found at http://nchancellor.net/Downloads/TWRP/shamu/ ?
TMG1961 said:
...I just finished installing velocity rom
Click to expand...
Click to collapse
I thought that ROM ceased development a long time ago? Happen to have any links with more info on it? https://www.android-port.de/themen/rom-n-7-1-1-velocity-shamu.9596/
espionage724 said:
Is there any difference between this and the TWRP F2FS builds found at http://nchancellor.net/Downloads/TWRP/shamu/ ?
Click to expand...
Click to collapse
Thing is, by the time I posted, I hadn't realized he updated his. But the things that are different are basically the kernel the recovery image is built with (we use our own kernels), and the support. I will be actively building and supporting while The Flash has pretty much moved on from shamu to angler. Any bugs that arise I will try to fix and I will always be trying to keep everything updated. Over time our builds will start to become more and more different.
Latest TWRP changelog :
New features of 3.2.3-0:
Changelog)
Download Link - 64 bits version (non-treble)
twrp-3.2.3-0-64bits.img
Download Link - Treble version (64bits too)
twrp-3.2.3-0-treble.img
Working/Bugs
I have just tested on 16 GB variant and all seems to be working. If something is broken lemme know.
IMPORTANT NOTE :
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
Force encryption is enabled by default in stock OS and twrp will successfully decrypt /data at first boot if all goes well
If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data
Installation Guide
Make sure you have unlocked bootloader
Reboot to bootloader
fastboot flash recovery twrp-****.img (if you want permanent flash) or fastboot boot twrp-****.img (if you want temporary
boot)
XDA:DevDB Information
[Unofficial] TWRP 3.2.3-0 Moto G5, Tool/Utility for the Moto G5
Contributors
ZJRDroid
Source Code: Local manifests
Version Information
Status: Stable
Stable Release Date: 2019-01-18
Created 2019-01-18
Last Updated 2019-01-18
Thanks for the updated TWRP! Works like a charm
Are there any circumstances which would make it necessary to use the non-treble version?
image not signed or corrupted moto g 5 cedric. is this for cedric?
edit2: my friend used the fastboot boot recovery option the recovery booted and asked a password, then he pressed back and the other screen with the swipe button has appeares (allow system modifications) and now what to do? the sdcard folder doesn't have nothing inside, neither the external sd
update3: after requering the password he pressed back and then formatted the phone, phone booted into the stock rom, and the twrp is gone.
update4: tried install viperos cedric android 9.0.0 gave error 7 I don't know what to do twrp is working, he tried this https://www.youtube.com/watch?v=VCqROwIGLLE and now stock rom is gone. we are loosing hope ;-;
update 5: tried using the twrp provided by this guy https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737/page11 but nothing. still error 7 even doing the procedure above ^^
update 6: Forget everything you read, upthere^^^^ he downloaded the rom for a different phone XD
so anone tested any treble roms from the project forum on our phones with this twrp?
luigge said:
edit2: my friend used the fastboot boot recovery option the recovery booted and asked a password, then he pressed back and the other screen with the swipe button has appeares (allow system modifications) and now what to do? the sdcard folder doesn't have nothing inside, neither the external sd
Click to expand...
Click to collapse
What did he do exactly to avoid the password screen?
so...does this fix some of the issues present in the previous treble recovery? such as the camera not working? flashlight not working? crashes? can i use it as a daily driver?
I tried this ones. Camera working and no crashes, really stable.
[PORTED][semi-GSI][PPR2.181005.003][UNOFFICIAL]P sGSI PR2[A-ONLY]
......
[8.1][sGSI]MIUI10 for Project Treble
......
[9.0] [UNOFFICIAL] [ARM64 A-ONLY] AOSiP Pizza Alpha [EXPERIMENTAL] (Camera crashes but open camera works with videos)
.......
[GSI] OmniROM 8.1 [Unofficial] [ARM64]-[A-Only] [21.10.18]
Those i tested for like 1 hour and in this time everything works good. Iam staying with Omni cuz it feels uber fast and stable.
alright so here's a question: the lineage treble build to flash before the img is down, so where can i find a treble-ised rom to flash before the actual image?
fenerbuuh said:
I tried this ones. Camera working and no crashes, really stable.
[PORTED][semi-GSI][PPR2.181005.003][UNOFFICIAL]P sGSI PR2[A-ONLY]
......
[8.1][sGSI]MIUI10 for Project Treble
......
[9.0] [UNOFFICIAL] [ARM64 A-ONLY] AOSiP Pizza Alpha [EXPERIMENTAL] (Camera crashes but open camera works with videos)
.......
[GSI] OmniROM 8.1 [Unofficial] [ARM64]-[A-Only] [21.10.18]
Those i tested for like 1 hour and in this time everything works good. Iam staying with Omni cuz it feels uber fast and stable.
Click to expand...
Click to collapse
how'd you get the MIUI10 sGSI working on your phone? mine keeps rebooting into twrp
Links for both versions are down. Can you re-upload, please?
actuallynxthing said:
Links for both versions are down. Can you re-upload, please?
Click to expand...
Click to collapse
here
Both of these are not working for me.
All I get is the normal, stock recovery screen.
But yeah, do note that I had installed the 3.3 official which worked for just one boot. After that, I'm getting the stock recovery screen too.
---------- Post added at 04:58 AM ---------- Previous post was at 04:14 AM ----------
eljoantonyn said:
Both of these are not working for me.
All I get is the normal, stock recovery screen.
But yeah, do note that I had installed the 3.3 official which worked for just one boot. After that, I'm getting the stock recovery screen too.
Click to expand...
Click to collapse
Spoke too soon !
Got it working.
Now I need to see why it says "wrong password" while trying to decrypt.
Link fallen
Would you people kindly stop deleting your files from android file host, sick of broken links
Cloudane said:
Would you people kindly stop deleting your files from android file host, sick of broken links
Click to expand...
Click to collapse
I would use the 64bit twrp in the link below
It's not treble but then there's no stable treble roms for this device anyway (which is probably why this twrp is not maintained)
The following 64bit twrp will work with all 64bit custom roms
https://drive.google.com/open?id=1MLlljM7BzMj9Da57LeyBHyg81cHdW1cB
Treble version works good in XT 1670 (2GB 32GB). Some laggy gui, but good. Ty for your hard work!
He.Art said:
Treble version works good in XT 1670 (2GB 32GB). Some laggy gui, but good. Ty for your hard work!
Click to expand...
Click to collapse
If you want an never version use Jarl's TWRP - it works perfectly fine except if you encrypt backups (not the same as backing up encrypted data)
AOSP Q for Suzu/f5121
DISCLAIMER
As always use it at your own risk.
Build it in my spare time to test how the development is proceeding.
Installation instructions
NB: This is a full software update in the sense that will replace everything, recovery included, with aosp version. You need to reflash twrp afterwards.
Clean Install
enter twrp and factory reset
format data partition (only if coming from Pie or below)
flash the rom
flash GApps (optional)
reboot
Updating from previous version
enter TWRP and wipe dalvik/cache
flash ROM
reboot
Alternative way to install
You can also unzip the file and flash via flashboot only what you need:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash userdata userdata.img (only if not updating or coming from Pie or below)
fastboot flash oem xxxx.img
Now you can boot into TWRP and flash gapps and other stuff if you want.
First boot will get stuck on Sony logo for 30/40 seconds, and maybe reboot itself one or two time. Just have patience and everything will be all right
Downloads:
ROM: Latest Build
OEM: Binaries for 4.9 kernel
TWRP: Official TWRP for Suzu
BitGapps: Suggested GApps
What's works:
RIL
Bluetooth
Wifi
Fingerprint
NFC
Camera
USB tethering
Everything else?
What doesn't:
Random reboots (should be solved in latest build)
WiFi Hotspot
Expected the same bugs for Pie ROM since the kernel and binaries are the same, but let me know if you find anything else, will do my best to try to fix it.
Click to expand...
Click to collapse
Changelogr41
Update sources to r41
Overvolt BIG processor to improve stability on higher frequencies (should fix random reboots)
r33
Update sources to r33
r32.v1b
Reverted patch to enable developer option by default
r32.v1
Removed default searchbar from Launcher3
Enabled developer settings by default
Add MicroG support (testing)
r32:
Initial booting build
Click to expand...
Click to collapse
ROM Version: r41
ROM Status: Stable
Created: 2019-12-04
Last Update: 2020-09-20
Thanks to:
@twain55 for the screenshot and testing
@dslul to help in the bug fixing
@ix5 for the initial patches
sonyxperiadev project for providing sources
and last but not least thanks to all that will test this.
Screenshots
flashed with fastboot and stuck at splash screen
Adi_OP said:
flashed with fastboot and stuck at splash screen
Click to expand...
Click to collapse
Still testing and had the same results. Can you try to use the old OEM IMG for pie and report if boots? If not I'll try It during the weekend and let you know.
EDIT
Tried with the pie OEM IMG and doesn't boot. Will rebuild the boot image this weekend and see how to fix
Stuck at splash screen too, using fastboot!
Same here with twrp..try with and w/o gapps,stuck at sony logo.It seem the problem is at boot image
lookmanns14 said:
Same here with twrp..try with and w/o gapps,stuck at sony logo.It seem the problem is at boot image
Click to expand...
Click to collapse
It seems to me too. I'm trying to find where is the issue. Building another image today and tested on my device but didn't worked either.
Does it work for F5122?
Thank you for your try.
Does it work for F5122 as well.
Hope you to fix this rom as a stable.
Good luck
Sorry for the waiting, I've had a lot of work to do lately. Hope to have news/a new build (at least for boot.img) this weekend.
New images are up. I'll try them this afternoon (out now) but if someone would take the leap before me here it is the link
https://mega.nz/#F!vNtx2QZZ!GuV1qwYXjLk3ajd3xoaPPA
Let me know. And thanks again for helping me testing.
Unfortunately, still stuck at Sony logo... I used the latest OEM released on December 10th, SW_binaries_for_Xperia_Android_10.0.7.1_r1_v2C_loire, will try with SW_binaries_for_Xperia_Android_10.0.7.1_r1_v2B_loire, but I doubt this will change anything!
Iscariah said:
Unfortunately, still stuck at Sony logo... I used the latest OEM released on December 10th, SW_binaries_for_Xperia_Android_10.0.7.1_r1_v2C_loire, will try with SW_binaries_for_Xperia_Android_10.0.7.1_r1_v2B_loire, but I doubt this will change anything!
Click to expand...
Click to collapse
I doubt it too sadly but if still stuck I'm at a loss right now. I've to try to see if I can catch some log even if stuck at Sony. Thanks for the report
Any update on this ROM? Is it still in development?
GOrMHATRe said:
Any update on this ROM? Is it still in development?
Click to expand...
Click to collapse
It is. Latest build still doesn't boot. I'm debugging to see if I can find the problem.
Have we wait for next weekends till any further update?
Any good news
[email protected] said:
Any good news
Click to expand...
Click to collapse
Sadly not yet. Having trouble with the building of r15. I think that could be some changes in Q building system because pie build correctly. Hope to fix in this holidays.
ParanoidNemo said:
Sadly not yet. Having trouble with the building of r15. I think that could be some changes in Q building system because pie build correctly. Hope to fix in this holidays.
Click to expand...
Click to collapse
Cheers
Any good news
Are there still this random reboots and homescreen freezes we have with Pie and the 4.9 kernel?
mase76 said:
Are there still this random reboots and homescreen freezes we have with Pie and the 4.9 kernel?
Click to expand...
Click to collapse
Right now the ROM doesn't boot. The issue is upstream and as far as I know this should be fixed when the v3 of the binaries is released (right now we are at v2c). Hopefully the reboot issue will be fixed but we have to wait sadly.
@ParanoidNemo
Which kernel did you use?