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] Serieus problem with the Nexus 5

Hello XDA developers!
I hope you can help me with a serieus problem on my Nexus5 Device!
Let's tell you my little adventure with my Nexus5 :
First my Nexus5 Device worked perfectly, but then the radiobaseband and the sensors magically dissapeared!
https://db.tt/cdZiSukZ i've tooked some screenshots of it on dropbox.
Then I Flashed the factory image for my device by following this guide: http://forum.xda-developers.com/showthread.php?t=2513701
And it started to work perfectly, till now........
after about a week i watched a unspecified video on Google Chrome and the screen freezed ( not literally )
So I hold the power button and turn it off, turn it back on and i got a infinity bootloop.
So I flash again the official factory image and it can't flash my system?
its look like this;
trying to flash system.img....
FAILED
the rest of the process flash succesfull until it reach system.img
and a friend of mine therinsem tried to add a custom recovery and it didn't work, so we flashed again the factory image and it still FAILED,
to flash system.img the rest of the process work until it reach system.img.
now it doesn't even boot? it's only going straight into fastboot-mode
and if i press in fastboot-mode recoverymode than it shows nothing? ( i think because we tried to flash a custom recovery )
- iv'e tried on a bunch of diffrent windows laptop's
- i can't access the internal storage of the device
- i can still '' side-load'' I think
so this is my problem with the nexus5, does anyone have a solution?:crying:

Download the factory image again and make sure the md5 checks. Then try again

There's another thread around here somewhere with pretty much the same issue. Sounds like bad memory. From fastboot try:
Code:
fasboot format system
If that succeeds reflash the factory image. If that fails your most likely looking at RMA.

I wouldn't really since google will charge you twice for tampering with the imei
Sent from my Nexus 5

dicecuber said:
I wouldn't really since google will charge you twice for tampering with the imei
Sent from my Nexus 5
Click to expand...
Click to collapse
What? Who's taking about imei?

jd1639 said:
Download the factory image again and make sure the md5 checks. Then try again
Click to expand...
Click to collapse
Thank you for a answer! i will try it and will give a update status soon.

jd1639 said:
What? Who's taking about imei?
Click to expand...
Click to collapse
Judging from pictures, the stock imei is unknown. I'd refrain from rmaing it just yet
Sent from my Nexus 5

dicecuber said:
Judging from pictures, the stock imei is unknown. I'd refrain from rmaing it just yet
Sent from my Nexus 5
Click to expand...
Click to collapse
Sometimes it happens that you lose your imei. Flashing the factor image can bring it back. Nothing nefarious going on

dicecuber said:
Judging from pictures, the stock imei is unknown. I'd refrain from rmaing it just yet
Click to expand...
Click to collapse
Ummmmm? That's why where trying to help the OP recover. lol OP you can also run this and see what the output is:
Code:
fasboot getvar all

^someone suggested Op rma it. I suggested he refrain from doing that
Sent from my Nexus 5

theesotericone said:
Ummmmm? That's why where trying to help the OP recover. lol OP you can also run this and see what the output is:
Code:
fasboot getvar all
Click to expand...
Click to collapse
theesotericone said:
There's another thread around here somewhere with pretty much the same issue. Sounds like bad memory. From fastboot try:
Code:
fasboot format system
If that succeeds reflash the factory image. If that fails your most likely looking at RMA.
Click to expand...
Click to collapse
Thank you very much for the answers! i will setup my laptop again and will use your advice, to recover my device! ( that rhymes! )
Tomorrow i will give a update, i am going to sleep! good night folk!

tomaszcs said:
Thank you very much for the answers! i will setup my laptop again and will use your advice, to recover my device! ( that rhymes! )
Tomorrow i will give a update, i am going to sleep! good night folk!
Click to expand...
Click to collapse
Formatting system did not work.
I helped Tomasz doing this

[Q] Nexus 5 Flash Write Failure

Hey guys,
I have a rooted Nexus 5 and on Saturday it suddenly froze and when I restarted the phone it was stuck on a boot loop. I tried to go into my TWRP recovery and it asked for a password and it says that the internal storage is 0 MB. I have tried to flash stock rom using fastboot manually and it keeps saying (remote: flash write failure). Will someone please help me on this? I can't figure out what to do.
Thank You

sounds like your internel memory went bad. youll need to replace it.

amalthomas994 said:
Hey guys,
I have a rooted Nexus 5 and on Saturday it suddenly froze and when I restarted the phone it was stuck on a boot loop. I tried to go into my TWRP recovery and it asked for a password and it says that the internal storage is 0 MB. I have tried to flash stock rom using fastboot manually and it keeps saying (remote: flash write failure). Will someone please help me on this? I can't figure out what to do.
Thank You
Click to expand...
Click to collapse
Try to flash back only cache.img.
And if that doesn't work probably ur internal memory has some problem.

