Database Users

Please help me..in saving my X8

Guys Please help me..
I am using Xgin Rom with Alfs kernel
I was playing with governors and overclocking then suddenly my phone switched off even on 600 Mhz with smartass v2 governor.
Now after that I have done a lot of things but my phone is not awaking.
Battery was 73% when it happend.
I tried to Flash Kernel again but it stuck at its logo and not Accessing recovery.
I flashed back to Stock kernel but any of recovery not accessible.
Finally I decide to use SEUS it says Device not recognized .
Also I tried with PC companion, it says drivers not found (notification).
I installed drivers that came with Flashtool and restarted my PC but still saying drivers not found.
I gave it to my friend who knows electronics work of phone.
After 1/2 hr. he told me hardware is safe there is no error
I also gave it to another mobile repair shop, they told me same as hardware is safe.
So now what wrong with me.... Help me guys...

How did you installed kernel without working Flashtool? Try to install Alfs or other custom kernel again and after booting press back button several times, then do full wipe. Otherwise flash stock ROM with flashtool.
If you still getting errors, install newest PC Companion and gg-drivers from flashtool.

eagleeyetom said:
How did you installed kernel without working Flashtool? Try to install Alfs or other custom kernel again and after booting press back button several times, then do full wipe. Otherwise flash stock ROM with flashtool.
If you still getting errors, install newest PC Companion and gg-drivers from flashtool.
Click to expand...
Click to collapse
I mean to say that when PC says device not recognized and Drivers not found then
I uninstalled gg-drivers then Reboot PC and Reinstall drivers and reboot.
After that it still says Drivers not found.
I tried to flash the Stock Rom with Flashtool. But at the time of boot It stuck at its logo and now no further loading of ROMS(stock or custom).
What should I have to do ? please help me..

Might have problem with your pc. If you could try it to another pc and see if it will recognize your device, but if it the same problem then why those repair shop said your hardware is safe what do they mean about that?

Mika Dee said:
Might have problem with your pc. If you could try it to another pc and see if it will recognize your device, but if it the same problem then why those repair shop said your hardware is safe what do they mean about that?
Click to expand...
Click to collapse
No buddy, I have just tried this on another PC and it says the same.
Problem is with my phone not PC.
Repair shop said that my phones hardware is not bricked, everything is Ok, but the problem is of Software.
I never told them that I have rooted it, unlocked bootloader and install kernel etc.
Now, is there any another way to repair its software ? I am crying...plz..help..

Maybe you have damaged usb-port in phone?

Hardware is ok. no problem. but its Software problem.
I have searched on XDA but no such case or post or thread found. Is that the first case of this type?

But it looks like hardware problem. Otherwise you should be able to connect device to PC at least in flash mode.
I'm too dumb to help you, sorry. 0_o

I will wait for someone to help me. After 8 hrs. I will through it in swimming pool if no one can help me(Because my father will kill me if he came to know that phone is bricked during experiments). So please is there anyone who can help me in saving my X8.

If you can show us some screenshots of the errors maybe we might have a solution for that. If what you are saying is right then it would be really hard to fix when two theory is contradicting. You can easily know if it is software or hardware related problem. Im also confused about it but for sure it has something to do with your hardware. If the phone shop said its ok or safe or whatever you call it, can you ask those person also to help you fix it if there diagnostic is "safe". I think its damage as you were playing with overclocking.

May be you are right ? I will do this and ask them for help.
And how can I take Screenshots with Busted X8. No another camera.Sorry.

I am not into developing stuff.. but
. still wanna help you ..... try other USB wire... might b am prob in it

ok . I will check it.
EDIT:1
I recently used another USB cable. prob still exists.
I am going to repair shop for help.
EDIT:2
Repair shops dropeed their screw driver in this case.
Software repair shops just holding their heads for solution.
They confirmed it as software problem not hardware.
Asking me for giving them 2hrs. to understand the software problem.
Now there is a hope for my X8.

Use your pc button print screen! Download new pc companion and install all dtivers for x8! Its driver problem
Sent from my X8 using XDA App

Recently repairer told me that by overclocking the CPU beyond its capacity has deleted some programs stored in the memory locations of CPU.
So it will take a long time to repair it. They need a perfect programmer that knows machine language or assembly language for operating their machine.
So guys beware of OVERCLOCKING.

The arm cpu is "hardwired",you can't reprogram a cpu.If your phone boots to screen logo there can't be something wrong with the cpu.(Correct me if I am wrong)Did you test with adb

