Related
some guy successfully bricked his N1 as soon as he received it about 2 months ago. When this expensive brick reached my hand, he didn't even remember what he had done... and this brick had been through many many ppl for repair, so there is no way for me to know what exactly happened during the last 2 months...
Anyway, now it:
1. light doesn't turn on when charging(not sure yet whether it is actually charing)
2. trackball + power could gets it to fastboot screen, but none of the key is working then.
3. after single press of power button when powered off, red/green/blue/white color bar and 3 droids on the screen
so , now I cannot put it in fastboot nor recovery mode, stuck.
could there be anything I can do to rescue it?
ndep said:
2. trackball + power could gets it to fastboot screen, but none of the key is working then.
Click to expand...
Click to collapse
Verify this. Enter fastboot mode (connected to usb) and then try "fastboot devices" in a command prompt. It it reports a connected device then its definitely recoverable.
The only way that a N1 get bricked (software wise) is by upgrading a wrong radio, and unfortunetly the only way to recover it (now) is by sending it to Google/HTC
more explanation
thanks i did try that...fastboot devices could not detect anything,coz it just freezes at that screen and could not enter any mode using power and voldown button.
what puzzlrs me most is that screens with multicolor bars, how on earth does that happen?
britoso said:
Verify this. Enter fastboot mode (connected to usb) and then try "fastboot devices" in a command prompt. It it reports a connected device then its definitely recoverable.
Click to expand...
Click to collapse
update: the light turns orange now and then when charging, and it is actually charging no matter the light is on or not. ( using my own nexus to verify that )
Did you plugged it to your PC?
I knew a guy who bought a ''flashing device'' capable of formating any chipset over USB, so he could do a clean install of the Firmware again. Perhaps you could find one of these devices over ebay
britoso said:
Verify this. Enter fastboot mode (connected to usb) and then try "fastboot devices" in a command prompt. It it reports a connected device then its definitely recoverable.
Click to expand...
Click to collapse
That's assuming he has the android sdk installed with the correct drivers. We don't know if the op has.
@vegetaleb: the device you mentioned is somewhat mysterious... a search on ebay with "flash device" does not give me anything related, do you have a specific name?
@C.Slater: I do have them, coz I myself own a nexus too..
should be deleted, sorry
@vegetaleb: the device you mentioned is somewhat mysterious... a search on ebay with "flash device" does not give me anything related, do you have a specific name?
@C.Slater: I do have them, coz I myself own a nexus too..
edit: isn't there an option to delete this reply? I clicked the submit button twice,sorry.
does typing fastboot devices in the cmd prompt work for your non bricked nexus?
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Does holding power+trackball bring you to fastboot?
Yes=It's not bricked
No=Kiss it goodbye, it's bricked
Simple as that
TFJ4 said:
Does holding power+trackball bring you to fastboot?
Yes=It's not bricked
No=Kiss it goodbye, it's bricked
Simple as that
Click to expand...
Click to collapse
power+trackball will bring it to fastboot screen, note just the fastboot screen, it just freezes there. All the buttons does not work, and connecting to PC using a USB cable does not show "FASTBOOT USB".
However, it could enter HBOOT with power+voldown, I noticed it searches for passdiag.zip , passdiag.nbh, etc. Could I use this builtin function to flash it? which file in this post should I use?
http://android.modaco.com/content/g...-online-kitchen-optional-root-insecure-himem/
I tried to use the first one ( http://www.romraid.com/paul/nexusone/EPE76-update-nexusone-stock-images.zip ), rename to PASSDIAG.zip , but HBOOT is still complaining about "No Image"
Perhaps it's physically damaged!
It remembers me of my boss iphone that looked perfectly normal but couldn't get a FW installed because the power part has been damaged by water(power button couldn't work at all)
Try renaming it to passimg.zip and use hboot again.
speedyls91 said:
Try renaming it to passimg.zip and use hboot again.
Click to expand...
Click to collapse
tried PASSIMG.zip , still "No Image"...
You can send it to htc for repair but the downside would be that you would never know how to deal with this kind of problem yourself...
Continue the research and keep us posted ...
i maybe wrong but i think is it case-sensitive.....meaning PASSIMG.zip would fail but passimg.zip wouldn't.....Correct me if i'm wrong please....
Case sensitive
I'm pretty sure it is case sensitive. Used to be that way with other android and HTC devices. Can't imagine it's changed.
linux is case sensitive, for sure.
i say approach from the adb/fastboot route, using usb. first, ensure that you have all the correct drivers etc for adb use (the sdk, the usb drivers, and the device specific drivers).
try ur 'adb devices' command
if adb sees it, in normal mode, you should be okay. make sure the phone has 'usb debugging' turned on in settings
Pretty sure the phone is toast, but wanted to confirm. I was erasing each of the partitions (boot, system, recovery, etc.) in order to write the latest Dell 2.2 packages, and after I erased each parition, my dog knocked my phone off the table, and the battery flew out.
Now it will not boot in any form (obviously because I blew everything away). I assume there is nothing I can do at this point, is that right?
Guess I will be sending it back to Dell.
Fixed it
I was able to follow steps found at whirlpool.net.au wiki dellstreak22 to correct the problem and get running again.
i'm in the same situation, no boot, fastboot or recovery. It remain with a black screen. I tried to use the guide but the Streak doesn't respond. Please give me an help
try that
whirlpool.net.au/wiki/dellstreak22
No luck
freepal08 said:
try that
whirlpool.net.au/wiki/dellstreak22
Click to expand...
Click to collapse
I have same problem.
I tried the thread above but when I try to install the Qualcomm driver on my x64 system (I followed certificate advice) I get an error message, the Qualcomm with ! mark changes to a com port with a ! mark in the device manager on the pc so I am not able to use the QDL. Get an error message that this driver is not for my system.
Can somebody please advice.....
Kind regards,
Pascal
freepal08 said:
try that
whirlpool.net.au/wiki/dellstreak22
Click to expand...
Click to collapse
the baseband upgraded correctly but my streak doen't go in fastboot mode it remain with the black screen. I think that is definitely bricked
Hi,
I tried to upgrade from v2.1 to new Android 2.3.5 Gingerbread For LG Optimus GT540 and I followed instructions exactly, but I am stuck at number 8, I did this:
8- Now click “Launch software update”, DO NOT USE THE PC TO THE PROCESS IS COMPLETE. THE PHONE WILL REBOOT WHEN FINISHED THE PROCESS IN KDZ. (The process takes about 15 minutes in KDZ).
and about 2 minutes text log writes and stopped, I am now waiting more then 40 minutes my phone didn't reboot. On display is still written download mode, what should I do now ?
In kdz is written:
3GQCT: wParam = 205. IParam = 36
p.s.
I disconnected phone from usb and pull out battery and now I cannot turn on phone, I tried to push vol down + power for 5 sec.
Any idea what should I do now? I hope I didn't brick my phone
What programs are you using?
What are you using to update your phone and have you tried taking out your SIM, SD card and battery then turned it on with the USB cable?
I used KDZ updater and tried to install CyanogenMod7 (2.3.5) @ GT540 Swiftdroid2 RC3 by Mur4ik. if that is what you ask ?
I removed sim card and battery also, then tried to turn it on while plugged in to computer usb but no response from phone, I can't turn it on
p.s. I am using win 7 64 bit OS
gorantz said:
I used KDZ updater and tried to install CyanogenMod7 (2.3.5) @ GT540 Swiftdroid2 RC3 by Mur4ik. if that is what you ask ?
I removed sim card and battery also, then tried to turn it on while plugged in to computer usb but no response from phone, I can't turn it on
p.s. I am using win 7 64 bit OS
Click to expand...
Click to collapse
If you can't get into download mode, then it's game over I'm afraid. What you will need to do is return the phone back to where you bought it. This happened to me some time ago. But the Carphone Warehouse were happy to fix it (even though I had voided the warranty but don't tell them that ). Don't say that you tried to mod the phone, say something like 'I installed LG's PC Suite and it said my device had a software update. I went along with it, but it gave me an error half way through. Now my phone won't turn on at all' It might just work!
I had the same problem when modding with kdz.
completely bricked my phone, but was able to fix by putting kdz into emergency mode instead of diag and updating with a fastboot stock rom,
it would stop after 2 minutes and give me and error but it managed to get fastboot onto my phone,
(camera + power)
then just flashed the fastboot method with adb and everything was fine,
my problem was something to do with lg modem drivers i believe,
I read a thread that said to disable the lg virtual modem. (didnt
work for me)
pretty noob myself
but the above method worked for me,
not sure if this can do anymore damage to the phone
have a look at this is u get it into emegancy mode.
On the kdz updater instead of 3GQCT put into emergancy
http://www.youtube.com/watch?v=fDmU9RSIiDA
If you have tried flashing with Cm7 you might be lucky,
try holding camera button and powering on the phone, a black screen should come up thats fastboot.
if that comes up u should be able to just reflash following mur4iks instruction
if not try what i said in my last post and reflsh with phone type 3QGCT and PhoneMode EMERGENCY
again only going of how i fixed my bricked phone
ZxWelshyxz said:
If you have tried flashing with Cm7 you might be lucky,
try holding camera button and powering on the phone, a black screen should come up thats fastboot.
if that comes up u should be able to just reflash following mur4iks instruction
if not try what i said in my last post and reflsh with phone type 3QGCT and PhoneMode EMERGENCY
again only going of how i fixed my bricked phone
Click to expand...
Click to collapse
He was trying to flash a fastboot rom (to install CM7) but bricked his device in the process. So he can't flash CM7-.-
Yeah I know that but I mean when I got the error he has, I flashed with a stock 2.1 fastboot rom With Diag changed to EMERGENCY and was able to get on to fastboot mode (camera+power), I got the error again as i was flashing but the phone would load fastboot and not start up
If he can get lucky and get into fastboot like i did, a simple:
fastboot -w
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
should fix his problem or did i just get lucky?
sorry if im confusing thinks here, but this is how i fixed mine. which was also dead and not turning on
Sent from my GT540 using XDA App
@ZxWelshyxz
I am total neewbie, can you write to me some kind of tut, like press that then do that etc
gorantz said:
@ZxWelshyxz
I am total neewbie, can you write to me some kind of tut, like press that then do that etc
Click to expand...
Click to collapse
Well like i told you im a noob at this myself (Android phone flashing atleast)
I suppose it would be good to see if you got fastboot??
Power on the phone while holding camera button (hold the camera button until the screen goes black) if you can get fastboot you can just follow the fastboot flash instructions after fastboot -w
if not on kdz in the top right were it says DIAG, Change this to CS_EMERGENCY,Click Launch update and flash again with a stock fastboot rom
after THIS see if the phone loads or boot loops(had this once too) or loads fastboot
Il try look to find the thread i read on another forum for troubleshooting kdz it helped me alot
EDIT: http://android.modaco.com/topic/321895-faqgt540-reference-thread/ try some of the troubleshooting tips at the bottom of the O.P
I basicly aimed to get fastboot working so make sure your flashing with a stock FASTBOOT! rom
again im new to this im just saying what got my phone back to life
my fone stuck in download mood what can i do?
corecrack said:
my fone stuck in download mood what can i do?
Click to expand...
Click to collapse
Pull out the battery and turn on the phone again (if you have knocked the phone when turning on, or flash a KDZ (when connected to PC)
@gorantz
Can i advise to follow step by step tutorial pin pointed by lavero.burgos, am a total neewbie like u man,but now using latest CM7 by Mur4ik and waiting for new release from devs
Sent from my GT540 using XDA App
thanks, but my phone is now at service when I get it back maybe I'll try....but maybe
gorantz said:
thanks, but my phone is now at service when I get it back maybe I'll try....but maybe
Click to expand...
Click to collapse
I bricked my phone and I tried it again after getting it back from lg
I'm new here and to having a Smartphone, I've just been given an LG Android GT540 which is at version 1.6. The LG site tells me I can upgrade to 2 something or other, sorry can't remember the exact number and gives instructions on how to do the upgrade, but I'm a bit on the cautious side as I don't want to brick it, not this early on in owning my first Smartphone.
I'll be reading a lot of the posts here to try and find out as much as I can before I attempt to do this.
Well don't worry if it's official update. But if you some how brick your phone just tell lg the update bricked your phone and we are talking about unofficial updates
Sent from my GT540 using XDA App
gorantz said:
thanks, but my phone is now at service when I get it back maybe I'll try....but maybe
Click to expand...
Click to collapse
Dont hesitate to ask for help man its worth upgrading.
Sent from my GT540 using XDA App
I've got phone today from service (not official LG service), repairman just manage to wake up phone so I can turn it On, but when I turn it I get black screen with message on it ''download mode''. Now computer recognize phone when I plug it, and I tried to update or flash it with kdz updater but have no luck
I launch kdz in emergency mode, load rom with updater, press launch button, and process started, (get messages unpacking software etc.) but after 3-4 minutes I notice that computer is blocked I couldn't do anything with mouse pointer, and I waited 15 minutes but computer is still blocked, even time on computer is stopped. I tried this procedure few times, every time it is same. Also tried to disable lg virtual modem in device manager. Any idea what I could do ?
p.s. repairman in service told me that he tried it to flash it with riff box, process started but after few minutes if stopped and blocked his riff box
OK,, so I. Came Fro the AOKP rom then flashed. .30 stock from Asus. So I could flash the Hydro 4.0 rom. Everything went fine. Was working perfectly for couple days. Didn't use for one day. Try turn on screen, nothing. Hold power to turn on, nothing. Neither can boot into recovery :/ After I flashed the hydro rom. Haven't messed with anything, don't even think I installed any new apps.
When screen is black, can only see charging light while charging. Anny ideas?!?!
Please and thank you
try if you can get adb running after you switched it on
then type these messages
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1
Enter
when finished
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1
Try to boot now. If it´s still not running
dl this file:
http://www.4shared.com/zip/7XYW-4c4/WSG_UnBricker_TF300T_V102.html Its for the tf300T
unback it
start WSGFlasher
choose 2 for Install menu
choose 1 for full unbrik
Ill try this right when I get home, but I have no idea what could've happened to brick it. The first part you said with adb, what exactly will that do. Just same thing as zip, without using the zip?
So for the life of me I cant get adb to work! Idk what I can or should do. My comp recognized it as an advanced device before. The only sign of life it has is a solid orange light by the power button.(charging or not) I've tried everything. Any help will be so much appreciated. And thanked as many times as I can press it lol
Mine is on its way back from the repair center from similar symptoms. Everything working, but the screen was black. I could see the backlight coming on when I hit the power button. Heard the 'ding' when I plugged in the charger, and could see it on my TV when I purchased an HDMI cable. It started after a quick charge - it was working fine in the morning, I charged it during lunch, and then never could get it back on.
Ya I read ur situation happening alot, like alot on previous TF models, you would think a big company like Asus would recognize all the problems from previous tabs. And find a solution so it doesn't happen with the next model. Everyone keeps rushing out there new tablet when the still have aloe of bugs and defects
When you sent urs in, did you have ur bootloader unlocked?
And my problem is way different than urs. Mine won't turn on at all. Just happened out of no where. I wish I had ur problem. Cause at least I could use it threw HDMI. And still use it. But idk what to do, and don't no if it was my fault or damn hardware to a **** (that Asus sold me)
If anyone has any work around please help (ADB doesn't work anymore, used to not now)
trevor7428 said:
Ya I read ur situation happening alot, like alot on previous TF models, you would think a big company like Asus would recognize all the problems from previous tabs. And find a solution so it doesn't happen with the next model. Everyone keeps rushing out there new tablet when the still have aloe of bugs and defects
When you sent urs in, did you have ur bootloader unlocked?
And my problem is way different than urs. Mine won't turn on at all. Just happened out of no where. I wish I had ur problem. Cause at least I could use it threw HDMI. And still use it. But idk what to do, and don't no if it was my fault or damn hardware to a **** (that Asus sold me)
If anyone has any work around please help (ADB doesn't work anymore, used to not now)
Click to expand...
Click to collapse
Does windows device manager sees any kind of a transformer device?
If yes try to install the drivers by hand.
right klick on the device
choose update driver software
choose search manually on computer
next window choose from a list on computer (the one at the buttom of the window)
Then you will get a 2sided window
right side you have the company names
left side you have the model type
if you have something like asus ther on the right side choose it
then on the left side choose Asus android ADB device (!!!! not the one with Composite)
then klick on next
if a window pops up saying something like its not recommended just hit yes and install it anyway.
Translatet it from German, so I hope the translation is correct. Just follow the steps and you will know what I mean.
or, if you are only able to get Fastboot running you need the blob file out of the Asus update (it has to be placed in the folder were the fastboot.exe is) update and this fastboot command:
fastboot -i 0x0B05 flash system blob
I had to run the fastboot command more than 20 times, but finally it run through and i was back to stock.
for fastboot dl this package
http://www.4shared.com/zip/npKPgYok/WSG_UnBricker_Skript_no_Fw.html
extract the folder to c: and rename the folder to trecovery
open cmd
type cd c:\trecovery\
now you are in the folder with fastboot.exe
Than type the fastboot command
mikaole said:
Does windows device manager sees any kind of a transformer device?
If yes try to install the drivers by hand.
right klick on the device
choose update driver software
choose search manually on computer
next window choose from a list on computer (the one at the buttom of the window)
Then you will get a 2sided window
right side you have the company names
left side you have the model type
if you have something like asus ther on the right side choose it
then on the left side choose Asus android ADB device (!!!! not the one with Composite)
then klick on next
if a window pops up saying something like its not recommended just hit yes and install it anyway.
Translatet it from German, so I hope the translation is correct. Just follow the steps and you will know what I mean.
or, if you are only able to get Fastboot running you need the blob file out of the Asus update (it has to be placed in the folder were the fastboot.exe is) update and this fastboot command:
fastboot -i 0x0B05 flash system blob
I had to run the fastboot command more than 20 times, but finally it run through and i was back to stock.
for fastboot dl this package
http://www.4shared.com/zip/npKPgYok/WSG_UnBricker_Skript_no_Fw.html
extract the folder to c: and rename the folder to trecovery
open cmd
type cd c:\trecovery\
now you are in the folder with fastboot.exe
Than type the fastboot command
Click to expand...
Click to collapse
I understood perfectly. But device manager does not pick up my tf300 anymore. It used to say Asus transformer but not after black screen. And I've had to use fastboot in the past with C:/recovery. But adb won't recognize so I don't no if i have any options left. If so don't no what my options are.
I thanked you anyways for trying to help I appreciate that.
trevor7428 said:
I understood perfectly. But device manager does not pick up my tf300 anymore. It used to say Asus transformer but not after black screen. And I've had to use fastboot in the past with C:/recovery. But adb won't recognize so I don't no if i have any options left. If so don't no what my options are.
I thanked you anyways for trying to help I appreciate that.
Click to expand...
Click to collapse
If you are not able to get fastboot or adb running I think you are stucked. Only way I know of to unbrick without them is APX with NVflash, but this is not running on TF300 till now. But I heard someone is working on it, cause it is already out for the prime. So maybe in the near future we will get it for the TF300.
mikaole said:
If you are not able to get fastboot or adb running I think you are stucked. Only way I know of to unbrick without them is APX with NVflash, but this is not running on TF300 till now. But I heard someone is working on it, cause it is already out for the prime. So maybe in the near future we will get it for the TF300.
Click to expand...
Click to collapse
Well that sucks. But I really don't no if its bricked or a hardware problem. Cause everything was fine beforehand. I flashed stock then hydro rom. And was working good for couple days with reboots. Then I went to turn it on but it wouldn't. I didn't even instal a new app after flashing hydro. (Not saying its hydro rom fault. Just last thing I did before black screen)
Could a brick happen for no reason? If its hardware I wonder if its something someone could fix. That's not Asus or costing same as new tablet.
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