Chromecast won't root - Google Chromecast

Hello
I need help, I'm trying to root my Chromecast but when I plug in my flash drive and connect to power I press the button on the Chromecast and the screen sets to black with a little line with colors an the flash drive starts to blink as if it's being reed but the Chromecast never reboots so I don't know what to do next I've already try with 2 different otg cables and 2 Chromecast so it definitely is something I'm doing wrong and the bin was flashed correctly (I think) I'll appreciate any help

Patched
Hell.Knight said:
Hello
I need help, I'm trying to root my Chromecast but when I plug in my flash drive and connect to power I press the button on the Chromecast and the screen sets to black with a little line with colors an the flash drive starts to blink as if it's being reed but the Chromecast never reboots so I don't know what to do next I've already try with 2 different otg cables and 2 Chromecast so it definitely is something I'm doing wrong and the bin was flashed correctly (I think) I'll appreciate any help
Click to expand...
Click to collapse
Sounds like your bootloader is locked. Even new retail devices (bought one yesterday) already have the exploit patched.
the momentary access of the thumbdrive followed by the sliver of colored pixels and then a blank screen indicates you cannot exploit the bootloader on that chromecast (this root method has been closed tight like the sphincter of a young human)

Bild 12072
BusterChestnut said:
Sounds like your bootloader is locked. Even new retail devices (bought one yesterday) already have the exploit patched.
the momentary access of the thumbdrive followed by the sliver of colored pixels and then a blank screen indicates you cannot exploit the bootloader on that chromecast (this root method has been closed tight like the sphincter of a young human)
Click to expand...
Click to collapse
I Appreciate your reply but the thing is that I double check the build version and well one is all ready on the 12940 build which updated today but the other one is still on the older build 12072 which I thinkit can still be rooted doesn't it?

Hell.Knight said:
I Appreciate your reply but the thing is that I double check the build version and well one is all ready on the 12940 build which updated today but the other one is still on the older build 12072 which I thinkit can still be rooted doesn't it?
Click to expand...
Click to collapse
Stick the USB stick into a computer. If you can't see any files and folders with Explorer, then there is the problem.
I use Win32DiskImager.exe instead of dd
to write to the USB stick.
I find it is more reliable.

HowardZ said:
Stick the USB stick into a computer. If you can't see any files and folders with Explorer, then there is the problem.
I use Win32DiskImager.exe instead of dd
to write to the USB stick.
I find it is more reliable.
Click to expand...
Click to collapse
I use Win32DiskImager as well. The file shows up on the USB drive. When I connect the OTG/USB cable to the CC while holding the reset button, I get the same black screen with a few colored dots. My build is 12072.
How long does reset need to be held?
We are supposed to be using the .bin file in Win32Diskimager, and not the .zip, correct? Win32DiskImager by default asks for files of type .img, .IMG. and you must change this, correct?
What kind of file system must the USB drive be formatted in before using Win32DiskImager?
The unpacked .bin file is 125MB on the computer, but after being flashed to the USB it is only 68.8MB. Is this correct?

Donteventrii said:
I use Win32DiskImager as well. The file shows up on the USB drive. When I connect the OTG/USB cable to the CC while holding the reset button, I get the same black screen with a few colored dots. My build is 12072.
How long does reset need to be held?
We are supposed to be using the .bin file in Win32Diskimager, and not the .zip, correct? Win32DiskImager by default asks for files of type .img, .IMG. and you must change this, correct?
What kind of file system must the USB drive be formatted in before using Win32DiskImager?
The unpacked .bin file is 125MB on the computer, but after being flashed to the USB it is only 68.8MB. Is this correct?
Click to expand...
Click to collapse
I used the .bin file without renaming it.
When Win32DiskImager is done, Windows Explorer shows it as being a 128gb drive. It actually is a 256gb drive, but apparently the . bin file repartitions it to be 128gb. I don't think it matters how the USB drive is formatted, because the WI 32DiskImager will repartition and reformat it. With windows Explorer I can see files on the flash drive.
Then I connect the chromecast to the USB stick, then connect the chromecast to the TV, then hold the reset button, then plug in the ac power supply for the chromecast. I'm not sure exactly how long I kept pressing the reset button after providing power to the chromecast, but my guess is about 30 seconds.

