Database Users

Rooted/custom ROM and warranty

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.

Help! IMEI=0 only 4.2.2 boots no signal

I was on stock android version 4.2.2 with stock recovery and unrooted when I received the 4.3 version notification after updating the boot animation remained stuck on the X logo for hours and clearing cache,data from stock recovery didn't help it boot. I flashed the factory 4.2.2 image and it finally booted but I had no phone signal only wifi was working. On inspection I discovered that the baseband was 'unknown' and IMEI number, IMEI SV reset to zero. Strangely the baseband was being detected while in bootloader mode. I have tried both custom recoveries, flashed various roms through custum recovery as well as stock factory images right uptil kitkat. These are my findings:
All Android 4.2.2(and 4.2.1) based roms boot but with baseband unknown and IMEI 0 rendering the phone unable to make calls and send/receive text messages.
All Android 4.3 roms don't boot are stuck at boot animation(flashing old radios like 0.48 and other older versions didn't help)
All Android 4.4 roms also behave the same way as 4.3 i.e stuck at boot animation.
Bottom line is I am stuck on Android 4.2x with a non working radio IMEI=0.... My device is now a mere tablet with inability to be updated. I have seen many people with similar problems but all such threads remain unresolved. I don't know what bug in 4.3 has done this to my phone I even tried the 99 percent working unbrick method but to no avail. I am considering selling this phone at a big loss(cant do much because I am in Pakistan) if any experienced developer is able to help me with fixing my phone(if that's even possible) then I shall be really grateful. Otherwise its bye bye Nexus 4.

liquidmetal88 said:
I was on stock android version 4.2.2 with stock recovery and unrooted when I received the 4.3 version notification after updating the boot animation remained stuck on the X logo for hours and clearing cache,data from stock recovery didn't help it boot. I flashed the factory 4.2.2 image and it finally booted but I had no phone signal only wifi was working. On inspection I discovered that the baseband was 'unknown' and IMEI number, IMEI SV reset to zero. Strangely the baseband was being detected while in bootloader mode. I have tried both custom recoveries, flashed various roms through custum recovery as well as stock factory images right uptil kitkat. These are my findings:
All Android 4.2.2(and 4.2.1) based roms boot but with baseband unknown and IMEI 0 rendering the phone unable to make calls and send/receive text messages.
All Android 4.3 roms don't boot are stuck at boot animation(flashing old radios like 0.48 and other older versions didn't help)
All Android 4.4 roms also behave the same way as 4.3 i.e stuck at boot animation.
Bottom line is I am stuck on Android 4.2x with a non working radio IMEI=0.... My device is now a mere tablet with inability to be updated. I have seen many people with similar problems but all such threads remain unresolved. I don't know what bug in 4.3 has done this to my phone I even tried the 99 percent working unbrick method but to no avail. I am considering selling this phone at a big loss(cant do much because I am in Pakistan) if any experienced developer is able to help me with fixing my phone(if that's even possible) then I shall be really grateful. Otherwise its bye bye Nexus 4.
Click to expand...
Click to collapse
try this for reference http://blog.falcondai.com/2013/10/fixing-galaxy-nexuss-imei-number.html

But this post specifically required the IMEI number to be exactly the SAME as mentioned otherwise it says the method wont work and it also seems to be T-Mobile blocked IMEI or something I don't think this fix is for my issue(correct me if I am wrong I am a noob lol)
My IMEI issue seems to linked to the Android 4.3 update which has broken something and this problem seems quite common on Nexus 4 as I came across many threads with people with exactly the same issue as mine. All the replies given usually say wipe cache and/or flash factory image sadly the problem remains.
I am really disappointed at my decision to buy the Nexus 4(my year long experience with the Galaxy Nexus was without issues) I never expected Google to release an update that breaks radios of many users(just google this problem many seem to have exactly the same symptoms as mine but the problem remained unresolved) and then remain silent despite many complaining on their product support forums.
Seems the device is beyond repair like most affected Nexus 4 phones(some have luckily got fixed by themselves it seems and IMEI appeared again)
Guess I will have to sell it at a very low price. I am skeptical about buying even the Nexus 5 now should I run into another dreaded unfixable IMEI issue caused by Google's own update(just paranoia I guess)
If only someone comes up with some fix I guess that will help plenty of disappointed Nexus 4 owners.

