No Wifi after attempt to root - Samsung Galaxy Mega

My mega installed cwm and rooted fine without a problem. I got it unlocked though. it is a carrier version but the guy unlocked it before selling to me.
I try doing the same to my friend's mega who's a locked rogers carrier version and not only did cwm recovery refuse to install, root would not work, and i kept getting some yellow message at the top right called "warranty bit: kernel"
I tried flashing the stock rom via odin and did a full factory reset. wifi will not switch on..it just stays in the off position.
does this have something to do with knox? How come my mega rooted no problem and i never had these problems with my mega yet my friend's mega is basically locked out? Do I need to unlock his phone before rooting? Is this because the bootloader is locked due to the fact that it's a locked phone?
Help please
Thanks.
EDIT
I was able to flash cwm philz touch version and rooted successfully. I still get the Warranty Bit Kernel message at the top and the phone boots a lot slower than it should I also downloaded wifi fixer and it states my wifi is "stuck".

d4ndr0id said:
My mega installed cwm and rooted fine without a problem. I got it unlocked though. it is a carrier version but the guy unlocked it before selling to me.
I try doing the same to my friend's mega who's a locked rogers carrier version and not only did cwm recovery refuse to install, root would not work, and i kept getting some yellow message at the top right called "warranty bit: kernel"
I tried flashing the stock rom via odin and did a full factory reset. wifi will not switch on..it just stays in the off position.
does this have something to do with knox? How come my mega rooted no problem and i never had these problems with my mega yet my friend's mega is basically locked out? Do I need to unlock his phone before rooting? Is this because the bootloader is locked due to the fact that it's a locked phone?
Help please
Thanks.
EDIT
I was able to flash cwm philz touch version and rooted successfully. I still get the Warranty Bit Kernel message at the top and the phone boots a lot slower than it should I also downloaded wifi fixer and it states my wifi is "stuck".
Click to expand...
Click to collapse
That yellow warranty you see is because knox is present in the phone..what model is your mega.?

i have same problem. My model is mega 6.3.

i also have same problem with i9205 no wifi and gallery cannot open

starmaster10 said:
That yellow warranty you see is because knox is present in the phone..what model is your mega.?
Click to expand...
Click to collapse
It's the same sgh-i527. I figured out the problem. Newer Megas plus all future Samsung devices will come with with a permanent knox bootloader. Once the knox kernel goes 0x01, not only is your warranty void but it ****s your stock Rom up.
My first mega was a older version without the knox crap on it. Solution is to go custom Rom, I installed pacrom on my friends mega and all is working again.
We must boycott Samsung as they are taking the apple route.
Sent from my GT-I9205 using Tapatalk

Related

[Q] Device Status: Official

I have rooted and installed a custom rom on my GS4 and it still says official. Is this normal?
I expected that after bricking and flashing stock and rerooting and everything I must have tripped the flash counter.
I don't really care as I don't plan on needing the warranty, I'm just surprised. I even previously had the custom unlock boot screen before bricking the phone.
Am I just looking in the wrong place?
DanGerousDroid said:
I have rooted and installed a custom rom on my GS4 and it still says official. Is this normal?
I expected that after bricking and flashing stock and rerooting and everything I must have tripped the flash counter.
I don't really care as I don't plan on needing the warranty, I'm just surprised. I even previously had the custom unlock boot screen before bricking the phone.
Am I just looking in the wrong place?
Click to expand...
Click to collapse
Flash counter will only register non Samsung images which we cannot flash successfully with a locked boot loader. Unless you are unlucky enough to accidently use Odin to install cwm or push a rom, them a factory restore via Odin should for all intents be undetectable as previously rooted. There might be something on a hidden partition I am unaware of but I have heard nothing yet.
Sent from my Galaxy S4

[Q] Need help ASAP

