Database Develop

[BRICKED] I managed to brick my N4 just 12hours after purchase

Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Now, I'm not creating this topic to moan about it, I'm fully aware that bricking is a possibility for every flash, and the phone is already sent back to LG. I just want to tell you all what I did, so we can, possibly, find what I did wrong and help other people to avoid it :highfive:. And a little bit of background, I got Gnex for a year, before that is a G1, with flashing almost become a daily job (not so with the Gnex, as I prefer the stock experience, but still a lot of rom switching and kernel flashing every few months).
My N4, right of the bat, I put it into fastboot unlock, root (the usual thingies). It's still working as normal, but the battery life is not so stellar, so I decided to try franco's kernel. I flashed r53 to my phone, it boot up normally, I feel the performance is too slow compare to stock, so I flashed the latest test version r61, too. It's still working without a hitch, abeit not as smooth as stock.
So I decided to get back to stock. I'm too lazy to do fastboot with stock image, so I download the stock kernel CWM package from this topic, and just to be safe, I flashed faux's kernel reset from here before that. The flashing was succeed, no error, but when I reboot, the phone failed to boot up, just black screen. If I plug it into my computer, it show up as qhsusb_dload, which is a telltale sign of a corrupt internal memory aka definite brick.
To put it short, the sequel is: stock -> unlock -> root -> franco r53 -> franco r61 -> faux reset -> stock kernel flash -> brick.
I guess I did something wrong between the faux reset and stock kernel flashing. can anyone tell me what I did wrong? I did happen to flash wrong kernel build on my Gnex before but the worst I got is a boot loop, not straight up brick like this. And I'm very surprised that a core part of the phone (fastboot) can be corrupted that easy.
And, flash safely :good:

interesting, ive been having problems with my kernel, and used faux reset plenty of times. hopefully someone can chime in for you. Mine is still up and running with faux kernel too

I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2

italia0101 said:
I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I swear you are a complete moron.
As for the OP's problem download nexus tool kit , Put the phone in bootloader mode and flash stock factory image.

italia0101 said:
I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Are u serious Every phone has a chance of that alot of times
Soon To Be A Nexie

berz said:
I swear you are a complete moron.
As for the OP's problem download nexus tool kit , Put the phone in bootloader mode and flash stock factory image.
Click to expand...
Click to collapse
Yea ... im a complete moron.. iv not seen this " red light " problem with any other Nexus device, have you? of course i know theres a chance of bricking with anything , but iv never seen a nexus device die so easily just by running a benchmark ?!? thats all im saying
i know this isnt the problem the op is having , but its just strange..
either way , maybe chill out a bit before you start pulling out the names yea...

I want to chime in ^_^
I think the kernel reset screwed everything up IMO. I think there was maybe some left over files on the ram disk that didn't get wiped out 100% (I'm assuming you didn't wipe completely, regardless of a kernel reset) and when you flashed stock kernel it couldn't rearrange them correctly and you ended up with a bricked device.
Just my thoughts.
Sent from my Nexus 4 using xda app-developers app

when going back to stock just flash the factory image. it is very easy once you have the files and learn how to do it and always work,

juliano_q said:
when going back to stock just flash the factory image. it is very easy once you have the files and learn how to do it and always work,
Click to expand...
Click to collapse
Bricking Nexus? lol? this is a joke? just reinstall the stock firmware and you're done.
as long as u didnt fscked up the bootloader or the partition scheme then you shall be not affraid and its fairly easy to recover.
Adam

Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium

AdamLange said:
Bricking Nexus? lol? this is a joke? just reinstall the stock firmware and you're done.
as long as u didnt fscked up the bootloader or the partition scheme then you shall be not affraid and its fairly easy to recover.
Adam
Click to expand...
Click to collapse
I still dont have my N4 but I always thought this. Coming from previous devices the only reason Ive seen a true brick is someone screwing up flashing radios or dicking with the boot-loader. I didn't think you could actually brick a device with ROMS/Kernels.

linh1987 said:
Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Click to expand...
Click to collapse
Power off. Hold "volume down" and press power button. This should get you to the bootloader. If it does, your phone is not bricked and there's loads of info on here to put it right again (stock factory image would be my first call here). If it doesn't work, I'd be tempted to remove the battery (IIRC, quite easy once you remove the screws at the bottom) and repeat the above instructions. (if you can get to the bootloader one way or another, your phone is most certainly not bricked!)
If this doesn't work, it's probably dead and you'll need to send back.
Daern
---------- Post added at 01:34 PM ---------- Previous post was at 01:27 PM ----------
berz said:
I swear you are a complete moron.
Click to expand...
Click to collapse
Didn't your mother ever teach you - "If you can't say anything nice, say nothing at all"?
This is not a site for trolling. Please go away.

