Database Users

Back to Factory with no computer access.

I everyone!
I just tried to connect my Nexus 4 to my windows 8.1 laptop and the phone is not recognised by the PC. It gives me Code 43 error, I tried everything, form fresh driver install to cable change. I also tried on another W7 laptop and nothing pops up there. The phone charges but in Device Manager it is not listed under Google ADB devices but appears with an exclamation mark under USB controllers saying Device Descriptor Request Failed. I fear it is an hardware problem and RMA is the only option left. However, my phone is Rooted, Stock but with modified build.prop, with TW touch recovery and unlocked. Since I have no access to ADB I cannot use the Android SDK tools or anything to flash the factory img. Is there any way in which I could flash back the sock image and lock the bootloader via recovery only?
Thanks everyone :crying::crying:

you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.

Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app

Thibaultvw said:
Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This was what I was thinking, however, the main issue would be locking the bootloader again
simms22 said:
you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.
Click to expand...
Click to collapse
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time

c0sk said:
This was what I was thinking, however, the main issue would be locking the bootloader again
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time
Click to expand...
Click to collapse
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.

mrhiab said:
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.
Click to expand...
Click to collapse
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?

c0sk said:
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?
Click to expand...
Click to collapse
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.

efrant said:
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.
Click to expand...
Click to collapse
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??

c0sk said:
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??
Click to expand...
Click to collapse
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2

efrant said:
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset

c0sk said:
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset
Click to expand...
Click to collapse
The way you removed SuperSU must have not worked properly. (I've never tried doing it from the SuperSU settings.) In any case, there's nothing more you can do now, so might as well send it in for RMA.

No OS. PLEASE HELP!!

I have an LG G2 vs980. I can get into fastboot and TWRP but for some reason the touch screen is really wonky and when i boot into download mode it takes me to fastboot. Right now im running Ubuntu but i can re install windows if i have to. Any help would be muchly appreciated.

shaggy9585 said:
I have an LG G2 vs980. I can get into fastboot and TWRP but for some reason the touch screen is really wonky and when i boot into download mode it takes me to fastboot. Right now im running Ubuntu but i can re install windows if i have to. Any help would be muchly appreciated.
Click to expand...
Click to collapse
we need a story, for starters what did you do/happened before you got into fastboot?

XxZombiePikachu said:
we need a story, for starters what did you do/happened before you got into fastboot?
Click to expand...
Click to collapse
Well im kinda new to the rooting thing but I believe my phone was only soft rooted. I was trying to install twrp but I got a dead android with a explanation mark or it would go to a black screen after the lg logo.i didn't know I was soft rooted when I was trying this. so after awhile I gave up. my phone still booted normally without trying to go into recovery. recently an update for android came out ( kitkat 4.4.2) so I decided to see if it would work. it restarted the phone to install the update and it got stuck in fastboot mode. i managed to find a way to install twrp using fastboot and adb. i did it but the touch screen was all funked up and i ended up wiping the system i think. just cant win. twrp wont mount the drive eiher. maybe because i have Ubuntu?

shaggy9585 said:
Well im kinda new to the rooting thing but I believe my phone was only soft rooted. I was trying to install twrp but I got a dead android with a explanation mark or it would go to a black screen after the lg logo.i didn't know I was soft rooted when I was trying this. so after awhile I gave up. my phone still booted normally without trying to go into recovery. recently an update for android came out ( kitkat 4.4.2) so I decided to see if it would work. it restarted the phone to install the update and it got stuck in fastboot mode. i managed to find a way to install twrp using fastboot and adb. i did it but the touch screen was all funked up and i ended up wiping the system i think. just cant win. twrp wont mount the drive eiher. maybe because i have Ubuntu?
Click to expand...
Click to collapse
well first the reason your phone died is because of the update you did after you had broken your stock recovery, if you have twrp currently there are two things you need to do:
1)get rid of the update using this
2)adb push/sideload a rom and try to flash or try and get in download mode to restore to stock

XxZombiePikachu said:
well first the reason your phone died is because of the update you did after you had broken your stock recovery, if you have twrp currently there are two things you need to do:
1)get rid of the update using this
2)adb push/sideload a rom and try to flash or try and get in download mode to restore to stock
Click to expand...
Click to collapse
is there a way to flash a rom using adb while in twrp or fastboot?

