Database Users

[GUIDE] Flashing with Heimdall

Heimdall is an alternative, cross-platform tool to flash firmwares for the Galaxy S series of devices, including the Tab.
Heimdall
Some of you might not have heard but a brilliant guy one day woke up and thought 'damn it Odin' and started working on Heimdall. The guy reverse-engineered the protocol to flash our Galaxy's and turned up a piece of software called Heimdall that can do exactly the same as Odin.
This tool is open-source and runs on Qt for its GUI and libusb to communicate over USB making this tool completely cross-platform. This basically means flashing your Galaxy is not just limited to Windows anymore.
This guide will walk you through the steps to work with Heimdall. I'm a Mac user so the screenshots you'll see will be Mac-y. However, since the app and GUI are cross-platform the same apply for both Windows and Linux.
Disclaimer:
Flashing your device through anything but Kies can be a dangerous business and can brick your Galaxy S.
That said, Samsung seems to have engineered the Galaxy S series in a way that makes it relatively difficult to brick even if you **** up.
Proceed with caution and at your own discretion, both the developers of Heimdall and I can not be held accountable for the possible damage you do to your device by following this guide or using Heimdall.
Flashing with Heimdal
Flashing with Heimdall is a little bit different than with Odin. With Odin you usually select a PIT, if necessary, add the PDA.tar.md5, Modem.tar.md5 and CSC.tar.md5 to the locations, put the phone in download mode and hit go.
Heimdall takes a different approach. In the Heimdall GUI you need to select all components you want to flash. This means extracting the TAR-archives and pointing Heimdall to their respective files. This allow relative fine-grained control over what you flash and doesn't depend on files being named correctly.
In order to install Heimdall head over to the guy's website and download and install Heimdall.
Do yourself a favor, even if you're on Linux or Mac, just reboot after the install. On OS X the installation includes a kernel extension and though this can usually be reloaded by logging out and back in again the reboot is safer and can't hurt.
Mac OS X specific
For Mac OS X the 1.1.0 version of Heimdall includes some nuked Qt binaries which means the GUI won't start. This can be fixed by afterwards installing Qt from here.
The above should not apply to the latest Heimdall release anymore according to the release notes. If however you still get errors about Heimdall failed to start, just install the Qt binaries linked above anyway, should take care of the error.
There is a second problem unfortunately on OS X. Due to a bug in older versions of the bootloader the device doesn't register correctly in download mode. If you then try to flash without having fixed the bootloader you'll nuke the Galaxy S and end up at a "black screen of death". Trust me, I tried, it broke and it scared the crap out of me.
Don't worry, this isn't the dreadful black screen of death meaning your device is busted, it just means your firmware is. You can just put it into download mode again and flash another firmware over it with Odin (Windows)
In order to avoid this we need to fix the bootloader first. Everyone who has installed the official Froyo update through Kies will already have a fixed bootloader and so you can ignore the next bit. If however you hocus-pocused around with Kies / Odin to flash Froyo like I did you probably don't have the updated bootloader.
Unfortunately we're going to need Windows for this and Kies so either get a VM ready, bootcamp into Windows or find a friend who'll lend you his pc for an hour.
See the second post, "Fixing the bootloader" for instructions.
Click to expand...
Click to collapse
Linux specific
As far as I'm aware there are no Linux specific problems, not even the bootloader issue mentioned above for OS X. However, it might be wise to follow the instructions anyway since an updated bootloader can't hurt.
Click to expand...
Click to collapse
Windows specific
As far as I'm aware there are no Windows specific problems, not even the bootloader issue mentioned above for OS X. However, it might be wise to follow the instructions anyway since an updated bootloader can't hurt.
Click to expand...
Click to collapse
Now, time to get busy.
I'm going to assume that you have downloaded a firmware, for example from samfirmware, and have extracted the .RAR and the .TAR inside and now have a folder with at least the following:
factoryfs.rfs (PDA > FactoryFS)
param.lfs (PDA > Param.lfs)
zImage (PDA > Kernel (zImage))
Additionally you might have:
cache.rfs (CSC > Cache)
modem.bin (Other > Modem)
Be aware, there are other configurations possible. For example, when you're rooting by flashing a rooted kernel there will probably only be a zImage.
Start Heimdall or Heimdall-frontend, you should get a screen similar to this:
{
"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"
}
Now, unless explicitly stated that you need a .PIT to flash this firmware you can leave this field blank. If you load a PIT, be sure to see if you need to repartition. The general rule is that you won't, unless you flashed with a firmware that had a different PIT than what samfirmware is indicating you need.
After that, start hitting the browse button for the components you want to flash with Heimdall and add them. Your screen will probably look something like this:
Now, it's time to put your phone in download mode. Power off the phone and wait for it to completely have shut down and unplug it from USB / charger. Hold down the Home and Volume Down buttons and then press Power. Keep holding those three buttons until you get into download mode (you'll know when you see it).
If you can't get into download mode / nothing seems to happen, you probably have a Galaxy with the broken 3-button combo problem, see here for a fix:
http://forum.xda-developers.com/showthread.php?t=785201
Now, connect the phone over USB with your computer. If you're on on Mac and Linux you can proceed immediately. If you're on Windows you'll probably need to wait for Windows to install a driver or two.
Now hit the Start button and watch it go!
If all goes well you'll see the progress bar on both Heimdall and in your phone filling up (might take a while for one to appear on the Galaxy S). Once it's done it'll probably say everything went OK and the Galaxy will reboot into recovery. Let it do it's thing, it will reboot again and begin booting the new firmware.
After having installed a new firmware the first boot might take a while. You'll just seem to be stuck at the glowing S, just let it run it will boot eventually.
If however Heimdall says "Failed" your phone will (probably) reboot or when you try to reboot you'll get stuck at the "black screen of death":
This isn't a "my device is bricked" screen, just that you ****ed up the firmware. Just follow the instructions again, put it in download mode and try again.
If, after having seen the above screen, you can't get your phone into download mode, then you're toast.

