Related
Here you go! Ripped straight from my article: How To: Remove AT&T From Captivate.
Instructions
WARNING: I am not responsible for any bricked, messed up, ruined devices. You modify your phone at your own risk. These processes are not necessarily safe for your Samsung Captivate or any other device.
Root the Samsung Captivate
First things first. You’ll need to root your device to continue with many of the modifications listed below. For our “How to Root the Samsung Captivate” guide, click here. It’s very very easy. Even a total noobie can do it! If you have questions, post a comment and we’ll get back to you A.S.A.P. Look below if you get the idea, check out our “How to Root the Samsung Captivate” guide if you don’t.
Download Update.zip
Plug in your Captivate to your computer. When the phone notifies you that the USB has been plugged in, scroll down your notifications bar and click on “USB connected: Select to copy files to/from your computer.”
Click “Mount”
Now, you’ll probably see a popup telling you a new USB drive has been inserted, open it up on your computer. In Windows, click “Open folder to view files.”
Drag Update.zip into the Captivate USB drive (on the top level… do not navigate into folders)
Turn off the Captivate (Power Off)
Hold down the Volume Up/Down rocker and the power button until you see some action. Your phone is now booting into recovery.
Use the volume down button to scroll down to “Reinstall packages”
Click the power button to select that option
Enable App Sideloading
AT&T has some weird reservations against app sideloading. That means, AT&T Android users can not use any apps not downloaded on the Android Market. Have no fear! You can remove this restriction easily. Check below for the basic instructions, or click to go to our “Enable Captivate App Sideloading” guide.
BusyBox Installed
Samsung Captivate with root
SQL Database Manager
We suggest trying the SQLite plugin for Firefox, you can find it here.
Turn on USB debugging: Settings >> Applications >> Development
Plug in your Samsung Captivate
Open up Command Prompt on your computer (Windows: start, search, type “cmd”, right click cmd, Run as Administrator)
Type in: cd _____PATH TO ANDROID SDK FOLDER______\tools
Example: cd C:\Users\USERNAME\Desktop\android-sdk-windows\tools
Type in: adb shell
Type in: su
Type in: cp /dbdata/databases/com.android.providers.settings/settings.db /sdcard/settings.db
Type in: cp /dbdata/databases/com.android.providers.settings/settings.db /sdcard/settings.db.backup
Type in: exit
Type in: exit
Type in: adb pull /sdcard/settings.db %userprofile%\desktop
Leave Command Prompt open
Open SQLite Manager in Firefox by pressing Tools >> SQLite Manager
Click “Database”
Then click “Connect Database”
Navigate to “settings.db” on your Desktop
Expand the tables
Click “Secure” on the panel
Scroll down to ID 6, “install_non_market_apps”
Double click it and change “value” from 0 to 1.
Close SQLite Manager
Go back to the command prompt window, type in: adb push %userprofile%\desktop\settings.db /sdcard
Type in: adb shell
Type in: su
Type in: cp /sdcard/settings.db /dbdata/databases/com.android.providers.settings
Type in: chmod 777 /dbdata/databases/com.android.providers.settings/settings.db
Type in: reboot
Disconnect your Captivate from your computer while your phone reboots.
Remove AT&T Bloatware Apps
Must have root and BusyBox installed before performing this process!
Open up Android Market and search/download “Titanium Backup”
Make sure your phone is not “Mounted” with USB
Open Titanium Backup
Press the Backup/Restore button
Click on each app and press un-install if you’d like to get rid of it. Do not delete apps off of this list, unless you know it is safe! This deletes these potentially forever… so be sure about things!
Delete-able:
AT&T Navigator
AT&T Radio
AT&T Maps
AT&T Music
AT&T Mobile Hotspots
Mobile Banking
Mobile Video
Where
YPmobile
AT&T FamilyMap
Mini Diary
MobiTV
Write and Go
Remove AT&T Market Restrictions
Market restrictions? What? You mean AT&T really censors what apps I can and cannot see on my Samsung Captivate? Yes they do. But, no problem. Android developer Andrea Baccega has developed an app called "Market Enabler" to remove the censorship by emulating the T-Mobile market on the Samsung Captivate as well as other devices. Instructions below if you've already got root access:
Download “Market Access” and install the latest version of the APK file on your Captivate.
Don't know how to install .apk files? Copy the file to your phone and then install "Apps Installer" or "Astro File Manager" from the market. It's easy! Just double click the .apk when you find it!
Close the Market down fully. If you were running the Market previously, reset the phone so it is not a running task. Or use a task killer and end the Market app.
Open up the Market Access application and go to "Backup value" in case you need to get back to the AT&T market
Then click "Providers" and find: "T-Mobile [US]"
Click and hold that option until it says "Emulate "T-Mobile" SIM?" -- click "Yes" there
You may have to Allow Market Access in Superuser Permissions
Click back to "Settings" click the checkbox next to "Emulate on boot"
All done. Now your Market is uncensored.
Remove AT&T and/or Samsung Logos on the Device
Not quite yet! Check back later. We are working with some chemistry-experts to see if we can dissolve those logos. Have you seen how sexy the Captivate is without logos? Click here to check out the video.
Credits
Big thanks to the XDA-Developers forum users for all their hard work on posting Captivate guides. User: nbs11 – bloatware removal. User: clubtech – market censorship removal application. User: blackjackboy – original root guide. User: kirbo20 – app sideloading.
Thank you for compiling all this in a FAQ WT fasion.
Sent from my AOSP on XDANDROID MSM using XDA App
got everything to work... except the Swoosh
Ok heres is what happened. I started on this whole guide and got hung up somewhere in the middle. I had to use Root Manager and SQLite Editor. Got everything but the AT&T Boot Swoosh sound off. I realize that this is not the exact post for the swoosh sound, but here goes. whenever im using the /sdcard command at the end of my command, it will say that this is a read only file system. it was writing to the sd card at one point, then somehow stopped. Any suggestions on how to fix this?
ThePatient said:
Ok heres is what happened. I started on this whole guide and got hung up somewhere in the middle. I had to use Root Manager and SQLite Editor. Got everything but the AT&T Boot Swoosh sound off. I realize that this is not the exact post for the swoosh sound, but here goes. whenever im using the /sdcard command at the end of my command, it will say that this is a read only file system. it was writing to the sd card at one point, then somehow stopped. Any suggestions on how to fix this?
Click to expand...
Click to collapse
you can either delete it from system/etc/PowerOn.wav
or you can install silent boot
http://www.androlib.com/android.application.com-antweb-silentboot-BnqC.aspx
Anyone try to remove the AT&T Address Book app yet?
I remember seeing this....and would be incredibly happy if this was possible!
kennethpenn said:
Not quite yet! Check back later. We are working with some chemistry-experts to see if we can dissolve those logos. Have you seen how sexy the Captivate is without logos? Click here to check out the video.
Credits
Click to expand...
Click to collapse
Great write up, still hoping we can remove that logo
decepticon said:
Great write up, still hoping we can remove that logo
Click to expand...
Click to collapse
Now only if I can remove the AT&T logo from the front of my phones screen at the top!
22 steps to enable sideloading, and you are still using a gui editor, this can be done in 8 steps shown here on xda-developers:
/showpost.php?p=7267391&postcount=1
Also, to remove the at&t/samsung boot animation you can delete (or rename) the file /system/media/bootsamsung.qmg however this leaves the at&t white "world phone" screen on longer and then a black screen for the rest of the boot process. Haven't found anything that will edit the .qmg file (which was used on the samsung moment and the galaxy spica as well), also placing a bootanimation.zip in this folder after removing the bootsamsung.qmg does not work(although it does on the samsung moment).
not sure how i'm still a new user and can't link websites when I've been a member since 2008...
shad0wf0x said:
22 steps to enable sideloading, and you are still using a gui editor, this can be done in 8 steps shown here on xda-developers:
/showpost.php?p=7267391&postcount=1
Also, to remove the at&t/samsung boot animation you can delete (or rename) the file /system/media/bootsamsung.qmg however this leaves the at&t white "world phone" screen on longer and then a black screen for the rest of the boot process. Haven't found anything that will edit the .qmg file (which was used on the samsung moment and the galaxy spica as well), also placing a bootanimation.zip in this folder after removing the bootsamsung.qmg does not work(although it does on the samsung moment).
not sure how i'm still a new user and can't link websites when I've been a member since 2008...
Click to expand...
Click to collapse
It's just very detailed. Takes like five minutes to do...
Nice job kenneth. If I were you id take a look at the guide I wrote on the subject in general. Nb added stuff and did edits. Feel free to use the info there to simplify your own guide.
Sent from my Samsung Captivate using XDA app
You didn't really explain how to uninstall the AT&T applications. How is this done?
raid0422 said:
You didn't really explain how to uninstall the AT&T applications. How is this done?
Click to expand...
Click to collapse
Open Titanium Backup
Press the Backup/Restore button
Click on each app and press un-install if you’d like to get rid of it. Do not delete apps off of this list, unless you know it is safe! This deletes these potentially forever… so be sure about things!
Delete-able:
AT&T Navigator
AT&T Radio
AT&T Maps
AT&T Music
AT&T Mobile Hotspots
Mobile Banking
Mobile Video
Where
YPmobile
AT&T FamilyMap
Mini Diary
MobiTV
Write and Go
Does this mean that Titanium Backup is what you use to uninstall software? I looked at the description of it and it just said it was for creating a backup image.
OK, yeah it is. I just used it to uninstall everything.
Yes Titanium Backup can be used. I've updated the post to make things clearer... thanks for your feedback!
Sent from my Samsung Captivate using XDA app
Here is the stock Galaxy S startup animation and sound to get rid of the AT&T antenna animation and swish sound.
Thanks to emclondon in the Galaxy S forums for the upload.
Cool.. I will definitely refer to this thread when I get my captivate
when I type su it gets me permission denied...any ideas?
raid0422 said:
OK, yeah it is. I just used it to uninstall everything.
Click to expand...
Click to collapse
How?
Instructions:
Open Titanium Backup
Press the Backup/Restore button
Click on each app and press un-install if you’d like to get rid of it
OK after Pressing Backup/Restore there are only 5 options in the list (apparently for backing up)
Accounts
Applications Widgets
Bluetooth Pairings
Country, Language, Time zone
Wi-Fi Access Points
Where are the applications listed to uninstall?
There was an application called instantroot that roots HTC hero running 1.5 but until the software was upgraded nothing was done for the instantroot application. Do you have information about that? Is the developer still working on it?
rapsass said:
There was an application called instantroot that roots HTC hero running 1.5 but until the software was upgraded nothing was done for the instantroot application. Do you have information about that? Is the developer still working on it?
Click to expand...
Click to collapse
Not heard of it for a while, but this method at http://forum.xda-developers.com/showthread.php?t=726118 works on 2.1 fine with little issues.
Thanks but I'm still looking for a very easy way to do the root. I don't know why(may be I'm afraid) but I still hesitate to root my hero. I'll think about it again, thank again.
Following that link pulser gave will give the easiest way to root your hero.
Its thanks to that I'm able to root it with no problems whatsoever.
Good Luck!! Don't let yourself stay unrooted!!!
Ok. I'll try later as the villainrom web site is not reachable now.
rapsass said:
Ok. I'll try later as the villainrom web site is not reachable now.
Click to expand...
Click to collapse
Hmm. Are you having trouble too getting onto the site?
Here's the instructions as posted.
Hi all,
I believe I have managed to find a way to root the 2.1 RUU for GSM Hero, completely using the work of wag3slav3 over at XDA (http://forum.xda-developers.com/showthread.php?t=724741), so thanks to him
I took his Droid Eris root and used the correct files for our Hero, and thanks to daentech on IRC, we tested the process and it worked. Here are the conditions used in the test:
1) GSM HTC Hero installed with the 2.1 ROM based on RUU (on this occasion an update.zip was used, as the user involved didn't want to lose root obviously). That zip is unrooted and stock, taken straight from the RUU and converted to update.zip.
2) Booted into ROM, and enabled USB debugging. ADB was installed and set up on this machine, as per this guide - http://www.villainrom.co.uk/viewtopic.php?f=46&t=1735
3) Then downloaded this file: http://www.villainrom.co.uk/uploads/GSMRoot.zip
4) Extract it to a folder on your computer. Open the command prompt using Start > Run > cmd.exe (and press enter)
5) use cd to get into the folder you stored the extracted files.
6) Run the command "runindos.bat"
(If you use linux, put adb in your path folder, and then download this shell script: http://www.villainrom.co.uk/uploads/runinlinuxadb.sh and execute it as normal. Rest will be same as in windows. )
7) Ideally, the phone should sit there for a bit, with some things appearing on screen like
Files copied and permissions set, rebooting HTC Andriod 2.1
Your phone will now reboot into normal mode, then reboot into recovery mode
If it does not reboot the second time, wait 10 minutes and manually reboot and begin again
Your phone is now rebooting in Rooted Recovery mode, do a backup and load yourROMs
Click to expand...
Click to collapse
And it will reboot a couple of times. You will hopefully end up sitting in recovery with a blue 'care bear' in the background
If so, you now have a custom recovery installed. Do a nandroid, and flash a custom ROM like VillainROM 12 or whatever. You should now have root.
8) To further enhance the usefulness of recovery flash VR 12 from here: http://villainrom.co.uk/viewtopic.php?f=95&t=1807 which includes a modified recovery that wipes better than the stock Amon-Ra
If you don't get it to work, please post any errors or details of what happens, and copy and paste your entire command prompt window contents into a
Code:
[/quote] box in the forum window so we can see what's happening.
Hope this works
[size=3]PS. Here are some ROM links for you.
http://villainrom.co.uk/viewtopic.php?f=95&t=1807 - VillainROM 12 (Full Sense 2.1 ROM)
http://www.villainrom.co.uk/viewtopic.php?f=45&t=2844 - FroydVillain 1.1.0 (Vanilla 2.2 Froyo ROM)[/size]
[/quote]
If you can't download the file, get it from http://dl.dropbox.com/u/7618177/GSMRoot.zip
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Oh man thank you. I wonder if I must install ADB to root my phone. I ask this because I still can't reach villainrom web site to check this guide http://www.villainrom.co.uk/viewtopic.php?f=46&t=1735
rapsass said:
Oh man thank you. I wonder if I must install ADB to root my phone. I ask this because I still can't reach villainrom web site to check this guide http://www.villainrom.co.uk/viewtopic.php?f=46&t=1735
Click to expand...
Click to collapse
If you find the user btdag, his signature has the same guide, as he wrote it on both sites. I just use that link as it's easier to find.
pulser_g2 said:
If you find the user btdag, his signature has the same guide, as he wrote it on both sites. I just use that link as it's easier to find.
Click to expand...
Click to collapse
I would love to take credit for that guide but the user ante0 created it (such a simple method I overlooked). Here is it quoted. It is missing pictures but should make enough sense (i hope). It is highly recommended to have the latest HTC Sync installed (link in my sig) for this guide.
Tools needed:
Android SDK (Links below)
HTC Sync (Links below)
Winrar - to extract Android's SDK files.
Patience and time.
1. Getting ADB (Android Debug Bridge)
Okay. You now need to get ADB, which is a part of android's SDK. It can be obtained here http://developer.android.com/sdk/downlo ... indows.zip
or if it's updated when you read this you can go here http://developer.android.com/sdk/index.html and download it. Get the Windows version if you use a windows PC.
Next we need to "install" it. This is done by simply extracting it to your harddrive (Install WinRar, then rightclick on the zip file). I chose C:\android-sdk-windows\. (Actually I chose C:\, the folder in the zip is named android-sdk-windows, so it goes there by default.)
After that is done we are now done with the "installing" part.
2. Setting up environment variables (access adb from outside of \sdk\tools directory.)
Now that we have extracted all files we need to set up environment variables to make our lives easier.
I always do this, because if you don't you need to be in the sdk\tools folder at all times...
Okay, so here we go...
Windows XP:
Rightclick on "My computer" and select "Properties".
click on the "Advanced" tab in the box that appears, looks like the pic below.
Image
Click on the button named "Environment Variables".
Now, doubleclick on the text entry named "Path" in the lower list box.
at the end of it, enter "might\have\other\entries\before\;C:\Path\To\SDK\Tools".
In my "path" it looks like this ";C:\android-sdk-windows\tools\".
(";" is required at the start so windows knows it's a new entry.)
Click on OK to exit out of the dialog, then OK again to get out of My computer's properties.
Now we have it set up.
Windows 7/Vista:
This is similar to Windows XP's setup of environment variables.
Rightclick on "My computer" and select Properties.
In the System window that appears click on "Advanced System settings" located in the left list.
Click on the Advanced tab in the box that appears, then on the "environment variables" button.
Same thing here. Doubleclick on "Path" located in the lower list box.
At the end of it, enter "might\have\other\entries\before\;C:\Path\To\SDK\Tools".
In my "path" it looks like this ";C:\android-sdk-windows\tools\".
(";" is required at the start so windows knows it's a new entry.)
Now click on OK, then OK again to exit.
Alright, all set up!
3. Making sure USB works...
Use this guide: viewtopic.php?f=15&t=379
4. Using ADB
I won't list all commands you can use here. I will only list some examples...
Remember to plug your phone in your usb cable (I've forgotten sometimes... lol)
Start by opening a command prompt.
This is done by opening up the startmenu then click on "Run..." (Alternative way: Windowskey + R).
In the "Run..." box, enter "cmd" without quotes.
If you have some knowledge of using a cmd prompt you don't need to read the next part.
To navigate you mainly use the commands CD and DIR.
Here's an image of what it looks like
Image
C:\Documents and settings\jwork> tells you what your current working folder is.
To get out of it, use the command "cd ..".
This will go back one folder, so your new location will be C:\Documents and settings>
One more "cd .." will take you to C:\.
Now, lets say you have a folder named Images in C:\. To enter it you use "cd Images".
If you want to list all files in that folder, enter the command "dir".
Now you might have a image named image01.jpg in that folder, that you want to get to your phone.
Use the command adb push image01.jpg /sdcard/
It should notify you now if the push was successful.
You can check if the image is on your sdcard by using the command "adb shell ls /sdcard/".
That should conclude this guide...
One more thing, if you just enter "adb" it will show a list of all commands with descriptions.
Click to expand...
Click to collapse
Have you ever heard of Universal Androot? It is only one click away to root your hero2.1.
It's working on my hero.
Universal Androot? Never heard of it. But it looks great and easy. Can I also install another firmware after I root my device with it?
Can I install another firmware like FroydVillain 1.2.2 OTA on my hero after rooted it with this application?
If it installs a custom recovery image then yes you should be able to. If not try installing ClockworkMod and then installing AmonRA - once you have root.
You are the best. Thank you.
Application thread in the Nexus forum. Worked on my Hero 2.1 for instant root.
http://forum.xda-developers.com/showthread.php?t=747598
{
"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"
}
Background:
It all started with me often finding myself sending small files to my device, and quickly got sick of the constant enabling/disabling of USBMS on my old phone, which is quite slow with re-mounting the SD card(ZTE Blade).
I also quickly got sick of not being able to quickly transfer files from my PC to my tablets internal storage.
There are a few graphical interfaces for adb out there, but none was really what I wanted...
So I decided to attempt to code something myself, and here we are!
Info:
A graphical UI for "adb push" to quickly transfer files from your PC to any location on your Android device.
.... Thats what I planned when i started, and what the first 2 versions did...
Now it hosts a powerful File Explorer thats capable of doing everyday tasks such as copy, paste, rename, create folders, delete files and folders, as well as transfering files on its own.
Features:
The main application is capable of sending and receiving files, and installing APKs.
It also serves as the connection-manager as can connect to devices using either your USB Sync cable, or by using WLAN (req. an app on your device to enable wireless adb).
Finally, it hosts a few other functions such as reboot to recovery, reboot to bootloader and a plain reboot.
The Filebrowser is very similar to any other filebrowser you use everyday on your PC.
It can copy/cut and paste files and folders within the device, rename file and folders, create new folders, delete files and folders.
Highlights would be:
Browse the content of your device like you browse your PC's harddrives
Drag and drop files between your PC and your Android device
Move, copy, delete and rename files and folders
Limitations:
The main program does not detect case sensitive, which can end up with funny results if you push a file to "/removable/" instead of "/Removable/" for example.
ADB is only capable of sending 1 file at a time, but is capable of sending whole directories incl. subdirs.
In a future update, I will add the ability to send multiple files.
Getting started:
Everything should be self explanatory. Most of the buttons have tooltips that tells you what they do.
Basically you make sure USB Debugging is turned ON on your device, plug it into your PC and start Quick ADB Pusher.
If you are connecting using a USB Cable, the application should find it automatically.
If you're connecting through wifi, you will need to type the IP address in the dedicated field. Port only needs to be provided if you are using any other port than the standard 5555. The IP address will be saved, and you can select it from the drop-down list the next time you start the application.
Requirements:
An Android device.
Windows
.NET 3.5
USB Debugging turned ON.
Additional Recommendations:
Root
Busybox
Vulnerable Kernel or Custom ROM
Q&A
Q: My device is rooted, but the program says it cant get root access
A: You are probably on stock rom or kernel. Most shipped roms have root-access from adb blocked.
To check this: Open default.prop located in the root of your device ("/"). If ro.secure is set to 1, thats your issue. Note: Default.prop gets overwritten everytime you restart the device, so changing this file will do nothing.
Theres is an app available that can fix/bypass this: http://forum.xda-developers.com/showthread.php?t=1687590
Q: The cache didnt delete itself when I closed the app!
A: You have two choices here: Either delete the cache/ folder located in the same location as the adb pusher exe, or you can just open and close the program.
If the cache still wont delete itself, report it as a bug.
Q: I cant connect to my device over wifi!
A: Make sure you have an app on your device that enables wireless ADB and that its turned ON. I personally use adbWireless found on the Play Store.
Double-check you are attempting to connect to the correct IP and port.
Q: Whats the "Information" window good for?
A: Its actually a left-over debug window, but can provide you with useful information should a transfer fail. If nothing else, you can use it if and when you report a bug.
Note that the Info window only shows what the main program is doing. ADB Explorer works independently, and will not report anything to the Info window.
Q: Why do I have to click a button to switch between push, pull and install?
A: The program need to knows which adb command to run (adb push or adb pull), and having a button for it was the easiest way for me .
The install option is there because you might not always want to install an .apk, but rather store it on your SD card or something. I know I do.
Q: Why cant I send a whole folder to my device from the main program?
A: Old implementation, use the built-in ADB Explorer instead, which allows you to send whole folders.
Q: Whats the point in the main program, when the Explorer can do everything but better?
A: At the moment it still controls the actual transfers as well as the connections to your device(s).
The main program is, however, more or less untouched since v0.3, while the Explorer is constantly being updated. Therefore, the Explorer hosts more and better features.
I am concidering removing the main form, as its rather obsolete by now.
Q: I Have a question!
A: Feel free to ask in this thread, and I'll answer your question as best I can.
Q: Can I donate?
A: No, I dont feel this program is worth "paying for" and it wouldnt feel right to receive money for it in any form.
Hit 'thanks' and vote the thread 5stars instead
Q: I Found a bug, how do I report it?
A: Report it to me on this forum, either in the thread or through PM, and I'll make sure to look into it.
Just make sure to provide as much info you can.
And remember: I cant fix anything if I dont know about it! So dont hesitate reporting bugs.
Changelog:
v0.5 current version
First of all... v0.4.1 had 6570 views on the attachement alone. Not bad... :victory:
Added an awesome splashscreen! As those who have used this program before should know - the program takes a while to load. The splashscreen is visible during this load, so you know the program is actually starting.
The wifi-field has been redesigned. It now saves your IP adresses so you dont have to retype them every time.
Added an "X" button next to the wifi-field. This button clears the wifi-cache and removes all entries in the list.
Added my name with a link to this thread, Ive seen my program hosted at a few sites with no credit whatsoever. I dont mind anyone hosting it elsewhere, in fact Im happy it gets spread, but PLEASE at least give me credit for it.
Slight redesign
Added tooltips to both the main application and the Filebrowser
Filebrowser:
Renamed "ADB Filebrowser" to "ADB Explorer". It can do so much more than just view the files on the device, so this name is more fitting. I should think of a new name for the entire application as well... "Quick ADB Pusher" isnt even half the truth anymore
Added cache feature! Everytime you enter a directory youve already been in, the cache kicks in rather than asking the device for the content. Each device has its own cache (note: a wifi-connected device will have its own cache based on the IP, so if you connect to the same device using cable or another IP, the cache needs to be rebuilt).
The cache will update as follows:
When entering a new directory not currently present in the cache.
When you hit the refresh button.
When you rename a file/folder.
When you create a new folder.
When you paste a file/folder from the clipboard.
When you delete a file/folder.
When you transfer a file/folder to the device.
The cache will NOT update when you send a file from the device to your PC
The cache will get deleted upon application exit.
You can now cancel the contentlisting and go back by hitting "../", Backspace shortcut-key or the Back button. Added because some directories takes ages to load on various devices, and its not so fun rolling your thumbs when all you want to do is go back to the previous dir
Added "drag-drop" to the filebrowser - you can now dragdrop files and folders directly to the browser to send it(or install, if .apk) to your device. The cache will refresh upon completion. You can also drop files and folders FROM the browser to your PC!*
* this might not sound so special, but it was a ***** to implement. Dragging stuff to the browser - ~50 lines of code. Dragging stuff FROM the browser - a little over 200 lines of code... C# sure has its limitations...
Added "Grab" to the right-click menu. This will send the selected file/folder from your device to your PC.
In short, the filebrowser can do what the main application can, so you dont have to close the browser to send/recieve a file/folder. A loading thingy will appear over the browser while a filetransfer is in progress.
Added "Properties" to the right-click menu. This shows some info such as the size of the file, and even the total size of a folder (incl. sub dirs). If you select a folder with a lot of content/folders, it might take a while to calculate the size. Other things it show is where its mounted and what permissions the file/folder has. NOTE: Requires Busybox, and root for files and folders only accessible by root (duh!)
Added 3 warnings upon opening the browser: One to inform you if your device isnt rooted, one to warn you busybox is missing and one to warn you if your device is rooted, but ADB was unable to acquire it. None of these warnings will show if adb acquires root and busybox is present.
Added a textarea showing the used space on the device, based on the mounted partition (such as /data, /sdcard, etc). So dont be scared if the number jumps around while youre browsing - it just means youve entered a different partition. Click to switch between used and free space. Requires Busybox
The browser now remembers your last location and will not start from "/" everytime you open it. Memory is lost upon main program exit and when you select a different device.
Added "View file" (prev. unfunctional "Open" menu item) to the right-click menu. This allows you to view smaller files (up to 10MB) without permanentally save them on your PC. I have blocked larger files because the time it takes to transfer those files isnt worth it for just "a quick look". My devices transfers a 10MB files between 2 and 5 seconds(depending on device) - which I think is ok, so I set the limit there.
Tweaked and tuned to make the browser act somewhat normal for devices without root/busybox. Devices without root/busybox will miss out on quite a lot though And before anyone asks - No, I do not plan on making this program able to root your devices. There are plenty of tools for that already.
Fixed the shortcutkeys that only worked when they wanted to. In addition, several more shortcuts have been added.
List of currently supported shortcuts:
ctrl+x: Cut file/folder
ctrl+c: Copy file/folder
ctrl+v: Paste file/folder
ctrl+s: Grab the selected file/folder
shift+delete: Delete the seleceted file/folder
shift+n: Create a new folder
F1: View file
F2: Rename file/folder
You can also use the arrowkeys to navigate, similar as in explorer. cut/copy/paste only works within the ADB Explorer.
Added Forward and Back buttons. Works the same way ordinary back/forward buttons do. Also changed icon for Refresh
Added a Toolbar, containing more buttons such as "view file", "download", "upload", "delete"...
Added 2 eastereggs , one is easy to find. The other is well hidden, and actually serves a purpose Well actually, the latter isnt really an easteregg, but it should be hard enough for you mortals to find
Known issues:
You friends might rage and throw their IPhones at you when they see this
------
HTC Sync REALLY doesnt like ADB, so close that crap before starting this app, or better yet - uninstall it!
It seems HTC Sync is trying to start its own adb server, and is very persistant in doing so.
This results in Quick ADB Pusher and HTC Sync having a fight for their life on who is going to start the server.
------
If you install an .apk, then try to send something else, the program will try to install that as well. This is because I was retarded and forgot to add one check.
Solution: Close the filebrowser, untick "install apk". Will be fixed in the next version, I promise! :angel:
Version History:
v0.4.1 - 6570 views on the attachement alone. Not bad...
Fixed filebrowser not working on some devices, I hope. Please test this for me as the browser has always worked fine for me on all my devices.
Changed apk install method to use AndroidLib's method. It now tells you if the installation was successful or not.
... Some minor things I cant remember.
Note, the "Open" option in the filebrowser is just a placeholder for now, its not a bug that it doesnt work, it isnt ment to work.
v0.4
Fixed bug where files and folders containing "_(" threw a syntax error.
Added file browser for device (see Seperate notes).
Added wireless ADB support.
Added Pull-file mode.
Re-designed the UI.
Moved the info-view to 3rd tab. Im moving away from it more and more.
A lot of the text and button-text will now change depending on your current choices. Ex. the Send-button now switches between Send, Pull and Install.
A truckload of code rewriting and optimizations.
Added an additional check for Root remounting, which should fix rare cases where remounting fails (If your device cant be remounted as root, please report it along with your device, rom etc)
Added "Install APK" You can now install APKs directly through the program.
Added reboot options in the Advanced tab
Added device info in the Advanced tab (The temp seems to be reported in C * 10, so I report it as C / 10, let me know if it doesnt look right for your device, and dont forget to tell me what device/rom you're using)
Filebrowser Features:
Browse and select files.
Context menu (right-click menu).
Copy or move(cut) files/folders within the device.
rename files/folders on the device.
delete files/folders on the device. Warning: Deleting the wrong files might brick your device! Double-check that you really want to delete the file before doing so!
create new folders on the device.
icons for certain formats (more to be added).
progressbar for directory loading progress.
'clipboard' icon to remind you what you currently have selected for copy/cut.
Notes:
The filebrowser is in its early stage. I have bugtested it as much as I can and it works flawless with my 3 devices.
The speed of listing directoiess/files greatly differs with device. My TF101 lists the contents about twice as fast as my ZTE Blade, theres not all that much I can do about it, as I dont have the time right now.
When pasting a file in a location where a file with the same name already exists, the program will currently simply overwrite the file. I havnt had time to add a check for it yet (ETA: Next version).
---To be added:
Direct interacting/editing of files, such as text files etc.
cache-feature, to reduce the frequency of grabbing the dir. contents from the device (which will help speed up changing paths).
A "file exists" check when pasting, allowing you to chose to overwrite or rename the old file.
v0.3
Fixed program freeze when no device was connected.
Added device selection, so it should work with multiple devices connected. please test this for me
Rewrote most of the program to make use of AndroidLib.dll
Removed the console(debug) tab, as it served little to no use now
Added an 'Advanced' tab for future use
Cleaned up a lot of garbage code
Fixed system not mounting as R/W
Other minor changes and fixes
v0.2
First public release
v0.1
very first version I wrote, which was buggy and often froze and god knows all...
Trust me, it was terrible. It worked and did what it set out to do but... It was terrible...
The latest Version has been tested and bugfixed on the following devices:
ZTE Blade with Swedish Spring 5, connected through USB Cable
ASUS Transformer TF101 with Team EOS Nightly build 28, connected through WIFI
HTC One S with stock 4.0.3, no root, no busybox. USB Cable
HTC One S with stock 4.0.4, root, no busybox. USB Cable
HTC One S with stock 4.0.4, root, busybox. USB Cable.
-------------------
Suggestions for improvements, feedback etc are more than welcome
Thanks to:
regaw_leinad - for writing the very handy AndroidLib found here
Dont forget to hit 'thanks' if you like my application. Every thanks I get brings a smile to my face
Download:
If the attachment doesnt work, try this mirror (select version and hit ctrl+s, or file -> download)
i think making a batch file was easier
Hey, cool app. There does however seem to be a problem with XDA's attachment feature, and it only downloads about 1k of the zip, then says complete. Also, if you plan on extending this a little more, check out my .NET Android Library named... well AndroidLib. It will help you out a bunch with the coding of the features you want to add.
regaw_leinad said:
Hey, cool app. There does however seem to be a problem with XDA's attachment feature, and it only downloads about 1k of the zip, then says complete. Also, if you plan on extending this a little more, check out my .NET Android Library named... well AndroidLib. It will help you out a bunch with the coding of the features you want to add.
Click to expand...
Click to collapse
Thanks for the heads up.
I placed it on google docs, hopefully it works better
Linky
If it doesnt, perhaps you could give me a tip as to where to upload it. I used to have my own server so never really used any other file-sharing method
regaw_leinad said:
Also, if you plan on extending this a little more, check out my .NET Android Library named... well AndroidLib. It will help you out a bunch with the coding of the features you want to add.
Click to expand...
Click to collapse
O nice, Ill definitely check that out Thanks.
Goatshocker said:
Thanks for the heads up.
I placed it on google docs, hopefully it works better
Linky
If it doesnt, perhaps you could give me a tip as to where to upload it. I used to have my own server so never really used any other file-sharing method
O nice, Ill definitely check that out Thanks.
Click to expand...
Click to collapse
Yup, the new link works great! Unfortunately, when I don't already have an adb server running and hit the 'Check ADB Status' button, the form freezes and the process needs to be killed to close the program. Works fine when adb.exe is already running though.
---------- Post added at 12:26 AM ---------- Previous post was at 12:17 AM ----------
Killing adb.exe while it's frozen fixes the issue I pointed out, probably means there is an error in your
Code:
Process
code
EDIT:
Stalls on process.WaitForExit() when debugging
regaw_leinad said:
Yup, the new link works great! Unfortunately, when I don't already have an adb server running and hit the 'Check ADB Status' button, the form freezes and the process needs to be killed to close the program. Works fine when adb.exe is already running though.
---------- Post added at 12:26 AM ---------- Previous post was at 12:17 AM ----------
Killing adb.exe while it's frozen fixes the issue I pointed out, probably means there is an error in your
Code:
Process
code
EDIT:
Stalls on process.WaitForExit() when debugging
Click to expand...
Click to collapse
Thanks for the report,it seems to happen when theres no device connected. Silly me have only even tried the app with a device connected hehe.
I'll try to fix it later today
Goatshocker said:
Thanks for the report,it seems to happen when theres no device connected. Silly me have only even tried the app with a device connected hehe.
I'll try to fix it later today
Click to expand...
Click to collapse
ah, you're calling
Code:
adb get-state
that gets the state of the device connected.
My .NET Android library handles everything adb wise, it even uses it's own adb binary, so the user doesn't have to have the sdk for it to work. let me know if you're going to reference it with your app, and I'll put your project in AndroidLib's post of "Projects using AndroidLib"
regaw_leinad said:
ah, you're calling
Code:
adb get-state
that gets the state of the device connected.
My .NET Android library handles everything adb wise, it even uses it's own adb binary, so the user doesn't have to have the sdk for it to work. let me know if you're going to reference it with your app, and I'll put your project in AndroidLib's post of "Projects using AndroidLib"
Click to expand...
Click to collapse
Yep, I assumed that would work since it works fine if you do it directly in cmd. But guess not adb start-server didnt work either...
I think I'll leave the bug for now and start looking into your lib instead.
Really nice app
Do you plan to develop a Linux version ?
Great idea, thanks =)
How does it achieve rw access, since device-dependent?
For example, on some devices, in ADB shell, you use
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
But, in some, you use mtdblock3 instead of mtdblock0.
Since there's no setting on which mtdblock to use, how does the program know which one is correct?
Theonewithideas said:
How does it achieve rw access, since device-dependent?
For example, on some devices, in ADB shell, you use
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
But, in some, you use mtdblock3 instead of mtdblock0.
Since there's no setting on which mtdblock to use, how does the program know which one is correct?
Click to expand...
Click to collapse
adb remount does all the job as you are ultimately using adb..
the command which you specified is used to mount on device shell which you enter by adb shell
madman_amit said:
adb remount does all the job as you are ultimately using adb..
the command which you specified is used to mount on device shell which you enter by adb shell
Click to expand...
Click to collapse
Oh, so that's what it does! lol
Thanks.
Actually, when trying it out, it says, after starting daemon "remount failed, action not permitted"
Nevermind, will check the program, it seems easier...
Looks cool! I shall give this a try later and see how it does with my HTC Rezound.
Thank you for your work!
Wow, responses
Thanks for the feedback guys.
Unfortunely Ive kinda killed my sync cable for my TF (tried to convert it to a usb host adapter^^), and currently dont have any other android device to play with.
So development has kinda stalled right now. Ive got rid of the freeze-when-no-device-connected, but developed another issue instead. Not anything major, but very annoying. The app freezes while it checks for a device >_>, its only for a few seconds, but annoying nevertheless.
As for linux version... Im afraid thats way above my coding skills, and I dont have a linux PC to test on anymore (I killed the laptop which was running linux when I tried to build a touchscreen on it. Yes! I break a lot of things)
Awesome, just what I needed!
Could you please add an option to connect the phone using network?, with the "adb connect" command, I can use a bat file before starting the app but because I have several devices connected to the network the phone´s ip change in time, and having it built in the app would be great
Awesome work, just tried it out now and it's pretty awesome.
I think an adb connect option would be awesome, for those who have adb wireless app on there phone then it'll be really easy to transfer files and it'll be pretty sweet.
Anyway keep up the good work
Hey, just an fyi,
Code:
adb remount
will NOT work if the device connected does not have the option ro.secure=0 in the default.prop of the ramdisk. You shouldn't assume it does, because not all "ROM" developers know how to change it. My library does check for this, but in case you don't want to use it, be sure you can mount the filesystem /system as rw that way, or using the mount binary on the phone directly.
regaw_leinad said:
Hey, just an fyi,
Code:
adb remount
will NOT work if the device connected does not have the option ro.secure=0 in the default.prop of the ramdisk. You shouldn't assume it does, because not all "ROM" developers know how to change it. My library does check for this, but in case you don't want to use it, be sure you can mount the filesystem /system as rw that way, or using the mount binary on the phone directly.
Click to expand...
Click to collapse
Hey thanks for the info. I had no idea about that, remount have always worked on all my devices on all roms Ive tried.
I'll keep that in mind when Ive fixed my sync cable
Could you give an example of a device/rom combo remount does not work on?
Goatshocker said:
Hey thanks for the info. I had no idea about that, remount have always worked on all my devices on all roms Ive tried.
I'll keep that in mind when Ive fixed my sync cable
Could you give an example of a device/rom combo remount does not work on?
Click to expand...
Click to collapse
I can't think of a specific example, but if the developer does compile a boot.img with ro.secure=1, adb remount will not work but lots of 'devs' these days just grab the boot.img from people who actually know what they're doing, so you should be ok, just in rare cases, this will not work.
Unroot Razer Phone 2
This is the method that I used, I bought a phone that was rooted (little did I know) custom recovery was not installed on my device, but bootloader was unlocked and the phone was rooted. Disclaimer:I am no expert, i just used this method last night (2/2/2019) the Razer guides weren't the best at step by step so I am compiling what I learned from doing this. I am not responsible if you brick or bootloop your phone. You should also do independent research on XDA etc before you attempt this process so you understand the risks. I invite others that know more than me to correct what I may have missed and I will updated the OP.
Step 1
You need a USB C to A cord similar to the one that came with the phone, but Razer says that they don't recommend you use that one because it is designed for quick charge not data transfer so I used one that I bought on Amazon years Ago.
Step 2 you need to download 3 things:
The stock image that can be found here:https://developer.razer.com/razer-phone-dev-tools/factory-images/
You need to download Android SDK
https://developer.android.com/studio/releases/platform-tools.html
You need to download the drivers:
https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip
Also open this https://developer.razer.com/razer-p...02.1384856067.1549140743-333350818.1549140743
Unzip all of these files to a new folder on your desktop call it Razer Phone 2 or whatever.
I also went into the phone tapped build number repeatedly to enable developer options and turned on USB debugging.
On the device, go to Settings > About <device>.
Tap the Build number seven times to make Settings > Developer options available.
Then enable the USB Debugging option.
Step 3 you need to Open this PDF courtesy of Razer:
https://s3.amazonaws.com/cheryl-fac...stall_Android_Fastboot_Drivers_on_Windows.pdf
This document loosely tells you how to install the drivers follow through all of the steps they give you
It should be noted you see a reference to “Download Mode” there is no such thing also the easiest way to get to this screen is to turn the phone off plug the USB into the computer with the phone not plugged in then hold volume down and plug the phone into the computer and press the power button holding volume down you should be taken to a screen that looks like this (aka download mode): see the image I attached.
I had an issue when I got to the Have Disk portion once I got to the step I had to drill all the way down to the android_winusb.inf file located inside the usb_driver folder. Once i got that it finally showed me the Android ADB Interface and the following dialogue screens. (if you are scrolling through a screen of Manufacturer -Models looking for something then you are doing it wrong) Once it is installed the device Should not have the Android with a ? on the device manager screen it should now say Android ADB Interface. (this part took me almost 2 hours I got frustrated and had to walk away for a bit so dont give up)
You can test that the drivers have been installed correctly like they say in the document but they left a step out for the not as tech savvy people. The way to do it is to open up a command prompt. You will see the directory that is is pointing to is likely C:\Users\[Insert user Name]. We need to change the directory it is looking at by typing.
Cd C:\Users\[insertusername]\Desktop\razer phone 2\platform-tools
(the command cd changes the directory)
You should see the directory change to be looking specifically at that folder now. Now simply type fastboot devices. The command should run and you should see the serial number of your device in the command prompt. If it does not return this then the drivers are not installed correctly.
(some other guides said you should also run the command adb devices, but I never got that to return anything all it ever told me when i ran it was “List of devices attached” with nothing else.
Step 4
Setting the Environment
Once i got to this step I was a little scared because I have never dealt with this before this allows you to call the ADB commands from the command prompt without having to specify the specific folder these ADB commands are located.
Follow the document referenced above until you get to the step that says click New
Instead we are going to look in the section titled “User Variables for [InsertUsername]
Under this section you will see a variable called PATH click on PATH and click edit. A box should pop up and on the right side it should say New, Edit, Browse, Delete, Move Up, Move Down.
Click on New and specify the folder called platform-tools mine looked like this
C:\Users\[username]\Desktop\razer phone 2\platform-tools
Click on ok the box will close and then click on ok again all the boxes pertaining to the environment variables will close.
Step 5
Test that the environment is set up correctly.
You might remember in step 4 we had to open a command prompt and tell it to look specifically at the platform-tools folder to run the ADB commands. With the environment now set we no longer have to specify the folder to run these commands, we can call them from any directory. To test this open a new command prompt it will likely be pointing to
C:\Users\[Insert user Name]
With the phone still plugged in and in “download mode” and without changing the directory, type
fastboot devices it should return the serial number of the phone if the environment has been properly setup if it has not been properly setup then it will return this error.
fastboot' is not recognized as an internal or external command,
operable program or batch file.
Step 6 (im not sure if this is necessary)
Because I bought my phone used I used rootchecker app to ensure the phone was indeed rooted and “download mode” told me the bootloader was unlocked. I wasnt sure if I needed to unlock the critical partitions, but you will notice in the razer instructions right above flash system image they call for them to be unlocked. I simply opened a command prompt and typed:
fastboot flashing unlock_critical
It said they were already unlocked so I moved forward with flashing the system image.
Step 7
Install the system image
From here I followed the razer instructions when i got to the step:
“Navigate to the unzipped system image directory” you open a command prompt and type
Cd C:\Users\[insertusername]\Desktop\razer phone 2\aura-o-global-2009
What this allows you to do is run the flash_all script.
The flash all script uses the command fastboot which if you remember is in the platform-tools folder this is why we had to add the environment in the previous steps so that once we got to this step the flash_all script could find and run that command. I ran this and had no issues the phone will continue to restart and in the command prompt you will see it pushing all the files to the phone. After about 3-4 minutes the phone was at the Wizard. I continued following the guide to lock the bootloader
Reserved
Duplicate post
my phone is not detected in bootloader mode now. i just want to relock my bootloader and i am stuck now
thank you so much! I was almost giving up trying to fix my phone till i saw your post
LordCandyAndy said:
thank you so much! I was almost giving up trying to fix my phone till i saw your post
Click to expand...
Click to collapse
Same here this post was a god send.
The only issues I keep having is that it keeps saying waiting on device, I have uninstalled and removed everything and then reinstalled everything step by step and I keep getting waiting for device in cmd and ps.
any help would be great.
Thanks for the guide.
flash_all kept failing for me because it wouldn't allow fastboot from the ROM's folder. Copying the contents of my platform-tools (adb) folder into the ROM's folder fixed this issue for me. I'm assuming this is because I didn't set up the environment variables correctly.
Darkann said:
The only issues I keep having is that it keeps saying waiting on device, I have uninstalled and removed everything and then reinstalled everything step by step and I keep getting waiting for device in cmd and ps.
any help would be great.
Click to expand...
Click to collapse
I am having the same issue any help
Update: At the time of writing this, I completely forgot that I am running Linux Mint - Cinnamon 20.1 on my laptop, which connects the bluetooth with my phone just fine. However, it did NOT work when I booted into windows and tried it. I am not sure why this is, but just beware. I recommend that you look into it yourself and see if you can find a resolution that works for you if you aren't using a linux os.
Hi everyone, after using another guide on here by Marcos8760, I noticed that there were a lot of things missing from the steps layed out, and decided to create my own guide with every step that should be done to have a fully functional Razer 2 with Android 11 OS. I will be using a part of his guide in this tutorial, and the link to his if you want to check it out is: https://forum.xda-developers.com/t/guide-android-11-gsi-with-gapps-and-root-magisk.4216117/
**DISCLAIMER**
First, I am not responsible for any bricked devices or errors that occur. This is completely at your own risk.
Second, this OS is NOT supported by Verizon. If you use Verizon then this will not be able to work on your phone.
Third, MAKE SURE that you have backed up all your files and data before doing this, again, I am not responsible
for you losing your data, because you will lose it if it isn't backed up, and I have warned you to do so.
Fourth, any commands will be in '' quotes, do not type these into your own cmd window, they are just to indicate what the commands are.
Last, This is not a troubleshooting guide, I am not covering how to fix errors, only simply how to install and get working with the Android 11 GSI. If there are errors please try to do research and resolve them on your own.
Before we begin anything, we need a few tools. These are the download links to all the files you will need to complete this process.
1. You will need a program such as WinRar, 7zip, or my personal fav, WinZip, to be able to extract these files, make sure you have one of these installed before proceeding.
2. We need to have a backup of the stock firmware in case of any kind of bootlooping or other bricking that might occur that you can revert back to. Extract this.
Link: https://s3.amazonaws.com/cheryl-factory-images/aura-p-release-3201-user-full.zip
3. This is the link to the GSI we will be installing. If you want a rooted system, you need to download system-roar-arm64-ab-vndklite-gapps.img.xz file. This will allow you to install Magisk and enable Google's Play Protect which is what this guide will be about, of course you can choose your own, however you will have to figure out how to get play protect certified yourself. Extract This.
https://github.com/phhusson/treble_experimentations/releases
4. We need the kernel that allows TWRP to be installed, which is the file manager we will be using for some of the programs we need to install, as well as being able to boot the phone up during this process. Extract This.
https://github.com/francisrosario/a...load/4.0/TrinityKernel-kernel-r4-20200512.zip
5. This is a file system program used to write large scale data with much faster read and write speeds for Linux and Android systems alike. Here is a link to learn more about it: https://c.mi.com/thread-2487060-1-0.html
*DL link: https://arter97.com/browse/aura/f2fs/20190114/f2fs_fstab.zip
*Leave this as a zip file, you just simply need to save it.
6. Here is the link to the latest Magisk version. (Needed to root the device) Leave as zip file.
https://github.com/topjohnwu/Magisk/releases/tag/v21.3
7. We need a program called VoLTE Fix-It. This is needed to enable your mobile network and data for LTE on this GSI.
*https://github.com/KhushrajRathod/VoLTE-Fix
*Just press the green 'Code' button and download as zip. Leave this as a zip file as well.
8. We need the Android ADB Driver to be able to enter commands to install everything.
https://developer.android.com/studio/run/win-usb Click download zip, accept agreement, and download and extract.
9. We need Android SDK Platform Tools to be able to run fastboot and adb commands. Extract this.
https://developer.android.com/studio/releases/platform-tools
10. Lastly, (I promise), you need the Qualcomm Android USB Driver. The link explains why. Extract this and go through the setup and install.
https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
Now we can begin the process.
First, copy all of the files in the aura-p-release folder, and paste them into the platform tools folder where all of those files are. Then enable USB debugging on your phone. Go to settings, click on About Phone, scroll to bottom and tap "Build Number' 7 times. You are now in dev mode. Search in the search bar for usb debug, tap it, then enable it and select allow.
To install the Android ADB driver, right click on start (Windows icon in bottom left of task bar), select device manager. Then we need to go into fastboot mode. Hold both volume buttons and power button down, be patient, it takes a second. When the screen goes black immediately press and hold the Volume down button for at least 3-5 seconds until a screen comes up that has an option to 'Restart Bootloader' at the top. Now we can install the driver. You should have device manager open, an option called 'Other devices' should come up, with Android that has a yellow exclamation mark by it. If it doesn't, unplug and replug the phone's usb, and it should. Once that shows up, right click and select update driver. Select Browse computer, select Let me pick. Show All devices should be selected, if not, go ahead and do so, then click next. Select 'Have Disk', Select Android ADB Interface, click browse and go to the folder where you downloaded the ADB driver, then select 'android_winusb' and click ok. Click ok again, a warning will come up, you don't need to worry it is needed to install this OS, so go ahead and click yes. It should install, you can close out when it is finished.
Next, in file explorer open the folder with all of the platform tools and aura-p-release files. Erase what is in the address bar, and type 'cmd', press enter. This will open a command prompt window in this location. Now, type in the cmd window, 'fastboot devices' and a serial number should show up. If not, then you have done something wrong or missed a step and need to uninstall the driver and go back into fastboot mode and do it again, or refer to the last disclaimer I made. Now, if the serial number did show, we can proceed. First we need to unlock the bootloader (if it isn't already) to be able to root and install. Type in the cmd window 'fastboot flashing unlock' and press enter, a confirmation should pop up on the device, use the volume buttons to navigate and the power button to select and confirm. When thats done, type in 'fastboot flashing unlock_critical', again a confirmation should come up so just do the same.
We can get into the meat of the installation process now.
You should still be in fastboot mode. In the cmd window, type 'fastboot flash system' and drag and drop the system-roar file you downloaded and extracted in file explorer into the cmd window.
Your command will look a little something like this: fastboot flash system C:\Users\user\Desktop\system-roar-arm64-ab-gapps.img
The file path will be different depending on where you downloaded the image to.
Wait until it says complete or something similar like done and has no errors. Then, its time to flash the kernel. Navigate to the where you downloaded the TrinityKernel file, open it. There should be a .img filed simply called 'boot.img'. Go back to your cmd window, and we will be typing in: "fastboot flash boot" then drag and drop the boot.img file, like you did with the system file, again, wait until it says done or complete and has no errors.
After that is done, use the volume buttons to select restartt bootloader with your power button on your phone. When it reboots, go to recovery mode, check never show this screen, and swipe where it says to swipe. Go to the wipe menu and then tap on format data. Type yes and then press enter/ok. Go back to your computer and open file explorer.
Next, copy and paste the f2fs zip file using windows explorer into the Razer 2's internal storage.
Head back to your phone, and press install. Scroll down until you find the zip file and press it and install it. (ignore the errors that may or may not be there) After that go back to the TWRP home screen, button that looks like a house at the bottom in the middle, go to the reboot menu, then reboot into recovery. When it reboots, go to wipe menu, and tap on format data and type in "yes" and tap ok again. Click on "don't install" because you don't need the TWRP app on your phone.
Next we need to install magisk to enable google play protect cert and have a rooted system. Just do the exact same thing that you just did with the f2fs file, except do not format data this time.
Select mount and check all the boxes. Go back to home page and select install, scroll to magisk and swipe to install.
Now, this is where you have to make a big decision. Bluetooth on this rom is a fickle son of a gun. I have tried to make it work on a pc that doesn't have bluetooth software built into it for a very lengthy amount of time, trying all sorts of things. The only way I could get it to connect is by setting it as a device to control with my keyboard and mouse. Maybe you will have better luck, but I have confirmed that the bluetooth works on devices with already built in bluetooth software. It works perfectly on my laptop and in my car. So, if you want to proceed with this, then I will tell you, if not, you can skip over it.
Select advanced on the home menu, go to file manager, select vendor then overlay. delete BOTH the bluetoothcommon.apk and razeraurabluetooth.apk.
This step applies to those who skipped the bt part as well. Go back to home, select reboot and click system, when it reboots, select allow usb debugging, DO NOT DO ANYTHING ELSE. THIS IS CRITICAL. Go back to your cmd window and type "adb devices", a serial number should show, then type the following cmds in order: "adb root", "adb shell", "mount -o remount,rw /", "mv /bin/resetprop_phh /bin/phh-resetprop" - if this one gives an error saying its in use, don't worry, just do the next cmd, which is "phh-securize.sh"
If the 3rd cmd gave the error, the last cmd will ask if you want to confirm it, click y for yes for each option it gives, it should go thru and the device should reboot.
Now then, it may seem slow during set up, but set it up like normal. Everything should be well and good. after you finish setup, to enable better fps, go into settings, select phh settings, select misc features, scroll down to and click on 'force fps', select the last option to have 120fps, but you have to do it twice because for some reason it doesn't change to the very last option the first time.
Now, we have to setup your mobile network with volte, it is a program that allows LTE coverage from your carrier to enable data on custom gsi roms. Now, go to the volte fix it zip file in file explorer, copy paste to the phone's internal storage. Go into fastboot mode, select recovery, it will boot into twrp. Do the same thing as the other zip files, install then select and swipe. Now press home button and select reboot, click system. Go to phh settings, click ims features, check the boxes on the bottom 2 options, click on create ims apn, it wont do anything, then click install ims apk, when it is done a notification will pop up on the bottom that says to reboot, you may now reboot the phone. Once it is booted up, go to network and internet, select mobile network, change pref network type to lte, then enable volte. You should have full service of your mobile network.
There are a few last things. The default camera sucks, I've tested some from the play store, and YouCam is by far the best free camera you can get from there. 2nd, to enable the backlight on the Razer 2, download and install logo+ apk, grant it root perms, and you can select the effects and colors you want it to be. This should be everything to get you going on the gsi. If you want to do custom things like custom boot animations or alarm sounds or whatever, download either root browser or pay for root explorer on the play store, and you can look up how to do whatever you want and you can do it through one of those. There it is. Enjoy the new os and have fun with it!
**IF YOU DO RUN INTO A BOOTLOOP OR ANY SORT OF BRICKING, RETURN TO FASTBOOT MODE BY HOLDING POWER, AND HOLD VOL DOWN WHEN THE SCREEN TURNS BLACK. You can go into platform folder, find the flash_all.bat file, double click and it should bring the phone back to original stock, and you can start over. IF YOU HAVE ANY OTHER ERRORS DURING THIS PROCESS PLEASE TRY TO FIND THE RESOLUTION YOURSELF. This is NOT a troubleshooting guide.**
Nice guide!
The link in Step 4 is broken.
hey i am attempting to install VOLTE because my data works just fine, but i cant make any calls from my phone. I get the error `mobile network is not available` but my data not connected to wifi works. Any ideas. I followed your instructions to a T. i am also on verizon RP2 on Havoc OS if that helps
Thank you Ahead of time!