Main thread + features + install instructions + dev support :
http://forum.xda-developers.com/showthread.php?t=2201860
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Update (6.41.8) [27.05.2014] :
General Changelog
Code:
6.43.8 (26.05.2014)
6.43.8
- fix recursive path creation bug for /data/media/0
- f2fs: do not try f2fs recovery.fstab mount options on an ext4 partition
- f2fs: do not redefine default recovery ext4 mount options when migrating from an f2fs recovery.fstab
- f2fs: error message when converting unsupported file systems
- fix Galaxy Mega variant background resolution
6.43.5
- default to /data/media/0 unless we define BOARD_HAS_NO_MULTIUSER_SUPPORT
- use lstat to check if file exists
6.43.4
- fix text print colour could persist after md5 check
6.43.3
- fix f2fs conversion of /data on /data/media devices
- allow ext4 f2fs backup data migration in nandroid
- cleanup code
6.43.0
- nandroid backup: fix 'media' exception:
In CWM, a bug present from the begining was preventing any path/file named media from backup on /data/media devices
This fix will only exclude /data/media path and not other media files/folders
6.42.9
- default again to libtar for backup/restore
6.42.7
default to busybox tar:
- use busybox tar by default as it now supports selinux context backup/restore
- unify libtar and busybox tar options (-p for selinux context)
- remove now deprecated external selinux container code
6.42.5
- f2fs: recreate /etc/fstab after ext4/f2fs conversion for proper use of system mount command
- comment useless dead code
6.42.4
- f2fs: fix nandroid restore to f2fs partitions
- f2fs: support format extra storage to f2fs (vold patch needed)
- f2fs: support switching between f2fs/ext4 (needs f2fs in kernel modules), thanks @KumaJaya
- f2fs: reload volume table after f2fs/ext4 conversion (no reboot needed after conversion)
- f2fs: do not format whole /data when not expected on /data/media devices
- f2fs: allow /data f2fs/ext4 conversion for non data_media devices
Personal Changelog
Code:
- Add Ali.Filth Background
- Fix Philz default Background
- Revert fstab , use sdcard1 for external storage ( fix fstab error for some user )
Screenshoot :
FULL CHANGE LOG : LINK
Special Thanks : @manojkumar8552 for helping and testing
XDA:DevDB Information
CWM 6.0.4.8, Tool/Utility for the Samsung Galaxy Grand Quattro
Contributors
ali.filth, Phil3759
Version Information
Status: Stable
Current Stable Version: 6.43.8
Stable Release Date: 2014-06-03
Created 2014-04-03
Last Updated 2014-06-02
DOWNLOAD LINK : delos3geur
Ali.Filth DOWNLOAD : http://d-h.st/users/ali.filth/?fld_id=35415#files
OR
Philz OFFICIAL DOWNLOAD : http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Reserved
Please give your feedback, working or not, or may have bugs, and after that I will add to the main thread ..
Thanks
Hi, Odin versiyon not working. Eror code is below.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> philz_touch_6.22.1-delos3geur.tar.md5 is invalid.
<OSM> End...
ozankardes said:
Hi, Odin versiyon not working. Eror code is below.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> philz_touch_6.22.1-delos3geur.tar.md5 is invalid.
<OSM> End...
Click to expand...
Click to collapse
can you flash them using cwm or terminal emulator? I need the result works or not
EDIT : if you want install it through terminal emulator,I can give you how to install it
- extract flashable zip and put recovery.img to your internal sdcard
- open terminal emulator
- type :
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
Click to expand...
Click to collapse
- go to recovery
thanks
ali.filth said:
can you flash them using cwm or terminal emulator? I need the result works or not
EDIT : if you want install it through terminal emulator,I can give you how to install it
- extract flashable zip and put recovery.img to your internal sdcard
- open terminal emulator
- type :
- go to recovery
thanks
Click to expand...
Click to collapse
Hey Dude Can U make flashble recovery which can flashed via CWM ??
manojkumar8552 said:
Hey Dude Can U make flashble recovery which can flashed via CWM ??
Click to expand...
Click to collapse
see first post..it's already exist in devdb
ali.filth said:
see first post..it's already exist in devdb
Click to expand...
Click to collapse
sry bro i have not noticed !!!
one question if recovery bricked or curropted than can it affect on booting ???
i m going to flash it so asking u
manojkumar8552 said:
sry bro i have not noticed !!!
one question if recovery bricked or curropted than can it affect on booting ???
i m going to flash it so asking u
Click to expand...
Click to collapse
you can flash original recovery.img through odin if this recovery not working..but it can't effect to booting, as long as you do not go to cwm with commands or third-party applications.but if that working, maybe next time you can go to recovery via commands or third-party apps.
ali.filth said:
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 Link:
FromDevdb (Flash via old CWM recovery)
DevHost (Flash via odin)
XDA:DevDB Information
CWM 6.0.4.7, a Tool/Utility for the Samsung Galaxy Grand Quattro
Contributors
ali.filth, Phil3759
Version Information
Status: Testing
Current Beta Version: 6.22.1
Beta Release Date: 2014-04-04
Created 2014-04-03
Last Updated 2014-04-03
Click to expand...
Click to collapse
DONT TRY FIRST VERSION BETA :;;---
i cant boot my device now.
Download mode is safe so can flash cwm old !!!!!
ARoma Worked Fine !!!
manojkumar8552 said:
DONT TRY FIRST VERSION BETA :;;---
i cant boot my device now.
Download mode is safe so can flash cwm old !!!!!
ARoma Worked Fine !!!
Click to expand...
Click to collapse
Recovery work? Can you tell me why can't boot? You stuck on cwm or?
Please don't quote OP post..
ali.filth said:
Recovery work? Can you tell me why can't boot? You stuck on cwm or?
Please don't quote OP post..
Sent from my GT-I8262 using xda app-developers app
Click to expand...
Click to collapse
ok ok !!!!
samsung logo comes and then booo.,.,.,. phones off !!
even cant see samsung galaxy grand quattro gt-i8558 symbol after samsung logo come !!
flashed via recovery and reboot recovery via old cwm !!!
and got nothing !!!
and nothing is booting right now even rom too !! fix it bro !!
manojkumar8552 said:
ok ok !!!!
samsung logo comes and then booo.,.,.,. phones off !!
even cant see samsung galaxy grand quattro gt-i8558 symbol after samsung logo come !!
flashed via recovery and reboot recovery via old cwm !!!
and got nothing !!!
and nothing is booting right now even rom too !! fix it bro !!
Click to expand...
Click to collapse
Ok..thanks for trying and give result..I'll fix soon..
ali.filth said:
Ok..thanks for trying and give result..I'll fix soon..
Sent from my GT-I8262 using xda app-developers app
Click to expand...
Click to collapse
10x dude for trying to do in phillz recovery i also thinking abt this frm last 2 week but u r doing it !!!
nice work bro keeep it up !!1
Reporting the same for the i8550L device, not working either, can get to the Samsung w/triangle but no further than there
EDIT: Tried CWM version, now going for ODIN one.
EDIT 2: It works!!! @ali.filth you should post the link for ODIN vers. here Dunno if you'll make a CWM-Flashable zip out of it
Wow great.. hope soon will get working philz recovery...
Sent from my GT-I9500
El_Dark said:
Reporting the same for the i8550L device, not working either, can get to the Samsung w/triangle but no further than there
EDIT: Tried CWM version, now going for ODIN one.
EDIT 2: It works!!! @ali.filth you should post the link for ODIN vers. here Dunno if you'll make a CWM-Flashable zip out of it
Click to expand...
Click to collapse
Can you show your ss for that !!
PLEASE TEST BUILD 2 AND GIVE ME RESULT
Thanks
:good:
coolkoushik07 said:
Wow great.. hope soon will get working philz recovery...
Sent from my GT-I9500
Click to expand...
Click to collapse
yaa me toooo
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We are not responsible for bricked devices, dead SD cards, thermonuclear
war, or the current economic crisis caused by you following these directions.
YOU are choosing to make these modificiations, and if you point the finger at
us for messing up your device, we will laugh at you.
In a serious Note,Kernel level flashing and development is pretty serious.Only brave at heart should try flashing this down.Remember to make TWRP/CWM backups and even Keep ODIN and Stock firmwares ready,it can be necessary to flash the device full due to bootloops or any such issues.My Request Please don't try to flash this if you don't know what you are doing or what this is. Neither Samsung Nor Me will take resoonsibility,if anything happens to your device.
Click to expand...
Click to collapse
Link to Discussion Thread--Here
This is the Development thread,have questions? there is the discussion thread linked above.
Sources :-
Sources at https://github.com/RittikBhowmik/Project-Crater-Kernel-GT-i9152
Simply clone all to a directory and run build.
Click to expand...
Click to collapse
Features:-
-Stock Kernel.No OC for now,trying to keep it stable.
-Battery patch for the 15%battery bug.
-SmartAssV2 and Lulzactive Governers Added for performace improvements and enhanced battery life.
-Sio I/O schedulers
Click to expand...
Click to collapse
Changelog:-
14/01/2014-
-Happy New Year and thanks for all the ♥
-Test Zip.
-Revised Sio
-Revised Lulzactive Governor.
-Revised Config thanks to Grarak.
22/12/2013-
-Sio I/O schedulers
21/12/2013-
-smartassV2 and Lulzactive Governers
20/12/2013-
-first release
-Battery script patch to get rid of the below 20% battery samsung bug.
Click to expand...
Click to collapse
Downloads:-
1)http://www.androidfilehost.com/?fid=23311191640113930 [Recovery Flashable .zip] md5: 9c5522e1b2d3f35f165260c0360bbca0
2)http://www.androidfilehost.com/?fid=23269279319198428 [odin .tar] md5: c250d7dd17803aafa32958ea75e6fb77
3)http://www.androidfilehost.com/?fid=23269279319198429 [boot.img] md5: efd58b1cc3dc590e6b09ec9334237cfd
Before downloading recheck the md5 on the sites with the ones here on the post
Stock kernel ---http://www.androidfilehost.com/?fid=23269279319198434 md5: ed9776c5eb79be14b79b2d21ae83738e
Updated with stock boot.tar.md5 so that people dont have to search for the stock-touchwiz-kernel like i had to
Click to expand...
Click to collapse
Click to expand...
Click to collapse
-Sir Silesh or @Silesh.Nair for helping me in all of my steps.
-Willi or @Grarak for the defconfig for crater and uploading the kernel sources to github,and always helping me.
-Rabih or @Somcom3X for Helping and Support (i disturb him a LOT )
-Nebixts for supplying the stock boot.img
- @DooMLoRD for Linaro toolchain.
- Team Rookie for their numorous guides.
- XDA University for few guides and outlines.
Click to expand...
Click to collapse
How to DonateYou can donate to me to keep me motivated and to keep the development alive. College and updating the kernel isnt really an easy task.
To donate,People can donate by clicking on "Donate" button on my signature Or "Donate to me" button below my avatar.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Hi Rittik my friend, longtime I didn't visit forum, sorry for missing your PM. Do you still need them? stock kernel & boot?
No I got the Boot.img thanks to Nebixts
Sent from my GT-I9152 using Tapatalk 4
thanks @Rittik for making kernel for our mega 5.8
i will try it later...for great kernel you created.
New Build up. check OP
Gud work rittik,
My wife has a Mega 5.8, but she won't allow me to root it. Else i could have tried.
the tar.md5 file is invalid on odin 3.07
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> rittik_project-crater-20131222-kernel.tar.md5 is invalid.
<OSM> End..
I tried the boot.img file and archive it into a tar file. ODIN recognied it as a kernel but it will not flash.....
bongski55 said:
the tar.md5 file is invalid on odin 3.07
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> rittik_project-crater-20131222-kernel.tar.md5 is invalid.
<OSM> End..
I tried the boot.img file and archive it into a tar file. ODIN recognied it as a kernel but it will not flash.....
Click to expand...
Click to collapse
how did you archieve into .tar? it wont work that way. thanks for pointing it out.
i have uploaded the .tar check it out. .md5 is useless i got it. Remember never rename the files after downloading,else odin wont flash. rename=break the files.
NEW ERROR------odin downloader has stopped working. md5 hash have been checked.....
Problem signature:
Problem Event Name: BEX
Application Name: Odin3 v3.07.exe
Application Version: 3.0.0.0
Application Timestamp: 4fc5bb56
Fault Module Name: Odin3 v3.07.exe
Fault Module Version: 3.0.0.0
Fault Module Timestamp: 4fc5bb56
Exception Offset: 00043f8b
Exception Code: c0000417
Exception Data: 00000000
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 13321
Additional Information 1: ff1f
Additional Information 2: ff1fc8f2bf7f90852b65f27059da79cf
Additional Information 3: f0ee
Additional Information 4: f0eef1eabe7ce205b69d8bac94fa714a
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
Sorry but this is the first time I encountering all these errors and since I use the Mega5.8 as a daily phone I am afraid to break it.
I will leave the testing to others....
bongski55 said:
the tar.md5 file is invalid on odin 3.07
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> rittik_project-crater-20131222-kernel.tar.md5 is invalid.
<OSM> End..
I tried the boot.img file and archive it into a tar file. ODIN recognied it as a kernel but it will not flash.....
Click to expand...
Click to collapse
bongski55 said:
NEW ERROR------odin downloader has stopped working. md5 hash have been checked.....
Problem signature:
Problem Event Name: BEX
Application Name: Odin3 v3.07.exe
Application Version: 3.0.0.0
Application Timestamp: 4fc5bb56
Fault Module Name: Odin3 v3.07.exe
Fault Module Version: 3.0.0.0
Fault Module Timestamp: 4fc5bb56
Exception Offset: 00043f8b
Exception Code: c0000417
Exception Data: 00000000
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 13321
Additional Information 1: ff1f
Additional Information 2: ff1fc8f2bf7f90852b65f27059da79cf
Additional Information 3: f0ee
Additional Information 4: f0eef1eabe7ce205b69d8bac94fa714a
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
Sorry but this is the first time I encountering all these errors and since I use the Mega5.8 as a daily phone I am afraid to break it.
I will leave the testing to others....
Click to expand...
Click to collapse
its wierd...i am guessing its a sofrware issue..is your odin working fine?. BEX is aknown microsoft application error, take a look here..http://answers.microsoft.com/en-us/...-message/cf5baf73-0877-4070-abfb-a2c3a17a9e10
MD5 error it says. How did you pack the boot img to tar format?
Silesh.Nair said:
MD5 error it says. How did you pack the boot img to tar format?
Click to expand...
Click to collapse
Simple. On terminal-
Code:
$ tar -H ustar rittik_project-crater-20131222-boot.img > rittik_project-crater-20131222-boot.img.tar
md5 error was at the last file which was .tar.md5 to fix it i got rid of the md5 stuffs and uploaded just the .tar file.
Am pretty sure BEX error is a windows issue.
Try this
Code:
tar -H ustar -c rittik_project-crater-20131222-boot.img > rittik_project-crater-20131222-boot.tar
md5sum -t rittik_project-crater-20131222-boot.tar >> rrittik_project-crater-20131222-boot.tar
Silesh.Nair said:
MD5 error it says. How did you pack the boot img to tar format?
Click to expand...
Click to collapse
Silesh.Nair said:
Try this
Code:
tar -H ustar -c rittik_project-crater-20131222-boot.img > rittik_project-crater-20131222-boot.tar
md5sum -t rittik_project-crater-20131222-boot.tar >> rrittik_project-crater-20131222-boot.tar
Click to expand...
Click to collapse
md5 isnt really necessary..for md5 i was using this..
Code:
$ tar -H ustar -c rittik_project-crater-20131222-boot.img > rittik_project-crater-20131222-boot.tar
$ md5sum -t rittik_project-crater-20131222-boot.tar >> rittik_project-crater-20131222-boot.tar
$ mv rittik_project-crater-20131222-boot.tar rittik_project-crater-20131222-boot.tar.md5
this is for making it into .tar.md5
I don't think it is a windows error. I tested it on 3 different laptops all with odin that I have used before-Windows 7 toshiba, Asus windows xp pro and Dell Vista laptops all resulted in odin download error.
bongski55 said:
I don't think it is a windows error. I tested it on 3 different laptops all with odin that I have used before-Windows 7 toshiba, Asus windows xp pro and Dell Vista laptops all resulted in odin download error.
Click to expand...
Click to collapse
All BEX error?. Really wierd. i myself have never seen this..
Take a look here, can you provide a windows screenshot? i will be able to help you better..if the problem is like this..take a look here.http://youtu.be/cEkoK3EHOlU
I consulted a friend of mine,who strangely faced similar issues few days earlier, he said he fixed his issue by using another odin version, I found one including all the odin versions compatible with our device-- Here
Sent from my U8800pro using Tapatalk 4
Hi @Rittik,
I just flash via odin file kernel you are created, but i got some error (screenshoot on attachment file below).
if i flash anyfile nothing error like flash stock rom or cwm or twrp, etc. file format with extension .tar or .md5
please repair ???
nebixts said:
Hi @Rittik,
I just flash via odin file kernel you are created, but i got some error (screenshoot on attachment file below).
if i flash anyfile nothing error like flash stock rom or cwm or twrp, etc. file format with extension .tar or .md5
please repair ???
Click to expand...
Click to collapse
Till these issues gets fixed, i will release test builds on the discussion thread, please test them out, keep a look out at the discussion thread.
Hello guys.
Hei rittik, have you fix it for the kernel you make and we can use it...or try it...
Sent from my GT-I9152 using xda app-developers app
TWRP for Transformer Pad TF201T
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MUST BE ON THE HAIRYBEAN BOOTLOADER ENDING IN 27.1
Changelog 2.7.8.2
- All Upstream changes
- Small changes to the 'new theme' (thx z31s1g)
- Added flash to staging partition, via flash image feature.
Changelog 2.8.7.1
- Removed ability to flash raw .img files....
- gui: keyboard: support longpress label offset, code cleanup ( Thx @_that)
- Added flashable zip
- merged upstream changes
Changelog- 2.8.7.0
- Fully merged 2.8.7.0 source from upstream
- Removed SU from twrp ( Its useless & only takes up extra room)
Changelog- 2.8.6.5
- New theme fully implemented ( Huge thx to @z31s1g ) Still a WIP
- Fix mount -o bind error on recreating /data/media/0 (Huge thx to @xiaolu ) & ( @_that )
- All upstream merges by Team Win
Changelog 2.8.6.1
- GUI: Prevent duplicate page overlays. Thx Matt & _that
- Replace legacy DEVICE_RESOLUTION with the new TW_THEME
- Using new common repo to build recovery.
- Build with grimlocks-5.1 kernel from zombi
- All upstream changes. Thx TeamWin
Changelog- 2.8.6.0
- All upstream changes (They are on git)
- Cleaned up external mount labels
Changelog- 2.8.5.1
- Added dock sd card support to twrp
Changelog- 2.8.5.0
- Added formatting of ext sdcard for ROM2SD & DATA2SD
- Added ability to backup ext sdcard partitions
- Added reboot to recovery & reboot to bootloader from with TWRP
- Fixed error formatting /data to f2fs <- Thx Dees Troy for this fix
- A few upstream changes
Click to expand...
Click to collapse
UPGRADE INSTRUCTIONS----------------------------------------------------------------------------------------------------------------------------------------
- Flashing recovery with fastboot
- Boot tablet into fastboot.
Code:
fastboot -i 0x0B05 flash recovery foo.img
- Replace foo with the file name.
- Once flashed reboot into bootloader.
Code:
fastboot reboot-bootloader
- Enter recovery.
----------------------------------------------------------------------------------------------------------------------------------------
- - Flashabale zip
- Boot into current recovery .....
- Flash the zip it is signed so turn that on ......
- Reboot in to android, fully
- Boot into bootloader, enter newly flashed RCK ....
----------------------------------------------------------------------------------------------------------------------------------------
XDA:DevDB Information
TWRP for TF201T [KANG], Tool/Utility for the Asus Eee Pad Transformer Prime
Contributors
lj50036, hardslog
Source Code: https://github.com/zombi-x-lp
Version Information
Status: Testing
Created 2015-03-06
Last Updated 2015-03-06
DOWNLOADS
OLDER VERSIONS
TWRP [email protected] kang full mirror 1
TWRP [email protected] kang flashable zip by alias4ever full mirror 1
TWRP [email protected] kang full mirror 1
TWRP [email protected] kang flashable zip by alias4ever full mirror 1
TWRP [email protected] kang full mirror 1
TWRP [email protected] kang flashable zip by alias4ever full mirror 1
TWRP [email protected] kang full mirror 1
TWRP [email protected] kang flashable zip by alias4ever full mirror 1
TWRP [email protected] kang full mirror 1
TWRP [email protected] WILL UPLOAD
The more you know
JOIN US ON IRC !!!https://webchat.frt/
Channel: #zombi-x
HOW TO TAKE A RECOVERY LOGYou will be taking this log cause of some kind of error message .....
Once you get and error message, here is how to retrieve a recovery log ....
Using a PC with adb/fastboot installed on it, and if windows the correct drivers. ....
Code:
adb pull /tmp/recovery.log
This log will be in the same directory as the terminal/cmd window is cd'd into ....
Now you have the log, upload it to a pasting site or for download, and give us a link....
lj50036 said:
it may appear to hang on the twrp curtain, let it boot there is nothing wrong here
Click to expand...
Click to collapse
Do you want a flashable zip? Also if I make you a bootloader upgrade with this TWRP built in would you be able to test it as I don't have access to the machine any more?
flumpster said:
Do you want a flashable zip? Also if I make you a bootloader upgrade with this TWRP built in would you be able to test it as I don't have access to the machine any more?
Click to expand...
Click to collapse
I am going to make a flashable zip.... :good:
Yes I can test anything that needs testing for sure .....
Let me know, Thx Josh
lj50036 said:
I am going to make a flashable zip.... :good:
Yes I can test anything that needs testing for sure .....
Let me know, Thx Josh
Click to expand...
Click to collapse
Try this one first mate. I made this the other day for das chaos but he bricked his machine before he could test it.
Link removed for now.
This is the bootloader upgrade and twrp 2.8.4.0 and the partition table setup. If this works then it will be simple for me to make one using your file above.
The best way to test this is to use my downgrade zip to go back to 4.1.1 and then try this to upgrade.
No one else test this please unless you know what you are doing and have nvflash backups. I don't like uploading things I haven't tested myself but have no other option here.
flumpster said:
Try this one first mate. I made this the other day for das chaos but he bricked his machine before he could test it.
https://www.androidfilehost.com/?fid=95916177934537081
This is the bootloader upgrade and twrp 2.8.4.0 and the partition table setup. If this works then it will be simple for me to make one using your file above.
The best way to test this is to use my downgrade zip to go back to 4.1.1 and then try this to upgrade.
No one else test this please unless you know what you are doing and have nvflash backups. I don't like uploading things I haven't tested myself but have no other option here.
Click to expand...
Click to collapse
Got it if you would like to pull the download your call ....
Yes I will go back to stock bootloader then upgrade .....
Will let you know how I get on ....
Thx Josh
flumpster said:
Try this one first mate. I made this the other day for das chaos but he bricked his machine before he could test it.
Link removed for now.
This is the bootloader upgrade and twrp 2.8.4.0 and the partition table setup. If this works then it will be simple for me to make one using your file above.
The best way to test this is to use my downgrade zip to go back to 4.1.1 and then try this to upgrade.
No one else test this please unless you know what you are doing and have nvflash backups. I don't like uploading things I haven't tested myself but have no other option here.
Click to expand...
Click to collapse
zip flashed just fine ....
Rebooted TWRP ......
Blue bar filled to about 85% ......
Tablet did what can only be called a soft reboot ....
As in did not power all the way off, just flashed back to the bootloader screen with 'THIS DEVICE IS UNLOCKED'
But now the blue bar was gone .... It did boot into 2.8.4.0 TWRP and could not mount anything ...
A simple reboot back into TWRP and all is good ....
I am now on your WW bootloader flashed my kang TWRP and installed zombi-pop ....
Life is good ......
Thx Josh
This is fantastic for users of rom/data2SD!
Question about that, however: Will this have an option to automatically flash zips to romSD/dataSD, or will we still have to use the ROM2SD/DATA2SD zips when not flashing something that already has a script for it?
Lavrentsii said:
This is fantastic for users of rom/data2SD!
Question about that, however: Will this have an option to automatically flash zips to romSD/dataSD, or will we still have to use the ROM2SD/DATA2SD zips when not flashing something that already has a script for it?
Click to expand...
Click to collapse
Well if it is built into the ROM as it is for zombi and crombi then ....
There will be no need for the extra zips .... I am still trying to think how we can ....
Support other ROMS easily, but this is going to take some doing ..... Stay turned ..... :good:
Thx Josh
lj50036 said:
zip flashed just fine ....
Rebooted TWRP ......
Blue bar filled to about 85% ......
Tablet did what can only be called a soft reboot ....
As in did not power all the way off, just flashed back to the bootloader screen with 'THIS DEVICE IS UNLOCKED'
But now the blue bar was gone .... It did boot into 2.8.4.0 TWRP and could not mount anything ...
A simple reboot back into TWRP and all is good ....
I am now on your WW bootloader flashed my kang TWRP and installed zombi-pop ....
Life is good ......
Thx Josh
Click to expand...
Click to collapse
Cheers mate. I am in bed at the moment but I will make you another test tomorrow with your recovery added into it for you to try.
lj50036 said:
Well if it is built into the ROM as it is for zombi and crombi then ....
There will be no need for the extra zips .... I am still trying to think how we can ....
Support other ROMS easily, but this is going to take some doing ..... Stay turned ..... :good:
Thx Josh
Click to expand...
Click to collapse
I'm testing DATA2SD on a non-supported ROM (Katkiss LP with Grimlock 300t/201 kernel) and so far with this recovery and the DATA2SD zip it seems to be working fine. This looks pretty promising
lj50036 said:
TWRP [email protected] kang full mirror 1
TWRP [email protected] kang flashable zip by alias4ever full mirror 1
Click to expand...
Click to collapse
I can confirm that this works thanks to Josh's help/instruction on doing it. He is an awesome & great teacher as I learned so much from him. GREAT RECOVERY! Thanks again Josh! :good:
Thanks! I'm testing 2.8.5.1 with ZOMBi-POP
Is there any way to change partition sizes from this recovery? I can't find it
elchevi said:
Thanks! I'm testing 2.8.5.1 with ZOMBi-POP
Is there any way to change partition sizes from this recovery? I can't find it
Click to expand...
Click to collapse
No there is not yet, I am looking into making this happen...
Not sure if it will ever happen as I think I would also have to let users partition the internal storage also ...
I dont know if I am ready for the storm of bricks that may bring ....
Thx Josh
lj50036 said:
No there is not yet, I am looking into making this happen...
Not sure if it will ever happen as I think I would also have to let users partition the internal storage also ...
I dont know if I am ready for the storm of bricks that may bring ....
Thx Josh
Click to expand...
Click to collapse
Maybe choosing among some predefined templates would do the trick for most users. But yes, it can be potentially problematic hehe
Thanks!
Img vs. blob
@lj50036 - Hi Josh, a stupid question - what´s the difference between img and blob file regarding recovery??? Did they flash the same via fastboot? And why did you switched from blob to img? Just asking, to learn something new.
Thx in advance
JuraP said:
@lj50036 - Hi Josh, a stupid question - what´s the difference between img and blob file regarding recovery??? Did they flash the same via fastboot? And why did you switched from blob to img? Just asking, to learn something new.
Thx in advance
Click to expand...
Click to collapse
It is not a .img it is still a blob, but when I build it the process outputs a recovery.img
Even thought its a blob ....
if you would like to learn about blobs check this out by @_that
http://forum.xda-developers.com/showpost.php?p=36925180
Thx Josh
lj50036 said:
It is not a .img it is still a blob, but when I build it the process outputs a recovery.img
Even thought its a blob ....
if you would like to learn about blobs check this out by @_that
http://forum.xda-developers.com/showpost.php?p=36925180
Thx Josh
Click to expand...
Click to collapse
So, the name, including file format, actually doesn´t matter as the output is done right? As the file will be just pushed to recovery partition? Or should it be renamed to foo.blob???
JuraP said:
So, the name, including file format, actually doesn´t matter as the output is done right? As the file will be just pushed to recovery partition? Or should it be renamed to foo.blob???
Click to expand...
Click to collapse
It does not matter you can leave it .img or rename it .blob will not matter ....
Thx Josh
This is Old twrp . New for a800i and a800f can be found here http://forum.xda-developers.com/sam...xy-a800i-f-t3350856/post66169421#post66169421
Code:
[HIDE][CODE]#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. 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 me for messing up your device, I will laugh at you.
*/
Warning
This recovery will TRIP your Knox Counter and your warranty will be void.
This recovery is only for Samsung Galaxy A8 (SM-A800F) Exynos Octa 5430 variant running 5.1.1 (Lollipop).
Tested Safely on following devices.
Samsung Galaxy A8 (SM-A800F)
Why TWRP ? Why not some rooted firmware which keeps warranty safe ?
TWRP is a custom recovery. It has many more functionality than stock recovery! if something goes wrong while flashing something you can always make a backup use this recovery which can be restored when things get messed. if mess is of large extend you can always flash stock firmware.
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Instructions
Follow the instructions carefully.
Step 1 :
Install Samsung Drivers and connect your device to PC. let it install drivers and if its updating let it update. your device drivers should be perfectly installed without a single failure.
Link to Samsung Drivers
Step 2 :
Download Odin 3 you can use 3.07 or 3.09
You can download Odin from here
Download the TWRP Recovery
Step 3:
Turn of your device and go to odin mode [ Vol down + power + home button (all at the same time) ] release it when you see Galaxy A8 Logo
Press vol up to confirm
Step 4:
Now that you are in Odin Mode connect your device via USB cable.
Now open Odin3 3.09 or 3.07 that you have downloaded.
If there is a pop-up like Installing ADB drivers let it get finished it usually updates.
Make sure the COM : xx (xx is usb port number it can be any number so don’t worry about it, just verify COM is lit up)
Now select AP and browse to where you have .tar file and select it
Make Sure only Default Auto Reboot and F. Reset Time is ticked and nothing. verify twice only these 2 are ticked.
Untick Auto Reboot if you are installing recovery for first time!
Click Start and wait for the process to end. DO NOT Interrupt during this time.
Once it says PASS. BOOT INTO RECOVERY USING VOL UP + HOME + POWER BUTTON.
Done.
OR
If you want to flash TWRP without PC (Odin) then download recovery.img and flash it with Flashify.
You won't be able to boot into twrp after install use rebooter app to boot into twrp
Credits:
TWRP Team i.e. @Dees_Troy for his awesome recovery.
@paveenash for testing recovery!
Contributors
androidlover5842, shubham540
Source Code: https://github.com/Grace5921/device_samsung_a8elte/tree/slim-4.4
Kernel Source Code: https://github.com/Grace5921/Kernel_samsung_a8elte
@DigiGoon for his compressed sources
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Based On: Cyanogenmod
Version Information
Status: Stable
Created 2016-01-01
Last Updated 2016-01-03
[/HIDE][/CODE]
md5 error! Binary is invalid.
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> TWRP_2.7.1.0.tar.md5 is invalid.
<OSM> End...
sa3aad said:
md5 error! Binary is invalid.
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> TWRP_2.7.1.0.tar.md5 is invalid.
<OSM> End...
Click to expand...
Click to collapse
remove the .md5 from its end and then try. md5 is not that relevant.
not working. stock on boot
update
after flashing it with flashify it works now but not in full screen mode
sa3aad said:
md5 error! Binary is invalid.
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> TWRP_2.7.1.0.tar.md5 is invalid.
<OSM> End...
Click to expand...
Click to collapse
i have updated recovery to latest version try and tell me
androidlover5842 said:
i have updated recovery to latest version try and tell me
Click to expand...
Click to collapse
I still dont know why even after factory reset still cannot boot if installed via Odin / flashify.
AMDFusion said:
I still dont know why even after factory reset still cannot boot if installed via Odin / flashify.
Click to expand...
Click to collapse
Flash it with the stock firmware
sa3aad said:
Flash it with the stock firmware
Click to expand...
Click to collapse
Nope doesnt work.Still stuck at samsung logo.
AMDFusion said:
Nope doesnt work.Still stuck at samsung logo.
Click to expand...
Click to collapse
it working on my all friends devices try to reflash your device
Regards twrp for a800f
twrp worked for me thanks androidlover5842
Works fine now
sa3aad said:
Works fine now
Click to expand...
Click to collapse
but how it is not booting on all devices how you did that??
each time i want to enter TWRP I flash my phone by using flashify. If you use the normal method (Home+Power+V. up) the phone will stock on boot logo.
sa3aad said:
each time i want to enter TWRP I flash my phone by using flashify. If you use the normal method (Home+Power+V. up) the phone will stock on boot logo.
Click to expand...
Click to collapse
thanks for help
waiting for CM
Links Updated!
Enjoy
flashed it and it worked, at least once. I managed to do nandroid backup and then when I boot the phone, it has issue with Sim Network Signal indicator on the status bar, don't know if it is even related with TWRP, but it just happened after I flashed TWRP. I re try to boot again into TWRP, not working anymore, stuck on Galaxy A8 logo, and I have tried it 8 times until now.
androidlover5842 said:
but how it is not booting on all devices how you did that??
Click to expand...
Click to collapse
First of all need flash spacexkernel has to flash and have to install supersu
After that only twrp have to install then only it works for me.
---------- Post added at 06:45 AM ---------- Previous post was at 06:42 AM ----------
Rei Zazie said:
flashed it and it worked, at least once. I managed to do nandroid backup and then when I boot the phone, it has issue with Sim Network Signal indicator on the status bar, don't know if it is even related with TWRP, but it just happened after I flashed TWRP. I re try to boot again into TWRP, not working anymore, stuck on Galaxy A8 logo, and I have tried it 8 times until now.
Click to expand...
Click to collapse
First of all its not possible to go recovery using by buttons.
U have to install ndr utils or some other apps by using that only u have to go for go recovery mode
thanks it is great job. finally we have TWRP now. but is there anyway to use it without rebooter apps?
Helloo.. what's up guys...
I'm so sorry. Long time no post.. hehe
Today i'm gonna share custom recovery (again) for Samsung Galaxy V SM-G313HZ aka vivalto3gnvdx. This custom recovery called TWRP 3.0.
Quoted from official website :
Screenshots :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What’s new in 3.0.2-0:
Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
Add Greek translation to some builds.
Link : Since our device officially supported by teamwin, then all updates can be downloaded directly to the official website TWRP on the vivalto section here
Old build :
What’s new in 3.0.0-0:
Completely new theme - Much more modern and much nicer looking (by z31s1g)
True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
SuperSU prompt will no longer display if a Marshmallow ROM is installed
Update exfat, exfat fuse, dosfstools (by mdmower)
Update AOSP base to 6.0
A huge laundry list of other minor fixes and tweaks
Link :
Odin version
Flashable version
Changelog :
Fix MTP
Thanks to Allah SWT
Credits :
Team win
Cleverior
corphish (for his clue to fix MTP)
And you...
DO WITH YOUR OWN RISK !!!
IF YOU WANNA RESHARE THIS RECOVERY, PLEASE FOLLOW THIS RULES :
DON'T USE SHORTENER LINK (i.e. adfly, adfoc, etc)
PLEASE PUT THIS POST AS SOURCE. THANKS
Well, the device codename is vivalto3gvn, not vivalto3gvndx. It's product name
BTW, good job bro. Is this support MTP yet?
Older version doesn't
doesntexits said:
Well, the device codename is vivalto3gvn, not vivalto3gvndx. It's product name
BTW, good job bro. Is this support MTP yet?
Older version doesn't
Click to expand...
Click to collapse
Ok.. thanks for correction.
MTP is detected but can not mount. In adb, device is in recovery status. not in device status. is this same with you ?
screenshot of adb is attached.
Hmm... adb shows "device" with me once disable and re-enable MTP again, but MTP doesn't work btw
Have you correct the lun file location? It's in /sys/class/android_usb/f_mass_storage/lun%/file (correct me if i'm wrong). If it's wrong, MTP doesn't work is right
One Q: How did you get TWRP repo source?
doesntexits said:
Hmm... adb shows "device" with me once disable and re-enable MTP again, but MTP doesn't work btw
Have you correct the lun file location? It's in /sys/class/android_usb/f_mass_storage/lun%/file (correct me if i'm wrong). If it's wrong, MTP doesn't work is right
One Q: How did you get TWRP repo source?
Click to expand...
Click to collapse
There is no custom lun in my boardconfig. Maybe i can try to add it later. And the correct lun file location is in /sys/devices/virtual/android_usb/android0/f_mass_storage/lun .
I'm using TWRP source from omni source.
adb shell is working bro. Now your problem is MTP only.
doesntexits said:
adb shell is working bro. Now your problem is MTP only.
Click to expand...
Click to collapse
Ya. MTP still not detected. On my windows 8, there is notif "USB not recognized" when i connecting my device in recovery mode. Even i enable "mount usb storage" button in twrp, the MTP still not detected.
cleverior.ipul said:
Ya. MTP still not detected. On my windows 8, there is notif "USB not recognized" when i connecting my device in recovery mode. Even i enable "mount usb storage" button in twrp, the MTP still not detected.
Click to expand...
Click to collapse
Even with lun file?
Well then, i'm out of ideas. That fix mount storage in CWM but should work with TWRP
doesntexits said:
Even with lun file?
Well then, i'm out of ideas. That fix mount storage in CWM but should work with TWRP
Click to expand...
Click to collapse
Ya, even using custom lun but still not working.
Update with fix MTP
help, im trying to install twrp into galaxy v
but then the recovery never replaced, i've tried cwm and twrp, and when i go into recovery mode it always stock recovery
i've tried looking into the problem in xda and firmware compability is the problem? can someone tell me what's the stock firmware for this one?
Kazryu said:
help, im trying to install twrp into galaxy v
but then the recovery never replaced, i've tried cwm and twrp, and when i go into recovery mode it always stock recovery
i've tried looking into the problem in xda and firmware compability is the problem? can someone tell me what's the stock firmware for this one?
Click to expand...
Click to collapse
which version of firmware do u use ? have u try to install twrp using odin ?
Kazryu said:
help, im trying to install twrp into galaxy v
but then the recovery never replaced, i've tried cwm and twrp, and when i go into recovery mode it always stock recovery
i've tried looking into the problem in xda and firmware compability is the problem? can someone tell me what's the stock firmware for this one?
Click to expand...
Click to collapse
If you install TWRP from Odin, make sure you've choose .tar file as PDA, if not the recovery won't be installed
There's no way to install it through stock recovery, since it always gives "E: Signature verification failed".......
yes i've tried using Odin, even though it was successfull the stock recovery never get replaced by cwm or twrp
my kernel is G313HZDBU0AOD1
Kazryu said:
yes i've tried using Odin, even though it was successfull the stock recovery never get replaced by cwm or twrp
my kernel is G313HZDBU0AOD1
Click to expand...
Click to collapse
When install custom recovery using Odin, don't tick auto reboot. After install successfully, pull your battery out, seriously!
@cleverior.ipul
Can you add this line to TWRP BoardConfig.mk?
We're going to have f2fs support on OC Kernel
Code:
TARGET_USERIMAGES_USE_F2FS := true
doesntexits said:
@cleverior.ipul
Can you add this line to TWRP BoardConfig.mk?
We're going to have f2fs support on OC Kernel
Code:
TARGET_USERIMAGES_USE_F2FS := true
Click to expand...
Click to collapse
I'll add it later. I'm AFK now. but what the effect of that flag for twrp ?
cleverior.ipul said:
I'll add it later. I'm AFK now. but what the effect of that flag for twrp ?
Click to expand...
Click to collapse
It adds f2fs support for TWRP recovery, so we can flash other ROMs with f2fs partition support
I cannot use `adb shell`, can you use it?
---------- Post added at 14:33 ---------- Previous post was at 13:57 ----------
In TWRP 2, I remove all adbd control scripts in init.rc, just leave adbd service def, then in init.recovery.scx15.rc:
Code:
on init
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 18d1
write /sys/class/android_usb/android0/idProduct D002
write /sys/class/android_usb/android0/functions [B]mtp,mass_storage,adb[/B]
# adb won't work in OSX without this
write /sys/class/android_usb/android0/bDeviceClass EF
write /sys/class/android_usb/android0/bDeviceSubClass 02
write /sys/class/android_usb/android0/bDeviceProtocol 01
[B] export PATH /sbin:/system/bin
export LD_LIBRARY_PATH .:/sbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /external_sd
write /sys/class/android_usb/android0/enable 1
start adbd[/B]
So now I can use adb shell and MTP in TWRP 2.
Dude, on the TWRP Official Site I see it is in version 3.0.2-0, so it is safe to install that version and you will update this thread to the new version ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP_3.0.3 for Samsung Galaxy SM-J510FN J5(2016)
Unofficial
Description:
TWRP_3.0.3 :
Based on TWRP for seed -twrp-3.0.3-0-seed 21.8M 2017-01-02 12:09:51
-Added item in the Backup section ->Modem
-Added Mount-firmware
-Added Mount-persist
OTG -Works good,you can install or Restore from external flash drive
-Theme TWRP-Works good theme-twrp-materialised-dark-light-play
Screenshot -Volume -and Power buttons save in externall SD
What should I back up in TWRP?
Bugs:
- PC mounting MTP (but adb should work,Windows 10 cant install MTP driver)
How to install:
Code:
1. Install device usb drivers and Odin
In Phone Developer options - On OEM unlock
2. Power off the device.
3. Boot to download mode (VOLUME DOWN/HOME/POWER).
4. Volume UP once.
5. Open Odin as an administrator, connect the device to a usb port,
and make sure a blue button appears and says "Added" in description on the left.
6. Select AP or PDA for older Odin and search for the downloaded tar file.
7. Uncheck auto reboot from the second tab.
8. Start flash and you should see the succeeded command.
9. Unplug the device and remove the battery.
10. Reboot to TWRP and enjoy! (VOLUME UP/HOME/POWER).
Screenshots:
NEW!!!
TWRP 3.1.0-0 for Samsung Galaxy SM-J510 J5(2016)Old versions:
Description:
TWRP_3.0.2-1 :
-Added item in the Backup section -> System Image
-Added item in the section Install Image -> System Image
TWRP_3.0.2
Fix : No error with third-party reboot,Reboot recovery
Fix :Removed cursor from the screen
Fix :Added in Wipe menu "Android secure''
Fix :OTG -Works good,you can install or Restore from external flash drive
Bugs:
- PC mounting MTP (but adb should work,Windows 10 cant install MTP driver)
View attachment TWRP_3.0.2_J510FN.tar
View attachment TWRP_3.0.2-1_J510FN.tar
Bro , check this:
https://forum.xda-developers.com/galaxy-j5/development/recovery-twrp-3-0-2-samsung-galaxy-t3406889
wolty said:
Bro , check this:
https://forum.xda-developers.com/galaxy-j5/development/recovery-twrp-3-0-2-samsung-galaxy-t3406889
Click to expand...
Click to collapse
Bro ,i I know this with bugs .For my J510FN this TWRP 3.0.2 J510Н -Reboot recovery dont work,cursor in screen,wipe without Android secure.etc
I have repaired these bugs.
Or for you all works ?
https://forum.xda-developers.com/showpost.php?p=69188548&postcount=34
https://forum.xda-developers.com/showpost.php?p=67988962&postcount=14
https://forum.xda-developers.com/showpost.php?p=68115566&postcount=17
https://forum.xda-developers.com/showpost.php?p=68345605&postcount=23
lemlis said:
Bro ,i I know this with bugs .For my J510FN this TWRP 3.0.2 J510Н -Reboot recovery dont work,cursor in screen,wipe without Android secure.etc
I have repaired these bugs.
Or for you all works ?
https://forum.xda-developers.com/showpost.php?p=69188548&postcount=34
https://forum.xda-developers.com/showpost.php?p=67988962&postcount=14
https://forum.xda-developers.com/showpost.php?p=68115566&postcount=17
https://forum.xda-developers.com/showpost.php?p=68345605&postcount=23
Click to expand...
Click to collapse
Recovery is not seandroidenforce
echo -n "SEANDROIDENFORCE" >> recovery.img
?
You change /dev/block/platform/7824900.sdhci/by-name/boot
To
/dev/block/platform/soc.0/7824900.sdhci/by-name/boot
Nice ?
In the other recovery when you rebooted from the recovery while the device is charging. The device enters the charging mode and not the system
The only problem is MTP
When I enter the backup option. Red letters appear saying that could not find something related to the firmware and the efs
Demicro said:
When I enter the backup option. Red letters appear saying
Click to expand...
Click to collapse
Hey bro!For me all works great,you're doing something wrong.There are no red letters.
Only MTP .
lemlis said:
Hey bro!For me all works great,you're doing something wrong.There are no red letters.
Only MTP .
Click to expand...
Click to collapse
In restore
This is normal or I should worry☺
Demicro said:
In restore
This is normal or I should worry
Click to expand...
Click to collapse
"EFS1 and EFS2" your backup was made with old TWRP .
New TWRP dont have partition EFS1 EFS2. Have partition EFS
Make backup with new TWRP- then restore will be without mistakes
TWRP_3.0.2-1 :
-Added item in the Backup section -> System Image
-Added item in the section Install Image -> System Image
I can not fix MTP
There is a problem with this TWRP, after flashing, my computer does not detect anymore my device (odin yes) so I cant open device files from computer...
Sent from my SM-J510FN using XDA Labs
---------- Post added at 11:26 PM ---------- Previous post was at 11:19 PM ----------
lemlis said:
"EFS1 and EFS2" your backup was made with old TWRP .
New TWRP dont have partition EFS1 EFS2. Have partition EFS
Make backup with new TWRP- then restore will be without mistakes
TWRP_3.0.2-1 :
-Added item in the Backup section -> System Image
-Added item in the section Install Image -> System Image
I can not fix MTP
Click to expand...
Click to collapse
With this TWRP my laptop does not detect my device, so I can't transfer files throught usb cable' I use a sd adapter... How to solve this?
Sent from my SM-J510FN using XDA Labs
TheWalkingSans said:
There is a problem with this TWRP, after flashing, my computer does not detect anymore my device (odin yes) so I cant open device files from computer...
Sent from my SM-J510FN using XDA Labs
---------- Post added at 11:26 PM ---------- Previous post was at 11:19 PM ----------
With this TWRP my laptop does not detect my device, so I can't transfer files throught usb cable' I use a sd adapter... How to solve this?
Click to expand...
Click to collapse
It is a known problem, which for now has not been resolved.
Mtp issues in recovery
The phone does not enter the recovery if it is connected to the charger. That is, when a reboot is made from the terminal
Reboot recovery
?
Charge mode
Demicro said:
The phone does not enter the recovery , when a reboot is made from the terminal
Click to expand...
Click to collapse
TWRP_3.0.3
It may be this version will work correctly from the terminal
In this TWRP_3.0.3 from TWRP Terminal reboot recovery comand works good
error unmounting \'/cache\' (no such device)
trying to format a partition to f2fs
to restore to ext4 I have to do it manually because if I try to farmat to ext4 the error appear
mke2fs -t ext4 /dev/block/bootdevice/by-name/cache
your mke2fs.conf file does not define the f2fs filesystem type
formating with mkfs.f2fs === succefull but twrp can't mount f2fs partition
Demicro said:
trying to format a partition to f2fs
to restore to ext4 I have to do it manually because if I try to farmat to ext4 the error appear
mke2fs -t ext4 /dev/block/bootdevice/by-name/cache
your mke2fs.conf file does not define the f2fs filesystem type
Click to expand...
Click to collapse
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.
lemlis said:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.
Click to expand...
Click to collapse
I can not restore the backup because twrp can not mount f2fs
I added f2Fs to the kernel for the future
flag in the anykernel zip
f2fs=true or false
and I will cheery pick f2fs(linux 3.18) from the official twrp source code for J7
Demicro said:
I can not restore the backup because twrp can not mount f2fs
Click to expand...
Click to collapse
Maybe dann need to make TWRP from your new version kernel with added f2Fs to the kernel for the future ?
Sorry,my english is very bad.I do not quite understand what I have to do?
New Recoverys with Aroma support for J5 2016
Here
New Thread Here:
TWRP 3.1.0-0 for Samsung Galaxy SM-J510 J5(2016)
Thread closed on OP's request.
Regards
Vatsal,
Forum Moderator.