Database Users

[GUIDE] TF300T Unlock/Root/Flash for Factory JB Devices on 4.1.X (newbie friendly)

Having recently purchased a TF300T with intent to customize the hell out of it, I ran into a big problem. There wasn't one definitive guide for my general case, some of the steps I read weren't completely clear, and I often had to put pieces together from multiple guides to get where I wanted. Halfway through the process it occurred to me that sharing my experience in form of a guide could give the community something I wish that I had when I began. So enough with the intro, let's visualize the process before we begin.
This guide is for new owners of TF300T devices that have Jelly Bean 4.1.X preflashed from the factory. ​
joelalmeidaptg said:
If your tablet has 4.2.1 Android version from Asus, DO NOT FLASH A RECOVERY THAT WAS ACTUALLY MADE FOR 4.1 TABLETS! You will end up on a PERMANENT BRICK with no solution until now. You won't be able to use fastboot ever again. You won't be able to flash anything ever again. You will be stuck with a bricked tablet!
If you are looking for a Recovery for a 4.2.1 bootloader (and a complete guide for updating), read this thread: http://forum.xda-developers.com/showthread.php?t=2187982 Don't do it with any other tutorial: they are for 4.1 bootloaders!
Click to expand...
Click to collapse
For those curious...
My TF300T was one of the Champagne Gold models purchased from Groupon with a serial that begins with C9. I recall seeing a user with a Champagne Gold from Amazon that still had ICS. If you're still on ICS, this guide isn't for you-- Read up on NVflash and decide if you want to take advantage of it BEFORE you upgrade to JB.
Here's an overview of what we will be doing:
Click to expand...
Click to collapse
Unlock the TF300T
Backup apps, app data and files (Recommended, Optional)
Install ClockworkMod Recovery (soon to be replaced with TWRP; I gave in)
Root the TF300T (Optional)
Backup your stock Asus ROM (Recommended, Optional)
Flash a Custom ROM
Backup your working Custom ROM (Optional)
Additional information you should know:
Click to expand...
Click to collapse
This guide has been made with the total android noob in mind. Having only owned an android tablet for a week, I too am an android noob. On the flipside, I'm no noob to hardware and software exploits and modifications. I've tried to make this friendly for any type of noob, but there are a few instances where I expect basic menu and Windows 7 navigation skills.
ClockworkMod Recovery doesn't appear to have a "Shutdown" function, nor does it display current battery level-- for this reason, the recommendation and warning to have a battery charged to at least 60% is extremely heavy. The worst thing that can happen to any device is usually an incomplete flash. Don't let it happen to you-- start charging your TF300T NOW.
I have seen reports that "Fastboot" doesn't work properly on Windows 7 64-bit. This guide addresses that issue, as I also encountered it. If you don't know what "Fastboot" is, in the words of an admirable comedian, "You gonna learn today". Don't worry about it for now!
Your device came with JB-- you didn't miss the bus for NVflash. In your case, the bus never came.
I am not responsible for any damages caused to (but not limited to) yourself or your device.
Even if you think you're pretty good at figuring this stuff out, stick to the directions as close as possible.
If you love tweaks, you're going to love your custom ROMs.
Let's get started!
Unlocking Your TF300T
Click to expand...
Click to collapse
WARNING: Unlocking your TF300T will void your warranty. If your device breaks or fails under normal use, don't expect Asus to pick up the tab! Be aware that once unlocked, it cannot be relocked.
There are two ways you can go about this-- Either download the official Asus unlock utility for Windows or download the .apk and install from your tablet (Asus utility still working! I successfully unlocked mine on JB 4.1.1). I chose to download the .apk and install directly on my tablet, therefore this is the method I will cover.
To download the .apk file, scan the QR Code below with Barcode Scanner (free; on Play store) and open the URL to the Asus Support page for the TF300T. Alternatively, if you are viewing this thread on your TF300T, you may simply tap the code below.
​
On the Asus Support page, select "Android" as your OS. The page will reload and present you with a list. Click on "Utilities", then after it has loaded, download the Unlock Device App. When it is done downloading, a notification will pop up in the lower right corner. Click on it to install the Unlock tool. You'll also be able to open the app immediately after the install completes-- open it now.
After scrolling to the bottom of the End User Licence Agreement, select the checkbox indicating that you agree to those terms. You should now have access to the slider that will unlock your tablet. Stay connected to your wifi and unlock when ready. The unlock will not work without access to the internet.
If I recall correctly, your tablet should reboot. Just let it do what it wants. After it's done doing it's thing, take this opportunity to make backups! when you and your tablet are ready, we'll continue on to the next step.
Setting Up The Android SDK and Installing ClockworkMod Recovery
Click to expand...
Click to collapse
​Perhaps this was the most frustrating part of my experience-- Installing the Android SDK went fine when I could actually find the .exe download. After that it was a matter of getting the drivers for Fastboot working properly. I was able to narrow it down to a problem for users of Windows 7 64-bit.
From your PC, go HERE, scroll down and click on "Download For Other Platforms". Scroll down more and under the "SDK Tools Only" downloads, you should find a download that looks like: "installer_r##-windows.exe" where "##" is the revision number. Download this .exe and assuming Windows is installed on C:\, install it to either "C:\tools\android-sdk" or "C:\android-sdk". If Windows is not installed to drive letter C, replace the drive letter with the correct letter for your system. Do the same when following the command prompt examples that follow.
Open the Android SDK Manager. Search for "SDK Manager" in the start menu and you should find a result with the same name and a little android icon. Once it's open, you'll be presented with a list. Check the box next to the "Tools" folder, then expand the "Extras" folder and check the box next to "Google USB Driver". In the lower right corner, click "Install packages...", agree to all when ready and begin your downloads.
In the settings application of your tablet, go to the "Developer options" tab near the bottom. Ensure that the switch in the top right corner is in the "ON" position, then under the "Debugging" header, enable "Android debugging". Read the following carefully before you continue: Shut down your tablet and connect your USB cable. Hold the power and volume down buttons at the same time. Keep holding until you see a menu. The menu will consist of a few items, among them there is "RCK", a USB icon, an Android icon, and a "Wipe Data" icon. Tap volume down until the USB icon is selected, then press volume up. Cross your fingers and hope drivers install automatically.
They probably won't, so have windows look in the \android-sdk\extras\ folder. It should say the drivers installed successfully. Either way, open the start menu, and right click on "Computer". Click "Manage", then in the left hand pane of the new window, click "Device Manager". The "Other Devices" section may be already expanded in the center pane. If it is, look to see if "Fastboot" appears in that section with a yellow exclamation mark.
If it isn't there, you shouldn't be worried-- check for a section called "Android Phone" or "Portable Devices". Look for a device called "Android ADB Interface" or "Fastboot". It shouldn't have a yellow exclamation mark next to it.
In the event you have the device appearing with a yellow exclamation mark next to it, go HERE and download PdaNet. This was my remedy for this error. Unplug your TF300T from your computer and install PdaNet following instructions. During the install a warning will appear to install unsigned drivers. Install the driver anyway, and let the installation finish. You can now plug your TF300T back in, and it should be recognized automatically. Just in case, hold the volume down and power buttons again until your tablet restarts and you see your hidden menu again. Once again, tap volume down until the USB icon is selected, then press volume up again to select it. Check the Device Manager again and you should find the "Android Phone" section at the top. Within it, you'll find a device called "Android ADB Interface".
Now that we have your tablet and computer set up nicely, we can finally install ClockworkMod (CWM) Recovery. Go to THIS thread and download the attachment called "recovery-jb.img" (thanks XpLoDWilD!). It is VERY important that you download "recovery-jb.img" as this is the version for users with Jelly Bean bootloader!
Rename the file you just downloaded to "recovery.img" and place it in \android-sdk\platform-tools . In Windows 7, open the Start Menu and search for "cmd". You should see a result called "cmd.exe". Right click that result and click "Run as Administrator". Now type the following commands into the new command prompt window in order to flash CWM Recovery:
Code:
cd C:\tools\android-sdk\platform-tools\
fastboot -i 0x0B05 flash recovery recovery.img
DON'T unplug your tablet!! Don't close the window either! Wait for the command prompt to finish what it's doing, then you can type the final command:
Code:
fastboot -i 0x0B05 reboot
Your tablet will reboot. Once it has fully rebooted, shut it down and hold volume down and power again to access our tablet's hidden menu. This time, instead of selecting the USB icon, select "RCK" and press volume up. If I'm not mistaken, "RCK" stands for "ReCovery Kernel". ClockworkMod Recovery should load up. If it doesn't, then you were not successful in flashing CWM. If it does, then you can go to the Backup and Restore menu and create a backup.
I was overconfident when I went through all this, and I didn't make a backup-- for me, I wasn't able to get my SD card detected (64GB fat32), but even in this case you should be able to make a backup to your "Internal SD card". Unfortunately, you are on your own for this step. Make sure that you transfer this backup to your PC after creating it. You may need to disable Developer options in your TF300T's settings before you can transfer files over again.
In THIS post, XpLoDWilD gives instructions on how to Root your tablet. If I'm not mistaken, this applies to users who are using a ROM that does not already have root. If you care about Root right now, you can go ahead and flash his attached .zip file using CWM to your TF300T.
When I did this, I selected the .zip file with CWM and then went back to the main menu to select reboot. CWM then prompted me that it needed to fix permissions in order to keep Root. I tried it both ways-- first I let it fix permissions, then used a Play store app to check for root. Test came up negative, so I tried again without allowing it to fix permissions. Negative again. I tried again, allowing it to fix permissions again and then left it alone. If you are successful in rooting your TF300T, you can use Titanium Backup to backup your device later. However I used an app that did not require root that worked fine. The choice is yours.
Flashing a custom ROM
Click to expand...
Click to collapse
Now it's time to find a custom ROM to flash. For my guide I will cover Baked TF300T Blackbean #6-- Based on CyanogenMod10, and quite a nice upgrade from the stock ROM. The only downside I found is the Asus App Backup application is not included and cannot be installed. I'm unsure why this is the case-- I have even attempted to install it via CWM with no success. If you need this app or the App Locker app, I suggest you choose a non-CM10 ROM. You are on your own in deciding an alternative, but I have heard great things about CleanROM and I seem to recall reading that these incompatible Asus apps work on it. Don't take my word for it-- do your own research to make sure!
It should also be noted that ROMs like Blackbean #6 have some potentially dangerous settings that can make a power user salivate profusely.
Spiderman's Dad said:
With great power comes great responsibility
Click to expand...
Click to collapse
Okay, so it was his uncle, whatever. But either way, if you're going to install this ROM (or any other with overclock tweaks), BE CAREFUL when selecting different settings for CPU speed and overclocking. I used to overclock my PC as a hobby and pushed a 1.8GHz CPU to 2.77GHz on air cooling.. The thing I learned in the process is if you don't have the proper settings, your computer becomes unstable and weird things start happening. Data corruption, clicking the Start Menu does something crazy and unusual, PC crashes randomly, etc... Some of these errors are due to insufficient cooling-- a problem you cannot remedy when working with a portable device.
Assuming you are new to this tablet like I am, use this rule of thumb when dealing with foreign and potentially dangerous things: DON'T TOUCH IT until you understand it. Then when you understand it, understand it again. Then when you feel you've understood it twice, take baby steps. It's like jumping up a cement set of stairs-- you're definitely not going to try to jump five steps in your first attempt, unless you want to risk smashing your face and bloodying yourself up. Take it one step at a time-- make sure you can land on your feet before deciding to go further.
There's a lot of other options Blackbean #6 has that the average user can still appreciate, so ignore those overclocking/CPU stuff and focus on the other tweaks. Nova Launcher is included and is pretty sweet. I upgraded to Nova Launcher Prime and feel it's worth the extra $4, but I'll leave that for you to decide. There are more options than merely Nova Launcher alone, and not all of them have a price tag.
Without further adieu, let's download the Blackbean #6 ROM and Gapps. Head over to THIS official release thread for the downloads. The names of the files you want are:
baked_tf300t_blackbean-6_jb-bl_b6.zip
gappsinverted-jb-20121029-signed.zip​
Put them into a folder called "bb6" and copy the folder over to your TF300T. If your SD card is working in CWM (from CWM, go to the "mount" menu and try to mount SD card), copy the folder to your SD card.
NOW is the time to do any final backups before your fresh ROM install! I recommend "App Backup & Restore" on the Play store. If your tablet is rooted, you can also use Titanium Backup. Both will work fine, though generally speaking people seem to prefer Titanium Backup. People also seem to prefer TWRP over CWM, but I personally find the design unappealing. More importantly, I could only find a proper guide on installing CWM on a factory flashed JB TF300T.
Once you've made your backups, don't do anything until these backups are safely transferred to your PC! Don't forget to backup your music, movies and photos...
Now that you're 100% confident you've made all the backups you need and your battery is well charged and ready to go, let's flash your custom ROM! Shutdown and enter our hidden menu you should be very familiar with by now. Boot into CWM (with RCK icon from hidden menu selected, press volume up), then press volume up/down to navigate.
READ THE FOLLOWING SECTION BEFORE DOING ANYTHING ELSE:
Select "install zip from sdcard" and tap power. If you placed your "bb6" folder on your SD card, tap the power button once more. If it says "Can't mount /sdcard/" in the bottom left corner, then select "choose zip from internal sdcard" and tap power. Earlier you should have put your ROM and Gapps in a folder called "bb6". If you can't find this folder in either the SD card or internal SD card locations, GO BACK, reboot, and make sure you put the folder on your TF300T or your SD card. You should also make sure that the ROM and the Gapps file are inside that folder as well. Do NOT unzip them! They are just fine as they are. We are NOT flashing the ROM and Gapps yet, we are merely making sure they are there before you wipe your tablet. If the files are there, go back to CWM's main menu.
Select "wipe data/factory reset" and tap the power button. Confirm that you want to wipe, wait for it to finish.
Now select "wipe cache partition" and press the power button. Confirm that you want to wipe, wait for it to finish.
Go back to the main menu and select "advanced" and tap power, then select "wipe dalvik cache" and tap power. Confirm that you want to wipe, wait for it to finish.
Don't worry! Your ROM and Gapps should still be in your bb6 folder. Navigate to "install zip from sdcard" again, and let's make the magic happen. We are going to install the ROM first, then install Gapps. Only after both the ROM and Gapps are installed will we reboot our tablet.
So select the ROM first, confirm that you want to install, wait for it to finish. This one will take a long time compared to the Gapps. Just be patient and wait, even though it looks like it's not doing anything.
Then select the Gapps, confirm that you want to install, wait for it to finish.
Finally, reboot your tablet and cross your fingers. You should be greeted with the sweet victory of the startup animation. Go through the first time setup routine, and make sure the tablet works. From here you can optionally backup your custom ROM, but I recommend getting your settings the way you like them before you backup.
Give yourself a pat on the back--you survived! Hope this guide helped someone out-- I was able to sort through my problems fine, but I felt it important to share my experience. I know I couldn't have been the first to hop through these hoops anyway.
Congrats on your custom ROM Transformer Pad. Enjoy your tablet.
P.S. Questions? Comments? Suggestions? If you have any of the three, feel free to share! If it's a suggestion, please PM me and I'll see about making edits to my guide. All are appreciated, and especially anything that clears up any uncertainties I've expressed.
Special thanks (individuals and groups I owe credit for my process):
Drgravy, Team Baked, and everyone who wrote code that was used in the Blackbean ROMs. Blackbean #6 is my first custom ROM, and so far it's been great!! Keep up the awesome work!
XpLoDWilD, for CWM Recovery + Root on TF300T. These files and instructions were the major keys in making my endeavor a success
I also want to send out a big thank you to every other individual and team who has released a custom ROM for the TF300T-- admirable work, and far more than I could ever do. Thanks for giving us options and making us excited to have a customized tablet!
(....And many more! Currently in finals week (yikes) and can't recall everything right now-- will add more as I remember)

It's a shame that such a well written guide has so little thanks. Have mine.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Very nice. hopefully this helps people just getting the tf300.
note, if you want to install TWRP recovery instead, your command will change accordingly, just make sure you type in the exact file name you want to flash. so if your recovery file is named twrp.blob:
fastboot -i 0x0B05 flash recovery twrp.blob

Thanks!
Your guide helped me a lot. I had problems only with root. Flashed 4 times, but always got "no root acces". Finally, I downloaded root package from here http://forum.xda-developers.com/showthread.php?t=1845377 and it works well

is there any way around that "unknown error..." when i try to use the unlock app yet?
I keep trying but the same error message keeps coming up

sq1ne said:
is there any way around that "unknown error..." when i try to use the unlock app yet?
I keep trying but the same error message keeps coming up
Click to expand...
Click to collapse
Is your tf300 new? first hand? or have u ever sent it to asus for repair before?

Well written, well thought out instructions. Many, many thanks!! I'm still having some trouble though. I get stuck once I download the unlock app, open it, agree to the EULA, then another warning appears that is a black screen white text and a yellow triangle. Nothing happens after that. There are no buttons to agree, no checkboxes, nothing happens. Any advice?
*UPDATE* Figured it out. Be sure to sent the font in settings->display->font size to small, then you will see it. The large font pushes the agree button off the bottom of the screen.

It would be great if CWM in this OP were replaced with TWRP. Many are having issues with CWM. Me being one of them. I flashed TWRP with fastboot and no more problems!
I agree with the post above. Sad that such a well written post has so little thanks. :good:

thnx for this amazing guide, but I am still unsure of this guide will work for me.
I am from Holland (Europe)
specs from my ASUS Transformer TF300T:
Android 4.1.1
Kernel 3.1.10 ([email protected])
Buildnr JR003C.WW_epad-10.4.2.18-20121122
Pad EC Version PAD-EC20T-0216
My question is...will this guide also work for me? ...since I have JB 4.1.1 & build 10.4.2.18
I am also worried about the fact that this guide in for an american(?) transformer I gues...so do I need other files then the files mentioned?
I would love to have ROOT and install a custom rom and remove bloatware etc.
thnx for the help in advance!

Thank you so much, perfect for so many people here.
Can you edit it with TWRP? I would use this right now but as above poster said there have been issues with CWM so don't want to try it.
P.s. i got mine from groupon too

Tamaskan said:
Is your tf300 new? first hand? or have u ever sent it to asus for repair before?
Click to expand...
Click to collapse
bought mine brand new just this past Black Friday.
updated to .18 firmware
I don't want to have to send it in.

GodfleshNL said:
thnx for this amazing guide, but I am still unsure of this guide will work for me.
I am from Holland (Europe)
specs from my ASUS Transformer TF300T:
Android 4.1.1
Kernel 3.1.10 ([email protected])
Buildnr JR003C.WW_epad-10.4.2.18-20121122
Pad EC Version PAD-EC20T-0216
My question is...will this guide also work for me? ...since I have JB 4.1.1 & build 10.4.2.18
I am also worried about the fact that this guide in for an american(?) transformer I gues...so do I need other files then the files mentioned?
I would love to have ROOT and install a custom rom and remove bloatware etc.
thnx for the help in advance!
Click to expand...
Click to collapse
Yes, it will work, I've tried it. But i suggest you use TWRP custom recovery though. CWM has high chances of getting bricked.

Tamaskan said:
Yes, it will work, I've tried it. But i suggest you use TWRP custom recovery though. CWM has high chances of getting bricked.
Click to expand...
Click to collapse
Could you also please add a NOOB tutorial for installing TWRP Recovery (this forum is very confusing in getting the right tutorials / avoiding outdated tutorials which would brick my TF300T etc)?
Example:
quote from XDA forum in TWRP topic: "The fastest and easiest way to install TWRP is to use the GooManager app" <--- GooMnager needs ROOT so I can't use this method?
My ASUS TF300T is completely untouched & unrooted still and don't won't to mess it up.

GodfleshNL said:
Could you also please add a NOOB tutorial for installing TWRP Recovery (this forum is very confusing in getting the right tutorials / avoiding outdated tutorials which would brick my TF300T etc)?
Example:
quote from XDA forum in TWRP topic: "The fastest and easiest way to install TWRP is to use the GooManager app" <--- GooMnager needs ROOT so I can't use this method?
My ASUS TF300T is completely untouched & unrooted still and don't won't to mess it up.
Click to expand...
Click to collapse
www.mediafire.com/?7v1gwbbzqzvzto7 <- fastboot and twrp, the twrp is out dated so if you want you can download new one from twrp website.
2)Extract the recovery with fastboot files zip and open a command prompt in the same folder of the adb and fastboot files (you must click the fastboot and adb when extracred and i suggest you put your extracted fastboot and recovery zip in C:\(foldername) and then open cmd)
3) Reboot into the bootloader of your tablet, type: adb reboot bootloader
4) When your tablet has reached the bootloader navigate with volume down to the usb icon and press volume up to confirm.
5) To flash the recovery type:
fastboot -i 0x0b05 flash recovery tf300t-jb.blob
Credits to krabappel2548.

