Related
I can't fine a forum for the T-Mobile Galaxy S2, so I'm posting this here.
I'm having problems completing a firmware upgrade on my wife's Galaxy S2. It's at ICS and I want to get it to Jelly Bean. We're using the horrible Samsung program Kies, which is hosting the update to us. It sees the S2 fine... No problems there. Every time I perform the update, it downloads the firmware and when it reboots the phone, I get an error that the device can't be found and I should try again. When I go in device manager I see an exclamation point on Samsung Mobile USB CDC composite device and it says the device couldn't be started.
I've checked that I have the most current drivers, which I do. I've uninstalled then and reinstalled them and uninstalled Kies and reinstalled Kies and still get the error. I've also already updated the firmware on my Galaxy S3 using Kies on this computer and it worked fine. Now when I do it on my wife's S2, it bombs.
I then loaded Kies on another laptop and it's even worse. It downloads the firmware update and the entire application totally crashes.
I've gone to T-Mobile and they can't help with anything. They suggested turning USB Debugging on in the Developer Options on the phone, which I did. Still, nothing.
I located the hooks in the registry editor for the CDC composite device driver and everything *looks* good, as far as I can tell. I just don't know what to do.
Can anyone provide any advice or help? I've sent about 11 hours on this over two days and I'm running out of ideas.
-Paul
Sticker on the phone chassis under the battery; what does it say ? I think your question probably belongs here but we'll check just to be sure.
MistahBungle said:
Sticker on the phone chassis under the battery; what does it say ? I think your question probably belongs here but we'll check just to be sure.
Click to expand...
Click to collapse
Model is SGH-T989,,.
-Paul
Just as I suspected. I've asked mods to move your thread to T-Mobile Q&A I linked to in my previous post.
I'm having problems completing a firmware upgrade on my wife's Galaxy S2. It's at ICS and I want to get it to Jelly Bean. We're using the horrible Samsung program Kies, which is hosting the update to us. It sees the S2 fine... No problems there. It identifies the phone and tells us there's a newer firmware version we can download. Every time I perform the update, it downloads the firmware and when it reboots the phone, I get an error that the device can't be found and I should try again. When I go in device manager, I see an exclamation point on Samsung Mobile USB CDC Composite Device and it says the device couldn't be started.
It looks as thought, when the phone reboots to download the firmware from the laptop after the laptop has the firmware, Kies isn't seeing the phone. So I did vol-up-down to get it in programming mode and then reinitiated the download. That little trick doesn't work since Kies isn't identifying the device.
I've checked that I have the most current drivers, which I do. I've uninstalled them and reinstalled them and uninstalled Kies and reinstalled Kies and still get the error. I've also already updated the firmware on my Galaxy S3 using Kies on this computer and it worked fine. Now when I do it on my wife's S2, it bombs.
I then loaded Kies on another laptop and it's even worse. It downloads the firmware update and the entire application totally crashes.
I've gone to T-Mobile and they can't help with anything. They suggested turning USB Debugging on in the Developer Options on the phone, which I did. Still, nothing.
I located the hooks in the registry editor for the CDC composite device driver and everything *looks* good, as far as I can tell. Driver is dated 1/23/2013. As I said, it updated the firmware on my S3 fine... It just won't do it on my wife's S2. I don't know what to do.
Can anyone provide any advice or help? I've spent about 11 hours on this over two days and am running out of ideas.
-Paul
premington said:
I'm having problems completing a firmware upgrade on my wife's Galaxy S2. It's at ICS and I want to get it to Jelly Bean. We're using the horrible Samsung program Kies, which is hosting the update to us. It sees the S2 fine... No problems there. It identifies the phone and tells us there's a newer firmware version we can download. Every time I perform the update, it downloads the firmware and when it reboots the phone, I get an error that the device can't be found and I should try again. When I go in device manager, I see an exclamation point on Samsung Mobile USB CDC Composite Device and it says the device couldn't be started.
It looks as thought, when the phone reboots to download the firmware from the laptop after the laptop has the firmware, Kies isn't seeing the phone. So I did vol-up-down to get it in programming mode and then reinitiated the download. That little trick doesn't work since Kies isn't identifying the device.
I've checked that I have the most current drivers, which I do. I've uninstalled them and reinstalled them and uninstalled Kies and reinstalled Kies and still get the error. I've also already updated the firmware on my Galaxy S3 using Kies on this computer and it worked fine. Now when I do it on my wife's S2, it bombs.
I then loaded Kies on another laptop and it's even worse. It downloads the firmware update and the entire application totally crashes.
I've gone to T-Mobile and they can't help with anything. They suggested turning USB Debugging on in the Developer Options on the phone, which I did. Still, nothing.
I located the hooks in the registry editor for the CDC composite device driver and everything *looks* good, as far as I can tell. Driver is dated 1/23/2013. As I said, it updated the firmware on my S3 fine... It just won't do it on my wife's S2. I don't know what to do.
Can anyone provide any advice or help? I've spent about 11 hours on this over two days and am running out of ideas.
-Paul
Click to expand...
Click to collapse
First u got check USB debugging ON (on the phone)
disable anti virus on the pc/laptop
kies will put your phone into download mode and will take awhile (Kies is super slow) for good reasons
Also consider rooting your phone and install custom recovery (CWM) and flash all the rom(s) you wish [if that's an option]
hit Thanks if i helped
Thanks for the help, Sam.
I'll try it again with the virus protection off. I disabled the Windows firewall and that did nothing. I've tried it about 12 to 15 times, which takes a long time because Kies takes so long to download what it needs.
Can I root a T-Mobile phone? I used to have a Motorola Atrix 2 and rooted that and did manual firmware and ROM upgrades, but that was an unlocked and rooted phone. I'm afraid I may screw up the phone or my T-Mobile service by rooting it and doing custom installs. Does anyone have experience with this on a T-Mobile phone they purchased at T-Mobile? I don't want to mess the phone up.
At this point, I think that's the only way I'm going to go Jelly Bean on my wife's phone.
-Paul
Rooting your s2 is simple and easy to do. Go to the dev section and look at the threads on how to do it.
You will use Odin to flash a custom recovery such a TWRP whick will install supersu. At that point you can flash the ROM of your choice and not have to deal with Kies anymore.
Hope this helps
Sent from my SAMSUNG-SGH-T989 using xda premium
use this as a ref. http://galaxys2root.com/galaxy-s2-root/how-to-root-t-mobile-galaxy-s2-sgh-t989/
make sure to backup your current ROM as soon as your get root& cwm
after that u can flash any rom here is a list :http://www.androidmodmarket.com/ModMarket/Devices/Device-XDA-F-1332.html
i think u will like a clean fast 4.2.2 (jb) rom like slimbean....
try 'em & see which one u like......xda is your best bet for help & just about anything ROM
hit thanks if u like
sam.balia1012 said:
use this as a ref. http://galaxys2root.com/galaxy-s2-root/how-to-root-t-mobile-galaxy-s2-sgh-t989/
make sure to backup your current ROM as soon as your get root& cwm
after that u can flash any rom here is a list :http://www.androidmodmarket.com/ModMarket/Devices/Device-XDA-F-1332.html
i think u will like a clean fast 4.2.2 (jb) rom like slimbean....
try 'em & see which one u like......xda is your best bet for help & just about anything ROM
hit thanks if u like
Click to expand...
Click to collapse
This is all great information... Thanks so much. I've pressed "Thanks" to each of you. :good:
-Paul
I recently formatted my computer to change it from Windows 8 back to 7 and now when I install Kies or Samsung drivers, they both pick my phone up as a Galaxy Nexus. I have tried redownloading and reinstalling the drivers but it still turns out the same. Any ideas? Thanks in advance.
scream_clarity said:
I recently formatted my computer to change it from Windows 8 back to 7 and now when I install Kies or Samsung drivers, they both pick my phone up as a Galaxy Nexus. I have tried redownloading and reinstalling the drivers but it still turns out the same. Any ideas? Thanks in advance.
Click to expand...
Click to collapse
What rom are you running? Some of them just display the default samsung android phone aka the Nexus
scream_clarity said:
I recently formatted my computer to change it from Windows 8 back to 7 and now when I install Kies or Samsung drivers, they both pick my phone up as a Galaxy Nexus. I have tried redownloading and reinstalling the drivers but it still turns out the same. Any ideas? Thanks in advance.
Click to expand...
Click to collapse
Are you also uninstalling the Nexus device from device manager?
mrevankyle said:
What rom are you running? Some of them just display the default samsung android phone aka the Nexus
Click to expand...
Click to collapse
Mine ALWAYS displays SGH-I317
Sent from my Note 2 running MEAN MUTHA F'N BEAN????
roll back driver
you got one of few issues.
1. Your not the installed admin user on your computer. (each manufacture puts a Hidden Admin account on each computer) its a Dell or Hp etc thing not a Microsoft issue.
To become hidden admin (do this step last if no others work)
2. You need to roll back your drivers and install the ones from the Phone NOT the ones from Windows. So to roll back to starting position or delete them go to this Guide here for Rollback
Next you need to Keep windows from grabbing the Samsung drivers from Windows which can be the issue
Go here for help if you don't know how to do this
3. You need to uninstall and the drivers for the phone, and download the new drivers from Samsung and/or delete the drivers and ALLOW the phone to install them only
To do this go HERE
This above link is to delete the old USB drivers. IT WILL DELETE MOST OF THEM, dont worry the devices will auto load when you put them back into the computer.
IF 2 or 3 DONT work then do step one. Between each step do a rest, and keep all devices of USB unplugged.
Good luck
softballjunkee13 said:
Mine ALWAYS displays SGH-I317
Sent from my Note 2 running MEAN MUTHA F'N BEAN????
Click to expand...
Click to collapse
I was just thinking back to my Captivate days where a lot of roms were ports from the Nexus S and it would often display that when plugged into computers and my brothers S2 would often display as a G Nexus when plugged into a lot of computers
Credit to @roustabout for providing @Chainfire with the stock recovery. And to @blulite for monitoring the CF thread for the release of CF Auto-Root.
NOTE #1: This procedure WILL trip the Knox flag.
NOTE #2: It is advisable that you do not connect your Tab Pro 8.4 to your computer until reaching Step 7.
STEP 1
Download Samsung USB Driver for Mobile Phones (Windows Only):
Softpedia
Samsung's Website (you'll have to search a generic device, like Galaxy S4, in order to find the driver)
OR
Install Kies:
http://content.samsung.com/us/contents/aboutn/kiesIntro.do
STEP 2
Tab 8.4 Download CF Auto-Root (8.4)
Tab 10.1 Download CF Auto-Root (10.1)
STEP 3
Extract files to a folder on your desktop, open newly created folder, run Odin.
STEP 4
In Odin, for the Tab 8.4, choose "PDA" and select the file "CF-Auto-Root-mondrianwifi-mondrianwifixx-smt320.tar.md5" (included in the CF Auto-Root zip)
For the Tab 10.1, choose "PDA" and select the file "CF-Auto-Root-picassowifi-picassowifixx-smt520.tar.md5" (included in the CF Auto-Root zip)
STEP 5
Power off your Tab.
STEP 6
On your Tab, hold the Power and Volume Down buttons until you see a "Warning!!" screen with a large yellow triangle at the bottom. Press Volume Up to continue.
STEP 7
Connect your Tab to your computer using the supplied USB cable.
Your computer should now automatically install the appropriate drivers for use in the Tab's "Download Mode".
STEP 8
In Odin, verify that your Tab is connected to a COM port (yellow box with text "COM x" where "x" is a number)
STEP 9
In Odin, press "Start"
FINISHING UP
Upon a successful flash, Odin will display "PASS" and your Tab will reboot.
You can expect to have to disable Knox, and SuperUser should prompt you to do this.
Be sure to thank @Chainfire; he's an amazing contributor to all that is Android.
leatherneck6017 said:
Credit to @roustabout for providing @Chainfire with the stock recovery. And to @blulite for monitoring the CF thread for the release of CF Auto-Root.
NOTE: It is advisable that you do not connect your Tab Pro 8.4 to your computer until reaching Step 7.
STEP 1
Download Samsung USB Driver for Mobile Phones (Windows Only):
http://forum.xda-developers.com/showthread.php?t=2038555
OR
Install Kies:
http://kies.samsung.com/
STEP 2
Download CF Auto-Root (link is at the bottom of the page)
STEP 3
Extract files to your desktop and run "Odin3-v1.85.exe"
STEP 4
In Odin, choose "PDA" and select "CF-Auto-Root-mondrianwifi-mondrianwifixx-smt320.tar.md5" (it was included in the CF Auto-Root zip)
STEP 5
Power off your Tab.
STEP 6
On your Tab, hold the Power and Volume Down buttons until you see a "Warning!!" screen with a large yellow triangle at the bottom. Press Volume Up to continue.
STEP 7
Connect your Tab to your computer using the supplied USB cable.
Your computer should now automatically install the appropriate drivers for use in the Tab's "Download Mode".
STEP 8
In Odin, verify that your Tab is connected to a COM port (yellow box with text "COM x" where "x" is a number)
STEP 9
In Odin, press "Start"
FINISHING UP
Upon a successful flash, Odin will display "PASS" and your Tab will reboot.
You can expect to have to disable Knox, and SuperUser should prompt you to do this.
Be sure to thank @Chainfire; he's an amazing contributor to all that is Android.
Click to expand...
Click to collapse
The link on that thread for the usb drivers has been deleted, and the kies site isn't loading.
scottharris4 said:
The link on that thread for the usb drivers has been deleted, and the kies site isn't loading.
Click to expand...
Click to collapse
Thanks. Updated OP.
leatherneck6017 said:
Thanks. Updated OP.
Click to expand...
Click to collapse
Thanks, and does this delete anything on my device when I root like it did on the Nexus 7 and Nexus 4?
scottharris4 said:
Thanks, and does this delete anything on my device when I root like it did on the Nexus 7 and Nexus 4?
Click to expand...
Click to collapse
No.
leatherneck6017 said:
No.
Click to expand...
Click to collapse
Awesome. I'll have to try this soon, sometime when I have the time to fix it if I screw up somehow!
leatherneck6017 said:
.....
STEP 1
Download Samsung USB Driver for Mobile Phones (Windows Only):
Click to expand...
Click to collapse
Erm.. latest Samsung USB Drivers are linked to on this very site...
SAMSUNG USB Drivers for Mobile Phones (x86 & x64) v1.5.33.0
SuperUser hasn't asked me to disable Knox. How do I do it manually?
Thanks for the detailed instructions for rooting. I do have a question as a newbie, if it's okay.
If I root my Tab Pro 8.4, can I still use Comixology and Zinio accounts? If yes, can I use the SD card as the main installation for Comixology and Zinio since I have lots of digital comics and magazines I would like to download.
Will this root work on the 10.1?
Sent from my SM-T520 using XDA Premium 4 mobile app
davidn11 said:
Thanks for the detailed instructions for rooting. I do have a question as a newbie, if it's okay.
If I root my Tab Pro 8.4, can I still use Comixology and Zinio accounts? If yes, can I use the SD card as the main installation for Comixology and Zinio since I have lots of digital comics and magazines I would like to download.
Click to expand...
Click to collapse
Rooting should have no effect on what non-root-requiring apps you can use. If the apps allow you to select a storage location, you should be able to use the SD after doing THIS.
scottharris4 said:
SuperUser hasn't asked me to disable Knox. How do I do it manually?
Click to expand...
Click to collapse
Open the SU app, it should prompt you then. If not, download SuperSU from the Play Store. It'll probably prompt you to update the binary as well.
http://true-android.blogspot.com/2014/02/how-to-root-samsung-galaxy-tab-pro-101.html
Sent from my SM-T520 using XDA Premium 4 mobile app
Thank You leatherneck6017 for pulling the rooting info together
Root was a breeze
Going with out a rooted device just seems so unnatural..
Worked like a charm on my 10.1 thanks for the instructions and as always huge thanks to Chainfire!!
Holy ****... I just got a bsod right in the middle of flashing with odin. Luckily it didn't brick or anything but I am not rooted after this. Will try again.
Edit: with the 8.4. Using a windows 7 machine.
Edit 2: well it bsod'ed a second time, i might try this on my windows 8.1 machine.
Encryption and stock firmware
So far so great over the last few days on my 8.4, thank you!
I tried to encrypt the device itself (not SD), had full password enabled, it reboots like it is going to start encrypting but never does. Another forum had some info that as of 4.3 this was happening on rooted devices (possibly knox related?) and you had to go back to stock everything to encrypt THEN root the device. No big deal, but I can't find a way to go back aside from a link to 4.4.2 firmware from nasirtech's blogspot which I don't really know if it's legit or not. Why can't we just download it from Samsung's website? I also tried KIES 3 and it says I'm running the latest firmware.
Downloading OTA gives "Your device has been modified. Software updates are not available" ok who cares, I'm planning to use CM whenever it's working anyway.
Aside from that the only other negative thing I've noticed since rooting was the KNOX WARRANTY VOID: 0x1 message on the custom download screen, but again, I don't care.
Really just curious if anyone has a workaround to the encryption thing, or if there's some better alternative anyway.
has anyone used this method with windows 8.1?
I have. Worked fine.
Sent from my SM-T320 using Tapatalk
qn1gJ1 said:
So far so great over the last few days on my 8.4, thank you!
I tried to encrypt the device itself (not SD), had full password enabled, it reboots like it is going to start encrypting but never does. Another forum had some info that as of 4.3 this was happening on rooted devices (possibly knox related?) and you had to go back to stock everything to encrypt THEN root the device. No big deal, but I can't find a way to go back aside from a link to 4.4.2 firmware from nasirtech's blogspot which I don't really know if it's legit or not. Why can't we just download it from Samsung's website? I also tried KIES 3 and it says I'm running the latest firmware.
Downloading OTA gives "Your device has been modified. Software updates are not available" ok who cares, I'm planning to use CM whenever it's working anyway.
Aside from that the only other negative thing I've noticed since rooting was the KNOX WARRANTY VOID: 0x1 message on the custom download screen, but again, I don't care.
Really just curious if anyone has a workaround to the encryption thing, or if there's some better alternative anyway.
Click to expand...
Click to collapse
That one on nasirtech's blogspot appears to be for Portugal. As far as I know, no one has posted a stock firmware for US models yet. Which makes me wonder...could it be extracted from Kies somehow?
I have a Sprint Samsun Galaxy Note 4, in the USA. I'm trying to root my device - I've read online tutorials, watched videos, and it doesn't seem to be working. Here's what happens:
1. Downloaded CF Auto Root for my device, unzipped it.
2. Set up ODIN.
3. Set phone to download mode, plugged in to PC.
4. Did not see the blue light, figured I didn't have the right drivers.
5. Turned phone back on, and noticed that ODIN light now works (as do file transfers), but downloaded new drivers anyway.
6. Uninstalled old drivers, rebooted.
7. Installed new drivers, rebooted.
8. Placed phone in download mode again, same issue.
Any ideas?
Did you wait a couple of minutes between steps 3 and 4 before giving up. I just re-did this last night; I didn't time it but my PC must have taken a minute to show COM to be ready to start Odin on the stock tar.
I was also having USB driver issues and reinstalled. My PC has been having USB issues in general with Windows 8.1 updates; had to uninstall and reinstall the same PC generic USB driver. Circa 2009 era PC needs an overhaul or replacement.
BTW, if you're using an older CF Auto root, CF went back to Odin 3.07 and updated to superSU v2.45
I did, because I was unsure what was going on. This is only the second time I've rooted a phone, so I was unsure what would happen if I pulled the battery. I think I waited about 20 minutes while looking online to figure out what was going on.
I'm not sure what you mean by an older version. I downloaded the version for my phone from chainfire.eu
http://redirect.disqus.com/url?url=...&thread=3459253652&zone=thread&area=discovery
http://redirect.disqus.com/url?url=...&thread=3443914612&zone=thread&area=discovery
Some questions I should have asked earlier: USB debugging enabled? Using USB 2.0? Tried different USB cables?
Yes, device debugging is enabled. First thing I did on my phone after activation =)
I'm not sure how to tell if I'm using USB 2.0 or 3.0.
I did try a different cable. I don't think the cable would be the issue since it works when the phone is on normally, though?
I'm going to follow the troubleshooting guide in the links you posted, see if that helps =)
Yes, device debugging is enabled. First thing I did on my phone after activation =)
I'm not sure how to tell if I'm using USB 2.0 or 3.0.
I did try a different cable. I don't think the cable would be the issue since it works when the phone is on normally, though?
I'm going to follow the troubleshooting guide in the links you posted, see if that helps =)
PS. Did you use Kingo to root your note 4? I might give it a try.
No, I just posted links for the thoroughness of checks. I used CF Auto root. Good luck.
Did not work either. It DOES say I'm connected, went through the reboot, but then just starts over again. /sigh
I'm thinking the MTP might be the issue, but I don't seem to have a MSD option on my note 4?
Any more ideas?
What Windows version are using? If it's 8.1, has it been updated? There was a USB 2.0 update that fixed some devices reporting as compatible greater than 2.0 but not handled correctly by Windows 8.1 but was OK with Windows 8.0 and below. Windows 8.1 got an update July, 2014, that should have fixed that but not all were fixed; there's a link for reporting exceptions with a log but I'm not sure that applies to you.
Have you tried using the USB port on test of PC case?
Maybe being more specific about your PC and what you've tried would help.
From there, if anyone else has some suggestions, please advise.
faile486 said:
I have a Sprint Samsun Galaxy Note 4, in the USA. I'm trying to root my device - I've read online tutorials, watched videos, and it doesn't seem to be working. Here's what happens:
1. Downloaded CF Auto Root for my device, unzipped it.
2. Set up ODIN.
3. Set phone to download mode, plugged in to PC.
4. Did not see the blue light, figured I didn't have the right drivers.
5. Turned phone back on, and noticed that ODIN light now works (as do file transfers), but downloaded new drivers anyway.
6. Uninstalled old drivers, rebooted.
7. Installed new drivers, rebooted.
8. Placed phone in download mode again, same issue.
Any ideas?
Click to expand...
Click to collapse
Press volume up to confirm download mode?
rawintellect said:
Press volume up to confirm download mode?
Click to expand...
Click to collapse
Yes, that has to be done to get to download mode? I'm at the screen where it says 'Downloading...Do not turn of the target!!'
faile486 said:
Did not work either. It DOES say I'm connected, went through the reboot, but then just starts over again. /sigh
Click to expand...
Click to collapse
I'm sorry but I don't recall seeing this reply because I don't understand it now. I may have overlooked it?
Are you saying the phone appears to download but boot loops? You should see success and 0 failures prior to auto boot. Is that the CF Auto root flash in Odin or another Odin flash like recovery or stock tar? If that's happening, did you try to pull battery and delete cache and dalvik cache in recovery? Is the phone semi bricked or just not rooted? Can you Odin the recovery tar for TWRP recovery? If so, you could just flash the superSU zip file in TWRP.
http://download.chainfire.eu/supersu
Another suggestion, if you're getting anywhere with Odin, you should close and reopen Odin if doing multiple flashes. Close after each flash; i.e., power down, flash stock tar, close Odin, open Odin, flash CF Auto root, close Odin, flash recovery (download mode steps omitted since you know that already).
Again, someone might could help with detailed setup details and steps taken. Sorry if I'm not following well; I'd like to help, if possible.
samep said:
What Windows version are using? If it's 8.1, has it been updated? There was a USB 2.0 update that fixed some devices reporting as compatible greater than 2.0 but not handled correctly by Windows 8.1 but was OK with Windows 8.0 and below. Windows 8.1 got an update July, 2014, that should have fixed that but not all were fixed; there's a link for reporting exceptions with a log but I'm not sure that applies to you.
Have you tried using the USB port on test of PC case?
Maybe being more specific about your PC and what you've tried would help.
From there, if anyone else has some suggestions, please advise.
Click to expand...
Click to collapse
I'm using Windows 7. Using another PC is a good idea, I'll try that.
faile486 said:
I'm using Windows 7. Using another PC is a good idea, I'll try that.
Click to expand...
Click to collapse
Didn't realize the auto correct suggested wrong word. I meant rear USB of PC case but trying another PC is also suggested.
Windows 7 means most of my suggestions regarding the drivers may not apply to you. Off topic: upgrading to Windows 8 from Windows Vista had me searching for needed applications and tools omitted from Windows 8. Windows 7 is more developer ready than Windows 8. Simply rooting should be OK with either version as long as drivers and Windows updates are up to date and not broken.
Try those ideas; if still no success, consider the suggestions and questions I gave in the reply earlier today.
samep said:
Didn't realize the auto correct suggested wrong word. I meant rear USB of PC case but trying another PC is also suggested.
Windows 7 means most of my suggestions regarding the drivers may not apply to you. Off topic: upgrading to Windows 8 from Windows Vista had me searching for needed applications and tools omitted from Windows 8. Windows 7 is more developer ready than Windows 8. Simply rooting should be OK with either version as long as drivers and Windows updates are up to date and not broken.
Try those ideas; if still no success, consider the suggestions and questions I gave in the reply earlier today.
Click to expand...
Click to collapse
I don't know what I did differently on the 18 ****ING TIME but it finally worked! Your thanks meter has been duly increased =)
faile486 said:
I don't know what I did differently on the 18 ****ING TIME but it finally worked! Your thanks meter has been duly increased =)
Click to expand...
Click to collapse
Glad to see you among the rooted in Sprint Note 4 XDA. Hopefully your solution can be repeated for future updates. Lollipop well be here some day.
Does Kingo root Trip Knox?
Sent from my SM-N910P using XDA Free mobile app