Database Develop

Root or Not to Root?

I have recently purchased a Nexus One and i must say it is an amazing phone, but also very expensive! I just spent £370 on buying this brand new phone. Which brings me onto my main point, should i risk rooting or not?
I am confident with the rooting proccess and have rooted my hero etc etc, but i was happy to do so because i could also reinstall an official RUU incase something went wrong. However as we know with the N1 its not that simple. I want to be able to use features such as trackball to wake, and using the lights for notifications, being able to install market enabler and apps like autokiller and also being able to theme my nexus - but to do small things like this i still need to root my phone and void my warrenty.
So ive decided to ask you guys on wether you think it is worth my rooting my nexus one, and voiding my warrenty, or making do with no true customisational potential?
(Also silently hopeing someone finds a way to lock the bootloader :'( )
thanks

Just root it already. No regrets. I asked the same question.

But
But what if anything goes wrong with the phone over the next year? Just seems unecassary that i have to loose my warrenty to be able to make small customisations to the phone

I didn't root my phone in the first 5-6 weeks or so then once I had seen there were no obvious hardware faults I rooted it. It might be safe to take a similar approach.

Is totally up to you.. 2 things:
If you are affraid of bricking your phone due to flashing, don't be. Rule of thumb is always do Nandroid. And flash all you want. The exceptions are Radio's which pose higer risks of bricking.
That leaves hardware issues. If your screen cracks, battery explodes or button cease to function, HTC might switch your phone regardless if you have unlocked boot-loader or not. But im not sure how HTC customer service are in UK. People have done it in US and HTC didn't even raised an eyebrow to this.
edit:
like nDrg says, is to roadtest your phone for some weeks, see if no dust crops up under the screen, or other things starts to defect. Errors on new phones usually reveal themselves in the first weeks.

rooted just after 1 day i receive it lol and Froyo inside my nexus one since Yesterday Yes From France ^^

Hmm
Ok thanks for your feedback. I was having a think and i decided to wait untill froyo comes officially to UK, and if thats not good enough to keep me happy then i will root. Thanks

[Q] Random restart and other issues on streak 7! =/

Got my streak for about a week now, but problems now start to happen. 2 days ago my streak started to mess up when playing sound. Whenever I turn the volume to max while playing music or playing a game, or just watching a video, the sound that is supposed to be played would stop and instead starts playing a buzz noise. This noise would not stop until I restart the streak.
Also, the streak is now randomly restarting. It was just sitting on my desk and all of the sudden the dell logo appears. Anyone else have this problem? Should I just send it back and get a replacement?
Any help would be great!

I've been watching this thread to see if thar be any responses... nothing.
I have the same issues, I've been trying to find out more about it but I havent come up with much.
That being said I do believe this is a software issue. Froyo and Dells apparent lack of interest seem to be the most likely culprit.
I could ofcourse be completely wrong and we both have brand new toys that are busted :-(
Sent from my Inspire using XDA App

I don't have anything helpful to add other than my Streak 7 has never displayed this kind of bahaviour.

Elvis, what did you decide to do? Did you send it in for replacement? I factory reset mine and so far other than some random lag and random resets, the sound issue is gone.
Z4nd4r, thanks anyway. I wish my streak behaves like yours.
One side question, in the next 2 weeks, before my return window closes, if I install the HC beta on my streak, can I still return it? Or do I have to downgrade it back to 2.2.2 without root before I return?

crzayalex said:
Elvis, what did you decide to do? Did you send it in for replacement? I factory reset mine and so far other than some random lag and random resets, the sound issue is gone.
Z4nd4r, thanks anyway. I wish my streak behaves like yours.
One side question, in the next 2 weeks, before my return window closes, if I install the HC beta on my streak, can I still return it? Or do I have to downgrade it back to 2.2.2 without root before I return?
Click to expand...
Click to collapse
It's always a good bet to return it to stock unrooted if you return. They may not care (people have sent rooted/ROM'd phones in to service without issue in the past), but better safe than sorry. Just my $0.02.

well I still have it, havent decided what to do yet. I found a few instances of the same problem around the net but no one goes into much detail. Im back to stock/unrooted after using streak droid for a bit but after a few days of happy video playing the freezes/restarts came back. I want to put the stock recovery back on and do a full reset...but I havent really looked into doing it, if anyone can point me in the right direction that would be swell.

Okay I see. Thanks Z4nd4r. I think I might just leave it at HC cuz it is too much work to get it back down to 2.2.2
HallucinatingElvis, good luck! Is yours the wifi version? The stock rom for the wifi version is in this forum. One of the top posts. You should be able to find it easily.

Well I just fired off an RMA request to New Egg, I figure if im spending 300 bucks it should be able to play a frickin video without choking. Im simply asking for a new one, hopefully I wont experience the same issues otherwise ill try and see if they'll let me exchange it for something else. I really like the little bastard too...

Ohh aww. Its okay, when you get a new one it will be all better. Best of luck to you.

[Q] I hard bricked and am getting a new one thru warranty, will I be screwed?

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.

[Q] Nexus 6 being glitchey

I just got my nexus 6, two and a half weeks ago. I am coming from a Verizon galaxy nexus, so I'm pretty good at unlocking, rooting, installing roms, and the like. I bought it at best buy because I broke my gn, and being they are the only ones that had any in stock, and I need a phone or im lost, I was on vacation visiting family. So I got the none branded one called Verizon got it up in running in five minutes after the 20 min wait to talk to someone.
The first few days I played with it as is never had a problem. So I unlocked it, rooted it and still not any problems. Then a few days later I noticed the speaker would crackle not big thing just noticed it. After that though another weird thing started happening if I answered the phone then decided to use speaker phone i could not hear the other person and they could not hear me, and going back off speaker didn't help till we hung up and recalled.. It does not do it ever time just sometimes.. I had not installed a rom just kept it Google 5.1.1, I really like the new Android. But I did unrooted, relock, factory reset. Then did it all again. Still get some of the problems but not as much. This last problem really pist me off. I had been in 4 states and service from Verizon was great in all but one of them. The one that it didn't not work in was in Missouri not even when I got to Springfield. It was late at night so none of the ton Verizon stores I seen were open, I could dial but not have net service. I tried restarting phone even did a factory restore after trying everything I could think of. That reset screwed me though because it made it a useless since I had no net and was unable to set it back up.. Also I couldn't stop at the ton of Verizon stores in the morning bc they didn't open till later in the day and I needed to get home. The weird thing is almost as soon as I crossed into OK the phone loaded up and started working internet and all.
So my question is, is this normal with these phones? And is their any way to make the radio better? It was on global in that setting so I switched to USA. Still seems to work fine now at my house.
Any help or tips would be much appreciated. Or should I try and do a warranty through Motorola?
I really like this phone and its a major improvement over the gn since we at Verizon got skipped with nexus 5. This battery is a beast 12+hrs doing a crap load of stuff on it rocks

Rbh50815 said:
I just got my nexus 6, two and a half weeks ago. I am coming from a Verizon galaxy nexus, so I'm pretty good at unlocking, rooting, installing roms, and the like. I bought it at best buy because I broke my gn, and being they are the only ones that had any in stock, and I need a phone or im lost, I was on vacation visiting family. So I got the none branded one called Verizon got it up in running in five minutes after the 20 min wait to talk to someone.
The first few days I played with it as is never had a problem. So I unlocked it, rooted it and still not any problems. Then a few days later I noticed the speaker would crackle not big thing just noticed it. After that though another weird thing started happening if I answered the phone then decided to use speaker phone i could not hear the other person and they could not hear me, and going back off speaker didn't help till we hung up and recalled.. It does not do it ever time just sometimes.. I had not installed a rom just kept it Google 5.1.1, I really like the new Android. But I did unrooted, relock, factory reset. Then did it all again. Still get some of the problems but not as much. This last problem really pist me off. I had been in 4 states and service from Verizon was great in all but one of them. The one that it didn't not work in was in Missouri not even when I got to Springfield. It was late at night so none of the ton Verizon stores I seen were open, I could dial but not have net service. I tried restarting phone even did a factory restore after trying everything I could think of. That reset screwed me though because it made it a useless since I had no net and was unable to set it back up.. Also I couldn't stop at the ton of Verizon stores in the morning bc they didn't open till later in the day and I needed to get home. The weird thing is almost as soon as I crossed into OK the phone loaded up and started working internet and all.
So my question is, is this normal with these phones? And is their any way to make the radio better? It was on global in that setting so I switched to USA. Still seems to work fine now at my house.
Any help or tips would be much appreciated. Or should I try and do a warranty through Motorola?
I really like this phone and its a major improvement over the gn since we at Verizon got skipped with nexus 5. This battery is a beast 12+hrs doing a crap load of stuff on it rocks
Click to expand...
Click to collapse
The speaker issue is definitely a known issue. RMA is the only solution.

Crap that really sucks. Thank you though for the reply. Do you know with the RMA if I have to send the phone back first and wait, or will they send a replacement first? Also do they replace with a new one or reman?
I was really hoping it was something in the settings

Rbh50815 said:
Crap that really sucks. Thank you though for the reply. Do you know with the RMA if I have to send the phone back first and wait, or will they send a replacement first? Also do they replace with a new one or reman?
I was really hoping it was something in the settings
Click to expand...
Click to collapse
Not sure, best to call and find out.

Rbh50815 said:
Crap that really sucks. Thank you though for the reply. Do you know with the RMA if I have to send the phone back first and wait, or will they send a replacement first? Also do they replace with a new one or reman?
I was really hoping it was something in the settings
Click to expand...
Click to collapse
May luck out and get new but at this point in the cycle probably refurb. Have to send in first or have creditcard they can hit for what it worth now to send first. Credit hit will be deleted once they show it coming back.

Frustrated with Note 4

So, I've been using this wonderful device for a while now, since early October. I've finally got it set up the way I like it and all. Now, I'm just flashing ROMs to see which I prefer. Just a few hours ago, I decided to revert to the T-Mobile ANK3 (or AN-whatever) stock ROM because on Lollipop 5.0.1+ the battery dies much quicker than I'd like it to. Yet, that ROM would constantly either:
A) Die whenever it wanted to
B) Freeze and just not respond
C) Require a battery pull
D) Send me to D/L mode with "mmc_read fail".
So I decided to revert back to stock 5.0.1 because I was tired of all the bugs I was encountering with 4.4.4.
Now, every hour or so, the phone dies and gets stuck on the splash screen (with the obvious SEAndroid not enforcing + Set Warranty Bit). Or if it isn't that, the phone just outright freezes when I'm using a light application (i.e. Kik Messenger).
I'm starting to think that my eMMC is dying, because the phone was not acting like this when I first got it in early October. Every once in a while D/L mode keeps repeating my fears. I cannot send it in to Samsung because I already voided my warranty, and I am a prepaid subscriber on T-Mobile. (So, no, T-Mobile will not help me, likely.)
Any ideas on what's happening, or what I should do?