Nexus 5
varuntis1993 said:
Try to flash back only cache.img.
And if that doesn't work probably ur internal memory has some problem.
Click to expand...
Click to collapse
Hey, when i do that it says (remote: failed to erase partition)
I am dying here i have been trying to fix this since Saturday.
Is there anything else I can try?
Thank You.

Nexus 5
simms22 said:
sounds like your internel memory went bad. youll need to replace it.
Click to expand...
Click to collapse
Hey, where would I be able to buy that?
Thank You

this??
http://forum.xda-developers.com/showthread.php?t=2577447
going to search .. if i'll find something will post here

amalthomas994 said:
Hey, when i do that it says (remote: failed to erase partition)
I am dying here i have been trying to fix this since Saturday.
Is there anything else I can try?
Thank You.
Click to expand...
Click to collapse
Sorry to say it seems like ur internal memory partition has gone corrupt.
U will need to send ur device back to google or to lg service center.

Nexus 5
varuntis1993 said:
Try to flash back only cache.img.
And if that doesn't work probably ur internal memory has some problem.
Click to expand...
Click to collapse
By the way, what is the actual command to flash only cache.img, just making sure I did it correctly.

amalthomas994 said:
By the way, what is the actual command to flash only cache.img, just making sure I did it correctly.
Click to expand...
Click to collapse
Fastboot erase cache
Fastboot flash cache cache.img

Nexus 5
enricocid said:
this??
http://forum.xda-developers.com/showthread.php?t=2577447
going to search .. if i'll find something will post here
Click to expand...
Click to collapse
Hey, thank you, I tried that but this is what i get when i get to the adb part
e2fsck: unable to set superblock flags on /dev/block/platform/msm_sdcc.1/by-name
/userdata

amalthomas994 said:
Hey, where would I be able to buy that?
Thank You
Click to expand...
Click to collapse
no no no.. get your whole phone replaced. you wont have any issue doing it, its a known issue.

simms22 said:
no no no.. get your whole phone replaced. you wont have any issue doing it, its a known issue.
Click to expand...
Click to collapse
But since it is rooted and i can't relock the bootloader, will they replace it?

amalthomas994 said:
But since it is rooted and i can't relock the bootloader, will they replace it?
Click to expand...
Click to collapse
yes. if you bought it through google, they will generally replace rooted phones especially if its a hardware issue(has nothing to do with root). and if its not google, they wont boot it up anyways(i dont think).

amalthomas994 said:
But since it is rooted and i can't relock the bootloader, will they replace it?
Click to expand...
Click to collapse
did you try flashing userdata and cache via fastboot?

Nexus 5
simms22 said:
yes. if you bought it through google, they will generally replace rooted phones especially if its a hardware issue(has nothing to do with root). and if its not google, they wont boot it up anyways(i dont think).
Click to expand...
Click to collapse
Ok, thanks a lot, that atleast gives me some kind of hope lol

Nexus 5
samersh72 said:
did you try flashing userdata and cache via fastboot?
Click to expand...
Click to collapse
Yep, no luck, keep getting write errors
thanks anyways

Nexus 5
Hey everyone,
I am able to get to adb and fastboot, so is there any way I can fix the corrupted files or anything?

amalthomas994 said:
Hey everyone,
I am able to get to adb and fastboot, so is there any way I can fix the corrupted files or anything?
Click to expand...
Click to collapse
no, your storage is physically broken.

Nexus 5
simms22 said:
no, your storage is physically broken.
Click to expand...
Click to collapse
Ok thanks for the reply.
But WOW.. how can something like that even happen..
I know it was not a mistake I did

amalthomas994 said:
Ok thanks for the reply.
But WOW.. how can something like that even happen..
I know it was not a mistake I did
Click to expand...
Click to collapse
its actually a sorta common issue with the nexus 5. at least ive seen more than enough nexus 5 here with that issue. its a hardware issue, nothing you did.

