Unless they are Developer editions there is no way they are unlocked if they are Verizon S5. If they are just an S5 that is unlocked this means they are a GMS phone and they won't work on Verizon. In order to root the phone needs to have BOC5 firmware or lower
...that's it then. It is truly impossible to develop apps directly on a retail edition of a Samsung phone with build BOG5 or later - unless, of course, you are a carrier or Google employee. Nono, don't tell me they can't do it - you know they have special phones not available to the developer community with special bootloaders where they can write any app they want on it.
)
...that's it then. It is truly impossible to develop apps directly on a retail edition of a Samsung phone with build BOG5 or later - unless, of course, you are a carrier or Google employee. Nono, don't tell me they can't do it - you know they have special phones not available to the developer community with special bootloaders where they can write any app they want on it.
There are only two options left then:
a. If a level 1 hypervisor exists for Android devices in the Google Play store, then one could run AndroidX86's fine port as a virtual image on top of the locked OS on the phone. And if that worked one could flash a custom ROM on top of that. Of course, a level 0 hypervisor can't exist because installation of any system directly on the hardware is impossible except for carrier or Google developers. (I'm old enough to remember the IE/Netscape for Windows war, where IE had the clear advantage because the Windows developers were right down the hall, but the Netscape developers had no access. The CEO gave up and open sourced Netscape, which became Firefox. >
b. Run the AndroidX86 port on VMWare Fusion Pro for OSX, or in VirtualBox.
...And if NEITHER option is possible, then this...'open source' system called Android is in fact a CLOSED system to all but carrier and Google software developers.
Update: AndroidX86 version 4.x WILL load up in VMWare Fusion Pro. It won't run, however - but it will install and run.
Looks like my research is complete. Thanx to everyone who helped me, they were invaluable. :highfive:
...Uhm, no, I'm afraid not. Sorry. From the DriveDroid page:
I came from the same state. Following this thread worked well for me. Read thru it and you'll be fine.
It has to be flashed you had to get to boe1 rooted by flashing something so use that same method to flash rooting tools
I can't seem to find either Safestrap or Flashfire for BOE1. Can you point me to a download for either? Thanks for taking the time to help me.
SafeStrap is already in the download file that JK told you about. Once you download the file, use root explore, open up the rooting tools file you downloaded, open up the RootS5 file, and you'll see the SafeStrap app and install it.
Never mind he answered this question. Great set of tools. Thanks
I currently have muniz OG5 "Odexed" rooted. Can I just flash jrkruse VZW_BOG5_STOCK_ROM_DEODEXED.ZIP to change from ODEXED to DEODEXED, then just Wipe Dalvik Cache and Cache, then Reboot Normal? Or are there other steps I NEED to take in order to switch? (Using Flash Fire v.21)
Thanks for helping out an Old Grandpa
From one grandpa to another, I would do a full wipe, then install the Rom. As the saying goes...no wipes, no gripes
No worries. Full wipe is, dalvik, cache, system, and data. But be careful not to have your .zip files on your internal storage, and not to wipe your external sdcard if your using SafeStrap. Just gotta take your time, and you'll be fine
That's because you have to flash a kitkat kernel to access SS. You can't boot into it if your on a LP rom and kernel.
