Database Users

Hard Brick [Resolved] - Still need Advice

Hello everybody.
A few days back I managed to brick my Nexus 4 after using it for 1 day!!!! I realize that this all is a very moronic situation and there isn't a fix for my brick because a used a *Toolkit*. Well, I'm already receiving my replacement and it will be here in an hour.
I know how everyone here feels about Google paying for our mistakes but I'm so lucky they're so kind. The advice that I need is on how to NEVER be in this same position. If I were to have set up fastboot instead of a toolkit would all of this have been avoidable? Btw, CM 10.1 is how I bricked my phone....I never have had any luck with that rom.
Thanks everyone for your advice.

Almost all errors are caused by, you guessed it, users. I am skeptical when people claim the toolkit bricked their phone. Also, if cm 10.1 has been troublesome for you, why keep using it? Its the very definition of insanity: keep doing the same thing over and over and expecting different result.
Sent from my Nexus 4 using xda premium

Sooooo, in your professional opinion....would my brick have been less severe if I used fastboot?

Maybe you flashed the wrong cm 10.1 ROM. Perhaps, from another device?
Sent from my Nexus 4

blitzzz3434 said:
Maybe you flashed the wrong cm 10.1 ROM. Perhaps, from another device?
Sent from my Nexus 4
Click to expand...
Click to collapse
Well what happened was when I tried to flash it the first time I got a boot loop. So I restored from a backup. Then I redownloaded and when I was in my custom recovery I did a factory reset, a cache wipe and a factory wipe. Then I installed CM.
No after like 3 minutes of booting, I got to my homescreen. I think what happened was I wanted to get off CM because it wasn't working right so I tried to boot into recovery so I held down power and volume keys. I got a yellow light then a red light and now bootloader. After deliberation I figured that when I reset factory settings I got rid of the bootloader some how so I googled it. I found smirkit and tried to install a bootloader. After I did that from my phone I powered down my phone and tried to get to the bootloader but I found that I was bricked.
My excuse for all of this stupidity is that it was 6am and I hadn't slept yet. Nothing good happens for me without sleep lol. btw, thats as accurate as I remember.

Alpha-Wat3rloo said:
After deliberation I figured that when I reset factory settings I got rid of the bootloader some how so I googled it. I found smirkit and tried to install a bootloader. After I did that from my phone I powered down my phone and tried to get to the bootloader but I found that I was bricked.
Click to expand...
Click to collapse
What is smirkit? The only hits I could find on it were for the Kindle Fire. It sounds to me like you flashed a bootloader for another device, that would certainly give you a hard brick.
Sent from my Nexus 4

As I suspected, user error.
Sent from my Nexus 4 using xda premium

I don't think you needed to suspect anything. I am admitting that I bricked it and it wasn't a toolkit.... What I needed you to tell me is would it have been recoverable if I used fastboot and not a toolkit. I would appreciate it if you would answer that question instead of needlessly placing blame.
Sent from my Nexus 4 using xda app-developers app

Thank you you've actually helped Mr to figure out why it happened. It was super late/early. Serves me right flashing anything without proper rest.
Sent from my Nexus 4 using xda app-developers app

If you had flashed the wrong bootloader or kernel (one meant for a different device) via fastboot then you would still have a hard brick.
Using fastboot instead of a toolkit does mean you have more control over what your are doing, but you still need to make sure you are still flashing the right things.
Sent from my Nexus 4

Alpha-Wat3rloo said:
I don't think you needed to suspect anything. I am admitting that I bricked it and it wasn't a toolkit.... What I needed you to tell me is would it have been recoverable if I used fastboot and not a toolkit. I would appreciate it if you would answer that question instead of needlessly placing blame.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Your original post made it sound like you used one of the toolkits made specifically for the Nexus 4 and that is what had bricked your phone. It wasn't till half way down the thread you mention you used a tookit for another device. Toolkits are not free from user error even when you use the correct one as you still have to download the correct files and place them in the correct folders. There have been a lot of newbies bricking phones because they have downloaded the incorrect files and then blame it on the developers and or phone for being defective. So this is why people are skeptical when they read these threads.

