Database Users

[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

Possible working LG one click root tool.

Hey all I don't have an LG G4 but I have a G3 which just got a security update yesterday (trying to block root) which I rooted. I'm thinking that the two phones are pretty similar so it is worth a shot to try the same method on both. Is anyone willing to try my root script on their G4. Worst case scenario it doesn't work. But it won't brick anything. It is based on the LG one click root tool. If anyone is interested you can check out my post in the Sprint LG G3 forum here on xda. link
Thanks for the help.

l33tlinuxh4x0r said:
Hey all I don't have an LG G4 but I have a G3 which just got a security update yesterday (trying to block root) which I rooted. I'm thinking that the two phones are pretty similar so it is worth a shot to try the same method on both. Is anyone willing to try my root script on their G4. Worst case scenario it doesn't work. But it won't brick anything. It is based on the LG one click root tool. If anyone is interested you can check out my post in the Sprint LG G3 forum here on xda. link
Thanks for the help.
Click to expand...
Click to collapse
I tried, doesnt work. Gets to the part where I have to put it in download mode and nothing happens. Thanks for trying though :good:

painedglass said:
I tried, doesnt work. Gets to the part where I have to put it in download mode and nothing happens. Thanks for trying though :good:
Click to expand...
Click to collapse
Did you put your phone in download mode manually? It takes a minute after you enter download mode. Also if you enable daig mode in the dialer ##DIAG# or ##3424# it should automatically put you into download mode when running the script however you may need your SPC/MSL to enable diag mode.

Yeah, exactly as the script told me to. Hold the power button up and plug the usb cable in. Download screen pops up with a progress bar and nothing, all the while the command prompt says waiting (for the download to begin I assume) I left it like that for appx. five minutes so I popped the battery back out. I tried three times and
always the same result. Should I leave it longer?

painedglass said:
Yeah, exactly as the script told me to. Hold the power button up and plug the usb cable in. Download screen pops up with a progress bar and nothing, all the while the command prompt says waiting (for the download to begin I assume) I left it like that for appx. five minutes so I popped the battery back out. I tried three times and
always the same result. Should I leave it longer?
Click to expand...
Click to collapse
No sounds like you did it correctly. You may have to unplug the device once it enters download mode and plug it back in.
Did you check device manager to make sure that your phone is detected and what com port it is on?
If you see your phone in device manager try opening cmd and navigating to the directory where LG Root Script.bat is and run the following replacing the # with your com port number.
Code:
Send_Command.exe \\.\COM#
If it works it should show a # prompt. If that works then we should be able to root it. It is just a matter of playing with what commands we can and cannot run in download mode. When you are done you can type
Code:
LEAVE
and your phone will reboot.
As I mentioned earlier I don't have a G4 so things might be a bit different but not that much.

Its listed under portable devices.....not sure how to figure out the port thing though.
---------- Post added at 11:23 AM ---------- Previous post was at 11:12 AM ----------
Ok, my COM ports are 0004 or 0003 how do I enter the text into the command prompt? I copied and pasted the send command and after I put in lets say 0004 it will throw back "special command: Enter, Leave" and it sends me back to c:\ If you can walk me through this final step, we may get this.

painedglass said:
Its listed under portable devices.....not sure how to figure out the port thing though.
Click to expand...
Click to collapse
It should be listed under "Ports (COM & LPT)" If it isn't then your computer isn't detecting your phone correctly hence it getting stuck in download mode and not rooting.
OK just got your updated post. Use COM4 in the command not COM0004
Should look like
Code:
Send_Command.exe \\.\COM4
If that works do a ctrl+C to kill the command and run the following.
Code:
Send_Command.exe \\.\COM4 < installRoot
You should see about 4 or 5 hashs (#####) and then just wait about a minute or two, it will say a bunch of things and then tell you to reboot.

I also added enter after the COM#0004 then it threw up the "Enter/leave" as well as "USAGE: SEND_COMMAND.EXE [PORT]"

painedglass said:
I also added enter after the COM#0004 then it threw up the "Enter/leave" as well as "USAGE: SEND_COMMAND.EXE [PORT]"
Click to expand...
Click to collapse
get rid of the # and the 0's should look like this
Code:
Send_Command.exe \\.\COM4 < installRoot

This is a bit too advanced for me. I'm running windows 10 and I'm spinning my wheels here because there are no ports listed in my device manager. I keep copying and pasting but it does nothing. I'm Not sure what to do now. Maybe someone else with a bit more experience can help.

are we ok to post here think it worked
http://imageshack.com/a/img908/9774/V8jIv2.jpg
http://imageshack.com/a/img537/2502/XYIm5B.jpg

What does root checker say?
Poslano sa mog LG-D802 koristeći Tapatalk

l33tlinuxh4x0r said:
Hey all I don't have an LG G4 but I have a G3 which just got a security update yesterday (trying to block root) which I rooted. I'm thinking that the two phones are pretty similar so it is worth a shot to try the same method on both. Is anyone willing to try my root script on their G4. Worst case scenario it doesn't work. But it won't brick anything. It is based on the LG one click root tool. If anyone is interested you can check out my post in the Sprint LG G3 forum here on xda. link
Thanks for the help.
Click to expand...
Click to collapse
You now have your own thread here in the LG-G4 General section

looks like lg_root.sh not starting to work
somything wrong with rights?

gavo84 said:
are we ok to post here think it worked
http://imageshack.com/a/img908/9774/V8jIv2.jpg
http://imageshack.com/a/img537/2502/XYIm5B.jpg
Click to expand...
Click to collapse
What was verdict?? What carrier r u on
Sent from my VS986 using Tapatalk

Syrop said:
looks like lg_root.sh not starting to work
somything wrong with rights?
Click to expand...
Click to collapse
Yup, write protection is on just like the Note4 and other devices on lollipop.

The one click method adds viruses and Trojans to ur pc. Good luck
BAD ASS NOTE 4 & LG G4

Oh lord, please let this work. ?
Sent from my G4 whilst wishing for root

Windows 10 DOES NOT recognize LG devices properly in DL mode. I was just restoring a G2 to stock with LG Flash tool, it wouldn't recognize properly in 10. Went to 8 and worked beautifully. =

BACARDILIMON said:
The one click method adds viruses and Trojans to ur pc. Good luck
BAD ASS NOTE 4 & LG G4
Click to expand...
Click to collapse
Before you spout off, explain your comments. Show proof of the issue.

Amazon Blu R1 HD [Firmware] [Restore] [Unbrick] [Unroot]

How to Firmware Restore the Amazon Blu R1 HD
With the Help of many of you at XDA we have put together a working scatter file and I have pulled the Firmware from the device so that we can now restore this phone.
View attachment 3826922
STEPS TO RESTORE DEVICE AND BE ABLE TO HAVE ADS AND OTA UPDATES WORKING AGAIN
1. Download SP_Flash_Tool_BLU_R0010UU_V6.4_Firmware.zip
2. Extract the SP_Flash_Tool_BLU_R0010UU_V6.4_Firmware.zip to your desktop. Note 7zip is great to extract files.
3. lauch Flash_tool.exe
4. select scatter-loading and browser to load MT6735_Android_scatter_R1_HD_Amazon.txt
5. click download button to start.
6. now plug your phone into the computer. to boot the device to preloader and start the flash. You can do it two ways: 1. power off the phone and flash will start or 2. From a powered off stat power on the device while plugged into the computer. either way will start the sp flash tool.
7. once the flash is complete you can unplug the device and reboot it with the power button. Congrats you have fully restored your Amazon Blu R1 HD. Bonus you have also enabled bootloader unlocking if you want it.
Tutorial Video with all the steps need to restore.
NOTE: This has been fully tested on the Amazon R1 HD 16GB model but should work on the 8gb also.

You're the man!

Hi, I keep getting this error:
BROM ERROR: S_DL_GET_DRAM_SETTING_FAIL(0x13BE)
[EMI]Obtain DRAM Failed!
[HINT]:
Please check your load matches to your target which is to be downloaded
Do you have any idea how to fix it? Thanks.

Dude this doesnt work for me.
When I plug in my phone, a popup from Flash tools comes up saying, "PMT changed for the ROM; it must be downloaded."
Then what?

johnsmithsir12 said:
Dude this doesnt work for me.
When I plug in my phone, a popup from Flash tools comes up saying, "PMT changed for the ROM; it must be downloaded."
Then what?
Click to expand...
Click to collapse
EDIT - DO NOT USE THE DOWNLOAD+FORMAT MODE EVER ON THE R1, IT WILL RESULT IN A BRICK, IT MAY WORK ON OTHER MTK MODELS, BUT EXPERIENCE HAS SHOWN IT WILL BRICK THE R1 HD!!!! DOWNLOAD ONLY IS THE ONLY SAFE METHOD!!
Occurs if the names or addresses of the blocks in the scatter differ from the table inside the phone (PMT).
Thats not good, i suggest maybe checking the scatter file making sure its not currupt... Or try the following alternate solution....
http://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
This also seems to be a solution,but perhaps more dangerous last ditch effort maybe?? The video is for a different MTK SoC, but from what what im reading it's the same technique across the MTK lineup..
Perform at your own discretion, not responsible for bricked devices....

kal250 said:
Occurs if the names or addresses of the blocks in the scatter differ from the table inside the phone (PMT).
Thats not good, i suggest maybe checking the scatter file making sure its not currupt... Or try the following alternate solution....
http://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
This also seems to be a solution,but perhaps more dangerous last ditch effort maybe?? The video is for a different MTK SoC, but from what what im reading it's the same technique across the MTK lineup..
Perform at your own discretion, not responsible for bricked devices....
Click to expand...
Click to collapse
I rooted my phone via this method: http://forum.xda-developers.com/r1-hd/how-to/twrp-how-to-root-t3425677
Keep in mind, only "recovery" was checked and nothing else.

yujiba said:
Hi, I keep getting this error:
BROM ERROR: S_DL_GET_DRAM_SETTING_FAIL(0x13BE)
[EMI]Obtain DRAM Failed!
[HINT]:
Please check your load matches to your target which is to be downloaded
Do you have any idea how to fix it? Thanks.
Click to expand...
Click to collapse
Try this: http://onlinejobwithoutanyinvestment.com/sp-flash-tool-errors-fix-brom-error/
Format your phone, but not the bootloader, and then try reflashing

We're seeing reports of this bricking phones. If you are considering trying it, don't! If you have bricked your phone, please join our Hangout right here and cooperate with us to find the cause of the brick and a way to unbrick it!
Join the conversation on Hangouts: https://hangouts.google.com/group/Q5wGs6508l1rqGng2
Sent from my LG G4 using XDA Labs

ColtonDRG said:
We're seeing reports of this bricking phones. If you are considering trying it, don't! If you have bricked your phone, please join our Hangout right here and cooperate with us to find the cause of the brick and a way to unbrick it!
Join the conversation on Hangouts: https://hangouts.google.com/group/Q5wGs6508l1rqGng2
Click to expand...
Click to collapse
The format method, i stumbled upon, i just added as a last ditch effort, I'm not sure whats causing the errors to begin with. The scatter addresses all still match the block addresses mapped in the new OTA, so that theory is shot, im not sure what else could be going on.

If SPFT WON'T FLASH
1. Power off your phone.
2. Hold the power and volume up buttons then choose "recovery" from the menu that shows up.
(volume buttons = up/down, power button = ok/select)
3. Now choose power off.
Doing the above makes sure your phone is COMPLETELY shut off, windows can find your phone, and SPFT will be able to flash it.
I believe that, when you use "power off", from within android, it actually puts the phone in some type of suspend or hibernation mode. I say this because you can hit the power button and it will boot very quickly after powering off within android, but from recovery it takes longer to boot. This was the case with mine.
Your only other option is to let the battery completely drain, then try SPFT.
SHOUT OUT TO ALL THE GUYS THAT ROOTED THIS SUCKER AND UNLOCKED IT! GREAT WORK! ???? :good:

burnanator said:
If SPFT WON'T FLASH
1. Power off your phone.
2. Hold the power and volume up buttons then choose "recovery" from the menu that shows up.
(volume buttons = up/down, power button = ok/select)
3. Now choose power off.
Doing the above makes sure your phone is COMPLETELY shut off, windows can find your phone, and SPFT will be able to flash it.
I believe that, when you use "power off", from within android, it actually puts the phone in some type of suspend or hibernation mode. I say this because you can hit the power button and it will boot very quickly after powering off within android, but from recovery it takes longer to boot. This was the case with mine.
Your only other option is to let the battery completely drain, then try SPFT.
SHOUT OUT TO ALL THE GUYS THAT ROOTED THIS SUCKER AND UNLOCKED IT! GREAT WORK! ???? :good:
Click to expand...
Click to collapse
Never occurred to try that, curse this trend of non removable batteries anyways -_-

kal250 said:
Never occurred to try that, curse this trend of non removable batteries anyways -_-
Click to expand...
Click to collapse
Yup. That's why i tried it. This is the first phone i have had with a non-removable battery.

johnsmithsir12 said:
Dude this doesnt work for me.
When I plug in my phone, a popup from Flash tools comes up saying, "PMT changed for the ROM; it must be downloaded."
Then what?
Click to expand...
Click to collapse
I just saw your other thread you started
http://forum.xda-developers.com/r1-hd/how-to/question-restoring-to-factory-default-t3440059
And now I see why you had this error. You have the 8gb version not the 16gb. So this method uses the wrong scatter file for you phone. Please update the forum if you still have the phone and need assistance. There are some commands that you can run in adb to see the partition sizes and then with that the scatter file can be adjusted for your phone

sorry for being off topic here but i really need to know if its possible to unlock more 4g bands , in my contry they don't release the infomation of what bands the providers work so its a guessing game, since i got this phone i purchased the 4g sim card , even with the band 12 update still stuck at 3g , even with proper 4g apn still stuck at 3g wich i came to a conclusion that the 4g bands from the Blu R1 HD are not the same as my providers...in conclusion can it be done ( open up more bands to see wich band will get me the 4g) and if so please explain to me how i can do so please.

This worked for me, but I had to factory reset after because OTA was still detecting root.

Help me!
hello, I do all the steps but remains in the logo and reboots

THIS DOES NOT WORK WITH 8GB/1GB version :'(

Hello,
I just want to unroot my Blu R1, what should I do?

DOA Bricked
Any hope for an R1 which will now not even power up?

This will not work on any of the latest versions. My model is a 2GB/16GB - I was on Coltons root and tried this to go back to stock with my phone now stuck in boot loop.
Do not use this method.

[UNBRICK] Xiaomi Mi Max 64/128 GB a.k.a Helium - %100 Tested Recover From Hard Brick

Ok guys here is the step by step even for noobs how to unbrick Xiaomi Mi Max (helium).
If you have access to fastboot jump to step 11
Requirements :
* MiFlash Beta :Download Here
* MiFlash 20151028 : Download Here
* Global Fastboot Rom : Download Here
* Xiaomi Qualcomm Drivers
* Screw and tools.
* Paper clip or cable
* For sure Usb Cable.
Now if you all ready lets continue repair. First of all you need to open back cover.
1) Open Back cover and disconnect fingerprint sensor and battery. Dont connect battery till you finish whole process. (How to disassemble video : https://www.youtube.com/watch?v=YMG04GqVU_0&t=64s)
2) Make a paper clip to setup short circuit in your mainboard. Here are the testpoints. https://s15.postimg.org/s0j0qhq3v/Xiaomi_Max_Test_Points.png
3) Ok here is the hardest and trickiest one. While you are holding paper clip or cable with those testpoint you need to connect phone to pc. My suggestion 1st connect usb cable to phone then make short circuit then connect to pc.
* One more time you need to connect phone to pc while those two testpoints connected to eachother with a paperclip or a cable.
4) Here is the second tricky part. Unzip rom file. Important part is the name of folder. Please try to make it as short as possible.
Ex : C:\mimax\
So after extraction your folder will looks like this : http://oi63.tinypic.com/334rr11.jpg
5) You need to install both MiFlash versions. They are 2 different software so you shouldnt see any errors like "it is already installed".
6) Go To C:\XiaoMi\XiaoMiFlash and run XiaoMiFlash.exe as an administrator. Click browse and choose your rom folder. NOT IMAGES FOLDER ROM FOLDER !!!! ( Ex : C:\mimax)
7) Click "refresh" you will see COM port and click "flash" If you dont see any COM port here first check if you installed drivers correctly. If drivers are installed correct please go back to step 3 and try again.
8) Install will start and continue and %99 possibly it will stop in the middle You will receive Max buffer 256 error. No worries just keep calm and take deep breath. Go to next step
9) Disconnect usb cable from pc and phone. Reconnect battery. Now voila phone will ready to work BUT NOT READY TO WORK FLAWLESS. So now put your phone to fastboot mode. Yes you read correct now your phone will be in fastboot mode even it could be ready to use but just wait for next step.
10) Fastboot mode : Volume Down + Power button you will see fastboot screen and connect to PC.
11) Now close old MiFlash and run the normal one from either desktop or C:\Program Files (x86)\Xiaomi\MiPhone\MiFlash.exe or C:\Program Files\Xiaomi\MiPhone\MiFlash.exe.
12) Choose your rom folder. NOT IMAGES FOLDER ROM FOLDER !!!! ( Ex : C:\mimax).
13) Click "refresh" and this time you have to see device serial number on device tab. Now click flash and let process finish. It takes around 3-5 minute and phone will reboot by itself.
Now re-assemble your phone. DONT FORGET TO CONNECT FINGERPRINT SENSOR. Now you are totally ready.
Tried 5 times with my very own Xiaomi Mi Max 128 GB.

