Related
Hello,
I've spent the better part of 2 days trying to figure this out. First, I attempted to use ThePagel's ODIN guide to root without tripping the KNOX counter. That wouldn't work, as I constantly received NAND write start/fail messages. Ultimately, I followed the CF Auto Root guide at tomsguide-dot-com/us/samsung-galaxy-s6-guide,review-2856-3.html. I located my device (SM-G920T), and downloaded the appropriate auto root files which included ODIN 3.10.6. I previously downloaded and attempted to use ODIN 3.10.6 and ODIN 3.10.7. The ODIN version that came with the auto-root program had differences in the ODIN.ini file, but when I followed the instructions it flashed a CACHE.img and RECOVERY.img file, showed a green "PASS" sign, and attempted to reboot.
When my phone automatically attempted to reboot, the top of the GS6 logo screen has red letters stating "Recovery is not SEAndroid Enforcing." When I return to the download/ODIN screen I see the following in formation now:
Product Name: SM-G920T
Current Binary: Custom
System Status: Official
FRP Lock: Off
Secure Download: Enabled
KNOX Warrant Void: 1 (it tripped)
RP SWRev: B:3, K:2, S:2
After this failure, I realized my phone was previously Android 5.1.1, and the CF Auto Root files I used are for 5.0.2. Now I'm attempting to use ODIN to restore a stock 5.0.2 as well as a 5.1.1 build, but keep receiving the NAND Write Start/Fail message. After a NAND failure going to Android 5.0.2, I notice my device has a black and red message reading, "SW Rev. Check Fail. Device: 3, Binary: 1." Attempting to go back to Android 5.1.1 (where I started), the error message states "Device 3, Binary 2."
I've attempted to alter the .tar.md5 file and include ONLY the CACHE.img and RECOVERY.img, but when I do, the MD5 value doesn't match, and I am unable to proceed.
I'll continue to read threads and try to figure out how to fix this, but any help would be appreciated. Thank you.
I've tried to create my own tar.md5 files including only the CACHE.img and RECOVERY.img and naming them after the CF-Auto-Root-zerofltetmo-zerofltetmo-smg920t filename, but the MD5 hash/checksum doesn't match. I can't find anywhere to change it, and can't figure out how to make the MD5 check pass. WTF. I don't remember being this stupid the last few times I rooted phones.
**SOLVED**
MBuckley81 said:
I've tried to create my own tar.md5 files including only the CACHE.img and RECOVERY.img and naming them after the CF-Auto-Root-zerofltetmo-zerofltetmo-smg920t filename, but the MD5 hash/checksum doesn't match. I can't find anywhere to change it, and can't figure out how to make the MD5 check pass. WTF. I don't remember being this stupid the last few times I rooted phones.
Click to expand...
Click to collapse
Not sure what exactly changed, but maybe the fact I read this:
forum.xda-developers.com/tmobile-galaxy-s6/help/tried-to-root-5-0-2-5-1-1-guide-t3191903/
I tried doing the same stuff, but it wasn't until I used PeaZip instead of WinRAR or 7Zip. I put the stock 5.1.1 Cache.img and Recovery.img files in my own .tar file (not tar.md5), and was able to use ODIN to push them to the phone. It rebooted, then did the dancing android monkey loading screen. All my other stuff is still on the phone.
MBuckley81 said:
I've tried to create my own tar.md5 files including only the CACHE.img and RECOVERY.img and naming them after the CF-Auto-Root-zerofltetmo-zerofltetmo-smg920t filename, but the MD5 hash/checksum doesn't match. I can't find anywhere to change it, and can't figure out how to make the MD5 check pass. WTF. I don't remember being this stupid the last few times I rooted phones.
Click to expand...
Click to collapse
You don't need to add the .MD5 to the file name..
Stick with .TAR, that will bypass the MD5 Check..
Unofficial release -TWRP recovery for the Galaxy A3 - SM-A310F/FD/Y/M Exynos7580
UPDATE 14/4/2016: TWRP 3.0.2-0 released. TWRP build updated to 3.0.2-1
https://twrp.me/site/update/2016/04/05/twrp-3.0.2-0-released.html
Seandroid warning fix.
New feature available in TWRP 3.0.0-x is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory images from the official firmware can now be flashed with TWRP instead of ODIN. I have extended this feature to include BOOT, RECOVERY, SYSTEM, CACHE, HIDDEN and RADIO(MODEM) partitions.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
NOTE: To flash the modem, first it needs to be renamed to modem.bin.img
F2FS support added.
Internal SUPERSU root option removed. This is to prevent boot loops on 5.11/6.0 devices
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
twrp_3.0.2-1_sm-a310
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
To Root:
Flash the file below with TWRP:
DO NOT LET TWRP ROOT YOUR DEVICE IF IT ASKS. USE ONLY THE FILE BELOW:
http://download.chainfire.eu/969/SuperSU/
DEVICE TREE: soon
Guide
http://www.theandroidsoul.com/galaxy-a3-2016-twrp-recovery-89527/
NOTE: ON SOME ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Credits: Me, Teamwin and my testers - nhthiencp
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
xmodgames
yes rooted. but xmodgames not working on sm-a310f
yareodigiy said:
yes rooted. but xmodgames not working on sm-a310f
Click to expand...
Click to collapse
try use supersu 2.45
chandarakk said:
try use supersu 2.45
Click to expand...
Click to collapse
No, don't it will brick your device.
ashyx said:
No, don't it will brick your device.
Click to expand...
Click to collapse
thanks. do you have a suggestion for xmod work ?
yareodigiy said:
thanks. do you have a suggestion for xmod work ?
Click to expand...
Click to collapse
Sorry I don't really play games, what's the issue?
Removed
alexax66 said:
I added samsung signature into recovery.img and repacked TWRP 3.0.0-0: https://drive.google.com/file/d/0B6vI9V6s4jvbRUtIZDRhb0ZjWlU/view?usp=sharing
Now label "recovery is not seandroid enforcing" will not appear when you start recovery mode.
I think that for those who don't install TWRP yet it is possible will not trip knox after installing this modded TWRP
Test it and report us.
Good luck!
Click to expand...
Click to collapse
Can you please not modify the work of others without getting permission first.
I would have got around to doing this myself, but it wasn't high on my priority list as its just a warning.
It will still trip knox regardless.
ashyx said:
Can you please not modify the work of others without getting permission first.
I would have got around to doing this myself, but it wasn't high on my priority list as its just a warning.
It will still trip knox regardless.
Click to expand...
Click to collapse
ОК!
does anyone tried to install xposed frameworks? if you did, which one should i install?
It's works perfectly, fast and stable so far
Thanks for your hard work and time
I'm using a310f from PLUS GSM in Poland, 16GB.
Custom recovery, root and xposed are working on this phone
Sorry for my English
stuck in download-screen
i'm stuck in the flashing of twrp using your files.
after booting the device into the download-mode, selecting the twrp-tar-file into the AP-slot of odin and pressing "Start!", odin prints:
<ID:0/015> Added!!
<ID:0/015> Odin engine v(ID:3.1100)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> SingleDownload.
<ID:0/015> recovery.img
<ID:0/015> NAND Write Start!!
<ID:0/015> RQT_CLOSE !!
<ID:0/015> RES OK !!
<ID:0/015> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
but the device is still in the download-mode and the small progress-bar stopped a few pixels before the end...
[see the picture]
{
"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"
}
fook42 said:
i'm stuck in the flashing of twrp using your files.
after booting the device into the download-mode, selecting the twrp-tar-file into the AP-slot of odin and pressing "Start!", odin prints:
but the device is still in the download-mode and the small progress-bar stopped a few pixels before the end...
[see the picture]
Click to expand...
Click to collapse
Nothing is stuck, you haven't followed the instructions in the OP.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
Click to expand...
Click to collapse
ashyx said:
Nothing is stuck, you haven't followed the instructions in the OP.
Click to expand...
Click to collapse
you're right ..
i thought there should be more "feedback" on the device that tells me, the flashing was successfully finished.
"after flashing" means, when ODIN states the process is done, it is done.
UPDATE 14/4/2016: TWRP 3.0.2-1 released.
hi guys
thanks for your great rec
i have a problem , in voice calls the other side suddenly dont hear my voice but i do i after few second again the voice comes and go
its very annoying on voice calls for me , is this about radio? if yes where can i found mine? A310F Asia Iran
thanks all waiting for your help
I get a "failed" thread, seems like Odin doesn't connect properly to my phone.
* plug in the phone with usb cable
* downloaded the Samsung USB driver (SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.25.0-retail.exe)
* opened odin
* unchecked auto-reboot
* loaded the twrp file to AP
=> fail
Attached photo:
Any ideas?
ulfmais said:
I get a "failed" thread, seems like Odin doesn't connect properly to my phone.
* plug in the phone with usb cable
* downloaded the Samsung USB driver (SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.25.0-retail.exe)
* opened odin
* unchecked auto-reboot
* loaded the twrp file to AP
=> fail
Attached photo:
Any ideas?
Click to expand...
Click to collapse
You need to put the device in download mode first. Also make sure OEM unlock is enabled and FRP lock is off.
ashyx said:
You need to put the device in download mode first. Also make sure OEM unlock is enabled and FRP lock is off.
Click to expand...
Click to collapse
Cheers @ashyx :good:
Confirmed working like a charm for my new A3 2016 (bought in Norway)
Now I can uninstall all the crap bloatware
(f**k you Samsung for bundling all sorts of crap that I can't remove, even as the owner of the device)
Great work, thanks a lot!
Is the build configuration open source? Is it possible to build it by myself? Can you give me a link to the sources?
Thanks, regards
TWRP 3.3.0 For A3 2017
{
"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"
}
Disclaimer
Code:
/*
* Your warranty will be VOID after installing a custom recovery.
*
* Get notified yourself that 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 recovery
* 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.
*/
This is for A3 2017 only
Download
• TWRP Unoffiicial for a3 2017 : host.mcfy.fr
• TWRP Offiicial for a3 2017 : twrp.me
Instructions
• With Odin : download the .tar file and flash on AP case of Odin
• With Twrp : download the .img file on your phone and flash it throw the older twrp by the image installation menu
Credits and sources
• @TwrpBuilder Our team check our project ! twrp buider
• source : https://github.com/TwrpBuilder/android_device_a3y17lte
Changelog
Code:
- 5th March 2018 : Initial build : TWRP 3.2.1-0
- 10th March 2018 : Fixed ODIN ZIP format
- 26th June 2018 : TWRP is now official
- 8th august : TWRP 3.2.3
- 18th Aprile 2019 : TWRP 3.3.0
what is difference between this version and https://forum.xda-developers.com/sa...elopment/recovery-galaxy-a3-sm-a320f-t3562302 this version of twrp?
EVILWAR83 said:
what is difference between this version and https://forum.xda-developers.com/sa...elopment/recovery-galaxy-a3-sm-a320f-t3562302 this version of twrp?
Click to expand...
Click to collapse
This one is up to dated, and can flash oreo zip, my lineage 15.1 zip's were edited to can be flashed on the older twrp
THANK YOU
McFy, amazing contribution!
i got a new a3 (2017 sm-a320f) and wanted to flash twrp. since there is [no official release][1], i came across your unofficial release, which is the most up to date i could find.
i am on a macos box, still trying to figure out what is the safest and easiest way to flash the bootloader ([odin is only compatible with windows][2]) and whether i should unlock the bootloader... but once i do, i am definitely going to give your build a try and report back.
searching the net i couldn't find how one contributes his code to the twrp upstream. could you please share any details you have on it as i would be happy to see your code changes being pushed to the twrp upstream for others to enjoy it.
Code:
[1]: https://teamw.in/Devices/Samsung/
[2]: https://samsungodin.com/
vwtc6yc8e said:
McFy, amazing contribution!
i got a new a3 (2017 sm-a320f) and wanted to flash twrp. since there is [no official release][1], i came across your unofficial release, which is the most up to date i could find.
i am on a macos box, still trying to figure out what is the safest and easiest way to flash the bootloader ([odin is only compatible with windows][2]) and whether i should unlock the bootloader... but once i do, i am definitely going to give your build a try and report back.
searching the net i couldn't find how one contributes his code to the twrp upstream. could you please share any details you have on it as i would be happy to see your code changes being pushed to the twrp upstream for others to enjoy it.
Click to expand...
Click to collapse
I would at your place look at jodin3 for mac, after having installed it, it will be the same than for the windows users, tick AP box select twrp and hit flash, think to disable OEM on developper settings
McFy said:
I would at your place look at jodin3 for mac, after having installed it, it will be the same than for the windows users, tick AP box select twrp and hit flash, think to disable OEM on developper settings
Click to expand...
Click to collapse
thank you for the reply!
from what i understood, jodin3 has issues flashing "large" files and no one provided any quantification to what is "large" so i thought i better use [heimdall][1].
if you worked with jodin3 and you were able to flash twrp, i will head and do that.
@McFy, could you please relate to my question on how can we merge your code changes into twrp code base?
[1]: https://glassechidna.com.au/heimdall/
vwtc6yc8e said:
thank you for the reply!
from what i understood, jodin3 has issues flashing "large" files and no one provided any quantification to what is "large" so i thought i better use [heimdall][1].
if you worked with jodin3 and you were able to flash twrp, i will head and do that.
@McFy, could you please relate to my question on how can we merge your code changes into twrp code base?
[1]: https://glassechidna.com.au/heimdall/
Click to expand...
Click to collapse
Maybe, but twrp is not a large file, large file would be a rom, what do you mean by merging my change to twrp code base ?, I didn't edited source code twrp, just build it for a3 2017
For me Odin gets stuck at: NAND Write Start!!
Complete log:
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1101)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> recovery_a3y17lte-050318.img
<ID:0/006> NAND Write Start!!
Click to expand...
Click to collapse
When I use my existing TWRP, it doesn't see the image file (.img and .tar, both do not work). What am I doing wrong?
UPDATE:
Oh my bad, I found out in TWRP I have to press "Install image" to actually see the image file.
xtracter360 said:
For me Odin gets stuck at: NAND Write Start!!
Complete log:
When I use my existing TWRP, it doesn't see the image file (.img and .tar, both do not work). What am I doing wrong?
UPDATE:
Oh my bad, I found out in TWRP I have to press "Install image" to actually see the image file.
Click to expand...
Click to collapse
And you have to flash the .tar file in Odin. It seems you tried the .img file.
McFy said:
Maybe, but twrp is not a large file, large file would be a rom
Click to expand...
Click to collapse
in case something goes wrong, i wanted to be able to flash stock recovery.
the stock firmware (rom) that i have in hand, does not contain a recovery image, at least that is what it seems to a samsung device newbie like me. these the files that i do have within the firmware archive:
Code:
AP_A320FXXU2BQI3_CL11883096_QB15086315_REV00_user_low_ship_meta.tar.md5
BL_A320FXXU2BQI3_CL11883096_QB15086315_REV00_user_low_ship.tar.md5
CP_A320FXXU2BQG4_CL589129_QB6977370_SIGNED.tar.md5
CSC_OJV_A320FOJV2BQI3_CL12328718_QB15071626_REV00_user_low_ship.tar.md5
HOME_CSC_OJV_A320FOJV2BQI3_CL12328718_QB15071626_REV00_user_low_ship.tar.md5
so if there is no way to only flash the stock recovery, i am afraid of bricking the phone...
@McFy: i am sure you could shed the light on the matter - what is the best way (if there is such) to flash only the stock recovery?
vwtc6yc8e said:
in case something goes wrong, i wanted to be able to flash stock recovery.
the stock firmware (rom) that i have in hand, does not contain a recovery image, at least that is what it seems to a samsung device newbie like me. these the files that i do have within the firmware archive:
Code:
AP_A320FXXU2BQI3_CL11883096_QB15086315_REV00_user_low_ship_meta.tar.md5
BL_A320FXXU2BQI3_CL11883096_QB15086315_REV00_user_low_ship.tar.md5
CP_A320FXXU2BQG4_CL589129_QB6977370_SIGNED.tar.md5
CSC_OJV_A320FOJV2BQI3_CL12328718_QB15071626_REV00_user_low_ship.tar.md5
HOME_CSC_OJV_A320FOJV2BQI3_CL12328718_QB15071626_REV00_user_low_ship.tar.md5
so if there is no way to only flash the stock recovery, i am afraid of bricking the phone...
@McFy: i am sure you could shed the light on the matter - what is the best way (if there is such) to flash only the stock recovery?
Click to expand...
Click to collapse
https://desktop.firmware.mobi/device:141/firmware:15535 there you can download latest stock recovery
Pat750 said:
And you have to flash the .tar file in Odin. It seems you tried the .img file.
Click to expand...
Click to collapse
Nope I selected the .tar file (btw: you can't pick an .img file in Odin). The log is .img because I think Odin extracted it.
vwtc6yc8e said:
in case something goes wrong, i wanted to be able to flash stock recovery.
the stock firmware (rom) that i have in hand, does not contain a recovery image, at least that is what it seems to a samsung device newbie like me. these the files that i do have within the firmware archive:
Code:
AP_A320FXXU2BQI3_CL11883096_QB15086315_REV00_user_low_ship_meta.tar.md5
BL_A320FXXU2BQI3_CL11883096_QB15086315_REV00_user_low_ship.tar.md5
CP_A320FXXU2BQG4_CL589129_QB6977370_SIGNED.tar.md5
CSC_OJV_A320FOJV2BQI3_CL12328718_QB15071626_REV00_user_low_ship.tar.md5
HOME_CSC_OJV_A320FOJV2BQI3_CL12328718_QB15071626_REV00_user_low_ship.tar.md5
so if there is no way to only flash the stock recovery, i am afraid of bricking the phone...
@McFy: i am sure you could shed the light on the matter - what is the best way (if there is such) to flash only the stock recovery?
Click to expand...
Click to collapse
Yes it's possible. you can extract the recovery.img from AP package and either flash as img in twrp or tar it and use odin. Samsung are pretty safe from hardbrick, you will everytime have access to the download mode
McFy said:
Yes it's possible. you can extract the recovery.img from AP package and either flash as img in twrp or tar it and use odin.
Click to expand...
Click to collapse
the recover.img file is indeed within the ap package.
if flashing twrp fails and i have to flash the stock recovery, clearly i won't be able to use twrp to do so
@McFy: thank you for answering so many questions. deeply appreciated.
McFy said:
tar it and use odin.
Click to expand...
Click to collapse
i see that the files have the tar.md5 file extension and not only tar.
(1) where is the md5 digest?
(2) why is it names like that?
(3) can i just only tar the recovery.img and i am done?
vwtc6yc8e said:
the recover.img file is indeed within the ap package.
if flashing twrp fails and i have to flash the stock recovery, clearly i won't be able to use twrp to do so
@McFy: thank you for answering so many questions. deeply appreciated.
i see that the files have the tar.md5 file extension and not only tar.
(1) where is the md5 digest?
(2) why is it names like that?
(3) can i just only tar the recovery.img and i am done?
Click to expand...
Click to collapse
md5 doesn't matter, you can still extract it as a tar archive, then you will get the recovery.img,
trust me it will not happen
in the developer options i've enabled usb debugging and oem unlock.
i installed samsung usb drivers and adb. using
Code:
adb devices
i was able to detect my device.
using oding v3.13.1 i tried to flash twrp but i got the following error:
Code:
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 19 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> recovery_a3y17lte-050318.img
<ID:0/004> Complete(Write) operation failed.
tried again on a different usb port, and got a different error:
Code:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 19 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> recovery_a3y17lte-050318.img
<ID:0/005> Unassigned file
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
could someone please shed the light on the issue?
this is what i did in order to flash it:
1. flashed twrp 3.1.1-1
2. then using twrp, i flashed the twrp img (not tar) file
now i have twrp ver 3.2.1 running.
i am unsure how the image was compiled even when i looked at the code, but i was unable to read the /data partition which was encrypted.
i had to decrypt it in order to be able to flash magisk.
@McFy:
1. is it possible to check\get the complication flag from adb or twrp itself?
2. can you please also share what are the flags that you used to compile it? (see all my links above)
3. if the TW_INCLUDE_CRYPTO is set to false in your build, could you kindly include it in your next build if you make one?
vwtc6yc8e said:
i am unsure how the image was compiled even when i looked at the code, but i was unable to read the /data partition which was encrypted.
i had to decrypt it in order to be able to flash magisk.
@McFy:
1. is it possible to check\get the complication flag from adb or twrp itself?
2. can you please also share what are the flags that you used to compile it? (see all my links above)
3. if the TW_INCLUDE_CRYPTO is set to false in your build, could you kindly include it in your next build if you make one?
Click to expand...
Click to collapse
1. I think it's impossible
2. You can look at them on sources
3. It's yet set in true
McFy said:
3. It's yet set in true
Click to expand...
Click to collapse
didn't understand you. do you set the value to true when you compiled?
In this tutorial I'd like to show you how to boot GSI on some european firmware, possible all too.
The Goal
I know that there already a topic about GSI, as we know not all GSI ROMs will boot by itself, extra hands would be useful, so please specify in your comments which firmware you boot those roms and how to help the other users for better experience.
How to Flash GSI ROMs
Requirements
A705FNXXU1ASD1 or equivalent. (I'm talking about March build for my case, the actual guide isn't worked for me)
Unloked Bootloader.
TWRP.
DM-Verity Disabler.
Kernel Sepolicy Patcher.
A/B ROMs
Steps:
Flash your GSI.
Flash DM-Verity Disabler.
Flash Kernel Selinux Patcher Follow script wizard I switch to Permissive to boot on ITV region firmware.
Tab Wipes > Factory Reset > YES.
Enjoy.
Booted ROMs on A705FNXXU1ASD1
Descendant (I'll report you).
OmniROM (SystemUI crashed).
How Can I Restore to OneUI?
Assuming that you are bored from GSI ROMs for many reason that you want to back to stock firmware but you don't know how to do, sit and drink something while read.
Requirements:
Odin, I'd reccomend the 3.13 version, click here to get it.
Your last firmware, sammobile is your friend.
Samsung USB drivers from Samsung Developers, must be installed on your system.
Steps:
Reboot to bootloader by pressing Vol Up and Vol Down together to enter "Downloade Mode".
Extract the downloaded firmware from SamMobile.
Open Odin application.
Before doing mistakes like me, give a look into extracted and see how must be configured in Odin (I'm basing my self with Italian firmware ** A705FNXXU1ASD1_A705FNOXM1ASD1_ITV** but should be same for other one).
AP_A705FNXXU1ASD1_CL15723567_QB22975198_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar > must goes in AP.
BL_A705FNXXU1ASD1_CL15723567_QB22975198_REV00_user_low_ship_MULTI_CERT.tar > must goes in BL .
CP_A705FNXXU1ASD2_CP12349781_CL15723567_QB23029337_REV00_user_low_ship_MULTI_CERT.tar > must goes in CP.
CSC_OMC_OXM_A705FNOXM1ASD1_CL15723567_QB22975198_REV00_user_low_ship_MULTI_CERT.tar > must goes in CSC.
HOME_CSC_OMC_OXM_A705FNOXM1ASD1_CL15723567_QB22975198_REV00_user_low_ship_MULTI_CERT.tar >must goes in USERDATA
Now click on Options tab and select Auto Reboot and F.Reset Time.
Once you done with selecting files and options, it's time for flashing so make sure to see the COM port "CONNETTED" in Odin application, all you have to do it is click on "Start"
Is it Possible to Re-Flash OneUI without losing Data of GSI?
Yes and No, all you can do before flashing OneUI is uncheck "F.Reset Time" to avoid factory reset and prolly you'll get your old data from GSI without need to restore again each time.
Is it Possible to fix Knox?
No and NO.
The only "solution" to fix it, by sending a "dead" phone to replace the old motherboard. xD
Is it possible to Relock Bootloader?
Yes, let's see how.
Requirements:
Unlocked bootloader.
Stock recovery must be installed.
Steps:
Reboot the phone by keeping 2 Volume buttons pressed.
Long press with Volume Up in warning screen.
Press Volume Up to re-lock the bootloader, keep in mind will run factory reset automatically each time doing this step.
Reboot to OneUI > Conenct to Wifi and now you should see "OEM Unlock" in developers options.
reserved
Please do not quote the main op.
Great, you figured out what's different on FN :laugh:
I'll link this in my GSI list post :good:
FriendlyNeighborhoodShane said:
Great, you figured out what's different on FN :laugh:
I'll link this in my GSI list post :good:
Click to expand...
Click to collapse
sure bro I'll add credits once done
theses roms wont boot:
FW used : https://www.sammobile.com/samsung/galaxy-a70/firmware/SM-A705FN/BTU/download/A705FNXXU3ASG6/284152/
United Kingdom 2019-08-07 A705FNXXU3ASG6 A705FNOXM3ASG6 July patch
Pixel experience by EnesSastim
Pixel Experience by NFound
Resurrection remix 7.02 by peaktogoo
Aosp extended 6.6 by EnesSastim
LLuviaOS by NFound
AOSP Extended by AryanPatidar
AOSP Extended by TingyiChen
Android P Pixel GSI from erfanoabdi
Android Q GSI beta build 6 from erfanoabdi
ViperOS by peaktogoo
OctopusOS by Deepflex
UltraSuccROM by DanielTheCzlek
FlokoROM by Andro Plus
AquariOS bya1Pha
BK said:
theses roms wont boot:
FW used : https://www.sammobile.com/samsung/galaxy-a70/firmware/SM-A705FN/BTU/download/A705FNXXU3ASG6/284152/
United Kingdom 2019-08-07 A705FNXXU3ASG6 A705FNOXM3ASG6 July patch
Pixel experience by EnesSastim
Pixel Experience by NFound
Resurrection remix 7.02 by peaktogoo
Aosp extended 6.6 by EnesSastim
LLuviaOS by NFound
AOSP Extended by AryanPatidar
AOSP Extended by TingyiChen
Android P Pixel GSI from erfanoabdi
Android Q GSI beta build 6 from erfanoabdi
ViperOS by peaktogoo
OctopusOS by Deepflex
UltraSuccROM by DanielTheCzlek
FlokoROM by Andro Plus
AquariOS bya1Pha
Click to expand...
Click to collapse
On P8 Lite 2017 have same issue, not all roms booted as should.
and we fix in some roms by replace a selinux files by copy in /system/etc/selinux/mapping I'm wonder if will work here too. check my attached files.
haky 86 said:
On P8 Lite 2017 have same issue, not all roms booted as should.
and we fix in some roms by replace a selinux files by copy in /system/etc/selinux/mapping I'm wonder if will work here too. check my attached files.
Click to expand...
Click to collapse
ill check that right now since im in download mode , thanks alien god sended by area 51
---------- Post added at 21:35 ---------- Previous post was at 21:27 ----------
do you know a way to bypass samsunge firmware verification? my phone been shipped with SM-705FN Europe but i want to flash SM-A705GM India and it wont let me
<ID:0/005> 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/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 114 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> abl.elf
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
BK said:
ill check that right now since im in download mode , thanks alien god sended by area 51
---------- Post added at 21:35 ---------- Previous post was at 21:27 ----------
do you know a way to bypass samsunge firmware verification? my phone been shipped with SM-705FN Europe but i want to flash SM-A705GM India and it wont let me
<ID:0/005> 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/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 114 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> abl.elf
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Hmm, check just auto reboot and f.reset time then see.
haky 86 said:
Hmm, check just auto reboot and f.reset time then see.
Click to expand...
Click to collapse
i seen ur policy.tar , do i have to flash in odin?
---------- Post added at 22:08 ---------- Previous post was at 22:03 ----------
haky 86 said:
Hmm, check just auto reboot and f.reset time then see.
Click to expand...
Click to collapse
auto reboot n f.reset were checked
BK said:
i seen ur policy.tar , do i have to flash in odin?
---------- Post added at 22:08 ---------- Previous post was at 22:03 ----------
auto reboot n f.reset were checked
Click to expand...
Click to collapse
no bro, extract that files then boot to twrp > Mount > /system
and push that files to /system/etc/selinux/mapping via adb
haky 86 said:
no bro, extract that files then boot to twrp > Mount > /system
and push that files to /system/etc/selinux/mapping via adb
Click to expand...
Click to collapse
i almost never use adb whats the command? adb sideload policy.tar /system/etc/selinux/mapping ?
BK said:
i almost never use adb whats the command? adb sideload policy.tar /system/etc/selinux/mapping ?
Click to expand...
Click to collapse
the command are right, but extract policy.tar with 7zip and push them one by one, just open the archive and will see 3 files.
edi: run this
adb push 26.0.cil /system/etc/selinux/mapping
adb push 27.0.cil /system/etc/selinux/mapping
adb push 28.0.cil /system/etc/selinux/mapping
haky 86 said:
the command are right, but extract policy.tar with 7zip and push them one by one, just open the archive and will see 3 files.
edi: run this
adb push 26.0.cil /system/etc/selinux/mapping
adb push 27.0.cil /system/etc/selinux/mapping
adb push 28.0.cil /system/etc/selinux/mapping
Click to expand...
Click to collapse
always show : error: closed
edit 1 : i think it worked but rebooted and now bootloop
BK said:
always show : error: closed
edit 1 : i think it worked but rebooted and now bootloop
Click to expand...
Click to collapse
thanks for testing.
Kernel sepolicy patcher causes Error 1 while flashing: cannot mount /system. I can mount system partition in twrp but the zip always fail to flash.
My List of GSIs
Pi GSIs
1. AOSP 9 v119
https://github.com/phhusson/treble_e...tions/releases
2. Floko
https://drive.google.com/drive/mobil...VVXXJ5-MUVAsSq
3. Arrow
https://sourceforge.net/projects/arr...arrow-9.x/GSI/
4. Havoc
https://forum.xda-developers.com/pro...oc-os-t3930030
5. Bootleggers
https://androidfilehost.com/?w=files...&sort_dir=DESC
6. Lineage ( use instructions on link)
https://www.android-hilfe.de/forum/s...an.928318.html
7. EvolutionX
https://sourceforge.net/projects/evolution-x/files/GSI/
8. MSM-Xtended (my favourite)
https://mega.nz/#!U1EiWC7R!BMPOu08zw...ROSyuMIRtD0VRA
Q GSIs
1. AOSP 10
https://github.com/phhusson/treble_e...tions/releases
2. Pixel Experience, EvolutionX & Havoc
https://forum.xda-developers.com/pro...-gsis-t4003457
3. Crdroid
https://sourceforge.net/projects/amb...mg.xz/download
Custom Android 10 boot screens
https://forum.xda-developers.com/gal...0-gsi-t4019693
List of all GSIs
https://github.com/phhusson/treble_e...(GSI)-list
Hello all
It was a long time since my last post, I manage to boot my own LineageOS 17.1 for OneUI 2.0 firmware. the idea here is doing a DSSI (Device Specific System Image), only a system image based on stock kernel, product and vendor. I'll do a foss vendor once everything got fixed. so if you are interesting about it just tag me to upload a testing rom.
P.S: it's a from scratch project, has nothing to do with the actual works
Ни одна из прошивок GSI на Samsung A705FN не видит компьютер через USB..как это исправить??
None of the GSI firmware on the Samsung A705FN does not see the computer through the USB..How to fix it??
Hello Guyz any solution for rooting our beloved A600FN with android 10 ?
Thx in advance
All our hope are on you @corsicanu
If you want root on stock rom and don't want custom rom you can use magisk's patching firmware feature.
Zeflay said:
If you want root on stock rom and don't want custom rom you can use magisk's patching firmware feature.
Click to expand...
Click to collapse
Without custom recovery?
Show me how you do that, dude!!!
For me we need twrp for a600fn on Android 10... Then we can root...
Envoyé de mon POCO F1 en utilisant Tapatalk
https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
I found it!!! And it's so simple....
Basically, it's without custom recovery
0/ Unlock your Bootloader
1/ Download your stock rom android 10 from Sammobile or Frija (On your PC)
2/ Transfer the AP file in your phone
3/ Patch it with Magisk manager
4/ Copy back the pached file (tar extension) to your PC
5/ Reboot in Download mode
6/ Flash your phone via Odin, replacing the original AP file by the patched one
7/ reboot to stock recovery and factory format
8/ reboot system and enjoy your rooted Samsung phone!!!
Read carefully
Mastakony said:
https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
I found it!!! And it's so simple....
Basically, it's without custom recovery
0/ Unlock your Bootloader
1/ Download your stock rom android 10 from Sammobile or Frija (On your PC)
2/ Transfer the AP file in your phone
3/ Patch it with Magisk manager
4/ Copy back the pached file (tar extension) to your PC
5/ Reboot in Download mode
6/ Flash your phone via Odin, replacing the original AP file by the patched one
7/ reboot to stock recovery and factory format
8/ reboot system and enjoy your rooted Samsung phone!!!
Read carefully
Click to expand...
Click to collapse
Yes, but don't forget you didn't flash RMM bypass. So you can easily get KG prenormal state.
Zeflay said:
Yes, but don't forget you didn't flash RMM bypass. So you can easily get KG prenormal state.
Click to expand...
Click to collapse
I'm ok with that.
I just wanted to Root my device.
I don't want to flash custom binaries so it's cool...
No enough dev on this phone so no custom roms for me...
Root is enough
Mastakony said:
I'm ok with that.
I just wanted to Root my device.
I don't want to flash custom binaries so it's cool...
No enough dev on this phone so no custom roms for me...
Root is enough
Click to expand...
Click to collapse
Is gaming still smooth on your device on android 10 just like android 9?
Curcepogi said:
Is gaming still smooth on your device on android 10 just like android 9?
Click to expand...
Click to collapse
I don't know, dude.
This phone is really not designed for gaming (IMO)
I use it as my secondary phone...
My pocoF1 for gaming
Rooting ok but?
I rooting with metod of the 2 or 3 post is ok but I want copy frida in system/bin but is not possible
Is only read
With root explorer (superuser) change in r/w
launch command copy
And the phone reboot
Why?
Help and sorry for my English ?
Where can we get this file (Download your stock rom android 10 from Sammobile or Frija)
Sammobile
---------- Post added at 10:58 PM ---------- Previous post was at 10:32 PM ----------
The last stock rom
Mastakony said:
https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
I found it!!! And it's so simple....
Basically, it's without custom recovery
0/ Unlock your Bootloader
1/ Download your stock rom android 10 from Sammobile or Frija (On your PC)
2/ Transfer the AP file in your phone
3/ Patch it with Magisk manager
4/ Copy back the pached file (tar extension) to your PC
5/ Reboot in Download mode
6/ Flash your phone via Odin, replacing the original AP file by the patched one
7/ reboot to stock recovery and factory format
8/ reboot system and enjoy your rooted Samsung phone!!!
Read carefully
Click to expand...
Click to collapse
Hi, can you still use samsung account, and fingerprint payment features ?
Thanks in advance.
Samsung account works
Fingerprint too
Don't use paiement features but it should work it you use the good tricks (when rooted)
Envoyé de mon POCO F1 en utilisant Tapatalk
Thanks so much.
It works fine on A605FN too.
Hello, i have a A600FN with Android 10.
First i make OEM-Unlock, so it make a Factory Reset.
I Install the new Firmware from SamMobile with Odin.
After this, i install MagiskManager and Patch the AP from the Firmware.
So i try install the Magisk-Patched.Tar but it failed in Odin
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 4760 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> system.img
<ID:0/005> vendor.img
<ID:0/005> userdata.img
<ID:0/005> boot.img
<ID:0/005> RQT_CLOSE !!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I test this with the Boot.img from the AP to, same Error.
Right the now the OEM-Unlock Option is disappeared too. (Yes WiFi is on and i test it to with the 8 days back)
I root lot of more Devices. But this one trigger me.
Mastakony said:
https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
I found it!!! And it's so simple....
Basically, it's without custom recovery
0/ Unlock your Bootloader
1/ Download your stock rom android 10 from Sammobile or Frija (On your PC)
2/ Transfer the AP file in your phone
3/ Patch it with Magisk manager
4/ Copy back the pached file (tar extension) to your PC
5/ Reboot in Download mode
6/ Flash your phone via Odin, replacing the original AP file by the patched one
7/ reboot to stock recovery and factory format
8/ reboot system and enjoy your rooted Samsung phone!!!
Read carefully
Click to expand...
Click to collapse
Confirmed working Magisk on Android 10 using this method on SM-A605G - A605GDXU6CTC9 XID. Thanks! :good:
Hey! Thanks so much for sharing this info with all the XDA community, all those of us who own an a600fn will be forever grateful, me in front line haha I rooted my phone with this method, but I immediately had this problem:
Booted to the system, everything working just fine, root apps working great, but I installed the BusyBox magisk module and it all went down hill. The phone would not boot properly, only on safe mode, and I had to reinstall the firmware with the root AP file all over again. I installed another magisk module, but it was the same thing: It went on a bootloop, or just wouldn't boot at all, only on safe mode, so I've concluded that is not possible to use them on this phone by rooting this way, meaning no magisk modules for me, since I've already upgraded to android 10 and I can't go back to Pie's bootloader or so I've heard. Im i being overly dramatic? Is there a solution for this? Is it because we can't flash the RMM state file without TWRP wich is not available for this phone with this android version?
btw I'm like super fan of all of you who work so hard in pro of making our phones better, there's no enough (insert anything good or that you just love in here) in the world to thank you all. Have a great day!
I hope for your answer
I'll write here because I didn't want to open e new thread.
I wanted to root the Galaxy A+ for my girl. I activated OEM unlock and did the following reset. Then I flashed twrp via Odin and the suggested files in addition. Unfortunately I ran into a bootloop, showing the black android screen with yellow writing in the upper left corner "warranty bit: kernel". The screen appears, gets black, reapperars and so on. Next I tried to flash the latest firmware via odin without success, read a lot about the odin flashing procedure. I think I might use the csc file without the "home" as fourth file, besides the usual bl, ap and cp. But when I choose this csc file, odin gets force closed. I can only use csc_home. The flashing process is very fast and says "success", but leads me into bootloop again. I tried booting into twrp after flashing and wiping cache and other things (lot of attempts) with same result.
If anybody has an idea I'll be very thankful.
no_means_no said:
I'll write here because I didn't want to open e new thread.
I wanted to root the Galaxy A+ for my girl. I activated OEM unlock and did the following reset. Then I flashed twrp via Odin and the suggested files in addition. Unfortunately I ran into a bootloop, showing the black android screen with yellow writing in the upper left corner "warranty bit: kernel". The screen appears, gets black, reapperars and so on. Next I tried to flash the latest firmware via odin without success, read a lot about the odin flashing procedure. I think I might use the csc file without the "home" as fourth file, besides the usual bl, ap and cp. But when I choose this csc file, odin gets force closed. I can only use csc_home. The flashing process is very fast and says "success", but leads me into bootloop again. I tried booting into twrp after flashing and wiping cache and other things (lot of attempts) with same result.
If anybody has an idea I'll be very thankful.
Click to expand...
Click to collapse
Dude, is TWRP. Uninstall it. I ran into the same problem. That recovery just isn't compatible with the bootloader of android 10 for this phone, and it will never boot if it's on your A6. It's all Samsung's fault, hahahaha
Hope I helped you!
no_means_no said:
I'll write here because I didn't want to open e new thread.
I wanted to root the Galaxy A+ for my girl. I activated OEM unlock and did the following reset. Then I flashed twrp via Odin and the suggested files in addition. Unfortunately I ran into a bootloop, showing the black android screen with yellow writing in the upper left corner "warranty bit: kernel". The screen appears, gets black, reapperars and so on. Next I tried to flash the latest firmware via odin without success, read a lot about the odin flashing procedure. I think I might use the csc file without the "home" as fourth file, besides the usual bl, ap and cp. But when I choose this csc file, odin gets force closed. I can only use csc_home. The flashing process is very fast and says "success", but leads me into bootloop again. I tried booting into twrp after flashing and wiping cache and other things (lot of attempts) with same result.
If anybody has an idea I'll be very thankful.
Click to expand...
Click to collapse
You can have root without recovery tho