Hello all,
I've had my Iconia A100 for 2 days in which I got familiar with the whole android experience, rooted it as well and everything was peachy. Then the battery stopped charging so it died completely(no charging light when plugged in using multiple chargers).
I have to RMA for the device now but now i'm wondering since I rooted the device earlier and I'm unable to un-root because of it not turning on, what will happen when I send it back to be repaired? Will I have to pay to have the battery replaced because it is rooted?
rooting does not void warrentee, only unlocking the bootloader will.
really? Wow that's a load off my chest man, you don't understand
the things you own, end up owning you
Related
Hi
So i got my Desire HD 2 days after they started selling here in sweden and i've never had any problems with it what so ever, until today.
So when i got to school today my Desire HD wouldn't boot up, it worked this morning when i sent a text to my friend. I figured i hadnt plugged it in correctly when i was going to charge it last night but that wasn't the case. I tried to remove and reinsert the battery but that wouldn't work, i also tried to remove the memory card, wouldn't work either.
I can't boot it at all, i can't even boot it to recovery mode.
I really am in big trouble, if anyone knows what is causing this or has experienced this please respond...
ille16 said:
Hi
So i got my Desire HD 2 days after they started selling here in sweden and i've never had any problems with it what so ever, until today.
So when i got to school today my Desire HD wouldn't boot up, it worked this morning when i sent a text to my friend. I figured i hadnt plugged it in correctly when i was going to charge it last night but that wasn't the case. I tried to remove and reinsert the battery but that wouldn't work, i also tried to remove the memory card, wouldn't work either.
I can't boot it at all, i can't even boot it to recovery mode.
I really am in big trouble, if anyone knows what is causing this or has experienced this please respond...
Click to expand...
Click to collapse
If it is completely dead then Id try another battery....yeah easier said than done I know...none of your mates got one??
Is it under warranty??
Have you installed a custom rom?
Does it boot when plugged into the mains?
It may just be the circuit board or connectors to the battery??
To be honest...it could be bloody anything..
rixsta said:
If it is completely dead then Id try another battery....yeah easier said than done I know...none of your mates got one??
Is it under warranty??
Have you installed a custom rom?
Does it boot when plugged into the mains?
It may just be the circuit board or connectors to the battery??
To be honest...it could be bloody anything..
Click to expand...
Click to collapse
Nope no one i know have one :/
It's unrooted so no custom roms in it.
It does NOT boot when plugged into the mains either
I think it's under warranty since i bought it not that long ago, but i didn't buy extended warranty though so i dunno
does a light come on when you plug it into the wall to charge?
Have you looked at the connectors on the SIM card & battery covers? Mine look like they are simply painted on. Yours maybe worn....
Nope theres no light...
I don't really know what you mean by painted on because i looked at mine and they stick out a bit, if i'm looking at the right piece.
It's a bit useless to begin discussing about this. YOu have done nothing to void your warrenty. It should boot and it doens't. That means you should return it. This isn't you problem, so to say.
I had the same issues, unattented reboots, then DHD randomly turning off. And last Saturday, impossible to start it again. At this point, I had rooted it, S-OFFed it and installed ClockWork Recovery and a custom ROMS as well.
Anyway, I sent it for maintenance yesterday and expect to have my DHD repaired within the next two weeks...
Hi guys,
I'm considering flashing the JB leak but I'm hesitating for some possibly unrelated reasons that maybe you all can clear my mind about.
I recently bought a new Acer Aspire laptop and a couple weeks later a Galaxy Nexus. I used to have a Dell laptop and a Galaxy S2 that I rooted and maintained using that Dell with no problems. After getting my new tech I plugged in my Gnex and installed the drivers, then installed the Gnex toolkit for rooting my phone.
I rooted the phone with ease, but ended up having to return that phone because it had screen problems. Shortly after the toolkit and drivers installation, my new laptop began having terrible problems: It would randomly BSOD while performing simple tasks and then tell me that no OS was installed, and it developed an extremely annoying habit of randomly beeping and dimming while plugged in and charging.
It was so bad that I tried a factory reset, which did not solve the problem. I eventually sent the laptop back to Acer for repairs. According to the report I received, they updated the HDD firmware and BIOS to correct the problems. I haven't had any of the problems since it was returned, but it's only been a week or two.
So now I have a new Gnex and my repaired laptop. I want to root it and flash JB but I'm paranoid about the driver installation process effing up my laptop again. I don't know for sure that this is what caused the problem. Coincidence is not necessarily causation. I also don't understand why smartphone drivers would cause a problem like the beeping I suddenly experienced.
What do you guys think? Is it indeed possible that setting up the rooting environment caused the problems I experienced? Or was the laptop's firmware simply faulty from the get-go and I've been deceived by the timing of it all?
TL;DR
Want to root, but setting up the rooting environment appears to have seriously messed up my laptop last time I did it. Is that at all possible?
Follow this and forget about toolkits.
rosemachinegun said:
Hi guys,
I'm considering flashing the JB leak but I'm hesitating for some possibly unrelated reasons that maybe you all can clear my mind about.
I recently bought a new Acer Aspire laptop and a couple weeks later a Galaxy Nexus. I used to have a Dell laptop and a Galaxy S2 that I rooted and maintained using that Dell with no problems. After getting my new tech I plugged in my Gnex and installed the drivers, then installed the Gnex toolkit for rooting my phone.
I rooted the phone with ease, but ended up having to return that phone because it had screen problems. Shortly after the toolkit and drivers installation, my new laptop began having terrible problems: It would randomly BSOD while performing simple tasks and then tell me that no OS was installed, and it developed an extremely annoying habit of randomly beeping and dimming while plugged in and charging.
It was so bad that I tried a factory reset, which did not solve the problem. I eventually sent the laptop back to Acer for repairs. According to the report I received, they updated the HDD firmware and BIOS to correct the problems. I haven't had any of the problems since it was returned, but it's only been a week or two.
So now I have a new Gnex and my repaired laptop. I want to root it and flash JB but I'm paranoid about the driver installation process effing up my laptop again. I don't know for sure that this is what caused the problem. Coincidence is not necessarily causation. I also don't understand why smartphone drivers would cause a problem like the beeping I suddenly experienced.
What do you guys think? Is it indeed possible that setting up the rooting environment caused the problems I experienced? Or was the laptop's firmware simply faulty from the get-go and I've been deceived by the timing of it all?
TL;DR
Want to root, but setting up the rooting environment appears to have seriously messed up my laptop last time I did it. Is that at all possible?
Click to expand...
Click to collapse
On my phone, rooting, roms and cwm make incurable problems to my htc...
I an not going to root again until my phone has been with me for at least two years, the htc warranty has an expiry date on new phones... Oh no, another problem...
Ok so I have the 1st gen kindle fire and it seems to have a charger port problem of some kind so amazon is going to replace it (a month out of warrenty)
but the problem is its rooted with the play store and several other apps no custom rom or anything . I need to know if i need to unroot before i send it back and if so how ...
It wont take a charge and will only turn on when plugged in and even then it only stays on for maybe a minute then turns off so how can I unroot or should i just say the heck with it and send it back rooted??? will I be charged ?
anybody have any past experience with a similar situation????
I don't know from experience but my suggestion would be don't send it back to Amazon rooted because the act of rooting usually voids any warrenty. It's possible they wouldn't replace it because it is rooted.
they made an exception to the warrenty being out by a couple months and they know its a hardware issue. can't factory reset because the battery wont take a charge. battery wont take a charge there fore i cant plug into a computer to unroot either
this sucks
My Usb died this week and now I'm sending it back. I never mentioned it was rooted but they're still sending me a replacement anyway.
Sent from my Galaxy Nexus using Tapatalk 2
Rpatton;Son
28116 said:
Ok so I have the 1st gen kindle fire and it seems to have a charger port problem of some kind so amazon is going to replace it (a month out of warrenty)
but the problem is its rooted with the play store and several other apps no custom rom or anything . I need to know if i need to unroot before i send it back and if so how ...
It wont take a charge and will only turn on when plugged in and even then it only stays on for maybe a minute then turns off so how can I unroot or should i just say the heck with it and send it back rooted??? will I be charged ?
anybody have any past experience with a similar situation????
Click to expand...
Click to collapse
I had the same USB port problem. They sent a replacement. A week later I returned the broken rooted unit. I never heard anything further from Amazon.
Good luck,
The Don
Nice. I'm sure part of their standard procedure is a clean wipe and flash of the factory image.
Sent from my Galaxy Nexus using Tapatalk 2
Also rooted and claimed warrenty
I had the same problem with mine and I just let the battery drop so it wouldn't turn on anymore. Now amazon would have to put a new port on in order to get it working.
My Note 2 has just died It was getting surprisingly laggy at odd moments in the past week, but I didn't think anything was wrong. I was updating a lot of applications one after another tonight (music was playing but it was jumpy, i think because apps were updating so i stopped music) and people were messaging me on the facebook app so I could see the notification light flash green. I was busy on my laptop, so I ignored the phone about 10 mins.
The green light kept flashing, but the screen wouldn't turn on when i pressed home or power key. so i took the battery out from the back and reinserted it. It wouldn't switch on at all, no SGS Note 2, no Samsung logo. nothing at all except a little red light flashing where the infrared light is everytime i tried to turn it on.
I tried connecting it to my computer. nothing happened. recovery mode bootup also failed. I tried charging the phone, even though the battery wasn't empty, still wouldn't switch on during charger plugged in or pulled out. Took out SD/Sim, no effect. A new battery didn't help. The phone doesn't charge either, the charger makes a funny electrical whining noise and the infrared red light flashes every so often.
It's basically dead. What can I do? The phone is also rooted, I can't remember how (think it's original chainfire root? i got my phone last oct). Will Samsung be able to switch on my phone and discover it's rooted? Also I read somewhere that legally speaking if rooting didn't cause the failure, you're still covered by EU law?
I am in the UK, bought Note 2 off a 3rd party reseller (Buymobilephones) who provided a handset, and T-Mobile for the contract.
Thanks
jeanclaudevandamme said:
My Note 2 has just died It was getting surprisingly laggy at odd moments in the past week, but I didn't think anything was wrong. I was updating a lot of applications one after another tonight (music was playing but it was jumpy, i think because apps were updating so i stopped music) and people were messaging me on the facebook app so I could see the notification light flash green. I was busy on my laptop, so I ignored the phone about 10 mins.
The green light kept flashing, but the screen wouldn't turn on when i pressed home or power key. so i took the battery out from the back and reinserted it. It wouldn't switch on at all, no SGS Note 2, no Samsung logo. nothing at all except a little red light flashing where the infrared light is everytime i tried to turn it on.
I tried connecting it to my computer. nothing happened. recovery mode bootup also failed. I tried charging the phone, even though the battery wasn't empty, still wouldn't switch on during charger plugged in or pulled out. Took out SD/Sim, no effect. A new battery didn't help. The phone doesn't charge either, the charger makes a funny electrical whining noise and the infrared red light flashes every so often.
It's basically dead. What can I do? The phone is also rooted, I can't remember how (think it's original chainfire root? i got my phone last oct). Will Samsung be able to switch on my phone and discover it's rooted? Also I read somewhere that legally speaking if rooting didn't cause the failure, you're still covered by EU law?
I am in the UK, bought Note 2 off a 3rd party reseller (Buymobilephones) who provided a handset, and T-Mobile for the contract.
Thanks
Click to expand...
Click to collapse
I wish you a Good luck then.
jeanclaudevandamme said:
My Note 2 has just died It was getting surprisingly laggy at odd moments in the past week, but I didn't think anything was wrong. I was updating a lot of applications one after another tonight (music was playing but it was jumpy, i think because apps were updating so i stopped music) and people were messaging me on the facebook app so I could see the notification light flash green. I was busy on my laptop, so I ignored the phone about 10 mins.
The green light kept flashing, but the screen wouldn't turn on when i pressed home or power key. so i took the battery out from the back and reinserted it. It wouldn't switch on at all, no SGS Note 2, no Samsung logo. nothing at all except a little red light flashing where the infrared light is everytime i tried to turn it on.
I tried connecting it to my computer. nothing happened. recovery mode bootup also failed. I tried charging the phone, even though the battery wasn't empty, still wouldn't switch on during charger plugged in or pulled out. Took out SD/Sim, no effect. A new battery didn't help. The phone doesn't charge either, the charger makes a funny electrical whining noise and the infrared red light flashes every so often.
It's basically dead. What can I do? The phone is also rooted, I can't remember how (think it's original chainfire root? i got my phone last oct). Will Samsung be able to switch on my phone and discover it's rooted? Also I read somewhere that legally speaking if rooting didn't cause the failure, you're still covered by EU law?
I am in the UK, bought Note 2 off a 3rd party reseller (Buymobilephones) who provided a handset, and T-Mobile for the contract.
Thanks
Click to expand...
Click to collapse
How long ago did you buy the phone?
If you were rooted, were you on stock rom?
If yes, than which build were you on, do you remember?
I have heard of phones dying from sds, were you on an older rom. If that is the case, and if you have hard bricked your phone, AND if you are under warranty you need not fear...the guys at samsung wouldn't be able to open your phone either to check whether its rooted or not, you are covered. Your phone would require a motherboard rwplacement 8n that case. I hope you had backups.
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
SacGuru said:
How long ago did you buy the phone?
If you were rooted, were you on stock rom?
If yes, than which build were you on, do you remember?
I have heard of phones dying from sds, were you on an older rom. If that is the case, and if you have hard bricked your phone, AND if you are under warranty you need not fear...the guys at samsung wouldn't be able to open your phone either to check whether its rooted or not, you are covered. Your phone would require a motherboard rwplacement 8n that case. I hope you had backups.
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
Click to expand...
Click to collapse
I bought it at end of last october, 1st gen/batch of Note 2s to hit the UK (IMEI starts with 354.....
I was rooted. The first auto-root Chainfire method via Odin.
Stock samsung rom. Very earliest versions of software.
I basically bought the phone last year when it first came out, rooted it as soon as possible and then did nothing else except enjoying my phone and install new apps. Whatever people were rooting/flashing/roms/kernels etc at the end of last october when the note 2 first came out in the uk is what I would have been on. Never updated since.
I might sound a bit stupid, but does a motherboard change means you lose everything in internal storage? ie photos, texts, contacts etc. I have no backups of anything. my fault I know. And Samsung wont' detect root after motherboard has been changed?
When you say "hardbricked", do you just mean it wont' physically and electrically turn on? Because i didn't interrupt rooting/flashing etc.
I googled SDS for the Note 2. Seems there is an issue I can't think how else my phone would just die.
jeanclaudevandamme said:
I bought it at end of last october, 1st gen/batch of Note 2s to hit the UK (IMEI starts with 354.....
I was rooted. The first auto-root Chainfire method via Odin.
Stock samsung rom. Very earliest versions of software.
I basically bought the phone last year when it first came out, rooted it as soon as possible and then did nothing else except enjoying my phone and install new apps. Whatever people were rooting/flashing/roms/kernels etc at the end of last october when the note 2 first came out in the uk is what I would have been on. Never updated since.
I might sound a bit stupid, but does a motherboard change means you lose everything in internal storage? ie photos, texts, contacts etc. I have no backups of anything. my fault I know. And Samsung wont' detect root after motherboard has been changed?
When you say "hardbricked", do you just mean it wont' physically and electrically turn on? Because i didn't interrupt rooting/flashing etc.
I googled SDS for the Note 2. Seems there is an issue I can't think how else my phone would just die.
Click to expand...
Click to collapse
I think we know the cause now, its sds. Only roms and kernels which have been developed after January 2013 are free of this problem. As you had rooted very early you would not have recieved stock updates from samsung. And as you had not flashed anything new, the rom/kernel you used had the sds problem. Had you recieved stock updates or had you flashed any latest rom your device would most probably be working.
Now the good news is, as I said, samsung has no way of learning whether your phone was rooted or not. A soft brick is when your phone is in a bootloop. A hardbrick means it wont't turn on, won't do anything at all. Your phone is hardbricked in a way. So a samsung engineer would be as powerless to turn your phone on in this condition as you are. And thus, you would be under warranty.
The bad news is, yes, all the data on your internal storage is gone. The phone you would be provided would be a new factory reset model altogether. That is of course, if the problem is sds, as it seems right now. Even if the problem is different, something smaller, a factory reset is what you will get in all probability, so no chance of saving the data.
I am really sorry for your data, and I know it doesn't help when I play Captain Hindsight, but you should have made a titanium and nandroid backup at the very least. Do that for your next phone regularly. It is the most useful aspect of rooting your phone if you ask me.
Of course, I could be wrong here. The problem could be something smaller. I suggest you throw this problem @dr.ketan on this thread
http://forum.xda-developers.com/showthread.php?t=1896696
He knows a lot more than I do and can confirm this.
Also, do press thanks if I helped
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
Hey everyone... I was using my phone as usual when suddenly it blue screened and died on me. Like dieded died. I've been soft bricked before but this was bad. It wouldn't on after taking out the battery, charging, different batteries (anker)
Left it for a while tried again, nothing. Like not even the boot up animation. Now, the phone had been acting up for the past 2 days. Random reboots every few hours and it even blue screened the day b4 but came back as usual. I was just considering a new rom cos i had been on this one a while so i thought maybe it was just time for a new flash when all this happened. Full disclosure im rooted xposed on Dirty Unicorns Marshmallow. Also not sure if this is relevant but i had recently begun using new batteries from anker for the past 2 months
That's the only new thing i did to my phone. I use my phone to just below 5%, off then pop a new 100% battery in. I hadn't charged my phone my cable since.
I went to a repair shop immediately and they tried hooking it up directly to a positive negative power source but they said it wasnt registering at all, so im thinking this is serious.. I Googled around and best i could find was that this maybe a motherboard issue. The only solution ive found online (https://forum.xda-developers.com/lg-g3/help/lg-g3-d855-blue-screen-death-t3380844) were those saying i need to bake\heat the motherboard?? At first i thought it was a troll but im desperate and not sure anymore
Is that a legit solution and if not, what is...? Please guys i can't afford a new phone for at least another year. Thanks in advance.