Database Users

[Q] Please help guys

I have installed 4.2.2 on nexus 7. As I had skipped account login at welcome screen, i could not login the account. I altered the apk of login. After factory reset my device has hanged on setup on welcome screen. I tried installing custom rom through stock bootloader but the bootloader says installation failed. How do I solve thia problem guys???

subin.nexus7 said:
don't know the exact steps, but i got it out of the APX mode and into the bootloader.
1. Tablet plugged into computer.
2. Held Volume Down + Volume Up + Power (simultatenously) for three seconds
3. And then released all, and pressed Power again.
4. Tablet booted into bootloader.
I thought that unlocking the bootloader ALWAYS voided the warranty, but in anycase I flashed reflashed ALL stock and locked the bootloader. Will be sending it to ASUS now. Thanks again!
EDIT:
So I wanted to verify that it was a CPU problem, and I downloaded StabilityTest again and ran the CPU load test. It crashed within two minutes, and went into AXP mode again. To get it out of AXP mode, the correct instructions:
1. Plug in the usb into computer
2. Hold Volume Down + Volume Up + Power simultaneously for like 15 seconds
3. The bootloader should show up.
4. If it doesn't, unplug the usb cable, and plug it back in and then repeat the these procedures.
Click to expand...
Click to collapse
Very helpful! I don't have a problem but I've read about others stuck in APX mode. This should be pinned if it works for those stuck in APX. Maybe you should change the thread title to something about APX solution so it draws some attention.

kieso said:
Very helpful! I don't have a problem but I've read about others stuck in APX mode. This should be pinned if it works for those stuck in APX. Maybe you should change the thread title to something about APX solution so it draws some attention.
Click to expand...
Click to collapse
Well... being stuck in APX doesn't necessarily mean your hardbricked. (Corrupt or erased bootloader).
But being hardbricked DOES mean your device will default to APX mode.
To use a mathematical metaphor, one is a SUBSET of the other.
-------
bftb0 has posted an exhaustive list of Nexus 7 button press combos here...
http://forum.xda-developers.com/showthread.php?t=2133986
... which includes how to pro-actively get into APX mode... although until somebody figures how to nvFlash the N7, APX is sort of redundant.
Rgrds,
Ged.

Delete

subin.nexus7 said:
I have installed 4.2.2 on nexus 7. As I had skipped account login at welcome screen, i could not login the account. I altered the apk of login. After factory reset my device has hanged on setup on welcome screen. I tried installing custom rom through stock bootloader but the bootloader says installation failed. How do I solve thia problem guys???
Click to expand...
Click to collapse
I'm sort of confused about the relationship between your edited post and what (apparently ?) kieso quoted, but I'll throw out a few suggestions:
1) AFAIK, there is no way to flash a dev ROM using fastboot (only the boot image of a dev ROM can be flashed this way). You said "bootloader", not "custom recovery" ... so that implies using fastboot. If that is not the case, then your use of terminology is not correct. (It's a computer - reporting details correctly is incredibly important).
2) If you bypass the WiFi login, an account can be added at any time later using the settings menu or simply by launching the Google Play (market) app - there is no need to "alter the apk of login", whatever that means.
3) I would recommend at this point that you start completely over by flashing a factory ROM using fastboot - see the sticky thread about returning to stock using fastboot. If you already have the 4.18 bootloader installed, I recommend you avoid like the plague any operation involving flashing the bootloader.
4) It should be obvious from the trouble that you got yourself into that you should learn what nandroid backups are and that you START USING THEM. The first thing you do after rooting is "make a backup", not "flash a ROM"
good luck

Thanq so much.But still some clarification needed
Now What do I do? My nexus 7 can't pass through at welcome screen saying saying unfortunately setup wizard has stopped. and in recovery{i have no custom recovery, I use bootloader 4.18} i cant flash any rom. I just want to start device any how.. any way.. Is there any way??

subin.nexus7 said:
Now What do I do? My nexus 7 can't pass through at welcome screen saying saying unfortunately setup wizard has stopped. and in recovery{i have no custom recovery, I use bootloader 4.18} i cant flash any rom. I just want to start device any how.. any way.. Is there any way??
Click to expand...
Click to collapse
I guess I am having trouble understanding the sum total of information you have provided - I guess you have omitted some information or mis-stated something. No custom recovery sort of implies a full stock device, but yet you previously mentioned modifying/changing an .apk in /system... normally that would be possible only with a rooted ROM or a custom recovery to do that.
If your tablet is 100% stock, a factory reset of the tablet should allow you to boot once again - at the cost of deleting everything you put on the device, including all files you put on the (pseudo-) SD card.
If that is the case:
- press and hold power+vol-down until the bootloader screen shows up
- use vol-up/vol-down to select "start recovery" and press the power button
- an android lying on it's back should show up; this is the stock recovery splash screen, so
- press power+vol-up simultaneously for about one second - the stock recovery menu should show up
- select factory reset (with vol-up/vol-down) and press the power button.
good luck

bftb0 said:
I guess I am having trouble understanding the sum total of information you have provided - I guess you have omitted some information or mis-stated something. No custom recovery sort of implies a full stock device, but yet you previously mentioned modifying/changing an .apk in /system... normally that would be possible only with a rooted ROM or a custom recovery to do that.
If your tablet is 100% stock, a factory reset of the tablet should allow you to boot once again - at the cost of deleting everything you put on the device, including all files you put on the (pseudo-) SD card.
If that is the case:
- press and hold power+vol-down until the bootloader screen shows up
- use vol-up/vol-down to select "start recovery" and press the power button
- an android lying on it's back should show up; this is the stock recovery splash screen, so
- press power+vol-up simultaneously for about one second - the stock recovery menu should show up
- select factory reset (with vol-up/vol-down) and press the power button.
good luck
Click to expand...
Click to collapse
when you say at the cost of deleting everything, does this include deleting everything in the bootloader because thats what I did when I used the command "fastboot erase bootloader"

[TUTORIAL][CM11][4.4.2] CyanogenMod Tutorial for Sony Xperia Tablet Z (pollux)

