Database Develop

adb problems.......

first of all iv been trying to root my legend for hours and this is geting very furstarting... i am using the guide here http://forum.xda-developers.com/showthread.php?t=845512
i have finaly managed to get adb to work and have made my goldcard after 2 days of intense work and now im trying to downgrade my phone to root it
i am geting the following error in adb
when i type adb remount it says remount failed operation not permitted i have looked all over the net and found no answer
in additon to that when im trying to use adb push i type the following
adb shell
$su
su
#adb push flash_image /data/local/
adb push flash_image /data/local/
i just get the same line repeated how to excute commands from adb? this is very confusing since im noob with rooting also the following lines i don't know how to excute them too
adb push flash_image /data/local/
adb push misc1-2.img /data/local/
chmod 755 /data/local/flash_image
cat /dev/mtd/mtd0 > /sdcard/misc_backup.img
/data/local/flash_image misc /data/local/misc1-2.img
please explain to me how to use theese thanks!

That one is relatively easy. You could also follow Paul's guide but I like my approach better
Connect your phone to your PC. Second you have to install VISIONary r13 into your phone and do the "temproot" procedure. After a successful "temproot" you should be able to adb shell and then su. Fire up command prompt and issue:
adb shell
su
...you should have root privileges now (showing #). Next thing is backing up misc partition and replacing it with one from hack4legend-v5.zip. Extract this zip somewhere and fire another command promt there. Now you should upload flash_image binary and misc1-2.img:
adb push flash_image /data/local/
adb push misc1-2.img /data/local/
...switch back to 1st command prompt and change permission of flash_image_binary:
chmod 755 /data/local/flash_image
...and backup your current misc partition:
cat /dev/mtd/mtd0 > /sdcard/misc_backup.img
Now flash misc1-2.img:
Code:
/data/local/flash_image misc /data/local/misc1-2.img
exit
...and you are set to downgrade retaining HBOOT 1.00.
Click to expand...
Click to collapse
Read better, you have to open a new terminal for pushing the files to the phone, you can't use adb push while you are in adb shell.
BTW you should avoid posting questions in development section.

Just and FYI

I have a v6 stock phone, no root, no cwm. Thought I would run through the ADB manual method of root to see what happens. I get to this point...
Code:
>adb devices (verifies you are connected)
>adb push rageagainstthecage-arm5.bin /data/local/temp/rage
(if the above command fails due to read-only, type 'adb usb' then 'adb root' to validate root status, then 'adb devices' again to verify connection)
>adb push su /data/local/temp/su
>adb shell chmod 777 /data/local/temp/rage
>adb shell ./data/local/temp/rage
When I try to do the SU because I get the $ I get Permissions denied.
I know that this method does not work but I wanted to see where it fails. It appears that they may have fixed the glitch that allowed the rage exploit to work.
I also tried cubes other way and it failed as well.
Code:
Open ADB shell
Your command prompt should be "$"
Run
kill `busybox pidof adbd`
Re-run ADB shell, your command prompt should change to "#"
Just thought I would toss this out there in case someone wanted to know...

Thanks for the heads up on this good info to know when I get my rev on Saturday
Sent from my SHIFTAO5P using XDA Premium App

Haxcid said:
I have a v6 stock phone, no root, no cwm. Thought I would run through the ADB manual method of root to see what happens. I get to this point...
Just thought I would toss this out there in case someone wanted to know...
Click to expand...
Click to collapse
Mm, I went through that last night, then downgraded to the V4 software as shown by the other post - still, none of it worked for me.

Pull your SDcard out when trying to root after the downgrade. Or format the SD card. It should work then.

[Q] Qemu local.prop root method bricked my KFHD

I used Qemu local.prop method to set /system/fonts folder as 766 and bricked my KFHD with the following steps:
adb shell
rm -r /data/local/tmp
ln -s /data/ /data/local/tmp
exit
adb reboot
adb shell
echo ‘ro.kernel.qemu=1′ > /data/local.prop
exit
adb reboot
adb shell mount -o remount,rw /system
adb push myfont.ttf /system/fonts
adb shell
cd /system/fonts
mv DroidSans.ttf DroidSans.ttf.bak
ln -s myfont.ttf DroidSans.ttf
chmod -R 06766 /system/fonts
rm /data/local.prop
exit
adb reboot
Click to expand...
Click to collapse
Now my KFHD does gets stucked in
"Your Kindle doesn't seem to be able to boot"
Is that because I changed the permission? Or is it because I did not reboot first after changing permission, and than delete local.prop? Which step was wrong? I am worried that doing that again would cause the same problem. I assume that the only way to recover from this would be to get into fastboot mode with factory cable. But I still want to keep fonts folder as writable.

When you edit files like this, with a device like a KFHD, odds are they deal with the framework-res.apk And if you mess with files that deal with framework-res.apk, your bound to get boot loop. But anyways, can you get adb? If not, fast boot might be your best friend. Cables are available that can boot to it, and if you see the system img. Files in the android development section, you can use fasboot to flash those. It's not the easiest solution, but it is something.
Sent from my Fire HD with root!

Rooting/unlocking Nexus One with broken power button using Linux terminal tools

I am attempting to get Cyanogenmod onto my Nexus One, but am running into far more problems than expected. The information on rooting Android devices seems heavily fragmented across the web and the tools unreliable. At least in my case, SuperOneClick has proven a complete misnomer. So I'd like to go back to basics - executing as many of the commands as possible from a Linux terminal to get the phone rooted/unlocked/whatever else has to happen to get Cyanogenmod installed. The two constraints I'm working with here are as follows:
1. The device is running Android 2.2.1 (I downgraded from 2.3.x using the PASSIMG method).
2. The power button on the device is broken, so any method which requires pressing/holding it is ruled out.
The problem I am having is that even after following Linux-centric guides, I get to the point of installing the SuperUser app followed by the ROM Manager app, but I'm never prompted to give ROM Manager superuser permissions and so can't flash the ClockworkMod recovery.
Below I describe the steps I've been taking so far, based on the "How To Root Nexus One Running Android 2.2.1 From Ubuntu Linux" guide (Google it, I can't post hyperlinks).
- Download/extract/move Nexus One Softroot files to same directory as adb
- From adb directory, execute the following commands:
sudo ./adb push psneuter /data/local/tmp/psneuter
sudo ./adb push busybox /data/local/tmp/busybox
sudo ./adb push su /data/local/tmp/su
sudo ./adb shell chmod 755 /data/local/tmp/psneuter
sudo ./adb shell chmod 755 /data/local/tmp/busybox
sudo ./adb shell chmod 755 /data/local/tmp/su
sudo ./adb shell cd /data/local/tmp ./psneuter
sudo ./adb shell
After executing sudo ./adb shell as above, I get the # prompt, which is purported to indicate that rooting was successful.
- Still following the guide, I then execute the commands which purportedly make root permanent:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /data/local/tmp
./busybox cp busybox /system/bin
chmod 4755 /system/bin/busybox
busybox cp su /system/bin
chmod 4755 /system/bin/su
exit
exit
- Again, still following the guide, I execute the commands which purportedly set the /system partition back to read-only:
sudo ./adb shell
su
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
exit
exit
- Now, I download the SuperUser app from the Android Market and open it to make sure it's running.
- Next, I download the ROM Manager app from Google Play (looks like it pulled a sneaky and upgraded from Android Market to Google Play here).
- I run ROM Manager and choose Flash ClockworkMod Recovery. I'm prompted to confirm the phone is a Google Nexus One and then ROM Manager runs for about 30 seconds (yellow program bar goes all the way) before spitting out An error occurred while attempting to run privileged commands!. And this is the point I am stuck at.
I should note that at no point am I prompted by the SuperUser app to give the ROM Manager app super user permissions. I don't restart the phone or do anything else throughout all of the steps I've described above, so I can't see any reason for root to have been lost at any point. In fact, if I execute the command sudo ./adb shell after all this, I still get the # prompt indicating root. And when I execute id afterwards, I get uid=0(root) gid=0(root) -- further confirmation of root. I really am stuck on this one. I've spent a lot of time digging through forum posts and online articles, but the signal to noise ratio is poor and I haven't been able to find anything that actually works. Can someone suggest where I am going wrong?

Programs might expect su to be in /system/xbin rather than /system/bin, which is probably your case.
Also, use SuperSU instead of Superuser.
Also, make sure the su you're using is matching the relevant control program - which means, downloading Superuser from the Play Store won't help, if it can't work with the binary you have. So download a complete ZIP from XDA with SuperSU.apk and su binary, and use those. The last version I used was 0.89 and it was on XDA just like I described above.

interesting problem with ez fix, get new phone. n1's are $100 on ebay, thats how i got mine.

Cant root L90 D410hn, stucked in commands

I tried this frist: http://forum.xda-developers.com/lg-l90/general/guide-root-l90-varients-updates-t2928364
but the command adb reboot --bnr_recovery just only reboot the device not to recovery and nothing happens
so I tried this http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
but after all the things, in the last command adb.exe push busybox /data/local/tmp/ && adb.exe push lg_root.sh /data/local/tmp && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp
just nothing happens, no root installed
also tried the one click http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
seems every things work but noone root gain
look the log, seems jump some things:
Code:
Phone found at COM3!
Rooting phone...
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
##
Done!
what should I do?
the driver is from these threads, 4.1.1.0
rom 5.0.2 V20c-SCA-XXX