Database Users

[GUIDE]Flash Android 2.3.4 with Windows x64/x86

Prerequisites
AT&T Atrix 4G with and UNLOCKED bootloader
Windows OS x64/x86
Motorola drivers installed
The .zip file listed below contains all the files you need.
Extract this to the root of you C drive and use the following commands in the listed order, one at a time :
Put your device in Fastboot mode by holding the volume down button while booting then volume up
Open up a command prompt and type( ONE AT A TIME )
cd C:\moto-fastboot
moto-fastboot flash boot atrix-2.3.4-hktw-boot.img
moto-fastboot flash system atrix-2.3.4-hktw-system.img
moto-fastboot -w
moto-fastboot reboot
If you followed the steps correctly you should have Gingerbread 2.3.4 on you AT&T Atrix.
Cheers!
Thanks to romracer for compiling the moto-fastboot-win32.
I made this user friendly guide and compiled the .zip with everything you need.
WARNING
The leaked build from Hong Kong / Taiwan was probably not built for a device that is exactly like ours. Test phones can have different hardware. Don't expect everything to work, it's super-duper beta and since we've all only been unlocked 24hrs no one really knows how usable it is! Flash at your own risk... (PS you can 'Skip' Motoblur just by hitting 'Menu' during setup. It won't connect anyway...)

Guide for ROOT

I'm gonna try that right now

Question how would i do this for windows xp 32bit

Can someone tell me what works / doesn't work when using HKTW 2.3.4? Also curious about the speed and stability of the Atrix when using the rom. Is it ready for daily use or should we wait on something else?

mudd_cat23 said:
Question how would i do this for windows xp 32bit
Click to expand...
Click to collapse
This guide should work, XP 32bit is x86.

dcarpenter85 said:
Can someone tell me what works / doesn't work when using HKTW 2.3.4? Also curious about the speed and stability of the Atrix when using the rom. Is it ready for daily use or should we wait on something else?
Click to expand...
Click to collapse
It can be used as a daily ROM
only the Webtop and Fingerprint read dont work, i believe however there's a fix for the Webtop.
Webtop Fix

XLR88 said:
It can be used as a daily ROM
only the Webtop and Fingerprint read dont work, i believe however there's a fix for the Webtop.
Webtop Fix
Click to expand...
Click to collapse
Thanks for the info, I will have to give it a try.

mudd_cat23 said:
Question how would i do this for windows xp 32bit
Click to expand...
Click to collapse
More than likely it should work on XP/Vista x64/x86 and I can confirm it works on Windows 7 x64/x86.

Sucks to be me, I guess.

Ok flashed and now need to go trough motoblur wizard
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\moto-fastboot-2.3.4\moto-fastboot>moto-fastboot flash boot atrix-2.3.4-hktw-boot.img
sending 'boot' (3358 KB)... OKAY [ 0.347s]
writing 'boot'... OKAY [ 0.704s]
C:\moto-fastboot-2.3.4\moto-fastboot>moto-fastboot flash system atrix-2.3.4-hktw-system.img
sending 'system' (262144 KB)... OKAY [ 27.876s]
writing 'system'... OKAY [ 13.985s]
sending 'system' (65410 KB)... OKAY [ 7.065s]
writing 'system'... OKAY [ 3.377s]
C:\moto-fastboot-2.3.4\moto-fastboot>moto-fastboot -w
erasing 'userdata'... OKAY [ 6.140s]
erasing 'cache'... OKAY [ 2.136s]
C:\moto-fastboot-2.3.4\moto-fastboot>
C:\moto-fastboot-2.3.4\moto-fastboot>moto-fastboot reboot
rebooting...
C:\moto-fastboot-2.3.4\moto-fastboot>

Hmm, what the hell could I be doing wrong?

Interesting.. can't login to moto blur..
It say's
Error signing into account
An error has occurred. Please try again..
I check username and pass several times..

jwhited said:
Sucks to be me, I guess.
Click to expand...
Click to collapse
Flash 1.83 SBF using RSDLite and then try again
Copy and paste the commands one at a time instead of typing to prevent errors.

zexbig said:
Interesting.. can't login to moto blur..
It say's
Error signing into account
An error has occurred. Please try again..
I check username and pass several times..
Click to expand...
Click to collapse
Press Menu->Skip
unless you really want MotoBlur. (and i am sure you are the only one in the world who wants blurrrrrrr). If thats the case, blurrr wont work on this build. Go back to 1.83 or some other official release

zexbig said:
Interesting.. can't login to moto blur..
It say's
Error signing into account
An error has occurred. Please try again..
I check username and pass several times..
Click to expand...
Click to collapse
Forgot to mention, Motoblur does not work......press menu and then select skip on the screen.

This was way to easy.
Thank you!!

Well.. there is new option.. during setup press menu button and select skip setup..
It will skip moto blur setup and disable locate my phone trough moto blur but that's about it

Where do we put the root commands?
/preinstall/dosu
/bin/mount -o remount,rw /system
cp /preinstall/su /system/bin/
PATH=/system/bin:$PATH pm install /preinstall/Superuser.apk
Click to expand...
Click to collapse

XLR88 said:
Flash 1.83 SBF using RSDLite and then try again
Copy and paste the commands one at a time instead of typing to prevent errors.
Click to expand...
Click to collapse
Hmm, I did start from a 1.83 SBF (from a different source, mine was a .7z file.. Worked just the same, though.) I'll try the one from your link, and go from there.
Should just need to flash SBF, unlock, and go, right?

[Q] Using fastboot.

So I am not quite sure what exactly fastboot is supposed to do. I know you can flash recoveries, bootloaders, etc with it but that is about it for my understanding.
I tried to get into fastboot (following instructions here on the forum) mode earlier today and while the tablet gives me the fastboot message in the upper left, windows says that fastboot failed. Is there a folder I am supposed to be running cmd prompt from?
Sorry, still new to this stuff and my understanding of some of these tools is limited at best.
Sent from my A500 using Tapatalk 2

a friendly warning
CyaN1de said:
So I am not quite sure what exactly fastboot is supposed to do. I know you can flash recoveries, bootloaders, etc with it but that is about it for my understanding.
I tried to get into fastboot mode earlier today and while the tablet gives me the fastboot message in the upper left, windows says that fastboot failed. Is there a folder I am supposed to be running cmd prompt from?
Sorry, still new to this stuff and my understanding of some of these tools is limited at best.
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
Give me 30 mins got all the reading u gonna need b4 u make an attempt
if u fk up in here there is definitely NO WAY BACK in meantime you'll
Want to set adb as environmental variable in windows gonna make it
Helluva lot easier . Android sdk will too. f u don't know what I'm on About..
.best do some reading up on these as well.
Fast boot ain't something someone else can talk u thru and I doubt the devs will
Have any sympathy for anyone asking ....i bricked my tab pls help....

