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

[Q] Xperia Tl Bricked won't turn on QHSUSB driver?

Okay, how about this one?
My phone WAS stuck in one of these infamous boot loop/battery thingys, but I just removed the battery and charged it with an external RC Battery charger ($60, charges EVERY type of battery, everyone should have one). When I put it back in, everything was great. I then used Flashtool to unlock the bootloader without problem. Then I went to flash a stock ROM to the thing via flashtool and left it go. When I came back, flashtool had completed the operation without errors, and had last told me to reset the phone. The phone, however, wouldn't turn on or respond AT ALL to anything I did. So I took the battery out and charged it, thinking it must just have run out of power but upon putting the battery back in, the phone remained unresponsive.
No modes, no lights, nothing. The ONLY thing that happens is if I have the thing plugged into the PC and I hold the UP (maybe the DOWN, i don't remember) button, the PC detects and tries to find drivers for something called QHSUSB_DLOAD... qualcomm High Speed USB download drivers, maybe? I've looked around and somewhere someone said that for another Xperia (don't remember which one) THEY had read that you could get the phone into flashboot mode somehow once installing the drivers. They supposedly come with the "gordon's" USB tools or whatever the heck it's called, but I couldn't get xp to accept anything included with gordon's as a proper driver. Yes, I know I had to INSTALL gordons, since an exe sure isn't a driver.
I've also found that, at least for the Galaxy 2, once you're at a point where it's asking for QHSUSB_DLOAD drivers, there's nothing you can do short of JTAG repair. However, as my friend so succinctly put it, "That's not a galaxy, it's an xperia" so I'm still holding onto hope. Anybody have any ideas? Or where I could find a QHSUSB_DLOAD driver and what to do with it then? I AM planning on getting a jtagger soon, so maybe this'll be the reason I finally do.

1) you did not unlock your boot loader successfully using flash tool, that's impossible.
2) uninstall all Sony and any phone software/drivers from your PC
3) charge your phone for at least 24 hours without touching it.
4) install pccompanion to your PC
5) with the phone still turned off, press and hold the volume down button and attach usb cable, then whilst still holding the volume button press the power button until the phone vibrates.
6) the phone should go in to flash mode and you should be able to repair using flash tool, if it doesn't try the next steps.
7) install flash tool and run drivers.exe, choose flash mode, fastboot and tx drivers.
8) press and hold volume. Up and power button until phone vibrates and go back to step 5
9) after you have tried all this please let me know what happens
Sent from my LT30p using xda premium

xperia
gregbradley said:
1) you did not unlock your boot loader successfully using flash tool, that's impossible.
2) uninstall all Sony and any phone software/drivers from your PC
3) charge your phone for at least 24 hours without touching it.
4) install pccompanion to your PC
5) with the phone still turned off, press and hold the volume down button and attach usb cable, then whilst still holding the volume button press the power button until the phone vibrates.
6) the phone should go in to flash mode and you should be able to repair using flash tool, if it doesn't try the next steps.
7) install flash tool and run drivers.exe, choose flash mode, fastboot and tx drivers.
8) press and hold volume. Up and power button until phone vibrates and go back to step 5
9) after you have tried all this please let me know what happens
Sent from my LT30p using xda premium
Click to expand...
Click to collapse
1) Are you sure of that? I mean, it even has a BUTTON for it... it just automates the flashboot thingy if I remember correctly... the thing is, when I was writing my post, I wasn't sure if I was confusing this phone with another I was working on right then... but, no I'm pretty certain I did it through flashboot. Maybe not. Anyway, it wouldn't have even let me flash if my bootloader was locked still, right?
2) Haha- I'm afraid that's not really possible, BUT I already have PC companion installed and it was working fine. (Can you unlock your bootloader through PC companion? Maybe THAT's what I did- I KNOW I didn't do it through the command prompt, though...)
3) Okay, I am actually trying this as we speak, though I did take the battery out and charged it fully already
4) PC Companion installed
5) asks for QHSUSB_DLOAD driver, never vibrates
6) I wish
7)done
8) does nothing
9) Okay, so I will allow that perhaps there are things going on that all the uninstalling and reinstalling would fix and so I will try it out on a clean computer here in a little bit, but I don't think I'm gonna have any luck. I'll let you know what happens...

