Hi everybody,
11 months ago I bought a brand new HTC Desire Z (bought in Belgium, in a retail shop, no webshop).
During the time I rooted the phone, installed several custom ROM's, for example: now it is running Andromadus Audacity B3.
Now I have a (hardware) problem with my phone:
sometimes the phone goes off. The phone doesn't shutdown (no software fault), but i think it is the battery that doesn't make contact with the motherboard.
I can reproduce the problem very simple: moving the battery a little bit when the phone is running.
Cleaning the contacts doesn't make sense; the battery have a solid contact with the 'clips'. So I think there is something wrong on the motherboard of the phone.
I want to send the phone back to HTC because it is still in warranty.
Should they make noise about the fact that the phone is rooted and there is a custom ROM installed?
Should I restore the phone back to factory defaults before sending it back?
How can I do this (setting the phone back to the original firmware/ROM and unrooted).
Or shouldn't it make sense?
Can someone help me?
Thx!
Most people don't seem to have a problem sending back rooted phones but some do. If you don't mind the small amount of effort involved nipqer has a guide to revert back, search the development thread
Sent from my HTC Vision using xda premium
It is understood that when you root your phone the supplied warranty is null and void. You are doing something to the phone that you were not meant to do by the manufacturer/retailer but is fully capable of doing it.
If you want to attempt to return the phone for a claim under warranty, you will have to revert your phone to it's original factory state. That means getting S-ON (if you achieved S-OFF), unrooting the phone, restoring the factory ROM and restoring the factory CID (if you achieved SuperCID).
There are people who have gotten their phones serviced while S-OFF and rooted, but it will be at the final discretion of the repair shop/manufacturer if they will go ahead on a repair on a device that is technically out of warranty.
Good luck.
Here, follow my guide to unroot http://forum.xda-developers.com/showthread.php?t=1442988
-Nipqer
Thx very much guys!
I won't take the risk that the serial number of my phone will be registrated as 'warranty void' if they see that the phone is rooted and no original ROM.
I will take a backup of the current ROM and all settings, and I will follow the guide posted in this thread.
Fingers crossed, I have to leave my Desire Z for about 4 weeks and going backup to a Nokia 6300
Thx for all the answers!
Can't understand it.
I followed the guide to go back to stock rom/settings succesful.
The phone was back in it's original state (thx for the tutorial!).
When I tried to reproduce the problem with original firmware: impossible, phone was working for 100%.
Now I rerooted the phone, clockworkmod installed and so on. I reflashed my backup of Audicity B3, and now the phone is working for 100%?
I can't understand... It couldn't be a software problem, or am I wrong? The phone didn't reboot but was 'shut off' in just 1/4 second.
What should I do?
Waiting further, to know if the problem comes back...?
Wow I thought I was the only one!!! I just had this problem a few days ago. Happened if I pushed the bottom of the metal door/cover for the battery. EVERY time I just pushed slightly on it, the phone would immediately shut off.
Seems I have fixed it by just taking the battery out and cleaning off the contacts. I haven't had the problem in a while now. Will report back if it does happen again. But maybe it cleaned itself off from you removing/replacing the battery so many times? lol sound stupid I dunno.
Related
My G1 is only 5 weeks old, yesterday while using TeleNav GPS my phone overheated or something and now it wont charge. I need to exchange it for a new G1, does anyone know if tmobile will reject me because the phone is rooted and has the JF mod?
you can unroot your phone before sending it in. if you send it in with mod'd software you may be charged for an out of warranty fee. just flash RC29 NBH and then apply the official signed RC33 full update.
yeah, im having an issue going back to RC29, keep giving me an error. Do I need other files besides the RC29 update.zip file?
All you have to do is get the rc30.nbh file and reflash. That's it all done. You can find it some where on xda
rc30.nbh
http://forum.xda-developers.com/showthread.php?p=3014684
In all honesty, with T-Mobile now "supporting" rooting on their own support forums, I think they will be accepting all G1's (rooted and not) as long as it isn't a software problem or caused by flashing (brick due to bad flash)
rooting never violated your TOS, although it could void a warranty but I believe you can't void a warranty for hardware if you update software.
G1 trade-in
As longas the sticker on the inside of the phone (where the battery goes) is white, NOT red, and there is no phyiscal damage to the device, you should have no trouble geting a replacement phone. You could also revert the phone back to it's unmodded state, but there's really no need to. Just order your new phone, by phone, and not through the dealer. Either way you'll still have to wait 2 or 3 days.
I have a Defy that's from Movistar Chile (Froyo 2.2.2 "3.4.2-108_JDNL-2"), I was looking to root it and install another rom, because the phone randomly reboots when entering certain specific towers, and see if my problems were solved.
Since the only way to change the radio was flashing other Full SBFs, I wanted to try other, the thing is that the SBF for my region/carrier is nowhere to be found. And I kinda need some way to go back to stock in case I need to use the warranty.
Besides, I installed 2nd init, and I'm worried that because the uninstall is partial the tech support could reject the phone. Do I have a solution or am I screwed?
Best Regards,
Lugaidster
Here You have almost all roms to Defy. If You wont find yours 2.2 try to find 2.1 and then use MSU to upgrade to Froyo. 2nd Inint will be removed after full flash sbf.
Sorry for my ignorance, but what is MSU?
Best Regards,
Lugaidster
Motorola Software Update which You can find on Motorola's site.
One last question, when you say 2.1 in your other post, do you mean 2.2.1? I'm under the impression that I can't downgrade to Ecclair or Froyo 2.2.1 if my phone came with Froyo 2.2.2 (because of the whole eFuse deal).
Best regards,
Lugaidster
Right, I forgot about unsigned kernels so if You have Defy with Froyo without any upgrade You can't downgrade it to Eclair and then upgrade to Froyo back.
I'm afraid that You wont find this rom. Only way is to find someone with it and ask for nand backup and then uninstall 2nd init. But as I remember in my region (CEE) before upgrade to Froyo people who had damaged phones with installed beta or chinese Froyo was sending their phones to Motorola on warranty and in few cases Motorola didn't asked about different software and they repaired hardware damages. If You wont find it u can flash it with some 3.4.2_107 and try to send it to Motorola if You need warranty repair.
Ok, thanks anyway. I think I'll take my chances and leave it as it is. I guess I'm stuck with a randomly-rebooting phone (Already took it to tech repair and they said that there was nothing wrong with the phone, and unless there's something wrong with it they won't change it).
Best Regards,
Lugaidster
BTW it's normal in Defy rebooting sometimes. I had Defy normal on stock Eclair and next Froyo and now I have Defy+ on stock 2.3.4 and now testing CM7 and on both phones and all firmware versions phones had 3-4 randomly reboots in week.
The thing is that more often than not, it reboots like 10 times in the span of an hour. It's incredibly annoying.
When it keeps rebooting turn on airplane mode and watch for results. If it stop rebooting it's problem with sim card. I heard that in few cases T-Mobile cards had problems in Defy and device keeps rebooting all the time and freezes. It can be problem with SetVsel if You have one, set defaults values. But if airplane mode helps just change sim card on new carrier or normal/micro sim (different that one You have now). Hope it should solve Your problem.
As you mentioned, airplane stops it from rebooting, the thing is that it doesn't matter which simcard it has, it reboots either way, I have it locked so I haven't tried with other carriers, but with the current carrier it reboots like hell. The most annoying thing is that it does so only on certain locations and I happen to live in one of those. I leave for work and it stops rebooting until I return.
Try to mix 2G/3G only and with/without data transfer and set network manually/auto.
I'll try that, but I won't keep my hopes up... I'll notify in case it fixes something, since I can't be the only one with this problem.
Best Regards
Nope You're not. Here You have similar problem. I didn't read whole thread but parts about sim card problem. Maybe it gonna help You somehow.
Well when I look at the advanced radio settings I keep getting "imei: unknown" status at my nexus 4. Together with baseband unkown and all mobile connectivity seems wrong. I am currently running the stock run and not updated anything or done anything (heck I took great effort to "relock" it when I unlocked it to FIX this. (On top of this: loading takes ages, sometimes refusing to load till battery level drops below 10%).
I've tried flashing android 4.4 (but this creates the soft-brick looping while starting android).
I've tried factory reset,
I've tried hard reset
And I've tried the manual resets by flashing 4.2.2 back on.
In all combinations
What can be done, and how can I start using my mobile phone as a PHONE again? Anything but asking for a warranty (as I sadly void It when I had to downgrade from 4.3 to 4.2 to fix a bug introduced in 4.3 that prevented deep sleep)
From what I have read, you cannot run any rom that is newer than 4.2.2 if your phone has imei problems. The only way to fix the imei issue is to send it to LG.
audit13 said:
From what I have read, you cannot run any rom that is newer than 4.2.2 if your phone has imei problems. The only way to fix the imei issue is to send it to LG.
Click to expand...
Click to collapse
So I'm stuck? As my warranty is "void" because I "rooted" the phone to get 4.2.2 back on?
Great having to throw away a phone less than 5 months old. Last time I bought a smartphone it seems; I can't live with those stupid warranty rules rooting & modifying oses runs through my veins. I specifically bought the nexus (and thus stock android) for that.
PS: why is there a "5 minute wait" on UPDATING posts here?
pulli23 said:
So I'm stuck? As my warranty is "void" because I "rooted" the phone to get 4.2.2 back on?
Great having to throw away a phone less than 5 months old. Last time I bought a smartphone it seems; I can't live with those stupid warranty rules rooting & modifying oses runs through my veins. I specifically bought the nexus (and thus stock android) for that.
PS: why is there a "5 minute wait" on UPDATING posts here?
Click to expand...
Click to collapse
I don't know if that still affects your warranty, but you can unroot and re-lock the bootloader using the Nexus Rooting Toolkit or another method of your choosing...
Hi,
I have been having a ongoing problem with my Galaxy Note 3 N9005 in where after the 5.0 upgrade (stock over air) it has been restarting pretty much 4-5 times during the day, and a number of times while even just sitting on the desk doing nothing.
Since I am still on contract with my supplier in NZ, I took the phone back to get repaired, in which Samsung sent it back to state "Software corruption, reloaded software".
I didn't believe them, but hoped it was correct - but sure enough the same thing happened. So I once again took it back, where they have once again told me the same thing. It is now the third time I have done this, with Samsung saying the same thing!
Now I am at wits end, and have asked for replacement, but I am being told "It is due to your google account being corrupt, and it is causing software corruption....." *sigh*
So now not only is Samsung just not helping, they are blaming my Google accounts for causing the issue. Which btw - I didn't setup the last time, and still it restarted - but they are ignoring that fact!
Anyway - the advice I want to get is has anyone else had the same issue with the Galaxy Note 3 after upgrading? I know there is no way to rollback 5.0 to old version, but did anyone fix the issue by Root and then adding another ROM (I don't want to root this phone, but to be honest I also can't afford right now to replace so I am looking at options)
Right now I am facing a ongoing battle with Samsung and my provider to replace the phone, but they are fighting it a lot and to be honest I have lost my patience so I am thinking to just drop them, root/flash new Rom, and then go to another provider - and probably never buy Samsung again when I can finally upgrade.
(used to love Samsung products but this behavior I have had is certainly making me think twice before I touch them again)
Since they refuse to accept warranty you can try to flash twrp. Then clear everthing(system/caches). Then back to stock with odin. There might be leftover of corrupted files that could cause reboot.
But later they have a better reason not to accept your phone, knox tripped.
And you can actually downgrade to 4.4.2. Just flash firmware of the same csc to be safe.
Sent from my SM-N920C
Do you have memory card installed? if so then scan you memory card for possible viruses.
Actually I have this issue too before.
Even if I left it lying on the table, it can restart by itself.
I tried to update to latest PB1 rom, the update failed, the phone restart while ODIN updating.
So I use Kies recovery and got it working again.
After that, i tried again update to PB1 rom using ODIN. and now no issues at all.
I dont know which one did the trick whether update to PB1 or KIES recovery.
Goldendawn said:
Hi,
I have been having a ongoing problem with my Galaxy Note 3 N9005 in where after the 5.0 upgrade (stock over air) it has been restarting pretty much 4-5 times during the day, and a number of times while even just sitting on the desk doing nothing.
Since I am still on contract with my supplier in NZ, I took the phone back to get repaired, in which Samsung sent it back to state "Software corruption, reloaded software".
I didn't believe them, but hoped it was correct - but sure enough the same thing happened. So I once again took it back, where they have once again told me the same thing. It is now the third time I have done this, with Samsung saying the same thing!
Now I am at wits end, and have asked for replacement, but I am being told "It is due to your google account being corrupt, and it is causing software corruption....." *sigh*
So now not only is Samsung just not helping, they are blaming my Google accounts for causing the issue. Which btw - I didn't setup the last time, and still it restarted - but they are ignoring that fact!
Anyway - the advice I want to get is has anyone else had the same issue with the Galaxy Note 3 after upgrading? I know there is no way to rollback 5.0 to old version, but did anyone fix the issue by Root and then adding another ROM (I don't want to root this phone, but to be honest I also can't afford right now to replace so I am looking at options)
Right now I am facing a ongoing battle with Samsung and my provider to replace the phone, but they are fighting it a lot and to be honest I have lost my patience so I am thinking to just drop them, root/flash new Rom, and then go to another provider - and probably never buy Samsung again when I can finally upgrade.
(used to love Samsung products but this behavior I have had is certainly making me think twice before I touch them again)
Click to expand...
Click to collapse
Munawar Mehmood said:
Do you have memory card installed? if so then scan you memory card for possible viruses.
Click to expand...
Click to collapse
Thanks - but no I don't - these are the first things I did when it started happening.
When it started happening I did factory reset, removing memory card, factory reset again, didn't restore backup from google... etc etc - so the general admin tech stuff.
Because under warranty (2 year contract) I didn't want to do anything more so sent to provider to get dealt with (into my 22 months of 24 months). For the last 4 months it has been to them a number of times for the same thing.
Now each time they send it back they claim "software corrupt" and that there is no hardware issue. So doing a software root and mod change for me is a hope - and probably not a good one - that the Stock 5.0 is the problem on this phone. And only going down this road because I am coming out of the warranty and right now I have a phone I can't really use, and damn Samsung won't support it or fix it (which is really all I want them to do!!) sigh
syamsoul said:
Actually I have this issue too before.
So I use Kies recovery and got it working again.
Click to expand...
Click to collapse
Thanks for this information, because in fact you are not the first time I have read this but I am not sure what the Kies recovery is - is there some instructions you have because maybe that is what should try, because I have seen other people on Google state this has helped them with restarting, but that was usually after Mod fix. Maybe there is something in the 5.0 update on GN3 that might cause this?
Rosli59564 said:
Since they refuse to accept warranty you can try to flash twrp. Then clear everthing(system/caches). Then back to stock with odin. There might be leftover of corrupted files that could cause reboot.
But later they have a better reason not to accept your phone, knox tripped.
And you can actually downgrade to 4.4.2. Just flash firmware of the same csc to be safe.
Sent from my SM-N920C
Click to expand...
Click to collapse
Thanks I didn't think from what I was reading that you could backwards - in fact Samsung have just down right refused, which is all I have asked them to do in the last two times - "Just flash back to the version that was on there last 4.4.2. because that didn't cause any issues!" However, they are stating very firmly that you can not rollback or re-flash back to a previous version.
Is there any instructions which are for the 9005? I have seen for the 900 but the instructions state very clearly you can't use them for 9005.
Goldendawn said:
Thanks I didn't think from what I was reading that you could backwards - in fact Samsung have just down right refused, which is all I have asked them to do in the last two times - "Just flash back to the version that was on there last 4.4.2. because that didn't cause any issues!" However, they are stating very firmly that you can not rollback or re-flash back to a previous version.
Is there any instructions which are for the 9005? I have seen for the 900 but the instructions state very clearly you can't use them for 9005.
Click to expand...
Click to collapse
Just flash the firmware with odin. Factory reset in recovery after it's done. That's it. There are a lots of threads about going down such this:
http://forum.xda-developers.com/gal...o-downgrade-lollipop-to-kitkat-t2990262/page2
I suggest you read through before you go further. They are mixed results. Some successful. Some did not. That is why it is better to flash the same csc firmware.
I even able to downgrade my S6 from 6.01 to 5.1.1 without issue but of course it's different phone.
Sent from my SM-N920C
---------- Post added at 08:38 PM ---------- Previous post was at 08:15 PM ----------
I sent you a PM.
Sent from my SM-N920C
Bought a OTG from China, used one, left plugged into the phone as I slept...don't know if it's the cause of my troubles to start happening, or if the Twitter app I installed at the same time is the cause.
The phone became TROUBLE and I eventually decided to try going back to stock. I did manage to get stock on but couldn't use because the phone immediately would display the dreaded "Unfortunately.......", which pops up so often that you cannot do anything. So I decided to do a full wipe from factory recovery. Since then, the phone wont power on at all! I have left it to charge overnight, all day, NO POWER!!!! I have read many similar accounts. I lost as what to do! I had ZERO power issuses before. Saw a vid where a guy says the power switch is faulty. He ordered one from eBay and replaced it. 1) I don't think it's the case. 2) don't think I wanna try soldering, etc.
Any help would be appreciated!!!
I have the 910W8 from Rogers in Canada. ODIN flashed with no problems (used the latest firmware from sammobiles for my phone) but would get that error after the flash, causing it to be unuseable. I flashed a second time and same thing. That's when I decided to do a wipe from recovery. Now it won't boot up.
Wow! NOBODY?!
kojam said:
I have the 910W8 from Rogers in Canada. ODIN flashed with no problems (used the latest firmware from sammobiles for my phone) but would get that error after the flash, causing it to be unuseable. I flashed a second time and same thing. That's when I decided to do a wipe from recovery. Now it won't boot up.
Click to expand...
Click to collapse
Cannot believe nobody has replied. I did get one of the usb things from a very nice member (i have to register myself as someone who now has one) but the phone is still not working.
Having done some confusing reading to try to fix mine but don't think i can.
Wondering if there's a good, reliable, store in the GTA (north end preferrably) that can do repair with JTAG? Wondering if there's any hope in recovering this phone. I get the impression that there's a good chance JTAG repair can bring it back to life.