Develop Bugs

[Q] Need your help!

I'm not used to not having an SD card so now I am stuck in a hole hoping you guys can help me out. I am rooted but I mistakenly wiped everything on my tablet including the stock rom so now it wont even boot. Gets stuck on the boot screen. Because of this, I cant enable debugging in order to adb sideload or transfer a rom to flash. What can I do?

http://forum.xda-developers.com/showthread.php?t=2381582
[TOOL] 08/09/13 updated w/ factory images One Click Factory Restore (dead or alive)

fstbusa said:
http://forum.xda-developers.com/showthread.php?t=2381582
[TOOL] 08/09/13 updated w/ factory images One Click Factory Restore (dead or alive)
Click to expand...
Click to collapse
Says I need USB Debugging enabled...

I would try it anyway, you don't have much choice in the matter now. Have you tried a factory reset from recovery?
Get to the boot loader, go to recovery and press the volume up and power at the same time.

What happens if you power off, then power on while holding the vol down button?
That *should* get you to a point where you can use fastboot to unlock and flash a recovery or an OS.

roustabout said:
What happens if you power off, then power on while holding the vol down button?
That *should* get you to a point where you can use fastboot to unlock and flash a recovery or an OS.
Click to expand...
Click to collapse
I get to my bootloader which is still unlocked. I just dont know how to proceed after that. Sorry, I have been away from android for over a year now.

valdesr11 said:
I get to my bootloader which is still unlocked. I just dont know how to proceed after that. Sorry, I have been away from android for over a year now.
Click to expand...
Click to collapse
Download the factory image from here:
http://developers.google.com/android/nexus/images#razor
place the following files from your platform-tools (adb) in the resulting razor-jss15j directory
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
boot your tablet to the bootloader using Power+VolDown
connect via usb to pc
in command prompt in the razor-jss15j directory type
flash-all.bat

sfhub said:
Download the factory image from here:
http://developers.google.com/android/nexus/images#razor
place the following files from your platform-tools (adb) in the resulting razor-jss15j directory
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
boot your tablet to the bootloader using Power+VolDown
connect via usb to pc
in command prompt in the razor-jss15j directory type
flash-all.bat
Click to expand...
Click to collapse
You're a beast - This worked!
Thank you guys for all your help and I am sorry for the bother.

[HOW-TO] Root the Shield TV

