Where to find the stock ROM - Samsung Galaxy J5 Questions & Answers

Hi,
does anybody know, if there is a server, where i can get the STOCK ROM?
Thanks a lot!

jaggedN said:
Hi,
does anybody know, if there is a server, where i can get the STOCK ROM?
Thanks a lot!
Click to expand...
Click to collapse
Sammobile
Updato
You can get them from telegram through a bot.
If you just googled it you would have found a lot of results

garylawwd said:
Sammobile
Updato
You can get them from telegram through a bot.
If you just googled it you would have found a lot of results
Click to expand...
Click to collapse
Hi,
thanks for the fast reply.
I am trying https://www.sammobile.com/samsung/galaxy-j5-pro/firmware/SM-J530F/DBT/download/J530FXXU6CSK9/308877/
I will report how it works....

jaggedN said:
Hi,
thanks for the fast reply.
I am trying https://www.sammobile.com/samsung/galaxy-j5-pro/firmware/SM-J530F/DBT/download/J530FXXU6CSK9/308877/
I will report how it works....
Click to expand...
Click to collapse
You may need to set up an account for sammobile but it's completely free.
Also downloads are restricted so it may take up to 2 hours to download. It's a bit of a disaster but it works and it's free so...

jaggedN said:
Hi,
thanks for the fast reply.
I am trying https://www.sammobile.com/samsung/galaxy-j5-pro/firmware/SM-J530F/DBT/download/J530FXXU6CSK9/308877/
I will report how it works....
Click to expand...
Click to collapse
Hmmm. i downloaded a J530FXXU6CSK9_J530FDBT6CSL1_DBT.zip
If i do a
adb sideload J530FXXU6CSK9_J530FDBT6CSL1_DBT.zip
but the smartphone refuses with "invalid zip file format"
Inside the ZIP there are the following files:
AP_J530FXXU6CSK9_CL16642474_QB27583084_REV00_user_low_ship_meta_OS9.tar.md5
BL_J530FXXU6CSK9_CL16642474_QB27583084_REV00_user_low_ship.tar.md5
CP_J530FXXU6CSK9_CP14486297_CL16642474_QB27583084_REV00_user_low_ship.tar.md5
CSC_DBT_J530FDBT6CSL1_CL17419960_QB27658856_REV00_user_low_ship.tar.md5
HOME_CSC_DBT_J530FDBT6CSL1_CL17419960_QB27658856_REV00_user_low_ship.tar.md5
Do i have to flash the ROM with heimdall?

I tried with heimdall:
Code:
~/bin/heimdall flash --RECOVERY J530FXXU6CSK9_J530FDBT6CSL1_DBT.zip
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
6%
Now it is stuck at 6%...
Any idea? Can i switch of my phone without completely damaging it?

Got it running:
unzip the ZIP
then
Code:
for a in *md5; do echo $a; tar -xvf $a; done
then
Code:
for a in *lz4; do echo $a; unlz4 $a; done
and after all i followed: https://ar.al/2018/07/15/flashing-s...-s9+-sm-g965f-on-ubuntu-18.04-using-heimdall/
Code:
~/bin/heimdall flash --BOOT boot.img --SYSTEM system.img --CACHE cache.img --HIDDEN hidden.img --PARAM param.bin --CM cm.bin --USERDATA userdata.img --RADIO modem.bin --BOOTLOADER sboot.bin --RECOVERY recovery.img
and now it is booting up with the samsung logo again

Related

[Q] How can i flash aboot.mbn