I flashed different kernels many many times.
Never a problem.
OP should check for human error instead of blaming the device.
Sent from my Nexus 4 using xda premium

atulalvenkar said:
Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium
Click to expand...
Click to collapse
Sorry but i don't know what are you talking about ? what the same ID as bootloader? erm?
partition name in case of bootloader is bootloader, for case of kernel is boot
Adam

linh1987 said:
Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Now, I'm not creating this topic to moan about it, I'm fully aware that bricking is a possibility for every flash, and the phone is already sent back to LG. I just want to tell you all what I did, so we can, possibly, find what I did wrong and help other people to avoid it :highfive:. And a little bit of background, I got Gnex for a year, before that is a G1, with flashing almost become a daily job (not so with the Gnex, as I prefer the stock experience, but still a lot of rom switching and kernel flashing every few months).
My N4, right of the bat, I put it into fastboot unlock, root (the usual thingies). It's still working as normal, but the battery life is not so stellar, so I decided to try franco's kernel. I flashed r53 to my phone, it boot up normally, I feel the performance is too slow compare to stock, so I flashed the latest test version r61, too. It's still working without a hitch, abeit not as smooth as stock.
So I decided to get back to stock. I'm too lazy to do fastboot with stock image, so I download the stock kernel CWM package from this topic, and just to be safe, I flashed faux's kernel reset from here before that. The flashing was succeed, no error, but when I reboot, the phone failed to boot up, just black screen. If I plug it into my computer, it show up as qhsusb_dload, which is a telltale sign of a corrupt internal memory aka definite brick.
To put it short, the sequel is: stock -> unlock -> root -> franco r53 -> franco r61 -> faux reset -> stock kernel flash -> brick.
I guess I did something wrong between the faux reset and stock kernel flashing. can anyone tell me what I did wrong? I did happen to flash wrong kernel build on my Gnex before but the worst I got is a boot loop, not straight up brick like this. And I'm very surprised that a core part of the phone (fastboot) can be corrupted that easy.
And, flash safely :good:
Click to expand...
Click to collapse
If you took the same amount of time to search that you took to write this terrible OP you would have already fixed your phone....

tweaked said:
If you took the same amount of time to search that you took to write this terrible OP you would have already fixed your phone....
Click to expand...
Click to collapse
Hey tweaked, thanks for your contribution, but if you take 5 secs to search for a black screen issue with qhsusb_dload show up in windows, you will know that I went to a dead end.
@all: yes it's 100% my fault, I just double check and I DID flash grouper (aka N7) kernel to my N4, but I just feel it's so much easier to flash N7 kernel to N4 without any error. And again, I just want to repeat that I'm not moaning about it, it's totally my fault. I just want to help other people to avoid it :highfive:

atulalvenkar said:
Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium
Click to expand...
Click to collapse
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day

linh1987 said:
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day
Click to expand...
Click to collapse
You are the first person I heard that flashed a wrong KERNEL.
Congratz.
Sent from my Nexus 4 using xda premium

linh1987 said:
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day
Click to expand...
Click to collapse
Saw couple of posts on reddit where many people did the same thing. The problem is franco develops for both N7 and N4 and his XDA thread subject doesn't have any indication of the device. Because of this it's easy to get pointed to the wrong thread and download wrong kernel.

My phone bricked spontaneously. I had installed CM 10.1, with the stock kernel, about 12 hours earlier and was actually browsing facebook when the phone spontaneously rebooted. I could get into fastboot, but no matter what I tried, I couldn't flash a stable recovery or full image. Constant boot loops with the occasional successful system boot, only to reboot within a few seconds.. starting the whole process over again.
Flashed and formatted every accessible partition, followed every "how to" I could find. Absolutely no success. Luckily Google sent me a replacement and I had a new phone in 2 days. Running the same CM 10.1/stock kernel now, no issues.
My first phone (a Rev_11) always ran somewhat hot, and the battery wouldn't last a day. The replacement phone (also a Rev_11) runs much cooler and the battery lasts for 2 days easy, with the exact same software. I'm thinking the old phone just somehow toasted itself. Just speculation. Oh, the old phone was also a "slow" binned CPU.
Anyway, the point of my story is that is ISN'T entirely true that the ability to boot into bootloader/fastboot will guarantee you success when trying to resurrect a dead phone.

