Database Info

[Q] NEXUS 5 BRICKED TRYING TO ROOT WITH CF AutoRoot. HELP!?

Hi all
A bit new to posting in here but am really hoping to receive some help from you all. Last night I installed all the standard USB drivers i.e. Android SDK pack and followed them all as mentioned. Then using the root tool from ChainFire I got to the little android guy after going through the process of unlocking the bootloader and gaining root, but the phone never actually rebooted.
Now when I try to flash the original fastboot files using the WUG kit I get "FAILED: remote: flash write failure" The same is the case with writing the boot img and recovery img. See attached.
I can put the phone into Fastboot mode only and it says lock state is "unlocked" but it would seem that I can no longer write anything to the internal disk as nothing will work or boot. I also get a status on my PC saying that the driver QHSUSB_Bulk could not be found.
Has anybody had a similar problem to this? Is there any way to somehow get this working again? And if I RMA with Google will they say my warranty is voided now that it says the lock state in Fastboot is unlocked?
Many thanks in advance guys any help is appreciated.

Meakii said:
Hi all
A bit new to posting in here but am really hoping to receive some help from you all. Last night I installed all the standard USB drivers i.e. Android SDK pack and followed them all as mentioned. Then using the root tool from ChainFire I got to the little android guy after going through the process of unlocking the bootloader and gaining root, but the phone never actually rebooted.
Now when I try to flash the original fastboot files using the WUG kit I get "FAILED: remote: flash write failure" The same is the case with writing the boot img and recovery img. See attached.
I can put the phone into Fastboot mode only and it says lock state is "unlocked" but it would seem that I can no longer write anything to the internal disk as nothing will work or boot. I also get a status on my PC saying that the driver QHSUSB_Bulk could not be found.
Has anybody had a similar problem to this? Is there any way to somehow get this working again? And if I RMA with Google will they say my warranty is voided now that it says the lock state in Fastboot is unlocked?
Many thanks in advance guys any help is appreciated.
Click to expand...
Click to collapse
Try flashing the factory images manually.
http://forum.xda-developers.com/showthread.php?t=2513701
Method 2.
Does fastboot work properly? What output does 'Fastboot devices" have?

abaaaabbbb63 said:
Try flashing the factory images manually.
http://forum.xda-developers.com/showthread.php?t=2513701
Method 2.
Does fastboot work properly? What output does 'Fastboot devices" have?
Click to expand...
Click to collapse
Thanks have tried flashing them manually but still the same error saying FAILED: remote: flash write failure
It as if nothing can be written to the phone at all.
Yea fastboot seems to work fine but sorry what do you mean by what ouput does fastboot devices have?
Thanks a lot

Meakii said:
Thanks have tried flashing them manually but still the same error saying FAILED: remote: flash write failure
It as if nothing can be written to the phone at all.
Yea fastboot seems to work fine but sorry what do you mean by what ouput does fastboot devices have?
Thanks a lot
Click to expand...
Click to collapse
write "Fastboot devices" in CMD while phone is in fastboot.
What happens when you boot in recovery? Try that, and do a factory data reset.

abaaaabbbb63 said:
write "Fastboot devices" in CMD while phone is in fastboot.
What happens when you boot in recovery? Try that, and do a factory data reset.
Click to expand...
Click to collapse
Ok see attached. Also it doesn't allow me to boot into recovery at all. I used the WUG kit to temporarily boot into TWRP and tried a factory reset there but it says there's no ROM installed. It's like everything has been wiped and it can't write anything to the internals to read from. Thanks for you help so far. Any other suggestions?

Meakii said:
Ok see attached. Also it doesn't allow me to boot into recovery at all. I used the WUG kit to temporarily boot into TWRP and tried a factory reset there but it says there's no ROM installed. It's like everything has been wiped and it can't write anything to the internals to read from. Thanks for you help so far. Any other suggestions?
Click to expand...
Click to collapse
Just... stop using toolkits for a second here! These automated processes got you here in the first place.
Try this command:
fastboot erase userdata
Does it succeed?

abaaaabbbb63 said:
Just... stop using toolkits for a second here! These automated processes got you here in the first place.
Try this command:
fastboot erase userdata
Does it succeed?
Click to expand...
Click to collapse
Ok ummm see attached. I'm so gutted any further thoughts or advice?

