Database Users

HEIMDALL bricked my phone

Hi,
I just tried this command on my i9000
heimdall dump --chip-type NAND --chip-id 0 --output ttt1
It bricked my phone. I thought this was going to be a read only function, but it seems to have written something bad to my phone.
It is displaying the phone ! computer picture.
The computer does not see a usb device when the phone is connected and download mode is not reachable.

You should use a USB JIG to get into Download Mode again and reflash a stock rom with Odin/Heimdall!
Sent from my SGS with Simply 3.0 RC2 ROM

midas5 said:
Hi,
I just tried this command on my i9000
heimdall dump --chip-type NAND --chip-id 0 --output ttt1
It bricked my phone. I thought this was going to be a read only function, but it seems to have written something bad to my phone.
It is displaying the phone ! computer picture.
The computer does not see a usb device when the phone is connected and download mode is not reachable.
Click to expand...
Click to collapse
Take the battery out for 10 min. and place it back, see then if the phone can be started.

midas5 said:
Hi,
I just tried this command on my i9000
heimdall dump --chip-type NAND --chip-id 0 --output ttt1
It bricked my phone. I thought this was going to be a read only function, but it seems to have written something bad to my phone.
It is displaying the phone ! computer picture.
The computer does not see a usb device when the phone is connected and download mode is not reachable.
Click to expand...
Click to collapse
Dumping doesn't work unfortunately. As far as I know I haven't implemented anything incorrectly as Odin fails as well. I think the secondary boot loader on the device just can't dump properly. There is a note about this if you run "heimdall --help".
The operation is essentially read-only except for a flag that the secondary bootloader sets when you start an operation. The flag is unset when the operation finishes succesfully but the problem is when attempting to dump the phone eventually stops responding. So to fix this you need to put your device in download mode, possibly with a custom jig, then run "heimdall close-pc-screen". This command will just unset the flag so that your phone is able to boot normally, no personal data will be lost.

Benjamin Dobell,
Thank you very much. All is not lost then.
I just have to wait for the cable I just ordered off ebay to arrive so that I can turn it into a jig.
How about a feature request for the heimdall code.
Add into the help text on heimdall that
"Note: dump can brick your phone, so have a 301k jig ready before your try it."

Benjamin Dobell,
I used the jig as you directed, and it worked. I have my phone back with all its contents.
Thank you

midas5 said:
Benjamin Dobell,
I used the jig as you directed, and it worked. I have my phone back with all its contents.
Thank you
Click to expand...
Click to collapse
Great to hear. I'll also include a better warning in the next update, whenever I finally get the time to finish it

Galaxy S5 G900M Pit file don't work

Hello Guys,
I'm in trouble with a G900M device, after a OTA update, it stay in bootloop, but i cannot enter in a recover mode, when i try flash any room in Odin (various versions) don't work and i receive a message on the screen:
" ODIN: flash read failure"
" ERROR: there is no a pit binary"
"SECURE CHECK FAIL : PIT"
" ODIN: flash read failure"
i have tryied to flash de pit file from this forum, and another in the internet, bot i had the same message.
can anyone help me ?
Thx.

The messages you are getting would indicate this is Odin not communicating with the device, so it's probably a PC end problem....
There is a basic checklist for odin flashing, the chances are you are probably doing everything correctly, but it won't hurt to make sure....
1) which version of Odin are you using. (3.10.7 is usually the best for the S5)
2) do you have the Samsung USB drivers installed on your PC. (You will get them when you install Kies)
3) Which version of Windows are you using. (From Windows Vista onwards you need to run Odin as administrator and Odin has had problems with Windows 8)
4) Do you have firewalls/antivirus disabled.
5) have you killed all Kies processes in task manager. (Kies interferes with Odin)
6) Are you using a primary USB socket on the pc. (A USB socket connected directly to the motherboard instead of one that runs through a 'hub')
7) are you using an official Samsung USB cable. (Other, cheaper, non branded cables are known to cause issues)
http://i.imgur.com/rVnFwJM.jpg