Tamaskan said:
www.mediafire.com/?7v1gwbbzqzvzto7 <- fastboot and twrp, the twrp is out dated so if you want you can download new one from twrp website.
2)Extract the recovery with fastboot files zip and open a command prompt in the same folder of the adb and fastboot files (you must click the fastboot and adb when extracred and i suggest you put your extracted fastboot and recovery zip in C:\(foldername) and then open cmd)
3) Reboot into the bootloader of your tablet, type: adb reboot bootloader
4) When your tablet has reached the bootloader navigate with volume down to the usb icon and press volume up to confirm.
5) To flash the recovery type:
fastboot -i 0x0b05 flash recovery tf300t-jb.blob
Credits to krabappel2548.
Click to expand...
Click to collapse
Here is a little update on my progress...
- I unlocked the bootloader of my TF300T
- I managed to install latest TWRP
- Made a (COMPLETE) backup of the untouchedl system with TWRP <--- DO THIS BEFORE ANYTHING ELSE!
- Rooted the TF300T with the WW file in this topic: http://forum.xda-developers.com/showthread.php?t=2033205 <----works awesome!
- Made a second (COMPLETE) backup of the now ROOTED system with TWRP
- Tried installing the latest "Cleanrom 3.01 Inheritance", but got the infamous "bootloop" too...the rom has been pulled down from the forum till that is fixed ( I thought I had done something wtong flashing a custom rom, but actually a lot of others had the same problem)
- Waiting for a "bootloop fixed" Cleanrom Inheritance 3.02....and gonna try flashing it again.

