Related
So, all yesterday, I was having problems getting service anywhere I went. Towards the end of the day I got no service anywhere. So... put my phone on the charger all night, woke up and... Nothing.
Phone wont turn on, battery pull won't work, can't get into bootloader. Orange light turns on when I plug into charge.
I was running the stock HTC ROM with a couple programs installed. Google maps, iContact and Soft Key Changer. Thats it. Had no problems until now.
I called the company I got if from said bring it back they will get me a new one (just got it last Sunday). I can't get Activesync to see the phone so reflash is not a possibility.
They won't be able to turn it on at the store, this thing is gone. But if someone somewhere sees its a new ROM when they send it back (if they can get it on), am I screwed? I think I'd just say the guy in the store did it cause he had is last...
from what I understand you void the warranty by using a different rom.
xconradx said:
So, all yesterday, I was having problems getting service anywhere I went. Towards the end of the day I got no service anywhere. So... put my phone on the charger all night, woke up and... Nothing.
Phone wont turn on, battery pull won't work, can't get into bootloader. Orange light turns on when I plug into charge.
I was running the stock HTC ROM with a couple programs installed. Google maps, iContact and Soft Key Changer. Thats it. Had no problems until now.
I called the company I got if from said bring it back they will get me a new one (just got it last Sunday). I can't get Activesync to see the phone so reflash is not a possibility.
They won't be able to turn it on at the store, this thing is gone. But if someone somewhere sees its a new ROM when they send it back (if they can get it on), am I screwed? I think I'd just say the guy in the store did it cause he had is last...
Click to expand...
Click to collapse
Try a different battery or a different charger first.
brynwall said:
from what I understand you void the warranty by using a different rom.
Click to expand...
Click to collapse
Thats what I understand too. However, you can't get the thing on, no connections - nothing. They won't be able to tell at the dealer for sure. And I think in this state it goes to the junk pile cause I can't get any connection on it period.
From my dealing with Cingular and having to exchange my 8125/Wizard, they always include the statement regarding voiding your warranty if you load unauthorized rom images on your phone.
That being said, I have sent back many bricked 8125's for various reasons (none of which were bad rom images), and I never had an issue with them actually noticing that I had a custom rom loaded on it.
Of course every carrier is different, but judging from my experiences, I think you'll be fine.
NotATreoFan said:
From my dealing with Cingular and having to exchange my 8125/Wizard, they always include the statement regarding voiding your warranty if you load unauthorized rom images on your phone.
That being said, I have sent back many bricked 8125's for various reasons (none of which were bad rom images), and I never had an issue with them actually noticing that I had a custom rom loaded on it.
Of course every carrier is different, but judging from my experiences, I think you'll be fine.
Click to expand...
Click to collapse
Cool, thanks man. I think I'll be fine too. I feel that the issues has nothing to do with the ROM, as the ROM has been working fine for a few days now with no glitches except for the service problem yesterday. I wont mention the ROm of course, but the thing does not turn on in any way whatsoever. The only thing that happens is when you plug in the power you get a orange light up top.
Thanks for your help, I'm glad they haven noticed even on working phones with different roms.
It sounds like it could be as simple as a power issue. Either charger or battery.
But I had the same thing happen to a Razor once. Bricked at the bootlloader screen and would not take a charge from that point on. My carrier (AT&T) had told me the device was beyond repair (translation: they had no clue at the store). Ended up having to borrow a charged battery to re-flash the device.
Haha, I bricked a razr once too, and was able to revive it with via a number of things (barely). I was trying to change the boot screen. Those phones are fun to mess with - at least you could get into the boot loader most of the time even if it was near death.
I'll try a different battery when I get to the store.
I went to the store just now, they changed the battery and... nothing she tried my battery in a new phone and it worked, so the battery is fine, but my phone is f*cked.
I am replaceing tomorrow.
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
Ok, so I bought a brand new in box Moto X from an acquaintance. After a month or two it started randomly rebooting, and after a couple of weeks of rebooting once or more per day, it died. Wouldn't power on (not even recovery). I sent it in for repair>got it back>3 days and it died again>sent it in again>got it back>1 day and it died again>sent it in again>got replacement>2-3 months later the new phone is starting the cycle again. Every time I pull it out of my pocket, the lock button doesn't work, and it's locked up on Active Display. I hold the power button and reboot it, only to have it happen again in an hour. I am doing a factory reset now--does anyone have any idea what the problem may be? what i should avoid when setting it up again?
This phone is 100% untampered with. No root, no nothing.
Please help me out. Thanks!
quaxer said:
Ok, so I bought a brand new in box Moto X from an acquaintance. After a month or two it started randomly rebooting, and after a couple of weeks of rebooting once or more per day, it died. Wouldn't power on (not even recovery). I sent it in for repair>got it back>3 days and it died again>sent it in again>got it back>1 day and it died again>sent it in again>got replacement>2-3 months later the new phone is starting the cycle again. Every time I pull it out of my pocket, the lock button doesn't work, and it's locked up on Active Display. I hold the power button and reboot it, only to have it happen again in an hour. I am doing a factory reset now--does anyone have any idea what the problem may be? what i should avoid when setting it up again?
This phone is 100% untampered with. No root, no nothing.
Please help me out. Thanks!
Click to expand...
Click to collapse
That sounds like a headache.
When were both phones manufactured? What version of KK were you running? Did you upgrade software OTA, if so what did it upgrade to?
Are you saying you never downloaded any apps? never installed anything on the phone? What services did you use? (apps.. anything, what were they?) Were there any other things you noticed out of the ordinary? What were Motorola's responses the first time they replaced the phone? What are their responses now that you are having the same issues with this replacement device?
Otherwise I'd advise you let us know what modifications (apps installed, anything) you had done and continue to do, that will give a variable context to the issue, at least. Other wise we a have an issue with no variables on the actual phone. The more information you give the higher quality the responses you can receive
bothgoodandbad said:
That sounds like a headache.
When were both phones manufactured? What version of KK were you running? Did you upgrade software OTA, if so what did it upgrade to?
Are you saying you never downloaded any apps? never installed anything on the phone? What services did you use? (apps.. anything, what were they?) Were there any other things you noticed out of the ordinary? What were Motorola's responses the first time they replaced the phone? What are their responses now that you are having the same issues with this replacement device?
Otherwise I'd advise you let us know what modifications (apps installed, anything) you had done and continue to do, that will give a variable context to the issue, at least. Other wise we a have an issue with no variables on the actual phone. The more information you give the higher quality the responses you can receive
Click to expand...
Click to collapse
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
quaxer said:
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
Click to expand...
Click to collapse
Thanks, hopefully your info helps someone help you better or hopefully it can help/spark someone truly seasoned in android/moto x etc to chime in
To check your manufacture date boot into your fastboot menu, check image to verify you're there.
Then choose BP Tools and then once that menu loads choose the option for UPC/Manufacture date read out, check for the date when it appears on the screen, maybe you are on a batch that has specific issues.
I've never heard of this issue, yuk sounds terrible. Goodluck! If you do end up finding answers somewhere else can you please come back here and post the resolution?
When I hit BP Tools it just reboots the phone... I don't know what's wrong???
maybe static electricity?
or do you use any cases?
maybe wrong charger?
Multiple devices, different Android versions, Sounds like an app issue to me.
If it happens frequently, then that is good in a way... You could factory reset and don't install a single app. If it doesn't act up for a couple days ..... Install about 5 apps. Go a couple days.... Install 5 more, etc... Etc. When it starts to act up, you know it's an app you recently installed, so it'll be easier to narrow down.
A logcat could help too. Search on that for how. It would likely show what happened at the time of the reboot /shutdown.
quaxer said:
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
Click to expand...
Click to collapse
quaxer said:
When I hit BP Tools it just reboots the phone... I don't know what's wrong???
Click to expand...
Click to collapse
use the volume +up button (once BP Tools is highlighted) and not the power button to select BP Tools I'm assuming that's what's happening, hmm
I would send it back to Motorola again. If the issues continue, tell them you want it replaced with something else like the 2014 Moto X.
Ok -- so the issues stopped completely over Christmas vacation, but I went back to work this morning (I work in a dusty woodworking plant) with my phone in my pocket, and bang, they were back. Every time I pulled my phone out of my pocket it had powered off, and finally it didn't want to power back on. I called Moto, and this time actually got a competent rep on the line. He blamed the issues on static electricity, and I second his opinion, because the machinery I work with tends to create some static, and the dust in my pocket may exacerbate the problem (?)
Anyway, he recommended that I plug the phone in and hold the power button for 2 minutes to drain the static. Voila! It seems to have worked.
Solved for the time being. Thanks everyone for your input.
quaxer said:
Ok -- so the issues stopped completely over Christmas vacation, but I went back to work this morning (I work in a dusty woodworking plant) with my phone in my pocket, and bang, they were back. Every time I pulled my phone out of my pocket it had powered off, and finally it didn't want to power back on. I called Moto, and this time actually got a competent rep on the line. He blamed the issues on static electricity, and I second his opinion, because the machinery I work with tends to create some static, and the dust in my pocket may exacerbate the problem (?)
Anyway, he recommended that I plug the phone in and hold the power button for 2 minutes to drain the static. Voila! It seems to have worked.
Solved for the time being. Thanks everyone for your input.
Click to expand...
Click to collapse
This thread is awesome.
Also, I recommend leaving your phone on your desk/home/car when you work
Or maybe a full-body armor case or something.
Statics & electronics = bad idea. Even if you can drain it and it works, it's still hurting the components inside.
So, it's been a bit, but I just came back to this phone. I never did send it in to Moto, though it seemed to have died completely. It sat in the drawer for a couple of weeks, and now on a whim I plugged it into my computer, and it started up! I had never tried plugging it into a computer, just chargers...
BUT,
In the last 10 minutes it's been sitting here rebooting itself every 2 minutes... I guess I'll try wiping it again (It didn't do the trick last time), but this phone has serious problems.
Hiya, Remember this thread? http://forum.xda-developers.com/htc-one/help/htc-one-m7-stuck-boot-loop-t3028651/page1
Well, we got it working and everything. We used twrp to flash cyanogen mod snapshot (cm-11-20141112-SNAPSHOT-M12-m7.zip) and then flashed gapps right after (gapps-kk-20140606-signed). Everything went fine and the phone was stable. This morning we ended up putting in my friends SIM card. It worked for a moment and then the data stopped working. Stumped we made a call and found out the device was blocked. This deactivated my friends SIM. We do a IMEI Search on Swappa and the phone comes up as reported stolen. Well bummer. At least the phone still works. Well later in the day, my friend starts to use the phone generally on his WiFi and starts to have issues when he installed Facebook and tried to open it, the phone started to lag and he decided to reset the phone. It booted back up fine, then started to lag again. Something about Google now I think popped up and then the phone froze again. he restarted the phone. he got to the HTC logo and it froze. He restarted it again, and now it won't boot. I can say the battery was at about 15% when this did happen. I've had the phone connected to my portable charger all day. I am not sure what to do. I've tried the bright light trick and that didn't work. Any suggestions?
CloudHD said:
Hiya, Remember this thread? http://forum.xda-developers.com/htc-one/help/htc-one-m7-stuck-boot-loop-t3028651/page1
Well, we got it working and everything. We used twrp to flash cyanogen mod snapshot (cm-11-20141112-SNAPSHOT-M12-m7.zip) and then flashed gapps right after (gapps-kk-20140606-signed). Everything went fine and the phone was stable. This morning we ended up putting in my friends SIM card. It worked for a moment and then the data stopped working. Stumped we made a call and found out the device was blocked. This deactivated my friends SIM. We do a IMEI Search on Swappa and the phone comes up as reported stolen. Well bummer. At least the phone still works. Well later in the day, my friend starts to use the phone generally on his WiFi and starts to have issues when he installed Facebook and tried to open it, the phone started to lag and he decided to reset the phone. It booted back up fine, then started to lag again. Something about Google now I think popped up and then the phone froze again. he restarted the phone. he got to the HTC logo and it froze. He restarted it again, and now it won't boot. I can say the battery was at about 15% when this did happen. I've had the phone connected to my portable charger all day. I am not sure what to do. I've tried the bright light trick and that didn't work. Any suggestions?
Click to expand...
Click to collapse
If the phone is stolen do the right thing and hand it in to the police!I would say this is Karma
CloudHD said:
Hiya, Remember this thread? http://forum.xda-developers.com/htc-one/help/htc-one-m7-stuck-boot-loop-t3028651/page1
Well, we got it working and everything. We used twrp to flash cyanogen mod snapshot (cm-11-20141112-SNAPSHOT-M12-m7.zip) and then flashed gapps right after (gapps-kk-20140606-signed). Everything went fine and the phone was stable. This morning we ended up putting in my friends SIM card. It worked for a moment and then the data stopped working. Stumped we made a call and found out the device was blocked. This deactivated my friends SIM. We do a IMEI Search on Swappa and the phone comes up as reported stolen. Well bummer. At least the phone still works. Well later in the day, my friend starts to use the phone generally on his WiFi and starts to have issues when he installed Facebook and tried to open it, the phone started to lag and he decided to reset the phone. It booted back up fine, then started to lag again. Something about Google now I think popped up and then the phone froze again. he restarted the phone. he got to the HTC logo and it froze. He restarted it again, and now it won't boot. I can say the battery was at about 15% when this did happen. I've had the phone connected to my portable charger all day. I am not sure what to do. I've tried the bright light trick and that didn't work. Any suggestions?
Click to expand...
Click to collapse
As the guy says above, however if it is your phone, then get in touch with your network operator and ask them whats going on, the phone has been IMEI blocked by the network and theres nothing you can do to get it working again, you cant even flash a rom as during setup it checks IMEI, and will just reboot loop when it fails to register.
shepppster said:
If the phone is stolen do the right thing and hand it in to the police!I would say this is Karma
Click to expand...
Click to collapse
Seanie280672 said:
As the guy says above, however if it is your phone, then get in touch with your network operator and ask them whats going on, the phone has been IMEI blocked by the network and theres nothing you can do to get it working again, you cant even flash a rom as during setup it checks IMEI, and will just reboot loop when it fails to register.
Click to expand...
Click to collapse
I would turn it in to the police. You know, it's just the fact that this phone didn't come from somewhere local, it came from about 5 states away. On top of that, I was reading some articles and found out that sometimes the network will mark it as stolen and block the IMEI since the original owner did not pay their bill. I bought this phone from ebay. I still have to get my money back, and I need to give the seller a chance to respond, as maybe this is all a misunderstanding. I called the network. They couldn't look up the IMEI or anything for them to contact the original owner. I was told that to get it unblocked the owner of the phone would have to call and report it as not stolen. Also, seanie, are you saying due to the IMEI block, the phone is acting like it is?
CloudHD said:
I would turn it in to the police. You know, it's just the fact that this phone didn't come from somewhere local, it came from about 5 states away. On top of that, I was reading some articles and found out that sometimes the network will mark it as stolen and block the IMEI since the original owner did not pay their bill. I bought this phone from ebay. I still have to get my money back, and I need to give the seller a chance to respond, as maybe this is all a misunderstanding. I called the network. They couldn't look up the IMEI or anything for them to contact the original owner. I was told that to get it unblocked the owner of the phone would have to call and report it as not stolen. Also, seanie, are you saying due to the IMEI block, the phone is acting like it is?
Click to expand...
Click to collapse
The IMEI block would explain it not booting fully into a rom, but are you saying it not charging either ?
If you brought it from ebay I would file a case myself if it was me with paypal and explain what the fault was, paypal will just give you his address to send it too, send it registered post, as soon as it arrives and you have proof of that, paypal will give you your money back, the seller wont get a say in it, ive done it myself before where a seller has sold me faulty goods without me knowing.
Seanie280672 said:
The IMEI block would explain it not booting fully into a rom, but are you saying it not charging either ?
If you brought it from ebay I would file a case myself if it was me with paypal and explain what the fault was, paypal will just give you his address to send it too, send it registered post, as soon as it arrives and you have proof of that, paypal will give you your money back, the seller wont get a say in it, ive done it myself before where a seller has sold me faulty goods without me knowing.
Click to expand...
Click to collapse
Yes, it's not charging either. The reason I haven't gone to paypal yet is I want to give seller time to try and resolve the problem. My friend really wanted this phone. On top of that, WE FIXED THE PHONE! It was broken originally. If it does turn out to be the imei being the problem and the seller gets it back, gets the imei unblocked and it works, he can sell the phone for more. It may not be working now, but I don't feel it's fair for me to get what I bought it for back. That's why I am taking a different route.
CloudHD said:
Yes, it's not charging either. The reason I haven't gone to paypal yet is I want to give seller time to try and resolve the problem. My friend really wanted this phone. On top of that, WE FIXED THE PHONE! It was broken originally. If it does turn out to be the imei being the problem and the seller gets it back, gets the imei unblocked and it works, he can sell the phone for more. It may not be working now, but I don't feel it's fair for me to get what I bought it for back. That's why I am taking a different route.
Click to expand...
Click to collapse
the charging problem could be a few different possibilities, I would try the cheapest option first, the charger and the lead, failing that, you will have to think about things like the charging port or the battery itself, not an easy job being sealed units.
Seanie280672 said:
the charging problem could be a few different possibilities, I would try the cheapest option first, the charger and the lead, failing that, you will have to think about things like the charging port or the battery itself, not an easy job being sealed units.
Click to expand...
Click to collapse
Of course. I don't have any other micro-usb cables. I guess I'll have to wait till later. What I can say is that that I want to confirm the phone will not boot a custom rom if the imei is blocked? Also, I'll note this issue occured after I called ATT to ask them about the phone now that I think about it.
I've had it since Saturday and so far its done it 3 times.
Once yesterday just when I was trying to open the phone with the fingerprint sensor and twice now today when trying to do something with the phone connected to Bluetooth.
This morning I was trying to set up the connection to my in car TomTom Toyota 2 unit for the first time. Got part way through the process then it failed then when i tried again the phone rebooted then it worked.
This afternoon I turned on my Bluetooth connected to the car but it wouldn't do anything then the phone froze and rebooted but then it all worked fine.
I'm not giving up yet but its making me a bit nervous having these issues so soon (better now than later i guess). If it happens more this week ill take it back and might see about a different phone.
Just curious if anyone else has had similar?
This Bluetooth device worked fine previously with my Nexus 5X also on Oreo so its fine software compatibility wise.
Oblox said:
Just curious if anyone else has had similar?
Click to expand...
Click to collapse
I haven't, and I use BT in the car everyday.
Thanks. I'll see if it happens again this week and take mine back if so.
No, I haven't had a single reboot in the 6 days that I own the device.
Oblox said:
I've had it since Saturday and so far its done it 3 times.
Once yesterday just when I was trying to open the phone with the fingerprint sensor and twice now today when trying to do something with the phone connected to Bluetooth.
This morning I was trying to set up the connection to my in car TomTom Toyota 2 unit for the first time. Got part way through the process then it failed then when i tried again the phone rebooted then it worked.
This afternoon I turned on my Bluetooth connected to the car but it wouldn't do anything then the phone froze and rebooted but then it all worked fine.
I'm not giving up yet but its making me a bit nervous having these issues so soon (better now than later i guess). If it happens more this week ill take it back and might see about a different phone.
Just curious if anyone else has had similar?
This Bluetooth device worked fine previously with my Nexus 5X also on Oreo so its fine software compatibility wise.
Click to expand...
Click to collapse
Have you tried performing a factory reset? It might fix your problem. If it persists, then you can send it back for a replacement.
Rebooted again today just in the camera.
Not tried a factory reset yet, will take it into store today and see what they say is best to do. Don't mind doing a reset but then its waiting again to see if it does it again after which isn't something I can easily replicate.
If i can get a new unit id prefer that so i can see if its just my current one with an issue, even with the pain of having to buy a new screen protector.
Lazaros_K said:
Have you tried performing a factory reset? It might fix your problem. If it persists, then you can send it back for a replacement.
Click to expand...
Click to collapse
If the factory reset doesn't work, install the Sony Companion software and run a software repair on it. That may fix the issue. Mine hasn't restarted at all in the 24 hours I've had it, even after using Wifi, Bluetooth, installing lots of apps, using 3G and 4G... However, I installed Newpipe via F-Doid and it crashed at least 4 times on me when I left the video I was watching and came back to it.
No reboots. Two days of heavy use.
I factory reset it soon as I received it and firware update poped up.
Oblox said:
Not tried a factory reset yet, will take it into store today and see what they say is best to do. Don't mind doing a reset but then its waiting again to see if it does it again after which isn't something I can easily replicate.
Click to expand...
Click to collapse
No reboot, have had phone for over a week now.
What did the store recommend you do? Here, they always suggest you factory reset first, same with going to the service center, they actually do that first thing when you send in for repairs.
What did you eventually do? Did it solve your problem?
mhaha said:
No reboot, have had phone for over a week now.
What did the store recommend you do? Here, they always suggest you factory reset first, same with going to the service center, they actually do that first thing when you send in for repairs.
What did you eventually do? Did it solve your problem?
Click to expand...
Click to collapse
I took it into a store the other day and they had no stock so i'm taking it to a different one today. The store i went to said it would be no problem though as id not had it long. Its been rebooting still a few times just when sitting in my pocket doing nothing, ive had the must enter pin after reboot message.
Well on the way to store speaking to my wife (also with XZ1 compact) her phone froze mid call and rebooted. When she rang back she said she was showing a software update. Checked mine when parked and i had it too.
Sony rep happened to be in store today so told him the issue, he had one himself and hasn't experienced or heard of this but said to do a repair with xperia companion to clean flash the new firmware on both our phones. If still having issues then theres nothing more we could do ourselves and bring back to store to swap.
I have another week in which i can change phone or another 3 weeks to swap for a new XZ1 compact.
Will do repairs tonight and hope the problem goes away.
Repaired friday evening, phone rebooted randomly again after freezing sunday. Taking in today to swap for a new unit.
If any similar problems this week with the new one ill ask to swap to a different phone entirely.
Probably need a software update. Mine is running fine on 47.1.A.2.324
Sent from my G8441 using Tapatalk
No i updated that on friday before repairing and the repair had that version too and it still rebooted sunday and today.
Me and my wife got a new unit now so will see how these ones go.
got my first reboot today after plugging the headphone... weird...
profyler said:
got my first reboot today after plugging the headphone... weird...
Click to expand...
Click to collapse
Not good if others are getting this too, lets hope it was a one off for you.
So far just setup and listened to music on my new phone and all is good but there's no pattern to what causes the reboot so will see how the next few days go.
My XZ1 Compact also has the reboot-issue...
Mine has just done the fourth reboot in just a little more than one week. In different situations, with bluetooth in use and without. Once when I tried to call someone, once when I was searching for wifi networks and the other two times in pretty normal "just using it" situations.
As not everyone is having those issues, I think it is some hardware defect and I need to get the phone replaced, right?
Harry
flyhigh79 said:
Mine has just done the fourth reboot in just a little more than one week. In different situations, with bluetooth in use and without. Once when I tried to call someone, once when I was searching for wifi networks and the other two times in pretty normal "just using it" situations.
As not everyone is having those issues, I think it is some hardware defect and I need to get the phone replaced, right?
Harry
Click to expand...
Click to collapse
Difficult to tell. A hard reset might help but it could also be a problem with Android 8 on xz1 that wasnt very well optimized..
Id get the handset replaced, 'repairing' didn't do anything for my issue. Only time will tell if my new handset has the same issues and same for you.
Well this morning I got in the car to go to work and went to turn on bluetooth. Tried OK google no response at all, went to manually unlock and it sat on the lock screen my finger prints not working and wouldnt swipe up for PIN entry. Mic and camera toggle reacted to swipes but didnt do anything. Then it rebooted.
Bye bye Xperia XZ1 Compact, the potential was there but rebooting and dodgy camera is too much to hope for a fix for.