After many tries of failure from ROM flashing, reprogramming and trying to understand the alien language to me, I finally figured out how to get wifi tether working for your galaxy note 2. There are links in this thread and make sure that you follow the instruction I have for you here as well.
*** Disclosure ***
I am not an expert or a someone who can give you an advice. Directions hereafter are what worked for me and I am only sharing how I got it worked. However, it is not a definite way to get wifi tether working for T-Mobile Samsung Galaxy Note 2 (SGH-T889). Please do this for US model only.
This direction is for people who have never done rooting and programming phones, and upgraded to JB 4.3 via OTA with KNOX enabled bootloader. By the end of this direction, your GN2 will be rooted on T-Mobile stock ROM with wifi tether enabled. Please be aware that this direction will void your phone's warranty by tripping KNOX counter. So do this at your own will. Also, back up your most recent ROM and personal files just in case.
So, enough disclosure.....and here it is.
(For this part of instruction, I would like to give a big thanks to mrRobinson for providing pre-rooted stock T-Mobile ROM.)
1. Download ODIN (version does not matter, but 3.07 or 3.09 should work fine)
2. Find Tmobile ROM and download JellyBean Release 4.3 (December 2013) from this link http://forum.xda-developers.com/showthread.php?t=1975560
3. Unzip downloaded ROM in your PC and run ODIN (Leave Auto Reboot and F. Reset Time checked in ODIN)
4. Find and click PDA or AP in ODIN and load downloaded ROM (root66_TMO_T889UVUCMK7_2.tar.md5)
5. Turn T889 off, then put the phone to download mode by pressing and holding Volume Down, Home and Power. Then plug USB cable to the phone
6. Click START to flash your phone
Once the phone reboots, your phone will be rooted. Easy so far, right?
Now the next step...
(For this part of instruction, I would like to give a big thanks to mattlowry.)
1. Visit this thread http://forum.xda-developers.com/showthread.php?t=2564430 and download 2 files: Version 2.1 of SWARM ROM (Look for Download(v2.1)) and WifiTethering.zip (Look for a mediafire link on Version 2.1)
2. Copy these files on your phone's SD Card
3. Turn T889 off, then enter into recovery mode by pressing and holding Volume Up, Home and Power. If the recovery mode says Android System Recovery 3e on top and does not have "advanced" menu, reboot your phone and go to Play Store. Download ROM Manager by ClockworkMod. Run Rom Manager and choose Recovery Setup. Under the Recovery Setup, install or update recovery "ClockworkMod Recovery". After this install/update, turn your phone off and enter into recovery mode.
4. In the recovery mode, select "wipe data/factory reset", then select "wipe cache partition", then select "advanced", then select "wipe dalvik cache." Once you are done this far, select "Go Back", then select "install zip." Under install zip menu, select "Choose zip from /storage/sdcard1". (There will be about 15 to 20 second delay until the next menu.) Find the SWARM ROM zip file and flash the phone's ROM.
5. After flashing the phone with SWARM ROM, go back to install zip menu and find WifiTethering.zip, then flash your phone.
A bit painful, but you've done great!...but we are not done yet.
Now, do not panic if your Wifi does not work after this step. There is a fix.
(For this part of instruction, I would like to give a big thanks to dr.ketan.)
1. Visit this link http://forum.xda-developers.com/showthread.php?p=48468121&highlight=mattlowry#post48468121
2. Download "Wifi_patch_t889.tar.rar" and extract the file in your PC.
3. Run ODIN and click on PDA or AP, then load the file "Wifi_patch_t889.tar.md5".
4. Press START and wait until your phone reboot.
Now your Wifi patch is done, but your wifi won't work until you do the following.
(For this part of instruction, I would like to give a big thanks to DerTeufel1980 for Devil Kernel.)
1. Visit this link http://forum.xda-developers.com/showthread.php?t=2239453
2. Very bottom of this thread there are files for download. Download "Devil2-2.3.2-t0lte-DUAL-20140102.zip" and save it in your phone's SD card. Make sure the file name as others will get you stuck in booting. If you download wrong kernel, you have to restart the whole process from the very top of this instruction.
3. Turn your phone off and enter into recovery mode again. Select "install zip", find the "Devil2-2.3.2-t0lte-DUAL-20140102.zip" file, then flash your phone.
4. One the flash is done, reboot your phone.
By now, your phone is rooted with Devil Kernel. All functions should work fine.
Now the wifi tether...
1. Go to Play Store and search wifi tether.
2. From the list of apps, find Wifi Tether: Network Sharing by Topapploft.
3. Do not install this app and look for a link under Description for 10.1.0 version.
4. Download the app from this link and install this app (phone will ask for installation permission for unknown source app.)
5. After the installation, run the app and go to the settings.
Change Device-Profile: Choose Generic ICS/JB (wlan0)
Change Setup-Method: Choose Netd-Ndc (master)
Send Netd Max Client Cmd: checked
Send No Tether-Interface Cmd: checked
WiFi-driver reload 2: checked
MSS clamping: checked by default
Routing fix: checked by default
You are done!
On a side note, do not use wifi tether trevemod. It has same functions as the above app, but for some reason it forcefully reboots your phone and tethering do not work.
Also, do not use Wifi Tether Router as this app will cause blackout of your phone screen on some cases. I purchased this app and regret it.
One more thing, I have not tried skipping SWARM ROM flashing. So if anyone tried, please comment it for other people.
Thanks for reading this long instruction and hope your phone works as mine.
Love the idea.
In the first bit, skip mrRobinson's rom. Start with Odin installing a custom recovery such as TWRP. Then odin the wifi patch if you are not on the Knox bootloader and don't plan on using Devil Kernel or Agni. Then pull a nandroid backup.
Complete wipe.
Install the 4.3 rom of your choice. I like Jedi Master X, wifi tether is already configured of you stick with mobile devices (tablets etc). Follow instructions on install.
If you are on another rom, go ahead and follow your instructions.
Thanks for helping the community.
Hastily spouted for your befuddlement
Coug76 said:
Love the idea.
In the first bit, skip mrRobinson's rom. Start with Odin installing a custom recovery such as TWRP. Then odin the wifi patch if you are not on the Knox bootloader and don't plan on using Devil Kernel or Agni. Then pull a nandroid backup.
Complete wipe.
Install the 4.3 rom of your choice. I like Jedi Master X, wifi tether is already configured of you stick with mobile devices (tablets etc). Follow instructions on install.
If you are on another rom, go ahead and follow your instructions.
Thanks for helping the community.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
Thank you for your input and comment.
You shouldn't need both the WiFi patch and devil kernel for WiFi to work. Its 1 or the other. But nice thread!
Sent from my SGH-T889 using Tapatalk 4
mattlowry said:
You shouldn't need both the WiFi patch and devil kernel for WiFi to work. Its 1 or the other. But nice thread!
Sent from my SGH-T889 using Tapatalk 4
Click to expand...
Click to collapse
Thank you for your input.
I've tried WiFi patch first, but it did not work. So, I had to use devil kernel for both WiFi and tethering to work. I put both instruction just to make sure they work.
I can confirm that just using the patch does not give you wifi back on stock, rooted MK7. However, I much prefer the stock kernel to Devil Kernel in terms of smoothness.
Any idea on how to undo the WifiTethering.zip changes without having to redo the entire phone?
drdoombot said:
I can confirm that just using the patch does not give you wifi back on stock, rooted MK7. However, I much prefer the stock kernel to Devil Kernel in terms of smoothness.
Any idea on how to undo the WifiTethering.zip changes without having to redo the entire phone?
Click to expand...
Click to collapse
Flash your ROM over your present install. Should paint over the tethering changes.
Hastily spouted for your befuddlement
Thanks!!
First I want to thank you for this thread!! Since upgrading to Android 4.3 I have not been successful in getting wifi tethering to work. Prior to 4.3, trev-mod was working perfectly fine but after the update nothing seem to work except bluetooth tethering with Fox-Fi along with PDANet+ and many apps didn't work with that method.
Also I'd just like to add that I hardly ever tether at all... it's just nice to know when you are in a bind you have some sort of solution.
I'm currently on the 4.1.2 bootloader because I didn't want to have to deal with knox. Even though my warranty has already expired, for some reason I still do not want to upgrade to the new one. The wifi patch was giving me all sorts of freezes and random reboots so I decided to go back to the original bootloader, after reading EdKey's Conch Replubic thread. His ROM was very stable for me, however I recently acquired the Gear 2 and unfortunately not all was working correctly since it is heavily debloated. I'm currently using SWARM 2.1 with AGNI Kernel. Was using Devil before but battery drain appears to be very high with this ROM so I'm giving Agni a go for a couple of days. Since I am on the old bootloader, the only way to get wifi to work properly is either using Devil or Agni kernel unless there is another one out there that I'm unaware of at this time.
Anyway... I digress. My experience so far is this, when I initially start the tethering process, none of my devices see an access point until I stop tethering and start it again for a second time. Then I'm able to see the AndroidTether access point. I can connect and tether even without any sort of vpn or browser ID spoofer. I'd still recommend using a VPN anyway, just in case the operator starts packet sniffing. Who knows, maybe Trev Mod was working, I don't recall trying to re-enable tethering for a second time when I didn't see any access points so I just kind of gave up and stumbled across this thread
However, when I stop the tethering, I'm not able to reconnect to my normal home wifi until I toggle on/off the Mobile HotSpot option in the Rom. My wifi icon is enabled, but for some reason does not connect to my router until I toggle it on and then off again. This is still a better work around than having to reboot the phone each time to get my wifi to reconnect. It might have something to do with my current bootloader, but I'm not sure. I guess it will be back to the drawing board after KitKat comes out. Hopefully this will remain working for awhile...
So I just wanted to share my experience and thank you again for this thread.
Just so you know you can install jedi master rom x2. And follow my guide. It's a lot easier than doing all of this. Here's the link. http://zuck.com/xda/JediMasterX-FAQ.html#teather
Sent from my SM-G900T using XDA Premium 4 mobile app
hotspot working on t-mobile galaxy note 2 running 4.3 Jellybean
jinimini1026 said:
After many tries of failure from ROM flashing, reprogramming and trying to understand the alien language to me, I finally figured out how to get wifi tether working for your galaxy note 2. There are links in this thread and make sure that you follow the instruction I have for you here as well.
*** Disclosure ***
I am not an expert or a someone who can give you an advice. Directions hereafter are what worked for me and I am only sharing how I got it worked. However, it is not a definite way to get wifi tether working for T-Mobile Samsung Galaxy Note 2 (SGH-T889). Please do this for US model only.
This direction is for people who have never done rooting and programming phones, and upgraded to JB 4.3 via OTA with KNOX enabled bootloader. By the end of this direction, your GN2 will be rooted on T-Mobile stock ROM with wifi tether enabled. Please be aware that this direction will void your phone's warranty by tripping KNOX counter. So do this at your own will. Also, back up your most recent ROM and personal files just in case.
So, enough disclosure.....and here it is.
thering-menu/
(For this part of instruction, I would like to give a big thanks to mrRobinson for providing pre-rooted stock T-Mobile ROM.)
1. Download ODIN (version does not matter, but 3.07 or 3.09 should work fine)
2. Find Tmobile ROM and download JellyBean Release 4.3 (December 2013) from this link http://forum.xda-developers.com/showthread.php?t=1975560
3. Unzip downloaded ROM in your PC and run ODIN (Leave Auto Reboot and F. Reset Time checked in ODIN)
4. Find and click PDA or AP in ODIN and load downloaded ROM (root66_TMO_T889UVUCMK7_2.tar.md5)
5. Turn T889 off, then put the phone to download mode by pressing and holding Volume Down, Home and Power. Then plug USB cable to the phone
6. Click START to flash your phone
Once the phone reboots, your phone will be rooted. Easy so far, right?
Now the next step...
(For this part of instruction, I would like to give a big thanks to mattlowry.)
1. Visit this thread http://forum.xda-developers.com/showthread.php?t=2564430 and download 2 files: Version 2.1 of SWARM ROM (Look for Download(v2.1)) and WifiTethering.zip (Look for a mediafire link on Version 2.1)
2. Copy these files on your phone's SD Card
3. Turn T889 off, then enter into recovery mode by pressing and holding Volume Up, Home and Power. If the recovery mode says Android System Recovery 3e on top and does not have "advanced" menu, reboot your phone and go to Play Store. Download ROM Manager by ClockworkMod. Run Rom Manager and choose Recovery Setup. Under the Recovery Setup, install or update recovery "ClockworkMod Recovery". After this install/update, turn your phone off and enter into recovery mode.
4. In the recovery mode, select "wipe data/factory reset", then select "wipe cache partition", then select "advanced", then select "wipe dalvik cache." Once you are done this far, select "Go Back", then select "install zip." Under install zip menu, select "Choose zip from /storage/sdcard1". (There will be about 15 to 20 second delay until the next menu.) Find the SWARM ROM zip file and flash the phone's ROM.
5. After flashing the phone with SWARM ROM, go back to install zip menu and find WifiTethering.zip, then flash your phone.
A bit painful, but you've done great!...but we are not done yet.
Now, do not panic if your Wifi does not work after this step. There is a fix.
(For this part of instruction, I would like to give a big thanks to dr.ketan.)
1. Visit this link http://forum.xda-developers.com/showthread.php?p=48468121&highlight=mattlowry#post48468121
2. Download "Wifi_patch_t889.tar.rar" and extract the file in your PC.
3. Run ODIN and click on PDA or AP, then load the file "Wifi_patch_t889.tar.md5".
4. Press START and wait until your phone reboot.
Now your Wifi patch is done, but your wifi won't work until you do the following.
(For this part of instruction, I would like to give a big thanks to DerTeufel1980 for Devil Kernel.)
1. Visit this link http://forum.xda-developers.com/showthread.php?t=2239453
2. Very bottom of this thread there are files for download. Download "Devil2-2.3.2-t0lte-DUAL-20140102.zip" and save it in your phone's SD card. Make sure the file name as others will get you stuck in booting. If you download wrong kernel, you have to restart the whole process from the very top of this instruction.
3. Turn your phone off and enter into recovery mode again. Select "install zip", find the "Devil2-2.3.2-t0lte-DUAL-20140102.zip" file, then flash your phone.
4. One the flash is done, reboot your phone.
By now, your phone is rooted with Devil Kernel. All functions should work fine.
Now the wifi tether...
1. Go to Play Store and search wifi tether.
2. From the list of apps, find Wifi Tether: Network Sharing by Topapploft.
3. Do not install this app and look for a link under Description for 10.1.0 version.
4. Download the app from this link and install this app (phone will ask for installation permission for unknown source app.)
5. After the installation, run the app and go to the settings.
Change Device-Profile: Choose Generic ICS/JB (wlan0)
Change Setup-Method: Choose Netd-Ndc (master)
Send Netd Max Client Cmd: checked
Send No Tether-Interface Cmd: checked
WiFi-driver reload 2: checked
MSS clamping: checked by default
Routing fix: checked by default
You are done!
On a side note, do not use wifi tether trevemod. It has same functions as the above app, but for some reason it forcefully reboots your phone and tethering do not work.
Also, do not use Wifi Tether Router as this app will cause blackout of your phone screen on some cases. I purchased this app and regret it.
One more thing, I have not tried skipping SWARM ROM flashing. So if anyone tried, please comment it for other people.
Thanks for reading this long instruction and hope your phone works as mine.
Click to expand...
Click to collapse
Want to get hotspot working on t-mobile SGH T-889??Follw the link below or just download (hotspot control) from google play/market and enable ACESS POINT.And you can turn hotspot from your phone's setting the normal way,without root and without downloading any other tethering apps.
http://www.androidpolice.com/2013/0...harnesses-the-latent-power-of-your-devices-te
Help samsung galaxy note ii t889 root access
Greetings to the entire community, I'm new here and I wanted to ask for some help on this problem that I have and maybe others have too.
I have a note II t889 which I've rooted, SuperSU appears installed on the phone, when I open any application that requires root it asks me permission, I click accept and it tells me I have been granted permissions, but when I try to use the application tells me that the root has failed, or that need root access to use the application.
Note: I have already tried this several rooting using odin and corresponding files (CF-Root-Auto for note II t889, root66_TMO_T889UVUCMK7_2.tar.md5, and others, and the result is the same, according to the rooteado odin has been done successfully)
Another thing I have android 4.3 version and I already delete knox using root browser (it asked me root access to use it and it worked to remove the data relating to knox)
Thanks
Found solution
Ok anybody outthere doing this it took me a couple of hours but I couldn't find Wi-Fi tether by Topapploft, no longer in the play store, thankfully I found something that worked, first go to play store and get network share & wifi tether by joliejoy, then it's going to ask you to download newest one, wifi tether plus, file name: AndroidWifiTether_10.1.10.apk, follow the instruction above, EXCEPT the device should be GALAXY S4!! It worked for me
My note 2 is unrooted but wifi tether works fine.
Related
PREPARATION STEP! download sgs kernel flasher from the market (must be rooted I believe) and do a kernel backup as this process changes your kernel.
SPRINT TAB INSTRUCTIONS THAT WORKEDFOR MANY SPRINT TAB OWNERS. IT MAY NOT WORK FOR YOU!
Ok here it is, Thank koushs for this product, cruiserbax for his awesome instructions and Benjamin Dobell for giving up Heimdall flashing utility and install instructions.
I NOR THE ANYONE LIST ABOVE ARE RESPONSIBLE FOR THIS NOT WORKING!!! OR ANY DAMAGE IT MAY DO TO YOUR TAB!!
To get the zip file containing the zimage download it from here. http://www.megaupload.com/?d=SV6IKL1D
To flash the zimage you will need to use Heimdall which can be downloaded here. http://www.glassechidna.com.au/products/heimdall/ <--------click on the binaries link for 1.1.1
instruction are below.
Heimdall install instructions
1. Download Heimdall here http://www.glassechidna.com.au/products/heimdall/
2. Download Microsoft Visual C++ 2010 Redistributable Package (x86) and install it. http://www.microsoft.com/downloads/...5E-6DE6-4D3A-A423-37BF0912DB84&displaylang=en <------only if you are using Microsoft widows
2. Unzip Heimdall and you should have several files in the folder called Heimdall.exe, Heimdall-Frontend.exe, QtCore4.dll, QtGui4.dll, Readme.txt and drivers folder containing zadig.exe
3. Put you tab into Download mode(while the tab is OFF hold Volume Down + Power Button). Hook the tab up to you PC and Run Zadig.exe to install the drivers.
4. From the menu chose Options -> List All Devices.
5. From the USB Device list chose "Samsung USB Composite DEvice".
6. Press "Install Driver", click "Yes" to the prompt and if you receive
a message about being unable to verify the publisher of the driver
click "Install this driver software anyway".
7. Done. This only needs to be done once.
ClockWorkMod Install Instructions
1. First root you tab (use one click root or z4root) then downloaded rom manager.
2. Unzip the flash_image_VZW_zimage.zip. It will have have two files flash_image and zimage. you only need to use the zimage file. Open Heimdall-Frontend.exe and browse to where you unzipped the zimage to and select it. Make sure the box infront of zimage is checked. Hit start and it should flash the zimage and reboot the tab.
when it reboots it will get stuck at the samsung screen long hold the power button to shut it off. boot into recovery (cwm) power button plus volume up button it will start backing up to do the fs conversion but it will fail at /data and /cache. it will leave you in recovery.
3. While still in recovery select factory reset/data wipe when finished also do a cache wipe.
4. select reboot system, if you let it try to boot it will loop/hang on the SAMSUNG logo, this is not an issue just hold power key until it powers off.
5. while off hold volume up + power until you see the SAMSUNG logo then release both keys! NOTE: if step 4 does not fully power off and reboots just keep holding the power button until the screen blanks again then let go and quickly hold down only volume up + power until you see the SAMSUNG logo.
6. once it boots back into recovery (cwm) it will start the same backup/conversion process again, this time it will finish and leave you in recovery.
7. select reboot system and wait for it to load the tab back to froyo. (it will be back to factory defaults with the activation screen again)
8. Your tab will still be rooted so install terminal emulator and run "mount" to verify that your partitions are ext4.
9. Power off then boot back into recovery with volume up + power, it will boot back into recovery (cwm)
10. Do a backup and reboot your tab.
Source:
http://www.thegalaxytabforum.com/index.php?/topic/1775-clockworkmod-for-sprint-galaxy-tabs/
Yes, I tried this and it works great but be aware that certain kernels seem to mess it up.
Which Kernel Seems To Work The Best?
@ lloydcabraham
Which kernel is the most stable?
I rooted my tab last night in preparation for the HC port, and I'm curious about whether CWM is necessary... seems everything needs to be flashed via Heimdal or Odin, so is the advantage to having CWM installed just the wipe capabilities? I'm used to my EVO, and flashing/rooting/modding which is obviously different, I just don't understand what the differences are, I guess. THANKS SO MUCH FOR THE STEP BY STEP! Simpletons like me find them EXTREMELY useful!
Great work, and thanks again!
Sent from my PC36100 using XDA Premium App
I'll have to try this soon.
IP IHI II IL said:
I rooted my tab last night in preparation for the HC port, and I'm curious about whether CWM is necessary... seems everything needs to be flashed via Heimdal or Odin, so is the advantage to having CWM installed just the wipe capabilities? I'm used to my EVO, and flashing/rooting/modding which is obviously different, I just don't understand what the differences are, I guess. THANKS SO MUCH FOR THE STEP BY STEP! Simpletons like me find them EXTREMELY useful!
Great work, and thanks again!
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Somewhat Offtopic:
Chances are the honeycomb port will come to GSM Devices First, We can only hope that it comes to Sprint and Verizon devices.
I believe the build being worked on right now in here is based on a cdma device...
Not off topic at all. THE ONLY HC port is currently being built by spacemoose (reading more than one thread on one website helps) and that wasn't the focus of my question. Please read before you quote/insinuate. Don't wanna be tagged with the troll label...
cdguider said:
Somewhat Offtopic:
Chances are the honeycomb port will come to GSM Devices First, We can only hope that it comes to Sprint and Verizon devices.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA Premium App
Clockworkmod has many advantages if you flash different roms, or say wanted to backup your current sprint rom & settings before testing Honeycomb Port.
As far as Honeycomb Port goes,
Again Chances are Honeycomb will port to Gsm Devices First,
Honeycomb is still Closed Code.
I said somewhat off topic, which it was, considering the thread is titled Clockworkmod.
Get your facts straight.
cdguider said:
@ lloydcabraham
Which kernel is the most stable?
Click to expand...
Click to collapse
I like Bauxite but you will get a flaky camera (Sometimes won't initialize without reboot) and seems to mess up CWM (Although redoing these steps fixes it) but I do love running @ 1.4 super stable!
cdguider said:
Clockworkmod has many advantages if you flash different roms, or say wanted to backup your current sprint rom & settings before testing Honeycomb Port.
As far as Honeycomb Port goes,
Again Chances are Honeycomb will port to Gsm Devices First,
Honeycomb is still Closed Code.
I said somewhat off topic, which it was, considering the thread is titled Clockworkmod.
Get your facts straight.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=11780452&postcount=1
3/26/11 #2:...Second... The "dirty" port will be for CDMA devices, but as soon as the CDMA version is released I'll look into getting a GSM version out asap. Shouldn't be hard. Instead of using my own kernel for this one, I'm using a modified version of Boushh's kernel and can probably hack together a suitable kernel for other devices as well. My own kernel for the larger project is still in fluctuation as I have to make changes to suit the build on a regular basis, but when I finalize that kernel I'll release it as an update and it will get a repo of it's own.
Click to expand...
Click to collapse
The quote was for what?
Re-read it one more time...
Really
I still stand by my message.
It's also apparent you didn't go back to page 1 otherwise you would have known I acknowledged spacemoose1 Honeycomb Port.
Despite someone working on Honeycomb port for Sprint / CDMA devices.
Chances are someone else is working on it for GSM, as with damn near anything, GSM devices will most likely get it first,
KEYWORD: most likely, and if you read the previous post - keyword is chances are
Bottom line is who cares who gets it first.
I'm well aware of most developments going on XDA
can u guys just drop it already!
Ok im stuck I followed steps but I am stuck at the samsung screen won't boot into recovery I don't know what I did wrong... I need help I have it stuck! (sigh) uSING hEIMDALL It isn't specific on which box I should use the zimage in which box using heimdall... I used it in the recovery under other made sure the box was checked. It ran through backups 2 times then looked like it was launching into recovery cwr 3.0 but when I picked it up it turned off when I turned on all I get is the samsung logo FOREVER... I have tried using heimdall again and tried to use it under FACTORYFS but same result. Please help. All I have now is a Huge Expensive Paper Weight. HELP
*** Ok after further review *SIGH* I understand I probably should have studied the damn thing better there is an option for zImage there... So how bad did I mess this thing up and is there a way to UnDue what I have Done?
Update-
So I was able to flash the Zimage and get to recovery but when I tried to wipe/data/cache and load K-lean rom I got this ---->http://img819.imageshack.us/img819/8655/imag0061y.jpg
I was also able to boot in but couldn't launch because every one of the launchers would fc.
I will attempt another ROM but I fear it is bricked.... I don't give up easily so any help would be awesome.
Thanks in advance.
Damn,
Can you boot into recovery at all? Ifa ll fails, put your Tablet in downloader mode, and flash the file below, follow the instructions in the zip file, if you have done some of the steps skip them, however read very carefully.
http://www.gsmelite.com/Sprint Galaxy Tab EA24 Flasher Odin.zip
cdguider said:
Damn,
Can you boot into recovery at all? Ifa ll fails, put your Tablet in downloader mode, and flash the file below, follow the instructions in the zip file, if you have done some of the steps skip them, however read very carefully.
http://www.gsmelite.com/Sprint Galaxy Tab EA24 Flasher Odin.zip
Click to expand...
Click to collapse
So I was able to flash the Zimage and get to recovery but when I tried to wipe/data/cache and load K-lean rom I got this ---->http://img819.imageshack.us/img819/8655/imag0061y.jpg
I was also able to boot in but couldn't launch because every one of the launchers would fc.
I will attempt another ROM but I fear it is bricked.... I don't give up easily so any help would be awesome.
Thanks in advance.
Thanks for the link... Will give it a try.
Really don't know what to say about the error message, My tab was messed up with errors like can't mount....., some other stuff, I had to send mine in to get replaced, never would go past the samsung logo. At the time the only thing Sprint users had was the Stock DJ30 With Modem.
Now we have no modem.
EA24 Stock
Ext 4
Honeycomb Port In Progress.
cdguider said:
Damn,
Can you boot into recovery at all? Ifa ll fails, put your Tablet in downloader mode, and flash the file below, follow the instructions in the zip file, if you have done some of the steps skip them, however read very carefully.
http://www.gsmelite.com/Sprint Galaxy Tab EA24 Flasher Odin.zip
Click to expand...
Click to collapse
Before I tried that I loaded the Honeycomb ROM well it isn't but the Khasmek's AOSP beta 1 and it worked everything working but the real question is what to do now... If I reboot does it load agian? Should I use Rom manager and run a recovery Backup? what would you advise?
****Update
So after getting everything setup I tried to do a boot to recovery through Rom Manager and low and behold back to dreaded SAMSUNG screen with NUTIN happening. Will try your steps next
****Update
After following steps and flashing image with odin... I was able to boot up fine... Downside---> My Verizon tab is now a Sprint Tab ... I need to find the .tar for VZW anyone? ANYONE? *SIGH*
Hello,
I know nothing about rooting so I may be using the wrong terms. I've read a number of people are having issues with their phones after they've rooted or changed to rom or something. I've also read you can run stock(?) but be rooted (or something like that) so you won't have any issues.
Is there a way to give root access without really changing anything about your phone other than enabling tethering? I really only want to enabling tethering. Oh and the sonicwall client says the phone must be rooted or have root access or something before I can run it.
Yeah that can be done, but once you're rooted, you'll end up flashing roms lol
Sent from my SPH-D710 using xda premium
Instructions on how to get root with stock kernel here: http://forum.xda-developers.com/showthread.php?t=1273730
I followed the instructions to the tee and it worked perfectly. I have wifi tethering working now.
Thanks. If anyone has been flashing or rooting on Samsung Androids for a while, what do you think the chance is that I'll be able to do the over the air update for this phone when it comes out if I do root it?
boe said:
Thanks. If anyone has been flashing or rooting on Samsung Androids for a while. What do you think the chance is that I'll be able to do the over the air update for this phone when it comes out if I do root it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=18038477&postcount=46
The other thread is long and convoluted, pm me if you need anymore details, but the original threads in development by ACS are quite clear and easy to follow.
nabbed said:
http://forum.xda-developers.com/showpost.php?p=18038477&postcount=46
The other thread is long and convoluted, pm me if you need anymore details, but the original threads in development by ACS are quite clear and easy to follow.
Click to expand...
Click to collapse
Thanks. I appreciate you taking the time to reply. To be honest I really don't know what you said though. I'm sure it is simple and obvious but I don't know squat about modifying my android phone so I'm not sure what you said really means.
Anyone know if there are any videos I can follow along to get to where I need to be. I think if someone tries to explain it to me in text I'll get lost and people will get frustrated with my lack of android knowledge.
boe said:
Thanks. I appreciate you taking the time to reply. To be honest I really don't know what you said though. I'm sure it is simple and obvious but I don't know squat about modifying my android phone so I'm not sure what you said really means.
Anyone know if there are any videos I can follow along to get to where I need to be. I think if someone tries to explain it to me in text I'll get lost and people will get frustrated with my lack of android knowledge.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1268037
http://forum.xda-developers.com/showthread.php?t=1273647
Here's what you will be doing:
1) Use "Odin" method to flash kernel+cwm recovery (.tar file) from your computer to the phone.
2) Use recovery to flash su.zip from the phone itself.
3) Same as 1 but stock kernel+recovery.
Here's how to do it:
1) Install Samsung Kies software on your computer. It installs usb drivers necessary to communicate to the phone.
2) Install odin software on your computer. Download .tar file for kernel+cwm.
3) Open odin, follow directions in the first thread to point to the .tar file you download from the same thread.
4) Shut down phone. Use key combination to reboot the phone into "download mode". Connect phone to computer with usb cable. Use odin on computer to commence flash of .tar file. Phone will reboot.
5) Download su.zip from the first thread. Place it on usb storage of the phone.
6) Shut down phone again. Hold down Volume Up and power buttons until you see orange menu. That's CWM recovery.
5) Choose install .zip from sdcard (it really installs from usb storage, not from sdcard). Choose select zip on sd card. Navigate to su.zip, confirm.
Then use the menus to go back and reboot the phone.
6) Download stock kernel+recovery from second thread. Start from step 3 above to flash the stock .tar file.
EDIT: Oh yeah, there's a video in the first thread. Not sure how useful it is though.
EDIT2: The video is old. It has conflicting information with the stuff in the first thread. Use it very cautiously, use the links to download from the first thread. You also don't need .pit file. Only .tar files.
EDIT3: these are the file links:
Kies: link
odin: http://forums.acsyndicate.net/ACS/Odin3 v1.85.zip
CWM+kernel .tar: http://forums.acsyndicate.net/ACS/acs-eb30-clockwork-epic-touch-4g-sep-20-4-00-pm.tar
su.zip: http://www.multiupload.com/TD3X6TM9O1
stock .tar: http://www.inspiringandroid.com/mirrors/devices/epic4gtouch/kernels/acs-eg30-stock-kernel-pulled.tar
Thanks! I'll give it a try.
I installed KIES it says "reconnect the device in Samsung Kies (PC Studio) mode. Current connection mode not supported by Kies. I'm not sure how to connect it in Samsung Kies mode.
Odin 1.85 shows it connected as ID0 (com5)
I only have auto reboot selected and the check for PDA as well as the acs-eb30 ewm file.
The phone says downloading but the first box in odin says fail.
Not sure if it is safe to reboot phone.
To answer a question you asked earlier, if you root and take an OTA update the chances are very good you'll lose root. If you're rooted and want to stay that way, wait until devs work with the update and come up with a "root-safe" version.
.....
boe said:
Thanks! I'll give it a try.
I installed KIES it says "reconnect the device in Samsung Kies (PC Studio) mode. Current connection mode not supported by Kies. I'm not sure how to connect it in Samsung Kies mode.
Odin 1.85 shows it connected as ID0 (com5)
I only have auto reboot selected and the check for PDA as well as the acs-eb30 ewm file.
The phone says downloading but the first box in odin says fail.
Not sure if it is safe to reboot phone.
Click to expand...
Click to collapse
You don't need to run kies to use Odin. Kies is only installed for usb drivers.
I'm not sure what would happen if you had both running at the same time.
If you want to use Kies later, you would need to uncheck USB Debugging on the phone in Settings/Applications/Development.
The phone says "downloading" regardless of whether it is flashing the kernel or not. Did you follow the instructions from the first thread?
4. Open Odin3 V1.85 and on the left side ONLY have AUTO reboot checked (VERY IMPORTANT)
6. Check the PDA slot and then press the PDA button and navigate to the Tar file and select it
7. Now power off your Epic Touch.
8. Once fully powered off, press and hold volume down, home key, and power button at the SAME time.*This will take you into Odin mode.
9. Plug your phone into your PC.
10. You should see COM# (the number doesn't matter) in the ID:COM box
11. Press start and let it run through the process!*
Click to expand...
Click to collapse
There's a step missing, but I suppose they didn't mention it since it's fairly obvious. I don't know if it matters...
The step is 8a) When you see odin prompt to continue, confirm to enter odin mode.
Also make sure that those .tar files downloaded correctly.
Thanks - you nailed it. If you have kies running you can't get odin to update the phone. My phone is all updated - ran all the steps.
Do I use a built in app on it for tethering or add an app?
boe said:
Thanks - you nailed it. If you have kies running you can't get odin to update the phone. My phone is all updated - ran all the steps.
Do I use a built in app on it for tethering or add an app?
Click to expand...
Click to collapse
I think you need Wifi Tether. Search for it, it's gonna be on code.google.com. I myself don't use it, but I heard it works pretty much out of the box w/o tweaking.
nabbed said:
I think you need Wifi Tether. Search for it, it's gonna be on code.google.com. I myself don't use it, but I heard it works pretty much out of the box w/o tweaking.
Click to expand...
Click to collapse
My sonicwall client works great with root access. I haven't been able to get the wifi tether to work yet. I can't find the device if I enable security. I can't seem to find the right BT drivers when my computer finds it via BT. If I disable security I can findi it via wifi but with our without acccess control disabled I can't actually complete the wifi connection.
Update - I did get it to connect via tether after all. I hadn't ever had an issue connecting to about 20 wireless networks with my laptop but I did notice a 5002 event churning away in the event viewer when I tried to connect. I updated my wireless drivers and I'm all set!
Thanks for all the help and patience!!!
UPDATE: MOP Just updated to support, so you could probably reflash the ROM in step 3 below, and that should fix this issue. You can also just push the CSC.tar to the phone and use MOP to fix if you ever do a factory reset, as 60MB is a lot less than 2GB
Long Story Short: If you were DLG Rooted (Knox 0x0) and upgraded to 4.4.2 with Mobile Odin Pro (Everroot) and flashing the Bootloader in Odin, before reboot, and your phone is acting strange or you wiped/factory reset your phone and lost stability, flash the CSC.tar file in Odin, and it should fix it for you. [Can also be flashed before you wipe/factory reset, and may fix your problem, eliminating the need to wipe, as it did for me]
Proof Below [Screen shot and photo of Knox status]
Following this thread I was able to go from a De La Vega Knox 4.3 Knox 0x0 to 4.4.2 with root, and Knox still at 0x0 [See images below].However, I was having issues with some things, so against the recommendations in that thread, I wiped the cache. Well this ballsed up the phone quite well. Keyboard didn't work, action memo stopped, and just wasn't happy. Next, against better advice (BIG RED WARNING IN APP) I tried to reflash the stock ROM with Mobile Odin Pro....
Bootlooped my phone, Called in a warranty replacement, that came in today. I then did the following:
1) De La Vega Root Method
2) Copy new Stock Rom to Root of Phone
3) Flash with Mobile Odin Pro (Keeping Root), and set to reboot in to Download Mode
4) In Odin (Desktop Version) Flash the File in post 3 of the thread I mentioned at the start
5) Reboot phone
6) Flash the CSC.tar [Link] in Odin (Desktop Version) <-- I had to do this step, as while keyboard was working, the phone just felt buggy. Settings crashed and was just unhappy
{
"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"
}
http://tinypic.com/r/2vbmwed/8<---Bigger pic
http://tinypic.com/r/2dwc4u8/8
Mediafire link to CSC.tar
Credit:
designgears for RDLV
joetzzz for the 4.4.2 Bootloader
Dreamgun for starting the other thread
krishsastry for the first readable translation from the german website posted by Dreamgum
Chainfire for SU and MOP
And anyone else I missed (Did a bunch of research on how to extract the cache and convert to tar Odin flashable)
nygmam said:
1) De La Vega Root Method
2) Copy new Stock Rom to Root of Phone
3) Flash with Mobile Odin Pro (Keeping Root), and set to reboot in to Download Mode
4) In Odin (Desktop Version) Flash the File in post 3 of the thread I mentioned at the start
5) Reboot phone
6) Flash the CSC.tar [Link] in Odin (Desktop Version) <-- I had to do this step, as while keyboard was working, the phone just felt buggy. Settings crashed and was just unhappy
Click to expand...
Click to collapse
nygman, thank you for taking this plunge as I was thinking of doing the same for the sake of Science!
I am going to try this tonight; some questions for clarity on your process, if you please:
Step #2 - Are you referring to this file: N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar.md5 [Size: 2.07 GB (2,230,825,042 bytes)] ?
Step #3 - Are you using the same MOP settings as referenced in the original German thread?
EverRoot
Inject SuperSU
Inject MobileOdin
Wipe Dalvik Cache
Step #5 - When you reboot the phone - do you IMMEDIATELY go into DOWNLOAD mode to initiate step #6 or should I boot the phone normally see how things are and determine if my flash results in sluggish/buggy/fc's as you were experiencing before proceeding to final step?
Regards,
drExel said:
nygman, thank you for taking this plunge as I was thinking of doing the same for the sake of Science!
I am going to try this tonight; some questions for clarity on your process, if you please:
Step #2 - Are you referring to this file: N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar.md5 [Size: 2.07 GB (2,230,825,042 bytes)] ?
Click to expand...
Click to collapse
That's the one
Step #3 - Are you using the same MOP settings as referenced in the original German thread?
EverRoot
Inject SuperSU
Inject MobileOdin
Wipe Dalvik Cache
Click to expand...
Click to collapse
Yes
Step #5 - When you reboot the phone - do you IMMEDIATELY go into DOWNLOAD mode to initiate step #6 or should I boot the phone normally see how things are and determine if my flash results in sluggish/buggy/fc's as you were experiencing before proceeding to final step?
Click to expand...
Click to collapse
I would wait and see how it is. Let it reboot, try the keyboard, create and save a new action memo, and go to settings, input, and see if you can change the handwriting language. When I completed step 5, I had issues with action memo and settings, not keyboard. If it works, I would leave it, but both times I have done this, the phone felt buggy after, only to become unusable after a factory reset. The CSC file should fix this. It did for me, so I posted it, Hoping to help others fix theirs should the same issue or others arises.
One last thing I forgot to note, this is for the T-Mobile SM-N900T.
Success is a Wonderful Story
I followed this guide directly.
After the initial boot at Step #5, tested keyboard and it seemed okay.
But attempting to access Action Memo caused a FC. As well as attempting to access Language in Settings.
After flashing the provided .CSC - no issues.
I am now at 4.4.2 w/root!
Knox Kernel Lock and Warranty Status remained: 0x0
Note: System Status reflected as "Custom" -- I know this can be reset to "Official" -- I think using Wanam?
Thank you again!
Regards,
drExel said:
I followed this guide directly.
After the initial boot at Step #5, tested keyboard and it seemed okay.
But attempting to access Action Memo caused a FC. As well as attempting to access Language in Settings.
After flashing the provided .CSC - no issues.
I am now at 4.4.2 w/root!
Knox Kernel Lock and Warranty Status remained: 0x0
Note: System Status reflected as "Custom" -- I know this can be reset to "Official" -- I think using Wanam?
Thank you again!
Regards,
Click to expand...
Click to collapse
Great news, glad it helped hopefully it helps others. Enjoy your new KitKat rooted Knox 0x0 status!
nygmam said:
Great news, glad it helped hopefully it helps others. Enjoy your new KitKat rooted Knox 0x0 status!
Click to expand...
Click to collapse
Good job man
dragonstalker said:
Good job man
Click to expand...
Click to collapse
Thanks. I just got the MOP update and it now supports 4.4 on this phone so you could probably just reflash the full ROM again in MOP as above and fix issues. However, I still think this is a good post, as now I have this CSC.tar file on my phone, so if I factory reset, I can flash this file on the phone and revive the phone easily. Plus it is smaller than the 2GB ROM, which fees up space. I will update post 1 later today to reflect this option.
Thanks NYGMAM for this info, I was able to successfully update, root and now I'm on stock T-Mobile N900T 4.4.2, fully rooted and the Knox warranty is still on 0X0 and the Device Status is still on Official mode.
Phone is working fine so far and I didn't have to use the CSC. tar file.
Great info. ?
Sent from my SM-N900T using xda app-developers app
I confirm, my T-Mobile Samsung Galaxy Note 3 N900T is rooted to Android 4.4.2 KitKat without tripping Knox. Knox is at 0x0.
I successfully did it following only this thread without having to read the German website.
These instructions require your phone to ALREADY be rooted. It allows you to KEEP the Root access you already have and upgrade to Android 4.4.2 KitKat without losing your Root access. Your phone must be rooted FIRST!
REQUIREMENTS:
1- Purchase and install Mobile Odin Pro from the Google Play Store.
2- Download Odin that has the BL (bootloader) button from http://forum.xda-developers.com/attachment.php?attachmentid=2551152&d=1391196733
3-
A) IF YOU HAVE A US T-MOBILE Galaxy Note 3 N900T, THEN download the Bootloader (N900TUVUCNB4_BL.rar) referenced in http://forum.xda-developers.com/showthread.php?p=50963302
OR
B) If you DO NOT have a US T-MOBILE Galaxy Note 3 N900T, then the Bootloader above will not work for you. You must build your own using the German instructions at http://www.mobtivity.com/de/news/galaxy-note-3-update-auf-android-kitkat-mit-root-und-knox-0x0.html You can go to http://translate.google.com and copy that link into the input box and press the button to have Google translate the website for you.
4- Download N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar.md5 Size: 2.07 GB (2,230,825,042 bytes)]
5- Download CSC.tar referenced at the top of this thread.
N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar.md5 will be copied to your phone and used by Mobile Odin. All other files will be used by Desktop Odin on your computer.
OVERVIEW:
When you upgrade to the stock KitKat ROM without following the instructions in a guide like this, you will lose Root.
This guide allows you instead to hijack the phone before it finishes booting to install a custom BootLoader which put Root back into the phone before the phone finishes the first boot.
The settings you put into Mobile Odin will perform 2 functions. 1. It flashes the 4.4.3 Kit Kat ROM onto the phone and 2. IT SETS THE PHONE TO REBOOT TO DOWNLOAD MODE (<-IMPORTANT!!!) and NOT to reboot normally.
Once KitKat is flashed, Mobile Odin reboots the phone into DOWNLOAD MODE, THEN you can use Desktop Odin, CHECK AutoReboot AND Phone BootLoader Update, to insert a custom bootloader which will allow you to keep root.
Once the bootloader is flashed, the phone will boot up normally. I immediately shut the phone down, put it into download mode, and flashed the CSC.tar file into the CSC button on Desktop Odin with the only option checked is AutoReboot.
STEPS:
1) Safety: Remove your SDCard, backup your phone, etc.
2) De La Vega Root Method (<- Skip if your phone has already been rooted)
Since my phone had already been rooted with the Root De La Vega method and was running Jellybean, I skipped Step 1.
3) Copy new Stock Rom to Root of Phone (N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar.md5 [Size: 2.07 GB (2,230,825,042 bytes)])
Your phone needs to be rooted before you can copy the ROM to your phone. My phone would not allow me to copy the file to the root directory (/), so I copied it to the sdcard directory (/sdcard)
4) Flash with Mobile Odin Pro (Keeping Root), and set to reboot in to Download Mode
Start Mobile Odin Pro:
i) Scroll to Open File... and click it.
ii) Find the N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar.md5 file from whatever directory you copied it to on your phone.
iii) Scroll to EVERROOT and ensure the following are checked
a. Enable EverRoot
b. Inject Superuser
c. Inject Mobile ODIN
iv) Scroll to WIPE
a. Ensure "Wipe Dalvik cache" is checked
v) Scroll to After wipe... and click it.
vi) Select Download mode and click the back button.
viii) Leave all other settings as they are.
iv) Scroll up to where it says "Wipe Start the wipe procedure" and click it.
This will flash KitKat onto the phone and reboot the phone into Download mode. Once the phone is in Download mode...
5) In Odin (Desktop Version) Flash the File in post 3 of the thread I mentioned at the start
i. Open ODIN on your computer.
ii. Verify your phone is connected to your computer and recognized by Odin with a COM Port number under ID:COM and ADDED! message in the messages window.
iii. Check Auto Reboot
iii. Click the BL button and select the bootloader from wherever you saved it on your computer.
a) If you are using the T-Mobile Galaxy Note 3 N900T, use the N900TUVUCNB4_BL.rar bootloader referenced above.
b) If you are not, use the bootloader you created following the German instructions.
iv. Check Phone Bootloader Update.
v. Verify everything looks like http://www.mobtivity.com/images/news/Tutorials/Note3-Knox0/Odin.jpg and click Start button.
6) Phone will reboot. Then turn it off and set it to download mode ( Press Power, Home and Volume Down buttons at the same time).
7) Once the phone is in download mode...
i. Open ODIN on your computer.
ii. Verify your phone is connected to your computer and recognized by Odin with a COM Port number under ID:COM and ADDED! message in the messages window.
iii. Check Auto Reboot
iv. Click the CSC button and select the CSC.tar file from wherever you saved it on your computer.
v. Verify that only Auto Reboot is checked, and all buttons are blank except for the CSC.tar file beside the CSC button, then click Start.
After CSC is flashed, phone will reboot into KitKat with Root! Give the phone a little time for everything to load. Checkroot gave me a heart attack by stating I didn't have root access, but it was only because the phone hadn't fully booted up yet!
i wonder if this will work on galaxy s5 (exynos edition). i really want to root my phone but dont want to trip the knox... please help
thanks.
cnn888 said:
i wonder if this will work on galaxy s5 (exynos edition). i really want to root my phone but dont want to trip the knox... please help
thanks.
Click to expand...
Click to collapse
You might get better help in the galaxy s5 forums.
Getting a bunch of FCs after updating to NE6. Can I try flashing this CSC or is this specific to NB4? TIA
Sent from my SM-N900T using Tapatalk
hamsup1o said:
Getting a bunch of FCs after updating to NE6. Can I try flashing this CSC or is this specific to NB4? TIA
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
I'm not entirely certain what the CSC file is for, but seeing as how I went straight MI7 to NE6 I made a CSC for NE6 especially since my phone was saying the CSC version was NB4 (so yes, NB4 will work, but it will not be the version of the NE6 ROM). My phone is working well, no FCs my Direct Input works, Samsung Keyboard works, haven't had any issue with an app yet, only lag I've experience was when I was restore my backup texts, but that's 12k+ so yeah. Anyways, this CSC is taken directly from the stock ROM N900TUVUDNE6_N900TTMBDNE6_N900TUVUDNE6
CSC 4.4.2 NE6
Hello, I have a Samsung Galaxy S3 T-Mobile version (SGH-T999). I had the official Android 4.0.4 version,I could not do the update to 4.3 version,so I only variant has to do root on the phone and snort with unroot install a 4.3 version,which I did. After installing I had the first boot and I had setup Google accounts, Dropbox accounts, etc. .. I did not do the setup, but I skipped because I was activated mobile data. When we had removed all the money that I had in the mobile card,I went in the settings and tried to enable Wi-Fi,but could not, constantly goes out. I do not know what the problem was but would gladly like to help me, because my phone never do true Wi-Fi. Thank you in advance!
Please do a Factory Reset and set up all over again.
I supplemented the money on the card,this morning at 9 am done factory reset. I tried to turn on Wi-Fi but the same as before the reset and,again, I turn on the mobile data and took my money from mobile cards. If it is to google accounts'll pay packages for internet and I'll set. If you need I will put pictures.
Can you please post the thread or instructions you followed to get 4.3 ? If Factory Reset didn't cure your issue, we need to look at how you did the update.
Make sure auto switch networks is turned off in settings. Did you try with the sim card removed?
Sent from my SM-N900T using Tapatalk
@ Perseus17 On the phone I did root through Odin3 program, entered into recovery mode and installed SuperUser phone was rooted. I downloaded the official 4.3 update for the appropriate model and unroot when I installed a 4.3. Unroot I've done over the application Triangle Away and Mobile Odin. If you want, I can explain in more details how I installed. Hello!
@ DocHoliday77 How do you turn off that? Whether we can send a picture or explain the steps on how to find it? Hello!
If you installed the Official 4.3 Release and then right now its not Rooted. Is this correct ?
Secondly, If I understand it correct, Right now, the phone will not connect to any Wireless networks. Especially those it was able to connect before the update ? Kindly confirm.
It is true that the phone is no longer rooted because when installing official Android version of the phone is no longer rooted. Phone before the update could go on any Wi-Fi network. After the update can not be either one,or more precisely, the Wi-Fi does not start.
Just for Kicks, can you flash the Insecure Kernel via custom Recovery such as CWM or TWRP ?
See the state of Wireless after reboot.
What I need to do?
Step 1 - You flash a Custom Recovery such as CWM or TWRP via Respective Apps Rom Manager or Goo Manager.
Step 2 - Download the insecure kernel I linked in my last post to your phone's SD Card. Reboot to the Recovery and flash that kernel Zip file.
I have obtained a Sprint s4 mini. From what I can find, the current kernel is SE secure enforcing.
The exact build number is KOT49H.L520_4.4.2_0016
Build date is Oct 7 2014
I am not new here, I know that all known root methods are now bust. What other options are there?
Searching seems to be pretty difficult for this device. All searches for bootloader and recovery come up for the i9190 / i9195
If I use Kies or Odin to flash a previous recovery image, will that brick the device? Also in the settings, it says Secure Boot Status - Type: Samsung
Guess that is referring to the Knox enforcing
The particular image I had in mind to flash with Odin is SPR-L520VPUAMK2-20131115204826
Will it work? Or am I screwed?
Well no one was able to answer my question, so I had to figure it out on my own. Hopefully the following information will be of help to someone else without spending 36+ hours digging through the internet for answers.
You CAN fix your phone it you are on the NJ1 kernel. This is NOT a guide to fixing a bricked phone, although it may fix that too.
If you are on the NJ1 kernel, there are no root methods currently available. You MUST be on NE3 or lower. I also attempted to flash the custom recovery through Odin, but after a reboot it was as if I did nothing. No Knox flag, no warranty trip, no custom recovery.
Here is what I did to get custom recovery and root:
READ THIS BEFORE ATTEMPTING STEP 1.
This is only for the Sprint variant of the S4 Mini. Model number SPH-L520
Your Warranty could be voided. Proceed if you like. (More info on steps 5 and 6)
I had a horrible time getting the downloads from Sammobile. You WILL have to create an account and login to download files. I could not find any working links for the firmware below except for this site. Register a user name and password, DO NOT UNCHECK THE BOX that says receive emails from Sammobile OR YOU WILL NOT GET YOUR REGISTRATION EMAIL. On the Register page it is at the bottom. After you register, check your email and click on the link to complete the registration.
Close all your windows that are open to sammobile.
You are going to want to download Internet Download Manager in order to download files from Sammobile. After many many attempts to download the firmware from Sammobile, all tries failed. YOU ARE GOING TO NEED IDM to get a reliable download.
Download IDM ---> https://www.internetdownloadmanager.com/download.html
Install it and follow these directions to enable resume downloads in IDM ---> http://forum.xda-developers.com/showthread.php?t=2765456
If you do not do the steps above, you most likely will have failed download after failed download.
Even after setting this up, the firmware download failed on me twice. I deleted it from the download list in IDM and started it again.
IDM integrates well with Internet Explorer. Kinda buggy with Chrome. I would suggest using IE for the rest of this Tutorial.
Ok, now that you have that squared away, move on to step 1
_________________________________________________________________________________________________________________________
1) Flash your phone back to NE3. You can get that here ---> http://www.sammobile.com/firmwares/download/31482/L520VPUBNE3_L520SPTBNE3_SPR/ (click Regular Download, then on new page right-click Confirm Download and click SAVE AS. After that the IDM window should pop up. Just Start Download)
Also go ahead and download download the NJ1 in case things get rough. List of all firmwares here ---> http://www.sammobile.com/firmwares/database/SPH-L520/
2) Download and install the Samsung drivers ---> http://www.mediafire.com/download/a4hd8y0c1iakysk/Samsung-Usb-Driver-v1.5.49.0.exe
Download Odin 3.09 ---> http://androidhost.org/PVAIv
Unzip Odin to a folder or desktop. Do not run it from in the zip folder.
3) Run Odin 3.09.
Reboot your S4 Mini SPH-L520 into download mode. Turn phone off > Hold Volume Down, Home Button, and Power Button all at the same time. Wait for the phone to buzz and the pop up on the screen. Release the buttons and press Volume Up to confirm.
Now plug in your phone to your computer. It might take a few seconds for the drivers to install. Wait until Odin shows blue color in the first bar on the left side. Should say 0:[COM3] (the COM number will be different depending on your computer and the USB port you plugged it into)
VERY VERY IMPORTANT! Make sure that the AUTO-REBOOT and F. RESET TIME boxes ARE checked. Make sure that the RE-PARTITION box is NOT checked.
4) Unzip the NE3 download from earlier. Click on the AP button in Odin and navigate to where you unzipped NE3. It should be a .MD5 type of file
Give Odin a few mins to check the file. It may appear that Odin has hung up, just be patient.
After Odin has run the check, it should say ok in the little window on the bottom left. Now click START and wait.
DO NOT bump the phone, the laptop, the usb cord, and MAKE SURE THE BATTERY DOES NOT FALL OUT!!!
After Odin is done flashing, it will reboot the phone. After the initial reboot, the phone will reboot itself once more. Be patient
Now wait for the phone to completely boot up.
5) After you have got back to ME3, you can follow this guide to root it ---> http://androidxda.com/root-samsung-galaxy-s4-mini-sprint-sph-l520
You already have most of the files you need. Just follow the instructions and download what you do not have already.
By the way, in Odin the AP button and the PDA button are the same
(This method should not trip the Knox counter, but I am unsure. Mine was already tripped before all of this)
OPTIONAL (this will trip the Knox counter and lose warranty status)
6) Now you can use this guide to install the custom recovery ---> http://techbeasts.com/2014/05/04/in...-root-sprint-samsung-galaxy-s4-mini-sph-l520/
Again, you already have most of the files you need. DL what you don't have.
_________________________________________________________________________________________________________________________
I am planning on instaling CM11 ---> http://forum.xda-developers.com/showthread.php?t=2669991
This ROM apparently needs a specific recovery in order to work properly. I installed that one instead.
MAKE A BACKUP IN THE RECOVERY OF THE STOCK ROM BEFORE FLASHING ANY CUSTOM ROMS, or else be sorry later.
This is about as simplified as I could get it. Hope this helps out those of you that were as confused as I was.
I will not be providing support. Simply do not have the time. There is more than enough info here to help you figure out what to do.
fire3element said:
I have obtained a Sprint s4 mini. From what I can find, the current kernel is SE secure enforcing.
The exact build number is KOT49H.L520_4.4.2_0016
Build date is Oct 7 2014
I am not new here, I know that all known root methods are now bust. What other options are there?
Searching seems to be pretty difficult for this device. All searches for bootloader and recovery come up for the i9190 / i9195
If I use Kies or Odin to flash a previous recovery image, will that brick the device? Also in the settings, it says Secure Boot Status - Type: Samsung
Guess that is referring to the Knox enforcing
The particular image I had in mind to flash with Odin is SPR-L520VPUAMK2-20131115204826
Will it work? Or am I screwed?
Click to expand...
Click to collapse
Can you help me to backup your first partition on your phone and send to me. You can use EFS Professional on xda.
Hmm....I installed the NJ1 update through Odin. And then flashed the CF auto root (or maybe it was the recovery.tar) with no issues. I did this when NJ1 was first released.
NCTP2 said:
Hmm....I installed the NJ1 update through Odin. And then flashed the CF auto root (or maybe it was the recovery.tar) with no issues. I did this when NJ1 was first released.
Click to expand...
Click to collapse
Can you backup your phone by EFS Pro and send to me. Thanks.
NCTP2 said:
Hmm....I installed the NJ1 update through Odin. And then flashed the CF auto root (or maybe it was the recovery.tar) with no issues. I did this when NJ1 was first released.
Click to expand...
Click to collapse
I was unsure about it considering all the changes with SE Secure and Knox. Always pays to be safer than sorry. I could not find any reports of this anywhere after hours of reading and searching. Thanks for confirming though. :good:
quanqw said:
Can you backup your phone by EFS Pro and send to me. Thanks.
Click to expand...
Click to collapse
I am sorry, I have been really busy. What exactly are you trying to do? Asking someone to backup sensitive data from their phone and share it to a stranger can be alarming.
At least tell us what is going on or why you need the backup.
worked
fire3element said:
I was unsure about it considering all the changes with SE Secure and Knox. Always pays to be safer than sorry. I could not find any reports of this anywhere after hours of reading and searching. Thanks for confirming though. :good:
I am sorry, I have been really busy. What exactly are you trying to do? Asking someone to backup sensitive data from their phone and share it to a stranger can be alarming.
At least tell us what is going on or why you need the backup.
Click to expand...
Click to collapse
thanks alot
the baseband nearly killed me but i thanked my God for you. it worked for me
my question is, is there any way to get it work for domestic sim outside USA?