first of all thanks a lot ive been going crazy looking for this!! my question is will it work for me?
i bought my tf300t in sept with ics and upgraded to jb....
also i tried this not to long ago and ran into a problem after i unlocked
so right now its just unlocked but not rooted do i need to reverse that or what?
my apologies im extremely noob haha

GodfleshNL said:
Here is a little update on my progress...
- I unlocked the bootloader of my TF300T
- I managed to install latest TWRP
- Made a (COMPLETE) backup of the untouchedl system with TWRP <--- DO THIS BEFORE ANYTHING ELSE!
- Rooted the TF300T with the WW file in this topic: http://forum.xda-developers.com/showthread.php?t=2033205 <----works awesome!
- Made a second (COMPLETE) backup of the now ROOTED system with TWRP
- Tried installing the latest "Cleanrom 3.01 Inheritance", but got the infamous "bootloop" too...the rom has been pulled down from the forum till that is fixed ( I thought I had done something wtong flashing a custom rom, but actually a lot of others had the same problem)
- Waiting for a "bootloop fixed" Cleanrom Inheritance 3.02....and gonna try flashing it again.
Click to expand...
Click to collapse
i never backup.... I only backup app using titanium backuo, if something on the rom goes wrong i just reflash latest firmware from asus website. If you like custom roms, i suggest you use Energy Rom if you want OC or Hydro rom if you want just modified stock rom with better performance.