i've tryed to flash again whit Samsung USB 3.0 cable, and have the same trouble, i'm using windows 10, and have tested much versions for odin.

What about Kies? Have you installed it? It will give you the latest USB drivers.....
Also I'm wondering if you using Windows 10 is the problem.....it's a new OS and I'm not sure if Odin is 100% compatible yet.
If you have access to an older pc it could be worth giving it a try on that.....
I have an old XP laptop that I use whenever I flash a device......I refuse to get rid of it....lol
http://i.imgur.com/rVnFwJM.jpg

i'd installed Kies, samsung smart, drivers around internet forums and nothing, (i uninstall each item rsrs)
now i have tested at windows XP computer and odin return it:
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Device screen returns:
" ODIN: flash read failure"
" ERROR: there is no a pit binary"
" SECURE CHECK FAIL : PIT"
" ODIN: flash read failure"
using two different cables (a xperia Z2 cable and 3.0 usb for samung S5 )
no longer know what to do...

My S5 is dead?

lombardy said:
My S5 is dead?
Click to expand...
Click to collapse
You can use Kies Firmware Recover instead of flash via Odin.

kies returns the same error at device screen, i'm now thinking for the trouble is in logicboard.

Sorry fella, I'm pretty much out of ideas if you want to remain stock.....I know of a website where you can get engineer or repair firmwares for the S5.....but I've already checked and they don't do one for the M variant. I don't suppose there's any way you can take it to a service centre is there?......
Have you thought about trying out a custom rom setup?
http://i.imgur.com/rVnFwJM.jpg

SM-G900F bricked (?) water damaged - can get into download mode

Felt slight stupid as I saw my s5 going round the washing machine, thought I'd have a play after it's dried out.... I like learning but don't really know phones.
It was encrypted but was stock firmware.
Currently:
- It powers on
- I can get to the download in boot ok (vol. down)
- It resets when trying to get into recovery mode
- Kies see's something trying to connect but times out. Heimdall detects it but throws errors upon trying to flash , I'm yet to try Odin, just getting stock firmware as I write this.
(Heimdall error - libusbx: error [winusbx_submit_bulk_transfer] ReadPipe/WritePipe failed: [22] Th
e device does not recognize the command.)
I've got some more playing around to do but it feels like, at least, the storage is screwed but that's a complete guess.
1) I was hoping someone would know if it's worth playing further?
2) Whether anyone could take a guess of whether replacing the mother/logic board would be a *possible* fix
3) Could anyone point me to any resources explaining the how the phone works- I'm initially trying to understand what components sit on the logic board and the boot sequence. e.g. could the CPU/ storage be fried but it still boot this far?
Many thanks in advance for any help.

OK, I'm a little further along with this now.
I'm using various versions of odin (3.0.7,9,12.3). Various computers (all windows 10 now but did try heimdal on a 2 nix machines) and a whole lot of leads. Just getting Odin to recognise the phone was fun.
Tried using the AP part to install the BTU UK version of firmware from sammobile
Tried getting the hidden .img.tar from it and flashing that
Tried flashing a twrp recovery
But all come up with
Code:
GetPIT for Mapping
There is no PIT Partition
So I got a couple of Pit files for and tried them with the Re-partition ticked
Code:
Set PIT file...
DO NOT TURN OFF TARGET!!
Complete (Write) Operation failed
OSM All threads completed (succed 0/ failed 1)
So a few questions:
1) How do I uploda photos here? Or do they have to be inserted links. May be my low post count? Or I'm blind
2) Is it normal that odin stops recognising the phone the moment there's an error like the one's I'm having. Odin's ID:COM part goes blank and I have to remove/ insert the USB again.
I just want to check that's not some other reason.
3) Is there anyway to test whether the NAND's working/ can be accessed without pressing that scary NAND erase all button?
Many thanks

Why not just get it fixed from service center?