I went through a lot of searching and trouble to install CM11 on my Xperia Tablet Z, and I'd like to share a tutorial I made for anyone who is also wanting to accomplish this.
All links are in Dark Green because I cannot post links yet.
1. Download and extract the ADB+Fastboot+Drivers zip (alexpja.com/sony/adb-fastboot-win.zip)
2. Now we’ll unlock the bootloader.
a. If you do not have a Phone app (like I don’t on the SGP351), you can either get the IMEI from About -> Status in the settings OR you can find the IMEI right after the IC code, nearby the barcode on the bottom of the tablet.
b. If you do have a Phone app, enter *#06# to retrieve the IMEI.
c. Save this for later use.​3. Place the tablet into fastboot mode and connect it to the computer.
a. Power off the device
b. Connect USB to computer
c. While plugging in the other side of the USB cable into the tablet, hold down the Vol + button.
d. If your speakers are on, you should a sound.
e. We have to install the drivers for fastboot. Open devmgmt.msc via the Run window or in the Start menu and in Other Devices section, you should see S1 Service or S1 Fastboot (anything containing S1).
i. If it is showing a yellow exclamation mark: Follow 3.e.i.1. If it is not, continue to 3.f.
1. We need to download Flashtool and use the driver setup. Download Flashtool (unrestrict.li/flashtool) and install it.
2. Find cmd.exe, right click it, and select Run as administrator.
a. Type in
Code:
bcdedit /set testsigning on
and press enter.
b. Reboot your computer.​3. Once you have rebooted the computer, open the folder where you installed Flashtool (default: C:\Flashtool).
4. Open up the drivers folder and open Flashtool-drivers.exe.
5. Select the first two driver choices (Flashmode and Fastboot) and select “Xperia Tablet Z Drivers” and continue.
6. A new window will appear, continue on with that.
7. A window like this may appear a few times, just press Install this driver software anyway.
8. Run 3.e.2. again and run
Code:
bcdedit /set testsigning off
. Reboot your PC now or after the tutorial.​f. The LED pulse light above it should be emitting a blue-ish color. The screen will be dark.​4. Now we’ll verify if you have fastboot running.
a. Open the tools folder that was extracted from the ADB ZIP and double-click on START.cmd to open Command Prompt in the current directory (all it does is literally open cmd.exe, you can edit the script to verify).
b. Run the command
Code:
fastboot -i 0x0fce getvar version
. If you get
Code:
<waiting for device>
, then you did something wrong. Retrace your steps! (For example, I get
Code:
version: 0.5
)​5. Go to (unlockbootloader.sonymobile.com) and continue until you reach the screen where you put type in the IMEI and an email address. Type in the first 14 digits of the IMEI (remove the last one) and your email address (not sure if name is required). You should get an email instantly with the key.
6. In the Command Prompt, run
Code:
fastboot -i 0x0fce oem unlock 0xKEY
where KEY is the key you received in the email from Sony.
7. Download whatever release you would like to use on the tablet (I’m using CM 11 nightly) from (download.cyanogenmod.org/?device=pollux)
a. Optional: Also download gapps for Google apps such as Gmail, Google Play Services, etc. (wiki.cyanogenmod.org/w/Google_Apps)​8. Extract the ZIP file (but don’t delete it either) and copy boot.img to the tools folder.
9. If your device is still turned off, turn it on and enable USB storage mode. Copy the CM zip to either the internal storage (sdcard) or, if one is inserted, the microSD card (sdcard1).
10. Place it into fastboot mode again (#3).
11. Go back into the Command Prompt and enter:
a.
Code:
fastboot -i 0xfce flash boot boot.img
b.
Code:
fastboot -i 0xfce reboot
c. Enter recovery.
1. Once it shuts down, rapidly tap the Vol + button in order to get into the recovery.
2. Grep_The_Truth's tip: Look at the LED. It will turn orange and afterwards it'll turn purple. You want to press Vol+ as soon as it changes colors.​12. Select “wipe data/factory reset” and wipe it. Afterwards, go back to main menu.
13. Select “Install zip” and either select “Choose zip from /sdcard” (internal storage) or “Choose zip from /storage/sdcard1” (microSD card).
I’ve had varying experience with installing from the /sdcard because sometimes it doesn’t want to mount /data while wiping (/data/media which is /sdcard is safe in wipe) the tablet, so if you were to install the zip from /sdcard with the error present, it would screw things up. I prefer the microSD card route (/storage/sdcard1), and you don’t even need a big one. 512MB works just fine. The actual path would be /sdcard/0/ when looking for the cm.zip in the internal storage.
14. When you have chosen to install from either /sdcard or /storage/sdcard1, select the cm.zip and install it.
a. If you downloaded gapps.zip, install it the same way as you did with the cm.zip.​15. Go back to the main menu now and select “reboot system now”
a. Once, I had the option to install root access before rebooting, I declined (was planning on rooting after tutorial) but it gave me root anyway.​
That’s it! You can now use CyanogenMod with the Sony Xperia Tablet Z.

Getting in to recopvery
I just struggled with entering recovery for way too long and I want to help others avoid this. I kept finding vague instructions.
The step I want to clarify is:
c. Once it shuts down, rapidly tap the
Code:
Vol +
button in order to get into the recovery.
Click to expand...
Click to collapse
This didn't work for me because if you press Vol+ too soon it goes right back in to fastboot mode. If you press it too late you will miss the recovery mode. You only have to press Vol+ once.
Please change step c. to read:
Look at the LED. It will turn Orange and then Purple. You want to press Vol+ as soon as it changes from Orange to Purple to enter recovery mode.

Grep_The_Truth said:
I just struggled with entering recovery for way too long and I want to help others avoid this. I kept finding vague instructions.
The step I want to clarify is:
This didn't work for me because if you press Vol+ too soon it goes right back in to fastboot mode. If you press it too late you will miss the recovery mode. You only have to press Vol+ once.
Please change step c. to read:
Look at the LED. It will turn Orange and then Purple. You want to press Vol+ as soon as it changes from Orange to Purple to enter recovery mode.
Click to expand...
Click to collapse
I'll add it along with mine, because I can do it with no problem.

alexpja said:
I'll add it along with mine, because I can do it with no problem.
Click to expand...
Click to collapse
alexpja Thanks for your tutorial, this is very detailed and easy to follow.
my Xperia is SGP321.
I put it into practice and the results it gives me the "oem unlock" is:
FAILED: (remote: Command nor allowed).
I guess you should treat my tablet has the bootloader locked and not allowed (for now??) the unlocked.
I hope someone gives us the opportunity to unlock the devices and in the future can be unlocked.

I had the same experience where at times the steps were a little confusing, especially for a beginner. Each set of instructions would either leave something out or skim over it as if everyone already knew it. That's understandable since they were probably written for that audience. I soft-bricked my SGP311 at least 10 times.
I was even going to write something like this but I got lazy.
One suggestion I would offer is to request the bootloader unlock key first since it sometimes takes a little while and a person can reduce the possibility of having to stop and wait just when they are making progress.
And for anyone going this route for the first time, don't make my mistake - flash exactly what the instructions say to flash, particularly boot.img. Once you have that recovery flashed you have a lot more control over your device. If something goes wrong in a following step like getting boot loops you can still fix it. But if you get annoyed and start poking at it then you can mess up the recovery. Then you have to reset everything to stock and just about start over.
While I don't want to say something stupid like claiming the tablet is indestructible, I found that whether I got stuck in a boot loop I couldn't get out of or screwed it up so bad that all I could get from the tablet was an occasional LED flash, I could always restore it using Emma. It's annoying to have to start all over but it's a huge relief when it boots normally.

for me flashing was fine and without any error but my Tab doesn't boot up with CM flashed...any idea?

Hanging at reboot
Hi.
I tried this procedure on my sony xperia tablet z 311. It unlocked fine and wrote boot.img fine but on reboot command, I get a red light and it hangs there.
I've managed to get it back to fastboot mode (pressing power and vol+, some white blinking lights).
But that's it, that's all I can do with this right now. It's a brick that can get into fastboot mode and that's it. Any time I write a boot.img (have tried a different one also), it writes fine but hangs with a red light at reboot.
Edit:
Used Sony's Emma in flash mode to get back to stock, tried again and it worked.
Maybe the problem was using the pollux instead of pollux_windy download, my bad.

Guess my bootloader won't be unlocked. This is A lot of work. Good job on the write up though maybe one day I'll tackle it.

BOOT LOOP Step 9
All was going well, but step 9 powering on device, now its looping.....Ill use flash tools to put jelly bean on and try again, since i was trying with kitkat...why i suspect kitkat is the issue, before i used to be able to unlock and lock boot-loader with jelly bean but with kitkat it didn't work, which i then forced it via cmd

No GPS
I used the tutorial for my Pollux Windy (WiFi Only) and used the latest nightly. everything went well but my GPS is now broken. Is this a known issue?

kevinsickles said:
Is this a known issue?
Click to expand...
Click to collapse
yep! use search to find out more.

mulebreath said:
Hi.
I tried this procedure on my sony xperia tablet z 311. It unlocked fine and wrote boot.img fine but on reboot command, I get a red light and it hangs there.
I've managed to get it back to fastboot mode (pressing power and vol+, some white blinking lights).
But that's it, that's all I can do with this right now. It's a brick that can get into fastboot mode and that's it. Any time I write a boot.img (have tried a different one also), it writes fine but hangs with a red light at reboot.
Edit:
Used Sony's Emma in flash mode to get back to stock, tried again and it worked.
Maybe the problem was using the pollux instead of pollux_windy download, my bad.
Click to expand...
Click to collapse
Hi,
I've been trying with my Xperia Tablet Z Wi-Fi SGP311. Ran into the same problem. On reboot command the LED was stuck on red for 10 minutes and the cmd window was still open. I unplugged the USB and the LED would not turn off. Tried some things, I don't remember specifically what, but it got the LED to turn off. Now my device can't be detected. I've downloaded Emma and it is not recognising my tablet. I've tried to plug the USB in while hold Vol +, Vol -, and the Power button. No detection for any. All I can do with my tablet is make the LED flash white, purple and red in rapid succession by holding Vol + and Power for 5 seconds.
Anyone know what's happened? I suspect I've completely bricked it :L
EDIT: Apparently there are different modes which you can cycle through. If you hold down Vol + and Power for 5 seconds, the LED will flash according to which mode the tablet is in. The different modes give these flashes:
- 1 White flash
- 3 Rapid which flashes
- A white, purple and red flash in quick succession
To switch between the modes, I hold down Vol+ and Power, and after 5 seconds it will take around 3 more seconds to change modes. One of these modes will not appear unless plugged into a PC. What do these mean and can I do anything with it? Tablet is still bricked.
EDIT2: I've managed to get Emma to recognise my tablet. Turns out the modes do have different purposes. I should be fine now, problem solved. I will just leave the solution here in case anyone runs into the same problem.
Unplug your device and hold Vol + and Power for 10 seconds. At the 5 second mark your LED should flash white ONCE. Keep both buttons held and within 5 more seconds, your LED will flash white THREE times consecutively. This will allow you to enter Flashmode (plug in USB while holding Vol -) and Fastboot (plug in USB while holding Vol +). For Emma to recognise your device, enter Flashmode and you can restore and try again.

Bootloop
I've tried many times to flash cyanogenmod onto my Xperia Tablet Z (SGP311). This is a Wi-Fi only tablet and I have downloaded the versions of CM from (download.cyanogenmod.org/?device=pollux_windy) I've followed all of the steps and tried all of the versions of CM down to 10.2 (I used GApps10.2 for CM10.2). Each version gets stuck in bootloop. I've cleared all data (in CWM - wipe data/factory reset, wipe cache partition, wipe delvik cache) before flashing CM and GApps; however, when I try to clear data I get an error. This is what the tablet says:
-- Wiping Data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cacha
Formatting /sd-ext...
Formatting /sdcard/.android_secure!
Skiiping format...
Data wipe complete.
Click to expand...
Click to collapse
I'm thinking the "Error mounting /data" is the problem, but I'm not entirely sure, nor am I sure of how to fix it.
Any suggestions?
EDIT: Turns out I'm just really bad with Android stuff. I ended up flashing the original Xperia software, unlocking the bootloader (according to this tutorial's instructions), then I downgraded to 4.1.2, rooted my tablet (forum.xda-developers.com/showpost.php?p=53063218&postcount=14) and installed the PhilZ and TWRP custom recoveries. I didn't get to use them in the end. For some reason CWM kept coming up no matter what combination of buttons I pressed while rebooting. After downgrading and rebooting, I followed the rest of the instructions on this tutorial (from step 7). This time I got no errors while cleaning the disk, cache and delvik cache. Flashed the zip files, rebooted the device and voila, Cyanogenmod11!
Again, I'll leave this edit here in case someone runs into a similar problem. I couldn't get any version of CM until I rooted first.

