Related
I had rooted my xzu with no prblms....had been using it gor a week had even upgraded to lolipop. Then when i tried to flash my device with a custom rom it did not start again. When i press the power button all it does was vibrate. No led indication light blinking no screen nthng just vibrated. I even tried to recover through s1 tool by following some posts on the forum. For that i had to disassemble my xzu to use the test point. But trying to flash it with xzu ftf it gave error ' resource msm 8274 rom error' i then downloaded s1tool frm a different link then it gave me error hardware not detected. What shud i do to start my phone again, is there any other method to start it
razorine said:
I had rooted my xzu with no prblms....had been using it gor a week had even upgraded to lolipop. Then when i tried to flash my device with a custom rom it did not start again. When i press the power button all it does was vibrate. No led indication light blinking no screen nthng just vibrated. I even tried to recover through s1 tool by following some posts on the forum. For that i had to disassemble my xzu to use the test point. But trying to flash it with xzu ftf it gave error ' resource msm 8274 rom error' i then downloaded s1tool frm a different link then it gave me error hardware not detected. What shud i do to start my phone again, is there any other method to start it
Click to expand...
Click to collapse
Hello, thank you for using XDA Assist!
Please post your question here:
http://forum.xda-developers.com/xperia-z-ultra/help
Your device experts are located there.
Good luck!
Thread closed.
my xperia L c2104 is death , but no for so long i guess , an cyanogenmod 12.1 crash kill him , the phone cant turn on ,cant enter to flashmode and fastmode, when i connect the usb to the computer it appears but like this QHSUSB_DLOAD thats the Boot Repair mode
but i cant find the boot of c2104 on internet to repair the boot, if someone can help me ,really thanks , many people falls in this HardBrick :C
yup this means hardbrick, at this moment no way how to fix this only replacing motherboard
files we need to revice our device have only qualcomm
How the **** did that happen?
same situation, but mine still able to open flashmode, fastboot, and recovery. but after trying to fix things by my self (since no help came, and no luck searching forum), well, finally my xperia l rest in peace 2 days ago. mine have problem with superblock btw.
keep strong my friend, maybe it's time to move up to updated phone.
time_san said:
same situation, but mine still able to open flashmode, fastboot, and recovery. but after trying to fix things by my self (since no help came, and no luck searching forum), well, finally my xperia l rest in peace 2 days ago. mine have problem with superblock btw.
keep strong my friend, maybe it's time to move up to updated phone.
Click to expand...
Click to collapse
you can reach flashmode and recovery?
well then you could boot from external sd
Sent from my Xperia T using XDA Free mobile app
Hello Friends ,
While flashing CM13 and making some changes in sdcard0 to ext4 format , my phone suddenly went to hard brick or as it seems with following condition : No logo, no vibration , No LED except for one blink whenever it is connected to usb wall charge or laptop .
Cant detect via flashtool on system , only part is while connecting with Windows8 , it makes the usual windows ping as if you connect a flashdrive or any other hardrive .
I was using xperia TX CM12.1 unofficial version .
Attached 2 snapshots showing the errors , before it went to sleep .
Once the phone went blank and i connected with my laptop , it pops up with QHSUSB_Dload driver installing message .
Please help , as I couldnt find any proper resolution to this solution .
@Antiga Prime & @Adrian DC any view .
srd34 said:
Hello Friends ,
While flashing CM13 and making some changes in sdcard0 to ext4 format , my phone suddenly went to hard brick or as it seems with following condition : No logo, no vibration , No LED except for one blink whenever it is connected to usb wall charge or laptop .
Cant detect via flashtool on system , only part is while connecting with Windows8 , it makes the usual windows ping as if you connect a flashdrive or any other hardrive .
I was using xperia TX CM12.1 unofficial version .
Attached 2 snapshots showing the errors , before it went to sleep .
Once the phone went blank and i connected with my laptop , it pops up with QHSUSB_Dload driver installing message .
Please help , as I couldnt find any proper resolution to this solution .
@Antiga Prime & @Adrian DC any view .
Click to expand...
Click to collapse
Regardless of what you may or may not have done for that to happen, I would try following this guide.
You need to register an account in order to download the files, btw.
@Antiga Prime
Reached to a level where S1 tool works but shows Unknown SIN version . snapshot attached and again stuck ,
thanks added for your quick response and related link .
what else can be done
Antiga Prime said:
Regardless of what you may or may not have done for that to happen, I would try following this guide.
You need to register an account in order to download the files, btw.
Click to expand...
Click to collapse
srd34 said:
@Antiga Prime
tried using the steps shown except for opening the phone part for test point and got error attached .
Thanks for the link though . any other view ?
Click to expand...
Click to collapse
You're welcome. Any other view? No, but the entire point of that tutorial is that you have to use the testpoint, that's why you're getting that error. If you don't feel confident enough to do it yourself, I guess you'll have to take it to a repair shop.
@Antiga Prime There is an update now . need correct SIN file for xperia TX refer snapshot ..
Antiga Prime said:
You're welcome. Any other view? No, but the entire point of that tutorial is that you have to use the testpoint, that's why you're getting that error. If you don't feel confident enough to do it yourself, I guess you'll have to take it to a repair shop.
Click to expand...
Click to collapse
srd34 said:
@Antiga Prime There is an update now . need correct SIN file for xperia TX refer snapshot ..
Click to expand...
Click to collapse
I have never done this procedure, by the way, but what I can gather from your screenshot is that either the person who wrote the tutorial I linked to originally made a mistake and uploaded the wrong file, or you're using the wrong file. It seems that at some point you might have also downloaded the file found here, which is a forum post for Xperia SP. I do not know which one is the correct file, but just make sure you're using the correct one. If the one posted in the tutorial I linked to doesn't work, I guess you'd have to find one that does.
Thanks , but it seems this SIN file is also not compatible .
Seems the last resort is to reach service center .
Antiga Prime said:
I have never done this procedure, by the way, but what I can gather from your screenshot is that either the person who wrote the tutorial I linked to originally made a mistake and uploaded the wrong file, or you're using the wrong file. It seems that at some point you might have also downloaded the file found here, which is a forum post for Xperia SP. I do not know which one is the correct file, but just make sure you're using the correct one. If the one posted in the tutorial I linked to doesn't work, I guess you'd have to find one that does.
Click to expand...
Click to collapse
srd34 said:
Hello Friends ,
While flashing CM13 and making some changes in sdcard0 to ext4 format , my phone suddenly went to hard brick or as it seems with following condition : No logo, no vibration , No LED except for one blink whenever it is connected to usb wall charge or laptop .
Cant detect via flashtool on system , only part is while connecting with Windows8 , it makes the usual windows ping as if you connect a flashdrive or any other hardrive .
I was using xperia TX CM12.1 unofficial version .
Attached 2 snapshots showing the errors , before it went to sleep .
Once the phone went blank and i connected with my laptop , it pops up with QHSUSB_Dload driver installing message .
Please help , as I couldnt find any proper resolution to this solution .
@Antiga Prime & @Adrian DC any view .
Click to expand...
Click to collapse
Hello. Have you find the decision about QH SUSB on TX?
No solution yet . The device still with me and gets blinked when connected with charger , however . No solution to recover from hard brick I believe . Service centre also of no help since this model was a limited edition one and they dont have in their SKU list to do anything . keeping as fancy paper weight
Hi guys its the 3rd time that i post here in the forum hopping to restore my "dead" Moto G3 XT1543 1GB RAM Snapdragon 410 (MSM8916).
Some days ago I've unlock my phone bootloader in order to install CM14.1 and i did it with success! but my sim card wasn't working, so, I tried to look for a solution. And I found a video on youtube that showed the supost fix for this issue, but i was wrong. I've flashed the file which broke my phone immediately and now my phone doesn't do ANYTHING!! Well, at least it shows on my computer as QDLoader 9008 but for now on I dont know what I have to do! I know that the easiest way to fix it is buying another motherboard, but I think that still hope for someone to find the way to fix it! Well, if the pc recognizes the processor so there's something to be done right?
I had searched all over the internet during this week, and I found some interesting possible ways to fix it, but im not a developer so I need help and opinions from other people.
1)The first way was to change the mode to 9006 aka diag mode though some files wich in theory allows you to acces eMMC partition and restore all the 29 inside partition and recover your phone. The problem is: I don't know how to change it to diag mode, but yea i have the needed files, and i don't have the tool to acces the eMMC of the phone and i dont have a backup of the partitions to write over the corrupted ones.
2)The second way was to use this tutorial *http://www.droidsavvy.com/unbrick-qualcomm-mobiles/* that i still havent tried since my phone isn't with me right now. So, in this supose way we can contact the phone through a tool called QFIL and try to "Inject" the bootloader or whatever, in the phone to foce him into a bootloop and so enabling the fastboot mode which allows you to install a rom later on. well the problem for this one is, i dont know if it works on your moto g3 but i gonna try. (if you try this option tell me and i gonna upload the needed files because the folder avaliable in the link contais files for the processor Snapdragon 610 and Moto G3 processor is a 410)
3) The third way is a Jtag repair in a authorized store, but i dont think Moto G3 have a jtag fix (im posting this possibility because i could be wrong)
4) In this way could be a updated Blank Flash actually used to hard unbrick the Moto G1 and I Guess the G2? But im not a developer and I dont know too much about programing, but i'm sure someone out there is a pro
5) Use the QPST which is kinda the same thing as use a eMMC tool? ( again im not a dev ) and from what i got, is used to config all your phone from scratch. would be good if there's a tuto out there
6) Sit and wait till Motorola release the MBM-CI 5.0 which from what i got is used like the Blank Flash or used to make a Blank Flash idk
AGAIN!!! IM NOT A DEV, THIS IS JUST SOME WAYS THAT I FOUND OUT THERE ON THE INTERNET WHICH COULD BE USED TO FIX YOUR BELOVED MOTO G3!! SO, I'M SHARING ALL MY RESEACH WITH YOU GUYS BECAUSE IS A SHAME HAVE TO DUMP MY DEVICE LIKE THAT OR HAVE TO EXPEND LIKE R$ 500 IN A NEW MOTHER BOARD WHICH IN DOLLAR ITS LIKE 1600 U$D (this is Brazil guys yea it's a horrible country T_T ) SO I HOPE THAT THIS POST HELPS SOMEBODY AND IF YOU GOT SOME INFO SHARE TO HELP US TRY TO FIX THE PHONE!
hey you got successful??? in unbricking your phone?
[email protected] said:
hey you got successful??? in unbricking your phone?
Click to expand...
Click to collapse
not yet, i send my phone to an authorized i hope they can fix it via programming box
IkkyShad said:
not yet, i send my phone to an authorized i hope they can fix it via programming box
Click to expand...
Click to collapse
Ohhkay
You'll need blankflash for this device, that's the only thing which will take it back to bootloader mode so you can flash a firmware. Blankflash is usually found in stock firmwares, however the chances are kinda low
siredux said:
You'll need blankflash for this device, that's the only thing which will take it back to bootloader mode so you can flash a firmware. Blankflash is usually found in stock firmwares, however the chances are kinda low
Click to expand...
Click to collapse
yeah i know, i tried everything in 3 weeks but with no success, unfortunately the moto g3 firmwares are kinda different from other firmwares
IkkyShad said:
yeah i know, i tried everything in 3 weeks but with no success, unfortunately the moto g3 firmwares are kinda different from other firmwares
Click to expand...
Click to collapse
Can we even try a firmware of Moto g 2 Nd gen ,to get into fastboot anyhow ? Bcoz Moto g 2nd gen is hardbirck recoverable
[email protected] said:
Can we even try a firmware of Moto g 2 Nd gen ,to get into fastboot anyhow ? Bcoz Moto g 2nd gen is hardbirck recoverable
Click to expand...
Click to collapse
yeah, you can try but the models are different and also the partitions inside the phone... try it out and if it works you can post here
No u can't try the Moto g2 firmware..... As Moto g2 is also waiting for MBM CI 5 file for lollipop and Motorola is not releasing those file needed for blankflash
Sorry to bump needlessly but has there been any progress in this regard?
Has anyone found a solution or blankflash files?
I managed to hardbrick my device while trying to resize the system and userdata partitions (stupid, I know)
Jaysin365 said:
Sorry to bump needlessly but has there been any progress in this regard?
Has anyone found a solution or blankflash files?
I managed to hardbrick my device while trying to resize the system and userdata partitions (stupid, I know)
Click to expand...
Click to collapse
No... And just like previous Moto devices, it is unlikely we will ever get the necessary files.
Same situation, any updates?
I'm currently facing the same situation with XT1543, it ran Marshmallow 6.0 stock (came with Lollipop) and suddenly it hard bricked (last time i checked there were no software updates and even if there were, the phone would not restart itself to update). I ran blankflash but the results were these:
greeting device for command mode
opening device: \\.\COM3
OKAY [ 0.001s]
greeting device for command mode
FAILED (blank-flash:greet-device:error reading packet)
Click to expand...
Click to collapse
I appreciate any help!
gibarsin said:
I'm currently facing the same situation with XT1543, it ran Marshmallow 6.0 stock (came with Lollipop) and suddenly it hard bricked (last time i checked there were no software updates and even if there were, the phone would not restart itself to update). I ran blankflash but the results were these:
I appreciate any help!
Click to expand...
Click to collapse
If you can't get to the bootloader, it's toast... we do not have the proper files to do a Qload reflash, and the chances of getting them are near zero.
Try the usual... drain the battery and hold Power+Vol Dn (normal method to access bootloader) or press and hold Power+Vol Dn for 15-30 seconds, if you can't get to the bootloader there is NO recovery method available. Sorry.
acejavelin said:
If you can't get to the bootloader, it's toast... we do not have the proper files to do a Qload reflash, and the chances of getting them are near zero.
Try the usual... drain the battery and hold Power+Vol Dn (normal method to access bootloader) or press and hold Power+Vol Dn for 15-30 seconds, if you can't get to the bootloader there is NO recovery method available. Sorry.
Click to expand...
Click to collapse
Thanks for the quick reply, I will post my results here whether it's successful or not.
acejavelin said:
If you can't get to the bootloader, it's toast... we do not have the proper files to do a Qload reflash, and the chances of getting them are near zero.
Try the usual... drain the battery and hold Power+Vol Dn (normal method to access bootloader) or press and hold Power+Vol Dn for 15-30 seconds, if you can't get to the bootloader there is NO recovery method available. Sorry.
Click to expand...
Click to collapse
+1 on this.
The only other thing I would do is take it apart and detach one wire from battery and short that lose wire to the other wire (short the phone, NOT the battery!) for 15 sec or so and reconnect wire to battery and put phone back together and try boot to bootloader (power plus vol-dn). If no go, at that point if it were worth it I would give it to ATT to fix, or toss it in the drawer for parts.
I too hard bricked my g3.
My PC detected it as Qualcomm 9008 mode
Plz help how to solve this
Durga teja said:
I too hard bricked my g3.
My PC detected it as Qualcomm 9008 mode
Plz help how to solve this
Click to expand...
Click to collapse
Tell us how you bricked it?
KrisM22 said:
Tell us how you bricked it?
Click to expand...
Click to collapse
Rooted and installed twrp nd framework on 5.0
Bro accidentally updated to 6.0 on WiFi
Blank screen. No bootloader.
LED blinkinh
Durga teja said:
Rooted and installed twrp nd framework on 5.0
Bro accidentally updated to 6.0 on WiFi
Blank screen. No bootloader.
LED blinkinh
Click to expand...
Click to collapse
beyond my knowledge. Hopefully someone will jump in.
Durga teja said:
Rooted and installed twrp nd framework on 5.0
Bro accidentally updated to 6.0 on WiFi
Blank screen. No bootloader.
LED blinkinh
Click to expand...
Click to collapse
If there is no bootloader and the only thing that can be seen on the computer is QdLoader mode, it's done... Send it to Moto for repair or send it to the recycler, there is no fix we can do.
Ok, i have a doogee x5 pro phone and i tried to root it by flashing twrp recovery using sp flash tools. While flashing i got the error "PMT Changed for the rom it must be download". So i did a small research on internet and i found out that i needed to format everything except bootloader. This succeded. So after that i tried to install the firmware with this succeding to. Unfortunately the time i tried to turn phone on it was dead. SP Flash Tools wont detect it anymore. Please help me cause the phone is not mine and its brand new! I can rate my self as moderate android user. :crying:
i think i have a bigger problem... I downloaded a stock rom for doogee max pro(cause i just realised it wasnt just pro it was max pro) and it didnt seem to be recognised again. Any help would be appreciated. I constantly keep trying to raise it from the deads. Thanks!
Ap0s said:
i think i have a bigger problem... I downloaded a stock rom for doogee max pro(cause i just realised it wasnt just pro it was max pro) and it didnt seem to be recognised again. Any help would be appreciated. I constantly keep trying to raise it from the deads. Thanks!
Click to expand...
Click to collapse
On mtk devices a preloader is independently installed, it should be almost impossible to destroy, I owned a x5 pro and had best success to flash it with sp flash by taking out the battery, press flash button and plug it in...
The second huge issue I see is when you used the specific flash tool format option you very, very likely killed the nvram partition which contained the imei, so you'll have to fix this too by generating a new one and using mtk engineer mode which is well described and to find on Google..
But let's go step by step. Check without battery, or if it's a non replaceable you'll need find the reset button..
i have tried before without battery and i tried just now but nothing. Its very weird it was detected before and now no in same and another machine. I am pretty confused and stressed. Hope i didnt do any physical damage.. :crying:. THANKS!
starting to get pretty stressed omg! and is there a difference between MT6737M and MT6737?
i came to the point im starting to lose my mind... tried everything i could, i have 5 days left to repair this phone and i dont wanna pay 85 euros for this. SP Flash Tools wont detect the phone. Tried almost 5 different scatter files,2 different PCs and different mtk drivers. Im losing my mind already
UPDATE: I almost fixed it! I had flashed wrong preloader so phone wasn't recognized by SP Flash Tool. I fixed preloaded with a little trick from here: link. After that i flashed stock rom downloaded from doogee.cc but phone will not boot resulting in a total black screen. When i hot Power + Vol Up it takes me to another screen:
Select Boot Mode:
Recovery
Bootloader
Normal
Doesn't matter which boot mode i choose i just get a total black screen which means i get nothing. Idk what is happening! Any further help would be appreciated! I constantly try to bring it back working with little success and small improvements.
Last UPDATE: FIXED my phone had no juice left inside so couldnt complete boot proccess. Now its all good running Btw someone must pin this META trick link i send on my previous post cause im sure more people out there have preloader issues!!! Thank you everyone!!
Sam Nakamura said:
On mtk devices a preloader is independently installed, it should be almost impossible to destroy, I owned a x5 pro and had best success to flash it with sp flash by taking out the battery, press flash button and plug it in...
The second huge issue I see is when you used the specific flash tool format option you very, very likely killed the nvram partition which contained the imei, so you'll have to fix this too by generating a new one and using mtk engineer mode which is well described and to find on Google..
But let's go step by step. Check without battery, or if it's a non replaceable you'll need find the reset button..
Click to expand...
Click to collapse
And yes i couldnt flash it with battery only with!