I have a problem while I try to run the flash recovery command. I have done all steps prior to this.The only difference I see is in device manager I get "ASUS Android Devices". Now, the error I am getting comes after trying to run the command, I get "error: cannot load 'recovery.img' No error" . I have also tried the pdanet solution. Thank you for your help in advance.

Stupid question... but I am going to ask it. Having never rooted my TF300 it is on latest firmware will this guide still apply to be even though I bought my device running ICS but have updated to latest firmware? Have never rooted tablets before so all new to this.

Agera said:
Stupid question... but I am going to ask it. Having never rooted my TF300 it is on latest firmware will this guide still apply to be even though I bought my device running ICS but have updated to latest firmware? Have never rooted tablets before so all new to this.
Click to expand...
Click to collapse
It will work as long as you are using Jelly Bean

[Q] MJ7 Root?

Are there any devs' working on a MJ7 root, or are we just completely screwed?

Lemmiwinx said:
Are there any devs' working on a MJ7 root, or are we just completely screwed?
Click to expand...
Click to collapse
I am curious about this as well. I just upgraded to the Note 3 (N900V) from the Note 2 and the volume levels are just so low. Even with a portable speaker that I use while at work I can barely get it loud enough to hear at full blast and to my knowledge rooting is the only real solution to that.

Klingo works fine with MJ7

jmorton10 said:
Klingo works fine with MJ7
Click to expand...
Click to collapse
Kingo works too.
Sent from my SM-N900V using Tapatalk

Kingo isn't suppose to have malware ?

um...
G8orDroid said:
Kingo works too.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
I've tried Kin go at least a dozen times, and no go. Tried switching cords and computers.... Nothing

Do you have USB debugging enabled? It should work
Sent from my SM-N900V using xda app-developers app

I don't see that the verizon note 3 is supported on the Kingo site.