liquidmetal88 said:
But this post specifically required the IMEI number to be exactly the SAME as mentioned otherwise it says the method wont work and it also seems to be T-Mobile blocked IMEI or something I don't think this fix is for my issue(correct me if I am wrong I am a noob lol)
My IMEI issue seems to linked to the Android 4.3 update which has broken something and this problem seems quite common on Nexus 4 as I came across many threads with people with exactly the same issue as mine. All the replies given usually say wipe cache and/or flash factory image sadly the problem remains.
I am really disappointed at my decision to buy the Nexus 4(my year long experience with the Galaxy Nexus was without issues) I never expected Google to release an update that breaks radios of many users(just google this problem many seem to have exactly the same symptoms as mine but the problem remained unresolved) and then remain silent despite many complaining on their product support forums.
Seems the device is beyond repair like most affected Nexus 4 phones(some have luckily got fixed by themselves it seems and IMEI appeared again)
Guess I will have to sell it at a very low price. I am skeptical about buying even the Nexus 5 now should I run into another dreaded unfixable IMEI issue caused by Google's own update(just paranoia I guess)
If only someone comes up with some fix I guess that will help plenty of disappointed Nexus 4 owners.
Click to expand...
Click to collapse
Your IMEI information should be on your box if you still have it. Now there has to be a tutorial out there somewhere to enter IMEI info for your phone. I know I found some stuff when trying to this to a Galaxy S3.... I would keep looking or contact Google for a RMA

Still no luck. Now flashing the just released Kitkat image, who knows it may work.
Edit: Still the same result.
Wonder why only 4.2.2 based roms boot but 4.3x and 4.4 based ones do not. I also don't get why baseband is detected in the bootloader mode but not within the OS.
And what is the process of this RMA thingy? Is it applicable for countries outside US? I am from Pakistan btw and got it from a local shop. Nexus 4 can't be bought from Play Store in my country

Any Luck yet?
liquidmetal88 said:
Still no luck. Now flashing the just released Kitkat image, who knows it may work.
Edit: Still the same result.
Wonder why only 4.2.2 based roms boot but 4.3x and 4.4 based ones do not. I also don't get why baseband is detected in the bootloader mode but not within the OS.
And what is the process of this RMA thingy? Is it applicable for countries outside US? I am from Pakistan btw and got it from a local shop. Nexus 4 can't be bought from Play Store in my country
Click to expand...
Click to collapse
Hi @[liquidmetal88] did you get any solution, exactly the same issue as yours. Please share if you have solved it, would be of great help

sambitshankar said:
Hi @[liquidmetal88] did you get any solution, exactly the same issue as yours. Please share if you have solved it, would be of great help
Click to expand...
Click to collapse
Am also facing this issue...only the 4.2.2 boots with no basebanc versiono no IMEI no. and doesn't detects any Sim card

Unlike Samsung phones, the imei cannot be re-injected into the phone's file system. People have had to return the phone to Google to have it fixed.
If you try to install a stock 4.3 or 4.4 ROM, the phone will not even boot to the desktop.

[Q] SM-N9000W major problem help

Hi all, I'm new to XDA so hopefully someone can help me. I purchased a brand new unlocked note 3 N9000W8 in canada from a cellphone store on Monday Morning. The phone was great and worked without a hitch and had android 4.3 on it.
Later on during the day, there were numerous news headlines regarding a 4.4.2 was officially released. So i decided to do the software update. With failed attempts with the message "Your device have been modified, Software updates are not available"
I checked my Settings > about device > status > device status and it states custom or modified. I am unsure how this is possible thinking it was a brand new phone. After some in depth reading i powered off the phone and check the android download mode (power, home button vol down key combo).
It states device status: custom, firmware: custom, knox 0x1 (which meant my warranty was gone essentially). I proceeded to call the shop i purchased the phone at, and the manager said they buy the phones from the distributor which unlocks them before it gets in their hands. so it must have been rooted prior to me receiving the phone.
Long story short...i know its been quite the reading already my appologies. I used samsung KIES to backup the phone and it updated it back to the stock firmware 4.4.2. I was prepared to loose the root as i dont need it. More concerned about the warranty. With the device and firmware status back to original i can now do OTA updates, however
Problem i have now is after the factory firmware upgrade to stock, my sim no longer works on the network. Seems as if the device has a sim lock, but it never asked for one. A local cellphone shop in st.catharines said there might be an issue with the baseband after the official update.
before the update, i tried all the suggestions such as unmounting the sd card, wiping cache, using supersu to unroot.
Can anyone chime in on what the problem may be? I go to school here, so if all else fails i will have to go back to toronto where i purchased it, and have them figure it out. just a hassle for me to get there without a car.

i just realized this was posted in the wrong section of the forum. sorry mods, can it be moved to Q/A?