Hello everyone,
I was wondering if there was a way to flash aboot.mbn to the aboot partition.
I have tried Heimdall however it does not seem to be compatible with the s5 yet and odin v3.09 and v1.85 also gives me problems and thus far have been unable to flash it. I have also tried the dd command from and android terminal emulator
Code:
dd if=/storage/extSdCard/aboot.mbn of=/dev/block/mmcblk0p6
which also did not work and i do not believe that mobile odin can flash aboot either.
So my question is is there any other way to flash aboot or am i stuck until heimdall updates compatibility?
i am on G900T s5.
Thank You.
If u got adb installed on your pc, using following command
fastboot devices
fastboot flash aboot aboot.img
babygau said:
If u got adb installed on your pc, using following command
fastboot devices
fastboot flash aboot aboot.img
Click to expand...
Click to collapse
I tried but i do not think that samsung adds support for fastboot at all since the use their own download mode for odin and stuff
I am still stuck on this last hurdle, any help welcome thanks
I could really use the help, this is the last thing in my way
cm0002 said:
I could really use the help, this is the last thing in my way
Click to expand...
Click to collapse
Can you not be able to reflash stock firmware using Odin???
babygau said:
Can you not be able to reflash stock firmware using Odin???
Click to expand...
Click to collapse
No for whatever reason odin fails to flash when i package aboot.
i package it as a tar with 7zip, just aboot.mbn file nothing special and no special settings, or am i missing something that odin needs?
cm0002 said:
No for whatever reason odin fails to flash when i package aboot.
i package it as a tar with 7zip, just aboot.mbn file nothing special and no special settings, or am i missing something that odin needs?
Click to expand...
Click to collapse
Odin doesn't flash zip file bro
Why not using Odin to flash your complete stock firmware?
Hi,
I am also stuck with flashing aboot.mbn, did you have any luck since?
ferdossi said:
Hi,
I am also stuck with flashing aboot.mbn, did you have any luck since?
Click to expand...
Click to collapse
what is the purpose of just flashing the aboot.img?
youdoofus said:
what is the purpose of just flashing the aboot.img?
Click to expand...
Click to collapse
in fact I don't just flash aboot, my issue occurs when I try to flash the I9505XXUHPK2.tar bootloader which contains also other files but ODIN stops when trying to flash aboot.mbn

Unbrick using Heimdall and linux

Ok, in my case I had already upgraded to an MLD baseband, and after messing around with some ROMs, couldn't get back into safestrap recovery. I don't know if this will work if you've upgraded to NB1 or NC1, maybe someone else can chime in.
1. Install heimdall. It's in the ubuntu repositories. Also, put the towelroot and safestrap (I used v. 3.72) apks, as well as a kitkat ROM (no need for it to be pre-rooted). Also get the Deadly Venom safestrap kit, version 2 MLD/MK2 and save to your computer. Get the mldmodules.zip file and place on your SD card as well.
2. Download the appropriate firmware. In this case, you're looking for stock MK2/ I337. I got it from this link, and used the 4 separate files in post #1.
3. Untar the files. You can either rename the *.md5 files, removing the md5 extension, or just tar -xvf each file. You should end up with boot.img, cache.img.ext4, hidden.img.ext4, JFLTE_USA_ATT_16G.pit, modem.bin, NON-HLOS.bin, persdata.img.ext4, recovery.img, rpm.mbn, sbl1.mbn, sbl2.mbn, sbl3.mbn, system.img.ext4, and tz.mbn.
4. Put your device in download mode by pressing volume down + power, then letting go of power button. Connect your USB cable.
5. Run the following commands, which I got from here.
Code:
sudo heimdall flash --RECOVERY recovery.img --SYSTEM system.img.ext4 --HIDDEN hidden.img.ext4 --BOOT boot.img --no-reboot
I added the no-reboot option because I was able to see the errors on the device screen. I then rebooted back into download mode.
Code:
sudo heimdall flash --MDM modem.bin --APNHLOS NON-HLOS.bin --ABOOT aboot.mbn --BOOT boot.img --TZ tz.mbn
At this point I rebooted again, and it booted, but hung at the AT&T logo. I rebooted and it started normally. I didn't actually use the next step.
Code:
sudo heimdall flash --CACHE cache.img.ext4
And Poof! You're back to stock. At this point, go to My Files, and find the towelroot apk, and install it. Then install safestrap. Reboot to recovery (power + vol up), wipe everything except your SD under advanced wipe, and install your ROM. Don't reboot here--install the mldmodules.zip file. Now reboot back into download mode.
Unrar (or whatever, I forget how it was compressed) the Deadly Venom kit. You should end up with an MLD directory. Go to the MLD Odin Files directory, and untar the md5 files there. Again, you can rename them first or not. You should end up with:
modem.bin, recovery.img, sbl1.mbn, sbl3.mbn, ap_mld_safestrap.tar, bl_mld_safestrap.tar, boot.img, cp_mld_safestrap.tar.md5, NON-HLOS.bin, rpm.mbn, sbl2.mbn, and tz.mbn.
Ok, so here's where I did some guessing. I don't know how to use Heimdall, and I couldn't make sense of the front end. I did some trial and error, and here's the command that I ended up with that worked:
Code:
sudo heimdall flash --RECOVERY recovery.img --BOOT boot.img --ABOOT aboot.mbn --APNHLOS NON-HLOS.bin --MDM modem.bin --SBL1 sbl1.mbn --SBL2 sbl2.mbn --SBL3 sbl3.mbn --TZ tz.mbn --RPM rpm.mbn
Now reboot, and you should be in business. You may need to run towel root again. Oh, and I was getting a lot of weird errors when I was trying to flash with heimdall--I think it ended up being a flaky USB controller on my computer (or maybe a bad USB cable). The install kept hanging. Changing to a different computer solved the problem.
I stumbled through a lot of this, so if there is any redundancy, or if someone wants to improve on this, please do. But hopefully this helps someone...