I followed this guide and bricked my device. If anyone has any tips - PLEASE HELP!
I tried to flash CM11, all seemed to be going great until CM11 and Gapps where installed any I hit "Reboot system now" in CVM. The device never booted again (I which I knew why!), and is now pretty much dead. I can however:
- Enter Flashmode
- Enter Fastboot mode
- Relock/Unlock bootloader
- Emma recognizes my device just fine in flashmode.
So I still think there is some hope, right?
I have tried installing the firmware that Emma suggests, doesn't work.
I have tried flashing a firmware I found on the internet with Flashtool, doesn't work.
I have tried relocking the bootloader and trying to repair the device through SUS, doesn't work.
So, PLEASE, help my sort this out! I would be forever greatful!

tp_88 said:
I followed this guide and bricked my device. If anyone has any tips - PLEASE HELP!
I tried to flash CM11, all seemed to be going great until CM11 and Gapps where installed any I hit "Reboot system now" in CVM. The device never booted again (I which I knew why!), and is now pretty much dead. I can however:
- Enter Flashmode
- Enter Fastboot mode
- Relock/Unlock bootloader
- Emma recognizes my device just fine in flashmode.
So I still think there is some hope, right?
I have tried installing the firmware that Emma suggests, doesn't work.
I have tried flashing a firmware I found on the internet with Flashtool, doesn't work.
I have tried relocking the bootloader and trying to repair the device through SUS, doesn't work.
So, PLEASE, help my sort this out! I would be forever greatful!
Click to expand...
Click to collapse
download a proper stock (not bricked) firmware for your device and flash with flashtool.

