Develop Bugs

[q] superoneclick

I just downloaded this after finding it online. it says im missing the runtime. how do i fix this

Make sure you use the most recent version which can be found in the Android dev section on these forums.

DirkGently1 said:
Make sure you use the most recent version which can be found in the Android dev section on these forums.
Click to expand...
Click to collapse
I was on the SuperOneClick Android dev. page but it would not allow me to post as I am a horrible underling and have no privileges.
So if anyone can post it there or answer it here then this is the failure error I get for the device (A coby Kyros MID8024)
I have everything set up and the tablet is running android 2.2 all drivers and other files needed are installed.
Installed terminal emulator confirms NO SU allowed.
Getting mount path...
rootfs on / type rootfs (rw)
ubi0:rootfs on / type ubifs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
none on /proc/bus/usb type usbfs (rw,relatime,devmode=666)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p3 on /data type ext4 (rw,nosuid,nodev,relatime,barrier=1,data=ordered)
/dev/block/mmcblk0p2 on /cache type ext4 (rw,nosuid,nodev,relatime,barrier=1,data=ordered)
/dev/block/vold/179:1 on /mnt/nand type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=utf8,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:9 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=utf8,shortname=
FAILED
Thanks if anyone can assist.

I used the super 1click method to root. It failed the first time but I rebooted my tablet and ran the super1click a second time and it sucessfully rooty my tablet...now looking for instructon for installing market.

Vernox701 said:
I used the super 1click method to root. It failed the first time but I rebooted my tablet and ran the super1click a second time and it sucessfully rooty my tablet...now looking for instructon for installing market.
Click to expand...
Click to collapse
Why not just flash google apps? That should install the market or you could download the apk for the market directly. See this thread: http://forum.xda-developers.com/showthread.php?t=1231290 .

Market fails to download anything on CM7 RC1V2 - screwed up partitioning?

I have installed CM7 RC1 on top of a brand new SBF179 (did a factory reset after the flashing of that one). While the market initially downloaded all the old apps, it now fails to install or update any apps from the market with a download unsuccessful message. To resolve this, I was looking at s0be's fix which supposedly works:
Here is the s0be's fix
1. adb shell
2. su
3. mkdir /cache/download
4. chown system:cache /cache/download
5. chmod ug+rwx /cache/download
6. chmod a+x /cache/download
I can su but my /cache dir is read only, which presumably is because there is not really a cache partition:
Code:
mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk1p21 on /system type ext3 (ro,noatime,nodiratime,barrier=1,data
=ordered)
/dev/block/userdata on /data type ext3 (rw,nosuid,nodev,noatime,nodiratime,error
s=continue,data=ordered)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
tmpfs on /data/tmp type tmpfs (rw,relatime,size=2048k)
/dev/block/pds on /pds type ext3 (rw,nosuid,nodev,noatime,nodiratime,barrier=1,d data=ordered)
Can anyone shed some light on this? Is there something wrong with the setup here? And why is the cache folder read only?

Market "Download paused" over WiFi
i also had market issue after downgrade cm7 rc1 to froyo rom somebody plz help ......
Market "Download paused" over WiFi

I had the same issue. I found this, and the "fix" worked.
http://www.androidpolice.com/2011/0...on-usb-storage-or-sd-card-problem-on-android/

That does not seem to be my issue - in any case that file does not exist in either locations. In my case I dont even get an error pop up just a silent, quick note in the download bar that the download was unsuccessful.
I still think its weird that my /cache folder is entirely empty and on a read only filesystem to boot?

in my case there is no download folder on /cache
i can able to download file from 2g/2g but download pause if i do it from WiFi ...

did u try flashing google apps again?
it works normally..

how to do it on stock froyo ?

ankit360 said:
how to do it on stock froyo ?
Click to expand...
Click to collapse
well u need to root it and install 2ndInit Recovey and then u can flash anything u like from custom recovery

I just reflashed gapps-2011-03-XX from stable recovery, no change.

nupi said:
I just reflashed gapps-2011-03-XX from stable recovery, no change.
Click to expand...
Click to collapse
i even try gapps-gb-20110613-signed.zip not working

I think I may just go back to RC0 tomorrow, that seemed to be more stable after all

So wiped data and cache on RC1V2, still same issue. Going back to RC0 now

Ok so I did reinstall 177 Nordic, flashed CM7.1RC0 and it STILL does not work.
However, I am still thinking there is something wrong with my partioning of the Defy as custom recovery gave me the following errors:
Can't mount /dev/block/memblk1p24
Can't mount /cache
Can't mount cache:recovery/log
Similarly, stock recovery upon starting also gives me:
Can't mount CACHE:recovery/command
Can't mount CACHE:recovery/caller
Can't mount CACHE:recovery/log
Last vain hope of going back to 177-Nordic and not installing CM7 for now, let's see what happens there.

where apk get save ? /cache/download or /cache ?
when i create download folder in cache it get deleted automatically and downloadfile.apk is get created is this normal plz help me ....

On vanilla 177-NORDIC it works. Confuses the hell out of me.