tedmonddo said:
Hi all, I'm new to XDA so hopefully someone can help me. I purchased a brand new unlocked note 3 N9000W8 in canada from a cellphone store on Monday Morning. The phone was great and worked without a hitch and had android 4.3 on it.
Later on during the day, there were numerous news headlines regarding a 4.4.2 was officially released. So i decided to do the software update. With failed attempts with the message "Your device have been modified, Software updates are not available"
I checked my Settings > about device > status > device status and it states custom or modified. I am unsure how this is possible thinking it was a brand new phone. After some in depth reading i powered off the phone and check the android download mode (power, home button vol down key combo).
It states device status: custom, firmware: custom, knox 0x1 (which meant my warranty was gone essentially). I proceeded to call the shop i purchased the phone at, and the manager said they buy the phones from the distributor which unlocks them before it gets in their hands. so it must have been rooted prior to me receiving the phone.
Long story short...i know its been quite the reading already my appologies. I used samsung KIES to backup the phone and it updated it back to the stock firmware 4.4.2. I was prepared to loose the root as i dont need it. More concerned about the warranty. With the device and firmware status back to original i can now do OTA updates, however
Problem i have now is after the factory firmware upgrade to stock, my sim no longer works on the network. Seems as if the device has a sim lock, but it never asked for one. A local cellphone shop in st.catharines said there might be an issue with the baseband after the official update.
before the update, i tried all the suggestions such as unmounting the sd card, wiping cache, using supersu to unroot.
Can anyone chime in on what the problem may be? I go to school here, so if all else fails i will have to go back to toronto where i purchased it, and have them figure it out. just a hassle for me to get there without a car.
Click to expand...
Click to collapse
When the distributor told you that the phone had been modified to enable an unlock, why did you say, "I was prepared to loose root as i dont need it"... the problem is fairly obvious, you had a software-unlocked phone and even though the seller told you that you would lose your unlock, you wiped it back to factory anyway lol...
honestly though, that's extremely sketch, lemme know that shop and I'll report them to BBB, you should never be paying for a cell phone that comes rooted unless your buying something from pacific mall, there are several options for you to unlock the phone, using software, hardware, or IMEI unlock codes

tedmonddo said:
...
Can anyone chime in on what the problem may be? I go to school here, so if all else fails i will have to go back to toronto where i purchased it, and have them figure it out. just a hassle for me to get there without a car.
Click to expand...
Click to collapse
You had a pre-rooted software-unlocked phone (that was originally network-locked). Your warranty to Samsung is completely void, you should get something in writing (or record on audio) from the guy that sold you the phone as to the warranty of the phone.
Other than that - you can buy a network unlock code for something like 15 USD or so.

[Q] Unable to remove custom padlock stock lolipop

I have tried everything I can possibly think of in a short period of time, and need an answer in a hurry. The phone (Verizon Samsung Galaxy Note 3 N-900V) was rooted back when kitkat was the main OS using geohot's towelroot (or possibly kingo root I can't remember which i used after I got the phone and upgraded from ICS). I have 2 of these exact same phones, used the exact same rooting method, and unrooted by uninstalling the superuser app, rebooted, and installed the OTA update to lolipop. My phone works fine, (the one I'm typing from) however, my other phone decided to take a dump. It's a software bug between the samsung firmware and the new lolipop OS. It was working for several months, then all the sudden it wouldn't recognize/register the APN. Now it doesn't see anything just about with the phone. Not even the IMEI from the phones serial number. The sim card has been replaced twice and has worked for a matter of a few hours, however, upon restarting the phone, it goes back to no service, and nothing is registered or recognized. I reflashed the phone with the stock 5.0 Lolipop using Odin several times to no avail. My phone (one I'm using now) once did this months ago, and I was able to access the service menu and reregister the SIM card and phone has worked fine since. With this other phone, I can't get into the service menu at all because nothing is registering. So, after reflashing 4 or 5 times, factory reseting from both the OS and from recovery booting, it still has the same issue. Here is my question. It used to be when I reflashed, the custom padlock would disappear. I'm getting a new phone tomorrow, and I need to get rid of the custom padlock before I return the old phone. I can use Odin, or whatever but it has to be something, I can do while it stays stock. The knox counter has not been tripped, and the flash counter is not tripped nor showing anything on the download mode. Everything lools, and feels stock, except that custom padlock. Is there a way to get rid of that custom padlock unrooted, by reflashing? I even used a pit file to repartition, but that didn't work either. Need help A.S.A.P.!

I would just hard brick the phone just before returning it...they will just throw it out at that point and your secret will be safe.

Hard Brick
xxperrin said:
I would just hard brick the phone just before returning it...they will just throw it out at that point and your secret will be safe.
Click to expand...
Click to collapse
You thinking maybe a NAND erase?

Hard Brick
I've thought about flashing the wrong rom too but dunno if that will work 100%. I either need to fix it, or make it 100% unrecoverable. Any advice?

Stock SM-N9005 Restarting 4-5 times a day - need some advice

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