Alpha-Wat3rloo said:
I don't think you needed to suspect anything. I am admitting that I bricked it and it wasn't a toolkit.... What I needed you to tell me is would it have been recoverable if I used fastboot and not a toolkit. I would appreciate it if you would answer that question instead of needlessly placing blame.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
And that`s what happens when your SMARTphone is Smarter than you.....

[Q] Canadian Variant [SM-N900W8] Stuck In Boot Loop!

I've been reading through other threads here on XDA about a common boot loop issue that N900T users are experiencing, but nowhere was it mentioned that the Canadian variant users had a similar problem, but I do.
I was wondering if there were any other SM-N90028 users out there that were stuck in a boot loop?
Here is my situation:
I have a Canadian SM-N900W8 (it is, also a Qualcomm LTE version) and I'm in a boot loop... it all started when I tried to restore a Stock-Rooted Rom with TWRP.
I can't, however get it out, and I've tried all of the versions of TWRP, I've also used odin like 30 times... nothing.
I successfully restored a Rooted stock ROM through TWRP, but it wasn't until I re-installed a factory un-rooted one that things got ugly..
So I was thinking about this and perhaps the cause of this is KNOX... since the first thing I did when I rooted my phone initially was uninstall KNOX and all of its files. I know these didn't carry over when I did a TWRP backup, which is perhaps why my restore of that backup worked the first time. The second time, I just went and downloaded everything stock and used Odin, and that's when the bootloop occurred.
if anyone knows of a way to solve this, I'd be forever grateful!
I really hope I will be able to fix this...

Not to sound.to xdaish...but dude seriously this topic.is all.over the n3 forums. Have a.look and you will find tons of info.
Also...good idea to.read prior to flashing..if you had you would have know not to restore with twrp since it causes bootloops.
Just trying to you some friendly advice.
Sent from my SM-N900W8 using xda premium

force70 said:
Not to sound.to xdaish...but dude seriously this topic.is all.over the n3 forums. Have a.look and you will find tons of info.
Also...good idea to.read prior to flashing..if you had you would have know not to restore with twrp since it causes bootloops.
Just trying to you some friendly advice.
Sent from my SM-N900W8 using xda premium
Click to expand...
Click to collapse
Thank you, but I've read them all and most are regarding the n900t, I felt it appropriate to ask about the n900w8 variant.
Also, I know that would have been better, but it's too late for that now. I just thought I'd share my experiences here with this issue so that others will know better.

So I tried a different stock ROM, and with the latest version of Odin, but it still is in a boot loop.
However there is one difference; this time it will boot past the Samsung logo and into android, but then a window will pop up saying "Process system isn't responding" and ask me to wait for it to respond or close it. Regardless of what I select, it will end up rebooting seconds later.
In the very short time that everything stays booted for, I can access the two pull-down menus from the top, but selecting anything will yield me no results.
Perhaps this can tell us more about this issue?

Did you have a read.through this....a few.guys have revived their n900w8s here
http://forum.xda-developers.com/showthread.php?p=46450690
Sent from my SM-N900W8 using xda premium

force70 said:
Did you have a read.through this....a few.guys have revived their n900w8s here
http://forum.xda-developers.com/showthread.php?p=46450690
Sent from my SM-N900W8 using xda premium
Click to expand...
Click to collapse
Thanks! I checked it out and my phone is already set to those settings, so it didn't work, but I'm still trying!

c_est_la_vie said:
Thanks! I checked it out and my phone is already set to those settings, so it didn't work, but I'm still trying!
Click to expand...
Click to collapse
Check post #350 in this thread and read forward. http://forum.xda-developers.com/showthread.php?t=2467001&page=46

this worked!
Hey guys, I'm not sure if anyone's checked this out yet, but I managed to get myself out of the boot loop!
here is the solution:
http://forum.xda-developers.com/showthread.php?t=2471421

Glad your back up and running!
Sent from my SM-N900W8 using xda premium

Thanks!
Sent from my Nexus 7 using XDA Premium 4 mobile app

Help please

So I was trying to help a friend flash stock using Odin because his phone app was being a piece of crap, he was on a CM 11 nightly and, well, long story short I almost bricked his phone not knowing there is a limit on how many times you can flash a Samsung device using Odin because of the yellow triangle. I can't use triangle away because it's the CM ROM on a CM kernel, I was able to get rid of the softbrick by using a older CM ROM on his SD card, this wouldn't be a problem if his phone app was still working, his WiFi was working and if his sound was working, but it's not. So to recap and for the question, Samsung is stupid, and can anyone help?
Thanks in advanced
Sent from my awesome LG-E980

lonlyhornet said:
So I was trying to help a friend flash stock using Odin because his phone app was being a piece of crap, he was on a CM 11 nightly and, well, long story short I almost bricked his phone not knowing there is a limit on how many times you can flash a Samsung device using Odin because of the yellow triangle. I can't use triangle away because it's the CM ROM on a CM kernel, I was able to get rid of the softbrick by using a older CM ROM on his SD card, this wouldn't be a problem if his phone app was still working, his WiFi was working and if his sound was working, but it's not. So to recap and for the question, Samsung is stupid, and can anyone help?
Thanks in advanced
Sent from my awesome LG-E980
Click to expand...
Click to collapse
First thing you have to do for anyone to help you is,provide which build you were on and which stock rom you were trying to flash. There are tons of people here with great knowledge if you can be real specific.
Sent from my Nexus 5 using Tapatalk

So you wanna go to complete stock on a sprint s4?
Sent from my SPH-L720 using XDA Premium 4 mobile app

Fairly sure there is no limit to the amount of times you can flash using Odin. There is a counter but no limit
Sent from my SPH-L720 using xda app-developers app

Sorry, Samsung isn't stupid or they wouldn't just magically be a $250+billion dollar company that has been around for 76 years.
Because you jumped in and were unsuccessful with what you were doing doesn't constitute failure on their part.
How about taking that phone - S4 back to bone stock. ALL the answers on how to do that are here. In fact in the last couple days I've personally given instructions on how to do that for a number of people here in the help section. Do some searching and reading and you'll find your answers.
It always helps to come to a manufacture's section and say how sh**y they are. Makes those of us who choose to use and support them feel ever so helpful.

Ok sorry should've been more specific, I'm not new to these forums I was just in a hurry, also seriously guys I'm just frustrated I know Samsung is not stupid you don't have to post their history, they're awesome it's just dumb that they have a limit, and yes if you install the latest stock Sprint update (the one I did before I rooted and rom'd his phone) there wouldn't be a thing such as triangle away. Anyway on Odin it says it passed when flashing stock (the firmware that comes with the phone) but it does it in 4 seconds, and when his phone boots up and it just restores CM, so far everything we've tried either softbricks it or restores CM. Is there anything that completely and I mean completely restores this phone
Sent from my awesome LG-E980

lonlyhornet said:
Ok sorry should've been more specific, I'm not new to these forums I was just in a hurry, also seriously guys I'm just frustrated I know Samsung is not stupid you don't have to post their history, they're awesome it's just dumb that they have a limit, and yes if you install the latest stock Sprint update (the one I did before I rooted and rom'd his phone) there wouldn't be a thing such as triangle away. Anyway on Odin it says it passed when flashing stock (the firmware that comes with the phone) but it does it in 4 seconds, and when his phone boots up and it just restores CM, so far everything we've tried either softbricks it or restores CM. Is there anything that completely and I mean completely restores this phone
Sent from my awesome LG-E980
Click to expand...
Click to collapse
Where are you getting this idea there is a limit on Odin flashes?
Sent from my SPH-L720 using xda app-developers app

There is no limit, as mentioned already, with Odin.
I've used it probably a hundred times since I got my S4. I know others have used it more.
Take some time, look through the Q&A/help forum and you'll see some posts I've helped others with, in the last 24hours alone, on how to get back to stock.
Edit:
Okay read this post. It'll get you to stock. Just read the instuctions on how to do it.

Ok I'll try it thanks for tolerating me I can be hard to understand when panicking
Sent from my awsome LG-E980

leaderbuilder said:
There is no limit, as mentioned already, with Odin.
I've used it probably a hundred times since I got my S4. I know others have used it more.
Take some time, look through the Q&A/help forum and you'll see some posts I've helped others with, in the last 24hours alone, on how to get back to stock.
Edit:
Okay read this post. It'll get you to stock. Just read the instuctions on how to do it.
Click to expand...
Click to collapse
Did it and it worked thanks man! sorry for being rude I was just worried that I may have ruined my friends phone.

lonlyhornet said:
Did it and it worked thanks man! sorry for being rude I was just worried that I may have ruined my friends phone.
Click to expand...
Click to collapse
Glad you got it working and THANK YOU for posting back - that is what helps the community.
I understand the panic too. Especially when things are f'd up.
But if there is one valuable lesson I've learned in my half century of life; if you can just pause, relax and step back, many problems are easily resolved. And better yet more avoided by haste.
Good luck with the new phone setup.

OK one more quick thing, we flashed it successfully but now it won't boot its been over an hour after we flashed and its stuck on the Sprint logo

lonlyhornet said:
OK one more quick thing, we flashed it successfully but now it won't boot its been over an hour after we flashed and its stuck on the Sprint logo
Click to expand...
Click to collapse
You can first boot to stock recovery (power on + volume up) and choose a 'factory reset'. That often clears stuff up pretty well
Or
Try and PC Oding a stock MK2 kernel. Then battery pull and restart after. Saw this on a few phones
I'll have to search to find it but it's here somewhere.

leaderbuilder said:
You can first boot to stock recovery (power on + volume up) and choose a 'factory reset'. That often clears stuff up pretty well
Or
Try and PC Oding a stock MK2 kernel. Then battery pull and restart after. Saw this on a few phones
I'll have to search to find it but it's here somewhere.
Click to expand...
Click to collapse
Thanks! Factory resetting worked his phone is back on stock and ready for 4.4.2 thanks for the help LeaderBuilder!

lonlyhornet said:
Thanks! Factory resetting worked his phone is back on stock and ready for 4.4.2 thanks for the help LeaderBuilder!
Click to expand...
Click to collapse
Great!
Sent from my SPH-L720 using XDA Premium 4 mobile app

[Q] D800 - No recovery - Unable to flash in DL mode

So I'll start by saying I made a boo boo and this is 100% my fault.
I rooted my stock D800 and flashed TWRP. I flashed Cyanogenmod but where I messed is up when I flashed the D802 ROM and not the D800. I figured I'd just boot into recovery again using the hardware buttons, but all that happens is the screen turns on but nothing actually displays.
After that, I figured I'd just flash a stock ROM and basically start over using Download Mode and FlashTool. Unfortunately, I can't flash the stock firmware because the phone is NOT identifying itself as a D800, it's identifying as a D802, so FlashTool will not allow me to flash the proper files.
What I don't understand is why was I able to get into TWRP that one instance and flash the ROM but now whenever I attempt to get into recovery again the screen just turns on but recovery doesn't show. Makes no sense to me. I've tried getting into recovery using the hardware buttons a million times after but no dice.
I know it's not much, but I'm willing to throw in 10 bucks via PayPal for whoever can help me fix this.

bbeaulieu said:
So I'll start by saying I made a boo boo and this is 100% my fault.
I rooted my stock D800 and flashed TWRP. I flashed Cyanogenmod but where I messed is up when I flashed the D802 ROM and not the D800. I figured I'd just boot into recovery again using the hardware buttons, but all that happens is the screen turns on but nothing actually displays.
After that, I figured I'd just flash a stock ROM and basically start over using Download Mode and FlashTool. Unfortunately, I can't flash the stock firmware because the phone is NOT identifying itself as a D800, it's identifying as a D802, so FlashTool will not allow me to flash the proper files.
What I don't understand is why was I able to get into TWRP that one instance and flash the ROM but now whenever I attempt to get into recovery again the screen just turns on but recovery doesn't show. Makes no sense to me. I've tried getting into recovery using the hardware buttons a million times after but no dice.
I know it's not much, but I'm willing to throw in 10 bucks via PayPal for whoever can help me fix this.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2582845 This ROM is compatible with both d800 and d802 variants. You can try flashing this just to get your phone up and running

Art Vanderlay said:
http://forum.xda-developers.com/showthread.php?t=2582845 This ROM is compatible with both d800 and d802 variants. You can try flashing this just to get your phone up and running
Click to expand...
Click to collapse
Unfortunately I can't do that because I can't get into recovery mode

Im in the same situation as you bro. Tried to use LG flash tools to flash my sprint back to stock and its detecting my phone as a d801. No help yet

same here from 2 weeks..

EVERYONE! I have found a resolution for this.
First, visit this thread.
Download the DLL from this post and flash with a normal stock ROM. I used this combo and it flashed WITHOUT issue. Hope it helps you guys out as well.

bbeaulieu said:
EVERYONE! I have found a resolution for this.
First, visit this thread.
Download the DLL from this post and flash with a normal stock ROM. I used this combo and it flashed WITHOUT issue. Hope it helps you guys out as well.
Click to expand...
Click to collapse
Yeah this should Definitely be in a FAQ somewhere
Sent from my LG-D800 using xda app-developers app

afrojoc said:
Yeah this should Definitely be in a FAQ somewhere
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
No you guys just need to slow down.
Sent from my SCH-I545 using XDA Premium 4 mobile app

JCBiznatch said:
No you guys just need to slow down.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So it doesn't need to be in FAQ somewhere?Lol it would've helped me out dramatically! It's not my fault that there are recoveries that mess up your phone. Coming from Samsung phones I didn't think that someone would release faulty software that would render your phone unusable.

[Q] I'm stuck in CWM recovery mode

Hello,
Yesterday an update came up on my screen, I clicked "Install Now"
The phone restarted into CWM.
I am rooted ofcourse, and I'm really scared for my phone,
Is there anything to be done?

Which phone do you have?
Your phone is rooted, do you have a stock or custom ROM?
You should provide a little more information so people can help you.
Sent from my HTC One X+ using xda app-developers app

LG G2 D802 T-mobile version
umm...I had stock firmware,
Just now i installed CyanogenMod, and still im going back to recovery...

btw, if i have recovery up and working, i shouldn't be madly worried...shoud i?,,

iMetalliX said:
LG G2 D802 T-mobile version
umm...I had stock firmware,
Just now i installed CyanogenMod, and still im going back to recovery...
Click to expand...
Click to collapse
You should try to reverse back to stock.
http://forum.xda-developers.com/showthread.php?t=2432476
I've found that on the forums for LG G2's.
Verstuurd vanaf mijn HTC One X+ met Tapatalk
---------- Post added at 08:00 AM ---------- Previous post was at 07:54 AM ----------
iMetalliX said:
btw, if i have recovery up and working, i shouldn't be madly worried...shoud i?,,
Click to expand...
Click to collapse
The only thing you probably have to worry about is the data on your device since it is possible you have to wipe it. No worries on bricked device.
Verstuurd vanaf mijn HTC One X+ met Tapatalk

iMetalliX said:
btw, if i have recovery up and working, i shouldn't be madly worried...shoud i?,,
Click to expand...
Click to collapse
No. But it looks like you flashed a borked file. Maybe the CM you installed has a wrong MD5, or you might have flashed a CM that's for a different G2. Either way, you can either push a new ROM zip into your phone to flash, or KDZ back to stock like the guy above me said. Good luck!
And don't worry, your phone is completely fine. But this should be a lesson to always perform a backup before ANY ROM flashing.

mackster248 said:
No. But it looks like you flashed a borked file. Maybe the CM you installed has a wrong MD5, or you might have flashed a CM that's for a different G2. Either way, you can either push a new ROM zip into your phone to flash, or KDZ back to stock like the guy above me said. Good luck!
And don't worry, your phone is completely fine. But this should be a lesson to always perform a backup before ANY ROM flashing.
Click to expand...
Click to collapse
Thank you mate )
umm..i'm going back to stock, and the MD5 was ok, and yes, im a noob

Lg g2 d80220a
iMetalliX said:
btw, if i have recovery up and working, i shouldn't be madly worried...shoud i?,,
Click to expand...
Click to collapse
What I'd like to know is how did you get CWM in the first place? I've tried for a couple of hours with ROM Manager and the D802 is not supported even though it claims it is. All I get is the red triangle on top of the green android bot and what looks like 2.x CWM. Not sure since I'm new. But it only has about 5 options. No MOUNT, NO ADVANCED, Looks unsuitable for flashing a ROM. I saw this version the very first time I flashed a phone and I soft bricked the phone. It was a Nexus 4. I recovered but I'm not taking any chances and messing with that again. The only way I recovered was using Wugfresh. I need something like Wugfresh for my D802 where I can take those risk. I'm angry because I can't flash anything now. I've got 327 apps to get installed. No one wants to do that manually. It is really inconceivable that this phone which is still arguably the best in the world after 6 months is not supported the way it should be with recovery. Any help in getting CWM working would be greatly appreciated.

notanymore said:
What I'd like to know is how did you get CWM in the first place? I've tried for a couple of hours with ROM Manager and the D802 is not supported even though it claims it is. All I get is the red triangle on top of the green android bot and what looks like 2.x CWM. Not sure since I'm new. But it only has about 5 options. No MOUNT, NO ADVANCED, Looks unsuitable for flashing a ROM. I saw this version the very first time I flashed a phone and I soft bricked the phone. It was a Nexus 4. I recovered but I'm not taking any chances and messing with that again. The only way I recovered was using Wugfresh. I need something like Wugfresh for my D802 where I can take those risk. I'm angry because I can't flash anything now. I've got 327 apps to get installed. No one wants to do that manually. It is really inconceivable that this phone which is still arguably the best in the world after 6 months is not supported the way it should be with recovery. Any help in getting CWM working would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried philz http://forum.xda-developers.com/showthread.php?t=2554053
Sent from my LG-D800 running stock kk, rooted with philz using XDA app

Lg g2 d80220a
XxZombiePikachu said:
Have you tried philz http://forum.xda-developers.com/showthread.php?t=2554053
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
That won't work because you can't even get to the menus to install the zip. That the whole problem. You can't really do anything because it basically hangs up with the red triangle. With the number of people having this problem and how great a phone this is you'd figure this problem would not even exist. Here's a screen shot of the problem everybody is having.

notanymore said:
That won't work because you can't even get to the menus to install the zip. That the whole problem. You can't really do anything because it basically hangs up with the red triangle. With the number of people having this problem and how great a phone this is you'd figure this problem would not even exist. Here's a screen shot of the problem everybody is having.
Click to expand...
Click to collapse
okay so that's the stock recovery, by any chance are you on kitkat because it says d80220a?

iMetalliX, can you still flash a .zip file?, if you can I know this would work for you, just translate the thread and OTG flash the small zip file. This happened to me yesterday, and piece of cake.

me having the same problem (stock recovery)
cant flash anything (E:footer is wrong ) (E:signature verification faild)
and now when flashing new Philz recovery ( assert faild : run_program (`/temp/loki.sh`) ==0 E:error in /temp/update.zip status 7
since 2 days trying to get out of it but i cant lol

same thing happened to me but i managed to install twrp now my problem is im stocked at lg logo. I have no back up nor any rom downloaded. i have kdz file saved on my g2 but i cant copy it to the computer since it cant be detected or if it has a way please please let me know. Pls help me out of it, i miss my phone. Thank you.

Lg g2 d80220a
XxZombiePikachu said:
okay so that's the stock recovery, by any chance are you on kitkat because it says d80220a?
Click to expand...
Click to collapse
Yeah I made the foolish mistake of upgrading to kitkat. I knew it as soon as I hit yes button to upgrade. Too late.
---------- Post added at 08:37 AM ---------- Previous post was at 08:24 AM ----------
pmorales said:
iMetalliX, can you still flash a .zip file?, if you can I know this would work for you, just translate the thread and OTG flash the small zip file. This happened to me yesterday, and piece of cake.
Click to expand...
Click to collapse
I'm new so don't know much. My understanding is you can't flash anything without being in recovery, right? Look at busted25's post. I'm not risking anything that is not concrete. Much as I like to tinker around I accomplish nothing if I end up with a brick. On my Nexus I could risk everything and because I had Wugfresh. No such thing. I'm going to look at he LG software suite and see if can backup the phone enough to restore it should i soft brick or something

notanymore said:
Yeah I made the foolish mistake of upgrading to kitkat. I knew it as soon as I hit yes button to upgrade. Too late.
Click to expand...
Click to collapse
Well that's why you can't get recovery, kit Kat does not have ability for recovery and who knows if it ever will
Sent from my LG-D800 running stock kk, rooted with philz using XDA app

notanymore said:
Yeah I made the foolish mistake of upgrading to kitkat. I knew it as soon as I hit yes button to upgrade. Too late.
---------- Post added at 08:37 AM ---------- Previous post was at 08:24 AM ----------
I'm new so don't know much. My understanding is you can't flash anything without being in recovery, right? Look at busted25's post. I'm not risking anything that is not concrete. Much as I like to tinker around I accomplish nothing if I end up with a brick. On my Nexus I could risk everything and because I had Wugfresh. No such thing. I'm going to look at he LG software suite and see if can backup the phone enough to restore it should i soft brick or something
Click to expand...
Click to collapse
Yesterday I just write but I forgot to include the thread to be translated for the instructions and the .zip file to be OTG flashed, here it is, sorry
http://www.htcmania.com/showthread.php?t=746320

Lg g2 d80220a
XxZombiePikachu said:
Well that's why you can't get recovery, kit Kat does not have ability for recovery and who knows if it ever will
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
What?! Are you sure about that? If true that is really foul. What, do they think we are Apple fans or something? If we didn't want recovery we would have bought Apple. I hope that is not true. Why would they do such think knowing you can't flash if you they do that. I'm addicted to custom roms...LOL! I need my fix now!!
---------- Post added at 08:50 PM ---------- Previous post was at 08:44 PM ----------
pmorales said:
Yesterday I just write but I forgot to include the thread to be translated for the instructions and the .zip file to be OTG flashed, here it is, sorry
It is in Spanish. Just trying working with that on your beautiful phone as a noobie...hahahaha! Thanks though.
Click to expand...
Click to collapse

notanymore said:
What?! Are you sure about that? If true that is really foul. What, do they think we are Apple fans or something? If we didn't want recovery we would have bought Apple. I hope that is not true. Why would they do such think knowing you can't flash if you they do that. I'm addicted to custom roms...LOL! I need my fix now!!
Click to expand...
Click to collapse
Well the exploit we were using to install recovery/Loki was patched in kk so currently if you want recovery it's the same procedure for all devices downgrade to 4.2(first firmware available) root install recovery and depending on your device I can link you a modified kk that uses the aboot from 4.2 plus modified kk kernel to boot to kk while retaining root/recovery
Sent from my LG-D800 running stock kk, rooted with philz using XDA app

Lg g2 d80220a
XxZombiePikachu said:
Well the exploit we were using to install recovery/Loki was patched in kk so currently if you want recovery it's the same procedure for all devices downgrade to 4.2(first firmware available) root install recovery and depending on your device I can link you a modified kk that uses the aboot from 4.2 plus modified kk kernel to boot to kk while retaining root/recovery
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
I don't know if I have the skills to pull that off. I could wind up like busted25 and all the others who bricked. I think my best option might be to sell it very cheap quickly and order a new one and never upgrade. I'll take the hit. Phone is less than a week old. One thing I'm not understanding though is I'm seeing only kitkat custom roms for this phone out there. That's why I thought it was ok to upgrade. I didn't see any 4.2.2. Everybody who flashed the custom roms must have been fairly or very skilled.One thing that made me upset is ROM Manager advertised recovery for this phone that was bogus. I even paid for the touch version and got nothing and no email reply