But also, I get a much different filesystem hierarchy - now I actually get /cache, android secure etc!
$mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk1p21 /system ext3 ro,noatime,nodiratime,barrier=1,data=ordered 0 0
/dev/block/userdata /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/cache /cache ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,barrier=1,data=ordered 0 0
tmpfs /tmp tmpfs rw,relatime,size=2048k 0 0
/dev/block/pds /pds ext3 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.trueaxis.jetcarstuntslite-1 vfat ro,dirsync,nosuid,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
$
Click to expand...
Click to collapse
I still think there is something wrong with the CM7 mount points I get!

I had the problem at rc0. Also got the mounting error. What worked for me was to unmount the cache and than mount again via recovery.
Sent from my MB525 using XDA App

How do I unmount/mount stuff in recovery? Also, did that fix market issues?

For me it fixed the problem. I had also this problem on RC0 and got the error of cant mount cache.
You can unmount and mount it in custom recovery. It do not exactly know where it is in recovery. Thought it was at the advanced menu.
Sent from my MB525 using XDA App

This explains why this happens and how to fix it:
http://forum.cyanogenmod.com/topic/19100-cm7-rc3-market-fails-to-download-big-apps/
Give me thanks for this if it helps, it took me hours to find this fix! thanks

Despite changes RW into RO on ext4 partition

Hi!
After some experiments , ext4 partition lost property rw .
Installing android_3.2.78.ext4 we give root perm. with rights rw . Ok that is true.
Now just installing ES File Explorer , enabe only Root Explorer and change Home Directory : / we can : copy , mkdir, mov , rm .....anywhere ( this is normal )
But how I lost this right .....
Shut down device or >adb reboot .....when device is open I have tried this command:
>adb shell
/# mount
..........................
/dev/loop0 on / type ext4 (ro,relatime,barrier=1,data=writeback)
............................
Now I can't do even >adb shell mkdir xxx ........cannot create directory xxx Read-only file system .
Expert opinions wait !!!

Add all commands > adb shell mount
.............................................................................................................
c:\Program Files (x86)\Android\android-sdk\tools>adb shell
BusyBox v1.7.2 (2011-12-22 03:11:13 CET) built-in shell (ash)
Enter 'help' for a list of built-in commands.
/ # mount
mount
rootfs on / type rootfs (rw)
/dev/mmcblk0p2 on /mnt/system type ext4 (rw,noexec,noatime,barrier=1,data=ordere
d)
/dev/mmcblk0p4 on /data type ext4 (rw,noexec,noatime,barrier=1,data=ordered)
/dev/loop0 on / type ext4 (ro,relatime,barrier=1,data=writeback)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
usbfs on /proc/bus/usb type usbfs (rw,relatime,devuid=1000,busuid=1000,listuid=1
000)
tmpfs on /tmp type tmpfs (rw,relatime,mode=775,gid=1000)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p1 on /mnt/rawfs type rawfs (rw,relatime)
/dev/block/mmcblk0p2 on /mnt/system type ext4 (rw,nosuid,noexec,noatime,barrier=
1,data=ordered)
/dev/block/mmcblk0p4 on /data type ext4 (rw,nosuid,noatime,barrier=1,data=ordere
d)
/dev/fuse on /mnt/nand type fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id
=1015,default_permissions,allow_other)
/dev/fuse on /mnt/storage type fuse (rw,nosuid,nodev,relatime,user_id=1000,group
_id=1015,default_permissions,allow_other)
/dev/block/vold/179:17 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,
noatime,nodiratime,uid=1000,gid=1023,fmask=0000,dmask=0000,allow_utime=0022,code
page=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/ #
..............................................................................................................

Very very strange!!!! No it's work , I have again rights RW .....strange is that I did nothing.....just maybe I have not used 24 hours ....

[Q] N7105 Bootloop / Access Internal Storage Recovery / Signature Verfication Failed