Rootk1t said:
download a proper stock (not bricked) firmware for your device and flash with flashtool.
Click to expand...
Click to collapse
What makes you think that the stock firmwares I've tried are bricked? I've since my post tried one which I downloaded through Flashtool - same result.

[Noob Guide] Rooting a Verizon (XT1096) or ATT (XT1097) Moto X 2014 Running Lollipop

MoFo will NOT work on 5.1 so do NOT upgrade to the 5.1 bootloader or partition table if you want to use MoFo.
This method involves purchasing a piece of software named mofo.exe that allows you to flash a modified, unsigned system image to your device despite its locked bootloader. The cost is $20. Links to the modified images for the XT1096 and XT1097 are found in the OP of the MoFo support thread:
http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404
This Method Does Not Disable Write Protection. Please read the following post if you don't know what that means:
http://forum.xda-developers.com/showpost.php?p=60412113&postcount=292
This Method Trips the Root Checker and Your qe Will Convert to qe 1/1 Permanently! What this means is that if you boot your phone into recovery, you will see qe 1/1, which means you are currently running modified software. The qe will stay at 1/1 even if you flash back to stock.
1. Check Your Software Version and Enable USB Debugging
Go to Settings -> About Phone and read your Android Version – it should say 5.0 on the XT1096 and 5.0.2 on the XT1097. If not, and it says 4.4.4, you are still on 4.4.4 and as long as you have not modified your system by flashing using mofo.exe, you should still be stock and can take the 5.0 or 5.0.2 OTA.
If you haven’t already, go into Settings -> About Phone and click on Build Number repeatedly until you get the message you are developer now (or something like that). Then hit the back button and you will see that the Developer Options now appear. Click on Developer Options and check USB Debugging.
2. Install Motorola Device Manager (MDM) and Drivers to Your Computer
You can download MDM and the drivers here:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Install MDM on your computer after you download it. MDM should install the drivers.
3. Download Copies of Adb and Fastboot
You can get these from the Adroid SDK but you don’t need the whole Android SDK. Root Junky has the files you need on his site here:
http://rootjunkysdl.com/?device=Adb Fastboot Files
I made a folder on my computer named c:\mx2014 and put the zip file in there. Then I unzipped it with 7-zip.
http://www.7-zip.org/
4. Download a Copy of the Official Firmware
Root Junky has a copy of the XT1096 5.0 official firmware here:
http://rootjunkysdl.com/?device=Moto X 2014&folder=Official Firmware
and the XT1097 5.0.2 fxz is here:
http://www.filefactory.com/file/1cekivswpakf/VICTARA_ATT_XT1097_5.0.2_LXE22.46-34_cid1_CFC.xml.zip
You should download it into a separate folder (I put mine in a folder named c:\mx2014\lollipop) and unzip it so if you have any problems you can flash back to stock. Place a copy of fastboot.exe, adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll in the folder with the lollipop official firmware.
Also if you are planning on taking the 5.1 OTA when it is released, you would need to flash your system back to stock so it is a good to have it ready. And if you are planning to update to 5.1 via MDM I would still flash back to stock because if you don't, IME MDM will detect that you are running a modified software and will wipe your device when it upgrades you to 5.1. If you flash back to stock first, MDM will not wipe your data and sdcard when it upgrades you to 5.1.
5. Test the Drivers and Adb
Once you have completed Steps 1-3, you can test the drivers and adb. Power on your phone and after it boots, connect it to your computer via the data cable. Open a command prompt, and then navigate to the directory where you have adb and fastboot by typing:
cd c:\mx2014 (or wherever you have adb and fastboot stored)
and hitting enter. Then type:
adb devices
You should then see a prompt on your phone asking you to authorize your computer. Check always allow and click OK. Adb should show you the serial number (not the IMEI) of your device.
Now type:
adb reboot bootloader
to get into bootloader (BL) mode (aka fastboot mode).
6. Test the Drivers and Fastboot
Once you are in BL mode, double check that on your phone’s screen right above the first green line you see this:
Transfer Mode: USB Connected.
If it does not say that, go to Root Junky’s site and download the Motorola drivers and manually install them.
http://rootjunkysdl.com/?device=Android Drivers&folder=Motorola
Then type:
fastboot devices
and hit enter. Fastboot should return your device’s serial number.
7. Test Getting into Recovery and Wiping Cache
While in BL mode, scroll down to Recovery by pressing the vol dwn button to highlight Recovery. Then select Recovery by pressing vol up. You should see the dead android with a red triangle having an exclamation point in it coming out of its stomach. Then press the pwr button for a couple of seconds and then press and release the vol up button and then release the pwr button to get into the recovery menu. Use the vol dwn button to scroll to wipe cache partition and then press the pwr button to select it. You should see that the cache is being formatted.
When cache is done being wiped, the recovery menu should reappear and you should hit the pwr button to reboot into system.
8. Test That You Know How to Get Into Bootloader Mode Using Buttons
Disconnect your phone from your PC, power down your phone and then hold down volume down and then press and hold the power button. Hold both buttons simultaneously for about 4 seconds and then release the power button and then the volume down button. This should put you in Bootloader mode (aka fastboot flash mode). Alternatively, you can try pressing volume down + volume up + power and holding for about 4 seconds then releasing.
Once in BL mode, you can either hit the power button to boot back into Android or if you want to test that you know how to flash back to a stock system, complete the instructions in Step 9.
NOTE – flashing the system partition does NOT affect your apps/settings/text messages/call history, which are stored on the data partition, not the system partition. Updates to system apps since 5.0/5.0.2 was rolled out will be lost as well as any system app settings that are relevant to the updates or stored on the system partition.
NOTE – flashing the system partition does NOT affect your stored media (e.g, pictures, music, videos), which are stored on the sdcard partition, not the system partition.
9. Test That You Know How to Flash Stock System (Optional)
While in BL mode you can test that you know how to flash back to a stock system. This is optional but if you have never done it before, it is a good idea to do it IMO. When you flash a system.img, you do not lose your apps/data/texts or your media unless the app is a system app, then you will lose the updates since 5.0 was rolled out (but those can be re-downloaded from the Playstore). However, it is always a good idea to backup before you flash in case you do something wrong. I use SMS Backup and Restore to backup my texts and my photos are backed up to my Google account.
Put your device in BL mode and then connect it to your computer. Open a command prompt and navigate to where you have the stock 5.0/5.0.2 image stored on your computer. Type the following:
fastboot flash system system.img_sparsechunk1
and then hit enter to flash the first sparsechunk. Repeat for the other sparsechunks until you have flashed all 9 of them. Then boot into recovery, wipe cache and boot into system.
10. Purchase MoFo.exe
First you should go to:
http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404
and read all of the information. And be sure to watch Root Junky’s video here:
https://www.youtube.com/watch?v=AXAYjbf76II&feature=youtu.be
The high level summary of what you will be doing is this:
1. Verifying that your device qualifies for purchasing mofo.exe by using MoVerify;
2. Using the link generated by MoVerify to navigate to where you can purchase mofo.exe; and
3. Purchasing and downloading mofo.exe.
11. Download, UnZip and Flash a Pre-rooted Ext4 Image
The OP of the MoFo thread has links to the pre-rooted images that are available for the XT1096 and XT1097. Once you download one of them, unzip it and move the image file to wherever you have mofo.exe stored on your computer. Put your device into BL mode and connect it to your PC. Then navigate to where mofo.exe is stored on your computer, click on mofo_gui.bat and a command window will open. Type the following at the command prompt:
mofo.exe flash [Insert name of image file here]
then hit enter. Of course you do not put brackets around the name of the image file. Once the pre-rooted image has been flashed (about 25 minutes), boot into recovery and wipe the cache then boot into system.
It may take a few seconds for the boot animation to start so don’t panic. Once the system has booted, to check that you are rooted, download root checker basic from the Playstore and confirm that you are rooted. Your device will also bypass the subscription check when you turn on WiFi hotspot.
The copy of mofo.exe that you buy is specific to your device. It cannot be used on any other device, including any warranty replacement devices that you may get in the future. But you can use it on your device as much as you want once you purchase it - unless you upgrade to a higher version of Android. If you upgrade to a higher version of Android, once that higher version of Android is supported by MoFo for your device, you can re-download mofo.exe for the higher Android version.
http://forum.xda-developers.com/showpost.php?p=60471334&postcount=432
Mofo will NEVER be updated to support 5.1 as the exploit was closed with the 5.1 bootloader.

