Related
I used the Nexus 7 toolkit to flash the latest CWM recovery. If I boot into fastboot and choose recovery mode it just hangs on the Google boot animation. I can boot to it from the toolkit though. Anyone else experience this/know what I did wrong?
SpencerRelly said:
I used the Nexus 7 toolkit to flash the latest CWM recovery. If I boot into fastboot and choose recovery mode it just hangs on the Google boot animation. I can boot to it from the toolkit though. Anyone else experience this/know what I did wrong?
Click to expand...
Click to collapse
Its a known issue that is yet to be fixed. You did nothing wrong.
Sent from my Nexus 7 using xda premium
leelaa said:
Its a known issue that is yet to be fixed. You did nothing wrong.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Alright. Thanks for the reply!
SpencerRelly said:
I used the Nexus 7 toolkit to flash the latest CWM recovery. If I boot into fastboot and choose recovery mode it just hangs on the Google boot animation. I can boot to it from the toolkit though. Anyone else experience this/know what I did wrong?
Click to expand...
Click to collapse
You need to have a USB cable connected to the Nexus 7, and if you're in fastboot it'll load into recovery. Known bug
Wrong section dude but as said before known bug
Sent from my Nexus 7 using Tapatalk 2
flash twrp recovery, its not buggy and is more functional.
SpencerRelly said:
I used the Nexus 7 toolkit to flash the latest CWM recovery. If I boot into fastboot and choose recovery mode it just hangs on the Google boot animation. I can boot to it from the toolkit though. Anyone else experience this/know what I did wrong?
Click to expand...
Click to collapse
It's a problem with the boot loader. For now you will need to be plugged into a computer to go into recovery. It doesn't even have to have drivers or anything installed.
Plug in tablet into computer
Use power and volume buttons to get into recovery
And no, this problem won't be fixed by flashing twrp because it deals with the boot loader.
Just boot to recovery from Rom manager or similar.
I can confirm that quick boot does work to get you into recovery.
-----
Sent from my Nexus 7
Moved to QA...The Development section is for..........development only, not questions...
Same problem
I've read in other threads that deleting the stock recovery, or modifying it's filename, will fix this problem. Does anyone know if this is true? I can boot recovery through Rom manager or through the power menu. The only worry I have is if I ever get stuck in a bootloop, or brick. It is good to know about the usb trick to load CWM, thanks for that.
Flash TWRP, and use an app like quick boot to reboot into recovery.
Sent from my Nexus 7 using xda app-developers app
I use TWRP and boot to recovery through the roms power menu. I've been very happy with TWRP though, I use a recovery because of stability and performance. I could really care less if it's touch or if it has themes, so when I recommend TWRP it's because I've been using it so long on my transformer prime and nexus 7 and it has done nothing but work exactly like it should.
veeman said:
It's a problem with the boot loader. For now you will need to be plugged into a computer to go into recovery. It doesn't even have to have drivers or anything installed.
Plug in tablet into computer
Use power and volume buttons to get into recovery
And no, this problem won't be fixed by flashing twrp because it deals with the boot loader.
Click to expand...
Click to collapse
Weird because today I tried to get into CWR for the first time since I rooted, and it wouldn't work. I got the red ! triangle [sticking out of the green robot].
I plugged it into my laptop.. [and btw I was holding vol UP/DOWN, press power, in the bootloader then selecting 'Recovery' then <Power>] and this time it showed the "Google" and the unlocked lock.. but then booted into the Android OS.
So I flash TWRP [using Ubuntu, and $ fastboot install recovery {TWRP-filename.img}. And what do you know. It booted perfectly into recovery.
So how do you explain that?
mvmacd said:
Weird because today I tried to get into CWR for the first time since I rooted, and it wouldn't work. I got the red ! triangle [sticking out of the green robot].
I plugged it into my laptop.. [and btw I was holding vol UP/DOWN, press power, in the bootloader then selecting 'Recovery' then ] and this time it showed the "Google" and the unlocked lock.. but then booted into the Android OS.
So I flash TWRP [using Ubuntu, and $ fastboot install recovery {TWRP-filename.img}. And what do you know. It booted perfectly into recovery.
So how do you explain that?
Click to expand...
Click to collapse
The only possible ways to boot into recovery from a working system partition is by either using an app that reboots for you/terminal command.
To reboot from bootloader/button combination you need to have a USB connection otherwise it will freeze at the Google logo. This is bootloader related and not recovery related as any recovery (stock/cwm/twrp) show the same behavior.
You can try fully powering off the tablet and try booting by button combo and you will see it freezes. Using the power adapter will completely freeze your bootloader if you try, so you require a USB connection to a computer to get into recovery.
For me to boot into recovery , I have to use the tool kit all the time. Is that what everyone is doing??? Because every time I go to fastboot and choose recovery (with my N7 plugged on the usb) I get the Android with the exclamation point.
Sent from my HTC One X using xda app-developers app
Skunk2 DC said:
For me to boot into recovery , I have to use the tool kit all the time. Is that what everyone is doing??? Because every time I go to fastboot and choose recovery (with my N7 plugged on the usb) I get the Android with the exclamation point.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I had the same thing, but I flashed TWRP and it works most of the time. let me know if you try it.
What is the Difference between CWM vs TWRP recovery and which one is best for the my nexus 7
Any idea?:highfive:
OLYMPIAKOI said:
What is the Difference between CWM vs TWRP recovery and which one is best for the my nexus 7
Any idea?:highfive:
Click to expand...
Click to collapse
Both are relatively similar. I would have to take the side of TWRP at least on the N7. Last time i tried to flash something with CWM it didnt wipe correctly or flashed incorrectly and ended up with a courrpt ROM. Had to redownload and reflash with TWRP and it was fine. Dont know what it is with CWM on this device but on my Gnex it was just fine. As of right now i would stick to TWRP. It also doesnt do the whole blob deal for nandroids which IMO isnt quite ready and causes issues. At least in my experience.
Installation
ÜBER™ said:
Both are relatively similar. I would have to take the side of TWRP at least on the N7. Last time i tried to flash something with CWM it didnt wipe correctly or flashed incorrectly and ended up with a courrpt ROM. Had to redownload and reflash with TWRP and it was fine. Dont know what it is with CWM on this device but on my Gnex it was just fine. As of right now i would stick to TWRP. It also doesnt do the whole blob deal for nandroids which IMO isnt quite ready and causes issues. At least in my experience.
Click to expand...
Click to collapse
And where should I Flash TWRP?
1. Boot
2. Bootloader
3. Recovery
4. System
5. Userdata
Which Option shouldI choose?
D/L Goo.im from the PlayStore and install TWRP from there.
Sent from my Nexus 7 using xda app-developers app
OLYMPIAKOI said:
And where should I Flash TWRP?
1. Boot
2. Bootloader
3. Recovery
4. System
5. Userdata
Which Option shouldI choose?
Click to expand...
Click to collapse
Reboot to bootloader
open command prompt or terminal
type:
Code:
fastboot flash recovery openrecovery-twrp-2.3.1.1-grouper.img
(or whatever its called)
hit enter
You should see something like this:
Code:
[email protected]:~/Downloads$ fastboot flash recovery openrecovery-twrp-2.3.1.1-grouper.img
sending 'recovery' (7064 KB)...
OKAY [ 0.931s]
writing 'recovery'...
OKAY [ 0.489s]
finished. total time: 1.420s
[email protected]:~/Downloads$
then use the volume keys to ether select reboot or reboot to recovery
dparrothead1 said:
D/L Goo.im from the PlayStore and install TWRP from there.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yep!
I just did it as I had a problem with CWM, in goomanager you just go settings and choose "install open recovery" when it has downloaded you then select "reboot recovery" and that's it.
I think I like it better than CWM already, I like being able to name my backups as I do them, very handy.
ROOT
OK I have istalled TWRP ,
Now, HOW DO I ROOT IT?
OLYMPIAKOI said:
OK I have istalled TWRP ,
Now, HOW DO I ROOT IT?
Click to expand...
Click to collapse
Easily with either one of these.
http://forum.xda-developers.com/showthread.php?t=1766475
http://forum.xda-developers.com/showthread.php?t=1809195
I've used the latter.
OLYMPIAKOI said:
OK I have istalled TWRP ,
Now, HOW DO I ROOT IT?
Click to expand...
Click to collapse
Flash a superuser package or flash a custom ROM.
Sent from my Nexus 7
I have always used CWM on my phone for no reason other than that was what came w/ the kernal or rom pick of the day. Using the Nexus 7 Toolkit http://forum.xda-developers.com/showthread.php?t=1809195 I installed CWM, or tried to, ended up going to the play store for touch.
I have tried holding the power key, powerkey + vol, power++ or - vol and can not get into CWM to no avail. Yes it was connected to USB. I have to use Rom Manager to get to it. Just thinking if something/everything locks up there should another way to get to recovery.
Can I have both Twerp and CWM at the same time?
No. One recovery at a time.
But if you have root access all you need to do is get the terminal emulator from the market type :
Su(enter, grant root)
Reboot recovery
Or if you have adb on your computer (which you really should of you're going to be flashing anything) Just make sure you have. Usb debugging on and type: adb reboot recovery.
Btw the button combo is all three buttons(both volumes and the power button to boot into the bootloader the use the volume keys to toggle the option to recovery mode and hit the power button to confirm.
studacris said:
Btw the button combo is all three buttons(both volumes and the power button to boot into the bootloader the use the volume keys to toggle the option to recovery mode and hit the power button to confirm.
Click to expand...
Click to collapse
Thanks.....That's what I thought....didn't happen.
studacris said:
No. One recovery at a time.
But if you have root access all you need to do is get the terminal emulator from the market type :
Su(enter, grant root)
Reboot recovery
Or if you have adb on your computer (which you really should of you're going to be flashing anything) Just make sure you have. Usb debugging on and type: adb reboot recovery.
Btw the button combo is all three buttons(both volumes and the power button to boot into the bootloader the use the volume keys to toggle the option to recovery mode and hit the power button to confirm.
Click to expand...
Click to collapse
There are also apps like Quick Boot if you don't want to have to type in the terminal window each time you want to go to recovery
studacris said:
Btw the button combo is all three buttons(both volumes and the power button to boot into the bootloader the use the volume keys to toggle the option to recovery mode and hit the power button to confirm.
Click to expand...
Click to collapse
Vol Down and power is all it takes for me from a powered down state. The All-Three button is for hot-reboots.
a5ehren said:
There are also apps like Quick Boot if you don't want to have to type in the terminal window each time you want to go to recovery
Click to expand...
Click to collapse
+1 for Quick Boot
With the N7 running, I have found that if I hold the power button down with or without combos for 15-20 sec. it'll reboot, not just shut down. And yes, when starting with the power & -vol it starts in fastboot. I guess I assumed that it would behave just like my sg4g....live and learn .
I'm using ROM Manager to get to TWRP. Haven't decided which I like best twrp or cwm.
My thanks for putting up w/my noobie questions!
Sent from my Nexus 7 using xda premium
TheAtheistReverend said:
Vol Down and power is all it takes for me from a powered down state. The All-Three button is for hot-reboots.
+1 for Quick Boot
Click to expand...
Click to collapse
Firstly, love your username.
And You're right about the button combo.. I thought I was in the section for my phone lol.
Apps such as that are useful enough I spose.
Power tool is what I used back when my phone first came out and there was no rom with an extended power menu.
Was written by an xda recognized developer and good friend of mine, flappjaxxx
link to power tool if you wanna check it out
I have ICS Unlocked bootloader V8 with root on my A500.
Build Number
Acer_AV041_A500_1.041.00_WW_CUS1
Image version
Acer_AV041_A500_RV06RC01_WW_CUS1
Android version 4.0.3
kernel 2.6.39
I would like to install new CM10.1 JellyBean 4.2.1 or other.
Is it somewhere instruction how I can do it?
Where need to copy new image? Is it root directory? .Acer? or where?
Is it need copy zip file cm-10.1-20130105-UNOFFICIAL-a500.zip? or just image file?
Thanks,
Michael
Hi Michael, u should already have cwm it comes with the v8 bootloader...
What happens if u power your tab on with volume down button held in?
dibb_nz said:
Hi Michael, u should already have cwm it comes with the v8 bootloader...
What happens if u power your tab on with volume down button held in?
Click to expand...
Click to collapse
Hi dibb_nz,
I see boot loader menu.
If I push cm-...-a500.zip file to external sdcard and go to Boot Recovery
It just reboot.
Thanks,
Michael
ch_m said:
Hi dibb_nz,
I see boot loader menu.
Click to expand...
Click to collapse
do you mean skrilax v8 Fastboot Menu??? This is accessed by holding volume UP and Power
IF and only IF, you have the fastboot menu you can choose to enter fastboot mode, and connect your tab to your pc
Download the recovery image at the bottom of this post and put it in the same folder with fastboot.exe/adb.exe:
Run the following commands
Code:
fastboot devices
it should return a ?
Code:
fastboot flash recovery recovery_CWM.img
should say Done
Code:
fastboot reboot
quickly hold in the volume down button while it reboots - if you time it right it should boot to cwm...otherwise just power it down then try again
Please note again this is only possible with the unlocked bootloader
dibb_nz said:
do you mean skrilax v8 Fastboot Menu??? This is accessed by holding volume UP and Power
IF and only IF, you have the fastboot menu you can choose to enter fastboot mode, and connect your tab to your pc
Download the recovery image at the bottom of this post and put it in the same folder with fastboot.exe/adb.exe:
Run the following commands
Code:
fastboot devices
Click to expand...
Click to collapse
Yes. I did install Skrilax V8 unl bootloader with menu:
fastboot, boot Pr.., boot Sec... , Boot Recovery, Set... Wipe Cache
I use ADB from Android SDK platform-tools.
Never use fastboot.exe from it. I see it.
I will try.
Thanks,
Michael
Must I unlock bootloader to install CWM?
Mlopik said:
Must I unlock bootloader to install CWM?
Click to expand...
Click to collapse
Yes to get cwm or any other custom recovery the bootloader has to be unlocked first.
You have the unlocked v8 bootloader but not a recovery i don't know why you don't have one?? I'm confused!!
To get cwm now you can reflash the v8/cwm package
Or use fastboot method...
Hope that explains things better!
Sent from my GT-I9300 using Tapatalk 2
---------- Post added at 09:12 PM ---------- Previous post was at 09:09 PM ----------
What method/tool did u use to put the v8 on there in the first place?
Sent from my GT-I9300 using Tapatalk 2
dibb_nz said:
What method/tool did u use to put the v8 on there in the first place?
Click to expand...
Click to collapse
I used
V8-UNL-ICS-HC-bootloader-MULTI-cwm
and
APX_v0.4A-flashTool-500Manager1.0.2
I don't remember which one was finally.
Now I used fastboot flash recovery with your recovery_CWM.img.
Thanks it was work.
I did install
gapps-jb-20121212-signed.zip and
cm-10.1-20130105-UNOFFICIAL-a500.zip
It was success.
But I have CyanogenMod logo loop
I can't enter
What I did wrong?
Can I fix it?
Thanks,
Michael
I did it.
After factory reset and install it again.
It is working now.
Thanks everyone,
Michael
Great news! Feel free to hit the thanks button ae
Hows the rom going I haven't tried that one yet?
Sent from my GT-I9300 using Tapatalk 2
dibb_nz said:
Great news! Feel free to hit the thanks button ae
Hows the rom going I haven't tried that one yet?
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I have rooted acer iconia tab a500 but I want to install CWM... Some guide for this?
Thanks for advice
dibb_nz said:
Great news! Feel free to hit the thanks button ae
Hows the rom going I haven't tried that one yet?
Click to expand...
Click to collapse
It is working now. Looks good.
Unfortunately I lost connection from my adb now
Is it change device id?
I see it in Win explorer. But not in adb
Michael
Mlopik said:
I have rooted acer iconia tab a500 but I want to install CWM... Some guide for this?
Thanks for advice
Click to expand...
Click to collapse
I follow instructions from dibb_nz.
See this thread.
Michael
ch_m said:
It is working now. Looks good.
Unfortunately I lost connection from my adb now
Is it change device id?
I see it in Win explorer. But not in adb
Michael
Click to expand...
Click to collapse
I don't see developers setup option
USB debugging ? or TCP/IP ?
Mlopik said:
I have rooted acer iconia tab a500 but I want to install CWM... Some guide for this?
Thanks for advice
Click to expand...
Click to collapse
guide here: http://forum.xda-developers.com/showthread.php?p=35500578#post35500578
---------- Post added at 09:18 AM ---------- Previous post was at 09:13 AM ----------
ch_m said:
I don't see developers setup option
USB debugging ? or TCP/IP ?
Click to expand...
Click to collapse
yeh google hid it away on 4.2 at least on my Galaxy s3 they did....I had to go to Settings>About Phone> and tap on the build number 7 times???? bizarre I know!!!
You're best to go to the rom thread itself, it should be in the OP itself if not, it'll be in the main thread somewhere!!
recovery_CWM.img
hi sir in my case i cant flash the recovery_CWM.img ..when i try to flash it says "not support the command in lock mode"failed to process command download:00496800 error(0x2)"
please help me..thanks
http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_do-full_ota-28311_475.5300.zip
Disclosure:
Flash at own risk, not officially released.
You do not need root or anything else. This will work if you're bone stock.
The easiest way accomplish this is with an SD Card.
Once you have downloaded the OTA, copy it to your SD Card.
Power off device
Boot in Bootloader:
While device is off HOLD Vol-Down and TAP the Power Button once (do not hold the power button). Let go of Vol-Down once you see logo.
Boot into Recovery
Once in Bootloader use the Volume buttons to navigate to Recovery Mode, use Power button to select.
You will then see an Android with an ! and says no command. IGNORE THIS.
Push Vol-UP and then Power.
You will access the Recovery Menu.
Select Apply Update from SD Card.
Find your .zip and select.
It will apply update and will say finished at the bottom of the screen.
Now select Reboot System.
Wait till it boots.
Depending on your setup it can take anywhere from 2min to 30min. Be patient.
Now you have your update. Enjoy
Click to expand...
Click to collapse
If you want to do an "adb sideload"
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
If you get an error while trying update, verify your .zip file is the right size.
If for some reason you completely crap your device follow this link and scroll down to Recovery images.
https://developer.nvidia.com/develop4shield
Click to expand...
Click to collapse
timskyline86 said:
http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_do-full_ota-28311_475.5300.zip
Disclosure:
Flash at own risk, not officially released.
Click to expand...
Click to collapse
Updated my US LTE version with this file and everything seems to be just fine. just beware that after flashing the Nvidia logo will remain on the screen for 3-5 minutes before finalizing the upgrade script. I must admit I did sweat a little...
Carlos
Chaleman said:
Updated my US LTE version with this file and everything seems to be just fine. just beware that after flashing the Nvidia logo will remain on the screen for 3-5 minutes before finalizing the upgrade script. I must admit I did sweat a little...
Carlos
Click to expand...
Click to collapse
HOW did you flash it?
Prfndhatrdofman said:
HOW did you flash it?
Click to expand...
Click to collapse
I put the zip in mysdcard and boot to recovery. I flashed it from there. I had previously installed CWM on my tablet....
Carlos
For stock
ADB sideload. Or SD Card
Power off device.
Hold Volume Down then Power button until Bootloader.
Choose Recovery
Then your option.
If you do it through the computer its:
Adb devices
adb sideload filename.zip
Reboot
Done just like the Nexus devices.
Flashed via PhilZ, worked like a charm.
timskyline86 said:
For stock
ADB sideload. Or SD Card
Power off device.
Hold Volume Down then Power button until Bootloader.
Choose Recovery
Then your option.
If you do it through the computer its:
Adb devices
adb sideload filename.zip
Reboot
Done just like the Nexus devices.
Click to expand...
Click to collapse
I can't believe is that easy, I'm super happy and I will be testing it once I load it in to the SM Card.
---------- Post added at 12:40 PM ---------- Previous post was at 12:29 PM ----------
I found the following information on the Nvidia developer site :
(https://developer.nvidia.com/sites/...eld/SHIELD_tab/HowTo-Flash-Recovery-Image.txt)
SHIELD TABLET RECOVERY IMAGE FLASHING INSTRUCTIONS
To follow the instructions in this guide, you will need adb and fastboot.
These tools are provided as part of the Android SDK:
http://developer.android.com/sdk/index.html
Before flashing this recovery image to your SHIELD TABLET, connect your SHIELD TABLET
via USB to the PC where you downloaded this recovery image.
Next, put your SHIELD TABLET into fastboot mode using one of the following methods:
SW method:
- Boot to android home screen
- Connect the device to linux/windows system
- Open terminal (on linux); command prompt (on windows).
- Type "adb reboot bootloader" in terminal/command prompt
HW method:
- Turn off the device
- Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
To flash this recovery image to your SHIELD TABLET, run the following commands from
the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader (see
below):
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
Unlocking the Bootloader
Your SHIELD TABLET may have shipped with a locked bootloader. To update the device,
you must unlock the bootloader using the following:
- fastboot oem unlock
- Press the "Volume Down" button to select "Unlock bootloader" option on device
- Press the "Power" button to confirm the unlock. Your device's bootloader is now unlocked.
---------- Post added at 12:46 PM ---------- Previous post was at 12:40 PM ----------
timskyline86 said:
Hold Volume Down then Power button until Bootloader.
Choose Recovery
Then your option.
Click to expand...
Click to collapse
For some reason I can't get it to boot into the bootloader by pressing the power and volume down. It just boots up and shuts down, how long should I wait until I let go?
an0m13 said:
For some reason I can't get it to boot into the bootloader by pressing the power and volume down. It just boots up and shuts down, how long should I wait until I let go?
Click to expand...
Click to collapse
Steps that worked for me:
Shut down
Wait 20 seconds after shut down
Hold Vol Down
Press power button (don't hold)
an0m13 said:
I can't believe is that easy, I'm super happy and I will be testing it once I load it in to the SM Card.
---------- Post added at 12:40 PM ---------- Previous post was at 12:29 PM ----------
I found the following information on the Nvidia developer site :
(https://developer.nvidia.com/sites/...eld/SHIELD_tab/HowTo-Flash-Recovery-Image.txt)
SHIELD TABLET RECOVERY IMAGE FLASHING INSTRUCTIONS
To follow the instructions in this guide, you will need adb and fastboot.
These tools are provided as part of the Android SDK:
http://developer.android.com/sdk/index.html
Before flashing this recovery image to your SHIELD TABLET, connect your SHIELD TABLET
via USB to the PC where you downloaded this recovery image.
Next, put your SHIELD TABLET into fastboot mode using one of the following methods:
SW method:
- Boot to android home screen
- Connect the device to linux/windows system
- Open terminal (on linux); command prompt (on windows).
- Type "adb reboot bootloader" in terminal/command prompt
HW method:
- Turn off the device
- Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
To flash this recovery image to your SHIELD TABLET, run the following commands from
the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader (see
below):
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
Unlocking the Bootloader
Your SHIELD TABLET may have shipped with a locked bootloader. To update the device,
you must unlock the bootloader using the following:
- fastboot oem unlock
- Press the "Volume Down" button to select "Unlock bootloader" option on device
- Press the "Power" button to confirm the unlock. Your device's bootloader is now unlocked.
---------- Post added at 12:46 PM ---------- Previous post was at 12:40 PM ----------
For some reason I can't get it to boot into the bootloader by pressing the power and volume down. It just boots up and shuts down, how long should I wait until I let go?
Click to expand...
Click to collapse
When the device is off, start by holding the volume down button. While holding the volume down button, just press the power button once. Keep holding volume down until you get into fastboot mode, then you can let go and do your thing.
Thanks, all it needed was a tiny tap on the power button ( I was just holding until I saw the logo)
---------- Post added at 12:59 PM ---------- Previous post was at 12:56 PM ----------
I got in to the bootloader and then I select "Recovery mode" and all I get is a "No command" message with the android with the red exclamation sign.
an0m13 said:
Thanks, all it needed was a tiny tap on the power button ( I was just holding until I saw the logo)
---------- Post added at 12:59 PM ---------- Previous post was at 12:56 PM ----------
I got in to the bootloader and then I select "Recovery mode" and all I get is a "No command" message with the android with the red exclamation sign.
Click to expand...
Click to collapse
Sounds like the stock recovery. Someone on GeForce forums is reporting that you can use flashify with the stock recovery, though!
From the No Command screen hold Power + Up Volume. You should see the recovery options.
My SDCard would not mount, so I had to ADB Sideload the file. After a long reboot things seem to be working just fine.
Bit of a noob question, but how do i know if my shield tab is a US LTE or EU LTE???
theRealBra_Zee said:
Bit of a noob question, but how do i know if my shield tab is a US LTE or EU LTE???
Click to expand...
Click to collapse
It's based on where you live most likely
US=America
EU=Everywhere Else
SuperPichu said:
It's based on where you live most likely
US=America
EU=Everywhere Else
Click to expand...
Click to collapse
I'm in Ghana(Africa), got the tab from an aunt in the US, so i'm guessing it's US LTE. Came with an AT&T sim card and everything
theRealBra_Zee said:
I'm in Ghana(Africa), got the tab from an aunt in the US, so i'm guessing it's US LTE. Came with an AT&T sim card and everything
Click to expand...
Click to collapse
Yeah that is probably the US one then.
khart1978 said:
From the No Command screen hold Power + Up Volume. You should see the recovery options.
My SDCard would not mount, so I had to ADB Sideload the file. After a long reboot things seem to be working just fine.
Click to expand...
Click to collapse
Did you use stock recovery?
Sideloaded about an hour ago and everything seems fine with my TMO service.
Those of you who're in the US and have flashed your LTE unit and who use T-mobile, can you give us any impressions of the alleged "fix" nvidia did for T-mobile LTE signals/coverage? Better? Worse? No difference?
I'm really struggling to decide whether or not I should wait or go ahead and install this "EU" rooted version instead. The only thing I am interested in is better T-Mobile LTE coverage. On KitKat, the LTE T-mobile signal is either non-existent or abysmal at best.
isamu99 said:
Those of you who're in the US and have flashed your LTE unit and who use T-mobile, can you give us any impressions of the alleged "fix" nvidia did for T-mobile LTE signals/coverage? Better? Worse? No difference?
I'm really struggling to decide whether or not I should wait or go ahead and install this "EU" rooted version instead. The only thing I am interested in is better T-Mobile LTE coverage. On KitKat, the LTE T-mobile signal is either non-existent or abysmal at best.
Click to expand...
Click to collapse
I'm not getting much difference in behavior.
Dear Team,
Please help, I have AZP2 4GB Ram, 64GB ROM, 2.3GHZ version phone. Up volume button has stopped working and i required to go into recovery mode. But due to hardware fault i can't do it.
My phone is ROOTED with 5.0 Android
Is there any i can change the hardware button setting from UP volume to Down Volume to enter into recovery mode. I have tried several app to enter into recovery mode but every time system boots up to home screen of Asus. Tested apps are Terminal, Rom manager and Windows Batch mode, but all fails.
Please help.
dineshdotcom2000 said:
Dear Team,
Please help, I have AZP2 4GB Ram, 64GB ROM, 2.3GHZ version phone. Up volume button has stopped working and i required to go into recovery mode. But due to hardware fault i can't do it.
My phone is ROOTED with 5.0 Android
Is there any i can change the hardware button setting from UP volume to Down Volume to enter into recovery mode. I have tried several app to enter into recovery mode but every time system boots up to home screen of Asus. Tested apps are Terminal, Rom manager and Windows Batch mode, but all fails.
Please help.
Click to expand...
Click to collapse
Connect the phone to a computer and use 'adb reboot recovery'
Sent from my ASUS_Z00AD using Tapatalk
---------- Post added at 04:20 AM ---------- Previous post was at 04:19 AM ----------
Or use one of the power/reboot widgets you can get in the play store
Sent from my ASUS_Z00AD using Tapatalk
kenbo111 said:
Connect the phone to a computer and use 'adb reboot recovery'
Sent from my ASUS_Z00AD using Tapatalk
---------- Post added at 04:20 AM ---------- Previous post was at 04:19 AM ----------
Or use one of the power/reboot widgets you can get in the play store
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
TIt gives an error: One or more device/emulator
dineshdotcom2000 said:
TIt gives an error: One or more device/emulator
Click to expand...
Click to collapse
http://androidforums.com/threads/adb-shell-error-more-than-one-device-and-emulator.48572/
Sent from my ASUS_Z00AD using Tapatalk
If not stuck on asus loading screen !
https://play.google.com/store/apps/details?id=com.codem.reboot -- requires root rights
Reboot recovery , goes straight into recovery if TWRP installed .
No good if got stock recovery .
If stock recovery , you can only choose reboot bootloader . Where you can fastboot flash TWRP --
Reboot to recovery with TWRP and the app is all good after !
If already TWRP , alls good from the off !
If no success with Kenbo`s linked solution