Different reactions
Hi,
My device could still boot on fastboot mode, and flashes successfully through it on MiFlash Beta. However, the device remains stuck on Mi logo. I've already tested flashing on EDL mode apparently successfully, with the same results. I've flashed TWRP, but the device don't enter recovery mode. What can I do? Any suggestion will be welcome.

benzersizadam said:
Many thanks for this thread, I stuck on my mi max with no reaction at anything, I read more than 100 threads, I tried testpoint, DFC (deep flash cable), click inside usb terminal to pc, windows 8, 7 10, 32 bits, 64 bits, programms like qfil (qpst), flasher tools for other phones and nothing, before with other apps at first second gives me error "can not read from port COM...", and now at least advance to 5 seconds with same error, I need to know it is neccesary too disconnect, remove two plastic cables down where places the battery
Click to expand...
Click to collapse

Working also with Hydrogen. Thanks.

@benzersizadam
This is why XDA is a great FORUM! Thank you for writing this thorough solution!
My device is up and running currently with MIUI 8! It went from a dead brick to a productive device again! I was almost giving up hope! You saved the day! It was a lot of work, but it is great seeing the device alive again.
I would just add that taking the cover off doesn't even need a tool like in the original disassembly youtube video: https://www.youtube.com/watch?v=dULcMWCEgEc
Yay!