First of all, let me say this isn't my post, and I didn't develop this method. The user, "Teletype" got this all figured out and did an amazing write-up for it. I'm posting it on their behalf so it can be in this newly added forum. The link to the recovery zip is also in his original thread, which I've linked below.
Here's the link to his original thread. If you feel the urge to press "thanks", please go to his original thread and press it for him, he deserves all the credit.
teletype said:
I just managed to get TWRP running on the new Shield console, and installed SuperSU successfully. Two caveats: the display is upside down, and the USB host ports don't work. I had to plugin a mouse via an OTG cable in order to interact with it. ETA: That's only an issue when booted to TWRP. Everything's working fine in the stock ROM after rooting.
Procedure:
- enable developer tools / USB debugging
- adb push supersu.zip /sdcard
- adb reboot bootloader
- fastboot oem unlock
- fastboot boot twrp-2.8.6.0-shieldtv-unofficial.img
- unplug USB cable, connect mouse via USB, install SuperSU
TWRP boot image is attached. Off to explore...
EDIT: by request, some more detailed instructions:
On the Shield device, head to Settings -> About, and click "Build number" 7 times. This will enable Android's Developer options.
Go to Settings -> Developer options, and enable USB debugging.
Install the ADB/fastboot drivers and utilities if you don't already have them. When "adb devices" shows your Shield, you're good to go.
Download and extract recovery.zip from this thread.
Head to the SuperSU forum and download the latest version.
Open a command prompt and navigate to the directory where you downloaded everything. (Google this for your OS if you don't know how).
With the Shield still booted, run "adb push supersu.zip /sdcard" (change supersu.zip to appropriate file name). This will upload the SuperSU update zip to your device, which you'll install from TWRP.
If that worked fine, run "adb reboot bootloader". Your device should shut down, and display the Fastboot screen after a few seconds.
FOLLOW THE NEXT THREE INSTRUCTIONS AT YOUR OWN RISK. This WILL wipe all your user data, back it up with ADB first if you want to preserve it. DISCLAIMER #2: I have no idea if there are any DRM keys or anything that get wiped when this is done (this was the case on my Xperia Z3 Compact). I will say that Grid streaming still works fine after doing this.
This step will unlock your bootloader to enable booting unsigned images.
Run "fastboot devices" and make sure your Shield is visible.
Run "fastboot oem unlock" and follow the prompts on the screen. Your bootloader is now unlocked.
Now, boot the TWRP image with: "fastboot boot twrp-2.8.6.0-shieldtv-unofficial.img" - Note: I used this instead of "fastboot flash" so I could keep the stock recovery around, to grab an image of it after rooting.
You should now see a TWRP recovery menu (upside down for now).
Connect a keyboard or mouse via OTG cable, and select "Install", navigate to your SuperSU zip, select it, and follow the prompts.
Click "reboot" and you should now be rooted.
Click to expand...
Click to collapse

does this have to be done with an otg cable

You can use the supplied micro USB cable to do the adb portion. You shouldn't ever need otg with this device since it also has 2 full sized USB ports.
Sent from my nexus 9 using XDA Free mobile app

Instructions got updated
Hi,
I have updated the instructions to ones that more closely aligned with my experience of doing this. The initial instructions were good for me - but some were in slightly the wrong order or not quite clear enough to be immediately intuitive. I've tried to fix that Hope it helps.
On the Shield device, head to Settings -> About, and click "Build number" 7 times. This will enable Android's Developer options.
Exit settings, then go back in to settings -> Developer options, and enable USB debugging.
Install the ADB/fastboot drivers and utilities on to your PC if you don't already have them. When "adb devices" shows your Shield, you're good to go.
Download the latest Super user zip file from the super user thread here.
Download and extract the recovery file from here. (it needs to be a .img not a .zip)
run "adb reboot bootloader". Your device should shut down, and display the Fastboot screen after a few seconds.
FOLLOW THE NEXT THREE INSTRUCTIONS AT YOUR OWN RISK. This WILL wipe all your user data, back it up with ADB first if you want to preserve it. DISCLAIMER #2: I have no idea if there are any DRM keys or anything that get wiped when this is done.
This step will unlock your bootloader to enable booting unsigned images.
Run "fastboot devices" and make sure your Shield is listed when you do so.
Run "fastboot oem unlock" and follow the prompts on the Shield's screen. You use the power button on the shield device itself to navigate the menu, and long press to select an option. Once you have confirmed, this can take along time to unlock (hour and a half for me on the Pro version). Your bootloader is now unlocked.
"Fastboot reboot" to reboot to AndroidTV.
run "adb push supersu.zip /sdcard/" (change supersu.zip to appropriate file name that you downloaded earlier). This will upload the SuperSU update zip to your device, which you'll install from TWRP.
Now, boot the TWRP image with: "fastboot boot RECOVERYFILENAME.img" - Note: I used this instead of "fastboot flash" so I could keep the stock recovery around, to grab an image of it after rooting. (change the name of the file in the instructions to the name of your recovery file that you downloaded).
After a short while you should now see a TWRP recovery menu.
Connect a keyboard or mouse via OTG cable, and select "Install", navigate to your SuperSU zip, select it, and follow the prompts.
Click "reboot" and you should now be rooted.
Click to expand...
Click to collapse

Anyone tried kingroot?

Sean09 said:
Anyone tried kingroot?
Click to expand...
Click to collapse
We have a factory supported way to unlock and root. No real point in trying to exploit the system. If you are rooted, you should have a custom recovery anyway, which means you need to unlock the bootloader anyway in case you need to fix something.

Hey, I have rooted my shield and I didn't backup my stock recovery, anyone have a stock recovery img, I want to update to 1.4
Thanks

Gig11gs said:
Hey, I have rooted my shield and I didn't backup my stock recovery, anyone have a stock recovery img, I want to update to 1.4
Thanks
Click to expand...
Click to collapse
You can download the 1.4 firmware and flash it manually. There's a discussion on it a few pages back :good:

Will I be able to get OTA updates if I root ?

rahulkadukar said:
Will I be able to get OTA updates if I root ?
Click to expand...
Click to collapse
You'll get the OTA notification but I was not able to install the OTA. You will need to download and new firmware and flash from fastboot.

Can I still root it this way if I already updated to 1.4 as I'm still fully stock and took the OTA

Im asking the same, im on the latest as of 2015 10 19, can i root using this method ?

baileyjr said:
You'll get the OTA notification but I was not able to install the OTA. You will need to download and new firmware and flash from fastboot.
Click to expand...
Click to collapse
You're guided imagery? I read without understanding very much

Can anyone confirm this rooting method works for new firmware 2.1?

garz said:
Can anyone confirm this rooting method works for new firmware 2.1?
Click to expand...
Click to collapse
I struggled to get root with this write up, and I am not a rookie. There were a few key steps missing, for example, you actually have to flash twrp, you can't just boot from twrp as suggested, if you are on 1.4 and up. Also, you have to let the unit reboot after you do the OEM unlock before flashing twrp. I didn't and mine just froze after flashing the recovery img. I found this write up http://nvidiashieldzone.com/index.php/shield-android-tv/root-shield-android-tv/
That one in the shield zone forum was so much more complete. And yes, it worked just fine with the 2.1 update. I did it yesterday with no problems. It will wipe out your data, and it will take a long time after you do the fastboot oem unlock, especially if you have the PRO version. But root is working with no problems.

RyanInBinary said:
First of all, let me say this isn't my post, and I didn't develop this method. The user, "Teletype" got this all figured out and did an amazing write-up for it. I'm posting it on their behalf so it can be in this newly added forum. The link to the recovery zip is also in his original thread, which I've linked below.
Here's the link to his original thread. If you feel the urge to press "thanks", please go to his original thread and press it for him, he deserves all the credit.
Click to expand...
Click to collapse
Do you want to build pre-root shiled TV firmware by nvidia open source？ and have experience？

Rooting.
KingRoot dose not work on this device.

Good guide thanks.

OK i have a 16gb model on 2.1, got adb hooked up but get this when trying to push supersu.zip to sdcard0:
C:\shield>adb push supersu.zip /sdcard1
failed to copy 'supersu.zip' to '/sdcard1': Read-only file system
Any ideas?

bearkilla said:
OK i have a 16gb model on 2.1, got adb hooked up but get this when trying to push supersu.zip to sdcard0:
C:\shield>adb push supersu.zip /sdcard1
failed to copy 'supersu.zip' to '/sdcard1': Read-only file system
Any ideas?
Click to expand...
Click to collapse
Try
Adb push supersu.zip /sdcard/
Inviato dal mio SHIELD Tablet utilizzando Tapatalk

Factory kernel or how to unbrick

I flashed the custom kernel posted here. Also I flashed the custom recovery. The question is that I wiped ALL, and now I dont have OS. I try sony pc utility to flash but not working.
Can someone send me the factory kernel to try to flash is and then mayne sony pc companion will work.
Thanks

Find the restore thread in android development, or my rollback thread in the general section. They have the system images for 5.0.1. They will work no matter what version you are on. But, you will need to roll forward to get to 5.1.3. Then, use classify to back them up.

lekofraggle said:
Find the restore thread in android development, or my rollback thread in the general section. They have the system images for 5.0.1. They will work no matter what version you are on. But, you will need to roll forward to get to 5.1.3. Then, use classify to back them up.
Click to expand...
Click to collapse
how to update? Pc Companion not working and update form wear seems to install but not install the last, still in 5.0.1
Thanks

You will need to get your hands dirty. Fastboot and adb.

lekofraggle said:
You will need to get your hands dirty. Fastboot and adb.
Click to expand...
Click to collapse
Can you be more specific?

Sure. Both threads have all the details, but here is the short of it.
Install the adb and fastboot drivers on your computer using a method appropriate for your computer's Os. I am on Win. 10 so I used the pdanet drivers (for adb on the watch Os and fastboot) and the general Google ones (for adb through twrp).
Put your watch in fastboot mode by putting it in sub mode then pressing the button twice.
Plug your watch into your computer
Open a command prompt
Type fastboot boot (or flash if you already unlocked your boot loader) <twrp.zip>
Reboot to recovery
On your computer type adb push <5.01.zip> sdcard/
On the watch, go into twrp and install the zip.
Reboot.
Let your watch sync and update (or not)
Good luck.

Nexus 7 - 2nd gen: update failed to Lollipop 5.1

HI everyone,
I updated "successfully" from Kitkat to 5.0.2 on my rooted (stock ROM) Nexus 7 second gen.
Unfortunately, when I tried to upgrade to 5.1 everything seem to be normal until the device rebooted and it went through the "update process". 3/4 the way through, the green droid went on his back and the "ERROR" message appeared.
I wiped the cache partition but that doesn't help. I tried to download the update in safe mode, but no success. I also find it odd that each time I reboot my device, I get a message from Android that it is "updating my apps".
If I didn't have any apps and a lot of data on my Nexus, I would wipe the device clean but I'd rather avoid this, if at all possible.
Is there a way to upgrade to 5.1 or reinstall 5.0.2 without losing everything?
Thanks

Michael Carleone said:
Is there a way to upgrade to 5.1 or reinstall 5.0.2 without losing everything?
Click to expand...
Click to collapse
No problem. As you rooted it before then presumably it is unlocked and equipped with custom recovery, so all you have to do is:
boot TWRP
connect PC
transfer data and APKs to PC
flash OS
If you don't have TWRP installed, then boot it like this fastboot boot twrp-3.0.2-0-flo.img

k23m said:
No problem. As you rooted it before then presumably it is unlocked and equipped with custom recovery, so all you have to do is:
boot TWRP
connect PC
transfer data and APKs to PC
flash OS
If you don't have TWRP installed, then boot it like this fastboot boot twrp-3.0.2-0-flo.img
Click to expand...
Click to collapse
Hi,
Thanks for the reply. I rooted with Kingroot. I don't believe I have a custom recovery. The bootloader is locked as shown when I boot into recovery mode.
I want to avoid transferring my data and APK files to my PC.
Should I assume there is no way of reinstalling the OS without wiping out the device?Also, there is no link in the above quote: fastboot boot twrp-3.0.2-0-flo.img

Since I got no other replies, I went and restored to factory image. I do have another question. I hope I get a better response there: http://forum.xda-developers.com/nex...a/nexus-7-2013-wifi-root-marshmallow-t3515072

Thanks for the reply.
Can we compare using fastboot flashing TWRP vs Nexus Root Tool Kit: http://www.wugfresh.com/nrt/? I ended up using this utility instead because it was pretty much one click and it didn't require command lines and for whatever reason, I found instructions using fastboot a bit confusing. Which method is better or has more advantages? I left my bootloader unlocked.
Incidentally, I think there was something wrong with my Nexus image. As a result, I did use Google's instructions on how to flash etc. the OEM image. Instructions weren't ideal but I managed to figure things out: https://developers.google.com/android/images
The instructions are here which I assume would be similar if I wanted to fastboot TWRP?
To flash a system image:
Download the appropriate system image for your device below, then unzip it to a safe directory.
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
Using the adb tool: With the device powered on, execute:
adb reboot bootloader
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device. For example, to put a Nexus 5 ("hammerhead") into fastboot mode, press and hold Volume Up + Volume Down + Power as the device begins booting up.
If necessary, unlock the device's bootloader by running:
fastboot flashing unlock
or, for older devices, run:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal and navigate to the unzipped system image directory.
Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
fastboot flashing lock
or, for older devices, run:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Click to expand...
Click to collapse
Also, I could've sworn that when I rooted KitKat on my Nexus, my data wasn't wiped out. I don't recall doing anything to the bootloader. I can't recall which method I used, but I know for certain I didn't use the Nexus Root Toolkit. I should've recorded my steps when I rooted.

i rooted my nexus 7 using towel root on kitkat .. i unrooted using supersu... and ota untill marhsmallow with out a problem never use kingroot as its so un stable.

Rooting build number NDE63V

Can you root using Boot-to-Root with build version NDE63V? I tried and was stuck in a permanent boot. If not do I need to flash an old factory image first? Thanks in advance

john7760 said:
Can you root using Boot-to-Root with build version NDE63V? I tried and was stuck in a permanent boot. If not do I need to flash an old factory image first? Thanks in advance
Click to expand...
Click to collapse
What command did you use in fastboot? Was it fastboot flash boot-to-root? Or fastboot boot boot-to-root?

Never use fastboot flash boot-to-root.img as you will bootloop.
ALWAYS use fastboot boot boot-to-root.img to root. Make sure you have downloaded the correct img from Chainfire's post.

xocomaox said:
Never use fastboot flash boot-to-root.img as you will bootloop.
ALWAYS use fastboot boot boot-to-root.img to root. Make sure you have downloaded the correct img from Chainfire's post.
Click to expand...
Click to collapse
I'll give that a try I may have inadvertently done just that. Many thanks

xocomaox said:
Never use fastboot flash boot-to-root.img as you will bootloop.
ALWAYS use fastboot boot boot-to-root.img to root. Make sure you have downloaded the correct img from Chainfire's post.
Click to expand...
Click to collapse
How long did it take for your first boot? Seems like it is taking forever but don't want to cut it off short

john7760 said:
How long did it take for your first boot? Seems like it is taking forever but don't want to cut it off short
Click to expand...
Click to collapse
It will take a few minutes vs the normal time.
You may be screwed up, however, and will have to follow the adb sideload procedure (THIS WILL NOT ERASE DATA) to right yourself before trying to root again:
Please reboot to the bootloader (Hold Power and Volume Down while powering on the phone)
Use the volume keys and choose recovery
At the No Command screen hold power and while holding power press and hold volume up for about 5 seconds, let go of volume up and power and it should take you to recovery.
At the top it will give you the Build number Example: NDE63X
Go https://developers.google.com/android/ota and download the OTA that matches your build number
Copy the zip file to the same folder ADB is in
Choose Update from ADB in recovery
Open command prompt on your pc
enter
adb sideload name_of_ota.zip
Replace name_of_ota with the correct file name.
And make sure your ADB is up to date with the Android SDK Manager!

xocomaox said:
It will take a few minutes vs the normal time.
You may be screwed up, however, and will have to follow the adb sideload procedure (THIS WILL NOT ERASE DATA) to right yourself before trying to root again:
Please reboot to the bootloader (Hold Power and Volume Down while powering on the phone)
Use the volume keys and choose recovery
At the No Command screen hold power and while holding power press and hold volume up for about 5 seconds, let go of volume up and power and it should take you to recovery.
At the top it will give you the Build number Example: NDE63X
Go https://developers.google.com/android/ota and download the OTA that matches your build number
Copy the zip file to the same folder ADB is in
Choose Update from ADB in recovery
Open command prompt on your pc
enter
adb sideload name_of_ota.zip
Replace name_of_ota with the correct file name.
And make sure your ADB is up to date with the Android SDK Manager!
Click to expand...
Click to collapse
Thanks for the help. I tried like 30 times to get it to start the recovery menu to sideload the OTA file without any luck. I gave up flashed stock image and relocked bootloader. Maybe one day I'll try again or if anyones in the Allentown, PA area hit me up