alfsamsung said:
The arm cpu is "hardwired",you can't reprogram a cpu.If your phone boots to screen logo there can't be something wrong with the cpu.(Correct me if I am wrong)Did you test with adb
Click to expand...
Click to collapse
But after sometime when returned to Stock kernel, Boot logo disappear and there was a black screen with a glow.
If ARM can't be rewrite then is there a possibility of replacing it with same ARM cpu or something different. Sorry for noob question

easy way is go back to stock
Sent from my X8 using xda premium

If flashtool work I would first try to reflash stock baseband,kernel and rom with flashtool.Se here for .ttf downloads

The phone it recognised by S1tool?
If yes, the flash mode work and you can repair it
try those solutions here:
http://forum.xda-developers.com/showthread.php?t=1356349

Rogers focus stuck in loop... Any ideas?

I too have a focus that is stuck in a loop at the Samsung logo. I bought it like that thinking I might be able to resurrect it as another toy. I have had lots of experience with Samsung, HTC and Sony droid phones, this would be the first WP.
It is a I917R on Rogers, there is no hardware revision under battery. I am assuming it is V1.3 as I have only seen software for the that version posted. I do not know how the phone got to its present state. They just said it happened during normal use?
I can get to both download mode and factory reset. I have flashed the stock rogers files without errors, but I never get the screen connecting to pc. The phone just restarts after successfully flashing, only to reboot continuously. I have been able to install MAGLDR and flashed every v1.3 ROM i could download. All without errors, just the same outcome they all just keep displaying Samung logo and then reboot. Only thing I noticed is that when I flash MAGLDR and custom ROMs it takes the phone longer to reboot.
I never get the connect to pc if I hold camera and power, nor do I ever get that screen when I flash a ROM.
Not sure if situation is similar... I am puzzled?

Your situation is very similar with other folks' here, unfortunately. It's not clear what causes it and there's no solution as of yet. For some, re-flashing worked. For others, a new battery. Most are stuck on loop...
When you connect the phone to USB when in download mode, what do you get?

When I boot to download mode I can flash Rom with WP7. I get to the yellow triangle download mode and flashes ok, no errors. Just noticed that it never goes to connect to pc mode.
Same with when I format, no connect to pc mode.
Nothing I try seems to help.

blackangel21 said:
When I boot to download mode I can flash Rom with WP7. I get to the yellow triangle download mode and flashes ok, no errors. Just noticed that it never goes to connect to pc mode.
Same with when I format, no connect to pc mode.
Nothing I try seems to help.
Click to expand...
Click to collapse
I see. What messages do you get when you connect the phone to the PC via USB, in either mode?

No messages, just shows up as Samsung USB composite device, Samsung mobile modem and Samsung mobile modem diagnostic serial port in download mode.
In magldr it shows up add Microsoft USB sync.
The only thing I forgot to mention was that when I flash with WP7 it finished without error in 90 seconds, but on the phone it says it will take 10 minutes.

Not sure what more I can add...
You could try different downloaders. Please see this thread for 7.41 downloader, maybe that helps?

Tried both, same outcome... No errors, just keeps rebooting... No Connect to PC message.

Im having the same problem. And i can see many other people who are having the same issue also. So i think its time to dump those phones, not worth a penny. The one i have in here was actually working, i followed all the directions in order to flash it. And still the phone got stuck into that bootloop. Its ridiculous from what i can see. I think ive read once you put that SDmini in it the phone will use it for the OS. But the one i had was working actually without it, i could turn it off as many times as i wanted and nothing happened. But if i tried a factory reset data would stay and diagnosis mode wasnt working. So i decided to flash it. Big, huge mistake! Hope you have better luck than i did. Because im dumping this one....

Same problem here, ive checked a couple of threads and no solution so far

[Q] Help! Lumia 520 dead during restoring from WP10 preview

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

Any help with fully bricked device

Hello!
THink I have bricked my phone, but just checking before I go through what I suppose is a long process with oneplus.
Looking for any help. I had a working device - unlocked bootloader and installed TWRP and magisk using MauronofrioTool. ok - however, I found out I couldn't use a fingerprint security option on that would have been anoying. So... Long story short. I used MauronofrioTool to relock bootloader. Oops - so that didn't work. THen found out I couldn't do anything except stare at g.co/ADH message on my screen. Couldn
't get to fastboot or TWP. ANyway, so I managed to up and down volume and enter into TWRP. Was still connecting to the tool, so I downloaded factory Zips and tried to install via tool after unlocking - Seemed to be working ... but it stopped mid way through a process and hasbn't come back! NOthing at all. I wonder if I could have triggered an OEM thing? ANyway - literally nothing no buttons work no screen action. I see a QUSB_BULK_CID:etc number when connecting the phone, but that is it. No fast boot or any other actions available.
PLease, pretty devastating, Anyone know if I can do anything?