Meakii said:
Ok ummm see attached. I'm so gutted any further thoughts or advice?
Click to expand...
Click to collapse
It seems like a brick. Something got corrupted. I searched far an wide on XDA and other forums, but no one with this problem has found the solution.
It seems that your last chance is RMA.

abaaaabbbb63 said:
It seems like a brick. Your internal memory got corrupted. I searched far an wide on XDA and other forums, but no one with this problem has found the solution.
It seems that your last chance is RMA.
Click to expand...
Click to collapse
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?

Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
Who knows? Try it!
I don´t think the reason was CF-auto root. There must be something wrong with the device´s flash from the beginning. My thoughts are that you´r flash has a corrupted area which surprisingly wasn´t used for the stock factory flash and CF-autoroot triggered it while flashing a specific partition. Maybe i´m completely wrong.
I hope you´ll get it exchanged :good:.

Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
I don't really know what happened. I guess there are always risks when using tools like this. That's why I always recommend rooting using the manual method.
I have no idea how google will react. In theory, a simple unlocked bootloader won't affect warranty. In reality, anything can happen. Good luck, and sorry!

Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.

abaaaabbbb63 said:
I don't really know what happened. I guess there are always risks when using tools like this. That's why I always recommend rooting using the manual method.
I have no idea how google will react. In theory, a simple unlocked bootloader won't affect warranty. In reality, anything can happen. Good luck, and sorry!
Click to expand...
Click to collapse
Absolutely gutted but thanks so much for your help. I'll report back with Googles response.

pert_S said:
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
Click to expand...
Click to collapse
It will respond, but the memory won't flash. Major no-fix problem.

pert_S said:
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
Click to expand...
Click to collapse
Hi nah it only boots into Fastboot mode where it says down the bottom in red "LOCK STATE - unlocked" . Have tried every trick posted on here but it seems that during the rooting process somehow corrupted internal storage meaning it can't write anything to the phone (therefore not being able to reset to factory etc etc).
What a disaster.

Would opening the command prompt window with administrative rights make a difference? Worth a shot.

Meakii said:
Hi nah it only boots into Fastboot mode where it says down the bottom in red "LOCK STATE - unlocked" . Have tried every trick posted on here but it seems that during the rooting process somehow corrupted internal storage meaning it can't write anything to the phone (therefore not being able to reset to factory etc etc).
What a disaster.
Click to expand...
Click to collapse
Oh I see.
Well like abaaaabbbb63 said, in theory it shouldn't affect warranty.
They would have to show that unlocking the bootloader caused the fault I presume.

Make sure you tell Google that this happened when using a toolkit and a script when asking for a new phone free of charge.
Sent from my Nexus 5 using Tapatalk

El Daddy said:
Make sure you tell Google that this happened when using a toolkit and a script when asking for a new phone free of charge.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
How would that help? I think pleading ignorance to how it happened would probably be best wouldn't it?
Thanks for all the replies.

It's sarcasm friend. ;3. Daddy isn't a fan of toolkits nor of people claiming new handsets after a problem occurs as a result of one.

[Q] At&t htc one x problem

HELLO developers,i have some problem with my phone HTC ONE X from at&t.I try some programs to root them now my phone no turning on forced off next it dosen't charge can you help me please what i need to do to repair them how i can factory unlock.I can't put them to bootloader.Help me please
The fastboot is screanshot when the phone was OK,not from now ...

albhosts said:
HELLO developers,i have some problem with my phone HTC ONE X from at&t.I try some programs to root them now my phone no turning on forced off next it dosen't charge can you help me please what i need to do to repair them how i can factory unlock.I can't put them to bootloader.Help me please
The fastboot is screanshot when the phone was OK,not from now ...
Click to expand...
Click to collapse
What programs did you try and where did you get them exactly?

bimmernut318 said:
What programs did you try and where did you get them exactly?
Click to expand...
Click to collapse
i have try EZToolkit Cloud Evita.and when i try them i see errors i download HTC_One_X_RUU_5.18.502.1.exe working for moment next is down now i make some comands with linux and the red light is on. and when i press volume down + power off for 30 seccond phone try to turn on like in picture and forced down

albhosts said:
i have try EZToolkit Cloud Evita.and when i try them i see errors i download HTC_One_X_RUU_5.18.502.1.exe working for moment next is down now i make some comands with linux and the red light is on. and when i press volume down + power off for 30 seccond phone try to turn on like in picture and forced down
Click to expand...
Click to collapse
You need to be much more specific than that. The terms 'some errors' and 'some commands' don't mean anything unless you outline specifically what errors and what commands you're talking about. Did you run the RUU? If you did there's no way for you to unlock/root the phone now. And you need to run it twice to work in most cases.