Fixing the bootloader
Fixing the bootloader
In order to fix the bootloader we need to flash some firmware. There's always the risk of data loss so make a backup first!
First we need Kies available on Windows, so grab it and install it. See the XDA wiki about this.
Once Kies is done installing don't launch Kies or exit it first, then connect your Galaxy S. Let Windows purr for a while as it gets busy installing your device drivers. Once it says it's done, you can start Kies.
Now, it's time to get the Kies registry patcher. We'll use this tool to fool Kies into thinking an older version is running on the Galaxy S so that it presents us with the option to grab the Froyo update.
Once you've started Kies and Kies has recognised your phone, start the Kies registry patcher. Set the Fake mode to True and select your product code. As I'm Dutch, I selected XEN from the dropdown. There is a list on the XDA wiki to tell you which product code is suited for your country, I suggest you use that one.
Now hit the "Write registry" button and then inside Kies, select the update firmware button in the bottom right corner (the phone with the arrow). Kies will now probably tell you it has an update for your phone which should be in the JP* series or GJK3, meaning it is the Froyo update.
Tell Kies to update your phone. Kies will get busy downloading the firmware and flashing it. Your phone will reboot into download mode, once that done you'll see recovery mode and then it will start booting.
Now that you have installed the official Samsung Froyo Galaxy S update you'll have the fixed bootloader you need in order to be able to use Heimdall on OS X.

crystal clear and helpful. thank you.

Many THANKs for this Guide!! Great work

great guide !
... added to the wiki

AllGamer said:
... added to the wiki
Click to expand...
Click to collapse
Thanks. Figured it might help some people .

No Windows
The reason why I'm using Heimdall is because I'm on a mac and don't have access to a Windows pc. The whole bootloader step kind of makes it impossible for me to use Heimdall. Is there a workaround?
Ps. When I say I don't have access to a windows pc, I mean it. I'm approx. 10 hours north of any major city, in the wilderness.

If you had working 3-BR prior to flashing & getting the phone computer icon with a ! in the triangle, I think there is hope.
If you really blotched your flashing, & get that semi-bricked icon when you try to into download mode, Heat the phone a bit & press Vol down + Menu + Power button for a very long time. This has happened to me thrice on my SGS with working 3-BR, & the longest it took me to go into download mode was something like over 30 seconds.
Hope this helps.

My Heimdall doesn't let me flash if I select a PIT file... And already tried with 3 diferent PIT files. Do you know why?

i followed the guide, but heimdall says "Failed to start Heidall"
i've a mac intel 10.6

hi
what does the following error mean?
Failed to access device. Error: -12

Failed to access device is quite literally what it means, failed to access device.
This usually means something is wrong in download mode or the USB kext is acting up. A reboot should solve it, put your phone back into download mode and you should be good to go.

baul87 said:
i followed the guide, but heimdall says "Failed to start Heidall"
i've a mac intel 10.6
Click to expand...
Click to collapse
I only got that error with the problematic QT binaries. Did you install the "normal" QT binaries after installing Heimdall? (See the Mac OS X Specific part of the opening post).

I'm on a Samsung Fascinate is it completely necessary to update to the Samsung Froyo Bootloader for this to work? The Fascinate doesn't even have Froyo yet. Thanks in advance.

daenney said:
If, after having seen the above screen, you can't get your phone into download mode, then you're toast.
Click to expand...
Click to collapse
Well, I got that screen message and can no longer go into download mode. Not sure what happened, but I apparently did something wrong.
QUESTION: if I take this into a Verizon store, will they be able to tell that I had rooted the device? I'd like to take it in under warranty.