Thank you for the guide and for the testing - its a great service to Moto X owners.
Tried going through it this morning but it appears the Mofo site is down... Anyone else having trouble?

HTC-OH_SNAP said:
Tried going through it this morning but it appears the Mofo site is down... Anyone else having trouble?
Click to expand...
Click to collapse
It is best to ask on the MoFo support thread where you are more likely to get maiko1's attention.
http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404

Adding this to the OP
This is from the MoFo support forum - there appears to be some confusion about mofo.exe being device specific. The copy of mofo.exe you buy is specific to your device. It cannot be used on any other device, including any warranty replacement devices that you may get in the future. But you can use it on your device as much as you want once you purchase it.
http://forum.xda-developers.com/showpost.php?p=60471334&postcount=432

JulesJam said:
1. Verifying that your device qualifies for purchasing mofo.exe by using MoVerify;
Click to expand...
Click to collapse
might want to expand the MoVerify process with little baby steps.... the Mofo site and the Mofo forum here are again very sparse on details.
1) download and unzip the MoVerify program
2) connect you phone to computer
3) open cmd window
4) navigate to c:\mx2014 (or wherever you have adb and fastboot stored)
5) type adb devices
6) type adb reboot bootloader
7) navigate to the MoVerify folder
8) go to the folder that represents your computer's OS; let's assume Windows here
9) in the Windows folder, double click on "mofoverify_gui.bat"
10) MoVerify will open a cmd window and return back that your devices was found and give a link that looks like
https://mofo.disekt.org/verify/ [big long alphanumeric string]
11) right click anywhere in the text that is in the MoVerify cmd window and select "Select All" and then hit enter
12) open Notepad or other text editor and past the text
13) cut and paste the https address into your browser
14) follow steps to purchase Mofo
i have purchased but have not gotten farther yet... may have some more suggestions later...

Nice job putting this together. And thanks for all of your testing during the process!

is there any difference in getting into BL mode by pressing phone buttons versus connecting phone to computer and using adb?
i ask b/c there are several places in the directions above where you say "put you phone into BL mode, then connect it to your computer"
could those equally say, "connect your phone to your computer, open a cmd window, navigate to c:/mx2014, and type adb reboot bootloader to get into BL mode"
i find it is easier to go the adb route to get into BL mode, as pressing the buttons is more of a skill. if these two merhids are equivalent for this mofo process, maybe both options should be stated in the step by step.
is there any time when the button method MUST be used?
---------- Post added at 06:40 AM ---------- Previous post was at 06:33 AM ----------
one more question more out of curiousity than need to know... why does flashing back to the stock system take sequential flashing 9 "sparse chunks" (as in your step 9), whereas the mofo flash of the modified sys img is a single step?

[email protected] said:
is there any difference in getting into BL mode by pressing phone buttons versus connecting phone to computer and using adb?
Click to expand...
Click to collapse
No.
[email protected] said:
i ask b/c there are several places in the directions above where you say "put you phone into BL mode, then connect it to your computer"
Click to expand...
Click to collapse
I tend to use the buttons so that is why I wrote it up that way.
[email protected] said:
could those equally say, "connect your phone to your computer, open a cmd window, navigate to c:/mx2014, and type adb reboot bootloader to get into BL mode"
Click to expand...
Click to collapse
Yes, that would work.
[email protected] said:
i find it is easier to go the adb route to get into BL mode, as pressing the buttons is more of a skill.
Click to expand...
Click to collapse
True but if you soft brick your phone, the buttons are the only way to get into bootloader mode so best to be familiar with this way.
Did you try holding vol dwn/up and pwr simultaneously for 4 seconds and then releasing? After the lollipop update I swear that works the best for me. Let me know if that works more reliably for you - it does for me.
[email protected] said:
is there any time when the button method MUST be used?
Click to expand...
Click to collapse
If you get into a bootloop or your screen goes black and the phone is unresponsive.
[email protected] said:
one more question more out of curiousity than need to know... why does flashing back to the stock system take sequential flashing 9 "sparse chunks" (as in your step 9), whereas the mofo flash of the modified sys img is a single step?
Click to expand...
Click to collapse
Standard fastboot has a size limitation on how large of a file it can flash. So system images above that size limitation have to be broken down into smaller chunks. The version of the 5.0 Official firmware that is available to us is the one on Root Junky's site and that one is broken down into chunks.
Motorola made a modified version of fastboot, often referred to as mfastboot, that can flash larger files. However, I cannot find a version of mfastboot that can flash the 5.0 system.img (fxz) that we have available to us. If anyone has a version of mfastboot that can flash the 5.0 fxz system.img, then you could flash it. RSD Lite may be able to flash it, idk I didn't try it.
As for mofo.exe - mofo.exe has a way to avoid the size limitations of standard fastboot. Idk why standard fastboot has a size limitation in the first place. But it does and so large files have to be broken down into chunks when you use standard fastboot to flash. Mofo.exe doesn't have that same size limitation.

