Related
my phone will not turn on after successfully performed a restore backup with Heimdall
the backup are the Original from Factory....
whats happen i try to charge my phone, and the screen doest show any sign of life
it doestn boot it doesnt charge, it cannot opened by me
heeeeeeeeeeeeelllppppp
If Heimdall didn't give you any errors then the flash went through fine. Are you sure that you flashed files that were meant for your particular model of Galaxy Tab?
Given the information you've given about the device not turning on or responding at all, it seems as though you've flashed a bootloader that was not designed for your device. You can try create a custom jig and it may be able to boot your device into download mode using the backup secondary bootloader. If that doesn't work then the only other fix is a JTAG fix which is best performed by Samsung themself.
i put in First Boot Loader
boot.bin
i Put on Secondary Boot Loader
Sbl.bin
any mistakes here? these files are recovered from my Tab with Roto BackUp
any chance to do it in da house and not from Samsung Warranty?
Benjamin Dobell said:
You can try create a custom jig and it may be able to boot your device into download mode using the backup secondary bootloader.
Click to expand...
Click to collapse
HOW to do IT ??? explain me more steps
i found this video for make cable for samsung captative......
http://www.youtube.com/watch?v=Rdn5GoRjhn0
what type of cable i need to do the same on my Tab???
anyone can tell me any steps please??
Maybe try this:
http://forum.xda-developers.com/showthread.php?t=885919&highlight=reset+battery
interesting information but i need to research much more
http://forum.xda-developers.com/showthread.php?t=819551
Reediting:
I try with Android SDK and ADB reading this little tutorial
http://mingersoft.com/blog/2010/09/samsung-galaxy-s-why-download-and-recovery-modes-are-missing/
When I plug it into my computer it tries to install a driver for "SEC S5PC110 Test B/D"
any one have a copy of this driver, or can create one for this proposit????
Does the device power on and show anything on the screen? If the Tab won't even turn on then you are bricked but not to worry.. I did the same to mine, and samsung has repaired the device and its on its way home to me today.
i think the better idea is call samsung, wait 2 or 3 weeks.......
but i want know more about some info posted in this thread
perhaps, how and where are the first person whit this Driver, or the first or second with a custom cable jig Compatible with Galaxy Tab and can post where are the steps to do it in da home
Hello guys!
I have totally bricked my phone with Heimdall 1.1.1. I followed the procedure to build Heimdall from source on my Arch Linux box. Then I have used the stock JVQ firmware from samfirmware.com to flash. Unpacked CODE.tar, CSC.tar and MODEM.tar and using heimdall-fronted selected following files to flash:
PIT -> s1_odin_20100512.pit
From CODE.tar:
FactoryFS -> factoryfs.rfs
Kernel -> zImage
Param.lfs -> param.lfs
Primary Bootloader -> boot.bin
Secondary Bootloader -> Sbl.bin
From CSC.tar:
Cache -> cache.rfs
Database data -> dbdata.rfs
The whole flashing procedure was successful, but the phone didn't boot at all. I don't even see the phone ! computer picture that I used to see couple of times before when I was trying to flash something with odin. Nothing. The phone is totally unresponsive. No three button combo, no download mode, no repair mode.
Note that I was never able to successfully flash the firmware from the same machine (my laptop) when flashing with odin on Windows 7. I got only the above mentioned ! computer picture and was able to get the download mode again. Then I flashed the firmware with odin on my Desktop Windows 7 machine.
What do you think about that guys? Did I do something wrong when flashing? Do I have to send the phone to Samsung for the warranty or will I be able to unbrick the phone by my self? I have read that even the USB jig which I have ordered on ebay won't work for me, since I can't even power on my phone. Do you think that people in Samsung will be able to fix it?
Hi! Sorry for my bad english...
u already have the USB jig in your hands? i have an i9000B phone and bricked it in a power failure while flashing a ROM with repartition... the phone went to the "phone!PC" screen, and after taking out the battery to try download mode it didn´t power on again. totally dead.
after a quick search in the forums i´ve found the thread about the USB JIG.
i´ve made a homemade one, as described in the thread... tooke out the battery, waited some seconds, pluged the jig in usb port, then put the battery back in... just got download mode! u must plug the jig with the phone powered down...
to make sure its really of, remove the battery, plug the jig, replace battery.
Good luck =D
frangows said:
u already have the USB jig in your hands?
Click to expand...
Click to collapse
Thank you for your reply. I still don't have the jig, just ordered it. It will ship probably next week (the weekend is coming). It might take some extra time, because is coming from US to Europe. I will let you know whether it works then.
The file -> partition mappings you listed are correct, are you sure that's exactly what you entered?
If you didn't receive an error then the files were transferred to the phone in their entirety without any problems. If a device doesn't boot after this it usually means the files weren't meant for your device (probably not the case here) or you that you accidentally put one of the bootloaders or param.lfs in the wrong spot. This is one reason why I'm hoping Heimdall Firmware Packages will be adopted.
Even if you can't see the screen working try charge your phone for a bit, 3-button combo and then see if your PC detects the phone. I recently read that sometimes a corrupt param.lfs might simply cause your screen to stop working rather than hard-bricking the whole device, although I can't confirm this.
A custom jig is still worth a shot, as it causes your device to boot using a backup secondary bootloader. So if the problem is with the secondary bootloader then the jig will allow you to access download mode.
However if the problem is with boot.bin or param.lfs then a JIG probably won't work and you'll need to take your phone into a Samsung Repair Centre. Either that or send your phone to someone who can perform a JTAG repair, the former tends to be much simpler.
Benjamin Dobell said:
If you didn't receive an error then the files were transferred to the phone in their entirety without any problems. If a device doesn't boot after this it usually means the files weren't meant for your device (probably not the case here) or you that you accidentally put one of the bootloaders or param.lfs in the wrong spot. This is one reason why I'm hoping Heimdall Firmware Packages will be adopted.
Click to expand...
Click to collapse
I'm pretty sure I did everything right (but you can't be always 100% sure). I still think there is something wrong with USB ports on my laptop. When I was flashing with odin on the same laptop in win7, the flashing procedure was successful, but I got the "phone!computer" picture and was able to get into download mode again. Fortunately, I flashed only kernel and not the whole package with bootloader. Then I used my desktop computer to successfully flash the firmware again.
Benjamin Dobell said:
However if the problem is with boot.bin or param.lfs then a JIG probably won't work and you'll need to take your phone into a Samsung Repair Centre. Either that or send your phone to someone who can perform a JTAG repair, the former tends to be much simpler.
Click to expand...
Click to collapse
I will wait for my ordered JIG and if it won't work, I'm going to take the phone to Samsung. Any way, I will never try to flash anything to my phone from the laptop. The desktop computer way seems to be the better way.
Well, I almost forgot I have posted here. The JIG didn't work for me so I had to send my phone to the service. After three weeks phone came back. They had to change a defective part of the phone. I don't know which part it was (it was the state of e-shop, where I bought the phone).
Flashing primary bootloader is generally a dangerous thing to do.
http://forum.xda-developers.com/showthread.php?t=1236273
or you could've helped these guys out
Hot To Unbrick Galaxy S JIG Method
this is a giude
I test this guide 1 month ago and it works
while I had put my I9000 into downloading mode, accidently its battery dropped out, and now its just showing a pic of mobile ==/!\== computer.
I tried recovery mode by trying all combinations of UP+HOME+POWER and others but did not work.
Any solutions.
Am new to all this, so no idea what it would be. Initially I just wanted to check what downloading mode is and how it looks.
thanks
Amol
amolpujari said:
while I had put my I9000 into downloading mode, accidently its battery dropped out, and now its just showing a pic of mobile ==/!\== computer.
I tried recovery mode by trying all combinations of UP+HOME+POWER and others but did not work.
Any solutions.
Am new to all this, so no idea what it would be. Initially I just wanted to check what downloading mode is and how it looks.
thanks
Amol
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1134975
Dunno why your phone got softbricked..because it shouldn't do that if you weren't flashing anything
Can Heimdall help me out here?
Did you flash sth. While the battery dropped out??
Sent from my GT-I9000 using XDA App
Actually I was doing "Installing the ClockworkMod Recovery" from this link - __wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_Full_Update_Guide
and I was about to run "heimdall flash --kernel zImage"
I ran it too, but zImage was not at place, hence this did not complete saying so.
And after this battery dropped out slightly.
thanks
Amol
Use Heimdall
amolpujari said:
Can Heimdall help me out here?
Click to expand...
Click to collapse
Yeah try this heimdall close-pc-screen
its not detecting it now....
[email protected]:~$ heimdall close-pc-screen
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
__glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
__glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Failed to detect compatible download-mode device.
[email protected]:~$ heimdall detect
Failed to detect compatible download-mode device.
[email protected]:~$
this too below fails....
[email protected]:~/android-sdk-linux/platform-tools$ ./adb devices
List of devices attached
[email protected]:~/android-sdk-linux/platform-tools$
I tried several times to restart it in proper download/recovery mode by trying out several buttons combinations, but it starts in
mob --/!\ comp
Buy a Jig at eBay it costs 10$, and you get your SGS into DL mode.
Sent with my Galaxy S using Tapatalk
Hi @ all
i have a different problem....after flashing my SGS it boot till
--Copying media files
and stuck... I also cant enter the recovery mode...to factory reset...
have anybody a idea how to fix this problem...
thy alot and sorry for my terrible english
Can you enter Download-Mode?
Sent from my GT-I9000 using XDA App
hey guys ...
when USB unplugged (optional)
if I do Vol DOWN + HOME + power....it flashes and I release off power button, it gets back to downloading mode....
what next, shall I try for ics and by following which link ....
or how shall I get back to normal mode now ...
Yes entering download mode is possible...with the three buttons and also with jig...
i reflashed it a few times with repart...but i couldn´t fix the problem always the same...
i had tried to start recovery mode for factory reset...but i can´t enter it...
next i found a fix for the recovery with 3 button mode... after flashing the boot loader
and try to start recovery mode...my Display became grey like a TV without signal
But i can still enter the download mode and it boots till copying media file
new_tron said:
Yes entering download mode is possible...with the three buttons and also with jig...
i reflashed it a few times with repart...but i couldn´t fix the problem always the same...
i had tried to start recovery mode for factory reset...but i can´t enter it...
next i found a fix for the recovery with 3 button mode... after flashing the boot loader
and try to start recovery mode...my Display became grey like a TV without signal
But i can still enter the download mode and it boots till copying media file
Click to expand...
Click to collapse
Corrupted internal sd? Search forum for a fix (dunno if that's your real problem). And also flash always with 3 files if using re-partition.
Sent from my sandwiched SGS
amolpujari said:
hey guys ...
when USB unplugged (optional)
if I do Vol DOWN + HOME + power....it flashes and I release off power button, it gets back to downloading mode....
what next, shall I try for ics and by following which link ....
or how shall I get back to normal mode now ...
Click to expand...
Click to collapse
So if you are now able to enter download mode and PC detects your phone, I'd suggest flashing stock JVU. After that if everything is working again, flash ics or whatever you want
Sent from my sandwiched SGS
My old charger for the Iconia 500 broke and I got a replacement charger (not acer). When it came the iconia was already completely drained. I plugged it in, charged it, and since then the only thing that happens is this:
- I push power and after about 3s it turns white. Nothing happens on the screen, no vibration, nothing.
- I can turn the power back off by holding the button for 5s.
> I have tried holding the button longer but no difference.
> From what I have read I suspect it might somehow have gotten into APX mode?
> I have tried to read through the numerous posts on this forum but cannot quite find this same problem/am overwhelmed by the lingo.
> I have tried to connect the tablet to my PC with a microSD cable, and it lists it as APX, category unknown, APX doesn't have a driver
- Can anyone confirm/suggest what might be wrong with my tablet?
- Is this something that can be fixed at a repair shop?
- Is this something I could fix? (I have no ID's or codes for the tablet, have never played with APX mode before)
Thank you for any advice!
- Chris
CKM80 said:
My old charger for the Iconia 500 broke and I got a replacement charger (not acer). When it came the iconia was already completely drained. I plugged it in, charged it, and since then the only thing that happens is this:
- I push power and after about 3s it turns white. Nothing happens on the screen, no vibration, nothing.
- I can turn the power back off by holding the button for 5s.
> I have tried holding the button longer but no difference.
> From what I have read I suspect it might somehow have gotten into APX mode?
> I have tried to read through the numerous posts on this forum but cannot quite find this same problem/am overwhelmed by the lingo.
> I have tried to connect the tablet to my PC with a microSD cable, and it lists it as APX, category unknown, APX doesn't have a driver
- Can anyone confirm/suggest what might be wrong with my tablet?
- Is this something that can be fixed at a repair shop?
- Is this something I could fix? (I have no ID's or codes for the tablet, have never played with APX mode before)
Thank you for any advice!
- Chris
Click to expand...
Click to collapse
Hi chris, yes you are stuck in apx mode.
To fix this you must have your tabs CPUID.
The easiest way is from an old nandroid backup, thats if you have one. If you do, look in the cwm backup folder under cpuid.txt
If you dont have a backup, your only chance is thru ubuntu. There is a guide by "srbeen" stickied in the General forum.
If you can retrieve yr cpuid, post back here and we can help u get fixed. YoU will need anutha file to do this tho'. Its called babsector.rar and you can download it in post 2 in the root guide in my sig.
You will also need a rom to flash - only ICS or JB.
To summarise,
1. Retrieve the cpuid/sbk
2. Once you have that then
3. Download babsector and a rom.
4. Come back here for unbricking help.
Good luck with the cpuid/sbk, without it you can do nothing.
dibb
Thanks for your reply and your advice! It is nice to have the confirmation about what the problem is, and a step by step guide to start tackling it. I feel a bit less lost now I'm going to try to follow your steps and will let you know if I get stuck anywhere.
- Chris
next steps?
Ok, so somehow (a miracle I guess) I managed to do your steps:
- installed ubuntu
- followed srbeen's steps upto the point where I got my CPUID
- got my SBK
- downloaded babsector.rar (luckily chrome offered to translate the russian site I found it at)
- unrarred it
- downloaded a ROM from http://forum.xda-developers.com/showthread.php?t=1935582 (is this an appropriate ROM?)
- unzipped the ROM and copied it to the external micro SD card
Can you point me in the right directions for the next steps?
Thanks,
Chris
dibb_nz said:
Hi chris, yes you are stuck in apx mode.
To fix this you must have your tabs CPUID.
The easiest way is from an old nandroid backup, thats if you have one. If you do, look in the cwm backup folder under cpuid.txt
If you dont have a backup, your only chance is thru ubuntu. There is a guide by "srbeen" stickied in the General forum.
If you can retrieve yr cpuid, post back here and we can help u get fixed. YoU will need anutha file to do this tho'. Its called babsector.rar and you can download it in post 2 in the root guide in my sig.
You will also need a rom to flash - only ICS or JB.
To summarise,
1. Retrieve the cpuid/sbk
2. Once you have that then
3. Download babsector and a rom.
4. Come back here for unbricking help.
Good luck with the cpuid/sbk, without it you can do nothing.
dibb
Click to expand...
Click to collapse
Next steps?
Hi dibb_nz (and others)
I am still stuck. I have been trying several things, but none worked so far.
- I think the drivers are installed properly. When I go to device manager it lists APX under unspecified device - with Acer USB Boot recovery Driver installed under the hardware tab. It also says Model: APX, Category: Unknown
- I tried to run babsector, and it gives me an error. Before giving me the error it does get my tablet to show the text "Entering Acer Download Mode" in the topleft corner. Then I get the error "failed executing command 16 NvError 0x120002, command failure: create failed (bad data)" in the attached image.
- I also tried to follow the steps in Timmy Dean's V4 post, since I hoped maybe that would help, but that also gave me an error. (Red letters saying it failed, and to follow the steps again and try again).
I feel once more defeated, and hope you know what to do next.
- Chris
dibb_nz said:
Hi chris, yes you are stuck in apx mode.
To fix this you must have your tabs CPUID.
The easiest way is from an old nandroid backup, thats if you have one. If you do, look in the cwm backup folder under cpuid.txt
If you dont have a backup, your only chance is thru ubuntu. There is a guide by "srbeen" stickied in the General forum.
If you can retrieve yr cpuid, post back here and we can help u get fixed. YoU will need anutha file to do this tho'. Its called babsector.rar and you can download it in post 2 in the root guide in my sig.
You will also need a rom to flash - only ICS or JB.
To summarise,
1. Retrieve the cpuid/sbk
2. Once you have that then
3. Download babsector and a rom.
4. Come back here for unbricking help.
Good luck with the cpuid/sbk, without it you can do nothing.
dibb
Click to expand...
Click to collapse
CKM80 said:
Hi dibb_nz (and others)
I am still stuck. I have been trying several things, but none worked so far.
- I think the drivers are installed properly. When I go to device manager it lists APX under unspecified device - with Acer USB Boot recovery Driver installed under the hardware tab. It also says Model: APX, Category: Unknown
- I tried to run babsector, and it gives me an error. Before giving me the error it does get my tablet to show the text "Entering Acer Download Mode" in the topleft corner. Then I get the error "failed executing command 16 NvError 0x120002, command failure: create failed (bad data)" in the attached image.
- I also tried to follow the steps in Timmy Dean's V4 post, since I hoped maybe that would help, but that also gave me an error. (Red letters saying it failed, and to follow the steps again and try again).
I feel once more defeated, and hope you know what to do next.
- Chris
Click to expand...
Click to collapse
OK< there is a slim chance u may be able to recover your tab.
There is a bct error - usually only one tool can repair this.
Download the apxflash tool.
Power your tab off.
Enter apx mode via the buttons - DO NOT use the tool to do this -
Connect your usb cable.
Run the tool - choose to go to the bundle market and download bundle 17.
If the apx driver has loaded and is showing in device manager then continue with the apx flash tool -
You will eventually see a window asking whether to dump and save yr bct, choose yes.
Hopefully the tool will carry on with the flash, once thats done, boot straight to recovery, complete the wipes and formats and then flash your rom.
I have done the steps below.
Just to make sure, when you are talking about the APX drivers being loaded, do you mean the one I see when I go to devices, right click on APX, choose hardware, where it says "ACER USB Boot-recovery driver" under device functions?
So when I tried to dump my own it gave me the following error (attached as image):
Unhandled exception, could not find file bct.dec.
It gave me the option to try to continue anyway, which I tried, but now it has been hanging in the screen "staging and backing up BCT, Using default BCT" for a long time...
so, does this mean it really is dead? And if so, what part of the tablet is dead? And if not (*hope*), then what else can I try?
Thanks,
Chris
ps. my tablet was never rooted, so I don't know if that complicates the matter... it does say that it needs to have been rooted to choose the dump option. Moreover, I never was able to turn USB debugging on, because I don't have access to the tablet. It does nothing besides black screen and occasionally the "Enter download mode" (but not with these steps)
dibb_nz said:
OK< there is a slim chance u may be able to recover your tab.
There is a bct error - usually only one tool can repair this.
Download the apxflash tool.
Power your tab off.
Enter apx mode via the buttons - DO NOT use the tool to do this -
Connect your usb cable.
Run the tool - choose to go to the bundle market and download bundle 17.
If the apx driver has loaded and is showing in device manager then continue with the apx flash tool -
You will eventually see a window asking whether to dump and save yr bct, choose yes.
Hopefully the tool will carry on with the flash, once thats done, boot straight to recovery, complete the wipes and formats and then flash your rom.
Click to expand...
Click to collapse
CKM80 said:
I have done the steps below.
Just to make sure, when you are talking about the APX drivers being loaded, do you mean the one I see when I go to devices, right click on APX, choose hardware, where it says "ACER USB Boot-recovery driver" under device functions?
Click to expand...
Click to collapse
yep thats correct
So when I tried to dump my own it gave me the following error (attached as image):
Unhandled exception, could not find file bct.dec.
It gave me the option to try to continue anyway, which I tried, but now it has been hanging in the screen "staging and backing up BCT, Using default BCT" for a long time...
Click to expand...
Click to collapse
Do you have the latest version of the apxflash tool....as far as I know, this is the ONLY way to fix a bct error....
So if you try and save yr tabs bct but you get the error and if u try to continue it just hangs???
The only thing I can suggest now is to power off both devices and then power on. When u get to the bct option try the default option first if it still hangs, power everything down again and this time try saving the bct again. Not much help I'm afraid, sometimes the tools do get stuck, and its best to power down and try again.
so, does this mean it really is dead? And if so, what part of the tablet is dead? And if not (*hope*), then what else can I try?
Click to expand...
Click to collapse
I hope not!! If the tool insists on hanging, you can TRY the babsector file, post an error if you get one. Its in the root guide in my sig, along with instructions for use
good luck
dibb
EDIT: Added attachment apxFlash Tool v1.1.1 @CKM80
Well, I am trying to again with the default option, but it has been saying "Flashing bootloader (EBT) stage two - uploading image" for 45 minutes now, while another nvflash.exe window that popped up says "nvflash started, [resume mode]"
The tablet says "Acer Iconia APX mode" in the topleft.
I am not sure if it is doing something still (after 45 min) or that it is hanging.
I will let it sit a while longer, and if it doesn't work I will try all options again.
Will keep you posted.
Chris
dibb_nz said:
yep thats correct
Do you have the latest version of the apxflash tool....as far as I know, this is the ONLY way to fix a bct error....
So if you try and save yr tabs bct but you get the error and if u try to continue it just hangs???
The only thing I can suggest now is to power off both devices and then power on. When u get to the bct option try the default option first if it still hangs, power everything down again and this time try saving the bct again. Not much help I'm afraid, sometimes the tools do get stuck, and its best to power down and try again.
I hope not!! If the tool insists on hanging, you can TRY the babsector file, post an error if you get one. Its in the root guide in my sig, along with instructions for use
good luck
dibb
EDIT: Added attachment apxFlash Tool v1.1.1 @CKM80
Click to expand...
Click to collapse
CKM80 said:
Well, I am trying to again with the default option, but it has been saying "Flashing bootloader (EBT) stage two - uploading image" for 45 minutes now, while another nvflash.exe window that popped up says "nvflash started, [resume mode]"
The tablet says "Acer Iconia APX mode" in the topleft.
I am not sure if it is doing something still (after 45 min) or that it is hanging.
I will let it sit a while longer, and if it doesn't work I will try all options again.
Will keep you posted.
Chris
Click to expand...
Click to collapse
sorry m8, missed your post...did u try the flash tool version i posted??
Have u tried the babsector file??? I'd be tempted to run that but from what you have said its sounding like a hardware failure....babsector will tell you tho
Hang in there and hopefullly we can have it resolved one way or another!
dibb
Hi Dibb_nz,
I did try... the flashing never worked, always stopped.
Babsector gave the attached error,
Chris
dibb_nz said:
sorry m8, missed your post...did u try the flash tool version i posted??
Have u tried the babsector file??? I'd be tempted to run that but from what you have said its sounding like a hardware failure....babsector will tell you tho
Hang in there and hopefullly we can have it resolved one way or another!
dibb
Click to expand...
Click to collapse
CKM80 said:
Hi Dibb_nz,
I did try... the flashing never worked, always stopped.
Babsector gave the attached error,
Chris
Click to expand...
Click to collapse
oh right. the bct thing...thats a bumma m8, wish I could suggest something for ya, but my bag of tricks is empty
All I can tell u is that 'sometimes' after trying wot seems everything a hundred tries or more, something finally happens and it works...this doesn't mean you do not have a faulty memory chip, as this is just what happens...you could try it next week and it may well work....no consolation I know...
You might wanna try a friends computer (specially if they do not have win8!!) you neva know yr luck!!
Yeah, I think I'll try a couple of times, but I am pretty much ready to give up.
Thanks for all your tips along the way.
- Chris
dibb_nz said:
oh right. the bct thing...thats a bumma m8, wish I could suggest something for ya, but my bag of tricks is empty
All I can tell u is that 'sometimes' after trying wot seems everything a hundred tries or more, something finally happens and it works...this doesn't mean you do not have a faulty memory chip, as this is just what happens...you could try it next week and it may well work....no consolation I know...
You might wanna try a friends computer (specially if they do not have win8!!) you neva know yr luck!!
Click to expand...
Click to collapse
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