Is it safe to do a factory reset via stock recovery straight out of the box... it won't lock the phone? Or should I first start it, do a fast set up and then do a factory reset?
Anyone?
mk89pwnz said:
Anyone?
Click to expand...
Click to collapse
I'm not going to jump straight into a reset. I had the boot loop problem and wiping the cache from recovery finished the phone off for good. DM verity error, failed to set up dirty target etc. Been unusable since. I'm personally not going to touch any recovery options until the stock levels are high so I can get a replacement straight away if something goes wrong. I'm sure they'll have addressed the issue with the firmware but not going to take the risk just yet.
zanderswigan said:
I'm not going to jump straight into a reset. I had the boot loop problem and wiping the cache from recovery finished the phone off for good. DM verity error, failed to set up dirty target etc. Been unusable since. I'm personally not going to touch any recovery options until the stock levels are high so I can get a replacement straight away if something goes wrong. I'm sure they'll have addressed the issue with the firmware but not going to take the risk just yet.
Click to expand...
Click to collapse
I was thinking about the same... if I get a bootloop then I'am doomed. I want to do this because a lot of ppl are saying it improves the battery life drastically but they mi might be wrong. BTW have you tired flashing stock firmware with odin or using Samsung smart switch? Imo it should fix the problem!
mk89pwnz said:
I was thinking about the same... if I get a bootloop then I'am doomed. I want to do this because a lot of ppl are saying it improves the battery life drastically but they mi might be wrong. BTW have you tired flashing stock firmware with odin or using Samsung smart switch? Imo it should fix the problem!
Click to expand...
Click to collapse
Yeah tried absolutely everything mate. Tried emergency recovery which got to 100% on the pc. When the install started on the device it sticks at 32% then restarts back into recovery. Exact same thing when I flashed the AP via Odin. Completely bricked
zanderswigan said:
Yeah tried absolutely everything mate. Tried emergency recovery which got to 100% on the pc. When the install started on the device it sticks at 32% then restarts back into recovery. Exact same thing when I flashed the AP via Odin. Completely bricked
Click to expand...
Click to collapse
That's rly sad... I will wait for a month and see how is the battery and then do a factory reset if I'am not getting good SOT. Rooted a lot of sammy devices can a lot of bootloops few bricks but if I managed to get in dl mode odin always saved me, maybe it has something to do with the battery problem?
mk89pwnz said:
That's rly sad... I will wait for a month and see how is the battery and then do a factory reset if I'am not getting good SOT. Rooted a lot of sammy devices can a lot of bootloops few bricks but if I managed to get in dl mode odin always saved me, maybe it has something to do with the battery problem?
Click to expand...
Click to collapse
I have read elsewhere that Samsung were initially pulling the mother boards out and replacing them to fix this issue. By the time mine died theyd recalled them worldwide anyway so they weren't interested in repairing it only to have to replace it.
zanderswigan said:
I have read elsewhere that Samsung were initially pulling the mother boards out and replacing them to fix this issue. By the time mine died theyd recalled them worldwide anyway so they weren't interested in repairing it only to have to replace it.
Click to expand...
Click to collapse
Maybe that's why it's a world wide recall mb problem + battery... rly sad that such a beast is having so much problems... BTW what is your note version?
mk89pwnz said:
Maybe that's why it's a world wide recall mb problem + battery... rly sad that such a beast is having so much problems... BTW what is your note version?
Click to expand...
Click to collapse
Yeah it's a much more widespread problem than the battery exploding it would seem. Affecting lots of people to varying degrees. Definately a massive part of why they've had to recall them. The battery issue means they get to use safety as the main driver instead of actually having to acknowledge there is a catastrophic problem with motherboards or firmware whatever it is that's causing the reboots. I have the exynos with the single sim. Uk version in blue. Yourself?
zanderswigan said:
Yeah it's a much more widespread problem than the battery exploding it would seem. Affecting lots of people to varying degrees. Definately a massive part of why they've had to recall them. The battery issue means they get to use safety as the main driver instead of actually having to acknowledge there is a catastrophic problem with motherboards or firmware whatever it is that's causing the reboots. I have the exynos with the single sim. Uk version in blue. Yourself?
Click to expand...
Click to collapse
Will be the same 930F the international one. That doesn't sound very good. Can't wait to get mine and test it out.
Maybe someone tried the factory reset on the new note 7?
Bump... anyone tried factory reset with stock recovery out of the box?
I was thinking about factory resetting my new N7 out of the box. Not sure I will though - would like to know the ramifications (good and bad). My original N7 has great battery life and no issues so IDK if should even mess with a factory reset to start with.
I factory reset from recovery on both my exchanged AT&T Note 7s at the store when exchanging, and then again when I got home and have had not a single issue.
mk89pwnz said:
Bump... anyone tried factory reset with stock recovery out of the box?
Click to expand...
Click to collapse
Im not sure what the big deal is here.....go ahead and reset it...it will do what it always does and has always done.
No more no less and the first thing i do when i get a new device.
If you set up then reset the only extra thing it will do is undo everything you just set up lol.
Kinda of counterproductive if anything.
Sent from my SM-N930F using Tapatalk 2
force70 said:
Im not sure what the big deal is here.....go ahead and reset it...it will do what it always does and has always done.
No more no less and the first thing i do when i get a new device.
If you set up then reset the only extra thing it will do is undo everything you just set up lol.
Kinda of counterproductive if anything.
Sent from my SM-N930F using Tapatalk 2
Click to expand...
Click to collapse
Just paranoid Was waiting for the phone so long if it bootloops then I'am f... Anyway will try booting on then going to recovery and do the wipe
Related
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:
Ok the meat of the problem is my vibration function quit. It happened after my battery dropped to around 10% yesterday. Though, even after a full charge its still not functional.
I've tried wiping the cache, reflashing InsertCoin Rom, restoring an old venom Rom, and updating from there. The best I can get is it now intermittently works.
Any other trouble shooting ideas?
It's happened to a bunch of people and appears to be a hardware problem. Some people have it randomly return to them. Mine works ... once a week maybe, but is otherwise permanently dead.
Nooooo!!! That sucks thanks for the info though. Guess I flash it to stock and see if I can warranty it.
devlmaycry81 said:
Nooooo!!! That sucks thanks for the info though. Guess I flash it to stock and see if I can warranty it.
Click to expand...
Click to collapse
Let me know how that goes please. My phone's vibration died within 4 hours of purchase. It's an international version so I'm going to have to pay HTC for the warranty -_-
Yeah it really sucks. It just went out without warning. I never had an issue like this with any of my galaxy phones or my ancient HTC aria.
I am sick of Lollipop on my Note 4. It has terrible battery life, my wifi doesnt connect unless I turn it off and back on. I have already tried clearing the cache, doing a battery pull, removing sim and SD card to no avail. I just want to go back to the way things were.
How do I go back to the factory image before Lollipop? I have looked and saw some threads mention odin, but nothing with a concrete tutorial. I dont want to brick the thing as I just sold my old phone and burnt my upgrade on the Note 4. The model number is SM-N910V. It is not the dev edition.
Only way to get back to KK 4.4.4 is to d/l the full firmware tar for the Note 4 retail and flash it with Odin 3.0.9.
outcasted2003 said:
Only way to get back to KK 4.4.4 is to d/l the full firmware tar for the Note 4 retail and flash it with Odin 3.0.9.
Click to expand...
Click to collapse
Ive used Odin before so that doesnt scare me. Im just looking for a tutorial on how to do it properly.
whitedragon551 said:
I am sick of Lollipop on my Note 4. It has terrible battery life, my wifi doesnt connect unless I turn it off and back on. I have already tried clearing the cache, doing a battery pull, removing sim and SD card to no avail. I just want to go back to the way things were.
How do I go back to the factory image before Lollipop? I have looked and saw some threads mention odin, but nothing with a concrete tutorial. I dont want to brick the thing as I just sold my old phone and burnt my upgrade on the Note 4. The model number is SM-N910V. It is not the dev edition.
Click to expand...
Click to collapse
Hey my wife is going through the same thing she just told me not even 30 minutes ago how much she hates lollipop and want to go back to kit Kat all the freezing screen not responding heavy lagg she's been rebooting and battery pulling all week ..smdh
Sent from my iPhone using Tapatalk
waco2hot33 said:
Hey my wife is going through the same thing she just told me not even 30 minutes ago how much she hates lollipop and want to go back to kit Kat all the freezing screen not responding heavy lagg she's been rebooting and battery pulling all week ..smdh
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
The battery drain isnt my gripe. Even on my phone all day using it for my job I still have 30% left at the end of the day and never start the day off with a full charge. The wifi issue is. I have 6Gb on Verizon between 2 accounts. 15 days into the cycle I had used 75% of my data due to my phone randomly disconnecting from Wifi. In the past we have never used more than 2Gb of our 6 combined.
whitedragon551 said:
The battery drain isnt my gripe. Even on my phone all day using it for my job I still have 30% left at the end of the day and never start the day off with a full charge. The wifi issue is. I have 6Gb on Verizon between 2 accounts. 15 days into the cycle I had used 75% of my data due to my phone randomly disconnecting from Wifi. In the past we have never used more than 2Gb of our 6 combined.
Click to expand...
Click to collapse
Ooh forgot to put that in I feel you she complains about the same wifi issue for some reason she's the one on my account that always uses the least data we have 15gb and lately she's been dropping her wifi also and using anywhere between 5 to 6gb a month when she usually only use 1 to 2
Sent from my iPhone using Tapatalk
and im still on kitkat over here. if it isnt broke down fix it
whitedragon551 said:
I am sick of Lollipop on my Note 4. It has terrible battery life, my wifi doesnt connect unless I turn it off and back on. I have already tried clearing the cache, doing a battery pull, removing sim and SD card to no avail. I just want to go back to the way things were.
How do I go back to the factory image before Lollipop? I have looked and saw some threads mention odin, but nothing with a concrete tutorial. I dont want to brick the thing as I just sold my old phone and burnt my upgrade on the Note 4. The model number is SM-N910V. It is not the dev edition.
Click to expand...
Click to collapse
Pretty much step by step Make sure to block OTAs afterwards or it will automatically take the update.
mademan420 said:
Pretty much step by step Make sure to block OTAs afterwards or it will automatically take the update.
Click to expand...
Click to collapse
Doesnt look like many people have done that. Any feedback on that method?
whitedragon551 said:
Doesnt look like many people have done that. Any feedback on that method?
Click to expand...
Click to collapse
Did it myself:good: He basically just took someone else's steps and added a little more detail to it, seen here.
Cant just go by the "Thanks" to tell you if people have used it or not
Once Im back on KK, how do I disable OTA? Im guessing there is an Android service that runs that needs to be stopped.
whitedragon551 said:
Once Im back on KK, how do I disable OTA? Im guessing there is an Android service that runs that needs to be stopped.
Click to expand...
Click to collapse
http://forum.xda-developers.com/note-4-verizon/general/disable-knox-ota-root-t2972263
or
http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294 and block com.samsung.sdm
Awesome. Thanks. Im back on KitKat and OTA updates are disabled, atleast until I start to hear better things about LP.
whitedragon551 said:
Awesome. Thanks. Im back on KitKat and OTA updates are disabled, atleast until I start to hear better things about LP.
Click to expand...
Click to collapse
Sweet! Same here. I probably will hold out until the next OTA. Hopefully it will be at least 5.1 with several fixes:fingers-crossed:
whitedragon551 said:
Awesome. Thanks. Im back on KitKat and OTA updates are disabled, atleast until I start to hear better things about LP.
Click to expand...
Click to collapse
mademan420 said:
Sweet! Same here. I probably will hold out until the next OTA. Hopefully it will be at least 5.1 with several fixes:fingers-crossed:
Click to expand...
Click to collapse
If you do decide to try LP again you may want to try a factory data reset (i.e., Settings, Backup and reset, Factory data reset) before taking the OTA to LP and do another factory data reset after taking the OTA to LP. That's how I upgraded from KK to the current LP 5.0.1 and I'm not experiencing any of the problems reported by others. I get good battery life and have no problems with dropped WiFi.
The thing that sucks is that you shouldn't have to do all of that, just to take an update. You shouldn't have to set up your phone again.
Missing root.
usmaak said:
The thing that sucks is that you shouldn't have to do all of that, just to take an update. You shouldn't have to set up your phone again.
Missing root.
Click to expand...
Click to collapse
Agreed, but this seems to be the situation that we face with the current upgrade process. It is a pain, but not all that bad, and probably required if you want to run LP anytime in the near future.
i need help! ill donate a little cash to the first person that finds a working solution im absolutely stumped on this. two weeks ago i tried upgrading my rooted sprint note 4 from android 4.4.4 to lollipop and everything seemed to go well until i opened up the camera and i went in to a bootloop. since then it hasn't stopped. i have tried flashing stock tars with odin. ive tried CM roms, noterized rom, tons of roms with custom recovery. ive used windows xp, and windows 7, 2 different computers, different cables, different usb ports. odin with administrator rights. nothing will stick. ive gotten passes and fails with odin. when it passes the phone will work as long as im on a charger after first boot once it comes off the charger it immediately goes in to a bootloop and then will not go past the samsung logo and if it does it reboots at the Spark logo. ive wiped cache 3x and factory reset 3x prior to flashing ive checked threads for the past two weeks and only made this account to ask for help. im not new to rooting and have never encountered and issue like this before. i can get in to download mode and recovery so i still have hope its just beyond my knowledge. occasionally recovery bootloops unless im on a charger as well. can someone PLEASE help me?? its making my stomach sick. my only option for internet is a galaxy s5 i bought with root for hotspot so everything i do takes forever to download. sorry for the legthy post im just trying to be detailed as possible for what ive already tried. like i stated above ive done my research this is my last option. thank you.
Could be your battery is dying. Heard of similar situations where it was due to battery failing.
ianmb said:
Could be your battery is dying. Heard of similar situations where it was due to battery failing.
Click to expand...
Click to collapse
i was thinking that as well but with my luck figured that would be too easy of a solution and weird that it decided to go ploop immediately after the flash. i play XBL off my hotspot and it can get rather hot. i usually keep an ice pack with a piece of cloth under it when i run it for an extended period of time though. ill buy a cheap one on ebay as a test. appreciate your input.
ianmb said:
Could be your battery is dying. Heard of similar situations where it was due to battery failing.
Click to expand...
Click to collapse
hey the stupid battery was the issue. dm me your PayPal if you'd like and I'll throw you a couple dollars for a beer or something. I feel like an idiot.
AssmanProctologist said:
hey the stupid battery was the issue. dm me your PayPal if you'd like and I'll throw you a couple dollars for a beer or something. I feel like an idiot.
Click to expand...
Click to collapse
Not a problem. Just glad to help out. Keep your money bro, times are hard for some.
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!