JulesJam said:
Once you download one of them, unzip it and move the image to wherever you have mofo.exe stored on your computer. Put your device into BL mode and connect it to your PC. Then navigate to where mofo.exe is stored on your computer, click on mofo_gui.bat and a command window will open. Type the following at the command prompt:
mofoe.exe flash XT1096_5.0_22.21.11_rooted.img
then hit enter.
Click to expand...
Click to collapse
ok. so i attempted this today
1) powered off phone
2) booted in BL mode using power and volume buttons (yes it does work very well, esp after taking the phone OUT of the case so buttons are more fully accessible) - phone screen says "AP Fastboot Flash Mode (S)" at very top
3) plugged phone into computer
4) double clicked the mofo_gui.bat to open cmd window
5) copy and pasted your text exactly
6) after hitting enter, i got the following error
======================================
'mofoe.exe' is not recognized as an internal or external command,
operable program or batch file.
======================================
methinks you have a typo in your mofo command... extra "e" that should not be there??
taking out the "e" worked and it flashed
it then said
=====================
Flashing 'XT1096_5.0_22.21.11_rooted.img' to device. Do not interrupt.
Progress: 100%
Complete. Press power to start.
=====================
i pushed the power button. it passed though a screen showing the battery level at 97%, but it has not fully booted up... black screen for like ?5 minutes!
if i hit the power button again, it still showed the battery level screen
so i pressed and held BOTH the power and volume buttons, and it booted!
when i power down, it goes to the batter level screen. and i can't seem to get into BL mode using the power and volume buttons
however, i can get to BL, then Recovery using adb, and was able to wipe cache partition
i installed and ran Root Checker Basic ... make sure you click "Grant" when it asks for permission while checking root access, or it will return a "no root access" message.
i now have wifi tethering! yahoo!
unfortuantely, the wifi hotspot toggle widgets i have tried from the Play Store seem to be able to turn hotspot on from the homescreen... i tried like the first two or three that came up when i searched for "wifi hotspot toggle"... anyone have one that works??
i am running Nova Launcher... could that be the issue with the widget not working?
otherwise, i have to go into Settings to turn it on/off... which is better than NOT having hotspot at all!

[email protected] said:
methinks you have a typo in your mofo command... extra "e" that should not be there??
Click to expand...
Click to collapse
Oops! Thanks for catching that - I will edit!

[email protected] said:
i pushed the power button. it passed though a screen showing the battery level at 97%, but it has not fully booted up... black screen for like ?5 minutes!
Click to expand...
Click to collapse
Disconnect it from your PC and then press the power button to turn it on.

[email protected] said:
when i power down, it goes to the batter level screen.
Click to expand...
Click to collapse
That is b/c it is connected to your computer. The same thing will happen if you have it plugged into the wall.

[email protected] said:
i now have wifi tethering! yahoo!
Click to expand...
Click to collapse
Yay!!!! I am at over 50GB this month from all of the downloading of images I did to test them, lol! I have never used that much before.

[email protected] said:
unfortuantely, the wifi hotspot toggle widgets i have tried from the Play Store seem to be able to turn hotspot on from the homescreen... i tried like the first two or three that came up when i searched for "wifi hotspot toggle"... anyone have one that works??
Click to expand...
Click to collapse
Go to your app drawer - there is a Mobile Hotspot icon there. Just press and hold it and drag it to your homescreen.

JulesJam said:
Go to your app drawer - there is a Mobile Hotspot icon there. Just press and hold it and drag it to your homescreen.
Click to expand...
Click to collapse
tried that... that does take you into Settings so you can turn on the hotspot.
i was hoping to get an app or widget that would turn the hotspot on/off from the home screen with one click, w/o having to do multiple clicks.

[email protected] said:
i was hoping to get an app or widget that would turn the hotspot on/off from the home screen with one click, w/o having to do multiple clicks.
Click to expand...
Click to collapse
you want a hotspot toggle then, but idk of any off hand.

JulesJam said:
Disconnect it from your PC and then press the power button to turn it on.
Click to expand...
Click to collapse
might want to just add the words "disconnect the phone fromthe usb cable" somehwere in the OP directions, you know, just for all those noobs out there that might get panicked

JulesJam said:
Disconnect it from your PC and then press the power button to turn it on.
Click to expand...
Click to collapse
After mofo runs and says complete, it says to hit the power button to restart. What you really want to do is hit the volume up button to activate the highlighted "normal bootup" option in the bootloader menu. This avoids all the weirdness if you're connected to power and using the power button.
---------- Post added at 10:24 AM ---------- Previous post was at 10:21 AM ----------
​
JulesJam said:
Go to your app drawer - there is a Mobile Hotspot icon there. Just press and hold it and drag it to your homescreen.
Click to expand...
Click to collapse
The image with busybox in it also enables the hotspot QS tile which works great to enable/disable the hotspot. If WiFi is on, it turns off the WiFI, then turns on the hotspot. If the WiFi was on, it remembers to re-enable it when turning the hotspot off.

mikeoswego said:
After mofo runs and says complete, it says to hit the power button to restart. What you really want to do is hit the volume up button to activate the highlighted "normal bootup" option in the bootloader menu. This avoids all the weirdness if you're connected to power and using the power button.
Click to expand...
Click to collapse
thanks! I suggest booting into recovery and wiping cache before you boot back into Android.
mikeoswego said:
The image with busybox in it also enables the hotspot QS tile which works great to enable/disable the hotspot. If WiFi is on, it turns off the WiFI, then turns on the hotspot. If the WiFi was on, it remembers to re-enable it when turning the hotspot off.
Click to expand...
Click to collapse
yeah I noticed that last night, it is great!

[email protected] said:
tried that... that does take you into Settings so you can turn on the hotspot.
i was hoping to get an app or widget that would turn the hotspot on/off from the home screen with one click, w/o having to do multiple clicks.
Click to expand...
Click to collapse
There is a Hotspot toggle in quick settings. From your lock screen, just swipe down from the top of the screen to see it. From your home screen, swipe down with 2 fingers.

(help) yotaphone 2 brick after update

Last week, my yotaphone 2 informed that there is a system update from yotaphone. I downloaded and updated but then my phone cannot work. It show only black start screen with word "Android" until battery empty.
I tried to android recovery mode (hold power and volume up),
it show that the error is "e:cannot load volume /misc!".
And I do not know how to solve that problem.
Please help me!