coffee-turtle said:
@benzersizadam
This is why XDA is a great FORUM! Thank you for writing this thorough solution!
My device is up and running currently with MIUI 8! It went from a dead brick to a productive device again! I was almost giving up hope! You saved the day! It was a lot of work, but it is great seeing the device alive again.
I would just add that taking the cover off doesn't even need a tool like in the original disassembly youtube video: https://www.youtube.com/watch?v=dULcMWCEgEc
Yay!
Click to expand...
Click to collapse
Can you kindly explain some tips or secret to get unbrick cause mine is more than 4 months almost totally dead, just receive charge the battery but any signal of life in display, don´t enter recovery, fastboot, in mode EDL pc identifies like hs-usb qdownload 9008 but in 4 or 5 seconds cut conection with pc. and in my country nobody knows about Xiaomi. thanks in advance

SubwayChamp said:
Can you kindly explain some tips or secret to get unbrick cause mine is more than 4 months almost totally dead, just receive charge the battery but any signal of life in display, don´t enter recovery, fastboot, in mode EDL pc identifies like hs-usb qdownload 9008 but in 4 or 5 seconds cut conection with pc. and in my country nobody knows about Xiaomi. thanks in advance
Click to expand...
Click to collapse
Hi @SubwayChamp Everything I did was in the post and video from above in the first post by benz....
His instructions were perfect along with the youtube video. It's tricky, true, but with patience you can go through the steps and get your device running again. I was so glad that @Qulox gave me this link to this thread.
As you go through the steps, if you get stuck, we can try to give you advice.