Lemmiwinx said:
I've tried Kin go at least a dozen times, and no go. Tried switching cords and computers.... Nothing
Click to expand...
Click to collapse
We need more info than "no go" and "Nothing". Does it show that it's connecting? Is it giving a failed status at completion?
Steps to take:
1. Make sure USB Debugging is enabled.
(To enable Developer Options and subsequently USB debugging go to Settings>About Phone then tap Build Number several times [7, I think].
This will enable Developer Options on the main settings page. Then go into Developer Options and enable USB Debugging.
2. Reboot your PC and disable any anti-virus or firewall software.
2. Shut down the phone an pull the battery for a few seconds.
3. Restart the phone and launch Kingo. It should work.\
If it doesn't repeat the steps. Sometimes it takes a few tries, but you must have a "connected" status in Kingo or it will never work.

x82nd said:
I don't see that the verizon note 3 is supported on the Kingo site.
Click to expand...
Click to collapse
I've noticed that also. I wonder what phone people are choosing.

I rooted my VZW Note 3 2 days ago. The latest Kingo does work on MJ7.
Seriously, Use Google & read. Make sure you have USB drivers installed or Kies 3. It's not that hard

G8orDroid said:
We need more info than "no go" and "Nothing". Does it show that it's connecting? Is it giving a failed status at completion?
Steps to take:
1. Make sure USB Debugging is enabled.
(To enable Developer Options and subsequently USB debugging go to Settings>About Phone then tap Build Number several times [7, I think].
This will enable Developer Options on the main settings page. Then go into Developer Options and enable USB Debugging.
2. Reboot your PC and disable any anti-virus or firewall software.
2. Shut down the phone an pull the battery for a few seconds.
3. Restart the phone and launch Kingo. It should work.\
If it doesn't repeat the steps. Sometimes it takes a few tries, but you must have a "connected" status in Kingo or it will never work.
Click to expand...
Click to collapse
Ive done all of those steps multiple times.( I thought common sense was obvious, sorry...)

Lemmiwinx said:
Ive done all of those steps multiple times.( I thought common sense was obvious, sorry...)
Click to expand...
Click to collapse
The steps I outlined have worked for me and many others that have posted on these forums. I was simply trying to help. Obviously, based on that response, you don't need any help. You must have it all figured out. Well, all but how to root your phone.
Good day and good luck.
PS: you still haven't given any real useful information.
Sent from my "ROOTED" SM-N900V using Tapatalk

Is safestrap kexec possible?

If you will look around on the forum before you ask a question more than likely you will find a answer quicker than a response.....
Sent from my SM-N900V using xda app-developers app

G8orDroid said:
The steps I outlined have worked for me and many others that have posted on these forums. I was simply trying to help. Obviously, based on that response, you don't need any help. You must have it all figured out. Well, all but how to root your phone.
Good day and good luck.
PS: you still haven't given any real useful information.
Sent from my "ROOTED" SM-N900V using Tapatalk
Click to expand...
Click to collapse
whoa, there's no malice intended man. My response was more self deprecating than anything. Thanks for the info.

Lemmiwinx said:
whoa, there's no malice intended man. My response was more self deprecating than anything. Thanks for the info.
Click to expand...
Click to collapse
My apologies. Inflection and intent is hard to judge in the printed word.

Lemmiwinx said:
whoa, there's no malice intended man. My response was more self deprecating than anything. Thanks for the info.
Click to expand...
Click to collapse
Here's directions I found elsewhere on this forum & others using Google
Kingo version 1.1.4.1785 has SuperSU 1.65, I replaced that SuperSU with an updated version. SuperSU Version 1.80 is out now. No issues. Follow the steps below & you'll be up & running. Credit goes to either TomsGT or Kachow I can't remember which so I'll give them both credit
1) Begin by going to the website Root Android phone, flash custom ROM and manage your Android devices, Rooting Freeware Download - Kingo and hit the large green button that reads “Download”. The android_root.exe should begin downloading on Windows 7. Once, it has completed, go ahead, open it and select run. Should receive a box Root Set-up Wizard> select “next”> “I accept the agreement” then next> select the folder for the install, then next> folder selection, then next> create a desktop icon, then next> install> Launch Kingo Android ROOT, finish.
2) This next step can be tricky make sure for simplest use, to have a Micro USB 2.0 cable, Windows 7 computer, USB Debugging enabled. With the Kingo application Launched, there should be a red circle in the middle of screen indicating a device and a computer being connected. Connect both the device and the computer, with both connected, watch the red button turn orange and watch the device for a USB Debugging permission grant to appear and authorize it. Select the “Root” option, watch the screen of your device for the Super User to appear and pop up to authorize ADB Shell> and Grant it (you now have Root), let the rest application run, as soon as device Reboots> DISCONNECT. In fact you can UNINSTALL KINGO FROM YOUR COMPUTER.
3) There’s 2 big steps coming up, one is getting rid of Kingo and replacing it with a pure form of Root and then installing Safestrap, using it to install that pure form of Root. To get started let’s begin with the latest version of SuperSU which is version 1.69. The way this is going to be installed is a different form than usual, as we are actually going to Flash SuperSU. THIS WILL HAPPEN AT A LATER POINT, I WANT TO GET THIS FILE IN POSITION SO WE CAN QUICKLY FLASH IT AND INSTALL IT WHEN THE TIME IS RIGHT. Go ahead and download this file, please save this to the Internal Memory that should read in the folder [ sdcard/UPDATE-SuperSU-v1.69.zip ]. This will be a quick access location.
4) The next step is to install Safestrap, as of today it is running stable which is excellent news, it is also based on TWRP which happens to be a Custom Recovery. Safestrap is Recovery that is designed to work with devices that have locked Bootloaders, in the past years SS was limited to Motorola devices and until recently Hashcode the Developer of Safestrap has transitioned over to the darkside. Hashcode has put thousands of hours into SS and other projects and I owe him the credit to let him explain, here are his two main threads on
Rootzwiki
XDA
After reading Hashcode’s OP’s you should have a complete understanding how to set-up and install SS. I am leaving this section thin as Hashcode does an excellent job explaining how to install SS, what it is, how it works, and all the above. If any questions in specific please ask in this thread.
5) This is the main event, the goal here is to remove Kingo Root and replace it with a Genuine Root. To do this we need to first go into SuperSU app> go under the Settings> scroll to the bottom and find under “Cleanup”/ “Switch superuser app”. Then go ahead and press this area (nothing will indicate that it was pressed.) Then exit SuperSU, if you try to click on the app it will say the app is not installed (this is correct as you will be changing SuperSU momentarily.) Go ahead and Reboot the Device.
6) As the Device is restarting look for the Safestrap Logo Robot to appear, the bottom left corner says “Recovery” and go ahead select it. In the Top Right corner find the “Install” letters in Red> select Storage: Internal Storage (xxxx) /datamedia/media/0 > scroll down and find UPDATE-SuperSU-v1.69.zip, then touch it, on the next screen make sure it is the right file and slide the button to the right to “Swipe to Confirm Flash”. Should be > Successful < if so hit Reboot System.
7) Once, system Restarts> open your app drawer open up SuperSU and Grant any User Apps that you desire.

Mr. HQ said:
Here's directions I found elsewhere on this forum & others using Google
Kingo version 1.1.4.1785 has SuperSU 1.65, I replaced that SuperSU with an updated version. SuperSU Version 1.80 is out now. No issues. Follow the steps below & you'll be up & running. Credit goes to either TomsGT or Kachow I can't remember which so I'll give them both credit
1) Begin by going to the website Root Android phone, flash custom ROM and manage your Android devices, Rooting Freeware Download - Kingo and hit the large green button that reads “Download”. The android_root.exe should begin downloading on Windows 7. Once, it has completed, go ahead, open it and select run. Should receive a box Root Set-up Wizard> select “next”> “I accept the agreement” then next> select the folder for the install, then next> folder selection, then next> create a desktop icon, then next> install> Launch Kingo Android ROOT, finish.
2) This next step can be tricky make sure for simplest use, to have a Micro USB 2.0 cable, Windows 7 computer, USB Debugging enabled. With the Kingo application Launched, there should be a red circle in the middle of screen indicating a device and a computer being connected. Connect both the device and the computer, with both connected, watch the red button turn orange and watch the device for a USB Debugging permission grant to appear and authorize it. Select the “Root” option, watch the screen of your device for the Super User to appear and pop up to authorize ADB Shell> and Grant it (you now have Root), let the rest application run, as soon as device Reboots> DISCONNECT. In fact you can UNINSTALL KINGO FROM YOUR COMPUTER.
3) There’s 2 big steps coming up, one is getting rid of Kingo and replacing it with a pure form of Root and then installing Safestrap, using it to install that pure form of Root. To get started let’s begin with the latest version of SuperSU which is version 1.69. The way this is going to be installed is a different form than usual, as we are actually going to Flash SuperSU. THIS WILL HAPPEN AT A LATER POINT, I WANT TO GET THIS FILE IN POSITION SO WE CAN QUICKLY FLASH IT AND INSTALL IT WHEN THE TIME IS RIGHT. Go ahead and download this file, please save this to the Internal Memory that should read in the folder [ sdcard/UPDATE-SuperSU-v1.69.zip ]. This will be a quick access location.
4) The next step is to install Safestrap, as of today it is running stable which is excellent news, it is also based on TWRP which happens to be a Custom Recovery. Safestrap is Recovery that is designed to work with devices that have locked Bootloaders, in the past years SS was limited to Motorola devices and until recently Hashcode the Developer of Safestrap has transitioned over to the darkside. Hashcode has put thousands of hours into SS and other projects and I owe him the credit to let him explain, here are his two main threads on
Rootzwiki
XDA
After reading Hashcode’s OP’s you should have a complete understanding how to set-up and install SS. I am leaving this section thin as Hashcode does an excellent job explaining how to install SS, what it is, how it works, and all the above. If any questions in specific please ask in this thread.
5) This is the main event, the goal here is to remove Kingo Root and replace it with a Genuine Root. To do this we need to first go into SuperSU app> go under the Settings> scroll to the bottom and find under “Cleanup”/ “Switch superuser app”. Then go ahead and press this area (nothing will indicate that it was pressed.) Then exit SuperSU, if you try to click on the app it will say the app is not installed (this is correct as you will be changing SuperSU momentarily.) Go ahead and Reboot the Device.
6) As the Device is restarting look for the Safestrap Logo Robot to appear, the bottom left corner says “Recovery” and go ahead select it. In the Top Right corner find the “Install” letters in Red> select Storage: Internal Storage (xxxx) /datamedia/media/0 > scroll down and find UPDATE-SuperSU-v1.69.zip, then touch it, on the next screen make sure it is the right file and slide the button to the right to “Swipe to Confirm Flash”. Should be > Successful < if so hit Reboot System.
7) Once, system Restarts> open your app drawer open up SuperSU and Grant any User Apps that you desire.
Click to expand...
Click to collapse
so there is no windows 8 support?

