I'm having a problem with my Nexus 4 that when I connect it to my laptop, I get a message saying "one of the devices attached to this computer has malfunctioned" and shows as "Unknown Device" in device manager. It doesn't show up in my computer. I've made sure MTP is enabled on the phone. I've tried different cables, tried uninstalling drivers and installing the latest official usb drivers. I've tried another computer and same problem. I found this thread saying that it could be a hardware problem. Phone is still under warranty but I have bootloader unlocked and a custom recovery with a stock rom but with no way of returning to complete stock.
Any ideas? Any help is much appreciated.
Are you by any chance, using Windows XP? If you do,go check How to connect to Windows XP thread.
No my laptop is running Windows 7 and also tried it on a Windows 8 Laptop.
cyanisblue said:
No my laptop is running Windows 7 and also tried it on a Windows 8 Laptop.
Click to expand...
Click to collapse
Yeah, most probably hardware failure on the phone. You can return to complete stock by following this guide, unroot, then locking the bootloader I think. There should be guides everywhere in the forum. After that you can claim warranty, some places doesn't even check the state of the phone but just to be safe. Good luck dude.
uchihakurtz said:
Yeah, most probably hardware failure on the phone. You can return to complete stock by following this guide, unroot, then locking the bootloader I think. There should be guides everywhere in the forum. After that you can claim warranty, some places doesn't even check the state of the phone but just to be safe. Good luck dude.
Click to expand...
Click to collapse
How can flash factory image and lock bootloader if I can't get adb/fastboot to work? It won't recognize the device at all.
cyanisblue said:
How can flash factory image and lock bootloader if I can't get adb/fastboot to work? It won't recognize the device at all.
Click to expand...
Click to collapse
Oh right, dang. I think the work around is to find a flashable zip of stock ROM and maybe an app that can relock bootloader directly. I'll try finding some when I'm surfing.
Sent from my blazing fast Nexus 4
uchihakurtz said:
Oh right, dang. I think the work around is to find a flashable zip of stock ROM and maybe an app that can relock bootloader directly. I'll try finding some when I'm surfing.
Sent from my blazing fast Nexus 4
Click to expand...
Click to collapse
I found this app which can lock the bootloader and I've found a flashable stock 4.4 recovery.
Which order would I do all this in.
Would I flash stock 4.4 recovery zip then run lock bootloader app then full unroot in supersu?
Edit: Bootloader is locked and stock recovery installed now, all that's remaining is supersu which I can just use the unroot function.
Did you find the stock ROM though? It should be flashing stock ROM (automatically unroots), recovery, then lock the bootloader
Sent from my blazing fast Nexus 4
uchihakurtz said:
Did you find the stock ROM though? It should be flashing stock ROM (automatically unroots), recovery, then lock the bootloader
Sent from my blazing fast Nexus 4
Click to expand...
Click to collapse
I already had a rooted stock rom installed, and the thing is you need root for the app to lock the bootloader.
Sent from my Nexus 7 using Tapatalk
cyanisblue said:
I already had a rooted stock rom installed, and the thing is you need root for the app to lock the bootloader.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I think it's safe to lock the bootloader then unroot, since unlocking bootloader is only used to install custom recoveries not rooting.
uchihakurtz said:
I think it's safe to lock the bootloader then unroot, since unlocking bootloader is only used to install custom recoveries not rooting.
Click to expand...
Click to collapse
I ended up reflashing stock leaving the bootloader locked and then flashing stock recovery after. I'm going to take it back later this week.
Thanks for your help.
Sent from my Nexus 7 using Tapatalk
cyanisblue said:
I ended up reflashing stock leaving the bootloader locked and then flashing stock recovery after. I'm going to take it back later this week.
Thanks for your help.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
You're welcome bro, good luck and I hope your mako gets well soon
Related
Well, after trying to charge my Nexus in the car, it appears the USB has gone kaput and only charges the device now (although it doesn't actually say it's charging, the percentage just increases). Anyway, as it would appear a return is in order, I'd like to remove the unlocked sign on my bootloader to be able to send it back, but without USB, the conventional fastboot/adb method is out the window. Anybody got any suggestions? Thanks.
Bump, per chance?
Use wugfresh toolkit and Hitt the oem lock option
Sent from my Nexus 7 using xda app-developers app
The OP clearly said they are looking for a method that doesn't require USB. So your method suggesting he use wugs toolkit isn't the answer he's looking for. And honestly I don't think there is a way to do it without USB capabilities.
Sent from my Nexus 7 using Tapatalk 2
I don't think you can.
I'm not exactly a pro at this, but as far as I know you need fast boot mode to lock/unlock the bootloader.
I installed twrp last night (got bored with cwm) and noticed it has a command line section. I don't know if you could use this to lock the bootloader. If you look up one of the manual guides to locking/unlocking maybe try whatever it says to type in a terminal there?
The only problem is then you couldn't put back the stock recovery.
Sent from my Nexus 7 using xda app-developers app
You can use this to install the stock ROM and kernel, there is also an option to unroot it. http://forum.xda-developers.com/showthread.php?t=1929270 (install zip in custom recovery)
I don't know how to OEM lock your tablet without a pc..
Hope this helps
Sent from my Nexus 7 using xda app-developers app
I would be really surprised if it is not simply a bad micro USB cable. Try another one, if you have it laying around, or pick one up for cheap. My unofficial cable would charge, but not write for some reason.
i had the same problem after using a car charger.After some days that i charged with original charger only, charging icon started working and also fastboot.But usb otg functions were still dead either in twrp recovery or inside the rom.
After i flashed ota update (i was in stock 4.1.2) for 4.2 it magically started fully working.First i thought that it was 4.2 that made it work,but i went back in 4.1.2 (nandroid restore) and it continue to work ok.Of course i dont use anymore 3rd party chargers.I see now that my bootloader is 4.13 but it work ok with 4.1.2 too,so i will not change it to 3.41
I've tried 4 or 5 different cables and no luck unfortunately. Going from my beloved PA 2.54 to stock 4.2 temporarily to see if it fixes it, fingers crossed!
Update: Unfortunately I've not been so lucky problem persists...
Adb over WiFi?
Sent from my SPH-D710 using xda app-developers app
And now I'm stuck on 4.2 with root not working, my recovery corrupt, and USB still not working :crying:
Looks like I'll be sending it back and hoping they ignore the little opened padlock on my splash screen
DaMan90 said:
Adb over WiFi?
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Adb won't do it, it has to be fast boot, and it has to be usb.
Cadabena said:
And now I'm stuck on 4.2 with root not working, my recovery corrupt, and USB still not working :crying:
Looks like I'll be sending it back and hoping they ignore the little opened padlock on my splash screen
Click to expand...
Click to collapse
Hi ! I'm in the same situation and am thinking of returning it. How did it go ? Did they accept it ?
chuck_0 said:
Hi ! I'm in the same situation and am thinking of returning it. How did it go ? Did they accept it ?
Click to expand...
Click to collapse
Accepted it no problem
However, they'd be well within their rights not to so I'm not guaranteeing. Best of luck!
Hello im on stock 4.2.2 and im rooted with an unlocked bootloader. Will i have to relock it once the new 5.0 klp update comes out to get it or will it still work fine? I know theres still a while until the update but id like to be prepared
Depends, if you want the KLP version from google, you'll need to go back to stock and lock the bootloader.
However, there's a 99.99999999% chance someone here at XDA will have a KLP rom before google officially releases one for our N10s.
Ok thanks but can i keep it rooted or do i need to unroot aswell?
Sent from my Xperia Play (r800x)
OK so I heard some rumors about a jellybean update to 4.3 soon. I really don't want to lose all my data by flashing a stock image once it comes out. Is there a way to relock the boot loader without losing data? And if not is there a way to backup all my data and restore it afterwards. I tried using wugs toolkit to do this but the problem is it only backs up the main user and not the secondary ones. Any suggestions would be appreciated thank you.
Sent from my Xperia Play (r800x)
I believe unlocking/locking the boot loader will in fact wipe all data. So you'd have to manually handle the backup/restore if you don't want to lose the data.
I'd try something like TB to backup and restore. I usually start from scratch again as I've read restoring app data can cause issue under certain circumstances. YMMV...
cowabunga said:
I believe unlocking/locking the boot loader will in fact wipe all data. So you'd have to manually handle the backup/restore if you don't want to lose the data.
I'd try something like TB to backup and restore. I usually start from scratch again as I've read restoring app data can cause issue under certain circumstances. YMMV...
Click to expand...
Click to collapse
OK I guess I'll just do that but doesn't locking the boot loader wipe "sd card" data as well? So would I have to save my tb files to a CPU?
Sent from my Nexus 10 using xda app-developers appu
abdel12345 said:
OK I guess I'll just do that but doesn't locking the boot loader wipe "sd card" data as well? So would I have to save my tb files to a CPU?
Sent from my Nexus 10 using xda app-developers appu
Click to expand...
Click to collapse
If you are rooted, use nexus boot unlocker from the play store to lock the bootloader without losing data...
the_boo said:
If you are rooted, use nexus boot unlocker from the play store to lock the bootloader without losing data...
Click to expand...
Click to collapse
Awesome thanks man. This is like the fifth time you've helped me out to solve my problem exactly. You are awesome. Thanks again I really didn't want to delete all my name data and now I don't have to
Sent from my Nexus 10 using xda app-developers app
abdel12345 said:
Awesome thanks man. This is like the fifth time you've helped me out to solve my problem exactly. You are awesome. Thanks again I really didn't want to delete all my name data and now I don't have to
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Haha.. No problem.. Although, if you are on a custom ROM, I'm pretty sure you will have to flash a stock rom before you do the OTA... If you are on a custom ROM it will be better to wait for the devs to update it themselves...
the_boo said:
Haha.. No problem.. Although, if you are on a custom ROM, I'm pretty sure you will have to flash a stock rom before you do the OTA... If you are on a custom ROM it will be better to wait for the devs to update it themselves...
Click to expand...
Click to collapse
I'm on stock so I won't have to worry about that. Thanks
Sent from my Nexus 10 using xda app-developers app
What if you have unlocked boot loader, but not root - that will update won't it? Pretty sure thats how I did 4.2.1 to 4.2.2 if I am remembering correct....
bigmatty said:
What if you have unlocked boot loader, but not root - that will update won't it? Pretty sure thats how I did 4.2.1 to 4.2.2 if I am remembering correct....
Click to expand...
Click to collapse
I'm not sure so far all I've heard is that you have to lock the bootloader first... And I'd rather not take the risk. Anyway that app mentioned earlier locks and unlocks your boot loader with a click so its great
Sent from my Nexus 10 using xda app-developers app
hmm, from reading that apps description it gives me the impression a bootloader could be locked again w/out wiping - its just then when you would want to re-unlock that it would re-wipe.
right now Im unlocked but stock everything else. I think I will see what happens just trying the upgrade w/out relocking (again because Im pretty sure that's the same as the .2 I just did.)
if anyone can confirm any of this it would be welcomed
bigmatty said:
hmm, from reading that apps description it gives me the impression a bootloader could be locked again w/out wiping - its just then when you would want to re-unlock that it would re-wipe.
right now Im unlocked but stock everything else. I think I will see what happens just trying the upgrade w/out relocking (again because Im pretty sure that's the same as the .2 I just did.)
if anyone can confirm any of this it would be welcomed
Click to expand...
Click to collapse
The app says it does the locking and unlocking without wiping anything. I've already relocked mine and ill see if it worked once I turn on my tablet. (Ill check if the unlocked sign is still there)
Sent from my Xperia Play (r800x)
OK I treid the app and can confirm it works great
Sent from my Nexus 10 using xda app-developers app
abdel12345 said:
Hello im on stock 4.2.2 and im rooted with an unlocked bootloader. Will i have to relock it once the new 5.0 klp update comes out to get it or will it still work fine? I know theres still a while until the update but id like to be prepared
Click to expand...
Click to collapse
To get any Google OTA you do not need to re-lock the bootloader. You might need to flash the stock recovery prior to install the OTA.
At least this is what I did. Of course, to be safe I installed "Bootunlocker", "Voodo OTA Rootkeeper", and "SuperSU".
SuperSU gives permission to keep your phone root when you flash stock recovery.
After you re-install a custom recovery you need, prior to reboot, to wipe "Dalvik-Cache".
The long wait can start
@gunner1937 OK thanks. But where can I get stock recovery? Also I already have super su installed so do I need to do anything before flashing stock recovery or I just need to have supersu installed and then flash to keep root? Will flashing stock recovery wipe data? And are there any other steps I need to take. Please explain thanks
Sent from my Nexus 10 using xda app-developers app
abdel12345 said:
@gunner1937 OK thanks. But where can I get stock recovery? Also I already have super su installed so do I need to do anything before flashing stock recovery or I just need to have supersu installed and then flash to keep root? Will flashing stock recovery wipe data? And are there any other steps I need to take. Please explain thanks
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
To get stock recovery go to https://developers.google.com/android/nexus/images.
Download the factory image for Nexus 10 "mantaray".
Extract the files using, preferably,7-zip.
In the extract files select the file with extension.tar. Unzip with 7-zip.
Open file " mantaray-jdq39". Click on file "image-mantaray-jdq39.zip: this is where you will find all the img files including "recovery.img"
gunner1937 said:
To get stock recovery go to https://developers.google.com/android/nexus/images.
Download the factory image for Nexus 10 "mantaray".
Extract the files using, preferably,7-zip.
In the extract files select the file with extension.tar. Unzip with 7-zip.
Open file " mantaray-jdq39". Click on file "image-mantaray-jdq39.zip: this is where you will find all the img files including "recovery.img"
Click to expand...
Click to collapse
Ok thanks alot man Ill do this
Sent from my Xperia Play (r800x)
I have a N4 which was unlocked and rooted after updating to 4.3. I figured, I'd give Franco Kernel a shot so I proceeded to download the Franco Updater from Google Play.
Selected automatic flash and reboot and now it's stuck in a perpetual boot state. I attempted to proceed with a hard reset through the recovery mode; using ClockworkMod Recovery. I wiped my data, cache and dalvik cache and then went on to reboot system.
Up till' now, my N4 is on the boot Google screen. I tried doing the above steps multiple times but the results remain the same.
I'd appreciate if any help is directed on how I would be able to reset my device to factory settings. I don't mind going through the unlocking and rooting process again; I just need it to get through the boot screen
Go to the bootloader and run this tool: https://developers.google.com/android/nexus/images#occamjwr66v
It works every time.
Something went wrong with the flash for sure, I can tell in many ways so wiping will not help anyway unless you flash an other kernel.
This will wipe EVERYTHING so I don't know if it is worth flashing or flash an other kernel, you choose.
Sent from my Nexus 4 using Tapatalk 4 Beta
andyabc said:
Go to the bootloader and run this tool: https://developers.google.com/android/nexus/images#occamjwr66v
It works every time.
Something went wrong with the flash for sure, I can tell in many ways so wiping will not help anyway unless you flash an other kernel.
This will wipe EVERYTHING so I don't know if it is worth flashing or flash an other kernel, you choose.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Alright so I've downloaded the necessary file from your link, how do I go about running it? I apologize if this is a silly question to surface.
omgzam said:
Alright so I've downloaded the necessary file from your link, how do I go about running it? I apologize if this is a silly question to surface.
Click to expand...
Click to collapse
Make sure it is Mako/Occam.
What ever android version you chose extract the file twice until you get to the contents and run flash_all.bat, if the script says that you are missing the Fastboot file you have to get it from the SDK.
Make sure your device is on the bootloader which is unlocked.
Sent from my Nexus 4 using Tapatalk 4 Beta
andyabc said:
Make sure it is Mako/Occam.
What ever android version you chose extract the file twice until you get to the contents and run flash_all.bat, if the script says that you are missing the Fastboot file you have to get it from the SDK.
Make sure your device is on the bootloader which is unlocked.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'm guessing this doesn't work on Mac? Because I'm currently on my Mac machine at work. If it's only for Windows, I gotta try it when I get home later.
omgzam said:
I'm guessing this doesn't work on Mac? Because I'm currently on my Mac machine at work. If it's only for Windows, I gotta try it when I get home later.
Click to expand...
Click to collapse
There is .sh has well which should work on Mac BUT you have to go though a lot with drivers.
FACT: Google Developers use Mac.
Sent from my Nexus 4 using Tapatalk 4 Beta
andyabc said:
Go to the bootloader and run this tool: https://developers.google.com/android/nexus/images#occamjwr66v
It works every time.
Something went wrong with the flash for sure, I can tell in many ways so wiping will not help anyway unless you flash an other kernel.
This will wipe EVERYTHING so I don't know if it is worth flashing or flash an other kernel, you choose.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Just to be clear, this solution is just to flash your device back to stock.
I was updating my mdl s4 to a new build and flashed a rom for t0ltetmo, a T-Mobile note, by accident. I believe it updated the bootloader but not totally sure.
This is the error I get from TWRP when trying to flash a backup:
twrp E: unable ti mount ' /system'
If I go back to stock using kies can I then root with casual? Or will kies change my bootloader to something undesirable (mk1, nb1, etc.)
Any help would be greatly appreciated.
Have you tried flashing the correct firmware in Odin? You may have bricked your device, but it's a good sign you can still get into twrp.
Sent from my Nexus 5
No haven't tried Odin. I only have a Mac, need to borrow a friends PC. Don't think it's bricked. I believe it has the note 2 bootloader, and that's why TWRP isn't flashing the backup
numbere said:
No haven't tried Odin. I only have a Mac, need to borrow a friends PC. Don't think it's bricked. I believe it has the note 2 bootloader, and that's why TWRP isn't flashing the backup
Click to expand...
Click to collapse
If odin doesnt work, check out mobiletechvideos.com they fixed my bricked S4.
numbere said:
No haven't tried Odin. I only have a Mac, need to borrow a friends PC. Don't think it's bricked. I believe it has the note 2 bootloader, and that's why TWRP isn't flashing the backup
Click to expand...
Click to collapse
You could try a Windows vm on the Mac
Sent from my Nexus 5
Will try running odin on windows vm. Do you know if I go back to stock using kies if the bootloader will update to something other than the original MDL?
numbere said:
Will try running odin on windows vm. Do you know if I go back to stock using kies if the bootloader will update to something other than the original MDL?
Click to expand...
Click to collapse
If you use kies it'll force the latest firmware. You want to use Odin.
Sent from my Nexus 5
jd1639 said:
If you use kies it'll force the latest firmware. You want to use Odin.
Sent from my Nexus 5
Click to expand...
Click to collapse
Thanks for all the support! That was a scary situation.
Got Odin to run on parallels. Before using Odin I gave twrp one last try. Factory reset and then flashed a rom I tried previously, but this time without the gapps. Success! Got very lucky on this mistake.
Word to the wise double check your rom before flashing.
numbere said:
Thanks for all the support! That was a scary situation.
Got Odin to run on parallels. Before using Odin I gave twrp one last try. Factory reset and then flashed a rom I tried previously, but this time without the gapps. Success! Got very lucky on this mistake.
Word to the wise double check your rom before flashing.
Click to expand...
Click to collapse
Glad you got it working. It may have been a bad download of gapps.
Sent from my Nexus 5
No I definitely flashed a rom for the note 2.
Makes me think it's a sign that the software in our community is becoming more stable. Meaning that one can flash the incorrect ROM and potentially not destroy their device.
Sent from my SGH-I337 using XDA Premium 4 mobile app
numbere said:
No I definitely flashed a rom for the note 2.
Makes me think it's a sign that the software in our community is becoming more stable. Meaning that one can flash the incorrect ROM and potentially not destroy their device.
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No, you got lucky. The partitions are different for different devices and that's what will get you. I.e.flash a boot img where system is supposed to be and you'll be hard bricked
Sent from my Nexus 5
Wow, what a coincidence.
I had a similar issue over the last couple of days.
Here: http://forum.xda-developers.com/showthread.php?t=2701379
I used Odin in VMWare Fusion and it would not work at all, except to flash bootloaders and kernels. I finally got it to work through using heimdall using this thread: http://forum.xda-developers.com/showthread.php?t=2374441
I recently fixed an infamous bootloop i had by letting the battery die 100% (yeah I know it is bad), and then it booted. Well i went to flash a new rom and it never rebooted. I then went to flash stock from google. Still a bootloop. tried like 3 roms, still a loop. I then tried the killing my battery thing. Still a loop. Please, i know the phone isn't hard bricked, is there anything else i can do to boot it other than just flashing stock and factory resetting. Thanks.
Another thing, when i try to flash 4.2.2 the phone doesn't go to the boot logo.
Anybody? I need to fix this phone soon.
Wrong thread sorry
YFBanana said:
Anybody? I need to fix this phone soon.
Click to expand...
Click to collapse
Fastboot flash the factory image. Then boot into the stock recovery and do a factory reset.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Fastboot flash the factory image. Then boot into the stock recovery and do a factory reset.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
unfortunately that doesn't work, i have tried it many times.
YFBanana said:
unfortunately that doesn't work, i have tried it many times.
Click to expand...
Click to collapse
Then you have an issue with your device. What happens if you lock the bootloader and then reboot? Does it stay locked or is it still unlocked?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Then you have an issue with your device. What happens if you lock the bootloader and then reboot? Does it stay locked or is it still unlocked?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
It stays locked. I am guessing thats a good thing?
YFBanana said:
It stays locked. I am guessing thats a good thing?
Click to expand...
Click to collapse
Yep, if it didn't your emmc flash memory would be bad. I'd try re-downloading the factory image and trying again. Are you using the flash-all.bat to flash? You might try flashing all the components separately and see if any of them fail.
Sent from my Nexus 5 using XDA Free mobile app
You flashed stock firmware and it didn't work? What did it do when you flashed it?
Sent from my Moto G running Carbon ROM 4.4.4
jd1639 said:
Yep, if it didn't your emmc flash memory would be bad. I'd try re-downloading the factory image and trying again. Are you using the flash-all.bat to flash? You might try flashing all the components separately and see if any of them fail.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
None of the flashes failed. I have tried redownloading and i have also checked the md5's, so i dont think that would be it. I have also tried reformatting through twrp, and then flashing stock. Still nothing.
flashing 4.4.4 separately got me on the starting apps step, but that seems to be the place where it gets stuck.
I need to decide if i wanna take another month trying to fix the nexus 4 or just get the nexus 5. Nothing is working and i think i should just leave it now. But at the same time, i just wanna fix it so i don't have to spend money on a new phone. I have run out of things to try and revive the phone so i don't know what to do anymore.
YFBanana said:
I need to decide if i wanna take another month trying to fix the nexus 4 or just get the nexus 5. Nothing is working and i think i should just leave it now. But at the same time, i just wanna fix it so i don't have to spend money on a new phone. I have run out of things to try and revive the phone so i don't know what to do anymore.
Click to expand...
Click to collapse
so now you can boot to 4.4.4 ROM but your phone stuck at the "Starting apps" box rite?
groovepeppy said:
so now you can boot to the ROM? but never pass the "Starting apps"?
Click to expand...
Click to collapse
I think it was just the order i flashed the img files that made it go to that point, but i am pretty sure starting apps is where it gets stuck every time.
YFBanana said:
I think it was just the order i flashed the img files that made it go to that point, but i am pretty sure starting apps is where it gets stuck every time.
Click to expand...
Click to collapse
You can fastboot your phone i believe, you should try [HOW-TO] How to flash a factory image / return to stock / unlock / root #
Start from point C
I hope you haven't tried it yet
groovepeppy said:
You can fastboot your phone i believe, you should try [HOW-TO] How to flash a factory image / return to stock / unlock / root #
Start from point C
I hope you haven't tried it yet
Click to expand...
Click to collapse
I have tried it. Still no boot.
YFBanana said:
I have tried it. Still no boot.
Click to expand...
Click to collapse
there's must be a way cause you can boot on 4.4.4 but unfortunately i'm not that good in these kind of problems
but i hope you can find the cure soon
You can obviously get into flashboot, have you tried booting the latest twrp, wiping /system /data /cache and sideloading something different, like Paranoid Android?
Bootloop fix
First thing is that you have use Wug's Tool and flash the 4.3 stock image. In the Wug's tool select the option 'SOFT BRICK or BOOTLOOP' option and then flash the stock image in the fastboot mode. Definitely, I hope the phone will launch without any problem. The same problem I had faced with my nexus 4 and I flash the 4.3 stock image with the help of Wug's tool. Try it I hope it will fix the problem.