Get yourself a USB JIG (see toopic about unbrick JIG), when you plug that into your phone (when its offline) it will go into download mode no metter you did had BSOD or not (I have it all the time with odin, I'm starting to think my device is ****ed up though )

I receive "Failed to detect compatible device" I have Heimdall running. The only way I can get into the Download screen is to take my battery out completely and plug into USB while holding Vol Down and power.I put the correct Modem.bin file in the correct place and hit start but I keep getting an error.
Im on a rooted Fascinate coming from a Stock DL09. I installed a Rom and Kernel w/ Rom manager.But I had issues w/ SMS learned it was because of the Radio/Modem

I keep getting failed to access device error 12. I'm not sure why. I've restarted the SW and get same response. Odin detects the device as well as my OS. Is this not compatible with the Sprint Galaxy tab or do i need specific drivers?

Bxsteez said:
I keep getting failed to access device error 12. I'm not sure why. I've restarted the SW and get same response. Odin detects the device as well as my OS. Is this not compatible with the Sprint Galaxy tab or do i need specific drivers?
Click to expand...
Click to collapse
Check the readme in the heimdall directory. For the windows version you must install the drivers attached.

kunjar said:
Check the readme in the heimdall directory. For the windows version you must install the drivers attached.
Click to expand...
Click to collapse
Yup. I did that but it appears i installed the wrong driver. I tried to delete the driver but that didn't work. I had to switch to another computer and it worked perfectly.

[Ref][Guide] Galaxy Note N7000 Factory Firmware Restore

This is just like any other guide that tells you how to restore your phone to factory...
Please Note All User Data Will Be Lost
Recommended Battery is Fully Charged..
Requirement:
Odin3 1.85 (Download links Attached)
Window Drivers [32bit] or [64bit]
MicroUSB data cable for phone
Firmware files for mobile phone
Phone Obviously....
GB Firmwares: (if password required its "samfirmware.com")
-N7000DXKK1; N7000DXKJ3; N7000OLBKJ6
-N7000JPKJ4; N7000XXKJ4; N7000OJPKJ3
-N7000JPKK2; N7000XXKK5; N7000OJPKK2
-N7000XXKJ4; N7000XXKJ4; N7000PLSKJ3
-N7000XXKJ1; N7000XXKJ1; N7000OXAKJ1
-N7000XXKJ4; N7000XXKJ4; N7000OXAKJ4
-N7000XXKJ4; N7000XXKJ4; N7000XEOKJ1
-N7000XXKJA; N7000XXKJ4; N7000OXXKJ8
-N7000XXKK9; N7000XXKK5; N7000OXAKK9
-N7000XXKKA; N7000XXKK5; N7000OXXKK5
-N7000ZSKK1; N7000XXKJ6; N7000OZSKK1
ICS Firmware (Official)
N7000XXLPY (Single File Load in PDA)
N7000ZSLPF Build: 15.05.2012
FIRMWARE NAME DECODE
Warning: Don't Do This For Fun... could make your phone a nice paper weight..... use only if NEEDED.... I'm not responsible for any mistakes.... The Risk is YOURS!!!
PIT Info:
Changing PIT file (repartitioning ROM) will not affect mobile phone's speed.
PIT files will repartition the mobile phone's ROM (Read-Only Memory). Changing (repartitioning the ROM area) will modify only the space trade between the /system and /dbdata.
What is CSC?
CSC = Country Sale Code
CSC code depends on the region where the phone was sold.
CSC contains the phone settings (internet, wap, mms...), specific applications which available in certain regions, and operator customizations.
CSC code could be changed by flashing a new firmware (including CSC file) on phone. That will change phone language and settings.
Use *#272*IMEI# code on phone to view the list of the available CSCs, or change CSC. (Changing CSC will erase the phone!)
Lets Get Started..
1. Install Samsung USB drivers (in most cases already installed)..
2. Enter Download mode by pressing Volume down, OK and power buttons at the same time. Phone will start in Download mode.
{
"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"
}
3. Press Volume Up..
4. Connect phone to USB cable. (Windows will install if needed).
5. Run Odin Software
6.If repartition is needed, Press PIT button to select .pit file. (Choose The Correct one for your phone internal memory size 16 or 32 GB)
7. Flash Bootloader If Needed, Enable Phone Bootloader Update then press Bootloader button to select bootloader file (filename: KERNEL_... .md5). (Important: Changing / flashing wrong bootloader could damage the phone!)
8.Press PDA, then select PDA file (filename: CODE_... .md5).
9. Press PHONE, then select PHONE file (filename: MODEM_... .md5)
10.Press CSC, then select CSC file (filename: ...-CSC-... .md5).
11. Verify Odin software recognize phone. When the phone is recognized, ID:COM is highlighted in yellow Note: the number can vary(if not repeat steps 2.)
12.Press Start button to begin flashing procedure.
13. Wait a few minutes flashing procedure to complete, This Can Take Some Time.... Plz Be Patience.....
Once Completed PASS! will appear on the upper left corner, and it will be highlighted in green.
---------------------------------------------------------------------------------------------------
Note: if only one file is in firmware download load in into PDA Section leave the rest empty and off as default

hello cannot download one of your roms

brockyneo said:
hello cannot download one of your roms
Click to expand...
Click to collapse
sorry try again links fixed

antiguangenius said:
sorry try again links fixed
Click to expand...
Click to collapse
thank you why do you think this will work for our bricked devices
also are all the files like bootloader and kernel all with the rom download i really hope this works thank you

brockyneo said:
thank you why do you think this will work for our bricked devices
also are all the files like bootloader and kernel all with the rom download i really hope this works thank you
Click to expand...
Click to collapse
read whole post carefully....

Thanks a lot mate, I've finally recovered my phone

Last resort actions always...pit & bootloader flashing. does the ics update require these?

Avlrln said:
Last resort actions always...pit & bootloader flashing. does the ics update require these?
Click to expand...
Click to collapse
dude this guide is all about factory state... in other words GB

Thank You!!!

not work in my case do same as he mantion
brockyneo said:
thank you why do you think this will work for our bricked devices
also are all the files like bootloader and kernel all with the rom download i really hope this works thank you
Click to expand...
Click to collapse
not work in my case do same as he mantion

.pit file
.PIT file is used for full flashing method, this is only advisable and useful for reverting back to original firmware when previously installed unofficial ROM or to fix softbricked devices like unable to boot normally.

I hope not to be OT in this thread and sorry for my bad english.
I would like to ask a question about the recovery / download mode.
It is necessary that the device is turned off before using the specific combo? (vol. up/down + home + power)
Can I go into recovery mode even when the terminal is already on?
If not, why?
Thanks in advance

posalaquaglia said:
I hope not to be OT in this thread and sorry for my bad english.
I would like to ask a question about the recovery / download mode.
It is necessary that the device is turned off before using the specific combo? (vol. up/down + home + power)
Can I go into recovery mode even when the terminal is already on?
If not, why?
Thanks in advance
Click to expand...
Click to collapse
You need to switch off first, otherwise it will just bootloop rather starting in recovery.

posalaquaglia said:
I hope not to be OT in this thread and sorry for my bad english.
I would like to ask a question about the recovery / download mode.
It is necessary that the device is turned off before using the specific combo? (vol. up/down + home + power)
Can I go into recovery mode even when the terminal is already on?
If not, why?
Thanks in advance
Click to expand...
Click to collapse
Are you asking if you can go into Recovery or Download mode when your phone is on,ie,w/o switching it off?
Yes you can.For recovery mode press up volume+home+power(strangely enough any combo works.power+home+volume but keep them pressed till the phone reboots and you see the Samsung GT-N7000 logo then u can let go.
For Download mode press down volume+home+power(again in any combo)
Hope i answered your question

dr.ketan said:
You need to switch off first, otherwise it will just bootloop rather starting in recovery.
Click to expand...
Click to collapse
I already tried going into recovery mode with the phone turned on without bootloop problem!
I'd like to know if this is a correct procedure or not, because there are people who say they can usually do.
---------- Post added at 08:01 PM ---------- Previous post was at 07:33 PM ----------
zeeshanonlyme said:
Are you asking if you can go into Recovery or Download mode when your phone is on,ie,w/o switching it off?
Yes you can.For recovery mode press up volume+home+power(strangely enough any combo works.power+home+volume but keep them pressed till the phone reboots and you see the Samsung GT-N7000 logo then u can let go.
For Download mode press down volume+home+power(again in any combo)
Hope i answered your question
Click to expand...
Click to collapse
Yes!
Thanks a lot.

Lots of people have bricked their phone while repartitioning and using PIT.
I would say read carefully when you try it.
If I ever get superbricked I'd just kill it with Angelom test kernel or if I want to return to clean state - I'd flash any safe kernel - perform factory reset, format system partition and sd card then flash latest stock firmware available for my region.

doesn't work
it stops by "Hidden"
<ID:0/005> factoryfs.img
<ID:0/005> hidden.img
I let it for 1 hour, but it's not working... Can someone tell me what I'm doing wrong

Galaxy Note GT-N7000 Modem locked
My Galaxy Note GT-N7000 I purchased this Cell phone in europe it was not working as 3 G on Tmobile I flashed modem, after that I was not able use as cell when I try to call getting insert the SIM card. My SIM is there please Help

Hey i managed to use the odin software to load the gb firmware onto my phone but now when i tr to boot up the phone just hangs at the smasung logo. did i do something wrong or do i need to load something else onto the phone using odin?

lolgical said:
Hey i managed to use the odin software to load the gb firmware onto my phone but now when i tr to boot up the phone just hangs at the smasung logo. did i do something wrong or do i need to load something else onto the phone using odin?
Click to expand...
Click to collapse
Reboot into recovery and wipe cache and data.

[Solved] Stuck in Boot Loader

* I don't know enough to be messing with this, but here I am.
** My device is rooted, but I got into this mess by updating (device was working fine, did not use 3rd party software) and when it restarted after install it went to boot loader.
*** Device only turns on when its plug into wall outlit for 20 seconds. I can not get it to turn on with power button or when its plugged into laptop. Not sure if this is normal or not.
**** Something similar happened to this before but I just used twrp and fixed it. I can not flash a recovery unless my nexus is working normally.
***** Yes, I read other threads, on this forums and others, havnt found anything that has helped. I figured i could post specific details that other threads were lacking.
My nexus 10 is currently stuck in boot loader. If I select recovery mode, it does not switch to the smaller green android, that you can press down power, volume down/up and get into TWRP. Nothing I have done has gotten me anywhere except boot loader. I have tried to use Nexus Root Tool Kit and use the Flash Stock + Unroot and Flash Image to various partitions. No success. Today, downloaded Odin 3.07, but it crashed when file analysis in message box.
Im downloading SDK tools right now, but Im not quite sure what those are, will have to experiment.
See attached files please.
{
"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"
}
Image of recovery that I can not get to.
Current state of device. can not get anywhere else.
Close up of date.
Picture of odin failing. I tried to flash using the option called PDA by the way.
Picture of options Im trying to use on NRT. I also tired flash stock +unroot but no change to device.
solved - cant find where to set this thread to solved thought.
Any help is greatly appreciated.

Nyreb said:
* I don't know enough to be messing with this, but here I am.
** My device is rooted, but I got into this mess by updating (device was working fine, did not use 3rd party software) and when it restarted after install it went to boot loader.
*** Device only turns on when its plug into wall outlit for 20 seconds. I can not get it to turn on with power button or when its plugged into laptop. Not sure if this is normal or not.
**** Something similar happened to this before but I just used twrp and fixed it. I can not flash a recovery unless my nexus is working normally.
***** Yes, I read other threads, on this forums and others, havnt found anything that has helped. I figured i could post specific details that other threads were lacking.
My nexus 10 is currently stuck in boot loader. If I select recovery mode, it does not switch to the smaller green android, that you can press down power, volume down/up and get into TWRP. Nothing I have done has gotten me anywhere except boot loader. I have tried to use Nexus Root Tool Kit and use the Flash Stock + Unroot and Flash Image to various partitions. No success. Today, downloaded Odin 3.07, but it crashed when file analysis in message box.
Im downloading SDK tools right now, but Im not quite sure what those are, will have to experiment.
See attached files please.
View attachment 2637629
Image of recovery that I can not get to.
View attachment 2637596
Current state of device. can not get anywhere else.
View attachment 2637598
Close up of date.
View attachment 2637611
Picture of odin failing. I tried to flash using the option called PDA by the way.
View attachment 2637622
Picture of options Im trying to use on NRT. I also tired flash stock +unroot but no change to device.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Shoot me a email at [email protected]... We can talk more about your issues there..... Thx lj

Solution
Thanks to lj50036, my nexus now actually works.
Here's what he told me to do:
----------
1.) start here http://forum.xda-developers.com/showthread.php?t=2588979
This will install abd fastboot and the drivers for your tablet just follow instructions.
2.) Now open cmd as admin and type
fastboot
should see commands and options listed
3.) now type
cd /
this will move root to c drive.
4.) plug in tablet, boot into bootloader (holding down power, volume up and down I think) and type
fastboot devices
this output serial number of device and then type of device (Fastboot)
5.) go to https://developers.google.com/android/nexus/images#mantaray or google factory images and find Nexus 10. use what ever version you want. download, unzip and you should see something along the lines of this (the kot49h will be what ever version of the image you used.)
6,) move everything but the 2 .sh files to root of c drive (c:/)
and then in cmd prompt type
dir
this will print out file names, data, and other information of c:/. make sure you see the 3 files you moved from the factory image you unzipped.
7.) if so, make sure tablet is in bootloader still, and type
flash-all.bat in cmd prompt.
--About halfway through it reboots your nexus and because my nexus wont reboot its self, and will only come on when its plugged into wall outlet for a bit, I just did that and plugged in and it worked fine.
-- once the whole process runs, my nexus rebooted into recovery mode, and after a minute rebooted correctly and I was able to start setting up.
----------------
Thank you again to lj50036

