Database Users

Issues

I'm trying to flash this device with the NVFlash method, but every time I try to install the drivers, I get:
NVIDIA USB Boot-recovery driver for Mobile devices
Any ideas why my tablet keeps doing this while in the APX mode?
Really would like to get this device upgraded to at least ISC. Is there any other, easier method?
EDIT: Also, I am trying to come from stock.

most tablet has locked bootloader, so nvflash isn't working anyway

quyTam said:
most tablet has locked bootloader, so nvflash isn't working anyway
Click to expand...
Click to collapse
So then how do I get a updated OS onto the device?
I've read through all the forums I could find, and I think my problem with doing the nvflash method is that I can't do this part:
1. The USB cable to connect your tablet to a PC (Yes, you will need a PC)
2. Your battery should be charged to 100%
3. You must have these drivers installed on your PC.
/devs/khanning/k1/K1_APX_Drivers.zip[Nvflash Windows Drivers]
md5sum: 9aa3a4814ca63366329d85a22ed01f64
because I can't find the drivers I need to install, does anyone know where I can find these files?
(Trying to use the method found at the Lenovo forums, would post link if I could)

sslater said:
So then how do I get a updated OS onto the device?
I've read through all the forums I could find, and I think my problem with doing the nvflash method is that I can't do this part:
1. The USB cable to connect your tablet to a PC (Yes, you will need a PC)
2. Your battery should be charged to 100%
3. You must have these drivers installed on your PC.
/devs/khanning/k1/K1_APX_Drivers.zip[Nvflash Windows Drivers]
md5sum: 9aa3a4814ca63366329d85a22ed01f64
because I can't find the drivers I need to install, does anyone know where I can find these files?
(Trying to use the method found at the Lenovo forums, would post link if I could)
Click to expand...
Click to collapse
The link is dead :crying: please reupload

[Q] Bricked Updating to CM11

Hey guys any help or suggestions will be greatly appreciated on this matter. I will try to be as detailed as possible but I'm trying to fix this phone for a friend and he isn't very phone savvy. From what I understand, he was previously on CM10 and tried updating to CM11 using the cmupdater. For some reason it failed and he was stuck in TWRP. When he tried to reboot it kept kicking him back to recovery. He took his phone to a phone repair shop who then wiped his device. At this point he gave me the phone to try to fix.
First of all I have working fastboot and adb drivers for my Nexus 5 so I don't think this is a driver issue but I'm no expert on the Nexus 4 so I could be wrong. I'm also running Windows 8.1 if this is any relevance.
I can still access the devices bootloader (ver MAKOZ20i)
I can still access TWRP (ver 2.6.0.0)
When plugging the device into my USB 2.0 ports, nothing shows up in my device manager in bootloader, TWRP, or TWRP ADB sideload.
When plugging the device into my USB 3.0 ports, I see 'Unknown USB Device (Device Descriptor Request Failed)' and the Device Instance Path is 'USB\VID_0000&PID_0002\7&20F39B9B&0&2' in bootloader, TWRP, or TWRP ADB sideload.
I've never heard of a device not being seen at all in by USB 2.0 ports but showing using USB 3.0 ports so I attempted to give extra juice to the phone using a powered USB OTG cable. Still nothing shows up.
I've tried running 'fastboot device' and 'adb devices' with no luck.
I think I've covered all the bases... can anyone think of anything that could help me re-install a new rom or factory reset or his he out of luck?

I think it may be a Win8 problem. You have access to another machine with Win7 or WinXP?

Install "universal driver.exe" in win7, than connect phone while power off, I think it'll install driver...than push any custom ROM to phone via adb or just flash any official IMG..

Well I can tell you WHY it didn't work. That version of TWRP is not able to install 4.4 (CM11). if you manage to successfully push via adb and get it started again, make sure to flash the newest version of TWRP before trying that again.

