lumia 520 stuck on red screen with nokia logo after trying to rollback to wp8.1 - Nokia Lumia 520 Questions & Answers

Yesterday I tried to upgrade to windows phone 10 technical preview, but it got stuck on cog wheel page screen with no progress for 2 hours.
I searched a bit on net and found that removing the sd card helped, so I removed the battery between update and removed the battery and then sd card, and rebooted the device. This time it progressed but after some time it stuck in a boot loop, where it would repeatedly restart to cog wheel screen.
I tried all the reset options on the net, but it didn't work. Finally I decided to roll back to windows phone 8.1, using windows phone recovery tool. It successfully started, downloaded required file, started installation and then showed an error and after that it is stuck on a red screen with large NOKIA logo on it.
I have tried everything given here
goo.gl/UVSjQi (xda thread)
goo.gl/A8ltgT (step by step process on how to recover bricked windows phone) and a lot more places.
I think the problem is they want the device to be connected as "QHSUSB_DLOAD" but my lumia 520 is detected as "NOKIA FLASH" in windows 10, and it gives error while trying to write data to phone.
I'm trying the same process in windows 8.1 virtual machine, as I post the question here.
F.A.Q.
1. The phone in question is lumia 520
2. On pressing volume down and power key, it reboots to red screen.
3. No I didn't hard reset the phone before starting to upgrade to windows 10 technical preview.

Related

Omnia 7 stuck boot screen