Hello everyone!
I am (until recently) happy user of a Galaxy Note II N7105. And because it already did everything I needed, I never rooted it, installed CWN/TWRP or flashed a custom ROM. It is 4.1.2 (Hong Kong) version and had only OTA updates until now.
Problem description:
At some point I ran out of internal storage about which the system notified me. I deleted some stuff and rebooted - and then it got stuck in a boot loop. That is after the initial splash screen, it repeats the pretty blue/purple swoosh animation with SAMSUNG indefinitely (at least 20min, battery pulled after that).
As for now, I can get into RECOVERY MODE and DOWNLOAD MODE. Because I still have important data on the internal sd, I don't want to wipe the data/factory reset it. My goal now is just to access the internal storage and extract the data stored on it.
What I have tried:
After installing the drivers I could connect my phone with my laptop. From there I could access my phone via adb
Code:
>adb devices
List of devices attached
42f71b0bf29aaf97 recovery
where I entered the shell (no root --> no su rights) to access all the data and, if possible, use adb pull to copy it to my laptop. But somehow, the two folders sdcard and sdcard1 are empty:
Code:
>adb shell
[email protected]:/ $ ls
ls
cache
data
default.prop
dev
efs
etc
fstab.smdk4x12
init
init.rc
lib
lpm.rc
preload
proc
res
root
sbin
sdcard
sdcard1
sys
system
tmp
ueventd.goldfish.rc
ueventd.rc
ueventd.smdk4x12.rc
[email protected]:/ $ cd sdcard
cd sdcard
[email protected]:/sdcard $ ls
ls
[email protected]:/sdcard $ cd ../sdcard1
cd ../sdcard1
[email protected]:/sdcard1 $ ls
ls
[email protected]:/sdcard1 $
So I was wondering if the internal sdcard (suspect it should be /sdcard) needed to be mounted first, but I could not find a mount point to do so:
Code:
[email protected]:/sdcard1 $ mount
mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p12 /cache ext4 rw,nodev,noatime,nodiratime,barrier=1,data=ord
ered 0 0
/dev/block/mmcblk0p13 /system ext4 rw,nodev,noatime,nodiratime,barrier=1,data=or
dered 0 0
==> Is there a way to mount/access the internal sd card from recovery?​I also tried to simple use the command adb pull so that it would copy everything. sadly, it only copied the two folders /sys and /system which are no use to me.
What I have also tried:
Install stock ROMS of 4.1.2 and 4.3 from external sd, via ODIN and adb sideload
GT-N7105_TGY_1_20121026091349_N7105ZHALJ4.zip
NEE-N7105XXUEMK5-20131119111744.zip
(and several others, accidentally also ones for N7100 which also didn't work)​but it resulted in E: signature verification failed
Install CWM and TWRP from external sd and ODIN but both also ended up in E: signature verification failed
Kies: But this somehow always entails a factory reset/wipe data which I want to avoid
==> Where can I get an original 4.1.2 stock ROM that is signed by Samsung?​
I'm open to whatever approaches to get the data.
My thought is: Once it is connected to the laptop, can't I access it as an external hard drive? Any program to do that?
Any help is greatly appreciated!
mrmuhkuh

KF2 Soft brick - /data and /sdcard read-only

My mom has a Kindle 2nd Generation running 10.5.1 stock.
The other day, it started rebooting, but not in the traditional bootloop sense. The OS would load to the lock screen, you could swipe and use it (albeit sluggishly) for approximately 30 seconds before it rebooted again. So, it made it impossible to access the device via ADB.
I made a factory cable, accessed fastboot, and did the following:
fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
fastboot -i 0x1949 flash recovery otter2-twrp-2.6.3.1-recovery.img
fastboot -i 0x1949 flash boot otter2-freedom-boot-10.4.6.img
(if using a fastboot USB cable, swap to a normal USB cable before entering the next command)
fastboot -i 0x1949 oem recovery
Click to expand...
Click to collapse
This worked fine. I was able to get into recovery mode with TWRP and access ADB. I pulled all the data off the /sdcard partition. This was a big concern since my mom has been using this thing for a couple years now and she's collected quite a bit. Originally, my directive was to factory reset and reflash the stock firmware from Amazon: update-kindle-10.5.1_user_5174820.bin. It would be nice if they supplied a checksum, but they don't apparently.
Anyway, the more I thought about it, I thought I could clear some caches, uninstall some apks and that would resolve the issue without a new system image. Then I started to notice the problem:
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 336.6M 136.0K 336.5M 0% /dev
/dev/block/mmcblk0p13
5.6G 4.8G 755.9M 87% /data
/dev/block/mmcblk0p13
5.6G 4.8G 755.9M 87% /sdcard
/dev/block/mmcblk0p12
639.8M 11.0M 628.8M 2% /cache
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
/dev/block/mmcblk0p13 on /data type ext4 (ro,seclabel,relatime,user_xattr,barrier=1,data=ordered)
/dev/block/mmcblk0p13 on /sdcard type ext4 (ro,seclabel,relatime,user_xattr,barrier=1,data=ordered)
/dev/block/mmcblk0p12 on /cache type ext4 (rw,seclabel,relatime,user_xattr,barrier=1,data=ordered)
~ #
Click to expand...
Click to collapse
Both /data and /sdcard are read-only. They also use the same block device. Maybe that's normal? I've already tried remounting the partitions read-write to no avail.
mount -o rw,remount /sdcard
mount -o rw,remount /data
Click to expand...
Click to collapse
Both commands execute as if they were accepted successfully (ala no output). However, rechecking mount's output, shows no change. It's still read-only.
I've tried sideloading in TWRP, but that resulted in a protocol fault. Also through TWRP, the factory reset succeeds, but actually does nothing. All of the data is still there. My other idea is to push the image onto the /cache partition (there's just enough room), and try to install that way, but I have a feeling that 1) won't work and 2) may exacerbate problems.
I'm stuck. Anyone have any ideas?

Solved
I was able to free the partitions.
fastboot -i 0x1949 erase userdata
Click to expand...
Click to collapse
It must have been some sort of corruption in userspace. I had previously tried a wipe through TWRP which was claimed to be successful. I still can't determine if TWRP doesn't check all their syscalls and handle the return codes or the Linux subsystem in Android is the root of the bugs. Either way, upon reboot, the device returned to factory "out of box" state.