OK here is what happened. I am running zulu99 full android os. Worked great. I downloaded an app from the Google play store to change the dpi. After I made the change to the dpi settings the app ask me to OK a reboot. Now my Shield TV Pro is stuck on a bootloop and I cant get it into hardware recovery. Any ideas on how to enter recovery another way? I tried unplugging the shield plugged the power back in . Then I hold down the power button for 3 seconds let the power button go and press it down again for a second. I tried this many times and I just end up back in bootloop. Is there any other way to get into fastboot to flash back to stock ? Or do I now have a paper weight ?
Thank you
milko002 said:
OK here is what happened. I am running zulu99 full android os. Worked great. I downloaded an app from the Google play store to change the dpi. After I made the change to the dpi settings the app ask me to OK a reboot. Now my Shield TV Pro is stuck on a bootloop and I cant get it into hardware recovery. Any ideas on how to enter recovery another way? I tried unplugging the shield plugged the power back in . Then I hold down the power button for 3 seconds let the power button go and press it down again for a second. I tried this many times and I just end up back in bootloop. Is there any other way to get into fastboot to flash back to stock ? Or do I now have a paper weight ?
Thank you
Click to expand...
Click to collapse
==========
HowTo Flash:
==========
Before flashing images from this build to your SHIELD, connect your SHIELD
via USB to the PC where you built this tree.
Next, put your SHIELD into fastboot mode using following method:
SW method:
Boot to android home screen
Connect the device to linux system
Open terminal(on linux)
Type "adb reboot bootloader" in terminal
HW method:
Disconnect power cable
Insert USB OTG cable and make sure to connect other end to a host PC
Connect power cable to SHIELD
Quickly start pressing power button for ~3 seconds
Do not hold the button and connect power supply afterwards
HDMI TV should be always connected to SHIELD
Alternative method:
Perform software shutdown on SHIELD by holding Power button for 10 seconds
Connect USB OTG cable to SHIELD
Start pressing power button for 3 seconds
HDMI TV should be always connected to SHIELD
Click to expand...
Click to collapse
source: http://nv-tegra.nvidia.com/gitweb/?...ob_plain;f=README_SHIELD;hb=rel-22r18-partner
I suggest you keep trying those methods. There's some issues with the current bootloader, so if you can't get it to work eventually you'll be stuck with having to rma it. If you get it working, I suggest you stop messing with it until after the next OTA, which is supposed to fix the bootloader issues.
Some of the issues are mentioned here, with a response from nvidia: https://forums.geforce.com/default/topic/893616/bootloader-issues
The HW method worked .
Thanks For the help !
Related
I tried to downgrade from 3.2 with that tool and every time it shows me that the operation had failed
Now i am stuck in APX mode help
please anyone????
jimmis1996 said:
please anyone????
Click to expand...
Click to collapse
Reinstall your USB drivers and try again.
And make sure your tablet is in apx mode.
How :
Connect tablet with USB cable when it is off.
Now with paperclip press the reset button and power button together for 3 seconds, then release power button and one second later you release the reset button ( screen of tablet stays black but you will see that in device manager on your pc under USB devices you should see Acer Picasso recovery driver listed , then you know your tablet is in apx mode and connected.)
Now you can Start.
civato said:
Reinstall your USB drivers and try again.
And make sure your tablet is in apx mode.
How :
Connect tablet with USB cable when it is off.
Now with paperclip press the reset button and power button together for 3 seconds, then release power button and one second later you release the reset button ( screen of tablet stays black but you will see that in device manager on your pc under USB devices you should see Acer Picasso recovery driver listed , then you know your tablet is in apx mode and connected.)
Now you can Start.
Click to expand...
Click to collapse
i done it a lot of times but i still says tha the operation cannot be completed.
Could i leave APX mode and boot normally?
HELP PLEASE
OOF!!!!
Well i managed to boot again by using an other pc
Thanks for your help
Okay so I seem to have run into a little problem I was planning on updating cleanrom up to 1.2.5 but was on cwm. I had managed to switch over successfully to twrp 2.2.0. I went ahead and used goo manager to download the updated zip of 2.2.1 and tried flashing it thru twrp. Now I am stuck in google bootloop and cant get into recovery or more importantly bootloader. I have been trying last 30mins to hold power and both volume buttons but it either keeps rebooting back to the google screen or not doing anything at all just have to repress to to turn it off but it will turn back on automatically. I tried hooking it up to my usb and labtop but it looks like it wont even recognize it. I just fully charged it so I am good for now just a little worried cant get out of this mess.
I ran into a problem like that with clockwork recovery it kept on rebooting in recovery but I could still go into download mode I was at work away from my computer so I had no choice but to keep trying that three button magic until it finally restored a backup I had on my external card.just keep on trying to pull the battery then try to go into recovery. You might 've gotten a bad download
Sent from my SGH-T999 using xda premium
problem is I cant get into recovery. or the green screen to get to bootloader. It just completely stuck in a bootloop on the google screen mocking me... I am really contemplating opening it up and taking out battery but is that a good idea? Or is there anything else I can do?
so I pulled off the back cover but really dont want o disconnect the battery might mess something up but I cannot get the device to shut off.
disconnecting the battery does nothing it shuts it off and keeps it off but when I connect it to the charger the battery symbol pops up for a second and then goes completely blank. I went ahead and tried again to boot into bootloader pressing power vol up + down and all combinations of power vol -, power vol +
power turbo press vol +/- but no luck still in google screen.
If you're in a bootloop you need to connect your Nexus 7 to a computer. Then you will be able to access recovery via the Power button and volume buttons.
is it going to make a difference that everytime i try to reboot it just the black google screen? I have tried it connected to the wall charger and connected usb to the labtop but nothing.
clago87 said:
is it going to make a difference that everytime i try to reboot it just the black google screen? I have tried it connected to the wall charger and connected usb to the labtop but nothing.
Click to expand...
Click to collapse
It's supposed to do that when you're trying to go to recovery from bootloader without the USB cable plugged into a computer, may need to have the drivers installed on said computer. It's an issue with the nexus 7 bootloader and every one of them does it. What your experiencing is perfectly normal if you tried to go to recovery from bootloader with the bolume buttons and then got the google screen bootloop.
If it doesn't work when you plug it in and try, then try unplugging it, manually rebooting with it plugged in first, or vice versa
Update: I can get on Team Viewer and remotely reboot you into recovery through the PC if you want, or at least give it my best shot.
ok so i disconnected battery and have the device off. I should then try connecting it to the pc and try booting up holding down all buttons?
clago87 said:
ok so i disconnected battery and have the device off. I should then try connecting it to the pc and try booting up holding down all buttons?
Click to expand...
Click to collapse
Have you installed the right drivers on the computer you're using, for ADB and the device drivers, when you unlocked and rooted?
Answer to your question is yes try that. But I wouldn't be disconnecting and reconnecting it, I can't recommend that and then learn tomorrow that static zapped something important.
yea I am getting nothing by connecting to pc. I have all the drivers adb and fastboot installed when I rooted and unlocked couple weeks back but it looks like device is not being recognized or read at all by the pc.
connecting to the pc holding the volume + button gets it recognized for a second and tries to install a driver apx but unsuccessfully.
I am not making any progress whatsoever kinda sucks starting the weekend like this. I have gone thru some bad stuff with my atrix but nothing like this were I cant even access my bootloader boot into recovery or even fastboot. Should I try and get it to just stay off and see if overnight it works its own magic? Hate going to sleep witht his on my mind but I think with a clear mind in the morning something good will happen.
I can get it to stay off by holding both vol+ and vol- but trying to turn it off with just the power button just keeps it turning back on/off...
so I slepted on it thru the night let the tablet rest but went back this morning and I still cant get into bootloader or recovery. Is there anything I can do?
Has anyone else had this problem where they cant boot into recovery or bootloader? It's like the power button and vol keys are unresponsive even though they still work to turn on the device.
are you sure that you flashed the right recovery? but you should still be able to get the bootloader. are you pressing power + volume down(volume down, not both volume buttons. i noticed you wrote both volume buttons) to get into the bootloader?
I think I chose the right recovery the first version downloaded thru goo manager but it was the 2.2.0 version. I had the option on the of downloading the 2.2.1 zip or the .img but i downloaded the .img to just to flash with the current version of twrp that was working. There have been times were I have not been able to get into recovery on my atrix or htc but I've always been able to get into the bootloader this is the first time I've been locked out of my device kind of got me scared its not even a month old. So you say to get into bootloader you dont have to hold down both volume buttons? I will try again to power back up using the volume down and power button at same time... Wish me luck
clago87 said:
I think I chose the right recovery the first version downloaded thru goo manager but it was the 2.2.0 version. I had the option on the of downloading the 2.2.1 zip or the .img but i downloaded the .img to just to flash with the current version of twrp that was working. There have been times were I have not been able to get into recovery on my atrix or htc but I've always been able to get into the bootloader this is the first time I've been locked out of my device kind of got me scared its not even a month old. So you say to get into bootloader you dont have to hold down both volume buttons? I will try again to power back up using the volume down and power button at same time... Wish me luck
Click to expand...
Click to collapse
good luck!
yea, only power button and the volume down button.
quick question before I connect the battery does it make a difference whether or not I have it plugged in charging or connected to the PC while trying to boot into bootloader?
OMG, my Shield wont boot anymore, it's stays at Nvidia Logo. I am on stock rom, with custom recovery and root.
I made a full wipe from TWRP and after reboot, Shield wont pass Nvidia logo. Any advice? I hope is not a hard brick or something, i dont know why not to boot after wipe...(
http://myprintscreen.com/s/b7ks/41bcbe9070
http://myprintscreen.com/s/b7kt/274989961f
darktyroll said:
http://myprintscreen.com/s/b7ks/41bcbe9070
http://myprintscreen.com/s/b7kt/274989961f
Click to expand...
Click to collapse
well it is told a lots of time,twrp is unstable with the shield...
there are chances you can flash again the shield by following nvidia tutorial with the power button to put it in recovery mode and flash factory images but if it does not work you are good to rma the device.
tailslol said:
well it is told a lots of time,twrp is unstable with the shield...
there are chances you can flash again the shield by following nvidia tutorial with the power button to put it in recovery mode and flash factory images but if it does not work you are good to rma the device.
Click to expand...
Click to collapse
If you reffer about the tutorial with plug in power source then press 3 seconds the power button an shield and telease it...i tryed. Same thing, nvidia logo.
If i send it back to amazon, they can find it it was rooted with custom recovery?
darktyroll said:
If you reffer about the tutorial with plug in power source then press 3 seconds the power button an shield and telease it...i tryed. Same thing, nvidia logo.
If i send it back to amazon, they can find it it was rooted with custom recovery?
Click to expand...
Click to collapse
yep but not sure. try again,if adb or fastboot detect it you are good.
tailslol said:
yep but not sure. try again,if adb or fastboot detect it you are good.
Click to expand...
Click to collapse
adb dont see my device.
anyway, when i plug in power cable, the shield turn on (without me to press power button), it is normal?
i belive the shield must power on only when i press power button, not to plug the cable in. I am right? Is weird....
My PC see the driver MTP USB, and i hear that sound when i connect to PC, but what to do more? I dont know....
darktyroll said:
adb dont see my device.
anyway, when i plug in power cable, the shield turn on (without me to press power button), it is normal?
i belive the shield must power on only when i press power button, not to plug the cable in. I am right? Is weird....
My PC see the driver MTP USB, and i hear that sound when i connect to PC, but what to do more? I dont know....
Click to expand...
Click to collapse
yep mine does that all the time. there a easy way of doing it by mashing the power button while plugin the shield (with hdmi still connected.)
Yeee, i`m happy, problem solved. Finnaly i was able to access recovery menu (via Nvidia tutorial) and flash back again stock rom.
I dont know why first 5472357242354239 times won't boot
darktyroll said:
Yeee, i`m happy, problem solved. Finnaly i was able to access recovery menu (via Nvidia tutorial) and flash back again stock rom.
I dont know why first 5472357242354239 times won't boot
Click to expand...
Click to collapse
yes the timing is super tight and finicky thats why i told you to try again,this thing is a b... to reboot in recovery.
tailslol said:
yes the timing is super tight and finicky thats why i told you to try again,this thing is a b... to reboot in recovery.
Click to expand...
Click to collapse
Very indeed. "Hard with 1 button only"
Hi together,
thanks especially to xyz` and k4y0z for your effort and your contributions! This is amazing!
I have an Amazon Fire HD 8 (karnak) with FireOS 6.3.1.2 which I want to root, unlock and install LineageOS on.
With 6.3.0.0 on another tablet, I already performed this procedure successfully.
As k4y0z writes in https://forum.xda-developers.com/hd...nlock-fire-hd-8-2018-karnak-amonet-3-t3963496 that a hardware-change in combination with the soft-brick method could lead to a real brick rendering the device unusable, I went for the hardware method.
What I did:
1. Disconnect tablet
2. Run "bootrom-step.sh"
3. Shorten CLK to GND and at the same time connect the tablet to USB
4. I get the message to remove the short and confirm with ENTER
--> flashing occurs and I find myself in fastboot mode (the tablet also shows up when I do a "fastboot devices")
5. Run "fastboot-step.sh"
--> flashing of recovery and misc occurs, followed by a reboot
Then I see the "Amazon" logo flashing shortly and then the screen stays black. I tried pressing power and the volume-keys shortly, twice, for a long time, ... nothing happens.
If I disconnect and reconnect USB I see the "Amazon" logo flashing again. The device is not in fastboot mode, ("fastboot devices" shows no device) nor is it in adb mode ("adb devices" also shows no device).
Luckily the steps below can be performed again and the flash procedure happens again so I can always get into fastboot mode but then I'm stuck flashing the TWRP with the fastboot-step.sh...
I tried the files from karnak-3.0, karnak-3.0.1 as well as the original amonet-v2, all with the same issue.
Can anybody please shed some light here? What am I doing wrong? Is there anything else I can try or is the tablet unusable now (which I cannot believe as there is fastboot access).
I am in fact running Debian 10 on a VirtualBox on my MacBook with USB forwarding to the Virtual Machine but I'm not sure if that can be the issue as all the flashes are working just fine.
Thanks for your support!
How old is the tablet? Anything bought January or newer is potential unlock-blocked....
Thanks for your answer, Michajin.
The tablet was bought in February 2020. Does that mean I'm out of luck getting LineageOS to run on this tablet?
Would the error I am seeing fit the unlock-block? I had the feeling that all the installing went through just fine, just TWRP is not loaded correctly, right?
Thanks!
Michajin said:
How old is the tablet? Anything bought January or newer is potential unlock-blocked....
Click to expand...
Click to collapse
freddy40 said:
Thanks for your answer, Michajin.
The tablet was bought in February 2020. Does that mean I'm out of luck getting LineageOS to run on this tablet?
Would the error I am seeing fit the unlock-block? I had the feeling that all the installing went through just fine, just TWRP is not loaded correctly, right?
Thanks!
Click to expand...
Click to collapse
If the fastboot-step finishes as success you have TWRP (fastboot step is just the flashing of twrp replacing stock recovery). You should be able to hold the volume down and press the power button, this will boot the device into recovery.
Thanks, Michaejin! That did the trick. Pressing those buttons yesterday didn't help as the tablet was somehow turned on, now I disconnected and reconnected the battery and pressed VolDown + Power and got into TWRP!
Great! Thanks again!
Michajin said:
If the fastboot-step finishes as success you have TWRP (fastboot step is just the flashing of twrp replacing stock recovery). You should be able to hold the volume down and press the power button, this will boot the device into recovery.
Click to expand...
Click to collapse
freddy40 said:
Thanks, Michaejin! That did the trick. Pressing those buttons yesterday didn't help as the tablet was somehow turned on, now I disconnected and reconnected the battery and pressed VolDown + Power and got into TWRP!
Great! Thanks again!
Click to expand...
Click to collapse
You can also hold the power button for about 10 seconds to force a power down, so you should have to pull the cover off in case something goes wrong. Likely the device was stuck in preloader or bootrom.
Hello dear xda community
I have a px6 device from the company "Wondefoo" installed in my Mazda (without any hard buttons). It worked so far so good, but ZLink (Apple Carplay) didn't work, so I tried to fix this. To do that, I rooted the device, uninstalled the "ZLink" app and reinstalled a newer version. Then I tried to reboot. And then my problems started:
The device doesn't boot anymore. It tries to start up, I can see the Android 10 boot logo ("multi-media on-vehicle Navigation System" screen), but after about one minute, this logo disappears and the screen remains black.
OK, easy fix --> Just go into recovery mode and reset the device. But here's the big problem: I can't get into recovery mode.
Here's what I tried:
1. Ignition off and on --> Screen still black
2. Press "Reset" button (my device only has this one physical button) --> Boot process started again, but same outcome
3. Unmount the device, plug the power out, wait an hour, plug it in again and try again --> Boot process started again, but same outcome
4. Tried to connect with adb over Wi-Fi to the device (used the last known IP address) --> Connection timeout, Wi-Fi probably not started yet
5. Press&Hold "Reset" button until lights beign to flash to get into recovery mode --> Lights never flash because the "Reset" button somehow breaks the power circuit and when I release it, the device gets power again and boot process starts again with same outcome
6. Press&Hold "Reset" button for a minute, then release it, then press it again quickly within 1sec --> Boot process started again, same outcome
7. Tab with 5 fingers on the boot logo --> Nothing happened
8. Attached keyboard and pressed "Alt" + "PrintScreen" + "I" all the time --> Nothing happens. Keyboard is with RGB LEDs, so I saw it was active when the boot logo was displayed... Then, the LEDs on my keyboard turned off which was telling me that there is no keyboard input possible anymore
9. I even tried this: https://forum.xda-developers.com/t/new-method-enter-recovery-no-physical-buttons.4013453/ --> I just have one similar cable, not two as described in this post... So I put everything together again and just tried again --> Boot process started again, same outcome
Well... Is there any option left? I'm thinking about buying a USB male-to-male cable and try again with adb, but everyone tells me that I need to get into recovery mode first which I really can't
* Is there any other way to get into recovery mode? Maybe with my keyboard?
* Does anyone have another idea what I could try? Maybe without recovery mode?
Thanks in advance and cheers
T
As you said:
1. Ignition off and on
2.Have ready the needle for reset and do that instantly as you see the boot logo.
Once device restarted, wait until will see the boot logo again and pull out the ignition key.
3. Put in an USB socket a pen drive with the right firmware
4. Put back the ignition key and let it in ON position, without starting the engine. The update process will start, have a bit of patience until will finish. The device will restart at the end of the update, and straight after the boot logo, shortly press the reset button.
With a bit of luck, will have a fresh firmware on your device.
Thanks for your quick answer.
I tried what you said several times, but unfortunately I always end up on the black screen, no matter what I try.
My usb stick flashes quickly during the boot process, but nothing happens with it.
I also tried with an USB male-to-male cable and connect via adb, but it won‘t connect...
t-to-the-a said:
5. Press&Hold "Reset" button until lights beign to flash to get into recovery mode --> Lights never flash because the "Reset" button somehow breaks the power circuit and when I release it, the device gets power again and boot process starts again with same outcome
Click to expand...
Click to collapse
Are you sure you are holding the reset button for long enough?
On my machine (Dasaita) you hold the reset and the machine turns off... but you have to keep holding it even after it has turned off. Could be upwards of 1.5 minutes. Once the lights flash (and finished flashing), release and press one more time within 3 seconds.
Thank you for this idea. I have tried 30 seconds, but no more until today...
Now I tried with 1min, 2mins, even 3mins, but nothing happens.. I think the power is immediately cut as soon as I press the reset button. So there is probably no way to fix this easily
I also contacted the seller, but they have a talent to not understand my question. I just get answers like "press the reset button 2 sec and then everything is fixed" or "plug in the USB drive with the new ROM and press update" - of course that doesn't help.
Well I guess I'm left with one last thing: Throw this device away and buy a new one. Not from Wondefoo anymore of course, and hopefully with a working reset button.
I have the same issue. What did you end up doing?
Where did you buy your unit from?