First thing I would do Is flash a different kernel

Odin back to stock and reroot the device. Sounds like something got messed up.
Sent from my SM-N910T using XDA Free mobile app

ShrekOpher said:
Odin back to stock and reroot the device. Sounds like something got messed up.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
Did that, ended up having the same problems. I said screw it, and am now using CM12.1...
Although I really don't like it (because TW is now a good thing as opposed as to how bad it was on the S3), I'll settle with it. It's not so bad.
---
LMAO OOOOO I LIED TO MYSELF
even CM is force rebooting itself wwwwhat

Why can't u take it in for warranty? Out of warranty they just replaced my note 4 under warranty and it was rooted

sqmala4321 said:
Why can't u take it in for warranty? Out of warranty they just replaced my note 4 under warranty and it was rooted
Click to expand...
Click to collapse
I bought the phone second hand, and it is out of warranty. I can't fork over money right now, as seeing how replacing the eMMC chip is probably expensive. I'll probably find some hackjob way of finding a replacement, or just live with it. I also don't think reflashing the bootloader will help.
Each time I power on the phone, it seems that it keeps getting worse each time. I get the "ddi: mmc_read fail" message more often, and off a cold boot, the phone will not actually boot and I have to battery pull like 2 times before it actually boots. Gee, looks like I'm screwed.