I'm no pro but I use this tool which helped me:

henk-jan said:
I'm no pro but I use this tool which helped me:
Click to expand...
Click to collapse
Thank you. I feel I am little past this stage now though.. Also trying the brick reprieve software . Just can't get my computer to recognise the phone now. No ability to get to emergency download path - think it is my crappy cihinese pc (old Huawei tablet basically) or Windows via apple that have me stranded.
**********SOLVED
THe crappy Chinese language Windows tablet worked as the unbrick OP said WIndows would. Must be a kink in the Windows via Mac that could get me into the situation, but not out.
Very relieved... Even though I still am not 100% sure what I actually ended up clicking to get it to register and connect with the unblock tool (which of course was in Chinese) hahaha.
Cheers
CHeers though

Glad you got it sorted out! Cheers

Need Help, please
Just received my OnePlus 8 pro, decided to Root and unlock the bootloader---this went fine.
I then went and upgraded to Android 11 DP3.
I'm now only able to get into Fastboot. at points it will try to boot but only get to the logo screen and then goes black.
When the phone boots up, it goes to Qualcomm CrashDump Mode.
I've been attempting to solve this for half the day with no luck. I've tried Msmtool, but it doesn't recognize the device, even after loading drivers again.
Is there a way to load a ROM from fastboot mode?
Hoping someone can assist, this is super frustrating and I would appreciate any help, please.
Rick

rickhurl said:
Just received my OnePlus 8 pro, decided to Root and unlock the bootloader---this went fine.
I then went and upgraded to Android 11 DP3.
I'm now only able to get into Fastboot. at points it will try to boot but only get to the logo screen and then goes black.
When the phone boots up, it goes to Qualcomm CrashDump Mode.
I've been attempting to solve this for half the day with no luck. I've tried Msmtool, but it doesn't recognize the device, even after loading drivers again.
Is there a way to load a ROM from fastboot mode?
Hoping someone can assist, this is super frustrating and I would appreciate any help, please.
Rick
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-8-pro/how-to/rom-stock-fastboot-roms-oneplus-8-pro-t4083997

cultofluna said:
https://forum.xda-developers.com/oneplus-8-pro/how-to/rom-stock-fastboot-roms-oneplus-8-pro-t4083997
Click to expand...
Click to collapse
Thanks so much. I ended up getting Msmtool to work. Although my device wasn't on (black screen) and it didn't fully show up in the tool, I decided to start the process anyway and it began to load.
I've been on here for over 10 yeas (XDA) I've just lost my account info and made a new one.
Thanks for taking the time to respond. Much appreciated.

Lumia 520 Unable to enter flashing mode

Hello!
I recently got my hands on a Nokia Lumia 520 for tinkering with. Its running on really old firmware, and I figured before I try anything weird, I'd mess around with it in its stock state. Thus, I tried updating the firmware.
The internal updater returned an error, stating that it could not contact the server for whatever reason. I figured this is most likely due to the Windows phone being discontinued, so I scoured the internet for firmware files. I eventually stumbled upon a YouTube guide that linked to a guide on Microsoft's Own guides page. It explained how to reinstall the firmware to a stock state. Desperate for progression. I gave it a shot.
The guide provided the "windows Device recovery tool", Which I would install on my windows 11 machine. I then proceeded to run the software and plug in the phone. HURRAY! It was able to tell me exactly what type of phone it was. Clicking the option to proceed, I was shown a screen explaining just how dated my firmware was. Suggesting It would fetch newer if not the latest firmware for me. I clicked on install and it started downloading.
I waited patiently for the software to download the firmware. After which it went to the installation screen. It then attempted to put the phone in flashing mode. Explaining that in this mode, the phone would restart, then have a blank screen. Instead what happened was that the system restarted normally, asking me to unlock the device. I wondered if maybe I had been impatient, so I waited for another while. The phone restarted again, still on the normal lock-screen. This happened another two times before the Recovery tool gave up and told me it had failed.
My question: Is there any reason why it would do this? Are there any methods to get it into flash mode?
I would hate to discard the potential of this device simply due to the inability to flash it. And I really hope it can be helped. Please let me know if there's anything else I should share about this. I'll happily take any help I can get!
Thanks in advance!
Edit, after a lot of trial and error, I managed to force it into flashing mode. Turns out the guides I followed missed a step. Pressing the Power and Camera buttons did the trick