HowardZ said:
I used the .bin file without renaming it.
When Win32DiskImager is done, Windows Explorer shows it as being a 128gb drive. It actually is a 256gb drive, but apparently the . bin file repartitions it to be 128gb. I don't think it matters how the USB drive is formatted, because the WI 32DiskImager will repartition and reformat it. With windows Explorer I can see files on the flash drive.
Then I connect the chromecast to the USB stick, then connect the chromecast to the TV, then hold the reset button, then plug in the ac power supply for the chromecast. I'm not sure exactly how long I kept pressing the reset button after providing power to the chromecast, but my guess is about 30 seconds.
Click to expand...
Click to collapse
What did you see when you it booted up? The black screen with the few colored dots?
How big is the bin file on the the disk?

Donteventrii said:
What did you see when you it booted up? The black screen with the few colored dots?
How big is the bin file on the the disk?
Click to expand...
Click to collapse
You live in Baltimore.
I am about one hour drive away.
If you are having so much difficulty, you can come over and I can do it for you.
Howard

HowardZ said:
Stick the USB stick into a computer. If you can't see any files and folders with Explorer, then there is the problem.
I use Win32DiskImager.exe instead of dd
to write to the USB stick.
I find it is more reliable.
Click to expand...
Click to collapse
I used another program and got the exact same lines and loops. I used Win32DiskImager.exe with the same bin, cable and USB stick.....All I was asked when everything was done was to set up my chromecast

Rooted
HowardZ said:
Stick the USB stick into a computer. If you can't see any files and folders with Explorer, then there is the problem.
I use Win32DiskImager.exe instead of dd
to write to the USB stick.
I find it is more reliable.
Click to expand...
Click to collapse
Thank you man! In fact after using dd my pc would tell me that my usb had no format and I thought it was normal but with win32diskimager.exe it was faster to write to the usb stick and the Chromecast was rooted in no time.
I really appreciate you're help, thanks a lot.

Related