I have problem now my phone not turning on how i can repair,i need to restore my phone again sorry for them but i am new .Help me Please!!!

You've been told twice already that you need to be more specific. I need the exact details of everything you did to the device leading up to now, otherwise I can't help you.
Sent from my Evita

sir copsis
timmaaa said:
You've been told twice already that you need to be more specific. I need the exact details of everything you did to the device leading up to now, otherwise I can't help you.
Sent from my Evita
Click to expand...
Click to collapse
Sorry man becouse im new to android,i need to put them in bootloader it can't i need to install jb rom i cant do this becouse my phone not booting .. how i can restore to factory exist any method what can i do or help me with comands how to turn on

albhosts said:
Sorry man becouse im new to android,i need to put them in bootloader it can't i need to install jb rom i cant do this becouse my phone not booting .. how i can restore to factory exist any method what can i do or help me with comands how to turn on
Click to expand...
Click to collapse
You still haven't given any information on what you've done to the device. You need to tell me everything I've done to the device.

albhosts said:
Sorry man becouse im new to android
Click to expand...
Click to collapse
Being new has nothing to do with it. I have a feeling there is a language barrier here. But you also have completely ignored the questions posed to you. You need to answer everything asked of you, and provide the proper specific information in order for anyone to help you. You haven't done that, so we can't help you, and just asking over and over again how to fix it, isn't going to change that.

redpoint73 said:
Being new has nothing to do with it. I have a feeling there is a language barrier here. But you also have completely ignored the questions posed to you. You need to answer everything asked of you, and provide the proper specific information in order for anyone to help you. You haven't done that, so we can't help you, and just asking over and over again how to fix it, isn't going to change that.
Click to expand...
Click to collapse
sorry for them im not ignoring,my problem is i have install htc one x+ firmware ruu and now the phone not turning on and i cant goo to bootloader if anyone have skype or any messanger to speak to help me.Thanks you people for helping us

If you've installed software or firmware from the One X+ onto the at&t One X then you've bricked the phone. There's nothing you can do except maybe get a jtag repair done, which may or may not work. Why on earth did you install software/firmware not intended for this device?
Sent from my Evita

timmaaa said:
If you've installed software or firmware from the One X+ onto the at&t One X then you've bricked the phone. There's nothing you can do except maybe get a jtag repair done, which may or may not work. Why on earth did you install software/firmware not intended for this device?
Sent from my Evita
Click to expand...
Click to collapse
my brother downloaded them i wasn't read the full name...now ****ed evrything

Yep, pretty much. It pays to be very careful when modifying your device.
Sent from my Evita

[Q] Phone hard bricked after unlocking bootloader

So it seems I've really put myself into a bad spot, here.
I recently rooted my phone (Verizon S3) using towelroot, which seemed to work exceedingly well, so I decided to try to make a NANDroid backup using ClockworkMod. I installed ROM Manager, set that up, and chose the "restart in Clockwork recovery mode option", which didn't work. I soon realized I forgot to unlock my bootloader so, at the recommendation of a few sites, used EZ-Unlock to try to do that. The app reported that it was successful, so I tried restarting my phone in Clockwork recovery mode again. To my utter horror, my phone did not turn on, and has not turned on since.
When I say that it doesn't turn on, I mean that it gives me no audio, vibrational, or visual feedback, almost like there's no battery in the phone. I've pulled the battery and also attempted to do the fix outlined in a video, but to no avail. (I would post the link if the forum allowed me to. The title of the video is "Unbrick hard bricked Verizon Galaxy S3 running 4.3 Jelly Bean")
Feel free to scold me all you like for my irresponsibility and stupidity, it's probably deserved. Any help will be hugely appreciated, though! Thank you so much!
Edit: I guess I should mention that this is my first time doing this sort of thing to an Android device. However, I do like to think I "know my way around", as they say. (although I guess not enough to avoid messing things up!)