[Q] Samsung Galaxy S GT-i9000 freezes after around 30 seconds from reboot.

Hello everyone, thanks for taking your time and reading this.
I've owned a Samsung Galaxy S GT-i9000 for about two years now. This phone is not my primary phone, as I just use it as a secondary phone for different apps/backup, most of the times the phone is turned off.
But a few days ago, I turned the phone on, and once the homescreen had loaded, around 20-30 seconds later, the phone will freeze, and there's nothing else you can do other than take the battery out to turn it off.
A few details about the phone: the phone has never been flashed, and the OS has never been touched. It's basically at stock, but the only thing I remember is updating the official firmware through the Samsung link in the settings. The phone has never been modded, and that's what bugs me the most. (I've never had experience with 'modding' phones with custom ROMS and such)
So, after sitting at home all day looking for a fix, I couldn't find anyone else in my situation. There are a few similar situations, but I am yet to find something that replicates my problem exactly.
I've also tried rebooting the phone in many different ways, for example, taking out the memory card, then taking out the sim card, then taking them both out completely.
That's when I found a link which gave me information on how to factory reset the device. Since nothing else was working, I decided to go for it.
I held the VOLUME UP button + the HOME button, and hit the power button and got the menu up.
The menu works fine, I was flicking through the options for 10 whole minutes just to check if it freezes or not, and it works perfectly fine.
So then I factory reset the phone, wiped the system cache, and I also formatted the internal SD card.
Still, the problem persists. This time, the phone will reboot for a little while longer, since I expect the system files are getting set up, then it asks for the language, and before I can hit English, it freezes, and the screen stays like that until the battery is dead. All the hardware buttons don't do anything, it's basically fully dead with the screen still on the OS menu.
I was wondering if anyone knows what I should do?
I can provide more information if needed, and I can even upload a video to YouTube if you want a better aspect of the problem.
Any help is appreciated, thanks.

is it i9000 or 9100?
Sent from my GT-I9000 using xda premium

compacity said:
is it i9000 or 9100?
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Ah, sorry, got the title completely messed up there.
Yes it's the GT-i9000 and I think it had Froyo 2.2.1, forgot to include that in the main text.

Could try Rooting the phone and wiping all options in Recovery and Reboot
or
Could be that something maybe corrupted which is halting the system
Upload a video so that we can offer better advice
Which Rom / Firmware are you using?
Last option.
Would Recommend Downloading Rom (whichever you choose) and go from there....

Major UPDATE:
Okay, so after sticking at it the whole day and trying to get a better understanding of this situation, I've managed to work around the problem slightly. It's not fixed yet, though.
So after the screen had frozen for the (insert number here)th time, the battery was starting to go empty, so I stuck it on charge, but I forgot that I had left the frozen screen on (currently frozen on the 'Language Select' set up menu).
After about 20 minutes, the phone vibrated and a little message popped up, and it said that 'the process Soundhound.com.xxx.xxx was force closed', or something along the lines. I can't remember fully because it popped up for only around 4 seconds and disappeared.
As soon as I saw that, I quickly went to the application settings and deleted all of the soundhound cache/data and then removed the app completely. After that I thought it was fixed for sure, so I was messing around with the phone and using different apps to see if it freezes again, and it didn't.
But I had to restart the phone to see if the freeze issues happened again, and yep, it was there again, this time the same as the first issue, where it used to freeze up in the home screen. AND, I let it sit on the frozen screen for 15 minutes and it was that SAME soundhound app that got force closed, so once it got out of the frozen state, I quickly went to the application settings and the app was still there, it was like I didn't even delete it?
This leads to my new problem, the so called 'hard factory wipe/reset' doesn't actually reset EVERYTHING. As seen in my other post: http://forum.xda-developers.com/showthread.php?t=2305825
Now I'm completely confused as to what I should do.
I've pretty much tried everything, and i'm sure a FULL hard reset where EVERYTHING gets wiped out might just fix it? The thing is though, I don't know how? I've been trying to fix this phone for about 7 hours straight now.

My opinion Flash a Stock Rom or what ever you wish and then Root it...
If selling it just dont bother with Rooting it.
As you say you have been at it for Several hours and flashing takes less than an hour even for a newbie if following the procedure correctly
As going by what you say it seems that files are messed up on the phone and better to start fresh

ywasaf acquitted
EwOkie said:
My opinion Flash a Stock Rom or what ever you wish and then Root it...
If selling it just dont bother with Rooting it.
As you say you have been at it for Several hours and flashing takes less than an hour even for a newbie if following the procedure correctly
As going by what you say it seems that files are messed up on the phone and better to start fresh
Click to expand...
Click to collapse
Is there a legit way to flash it, maybe through Samsungs website? I don't want to mess around with custom files, as I would like to keep everything clean.
Oh, and also, I just went through the media files and found some of my old pictures too. So for some reason, the 'format internal SD' option in the recovery menu isn't working.
If I flash it, will I have to flash it to Froyo 2.2.1 which it is currently in right now?
Here's information I found on the 'About phone' menu:
Kernel version:
2.6.32.9
[email protected] # 1
Build number:
FROYO.XXJPY
Baseband version:
i9000XXJPY
Thanks for all the help so far.

Legit way your on XDA!
Flash a Stock 2.3.6 (Clean) which is the same as Samsung Site its in my How to Guide if you wish to follow it
Its the exact same Rom just not on there Site

EwOkie said:
Legit way your on XDA!
Flash a Stock 2.3.6 (Clean) which is the same as Samsung Site its in my How to Guide if you wish to follow it
Its the exact same Rom just not on there Site
Click to expand...
Click to collapse
Thanks.
Briefly read your guide, and it's all mind boggling to a newbie like me :silly: lol
I might just have to flash it, because this problem is getting a little bit annoying now.
Which parts of your guide should I follow exactly? And shouldn't I be sticking Froyo 2.2.1 back in? Won't a newer firmware (such as the 2.3.6) make the phone slower/drain more battery than usual?
Oh and one last thing, what's the difference between rooting and flashing a phone? Cheers.

Rooting briefly means :
Giving yourself root access to system files and the ability to change things that normally are marked read only
This allows you to change all kinds of things that normally you wouldn't be able to
Flashing : Erm.. Flashing a new Rom on your Phone or the process of over-writing your internal memory
2.3.6 will be ok for you if you wish to stay just Stock on your phone.
Plus the fact if you wish to move to another Rom later on its just a matter of Rooting the Phone and installing the Custom Rom
Just follow guide from the : HOW TO GUIDE : TUTORIAL TO FLASH 2.3.6 JVU + ROOT BEFORE INSTALLING CUSTOM ROM
and you will be ok.

EwOkie said:
Rooting briefly means :
Giving yourself root access to system files and the ability to change things that normally are marked read only
This allows you to change all kinds of things that normally you wouldn't be able to
Flashing : Erm.. Flashing a new Rom on your Phone or the process of over-writing your internal memory
2.3.6 will be ok for you if you wish to stay just Stock on your phone.
Plus the fact if you wish to move to another Rom later on its just a matter of Rooting the Phone and installing the Custom Rom
Just follow guide from the : HOW TO GUIDE : TUTORIAL TO FLASH 2.3.6 JVU + ROOT BEFORE INSTALLING CUSTOM ROM
and you will be ok.
Click to expand...
Click to collapse
So the 2.3.6 Firmware you provide, is that known a 'custom firmware'?
I've been searching for YouTube videos with people explaining how to flash, but all the videos sound like they're speaking about some rocket science sh** lol
Now I'm super confused, some guy on YouTube is flashing to 2.3.6 JVT while you're doing JVU, I don't even know what that means haha
I just don't want to brick the phone and make it completely dead, that's why I'm just making sure I understand the basics before I go ahead with it, sorry if I'm starting to sound annoying lol

You wont brick it if you follow it correctly...
2.3.6 JVU is the basis for all custom roms been flashed unless stated otherwise by Rom Developers.
As its basically a stock 2.3.6 then when you want to flash another Rom its just a matter of Rooting the 2.3.6

EwOkie said:
You wont brick it if you follow it correctly...
2.3.6 JVU is the basis for all custom roms been flashed unless stated otherwise by Rom Developers.
As its basically a stock 2.3.6 then when you want to flash another Rom its just a matter of Rooting the 2.3.6
Click to expand...
Click to collapse
Ah, okay.
Well, I'm in the process of downloading your files, THANKS for ALL the help you've given so far, sir!
I'll flash once all the files are downloaded. By the way, does 2.3.6 have Google Play store, and not the old Andropid Market?
I hope I can get this done before I head off to sleep in a few hours, been a very long day haha
I'll let you know of the results, cheers and have a good day sir.

No problem hope it all works out for you :good:
Not sure if Google Play is on it as its 2.3.6 Stock ...just upgrade it if possible

EwOkie said:
No problem hope it all works out for you :good:
Not sure if Google Play is on it as its 2.3.6 Stock ...just upgrade it if possible
Click to expand...
Click to collapse
why is it i cant see ur online status? is my app ...... nevermind that.
Sent from my GT-I9000 using xda premium
---------- Post added at 05:14 AM ---------- Previous post was at 05:13 AM ----------
f2k8 said:
Ah, okay.
Well, I'm in the process of downloading your files, THANKS for ALL the help you've given so far, sir!
I'll flash once all the files are downloaded. By the way, does 2.3.6 have Google Play store, and not the old Andropid Market?
I hope I can get this done before I head off to sleep in a few hours, been a very long day haha
I'll let you know of the results, cheers and have a good day sir.
Click to expand...
Click to collapse
GOOD LUCK N MAY LADY LUCK ON UR SIDE WHILE FLASHING
Sent from my GT-I9000 using xda premium

EwOkie said:
No problem hope it all works out for you :good:
Not sure if Google Play is on it as its 2.3.6 Stock ...just upgrade it if possible
Click to expand...
Click to collapse
Back again, haha.
I was just wondering, did you say I should root or not? As rooting it seems like a bit of a hassle? Plus, it says that I should install a custom rom zip file if I decide to root it, but I don't have one? I am using your 2.3.6 which was in your Odin Files download link, right?
So if I root, what do I do exactly?

compacity said:
why is it i cant see ur online status? is my app ...... nevermind that.
Click to expand...
Click to collapse
Hiding from the Tax Man :laugh:
Rooting takes 15 seconds to do

EwOkie said:
Hiding from the Tax Man :laugh:
Rooting takes 15 seconds to do
Click to expand...
Click to collapse
Okay, so I've rooted it also now, and unplugged the USB.
Now it's restarted, and the language set-up page is there, and guess what? .. It froze again :|
Exactly the same way before I flashed it :crying: :crying: lol
I actually feel like crying right now haha, I think the phone may be completely dead? Something is seriously corrupt with it I'm guessing?
I've never dropped it, or accidentally dropped liquid on it or anything like that.
I have absolutely no idea what to do now. Sigh.
Thanks for your help either way though.

can you upload a video on whats happening?

EwOkie said:
can you upload a video on whats happening?
Click to expand...
Click to collapse
how bout activate repartition?
Sent from my GT-I9000 using xda premium
---------- Post added at 05:49 AM ---------- Previous post was at 05:48 AM ----------
EwOkie said:
Hiding from the Tax Man :laugh:
Rooting takes 15 seconds to do
Click to expand...
Click to collapse
so thats why, i thought my app got error.
Sent from my GT-I9000 using xda premium

[Q] Whoops... Wiped System. Mayday!

Good Evening XDA Note 4 Devs/Users,
The Bad News;
I seem to have gotten myself into a pickle. and, Hopefully.. one that isn't permanent.
So, I was planning on reinstalling Firekat 4.4.4 after being on CM12 (Lolipop) Remix. everything went super till I went to wipe my data/cache. In the process of being yelled at by two people and in the stress of it all I accidentally wiped the system data too. Which, seems to have deleted just about everything.. including the original backup of my device, the two ROMS and the system OS. The phone is also claiming not to be rooted now and TWRP seems to have been deleted too. The only thing I can really do is boot into download mode which ODIN keeps refusing to detect. and, Windows 8.1 keeps thinking the phone is a Banana.
The Good News;
I May have a Backup of the Original Unrooted TMO KitKat stored on my Laptop from ODIN.
I May Be able to push the Unrooted ROM by ADB / ODIN
I can boot into Download mode.
So, knowing my predicament and knowing I screwed up. Any advice or help from here to get the device working again?
Also, I promise not to try and turn the phone into a brick again. :good:
Thank you in Advance! :highfive:

Odin

follow this http://forum.xda-developers.com/not...sy-steps-stock-odin-n910tuvu1anih-cf-t2903733

I'm on FK, I always wipe everything. As long as my Zip (for install) is on the external SD card, I'm good. So what's wrong?
As for not having TWRP, I would also just Odin to stock, reinstall it. Should be an easy fix.

madmike23 said:
I'm on FK, I always wipe everything. As long as my Zip (for install) is on the external SD card, I'm good. So what's wrong?
As for not having TWRP, I would also just Odin to stock, reinstall it. Should be an easy fix.
Click to expand...
Click to collapse
I came from a phone that if you end up deleting everything like this. You bricked the device completely with it not even turning on. (Older android phone). So, Naturally. I thought I had screwed myself with it. lol
I did fix it though right after I posted the thread. I managed to get one of the rom's to flash through odin. (so, I guess I did not accidentally unroot it). I think I Love Samsung phones now that I can accidentally brick it and then still get myself out of trouble with the help of you all

I dont know anyone who has bricked a samsung in a while. Odin is great. Only mess up would be if you delete pit file

BACARDILIMON said:
I dont know anyone who has bricked a samsung in a while. Odin is great. Only mess up would be if you delete pit file
Click to expand...
Click to collapse
I regret to say this is my first Samsung device.. was a Motorola and HTC fanboy before both which I bricked one way or the other..

BACARDILIMON said:
I dont know anyone who has bricked a samsung in a while.
Click to expand...
Click to collapse
I would still be careful. I managed to brick my Note 3 so hard that JTAG couldn't bring it back to life. They are easy to recover from soft bricks, but they aren't invincible...

Face_Plant said:
I would still be careful. I managed to brick my Note 3 so hard that JTAG couldn't bring it back to life. They are easy to recover from soft bricks, but they aren't invincible...
Click to expand...
Click to collapse
Really. I was working on 3 phones and flashed the wrong rom on my note 3. It was from a totally different phone. Took 6 hours to bring back to life. Odin would install a part then fail so just kept pushing and wiping and finally went in. I was mad as hell since i qas going on vacation the next day. Lol.

BACARDILIMON said:
Really. I was working on 3 phones and flashed the wrong rom on my note 3. It was from a totally different phone. Took 6 hours to bring back to life. Odin would install a part then fail so just kept pushing and wiping and finally went in. I was mad as hell since i qas going on vacation the next day. Lol.
Click to expand...
Click to collapse
I couldn't get into download mode. The phone was completely unresponsive to all button combos and my laptop. I tried a USB jig, an unbrick image flashed on an SD card, yelling at it, and sending it off for JTAG but nothing could bring it back. I was quite sad because I had a lot of good memories with that phone, but my Note 4 fills the void nicely.

Hi
I managed to get in trouble with note 3...I have listed my entire trial & error here, can someone please help me bring this phone back to life.
http://forum.xda-developers.com/gal...ed-samsung-note-3-n9005-t3058408/post59580154

I really messed my new phone up.

Just got a new Verizon Nexus 6. Never rooted or messed with android in my life. I installed Android M on it (with hours of frustration) and then was following a guide to root it while being on Android M. Somehow I deleted EVERYTHING on the phone, it says the phone is corrupt and wont start when I try to turn it on. (I have Team Win Recovery Project v2.8.7.1) How can I fix this ASAP? Have no idea how. I just need a working phone. Please help thanks!

If you can boot into TWRP just download a ROM and push it to the device and flash it. If you can get into bootloader you can flash a factory image to fix.
If you've never rooted, let alone even used Android, why the hell are you installing a dev preview onto your device? Guess you found out the hard way. Just saying....
Sent from my Nexus 6 using Tapatalk

Highway 55 said:
If you can boot into TWRP just download a ROM and push it to the device and flash it. If you can get into bootloader you can flash a factory image to fix.
If you've never rooted, let alone even used Android, why the hell are you installing a dev preview onto your device? Guess you found out the hard way. Just saying....
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah I agree. I need some one with skype to walk me though it. I literally followed step by step guides on youtube without knowing what I was doing, it was my fault.

Did you ever figure it out. I have no problem walking you through it. Just shoot me a pm and we can go from there.
Nick

I hope everything turns out okay and you get your phone working again. I would Skype with you but I'm on dad duty with my kids tonight. Good luck!
Sent from my Nexus 6 using Tapatalk

Jaimbi said:
Just got a new Verizon Nexus 6. Never rooted or messed with android in my life. I installed Android M on it (with hours of frustration) and then was following a guide to root it while being on Android M. Somehow I deleted EVERYTHING on the phone, it says the phone is corrupt and wont start when I try to turn it on. (I have Team Win Recovery Project v2.8.7.1) How can I fix this ASAP? Have no idea how. I just need a working phone. Please help thanks!
Click to expand...
Click to collapse
That was your mistake. If never messed with Android worst thing you could do is jump right on a Beta build.
---------- Post added at 08:14 PM ---------- Previous post was at 08:08 PM ----------
Easy to fix if unlocked and have TWRP. Recommend going to stable build first and work your way up. At least will have a working phone. Make a backup up stable build and then play all you want. Could have made backup of stock before even flashed M and would have been golden.

What did you do when you got the corrupt message? I'm asking because many people get this message but if you ignore it, it should boot up anyway.

slosrtnick said:
Did you ever figure it out. I have no problem walking you through it. Just shoot me a pm and we can go from there.
Nick
Click to expand...
Click to collapse
yeah I got it! i watched a video on re-flashing M? I think? It works now, I'm still not sure how to back up my stuff properly but I have a working phone! Thanks for the reply!

Jaimbi said:
Just got a new Verizon Nexus 6. Never rooted or messed with android in my life. I installed Android M on it (with hours of frustration) and then was following a guide to root it while being on Android M. Somehow I deleted EVERYTHING on the phone, it says the phone is corrupt and wont start when I try to turn it on. (I have Team Win Recovery Project v2.8.7.1) How can I fix this ASAP? Have no idea how. I just need a working phone. Please help thanks!
Click to expand...
Click to collapse
It sounds like all you need to do is: when you get to that "phone is corrupt" screen, press volume down and then the power button to continue.

H811 unbrick help

Hi everyone,
Please forgive any n00b questions.
I got started with rooting / custom ROMs on a Nexus 4, and I didn't realize at the time that this made things really easy and I didn't need to learn very much about how everything worked. Fast forward to last week -- I decided, at long last, that I was tired of using stock MM on my T-Mo G4 / H811. How hard could it be? Probably not much different from playing on my old Nexus 4 right? Lol, maybe not.
So now 72 hours later, my phone is hard bricked and will not enter download mode. and I need some assistance, if anyone would be so kind.
I will try to recount what I did:
To start with, I was using a Mac, so I used Homebrew to install Android platform tools / ADB.
I decided I wanted to try out LineageOS so I went ahead and followed their very clear steps (on LOS wiki) to unlock the bootloader install TWRP. However, TWRP doesn't seem to have an official build for the G4(!) so I had to look up and use one of the betas from this post. Is this where I went off the rails already? [Of course, very stupidly I also failed to make a complete backup of anything before going on ahead. Rookie mistake.]
After unlocking bootloader and flashing my TWRP beta, I was able to boot into TWRP just fine. I followed the normal prescribed steps of doing a Wipe (normal TWRP defaults -- system, cache, etc.?) before flashing the latest LOS nightly (14.1-something) and also the nano-x64 variety of gapps. I rebooted and got stuck with the LOS boot animation. I let this go for 55 minutes, so I am pretty sure it was an actual bootloop, not just the 1st-time-startup and optimization going on.
I rebooted into TWRP and decided to try a different ROM to see if that was the issue. So I wiped again, flashed another ROM (I believe it was a flavor of AOKP 14.1.x), flashed gapps again, and gave it another try. Again got stuck with an endless bootloop (45 minutes).
Since this is my daily driver, I decided to go back to stock. Found this thread, downloaded the MM-debloated zip, pushed to phone, and again Wiped + Flashed. This time, when I hit reboot, my phone was immediately hard-bricked. No startup screen, no nothing. That was quite unexpected. Also, the first time I had ever HARD bricked a device that I was playing with. Yikes!
Since then, I got a hold of a PC, and have been trying to revive the device by flashing an image to the microSD and booting into Download mode, in the form of this thread or this one.
I did get this to work briefly yesterday, or at least I got to Download Mode / Firmware Update screen, and then attempted to run LGUP with the KDZ file. However I ran into an error at about 9%, and couldn't continue -- and then I had to give back my loaner PC for the day. I also noticed that the LG Mobile Support tool was recognizing my phone NOT as an H811 but as something like HX230 or ... whatever it was, it was definitely wrong. Which is worrisome.
Today I'm giving it another try but my phone will not enter Download Mode at all, nor respond in any other way. I'm curious if this is a battery issue? So I am simply charging it for the time being. I also re-formatted the microSD and re-flashed the single .img just to be safe, but still can't get a response out of the phone. On my PC's device manager it is showing up as the common Qualcomm 9008 that a lot of people seem to have seen. No recognition from LG Mobile Support tool, nor from LGUP.
So ... what now?
It's possible that once my battery gets some charge again, maybe I'll be able to enter DL mode. Let's hope so.
However, I am also totally in the dark about which software version I should be using. 20i? 20p? I have no idea what these refer to, and I did not make any prior notes to capture the state that my phone was in before this all began. So IF I get to DL mode I will definitely need further instruction on the CORRECT KDZ FILE to be flashing. Else I will just compound my problems.
ANY tips or suggestions will be appreciated! Thanks so much.

Should have verified being on 20o firmware
Upon further reading, quite obvious, at the top of this thread, I definitely should have followed the Prerequisite steps. I did NOT verify that I was on 20o firmware. "OR RISK BRICKING YOUR DEVICE" is right.
So I bricked my device, in exactly the way I was warned not to do, it seems.
Still, what's the next step? Any thoughts?

freeradical426 said:
Upon further reading, quite obvious, at the top of this thread, I definitely should have followed the Prerequisite steps. I did NOT verify that I was on 20o firmware. "OR RISK BRICKING YOUR DEVICE" is right.
So I bricked my device, in exactly the way I was warned not to do, it seems.
Still, what's the next step? Any thoughts?
Click to expand...
Click to collapse
try search for a fix if not may be @steadfasterX knows how to help you.

Re: searching for unbrick solutions
raptorddd said:
try search for a fix if not may be @steadfasterX knows how to help you.
Click to expand...
Click to collapse
Thanks, I have been looking around for solutions, but can't seem to find anything aside from the unbrick-guides that I've already listed / already attempted.
Will hope for help from @steadfasterX ! Or some other knowledgeable / benevolent party.

freeradical426 said:
Thanks, I have been looking around for solutions, but can't seem to find anything aside from the unbrick-guides that I've already listed / already attempted.
Will hope for help from @steadfasterX ! Or some other knowledgeable / benevolent party.
Click to expand...
Click to collapse
Ok what was the last KDZ file you flashed which had worked? 20o?
As you have hard bricked your device you can try the sdcard method again if it works flash 20o again (of it it was 20o).
If you flash a lower version you will hard brick again.
If the sdcard doesn't work anymore for you you can try to flash with QFIL but beware to use the right one. If you use the wrong one it will convert your device and believe me that's not what you want. I can share the good ones but unfortunately maybe on next week first.
Otherwise search on your own for 9008 unbrick but check the md5sum of the programmer!! Compare it with the Evil one mentioned in my ARB list here: http://tinyurl.com/antirollg4 and DO NOT USE THE EVIL one..
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Ok what was the last KDZ file you flashed which had worked? 20o?
As you have hard bricked your device you can try the sdcard method again if it works flash 20o again (of it it was 20o).
If you flash a lower version you will hard brick again.
If the sdcard doesn't work anymore for you you can try to flash with QFIL but beware to use the right one. If you use the wrong one it will convert your device and believe me that's not what you want. I can share the good ones but unfortunately maybe on next week first.
Otherwise search on your own for 9008 unbrick but check the md5sum of the programmer!! Compare it with the Evil one mentioned in my ARB list here: http://tinyurl.com/antirollg4 and DO NOT USE THE EVIL one..
Click to expand...
Click to collapse
Thanks very much for the guidance! The post that you linked to REALLY helps. Until now I really was not sure what 10n, 20i, 20o, etc. referred to, aside from just various software versions. Having a definition for anti-rollback and further links to explain, really helps! This gives me more information and I might be able to self-resolve from here. I will give it a shot.
As for your question ... unfortunately there was NO instance where I flashed a working KDZ file, and I didn't know (due to my past experience with my Nexus) that I needed to check the STOCK software version of my phone before beginning to play with ROMs. In other words, I have no idea if I was on 20i, 20o, 20p, etc. From what I understand, this makes things a lot more difficult
Having looked at the linked thread just a little bit, it appears that using a 20o KDZ is the best bet -- because I bricked my device using a 20i ROM so I expect it was due to violating the anti-rollback restriction.
I will look into it more closely and come back if I hit another brick wall. Thanks so much!

If anyone cares, here are the ending results of all this ...
#1 Be wary of anti-rollback restrictions before you flash anything to your G4. You WILL brick your phone!
I tried multiple rounds and multiple variations of all the MicroSD card methods that I could find. I could NOT succeed in unbricking my phone.
#2 Luckily ... I was able to convince LG that I was still technically under warranty!
Because I had the stock bootloop issue in May 2017, LG did an in-warranty repair for me, and replaced the motherboard. So last week, I simply told them "my phone is AGAIN unable to charge and will not power on, just like in May". Since it had only been 5-6 months since the first issue, they agreed to replace the motherboard again.
Moral of the story: you can definitely unbrick your phone by having LG replace the mobo XD XD
From here, I think I will just totally avoid doing any rooting or custom ROMs on my totally-stock G4 coming today in the mail. I will cross my fingers and hope we get OEM Nougat in the USA sometime in the next couple of months.
Thanks again for the help everyone!