Thanks for the reply guys. I kind of guessed that the version of TWRP was not compatible as I installed CM11 on my old Nook Tablet and had to update my recovery before installing it. Unfortunately the guys who wiped the phone prevented me from installing an old version of CM10 that my friend probably had from the cmupdater.
As for Windows 8 being the issue.. I attempted to try to use my laptop which runs Windows 7 but was unable to get anything to happen. Since the laptop only had USB 2.0 ports, plugging in the device to any of the ports did the exact same thing as what it did on my desktop (Windows doesn't even recognize anything is connected). I still get the charge animation on the phone but yea... nothing in device manager. I'm thinking of running Linux from a live installation to see if anything different happens, unfortunately its been ages since I've touched Linux so this is kind of a last ditch effort here.
Any other thoughts?

mrlazyone said:
Thanks for the reply guys. I kind of guessed that the version of TWRP was not compatible as I installed CM11 on my old Nook Tablet and had to update my recovery before installing it. Unfortunately the guys who wiped the phone prevented me from installing an old version of CM10 that my friend probably had from the cmupdater.
As for Windows 8 being the issue.. I attempted to try to use my laptop which runs Windows 7 but was unable to get anything to happen. Since the laptop only had USB 2.0 ports, plugging in the device to any of the ports did the exact same thing as what it did on my desktop (Windows doesn't even recognize anything is connected). I still get the charge animation on the phone but yea... nothing in device manager. I'm thinking of running Linux from a live installation to see if anything different happens, unfortunately its been ages since I've touched Linux so this is kind of a last ditch effort here.
Any other thoughts?
Click to expand...
Click to collapse
One more, when you plug into usb 3.0 you can see unknown device Right ??
If yes, download driver files from here Here.
It's a zip contains .inf files, Now click on unknown device and select update drivers then give the path to these drivers manually.
Hope this will help you out.

I'm pretty convinced at this point that the phone can't be fixed by me. Running it through Ubuntu I can't see the device at all (USB 2 & 3) when running the lsusb command but it sees my nexus 5 just fine. I even tried modifying drivers to match vendor id product id and class id as reported by windows. Thanks for the suggestions. Does anyone know of a reputable service to get this phone repaired? How much does a JTAG repair usually cost?
Sent from my Nexus 5 using XDA Premium 4 mobile app

mrlazyone said:
I'm pretty convinced at this point that the phone can't be fixed by me. Running it through Ubuntu I can't see the device at all (USB 2 & 3) when running the lsusb command but it sees my nexus 5 just fine. I even tried modifying drivers to match vendor id product id and class id as reported by windows. Thanks for the suggestions. Does anyone know of a reputable service to get this phone repaired? How much does a JTAG repair usually cost?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The following method may still help
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060

DrFredPhD said:
The following method may still help
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Click to expand...
Click to collapse
Awesome! Didn't realize this was an option. It didn't work using the USB 3.0 ports but the USB 2.0 actually worked for this method. Thank you!

Bricked my 6p and computer wont recognise it

Ok, so i managed to brick my nexus 6p, it will not boot into android, stupid as i am i do not have a backup on the phone, and on top of that, windows does not recognise my device in bootloader mode. Of course i have tried installing USB drivers, but strangely my computer will not even recognise that im plugging in a USB device, i/e it wont even make the USB connected sound.
Not really sure what to do, but im hoping anyone could maybe help me out, thanks!

axeeeel said:
Ok, so i managed to brick my nexus 6p, it will not boot into android, stupid as i am i do not have a backup on the phone, and on top of that, windows does not recognise my device in bootloader mode. Of course i have tried installing USB drivers, but strangely my computer will not even recognise that im plugging in a USB device, i/e it wont even make the USB connected sound.
Not really sure what to do, but im hoping anyone could maybe help me out, thanks!
Click to expand...
Click to collapse
How did you brick it? What drivers are you using?

Heisenberg said:
How did you brick it? What drivers are you using?
Click to expand...
Click to collapse
I tried to install franco kernel on my chroma rom, and it just wouldn't boot.
Also, I am using the drivers installed by the unified android toolkit.

axeeeel said:
I tried to install franco kernel on my chroma rom, and it just wouldn't boot.
Also, I am using the drivers installed by the unified android toolkit.
Click to expand...
Click to collapse
Do you still have the Chroma zip on your phone? I'm guessing not, but if you do just flash that. You could try uninstalling the drivers that you currently have and installing the drivers from the Android SDK. I have a link to the SDK download page and instructions on how to install it in my guide. Otherwise, do you have access to a Linux machine? No drivers required for Linux, you just need to install the Android SDK and adb and fastboot should work out of the box so to speak. Or if you don't have access to a Linux machine you could even create a bootable Linux usb and do it that way.

Heisenberg said:
Do you still have the Chroma zip on your phone? I'm guessing not, but if you do just flash that. You could try uninstalling the drivers that you currently have and installing the drivers from the Android SDK. I have a link to the SDK download page and instructions on how to install it in my guide. Otherwise, do you have access to a Linux machine? No drivers required for Linux, you just need to install the Android SDK and adb and fastboot should work out of the box so to speak. Or if you don't have access to a Linux machine you could even create a bootable Linux usb and do it that way.
Click to expand...
Click to collapse
I just came back home from buying a new USB cable, and apparently it was just my cable (original 6p cable) that wasnt working... Terribly sorry for wasting your time, i appreciate it though!

axeeeel said:
I just came back home from buying a new USB cable, and apparently it was just my cable (original 6p cable) that wasnt working... Terribly sorry for wasting your time, i appreciate it though!
Click to expand...
Click to collapse
No problem at all, glad to see you're up and running again.

Updating Yotaphone 2 YD201 ME Build

Dear all, I'm new here and just got my yotaphone 2 today, bought it locally from UAE, i beleive that the build ME refers to Middle East, got an android version of 4.4.3 YD201 model.
I thought that YD201 models are OTA updatable versions but seems not
Please can you guide me in a simple way how to update to lollipop? Noting that I've never flashed or done this before
Thank you so much..

https://forum.xda-developers.com/yo...grade-yotaphone-2yd206-running-4-4-4-t3506293
You can follow this guide fully but you don't need to flash HK first, so you just flash RU 5.0.0 firmware directly.

Caferatte89 said:
https://forum.xda-developers.com/yo...grade-yotaphone-2yd206-running-4-4-4-t3506293
You can follow this guide fully but you don't need to flash HK first, so you just flash RU 5.0.0 firmware directly.
Click to expand...
Click to collapse
Thank you so much.. Totally appreciate that.. But I don't know if it really matters as the tools relates to YD206 while I have YD201.. Should I proceed ?

By the tools do you mean YotaphoneFlasher? It works on both 201 and 206 since it's from official.

Thank you again.. OK I'm all set everything is ready but the only thing that's keeping me is drivers installation... Somehow the Google drive coming with the flasher is not being installed. I tried all ways possible, I.e. right click on the INF file and install but I get error message, and also tried to install it from device manager but couldn't. Can you please help with this? Thanks again
Btw I'm using Windows 7

Would you mind to post the srceenshot so I know your problem?
https://www.youtube.com/watch?v=R3wROHMJBDU This is the video of how you install driver

Caferatte89 said:
Would you mind to post the srceenshot so I know your problem?
https://www.youtube.com/watch?v=R3wROHMJBDU This is the video of how you install driver
Click to expand...
Click to collapse
my dear friend, i managed to update the driver, thanks to you, but it seems that when i power off the phone and enter the "downloading " mode on the phone screen then connect it to the computer it seems the phone is not being connected.. i used the flasher chosed option 1 "flash the cellphone" then i get the message "waiting for device" on the flasher..
i had a screenshot just to show that i have done everything i should (i guess) .. i.e. copied the firmware.. etc,,,
mindyou, i think the problem is that when i conncet the phone to usb it goes under other devices/Android which is not being recognized..
you are the best and thank you for your help again and again!

Weird. Do you've already install both drivers and restart your computer?
If yes, how about try to plug another usb port?

I got both ADB and Qualm drivers installed.. but nothing happening! I tried the 3 usb ports already..
I don't know how to solve this.. I think I need to try it on another computer .. maybe it'll work out!

Your driver not properly install. Try reboot pc, enable usb debugging at phone, plug in usb. See if there is any changes at device manager.
There is yellow triangle. So it mean.. Oh.. Oo..
If stilk not ok. Plug out usb from pc. At device manager, unsinstall both yellow triangle. Plug in back usb. So it will detect device and windows trying to install it.

If you have Windows 10 you have to disable signature driver verification, entering in the advanced boot menu of windows. After that the .inf driver will install.

I got the update at last and it's working beautifully smooth I downloaded universal driver from adbdriver.com and it worked perfectly. Thank you all guys for your help and efforts

[HELP]. Fire HD 8 2018 stuck on "Waiting for bootrom" after root attempt

So long story short, I followed the initial tutorial to root the Fire HD 8 2018 (https://forum.xda-developers.com/hd8-hd10/general/tut-root-hd82018-via-magisk-t3906554/) after getting the mtk-su temp root. I made sure all the codes were correct before powering off my tablet, and everything seemed to be going smoothly until I ran the code on LInux to go into BootRom mode.
That was when the code was stuck on "Waiting for bootrom...". I connected my device to my PC, but the code didn't change at all. The USB also wasn't being recognized by the computer and was randomly being connected and disconnected. I'm not really sure what to do next as nobody else on the thread seemed to have my problem. I am a newbie, so please bare with me .
If anyone does have the solution, I'd be extremely grateful. Thanks in advance!

Is your tablet bricked as required by the guide? Or does it boot/show Amazon or fire logo?
If it is properly bricked, you could try a different USB port or cable.
If all else fails, your best bet is to follow the instructions in the original unlock/debrick thread:
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256

Can you use the transferrable micro USB Cable?

I had the same issue with mine. I was getting the device showing in linux as a "mediatek" phone. When I plugged it, it would randomly connect and disconnect. finally it got recognized, and I ran into the BOOT0 broken issue mentioned elsewhere. I commented the != in the main.py first method to ==, and it flashed twrp correctly.

To avoid stuck in Waiting for bootrom...
Make sure your Fire tablet is shut down
Disable or uninstall the ModemManager
Use the transferrable micro USB cable
To short CLK to GND point using conductive objects. Do Not use the diode, capacitor or resistor to short the test point
USB access is enabled in VirtualBox settings