[RECOVERY][SM-A800F] TeamWin Recovery Project 2.8.7.0 Touch Recovery (2016-01-03) - Galaxy A3, A5, A7, A8, A9 Original Android Develop

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?

Related

[Q] Samsung S3 i9300 Stuck In Bootloop

Hi guys
First some details about the S3:
Model: GT-i9300 (International)
ROM: Custom (Omega v34)
Kernel: SiyaKernel v1.6
FW ver: 4.1.2
The boot loop happened freakishly :silly:. I'm saying it because, yesterday the S3 was working fine. I went to sleep and upon waking up found the S3 in a boot loop with the "Samsung i9300" and the black screen background.
I've been using the custom rom since 1 month without any issue. All I did yesterday (out of the ordinary), was to install a few updates of a few apps like AllShare/Facebook etc.
I'm able to boot into Recovery as well as Download mode. The Download mode shows:
Product Name: GT-I9300
Custom Binary Download: Yes (2 Counts) - I'm guessing this is the binary counter
Current Binary: Custom
System Binary: Custom
Had created a Nandroid backup, so tried restoring from it. Tried advanced restoring with boot first, but the phone restarted midway and then had the boot loop again. After that I tried a normal restore, same thing happened.
I've gone through a few similar posts here, but couldn't find an exact match for mine. Hence, I created this thread. For one, the details in the Download mode are different from others (in some the product or the other was missing, but all are showing in mine). So, I'm guessing my boot partition is still intact (I'm a noob, so, I might be wrong).
What are my options here:
Can I flash a newer ver of custom rom on it?
Will wiping data/factory reset help?
How about Cache Partition/Devlik cache?
Or should I flash a stock rom?
Also, if any other option available and in what order?
Any help will be really appreciated with a big THNX :good::angel:
Just go to download mode, flash a stock rom.. root it again and flash a custom rom (if you like)
Factory resetting wont help, nor wiping caches and dalvik cache
Sent from this girl who's an Android Nerd
saywhatt said:
Just go to download mode, flash a stock rom.. root it again and flash a custom rom (if you like)
Factory resetting wont help, nor wiping caches and dalvik cache
Sent from this girl who's an Android Nerd
Click to expand...
Click to collapse
Thnx for the info :good: . Will give it a try and revert back with the result
Fingers :fingers-crossed:
yup. flashing stock rom with odin and start all over again is ur best chance
I tried installing Stock Rom from the Download mode using ODIN.
Followed this thread http://tutorialfor-android.blogspot.in/2012/08/how-to-flash-firmware-to-galaxy-s3-via.html
Did everything, but ODIN returns as FAIL. What am I doing wrong? Am using ODIN v3.07..
Downloaded the stock rom from SamMobile..
The snapshot:
{
"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"
}
HELP!!!!!!
Use XDA instructions .
http://forum.xda-developers.com/showthread.php?t=1671969
BASICS
http://forum.xda-developers.com/showthread.php?t=1927113
jje
JJEgan said:
Use XDA instructions .
http://forum.xda-developers.com/showthread.php?t=1671969
BASICS
http://forum.xda-developers.com/showthread.php?t=1927113
jje
Click to expand...
Click to collapse
Thnx a lot buddy:good:. Will check and let you know how it went. Maybe post in that same thread for more help
Hey buddy "JJEgan". Tried what you had mentioned. Went to the respective threads and did exactly what was advised in them. But the end result was the same.
This time around I used an older ver of ODIN 3.04. This time the update process moved ahead a bit more. But after a while I got an error msg:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXDLK1_I9300ODDDLI7_I9300DDDLJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I'm not sure what to make out about the issue. At wits end. Could you help me find a solution?
Sudden death, your NAND is dead, replace the motherboard under warranty
anirmj said:
Hey buddy "JJEgan". Tried what you had mentioned. Went to the respective threads and did exactly what was advised in them. But the end result was the same.
This time around I used an older ver of ODIN 3.04. This time the update process moved ahead a bit more. But after a while I got an error msg:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXDLK1_I9300ODDDLI7_I9300DDDLJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I'm not sure what to make out about the issue. At wits end. Could you help me find a solution?
Click to expand...
Click to collapse
Try this ,
1. go to http://checkrom.com download the latest resurrection rom , make sure you have usb drivers installed
2.go into download mode in your phone and flash this rom through odin 3.04 ( administrator mode)
3.once everything is done it should boot into cwm recovery after that wipe data/factory rest and wipe cache partition and then reboot system
4. if everything goes well it should boot into the resurrection rom
Good Luck!
why would resurrection work if the stock rom didn't?
Glebun said:
why would resurrection work if the stock rom didn't?
Click to expand...
Click to collapse
when i had a bootloop .. the stock rom didnt work but when i flashed the resurrection rom it did .. so maybe it may work for him too .
Just wanted to ask. Are there any other options that I might have before taking the mobile to the customer care?
I have read somewhere that a PIT file could resolve issues. Can that work in this scenario? If so, which file to use and what are the perils of using such a file?
Also, buddy "galaxy3lover", when you talk about resurrection rom, can you guide me to the exact FW that you are talking about? The link that you have provided contains a lot of links. Which one should I download from?
http://checkrom.com/download/ scroll down gt - 19300 if you are using the international model ... and then checkrom v6.zip
galaxys3lover: Tried ur resurrection rom, but its a no go.
Other than that also tried the PIT file/re-partitioning method but that too failed.
Searched a lot but couldn't find any other methods for my soft brick. So, is it really game over, even though mine is not a hard brick? Isn't there any other way to fix the issue?
Well if the nand and bootloaders are fine, Odin should be able to just flash it.
Try Kies firmware initialization
xSpeced said:
Well if the nand and bootloaders are fine, Odin should be able to just flash it.
Try Kies firmware initialization
Click to expand...
Click to collapse
Yeah, no harm in trying that as well. Its interesting to note that where ODIN failed can KIES come to the rescue?
Stay tuned for the answer
No even KIES turned out to be a dead end. It begun and stopped with an error. Tried emergency recovery but failed again.
Guess the only option left for me now is take it to the Service Center...
anirmj said:
No even KIES turned out to be a dead end. It begun and stopped with an error. Tried emergency recovery but failed again.
Guess the only option left for me now is take it to the Service Center...
Click to expand...
Click to collapse
You have void warranty so be prepared .
jje
JJEgan said:
You have void warranty so be prepared .
jje
Click to expand...
Click to collapse
Yeah, I always knew about that final outcome

