I have my Samsung note 3, and it will never be unlocked. So i was thinking about moving to this. Is the Verizon edition unlocked for custom roms?
Sent from my SM-N900V using XDA Free mobile app
scoreboard said:
I have my Samsung note 3, and it will never be unlocked. So i was thinking about moving to this. Is the Verizon edition unlocked for custom roms?
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
It doesn't come unlocked, but you can unlock it. That's why are a lot of us are on this phone. I had an S5 ordered, but decided against it, when I saw there wasn't any progress being made on it. I cancelled my order, bought my M8, and haven't looked back. Give me an unlocked bootloader, or give me death.
You can S-OFF (which unlocks bootloader) & root it immediately after getting it.
I came from a locked Galaxy S4 and have to say this phone is snappier than an iPhone & as unlockable as a door thats compatible with all keys ;D. Love love loveeee this phone and highly recommend it! Go for it!
I unlocked mine the moment I got home with it, no OTA update required as some people have said to do before unlocking it & as far as I've seen no ones had an actual "Oh no! They made it impossible to unlock like Sammysung!" moment.
Ive tried a for the last two days to root my htc m8..but i can not get it to work...tried htc unclock tried setting up adb...but the first gives me an mid error and the second does not recognize my phone...i did install the newest update before i tried to s-off....any help would be great...
Frausbite77 said:
Ive tried a for the last two days to root my htc m8..but i can not get it to work...tried htc unclock tried setting up adb...but the first gives me an mid error and the second does not recognize my phone...i did install the newest update before i tried to s-off....any help would be great...
Click to expand...
Click to collapse
Have u tried the weak sauce app for root then fire water to s-off?
Sent from my Insanely powered M8 using Tapatalk
holla420 said:
Have u tried the weak sauce app for root then fire water to s-off?
Sent from my Insanely powered M8 using Tapatalk
Click to expand...
Click to collapse
I set up adb using the method from root junky. but my computer won't recognize my device. I must have tried it like 50 times, so i tried the htcdev unlock method...my computer recognizes by device but after i copy the token i get the mid 160 error.
Frausbite77 said:
I set up adb using the method from root junky. but my computer won't recognize my device. I must have tried it like 50 times, so i tried the htcdev unlock method...my computer recognizes by device but after i copy the token i get the mid 160 error.
Click to expand...
Click to collapse
U must not being in the right directory
Sent from my Insanely powered M8 using Tapatalk
Frausbite77 said:
I set up adb using the method from root junky. but my computer won't recognize my device. I must have tried it like 50 times, so i tried the htcdev unlock method...my computer recognizes by device but after i copy the token i get the mid 160 error.
Click to expand...
Click to collapse
What that guy above me said, if you using Windows make sure you right click+shift in the platform tools directly then see if it shows up with adb devices, if not check your drivers.
Frausbite77 said:
Ive tried a for the last two days to root my htc m8..but i can not get it to work...tried htc unclock tried setting up adb...but the first gives me an mid error and the second does not recognize my phone...i did install the newest update before i tried to s-off....any help would be great...
Click to expand...
Click to collapse
HTCDEV unlock doesn't work for the Verizon variant. To s-off just follow this step by step guide:
http://forum.xda-developers.com/showthread.php?t=2708628
PRO TIPS: Let's say that your adb and fastboot files are located in C:\Program Files\Android. Add this directory to your system path by pressing the Windows key and typing "environment". After a few letters you'll see an option called "Edit the System Environment Variables". Click on this option. The system properties windows will open to the Advanced tab. Click the Environment Variables button. In the System Variables field you'll see a variable called Path. Click on it and choose edit. In the variable value field you'll see a list of paths separated by semi colons. We want to add the path of your adb and fastboot files to the system Path variable so that adb and fastboot commands can be executed anywhere. For the example location I used above you would add the following to the end of the list:
;C:\Program Files\Android
To test, open a command prompt and type "adb". This should launch adb with no parameters. Now you can use adb and fastboot commands anywhere. When you download the firewater script file, you can just leave it in the Downloads directory. If you use Chrome you could click the arrow next to the file and choose "show in folder". Then shift+right click an empty portion of the Downloads directory window and choose "open command window here" (you can also shift+right click on folders icons to accomplish this). Should be easy to s-off now.
NOTES:
*Once adb is setup issue the command "adb devices" to ensure your phone is recognized. The first time you will get a popup on your phone asking if you want to allow the PC adb access. Make sure you check "always allow".
*Before you issue the "su" command wait about 30 seconds to allow WeakSauce to root the phone after reboot. If you get an error saying "su not found" it's because WeakSauce has not yet rooted the phone. Wait 10 seconds and try again.
*When you issue the "su" command wake your phone's display and look for a SuperSu request. Allow it obviously.
*It's possible that the process may fail. If it does just try again. If it keeps failing try a different USB 2.0 port. Also make sure you're using the best USB cable that you have. The one that came with the phone should work.
Doc Ames said:
HTCDEV unlock doesn't work for the Verizon variant. To s-off just follow this step by step guide:
http://forum.xda-developers.com/showthread.php?t=2708628
PRO TIPS: Let's say that your adb and fastboot files are located in C:\Program Files\Android. Add this directory to your system path by pressing the Windows key and typing "environment". After a few letters you'll see an option called "Edit the System Environment Variables". Click on this option. The system properties windows will open to the Advanced tab. Click the Environment Variables button. In the System Variables field you'll see a variable called Path. Click on it and choose edit. In the variable value field you'll see a list of paths separated by semi colons. We want to add the path of your adb and fastboot files to the system Path variable so that adb and fastboot commands can be executed anywhere. For the example location I used above you would add the following to the end of the list:
;C:\Program Files\Android
To test, open a command prompt and type "adb". This should launch adb with no parameters. Now you can use adb and fastboot commands anywhere. When you download the firewater script file, you can just leave it in the Downloads directory. If you use Chrome you could click the arrow next to the file and choose "show in folder". Then shift+right click an empty portion of the Downloads directory window and choose "open command window here" (you can also shift+right click on folders icons to accomplish this). Should be easy to s-off now.
NOTES:
*Once adb is setup issue the command "adb devices" to ensure your phone is recognized. The first time you will get a popup on your phone asking if you want to allow the PC adb access. Make sure you check "always allow".
*Before you issue the "su" command wait about 30 seconds to allow WeakSauce to root the phone after reboot. If you get an error saying "su not found" it's because WeakSauce has not yet rooted the phone. Wait 10 seconds and try again.
*When you issue the "su" command wake your phone's display and look for a SuperSu request. Allow it obviously.
*It's possible that the process may fail. If it does just try again. If it keeps failing try a different USB 2.0 port. Also make sure you're using the best USB cable that you have. The one that came with the phone should work.
Click to expand...
Click to collapse
Thank you for letting me know about the HTC Dev...I have a mac and set up ADB...it shows my phone off line...i get the message that says allow this computer and check always...i run adb devices and now it just returns blank...i reinstall drivers which is htc sync but the problem persists....
Frausbite77 said:
Thank you for letting me know about the HTC Dev...I have a mac and set up ADB...it shows my phone off line...i get the message that says allow this computer and check always...i run adb devices and now it just returns blank...i reinstall drivers which is htc sync but the problem persists....
Click to expand...
Click to collapse
Try 'adb kill-server' then issue 'adb start-server' then try 'adb devices'. If that doesn't work, try a different USB port. If still no joy try a different USB cable. If that doesn't work try restarting the Mac, restarting the phone, spinning around in an office chair three times, and blowing into a Nintendo cartridge. If that doesn't work I don't know what else to suggest besides trying it on a different computer or maybe in Windows. I've never had an issue with ADB so if somebody else has any ideas for Frausbite77 please chime in.
Edit: I googled this Mac ADB guide. I don't know if it really matters, but it says to have ADB/fastboot in the /usr/bin directory. Check it out. There's a script file and when run it installs the Android SDK tools to the appropriate folder. Also check the comments. Somebody else has probably had the same problem as you:
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
Edit 2: After reading a user's comment that the script was broken I looked at the script and it was, in fact, broken. I fixed it. Follow the guide but use this zip instead:
Doc Ames said:
Try 'adb kill-server' then issue 'adb start-server' then try 'adb devices'. If that doesn't work, try a different USB port. If still no joy try a different USB cable. If that doesn't work try restarting the Mac, restarting the phone, spinning around in an office chair three times, and blowing into a Nintendo cartridge. If that doesn't work I don't know what else to suggest besides trying it on a different computer or maybe in Windows. I've never had an issue with ADB so if somebody else has any ideas for Frausbite77 please chime in.
Edit: I googled this Mac ADB guide. I don't know if it really matters, but it says to have ADB/fastboot in the /usr/bin directory. Check it out. There's a script file and when run it installs the Android SDK tools to the appropriate folder. Also check the comments. Somebody else has probably had the same problem as you:
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
Edit 2: After reading a user's comment that the script was broken I looked at the script and it was, in fact, broken. I fixed it. Follow the guide but use this zip instead:
Click to expand...
Click to collapse
Ok, well so I never got adb to show my device on line....but when i typed ./adb reboot, the device actually responds to the commands...taking a risk i went ahead and pushed the firewater files and the process worked. I was able to unlock my device and install twrp...so i figured out that for and to work i have to type in ./ before i type in any commands...i don't if i messed something up along the way or what...but in the end i have gotten i was able to root and get s off....maybe i got lucky lol...thanks so much for the help!!
Frausbite77 said:
Ok, well so I never got adb to show my device on line....but when i typed ./adb reboot, the device actually responds to the commands...taking a risk i went ahead and pushed the firewater files and the process worked. I was able to unlock my device and install twrp...so i figured out that for and to work i have to type in ./ before i type in any commands...i don't if i messed something up along the way or what...but in the end i have gotten i was able to root and get s off....maybe i got lucky lol...thanks so much for the help!!
Click to expand...
Click to collapse
That's the proper command line for using Adb on a Mac. It won't work without using ./ before the command.
Sent from my HTC6525LVW using Tapatalk
Frausbite77 said:
Ok, well so I never got adb to show my device on line....but when i typed ./adb reboot, the device actually responds to the commands...taking a risk i went ahead and pushed the firewater files and the process worked. I was able to unlock my device and install twrp...so i figured out that for and to work i have to type in ./ before i type in any commands...i don't if i messed something up along the way or what...but in the end i have gotten i was able to root and get s off....maybe i got lucky lol...thanks so much for the help!!
Click to expand...
Click to collapse
My bad. I should have mentioned that to execute a file in a Unix-like operating system you need to enter the full or relative path if it's not in your $Path environment variable. That's why you needed to add a './' before the command. The './' indicates that the file is in the current directory. That's probably why that guide recommended putting adb and fastboot in /usr/bin. If you want to fix it so that adb and fastboot commands can be run from anywhere open a terminal, change to the directory where adb and fastboot are located, and issue the following commands:
sudo mv adb /usr/bin
sudo mv fastboot /usr/bin
That will move adb and fastboot into /usr/bin which is in your $Path so you can issue the commands anywhere without using './'. I'm glad you got your M8 s-offed and recovery installed. If you're looking into custom ROMs, I can personally recommend ViperOne as a great stock option and LiquidSmooth as an AOSP option. Try em' out. Now that you have recovery you can just restore a backup if you don't like your current ROM.
Doc Ames said:
My bad. I should have mentioned that to execute a file in a Unix-like operating system you need to enter the full or relative path if it's not in your $Path environment variable. That's why you needed to add a './' before the command. The './' indicates that the file is in the current directory. That's probably why that guide recommended putting adb and fastboot in /usr/bin. If you want to fix it so that adb and fastboot commands can be run from anywhere open a terminal, change to the directory where adb and fastboot are located, and issue the following commands:
sudo mv adb /usr/bin
sudo mv fastboot /usr/bin
That will move adb and fastboot into /usr/bin which is in your $Path so you can issue the commands anywhere without using './'. I'm glad you got your M8 s-offed and recovery installed. If you're looking into custom ROMs, I can personally recommend ViperOne as a great stock option and LiquidSmooth as an AOSP option. Try em' out. Now that you have recovery you can just restore a backup if you don't like your current ROM.
Click to expand...
Click to collapse
Thanks for the advice...actually i was just going to ask about some roms...just flashed viper rom and gonna give it a go...thanks for all the help...
Frausbite77 said:
Thanks for the advice...actually i was just going to ask about some roms...just flashed viper rom and gonna give it a go...thanks for all the help...
Click to expand...
Click to collapse
You'll love it. A couple thing to note though. For some reason the 1.6 download doesn't actually contain the 1.6 OTA so you'll want to go to 'About phone' and update to 1.6. Also I believe that ViperOne defaults to power saver mode. You can change this by using the toggle in the notification drawer. If you want to add power saver and extreme power saver to the settings menu follow this guide:
http://forum.xda-developers.com/showthread.php?t=2710946
Doc Ames said:
You'll love it. A couple thing to note though. For some reason the 1.6 download doesn't actually contain the 1.6 OTA so you'll want to go to 'About phone' and update to 1.6. Also I believe that ViperOne defaults to power saver mode. You can change this by using the toggle in the notification drawer. If you want to add power saver and extreme power saver to the settings menu follow this guide:
http://forum.xda-developers.com/showthread.php?t=2710946
Click to expand...
Click to collapse
wow, man viper rom is insane, thanks for the update heads up...i wouldn't have even thought to do that...guess i have tons of reading to catch up on...thanks...
I seem unable to use the adb backup command. Whenever I do it says: Now unlock your device and confirm the backup operation. Now my device is unlocked and it show nothing on the screen. And in the command prompt window nothing happens. I think I may have deleted an app on the phone that is required for adb backup. It is a Motorola XT907. If you could tell me what apps are required that would be extremely helpful.
I accepted the forced OS upgrade over the weekend (I think it was for Pie) on my Samsung Note 8. Upon restart, it is no longer accepting my encryption password and I can't get to my home screen. Yes, I know my password, and yes I'm freaking out (so any help would be appreciated!). I would like to not wipe the data off my phone.
So far he's what I've tried on my own:
Restarting/rebooting the device
Samsung Sync to try and back up
Find my mobile (both the android version and samsung version) to try and back up the device. No dice.
Load to bootloader (but device not recognized)
I'm down to three tries before the Factory Reset Protection (FRP) kicks in. (any way to extend number of tries is a separate, but equally important question.)
I finally started brushing up on adb and ran "adb devices". Server starts and it recognizes the device (whew!) but it's "unauthorized" which I assume it has to do with my encryption. Again, I have no access to the settings menu in order to enable USB debugging, so going into the GUI is not possible.
I also tried this:
[email protected]:~# adb backup -apk -shared -all -f ~/android/backup.ab
adb: unable to connect for backup: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
[email protected]:~# adb kill-server
[email protected]:~# adb start-server
* daemon not running; starting now at tcp:5037
* daemon started successfully
[email protected]:~# adb backup -apk -shared -all -f ~/android/backup.ab
adb: unable to connect for backup: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Again, the fact that ADB is recognizing the device is a good sign in my opinion, just need to get past that so I can backup and pull the data off my phone. If there are any how-to's or steps that show what I can do to fix my actual problem and get my phone back to the way it was on Saturday, that would be AWESOME.
I haven't tried rebooting without the SIM inserted or wiping cache partition from the reset screen, but I'm willing to try that if anyone thinks that'll do it.
Please help.
My Pixel 2 took a dive on a few days ago and I've been trying to get it operational ever since. The things i've tried are
1. Waiting it out
2. Force restart
3. Force restart more than 7 times in a row to get it to revert back to another version
4. ADB sideload the proper system image to get it to begin working
But none of these has worked. Right now all I'm really concerned about is trying to salvage my data and create a backup file for all my apps and data but when I try to do the backup through the adb using 'adb backup -apk -shared -all -system -f Direction:\filename.ab' it gives me an error that says "adb: unable to connect for backup: closed" And there's no other way around it.
Side note, I've only been able to get my phone to show up on the adb devices list when i say to do a recovery through adb, otherwise it simply doesn't show up there and only shows up under fastboot devices.
I would love some help here, anything you all can do to point me in the right direction would be fantastic.
@Otonirez
It seems the Android version doesn't support the ADB backup-interface. AFAIK in spring 2019 Google announced to remove the ADB backup feature.
jwoegerbauer said:
@Otonirez
It seems the Android version doesn't support the ADB backup-interface. AFAIK in spring 2019 Google announced to remove the ADB backup feature.
Click to expand...
Click to collapse
So what you're telling me is, that as far as you know, there is no real way for me to backup my data at this point?
Otonirez said:
So what you're telling me is, that as far as you know, there is no real way for me to backup my data at this point?
Click to expand...
Click to collapse
You know "ALL / DIFFERENT WAYS LEAD TO ROME", hence you simply pull the data off the phone - of course utilizing the ADB driver provided by phone's OEM: The format of the pull request is simple, you start with the command adb pull, then add the file/folder you are pulling and the location you want it to go.
Example:
Code:
cmd
mkdir C:\PHONE-BACKUP
adb devices
adb pull /data/ C:\PHONE-BACKUP
move /Y C:\PHONE-BACKUP PHONE-BACKUP-%DATE%
jwoegerbauer said:
You know "ALL / DIFFERENT WAYS LEAD TO ROME", hence you simply pull the data off the phone - of course utilizing the ADB driver provided by phone's OEM: The format of the pull request is simple, you start with the command adb pull, then add the file/folder you are pulling and the location you want it to go.
Example:
Code:
cmd
mkdir C:\PHONE-BACKUP
adb devices
adb pull /data/ C:\PHONE-BACKUP
move /Y C:\PHONE-BACKUP PHONE-BACKUP-%DATE%
Click to expand...
Click to collapse
I really wish I would have seen this a few minutes ago because I did a factory reset on my phone like right before i saw this. I doubt there's anything I can do at this point to reclaim my stuff
I just switched to the Pixel 6a and have botched something with an app I use.
I have the app's files from the old phone, which were in /data/data/com... folder, and want to overwrite files on the new phone, with them.
I did "adb pull ..." on the old phone to get files on the computer and intended to do "adb push ..." to the new,
but I can't get it to connect to adb, in recovery mode.
The old phone had TWRP.
When I rebooted it into recovery and connected with cable to PC, "adb devices" would print:
List of devices attached
<device_ID> recovery
On the new one, when I go into recovery (stock), "adb devices" prints nothing.
When I select the sideload option, "adb devices" prints:
<device_ID> sideload
In this sideload mode, the pull, push, shell... adb commands don't work.
How can I get the Pixel 6a to connect to the computer so that "adb devices" prints:
<device_ID> recovery
?
Stock recovery isn't TWRP! You have no access to anything in your file system.
Svrmirac said:
How can I get the Pixel 6a to connect to the computer so that "adb devices" prints:
<device_ID> recovery
?
Click to expand...
Click to collapse
Use TWRP. Stock recovery has no adbd, only a minimal adbd with no features except a sideload option for signed update.zips
Thank you for the suggestion, @WoKoschekk, but I don't think I can do that.
If I understand correctly, I have to unlock the bootloader to load TWRP.
With an unlocked bootloader, my banking app stops working, which is unacceptable,
and re-locking it apparently wipes all data, which I just jumped through hoops overwriting.
I seem to be at an impasse, with the stock ROM/recovery.
Svrmirac said:
If I understand correctly, I have to unlock the bootloader to load TWRP.
With an unlocked bootloader, my banking app stops working, which is unacceptable,
and re-locking it apparently wipes all data, which I just jumped through hoops overwriting.
Click to expand...
Click to collapse
Yes, (un-)locking wipes all data. But that is exactly the reason why /data is inaccessible from recovery. To keep your data safe.
I don't even think TWRP is a thing for modern pixels
ctfrommn said:
I don't even think TWRP is a thing for modern pixels
Click to expand...
Click to collapse
No it isn't the closing thing you'll find to TWRP on Pixel 6A is the Lineage Recovery.
I would suggest using a tool like Titanium Backup. That allows the saving and reinstating of apps.
Booting a custom recovery requires unlocking the bootlader, which I don't want to do now.
Titanium backup requires rooting as well...
Thank you for the suggestions but I'm counting this one as lost.
You won't be able to directly write to the /data/data/com.your.packagename folder without root. The only options I can think of are
1. Using adb backup... backup your app data from your old phone and restore it to the new phone
Bash:
To backup
# adb backup -noapk com.your.packagename -f backup.adb
To restore
# adb restore backup.adb
2. If the app in question is debuggable, you can assume the application permission and access the folder
Bash:
# adb shell
bluejay:/ $ run-as com.your.packagename
bluejay:/ $ cp -r /storage/emulated/0/Download/backup/* /data/data/com.your.packagename