About SM-A750GN Bin 1 - Samsung Galaxy A7 (2018) Questions & Answers

I looked at several forums and nobody mentioned about the update of binary 1 for the GN model since I understand should not be placed binary 2, any idea of ​​what happens?
A750GNUBU1ASB2

Related

[Q] Tar header contained an invalid file size?

Ok, so I've a few days reading the gi-normous amount of threads throughout these forums (very insightful by the way) and have yet to find an actual response to the question of what is causing me to get the error message "Tar header contained an invalid file size" when trying to use Heimdall Frontend to "hopefully" reflash my new Samsung Duos S7562. Unfortunately for me, I removed the battery from the phone when it got stuck doing the Samsung software updater and since then has been stuck in bootloop. I can get it into download and Heimdall actually detects it but can load the firmware package. Before you ask , I've downloaded this file multiple times, using different browsers (Safari, Chrome and Firefox) as well as doing so through Linux using VBox, dowload other firmware version and also used different versions of Heimdall (1.3.2, 1.3.1 and 1.3.0). Same issue in all.
OS: Mac Snow Leopard 10.6.8
Phone: Samsung Duos S7562
Firmware: S7562XXALHB_S7562ATOALH1_S7562XXLH5.tar.md5 (contained in a zip file of course)
I've seen where a couple of other people have asked as well but no one has ever received an answer; at least not in the forum for me to see as well. The one topic started on cyogenmod was referred to the XDA Heimdall thread which, although quite LONG and educational, never really addressed the issue to completion.
Anyway, can anyone explain why I'm getting this error and MOST IMPORTANTLY HOW I or anyone else still trying to figure it out can get around it? Would greatly appreciate it from the brain trust we have here. :fingers-crossed:
Any progress on this? I'm receiving the same error and don't know why???

How to update su binary?