This works for Hydrogen as well.
Many thanks

I have two dead mi max. One 128gb helium and one 32gb hydrogen.
128gb helium is completely lifeless. No charging led, no vibrations, no fastboot mode. Though i could bring it up to edl mode showing right qualcomm device in device manager. I tried flashing stock rom as mentioned in this guide which rather went successful without giving any error, even while battery connector was removed.
But mobile is still in same lifeless condition. Other than flashing process going through, it didnt make any difference. Dont know whats wrong. Also i didnt have to use two miflash versions as mentioned in steps as flashing process didnt give any error.
32gb hydrogen, boots up in flashboot mode, shows charging led, mi logo even edl model worked without any issue. It even boots up, but gives error of encryption unsuccessful asking me to reset device. I tried factory reseting it. Tried flashing twrp and wiping, formatting data, changing file system to all formats like fat, f2fs, ext1, ext2, ext3, ext4. Tried flashing crdoid and RR based on orea. Nothing working.
With twrp it keeps bootlooping showing mi logo. And with stock rom, recovery shows up encryption error. Followed procedure mentioned in this guide as well.
Is there anything am i missing or can do? Btw, bootloader is locked for both the devices. I could flash twrp referring another guide which suggested to replace stock recovery in rom files/ folder and flashing it like stock rom through miflash tool.

