I do not have root,but I was able to get portable storage. I was just tinkering around and went ahead and clicked format. It then told me that it format to portable storage. It's weird,because I can't use ES File Pro,but I can use stock file manager to move files to my micro SD. I do not have root(Sprint Phone),nor did I use ADB. You can see proof in screenshots below.
So you have a 120gb sdcard formated as portable storage. Whats the point?
Portable is not adoptable.
Darn it ! I got them confused.
OK
I finally got adoptable storage to work. I used the instructions on this page. You do not need root,but you need adb on your PC. I have pictures below.
BR7fan said:
OK
I finally got adoptable storage to work. I used the instructions on this page. You do not need root,but you need adb on your PC. I have pictures below.
Click to expand...
Click to collapse
Im using Modaco method in sandisk 200gb card using "sm partition disk:179,0 mixed 50" but when I try to migrate data to adoptable sd card popup says no enough space and cant move apps to adoptable card.
Anyone with this problem?
BR7fan said:
OK
I finally got adoptable storage to work. I used the instructions on this page. You do not need root,but you need adb on your PC. I have pictures below.
Click to expand...
Click to collapse
When you go to File Manager, does your internal storage show as it was before? Mine shows 14.12 GB available / 22.95 GB, which is weird because it should be out of 32GB...
ishould said:
When you go to File Manager, does your internal storage show as it was before? Mine shows 14.12 GB available / 22.95 GB, which is weird because it should be out of 32GB...
Click to expand...
Click to collapse
That's a known problem with the hack the space available doesn't show correctly. When I use ES File explorer it shows it correctly
BR7fan said:
That's a known problem with the hack the space available doesn't show correctly. When I use ES File explorer it shows it correctly
Click to expand...
Click to collapse
I wonder what it'll say when you go over 22.95GB
Sent from my RS988 using XDA-Developers mobile app
BR7fan said:
OK
I finally got adoptable storage to work. I used the instructions on page. You do not need root,but you need adb on your PC. I have pictures below.
Click to expand...
Click to collapse
can you take pics of the steps caouse the command prompt keeps telling me error:device '<null>' not found
and i have no idea what im doing wrong
There are allready Threads about Adoptable Storage! No need to create a new one...
Just a hint...
BR
evilsanta8585 said:
can you take pics of the steps caouse the command prompt keeps telling me error:device '<null>' not found
and i have no idea what im doing wrong
Click to expand...
Click to collapse
Id love to,but I'm out on the road right now. I wont be home till next week.
BR7fan said:
Id love to,but I'm out on the road right now. I wont be home till next week.
Click to expand...
Click to collapse
Can you please take pics when you get back. And do you know what the problem is if I have that error every time I enter adb shell
evilsanta8585 said:
Can you please take pics when you get back. And do you know what the problem is if I have that error every time I enter adb shell
Click to expand...
Click to collapse
These are the instructions I used CLICK HERE.
Here are instructions an xda member did for the G5 CLICK HERE
Im having a problem i type in adb shell and this is what comes up
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Dawid>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
C:\Users\Dawid>
what do i do
evilsanta8585 said:
Im having a problem i type in adb shell and this is what comes up
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Dawid>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
C:\Users\Dawid>
what do i do
Click to expand...
Click to collapse
Make sure you have enabled "USB Debugging".
Copied from Reddit:
How do I do this?
Step 1: USB Debugging Enabled (go to Settings > About > Software info > Tap Build Number 7 times > Go back to main settings page > Developer Options > USB Debugging )
Step 2: Next you will need to have adb installed on your computer
Step 3: Open a command prompt window and type adb shell (with your phone connected and in Picture Transfer mode) This will start an adb shell
Step 4: After the shell has started type the command "sm list-disks" it will respond with something that looks like this: "disk:179,0" this is your SD card's ID
Step 5: Decide whether you want to dedicate 100% of this SD card as Internal Storage, or still have part of it be Portable Storage.
Step 6: Once you've decided, if you want your entire SD card to be Internal Storage then type "sm partition disk:179,0 private" if you want your SD card to be mixed type: "sm partition disk:179,0 mixed 50" 50 being the percentage of space you want dedicated to Internal Storage
Click to expand...
Click to collapse
ysko said:
Make sure you have enabled "USB Debugging".
Copied from Reddit:
Click to expand...
Click to collapse
Ok what am i missing ive got USB debugging on and keep getting the
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
on my LG G5 unrooted so what do i do to get this to work ?
Related
Update 1: Thank you all the members for making this thread more simpler.
I will do some more edits as instructed by others to make it more understandable.
As we all know it, this guide is no more "easiest".
First of all, thank you to all the members for the Pre-Rooted ROM's, Tutorials, Ideas etc.
I have just made it simpler for the newbies to understand what the devs are doing to get a rooted-Eclair phone.
It has been discussed many times that the current guides are very difficult for newbies to understand.
So I will tell you step-by-step how to do the stuff.
Though it needs many downloads, bit of thinking, but in the end you will be successful!
Make sure to put the phone in USB Debugging Mode everytime.
For that go to -Settings>Applications>Development>USB Debugging(Tick the option)
And maximize the Screen Timeout Limit.
Settings>Sound & Display>Screen Timeout(Set it to 30 minutes).
Update: Many people don't know what "Flashmode" is,
For this you need to unplug the phone from PC, take out phone battery for 5-10 seconds, after that put the battery back, keep holding the Back button and plug the phone back(the notification light will turn Green).
First of all Flash Android 1.6 Link and Root it Link.
Download the files required-
(1) Download the latest Firmware files by propc.
Link 1
Link 2
(2) Download newx8rooted.yaffs.7z Link
(3) Extract newx8rooted.unyaffs.7z to the root of your sdcard(there should be 3 files- (i) newx8rooted.yaffs.img
(ii) busybox
(iii) unyaffs)
(4) Download install.sh.zip(see the attachments)
How to get in the ADB Shell-
(1) First of all we need the ADB files. I have put the files in the folder. See the attachments please.
(2) Extract the files and save them in C: drive.
(3) Now open cmd(Command Prompt).
(4) Type-
cd C:\android
Click to expand...
Click to collapse
Hit Enter.
(5) Now type-
adb shell
Click to expand...
Click to collapse
(6) Remember you must be having Rooted Android 1.6 and 4 files(install.sh, newx8rooted.yaffs.img, busybox, unyaffs) in your SD card at this stage.
After this step the command prompt should be something like this-
C:\android>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$
Click to expand...
Click to collapse
(7) Now type-
su
Click to expand...
Click to collapse
**NOW HAVE A LOOK AT PHONE SCREEN, SUPERUSER MUST BE ASKING FOR PERMISSION, CLICK ON "Allow".(And yes, maximize the Screen timeout time for no spoilling.)**
**NOW THERE SHOULD BE A "#" SIGN IN COMMAND PROMPT.
Sometimes the command takes some time to execute so you need to wait for the "#" prompt before typing next command.**
(8) Now type
cd /sdcard
Click to expand...
Click to collapse
(9) Now type
sh install.sh
Click to expand...
Click to collapse
Update: Many people are facing the problem saying-
# sh install.sh
sh install.sh
sh: Can't open install.sh
#
Click to expand...
Click to collapse
For this, you need to take care of few things.
First of all that you don't miss any commands.
Secondly you must have the drivers installed on your PC. If you don't have please see the attachments, and install it via Device Manager.
Thirdly, make sure that the phone is in USB Debugging Mode.
The phone storage should be turned off.
Sometimes if the error repeats itself, it is always advisable to either Restart both PC and device, or try it on another PC.
There should be a lot of line scrolling, Now sit for sometime and relax!
After all this, it should say-
Reboot phone!
Flash 2.1 now, but remove system.sin
Click to expand...
Click to collapse
Now just Flash Android 2.1 Flasher by Bin4ry works well! and REMEMBER TO REMOVE "system.sin" from the folder of the firmware!!!
Sit back and relax!!
Now just reboot the phone(1st Reboot will take 5-10 mins.).
And you are done!
Hope that I am helpful!
Edit:Many people don't know what "Root of SD Card is"
This means that the files should be on your SD Card directly, do not put these files in any Folder, simply paste them in you SD Card.
Any suggestions and queries are welcomed.
Update 2:
Guys it is really very difficult to know exactly what the problem is. Because it is working for many and not for few, it is hard to know the
exact mistake.
So I advice you people to please repeat the process again, or try it on another PC, if you dont mind that, I am not a pro, I am here just to sort out few problems.
I am sorry but i really ain't able to get solution for random problems.
Can any other "Senior" help this out?
Special Thanks to-
propc
Bin4ry
a-k-t-w
pullpoff2
You can always appreciate my work by just clicking "Thanks"!
Cheers!
you don't need the Android SDK. ADB shell is already in superoneclick.
thanks for instruction
Botoxopfer said:
you don't need the Android SDK. ADB shell is already in superoneclick.
Click to expand...
Click to collapse
I didn't noticed that!!
God! I need to edit it!!
mohakrastogi said:
I didn't noticed that!!
God! I need to edit it!!
Click to expand...
Click to collapse
Also change it to , Copy and paste the three adb files into the /system32 folder, that way adb shell can be accessed without cding, (makes it even simpler )
timk1764 said:
Also change it to , Copy and paste the three adb files into the /system32 folder, that way adb shell can be accessed without cding, (makes it even simpler )
Click to expand...
Click to collapse
Thank you for the suggestion!
Now that you've put the "$" sign after adb shell, you can also put the "#" sign after su, so they will know when to type again. Sometimes the command takes some time to execute so tell them you need to wait for the "#" prompt before typing next command.
Special thanks for this, it's done.
Now i have rooted 2.1 and Gingerbread Theme.
What I'm doing wrong ?
# sh install.sh
sh install.sh
sh: Can't open install.sh
#
Arkaeris said:
What I'm doing wrong ?
# sh install.sh
sh install.sh
sh: Can't open install.sh
#
Click to expand...
Click to collapse
Code:
cd /sdcard
sh install.sh
and make sure your sdcard is not mounted. turn off usb storage on your PC
This guide is great...
But after the last step, flashing 2.1 without system.sin.. My X8 is stuck on "Sony Ericsson" without the logo...
"turn off usb storage on your PC"
sorry, but how to do that ?
Arkaeris said:
"turn off usb storage on your PC"
sorry, but how to do that ?
Click to expand...
Click to collapse
ops, turn off USB storage on your phone. drag down the status bar, press Turn off USB storage. press turn off
I have unmount sd card, I have turn off usb storage but..
C:\android>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\android>
Arkaeris said:
I have unmount sd card, I have turn off usb storage but..
C:\android>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\android>
Click to expand...
Click to collapse
Install Update Service and PC companion. or download X8 driver at http://developer.sonyericsson.com/
propc said:
Install Update Service and PC companion. or download X8 driver at http://developer.sonyericsson.com/
Click to expand...
Click to collapse
okey I have install update service and reinstall pc companion and download x8 drivers.
C:\android>adb shell
$ su
su
# cd /sdcard
cd /sdcard
# sh install.sh
sh install.sh
sh: Can't open install.sh
#
I don't understand where I go wrong.....
Arkaeris said:
okey I have install update service and reinstall pc companion and download x8 drivers.
C:\android>adb shell
$ su
su
# cd /sdcard
cd /sdcard
# sh install.sh
sh install.sh
sh: Can't open install.sh
#
I don't understand where I go wrong.....
Click to expand...
Click to collapse
check that you had turn off USB storage, check that you copied the files to the root of your sdcard
propc said:
check that you had turn off USB storage, check that you copied the files to the root of your sdcard
Click to expand...
Click to collapse
what does it mean "to the root of your sdcard" ?
is folder name or something like that ?
Maybe my computer has some windows problems ?
Root of SD-Card means that u only put it into the sdcard into no folder. Just click on the sdcard and copy the file in it.
[email protected] said:
Root of SD-Card means that u only put it into the sdcard into no folder. Just click on the sdcard and copy the file in it.
Click to expand...
Click to collapse
I'm doing just you said but.. It still Can't open install.sh
Before yesterday when powering up my nook tablet I would get the "Installing factory Software...Do not Turn off your device" but immediately after I would get the error message "Please contact nook support." Now my nt just turns off after powering on and displaying the n screen. I have absolutely no clue what is wrong with my tablet or what steps to follow in order to fix it. I would greatly appreciate any input from the knowledgeable members here to point me in the right direction in terms of what procedures need to be followed. Thanks
Heathie89 said:
Before yesterday when powering up my nook tablet I would get the "Installing factory Software...Do not Turn off your device" but immediately after I would get the error message "Please contact nook support." Now my nt just turns off after powering on and displaying the n screen. I have absolutely no clue what is wrong with my tablet or what steps to follow in order to fix it. I would greatly appreciate any input from the knowledgeable members here to point me in the right direction in terms of what procedures need to be followed. Thanks
Click to expand...
Click to collapse
Okay! Step one, you need to make a bootable CWM card.
Get yourself a microSD card, format it, and copy the files from HERE (download, unzip to your SD card).
Power your NT completely down, plug in the card, and then plug in the USB cable.
You should boot to a "cardboard" box screen.
After that, its going to boot into CWM recovery. Now you're not going to have alot of tools on the card at this point, but you may see some errors about stuff not being able to be mounted, etc.
Once you've got that done, post back here, and also include any errors you see!
From there, we can try to figure out exactly what's gone wrong, and the best approach to fix it.
--Also! Include the information about your NT, Is it rooted? What firmware or Rom? Other than powering up, what had you done (If anything) previously before the error!
^ Thanks for your quick reply!
As I wrote in my first post I'm a complete noob when it comes to rooting or hacking any devices. I have not once tried rooting my NT. What I did do though in order to have android as an option on my tablet is buy one of those Nook2Android cards. Now I think I may have accidentally pressed Format SD card or something like that when trying to do something else. That's all that I can think of that I may have done to cause the error.
I'm going to try and make the bootable CWM card right now. I'll make sure to report back!
lag0matic,
I now have a bootable CWM card.
So when I boot into CWM I get this error:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
What needs to be done now? Thanks
Heathie89 said:
lag0matic,
I now have a bootable CWM card.
So when I boot into CWM I get this error:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
What needs to be done now? Thanks
Click to expand...
Click to collapse
Erf. Okay, you've managed to bork your partitions.
Lets hope this goes easily!
First, lets get Parted (and some other tools) on your CWM recovery card.
Download this file here then unzip them to the root of your CWM Sd card.
Then you need to get ADB up and installed.
I used This forum to get the drivers, however, I couldnt get ADB to work right off the bat.
I'll copy/paste the steps I used and helped others get ADB runnng.
First, google this application: Usbdeview
Download the appropriate one for your system.
Unplug all USB mass storage devices (USB HDD's, Card readers, Memory sticks, etc)
Run USBDeview, delete anything Google, Android, Nook, Barnes and Noble, and Mass storage.
Reboot.
Open device manager
Run the "Runmefirst" or whatever its called from the ADB directory
Plug in your NT.
Go to device manager - look for a broken driver on the tablet, and tell it to install the drivers (you may have to use "have disk" and point to the usb driver directory)
This should install the driver for your NT.
You may also need to edit a file in the .android directory, at the root of your windows username folder.
in which case, drop to a command prompt and type
echo 0x2080 > %username%\.android\adb_usb.ini
after that, switch to the directory you unziped the ADB files to (I used C:\ntroot) and try to connect to your NT by typing "adb devices"
you _should_ see something like
1234567890 Recovery
Or
000000000 Recovery
Now, once you see one of the above messages
in the same command promt window enter the follwing commands
adb shell
mount /sdcard/
cd /sdcard/
parted /dev/block/mmcblk0
you'll then get a prompt that looks like
(parted)
type "print"
and hopefully you'll see a few errors, and it will ask you to fix them, choose fix for both.
Once you get this far (Or, if you run into troubles) post again and i'll see what I can do for you!
(I have successfully un-bricked my NT, but I did it in a way I want to avoid fo you, as we want yours to run stock roms)
lag0matic said:
Erf. Okay, you've managed to bork your partitions.
Lets hope this goes easily!
First, lets get Parted (and some other tools) on your CWM recovery card.
Download this file here then unzip them to the root of your CWM Sd card.
Then you need to get ADB up and installed.
I used This forum to get the drivers, however, I couldnt get ADB to work right off the bat.
I'll copy/paste the steps I used and helped others get ADB runnng.
First, google this application: Usbdeview
Download the appropriate one for your system.
Unplug all USB mass storage devices (USB HDD's, Card readers, Memory sticks, etc)
Run USBDeview, delete anything Google, Android, Nook, Barnes and Noble, and Mass storage.
Reboot.
Open device manager
Run the "Runmefirst" or whatever its called from the ADB directory
Plug in your NT.
Go to device manager - look for a broken driver on the tablet, and tell it to install the drivers (you may have to use "have disk" and point to the usb driver directory)
This should install the driver for your NT.
You may also need to edit a file in the .android directory, at the root of your windows username folder.
in which case, drop to a command prompt and type
echo 0x2080 > %username%\.android\adb_usb.ini
after that, switch to the directory you unziped the ADB files to (I used C:\ntroot) and try to connect to your NT by typing "adb devices"
you _should_ see something like
1234567890 Recovery
Or
000000000 Recovery
Now, once you see one of the above messages
in the same command promt window enter the follwing commands
adb shell
mount /sdcard/
cd /sdcard/
parted /dev/block/mmcblk0
you'll then get a prompt that looks like
(parted)
type "print"
and hopefully you'll see a few errors, and it will ask you to fix them, choose fix for both.
Once you get this far (Or, if you run into troubles) post again and i'll see what I can do for you!
(I have successfully un-bricked my NT, but I did it in a way I want to avoid fo you, as we want yours to run stock roms)
Click to expand...
Click to collapse
So I'm currently going through the process of installing the drivers but I keep getting OMAP4430 under Other devices while Device Manager keeps refreshing.
Heathie89 said:
So I'm currently going through the process of installing the drivers but I keep getting OMAP4430 under Other devices while Device Manager keeps refreshing.
Click to expand...
Click to collapse
^ wow.... that is exactly what i got after the second time my unit barfed.
can you right click on the "omap4430" entry in the device manager and update the drivers by pointing to the folder that has the "nook drivers" folder in the adb + driver + fast zip file?
I imagine you will get a error telling you the drivers are not for this device.
Question to you, did you happen to try formatting the "internal sdcard" ?
@ Lag0matic. this is what killed my unit *dead* today. but it only occured *after* using the 2.3.7 memory managers (not rom-manager) to format the SDcard and the internal SDcard...
maxxcool7421 said:
^ wow.... that is exactly what i got after the second time my unit barfed.
can you right click on the "omap4430" entry in the device manager and update the drivers by pointing to the folder that has the "nook drivers" folder in the adb + driver + fast zip file?
I imagine you will get a error telling you the drivers are not for this device.
Question to you, did you happen to try formatting the "internal sdcard" ?
@ Lag0matic. this is what killed my unit *dead* today. but it only occured *after* using the 2.3.7 memory managers (not rom-manager) to format the SDcard and the internal SDcard...
Click to expand...
Click to collapse
The good news is I have now installed the drivers! My NT under Android Phone appears as Android Composite ADB Interface in Device Manager.
Sadly,though, after getting this far it seems adb still does not recognize my device?
After imputing "adb devices" in cmd in the directory containing the adb files what I get is:
List of devices attached
I don't know if I have missed a step or did one incorrectly.
Heathie89 said:
The good news is I have now installed the drivers! My NT under Android Phone appears as Android Composite ADB Interface in Device Manager.
Sadly,though, after getting this far it seems adb still does not recognize my device?
After imputing "adb devices" in cmd in the directory containing the adb files what I get is:
List of devices attached
I don't know if I have missed a step or did one incorrectly.
Click to expand...
Click to collapse
couple different things to try
#1
adb kill-server
adb start-server
adb devices
try this a couple times. my nook did not get hooked until i did this 2,3 times
#2 with the unit booted from cwm recovery *on the sd card*, reboot windows while leaving the device plugged in.
once back in windows try the adb devices command again.
failing that you are where i was. but at least you can get into cwm, mine ceased booting from sd entirely. heres a thought and a test. can you make the bootable-apla SD card and still use the nook via sd card only? or does it freeze up... ?
Heathie89 said:
The good news is I have now installed the drivers! My NT under Android Phone appears as Android Composite ADB Interface in Device Manager.
Sadly,though, after getting this far it seems adb still does not recognize my device?
After imputing "adb devices" in cmd in the directory containing the adb files what I get is:
List of devices attached
I don't know if I have missed a step or did one incorrectly.
Click to expand...
Click to collapse
i have had that happen a few times and the problem was that my drivers were not installing correctly. sure it appeared as android adb composite device, but it most likely installed the wrong driver for the wrong device.
this is where things get a bit complicated because you need to look for the product and vendor id's for the nook tablet and modify them correspondingly in the android_winusb.inf.
also make sure you execute the runmefirst.bat
that creates a .android folder in your user folder. that was the step i kept missing when i had your problem with the drivers... ironic right? "runmefirst" and i run it last haha...
Today my Tablet (Hyundai A7HD) with CM9 started behaving very strange.
It doesnt recognize my sd card, nor its own internal nand storage anymore.
I dont know what to do, since i cant even flash an update through CWM anymore without a functioning storage medium.
the sd card works fine on my pc and i cant format the internal storage through my tablet.
what else can i do to fix this?
I could really use some help, if someone knows a way to do it.
IndigoHD said:
I could really use some help, if someone knows a way to do it.
Click to expand...
Click to collapse
Supply more information. How do you know it's not detecting the internal storage? What are the symptoms? In my point of view, the device would be bricked in this case. Can it boot at all? Or is it fastboot complaining , trying to flash it? The internal memory, is it a MTD for /system plus an MMC for /data, or only an MTD? Only one MMC? Does the devices still exists or not? The partitions..?
Give us some more information, and we'll see if someone here can come with an intelligent suggestion.
Thank you for your reply!
The Device is an Hyundai A7HD and it says that what it calls "sdcard" but actually is its internal storage is damaged. Formatting doesnt work.
It still boots fine but cant access the internal storage, so nothing can be downloaded onto the device and such.
It has a special partition where applications are installed, but nothing can be saved there.
im guessing that something is wrong with the OS, and maybe i could fix it using ADB (if someone could explain to me how)?
Ok, so no /sdcard and /sdcard is supposed to be the phones internal memory, no /data partition, hence not able to download new apps, but the phone boots and so, i.e. system partitions works fine.
This sounds quite like this (confusing) thread to me. In summary, we are talking about three devices, the internal MTD device with /system, boot image, cache etc, the internal MMC device with /sdcard and /data plus an external sdcard named something like /sdcard/external_sd. The internal MMC broken beyond repair (hardware failure).
Still it may be something else only reassembling this.
If you believe your problem is due to some problem with your ROM I suggest you try to reinstall stock ROM using the vendors standard flash tools.
If this doesn't work, we can see if a solution similar to the one in the thread above may be applicable to you.
When i use Astro file manager to look at my phones storage the internal memory calls itself "sdcard" and my ACTUAL micro-sdhc calls itself "extsd" in a folder called "mnt".
the original flash tool doesnt seem to function anymore since i would normally hold down the "menu"-button, then plug the cable into my pc and while STILL holding menu id press power 7 to 10 times and then flashing would start automatically. but ever since installing cwm and a cm9 custom-rom, this doesnt seem to function anymore.
EDIT: in Clockwordmod recovery its called "emmc" for internal memory and "sdcard" for my actual sdcard.
Ok, this is consistent. Can you do a couple of shell commands?
# mount
and
# ls -l /dev/block
... and paste in the result here. As root or as shell user (or any other user) doesn't really matter.
when i plug the device into usb it says debugging enabled. so i open adb and type in "adb devices" and it starts listing devices. But no device is recognized.
EDIT: it recognizes my phone tho.
IndigoHD said:
when i plug the device into usb it says debugging enabled. so i open adb and type in "adb devices" and it starts listing devices. But no device is recognized.
Click to expand...
Click to collapse
Tricky. And not possible to install apps, so no ConnectBot or similar ...
Do you have a link to the CM9 you are using?
kuisma said:
Tricky. And not possible to install apps, so no ConnectBot or similar ...
Do you have a link to the CM9 you are using?
Click to expand...
Click to collapse
wait! i CAN install apps from the market!
and yes, one second.
http://www.slatedroid.com/topic/33373-rom-cm9-nightlies/
im using version 20120711
EDIT: Its an Allwinner A10 Device.
IndigoHD said:
wait! i CAN install apps from the market!
Click to expand...
Click to collapse
That makes all the difference!
So, what does "mount" say?
when i type "adb mount" it just gives me a long list of commands and explanations.
EDIT: there are many versions of connectbot. which one do we need?
IndigoHD said:
when i type "adb mount" it just gives me a long list of commands and explanations.
Click to expand...
Click to collapse
No, run mount from the command line using ConnectBot. ADB didn't work, you told me before.
$ mount
Click to expand...
Click to collapse
but which connectbot on the market is the right one? There are so many.
IndigoHD said:
but which connectbot on the market is the right one? There are so many.
Click to expand...
Click to collapse
Please. Show a little more effort.
https://play.google.com/store/apps/details?id=org.connectbot
i installed it and started it.
now it asks me to connect to a host.
i honestly dont know what im doing here.
IndigoHD said:
i installed it and started it.
now it asks me to connect to a host.
i honestly dont know what im doing here.
Click to expand...
Click to collapse
Select "local", give the session some name of you choice and connect. Now you are running a local shell in the same way as using "adb shell". You are familiar with "adb shell"..?
kuisma said:
Select "local", give the session some name of you choice and connect. Now you are running a local shell in the same way as using "adb shell". You are familiar with "adb shell"..?
Click to expand...
Click to collapse
isnt adb shell a terminal that accepts commands either locally or by usb connection?
EDIT: What should i do now on connectbot?
Can anyone help me, perhaps?
Has anyone had a successful root on a plt7602g. I have tried a couple different methods.
Rooting the PLT7602G
sallanm said:
Has anyone had a successful root on a plt7602g. I have tried a couple different methods.
Click to expand...
Click to collapse
Here is a procedure to root the Curtis Proscan PLT7602G tablet (Build number PLT7602G-ANDROID4.2.2-v1.0.0).
1. Install adb on your computer and enable adb on the tablet. http://developer.android.com/tools/help/adb.html
2. Enable ADB on the tablet:
Settings > About Tablet > tap build number 7 times until it says "You are now a developer!"
Developer options > switch On > OK
Check "USB Debugging" > OK
3. Connect USB and wait for ADB drivers to load on the PC. Using the Google drivers installed with ADB, your system may need manual help to find the right drivers: Go into Windows device manager > Update Driver Software > browse My Computer for driver software > 'Let me pick from a list of devices drivers...' > Pick Android ADB Interface from the model list.
4. You will see a notification "USB Debugging Connected" on the tablet.
5. If this is the first time, you will next see a dialog on the tablet asking "Allow USB debugging?" Check "Always allow from this computer" and click OK.
6. At the command prompt on the computer enter "adb devices". You should see the device listed. If not, reboot the PC and repeat steps 1 through 5 as necessary to get everything working together.
C:\Users\entropy>adb devices
List of devices attached
CD1LBROR50 device
C:\Users\entropy>7. Download pwn.zip here: http://forum.xda-developers.com/showpost.php?p=53407127
8. Unzip "pwn" from the zip file to your windows current directory
9. At the command prompt on the computer enter the following sequence of commands:
C:\Users\entropy> adb push pwn /data/local/tmp/pwn
C:\Users\entropy> adb shell chmod 755 /data/local/tmp/pwn
C:\Users\entropy> adb shell /data/local/tmp/pwn
Beaups and jcase were here
donations may go here, pleaes say what it was for -> [email protected]
10. After a few seconds, you should hear the USB disconnect sound, followed by the USB connection sound again.
11. At the command prompt, enter “adb devices” and ensure the device is listed as before. If not, wait a few seconds and then repeat this step.
C:\Users\entropy> adb devices
12. At the command prompt, enter:
C:\Users\entropy> adb shell
7. At the shell prompt, enter "su". You should now have a root prompt.
[email protected]:/ $ su
[email protected]:/ #
8. Exit back out to the command prompt:
[email protected]:/ # exit
[email protected]:/ $ exit
C:\Users\entropy>
9. On the tablet, go to the play store, download and install the latest SuperSU, or use the Google Play link in this thread: http://forum.xda-developers.com/show....php?t=1538053
10. Open the SuperSU that you just installed. SuperSU will prompt you to install a newer su binary when you run it, so click “Continue” do that, then “Normal”, then “OK”.
11. Reboot the tablet.
The tablet should now be fully rooted. Please let me know if you find any errors or if anything is unclear. I hope you find this useful!
I've downloaded the "Unrevoked" USB driver but the device is not being installed...
Marco Dufal said:
I've downloaded the "Unrevoked" USB driver but the device is not being installed...
Click to expand...
Click to collapse
It has been a while since I got this working and I honestly don't remember exactly what I did to make it work.
Try this... install the official Google driver and reboot:
http://developer.android.com/sdk/win-usb.html
If i still doesn't work, download the adb_usb.ini from here and replace the adb_usb.ini in c:\users\<yourusername>\.android\adb_usb.ini with this one, then reboot and try again. I verified that this adb_usb.ini contains the necessary device ID, so that should definitely do the trick.
https://github.com/apkudo/adbusbini
If you get it working, please post here so others can benefit.
Sice I had already installed the official Google drivers I proceeded with the adb_usb.ini method, but even after rebooting my pc it didn't work... What worked for me was:
Going into window device manager -> Update Driver Software -> browse my computer for driver software -> 'let me pick from a list of devices drivers...' -> Picked Android ADB Interface (from the model list).
I don't get why it did't install it automatically since the driver is actually compatible; did the same thing with another device (Sony experia E1). I got two of them, the first one got recognized while I had to do this process for the second one... Maybe it's my pc fault..
Anyway thank you very much for your replies and the guide. Am I risking to brick the device by following it ?
P.S.
For those who have android studio installed, to run the guide prompt commands you can set an environment variable called 'adb' with this value 'C:\Users\{USERNAME}\AppData\Local\Android\sdk\platform-tools\adb.exe' and easily replacing 'adb' with '%adb%' .
For example : 'C:\Users\{any directory}>%adb% devices'
Marco Dufal said:
Sice I had already installed the official Google drivers I proceeded with the adb_usb.ini method, but even after rebooting my pc it didn't work... What worked for me was:
Going into window device manager -> Update Driver Software -> browse my computer for driver software -> 'let me pick from a list of devices drivers...' -> Picked Android ADB Interface (from the model list).
I don't get why it did't install it automatically since the driver is actually compatible; did the same thing with another device (Sony experia E1). I got two of them, the first one got recognized while I had to do this process for the second one... Maybe it's my pc fault..
Anyway thank you very much for your replies and the guide. Am I risking to brick the device by following it ?
P.S.
For those who have android studio installed, to run the guide prompt commands you can set an environment variable called 'adb' with this value 'C:\Users\{USERNAME}\AppData\Local\Android\sdk\platform-tools\adb.exe' and easily replacing 'adb' with '%adb%' .
For example : 'C:\Users\{any directory}>%adb% devices'
Click to expand...
Click to collapse
I'm glad you got ADB working. Thanks for the additional tips, I'm sure they will be useful to others.
I don't think there is any significant risk of bricking unless you make a horrible mistake, like deleting everything in /system instead of shifting the new file into place. Anything else, like accidentally picking the wrong su binary to install, should be easily recoverable by just rebooting if necessary and then trying again.
maximumentropy said:
I'm glad you got ADB working. Thanks for the additional tips, I'm sure they will be useful to others.
I don't think there is any significant risk of bricking unless you make a horrible mistake, like deleting everything in /system instead of shifting the new file into place. Anything else, like accidentally picking the wrong su binary to install, should be easily recoverable by just rebooting if necessary and then trying again.
Click to expand...
Click to collapse
Quick info. I am rooting because of the low storage. Currently this is my storage situation :
total 4GB
Firmware 2.04GB
---------------------
Total space 1.96GB
197MB Available
232MB Apps
few KB Cached data & Misc.
There must be something wrong... Anyway my question is. Should I flash a custom rom to free some of the firmware allocated memory ? How is the external card going to be used (can I install app on it) ?
EDIT
I get
`su: not found`
Marco Dufal said:
Quick info. I am rooting because of the low storage. Currently this is my storage situation :
total 4GB
Firmware 2.04GB
---------------------
Total space 1.96GB
197MB Available
232MB Apps
few KB Cached data & Misc.
There must be something wrong... Anyway my question is. Should I flash a custom rom to free some of the firmware allocated memory ? How is the external card going to be used (can I install app on it) ?
Click to expand...
Click to collapse
I haven't found any custom ROMs for this tablet. If you know of some, please speak up. You could try reflashing the original ROM but that might be overkill. You can use an app like DiskUsage to help you identify what's eating the most space.
Marco Dufal said:
EDIT
I get
`su: not found`
Click to expand...
Click to collapse
I can't help you if you give me an error message but no hint of what you entered that caused the message.
maximumentropy said:
I haven't found any custom ROMs for this tablet. If you know of some, please speak up. You could try reflashing the original ROM but that might be overkill. You can use an app like DiskUsage to help you identify what's eating the most space.
Click to expand...
Click to collapse
Thanks I will check it up.
maximumentropy said:
I can't help you if you give me an error message but no hint of what you entered that caused the message.
Click to expand...
Click to collapse
C:\Users\Marco\AppData\Local\Android\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
Marco Dufal said:
Thanks I will check it up.
C:\Users\Marco\AppData\Local\Android\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
Click to expand...
Click to collapse
Please try entering it with full path:
[email protected]:/ $ /system/xbin/su
maximumentropy said:
Please try entering it with full path:
[email protected]:/ $ /system/xbin/su
Click to expand...
Click to collapse
Still negative result :
[email protected]:/ $ /system/xbin/su
/system/xbin/su
/system/bin/sh: /system/xbin/su: not found
127|[email protected]:/ $ ls /system/xbin/
ls /system/xbin/
dexdump
io
[email protected]:/ $
Marco Dufal said:
Still negative result :
Click to expand...
Click to collapse
What is your build number in Settings > About Tablet?
maximumentropy said:
What is your build number in Settings > About Tablet?
Click to expand...
Click to collapse
PLT7602G-ANDROID4.2.2-v1.0.0
Marco Dufal said:
PLT7602G-ANDROID4.2.2-v1.0.0
Click to expand...
Click to collapse
Well, I apologize for being an idiot. That's what I get for trying to document a root procedure I did last year, from memory. I have several similar cheap tablets and I misremembered this one as being pre-rooted as I described.
I just re-flashed from stock and re-rooted it. Fortunately, I had left enough breadcrumbs on my computer that I was able to reconstruct the right procedure.
I will do another full run-through within the next few days as soon as I have some time, to make sure I have everything 100% straight, and will clean this up to update the OP. Meanwhile, if you're feeling brave, here's the notes I took as I did it:
Settings > About Tablet > tap build number until it says you are a developer
Developer options > switch On > OK
USB Debugging > OK
Connect USB
see "USB Debugging Connected" notification
Wait for "Allow USB debugging?" dialog, check "Always allow from this computer" and click OK
adb devices
Download pwn.zip here: http://forum.xda-developers.com/showpost.php?p=53407127
Unzip "pwn" from the zip file to your windows current directory
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
Hear USB disconnect sound
Wait about 1 minute (may or may not need to disconnect and reconnect USB cable)
adb wait-for-device
adb shell
su (should give a root shell)
exit
Install SuperSU from Play Store
Run it
The SU binary needs to be updated. Continue?
Continue > Normal > OK
Reboot
Don't worry it's ok.. Anyway I am not felling brave at all so I think that I will wait for now...
Marco Dufal said:
Don't worry it's ok.. Anyway I am not felling brave at all so I think that I will wait for now...
Click to expand...
Click to collapse
No guts, no glory!
I updated the instructions in post #2 and did another trial run through. Give it a shot at let me know if you run into any trouble. You already have ADB functioning, so you can just skip to step 6 and go from there.
http://forum.xda-developers.com/showpost.php?p=59530490&postcount=2
maximumentropy said:
No guts, no glory!
Click to expand...
Click to collapse
Just did it and every thing worked ! It was fast and clear... Now I wonder, how many devices can I root with the same procedure ?
Marco Dufal said:
Just did it and every thing worked ! It was fast and clear... Now I wonder, how many devices can I root with the same procedure ?
Click to expand...
Click to collapse
Great, I'm glad it worked for you!
The pwn exploit will work with many JellyBean devices. Many of the cheap Chinese tablets don't even need it though, as they will either give you a root prompt immediately when you connect using ADB, or after entering "su" to ADB. The trick then is just to use that access to install an "su" from SuperSU or another full SU package, so that you get full root from the user interface as well as from ADB. You could still use the pwn method on such a device, but I personally prefer to use the least invasive method to get the required access.
maximumentropy said:
Great, I'm glad it worked for you!
The pwn exploit will work with many JellyBean devices. Many of the cheap Chinese tablets don't even need it though, as they will either give you a root prompt immediately when you connect using ADB, or after entering "su" to ADB. The trick then is just to use that access to install an "su" from SuperSU or another full SU package, so that you get full root from the user interface as well as from ADB. You could still use the pwn method on such a device, but I personally prefer to use the least invasive method to get the required access.
Click to expand...
Click to collapse
Sorry if this is a newb question but can this be done if your microusb port is broken? I can get the file on the tablet via sd card but I can't seem to perform the steps with Terminal Emulator like I had hoped. This is using the same ProScan PLT7602G as in the OP.
Thanks
Ian1331 said:
Sorry if this is a newb question but can this be done if your microusb port is broken? I can get the file on the tablet via sd card but I can't seem to perform the steps with Terminal Emulator like I had hoped. This is using the same ProScan PLT7602G as in the OP.
Thanks
Click to expand...
Click to collapse
I don't think it will work in a terminal emulator because you need to run with uid 2000 (shell) for permission on the /data/local/tmp directory.
Hey Guys,
Been lurking for a while. I want to get into some Android development. I bought a cheap Galaxy Tab s SM-T800 from ebay. It was a retail unit, so came with the usual retail protection, but that was no issue, I've reflashed it and rooted it, it is now running 6.0.1 with build number MMb29K.T800XXU1CRJ1.
The issue is, there are a bunch of apps and files that appear to be left over from the retail demo mode, and I can't remove them. The apps won't uninstall, it just says "uninstall unsuccessful", and the files, when I try to delete them, it just says "failed to delete".
Even after freshly restoring the new firmware, the storage on this device is pretty much zero, a lot of the space being taken up with the files and apps that I can't remove.
There was just about enough space remaining to install System App Remover, but that couldn't delete the files and apps either.
How are these files being write protected? How do I go about removing the write protection? I'm wondering if this device, because it was a retail demo unit, was configured with some kind of write protected partition, which is why the storage is so low, and why I can't delete the apps?
Any thoughts, this is driving me nuts.
Thanks
Install a file manager that allows to mount the partitions in question as READ-WRITE, thus folders/files can get deleted
jwoegerbauer said:
Install a file manager that allows to mount the partitions in question as READ-WRITE, thus folders/files can get deleted
Click to expand...
Click to collapse
Thanks, but I can't install any of the file manager apps, as there is not enough free space. I'll need to do it by connecting from Windows. What android partition/file manager would be a good one to use from Windows?
DotNetDude said:
Thanks, but I can't install any of the file manager apps, as there is not enough free space. I'll need to do it by connecting from Windows. What android partition/file manager would be a good one to use from Windows?
Click to expand...
Click to collapse
Because your device is rooted, you use ADB ( read: Android Debug Bridge ) - what you've to install on your Windows computer - to manage this device - you must have turned on Developer options -> USB Debugging on it, of course: IMHO the only the chance you have.
Once done so, you connect your device via USB cable with Windows computer, then in Windows command prompt run the commands as follows - one after one:
Code:
adb devices
adb root
adb shell mount -o rw,remount / -t auto
If success then your Android device completly is switched to READ-WRITE mode, you then via further relevant ADB commands can remove folders/files which you consider dispensable, even apps if you know their package name, and so on ...
jwoegerbauer said:
Because your device is rooted, you use ADB ( read: Android Debug Bridge ) - what you've to install on your Windows computer - to manage this device - you must have turned on Developer options -> USB Debugging on it, of course: IMHO the only the chance you have.
Once done so, you connect your device via USB cable with Windows computer, then in Windows command prompt run the commands as follows - one after one:
Code:
adb devices
adb root
adb shell mount -o rw,remount / -t auto
If success then your Android device completly is switched to READ-WRITE mode, you then via further relevant ADB commands can remove folders/files which you consider dispensable, even apps if you know their package name, and so on ...
Click to expand...
Click to collapse
Thanks for your details.
So I tired this but the adb root command wasn't working. It was coming up with the message:
adbd cannot run as root in production builds
So after a bit of research, I found the adp insecure app from Chainfire, that apparently resolves this exact problem. So I've deployed that to the tab and run it, but now when I connect the tablet to my PC, the PC doesn't connect. I get the charging symbol on the tab, so the connection is in place, but it is not detected by the pc, so I can't connect using adb.
Any suggestions would be much appreciated?
Thanks
DotNetDude said:
Thanks for your details.
So I tired this but the adb root command wasn't working. It was coming up with the message:
adbd cannot run as root in production builds
So after a bit of research, I found the adp insecure app from Chainfire, that apparently resolves this exact problem. So I've deployed that to the tab and run it, but now when I connect the tablet to my PC, the PC doesn't connect. I get the charging symbol on the tab, so the connection is in place, but it is not detected by the pc, so I can't connect using adb.
Any suggestions would be much appreciated?
Thanks
Click to expand...
Click to collapse
I realise I am responding to my own message!
Now that I am running with adb insecure, I have realisd that the USB debugging mode from developer settings is working in reverse. That is, if I enable it, the tab detaches form the PC. If I disable it, the tab reconnects to the pc. However with that setting disabled, and the pc connected, when I then run the command adb devices, it says there are no devices connected (even though I can browse to the tablet through windows explorer)
From within the adb insecure app on the tablet, when I enable the app, I can see it displays a message that says USB debugging is disabled.
I have no idea what is going on here...
Any help much appreciated?
Thanks
@DotNetDude
May be reading this helps.
jwoegerbauer said:
@DotNetDude
May be reading this helps.
Click to expand...
Click to collapse
Thanks for this. Actually, adbd insecure was just causing more problems. In the end I have resolved this by extracting the PIT file and re-partitioning. Firmware then restored correctly and all the problems are now gone, and there is plenty of free space remaining.