Velovix said:
So it seems I've really put myself into a bad spot, here.
I recently rooted my phone (Verizon S3) using towelroot, which seemed to work exceedingly well, so I decided to try to make a NANDroid backup using ClockworkMod. I installed ROM Manager, set that up, and chose the "restart in Clockwork recovery mode option", which didn't work. I soon realized I forgot to unlock my bootloader so, at the recommendation of a few sites, used EZ-Unlock to try to do that. The app reported that it was successful, so I tried restarting my phone in Clockwork recovery mode again. To my utter horror, my phone did not turn on, and has not turned on since.
When I say that it doesn't turn on, I mean that it gives me no audio, vibrational, or visual feedback, almost like there's no battery in the phone. I've pulled the battery and also attempted to do the fix outlined in a video, but to no avail. (I would post the link if the forum allowed me to. The title of the video is "Unbrick hard bricked Verizon Galaxy S3 running 4.3 Jelly Bean")
Feel free to scold me all you like for my irresponsibility and stupidity, it's probably deserved. Any help will be hugely appreciated, though! Thank you so much!
Edit: I guess I should mention that this is my first time doing this sort of thing to an Android device. However, I do like to think I "know my way around", as they say. (although I guess not enough to avoid messing things up!)
Click to expand...
Click to collapse
You need to report your post so it can be moved to the Verizon s3 forums where you can get help for your problem.

Darke5tShad0w said:
You need to report your post so it can be moved to the Verizon s3 forums where you can get help for your problem.
Click to expand...
Click to collapse
Oh, my mistake. I'll do that right away. Thank you!

Velovix said:
Oh, my mistake. I'll do that right away. Thank you!
Click to expand...
Click to collapse
No problems. This is the forum for the International version and we don't have locked bootloaders so you will have more chance in there than you will here.

can you get the phone to go in to download mode? that power+home+vol down

Timothy08 said:
can you get the phone to go in to download mode? that power+home+vol down
Click to expand...
Click to collapse
No, unfortunately, I cannot. I hope I'm not already out of luck.

Velovix said:
No, unfortunately, I cannot. I hope I'm not already out of luck.
Click to expand...
Click to collapse
Was your phone on android 4.3 before you tried to unlock bootloader? If so, that isn't good.

sjpritch25 said:
Was your phone on android 4.3 before you tried to unlock bootloader? If so, that isn't good.
Click to expand...
Click to collapse
Uhh, yes, it was.. Any suggestions?

Velovix said:
Uhh, yes, it was.. Any suggestions?
Click to expand...
Click to collapse
Maybe try looking at the unbrick thread in the q&a?

Velovix said:
Uhh, yes, it was.. Any suggestions?
Click to expand...
Click to collapse
Do what the guy above suggested. Oh just so you know when you are on 4.3 you can not unlock your bootloader. Only root. Also once on 4.3 you can not downgrade to any earlier firmware versions. You can thank Verizon for that.
Sent from my SCH-I535 using Tapatalk

YevOmega said:
Maybe try looking at the unbrick thread in the q&a?
Click to expand...
Click to collapse
If you're referring to "[GUIDE] Debrick your bricked SCH-I535! [BOOTLOADER/HARDBRICK]", I have tried that a few times. I guess I could give it a few more shots if that's my only option.

Sandman-007 said:
Do what the guy above suggested. Oh just so you know when you are on 4.3 you can not unlock your bootloader. Only root. Also once on 4.3 you can not downgrade to any earlier firmware versions. You can thank Verizon for that.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
That's awful. I guess I was looking at a guide for a non-Verzion phone. Thank you for the information, though.

So, if I understand my situation, I guess the question now is: How can I lock my bootloader back up while it's hardbricked, correct?

Velovix said:
So, if I understand my situation, I guess the question now is: How can I lock my bootloader back up while it's hardbricked, correct?
Click to expand...
Click to collapse
No. Your only focus is on getting the phone to boot back up. The only method that we have to do so is the bootloader/hardbrick thread by SpryroDazee posted at the top of our Q/A section.

SlimSnoopOS said:
No. Your only focus is on getting the phone to boot back up. The only method that we have to do so is the bootloader/hardbrick thread by SpryroDazee posted at the top of our Q/A section.
Click to expand...
Click to collapse
Alright, I'll see what I can do. Thanks for the help!

Velovix said:
Alright, I'll see what I can do. Thanks for the help!
Click to expand...
Click to collapse
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-s3-bootloader-downgrade-service/
This might help. Try mobile tech videos. they can Jtag and downgrade for you.

[Q] Help me Unbrick my Moto G...please