beardedfool said:
OK, I'm a little further along with this now.
I'm using various versions of odin (3.0.7,9,12.3). Various computers (all windows 10 now but did try heimdal on a 2 nix machines) and a whole lot of leads. Just getting Odin to recognise the phone was fun.
Tried using the AP part to install the BTU UK version of firmware from sammobile
Tried getting the hidden .img.tar from it and flashing that
Tried flashing a twrp recovery
But all come up with
Code:
GetPIT for Mapping
There is no PIT Partition
So I got a couple of Pit files for and tried them with the Re-partition ticked
Code:
Set PIT file...
DO NOT TURN OFF TARGET!!
Complete (Write) Operation failed
OSM All threads completed (succed 0/ failed 1)
So a few questions:
1) How do I uploda photos here? Or do they have to be inserted links. May be my low post count? Or I'm blind
2) Is it normal that odin stops recognising the phone the moment there's an error like the one's I'm having. Odin's ID:COM part goes blank and I have to remove/ insert the USB again.
I just want to check that's not some other reason.
3) Is there anyway to test whether the NAND's working/ can be accessed without pressing that scary NAND erase all button?
Many thanks
Click to expand...
Click to collapse
Yeah that sounds like water damage alright. I'm sorry to tell you it sounds like your NAND is semi-corrupted in that part of the BL seems to have survived but basically everything else is kaput.
If the PIT partition is missing that is a flag right there to a likely NAND corruption.
Sorry to be the one to have to tell you this but at this point you're best bet is to take it as a total loss and try to sell any undamaged parts (ex. Digitizer, LCD) to raise the cash for a new phone.

Help to restore bootloader on Nokia 6

Help to restore bootloader on Nokia 6

What happened? We are no magicians

ZeroPointMax said:
What happened? We are no magicians
Click to expand...
Click to collapse
The phone worked properly, but I wanted to install the European firmware, through the program QFIL I installed the firmware in the phone, and after that the phone does not turn on, or rather all the LEDs light up and the computer determines how Port Diagnostics 900E? I ported the drivers all without result. can not enter mode Downalds mod ...

Evgeny_14 said:
The phone worked properly, but I wanted to install the European firmware, through the program QFIL I installed the firmware in the phone, and after that the phone does not turn on, or rather all the LEDs light up and the computer determines how Port Diagnostics 900E? I ported the drivers all without result. can not enter mode Downalds mod ...
Click to expand...
Click to collapse
Oops, you bricked your device. You cannot flash another region if that was your intention... You can either go to customer support or try to make a USB flash cable to force the files onto your device (pls use original firmware for your device). I know that this was mentioned in the forum before but I cannot remember where exactly and I don't know if it is actually working. If it fails, your device is pretty much ******...

Just use the OST Tools and official firmware to root ur device.
Tutorial video:
OST Tools and firmware download: https://forum.xda-developers.com/nokia-6/development/nokia-6-official-firmware-mena-region-t3664441
Recovery download: https://forum.xda-developers.com/no...ecovery-project-nokia-6-t3650499/post73625011
Guide: https://forum.xda-developers.com/no...de-how-to-flash-custom-recovery-root-t3702354

Nokia 6 (TA-1003) bootloader restore how?
Dear,
My phone will not start up
How can i restore the bootloader an reflash the firmware?
I hope on a solution!
Greet,
Marno