How to FORCE stop phone from showing up as USB drives in Recovery, still no root :(

Okay I don't know if this will help anyone, but I figured out how to stop Windows from detecting the phone as two USB drives when the phone goes into Recovery mode, and to make it show up as Android Composite ADB device.
I do NOT have HTC installed, rather, I'm using the USB 3 drivers that come down through the SDK, so I'm not sure how to do this if you are using the HTC Sync drivers intead.
At any rate, start with the phone off and disconnected. Open the Device Manager. Boot with your prefered method into Recovery mode, then connect the phone. It should detect as USB Mass Storage Device under Universal Serial Bus Controllers. Right click on USB Mass Storage Device and click Uninstall and then OK. Once this is done, disconnect the phone (you can leave it running in Recovery).
Open My Computer and navigate to C:\Windows\inf. Copy the files usbstor.inf and usbstor.pnf to your desktop or wherever, it doesn't matter, just make sure you put them somewhere you can get them later. Then delete them from the C:\Windows\inf folder. These are the drivers that Windows automatically uses for USB storage devices.
Ok, now bring Device Manager back to the foreground and plug the phone back in in Recovery. It should show up as Android Phone with an exclamation mark. If Device Wizard pops up cancel out of it. Now right click on the Android Phone and click update driver. Click Browse my computer for driver software. Click Let me pick from a list... Click Android Phone and Next. Click Have Disk. Browse to your SDK folder into the USB Drivers folder and you should see android_winusb.inf, select that then click OK. You should now have a list of three items to select, this part I am not sure if there is a 'right' or a 'wrong' but I go with Android Composite ADB Interface.
Select that or whichever one you think and this is what it will install as. Bingo, now whenever you connect the phone into Recovery or boot into Recovery with it already connect it correctly detects as the Composite ADB Interface or whichever you selected, but does NOT show up as any USB drives.
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
At any rate, to get everything back to normal as far as your computer being able to use USB storage devices just copy those two files back to the inf folder before you connect them and you should be fine.
bast525 said:
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
.
Click to expand...
Click to collapse
Format it LONG Fat32, 1024k allocation, name it TEST, put PB31IMG.zip (downgrade ROM) on it, power on into bootloader holding volume down until you get to volume up to start upgrade, run the downgrade from Bootloader, then immediately reboot with holding the track button switch into Fastboot menu, power to Bootloader, let the card check run, decline upgrade this time, run your loop.bat or loop.sh if you like linux, power the phone into recovery boot, and prepare yourself to be happy--I think that will work. The whole trick is get a card/format that forces recovery into an ADB-available mode.
Or you could try what I've done 7 times and achieved ADB Shell 7 times...
1. Turn the phone off.
2. Start running Loop.bat
3. Unplug USB cable.
4. Turn device on in Fastboot by holding in the optical joystick and power.
5. Plug USB in.
6. Hit power button once to get to HBOOT.
7. Wait two seconds for it to do it's thing.
8. Pull off the back of the phone.
9. Hit Vol - to Recovery then hit power.
10. Immediately after doing this continuously push the sd card in and out (about every .5 - .75 seconds)
11. ?????
12. Profit
@DigitalDementia--
How is what you said relevant in this thread?
bast525 said:
Unfortunately... I still could not get ADB Shell to connect (I even went out and bought a 2GB PNY card).... so I don't know if this will help any of you but I figure it's one step closer to what we need to happen.
Click to expand...
Click to collapse
drtrmiller said:
@DigitalDementia--
How is what you said relevant in this thread?
Click to expand...
Click to collapse
Pretty positive it had everything to do with that section of the first post, he said he still couldn't achieve root I attempted to help him. Why don't you explain to me exactly what it doesn't have to do with this thread?
rynosaur said:
Format it LONG Fat32, 1024k allocation, name it TEST, put PB31IMG.zip (downgrade ROM) on it, power on into bootloader holding volume down until you get to volume up to start upgrade, run the downgrade from Bootloader, then immediately reboot with holding the track button switch into Fastboot menu, power to Bootloader, let the card check run, decline upgrade this time, run your loop.bat or loop.sh if you like linux, power the phone into recovery boot, and prepare yourself to be happy--I think that will work. The whole trick is get a card/format that forces recovery into an ADB-available mode.
Click to expand...
Click to collapse
The real bummer here - and I should have known better, really - is that this wipes your phone.
I suppose it should be obvious, but take it from someone who's pretty new to Android phones and just wiped their entire phone after following your steps: Please add a warning to your original post.
It's late, I'm tired and irritated, but I'm sort of bummed to know I went from hero to zero in trying to enter shell (again) during recovery all in an effort to get proper perm. root. Sort of ****ty to know that I just lost everything.
still no root
I'm sorry, I shouldn't have assumed people knew an IMG flash from bootloader wipes user data. Believe me, that's not the only time you'll wipe if you keep modding
-------------------------------------Sent via the XDA Tapatalk App
USB drives are ok in recovery
When I am in recovery with adb and working correctly it still shows the 2 USB drives so this is normal and ok, what you have done is fool yourself into thinking that your phone is in correct mode but it really is not, this is why it still does not work, sorry.
rynosaur said:
I'm sorry, I shouldn't have assumed people knew an IMG flash from bootloader wipes user data. Believe me, that's not the only time you'll wipe if you keep modding
-------------------------------------Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Now that I've scorched the earth, I'm hitting this thing hard with every trick I can think of to get the shell in recovery again.
Thankfully, I at least have my app list on appbrain.
After researching around the different forums, I think this maybe my issue. I will have to make this attempt when I get home.
This is what I posted on a different forum. I am not sure if this is a similar experience you were having:
So, for a little a bit I was having issues with finding and modding the usb.inf file. I got that finally resolved... Now as I go to one of the first parts of the procedure, executing the adb shell command. Well at first it said the 2 lines, about the daemon and whatever the second line was. Anyways, the third line did not say "no device found" it went straight to a shell prompt "$" . The instructions made a point in the instructions for it to say " no device found" .
I went ahead with the rest of the instructions. No Luck. And I did both methods. A co-worker of mine told to run adb devices to see if my phone is recognized. I will also make that attempt tonight.
I wanted to know if any of you had some insight. I made sure I was in the right directory.
I will make another attempt on a different machine tonight.
Thanks. Oh yeah, I do have some UNIX experience if that makes a difference.
I had the same problem, used this method here
addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/
Click to expand...
Click to collapse
Seemed to help me with the dumb usb mass storage devices whilst in recovery
I don't know how I missed this thread earlier though, It had been a problem for me for days!
kentoe said:
I had the same problem, used this method here
Seemed to help me with the dumb usb mass storage devices whilst in recovery
I don't know how I missed this thread earlier though, It had been a problem for me for days!
Click to expand...
Click to collapse
I rooted in Windows, rather than linux, simply because I like the look of MejDam's procedure better than the linux script posted here on XDA--and his windows procedure is accompanied by his YouTube video
Long story short: I had ADB Composite Device AND the two storage volumes mounted together, as I got shell, and did the other steps in recovery. NB: they were mounted as Generic Storage Volumes, not writeable partitions. The stock recovery on DI does not allow host to mount either partions, although I'd like to see if
Code:
mount /dev/block/mmcblk0p1
worked for the SDcard on the sdcard, cuz then it would be a cinch to mount sdcard/emnc partition into host OS--windows, linux, Atari 2600, etc Worth a try.
Anyhow, my conclusion: a bad driver setup could be a barrier to catching adb shell, but it is certain not the prevailing problem for most, IMHO.
Was wondering if bast525(the creator of the thread) was ever able to adb shell while in recovery, and if so what did you do thanks.
Heh, I wish.... I've tried just about every method posted on these forums, and five different SD cards from Sandisk, PNY, and Kingston. The only thing I haven't tried is rolling back to the pre OTA update, because I don't want to wipe the phone at this point.

[Q] ICS connect to computer?

So incredibly stupid question, and not even sure how to search for it to get an answer... but I want to connect my touchpad to my computer like I used to with CM7 and transfer files over. Normally when I connected it in the past I'd get a little notification telling me I can turn on usb storage or whatever... that doesn't show up now with CM9... what do I do?
If you read the wiki, it doesnt work with cm9 yet. Boot into recovery, go to Mounts and Storage, then go down to Mount USB Storage.
xanderharris86 said:
So incredibly stupid question, and not even sure how to search for it to get an answer... but I want to connect my touchpad to my computer like I used to with CM7 and transfer files over. Normally when I connected it in the past I'd get a little notification telling me I can turn on usb storage or whatever... that doesn't show up now with CM9... what do I do?
Click to expand...
Click to collapse
Try using Wifi File manager apps.
I use the Wifi File Explorer Pro do transfer files from my PC to android devices. No physical connection is needed since it's done through wifi.
Install this app (or others. They seem to work very similarly) and launch the app on the device. Leave it running so if you have a lot of files, you might want to keep it plugged into a charger.
The apps will give you an IP address.
Go to your PC and launch a web browser. Type in the address the app gave you. You are now connected. Go to the folder you need to add files to and search your PC for files to transfer. Done...
xanderharris86 said:
So incredibly stupid question, and not even sure how to search for it to get an answer... but I want to connect my touchpad to my computer like I used to with CM7 and transfer files over. Normally when I connected it in the past I'd get a little notification telling me I can turn on usb storage or whatever... that doesn't show up now with CM9... what do I do?
Click to expand...
Click to collapse
What I'm told you are supposed to do is to open /Settings/Developer Options and uncheck Android debugging. Then when you connect to a Windows computer, it will see the TP as an MTP device.
Unfortunately, I've yet to get this to work. I've tried a couple of Win7 boxes and both see the TP as an MTP device and try to load drivers for it. But after a couple of minutes trying, it pops up an error message saying if failed to load the drivers. On an XP box the only option you get when you plug in the TP are to use either Media Center or Winamp, both of which seem to look only for "media" files.
The only way I've found to transfer files directly to/from the TP is to reboot and choose Clockwork Mod from the boot menu and then /mounts and storage/mount USB storage. Then your TP appears as a regular USB hdd on whatever computer you connect.
I've tried to google for MTP support but the only things I've found relate to connecting Digital Cameras.
Okay so no offense but you all have it wrong. I can see my CM9 Alpha 2 in my Windows 7 desktop machine just fine. You need to do the following:
1) Go into Settings
2) Click on the Storage
3) Up in the right top corner of your TouchPad screen you see 3 boxes, click (touch) that.
4) Then click (touch) USB computer connection that pops up
5) Now make sure the box labeled Media device (MTP) is checked
DONE! You should be able to connect your TouchPad booted into CM9 Alpha 2 and transfer files over to it just fine. Mine comes up as cm_tenderloin on my Windows 7 64-bit if I recall correctly!
I hope this helps and I hope it works! Let me know!
xanderharris86 said:
So incredibly stupid question, and not even sure how to search for it to get an answer... but I want to connect my touchpad to my computer like I used to with CM7 and transfer files over. Normally when I connected it in the past I'd get a little notification telling me I can turn on usb storage or whatever... that doesn't show up now with CM9... what do I do?
Click to expand...
Click to collapse
Read this thread, I think that the information you're looking for could be here.
forum.xda-developers.com/showthread.php?t=1508572
alias4ever said:
Okay so no offense but you all have it wrong. I can see my CM9 Alpha 2 in my Windows 7 desktop machine just fine. You need to do the following:
1) Go into Settings
2) Click on the Storage
3) Up in the right top corner of your TouchPad screen you see 3 boxes, click (touch) that.
4) Then click (touch) USB computer connection that pops up
5) Now make sure the box labeled Media device (MTP) is checked
DONE! You should be able to connect your TouchPad booted into CM9 Alpha 2 and transfer files over to it just fine. Mine comes up as cm_tenderloin on my Windows 7 64-bit if I recall correctly!
I hope this helps and I hope it works! Let me know!
Click to expand...
Click to collapse
This worked for me, Thanks alias4ever!
alias4ever said:
Okay so no offense but you all have it wrong. I can see my CM9 Alpha 2 in my Windows 7 desktop machine just fine. You need to do the following:
1) Go into Settings
2) Click on the Storage
3) Up in the right top corner of your TouchPad screen you see 3 boxes, click (touch) that.
4) Then click (touch) USB computer connection that pops up
5) Now make sure the box labeled Media device (MTP) is checked
DONE! You should be able to connect your TouchPad booted into CM9 Alpha 2 and transfer files over to it just fine. Mine comes up as cm_tenderloin on my Windows 7 64-bit if I recall correctly!
I hope this helps and I hope it works! Let me know!
Click to expand...
Click to collapse
after you transfer file from the comp to tp via this method, how do you find the file on the tp?
Thanks
na_tra said:
after you transfer file from the comp to tp via this method, how do you find the file on the tp?
Thanks
Click to expand...
Click to collapse
The same way you'd find any other file on the TP. Use a File Manager such as Root Explorer.
lewmur said:
The same way you'd find any other file on the TP. Use a File Manager such as Root Explorer.
Click to expand...
Click to collapse
thanks for your help
I'll have to try this MTP option. I've just been using the wifi file browsers like Airdroid or booting into WebOS for file transfer. Thanks.

