Hi,
Im hoping someone can help me, I have been given a OEM tablet from where I work. I think its an unbranded Coby Kryos 7022, this the closest resembulance.
I installed clockworkmod from the android store to backup the rom, but when I rebooted, the clockmod loaded (IMG 1) and doesnt allow me to do anything, if i select reboot the device reboots back the clockworkmod. So Im stuck in this loop. Clockwork also wont mount the sdcard.
I have the Android SDK installed and followed a guide to replace the recovery.img but when it comes to replacing it i get error -1, im also unable to su in adb shell....
I did manage to get the device in to fastboot i think. As the screen was black and windows tried to load drivers but was unable to find them.
I have tried adb devices but get waiting for devices and fastboot devices and get nothing. I'm guessing i haven't got the right drivers for this device in whatever state its currently in. I have tried googles android composite adb driver with no success.
any help is appreciated
unable to post image
Hi, This is the first time i am having this problem, i previously had a CM 11S ROM and wanted to change and try liquid smooth ROM, so i went into recovery and did a clean wipe and cleared all data then i went into ADB sideload to sideload the rom and flash it and it says error: device not found.
When i go into bootloader and do fastboot devices, i can see my device so i thought it must be an error with my recovery and i flashed the new TWRP recovery v2.7.1.1 and again did fastboot in bootloader and device is seen but when i get into recovery and try to sideload i get the same message of error device not found.
What could be the issue here?
If i had example ADB off in the ROM, is there a way of turning it back on? I've already clean wiped everything so i had no ROM installed, any other way of turning it on, think maybe that could be the issue?
Thanks in advance.
EDIT:
So i updated my SDK and i download Stock Image from Google and flashed it via fastboot and the phone booted, i turned on adb and went back into recovery and i was able to sideload the custom ROM i wanted, so either the problem was with my SDK or because maybe ADB wasn't ticked in my old ROM, but problem is solved.
Thanks.
Could be a driver issue?
Try to kill and relaunch adb server.
Did u update the SDK? Check your path for adb.exe.
Shiestie said:
Could be a driver issue?
Click to expand...
Click to collapse
I've always used the same laptop and USB port
Haven't updated my SDK and i even restarted my laptop
EDIT:
Lemme try updating my SDK and try again
For some reason I cant get TWRP to show my device using adb commands, which is making it impossible to adb push a rom.zip to storage. Everytime i run the adb push command i get "error: device '(null)' not found"
In bootloader, the fastboot devices command shows my device, in android adb devices shows my device also.
Ive installed and uninstalled the motorola driver numerous times and i also tried a universal adb driver. Im running windows 10 64bit, Device manager picks up my device fine when in android and in bootloader, but in twrp device manager shows a yellow exclamation under "other devices, android"
well heres the resolution to the issue...
heres what it wasnt
-tried on a fresh install of windows 7=no go
tried different drivers=no go
tried different versions of twrp=no go
The problem, it appears, was TWRP
The solution was to install Philz recovery, once this was installed i had no further issues with the device showing up in recovery using "adb devices" and consequently adb push works just fine now
TWRP ADB does work with Linux - no drivers required. It has however, always been a tricky affair when it comes to Windows.
lost101 said:
TWRP ADB does work with Linux - no drivers required. It has however, always been a tricky affair when it comes to Windows.
Click to expand...
Click to collapse
twrp has never been tricky with my samsung or HTC phones, i guess i just have to get use to all the quirks with motorola phones
Hi, I've deleted all storage from my device and all I've got now is TWRP recovery.
I', trying to push a rom through fastboot but my PC won't recognize my device, I have Universal ADB Drivers intalled, also I've got Samsung ADB drivers istalled, and Android SDK installed; yet my device won't show up when I'm in fastboot and typing 'adb devices'.
Obviously I cannot turn Debugging on since I don't have a system.
so...
what CAN I do?
thanks
Lidor167 said:
Hi, I've deleted all storage from my device and all I've got now is TWRP recovery.
I', trying to push a rom through fastboot but my PC won't recognize my device, I have Universal ADB Drivers intalled, also I've got Samsung ADB drivers istalled, and Android SDK installed; yet my device won't show up when I'm in fastboot and typing 'adb devices'.
Obviously I cannot turn Debugging on since I don't have a system.
so...
what CAN I do?
thanks
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2788632
Use drivers and setup from this guide.
hi guys,
i my shield is stuck on the nvidia logo when booting normally, if it brings up the bootloader, it shows unlocked but hitting continue caused it to freeze on the screen, recovery freezes on nvidia logo and fastboot protocol just brings it back to this screen. i orginally installed twrp and it confirmed successful flash of new os .... on reboot it bricked to its now state, i cant get into twrp or get my pc to see it to install a new copy
anyone got any ideas
thanks
@Fairmax don't click continue, it freezes because there is nothing to continue to, as long as you can enter bootloader your device isn't fully bricked. So, to fix your problem you will have to download official ROM from nvidia's site (https://developer.nvidia.com/shield-open-source find your model and click recovery images).
When you download latest ROM unzip it and follow the textual guide, but, there will be one file missing (i can't remember which one, user data maybe or something like that), don't worry and just continue with the next step. After you flash just reboot to system by holding power button. Good luck !
i cant seem to get it to be recognised by windows all i get is this-- Windows has stopped this device because it has reported problems. (Code 43) A request for the USB device descriptor failed.--
trying to install nvidia usb driver via have disk bring up an error that the file is not usable with x64 system
ok after many driver reinstall iv got device manager to say android adb interface but still not showing on on device list in cmd
Fairmax said:
ok after many driver reinstall iv got device manager to say android adb interface but still not showing on on device list in cmd
Click to expand...
Click to collapse
Which command did you type in?
fpozar said:
Which command did you type in?
Click to expand...
Click to collapse
adb devices shows no devices
i tried the 3 different option in the driver install which was android adb, bootloader, and something else and nothing shows in devices. i tried it on my laptop and a different cable and cant get adb to list the device :crying:
Fairmax said:
adb devices shows no devices
i tried the 3 different option in the driver install which was android adb, bootloader, and something else and nothing shows in devices. i tried it on my laptop and a different cable and cant get adb to list the device :crying:
Click to expand...
Click to collapse
Well of course adb devices shows no devices because you are not actually in adb mode, you are in the bootloader mode. Just download minimal fastboot and adb, install it and extract recovery image into the folder where you installed minimal adb and fastboot (you don't need any other drivers).After you did this and your device is in bootloader and connected, click on the path in your fastboot & adb folder and delete everything and type cmd. No need to do adb devices, just proceed with fastboot flash ...
fpozar said:
Well of course adb devices shows no devices because you are not actually in adb mode, you are in the bootloader mode. Just download minimal fastboot and adb, install it and extract recovery image into the folder where you installed minimal adb and fastboot (you don't need any other drivers).After you did this and your device is in bootloader and connected, click on the path in your fastboot & adb folder and delete everything and type cmd. No need to do adb devices, just proceed with fastboot flash ...
Click to expand...
Click to collapse
ah now that makes sence....silly me i dont do this very often . so fastboot saw device and iv uploaded all parts of the recovery image and rebooted but it is still stuck on the nvidia logo, that was the original file so now il try 5.2.0 and see if that works
Fairmax said:
ah now that makes sence....silly me i dont do this very often . so fastboot saw device and iv uploaded all parts of the recovery image and rebooted but it is still stuck on the nvidia logo, that was the original file so now il try 5.2.0 and see if that works
Click to expand...
Click to collapse
You can also try flashing twrp and then lineageos or something from twrp.
fpozar said:
You can also try flashing twrp and then lineageos or something from twrp.
Click to expand...
Click to collapse
good news after a few hours of trying (usb dropped connection a few times then battery died) it finally works again .....been over 2 years since iv had this shield running after nvidia did the recall , now goto put a different rom on there so it dosnt update and kill itself
Hello I had a similar issue with my k1 tablet and ended up flashing factory images via adb fastboot and all flashed fine. Now my tablet is stuck on the boot screen with the green and white nvidia logo. How long does it take to boot please?
I have same issue too. I can load TWRP and flash the other partitions but TWRP shows un-mountable partitions and even a full stock ROM flash will not allow it to boot. I have a similar issue with a recall tablet. what did you do to fix it?