I have rooted and used this kit once before. I was able to clearly choose what build and android version. Since then my glass broke and I had sent it away to get fixed from samsung and they reset everything and must have updated the device from 4.1.1 to 4.1.2. Now I am looking at my build and android version and am confused about which one to choose because it is different from the last. They did not send me back a refurbished phone by the way.
In settings, my phone currently says:
Model number SGH-T999
Build number JZO54K.T999UVDMD5
Android version 4.1.2
In the tool kit under section US TMOBILE MODEL GSM [SGH-T999] i have the options to choose:
61. Android 4.0.4 [Build IMM76D ALJ4]
62. Android 4.1.1 [Build JRO03C ALK5]
Confused because the first time I had rooted I had chosen 62., but now the numbers do not match.
Or in section INTERNATIONAL LTE [GT-I9305] I have the otions to choose:
11. Android 4.1.1 [Build JRO03C ALI5]
12. Android 4.1.1 [Build JRO03C ALJ4]
13. Android 4.1.1 [Build JRO03C ALJ7]
14. Android 4.1.1 [Build JRO03C ALK5]
15. Android 4.1.2 [Build JZO54K BLL3]
16. Android 4.1.2 [Build JZO54K BLL5]
I would think this time to choose option 15 or 16 but I'm not sure because it's NOT an international phone and again, it says SGH-T999 in the settings/about phone.
Any help to clear up this issue I would appreciate. Thanks.
TheKid1 said:
I have rooted and used this kit once before. I was able to clearly choose what build and android version. Since then my glass broke and I had sent it away to get fixed from samsung and they reset everything and must have updated the device from 4.1.1 to 4.1.2. Now I am looking at my build and android version and am confused about which one to choose because it is different from the last. They did not send me back a refurbished phone by the way.
In settings, my phone currently says:
Model number SGH-T999
Build number JZO54K.T999UVDMD5
Android version 4.1.2
In the tool kit under section US TMOBILE MODEL GSM [SGH-T999] i have the options to choose:
61. Android 4.0.4 [Build IMM76D ALJ4]
62. Android 4.1.1 [Build JRO03C ALK5]
Confused because the first time I had rooted I had chosen 62., but now the numbers do not match.
Or in section INTERNATIONAL LTE [GT-I9305] I have the otions to choose:
11. Android 4.1.1 [Build JRO03C ALI5]
12. Android 4.1.1 [Build JRO03C ALJ4]
13. Android 4.1.1 [Build JRO03C ALJ7]
14. Android 4.1.1 [Build JRO03C ALK5]
15. Android 4.1.2 [Build JZO54K BLL3]
16. Android 4.1.2 [Build JZO54K BLL5]
I would think this time to choose option 15 or 16 but I'm not sure because it's NOT an international phone and again, it says SGH-T999 in the settings/about phone.
Any help to clear up this issue I would appreciate. Thanks.
Click to expand...
Click to collapse
Don't use the toolkit at all. It really has become irrelevant. They are much easier, far more foolproof ways to do what you need. Rooting is what you need, correct?
You are on stock ROM now, did you want something different? If you wanted the stock ROM, you would use Odin from my signature to flash the TWRP tar from my signature. Then use TWRP to flash the SuperSU from my signature.
Yes, I want root. I don't want the stock rom, I want a different rom. How do I go about rooting if I want a different rom. You only mentioned how to root if I want stock rom.
Sent from my SGH-T999 using xda app-developers app
TheKid1 said:
Yes, I want root. I don't want the stock rom, I want a different rom. How do I go about rooting if I want a different rom. You only mentioned how to root if I want stock rom.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
After you flash a custom recovery, flash your ROM instead. Don't need to flash SuperSU, because the ROM will include it.
Ok, I'm pushing the twrp link in your signature and nothing happens. I'm doing this from my gs3, correct, not pc?
Sent from my SGH-T999
TheKid1 said:
Ok, I'm pushing the twrp link in your signature and nothing happens. I'm doing this from my gs3, correct, not pc?
Sent from my SGH-T999
Click to expand...
Click to collapse
Use the tar, and do it through Odin.
Put phone into download mode, put twrp tar file in Odin PDA slot.
Aerowinder said:
Use the tar, and do it through Odin.
Put phone into download mode, put twrp tar file in Odin PDA slot.
Click to expand...
Click to collapse
Lol, I'm lost. I don't know what tar or odin is and not sure how to put phone into download mode. Does any of this take place on PC? If so, I may as well use the tool kit because I don't care if I trip the flash counter. What is the difference other then that? Which brings me back to original question: Since samsung updated my phone to 4.1.2, which option do I pick that corresponds to my phone in the tool kit? Or I am open to the odin thing if it is easier, but so far it doesn't seem that way. Thanks for your help so far.
Sent from my SGH-T999 using xda app-developers app
TheKid1 said:
Lol, I'm lost. I don't know what tar or odin is and not sure how to put phone into download mode. Does any of this take place on PC? If so, I may as well use the tool kit because I don't care if I trip the flash counter. What is the difference other then that? Which brings me back to original question: Since samsung updated my phone to 4.1.2, which option do I pick that corresponds to my phone in the tool kit? Or I am open to the odin thing if it is easier, but so far it doesn't seem that way. Thanks for your help so far.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
As I understand it, the toolkit doesn't support md5 unless you buy it. It causes lots more bricks and confusion and I don't recommend it.
Don't take this the wrong way, but if you don't even know what Odin is, you have gone too far too fast. You should take the time to read through the sticky threads at a minimum. And use Google, and the xda search function for questions you still have. If you're going to be rooting and messing with the device this way, it is expected that you have at least a basic understanding of what tools are used and what it is you are actually doing to your device. Knowledge of Odin is an absolute must when dealing with Samsung devices.
Sent from my SCH-I535 using Tapatalk 4
Probably the tool isn't updated. Just download the root66 uvdmd5 .tar file for your device. The file is already pre rooted, so all you got to do is use Odin to flash it into your device.
Read this first
http://forum.xda-developers.com/showthread.php?t=1949687
USING ODIN
Download and install the latest Samsung USB Drivers
Download and extract Odin
Download the firmware of your choosing (use the root66 version if you want root)
Run Odin by double clicking the Odin.exe within the folder you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the FW you downloaded
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache! (It may seem to hang during boot, this is normal and you must be patient!!!)
DONE!!! :victory:
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
ayeitschris said:
Probably the tool isn't updated. Just download the root66 uvdmd5 .tar file for your device. The file is already pre rooted, so all you got to do is use Odin to flash it into your device.
Read this first
http://forum.xda-developers.com/showthread.php?t=1949687
USING ODIN
Download and install the latest Samsung USB Drivers
Download and extract Odin
Download the firmware of your choosing (use the root66 version if you want root)
Run Odin by double clicking the Odin.exe within the folder you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the FW you downloaded
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache! (It may seem to hang during boot, this is normal and you must be patient!!!)
DONE!!! :victory:
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
You did not mention a recovery like TWRP for instance. Do I need that?
Sent from my SGH-T999 using xda app-developers app
TheKid1 said:
You did not mention a recovery like TWRP for instance. Do I need that?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
You don't need it for root, but it's handy to have. If you want it, flash after root66.
Aerowinder said:
You don't need it for root, but it's handy to have. If you want it, flash after root66.
Click to expand...
Click to collapse
I don't want to flash root66, instead, I was flashing a custom ROM in the PDA slot in ODIN. The touchwiz 4.1.2 ROM i am inserting in the PDA slot is the UVDMD5 4.1.2 Rooted/Modified. Can I do it this way? After I had downloaded this custom ROM, it is in a zip folder. I had extracted the zip folder and there are multiple folders which I am confused as to which one to insert in the PDA slot. Please help.
TheKid1 said:
I don't want to flash root66, instead, I was flashing a custom ROM in the PDA slot in ODIN. The touchwiz 4.1.2 ROM i am inserting in the PDA slot is the UVDMD5 4.1.2 Rooted/Modified. Can I do it this way? After I had downloaded this custom ROM, it is in a zip folder. I had extracted the zip folder and there are multiple folders which I am confused as to which one to insert in the PDA slot. Please help.
Click to expand...
Click to collapse
.tar, .tar.md5 = Odin
.zip = recovery
Aerowinder said:
.tar, .tar.md5 = Odin
.zip = recovery
Click to expand...
Click to collapse
Just to be clear, instead of doing root66, I want to flash a custom rom but i do not see a .tar, .tar.md5 file after unzipping. As a matter of fact, I even tried downloading the root66 file, and is not a .tar or .tar.md5 file either. What is going on?
TheKid1 said:
Just to be clear, instead of doing root66, I want to flash a custom rom but i do not see a .tar, .tar.md5 file after unzipping.
Click to expand...
Click to collapse
Stop unzipping it. Flash the zip in recovery. Odin is for flashing stock firmware packages. Not custom ROMs.
Aerowinder said:
Stop unzipping it. Flash the zip in recovery. Odin is for flashing stock firmware packages. Not custom ROMs.
Click to expand...
Click to collapse
As a matter of fact, I even tried downloading the root66 file, and is not a .tar or .tar.md5 file either. What is going on? when looking where I downloaded the root66 file, it is named root66_TMO_UVDMD5. Is that what I put in the PDA slot?
Aerowinder said:
Stop unzipping it. Flash the zip in recovery. Odin is for flashing stock firmware packages. Not custom ROMs.
Click to expand...
Click to collapse
Let me just reiterate so we are on the same page. My phone is completely stock. I downloaded samsung drivers. I downloaded ODIN. Everything is good so far. Since you are telling me I cannot put a custom ROM in the PDA slot, I am trying the Root66 file. I downloaded the Root66 file for my phone. The Root66 file is not labeled with .tar. It is labled: root66_TMO_UVDMD5. What am I doing wrong?
Ok, it turns out that I wasn't seeing the .tar file because I needed to download winrar. Ok, everything worked out great. Now that I am rooted with root66, how do I get TWRP so I can flash a custom ROM?
A little Google magic and....
http://teamw.in/project/twrp2/106
http://forum.xda-developers.com/showthread.php?t=849028
Yes, this is an att thread, if you use files for your model, most info should still be good.
Also, read my T999L thread. Before walking you through flashing in recovery, I walk you through how to get the recovery. Like the link above, the info is relevant, just use your models files.
Oh, and btw, aerowinder already told you how to flash recovery. Re-read this thread too.
Good luck!
Sent from my SGH-T999V using Tapatalk
Related
Been seeing a lot of post about how to install OTA with a rooted stock ROM. This is by far the easiest way for people to update and not lose any data. All are done using Odin 3.07 on Windows 7 and not going to link it or how to use it lots of tutorials out that show you.
To put in Download Mode -> Vol Down + Home + Power
To Boot into Recovery -> Vol Up + Home + Power
Things needed:
ROM
CWM-Recovery
Root zip file
ROMS
NOTE: These are the FULL firmware of LH1 and NOT small OTA. This is good to have as a backup should something go wrong.
Bell
Telus
Rogers
Sasktel
CWM-Recovery
See Attached, this is an Official CWM from CWM team. If you don't want to use this use whatever recovery you want or had before.
Root: MOVE THIS TO PHONE STORAGE
Chainfire SuperSU
1.) Boot into recovery and create backup, always better to backup
2.) Unzip firmware file and you will see 2 files a dll and md5. The one we need is the md5
Im with bell so mines is -> KIES_HOME_I747MVLALH1_I747MOYCALH1_20120814.100513_REV04_user_low_ship.tar.md5
3.) Put phone into download mode
4.) Load Odin select PDA and select the firmware file you unzipped in step 2. The MD5 file.
5.) Let the phone do its thing and do not touch it until you are at the lockscreen.
7.) Boot into download mode again and select PDA and this time select the recovery tar file
8.) Uncheck F. Reset and flash
9.) Once back on the lockscreen go into Recovery and install the CWM-SuperSU-v0.96.zip to root from phone storage.
10.) Get Triangle Away from here and reset counter.
Excellent guide with links thanks
Sent from my SGH-I747M using xda app-developers app
Any way to flash only the new modem, without reflashing the entire Rom ?
Sent from my SGH-I747
Thanks OP. But i have already flashed LH1 via ODIN. Now i want to install CWM, can you post to link to installation instructions of CWM v6.?
850T5m said:
Any way to flash only the new modem, without reflashing the entire Rom ?
Sent from my SGH-I747
Click to expand...
Click to collapse
Yes, right here.
New cwm flashable modem available here.
---------- Post added at 01:02 AM ---------- Previous post was at 12:59 AM ----------
David Dee said:
Yes, right here.
Click to expand...
Click to collapse
Lol you beat me by seconds.
Sent from my SGH-T999 using xda premium
tarick09 said:
Thanks OP. But i have already flashed LH1 via ODIN. Now i want to install CWM, can you post to link to installation instructions of CWM v6.?
Click to expand...
Click to collapse
Instructions are in his OP. I have pasted below:
7.) In Odin: Boot into download mode again and select PDA and this time select the recovery tar file (he has attached odin flashable cwm tar in the op)
8.) Uncheck F. Reset and flash
After that you will have CWM. Go to step 9 if you want to root and install SuperSU.
I already updated via Kies and of course now lost my root. If I follow this method (now, after the update) will I get root back or is there another method you guys would recommend? Thanks
#1RAGE said:
I already updated via Kies and of course now lost my root. If I follow this method (now, after the update) will I get root back or is there another method you guys would recommend? Thanks
Click to expand...
Click to collapse
You have essentially completed steps 1-5 above using Kies. Go to step 7 (6 is missing) and follow instructions to flash the CWM tar file attached in OP via ODIN and the supersu zip via CWM and you are done.
I was about to follow the video guide found in this thread: http://forum.xda-developers.com/showthread.php?t=1728824 which shows you how to root and install CWM without tripping the flash counter. Can I follow his installation instructions, but instead use the rooted stock Telus rom linked to in this thread? I assume that if i follow the guide in his thread and use the files he links to, I will end up re-flashing the stock 4.0.1 rom instead of the new 4.0.4, which I want to keep.
Plus I want to have CWM and not trip my flash counter so I dont need to bother with Triangle Away.
This is my first time rooting or flashing anything to my phone, so my apologies for my extreme n00bness. Thanks
sn0w420 said:
I was about to follow the video guide found in this thread: http://forum.xda-developers.com/showthread.php?t=1728824 which shows you how to root and install CWM without tripping the flash counter. Can I follow his installation instructions, but instead use the rooted stock Telus rom linked to in this thread? I assume that if i follow the guide in his thread and use the files he links to, I will end up re-flashing the stock 4.0.1 rom instead of the new 4.0.4, which I want to keep.
Plus I want to have CWM and not trip my flash counter so I dont need to bother with Triangle Away.
This is my first time rooting or flashing anything to my phone, so my apologies for my extreme n00bness. Thanks
Click to expand...
Click to collapse
If you use the rooted ROM in the other thread you will have that version and not the August LH1 update, remember the ones i linked are full stock firmware. Maybe someone will create a stock rooted flashable odin tar, but you really dont need it. Just flash using the above steps and use Triangle Away. Triangle Away although dangerous does no harm at all, its a simple apk file that installs like any other app, once you confirm it is displaying the correct model (our is I747M) then just hit the reset counter and let it do its thing and then you can uninstall it simple as that.
No point in waiting for someone to create a no trip counter file because that is much hard to do. Plus the only reason I think the first ones where like that was because Triangle Away did not fully support the I747M.
sn0w420 said:
I was about to follow the video guide found in this thread: http://forum.xda-developers.com/showthread.php?t=1728824 which shows you how to root and install CWM without tripping the flash counter. Can I follow his installation instructions, but instead use the rooted stock Telus rom linked to in this thread? I assume that if i follow the guide in his thread and use the files he links to, I will end up re-flashing the stock 4.0.1 rom instead of the new 4.0.4, which I want to keep.
Plus I want to have CWM and not trip my flash counter so I dont need to bother with Triangle Away.
This is my first time rooting or flashing anything to my phone, so my apologies for my extreme n00bness. Thanks
Click to expand...
Click to collapse
The thread for the no trip method referred to in that video is here. The OP in that thread is still working on root injected versions for the new Canadian firmwares, the ones currently in the OP are the old versions. He can create them quickly, I think he is just waiting for volunteers to mirror the files. Keep checking and when you see a Telus version up ending in LH1, you are good to go.
Thanks OP, that works just fine to reroot my phone and reset the trip counter!
I have a rogers Galaxy SIII if that could help anyone!
New Telus, Rogers, Bell flashable modem zip LH1
http://d-h.st/qjN
stuck on samsung screen
i did all your instructions to a t except i was using odin 3.04 and now my phone is stuck on the samsung screen i can go into dl mode and stock recovery buy no boot up can u suggest somthing for me plzz.....???
jebise101 said:
Been seeing a lot of post about how to install OTA with a rooted stock ROM. This is by far the easiest way for people to update and not lose any data. All are done using Odin 3.07 on Windows 7 and not going to link it or how to use it lots of tutorials out that show you.
To put in Download Mode -> Vol Down + Home + Power
To Boot into Recovery -> Vol Up + Home + Power
Things needed:
ROM
CWM-Recovery
Root zip file
ROMS
NOTE: These are the FULL firmware of LH1 and NOT small OTA. This is good to have as a backup should something go wrong.
Bell
Telus
Rogers
Sasktel
CWM-Recovery
See Attached, this is an Official CWM from CWM team. If you don't want to use this use whatever recovery you want or had before.
Root: MOVE THIS TO PHONE STORAGE
Chainfire SuperSU
1.) Boot into recovery and create backup, always better to backup
2.) Unzip firmware file and you will see 2 files a dll and md5. The one we need is the md5
Im with bell so mines is -> KIES_HOME_I747MVLALH1_I747MOYCALH1_20120814.100513_REV04_user_low_ship.tar.md5
3.) Put phone into download mode
4.) Load Odin select PDA and select the firmware file you unzipped in step 2. The MD5 file.
5.) Let the phone do its thing and do not touch it until you are at the lockscreen.
7.) Boot into download mode again and select PDA and this time select the recovery tar file
8.) Uncheck F. Reset and flash
9.) Once back on the lockscreen go into Recovery and install the CWM-SuperSU-v0.96.zip to root from phone storage.
10.) Get Triangle Away from here and reset counter.
Click to expand...
Click to collapse
Repeat the steps with odin 3.07?
Sent from my SGH-I747M using xda app-developers app
Repeat with odin 3.07?
Sent from my SGH-I747M using xda app-developers app
oriveradel said:
New Telus, Rogers, Bell flashable modem zip LH1
http://d-h.st/qjN
Click to expand...
Click to collapse
Anyone confirm this is a good modem to use? I'm assuming this is a cwm flashable zip right?
Sent from my SGH-I747M using xda app-developers app
---------- Post added at 04:36 PM ---------- Previous post was at 04:32 PM ----------
Nevermind. Flashed and speeds seem a lot better. I'm getting around 7mb down using h+. No LTE out here (Ancaster)
Sent from my SGH-I747M using xda app-developers app
This is my baseband version I747MVLLH1 is the flashable modem a couple posts above newer than mine?
Sent from my SGH-I747M using xda premium
A little easier guide to get root?
Hi, I made this easier a little bit. Follow the posted guide from the op
Download your FW and Odin 3.07 (and ofc sammy drivers and what not)
1.) Boot into recovery and create backup, always better to backup
2.) Unzip firmware file and you will see 2 files a dll and md5. The one we need is the md5
Im with bell so mines is -> KIES_HOME_I747MVLALH1_I747MOYCALH1_20120814.100513 _REV04_user_low_ship.tar.md5
3.) Put phone into download mode
4.) Load Odin select PDA and select the firmware file you unzipped in step 2. The MD5 file.
5.) Let the phone do its thing and do not touch it until you are at the lockscreen.
7.) Boot into download mode again and select PDA and this time select the recovery tar file
Click to expand...
Click to collapse
Then
8.) click start, wait for you to go back to lockscreen.
9.) Flash the zip attached below (through your CWM) (vol up+ power button+ home button to get to recovery)
[BOOM you have root!]
10.) get triangle away, reset flash counter.
I did not make the zip i just got it from searching around.
I rooted and installed CWM on my Sprint GS3 yesterday. I found I cannot enable wifi. I'd like to know if I flash a rom will I be able to enable wifi or should I unroot and start over again. Thanks in advance for your help!!!
can you post which recovery, rom and modem you're using. as well as the steps you took to root and install?
Did you use the toolkit? If so, just flash another kernel
Did you use the toolkit, are on 4.1.2 and root using the 4.1.1 method?
CrimSin said:
Did you use the toolkit, are on 4.1.2 and root using the 4.1.1 method?
Click to expand...
Click to collapse
4.1.2 roots the same way as 4.1.1
CNexus said:
4.1.2 roots the same way as 4.1.1
Click to expand...
Click to collapse
But with known wifi problems, according to the toolkit dev thread.
Yeah, but thats just the toolkit itself
Did you ever find a solution??
Hi,
I've rooted my phone and now wifi will not turn on, either.
First, I tried the unified toolkit method to root. It was successful, but this is where I first found wifi not working. I went back to factory install, but still had no wifi. Figuring that root was better for troubleshooting purposes, I opted to try yet a different method (from the qbking77 site at /how-to-root/root-samsung-galaxy-s-iii), which worked beautifully and I am rooted right now, but still no wifi. I used ClockWorkMod-Recovery-LTE-SGS3-v5.
Thanks!
~Jayme
ClockWorkMod-Recovery-LTE-SGS3-v5
Model#
SPH-L710
Android Version:
4.1.1
Baseband Version:
L710VPBLJ7
Kernel version:
3.0.31-CL616748
[email protected] #1
SMP PREEMPT Sat Dec 1 23:25:55 KST 2012
Build#:
JRO03L.L710VPBLJ7
Hardware Version:
L710.14
jaymethunt said:
Hi,
I've rooted my phone and now wifi will not turn on, either.
First, I tried the unified toolkit method to root. It was successful, but this is where I first found wifi not working. I went back to factory install, but still had no wifi. Figuring that root was better for troubleshooting purposes, I opted to try yet a different method (from the qbking77 site at /how-to-root/root-samsung-galaxy-s-iii), which worked beautifully and I am rooted right now, but still no wifi. I used ClockWorkMod-Recovery-LTE-SGS3-v5.
Thanks!
~Jayme
ClockWorkMod-Recovery-LTE-SGS3-v5
Model#
SPH-L710
Android Version:
4.1.1
Baseband Version:
L710VPBLJ7
Kernel version:
3.0.31-CL616748
[email protected] #1
SMP PREEMPT Sat Dec 1 23:25:55 KST 2012
Build#:
JRO03L.L710VPBLJ7
Hardware Version:
L710.14
Click to expand...
Click to collapse
Jayme stick with me on the other thread we will get you working.
Transmitted with a portable device using Xparent Blue Tapatalk 2
NEED HELP! Lost WiFi after rooting with SAMSUNG GALAXY S3 UNIFIED TOOLKIT V7.0
edfunkycold said:
Jayme stick with me on the other thread we will get you working.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
HELP!
I am having the same problem and would GREATLY appreciate some help.
I used SAMSUNG GALAXY S3 UNIFIED TOOLKIT V7.0, following MSKIP's instructions. Everything seemed to go ok, except I can no longer turn on WiFi.
MY DEVICE.............
Model# - SPH-L710
Android Version: 4.1.2
Baseband Version: L710VPBMB1
Kernel version: 3.0.31-329968
[email protected] #1 - SMP PREEMPT Tue Oct 16 22:37:51 KST 2012
Build#:JZO54K.L710VPBMB1
Hardware Version: L710.14
Why is searching so difficult.
There are many other threads about this, and the toolkit itself states that it messes up wifi.
Just flash another kernel (or rom) and you'll be good.
Did any body get a fix for this yet? What kernel do you flash to fix it?
If you use the tool kit you have to flash a Rom after rooting. For some reason it messes it up. I don't use toolkits but this is what's been said over and over.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Tedwise said:
Did any body get a fix for this yet? What kernel do you flash to fix it?
Click to expand...
Click to collapse
This. If you're not comfortable or don't know how to flash a kernel by itself yet, just flash another rom as they come with kernels built-in.
same problem here
used samsung gs3 toolkit v7.0 and selected 4.1.1 when im running MD4 firmware (i think its 4.1.2)
no wifi anymore
can someone link to the correct kernel and how to flash it so we can get wifi back?
thanks
one more thing.
so what is the correct way to flash a custom recovery with MD4?
Ok, listen very carefully.
When using the toolkit, it very often messes up your Wi-Fi. This is a known and predictable result of using it.
In order to fix Wi-Fi, all you have to do is flash a new Rom. Not a kernel, a Rom. If you want to keep your system as close to stock as possible, pick Freeza's stock rooted Rom from the Android developers section.
Hope this helps!
Sent from my SPH-L710 using xda app-developers app
topherk said:
Ok, listen very carefully.
When using the toolkit, it very often messes up your Wi-Fi. This is a known and predictable result of using it.
In order to fix Wi-Fi, all you have to do is flash a new Rom. Not a kernel, a Rom. If you want to keep your system as close to stock as possible, pick Freeza's stock rooted Rom from the Android developers section.
Hope this helps!
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
so i'm stupid and can't find freeza's stock rooted rom.
i've been looking for 1/2 an hour now
courpalais said:
so i'm stupid and can't find freeza's stock rooted rom.
i've been looking for 1/2 an hour now
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1910947
CNexus said:
http://forum.xda-developers.com/showthread.php?t=1910947
Click to expand...
Click to collapse
thanks
I've found a sure fire solution(Only if the toolkit was used)
jmlape said:
I rooted and installed CWM on my Sprint GS3 yesterday. I found I cannot enable wifi. I'd like to know if I flash a rom will I be able to enable wifi or should I unroot and start over again. Thanks in advance for your help!!!
Click to expand...
Click to collapse
Ok, I had this exact problem with my SGH-T999(T-Mobile S III), I was on 4.1.2, & used the toolkit 4.1.1 method. Next thing I knew my S3's Wifi would not turn on. Here's how I fixed it. It turns out that In the process of rooting, when you install the insecure boot on your phone, that will cause the wifi to not work. So what we want to do is make a backup of our boot.img, before hand. then restore it after the root process is complete.
If your phone is model SGH-T999 then you're in luck because you don't have to do most of this stuff, as I've already done it for you. Just Skip to the part that says "SGH-T999 4.1.2 ONLY!"
What you need:
1.) Your Galaxy S III(Not rooted)
2.) The Odin flashable CWM Recovery for your specific model
3.) Odin 3.07
Pre-fix Step.) If your phone has already undergone the root process, then you're going to need to restore the stock rom, unless you've already made a nandroid backup somehow.
Steps:
1.) (Skip to step 5 if you already have CWM Recovery Installed) Boot your phone into download mode, by powering it off then, holding VolDown+Home+Power. Once you see the prompt press VolUp, then plug your phone into your PC & leave it like that.
2.) On your PC open Odin 3.07, make sure only, Auto Reboot, & F. Reset Time are checked.
3.) Now, in Odin, click the PDA button, & navigate to your SIII Toolkit folder, once there open the recovery folder, there should be a bunch of tar files, choose the appropriate one(if your SIII is a model SGH-T999 then the file name will be something like this "recovery-cwmtouch-6.0.2.3-SGHT999.tar")
4.) After choosing the appropriate file, click start on odin, once your phone reboots you'll then have CWM Recovery on your phone.
5.) (Skip to step 7 if you already have a recent backup) Now we want to boot our phone into the new recovery mode by powering it off, then holding VolUp+Home+Power
6.) Once your phone boots into CWM Recovery, Goto "Backup and Restore", then click "Backup", proceed with the backup process, & then boot your phone normally.
7.) Now plug the phone into your PC, and navigate to the Internal memory, or external if your backed up to External SD, open the "clockworkmod" folder then the "backup" folder. Now open the folder that contains the backup that we made.) and copy the "boot.img" file to your PC where you can find it later.
8.) (Skip If you already had a backup, & have already done the root via the toolkit.) Now go ahead and follow the toolkit's rooting instructions.
9.) Now your phone is rooted, but the Wi-fi Likely won't turn on. (If it does your lucky)
10.) Now it's time to restore the original boot partition. First we want to turn that "boot.img" into "boot.tar.md5". To do that follow the tutorial here(Replacing the parts that say recovery with boot) "w0lfdroid .com/2013/04/android-how-to-convert-img-recovery-to.html"(Remove spaces)
11.) When you're done, there should be a file named "boot.tar.md5" in "C:\cygwin\home\%USER%"(%USER% is where your username should go.) If it's there your almost done, if not then you need to repeat step 10 thoroughly.
12.) Now the final step is to repeat steps 1-4, but in step three this time we want to navigate to our newly created boot.tar.md5, Instead of going to the toolkit recovery folder. After you complete these steps(AGAIN, using the boot.tar.md5, & not "recovery-cwmtouch-6.0.2.3-xxxxxxx.tar") your Wi-Fi should now work again.
SGH-T999 4.1.2 ONLY! (Any other model will be bricked by using this method):
Since you've got the same Model Phone, as well as the same Android version as me, you can take quite the shortcut. Reducing it down to only a few steps. Now Lets Start.
What you need:
1.) Your Galaxy S III(SGH-T999, with Android 4.1.2) that is experiencing this problem after rooting via toolkit.
2.) This file "https ://dl.dropboxusercontent .com/u/36653831/boot.tar.md5"(Remove Spaces)
3.) Odin 3.07
Steps:
1.) Boot your phone into download mode, by powering it off then, holding VolDown+Home+Power. Once you see the prompt press VolUp, then plug your phone into your PC & leave it like that.
2.) On your PC open Odin 3.07, make sure only, Auto Reboot, & F. Reset Time are checked.
3.) Now, in Odin, click the PDA button, & navigate to the "boot.tar.md5" you downloaded, select it, then click start. Once your phone restarts your wifi should work just fine.
Side Notes:
Let me know if this works for you.
If you use my boot.tar.md5 the you'll be getting the stock secure boot for you phone.
Note for Admins: You might want to sticky this post if people find it helpful.
Hi. I have a SGH-T999 and I have tried to install the STOCKORAMA v2 rom, which uses the AROMA installer, but it keeps giving me the status 7 error. Also in the aroma installer you can check your system info and for some reason its showing my gs3 as SCH-I535, which is the verizon version. Anyone have any idea what could be causing this. By the way when I go to about phone in my regular ROM it shows it as SGH-T999
fanatik29 said:
Hi. I have a SGH-T999 and I have tried to install the STOCKORAMA v2 rom, which uses the AROMA installer, but it keeps giving me the status 7 error. Also in the aroma installer you can check your system info and for some reason its showing my gs3 as SCH-I535, which is the verizon version. Anyone have any idea what could be causing this. By the way when I go to about phone in my regular ROM it shows it as SGH-T999
Click to expand...
Click to collapse
Is it a port? Why do you need a port now that we have 4.1.2? Use Wicked and be done with it.
I was reading for some fixes, it mentioned that I should update my boot loader to the newest one? Where would i get the latest version of the bootloader for my phone? Does this make any sense to anyone? Thanks for the replies.
re: booloaders
fanatik29 said:
I was reading for some fixes, it mentioned that I should update my boot loader to the newest one? Where would i get the latest version of the bootloader for my phone? Does this make any sense to anyone? Thanks for the replies.
Click to expand...
Click to collapse
Stay away from bootloaders unless you want to end up with a nice shiny brick..........
Even the developers do their best to stay away from bootloaders as much as possible.
The issue that you are having has nothing to do with bootloaders.
Here is a sure way to fix error 7 issues as well as other problems.
This guide will get your phone back up and running properly
Easy and sure way fix your problem - Here is s step by step guide to have a fresh start with the newest official Jellybean firmware:
This rom is the official Samsung Galaxy S3 T999 Jellybean 4.1.2 Touchwiz firmware with the benifit of being pre-rooted.
Download the newest pre-rooted Samsung Galaxy S3 T999 Jellybean v4.1.2 rom: T999_UVDMD5
After downloading make a folder on your computer's desktop and unzip the
file using Winzip or 7zip so the .TAR file is in the new folder you just made.
Download and extract Odin into the same folder you made containing the TAR file
Here is the link for Odin: http://d-h.st/Q14
Download ODIN which is required for flashing the stock rooted firmware (a windows app)
Download the Odin Flash firmware for T999 Tmobile then copy it to the same folder as Odin
Run Odin by double clicking the Odin.exe within the same folder as the TAR file you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the Firmware you downloaded (TAR file)
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache!
(It may seem to hang during boot, this is normal and you must be patient!!!)
Good Luck!
That's only for AOSP ROMs.
Aerowinder said:
That's only for AOSP ROMs.
Click to expand...
Click to collapse
The post above has NOTHING to do with AOSP/AOKP/CM10 roms.
It has all to do with Odin flashing the Samsung Jellybean 4.1.2 pre-rooted stock rom.
Hey, don't take my word for it... Check it out, click on the link and see for yourself.
This step by step is a very good way to start all over with a clean fresh start with the newest official samsung jellybean 4.1.2 rooted rom.
It's excellent for those people who are experiencing a lot of different issues, problems and difficulties .
But as I always say, everyone is entitled to their own suggestions and opinions here in these xda forums.
P.S. Does this XDA forum have a feature where we can follow users around to different threads and keep tabs on their posts?
If so let me know how to do it, it sounds like a lot of fun. LOL
^^^ You know that if you Odin the latest pre rooted rom it will update your bootloader as well?
Ps: to op, if you don't want to odin and start from scratch again check this out. Don't flash of you don't feel comfortable. I did it and it updated my bootloader with no problems.
http://forum.xda-developers.com/showthread.php?t=2282603
Sent from my SGH-T999 using xda app-developers app
I actually just figured it out, I think I had the verizon version of cwm installed on my phone so when I would try to install certain roms it would give me that error. Thank you for the replies though.
re: shiny brick
chrisram88 said:
^^^ You know that if you Odin the latest pre rooted rom it will update your bootloader as well?
Ps: to op, if you don't want to odin and start from scratch again check this out. Don't flash of you don't feel comfortable. I did it and it updated my bootloader with no problems.
http://forum.xda-developers.com/showthread.php?t=2282603
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
You are right, if all you do is flash an official stock rooted Galaxy S3 Tmobile T999 Jellybean 4.1.1 or 4.1.2 Odin flash rom
then you won't be having any problems commonly associated with flashing bootloaders at all.
But the OP of this thread was talking about and asking where he can find a "bootloader" to flash.
That's why I posted that by doing what he was asking about would be a sure way to end up with a nice shiny brick! LOL
This is a stock MI7 tmobile firmware downloaded from sammobile and rooted using URDLV.
I am uploading this to those who don't want to(or don't know to) use cygwin to generate the rooted firmware described in the root de la vega thread.
None of this is my work, All CREDITS GOES to designgears
If you follow the instructions properly, this is will not set your KNOX flag , THIS WILL NOT RESET IF IT'S ALREADY SET.
Instructions
1. Open ODIN, make sure Re-Partition is unchecked. Auto Reboot and F. Reset Time must be checked.(you can get ODIN from here http://forum.xda-developers.com/showthread.php?t=2189539)
2. Connect your phone to your PC and reboot it to the download mode(Volume Down+Home+Power keys simultaneously).
3. Once ODIN shows your device connected(ID-COM bar lit up and log says 'Added')
4. Drop the unzipped downloaded Rom( N900TUVUBMI7_N900TTMBBMI7_N900TUVUBMI7_HOME_VEGA.tar.md5 file) in the AP slot, and click start.
5. It takes a while, once its completed, device will reboot and ODIN will show 'PASS' in green.
6. Now download the root_de_la_vega_sdcard.7z file from this thread http://forum.xda-developers.com/showthread.php?p=46818366
7. Unzip it and place the contents(a root_de_la_vega.sh script file and root_files folder) in the root of your phone memory(internal storage).
7. Reboot.
8. Delete the newly added files(a root_de_la_vega.sh script file and root_files folder) and Reboot again
You are done!! , Now you are Rooted and stock.
I urge you to follow this thread http://forum.xda-developers.com/showthread.php?p=46818366 , this thread is only for those who don't have basic UNIX knowledge or don't want to install cygwin for some reason.
Download
This was tested only by me and it worked for me without any issues , no force closes or anything. My phone also came with MI7, i don't know if it will work if your phone came with a different firmware.
This is only T-Mobile NOTE 3
TRY THIS ROM AT YOUR OWN RISK , YOU ARE RESPONSIBLE FOR YOUR DEVICE
Credits
Sammobile for their ROM
designgears for the actual work
depakjan said:
This is a stock MI7 tmobile firmware downloaded from sammobile and rooted using URDLV.
I am uploading this to those who don't want to(or don't know to) use cygwin to generate the rooted firmware described in the root de la vega thread.
None of this is my work, All CREDITS GOES to designgears
If you follow the instructions properly, this is will not set your KNOX flag , THIS WILL NOT RESET IF IT'S ALREADY SET.
Instructions
1. Open ODIN, make sure Re-Partition is unchecked. Auto Reboot and F. Reset Time must be checked.(you can get ODIN from here http://forum.xda-developers.com/showthread.php?t=2189539)
2. Connect your phone to your PC and reboot it to the download mode(Volume Down+Home+Power keys simultaneously).
3. Once ODIN shows your device connected(ID-COM bar lit up and log says 'Added')
4. Drop the unzipped downloaded Rom( N900TUVUBMI7_N900TTMBBMI7_N900TUVUBMI7_HOME_VEGA.tar.md5 file) in the AP slot, and click start.
5. It takes a while, once its completed, device will reboot and ODIN will show 'PASS' in green.
6. Now download the root_de_la_vega_sdcard.7z file from this thread http://forum.xda-developers.com/showthread.php?p=46818366
7. Unzip it and place the contents(a root_de_la_vega.sh script file and root_files folder) in the root of your phone memory(internal storage).
7. Reboot.
8. Delete the newly added files(a root_de_la_vega.sh script file and root_files folder) and Reboot again
You are done!! , Now you are Rooted and stock.
I urge you to follow this thread http://forum.xda-developers.com/showthread.php?p=46818366 , this thread is only for those who don't have basic UNIX knowledge or don't want to install cygwin for some reason.
Download
This was tested only by me and it worked for me without any issues , no force closes or anything. My phone also came with MI7, i don't know if it will work if your phone came with a different firmware.
This is only T-Mobile NOTE 3
TRY THIS ROM AT YOUR OWN RISK , YOU ARE RESPONSIBLE FOR YOUR DEVICE
Credits
Sammobile for their ROM
designgears for the actual work
Click to expand...
Click to collapse
Sorry but isn't there already a thread on how to return to stock with odin?
Sent from my SM-N900T using XDA Premium 4 mobile app
mr pnut said:
Sorry but isn't there already a thread on how to return to stock with odin?
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my SM-N900T using Tapatalk
file sizes
I wonder why this stock Odin flash firmware is only approximatly 1/2 the size
of the official stock Note 3 N900T MK2 firmware found on SamMobile.com?
If all that's been done to it is root, it should be about the same size.
Thanks!
Misterjunky said:
I wonder why this stock Odin flash firmware is only approximatly 1/2 the size
of the official stock Note 3 N900T MK2 firmware found on SamMobile.com?
If all that's been done to it is root, it should be about the same size.
Thanks!
Click to expand...
Click to collapse
What N900T mk2 firmware just looked and there is only bmi7 for tmobile on there
Sent from my SM-N900T using XDA Premium 4 mobile app
mr pnut said:
Sorry but isn't there already a thread on how to return to stock with odin?
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
hay dios mio
do you guys read at all OMG READ STOCK ROOTED
re: firmware
allenjthomsen said:
What N900T mk2 firmware just looked and there is only bmi7 for tmobile on there
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You are right about bmi7 for tmobile, but I was wondering why designgear's odin flash
rooted is so much smaller than the SamMobile official stock firmware.
If designgear's is also supposed to be stock firmware it should be about the same size
as the official stock firmware at sammobile.
Size is different because its a zip file, if you unzip it will be same 1.84 gb file.
depakjan said:
This is a stock MI7 tmobile firmware downloaded from sammobile and rooted using URDLV.
I am uploading this to those who don't want to(or don't know to) use cygwin to generate the rooted firmware described in the root de la vega thread.
None of this is my work, All CREDITS GOES to designgears
If you follow the instructions properly, this is will not set your KNOX flag , THIS WILL NOT RESET IF IT'S ALREADY SET.
This was tested only by me and it worked for me without any issues , no force closes or anything. My phone also came with MI7, i don't know if it will work if your phone came with a different firmware.
This is only T-Mobile NOTE 3
TRY THIS ROM AT YOUR OWN RISK , YOU ARE RESPONSIBLE FOR YOUR DEVICE
Credits
Sammobile for their ROM
designgears for the actual work
Click to expand...
Click to collapse
My buddy just got a T-Mobile Note 3 about 4 hours ago with MI7 firmware and want to know if I would root it for him (note: he didn't care if Knox was tripped or not, not something he will ever use), so I figured I'd try the instruction you've posted here to see if would trip Knox or not.
I can say that this DOES work, Knox still at 0x0
Time to de-bloat this sucker :-]
Thanks for this...
Surprised this hasn't gained more attention...
widto08 said:
My buddy just got a T-Mobile Note 3 about 4 hours ago with MI7 firmware and want to know if I would root it for him (note: he didn't care if Knox was tripped or not, not something he will ever use), so I figured I'd try the instruction you've posted here to see if would trip Knox or not.
I can say that this DOES work, Knox still at 0x0
Time to de-bloat this sucker :-]
Thanks for this...
Surprised this hasn't gained more attention...
Click to expand...
Click to collapse
Because its not that big of a deal, i have just eliminated one step from the original method.
depakjan said:
Because its not that big of a deal, i have just eliminated one step from the original method.
Click to expand...
Click to collapse
Does this method still work not to trip your knox?
Yes it does work if you have tmobile MI7 firmware
Worked perfectly
Thanks for posting this. Worked like a charm.
depakjan said:
This is a stock MI7 tmobile firmware downloaded from sammobile and rooted using URDLV.
I am uploading this to those who don't want to(or don't know to) use cygwin to generate the rooted firmware described in the root de la vega thread.
None of this is my work, All CREDITS GOES to designgears
If you follow the instructions properly, this is will not set your KNOX flag , THIS WILL NOT RESET IF IT'S ALREADY SET.
Instructions
1. Open ODIN, make sure Re-Partition is unchecked. Auto Reboot and F. Reset Time must be checked.(you can get ODIN from here http://forum.xda-developers.com/showthread.php?t=2189539)
2. Connect your phone to your PC and reboot it to the download mode(Volume Down+Home+Power keys simultaneously).
3. Once ODIN shows your device connected(ID-COM bar lit up and log says 'Added')
4. Drop the unzipped downloaded Rom( N900TUVUBMI7_N900TTMBBMI7_N900TUVUBMI7_HOME_VEGA.tar.md5 file) in the AP slot, and click start.
5. It takes a while, once its completed, device will reboot and ODIN will show 'PASS' in green.
6. Now download the root_de_la_vega_sdcard.7z file from this thread http://forum.xda-developers.com/showthread.php?p=46818366
7. Unzip it and place the contents(a root_de_la_vega.sh script file and root_files folder) in the root of your phone memory(internal storage).
7. Reboot.
8. Delete the newly added files(a root_de_la_vega.sh script file and root_files folder) and Reboot again
You are done!! , Now you are Rooted and stock.
I urge you to follow this thread http://forum.xda-developers.com/showthread.php?p=46818366 , this thread is only for those who don't have basic UNIX knowledge or don't want to install cygwin for some reason.
Download
This was tested only by me and it worked for me without any issues , no force closes or anything. My phone also came with MI7, i don't know if it will work if your phone came with a different firmware.
This is only T-Mobile NOTE 3
TRY THIS ROM AT YOUR OWN RISK , YOU ARE RESPONSIBLE FOR YOUR DEVICE
Credits
Sammobile for their ROM
designgears for the actual work
Click to expand...
Click to collapse
Is this supposed to be an .exe?
phatkid01 said:
Is this supposed to be an .exe?
Click to expand...
Click to collapse
Only thing I'm seeing is a small MD5 contained in an .exe file. Any other links to the full archive?
Thank u! Gunna need this soon when we get kitkat!
Sent from my ZeroLemon Powered Galaxy Note 3
It worked for me when I tried from phone, tried first on pc.
thunderstruck! said:
Only thing I'm seeing is a small MD5 contained in an .exe file. Any other links to the full archive?
Click to expand...
Click to collapse
Don't select this box
I was able to locate a copy of the file via Google and flashed it last night, then rooted. Got that done so then I used my Google backup to restore my phone. Is there any real harm in flashing back to the stock version then going back to rooted later, as long as I haven't done any system updates? I ask because Isis still complains about being rooted, and it was a PITA to get it working on my VZ Note 2. Since I can't nandroid back and forth between roms like on the Note 2, I have to use Odin and flash firmware. They have to make such a production out of it-I miss fastboot and flashing ROM's till all hours of the morning!
thunderstruck! said:
I was able to locate a copy of the file via Google and flashed it last night, then rooted. Got that done so then I used my Google backup to restore my phone. Is there any real harm in flashing back to the stock version then going back to rooted later, as long as I haven't done any system updates? I ask because Isis still complains about being rooted, and it was a PITA to get it working on my VZ Note 2. Since I can't nandroid back and forth between roms like on the Note 2, I have to use Odin and flash firmware. They have to make such a production out of it-I miss fastboot and flashing ROM's till all hours of the morning!
Click to expand...
Click to collapse
Do you know what xposed framework is? There's a root cloak module for it. .. for your question. There's no harm . Just odin the stock rom then root down the road. .
Sent from my SM-N9005 using Tapatalk
I'm new to making modifications on my phone and I need some help deodexing the ROM.
I've got a Note 4 from Sprint running Android 5.01. I've installed TWRP and made a backup. I've also downloaded the version of Xposed that I want to get installed. But when I tried to flash Xposed to the phone, I got a message that a deodexed ROM was required.
I know that Titanium Backup can be used to deodex apps but it doesn't work with the framework. Is there a tool or app that anyone can recommend to me for this? Or is there a deodexed version of Samsung's stock ROM that I can easily swap out with the existing ROM?
Any help would be much appreciated.
Android 5.0.1 does require deodexed ROM and this thread should help you or you could try Tickle My Android by ticklefish on XDA to deodex ROM. Google that one but here's the thread for the Xposed you're looking for (Android 5.0 only).
https://forum.xda-developers.com/showpost.php?p=60857320&postcount=1
That may help but I'd recommend either KitKat or Lollipop 5.1 or higher so you could use the Odex stock ROM or custom ROM- Odexed or deodexed. KitKat uses the standard rovo89 Xposed framework for KitKat. Lollipop 5.1 and Marshmallow uses Wanam unofficial Xposed framework; it works for both Odexed and deodexed ROMs though it didn't always when I used it on Lollipop but updates allow for better with Odexed ROMs when adding system apps.
You'd have to provide bootloader version to advise which path to take. Maybe your bootloader is OB7 and you've read warning about updating bootloader past that prohibits using KitKat or Android 5.0.1 again but there are methods that make it possible with the updated bootloader and Android 5.1 kernel but not degradable with Odin.
But IMO, Android 5.0.1 is not a good place to be. Android OS updates are notably benching faster so there's that but others prefer KitKat for simplicity and theme flexibility but less secure. Android 5.0.1 is neither of those and less secure. I'd consider KitKat or higher update but not settle for Android 5.0.1
You can use Galaxy Tools or this app to get your bootloader version.
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
But you may want to get your MSL number before updating if you can't get it from Sprint. Sprint will give it to you if you're a Sprint customer with phone paid in full and good standing on account. But I'd get it before updating anyway if you don't have it already.
Sent from my SM-N920P using Tapatalk
Thank you and some additional questions
samep said:
Android 5.0.1 does require deodexed ROM and this thread should help you or you could try Tickle My Android by ticklefish on XDA to deodex ROM. Google that one but here's the thread for the Xposed you're looking for (Android 5.0 only).
https://forum.xda-developers.com/showpost.php?p=60857320&postcount=1
That may help but I'd recommend either KitKat or Lollipop 5.1 or higher so you could use the Odex stock ROM or custom ROM- Odexed or deodexed. KitKat uses the standard rovo89 Xposed framework for KitKat. Lollipop 5.1 and Marshmallow uses Wanam unofficial Xposed framework; it works for both Odexed and deodexed ROMs though it didn't always when I used it on Lollipop but updates allow for better with Odexed ROMs when adding system apps.
You'd have to provide bootloader version to advise which path to take. Maybe your bootloader is OB7 and you've read warning about updating bootloader past that prohibits using KitKat or Android 5.0.1 again but there are methods that make it possible with the updated bootloader and Android 5.1 kernel but not degradable with Odin.
But IMO, Android 5.0.1 is not a good place to be. Android OS updates are notably benching faster so there's that but others prefer KitKat for simplicity and theme flexibility but less secure. Android 5.0.1 is neither of those and less secure. I'd consider KitKat or higher update but not settle for Android 5.0.1
You can use Galaxy Tools or this app to get your bootloader version.
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
But you may want to get your MSL number before updating if you can't get it from Sprint. Sprint will give it to you if you're a Sprint customer with phone paid in full and good standing on account. But I'd get it before updating anyway if you don't have it already.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Thank you for all of the information. It sounds like I should probably upgrade to Android 5.1. I'm not sure how I would go about doing that though. Can you point me in the right direction? Is there a guide to do this somewhere? My bootloader version is N910PVPU2BOE1.
jmalmberg said:
Thank you for all of the information. It sounds like I should probably upgrade to Android 5.1. I'm not sure how I would go about doing that though. Can you point me in the right direction? Is there a guide to do this somewhere? My bootloader version is N910PVPU2BOE1.
Click to expand...
Click to collapse
You can upgrade through Odin. There's a stock tar thread here with Odin download link and simplified instructions.
https://forum.xda-developers.com/showthread.php?p=63868221
If you're looking for a custom ROM, decide which ROM, check its update version and follow OP install instructions for flashing help and advice. Get the tar from thread above; it has older versions too.
If you're interested in a Lollipop custom ROM, check out the Note 5 Ultimate ports by tx_dbs_tx to see if they will work for you. Those require stock tar OK1 version and have detailed install instructions that should be followed, if interested.
You're gonna want to stop auto updates immediately after updating and also after flashing custom ROM to avoid update download and nags to update.
Sent from my SM-N920P using Tapatalk
samep said:
You can upgrade through Odin. There's a stock tar thread here with Odin download link and simplified instructions.
https://forum.xda-developers.com/showthread.php?p=63868221
If you're looking for a custom ROM, decide which ROM, check its update version and follow OP install instructions for flashing help and advice. Get the tar from thread above; it has older versions too.
If you're interested in a Lollipop custom ROM, check out the Note 5 Ultimate ports by tx_dbs_tx to see if they will work for you. Those require stock tar OK1 version and have detailed install instructions that should be followed, if interested.
You're gonna want to stop auto updates immediately after updating and also after flashing custom ROM to avoid update download and nags to update.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Thank you for this. I've downloaded Odin but have a couple of additional questions. First, I only see two files with Odin. A .exe and a .ini file. Is that correct?
Second, does is matter which one of the MD5 files I download and flash over or will any of them work for me? Are there any that you consider to be better than the others?
jmalmberg said:
Thank you for this. I've downloaded Odin but have a couple of additional questions. First, I only see two files with Odin. A .exe and a .ini file. Is that correct?
Second, does is matter which one of the MD5 files I download and flash over or will any of them work for me? Are there any that you consider to be better than the others?
Click to expand...
Click to collapse
The .exe is an executable to launch Odin. Place the unzipped contents in an Odin folder or whatever you name it. I prefer to have Odin in my stock tar folder along with TWRP so it easily finds those to load and flash. Grab this img.tar for Odin flash of TWRP:
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Be aware that TWRP recovery flash requires you to uncheck Odin option of auto reboot and wait for flash to finish but make sure you see COM added in highlighted field before starting. Upon success, remove USB cable and battery and wait at least 30 seconds and boot into recovery. If you fail to boot into recovery on initial boot after TWRP flash, the stock recovery will restore itself and you won't see TWRP later when booting recovery.
Be aware that Odin flashing tar files will utilize the AP slot to load and flash. Stock tar will take a while to check the md5 so wait until you see you see your device added as COM in the Odin log and highlighted field before you start a flash, particularly stock tar; expect a wait period for md5 verification.
The stock tar you choose would depend on the ROM you choose. I don't know your preference but for Odin, you should limit your choices from OG5 and up to latest. You can downgrade to lollipop or upgrade to marshmallow at will but in your case, I think either is an upgrade for you.
Lots of choices so pick one and look in OP for what update it's based on. Then you'll know which update to download.
I only suggested the Note 5 Ultimate ports because you mentioned lollipop. The ROM is stable but read the OP and see if that's what you want. Custom ROMs usually give a list of broken features and install directions to consider complexity of install and setup and result to expect.
There's also stock ROMs or Cyanogen Mod (CM) ROMs. Each have their own appeal and following.
There is a marshmallow port based on Note7 but the degree of difficulty is higher. There's fix workarounds that may require extra steps and experience that you either have or will learn along the way and glean from searching thread. Up to you what to choose but backup stock first, once you Odin and get TWRP and then backup any ROM you like if seeking alternatives.
Sent from my SM-N920P using Tapatalk
samep said:
The .exe is an executable to launch Odin. Place the unzipped contents in an Odin folder or whatever you name it. I prefer to have Odin in my stock tar folder along with TWRP so it easily finds those to load and flash. Grab this img.tar for Odin flash of TWRP:
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Be aware that TWRP recovery flash requires you to uncheck Odin option of auto reboot and wait for flash to finish but make sure you see COM added in highlighted field before starting. Upon success, remove USB cable and battery and wait at least 30 seconds and boot into recovery. If you fail to boot into recovery on initial boot after TWRP flash, the stock recovery will restore itself and you won't see TWRP later when booting recovery.
Be aware that Odin flashing tar files will utilize the AP slot to load and flash. Stock tar will take a while to check the md5 so wait until you see you see your device added as COM in the Odin log and highlighted field before you start a flash, particularly stock tar; expect a wait period for md5 verification.
The stock tar you choose would depend on the ROM you choose. I don't know your preference but for Odin, you should limit your choices from OG5 and up to latest. You can downgrade to lollipop or upgrade to marshmallow at will but in your case, I think either is an upgrade for you.
Lots of choices so pick one and look in OP for what update it's based on. Then you'll know which update to download.
I only suggested the Note 5 Ultimate ports because you mentioned lollipop. The ROM is stable but read the OP and see if that's what you want. Custom ROMs usually give a list of broken features and install directions to consider complexity of install and setup and result to expect.
There's also stock ROMs or Cyanogen Mod (CM) ROMs. Each have their own appeal and following.
There is a marshmallow port based on Note7 but the degree of difficulty is higher. There's fix workarounds that may require extra steps and experience that you either have or will learn along the way and glean from searching thread. Up to you what to choose but backup stock first, once you Odin and get TWRP and then backup any ROM you like if seeking alternatives.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Since this is my first time doing this, I think I want to keep it as simple as possible. So I'm going to stick with lollipop. The version that I'm thinking of using is:
OJ6 Lollipop TAR: N910PVPU4COJ6_N910PSPT4COJ6_SPR.zip
md5: 13ab3afb59130382b2ce0f9113a193a8
I've opened Odin, put the phone into download mode and attached it. Odin can see the phone but I haven't tried to do anything yet. Sorry to pepper you with questions but I really don't want to brick my phone, so here are a few more.
1. When I flash the new ROM, will my phone still be rooted or will I need to do that again?
2. If I don't repartition the phone, will my data and apps still be there when I reboot?
3. If this doesn't work, can I restore my old system using a backup that I made with TWRP?
Thanks again for the assistance. I really appreciate it.
jmalmberg said:
Since this is my first time doing this, I think I want to keep it as simple as possible. So I'm going to stick with lollipop. The version that I'm thinking of using is:
OJ6 Lollipop TAR: N910PVPU4COJ6_N910PSPT4COJ6_SPR.zip
md5: 13ab3afb59130382b2ce0f9113a193a8
I've opened Odin, put the phone into download mode and attached it. Odin can see the phone but I haven't tried to do anything yet. Sorry to pepper you with questions but I really don't want to brick my phone, so here are a few more.
1. When I flash the new ROM, will my phone still be rooted or will I need to do that again?
2. If I don't repartition the phone, will my data and apps still be there when I reboot?
3. If this doesn't work, can I restore my old system using a backup that I made with TWRP?
Thanks again for the assistance. I really appreciate it.
Click to expand...
Click to collapse
Repartition should only be used if there's a problem. Like I said, use the Odin defaults for stock tar.
Stock tar is factory firmware so yes, you must root again. Think of it as out of the box stock but your data and user apps should remain. No guarantee so you should backup to extSdCard but you never really know if the internal memory gets wiped or not. Usually not for those running touchwiz ROMs.
You could restore the backup but if the flash takes then there may be some compatibility issues.
It's often recommended to clean install ROMs for best compatibility so that's up to you if you want to risk keeping your user apps and data on there. You can expect longer boots to optimize the apps but consider the stock tar would boot right up, if installed cleanly.
Custom ROMs will have to optimize applications. If you're also keeping the user apps, they'll have to be optimized again so that makes the initial boot even longer. You should consider cooling with forced air for these initial boots and have ample charge. I recommend 80% or more.
Sent from my SM-N920P using Tapatalk
samep said:
Repartition should only be used if there's a problem. Like I said, use the Odin defaults for stock tar.
Stock tar is factory firmware so yes, you must root again. Think of it as out of the box stock but your data and user apps should remain. No guarantee so you should backup to extSdCard but you never really know if the internal memory gets wiped or not. Usually not for those running touchwiz ROMs.
You could restore the backup but if the flash takes then there may be some compatibility issues.
It's often recommended to clean install ROMs for best compatibility so that's up to you if you want to risk keeping your user apps and data on there. You can expect longer boots to optimize the apps but consider the stock tar would boot right up, if installed cleanly.
Custom ROMs will have to optimize applications. If you're also keeping the user apps, they'll have to be optimized again so that makes the initial boot even longer. You should consider cooling with forced air for these initial boots and have ample charge. I recommend 80% or more.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
OK, I think I'm ready to try this. Just want to make sure I've dotted all the "i"s and crossed all the "t"s.
Can you confirm the following procedures for me.
I've removed most of my apps to make the process go a little more smoothly. I've downloaded the ROM I want to flash. When I open Odin 3.12.3 and connect my phone, under Options, I remove the check mark by auto reboot and leave the box checked by F. Reset Time. Everything else under options is unchecked. Then to the right, I check the box next to the AP button and select the TAR for the ROM. I leave everything else alone. Is that correct?
I'm not sure what to do with the TWRP TAR file you had me download. Do I place that in one of the other boxes?
After that, I select start and wait for it to complete. Is there anything else I should know?
Thank you for your help on this.
jmalmberg said:
OK, I think I'm ready to try this. Just want to make sure I've dotted all the "i"s and crossed all the "t"s.
Can you confirm the following procedures for me.
I've removed most of my apps to make the process go a little more smoothly. I've downloaded the ROM I want to flash. When I open Odin 3.12.3 and connect my phone, under Options, I remove the check mark by auto reboot and leave the box checked by F. Reset Time. Everything else under options is unchecked. Then to the right, I check the box next to the AP button and select the TAR for the ROM. I leave everything else alone. Is that correct?
I'm not sure what to do with the TWRP TAR file you had me download. Do I place that in one of the other boxes?
After that, I select start and wait for it to complete. Is there anything else I should know?
Thank you for your help on this.
Click to expand...
Click to collapse
You'll do two flashes with Odin in order to get to update required with Odin defaults, you flash the stock tar and let it auto boot. Close Odin when done.
Flashing TWRP requires the auto reboot unchecked because you need to boot into recovery on first boot after flashing TWRP.
Both are flashed in AP slot on separate Odin sessions because they're tar files. You'll need to Odin TWRP and root again after flashing a stock tar. For custom ROMs, consider the ROM zip is already pre-rooted so all you need is TWRP.
Unless you want to root stock, I'll leave that part out of this post.
Sent from my SM-N920P using Tapatalk
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
Do you have the USB driver for Note 4 installed on PC? If not, goto Samsung support and get the one for Note 4 from the download section.
Sent from my SM-N920P using Tapatalk
samep said:
You'll do two flashes with Odin in order to get to update required with Odin defaults, you flash the stock tar and let it auto boot. Close Odin when done.
Flashing TWRP requires the auto reboot unchecked because you need to boot into recovery on first boot after flashing TWRP.
Both are flashed in AP slot on separate Odin sessions because they're tar files. You'll need to Odin TWRP and root again after flashing a stock tar. For custom ROMs, consider the ROM zip is already pre-rooted so all you need is TWRP.
Unless you want to root stock, I'll leave that part out of this post.
Sent from my SM-N920P using Tapatalk
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
Do you have the USB driver for Note 4 installed on PC? If not, goto Samsung support and get the one for Note 4 from the download section.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I was able to flash the ROM to the phone without any real issues. Thank you for your help on that. I wouldn't have got that done without your assistance and I really appreciate it.
After I was finished with the ROM, I used CF Auto Root to reroot the phone and then I tried to flash TWRP recovery. I'm having issues with TWRP.
I closed Odin and they reopened it as an administrator. When I click on the button next to the AP slot, it opens a file window. At that point I clicked on the extracted TWRP .tar file you had me download. The program just seems to hang and never actually shows up in the box next to the AP button. Any suggestions?
jmalmberg said:
I was able to flash the ROM to the phone without any real issues. Thank you for your help on that. I wouldn't have got that done without your assistance and I really appreciate it.
After I was finished with the ROM, I used CF Auto Root to reroot the phone and then I tried to flash TWRP recovery. I'm having issues with TWRP.
I closed Odin and they reopened it as an administrator. When I click on the button next to the AP slot, it opens a file window. At that point I clicked on the extracted TWRP .tar file you had me download. The program just seems to hang and never actually shows up in the box next to the AP button. Any suggestions?
Click to expand...
Click to collapse
You shouldn't unzip or extract img.tar files but flash as downloaded. If it had a .zip extension, yes, but as I recall, it's not zipped nor need extracting.
It's already a tar file for flashing. Tricky annotation but I think it just means that it's been converted from .img to .tar and ready for Odin. I think only TWRP does that extension naming.
Hopefully, it's only hanging because Odin or phone doesn't know what to do with it. Pull battery and check that it still boots recovery and system. Then back to download mode to Odin without extracting img.tar file.
I guess if you extract properly, you're left with an image file but I wouldn't do it by extraction because you can download image files from TWRP without needing to convert. Just so you know, those .img files can be flashed in TWRP recovery to update whenever that happens again.
Sent from my SM-N920P using Tapatalk
samep said:
You shouldn't unzip or extract img.tar files but flash as downloaded. If it had a .zip extension, yes, but as I recall, it's not zipped nor need extracting.
It's already a tar file for flashing. Tricky annotation but I think it just means that it's been converted from .img to .tar and ready for Odin. I think only TWRP does that extension naming.
Hopefully, it's only hanging because Odin or phone doesn't know what to do with it. Pull battery and check that it still boots recovery and system. Then back to download mode to Odin without extracting img.tar file.
I guess if you extract properly, you're left with an image file but I wouldn't do it by extraction because you can download image files from TWRP without needing to convert. Just so you know, those .img files can be flashed in TWRP recovery to update whenever that happens again.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Thank you! It worked.
jmalmberg said:
Thank you! It worked.
Click to expand...
Click to collapse
Now, hopefully you have ROM picked out and on extSdCard ready to flash.
I'd backup stock ROM to extSdCard in TWRP just in case.
Follow the OP on your ROM install. Enjoy!
Sent from my SM-N920P using Tapatalk