Problems with Rooting, Errors with dd

I have extracted the two files from gtvhacker to my desktop and when I try to run the dd command It comes up with this error. Error opening output file: 3 The system cannont find the path specified. Im kind of stuck and have searched the forums and I am having some trouble coming up with a solution. If anyone can help it would be much appreciated as I dont want to plug in my chromecast for OTA before I do this. Thanks!
I'm not totally for sure, but if you're just opening a command-prompt window(black DOS prompt screen) from any folder other than the folder that the "dd" program is in and trying to just type in "dd" at the prompt, it won't work. You can only run the "dd" command by either 1.) opening the command-prompt window from inside the folder with the "dd" program 2.) If you open the command-prompt window from outside the program's folder, just navigate to that folder OR. 3.) Make sure your environment path variables are set properly, so that you can execute the "dd" command from within any folder. Try that, it sounds like that's your problem. I could be wrong, but it's at least worth looking into...
Sent from my VZW Galaxy S3 using Tapatalk 4 Beta
jsdecker10 said:
I'm not totally for sure, but if you're just opening a command-prompt window(black DOS prompt screen) from any folder other than the folder that the "dd" program is in and trying to just type in "dd" at the prompt, it won't work. You can only run the "dd" command by either 1.) opening the command-prompt window from inside the folder with the "dd" program 2.) If you open the command-prompt window from outside the program's folder, just navigate to that folder OR. 3.) Make sure your environment path variables are set properly, so that you can execute the "dd" command from within any folder. Try that, it sounds like that's your problem. I could be wrong, but it's at least worth looking into...
Sent from my VZW Galaxy S3 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'm getting this problem too, and I have tried all the solutions you posted - no luck!
error with dd
StuMcBill said:
I'm getting this problem too, and I have tried all the solutions you posted - no luck!
Click to expand...
Click to collapse
Try this dd if=gtvhacker-chromecast.bin of=\\.\x: bs=1024 "x" being the letter of the usb
This isn't necessarily a solution to your dd issue (As I'm going to recommend another program), but I'm lazy and just use USB Image Tool to flash all my Chromecast images. It's 2 button clicks to flash the USB drive and I've never had it fail.
USB Image Tool Link
I had issues running DD on a Windows 7 machine. I eventually switched to an old XP machine and got it to work.
I'd second the recommendation of using another program. I suspect your issues will go away.....
ften said:
This isn't necessarily a solution to your dd issue (As I'm going to recommend another program), but I'm lazy and just use USB Image Tool to flash all my Chromecast images. It's 2 button clicks to flash the USB drive and I've never had it fail.
USB Image Tool Link
Click to expand...
Click to collapse
I agree. It's like this... You can get on a boat in SoCal, cruise over to Japan, then fly to Australia, and finally swim across the Pacific to the Baja in Mexico... or you can just take your chances crossing the border straight over into Mexico from SoCal. Same result, less hassle Lol I've used both the USB Image Tool and win32diskimager with great success. Take your pick. Both are just a few clicks and darn near stress-free.
sic0048 said:
I had issues running DD on a Windows 7 machine. I eventually switched to an old XP machine and got it to work.
I'd second the recommendation of using another program. I suspect your issues will go away.....
Click to expand...
Click to collapse
Sent from my VZW Galaxy S3 using Tapatalk 4 Beta
jsdecker10 said:
I agree. It's like this... You can get on a boat in SoCal, cruise over to Japan, then fly to Australia, and finally swim across the Pacific to the Baja in Mexico... or you can just take your chances crossing the border straight over into Mexico from SoCal. Same result, less hassle Lol I've used both the USB Image Tool and win32diskimager with great success. Take your pick. Both are just a few clicks and darn near stress-free.
Sent from my VZW Galaxy S3 using Tapatalk 4 Beta
Click to expand...
Click to collapse
ften said:
This isn't necessarily a solution to your dd issue (As I'm going to recommend another program), but I'm lazy and just use USB Image Tool to flash all my Chromecast images. It's 2 button clicks to flash the USB drive and I've never had it fail.
USB Image Tool Link
Click to expand...
Click to collapse
So to use the USB Image Tool I just plug in the microUSB cable to my Chromecast, hold down the button and plug the cable into my computer, and run the Image Tool to copy the gtvhacker-chromecast-12940.bin from my computer onto the Chromecast?
Or do I need to have the Chromecast plugged in to the TV as described for using the OTG cable on the GTVhacker site?
edit: OK. So after more research the Image Tool simply applies the .bin file to the USB stick. The rest of the process is the same as listed on the GTV site, correct?
FireRaider said:
So to use the USB Image Tool I just plug in the microUSB cable to my Chromecast, hold down the button and plug the cable into my computer, and run the Image Tool to copy the gtvhacker-chromecast-12940.bin from my computer onto the Chromecast?
Or do I need to have the Chromecast plugged in to the TV as described for using the OTG cable on the GTVhacker site?
edit: OK. So after more research the Image Tool simply applies the .bin file to the USB stick. The rest of the process is the same as listed on the GTV site, correct?
Click to expand...
Click to collapse
Correct
Sent from my XT897 using xda app-developers app