deletion request

mods delete this thread
droid.riz said:
Pre-requisites - Drivers Installed,ADB,Fastboot.
Download - cm-12.0-YNG1TAS0YL-bacon-signed-fastboot
Download - user_data(64gb variant) (also you can use cm11s one if you have it place it inside the extracted fastboot files)
-Reboot your device into Fastboot Mode (power + volume up).
-connect your phone to your PC via usb cable.
-Unzip the file you downloaded and put its contents into your fastboot folder (the same folder that you have adb.exe and fastboot.exe located in on your PC).
-Open CMD in that folder (Shift+Right click and open new cmd window here)
-first check the device by entering this command
Code:
fastboot devices
- Enter these commands one by one
Code:
fastboot flash modem NON-HLOS.bin
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash sbl1 sbl1.mbn
Code:
fastboot flash dbi sdi.mbn
Code:
fastboot flash rpm rpm.mbn
Code:
fastboot flash aboot emmc_appsboot.mbn
Code:
fastboot flash tz tz.mbn
Code:
fastboot flash LOGO logo.bin
Code:
fastboot flash oppostanvbk static_nvbk.bin
Code:
fastboot flash boot boot.img
Code:
fastboot flash cache cache.img
Code:
fastboot flash system system.img
Code:
fastboot flash userdata userdata_64G.img
or fastboot flash userdata userdata.img if you have the 16gb model)
P.S This Userdata will wipe ur internal storage you can skip it if you want.
​
Click to expand...
Click to collapse
What the hell? You plagiarized these instructions directly from my guide thread here:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
You've barely even bothered to change the wording.
Transmitted via Bacon
@timmaaa added credits.
droid.riz said:
@timmaaa added credits.
Click to expand...
Click to collapse
Too late for that now, the damage is done. You can't just steal someone else's work and try to pass it off as your own. I worked damn hard on my guide thread, to make sure it's accurate and safe for people to use, I didn't do all that work only to have someone steal it and claim authorship.
Transmitted via Bacon
And about userdata_64G.img from here
timmaaa said:
Too late for that now, the damage is done. You can't just steal someone else's work and try to pass it off as your own. I worked damn hard on my guide thread, to make sure it's accurate and safe for people to use, I didn't do all that work only to have someone steal it and claim authorship.
Transmitted via Bacon
Click to expand...
Click to collapse
okay great ! i am requesting mod to delete the thread.
anagramgenius said:
And about userdata_64G.img from here
Click to expand...
Click to collapse
hahah i never saw your post!
I'll just leave this here:
12. Using the work of others.
"If you are developing something that is based on the work of another Member, you MUST first seek their permission and you must give credit to the member whose work you used. If a dispute occurs about who developed / created a piece of work, first try to settle the matter by private message and NOT in open forum. If this fails, you may then contact a Moderator and provide clear evidence that the work was created by you."
Thread closed

Heimdall back to stock.