I used Windows 7.

[ROOT] Root the new Blu Studio G with Kingo Root

Okay, so this isn't my work I'm just verifying that it does attain root on the new Blu Studio G, and making the necessary program easy to find. All thanks should go to Kingo ROOT.
WARNING!!! You could brick your phone. I am not responsible if you brick it, chuck it at someone, or fling it off your balcony in frustration. That's on you!!!
What you will need:
1) Kingo ROOT (attached to this thread).
2) A windows PC. (This may work in WINE on Linux, or in Virtual box on Mac, but I can't confirm that.)
3) Developer Options, USB Debugging, and install from Unknown Sources enabled on your phone.
4) your sync cord.
5) About 10 minute.
Got all that? Let's get started.
STEP ONE: Go to Settings, About Phone, Build Number. Tap it 7 times. It will sa "You're a Developer Now"
STEP TWO: Go to Settings, Developer Options. Turn on the soft switch in the upper right corner. Now scroll down to USB Debugging and check the box.
STEP THREE: Go to Settings, Security. Scroll down to Unknown Sources and check the box.
STEP FOUR: Connect your phone to your PC, and wait for all the drivers to install. If they don't automatically on your version of Windows as they do on Windows 10, the drivers are available on the XDA wiki.
STEP FIVE: Unzip and Install Kingo ROOT Installer. Now run it and follow on screen directions closely. when it is done, reboot.
STEP SIX: Install your favorite Busybox installer from the Play store [I use the by Stephen (Stericson) because it has the newest stable busybox.] When that is done, Reboot.
YOU ARE DONE.:laugh:
P.S. I ported TWRP touch recovery - available here. There is also a Philz touch recovery made for our device by nobreak1970 available here.
P.P.S. I am also working on several ROMs for the Studio G - when they are flawless I will post them; NOT BEFORE.

Rooted mine yesterday with KingRoot and used SuperSume to replace it with SuperSu.
Flawless.
I'm running exposed all sorts of different modules haven't found one that doesn't work all we need is a custom recovery now.

Blu studio G plus (BLU_S510_V13_GENERIC) Roms/help
Hi guys. I've made a big mistake. Earlier today I was deleting old Twrp backups to make room for new ones with fx root. Well while I was at it I deleted a couple of logs to and some things I thought were just empty residual files. When I closed out fx my phone crashed to boot screen. And is stuck there. I can get to recovery but currently there are no stock/custom Roms for my particular build. I have looked everywhere. I've found every build but my own and its frustrating. I don't know what I deleted to make my system fail. So I have no chance of trying to look up files and manually install them. I've found a ROM pretty close to my build (S510_V09) But before I result to such drastic measure that will potentially do more harm than good. I figured I would try my chances here first. Any ideas at this point would be greatly appreciated. Thank you guys.

Root for FireOS v4.5.5.1

It has been less than 12 hours since this was discovered (thanks to @rb11701) but potentially big news to those with 3rd gen devices that will not be receiving FireOS v5.
It appears FireOS v4.5.5.1 can be directly rooted with Kingroot! This greatly simplifies the process of obtaining root for those running FireOS > 4.5.2. Simply allow the device to update to 4.5.5.1 via normal OTA and then root.
There are early reports that Safestrap v4 and GAaps (Play Store) also work on 4.5.5.1. More testing is needed, especially wrt Safestrap. I strongly recommend against installing one of the Safestrap compatible custom roms until further testing has been done.
One thing you should immediately do after rooting 4.5.5.1 is block over-the-air (OTA) updates in the event a successor to 4.5.5.1 removes root and closes the vulnerability that Kingroot exploits. Instructions here.
Please note these are early reports. It may not work with all devices. There may be hidden 'gotchas'. All your hair might fall out. Amazon may have installed secret trackers in 4.5.5.1 that transmit your whereabouts to their secret base on Mars (built by Curiosity in cooperation with NASA) before bricking your device. Go in with eyes open.

yes.... THANKS! seems to be working...
where can i found the gaaps? is there i download-package with the latest gapps?

mkraus81 said:
yes.... THANKS! seems to be working...
where can i found the gaaps? is there i download-package with the latest gapps?
Click to expand...
Click to collapse
http://opengapps.org/
Suggestion: go small (nano, micro); add content as needed from play store.

