Develop Bugs

Convince me to root!

So far I have zero complaints about this phone, there are some ui things I would like fixed, and I know can be fixed via rooting, but they just don't seem to be enough to push me over the edge. I have files downloaded and ready to go, but just can't seem to take the plunge. I thought I had my first los today, but the phone recovered as soon as I was back in signal(if it hadn't that would have done it).
So why should I root?
Sent from my SPH-D710 using Tapatalk

You can always revert back to the stock kernel if you have an issue (or have them that frequently that you can't stand it). Anybody who thinks that once you root there is no way to go back is an idiot. "lol, I got no LOS then I rooted and even though I put stock kernel back its all [email protected] lol" not true.
I got 2 LOS in the first week stock...rooted...got a bit more than usual, but nothing crazy. Flashed stock kernel back, still rooted, didn't have another for a few weeks until I flashed a new kernel...flashed back, have had none...etc etc etc, YMMV, but, umm, I don't think you have anything to be afraid of. Just know what you are doing...don't just flash stuff and figure it out later. Know why you want something and how to 'put it back'...also having/making a USB jig would be a good idea, but not necessary.
You can get them for like $3 on amazon or build one with a microUSB cable and $1 worth of stuff from radioshack.
I don't know about you but I certainly didn't get this phone to NOT mod it.

I didn't get the phone to keep it stock, not really worried about los, it recovers after flying for 2 hours with no signal, rooting shouldn't make much difference., planning on using viperom and lostkernel.
Maybe tomorrow I will root
Sent from my SPH-D710 using Tapatalk

flyboy1100 said:
I didn't get the phone to keep it stock, not really worried about los, it recovers after flying for 2 hours with no signal, rooting shouldn't make much difference., planning on using viperom and lostkernel.
Maybe tomorrow I will root
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
The only thing I can tell you is that read the directions and understand ODIN for all of the ODIN stuff you do. That is one of the ways you can brick the fnck out of this phone...not paying attention in ODIN. Don't write a partition if you are not told to...and try to only use it to flash a kernel+CWM and flash everything else from CWM if and when possible.
If you aren't worried about LOS (and it is real and under the right circumstances it'll effect every phone...reboot...no big deal...if it is flash a pulled stock kernel) then go for it.
I haven't tried ViperROM on this phone yet, but, I can tell you from my time with the E3D that kid knows what he's doin'....I'm sure this ROM is no different and I've heard nothing but great things about the LoST kernel.

If you don't want to root, don't. Why would anyone want to pressure you?
Sent from my extra sensory space modulator while performing the slippery cricket

Tell us how it goes. You won't be disappointed.
Sent from my HTC Glacier using xda premium

If U need convincing, you probably don't need it.
Sent from my Galaxy S2

Someone convince me to strangle my puppy. I love him and all and he is very well mannered but if you guys can talk me into strangling him, I will.

ravizzle said:
If U need convincing, you probably don't need it.
Sent from my Galaxy S2
Click to expand...
Click to collapse
I agree. You root cause u want to. If u want someone to convince u then maybe u shouldn't.
Sent From My Evo Killer!!!

I don't understand why some people view this almost like losing their virginity, trying a drug or robbing a liquor store. It's a very well understood technical process with very specific pros and cons that are also very well understood.

Yep. First android phone for me, and I bought it with the full intention of making it MY phone. After all, they are basically an additional limb for most people, no? (I'd say if you're registered with xda that is most likely the case! ) So you might as well go balls to the walls, right? If you're not into that kind of thing, then keep it stock! This phone is AMAZING just sitting at the home screen...it looks awesome! It is a great piece of technology, with plenty of great features and capability, and will serve you very well whether its rooted or not. Good luck with whatever you do!

buggerritt said:
If you don't want to root, don't. Why would anyone want to pressure you?
Sent from my extra sensory space modulator while performing the slippery cricket
Click to expand...
Click to collapse
Not looking for pressure. I will probably root it tomorrow or next week
Sent from my SPH-D710 using Tapatalk

Because all the cool kids are doing it!
I broke down and did it yesterday when someone said viper ROM solved his app freezing due to using a ton of CPU usage bug. So far, so good.
Sent from my SPH-D710 using XDA App

OP if you are on EG30 baseband could you extract the modem.bin file for us so we could test it?

I would just stay stock. Honestly, no offense to the developers, but there is just nothing substantial out there. If you want a couple of different themes, you could consider rooting, but other than that every ROM I have flashed provided close to nothing really.
I mean, what? Battery percentage mod? Removed CIQ? "Speed" tweaks? A reboot option?
Nothing made this phone faster or more efficient than stock touchWiz. There is no real difference except that people like to flash, so they would flash anything.
Sorry. That's just my take on it.
Wait for MIUI or CM.

I gotta say i miss root, I was finicky on rooting my epic 4g ad once I did, oooh lord I never looked back , of course I've stumbled into troubles but following directions, I got back on track and learned a few this gs along the way, now what's stopping me on rooting the ET4G is not having the actual way to go back to full true stock,like we were able to do on the epic 4g with using Odin, giving you a factory full stock phone , or any older device, since we don't have true stock roms and kernels, unless I'm wrong g of course and I've been missing out! If so direct me!

Kikoshi said:
I gotta say i miss root, I was finicky on rooting my epic 4g ad once I did, oooh lord I never looked back , of course I've stumbled into troubles but following directions, I got back on track and learned a few this gs along the way, now what's stopping me on rooting the ET4G is not having the actual way to go back to full true stock,like we were able to do on the epic 4g with using Odin, giving you a factory full stock phone , or any older device, since we don't have true stock roms and kernels, unless I'm wrong g of course and I've been missing out! If so direct me!
Click to expand...
Click to collapse
We have stock roms to ODIN, but it's not factory stock. We have the factory stock kernel that was pulled from a stock phone. What we lack is an OEM RUU to make it 100%-in-every-way-stock.
That said, I have trashed my 4G and wifi somehow on multiple occasions due to rampant recklessness on my part. I just factory-wiped (apparently...I don't remember that part but I must have) and flashed the ODIN rooted stock (with stock kernel) and it fixes everything every time.

daneurysm said:
We have stock roms to ODIN, but it's not factory stock. We have the factory stock kernel that was pulled from a stock phone. What we lack is an OEM RUU to make it 100%-in-every-way-stock.
That said, I have trashed my 4G and wifi somehow on multiple occasions due to rampant recklessness on my part. I just factory-wiped (apparently...I don't remember that part but I must have) and flashed the ODIN rooted stock (with stock kernel) and it fixes everything every time.
Click to expand...
Click to collapse
So then you recommend rooting this early?

i rooted so i could have wifi tethering and control over CPU speeds (via setcpu) in addition, there's some neat functionality that starburst ROM allows:
- better lock screens
- motion controlled silencing of phone
- battery % viewing
some people care about the speed tweaks (i haven't noticed any speed increase) and ciq (i don't really care for this), but there are several reasons to root. that being said, if you don't need the additional functionality of the phone, then preserve your phone's warranty!

Yea I'd say stay stock in terms of the ROM and kernel, but hell yea why not root? Right now I'm running stock kernel with CWM (http://forum.xda-developers.com/showthread.php?t=1305099) and the stock ROM with root and busybox (http://forum.xda-developers.com/showthread.php?t=1282415) and I love it. I was running Midnight ROM but I went back to stock to see if that helped the LoS issues at all. If you're like me and really just want control over the hotspot feature and CPU underclocking (things of that nature) then def go stock rooted fo shoski.

Counter for amount of times ROM flashed

As some of you might or might not know.
Can anyone that has flashed a Custom ROM verify if there is a counter on our incarnation of SGS2
details here:
[HOWTO] reset custom binary counter in download mode
and here:
Default [ROOT] Stock FW, w/o increasing custom counter

Dude. I was wondering how the hell we were gonna fix this. Thanks for sharing
Sent from my HTC Glacier using XDA App

mikeyinid said:
Dude. I was wondering how the hell we were gonna fix this. Thanks for sharing
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Thanks for sharing!!! ur psychic

Why do they want to keep a record of how many times we flash? I wonder if it's to prove that they don't have to pay for warranty.

most likely something along the line
or perhaps to count how many times the internal storage has been written to, which causes wear

AllGamer said:
most likely something along the line
or perhaps to count how many times the internal storage has been written to, which causes wear
Click to expand...
Click to collapse
Normally, I'd scoff at the idea that a company was being all big-brother and trying to embed ways to track what your doing to your device but I see no reason for this type of software besides A) giving my wife more proof that I spend way too much time, effort, and money on my phone and B) giving Samsung another reason to not honor your warranty. That said, I'm not the type to try and make someone else pay out for my mistakes but I'm not a fan of being spied on.

i got the jig that is "suppose" to reset the counter also. maybe its with our variant of the GSII that it doesnt reset?

lookitzjohnny said:
i got the jig that is "suppose" to reset the counter also. maybe its with our variant of the GSII that it doesnt reset?
Click to expand...
Click to collapse
possibly, since our CPU is different, it might be related to that?
or perhaps related to the SIM unlock, which in our phone is also different than the regular SGS2

kenvan19 said:
Normally, I'd scoff at the idea that a company was being all big-brother and trying to embed ways to track what your doing to your device but I see no reason for this type of software besides A) giving my wife more proof that I spend way too much time, effort, and money on my phone and B) giving Samsung another reason to not honor your warranty. That said, I'm not the type to try and make someone else pay out for my mistakes but I'm not a fan of being spied on.
Click to expand...
Click to collapse
This was one of the reasons I started the thread on getting insurance. I don't want any problems when it comes to getting my phone replaced. Manufacturers suck when it comes to that. I could see them easily denying a replacement for that reason alone. I'll just deal with tmobile instead.

this is one of the little reasons that actually makes the Best Buy no question no hassle insurance really worth while

I know someone that was having problems with their vibrant and called in a warranty replacement. They told the rep that the phone was rooted and had a different ROM. The rep checked with their supervisor and said that the warranty was still in place. He got a new vibrant and was not charged an out of warranty fee.

has anyone found a way to reset it yet?

Where is this counter? Didn't know there was one. I've done a lot of exchanges ( Vibrant, G2, G2X and SGS2) from different phones and never bothered to reset any counter.
Ooopps!
Hercules Hercules!!

The thing is, from having,worked at Tmobile is that most phones will get inspected for common warranty breaking.g things, like water damage, taking apart your phone. Other than that, I believe they just factory wipe the data with their computers and either refurb. Or recycle. I've sent back phones that have been bricked from bad ROM flashes and have never incurred a fee.
Sent from my SGH-T989 using XDA App

Jigs work to get into download mode but they don't reset the count. This is from my personal experience
Sent from my SGH-T989 using Tapatalk

I saw I forgot to post the URL. I added it to op
Sent from my SGH-T989 using XDA App

i would be really interested to know if this resets the counter tooooooo

What does the counter do anyways? In terms of flashing ROMs, does it limit the number of times we can flash custom ROMs?
Sent from my SGH-T989D using xda premium

Why would we need to reset the counter? I've returned lots of phones without resetting and I've had no problems.
Just curious as to why? Thanks.
Hercules Hercules!!

if u sent ur phone back to samsung it tells them how many times u have flashed roms on it! ive never heard of a person getting in trouble for a high count before but thats wht i know

[Q] How to unbrick? (Blue LED of death)

I pretty much already know the answer - JTAG. I'm just hoping for a little bit of HOPE. Are there any other possible ways of me unbricking it with a blue LED of death?
No USB recognition, no Download mode, no recovery.
I was already on AOKP Build 30, I was getting forcecloses because I went from Build 29 to 30 without wiping data, so I used Mobile Odin for EL26 kernel, did a full wipe on data/cache, flashed AOKP Build 30, flashed Gapps, then I did a reboot. It rebooted onto the Galaxy SII screen with the yellow triangle, then it went away and rebooted again to come to the Blue LED of death and doesn't go away until a battery pull.
Apparently a USB jig won't work.
I can take it into Sprint (I have a warranty), but what should I tell them? Would they charge me for a new phone, and would I get it right away?

hrffd said:
I pretty much already know the answer - JTAG. I'm just hoping for a little bit of HOPE. Are there any other possible ways of me unbricking it with a blue LED of death?
No USB recognition, no Download mode, no recovery.
I was already on AOKP Build 30, I was getting forcecloses because I went from Build 29 to 30 without wiping data, so I used Mobile Odin for EL26 kernel, did a full wipe on data/cache, flashed AOKP Build 30, flashed Gapps, then I did a reboot. It rebooted onto the Galaxy SII screen with the yellow triangle, then it went away and rebooted again to come to the Blue LED of death and doesn't go away until a battery pull.
Apparently a USB jig won't work.
I can take it into Sprint (I have a warranty), but what should I tell them? Would they charge me for a new phone, and would I get it right away?
Click to expand...
Click to collapse
I think you may be hosed but if you have the jig I'd definitely give it a shot (just in case). If that doesn't work you can take it into Sprint. If I remember right with the warranty if they can repair it there's no charge, if they need to send you a new device it's a $100 deductible. Most people just say it quit working on them without offering an explanation, seems to work most of the time.
Good luck!

Apparently JTAG is not going to work either. Something seems to be actually destroying the MMC chip when you mess with ICS and custom recoveries.

sputnik767 said:
Apparently JTAG is not going to work either. Something seems to be actually destroying the MMC chip when you mess with ICS and custom recoveries.
Click to expand...
Click to collapse
JTAG has been able to recover some hard bricks. I think it depends on the extent of the damage.
Sent from my SPH-D710 using Tapatalk

Dchibro said:
JTAG has been able to recover some hard bricks. I think it depends on the extent of the damage.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Have not heard of Jtag bringing anyone back from these bricks though.. Also there is a guy in the thread above yours... right before I posted that had a similar issue with AOKP Build30... Hope there is no problem with that rom..

playya said:
Also there is a guy in the thread above yours... right before I posted that had a similar issue with AOKP Build30... Hope there is no problem with that rom..
Click to expand...
Click to collapse
Ya, Me too.

hrffd said:
I pretty much already know the answer - JTAG. I'm just hoping for a little bit of HOPE. Are there any other possible ways of me unbricking it with a blue LED of death?
No USB recognition, no Download mode, no recovery.
I was already on AOKP Build 30, I was getting forcecloses because I went from Build 29 to 30 without wiping data, so I used Mobile Odin for EL26 kernel, did a full wipe on data/cache, flashed AOKP Build 30, flashed Gapps, then I did a reboot. It rebooted onto the Galaxy SII screen with the yellow triangle, then it went away and rebooted again to come to the Blue LED of death and doesn't go away until a battery pull.
Apparently a USB jig won't work.
I can take it into Sprint (I have a warranty), but what should I tell them? Would they charge me for a new phone, and would I get it right away?
Click to expand...
Click to collapse
I am not sure if you listed every step you did or were just summarizing.
Did you have the Yellow Triangle before any of this? I ask because nothing you did should have triggered the yellow triangle unless you had it before (or traditional ODIN'd CWM outside of the steps you listed)
Also, nothing you did should have prevented you from getting into ODIN DL mode. Even in the case of /data EMMC corruption, you can still get into ODIN DL mode.
Are you sure you can't get into ODIN DL mode? Pull the battery, then as you insert the battery press-and-hold Power+VolDown. If it is difficult to do the finger combination, then you are doing it right.
If you can get into ODIN DL mode, use the EL29 OneClick to get back to a known base. Use the Full version. If it hangs on data.img, then you have the /data emmc corruption and your only option is to get the unit replaced. JTAG will not work.

I have a quick question since we seem to be on the topic of bricks today. Has anybody bricked from making a nandroid in ICS recovery then using format all zip and then restoring from it. I am not referring to AOKP, CM9, etc rather stock or themed stock ROMs. I would NEVER recommend anyone to do this but I have made a few and restored them only wiping with format all zip. Am I tempting fate here or what? I thought this was narrowed down to wiping individual partitions or working from AOKP, CM9 recovery. Any thoughts here?
Sent from my Nexus S 4G using xda premium

JohnCorleone said:
I have a quick question since we seem to be on the topic of bricks today. Has anybody bricked from making a nandroid in ICS recovery then using format all zip and then restoring from it. I am not referring to AOKP, CM9, etc rather stock or themed stock ROMs. I would NEVER recommend anyone to do this but I have made a few and restored them only wiping with format all zip. Am I tempting fate here or what? I thought this was narrowed down to wiping individual partitions or working from AOKP, CM9 recovery. Any thoughts here?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
the question is why are you wiping when restoring a nandroid back up?
You should be fine but the wiping step is pointless. The restore process should do it automatically.
Also yes, I have done a backup while in FC22 based CWM and recovered it from another FC22 based CWM install and it worked fine. No need to wipe at all.
Sent from my SPH-D710 using Tapatalk 2 Beta-5

@JohnCorleone,
There are other posters that agree with you that not all ICS ROMs have that problem. Epix4G has reminded me of this on occasion, but that was in regards to using Calk's ROMs and solutions. But I would also caution that this probably isn't a good idea for Joe Schmoe with a shiny new E4GT... maybe those that have been around longer or are willing to take that risk.
In my personal case I don't have the option for insurance and had to pay full price for this phone. I can't afford to brick it so I stick with the ODIN TARs for now. Maybe a few months down the road, once ICS is out and hopefully there's a better handle on this, I'll try some of the other options out there. Besides, coming from an Optimus S stock will do everything I need and more right now.

garwynn said:
@JohnCorleone,
In my personal case I don't have the option for insurance and had to pay full price for this phone. I can't afford to brick it so I stick with the ODIN TARs for now. Maybe a few months down the road, once ICS is out and hopefully there's a better handle on this, I'll try some of the other options out there. Besides, coming from an Optimus S stock will do everything I need and more right now.
Click to expand...
Click to collapse
Ya, I was using my phone on a different carrier, and bricked it. Talk about a ****ty realization. And coming from an Optimus, life is goooood eh? lol.

take the phone to sprint as long as they cant see anything your good to go. tell them you plugged it in to charge came back and smelt something funny and phone was real hot.

Same brick here, only blue led of death and no activity.
The phone is outside US so can't even get warranty / replacement. Can't get get mmc chip from Samsung which in this case is KLMAG4FEJA-A003

Jtag
sent from MY BAD A$$ ET4G

JTAG has failed over RISC

Disillusioned said:
Same brick here, only blue led of death and no activity.
The phone is outside US so can't even get warranty / replacement. Can't get get mmc chip from Samsung which in this case is KLMAG4FEJA-A003
Click to expand...
Click to collapse
Are you able to get ahold of a USB jig and see if this will somehow get it to come to life? If not, have you considered asking someone in the US to try and work with Samsung on your behalf?

Its pretty much dead at this point, time to replace the device. Even if a jig will trigger dl mode it will more than likely fail/hang at /data in odin.
Sent from my SPH-L710

-EViL-KoNCEPTz- said:
Its pretty much dead at this point, time to replace the device. Even if a jig will trigger dl mode it will more than likely fail/hang at /data in odin.
Sent from my SPH-L710
Click to expand...
Click to collapse
Yes, but if there is not a replace option getting that far would mean a modified pit will restore most functionality.
Sent from my SPH-D710 using Tapatalk 2

garwynn said:
Yes, but if there is not a replace option getting that far would mean a modified pit will restore most functionality.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
True, that's a 50/50 shot and worth the try if there's not a warranty or ins option, but if warranty is an option I'd personally grab a replacement instead of patching up a borked one just so I wouldn't run into a major issue from patching it back together and then be out of warranty and stuck with a total brick. I've also seen a few ppl be able to get to dl mode and it fail at data but the pit not work, probably user error but never know could just be totally fubar from the emmc bug
Sent from my SPH-L710

-EViL-KoNCEPTz- said:
True, that's a 50/50 shot and worth the try if there's not a warranty or ins option, but if warranty is an option I'd personally grab a replacement instead of patching up a borked one just so I wouldn't run into a major issue from patching it back together and then be out of warranty and stuck with a total brick. I've also seen a few ppl be able to get to dl mode and it fail at data but the pit not work, probably user error but never know could just be totally fubar from the emmc bug
Sent from my SPH-L710
Click to expand...
Click to collapse
It was def user error. In another post he said he loaded aokp from rujelus recovery:crying:

HTC One V Dead

So I bought my gf a one v and she loves it. One month after using it (stock, unrooted) it just went dead. Doesn't charge and doesn't get into bootloader (but not the QHSUSB_DLOAD and Blank Screen issue). Guy at repair told me that this was an issue with the ICS kernel causing a hard brick. Now, I naturally sent phone for repair since it is a warranty case. So far so good, lets just hope they get it done fast.
My question is though: should I root device and flash another ROM with presumably no such issues so I can avoid a future brick? I mean, I'm using a rooted desire and have no issues for over 2 years, now just didn't want to mess with the new phone of my gf and thought 'hey, lets keep it stock'... But the thought that it would die again after having it repaired is really discouraging. My gf is kind of frustraded and I don't want this to happen again. But are there such issues with custom ROMs for the One V? Like I said, I'm using the good old desire and don't know much about the one v, so I would really apreciate if you can tell me - because if such an issue is possible on custom roms, there is no point to bother flashing and voiding warranty.
Thanks for your time guys!

Well at the moment we have only modified stock ROM for this device and one custom kernel (in beta state) which is still an ICS kernel.
However you''ll never know whether this happens again or not. But one thing you can know for sure is that if you unlock the bootloader and install a custom kernel and ROM and it happens again then your are screwed because you lost your warranty.
Maybe you should wait a bit for some stable custom rom. Because an unstable and buggy ROM would make your gf even more frustrated and andgry

Oh well, thanks for the insight my friend..So, If I got this right, if I root and flash one of the current roms and it bricks again, I will still not be able to acces bootloader? And is this really a kernel issue with ICS? I'm willing to even flash a GB rom, if it is possible, in order to avoid this...gf won't mind for sure lol, if this delivers a stable phone in the future
P.S. Does this even happen with other ICS roms/on other stock ICS devices? Or did HTC just screw up on this one? I can understand a phone bricking when changing hboots or other tinkering, but just dieing like that is pretty damn stupid. And from what I read it happens to quite a few other one v users...Hope noone of you guys gets to experience this crap

falconyx said:
Oh well, thanks for the insight my friend..So, If I got this right, if I root and flash one of the current roms and it bricks again, I will still not be able to acces bootloader? And is this really a kernel issue with ICS? I'm willing to even flash a GB rom, if it is possible, in order to avoid this...gf won't mind for sure lol, if this delivers a stable phone in the future
P.S. Does this even happen with other ICS roms/on other stock ICS devices? Or did HTC just screw up on this one? I can understand a phone bricking when changing hboots or other tinkering, but just dieing like that is pretty damn stupid. And from what I read it happens to quite a few other one v users...Hope noone of you guys gets to experience this crap
Click to expand...
Click to collapse
1. In no other galaxy, no other planet... IT IS NOT A KERNEL FAULT! it may at well be a piece of poorly made phone. you should get another one from the warranty. I can 100% say that you will not have any problems. The kernel doesn't suddenly causes hard brick to your phone. If it does, do you know how many phones running ICS are there? Or One V's...
I have flashed alpha/beta/final kernels/roms for millions of times, no problems whatsoever.
in no way this is a kernel/soft problem. more likely the flash drive from your gf's phone, died!

1ceb0x said:
1. In no other galaxy, no other planet... IT IS NOT A KERNEL FAULT! it may at well be a piece of poorly made phone. you should get another one from the warranty. I can 100% say that you will not have any problems. The kernel doesn't suddenly causes hard brick to your phone. If it does, do you know how many phones running ICS are there? Or One V's...
I have flashed alpha/beta/final kernels/roms for millions of times, no problems whatsoever.
in no way this is a kernel/soft problem. more likely the flash drive from your gf's phone, died!
Click to expand...
Click to collapse
Thx dude, I was sort of wondering how this could really be a kernel problem, since the guy over at the repair told me so - 'Its a kernel issue with ICS'... well, I hope he was really wrong and the device we receive (hopefully soon) will be proper

falconyx said:
Thx dude, I was sort of wondering how this could really be a kernel problem, since the guy over at the repair told me so - 'Its a kernel issue with ICS'... well, I hope he was really wrong and the device we receive (hopefully soon) will be proper
Click to expand...
Click to collapse
That guy should really make his homework. In no way a kernel can brick the phone. If this was true, the phone will not boot and work for weeks in the first place. Its not like the kernel has a "time-bomb" inside and it triggers when it is set.
As I said, it is a phone problem, something hardware has failed.
Hopefully it will be fixed for you gf and she will not have any problems in the future.

It happens in India too
My htc one v got bricked suddenly while using it. Forums at internet says it happens if battery charge goes below certain limit. Mine it went down to 24%

It happened to me when my battery level was 14%. now I have to pay 200$ for repairs. (because I live in Iran.)

HTC ONE V dead
falconyx said:
Oh well, thanks for the insight my friend..So, If I got this right, if I root and flash one of the current roms and it bricks again, I will still not be able to acces bootloader? And is this really a kernel issue with ICS? I'm willing to even flash a GB rom, if it is possible, in order to avoid this...gf won't mind for sure lol, if this delivers a stable phone in the future
P.S. Does this even happen with other ICS roms/on other stock ICS devices? Or did HTC just screw up on this one? I can understand a phone bricking when changing hboots or other tinkering, but just dieing like that is pretty damn stupid. And from what I read it happens to quite a few other one v users...Hope noone of you guys gets to experience this crap
Click to expand...
Click to collapse
Hi My HTC one V just died , I didn't know how it was happened . 10 minutes before I made I call and just after sometime It stopped working .
Even it is not charging at all, mobile is out of warranty. don't really know what to do ..
Any suggestion would be appreciated .
Regards
Manoj

How does Samsung feel about rooted phones?

I need to send my phone back to Samsung because they have a 1 year manufacturer warranty per Sprint. If I send them back a Stock but rooted phone will they notice/care? The repair is hardware related not software. I need to get half of the small little hooks that are compressed when the battery is inserted. My only though is they may want to wipe battery stats and when they go into Recovery and notice it's TWRP they might get pissy. Thoughts & experiences? Thanks.
Sent from my SPH-L710 using xda premium

I took mine to sprint fully rooted and on a custom ROM, because my LCD was fried.. They didn't care at all. I wouldn't worry about unrooting it and crap. Just send that bad boy in.
Sent from my SPH-L710

xbmoyx said:
I need to send my phone back to Samsung because they have a 1 year manufacturer warranty per Sprint. If I send them back a Stock but rooted phone will they notice/care? The repair is hardware related not software. I need to get half of the small little hooks that are compressed when the battery is inserted. My only though is they may want to wipe battery stats and when they go into Recovery and notice it's TWRP they might get pissy. Thoughts & experiences? Thanks.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
My initial thoughts are as follows:
Samsung bootloaders are unlocked by default and they have indicated that they will not lock them in the future. So I'd think they're more likely to forgive rooting when it comes to their 1-year warranty.
According to Samsung's warranty page, as long as the defects you have are in no way caused by custom ROMs or the rooting process, they should cover the repair. Unfortunately, they have the final say in what caused the damage to the phone and could say that the custom kernel fried whatever part is malfunctioning. I seriously doubt that they'd do that, but it all depends on which service person you get and how good/bad their Monday has been. I'd say it'd be best to triangle-away the flash counter and to restore the stock recovery/rom. As always, qbking77 has a great video on how to unroot, so check it out.

I dont know. Samsung would probably be more "aware" of your phones root state compared to sprint. If its something simple like bad USB port, or burnt pixels, I doubt they would care. If your phones O.S. is jacked or you hard brick your phone, likely they will notice. You can avoid these problems if you install triangle away and have it automatically clear your bootloader every time you boot your device.
Remember,
You are taking a risk when you root your phone. Sometimes you will get a service rep who doesn't know anything about rooting and/or could care less....sometimes you will get an XDA Member service rep pissed you are raising their premium, it all depends.

Thanks everyone for your responses! Awesome I'm glad Samsung is open minded with this matter. Yes there is no way my hardware issue is ROM/Software related so I'm hoping they won't care. I'm still going to flash the stock MB1 ROM and use the paid SuperUser app to hide the icon in the app drawer before sending it out just in case. Thanks everyone!
Sent from my SPH-L710 using xda premium

xbmoyx said:
Thanks everyone for your responses! Awesome I'm glad Samsung is open minded with this matter. Yes there is no way my hardware issue is ROM/Software related so I'm hoping they won't care. I'm still going to flash the stock MB1 ROM and use the paid SuperUser app to hide the icon in the app drawer before sending it out just in case. Thanks everyone!
Click to expand...
Click to collapse
What happens after you sent your device to Samsung.... Please let me know....nothing personal just curious to see what their reaction is

tasnim_tamim said:
What happens after you sent your device to Samsung.... Please let me know....nothing personal just curious to see what their reaction is
Click to expand...
Click to collapse
This thread is 3 years old, they probably won't answer.
Sent from my SCH-I535 using Tapatalk

Droidriven said:
This thread is 3 years old, they probably won't answer.
Click to expand...
Click to collapse
Maybe Samsung didn't fixed it at all and they forgot their XDA password...