@Nyreb
Change the forum name to include (SOLVED)

@lj50036
So I had mostly the same problem happen, except I tried to get into recovery to flash a CM11, but I was completely stock. It would get stuck on the screen below. I did what you said to do above and it still sticks at the same screen it did before, except sometimes it shows the Google logo before getting stuck. It used to just show the android on it's back right off the bat. Not sure what to do anymore.

spudsmac said:
@lj50036
So I had mostly the same problem happen, except I tried to get into recovery to flash a CM11, but I was completely stock. It would get stuck on the screen below. I did what you said to do above and it still sticks at the same screen it did before, except sometimes it shows the Google logo before getting stuck. It used to just show the android on it's back right off the bat. Not sure what to do anymore.
Click to expand...
Click to collapse
Shoot me a email.... Sounds like you need some help....

So I ended up emailing @lj50036 and we went back and forth and had to reflash everything, including custom recovery, TWRP. I think the recovery was messed up.
Finally works again!

spudsmac said:
So I ended up emailing @lj50036 and we went back and forth and had to reflash everything, including custom recovery, TWRP. I think the recovery was messed up.
Finally works again!
Click to expand...
Click to collapse
What happen in android some time, and I may be way off in left field here but, it has happened this way on the tf700, tf300, tf201, and the nexus 10... Just what I have help people with is that....
The storage no matter what command you issue in fastboot e.g
Code:
fastboot erase boot
fastboot erase system
fastboot -w
It just will not erase everything, and by doing these commands your really only telling the tab and or phone that you are going to be putting other
data in those partitions, so if you just flash exactly what was already on the tablet it does not like it...
@spudsmac had upgraded to 4.4.2 and was trying to install cm11 when things went wrong
So by us trying to reset the tablet to factory 4.4.2 firmware it would not take it... Just froze at android guy with x
So when, we went one version older on the firmware... Magic happened and he was golden....
Thx Josh