dibb_nz said:
Give me 30 mins got all the reading u gonna need b4 u make an attempt
if u fk up in here there is definitely NO WAY BACK in meantime you'll
Want to set adb as environmental variable in windows gonna make it
Helluva lot easier . Android sdk will too. f u don't know what I'm on About..
.best do some reading up on these as well.
Fast boot ain't something someone else can talk u thru and I doubt the devs will
Have any sympathy for anyone asking ....i bricked my tab pls help....
Click to expand...
Click to collapse
Running adb from its native folder is not an issue.....is fastboot the same way having to run cmd from folder that a file is located?
I prefer not to mess stuff that I do not fully comprehend (not that I fully comprehend ANY of this) but some of it makes more sense once you are into it rather than reading someone elses interpretation.
Sent from my A500 using Tapatalk 2

CyaN1de said:
Running adb from its native folder is not an issue.....is fastboot the same way having to run cmd from folder that a file is located?
I prefer not to mess stuff that I do not fully comprehend (not that I fully comprehend ANY of this) but some of it makes more sense once you are into it rather than reading someone elses interpretation.
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
yeh just a group of extended adb commands that allow you to do some pretty awesome stuff - like really, really bricking your tab for instance, lol. I'm unsure as to whether all the fastboot commands are available to us - i havent had enough spare time to devote to heavy duty reading in the Dev Forums!!!! You can flash everything in here so its like a supercharger;;;;Sort of like going from timmydeans EUU root to Civ's nvflash unlocking bootloaders thing, if you know what i mean.......
But heres some reading, most of it tutorial step by step stuff, mostly for other devices which may not apply to our tab but definitely apply to fastboot. AS you know, there is alot of info in our own dev forum but its hard to find a flow as the devs actually speak a different language to us!!!! So the tutorials are quite good in that respect as they use noob-ite speak
the backup and restore tute is a goody, couldnt get it going on v3 so looking forward to giving it a go on v4 (when i can find a quiet 30 mins or so, that is)
anyways happy reading be interested in your thoughts and keep us posted about what you get around to trying
rgds
Full Phone Backup http://forum.xda-developers.com/showthread.php?t=1420351
setup adb http://forum.xda-developers.com/showthread.php?t=1249798
adb http://forum.xda-developers.com/showthread.php?t=879701
adb logcat http://droid-force.com/showthread.php?tid=150&pid=573#pid573
ics BL by Skrilax_CZ http://forum.xda-developers.com/showthread.php?t=1514951

So I located Fastboot in D:\Android\android-sdk\platform-tools\Fastboot.exe
But putting tablet into fastboot mode yields the driver installer to report that "Device driver software was not succesfully installed".......Fastboot X Failed....is this normal? Will it run when I use cmd prompt from D:\Android\android-sdk\platform-tools?
I guess a little linux knowledge would go a long way.....too bad I can't get a grasp on that either.
Thanks for the links.....hopefully I can find time to give a read.

Set up adb/fastboot for noob-ites 101
CyaN1de said:
So I located Fastboot in D:\Android\android-sdk\platform-tools\Fastboot.exe
But putting tablet into fastboot mode yields the driver installer to report that "Device driver software was not succesfully installed".......Fastboot X Failed....is this normal? Will it run when I use cmd prompt from D:\Android\android-sdk\platform-tools?
I guess a little linux knowledge would go a long way.....too bad I can't get a grasp on that either.
Thanks for the links.....hopefully I can find time to give a read.
Click to expand...
Click to collapse
weird??? i kicked straight in to bl, fastboot drivers installed, never saw red x
u mean u arent cmd from platform tools???
in the cpuid guide I suggested extracting the just_adb.zip into C:\ so setting
up the env. var. would be easier I have been meaning to post the steps for
doing that, guess theres no time like the present
Set adb as Environment Variable or call adb direct from command prompt
............ first, copy the path to your install - in your case:
............ "Path to adb" = D:\Android\android-sdk\platform-tools
1. Click on the Start menu
2. Right click on Computer
3. Click on Advanced system settings
4. Click on the Environment Variables button
5. Look for Path in the System Variables section. Double click on it
6. Go to the end of the Variable value box and put in a semicolon ;
7. Now paste your "Path to adb" after the ;
8. it should look like this in your case ;D:\Android\android-sdk\platform-tools
9. Now test it out - start - run/search - cmd - in cmd window type: adb devices
10. If you've followed the steps you will see your device ID - voila!!!!
as you can see this makes trouble shooting so dam easy -
if you cant get a device id do not go any further in what u r doing
cos it aint gonna work....period!!!!! also since ICS has screwed
with getting our cpuid like this, for our purpose here, it is only important
that a device id is shown - not how right or wrong it is.....clear????
so getting back to it, check fastboot*.exe in same folder as adb.exe -
it came like this in my own setup not sure about the asdk setup -
remember too fastboot only has a few commands and i still havent
got round to trying them all out yet....
to anyone following this, I cannot say enough how dangerous this can be
please, please, please take a moment to read thru just one of the links i
posted earlier - they are tutorials and if you see the dev thread regarding
v4 unlock...you will not only learn something amazing but begin to
appreciate and respect the work done by these devs who laid the groundwork
that enabled civato and blakthund3r to produce what they have with the
unlocked bootloader - without this groundwork we would still be waiting
for a way to get full root access and cwm, custom roms, themes and mods......

Thanks for that
Seems my Windows skillz need brushing up on again too....LOL
C:\Users\username>adb devices
List of devices attached
11717XXXXXX device

CyaN1de said:
Thanks for that
Seems my Windows skillz need brushing up on again too....LOL
C:\Users\username>adb devices
List of devices attached
11717XXXXXX device
Click to expand...
Click to collapse
sweet m8 -
yeh whoever thought windoze would actually be useful!!!!
which i guess is freakn handy as having to go linux would spin me out....
what can i say??? I'm a child of windoze had no choice, forced-addiction
before i was born, lol - breaking the habit, but always go back, goddamit

