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.....

What a freakin mess....

So last night I decided (against my better judgment) to install TWRP recovery and flash the OTA. I did it, then had trouble rooting it. I decided to just say screw it and then restore my Nandroid backup (which I made like a good boy). Then I got a failed message on the restore. Booted back up to a fresh boot. Brand new "please select your language" .. Wtf? So then I went back to TWRP wiped everything tried to restore again. Now... Fail. So now I can't boot up because I wiped my ROM and I'm freaking stuck all over this 4.3 update. Really?
So now I will try to wait until WUGS toolkit gets updated and see if I can use it to flash a stock 4.3 image to the device then root it. I don't know if i can even use that toolkit if I don't have a ROM on the device. Anyone had experience with such a cluster and have advice? Any thoughts on why the nandroid didn't restore?
:banghead:
Sent from my Nexus 7 using xda app-developers app

Start again, using the 4.3 factory image, and do it MANUALLY - none of this BS toolkit rubbish

EddyOS said:
Start again, using the 4.3 factory image, and do it MANUALLY - none of this BS toolkit rubbish
Click to expand...
Click to collapse
I haven't had any trouble with the toolkits personally and Wugs kit is very nice and easy to use. This whole mess does not stem from the use of a toolkit. Really something screwed up with TWRP I just don't know what caused it.
Sent from my Nexus 7 using xda app-developers app

Here's a guide made by me... It's really straight forward. And no waiting for toolkits
https://www.youtube.com/watch?v=uO7HkTrRzwM&feature=youtube_gdata_player
Sent from my Nexus 4 using Tapatalk 4 Beta

italia0101 said:
Here's a guide made by me... It's really straight forward. And no waiting for toolkits
https://www.youtube.com/watch?v=uO7HkTrRzwM&feature=youtube_gdata_player
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
To follow your guide do i need to be stock or can i use flash-all.bat even if i'm on sabermod and have twrp installed?

Federico_96 said:
To follow your guide do i need to be stock or can i use flash-all.bat even if i'm on sabermod and have twrp installed?
Click to expand...
Click to collapse
Yep anything you want. Doesn't matter, I was on pa and matrix
Sent from my Nexus 4 using Tapatalk 4 Beta

Well thanks. I will look forward to watching this. Again this will flash stock img, root, and unlock bootloader? And I don't have a rom on my device at all. Is that okay?
Sent from my Nexus 7 using xda app-developers app

jcnbama said:
So last night I decided (against my better judgment) to install TWRP recovery and flash the OTA. ...
Click to expand...
Click to collapse
I could tell this was going downhill after reading this first sentence. Why would you install a custom recovery in order to flash an OTA? I don't mean to offend you but you have a lot of reading to do before you continue flashing anything.
I was in the same boat and confused as hell back in my Nexus One/Galaxy Nexus days. What I've discovered after a lot of trial and error as well as A LOT of reading, is that once you become extremely familiar with using ADB and Fastboot commands you realize how unbelievably simple this stuff really is. Even soft bricks are just small hiccups that won't stress you out anymore.
Learn how to properly use ADB/Fastboot commands through terminal (in OSX) or command prompt (n Windows) and you will realize that the toolkits are silly and do exactly the same thing.
Again, I mean this in the least offensive way possible. This is coming from someone who thought he bricked his Nexus 7 and let it sit in a drawer for 5 months before finally understanding ADB/Fastboot, pulling it out of the drawer and having it back up and running within 10 minutes...
jcnbama said:
Well thanks. I will look forward to watching this. Again this will flash stock img, root, and unlock bootloader? And I don't have a rom on my device at all. Is that okay?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
This is completely OK. Follow THIS guide (just one of many) to learn how to setup your computer for ADB/Fastboot. Then follow THIS guide to learn how to flash back to completely stock. No current ROM is required on your phone to do any of this.

I swear this is a nightmare. I don't have TBU or anything. I literally have to start over. I am always VERY careful to read and make back ups that's why I use TWRP it's why I make Nandroids and this just sucks. Ugh. I have to piss and moan I don't know where to start lol. Thanks for letting me vent..
Sent from my Nexus 7 using xda app-developers app

jcnbama said:
I haven't had any trouble with the toolkits personally and Wugs kit is very nice and easy to use. This whole mess does not stem from the use of a toolkit. Really something screwed up with TWRP I just don't know what caused it.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
its not that there is trouble using root toolkits(even though there is occasionally), it the fact that you dont learn to do things the right way. and when little issues come up, the knowledge isnt there to fix things yourself. and those little minor things turn into major headaches/issues.

simms22 said:
its not that there is trouble using root toolkits(even though there is occasionally), it the fact that you dont learn to do things the right way. and when little issues come up, the knowledge isnt there to fix things yourself. and those little minor things turn into major headaches/issues.
Click to expand...
Click to collapse
Well I do understand that point. It's a good one. I honestly don't know how to use ADB like I should. But at the same time it's a lot easier and if used properly can prevent mistakes. And good Devs make good money in donations so everyone is happy.. Lol :beer:
Sent from my Nexus 7 using xda app-developers app

How to unlock bootloader and install custom recovery TWRP 2.6.3.2 on Verizon model?

I'm sorry to bother you all, however I am having a hard time discovering first off how to unlock the bootloader on my Verizon LG G2. I'm pretty illiterate but I enjoy tweaking all my devices and finding ways to make them perform more efficiently and although I love the phone it is not blowing me away. In its current state, it's a very fast phone but LGs software is poorly designed in my opinion so when it glitches constantly at least it gets through the glitch quickly, if you can make sense of that. Anyway I have downloaded the newest android SDK, and the XDA recommended version of TWRP. Now what? Can anyone lead me in the right direction?