Hi all,
I need help badly. I recently bought a Samsung galaxy s4, rooted it on the mj7 build, there was an ota mk2 I did. After I was done updating root was broken. I am sending the phone back and needed to remove root and the custom boot logo. I did a factory reset on the device, I downloaded Odin and tried numerous m5 files to flash back to stock. It keeps failing. Now the phone won't boot normally. Someone please help
chudze said:
Hi all,
I need help badly. I recently bought a Samsung galaxy s4, rooted it on the mj7 build, there was an ota mk2 I did. After I was done updating root was broken. I am sending the phone back and needed to remove root and the custom boot logo. I did a factory reset on the device, I downloaded Odin and tried numerous m5 files to flash back to stock. It keeps failing. Now the phone won't boot normally. Someone please help
Click to expand...
Click to collapse
If you're going to return the phone, flash the emergency recovery MJ7 ROM in the Android Development thread.
Hopefully you didn't trip the Knox Warranty Void flag with your serial flashing.
k1mu said:
If you're going to return the phone, flash the emergency recovery MJ7 ROM in the Android Development thread.
Hopefully you didn't trip the Knox Warranty Void flag with your serial flashing.
Click to expand...
Click to collapse
Hi, thanks for replying. I was able to successfully restore to mk2, I don't see the boot screen that says Samsung custom, and I don't see supersu either. I don't know what knox is, and how would I check to see if something happened to that?
chudze said:
Hi, thanks for replying. I was able to successfully restore to mk2, I don't see the boot screen that says Samsung custom, and I don't see supersu either. I don't know what knox is, and how would I check to see if something happened to that?
Click to expand...
Click to collapse
Boot your phone into bootloader mode and read the REALLY TINY text. One line will read "Knox Warranty Void" and either 0x0 (warranty OK) or 0x1 (warranty void).
Get into bootloader mode by powering off, then holding volume down, home, then power. Release when the phone vibrates.
k1mu said:
Boot your phone into bootloader mode and read the REALLY TINY text. One line will read "Knox Warranty Void" and either 0x0 (warranty OK) or 0x1 (warranty void).
Get into bootloader mode by powering off, then holding volume down, home, then power. Release when the phone vibrates.
Click to expand...
Click to collapse
OK, I followed your instructions and it says 0x0, so everything should be OK. Thank you

SGH-M819N (Metro PCS) Mega update via Kies