shaggy9585 said:
is there a way to flash a rom using adb while in twrp or fastboot?
Click to expand...
Click to collapse
no fastboot is only for restoring the phones stock partitions but if you use twrp sideload feature it should flash it once it's done copying it(I know that's how it works with philz)

XxZombiePikachu said:
no fastboot is only for restoring the phones stock partitions but if you use twrp sideload feature it should flash it once it's done copying it(I know that's how it works with philz)
Click to expand...
Click to collapse
now i just need to figure out whats going on with the touch sensor. idk if its the phone or just twrp

Issue updating to Android 5.0

I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4

Your build.prop isn't standard, get the original one, or just use the factory image to update.

Rusty! said:
Your build.prop isn't standard, get the original one, or just use the factory image to update.
Click to expand...
Click to collapse
what i need to install to correct his to the correct build.prop of 4.4.4?
ps. my last 4.4.4 was updated directly OTA..

Just download the 5.0 factory image, remove -w from the flash-all script and it will update you. Less dicking around that way.

inspiron41 said:
I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4
Click to expand...
Click to collapse
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?

CBers said:
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?
Click to expand...
Click to collapse
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app

inspiron41 said:
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?

CBers said:
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?
Click to expand...
Click to collapse
Go to this website:
http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It has detail instruction and jump down to step 3 regarding to -w
Sent from my Nexus 5 using XDA Free mobile app

I was having the same issue as the OP. So after reading this thread, I've performed the following:
Downloaded Android 5.0 factory image from: https://developers.google.com/android/nexus/images
Followed the instructions at this site, AND MADE SURE TO REMOVE '-w' AS INSTRUCTED, TO PRESERVE DATA: http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It was pretty easy. I've been waiting about 30 minutes looking at the boot graphic. Hope it turns out OK. But it is easier than playing with the OTA.

After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk

Darnell_Chat_TN said:
After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?

[Lemmy] said:
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?
Click to expand...
Click to collapse
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.

Darnell_Chat_TN said:
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.
Click to expand...
Click to collapse
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.

[Lemmy] said:
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.
Click to expand...
Click to collapse
Why not just update using the 5.1 factory image? I run unlocked stock/rooted on my N10, and that's the method I always use to update. Would also do it this way on my N5 and now N6. Just fastboot flash all the images from the factory image manually (READ: EXCEPT USERDATA). You can also skip flashing the recovery if you run a custom recovery. However, for the sake of completion, I include flashing the stock recovery. Then I let it boot up normally. Then I'll boot back into the bootloader and flash TWRP and flash SuperSU. Updating this way is easier for me since I don't have to worry about the OTA failing due to customizations I may have made to the system (especially now with the new way Android updates after 5.0).

I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?

[Lemmy] said:
I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?
Click to expand...
Click to collapse
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.

charesa39 said:
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.
Click to expand...
Click to collapse
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!

mj56gt said:
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!
Click to expand...
Click to collapse
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.

charesa39 said:
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.
Click to expand...
Click to collapse
Thanks a lot for the suggestions! Have a wonderful weekend...

Never mind

Recovery Broken

Hey guys,
I have a Rogers p705G. I tried flashing a recovery. However I accidentally flashed one for L3. Now when I go into recovery the graphics is completely messed up and I cant read anything. Before this I flashed Kitkat Prime. For some reason I have lost root. I am trying to reinstall a proper recovery for the L7 so I can properly flash another rom or go to stock. Can anyone please help me with this? Thanks.
Oppiee

Hmm... I think I'd tried a hard reset with the hardware buttoms, if not I'd tried to install a stock room in download mode. Then, you can try it (root, recovery, flashing) again.

oppiee said:
Hey guys,
I have a Rogers p705G. I tried flashing a recovery. However I accidentally flashed one for L3. Now when I go into recovery the graphics is completely messed up and I cant read anything. Before this I flashed Kitkat Prime. For some reason I have lost root. I am trying to reinstall a proper recovery for the L7 so I can properly flash another rom or go to stock. Can anyone please help me with this? Thanks.
Oppiee
Click to expand...
Click to collapse
download cwm for your device place it on your internal sdcard and download flashify apk from google play or any other marker you may be using. And flash the recovery from the app.
Sent from my LG-E610 using XDA Free mobile app