Sorry for posting this, but please just try to understand me and help solve my problem. I know there is Threads for this, Please... I am just nowhere, my phone just treason me when I needed it most, It is very hard Bricked, nothing working, contacted support and they told me it need Replace (but I can't send to service #close this question)
My Story:
Constant restart loop, on Motorola logo. It can go in Bootloader when press Vol Down and Power Button, but that's it, (actually when going in recovery it goes to Broken Android sign, but than restart again)... so how it happened?? I do not know as u do not, I am just normal user, never done anything to crash system, never Rooted, even not installed any kind Launcher, nothing, just some normal Apps and only two game, and lot of music listening, that's it that's all (also physically it's like new, never ever droped or water splashed even). and one day come home, plug in for charging in my PC as always and boom, some strange app crashes and it restarted for EVERRR, wtf is this just do not understand, WHYY?????? so disappointed and so bored...
Question:
so Can it be Helped? Unbricked? I do not care Contacts or any kind Data, just work again....And if it can please step by step I will follow, and do not redirect me to other thread, just help me out here please
And if it cant be Helped, just say frankly and I will capture video how I am splashing it on REAL BRICK wall and will post it on this thread...this will be closing and **** sending of Motorola
My Spec:
Moto G (16GB Global GSM, no SD card slot, single SIM) - KitKat 4.4.4 (it bricked so I cant see Falcon version or other spec, but I have original Box)
I searched everywhere and seen lot, but all of them are 4.4.2 or 3 and also US versions, strange languages and so on. also here on XDA but as I'm Noob I do not know if it will work for me, and before destroy it completely I wanted to know from people who knows much more then me, what can do and what not, so please be patient for my Noobety, Thanks and Sorry...

