Related
I don't find instruction for sideload ota on the Ouya forum so here what i found.
Enter Recovery Mode
1. Connect a usb keyboard
2. use command "adb reboot recovery" or
Boot the console and hit "Alt + PrntScrn + i" multiple time until you see the Ouya logo with red (!)
3. Hit home on the keyboard and the recovery menu will appear
Side load OTA
1. Select "apply update from ADB" with the arrow key then hit enter
2. use command "adb sideload RC-OUYA-version number_ota.zip
Look this thread to install ADB driver.
And this thread for downloading OTA.
OTA site link. https://ouyafw.skumler.net
The PrntScrn don't have the same name from one keyboard to another most of time is in the top row next to the F1-F12 key.
i don't know why no one has commented here. i think this is great.
obviously you didn't come up with any of this, but you put it all together in one place, so thats nice.
thanks dog. keep up the good work.
You're the man!
Thank you so much for this!
This will save me for waiting those update times (since the connection in my house sucks)
joelzombie said:
Thank you so much for this!
This will save me for waiting those update times (since the connection in my house sucks)
Click to expand...
Click to collapse
The Ouya connection in general is unstable, the rom still need many update.
Hi folks.
I'm new to this device, but not to Android, and I have one question.
I bought this tab for my wife and she don't want me to root it I wonder if I can update to 4.4.2 without root ? If yes, how?
Thanks
You can update by OTA which has rolled out for n10 and wait for sometime you will have notification about it or check it manually....
Piyush Pastor said:
You can update by OTA which has rolled out for n10 and wait for sometime you will have notification about it or check it manually....
Click to expand...
Click to collapse
Do I need root for the manual way ?
The Wugfresh Nexus Root Toolkit (http://www.wugfresh.com/nrt/) will let you flash a stock image and root and/or unroot your device. It's always worked for me, with the major hassle being getting the correct drivers loaded and working on the PC.
tjupille said:
The Wugfresh Nexus Root Toolkit (http://www.wugfresh.com/nrt/) will let you flash a stock image and root and/or unroot your device. It's always worked for me, with the major hassle being getting the correct drivers loaded and working on the PC.
Click to expand...
Click to collapse
Don't you have to unlock it first before you can do anything which isn't OTA? So unlock, then flash stock+unroot, then lock.. You can do each of those 3 steps with WUGS NRT. Not sure about if unlock needed before stock+unroot.
Then it will be 100% vanilla 4.4.2 and receive OTAs in the future.
Don't you have to unlock it first before you can do anything which isn't OTA?
Click to expand...
Click to collapse
Good point. I unlocked and rooted as soon as I got the tablet in the first place. Actually, Wugfresh has done a good job of "bulletproofing" the scripts and the informational messages are, in fact, informative so I suspect that it'll tell you if you need to unlock.
Hi,
You can Google for Nexus 10 OTA (the version you want) and then installing it via the stock recovery, just plug your tablet to your computer, copy the OTA zip to your adb folder and do the following steps:
1 - Make sure that USB Debugging is on (if it's not search how to do it)
2 - Open a cmd in your adb + OTA zip folder and type the following:
Code:
adb reboot recovery
3 - Wait for your tablet to boot and then you'll probably see an android with a red exclamation mark, press volume+, hold it and press power (if it didn't do the trick try the opposite, hold power and press volume+).
4 - You'll see a menu now, using volume - go to flash zip via sideload and press power button.
5 - Now simply type on your cmd in the folder
Code:
adb sideload *inserttheOTAzipfullnamehere*
And you're done. If the tablet didn't reboot, do it yourself by the same way you selected sideload, select reboot.
Hope this helps,
~Lord
"Time is too short to cry, long enough to try." - March of Time (Helloween)
Sent from my KitKat Nexus 10
XxLordxX said:
Hi,
You can Google for Nexus 10 OTA (the version you want) and then installing it via the stock recovery, just plug your tablet to your computer, copy the OTA zip to your adb folder and do the following steps:
1 - Make sure that USB Debugging is on (if it's not search how to do it)
2 - Open a cmd in your adb + OTA zip folder and type the following:
Code:
adb reboot recovery
3 - Wait for your tablet to boot and then you'll probably see an android with a red exclamation mark, press volume+, hold it and press power (if it didn't do the trick try the opposite, hold power and press volume+).
4 - You'll see a menu now, using volume - go to flash zip via sideload and press power button.
5 - Now simply type on your cmd in the folder
Code:
adb sideload *inserttheOTAzipfullnamehere*
And you're done. If the tablet didn't reboot, do it yourself by the same way you selected sideload, select reboot.
Hope this helps,
~Lord
"Time is too short to cry, long enough to try." - March of Time (Helloween)
Sent from my KitKat Nexus 10
Click to expand...
Click to collapse
That's what I wanted to know. Thank you all !!
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.
Ever since i flashed my Nokia 6 with the Oreo Beta update i no longer have access to the recovery menu.
I want to update to Oreo Final, but how can i do that now?
My Nokia is a TA-1000 model, but recognized as TA-1025.
IndigoHD said:
Ever since i flashed my Nokia 6 with the Oreo Beta update i no longer have access to the recovery menu.
I want to update to Oreo Final, but how can i do that now?
My Nokia is a TA-1000 model, but recognized as TA-1025.
Click to expand...
Click to collapse
There is 2 way to access recovery menu:
Normal Way:
Step 1) Turn the power off.
Step 2) Hold and Press Volume up + Power Button for about 10 second and release
Step 3) If you see Nokia logo it means failed repeat step 2
Step 4) If you see no command Android logo it means success
Step 5) In no command Android logo Press Volume up + Power Button + Home Button(Center One)
Step 6) You will see recovery menu
Developer Way:
Step 1) In the System->About Phone Tap Build Number Multiple Time to enable developer mode
Step 2) In Developer options enable usb debugging
Step 3) Connect your phone to computer using usb and Allow the access.
Step 4) Download sdk tools from developer.android.com
Step 5) Open adb by cmd and type "adb devices" to detect your phone
Step 6) Then type "adb reboot recovery" to force your phone to reboot and open recovery
Step 7) You should get no command Android logo
Step 8) In no command Android logo Press Volume up + Power Button + Home Button(Center One)
Step 9) You will see recovery menu
IndigoHD said:
Ever since i flashed my Nokia 6 with the Oreo Beta update i no longer have access to the recovery menu.
I want to update to Oreo Final, but how can i do that now?
My Nokia is a TA-1000 model, but recognized as TA-1025.
Click to expand...
Click to collapse
Reflash the mena firmware and wait if you receive otas. If not, you could flash the zip for final oreo. However, I think there's not the link for ta-1025 yet.
Gonz19 said:
Reflash the mena firmware and wait if you receive otas. If not, you could flash the zip for final oreo. However, I think there's not the link for ta-1025 yet.
Click to expand...
Click to collapse
Every zip work on TA-1025/and MENA firmware
Because, internally mena firmware is also TA-1025 and all OTA zips are made and targeted to TA-1025 varient only
So you can even flash OREO FINAL VERSION ALSO
Hit thanks button if you find this useful
Happy flashing
Tried flashing Oreo Final after finding the recovery, now my phone is broken.
Flashing didnt finish and it would no longer boot.
Tried restoring to an older firmware with OST LA, now it just flickers all the time.
Sometimes i see the recovery screen, but then it flickers off again.
Cant do anything anymore. Its broken.
IndigoHD said:
Tried flashing Oreo Final after finding the recovery, now my phone is broken.
Flashing didnt finish and it would no longer boot.
Tried restoring to an older firmware with OST LA, now it just flickers all the time.
Sometimes i see the recovery screen, but then it flickers off again.
Cant do anything anymore. Its broken.
Click to expand...
Click to collapse
Hey dont be sad , we are here to assist you
Try installing OTA manually
when u see the recovery menu, move to the OTA folder and install
Install till January, and then try the OTA of OFFICIAL OREO
this might work, you need to have patience and quick to install the OTA
if I would be there with you, I would love to help you
sltushar said:
Hey dont be sad , we are here to assist you
Try installing OTA manually
when u see the recovery menu, move to the OTA folder and install
Install till January, and then try the OTA of OFFICIAL OREO
this might work, you need to have patience and quick to install the OTA
if I would be there with you, I would love to help you
Click to expand...
Click to collapse
Tried it. Phone just keeps flickering. No longer reacts to anything i do and i cant use the recovery at all. Most of the time the screen is black then it suddenly flashes the recovery for a second.
Cant input any button commands and cant chose anything there.
IndigoHD said:
Tried it. Phone just keeps flickering. No longer reacts to anything i do and i cant use the recovery at all. Most of the time the screen is black then it suddenly flashes the recovery for a second.
Cant input any button commands and cant chose anything there.
Click to expand...
Click to collapse
Can you do one thing,
Its okay it flickers
Try this
When you think you are in recovery mode but still cant see
Then
Just press volume down 4 time(not so quickly, you should know that you pressed it 4 times)
Then click power button
Click one time volume down button
Then again power button
After 20 second press power button
Wait for to reboot the device, if it doesn't
Try force rebooting
Hope this work:fingers-crossed:
sltushar said:
Can you do one thing,
Its okay it flickers
Try this
When you think you are in recovery mode but still cant see
Then
Just press volume down 4 time(not so quickly, you should know that you pressed it 4 times)
Then click power button
Click one time volume down button
Then again power button
After 20 second press power button
Wait for to reboot the device, if it doesn't
Try force rebooting
Hope this work:fingers-crossed:
Click to expand...
Click to collapse
Doesnt work. Forcing a reboot doesnt work either.
Soft reboot works, but i cant get into download mode this way.
IndigoHD said:
Doesnt work. Forcing a reboot doesnt work either.
Soft reboot works, but i cant get into download mode this way.
Click to expand...
Click to collapse
These steps are for hard reset not for download mode
Well i have one solution for you, but its lil expensive
I have firmware, which can be installed through infinity CM2 dongle
This dongle can upgrade, downgrade and do much things on Nokia devices
It costs 70 US dollar
This can only work for you, cause Nokia care will replace your motherboard, they wont repair it, because even they don't know how to deal with it
So if you can buy this dongle then you can flash it else wait for OFFICIAL OREO firmware to be come soon
sltushar said:
These steps are for hard reset not for download mode
Well i have one solution for you, but its lil expensive
I have firmware, which can be installed through infinity CM2 dongle
This dongle can upgrade, downgrade and do much things on Nokia devices
It costs 70 US dollar
This can only work for you, cause Nokia care will replace your motherboard, they wont repair it, because even they don't know how to deal with it
So if you can buy this dongle then you can flash it else wait for OFFICIAL OREO firmware to be come soon
Click to expand...
Click to collapse
Thanks everyone for all your help and to you sltushar, especially!
I guess i will let it discharge for now and hope i can enter into download mode after that.
For now i will use my old phone.
IndigoHD said:
Thanks everyone for all your help and to you sltushar, especially!
I guess i will let it discharge for now and hope i can enter into download mode after that.
For now i will use my old phone.
Click to expand...
Click to collapse
Till don't be sad, we are here, finding solutions for you and mate like you
IndigoHD said:
Thanks everyone for all your help and to you sltushar, especially!
I guess i will let it discharge for now and hope i can enter into download mode after that.
For now i will use my old phone.
Click to expand...
Click to collapse
When phone is powered off, connect charger and keep pressing volume down +power button. It should take you straight to download mode.
I had exact problem and by coincidence today
Can u see the no cammand page of recovery.
If yes then try pressing both volume up and Power button together. Try again and again it must take you to recovery... If you land in recovery only for once you just have to select the reboot to bootloader option, so the download mode will open then.. then use OST
Im also having the same problem, after oreo stable update in my nokia 6 im not able get into recovery mode. Please someone help!
I'm discovered, that Windows 10 and USB 3.0/3.1 may cause problems with flashing using OST. If you can, use USB 2.0 ports and older Windows operating system (in my case - Windows 8.1). I also bricked my phone and my new notebook cannot communicate with my phone, after use OST using my older PC - it communicate without any problem
leszczu8023 said:
Im discovered, that Windows 10 and USB 3.0/3.1 may cause problems with flashing using OST. If you can, use USB 2.0 ports and older Windows operating system (in my case - Windows 8.1). I also bricked my phone and my new notebook cannot communicate with my phone, after use my older PC - it works without any problem
Click to expand...
Click to collapse
No need of older windows i have done it (today) on windows 10 (64bbit) with USB 3.0 port today.. and now i am typing this from my recoverd Nokia 6.
All you need is that your .NETFramework version 3.5 is enabled in windows and you install OST tool properly which includes all drivers.
Bdw my windows 10 is on Fall Creator update.
minhas729 said:
No need of older windows i have done it (today) on windows 10 (64bbit) with USB 3.0 port today.. and now i am typing this from my recoverd Nokia 6.
All you need is that your .NETFramework version 3.5 is enabled in windows and you install OST tool properly which includes all drivers.
Bdw my windows 10 is on Fall Creator update.
Click to expand...
Click to collapse
Idk, but maybe it depends by hardware and software configuration... I also installed OST with all frameworks included in package without any success. Phone starts flashing and... reboots into recovery mode after +/- 10% of flashing progress. But it's my own flash experience
And yep, I also using W10 Fall Creators Update (10.0.16299.192) x64
leszczu8023 said:
Idk, but maybe it depends by hardware and software configuration... I also installed OST with all frameworks included in package without any success. Phone starts flashing and... reboots into recovery mode after +/- 10% of flashing progress. But it's my own flash experience
And yep, I also using W10 Fall Creators Update (10.0.16299.192) x64
Click to expand...
Click to collapse
That reboot thing also occurred with me in first try... All you had to do is press Volume down and power till phone goes back to download mode. And just press next again
leszczu8023 said:
I'm discovered, that Windows 10 and USB 3.0/3.1 may cause problems with flashing using OST. If you can, use USB 2.0 ports and older Windows operating system (in my case - Windows 8.1). I also bricked my phone and my new notebook cannot communicate with my phone, after use OST using my older PC - it communicate without any problem
Click to expand...
Click to collapse
minhas729 said:
No need of older windows i have done it (today) on windows 10 (64bbit) with USB 3.0 port today.. and now i am typing this from my recoverd Nokia 6.
All you need is that your .NETFramework version 3.5 is enabled in windows and you install OST tool properly which includes all drivers.
Bdw my windows 10 is on Fall Creator update.
Click to expand...
Click to collapse
leszczu8023 said:
Idk, but maybe it depends by hardware and software configuration... I also installed OST with all frameworks included in package without any success. Phone starts flashing and... reboots into recovery mode after +/- 10% of flashing progress. But it's my own flash experience
And yep, I also using W10 Fall Creators Update (10.0.16299.192) x64
Click to expand...
Click to collapse
Exactly, @minhas729 even i did all the things from my windows 10 fall creator update and though windows 10 is the best OS to flash phones, it rarely ask for phone drivers or anything, everything is pre-installed and you can just go straight to flashing, automatically system updates downloads all required things automatically.
So no need to go back to the old windows OS to flash it. And also its true on the first go, the OST tool gives error and stuck to flashing splash....
All you need it try once again, second time it flashes successfully
minhas729 said:
That reboot thing also occurred with me in first try... All you had to do is press Volume down and power till phone goes back to download mode. And just press next again
Click to expand...
Click to collapse
Last night i installed oreo stable in my nokia 6 and i wanted to reset and clear cache partition, since i wanted a fresh start. And i tried to go to recovery mode and i was stuck at no command screen and i accidentally did a combination of " press and hold the power button then press the volume up button once". This took my phone to recovery mode from no command screen.
So I hadn't tried to flash a ROM on my "tube" Shield TV 2019 until the Experience 9 ROMs just leaked. I didn't realize it didn't have a USB port. I have been flashing ROMs on Android phones for over a decade, so I'm good there but what about Fastboot access via network TCP/IP or UDP? I was able to ADB to the Shield with "ADB connect [IP address]" but Fastboot doesn't see the unit at the same IP and I've looked on my router's device list and don't see anything. I have the latest 1.4.3 ADB/Fastboot tools.
So no access to flashing using the SD card slot, ethernet, or network?
THANKS!
KeepingItCuttingEdge said:
So I hadn't tried to flash a ROM on my "tube" Shield TV 2019 until the Experience 9 ROMs just leaked. I didn't realize it didn't have a USB port. I have been flashing ROMs on Android phones for over a decade, so I'm good there but what about Fastboot access via network TCP/IP or UDP? I was able to ADB to the Shield with "ADB connect [IP address]" but Fastboot doesn't see the unit at the same IP and I've looked on my router's device list and don't see anything. I have the latest 1.4.3 ADB/Fastboot tools.
So no access to flashing using the SD card slot, ethernet, or network?
THANKS!
Click to expand...
Click to collapse
I'm sorry, this is slightly off topic, but consider it a bump. haha. A quick question. Do you have a link for the experience rom? I would love to look at it, or do you know what OS they are rolling?
Hello,
trying to do the same but fastboot mode is as far as I get as well. Any ideas on how to flash the image on the tube?
@jenneh
Here you go . The OS is Android 11
KeepingItCuttingEdge said:
So I hadn't tried to flash a ROM on my "tube" Shield TV 2019 until the Experience 9 ROMs just leaked. I didn't realize it didn't have a USB port. I have been flashing ROMs on Android phones for over a decade, so I'm good there but what about Fastboot access via network TCP/IP or UDP? I was able to ADB to the Shield with "ADB connect [IP address]" but Fastboot doesn't see the unit at the same IP and I've looked on my router's device list and don't see anything. I have the latest 1.4.3 ADB/Fastboot tools.
So no access to flashing using the SD card slot, ethernet, or network?
THANKS!
Click to expand...
Click to collapse
Well I figured it out. First copy the downloaded image to the external sd card of the tube. Then:
When you reboot to fastboot using wifi ADB, then first unlock the bootloader.
Then choose "Boot recovery kernel" from the menu. The power button is located above the HDMI port on the tube.
When the dead android image appears, press the power button for 3 seconds and then release.
You should see the recovery menu. If you still see the dead android, then repeat the process by holding the power button pressed for 3-4-5-6 seconds. It can be tricky.
Once in the menu, choose the sd card.
Choose the file.
The process will start. and it should complete after a couple of minutes.
You are then done.
I did some extra steps:
I performed a factory reset and cleared cache from the recovery menu, although this happens automatically when you unlock the bootloader.
I then got back to the fastboot menu and locked the bootloader again. Otherwise you get a warning every time you boot the device.
Be ware that locking/unlocking the bootloader, erases the data of the user partition and the device needs to be setup as from a factory reset. This is by design.
Here is a link with all the images.
Cheers
m33ts4k0z said:
Well I figured it out. First copy the downloaded image to the external sd card of the tube. Then:
When you reboot to fastboot using wifi ADB, then first unlock the bootloader.
Then choose "Boot recovery kernel" from the menu. The power button is located above the HDMI port on the tube.
When the dead android image appears, press the power button for 3 seconds and then release.
You should see the recovery menu. If you still see the dead android, then repeat the process by holding the power button pressed for 3-4-5-6 seconds. It can be tricky.
Once in the menu, choose the sd card.
Choose the file.
The process will start. and it should complete after a couple of minutes.
You are then done.
I did some extra steps:
I performed a factory reset and cleared cache from the recovery menu, although this happens automatically when you unlock the bootloader.
I then got back to the fastboot menu and locked the bootloader again. Otherwise you get a warning every time you boot the device.
Be ware that locking/unlocking the bootloader, erases the data of the user partition and the device needs to be setup as from a factory reset. This is by design.
Here is a link with all the images.
Cheers
Click to expand...
Click to collapse
First of all, THANK YOU for this share~ ~! secondly, would you happen to have any idea why my usb ports have stopped working all of a sudden. I swear I didn't step on the shield this time. Lol
m33ts4k0z said:
he menu, choose the sd card.
Choose the file.
The process will start. and it should complete after a couple of minutes.
You are then done.
I did some extra steps:
Click to expand...
Click to collapse
m33ts4k0z said:
Hello,
trying to do the same but fastboot mode is as far as I get as well. Any ideas on how to flash the image on the tube?
@jenneh
Here you go . The OS is Android 11
Click to expand...
Click to collapse
false alarm Sir!!! I plugged my mouse in where the usbc cord usually goes, and i have access back! i was about to go return this sield to bestbuy for the 5th time for another hahaha
I want to go back from Android 11 to Android 9. It is possible to download a ROM for Shield 2019 Non Pro 8GB ATV 8.2.3? THX
There are links to the recovery firmware 8.2.3 but I can't get past the agree button that shows when klicking on the link..
It could be my old laptop.. but here's the link..
Gameworks Download Center
Get the latest Gameworks software for your game development work.
developer.nvidia.com
Sinse the update most of my aps are gone or not usable..
I can not fint the shield on my network.. and there is no installable apk showing up in any file manager.
I wil do my best to get back to android 9.
Tried to go back using the 8.2.3 recovery img.. but no luck.
I get an error saying cant flash over newer firmware.
Ugg... I didn't see this post that you can't downgrade until I tried it myself and also got the error.
Anybody have any possible work around ideas?
The same here:
The method I used is the one below according to nvidia's instructions:
Hardware Method:
- Disconnect power cable
- Connect power cable to SHIELD and hold down the remote locator button
- Release the keys once you see the fastboot menu on the screen (it's
red in color)
- If the standard boot process starts, disconnect the power cable and
repeat
the process
*******************************************************************************
FASTBOOT MENU NAVIGATION
*****
Once in fastboot mode (it's red in color), navigate the menus using the
remote locator button on the device.
Short press to navigate and long press for ~2s to select.
*******************************************************************************
FLASHING THE DEVICE
*****
To flash the recovery image to your SHIELD from fastboot, download the
image package.
- Download the image package. Copy the same downloaded zip file with
name
'nv-recovery-image-shield-atv-2019_.zip' to a uSD card that is FAT32
formatted
(where corresponds to the image version of the update being
installed).
Insert uSD card into the uSD card slot on the device
- in fastboot mode select Factory Data reset (opp in Recovery menu
scegli wipe data/factory reset)
- Enter recovery kernel by selecting the option "Boot recovery kernel"
from fastboot menu
- Once the device boots into recovery kernel, you will see a "No
command" image on the
screen
- Long press the remote locator button for ~2s and release button.
Recovery menu should show up (it's blue and green).
If not, please try to long press the button again
- On the recovery menu, select the option "apply update from SD card"
(navigate using short
press of remote locator button and long press ~4s to select and
release button)
- From the SD card contents, select the image package
- At anytime if the display goes back to the "No command" picture, press
the button for ~2s and release button
to go back to the previous screen
- Once the image is selected, the update process should start
Unfortunately the process interrupts with "newer build ....error status
7". I deleted the first two rows of UPDATE-SCRIPT, repacked in ZIP and
reflashed but in vain!! the error was:"Signature failure"
I also use SIGNAPK to sign the new ZIP, but in vain....
Any help?
Does anybody found solution to force downgrade (2019 nonPRO of course)?
Hello, I have a device that at this moment, after a failed update, ended up blocking..Now I turn it on, I feel that the nvidia heats up, but I don't have a signal on the television or anything, I've tried to do a reset but I haven't been successful because I am unable to enter to the fastboot screen... Does anyone who has gone through the same problem have any tips? Any help would be nice...Thanks
kuki68ster said:
Hello, I have a device that at this moment, after a failed update, ended up blocking..Now I turn it on, I feel that the nvidia heats up, but I don't have a signal on the television or anything, I've tried to do a reset but I haven't been successful because I am unable to enter to the fastboot screen... Does anyone who has gone through the same problem have any tips? Any help would be nice...Thanks
Click to expand...
Click to collapse
This is exactly what's happening to me. For some reason the network stopped working. I tried to see what happens if I factory reset. After the factory reset the device no longer displays anything. It does turn on and I can turn the tv and receiver on and off with the shield remote. I can enter the bootloader though.
Is this a coincidence or did the latest update screw something up?