Related
When I first got my desire back in July, I was over the moon with all these jam packed features and functions and that AMOLED screen not to mention my very first smart phone. That didn't last, ever since I moved to the HTC Desire it gives me nothing but grief, I can hardly use it due to its faults, either be it hardware or software based; Boot Loops, Boot Freeze, Inconsistency, On-board Low Memory, Overheating, Buggy that's just a few problems with it.
Trying to fix it by debranding to the HTC Stock ROM didn't solve any problems.
I think the time has come now to move on from my desire and chose another device other than HTC, preferably iPhone?
Please share your experiences regarding this device and what would you recommend as my next device.
-Deeco
Did you try rooting, S-OFF and installing a non-stock ROM? I know 3-4 people with a Desire and they are all stock and they all work immaculately.
I am not interested in using a Non-Stock ROM and I don't think that would make any difference. I was talking generally about the phone and the amount of flaws disadvantages it's self from reliability.
I am absolutely satisfied with HTC after using 3 different phones made by them in the past 3 years. iOS and Apple are great for dumb people.
Why didn't you bring it in for warranty? Freezes and reboots are not normal on an unrooted desire.
Sent from my HTC Desire using XDA App
Deeco7 said:
I am not interested in using a Non-Stock ROM and I don't think that would make any difference. I was talking generally about the phone and the amount of flaws disadvantages it's self from reliability.
Click to expand...
Click to collapse
Maybe it's just a dodgy phone? A new ROM would amost certainly fix your issues providing they aren't hardware related. Have you tried to get it repaired using your warranty?
I came from an iPhone. iPhone get hotter than this phone.. you probably got a defective phone, mine works flawlessly...
And believe me, use this rom and you'll love it:
http://forum.xda-developers.com/showthread.php?t=741663
If you want to move to another phone look around go in shops there are many try an iPhone, Blackberry, or another phone. It's your choice no one can make that decision for you.
Ik Desire said:
Why didn't you bring it in for warranty? Freezes and reboots are not normal on an unrooted desire.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
That would be the obvious thing to do, but I am unwilling to have my AMOLED screen replaced with a SLCD one, that's just me.
The phone is defective you guys are right but as explained I don't want the above scenario to occur.
TBH, the only reason one I metioned iPhone is because it has all the features I want 'Front face camera' etc besides the Signal Problem, I can jailbreak/mod the phone to my desire and needs.
Deeco7 said:
That would be the obvious thing to do, but I am unwilling to have my AMOLED screen replaced with a SLCD one, that's just me.
The phone is defective you guys are right but as explained I don't want the above scenario to occur.
TBH, the only reason one I metioned iPhone is because it has all the features I want 'Front face camera' etc besides the Signal Problem, I can jailbreak/mod the phone to my desire and needs.
Click to expand...
Click to collapse
??
But you're not willing to root your Desire and flash a custom ROM?
brummer101 said:
??
But you're not willing to root your Desire and flash a custom ROM?
Click to expand...
Click to collapse
Like I mentioned above, I had rooted it but I consider flashing to a Custom ROM will make no difference whatsoever as my device is fault and unwilling to deliver to HTC under warranty due to screen replacement.
Deeco7 said:
Like I mentioned above, I had rooted it but I consider flashing to a Custom ROM will make no difference whatsoever as my device is fault and unwilling to deliver to HTC under warranty due to screen replacement.
Click to expand...
Click to collapse
so, you're looking for an excuse to buy an iPhone, or you are making yourself a martir? You dont want to try a custom ROM, but dont want to change the phone neither... so what's the point of this thread?
brummer101 said:
??
But you're not willing to root your Desire and flash a custom ROM?
Click to expand...
Click to collapse
Good point. I'd rather be with an Android OS than iOS, but with that said I'm not going to go over the rigmarole of an Android Vs iOS Vs WP7 'discussion'.
If it was my phone I'd take the time to atleast root it and get Clockwork recovery installed and try a light Sense-based ROM to see if it is defective hardware or not.
What's even more simple than that is resetting the phone to factory defaults to see if the problems persist, have you given that a go?
netomx said:
so, you're looking for an excuse to buy an iPhone, or you are making yourself a martir? You dont want to try a custom ROM, but dont want to change the phone neither... so what's the point of this thread?
Click to expand...
Click to collapse
Look, I'm not sure if I have phrased it wrong or something, but using a custom rom hadn't made any difference.
Deeco7 said:
Look, I'm not sure if I have phrased it wrong or something, but using a custom rom hadn't made any difference.
Click to expand...
Click to collapse
Aye you did, if it still persists you've got a duff phone. Warranty is the best bet, get them to replace it, then stick with it or try another phone. As it's pointless using a defective device, it'd drive me up the wall.
netomx said:
... so what's the point of this thread?
Click to expand...
Click to collapse
Exactly, so you've got a defective phone but won't RMA it, purely on the basis you'll get an LCD screen instead? Madness... Those early AMOLEDS are nothing to write home about too.
Deeco7 said:
Look, I'm not sure if I have phrased it wrong or something, but using a custom rom hadn't made any difference.
Click to expand...
Click to collapse
I thought you didnt tried a custom ROM, my bad. Well, send it to repair, and then sell it in ebay and get an AMOLED one. If you're insterested, and if you live in USA, I got the A8181 version, and I want the A8183 (WCDMA 850), and I dont care to get a SLCD screen.
The SLCD's are actually more vibrant in colour, although I'd say the AMOLEDs are more efficient.
Kalavere said:
The SLCD's are actually more vibrant in colour, although I'd say the AMOLEDs are more efficient.
Click to expand...
Click to collapse
Yet again, I have mentioned that I don't want to sacrifice my AMOLED screen for SLCD as I the AMOLED is what I payed for and is better in comparison. The Desire battery is bad as it is and adding SLCD will not do anygood.
I don't want to drift into that, a back to my first post.
Deeco7 said:
Yet again, I have mentioned that I don't want to sacrifice my AMOLED screen for SLCD as I the AMOLED is what I payed for and is better in comparison. The Desire battery is bad as it is and adding SLCD will not do anygood.
I don't want to drift into that, a back to my first post.
Click to expand...
Click to collapse
Considering you are asking people for help, you are being very short and sharp with people and really aren't being too polite. That was a statement, I was retorting generally to sarge78's post about screens.
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
I found this ROM:
http://www.gearengine.it/?page_id=2
...and would LOVE to run it on my AT&T GSIII but it says they're running it on the international version. I was planning on giving it a shot anyway but, while I'm working on rooting, I'd ask a few questions.
Think it'd work on the AT&T version?
If not, is there an equivalent ROM that will?
I want to keep ALL the stock functionality...camera wise, hardware wise (NFC, Bluetooth, etc) yet still getting the customization that that ROM afforded (I loved the Aroma installer, the inverted apps, etc) while running an overclock/undervolt kernel so I can juice this thing!
What are you guys running?!
One word of advice would be not to flash an international ROM on your AT&T device. I think that would lead to a brick.
Do some reading in the development sections to familiarize yourself with the basics.
Sent from my SGH-I747 using xda app-developers app
CamFlawless said:
One word of advice would be not to flash an international ROM on your AT&T device. I think that would lead to a brick.
Do some reading in the development sections to familiarize yourself with the basics.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I have to agree. I actually just commented in a thread before coming across this one: http://forum.xda-developers.com/showthread.php?t=2056655
Foxhound was flashed to their device, and their device was hard bricked. Please do not flash i9300 ROMs to US device variants.
I am currently running cm10.0.0 stable. It runs like a dream, not one issue with it so far. I would not recommend the new cm10.1 nightly builds until the data problem is fixed however.
LOL!!!
Well...this website was down for a few and I though ah hell, why not.
smh
Never actually heard of anyone hard bricking a phone. Awesome. This rounds out my Android experience nicely. Just as dude says, it doesn't do a damn thing. No power, not light, no vibration, nothing.
I can't believe there's no way to fix something like this. I'm all around amazed...I must say.
But yea...so...AT&T I go in the morning to test my acting skills I guess. *shrug*
And the Aroma installer was SO COOL!!!! What a shame...
Had I known the consequences could be so dire...
rmp5s said:
LOL!!!
Well...this website was down for a few and I though ah hell, why not.
smh
Never actually heard of anyone hard bricking a phone. Awesome. This rounds out my Android experience nicely. Just as dude says, it doesn't do a damn thing. No power, not light, no vibration, nothing.
I can't believe there's no way to fix something like this. I'm all around amazed...I must say.
But yea...so...AT&T I go in the morning to test my acting skills I guess. *shrug*
And the Aroma installer was SO COOL!!!! What a shame...
Had I known the consequences could be so dire...
Click to expand...
Click to collapse
Very sorry to hear your luck =( Good luck at AT&T... Don't let this deter you from future ROM flashes, just make sure you are flashing the correct GS3 variant. If you are on AT&T your device is model# i747 and the codename is d2att when flashing ROMs.
I didn't need too many acting skills, I just told them I woke up in the morning and my phone would no longer turn on. They swapped it out pretty quickly =) My hard brick came from a CWM flash when I was inexperienced at flashing. (I came from an iPhone... bleh). I had used a terminal emulator and used some commands to install CWM. Big mistake. I then followed Cyanogenmod's WIKI on installing CWM and it worked like a charm. =)
Of course, in my opinion, nothing beats TWRP recovery installation... Step 1: Download Goo Manager from the PlayStore. Step 2: Click menu and "Install OpenRecovery Script" Step 3: Wait for your phone to reboot into recovery =)
Well now that I'm done with my tangent, I think I'm heading to bed for the night lol. Good luck at the AT&T store tomorrow! ...and have a Happy Holiday! =)
RPelham said:
Very sorry to hear you luck =( Good luck at AT&T... Don't let this deter you from future ROM flashes, just make sure you are flashing the correct GS3 variant. If you are on AT&T your device is model# i747 and the codename is d2att when flashing ROMs.
I didn't need too many acting skills, I just told them I woke up in the morning and my phone would no longer turn on. They swapped it out pretty quickly =)
Again, good luck, and have a Happy Holiday!
Click to expand...
Click to collapse
Hey...it's all good man. I've been in the Android game since the G1 and STILL I'm getting firsts. LOL!!! I will ALWAYS hack, tinker and tweak. That's the fun of it...this included.
I KNEW it was the wrong version. However...what I DIDN'T know was the likely outcome! Had no idea. Only ever heard of hard bricks as a mythical monster-like sorta thing. Through my G1 days, GS days, HTC Doubleshot, HTC One S and AAAAAAAAAAALL the devices I've rooted and ROM'd in between (my tablets and who knows how many friend's devices), I've never seen or had a true hard brick happen. Had a close call sorta with the ex-wife's GS, but I fixed it.
Honestly didn't think this was something that could ACTUALLY happen!!!
We'll see what happens.
Thanks everyone!!
rmp5s said:
Hey...it's all good man. I've been in the Android game since the G1 and STILL I'm getting firsts. LOL!!! I will ALWAYS hack, tinker and tweak. That's the fun of it...this included.
I KNEW it was the wrong version. However...what I DIDN'T know was the likely outcome! Had no idea. Only ever heard of hard bricks as a mythical monster-like sorta thing. Through my G1 days, GS days, HTC Doubleshot, HTC One S and AAAAAAAAAAALL the devices I've rooted and ROM'd in between (my tablets and who knows how many friend's devices), I've never seen or had a true hard brick happen. Had a close call sorta with the ex-wife's GS, but I fixed it.
Honestly didn't think this was something that could ACTUALLY happen!!!
We'll see what happens.
Thanks everyone!!
Click to expand...
Click to collapse
I have been with Android through the GS1, GS2, and now GS3. I totally agree with you. I have done some really stupid stuff, but have always been able to fix the problem, mostly from help from this forum.
It may be just me, but it seems that it is a lot easier to brick the GS3 than its predecessors. Not from personal experience (knock on wood), but from reading through these forums.
Let us know what happens at the AT&T store. As an aside, does anyone ever know what happens in the long run when you turn in a hard brick to AT&T and get it replaced? I would imagine that once they JTAG it they would see that it was flashed. Could they charge you for the device?
cjranucci said:
I have been with Android through the GS1, GS2, and now GS3. I totally agree with you. I have done some really stupid stuff, but have always been able to fix the problem, mostly from help from this forum.
It may be just me, but it seems that it is a lot easier to brick the GS3 than its predecessors. Not from personal experience (knock on wood), but from reading through these forums.
Let us know what happens at the AT&T store. As an aside, does anyone ever know what happens in the long run when you turn in a hard brick to AT&T and get it replaced? I would imagine that once they JTAG it they would see that it was flashed. Could they charge you for the device?
Click to expand...
Click to collapse
That is a fantastic question. I was concerned about that myself the first time it happened. From my experience I was never charged when I went into the store to do the exchange. No bills came later in regards to it either. I think its pretty safe, but I wouldn't make any guarantees.
I also agree with you in that the GS3 seems a lot easier to brick than other phones I've dealt with.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Well...they gave me another one. Couldn't get another red one like I wanted since they didn't have any in stock which kinda sucks so I got the blurple one. Looks cool.
Obviously, I can't agree with the comments on the GSIII's resistance to bricking since I had something happen with this device that I've never seen or even HEARD of anyone doing. lol But it's all good. Time to start tinkering again.
Think I'm going to go the CM10 route since that is apparently a good ROM. However...does everything work with it? NFC and all? And...is there an OC/UV kernel that is compatible with that ROM?
As far as what they do with it after, I don't really know. I had to take it back to Best Buy since that's where I got it and it was so soon after getting it. I only had the thing...for...like...4 hrs when it got killed. lol I would imagine that they have the resources to easily fix a device that has had this happen. If they didn't replace it, I was just going to make a JIG for it (http://www.androidnova.org/unbrick-your-hard-bricked-smartphone/).
Thanks for all the help, guys!!!
Well...I didn't kill it. lol
So...first setup I tried:
ROM - http://forum.xda-developers.com/showthread.php?t=1766684
Kernel - http://forum.xda-developers.com/showthread.php?t=1756776
My ratings, out of 10?
Look and feel: 7...I only give it so low since it's EXACTLY the same as the HTC One S ROM I was running. This is usually a good thing but I was wanting something different.
Functionality: 4...every time I send a text, the damn thing says it didn't send! But it does! Very strange, very annoying, very unusable.
Customizability: 12...it's an AOKP ROM...with the Nova launcher...there are a mind bending number of options. I love it!
Quadrant score: 3...What the hell is an overclocked, current gen phone juiced to over 2.1GHZ doing getting ~3600 pts in quadrant? EXTREMELY disappointing.
Final words: Running Android 4.2...awesome. I love being cutting edge, but there isn't anything really awe-inspiring about it aside from the Jelly Bean 4.2 but the text messaging problem is just insurmountable.
Next is going to be this one:
http://forum.xda-developers.com/showthread.php?t=1949025
Going to keep the kernel and we'll see what happens! I'll let you know!
Glad it worked out. =) Just a heads up 4.2 has a lot of common bugs with it being so new. That texting problem is among many. Bluetooth issues, USB MTP issues, internal/external storage swapped, mobile data and WiFi issues to name a few.. I'd recommend sticking to 4.1 unless you don't mind the above annoyances. =p They will get ironed out soon enough I'm sure. =)
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
That ROM flat out didn't work...it booted and everything but the keyboard kept giving me an FC. No bueno.
Back to the other I go!
Can anyone recommend a ROM that is as customizable as the AWESOME AOKP ROMs but still retain a bit of the Samsung-ness? Like...I like having the burst shot in the camera, the cool gesture and motion stuff they have, etc. Is there a middle ground?
rmp5s said:
That ROM flat out didn't work...it booted and everything but the keyboard kept giving me an FC. No bueno.
Back to the other I go!
Can anyone recommend a ROM that is as customizable as the AWESOME AOKP ROMs but still retain a bit of the Samsung-ness? Like...I like having the burst shot in the camera, the cool gesture and motion stuff they have, etc. Is there a middle ground?
Click to expand...
Click to collapse
Checkout NexusMOD in the development forum. Its a touchwiz ROM with AOSP messaging and email. You can still run Nova Launcher if you want, and holo locker if you don't want the TW lock screen.
I'm still tinkering and trying different ROMs. Downloading LiquidSmooth right now, can't find the NexusMOD one mentioned and I just tryed to flash an AOKP ROM and it wouldn't flash.
I SO BADLY want the 4.2 to work. I LOVE it!!! The Camera (wish it had HDR and multi shot modes, though), the stock messenger, LOCK SCREEN WIDGETS...it's just awesome.
I'm with you all the way rmp5s(except the bricking part), I want this ROM sooo bad. It's stockish which I like, yet has a lot of mods, any word yet on it coming to I747?
Should it take the HTC M8 or the ONEPLUS one?
Is the htc getting stuck after a few months because laggy UI? like Samsung?
I really want a device that can last like 2 years without the need to flash new roms to keep it smooth...
Tell me about your experience with the device
* Im sorry if it the wrong forum to open this thread ...please tell me were to go
ilay47 said:
Should it take the HTC M8 or the ONEPLUS one?
Is the htc getting stuck after a few months because laggy UI? like Samsung?
I really want a device that can last like 2 years without the need to flash new roms to keep it smooth...
Tell me about your experience with the device
* Im sorry if it the wrong forum to open this thread ...please tell me were to go
Click to expand...
Click to collapse
I'm a phone junkie and want something new, but can't find anything I'd rather have. This is the longest I've had one phone for a long time. Plenty of dev still and stock or custom you won't experience any lag whatsoever.
My TMobile Samsung s21fe 5g freezes and reboots repeatedly over and over. It's not boot loop cause it stays frozen for 2 min approximately before reboot. I have hard reset, factory reset,ect and nothing's helped. Please help meee! Thank you
Welcome to XDA.
Does it happen when on the boot menu?
Can it stay on in that state?
Was the firmware recently upgraded or updated?
blackhawk said:
Welcome to XDA.
Does it happen when on the boot menu?
Can it stay on in that state?
Was the firmware recently upgraded or updated?
Click to expand...
Click to collapse
It's starts as soon as I put pattern to unlock in it. It had update couple months ago and was fine but earlier I used Odin and flashed the firmware. Odin said it was successful but the phone gave me this message I will link. Only think I can guess to do is twrp maybe and go from there? Any help would be great and ty!
Try flashing to the original firmware that worked.
If it's not firmware, it's hardware.
A different rom may bypass the damage if that's the cause.
This far more trouble than I ever experienced with Androids. My running rule is to leave the firmware alone, lol with Samsung's it has served me well.
Thank you I will try. Does it matter on rom choice? I have never ran into issues like this unless I caused them trying things I new nothing about lol. With it saying corrupted and the factory reset it but once reset it changes nothing that kinda throws me a little. I'm gonna keep trying due to really like the s21 but that's wearing thin after this. Thanks again
bchatter said:
Thank you I will try. Does it matter on rom choice? I have never ran into issues like this unless I caused them trying things I new nothing about lol. With it saying corrupted and the factory reset it but once reset it changes nothing that kinda throws me a little. I'm gonna keep trying due to really like the s21 but that's wearing thin after this. Thanks again
Click to expand...
Click to collapse
Go back before the most recent firmware upgrade or update.
There are billions of transistors in the SOC, ever wonder what happens if one or more fail?
If this is the case a different rom may not use the damaged area. There maybe no work around if this is the case. It's possible a BGA chipset has a fractured solder joint as well or anyone of numerous possible mobo failures.
Always protect phones from high G load impacts from drops with a good case. These can even cause internal damage to chipsets. Mobos are intolerant to board flexing as well. It's remarkable these devices are as robust as they normally are, all things considered.
Perfect, again thanks so much for input. I am gonna try and see what happens cause that make since. Appreciate your time to me help and take care!