OK....I get the adb ok.
But when I put tab into FB i get the driver error (see attachment). I suppose that I should not be getting this?
Trying just "fastboot reboot" (not wanting to go any farther until I get a grasp...HAHA) I get "waiting for device"

CyaN1de said:
OK....I get the adb ok.
But when I put tab into FB i get the driver error (see attachment). I suppose that I should not be getting this?
Click to expand...
Click to collapse
dont let windows install
choose let me choose where to install dunno exact wording

Does not give me a choice.
Driver is located at D:\Android\android-sdk\extras\google\usb_driver ???
This is making my head hurt....LOL

CyaN1de said:
Does not give me a choice.
Driver is located at D:\Android\android-sdk\extras\google\usb_driver ???
This is making my head hurt....LOL
Click to expand...
Click to collapse
Yr head hurts????
Ive updated the cpuid guide u my wanna take 5 min timeout to read it, the answers r all in there
I don't use full sdk there's a link to mini sdk zip in that post just has ad and fast boot
I've never had to use google drivers
Just plugged my tab in and its just 'worked'
DL Acer drivers if u haven't already . These are the most important ones to have installed right.
Disconnect and reboot everything
Run Acer setup.exe
Plug USB in
Go into fast boot, win doze will want to install f/b drivers let win doze do it, but if they fail, then run again and choose let me install, blah, blah, blah
What OS u got? Vista/win 7 don't normally have any probs

Acer drivers have been installed and all relevant sdk packages installed and up to date AFAIK. (USB_Acer_1.06.1500_A30HA31H_A.zip)
Had no issues installing ICS Bootloader V.3 manually through APX (no auto script) via instructions so I know I can at least do that well.....LOL
Might have to try reinstalling USB drivers and see if that helps.
Thanks
EDIT: Reinstalled USB Drivers now I can't get adb working....F#@K!!!!!!!!!
EDIT II: Re-Re-Installed Drviers and ADB working again...yay...LOL
EDIT III: Used A500_Manager.exe, clicked on "Enter Fastboot" and windows installed and recognized drivers......DBL YAY!!!!
C:\Users\username>fastboot reboot
rebooting...
finished. total time: 0.165s
Now.......to Brick this puppy.....
Thanx for your help dibb_nz....looks like all I needed in the first place was a driver reinstall...HAHA.

Hek m8 for a second or two there, I was feeling ya pain, lol
Oh but the elation when it finally happens!!!!!
I dunno why those drivers act out like that, but it always the same....
Fail, reinstall, fail, reinstall u can understand why peeps get frustrated
Glad u got it m8

restore with nvflash in apx mode?

Hello,
I've done something very silly to my Nexus 7. I wanted to manually install a new boot.img via fastboot, but in haste i ran 'fastboot erase bootloader' and now it doesn't boot at all, not even the google logo.
I've read about NVflash but I don't have the partition information or other files to flash something working, though it does seem to detect the device.
Any help will be appreciated. It seems many nvidia devices have various custom tools to recover from apx mode, so hopefully something can be found for the Nexus 7 too.

You need the partitions for the 16gb or the 8gb version? I haven't done APX mode on the Nexus 7 but did on my old streak 7 and can probably pull off the files tomorrow (I have 16gb)

onilink67 said:
You need the partitions for the 16gb or the 8gb version? I haven't done APX mode on the Nexus 7 but did on my old streak 7 and can probably pull off the files tomorrow (I have 16gb)
Click to expand...
Click to collapse
That would be fantastic, I also have the 16 GB version!

So, would this mean that even when you completely kill the N7 by corrupting the bootloader, you can STILL recover?
That would be amazing.... something I'd wish my other Android devices would have, kill the bootloader on there and it's hard bricked, dead.
I'll keep an eye on this thread, this is something I am absolutely interested in as well
P.S.:
Is there a way to read / dump the required information from an N7 while it's OK and running?
Like a backup for later recovery.

If you want to try it on linux, grab the All-in-one package from here.
To get it to boot into APX mode i held all three buttons while plugging it in. To confirm it is in APX mode run lsusb and you'll see something like:
Code:
Bus 003 Device 005:[B] ID 0955:7330 NVidia Corp.[/B]
After that, assuming onilink67 can get the files, we can run something like:
Code:
./nvflash --bct nexus7.bct --setbct --bl bootloader.bin --configfile nexus7.cfg --create --go
And it may restore the bootloader.
hopefully on onilink67 can supply some better info since he already has experience with APX
Information taken from slatedroid.com, androidroot.mobi and androidroot.mobi

Subscribed! this is the exact problem i have run into. I cant get into my bootloader and device when connected.to the pc.installs a APX driver.by Nvidia
Sent from my HTC PH39100 using xda premium

OP and onilink would the files and partitions frim the 16gb be the same or would i need someone with a working 8gb to pull them for me?
Sent from my HTC PH39100 using xda premium

clago87 said:
OP and onilink would the files and partitions frim the 16gb be the same or would i need someone with a working 8gb to pull them for me?
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
normally you want the one from your device since this actually copies partitions some will be different on the 8gb model

This would be great to get a working solution. I screwed mine by blowing up the bootloader on accident. Luckily I could return mine to staples. I had "some" experience with nvflash with my G2x but I couldn't get it to do much.

Yea i am unlock and on custom rom but i read somewhere asus doesnt void warranty for that. Since I'm completely bricked they shouldnt be able to see I'm on clean rom. Some wishful thinking but this does sound like something viable if i could get those filea and partitions I would definitely give it a shot before calling it quits
Sent from my HTC PH39100 using xda premium

So last time I used APX mode I had a bct file provided to me. IIRC if tegra 2 didn't like the bct file it would refuse to do anything so for the sake of my nexus I hope Tegra 3 is the same. I'm going to research this a little more and hopefully can get something to you guys soon. FYI these files are normally huge

onilink67 said:
So last time I used APX mode I had a bct file provided to me. IIRC if tegra 2 didn't like the bct file it would refuse to do anything so for the sake of my nexus I hope Tegra 3 is the same. I'm going to research this a little more and hopefully can get something to you guys soon. FYI these files are normally huge
Click to expand...
Click to collapse
Here is to Tegra 3 being a little more mature than T2 and it works for us. If not I guess I have a year to contact asus and send em my paper weight. Thanks for helping out