1) I am certain you have not unlocked your bootloader via flash tool or by pccompanion.
2) step 3 said charge battery for 24 hours, so you have not done that yet.
3) the remaining steps need to be done after the charging, so please follow the instructions as I have said them
4) the way you keep confusing terms and mixing up words makes me think you have not really done your research before trying to flash your phone. Reading is a great thing, try post 2 of the all in one thread. (there is no such thing as flashboot, that's a weird mixture of two different things, flash mode and fast boot, you need to know the difference between them. Also you can flash roms with a locked bootloader, you need to understand the difference between rooting and unlocking)
Sent from my LT30p using xda premium

greg,since 23rd February 2013 you can unlock BL via flashtool.You should know that...
Unified Bootloader unlock feature with the new BLU icon. No more unlock plugin.
Click to expand...
Click to collapse
http://www.flashtool.net/changelog.html

AFAIK that is just for the devices it could unlock before (2012 and before), not the newer devices that it could never unlock such as ours.
Sent from my LT30p using xda premium

gregbradley said:
1) I am certain you have not unlocked your bootloader via flash tool or by pccompanion.
2) step 3 said charge battery for 24 hours, so you have not done that yet.
3) the remaining steps need to be done after the charging, so please follow the instructions as I have said them
4) the way you keep confusing terms and mixing up words makes me think you have not really done your research before trying to flash your phone. Reading is a great thing, try post 2 of the all in one thread. (there is no such thing as flashboot, that's a weird mixture of two different things, flash mode and fast boot, you need to know the difference between them. Also you can flash roms with a locked bootloader, you need to understand the difference between rooting and unlocking)
Sent from my LT30p using xda premium
Click to expand...
Click to collapse
1) http://news.softpedia.com/news/Sony...ts-Flash-Tool-for-Xperia-Devices-315706.shtml - no wait, that just says it's supported by flashtool. I'll keep looking. I could tell you real easy if my bootloader was unlocked or not, but the thing wont turn on Would flashtool have offered me the bootloader unlock button if it didn't support it for my device? It tells me how to get to flashmode erroneously (for MY model, not most) but I figured it just wanted me in flashmode so I put the phone in flashmode. Hell, maybe I never unlocked the bootloader and just tried flashing a stock rom... would flashtool have allowed me to try and flash a non-stock rom with an unlocked bootloader? Would THAT have bricked the phone? I'm gonna go see what the rom I flashed was called now....
2) yeah, as I said, I'm doing that right now. though I took the battery out and charged it, so I thought it might work... even still, it's not been on for 24 hours yet as I writing this, so waiting... is there something that being on the charger for 24hours does besides ensure the battery is charged? Calibration or something? I can assure you the battery is fully charged to peak capacity.
3) will do, though when it doesn't work, do you promise that we can try to talk about QHSUSB_DLOAD? I promise that when it DOES work, I'll happily thank you and admit that even though you haven't quite given me a reason WHY, leaving it plugged in for 24 hours did something more than charge the battery. I know that sounds sarcastic, but I really think there's a chance it could but as I said, I can assure you the battery is charged to peak capacity
4) so I call "flashmode" "flash boot" mode- I am quite well aware of the differences between flashmode and fastboot mode. Figured since the one said flash and the one said fast it was obvious. Man, I did my "research", I read the all-in-one thread, as well as others... I've done this to dozens of phones over the last 3 years and just recently an Xperia Play which acquainted me with many of the idiosyncrasies of the Xperia line, flashboot, pc companion, etc... so when, after 3 years I finally actually ASK a question, I start to get this particular brand of close- mindedness... the way you keep not even trying to actually answer my question makes me think you didn't necessarily read my post before offering up a standard "cookie cutter" recipe which you don't necessarily understand enough to see how it might not necessarily apply. My REAL question was about QHSUSB_DLOAD device requiring a driver since that's the ONLY RESPONSE I CAN GET AT ALL from a phone WITH A FULLY CHARGED BATTERY. (you see, there I wanted to say QHSUSB_DLOAD driver, but that's not quite correct- QHSUSB_DLOAD.dll would be a possible name for the driver, but it's really a device called QHSUSB_DLOAD which does not have a driver. See how I'm taking pains to watch my words so as to not promote confusion.)
Cause you're RIGHT, really; using the proper terms IS important, but can you tell me that you SERIOUSLY didn't know what I meant when I said flashboot mode instead of flashmode? Or that you knew what I meant, but you thought that I didn't ? Did I ever confuse the two terms flashboot and fastboot? "there's no such thing as a flashboot"... what a silly-sounding thing to say... anyway, I never said there was- just that there was a flashboot mode. )Anyway, I do appreciate the help, just not the attitude, y'know?

The attitude was not meant (Nor I hope delivered, maybe its just a style of writing and trying to get to the point quick)
What charging for 24 hours does is to make sure there is some charge in the phone. I am no technical expert here, I am just very good at fault finding and knowing a trick or two that helps. The majority of people on here do not do their own fault finding before asking for help so before I dive in and help people I want to know that something simple has not been overlooked.
Charging for 24 hours has helped about 80% of the people on here who claim a hard/soft brick and they have tried ABSOLUTELY EVERYTHING to fix it.
Anyway, as for the QHSUSB download, I have had that before and just a perseverance of starting again from scratch and charging worked. (That's why I asked you to wipe all sony/phone/adb etc software from your pc) However, I am sure you are aware that the majority of times this happens you are left with a hard brick. Google gives a lot of results on this about Samsung and HTC phones (All of which offer no solutions) but very little for xperia phones.
All I am trying to do is guide you through some fault finding techniques and then give you some advice on things that have worked for people in the past.
NB
It is sometimes hard for me to hold the hand of all the users I help. I get between 20-30 PM's a day (Some of which are quite bad mannered because I have not replied within a few hours with a message on how to help them, that does not put me in a good mood) and check the Q&A thread (And general thread for those that cannot post in the correct forum) on a very regular basis in order to help people, but the increase in people not reading and just flashing means I cannot dedicate the time to being a personal assistant to all, you may have see 4 new threads in the Q&A section in the last 24 hours, all made by different users with the same problem, all of which occurred because they were flash happy and tried CM roms without unlocking the bootloader....
EDIT
There is still no such thing as flashboot....its called flashmode
In the past some users have called these two modes different things, got them mixed up or even thought they were the same thing, that's why I wanted to know which one you meant.
Also, the flashtool you linked to in point 1 is the official flashtool for Sony that only works on unlocked bootloaders. The flashtool from the first post in the dev section is the original flashtool by Androxyde and Bin4ry (First developed for the x10) and is the one to use for flashing FTF's and the one you used from your original post.

i also have this problem.
my xperia TL won't response anything. Plug in to PC it searching for QHUSB_DLOAD driver.
now, phone still in my drawer for 4 month

gregbradley;45518226]The attitude was not meant (Nor I hope delivered, maybe its just a style of writing and trying to get to the point quick)
Click to expand...
Click to collapse
S'okay. Attitude was a big strong for what I meant, but I couldn't think of the right word at the time...
What charging for 24 hours does is to make sure there is some charge in the phone.
Click to expand...
Click to collapse
Yeah, that's what I had gathered... I just got out of a bootloop by charging the battery with a programmable peak charger, so I KNOW its got a full charge.
The majority of people on here do not do their own fault finding before asking for help so before I dive in and help people I want to know that something simple has not been overlooked.
Charging for 24 hours has helped about 80% of the people on here who claim a hard/soft brick and they have tried ABSOLUTELY EVERYTHING to fix it.
Click to expand...
Click to collapse
See, right- that's what I always hear everybody say on forurms like this... cause it's TRUE. Most people asking a question generally barely know the proper question to ask and when the DO, they don't think to SEARCH for it. (Although I've always found the Xda forum search EXTREMELY lacking; I'd do a search for a term in the xda search and get nothing so I had to go to google and find the proper xda page through IT. It's much better of late, though)
However, it has been my experience that everything everybody always complains about; people asking before even searching themselves, people asking questions but not providing enough relevant information for the questions to be answered, etc... all these "rules of conduct" are based around the avoidance of WASTED TIME/EFFORT. Which I whole-heartedly agree with. I almost never ask about anything on the forums because it's almost ALWAYS faster to find the answer myself. It's usually out there.. so when I DO post a question, I will give a detailed account of my situation, how I got there and where I'm at... so, with all that everybody says about reading BEFORE you post questions why does it always seem like NO ONE EVER READS MY QUESTIONS before answering? For example, this time I was just like- "wow, dude didn't even read the background, gave me a cookie-cutter set of instructions and didn't even TRY to answer my actual question!"
Anyway, as for the QHSUSB download, I have had that before and just a perseverance of starting again from scratch and charging worked. (That's why I asked you to wipe all sony/phone/adb etc software from your pc)
Click to expand...
Click to collapse
For real? You've actually had that before and come out of it? Was it on an xperia device? That means there IS hope beyond JTAG service... galaxys don't have flashmode, know what I'm sayin? I'm thinking maybe if I get the QHSUSB_DLOAD driver qpst or (more likely) qxdm will communicate with the port and I can do something like getting it into flashmode or rebuilding it or just figuring out what happened.
Haven't had much luck finding the drivers, but I haven't really looked that hard yet...
However, I am sure you are aware that the majority of times this happens you are left with a hard brick. Google gives a lot of results on this about Samsung and HTC phones (All of which offer no solutions) but very little for xperia phones.
Click to expand...
Click to collapse
Sure am. Yeah, what led me to post was when every time QHSUSB_DLOAD was even mentioned by galaxy owners, the immediate consensus was that this always means you're bricked and require JTAG repair service. As you say, not much regarding xperia, although the ONE thing I saw was someone who said that THEY heard something about getting the driver and being able to parlay that up into getting it back into flashmode or fastboot mode but that's about it. I'm gonna keep on it...
NB
It is sometimes hard for me to hold the hand of all the users I help. I get between 20-30 PM's a day (Some of which are quite bad mannered because I have not replied within a few hours with a message on how to help them, that does not put me in a good mood) and check the Q&A thread (And general thread for those that cannot post in the correct forum) on a very regular basis in order to help people, but the increase in people not reading and just flashing means I cannot dedicate the time to being a personal assistant to all, you may have see 4 new threads in the Q&A section in the last 24 hours, all made by different users with the same problem, all of which occurred because they were flash happy and tried CM roms without unlocking the bootloader....
Click to expand...
Click to collapse
No doubt... it is sometimes hard for me to ask questions because most times I only end up having to bring the person supposed to be helping me up to speed simply to be able to ask the question and have the answer be (usually, but not ALWAYS) "you're guess is as good as mine". I don't mean you, just so you know; I'm speaking of "how it usually goes".
EDIT
There is still no such thing as flashboot....its called flashmode
Click to expand...
Click to collapse
oh, for sure. flashboot MODE, however- well, there's still no such thing, but at least it's not as blatantly misleading
In the past some users have called these two modes different things, got them mixed up or even thought they were the same thing, that's why I wanted to know which one you meant.
Click to expand...
Click to collapse
I was actually talking about fastmode and fastflash mode, but I would expect you'd never heard of THEM before, either?
Also, the flashtool you linked to in point 1 is the official flashtool for Sony that only works on unlocked bootloaders. The flashtool from the first post in the dev section is the original flashtool by Androxyde and Bin4ry (First developed for the x10) and is the one to use for flashing FTF's and the one you used from your original post.
Click to expand...
Click to collapse
[/QUOTE]
Yeah, I know; I posted that link thinking it said something other than what it did- like there's gonna be a news article about Sony adding support I edited the post and mentioned that and left the link instead of just deleting it. Dunno why.
All that the Sony flashtool can really do is return you back to stock, right? I think I read something like that...
So anyways, I tried it after charging 24hrs but there was no difference. Gonna look into this Qualcomm HSUSB Download driver- ANYONE know ANYTHING about it?

adol.ivxx said:
For real? You've actually had that before and come out of it? Was it on an xperia device? That means there IS hope beyond JTAG service...
Click to expand...
Click to collapse
Yes, but it only happened the once, a fair few years ago before I really had heard of the problem. That's why I can not be quite sure how I fixed it, but it certainly was nothing more than perseverance of trying different things.
I was actually talking about fastmode and fastflash mode, but I would expect you'd never heard of THEM before, either?
Click to expand...
Click to collapse
Not for Sony Xperia devices.
So anyways, I tried it after charging 24hrs but there was no difference. Gonna look into this Qualcomm HSUSB Download driver- ANYONE know ANYTHING about it?
Click to expand...
Click to collapse
Sorry I could not have been more help. I will continue to dig around and ask others I know that might shed more light on this. I will post here again as when I have something you might appreciate. Good luck.

Ur phone is hardbricked

[Q] my xperia x8 turns on and off again and again

Hello everyone.
I just got my xperia x8 from my brother because he didn't know how to fix it.
The phone seems like it has not even a scratch.
The issue is that everytime i turn it on it is just turning on and off and on and off again and again.
I don't even have time to input my pin.
The battery always seems to be drained although i charge it occasionally.
I have updated it's os with pc companion, but it keeps doing the same thing.
Is there anything that i can do to fix it?

Mr Skatosakoulas said:
Hello everyone.
I just got my xperia x8 from my brother because he didn't know how to fix it.
The phone seems like it has not even a scratch.
The issue is that everytime i turn it on it is just turning on and off and on and off again and again.
I don't even have time to input my pin.
The battery always seems to be drained although i charge it occasionally.
I have updated it's os with pc companion, but it keeps doing the same thing.
Is there anything that i can do to fix it?
Click to expand...
Click to collapse
try to flash stock frimware through flash tools(this wipes the data & reinstalls the system partition)
Normally flashing fixes all software fault but if your hardware is damaged so you shouldnt be hopeful.
I think its a sw problem but even an empty battery can cause exactly the same react.(put another battery then try flashtools)
Hope i could help you
Sent from my E15i using Tapatalk 2

Mr Skatosakoulas said:
Hello everyone.
I just got my xperia x8 from my brother because he didn't know how to fix it.
The phone seems like it has not even a scratch.
The issue is that everytime i turn it on it is just turning on and off and on and off again and again.
I don't even have time to input my pin.
The battery always seems to be drained although i charge it occasionally.
I have updated it's os with pc companion, but it keeps doing the same thing.
Is there anything that i can do to fix it?
Click to expand...
Click to collapse
Did he do any modifacations to the software?
If not, seems like a battery problem to me. Anyway try to flash stock rom.
Btw your username is...

stamatis said:
Did he do any modifacations to the software?
If not, seems like a battery problem to me. Anyway try to flash stock rom.
Btw your username is...
Click to expand...
Click to collapse
that's our little greek secret... no modifications to the software but he kinda had troubles with this mobile for the whole period of time he owned it.he didn't receive messages in the particular device as far as i can remember. the battery doesn't seem to have anything wrong though.it is just sliiiightly puffed but nothing that alerting.i mean i havent charged it for a long time and it can still power the mobile's "neverending loop". if there was a problem wouldnt it not turn on at all or something? i don't have an extra battery and i'm thinking of getting through with the flash stock romafter i charge it a bit.. should i? and if yes, how? i've never done that (a guide would be great )

Mr Skatosakoulas said:
that's our little greek secret... no modifications to the software but he kinda had troubles with this mobile for the whole period of time he owned it.he didn't receive messages in the particular device as far as i can remember. the battery doesn't seem to have anything wrong though.it is just sliiiightly puffed but nothing that alerting.i mean i havent charged it for a long time and it can still power the mobile's "neverending loop". if there was a problem wouldnt it not turn on at all or something? i don't have an extra battery and i'm thinking of getting through with the flash stock romafter i charge it a bit.. should i? and if yes, how? i've never done that (a guide would be great )
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=35338935&postcount=2

stamatis said:
http://forum.xda-developers.com/showpost.php?p=35338935&postcount=2
Click to expand...
Click to collapse
links don't work. i found the stock rom. all i need now is flashtools. Working link anyone?

I got it done. i flashed it succesfuly and was able to work with it while connected to my laptop. once i unplugged it, it went off after 2 minutes. Now all i have to do is buy a new battery.Thank you guys. i just got a free x8 from my stupid brother

Three random issues - Has anyone else experienced these?

Background info: I've had my Xperia Z1 only for two to three weeks now. I've been enjoying every part of it, but I've come across three particular gripes I have to mention.
First, random app crashes. One time the Album crashes, the other time System crashed. It appears to be random, not based on anything you were or weren't doing at that moment. I don't think I'm the only one with this though.
Secondly, and here's where it gets weird: my on-screen buttons disappeared. I believe I was just closing GTA: San Andreas. Suddenly, the buttons were gone. I could scroll through the app drawer perfectly, still. That's the odd thing. I should've taken a screenshot if I realised this earlier. I will next time it happens, so let's hope I don't have to. After a while, the phone froze and I decided to reset it, after which everything returned to normal. I guess that's one part where hardware buttons beat software - they don't magically disappear (I hope..).
Lastly, I opened the camera and it looked like it lagged. I pressed the Home button twice or thrice, but then the entire device froze and it kept vibrating like hell! I don't particularly enjoy 5" vibrating devices so I decided to reset it as quickly as possible. No way that could've been good for the device.
Have you experienced one of the last two issues I've had? Or have you had something similar yet different?
Let me know below!

i
Hermantje said:
Background info: I've had my Xperia Z1 only for two to three weeks now. I've been enjoying every part of it, but I've come across three particular gripes I have to mention.
First, random app crashes. One time the Album crashes, the other time System crashed. It appears to be random, not based on anything you were or weren't doing at that moment. I don't think I'm the only one with this though.
Secondly, and here's where it gets weird: my on-screen buttons disappeared. I believe I was just closing GTA: San Andreas. Suddenly, the buttons were gone. I could scroll through the app drawer perfectly, still. That's the odd thing. I should've taken a screenshot if I realised this earlier. I will next time it happens, so let's hope I don't have to. After a while, the phone froze and I decided to reset it, after which everything returned to normal. I guess that's one part where hardware buttons beat software - they don't magically disappear (I hope..).
Lastly, I opened the camera and it looked like it lagged. I pressed the Home button twice or thrice, but then the entire device froze and it kept vibrating like hell! I don't particularly enjoy 5" vibrating devices so I decided to reset it as quickly as possible. No way that could've been good for the device.
Have you experienced one of the last two issues I've had? Or have you had something similar yet different?
Let me know below!
Click to expand...
Click to collapse
these are not important problem
>> repair ur phone firmware by PCcompanion
:good:

x102x96x said:
these are not important problem
>> repair ur phone firmware by PCcompanion
:good:
Click to expand...
Click to collapse
I'm sorry, what?
It's pretty important to not lose the three main on-screen buttons, not to mention having a device that doesn't vibrate like you-know-what.
What would repairing the firmware do? The phone is still new. There couldn't be anything wrong with the firmware, not solvable by flashing the same firmware over it again, I reckon.

x102x96x said:
these are not important problem
>> repair ur phone firmware by PCcompanion
:good:
Click to expand...
Click to collapse
That's not an answer, even a solution tho. Please be friendly, respect the other.
Sent from my C6903 using Tapatalk

i
Hermantje said:
I'm sorry, what?
It's pretty important to not lose the three main on-screen buttons, not to mention having a device that doesn't vibrate like you-know-what.
What would repairing the firmware do? The phone is still new. There couldn't be anything wrong with the firmware, not solvable by flashing the same firmware over it again, I reckon.
Click to expand...
Click to collapse
yeah these are problems and easily can be solved
by PC companion.
even more issue can appear on new phone.
these are bugs on ur ROM
when u repair firmware, PC companion will download latest firmware (available for ur region) and install it on ur phone.
That can solve ur problem.
-
if repairing by PCC didn't help u should download Flash-Tool for Xperia & firmware of another region and flash it.
u can find useful information about it here.
Source
:good:

omegahanggara said:
That's not an answer, even a solution tho. Please be friendly, respect the other.
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Try repair is really the first thing to do with ROM dependent error, so there is nothing wrong with the answer.

harfot said:
Try repair is really the first thing to do with ROM dependent error, so there is nothing wrong with the answer.
Click to expand...
Click to collapse
How can this be a ROM dependent error when I just had my Xperia Z1 for a couple of weeks and updated to official Android 4.3 Jelly Bean through an Over The Air update? My Android firmware is as official and up-to-date as it gets right now.
EDIT: Actually, I wasn't even asking for a solution. I was purely wondering if anyone else had these specific issues as well.

Hermantje said:
How can this be a ROM dependent error when I just had my Xperia Z1 for a couple of weeks and updated to official Android 4.3 Jelly Bean through an Over The Air update? My Android firmware is as official and up-to-date as it gets right now.
EDIT: Actually, I wasn't even asking for a solution. I was purely wondering if anyone else had these specific issues as well.
Click to expand...
Click to collapse
Because any update (especially an OTA) might fail and because these errors (mentioned, i think, for the first time here) are ROM dependent.
So first thing I would do is trying the repair.
I'm aware that you only asked for similarities, but as the are annoying errors, we just wanted to help with a possible solution.

Are you running a 4.3 stock ROM?
Do you use bluetooth/have it turned on?
If yes to both, it is a bug in the 4.3 roms related to bluetooth. Only solution I am aware of is to restart the phone whenever it happens and if you can leave bluetooth off

footyfanatic said:
Are you running a 4.3 stock ROM?
Do you use bluetooth/have it turned on?
If yes to both, it is a bug in the 4.3 roms related to bluetooth. Only solution I am aware of is to restart the phone whenever it happens and if you can leave bluetooth off
Click to expand...
Click to collapse
Yes & no.
I never use bluetooth actually.

Issues upon issues upon more issues!

I may be the lucky one whose screen didn't start to peel off yet,but f*ck me this phone is starting to really piss me off.
Everything worked well after I have gone to SLiMM 1.4(way before) and as I was upgrading SLiMM versions it was slower and slower to the point where the phone is unusable!
So I thought,let's try to do a good old phone reset,reflash the ROM and go from the beginning.
I restored the apps,rebooted the phone and it was STILL painfully slow,so I resetted it again but this time restoring half the apps and half the Xposed modules I have used before.
It improved a tiny bit but nothing significant.
So I thought it is finally time to unlock the bootloader and see if there is any good AOSP ROMs,as the first one I tried was AOSP 7.1.1.
Fastest ROM I have used by far,the biggest problem,my device gets very hot from loading Messenger and jumping back to Snapchat and in AOSP 7.1.1 it would stop charging the phone because of the high temperature and this was quite a big issue.
So after using it for 2 weeks,I couldn't handle the charging thing anymore,so next best thing was Sony Concept ROM.
I install the ftf,goes well,install the recovery,install DRM fix,SuperSU and Xposed.
After rebooting I notice that Xposed didn't install properly so I jump back and flash it again,and the problem now was it would get like VERY VERY hot(you couldn't touch it) when it came to the "Android is starting" screen and of course the device started rebooting itself because it was way too hot.
So what I did was put the phone on a bag of f*cking ice to keep it cool,and it FINALLY passed that screen,only to find out a second later it returned to the bootanimation and gone into a bootloop.
Now I reflashed the ftf,but before even booting the ROM for the first time I flashed recovery,Xposed,SuperSU and the DRM fix.
It booted up fine,so I started to restore my apps and everything went well until I rebooted my device to find out it doesn't want to log in to Snapchat,the app I use very often.
So I flashed Magisk,systemless Xposed just that I can hide the root from it and disable Xposed just to log in to my account.
Even that didn't work so fine I'll try it next day.
So I decide to reboot the phone quickly and it has gone into the "Android is starting" screen and shut off in the half of the process. F*cking pissed.
I cool the phone down,boot it up,wait for it to finish and when it was close to finishing it has gone into a bootloop,and wiping cache doesn't solve it.
It is currently in a bootloop as we speak.
I really do like the phone but why is it behaving so badly? I do not know if someone had a similar experience as I did.
If anyone could give me a suggestion to make my phone stable and functional,please write a post since I need my phone to work.