Phone memory?

Can anyone tell me why memory phone is shown as a card and not as phone and why is named 0?
Also, I can't connect phone to usb because because something is going on with phone tethering or idk.. Is there any way to fix that?
billaras481 said:
Can anyone tell me why memory phone is shown as a card and not as phone and why is named 0?
Also, I can't connect phone to usb because because something is going on with phone tethering or idk.. Is there any way to fix that?
Click to expand...
Click to collapse
For your first question, I don't really know the exact truth, but somewhat in 4.3 Sony changes the emulation directory, resulting in a newer location of those two storages.
Now, internal storage can be explored with:
/storage/emulated/0/
And external:
/storage/removable/sdcard1
Maybe because of such emulation, ES File Explorer unable to show the old "sdcard0" label because as far I can remember the old emulation directory was named "sdcard0" and not 0. Plus it was in /storage's root.
Your second question, I cannot help you with that as there are not many infos you are trying to expose. How about starting your phone on a safe mode by holding power button then long tap the power off selection on screen. Then you will be prompted about rebooting to safe mode. Tap OK.
After reboot, try connecting your phone with USB again
TechnoSparks said:
For your first question, I don't really know the exact truth, but somewhat in 4.3 Sony changes the emulation directory, resulting in a newer location of those two storages.
Now, internal storage can be explored with:
/storage/emulated/0/
And external:
/storage/removable/sdcard1
Maybe because of such emulation, ES File Explorer unable to show the old "sdcard0" label because as far I can remember the old emulation directory was named "sdcard0" and not 0. Plus it was in /storage's root.
Your second question, I cannot help you with that as there are not many infos you are trying to expose. How about starting your phone on a safe mode by holding power button then long tap the power off selection on screen. Then you will be prompted about rebooting to safe mode. Tap OK.
After reboot, try connecting your phone with USB again
Click to expand...
Click to collapse
I can't connect my phone to PC because PC cannot find any driver.I could connect it before I install a ROM... (phone is rooter)
Phone just loads but when I click to connect on MTP mode nothing happens.. PC just doesn't install any driver while drivers were installed before.
billaras481 said:
I can't connect my phone to PC because PC cannot find any driver.I could connect it before I install a ROM... (phone is rooter)
Phone just loads but when I click to connect on MTP mode nothing happens.. PC just doesn't install any driver while drivers were installed before.
Click to expand...
Click to collapse
My God! I am so sorry that I left this thread hanging without helping you! Are you still on xda? Do you still encountering this problem? If you could respond to this thread, I would like to resume our long lost conversation.
TechnoSparks said:
My God! I am so sorry that I left this thread hanging without helping you! Are you still on xda? Do you still encountering this problem? If you could respond to this thread, I would like to resume our long lost conversation.
Click to expand...
Click to collapse
Sir, the problem was solved long ago! Thanks for your kindness!
billaras481 said:
Sir, the problem was solved long ago! Thanks for your kindness!
Click to expand...
Click to collapse
Very nice to know that. Again apologise for my lack of attention. It is actually quite impolite to leave people hanging.

