I try update my nvidia shield tv 2017 but now the System bootloop on Android circles animation (dont start box).
- I try fastboot with Controller but dont work (many, many times)
- I try conect to pc but dont connect device with fastboot
bricked bootloader??
I dont have solutions.... please help.
Sorry my english
Try un plugging the power then plug a USB keyboard in and hold the A and B key and then plug the power back in.
same problem for 3 days, can not enter fastboot mode. my shield is in bootloop
Shot in the dark, but have you tried different USB ports on the computer? I know in my case, some otherwise working ports will not work with the shield. Seems to be very fussy when it comes to which ports I choose. None of my front ports work on this desktop, I have to plug into rear ports in order for my computer and shield to see each other.
Also be sure to use the original cable that came with the shield.
Also make sure USB debugging is on.
Any fix ? Same problem
Have you tried "adb reboot bootloader" in command prompt when the android logo is looping?
I have no Android logo i have no os just twrp and twrp with no access adb and fastboot command dont work on NVIDIA logo
If you put lineage os on a usb stick can twrp read the usb stick? If so, you can install the zip file of lineage with gapps...once that's installed and booted up, you can enable usb debugging in the developers options and fastboot and adb should work again.
Related
- How My Phone Got Bricked?: (Chinese Version Oneplus 2) I Was On Oxygen OS 3.0 And TWRP 3.0 And I Decided To Flash The Resurrection Remix ROM, I Did A Full Wipe And I Installed The Rom And It Failed To Installed The ROM. Now My Phone Is In A Bootloop With No OS Installed. I Have The Chinese Version OP2
- Current State Of My Device: My Device Is In A Bootloop With No OS Installed, I Did Notice That My Phone Was Not Being Recognized VIA Fastboot & ADB On My PC. I Went Fastboot Mode And My Phone Is Not Being Recognized By PC, And I Went To TWRP, ADB Was Not Working And ADB Sideload Is Not Working. I Also Tried A USB OTG With A USB Drive And Still TWRP Recovery Is Not Recognizing It. How Ever When I Connect My Device To PC And Check Device Manager And Press Scan For Hard Ware Changes My Device Shows Up As "COM 1". I Also Did Try To Put My Phone Into Qualcomm Mode Trying Alot Of Key Combinations But My Phone Is Not Getting Into Qualcomm Mode Or It Just Might Be Me Since I Heard Its Tricky For The Phone To Get Into Qualcomm Mode. I Did Try One Click ADB And Fastboot Installed And Qualcomm USB Driver, Still No Luck. And I Did Try The MEGA Unbrick Guide. I Have Tried This With 3 Other Computers Which Are All Running Windows 10 And Turned Driver Signature Enforcement Off And Still No Luck, And Also A PC Running Linux Mint And Still No Luck. Please Help Me And I Will Put All Thanks On All Of Your Replies And I Really Appreciate Your Help!
- Whats Working:
- My Device Charges From The PC And Wall
- I Am Using The Official OP2 Cable
- Can Access Recovery + Fastboot
- Turns On But In A Bootloop
I think it's a bad cable... if you can get into fastboot and the PC with Windows 10 and Linux both don't see it.. cable
Not sure whats needed on windows, since I never use it....but after a fresh install of Ubuntu 16.04 a few days ago, I did have to install a few adb and fastboot packages before my devices were recognized. Do you know if the adb/fastboot packages and they're dependencies are installed on the Linux mint computer?
If yes, power off phone and plug into computer. Then start phone in fastboot mode. Open a terminal on the PC and run "adb devices" (without quotes of course) .....any output on screen?
foomanjackel said:
Not sure whats needed on windows, since I never use it....but after a fresh install of Ubuntu 16.04 a few days ago, I did have to install a few adb and fastboot packages before my devices were recognized. Do you know if the adb/fastboot packages and they're dependencies are installed on the Linux mint computer?
If yes, power off phone and plug into computer. Then start phone in fastboot mode. Open a terminal on the PC and run "adb devices" (without quotes of course) .....any output on screen?
Click to expand...
Click to collapse
Yeah I did try typing ADB devices and Fastboot devices in both twrp and fastboot. I think the issue might be the cable
evertking said:
I think it's a bad cable... if you can get into fastboot and the PC with Windows 10 and Linux both don't see it.. cable
Click to expand...
Click to collapse
Yeah I think the cable is probably the problem. Although my phone chargers with the cable. I will look into buying a new cable soon but its a little expensive. I will try to buy it next week
fahad999 said:
Yeah I think the cable is probably the problem. Although my phone chargers with the cable. I will look into buying a new cable soon but its a little expensive. I will try to buy it next week
Click to expand...
Click to collapse
I'm sure you been reading and seen people with the same cable as ours with the same problem.. works with charging but not adb or fastboot. But you can try to issue a command with it.. fastboot devices does sometimes come back empty.. just try to do OEM unlock for example.
evertking said:
I'm sure you been reading and seen people with the same cable as ours with the same problem.. works with charging but not adb or fastboot. But you can try to issue a command with it.. fastboot devices does sometimes come back empty.. just try to do OEM unlock for example.
Click to expand...
Click to collapse
My cable did used to work with adb and fastboot before, and I did unlock the bootloader with it before. I think now the cable got broken
Same issue working cable
Same issue... but my cable is working fine. I have a 2nd OP2 and tried the qualcomm connect with my cable and volume up, and worked perfect. More over, I swapped motherboards and still didnt work. I have access to twrp on the phone and I can get into fastboot. But no way to connect to my pc
hi
While working with the device, it reset without prior warning, and since it trying to start and when the Google logo disappears and the animation stage arrives, 3 seconds later it turns himself off.
I entered into the Recovery mode and cleaned Cash - did not help
I thought to take out the battery in case something might be stuck in my memory but I still have not done it because when I dismantled the small panel (on the part of the camera) I accidentally turned on the device and it showed me that it upgrades the apps, which was a good sign for me so I closed the panel and waited for it to finish The 147 applications. At the end he turned himself off
I did not proceed with the matter of dismantling the battery.
I have the default recovery, I did not install recovery applications that expand the possibilities in the recovery mode.
and i don't remember if i turned on the USB debugging.
I decided to transfer the files (pic's, whtsapp) by ADB befor i try the factory reset
but I get sideload instead of recovery
C: \ adb> adb devices
List of devices attached
R ********** sideload (I changed the stereo to asterisks)
and every command I try to run I get
error: closed
Does anyone have an idea of how to copy files or repair the system ?
thanks
You should be able to bring it to fastboot mode by powering it off, then holding Power, Volume up an Volume down until the robot appears.
From there you should see the device with "fastboot devices". You might need to install some drivers at that point.
When in fastboot you should be able to start TWRP with "fastboot boot twrp-3.1.1-0-manta.img". When in TWRP you can see /sdcard in Windows or you can start Advanced > File Manager and copy your data to a USB stick.
thanks bornheim2
i succeeded to load the TWRP
but when i unplug the USB for plugin the OTG the screen start blinking and the devices turned off.
i have charge the device all night
so my guess is that my battery is bad.
can i use usb a male to usb a male adapter
or Hittime smart 3 in 1 Micro USB OTG/Sync/Charging cable
( i can't put links )
to connect the device with OTG to the computer for power and for transfer data to the computer ?
thanks
[email protected] said:
i succeeded to load the TWRP
but when i unplug the USB for plugin the OTG the screen start blinking and the devices turned off.
i have charge the device all night so my guess is that my battery is bad.
Click to expand...
Click to collapse
You should see the device in Windows when TWRP is running (and the device is charged by the PC). That should be enough to save your files.
i don't see it on windows (computer)
[email protected] said:
i don't see it on windows (computer)
Click to expand...
Click to collapse
That might be a driver problem. Do you see it in Device Manager on Windows? Probably with a yellow triangle?
it's good in the devices manager "Android Bootloader Interface"
but after the TWRP it upload, the devices no longer appears in the device manager
and the screen is still blinking
when i run the "fastboot boot twrp-3.1.1-0-manta.img"
it turn in the device manager to "Android ADB recovery interface" and after 1 sec is disconnect
Tried miui 12 and after flashing rom the twrp is gone I tried to reflash it the same way I did first but sadly when I'm on fastboot PC can't detect it. also tried it with other softwares but same result. Device is fine and responds when open but not in fastboot mode. Currently running miui 11 .0.6 China stable. Stucked. Also all drivers are updated
Same here.
I accidentally flashed china stable 11.0.4 zip rom on my global device through twrp and upon booting up twrp was gone and when i plug in usb the pc doesn't detect anything. In order to make pc detect the phone via usb cable i have to reboot phone while plugging usb to laptop that way file transfer option shows up in laptop and adb works but fastboot doesn't work i can force boot to fastboot through adb but upon booting to fastboot the pc stucks at waiting for device. All the drivers are installed
Currently on china stable 11.0.6
Same issue indeed
That's exactly what's happening right now. I hope someone can help us
Quote me if u find any luck.
Same issues
That happens me sometimes. I only reboot the device into fastboot again, reboot the computer, and that it. This may change depending on your computer CPU, mine is AMD. And ussually I have to use a 2.0 USB or if it still does not work a USB 2.0 hub. I know the hub thing is strange but it worked for me when my pc does not detect the phone in fastboot. Hope it helps .
With my PC I have to open device manager, look for the device, usually has a yellow sign next to it. Right click on the device name, click update driver, click browse my computer for driver software, click let me pick from a list of available drivers on my computer and pick mtp USB device. Then I read it. I hope this helps.
daniml3 said:
That happens me sometimes. I only reboot the device into fastboot again, reboot the computer, and that it. This may change depending on your computer CPU, mine is AMD. And ussually I have to use a 2.0 USB or if it still does not work a USB 2.0 hub. I know the hub thing is strange but it worked for me when my pc does not detect the phone in fastboot. Hope it helps .
Click to expand...
Click to collapse
What hub?
Tried with multiple pcs with no success
epicblue8 said:
What hub?
Tried with multiple pcs with no success
Click to expand...
Click to collapse
I use a usb hub that is very old i guess, as it uses MiniUSB. By the way with multiple computer it should work, your error is very strange, I never saw it. A thing that may work is trying to use fastboot on a Linux system (no, with VMs no). So if you can flash a pen drive with a Ubuntu ISO or any linux distro, boot linux,install fastboot and check if it detects your phone.
daniml3 said:
I use a usb hub that is very old i guess, as it uses MiniUSB. By the way with multiple computer it should work, your error is very strange, I never saw it. A thing that may work is trying to use fastboot on a Linux system (no, with VMs no). So if you can flash a pen drive with a Ubuntu ISO or any linux distro, boot linux,install fastboot and check if it detects your phone.
Click to expand...
Click to collapse
Read my 1st reply to this op
Even file transfer option doesn't show up if i connect my phone via usb to laptop.
In order to make pc show file transfer option i have to reboot phone while connecting the phone to pc so.
That way i can use adb but as soon as i boot to fastboot via cmd pc doesn't detect the fastboot mode.
Tried with 3 laptops
Issue Fixed
epicblue8 said:
Same here.
I accidentally flashed china stable 11.0.4 zip rom on my global device through twrp and upon booting up twrp was gone and when i plug in usb the pc doesn't detect anything. In order to make pc detect the phone via usb cable i have to reboot phone while plugging usb to laptop that way file transfer option shows up in laptop and adb works but fastboot doesn't work i can force boot to fastboot through adb but upon booting to fastboot the pc stucks at waiting for device. All the drivers are installed
Currently on china stable 11.0.6
Click to expand...
Click to collapse
Dude I fixed it and I managed to flash global and maybe reflash EU when miui 12 stable arrive
Try another type c cord preferable the original one. I just change the cord and everything went fine fastboot can now be detected via "fastboot devices".
Chipotle crackers said:
Dude I fixed it and I managed to flash global and maybe reflash EU when miui 12 stable arrive
Try another type c cord preferable the original one. I just change the cord and everything went fine fastboot can now be detected via "fastboot devices".
Click to expand...
Click to collapse
Not with original but tried 3 type c cables and 3 pcs
epicblue8 said:
Quote me if u find any luck.
Click to expand...
Click to collapse
hey have find any solutions? we have the same problem
The Hisense 4K ATV4 runs Android 9 Pie. I got into Developer Options and enabled ADB. Unfortunately, the bootoader isn't unlockable, but I think that you might be able to root it using KingoRoot, or even install apps from ADB.
Specs:
Storage: 4 GB
RAM: 1 GB
Processor: ARM Cortex A55
Same problem, my tv is not unlockable. It goes all black when i run "adb reboot bootloader", I can not find OEM
Unlock option under Developer Options!
jerrydevis said:
Same problem, my tv is not unlockable. It goes all black when i run "adb reboot bootloader", I can not find OEM
Unlock option under Developer Options!
Click to expand...
Click to collapse
if you use mtkclient does it unlock?
$cronos_ said:
if you use mtkclient does it unlock?
Click to expand...
Click to collapse
Nope,I can not boot into fastboot mode! It only restarts the TV!
U can unlock it, my Hisense 43A6H is unlocked. After u get a usb male to male type a cable hook it up only 1 port communicates with the tv on my tv. Find out which one it is and it may require a reboot of the tv to get communication via adb initially then adb reboot bootloader then it reboots go to device manager install the bootloader interface driver for the device that shows up. Then run fastboot flashing unlock. That's as far as I have gotten, so do a fastboot reboot.
That's as far as I have gotten, I haven't been able to root it. I have the boot.img and i patched it with a lot of magisk versions and flashed to fastboot flash boot_b boot.img as fastboot flash boot boot.img & fastboot flash boot_a boot.img both basically brick the tv.
Before u continue call up Hisense and get your firmware and to recover rename the file from
usb_9612us_no_tvcertificate_user.pkg
to
usb_9612us_no_tvcertificate.pkg
Place the file only in the root of the fat32 flash drive unplug the tv and plug in the flash drive into ideally the port that communicates with the pc and hold power on the remote and plug in the tv... It will begin to recover the Hisense tv.
chris1892006 said:
U can unlock it, my Hisense 43A6H is unlocked. After u get a usb male to male type a cable hook it up only 1 port communicates with the tv on my tv. Find out which one it is and it may require a reboot of the tv to get communication via adb initially then adb reboot bootloader then it reboots go to device manager install the bootloader interface driver for the device that shows up. Then run fastboot flashing unlock. That's as far as I have gotten, so do a fastboot reboot.
That's as far as I have gotten, I haven't been able to root it. I have the boot.img and i patched it with a lot of magisk versions and flashed to fastboot flash boot_b boot.img as fastboot flash boot boot.img & fastboot flash boot_a boot.img both basically brick the tv.
Before u continue call up Hisense and get your firmware and to recover rename the file from
usb_9612us_no_tvcertificate_user.pkg
to
usb_9612us_no_tvcertificate.pkg
Place the file only in the root of the fat32 flash drive unplug the tv and plug in the flash drive into ideally the port that communicates with the pc and hold power on the remote and plug in the tv... It will begin to recover the Hisense tv.
Click to expand...
Click to collapse
I've tried 7-8 times running "adb reboot bootloader" with different ports, It goes all black and in PC's device manager, there's nothing!
if you want root privileges you can try connecting to shell via UART, I've heard that you'll be directly provided with root privileges on some hisense tv!
@jerrydevis Hi thx for the reply yes adb reboot bootloader goes to a black screen, thats the bootloader interface of Hisense. Test out different USB ports for detection, use your headphones if needed and make sure u hear the ding. I had a hard time getting my tv to connect hundreds of times of testing until I got it down. On my tv there are 2x usb 2.0 ports, 1 of which communicates with the tv which is the one furthest from the screen in the back, not the one closest to the screen as they are stacked usb ports. If you need some pics to help, I can help.
I left the fastboot driver I have had tremendous success with. For general adb access use the adb-setup.1.4.3.exe to install the general google driver for adb composite interface or whatever its called... lol
Let's Team Up & Root Our TVs Together!
chris1892006 said:
@jerrydevis Hi thx for the reply yes adb reboot bootloader goes to a black screen, thats the bootloader interface of Hisense. Test out different USB ports for detection, use your headphones if needed and make sure u hear the ding. I had a hard time getting my tv to connect hundreds of times of testing until I got it down. On my tv there are 2x usb 2.0 ports, 1 of which communicates with the tv which is the one furthest from the screen in the back, not the one closest to the screen as they are stacked usb ports. If you need some pics to help, I can help.
I left the fastboot driver I have had tremendous success with. For general adb access use the adb-setup.1.4.3.exe to install the general google driver for adb composite interface or whatever its called... lol
Let's Team Up & Root Our TVs Together!
Click to expand...
Click to collapse
Thnx for amazing guidance & necessary files, I'll try it and let you know very very soon!
chris1892006 said:
@jerrydevis Hi thx for the reply yes adb reboot bootloader goes to a black screen, thats the bootloader interface of Hisense. Test out different USB ports for detection, use your headphones if needed and make sure u hear the ding. I had a hard time getting my tv to connect hundreds of times of testing until I got it down. On my tv there are 2x usb 2.0 ports, 1 of which communicates with the tv which is the one furthest from the screen in the back, not the one closest to the screen as they are stacked usb ports. If you need some pics to help, I can help.
I left the fastboot driver I have had tremendous success with. For general adb access use the adb-setup.1.4.3.exe to install the general google driver for adb composite interface or whatever its called... lol
Let's Team Up & Root Our TVs Together!
Click to expand...
Click to collapse
Any way to get through this?
Edit: Done Successfully after restarting TV.
Great job buddy so did u unlock it?
Yes, I did
Great job. Hopefully @theydream has time to help us all out. Good luck all! theydream determined I & possibly we have A/B partition scheme i think is the right terminology. So I tried this command but no dice. I patched my boot.img with almost all magisk & even a modded magisk and all no dice.
fastboot flash boot_b boot.img
Click to expand...
Click to collapse
Hello. I have managed to unlock the Hisense U8G bootloader in the stupidest of ways. This will likely also work on the U6G, U7G, and U9G (Android TV models ONLY) since they run the same firmware. This will probably also work on every other Hisense Android TV.
So... tl;dr just run "fastboot flashing unlock" and that's it. No need to enable OEM Unlocking in Developer settings or anything since there is no FRP.
You will need:
A computer with adb and fastboot installed
Mediatek drivers if running Windows
udev rules if running Linux (available here: https://github.com/bkerler/mtkclient/tree/main/Setup/Linux)
Step-by-step on a stock TV OS (YOUR DATA WILL BE ERASED):
Enable Developer Settings by clicking on build number 7 times, standard stuff
Enable USB Debugging (this will also enable network debugging, but you will not need it)
That's all you need to do on the TV itself, settings-wise.
On the PC:
adb devices
On the TV:
Allow USB Debugging
On the PC:
adb reboot bootloader
fastboot flashing unlock
fastboot reboot
That's it. Your bootloader is now unlocked.
I am currently trying to figure out a way to dump boot.img and vbmeta.img and/or get into BROM mode so I can use mtkclient to dump boot.img and vbmeta.img. Help would be appreciated.
Hey. Do you know how to unlock bootloader of Hisense 50A71F, it goes all black when I run "adb reboot bootloader".
jerrydevis said:
Hey. Do you know how to unlock bootloader of Hisense 50A71F, it goes all black when I run "adb reboot bootloader".
Click to expand...
Click to collapse
Thats normal, need a usb type a male to male plugged into 1 of the ports of your tv only 1 port gets detected and other not so ask me for the adb bootloader interface driver for the tv and ill provide, I have a Hisense 43A6H its a MEDIATEK MT9612 SoC which I unlocked the bootloader and cannot root it as I have all the drivers and boot.img and I patched it and typed command and on my tv and likely yours is the same command in slot B but it didn't root the tv...... Anyone know of an alternative method to patch and flash the boot.img? Mtkclient gui might work with python but idk haven't tried yet... Make sure to get the latest firmware from hisense so u can recover if u do something wrong or want to relock the bootloader.
To recover take your .pkg file which for me is update_no_tvcertificate_user.pkg and rename to update_no_tvcertificate.pkg and have only that file on your fat32 flash drive and unplug the tv plug in the flash drive and hold power button on remote pointing at tv and plug in the tv and it'll start recovering and u can let go of the power button.
Code:
fastboot flash boot_b boot.img
Don't freak out if you brick your tv make sure before u do anything to call up Hisense to get your firmware and they will email it to you. I bricked my tv like 3 times but recovered it and im talking to u now on my Hisense 43A6H Google TV Android 11 with a mini wireless keyboard mouse usb 2.4ghz dongle plugged into a usb hub by Sabrent with a 4tb hdd ntfs plugged in and a 400gb sd card fat32 it detects everything. I was gonna make a guide on how to do stuff on our tvs as well its tricky but fun when u succeed.
I've been having a hard time rooting the tv. Nothing takes, may someone help?
chris1892006 said:
Don't freak out if you brick your tv make sure before u do anything to call up Hisense to get your firmware and they will email it to you. I bricked my tv like 3 times but recovered it and im talking to u now on my Hisense 43A6H Google TV Android 11 with a mini wireless keyboard mouse usb 2.4ghz dongle plugged into a usb hub by Sabrent with a 4tb hdd ntfs plugged in and a 400gb sd card fat32 it detects everything. I was gonna make a guide on how to do stuff on our tvs as well its tricky but fun when u succeed.
Click to expand...
Click to collapse
I would be thrilled if I could just get my Hisense to default to HDMI1 input upon startup, like you can with other SmartTVs.
Have a 65H6510G with a failed eMMC. Service port UART shows CPU trying to setup eMMC to retrieve data, fails and repeats. I can replace eMMC but need to flash in signed boot code. Any ideas?