Flash original android rom/kernel to the device to make device fully stock. Once it is back to stock, if problems still continue i recomend sell device and buy new one.. On my xperia, display stopped working out of blue, replaced it and my camera became blurry and vibration motor stopped working... Opened it again, fixed vibration motor, now it waits another opening to replace battery and camera lens... Disaster, but hey, device is great in hw department..

Strmy said:
Flash original android rom/kernel to the device to make device fully stock. Once it is back to stock, if problems still continue i recomend sell device and buy new one.. On my xperia, display stopped working out of blue, replaced it and my camera became blurry and vibration motor stopped working... Opened it again, fixed vibration motor, now it waits another opening to replace battery and camera lens... Disaster, but hey, device is great in hw department..
Click to expand...
Click to collapse
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.

Dinkec27 said:
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.
Click to expand...
Click to collapse
Jebiga mi Hrvati imamo lose srece sa mobitelima hahah
More luck next time

Dinkec27 said:
I forgot to mention,every time I said reset the phone I actually did flash the stock ftf and set it up all on my own,but whatever.
I guess it is just bad luck.
Click to expand...
Click to collapse
internal memory is failing.

bookworth said:
internal memory is failing.
Click to expand...
Click to collapse
Awesome

bookworth said:
internal memory is failing.
Click to expand...
Click to collapse
Dinkec27 said:
Awesome
Click to expand...
Click to collapse
Exactly, I suggest the same issue. I had exactly the same problem on my Xperia T, it became slower, slower, incredibly slow after three years so I couldn't even flash anything using flashtool - it was showing many errors. Even after factory resetting the phone, it was booting and setting up for like... two hours or more, becoming VERY hot but it finally booted, still was very slow.
Two solutions - warranty or selling it.

romcio47 said:
Exactly, I suggest the same issue. I had exactly the same problem on my Xperia T, it became slower, slower, incredibly slow after three years so I couldn't even flash anything using flashtool - it was showing many errors. Even after factory resetting the phone, it was booting and setting up for like... two hours or more, becoming VERY hot but it finally booted, still was very slow.
Two solutions - warranty or selling it.
Click to expand...
Click to collapse
It just doesn't make sense to me that the internal memory could be failing just under a year...
I cannot go for warranty since I voided it with unlocking the bootloader,and selling it is not an option because I am on a contract currently and I can only sell it once it expires and then get a new phone to renew my contract.
If it is internal memory,it is a second tine in a row,before I had the Galaxy S3 and it had the same symptoms,it looks like I'm prone to internal memory failures lol

Is there a way I can test the internal memory?