Database Info

Captivate (stock 2.2) stuck in kernel boot

Need help and I assume I am stuck in a ‘soft brick’ state.
My Captivate does not advance past a kernel flash screen.
Upon boot, I receive the AT&T logo boot animation, then black screen, then with 5 seconds receive the splash screen of the Kernel developer (“Trident”). The phone remains stuck on this screen.
I can, however, initiate download mode and recovery mode (signs of hope).
In download mode I cannot get the device recognized by the multiple PCs I used to access the device by (the USB drivers are on the PC…..as evidenced through its functionality before). Consequently, and SDK / adb and ODIN* is of no help to me as an option to recover the device.
In recovery mode, I can apply sd card zips and have a few available (had several updates, superuser, kernels, etc downloaded prior to this device bricking) to apply. Of the zips available are;
CWM Recovery v3.0.0.5
Voodoo Lagfix
recovery CWM 2.5.1.2
SuperOneClick 1.9.5
ROM Kitchen Froyo ROM
11-254 Trident (Kernel Manager – ytt3r7 )
Click to expand...
Click to collapse
Backup file on device was from the day that the kernel was installed
After applying any of these zips (except the ROM Kitchen file) I will get an abort with the
“E:no misc partition” message.
>>>>>>>>>>>>>>once ROM Kitchen setup is applied it says "successful" then reboot it does the exact same thing as before (sticks in kernel splash screen)
For what its worth, this occurs with no SIM card and no SD card in the device.
*I have successfully used Odin on this device (usb functioning, recognized the device in Odin) and flashed/reset the device prior to this kernel problem.
** the reason I am in this position was because after receiving a warranty replacement (in stock 2.2 Froyo) I received the signature verification error. No amount of sidestepping this worked (I’ve read every page of the guides for this issue and they did not work) so I figured the easiest way around it was simply to replace the kernel (it wasn’t the bootloaders giving me errors). The phone was rooted, had superuser permissions, just could not apply any ROMs because of the sig verification.
To get a kernel to load (ROM manager / recovery mode zips did not work), I figured I would use market apps for this. I downloaded “Kernel Manager” from the market and applied the only kernel available (“Trident”). Once it applied the kernel, it left me stuck in the current stat I’m in.
*** I have read all previous "stuck in boot" threads and none of them have ANY troubleshooting methods available.

Just for clarification before further troubleshooting, you are putting the phone in download mode unconnected from the computer, starting up Odin, then connecting, correct? The only reason I ask is that I had some trouble with the computer seeing my messed up phone when I connected it prior to opening Odin.

correct - though, I've tried it in every sequence....ODIN (PC itself) doesn't see any USB device.
If I could get ODIN to recognize the device, I could wipe the phone and start over.
I guess my question is two-fold.
FIRST - Is it a correct assumption that this device is recoverable (not complete brick)?
SECOND - is there any way to fix the kernel loop from recovery mode?

