It's good practice to run a full backup of your ROM and user data every once in awhile, in case you flash something and get into a bootloop. Thanks to TWRP's scripting capabilities, we can trigger a weekly backup.
Prerequisites
Root Access
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Instructions
Create a new Profile named TWRP Backup.
Create a Time context, and choose a time at night you want the TWRP backup to take place. For me, I made it at 4:00AM. To pick a single time, check both "From" and "To" and put the exact same time in both.
No need to name the task anything, just enter its configuration.
Code --> Run Shell. This is the code you'll need:
Code:
chmod 0777 /cache/recovery
echo "wipe cache\nwipe dalvik\nbackup SDBOM weeklybackup \ncmd reboot" > /cache/recovery/openrecoveryscript
Be VERY sure that this is typed exactly as such! Tick "Use Root" and then exit.
Files --> Delete Directory. Delete the TWRP/BACKUPS/YOURDEVICEUNIQUEID/weeklybackup. Check "Recurse." In order to get your device's unique ID, you need to simply navigate to TWRP/BACKUPS using any file explorer. You should have already made a previous backup, as TWRP will automatically create this folder. (Note: since you likely don't have a weeklybackup folder already here, it will likely fail the first time. You can easily just skip this action and make a backup once with this name, and then it'll work from then onwards).
Plugin --> Secure Settings. Go to Root Settings --> Reboot Options --> Reboot Recovery.
Exit out the task editing, and now add a few more contexts to make the backup run at an appropriate time. I added a power context so it only occurs when my phone is charging; I added a date context so it only runs on Sunday; and I also added a WiFi connected context so it only occurs when I'm at home.
That's it! This should satisfy the average TWRP user. MAKE THOSE BACKUPS!
I've been meaning to try to found out how to do this.
Thank you
For me it doesn't work
It's boots to recovery
Then it bootloops with message
"formatting cache using ext4"
Edit* I'm on 6.0.1 with TWRP 3.0
It works flawlessy, awesome! Thanks op
Reboot Recovery in Secure Settings is a PRO option!
Are there any decent alternatives to TWRP these days?
bjoswald said:
Are there any decent alternatives to TWRP these days?
Click to expand...
Click to collapse
Not really the thread to ask this question..
Could search for phillz it's available for select devices (but TWRP is better) and thats about it..
Giblet-dono said:
Reboot Recovery in Secure Settings is a PRO option!
Click to expand...
Click to collapse
Instead of using secure setting pro option, can't we just use run root shell command reboot recovery command?
No idea.. what I DO know is that this script gave me a hang on boot :<
Make a complete backup before running the script for the first time!
I am not sure yet why, but maybe someone (OP?) can help me out here..
I'm using an HTC One M8 with Marshmallow rom (ViperOneM8) which is stock HTC Sense based.
I use TWRP 2.7.8.0
Guess this doesn't work so well if you have secure boot enabled requiring a pin/passphrase.
So as I stated above this worked pretty well for me (it made the backup, rebooted me), but if I now go into tasker the "make-backup"-profile is gone?! This seems pretty pointless, if I have to set up the whole thing every time I use it ^^
Follow_and_Feel said:
So as I stated above this worked pretty well for me (it made the backup, rebooted me), but if I now go into tasker the "make-backup"-profile is gone?! This seems pretty pointless, if I have to set up the whole thing every time I use it ^^
Click to expand...
Click to collapse
Obviously you need to exit Tasker once, to save the profile. If you enter all actions in the task and run the task manually, it'll restart your phone without Tasker having saved what you've done.
Arstoien said:
Obviously you need to exit Tasker once, to save the profile. If you enter all actions in the task and run the task manually, it'll restart your phone without Tasker having saved what you've done.
Click to expand...
Click to collapse
Oh haha thank you! Stupidity at its best :laugh: thanks
I do my backup to a usb-otg drive though. What do I need to modify in this profile to make sure that the backup gets stored only on the otg drive and skips entirely if no otg drive is mounted?
Giblet-dono said:
No idea.. what I DO know is that this script gave me a hang on boot :<
Make a complete backup before running the script for the first time!
I am not sure yet why, but maybe someone (OP?) can help me out here..
I'm using an HTC One M8 with Marshmallow rom (ViperOneM8) which is stock HTC Sense based.
I use TWRP 2.7.8.0
Click to expand...
Click to collapse
Did you try to wait longer? I thought mine also bootloop-ed until I remember that the wipe cache & wipe dalvik command would cause the phone to take a while to load. I waited around 10 minutes.
---------- Post added at 05:18 PM ---------- Previous post was at 05:18 PM ----------
bagarwa said:
I do my backup to a usb-otg drive though. What do I need to modify in this profile to make sure that the backup gets stored only on the otg drive and skips entirely if no otg drive is mounted?
Click to expand...
Click to collapse
Did you try: http://wiki.rootzwiki.com/OpenRecoveryScript
---------- Post added at 05:22 PM ---------- Previous post was at 05:18 PM ----------
@MishaalRahman I found that you don't have to chmod 0777 in the beginning and you don't have to use "Secure Settings".
I tested to touch the file in tasker and it created the file just fine.
In regards to Secure Settings, I added the task code -> run shell -> 'reboot recovery'
Contivity said:
Did you try: http://wiki.rootzwiki.com/OpenRecoveryScript
Click to expand...
Click to collapse
That was very educational. Thanks for the link.
Do you know what would be the path for usb-otg?? Would the command be mount usb-otg or something different?
Also, I don't see an option of backing up vendor partition. I do need to backup that, because without that, a restore causing unlocking issue. (Nexus 6P)
Lastly, does Tasker have a way to detect whether a usb drive is plugged in? I would like to add that as one of the trigeers.
bagarwa said:
That was very educational. Thanks for the link.
Do you know what would be the path for usb-otg?? Would the command be mount usb-otg or something different?
Also, I don't see an option of backing up vendor partition. I do need to backup that, because without that, a restore causing unlocking issue. (Nexus 6P)
Lastly, does Tasker have a way to detect whether a usb drive is plugged in? I would like to add that as one of the trigeers.
Click to expand...
Click to collapse
OTG Path - I won't know and can't test right now
Tasker detect USB - you can do a file test and set the variable. then you can use that as trigger or if clause.
bagarwa said:
Lastly, does Tasker have a way to detect whether a usb drive is plugged in? I would like to add that as one of the trigeers.
Click to expand...
Click to collapse
Try using a file explorer to view the path with the usb plugged in. That's what I did to get the full path of my sd card for this to work properly. So far, so good.
---------- Post added at 01:29 AM ---------- Previous post was at 12:33 AM ----------
MishaalRahman said:
[*]Code --> Run Shell. This is the code you'll need:
Code:
chmod 0777 /cache/recovery
echo "wipe cache\nwipe dalvik\nbackup SDBOM weeklybackup \ncmd reboot" > /cache/recovery/openrecoveryscript
Click to expand...
Click to collapse
I don't have much experience with running scripts. Is it safe to leave out the "/nwipe dalvik" part? I assume that would just skip wiping Dalvik?
FYI here are my additions to the Profile:
• Instead of only Sunday, run it every day but execute the backup only if the last backup is at least 1 week old. This removes the chance of having a backup too old because you weren't home Sunday, or you weren't charging that night, etc.
• When booting (only if rebooted from the profile) enter the sim pin code, so you wouldn't miss any emergency phone calls/sms
• If next clock alarm is too soon (say closer than 3 hrs), then don't start a backup
• Log the time and date of backups to a custom log file.
• If by any chance the screen is on while Profile conditions are met, delay the backup by 15 min, so no work is accidentally lost.
If anyone's interested, I'll leave more detailed info on each of the points.
...
Related
Team,
This One-Click Root process will copy over the rooted-update.zip or unroot-update.zip file then reboot your phone. Follow the instructions in the CMD prompt that launches.
Credits:
LeshaK at Samdroid: for the original rooted-update.zip.
gunnarhafdal : for creating the Mac GUI for my app.
This has been tested on stock Android 2.1 Eclair only. If you rooted using another process you can use this process to unroot as long as you didnt load a rom that created links to busybox.
For the following models:
GT-I9000
Captivate SHG-I897
Vibrant SGH-959
GT-I9000M
Epic SPH-D700 (Untested but should work like other phones. Post with your results. This is harmless it will either work or it wont. It copies over 3 files to your existing build.)
Rooting adds the following to your system and unrooting removes them:
/system/xbin/busybox (version 1.17.1)
/system/xbin/su
/system/app/Superuser.apk (version 2.3.1)
and links /system/bin/su to /system/xbin/su
More will follow as they are released. PM me to add your Galaxy S Model.
Warning: I am not responsible for bricked phones, rooting can void your warranty....
PC Instructions:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download the app: GalaxyS_One-Click_Root_All_Models-PC. Or down Below.
Watch the video for the full procedure on The Unlockr.
Video/Procedure Link Click Here
Requirements: Install Link: Dot Net Framework version 4
Rooting Instructions:
1. Make sure your phone is on USB Debug mode: (MENU > Settings > Applications > Developement > USB debugging = Checked )
2. For Windows x86 and x64 systems make sure that the Samsung Drivers are installed. You can get them here.
3. Extract the contents of GalaxyS_Vibrant_One-Click_Root.rar to a folder.
4. Connect your phone to your PC via the USB cable and launch the file "T-Mobile Vibrant One-Click Root.exe" file.
5. Click the "One-Click Root" button. This will launch a command shell follow the instructions in the CMD window.
Mac Instructions:
Download the app: OneClickRootMac. Or Down Below.
It requires Mac OS X 10.5 or higher.
Rooting Instructions:
1. Make sure your phone is on USB Debug mode: (MENU > Settings > Applications > Developement > USB debugging = Checked )
2. Connect the phone to your computer.
3. Click one of the buttons depending on what you want to do.
4. After the phone has rebooted into recovery select "apply sdcard:update.zip" for I9000 and I9000M and choose "Reinstall Packages" for the US models using the volume keys and then press the home button for I9000 and I9000M and the power button on the right top side for US models to start the process.
=====================================================================
Done! You are rooted.
=====================================================================
Un-Rooting Instructions:
To Un-Root follow the same instructions except click on the Un-root button. If you rooted using another process you can use this process to un-root as long as you didnt load a rom that created links to busybox. I would suggest to restore you phone back to stock ROM before even needing to unroot and if you are on stock un-root all you want otherwise what is the point of un-rooting.
=====================================================================
Getting Started with Android After Rooting:
Flash Clockwork Custom Recovery On your phone:
Follow this URL to find fill information on ROM Manager:
http://forum.xda-developers.com/showthread.php?t=734164
Install ROM Manager from Market.
Launch ROM Manager and click on Backup ROM and save you android O/S stock rooted making getting back to stock un-rooted much easier..
the simplest root just got simpler
So is this actually faster? Or just "easier" not to mess up...
sounds like more work than just DLing, moving, and renaming with your phone... expecially for those without a comp...
anyway, this method has been added to the sticky in dev section..
junkdruggler said:
So is this actually faster? Or just "easier" not to mess up...
sounds like more work than just DLing, moving, and renaming with your phone... expecially for those without a comp...
anyway, this method has been added to the sticky in dev section..
Click to expand...
Click to collapse
I'd say its easier to not mess up. Faster for sure, if you already have the drivers installed.
This is for our newer brethren or anyone else that want a straight forward root method. And for those having trouble entering recovery from the button presses. ADB is bundled in the rar file so you don't need Android SDK.
Another thing that will help most is when I add unroot to the app which I should have completed tomorrow.
Doon2 asked for it, so here it is.
I appreciate the effort and skill...
BUT, how is this easier than downloading a file directly to your phone, renaming it and putting it at the root of your sd card and going to recovery?
s15274n said:
I appreciate the effort and skill...
BUT, how is this easier than downloading a file directly to your phone, renaming it and putting it at the root of your sd card and going to recovery?
Click to expand...
Click to collapse
Good question because that is what I do. Just an alternative method. The upcoming unroot will probably be more helpful to some.
But this method will help some for sure. It will download it to your phone for ya and put you in recovery. Well most of the other phones have it so why not ours.
Someone made the request and here it is. I will also be adding other tweaks to the app over time and useful info after rooting to this thread.
Sent from my SGH-T959 using XDA App
TGA_Gunnman said:
Good question because that is what I do. Just an alternative method. The upcoming unroot will probably be more helpful to some.
But this method will help some for sure. It will download it to your phone for ya and put you in recovery. Well all most of the other phones have it so why not ours.
Someone made the request and here it is. I will also be adding other tweaks to the app over time and useful info after rooting to this thread.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
this
I am stoked that someone would take the time to make this program. I dont have immediate access to a PC(I use a mac) but an easy unroot program clinches the decision to root my phone. thank you for taking the time to make this much props
please do it for Mac OS.
best wishes...
Awesome application thanks!
Sent from my SGH-T959 using XDA App
Great, easy app. Works!
Wish I had seen this a few hours ago! Just spent 30mins trying to get the button presses right to get into recovery mode before I finally got it.
alsatea said:
please do it for Mac OS.
best wishes...
Click to expand...
Click to collapse
Sorry I don't have a Mac to dev/test on. Neither do any of my friends. But, I will see what I can do.
Can't you dual boot windows on your Mac?
TGA_Gunnman said:
Sorry I don't have a Mac to dev/test on. Neither do any of my friends. But, I will see what I can do.
Can't you dual boot windows on your Mac?
Click to expand...
Click to collapse
If you write it in java, then it will run any OS, right?
Relase src code. I may be able to port to unix/macosx and/or java.
I have Windows 7 installed through Bootcamp and it worked perfectly. Thanks
kelmerp said:
If you write it in java, then it will run any OS, right?
Click to expand...
Click to collapse
Ok Let me see what I can do.
Yeah release the source... Ports will follow if necessary
jganyard said:
Wish I had seen this a few hours ago! Just spent 30mins trying to get the button presses right to get into recovery mode before I finally got it.
Click to expand...
Click to collapse
I know what you mean. I'm still used to holding down the buttons until the recovery screen pops up like on my G1. On the Vibrant, I have to remind myself to let go of the buttons as soon as the "Vibrant" screen comes up.
Yes, the overall process involved to use this program is longer, involves more steps, and, therefore, easier to screw up. Also, the fact that you have to download more than one file increases the chances of messing something up because of the possibility of corrupted files. Also, the "flash in recovery" method is OS agnostic, and technically doesn't even require a computer since you can download and rename the zip file right on your phone if you want to. Still, it's very easy to follow and would appeal to those who are new to rooting and don't feel comfortable with booting into recovery mode.
Updated the app to include unroot. Created a new update.zip file that will remove root. Also fixed the CMD shell launching minimized.
Lets see the java port. or even an APK to do so
jganyard said:
Wish I had seen this a few hours ago! Just spent 30mins trying to get the button presses right to get into recovery mode before I finally got it.
Click to expand...
Click to collapse
Why fuss with button pushes, just enable debugging, plug in your phone, open a command prompt and type the following
Code:
adb reboot recovery
It's easier than messing with those buttons I assure you.
QtADB is an app based on adb. It requires working android sdk (command “adb"), Qt libs version 4.7, ROOT and busybox installed on phone.
Features:
File manager
copying files and dirs between phone and computer
removing files and dirs
creating new dir
and other
App manager
installing apps[/B]
removing apps
creating backup of apps with data
restoring backups of apps with data
Shell
opens android shell
Screenshot
take screenshot of your device
save screenshot to png file
Fastboot
flash bootloader, radio and recovery
boot recovery
Recovery
nandroid backup/restore
wipe data
flash rom
wipe battery stats
fix uid mismatches
Reboot
to bootloader
to recovery
normal reboot
Settings
set font used by app
set starting paths (or remember paths on exit)
and other
Logcat
Automatically detects phone (device, fastboot and recovery mode)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download QtADB for windows, linux & mac os.
Connect with Cable and WiFi
Download adbWireless scan with Barcode App
really great app. surprised no ones posted about it. i see there has been updates in a while cuz there looking for devs to help. one problem i have is my phones apps only show up if i have an app moved using the system move to sd, i use link2sd. when i view system apps they all show.
Nice app. Everything works well except the sms-tab. I allways get an error.
But I have one question: what setting does this app modify on my phone when i toggle wifi connection? It works, but when i toggled wifi, I cant swith back to usb-connection and also cannot mount my SD to windows anymore..
doumer said:
Nice app. Everything works well except the sms-tab. I allways get an error.
But I have one question: what setting does this app modify on my phone when i toggle wifi connection? It works, but when i toggled wifi, I cant swith back to usb-connection and also cannot mount my SD to windows anymore..
Click to expand...
Click to collapse
Have you got QtADB.apk installed and running when you try to access the sms-tab?
ah no, wasn't running. sometimes the solution is so simple ^^
thank you
doumer said:
Nice app. Everything works well except the sms-tab. I allways get an error.
But I have one question: what setting does this app modify on my phone when i toggle wifi connection? It works, but when i toggled wifi, I cant swith back to usb-connection and also cannot mount my SD to windows anymore..
Click to expand...
Click to collapse
Got the same question, except not for the sms part, the wifi function screw me up.
help would be appreciated
Edit: problem resolved, download the apk, enable and disable the wireless adb on your phone, change connection type to diskdrive and solves the problem.
hey all,
FAQ on the official site solves 99% problems You can find there some info about using WiFi connection, SMS Manager and more.
burimii said:
QtADB is an app based on adb. It requires working android sdk (command “adb"), Qt libs version 4.7, ROOT and busybox installed on phone.
Features:
File manager
copying files and dirs between phone and computer
removing files and dirs
creating new dir
and other
App manager
installing apps[/B]
removing apps
creating backup of apps with data
restoring backups of apps with data
Shell
opens android shell
Screenshot
take screenshot of your device
save screenshot to png file
Fastboot
flash bootloader, radio and recovery
boot recovery
Recovery
nandroid backup/restore
wipe data
flash rom
wipe battery stats
fix uid mismatches
Reboot
to bootloader
to recovery
normal reboot
Settings
set font used by app
set starting paths (or remember paths on exit)
and other
Logcat
Automatically detects phone (device, fastboot and recovery mode)
Download QtADB for windows, linux & mac os.
Connect with Cable and WiFi
Download adbWireless scan with Barcode App
Click to expand...
Click to collapse
good one mate I use this app for one year or so, and it's amazing
Finally... exactly what I was looking for.
Can't thank you enough for posting this. I've been rooting around for a good all-in-one toolbox for a while. Blows DroidExplorer, etc., out of the water.
Any possibility you could add some more tags to improve other's chances of finding it? I'm certain there are lots more folks looking for exactly this kinda tool.
hey so this seems like a good use of getting around some bugs for usb mount... but quick question, im trying to open the QtADB.exe file, and then it asks me for the path to adb and aapt binaries. I've installed the adroid-sdk package, so where do I point the directory to? my android sdk path is on c:/-program files (x86)- Android. The FAQ doesn't really help in answering questions...
awesome tool!
wifi connection doesnt work.. i downloaded the apk and tried connecting but didnt work..
The most awesomest PC app for android ever! Sammy better learn something from you, and FAST!
dr. xp55 said:
hey so this seems like a good use of getting around some bugs for usb mount... but quick question, im trying to open the QtADB.exe file, and then it asks me for the path to adb and aapt binaries. I've installed the adroid-sdk package, so where do I point the directory to? my android sdk path is on c:/-program files (x86)- Android. The FAQ doesn't really help in answering questions...
Click to expand...
Click to collapse
Point it to the exact directory in which adb and aapt are found should be something like c:/program files (x86) - android/tools
Sent from my HTC Desire HD using Tapatalk
I've been using this for a while now and it works great, very useful via wifi. Thanks!
I was looking for something like this for some time. Awesome app, thank you!
It stops responding whenever I try to copy a file from the device. P6800 CWM
Dont open Qt-Adb site, contains Trojan Redirector
nice man, tnx
After much anguish, I finally started it, nice app.
Cant connect my phone to QTADB via usb or wifi
Hi,
I cant seem to connect my phone to QTADB via usb or wifi. Tried checking the faqs but no answer there.
Can anyone help?
The SoupKit
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is SoupKit? At it's heart, SoupKit is for those who are tired of messing around with Windows and are ready to do try something that works. It was created to be "sort of" modular in that after the ADB installer has been installed, other Linux scripts can be installed and run from the command line by just typing the name of the script and without worrying about changing directories or dealing with permissions. It's intended to make the transition from Windows to Linux for Android a little bit easier.
How does it work?
The SoupKit ADB Installer --- FOR ALL KINDLE FIRES
This puts everything where it needs to be, installs any necessary dependencies, installs drivers, configures Linux to run adb and fastboot commands, puts the SoupKit in your $PATH and cleans up after itself, all while taking a fraction of the space needed for the Android SDK. What this means for you is, you will be able open any terminal window and start entering adb or fastboot commands immediately. There's no need to change directories, add sudo commands or certain operators that are confusing to command line newbies ( ./ ). You can enter commands just as you see them in tutorials. No more worrying about “ADB Offline”, “Status Unknown” or “List of devices attached ????????????????”. This alone can make a huge difference for anyone having Kindle Fire problems that can't be fixed in Windows or those who are overwhelmed by the technicalities of configuring Linux for Android.
What you need:
First, you need Linux. Don't worry, it's not as bad as you may think.
Luckily, all Linux distros are free to download and install on your computer. It can also be booted from a USB flash drive so you don't have to wipe out your current OS (although you probably should anyway). You can use a VM, but the only VM that I've found that can detect the Kindle Fire in fastboot mode is Parallels. Vmware won't cut it, and VirtualBox sure as hell won't cut it so don't waste your time with them if you ever need to do anything in fastboot (if you're bricked, you need fastboot).
Probably the best method to get Linux running for a new user is by setting up a Linux LiveUSB.
I'm not going to teach you how to set up a Linux LiveUSB, but there are plenty of FREE programs out there that will not only create a Linux LiveUSB for you, but will download your choice of distro as well, and all you need is a USB flash drive (preferably 8GB or larger). A Google search of “Linux LiveUSB” will offer plenty of choices, although, PendriveLinux seems to be a favorite among most. Just be sure to add plenty of “persistence” (1 or more gigabytes) or you will lose everything every time you reboot. And the better quality of flash drive you can use, the better it will be in the long run. Some flash drives just don't do well and can cause some file system corruption over time (not something you want to be dealing with while you're having Kindle Fire problems).
You'll also have to figure out how to boot your computer from a USB. Check your computer's BIOS manufacturer website for instructions on how to do this.
If you're using a LiveUSB, there is no root/sudo password, just hit enter.
Do not use a USB 3.0 port
Once you have Linux installed and booted, you need to make sure your Internet is working. It may take some configuration on your part but it is necessary for the SoupKit to install properly. Luckily, once you have an Internet connection in Linux, the hard part is over.
Don't put the SoupKit.zip on the USB drive before creating the LiveUSB. Instead, use the web browser to navigate to this page and download it once you have Linux running and your Internet connected. Once it's downloaded, you'll likely find it in your Downloads folder.
SoupKit has been tested extensively on all the latest versions of Ubuntu and Mint, but it hasn't really been tested on anything outside of that. Try other distros if you will, but be warned.
To install:
Right-click the “SoupKit.zip”, select “Extract here” open the SoupKit folder and follow the instructions in the README.
Credits:
Don't worry. I didn't forget about you guys. I'll finish this when I have time. In the meantime, you know who you are, and thank you.
Is that all?
NOPE. What SoupKit would be complete without a little something to go with it? SEE POST #2
Due to recent updates, I've decided to remove the option to install Hashcode's 2nd bootloader. There are too many areas where things can go wrong so I think it would be best to let the user follow the small handful of instructions in the 2nd bootloader thread to get it done. IMO, it is not worth the risk to rely on the user to make sure a downgraded stock bootloader is installed before running the script. Plus I think using a script toinstall the downgraded bootloader gives users a false sense of safety in what is potentially very dangerous to do.
ROOT PLUS for 2nd Generation Kindle Fires
That's right. This works for ALL 2nd generation Kindle Fires.
What does it do?
The screenshot above should answer that question pretty quickly.
What do you need to know?
Since Hashcode's bootloader hack is device specific, you must download the version for your device. Each one has the exact same script but the stack, boot and recovery images are different for each particular device. You must have the SoupKit installed for this to work properly. It installs in the same way as the SoupKit; unzip, double click, run in terminal, blah blah.
Make sure you have ADB enabled under “Security” in the settings.
Anything else?
At any point after installation, if you need to run the utility again, just type "rootplus" in the terminal.
What's next?
I have a few more things in store for you guys and they will all be made for the SoupKit. As packages are installed, just type the name of the package in any terminal to launch them at any point (hence "modular"). Everything will be easy to install, easy to launch, and new user friendly.
Don't be skerrd. Move out of your comfort zone a little and give Linux and SoupKit a try. I'm sure you won't be disappointed.
Credits:
* Bin4ry - of course, for providing the root exploit
* Dees_Troy - for Team Win Recovery
* prokennexusa and his team - for testing this out on all of the second generation devices
* Thepooch - for extensive testing and always being there to lend a hand
Downloads:
SoupKit - http://d-h.st/PbX
RootPlus for all Kindle Fires - http://d-h.st/jOe
Changelog:
04-23-2013 - Update (RootPlus)
* Removed option to install Hashcode's 2nd bootloader, for safety reasons. There is absolutely nothing wrong with Hashcode's 2nd bootloader. The risk lies in recent updates from Amazon.
03-19-2013 - Update + bugfix (RootPlus)
* Fixed issue with 2nd bootloader install - everything works as it should now
* Added timestamp to saved partitions. Gives users the ability to save more than one set of partition images
03-18-2013 - Update: (RootPlus)
* Changed how 2nd bootloader is installed for compatibility with the KF2
* Added ability to update custom recovery. No need to update the script every time a new recovery is released.
* Added ability to choose partition images to be installed if more than one set exist in the BACKUP folder
* More intuitive restore of saved partition images - will hopefully prevent any chance of user error
03-16-2013 - Bugfix: (RootPlus)
* Fixed issue with permissions on the rootplus script
03-10-2013 - Update: (RootPlus)
* Added extra safety measures, including MD5 check on 2nd bootloader install
02-23-2013 - Initial release
I actually wish I needed this because god damn this is a sexy piece of kit.
Thanks soup
Sent from my Amazon Kindle Fire2 using xda app-developers app
Awesome. So glad to see the kf1 devs working for us over here!
I'll probably never need this, but there are MANY who will find this useful.
Thanks soupmagnet!
--
Sent from my Kindle Fire 2, CM 10.1
Wilkinsss said:
this is a sexy piece of kit.
Click to expand...
Click to collapse
Oh, I see what you did there...
soupmagnet said:
Oh, I see what you did there...
Click to expand...
Click to collapse
Well I don't need it I have adb and fastboot running fine on linux already but I still downloaded it anyways, just because I can.
Update 3-10-2013: Added extra safety measures, including MD5 check on 2nd bootloader install
I seem to have installed the soupkit correctly, I followed the instructions. I also installed the root plus in the same manner, but when it installs it just disappears. When I type rootplus in terminal it tells me "permission denied"
It also gives me command not found when I try to open soupkit.sh
thanks
2strokenut said:
I seem to have installed the soupkit correctly, I followed the instructions. I also installed the root plus in the same manner, but when it installs it just disappears. When I type rootplus in terminal it tells me "permission denied"
It also gives me command not found when I try to open soupkit.sh
thanks
Click to expand...
Click to collapse
That sucks...I'll have to fix that. In the meantime you can enter the following in terminal to fix the permissions:
Code:
sudo chmod a+x ~/bin/SoupKit/files/rootplus
Then you should be able to start it by entering "rootplus" in the terminal with no problem.
Sorry for the inconvenience.
[Edit:] There have quite a few downloads since the last update. Has anyone else had this problem?
soupmagnet said:
That sucks...I'll have to fix that. In the meantime you can enter the following in terminal to fix the permissions:
Code:
sudo chmod a+x ~/bin/SoupKit/files/rootplus
Then you should be able to start it by entering "rootplus" in the terminal with no problem.
Sorry for the inconvenience.
[Edit:] There have quite a few downloads since the last update. Has anyone else had this problem?
Click to expand...
Click to collapse
That worked like a charm! Thanks for all you do!
---------- Post added at 02:35 PM ---------- Previous post was at 02:11 PM ----------
I hate to be such a noob, but, I got the thing rooted and now trying to install the bootloader and TWRP, this is as far as I have gotten. Hasn't done anything in about 10 minutes. I've toggled ADB.
Verifying MD5 Checksum...
blaze-stack.img: OK
Checksum matched
Installing stack...
95 KB/s (4096 bytes in 0.041s)
0+1 records in
0+1 records out
4096 bytes transferred in 0.002 secs (2048000 bytes/sec)
Rebooting...
< waiting for device >
---------- Post added at 02:41 PM ---------- Previous post was at 02:35 PM ----------
I exited the terminal and re-ran option 6, this is what it gives me now:
blaze-stack.img: OK
Checksum matched
Installing stack...
93 KB/s (4096 bytes in 0.042s)
0+1 records in
0+1 records out
4096 bytes transferred in 0.001 secs (4096000 bytes/sec)
failed on '/system/etc/install-recovery.sh' - No such file or directory
Rebooting...
< waiting for device >
There may be something off with the timing. In original testing on my KFHD 8.9, that was caused from the script entering the command to reboot too fast. I had the script pause for a second or two before rebooting which seemed to help (or I thought I did). I'll look into it a little further to see if I can make it work better. The error you get on the second time you run the script is because the first time you ran it, that file was renamed so it wouldn't exist the second time around.
[Edit:] Just hold the power button to shut down and then reboot while the script is sitting at "waiting for device"
Hi Soup,
I installed soupkit, I installed rootplus. The terminal just disappears but I assume it installed correctly. What I am trying to figure out is this:
Make sure you have ADB enabled under “Security” in the settings.
I am running Ubuntu Precise. I don't see anything under Settings about Security or about enabling ADB. Can you help me out a bit? Thaks!
[Edit] I had to: sudo chmod a+x ~/bin/SoupKit/files/rootplus too to get a terminal window on rootplus. But it doesn't do anything when I press 1.
[Edit again] Nevermind... was stupid to think that the Security change was in Ubuntu, I found it on the KF.
empoy78th said:
Hi Soup,
I installed soupkit, I installed rootplus. The terminal just disappears but I assume it installed correctly. What I am trying to figure out is this:
Make sure you have ADB enabled under “Security” in the settings.
I am running Ubuntu Precise. I don't see anything under Settings about Security or about enabling ADB. Can you help me out a bit? Thaks!
[Edit] I had to: sudo chmod a+x ~/bin/SoupKit/files/rootplus too to get a terminal window on rootplus. But it doesn't do anything when I press 1.
[Edit again] Nevermind... was stupid to think that the Security change was in Ubuntu, I found it on the KF.
Click to expand...
Click to collapse
Yeah, sorry about that...I'm working to get the permissions fixed now so I can upload a new working version. Barring distractions (yeah right), I should have a new one up within the hour. If nothing else, it will be fixed by the end of the day.
soupmagnet said:
Yeah, sorry about that...I'm working to get the permissions fixed now so I can upload a new working version. Barring distractions (yeah right), I should have a new one up within the hour. If nothing else, it will be fixed by the end of the day.
Click to expand...
Click to collapse
Thanks soup! Just to give you an update (although I think you are working on this already), when I press 1 on root plus, I end up on <waiting for device> although the KF2's finished rebooting. I tried the previous suggestion about holding down the power button and re-launching rootplus, but it didn't resolve it.
I will gladly test your new version. Thanks again!
---------- Post added at 11:39 AM ---------- Previous post was at 11:22 AM ----------
empoy78th said:
Thanks soup! Just to give you an update (although I think you are working on this already), when I press 1 on root plus, I end up on <waiting for device> although the KF2's finished rebooting. I tried the previous suggestion about holding down the power button and re-launching rootplus, but it didn't resolve it.
I will gladly test your new version. Thanks again!
Click to expand...
Click to collapse
Another question if I may:
When you have shell updates, does it use the same folder on the same partition? I am not quite good at Linux yet, so cleaning up previous installations is not my strength at all. Thanks!
empoy78th said:
Another question if I may:
When you have shell updates, does it use the same folder on the same partition? I am not quite good at Linux yet, so cleaning up previous installations is not my strength at all. Thanks!
Click to expand...
Click to collapse
Assuming I understand you correctly,
I write the install script in such a way that updating to a newer version simply replaces what already exists, so there's no need to uninstall anything.
3-16-2013: Fixed issue with permissions on the rootplus script
soupmagnet said:
Assuming I understand you correctly,
I write the install script in such a way that updating to a newer version simply replaces what already exists, so there's no need to uninstall anything.
Click to expand...
Click to collapse
You understood it. Good to know. Thanks!
soupmagnet said:
3-16-2013: Fixed issue with permissions on the rootplus script
Click to expand...
Click to collapse
Do I download both soupkit and rootplus for updates? Sorry for the noob question.
In rootplus, options 1 and 5 worked for me. However, on option 6, I stay at <waiting for device>. Done it twice and also held the power button to no avail.
It seems as tho there hasnt ever been a sticky made for rooting the Gear 2 Neo, so here ya go(lets hope they make it a sticky).
youre going to need Odin and the tar.md5 file you flash in Odin to get this accomplished. No worries tho, its quite easy to do and the tar linked below works with every version attempted so far, and I've personally flashed all of the versions available on Sammobile.com.
WARNING!!! Do this at your own risk! If you mess it up, its on you, not me!!
download these 2 files
Odin 3.10
Gear 2 Neo tar.md5
the next best thing is to do is to create a folder on your desktop, name it whatever you like, and put those 2 files in it.
next, open Odin by right clicking and open as administrator.
there are some settings that can be changed in Odin, but leave them as they are for this.
click on the "AP" button in Odin and navigate to the folder on your desktop that has the tar.md5 file in it and double click on it to select it.
Go to your gear 2 neo and go to the gear icon. Scroll to the bottom and touch the icon with a lower case "i" in a circle, then check the box that says "USB Debugging"
connect a usb to micro usb cable to your computer and connect the charging dock to the watch, but do not connect the micro usb end of the cable to the cradle.... yet
press and hold the button on the Gear 2 Neo. It will present a menu asking if you want to reboot etc etc, but just keep pressing it. Itll eventually (about 8, or so, seconds later) turn the screen off for a second and then say "rebooting" At this point its critical that you rapidly press the button 5 times. No more, no less. It will then bring you to a screen that gives 4 options. Single press the button to navigate thru the choices and long press to select. The option you want is "Download"
Once the watch is in download mode, connect the micro usb to the cradle. Your computer will likely install some drivers and when its done, the top left box of Odin should show "Com:#" (the pound sign will be a random number of a com port your computer selected)
Next press the start button is Odin.
There will be a dialogue box on the bottom left of Odin that says what its doing and a progress bar that shows on the watch and Odin itself. This process should take around 70 to 90 seconds.
Once complete, the watch should reboot and you should now have root access.
The following posts will be reserved for instructions on how to add custom ringtones. The only supported file type for ringtones and message notifications is .OGG. Ill also include some notif tones im currently using myself because i think theyre HILARIOUS!!!
putting custom ringtones and notification sounds on the neo with stock firmware is done via SDB. Very similar to ADB, you use command prompt to push the tones to specific folders within the file structure of the watches internal storage.
Ok, so to add notification tones, you need to SDB into the filesystem of the watch
fist thing youll need is the SDK itself found here
Follow the install instructions on the page linked above and open a command prompt session, then navigate to the folder that the SDK is located in.
Next, youll need some tones. The notif tones need to be in .ogg format (there are many free tools online available to convert files from mp3 to ogg.) Word of warning here, dont make the notifs too long as the watch has a very limited amnt of space reserved for notif tones, and if you put too much in there, it could corrupt the existing tones. Here are a couple nice-n-short tones of Brak (from Space Ghost) saying woah, hey and dont touch me.
The one i use is Wilford Brimley saying diabeetuhs. (I need to say that diabetes isnt even slightly funny, but the way he says it is)
next thing after either creating your own files or downloading mine is to put them into the same folder that the SDK is located in (its just easier this way) and type the following commands
PHP:
sdb root on
then
PHP:
sdb push YOUR_RINGTONE.ogg /opt/share/settings/Alerts/
(but replace the YOUR_NOTIFICATION.ogg with the actual name of the file you want to inject to your watch)
id also like to stress the importance of not guessing at the commands, as in doing so, you can corrupt the existing tones and theyll not be recoverable on the device. To me, thats ok because the stock ones are lame anyways, but be forewarned
ringtones are basically the same process as above, but you push the files to a different location. Here is the code
PHP:
sdb push YOUR_RINGTONE.ogg /opt/share/settings/Ringtones/
as above, make sure to replace the "YOUR_RINGTONE.ogg" with the actual file name
reserved 3
reserved 4 (just in case i have MOAR fun stuff to add )
Have a question. The stock ringtones and notifications. Can those be removed? I would have asked elsewhere, but i believe you and I are the only ones in this ghost town of a forum. Thanks man.
Sent from my SM-N920P using Tapatalk
Thanks for the tutorial. My Gear 2 Neo was having issues with bluetooth, so I installed this new ROM with root and now it connects again.
fsunoles101 said:
Have a question. The stock ringtones and notifications. Can those be removed? I would have asked elsewhere, but i believe you and I are the only ones in this ghost town of a forum. Thanks man.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
yes you can. the command is something like "sdb rm /opt/share/settings/Ringtones/YOUR_RINGTONE.ogg"
and if that doesnt work try "sdb shell rm /opt/share/settings/Ringtones/YOUR_RINGTONE.ogg"
and to see whats in the folder "sdb LS /opt/share/settings/Ringtones/"
similarly, you might need to add a shell command to LS to see the contents of the folder you seek.
Also also, make sure to "sdb devices" and "SDB root on" before doing any of that stuff with usb debugging checked
youdoofus said:
yes you can. the command is something like "sdb rm /opt/share/settings/Ringtones/YOUR_RINGTONE.ogg"
and to see whats in the folder "sdb LS /opt/share/settings/Ringtones/"
Click to expand...
Click to collapse
Awesome. I will give it a try this evening. Thanks.
Sent from my SM-N920P using Tapatalk
fsunoles101 said:
Awesome. I will give it a try this evening. Thanks.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
not a problem. lemme know if you have any problems with it. ive removed most of my stock ringtones and alerts because i think theyre kinda dumb lol i just have space ghost, wilford brimley and some mario sounds on mine
Novakingwai said:
Thanks for the tutorial. My Gear 2 Neo was having issues with bluetooth, so I installed this new ROM with root and now it connects again.
Click to expand...
Click to collapse
No problem man. This section of the forum is a ghost town! Glad i could help
I know you said it takes 70-90 seconds for the rom to copy over, but mines been sitting here for almost an hour and it only moves a tiny bit every 10-15 minutes.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is it normal?
Not even slightly. Might want to try a different cable, USB port or computer.
Sent from my SM-G900P using XDA Free mobile app
uh oh!
so i found my gear 2 in a drawer the other day and decided to play with it. After flashing this thru odin it doesnt boot up. Everything in Odin showed it was good. How do i fix this now?
Can it even get to download mode?
Also, is it the gear 2 or gear 2 neo? The firmware posted was for the neo only
Yes I can get into download and it is the neo as well.
If you can get to download mode, then its likely a bad download. Try a fresh download and reflash in Odin. If that doesn't work, I'll grab the link from sammobile.com and try the flash from that download link
jwwolfe77 said:
Yes I can get into download and it is the neo as well.
Click to expand...
Click to collapse
Try downloading the firmware from here if the fresh download doesn't work.
http://www.sammobile.com/firmwares/download/46122/R381XXU0BOA2_R381OXA0BOA2_XJP/
If you can get to download mode in Samsung devices, you're not in trouble 99% of the time
youdoofus said:
Try downloading the firmware from here if the fresh download doesn't work.
http://www.sammobile.com/firmwares/download/46122/R381XXU0BOA2_R381OXA0BOA2_XJP/
If you can get to download mode in Samsung devices, you're not in trouble 99% of the time
Click to expand...
Click to collapse
youdoofus said:
If you can get to download mode, then its likely a bad download. Try a fresh download and reflash in Odin. If that doesn't work, I'll grab the link from sammobile.com and try the flash from that download link[/QUOTE
Ok. tried both and still nothing. It kinda does a boot loop a couple times and then the green just stayed black.
---------- Post added at 02:22 AM ---------- Previous post was at 01:50 AM ----------
so just to try, i flashed the android wear and that is working good. Id just rather have the tizenmod 3.0.
---------- Post added at 02:43 AM ---------- Previous post was at 02:22 AM ----------
HAHA!!!! i got it working.....the hard way. I flashed android wear, then the tizenmod full restore file and it worked after that. Everything is good. Thank you for all of your help.
Click to expand...
Click to collapse
Just unlocked and rooted my phone a few days ago and I made a nadroid backup with TWRP. Of course, that has taken up most of my storage and defeats the logic of having a backup somewhere other than the device being backed up.
It's been a few years since I last had a phone I could root. My last one could be mounted as a USB drive and any files easily taken off the phone. I could push it up to dropbox but even on a wifi connection with cable broadband that will take half a day.(the backup is like 5gb)
Is there an app I can use to push the file via the USB or even wifi to my PC?
nlinecomputers said:
Just unlocked and rooted my phone a few days ago and I made a nadroid backup with TWRP. Of course, that has taken up most of my storage and defeats the logic of having a backup somewhere other than the device being backed up.
It's been a few years since I last had a phone I could root. My last one could be mounted as a USB drive and any files easily taken off the phone. I could push it up to dropbox but even on a wifi connection with cable broadband that will take half a day.(the backup is like 5gb)
Is there an app I can use to push the file via the USB or even wifi to my PC?
Click to expand...
Click to collapse
Easy. Connect to PC via USB. Go to the TWRP folder, drag off the backup inside.
You do know how to connect to PC via USB cable, right? All your folders will show up like a flash drive. Look for TWRP.
How big is your backup? Something is wrong if it takes up most of your storage. I keep one or two backups on my phone all the time. Usually just one, as that's all I really need. I make a backup almost daily. In TWRP settings, you can choose level of compression. More compression will make smaller size.
ChazzMatt said:
Easy. Connect to PC via USB, Go to the TWRP folder, drag it off.
How big is your backup? Something is wrong if it takes up most of your storage. I keep one or two backups on my phone all the time. Usually just one.
Click to expand...
Click to collapse
That folder is empty and isn't the same folder as on the phone itself. I can't see the actual directory.
nlinecomputers said:
That folder is empty and isn't the same folder as on the phone itself. I can't see the actual directory.
Click to expand...
Click to collapse
OK, let's take one step at a time.
You made the backup with TWRP, right?
What version of TWRP are you on?
in the PC view, you will see all your folders. Inside TWRP will be the backup file.
No, the droid turbo doesn't support USB mode. It only supports MTP or PTP modes. If you going to be condescending at least know the product.
Sorry typo: doesn't support
nlinecomputers said:
No, the droid turbo does support USB mode. It only supports MTP or PTP modes. If you going to be condescending at least know the product.
Click to expand...
Click to collapse
Does or doesn't? Make up your mind.
I know the product so it's not being condescending. If have TWRP installed you should see the folder.
If that's a limit of Verizon stock ROM, then that's your fault.
You're saying Verizon stock ROM doesn't allow you to see the contents of your phone like a flash drive? That's a universal Android feature, so it's puzzling you can't see the folder.
Again, one step at a time... What version of TWRP are you on? Answer the question.
My backup is in /data/media/0/TWRP/BACKUPS
I can see that folder on my phone but not on the PC
nlinecomputers said:
My backup is in /data/media/0/TWRP/BACKUPS
I can see that folder on my phone but not on the PC
Click to expand...
Click to collapse
For the third time. What version of TWRP are you on?
TWRP is 287.
If that's a limit of Verizon stock ROM, then that's your fault.
Click to expand...
Click to collapse
How the **** is that? I'm not Motorolla I didn't make the phone.
You're saying Verizon stock ROM doesn't allow you to see the contents of your phone like a flash drive?
Click to expand...
Click to collapse
Yes. Common knowledge. https://www.verizonwireless.com/support/knowledge-base-117349/
nlinecomputers said:
TWRP is 287.
Click to expand...
Click to collapse
That should work. but go ahead and update to 3.0.
the reason I was asking is because a year ago there was an unofficial version of TWRP for Quark that worked with 4.4.4 but not Lollipop to see files on the PC. But 2.87 is official and works. Still go ahead and flash 3.0.
Now, when you connect to PC do you see the autoplay dialog pop up?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And if you see that, do you then see all the folders?
Inside that folder then is a "Backups" subfolder with the backup file.
Nope, that folder is empty. It is empty on my phone too. It isn't the same folder as /data/media/0/TWRP That folder is at /sdcard/TWRP
I'll redo the backup and plant the files there and see if they show up. But MTP doesn't show all files even in the folders that do show up.
IF you are not getting the auto play pop up dialog, then it means the proper Motorola drivers are not installed on your PC.
---------- Post added at 12:23 PM ---------- Previous post was at 12:22 PM ----------
nlinecomputers said:
Nope, that folder is empty. It is empty on my phone too. It isn't the same folder as /data/media/0/TWRP That folder is at /sdcard/TWRP
I'll redo the backup and plant the files there and see if they show up. But MTP doesn't show all files even in the folders that do show up.
Click to expand...
Click to collapse
Forget folder /data/media/0/TWRP
That has nothing to to do with seeing the folders on your PC as a flash drive.
Look at my screenshot above. You do not see any 0/data crap. It says "internal storage".
______
Are you getting the auto play pop up dialog? Do you have the proper Motorola drivers installed on your PC?
When you plug in the phone to your PC and it turns into a thumb drive, jump drive, flash drive, you will see all the media folders.
You shouldn't have to "plant" the backup anywhere.
I've added more screenshots above. But it will help if you answer the questions... do you see the auto play pop up dialog when you plug in the phone?
When I plug in my phone, in "My Computer", I see the phone model and beside it is a description "Portable Media Player". This means it's acting as a flash drive. What does yours say in the My Computer description?
Look at my screenshot above. You do not see any 0/data crap. It says "internal storage".
---------- Post added at 12:34 PM ---------- Previous post was at 12:23 PM ----------
Download and install these Motorola USB drivers:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
That may be your problem. Your smartphone is not being recognized as a flash drive properly.
Reboot the PC after installing the drivers.
Do you see the auto play pop up dialog?
---------- Post added at 12:40 PM ---------- Previous post was at 12:34 PM ----------
nlinecomputers said:
How the **** is that? I'm not Motorolla I didn't make the phone.
Yes. Common knowledge. https://www.verizonwireless.com/support/knowledge-base-117349/
Click to expand...
Click to collapse
No one else has that problem with TWRP installed. Everyone else sees their phone as a flash drive. But maybe they are on custom ROM?
No one else has that problem with TWRP installed. Everyone else sees their phone as a flash drive. But maybe they are on custom ROM?
Click to expand...
Click to collapse
Yep. MTP only shows the SDCARD directory on any phone. For a Droid Turbo, even with custom roms, that directory is emulated as there is no SDCARD on that phone.
The stock rom doesn't support USB mode. Phones that support that mode have that option in the USB connection menu. Your recovery program will not make any change on that. They are two separate OS environments.
Yes I have Moto drivers installed. Yes I get the popup(when I turn that feature on in Windows. I hate it so it is off on my machine by default) And yes I can see a TWRP directory but it isn't the same. Using root explorer, I can see TWO such directories and in two different locations. Again MTP mode only shows you the SDCARD directory of any phone. You can't get to the true /. So I can't see the /data directory and thus can't get to the default location TWRP put my files. Like I said when I get a spare moment I will move that location to the "sdcard" and try again. Thanks anyway talking to you let me work out what was going on so you have been a help.
nlinecomputers said:
Yep. MTP only shows the SDCARD directory on any phone. For a Droid Turbo, even with custom roms, that directory is emulated as there is no SDCARD on that phone.
The stock rom doesn't support USB mode. Phones that support that mode have that option in the USB connection menu. Your recovery program will not make any change on that. They are two separate OS environments.
Yes I have Moto drivers installed. Yes I get the popup(when I turn that feature on in Windows. I hate it so it is off on my machine by default) And yes I can see a TWRP directory but it isn't the same. Using root explorer, I can see TWO such directories and in two different locations. Again MTP mode only shows you the SDCARD directory of any phone. You can't get to the true /. So I can't see the /data directory and thus can't get to the default location TWRP put my files. Like I said when I get a spare moment I will move that location to the "sdcard" and try again. Thanks anyway talking to you let me work out what was going on so you have been a help.
Click to expand...
Click to collapse
All the Quarks have the same hardware, especially storage. While Verizon stock ROM may not support USB mode, I KNOW custom ROMs do.
go over to the Quark TWRP thread and ask...
If your problem is Verizon stock ROM, then maybe they can help you with workaround.
[RECOVERY][OFFICIAL TWRP 3.0.0-0][For all Quark][Moto Maxx/Turbo and Droid Turbo]
http://forum.xda-developers.com/mot...recovery-twrp-2-8-7-0-touch-recovery-t3180308
_____________
---------- Post added at 01:35 PM ---------- Previous post was at 01:28 PM ----------
I just went into ComputerFreak274 thread (stock ROM) and they see TWRP folders fine too.
computerfreek274 said:
Otg to flash drive auto mount in twrp fine. I use it all the time.
twrp also connects auto to windows and Linux just fine.
I did see it was buggy on Mac.
Click to expand...
Click to collapse
computerfreek274 said:
You do not have click USB under twrp. It is auto mounted in twrp it will show up in my computer a quark. That USB mount you see is if you had an USB flash drive like the new micro flash sticks.
You you do not see quark listed, go to device manager and see if you have an error on your driver. Seeing your on Mac you may have to search twrp Mac see if you find info. It works on windows and Linux just fine.
Go to reboot menu and hit reboot recovery and see if Mac mounts it there. Or on Mac load program "disk" and see if it is on the left side menu bar if it is right click and hit mount.
Click to expand...
Click to collapse
What he means is he is plugging in to the computer while in TWRP recovery -- and it auto-connects to his PC.
Whereas, I'm plugging in during regular Android CM12.1...
So, try his way. Boot into recovery and then plug in?
How are you doing it -- in Recovery or during regular ROM interface?
__________
---------- Post added at 01:41 PM ---------- Previous post was at 01:35 PM ----------
From the Quark TWRP thread:
mjc2251 said:
Does USB otg work on turbo? I just tried to mount an otg flash drive and it would not mount.
Edit: Nevermind I gave it a few more tries and got it working!
Click to expand...
Click to collapse
baybutcher27 said:
2# post update just in case more USB bugs...
Click to expand...
Click to collapse
Did you see the suggestions in this post? computerfreak274 drags off the TWRP files in Recovery. He's the dev for stock Verzon ROM with tweaks and TWRP works fine with stock Verizon ROM to see the files. It auto connects to Windows when the phone is in recovery mode. Have you tried that?
Also go to the TWRP thread.
ChazzMatt said:
All the Quarks have the same hardware, especially storage. While Verizon stock ROM may not support USB mode, I KNOW custom ROMs do.
go over to the Quark TWRP thread and ask...
If your problem is Verizon stock ROM, then maybe they can help you with workaround.
[RECOVERY][OFFICIAL TWRP 3.0.0-0][For all Quark][Moto Maxx/Turbo and Droid Turbo]
http://forum.xda-developers.com/mot...recovery-twrp-2-8-7-0-touch-recovery-t3180308
_____________
---------- Post added at 01:35 PM ---------- Previous post was at 01:28 PM ----------
I just went into ComputerFreak274 thread (stock ROM) and they see TWRP folders fine too.
What he means is he is plugging in to the computer while in TWRP recovery -- and it auto-connects to his PC.
Whereas, I'm plugging in during regular Android CM12.1...
So, try his way. Boot into recovery and then plug in?
How are you doing it -- in Recovery or during regular ROM interface?
__________
---------- Post added at 01:41 PM ---------- Previous post was at 01:35 PM ----------
From the Quark TWRP thread:
Click to expand...
Click to collapse
nlinecomputers said:
Is there an app I can use to push the file via the USB or even wifi to my PC?
Click to expand...
Click to collapse
This should work for WIFI transfer.
https://play.google.com/store/apps/details?id=com.pushbullet.android.portal
Sent from my XT1254 using Tapatalk
Accessing from TWRP instead of the normal phone allowed the hidden root files to be seen. It still only provides MTP access to the emulated SDCARD but that is enough to get the job done.. TWRP is root level and the normal file sharing isn't so I'm guessing that is the issue. A custom ROM probably gives full root access even from the phone.
Sorry guys I been off here for a bit been runing high fever and found out I have pneumonia. Thank you guys for stepping up and help each other. It is going to be a week or so before I am feeling better. We maybe able to have a custom build of marshmallow by the end of the month.
Twrp locks and hides backups after you exit twrp you must cope backups to your PC from twrp this info was listed and is also on twrp forums.
If anyone is still stuck with anything just PM me so I do not have to reply to stuff that may have already been fixed.
Thank you.
I to discovered the lack of access to the TWRP files in regular viewing when connecting the phone to PC. My solution was to move the file to 0/emulated using a file Explorer on the phone. Doing it from within TWRP, connected to PC is good to know.