I just noticed (may have been on going for a while) that my wifi is not connecting..... The toggle is light green and in settings the "on" is grayed out. Screenshots attached....
I've restarted a number of times and pulled battery a few times, as well.
I deleted some allshare files with TB.... Could that be the issue?
Any ideas on a fix?
Rooted MJ7.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SCH-I545 using Tapatalk
redwings73 said:
I just noticed (may have been on going for a while) that my wifi is not connecting..... The toggle is light green and in settings the "on" is grayed out. Screenshots attached....
I've restarted a number of times and pulled battery a few times, as well.
I deleted some allshare files with TB.... Could that be the issue?
Any ideas on a fix?
Rooted MJ7.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I recommend deleting that wifi connection and re-add it.
Do you have ssid broadcast turned off or Mac address filtering on the router?
Sent from my SCH-I545 using xda app-developers app
Nothing I've tried has worked....Warranty replacement is on the way.
Thanks for the help attempt!
Mightycaptain said:
I recommend deleting that wifi connection and re-add it.
Do you have ssid broadcast turned off or Mac address filtering on the router?
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
redwings73 said:
Nothing I've tried has worked....Warranty replacement is on the way.
Thanks for the help attempt!
Click to expand...
Click to collapse
I know what the issue is, but seeing as your getting a replacement it doesn't matter. Im willing to bet you were not using the stock modem, apnhlos, or boot.img or atleast modified in atleast some way correct? he most likely culprit is a mismatch of kernel version to kernel module/lib/hook. One of those three had a module/lib/hook that was probably from a recent build, probably Ml1 because it was somewhat compatible with wifi.
Surge1223 said:
I know what the issue is, but seeing as your getting a replacement it doesn't matter. Im willing to bet you were not using the stock modem, apnhlos, or boot.img or atleast modified in atleast some way correct? he most likely culprit is a mismatch of kernel version to kernel module/lib/hook. One of those three had a module/lib/hook that was probably from a recent build, probably Ml1 because it was somewhat compatible with wifi.
Click to expand...
Click to collapse
I´m facing exactly the same issue. Installed prerooted MJ7, flashed MJ7 baseband then via Odin as Phone. Restart and went into settings and saw that MJ7 baseband was applied correctly. But WiFi didn´t work properly, had to add my network again. I then flashed WiFi fix MJ7 via Odin as phone, too - but after another reboot it´s the same again... Any idea what to do to get my WiFi again to work?
kischde said:
I´m facing exactly the same issue. Installed prerooted MJ7, flashed MJ7 baseband then via Odin as Phone. Restart and went into settings and saw that MJ7 baseband was applied correctly. But WiFi didn´t work properly, had to add my network again. I then flashed WiFi fix MJ7 via Odin as phone, too - but after another reboot it´s the same again... Any idea what to do to get my WiFi again to work?
Click to expand...
Click to collapse
What wifi fix are you referring to? What kernel are you using?
Surge1223 said:
What wifi fix are you referring to? What kernel are you using?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=42798412
That's the posting where it can be found. Just seen you've got to scroll upwards to second post. Something went wrong with copying the link I guess...
And this is the link to the file itself:
http://d-h.st/lVI
Gesendet von meinem GT-I9505 mit Tapatalk
kischde said:
http://forum.xda-developers.com/showthread.php?p=42798412
That's the posting where it can be found. Just seen you've got to scroll upwards to second post. Something went wrong with copying the link I guess...
And this is the link to the file itself:
http://d-h.st/lVI
Gesendet von meinem GT-I9505 mit Tapatalk
Click to expand...
Click to collapse
Thats not for our device, go to my modem thread and flash the nonhlos and modem package for mj7 in recovery. If needed I can make you an odin tar instead. Then you should be good.
Edit: I just noticed don't have the 1545 VRUEMJ7...you have the international s4, my file wont work then. Im not familaiar with the 19505...
Sent from my SCH-I535 using xda app-developers app
Surge1223 said:
Thats not for our device, go to my modem thread and flash the nonhlos and modem package for mj7 in recovery. If needed I can make you an odin tar instead. Then you should be good.
Edit: I just noticed don't have the 1545 VRUEMJ7...you have the international s4, my file wont work then. Im not familaiar with the 19505...
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Oh my.. I´m really sorry but it seems as I came into Verizon model´s thread by accident. Hadn´t had a closer look when I saw another guy with the same problem, just searched for "MJ7 and WiFi". I wasn´t aware that your files could be named the same way as ours over in I9505 area.
But anyways thanks a lot for trying to help!!
Related
Dos anybody know what this is at the picture? Its only there at the Boot and only as long as the Samsung Galaxy S3 icon like in the picture is there.thx
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Same here
Sent from my GT-I9300 using xda app-developers app
Probably just means your phone is restarting
Sent from my GT-I9300 using xda premium
It's some kind of custom firmware counter, I think this happens on some of the latest SIII.
Sent from my GT-I9300 using Tapatalk 2
Thats possible because i get a New one due to a crack in the frame. On My old s3 i dont get this sign. I hope this sign disappear when i flash a original Firmware.
Gesendet von meinem GT-I9300 mit Tapatalk 2
I also have a red mark like that after rooting LK1
Must be something of an answer by Samsung for Triangle Away!
Go through this link http://forum.xda-developers.com/showthread.php?t=1918667
This will solve the issue
Sent from my GT-I9300 with a BIG
Mine just came back from repair ("sudden death syndrome") with a new mainboard and totally stock firmware, showing this red thingy, so it's got nothing to do with being rooted. I'd say it's a 'feature' of newer boards.
UncleBeer said:
Mine just came back from repair ("sudden death syndrome") with a new mainboard and totally stock firmware, showing this red thingy, so it's got nothing to do with being rooted. I'd say it's a 'feature' of newer boards.
Click to expand...
Click to collapse
This could be great info in order to make everybody calm (I mean if I have this then I will never experience the sudden death syndrome, because of newer motherboard).
But, on the other hand, the above mentioned thread has ways to remove it and mentioning that this is due to rooting (flash counter >=1 creates this sign)
Was your phone completely stock when it died ?
(btw I have the same mark on my boot screen)
STELIOSFAN said:
Was your phone completely stock when it died ?
Click to expand...
Click to collapse
Nope; rooted and running Wanam's J5. But since the entire motherboard was replaced, what could possibly remain in the phone to indicate that it had been rooted? The phone's essentially just a mainboard, battery and screen.
UncleBeer said:
Nope; rooted and running Wanam's J5. But since the entire motherboard was replaced, what could possibly remain in the phone to indicate that it had been rooted? The phone's essentially just a mainboard, battery and screen.
Click to expand...
Click to collapse
Maybe something in the motherboard drivers (bootlaoder, perhaps)?
Just guessing...
msri3here said:
Maybe something in the motherboard drivers (bootlaoder, perhaps)?
Click to expand...
Click to collapse
But . . . they're on the motherboard, right? Which was entirely replaced.
UncleBeer said:
But . . . they're on the motherboard, right? Which was entirely replaced.
Click to expand...
Click to collapse
I was reading this other thread and people faced this issue after the bootloader got updated (through OTA updates).
It seems that they flashe the old bootloader and the red line is gone!!
So, it looks pretty much like an OTA update issue (JB mostly)
jaidev.s said:
Go through this link http://forum.xda-developers.com/showthread.php?t=1918667
This will solve the issue
Sent from my GT-I9300 with a BIG
Click to expand...
Click to collapse
____________________
thanks fir this! now i know why there is a red mark on the top left of my screen
during boot up. i got it after rooting and flashing custom ROM on my I9300.
Also getting this after flashing a custom rom on an SGS3 that suddenly died and was replaced.. I'd say it's just another form of 'flash counter'
Anyone know how to remove it? Triangle away doesn't work
Sent from my GT-I9305 using xda app-developers app
prot- said:
Anyone know how to remove it? Triangle away doesn't work
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
For i9300, you need to flash back and old bootloader.. On i9305 dont know..
erto90 said:
For i9300, you need to flash back and old bootloader.. On i9305 dont know..
Click to expand...
Click to collapse
not true. TA works if you follow the instructions
Yep is because of the new Bootloader. I updated it on purpose a few weeks ago, flashed a stock firmware and recovery, rerooted the phone and installed a new recovery...this exclamation mark came up...nothing to worry about..
There is one way to solve that issue
It works for me every time
The red ! appeared if you used custom rom or kernel or recovery
So what you have to do is that flash only stock firmware, kernel and recovery
Then use triangle away to reset counter
After resetting flash counters with TA, the red ! will never appear as long as you use stock firmware, kernel and recovery
Sent from my GT-I9300 using xda premium
http://forum.xda-developers.com/showthread.php?t=2282892
all support will be discussed in this thread.. i originally made this for the t-mobile variant. ATT users were able to push the files of the fix into their phone because they didnt have a custom recovery, and it worked..
It is now confirmed that an ATT user now with a custom recovery has flashed this fix and it is now confirmed working.
I now present this to you guys. Would love to see you guys with wallet working using verizon. feel free to test this, but i STRONGLY reccomend you making a backup, or having a rom saved on your sd card that you can revert to in case any errors come about. Im almost sure this will work successfully if the instructions are followed correctly.
thanks and if you have any questions, ask in my original wallet thread.
joemagistro said:
http://forum.xda-developers.com/showthread.php?t=2282892
all support will be discussed in this thread.. i originally made this for the t-mobile variant. ATT users were able to push the files of the fix into their phone because they didnt have a custom recovery, and it worked..
It is now confirmed that an ATT user now with a custom recovery has flashed this fix and it is now confirmed working.
I now present this to you guys. Would love to see you guys with wallet working using verizon. feel free to test this, but i STRONGLY reccomend you making a backup, or having a rom saved on your sd card that you can revert to in case any errors come about. Im almost sure this will work successfully if the instructions are followed correctly.
thanks and if you have any questions, ask in my original wallet thread.
Click to expand...
Click to collapse
Thank you!
theidoctor said:
Thank you!
Click to expand...
Click to collapse
if youre up to giving it a go, ide appreciate your feedback.. again, the last comment in that thread was from an ATT user with a custom recovery, and he said its working like a charm.
joemagistro said:
if youre up to giving it a go, ide appreciate your feedback.. again, the last comment in that thread was from an ATT user with a custom recovery, and he said its working like a charm.
Click to expand...
Click to collapse
I was able to get it installed, card set back up in Wallet, Xposed installed, etc. without any problems. Rolled back the build.prop changes after getting it all configured and Wallet is still opening up fine. Won't be able to test it at a store until tomorrow.
budwizer said:
I was able to get it installed, card set back up in Wallet, Xposed installed, etc. without any problems. Rolled back the build.prop changes after getting it all configured and Wallet is still opening up fine. Won't be able to test it at a store until tomorrow.
Click to expand...
Click to collapse
great news!!
It says this is for only DEODEX ROMS, so if we are running the stock MDK ROM (rooted and unlocked) then it won't work?
FAUguy said:
It says this is for only DEODEX ROMS, so if we are running the stock MDK ROM (rooted and unlocked) then it won't work?
Click to expand...
Click to collapse
That would be correct.
FAUguy said:
It says this is for only DEODEX ROMS, so if we are running the stock MDK ROM (rooted and unlocked) then it won't work?
Click to expand...
Click to collapse
yes thats correct
joemagistro said:
great news!!
Click to expand...
Click to collapse
Just used it at the local BP. Working fine so far. Thanks a TON for this!
budwizer said:
Just used it at the local BP. Working fine so far. Thanks a TON for this!
Click to expand...
Click to collapse
hell yes!!
Okay, so to recap. After rooting, I'll have to flash custom recovery, install deodexed rom, then try to install wallet as that thread states?
Sent from my SCH-I545 using Tapatalk 4 Beta
dseda86 said:
Okay, so to recap. After rooting, I'll have to flash custom recovery, install deodexed rom, then try to install wallet as that thread states?
Sent from my SCH-I545 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Correct
Sent from my SCH-I545 using Tapatalk 4 Beta
Disregard
Darn, I was hoping to be able to keep the stock rom.
Sent from my SCH-I545 using Tapatalk 4 Beta
Thanks for the work!!
Ok, so I used root explorer to change the .prop lines then booted into recovery (twrp) and flashed the file listed and that went well.
Now, what permissions do I have to "fix" and how do I do that? I wasn't promoted nor saw an option to do this in TWRP recovery.
I rebooted and installed the wallet app from the play store, opened it, and now it seems to be stuck on "Setting up Wallet, this may take up to 5 minutes" and nothing happens.
What did I do wrong and how do I proceed?
Thanks in advance.
Wot-75 said:
Thanks for the work!!
Ok, so I used root explorer to change the .prop lines then booted into recovery (twrp) and flashed the file listed and that went well.
Now, what permissions do I have to "fix" and how do I do that? I wasn't promoted nor saw an option to do this in TWRP recovery.
I rebooted and installed the wallet app from the play store, opened it, and now it seems to be stuck on "Setting up Wallet, this may take up to 5 minutes" and nothing happens.
What did I do wrong and how do I proceed?
Thanks in advance.
Click to expand...
Click to collapse
glad to of got it working!
for anyone else with this issue, FIX PERMISSIONS is under advanced in TWRP..
Crap... does anyone have the original Verizon build.prop lines handy? I didn't read ahead to see that Im supposed to change it back to the default as the last step.
Thanks...
Wot-75 said:
Crap... does anyone have the original Verizon build.prop lines handy? I didn't read ahead to see that Im supposed to change it back to the default as the last step.
Thanks...
Click to expand...
Click to collapse
Here you go:
Code:
ro.product.model=SCH-I545
ro.product.name=jfltevzw
ro.product.device=jfltevzw
Wot-75 said:
Crap... does anyone have the original Verizon build.prop lines handy? I didn't read ahead to see that Im supposed to change it back to the default as the last step.
Thanks...
Click to expand...
Click to collapse
If you used root explorer it backed it up for you. Otherwise use the attached.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SCH-I545 using Tapatalk 4 Beta
jmart518 said:
Here you go:
Code:
ro.product.model=SCH-I545
ro.product.name=jfltevzw
ro.product.device=jfltevzw
Click to expand...
Click to collapse
Thanks!
I'm hoping to find hotspot mod for note 3 on kit kat stock rom.
Sent from my SM-N900P using Tapatalk
shadricksimms said:
I'm hoping to find hotspot mod for note 3 on kit kat stock rom.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
Here: droidforums.net/forum/android-news/255802-free-wifi-tether-galaxy-note-3-using-native-tether-app-no-root-no-hacks.html
Leave links plz
Sent from my SM-N900P using Tapatalk
DarkGrey said:
Here: droidforums.net/forum/android-news/255802-free-wifi-tether-galaxy-note-3-using-native-tether-app-no-root-no-hacks.html
Click to expand...
Click to collapse
This one is for Verizon tried it on our phone and does not work.
JSnively said:
This one is for Verizon tried it on our phone and does not work.
Click to expand...
Click to collapse
Try this way than:
http://www.youtube.com/watch?v=wLSWPaZI3rg
DarkGrey said:
Try this way than:
http://www.youtube.com/watch?v=wLSWPaZI3rg
Click to expand...
Click to collapse
That one will work if you are rooted not sure if OP is rooted sounded like he is not.
I'm going to try this right now..This is my setup on my note3
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N900P using Tapatalk
Like I said I'm on kit kat
Sent from my SM-N900P using Tapatalk
This only puts your phone in a bootloop and have to take steps to fix your phone. If on kit kat update wait for new mods
Sent from my SM-N900P using Tapatalk
This is to show I am rooted as well I know what I'm talking about.you don't cause your not on kit kat
Sent from my SM-N900P using Tapatalk
JSnively said:
That one will work if you are rooted not sure if OP is rooted sounded like he is not.
Click to expand...
Click to collapse
Yes he's rooted, he's been messaging me about his issue. Still can't find a fix.
Wireless tethering for root users should work, but off the top of my head I don't remember the settings.
I always had luck with beta 2 of the app: https://code.google.com/p/android-w...tail?name=wifi_tether_v3_2-beta2.apk&can=2&q=
Check routing fix
Leave network open.
DarkGrey said:
Yes he's rooted, he's been messaging me about his issue. Still can't find a fix.
Wireless tethering for root users should work, but off the top of my head I don't remember the settings.
I always had luck with beta 2 of the app: https://code.google.com/p/android-w...tail?name=wifi_tether_v3_2-beta2.apk&can=2&q=
Check routing fix
Leave network open.
Click to expand...
Click to collapse
Well I'm in the same boat as him. I've tried what you told me to use and it doesn't work with either of the settings. I used hotspot so much before with 4.3.
I tried the Beta 2 with NAB and it doesn't work this time around...
DarkGrey said:
Yes he's rooted, he's been messaging me about his issue. Still can't find a fix.
Wireless tethering for root users should work, but off the top of my head I don't remember the settings.
I always had luck with beta 2 of the app: https://code.google.com/p/android-w...tail?name=wifi_tether_v3_2-beta2.apk&can=2&q=
Check routing fix
Leave network open.
Click to expand...
Click to collapse
shadricksimms said:
I'm going to try this right now..This is my setup on my note3
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
hmm How are you on KK 4.4.2 and still using MI3 baseband?
slow_one said:
hmm How are you on KK 4.4.2 and still using MI3 baseband?
Click to expand...
Click to collapse
Good catch, lol wow!!!
For my sake I'm correctly on nab running sac's kk rom. 4.4.2
Nickitt said:
Good catch, lol wow!!!
For my sake I'm correctly on nab running sac's kk rom. 4.4.2
Click to expand...
Click to collapse
That's the original baseband for when the phone was first released.
But still the thought recurs...let us just post, "it's not working..."
Sent from my SM-N900P using Xparent BlueTapatalk 2
Actually, I did what @rlmiller said to do, was simple and got my wifi tether producing a signal again. You need to do a clean install if flashing the Rom you are on dirty doesn't fix the hotspot.
Rlmiller said:
When I do a CLEAN install...the process is as follows:
in TWRP.....
WIPE>advanced Wipe> selectdalvik cache, system, data, INTERNAL STORAGE, cache then swipe to wipe.... I do this twice
them go back and select FORMAT DATA....type yes and press go.... I do this twice...
then go back to main menu. and select reboot> RECOVERY....wait for recovery to restart.
Now install rom
tried service.jar from MJ4 days and it just made the phone hang...:laugh: Knew that it was gonna happen but what the heck, tried anyway... Guess wait for the updated service.jar..
Just wait for developers to come up with a solution.all old mods do not work on kit kat
Sent from my SM-N900P using Tapatalk
Nickitt said:
Actually, I did what @rlmiller said to do, was simple and got my wifi tether producing a signal again. You need to do a clean install if flashing the Rom you are on dirty doesn't fix the hotspot.
Rlmiller said:
When I do a CLEAN install...the process is as follows:
in TWRP.....
WIPE>advanced Wipe> selectdalvik cache, system, data, INTERNAL STORAGE, cache then swipe to wipe.... I do this twice
them go back and select FORMAT DATA....type yes and press go.... I do this twice...
then go back to main menu. and select reboot> RECOVERY....wait for recovery to restart.
Now install rom
Click to expand...
Click to collapse
Those are rom-specific instructions that are absolutely unnecessary for many on these forums.
I'm glad they worked for you, but there are TouchWiz KitKat roms on the grid now and in the pipeline for this phone where such guidance is both unnecessary and most certainly unwarranted.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Ok. I have now flashed back to JellyBean 4.1.2 on my sim unlocked Rogers note i717r.
I need to root this phone. I was given a link to follow. Seemed easy enough. Installed cwm, then did superuser. No root.
I tried to odin in a pre rooted kernel, it stuck me at Samsung screen.
I have flashed back to the stock 4.1.2. will be doing a factory reset here in moments.
I need to get this rogers phone working on mobilicity. so far the only success I have had was on Gingerbread firmware, but the phone was running so slow on that.
I believe I need to change the modem, but everything hinges on me rooting this damned phone. Nothing I have followed has worked!
Edit: wiped phone completely, got roaming network with my mobilicity sim in....had this before
Edit 2: I have bell, telus and Canadian roaming as my networks in my network operators
Did u update binaries in su settings?... If u have cwm installed try to install the rooted stock ROM or cm10 or cm11. They are prerooted
Sent from my XT894 using Tapatalk
rruleford said:
Did u update binaries in su settings?... If u have cwm installed try to install the rooted stock ROM or cm10 or cm11. They are prerooted
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
I just flashed cm10 over jellybean, and got stuck at the logo loading screen. i wasn't going to try it again. i will be grabbing supersu right now to update the binaries.
i have 4.1.2. and a root, with a blaze modem installed, but i will be trying cm10 again here in a moment after i update the binaries.
edit: i need to find this!
http://forum.xda-developers.com/showpost.php?p=47374316&postcount=8
the stock rom and the twrp
Make sure to format data and cache and system. That's y u got stuck prolly
Sent from my XT894 using Tapatalk
rruleford said:
Make sure to format data and cache and system. That's y u got stuck prolly
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
so, when i go to flash cm10, reformat?
do i just do a wipe and then install? or install then wipe?
Wipe before
Sent from my XT894 using Tapatalk
rruleford said:
Wipe before
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
do i wipe the davlik?
Yes. Dalvik AND cache AND data AND system.
Sent from my XT894 using Tapatalk
i'm in cm10.
it's showing mobilicity as a network operator. i'm currently trying to get it to register on the network, fingers crossed!
edit: didn't allow me to register on mobilicity, but at least i see it, that's something at least!
edit 2: when i try to register on mobil, its telling me my SIM card doesn't allow for a connection to this network.
should i flash another modem instead?
edit 3: i have an H network! i had 3G for like a second, lmao.
unlively said:
i'm in cm10.
it's showing mobilicity as a network operator. i'm currently trying to get it to register on the network, fingers crossed!
edit: didn't allow me to register on mobilicity, but at least i see it, that's something at least!
edit 2: when i try to register on mobil, its telling me my SIM card doesn't allow for a connection to this network.
should i flash another modem instead?
edit 3: i have an H network! i had 3G for like a second, lmao.
Click to expand...
Click to collapse
Do this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my XT894 using Tapatalk
rruleford said:
Do this
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Wasn't allowing me to in cm10
Really don't know what to tell you then. Wish I could help more. Good luck
Sent from my XT894 using Tapatalk
unlively said:
Wasn't allowing me to in cm10
Click to expand...
Click to collapse
That combination doesn't work on some modem. I can't tell you exactly which ones tho'.
Go here and see read up you might find something helpful.
If you google xda for i717 stock roms there's a link here with a bunch of Roms and modems that you can test.
Or basically just flash a de-bloated stock rom and see if your device can be registered on target network. Good luck!
I think I am screwed. What is this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SCH-I605 using Tapatalk
No idea on every you possibly did but was bored at work and nowhere does it recognize your version. Sorry man.
Sent from my SCH-I605 using Tapatalk
Dang. Im screwed
Sent from my SCH-I605 using Tapatalk
Hey just seen this and remembered about you but in case you haven't figured it out here you go. http://www.droid-life.com/2014/05/0...-gets-minor-update-includes-roaming-on-telus/
Sent from my SCH-I605 using Tapatalk
Thanks. Saw that too.
Sent from my SCH-I605 using Tapatalk
Download link???
Quick note to anyone coming from MJ9, this update can remove your root, and the MJ9 saferoot method will not work on it.
Happy updating to those out there!
I've lost root too..does anyone know of a root process for the build? I haven't tried the process listed in the Development section as it doesn't say anything about the VRUAND3 build...
Thanks!!
Saferoot is not working with the new update VRUAND3 so don't waste your time.
Sent from my SCH-I605 using Tapatalk
Latindude001 said:
Saferoot is not working with the new update VRUAND3 so don't waste your time.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Forever or is there plans to include it soon in the next safeboot build?
gee1000 said:
Forever or is there plans to include it soon in the next safeboot build?
Click to expand...
Click to collapse
At the moment we don't know yet. But I was told today that you can go back to 4.1.1 with a great risk of bricking your device.
Sent from my SCH-I605 using Tapatalk
how?
Latindude001 said:
At the moment we don't know yet. But I was told today that you can go back to 4.1.1 with a great risk of bricking your device.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
If you updated to 4.3 you cannot go back to 4.1.1
Also going to 4.1.1 is touchy. If you were to go back you need to go to 4.1.2
Basically if you have the official 4.3 update and beyond you cannot unlock the bootloader or in some instances root.
I am using the Skynote Rc2.5 ROM but I am technically coming from 4.1.2. There is no official 4.2.x update for this version of the Note 2.
bvzxa3 said:
If you updated to 4.3 you cannot go back to 4.1.1
Also going to 4.1.1 is touchy. If you were to go back you need to go to 4.1.2
Basically if you have the official 4.3 update and beyond you cannot unlock the bootloader or in some instances root.
I am using the Skynote Rc2.5 ROM but I am technically coming from 4.1.2. There is no official 4.2.x update for this version of the Note 2.
Click to expand...
Click to collapse
Right, I was asking because the ND3 update doesn't appear to be any different than MJ9 firmware wise except for what I assume are mostly changes in the baseband to accomodate the Telus bands. I would think that safeboot will be updated easily for this minor build but I am not any expert by any means.
I also saw people talking about for the same Telus update for the S3 to just Odin backflash VRUCNC1 4.3 to VRUCML1 4.3 with success (http://forum.xda-developers.com/showthread.php?t=2575661&page=153). Anyone tried that? I might actually try it myself to get root back. I don't this new "update". I think VZ did this more to take away root than add some really necessary Canadian roaming anyway.
gee1000 said:
Right, I was asking because the ND3 update doesn't appear to be any different than MJ9 firmware wise except for what I assume are mostly changes in the baseband to accomodate the Telus bands. I would think that safeboot will be updated easily for this minor build but I am not any expert by any means.
I also saw people talking about for the same Telus update for the S3 to just Odin backflash VRUCNC1 4.3 to VRUCML1 4.3 with success (http://forum.xda-developers.com/showthread.php?t=2575661&page=153). Anyone tried that? I might actually try it myself to get root back. I don't this new "update". I think VZ did this more to take away root than add some really necessary Canadian roaming anyway.
Click to expand...
Click to collapse
Curious to see what your results are if you do try this. I also feel that VZW did this update more to take root away, especially considering that the base band could have been incorporated into the (hopefully) upcoming 4.4 update.
Yup, this annoyed me enough that I finally got an account!
this update was just to steal root. they had already tried using the my verizon app to take it. telus uses gsm and the same lte frequency verizon uses. all vzw note 2's could already "roam" on telus. this was just vzw being f**ktards trying to control us.
Has anyone been able to revert or re root their phone after this?
mwinschel said:
Has anyone been able to revert or re root their phone after this?
Click to expand...
Click to collapse
Other users are reporting that you can Odin back to MJ9 and then root with saferoot. See this thread for details... http://forum.xda-developers.com/showthread.php?p=52792973
Sent from my SCH-I605 using XDA Premium 4 mobile app
I was forced the vruand3 update at about 4 am while I was sleeping. I woke up to no root and some issues tied to the freedom app not being uninstalled. I flashed back to mj9 with odin. I rerooted with saferoot. I was still having the connection issues with everything google related. I took the ota update again to try to fix the issue. The google issue fixed itself after the ota, but my root wasn't taken away this time. So now I'm on build vruand3 and have full root access. Maybe someone can shed some light on this , or it will help someone