oppiee said:
Hey guys,
I have a Rogers p705G. I tried flashing a recovery. However I accidentally flashed one for L3. Now when I go into recovery the graphics is completely messed up and I cant read anything. Before this I flashed Kitkat Prime. For some reason I have lost root. I am trying to reinstall a proper recovery for the L7 so I can properly flash another rom or go to stock. Can anyone please help me with this? Thanks.
Oppiee
Click to expand...
Click to collapse
Flash throught fastboot

Help the learning noob somewhat LG G2 T-Mobile D8o130b

Okay so i have a few questions here its been a while since i have placed a Rom onto my device the last one was a Sprint model of the G2 and i was able to successfully install CM12 nightly onto it.
With my T-Mobile G2 i had used the once click root application to do so and used auto rec from the app store to install TWRP recovery hopefully i didn't do anything wrong at this point. So now i try to boot into recovery using the power and the down key at the same time but when i did this i was prompted with do you want to reset all data or not and i of course i chose no and booted back home.
Yes i have Super Su with granting access so to solve this minor problem. I had the quick boot application here to boot into recovery but another problem persisted. I cant flash anything over it fails every time and i am trying to flash 5.1.1 cm 12 i think with gapps with 5.1 i believe but in doing so still failed it matched up and everything. I thought that maybe i was trying to flash something that's really not compatible with my phone so i tried to use the same rom but different carriers.
It was cm-12-20150406-NIGHTLY-D801.zip and gapps-lp-20150222-signed but still failed to install the rom? is there something im doing wrong? May i have a tutorial step by step on what to do to successfully flash? and why cant i boot into recovery with the button configuration did i do something wrong with that i just want to so that if theirs a boot load epidermic and i need to use that to restore and see what the problem is? just need help please

Tensaz said:
Okay so i have a few questions here its been a while since i have placed a Rom onto my device the last one was a Sprint model of the G2 and i was able to successfully install CM12 nightly onto it.
With my T-Mobile G2 i had used the once click root application to do so and used auto rec from the app store to install TWRP recovery hopefully i didn't do anything wrong at this point so now i try to boot into recovery using the power and the down key at the same time but when i did this i was prompted with do you want to reset all data or not and i of course i chose no and booted back home and yes i have Super Su with granting access so to solve this minor problem i had the quick boot application here to boot into recovery but another problem persisted i cant flash anything over it fails every time and i am trying to flash 5.1.1 cm 12 i think with gapps with 5.1 i believe but in doing so still failed it matched up and everything. I thought that maybe i was trying to flash something that's really not compatible with my phone so i tried to use the same rom but different carriers cm-12-20150406-NIGHTLY-D801.zip and gapps-lp-20150222-signed but still failed to install the rom? is there something im doing wrong? May i have a tutorial step by step on what to do to successfully flash? and why cant i boot into recovery with the button configuration did i do something wrong with that i just want to so that if theirs a boot load epidermic and i need to use that to restore and see what the problem is? just need help please
Click to expand...
Click to collapse
There's no way anyone can read that without any punctuation marks or any paragraph order.
Basically, the data reset function doesn't work when you have a custom recovery, that's how you enter it. But the TWRP version installed is usually old, somewhat like 2.7.0.0, so you need to update it before installing any roms.

If you really do have recovery installed when you get to the screen about erasing data just choose yes and yes and it will just take you to recovery. If that's too scary for you then just boot into recovery using an app like rebooter from the play store.
As far as flashing it sounds like you may have downloaded bad files. If you're using your phone to download the roms maybe try using a pc then transferring to your phone. And DON'T flash roms for a different carrier, you're just asking for trouble.
Sent from my LG-D801

Choristav said:
There's no way anyone can read that without any punctuation marks or any paragraph order.
Basically, the data reset function doesn't work when you have a custom recovery, that's how you enter it. But the TWRP version installed is usually old, somewhat like 2.7.0.0, so you need to update it before installing any roms.
Click to expand...
Click to collapse
I Have version 2.8.6.1