Ok, i watched your sign-up video, i read the READ BEFORE POSTING posts, i searched the search, and there is NOT ONE STRAIGHT answer to the most obvious and common issue: su binary update.
There is no official thread titled "su binary" which would be NICE if somebody post a link to the latest version of su binary, tells people which version of Superuser app it is compatible with (i know there's at least 3, CWM, ChainSDD, and Chainfire) I cant even google this binary. I cant even tell if somebody is developing on this binary.
I just don't understand how nobody brought up this issue in any manner. Nobody asked whether the binary code is available in the market, needs to be downloaded from the web and flashed on the phone, etc. In worst case scenario, if su binary is discontinued, then just say "It is no longer supported. Forget about rooting from now on."
I have T-Mobile GS4 (SGH-M919) running Android 4.2 baseband UVUAMDL, i rooted the phone using MotoChopper that gave me Superuser app by CWM.
If you can be ANY help, please reply with some kind of answer that somebody can actually understand. If you have no clue about a single word i just posted, there you go. There is no answer to this "su binary" issue, so forget about rooting and what not. Save your soul from googling 5 hours a day here and web, looking for answers that no one ever asked.
You're very welcome.
Superuser update
Cowls192,
There are a couple of ways to update SU ... I can share at least two ways.
1) If you have experience using Terminal and can get a hold of the updated SU binary, then you can simply copy it to
the appropriate place. I forget whether the location of the original SU binary is under the /sys or /system folder.
2) I'm quoting from DroidXForums here so take it for what it's worth ..
"The new superuser : su v2.3-ef can also be downloaded from the Google market."
I hope that this small bit of information shows you that the answer CAN be found with patience.
Lacking patience ... this IS a great place to find help!
If you found this to be of help, please condiser clicking the THANKS button.
Solidified
Couple things to straighten up here.
Okay, the whole problem with "su binary update failed" is because my phone was NOT rooted. End of that story.
After my phone was rooted successfully, it didn't ask me to install su binary, being out of date, nothing like that.
At this point, i will just assume that whenever app is released/updated, let it be Superuser SuperSU or else, the app itself includes su binary already.
It is still difficult to find answers and solutions for folks who are new to smartphone or Android world...and i mean VERY new, like he/she just got an Android phone for the first time in life today!! A lot of unnecessary questions and replies can be reduced if SOMEBODY creates FAQ or intro to rooting and flashing tips.
Finally, i have T-Mobile GS4 (SGH-M919), and although i read a post saying that su binary is not compatible with SuperSU at this point, (see, it's even harder to search for posts i read recently) after successfully rooting my phone, SuperSU DID NOT ask or even say anything about "su binary" whatsoever, so that made me smile today.
Thanks for those who took few seconds to read my posts, and i really hope somebody is being helped after reading these messages.
cowls192 said:
Couple things to straighten up here.
Okay, the whole problem with "su binary update failed" is because my phone was NOT rooted. End of that story.
After my phone was rooted successfully, it didn't ask me to install su binary, being out of date, nothing like that.
At this point, i will just assume that whenever app is released/updated, let it be Superuser SuperSU or else, the app itself includes su binary already.
It is still difficult to find answers and solutions for folks who are new to smartphone or Android world...and i mean VERY new, like he/she just got an Android phone for the first time in life today!! A lot of unnecessary questions and replies can be reduced if SOMEBODY creates FAQ or intro to rooting and flashing tips.
Finally, i have T-Mobile GS4 (SGH-M919), and although i read a post saying that su binary is not compatible with SuperSU at this point, (see, it's even harder to search for posts i read recently) after successfully rooting my phone, SuperSU DID NOT ask or even say anything about "su binary" whatsoever, so that made me smile today.
Thanks for those who took few seconds to read my posts, and i really hope somebody is being helped after reading these messages.
Click to expand...
Click to collapse
Hi. Im a noob and I am trying to update the su binary. I have a galaxy tab s. I just recently did the super su root but I cant. It installed correctly but the binary won't update. I've searched the Web but no clear answers. I've checked if the root is installed correctly and its not. I don't know where to look for any help is greatly appreciated.
Hello.
Same situation here...
Can't update bynary in SM-T700 - 5.0.2 LP...
me too...
me three.....I can,t update....
I used kingroot app, then superSU-ME, and superSU told me to update the su binary.(Another superuser app told me that my binary still remained "kinguser_su(348)")
Same here, from a nexus 6p
I have a Nexus 6p which I thought was already rooted, but when I used the root checker, it says my phone isn't properly rooted. Also, when I try running Super User it keeps saying that I'm missing the su binary or that it needs to be updated. I have no idea what the next step is now. Can someone help me figure out what I need to do?
Dg60069 said:
Hi. Im a noob and I am trying to update the su binary. I have a galaxy tab s. I just recently did the super su root but I cant. It installed correctly but the binary won't update. I've searched the Web but no clear answers. I've checked if the root is installed correctly and its not. I don't know where to look for any help is greatly appreciated.
Click to expand...
Click to collapse
idioleat said:
me three.....I can,t update....
I used kingroot app, then superSU-ME, and superSU told me to update the su binary.(Another superuser app told me that my binary still remained "kinguser_su(348)")
Click to expand...
Click to collapse
Those still having trouble ensure your device is rooted and also if su still can't install binary try another version some versions have trouble installing binary.
cowls192 said:
Couple things to straighten up here.
Okay, the whole problem with "su binary update failed" is because my phone was NOT rooted. End of that story.
After my phone was rooted successfully, it didn't ask me to install su binary, being out of date, nothing like that.
At this point, i will just assume that whenever app is released/updated, let it be Superuser SuperSU or else, the app itself includes su binary already.
It is still difficult to find answers and solutions for folks who are new to smartphone or Android world...and i mean VERY new, like he/she just got an Android phone for the first time in life today!! A lot of unnecessary questions and replies can be reduced if SOMEBODY creates FAQ or intro to rooting and flashing tips.
Finally, i have T-Mobile GS4 (SGH-M919), and although i read a post saying that su binary is not compatible with SuperSU at this point, (see, it's even harder to search for posts i read recently) after successfully rooting my phone, SuperSU DID NOT ask or even say anything about "su binary" whatsoever, so that made me smile today.
Thanks for those who took few seconds to read my posts, and i really hope somebody is being helped after reading these messages.
Click to expand...
Click to collapse
POST FOR EVERYONE WHO HAS TROUBLE FINDING/UPDATING THE BINARIES:
1. The SuperSU app version number corresponds to the su binary version. To check the version of the su binary go to Settings --> Apps --> SuperSU and look at the version number.
2. SuperSU app will push a notification if the binary needs to be updated.
3. You will also see a popup window once you open the SuperSU app in case there is a new version
4. To be sure you have the latest version you can follow one of the links below which will have the download for the latest recovery-installable zip that will root and install the SU app along with the latest binaries:
Stable (recommended): http://download.chainfire.eu/supersu-stable
Beta: http://download.chainfire.eu/supersu-beta
Latest: http://download.chainfire.eu/supersu
5. There is a thread dedicated to binary update problems. You will have more luck there: http://forum.xda-developers.com/apps/supersu/support-update-failures-t2907365
6. Also remember to visit the official post for any future updates and extra info: http://forum.xda-developers.com/showthread.php?t=1538053
NOTE: In most cases you have to update the SU app to get the latest binary version.
janekmuric said:
POST FOR EVERYONE WHO HAS TROUBLE FINDING/UPDATING THE BINARIES:
...
will have the download for the latest recovery-installable zip that will root and install the SU app along with the latest binaries:
Stable (recommended): http://download.chainfire.eu/supersu-stable
Beta: http://download.chainfire.eu/supersu-beta
Latest: http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
It is exactly how I'm doing and every time get: "binary update unsuccessful"
Sent from my E2303 using Tapatalk
pawwaap said:
It is exactly how I'm doing and every time get: "binary update unsuccessful"
Sent from my E2303 using Tapatalk
Click to expand...
Click to collapse
Then you didn't root properly. Try different root methods or re-root your phone.

[Q] Is Andr.Exploit.Ratc in CF-Auto-Root file malicous?

Greetings!
A couple of months ago, I rooted my Samsung Galaxy Note II (GT-N7105) using the file found at http://autoroot.chainfire.eu/, namely, the file CF-Auto-Root-t0lte-t0ltexx-gtn7105.zip with md5 hash of 196163105a21a52d49546bc63f7f4eec. I also followed these instructions from the respective forum thread.
After this, I left the file on my (Ubuntu) desktop, and only today scanned it with an antivirus scanner (yes, in retrospect, I really should have done this at the time!). It alerted me that the file contains the Andr.Exploit.Ratc exploit. Googling the exploit took me to this page.
Excuse me if the answer should be obvious, but can you tell me whether I should be concerned (ie the file is malicious), or whether the exploit is simply necessary in order to circumvent the manufacturer's security on the phone?
Many thanks in advance

Galaxy S9 SM-G960FXXS6CSH5 Combination File

Hi there,
I own a Samsung Galaxy S9 with model number SM-G960FXXS6CSH5, for private reasons I need the combination file to get the factory binary installed, HOWEVER, there is a HUGE problem. The combination file for it is NOWHERE to be found. Is there anyway I can obtain is? Maybe someone knows where? I would love to hear.
Sincerely,
rudertech

General Watch 4 R895U Nov Update (GVK6)

Full OTA ZIP.....Enjoy Folks....Link is in OP
model_name=SM-R895U
source_ap_file=AP_R895USQU1GVH2_CL24729085_QB54988379_REV00_user_low_ship_MULTI_CERT_meta_WATCH_OS11.tar.md5
source_bl_file=BL_R895USQU1GVH2_CL24729085_QB54988379_REV00_user_low_ship_MULTI_CERT.tar.md5
source_cp_file=CP_R895USQU1GVH2_CP22702263_CL24729085_QB54988379_REV00_user_low_ship_MULTI_CERT.tar.md5
source_csc_file=CSC_OMC_OYM_R895UOYM1GVH2_CL24729085_QB54988379_REV00_user_low_ship_MULTI_CERT.tar.md5
target_ap_file=AP_R895USQU1GVK6_CL25415909_QB59219472_REV00_user_low_ship_MULTI_CERT_meta_WATCH_OS11.tar.md5
target_bl_file=BL_R895USQU1GVK6_CL25415909_QB59219472_REV00_user_low_ship_MULTI_CERT.tar.md5
target_cp_file=CP_R895USQU1GVK6_CP23282039_CL25415909_QB59219472_REV00_user_low_ship_MULTI_CERT.tar.md5
target_csc_file=CSC_OMC_OYM_R895UOYM1GVK6_CL25415909_QB59219472_REV00_user_low_ship_MULTI_CERT.tar.md5
current_version=R895USQU1GVH2/R895UOYM1GVH2/R895USQU1GVH2
updated_version=R895USQU1GVK6/R895UOYM1GVK6/R895USQU1GVK6
dummy_version=R895USQU1GVK6.DM/R895UOYM1GVK6/R895USQU1GVK6
source_os_version=11
target_os_version=11
source_ap_build_date=Wed Aug 10 16:58:38 KST 2022
target_ap_build_date=Mon Nov 14 12:18:13 KST 2022
is_manual_build=N
security_patch_version=2022-11-01
csc_information=OYM(ACG ATT CCT GCF TMB TMK USC VZW XAA)
450.72 MB file on MEGA
mega.nz
How is this going to work with NetOdin?
I don't use NetOdin and i grabbed this from /data/fota inside my watch4. The files are structured the same an a regular OTA and because i haven't checked for myself on this watch....I'm sure this could be side loaded...but if I'm wrong...let me know....I'll add in OP....
Thanks for grabbing it. But in order to flash it will have to be done remotely. Once extracted it doesn't just give AP..CP.. etc. Maybe we need to do this remotely with adb which is possible I think. Just rename it to update.zip . If I am wrong someone correct me.
As soon as I can I will give it a go
Yes sir...
Rename to update.zip (it was that name originally when I pulled it) and adb sideload....i believe.
FOTA Delta aka update.zip NOT for netOdin...
This is only incremental update...
I NEVER found way to use... without rooted Watch...
In theory MAYBE way with rooted Phone...
But I have only tiny brain and limited time...
Best Regards
adfree said:
FOTA Delta aka update.zip NOT for netOdin...
This is only incremental update...
I NEVER found way to use... without rooted Watch...
In theory MAYBE way with rooted Phone...
But I have only tiny brain and limited time...
Best Regards
Click to expand...
Click to collapse
Thanks for the info. I have followed some of the research you have made available in regards to FOTA/DELTA. You're research has given me some clues as to how to handle other Samsung devices firmware. I'm working on repacking an OTA with a modified boot or init_boot (depending on device) and using same certs to try to pass. By I'm having issues repacking it all to generate a payload.bin which in turn when pushed in the right menu...will output update.zip and in same menu....will allow flash.
I tried to repack to bin file then rename to update.zip. Was able to connect to adb remotely. Repackingfile did not work. Adb sees watch but not file
butchieboy said:
I tried to repack to bin file then rename to update.zip. Was able to connect to adb remotely. Repackingfile did not work. Adb sees watch but not file
Click to expand...
Click to collapse
Yeah that's something on the end of my list...to research on and crack. S22U and VZW P7P...are on the top of my list at the moment. But i figure once this come along....Watch 4 should be a walk in the park as it does have fastboot at least already.
Watch 4 and 5 is not easy...
All things are blocked on Watch side...
A
You have no write access to:
Code:
/data/fota
To push update.zip to this folder...
B
You have NO Fastboot... not with USB cable not without...
Stock Bootloader sboot.bin NOT support Fastboot Commands...
C
Sideload also blocked... also with USB cable...
D
FOTA Manager blocked...
Blocked
Blocked
.
.
IMHO 1 chance with rooted Phone and activity blabla...
Or someone is able to find way to push to /data/fota
Plan for 2023...
If I have more time I will add few examples... what I mean...
Best Regards
adfree said:
Watch 4 and 5 is not easy...
All things are blocked on Watch side...
A
You have no write access to:
Code:
/data/fota
To push update.zip to this folder...
B
You have NO Fastboot... not with USB cable not without...
Stock Bootloader sboot.bin NOT support Fastboot Commands...
C
Sideload also blocked... also with USB cable...
D
FOTA Manager blocked...
Blocked
Blocked
.
.
IMHO 1 chance with rooted Phone and activity blabla...
Or someone is able to find way to push to /data/fota
Plan for 2023...
If I have more time I will add few examples... what I mean...
Best Regards
Click to expand...
Click to collapse
Ahh....so let me ask you this...is "system" the owner of /data/fota? I can check but I don't have the device with me right now.
Really good Question... will check...
Yeah 1 idea was to check this Device Owner thingie...
But was too lazy... and not smart enough...
Long time ago tested with Alliance Shield as Knox not fully integrated for this...
Best Regards
Edit 1.
I mean this:
Code:
ADB shell dpm set-device-owner com.rrivenllc.shieldx/.receivers.DeviceAdmin
Taken from Alliance Shield infos...
Device Owner Setup (QR or ADB) - Package Disabler
Need to know if your Samsung Device is secured by Knox? Not all Samsung devices are. Check here to see if Knox is available for your device.
alliancex.org
Maybe something like this possible with Filemanager or...
adfree said:
Really good Question... will check...
Yeah 1 idea was to check this Device Owner thingie...
But was too lazy... and not smart enough...
Long time ago tested with Alliance Shield as Knox not fully integrated for this...
Best Regards
Click to expand...
Click to collapse
How about if i told u.....if "system" was the owner and has rw access....wouldn't it be enough to let's says CP or MV an modified update.zip to the directory /data/fota and see what happems
I can not do something in /data/fota
Not mkdir nor something like this...
I will later check what you asked... now I have to leave...
Best Regards
adfree said:
I can not do something in /data/fota
Not mkdir nor something like this...
I will later check what you asked... now I have to leave...
Best Regards
Click to expand...
Click to collapse
This is for S22...and system is definitely owner that has r/w access...so I'm sure it's the same for Watch 4.
For Watch 4 can't modify signed zip
butchieboy said:
For Watch 4 can't modify signed zip
Click to expand...
Click to collapse
Wdym?
I asked someone about the Ota you posted. They believe since it's an Ota it's signed zip and can't be modified in order to sideload
butchieboy said:
I asked someone about the Ota you posted. They believe since it's an Ota it's signed zip and can't be modified in order to sideload
Click to expand...
Click to collapse
Did u ask Mo? On TG.....and I'm there as well.

Categories

Resources