The commands to do the backup should be fairly easy once you're in APX mode, according to this post:
powerx86 said:
./nvflash --bl bootloader.bin --getbct --bct backup.bct --go
./nvflash -r --getpartitiontable partition.txt
./nvflash -r --read 2 part2.img
./nvflash -r --read 3 part3.img
./nvflash -r --read 4 part4.img
./nvflash -r --read 5 part5.img
./nvflash -r --read 6 part6.img
./nvflash -r --read 7 part7.img
./nvflash -r --read 8 part8.img
./nvflash -r --read 9 part9.img
./nvflash -r --read 10 part10.img
./nvflash -r --read 11 part11.img
./nvflash -r --read 12 part12.img
Click to expand...
Click to collapse
which will generate the necessary bct file, and partition info, and a backup of all the partitions.
The trouble is the bootloader.bin, I'm not sure where to get that for our device. perhaps we can back it up with adb/fastboot.

might be silly but im guessing the bootloader info isnt in the img file nakasi-jro03d-factory-e102ba72 that you can download from one of the many threads correct?

onilink67 said:
normally you want the one from your device since this actually copies partitions some will be different on the 8gb model
Click to expand...
Click to collapse
I have a (working) 8G model
adfad666 said:
The commands to do the backup should be fairly easy once you're in APX mode, according to this post:
which will generate the necessary bct file, and partition info, and a backup of all the partitions.
The trouble is the bootloader.bin, I'm not sure where to get that for our device. perhaps we can back it up with adb/fastboot.
Click to expand...
Click to collapse
Amazing, I am going to try that ASAP!
clago87 said:
might be silly but im guessing the bootloader info isnt in the img file nakasi-jro03d-factory-e102ba72 that you can download from one of the many threads correct?
Click to expand...
Click to collapse
There is a bootloader.img in that download, I am fairly sure that's the one - not to be confused with the boot.img, which is the kernel AFAIK.
// EDIT
Narf, don't have a proper USB cable with me (at work ATM) so I gotta wait till home in about 9 or 10 hours :-/
nvflash must be used in Linux, right? There is no Windows tool for that?

I did the same thing... don't know what i was thinking. Was trying to get back to stock rom and now this... *sigh. If you guys manage to find a way would be most appreciated. I'm new to this APX stuff so been randomly trying to backup and restore just the bootloader provided by google. Haven't had any luck. It's either unknown device errors, and i haven't been able to find out the SBK either. Total bummer... I'm assuming that we'll be in the clear after restoring the bootloader?
HellcatDroid said:
I have a (working) 8G model
Amazing, I am going to try that ASAP!
There is a bootloader.img in that download, I am fairly sure that's the one - not to be confused with the boot.img, which is the kernel AFAIK.
// EDIT
Narf, don't have a proper USB cable with me (at work ATM) so I gotta wait till home in about 9 or 10 hours :-/
nvflash must be used in Linux, right? There is no Windows tool for that?
Click to expand...
Click to collapse

Maybe we need a nvflash version that supports the N7 or something.... where did the nvflash that's been linked to above come from?
We could ask nVidia for one.
Then again, I think this nvflash thing work with/for the Tegra CPU, so as long as it's provided with the proper input files it shouldn't be device specific - altough on that linked to page they had to use a custom binary to get things started....

Use the nvflash from the nvidia driver package, found here:
The ones floating around for various devices don't work, but I was able to get some responses from my device with that one.
Now I've hit another problem: I've been trying various things on my device, and now I can't get it into APX mode. In Windows the device connected sound constantly repeats, so I think I've drained the battery, and plugging it into the charger doesn't seem to charge it :/
Looks like I'll have to send it back...