rick09 said:
If you really do have recovery installed when you get to the screen about erasing data just choose yes and yes and it will just take you to recovery. If that's too scary for you then just boot into recovery using an app like rebooter from the play store.
As far as flashing it sounds like you may have downloaded bad files. If you're using your phone to download the roms maybe try using a pc then transferring to your phone. And DON'T flash roms for a different carrier, you're just asking for trouble.
Sent from my LG-D801
Click to expand...
Click to collapse
I used my computer to download the files all together and the problem still persisted.
And that i do know to not flash with different Carrier did it with a s4 without thinking.

Tensaz said:
I used my computer to download the files all together and the problem still persisted.
And that i do know to not flash with different Carrier did it with a s4 without thinking.
Click to expand...
Click to collapse
The problem might be that you are on the wrong bootloader so v30 lollipop. As loki and bump don't work on it it will result into an failed flash. What you can do is flash the right bootloader or easily downgrade bootloader and bootstack with autorec for your phone. Read carefully which one you need for your tmobile d801. If there is an loki error then just flash the jellybean bootloader what you easily can do with autorec.
Sent from my LG-D802 using Tapatalk

wulsic said:
The problem might be that you are on the wrong bootloader so v30 lollipop. As loki and bump don't work on it it will result into an failed flash. What you can do is flash the right bootloader or easily downgrade bootloader and bootstack with autorec for your phone. Read carefully which one you need for your tmobile d801. If there is an loki error then just flash the jellybean bootloader what you easily can do with autorec.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Still a bit noobish how do i do that boot loader thing?

Tensaz said:
Still a bit noobish how do i do that boot loader thing?
Click to expand...
Click to collapse
Well you download the right version for your d801
https://www.androidfilehost.com/?w=files&flid=13763
Then you need to install it
Click on the lollipop and let it do its job. If it asks for root then allow it.
It will probably reboot and you are done. Only need to flash then a newer recovery. Also search bender_007 on xda and leave him a thanks perhaps for his app
Sent from my LG-D802 using Tapatalk

wulsic said:
Well you download the right version for your d801
Then you need to install it
Click on the lollipop and let it do its job. If it asks for root then allow it.
It will probably reboot and you are done. Only need to flash then a newer recovery. Also search bender_007 on xda and leave him a thanks perhaps for his app
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
my god i can flash now awesome thank you now i have one last question if you dont mind telling me since i downgraded my boot loader to kk i think using the auto rec do i need to flash my current 30b boot-stack first before i use my stock restore? or is there an easier way to do so (tried to go into stock but was met with a black screen after lg logo)

Tensaz said:
my god i can flash now awesome thank you now i have one last question if you dont mind telling me since i downgraded my boot loader to kk i think using the auto rec do i need to flash my current 30b boot-stack first before i use my stock restore? or is there an easier way to do so (tried to go into stock but was met with a black screen after lg logo)
Click to expand...
Click to collapse
Well, as far as I know autorec downgrades to jb bootloader, to boot into stock you could find d801 lp modem and d801 lp bootstack/bootloader as it might need kk bootloader
Sent from my LG-D802 using Tapatalk

wulsic said:
Well, as far as I know autorec downgrades to jb bootloader, to boot into stock you could find d801 lp modem and d801 lp bootstack/bootloader as it might need kk bootloader
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
thank you for your help i now have a boot loader for stock that i found and im using auto rec for every time i reboot to cm12 getting the hang of this flashing thing i just want to know if theres any problems with the network service for cm12 at all?

Tensaz said:
thank you for your help i now have a boot loader for stock that i found and im using auto rec for every time i reboot to cm12 getting the hang of this flashing thing i just want to know if theres any problems with the network service for cm12 at all?
Click to expand...
Click to collapse
With cm12 I am not sure but the cause could be perhaps the wrong modem, and or bootloader. I also suggest to check out newer custom roms the only cyanogenmod as some custom roms are already running on lollipop modem and caf. CAF is code aurora forum so kinda it will also have changes specifically for qualcomm devices.
Sent from my LG-D802 using Tapatalk