I'm seeing an available firmware upgrade via kies (MK7).
I'm a little skeptical to try it. Has anyone else upgraded to this firmware?
If so, have you been able to root your mega and install a custom recovery after the upgrade?
I don't want to install this firmware upgrade only to find out that afterwards that knox is on it and prevents me from rooting the phone or unlocking the bootloader.
By the way, I tried downloading the firmware without my phone connected but kies keeps force closing on me before the download is complete.
I'm afraid to connect my phone and try the download because I think it will automatically install the upgrade which I don't want to do until I'm sure I can re-root it and re-install TWRP.
Sent from my SGH-M819N using xda app-developers app
Installed Update, Re-rooted, re-installed TWRP
curgervending said:
I'm seeing an available firmware upgrade via kies (MK7).
I'm a little skeptical to try it. Has anyone else upgraded to this firmware?
If so, have you been able to root your mega and install a custom recovery after the upgrade?
I don't want to install this firmware upgrade only to find out that afterwards that knox is on it and prevents me from rooting the phone or unlocking the bootloader.
By the way, I tried downloading the firmware without my phone connected but kies keeps force closing on me before the download is complete.
I'm afraid to connect my phone and try the download because I think it will automatically install the upgrade which I don't want to do until I'm sure I can re-root it and re-install TWRP.
Sent from my SGH-M819N using xda app-developers app
Click to expand...
Click to collapse
I bit the bullet and gave it a shot. I am happy to report that the firmware upgrade was successful using Kies, I was able to root the device via the Kingo Root app, and was able to re-install TWRP. I am now on firmware M819NUVUAMK7. It is still Android version 4.2.2, and the baseband is also M819NUVUAMK7. The kernel version is dated Fri Nov 22, 2013
I installed superSU and when I ran it, it asked me if I wanted to disable knox (YES OR NO). OF COURSE I DISABLED KNOX!!
I afterward performed a nandroid backup in TWRP (the first order of business).
I am more comfortable now deleting, freezing, uninstalling system apps now because (in the event of a softbrick or bootloop) I can always revert to my nandroid backup or in extreme cases, restart all over again by re-installing the firmware via Kies, re-rooting the device via the kingo root app, and reinstalling TWRP via ODIN.
Not sure what changed from the original firmware (no change log). In any event, the device is snappy and I'm not experiencing any lags.
curgervending said:
I bit the bullet and gave it a shot. I am happy to report that the firmware upgrade was successful using Kies, I was able to root the device via the Kingo Root app, and was able to re-install TWRP. I am now on firmware M819NUVUAMK7. It is still Android version 4.2.2, and the baseband is also M819NUVUAMK7. The kernel version is dated Fri Nov 22, 2013
I installed superSU and when I ran it, it asked me if I wanted to disable knox (YES OR NO). OF COURSE I DISABLED KNOX!!
I afterward performed a nandroid backup in TWRP (the first order of business).
I am more comfortable now deleting, freezing, uninstalling system apps now because (in the event of a softbrick or bootloop) I can always revert to my nandroid backup or in extreme cases, restart all over again by re-installing the firmware via Kies, re-rooting the device via the kingo root app, and reinstalling TWRP via ODIN.
Not sure what changed from the original firmware (no change log). In any event, the device is snappy and I'm not experiencing any lags.
Click to expand...
Click to collapse
never mind I got it. I had a brain fart and was doing the process back words. I put it in download mode for the root.
hotspot mod
I am rooted with stock rom just looking for a hotspot mod for my sgh m819n been searching and searching
reesemtk60 said:
I am rooted with stock rom just looking for a hotspot mod for my sgh m819n been searching and searching
Click to expand...
Click to collapse
as far as i know. there isn't a mod for Metro's phone. there are a few custom ROM's you can use that have free tethering built in. This one is the closest to stock. http://forum.xda-developers.com/showthread.php?t=2608110
It works fine on my M819N :good:
Deodex or odex
thanks one more question how can i tell if my phone is deodex or odex
reesemtk60 said:
thanks one more question how can i tell if my phone is deodex or odex
Click to expand...
Click to collapse
well easiest way is. if its your stock ROM that came with the phone when you bought it. it is odex.
if you are rooted, you can use root explorer to go into your system/app file and see if it shows odex settings for apps
I did and had no problem rooting with kingo. What I cannot find is a way around sim lock without going through metro and that sucks.
curgervending said:
I'm seeing an available firmware upgrade via kies (MK7).
I'm a little skeptical to try it. Has anyone else upgraded to this firmware?
If so, have you been able to root your mega and install a custom recovery after the upgrade?
I don't want to install this firmware upgrade only to find out that afterwards that knox is on it and prevents me from rooting the phone or unlocking the bootloader.
By the way, I tried downloading the firmware without my phone connected but kies keeps force closing on me before the download is complete.
I'm afraid to connect my phone and try the download because I think it will automatically install the upgrade which I don't want to do until I'm sure I can re-root it and re-install TWRP.
Sent from my SGH-M819N using xda app-developers app
Click to expand...
Click to collapse
bnb25 said:
as far as i know. there isn't a mod for Metro's phone. there are a few custom ROM's you can use that have free tethering built in. This one is the closest to stock. http://forum.xda-developers.com/showthread.php?t=2608110
It works fine on my M819N :good:
Click to expand...
Click to collapse
is that rom odex of deodex because my is odex
reesemtk60 said:
is that rom odex of deodex because my is odex
Click to expand...
Click to collapse
deodex
curgervending said:
I bit the bullet and gave it a shot. I am happy to report that the firmware upgrade was successful using Kies, I was able to root the device via the Kingo Root app, and was able to re-install TWRP. I am now on firmware M819NUVUAMK7. It is still Android version 4.2.2, and the baseband is also M819NUVUAMK7. The kernel version is dated Fri Nov 22, 2013
I installed superSU and when I ran it, it asked me if I wanted to disable knox (YES OR NO). OF COURSE I DISABLED KNOX!!
I afterward performed a nandroid backup in TWRP (the first order of business).
I am more comfortable now deleting, freezing, uninstalling system apps now because (in the event of a softbrick or bootloop) I can always revert to my nandroid backup or in extreme cases, restart all over again by re-installing the firmware via Kies, re-rooting the device via the kingo root app, and reinstalling TWRP via ODIN.
Not sure what changed from the original firmware (no change log). In any event, the device is snappy and I'm not experiencing any lags.
Click to expand...
Click to collapse
Almost had a heart attack from this upgrade. My phone was already rooted when I applied the update from Kies. Everything went through fine except when it restarted, I couldn't turn on Wifi at all and I was getting an E in the cell signal. I managed to download the TWRP tar file and Kingo app to root again. I was able to restore my previous backed up image and everything was when I last left it! WHEW!
That's strange. I had no problem. wifi worked and I haven't seen E at all (only 4g lte or 4g). My signal appears to be stronger and more stable with this update than with the original firmware (most of the time I have full bars). As mentioned I don't know what changes were made (no change log around) but this is my observation so far.
Sent from my SGH-M819N using xda app-developers app
Can somebody running MK7 please boot into download mode quickly to check whether this update has a new Knox bootloader?
(Vol - , Home, Power)
Need to know if the following strings are present or not:
KNOX KERNEL LOCK:
KNOX WARRANTY VOID:
BOOTLOADER RP SWREV:
Thanks in advance.
[QUOT1.0razykipa;50763526]Can somebody running MK7 please boot into download mode quickly to check whether this update has a new Knox bootloader?
(Vol - , Home, Power)
Need to know if the following strings are present or not:
KNOX KERNEL LOCK:
KNOX WARRANTY VOID:
BOOTLOADER RP SWREV:
Thanks in advance.[/QUOTE]
This string is present on my phone in download mode:
BOOTLOADER RP SWREV: 3
I have no lines displaying anything about KNOX.
In titanium backup I froze knox 1.0, knox notification manager 1.0, and knox store 1.0.
So it appears that knox is in the rom somewhere but it's had no impact on me. I'm rooted, have twrp installed and have flashed multiple custom roms on my device (both tw and aosp based roms).
Perfect, thanks! Glad you guys got spared from the horrid new Knox bootloaders. There's a small chance that the M819 can be downgraded to the older bootloader to remove Knox entirely, but if the update came with the newest bootloader (I got stuck with it on my i527M) there is no hope at all of downgrading.
Thanks to whoever posted this and the creator of this rom
bnb25 said:
as far as i know. there isn't a mod for Metro's phone. there are a few custom ROM's you can use that have free tethering built in. This one is the closest to stock. http://forum.xda-developers.com/showthread.php?t=2608110
It works fine on my M819N :good:
Click to expand...
Click to collapse
I have the sgh-m819n metro pcs model running the mk7 firmware. This was the only rom that worked 100% for me. Im running twrp recovery,super user and free hotspot. Not to mention all the extra cool apps that it comes with. Big props to the developers of this software may your days be blessed with many more hacks.
Must be unrooted to perform update thru kies without errors..
Galaxy Mega 6.3 On Liquidsmooth rom posted this
question to everyone....
ok not sure if am in the right area to post this but. I have a metro galaxy mega 6.3 (sgh m819n) successfully rooted with kingo. what im trying to find is how to put a custom recovery like twrp and how to do it like step by step. help would be greatly appreciated. or to point me in the right direction. thanks guys.
http://forum.xda-developers.com/showthread.php?t=2608110 this is a great rom for our mega(metropcs) imho. now in order to install CWM or TWRP you simply need to download the version thats for meliusltexx which is for the i9205 version of the mega.. These Roms and procedures are compatable with the M819n(metropcs) mega
thanksss
[email protected] said:
http://forum.xda-developers.com/showthread.php?t=2608110 this is a great rom for our mega(metropcs) imho. now in order to install CWM or TWRP you simply need to download the version thats for meliusltexx which is for the i9205 version of the mega.. These Roms and procedures are compatable with the M819n(metropcs) mega
Click to expand...
Click to collapse
ok thanks and this will work correct.... also before I add a new rom on the m819n I have another question... I used to get 4LTE every where and now I get only 4G or edge after rooting with stock rom. signal apps dont do crap. is there a way to fix this... I miss my LTE data speeds. if you know how to fix or anything please point me in the right direction thanks.