[GT-i9152][KERNEL][LINARO][DEV] Project-Crater [4.2.2+]

{
"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 Donate​You 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

[delos3geur][CWM Advanced Edition] PhilZ Touch (6.43.8)[03.06.2014]

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

HELP

Hi there,
My Samsung galaxy s6 edge doesnt reboot, only show this message "Recovery is not seandoird enforcing" and logo.
What i can do for it?
Any help?
Best regards
{
"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"
}
[/url][/IMG]
[/url][/IMG]
prootc1 said:
Hi there,
My Samsung galaxy s6 edge doesnt reboot, only show this message "Recovery is not seandoird enforcing" and logo.
What i can do for it?
Any help?
Best regards
[/url][/IMG]
[/url][/IMG]
Click to expand...
Click to collapse
Restore using samsung smartswtich or download frimware and flash it using odin
osman34 said:
Restore using samsung smartswtich or download frimware and flash it using odin
Click to expand...
Click to collapse
Hi there,
Thank you for trying to help me. I already try to use ODIN with G925F File ROM, but it happears one error and show Fail in red....
In the screen happears "SW REV Check Fail. Device: 3 Binary: 1"
Mayb e the ROM file is not correct?! Do you have the files?
My phone doesn´t turn on and i can´t put the debug mode activated, i only can put the phone in Download mode, don´t have the recovery mode and if i try to turn on, it stuck on boot logo loop...
Best regards
prootc1 said:
Hi there,
Thank you for trying to help me. I already try to use ODIN with G925F File ROM, but it happears one error and show Fail in red....
In the screen happears "SW REV Check Fail. Device: 3 Binary: 1"
Mayb e the ROM file is not correct?! Do you have the files?
My phone doesn´t turn on and i can´t put the debug mode activated, i only can put the phone in Download mode, don´t have the recovery mode and if i try to turn on, it stuck on boot logo loop...
Best regards
Click to expand...
Click to collapse
What error did you get whilst flashing the firmware?
What region are you in?
G925f is correct?
callumbr1 said:
What error did you get whilst flashing the firmware?
What region are you in?
G925f is correct?
Click to expand...
Click to collapse
Hi there,
I�m in Europe, this phone was given by family and i think this is some France provider...
The model is G925F.
In Download Rom appears:
Product Name: SW-G925F
Current Binary: Custom
System Status: Official
Reactivation Lock: Off
Secure Download: Enable
Knox Warrenty Void: 1 (0X0500)
RP SWREV: B:3 K:2 S:2
When i try using Odin the error is when trying to write in NAND...
"<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G925FXXU1AOCZ_G925FVFG1AOC4_G925FXXU1AOCW_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)"
Best regards
prootc1 said:
Hi there,
I�m in Europe, this phone was given by family and i think this is some France provider...
The model is G925F.
In Download Rom appears:
Product Name: SW-G925F
Current Binary: Custom
System Status: Official
Reactivation Lock: Off
Secure Download: Enable
Knox Warrenty Void: 1 (0X0500)
RP SWREV: B:3 K:2 S:2
Best regards
Click to expand...
Click to collapse
Them errors are normal.
Download and flash this
http://www.sammobile.com/firmwares/download/106963/G925FXXS4DPJ2_G925FBTU4DPH1_BTU/
If you get any errors in odin then copy the log to here.
It seems that the .rar file is corrupt...
I already try to download 2 times...
Need to find other.
regards
prootc1 said:
It seems that the .rar file is corrupt...
I already try to download 2 times...
Need to find other.
regards
Click to expand...
Click to collapse
Try this
https://samsung-firmware.org/download/Galaxy S6 edge/1i77/BTU/G925FXXS4DPJ2/G925FBTU4DPH1/
callumbr1 said:
Try this
https://samsung-firmware.org/download/Galaxy S6 edge/1i77/BTU/G925FXXS4DPJ2/G925FBTU4DPH1/
Click to expand...
Click to collapse
Hi there, thank you for the link.
One question about this, the phone keep rebooting and looping in Samsung logo, i already got remove the "Recovery is not seandoird enforcing" but it can´t turn on because it can´t get charge, if i plug off the usb cable it doesn~t have energie to startup...
Regards
prootc1 said:
Hi there, thank you for the link.
One question about this, the phone keep rebooting and looping in Samsung logo, i already got remove the "Recovery is not seandoird enforcing" but it can´t turn on because it can´t get charge, if i plug off the usb cable it doesn~t have energie to startup...
Regards
Click to expand...
Click to collapse
Remove the battery for 10 minutes. Then but battery back and try again. Make sure it's on the wall main plug and leave it for a few hours
callumbr1 said:
Remove the battery for 10 minutes. Then but battery back and try again. Make sure it's on the wall main plug and leave it for a few hours
Click to expand...
Click to collapse
I already open it and take out the battery and try to charge it, but when i put the cable, the phone reeboot and loop in logo...
I don´t know what we can do for it, i think that is no hope for this...
Regards
prootc1 said:
I already open it and take out the battery and try to charge it, but when i put the cable, the phone reeboot and loop in logo...
I don´t know what we can do for it, i think that is no hope for this...
Regards
Click to expand...
Click to collapse
Happens to mine all the time. Try to flash a different firmware
prootc1 said:
I already open it and take out the battery and try to charge it, but when i put the cable, the phone reeboot and loop in logo...
I don´t know what we can do for it, i think that is no hope for this...
Regards
Click to expand...
Click to collapse
maybe u messed with kernel stuff
easy way to fix download samsung smart switch from here
http://www.samsung.com/us/smart-switch/assets/downloads/Smart_Switch-PC_setup.exe
follow these step
https://www.youtube.com/watch?v=9QhJngOuLQ4
osman34 said:
maybe u messed with kernel stuff
easy way to fix download samsung smart switch from here
http://www.samsung.com/us/smart-switch/assets/downloads/Smart_Switch-PC_setup.exe
follow these step
https://www.youtube.com/watch?v=9QhJngOuLQ4
Click to expand...
Click to collapse
Hi there,
Sorry for late reply...
I did that with Smart Switch successfuly but the phone still rebooting, now the blue LED is on...
It ont start to main screen, still lopping on Samsung logo.
Best regards
prootc1 said:
Hi there,
Sorry for late reply...
I did that with Smart Switch successfuly but the phone still rebooting, now the blue LED is on...
It ont start to main screen, still lopping on Samsung logo.
Best regards
Click to expand...
Click to collapse
if that didnt work then maybe its a hardware issue not Sure tho
did u waited like 10 min for first boot after restoring with smartSwtich???
first boot takes some time
osman34 said:
if that didnt work then maybe its a hardware issue not Sure tho
did u waited like 10 min for first boot after restoring with smartSwtich???
first boot takes some time
Click to expand...
Click to collapse
It reloop alone, i didn´t touch it....
And if i try to hold volume up + home button, the screen go down but the blue LED still turned on...
Regards
prootc1 said:
It reloop alone, i didn´t touch it....
And if i try to hold volume up + home button, the screen go down but the blue LED still turned on...
Regards
Click to expand...
Click to collapse
1 last Shot
Try Flashing Twrp Recovery Using odin
if it works then download a custom rom and flash it using twrp
osman34 said:
1 last Shot
Try Flashing Twrp Recovery Using odin
if it works then download a custom rom and flash it using twrp
Click to expand...
Click to collapse
Already done, now it shows on screen logo "RECOVERY is not seandroid enforcing" and stop the loop issue...
prootc1 said:
Already done, now it shows on screen logo "RECOVERY is not seandroid enforcing" and stop the loop issue...
Click to expand...
Click to collapse
Recovery is not seandroid enforcing shouldnt really matter.
http://download.chainfire.eu/1014/SuperSU/SR5-SuperSU-v2.78-SR5-20161130091551.zip
Flash this supersu through twrp. Recovery message will go
callumbr1 said:
Recovery is not seandroid enforcing shouldnt really matter.
http://download.chainfire.eu/1014/SuperSU/SR5-SuperSU-v2.78-SR5-20161130091551.zip
Flash this supersu through twrp. Recovery message will go
Click to expand...
Click to collapse
I can´t get to TWR, still in logo but not loop and with "Recovery is not seandroid enforcing " with the blue LED on....

[ROM][SM-T510][UNOFFICIAL] LineageOS 16.0 for Galaxy Tab A 10.1 (2019)

{
"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"
}
In the spirit of moving custom ROM development along for the 2019 Galaxy Tab A 10.1 [SM-T510], here's a build of LineageOS 16.0 I just created based on the latest OEM firmware and @AndyYan's latest LineageOS 16.0 GSI. It's very much a work in progress, but it should hopefully help blaze the trail for even better work.
Notes:
The current process requires you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
Custom kernels are specific to OEM releases, and this one is based on the February 2020 Update (T510XXS3ATB4).
Stock recovery will be replaced with my latest TWRP build for the SM-T510..
This is built with root support (enabled in Developer Options). To remove (and enable vendor spoofing), just run "/system/bin/phh-securize.sh" with root access.
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for file-based encryption
Downloads:
lineage-16.0-20200422-UNOFFICIAL-T510XXS3ATB4.tar.md5 (Odin tarball)
lineage-16.0-20200422-UNOFFICIAL-T510XXS3ATB4.zip (TWRP update)
Change Log:
20200422:
New private build of LineageOS GSI with April 2020 Security Patch.
Updated to the OEM T510XXS3ATB4 kernel and vendor partition.
20200405:
Fixed Double Tap to Wake feature (enabled in Phh Treble Settings).
Fixed crash on first two attempts to launch Phh Treble Settings.
New private build of LineageOS GSI with the above fixes (#663 & #1228).
20200324:
New LineageOS GSI build of treble_a64_bvN target with March 2020 Security Update.
Switched to ext2simg for sparse image conversion to improve Odin compatibility and reduce download size.
Updated to T510XXS2ASK5 kernel (November 2019 Update)
20200308:
MTP file transfers should now work even with USB Debugging disabled.
Charging after full shutdown will no longer hang during level-of-charge animation.
Updated to T510XXS2ASK1 kernel (November 2019 Update)
20191019:
Initial release based on lineage-16.0-20191017-UNOFFICIAL-treble_a64_bvN
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install custom ROM tarball (.tar.md5 file) to AP with Odin
If TWRP launches, factory reset with Wipe->Format Data and reboot to system. (Not necessary for incremental upgrades.)
From existing TWRP install:
Hold Power & Vol Up during restart to enter TWRP recovery
Factory reset with Wipe->Format Data. (Not necessary for incremental upgrades.)
Tap Install, select your update (.zip file), and then swipe to install
Reboot to system
Source:
android_device_samsung_gta3xlwifi
treble_build_los
Phh-Treble
treble_build_los
Donations:
Your support is always appreciated! Just click here.
I'm leveraging a ton of work done by @AndyYan and @phhusson for Treble GSIs, so please show them some love here and here!
Leaving my own donation link here if anyone's feeling like it: https://paypal.me/AndyCGYan
One thing to note: LineageOS includes LiveDisplay and Night Light which affect the tone of the display (I like colder displays), but on this device both features lag the UI horribly, probably due to lack of HW acceleration. In this case, try the build.prop trick here to make things perceptibly smooth.
Gapps?
Thanks for this great ROM. I have managed to get it installed on my Black Friday purchased device. However, it would appear no to come with any Google stuff (which I would expect). Normally I would install from OpenGapps but it don't think any of those of suitable. Can anyone advise me what would be suitable. I was looking for the equivalent of the Full package on OpenGapps.
uknetfreak said:
Can anyone advise me what would be suitable. I was looking for the equivalent of the Full package on OpenGapps?.
Click to expand...
Click to collapse
Check out my Nexus Stock ROM.
ahhhh how to install.. im first rooting,....(for galuxy tab a 10.1 rooting tutorial)
#EDIT, wrong ROM
Fairly certain I followed all the steps but it has been a very long time since I've used Odin. Here's the failure log. Any idea where I'm going wrong? Tried running Odin as Administrator, same results. Thanks in advance for any help.
edit: Just tried your Nexus ROM and same results
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1303)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 1487 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> product.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Works like charm! thank you so much for the great work, are you going to release TWRP zip update files for coming version? also any idea why the tablet can't be encrypted? on other note, gsmarena mention that the CPU is Exynos 7904, which is not correct, mine is Exynos 7885! which isn't 64bit as far as I can tell, any idea of there was some versions with Exynos 7904 released?
Magendanz said:
In the spirit of moving custom ROM development along for the 2019 Galaxy Tab A 10.1 [SM-T510], here's a build of LineageOS 16.0 I just created based on the September 2019 Update and @AndyYan's latest LineageOS 16.0 GSI. It's very much a work in progress, but it should hopefully help blaze the trail for even better work.
Notes:
The current process requires you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
Custom kernels are specific to OEM releases, and this one is based on the September 2019 Update (T510XXU2ASI4).
Stock recovery will be replaced with my latest TWRP build for the SM-T510..
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Double-tap to wake
Support for file-based encryption
MTP only works when USB Debugging is enabled
Charging after full shutdown will hang during level-of-charge animation.
Downloads:
lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5
Change Log:
20191019:
Initial release based on lineage-16.0-20191017-UNOFFICIAL-treble_a64_bvN
Instructions:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install custom ROM to AP with Odin
When TWRP launches, wipe data if installing for first time. (Not necessary for incremental upgrades.)
Reboot to system
Source:
android_device_samsung_gta3xlwifi
treble_build_los
Phh-Treble
treble_build_los
Donations:
Your support is always appreciated! Just click here.
I'm leveraging a ton of work done by @AndyYan and @phhusson for Treble GSIs, so please show them some love here and here!
Click to expand...
Click to collapse
---------- Post added at 05:46 PM ---------- Previous post was at 05:44 PM ----------
Had some issues with TWRP, turned out to be a bad cable, was crashing with Odin and heimdall on Linux, but at 85% changed the cable and everything worked fine also not USB-C to USB-C cable in my case it had to be USB-A to USB-C cable.
sc00bied00 said:
Fairly certain I followed all the steps but it has been a very long time since I've used Odin. Here's the failure log. Any idea where I'm going wrong? Tried running Odin as Administrator, same results. Thanks in advance for any help.
edit: Just tried your Nexus ROM and same results
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1303)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 1487 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> product.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Hi
I've flashed this Rom yesterday and it does seem to work relatively well.
There are some issues, though. Mostly stability. Also the Tablet thinks that it is a phone. How do I tell it that it's a Tablet?
So.. where do we go from here? What are the next steps? How is this Rom built? What is the process to build it?
Regards
demoneg said:
Had some issues with TWRP, turned out to be a bad cable, was crashing with Odin and heimdall on Linux, but at 85% changed the cable and everything worked fine also not USB-C to USB-C cable in my case it had to be USB-A to USB-C cable.
Click to expand...
Click to collapse
Just tried with a brand new C -> A cable plugged into a USB 2.0 port and same error. I was originally using the cable that came with the tablet. Not sure what to try next.
sc00bied00 said:
Just tried with a brand new C -> A cable plugged into a USB 2.0 port and same error. I was originally using the cable that came with the tablet. Not sure what to try next.
Click to expand...
Click to collapse
I ran into this (the Odin error on product.img) on the 2 T510's I picked up for my kiddos. Both were initially running the November update, and both upon first boot and setup patched to the December update (this was before I realized there was a Lineage build available).
I was able to successfully flash this build by first downgrading to the September Samsung release (T510XXU2ASI4). I just pushed that through Odin, and immediately entered download mode again post-install, and then install Lineage without an issue. This worked on both of the tablets I have.
I ended up paying for a 3 day pass on samfrew.com because the download speeds are horribly crippled. I would be happy to upload/host the OEM firmware files somewhere to help others if it's not against the rules.
whoiswes said:
I was able to successfully flash this build by first downgrading to the September Samsung release (T510XXU2ASI4). I just pushed that through Odin, and immediately entered download mode again post-install, and then install Lineage without an issue. This worked on both of the tablets I have.
Click to expand...
Click to collapse
OK, that's odd. I bought this one at Costco about a month ago and it shipped with and factory resets to September AS14 :/
I'd already downloaded that rom from samfrew and even tried to flash it after both this and the Nexus ROMS failed. Same results as those two and failed with the same error at product.img
I wonder if I'll need to roll back to an even earlier one, or would loading a ROM earlier than what's in the recovery be a bad thing?
FWIW, in order to unlock the bootloader I went through the "disable auto-updates, auto time adjust, set the time to the past/future manually" trick.
sc00bied00 said:
OK, that's odd. I bought this one at Costco about a month ago and it shipped with and factory resets to September AS14 :/
I'd already downloaded that rom from samfrew and even tried to flash it after both this and the Nexus ROMS failed. Same results as those two and failed with the same error at product.img
I wonder if I'll need to roll back to an even earlier one, or would loading a ROM earlier than what's in the recovery be a bad thing?
FWIW, in order to unlock the bootloader I went through the "disable auto-updates, auto time adjust, set the time to the past/future manually" trick.
Click to expand...
Click to collapse
Odd. I didn't have any issues with applying the ASI4 updates (just the BG, AP, and CSC files) with Odin 3.14.1. I don't think OEM unlocking comes into play for this part.
What "KG STATE" in download mode showing? Prenormal means the knox protection got tripped which is probably (part of?) your issue. I can't say more because I honestly don't know (first Samsung device since the Galaxy Nexus). If you're at ASI4, and download mode shows KG STATE: checking, then you're in the same place I was for a successful flash of Lineage.
Sorry I can't be of more help.
Whelp, thar's mah problem. KG state is Prenormal. No idea how I tripped it but this is my first sammy since the S2. I'll start googling and would welcome any advice on what to do to get to a better state.
Thanks! At least now I know what's borked :/
EDIT [SOLVED]: The clue was in Menendez's reply in post #6 of MossyT's guide where he indicates that wifi should be enabled on the restart immediately after the Volume Up long press to unlock, thus revealing OEM Unlock in developer options. The very first go around, I was able to see the option and must have borked a stdep before or during Odin. All subsequent attempts after doing factory resets, I failed to activate wifi on first boot and went straight to Odin. Until the OEM rom can phone home, KG will remain 'prenormal'. Simply turning wifi on and verifying OEM Unlock in devops, KG changed to 'checking' and the flash went through fine.
Thanks for pointing me in the right direction. My daily drivers are a Moto G5+ and X so I'm a bit rusty at the "samsung way"
Any Chance to get double tap to wake (dt2w) running?
There seems to be a solution:
github.com /phhusson/treble_experimentations/issues/663
dussl said:
Any Chance to get double tap to wake (dt2w) running?
There seems to be a solution:
github.com /phhusson/treble_experimentations/issues/663
Click to expand...
Click to collapse
For now you can flash magisk and run those commands via adb as root on each reboot.
I suppose at some point we either fix the init.rc or phh extends the phh treble app to also run the connection check command.
Is this ROM still being updated or worked on? Just curious been 2 months and nothing from the OP. Thanks.
I am on T510xxu1ASEF. Am I correct to assume I need to upgrade the Firmware to the september release and then install the rom? Or is it as simple as flashing the new rom? I have unlocked the bootloader and have stopped until I find out what to do.
Edited because I'm an idiot and kept saying kernel when obviously the file I downloaded from Samsung was full rom not just kernel.
dcillusions77 said:
Is this ROM still being updated or worked on? Just curious been 2 months and nothing from the OP. Thanks.
Click to expand...
Click to collapse
I'll update it with the latest kernel source when I get back from holiday, but I wouldn't expect much because there haven't been any GSI updates from @AndyYan.
Magendanz said:
I'll update it with the latest kernel source when I get back from holiday, but I wouldn't expect much because there haven't been any GSI updates from @AndyYan.
Click to expand...
Click to collapse
Ok thanks for all your work much appreciated

Categories

Resources