Hey guys. I don't have a windows computer anymore and I'm trying to restore my wife's i9505 back to stock. Is there a one click file for heimdall I can use. I've been searching everywhere and can't find one. Thanks
Sent from my GT-N7100 using Tapatalk
Goneeuro said:
Hey guys. I don't have a windows computer anymore and I'm trying to restore my wife's i9505 back to stock. Is there a one click file for heimdall I can use. I've been searching everywhere and can't find one. Thanks
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Use this for reference:
http://andmod.blogspot.nl/2013/02/tutorial-flashing-i9000-i9100-or-i9300.html
You need to get the correct .pit file for the I9505.
You can also do it from the command prompt:
heimdall flash --APNHLOS NON-HLOS.bin
heimdall flash --ABOOT aboot.mbn
heimdall flash --BOOT boot.img
heimdall flash --HIDDEN hidden.img.ext4
heimdall flash --MDM modem.bin
heimdall flash --RECOVERY recovery.img
heimdall flash --RPM rpm.mbn
heimdall flash --SBL2 sbl2.mbn
heimdall flash --SBL3 sbl3.mbn
heimdall flash --SYSTEM system.img.ext4
heimdall flash --TZ tz.mbn
heimdall flash --CACHE cache.img.ext4
Click to expand...
Click to collapse
You can also do it one command: "heimdall flash --ABOOT aboot.mbn --BOOT boot.img" etc etc
Thanks. Hope all goes well tonight.
Sent from my GT-N7100 using Tapatalk

Touch will not work, no idea how to fix