Reading through this it seems there is a great deal of more information / data / files we need before we actually can use nvflash in PAX mode....
In order to get a working (e.g. --create) nvflash, we need a few bits of information as well as some files:
Secure Boot Key
BCT file (boot device setup, ram configuration and a bit more)
ODM data (board-specific bit-field specifying various board settings. *Needs* to be correct
flash.cfg (e.g. list of settings and names/identifiers of partitions.
Click to expand...
Click to collapse
The last thing ("flash.cfg") should be easy, I think it can be extracted / generated from a working device ("./nvflash -r --getpartitiontable partition.txt" should/could be it), but as for the rest....
adfad666 said:
Use the nvflash from the nvidia driver package, found here:
The ones floating around for various devices don't work, but I was able to get some responses from my device with that one.
Click to expand...
Click to collapse
Cool, thanks for that link, going to check it.
adfad666 said:
Now I've hit another problem: I've been trying various things on my device, and now I can't get it into APX mode. In Windows the device connected sound constantly repeats, so I think I've drained the battery, and plugging it into the charger doesn't seem to charge it :/
Click to expand...
Click to collapse
Yeah, the actual charging is handled by the kernel in LPM (low power mode), and it obviously needs a workgin bootloader to boot the kernel into LPM :-/

Here's a good description of the BCT/ODM, http://projects.pappkartong.se/a500/
Secure Boot Key - I don't think we need that as our bootloader is not locked / encrypted like other devices, though I could be wrong.
BCT file can be pulled from the device
ODM data can be pulled from the BCT
flash.cfg can be generated with ABX once you have the BCT.

Multi-platform 1-Click bootloader unlock for *ANY* 3rd Gen HDX (with VirtualBox)

UPDATE 2022-03-05: Network Access Snafu
During the last week or so, a server-side issue caused 1-Click to fail
either silently or with a "1-Click needs network access!" message
on startup. If you experienced the above, please try again!
Changed:
VirtualBox 6.1.x support (tested with 6.1.16)
works fine on Linux with Firefox and USB2 ports
tends to be flaky on MacOS with Safari; PLEASE use Firefox or Chrome!!
may need to connect via a USB2 hub or try different ports and cables
More accurate state assessment (i.e. rooted/unlocked/etc)
More aggressive planning logic
always look for ROM/GAPPS/SU in internal storage
may end up offering choices that make very little sense
Assorted fixes and improvements
hopefully fewer new bugs were introduced than old ones fixed
Unchanged:
No prerequisites on the device side
no root needed
full stock is OK
stuck in fastboot is fine
heck, it even works with _some_ soft-bricks
Does NOT work on Windows
1-Click is a virtual machine and a script that starts the VM in VirtualBox.
Unfortunately, VirtualBox on Windows fails to pass certain USB devices
including the HDX in bulk mode from Windows to the VM.
Network access required to grab the right aboot + TWRP for your device
Optional TWRP magic to auto-install ROM.zip, GAPPS.zip, and SU.zip from internal storage
PM me for a personal link and please state your regular HOST operating system.
Gotchas:
Requests without HOST OS information will be ignored.
Naturally, the same applies to requests with a Windows HOST OS.
Running 1-Click inside another VM is almost guaranteed NOT to work.
Link requests should be sent at the earliest 2 weeks after join date.
Freshly joined members are encouraged to spend some time
familiarizing themselves with the details of working with this device
by studying the relevant threads in this forum.
If you send a request be sure to monitor your account for replies!
A response should arrive within a week (or so), but the link is only valid for 2 days.
Don't miss your chance!

draxie said:
Title says it all..
(Well, almost: you need a vulnerable bootloader,
i.e. 3.2.3.2 or earlier, that foolishly accepts forged
signatures...)
Download and unpack the attached zip file.
Run the right '1-Click' script for your platform
(that is, '1-Click.bat' for Windows users,
and '1-Click' on OS X and Linux).
Simply clicking on the script works in Windows and OS X.
On these more "one-size fits all" operating systems, the scripts
-modulo network connectivity- will also download and install
VirtualBox, if it's not already installed.
Linux users need either VirtualBox or QEMU installed.
There are simply too many variants to automate this
for all the different distros. Sorry...
On some Linux variants, instead of launching the script
the click action opens the script in editor... YMMV
This may, in fact, be very useful, since on some of the same
Linux variants the script has to be run as root to avoid
automounters taking precedence; in which case, you're
well advised to make sure you read and understand what
the script is doing before you run it as root, because I take no
-that is: ZERO- responsibility for any damage that may result.
I personally tested the scripts on
Linux: Mint 17.2 (both 32-bit and 64-bit versions)
OS X: Mountain Lion, Yosemite, El Capitan
Windows: 7, 8.1, 10
The 1-Click VM runs a minimal Linux system with adb/fastboot
and a pure C "cuber" using OpenSSL's BigNum library.
No need to download adb/fastboot, python, or worry about
drivers on your host system.
Good luck!
Click to expand...
Click to collapse
Very cool! Will be interesting to try this out (have to wait for a someone with an eligible device that is willing to give it a whirl).

Any takers?
Davey126 said:
Very cool! Will be interesting to try this out (have to wait for a someone with an eligible device that is willing to give it a whirl).
Click to expand...
Click to collapse
BTW, this works with already unlocked devices also,
if anyone is willing to do some independent testing.
This is how I tested also... should be completely harmless.

Ran this against my HDX 7
Puttytel reported an 'error reading from serial device', but after it had initiated device shutdown so just a gui annoyance (I'm on windows, so commonplace.) It seemed to work, but I haven't verified yet..
> fastboot -i 0x1949 oem device-info
kindle fire [fastboot]
oem device-info...Device tampered: false
Ok.
I'll do some more testing later.

codeshane said:
Puttytel reported an 'error reading from serial device', but after it had initiated device shutdown so just a gui annoyance (I'm on windows, so commonplace.) It seemed to work, but I haven't verified yet..
> fastboot -i 0x1949 oem device-info
kindle fire [fastboot]
oem device-info...Device tampered: false
Ok.
I'll do some more testing later.
Click to expand...
Click to collapse
Thanks for reporting back!
The puttytel message is normal: the serial port it's talking to
disappears when the VM shuts down.
If/when you test again do check your Kindle after the fastboot prompt
appears but **before** you hit [Enter] in the puttytel window!
You should see "Unlock code correct" in green,
if the unlock worked...
Other than that, since you seem to have fastboot working, you can use
Code:
fastboot -i 0x1949 oem idme ?
to see if your device is unlocked (see here for a list of commands).

draxie said:
Other than that, since you seem to have fastboot working, you can use
Code:
fastboot -i 0x1949 oem idme ?
to see if your device is unlocked (see here for a list of commands).
Click to expand...
Click to collapse
C:\>fastboot -i 0x1949 oem idme ?
...
(bootloader) board_id: 0c0400
(bootloader) serial: xxxxxxxxxxxxxxxx
(bootloader) mac_addr: 00BB3Axxxxxx
(bootloader) bt_mac_addr: 00BB3Axxxxxx
(bootloader) productid: 0
(bootloader) productid2: 0
(bootloader) bootmode: 1
(bootloader) postmode: 0
(bootloader) bootcount: 203
(bootloader) panelcal:
(bootloader) time_offset: 0
(bootloader) signature:
(bootloader) idme done
OKAY [ 0.359s]
finished. total time: 0.361s
I feel rusty, haven't done any android dev in two years.. never tried to unlock a bootloader beyond 'fastboot oem unlock' before, but I really don't want them re-locking this one (they've taken root from me twice before.) I verified I have root still, but some apps are reporting that I don't. lame. more tests when I have some time, thanks for your time and effort!
Update:
Successfully flashed twrp recovery image recovery-twrp-recovery-2-8-1-0-apollo-t2991155
Happily considering ROMs to blow-away Amazon's 'os' with

codeshane said:
C:\>fastboot -i 0x1949 oem idme ?
...
(bootloader) board_id: 0c0400
(bootloader) serial: xxxxxxxxxxxxxxxx
(bootloader) mac_addr: 00BB3Axxxxxx
(bootloader) bt_mac_addr: 00BB3Axxxxxx
(bootloader) productid: 0
(bootloader) productid2: 0
(bootloader) bootmode: 1
(bootloader) postmode: 0
(bootloader) bootcount: 203
(bootloader) panelcal:
(bootloader) time_offset: 0
(bootloader) signature:
(bootloader) idme done
OKAY [ 0.359s]
finished. total time: 0.361s
Click to expand...
Click to collapse
codeshane said:
I feel rusty, haven't done any android dev in two years.. never tried to unlock a bootloader beyond 'fastboot oem unlock' before, but I really don't want them re-locking this one (they've taken root from me twice before.) I verified I have root still, but some apps are reporting that I don't. lame. more tests when I have some time, thanks for your time and effort!
Update:
Successfully flashed twrp recovery image recovery-twrp-recovery-2-8-1-0-apollo-t2991155
Happily considering ROMs to blow-away Amazon's 'os' with
Click to expand...
Click to collapse
Thoughts:
- take a backup of your current rom before flashing; leave it on the device until the new rom is stable (simplifies recovery)
- if you get a response from 'fastboot -i 0x1949 oem idme' your bootloader is unlocked!
- once you overwrite FireOS there is no chance of loosing root due to Amazon actions. OTA capability is baked into FireOS - not the device firmware.
- If you like AOSP go with Nexus v4. Any of the other HDX roms (CM11, CM12, SlimLP) are also fine choices. Each has a few minor quirks but no major 'gotchas'.

Sorry for the delay, wrote back a while ago but I guess it didn't post (cellular, pfft.)
Went for the Nexus v4 rom, which is running great so far. Thanks again for such a brilliantly simple unlock utility!

I have a few questions.
1. How can I tell I have a vulnerable bootloader?
I've been on Safestrap 3.7 and one of the early 4.2.2 Android Roms since the December after the HDX's release. My stock slot Fire OS hasn't been updated either. So am I on a vulnerable bootloader? How do I check?
2. Where do I start with this?
Is there anything I need to remove? Do I need to be on the stock Fire OS slot? Or do I simply run it as you stated.
3. After the unlock where do I go from there?
I'm so out of the loop I don't know what's the ideal stable rom to use .
Thanks, I'd appreciate any help .

zXiC said:
I have a few questions.
1. How can I tell I have a vulnerable bootloader?
I've been on Safestrap 3.7 and one of the early 4.2.2 Android Roms since the December after the HDX's release. My stock slot Fire OS hasn't been updated either. So am I on a vulnerable bootloader? How do I check?
2. Where do I start with this?
Is there anything I need to remove? Do I need to be on the stock Fire OS slot? Or do I simply run it as you stated.
3. After the unlock where do I go from there?
I'm so out of the loop I don't know what's the ideal stable rom to use .
Thanks, I'd appreciate any help .
Click to expand...
Click to collapse
Check your FireOS version in the stock slot. If 3.2.6 or below you can unlock the bootloader. The rollback procedure depends on the current version of FireOS. Report back and we'll go from there.

Just a little add-on to @Davey126's info:
3.2.3.2 and lower can unlock, 3.2.4 - 3.2.6 must downgrade first.
Once on 3.2.8 or higher you can NOT downgrade anymore due to rollback protection by Amazon, attempting would brick the device! So if you're on 3.2.6 or lower do NOT update!

Cl4ncy said:
Just a little add-on to @Davey126's info:
3.2.3.2 and lower can unlock, 3.2.4 - 3.2.6 must downgrade first.
Once on 3.2.8 or higher you can NOT downgrade anymore due to rollback protection by Amazon, attempting would brick the device! So if you're on 3.2.6 or lower do NOT update!
Click to expand...
Click to collapse
Just a quick comment: since there are no known adverse affects of a failed unlock,
you could just try unlocking to see if your bootloader is 3.2.3.2 or earlier..
If the unlock fails, you could move on to figuring out if downgrading is an option.

draxie said:
Just a quick comment: since there are no known adverse affects of a failed unlock,
you could just try unlocking to see if your bootloader is 3.2.3.2 or earlier..
If the unlock fails, you could move on to figuring out if downgrading is an option.
Click to expand...
Click to collapse
True!! But for for the 'typical' Kindle user (I know...sterotypes) working with a Windows host the effort to unlock far exceeds that of simply checking the FireOS version if still installed.

Hi, can any help why it keep telling me my kindle device is not connected? i using windowX86 and sure open the adb on kindle. thank you!

More accuracy please! (-;
fuxkamazon said:
Hi, can any help why it keep telling me my kindle device is not connected? i using windowX86 and sure open the adb on kindle. thank you!
Click to expand...
Click to collapse
Hi there,
I'm convinced that I can help you,
but I would need a more accurate
trouble report...
In the meantime, I'll try to give some background
and possible causes and remedies to what I think
might be your problem.
1-Click relies on VirtualBox's USB filter mechanism
to pass through any USB device with Amazon' s
vendorId (0x1949) to the 1-Click VM.
This may not always work.
The most common reasons are as follows:
No device is connected.
I presume this does *not* apply...
The device is in use.
This could happen easily, e.g. if you were browsing files on your Kindle.
Apart from possible privilege issues (see next bullet),
these kind of issues are usually solved by simply disconnecting
and reconnecting your device while the VM is running.
This is the most common/likely case, which 1-Click also tells you about..
Have you tried this? (Your report is not very clear on this.)
Possible lack of privilege.
I've only encountered this on Linux (as described in the first post),
but, then again, on all the Windows boxes I tested on, my user is
in the Administrators group; so, this may still apply there.
BTW, I'm guessing that you are on some 32-bit version of Windows,
although I must admit that the "windowX86" moniker in your post
doesn' t make this crystal clear.
Global USB filter rules in VirtualBox may override the rule used by 1-Click.
This only applies if VirtualBox had already been installed
and configured with global USB filter rules before 1-Click.
There may be other reasons, but the above should cover
the most obvious/common cases.

ty for you quick reply. i dun know what info i can provide but ill try. im now using this bl unlock on safestrap3.75 stock rom without opening or browsing any documents. yet, it show the samething i did last couple times. Here is,
Welcome to 1-Click
mount: proc mounted on /proc.
mount: sys mounted on /sys.
mount: dev mounted on /dev.
* daemon not run[ 1.269523] random: adb urandom read with 6 bits of entropy available
ning. starting it now on port 5037 *
* daemon started successfully *
Please make sure ADB is enabled on your Kindle
and connect the device to your computer
In case you don't already know, ADB is enabled by turning on the
'Settings/Device[ Options]/Developer Options/Enable ADB' option.
If 'Developer Options' is missing in 'Settings/Device[ Options]',
tapping 'Settings/Device[ Options]/Serial Number' seven times
will enable it..
Hit [Enter] to continue
No device appears to be connected..
You may need to disconnect and reconnect your device
Hit [Enter] to continue[ 27.214445] random: nonblocking pool is initialized
so hope you can find whats going wrong. ty!
draxie said:
Hi there,
I'm convinced that I can help you,
but I would need a more accurate
trouble report...
In the meantime, I'll try to give some background
and possible causes and remedies to what I think
might be your problem.
1-Click relies on VirtualBox's USB filter mechanism
to pass through any USB device with Amazon' s
vendorId (0x1949) to the 1-Click VM.
This may not always work.
The most common reasons are as follows:
No device is connected.
I presume this does *not* apply...
The device is in use.
This could happen easily, e.g. if you were browsing files on your Kindle.
Apart from possible privilege issues (see next bullet),
these kind of issues are usually solved by simply disconnecting
and reconnecting your device while the VM is running.
This is the most common/likely case, which 1-Click also tells you about..
Have you tried this? (Your report is not very clear on this.)
Possible lack of privilege.
I've only encountered this on Linux (as described in the first post),
but, then again, on all the Windows boxes I tested on, my user is
in the Administrators group; so, this may still apply there.
BTW, I'm guessing that you are on some 32-bit version of Windows,
although I must admit that the "windowX86" moniker in your post
doesn' t make this crystal clear.
Global USB filter rules in VirtualBox may override the rule used by 1-Click.
This only applies if VirtualBox had already been installed
and configured with global USB filter rules before 1-Click.
There may be other reasons, but the above should cover
the most obvious/common cases.
Click to expand...
Click to collapse

fuxkamazon said:
ty for you quick reply. i dun know what info i can provide but ill try. im now using this bl unlock on safestrap3.75 stock rom without opening or browsing any documents. yet, it show the samething i did last couple times. Here is,
Welcome to 1-Click
mount: proc mounted on /proc.
mount: sys mounted on /sys.
mount: dev mounted on /dev.
* daemon not run[ 1.269523] random: adb urandom read with 6 bits of entropy available
ning. starting it now on port 5037 *
* daemon started successfully *
Please make sure ADB is enabled on your Kindle
and connect the device to your computer
In case you don't already know, ADB is enabled by turning on the
'Settings/Device[ Options]/Developer Options/Enable ADB' option.
If 'Developer Options' is missing in 'Settings/Device[ Options]',
tapping 'Settings/Device[ Options]/Serial Number' seven times
will enable it..
Hit [Enter] to continue
No device appears to be connected..
You may need to disconnect and reconnect your device
Hit [Enter] to continue[ 27.214445] random: nonblocking pool is initialized
so hope you can find whats going wrong. ty!
Click to expand...
Click to collapse
This looks fine. The question is what you did next..
Have you tried disconnecting and reconnecting your Kindle
as the message above suggests?
(BTW, since this was the only direct question in my previous post,
I sort of expected you to answer that, but now you get another chance. )

just tried this. i had rooted my kindle when root first came out without safestrap as i didnt like all the restrictions of safestrap. i installed twrp much later and then cm 11 for twrp without an unlocked BL. tried this one click and had to disconnect and reconnect the tablet at one point, no biggie. at another it sat there with no instructions till i hit enter, but it did complete and said it was successful. so ty very much. at some point soon ill try a rom that requires an unlocked BL and see that my BL is really unlocked. great program if it really did work. will donate soon

I'm using Thor with stock 13.3.2.4 block OTA update and safetrap 3.75. So can i use this tool to unlock BL right away or i've downgraded 13.1.0.0 then unlock?

nickytun said:
I'm using Thor with stock 13.3.2.4 block OTA update and safetrap 3.75. So can i use this tool to unlock BL right away or i've downgraded 13.1.0.0 then unlock?
Click to expand...
Click to collapse
You can NOT unlock versions above 3.2.3.2, so you must downgrade first.
Good News is you can downgrade to 3.1.0 using the downgrade images provided by @ggow. Check page 2 here (page 1 is about 3.2.5/3.2.6 users who can NOT use these images!). Then flash TWRP, update the bootloader to 3.2.3.2, unlock the bootloader, then use ROM of your choice.
Read the info, ask if you've any questions before you brick your HDX! Note that factory reset in Safestrap means the standard wipe only (wipes data, cache & dalvik only)! Do NOT go into advanced wipe, do NOT wipe System!
Be sure to make backups of your current system (even if you don't need it anymore), remove the secondary slot(s) in Safestrap to get back the storage used by it (if you created any), and after installation of TWRP create a backup of your Fire OS before you flash any custom ROM.

[UNOFFICIAL][Guide] Update Original Shield Tablet to Android M (6.0)

Unofficial nVidia Shield Tablet (Original) Update to Android 6.0
| ROOT INCLUDED | Updated 1/21/16 |​
I take no credit for the development of this update other than this simplified guide. All of the development was from here mostly via the user 'fards' efforts, castrwilliam's found here, and Steel01 found here
THIS IS A MODIFICATION TO THE ORIGINAL SYSTEM PUT ON THE DEVICE BY NVIDIA. BY FOLLOWING THESE STEPS I ASSUME NO RESPONSIBILITY IF YOU BREAK YOUR DEVICE. THESE IMAGES ARE NOT FULLY TESTED. PROCEED AT YOUR OWN RISK KNOWING UNLOCKING THE BOOTLOADER VOIDS YOUR WARRANTY​
---------
Necessary Files
First, you'll need all of these files:
● https://drive.google.com/file/d/0B4WUjKii92l2bDl0UV9tS3BEbzA/view | This is the staging blob.
**************************************************(Pick ROOT method or non-root below)
● ***https://drive.google.com/file/d/0B4WUjKii92l2ZWROeFF6WTNaNFU/view | This is the rooted boot image (For use with Step 18 A)
OR
●***https://drive.google.com/file/d/0B4WUjKii92l2bHByWi1kaXZtWm8/view | This is the non-rooted boot image (For use with Step 18 B)
**************************************************(Ensure you follow the corresponding steps as addressed above)
● https://www.androidfilehost.com/?fid=24345424848487676 | This is the experimental TWRP for the Shield Tablet.
● https://www.androidfilehost.com/?fid=24345424848488107 | This is the reduced System Image file compatible with the original Shield Tablet.
---------
Installation Steps
Now begins the fun part, you will need to issue the following commands in order:
Step 1: You will need Fastboot drivers and be in a Fastboot permissible state on your Shield Tablet (Power button + Volume Down).
Step 2: Be in the directory you placed the files you downloaded (IE: "cd \users"username"\downloads")
Step 3: You will need to flash the Staging Blob downloaded from above. In a Command Prompt (or corresponding Window) type "fastboot flash staging blob.img"
Step 4: Power down the device and power on the device (it will bootloop).
Step 5: Return to a Fastboot permissible state (the bootloader).
Step 6: Issue the command "Fastboot getvar all" and ensure you see the line "(bootloader) max-download-size: 0x06000000" If you do not see that line, you flashed the blob wrong... so try again.
Step 7: Issue the command "Fastboot format system"
Step 8: Issue the command "Fastboot erase recovery"
Step 9: Issue the command "Fastboot format cache"
Step 10: Issue the command "Fastboot flash boot boot.img (Use your BOOT.IMG name, unless it is actually named 'boot.img'")
Step 11: Issue the command "Fastboot flash recovery twrpXXXXXXXXXXX (Not actually the recovery name, use tab-complete)"
Step 12: Issue the command "Fastboot flash system reducedsystem.img"
Step 13: Reboot.
Step 14: Return to a Fastboot permissible state.
Step 15: Issue the command "Fastboot format userdata"
Step 16: Reboot @terrigan (happy? )
Step 17: Wait for a long time at the "nVidia" logo.
Step 18: SEE LISTED OPTIONS BELOW
●STEP 18 A: Go through setup and in the Playstore install the app "phh's SuperUser"
OR
●STEP 18 B: Install SuperSU 2.65 BETA which can be downloaded https://download.chainfire.eu/752/SuperSU/BETA-SuperSU-v2.65-20151226141550.zip*FIXED
Step 19: Profit.
---------
Optional Stylus Support:
●The developer, fards, has also supplied us with the NVLauncher.apk which will give you the pop-up. That .apk is downloaded here: http://forum.xda-developers.com/attachment.php?attachmentid=3591547&d=1451326283
---------
Known Bugs
●Battery Drain (see fix)
---------
Battery Drain Fix
Thank you to @sockusminimus for finding this fix. What you need to do is be rooted and open a terminal emulator and issue these commands in order:
• su
• mount -o remount,rw /system
• chmod a-x /system/bin/logd
• Go wipe cache in TWRP
Utilizing this battery drain fix will break system logging.
---------
●A note for post-installation Android M end-users: DO NOT panic when the OS runs poorly. For the first several hours following install and use it will lag. This will subside, the ROM has a settling period. After the settling period, it SHOULD run smooth as stock OG shield 5.1.1
---------
Screenshots of OG Shield Tablet running Android M
●http://i.imgur.com/LtuQRyQ.jpg
●http://i.imgur.com/7hrLiOt.jpg
●http://i.imgur.com/aBKlixu.jpg
●http://i.imgur.com/yM02kD1.jpg

Nice - going to mess with this later and maybe get a 6.0 hybrid rom working.

Great work! Would you recommend it?
Stability and performance wise?
And is there not a chance we may get an OTA 6.0 for the original shield?

Thanks for putting it together.
If you run out of drive allowance I'll zip it all up and stick it on Afh.
I really like this mm build, but there's a lot of things can be done to improve on what Nvidia have done with this.
I quite like their nearly aosp builds, but there's still some slowdowns on sdcard access to work with, I don't understand why they feel the need for a ramdisk.
Virtual memory settings are bad, possibly because of the ramdisk.
Mounting the sdcard as a dynamic extension to internal memory is a great idea, if internal memory wasn't filed first, which throws up errors.
If I get a chance I'll look in to these. But no promises.

gotbass said:
Great work! Would you recommend it?
Stability and performance wise?
And is there not a chance we may get an OTA 6.0 for the original shield?
Click to expand...
Click to collapse
The ROM definitely needed settling time and was laggy for quite a while. But after I let all of the system apps update it runs very smoothly with expected battery life. So aside from the relatively complicated install, the experience is smoot.

fards said:
Thanks for putting it together.
If you run out of drive allowance I'll zip it all up and stick it on Afh.
I really like this mm build, but there's a lot of things can be done to improve on what Nvidia have done with this.
I quite like their nearly aosp builds, but there's still some slowdowns on sdcard access to work with, I don't understand why they feel the need for a ramdisk.
Virtual memory settings are bad, possibly because of the ramdisk.
Mounting the sdcard as a dynamic extension to internal memory is a great idea, if internal memory wasn't filed first, which throws up errors.
If I get a chance I'll look in to these. But no promises.
Click to expand...
Click to collapse
That sounds really great! If you would like some amendments to this or updated links.. Just let me know!

gotbass said:
Great work! Would you recommend it?
Stability and performance wise?
And is there not a chance we may get an OTA 6.0 for the original shield?
Click to expand...
Click to collapse
The OTA isn't expected until next year sometime.

IKOB3AST said:
The OTA isn't expected until next year sometime.
Click to expand...
Click to collapse
Thanks for your efforts.
Yeah the install looks like fun haha.

followed the steps and worked perfectly for me. now running android 6 on my og shield tablet

What about the killswitch?

hello, i have tried to flash that blob but the line you indicated on step 6, "(bootloader) max-download-size: 0x06000000", doesnt show up. any ideas?
C:\adb\platform-tools>fastboot getvar all
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno:
(bootloader) mid: 001
(bootloader) product: ShieldTablet
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) partition-size:bootloader: 0x0000000000600000
(bootloader) partition-type:bootloader: basic
(bootloader) partition-size:recovery: 0x0000000001000000
(bootloader) partition-type:recovery: basic
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-type:boot: basic
(bootloader) partition-size:dtb: 0x0000000000400000
(bootloader) partition-type:dtb: basic
(bootloader) partition-size:system: 0x0000000050000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x0000000040000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x0000000311600000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.137s
Update: I rebooted and went into a bootloop so something changed when i flashed it. I decided to go for it and everything installed perfect and im setting up 6.0 on og shield tablet.

Nailyouh said:
What about the killswitch?
Click to expand...
Click to collapse
Delete tegra-ota ?

fards said:
Delete tegra-ota ?
Click to expand...
Click to collapse
I mean is it possible that we wont recieve the switch due to updated Firmware ofc I will not try that hehe

Will this work on the LTE version?

Nailyouh said:
What about the killswitch?
Click to expand...
Click to collapse
Tested it on a pyrotab and the killswitch DID NOT activate!

aznmode said:
Will this work on the LTE version?
Click to expand...
Click to collapse
It does. I do not believe LTE will work though.

IKOB3AST said:
Tested it on a pyrotab and the killswitch DID NOT activate!
Click to expand...
Click to collapse
Thanks for being that brave haha I just have a pyrotab so I wont do it :b fear is stronger then being courios in this case :angel:

IKOB3AST said:
It does. I do not believe LTE will work though.
Click to expand...
Click to collapse
That's ok I don't use the LTE. Only reason I have the LTE version now is for the 32gb
Sent from my SM-N910T using Tapatalk

Thanx man! This seems intetesting. Is possible to revert to previous system configuration via nandroid backup twrp?
Sent from my LG-E975 using XDA Free mobile app

Paharsahath JG said:
Thanx man! This seems intetesting. Is possible to revert to previous system configuration via nandroid backup twrp?
Sent from my LG-E975 using XDA Free mobile app
Click to expand...
Click to collapse
No cuz u would backup the whole partition but u can use ie. Titanium backup for the appsettings and stuff works great IMO :good: