Related
I wiped my system because there was something wrong with the hero theme i was running. i booted back up and after i booted into the phone, i cant boot into the home screen, it boots for some reason into lock 2.0 and i didnt choose that as a default, why is it doing this? im running the dude's cupcake beta 12 and app2sd
Don't know...Never heard that occur before. I suggest a reflash of the ROM or even a e2fsck of the filesystems.
i hate when this stuff happens at work where my computer blocks me from plugging in something to the usb port so i have to wait until i leave
alritewhadeva said:
Don't know...Never heard that occur before. I suggest a reflash of the ROM or even a e2fsck of the filesystems.
Click to expand...
Click to collapse
e2sfck? whats that?
Checking of EXT filesystems...Do you have cyanogen's latest recovery? 1.3.1?
no, i couldnt figure out how to install it, but i believe i put it in the appropriate place on the sd card to install it, can i put it up through the recovery console?
Depends, did you download the .zip version, or the .img version? If you have the .zip .. Go to recovery console and:
Code:
mount /sdcard
cd /sdcard
mv cm-recovery-1.3.1-signed.zip update.zip
recovery
Then you can try flashing it. CM Recovery also lets you mount your phone via USB, so if you need to reflash and don't have an image on your phone, drop to the recovery and run
Code:
ums_enable
Copy file to your card, eject on the PC
ums_disable
recovery
If you downloaded the .img version of the recovery, I'm not sure that it can be flashed without getting into the main OS. What happens when you try to unlock Lock 2.0? You didn't really say..
Hey guys first off I'd like to apologize if this thread is already up somewhere but I couldn't find anything in the search
I'm selling my secondary G1 to a non tech savvy user but I'm leaving CM on there, I have an ext partition on the SD card and I was wondering if there was a way I could get rid of the Apps2SD so there wouldn't be a risk of them messing up the phone by switching the card
Thanks
You cann just reformat the whole card to FAT32
or you can delete the ext partition through parted and increase the size of the FAT32 to fill the unused space
How would I reformat the card from adb or recovery console?
AimanF said:
How would I reformat the card from adb or recovery console?
Click to expand...
Click to collapse
you can format with your pc or to format in phone settings either should work for you.
The format option in the phone settings is grayed out, and my sd card reader doesn't seem to be working, is there another way to do it through the phone?
AimanF said:
The format option in the phone settings is grayed out, and my sd card reader doesn't seem to be working, is there another way to do it through the phone?
Click to expand...
Click to collapse
recovery mode
parted dev/block/mmcblk0
print
rm 2
You can use AmonRA's recovery image and format the sdcard with that. You can install it from the terminal in the phone.
su
flash_image recovery/sdcard/recovery-dream-RA-v1.3.2G.img
Yes h/o
adb shell
parted /dev/block/mmcblk0
print
rm 1
rm 2
rm 3
Click to expand...
Click to collapse
This will remove all the data on the SDcard
Go to where it says Disk /dev/block/mmcblk0: XXXXMB
use the number in place of XXXX
mkpartfs primary fat32 0 XXXX
Click to expand...
Click to collapse
type "print" w/o quotes and see if it worked
type quit to exit parted
that should be all
EDIT: all this is while in recovery mode. Ace's method will only remove ext partition but it will not fill the empty space, wasting it
alright cool parted did the trick! Thanks alot everyone!
Tempestrs4 said:
You can use AmonRA's recovery image and format the sdcard with that. You can install it from the terminal in the phone.
su
flash_image recovery/sdcard/recovery-dream-RA-v1.3.2G.img
Click to expand...
Click to collapse
Make sure that there is a space between flash_image recovery and /sdcard
thank you. was a lot of help.
Hey guys, how do I get into the ADB shell?
you just answered your own question.
"adb shell"
After used "rm 1" I typed "print" and shows me same things. I can't format the microSD or delete the partitions, any help?.
OK.
So for the last week or two I've been trying to get myself fixed in this thread:
629469
You can read that for some background info. Seeing as this a new problem, I've posted a new thread.
I've pushed SuperD, signed-spl (danger) and ota-radio 2_22_19_26i to the phone.
But now I cant apply these updates. I choose "apply sdcard:choose zip"
and it says:
e:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid Argument)
E:Can't mount SDCARD:
HELP.
Wave invites for help (I'll try that one again)
I've run into the same problem but I got there a slightly different way.
I recently switched ROMs from kingklick's aosp 2.1 v1.5 to openeclair 1.5, and I wanted to switch back. I went to do the usual partition, wipe everything, apply update.zip and I got almost exactly the same error message that you got:
E: can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(File not found)
E: can't mount SDCARD:
With my limited knowledge of Unix, I decided to jump into the console and dig around in the dev folder, I didn't see anything in /dev/block that was called mmcblk0, there were several files called "loopX", and also "mtdblkX".
It seems like my phone is acting as though I do not have an SD card at all. I've been testing out different things, I started the process over again by trying to partition the SD card and noticed it finished almost instantly. And now when I connect it to the computer and turn on the USB connection, my computer does not recognize it as a storage device. I then popped out the SD card and put it into the computer itself, it seems fine but there were some extra dm files that I did not expect to see. Not sure what those files are or how they got there.
I have the Death SPL, and the last ROM I used was KingKlick's AOSP 2.1 v1.5
Does anyone out there have any idea why this happened or how I can fix it?
Both of you, it sounds like your sd card is formatted wrong or corrupt. From amon-ra recovery you should try to wipe again, including the SD, and repair SD EXT. If that doen't work go back and use the "format SD" option.
One more thing, please take a few minutes and put together a signature on the forum with all your info, phone, spl, rom, sd setup, what you like for breakfast, all that stuff. Much easier to tell where to start.
Edit...if this should happen to accidentally work, please don't send any wave invites. I will probably never get rid of my 25.
Wipe data - worked (supposedly)
Wipe dalvik - Error : Run 'wipe dalvik' via console!
Wipe SD:ext partition - Error : Run 'wipe ext' via console!
Repair SD:ext - Error : Run 'fs repair' via console!
I don't see an option for "Format SD" in Amon Ra's recovery v1.5.2, so I attempted to Partition SD and give 0 space to swap and ext2. That SAID it completed successfully, but it finished suspiciously fast, and upon inserting the SD into my computer, I can see that it was not re-partitioned nor wiped.
I went into the console and tried the commands mentioned in the error messages and got "No ext partition found!" from each command. I then went back to recovery to "partition" the SD with Swap - 192MB, Ext2 - 1024MB, Fat32 - remainder (approx 2.75GB). I then tried wiping and repairing again, and got the same error messages, then went back to console to try wiping from there, and again was told "No ext partition found!"
I noticed that my SD is class 4, but class 6 is recommended, I'm considering going to buy a new class 6 SD, do you think that will help?
Filled in my sig, did I miss any info?
dracoaffectus said:
Wipe data - worked (supposedly)
Wipe dalvik - Error : Run 'wipe dalvik' via console!
Wipe SD:ext partition - Error : Run 'wipe ext' via console!
Repair SD:ext - Error : Run 'fs repair' via console!
I don't see an option for "Format SD" in Amon Ra's recovery v1.5.2, so I attempted to Partition SD and give 0 space to swap and ext2. That SAID it completed successfully, but it finished suspiciously fast, and upon inserting the SD into my computer, I can see that it was not re-partitioned nor wiped.
I went into the console and tried the commands mentioned in the error messages and got "No ext partition found!" from each command. I then went back to recovery to "partition" the SD with Swap - 192MB, Ext2 - 1024MB, Fat32 - remainder (approx 2.75GB). I then tried wiping and repairing again, and got the same error messages, then went back to console to try wiping from there, and again was told "No ext partition found!"
I noticed that my SD is class 4, but class 6 is recommended, I'm considering going to buy a new class 6 SD, do you think that will help?
Filled in my sig, did I miss any info?
Click to expand...
Click to collapse
to format it, just go to partition, then select 0 for the first two and rest for fat 32. You don't need a new card unless you're running a hero rom, and a class 4 is actually pretty fast. If formatting it doesn't work its done. This happened to me on a brand new class 6 transcend. Sent it back and got a sandisk. Good luck
I have the same problem wiht my G1 and am sending back my phone to HTC for this.
I have made a post here:
http://forum.xda-developers.com/showthread.php?p=5594269
All our phones have activated a memory debugging mode from from hboot. Modifying anything while booted to recovery or system doesn't affect anything because the trigger is happening from hboot.
You can still use fastboot while stuck in this mode. But your phone has no sd card access at the moment because it is locked by the hboot for writing debug logs.
I found that I was not able to flash in fastboot, as my hboot showed S-ON. However it was still possible to use fastboot boot.
Run cat /proc/cmdline
You will see that it says something like the following:
board_trout.disable_uart3=1 board_trout.usb_h2w_sw=1 board_trout.disable_sdcard=1 smisize=64 androidboot.baseband=3.22.26.17 androidboot.cid=ROGER001 androidboot.carrier=Rogers androidboot.keycaps=qwerty androidboot.mode=normal androidboot.serialno=HT********** androidboot.bootloader=1.33.2005 no_console_suspend=1 con
sole=null
You could mount the cache partition to your sdcard directory for flashing files:
adb shell mount -t yaffs2 /dev/block/mtdblock4 /sdcard
I've had this problem for more than a week. I have tried changing SPL, unrooting, recompiling my boot.img, and appending kernel commands.
You can also force your recovery/system to mount the sdcard, but your phone will error out because both the hboot and system will try to write to the sdcard. There is a high chance of corrupting the sd card (correctable by reformatting) this way, but you can generate a gold card:
fastboot -c "board_trout.disable_uart3=0 board_trout.usb_h2w_sw=0 board_trout.disable_sdcard=0" boot recovery.img
The -c switch appends to the kernel cmdline at the end.
There is a working solution if you have SPL 1.76.x in your HBOOT. The command to disable memory debug logs is simply
fastboot oem enableqxdm 0
However I have never seen this SPL for the dream. 32B magic users who flashed this SPL with the accompanying radio ended with semi-bricks, with their SPLs showing 32A board. Attempts to downgrade back to 1.33.x have not worked. Here's the thread:
http://forum.xda-developers.com/showthread.php?t=625604
I did theorize that we might have been able to upgrade our spl and radio to 1.76.x, run the enableqxdm command, and then downgrade back to 1.33.2010 using the test ruu. The 1.33.2010 works for the 32A magic, the 32B magic and the dream. This is one of the variants of the so called danger spl. If you have 1.33.2005 you already have a spl from the magic.
hiddengopher said:
to format it, just go to partition, then select 0 for the first two and rest for fat 32. You don't need a new card unless you're running a hero rom, and a class 4 is actually pretty fast. If formatting it doesn't work its done. This happened to me on a brand new class 6 transcend. Sent it back and got a sandisk. Good luck
Click to expand...
Click to collapse
Ok, I tried that already and it didn't work. So you're saying the SD card is useless now and I just need to get a new one?
and Xaueious, I read your post and I have one question. What do you recommend I do?
dracoaffectus said:
Ok, I tried that already and it didn't work. So you're saying the SD card is useless now and I just need to get a new one?
and Xaueious, I read your post and I have one question. What do you recommend I do?
Click to expand...
Click to collapse
Try this first.
Enter recovery then console
1. type parted /dev/block/mmcblk0
2. type rm 2 to remove ext
3. type rm 3 to remove swap
to resize fat32:
4. type print to get start value and sdcard size
5. type resize 1 <start> <sdcard size> (if i were doing this for my card it would be resize 1 512B 8169M)
Then put the card in computer and format fat32. (just to be sure)
Put it back in the phone and recovery and partition.
If no other way works, the card may be corrupt.
You could use GPARTED in linux for this. Even a GPARTED live cd would be good. In fact that may be your best option.
billquinn1 said:
Try this first.
Enter recovery then console
1. type parted /dev/block/mmcblk0
2. type rm 2 to remove ext
3. type rm 3 to remove swap
to resize fat32:
4. type print to get start value and sdcard size
5. type resize 1 <start> <sdcard size> (if i were doing this for my card it would be resize 1 512B 8169M)
Then put the card in computer and format fat32. (just to be sure)
Put it back in the phone and recovery and partition.
If no other way works, the card may be corrupt.
You could use GPARTED in linux for this. Even a GPARTED live cd would be good. In fact that may be your best option.
Click to expand...
Click to collapse
also, you're going to want to go to "go to console" in recovery to do this
billquinn1 said:
Try this first.
Enter recovery then console
1. type parted /dev/block/mmcblk0
2. type rm 2 to remove ext
3. type rm 3 to remove swap
to resize fat32:
4. type print to get start value and sdcard size
5. type resize 1 <start> <sdcard size> (if i were doing this for my card it would be resize 1 512B 8169M)
Then put the card in computer and format fat32. (just to be sure)
Put it back in the phone and recovery and partition.
If no other way works, the card may be corrupt.
You could use GPARTED in linux for this. Even a GPARTED live cd would be good. In fact that may be your best option.
Click to expand...
Click to collapse
I went to console and typed "parted /dev/block/mmcblk0" and it said "Error: Could not stat device /dev/block/mmcblk0 - No such file or directory"
I tried "parted /dev/block/mtdblock0" instead and got into parted, but when I tried any command such as "print", I got "Error: /dev/block/mtdblock0: unrecognised disk label"
dracoaffectus said:
I went to console and typed "parted /dev/block/mmcblk0" and it said "Error: Could not stat device /dev/block/mmcblk0 - No such file or directory"
I tried "parted /dev/block/mtdblock0" instead and got into parted, but when I tried any command such as "print", I got "Error: /dev/block/mtdblock0: unrecognised disk label"
Click to expand...
Click to collapse
I would say the sd card is dead. Try someone else's or a spare.
Picked up a 2GB microSD at the store for like $10 and got the same results right from the beginning.
So this means it's something wrong with my phone, and not the SD card.
Any suggestions?
....can I unroot?
I don't know if this matters, but I noticed some dm files on my sdcards after trying to startup my phone.
EDIT: I managed to UNroot my phone back to RC29 following the instructions on theunlockr.com. Now I have to contemplate if I'm ready to jump straight back into hacking again.
EDIT2: Ok, so now I'm back on the latest OpenEclair. The key to "fixing" it was to get a totally clean start by UNrooting my phone (http://bit.ly/5qbzIU thanks Unlockr.com). I wasn't able to do step 1 cause I was getting the same errors as before, so I skipped straight to loading the DreaIMG.nbh file, then continued to update to cupcake, load the latest radio, danger SPL, and openEclair, now my phone is working again. (p.s. already on Wave, so no need to send that invite Lachy95 )
Thanks
Its all fixed.
Used a different sd card, im stupid.
Thanks you thank you thank you
ill always remember
I have been searching the forums for 2 hours trying to figure this out and I cannot find out how. I tried following the tutorials on the forums here on how to partition the SD card but none of the settings that were listed are not on my recovery. But I still tried it anyways. Here is the list of options on my recovery
Reboot system now
Nandroid v2.2 backup
Nandroid v2.2 restore
Apply sdcard:update.zip
Apply sdcard:choose zip
Wipe data/factory reset
Wipe SD:ext partition
Wipe SD:dalvik-cache
Part SD:fat32+ext2+swap
Part SDnly fat32
Repair ext filesystem
Convert ext2 to ext3
Fix apk uid mismatches
Fix rotate
USB Mass storage on
USB Mass storage off
The bottom says "Build : RA-heroc-v1.2.3".
Upon reading the tutorials, I decided to try something different. So I wiped ext partion, parted sd fat32 ext2 and swap, then converted ext2 to ext3. Applied PureHero 2.1 and I enabled Apps2SD, move apps to sd, move dalvik cache to sd, enable JIT, and changed dalvik heap to 24mb. It rebooted and none of the applications I downloaded and installed were transferred to the SD.
Before this I applied a rom before wiping and parting and changed the same settings and it wasn't working then either.
I tried using the cmd and located to my android-sdk-windows and tried finding what version of apps2sd I had but it kept aborting. I tried repairing and it kept aborting, I even tried installing and it kept aborting.
I am at a loss here and I am trying to get all of this working.
It is a 2gb card and it is only showing 1.34gb available so I have no idea how to give me the full 2gb like it was before I tried partitioning.
Before I posted this, I applied the program at http://forum.xda-developers.com/showthread.php?t=715116 and that didn't work as well.
Please help.
I'm not sure if it makes a difference, but I would try to upgrade to RA-heroc-v1.6.x, it might be your recovery not partitioning correctly or something. Once you have upgraded, go ahead and wipe everything (data, dalvik, and ext). Flash your ROM. Before you move your dalvik to the sd card you want to make sure you have at least a class 4 sd card. Once your phone is booted up check your internal memory and you should have 90+M out of 159 or so. If you have that then I am pretty sure your ap2sd is working. You can also check to make sure it is working through adb. I don't use the option in recovery to move the apps to sd. Hope this helps, and I hope my information is correct, lol. I still consider myself a noob.
Ok ill do some research on how to update and see what I find. If that don't work then ill come back and keep you updated.
Thanks
EDIT: I have tried updating my Recovery using FlashRec and it isn't backing up my recovery or finding the recovery at all. I am on ubuntu so maybe that might be the problem, idk. Is there any other way I can update my recovery? I have 1.6.2 downloaded and just need to apply it.
puppetmstr said:
Is there any other way I can update my recovery? I have 1.6.2 downloaded and just need to apply it.
Click to expand...
Click to collapse
The instructions are here http://forum.xda-developers.com/showthread.php?t=581521#1
I used the adb method last night no problem.
Note: the first thing it tells you to type is "mount -a"
After which your phone might spit out some sort of error message. Don't worry about it, it doesn't affect anything. That's what people said, and it didn't affect me.
c00ller said:
The instructions are here http://forum.xda-developers.com/showthread.php?t=581521#1
I used the adb method last night no problem.
Note: the first thing it tells you to type is "mount -a"
After which your phone might spit out some sort of error message. Don't worry about it, it doesn't affect anything. That's what people said, and it didn't affect me.
Click to expand...
Click to collapse
Well this is confusing lol. I went into recovery, went into USB mode getting ready to update my recovery option and a screen popped up in ubuntu with the folders app, app-private, dalvik-cache, and lost+found. Apparently I had apps2sd working the entire time... But I nandroid last night back to ZenEXP. Idk if it still works in Pure Hero.
But now that I have apps2sd working, I can flash a new rom and still have my applications right?
EDIT: In Windows 7, it doesn't show the partition anymore for the apps2sd. So im just gonna go ahead and update recovery then repartition everything.
Please update with whether or not your apps still work after flashing a new ROM, I want to know if it works like that.
c00ller said:
Please update with whether or not your apps still work after flashing a new ROM, I want to know if it works like that.
Click to expand...
Click to collapse
I cant update the recovery at all. I have tried both ways and it fails.
I tried adb and as soon as i try to use the command "mount -a" it says "no such device". I tried using "mount /sdcard" and it says "Device or resource is busy".
On the Fastboot + adb I can load into fastboot. But when i type "fastboot boot recovery-RA-heroc-v1.6.2-blue.img" it says "cannot load fastboot boot 'recovery-RA-heroc-v1.6.2-blue.img'".
I tried pressing the trackball on fastboot usb and the screen goes black for a second, then i hear a connect noise in the speakers then it shows fastboot for a split second then fastboot usb again.
Also in Fastbot +adb when I use the command "adb shell mount /sdcard" it says "device not found".
EDIT: im also starting to think my adb shell is broken or something lol.
Ok nevermind I got it working. I typed mount /sdcard and it said it was busy but then i used the command "flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2-blue.img" then Rebooted into recovery and it says 1.6.2 and its blue. I just hope I did it the right way and didnt **** anything up...
EDIT: Ok well I partitioned it with 64mb swap, 1024mb ext2, converted to ext3, and loaded up PureHero 2.1. How do I know if it is working? I have my DConfig options set to move dalvik and apps to sd, with JIT enabled. Do I just install an app and see if the internal memory lowers or stays the same? How do I access the apps folder through USB mode?
This is how to tell if you have A2SD working
http://forum.xda-developers.com/showpost.php?p=6848245&postcount=80
1-When ı push amon ra and restrat my devices its otomaticaly turn orgınal recovery condition.İ try to delete scipt but not successfull i need help
2- Posted by djmcnz
Code:
adb shell pm setInstallLocation 1
Well set future installs to "internal" (sd-ext).
You'll need to manually move the ones already on sd-fat back to "internal" using Manage Applications... then fixed...
This is the only a thing over adb and may i need any ext 3 or ext 4 partition my my sd card and how must be its size
I'm trying really hard to figure out how to respond to your questions, but I may be misunderstanding what you are asking.
1) What technique did you use for trying to flash Amon_RA's recovery? Have you already rooted your phone? Assuming you have rooted via the "fastboot oem unlock" method, you should be able to just execute "fastboot flash <Amon_RA_filename>.img recovery". Alternatively, you could install ROM Manager from the Market and use that to flash ClockworkMod recovery, which accomplishes the same thing. The ROM Manager route is generally much easier, as you can do it all from the phone. Your phone MUST be rooted to install a custom recovery.
2) If you are hoping to use the DarkTremor apps2ext method, you must have an ext2/3/4 partition on your SD card. You can partition your SD card from whichever recovery you end up with, but keep in mind that you will lose ALL data on the SD card so be sure to back it up first. 512MB should be more than enough for most people; I think my ext partition is 768MB or something.
Does this help?
I'm trying really hard to figure out how to respond to your questions, but I may be misunderstanding what you are asking.
1) What technique did you use for trying to flash Amon_RA's recovery?
via fastboot :
fastboot devices
fastboot flash recovery recovery-RA-passion-v2.2.1.img
And reboot.
----------------
Have you already rooted your phone?
Yes, i rooted
i have unlock boot loader
Assuming you have rooted via the "fastboot oem unlock" method,you should be able to just execute "fastboot flash <Amon_RA_filename>.img recovery".
i am anti-ClockworkMod recovery man.İts requiers too many permission
----------------------------------
when i try to use recovery its turn orginal state.
this method doesnt work,am i need to do this things in recovery mod
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
#1: From the console:
As mentionned in many previous posts, I have tried the following commands once connected to the nexus
mount: Operation not permitted
http://forum.xda-developers.com/showthread.php?t=740748
------------------------------------------------
2) If you are hoping to use the DarkTremor apps2ext method, you must have an ext2/3/4 partition on your SD card. You can partition your SD card from whichever recovery you end up with, but keep in mind that you will lose ALL data on the SD card so be sure to back it up first. 512MB should be more than enough for most people; I think my ext partition is 768MB or something.
İ def. understand but how usage of this script
Code:
adb shell pm setInstallLocation 1
Well set future installs to "internal" (sd-ext).
this way ?
Does this help?
Cralin said:
i am anti-ClockworkMod recovery man.İts requiers too many permission
Click to expand...
Click to collapse
ClockworkMod Recovery makes use of the exact same file access permissions as Amon_RA's recovery. As a user, you aren't really aware of the permissions required, since it is a pre-OS function and isn't explicitly granted any permissions from Android. ROM Manager requires a bunch of permissions for good reason - it has to be able to flash recoveries and ROMs. If you would try flashing a recovery using ROM Manager, it might help eliminate some issues.
when i try to use recovery its turn orginal state.
this method doesnt work,am i need to do this things in recovery mod
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
#1: From the console:
As mentionned in many previous posts, I have tried the following commands once connected to the nexus
mount: Operation not permitted
http://forum.xda-developers.com/showthread.php?t=740748
------------------------------------------------
Click to expand...
Click to collapse
Based on the thread that you referenced, the solution to that poster's issue was to make sure USB Debugging was enabled. Is yours enabled?
2) If you are hoping to use the DarkTremor apps2ext method, you must have an ext2/3/4 partition on your SD card. You can partition your SD card from whichever recovery you end up with, but keep in mind that you will lose ALL data on the SD card so be sure to back it up first. 512MB should be more than enough for most people; I think my ext partition is 768MB or something.
İ def. understand but how usage of this script
Code:
adb shell pm setInstallLocation 1
Well set future installs to "internal" (sd-ext).
this way ?
Does this help?
Click to expand...
Click to collapse
The function of the adb shell pm setInstallLocation 1 command is not related to DT Apps2ext in any way. It is a command that controls how the Froyo apps2sd method behaves (that is, using the FAT partition of your SD card rather than requiring an additional ext partition). Setting it to "internal" simply prevents the Android OS from automatically moving any applications to the FAT partition of your card; since DT apps2ext makes your phone think that the /sd-ext (linux) partition is a part of your internal storage, apps will be installed there.
Getting close?
the solution to that poster's issue was to make sure USB Debugging was enabled. Is yours enabled? yes but i cant delet it.Everytime same solution.
i read Apps2ext tag but ı cant sove it can u explain me ?