Related
Moto X does not call any more do not connect in the computer it does nor do noise of connection, I already did combination of keys. He was with more than 80 % of battery. I did already from everything and nothing. Help me please
What version are you on? I've seen your thread history.... Did you downgrade?
What have you done or tried to do to your phone?
At any rate.... Flashing the firmware again for your device... SAME version again... Will hopefully fix you up.
See the "complete Moto X guide" in general, under the return to stock section for instructions.
This will only work if flashable files are out yet for your phone and version of android.
If you flashed a different carriers firmware or downgraded.... You may be in trouble.
I was in 4.4.2 Stock Retail BR and I updated for 4.4.3. Before it had done the Downgrade of 4.4.4 for 4.4.2. After the updating for 4.4.3 when he restarted it was black and did not answer any more.
So, to be clear.... You downgraded from 4.4.4 to 4.4.2.
Then you did the OTA update to 4.4.3.
Is this right?
If it is.... You may be in trouble. You downgraded, then took an OTA. That is a very poor thing to do. And I'm sorry, but people warned you NOT to downgrade in your other threads. Also, warnings about NOT ever downgrading are everywhere in the Moto X section. Next time, taking the advice that the experienced guys give you would be a great idea.
We haven't seen many of 4.4.4 downgrade posts yet. So it's hard to say what can fix you. I'm thinking you will have to wait until files for 4.4.4 are released for your phone model and flash them with fastboot.
Until then.... You may be out of luck.
Please read read read and do some research before doing things in the future. Lesson learned I guess. Also.... When people say don't do something..... Is usually best not to do it. ?
Let's see if any other X experts have some ideas.
Good luck!
Does it have anything that I could do to revive my appliance? Or only a technician?
Christian Correia said:
Does it have anything that I could do to revive my appliance? Or only a technician?
Click to expand...
Click to collapse
If you had 4.4.4 on your phone then downgraded, the safest way to be able to fix it yourself (or with a forum member's help) will be to wait until the 4.4.4 SBF/FXZ for your phone's model and carrier to be leaked. We have no idea when that might happen, as we wait for someone to "FIND" the files.
IF your phone boots into the Android OS, then once the 4.4.4 SBF for your phone model/carrier leaks, you can use mfastboot and a series of commands to get back to working.
But if your phone is totally messed up, you could try and follow -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057 and follow it up by flashing the latest SBF which has already leaked for your phone model and carrier. BUT I have NO EXPERIENCE with that process, so I suggest you read that thread, and ask questions over there.
If you don't want to do that, or can't wait for the SBF to leak, then you can buy a new phone.
I already tried to do this tutorial-> http: // forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057 and it did not give right. So the cellular thing not of no type of connection with the PC
Unfortunately, if you can't communicate with the pc ... And you've reinstalled the Moto drivers, tried other cable, other USB ports on the pc... And even another pc... And still it won't see your phone.... Then there's nothing you can do.
He showed up. The green LED lighted and then he disconnected and it connects and desconecta next.
Until that issue is solved, there's nothing you can do. The phone needs to connect and stay connected.
Try everything I've said in my last post.
If nothing works, best to send in the phone for repair or exchange.
In the future, read and study everything and follow instructions completely before doing anything. Also, take advice from senior members.
And don't ever downgrade A Moto X.
Hope it works out for you!!
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.
Help me, blink my phone, moto x, after trying to install lollipop, corrupted bootloader and can not restore it!
We Need more details to be able to help you.
like...
What model do you have? XT1052? XT1058? XT1053, etc?
What rom was on your phone? Stock, custom? what andrid version?
What exactly did you do? flash rom xxxx using RSDLite? flash rom xxx using mFastboot? installed xxx.zip via TWRP?
What exact error do you see on your phone? (Can you post a picture)?
KidJoe said:
We Need more details to be able to help you.
like...
What model do you have? XT1052? XT1058? XT1053, etc?
What rom was on your phone? Stock, custom? what andrid version?
What exactly did you do? flash rom xxxx using RSDLite? flash rom xxx using mFastboot? installed xxx.zip via TWRP?
What exact error do you see on your phone? (Can you post a picture)?
Click to expand...
Click to collapse
XT1058, Lollipop used RSDLite..
The truth is that I see nothing as it does not turn with the corrumpido bootloader nothing happens ..
I'm trying to use the blankflash but nothing happens ..
It gives an error in the process ..
I am very aperriado because naum can buy another phone now, I'm broke, I need help ..
Thank right now
---------------------------------------------------------------------------------
I encontreu one aquivo here with various MSM8960 structures, however, I do not know if it is for something ..
J_Eudes said:
XT1058, Lollipop used RSDLite..
The truth is that I see nothing as it does not turn with the corrumpido bootloader nothing happens ..
I'm trying to use the blankflash but nothing happens ..
It gives an error in the process ..
I am very aperriado because naum can buy another phone now, I'm broke, I need help ..
Thank right now
---------------------------------------------------------------------------------
I encontreu one aquivo here with various MSM8960 structures, however, I do not know if it is for something ..
Click to expand...
Click to collapse
How did you get in this state? What did you do?
If trying to use blankflash, you will want to see this thread -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057 in particular around posts 442 through 455
KidJoe said:
How did you get in this state? What did you do?
If trying to use blankflash, you will want to see this thread -> http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057 in particular around posts 442 through 455
Click to expand...
Click to collapse
I do not understand English, ssou of Brazil , to read it all would take one year kkk my moto x lights the green led sometimes , that's good ?
You have the lollipop bootloader Archive ?
please save my life
J_Eudes said:
I do not understand English, ssou of Brazil , to read it all would take one year kkk my moto x lights the green led sometimes , that's good ?
Click to expand...
Click to collapse
Grean light means battery is dead and needs to be charged.
Travisdroidx2 said:
Grean light means battery is dead and needs to be charged.
Click to expand...
Click to collapse
What if I reload , it will come to life again ?
J_Eudes said:
What if I reload , it will come to life again ?
Click to expand...
Click to collapse
You need to get some charge in it if you are trying to flash anything. Unless you have a factory cable, a factory USB cable will charge the battery even if your phone is bricked
Travisdroidx2 said:
You need to get some charge in it if you are trying to flash anything. Unless you have a factory cable, a factory USB cable will charge the battery even if your phone is bricked
Click to expand...
Click to collapse
I have already put to load ...
This tool works here?
http://forum.xda-developers.com/showthread.php?t=2136738
J_Eudes said:
I have already put to load ...
Click to expand...
Click to collapse
Good.
Is that Qualcomm HS-USB*** thing still there in Device Manager when you have phone connected to PC?
What exactly did you flash in to brick your phone? Link to it, please
s5610 said:
Good.
Is that Qualcomm HS-USB*** thing still there in Device Manager when you have phone connected to PC?
What exactly did you flash in to brick your phone? Link to it, please
Click to expand...
Click to collapse
I was trying to put the new version of lollipop
****** NEWW ********
I can restore it, but only had to put other files and install new versions of python (2.7) and also the pyserial ...
######THANKS############
Thank you for helping me and for giving me attention! : Boa:: Toca aqui:: Dedos cruzados:: Rir:: Vitória:
KidJoe said:
We Need more details to be able to help you
Click to expand...
Click to collapse
What's happening? Bricks run away from us ) No, I have a hunch they return lately. Motorola isn't that easy quest.
Most annoying thought for me now is what will happen with those who raised their locked boot loaders to high Lollipop versions. Will they get flashable SBF (RSD) firmware, or not...
I could, but I lost a lot of night sleep kkkk other words, has that much to wrap your head get
Sent from my Moto X using XDA Premium 4 mobile app
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..