Hi,
New phone and new to Windows phone 7. Classic story - the phone has stuck in boot screen, it says only "Samsung Omnia 7" and that's all. I have tried all tips I could find from internet - took the battery out and let it sit, tried to hard reset it -nothing. Actually hard reset button combination seemed not to work - when I turn it on, holding camera and volume down buttons, nothing happens, it shows boot screen and that's all. It do switch to the download mode when I turn it on holding camera and volume up buttons. I tried to reflash it (got the rom files that it came originally), and after restart the situation is the same - boot screen stuck and nothing happens.
I used WP7_downloader version 7.41, Samsung USB drivers v5.02. The weird thing was that older versions of WP7_Downloader did not work - told that flash lock was on. 7.41 seemed to work, it erased and downloaded all areas fine. I don't know if this is normal, but the flashing process itself took about 120 seconds only. I tried alternative ROM (classic I8700XXJK1), the flashing time was slightly different, but nothing changed, after flashing the device restarts and stuck to the boot screen. As I have read the flashing process should took about 10 minutes or so? I waited for about 20 minutes and nothing changed.
Can I switch the device to some debug mode or do something else that could lead me to the reason the device is not booting?
Omnia 7 stuck at boot screen after
I upgraded to Mango last week and i now too am stuck at the "Samsung Omnia 7" boot screen.
The phone seemed to do two updates, the first suceeded no problem. I started the update before going to bed. In the morning it had completed the first and was awaiting my pin code to start the device. All good.
It then prompted about the Mango update. I clicked it and left it for an hour or so. Came back and zune stated it was on the step, "restarting the phone".
The phone was showing "Samsung Omnia 7", i left it for another hour and then came back, no progress.
Nothing i've found on the net up until today has worked for me.
I can enter the format and download modes still.
This is what i've found and tried so far.
1:
answers.microsoft.com/en-us/winphone/forum/wp7-wpdevices/samsung-omnia-7-bricked-stuck-in-boot-loop/76831b31-2c5b-4d3b-8f65-06111e1f3798
(Did a device wipe to factory defaults, and its still stuck at boot screen
2:
support.microsoft.com/kb/2547687
(yes this is an older issue but it looked like it was working until it said something about "flash lock").
Next step is a complete ROM reinstall. But i'd really like to find out precisely which ROM i should try and if Mango is the actual culprit. I'd like to reinstall Mango if possible.
My Omnia 7 was bought secondhand.
I am with Telstra NextG carrier.
After mango update mine is behaving strange too. It shuts down itself randomly and it is stucking at omnia 7 screen. After a few try I am able to open it. But I noticed something, it's shutting down much more while it's connecting to web or PC. Can this be related? Because I couldn't find another reason about that.

Is my Nexus 4 bricked or irreperably broken?

Hello people,
I have a German Nexus 4 and it gets stuck in bootloop whenever I turn the power on.
I've had issues with the phone since the last few months - i.e. random reboots, random program crashes.
But recently I tried to root it in order to install the Android L developer preview. It was during the booting process, when my Nexus crashed and it has been unable to boot ever since.
When I push all three buttons (power + 2 volume rocker buttons) simultaneously, I get the fastboot screen.
Choosing the following options has these effects:
Start --> phone tries to boot but gets stuck in bootloop forever and ever
Restart bootloader --> restarts the fastboot screen
Recovery mode --> phone shows the robot with an opened belly and a red warning sign (see photograph)*
Power Off --> turns the power off
Also, it is NOT detected or recognized by my Macbook when I connect the Nexus via USB cable. So it's impossible for me to access the phone via my Macbook.
*This is the screen shown when I try to go into Recovery mode in fastboot:
[can't upload outside link to image]
So this leaves me with no options as I never get further than the 4 turning circles forever and ever.
Is my Nexus 4 broken or is there still a chance to unbrick it? (I have a MacBook, so Windows programs won't work for me)
Of course it's not possible to recognize it when OS is not running.
Download WugFresh toolkit, ADB drivers (Universal) and the factory image. Enter fastboot, connect USB and flash the image
Your phone is not hardbricked, because it boots into the bootloader.
It might be recovered if you can access it with fastboot.
Try uninstalling all related drivers and install the Naked Universal Driver.
Thanks for your replies!
Unfortunately, the programs you mentionned don't work on my Mac (they seem to be Windows-only).
Also, how can I install stuff on my Nexus? Since it is not recognized by my MacBook, I can't load any files onto my Nexus.
And since any command on the fastboot screen only leads to the phone powered off, restart of the fastboot screen or the mentionned bootloop, I cannot perform any actions on the Nexus ...
Go to a friend with Windows.
Problem solved!
Somehow after the 1000th bootloop I finally reached the screen where I could wipe the phone.
And then it finally booted! Now all the data are lost and it's like a new phone, but at least it's working again!
How long was the boot loop? Was it the new boot animation from L?
Because when you flash L, the first boot up may take up to 15 minutes, leading you into thinking it's a boot loop.

Phone doesn't react to anything, doesn't boot

I might have bricked my LG G2.
Here is everything I did:
-I rooted the phone with the IO root kit
-wanted to installed a recovery so I installed TWRP manager
-applied SD card patch
-tried to install recovery with TWRP manager several times but app always crashed
-installed SDK on the PC
-started adb and executed "adb reboot bootloader"
the phone got a backlight screen and hasnt been reacting so far.
When I held the power button the screen went black but sometimes the backlight appeard again. I don't know how to reproduce the backlight though.
adb can't detect the phone when connected to the PC.
As soon as I plug it in dozens of Partitions show up. Windows show an error message for each of these partitions. It says I have to format the volumes to use them.
After testing I realized that everytime i long-press the power button for a few seconds the windows errors start popping up.
When i long pressed the power button for 30+ seconds to completely shut it down the notification LED started blinking red 8 times in roughly second intervals. then there was a short break and the 8 blinks repeated.
Thank you for all help, it would suck to have a 1 day old phone broke...
You probably chose the wrong device in TWRP Manager. Choosing the wrong device can easily lead to a brick because TWRP Manager may attempt to flash to the wrong partition. The G2 does not have a TWRP Manager flash available due to loki, so you couldn't have chosen the right device.
Almost have the same problem... the only difference is my black screen is blinking continuously while it is connected to the mac... Seems like it tries to boot but gets blocked and retries in a loop. Tried around now for two evenings without any progress...
Anybody who can help?

Lumia 520 bricked after reset

I tried to install the Windows 10 preview on my lumia 520 but after the spinning gears it always gave back an error code when it rebooted into windows 8.1. I decided to try and reset to fix the problem. It failed after 5 minutes and gave back a sad face and does this each time I reboot. I have tried many of the fixes on the site but I cant get the phone into any other mode other than the spinning gears and sad face. It connects to the computer for a few seconds that says Nokia Bootmgr in device manager but then just disconnects. Pressing the volume down doesnt work. Any suggestions?
Windows Device Recovery Tool?
Ive tried this but the problem is the computer doesnt recognize the phone at all

BCD Error Windows Phone - Can't Reset

Phone is an HP Elite X3. Randomly got a blue screen that says error 0xc000098 and something about the \BCD file not having operating system information in it. This is after restarting the phone twice after updating it.
It is not possible to put the phone in flash mode, it just brings back the blue screen when restarted. Can't boot to OS.
Any ideas? The computer does not recognize the phone.
dfeldt91 said:
Phone is an HP Elite X3. Randomly got a blue screen that says error 0xc000098 and something about the \BCD file not having operating system information in it. This is after restarting the phone twice after updating it.
It is not possible to put the phone in flash mode, it just brings back the blue screen when restarted. Can't boot to OS.
Any ideas? The computer does not recognize the phone.
Click to expand...
Click to collapse
Any luck ?
same here...no combination of keys work..reboot loop

Categories

Resources