Database Develop

[Q] Buying Droid Bionic tomorrow, can I root the device?

Verizon 4G LTE allows speeds of 10Mbps which is insane, Tmobile has around 3Mbps
Should I chose Droid Bionic or go to Sprint and chose Samsung Galaxy S II?
I like the idea of the Bionic having better resolution
I really like the idea of a device as fast as the HTC Thunderbolt but with dual CPU
Any advice?

It is supposedly already rooted somewhere. But personally I avoid Motorola blur enabled phones unless your whole intent is to have problem with crashing or resetting. I would wait to buy it until a stable nonBLUR ROM is out like cyanogen. I like Moto hardware, but supporting Moto software just plain sucks.
Sent from my mwp6985 / Trophy using XDA Windows Phone 7 App

http://phandroid.com/2011/09/02/mot...ore-we-can-even-get-an-official-release-date/ but browsing from my phone I am lazy to search the validity of the source.
Sent from my mwp6985 / Trophy using XDA Windows Phone 7 App

The droid 3 method works. http://www.psouza4.com/droid3/
The other thread here offering a bounty for the first root has confirmation.

One caveat. I do not believe there is a way to back out of root, yet, for the Bionic.

rafarataneneces said:
Verizon 4G LTE allows speeds of 10Mbps which is insane, Tmobile has around 3Mbps
Should I chose Droid Bionic or go to Sprint and chose Samsung Galaxy S II?
I like the idea of the Bionic having better resolution
I really like the idea of a device as fast as the HTC Thunderbolt but with dual CPU
Any advice?
Click to expand...
Click to collapse
10 would be the really really low end. I get 20+.

GertBFrobe said:
One caveat. I do not believe there is a way to back out of root, yet, for the Bionic.
Click to expand...
Click to collapse
Just removing su and Superuser.apk should be enough to back out of root for now.

I'm leaving now, hope to get the phone soon

