Related
Hello... I recently bricked my phone. I was running MrRobinsons root injected Bell ROM on my sasktel S3 (radio wouldn't work with the sasktel rom)... Everything was going great for months.... I had xposed framework installed and all was fine.... Had the Wanam Exposed module installed and the visual tweaks worked good too... I had the STATUS changed to OFFICIAL as it was showing custom (didn't think nothing of it just thought it was kewl I could change it cosmetically)....
So the KNOX counter was tripped so I couldn't install anything OTA... no big deal.... But when the update came out from sasktel for my phone it offered to update to Kitkat 4.4.2... I was shocked lol.... So I installed the update knowing I would lose root, but I wanted to try out Kitkat....
Everything seemed to work OK... Downloaded... Installed... Rebooted.... Had some errors (root access not granted)... I then Rebooted my phone.... Screen went black.... And that is where it sits.... No response to anything I do... Doesn't power on... Doesn't go into recovery MODE or download mode, doesn't even show if the battery is charging.... I bought a USB jig to try to get into download mode... That didn't work... Tried plugging into computer but gives driver error "QHSUSB_DLOAD".... Aside from replacing the board inside or sending away to get it jtag'd .... Is there anything else I could try? I'm assuming I screwed it up by trying to update a BELL rom with a sasktel update.... Any help or advice would be tremendously appreciated... Thank you
I'm not desperate to have it fixed as I replaced it with an S4 but wanted it for a spare or for my kids....
Night_1 said:
Hello... I recently bricked my phone. I was running MrRobinsons root injected Bell ROM on my sasktel S3 (radio wouldn't work with the sasktel rom)... Everything was going great for months.... I had xposed framework installed and all was fine.... Had the Wanam Exposed module installed and the visual tweaks worked good too... I had the STATUS changed to OFFICIAL as it was showing custom (didn't think nothing of it just thought it was kewl I could change it cosmetically)....
So the KNOX counter was tripped so I couldn't install anything OTA... no big deal.... But when the update came out from sasktel for my phone it offered to update to Kitkat 4.4.2... I was shocked lol.... So I installed the update knowing I would lose root, but I wanted to try out Kitkat....
Everything seemed to work OK... Downloaded... Installed... Rebooted.... Had some errors (root access not granted)... I then Rebooted my phone.... Screen went black.... And that is where it sits.... No response to anything I do... Doesn't power on... Doesn't go into recovery MODE or download mode, doesn't even show if the battery is charging.... I bought a USB jig to try to get into download mode... That didn't work... Tried plugging into computer but gives driver error "QHSUSB_DLOAD".... Aside from replacing the board inside or sending away to get it jtag'd .... Is there anything else I could try? I'm assuming I screwed it up by trying to update a BELL rom with a sasktel update.... Any help or advice would be tremendously appreciated... Thank you
I'm not desperate to have it fixed as I replaced it with an S4 but wanted it for a spare or for my kids....
Click to expand...
Click to collapse
If the Jig isn't working, Jtag might be your your cheapest option.
I think the error happened cause you didn't remove root prior to flashing the update. That being said, it shouldn't have even let you install it while rooted.
Yeah... I know... Every time I checked for update before it said system had been modified and wouldn't allow it....
Then when the option to update popped up I was kind of shocked.... But figured I would OTA and reroot after if I wanted... Didn't think I would brick it, but sasktel update on a bell rom wasn't good I guess... Wasn't even thinking about that aspect hehe..
Is there anywhere reliable to send away to get it jtag'd?
Sent from my SGH-I337M using XDA Premium 4 mobile app
Night_1 said:
Yeah... I know... Every time I checked for update before it said system had been modified and wouldn't allow it....
Then when the option to update popped up I was kind of shocked.... But figured I would OTA and reroot after if I wanted... Didn't think I would brick it, but sasktel update on a bell rom wasn't good I guess... Wasn't even thinking about that aspect hehe..
Is there anywhere reliable to send away to get it jtag'd?
Sent from my SGH-I337M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
mobiletechvideos.com is a very well known one around here that offers the service.
BWolf56 said:
mobiletechvideos.com is a very well known one around here that offers the service.
Click to expand...
Click to collapse
Thank you very much
hey guys I'm on 4.2.2 still. Rooted it and deleted the galaxy walking app, so haven't been able to do legit update, and with working alot just haven't fooled with it. Anyway I'm off and have time, want to come up to kitkat, am I not able to update my LTE radio? I'm reading and searching before turning to asking, but all I'm seeing is if I update it my sound will act up. Am I stuck on an old radio now? Was hoping for improved signal, can I go stock, update and reroot and everything will be current?? Anyway any help is appreciated.
If you don't care about tripping Knox counter, just flash the NB4 firmware with Odin and you'll be good.. I recommend fenny's fixed firmware
Edit: well it will only trip if you flash custom recovery or kernel, other than that there is root method without tripping if you plan to stay stock
serio22 said:
If you don't care about tripping Knox counter, just flash the NB4 firmware with Odin and you'll be good.. I recommend fenny's fixed firmware
Edit: well it will only trip if you flash custom recovery or kernel, other than that there is root method without tripping if you plan to stay stock
Click to expand...
Click to collapse
im not staying stock, just want the updated lte radio on it. thinking of going lg g3 since sammy become such a pain in the ass. I've flashed stock and am updating official kitkat now, i guess that will update my modem and lte radio also, i'll reroot after that and throw something on there
If you are updating officially there shouldn't be a reason to manually update anything
i was just trying to save time, my home internet is crappy ( 100.00 bucks a month for 5mb, more like 1-3 mb) and you have to use wireless to update. I'm on kit now, abut to root and find a rom
sleekgreek said:
i was just trying to save time, my home internet is crappy ( 100.00 bucks a month for 5mb, more like 1-3 mb) and you have to use wireless to update. I'm on kit now, abut to root and find a rom
Click to expand...
Click to collapse
There is a thread in general specifically for updating radios for those of us still on MDL. If you were to have followed that guide you would have updated your radio without any sound problems, would still be KNOX free, and would still be able to have the option to run 4.2.2, 4.3, and 4.4.x ROMs flawlessly.
lordcheeto03 said:
There is a thread in general specifically for updating radios for those of us still on MDL. If you were to have followed that guide you would have updated your radio without any sound problems, would still be KNOX free, and would still be able to have the option to run 4.2.2, 4.3, and 4.4.x ROMs flawlessly.
Click to expand...
Click to collapse
i've been searching here for years on everything. Unless you stay in the loop everything is just cluttered. Even rooting, I'm looking and reading threads from pre 4.4.2 where chainfire link was last updated in 2013, it sucks searching here. And I thank you guys for the help. I'm rooted now and didnt want to ota, but everything I found to read said I could update the modem but not the LTE radio without sound issues... I must of missed something. LOL, I had a ton of tabs open from searches before posting. Been rooting since iden on nextels in early 2000's so it's just basic info I need thats hard to find here , tons of threads I guess. Anyway lets a get rom on this thing..
sleekgreek said:
Unless you stay in the loop everything is just cluttered. Even rooting
Click to expand...
Click to collapse
I totally agree and understand. I've pretty much been tinkering around the S4 forums since a few weeks after release (before I even purchased my S4) and have followed pretty well everything from square one so it's pretty easy to remember THAT I've read something but not remember WHERE I read it... Looking back through the Q&A and General threads, I couldn't imagine just now getting into the S4.
lordcheeto03 said:
There is a thread in general specifically for updating radios for those of us still on MDL. If you were to have followed that guide you would have updated your radio without any sound problems, would still be KNOX free, and would still be able to have the option to run 4.2.2, 4.3, and 4.4.x ROMs flawlessly.
Click to expand...
Click to collapse
I would be interested in that thread... I have updated my GSM modem (modem.bin) to NB4 but as I understood it, the LTE part is tied to the bootloader. So, those of us with MDL have to retain the MDL LTE radio. If it is possible to update the LTE radio, without the sound/wifi problems, and retain MDL bootloader and thus no Knox, I'd love a link!
Frankenscript said:
I would be interested in that thread... I have updated my GSM modem (modem.bin) to NB4 but as I understood it, the LTE part is tied to the bootloader. So, those of us with MDL have to retain the MDL LTE radio. If it is possible to update the LTE radio, without the sound/wifi problems, and retain MDL bootloader and thus no Knox, I'd love a link!
Click to expand...
Click to collapse
Ahh, you got me on that one. It didn't even register to me that the LTE modem is unaffected by that method. My apologies.
I apologize if i am not as clear in this post as I need to be. My dad tried to root his note 2 sgh i371 using odin but said that once he did this, he was unable to access the internet outside of connecting to wifi, he could not get any cellular data. Because of this issue, he tried to then un-root his phone by flashing 4.1.2 stock rom. Unfortunately, the issue of not being able to get cellular data persists. In his frustration, my dad bought a note 3 and gave his note 2 to me saying that if I could fix it I could keep it. This is my first android and I would like to make it my primary phone if possible. what I would like to simply to reset the phone to factory default settings by flashing the latest stock rom for the phone. I have Odin, I was hoping that someone could tell me where I could get the latest stock rom and, if they believed that flashing it would fix the cellular data issue. I do not believe my dad made a backup at all. Thank you in advance.
GreatGrizzwald said:
I apologize if i am not as clear in this post as I need to be. My dad tried to root his note 2 sgh i371 using odin but said that once he did this, he was unable to access the internet outside of connecting to wifi, he could not get any cellular data. Because of this issue, he tried to then un-root his phone by flashing 4.1.2 stock rom. Unfortunately, the issue of not being able to get cellular data persists. In his frustration, my dad bought a note 3 and gave his note 2 to me saying that if I could fix it I could keep it. This is my first android and I would like to make it my primary phone if possible. what I would like to simply to reset the phone to factory default settings by flashing the latest stock rom for the phone. I have Odin, I was hoping that someone could tell me where I could get the latest stock rom and, if they believed that flashing it would fix the cellular data issue. I do not believe my dad made a backup at all. Thank you in advance.
Click to expand...
Click to collapse
Sammobile has all the stock firmwares for our phones, check there. Also check in about phone to see what it says, if it says Baseband unknown, then the EFS folder (and subsequently IMEI #, etc) have been corrupted. It's possible flashing the latest stock firmware will fix it (it includes a new modem and all), so try that first.
http://www.sammobile.com/
absinthesummer said:
Sammobile has all the stock firmwares for our phones, check there. Also check in about phone to see what it says, if it says Baseband unknown, then the EFS folder (and subsequently IMEI #, etc) have been corrupted. It's possible flashing the latest stock firmware will fix it (it includes a new modem and all), so try that first.
Thank you very much for the advice. I am downloading the firmware now. baseband version is showing i317ucama4. Right now the phone is not activated with AT&T, is there a way I could test if I will be able to get cellular data before going to AT&T and activating it?
Click to expand...
Click to collapse
Well you're baseband is good. Just get a little cheap prepaid sim card for testing purposes. The stock firmware should fix anything in the modem or system that could have been corrupted... So flash that and have a cheap at&t Sim handy for testing.
Just use your father's sim card. Either it connects to the GSM network or it doesn't.
absinthesummer said:
Well you're baseband is good. Just get a little cheap prepaid sim card for testing purposes. The stock firmware should fix anything in the modem or system that could have been corrupted... So flash that and have a cheap at&t Sim handy for testing.
Click to expand...
Click to collapse
I attempted to flash the stock rom via odin v. 307 but I get a failed message. The phone shows I have a custom binary download (12 counts), official Samsung binar but, my system status is custom and my knox warranty is void: 1. Then there is a red message stating "unsupported version" at the bottom. The date for the stock rom was Jan 2013 AT&T, US on the sammobile site. I can no longer boot into the phone's OS, I am stuck in download mode until I manually restart and then it displays a message that I need to connect to Kies recovery. Thank you for the help so far, Any chance I can salvage this phone still? I did try going into Kies, but it cannot connect with my phone for some reason?
1425
rangercaptain said:
Just use your father's sim card. Either it connects to the GSM network or it doesn't.
Click to expand...
Click to collapse
Unfortunately, I got the phone when I was visiting home, I currently live a few states away from him. It would definitely make things much simpler if I didn't right now though.
GreatGrizzwald said:
I attempted to flash the stock rom via odin v. 307 but I get a failed message. The phone shows I have a custom binary download (12 counts), official Samsung binar but, my system status is custom and my knox warranty is void: 1. Then there is a red message stating "unsupported version" at the bottom. The date for the stock rom was Jan 2013 AT&T, US on the sammobile site. I can no longer boot into the phone's OS, I am stuck in download mode until I manually restart and then it displays a message that I need to connect to Kies recovery. Thank you for the help so far, Any chance I can salvage this phone still? I did try going into Kies, but it cannot connect with my phone for some reason?
Click to expand...
Click to collapse
It sounds like the phone was updated previously to either 4.3 or 4.4.2, which have Knox and that pesky counter. Technically you can't directly downgrade, so be sure you're downloading firmware that is 4.3 or higher. I didn't realize sammobile only went to MA4 for US AT&T. (In a pinch you can use Canadian firmware, but we have other links for stock firmware). Also, don't worry too much about Kies. It can be helpful, but honestly I could never get my note 2 recognized by kies either.
When I get back from taking my kids to school, I'll gather some links that will help you revive this phone Links below:
@GreatGrizzwald:
More recent links to stock firmware: STOCK PACKAGES TO MK6 This is LJ2 (4.1.2), MK6 (4.3) and up. He's got all the stock firmwares, available for flashing either in recovery on via odin. I've highlighted the one I would use in the attached screenshot (MK6- ODIN)
He also has a thread for NE5 (The latest firmware, 4.4.2) HERE
So if MK6 doesn't work, try NE5. One of those two has to work. You're dad already updated to either 4.3 or 4.4.2, I don't know which so start with 4.3 (MK6) and if it doesn't work try 4.4.2 (NE5)
On those two threads, he has a TON of links that will be helpful to you in getting back to stock also.
And here's a reference page with some useful links: One Stop Shop
This one is dedicated to downgrading back to LJ2 (4.1.2) from 4.3+, it MIGHT come in handy for you: Downgrade Instructions
If you have trouble with the stock firmware, you can also try Chainfire's CF Auto Root. It's stock firmware but it's rooted. Try the other firmwares by Zen Arcade first though CF AUTO ROOT
We'll get it going for you The stock firmware will re-flash the modem and all the configuration files so you're data should work again. Then you can do whatever you want, root, recovery, flash other stuff, or leave it stock. You got this
---------- Post added at 07:51 AM ---------- Previous post was at 07:09 AM ----------
GreatGrizzwald said:
Unfortunately, I got the phone when I was visiting home, I currently live a few states away from him. It would definitely make things much simpler if I didn't right now though.
Click to expand...
Click to collapse
Also you have to figure out if it's software or hardware. I'm inclined to believe it's software so I think if you get it back to stock you'll be good. If it was hardware, it wouldn't even recognize a sim being inserted (recently repaired an htc one mini with this problem, it needed a new Sim tray, thankfully it was only $20).
But it sounds more like a bad flash corrupted some of those important files and configurations controlling data connections, it's all good, if it's software it can definitely be fixed. If it were hardware it could still be fixed it would just be a bit more time consuming.
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
absinthesummer said:
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
Click to expand...
Click to collapse
Thank you for all this, I will start working with it today. You have been a huge help.
GreatGrizzwald said:
Thank you for all this, I will start working with it today. You have been a huge help.
Click to expand...
Click to collapse
No problem, I know how much of a pain it can be when things just don't seem to be working. But you have all the resources you need now and I'm gonna talk to my friend who runs the one-stop shop page to see if he will update it and add some of these resources to make it easier for you, and others with similar problems, to find what they need. Good luck!
1100
absinthesummer said:
One more thing, after you flash the stock firmware, and you have a sim card to test with, make sure your apn settings are correct for whichever carrier you're using. If the apn is wrong, or there is no apn listed, it won't connect. If you need assistance with that, let me know.
Click to expand...
Click to collapse
Hey, I was able to flash the stock rom you recommended, everything is working fine. Took the phone to AT&T and got a new sim card, everything seems to be working perfectly. Thank you again for all your assistance. could not have done this without your help.
GreatGrizzwald said:
Hey, I was able to flash the stock rom you recommended, everything is working fine. Took the phone to AT&T and got a new sim card, everything seems to be working perfectly. Thank you again for all your assistance. could not have done this without your help.
Click to expand...
Click to collapse
That is great news! I'm so glad it's working for you. Enjoy your (new-to-you) note 2 and keep those files on hand in case you need them in the future!
absinthesummer said:
No problem, I know how much of a pain it can be when things just don't seem to be working. But you have all the resources you need now and I'm gonna talk to my friend who runs the one-stop shop page to see if he will update it and add some of these resources to make it easier for you, and others with similar problems, to find what they need. Good luck!
Click to expand...
Click to collapse
If I can ask one more question, the phone keeps trying to download and install a software update however, it is unable to complete the update. Could this be because my counter was tripped? or could I be missing something that I should have flashed along with the stock firmware?
GreatGrizzwald said:
If I can ask one more question, the phone keeps trying to download and install a software update however, it is unable to complete the update. Could this be because my counter was tripped? or could I be missing something that I should have flashed along with the stock firmware?
Click to expand...
Click to collapse
There are a few reasons it won't flash. If it still says custom in download mode, for instance, from when your dad tried to root it. You can check in your about phone section to see if it says modified or official. It should say official there but when you're in download mode it will tell you your status:custom.
Something like
Model : SGH-i317
Binary count:
Firmware: Samsung official
Status: Custom (it should say official to receive OTA)
Knox warranty bit: 0x1 (from where your dad tried to root)
^Either of those last two can prevent an OTA from completing. The update checks for certain things and then continues or rejects based on those checks.
Also (and this shouldn't apply to you) if you have a custom recovery installed or you've rooted and removed pre-installed apps, it won't flash. Check those things and your OTA should work. If it still doesn't, you can download the ne5 firmware I linked you to before. That's official 4.4.2 firmware and it will update you to the latest via Odin if you can't take the OTA for whatever reason.
The firmware you flashed should have taken everything back to stock for you, but it wouldn't really reset the Knox counter & custom status... and that very well could would an OTA. It seems it does anyway, so just update yourself with Odin.
Lastly, if you really want to reset completely, and be able to OTA, you can do that downgrade method I linked before to completely reset your phone and allow you receive OTAs again. (It would take you ALL the way back to 4.1.2 and you would OTA back to 4.3-4.4.2. Personally, I wouldn't do all that unless I planned to sell it, because the firmwares that are released for OTAs are usually available on here to flash with Odin within a day of release, so you'll always be able to have the latest firmware regardless.
Hope that helps you didn't miss anything, it's just the nature of the OTA.
---------- Post added at 09:08 PM ---------- Previous post was at 09:02 PM ----------
Edited to add, you can also go about it another way: root it and use triangle away to reset your custom status & flash counter and then reflash the same firmware you did yesterday. Then you should be able to OTA. (Although I'm not 100% on whether or not the Knox counter will interfere with the OTA update, I think it's just the flash counter that trips it).
And if you want the OTA notice to stop completely, you can root it and turn off the notifications entirely. I wasn't sure on whether you wanted to take the update or not... if you do, I'd just update with the latest via Odin. It's the simplest way to update and you wouldn't have any issues or surprises that people tend to get with OTAs.
absinthesummer said:
There are a few reasons it won't flash. If it still says custom in download mode, for instance, from when your dad tried to root it. You can check in your about phone section to see if it says modified or official. It should say official there but when you're in download mode it will tell you your status:custom.
Something like
Model : SGH-i317
Binary count:
Firmware: Samsung official
Status: Custom (it should say official to receive OTA)
Knox warranty bit: 0x1 (from where your dad tried to root)
^Either of those last two can prevent an OTA from completing. The update checks for certain things and then continues or rejects based on those checks.
Also (and this shouldn't apply to you) if you have a custom recovery installed or you've rooted and removed pre-installed apps, it won't flash. Check those things and your OTA should work. If it still doesn't, you can download the ne5 firmware I linked you to before. That's official 4.4.2 firmware and it will update you to the latest via Odin if you can't take the OTA for whatever reason.
The firmware you flashed should have taken everything back to stock for you, but it wouldn't really reset the Knox counter & custom status... and that very well could would an OTA. It seems it does anyway, so just update yourself with Odin.
Lastly, if you really want to reset completely, and be able to OTA, you can do that downgrade method I linked before to completely reset your phone and allow you receive OTAs again. (It would take you ALL the way back to 4.1.2 and you would OTA back to 4.3-4.4.2. Personally, I wouldn't do all that unless I planned to sell it, because the firmwares that are released for OTAs are usually available on here to flash with Odin within a day of release, so you'll always be able to have the latest firmware regardless.
Hope that helps you didn't miss anything, it's just the nature of the OTA.
---------- Post added at 09:08 PM ---------- Previous post was at 09:02 PM ----------
Edited to add, you can also go about it another way: root it and use triangle away to reset your custom status & flash counter and then reflash the same firmware you did yesterday. Then you should be able to OTA. (Although I'm not 100% on whether or not the Knox counter will interfere with the OTA update, I think it's just the flash counter that trips it).
And if you want the OTA notice to stop completely, you can root it and turn off the notifications entirely. I wasn't sure on whether you wanted to take the update or not... if you do, I'd just update with the latest via Odin. It's the simplest way to update and you wouldn't have any issues or surprises that people tend to get with OTAs.
Click to expand...
Click to collapse
Awesome, that makes a lot more sense now. Thanks again.
Hey I forgot you don't have custom recovery. Anyway, I sent you PMs,and you can do a search of this very forum- use the search term "update" or "ota" and you will find a LOT of threads on boot failures after OTA. Most people got their phones back.
If you can't get into DL mode (Vol-, Home, Power), try getting into the stock recovery (Vol+, Home, Power) because you should/could be able to factory reset the device from there. Also hold the button combo longer than usual. If one recovery option (DL mode) isn't working, than theoretically the other should still be accessible, through which you can adb sideload to the device or try factory reset. I know it's frustrating, but you're not the first nor the last to have an OTA go wrong ;/ We'll get ya back up & running.
You're not the only one in trouble after that update: http://forum.xda-developers.com/galaxy-note-2-att/help/todays-update-soft-bricked-phone-t2939649
Hi- I'm an apologetic noob
Just got a sprint galaxy s6, activated it (all seemed to work), then rooted it with cfautoroot. Flashed via ODIN the CF-Auto-Root-zerofltetmo-zerofltetmo-smg920t.tar (which i guess is the t-mobile one).
Unfortunately, somehow wifi was lost-- it seems to turn on, but just keeps searching and never finds any networks (there are plenty near me). Phone and bluetooth seem to work fine.
I had read that there would likely be problems with deep sleep after root, so i thought the wifi might be part of it, and i tried to flash proactively G920PVPU1AOCF_G920PSPT1AOCF_G920PVPU1AOCF_HOME.tar.md5
that just lost me root access, but didn't restore wifi.
so i reflashed the CF-autoroot.
Now it says i have
android version 5.0.2
and baseband version g920pvpu1a0cf
hardware version g920p02
am rooted again
but wifi is still lost
It may be because of my efforts to 'restore' from TiBu (possibly because also of things like xposed framework which doesn't work with touchwiz)
anyway- can anyone help a clueless noob?
(sorry if in wrong section)
thanks
lost wifi after root
sorry- i meant lost wifi after root, not wifi radio
spammy l said:
sorry- i meant lost wifi after root, not wifi radio
Click to expand...
Click to collapse
Safe route is to flash the stock tar through Odin. Then try to root again.
Sent from my SM-N910W8
daniel4653 said:
Safe route is to flash the stock tar through Odin. Then try to root again.
Sent from my SM-N910W8
Click to expand...
Click to collapse
thanks so much for the reply
didn't work unfortunately
i just re-flashed the only stock i see available (via sammobile) from here
xxx (the sammobile site- it won't let me post link) /firmwares/database/SM-G920P/
wasn't any wifi back even without root. rooting didn't change it.
is there another 'stock' somewhere?
Solution?.... hard factory reset
so
i finally essentially gave up and tried a hard factory reset which erased all data.
the good news is wi-fi reappeared. I will try to root again and hope it was just a glitch in the process.
wish me luck, thanks for the help, and I hope my experience helps someone else.
I know that a lot of people are gonna say to read several other similar threads, but having gone through all of that I still don't get it.
THE SITUATION:
My Samsung Galaxy Note 2 GT-n7100 is :
1) Stock Android 4.1.2 Rooted
2) Modified with Xposed
3) TWRP (Latest, updated regularly)
4) Never been updated ever. Like never ever.
THE A-HOLE PROBLEM:
I honestly never bothered to flash anything on my note 2, since I have all the stuffs working perfectly as it is. Until the god-damn son of a gun WIFI started acting like a sissy she-dog. The problem is that the WIFI keeps on disconnecting itself and reconnecting itself automatically, wierdly enough, only when an app tries to access it. I hope everyone can understand how horrible it is, especially when you are talking dirty to your girlfriend over a whatsapp call and it keeps dropping, just like my errection.
All jokes aside, this has been driving me mad. In-case you need the details, here is what I did to solve my annoying problem :
1) Factory reset.
2) Reboot.
3) Phone works fine. Wifi works fine. Does not disconnect or reconnect. Seems like problem solved.
Then, the camel-crap happens.
4) Open Google play store, it updates. Play services updated. Need it to access the google services.
5) Open any internet enabled app.
6) Wifi switches on/off automatcally.
7) I tear my gonads off.
Side-Note : I also turned off the wifi power saving mode using *#0011#. I also made all the necessary changes in the wifi settings menu.
THE QUESTION:
Since I have never updated, my bootloader, etc are still stock. I read a thread that if I dont update the bootloader, future flashing will not work. I have no earthly clue so as to what the heck am I supposed to do.
I need some simple directions, to the point if possible. I have taken a full nandroid backup, just to be safe.
I think only a CFW now can solve this weird problem of mine. So, any help will be appreciated.
Newer roms require up-to-date bootloaders and modems. The easiest way to update both would be to flash the latest stock ROM from sammobile.com in Odin. Make sure you back up your data before flashing.
audit13 said:
Newer roms require up-to-date bootloaders and modems. The easiest way to update both would be to flash the latest stock ROM from sammobile.com in Odin. Make sure you back up your data before flashing.
Click to expand...
Click to collapse
Okay. But, what about the filthy Knox ? Also, what about my root? Also, what about Knox ? Hmm, I wrote knox twice. Now, thrice.
Simply put, knox is poo. I dont want that. So, how do I get the latest knick-knacks without knox. Is it possible to flash the latest bootloader, modem etc.
Sorry for using "noobish". I hate that language too, but when it comes to 40k phones, I get a bit nervous. Hope you can help. Or someone else.
Regards,
TheBasterd.
If you flash the latest bootloader, you'll get Knox.
Personally, I have never found Knox to interfere with flashing custom ROMs.
audit13 said:
If you flash the latest bootloader, you'll get Knox.
Personally, I have never found Knox to interfere with flashing custom ROMs.
Click to expand...
Click to collapse
So, here is the thing. If I go here : http://forum.xda-developers.com/galaxy-note-2/development/rom-resurrection-remix-5-6-0-t3278709 and downloaded the ROM, did all the stuff the ROM maker says and flash it.
Without the latest bootloader and other poo, you are saying that my flash will be unsuccessful ?
That ROM will probably need an updated bootloader and modem to connect to a cell network, detect a sim, and wifi.
If you want to, you can flash the ROM and see what happens.
audit13 said:
That ROM will probably need an updated bootloader and modem to connect to a cell network, detect a sim, and wifi.
If you want to, you can flash the ROM and see what happens.
Click to expand...
Click to collapse
Hey audit, thanks for sticking around and helping me bro. I really appreciate that.
So, I took your advice and have put the ROM from Sammobile.com for the latest bootloader and the modem stuffs.
Hope that will work. Also, when I flash the ROm, wont I loose my root ?
Yes, you'll lose root but it doesn't matter if you don't intend to use a stock ROM.
audit13 said:
Yes, you'll lose root but it doesn't matter if you don't intend to use a stock ROM.
Click to expand...
Click to collapse
Allright ! That was easy. Done and done. Thanks audit. (Thanks hitted)
Now, I will ensure a painless future for all noobs like me by making a tutorial. This thread can be marked as fixed. Thanks audiot bro.
It's great that you resolved the issue.
We're all here to help and learn from each other.