I was trying to root my device but i got to the twrp recovery and the touch would not work. ADB requires me to re-authorize my device, which I can not do with the touch not functioning. I'm not sure what I need to do, I'd like to just forget the whole thing and go back to stock. I've got it at the "lets go" startup screen but can't click anything due to touch not working.
Please, can someone tell me how to do this, I've been looking for hours and am having to use a god damn iphone in the mean time until its fixed.
Thank y'all a bunch
mrwiggles727 said:
I was trying to root my device but i got to the twrp recovery and the touch would not work. ADB requires me to re-authorize my device, which I can not do with the touch not functioning. I'm not sure what I need to do, I'd like to just forget the whole thing and go back to stock. I've got it at the "lets go" startup screen but can't click anything due to touch not working.
Please, can someone tell me how to do this, I've been looking for hours and am having to use a god damn iphone in the mean time until its fixed.
Thank y'all a bunch
Click to expand...
Click to collapse
This is literally what everyone's been talking about lately.. there's a few threads here with detailed instructions I believe .
mrwiggles727 said:
I was trying to root my device but i got to the twrp recovery and the touch would not work. ADB requires me to re-authorize my device, which I can not do with the touch not functioning. I'm not sure what I need to do, I'd like to just forget the whole thing and go back to stock. I've got it at the "lets go" startup screen but can't click anything due to touch not working.
Please, can someone tell me how to do this, I've been looking for hours and am having to use a god damn iphone in the mean time until its fixed.
Thank y'all a bunch
Click to expand...
Click to collapse
You need the hyp and rpm images from both Aug and Sep.
If touch isn't working flash one or the other.
fastboot flash hyp_a hyp.mbn
fastboot flash hyp_b hyp.mbn
fastboot flash rpm_a rpm.mbn
fastboot flash rpm_b rpm.mbn
In the Sept release they were not initially included.
They changed from Aug to Sept, so if your kernel/boot was built with Aug or Sep you will need to change these files.
tech_head said:
You need the hyp and rpm images from both Aug and Sep.
If touch isn't working flash one or the other.
fastboot flash hyp_a hyp.mbn
fastboot flash hyp_b hyp.mbn
fastboot flash rpm_a rpm.mbn
fastboot flash rpm_b rpm.mbn
In the Sept release they were not initially included.
They changed from Aug to Sept, so if your kernel/boot was built with Aug or Sep you will need to change these files.
Click to expand...
Click to collapse
Right, so I can do that. However, I still have the issue of getting my phone to authorize the debugging from my computer with no touch ability. This is my big problems really. ANy idea besides that whole mouse adapter OTG?
mrwiggles727 said:
Right, so I can do that. However, I still have the issue of getting my phone to authorize the debugging from my computer with no touch ability. This is my big problems really. ANy idea besides that whole mouse adapter OTG?
Click to expand...
Click to collapse
You don't need to flash those zips or use OTG. Instructions in rooting thread, you have to use pre-patched boot.img that's linked in Notes in OP, worked for me on Sep builds: https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
I too was trying to deal with the touch issues, and this was the method that worked for me.
I got the touch to work and it boots into twrp recovery but i had to flashall and it smoked the zip files on my phone. How do I push the zips from computer to internal Storage? I was having trouble getting it in with adb
mrwiggles727 said:
I got the touch to work and it boots into twrp recovery but i had to flashall and it smoked the zip files on my phone. How do I push the zips from computer to internal Storage? I was having trouble getting it in with adb
Click to expand...
Click to collapse
adb push (original location on PC) /sdcard/file.extension
mrwiggles727 said:
I was trying to root my device but i got to the twrp recovery and the touch would not work. ADB requires me to re-authorize my device, which I can not do with the touch not functioning. I'm not sure what I need to do, I'd like to just forget the whole thing and go back to stock. I've got it at the "lets go" startup screen but can't click anything due to touch not working.
Please, can someone tell me how to do this, I've been looking for hours and am having to use a god damn iphone in the mean time until its fixed.
Thank y'all a bunch
Click to expand...
Click to collapse
I have same issue. Please help me solve it step by step. i am newbie. Thanks.
tech_head said:
You need the hyp and rpm images from both Aug and Sep.
If touch isn't working flash one or the other.
fastboot flash hyp_a hyp.mbn
fastboot flash hyp_b hyp.mbn
fastboot flash rpm_a rpm.mbn
fastboot flash rpm_b rpm.mbn
In the Sept release they were not initially included.
They changed from Aug to Sept, so if your kernel/boot was built with Aug or Sep you will need to change these files.
Click to expand...
Click to collapse
Do I need to download said files to flash or just type it into fastboot command line?
jrodbrown58 said:
Do I need to download said files to flash or just type it into fastboot command line?
Click to expand...
Click to collapse
Yes, you must download the files to your PC.
Any time you are fastboot flashing a file, the file must exist on the PC in a location where fastboot can find it. Typically, the file is put in the same directory that your Fastboot executable is located so you are not dealing with providing paths to the file; you just cd to the directory with the fastboot executable and run all of your command from there.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
Yes, you must download the files to your PC.
Any time you are fastboot flashing a file, the file must exist on the PC in a location where fastboot can find it. Typically, the file is put in the same directory that your Fastboot executable is located so you are not dealing with providing paths to the file; you just cd to the directory with the fastboot executable and run all of your command from there.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
That's what I thought and I found the hyp and rpm files I believe using this reddit post
https://www.reddit.com/r/essential/comments/9d3kru/the_september_update_twrp_and_touch/
But they are in a form of a zip and when I extract it there's no mbn file extension. So I don't know whether I should add that file extension or flash the zip in twrp...is there anything else I should do or know about before I try this again?
jrodbrown58 said:
That's what I thought and I found the hyp and rpm files I believe using this reddit post
https://www.reddit.com/r/essential/comments/9d3kru/the_september_update_twrp_and_touch/
But they are in a form of a zip and when I extract it there's no mbn file extension. So I don't know whether I should add that file extension or flash the zip in twrp...is there anything else I should do or know about before I try this again?
Click to expand...
Click to collapse
What aren't you using the files from post #3 (that you quoted in your initial post)?
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
ktmom said:
What aren't you using the files from post #3 (that you quoted in your initial post)?
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
Complete stupidity and lack of sleep from working too much lol but thank you for you help
tech_head said:
You need the hyp and rpm images from both Aug and Sep.
If touch isn't working flash one or the other.
fastboot flash hyp_a hyp.mbn
fastboot flash hyp_b hyp.mbn
fastboot flash rpm_a rpm.mbn
fastboot flash rpm_b rpm.mbn
In the Sept release they were not initially included.
They changed from Aug to Sept, so if your kernel/boot was built with Aug or Sep you will need to change these files.
Click to expand...
Click to collapse
Will this work on Nov patch?
I was following this guide, Guide B, since I was rooted in the AUG: https://www.reddit.com/r/essential/comments/9uhz9d/update_to_november_root_and_twrp_patched_boot/
and its made my touches unresponsive.
It works for me
mrwiggles727 said:
I got the touch to work and it boots into twrp recovery but i had to flashall and it smoked the zip files on my phone. How do I push the zips from computer to internal Storage? I was having trouble getting it in with adb
Click to expand...
Click to collapse
How did you get the touch working. Please help. I am stuck
Bitan701 said:
How did you get the touch working. Please help. I am stuck
Click to expand...
Click to collapse
If you are on the latest stock Nov. I would think the easiest way would be to download the same version from the back to stock images thread. In that will be a boot image pre patched with magisk and a working twrp. Just need to flash that boot image from fastboot.
If you don't want magisk you could still do this then flash the stock boot image within twrp and install the zip installer for twrp.
Or if you have a USB C OTG cable you can just plug in a mouse.

Categories

Resources