Related
By now some of you are anticipating in getting one & have researched every known articles. But while reading all these wonderful articles, I kept asking myself, "how about dev'n these bad boys. Is it easy to root, load a new ROM & recover from a brick?"
Let me tell you it's ridiculous easy to root, install recovery & ROMs and recover from an unbootable device.
Here's the basics on recovering from an unbootable device by booting into fastboot & re-installing
Press "POWER" until you see the Google logo then press "VOL DOWN". If you did it correctly, you should be in bootloader.
Download the N7 Google Image then plug your device to a Mac/Linux & type "./flash-all.sh" & wait 5-10mins. It's that simple.
You can go into the Dev forum to learn how to root, install recovery & location of the Google N7 image.
I left out the screen, storage, & etc... because you can find it here or on the net.
EDIT:
will include the full instructions since I assume you had Android SDK installed on your system
1. Download & unrar Google's Android SDK
http://developer.android.com/sdk/index.html
2. use the SDK to download platform-tools
2. download Googles N7 image & unrar in the platform-tools folder
https://developers.google.com/android/nexus/images#nakasi
3. make sure N7 is in bootloader (hit power & hit vol down when you see the google logo)
4. plug to your Mac or linux box
5. open up terminal & CD into the folder that has the N7 image (.../.../platform-tools/N7 folder)
6. type ./flash-all.sh or sudo ./flash-all.sh
7. you are now back to stock
That concludes it, I'm just your typical geek, flash happy gadget dude.
Apps used in testing:
stock text/PDF reader, video & music player
MX Player w/ ARM7 neon plugin
Stick It player with plugin
Quick Office Pro
Root Explorer
Hardware used:
I/O Nexus 7
Belkin 2 Port USB powered hub
generic OTG
generic usb sdcard adapter
32gb microSD
Files used:
text & pdf file
MP3
MKV anime
AVI XVID
Formatting sdcard via
formatted FAT32 & NTFS using Win 7 pc
formatted EXT3 & EXT4 using G-Parted from linux (VMWare WS running Ubuntu)
1st testing:
FAT32 & NTFS: I copied the files from the PC to the sdcard.
EXT3 & EXT 4: I copied the files from linux (VMWare WS running Ubuntu) to the sdcard.
results from 1st testing:
FAT32 & NTFS: Unable to read PDF's & play the video files
EXT3 & EXT 4: Unable to read PDF's & play video files
2nd testing:
I copied the files from the PC to the tablet & will then transfer the files from the tablet to FAT32, EXT3 & EXT4 sdcards
results from 2nd testing:
FAT32: Unable to play music, video files & read PDF
EXT3: able to play the music, video files & read PDF
EXT4: able to play the music, video files & read PDF
3rd testing:
I used AirDroid to copy files from Linux to the tablet & will then transfer the files from the tablet to FAT32, EXT3 & EXT4 sdcards.
results from 3rd testing:
FAT32: Did not test
EXT3: able to play the music, video files & read PDF
EXT4: able to play the music, video files & read PDF
what about windows?
RMXO said:
Let me tell you it's ridiculous easy to root, install recovery & ROMs and recover from a brick device.
Here's the basics on recovering from a brick device.
Press "POWER" until you see the Google logo then press "VOL DOWN". If you did it correctly, you should be in bootloader.
Download the N7 Google Image then plug your device to a Mac/Linux & type "./flash-all.sh" & wait 5-10mins. It's that simple.
Click to expand...
Click to collapse
Good to know that it is that easy to recover from a bricking. Sorry you had to find out how, though
rcrd-pt said:
what about windows?
Click to expand...
Click to collapse
My advice for folks on Windows that don't have a Mac or linux box is to download & install Sun's VirtualBox & install Ubuntu. It's very easy to do & doesn't take up much space.
revmra said:
Good to know that it is that easy to recover from a bricking. Sorry you had to find out how, though
Click to expand...
Click to collapse
No need to apologize, I was wondering how long before I took me to brick & learn how to get it back to stock. I'm now more comfortable in messing around with the device since I know I can restore it back to stock within 5-10mins.
RMXO said:
reserved for my power hub & MHL testing later
Click to expand...
Click to collapse
yeah, that really begs the question of whether I can plug OTG into a powered usb hub to use peripherals and a mass storage device AND charge at the same time.
Will be interesting to see:highfive:.
@RMXO
You previously confirmed read write EXT3 EXT4 on OTG. Is that correct?
Hemidroids said:
@RMXO
You previously confirmed read write EXT3 EXT4 on OTG. Is that correct?
Click to expand...
Click to collapse
That is correct, I created a folder & moved files from the tablet using Root Explorer
I don't know if you have already stated this or not, but have you tried putting it into the tablet ui?
doctahjeph said:
I don't know if you have already stated this or not, but have you tried putting it into the tablet ui?
Click to expand...
Click to collapse
how do i put it in tablet UI? my current DPI is 213 but that shouldn't matter though. Correct me if I'm wrong here.
RMXO said:
how do i put it in tablet UI? my current DPI is 213 but that shouldn't matter though. Correct me if I'm wrong here.
Click to expand...
Click to collapse
It does in the build prop lower the density to 160 using root explorer
Are you able to read from an otg devices without a hub?
Sent from my PG86100 using Tapatalk 2
aaronpoweruser said:
It does in the build prop lower the density to 160 using root explorer
Are you able to read from an otg devices without a hub?
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
I need to redo my testing on EXT3 & EXT4 from an OTG cable only.
Man, I can barely read anything with 160 DPI.
RMXO said:
I need to redo my testing on EXT3 & EXT4 from an OTG cable only.
Man, I can barely read anything with 160 DPI.
Click to expand...
Click to collapse
Did the UI change when you put it to 160 or did it stay in the phone UI?
doctahjeph said:
Did the UI change when you put it to 160 or did it stay in the phone UI?
Click to expand...
Click to collapse
Sorry I have yet to test tablet mode & won't do it until later. I just want to finish up what I'm doing now & then redo testing in tablet UI. Plus, I'm probably going to redo my testing later, I've been up this for a while & now my brain is fried.
RMXO said:
Sorry I have yet to test tablet mode & won't do it until later. I just want to finish up what I'm doing now & then redo testing in tablet UI. Plus, I'm probably going to redo my testing later, I've been up this for a while & now my brain is fried.
Click to expand...
Click to collapse
Awesome! Thank you so much for this. Get some rest. Maybe you can do a seperate thread for tablet ui testing.
doctahjeph said:
Awesome! Thank you so much for this. Get some rest. Maybe you can do a seperate thread for tablet ui testing.
Click to expand...
Click to collapse
I'm completely redoing all my testing with hopefully less confusing test methods. Once, I get done with that, I will re-do everything in Tablet UI mode.
Thank you for going to such great depths with this testing RMXO - it's reassuring for all of us that don't yet have our hands on our ordered N7's that there is hope It's greatly appreciated.
Revised my testing methods & posted results in thread #2
Thank you for all the testing and for passing along what you learned.
If you would, could you lay out what downsides, if any, there are to rooting?
I ask because I discovered I could not play movies from Google on my rooted phone.
I don't regret rooting my phone because the benefits (CM9 !) exceed the inconvenience by a mile.
I might think twice about rooting my tablet, 'cause I want to be able to rent or buy protected content without jumping through hoops.
danny8 said:
Thank you for all the testing and for passing along what you learned.
If you would, could you lay out what downsides, if any, there are to rooting?
I ask because I discovered I could not play movies from Google on my rooted phone.
I don't regret rooting my phone because the benefits (CM9 !) exceed the inconvenience by a mile.
I might think twice about rooting my tablet, 'cause I want to be able to rent or buy protected content without jumping through hoops.
Click to expand...
Click to collapse
Yo're welcome & I honestly can't answer the downside of rooting because I love tinker & the only way to do that is to root. Actually, by rooting, you open yourself to bricking your device. That is the extreme case if you don't know what you are doing & can't follow directions properly. I've listed a way to recover from a bricked N7 device.
There is an app called "Voodoo OTA Rootkeeper" that allows you to unroot & go back to root when needed.
My tablet is unlocked, rooted & able to play movies from the Google Play Store.
After testing CM10 for a while (thx codeworx) I now ported my NanoBoot image to CM10.
Changes compared to original CM10 boot:
"insecure" (means: / and /system mounted read-write (easy 'adb push' into /system ...), ro.secure = 0)
support for /system/etc/init.d/ init scripts
(somewhat) easy UMS access
Changes in r10:
Use 179:24 instead of 179:25 as address for UMS (fixes UMS on Windows)
to enable UMS for external SD with this boot.img it is enough to do:
Code:
setprop sys.usb.config mass_storage,adb
to return to MTP:
Code:
setprop sys.usb.config mtp,adb
TIP:
If you use Linux you may use some function like:
Code:
ums () {
if [[ $1 == "+" ]]; then
adb root
sleep 2
adb -s c1607c00051963f shell 'setprop sys.usb.config mass_storage,adb'
else
adb root
sleep 2
adb -s c1607c00051963f shell 'setprop sys.usb.config mtp,adb'
fi
}
'ums +' will enable UMS, 'ums -' will disable UMS on your tablet (not to mention it needs to be connected (...))
replace '-s c1607c00051963f' with '-s <your adb id>' - you get the id via 'adb devices'.
If you only got one adb-enabled device, you could remove '-s c1607c00051963f' from the commands.
If there's more than one device connected adb needs to know which one should receive the commands.
I did not yet have the time to modify framework-res.apk to add UMS to the list of options...
Flash using img/pit with either Odin or Heimdall. Or use zip to flash using CWM.
Images for Odin/Heimdall
PIT:
p3100.pit http://downloads.nanolx.org/P3110/p3100.pit
p3110.pit http://downloads.nanolx.org/P3110/p3110.pit
Stock CM10 Kernel:
NanoBoot-r10-CM10.img http://downloads.nanolx.org/P3110/NanoBoot-r10-CM10.img
Johnsel's CM10OC Kernel:
-No WiFi-
Zips for CWM
Stock CM10 Kernel:
NanoBoot-r10-CM10.zip http://downloads.nanolx.org/P3110/NanoBoot-r10-CM10.zip
Johnsel's CM10OC Kernel:
-No WiFi-
Tried this on my P3113 and it broke my WiFi.
Macadamia Daze said:
Tried this on my P3113 and it broke my WiFi.
Click to expand...
Click to collapse
Here with 3110 it works... if you provide me the original 3113 boot.img, I can re-pack one, that should work.
And it only works with Cyanogen Mod 10. Not on 9 or stock rom.
Setialpha said:
Here with 3110 it works... if you provide me the original 3113 boot.img, I can re-pack one, that should work.
And it only works with Cyanogen Mod 10. Not on 9 or stock rom.
Click to expand...
Click to collapse
I am using CM10, so here's the original boot.img for CM10 on the P3113. You don't need the stock one, do you?
Macadamia Daze said:
I am using CM10, so here's the original boot.img for CM10 on the P3113. You don't need the stock one, do you?
Click to expand...
Click to collapse
try with attached CWM zip.
n00b here.....what does this do??
Sent from my GT-P3113 using Tapatalk 2
F3AR420 said:
n00b here.....what does this do??
Sent from my GT-P3113 using Tapatalk 2
Click to expand...
Click to collapse
Just as first post says. This is a modified boot image for cyanogen mod 10 (no other ROM supported!) for galaxy tab 2 7", which makes / and /system read-write, adds support for init-scripts and adds pretty easy way to access UMS (USB Mass Storage) for external SD-Card.
According to your signature you're using an incompatible rom anyway - so don't use this.
@Macadamia Daze: now also tested with a 3100 I got my hands on: WiFi works. Dunno why it doesn't work with 3113 (I got no clue whether 3113 has some special WiFi stuff or whatever). Either way, please tell me, whether the attached one for 3113 (two posts above) works with WiFi.
Setialpha said:
@Macadamia Daze: now also tested with a 3100 I got my hands on: WiFi works. Dunno why it doesn't work with 3113 (I got no clue whether 3113 has some special WiFi stuff or whatever). Either way, please tell me, whether the attached one for 3113 (two posts above) works with WiFi.
Click to expand...
Click to collapse
Silly me; the problem was an incompatible kernel (Johnsel's). I returned to the default CM10 kernel and reflashed this, so now WiFi works. Still, in Windows it doesn't work properly. While it does create a new removable disk in Computer, it gives the "Please insert a disk into drive" error when I try to open it. Haven't tested in Linux yet, but based on my earlier tests with your previous UMS solution, it probably works.
---------- Post added at 08:12 PM ---------- Previous post was at 07:22 PM ----------
Ooh, I have good news! I used Device Manager to examine the blank drive letter on the computer, and it was recognizing it basically like an SD card reader with no SD card. So, I decided to poke around some of the files referenced in your UMS script from before to check their values. When I tried to open /sys/devices/virtual/android_usb/android0/f_mass_storage/lun/file, I got an error. Thinking it may not be working properly, I created a file on my computer with the contents "/dev/block/vold/179:24" and ADB pushed it to overwrite the broken file. Instantly, my SD card mounted on the PC. I hope this is useful information for you!
Macadamia Daze said:
Silly me; the problem was an incompatible kernel (Johnsel's). I returned to the default CM10 kernel and reflashed this, so now WiFi works. Still, in Windows it doesn't work properly. While it does create a new removable disk in Computer, it gives the "Please insert a disk into drive" error when I try to open it. Haven't tested in Linux yet, but based on my earlier tests with your previous UMS solution, it probably works.
---------- Post added at 08:12 PM ---------- Previous post was at 07:22 PM ----------
Ooh, I have good news! I used Device Manager to examine the blank drive letter on the computer, and it was recognizing it basically like an SD card reader with no SD card. So, I decided to poke around some of the files referenced in your UMS script from before to check their values. When I tried to open /sys/devices/virtual/android_usb/android0/f_mass_storage/lun/file, I got an error. Thinking it may not be working properly, I created a file on my computer with the contents "/dev/block/vold/179:24" and ADB pushed it to overwrite the broken file. Instantly, my SD card mounted on the PC. I hope this is useful information for you!
Click to expand...
Click to collapse
I see... 179:24 is the sdcard itself, 179:25 (what I use) is the first partition on the sdcard... unixoid systems don't care about that, but windows seems too... I'm gonna test with 179:24 on Linux and if it works there (I'd say yes even without testing, I provide an update). Thanks for testing.
r10 is now online - fixes UMS issue on Windows.
I can't get WiFi to work with Johnsel's CM10OC Kernel - so I skiped uploading those image/zip...
You can find me in Freenode #cyanogenmod-dev if you care to sort out what's happening with the wifi on my kernel
Johnsel said:
You can find me in Freenode #cyanogenmod-dev if you care to sort out what's happening with the wifi on my kernel
Click to expand...
Click to collapse
It fails to load something and therefore can't be enabled, don't remember exact log-message right now.
I'll contact you, when I'm hacking around the next time.
This is pretty interesting.
Two things
1-Doesn't CM10 already support init.d scripts?
2-Would it be possible to swap the mountpoints for the "internal" sdcard space and the actual microSD card slot? My current method of re-mounting things right after boot is OK but not very elegant.
DivinityCycle said:
This is pretty interesting.
Two things
1-Doesn't CM10 already support init.d scripts?
2-Would it be possible to swap the mountpoints for the "internal" sdcard space and the actual microSD card slot? My current method of re-mounting things right after boot is OK but not very elegant.
Click to expand...
Click to collapse
1 - atleast not via boot.img - that's why I added it.
2 - I have an older tablet I used before (ARNOVA 7C G2) it worked with this one, so it should work with this one, too. But you should never enable UMS while some app is running... On that other tablet I had to use EXT2 or EXT4 on SD-Card else all that permission stuff didn't work (FAT only has very basic permission rules for files). Also I recommend using second partition of SD-Card for /data. (first gets used as external storage and is managed by vold - at least that is what I did on my other tablet).
I attached init.espresso.rc, so that you can play around with the mount points (re-send me the file after you're done and I can provide you a flashable zip).
Setialpha said:
1 - atleast not via boot.img - that's why I added it.
2 - I have an older tablet I used before (ARNOVA 7C G2) it worked with this one, so it should work with this one, too. But you should never enable UMS while some app is running... On that other tablet I had to use EXT2 or EXT4 on SD-Card else all that permission stuff didn't work (FAT only has very basic permission rules for files). Also I recommend using second partition of SD-Card for /data. (first gets used as external storage and is managed by vold - at least that is what I did on my other tablet).
I attached init.espresso.rc, so that you can play around with the mount points (re-send me the file after you're done and I can provide you a flashable zip).
Click to expand...
Click to collapse
That's the thing I have been wrestling with lately, what's "the best" way to manage this stuff?
It seems like the main thing that needs to be done for legacy purposes is linking the regular /storage/sdcard0/data directory over to /storage/sdcard1/data/.
One idea I had was to format the "internal" sdcard (/storage/sdcard0) with ext4, which would allow symlinks to exist there, then just remove the data directory and replace it with a symlink that points to /storage/sdcard1/data.
From what I've read, ext4 is supposed to be a better, higher performance solution, so I'm kinda curious to try it out.
It would make UMS pretty worthless to Windows guys like me, but I basically do everything via network anyways (SFTP mostly).
Is it possible to control the file systems used on the internal & external sdcards in the init? I didn't look too deeply at it cuz I don't know how to rebuild a boot.img (at least not yet)
Tested this with the current AOKP JB nightly, and it also breaks WiFi. I'm trying now to keep the rom and restore the CM10 NanoBoot backup. Fingers crossed it will be stable.
editi guess sdcard is incorrect/confusing for my situation, it's the entire system up to root folders is stuck in a read-only type state.
I didn't really see anything that fits my current problem (sorry if there is an answer somewhere buried in here)
So to start off with info, I installed Android on the TP back in February for my fiancée just for the basics of email, videoplayer, comic reader, internet browsing. Nothing too extravagant, just something with more to offer than webos.
I never did any updates on it because it worked perfectly fine for what it was being used on.
I've changed out the video selection many times as she watches through the shows with no problems.
Now I go to change the files and I delete them, add the new stuff, all seems fine. Then I unmount it and everything I deleted is back and everything I added is gone. I've uninstalled apps and they come back, I've done updates to apps and they revert back to before the update.
I've gone into CMW and done the wipes and even formatted sdcard, cache, etc. Nothing works. Even mounting USB in CWM to add files gives the same result of them disappearing right after it is unmounted.
I've tried ACMEUnistaller but it doesn't work. I saw something flash by the screen about something failing, but it goes too fast to even really see what it's about.
Sorry this is so long. I appreciate any insight!
Kernel
2.6.35-palm-tenderloin
[email protected]ost #12
CyanogenMod version:
9.0.0-RC0-Touchpad-alpha2
Build Date
Mon, Feb 20 13:59:21 CST 2012
Build Number
IML74K
plasticsoldier said:
I didn't really see anything that fits my current problem (sorry if there is an answer somewhere buried in here)
So to start off with info, I installed Android on the TP back in February for my fiancée just for the basics of email, videoplayer, comic reader, internet browsing. Nothing too extravagant, just something with more to offer than webos.
I never did any updates on it because it worked perfectly fine for what it was being used on.
I've changed out the video selection many times as she watches through the shows with no problems.
Now I go to change the files and I delete them, add the new stuff, all seems fine. Then I unmount it and everything I deleted is back and everything I added is gone. I've uninstalled apps and they come back, I've done updates to apps and they revert back to before the update.
I've gone into CMW and done the wipes and even formatted sdcard, cache, etc. Nothing works. Even mounting USB in CWM to add files gives the same result of them disappearing right after it is unmounted.
I've tried ACMEUnistaller but it doesn't work. I saw something flash by the screen about something failing, but it goes too fast to even really see what it's about.
Sorry this is so long. I appreciate any insight!
Kernel
2.6.35-palm-tenderloin
[email protected] #12
CyanogenMod version:
9.0.0-RC0-Touchpad-alpha2
Build Date
Mon, Feb 20 13:59:21 CST 2012
Build Number
IML74K
Click to expand...
Click to collapse
I've run across this 3 times with TPs I work on....
1st one had to be sent back to HP because somehow internal memory was damaged and got locked in some some of read only mode
2nd one I saw, I went into webOS, installed the internalz app, mounted the TP to the computer, then added and erased some files and from then on all was good in both webOS and Android
3rd and 4th (same customer) had to be sent in to HP
Now let me mention I live in Costa Rica so all these have been exposed to several scans at airport security checkpoints. I mention this because I haven't seen anything close to a read only problem with the TPs in the USA
Sent from my aokp_tenderloin using Tapatalk 2
thank you so much for the info. Unfortunately Internalz didn't want to help the items stay deleted either. The stuck in read-only type mode is very weird.
I'm pretty sure I am 3 weeks out of the 1-year warranty on it, plus I am unable to remove android from it to even trick them that it just doesn't work.
I guess I'll try webos doctor and see if that can get it going.
edit: webos doctor not working, even with the closing it at 8-12% tricks and doing the lvm.static..... stuff... 'cause it of course doesn't see to actually delete anything... i'll have to double check tomorrow when i bought it, pretty sure it's over the year and since it turns on and has android kinda screwed
plasticsoldier said:
thank you so much for the info. Unfortunately Internalz didn't want to help the items stay deleted either. The stuck in read-only type mode is very weird.
I'm pretty sure I am 3 weeks out of the 1-year warranty on it, plus I am unable to remove android from it to even trick them that it just doesn't work.
I guess I'll try webos doctor and see if that can get it going.
edit: webos doctor not working, even with the closing it at 8-12% tricks and doing the lvm.static..... stuff... 'cause it of course doesn't see to actually delete anything... i'll have to double check tomorrow when i bought it, pretty sure it's over the year and since it turns on and has android kinda screwed
Click to expand...
Click to collapse
I would suggest trying to restore down to WebOS 3.0. In that procedure you literally wipe EVERYTHING on the internal partitions in novaterm and start from absolute scratch. Therefore, if it a software issue you could solve the problem. However, if it is a hardware issue, you'd be kinda screwed.
Yeah, none of the methods I've ended up finding about this problem or other bricked problems are working at all.
i checked at work when i bought it, which of course the 11th was the year mark... but I do have android installed so even if i can get any chance of them honouring it so close they'll probably be like "oh you have android, that'll be $$$ for us to do anything. thanks!"
So I guess I now I have a paperweight with some features.
cdzo72 said:
I've run across this 3 times with TPs I work on....
1st one had to be sent back to HP because somehow internal memory was damaged and got locked in some some of read only mode
2nd one I saw, I went into webOS, installed the internalz app, mounted the TP to the computer, then added and erased some files and from then on all was good in both webOS and Android
3rd and 4th (same customer) had to be sent in to HP
Now let me mention I live in Costa Rica so all these have been exposed to several scans at airport security checkpoints. I mention this because I haven't seen anything close to a read only problem with the TPs in the USA
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
When you got the tablets back had they been fixed or were they refurbs ? Did HP say anything about Android still being on it?
There is a thread in the General forum about how to restore and downgrade. Have you tried that thread ? It is usually a great way to try and get that last restore before sending it back to HP.
73 de VE6AY
Sent from my HP Touchpad, running the latest CM9 nightly, from the XDA Premium App
how are you adding and deleting files when in android? which version of android do you have installed? have you tried different rom versions? have you tried moving and/or deleting files over adb? are you using windows or linux on your computer that youre connecting the touchpad to? it doesnt make sense that the sdcard would be set to read only. is it only certain folders that you cant modify the contents of, or is it the entire sdcard? are you able to modify contents of folders in the / directory of the device using root file explorer or es file explorer in android? have you run "fix permissions"? Also, running webosdoctor wont wipe the sdcard contents or format the sdcard in any way. its going to change the data in the webos partition and may change some data in the /boot directory.
sstar said:
When you got the tablets back had they been fixed or were they refurbs ? Did HP say anything about Android still being on it?
Click to expand...
Click to collapse
They had been fixed but the owners sent them off and had to pay for the whole thing because they had Android on them. When I got my hands on them again I just reinstalled Android. HP charged a little over a hundred dollars for the fix
Sent from my aokp_tenderloin using Tapatalk 2
cdzo72 said:
They had been fixed but the owners sent them off and had to pay for the whole thing because they had Android on them. When I got my hands on them again I just reinstalled Android. HP charged a little over a hundred dollars for the fix
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the answer, this would tend to suggest that the problem is software based corrupted or otherwise. I am trying to find a program that will allow me to read/format the Android partition on my windows computer and will let you know if come up with anything.
Regards
i guess i should change the title slightly.. it's not sdcard, but basically the entire touchpad contents. go to root and delete whatever i want and it doesn't matter. connect it and format with windows and it doesn't actually matter.
haxin said:
how are you adding and deleting files when in android?
Click to expand...
Click to collapse
i've added and deleted just by using mtp. i've also deleted the files on the android side with the video player (vplayer) i've installed es file explorer (which after restart is gone) and deleted with that. i've also gone into webos and installed internalz pro and deleted files that way, which it then seems to work until i of course do anything related to restarting.
some of the files i've put on, i've had it recognize briefly. so for the video file, start it, then it gets really choppy/glitchy playing it. so stop it, go back into the vplayer and it's back to the old stuff
which version of android do you have installed? have you tried different rom versions?
Click to expand...
Click to collapse
android version 4.0.3. nothing else will install. if i add files while in android, when i boot into cwm they are gone. if i mount usb in cwm and add them they stay briefly but when i try to flash them they fail.
have you tried moving and/or deleting files over adb? are you using windows or linux on your computer that youre connecting the touchpad to?
Click to expand...
Click to collapse
i have not tried adb yet, just not as familiar using it properly, i will give it a try though.
i am using windows 7 on my laptop currently. i do have a pc upstairs that i barely use that has vista, but i don't know how that would make a difference to the touchpad
it doesnt make sense that the sdcard would be set to read only. is it only certain folders that you cant modify the contents of, or is it the entire sdcard?
Click to expand...
Click to collapse
yeah as i put above i guess saying sdcard was a bit confusing/misleading (my bad, sorry!), i didn't really know what else to call it at the time or how to explain myself properly at first.
are you able to modify contents of folders in the / directory of the device using root file explorer or es file explorer in android?
Click to expand...
Click to collapse
i can move/delete/modify anything which has absolutely no effect to the device. i've used es file explorer and gone up to root and deleted everything and the system runs fine. says the system is empty with lots of free space (its the 32gb model) but restart or even go into recovery and everything is once again there.
have you run "fix permissions"?
Click to expand...
Click to collapse
i've run it a few times. just acts likes it's working and then says done. i've even gone into the mounts and storage in cwm and formatted sdcard/cache/data/system. does nothing at all in the end of things
Also, running webosdoctor wont wipe the sdcard contents or format the sdcard in any way. its going to change the data in the webos partition and may change some data in the /boot directory.
Click to expand...
Click to collapse
it was just something to try to get somewhere right. it never gets past 12%. always fails to reboot.
I am currently letting the battery drain and see if it dying and then being charged will do anything. probably not. but who knows. i talked to a "tech" on the chat support (i never mentioned android) who told me that having preware installed in webos causing it to become corrupt and they "don't knowledge of preware installed devices" exact words. no idea what that means haha don't have knowledge, don't acknowledge...
anyhow. i've not quite given up. i just don't really see it turning out any differently from the previous times. i do appreciate all the feedback and help very much though
ok so heres what I would try. First try flashing a new fresh rom. download one that you want to your computer like cm9 nightly or aokp or whatever you feel like. then boot into CWM recovery connect the touchpad to the computer via usb. then connect to the touchpad with adb. I'm not sure how to do this in windows because it's been so long since I've done it on a windows box, I always use linux.
adb has alot of options, you can move files to and from the device, you can uninstall or install app packages, and more. this way you can adb push the rom .zip to the touchpad's sdcard while youre in cwm recovery. this way you dont have to reboot the touchpad and risk having the file disappear, you can just go to 'install zip from sdcard' and then 'choose zip from sdcard' in cwm recovery after you adb push the rom, you should see it in the folder you pushed it to on the sdcard.
If you arent familiar with how to use adb from the command line or the terminal this might not make alot of sense and i dont know how better to explain it than that. Also yes windows 7 vs windows vista does make a difference there are issues with novacom installing properly, that's why you would have problems running acmeuninstaller or acmeinstaller2. if you look around you should find some videos or how to's that can probably explain it better. Hope this helps.
http://www.webos-internals.org/wiki/Novacom_with_Windows_7
http://forums.webosnation.com/webos-internals/295881-webos-doctor-12-issue-fixed-5.html
http://forum.xda-developers.com/showthread.php?t=1426244 is the thread I was talking about - it allows you to access the hard root of the device, repartition it, and start again from scratch. It is what I was suggesting last night, from my tablet when I didn't have the link handy.
ve6ay said:
http://forum.xda-developers.com/showthread.php?t=1426244 is the thread I was talking about - it allows you to access the hard root of the device, repartition it, and start again from scratch. It is what I was suggesting last night, from my tablet when I didn't have the link handy.
Click to expand...
Click to collapse
Probably the best suggestion yet given that everything else has been tried.
Good luck.
****EDIT****
Before you attempt the step above I have just noticed a difference between between cwm and. TWRP2.2 which I have installed on my Touchpad via goo manager. If I open recovery via goo manager and then select wipe it gives me 4 options cache, davlik, factory reset AND system which i think says will remove your rom . I don't see the forth option available with the regular cwm/clockwork. Just a thought.
All the best with whatever you try next.
sstar said:
Probably the best suggestion yet given that everything else has been tried.
Good luck.
Click to expand...
Click to collapse
this would work, however you have to fix you novacom/novaterm issues on your windows machine before you'll be able to do any of this. the reason acmeuninstaller, acmeinstaller2 arent working is likely because youre on a windows7 64bit box and Palm-sdk, the novacomd.exe, noverm.exe, and javaruntime apps and drivers arent setup right. just make sure you have the proper javaupdates on your computer then you can install preware in webos, preware has some nice tools that will delete the entire android install partitions, one is called 'remove android' and the other is called 'tailor' you run them from within webos. after you do that then in webos you should do a full device reset. you'll find it in the "info" tab under settings in webos. this will delete and reformat the whole /media ,(aka sdcard) partition. so you will lose all the files you have stored on both webos and android. that format will take a long time probably like 30 min or more. after thats done. reboot the hp and run webosdoctor. now i know for sure this will work because ive done it on mine. remember to put the touchpad in developer mode in webos first to install preware. you can do that by typing webos20090606 into the webos search bar and hitting enter. I'll put links from my box.com accou t to everything you need.
https://www.box.com/s/479acdb6ef9c99fc7b92
https://www.box.com/s/1aed4722990aad251570
edit: also I'm not sure if youre on the 16gig 32gig or 64gig pad, the webosdoctor that i linked is for 32gig wifi only US version. if thats not what you have then youll need to get the doctor for for specific touchpad. or you could create a webosmetadoctor but thats a whole nother project.
i have the 32gb version. i assume US and Canadian aren't gonna make a difference
i've tried all those threads. any novacom/novaterm stuff doesn't work, the files won't delete so when trying to recreate they just error saying it already exists.
if the devices is on in androind the adb can find the device although the "Serial" has a bunch of ???? at the end of it. when i go to cwm adb cannot find the device.
in cwm i can mount and add files that way and go back to install zip sdcard but get:
Code:
--Installing /sdcard/aokp_tenderloin_milestone-4.zip
Finding update package...
Opening update package...
E: Can't open /sdcard/aokp_tenderloin_milestone-4.zip
(bad)
Installation aborted
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
plasticsoldier said:
i have the 32gb version. i assume US and Canadian aren't gonna make a difference
i've tried all those threads. any novacom/novaterm stuff doesn't work, the files won't delete so when trying to recreate they just error saying it already exists.
if the devices is on in androind the adb can find the device although the "Serial" has a bunch of ???? at the end of it. when i go to cwm adb cannot find the device.
in cwm i can mount and add files that way and go back to install zip sdcard but get:
Code:
--Installing /sdcard/aokp_tenderloin_milestone-4.zip
Finding update package...
Opening update package...
E: Can't open /sdcard/aokp_tenderloin_milestone-4.zip
(bad)
Installation aborted
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
Click to expand...
Click to collapse
ok no one will be able to help you fix this issue unless you give complete details of the problems. when you say " novacom/novaterm stuff doesn't work" we cant really help specific error details is what i need. I dont mind helping you fix this but you have to be a little more specific on exactly what,where, and how youre installing and running and mounting apps and directories.
your problem IS fixable but you need to slow down and really do things exactly step by step.
Ok so back to ./adb. now when you boot in to CWM recovery on he touchpad DONT do anything in CWM just plug it into the computer. do not mount it as a usb storage and dont mount or unmount the sd partition LEAVE IT.
you can then use ./adb from the command line or terminal on the computer to move the files to the touchpad' or install apk's uninstall apk's you name it. This will require that you know some linux terminal commands. for example to move a new rom zip to the internal sd card or into any other folder you can use ./adb push command to run a root shell on the android device itself you can use ./adb shell and then change folder and file properties from readonly to rw. this can all be done while the touchpad is patiently waitng in CWM recovery. this way when youre done installing or uninstalling apps from the device and moving flash zips to it, you can disconnect the .adb connection with ./adb disconnect or just type exit from the terminal till it closes. unplug it then you will be able to pick up the touchpad and install zip from the sdcard, keep in mind you dont want to choose 'apply u[date from sdcard' you want to use the 'install zip from sdcard option' you can read up more on how adb works. it is probally the most important part of hacking android.
with that being said. novaterm is the palm webos version of .adb. this is why when you boot into webos recovery to do things like acmeinstaller and acmeuninstaller2 the novaterm novacom and novacomd apps have to be installed correctly on the computer or else you wont be going anywhere fast. some screenshot examples of how it should appear below.
https://www.box.com/s/432e63a83215f00eea6a
https://www.box.com/s/970bc29542a05f98f036
https://www.box.com/s/63c0f656e8354f7f2d6a
https://www.box.com/s/cbe3266467ae8e3ebabe
https://www.box.com/s/005e56a61a178dd17fa4 some better resolution images.
Plasticsoldier said
used "remove android" in webos, but then nothing is different after the fact as usual. 'tailor' doesn't seem to exist anymore in preware at least that i can find
not sure if there is anything else I can do at this point
Yes there is
Firstly tailor does exist, it is a beta and the facility to dl must be enabled.
Read this and scroll down to Enabling beta test feeds and follow the instructions , when you get as far as using the Linux command you CAN copy and paste thank God.
http://en.m.webos-internals.org/wiki/Testing_Feeds?wasRedirected=true . After that reboot into Webos and launch preware. Go into managed feeds as per the instructions in the link above and install Tailor. Reboot again and the app will work. It looks very good actually.
But before attempting to actually use Tailor please read the article I have posted below it is only 7 pages long but will explain how to use Taylor properly as it is a powerful tool.
http://forums.webosnation.com/webos...partition-filesystem-editor-beta-testing.html
I have done all of this , this morning so if you have any problems pm me or ask in this thread.
I sincerely hope that this helps, it should be the answer to your problems.
@haxin: sorry, wasn't trying to be unhelpful when everyone is being helpful to me. I shall be more detailed in future responses. I think i was getting frustrated and had had a busy exhausting day so it didn't help me come across clearly/properly.
OK, so I had preware installed already, so I removed it, went into developer mode, used the linux commands, reinstalled preware, added Tailor.
(i've done this a few times, because I didn't remove the cable after doing the linux commands for preware, then i accidentally hit the wrong buttons and it connected to 'usb drive' mode and wouldn't connect on the pc side and got stuck on the "ow disconnected me properly next time" screen).
So it gives me the following options
USB (media)
Android (system)
Android (cache)
Android (data)
Unused Space
the 'usb media' starts mounted and will mount again if unmounted. If I use 'check filesystem' it'll pass. So then I try 'delete partition' which pretends to delete, then it takes me to the unused partition which is still at 16mb. so i try to use "check filesystem' again and it fails. try repair and it fails as well
I've tried mounting the android parts just to see, they just sit there processing that they are trying to mount. trying to delete or anything else fails as well.
and now after trying things, any of the 'cards' will try to open and just sit there grey. and with my usb cable not plugged in it still is giving me the option to enter usb drive mode. and with this i have to restart and go through the steps again of adding Tailor which is getting tedious.
I restarted, went through the motions to get back to Tailor. trying out resizing just to see how that goes. So far 15%. not sure what will happen when done, but we will see.
This is getting long, so i'll end this part and update on anything and also try to familiarize myself with adb a tad more
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).
I found something interesting. When i used the OTG checker, i noticed that 3 system files are disabled(they don't have full permissions).
Here's what you have to do(if the FIX button doesn't work)
1.Use a root explorer (Xplore is needed)
2.Find the files with the X from the screenshot
3. Change the permissions and check all the boxes.
4.Reboot and done!
Someone test this and comment if it does or if it doesn't work.
I didn't tried ( i didn't root yet) but i hope it will work
(Tried on my s4 mini and it worked)
Johnny TDN said:
I found something interesting. When i used the OTG checker, i noticed that 3 system files are disabled(they don't have full permissions).
Here's what you have to do(if the FIX button doesn't work)
1.Use a root explorer (Xplore is needed)
2.Find the files with the X from the screenshot
3. Change the permissions and check all the boxes.
4.Reboot and done!
Someone test this and comment if it does or if it doesn't work.
I didn't tried ( i didn't root yet) but i hope it will work
(Tried on my s4 mini and it worked)
Click to expand...
Click to collapse
Hey, just tried. I've fixed permission for android.hardware.usb.host.xml file and now the otg checker give me only green check. Rebooted the phone but when i plug in my usb pen anything happen
Zeph1990 said:
Hey, just tried. I've fixed permission for android.hardware.usb.host.xml file and now the otg checker give me only green check. Rebooted the phone but when i plug in my usb pen anything happen
Click to expand...
Click to collapse
You must do on the all files. Now only android.hardware.usb.host.xml
Zeph1990 said:
Hey, just tried. I've fixed permission for android.hardware.usb.host.xml file and now the otg checker give me only green check. Rebooted the phone but when i plug in my usb pen anything happen
Click to expand...
Click to collapse
Do it for all of the files. Not only on android.hardware.usb.host.xml
doesn't work..
you must make changes to kernel also for otg to work
snapdesign said:
doesn't work..
you must make changes to kernel also for otg to work
Click to expand...
Click to collapse
Did you checked all the boxes on the permissions?
Johnny TDN said:
Did you checked all the boxes on the permissions?
Click to expand...
Click to collapse
what do you see in the photo? also otg needs support from kernel... it doesn't work without it
i make a custom kernel with host permissions but doesn't work anyway...
Possible problem its software and managed vold's...
In the RAMDISK it's pointed correct for USB OTG
/devices/hisi-usb-otg/usb1/* auto auto defaults voldmanaged=usbotg:auto
BadWolfYe said:
i make a custom kernel with host permissions but doesn't work anyway...
Possible problem its software and managed vold's...
In the RAMDISK it's pointed correct for USB OTG
/devices/hisi-usb-otg/usb1/* auto auto defaults voldmanaged=usbotg:auto
Click to expand...
Click to collapse
can you make a kernel with multirom support?
edit: you are the same bad wolf from htcmania?
snapdesign said:
can you make a kernel with multirom support?
edit: you are the same bad wolf from htcmania?
Click to expand...
Click to collapse
Yes the same
And in this moment MultiROM its innecesary (no support for other roms only EMUI...)
BadWolfYe said:
Yes the same
And in this moment MultiROM its innecesary (no support for other roms only EMUI...)
Click to expand...
Click to collapse
well, someone is working on a cm build... when that will boot we should have a kernel with multirom...
i tried on more way too for OTG already,,, added lines too vold.fstab etc etc but it wont support,,,
UPDATE
My phone is rooted and i am testing it. Hope it works on mine. If it doesn't, the post should be removed
Hiya Fellas,
I was messing around with my development build last night and I was able to turn on USB host mode and successfully plug in and use a usb flash drive. Now keep in mind that this was on CM 13 but, this might also work on a rooted stock.
Using adb or terminal app.
1. Look for a path in /sys/devices that ends with hisi_usb (e.g /sys/devices/f4000000.hisi_usb)
2. Now inside that folder there should be a file called plugusb.
3. use this command
echo hoston > /sys/devices/f4000000.hisi_usb/plugusb
Replace "f4000000" with the real value.
Now plug in your device and see if it is recognized!
EDIT: You may need to be root to do this!
ADB: "adb root"
TERMINAL APP: "su"
Meticulus said:
Hiya Fellas,
I was messing around with my development build last night and I was able to turn on USB host mode and successfully plug in and use a usb flash drive. Now keep in mind that this was on CM 13 but, this might also work on a rooted stock.
Using adb or terminal app.
1. Look for a path in /sys/devices that ends with hisi_usb (e.g /sys/devices/f4000000.hisi_usb)
2. Now inside that folder there should be a file called plugusb.
3. use this command
echo hoston > /sys/devices/f4000000.hisi_usb/plugusb
Replace "f4000000" with the real value.
Now plug in your device and see if it is recognized!
EDIT: You may need to be root to do this!
ADB: "adb root"
TERMINAL APP: "su"
Click to expand...
Click to collapse
The value changed... I forgot my USB adapter in the car... will update the in a few minutes... if it works you resolved a big thing in what..2 days from having the device? great dev... thanks!
EDIT: unfortunately it doesn't work on my device... also after reboot the value changed to OFF again... great find although
Meticulus said:
Hiya Fellas,
I was messing around with my development build last night and I was able to turn on USB host mode and successfully plug in and use a usb flash drive. Now keep in mind that this was on CM 13 but, this might also work on a rooted stock.
Using adb or terminal app.
1. Look for a path in /sys/devices that ends with hisi_usb (e.g /sys/devices/f4000000.hisi_usb)
2. Now inside that folder there should be a file called plugusb.
3. use this command
echo hoston > /sys/devices/f4000000.hisi_usb/plugusb
Replace "f4000000" with the real value.
Now plug in your device and see if it is recognized!
EDIT: You may need to be root to do this!
ADB: "adb root"
TERMINAL APP: "su"
Click to expand...
Click to collapse
WORK !!! THANK YOU !
- install from Playstore Universal Init.d
- Open Universal Init.d and activate support
- Create a generic text file Ex. usbotg in /etc/init.d folder with the following content
#!/system/bin/sh
echo hoston > /sys/devices/f4000000.hisi_usb/plugusb
!!!! Replace "f4000000" with the value found in your smartphone (my: ff100000) !!!!
- give to the file 755 permission
- reboot
I used Root Explorer to do all.
Enjoy !
Meticulus said:
Hiya Fellas,
I was messing around with my development build last night and I was able to turn on USB host mode and successfully plug in and use a usb flash drive. Now keep in mind that this was on CM 13 but, this might also work on a rooted stock.
Using adb or terminal app.
1. Look for a path in /sys/devices that ends with hisi_usb (e.g /sys/devices/f4000000.hisi_usb)
2. Now inside that folder there should be a file called plugusb.
3. use this command
echo hoston > /sys/devices/f4000000.hisi_usb/plugusb
Replace "f4000000" with the real value.
Now plug in your device and see if it is recognized!
EDIT: You may need to be root to do this!
ADB: "adb root"
TERMINAL APP: "su"
Click to expand...
Click to collapse
ThankS!!!! It worked but, there are some troubles:
after using that command doesn't work the usb cable phone - PC (need reboot or to write "hostoff" instead of "hoston");
after rebbot need again to rewrite the command.
With universal Init.d it can be a little easy cause you can make 2 file ( 1 for hoston and 1 for hostoff) and just run them from app, so with 2 touch you can enable and disable otg instead of wirting everytime the command using terminal.
Edit: universal init.d doesn't work properly so I used a script runner and just run from it (with root permissions) 1 of 2 script (enable, disable).
Edit2: Look these images to see what I've done(don't need to reboot phone after):
Image 1: http://prnt.sc/ckk9hs
Image 2: http://prnt.sc/ckka26 (used this app: https://play.google.com/store/apps/details?id=com.snclabs.scriptrunner&hl=it)
Don't know if anyone else has this problem but for some weird reason when I try plug in my 8gb or 128gb it won't work but if plug in the 32gb memory stick bam it works fine any one know the reason y?
Sent from my HUAWEI VNS-L31 using XDA-Developers mobile app
Noel.89 said:
Don't know if anyone else has this problem but for some weird reason when I try plug in my 8gb or 128gb it won't work but if plug in the 32gb memory stick bam it works fine any one know the reason y?
Sent from my HUAWEI VNS-L31 using XDA-Developers mobile app
Click to expand...
Click to collapse
I've tried with my 16gb usb pendrive, 500gb external HD, 2TB external HD and it worked fine with all of them...
SevenSlevin said:
I've tried with my 16gb usb pendrive, 500gb external HD, 2TB external HD and it worked fine with all of them...
Click to expand...
Click to collapse
Really how did you get yours to work maybe I'm doing something wrong putting the file in wrong place
Sent from my HUAWEI VNS-L31 using XDA-Developers mobile app