Battery problems? in the 128 especially?
If "nothing works" through any normal software methods, the ram &/or ROM memory chips might have become semi-defect. They are not eternal . . .

cobben said:
Battery problems? in the 128 especially?
If "nothing works" through any normal software methods, the ram &/or ROM memory chips might have become semi-defect. They are not eternal . . .
Click to expand...
Click to collapse
Tried replacing battery as well. Surprising thing is completely dead 128gb helium does boot up in edl mode with flashing working perfectly file in miflash tool. Dont know how reliable that software is.....

Hello,
trying with both Helium & Hydrogen. Still on error like say these logs.
log#1
Code:
[0,02 COM7]:[COM7]:start flash.
[0,02 COM7]:received hello packet
[0,02 COM7]:can not found programmer file.
log#2
Code:
[0,00 COM7]:[COM7]:start flash.
[2,03 COM7]:cannot receive hello packet,MiFlash is trying to reset status!
[4,56 COM7]:cannot receive hello packet,MiFlash is trying to reset status!
[7,11 COM7]:try to reset status.
[7,13 COM7]:Switch mode back
[7,13 COM7]:cannot receive hello packet,MiFlash is trying to reset status!
[7,14 COM7]:Riferimento a un oggetto non impostato su un'istanza di oggetto.
Hope anyone can help me. What's my wrong following the guide.
Thanks