[Q] Problems after installing android 4.3 on S3

Hey guys,
Could someone please help me with my problem. I'll try to be as clear as possible.
I had my fully working, factory unlocked from Three carrier GT-I9300 with 4.1.2 version, however yesterday I decided to updated my phones firmware via Odin 3.07 to 4.3 I9300XXUGML3. Everything went smoothly but after a while i noticed that it does not have any reception.
In phones status it shows:
Network: Unknown
Service state: Out of Service
My Phone Number: Unknown
IMEI: 00499901640000
Device status: Official
I figured it out that culprit might be IMEI code, so I reinstalled 4.3 version a few times but without success. After that I rooted my phone with Kingo Android root in order to fix my reception problem but It did not work out. In the end I thought to just send it to Samsung's warranty.However before sending phone I wanted to run TriangleAway in order to reset my binary count, but It does not resets. I thought that Knox might be stopping it from resetting as it's 4.3, however phone does not have Knox installed in it, even when in Download mode there is nothing written about Knox.
So I'm now in a pickle as I have:
-Corrupted IMEI
-No Reception
-TriangleAway does not resets binary
-Knox nowhere to be found (But I guess it's a good thing)
It would be really good to at least to reset binary count in order to send it to warranty to just forget about this mess :laugh:
Any ideas what is going on? I could not find any solution or problem which is similar to mine.
Triangle away won't work on later bootloader, downgrade to ICS bootloader.
boomboomer said:
Triangle away won't work on later bootloader, downgrade to ICS bootloader.
Click to expand...
Click to collapse
Isn't there a high chance of bricking phone while downgrading from 4.3 to ICS?
I tried now to flash my phone with stock I9300XXUGMK6 firmware in order to root it with CF-Auto-Root and then use Triangle Away to reset my binary counter. However It did not reset it.
Before that tried CWM, flashed kernel, flashed modem, used mobile odin. Sadly everything was in vain. I'm at loss now, don't know what do to. Maybe i'm doing something wrong? Maybe there is some kind of problem with the phone?
Eskis said:
Isn't there a high chance of bricking phone while downgrading from 4.3 to ICS?
I tried now to flash my phone with stock I9300XXUGMK6 firmware in order to root it with CF-Auto-Root and then use Triangle Away to reset my binary counter. However It did not reset it.
Before that tried CWM, flashed kernel, flashed modem, used mobile odin. Sadly everything was in vain. I'm at loss now, don't know what do to. Maybe i'm doing something wrong? Maybe there is some kind of problem with the phone?
Click to expand...
Click to collapse
Just the bootloader
Method 2 easiest
http://forum.xda-developers.com/galaxy-s3/general/how-to-flash-to-bootloader-updated-t2083860
Sent from my GT-I9300 using Tapatalk
Fixed
So I fixed it!
I had Mk6 firmware installed with cf-auto root.
After that I installed Boeffla's kernel (beta5 version) with mobile Odin and used TriangleAway 3.26 in order to reset my binary counter. Immediately after using mobile Odin again I installed official mk6 firmware and voila! Everything official and binary count set to 0, however I still had problem with IMEI and network so I sent phone to samsung as I have warranty.
Thanks everyone for helping out

Samsung S4 AT&T "Custom" boot message.Is bootloader unlocked?

I recently swapped my iPhone 5c to a guy with a Samsung S4 AT&T.I am aware that these carriers are locking their bootloaders.Everytime I restart or turn on my phone normally,there is a "Samsung Custom" message on the boot screen with an unlocked padlock on it.Most of the time it shows up,and in rare random moments in goes away with the normal Samsung S4 boot screen.What does this mean? Did the guy unlocked the bootloader? or flashed another firmware? or is it because Knox was tripped off due to rooting,And I can see that the phone is actually rooted because there's the SuperSU app.I am asking on how I can indentify if my phone's bootloader is actually unlocked.Because I dont have access to my own PC,so it means I cant operate adb.Are there any direct methods? I also checked if he installed a custom recovery,and there's none,just the default one.
Most likely it's from just rooting it. The bootloader hasn't been unlockable on those since 4.2.2, build number ending in MDK (I think). Not many were kept on that update. It's possible to update the rest of the system and firmware on that older bootloader, but since it doesn't have a custom recovery already, that seems unlikely.
es0tericcha0s said:
Most likely it's from just rooting it. The bootloader hasn't been unlockable on those since 4.2.2, build number ending in MDK (I think). Not many were kept on that update. It's possible to update the rest of the system and firmware on that older bootloader, but since it doesn't have a custom recovery already, that seems unlikely.
Click to expand...
Click to collapse
Thanks for the reply! I am sending my phone to a local tech guy to unlock my bootloader.He only charged me $6 and it is pretty cheap.

Categories

Resources