I recently rooted my incredible 2 successfully and got CM7 on with no problem. I was trying to install a new splash screen, but accidentally installed my existing radio (1.09.01.0722) instead. Now I can't get any wireless signal or dial *228. I've tried different radios, but none of them work now. Any ideas?
thanks
You're able to still use the phone, but you don't get any data or anything?
Sent from my ADR6350 using xda premium
It's not bricked if you can turn in on.....
Did you remove the radio file after you flashed?
Had same issue on build 109 I placed a call and it fixed it. Yes placed a call with no 3g or 1x and no baseband showing in software. 3g then showed up and baseband updated.
Sent from my Incredible 2 HD using XDA App
kubes069 said:
It's not bricked if you can turn in on.....
Did you remove the radio file after you flashed?
Click to expand...
Click to collapse
Ya that's what I was thinking too. Didn't make sense to me about what he was saying.
Sent from my ADR6350 using xda premium
Try reflashing your original stock ROM and everything... Do the Ruu if nothing else works.. you'll lose root, but your phone will most likely work again... Then if you really want to, reroot.
Sent from my ADR6350 using xda premium
faehsemc said:
reflash...stock ROM, RUU if nothing else works.. etc. etc.
Click to expand...
Click to collapse
This is what I was about to say. seems like your only option and hope it fixes it.
I always thought that the flashing your Radio twice thing was just a rumor cause I can never find any answer as to why this would brick your device.
guess it doesn't care it just does!
Hope you can get an insurance replacement being rooted. Verizon wouldn't even cover my week old battery that was bad from the factory and wouldnt take a complete charge because the VZW dip behind the counter noticed the custom boot screen and started asking questions. guess I should have hidden my mods!
I really wish you guys would look up the definition of "brick" if you don't understand what a BRICK is. please refer:
Bricked
Bricked refers to ANY hardware that is unable to start up due to bad software; Usually because of a bad software flash, a modification done improperly, loss of necessary files, being overheated from overclocking or overuse if the item is a lemon, a short-circuiting, or a Trojan that deletes necessary files for a few examples.
The noob bricked his PSP because he took out the battery while running a firmware update.
andybones said:
I really wish you guys would look up the definition of "brick" if you don't understand what a BRICK is. please refer:
Bricked
Bricked refers to ANY hardware that is unable to start up due to bad software; Usually because of a bad software flash, a modification done improperly, loss of necessary files, being overheated from overclocking or overuse if the item is a lemon, a short-circuiting, or a Trojan that deletes necessary files for a few examples.
The noob bricked his PSP because he took out the battery while running a firmware update.
Click to expand...
Click to collapse
^ this
Sent from my Incredible 2 using Tapatalk
Thanks for all the help. I tried switching to a different rom and that worked. I'm afraid to go back to CM7, but MIUI works just fine, so I'm sticking with it.
morenone said:
Thanks for all the help. I tried switching to a different rom and that worked. I'm afraid to go back to CM7, but MIUI works just fine, so I'm sticking with it.
Click to expand...
Click to collapse
No reason to be afraid... Do a full wipe and everything.. will he just fine.. and my real advice.. stay away from radios...
Sent from my ADR6350 using xda premium
Related
Has anyone figured out how to juice up the radio? Much like overclocking the CPU, but with the radio to improve up and down signal.
Willing to run any experimental programming on my phone if anyone has something to try out.
I'm not worried about bricking my phone, as that's already happened and I've brought it back to life again, so gimme all you've got!!!
Sent from my ADR6300 using XDA App
Haven't ever seen anything like that, no.
.......and FYI if you're still using it, it wasn't "bricked"
Other
You could always try the other released radios. The 11.xx has been scoring some pretty "oh my goodness, how fast can I uninstall this thing" ratings, but the 9.xx may do you some good. On all radios, YMMV; and be VERY VERY careful when flashing.
When it bricked it was stuck in an infinite boot loop, then after a few tries, wouldnt go further than hboot. I got lucky and found a way to restore an old rom I saved to my PC with the sdcard. I'm just glad I could still get it to run clockwork recovery.
Sent from my ADR6300 using XDA App
Bricked actually means that you can't power it on its 100% unresponsive.
Sent from my Incredible using XDA App
jdmba said:
You could always try the other released radios. The 11.xx has been scoring some pretty "oh my goodness, how fast can I uninstall this thing" ratings, but the 9.xx may do you some good. On all radios, YMMV; and be VERY VERY careful when flashing.
Click to expand...
Click to collapse
Interestingly, the 11.x radio increased my battery life about 20% (no major impact on my reception, if anything it seemed to have cost me a dB or two) compared to the 7.x radio. Tried the 9.x for a few days; cost me nearly half my battery life and caused the phone to run above 100F just for surfing the web.
It's DEFINITELY a YMMV situation.
6stringandy said:
When it bricked it was stuck in an infinite boot loop, then after a few tries, wouldnt go further than hboot. I got lucky and found a way to restore an old rom I saved to my PC with the sdcard. I'm just glad I could still get it to run clockwork recovery.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Your phone wasn't even remotely close to being bricked. That would be kind of like saying a dislocated shoulder is total paralysis.
A bricked phone is one that can't do anything at all and is completely unrecoverable. A basic rule of thumb is that if you can get to the bootloader, the phone is in no way bricked.
Gahh Its Lee said:
Bricked actually means that you can't power it on its 100% unresponsive.
Ah, ok. Had no clue. Thought that was when the programming crashes. Thnx.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Sent from my ADR6300 using XDA App
When did this go from radios to bricks? I get it, I didn't brick it. (2 point for numbnuts)
Where do I go to get other radio versions, and which ones don't play nicely with Dinc?
Sent from my ADR6300 using XDA App
Search for the radio thread in the dev section.
6stringandy said:
When did this go from radios to bricks? I get it, I didn't brick it. (2 point for numbnuts)
Where do I go to get other radio versions, and which ones don't play nicely with Dinc?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Sent from my Incredible using XDA App
6stringandy said:
When did this go from radios to bricks? I get it, I didn't brick it. (2 point for numbnuts)
Where do I go to get other radio versions, and which ones don't play nicely with Dinc?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Flashing radios is the number one way to brick your phone; basically, be careful and check MD5 sums.
Sent from my Droid Incredible running Myn's Warm Two Point Two RLS5.3.
Grr
I wish VZW would just release an official updated radio already.
As much as it ticked me off that some guy declared his own thread to be the new official thread, I think this has the links:
http://forum.xda-developers.com/showthread.php?t=886129
You can also get all Radios except the 11.xx radio here:
http://adrynalyne.us/files/di_radios/
Guys -
I installed the Splashtop 2 on my Nexus 7 running AOKP and Trinity Krenel, and it bricked my device twice. Just running the software and suddenly it crashes, then no buttons work. Then the screen starts to flash and it shuts down. I was unable to get into recovery. I need to push a new recovery to get it running back again. This has happen twice today. Anyone else having this issue?
Its bricked?
So you put it in the trash or sent it back to ASUS?
I'm going to go out on a limb here and say this is not related to splashtop.
I had an issue using Splashtop 2 today that freaked me out a little. Going from Sharp to Smooth froze my N7 and when it booted back up, which took longer than usual, the speaker made a faint but distinct "hissing" noise then a louder "tap"
Everything is working again but that's never happened before. Not sure I liked Splashtop 2 enough to bother with it after that.
Hemidroids said:
Its bricked?
So you put it in the trash or sent it back to ASUS?
Click to expand...
Click to collapse
No.. I know how to get out of a jam. The device would not boot afterward the system froze, then rebooting I got stuck at Google screen. Then it wouldn't get into recovery from bootloader I had to flash a new recovery and flash back up. Sounds like it was bricked at the time to me.
Sent from my Nexus 7 using xda premium
tdrussell said:
I'm going to go out on a limb here and say this is not related to splashtop.
Click to expand...
Click to collapse
I would see why you would say this....however this happened twice when using the new splashtop. My set up or system has not changed in days. Only thing that changed was me installing splashtop. Once I stopped using it and went back to the old one. No issues. Someone else n the market review described the same thing to a t.
Sent from my Nexus 7 using xda premium
Installed HD2 this morning and same problem, freeze when changing from sharp to smooth. Hard reset twice, to get it to boot now the speaker sounds like its blown, was streaming some video from the PC. Running EOS + stock kernel.
Something isn't right with it that's for sure, avoid for now is my advice.
Sent from my Nexus S using xda premium
Knether said:
No.. I know how to get out of a jam. The device would not boot afterward the system froze, then rebooting I got stuck at Google screen. Then it wouldn't get into recovery from bootloader I had to flash a new recovery and flash back up. Sounds like it was bricked at the time to me.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Oh......so its not a brick. Might want to change the title.
Splashtop also froze my Nexus 7, fortunately hasn't knackered the speaker or anything. I was going to blame my undervolt though...
sensory said:
I had an issue using Splashtop 2 today that freaked me out a little. Going from Sharp to Smooth froze my N7 and when it booted back up, which took longer than usual, the speaker made a faint but distinct "hissing" noise then a louder "tap"
Everything is working again but that's never happened before. Not sure I liked Splashtop 2 enough to bother with it after that.
Click to expand...
Click to collapse
I had this same thing happen to me. Everything froze up then my Nexus rebooted itself. Other than that the app runs pretty damn good for me. No rooting or roms on mine.
PA 1.97a, Trinity Kernel @ 1640 (ondemand/deadline), Nova Launcher, Dark Jelly Theme.
Daily use out of Splashtop with absolutely no issue. It's one of the things I like best about this tablet.
my only negative view towards the nexus 7 is the influx of noobs that dont know what brick means. i have a g1 with a bad spl flash. that is a brick. you sir just need to flash a factory img. your not bricked.
xxmonsterx said:
my only negative view towards the nexus 7 is the influx of noobs that dont know what brick means. i have a g1 with a bad spl flash. that is a brick. you sir just need to flash a factory img. your not bricked.
Click to expand...
Click to collapse
The only reason he can't access recovery is because of a bug in boot loader 3.34 so its even less of a brick and more of a don't OV and OC
Sent from my Nexus 7 using xda app-developers app
xxmonsterx said:
my only negative view towards the nexus 7 is the influx of noobs that dont know what brick means. i have a g1 with a bad spl flash. that is a brick. you sir just need to flash a factory img. your not bricked.
Click to expand...
Click to collapse
Influx of noobs? I've been around XDA a bit longer than you. I am deeply sorry forum wordsmith for using the word brick not in the fashion you so desired.
Moving on:
I just wanted to get this word out there and just making sure its not my device. I spoke with Splash top and "they're on it." So we'll see :highfive:
Sorry good sir. I do suppose that was a bit rude. I may have taken out my dissapointment with what xda is becoming on you. My bad bud. I'm not here to compare the d!cks bro. I just can't stand seeing all these help I'm bricked threads.
xxmonsterx said:
Sorry good sir. I do suppose that was a bit rude. I may have taken out my dissapointment with what xda is becoming on you. My bad bud. I'm not here to compare the d!cks bro. I just can't stand seeing all these help I'm bricked threads.
Click to expand...
Click to collapse
No harm no foul. I don't hold grudges. Conflict resolution at its best. Thanks for that, means a lot and restores my faith in people. :laugh:
Harry GT-S5830 said:
The only reason he can't access recovery is because of a bug in boot loader 3.34 so its even less of a brick and more of a don't OV and OC
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
What is this bug you speak of?
Also, OC and OV is causing issues? Sorry If i dont know about this just yet, is there a thread that speaks about this?
Knether said:
What is this bug you speak of?
Also, OC and OV is causing issues? Sorry If i dont know about this just yet, is there a thread that speaks about this?
Click to expand...
Click to collapse
Try acessing recovery through boot loader on a healthy N7 and not plugged in, you will find that you can't access recovery. There's quite a few "Q" threads saying that I OC to 1600 and overvolted by 50MHz across the board, and my nexus fried? Why is this??
Sent from a Nexus 7 using my fingers
I've got the same problem with Splashtop and Nexus 7. Original ROM, no root. After switching smooth<>shart Nexus just reboots. Also there seems to be nothing interesting in logcat.
qrees said:
I've got the same problem with Splashtop and Nexus 7. Original ROM, no root. After switching smooth<>shart Nexus just reboots. Also there seems to be nothing interesting in logcat.
Click to expand...
Click to collapse
I seems to be fixed after todays update, but it's still strage that single app could crash the whole device.
Kinda new to the xda still trying to figure out rules. Kudos to the synergy guys tried a couple different roms and I'm addicted to this rom and is features. Just flanged the r484 and am support happy the mms issue wad fixed. Multi Window flawless. No problems with cameras. The only thing I have had issues with is reception 4g/3g. It seemed more stable with r433. Using ziggy and used custom install with pre selected synergy recs. If this post is on the wrong spot mod please fix. If someone has an answer for me greatly appreciated
Sent from my SPH-L710 using xda app-developers app
Have you tried changing your modem ? Or going to a different ROM and updating prl and profile ?
http://i1202.photobucket.com/albums/bb374/TexasEpic/ThePeoplesROM-KennyGlass123/daniel4653.png
Changing modem? Haven't heard that one yet. If you could elaborate on that one that would help. As for prl and profile I'll try that but I didn't have the issue with the previous build. Should I just try flashing stock and update? Then reflash. My area hasn't changed. Stock and previous r434 build I had very constant and strong 4g everywhere. With the r484 it can't make up its mind between 3g/4g. Thanks Daniel for the info
Sent from my SPH-L710 using xda app-developers app
You change your modem through Odin. Been a while since I've done it (on HTC for a while there when my Epic broke it's charge port) but as I recall you put the phone in download mode, put them modem in the 'Phone' field after downloading it to your computer, and fire away. Do check the instructions first, I'm going off of memory from six months ago.... Some radios work better with some phones than others. Depends on your device.
toolegit said:
You change your modem through Odin. Been a while since I've done it (on HTC for a while there when my Epic broke it's charge port) but as I recall you put the phone in download mode, put them modem in the 'Phone' field after downloading it to your computer, and fire away. Do check the instructions first, I'm going off of memory from six months ago.... Some radios work better with some phones than others. Depends on your device.
Click to expand...
Click to collapse
In CWM or TWRP recovery, he can flash new modem in .zip format from this thread- http://forum.xda-developers.com/showthread.php?t=1787677
FOLLOW DIRECTIONS CLOSELY, FLASHING MODEM WRONG CAN BRICK YOUR DEVICE!!
sent from somewhere
That's probably (read:is) easier than Odin.
Thanks for the input guys. Very appreciated. I'll try that the next time I'm at the home computer and let you know.
Sent from my SPH-L710 using xda app-developers app
toolegit said:
That's probably (read:is) easier than Odin.
Click to expand...
Click to collapse
Anything is easier than ODIN for most people.
sent from somewhere
joeyhdownsouth said:
Anything is easier than ODIN for most people.
sent from somewhere
Click to expand...
Click to collapse
I just came from HTC so odin is the simple for me!!
Nooblube said:
I just came from HTC so odin is the simple for me!!
Click to expand...
Click to collapse
Trust me I know about HTC, just s-offed my brothers HTC evo lte.
sent from somewhere
I s-offed an Evo3D.... that was fun. I got it right the first time by some luck....
Odin is *much* easier than HTC.
toolegit said:
I s-offed an Evo3D.... that was fun. I got it right the first time by some luck....
Odin is *much* easier than HTC.
Click to expand...
Click to collapse
I know right. I hate how the only way to root the newer HTC devices is by doing sketchy wire tricks.
Dunno about the ET4G, but my Epic was fairly easy to root. But the GS3 was much easier. My wife's Photon Q was about the same as the GS3.
I had an HTC but never played with it due to watching a friend ruin multiples of them. So I never attempted. Had my gs3 for three days before I rooted and started modding. For never doing this before and having mediocre comp skills this was fairly simple. Just want to make sure I cover my bases before doing something wrong.
Sent from my SPH-L710 using xda app-developers app
I made the ultimate mistake the other day. I flashed a kernel for another device onto my S3 and of course paid the price of bricking my phone.
To set the scenario, I had back surgery last Thursday and was released from the hospital on Friday with a supply of pain killers and orders to not do anything. Well, while sitting around doing nothing I got bored and decided to work on a couple of my friends tablets that needed rooting and roms installed. I got them done without any issue and then decided to mess with my phone. There were a couple of new kernels I wanted to test and so I decided to do this. I booted into recovery and selected the kernel and flashed. At that moment I realized that the kernel I just flashed was not for my phone and when I tried to turn on the phone and nothing happened, I knew immediately what I had done and after saying a few nasty words to myself I started searching for a way to fix it. While searching through the forums I kept reading about MobileTechVideos.com and their ability to jtag repair phones. Since I have never had to do this and my phone was not going to work anyway I decided to give them a call and see what they had to offer. I called them and asked about their services and they said that it should be no problem fixing my phone. I live in Dallas and the company is in Bryan, about 3 1/2 hr drive, I decided the easiest and fastest way to get my phone repaired was to take it to them and wait. On Tuesday morning I drove to Bryan and dropped off my phone. When I had called them they told me it might be a couple of hours to fix it, but once I told them it was a tmobile device they told me to wait because it might only take a few minutes. During this time they showed me around the office and I was really impressed. What impressed me the most is that no one working for this comany could have been over 25, even the owner. So after a brief tour of the office, about 10 minutes, my phone was fixed and was ready to go. I paid my $60, which I believe was well worth it, said thank you and was on my way with my fully functional phone.
They never asked me to post anything and I don't have any affiliation with this company. I just want to post about a company that provided the service they said they would at a price that is reasonable since without it I would have a $600 paperweight. So if anyone ever happens to make the foolish mistake that I made and you need your S3 repaired, I would 100% recommend this company. Here is the link to their website, http://mobiletechvideos.mybigcommerce.com, mods let me know if this is not allowed and I will remove it.
I know I am always questioning online companies likes these, but this particular company has earned a customer for as long as they are open and support whatever device I happen to be using. I just hope that since I made this mistake I will hopefully never make it again.
Moral of story: If on heavy doses of pain killers don't crack flash kernels. If might cost you in the end. :}
Never bricked a phone before but I've heard great things about that company. If I ever run to trouble I'll surely go to them immediately.
Thanks for the review.
Sent from my SGH-T999 using xda app-developers app
Thanks for the review - it's good to hear good comments about the company "just in case".
Hope you're feeling better.
Cool.... Drugs say No to them... Get well
Sent from my SGH-T999 using xda app-developers app
bgbagz said:
Cool.... Drugs say No to them... Get well
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Pain meds after back surgery are a definite yesssssss, just don't brick your phone. lol
Happy to read a ringing endorsement, though - also "just in case".
Hey dude. Im in Dallas too. Good to know. I read all about them. They are really good in jtag fix devices. They were the first ti have s-off on the htc one. They did it after an hour of getting the phone. I havent brick any phones yet but I have their number save just in case. I have seen where they sale the jtag device to do it yourself. It cost about $100 it is well worth it
Sent from my SGH-T999 using xda app-developers app
Good service but more expensive than some.. but local is good.
Sent while sleeping in chair.
I'm glad your device is back and operational. Thanks for letting us know about a trusted reputable service.
Sent from my SGH-T999 running Chihuahua v1 ROM
Thanks. I am not one who likes reviewing companies, but this one time I felt it was justly deserved. I read to many threads about shipping your device to someone and for a cheaper cost they will fix it. That makes me uncomfortable. I would rather pay a little more for the peace of mind. Even then I was more comfortable driving as far as I did, after just having surgery, because of my skeptism. That is why I felt the review was warranted to help someone when they are not local.
Sent from my Transformer Prime TF201 using xda premium
Josh @mobiletechvideos is certainly a trusted guy. He's been here since vibrant days.
Sent from my SGH-T999 using Tapatalk 2
I didn't realize your phone would get bricked with a bad kernel. You can't just go into odin and restore the original system image?
Not criticizing here, I'm just trying to learn something. Glad you had a good experience, as I'm sure at some point in my life I'm going to brick a phone.
Sent from my SGH-T999 using xda app-developers app
I can confirm that flashing a wrong kernel will brick your phone. I did that and still not sure if it was wrong one but in did screwed my phone, luckily I exchanged it for another device since I had it for a week.
Sent from my SGH-T999 using xda app-developers app
I have done the same thing. I flashed an international ROM on my T-999. I had also read great reviews people had using Mobiletechvideos. He had mine back to me in less than 1 week. Awesome work. If someone from MTV is on here, thank you!!
wcterp said:
I didn't realize your phone would get bricked with a bad kernel. You can't just go into odin and restore the original system image?
Not criticizing here, I'm just trying to learn something. Glad you had a good experience, as I'm sure at some point in my life I'm going to brick a phone.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
It wasn't a bad kernel, it was a kernel for a different device. I was working on several devices that day and put a kernel for a nook tablet into my S3 folder by mistake. Teaches me to only work on one device at a time.
Sent from my Transformer Prime TF201 using xda premium
Yes don't take painkillers give em to me lol
thanks for the write up good to know
Can't you just re flash the entire rom stock or not with Odin or cwm?
I dunno, first time I "bricked" my phone was from an incorrect kernel also. Just downloaded stock touch wiz rom go to download mode and flash with Odin.
I'm not aware that you can brick your phone unless you mess with the bootloader itself.
Bricking means exactly what it sounds like. It's just a piece of useless hardware that you can't recover, in this case, with an incorrect kernel flash, you can, either through another kernel that is compatible with your device or re flash the entire rom; with either Odin or cwm.
wardoc22 said:
Can't you just re flash the entire rom stock or not with Odin or cwm?
I dunno, first time I "bricked" my phone was from an incorrect kernel also. Just downloaded stock touch wiz rom go to download mode and flash with Odin.
I'm not aware that you can brick your phone unless you mess with the bootloader itself.
Bricking means exactly what it sounds like. It's just a piece of useless hardware that you can't recover, in this case, with an incorrect kernel flash, you can, either through another kernel that is compatible with your device or re flash the entire rom; with either Odin or cwm.
Click to expand...
Click to collapse
When trying to connect to computer it would not recognize the device correctly. So no odin if you can't connect to computer. No flashing anything else if the phone doesn't turn on. That would be as hard bricked as you can get.
Sent from my SGH-T999 using xda premium
tmjohnsonfse said:
When trying to connect to computer it would not recognize the device correctly. So no odin if you can't connect to computer. No flashing anything else if the phone doesn't turn on. That would be as hard bricked as you can get.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Yeah but you can't hard brick it if you flash a wrong kernel unless the kernel replaces your bootloader.
Oh wait, ok I get it. You flashed a kernel that replaces the bootloader also, like with the international dual boot kernel
wardoc22 said:
Yeah but you can't hard brick it if you flash a wrong kernel unless the kernel replaces your bootloader.
Oh wait, ok I get it. You flashed a kernel that replaces the bootloader also, like with the international dual boot kernel
Click to expand...
Click to collapse
Correct!
Sent from my Transformer Prime TF201 using xda premium
Yesterday I made the mistake of taking the OTA update to 4.3 while in the process of doing a clean install of the new MOAR rom. Unfortunately, I had failed to do the proper homework otherwise I would have known to avoid the update like the plague. Luckily, I didn't manage to brick my phone, by trying to revert back to an earlier bootloader, but I am stuck now with a tripped warranty bit, and a phone that drains battery at almost 1% per 5mins while being almost completely unable to maintain a cell or data signal.
Now, I know it's going to be a little time before devs have a chance to tear apart 4.3 to fix it's issues, but I'm hoping that I can get some guidance on how I might improve my phone's performance, or at least minimize the negative aspects of the new update in the meantime. Right now I am running MOAR 7 and I have already tried resetting and reinstalling the rom fresh.
Thanks for any help.
Sent from my GT-N8013 using xda app-developers app
treblesum81 said:
Yesterday I made the mistake of taking the OTA update to 4.3 while in the process of doing a clean install of the new MOAR rom. Unfortunately, I had failed to do the proper homework otherwise I would have known to avoid the update like the plague. Luckily, I didn't manage to brick my phone, by trying to revert back to an earlier bootloader, but I am stuck now with a tripped warranty bit, and a phone that drains battery at almost 1% per 5mins while being almost completely unable to maintain a cell or data signal.
Now, I know it's going to be a little time before devs have a chance to tear apart 4.3 to fix it's issues, but I'm hoping that I can get some guidance on how I might improve my phone's performance, or at least minimize the negative aspects of the new update in the meantime. Right now I am running MOAR 7 and I have already tried resetting and reinstalling the rom fresh.
Thanks for any help.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
If you're on MOAR, then your battery issues are not being caused because you tripped the warranty and flashed the OTA. You may flash any rom, mod, kernel, tweak, etc, you want through CWM, just don't try to downgrade to a different bootloader(ie 4.1.2), through Odin, or you'll brick. Try different roms, modems, combinations, just like before, until you get back to what you want. Good luck
Sent from my SPH-L710 using Tapatalk
So I can reflash the MD4 modem? I was under the impression that I was stuck with MK3. Can I basically change anything I want as long as I don't try to Odin in an older update?
Sent from my GT-N8013 using xda app-developers app
treblesum81 said:
So I can reflash the MD4 modem? I was under the impression that I was stuck with MK3. Can I basically change anything I want as long as I don't try to Odin in an older update?
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
Yes, you can flash the MD4 modem, but I tried flashing down to a 4.1.2 modem and lost data, so that may happen to you(probably will). And as long as you flash from cwm you are fine. But read any ROM OPs very carefully, because there are a few out there that flash a bootloader if I'm not mistaken. But overall, yes, you are ok flashing as long as you don't use Odin to try to downgrade to a different bootloader.
Sent from my SPH-L710 using Tapatalk
Well, I guess its good to know that I have some options, but also disappointing that I can't just Odin in a complete package to start from, since in the past that has always been the best way to ensure stability in the end result. As for the warranty bit, I'm not too worried about it, since it can only really hurt me if I need to take it to sprint for some work. That being said, if there really is no way to reset it, or completely remove Knox for that matter, I probably won't be buying another samsung phone... I really don't like the idea that the manufacturer would booby trap their product like that.
Sent from my GT-N8013 using xda app-developers app
treblesum81 said:
Well, I guess its good to know that I have some options, but also disappointing that I can't just Odin in a complete package to start from, since in the past that has always been the best way to ensure stability in the end result. As for the warranty bit, I'm not too worried about it, since it can only really hurt me if I need to take it to sprint for some work. That being said, if there really is no way to reset it, or completely remove Knox for that matter, I probably won't be buying another samsung phone... I really don't like the idea that the manufacturer would booby trap their product like that.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
I'm sure it's only a matter of time before someone cracks it. Genius devs like @Chainfire live for challenges like this
Sent from my SPH-L710 using Tapatalk
I hope they crack it soon.. I've already had the urge to throw it against a wall more than once today. Its magically unrooted itself three times already and the problems seem to multiply every time I try a different OS in the hopes that one will work well.
Sent from my GT-N8013 using Tapatalk