Database Info

Well I think I bricked her...

I only installed the software cwm recovery (not nvflash), so I have no way out now. I haven't done anything serious except flash paul's patch and use titanium to uninstall some crapware like qik, that reader software, polaris office, etc.. nothing OS related, just apps. I also removed the GPS software, so I don't know what killed it exactly.
After removing those apps with TB, everything ran fine except I kept getting a force close from Qik... so I rebooted. Now it doesn't load and freezes on the LG screen with the loading bar not moving.
I don't know of any other options at this point...

Load up nvflash and get CWM on there so you can vol down + power into it. Then wipe data/cache and reboot.
You're not bricked even tho you think you are

GideonX said:
Load up nvflash and get CWM on there so you can vol down + power into it. Then wipe data/cache and reboot.
You're not bricked even tho you think you are
Click to expand...
Click to collapse
brick means HARDWARE LOCK or SOFTWARE LOCK
if your screen turns on at all... there is hope
fallow gideonx instructions... they have a nice tut set up for Nvflash
plus a one click type thing in the development section

I'm bricked for the time being until I can get home. I'm locked out of the device manager here at work, so I can't install the nvflash driver. Ignorant sons o'....
Sometimes I really hate the IT department.
Hopefully this is a warning to everyone else that if they want a custom recovery, they should bypass the rom manager option as it's too dangerious and just do the nvflash option.

For now nvflash is a better option instead of RM.

So I got home and used nvflash to put the latest cwm recovery on it. I wiped cache and rebooted... it shutdown the phone instead. So I manually turned it back on and it did the same thing.
So I did a full wipe and flashed a rom... and now it bootloops. I may very well have a bricked device after all.

Flashed which rom?
Here's a nandroid restore you can use:
http://forum.xda-developers.com/showthread.php?t=1048274

Eagles Blood since it was the fastest available.
The stock backup image is taking a long time thanks to the slow download. It's really irritating when all I can get on my 20mbps connection is 64KB/s.

antoniouslj said:
Eagles Blood since it was the fastest available.
The stock backup image is taking a long time thanks to the slow download. It's really irritating when all I can get on my 20mbps connection is 64KB/s.
Click to expand...
Click to collapse
I'd do the nandroid restore if I were you...

antoniouslj said:
Hopefully this is a warning to everyone else that if they want a custom recovery, they should bypass the rom manager option as it's too dangerious and just do the nvflash option.
Click to expand...
Click to collapse
noone will heed that warning lol.

Not a brick bro...just a minor bump in the road..you will get wiser from this..
G2X

fcisco13 said:
Not a brick bro...just a minor bump in the road..you will get wiser from this..
G2X
Click to expand...
Click to collapse
Actually it is completely gone now... seems like I have a defective device.
It won't boot into recovery or anything for that matter now, it just freezes at the first LG screen (the one without the progress bar). What's even weirder is I haven't really done anything to it... just installed and ran apps/games. I shut it down so I could install CM, but it won't boot into recovery or anything.
I tried redoing nvflash and it went fine, but it still won't boot into recovery.
This really sucks too... right on the eve of CM for this thing.

[Q] reboot loop

My g2x keeps rebooting over and over again! This happened after i mounted it to my pc. it tries to read my sd card then just reboots over and over again. I have nv flash and tried to restore old back up but still does it. can any one help im thinking i need to flash stock.

you need to do a factory reset if your nandroid backup doesn't work. if that doesn't work reflash the rom.

I already did a factory reset and wipe and tried to re install the rom. it just continues to reboot. It starts up and if quick i can get into my lock screen and access things but within seconds it reboots and continues to do that

What rom are you using?