1. I would assume yes, as you have activity from the phone.
2. Possibly. Hopefully you backed up (or don't care about) your apps, because most solutions at this point have a good chance of losing them. Also, from recovery, the first thing I'd do is a nandroid backup.
If you haven't tried this already, see if you can get Odin to recognize your phone while it's at the boot loop.
Next step would be trying to flash a kernel like Onix. You can do this one from CWM, so there's a chance it could fix your phone.
If that doesn't work, you could to grab a custom rom with a full wipe package (Firefly, for example) and see if you can run that from CWM. As it contains a kernel as part of the package, there is a chance you would be able to get your phone functional again.
I can't guarantee any of these methods, but they might help.

so - likely recoverable IF ODIN can recognize the device
BECAUSE there would be no other way to put the other kernels on the device (if you can't get the OS to load {past the kernel loop}
IF ODIN can recognize the device;
1. wipe/clear the device
2. load a different kernel through ODIN.
or is there another to load a kernel without ODIN?

Actually, from CWM recovery you can flash kernels (like the Onix one). Use the method you used before to get back there (holding V+/V-/power, i'm guessing), and assuming you have a way to get files to and from your micro SD card, just copy the onix kernel to your sd card and put it in your phone.
To flash the kernel, from the recovery menu select the "install zip from sd card" option, then "choose zip from sd card", and then navigate to where you saved it.
Assuming all goes well, it will overwrite the Trident kernel, and since Onix claims to work with stock roms, you should be back up and running.

jmtheiss said:
get files to and from your micro SD card, just copy the onix kernel to your sd card and put it in your phone. .
Click to expand...
Click to collapse
duh! (oy) that was genius....gawd, I can't believe I didn't even consider that.
T-H-A-N-K-S
I will try this

Ragin Caucasian said:
duh! (oy) that was genius....gawd, I can't believe I didn't even consider that.
T-H-A-N-K-S
I will try this
Click to expand...
Click to collapse
No problem. We all have those forest-for-the-trees moments.
Just as a heads-up, the onix kernel will be an intermediate step to a more final solution. The reason I say this is that it's based on I9000 source, so you would either need to flash an I9000 modem, or flash back to stock (overwriting the onix kernel). Either way wouldn't be difficult, but just something to remember.

i thank you for the feedback/help. This should work, unfortunately, it doesn't.
When attempting to load zip from sd-ext I get
E:no misc partition
Click to expand...
Click to collapse
when mounting the "/sd-ext" from CWM, I get
"E:failed to mount /sd-ext (no such file or directory)
Error mountin /sd-ext!
Click to expand...
Click to collapse
even if I attempt to format the /sd-ext, I get
Formatting /sd-ext...
E:format_volume: make_extf4fs failed on /dev/block/mmblk1p2
Error formatting /sd-ext!
Click to expand...
Click to collapse
So I'm stuck / dependent on ODIN (correct)?

Hmm.. oddly enough, I can't get the mount /sd-ext on my phone to work either (same message). Odin is looking like it might be your only option right now, but we can try a few more things.
I know it's a long shot, but have you tried the "mount USB storage" option on that page and seeing if your computer recognizes that?
Also, do the "wipe cache partition" from the top-level menu, and "wipe dalvik cache" from the advanced menu. Once you've done those, retry earlier steps and see if any of those clear things up.
Just out of curiousity, what version/versions of Odin have you tried?

jmtheiss said:
Hmm.. oddly enough, I can't get the mount /sd-ext on my phone to work either (same message). Odin is looking like it might be your only option right now, but we can try a few more things.
I know it's a long shot, but have you tried the "mount USB storage" option on that page and seeing if your computer recognizes that?
Also, do the "wipe cache partition" from the top-level menu, and "wipe dalvik cache" from the advanced menu. Once you've done those, retry earlier steps and see if any of those clear things up.
Just out of curiousity, what version/versions of Odin have you tried?
Click to expand...
Click to collapse
The sd/ext won't work unless you have an ext partition on your SD card.

Have you tried re installing your drivers?
If you can get to DL mode your comp. should recognize your phone.

I dunno.....
I've tried 2 different PCs (win7....32 and 64 bit environment) neither recognize the device. I keep getting the
E: no misc partition
Click to expand...
Click to collapse
anytime I doing anything with the sdcard (internal / external)
I've been using Odin3 (which is what I used to flash it originally)
Like I said, I can boot into Recovery Mode (get the internal menu) or boot into Download Mode (yellow sign 'downloading....do not turn off target!") but I don't think this really is doing anything because the PC never recognizes it and I can get into this mode whether I'm connected to a PC or not.
When I attempt to run Heimdall it runs and immediately crashes. This is what it displays
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Heimdal Front end 1.1 used to work, but since the device isn't recognized, like ODIN nothing is presented to the application
I'm stumped. I just received this last Friday as a warranty replacement, I have 3 batteries and 2 usb cords, a rubber sleeve for the device willing to sell it all for $50 if anyone wants it.

Is the odin3 you're trying the one-click back to stock? Have you tried Heimdall? What version number shows up when you open it?
I used Odin3 v1.70 with my phone and had good luck. If you're using an earlier one, try using that one. If you're using v1.70, try an earlier version.
And to reiterate the earlier post, if you haven't tried uninstalling and reinstalling the drivers on your pc, that's worth a shot, too.

That dialog you're seeing with adb looks a lot like what happens if you run it without any arguments. Are you doing anything like "adb devices" or "adb reboot recovery"?

awesome!
Good news.....ODIN recognized the device
bad news......completely soft bricked the phone
I got the phone-<!>PC image and now the phone won't turn on again. great
I'll try the flux-capacitor jig fix sometime when I don't feel like strangling someone

Actually, you can use odin from the phone--!--pc screen. If you can get back there, try to flash the one click.

UPDATE
Bought the $10 jig (after my homemade resistor jig didn't work) - which works very well, btw.
* Uninstalled the USB drivers - reinstalled the USB drivers
* Used Odin3 1.8
* phone recognized by Odin.
* Flashed bootloader (what was originally wrong with the phone) and even a new ROM
Everything went FINE through Odin (first for me), even got a progress bar on my phone during the operation
now the phone is completely dead.
Will not give me the soft brick image.....can't go into download mode - nothing, completely unresponsive
$50....who wants it? This is a brand new phone just received as a warranty replacement....FOUR 1500m batteries, TWO USB cables, TV-OUT cable, and a rubber protective case

tf101 flashed touch cwm and could not intall driver correctly

1. Turn on xformer with power button - stuck at Asus Eee Pad screen
2. Try to boot into recovery with vol - + power;
- volume up to enter recovery, ded android with an exclamation
- volume down to choose between 'wipe' and 'cold boot' both result in getting stuck at Asus screen
3. Plug in xformer, hold power and vol +; nothing. windows notice found an unknow device but fail to intall the driver
4 i tried many times to manaual install the apx drivers that posted in the bbs, in device manager it always showed as""unknow device"" instead of ""apx device"" , driver installation fail by auto search the apxusb folder liked everybody said
i was able to force install the apx driver by manaul selected the usb.inf fil. however in device manager it said device is not running correctly error.
i try to rebooy laptop ans the error remain
my tf101 is now softbrick with touch cwm. i could not operate with removeable sdcard but internal sdcar.
the worse thing is i dony have any roms storage in internal sdcard
please anyone can give me a hand？

justinmise said:
1. Turn on xformer with power button - stuck at Asus Eee Pad screen
2. Try to boot into recovery with vol - + power;
- volume up to enter recovery, ded android with an exclamation
- volume down to choose between 'wipe' and 'cold boot' both result in getting stuck at Asus screen
3. Plug in xformer, hold power and vol +; nothing. windows notice found an unknow device but fail to intall the driver
4 i tried many times to manaual install the apx drivers that posted in the bbs, in device manager it always showed as""unknow device"" instead of ""apx device"" , driver installation fail by auto search the apxusb folder liked everybody said
i was able to force install the apx driver by manaul selected the usb.inf fil. however in device manager it said device is not running correctly error.
i try to rebooy laptop ans the error remain
my tf101 is now softbrick with touch cwm. i could not operate with removeable sdcard but internal sdcar.
the worse thing is i dony have any roms storage in internal sdcard
please anyone can give me a hand？
Click to expand...
Click to collapse
Further more
When i pressed V+& Power tf101 screen turn off and window found a unregonized device.
But, window only show" unknown device" instead of "APX" Device which yellow A! remark.
Did any one know how to slove this issue, i tried every drivers file i can file in this bbs but none of them work.
thx
justin

Did you install the APX driver?
You can find it with the nvflash package

baseballfanz said:
Did you install the APX driver?
You can find it with the nvflash package
Click to expand...
Click to collapse
hi
thx for ur reply
i tried to install the APX driver but fail
window pop up and said it found a new device and can not recongized.
device manager recongized it as a "UKNOW Device" With out Yellow ! remark.
as i read in other posts it should read as " APX" with yellow remark.
i also try to froce install the driver but fail again.

It means both WINXP and WIN 7 64bit not able to recongized my TF correctly,
device manage keep show " unknow device" but not able to indentity it as a APX device.
what steps am i missing ?

Exact same problem
I am at the same place as this person.
I Booted into CWM Recovery 5.5.0.4 and I can't get back out. I tried wiping. I had an update.zip on my internal SD card. I've tried everything I've seen on the forums. and NOTHING. On windows I get an Unknown Device in both APX and ADB and ADB won't recognize the device. ADB works fine on all of my other android devices. I feel like i've got a 200 door stop. PLEASE HELP!
My device is a B50 TF-101 SBK1
I'll give anyone that can help me solve this $40 through paypal.
Thanks!

Download universal naked driver from easy flash thread.. unzip the drivers into a folder.. Go to device manager in your laptop and look for that unknown device and there double click on unknown device and select update/install driver.. point the installation to the unzipped folders and click update driver and this should install apx drivers and you should be good to go as that's what I did. Its very easy so take your time and do it...
Sent from my Transformer TF101 using xda app-developers app

udupa82 said:
Download universal naked driver from easy flash thread.. unzip the drivers into a folder.. Go to device manager in your laptop and look for that unknown device and there double click on unknown device and select update/install driver.. point the installation to the unzipped folders and click update driver and this should install apx drivers and you should be good to go as that's what I did. Its very easy so take your time and do it...
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
Same problem ! dosn't work even with naked driver any solution yet ?

mickz said:
Same problem ! dosn't work even with naked driver any solution yet ?
Click to expand...
Click to collapse
Try plugging your tf101 into another usb port and installing the naked drivers.

I am at the same place as this person.
I Booted into CWM Recovery 5.5.0.4 and I can't get back out. I tried wiping. I had an update.zip on my internal SD card. I've tried everything I've seen on the forums. and NOTHING. On windows I get an Unknown Device in both APX and ADB and ADB won't recognize the device. ADB works fine on all of my other android devices. I feel like i've got a 200 door stop. PLEASE HELP!
My device is a B50 TF-101 SBK1
Click to expand...
Click to collapse
Remove the apx drivers you already have and try installing them again by following these steps:
1- Boot up your transformer into apx mode.
2- Goto device manager and right click on the unrecognized device and goto update drivers.
3- Manually point them to the Folder you extracted have the universal naked drivers and install them. Scan for hardware changes
4- Hopefully your transformer will be recognized in the apx mode.
5- Download the EasyFlasher tool from http://forum.xda-developers.com/showthread.php?t=1688012
6- open EasyFlasher and Choose your device SBK1 or SBK2
7- Flash a new recovery on the transformer with the tool and reboot it.
8- You will have the access to your external sd card where u have ur ROM stored.
These step did the trick on my transformer. Hopefully your problem will be solved.
Hit thanks if i have helped in any way!!

konark500 said:
Remove the apx drivers you already have and try installing them again by following these steps:
1- Boot up your transformer into apx mode.
2- Goto device manager and right click on the unrecognized device and goto update drivers.
3- Manually point them to the Folder you extracted have the universal naked drivers and install them. Scan for hardware changes
4- Hopefully your transformer will be recognized in the apx mode.
5- Download the EasyFlasher tool from http://forum.xda-developers.com/showthread.php?t=1688012
6- open EasyFlasher and Choose your device SBK1 or SBK2
7- Flash a new recovery on the transformer with the tool and reboot it.
8- You will have the access to your external sd card where u have ur ROM stored.
These step did the trick on my transformer. Hopefully your problem will be solved.
Hit thanks if i have helped in any way!!
Click to expand...
Click to collapse
I can't thank konark500 enough. I had previously installed ClockworkMod Touch Recovery using the img file using the instructions on the Cyanogenmod Wiki. It worked, but every time I rebooted it would reboot back into flash and I would have to vol- at reboot to get it to boot to Android. Using EasyFlasher I was able to install TWRP and I am so glad I did. Everything is running better and I boot straight to Android when I need to. TWRP also has a way to wipe system. I was having strange issues with bluetooth and wifi others were not having until I wiped system and started over.
Thanks again konark500

Hi,
Sorry to resurrect a dead thread, but I am facing a similar issue. I installed a bad CWM recovery and since then I am not able to use my TF101. I tried to install the Naked drivers, but it does not work. I tried changing ports, but still the same issue. Please help. I am using Windows 8.1.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

My guess - your TF101 cable is bad. I had a bad one but it still works with the wall wart to charge. One of the Data + or - cables is disconnected. Try a new cable is my best suggestion.

[SOLVED] Nexus 5 stuck in boot loop animation (Lollipop) , partially working with 4.4

I have a Nexus 5 32GB that's about 14 month old. Was running Lollipop 5.1 which was installed through OTA updates (4.44 >5.0 >5.01>5.1). The device is stock and unrooted.
One day, after powering the device up, it went into the boot screen and never managed to finsih the boot (for hours).
After reading extensively on this and other forums , here are the steps I tired , without success:
1. Go to bootloader and press Start
2.Go to bootloader , erase cache
3.Go to bootloader erase user data (factory reset).
I then tried to flash the factory image back. I tried all Lollipop versions from the google developers page of factory images.
starting with 5.1.0 (LMY47I) and going down. All flashing was completed successfully, but the problem remains.
Then I tried 4.4.4 (KTU84P) and the device finally booted up, but it was crippled: Most times It only sees a storage of 16GB , the phone does not recognize any cellular carriers, google play crashes, camera crashes, gallery crashes. An error states that "no external memory is available". Basically it was useless.
I took the phone to an LG lab. They said I need to replace the motherboard. Costs about 200$ !!
I was about to get a new phone , but decided to try one more google search for a fix.
This guide is for any poor soul in the same state.
This issue can be solved without replacing the motherboard for 200$.
The problem in my case was that the /persist partition was degraded, and could not mount.
I found out by trying to follow this guide: http://android.stackexchange.com/qu...dots-lollipop-screen-after-hard-factory-reset
I got as far as activating ADB Sideload when I got the error "cannot mount /persist".
This is a software problem.
Her's how to fix it (It's a long and detailed guide - but worth the result):
First, you must enable USB debugging mode , if it was not enabled (if it is enabled you can skip the first step of this guide) . The way to do that is to flash a stock image that will load, even if not fully working. In my case I could flash version 4.4x and get the phone to load. I am not aware of any other way to enable USB debugging, other than from within a working OS. If someone knows a way - please post it.
The easiest way I found to flash my phone is using Julian OS' script. You can download the stock image5.0 and 5.01 with the script from here:
https://www.androidfilehost.com/?w=files&flid=22367
You will need to adapt the 4.4x firmware to have the script flash it, but it's very easy, just a couple of files to rename.
When you open Julian's zip file you will see that he uses a script that flashes the firmware's images one by one. What I did was download the stock images from Google https://developers.google.com/android/nexus/images , used winrar to extracrt all the files from the .tgz file to a folder, then unzip the only zip file there (image-hammerhead-xxxxx.zip) which contains 5 img files. I then renamed the radio-hammerhead-xxxxx.img to radio.img and bootloader-hammerhead-xxxx.img to bootloader.img. Now all the file names comply with Julian's script. From Julian's archive copy the files "From Bootloader.bat" and "fastboot.exe" to the folder where all the images you just renamed are.
Put the phone in bootloader mode (turn the phone off, press the Vol- and the power buttons). Once the the phone is in bootloader mode, connect it to the PC and run "From Bootloader.bat" and follow the onscreen instructions. In about 2 minutes, your phone will be flashed.
Turn the phone on, it should load the OS. Disregard all the error messages, and don't bother setting the phone up. If you skip wifi, and don't have a sim in the phone you can finish the basic setup quickly.
Next you need to get developer tools activated: Settings>about phone>Build number. Tap 7 times on the build number and this will unlock Developer tools. Go back to settings and the new Developer Tools and enable usb debugging. Approve any popups.
*** I am not aware of how to enable usb debugging if you cannot go into the settings. If non of the stock images loads for you, search for a way to get usb debugging working , or else you cannot continue. You need this for ADB to connect to the phone.****
Next, you need to have ADB on your PC, and it should be able to reach your phone. If you already have - then skip to the next step. If you don't - then here is how to get the latest version:
Go here and download the installer https://developer.android.com/sdk/index.html#Other
Install the file and when it's done run SDK manager. Choose only the first 2 tools (Android sdk tools and Platform tools), this will install the latest adb and fastboot tools. To make sure all is installed open a command prompt (Click Start, type cmd in the search and run cmd.exe) and type adb. You should see all the adb possible commands typed. Now you can test if your phone can be reached by adb: connect your phone (remember usb debugging must be on!) and type: adb devices. After a few seconds you should see something like this:
List of devices attached
024703f599cc8feb device
If you get this, it means you have usb debugging enabled and a proper usb driver installed and you can go to the next step . If there is no device in the list you need to install/update the USB driver:
You have to make sure that when you connect your phone with USB debugging on, you have 2 entries in Winodws Device manager:
Under Portable devices >Nexus 5 , and under Android device> Android composite ADB Interface.
If the second one is missing, ADB will not work and you can't continue. There are 2 ways to fix that :
1. You can install an Android driver called Universal Naked Driver 0.73 from here: http://forum.xda-developers.com/showthread.php?t=2386956. Unzip the file to a folder.
The author of that guide states you need to uninstall any driver that already exists. This proved tricky because Windows would not uninstall the Nexus 5 driver. I decided to install it on a PC that has no android driver.
When you connect the phone to a windows 7 pc for the first time it will search for a driver. I disconnected the internet and windows installed a generic driver. In device manager I saw Nexus 5 with a yellow triangle. I Right clicked on it > update driver software > Browse my computer for driver software and point to the folder you unzipped the driver. You will get a warning - allow the installation.
2. If that does not work or if you don't have another "virgin" PC try this:
Run SDK Manager, under Extras mark Google USB driver. You don't need anything else marked. Install the driver.
Now connect your phone to the PC in normal mode (not bootloader!) . Open device manager. You should have two entries: Portable devices >Nexus 5 and Android device > Android Composite ADB Interface
If the second one is missing, but the Nexus 5 is properly installed, Right click on the Nexus 5 device >Update driver software > Browse my computer for driver software >Let me pick from a list. Now make sure that "Show compatible Hardware" is ticked . You should now have an entry called "USB composite device". Choose that and let it install. When it's done, if you still have an an Unknown device >Nexus 5 and no Android Composite ADB Interface in device manager, then unplug the phone and reconnect it again . You should now have both devices installed.
If by chance this does not work, and you have a Nexus 5 with a yellow error , right click it>update software driver> Browse my computer.> and point it to the Universal Naked Driver folder or the SDK>Extras>Google USB driver folder and it should update so both devices appear (Nexus 5 and ADB).
Once adb can see your pohne go here, to read bitdomo's guide to fix the broken persist partition.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
There are some prerequisites to getting this to work:
The first one is that the phone can be reached by ADB, this is why you needed the usb debugging mode to be turned on, and the proper usb driver installed.
Second, you need to install a custom recovery image. Don't worry, you will overwrite it later. The one I used is TWRP. Get the latest version from here:
http://techerrata.com/browse/twrp2/hammerhead
To install I recommend you copy Fastboot.exe and the TWRP file to an empty folder on your PC . Rename the TWRP file to "recovery.img". Open a command prompt in the folder (see here if you don't know how http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm) , in the black window type: fastboot flash recovery recovery.img and hit Enter. Wait a few seconds and it will finish.
Last, you need to root your device. There are many ways to do this. I did this very simply by downloading CF-Auto-Root from https://autoroot.chainfire.eu/ The file you need is this: https://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip . Unzip it, put your phone in bootloader, run root-windows.bat.
Now you are prepaired... Follow the guide by bitdomo . Open a command prompt , and run the 2 commands bitdomo wrote. You will get a series of questions , type y followed by Enter until it's all done.
SInce you are still in bootloader mode, and a big START is at the top of the screen, click the power button to reboot. Now your oS 4.4x should load properly. Make sure everything is working.
I did not follow the steps for the wifi and BT fix , because they worked fine (and still do 4 months later) , but you can go ahead and do that too.
Now you can flash to the latest firmware 5.10 - download the file from the developer site I gave before, use Jason Os's script to flash the image, and lock the device. Done! Boot up the device and make sure it recognizes the right amount of RAM on your phone (16 or 32GB). If it does, then all is well .
When I first booted the device , I saw that it only recognized 16GB instead of 32GB. To solve this install TWRP again, go to Wipe>Format data . Then reboot the device and make sure you have 32GB.
If you like the stock recovery instead of TWRP you can use Fastboot to flash the original recovery.img.
Now you have a working Nexus 5 , v5.10.
Thanks to LyricWulf and bitdomo for their life saving guides. I hope this helps others in the same spot, and saves them 200$ .

stuck at unlock step
how u unlock nexus 5 when stuck booplop n cnt go to android screen?alrdy using ths step "fastboot oem unlock" when i reboot for unlock,stuck at bootloop n alrdy w8ing 24hr still bootloop cnt see android home screen...n i go to restart nexus5,n locked again... i just stuck on this place,cnt go to next step..pls help me
sry my englsh so bad

Thanks! Helped me to save my N5!
Do not need to exactly as it is posted but the directions is good!
Thanks again.

killian.1140 said:
how u unlock nexus 5 when stuck booplop n cnt go to android screen?alrdy using ths step "fastboot oem unlock" when i reboot for unlock,stuck at bootloop n alrdy w8ing 24hr still bootloop cnt see android home screen...n i go to restart nexus5,n locked again... i just stuck on this place,cnt go to next step..pls help me
sry my englsh so bad
Click to expand...
Click to collapse
Not sure what your problem is, but if you are stuck at the boot screen (with the colored dots spinning) you might have the smae problem I describe. You can try to go to bootloader and wipe the cache, if that does not help and you don't mind a wiping all your data do a factory reset. , Go to recovery mode (third option in bootloader), then press the powr and vol up buttons together several times until you get into recovery. Then choose what you want to wipe.
If that does not restore your phone you need to follow my guide. Probably your persist partion is degraded and needs to be fixed. If you follow my guide you will find out what your problem is.
Good luck

Or just read the stickies.

I had the same problem, and for me, simple NAND restore from TWRP recovery solved this issue. I recently made this NAND backup for no reason and it happens to be a very good move. Cheers

Thank you so much for this! You saved my phone!

volvoxxda said:
I had the same problem, and for me, simple NAND restore from TWRP recovery solved this issue. I recently made this NAND backup for no reason and it happens to be a very good move. Cheers
Click to expand...
Click to collapse
But for that you have had to install TWRP in the first place...
Mine was stock.
Where is the backup saved?

Mine was rooted + TWRP recovery and I saved my backup on flash drive with TWRP's backup option. I was able to boot into boot menu (pwr + vol-) and it would let me to enter into TWRP only. For me it was enough to initiate a restore process..

volvoxxda said:
Mine was rooted + TWRP recovery and I saved my backup on flash drive with TWRP's backup option. I was able to boot into boot menu (pwr + vol-) and it would let me to enter into TWRP only. For me it was enough to initiate a restore process..
Click to expand...
Click to collapse
Flash drive? Do you mean the Nexus internal memory?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
External, like on this picture.

Final solution: power button micro tactile switch was faulty, causing boot loop from time to time. Replacing that little bastard solved this heartbreaking issue

volvoxxda said:
Final solution: power button micro tactile switch was faulty, causing boot loop from time to time. Replacing that little bastard solved this heartbreaking issue
Click to expand...
Click to collapse
Did you just replace the button or did you have to replace something more?
Thanks

Just the button. You can DIY, it's easy.

worked
worked great. confusing in the start but got it working. Thanks for a life saving guide for nexus 5

incredible
Hi eross,
I registered and logged in just to say thank you for this amazing tutorial. I've been trying to repair my N5 for about 12 hours, and I was about to give up when I saw this post. You saved my Nexus!!
Thanks again. :victory::highfive::good:

eross said:
Not sure what your problem is, but if you are stuck at the boot screen (with the colored dots spinning) you might have the smae problem I describe. You can try to go to bootloader and wipe the cache, if that does not help and you don't mind a wiping all your data do a factory reset. , Go to recovery mode (third option in bootloader), then press the powr and vol up buttons together several times until you get into recovery. Then choose what you want to wipe.
If that does not restore your phone you need to follow my guide. Probably your persist partion is degraded and needs to be fixed. If you follow my guide you will find out what your problem is.
Good luck
Click to expand...
Click to collapse
What if you cannot even get into recovery because it is missing?
Sent from my SM-G920T

ambervals6 said:
What if you cannot even get into recovery because it is missing?
Sent from my SM-G920T
Click to expand...
Click to collapse
You can try to download the stock firmware that's installed on your phone and flash the recovery img, or flash twrp recovery.

help
eross said:
This is a Nexus 5 32GB that's about 14 month old. Was running Lollipop 5.1 which was installed through OTA updates (4.44 >5.0 >5.01>5.1). The device is stock and unrooted.
Yesterday after powering the device up, it went into the boot screen and never managed to finsih the boot (for hours).
After reading extensively on this and other forums , here are the steps I tired , without success:
1. Go to bootloader and press Start
2.Go to bootloader , erase cache
3.Go to bootloader erase user data (factory reset).
I then tried to flash the factory image back. I tried all Lollipop versions from the google developers page of factory images. (can't post links yet...)
starting with 5.1.0 (LMY47I) and going down. All flashing was completed successfully, but the problem remains.
Then I tried 4.4.4 (KTU84P) and the device finally booted up, but it is crippled: Most times It only sees a storage of 16GB , the phone does not recognize any cellular carriers, google play crashes, camera crashes, gallery crashes. An error states that "no external memory is available". Basically it is useless.
I am wondering if it is a software or hardware problem. It appears as though part of the phone's memory is not functioning . Is there a way to check this? Is there a way to fix this?
Thanks
Edit: Just came back from an LG lab. Bad news. Need to replace the motherboard. Costs about 200$ !! Can't find anything cheaper on ebay. Guess it's time for a new phone
Edit #2 - SOLVED !!:laugh:
OK, this for any poor soul in the same state. This issue can be solved without replacing the motherboard for 200$.
The problem in my case was that the /persist partition was degraded, and could not mount. Here is how I found it out, and how I fixed it:
First, try to flash a stock image that will load, even if not fully working. You will need this later. In my case I could flash version 4.4x and get the phone to load.
The easiest way I found to flash my phone is using Julian OS' script. You can download the stock image5.0 and 5.01 with the script from here:
https://www.androidfilehost.com/?w=files&flid=22367
You will need to adapt the 4.4x firmware to have the script flash it, but it's very easy, just a couple of files to rename.
When you open Julian's zip file you will see that he uses a script that flashes the firmware's images one by one. What I did was download the stock images from Google https://developers.google.com/android/nexus/images , used winrar to extracrt all the files from the .tgz file to a folder, then unzip the only zip file there (image-hammerhead-xxxxx.zip) which contains 5 img files. I then renamed the radio-hammerhead-xxxxx.img to radio.img and bootloader-hammerhead-xxxx.img to bootloader.img. Now all the file names comply with Julian's script. From Julian's archive copy the files "From Bootloader.bat" and "fastboot.exe" to the folder where all the images you just renamed are.
Put the phone in bootloader mode (turn the phone off, press the Vol- and the power buttons). Once the the phone is in bootloader mode, connect it to the PC and run "From Bootloader.bat" and follow the onscreen instructions. In about 2 minutes, your phone will be flashed.
Turn the phone on, if you are lucky it will load the OS. Disregard all the error messages, and don't bother setting the phone up. If you skip wifi, and don't have a sim in the phone you can finish the basic setup quickly.
Next you need to get developer tools activated: Settings>about phone>Build number. Tap 7 times on the build number and this will unlock Developer tools. Go back to settings and the new developer tools and enable usb debugging. Approve any popups.
I am not aware of how to enable usb debugging if you cannot go into the settings. If non of the stock images loads for you, search for a way to get usb debugging working , or else you cannot continue. You need this for ADB to connect to the phone.
Once this is done , boot the phone into debugging mode.
Read the guide here http://android.stackexchange.com/qu...dots-lollipop-screen-after-hard-factory-reset
I got as far as activating ADB Sideload when I got the error "cannot mount /persist". I then understood what the problem was. If you get the same error - you are in luck!
Then go here, to learn how to fix the broken persist partition.
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
There are some prerequisites to getting this to work.
The first one is that the phone can be reached by ADB, this is why you needed the usb debugging mode.
Second, you need to install a custom recover image. Don't worry, you will overwrite it later. The one I used is TWRP. Get the latest version from here:
http://techerrata.com/browse/twrp2/hammerhead
To install I recommend you copy Fastboot.exe and the TWRP file to an empty folder on your PC . Rename the TWRP file to "recovery.img". Open a command prompt in the folder (see here if you don't know how http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm) , in the black window type: fastboot flash recovery recovery.img and hit Enter. Wait a few seconds and it will finish.
Third, you need to install an Android driver called Universal Naked Driver 0.73 from here: http://forum.xda-developers.com/showthread.php?t=2386956. Unzip the file to a folder.
Since the author of that guide states you need to uninstall any driver that already exists, I decided to install it on a PC that has no android driver. When you connect the phone to a windows 7 pc for the first time it will search for a driver. I disconnected the internet and windows installed a generic driver. In device manager I saw Nexus 5 with a yellow triangle. I Right clicked on it > update driver software > Browse my computer for driver software and point to the folder you unzipped the driver. You will get a warning - allow the installation.
Last, you need to root your device. (I think this can also be done from within TWRP , but I am not sure how...) I did this very simply by downloading CF-Auto-Root from https://autoroot.chainfire.eu/ The file you need is this: https://download.chainfire.eu/363/CF-Root/CF-Auto-Root/CF-Auto-Root-hammerhead-hammerhead-nexus5.zip . Unzip it, put your phone in bootloader, run root-windows.bat.
Now you are prepaired... Follow the guide by bitdomo . Open a command prompt where adb.exe is located , and run the 2 commands bitdomo wrote. You will get a series of questions , type y followed by Enter until it's all done.
SInce you are still in bootloader mode, and a big START is at the top of the screen, click the power button to reboot. Now your oS 4.4x should load properly. Make sure everything is working.
Now you can flash to the latest firmware 5.10 - download the file from the developer site I gave before, use Jason Os's script to flash the image, and lock the device.
When I first booted the device , I saw that it only recognized 16GB instead of 32GB. To solve this install TWRP again, go to Wipe>Format data . Then reboot the device and make sure you have 32GB.
If you like the stock recovery instead of TWRP you can use Fastboot to flash the original recovery.img.
Now you have a working Nexus 5 , v5.10.
Thanks to LyricWulf and bitdomo for their life saving guides. I hope this helps others in the same spot, and saves them 200$ .
Addendum: According to bitdomo, installing a custom recovery like TWRP enables USB debugging by default even if the phone does not boot. I have not tried this myself, but this means you can foergo installing os 4.4x , and go straight to ADB and run the command that fixes the persist partition.
Go ahead and try it. It will save you a lot of time!
Click to expand...
Click to collapse
My N5 has exact problem as yours even same errors of camera and playstorw crashing when i loaded older android version.. now im positive your instructions will help me but im having some trouble with your steps i do not know how to type comnands with ADB .. im truly novice and dont want to damage the phone more could you simplify the steps or make a video please? Thank you

Sorry, I can't make it any simpler than that. I can't make a video now because my phone is fixed. Adb is very simple, it's like an old DOS window where you type the text. I would follow Bitdomo's advice and start by installing TWRP. This will get you USB debugging, and you can run ADB and follow his instructions to fix the persist partition.

My phone is not yet 1 month old please help me

i was trying to root my phone i done it and i am trying to install a rom to it
after that i twrp and delete all files.
i have files still in my pc can someone help me how to put some zip in the phone because my pc cant detect my phone anymore.
thanks guys

Try re-installing the proper drivers for the device and also try to boot to fastboot and check if it detected. And if it does so, try restoring to official firmware.

If you can buy an OTG cable and try a pendrive. An OTG cable is a life saver in case of Mi4i since it doesn't have an MicroSD. If you haven't bought it yet, today maybe the time
If you have installed the driver. The copying from TWRP only works sometimes.
If you rooted then you must have used Fastboot so the drivers are there.
As hunkerpunk1 said install default ROM via fastboot using MiFlash.
Also if you are going to install CM12.1 or any custom roms here. You're phone must have MIUI 6 installed before not MIUI 7. So flash MIUI 6. Then root it and flash TWRP. Then install the ROM. This time copy the files inside the phone before hand

Please check if you're able to go into recovery (TWRP, NOT Stock), if answer is yes, you can use the mount option to copy those files again into your phone.
You simply need to :
1. Boot into TWRP
2. Connect the phone with PC (With Proper drivers installed)
3. Select the MOUNT option on TWRP Recovery
4. You'll see the prompt on your PC that Mi4i (with some Chinese words prepends) detected.
5. Copy the ROM & Gapps in phone.
6. BOOM (now I'm assuming you know how to move further)

upgrade method to another android version for Rockchip unit (px6 px5 Px30 and other )

following the official Rockchip upgrade tool https://forum.xda-developers.com/an...ment/mtcd-e-android-10-upgrade-using-t4123933
if you are upgrading from the same version ex android 9 to android 9 you don't need this
if you are upgrading from android 9 to android 10 or later version you will need this
tools link
https://github.com/rockchip-linux/tools
here is the simplified method ( for 1&2 you need update.img for 3 you need UPDATE.ZIP )
first method __________________________________________________________________________________________________________________________________________________________________
using usb A to A ( https://www.amazon.com/Monoprice-Male-24AWG-Cable-Plated/dp/B002KKXP3M/ref=sr_1_2?dchild=1&keywords=usb%2Batoa&qid=1594497313&sr=8-2&th=1 )
and laptop
download RockChip Batch Tool
connect the pc to the unit using the usb
in fw path chose the IMG file
the click upgrade
wait until you process is done will see the new version booting up
don't unplug until the app tel you to do so
second method _______________________________________________________________________________________________________________________________________________________________________________________
using the Real GPS SD port
download SDDiskTool
plug the SD to PC
select the SD from drop menu
Only upgrade option is checked
then select the IMG file
click create
when it is done
go to your unit
the put in to recovery
then plug the sd into the REAL GPS port
then from recovery select restart system
the upgrade process will start
then it will ask you to remove the sd
then it will boot up
third method ______________________________________________________________________________________________________________________________________________________________________________________
using the app modinstaller 2 on your unit ( http://hal9k.ru/?page_id=207)
click on the version you want
then NEW recovery will boot
put a OTA update.zip on sd or usb drive
select upgrade
then the upgrade will start don't remove the USB until update is done

and for anyone that his unit only have 1 SD card reader only ( media sd )
actually the second one is hiding inside (GPS SD)
if you want to try
i have moded my unit to be able to access the GPS port
you need to remove the one side the cut a hole to access the SD card
from top cover
https://i.imgur.com/fzusSZ5.jpg
close up to the SD card ( it comes empty)
https://i.imgur.com/uGgUdxn.jpg
after i remove the side case
https://i.imgur.com/gGxj61y.jpg
the side case after cutting ( i am very bad i know )
https://i.imgur.com/0qTW7Mw.jpg
after installing the side back and you can see the SD card
https://i.imgur.com/yQqeVIJ.jpg
this is after the android 10 install
https://i.imgur.com/yQqeVIJ.jpg

The Latest version in here https://yadi.sk/d/umCvHqCDzHccr
in the name if it is IMG for method 1& 2 as you need img
if the name is OTA is for method 3
after you upgrade you can upgrade to the latest ota like normal just put it on the usb
just so you know
HA3_HCT_CHS2 and other
are built for the same unit the only different is the launcher included in it
use the one you like

Thank you for this.
I have hal9k rooted ROM, Android 9, Dasaita max6.
If I do procedure method 1 (easy way) will it works without problem?
I know I will loose hal9k ROM, just I want be sure that HU will be like original but with Android 10.

Thank you for the explanation.
How to create a. Img from the ota update.zip?
Envoyé de mon Mi 9T en utilisant Tapatalk

spinose said:
Thank you for the explanation.
How to create a. Img from the ota update.zip?
Envoyé de mon foofoo en utilisant mrbungle
Click to expand...
Click to collapse
You dont. In theory, not impossible, just difficult unless OTA contains full files including bootloader and recovery - which they never do.
Instead, install appropriate full .IMG then OTA from recovery.
If next question is where do I find .IMG files, a search through the mtcd section is the best place to start

marchnz said:
You dont. In theory, not impossible, just difficult unless OTA contains full files including bootloader and recovery - which they never do.
Instead, install appropriate full .IMG then OTA from recovery.
If next question is where do I find .IMG files, a search through the mtcd section is the best place to start
Click to expand...
Click to collapse
Hi just to have the complete picture as this is were i get doubts , so to upgrade to a higher version of android you require a "third file " , if using SD card method ?
As for a normal upgrade you have
- DMCU file to upgrade MCU (DMCU.IMG)
- OTA file to upgrade manufacturer firmware ( update)
if i understand you correctly for android upgrade to a higher version you would require the OTA file(update) to be an image file(.img) as well ?
Or are the required files just the two you would normally use only you have to apply them dfferently as described above ?

spinose said:
Thank you for the explanation.
How to create a. Img from the ota update.zip?
Envoyé de mon Mi 9T en utilisant Tapatalk
Click to expand...
Click to collapse
don't create anything if you need IMG donwnload an img if you need a update zip download that
you can find them all in my 3rd post
if you want to use method 1 or 2 you need IMG like this
hct7_rk3399_10.0_IMG(20200415).zip
if you want to use method 3 you need ota like this
hct7_rk3399_10.0_ota(20200415).zip

Tempest67 said:
Hi just to have the complete picture as this is were i get doubts , so to upgrade to a higher version of android you require a "third file " , if using SD card method ?
As for a normal upgrade you have
- DMCU file to upgrade MCU (DMCU.IMG)
- OTA file to upgrade manufacturer firmware ( update)
if i understand you correctly for android upgrade to a higher version you would require the OTA file(update) to be an image file(.img) as well ?
Or are the required files just the two you would normally use only you have to apply them dfferently as described above ?
Click to expand...
Click to collapse
if you want to use method 1 or 2 you need IMG like this
hct7_rk3399_10.0_IMG(20200415).zip
if you want to use method 3 you need ota like this
hct7_rk3399_10.0_ota(20200415).zip

This video in GERMAN ( you can put subtitle in English )from Alex's Android Radio explain the method 3
https://www.youtube.com/watch?v=UIJFJYh2y4A

And here's the English video ?

How to update from 8.1 to 10 ?
I tried an update from 8 to 9 before using stock img but got aborted. Something to do with incompatibility with Hals rom.

Ati_gangster said:
And here's the English video
Click to expand...
Click to collapse
Thanks for showing the link but what a Waste of time. Instructions ineligible and video so fast, it was hard to know what was going on.
The only bit that is understandable was the section on how to pay.
Nothing on the merits of upgrading or function.
Just a big useless advert.

cleverdicky said:
Thanks for showing the link but what a Waste of time. Instructions ineligible and video so fast, it was hard to know what was going on.
The only bit that is understandable was the section on how to pay.
Nothing on the merits of upgrading or function.
Just a big useless advert.
Click to expand...
Click to collapse
You can adjust the playback speed to 0.75 or maybe better to 0.5.

abogrhen said:
don't create anything if you need IMG donwnload an img if you need a update zip download that
you can find them all in my 3rd post
if you want to use method 1 or 2 you need IMG like this
hct7_rk3399_10.0_IMG(20200415).zip
if you want to use method 3 you need ota like this
hct7_rk3399_10.0_ota(20200415).zip
Click to expand...
Click to collapse
where to find image for dasaita px6?

m1john said:
where to find image for dasaita px6?
Click to expand...
Click to collapse
The first thing if you want to update to 10 with this mode, you have to install the .img that is here. After you have android 10 you can install dasaita's if you want.
Enviado desde mi ONEPLUS A5010 mediante Tapatalk

It seems that I cannot upgrade to Android 10. My unit is Dasaita PX6 and whichever method I choose it always boots into...black screen.
1. USB A to A - does not recognise the unit in Windows, I have tried invoking booting into bootloader with command reboot bootloader....black screen
2. SDCard - boot into recovery, insert card, reboot ... black screen
3. Purchased MODInstallerPro, copied ZIP onto SD card, install the apk, reboots and black screen again

mariof said:
It seems that I cannot upgrade to Android 10. My unit is Dasaita PX6 and whichever method I choose it always boots into...black screen.
1. USB A to A - does not recognise the unit in Windows, I have tried invoking booting into bootloader with command reboot bootloader....black screen
2. SDCard - boot into recovery, insert card, reboot ... black screen
3. Purchased MODInstallerPro, copied ZIP onto SD card, install the apk, reboots and black screen again
Click to expand...
Click to collapse
I have a Dasaita PX6 unit and what did not work for me, was the bootable SD card method. The mod installer worked, the connection to the PC through the single USB cable worked, but make sure you have the drivers installed so that the pc recognizes the radio unit, when you use the USB cable method use the reset button to go into recovery mode and the PC will sound that something was connected, from there try to install the correct drivers. Show us the exact head unit that you have, mine doesn't have any buttons on the front, and sometimes there was a black screen because I needed to touch the power button and the screen would turn on showing the boot logo.

Al Ferro said:
I have a Dasaita PX6 unit and what did not work for me, was the bootable SD card method. The mod installer worked, the connection to the PC through the single USB cable worked, but make sure you have the drivers installed so that the pc recognizes the radio unit, when you use the USB cable method use the reset button to go into recovery mode and the PC will sound that something was connected, from there try to install the correct drivers. Show us the exact head unit that you have, mine doesn't have any buttons on the front, and sometimes there was a black screen because I needed to touch the power button and the screen would turn on showing the boot logo.
Click to expand...
Click to collapse
This is the Unit I have
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok, The Mod Installer finally worked for me. I mean it installed Android 10 but I did not see any progress at all. I have left the unit with blank screen for several minutes, then rebooted and the Android 10 logo showed up.
The USB method still does not work at all. I have tried different combinations
Tried all 3 USB ports
Booted into recovery with cable inserted - black screen, no Windows drivers beep sound
Boot into bootloader - black screen, no Windows drivers beep sound
Device off, cable inserted, powered on - black screen, no Windows sound.
Windows device manager did not recognise any unknown devices in all the above methods.

mariof said:
This is the Unit I have
Ok, The Mod Installer finally worked for me. I mean it installed Android 10 but I did not see any progress at all. I have left the unit with blank screen for several minutes, then rebooted and the Android 10 logo showed up.
The USB method still does not work at all. I have tried different combinations
Tried all 3 USB ports
Booted into recovery with cable inserted - black screen, no Windows drivers beep sound
Boot into bootloader - black screen, no Windows drivers beep sound
Device off, cable inserted, powered on - black screen, no Windows sound.
Windows device manager did not recognise any unknown devices in all the above methods.
Click to expand...
Click to collapse
when you have the device turned off, USB cable connected to pc, turn on the device and right away use the reset button to go into recovery, the drivers in your pc should be already installed before you do any of these steps, and have the android tool installed as well. Open the android app tool on your pc, open device manager if you want too, and scan for new devices, the head unit screen stays black when connected to the pc, but it will sound that it has connected, the single USB cable should be used from the back of the head unit.