Good news...since they know that the eMMC chip is bugging out, they'll do a free repair. Success! Now, time to go into the repair shop and hope they accept my reference ticket, since I'll be a walk in.
I can't call right now, seeing as my phone has difficulty doing ANYTHING now...

eduardog131 said:
I bought the phone second hand, and it is out of warranty. I can't fork over money right now, as seeing how replacing the eMMC chip is probably expensive. I'll probably find some hackjob way of finding a replacement, or just live with it. I also don't think reflashing the bootloader will help.
Each time I power on the phone, it seems that it keeps getting worse each time. I get the "ddi: mmc_read fail" message more often, and off a cold boot, the phone will not actually boot and I have to battery pull like 2 times before it actually boots. Gee, looks like I'm screwed.
Click to expand...
Click to collapse
actually i am having the same exact problem....i had the tmobile note 4, and its doing the same thing about 1 month ago...reboots, black screens; and all that you have mentioned. so i started to look into rooting/flashing tekxodus hd onto my phone...still the same problem...phones restarts to boot loop time to time...bad screens....i'm still trying to find outwhat the hack is going on...and the phone's warranty expireds about 1 month ago right before the phone start to act up....let me know if you find a solution to that..lol...thanks:good:
---------- Post added at 11:25 PM ---------- Previous post was at 11:17 PM ----------
ShrekOpher said:
Odin back to stock and reroot the device. Sounds like something got messed up.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
yes, i did that too...odin back to stock, still same problem...my phone was on stock when these problems started. i hoping different roms would solve the problem...so i started rooting and intalled tedxodus and the same problems...hopefully someone could help please.