Database Info

Added line to build.prop....now bricked?

So I wanted to wake up my nexus 5 with the volume buttons. Looking online I found that you could add code to your build.prop.. which I did.. then rebooted...
Now my phone does 'nothing'... When I press the power button it vibrates 2 times and nothing happens...
Help!.. Have no idea what i can do to get things running again
P.S. I've got Slimkat ROM running

S.Phrenic said:
So I wanted to wake up my nexus 5 with the volume buttons. Looking online I found that you could add code to your build.prop.. which I did.. then rebooted...
Now my phone does 'nothing'... When I press the power button it vibrates 2 times and nothing happens...
Help!.. Have no idea what i can do to get things running again
P.S. I've got Slimkat ROM running
Click to expand...
Click to collapse
Can you get into bootloader? Recovery?

Lethargy said:
Can you get into bootloader? Recovery?
Click to expand...
Click to collapse
Currently, nope... I'm trying.. I see that sometimes the screen is on... sometimes I see the Google Logo... but Can't fully figure out when that happens
[EDIT]YES!!!!!!!!! Got in.!!!!!!... *pfieuw*.. now what do i do?

Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX

Croc97 said:
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Click to expand...
Click to collapse
Please don't use toolkits.

Croc97 said:
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Click to expand...
Click to collapse
Don't exaclty know what you mean with that..
I've downloaded Kwongger's Nexus 5 All-In-One Toolkit , I hope that's what you meant. And then it says it's missing the hammerhead.image.zip... which I assume is the stockROM?.. If so, shouldn't I Reflash to Slimkat?
Sorry for being such a Noob. I've had Samsung for years and just switched to Nexus (bought it last week). Still need to learn my way around things

S.Phrenic said:
Don't exaclty know what you mean with that..
I've downloaded Kwongger's Nexus 5 All-In-One Toolkit , I hope that's what you meant. And then it says it's missing the hammerhead.image.zip... which I assume is the stockROM?.. If so, shouldn't I Reflash to Slimkat?
Sorry for being such a Noob. I've had Samsung for years and just switched to Nexus (bought it last week). Still need to learn my way around things
Click to expand...
Click to collapse
Read my reply to your PM and the 2nd link in my signature, then refer to the first link if you need

Lethargy said:
Read my reply to your PM and the 2nd link in my signature, then refer to the first link if you need
Click to expand...
Click to collapse
Let me start with, Thank you so much for your time
However, It seems like I'm unable to install the right drivers on my PC for my phone and adb doesn't detect my device (which is strange as CF-auto-root did see the device and worked fine)
I walked through multiple tutorials about installing drivers. Actually have windows detecting my phone fine (I see it in device manager) and I've reinstalled google USB drivers multiple times now, rebooting my PC and deleting drivers and reinstalling them
I've justed factory reset my phone, but that just got me to a Google logo stuck (which I read about in your link in your signature)..
Because adb doesn't detect my device I'm unable to pull build.prop... which means I feel stuck again.
Would you have a direction for me to go towards to continue my journey through Nexus5-Land?

S.Phrenic said:
Let me start with, Thank you so much for your time
However, It seems like I'm unable to install the right drivers on my PC for my phone and adb doesn't detect my device (which is strange as CF-auto-root did see the device and worked fine)
I walked through multiple tutorials about installing drivers. Actually have windows detecting my phone fine (I see it in device manager) and I've reinstalled google USB drivers multiple times now, rebooting my PC and deleting drivers and reinstalling them
I've justed factory reset my phone, but that just got me to a Google logo stuck (which I read about in your link in your signature)..
Because adb doesn't detect my device I'm unable to pull build.prop... which means I feel stuck again.
Would you have a direction for me to go towards to continue my journey through Nexus5-Land?
Click to expand...
Click to collapse
If you're using Windows 8, 8.1 or 8.1U1 you'll need to disable driver signature enforcement.
Try flashing the factory images in fastboot?

Could somebody not just make a flashable zip with the correct build.prop?
Failing that, just reflash the ROM.

Lethargy said:
If you're using Windows 8, 8.1 or 8.1U1 you'll need to disable driver signature enforcement.
Try flashing the factory images in fastboot?
Click to expand...
Click to collapse
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.

S.Phrenic said:
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
Click to expand...
Click to collapse
Glad you got it worked out

S.Phrenic said:
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
Click to expand...
Click to collapse
Glad you got it sorted but, unless you couldn't boot into recovery, you didn't need to go back to stock.
Flashing the correct build.prop or ROM you were using should have sorted it out, without losing any data (you would have lost any system mods if you flashed the ROM again, though).
I'm only mentioning this in case somebody else searches and finds this thread for the same problem.
I've changed the build.prop loads of times on many devices and only once it went into a bootloop. Flashing a build.prop zip sorted it.