desesperated
richardpimenov2001 said:
Just use the OST Tools and official firmware to root ur device.
Tutorial video:
OST Tools and firmware download: https://forum.xda-developers.com/nokia-6/development/nokia-6-official-firmware-mena-region-t3664441
Recovery download: https://forum.xda-developers.com/no...ecovery-project-nokia-6-t3650499/post73625011
Guide: https://forum.xda-developers.com/no...de-how-to-flash-custom-recovery-root-t3702354
Click to expand...
Click to collapse
Hi there. I'm a new user so i don't have enought privileges to make a tread about my issues. So i will try to be the most clear possible.
I got a Nokia 6 TA-1039 so i tryed to root it and that's why I'm here.
First of all the phone is now on Qualcomm HS-USB Qloader singed on 04/01/2013 and it's 2.1.0.5 version, by Xiaomi Technology Inc., then when i connect to the PC it recognizes it in that port. In the other hand, the device doesn't make any noise or dispolay anything on the screen, but in the pc it appears when i connect it.
I have downloaded following the treads the firmware Nokia_TA-1025_MSM8937_25082017_7.1.1.zip and extracted it. I was trying to use it with QFIL version 2.0.0.5 and using as configuration the next steps:
-Download protocol: 0-Sahara
-Device type: UFS
Validation mode: 0-No validation
[
then when i run it i found the next errors:
Error function: Sahara _rx_data: 194 unable to read packet header Only read 0 bytes
Error function: Sahara_main: 854 sahara protocol error
Error function: Sahara_main: 265 Uploading image using sahara protocol failed
Download fail: Sahara fail: QSaharaServer fail: Process fail
Then i tryed to flash it using Xiaomi MiFlash.exe and the errors are:
Cant found programmer file
Cannot recive Hello packet
cannot read hello packet
adittional to this I have a cable that i think that it's a EDL cable by GPGIndustries like this
http://shop.gpgindustries.com/produc...ml?pb=108&pc=2
I'm very desesperated about this. If someone can call me or help me in any way i really appreciate it.

grandroid7 said:
Dear,
My phone will not start up
How can i restore the bootloader an reflash the firmware?
I hope on a solution!
Greet,
Marno
Click to expand...
Click to collapse
I had exactly the same thing. . You must send the phone to the service.

Maxpowers88 said:
Hi there. I'm a new user so i don't have enought privileges to make a tread about my issues. So i will try to be the most clear possible.
I got a Nokia 6 TA-1039 so i tryed to root it and that's why I'm here.
First of all the phone is now on Qualcomm HS-USB Qloader singed on 04/01/2013 and it's 2.1.0.5 version, by Xiaomi Technology Inc., then when i connect to the PC it recognizes it in that port. In the other hand, the device doesn't make any noise or dispolay anything on the screen, but in the pc it appears when i connect it.
I have downloaded following the treads the firmware Nokia_TA-1025_MSM8937_25082017_7.1.1.zip and extracted it. I was trying to use it with QFIL version 2.0.0.5 and using as configuration the next steps:
-Download protocol: 0-Sahara
-Device type: UFS
Validation mode: 0-No validation
[
then when i run it i found the next errors:
Error function: Sahara _rx_data: 194 unable to read packet header Only read 0 bytes
Error function: Sahara_main: 854 sahara protocol error
Error function: Sahara_main: 265 Uploading image using sahara protocol failed
Download fail: Sahara fail: QSaharaServer fail: Process fail
Then i tryed to flash it using Xiaomi MiFlash.exe and the errors are:
Cant found programmer file
Cannot recive Hello packet
cannot read hello packet
adittional to this I have a cable that i think that it's a EDL cable by GPGIndustries like this
http://shop.gpgindustries.com/produc...ml?pb=108&pc=2
I'm very desesperated about this. If someone can call me or help me in any way i really appreciate it.
Click to expand...
Click to collapse
I dont know if this would help you guys or not but this is portable one,
You dont need to configure any sahara file or anything, just select mbn file then xml and hit download
This tool helped me alot for so many other phone which gave me sahara error
Find the tool in the attachment
Hope this will help you
Hit thanks button if you find this helpful
Happy flashing
jurek09 said:
I had exactly the same thing. . You must send the phone to the service.
Click to expand...
Click to collapse

Test Device and aboot -2???

Ok so the phone i have is/was actually a G935T, and had G935T firmware (BRC1) even though it says G935A on the board inside the phone. I tried to flash a different firmware, foolishly without turning off FRP, or turning on OEM, yeah im dumb. I ended up being stuck with the SBL error upload mode and couldnt even get back to download mode no matter how many times i tried, eventually i learned about EDL mode and took the phone apart and shorted the TP and re programmed the phone etc. and got it back to download mode.
Everything i flashed would always be successful in Odin, however nothing would ever boot past the looping S7 edge boot screen and recovery on every single firmware would also loop and ultimately give me kernel panic errors. i began to suspect that maybe i left something unplugged inside so i took it apart again and tried to keep the heat shield pressed down a bit more (since i had to open it up to access the test point) as i assembled the phone back together. No more kernel panics, but the boot looping was still present. I have tried G935T, A, P, V and U firmware and all of them do the same thing. Ive used the proper PIT files.
To make things worse, i flashed Oreo without realizing that i was putting my bootloader in handcuffs. To make things even MORE worse, i used a tool which claimed to convert an odin archive to be ADB enabled. now my device boots and says S7 edge etc, but then immediately goes to SBL error upload mode. Recovery still loops. Whats interesting though, is that since i used the converted archive, my device says exactly this in download mode:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G935A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: ON
WARRANTY VOID: 0xffffffff (0x0)
QUALCOMM SECUREBOOT: ENABLE fffffffe
RP SWREV: B-2 (-2, -2, -2, -2, -2) K8 S8
RP SWREV: TEST DEVICE
SECURE DOWNLOAD: ENABLE
IDDQ: G(25), S(7) mA
CPU SERIAL NUM : 0X1b9cea13
Fused open loop voltage: 1030mv
RPMB PROVISIONED
Any help would be much appreciated. Its going on nearly a month now trying to get this thing to work. I dont care about warranty, i dont care about knox i just want my phone to work....i cannot find any information about test device, how to go back to system status official or how to properly reformat all partitions that effect FRP or whatever the hell is locking me out of it. Also i am now not even able to flash ANY firmware because it keeps failing saying something about aboot fused -2 and none of the firmware i have will successfully flash. Im stumped.

I called a repair shop today and they want to charge me $30.00 to flash it with what they have. That seems a bit high to be honest. Should only take about 10 minutes right?

How to change Fuse -2 -> 1
Elem3nt0 said:
I called a repair shop today and they want to charge me $30.00 to flash it with what they have. That seems a bit high to be honest. Should only take about 10 minutes right?
Click to expand...
Click to collapse
Fuse -2 happened to my T380 Tab A tablet when I flashed wrong aboot and boot in the same TAR package.
So steps to fix it:
find the right combination firmware;
unzip it with 7zip archiver;
download TAR_MD5_PACKAGER;
open folder with unzipped comb_firmware and delete all files below from it:
-aboot,
-apdp,
-boot,
-devcfg,
-msadp,
-rpm,
-sbl1,
-tz.
copy all files what left to TAR_MD5_PACKAGER\parts;
start TAR_MD5_PACKAGER and press 1 to make tar file;
flash this file with Odin as AP;
now the fuse should switch to 1;
next flash the full combination file or stock firmware.
FUSE Number stands for software version,
samsung has protection against downgrading software,
So once you flashed firmware with number 2 in it, the device will change the fuse to 2 and after that
you will not able to flash anything less than with number 2 and so on.

S7 edge up and running
Dude thanks a lot!!! I read through multiple threads. Some more technical than others but this one was plain simple and it worked. Some of the files I deleted were a bit different, but hey, it got bit to work. One other thing for anyone experiencing the same issue, just look for a combination file matching your phones actual bootloader. Once you find it, just start deleting the files Odin is indicating are not letting the flash complete. In my case, files: hyp.mbn, pmic.elf, emmc_appsboot.mbn, xbl.elf. once I deleted those files I was golden. :laugh::laugh::laugh:

HI
I have smiliar problem.
I have a problem with a friend's phone. they give S7 Edge to the service because he have problem witch turn on telephone
When he received the phone displays an error: "An error has occured while updating software.. Use the Emergency recovery function in the Smart Switch PC"
Smart Swhitch doesn't recognized the phone
I try update firmware with odin but when i flashing i have error: SV rev. check fail(bootloader) Device: -1 Binary: 6
I try to insert TWRP and i have next error: Custom binary (recovery) blocked By FAP lock
I can not insert custom recovery witch TWRP, and I don't have any idea what official rom was uploaded last time :/
Sorry for my English :/