Database Develop

New Nexus Not Working

Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!

Sounds like a DOA. Really bad luck.

If you send it back you should not pay duty to get it back usually, unless you live in a very tax hungry country! Between US and CAN you would not get duty.
Beside try speaking with cust support, DOA are usually well handled by company and so far HTC seem to be handling repair quite well as per the few post about broken screen I have seen.
Did you try running the phone WITHOUT an SD card ? good luck!
Krypton1984 said:
Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Click to expand...
Click to collapse

If the boots, has never been rooted (boot unlock), no immediate physical damage, and has no signs of liquid damage or tampering (check void sticker).... it's likely just a software issue. Reload original firmware, or load a new firmware... Don't give up, sounds like the phone is still okay.

Was it bnib?

mrbkkt1 said:
Was it bnib?
Click to expand...
Click to collapse
So it seems.
Where are you from, Krypton1984 ?

Looks like some rogue app is loading at boot, causing reset. Possibly corrupt ROM image - but not sure. Might be software, might be hardware. But here's one thing to try:
If you're on a T-Mobile-compatible phone (900/1700/2100), do yourself a favor and flash stock Froyo. No need to root for that. The guide is in the sticky thread. In case of corrupted ROM image it'll do the trick.

I think you should factory reset it. Maybe even download the official 2.1 rom and install it. See if it fixes it.

Try a battery trade in first. Believe it or not, my first N1 seemed dead, and support gave me a swap for a new unit. When the new unit came in, it was still "dead" with the battery that originally shipped with the device. A new battery is what caused my N1 to finally come to life. The batteries that ship with N1's have QC issues, because I was one of many to report a DOA battery in the Google support forums.

its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.

Krypton1984 said:
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Click to expand...
Click to collapse
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.

You can also try a full factory reset through the bootloader. Search for the instructions as i do not know them off the top of my head

P00r said:
Between US and CAN you would not get duty.
Click to expand...
Click to collapse
Yeah, North America is all one big happy family. We've got NAFTA and everything now.
OP, I am assuming you've allowed the battery to charge full?

badomen said:
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
Click to expand...
Click to collapse
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...

padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
You'll probably need to swap based on what you're saying. I, though, actually think Refurbished devices are just as good or even better than new. Think about it, if you keep getting dust under the screen maybe a refurbished phone will already have the fix? For that scenario it works out.

padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
I really think this is a bad RAM issue.
I had this happen to my Nexus (ATT). It was prior to flashing froyo. I tried everything, flashing back to stock (including radio), cyan's latest, Paul's (stock) Froyo (with and without radio). Same result. Seemingly random reboots.
I thought initially that it was a software issue - It would not reboot while in fastboot/Amon's Recovery. But having tried every software combination, I've concluded that it MUST be hardware, unless I'm missing something big.
The phone, for the most part, would be fine as long as I DON'T TOUCH IT. It would stay idle for a long period of time (24hrs+), then I would use it Everything from web browsing to downloading apps to making calls, and it would reboot. It's frustrating because it seems that it's rebooting for no reason except that I'm touching it.
Sent in for a replacement, it arrives today. Hopefully it will not suffer this problem.

After talking with HTC they told me i need to swap the phone.
Because i'm out of america i need to send it to someone in the US amd then they send him the new divice after he sends my old one,
I am not satisfide with google's (first guy I talked with) and HTC because none of whome understand the severity and the hard feeling of getting a BRAND NEW IN BOX paper-weight. nothing about we'll compensate you or nada.
For me it tells me the brand is not strong enough to manage an outer state service and i wouldn't recomend them for countries that they don't cell it for.
If you where born in a HTC GOOGLE compatible country enjoy!
As i'm am probably less lucky and still in 2010 nationality counts

Unable to root Kindle Fire HD

Hi!
I got my kindle fire hd today (german edition) and tried to root my device. So i watched the guide on *** and read several articles and forum threads to be prepared rooting the kindle fire. Ok first of all: i might have damaged the screen, although i have no clue how this happened. One of the corner led doesn't work properly anymore. The effect is like heavy clouding on led tvs.
I followed exactly the tutorial on ****. After the first step, the processor starts to heat up and the tablet slows a bit down. After the second reboot the tablet gets really hot and significantly slows down. The screen starts to flicker and the tablet needs about 10 seconds to execute a command. After a reset to factory defaults everything works like charm except the clouding. I changed the usb port, reinstalled the android sdk and even used qemuroot. Nothing works. I am going to send my kindle back and buy another one, but i wont try to root it without solving this problem. Does anyone have an idea??
/edit as a new member i can't post any urls. The first *** is reverendkyle.c*m and the second is an article on redmondpie

Sounds like you received a defective device. Send it back.
Maybe the "German Edition" versions were those that didn't make the first round of quality control checks.

soupmagnet said:
Sounds like you received a defective device. Send it back.
Maybe the "German Edition" versions were those that didn't make the first round of quality control checks.
Click to expand...
Click to collapse
I only mentioned it because my firmware version isn't 7.21 (sorry my fault) but 7.20. Never heard of it, maybe the eu version somehow differs from the us version.