harpy.eagle said:
Tried replacing battery as well. Surprising thing is completely dead 128gb helium does boot up in edl mode with flashing working perfectly file in miflash tool. Dont know how reliable that software is.....
Click to expand...
Click to collapse
Hi there.. The link of video & image of test points is not working. Can anybody please share working links

Hi there.. The link of video & image of test points is not working. Can anybody please share working links

rizkhan77 said:
Hi there.. The link of video & image of test points is not working. Can anybody please share working links
Click to expand...
Click to collapse
This is the video of Test Point https://youtu.be/SqcVY8IWkZI

benzersizadam said:
Ok guys here is the step by step even for noobs how to unbrick Xiaomi Mi Max (helium).
If you have access to fastboot jump to step 11
Requirements :
* MiFlash Beta :Download Here
* MiFlash 20151028 : Download Here
* Global Fastboot Rom : Download Here
* Xiaomi Qualcomm Drivers
* Screw and tools.
* Paper clip or cable
* For sure Usb Cable.
Now if you all ready lets continue repair. First of all you need to open back cover.
1) Open Back cover and disconnect fingerprint sensor and battery. Dont connect battery till you finish whole process. (How to disassemble video : https://www.youtube.com/watch?v=YMG04GqVU_0&t=64s)
2) Make a paper clip to setup short circuit in your mainboard. Here are the testpoints. https://s15.postimg.org/s0j0qhq3v/Xiaomi_Max_Test_Points.png
3) Ok here is the hardest and trickiest one. While you are holding paper clip or cable with those testpoint you need to connect phone to pc. My suggestion 1st connect usb cable to phone then make short circuit then connect to pc.
* One more time you need to connect phone to pc while those two testpoints connected to eachother with a paperclip or a cable.
4) Here is the second tricky part. Unzip rom file. Important part is the name of folder. Please try to make it as short as possible.
Ex : C:\mimax\
So after extraction your folder will looks like this : http://oi63.tinypic.com/334rr11.jpg
5) You need to install both MiFlash versions. They are 2 different software so you shouldnt see any errors like "it is already installed".
6) Go To C:\XiaoMi\XiaoMiFlash and run XiaoMiFlash.exe as an administrator. Click browse and choose your rom folder. NOT IMAGES FOLDER ROM FOLDER !!!! ( Ex : C:\mimax)
7) Click "refresh" you will see COM port and click "flash" If you dont see any COM port here first check if you installed drivers correctly. If drivers are installed correct please go back to step 3 and try again.
8) Install will start and continue and %99 possibly it will stop in the middle You will receive Max buffer 256 error. No worries just keep calm and take deep breath. Go to next step
9) Disconnect usb cable from pc and phone. Reconnect battery. Now voila phone will ready to work BUT NOT READY TO WORK FLAWLESS. So now put your phone to fastboot mode. Yes you read correct now your phone will be in fastboot mode even it could be ready to use but just wait for next step.
10) Fastboot mode : Volume Down + Power button you will see fastboot screen and connect to PC.
11) Now close old MiFlash and run the normal one from either desktop or C:\Program Files (x86)\Xiaomi\MiPhone\MiFlash.exe or C:\Program Files\Xiaomi\MiPhone\MiFlash.exe.
12) Choose your rom folder. NOT IMAGES FOLDER ROM FOLDER !!!! ( Ex : C:\mimax).
13) Click "refresh" and this time you have to see device serial number on device tab. Now click flash and let process finish. It takes around 3-5 minute and phone will reboot by itself.
Now re-assemble your phone. DONT FORGET TO CONNECT FINGERPRINT SENSOR. Now you are totally ready.
Tried 5 times with my very own Xiaomi Mi Max 128 GB.
Click to expand...
Click to collapse
hi, could someone share with me the miflash beta? I can download the rest but I cannot download the beta one.
thanks