Please Help - Flashed Marshmallow 6.0 now only 24 gb space on 64 gb phone!

As title says. Also when I connect to USB into my windows computer the N6
icon appears, when I click on it its blank, no files! I tried to copy my pics and it
says devise cannot accept!
Seems my storage partition is somehow lost. I tried to reflash 2x, same result.
Can anyone guide me on what to do.
CC
cc999 said:
As title says. Also when I connect to USB into my windows computer the N6
icon appears, when I click on it its blank, no files! I tried to copy my pics and it
says devise cannot accept!
Seems my storage partition is somehow lost. I tried to reflash 2x, same result.
Can anyone guide me on what to do.
CC
Click to expand...
Click to collapse
Try doing a factory reset from within Android, I hope this helps.
http://forum.xda-developers.com/nexus-6/help/64gb-stuck-23gb-t2970279
Read down a few posts. It worked for me on 5.1.1.
I also have the same problem but with the 32gb version.
I started with a locked unrooted 5.1.1 Nexus 6.
I followed the instructions from Google's file image site.
I unlocked the boot loader.
Then ran the flash all script that failed, so I manually flashed the phone.
Phone rebooted and started up fine.
I attempted to re-lock the boot loader but it failed.
When connected to a windows system the phone shows up on auto play but file explorer shows No files or folders.
Tried a factory wipe still nothing.
worked
knightsh said:
http://forum.xda-developers.com/nexus-6/help/64gb-stuck-23gb-t2970279
Read down a few posts. It worked for me on 5.1.1.
Click to expand...
Click to collapse
That worked! TY
Now my last problem, when I enable USB debugging, plug into computer accept the computer
on the N6 and then I goto transfer my music files etc like I have done a million times before,
The icon appears on the computer when I double click its empty and I cannot
write to it! Any suggestions?
CC
This happened to me. I performed the advice recommended above and this fixed it for me
Edit: Ha. You just beat me.
copy
danieljw said:
This happened to me. I performed the advice recommended above and this fixed it for me
Edit: Ha. You just beat me.
Click to expand...
Click to collapse
Can you copy files to device with usb?
CC
cc999 said:
Can you copy files to device with usb?
CC
Click to expand...
Click to collapse
Yes. The phone defaults to charge-only mode via USB, which prohibits file transfer; this is why the device folder was empty in Windows. Switch to MTP mode via the notification shade and it will appear as it normally does.
In addition, in Developer options, you can configure the default USB mode, so as to prevent this from happening in the future.
or, just move into the 21st century, and use a program like wifi explorer pro, and never have to connect with a usb cable to transfer anything ever again..
wase4711 said:
or, just move into the 21st century, and use a program like wifi explorer pro, and never have to connect with a usb cable to transfer anything ever again..
Click to expand...
Click to collapse
Agreed that apps like this are very convenient. Sometimes still prefer hardwiring for transferring 20-30 GB worth of stuff, even though MTP is a total drag.
danieljw said:
Yes. The phone defaults to charge-only mode via USB, which prohibits file transfer; this is why the device folder was empty in Windows. Switch to MTP mode via the notification shade and it will appear as it normally does.
In addition, in Developer options, you can configure the default USB mode, so as to prevent this from happening in the future.
Click to expand...
Click to collapse
This fixed my Issue. It was set to MTP but I switched it to Charge only then back to MTP and it works now.
Thank you.
with a fast wifi connection, its not really much slower to transfer big stuff as well; although, how often are you transferring 20-30 gigs of stuff???
I think I have used the cable to transfer maybe 3 or 4 times since I got this phone..wireless charging, no cables to transfer files, its time to embrace 2015!
TWRP Resize partition function
Addressing just the problem posed in the title of this thread, if you have TWRP installed, or if you choose to install it after you discover this problem, then you have an option that will preserve your data: use the new "resize partition" function within recovery.
Boot to TWRP (version 2.8.7.1 or higher)
Choose "Wipe" button (do not slide yet!!) then "Advanced Wipe" button.
Select the Data partition, then "Repair or Change File System" button.
Choose the Resize button.
Now you can slide to confirm, and it will expand the partition to it's full potential, without disturbing the data.
danieljw said:
Yes. The phone defaults to charge-only mode via USB, which prohibits file transfer; this is why the device folder was empty in Windows. Switch to MTP mode via the notification shade and it will appear as it normally does.
In addition, in Developer options, you can configure the default USB mode, so as to prevent this from happening in the future.
Click to expand...
Click to collapse
Sorry for OT:
Definitely doesn't work on a rooted Nexus 5. It always jumps back to charge only. Does this work 100% on Nexus 6 devices?
File transfer also doesn't work properly for me (and at least one other person in the NExus 5 Troubleshooting subforums), if you want to move a folder onto the SD card which has a system file and / or subfolders in it, it will most likely fail. There are also a lot of folders not showing in Windows Explorer, so if i.e. I want to move Titanium Backup files to the SD card I just can't place a folder and name it "Titanium Backup" because it won't get recognized. I have to create a dummy folder, place the backup files in there and then move them manually with ES File Explorer to the now visibile real TB folder.
That bothered me so much I did a rollback to Lollipop, hopefully those things get fixed by Google or with an Xposed module (if this is working somewhen).

Categories

Resources