[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

HELP!!!!!! Locked bootloader after flashing a kernel and it doesn't want to boot

Hi guys
As you probably know by reading the title, i completely messed up. I was on the stock google factory image and decided to flash a custom kernel. I enabled usb debuging and oem unlock. after having unlocked the bootloader, I installed the twrp boot img and then flashed the kernel. All was well when i stupidly decided to lock my bootloader. Things crashed and now when i try to boot into my phone, the google logo appears and 1 seconds later crashes keeps doing it until i turn my phone off. My bootloader is locked and i think usb debuging and oem unlock are also disabled.
The same thing happens when i try to go to the recovery, it just crashes.
Any help would be greatly appreciated guys. thank you !!

Colday96 said:
Hi guys
As you probably know by reading the title, i completely messed up. I was on the stock google factory image and decided to flash a custom kernel. I enabled usb debuging and oem unlock. after having unlocked the bootloader, I installed the twrp boot img and then flashed the kernel. All was well when i stupidly decided to lock my bootloader. Things crashed and now when i try to boot into my phone, the google logo appears and 1 seconds later crashes keeps doing it until i turn my phone off. My bootloader is locked and i think usb debuging and oem unlock are also disabled.
The same thing happens when i try to go to the recovery, it just crashes.
Any help would be greatly appreciated guys. thank you !!
Click to expand...
Click to collapse
I feel bad for you. However, you bricked your Pixel.
As I mentioned yesterday, contact Google for an RMA replacement.

phaino00 said:
I feel bad for you. However, you bricked your Pixel.
As I mentioned yesterday, contact Google for an RMA replacement.
Click to expand...
Click to collapse
I bought the phone on ebay. Could i still get a RMA replacement ?

Colday96 said:
I bought the phone on ebay. Could i still get a RMA replacement ?
Click to expand...
Click to collapse
I don't believe so since you're not the original owner. However, it doesn't hurt to try.

If you bl locked the phone w modified software ur boned. I believe that RMA availability is transferrable from owner to owner, however, I also believe that they will refuse to RMA a phone which technically broke because AVB is doing its job properly. You can try but I'd say your chances are slim. Sorry mate. Also future reference: if you don't have any reason in particular to relock your phone, just don't. You'll save yourself the hassle of having to do it again and it wiping the phone everytime any software thing goes wrong or anytime u want to upgrade custom ROM or kernel or anything of the sort. This goes for any phone not just those with android verified boot.

phaino00 said:
I don't believe so since you're not the original owner. However, it doesn't hurt to try.
Click to expand...
Click to collapse
My seller is about to contact google to get a replacement. do you think google will know if i did something with it i shouldn't have ? Since i can't boot in the recovery, won't they be able to do it either ?

Colday96 said:
My seller is about to contact google to get a replacement. do you think google will know if i did something with it i shouldn't have ? Since i can't boot in the recovery, won't they be able to do it either ?
Click to expand...
Click to collapse
Assume they will.

Colday96 said:
My seller is about to contact google to get a replacement. do you think google will know if i did something with it i shouldn't have ? Since i can't boot in the recovery, won't they be able to do it either ?
Click to expand...
Click to collapse
Yes they will know but they have proprietary software to forcefully unlock/reformat the phone properly if they so choose to actually accept the phone

This just happened to me today, i was trying to reset it because I'm selling this phone and boom.. Brick... Just lost $400 ?

Nandolkz said:
This just happened to me today, i was trying to reset it because I'm selling this phone and boom.. Brick... Just lost $400 ?
Click to expand...
Click to collapse
You can still sell it for around 150 for parts on ebay

Nandolkz said:
This just happened to me today, i was trying to reset it because I'm selling this phone and boom.. Brick... Just lost $400
Click to expand...
Click to collapse
Can't you restore using the stock zips from google?

Poebat said:
Can't you restore using the stock zips from google?
Click to expand...
Click to collapse
I already tried, using both 8.1 and the first Nougat... It says oem can't unlock. I even download the skipsoft app to tryout but fail

Nandolkz said:
I already tried, using both 8.1 and the first Nougat... It says oem can't unlock. I even download the skipsoft app to tryout but fail
Click to expand...
Click to collapse
If you are flashing the latest version of Oreo you don't need to oem unlock. What version of Android were you running before you bricked it?

Poebat said:
If you are flashing the latest version of Oreo you don't need to oem unlock. What version of Android were you running before you bricked it?
Click to expand...
Click to collapse
8.0, well I already tried the dic 8.1 and it didn't work... Let me try the nov build.. or im going to try both let me see what happen.. I'll share the cmd log...

Nandolkz said:
8.0, well I already tried the dic 8.1 and it didn't work... Let me try the nov build.. or im going to try both let me see what happen.. I'll share the cmd log...
Click to expand...
Click to collapse
Okay. If that doesn't work try the 7.1.2 build with the flash-all.bat

Poebat said:
Okay. If that doesn't work try the 7.1.2 build with the flash-all.bat
Click to expand...
Click to collapse
It won't work because his bootloader is locked. I also tried the OTA file and that didn't work either. Do to have usb debugging on ?

Colday96 said:
It won't work because his bootloader is locked. I also tried the OTA file and that didn't work either. Do to have usb debugging on ?
Click to expand...
Click to collapse
He doesn't have a working OS so I doubt it

Here is what is happening to me... Any ideason how to fix it? ?

Nandolkz said:
Here is what is happening to me... Any ideason how to fix it? ?
Click to expand...
Click to collapse
Try flashing the stock rom with fastboot

Poebat said:
Try flashing the stock rom with fastboot
Click to expand...
Click to collapse
Here