S10+ now stuck on soft brick / download mode / black screen

Hi all,
xda newbe here.
I got my s10+ yesterday so Ive decided to root it and flash with custom ROM - beyondrom v5,0
what has been done in chronological steps
1. phone with stock os / bootloader locked
2. dev mode on
3. bootloader open and grayed out in stock os
4. flashing / isntalling custom recovery - twrp via odin - success
5. flashing custom rom via twrp, used usb dongle with usb key
6. aroma installer pop up as expected - ive untick apps which i dont like
6.1. then in aroma instlaller got asked something like what geo should be allocated / list of countries
6.2. i choose UK unspecified (most likely i messed up here), im located in Slovakia, i think in aroma istaller it was eastern europe option
7. ive clicked next in installer, installation went complete, aroma log saved
8. phone turn off
9. now atempt to enter recovery mode - unsuccessful
10. device immidiately boot into download mode pic no1
10.1. there is error log on the top of display in red -
Recovery: Public key used tp sign data does not match key in chain partitin desctiptor. (5)
product: Error validating footer. (6)
CUSTOM RECOVERY
VBMETA G95FXXU1AS05, 23234098A
11. not able to turn it off
11.1. after couple of hours device turn off, baterry went empty
12. connect to pc - odin - sammobile latest s10+ soft for Slovakia / TMS as the phone its from tmobile - pics no2 and no3
12.1. success, flashed with stock rom, see pic no4
12.2. device immidiate restart - boot - bang donwload mode with error log in red
product: Error validating footer. (6)
CUSTOM RECOVERY
VBMETA G95FXXU3ASG8, 24948476R
13. turned off device, bixby + vol down + cable - device on, warning, vol up, download mode with long colorfull log, but there is a red log on the botton (nAsv_TABLE: 5 I EVT 1.1 ) pic no5
Current status -
not able to turn on the phone of course
device can be turn off by instruction on download mode screen
able to enter download mode
odin recognize device
pc recognize device
as i didnt find anything related to this status i created this thread and hopefully someone of you, xda overlords, will help. Im suspicious that even after stock rom flash there is still some gap in geo support and the device ... manufacturer hardware support vs slovakia tcom soft version. Maybe Im bullshitting myself. I dont want to kill device completely.
{
"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"
}
pls advice, many thanks, your noob bunkerr