leviet4 said:
Last week, my yotaphone 2 informed that there is a system update from yotaphone. I downloaded and updated but then my phone cannot work. It show only black start screen with word "Android" until battery empty.
I tried to android recovery mode (hold power and volume up),
it show that the error is "e:cannot load volume /misc!".
And I do not know how to solve that problem.
Please help me!
Click to expand...
Click to collapse
You can probably recover.
To reflash a full firmware image you could try the relatively user-friendly yotaflasher application and ROM images from here. I haven't used this myself, but it's software by Yota, so should be safe. You can ask it not to touch /data, to preserve apps, settings etc.
A less user friendly way to reflash a full firmware image:
- Download a full firmware image (EU 1.60 flashable version here, let me know if you require a different one)
- With the phone off, press vol down + power until you see "Downloading ...."
- If you can't turn the phone off normally, keep vol down + power for at least 15 seconds till phone reboots, keep holding till you end up with "Downloading ...."
- connect to a PC with adb+fastboot with a USB cable
- You can now boot TWRP image (fastboot boot recovery_twrp_yd201_alpha2.img , see here.
- if you have important files on your phone, you can back them up now by using adb shell/adb pull (e.g. adb pull /sdcard/Pictures/yeti_sighting.jpg)
- In TWRP go to advanced -> sideload and confirm
- now you can sideload a ROM image from the PC with adb sideload <image>.zip, it should show progress while it's uploading the firmware. If it errors, you probably haven't confirmed initiating sideload in previous step.
- wipe cache&dalvik and reboot

thank you, the first way worked and my phone runs normally now.
thank you

Help please
SteadyQuad said:
You can probably recover.
To reflash a full firmware image you could try the relatively user-friendly yotaflasher application and ROM images from here. I haven't used this myself, but it's software by Yota, so should be safe. You can ask it not to touch /data, to preserve apps, settings etc.
A less user friendly way to reflash a full firmware image:
- Download a full firmware image (EU 1.60 flashable version here, let me know if you require a different one)
- With the phone off, press vol down + power until you see "Downloading ...."
- If you can't turn the phone off normally, keep vol down + power for at least 15 seconds till phone reboots, keep holding till you end up with "Downloading ...."
- connect to a PC with adb+fastboot with a USB cable
- You can now boot TWRP image (fastboot boot recovery_twrp_yd201_alpha2.img , see here.
- if you have important files on your phone, you can back them up now by using adb shell/adb pull (e.g. adb pull /sdcard/Pictures/yeti_sighting.jpg)
- In TWRP go to advanced -> sideload and confirm
- now you can sideload a ROM image from the PC with adb sideload <image>.zip, it should show progress while it's uploading the firmware. If it errors, you probably haven't confirmed initiating sideload in previous step.
- wipe cache&dalvik and reboot
Click to expand...
Click to collapse
I have yotaphone model YD206, but I am in the USA and would like to root and load the best rom I can for my device, it doesn't even have google apps on it. Thanks for any and all help

Kevinreid1 said:
I have yotaphone model YD206, but I am in the USA and would like to root and load the best rom I can for my device, it doesn't even have google apps on it. Thanks for any and all help
Click to expand...
Click to collapse
Root the phone using methods written on this forum > download build 1.60 flammable zip > flash that.
If all you want is Google apps then root the phone then download and flash a gapps package. The full Yota build zip is recommended though.

Can't download yotaflasher application from the link... does anybody have the exe file?
SteadyQuad said:
You can probably recover.
To reflash a full firmware image you could try the relatively user-friendly yotaflasher application and ROM images from here. I haven't used this myself, but it's software by Yota, so should be safe. You can ask it not to touch /data, to preserve apps, settings etc.
A less user friendly way to reflash a full firmware image:
- Download a full firmware image (EU 1.60 flashable version here, let me know if you require a different one)
- With the phone off, press vol down + power until you see "Downloading ...."
- If you can't turn the phone off normally, keep vol down + power for at least 15 seconds till phone reboots, keep holding till you end up with "Downloading ...."
- connect to a PC with adb+fastboot with a USB cable
- You can now boot TWRP image (fastboot boot recovery_twrp_yd201_alpha2.img , see here.
- if you have important files on your phone, you can back them up now by using adb shell/adb pull (e.g. adb pull /sdcard/Pictures/yeti_sighting.jpg)
- In TWRP go to advanced -> sideload and confirm
- now you can sideload a ROM image from the PC with adb sideload <image>.zip, it should show progress while it's uploading the firmware. If it errors, you probably haven't confirmed initiating sideload in previous step.
- wipe cache&dalvik and reboot
Click to expand...
Click to collapse

glax87 said:
Can't download yotaflasher application from the link... does anybody have the exe file?
Click to expand...
Click to collapse
Just click on the YotaPhoneFlasher folder then click the file (yotaphone2_flasher.exe), and save to your harddisk.
Or you can try this link straight to the yotaphone2_flasher.exe file.

https://drive.google.com/file/d/0B0KC5E0zkBYmcHAzMEFKaHRvZ3M/view?usp=sharing

HOW
leviet4 said:
thank you, the first way worked and my phone runs normally now.
thank you
Click to expand...
Click to collapse
Dude I've just bought my phone, and it has the same problem. But I'm a complete noob, how did you fix it? Please, i've just bought it.

On RU build 134 when I tried to swap users my user with Defaut user, the phone blocked, the display is on (time is the same when first happend - just a freeze image) but I can't do nothing on phone. Is a way to reset? because on a normal way I would remove battery but yota dont have this option.

queser.info said:
On RU build 134 when I tried to swap users my user with Defaut user, the phone blocked, the display is on (time is the same when first happend - just a freeze image) but I can't do nothing on phone. Is a way to reset? because on a normal way I would remove battery but yota dont have this option.
Click to expand...
Click to collapse
The analogue method of pulling out the battery is pressing the POWER button for at least 10 seconds. The phone will reboot.

Thanks, I pushed vol down + Power and the phone restarted normaly.
PS: If you know where to get a book from Алекса́ндр Солжени́цын - Aleksandr Solzhenitsyn to read on yota display, send me.

SteadyQuad said:
You can probably recover.
To reflash a full firmware image you could try the relatively user-friendly yotaflasher application and ROM images from here. I haven't used this myself, but it's software by Yota, so should be safe. You can ask it not to touch /data, to preserve apps, settings etc.
A less user friendly way to reflash a full firmware image:
- Download a full firmware image (EU 1.60 flashable version here, let me know if you require a different one)
- With the phone off, press vol down + power until you see "Downloading ...."
- If you can't turn the phone off normally, keep vol down + power for at least 15 seconds till phone reboots, keep holding till you end up with "Downloading ...."
- connect to a PC with adb+fastboot with a USB cable
- You can now boot TWRP image (fastboot boot recovery_twrp_yd201_alpha2.img , see here.
- if you have important files on your phone, you can back them up now by using adb shell/adb pull (e.g. adb pull /sdcard/Pictures/yeti_sighting.jpg)
- In TWRP go to advanced -> sideload and confirm
- now you can sideload a ROM image from the PC with adb sideload <image>.zip, it should show progress while it's uploading the firmware. If it errors, you probably haven't confirmed initiating sideload in previous step.
- wipe cache&dalvik and reboot
Click to expand...
Click to collapse
Sir, i can't even get into recovery mode, i get this problem like it suddenly happen and my battery was 38%.. i was on facebook and it hang and then reboot and then stuck at "POWERED BY ANDROID".
I try to get into recovery mode by pressing volume up + power button, it restart again to "POWERED BY ANDROID"
When i pressing volume down + power button, it show downloding... , and i try to flash it using yotaflasher with HK Firmware 5.0.
When it is done, the phone reboot.
And it still stuck at "POWERED BY ANDROID"
What is the real problem ?

Please help!!!
While trying to solve the network issue on my Yotaphone 2 I managed to brick my phone. He is dead! But since it is a Snapdragon inside it can be fixed.
I need a help from someone who has rooted his Yotaphone2!
I need files from Yotaphone2 software: rawprogram0.xml and patch0.xml
Please!!!

hlmboy said:
Sir, i can't even get into recovery mode, i get this problem like it suddenly happen and my battery was 38%.. i was on facebook and it hang and then reboot and then stuck at "POWERED BY ANDROID".
I try to get into recovery mode by pressing volume up + power button, it restart again to "POWERED BY ANDROID"
When i pressing volume down + power button, it show downloading... , and i try to flash it using yotaflasher with HK Firmware 5.0.
When it is done, the phone reboot.
And it still stuck at "POWERED BY ANDROID"
What is the real problem ?
Click to expand...
Click to collapse
You need to keep pressing the power up button after the showing of "POWERED BY ANDROID", the power does not need to be pressed after then.
If you can still not reach recovery, you probably have a broken recovery (maybe wrong version) and something else is messed up.
When you flash recovery, you need to instantly go into recovery mode by pressing +/up on calling the according command
(fastboot reboot).
It does not look like you changed file system related things, did you change anything on your system/with root permissions?
Are you sure the installation process went without failure etc?
Getting out the cause (kernel logs etc) would be a bit hard without getting into recovery mode[and maybe also nonworking kernel], like stated out here
https://android.stackexchange.com/q...n-i-recover-files-from-a-phone-that-wont-boot

Android P Update stuck on BOOT LOOP

[NVidia Shield 2017 model]
After yesterday's update restart, to Android P, my unit stuck on bootloop (10+hrs).
I'm now unable to get past it, or get into bootloader (ie A+B after Plug-In & Control Buzz).
At this point, I'd like to do a Factory Reset if possible.
I have access to a computer if it'll help.
Thanks
UPDATE (10/3/19)
I worked through this Guide for the SHIELD Pro a number of times.
Couldn't get past the broken robot screen. Going to try updating my Windows Driver and try again later. Will update.
(sorry. I haven't hit my 10 post min in order to post links)
UPDATE (10/4/19)
I've got a somewhat Parallel Thread going here discussing my Troubleshooting Steps:
https://www.nvidia.com/en-us/geforce/forums/shield-tv/9/321317/bootlooped-since-android-p-adb-fastboot-questio/

Same sort of issue. I read over at geforce forum, somebody installed OK, then stuck. Somebody asked if they had SD card in, and to try to remove and restart. Sounds dodgey, as the card is formatted as part of the system configuration now.

Stevio2 said:
Same sort of issue. I read over at geforce forum, somebody installed OK, then stuck. Somebody asked if they had SD card in, and to try to remove and restart. Sounds dodgey, as the card is formatted as part of the system configuration now.
Click to expand...
Click to collapse
I had a cluster of hd's connected to mine at the time ... Could be related?

I tried the suggestion, and removed my USB hub as well, and it didn't work. When I do get back in I'll have to see if doing that has trashed my system or app configuration.
However, I did discover in a thread below mention of a thread to do with the boot loader, and some instructions on his to get into it.
https://forum.xda-developers.com/showpost.php?p=80234203&postcount=10
(BTW: I am using my TV internal smart TV functions and players instead at the moment , and the picture with my pushed profile looks way better than on the shield. Yet another way they let us down. This might be the last shield when it dies, and I stopped recommending it, and may start recommending not to buy. Just one update promoted issue after another going on for an extreme long time, and just poor interface and system app design, as well as disabling my track pad and no Linux support. The system is nowhere near what it could be.)

How far are you guys getting when booting up?

Mine's the multicolored android animation before it forms the word.

Still Fastboot then broken Robot Screen for me ...

ezekieljesus said:
Still Fastboot then broken Robot Screen for me ...
Click to expand...
Click to collapse
So you are getting into the bootloader?
Are you pressing recovery by any chance when there?
edit: found this
Factory Reset SHIELD TV When You Are Unable to Access Android Settings
SHIELD TV 2017
1. Restart your SHIELD TV in Fast Boot mode. Instructions can be found here
2. Use the X and Y buttons on the controller to move to "Boot recovery kernel".
3. Press the A button to select "Boot Recovery Kernel".
4. You may see the dead Android robot on screen. This is expected behavior. If so, press B button on the controller.
5. You will see Android Recovery Menu.
6. Use the X and Y buttons on the controller to move to "wipe data/factory reset".
7. Press the A button to select "wipe data/factory reset".
8. After process select "reboot system now".
8. SHIELD will boot to home screen.
SHIELD Pro or SHIELD TV (2015)
1. Turn off your SHIELD.
2. Unplug the power cable from your SHIELD.
3. Connect your SHIELD to your PC/Mac/Linux computer via USB using SHIELD's micro USB port.
4. Plug the power cable back into your SHIELD.
5. Wait 2 seconds, and then hold the NVIDIA power button on SHIELD for 5-6s until you see the fastboot menu on the display.
6. Tap on NVIDIA button to move on Menu to "Boot recovery kernel".
7. Hold NVIDIA button to for 2-4s to select "Boot Recovery Kernel".
8. You may see the dead Android robot on screen. This is expected behavior.
9. Hold NVIDIA button to for 2-4s to process to next menu. If you don't see the Recovery menu, try this step a few times.
10. You will see Android Recovery Menu.
11. Tap on NVIDIA button to move to "wipe data/factory reset".
12. Hold NVIDIA button to for 4-6s to select "wipe data/factory reset".
13. After process select "reboot system now".
14. SHIELD will boot to home screen.

mLgz0rn said:
So you are getting into the bootloader?
edit: found this
Factory Reset SHIELD TV When You Are Unable to Access Android Settings
Instructions can be found here
Click to expand...
Click to collapse
Thanks, that's one of the links I wasn't able to post initially.
I've since moved the question, including current pursuits, to the page linked under my last update above.
NVidia has kindly resolved the issue with me since.
Good luck everyone, and thanks for the assists.
-z