Wanted to say thank you was able to recover my mi max 64gb unit.

[Hard Brick] Nexus 6P 7.1.2 Beta 2 [Solved]

Hey guys I just installed the full image of 7.1.2 beta 2 over top of beta 1 using Flashfire without the bootloader and modem selected and all went fine until I decided to use Flashfire to upgrade the bootloader and modem forgetting that we must use Fastboot as I am new to Flashfire and I was reading all through the beta thread before I did it and didn't understand we still must use Fastboot so anyways I am stuck in a hard brick now with the phone not powering on at all and can't do anything to restore it as my Windows 10 now detects the phone as unknown device (device descriptor request failed) is there anything I can do at this point as I just bought this phone used.
The error that I got in Flashfire was that the device storage is full when updating the bootloader as the modem went fine.

@rmorris003
You said the phone won't even power on. You mean no Google? Hold the power button down for a couple of minutes and see if it will reboot. If not put it on a charger, and after fully charging try the long press power button again. If you can get it to start, try to put it in fastboot mode. (ie. power+vol dn). If you can get to bootloader you can send fastboot commands and fix it. If you can get to this point, there are instructions here.

rmorris003 said:
Hey guys I just installed the full image of 7.1.2 beta 2 over top of beta 1 using Flashfire without the bootloader and modem selected and all went fine until I decided to use Flashfire to upgrade the bootloader and modem forgetting that we must use Fastboot as I am new to Flashfire and I was reading all through the beta thread before I did it and didn't understand we still must use Fastboot so anyways I am stuck in a hard brick now with the phone not powering on at all and can't do anything to restore it as my Windows 10 now detects the phone as unknown device (device descriptor request failed) is there anything I can do at this point as I just bought this phone used.
The error that I got in Flashfire was that the device storage is full when updating the bootloader as the modem went fine.
Click to expand...
Click to collapse
Hello... Well if your device is recognized as unknown, you could try to give this a shot:
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Try to install Qualcomm driver first check the device manager. If you see your phone recognized as:
HS-USB QDLOADER 9008
You may be lucky!
Good luck...

5.1 said:
Hello... Well if your device is recognized as unknown, you could try to give this a shot:
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Try to install Qualcomm driver first check the device manager. If you see your phone recognized as:
HS-USB QDLOADER 9008
You may be lucky!
Good luck...
Click to expand...
Click to collapse
I will try this when I get back from work, I just cant get my pc to see it as anything other than unknown device as it says this is the best driver for it.

