Related
So I was on atomic fusion and tried to flash another gb rom. Somewhere during the odin process it seemed to be stuck and I stopped it and tried again to get a red screen of death. I tried everything to get to d/l mode but nothing. So I called att and I have about a week left in my warranty so I went that route. Am I gonna be charged 400 dollars when they find out I was rooted with roms not theirs? I'm really nervous, I should have never flashed to gb, its to freeking complicated for me to understand all the bootloading and kernal stuff. Any thoughts or experiences to help ease the pain? Thanks
Prolly shouldn't have flashed if you weren't confident. In yourself.
Sent from my SGH-I897 using XDA Premium App
If your phone shows any signs of life they will most likely be able to tell that you are not stock.
Your fine, I did the same thing as you are doing. I just acted like a clueless idiot and they never suspected a thing, but it was with Rogers not AT&T.
Sent from my Galaxy S Firefly 3.0
For all the topics asking this question I'm yet to see anyone come back saying that they have been refused, or charged extra after a new one is already sent out. In all likely hood they don't even check because they don't really care. If it is a hardware issues they are gonna have to swap pieces or even the main/motherboard which will come with stock pre-loaded at factory. If it is software they will just use what ever method they designed into the phone to force rewrite over what was in there before.
Now if you were taking it to a service center, where they are going to take a look in hopes of getting that very phone back into a working condition then maybe... just maybe. But if the phone does not boot then they are just gonna add it to the rewrite pile and give you a referb (or new if you ask nicely enough). This is why they always say "you might lose all your data so make a backup before hand."
Thanks, that makes me feel better, now all I have to do is survive a couple days without it. I won't be making that mistake again. What did I do wrong? I had no problem going from phoenix ultimate to atomic fusion. I was gonna try to go to cog5, I thought I was doing it right. All I did was use the odin that it said to use and it seemed to be stuck. What do you do when it freezes up during the odin process? Are you screwed no matter what you do? Should I have used the odin that takes you to stock 2.1 first? I'm really trying to understand all this but there's just so many ways about everything.
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.
qhsusb_dload is all I get. Buttons no work. Doesn't vibe or anything. Soft reset doesn't work. Any help or am I screwed. I flashed overcome 8.9 wiped prior and wiped dalvik after the reboot and black screen since.
Sent from my SAMSUNG-SGH-I727 using xda premium
I'm really sorry but your device is done. The skyrocket people haven't been able to fix this yet by using a jig or qualcomm tools.
Reading and researching is really important. You can't flash any p73xx rom to the i957, it will brick.
This is exactly why I have tried to get a separate forum for the i957, but that hasn't worked yet.
Hope you are under warranty or that is an expensive mistake.
Sent from my SAMSUNG-SGH-I727 using xda premium
I did the exact same thing you did. It is very confusing (Well not really, I just did'nt take my time to read). I was exhausted because I was very happy to have my new skyrocket and new lte tab. I researched and researched. I rooted, installed custom rom and kernel on my skyrocket. I then rooted my tablet and it was great. I then installed a custom rom for a 7300 on my i957 and Boom, gone. Luckily I was within my 30 day return policy. Everything in my home is either jailbroken, rooted, homebrewed, w/e. so I have somewhat experience.
But the combination of tiredness, excitedness, and what ever else comes along with getting new gadgets, I didn't pay attention and blew up my tablet.
Even with my experience and never bricking anything before, I bricked my tablet. I took it back to the store and making believe I never even heard about rooting, jailbreaking, homebrewing; the sales people tried starting it up and eventually they couldn't get it to start up. I got a new tablet, I told them I left the tablet charging overnight and left it charging when I went to work, because I forgot to disconnect it. When I got home from work it just didn't turn on.
Eventually they gave me a new tablet and said do not charge it for more than 8 hours. They said I was the first customer to ever return this tablet because it was defective (This tablet is a beast). I told them sure I learned my lesson.
When I went home, I rooted it lol and installed the oc kernel. Remember there are no roms for the 4g model.
Before I went back to the store where I purchased my phone&tablet, I found that there is a youtube store that fixes bricked phones and tablets (He has videos of him fixing them) but when I emailed him, he said their program does not support in unbricking the lte tablet. This was about a month ago so you can check to see if they support it now. I think to unbrick phones it was like 50-100 dollars (I forgot)
You are not alone, I made the same dumb mistake. Never do important stuff when you are tired or excited or anxious. Sorry man, good luck.
I may have put this in the wrong area it was late last night and I was frustrated. I tried putting a 7300 ROM on a 7300. I didn't try anything fancy lol. But I appreciate the responsses. You think I'll be able to take it back and see what they can do? Maybe they'll exchange it as if it was a defect? I'll take it there today. See if they will exchange.lesson learned for me. Lesson being wait for updates from Samsung. As slow as they are. Lol thanks for the input if anyone has the capability to fix this
Hit me up.
Sent from my SAMSUNG-SGH-I727 using xda premium
A 7300 rom on a 7300 should only soft brick. Can you get into download or recovery?
Sent from my SAMSUNG-SGH-I727 using xda premium
If you try to turn on your tablet and your screen turns on you can try to install the stock rom through odin again and it will work. There is a thread in this forums that explains how. If it is off and you turn it on and ABSOLUTELY NOTHING happens and it just stays with the black screen, no vibration or anything then it is hard bricked.
If it is hard bricked you can try to take it back and act dumb, not sure how long ago you purchased the tablet. If you are still within the 30 days you should be good because the sales people I took my tablet to did not have the machine to see how many times my device was flashed. If you are outside the 30 days they will tell you to send it to a samsung repair dealer (which I think they will see how many times the device has been flashed). Once you rooted your tablet it voids the warranty and they either do not have to fix it or will charge you an amount equal to your tablet. I did hear of cases where people with rooted tablets just returned it and they fixed it for free. I guess it dpeneds on anything else in life (How lucky are you?)
Yes you did put your question on the right place since this is for all the 8.9 tablets. (Thats the problem I came across with, I wish they make two forums for both tablets because they are in fact different.
Posting from my mobile so I didn't read your post again.
It is extremely rare but sometimes this can happen. Did you have repartition checked in Odin? If so that's bad.
There is something called qpst - qualcomm product support tools - that people are trying to get to work to fix hard bricks.
Sent from my SAMSUNG-SGH-I727 using xda premium
No prob man. I'll look that up. I'm gonna seems it in to Samsung see if they can fix it. It's under warranty. Anyone done this before?
Sent from my SGH-I727 using xda premium
mobiletechvideos now has support for hard bricked tabs! finally! just sent the payment today and i will send out my tab once i get home from work. ill keep yall posted on how it goes.
here is the link: http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-tab-8-9-jtag-brick-repair/
Thanks for updating us.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Thought this was very odd. I was on phone with tech support cuz my phone bricked itself today. not sure how or why i wasnt even using it. The tech sending me replacement suggested i root my phone because it would help a lot with the random reboot issue i originally had called ina bout last week.
Proceeded to tell me that Verizon does not care if you root as long as the factory data reset will work as intended for them.
Didnt know if this information was well known or not just thought it was odd that a tech tell me to root my phone.
cbrebel said:
Thought this was very odd. I was on phone with tech support cuz my phone bricked itself today. not sure how or why i wasnt even using it. The tech sending me replacement suggested i root my phone because it would help a lot with the random reboot issue i originally had called ina bout last week.
Proceeded to tell me that Verizon does not care if you root as long as the factory data reset will work as intended for them.
Didnt know if this information was well known or not just thought it was odd that a tech tell me to root my phone.
Click to expand...
Click to collapse
I am guessing that means the LG/Stock Factory Reset but CWM Factory Reset does the exact same thing so I am still wondering what that means.. very suspicious
That's very odd. I used to work for AT&T and they said we could loose our job of we told a customer to change the core software on any device. Strange indeed.
--My REVO is Broken, tweaked, SC'd, and TB'd. Just awesome!
drt054 said:
I am guessing that means the LG/Stock Factory Reset but CWM Factory Reset does the exact same thing so I am still wondering what that means.. very suspicious
Click to expand...
Click to collapse
yeah that is what he was saying (he was telling me how he rooted his and was using cwm as well) but he said that verizons policy is that as long as the "STOCK" factory reset takes it back to original condition then they will not persue anything any further. (which btw is stock zv7 right now) the new phone they shipped me doesnt have zv8 yet either.
who knows i just thought i would elaborate what the tech told me.
the phone i sending back had CWM on it and wouldnt boot or charge battery. so i manage to get it into emergency mode and left it for about 18 hours which gave me almost 35 % charge( seems very low) but i managed to push the zv7 tot and revivie it to send back. YAY
Vzn and root
There is a lot of misconception about rooting, I used to co manage a vzn reseller.
If you go to the android market there are root apps all over the place, if rooting voided any warranties there would be huge liability issues for legal software developers and customer uproar. Plus the hardware OEMS would not alllow it to be sold legally. Rooting is a software change you are not hacking or modifying hardware here. Plus android is marketed as open source unlike iphone OS.
drutman said:
There is a lot of misconception about rooting, I used to co manage a vzn reseller.
If you go to the android market there are root apps all over the place, if rooting voided any warranties there would be huge liability issues for legal software developers and customer uproar. Plus the hardware OEMS would not alllow it to be sold legally. Rooting is a software change you are not hacking or modifying hardware here. Plus android is marketed as open source unlike iphone OS.
Click to expand...
Click to collapse
+1 U.S already has declared that rooting any android device is not under any circumstances classed as illegal.
Sent from my Sensation using XDA
RevoRooting
Verizon might also be less persnickety about rooting on the Revolution because it's on its way out. I know Verizon was much pickier about my Droid 1 when it was new than they were a few months ago.
sensation lover said:
+1 U.S already has declared that rooting any android device is not under any circumstances classed as illegal.
Sent from my Sensation using XDA
Click to expand...
Click to collapse
This was only a 1 year term on that ruling. it is coming up again soon whether or not it is viable to do it or not.
cbrebel said:
yeah that is what he was saying (he was telling me how he rooted his and was using cwm as well) but he said that verizons policy is that as long as the "STOCK" factory reset takes it back to original condition then they will not persue anything any further. (which btw is stock zv7 right now) the new phone they shipped me doesnt have zv8 yet either.
who knows i just thought i would elaborate what the tech told me.
the phone i sending back had CWM on it and wouldnt boot or charge battery. so i manage to get it into emergency mode and left it for about 18 hours which gave me almost 35 % charge( seems very low) but i managed to push the zv7 tot and revivie it to send back. YAY
Click to expand...
Click to collapse
Oh man, I totally did that when I had gotten my Revo. Fortunately Thecubed was around, and he took control of my computer and fixed the phone. It was awesome. I recall the battery taking for ever to recharge. We had to wait 30 minutes before we could try anything. We needed enough juice to run ADB and push stuff to my phone.
yep what the verizon sales/ tech guy said
walked into verizon today. my phone messed up but thats another thread... and he literally said verizon does not care if u root your phone... didnt say as long as or anything else. just said they dont care. so yeah feel free to ask them yourself.
LaggyWizard said:
walked into verizon today. my phone messed up but thats another thread... and he literally said verizon does not care if u root your phone... didnt say as long as or anything else. just said they dont care. so yeah feel free to ask them yourself.
Click to expand...
Click to collapse
That's the glory of open source...
Sent from my VS910 4G using XDA
Yeah they Dont care, but brick one & try to get a replacement in warranty if you do.
Last month i made a boo boo installing Clockwork Mod and locked it up.
While they were very helpful, nice, and understanding; And a couple weeks later when I came in with my repaired phone (thanks to un_brickable) were more than happy to get me back online with a new sim card (I had to use my sons old HTC Incredible until I FINALLY found the fix). The warranty is now VOID and I was NOT going to get a new one.
I also dropped the protection plan & bought a "development" Revolution off of E-bay. So if i blow one up i can be back up & running in a couple minutes. cheaper in the long run.
Sometimes being Honest doesnt pay off. But in the end I have a BETTER phone for the experience. (2 of them actually)
cbrebel said:
Proceeded to tell me that Verizon does not care if you root as long as the factory data reset will work as intended for them.
Click to expand...
Click to collapse
I find this hard to believe. If they don't care, why do they keep shutting the door on every new exploit?
Sent from my BrokenOut 1.1 4G VS910 LG Revolution using Tapatalk 2.
stackrat said:
I find this hard to believe. If they don't care, why do they keep shutting the door on every new exploit?
Sent from my BrokenOut 1.1 4G VS910 LG Revolution using Tapatalk 2.
Click to expand...
Click to collapse
Because an exploit is just that, something that can be used maliciously. They aren't trying to screw with rooted people, they are patching security holes.
Sent from my Gingervolt-ed VS910 4G using xda premium
stackrat said:
I find this hard to believe. If they don't care, why do they keep shutting the door on every new exploit?
Sent from my BrokenOut 1.1 4G VS910 LG Revolution using Tapatalk 2.
Click to expand...
Click to collapse
any vulnerable area in the code HAS to be patched because the first people we blame for the phone getting hacked, is Verizon, for not having the security it should have in the software
Sent from my VS910 4G using XDA
Rooted phones are a liability...
For Verizon. The reps don't care (of course), but the main company does. It does void your warranty if they find out about it.
See, the tethering apps, Google navigation, Google voice, etc, etc are all lost profits. This is especially true with this phone, where in stock form, they nickel and dime you for "Verizon Navigation," "Verizon Voicemail," and "Verizon Tether."
Another negative impact for them is the number of returns the early rooting and experimentation process creates. I can remember the number of "forced failures" and nit-picking occurring on my old Eris when people were flashing the leaked upgrade that permanently disabled root, just so they had an excuse to return them.
The Verizon reps are "next-to-minimum-wage," 18-30 year old employees who could give a rat's patootie what you do with your phone. The RMA techs, on the other hand, may not be so forgiving.
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