Just flash the stock firmware using odin you should be ok.
After that reinstall root..and etc.

Player04 said:
Just flash the stock firmware using odin you should be ok.
After that reinstall root..and etc.[/QUOTE
- as you can read in point 12 Ive already did a stock rom reflash. It doesnt help, or did something wrong? the phone after success in odin turn off, and then force to download mode by it self, no way to turn on phone or entry recovery mode
pls advise, thanks
Click to expand...
Click to collapse

Oh i see you flash the wrong csc file. You have to get the correct firmware country.. for me its BRI csc, so i dl bri stock firmware and flash everything (bl, ap,cp and csc) with odin

bunkrra said:
Hi all,
xda newbe here.
I got my s10+ yesterday so Ive decided to root it and flash with custom ROM - beyondrom v5,0
what has been done in chronological steps
1. phone with stock os / bootloader locked
2. dev mode on
3. bootloader open and grayed out in stock os
4. flashing / isntalling custom recovery - twrp via odin - success
5. flashing custom rom via twrp, used usb dongle with usb key
6. aroma installer pop up as expected - ive untick apps which i dont like
6.1. then in aroma instlaller got asked something like what geo should be allocated / list of countries
6.2. i choose UK unspecified (most likely i messed up here), im located in Slovakia, i think in aroma istaller it was eastern europe option
7. ive clicked next in installer, installation went complete, aroma log saved
8. phone turn off
9. now atempt to enter recovery mode - unsuccessful
10. device immidiately boot into download mode pic no1
10.1. there is error log on the top of display in red -
Recovery: Public key used tp sign data does not match key in chain partitin desctiptor. (5)
product: Error validating footer. (6)
CUSTOM RECOVERY
VBMETA G95FXXU1AS05, 23234098A
11. not able to turn it off
11.1. after couple of hours device turn off, baterry went empty
12. connect to pc - odin - sammobile latest s10+ soft for Slovakia / TMS as the phone its from tmobile - pics no2 and no3
12.1. success, flashed with stock rom, see pic no4
12.2. device immidiate restart - boot - bang donwload mode with error log in red
product: Error validating footer. (6)
CUSTOM RECOVERY
VBMETA G95FXXU3ASG8, 24948476R
13. turned off device, bixby + vol down + cable - device on, warning, vol up, download mode with long colorfull log, but there is a red log on the botton (nAsv_TABLE: 5 I EVT 1.1 ) pic no5
Current status -
not able to turn on the phone of course
device can be turn off by instruction on download mode screen
able to enter download mode
odin recognize device
pc recognize device
as i didnt find anything related to this status i created this thread and hopefully someone of you, xda overlords, will help. Im suspicious that even after stock rom flash there is still some gap in geo support and the device ... manufacturer hardware support vs slovakia tcom soft version. Maybe Im bullshitting myself. I dont want to kill device completely.
pls advice, many thanks, your noob bunkerr
Click to expand...
Click to collapse
Flash whole firmware not only ap.

Samsung Galaxy Note 4 sm-n910f - does it already have an unlocked bootloader?

Hi, this is my first post.
My Device: Samsung Galaxy Note 4
Model Number: SM-N910F
Build: MMB29M.N910FXXS1DQFB
Version: N910FXXS1DQFB//N910fXXS1DQA3
Android Version: 6.0.1
Qualcomm Snapdragon 805 APQ8084
My first attempt flashing my note4 ended with a brick, now it works again, but i don't know what went wrong. I already activated developer options, but there is no "oem unlock". I read a lot on XDA Forum and it is emphasized that it is important to unlock OEM/bootloader in order to modify the device. I already know that some Note 4 devices have a locked bootloader and some don't, an i assume i haven't a locked bootloader on my device, but i'm not sure.
Can anyone confirm that my Note 4 has already an unlocked bootloader?

Older phones do not have OEM.

To verify if your bootloader is unlocked read these steps.

Open the Phone app or the Dialer.
Enter the code: *#*#7378423*#*#
This should automatically open a new window.
Tap the Service info.
Open Configuration.
You should see one of the two messages:
– Bootloader Unlocked Allowed – Yes
– Bootloader Unlocked – Yes

@Samarimama -thank you, but this doesn't work without sim-card i guess?

I'm sorry, but the code doesn't work with my sim card.

Ok, take off your SIM card and try it again.

I've tried with and without SIM card: "Invalid USSD-Code". Any other options?

Try with ADB​Check from Your PC​To check your bootloader status from your PC, you’ll need to use an ADB and fastboot tool. Until recently, you needed to download the full Software Development Kit (SDK) to get to ADB and fastboot. But now, you can get this lightweight tool separately.
Step 1: Setting Up the Command Prompt​When you install the tool, you should:
Locate the path to the ADB and fastboot folder.
Click on the Start Menu and type ‘cmd’ until the Command Prompt icon appears.
{
"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"
}
Type the path to the ADB and fastboot folder in your Command Prompt. For example:
C:UsersUsernameDownloadsADB and fastboot
Step 2: Turning on the Fastboot Mode​Once the Command Prompt is set, you should set your phone to fastboot mode. To do this:
Turn your Android phone off.
Hold the Volume Down and Power/Unlock buttons at the same time until the phone turns on again.
When it turns on, release the Power button, but hold the Volume Down key until you see the bootloader menu. It should display the little Android bot lying on its back on a dark background, with a text under it.
Connect the computer and your phone with a data cable.
Step 3: Checking the Status​Now that everything is set, you can use the Command Prompt to check the status of your bootloader. To do this, you should:
Enter the ‘./adb devices’ command into the Command Prompt to check if ADB can locate your device. This should list your phone.
Execute the ‘./adb bootloader’ command to boot into bootloader.
Once you are in the bootloader, type the ‘fastboot devices’ command in the Command Prompt and execute it. If it lists a code, that means that the system can detect your phone.
Enter the ‘fastboot oem device-info’ command and run it. It should list some device data, including the bootloader information.
Look for ‘Device Unlocked’ from the info.
If it says ‘true’ next to it, it means that your device is unlocked. If it says ‘false,’ it means that that it’s still locked.
Sometimes, you can see this information right away in the bootloader display of your Android phone.
​

I agree with @Samarimama . Bootloaders are usually not locked on older phones, and the option to unlock it can not be found in developer options. However, my understanding is that bootloaders could be locked on carrier tied phones, most often USA-based, but those versions are usually not F, but some other letters. Unsure about the version you have.
I do believe tho that you should try and first update the firmware on that phone, since that does not seem to be the latest version. N910FXXU12DRI2, is the latest one, i have worked with several CSC-versions of it, and have yet to encounter one with locked bootloader.
I also figure that it should not be possible to flash any custom binary on to a phone with a locked bootloader, you should just get error while trying. So if you managed to actually flash something on to your phone, it is unlikely that the bootloader on your phone is locked. Then it is rather a question of how you went about while flashing that resulted in bricking the device. And what you mean by "bricked".

It is why we need to unlock the bootloader to flash a ROM.

prkfsz said:
I agree with @Samarimama . Bootloaders are usually not locked on older phones, and the option to unlock it can not be found in developer options. However, my understanding is that bootloaders could be locked on carrier tied phones, most often USA-based, but those versions are usually not F, but some other letters. Unsure about the version you have.
I do believe tho that you should try and first update the firmware on that phone, since that does not seem to be the latest version. N910FXXU12DRI2, is the latest one, i have worked with several CSC-versions of it, and have yet to encounter one with locked bootloader.
I also figure that it should not be possible to flash any custom binary on to a phone with a locked bootloader, you should just get error while trying. So if you managed to actually flash something on to your phone, it is unlikely that the bootloader on your phone is locked. Then it is rather a question of how you went about while flashing that resulted in bricking the device. And what you mean by "bricked".
Click to expand...
Click to collapse
I got my Note 4 from a friend in Austria, but i live in Germany, so i made a reset and this is why i never knew there is a firmware update for my Note 4. I only use it in Germany, and after the reset i have N910FXXS1DQFB//N910fXXS1DQA3. Is it really neccessary to flash the newer austrian firmware? It's a bit confusing for me, excuse me for being so dumb.

Samarimama said:
Try with ADB​Check from Your PC​To check your bootloader status from your PC, you’ll need to use an ADB and fastboot tool. Until recently, you needed to download the full Software Development Kit (SDK) to get to ADB and fastboot. But now, you can get this lightweight tool separately.
Step 1: Setting Up the Command Prompt​When you install the tool, you should:
Locate the path to the ADB and fastboot folder.
Click on the Start Menu and type ‘cmd’ until the Command Prompt icon appears.
Type the path to the ADB and fastboot folder in your Command Prompt. For example:
C:UsersUsernameDownloadsADB and fastboot
Step 2: Turning on the Fastboot Mode​Once the Command Prompt is set, you should set your phone to fastboot mode. To do this:
Turn your Android phone off.
Hold the Volume Down and Power/Unlock buttons at the same time until the phone turns on again.
When it turns on, release the Power button, but hold the Volume Down key until you see the bootloader menu. It should display the little Android bot lying on its back on a dark background, with a text under it.
Connect the computer and your phone with a data cable.
Step 3: Checking the Status​Now that everything is set, you can use the Command Prompt to check the status of your bootloader. To do this, you should:
Enter the ‘./adb devices’ command into the Command Prompt to check if ADB can locate your device. This should list your phone.
Execute the ‘./adb bootloader’ command to boot into bootloader.
Once you are in the bootloader, type the ‘fastboot devices’ command in the Command Prompt and execute it. If it lists a code, that means that the system can detect your phone.
Enter the ‘fastboot oem device-info’ command and run it. It should list some device data, including the bootloader information.
Look for ‘Device Unlocked’ from the info.
If it says ‘true’ next to it, it means that your device is unlocked. If it says ‘false,’ it means that that it’s still locked.
Sometimes, you can see this information right away in the bootloader display of your Android phone.
​
Click to expand...
Click to collapse
ADB does not recognize my Note 4. Debugging mode is already acitivated.

Me too I have this problem with the same phone. My PCs do not recognize him

prkfsz said:
I also figure that it should not be possible to flash any custom binary on to a phone with a locked bootloader, you should just get error while trying. So if you managed to actually flash something on to your phone, it is unlikely that the bootloader on your phone is locked. Then it is rather a question of how you went about while flashing that resulted in bricking the device. And what you mean by "bricked".
Click to expand...
Click to collapse
I already had twrp on my phone and i simply panicked while flashing a rom. After that it had a permanent bootloop, after taking out batteries it was impossible to switch it on. It happened some years ago, i used recovery software, made a factory reset and it works. And I still want to install a system that is not as old as 2017. I have a lot of patience, and i will find a way - if the bootloader is unlocked. Therefore i try to figure out if Note 4 has a locked bootloader or not. You say, Note 4 is that old, it hasn't any, and because twrp was on the phone already, it is unlocked. Then it seems to be a waste of time to try to use ADB to be sure. Instead i could try to flash it right now and don't care about unlocking something that doesn't exist on Note 4.

If you can go to TWRP, install the ROM you want with your phone and flash it with Gapps.

Old Lady said:
I got my Note 4 from a friend in Austria, but i live in Germany, so i made a reset and this is why i never knew there is a firmware update for my Note 4. I only use it in Germany, and after the reset i have N910FXXS1DQFB//N910fXXS1DQA3. Is it really neccessary to flash the newer austrian firmware? It's a bit confusing for me, excuse me for being so dumb
Click to expand...
Click to collapse
You're not dumb for not knowing something.. ;-)
It's hard to say if updating is totally necessary but it's almost always recommended to update your phone to the latest firmware before flashing custom ROMs. And I would say, especially since the last made firmware seems to have been made more that a year after the firmware you actually have on your phone I would strongly recommend updating to the latest firmware. It's not difficult, you go to settings and find where you choose to update and let the phone find the latest update itself while being connected to internet.
After that, if you already have TWRP installed, which I understand you do, just try and flash the custom ROM you want. But please remember to before that back up everything you want to save from the phone. And also make a twrp backup of the phone so you can restore it if something goes wrong. And read the suggested flashing procedure several times before actually doing it so you are familiar with it. If something goes wrong go to twrp and restore it from there.

Old Lady said:
I already had twrp on my phone and i simply panicked while flashing a rom. After that it had a permanent bootloop, after taking out batteries it was impossible to switch it on. It happened some years ago, i used recovery software, made a factory reset and it works. And I still want to install a system that is not as old as 2017. I have a lot of patience, and i will find a way - if the bootloader is unlocked. Therefore i try to figure out if Note 4 has a locked bootloader or not. You say, Note 4 is that old, it hasn't any, and because twrp was on the phone already, it is unlocked. Then it seems to be a waste of time to try to use ADB to be sure. Instead i could try to flash it right now and don't care about unlocking something that doesn't exist on Note 4.
Click to expand...
Click to collapse
What do you mean "panicked while flashing a ROM"? What did you do while flashing?

It is not a serious problem.

prkfsz said:
What do you mean "panicked while flashing a ROM"? What did you do while flashing?
Click to expand...
Click to collapse
Phone showed a litte red android while flashing but nothing seemed to happen for a long time, so i disconnected phone and pc. After that my phone didn't work anymore, now everthing is fine and soon i will try it once more - without disconnecting.