something is crazy/damaged...
i installed safetrap everything is working fine....
made a backup of the root Image...
than i installed Google gaaps Minimum package with restore (http://forum.xda-developers.com/showthread.php?t=2779598)
after that safetrap cant start recovery mode (safetrap disabled message)... i tried to uninstall safetrap and reinstall it...
i reinstalled...
with "Reboot to Recovery" i only get the kindle fire logo...
if i start normaly i get the safetrap window... with "Safetrap disabled" message...
click recovery button... i only get a black Screen whats wrong?
anybody has a solution for me?

mkraus81 said:
something is crazy/damaged...
i installed safetrap everything is working fine....
made a backup of the root Image...
than i installed Google gaaps Minimum package with restore (http://forum.xda-developers.com/showthread.php?t=2779598)
after that safetrap cant start recovery mode (safetrap disabled message)... i tried to uninstall safetrap and reinstall it...
i reinstalled...
with "Reboot to Recovery" i only get the kindle fire logo...
if i start normaly i get the safetrap window... with "Safetrap disabled" message... whats wrong?
anybody has a solution for me?
Click to expand...
Click to collapse
Well - you took your device into uncharted territory and may have paid the price. Safestrap v4 is not a true recovery environment. It was developed with one purpose in mind: host a small subset of roms on FireOS v4 that otherwise could not be installed.
Flashing (injecting) GApps into FireOS with Safestrap v4 is untested and therefore risky. It is also possible there is an unknown incompatibility/conflict between FireOS 4.5.5.1 and GAaps; I think that unlikely, at least one severe enough to keep your device from booting. That said, the presence of Safestrap v4 throws in a wildcard.
The symptoms you describe mirror those following a 'factory reset' from the native recovery menu. If accurate there is no known recovery.
Have you tried to access the device via adb?

i tried factory reset in kindle os menu but nothing happend...
is their a solution to to factory reset with adb?
UPDATE: now i am in a factory reset Loop..... i can select the language... an than kindle tried wifi Connection... than black Screen and select language again... and so on....

Hi,
I tried Kingroot it on my 4th gen HDX 8.9 with FireOS 4.5.5 installed and it worked fine.
Followed these instructions here: http://forum.xda-developers.com/showpost.php?p=59160158&postcount=1 to disable OTA and instalL GApps.
I can install stuff from the play store, use Chrome. So far so good !
Thanks to the rooting gods!

mkraus81 said:
i tried factory reset in kindle os menu but nothing happend...
is their a solution to to factory reset with adb?
Click to expand...
Click to collapse
No - but if you can get the device to identify itself via adb there is the (slim) potential for a future solution. It's a shelf item for now; sorry for your loss.

i tried "adb reboot recory" and in kindle recovery i made a factory reset
and now kindle is woking
but i dont have the backbutton....

mkraus81 said:
i tried "adb reboot recory" and in kindle recovery i made a factory reset
and now kindle is woking
but i dont have the backbutton....
Click to expand...
Click to collapse
First time I have heard of that approach working! Thanks for sharing.
Do you still have Safestrap v4 installed? It sounds like FireOS may have been 'damaged'. One path would be to reinstall (replace) FireOS with a known good version (4.5.2) but that requires Safestrap. Note - I'm not suggesting you reinstall SS if it is not present as you may end up in the same situation as before. Have to act with caution as your device does not have a true recovery. You need a functioning OS to commence most recovery/repair operations.

safestrap now working..... the only Problem i have...
i had no menu bar.... so i cant leave apps menus and so on...

Confirmed Saturn rooted via kingroot 4.5.5.1...

mkraus81 said:
safestrap now working..... the only Problem i have...
i had no menu bar.... so i cant leave apps menus and so on...
Click to expand...
Click to collapse
my softkeys are back
i had made a backup after installing safestrap first time...
i restore it... safestrap at the and said failed... but the softkeys are back
ist a Little bit tricky

XxD34THxX said:
Confirmed Saturn rooted via kingroot 4.5.5.1...
Click to expand...
Click to collapse
Thank you. Suggest holding off on Safestrap and custom roms for now. If you are following the conversation there have been some issues (albeit somewhat unique). Also consider whether FireOS v5 (lollipop based) would be a better long term choice. It's not bad...ran it for several weeks before switching to CM12 on a 5th gen Fire. Too soon to say if other LP options may become available for 4th gen devices.

mkraus81 said:
my softkeys are back
i had made a backup after installing safestrap first time...
i restore it... safestrap at the and said failed... but the softkeys are back
ist a Little bit tricky
Click to expand...
Click to collapse
Count your blessings!
Question: What is your long term goal: FireOS v4 w/Play Store or any ROM that supports the Play Store? If the latter I would give consideration to Nexus v4 or CM-11. Both run under Safestrap v4 and offer a complete android experience with full access to Google Services and applications. Difference between the two boils down to eye candy and a few obscure functions geared toward enthusiasts. I can provide further guidance (if desired) with a better idea of where you want to be.

my first Goal was... Google Playstore... but that dont work correct with this package
http://forum.xda-developers.com/showthread.php?t=2779598
i had a playstore but cant search apps... i press 1 char into the searchbar an app store is closing...
i try to use cm11

ok so Root confirmed for hdx7inch 3rd gen changed kinguser to su, then try to flash the pico zip gapps and got error code insufficient space, and this is the smallest so not sure if everything is working as it should any idea as to why I would have this issue? Thx

mkraus81 said:
my first Goal was... Google Playstore... but that dont work correct with this package
http://forum.xda-developers.com/showthread.php?t=2779598
i had a playstore but cant search apps... i press 1 char into the searchbar an app store is closing...
i try to use cm11
Click to expand...
Click to collapse
I saw this as well, but it went away after rebooting following the Play store installation.
I used the same package with the instructions from here http://forum.xda-developers.com/showpost.php?p=59160158&postcount=1
and rebooted before and after the PrebuiltGMSCore installation.

jo-me said:
I saw this as well, but it went away after rebooting following the Play store installation.
I used the same package with the instructions from here http://forum.xda-developers.com/showpost.php?p=59160158&postcount=1
and rebooted before and after the PrebuiltGMSCore installation.
Click to expand...
Click to collapse
i tried this... but still the same Problem

Davey126 said:
Thank you. Suggest holding off on Safestrap and custom roms for now. If you are following the conversation there have been some issues (albeit somewhat unique). Also consider whether FireOS v5 (lollipop based) would be a better long term choice. It's not bad...ran it for several weeks before switching to CM12 on a 5th gen Fire. Too soon to say if other LP options may become available for 4th gen devices.
Click to expand...
Click to collapse
Yeah, I've seen problems already. I've just disabled OTA, and i'll see if the next one will get root as well.

G900V Re-Activation Lock, BUILD KOT49H.FA44_G900VVRU2APA1 4.4.2

I'm stuck on some developer ROM.. Was trying to follow instructions to get passed the activation lock. So I currently have a barely working ROM installed (as it seems it's for developers). I don't care what version of android I get installed at this point.. Looking for some help. I've been trying to fix it for days now. I don't have access to the icloud email I used to set up the samsung account, that's what started all of this *cries*

FancyPantsu said:
I'm stuck on some developer ROM.. Was trying to follow instructions to get passed the activation lock. So I currently have a barely working ROM installed (as it seems it's for developers). I don't care what version of android I get installed at this point.. Looking for some help. I've been trying to fix it for days now. I don't have access to the icloud email I used to set up the samsung account, that's what started all of this *cries*
Click to expand...
Click to collapse
You could try using Odin to flash the appropriate firmware though I'm not sure if it would wipe the reactivation lock

FancyPantsu said:
I'm stuck on some developer ROM.. Was trying to follow instructions to get passed the activation lock. So I currently have a barely working ROM installed (as it seems it's for developers). I don't care what version of android I get installed at this point.. Looking for some help. I've been trying to fix it for days now. I don't have access to the icloud email I used to set up the samsung account, that's what started all of this *cries*
Click to expand...
Click to collapse
Which/what instructions were you going by....?

Deleted

FancyPantsu said:
I'm stuck on some developer ROM.. Was trying to follow instructions to get passed the activation lock. So I currently have a barely working ROM installed (as it seems it's for developers). I don't care what version of android I get installed at this point.. Looking for some help. I've been trying to fix it for days now. I don't have access to the icloud email I used to set up the samsung account, that's what started all of this *cries*
Click to expand...
Click to collapse
@FancyPantsu, do you know what OS version you were running before you had done what, IMHO, you shouldn't have unless you know exactly what you are doing. You didn't actually flash a ROM persay, you flashed, i believe, the engineering ROM or something like that.....let me/us know EXACTLY what Android version you were running before you ODIN'd the factory Tar file. By that I mean OG5, OK3, PB1, PD1, etc. But need that to possibly get you out of your predicament....

al50 said:
@FancyPantsu, do you know what OS version you were running before you had done what, IMHO, you shouldn't have unless you know exactly what you are doing. You didn't actually flash a ROM persay, you flashed, i believe, the engineering ROM or something like that.....let me/us know EXACTLY what Android version you were running before you ODIN'd the factory Tar file. By that I mean OG5, OK3, PB1, PD1, etc. But need that to possibly get you out of your predicament....
Click to expand...
Click to collapse
Honestly this would be the first time anything like this has happened, haha.. I've flashed many devices with custom roms and never seemed to have this much of a problem. Basically the whole situation was I got the phone from my cousin who didn't need it anymore, she doesn't know her google info (no way of finding out now), so I figured what the hell and started screwing with the phone. Samsung being Samsung.. This happened. I seem to have flashed a dev rom or as you said an engineering rom (which I'm pretty sure it is). If I can remember correctly it was running.. 6.0.1.
If it helps any, I'm up for trying anything I've got plenty of phones laying around at this point, would be nice to have the s5 again though.
**Sorry for the very, very, very late reply!
-Thanks.

... del ...