Bootloader cannot be unlocked, at least not yet.
Sent from my Nexus 10 using XDA Premium HD app

bradleyyy said:
I'm sorry to bother you all, however I am having a hard time discovering first off how to unlock the bootloader on my Verizon LG G2. I'm pretty illiterate but I enjoy tweaking all my devices and finding ways to make them perform more efficiently and although I love the phone it is not blowing me away. In its current state, it's a very fast phone but LGs software is poorly designed in my opinion so when it glitches constantly at least it gets through the glitch quickly, if you can make sense of that. Anyway I have downloaded the newest android SDK, and the XDA recommended version of TWRP. Now what? Can anyone lead me in the right direction?
Click to expand...
Click to collapse
You can follow this guide for installing TWRP on the vzw model. http://forum.xda-developers.com/showthread.php?t=2449670 I used it this afternoon to install TWRP.
You can root with this guide: http://forum.xda-developers.com/showthread.php?t=2448887

Try clean Rom. I am running it now with no problems.
Sent from my VS980 4G using xda app-developers 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] Can you hard brick lg g2 using autorec

Im scared to download twrp using autorec because some peoples devices got bricked and others didnt. Im worried about hard bricking my device as you can restore a soft bricked one but not a hard bricked one. My device is D802

People use the term "bricked my phone" way out of context. Hard brick, soft brick, light brick. Its either a brick or its a phone.
I honestly can't think of a single post since I got this phone in October where someone achieved a brick.
If you're afraid to use auto record then try flashify.
Afraid to use that? Then push it manually via adb.
Don't want to take the time to learn how, then don't install a recovery.
There's nothing that is 100% safe, its the decision you need to make.
Sent from my Vs980 running Mahdi 4.4.4

I softbricked my phone by using the wrong phone model version of autorec. Only had fast boot.
But fast boot is enough. Back and fixed after wasting a few hours.
Sent from my LG-D801 using XDA Free mobile app

Ahilliard, please take note of what lawlrus said. It's either a brick or not. There are no part bricks.
Thanks.
Sent from my LG-V500 using XDA Premium 4 mobile app

I updated TWRP to version 2.7 on my D801 variant DRUNK last night. I hardly remember doing it..... That's how easy Autorec is to use. I had never used the app before in my life.... Just sayin. It would be hard to mess that up.... :beer:
Sent from my LG-D801 using XDA Free mobile app

^
:laugh:

Thanks alot for the help i successfully downloaded twrp using autorec. I was just really scared because im not an expert in recovering bricked devices. Now im thinking of downloading the sokp rom

ahilliard said:
I softbricked my phone by using the wrong phone model version of autorec. Only had fast boot.
But fast boot is enough. Back and fixed after wasting a few hours.
Sent from my LG-D801 using XDA Free mobile app
Click to expand...
Click to collapse
hello i have the same pronlem how dd you fixed the fastboot pronlem i have a sprint lg g2 32gb

Abu7500 said:
Im scared to download twrp using autorec because some peoples devices got bricked and others didnt. Im worried about hard bricking my device as you can restore a soft bricked one but not a hard bricked one. My device is D802
Click to expand...
Click to collapse
yes there is a chance to soft brick with autorec only when you do not pay attention and download the wrong version, as long as you pay attention and use the correct version of autorec then there is nothing to worry about, if you are afraid of bricking in any case then make sure to read and research as much as possible before doing anything
Lawlrus said:
People use the term "bricked my phone" way out of context. Hard brick, soft brick, light brick. Its either a brick or its a phone.
I honestly can't think of a single post since I got this phone in October where someone achieved a brick.
If you're afraid to use auto record then try flashify.
Afraid to use that? Then push it manually via adb.
Don't want to take the time to learn how, then don't install a recovery.
There's nothing that is 100% safe, its the decision you need to make.
Sent from my Vs980 running Mahdi 4.4.4
Click to expand...
Click to collapse
that is actually not correct the term birck is used differently because there are two types of bricks:
soft brick- a soft brick is when something happens and a part of the device is inaccessible, for the lg g2 some possible soft bricks/hard bricks are as follows:
-broken download mode you can boot phone and use the android roms currently installed but you cannot enter download mode so cannot restore to stock and usually need to fix using fastboot
-flashing the wrong kernel on your g2 but it is still a g2 kernel results in soft brick and it needs to be fixed using fastboot
hard brick:
-flashing a kernel not meant for the g2 results in black screen which is not recoverable not with fastboot and not with qhusb_bulk mode and Ubuntu
-qhusb_bulk mode is a pretty tricky place to be in with the g2 sometimes it is recoverable but sometimes it results in hard brick
-do not recommend a member to use flashify on the g2 especially if they are on kitkat it will result in a soft brick/hard brick depending on what they flash
so a brick is not just a brick there is a difference, if not everyone who soft bricked would not be able to recover and everyone who hard bricked would be able to recover

great news
ahilliard said:
I softbricked my phone by using the wrong phone model version of autorec. Only had fast boot.
But fast boot is enough. Back and fixed after wasting a few hours.
Sent from my LG-D801 using XDA Free mobile app
Click to expand...
Click to collapse
Good to read you managed to do it after using the wrong verson of autorec. Please share the procedure as I am using the same model. Here is my situation... I bet you were in the same soup. http://forum.xda-developers.com/lg-g2/help/fastboot-mode-download-mode-bricked-t2845921
I believe william98 is in the same situation as well. http://forum.xda-developers.com/sprint-g2/help/qfastboot-mode-installing-autorec-lg-g2-t2836021
If anyone else know the procedure please help!! Can't stand another day without my cell.

I just bricked mine and its frustrating so can u please share how u got yours working again
Sent from my LG-D803 using XDA Free mobile app