[Need Help Fast] Boot Loop on Vega Iron NOT NORMAL

Hello I'm a user of a Sky Vega Iron (IM-A870)
And I need desperate help.
It's not an ordinary boot loop I wish it was, here's the story.
I rooted my phone just to let you know.
So I installed the wrong version of cwd recovery on my phone and so when I go into recovery mode the screen will turn like this.
imgurDOTcom/iOFieHG (sorry I can't you links yet cause I'm new)
But it wasn't a big deal I just didn't use it.
Now is the deal I decided to update my phone to stock kitkat that the vega devs supported themselves with vega station(the stock updating app)
And when it started installing it suddenly went into cwm.
I wasn't that worried at the moment just tried pulling the battery out and rebooting but...it started a boot loop.
I can't navigate cwm because of the way it is and I'm stuck. Is there another way to factory reset? or to get out of the loop?
Maybe a way to get rid of cwm and get back to stock recovery mode? Please help I need help until tomorrow! (personal reasons)
I searched online hours for solutions yet I can't find one.
Please help. I'm begging anyone out there.
Thank You

Cottyn said:
Hello I'm a user of a Sky Vega Iron (IM-A870)
And I need desperate help.
It's not an ordinary boot loop I wish it was, here's the story.
I rooted my phone just to let you know.
So I installed the wrong version of cwd recovery on my phone and so when I go into recovery mode the screen will turn like this.
imgurDOTcom/iOFieHG (sorry I can't you links yet cause I'm new)
But it wasn't a big deal I just didn't use it.
Now is the deal I decided to update my phone to stock kitkat that the vega devs supported themselves with vega station(the stock updating app)
And when it started installing it suddenly went into cwm.
I wasn't that worried at the moment just tried pulling the battery out and rebooting but...it started a boot loop.
I can't navigate cwm because of the way it is and I'm stuck. Is there another way to factory reset? or to get out of the loop?
Maybe a way to get rid of cwm and get back to stock recovery mode? Please help I need help until tomorrow! (personal reasons)
I searched online hours for solutions yet I can't find one.
Please help. I'm begging anyone out there.
Thank You
Click to expand...
Click to collapse
this seems like a bit of a pia, but it looks like the only way i can find. click the link under the video for detailed text instructions.

Thanks but failed
Thank you so much but it didn't work.
Thinking of going to a service center and getting it factory reset.
Think it'll work?

Cottyn said:
Thank you so much but it didn't work.
Thinking of going to a service center and getting it factory reset.
Think it'll work?
Click to expand...
Click to collapse
not sure, cant hurt to try.

bweN diorD said:
not sure, cant hurt to try.
Click to expand...
Click to collapse
Is there a way to factory reset by myself?
I have to fix it today but the service centers are closed for sundays.(once again personal issues)
Thank you again

Cottyn said:
Is there a way to factory reset by myself?
I have to fix it today but the service centers are closed for sundays.(once again personal issues)
Thank you again
Click to expand...
Click to collapse
you would need to get to one of 2 places, i thought you couldn't get to either, settings (from booted up) or recovery.
but factory resetting would only remove any data, it will not restore any files or fix your busted cwm.

bweN diorD said:
you would need to get to one of 2 places, i thought you couldn't get to either, settings (from booted up) or recovery.
but factory resetting would only remove any data, it will not restore any files or fix your busted cwm.
Click to expand...
Click to collapse
Oh so then factory resetting won't get me out of my boot loop?

Cottyn said:
Oh so then factory resetting won't get me out of my boot loop?
Click to expand...
Click to collapse
i cant say that for sure, all im saying is, factory reset does nothing more than wipe data.
if there is an issue in there causing your problem, then yes it will fix it. if your problem is caused by a software issue, then no it will not.

bweN diorD said:
i cant say that for sure, all im saying is, factory reset does nothing more than wipe data.
if there is an issue in there causing your problem, then yes it will fix it. if your problem is caused by a software issue, then no it will not.
Click to expand...
Click to collapse
Okay thank you for everything really
I've given up I think there's nothing I can do.
Next time I get a phone I'm not screwing with it

Cottyn said:
Okay thank you for everything really
I've given up I think there's nothing I can do.
Next time I get a phone I'm not screwing with it
Click to expand...
Click to collapse
lol, ok, no problem.