bbsc said:
All you need is:
1. Install a 4.4.2 with working Samsung Account. It's a little tricky because you cannot downgrade your phone via Odin to 4.4.2. Root that "developer ROM" you have, install Safestrap Recovery and use it to flash a custom stock-near 4.4.2.
2. Boot it and bypass Setup Wizard. It's a little tricky too but is easily done with an OTG cable and a USB stick. There are other methods but I like this one .
3. Create a new Samsung account (or login to your existing Samsung account) from the phone and turn Reactivation Lock off.
After this you'll be able to flash any firmware.
Click to expand...
Click to collapse
Is it possible to message you directly in case I need any help or have questions? @bbsc

... del ...

bbsc said:
Please, ask questions and I'll answer if I can.
Have a look at the first and the third post in this thread: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
It will give you directions how to root your current rom and to install Safestrap Recovery.
This will be the first step
P.S. Nothing more. Just G900VVRU2APA1, Apex launcher, BusyBox, Towelroot, Safestrap Recovery.
Click to expand...
Click to collapse
Oh jeez. That's confusing already.. Lol. I've got G900VVRU1ANCG downloaded \, Towelroot v3, Safestrap KLTEVZ
I'm currently booted into the current engineering rom. Next step?
(Sorry if I'm not catching it the first time)

... del ...

bbsc said:
The next step is to read the thread I've given you link to, download files, install Apex launcher, BusyBox, Towelroot, Safestrap recovery. To root engineering ROM.
You'll need some 4.4.2 stock-like ROM to install via Safestrap Recovery. Odin won't work. This ROM will do. You can download it here.
After this you need to reboot to Safestrap Recovery and install kltevzw_NCG_eLLiKat1_0.zip
Click to expand...
Click to collapse
Alright. Currently I have the files downloaded, moving them over to the sd card now. EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip, EMMC_15_Root_Bootloader_Unlock+S5_QB2_PB1.zip, Towelroot.apk, Safestrap.apk. Missing anything that you can notice? I'll continue to follow the steps and see where it lands me

... del ...

bbsc said:
Supersu.apk missing. My fault, sorry.
1. Copy apk files and kltevzw_NCG_eLLiKat1_0.zip into the phone's memory.
2. Install Apex_Launcher.apk (you'll need to turn Unknown Sources ON) but do not run it.
3. Install BusyBox.apk but don not run it.
4. Install Safestrap_KK.apk but do not run it.
5. Install tr_v2.apk - Open - make it rain (a message "You should have root, no reboot required" should appear) - Back.
6. Install Superuser.apk - Open - Continue - Normal - Reboot.
7. After reboot, in the pop-up window - Apex Launcher - Always - Ok.
8. Menu (dotted button) - BusyBox Free - Grant - close balloon - Install - close balloon - Back.
9. Safestrap - Grant - Agree - Install Recovery - Reboot to recovery. Wait patiently for SafeStrap Recovery to boot.
10. Swipe to Allow modifications - Wipe - Advanced Wipe - Dalvik/Data/Cache - Swipe to Wipe.
22. Back - Back - Back - Install, install kltevzw_NCG_eLLiKat1_0.zip.
Reboot system and now you must have a 4.4.2 phone with Samsung account locked. Next step will be to bypass Setup Wizard.
Click to expand...
Click to collapse
Got into recovery once. Followed the wrong directions- off the link you gave me. Wasn't supposed to do anything else from there I suppose. Now I reboot to custom binary blocked by reactivation lock. Solution? Gotta redo everything again?

... del ...

bbsc said:
Sorry.
You have to begin again from the start and flash COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_257265 6_REV00_user_mid_noship_MULTI_CERT.tar.md5 with Odin.
I'll prepare a detailed guide with files if needed but a bit later.
Click to expand...
Click to collapse
No need- I redid everything already. About to boot into safestrap.

... del ...

bbsc said:
I'll leave it here to edit and add links later.
1. Charge the battery to more than 50%.
2. Download Odin and COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_257265 6_REV00_user_mid_noship_MULTI_CERT.tar.md5.
3. Download applications files - apks.zip.
4. Download ROM file - kltevzw_NCG_eLLiKat1_0.zip.
5. Run Odin.exe.
6. Select COMBINATION_VZW_FA44_G900VVRU2APA1_VZW2APA1_257265 6_REV00_user_mid_noship_MULTI_CERT.tar.md5 in Odin's AP slot, boot the phone into the download (Odin) mode, connect with USB cable to the computer, press Start, wait till the flash process is finished. Press Exit and wait for the phone to complete reboot.
7. Disconnect USB cable from the phone and connect again.
8. Unzip apks.zip into the apks forlder on the Desktop.
9. Copy everything from apks folder to the root of phone's internal memory.
10. Copy ROM file kltevzw_NCG_eLLiKat1_0.zip to the root of phone's internal memory.
11. Disconnect the cable from the phone.
12. Press Menu (dotted button) - My Files - All - RootS5.
13. Apex_Launcher.apk - Settings - Unknown Sources - Ok - Back - Apex_Launcher.apk - Next - Install - Done.
14. BusyBox.apk - Install - Done.
15. Safestrap_KK.apk - Install - Done.
16. tr_v2.apk - Install - Open - make it rain (a message "You should have root, no reboot required" should appear) - Back.
17. Superuser.apk - Install - Open - Continue - Normal - Reboot.
18. After reboot, in the pop-up window - Apex Launcher - Always - Ok.
19. Menu (dotted button) - BusyBox Free - Grant - close balloon - Install - close balloon - Back.
20. Safestrap - Grant - Agree - Install Recovery - Reboot to recovery. Wait patiently for SafeStrap Recovery to boot.
21. Swipe to Allow modifications - Wipe - Advanced Wipe - Dalvik/Data/Cache - Swipe to Wipe.
22. Back - Back - Back - Install, install kltevzw_NCG_eLLiKat1_0.zip.
23. Reboot System - Do not install. After reboot you should see 4.4.2 Setup Wizard (dark background).
24. Connect to Wi-Fi AP.
25. Get a FAT-formatted USB stick of any size and a USB-OTG cable. Throw any apk file on the USB stick and connect it to the phone.
26. When the phone recognizes the storage it will pop-up an Explorer window. Navigate to your apk file and tap it once. You should see a security warning with link to Settings.
27. Press "Settings", navigate to Reactivation Lock and disable it. The phone will ask you to enter login/password from your Samsung account or to register a new one. Do it.
28. After logging into the Samsung account you should be able to disable Reactivation Lock.
29. Flash any firmware on your choice. The current firmware is outdated and may be non-operational in some points.
Click to expand...
Click to collapse
Thank you very much kind sir Restored, up and running again.

FancyPantsu said:
Thank you very much kind sir Restored, up and running again.
Click to expand...
Click to collapse
~~ Now if I want to flash a custom rom from 4.4.2 up to 7.0 how can I do that..? Currently trying multiple roms, none of them will boot correctly. Get's stuck in a boot loop

FancyPantsu said:
~~ Now if I want to flash a custom rom from 4.4.2 up to 7.0 how can I do that..? Currently trying multiple roms, none of them will boot correctly. Get's stuck in a boot loop
Click to expand...
Click to collapse
This question does not concern this discussion.
Your phone is now "clean" and if you flash a factory firmware with Odin and perform a factory reset it will be in a "like new" state.
You'd better begin with these threads:
One
Two
Personally I and my family and my friends use this ROM with the latest firmware for SM-G900V.