help_me_if_u_can said:
Sorry for posting this, but please just try to understand me and help solve my problem. I know there is Threads for this, Please... I am just nowhere, my phone just treason me when I needed it most, It is very hard Bricked, nothing working, contacted support and they told me it need Replace (but I can't send to service #close this question)
Click to expand...
Click to collapse
Do you use Windows, Linux, Mac?
EDIT: Have you tried this yet? http://forum.xda-developers.com/showthread.php?t=2542219

StrangerWeather said:
Do you use Windows, Linux, Mac?
EDIT: Have you tried this yet? http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
I have Windows 8 x64, I did not tryed anything yet, want to know what would be clever and correct to do in my situation...which one should I download ???? from here
have no idea, all I know is before It bricked it was on 4.4.4 and I do not have US version, it is GLOBAL GSM
and it is Locked, never Unlocked Bootloader

help_me_if_u_can said:
I have Windows 8 x64, I did not tryed anything yet, want to know what would be clever and correct to do in my situation...which one should I download ???? from here
have no idea, all I know is before It bricked it was on 4.4.4 and I do not have US version, it is GLOBAL GSM
and it is Locked, never Unlocked Bootloader
Click to expand...
Click to collapse
Dual sim or single sim? What region?

StrangerWeather said:
Dual sim or single sim? What region?
Click to expand...
Click to collapse
Single Sim, Georgia (not in US)

help_me_if_u_can said:
Single Sim, Georgia (not in US)
Click to expand...
Click to collapse
Ok, is it XT1032?
Don't worry, we'll get there...

StrangerWeather said:
Ok, is it XT1032?
Click to expand...
Click to collapse
I do not remember, is there any way to check it? I will do that if so, thanks

help_me_if_u_can said:
I do not remember, is there any way to check it? I will do that if so, thanks
Click to expand...
Click to collapse
Not sure. Just one thought, why don't you try a factory reset? https://www.youtube.com/watch?v=LoTAsuPey_E

StrangerWeather said:
Not sure. Just one thought, why don't you try a factory reset?
Click to expand...
Click to collapse
Remember with Support Team I already did that, but not worked.
I will try again as in this video after couple hours and share results quickly.

StrangerWeather said:
Not sure. Just one thought, why don't you try a factory reset?
Click to expand...
Click to collapse
so, I can reach to wipe manu and wiped it also wipe cache from there but not like in this video, my device is laggin on every step and after I wiped it steel when restart it normaly stuckes on Motorola
one thing to add, my device is not Power Off, it constatnly restating, if I will try to power off it will power on again

help_me_if_u_can said:
so, I can reach to wipe manu and wiped it also wipe cache from there but not like in this video, my device is laggin on every step and after I wiped it steel when restart it normaly stuckes on Motorola
one thing to add, my device is not Power Off, it constatnly restating, if I will try to power off it will power on again
Click to expand...
Click to collapse
Ok, don't worry, just follow the tutorial to reflash stock firmware and it will work again.
You need this: http://www.filefactory.com/file/1dw..._4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml.zip
The only thing to say is that when you reach:
Code:
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
you may have to try this instead if it doesn't work:
Code:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
Let us know how it goes!

okey I will try it right now, thaanks

StrangerWeather said:
Let us know how it goes!
Click to expand...
Click to collapse
I tryed but no result, I think because that my bootloader is locked....here I made screenshot of whole process and every command gives me [OKEY] but after that is failure....it I think is permissions problem because locked bootloader
So, I need to unlock it right?????? I already have key from motorola, just get... I will wait your answer...

StrangerWeather
??????????????

help_me_if_u_can said:
StrangerWeather
??????????????
Click to expand...
Click to collapse
Oops, sorry, I forgot... It's up to you about unlocking bootloader. If you do, you can't send your phone back for them to sort out the problem. However, if you root your phone, you'll be able to install a custom recovery such as TWRP, sideload a rom, and hopefully all will work. But of course I can't guarantee that it will work, so it's a risk. If it were me, I would send it back as you haven't rooted it and really it shouldn't brick itself on its own for no reason.

StrangerWeather said:
Oops, sorry, I forgot... It's up to you about unlocking bootloader. If you do, you can't send your phone back for them to sort out the problem. However, if you root your phone, you'll be able to install a custom recovery such as TWRP, sideload a rom, and hopefully all will work. But of course I can't guarantee that it will work, so it's a risk. If it were me, I would send it back as you haven't rooted it and really it shouldn't brick itself on its own for no reason.
Click to expand...
Click to collapse
tell me, if I want to install this stock firmware I need to unlock bootloader??? and because it not installing? or my device is problematic and it can be installed on locked bootloader?

help_me_if_u_can said:
tell me, if I want to install this stock firmware I need to unlock bootloader??? and because it not installing? or my device is problematic and it can be installed on locked bootloader?
Click to expand...
Click to collapse
This what the op says:
I have only tested this on a UK Retail Moto G with an unlocked bootloader, however as these are the original stock signed image files from Motorola it should work on all devices.
[. . .]
Edit: tkm89 reports that he was able to use this guide to restore Stock Retail British firmware on a bootloader locked Tesco-mobile Moto G
Click to expand...
Click to collapse

StrangerWeather said:
This what the op says:
Click to expand...
Click to collapse
I unlocked BOOTLOADER but steel geting Fail after OKEY, what could be reason? can I do something??? any ****ing thing to start this device working??

help_me_if_u_can said:
I unlocked BOOTLOADER but steel geting Fail after OKEY, what could be reason? can I do something??? any ****ing thing to start this device working??
Click to expand...
Click to collapse
I'm not sure what the reason is but if I were you I would now try to root my device, install TWRP, sideload a rom, and hope for the best.
To root, use: http://www.theandroidcop.com/how-to-root-motorola-moto-g/
Hope it goes well!

no help....
on every step, I am getting Fails....What could be Problem??? drivers??? or what?????? ANYONE????????
Unlocked Bootloader

Adb update! Plz help stuck in recovery! [Q&A],[SOFTBRICK/BOOTLOOP], QTAQZ3

Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
Device-State:Recovery/Bootloader
Ellipsis 8
QTAQZ3
Vendor:Verizon Wireless
Build:KTO49
4.2KitKat

samson716 said:
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
?
Click to expand...
Click to collapse
You want help with a device but you don't tell us any kind of information about your device, how smart was that? What you need and how to do it can depend on what device model number you have.
Sent from my SM-S903VL using Tapatalk

SORRY
Droidriven said:
You want help with a device but you don't tell us any kind of information about your device, how smart was that? What you need and how to do it can depend on what device model number you have.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3/4.2Jellybean/KTO49

samson716 said:
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3
4.2Kitkat
KTO49
Thanks!
Click to expand...
Click to collapse

samson716 said:
samson716 said:
Not very smart at all sorry about that! I didnt disclose that, reason being the research i have done everybod turns there head when this crap device is mentioned. Yes I agree not worth time and energy but already invested so much time its worth it to me and also i have.
Ellipsis8
QTAQZ3
4.2Kitkat
KTO49
Thanks!
Click to expand...
Click to collapse
are you using stock recovery or a custom recovery?
Click to expand...
Click to collapse

ayu321 said:
samson716 said:
are you using stock recovery or a custom recovery?
Click to expand...
Click to collapse
Stock
Click to expand...
Click to collapse

samson716 said:
ayu321 said:
Stock
Click to expand...
Click to collapse
Can you please tell me that what caused this problem ? what were you doing with the device? flashing roms ?
Click to expand...
Click to collapse

ayu321 said:
samson716 said:
Can you please tell me that what caused this problem ? what were you doing with the device? flashing roms ?
Click to expand...
Click to collapse
No I was literally doing nothing I was actually flashing my Samsung Device at that moment. From what I remember it occurred when I noticed at update to marshmallow updated then rebooted it. Ever since its been in this bootloop! Im not trying to root it put a custom rom on it just want it to function nothing special.
Click to expand...
Click to collapse

samson716 said:
ayu321 said:
No I was literally doing nothing I was actually flashing my Samsung Device at that moment. From what I remember it occurred when I noticed at update to marshmallow updated then rebooted it. Ever since its been in this bootloop! Im not trying to root it put a custom rom on it just want it to function nothing special.
Click to expand...
Click to collapse
You have soft bricked your phone . The only way to fix it is it flash its stock rom. If you are new to this stuff I would suggest you to read this article carefully and if you have any doubts , ask me.
https://www.maketecheasier.com/android-root-custom-recovery-and-roms/
Click to expand...
Click to collapse

samson716 said:
Hello everyone, I have a tablet that is stuck in recovery and looks to me ADB is going to be the only way out here. Problem is ADB isnt recognizing my device, device manager named it MTP but computer says Android. I have tried changing the USB /VID ID that reads off what is displayed in Device manager not sure if I did it right running myself crazy really, read HRS of Android info Im a noob but a fast learner especially if I get a little bit of guidance. I have tried doing every and all factory hard resets tried different flash tools probably didnt work because my computer doesnt display the correct model. Im trying to learn python at the very moment new to all of this have only hrs of experience of this all. Somebody plz be ever so kind to help me out, thanks!
Device-State:Recovery/Bootloader
Ellipsis 8
QTAQZ3
Vendor:Verizon Wireless
Build:KTO49
4.2KitKat
Click to expand...
Click to collapse
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a device exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk

ayu321 said:
samson716 said:
You have soft bricked your phone . The only way to fix it is it flash its stock rom. If you are new to this stuff I would suggest you to read this article carefully and if you have any doubts , ask me.
https://www.maketecheasier.com/android-root-custom-recovery-and-roms/
Click to expand...
Click to collapse
Okay not sure which Flash tool to use nor get my stock rom I dread to say but i dont think there is one available. Its a generic tablet its made by Quanta. Not sure how to put it in a download mode either I assume ADB is the only way to transfer any files.
Click to expand...
Click to collapse

Your device probably uses SPFlashtool or fastboot.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a deuce exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Its pretty easy to fix a soft bricked device , even if stock rom isnt available , any rom compatible with his device can fix the issue .

ayu321 said:
Its pretty easy to fix a soft bricked device , even if stock rom isnt available , any rom compatible with his device can fix the issue .
Click to expand...
Click to collapse
To be compatible, the ROM typically has to be ported and that usually requires the stock firmware or stock source from the device that the ROM is being ported over to. 99% of the time you can't just flash a ROM from a different model number, even if the CPU is the same, there's quite a bit more to it than that. The android operating system is built for the specific hardware it is installed on, the two devices would have to be exactly the same and have the exact same components, any differences in hardware make he firmwares incompatible.
For this particular device, I doubt the stock firmware or stock source code area available, even if it were, porting another ROM wouldn't be necessary because if it were available it could just be flashed with that instead of porting a ROM.
About the only time a ROM from a different model number can be used without any porting or edits being made is when the devices are exactly the same device just rebranded with a different "name".
But thanks for trying to tell me something that you thought I didn't know, now it seems I've told you something that you didn't know.
Sent from my SM-S903VL using Tapatalk

samson716 said:
ayu321 said:
Okay not sure which Flash tool to use nor get my stock rom I dread to say but i dont think there is one available. Its a generic tablet its made by Quanta. Not sure how to put it in a download mode either I assume ADB is the only way to transfer any files.
Click to expand...
Click to collapse
1.Search for your tablet's root package , download it and move it to your tablet's sd card. Then enter your recovery mode by pressing power button+ Home button+ Volume button at same time for 10sec. Once entered , go to option "apply update from sd card" and select the root package you downloaded. (CONGRATS YOU HAVE ROOTED YOUR PHONE!)
2.Search for your tablet's 'custom recovery' , download it and flash it through odin tool(pc) .
3.Final Step ! BASED ON THE RECOVERY YOU FLASHED THESE STEPS MAY DIFFER , SO REPLY ME IF YOU SUCCEED IN FLASHING CUSTOM RECOVERY
Click to expand...
Click to collapse

ayu321 said:
1.Search for your tablet's root package , download it and move it to your tablet's sd card. Then enter your recovery mode by pressing power button+ Home button+ Volume button at same time for 10sec. Once entered , go to option "apply update from sd card" and select the root package you downloaded. (CONGRATS YOU HAVE ROOTED YOUR PHONE!)
2.Search for your tablet's 'custom recovery' , download it and flash it through odin tool(pc) .
3.Final Step ! BASED ON THE RECOVERY YOU FLASHED THESE STEPS MAY DIFFER , SO REPLY ME IF YOU SUCCEED IN FLASHING CUSTOM RECOVERY
Click to expand...
Click to collapse
Odin is for Samsung devices, not other devices.
The device they are repairing is not a Samsung device. They have this device and a Samsung device. The issue on this device occurred while they were in the process of flashing their Samsung device.
I know you're trying to help but don't post anything unless you are absolutely certain that you know what you're talking about.
In this case, you didn't and that can easily lead to a hard bricked device because they followed your instruction.
Stick to answering questions about devices you personally have dealt with, don't go assuming that you understand someone else's device. They are all different, the methods, tricks and tools for one won't necessarily work on another.
You understand android somewhat but judging by your posts, you don't understand the differences in devices and methods. But you will after you've been here a while.
Sent from my SM-S903VL using Tapatalk
---------- Post added at 10:39 PM ---------- Previous post was at 10:32 PM ----------
DO NOT USE ODIN ON YOUR DEVICE!!!
Odin is only for Samsung devices.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
Where did this problem start? Did you cause this by modifying, attempting to root or flashing the device with something that caused this?
If so, about your only option is to use your device's flashtool to flash the stock firmware. If your device's stock firmware isn't available then you might be out of luck repairing your device. If this is the case then your only other option might be getting someone that has a device exactly like yours that is rooted and getting them to pull copies of the various .img files needed for your device then using adb shell to dd those .img files on your device. But, to be honest, I don't think this is gonna happen for you. You probably will have to take the device to a repair shop. It will probably be cheaper to just buy another tablet because the cost of repair will probably be more than what you paid for the device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
thankyou so much for the fast responses much appreciated to take your time to explain. Okay i have a question what would be the course of detailed action to preform getting any and all missing .img's it may need. Also i know its a crazy question but would i be able to preform this in store with the displayed tablet that matches mine? How difficult is something like this, and is there any other methods at all I can try to boot past this bootloader. And now that i remember correctly from reading others this happened when I upgraded to 5.1 or 5.0 thank you everybody once again!

samson716 said:
thankyou so much for the fast responses much appreciated to take your time to explain. Okay i have a question what would be the course of detailed action to preform getting any and all missing .img's it may need. Also i know its a crazy question but would i be able to preform this in store with the displayed tablet that matches mine? How difficult is something like this, and is there any other methods at all I can try to boot past this bootloader. And now that i remember correctly from reading others this happened when I upgraded to 5.1 or 5.0 thank you everybody once again!
Click to expand...
Click to collapse
No, you wouldn't be able to get it from a tablet in the store, it's a rather involved process that requires connecting the device to PC, it also requires rooting the device and flashing a custom recovery, and that's all before you actually get to where you can pull the files. It'll take a couple of hours,or more to do it.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
No, you wouldn't be able to get it from a tablet in the store, it's a rather involved process that requires connecting the device to PC, it also requires rooting the device and flashing a custom recovery, and that's all before you actually get to where you can pull the files. It'll take a couple of hours,or more to do it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Is there absolutely anything i can try, just a long shot in the dark?

samson716 said:
Is there absolutely anything i can try, just a long shot in the dark?
Click to expand...
Click to collapse
The only other option is pretty risky. You can try a firmware from another device that has the same CPU and hardware as your device, you'd have to compare specs. It would have to have the same CPU, same screen resolution, same camera(front and rear), same amount of RAM, same amount of internal storage, same accelerometers, etc.. It has to have all the same components that yours has.
Sent from my SM-S903VL using Tapatalk