I feel the pain
Cottyn said:
Hello I'm a user of a Sky Vega Iron (IM-A870)
And I need desperate help.
It's not an ordinary boot loop I wish it was, here's the story.
I rooted my phone just to let you know.
So I installed the wrong version of cwd recovery on my phone and so when I go into recovery mode the screen will turn like this.
imgurDOTcom/iOFieHG (sorry I can't you links yet cause I'm new)
But it wasn't a big deal I just didn't use it.
Now is the deal I decided to update my phone to stock kitkat that the vega devs supported themselves with vega station(the stock updating app)
And when it started installing it suddenly went into cwm.
I wasn't that worried at the moment just tried pulling the battery out and rebooting but...it started a boot loop.
I can't navigate cwm because of the way it is and I'm stuck. Is there another way to factory reset? or to get out of the loop?
Maybe a way to get rid of cwm and get back to stock recovery mode? Please help I need help until tomorrow! (personal reasons)
I searched online hours for solutions yet I can't find one.
Please help. I'm begging anyone out there.
Thank You
Click to expand...
Click to collapse
I am going through a similar situation here. I was using Choi Mobil Recovery and was trying to flash a custom ROM. It's now in BootLoop and there is nothing I can do!

fakesoul said:
I am going through a similar situation here. I was using Choi Mobil Recovery and was trying to flash a custom ROM. It's now in BootLoop and there is nothing I can do!
Click to expand...
Click to collapse
what variant of vega iron you were using and what rom youre trying to flash?

[SOLVED] Soft Brick on rooted N5 running 4.4.2

All,
I got myself into a bit of pickle and could use some advice.
First, device information:
Nexus 5 Hammerhead D821(E)
Hw version rev_11
Bootloader version HHZ11k
Secure boot enabled
lock state unlocked
I think it's 4.4.2 or 4.4.3. I haven't installed KitKat.
Also running some xposed modules and Teamwin recovery but haven't flashed a rom or kernel
The issue
About an hour ago I got into the com.android.systemui. The screen keeps flashing and I'm lucky if I can power off the device. No chance of starting an app or getting into settings. When the device is powered up I can not access file folders through Explorer, in bootloader the device is not even recognized.
I figure I need to do a factory reset but seeing that I can't reach settings I don't know how to do this exactly (I assume it's OK to do with a rooted device that's still running the custom ROM?) Should I do it through TWRP? And if so, how do I proceed? I've read a few threads that deal with similar issues but I haven't found a manual that I feel fits completely which make some uncomfortable to try.
Thanks very much in advance,
T
Also, I just found this one: http://forum.xda-developers.com/goo...l-06-03-14-one-click-factory-restore-t2513937
Would that be the right way to go?

First of all there isn't such thing as a "soft brick" It's either bricked or it's not.
You said you haven't "installed KitKat", well 4.4.x is KK. You sure you know what you're doing?
I suggest you see the first link of my signature and read some threads before you proceed with doing anything further to your device. You should be able to reflash factory images.

Lethargy said:
First of all there isn't such thing as a "soft brick" It's either bricked or it's not.
You said you haven't "installed KitKat", well 4.4.x is KK. You sure you know what you're doing?
I suggest you see the first link of my signature and read some threads before you proceed with doing anything further to your device. You should be able to reflash factory images.
Click to expand...
Click to collapse
Thanks for the swift reply Lethargy,
I referred to softbrick as in I can still boot but it gets into a loop I can't get out of. Apologies for the confusion re KitKat, I meant I hadn't installed 4.4.4.
I actually just ran the One click recover in the thread I mentioned and it worked like a charm, can use the phone again so marking this as solved!

Taeglian said:
Thanks for the swift reply Lethargy,
I referred to softbrick as in I can still boot but it gets into a loop I can't get out of. Apologies for the confusion re KitKat, I meant I hadn't installed 4.4.4.
Click to expand...
Click to collapse
That would be a "bootloop" or non-boot, not a "soft-brick".
Taeglian said:
I actually just ran the One click recover in the thread I mentioned and it worked like a charm, can use the phone again so marking this as solved!
Click to expand...
Click to collapse
Cool. But I do still suggest you have a look at various threads in the first link of my signature to learn a little more.

[Q] Stuck in bootloop.

Hi everyone.
I have the following problem with a Nexus 5: During an update, the system crashed. The phone is now stuck in an endless bootloop, trying to install the update. When left long enough, the update screens eventually come up, but you are immediately blasted with a ton of errors and no matter what you do, you are unable to complete the update. This, however, is not the problem.
I have tried various utilities in order to flash the phone back to factory settings. I have made use of Unified Android ToolKit, as well as Nexus Root Toolkit, but a problem with the phone itself is preventing me from flashing it and the problem is as follows: I can access the phone via USB, as well as the bootloader, but when I unlock the bootloader to start the flashing, it immediately locks itself again and I'm unable to start the flash process.
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?

Mystical_Titan said:
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Click to expand...
Click to collapse
If the lock state reverts on a reboot, 99 times out of 100, it means the internal memory has an issue. RMA.

rootSU said:
If the lock state reverts on a reboot, 99 times out of 100, it means the internal memory has an issue. RMA.
Click to expand...
Click to collapse
Thanks for the fast response. :good:

