Hi guys,
I read a lot of your wise threads while trying to save my phone but unfortunately I didn't find an answer.
I tried to upgrade my LG G2 mini (D620R) from official stock ROM 4.4.2 to official stock ROM 5.0.2 using the LG flash tool (phone is unrooted).
At the end of the upgrade I got stuck in bootloop. Maybe b/c I chose "normal flash".
1) The stock recovery mode only offers me a factory reset - It didn't help.
2) I'm not able to go into download mode.
3) The computer doesn't recognize the phone. It recognizes it as a USB power device.
4) Even tried ADB, but it doesn't see the phone.
Do you have any suggestions?
Maybe the bad flash damaged the memory hardware?
Thank you very much for all of your help.
Bro, plz ask for ur problem in this forum :-
forum.xda-developers.com/g2-mini
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.
How can i fix this? Need help
Flash again using LG Flash Tool, use D838 international version of Lollipop stock rom
Go to 'Download Mode'
Set the flash tool to CDMA+Emergency
Make sure you do everything OFFLINE
My phone got stuck at 90% while flashing D838 ROM. Now it does not open anymore - only the LG logo shows off and on and can no longer be detected by my PC. My phone now is on a 'bootloop" mode. And I can no longer go to Download mode so I can flash anew.
Any help from our Masters out there?
TIA.
profeduards said:
My phone got stuck at 90% while flashing D838 ROM. Now it does not open anymore - only the LG logo shows off and on and can no longer be detected by my PC. My phone now is on a 'bootloop" mode. And I can no longer go to Download mode so I can flash anew.
Any help from our Masters out there?
TIA.
Click to expand...
Click to collapse
Take a look at my thread for LG V20, read fastboot tutorial in particular. Most knowledge on my thread applies to LG-D838 which I own too. Just change things accordingly. For instance, instead of LG UP tool use LG Flash tool.
Once you read the articles, you would be your own master. Good Luck.
Hello everybody,
I have a bootloop issue with a Lenovo P11 Pro. It is stuck in a bootloop and keeps restarting 1 min after Lenovo logo.
I have tried anything from Hard Reset to Rescue Smart Assistant Flashing and Qfil Flashing. It flashes successful but Tablet still doesn't want to boot up.
Have any ideas? I bought it like that so don't know what the person before me did to it.
Tablet seems to charge.
Thanks in advance for all the ideas!
emybuse said:
Hello everybody,
I have a bootloop issue with a Lenovo P11 Pro. It is stuck in a bootloop and keeps restarting 1 min after Lenovo logo.
I have tried anything from Hard Reset to Rescue Smart Assistant Flashing and Qfil Flashing. It flashes successful but Tablet still doesn't want to boot up.
Have any ideas? I bought it like that so don't know what the person before me did to it.
Tablet seems to charge.
Thanks in advance for all the ideas!
Click to expand...
Click to collapse
I haven't had this situation, but what firmware have you tried flashing? Have you read the threads about the region codes, and how the firmware has to match them (in the latest firmwares) or the region code has to be changed. I would try flashing an international firmware, and if that doesn't work try a china firmware. There are only two regions I think, so one of those should work.
I could have got the wrong end of the stick with this as I've not been in this situation, so not very carefully read those threads yet, so just a suggestion!
mdurkin said:
I haven't had this situation, but what firmware have you tried flashing? Have you read the threads about the region codes, and how the firmware has to match them (in the latest firmwares) or the region code has to be changed. I would try flashing an international firmware, and if that doesn't work try a china firmware. There are only two regions I think, so one of those should work.
I could have got the wrong end of the stick with this as I've not been in this situation, so not very carefully read those threads yet, so just a suggestion!
Click to expand...
Click to collapse
Rescue and Smart Asistant does the job automaticaly and it flashed TB-J706L_S620103_211124_ROW. And with Qfil I tried the TB-J706L_S243005_210601_ROW.
emybuse said:
Rescue and Smart Asistant does the job automaticaly and it flashed TB-J706L_S620103_211124_ROW. And with Qfil I tried the TB-J706L_S243005_210601_ROW.
Click to expand...
Click to collapse
RSA did not succeed in my case.
$ fastboot set_active a did the trick for me!
Amatöhr said:
RSA did not succeed in my case.
$ fastboot set_active a did the trick for me!
Click to expand...
Click to collapse
Fail : not unlock, help me
I didn't think I had to, when I plug in the tablet it pops up with the name and everything.
Hi, I have the same issue with a Tab 11 pro gen 2. Could you let me know how to solve it? I can't even find the recovery, and tried all button combinations. I can only go to fastboot or meta modes.
im literally stuck on this ( fastboot ) screen... it boots straight to this screen. If i plug the device into my pc it says device not recognised and none of the drivers seem to work. I have tried everything to shut it down so i can try flash via EDL, but the power button just takes me back to fastboot again...
I'm having the same reboot issue 1 minute or less after fully booting. I have no idea how to fix it
Hello, my Motorola e Android phone got hard bricked and it began suddenly with the first error message being constant boot looping and eventually going to an error message with an adroid on its back where it said partition was corrupt or damaged and the only choices were try again or factory reset. I kept trying again.
I tried to fix it and eventually ended up stuck on ap fastboot flash mode(secure) and it says oem locked.
I gave up trying to do it myself and want to factory reset but recovery mode won't work even if I press it, says that start up failed and goes back to fastboot mode. It's stuck.
Serial number is ZY22DLT4R and last letter is a V or W, can't tell.
I dont know to flash or custom rom. Tried a few but I only have windows 10 on my PC and it didn't install drivers properly and I need this phone fixed ASAP . I think I'm considered a newbie.
I also need to know if it's too far gone so I'm prepared to buy another crappy phone and lose all my data. I don't have days/weeks to learn tutorials about how to mod, etc.
Please help.
edit: I don't know if my bootloader is locked or unlocked.
Re-flash phone's Stock ROM by means of this tool
Download Moto Auto Flash Tool v8.2 by Jamesjerss (2022)
Download Moto Auto Flash Tool v8.2 by Jamesjerss to flash Firmware on Motorola Phones. Follow this guide to Root, Unlock Bootloader, etc.
www.ytechb.com