Related
I have updated everytime there was an update. I updated to the new rom 6.1.1 on 12/17/10. About a week later I tried to use the USB tether on my laptop and then on my desk top. I could not use it as the computer said the driver is not signed. Or code 10. I'm not a great PC user. How do I fix this or is there a fix for it? I use to use it on the previous rom 6.1.0 with out ever having a problem. I asked a question about this in a different thread and was basically ignored. Both of my computers use XP.
So nobody else has this problem? Or nobody can or wants to which is it cause I have done lots of searching and reading without finding any answer or clue. Thanks
So anyone else that uses USB tethering, please reply and let me know if yours works. If so is there a trick to it?
I've never had any issues. Try doing a full wipe (clear data/cache) and reinstalling the rom.
Sent from my Liberty using XDA App
No issues on Liberated 2.2 with tethering. But still you can use 3rd party apps, like PdaNET.
mattbollenbach said:
I've never had any issues. Try doing a full wipe (clear data/cache) and reinstalling the rom.
Click to expand...
Click to collapse
I've done this three times with no success. Both of my computers still giving the error. (Code 10) driver not digitally signed. I noticed one thing thou that after wiping everything and reinstalling one of the times it would not reboot all the way. Stayed on the Cyanogen mod symbol with the stuff going around it. Every time it tried to load it just bounced back to this screen.
barisahmet said:
No issues on Liberated 2.2 with tethering. But still you can use 3rd party apps, like PdaNET.
Click to expand...
Click to collapse
Just about to try PdaNet. In my phone info: Says Android 2.2.1, Kernel Version Is: [email protected] #69 Mod version CyanogenMod-6.1.1-Liberty.
PDA net works. I really wished though that I could use what was already installed on the phone. It worked all the time flawless in the previous ROM.
Just to make sure, don't have your phone plugged in when you are using recovery mode; for some reason if your phone is off and you plug it in via usb it enters an unreliable version of clockwork recovery. Instead choose boot into recovery from the power down options within the rom.
Sent from my Liberty using XDA App
Did you try uninstalling the driver from your computer?
Also, start > control panel > system > hardware > driver signing
what setting do you have currently for driver signing?
mattbollenbach said:
Just to make sure, don't have your phone plugged in when you are using recovery mode; for some reason if your phone is off and you plug it in via usb it enters an unreliable version of clockwork recovery. Instead choose boot into recovery from the power down options within the rom.
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
No I dont have my phone plugged in when using recovery mode. Thats the way I always do it.
zervic said:
Did you try uninstalling the driver from your computer?
Also, start > control panel > system > hardware > driver signing
what setting do you have currently for driver signing?
Click to expand...
Click to collapse
My driver signing is set to ignore- Install the software anyway and dont ask for my approval. I dont really know how the settings in both computer would have changed. Unless when I installed a printer it automatically changed them. Cause besides the new ROM it is the only thing Ive changed. Also I have tried uninstalling and reinstalling and deleting the tether and downloading and reinstalling with the same every time.
On top of that now my phone is rebooting it self. Today while checking cl. it just flashed to the begining cyanogen screen. What's going on? What should I do Now?
I tried to reinstall the ROM again, cleared everything. I noticed while Wiping Dalvik Cache it just jumped back to the previous screen. It didnt show that it was wiping or anything. I reinstalled and apparently everything was not wiped because when my phone Rebooted. It took me through the setup screens like a new phone but when the screen poped up. My wallpaper was still there. Can someone help me? Im really getting sick of trying to get this to work now It seems as I have more problems now.
pcidiot said:
I tried to reinstall the ROM again, cleared everything. I noticed while Wiping Dalvik Cache it just jumped back to the previous screen. It didnt show that it was wiping or anything. I reinstalled and apparently everything was not wiped because when my phone Rebooted. It took me through the setup screens like a new phone but when the screen poped up. My wallpaper was still there. Can someone help me? Im really getting sick of trying to get this to work now It seems as I have more problems now.
Click to expand...
Click to collapse
Does the computer you're trying to use the tether on have wireless capabilities?
One of them does and the other does not. Both run xp though. Wiped again, wiping everything twice before flashing the ROM. I have not had any self reboot so far, and everything seems to be working ok. I have not got around to trying the usb tether yet though. Maybe a little later today.
I have a new Galaxy Note 3 (having bricked one trying to understand why it wouldn't encrypt) and now with a full stock rom I still find that the phone is impossible to encrypt.
I have an encrypted SD card in it. (only thing I can think of that might be causing problems)..
Settings > General > Security > Encrypt Device keeps stopping after a single shutdown,
How the heck do I encrypt this thing?? - Am I missing the blindingly obvious..
Thanks
tahnoonp said:
I have a new Galaxy Note 3 (having bricked one trying to understand why it wouldn't encrypt) and now with a full stock rom I still find that the phone is impossible to encrypt.
I have an encrypted SD card in it. (only thing I can think of that might be causing problems)..
Settings > General > Security > Encrypt Device keeps stopping after a single shutdown,
How the heck do I encrypt this thing?? - Am I missing the blindingly obvious..
Thanks
Click to expand...
Click to collapse
I'm having the exact same issue. Encryption is requited to get my work email and I can't get it to go.
Finally got mine to encrypt
Took me a bunch of tries.. and finally once i opened a chat with samsung support it finally worked.. i was at 100% charge, plugged into the wall and if finally worked. not sure if thats a bug in its detection if your over the stated 80% or not... good luck.. i finally got it working though.. only did a fast encryption as it didn't work on previous tries either way... so i just chose one and tried it again.
tahnoonp said:
I have a new Galaxy Note 3 (having bricked one trying to understand why it wouldn't encrypt) and now with a full stock rom I still find that the phone is impossible to encrypt.
I have an encrypted SD card in it. (only thing I can think of that might be causing problems)..
Settings > General > Security > Encrypt Device keeps stopping after a single shutdown,
How the heck do I encrypt this thing?? - Am I missing the blindingly obvious..
Thanks
Click to expand...
Click to collapse
I have the Google Policy Manager and Encryption is required for me too. I started at 81% and the first time I did it, it just rebooted. The second time I did it it worked like it was suppose to. Try it again right after it reboots and see if it works.
Make sure the phone is charged and keep trying over and over.
It will work eventually.
I gave up. I'm using touchdown now for work email which will allow me to skip full device encryption
Sent from my SM-N900V using Tapatalk
Same problem here, it will not encrypt
....help please
This is the answer I found doing a couple of root and unroot
1.If you encrypt the device and then root it you will net get past the passcode in the phone (black screen)
2. If you root the phone first and ten try to encrypt you will get the problems mentioned in this thread
..any tips how to get the phone rooted and then encrypted?
greffel said:
This is the answer I found doing a couple of root and unroot
1.If you encrypt the device and then root it you will net get past the passcode in the phone (black screen)
2. If you root the phone first and ten try to encrypt you will get the problems mentioned in this thread
..any tips how to get the phone rooted and then encrypted?
Click to expand...
Click to collapse
Bump. I'm looking for this answer too.
digittante said:
Bump. I'm looking for this answer too.
Click to expand...
Click to collapse
anyone at all? im stuck. Bump!
was having a similar problem on nexus 4 but safe mode helped there.
dind't help on my new n3. shouldn't have rooted before encrypting.
tried pressing encrypt about 10 times.
tried boot into recovery + wipe . also tried safe mode. also tried unroot + factory reset (pretty sure recovery + wipe /data is the same as reset user data from settings).
waiting for the firmware image to download - decided to try a firmware reflash
and then before flashing it I tried rebooting to recovery and powering off and encrypting and it worked. or maybe it was that random 12th time it worked because of an unrelated reason.
and after trying to root it again it just booted to a black screen after cf-root and enter encryption password screen.
*sigh*
My Work-Around
svyr said:
and then before flashing it I tried rebooting to recovery and powering off and encrypting and it worked. or maybe it was that random 12th time it worked because of an unrelated reason.
and after trying to root it again it just booted to a black screen after cf-root and enter encryption password screen.
*sigh*
Click to expand...
Click to collapse
I'm an AT&T customer, but I bought a T Mobile Note 3 off of Craigslist, unlocked it, rooted using Chainfire's ODIN thread, and then used the RegionFree Lock Away app. I was unable to encrypt just like you guys until I did the following. Flashed TWRP tar file from the TWRP site using ODIN. Rebooted into recovery and made an image, backup up everything, just in case. Rebooted and went in the SU Superuser application that Chainfire originally installed and uninstalled through the settings in the program. Once I rebooted I was able to encrypt the device (without fast method), I already had my SD Card encrypted. Once I encrypted the device I downloaded Kingo Root at the advice of DesignGears and used the one click root application from the Kingo Root site (google it.) After I did that, I now have full root access back, encryption, and never had to uninstall the region lock, so I didn't lose phone connectivity, applications, or anything else during the process. I recommend using TitaniumBackup and syncing via Google Drive or Dropbox before you start the process so you can restore your apps and data, once again, just in case.
encrypted ATT Note 3 not able to root
I was able to unroot my ATT Note 3 and then encrypted it. But Kingo Root failed to root the device. (I used it to root the phone once previously)
Now I stuck in a status with encrypted phone not able to root anymore.
Any suggestions please?
GHolbrook4 said:
I'm an AT&T customer, but I bought a T Mobile Note 3 off of Craigslist, unlocked it, rooted using Chainfire's ODIN thread, and then used the RegionFree Lock Away app. I was unable to encrypt just like you guys until I did the following. Flashed TWRP tar file from the TWRP site using ODIN. Rebooted into recovery and made an image, backup up everything, just in case. Rebooted and went in the SU Superuser application that Chainfire originally installed and uninstalled through the settings in the program. Once I rebooted I was able to encrypt the device (without fast method), I already had my SD Card encrypted. Once I encrypted the device I downloaded Kingo Root at the advice of DesignGears and used the one click root application from the Kingo Root site (google it.) After I did that, I now have full root access back, encryption, and never had to uninstall the region lock, so I didn't lose phone connectivity, applications, or anything else during the process. I recommend using TitaniumBackup and syncing via Google Drive or Dropbox before you start the process so you can restore your apps and data, once again, just in case.
Click to expand...
Click to collapse
I was able to get mine to encrypt after killing the bloat apps. All Google sync, amazon, and Verizon services. I can't say which one was killing it since it stopped pretty much every app or service that wasn't critical to the device.
Can anyone confirm that Encryption will never work once we root our phone ?
nlatifolia said:
Can anyone confirm that Encryption will never work once we root our phone ?
Click to expand...
Click to collapse
Same question here... Anyone was able to encrypt after being rooted???
Same question, rooted can't encrypt.
Just got a note 3 and this is an old thread. So wanted to update this question.
To encrypt device after root all that is needed to do is run the following command from terminal or adb shell as root. You must have the latest busybox installed.
pkill -KILL daemonsu
After running this command you should be back at the "$" prompt and out of root. Do not run su again.
Then encrypt your device. Encryption should work fine. Once rebooted you will have root again.
I had to repeat the above steps because I ran su again. Running su restarts daemonsu.
Good luck
Hi,
I was able to root and encrypt my sm-n900 note3 using the steps mentioned on this post:
http://forum.xda-developers.com/showthread.php?t=2791587
Just make sure that you have your backups ready case something goes wrong
I've installed the bloatwares after rooting and encrypt.
Its been almost 3 weeks since i cannot use my nexus 6p, i think im in a serious problem since my phone has some specific problems that makes my problem harder to solve.
Long story short, i installed SuperSU zip file with TWRP, after that, my phone did not wanted to pass the bootloader, i found that via file manager of the TWRP i could just delete the SUPERSU file and boot again, i tried, i have deleted it, but when i reboot it still doesnt pass the bootloader and in fact, when i go to TWRP again, the SUPERSU file is still right where it was.
When i try to delete it, it only appears "MTP enabled" in the user log.
I know i could delete it with my computer, but my phone isnt recognized by my computer, even after this problem, when it was functional it would be recognized and it wont fastcharge too, so thats a daughters board problem.
So what can i do? I have some roms in my downloads folder, but even if i try to install any of them, after the installation in the user log says "installation was [0]" instead of "installation was [succesful]" i really dont know where to start
Any one knows what should i do?
ernestomn98 said:
Its been almost 3 weeks since i cannot use my nexus 6p, i think im in a serious problem since my phone has some specific problems that makes my problem harder to solve.
Long story short, i installed SuperSU zip file with TWRP, after that, my phone did not wanted to pass the bootloader, i found that via file manager of the TWRP i could just delete the SUPERSU file and boot again, i tried, i have deleted it, but when i reboot it still doesnt pass the bootloader and in fact, when i go to TWRP again, the SUPERSU file is still right where it was.
When i try to delete it, it only appears "MTP enabled" in the user log.
I know i could delete it with my computer, but my phone isnt recognized by my computer, even after this problem, when it was functional it would be recognized and it wont fastcharge too, so thats a daughters board problem.
So what can i do? I have some roms in my downloads folder, but even if i try to install any of them, after the installation in the user log says "installation was [0]" instead of "installation was [succesful]" i really dont know where to start
Any one knows what should i do?
Click to expand...
Click to collapse
Have you tried connecting to PC from the bootloader menu? I don't know much about rooting. Have you tried installing the latest google usb driver? Does the device show up in device manager on pc? Have you tried using a different cable or different pc?
So I rooted my phone following information on this site/a video guide from youtube (I dunno if I'm able to post links but I can PM if you need to see what it had me do etc) so I did a fresh root with TWRP, RMM bypass, no-verify encryption, magisk. All worked great the phone was rooted etc, I then stupidly removed google play services to try get an early date APK which caused issues so I thought a wipe with TWRP would fix the issue but the startup wizard wouldn't work, so I then removed startup wizard via TWRP got back into the phone and put the new version of play services on, yet still had issues so I got the default firmware for my model at samsmobile and put it on via odin - all worked great phone booted fine etc but some apps said a boot was detected, so I made sure to go into developer options and make sure the OEM was locked, did a wipe via the default options when holding power>bixy>up however some apps still say the phone is rooted.. I checked with a rootchecker and I pass the safety and it says no boot detected. So I dunno what the problem is? The only thing I did see was when I did the wipe this came up
"remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (no such file or diectory)
e:[libfs_mgr] is_dt_compatible(): firmware info was not valid: '/proc/device-tree/firmware/android/compatible: no such file or directory"
Really dunno what to do from here.
bump
mrberta said:
So I rooted my phone following information on this site/a video guide from youtube (I dunno if I'm able to post links but I can PM if you need to see what it had me do etc) so I did a fresh root with TWRP, RMM bypass, no-verify encryption, magisk. All worked great the phone was rooted etc, I then stupidly removed google play services to try get an early date APK which caused issues so I thought a wipe with TWRP would fix the issue but the startup wizard wouldn't work, so I then removed startup wizard via TWRP got back into the phone and put the new version of play services on, yet still had issues so I got the default firmware for my model at samsmobile and put it on via odin - all worked great phone booted fine etc but some apps said a boot was detected, so I made sure to go into developer options and make sure the OEM was locked, did a wipe via the default options when holding power>bixy>up however some apps still say the phone is rooted.. I checked with a rootchecker and I pass the safety and it says no boot detected. So I dunno what the problem is? The only thing I did see was when I did the wipe this came up
"remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (no such file or diectory)
e:[libfs_mgr] is_dt_compatible(): firmware info was not valid: '/proc/device-tree/firmware/android/compatible: no such file or directory"
Really dunno what to do from here.
Click to expand...
Click to collapse
BUMPITY BUMP BUMP, plz help my fwiend!
Hey,
so i ****ed up my 6t (stock rom, twrp installed and rooted with magisk) yesterday after ota updating to 9.0.17., got stuck in a bootloop.. i guess it was the lawnstep magisk module that caused the **** up... but im not sure. normally i could do a ota just fine. so after unbricking and flashing 9.0.17 manually i cannot Access my storage outside from TWRP (when in recovery i can access the storage just as normal and it shows also on my pc as normal), apps cannot Access, pc - same. And i have no clue whats causing it.
Obviously i switched to file transfer in the notification area, usb Debugging enabled, reboot pc, 6t, switched usb ports, wiped the whole good damn phone again. nothing.
Any clues?
help would be greatly appreciated!
best,
T
Solved
TanakaX5 said:
Solved
Click to expand...
Click to collapse
Thanks for the very descriptive resolution to your issue. This will definitely help out anyone else that has this issue in the future!
Jager said:
Thanks for the very descriptive resolution to your issue. This will definitely help out anyone else that has this issue in the future!
Click to expand...
Click to collapse
Haha OK ok.. you are quite right...
It wasn't really a solution, did full reset of software with the unbrick tool provided here in the forum.
After that updated via Ota rooted and all is good again,
Peace
Haven't had that issue with 9.0.17, but I have had the issue where I'll go to use an app that requests root permission, it'll fail. Check magisk manager it says magisk isn't installed. A reboot fixes it, but I never had that issue on 9.0.16