Mystical_Titan said:
Thanks for the fast response. :good:
Click to expand...
Click to collapse
No probs. Sounds like the update got stuck at the bootloader flash and corrupted. It's probably not a fatal NAND issue, rather corrupt partition or two but it usually means sending it in.
You can try the LG flashtool as a last resort before doing so though, as you never know...
You can find a link to it in the sticky thread in my signature. Best to stay away from actual "toolkits" though and either use fastboot manually or LG flash tool, although fastboot probably cant help you here - just saying for future ref...

Mystical_Titan said:
Hi everyone.
I have the following problem with a Nexus 5: During an update, the system crashed. The phone is now stuck in an endless bootloop, trying to install the update. When left long enough, the update screens eventually come up, but you are immediately blasted with a ton of errors and no matter what you do, you are unable to complete the update. This, however, is not the problem.
I have tried various utilities in order to flash the phone back to factory settings. I have made use of Unified Android ToolKit, as well as Nexus Root Toolkit, but a problem with the phone itself is preventing me from flashing it and the problem is as follows: I can access the phone via USB, as well as the bootloader, but when I unlock the bootloader to start the flashing, it immediately locks itself again and I'm unable to start the flash process.
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Click to expand...
Click to collapse
happened to me while installing the new SNAPSHOT version of Cyanogenmod, I wiped everything and reflashed it and it works

BruKnowsBest said:
happened to me while installing the new SNAPSHOT version of Cyanogenmod, I wiped everything and reflashed it and it works
Click to expand...
Click to collapse
Can anyone suggest some steps for me to try before I RMA the phone? Although, being unable to unlock the bootloader probably limits my options.

Mystical_Titan said:
Can anyone suggest some steps for me to try before I RMA the phone? Although, being unable to unlock the bootloader probably limits my options.
Click to expand...
Click to collapse
I was stuck in the boot animation and when it opened there was a lot of system errors and it would reboot by itself over and over again.
what fixed it was to do a wipe cache and dalvik and reinstall it

BruKnowsBest said:
I was stuck in the boot animation and when it opened there was a lot of system errors and it would reboot by itself over and over again.
what fixed it was to do a wipe cache and dalvik and reinstall it
Click to expand...
Click to collapse
I tried the 'wipe cache' as well, but it returns a bunch of errors as well. I'm starting to think the NAND is screwed. What is dalvik?

Mystical_Titan said:
I tried the 'wipe cache' as well, but it returns a bunch of errors as well. I'm starting to think the NAND is screwed. What is dalvik?
Click to expand...
Click to collapse
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk

rootSU said:
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I completely forgot that you mentioned the LG Flashtool, I feel like such an idiot. I'll try that tomorrow as a last resort.

No worries
Sent from my Nexus 5 using Tapatalk

rootSU said:
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i thought about LG FLASHTOOL but decided to try reinstaling the rom cuz i had no other option since i forgot to leave a backup rom on the device. So I did it as if I was installing a brand new rom Wiped dalvik, cache and system then reflashed the rom and then the gapps. Even tho it was the same ROM file I had a different outcome. It's working fine now but I did go back to the nightlies after it started working again just to be safe.
Now... people may have a different outcome when trying to solve this issue but this actually worked for me after having a minor heart-attack thinking I was gonna lose all my stuff

BruKnowsBest said:
i thought about LG FLASHTOOL but decided to try reinstaling the rom cuz i had no other option since i forgot to leave a backup rom on the device. So I did it as if I was installing a brand new rom Wiped dalvik, cache and system then reflashed the rom and then the gapps. Even tho it was the same ROM file I had a different outcome. It's working fine now but I did go back to the nightlies after it started working again just to be safe.
Now... people may have a different outcome when trying to solve this issue but this actually worked for me after having a minor heart-attack thinking I was gonna lose all my stuff
Click to expand...
Click to collapse
Yes, but your issue is different to the OP's. His bootloader lock state reverts whenever he changes it. This is a pretty much "fatal" issue. What you did cannot help him unfortunately.

rootSU said:
Yes, but your issue is different to the OP's. His bootloader lock state reverts whenever he changes it. This is a pretty much "fatal" issue. What you did cannot help him unfortunately.
Click to expand...
Click to collapse
oh ok, I misunderstood

rootSU said:
No worries
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It speaks about a KDZ file. What is it and where would I find it?

Mystical_Titan said:
It speaks about a KDZ file. What is it and where would I find it?
Click to expand...
Click to collapse
Not sure, never used it. Are you following the Nexus 5 LG Flash tool guide? If not, have a look. You can get to it via my signature

rootSU said:
Not sure, never used it. Are you following the Nexus 5 LG Flash tool guide? If not, have a look. You can get to it via my signature
Click to expand...
Click to collapse
Well, that's that. This phone is done.

Yup. RMA
Sent from my Nexus 5 using Tapatalk

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