Related
Hello guys!
I'm kinda freakin' out here.
Here's the story:
I bought this amazing Redmi 3 Pro from China, and after waiting for 33 days, it arrived. I knew that it's important change the ROM that came with the device, so... I changed it. I'm from Brazil, so I needed a ROM with Portuguese-BR language and at least, stable. When I was going to change the ROM, my device just turn off and never turned on again.
OBS: The drivers are installed. It recognizes as "Qualcomm HS-USB QDLoader 9008", so I think that it's on EDL Mode.
OBS2: I tested flash on: Win7(x64) and Win10(x64). Neither worked.
OBS3: Every time, I get the error "Reached End of File.(0x80070026: Receiving Hello Packet.)
OBS4: I downloaded several ROMs, several versions of MiFlash (including the Beta version) and nothing passed from the error above.
OBS5: The device doesn't turn on, doesn't light on the LED, doesn't vibrate etc.
I believe that the problem resides on the missing two files: MPRG8936.mbn and 8936_msimage.mbn.. If anyone have those files, please, share here.
Thank's for those who can help! ^^
Brow1998 said:
Hello guys!
I'm kinda freakin' out here.
Here's the story:
I bought this amazing Redmi 3 Pro from China, and after waiting for 33 days, it arrived. I knew that it's important change the ROM that came with the device, so... I changed it. I'm from Brazil, so I needed a ROM with Portuguese-BR language and at least, stable. When I was going to change the ROM, my device just turn off and never turned on again.
OBS: The drivers are installed. It recognizes as "Qualcomm HS-USB QDLoader 9008", so I think that it's on EDL Mode.
OBS2: I tested flash on: Win7(x64) and Win10(x64). Neither worked.
OBS3: Every time, I get the error "Reached End of File.(0x80070026: Receiving Hello Packet.)
OBS4: I downloaded several ROMs, several versions of MiFlash (including the Beta version) and nothing passed from the error above.
OBS5: The device doesn't turn on, doesn't light on the LED, doesn't vibrate etc.
I believe that the problem resides on the missing two files: MPRG8936.mbn and 8936_msimage.mbn.. If anyone have those files, please, share here.
Thank's for those who can help! ^^
Click to expand...
Click to collapse
don't panic.. just try this method.. your phone will be back!!
http://en.miui.com/forum.php?mod=viewthread&tid=283484&page=9#pid5645253
Didn't worked
saikatmitra71 said:
don't panic.. just try this method.. your phone will be back!!
Click to expand...
Click to collapse
Heey, didn't worked. .-.
it will be solved with the method which explained on this thread
en.miui.com/thread-283484-5-1.html
Hey @Brow1998
Try this : HERE
Section How to Unbrick the Redmi3
Scenario B (Hardbrick)
adblocker said:
Hey @Brow1998
Try this : forum.xda-developers.com/redmi-3/development/redmi-3-pro-spacex-rom-t3406919
Section How to Unbrick the Redmi3
Scenario B (Hardbrick)
Click to expand...
Click to collapse
Well.. I believe that my phone's battery is dead.. How can I charge it externally? Cuz the charger isn't charging properly. Tried several chargers, but the light of low battery doesn't turn on in a couple days.
Brow1998 said:
Well.. I believe that my phone's battery is dead.. How can I charge it externally? Cuz the charger isn't charging properly. Tried several chargers, but the light of low battery doesn't turn on in a couple days.
Click to expand...
Click to collapse
You need to plug the battery to other redmi 3 and charge it
or charge it directly with 1A 3.9V (risk of damage)
adblocker said:
You need to plug the battery to other redmi 3 and charge it
or charge it directly with 1A 3.9V (risk of damage)
Click to expand...
Click to collapse
Well.. I live in Brazil, and I don't know anyone who have this device, so that's not an option. Any other sugestions to charge it?
Brow1998 said:
Well.. I live in Brazil, and I don't know anyone who have this device, so that's not an option. Any other sugestions to charge it?
Click to expand...
Click to collapse
you do not need to charge the phone before flashing. i had the same problem. connect your phone to computer and after some minutes (may be up to 20 minutes) in device manager you will the phone as..... qdloader.... 9008 and every thing is ready to flash according the instructions.
rekh said:
you do not need to charge the phone before flashing. i had the same problem. connect your phone to computer and after some minutes (may be up to 20 minutes) in device manager you will the phone as..... qdloader.... 9008 and every thing is ready to flash according the instructions.
Click to expand...
Click to collapse
The computer recognizes the device exactly like this "Qualcomm HS-USB QDLoader 9008 (COM20)"
When i'm going to flash, an error appears, "Reached End of File.(0x80070026: Receiving Hello Packet.)".
Using the MiFlash Beta, the error says "Coudn't communicate with port COM20"
I wanna play pokémon go :c
Brow1998 said:
The computer recognizes the device exactly like this "Qualcomm HS-USB QDLoader 9008 (COM20)"
When i'm going to flash, an error appears, "Reached End of File.(0x80070026: Receiving Hello Packet.)".
Using the MiFlash Beta, the error says "Coudn't communicate with port COM20"
I wanna play pokémon go :c
Click to expand...
Click to collapse
why dont you do what I said ! ?
try it
someone like you did it and he saved his phone!
adblocker said:
why dont you do what I said ! ?
try it
someone like you did it and he saved his phone!
Click to expand...
Click to collapse
If you're talking about the solution through the guide for Redmi 3, I just did it and nothing worked. On MiFlash 2015.10.28.0 appeared the error "0x800700aa" Something like "Current Resource current being used" and when I click on refresh and try it again, the same old error appears: "0x80070026: Receiving Hello Packet"
On MiFlash Beta, the error "Can not read from port COM4" still appears.
Just updating.
Using this method, it worked: http://en.miui.com/forum.php?mod=viewthread&tid=283484&page=5#pid5510469
I was making some mistakes, but doing it properly totaly works!
Thank you all!
Brow1998 said:
Heey, didn't worked. .-.
Click to expand...
Click to collapse
same with my problem yesterday , my redmi3 deadbrick, but i can repair it, sorry for my english , follow that tutorial link
Hi guys!
I think I did something stupid while updating my XT1650-03 to Nougat.
What I did was manually flash stock nougat ROM (retbr) through fastboot, following the instructions within flashfile.xml, but, as I've read some bad things about the updated bootloader I stupidly decided not to flash it. The result is that it won't power up, even though I've tried: pressing power+vol. down; power; plugging the charger; fastboot commmands ( I was hoping it was just the screen that was off); to no avail.
I've noticed that when I plug the usb cable to the computer it plays that sound of connected devices.
Any suggestions? I'm probably going to have to take my device to authorised repair (off warranty, I know), but they usually take weeks to fix anything, so you guys are my best bet for now.
Thanks in advance!
martonto said:
Hi guys!
I think I did something stupid while updating my XT1650-03 to Nougat.
What I did was manually flash stock nougat ROM (retbr) through fastboot, following the instructions within flashfile.xml, but, as I've read some bad things about the updated bootloader I stupidly decided not to flash it. The result is that it won't power up, even though I've tried: pressing power+vol. down; power; plugging the charger; fastboot commmands ( I was hoping it was just the screen that was off); to no avail.
I've noticed that when I plug the usb cable to the computer it plays that sound of connected devices.
Any suggestions? I'm probably going to have to take my device to authorised repair (off warranty, I know), but they usually take weeks to fix anything, so you guys are my best bet for now.
Thanks in advance!
Click to expand...
Click to collapse
Don't even bother going to the service center. The same happened with my device and they refused to give me the warranty. Motorola voids it the moment you get the unlock code. So my device was dead for 3 months. And I fixed it few days back. The good news is that your PC is detecting the device.
I will post the solution with a new thread in few minutes.
Manish54 said:
Don't even bother going to the service center. The same happened with my device and they refused to give me the warranty. Motorola voids it the moment you get the unlock code. So my device was dead for 3 months. And I fixed it few days back. The good news is that your PC is detecting the device.
I will post the solution with a new thread in few minutes.
Click to expand...
Click to collapse
Thank you so much for your reply, it's very much appreciated! I didn't think anyone would reply that soon
I'll wait for your thread!
There ya go
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-unbrick-moto-z-hardbricked-t3590133
So, I'm totally lost.
As I posted in the thread above, even though Manish54 has been very kind to help, that solution did not work for me, so I've been trying to find another way. The thing is, this issue is beyond my comprehension. I'm not new to flashing and stuff, but I am new to moto Z. I understand that I should've been more careful and also have read a bit more before starting to mess with a new device, so feel free to judge me .
For instance, I don't know what fsg.mbm, adspso.bin, BTFM.bin and oem.img are for, since my old phone didn't have those (or at least I didn't need to mess with those), and I also don't know it they're relevant to my problem. If anyone could point me to some info on that, it'd be greatly helpfull.
Besides that, I've found mentions to tools like qualcomm's BoardDiag and QPST QFIL, but I'm not really sure if they apply for my situation, or even if I can manage to adapt the guides I've found to work on the Moto Z.
Any help is very much appreciated!
Thank you!
Solved!
I managed to unbrick my phone.
If anyone needs it, the details are in the thread made by Manish54.
https://forum.xda-developers.com/mo...rick-moto-z-hardbricked-t3590133#post71876064
Is there any way to solve it ?
Hillterpty said:
Is there any way to solve it ?
Click to expand...
Click to collapse
Did you even read the posts?
Ajuda
martonto said:
I managed to unbrick my phone.
If anyone needs it, the details are in the thread made by Manish54.
https://forum.xda-developers.com/mo...rick-moto-z-hardbricked-t3590133#post71876064
Click to expand...
Click to collapse
Amigo tb estou com o meu morto, me ajuda, qual o modelo do seu.
https://uploaddeimagens.com.br/imagens/sem_titulo-jpg--9130
hard brick moto z
Manish54 said:
There ya go
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-unbrick-moto-z-hardbricked-t3590133
Click to expand...
Click to collapse
hello friends, I'm with hard brick on the moto z xt1650-3
due to an update via ota, when my bootloader was unlocked I was in the android oreo (8.0), however I went back to 7.0, due to an update via ota, the device did not call anymore, I tried several blankflash and nothing, I am very annoyed at this, thinking of dropping my hand, I took some assists nobody can solve, I hope someone here can help me, at least inform me something that is useful to recover my cell phone.
my cell phone is still recognized as "qualcomm hs-usb qdloader 9008 (com3)
please join the telegram group:
https://t.me/motozz
Hey, my phone was dead two (brazilian xt1650-03), i spent three days struggling until i could bring him back. Thanks to the help in this forum. Your phone probably has the latest update opls27-76-51-7-july, so it must work:
first, you have to bankflash it with blankflash_OPL_27.76-51, its in the 30+ page topic tutorial here in this forum. Very important, must be in windows 7 or 8, with usb2.0
second, use this rom opls27-76-51-7-july-moto-z. it must work because its the last one. Its not brazilian, evething works fine but the netflix app didnt , but hey, at least our phone is alive again.
The secret is in the version of the firmware instaled before the brick, it must be the rom installed or latest to work
I fear I may have bricked my phone while trying to flash a custom rom. I had TWRP installed. I used it to flash LineageOS and everything seemed to be going correctly, but then I rebooted the device and it after showing the initial splash screen it just turned off again. It only shows the splash screen now if I hold down Volume down and the Power button for 20 seconds. It doesn't boot into recovery mode or download mode and I don't understand why. I don't know if there's anything that could be done in a situation like this, but if anyone might be able to help I'd really appreciate it. The device is still in warranty, but when you turn it on it says that it's not running stock software so I don't know good of an idea it would be to try to get a replacement unit. I've done that before, successfully with another samsung phone I had about 7 years ago.
mimshipio said:
I fear I may have bricked my phone while trying to flash a custom rom. I had TWRP installed. I used it to flash LineageOS and everything seemed to be going correctly, but then I rebooted the device and it after showing the initial splash screen it just turned off again. It only shows the splash screen now if I hold down Volume down and the Power button for 20 seconds. It doesn't boot into recovery mode or download mode and I don't understand why. I don't know if there's anything that could be done in a situation like this, but if anyone might be able to help I'd really appreciate it. The device is still in warranty, but when you turn it on it says that it's not running stock software so I don't know good of an idea it would be to try to get a replacement unit. I've done that before, successfully with another samsung phone I had about 7 years ago.
Click to expand...
Click to collapse
Seems it's completely bricked and will need to reflash in EDL mode
TheExploitedOne said:
Seems it's completely bricked and will need to reflash in EDL mode
Click to expand...
Click to collapse
How do I boot into edl mode?
mimshipio said:
How do I boot into edl mode?
Click to expand...
Click to collapse
Usually through test points in the back of your device. If your able to get into recovery/main OS try adb reboot edl. If not you can able make or buy a deep flash cable that sets the device into EDL mode
TheExploitedOne said:
Usually through test points in the back of your device. If your able to get into recovery/main OS try adb reboot edl. If not you can able make or buy a deep flash cable that sets the device into EDL mode
Click to expand...
Click to collapse
I opened the device but there's no documentation on where the test points are. Will any EDL cable work? As I mentioned already, the device does not boot beyond the bootloader, no matter what.
mimshipio said:
I opened the device but there's no documentation on where the test points are. Will any EDL cable work? As I mentioned already, the device does not boot beyond the bootloader, no matter what.
Click to expand...
Click to collapse
Yep it's definitely in EDL. When you plug it in do you see Qcom HS-USB 9008 (or 9006) or just Qcom USB bulk or similar? If so then that's a good sign that you can recover, but you'll need a programmer that works with your device. Yes a deep flash cable should do the trick if not already in edl
TheExploitedOne said:
Yep it's definitely in EDL. When you plug it in do you see Qcom HS-USB 9008 (or 9006) or just Qcom USB bulk or similar? If so then that's a good sign that you can recover, but you'll need a programmer that works with your device. Yes a deep flash cable should do the trick if not already in edl
Click to expand...
Click to collapse
When I plug it in nothing happens at all. Thanks for the help. I think I'll buy a cable on amazon and see if it works :good:
mimshipio said:
When I plug it in nothing happens at all. Thanks for the help. I think I'll buy a cable on amazon and see if it works :good:
Click to expand...
Click to collapse
Do you not see anything in device manager or hear a connection? Unless your on a different chipset because the PBL cannot be corrupt by software. You're welcome! If you need further help please do send me a PM and we can go from there
TheExploitedOne said:
Do you not see anything in device manager or hear a connection? Unless your on a different chipset because the PBL cannot be corrupt by software. You're welcome! If you need further help please do send me a PM and we can go from there
Click to expand...
Click to collapse
When I plug it in nothing happens at all. If I try to turn it on while it's plugged, I get the charging screen but that's it.
mimshipio said:
When I plug it in nothing happens at all. If I try to turn it on while it's plugged, I get the charging screen but that's it.
Click to expand...
Click to collapse
Hmm seems it can boot into the kernel. Do you know the specs of the device? If it's Qualcomm I can go have a look around and see what I can find to point you into the right direction
TheExploitedOne said:
Hmm seems it can boot into the kernel. Do you know the specs of the device? If it's Qualcomm I can go have a look around and see what I can find to point you into the right direction
Click to expand...
Click to collapse
It's SoC is a proprietary Samsung chip. All Samsungs use proprietary chips afaik. The A10 uses the Exynos 7884.
mimshipio said:
It's SoC is a proprietary Samsung chip. All Samsungs use proprietary chips afaik. The A10 uses the Exynos 7884.
Click to expand...
Click to collapse
I thought they would have implemented a special mode of operation if you got into a brick like that. If the device comes on with the charger then it's probably not fully bricked. I've seen other threads that have had the same issue so you may have to check them out
TheExploitedOne said:
I thought they would have implemented a special mode of operation if you got into a brick like that. If the device comes on with the charger then it's probably not fully bricked. I've seen other threads that have had the same issue so you may have to check them out
Click to expand...
Click to collapse
Really? where have you seen other people with this issue? I've looked on the A10's forums but I found nothing. Could you send me some links?
mimshipio said:
Really? where have you seen other people with this issue? I've looked on the A10's forums but I found nothing. Could you send me some links?
Click to expand...
Click to collapse
Try to look for other devices and search deeply good sir you may find what you need. I use Qualcomm devices because we have a special EDL mode and I have a programmer for all my devices to restore in the case of a hard brick like yours. I've been able to use custom tools to create a restore firmware like the Zone 2 (LG) and flash the device far enough to get it into download mode to flash the KDZ
mimshipio said:
Really? where have you seen other people with this issue? I've looked on the A10's forums but I found nothing. Could you send me some links?
Click to expand...
Click to collapse
You'll need to search with other devices or just in general. I seen posts about it being in some USB mode but Samsung probably don't have that implementation
Hello,
I am currently facing the same problem. Were you able to solve the problem?
I was using my phone like normal when it froze on me. I shut down my phone as I usually do when it freezes using the Power off + Vol Down. After turning the phone off, it refused to turn back on again, the light indicator for charging also does not work anymore when plugging in the charger. I did a bit of research and found out that it is possibly bricked. The way they suggested to fix this issue is to flash the phone with the stock rom. So here are the things I've tried:
1. Using SP Flash Tool (not really sure how this one is supposed to work, it is asking me for a "Scatter Loading File" which to my knowledge, isn't part of the ROM file I downloaded from xiaomi.)
2. Booting into EDL mode by shorting the pins and Using the official Mi Flash Tool (This one barely worked for me, it got into the process of flashing but asked me for an authorized Mi Account, after a few hours of research I found out that you can't get one.)
3. Changing the original firehose file with the modified version to bypass the authentication (Still asked me to authenticate)
4. Other Flash Tools (Qualtek, MiracleBox, Qualcomm Flash tool, etc. All failed)
Not really sure what to do at this point, I am unable to launch into fastboot or recovery, phone is completely unresponsive. The only thing that is giving me hope is that the phone is detected in the device manager of my pc as Qualcomm HS-USB QDLoader 9008 (COM3). Is the phone dead or is it just bricked, all answers will be highly appreciated, Thanks in Advance
Take phone to authorized service center and let them try to fix it.
jwoegerbauer said:
Take phone to authorized service center and let them try to fix it.
Click to expand...
Click to collapse
Well it is kind of the only possible way because Xiaomi locked down the EDL mode and render a phone truly as useful as a brick, when bricked, unless you sign in with a authorized mi account. Also 99 percent of time the people online claiming that they can fix the device, it is a scam.
However Xiaomi store will probably not fix the phone (it is 3 years old) for the OP (original poster) and try to convince him to move on to new Xiaomi phones because, Xiaomi will earn more...
LR7875 said:
Well it is kind of the only possible way because Xiaomi locked down the EDL mode and render a phone truly as useful as a brick, when bricked, unless you sign in with a authorized mi account. Also 99 percent of time the people online claiming that they can fix the device, it is a scam.
However Xiaomi store will probably not fix the phone (it is 3 years old) for the OP (original poster) and try to convince him to move on to new Xiaomi phones because, Xiaomi will earn more...
Click to expand...
Click to collapse
would a motherboard replacement work?
vaizardsparagon said:
would a motherboard replacement work?
Click to expand...
Click to collapse
1000000 percent this will work because by replacing the motherboard, your corrupt data and chips (fried EMMC flash storage) (and snapped snapdragon) will be replaced.
Exactly same thing happened with my Poco F1 on 20th Aug. It comes up as Qualcomm HS-USB QDLoader 9008 (COM3) when connecting to my laptop.
What would be the cost for getting motherboard replaced? I want to be able to use my phone with minimal effect to its state before the issue happened. Want to avoid any resets.
chmohit25 said:
Exactly same thing happened with my Poco F1 on 20th Aug. It comes up as Qualcomm HS-USB QDLoader 9008 (COM3) when connecting to my laptop.
What would be the cost for getting motherboard replaced? I want to be able to use my phone with minimal effect to its state before the issue happened. Want to avoid any resets.
Click to expand...
Click to collapse
I'm afraid to say this but i think that your phone was stuck in EDL mode. here in my country the technicians offer remote EDL flash.. no success no payment transaction..
hey as per my username i'm no good at this but i got this far. so I got all the files together did sd _shadow's guide unlocked bootloader etc., RSA method doesn't work for me so i am trying the regular fastboot option but my phone cant do fastbootd also my CPU is QUALCOMM
so can i run the flashfile.bat via regular fastboot or will it brick my phone.
well forget it i hard bricked it living up to my name.hopefully ill get it fixed
purenoob said:
well forget it i hard bricked it living up to my name.hopefully ill get it fixed
Click to expand...
Click to collapse
bricked can mean several different things.
No sign of life?
Window PC?
sd_shadow said:
bricked can mean several different things.
No sign of life?
Window PC?
Click to expand...
Click to collapse
no sign of life, no power no charge, i'm on windows if plugged in its detected in the device manager.
can this be fixed by anyone i feel really bad, i know it's just a phone but ya know.
purenoob said:
if plugged in its detected in the device manager.
Click to expand...
Click to collapse
That is a sign of life
Is my device in EDL Mode?
sd_shadow said:
That is a sign of life
Is my device in EDL Mode?
Click to expand...
Click to collapse
in device manager it says quadcomm hs-usb qdloader 9008. so by the looks of this it's a candidate for EDL mode .
i don't want to mess up anymore i think ill give this to a technician. gonna be a while is it ok to let the battery die.
came across a blank flash my phone is RETLA but the flash is RETBR does it matter ?
purenoob said:
came across a blank flash my phone is RETLA but the flash is RETBR does it matter ?
Click to expand...
Click to collapse
If the bootloader is unlocked it should be fine.
Don’t worry about the battery, edl is very low power, battery can last weeks, and should still support charging
sd_shadow said:
If the bootloader is unlocked it should be fine.
Don’t worry about the battery, edl is very low power, battery can last weeks, and should still support charging
Click to expand...
Click to collapse
bootloader was unlocked before all of this happened, so does this mean i can use a android 10 back flash or use an android 11 one for avoid trouble again.
sd_shadow said:
If the bootloader is unlocked it should be fine.
Don’t worry about the battery, edl is very low power, battery can last weeks, and should still support charging
Click to expand...
Click to collapse
ok so now i'm getting this error.
Opening device: \\.\COM5 [ 0.002] Detecting device [ 34.509] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error [ 34.510] Check qboot_log.txt for more details [ 34.511] Total time: 34.514s FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
YES!! finally i got it into flashboot mode i just had to hold the pwr button 10 sec and tried blackflash again.
now im gonna dl RSA to get the correct stuff for my phone.
Might be to early to say but Thank you so much for the help!. ill post back later to update you.
update: success on flash still on a11 dont care its working again money saved.
i Wanted to downgrade becuase since this update my YouTube at higher resolutions would stutter and some of my main games started to chug in certain places.
phone lil hotter etc you know the woes oh well its working now thanks a million thanks again.
purenoob said:
YES!! finally i got it into flashboot mode i just had to hold the pwr button 10 sec and tried blackflash again.
now im gonna dl RSA to get the correct stuff for my phone.
Might be to early to say but Thank you so much for the help!. ill post back later to update you.
update: success on flash still on a11 dont care its working again money saved.
i Wanted to downgrade becuase since this update my YouTube at higher resolutions would stutter and some of my main games started to chug in certain places.
phone lil hotter etc you know the woes oh well its working now thanks a million thanks again.
Click to expand...
Click to collapse
Hey just reporting back i thought i could bear with android 11 but i just couldn't. Being really really carefull this time i managed to return to android 10.
Using the fastbootd method before i ignored it and flashed in regular fastboot. So this time i followed every step to a tee.
just wanted you too know and as all always thx sd_shadow.