Related
I had to send my ameo for warranty repairs. It took ten days before I had it back even though they initially quoted 3 weeks. I had to dig out my old Tornado (backup, backup, backup, as they say ). Fortunately I was in the eleventh month of my contract and so could get a free repair. They actually gave me a new unit but sent my old keyboard back.
Now my questions are
- how many of us have had to send our units back for repair and
- how far into your contract were you or how old was your unit?
- finally, is there a way around the microdrive issue; precautions, tips, etc, perhaps that would help? Or are we to be ready for another breakdown in 11-12 months time?
Please feel free to post your experience. Many thanks,
Abram.
I sent my X7500 Advantage back to HTC a couple of weeks ago when the microdrive went read-only, with some corrupt data, and various different attempts at formating failed. I got it in May last year, so that's about 11 months for me, too. I had already registered it online, and the warranty period stated there started a few days before I purchased it and ended in July, oddly.
Here in the UK HTC aim for a 5 working day turnaround. I flashed the HTC version of WM6 back onto it and sent it on the Thursday, at my own expense, and they acknowledged receipt on the Friday both by email and phone. I got it back last Wednesday, microdrive replaced but the buttons had all failed. I had to send it off again, again at my own expense, and got it back again yesterday microdrive and buttons working - they had replaced the "switch board" this time.
Another strange thing: when I came to reinstall everything my initial attempts to flash failed. I noticed the SPL had gone back to 1.10, so they obviously did something else too. They've not mentioned to me or listed in the job sheet any mention of finding Olipro 1.20 on it and obviously they've not charged me.
I spent many hours last night reflashing and putting all my software back on it (fortunately I have a list of all my registry keys) - only to notice I downloaded AP 3 Touch rather than AP 3 Dual. Oh well.
Ordered mine the day it appeared on the t-mobile website, so 13 months and counting.
Not one single hardware fault with it so far, apart from the dent from when i dropped it and the little rubber bit falling of the joypad.
Despite the warnings at the start of the microdrive issues on the T-Mobile Ameos I've been absolutely fine since day 1.
seems that the microdrives can be pretty hit and miss.....
7 months of daily use at this point, and no MD problems for me. I had all of my applications installed on it, and its what I used to store all files except the pictures my camera took (sending new pics to flash memory helps reduce problems of blurred pictures since the write delay is shorter). I'll admit though, that when I re-flashed the ROM a few weeks ago this time I installed everything to flash and I'm using flash for my personal files. I haven't touched the MD since, so it might be bad now and I wouldn't know.
3 months
my md died after 3 whole months. It simply disappeared from the file manager. I've got a 7501. After explaining to the tech support guy what a microdrive was(??!!), I sent it in and it was repaired. When I called to check on the status of the repair, I was told that the drive was ok. The controler was supposedly bad, so the motherboard was replaced. It's been about 6 months now since I've gotten it back. I've transfered all the important stuff to an 8 gb micro-sd and I'm just waiting for it to fail again. Once it does, I haven't decided if I'll get it fixed or just get by with the sd.
I wish pocket pc techs would come out with an upgrade to replace the md with a flash drive.
Thinking about it, i did have one problem. I had been playing about with the HTCmail service, and out of curiosity, wanted to see how well the remote device wipe worked on Exchange 2007.
Bloody thing formatted the microdrive and it disappeared from the OS completely.
Tried formatting three times - nothing. My heart almost stopped!
Had to run the recovery thing in WM6 twice before it came back.
I would recommend that if you have an Athena, DON'T use remote wipe. the Microdrive really doesn't like it.
pkchainsaw said:
my md died after 3 whole months. It simply disappeared from the file manager. I've got a 7501.
Click to expand...
Click to collapse
Seems like the forum has quite a few microdrive issue posts. There was one that claimed that the "format Microdive" tool in the unit MUST NOT BE USED. I did use it on mine prior to my MD getting problematic. Did anyone else use theirs?
Abram said:
Seems like the forum has quite a few microdrive issue posts. There was one that claimed that the "format Microdive" tool in the unit MUST NOT BE USED. I did use it on mine prior to my MD getting problematic. Did anyone else use theirs?
Click to expand...
Click to collapse
I've used it before,and have no said problem. 13 months now and still going well. Twice the content was corrupted and files were missing. Soft reset always fixed the problem.
No Microdrive problems yet (touch wood). I have formatted it a couple of times, but using the hard-reset mechanism rather than the 'in-os' Format microdrive tool. My fault was with the 3g radio failing, and I 'think' I've had a complete replacement unit which has different imei, different case but same serial number.
But yes, here's hoping for someone to come up with a way to replace the MD with Flash
Just sent mine for repair
Just mailed my X7500 to Houston for repair. The Microdrive disappeared after about 9 months and I'd continued to use the device with it broken until I had the downtime to part with it. No amount of soft or hard reset did any good, nor did the format tools in ROM or in the OS. Oddly, I thought I heard the faint whirr of the drive when doing an in OS format.
It sure would be nice if they'd swap out the drives with flash memory whenever someone sent one in. The little things are clearly failure prone, as I remember from having a Hitachi 4GB CF card with intermittent problems. This falls in the realm of manufacturing defect, so I would certainly hope when the newly installed Microdrive also fails, they would warranty its replacement as well.
even though, I dont posses athena, I have used MDs when I'd ipaq 2215. They never worked for more than 4months for me. after that duration, I used to experience data corruption blah blah.
May be they got it right with the x7510
It is already very reliable on the older Athena based on my own experience.
I've had my athena for 7 years now and not had a problem with the microdrive....
Confucious said:
I've had my athena for 7 years now and not had a problem with the microdrive....
Click to expand...
Click to collapse
months..right?
Looks like my microdrive is on the way out, struggling to read or write to it without it filling with junk.
Just checked I bought it 30/04/07 so going to see if I can get it warrantied.
I got mine back from their Houston Service Center on Monday. It looked like I got a different screen as the screen I sent back had a screen protector on it and the one I got back didn't. It also has 2 small scratches on it that I am sure were not on the original screen. Lucky me it was not very noticable. Otherwise, I have to send it back again. The internal components are probably new also (most likely refurbished) as the IMEI has changed. However, the serial number is the same and it looks like they printed another S/N, IMEI label and use a piece of cello tape to stick it to the battery cover door with some of it still sticking out of the battery cover door. How tacky! Oh yeah, and they reused my Athena's casing to house the new/refurbished stuff inside!!!!!!
The only good thing about sending it back is that I got an extra battery. When I sent back, I didn't include a battery. The one I got back has one. So now I have 4 batteries altogether. Oh yeah, and the MicroDrive is fixed. Though, I won't hold my breath that it will last for long.
I bought mine during Thanksgiving 2007.
I am installing CM7 (latest Phiremod version) on a refurbed nook bought off ebay the other day.
I initially could not get the CM7 to boot and realized it was because my CW Mod was an older version so I downloaded the new files and replaced the 4 files (uboot etc) with the newest one and when I boot into recovery, Clockwork Mod shows the latest version.
I've used the format tools to format boot/system/cache/data/Davlik and reboot in and out to format more than once just in case.
Install of Phiremod goes well and I can run it. Even on stock speed, it will randomly crash and lock up. I've done permissions repair, but it still does it. I've tried reinstalling the file after I initially installed it (per advice on the Phiremod thread) and it still does it. My older nook runs perfectly.
Is there something new in newer nooks? Do I have a bad one? is new Phiremod version just less stable on newer nooks? Thanks!
Was the refurb sold by B&N or a "3rd party"?
Are you running off eMMC or an SD card?
I'm leaning towards the idea that whatever caused the original owner to return the NC for repair was either not present during the refurb inspection because it was an intermittent problem (you can't fix what you can't find); or the repair agent decided that it was a "non-critical" fault and elected not to repair it.
Unfortunately for you "non-critical" is good enough to meet service levels but not good enough to run CM7.
Or it's a bad SD card, or it's PEBKAC (PEBTSAC?), or ... ?
Can't help with your issue
But I can confirm my new refurbed nook ( from the b&n user on ebay , latest sale ) running CM7 on emmc perfectly fine
it was B&N off ebay.
i tried older phiremods too. it would just crash. my sister said even on stock it would crash. she is sending it back for an exchange. i've never had this many probs installing CM7!!!
i was running off eMMC.
ingenue007 said:
it was B&N off ebay.
i tried older phiremods too. it would just crash. my sister said even on stock it would crash. she is sending it back for an exchange. i've never had this many probs installing CM7!!!
i was running off eMMC.
Click to expand...
Click to collapse
Sounds like a faulty unit. If it was crashing on stock that's the likely reason.
Sounds like they might have a two strike policy on faulty units. They seem to be very liberal on returns (little or no refusals). It's possible that in return, they only scrap the units with glaringly obvious faults. Either that or you you got one of a small number of "twofers". The (rare?) unit that has a second fault that waits for later to show up.
That's the hidden cost of trying to save money on refurbs. You have to take the higher risk of having to send it back again. It's generally a good tradeoff. Remember that you only hear the horror stories in forums lile this. The (many?) success stories never have to ask for help. You just lucked out this time and got a marginal unit that failed (again).
I've got a NC rooted using a 16GB SanDisk mSD card with CM7 on it (not sure precisely the version but don't think it matters). I set this up with help from the xda-developers site in December 2011 and have only used the NC in this mode ever since. I bought the NC as a refurb from the B&N eBay sale in late November 2011 and the unit has a one-year warranty.
Two days ago I was using the NC looking at photos and I let the screen time out and turn off. After this the NC wouldn't turn on; didn't matter what I did. I tried holding the power button down for 10-seconds, I pulled the mSD card and tried a hard reset (power, n, vol- for 5-seconds), tried charging the battery until the stock charging cable light went from orange to green. Did everything I could think of without any signs of life in the NC.
So I brought the NC to a B&N store (without the mSD card or mentioning that I'd been running it rooted) and the moment the guy in the store hit the power button the damned thing booted to the stock OS. The guy told me that this type of thing happens frequently and he thinks there's something about the WiFi in the store "waking up" the NC's (seemed like bull-bleep to me, but the NC was running). The guy told me he'd update the OS from the 1.2v it was at to the current 1.4v and this too could help. I let him do it figuring it probably didn't matter because I should be able to reset it to the factory config if there was something about the 1.4v that screwed up the root.
The guy gave me my NC back after updating it, told me if the problem persisted he'd do an exchange, and I went into my car in the parking lot. There I put in my mSD card into the NC after doing a full shutdown and it booted into CM7 with no problems. Today, however, same problem occurred, couldn't get the screen to turn on. So I pulled the mSD card, tried all the buttons, hard reset, etc. Then I shook the unit and was then able to get it to boot to the stock OS. Did a power down, installed the mSD card, and it booted to CM7 again no problem. That was ten-minutes ago, now the screen is again dead.
Even though the NC has lived a pretty easy life inside an Otterbox case, never been dropped or exposed to water or high humidity, I'm thinking this is a hardware problem and that I should just do an exchange. I've not found any similar posts or information about this type of thing, so I'd appreciate anybody's thoughts about the matter. Specifically:
1 - If I get an exchanged unit, should I be able to boot from my mSD card or will I have to format it and re-install CM7 like I did initially?
2 - If I'm offered a Nook Tablet in place of a NC, should I take the Tablet? I know it's got more power but I understand that rooting it even via mSD card is a PIA and not as straight forward as doing so on the NC.
3 - Is there anything obvious that I'm missing here?
Thanks for the help and apologies if I missed that this is a common problem the fix for which is commonly known.
Turgidson said:
I've got a NC rooted using a 16GB SanDisk mSD card with CM7 on it (not sure precisely the version but don't think it matters). I set this up with help from the xda-developers site in December 2011 and have only used the NC in this mode ever since. I bought the NC as a refurb from the B&N eBay sale in late November 2011 and the unit has a one-year warranty.
Two days ago I was using the NC looking at photos and I let the screen time out and turn off. After this the NC wouldn't turn on; didn't matter what I did. I tried holding the power button down for 10-seconds, I pulled the mSD card and tried a hard reset (power, n, vol- for 5-seconds), tried charging the battery until the stock charging cable light went from orange to green. Did everything I could think of without any signs of life in the NC.
So I brought the NC to a B&N store (without the mSD card or mentioning that I'd been running it rooted) and the moment the guy in the store hit the power button the damned thing booted to the stock OS. The guy told me that this type of thing happens frequently and he thinks there's something about the WiFi in the store "waking up" the NC's (seemed like bull-bleep to me, but the NC was running). The guy told me he'd update the OS from the 1.2v it was at to the current 1.4v and this too could help. I let him do it figuring it probably didn't matter because I should be able to reset it to the factory config if there was something about the 1.4v that screwed up the root.
The guy gave me my NC back after updating it, told me if the problem persisted he'd do an exchange, and I went into my car in the parking lot. There I put in my mSD card into the NC after doing a full shutdown and it booted into CM7 with no problems. Today, however, same problem occurred, couldn't get the screen to turn on. So I pulled the mSD card, tried all the buttons, hard reset, etc. Then I shook the unit and was then able to get it to boot to the stock OS. Did a power down, installed the mSD card, and it booted to CM7 again no problem. That was ten-minutes ago, now the screen is again dead.
Even though the NC has lived a pretty easy life inside an Otterbox case, never been dropped or exposed to water or high humidity, I'm thinking this is a hardware problem and that I should just do an exchange. I've not found any similar posts or information about this type of thing, so I'd appreciate anybody's thoughts about the matter. Specifically:
1 - If I get an exchanged unit, should I be able to boot from my mSD card or will I have to format it and re-install CM7 like I did initially?
2 - If I'm offered a Nook Tablet in place of a NC, should I take the Tablet? I know it's got more power but I understand that rooting it even via mSD card is a PIA and not as straight forward as doing so on the NC.
3 - Is there anything obvious that I'm missing here?
Thanks for the help and apologies if I missed that this is a common problem the fix for which is commonly known.
Click to expand...
Click to collapse
Could be you are experiencing the Sleep of Death (SOD) problem. The unit is still on but can't wake up. The only thing you can do to get out of it is to hard power it off and back on. Hold the power button for a long time. Release and push again until it turns back on.
SOD happens when you leave wifi on all the time and the unit goes into deep sleep. Sometimes you can't wake it back up.
If you have this happening a lot, there is a modded wifi kernel module that helps. If you need it, PM me and I will send you a link.
If you get an exchange it should work just like yours with the SD install. Just put the same card in and should run OK.
You won't get a nook tablet without paying more. If you are happy with the color, I would stay with it. The tablet is still iffy about running other ROMs yet.
Thanks for the info. Does the SOD affect the unrooted NC? If it doesn't then I should be able to trouble shoot the problem by running the NC with the stock OS for several days and see if the problem continues. Does this sound reasonable?
Sent from my SCH-I510 using XDA
Turgidson said:
Thanks for the info. Does the SOD affect the unrooted NC? If it doesn't then I should be able to trouble shoot the problem by running the NC with the stock OS for several days and see if the problem continues. Does this sound reasonable?
Sent from my SCH-I510 using XDA
Click to expand...
Click to collapse
It does not affect the stock. That should be a good test.
Hey
I've begun having problems with my rooted Nook a while ago - it was just freezing at random moments, sometimes unable even to be restarted.
Today I finally decided to perform a factory reset, hoping it would help. Unfortunately, it still happens - at first I wasn't even able to go through the registration process, as it freezed on a wifi page or on a login page. Now I've passed it and am on a home screen, but looks like the factory reset hasn't fixed my problem.. Any ideas what I should do?
I don't have any backups.
From what I've noticed the Nook usually gets back to life when I plug it in, so it might be a battery issue. The problem is, I can't my warranty to replace it, because I left it at home on the other side of the world, where I won't be back until january.. so I'm looking for something I can do on my own.
You only need your serial number to trigger a warranty replacement, as far as I know.
You will need to call BN and be ready to be on hold a long while, but they ought to be able to help you out.
roustabout said:
You only need your serial number to trigger a warranty replacement, as far as I know.
{/QUOTE]
That's a good thing then. And who covers the cost of shipping to US?
I've contacted their CS by email but seems like I'm getting answers not related to my problem..
Click to expand...
Click to collapse
They ship the unit to you, and I think they box is prepaid for the return shipment.
You will need to do this over the phone, as far as I know -- their CS is weak to start with, and I'd be very surprised if you were able to get a warranty replacment moving as a result of an email conversation.
roustabout said:
They ship the unit to you, and I think they box is prepaid for the return shipment.
You will need to do this over the phone, as far as I know -- their CS is weak to start with, and I'd be very surprised if you were able to get a warranty replacment moving as a result of an email conversation.
Click to expand...
Click to collapse
Just called them and looks like I need an american credit card or to go to USA, both being impossible for me (and probably they can send a new nook only to US either). So I'm looking for any other options, don't care about my warranty.
I think that I'd do some sleuthing and figure out if it is the battery.
Use any of the utilities to look at battery voltage and not "percentage".
If the battery is dead I'd try replacing it with a generic 3.7V Li ion battery.
The temperature sensor could be replaced with a fixed resistor if required.
There are some folks who have found that opening the device, disconnecting the battery, then doing something that reads like discharging a capacitor - there is sometimes a problem with the battery, where it is fully charged but the OS thinks it is fully discharged.
Here is a post that describes a fix which might apply for the OP:
http://forum.xda-developers.com/showthread.php?t=1813384
Simple Fix for Freezing Nook Simple Touch
I am going to post this here and on the xda thread referenced above. This may not work for everyone but it worked for me. And it is a simple fix that does not involve taking the NST apart.
Run the Battery Calibration v 1.2 app per the instructions on its opening screen (start app, charge to 100%, touch button in app.) App can be run while nook plugged in.
I found it here
https://battery-calibration.en.uptodown.com/android/download
But note that it is found here also (some of the mirror links still work)
https://forum.xda-developers.com/showthread.php?t=1033529
The Nook Simple Touch runs a modified version of the Eclair version of Android. Finding Eclair compatible apps is becoming increasingly difficult. So finding a battery calibration app that actually works is golden.
MY SYMPTOMS
Nook Simple Touch froze. Battery showed mid 70% range when plugged in to charge. After recharge everything was fine until it got back into the mid 70's again.
Then it started freezing in the 80% range.
I finally decided I needed to do something when it started freezing in the 90's.
I had even ordered a new battery (which will likely fix this issue also.) But decided to try this super simple fix first.
I got this thinking I am buying the best machine available for streaming and from day once , have been plagued by problems.
First on opening the unit, the AC adapter was faulty. It turned out to be a piece of plastic stuck between the contacts.
Anyway I solved that problem on my own as shipper refused to entertain any claims outside the USA.
Then when it finally got going, I noticed most apps had loading circles going around, and were waiting to download. Tried everything possible and they would not move ahead . Finally cleared cache and data on the Google Play Store app and the app started downloading for precisely one application then it stopped and again same circling. I had to clear data on the Play store app every time to update each and every app on the machine.
Then i couldnt find my favorite apps in the app store. Turns out , Shield does not support. Ok, no problem, i said lets compromise and move on.
Downloaded MX Player Pro from the Play Store and sat down to watch a 1080p movie on the USB drive and again the loading circle popped up on the screen. Buffering on a 1080p file from a usb 3.0 flash drive !!! I copied the file onto the HDD and again the same problem. I had no idea how to watch this movie, BTW had watched it a night before perfectly on my Alphawise H96 Pro+.
Then one by one all the apps started crashing.
I decided to do a factory restore which lasted 2,5 hours. After restore, same problem, all apps crashing.
I do not have anything connected to the Shield , no usb drive. no air mouse, nothing. Both ports are empty.
The surprising thing is even Google play store crashes , also the Lean back Launcher and the system crashes.
I called up Nvida support and they say we do not support the Shield as you are not in the USA. Guys, even the chinese from Aliexpress support you and give a replacement if item is faulty. All they ask is a video showing the problem. In todays times, there are going to be non us customers buying from the Usa, you need to support them also.
Stuck with a Lemon.
Cannot even sell it off as whoever buys it from me will throw it back in my face. The dam thing is just a few days old.
Havent slept three nights, trying to solve the problem, got finally tired and have connected the Alphawise to the TV and Shield goes back into the box
There are lots of other people complaining about similar issues but no fixes from Nvidia ?
If someone can please suggest something which I can try, I will be highly obliged. Else I am stuck with a $300 paper weight.
I did a Full Reset (2.5 hours) once and a Fast reset , hoping it would solve the problem. But no luck.
Please help, someone, please.
Wow, that sounds like a whole lotta suck.
Sorry to hear you had such hardship.
My Pro model had the blurry Recommendations section, which was a symptom of the faulty harddisk, for ages (before I knew about the mass RMA they had) and, one day, the Shield stopped responding to input, even from the capacitive power button on the device itself.
So I pulled the plug but it wouldn't turn back on afterwards.
I applied for a replacement here:
https://nvidia.custhelp.com/app/home
Where'd you get yours?
I'd purchased mine as soon as it was released through the US Amazon - I couldn't wait the extra month or so for it to be released in Europe
Despite this, they processed the replacement. I sent it off to the Netherlands, if I recall correctly, and they returned the refurbished unit shortly afterwards, which has been working fine ever since; all the useless recommendations load quickly and there's no slow down or stuttering like I'd experienced before. I also got a new controller in the box with it and an EU plug. :good:
Anyways, my point is that it shouldn't matter where it was purchased. Try that link and see if you can't get it sorted.
I wish you the best!
DreadfulDrummer said:
Wow, that sounds like a whole lotta suck.
Sorry to hear you had such hardship.
My Pro model had the blurry Recommendations section, which was a symptom of the faulty harddisk, for ages (before I knew about the mass RMA they had) and, one day, the Shield stopped responding to input, even from the capacitive power button on the device itself.
So I pulled the plug but it wouldn't turn back on afterwards.
I applied for a replacement here:
https://nvidia.custhelp.com/app/home
Where'd you get yours?
I'd purchased mine as soon as it was released through the US Amazon - I couldn't wait the extra month or so for it to be released in Europe
Despite this, they processed the replacement. I sent it off to the Netherlands, if I recall correctly, and they returned the refurbished unit shortly afterwards, which has been working fine ever since; all the useless recommendations load quickly and there's no slow down or stuttering like I'd experienced before. I also got a new controller in the box with it and an EU plug. :good:
Anyways, my point is that it shouldn't matter where it was purchased. Try that link and see if you can't get it sorted.
I wish you the best!
Click to expand...
Click to collapse
I have the 2017 shield pro. and all though I wouldn't say it has been a nightmare, it hasn't been without its problems; such as apps randomly not responding with a message saying close the app or wait...slow down of apps opening at all to include settings not opening...streaming apps to include Netflix not playing or simply force closing...even Leanback Launcher stopping with the message Leanback Launcher has stopped...close or wait....I finally bit the bullet after posting on this forum and getting no response and did a wipe of data and dalvic from TWRP and re-flashed the 6.1 or 6.2 firmware. It seems to be running smooth so far. Got my shield from amazon. wouldn't expect this many problems from a $300 device that claims to be the best on the market. When it works without problems it is a great device!
Hope you get it sorted out. If nothing else works, it may be worth it to fastboot boot TWRP if you have an unlocked bootloader...wipe data and dalvic and install the 6.1 firmware update.
Real sorry to here you had so many problems Mate. Hope they sort it for you ....But if they fail to deliver (which they really should not, Take no excuses from them ,Polite but firm)
You have the option to get a Donner clone from a thread based in these forums ,along with further help in the threads below.
https://forum.xda-developers.com/shield-tv/development/nvidia-shield-tv-ssd-t3402580
https://forum.xda-developers.com/shield-tv/general/guide-migrate-to-ssd-hdd-size-satv-pro-t3440195
I would almost Guarantee that it is your Hard drive at fault ...as your descriptive clearly points to this as the culprit.
I have read a number of post and comments in them threads ,and it is invaluable ... I am Dam sure many will bend over backwards to help you out.
Real shame the same can not be said concerning NVIDIA ...Hopefully they see your Dilemmas and respond dutifully.
Good Luck!
Best Regards,