Related
I broke my phone (radio rom) while trying to flash my dear Samsung Omnia i900 using GrandPrix. The full story can be found here: http://forum.xda-developers.com/showthread.php?t=418917
Here is the latest help I receive from chaimd:
The other way, I found strings of "phone.bin" or "SD download Mode" in eboot.bin.
I think you can try below;
1. copy i900DXHG4_phone.bin into a microSD as "phone.bin"
2. set the microSD and power on your OMNIA
you can try with microSD format FAT16 or FAT32.
And perhaps, entering SD download Mode need some key combination with POWER key.
Good Luck
Click to expand...
Click to collapse
I will try this out. Does anyone know how to enter the SD download mode?
10x for this
i try format fat 32 sd card i copy phone.bin and try some key combinations my omnia power buton light blu green and red but noting.How to setup in menu my phone boot whit mmc?
this is help as?
To boot from a program, create a folder entitled "MCSTART" which contain a programme call "AUTORUN.EXE". When you insert card, windows will copy executable and launch it with parameter "install" (and when you remove it, windows relaunch app with "unsinstall parameter")
So maybe you can create an executable that launch ROM update
NO you do not need autorun, bootloader should exevute the flash from SD but i am unaware of the key combination
Bootloader
mr_tormoz said:
i try format fat 32 sd card i copy phone.bin and try some key combinations my omnia power buton light blu green and red but noting.How to setup in menu my phone boot whit mmc?
Click to expand...
Click to collapse
Me too, I tried to press alot of key combinations but no help at all.
I found out the SD Download Mode is actually one of the Bootloader mode. Therefore if you know how to enter Bootloader Mode then please share it here. Thanks.
binh said:
Me too, I tried to press alot of key combinations but no help at all.
I found out the SD Download Mode is actually one of the Bootloader mode. Therefore if you know how to enter Bootloader Mode then please share it here. Thanks.
Click to expand...
Click to collapse
Thats were there is a little problem in the Omnia the boot loader mode is automatic. When your device starts up and you see the Samsung Omnia logo this is bootloader mode. If no request is made to to the system to enter bootloader the normal startup proceeds. This is why when you flash from Grandprix you have to press detect first then restart. The detect sends a command to go into bootloader mode.
bobsbbq said:
Thats were there is a little problem in the Omnia the boot loader mode is automatic. When your device starts up and you see the Samsung Omnia logo this is bootloader mode. If no request is made to to the system to enter bootloader the normal startup proceeds. This is why when you flash from Grandprix you have to press detect first then restart. The detect sends a command to go into bootloader mode.
Click to expand...
Click to collapse
That's why I think the solution to Samsung Omnia i900 SD Download Mode is to find a program that will activate it from Windows.
Anyone have better idea?
hello
My omnia is 5 days in service center but not alive. any progress for repair the phone part ? i have 2 x i900 one is work and one only pda i try metod phone to phone but not work.
I have the same problem. I tried to download HH1 rom, i followed the steps and the procedure went successfuly with any error, screen say job done. then my phone wont power on again.
will the SD download mode work if the phone won't even turn on? how to make it turn on? how to use the SD download mode? can anybody give exactly direction? please help.
My omnia original english rom working if can help with something to ressurect yours tell me.
anybody have more details of i900 SD Download Mode and how to use it?
will it recover the bricked phone? my phone wont power on now.
So, does anyone have idea?
Hmmm. Yesterday I kill 2 pcs I900 Omnia with GrandPrix 1.8.1 trying to flash with HH1 version (only PDA part), but after that I flash them with old version (HG3), and everything looks ok. I think if You do not kill the boot sector, you should bring your phone to live. And one more. NEVER try to flash bootloader in phones like this, because there is no solution to restore it!! It's this same problem like qualcomm phone series. No TestPoint, no solution, at now.
how can you flash it again it the power cant turn on? the main problem now is the power cant turn on. any ideas?
prpetrov said:
My omnia original english rom working if can help with something to ressurect yours tell me.
Click to expand...
Click to collapse
Thanks prpetrov, your kind heart is really appreciated especially when someone like me really need help.
We, the people who has half-bricked phone (no phone function) really need to know how to enter the SD Download Mode with or without using software.
People on this forum make me feel really welcome. Thank you all.
samsung service center
binh said:
Thanks prpetrov, your kind heart is really appreciated especially when someone like me really need help.
We, the people who has half-bricked phone (no phone function) really need to know how to enter the SD Download Mode with or without using software.
People on this forum make me feel really welcome. Thank you all.
Click to expand...
Click to collapse
I think there is no solution to our bricked omnia's but to send them to Samsung Service centers. If warranty covers it, it will cost $150 or so for shipping. Losing $150 is better than $700. Once I get it fixed, I will sell mine and won't get it again. If a firmware update caused this issue, I cannot rely it as the device of my choice. I have not even used any tricky methods, just tried to update with its firmware and now in Monahan's. Sucks big time.
I contacted samsung US. they told me they will only support handsets manufactured in US. I also contacted samsung singapore,they told me that there is no warranty on exported handsets. warranty is only availiable to handsets purchased from local stored in asia countries. all handsets purchased online from europe, US, do not have warranty, so samsung will not support those.
I am so disappointed with samsung. there are people all round the world purchase products from ebay and online stores, samsung do not provide services for them. this is a big problem.
I will say, can we all complain to Samsung? may be see some light? may be i am too silly.... If we don't try... we do not know the answer; Right?
source : http://www.modaco.com/
OK, here is time for report what I've done so far.
Firstly, THERE IS a function to download from SD card, but at this moment, there is only 1 way to activate this function, have to be done through telnet from JTAG.
People have MONAHANS is problem with PDA bootloader (PXA312) , then PHONE problem is related to Qualcomm bootloader.
Secondly, there is some functions that I tried on PXA312
sys.cpu PXA310
sys.JtagClock 10MHz
sys.option WAITRESET On
sys.up
data.set 0x40e10414 %long 0x00001841
after this, it will bring you control of MONAHANS
Something important here:
d.s 0x4A00000C %l 0x00000638 ; MSC1 (Static Memory Control Register - SRAM/Async Flash memory)
d.s 0x4A0000A0 %l 0x00000002 ; CSMSADRCFG(CS Config Register)
d.s 0x4A000088 %l 0x0033C919 ; CSADRCFG2(CS Address Config Register) set SCLK cycles address bits and 16 bit device
Any info?
vivi
So I intstalled the WP10 preview which includes support for the 520, but the settings app didn't work and I couldn't reset the device so I used the Windows Phone Recovery Tool to revert to 8.1. However, as the firmware was about to install, the device went into flash mode (as it does while installing a firmware) and an error dialgue opened on my laptop saying that there was an error. After that my phone's screen went black and its not vibrating or powering on even when connected to a power source. I doubt that it is restorable, but any help would be much appreciated
Thank you guys for letting me know about the link I'm posting it in the OP so that everyone having this issue can upvote on that thread.
Link: https://social.technet.microsoft.co...e-recovery-possible?forum=WinPreview2015Phone
theevilpotato said:
So I intstalled the WP10 preview which includes support for the 520, but the settings app didn't work and I couldn't reset the device so I used the Windows Phone Recovery Tool to revert to 8.1. However, as the firmware was about to install, the device went into flash mode (as it does while installing a firmware) and an error dialgue opened on my laptop saying that there was an error. After that my phone's screen went black and its not vibrating or powering on even when connected to a power source. I doubt that it is restorable, but any help would be much appreciated.
Click to expand...
Click to collapse
I've just got the exact same error and I've spent the last hours trying everything possible and every tutorial to make it work. I'm afraid it's completely bricked. It's not responding to anything, when plugged into the pc it shows up as "QHSUSB_DLOAD" which is usually a very bad sign, and every software recovery or phone recovery tool I've tried from MS and Nokia either don't detect it or say it's not supported.
It's dead.
520? :/ Same here. Time to get a new phone for school, I guess.
Yes, a 520 as well.
Just a heads up, if you give the windows phone subreddit a quick read you'll notice we are not the only people to have this issue. Apparently several other people trying to roll back their phone have it completely bricked and in the QHSUSB_DLOAD situation.
I don't think MS can do anything about it, since the boot crapped out you either need to buy the tools or get it repaired by someone having them, but at least it proves there is some kind of problem with rolling back from the preview.
angstdasein said:
I've just got the exact same error and I've spent the last hours trying everything possible and every tutorial to make it work. I'm afraid it's completely bricked. It's not responding to anything, when plugged into the pc it shows up as "QHSUSB_DLOAD" which is usually a very bad sign, and every software recovery or phone recovery tool I've tried from MS and Nokia either don't detect it or say it's not supported.
It's dead.
Click to expand...
Click to collapse
same here
After a bit of reading more and more people are reporting this, so please put your own experience on this technet thread, it's a good idea to centralize reports where Microsoft can see it.
I can't link it here (don't have the permission to post links yet) but it's the first result by typing "Lumia 620 bricked during rollback procedure: recovery possible?" in google.
NL525 w/ red screen here.
feherneoh, pls make tutor!
feherneoh said:
Here it is:
...
Click to expand...
Click to collapse
Praise the Lord feherneoh!
Greatest thanx to ya!
Same error here, black screen and phone do nothing.
Tried with Thor2 but didn't work.
azogh said:
Same error here, black screen and phone do nothing.
Tried with Thor2 but didn't work.
Click to expand...
Click to collapse
Be sure using good cable. Try few times (i did 3)
[QRCODE][/QRCODE]The same problem with L520. There is already post on Technet regarding this problem
You can search Google by typing in: QHSUSB_DLOAD technet
Please upvote, then we would have some respond from Microsoft, maybe alternative driver, tool or something...
My Nokia does not turn on
The same problem! My Nokia does not turn on. I've tried everything! Any solution?
rickmaran said:
The same problem! My Nokia does not turn on. I've tried everything! Any solution?
Click to expand...
Click to collapse
I don't think there is a solution yet. Just keep and eye on this and hope for the best: https://social.technet.microsoft.co...e-recovery-possible?forum=WinPreview2015Phone
Have you anyone has try using Lumia Recovery Tool ?
1. Download ffu saperatly. (8.1 GDR1)
2. Install Lumia Software Recovery Tool.
3. Launch recovery tool.
4. Remove battery, usb, device.
5. Select my phone doesn't respond in recovery tool.
6. Insert battery, usb, plug it to pc.
7. A- Press and hold volume down.
B- Press and hold Power + volume down
8. Flash it.
Hope this will work.
feherneoh said:
Here it is:
1: Find your Recovery Tool folder on your harddisk. Mine is "C:\Program Files (x86)\Microsoft Care Suite\Windows Phone Recovery Tool"
There should be a file called thor2.exe there.
2: Open an administrator command prompt here
3: Find the ROM Recovery Tool downloaded. Should be in "C:\ProgramData\Microsoft\Packages\Products"
You will need the FFU file for your device.
Mine is "C:\ProgramData\Microsoft\Packages\Products\rm-914\RM914_3058.50000.1425.0005_RETAIL_eu_hungary_429_05_443088_prd_signed.ffu"
4: To flash your device with THOR2, enter this to commandline:
Code:
thor2 -mode uefiflash -ffufile "C:\ProgramData\Microsoft\Packages\Products\rm-914\RM914_3058.50000.1425.0005_RETAIL_eu_hungary_429_05_443088_prd_signed.ffu"
Replace filename with your own
5: After flashing completes, reboot your phone by entering this:
Code:
thor2 -mode rnd -bootnormalmode
Click to expand...
Click to collapse
It says this error:
THOR2 1.8.2.14 exited with error code 393220 <0x60004>
Click to expand...
Click to collapse
zuchit said:
It says this error:
Click to expand...
Click to collapse
Same case
Same problem with DLOAD
The solution seems to do a JTAG... Bad news for normal people ::crying:
Bricked Nokia Lumia
Actually, the red screen means that the phone went into its UEFI MODE.
In UEFI MODE your phone could be restored as normal by a HARD RESET (see key combo).
If you have a hard luck, your phone will automatically start in Flashing Mode (IMO(0x0000001)) which only works on the downloading procedure when on Rolling back.
The RollBack program has to put your phone in Flashing Mode in order to gain access to it's microchip.
Well the app itself knows what to do, but something failed.
In this point, you disconnected the phone and tried all you've known to power it on. Meanwhile the app deleted it's cache file, it no longer knows why your phone is in that state and your PC will get it as QHSUSB_DLOAD which is a Side_Load driver for Qualcomm Enabled Phones.
At this point, RIFF JTAG is the only solution as your BOOTLOADER is dead.
Good thing? It could be fixed by any GSM Service and the price could be small.
DO NOT try any Nokia Care / Refurbish / Restore app. All of them are created to work with a phone that has it's bootloader working.
None of them will cooperate to reflash it.
Even if you manage to reflash the OS, you don't have a BIOS / BootLoader....
Hopefully, Microsoft will create a tool to fix this as it only occurs when Rolling Back from Windows 10 Tech. Prev. and 8.1 to 8.
But until that, your phone is dead.
Source of info: I'm working as an G.S.M. RepairMan.
feherneoh said:
Maybe some error message before this?
Click to expand...
Click to collapse
at the moment, i get this error when i cmd thor right after connecting phone to usb. (screenshot 1)
i58.tinypic. com/2qnz51d.jpg
Click to expand...
Click to collapse
these is what it says when i try cmd thor after red screen with Nokia logo appers.. (screenhot 2)
i61.tinypic. com/jkftq8.jpg
Click to expand...
Click to collapse
So ive finally got a working version of BoardDiag tool going, after shorting the capacitors to get it from unknown usb device to Qualcomm 9008(com41) i being the tests. AP check and EMMC test both pass than i get this error:
Code:
Device Reset!!
Waiting for DDR test....
Waiting for the device to connect in flash prg
connected to flash programmer
DDR TEST = NUK
sbl1 partition write done...
======== END
and TEST RESULT for SDRAM is FAIL
any thoughts, help or insight is appreciated.
Anyone? Same problem here
me myself and i said:
So ive finally got a working version of BoardDiag tool going, after shorting the capacitors to get it from unknown usb device to Qualcomm 9008(com41) i being the tests. AP check and EMMC test both pass than i get this error:
Code:
Device Reset!!
Waiting for DDR test....
Waiting for the device to connect in flash prg
connected to flash programmer
DDR TEST = NUK
sbl1 partition write done...
======== END
and TEST RESULT for SDRAM is FAIL
any thoughts, help or insight is appreciated.
Click to expand...
Click to collapse
Sorry for the necroposting, but i'm still trying to fix an hard bricked g3 (not g2). The phone seems to be recognized perfectly from windows 10 64 bit pc (Qualcomm HS-USB QDLoader 9008 (COM6) ) but when I try to flash mbn partitions (after 4 or 5 successful flash) phone disconnect or boarddiag say that phone isn't in DLOAD mode and I can't continue.
I think that I did everything in the right way: disable windows driver signature, shortcut right pin on motherboard, installed qualcomm drivers, remove battery, tried various tot file and kdz (for files from kdz I build partition.txt file by myself following this guide http://www.ez-pg.com/how-to-create-partition-txt-file-from-kdz.html) and tried on another windows 10 64bit pc.
With boarddiag I did the sdram test and the result is DDR TEST = NUK, test failed. Someone managed to solve?
Shadow 00 said:
Sorry for the necroposting, but i'm still trying to fix an hard bricked g3 (not g2). The phone seems to be recognized perfectly from windows 10 64 bit pc (Qualcomm HS-USB QDLoader 9008 (COM6) ) but when I try to flash mbn partitions (after 4 or 5 successful flash) phone disconnect or boarddiag say that phone isn't in DLOAD mode and I can't continue.
I think that I did everything in the right way: disable windows driver signature, shortcut right pin on motherboard, installed qualcomm drivers, remove battery, tried various tot file and kdz (for files from kdz I build partition.txt file by myself following this guide http://www.ez-pg.com/how-to-create-partition-txt-file-from-kdz.html) and tried on another windows 10 64bit pc.
With boarddiag I did the sdram test and the result is DDR TEST = NUK, test failed. Someone managed to solve?
Click to expand...
Click to collapse
Same problem here. Did you manage to solve it?
I open a Thread explaining: http://forum.xda-developers.com/lg-g3/general/restoring-boot-sequence-boarddiag-v2-99a-t3374096
Nash L. said:
Same problem here. Did you manage to solve it?
I open a Thread explaining: http://forum.xda-developers.com/lg-g3/general/restoring-boot-sequence-boarddiag-v2-99a-t3374096
Click to expand...
Click to collapse
It was an hardware, emmc related, problem. Seems that flash process was successfull, even if I had to disconnect and reconnect the phone everytime it gave me that problem.
The real problem was the emmc overheating, so (after the flashing process) I put the phone in the coldest place of my house... the freezer. I turned it on, then (really fast) I put the emmc in direct contact with an ice pack; the phone has been on long enough to allow me to backup all the files. Then it died again.
Shadow 00 said:
It was an hardware, emmc related, problem. Seems that flash process was successfull, even if I had to disconnect and reconnect the phone everytime it gave me that problem.
The real problem was the emmc overheating, so (after the flashing process) I put the phone in the coldest place of my house... the freezer. I turned it on, then (really fast) I put the emmc in direct contact with an ice pack; the phone has been on long enough to allow me to backup all the files. Then it died again.
Click to expand...
Click to collapse
Well, that sound like a unique solution. Where you able to sense the heat from the emmc with your hand/fingers? I don't believe my phone has the same problem, mine is dead cold all the time.
Nash L. said:
Well, that sound like a unique solution. Where you able to sense the heat from the emmc with your hand/fingers? I don't believe my phone has the same problem, mine is dead cold all the time.
Click to expand...
Click to collapse
Not during the flashing process. Disassemble the phone, turn it on and try to touch the emmc.
For the flashing process: just try to flash mentioned partition one by one; if bord diag says the phone isn't in dload mode anymore, try disconnect and reconnect the phone and continue from where it stopped
Im an Idiot. I went to twrp recovery and wiped everything, since I wanted to install a higher version of the Samsung tab e, and even when twrp told me that there was no OS installed, I rebooted anyways. I was new to this all thing, and had no idea what exactly that meant and thought, 'What could go wrong?' . . . I just wanted a higher device model, man.
Ugh. Now im stuck in the 'Powered by Android' logo screen, and cant boot into recovery or Download mode.
- What's even worse was that I didn't even enable USB Debugging so Adb is out.
- However, it is Rooted, if that even helps.
- Trying to use the Samsung 300k tool to force enter download mode ends up with 'Write file function failed (error 995)'
- My sibling has the same device model as me, but using T Flash via Odin and my 32GB micro SD card doesn't have a reaction to my device. (Or maybe im doing it wrong, since I don't see anything in the sd card when I plug it to the computer)
- Tablet gets recognized via Odin and Computer, but only as 'MTP USB Device', and in Devices, it is in Unspecified as 'Samsung Android'
- Only good thing that came out of this was the info that I had obtained over the past few days that has shocked my siblings as to why I have this much knowledge over Samsung devices and its functions (AKA I feel cool)
But honestly, at this point I am at a loss of what to do, and will not be surprised if I have to get a USB jig to force it to download mode (my only other option left), or take it to a service center to get it fixed. (the other option I have)
But if there is something you guys are aware of, that I had not tried yet, Please guide me.
Anybody?
norakana said:
Anybody?
Click to expand...
Click to collapse
The simplest way to get an operating system again is to put the ZIP file on a working MicroSD card and put it in your tablet, Then boot into the boot loader and choose to install the file by choosing the external micro sd card.
If you're stuck on a boot screen or download, get out of it by holding the power key + volume down, until the tablet resets.
Note for the future:
always backup your device to an external MicroSD card before deleting your existing operating system, or installing a new one.
So one day I wanted to install PostmarketOS and I managed to get the ZIP file to flash in TWRP, but it didn't work. Idiot me decided to extract the boot img and flash it onto the boot partition and now it's stuck on the boot logo "Samsung Galaxy Tab A6 blah blah...". I tried to get into recovery but to avail, even download mode too.
Well, with all that... Is it possible to somehow trigger an emergency download mode or since I took the back off the tablet, is there any pins that could short in order to reflash the EMMC? Here, I've attached some pics.
Let me know if all hope is lost and I have to get a new mobo. Thanks!
anon2003 said:
So one day I wanted to install PostmarketOS and I managed to get the ZIP file to flash in TWRP, but it didn't work. Idiot me decided to extract the boot img and flash it onto the boot partition and now it's stuck on the boot logo "Samsung Galaxy Tab A6 blah blah...". I tried to get into recovery but to avail, even download mode too.
Well, with all that... Is it possible to somehow trigger an emergency download mode or since I took the back off the tablet, is there any pins that could short in order to reflash the EMMC? Here, I've attached some pics.
Let me know if all hope is lost and I have to get a new mobo. Thanks!
Click to expand...
Click to collapse
You can refer to the video wherein the device is S20 FE but you will need to use EDL cable to get in the edl mode.
mvikrant97 said:
You can refer to the video wherein the device is S20 FE but you will need to use EDL cable to get in the edl mode.
Click to expand...
Click to collapse
Interesting, but my tablet's CPU is an Exynos 7870 Octa not a Qualcomm, not sure if it would work. Also, is it possible to make such EDL cable at home? Oh, and what about software, what do I need to use in order to reflash the stock ROM or at the very least bring back Download Mode? (I assume Odin wouldn't work?)
anon2003 said:
Interesting, but my tablet's CPU is an Exynos 7870 Octa not a Qualcomm, not sure if it would work. Also, is it possible to make such EDL cable at home? Oh, and what about software, what do I need to use in order to reflash the stock ROM or at the very least bring back Download Mode? (I assume Odin wouldn't work?)
Click to expand...
Click to collapse
[guide] repair hard bricked devices with deleted bootloader (sboot)
I'm writing this in android development section because this is only section for both models, i hope this is not a problem. Also i want to say thanks to sataccount from gsmhosting, he found working map at the end. This guide is for hard bricked...
forum.xda-developers.com