Related
Q&A for Unbrick Hard Bricked Moto G (2nd.Gen) [5.0/4.4.4]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Unbrick Hard Bricked Moto G (2nd.Gen) [5.0/4.4.4]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
A little different brick of my Moto G 2nd gen(XT-1068).plz help
Hi ,
Please dont ignore my mail just bcoz its too long. I have been following this thread from four to five days. Will you please help me ? Just have a look at my problem. I have been rooting my android phones and have good experience of testing , rooting the handsets. Recently I flashed my Moto G ( xt-1068 ) with lolipop because i was not able to wait till motorolla release it.
I tested it for few days , and successfully downgraded back to 4.4.4 kitkat. It was all fine. I love MIUI so I started my work to port MIUI over our favourite Moto G . I even ported it and was not booting. So I edited updter-script and was trying to flash it back on my xt-1068.
Now the mistake that happened was , due to some error in the script , It aborted the installation. When i checked the log from CWM , It has crossed partitioning and it aborted while extracting the directorties. By mistake I restarted the phone and since the partitions were flashed and there was nothing to execute , my phone is stuck. Its not even starting . Its getting recognised as "qhsusb_bulk". Thts why i came over this thread and tried to follow the procedure you have mensioned.
I am also getting the same error like while flaashing with blank-flash : FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame) and FAILED (blank-flash:sdl-transfer-image:sdl-hello:error sending packet) .
So do i have the same problem that happened with theses guys who tried to downgrade their handsets from Lolipop to kitkat ? If its so , should I also wait for Lolipop release by moto ? or will i have some other problem ? Do you have any solution ? I was really wanted to make MIUI available for our Moto G . I don't feel sad for bricking of m phone but what ifeel sad is I want it back. I can't pass my day without it. i am missing it. Please can you suggest me wht should I do ?
Thanks in advance.
DONT WORK FOR ME :s
I have a moto g 2014 XT1063 and after unlocking the bootloader the phone work well for a minutes. Then i power off the phone and when i try to turn on again the phone is die :S no custom no bootloader dont charge dont vibrate not nothing uu. i try this tutorial but when i run the blankflash he trhrow me a error :/ please help me
Moto G hard brick
Someone please help all of us who have wrongly hard bricked our lovely Moto G 2014 . The blankflash is giving "Error sending packet" error. We all will be really thankful of you. Please help. Although some Devs say that we will have to wait for lolipop, but Moto G 2014 has already 5.0 available. Someone please check this thread and solve the problem.....plz..
link : http://forum.xda-developers.com/moto-g-2014/development/unbrick-hard-bricked-moto-g-2nd-gen-5-0-t2966010
same problem
Hi, i have an moto g xt1068 too and din't power on since yesterday hope to find a solution is hard bricked too.
i bricked mine.problem is the code 43 wich it won t recognize at all the device whatever driver i use.
altho it wont boot black screen i dont know if it charge or not, PC will recognize as device once i press volumedown+power button.
wich on my opinion he works somehow but it isn t recognized bt the windows 7.
i will install a fresh copy of win7 and check again maybe is just a failure from windows.
any other advices feel free to share.
firmwares
do someone has the moto g 2gen firmwares on extention .tar.gz i need them to fix my phone
Help!!
Hi people.
Well, only 2 weeks ago I got my Moto G XT1063 and I unlocked bootloader to install Soak Test of Android 5.0.2 with RetailUSA firmware. (My device's original firmware, was for Claro Colombia).
It worked well, I got it running perfect. Yesterday I saw that official/final version of 5.0.2 was available for my device with RetailUSA firmware, but I needed to do a downgrade to KitKat first, because it wouldn't work if I was in Soak Test yet.
So I made the downgrade, and it was running well, I checked for updates, and there was no updates availables, so I decided to reboot, to see if it may make the update appear. But after turning off my device, and trying to turn it on again, just nothing happened.
Now, my device doesn't want to turn on, neither in fastboot mode. And now, I don't know what to do here. So I would be really thankful for any help provided.
Thanks in advance. Have a nice day.
So here is what happened,
My phone was maybe 14% plugged it in left it charging and went to sleep.
Woke up with the phone alarm and started reading whatsapp messages, at this point the phone was already at 100%.
Maybe 30-40 seconds later, with the cable still plugged in the phone turned off, with no message, it just "died".
Now it wont boot, fastboot, nothing.
Tried some solutions i found on the internet like holding vol down + power button for more than 2 minutes, and nothing.
I really need some help here guys, PLEASE.
The phone was running latest TITAN PRIME ROM 1.1 dev3
Everything will be appreciated, thanks in advance.
partitions whacked out?
It seems I am unable to flash anything probably due to partitions broken. When I try to do a fastboot flash, It results in OKAY, but it has no effect on the device. I tried to flash the gpt.bin to partition, but the problem remains. Is there any way to repair the partitions? I tried to format in fastboot, I get the error "formatting is not supported for filesystem with type 'raw'". I am also unable to change format from recovery. All ideas welcome!
This issue came up after my phone went battery empty.
arvinoids said:
It seems I am unable to flash anything probably due to partitions broken. When I try to do a fastboot flash, It results in OKAY, but it has no effect on the device. I tried to flash the gpt.bin to partition, but the problem remains. Is there any way to repair the partitions? I tried to format in fastboot, I get the error "formatting is not supported for filesystem with type 'raw'". I am also unable to change format from recovery. All ideas welcome!
This issue came up after my phone went battery empty.
Click to expand...
Click to collapse
Same here, also due to 0% battery.
Seems these phones do not shutdown early enough before the battery voltage drops below spec. ****ty engineering.
Please, someone help us for the sake of god.
There are several people with this problem and we don't know how to fix it.
Is there any possibility, any help, anything we could test would be welcome.
Phone Moto G 2014 not turning on after flashing BlissPOP ROM
i flashed "BlissPop-v3.6-titan-OFFICIAL-20150629-1948" ROM to my Moto G 2014 Model and Rebooted after.Unfortunately phone doesnt turn on.Even unable to open Recovery Mode also. Can some one tell me a solution. My phone was unlocked,rooted and TWRP flashed too...
Im too facing the same issue.. the device is not turning on.... i jus unplugged from the charger but before putting the device for charging it was 67% battery... after unplugged the device screen jus turned into black i tot,the screen went to sleep but later the device dint turn on..... plzzzzzz guys any1 has any solutions??????????
I followed according to this thread http://forum.xda-developers.com/moto-g-2014/general/unbrick-hard-bricked-moto-g-2nd-gen-5-0-t2966010 but nothing worked....
Gave my Bricked Moto G 2nd Gen to Moto Service Center
Hey folks... I tried giving my Bricked phone to nearby local mobile repair shop and even they were of no help.They were of assumption that its a motherboard issue. Seriously i still cant digest that . How come flashing a ROM in your mobile screw up the Motherboard. I appreciate if someone can throw some light on this.
Anyways i gave my bricked phone to Motorolla Service Center yesterday as Warranty is still there.I acted dump infront of them and told Godamm it!!My phone doesnt turn on all of a sudden. They took my phone and asked me to wait for 3 days till they can figure out What in the name of God has happend to my Phone. I will let you folks know if i get a replacement ....
lijuram said:
Hey folks... I tried giving my Bricked phone to nearby local mobile repair shop and even they were of no help.They were of assumption that its a motherboard issue. Seriously i still cant digest that . How come flashing a ROM in your mobile screw up the Motherboard. I appreciate if someone can throw some light on this.
Anyways i gave my bricked phone to Motorolla Service Center yesterday as Warranty is still there.I acted dump infront of them and told Godamm it!!My phone doesnt turn on all of a sudden. They took my phone and asked me to wait for 3 days till they can figure out What in the name of God has happend to my Phone. I will let you folks know if i get a replacement ....
Click to expand...
Click to collapse
Please let me know because also I've bricked my device & want to send it to nearest authorized service center.
lijuram said:
Hey folks... I tried giving my Bricked phone to nearby local mobile repair shop and even they were of no help.They were of assumption that its a motherboard issue. Seriously i still cant digest that . How come flashing a ROM in your mobile screw up the Motherboard. I appreciate if someone can throw some light on this.
Anyways i gave my bricked phone to Motorolla Service Center yesterday as Warranty is still there.I acted dump infront of them and told Godamm it!!My phone doesnt turn on all of a sudden. They took my phone and asked me to wait for 3 days till they can figure out What in the name of God has happend to my Phone. I will let you folks know if i get a replacement ....
Click to expand...
Click to collapse
I got my device from service centre n got motherboard replaced with warranty... But got updated to new firmware ss below....
Sent from my XT1068 using XDA Free mobile app
moto g2 shows qhsusb bulk plz somebody help
hello friends.. i don't have Rif JTAG box....to unbrick my moto g2
If anybody have box plz help me...& repaire my mobile bootloader
I will pay for this....plz help help help.......call me on this no.
9465351811
state punjab distt patiala teh nabha
vpo :CHHINTANWALA
exactly same problem.
lijuram said:
i flashed "BlissPop-v3.6-titan-OFFICIAL-20150629-1948" ROM to my Moto G 2014 Model and Rebooted after.Unfortunately phone doesnt turn on.Even unable to open Recovery Mode also. Can some one tell me a solution. My phone was unlocked,rooted and TWRP flashed too...
Click to expand...
Click to collapse
i have through exactly same thing. my phone was working exellently on blisspop rom and got bricked once i installed an addon.
now i want to know what u did after tht.
not to mention i dnt have warranty now.
wanna listern to a person going through same ****.
Hello frnds ....my bro have moto g 2nd gen running on lollipop with unlock bootloader rooted and twrp recovery. yesterday i flashed resurrection rom. every thing ok today i reflashed stock lollipop rom by restoring nandroid backup... Today my bro in my absence trying to flash again resurrection rom. my bro is totally noob ...he flash kernel instand of rom which is not compatible with this rom and phone get hard brick .....i has been tried this method but nothing heppened ....plzzz give me solution plzzzzzzzzz
Actually my friend bricked his phone, he flashed the 5.1 bootloader and radio.then somehow he flasheed back to 5.0.1 stock. then he flashed Euphoria again. The phone rebooted fine and he went to sleep. Then woke up and found out his phone was dead. And all buttons combo didn't work at all. It's just a piece of dead body.When plugging into the PC, it shows qhsusb_bulk. There were devices that had same problems but they managed to unbrick it, But those methods don't apply to Shamu. Odd thing is I did the same thing so far my Nexus 6 is fine .I've started worrying, tho. We bought it from amazon.fr and I'm sure i dont want to send it back all the way from China to France.
Also , i read some dudes encountered the same problem after flashing Cm12 with 5.1 BL. I really need your help.
I tried Nexus Root Toolkit to flash the factory image, it didnt work. It's still using the fastboot, and ofc i don't get to go there.
I've installed the Qualcomm_QHSUSB_driver, but it doesn't seem to fix anything.
no one?
Mine has done the same thing. Went to flash 5.1 nexus image from the google dev site. The flash did boot and radio and failed size on system ( even re-downloaded). I plug my N6 into my linux machine and this what I get on lsusb "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)". I am also in need of help.
This updates been a nightmare
synapses said:
Mine has done the same thing. Went to flash 5.1 nexus image from the google dev site. The flash did boot and radio and failed size on system ( even re-downloaded). I plug my N6 into my linux machine and this what I get on lsusb "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)". I am also in need of help.
Click to expand...
Click to collapse
So you're like me, no way to enter bootloader right? I've seen some other phones with the same problems but they figured a way out to solve it. I don't know we'll get that
beachbum40 said:
This updates been a nightmare
Click to expand...
Click to collapse
I'm not sure it has anything to do with the update. My friend didn't flash the 5.1 google factory image . He flashed the 5.1 BL on a 5.0.2 aosp based rom then went back to stock 5.0.1 then flashed the same 5.0.2 aosp rom. Now it ends up dead.
This happened on Samsung devices too and it was a emmc issue, so the internal drive among others was no longer readable and writable and hardware like buttons was not working either. Unless someone comes with the golden tip you`ll have to turn it in for repair. Good luck guys
randy6644 said:
So you're like me, no way to enter bootloader right? I've seen some other phones with the same problems but they figured a way out to solve it. I don't know we'll get that
Click to expand...
Click to collapse
doing some reading and it seams to be a broken bootloader.
synapses said:
doing some reading and it seams to be a broken bootloader.
Click to expand...
Click to collapse
I'm also a g2 owner, some just broke their devices and ended up sth similar. But they managed to unbrick it. I don't know if we stand a chance to bring it back to life.
I'm still stuck. Any progress ?
synapses said:
doing some reading and it seams to be a broken bootloader.
Click to expand...
Click to collapse
Any progress? I tried several ways and none of them worked
I had to RMA
randy6644 said:
Actually my friend bricked his phone, he flashed the 5.1 bootloader and radio.then somehow he flasheed back to 5.0.1 stock. then he flashed Euphoria again. The phone rebooted fine and he went to sleep. Then woke up and found out his phone was dead. And all buttons combo didn't work at all. It's just a piece of dead body.When plugging into the PC, it shows qhsusb_bulk. There were devices that had same problems but they managed to unbrick it, But those methods don't apply to Shamu. Odd thing is I did the same thing so far my Nexus 6 is fine .I've started worrying, tho. We bought it from amazon.fr and I'm sure i dont want to send it back all the way from China to France.
Also , i read some dudes encountered the same problem after flashing Cm12 with 5.1 BL. I really need your help.
I tried Nexus Root Toolkit to flash the factory image, it didnt work. It's still using the fastboot, and ofc i don't get to go there.
I've installed the Qualcomm_QHSUSB_driver, but it doesn't seem to fix anything.
Click to expand...
Click to collapse
Something should be able to be done using QPST (i.e., to force flash the bootloader), but that is above my level of knowledge.
efrant said:
Something should be able to be done using QPST (i.e., to force flash the bootloader), but that is above my level of knowledge.
Click to expand...
Click to collapse
I'm going through similar with a dead Nexus 7. I think the eMMC died in it though, as it just went out without any tinkering. No sign of life on the device, but is picked up as a Qualcomm modem port and detected by QPST in download mode. I don't have/can't find the hex files required by QPST to flash it though.
I theorize that if a working device can be put in QPST "diag" mode, then QPST will allow exporting the storage contents in a flashable hex file, and that file could be used to restore the boot partitions on the dead device. I haven't been able to find information about this "diag"nostic mode, however.
Same issue guys, Upgraded to 5.1 OTA rooted and flashed cm12 tried to reboot. Nothing. Stuck in "Qualcomm HS-USB QDLoader 9008" QPST will recognize it in Download mode. If we can get these Hex files I will give it a shot. Thanks!
http://bbs.gfan.com/forum.php?mod=viewthread&tid=7863761
found sth here dont know if its useful, all written in Chine
randy6644 said:
http://bbs.gfan.com/forum.php?mod=viewthread&tid=7863761
found sth here dont know if its useful, all written in Chine
Click to expand...
Click to collapse
Cant find much relating to our issue but there may be relevant info there, we cant download or make an account on that site due to our american IP anyway.
i will upload them when im home. i read sth about qc diag interface,qcn stuff. but this thread is a tutorial for cracking the China Telecom band. Dont know if theres anything useful
randy6644 said:
i will upload them when im home. i read sth about qc diag interface,qcn stuff. but this thread is a tutorial for cracking the China Telecom band. Dont know if theres anything useful
Click to expand...
Click to collapse
If you are able to export the Hex file with everything we need to restore through QPST you will be saving alot of peoples ass as the number of hard bricks are growing hourly now! Or at least the threads being started about hard bricks are! Appreciate the help brother. AdA
im not sure if i can find the useful files you need. just trying my best to contact that op , if he knows sth. my ass will ne saved. but its 1 .30 am in China.i dont think hes awake. i will keep an eye on that.
Hello there!
First of all, sorry for my bad english :/
Well i have the Kindle Fire HD 7. Tate Version.
So i had the Customrom Knology. After a year or so i developed some bugs, so i wanted to set it new etc.
Well i accidently erased the whole bootloader etc. :/
I have a factory cable. Via the Laptop of my Girlfriend i can connect the Kindle with factory cable in fastboot.
Then i ran the KFHD_SRTv1.3.5
Also SR-Tool.
After use Function 1 or 2.
Restore factory rooted etx.
I cant Start the kindle and its still in bootloop. Means Logo repeat and repeat Blinking.
Well when i try to erase the cache and userdata it takes LOOONG time for the userdata. i let it for hours but no result.
Well on PC itselfs i can Use the adb commands in the CMD window. But its waiting for Device. Both PC and Laptop have Windows 7 64 Bit
Pls help me :/
Trailerpark1 said:
Hello there!
First of all, sorry for my bad english :/
Well i have the Kindle Fire HD 7. Tate Version.
So i had the Customrom Knology. After a year or so i developed some bugs, so i wanted to set it new etc.
Well i accidently erased the whole bootloader etc. :/
I have a factory cable. Via the Laptop of my Girlfriend i can connect the Kindle with factory cable in fastboot.
Then i ran the KFHD_SRTv1.3.5
Also SR-Tool.
After use Function 1 or 2.
Restore factory rooted etx.
I cant Start the kindle and its still in bootloop. Means Logo repeat and repeat Blinking.
Well when i try to erase the cache and userdata it takes LOOONG time for the userdata. i let it for hours but no result.
Well on PC itselfs i can Use the adb commands in the CMD window. But its waiting for Device. Both PC and Laptop have Windows 7 64 Bit
Pls help me :/
Click to expand...
Click to collapse
Its gonna be hard to do anything if your PC doesn't recognize it or if your tablet doesn't respond to anything. Sounds to me like you're gonna have to get the stock firmware back on the device and start over with getting the second bootloader installed.
N_psycho_PD_uh? said:
Its gonna be hard to do anything if your PC doesn't recognize it or if your tablet doesn't respond to anything. Sounds to me like you're gonna have to get the stock firmware back on the device and start over with getting the second bootloader installed.
Click to expand...
Click to collapse
Well as i said with the laptop i can connect... how do i Install the Stockrom?
If you have a stock firmware .img then you should be able to flash it through fastboot.
Y?
Well which is the right firmware for me?
Trailerpark1 said:
Y?
Well which is the right firmware for me?
Click to expand...
Click to collapse
Its been a while since I've messed with a kindle so I'm not sure what firmware you need. That is decided by which model/version of kindle you have. I have the very first kindle, its been almost two years since I did any custom stuff to it and I've gone through many other devices since then. I wish I could help with an exact answer, I was only trying to get you headed in the right direction. Find your firmware based on which kindle you have.
Well i know which my kindle is. The CMD Command said, that the firmware is on the kindle. and then still bootloop
Trailerpark1 said:
Well i know which my kindle is. The CMD Command said, that the firmware is on the kindle. and then still bootloop
Click to expand...
Click to collapse
OK, so your firmware is still there and still shows but your bootloader is wiped out? OK, same answer, reflash your stock firmware to see if it will repair the bootloader and see if it will boot, if you've already tried flashing and it did nothing to restore your bootloader then I'm not sure what you can do about that, I don't understand the stock kindle stuff as well as I do other android devices, its kind of in its own class of android because its more android-ish than it is actual full on android so I don't know its elements are quite different.
Well thankl you then. Maybe anyone can help instead of u :/
Trailerpark1 said:
Well thankl you then. Maybe anyone can help instead of u :/
Click to expand...
Click to collapse
As I said, I wasn't trying to give you a definite answer, I was just trying to get you in the right direction. It IS the only response you've gotten so I wouldn't be so snide if I were you, I could have not answered and you would still be waiting for an answer from someone even now. I've told you what you can do to get straight, from what I've experienced the only thing you can do from the point that you're at is do some extensive searching on Google to find the build number of the stock firmware your device shipped with based on which version of kindle that you have and install it through fastboot, I know of nothing else that will restore a device from the state yours is in. If it doesn't work then the device is probably dead and useless.
Sorry pal, i doesnt want to be rude or snyde.. Im rly grateful to you.
as i said my english is bad.. and i had a long day... Sorry for being inpolite.
Trailerpark1 said:
Sorry pal, i doesnt want to be rude or snyde.. Im rly grateful to you.
as i said my english is bad.. and i had a long day... Sorry for being inpolite.
Click to expand...
Click to collapse
No problem, I was only trying to help in the capacity that I could. Have you taken what I've told you and asked around in other threads how to go about using it to get your kindle fixed?
Have you tried getting someone with the same device as yours that still has the stock firmware like yours to do a ROM dump in terminal emulator to create an .img for you then upload it so you can download it then try pushing it to your device through terminal on PC? It may work for you. Can you even boot to recovery? I expect not since you killed your bootloader. Have you tried flashing recovery through fastboot then trying to boot to recovery? I'm not sure that will work either but its worth trying.
Hello , I have a Moto X first gen Verizon model . Stock Bootloader locked and non rooted. It was working fine and just randomly switched off and won't completely boot back up again, It is stuck at the Boot screen with The Moto X Blue Logo . Running 4.4.4 . I tried doing a reset it didn't work. I tried going into recovery it didn't work , it comes back to the boot logo.
Any suggestions ? Please help. ?
galaxys3lover said:
Hello , I have a Moto X first gen Verizon model . Stock Bootloader locked and non rooted. It was working fine and just randomly switched off and won't completely boot back up again, It is stuck at the Boot screen with The Moto X Blue Logo . Running 4.4.4 . I tried doing a reset it didn't work. I tried going into recovery it didn't work , it comes back to the boot logo.
Any suggestions ? Please help. ?
Click to expand...
Click to collapse
I would boot into bootloader mode and flash stock system.img and boot.img.
JulesJam said:
I would boot into bootloader mode and flash stock system.img and boot.img.
Click to expand...
Click to collapse
Thank you so much for replying.. Could you give me instructions on how to do that? Also where can I get the system files for my phone?
Kind of dissapointed that you created a thread, asked in multiple places, and PM'd me the same question/issue. Especially considering it was 4AM eastern time when you started asking... (non of us in the USA would have been on, or well, very very few would have been on)
For those watching... I've posted a few replies and suggestions after post 191 in this thread -> http://forum.xda-developers.com/moto-x/moto-x-qa/help-thread-moto-x-question-t3032022/page8
KidJoe said:
Kind of dissapointed that you created a thread, asked in multiple places, and PM'd me the same question/issue. Especially considering it was 4AM eastern time when you started asking... (non of us in the USA would have been on, or well, very very few would have been on)
For those watching... I've posted a few replies and suggestions after post 191 in this thread -> http://forum.xda-developers.com/moto-x/moto-x-qa/help-thread-moto-x-question-t3032022/page8
Click to expand...
Click to collapse
I know , I am sorry , i was just really freaked out .. please go ahead and delete the other thread. I apologize.
Thank you so much for your patience and help. I have tried unlocking the bootloader and flashing stock firmware (both were succesfull) but the problem still remains , it is stuck on the boot screen. (earlier at the MOTO M Logo and now at Warning Bootloader unlocked screen) . There are no service centers where I Live so I can't send it to a service center , is there any last resort methods I could try ? Once again , Sorry and Thank you.
galaxys3lover said:
I know , I am sorry , i was just really freaked out .. please go ahead and delete the other thread. I apologize.
Thank you so much for your patience and help. I have tried unlocking the bootloader and flashing stock firmware (both were succesfull) but the problem still remains
Click to expand...
Click to collapse
Did you flash using RSDLite? That is the safest thing to do. Also, did you enable USB debugging and authorize your computer?
If not using RSD lite, how are you flashing back to stock?
Also, have you tried installing Motorola Device Manager and letting it repair your phone? You get into bootloader mode and then plug your phone into your computer and start MDM.
JulesJam said:
Did you flash using RSDLite? That is the safest thing to do. Also, did you enable USB debugging and authorize your computer?
If not using RSD lite, how are you flashing back to stock?
Also, have you tried installing Motorola Device Manager and letting it repair your phone? You get into bootloader mode and then plug your phone into your computer and start MDM.
Click to expand...
Click to collapse
I manually flashed the stock firmware with mfasboot , will try the MDM and let you know .
galaxys3lover said:
Hello , I have a Moto X first gen Verizon model . Stock Bootloader locked and non rooted. It was working fine and just randomly switched off and won't completely boot back up again, It is stuck at the Boot screen with The Moto X Blue Logo . Running 4.4.4 . I tried doing a reset it didn't work. I tried going into recovery it didn't work , it comes back to the boot logo.
Any suggestions ? Please help. ?
Click to expand...
Click to collapse
I've struggled with a similar issue on an XT1053, though mine already had an unlocked bootloader. Phone freaked out, shut down, and now crashes every time a few seconds after it gets to the blue logo., and goes into endless bootloops. Here for more detail -http://forum.xda-developers.com/moto-x/moto-x-qa/boot-loop-puzzle-t3080565
Since I've flashed the stock images a couple of times (which seems to work, or at least shows no errors), I think it might be a hardware or battery issue. I'll try MDM, but am not especially optimistic.
Had you installed any new apps? I had been playing a new driving game on the day it crashed, though it might be coincidence.
So i have a Moto g xt1072 wich i got second hand.. i got it into recovery mode and eventually got it working, but it was really unstable, so i wanted to reflash the stock rom, because it looked like the current one on the phone was corrupted (i was running android 6.0) (btw i have a xt1068 as my daily driver, but i want this to work again)
So i started flashing http://forum.xda-developers.com/moto-g-lte/general/stock-6-0-marshmallow-europe-reteu-t3338075 <-this
but i had errors and it was failing multiple times.. so i looked up some tutorials, and most of them were unlocking the bootloader at the beginning, so i was unlocking and locking the bootloader trying to get the commands to work,
then i found a tutorial wich coppyd all of the commands at once, so i tried that.. screen went black..
Wont boot into recovery, 3sec method or 120 sec method, and connects to my pc as QHSUSB_BULK
luckily i made a picture of the recovery when i tried to flash:
http://imgur.com/8avCk3T
I think i may need to blank flash, but im not certain..
I would also like to find the firmware for this phone that wont brick it..
Can anyone help?
Need more info?
Please just ask me, i will respond immediately
i dont care what i need to do.. even if i need to hardwire (because im really good at those finicky things)
Thanks for reading XD
Same issue here. I flashed a stock image and something must've gone wrong at some point
hamzahrmalik said:
Same issue here. I flashed a stock image and something must've gone wrong at some point
Click to expand...
Click to collapse
you probably also flashed the vootloader and the bootanimation, these are known to give problems, but ive foubd a test point on the pcb which brings the phone in a les hard bricked state, but ive yet to find a method to unbrick the phone..
ill keep you posted
ora69 said:
you probably also flashed the vootloader and the bootanimation, these are known to give problems, but ive foubd a test point on the pcb which brings the phone in a les hard bricked state, but ive yet to find a method to unbrick the phone..
ill keep you posted
Click to expand...
Click to collapse
Sorry could you please explain. How can a phone be less hard bricked. Thanks
Sent from my A0001 using Tapatalk
hamzahrmalik said:
Sorry could you please explain. How can a phone be less hard bricked. Thanks
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
okay, so there are different types of hardbricks, all act the same, but one is harder to unbrick than the other, there is qh usb bulk and qhas bulk with numbers behind it, search for force unbrick lg g2,
now the problem is, it should be easy to unbrick the phone at thsi point, but im not an expert in that and have no idea what to do now xD so i posted it on xda, but no one answered me.. xD hopefully this clears it up some more
ora69 said:
okay, so there are different types of hardbricks, all act the same, but one is harder to unbrick than the other, there is qh usb bulk and qhas bulk with numbers behind it, search for force unbrick lg g2,
now the problem is, it should be easy to unbrick the phone at thsi point, but im not an expert in that and have no idea what to do now xD so i posted it on xda, but no one answered me.. xD hopefully this clears it up some more
Click to expand...
Click to collapse
Oh ok I get you. Mines USB bulk 9000 or something i can't remmeber now
Sent from my A0001 using Tapatalk
ora69 said:
So i have a Moto g xt1072 wich i got second hand.. i got it into recovery mode and eventually got it working, but it was really unstable, so i wanted to reflash the stock rom, because it looked like the current one on the phone was corrupted (i was running android 6.0) (btw i have a xt1068 as my daily driver, but i want this to work again)
So i started flashing http://forum.xda-developers.com/moto-g-lte/general/stock-6-0-marshmallow-europe-reteu-t3338075 <-this
but i had errors and it was failing multiple times.. so i looked up some tutorials, and most of them were unlocking the bootloader at the beginning, so i was unlocking and locking the bootloader trying to get the commands to work,
then i found a tutorial wich coppyd all of the commands at once, so i tried that.. screen went black..
Wont boot into recovery, 3sec method or 120 sec method, and connects to my pc as QHSUSB_BULK
luckily i made a picture of the recovery when i tried to flash:
http://imgur.com/8avCk3T
I think i may need to blank flash, but im not certain..
I would also like to find the firmware for this phone that wont brick it..
Can anyone help?
Need more info?
Please just ask me, i will respond immediately
i dont care what i need to do.. even if i need to hardwire (because im really good at those finicky things)
Thanks for reading XD
Click to expand...
Click to collapse
So that link to another thread in XDA forum, I think I had a similar experience. I too have the XT1072 as I live in the UK. now here on XDA you have to be careful and ask 3 4 maybe 5 times before someone listens properly. I know it is hard for the devs with so many dumb noobs asking so many dumb questions, I include myself as a noob so no worries. Anyway to get to the point that link is not referring to our phone the XT1072. You should ignore LTE in your search criteria, it will always point you towards the 2015 model and believe you me all roms in my experience area very device specific. You need to simply put Moto G 2nd gen 2014 in search criteria when it comes to searching for custom recoverys and/or stock ROMS. The Titan.IMG is always a safe bet if I remember correctly, dont take my word for it, I have been known to have a memory like a sieve now and again, the problem with getting older, cache gets smaller and smaller, lol! Best of luck!
hamzahrmalik said:
Sorry could you please explain. How can a phone be less hard bricked. Thanks
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Read the beginning on this article: http://rootmyandroid.org/how-to-unbrick-your-android-device-the-ultimate-guide.html/
the bricked term is a common misconception for phones that still turn on..