Well here's my 2 cents. I just moved to Southern California and was on Sprint previously (with the Evo rooted) which sucks where I live so I went over and switched to T-mobile (with the Sensation stock). T-mobile wasn't cutting it for me either. Was on it for 29 days and returned it. Now I'm on Verizon with the LG revolution that I've had for a few days (worst phone I've used) till I pick up my bionic today. Verizons service and coverage is bad ass totally worth it. All I gotta say.
Sent from my VS910 4G using xda premium

Berzerker7 said:
Just removing su and Superuser.apk should be enough to back out of root for now.
Click to expand...
Click to collapse
B, doesn't the one-click process do more than just add in su and superuser.apk? I thought that there are other changes within the system files. I could be wrong.
I'll be waiting for an SBF, myself.

Doesn't look like it, it uses an exploit, which was already in the original code and doesn't do any system modifications besides adding files. Removing them will get rid of root.
Of course, if we had an SBF, it'd be easier.

redmatt said:
It is supposedly already rooted somewhere. But personally I avoid Motorola blur enabled phones unless your whole intent is to have problem with crashing or resetting. I would wait to buy it until a stable nonBLUR ROM is out like cyanogen. I like Moto hardware, but supporting Moto software just plain sucks.
Sent from my mwp6985 / Trophy using XDA Windows Phone 7 App
Click to expand...
Click to collapse
FWIW, my wife has a Droid X and it's been as stable, if not more so, than my Incredible. She has never had an issue with "crashing or resetting".

I got my Bionic at 8am this morning and the root method for the droid 3 worked perfectly. The longest part was waiting for the motorola drivers to install. I am now rooted and have made a backup of my apps with Titanium. I will be removing the Verizon installed bloat next. Until there is a recovery and way to restore I will leave all the blur and phone files alone though...

tbgreen89 said:
Well here's my 2 cents. I just moved to Southern California and was on Sprint previously (with the Evo rooted) which sucks where I live so I went over and switched to T-mobile (with the Sensation stock). T-mobile wasn't cutting it for me either. Was on it for 29 days and returned it. Now I'm on Verizon with the LG revolution that I've had for a few days (worst phone I've used) till I pick up my bionic today. Verizons service and coverage is bad ass totally worth it. All I gotta say.
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
+1 I did they exact same thing but with a Droid Charge... Verizon all the way!! Going to pick up my Bionic today for exchange..

So the Droid 3 root method works on the Bionic? I am trying to figure out which phone to get that I can EASILY root. I had a D2 and rooted with DoRoot with ease and since I know NOTHING about programming, etc. I need something easy. Thanks for any help!

rooting bionic
"I got my Bionic at 8am this morning and the root method for the droid 3 worked perfectly. The longest part was waiting for the motorola drivers to install. I am now rooted and have made a backup of my apps with Titanium. I will be removing the Verizon installed bloat next. Until there is a recovery and way to restore I will leave all the blur and phone files alone though..."
May i ask you if your bionic has 2.3.4 or 2.2.2?

EDIT........

WarrantyVoided said:
"I got my Bionic at 8am this morning and the root method for the droid 3 worked perfectly. The longest part was waiting for the motorola drivers to install. I am now rooted and have made a backup of my apps with Titanium. I will be removing the Verizon installed bloat next. Until there is a recovery and way to restore I will leave all the blur and phone files alone though..."
May i ask you if your bionic has 2.3.4 or 2.2.2?
Click to expand...
Click to collapse
All new bionics have 2.3.4

smalltownbird said:
I got my Bionic at 8am this morning and the root method for the droid 3 worked perfectly. The longest part was waiting for the motorola drivers to install. I am now rooted and have made a backup of my apps with Titanium. I will be removing the Verizon installed bloat next. Until there is a recovery and way to restore I will leave all the blur and phone files alone though...
Click to expand...
Click to collapse
Were you able to restore a previous backup from Titanium? I'm trying to use it and restore my apps from a backup on my Charge but it looks like the Bionic cannot see the backup.

stang68x said:
Were you able to restore a previous backup from Titanium? I'm trying to use it and restore my apps from a backup on my Charge but it looks like the Bionic cannot see the backup.
Click to expand...
Click to collapse
At first it did not see any of my stuff either at first. I'm not even really sure what I did beyond rebooting, but it worked just fine. Mine is rooted and all apps are back up and running. next step is to get rid of all the crapware.

[Q] Bionic won't turn on at all...

I found a similar thread from a while ago, but the scenario was different so I figured a new thread wouldn't be that far out of the question.
Any input is greatly appreciated.
So here's what's happening.
Five days ago I threw [R3]BLURR3D 1.7 on my friend's Bionic coming from 1.1.
Stupid as it is, I didn't do a full wipe/reset (Just wiped cache and dalvik) since I noticed that the other versions as they were coming out were no wipe updates.
Five days running smooth as all holy hell, and then yesterday his phone started skipping while playing music with the screen off. He couldn't turn the screen on so he pulled the battery. When attempting to turn the phone back on it booted up and hung on the boot animation then shut down. Now it wont turn on at all, tried two different batteries.
So my question is this, could this just be a random faulty model or could my stupidity have royally screwed up his phone?
I'm familiar with soft bricks and know that the phone will present text saying your screwed if it's a hard brick, but I've never seen a phone not even boot up due to screwing with ROMS and such.
TL;DR
Only wiped cache and dalvik upgrading to [R3]BLURR3D 1.7 from 1.1 (stupid, I know) and after five days of smooth sailing now my friend's Bioninc wont turn on at all.
Faulty hand set?
Can this be fixed?
Do I owe my friend a new phone?

Creepazoid said:
I found a similar thread from a while ago, but the scenario was different so I figured a new thread wouldn't be that far out of the question.
Any input is greatly appreciated.
So here's what's happening.
Five days ago I threw [R3]BLURR3D 1.7 on my friend's Bionic coming from 1.1.
Stupid as it is, I didn't do a full wipe/reset (Just wiped cache and dalvik) since I noticed that the other versions as they were coming out were no wipe updates.
Five days running smooth as all holy hell, and then yesterday his phone started skipping while playing music with the screen off. He couldn't turn the screen on so he pulled the battery. When attempting to turn the phone back on it booted up and hung on the boot animation then shut down. Now it wont turn on at all, tried two different batteries.
So my question is this, could this just be a random faulty model or could my stupidity have royally screwed up his phone?
I'm familiar with soft bricks and know that the phone will present text saying your screwed if it's a hard brick, but I've never seen a phone not even boot up due to screwing with ROMS and such.
TL;DR
Only wiped cache and dalvik upgrading to [R3]BLURR3D 1.7 from 1.1 (stupid, I know) and after five days of smooth sailing now my friend's Bioninc wont turn on at all.
Faulty hand set?
Can this be fixed?
Do I owe my friend a new phone?
Click to expand...
Click to collapse
Try dhacker29's 1-click restore in development. If that doesn't work, I'd say yes.
Sent from my DROID BIONIC using xda premium

mistawolfe said:
Try dhacker29's 1-click restore in development. If that doesn't work, I'd say yes.
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Thanks for the advice, but the phone wont turn on at all so there's no chance of getting it into fastboot.
Or was that an elaborate and sarcastic way to say I'm screwed haha.

Creepazoid said:
Thanks for the advice, but the phone wont turn on at all so there's no chance of getting it into fastboot.
Or was that an elaborate and sarcastic way to say I'm screwed haha.
Click to expand...
Click to collapse
I wasn't being sarcastic, however this is me now saying you're probably screwed.
Sent from my DROID BIONIC using xda premium

Have you tryed plugging it into a charger is the battery charged. Have held the volume down button while powering the phone on?

Haha, alright, well thanks again for the heads up on the one-click, definitely going to come in handy in the future.
Sent from my MB860 using XDA App

beidave said:
Have you tryed plugging it into a charger is the battery charged. Have held the volume down button while powering the phone on?
Click to expand...
Click to collapse
He said he's tried a few different batteries.
Sent from my DROID BIONIC using xda premium

So what was the verdict? Mine just did the same thing. However, I Have followed all of the directions everytime i've flashed and never had an issue til right now.

If you can't get the phone on at all, no fastboot or anything. No hardware buttons do anything, nothing comes up on the screen with anything you try....
That's a hard brick.
= requires a new phone
No way to fix it.

Couple more things. I mean this is almost identical to what mine did, the ONLY difference is I was browsing rootz using Dolphin HD. And I'm on
R3blurr3d V2.0 PBX
Ice Cream Sandwich Exp3ri3nce
Forever Root and .893 update
Misc Tweaks
I flashed everything yesterday ran fine last night and all day today. Now yesterday I bought a extended battery, but I flashed everything, charged all night, and used it all day with it installed.
well, I was just about to post and noticed something else here. The top of the phone near the earpiece, Sim card, etc., is warm. I would say warm like your battery would be during moderate use, and that is with it plugged in to ac power for about a half hour.

When I messed up my flash and my phone was stuck at the dual-core logo, I followed the steps below.
Pull your battery.
When you put it back in, hold down the power and volume down to access fastboot mode.
From there you can do a one-click restore method.
That is how I solved my problem. I hope it helps you.
Sent from my DROID BIONIC using xda premium

nickbeisher said:
Couple more things. I mean this is almost identical to what mine did, the ONLY difference is I was browsing rootz using Dolphin HD. And I'm on
R3blurr3d V2.0 PBX
Ice Cream Sandwich Exp3ri3nce
Forever Root and .893 update
Misc Tweaks
I flashed everything yesterday ran fine last night and all day today. Now yesterday I bought a extended battery, but I flashed everything, charged all night, and used it all day with it installed.
well, I was just about to post and noticed something else here. The top of the phone near the earpiece, Sim card, etc., is warm. I would say warm like your battery would be during moderate use, and that is with it plugged in to ac power for about a half hour.
Click to expand...
Click to collapse
have you triedf pulling the battery and putting it back in. the hold volume key down and power at the same time? if that works then just restore using fxz. if it does not work your phone is bricked

Brick!!
This is my third droid, I had The D1, the X, and now the bionic. By far I like this one much better than the the others. I have rooted all of them, and done the basic app freezing, overclocking, and other basic mods. This is my first go round with the custom rom flashing. I Flashed R3blurr3d, and every new update ( each update a new flash ). I also flashed D3blurr3d, and Liberty, just to check them out. I personally like Reblurr3d. When I flashed I always followed every direction to the letter, and if I was unclear on something rather than ask a stupid question, or ask something that had already been covered. I read and search until I find the answer I need and it is clear to me, sometimes that means searching for hours on end. I do this for the fear of ending up with a "Brick".
Now with everything I have read about any of these phones to "Brick" It is an error on the user's end while flashing or something of that sort, ( not following directions ).
So with everything operating butter smooth, and flashing dozens of times before this. What would cause a "Brick" during everyday use?

My guess is....he didn't know what he was doing. You rooted it for him and left it rooted for a user that knows nothing about root access. He probably did something using root access to fck something up.
When someone asks you to root their phone for them, the answer is always no.
Unless they know what they're doing, never give someone root access.

my first bionic did same thing. it was not rooted yet. just started rebooting it self. got more frequint then just quit the way you talked about. hardware problem.

Yes. That is what it is. It is a hardware issue, after talking to tech support it is a capacitor or something like along those lines, it stores battery power for times when more power is needed, like turning on the phone for instance. And when it randomly boots it is because it runs short on power due to the faulty hardware.
But apparently it is a known issue with Verizon, so if it happens to anyone else they should not have any trouble getting a new phone. I talked to a very nice tech support agent, and I will have a new phone by noon on Saturday.
And also I didn't have anyone root my phone, I do all of it on myself, Im no computer genius, but like I said I take my time and follow directions. And until now I have had no issues, and this had nothing to do with root access, flashing custom rims, or any other tweaking just a bad part Anthe phone. The thread was started by someone else. When I searched the threads, I found this and it was the same exact problem as I had, so that's why I asked what the end result was.
So with all that being said maybe this will be informative to someone else.

Random reboots.

*no need to comment problem resolved thank you*
kinda pissed im on my third d3. 1st one random reboot problems sent it back got a refurbished one. 2nd one headphone jack stoped working. 3rd one refurbished once again. this 3rd one that i got came with a dead pixle yes annoying but i lived with it also sliding mechinism scratched the gloss yes annoying i lived with it random reboots ok problem. i know i can fix it but i dont feel like spending the time to do it. ive been at it since the original droid custom roms kernels all that fun stuff and i would like to start developing not there yet but im not an idiot. my plan is to call verizon and get a droid 4 but i havent decided if i want to yet the only problems i see with the d4 are no removable battery/locked bootloader/motoblur. locked bootloader could possibly eventually be unlocked who knows. so i can cross out bootloader i can deal. motoblur i can just run the .sh or something to remove the bloat an get a better rom. so cross off motoblur. no removable battery thoughts?
im not asking for help fixing it because i know i can and no its not as easy as an .sbf at this point.
i know my information isnt perfect but i had my original droid for what 3 years? one not 2 of them one, and that thing runs beautifully. unlocked bootloader/removable battery/sturdy heavy. why don't they make em like they used to? moto blur free
so excuse my grammar and such im kinda ranting cause of the time ive spent working on it and im kinda angry but now i need to decide if i should get the droid 4.
minus how to fix my droid 3 cause im going to but im ya LOL scatter brain
thoughts on non removable battery?
your opinions and thoughts are valued.
*no need to comment problem resolved thank you*

If you're getting random reboots you may wanna try rooting and putting a custom bootstrap on there and wiping cache and delvik. Also there are some ROMs w\o Blur and you can choose between it or not. But the Blur isn't too bad at all once you get past the Verizon crap. I run Liberty and it's just Blur and Android, no Verizon crap except for My Verizon.

For the reboots, see if it still does it with no sd card in. I had read that there was a directory that could be causing it.
For the battery, do you carry a backup battery with you now? If not, who cares if you can take it out? My D1 I had multiple backup batteries, and I used them. My D3 I haven't had to use my backup yet, it is big enough to get me through the day, and the D4 has an even bigger one (course there's always the 4G to suck up all that power)
Sent from my XT862 using Tapatalk

My Droid 3 only reboots itself, if I leave it in Airplanemode for 8 hours or so. Then it reboots automatically. When not in Airplanemode it never reboots itself.
Maybe this helps?

thanks all its decided. im now getting my 4th refurbished droid 3. hopefully its not a pos again.

Im having the same issue lately. Ill try the suggestions here tonight when I get off work and let you know how it goes.

I'm upgrading from the Droid3, but this is the best built, most reliable phone I've ever owned. You guys must either be extremely hard on yours or extremely unlucky.
Sent from my DROID3 using xda premium

UNLUCKY lol received my 4th refurbished one its perfect btw. i take care of my tech.

jellman said:
UNLUCKY lol received my 4th refurbished one its perfect btw. i take care of my tech.
Click to expand...
Click to collapse
I got my Droid 3 about 5 or 6 months ago (if I'm remembering correctly) and I have yet to get a scratch anywhere besides the back of the screen (where the clips slide.) Now thats taking care of your technology, considering I use it all day, every day.

ChaoticWeaponry said:
I got my Droid 3 about 5 or 6 months ago (if I'm remembering correctly) and I have yet to get a scratch anywhere besides the back of the screen (where the clips slide.) Now thats taking care of your technology, considering I use it all day, every day.
Click to expand...
Click to collapse
i take care of my tech but, im sure you do the best job in the whole world with yours better than everyone congratulations. i am not hard on my phones.

I used to have random reboots while on Liberty and Mav, none Steel or any CM9A5+, since then I have recovered to both without any reboots, not sure, but assume complete wipes/resets between GB and ICS resolved issue.
CM9A7
Sent from my XT862 using XDA App

How to completely reset

I was hoping someone could give me a step by step on how to completely reset my phone back to the state it was in when I first pulled it out of the box. I just wanna completely start fresh.
My phone is running so damn slow and is all sorts of messed up cause my friend ****ed with it and tried to put one of the custom ROMs he made on it even tho I told him not to and he didn't remove the current ROM I had running first and it just made everything messed up. Which is why I don't want anyone messing with rooting or custom firmware on my phone except for me. I had my phone running the ROM I liked and had my phone running nice and smooth and fast. It ran perfectly. And when he did it he failed to make a nandroid backup beforehand and someone reformatted my sd-card so all the backups I had of my own are gone and now its all sorts of ****ed up.
I've never done a full reset except for on motorola phones and all you had to do with that is get the proper SBF file and run RSDlite. But I don't know what to do on this phone. So a detailed step by step or a link to a detailed guide would be very much appreciated. Thanks in advance for the help.
Sent from my VS910 4G using xda app-developers app

The only way I know of to fully get that "out of box" look and feel is to flash a tot, then factory reset.
Try this Then do a factory reset or vice versa. it's best to do the factory wipe from cwm. essentially wiping data, cache, and dalvik.
http://forum.xda-developers.com/showthread.php?t=1337386

Factory reset
Flash v9 Firmware
then Wipe SD and Internal Storage
Out of box.

I know its been awhile since I posted this, but I unfortunately went to jail shortly after posting this and finally got acquitted of the charges and released from custody just 4 days ago, because the witness refused to testify and all he would tell the Prosecutor was that I didn't start the fight and was only defending myself.
Which was the truth. I was sucker punched twice in the back of the head and after that I completely just saw red as they say, and I don't really remember much of what happened between the getting sucker punched and then being in hand-cuffs with blood on me that wasn't my own, but I apparently broke the dudes jaw and left eye socket. And they, they being the police, tried to say that even tho he swung first, I used excessive force in response and therefore it no longer was self defense lol which is bull****, and it took about 4 months in jail for me to prove that......Well technically I didn't prove anything, the prosecutor just didn't have a case since their so called eye witness ended up backing my story up and wouldn't testify, so they had no choice but to drop it.
And since no one I knew could afford 4,500$ in bail and even tho I had the money in savings, more then enough, they wont let you pay your own bail, unless you have the cash in your property but I only had my debit card and they wouldn't let me release it to anyone so they could pull the money out and since they don't have ATMs in jail lol I got ****ing stuck in there
Anyways, now that I explained my interesring story as to why I am having to resurrect a thread from like 4months ago, my question is, where can I get the current V9 firmware that the most recent poster mentioned. So I can do what I wanted to do 4 months ago lol
Sent from my VS910 4G using xda app-developers app

Give thanks to capt
http://forum.xda-developers.com/showpost.php?p=34196277&postcount=248

Screw Up Stories?

I don't know if this will catch on or not, but I'd like to hear people's stories on how they screwed up or thought they screwed up their phone and fixed it? I think this could be an interesting thread with plenty of good stories and such

absoluterebirth said:
I don't know if this will catch on or not, but I'd like to hear people's stories on how they screwed up or thought they screwed up their phone and fixed it? I think this could be an interesting thread with plenty of good stories and such
Click to expand...
Click to collapse
I haven't screwed this phone up but I remember when I first started rooting phones I bricked my Vibrant (Galaxy S). I think I bricked it because I flashed the wrong radio or something. After that I have never bricked another phone. **Knock on wood**
Now I take extra caution and read extensively before rooting, flashing Roms, kernels etc.
sent from my neXus 5

Heres how i screwed my Nexus 5 on stock, I forgot to charge it and its now dead..
How i fixed it? I charged it :good:

I didn't because I actually read the stickies on the top of the general forum.
/Thread
Sent from my Nexus 5 using Tapatalk

Just took apart my Nexus 5 after it was unresponsive after a week of putting into rice/silica gels. No idea of what I am doing. I have never opened anything up in my life. Soaked motherboard into isopropyl and cleaned it with toothbrush, dropped it like 10 times, ripped a couple of cables. Should be all good though. Will post if it worked.

eastpac said:
Just took apart my Nexus 5 after it was unresponsive after a week of putting into rice/silica gels. No idea of what I am doing. I have never opened anything up in my life. Soaked motherboard into isopropyl and cleaned it with toothbrush, dropped it like 10 times, ripped a couple of cables. Should be all good though. Will post if it worked.
Click to expand...
Click to collapse
Yeah, ripping cables is probably not going to turn out "all good". Just my opinion

markdapimp said:
Heres how i screwed my Nexus 5 on stock, I forgot to charge it and its now dead..
How i fixed it? I charged it :good:
Click to expand...
Click to collapse
Please accept this Thanks as your post is very accurate and straight to the point.:good: Many of us have had that experience before whether it's forgetting to charge it over night by not plugging it into a charging source or it running out of battery power from heavy/extented usuage and not being able to charge it immediately after.:highfive:

DON`T USE TOOLKITS, these are related to most screwups Oh and get your rooting/flashing/adb skills up to par

FuMMoD said:
I didn't because I actually read the stickies on the top of the general forum.
/Thread
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Same!
Sent from my Nexus 5 using Tapatalk

I've only totally bricked one device, that was a sprint HTC evo (og evo). I got a replacement device via insurance and due to new firmware, I bricked it trying to root it/set s-off. No fix possible, only a new phone.
As far as nexi, nexus 5 specifically, I've soft bricked it a ton of times. But, one of the reasons I love the nexus brand, its never taken any more than a nandroid restore or only once a revert to stock. Unless you Dev test (and knowingly flash untested fw) or just start randomly picking zips and flash a modem or boot loader from a different device I've found it damn near impossible to make a nexus device unrecoverable.
I did initially flash the multi-boot mod w an incompatible ROM (beanstalk) and a kernel that really didn't like the multi-boot idea either (don't remember which ver of which kernel ATM). I was stuck on the "Google" boot loader screen for hours til I tried flashing a different ROM (which also changed the kernel) and trying again. Frustrated the hell out of me, kept phone unusable for almost a whole day, and wasted a ton of my time due to my laziness to read the whole thread.
Best advice ever given on XDA, whether you are a novice/learning/a noob or a android pro many years of experience or even a skilled developer.....
ALWAYS, ALWAYS, ALWAYS... did I say ALWAYS read the whole op or even better whole op and hopefully 90%+ of the thread before you try something you are unsure of.
Sent from my Nexus 5 using Xparent Skyblue Tapatalk 2

helioXverse said:
As far as nexi
Click to expand...
Click to collapse
Nexuses

Had the device perfectly set-up, with a few twrp backups as well and then for no reason...moved those backups from the device to the pc (probably in order to free some space). Then in a sequence of screw-ups, downloaded Flashify and wiped the cache and and dalvik cache from within the app (thinking it would be cool)...AND...bootloop! No backups...nothing! Booted to recovery...wiped cache/Dalvik the usual way, still nothing! Wiped data...nothing! Couldn't get ADB to work in the recovery. Finally -> Bootloader -> Fastboot Flash Stock ROM!
Did not stop though. in the next 5 minutes I was back with custom recovery, root and Titanium backup...ready to get back the device in shape (done and dusted as I type )

Reading the undervolting thread I decided to go -75 across the board. I succeeded but then tried to push it lower. Bootloops occurred. Backup copied back to SD card from PC failed to restore (said data failed. This was my first time restoring a ROM on the Nexus 5. If someone has insight as to why this happened it would be appreciated). Decided to go aosp and flash Rasta + trinity kernel but for some reason my mobile data wouldn't activate nor could I update PRL or profile by clicking on the usual option even after reboot and continuously clicking. Now I'm just getting my phone back to the original state it was in before I screwed up my UV values. Cataclysm + ElementalX #Life of a Phone Nerd
Sent from my Nexus 5 using XDA Premium 4 mobile app

gee2012 said:
DON`T USE TOOLKITS, these are related to most screwups Oh and get your rooting/flashing/adb skills up to par
Click to expand...
Click to collapse
I actually used a toolkit to return mine back to stock after i shipped it out to LG for repair after my son dropped. It was much easier for me than to write out the commands. took me about 10 minutes and that was because I locked the bootloader before flashing a zip. and i had to go back yada yada but worked out fine.

Screwed up 2 Galaxy S2's, first one because I didn't pay close enough attention to the brickbug, second one because it just died... Due to the brickbug. Other than those I've never killed a phone. I thought I had broken my friends Nexus 5 though, I unlocked it and went to root it for him but TWRP/CWM couldn't mount any partitions because it's "encrypted". Got it fixed though.
I've killed xbox's, PSP's, everything. It's all part of the learning process.

...When I first got my Nexus 5 in MTP on my Windows PC I had my phone hooked up to, on Internal Memory I saw a folder called sdcard that was not there before that was supposedly empty according to MTP. Deleted it. Turns out it was a symlink screwup in MTP, and it deleted my entire SD card including photos, luckily the important ones were already uploaded to Facebook and such. Now I backup my phone almost daily just in case.
I bricked my Archos Home Connect 35 once. Kinda my fault. I had set the bootloader to boot SDE firmware for it defaultly on boot. (Dev edition firmware from Google that was rootable). I updated from .82 firmware to .83 firmware, forgot to change that. It took the SDE firmware out, normally youd have to reinstall it, and since it was set to boot from that in Archos. mess of a firmware and bootloader, it would just bootloop because the SDE firmware wasnt there. No way to get out of it. RMA'd it and got a new one from Archos though. Never again, will always just manually select the SDE Dev Edition firmware when/if i ever reboot it. (Its just a Alarm clock mostly that plays Pandora occasionally. it last went 300 days without a reboot until it hard locked and I had to reboot. )
Never had a unrecoverable problem with my Galaxy S4, or my Nexus 5.Worst case with the S4 I Odin'd back to stock firmware. Nexus 5 got a corrupt data or cache partition once, i could have ran fsck but I flashed stock images instead.

I was having an issue having my phone seen on my PC. This is after I've rooted... Transferred music and pics from PC to phone, so I knew my drivers were installed. So I tried going back to stock. I downloaded the stock image and tried fastboot flashing. My download was corrupted. It got froze sending the radio. Froze for 30 min... Just kept saying sending. So I finally unplugged and rebooted to bootloader as everything else has been wiped. Tried again and it froze again at sending the boot loader. Froze for 30 min. I unplugged and tried rebooting. It never turned back on. No charging indication or anything. Officially bricked. I had tmo send me a new one and I'm returning the old one today. Wish me luck
First brick of my life and I've been rooting and modding since the OG Nex1
Sent from my Nexus 5 using Tapatalk

My GPS was working intermittently so I applied the cardboard fix and now its great. But in the process I damaged my back cover and now NFC and wireless charging don't work.
Really wishing I just RMA'd it.
Sent from my Nexus 5 using XDA Premium 4 mobile app