noskill123 said:
I only mentioned it because my firmware version isn't 7.21 (sorry my fault) but 7.20. Never heard of it, maybe the eu version somehow differs from the us version.
Click to expand...
Click to collapse
7.20 is on the 32GB that I just received today.

soupmagnet said:
Sounds like you received a defective device. Send it back..
Click to expand...
Click to collapse
yup, it's the right advice. don't try to force any root, send the device back instead and have a new try with the next one.

The root will work for both 7.2.0 and 7.2.1, barring any anomalies with your specific device. I would use the automated root found on this forum when you try rooting next time, since it'll eliminate any possible mistakes (not saying you made any). Either way, everyone else is definitely right in saying you got a defective device. Luckily, Amazon's pretty good about replacements when you're under warranty. My own device's CPU was running so hot, it smelled like things were melting. Got it replaced with no fuss, and no extra charges.

noskill123 said:
Hi!
I got my kindle fire hd today (german edition) and tried to root my device. So i watched the guide on *** and read several articles and forum threads to be prepared rooting the kindle fire. Ok first of all: i might have damaged the screen, although i have no clue how this happened. One of the corner led doesn't work properly anymore. The effect is like heavy clouding on led tvs.
I followed exactly the tutorial on ****. After the first step, the processor starts to heat up and the tablet slows a bit down. After the second reboot the tablet gets really hot and significantly slows down. The screen starts to flicker and the tablet needs about 10 seconds to execute a command. After a reset to factory defaults everything works like charm except the clouding. I changed the usb port, reinstalled the android sdk and even used qemuroot. Nothing works. I am going to send my kindle back and buy another one, but i wont try to root it without solving this problem. Does anyone have an idea??
/edit as a new member i can't post any urls. The first *** is reverendkyle.c*m and the second is an article on redmondpie
Click to expand...
Click to collapse
That’s exactly what happen to me about 10 days ago my KFHD
Get hot and speed is unbelievable slow down but I do manage to reset to factory setting
http://forum.xda-developers.com/showthread.php?p=32866304#post32866304
But finally I manage to root my KFHD and switch off upgrade option because I don’t want
The same problem occurs to me again.
My mistake at the first time is I mix up the method using manually method by reverendkjr
And on half way using script giving by sparkym3, so on the second attempt I only use
manually method by reverendkjr doing exactly what he is done and I get my KFHD rooted
I hope this will help you
NB
Even I uncheck automatic update they still updated my KFHD now I am with 7.21
and became unroot yes will start allover again.:fingers-crossed:

Nexus 6 (rooted, stock rom) won't turn on anymore. Please help

Hello everyone,
I'm experiencing a pretty tough issue mith my beloved (and, so far, flawless) Nexus 6. It had root and a stock rom on it, 6.0.1 (MMB29V). I had unlocked the bootloader and rooted the phone right after buying it more than a year ago and I've been flashing new factory images a couple times (specifically when 6.0.0 and 6.0.1 were released). I usually do everything via Wugfresh's NRT, not because I can't use adb and fastboot, just because it works fine and I'm lazy.
Yesterday, while I was working, I used "Tiny Scanner Pro" to scan a document (legit copy bought on the store, as any other premium app in my phone) and it got stuck for a while, then a popup about Google Play Services came up. I dismissed it and another appeared, and it kept going like that. I was at a client's and I was in a hurry, so I took the pic with my tablet and forced the phone off. Later I turned it on, it seemed to boot regularly, but when the SIM unlock screen appeared and I entered the (right!) PIN, it said that no SIM was found, then the home screen appeared but after a while the screen went black and it started rebooting. Recovery (TWRP) and fastboot were working, so I decided to take it home and re-flash the stock rom: it had been a while since the last time anyway, a new version was out and the OTA update notification was getting annoying. I connected to my PC in recovery mode and transfered my pics and data via adb while I downloaded the latest stock rom (6.0.1 MOB30D). Then I user NRT to flash it (selecting "Soft-bricked/Bootloop" as current status). It appeared to work fine as it went through the usual copying and unpacking. Then, when the phone was supposed to reboot, it just blacked out. I waited a long time, in fact I went out and came back a few hours later, and it was still that way. Now it doesn't power up, no matter how long or hard I press any combination of the three buttons, adb and fastboot do not detect it in any way, of course, and it doesn't seem to charge either (i.e. I left it plugged to its original charger overnight and it still feels dead cold). By the way, the phone warranty shouldn't have expired, but I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
I've taken a look at similar threads but none of them describes the very same situation. Is there something, anything I can try to do before giving up? I hope somebody can help me. I thank you all very much in advance.
lupus

lupusyon said:
.... I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
Click to expand...
Click to collapse
Bricked!. When the phone is still under warranty send it for repair. Do not use arguments.
Just: phone will not switch on and does not charge.

Because this is a Nexus device, the custom recovery shouldn't affect your warranty. It is however, a moot point. The device is totally dead, and a call to Motorola is in order.

lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...

dahawthorne said:
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
Click to expand...
Click to collapse
I bought it on Amazon Italy Marketplace, I'm not sure if they're supposed to handle the thing or if I should contact Motorola. I'll just check with them first. Thank you everybody for the kind advice, I'll let you know how this turns out. :good:

I confirm what dahawthorne wrote above: it took them about a month but Motorola repaired my Nexus under warranty, no questions asked. It seems they replaced the Mainboard PCB.
Thanks everybody!

Phone dropped, now stuck in a continuous bootloop (but boots)

Hi everyone,
I dropped my phone (SM-W910N8, Vidéotron, Canada; at the time, stock 5.0.1, only rooted with TWRP) from a height of about 1 foot. It fell on the floor face first. As I picked it up, everything seemed normal. After some time, I realized that, while the phone worked, I was no longer connected to a network, so I went into the mobile network settings where it told me my SIM card was no longer detected.
I decided to restart the phone. That's when the bootloop started.
I went into TWRP, that worked great.
I made a backup and wiped cache, still bootloop. Tried a factory reset, still bootlooping. I tried restoring to a very early backup I had which led to yet another bootloop.
I tried copying a custom ROM from my PC while in TWRP, and have errors copying any files. (tried again after updating TWRP to the most recent version)
I tried reinstalling a fresh copy of Android 5.1.1. using TLS-N910W8VLU1COI4-20151002161810.zip through Odin, and it got to "Android is updating (...)" before bootlooping.
Now I installed a fresh copy of Android 6.0.1. using VTR-N910W8VLU1DPE2-20160531140250.zip through Odin, it got through "Android is updating (...)", can use Android for about 30 seconds to 1 minute, but the phone still bootloops.
Does anyone have any insight to fix this problem?
Thank you!

Try taking out the sum and booting and then putting it back in

noob4598 said:
Try taking out the sum and booting and then putting it back in
Click to expand...
Click to collapse
Thanks for the quick reply!
I forgot to mention, I tried with/without my SIM and/or SD card in all combinations

Sounds like a loose connector. Not really an easy fix for that :/ But I could be wrong.

Is your phone under warranty still? And if not . How tech savvy are you? I had two note 3s that I use to tear down and it's not that difficult if you are careful. Just find a guide on YouTube and take take the back off. All the connectors should be right there. Just detach and reattach each one and see if that helps

noob4598 said:
Is your phone under warranty still?
Click to expand...
Click to collapse
Nope, unfortunately.
noob4598 said:
And if not . How tech savvy are you? I had two note 3s that I use to tear down and it's not that difficult if you are careful. Just find a guide on YouTube and take take the back off. All the connectors should be right there. Just detach and reattach each one and see if that helps
Click to expand...
Click to collapse
Pippinkid said:
Sounds like a loose connector. Not really an easy fix for that :/ But I could be wrong.
Click to expand...
Click to collapse
I'm pretty tech savvy, I'm not afraid to tear it down, I've done it before to replace a screen on another model smartphone (SGS4, I believe?). I bought a LG/Google Nexus 5x (returning to my nexus roots) and love it, its my daily for now. That means I can toy around with my Note 4.
Thanks a lot for your insight, will post back with results after I try tearing it down.

quicksand10 said:
Nope, unfortunately.
I'm pretty tech savvy, I'm not afraid to tear it down, I've done it before to replace a screen on another model smartphone (SGS4, I believe?). I bought a LG/Google Nexus 5x (returning to my nexus roots) and love it, its my daily for now. That means I can toy around with my Note 4.
Thanks a lot for your insight, will post back with results after I try tearing it down.
Click to expand...
Click to collapse
Good luck brother! Let us know what comes.

Factory reset has not restored Auto-Rotate, Active Edge, and the "ear sensor" when making calls

Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)

aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)
Click to expand...
Click to collapse
I would try flashing the latest factory image via fastboot.
[Guide] Root Pixel 4 XL with Magisk Android 13
[Guide] Root Pixel 4 XL With Magisk Android 13 Android Security Bulletin—Feburary 2023 Pixel Update Bulletin—Feburary 2023 Introduction This Guide is for Pixel 4 XL owners that want to Root their phone, and enjoy the benefits of rooting it. The...
forum.xda-developers.com
https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/ (This is for a Pixel 2 XL but the process is the same. It's basically a condensed version of the one above.)

aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Click to expand...
Click to collapse
You did not provide the most important information we need- whether your phone is bootloader unlocked. Probably not, otherwise you would have already flashed it with a full Google image, which returns the phone to "out of the box" condition. You need to determine whether you can unlock your bootloader. If you cannot unlock (allow oem unlock is off and or greyed out in Dev options) then you will not be able to fastboot flash ANYTHING. If that is your case, the next best thing is flashing a full OTA image (sometimes called a rescue OTA) from recovery mode using the OTA via ADB option. This means you need fastboot/adb installed and working on your PC. Instructions on how are on the same Google dev page for OTA's.

So, my phone's bootloader is not unlocked. But I have an update for the crowd that may one day find this. I know your frustration and I can report that my phone is once again fixed.
A day (or two) after I sent this, a set of updates came down to my phone. And WebView was updated. That restored all of my sensors and also restored most of my crashing applications. It was an incredibly odd experience.
My phone once again functions. And the nightmare of owning a Google phone and talking to Google support has ended.