jcbofkc said:
What rom are you using?[/QUOTE
I was on a stock rooted rom when the problem happened. so i then i did a restore. when that didnt work i reflashed the stock rom that was posted on forum. i think it has something to do with my internal memory which i cannot access. this all happened when i was trying to back up my sd card while in usb and it just got an error when i unplugged it enless reboot.
Click to expand...
Click to collapse

I was hoping it was something simple like undervolting with a custom rom. I wish I could help. It sounds like you tried everything I would recomend. Maybe one of the real Android techie type guys can help you. I am still learning myself.

jcbofkc said:
I was hoping it was something simple like undervolting with a custom rom. I wish I could help. It sounds like you tried everything I would recomend. Maybe one of the real Android techie type guys can help you. I am still learning myself.
Click to expand...
Click to collapse
Thanks anyway! I even when as far as to re-flash stock recovery and then try to factory reset it but still did not work. I just dont know what the heck happened. So today I went to t-mobile and they r sending me a new phone and for know I have a loaner 10 days until I get the new phone they said it was backordered. oh well

[Q] Hard-Brick I535 After Restoring from Nandroid Backup?

I've looked around quite a bit, but can't find anyone who has had this problem when restoring. I was trying out Paranoid Android 3.10 D2VZW on my Galaxy SIII, and decided to go back to JellyBam 8.2.0 D2VZW. Both are 4.2.2 ROMs. I rebooted into CWM Recovery, wiped data and cache (can't remember if I wiped the Dalvik), and restored my JellyBam backup. The restore went fine, and I rebooted the system from CWM...nothing! Phone is completely black, no boot up at all. I tried the power button, a battery pull, booting into recovery, and booting into download. When I plug my phone into my computer (a Mac with Windows running in Parallels), I get QHSUSB_DLOAD. So far my research tells me this means my phone is hard-bricked. If I plug in without a battery, I get a red LED light that extinguishes after a few minutes. My understanding of hard-bricking is that it's caused by flashing ROMs not intended for my phone (i.e. an international version ROM). Why would my phone hard-brick if the last thing I did is restore a backup from a previously-working ROM built for my phone? I didn't check the md5, but if the md5 failed wouldn't the restore fail too? I literally can't do anything with my phone. No display, no Odin/download, no recovery. The only indications that it isn't completely fried are the red LED and my computer recognizing the QHSUSB_DLOAD and making a notification sound when it's connected or disconnected. I have no problem sending it to be JTAGed if need be, but I'm not 100% that it's hard-bricked. Any suggestions?

ransdell2 said:
I've looked around quite a bit, but can't find anyone who has had this problem when restoring. I was trying out Paranoid Android 3.10 D2VZW on my Galaxy SIII, and decided to go back to JellyBam 8.2.0 D2VZW. Both are 4.2.2 ROMs. I rebooted into CWM Recovery, wiped data and cache (can't remember if I wiped the Dalvik), and restored my JellyBam backup. The restore went fine, and I rebooted the system from CWM...nothing! Phone is completely black, no boot up at all. I tried the power button, a battery pull, booting into recovery, and booting into download. When I plug my phone into my computer (a Mac with Windows running in Parallels), I get QHSUSB_DLOAD. So far my research tells me this means my phone is hard-bricked. If I plug in without a battery, I get a red LED light that extinguishes after a few minutes. My understanding of hard-bricking is that it's caused by flashing ROMs not intended for my phone (i.e. an international version ROM). Why would my phone hard-brick if the last thing I did is restore a backup from a previously-working ROM built for my phone? I didn't check the md5, but if the md5 failed wouldn't the restore fail too? I literally can't do anything with my phone. No display, no Odin/download, no recovery. The only indications that it isn't completely fried are the red LED and my computer recognizing the QHSUSB_DLOAD and making a notification sound when it's connected or disconnected. I have no problem sending it to be JTAGed if need be, but I'm not 100% that it's hard-bricked. Any suggestions?
Click to expand...
Click to collapse
It's definitely hard bricked, whatever happened is very strange though, as a nandroid doesn't usually mess up your boot partition.
Flashing a rom not intended for your phone can cause a hard brick, but that's not the only way it can happen. Somewhere in the restore process your boot partition got corrupted. Your base coding somehow is not being recognized, and your computer and phone can't tell what's supposed to run. A jtag is really your only option.
TWRP offers you the option to disable the boot and recovery partition when restoring. After you fix your phone, I'd recommend trying that out so you're absolutely sure your boot partition doesn't get touched. Those really don't need to be restored anyway.
Sorry that happened to you.
Sent from my SCH-I535 using Tapatalk 2

Bummer. Thanks for the input. I kinda figured that was the case, but was hoping I was missing something. Guess I'm going to have it JTAGed, probably by Mobile Tech Videos. The process looks fairly simple. If the equipment costs were comparable to having someone else do it I might do it myself, but if that were the case everyone else would be doing that too! I'll let you know how it goes.

ransdell2 said:
Bummer. Thanks for the input. I kinda figured that was the case, but was hoping I was missing something. Guess I'm going to have it JTAGed, probably by Mobile Tech Videos. The process looks fairly simple. If the equipment costs were comparable to having someone else do it I might do it myself, but if that were the case everyone else would be doing that too! I'll let you know how it goes.
Click to expand...
Click to collapse
I think the price is reasonable if you factor in equipment and labor.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
I think the price is reasonable if you factor in equipment and labor.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Got my phone JTAGed by Patrick Walls (whose service is available on eBay for ~$35), and it works great. Fast service and great communication from Patrick. The phone came back unrooted with a stock 4.1.2 ROM. Of course I immediately re-rooted it and flashed a fresh JellyBAM ROM to it (with a huge feeling of trepidation), and so far everything is working, with the exception of the camera (I get "Can't connect to camera" after taking one picture, and a reboot is the only thing that enables the camera again, for one pictures, then can't connect, reboot, one pic, can't connect, etc.).
Having never hard-bricked before after many, many ROM changes on a Fascinate and about 10 ROM changes on my S3, I'm a little nervous about changing them now. Is my hesitation unfounded providing I don't mess with the bootchain? To root my phone I flashed the VRALEC bootchain, then TWRP, then rooted, then JellyBAM, then the VRBMD3 bootchain, as per this rooting guide:
http://forum.xda-developers.com/showthread.php?t=2046439
Now that I've put my phone back to the Jelly Bean bootchain, I should be free to flash ROMs built for my device without a serious concern about hard-bricking, right?

ransdell2 said:
Got my phone JTAGed by Patrick Walls (whose service is available on eBay for ~$35), and it works great. Fast service and great communication from Patrick. The phone came back unrooted with a stock 4.1.2 ROM. Of course I immediately re-rooted it and flashed a fresh JellyBAM ROM to it (with a huge feeling of trepidation), and so far everything is working, with the exception of the camera (I get "Can't connect to camera" after taking one picture, and a reboot is the only thing that enables the camera again, for one pictures, then can't connect, reboot, one pic, can't connect, etc.).
Having never hard-bricked before after many, many ROM changes on a Fascinate and about 10 ROM changes on my S3, I'm a little nervous about changing them now. Is my hesitation unfounded providing I don't mess with the bootchain? To root my phone I flashed the VRALEC bootchain, then TWRP, then rooted, then JellyBAM, then the VRBMD3 bootchain, as per this rooting guide:
http://forum.xda-developers.com/showthread.php?t=2046439
Now that I've put my phone back to the Jelly Bean bootchain, I should be free to flash ROMs built for my device without a serious concern about hard-bricking, right?
Click to expand...
Click to collapse
Glad you got it working.
There's always a risk of something going wrong and a hard brick reoccurring, you just had bad luck. I don't think your brick had anything to do with your bootchain.
I think what probably happened was when you made a nandroid in cwm, the boot partition somehow got corrupted. CWM by default restores your boot, recovery, data, system, and cache partitions. In the advanced restore section, you can restore one at a time but you have no way of simply disabling a particular partition from being restored. I think since the boot partition was messed up, it erased your good data and hard-bricked your phone.
TWRP by default only backs up your data, cache, and system partitions and leaves your boot and recovery partitions alone. If you restore that backup, then there's pretty much no way a hard brick can happen. I can't think of any reason why you really need to backup your recovery or boot partition.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
Glad you got it working.
There's always a risk of something going wrong and a hard brick reoccurring, you just had bad luck. I don't think your brick had anything to do with your bootchain.
I think what probably happened was when you made a nandroid in cwm, the boot partition somehow got corrupted. CWM by default restores your boot, recovery, data, system, and cache partitions. In the advanced restore section, you can restore one at a time but you have no way of simply disabling a particular partition from being restored. I think since the boot partition was messed up, it erased your good data and hard-bricked your phone.
TWRP by default only backs up your data, cache, and system partitions and leaves your boot and recovery partitions alone. If you restore that backup, then there's pretty much no way a hard brick can happen. I can't think of any reason why you really need to backup your recovery or boot partition.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Great, thanks for the info! I'll make sure that the boot and recovery partitions aren't touched in the future. I've primarily used CWM, but am probably just going to stick with TWRP.

screwed up phone bad,think its some kinda bricked HELP PLZ NOOB

So I had cm12 installed and something happened to where my.phone was lagging so I said screw it and reflashed, while something happened and now I tried to while everything. Well I think I did something wrong because I lost all my apps in the app drawer,but when I go into file manager all my stuff is still there,but now the last couple times I tried to reboot the charging light was flashing red to yellow, but when I take the battery out and put it back in it reboots fine back to the screwed up home screen. Still with all my apps and pictures. Viewable in file manager.someone please help I'm freaking out thinking my phone is screwed up for good ....

Very hard to understand you. What ROM did you flash to now? Does TWRP work, can you get into TWRP?

Yes I can get into twrp,basically it threw me back into my cm12 ROM with none of my apps,and I tried to reflash Google apps and it didn't work,so if I can get into twrp is there a way to fix this by doing like a general full factory reset? And if so exactly how do I do that? I dunno this sucks....I dont wanna try anything else until I kinda have an idea what to do, don't wanna screw it up anymore

kjhrezjr said:
Yes I can get into twrp,basically it threw me back into my cm12 ROM with none of my apps,and I tried to reflash Google apps and it didn't work,so if I can get into twrp is there a way to fix this by doing like a general full factory reset? And if so exactly how do I do that? I dunno this sucks....I dont wanna try anything else until I kinda have an idea what to do, don't wanna screw it up anymore
Click to expand...
Click to collapse
If you don't know how to factory reset you probably shouldn't be flashing in the first place. I highly suggest just doing a clean flash and flash Gapps right after you flash CM 12. In order to wipe data, you just click wipe in TWRP.

No I know how to factory reset lol.it's just I did that and when it would go to restart I got little error code up in left hand side of screen. But it doesn't matter because thanks to androidrootz I downloaded New firmware connected it to pc and completely reinstalled operating system. So I'm not rooted or anything and I'm back to square one, .but much better than where I was at.

If your custom Rom was bugging out it could have been a corrupted download. Sometimes all you can do is start from scratch. If you want to flash custom, you need to expect these things. Remember that this is a development site. I have seen where the same Rom acts differently on the exact same phone model. This could be due to a variety of things such as microscopic differences in hardware (this is one of the reasons phones of the same model handles being overclocked more our less than others), settings, tweaks, or apps installed.

I think I've bricked my phone and am not sure what to do

Hey all, before I start I'd like to apologise for making the post here but I don't know what you guys would classify the state of my phone as, "bricked, soft-bricked, hard-bricked", I have no clue! As a result I have no idea what threads to start looking in so I've come here to make this, sorry again!
I'm here looking for help because I think I've completely destroyed my Moto G and really really would like to fix it.
Basically, I had been running an old version of CyanogenMod for months and was not able to update due to the fact my bootloader was not updated. After finally updating it through a tool on XDA, I installed the newest version of CyanogenMod onto the phone and it was all going well, except for the fact all of my Google apps were crashing and making it impossible to use.
Now, I'm not sure why, but without taking any precautionary measures or looking into it at all or what I needed to do, I then decided to try and flash a Paranoid Android rom onto the phone, which installed fine. I load the phone up and something comes up with a passcode saying I need to unlock it to use the phone. I put in some random things and eventually get it, but it says my data is corrupted and therefore I need to reset to factory settings and there's a button there to do it. I think "why not" and click.
So now, the phone did something weird and basically went into a bootloop of the PA logo, so I restarted the phone and went to the bootloader thing. When doing "Normal Startup" it loads the phone with the PA logo like before, comes up with a brief "Android is Upgrading" screen before showing me the passcode screen for half a second, before repeating this, thus having a bootloop. Every so often, I can put my code in and press the reset button again, but it does the same thing.
On the other hand, if I try to access my ClockworkMod recovery system, the screen repeatedly flashes with the CWM background of the Android Alien guy, as if to say it keeps trying to start but it cannot.
TLDR: I cannot access my phone through a normal powerup or through my recovery, have I screwed it completely?
I'd hugely appreciate any help here guys because I'm stressing like I never have before here, thanks!
EDIT: it is the X0123 version!

Spaciouz said:
TLDR: I cannot access my phone through a normal powerup or through my recovery, have I screwed it completely?
I'd hugely appreciate any help here guys because I'm stressing like I never have before here, thanks!
EDIT: it is the X0123 version!
Click to expand...
Click to collapse
Just a few questions before I start suggesting a full flash to stock.
Did you have any SIM passwords, boot passwords, CWM passwords before flashing?
Also In CWM does it flash before any options are selected and did you dirty flash the new ROM over the old ROM?
Anyway, your phone is not hardbricked as it can get to recovery so thats good news.
I would suggest flashing your phone back to factory stock using the tools here on XDA (http://forum.xda-developers.com/showthread.php?t=2542219). That should hopefully resolve most of the issues and then if you feel like it you can start flashing custom ROMs again.