well recently i tried to root my phone and it went perfectly later than i tried to flash the rom and it failed.somehow my device stuck at the Samsung Galaxy A5 logo with these information that I cannot quite understand:
ODIN MODE
PRODUCT NAME:SM-A500F
CURRENT BINARY:CUSTOM
SYSTEM STATUS;CUSTOM
REACTIVATION LOCK(KK)FF
KNOX WARRANTY VOID:0x1(4)
QUALCOMM SECUREBOOET:ENABLED (CSB)
RP SWREV: S1,T1,H1,R1,A1,P1
SECURE DOWNLOAD:ENABLE
anyone please help me: crying:
sharifulaiman said:
well recently i tried to root my phone and it went perfectly later than i tried to flash the rom and it failed.somehow my device stuck at the Samsung Galaxy A5 logo with these information that I cannot quite understand:
ODIN MODE
PRODUCT NAME:SM-A500F
CURRENT BINARY:CUSTOM
SYSTEM STATUS;CUSTOM
REACTIVATION LOCK(KK)FF
KNOX WARRANTY VOID:0x1(4)
QUALCOMM SECUREBOOET:ENABLED (CSB)
RP SWREV: S1,T1,H1,R1,A1,P1
SECURE DOWNLOAD:ENABLE
anyone please help me: crying:
Click to expand...
Click to collapse
I had the same problem, when I flashed my testing recovery.
What u need is flash stock recovery and boot (you can find them by extracting official firmware; you can find it here) After extracted them you have boot.img and recovery.img, but odin flashes only tar files, so, to create boot.tar and recovery.tar, open terminal (if u use linux or cygwin if u use windows) and type:
Code:
tar -H ustar -c recovery.img > recovery.tar
and then
md5sum -t recovery.tar >> recovery.tar
for recovery.img and for boot.img type:
Code:
tar -H ustar -c boot.img > boot.tar
and then
md5sum -t boot.tar >> recovery.tar
If it doesn't work flash official firmware, but first try first metod, because by flashing official firmware your data will be wiped
Related
Hello,
I'm not able to build (repackage) correctly system.img for SM-G361F, output is always rejected by both Odin (10.3.7) and Heimdall
I'm trying to repackage (pre-root) system.img taken from "G361FXXU1APA2_G361FOXX1APA1_G361FXXU1APA2_HOME.tar.md5" (taken from ETL factory image named ETL-G361FXXU1APA2-20160202095551.zip )
Step-by-step:
1) tar xvf G361FXXU1APA2_G361FOXX1APA1_G361FXXU1APA2_HOME.tar.md5 system.img
2) simg2img system.img system.img.raw
3) mount system.img.raw /mnt
4) made changes
5a) make_ext4fs -s -g 32768 -b 4096 -T -1 -S file_contexts -f -l 1843M system.repack.img /mnt/
5b) mkuserimg.sh -s /mnt system.repack.img ext4 system 1843M file_contexts
6) tar --owner 0 --group 0 --numeric-owner -H ustar -c system.img > G361F_SYSTEM.tar
7a) Load either system.img through Heimdall (PIT file downloaded through Heimdall is here: http://forum.xda-developers.com/showpost.php?p=65779994&postcount=146 )
7b) Load G361F_SYSTEM.tar in Odin v3.10.7 in AP tab and flash it
On ODIN/Download screen I can see that
1) FRP LOCK: OFF
2) KNOX: 0x0
3) System status: official
4) RP SWREV: S1, L1, M1
Notes
1) I have checked the box "OEM Unlock" in Developers settings to enabled
2) "file_contexts" is taken from booted up device through ADB (adb pull /file_contexts)
3) I've tried repackage the image without making any changes
4) When I compare original and repackaged images ("ls -lsaR" outputs), it seems like owner:group permissions are not persisted
5) I've tried both simg2img/make_ext4fs/mkuserimg.sh from CM12.1 repository (up to date today) and from https://github.com/ASdev/android_img_repack_tools (branch android-5.1.1)
6) I'm not sure about size 1843M, however flashing fails in the same manner when I go with 1536M and 2048M and anything between those two
7) Heimdall fails at about 6% of flashing single (sparse system.img) file with error "Failed to unpack received packet"
OSS Kernel for SM-G361F is here: https://github.com/smarek/G361F-Kernel
OSS Platform for SM-G361F is here: https://github.com/smarek/G361F-Platform
Questions are:
1) Is there anything special to be aware of when building for Samsung devices?
2) Did I miss or misunderstood any step in system.img repackaging process?
As the title states, why can't I boot a custom boot.img when I repack the ramdisk.cpio.gz. It freezes and doesn't boot past the logo, with the text "KERNEL is not SEANDROIDENFORCING". BUT I know that the phone can boot custom boot.img 's as I removed the word "SEANDORIDENFORCING" from the original boot.img via a hex editor and flashed it to my phone. My phone booted up all the way and did not freeze or get stuck, even when the red text (KERNEL IS NOT SEANDROID ENFORCING) was shown at the top of my phone
I belive it has to do with the unpacking/repacking of the ramdisk.cpio.gz file. When ever I try to boot an image with a repacked ramdisk the phone won't boot.
Usefull info:
I am not using any scripts to unpack the boot.img as none of them seem to be able to handle a boot.img designed for a armv8 (arm64 (64 bit)) CPU (As they try to extract the kernel as a zImage when it is Image.gz, thus ending prematurely and not working). Therefore I manually unpack the boot.img via a hex editor. I know I have extracted the files properly as it would throw an error anytime you would try to extract it if it wasn't properly copied from the boot.img.
The Commands Used:
Unpack:
Code:
mkdir ramdisk
cd ramdisk
gunzip -c ../ramdisk.cpio.gz | cpio -I
Then to pack it up:
Code:
find . |cpio -o -H newc | gzip > ../ramdisk-custom.cpio.gz
OR repacking it with root ownership
Code:
find . |cpio -o -H newc -R 0.0 | gzip > ../ramdisk-custom.cpio.gz
Little Phone Info: Samsung XCover 3 Lollipop 5.1.1, No Root, Flashing via Odin.
Am I correct in assuming that the repacked ramdisk is not letting the phone boot? Or is there something I am missing or doing wrong or is just plain obvious. Any Info would be great.
In relation to this thread: http://forum.xda-developers.com/android/development/4-4-4-5-1-1-6-0-1-samsung-xcover3-t3465132/page2
DEVICE NOTE EDGE SM-N915F
I have only access to Download Mode
No Recovery or Functional ROM installed
Problem: Every time it says "There is no Pit Partition"
Already tried Install with Odin (AP_N915FXXU1BOA2.tar and TBLTE_EUR_OPEN.pit) But Same Error.
-----------------------------------------------------
ODIN MODE
Product Name: SM-N915F
Current Binary:Custom
System Status:Custom
Reactivation Lock: Off
Knock Warrenty Void: 0x1 (4)
Qualcomm Secure Boot: Enable (CSB)
AP SWREV : S1 T1 R1 A1 P1
Secure Download: Enable
UDC Start
ODIN Flash Read Failure
Error: There is no PIT Binary
Secure Check Fail: PIT
ODIN: Flash Read Failure
-----------------------------------------------------
Are you flashing only PIT and AP, or the full set: PIT, BL, AP, CP and CSC?
Sent from my SM-N915G using Tapatalk
i am receiving this same issue. is there any way you can assist as i am a first time samsung user?
I am Having same issue on my Samsung Galaxy Note Edge.
can anyone help with creating files for unbrick using MultiDownloader
1 BL1
2 Bl2.bin;
3 dram_el3mon.bin
4 dram_train.bin
5 epbl.bin
6 s-boot.bin
I uploaded sboot from firmware that was in the device
I also found boot1 and boot2 on YouTube for model a750f, should be the same since its a exynos 7885
eldon301 said:
can anyone help with creating files for unbrick using MultiDownloader
1 BL1
2 Bl2.bin;
3 dram_el3mon.bin
4 dram_train.bin
5 epbl.bin
6 s-boot.bin
I uploaded sboot from firmware that was in the device
I also found boot1 and boot2 on YouTube for model a750f, should be the same since its a exynos 7885
Click to expand...
Click to collapse
why you don't use heimdall and samloder for download original firmware tested on my SM-A750FN and I was angry theta this two programs saved my phone evrytime (one rule never flash **** on boot partitions use original fw. then you will be never Brik a phone.
use samloader like instructions
then flash in order one after another files in download mode on phone using himedall (download mode press both volume buttons and put cable in connected to pc) then use command to veryfite if device in developer mode is connected "add devices" then you use "adb reboot bootloader" then you downloads the pit file from phone to veryfite all partitions name on phone and files on computer for flash width heimadall, then flash original firmware
like me to extract original firmware on Mac OS (maybe on linux you must use other arguments for commands)
firmware to download on galaxyfirmware
for download mode press both volume buttons and put cable connected to pc
after download firmware you get it reddy for flash release firmware.zip width path of your zip
unzip -x *.zip ; rm -rf HOME_CSC* *.txt ; for f in *.md5; do tar xf $f; done && rm -rf *.md5 && unlz4 -dm *.lz4 && rm -rf *.lz4
Click to expand...
Click to collapse
then you flash it width heimdall
14 partitions in line order for flash
heimdall flash --BOOTLOADER sboot.bin --CM cm.bin --BOOT boot.img --RECOVERY recovery.img --SYSTEM system.img --VENDOR vendor.img --CACHE cache.img --ODM odm.img --OMR omr.img --HIDDEN hidden.img --RADIO modem.bin --PARAM param.bin --CP_DEBUG modem_debug.bin --USERDATA userdata.img
Click to expand...
Click to collapse
Hi,
I just bought an old Samsung Galaxy A5 (SM-A500FU) phone for experimenting purposes. I'd like to install LineageOS on this phone.
Apparently the phone has already been fiddled with. When booting into Download mode, it says "Current binary: Custom". So I downloaded the official firmware from sammobile.com and flashed it using Heimdall (I'm running Linux on my laptop):
Code:
heimdall flash \
--APNHLOS NON-HLOS.bin \
--MODEM modem.bin \
--SBL1 sbl1.mbn \
--ABOOT aboot.mbn \
--RPM rpm.mbn \
--QSEE tz.mbn \
--QHEE hyp.mbn \
--sec sec.dat \
--BOOT boot.img \
--RECOVERY recovery.img \
--SYSTEM system.img.ext4 \
--CACHE cache.img.ext4 \
--HIDDEN hidden.img.ext4
The official LineageOS documentation for my phone states to unlock the bootloader via the "OEM unlock" option in the developer options. Unfortunately this option is not showing on my phone, and judging from the number of blog posts on the web, I'm not the only one who's having this problem. Unfortunately the "solutions" offered on the web are not working, and most of them seem to be clickbait trash anyway.
Which leaves me clueless on how to unlock my bootloader. Any suggestions ?
PS : if you want to help, please post a method that works in your reply. Not some weird invitation to Discord, Telegram or some other obscure communication channel. This forum will do perfectly.
Hello kikinovak,
i have the same problem, but with a win10-pc. Because there is Stock-Android 6 on the mobile phone, there is no "OEM Unlock" in the developer options... Odin finds the device in fastboot mode, but i've to unlock the bootloader first...
Not really an advice, but who knows... ;o)
greetings from austria
on https://www.getdroidtips.com/oem-unlocking/ there is a new (but not helpful for me) info:
Now for devices launched in 2015 or later, type the following command: fastboot flashing unlock.
For devices launched prior to 2015, type the following command: fastboot oem unlock.
kikinovak said:
Hi,
I just bought an old Samsung Galaxy A5 (SM-A500FU) phone for experimenting purposes. I'd like to install LineageOS on this phone.
Apparently the phone has already been fiddled with. When booting into Download mode, it says "Current binary: Custom". So I downloaded the official firmware from sammobile.com and flashed it using Heimdall (I'm running Linux on my laptop):
Code:
heimdall flash \
--APNHLOS NON-HLOS.bin \
--MODEM modem.bin \
--SBL1 sbl1.mbn \
--ABOOT aboot.mbn \
--RPM rpm.mbn \
--QSEE tz.mbn \
--QHEE hyp.mbn \
--sec sec.dat \
--BOOT boot.img \
--RECOVERY recovery.img \
--SYSTEM system.img.ext4 \
--CACHE cache.img.ext4 \
--HIDDEN hidden.img.ext4
The official LineageOS documentation for my phone states to unlock the bootloader via the "OEM unlock" option in the developer options. Unfortunately this option is not showing on my phone, and judging from the number of blog posts on the web, I'm not the only one who's having this problem. Unfortunately the "solutions" offered on the web are not working, and most of them seem to be clickbait trash anyway.
Which leaves me clueless on how to unlock my bootloader. Any suggestions ?
PS : if you want to help, please post a method that works in your reply. Not some weird invitation to Discord, Telegram or some other obscure communication channel. This forum will do perfectly.
Click to expand...
Click to collapse
Hello,
Create a Windows VM and pass through all USB-input. It makes a lot easier!
You have to download the Samsung Drivers & Odin3 to your PC - install them.
Boot your phone ->ADB enabled (you don´t need the OEM-Unlock function, since it unlocks itself while flashing TWRP)<- into download mode (Vol. down + home + power).
Now flash your device specific TWRP with the AP-button using Odin3.
Make sure to uncheck auto reboot in Odin!
Unplug your phone, and hold Vol. up + home + power to boot into TWRP.
If you want to flash Lineage 18, make sure the TWRP version is at least 3.2, otherwise you´ll end up with error 7.
Feel free to ask me for help, in case you should need any!
Useful Links:
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
[RECOVERY][ROOT][TWRP 3.0.2-1]Samsung Galaxy A5(2015) SM-A500F/FU/G/H/M
Unofficial release -TWRP recovery for the Galaxy A5 - SM-A500F/FU/G/H/M, Qualcomm MSM8916 https://twrp.me/site/update/2016/04/05/twrp-3.0.2-0-released.html SEANDROID warning fix Recovery reboot fix Modem, APNHLOS, EFS and Recovery partition...
forum.xda-developers.com
Releases · DeadSquirrel01/lineage-17_a5_releases
lineageos 17 releases for Galaxy A5. Contribute to DeadSquirrel01/lineage-17_a5_releases development by creating an account on GitHub.
github.com
Download Odin 3.13.1 - Samsung Odin download with ROM Flashing Tool
Odin download. Download Samsung odin 3.13.1, latest Samsung ROM Flashing Tool for android - Samsung odin download
odindownload.com
This is what i´ve tested on my SM-A500FU.