Develop Bugs

whoami: not found after root

When I try to perform a whoami from:
$ su
# whoami
whoami: not found
# busybox whoami
whoami: unknown uid 0
# system/xbin/whoami
system/xbin/whoami: not found
# system/bin/whoami
system/bin/whoami: not found
This is preventing me from running titanium backup among other things.
Does anyone know how I can fix this?

jerrberr said:
When I try to perform a whoami from:
$ su
# whoami
whoami: not found
# busybox whoami
whoami: unknown uid 0
# system/xbin/whoami
system/xbin/whoami: not found
# system/bin/whoami
system/bin/whoami: not found
This is preventing me from running titanium backup among other things.
Does anyone know how I can fix this?
Click to expand...
Click to collapse
Did you run
busybox --install /system/xbin
While in recovery?

Yeah I'm having the same issue. When I did those commands in recovery it came back with a "--install: applet not found" error. For some reason the superuser (ninja icon) doesn't display anything in the white list. I do have su with the shell, but it's just not working. I also downloaded the newest busybox inside TB. I'm at a loss.
OK loss over with.....here is the fix:
Reboot your phone into recovery and mount the /system partition.
Code:
adb shell
su
cd /system/xbin
/system/bin/cat /sdcard/busybox > busybox
chmod 777 busybox
./busybox --install -s /system/xbin
This correctly installs busybox incase you messed something up to begin with. Now we need to deal with superuser permissions.
Code:
adb shell
su
/system/bin/cat /system/bin/sh > /system/bin/su
/system/bin/chmod 4777 /system/bin/su
Once at root (#) prompt in adb recovery
export PATH=$PATH:/system/bin
cd /system/app
cat /sdcard/Superuser.apk > Superuser.apk
cd /system/bin
cat /sdcard/su > su
ln -s /system/bin/su /system/xbin/su
chmod 06755 su
Did that and boom everything is working just fine now. Titanium backup is asking for superuser permissions etc. Thanks to everyone who has been posting and knows more about linux than me!

jmdearras said:
Did you run
busybox --install /system/xbin
While in recovery?
Click to expand...
Click to collapse
Nope - I used the newest (for Jun-29-2010) unrEVOked ota.zip/busybox/payload-update.zip toolchain that is supposed to do all of that for me. Maybe this needs tweaked?
The point is moot - I was trying to run titanium backup with the usb cable attached. Once I disconnected the phone from usb, titanium backup is working fine.
On the other hand, I think that I ought to be able to call whoami from the client machine adb shell or from a shell window in the phone (connectbot) with the usb cable connected, so I'll probably give this a try.

Rooting the Ampe A10 Dual core 3G

Rooting The Ampe A10 Dual core 3g ICS
1.
Download and install the drivers required to connect the tablet to a windows pc (I used Win7) not any old ADB drivers will do the first ones I came across didn’t work so I recommend downloading from here - http://www.topnotchtablets.com/installADBdriver (PDA Net for Android)
2.
Download the rooting program from this thread here
http://forum.xda-developers.com/showthread.php?t=1886460
Bin4ry…zip direct link - http://ul.to/h44f6vni
3.
Extract the contents of the zip folder into a directory on the pc
Rooting is done at your own risk!
4.
Plug the tablet into the pc and run the RunMe.bat file
Screen will pop up select option 1 Normal
follow the instructions on the screen, it will refer to the tablet and you need to select restore. Once updated a reboot will happen and root should be done, if you wish to check root download root checker from the android market
enjoy
you mite like Webkey for example to remotely use the Android

Thanks, I've already rooted the same device as Sanei N10 3G (MSM8625 CPU).
But do you know something about a recovery mod that works with this tablet?

recovery
Hello, I also Sanei N10. found recovery and third-party firmware if found give the link

murkin82 said:
Hello, I also Sanei N10. found recovery and third-party firmware if found give the link
Click to expand...
Click to collapse
Be careful, we're talking about the 3G version with Qualcomm Snapdragon CPU.
If you have anything but root, pls post it.

I have no Ampe A10/Sanei N10 Dual core 3G. recovery or firmware met?!

snapon said:
Rooting The Ampe A10 Dual core 3g ICS
2.
Download the rooting program from this thread here
http://forum.xda-developers.com/showthread.php?t=1886460
Bin4ry…zip direct link - http://ul.to/h44f6vni
Click to expand...
Click to collapse
First of all, thank you for your help!
Could you please upload this file on a site where one can really download it and isnʼt directed elsewhere to register for a paid package?
There are many good file sharing sites, even Googleʼs Drive.

murkin82 said:
Hello, I also Sanei N10. found recovery and third-party firmware if found give the link
Click to expand...
Click to collapse
The Ampe 10 seems to have its own recovery built in and can be started by turning the device off turn it back on hold both volume up and power. From this menu you can recover / update from the SD card. I found the original firmware here 86pp.com/download_view.asp and have installed this one you need to extract msm7627a_fw8937-ota-eng_mmc.zip from the downloaded zip copy it to the SD
I think the firmware can also be found here: szampe.com/support_down.asp? but as its all in Chinese its difficult to tell

Mazarin07 said:
First of all, thank you for your help!
Could you please upload this file on a site where one can really download it and isnʼt directed elsewhere to register for a paid package?
There are many good file sharing sites, even Googleʼs Drive.
Click to expand...
Click to collapse
Its not mine to re-distribute and you can download from that fileshare site without registering or paying you just use the 'Free' option and wait a little longer

thanks
thanks worked for me

murkin82 said:
Hello, I also Sanei N10. found recovery and third-party firmware if found give the link
Click to expand...
Click to collapse
Try this site slatedroid.com/blog/85/entry-96-aokp-cm9-cm10-installation-guide-for-ampe-a10-sanei-n10/

Thanks in advance!
W3sti said:
Thanks, I've already rooted the same device as Sanei N10 3G (MSM8625 CPU).
But do you know something about a recovery mod that works with this tablet?
Click to expand...
Click to collapse
Did you mean you rooted Sanei N 10 with dual core Qualcomm MSM8625? Could you please tell which method you followed, or how you managed to do it.
And also, will I ever be able to install Jelly bean on this particular tablet?
Thanks in advance!

Mt Everest said:
Did you mean you rooted Sanei N 10 with dual core Qualcomm MSM8625? Could you please tell which method you followed, or how you managed to do it.
And also, will I ever be able to install Jelly bean on this particular tablet?
Thanks in advance!
Click to expand...
Click to collapse
Try Tasselhofs rootscript at mediafire.com/?2jt4ft8xpfzyw2g
But in section :root I used this code:
Code:
adb root
adb shell "chmod 777 /system/local/tmp"
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
@PING 1.1.1.1 -n 1 -w 5000 >NUL
adb wait-for-device
adb shell "echo \"ro.kernel.qemu=1\"> /data/local.prop"
adb reboot
@PING 1.1.1.1 -n 1 -w 5000 >NUL
adb wait-for-device
adb remount
adb shell "chmod 777 /system/bin"
adb push su /system/bin/su
adb shell "chown root.shell /system/bin/su"
adb shell "chmod 06755 /system/bin/su"
adb shell "chmod 06755 /system/bin/su"
adb shell "ln -s /system/bin/su /system/xbin/su"
adb push Superuser.apk /system/app/.
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
adb push busybox /data/local/tmp/.
adb shell "chmod 755 /data/local/tmp/busybox"
adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
adb shell "chown root.shell /system/xbin/busybox"
adb shell "chmod 04755 /system/xbin/busybox"
adb shell "/system/xbin/busybox --install -s /system/xbin"
adb shell "rm -r /data/local/tmp/busybox"
adb reboot
It's not necessary to use any other options than 1. and 2.
After that install Titanium Backup and check for errors and let TB fix it (Some permissions seems to be "broken".).
snapon said:
Try this site slatedroid.com/blog/85/entry-96-aokp-cm9-cm10-installation-guide-for-ampe-a10-sanei-n10/
Click to expand...
Click to collapse
You cannot use this CM9/10, i'ts only for Allwinner A10 CPU!
For now, I didn't found a working recovery.img for MSM8625.

It worked fine, thank you very much! :good:
One problem still exist: the build.prop file still cannot be edited, is write-protected.
---------- Post added at 10:24 PM ---------- Previous post was at 10:18 PM ----------
snapon said:
...I found the original firmware here 86pp.com/download_view.asp....
I think the firmware can also be found here: szampe.com/support_down.asp? but as its all in Chinese its difficult to tell
Click to expand...
Click to collapse
It was deleted from the first site.
On the second site, more specifically from here, you can download the firmware (version 3 Nov, 2012), but I am afraid that everyting is in Chinese.

....
W3sti said:
Try Tasselhofs rootscript at mediafire.com/?2jt4ft8xpfzyw2g
But in section :root I used this code:
Code:
adb root
adb shell "chmod 777 /system/local/tmp"
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /data /data/local/tmp
adb reboot
@PING 1.1.1.1 -n 1 -w 5000 >NUL
adb wait-for-device
adb shell "echo \"ro.kernel.qemu=1\"> /data/local.prop"
adb reboot
@PING 1.1.1.1 -n 1 -w 5000 >NUL
adb wait-for-device
adb remount
adb shell "chmod 777 /system/bin"
adb push su /system/bin/su
adb shell "chown root.shell /system/bin/su"
adb shell "chmod 06755 /system/bin/su"
adb shell "chmod 06755 /system/bin/su"
adb shell "ln -s /system/bin/su /system/xbin/su"
adb push Superuser.apk /system/app/.
adb shell rm /data/local.prop
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
adb push busybox /data/local/tmp/.
adb shell "chmod 755 /data/local/tmp/busybox"
adb shell "/data/local/tmp/busybox mount -o remount,rw /system"
adb shell "dd if=/data/local/tmp/busybox of=/system/xbin/busybox"
adb shell "chown root.shell /system/xbin/busybox"
adb shell "chmod 04755 /system/xbin/busybox"
adb shell "/system/xbin/busybox --install -s /system/xbin"
adb shell "rm -r /data/local/tmp/busybox"
adb reboot
It's not necessary to use any other options than 1. and 2.
Hey in root you used the following commands means???how??
i have ordered this tablet and will reach me soon i think,i have the tasselhoof rootscript but it is as follows rite?
option 1 is to check the connection
option 2 is to root.
Then after choosing option 1 did you choosed option 2 or did something else???
can you explain briefly please??
Any help will be great...
Click to expand...
Click to collapse

I did root on my Sanei N10 3G Dualcore, but now I cannot find any recovery.img for CWM, can i use the one from single or quad core sanei N10 device?
I want to make a backup (nandroid) so waht can I do?
Thanks in advance

scotty2000 said:
I did root on my Sanei N10 3G Dualcore, but now I cannot find any recovery.img for CWM, can i use the one from single or quad core sanei N10 device?
I want to make a backup (nandroid) so waht can I do?
Thanks in advance
Click to expand...
Click to collapse
You cannot use an other image. For now it's not possible to use nandroid. Try "Titanium Backup Root" for a most complete backup.
---------- Post added at 08:47 PM ---------- Previous post was at 08:40 PM ----------
h.d.modi said:
...
Hey in root you used the following commands means???how??
i have ordered this tablet and will reach me soon i think,i have the tasselhoof rootscript but it is as follows rite?
option 1 is to check the connection
option 2 is to root.
Then after choosing option 1 did you choosed option 2 or did something else???
can you explain briefly please??
Any help will be great...
Click to expand...
Click to collapse
1. Edit the script, replace the code in section ":root", save the file and execute the script
2. Check the connection with option 1 and choose option 2 to root
3. If you don't know what i explained, ask somebody who knows a bit about batch-programming

its worked for sanei n10 dual core 3g tablet pc Thank you !

W3sti said:
You cannot use an other image. For now it's not possible to use nandroid. Try "Titanium Backup Root" for a most complete backup.
Click to expand...
Click to collapse
Thanks!
Is it possible to create an image out of an other one in an easy way and what do i need to do this?
Or is it to much complicated to work out an recovery image?
I am not really firm with those android things but willing to learn if possible with a "how to guide" for building recovery images

Worked great on Ampe A10, 5min job!
Any news about Android 4.1.x update/rom? Cyanogenmod? Any way to get Jellybean?

Tried to find a way to get jelly bean but i think there isn't any...
BTW, does anyone know SNES emulator that works with this tablet?

Please backup ur E980G Pro's File to share!!!

I need ATT G pro E980's base file,below:
1,m9kefs1.img
2,m9kefs2.img
3,drm.img
4,encrypt.img
5,eksst.img
6,persist.img
backup method: After root ur phone, execute below command
adb.exe shell su -c "mkdir /sdcard/System/"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p12 of=/sdcard/System/12m9kefs1.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p13 of=/sdcard/System/13m9kefs2.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p15 of=/sdcard/System/15DRM.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p22 of=/sdcard/System/22eksst.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p21 of=/sdcard/System/21encrypt.img"
adb.exe shell su -c "dd if=/dev/block/mmcblk0p26 of=/sdcard/System/26persist.img"
and share these files,,thx

[Q] F180K - lost sensors

Hi,
After my experiments with root, backup, change ROM etc. I've lost all my sensors:
Accelerometer, light sensor, orientation sensor, proximity, gyroscope, magnetic.
Pressure works fine.
Phone had one fall, but I think it's not a cause.
Back to stock rom (F180K20K_00.kdz) is not a solution (with LG mobile support tool - emergency firmware recovery). I did it few times - without effect.
To read sensors, I use this 2 apps:
https://play.google.com/store/apps/details?id=de.onyxbits.sensorreadout
https://play.google.com/store/apps/details?id=imoblife.androidsensorbox
I think, problem can be in backup tool:.
http://forum.xda-developers.com/showthread.php?t=2139861
after restore backup I've lost SD card (after flash E975 ROM), but I'm not sure, because I didn't check sensors with every step I make.
Most of my "activity" is in topic (I doubt that anyone will read this):
http://forum.xda-developers.com/showthread.php?p=43675111#post43675111
What can I do ?

Ganz.Conrad said:
Hi,
After my experiments with root, backup, change ROM etc. I've lost all my sensors:
Accelerometer, light sensor, orientation sensor, proximity, gyroscope, magnetic.
Pressure works fine.
Phone had one fall, but I think it's not a cause.
Back to stock rom (F180K20K_00.kdz) is not a solution (with LG mobile support tool - emergency firmware recovery). I did it few times - without effect.
To read sensors, I use this 2 apps:
https://play.google.com/store/apps/details?id=de.onyxbits.sensorreadout
https://play.google.com/store/apps/details?id=imoblife.androidsensorbox
I think, problem can be in backup tool:.
http://forum.xda-developers.com/showthread.php?t=2139861
after restore backup I've lost SD card (after flash E975 ROM), but I'm not sure, because I didn't check sensors with every step I make.
Most of my "activity" is in topic (I doubt that anyone will read this):
http://forum.xda-developers.com/showthread.php?p=43675111#post43675111
What can I do ?
Click to expand...
Click to collapse
May be a kernel fault , did you try flashing a different kernel? ( Don't know if you have other kernels than stock one for your version , since I have the international version E-975)
However ,good luck!

You may mess up with your efs partition.
You need a efs backup from another f180k.
Sent from my LG-E975 using xda app-developers app

I think I broke my phone when I made recovery from backup, and maybe it's EFS partition.
Is any of these files a part of kernel or EFS?:
adb.exe shell su -c "dd if=/sdcard/System/30DDR.img of=/dev/block/mmcblk0p30"
adb.exe shell su -c "dd if=/sdcard/System/20BNR.img of=/dev/block/mmcblk0p20"
adb.exe shell su -c "dd if=/sdcard/System/7BOOT.img of=/dev/block/mmcblk0p7"
adb.exe shell su -c "dd if=/sdcard/System/15DRM.img of=/dev/block/mmcblk0p15"
adb.exe shell su -c "dd if=/sdcard/System/22eksst.img of=/dev/block/mmcblk0p22"
adb.exe shell su -c "dd if=/sdcard/System/21encrypt.img of=/dev/block/mmcblk0p21"
adb.exe shell su -c "dd if=/sdcard/System/29fsg.img of=/dev/block/mmcblk0p29"
adb.exe shell su -c "dd if=/sdcard/System/36grow.img of=/dev/block/mmcblk0p36"
adb.exe shell su -c "dd if=/sdcard/System/12m9kefs1.img of=/dev/block/mmcblk0p12"
adb.exe shell su -c "dd if=/sdcard/System/13m9kefs2.img of=/dev/block/mmcblk0p13"
adb.exe shell su -c "dd if=/sdcard/System/14m9kefs3.img of=/dev/block/mmcblk0p14"
adb.exe shell su -c "dd if=/sdcard/System/18misc.img of=/dev/block/mmcblk0p18"
adb.exe shell su -c "dd if=/sdcard/System/10modemst1.img of=/dev/block/mmcblk0p10"
adb.exe shell su -c "dd if=/sdcard/System/11modemst2.img of=/dev/block/mmcblk0p11"
adb.exe shell su -c "dd if=/sdcard/System/16sns.img of=/dev/block/mmcblk0p16"
adb.exe shell su -c "dd if=/sdcard/System/32mpt.img of=/dev/block/mmcblk0p32"
adb.exe shell su -c "dd if=/sdcard/System/9pad.img of=/dev/block/mmcblk0p9"
adb.exe shell su -c "dd if=/sdcard/System/26persist.img of=/dev/block/mmcblk0p26"
adb.exe shell su -c "dd if=/sdcard/System/35reserved.img of=/dev/block/mmcblk0p35"
adb.exe shell su -c "dd if=/sdcard/System/6rpm.img of=/dev/block/mmcblk0p6"
adb.exe shell su -c "dd if=/sdcard/System/34rpmbak.img of=/dev/block/mmcblk0p34"
adb.exe shell su -c "dd if=/sdcard/System/16sns.img of=/dev/block/mmcblk0p16"
adb.exe shell su -c "dd if=/sdcard/System/17ssd.img of=/dev/block/mmcblk0p17"
adb.exe shell su -c "dd if=/sdcard/System/8tz.img of=/dev/block/mmcblk0p8"
adb.exe shell su -c "dd if=/sdcard/System/33tzbak.img of=/dev/block/mmcblk0p33"
adb.exe shell su -c "dd if=/sdcard/System/27tombstones.img of=/dev/block/mmcblk0p27"
adb.exe shell su -c "dd if=/sdcard/System/1modem.img of=/dev/block/mmcblk0p1"
Click to expand...
Click to collapse
And the most important: which one I shouldn't move from other phone to avoid change IMEI or other individual data?
I'm asking because I think, that moving EFS from other phone with FreeGee will change IMEI or other stuff.
Does Root can damage kernel?

anyone?

Ganz.Conrad said:
anyone?
Click to expand...
Click to collapse
I have the same problem.. if freegee was the problem, how to reapir it?

harvester said:
I have the same problem.. if freegee was the problem, how to reapir it?
Click to expand...
Click to collapse
My phone was in LG repair Service (warranty), they changed main board, software, and said "it's unrepairable". I don't have my phone now - changed to new one.
I'm pretty sure, that it can be repaired (i think it's software problem ), but i didn't found way to do it.

[Q] Is it possible to make a Nandroid backup DIRECTLY to PC hard disk?

Hello!
The title says it all! Is it possible to make a Nandroid backup directly to PC connected via USB? If yes, how?
Thanks!

amagalma said:
Hello!
The title says it all! Is it possible to make a Nandroid backup directly to PC connected via USB? If yes, how?
Thanks!
Click to expand...
Click to collapse
ADB pull can do almost anything. Step one of this OP http://forum.xda-developers.com/showthread.php?t=2128848 will show you how to backup everything.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

LinearEquation said:
ADB pull can do almost anything. Step one of this OP http://forum.xda-developers.com/showthread.php?t=2128848 will show you how to backup everything.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you for your answer!
The code in step 1 is:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img" # This will take a few minutes
adb pull /sdcard/boot0block.img
adb pull /sdcard/stock-boot.img
adb pull /sdcard/stock-recovery.img
adb pull /sdcard/stock-system.img # This will take a few minutes
What should I change in order to specify the exact path where to backup in my PC? And another question: will this create images that are exact copies in size? Which is to say, will I need 16GB of free space in my PC's hard drive? (I have the Nexus 2 16GB Wi-Fi)
Thanks!

What should I change in order to specify the exact path where to backup in my PC?
Click to expand...
Click to collapse
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
mkdir C:\name-of-the-file-you-made-on-your-pc-here
adb pull /sdcard/stock-boot.img/ [C:\name-of-your-file-make-on-on-your-PC-first)]
adb pull /sdcard/stock-recovery.img/ [C:\name-of-your-file]
adb pull /sdcard/stock-system.img/ [C:\name-of-your-file]
And another question: will this create images that are exact copies in size?
Click to expand...
Click to collapse
Yes
Which is to say, will I need 16GB of free space in my PC's hard drive?
Click to expand...
Click to collapse
What ever memory is in use is what you will need space wise for your nandroid. Look at the storage available and minus it from 16GB. That's the space you will need.
Find the name of the image to pull it. It may be labeled just plain recover.img, boot.img and (usually is.) What ever they are, just plug that info into the code. It all works the same you just have to tell (command) the computer what to pull. Sorry about the KFHD reference. I was on my tablet and that's where most of my help is focused at.

LinearEquation said:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
mkdir C:\name-of-the-file-you-made-on-your-pc-here
adb pull /sdcard/stock-boot.img/ [C:\name-of-your-file-make-on-on-your-PC-first)]
adb pull /sdcard/stock-recovery.img/ [C:\name-of-your-file]
adb pull /sdcard/stock-system.img/ [C:\name-of-your-file]
Yes
What ever memory is in use is what you will need space wise for your nandroid. Look at the storage available and minus it from 16GB. That's the space you will need.
Find the name of the image to pull it. It may be labeled just plain recover.img, boot.img and (usually is.) What ever they are, just plug that info into the code. It all works the same you just have to tell (command) the computer what to pull. Sorry about the KFHD reference. I was on my tablet and that's where most of my help is focused at.
Click to expand...
Click to collapse
Thank you very much for your help!