rmorris003 said:
I will try this when I get back from work, I just cant get my pc to see it as anything other than unknown device as it says this is the best driver for it.
Click to expand...
Click to collapse
I see... There's a txt file in the driver folder. Follow its instructions.
Good luck...

5.1 said:
I see... There's a txt file in the driver folder. Follow its instructions.
Good luck...
Click to expand...
Click to collapse
I am stumped, I have disabled driver enforcement and can't get any drivers to see my phone so I am not sure what to do.

rmorris003 said:
I am stumped, I have disabled driver enforcement and can't get any drivers to see my phone so I am not sure what to do.
Click to expand...
Click to collapse
You disabled driver signature and rebooted your computer? Then installed Qualcomm drivers from the thread I linked you to? I think you have to reboot your computer once more...
Good luck...

I held the power and vol down and now it shows up under com ports so this is a good sign.

Ok got bootloader back and now put twrp on, I had to use qfil with nexus6p_fix_bricked but it got stuck at writing system.img but atleast the phone is on now.
Flashed the 7.1.2 beta 2 full image using the fastboot method included and all is back to normal.
Thanks so much for the help.

rmorris003 said:
Ok got bootloader back and now put twrp on, I had to use qfil with nexus6p_fix_bricked but it got stuck at writing system.img but atleast the phone is on now.
Flashed the 7.1.2 beta 2 full image using the fastboot method included and all is back to normal.
Thanks so much for the help.
Click to expand...
Click to collapse
Wow glad it worked for you... You might push the thanks button in the OP of the thread where you found the debrick tools and thanks @tenfar since he offered the solution. He already saved a few N6P devices. I only linked you to his thread which you could have found yourself anyway...
Cheers...

5.1 said:
Wow glad it worked for you... You might push the thanks button in the OP of the thread where you found the debrick tools and thanks @tenfar since he offered the solution. He already saved a few N6P devices. I only linked you to his thread which you could have found yourself anyway...
Cheers...
Click to expand...
Click to collapse
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.

rmorris003 said:
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
Click to expand...
Click to collapse
You could report your experience in the other thread. Maybe it could help other users who faced the issue you had. :good:
Cheers...

rmorris003 said:
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
Click to expand...
Click to collapse
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!

Clarkeofcurtis said:
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Click to expand...
Click to collapse
I have the same exact problem, everytime i try to flash with qfil it says it can't connect to my COMPORT

Clarkeofcurtis said:
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Click to expand...
Click to collapse
Falitheman said:
I have the same exact problem, everytime i try to flash with qfil it says it can't connect to my COMPORT
Click to expand...
Click to collapse
Hello,
Someone mentioned this in another post:
Hold volume up and plug the USB cord to.your computer and start qfil flash. Keep holding volume up until the flash ends...
Good luck...

5.1 said:
Hello,
Someone mentioned this in another post:
Hold volume up and plug the USB cord to.your computer and start qfil flash. Keep holding volume up until the flash ends...
Good luck...
Click to expand...
Click to collapse
So i have some good news...it connects now. it says start sending programmer but then it says download failed: unable to download flash programmer using sahara protocol and then it fails. Any help?:crying:

Falitheman said:
So i have some good news...it connects now. it says start sending programmer but then it says download failed: unable to download flash programmer using sahara protocol and then it fails. Any help?:crying:
Click to expand...
Click to collapse
Hey,
What version of qpst did you install?
Good luck...

5.1 said:
Hey,
What version of qpst did you install?
Good luck...
Click to expand...
Click to collapse
I am using 2.7.441
Update: It seemed to be working for a second but then it says download failed: qsahara server fail: process fail. Any idea what that means? I really need my phone back

Falitheman said:
I am using 2.7.441
Update: It seemed to be working for a second but then it says download failed: qsahara server fail: process fail. Any idea what that means? I really need my phone back
Click to expand...
Click to collapse
Hey,
Google qpst 2.7.453
It's easy to find. Scan the files on virustotal.com though.
Maybe the older versions are incompatible...
Good luck...

5.1 said:
Hey,
Google qpst 2.7.453
It's easy to find. Scan the files on virustotal.com though.
Maybe the older versions are incompatible...
Good luck...
Click to expand...
Click to collapse
I tried with the version you suggested and i got the same error i just had. Can you send me your version so i can see if that works?