I tried the perma temp root that eugene373 posted but my sensation 4g doesn't give me root access. It seems to fail at the exploit:
C:\sensation 4g\RW_Sensation>adb wait-for-device
C:\sensation 4g\RW_Sensation>adb push fre3vo /data/local/tmp
C:\sensation 4g\RW_Sensation>adb shell chmod 777 /data/local/tmp/fre3vo
C:\sensation 4g\RW_Sensation>adb shell /data/local/tmp/fre3vo
Locating access point...
The exploit has failed.
C:\sensation 4g\RW_Sensation>adb wait-for-device
C:\sensation 4g\RW_Sensation>adb shell sleep 1
C:\sensation 4g\RW_Sensation>adb remount
remount failed: Operation not permitted
C:\sensation 4g\RW_Sensation>adb shell mount -o rw,remount rootfs /
mount: Operation not permitted
C:\sensation 4g\RW_Sensation>adb shell mount -o remount,suid /dev/block/mmcblk0p23 /data
mount: Operation not permitted
C:\sensation 4g\RW_Sensation>adb shell mkdir /vendor/bin
mkdir failed for /vendor/bin, Read-only file system
C:\sensation 4g\RW_Sensation>adb shell chmod 4755 /system/bin/sh
Unable to chmod /system/bin/sh: Read-only file system
C:\sensation 4g\RW_Sensation>adb push ./sqlite3 /vendor/bin
C:\sensation 4g\RW_Sensation>adb push ./libext4_utils.so /system/lib
C:\sensation 4g\RW_Sensation>adb push ./libfuse.so /system/lib
C:\sensation 4g\RW_Sensation>adb shell chmod 655 /system/lib/libext4_utils.so
Unable to chmod /system/lib/libext4_utils.so: Read-only file system
C:\sensation 4g\RW_Sensation>adb shell chmod 000 /system/lib/libfuse.so
Unable to chmod /system/lib/libfuse.so: Read-only file system
C:\sensation 4g\RW_Sensation>adb push ./default.prop /default.prop
C:\sensation 4g\RW_Sensation>adb push ./init.rc /init.rc
C:\sensation 4g\RW_Sensation>adb push ./init.pyramid.rc /init.pyramid.rc
C:\sensation 4g\RW_Sensation>adb shell chmod 755 /default.prop
Unable to chmod /default.prop: Read-only file system
C:\sensation 4g\RW_Sensation>adb shell chmod 755 /init.rc
Unable to chmod /init.rc: Read-only file system
C:\sensation 4g\RW_Sensation>adb shell chmod 755 /init.pyramid.rc
Unable to chmod /init.pyramid.rc: Read-only file system
C:\sensation 4g\RW_Sensation>adb push ./fixit /vendor/bin
C:\sensation 4g\RW_Sensation>adb push ./su /sbin
C:\sensation 4g\RW_Sensation>adb push ./su /data/bin
C:\sensation 4g\RW_Sensation>adb push ./busybox /vendor/bin
C:\sensation 4g\RW_Sensation>adb shell chmod 4755 /sbin
Unable to chmod /sbin: Read-only file system
C:\sensation 4g\RW_Sensation>adb shell chmod 4755 /sbin/su
Unable to chmod /sbin/su: Permission denied
C:\sensation 4g\RW_Sensation>adb shell chmod 4755 /data/bin/su
Unable to chmod /data/bin/su: No such file or directory
C:\sensation 4g\RW_Sensation>adb shell chmod 4755 /vendor/bin/fixit
Unable to chmod /vendor/bin/fixit: No such file or directory
C:\sensation 4g\RW_Sensation>adb shell chmod 4755 /vendor/bin/busybox
Unable to chmod /vendor/bin/busybox: No such file or directory
C:\sensation 4g\RW_Sensation>adb shell chmod 755 /vendor/bin/sqlite3
Unable to chmod /vendor/bin/sqlite3: No such file or directory
C:\sensation 4g\RW_Sensation>adb shell busybox --install -s /vendor/bin
busybox: permission denied
C:\sensation 4g\RW_Sensation>adb shell rm -r /vendor/bin/ls
rm failed for /vendor/bin/ls, No such file or directory
C:\sensation 4g\RW_Sensation>adb shell rm -r /vendor/bin/reboot
rm failed for /vendor/bin/reboot, No such file or directory
C:\sensation 4g\RW_Sensation>adb shell rm -r /vendor/bin/chmod
rm failed for /vendor/bin/chmod, No such file or directory
C:\sensation 4g\RW_Sensation>adb shell rm -r /vendor/bin/chown
rm failed for /vendor/bin/chown, No such file or directory
C:\sensation 4g\RW_Sensation>adb install ./Superuser.apk
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\sensation 4g\RW_Sensation>adb install ./androidterm.apk
pkg: /data/local/tmp/androidterm.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\sensation 4g\RW_Sensation>adb wait-for-device
C:\sensation 4g\RW_Sensation>adb shell sync
C:\sensation 4g\RW_Sensation>pause
Press any key to continue . . .
Click to expand...
Click to collapse
I have the T-mobile USA sensation 4g with the updated 2.3.4. It also has all the htc updates as well as the google updates.
I don't want permanent root just temp root so any help would be greatly appreciated.
I think that method was rendered unusable by the 2.3.4 update.
Is there any temp root that can be done on 2.3.4 for T-mobile Sensation 4g? What about a permanent root?
slubberry said:
Is there any temp root that can be done on 2.3.4 for T-mobile Sensation 4g? What about a permanent root?
Click to expand...
Click to collapse
Not that we know of..The good news is that you may still be able to do a perm root that can still be removed if needed. (Youll need to flash your stock ROM again though).
Are you S-OFF?
Matt
No, I am s-on. I don't want to s-off the phone through HTC because it will void the warrantee and I want to be able to revert back to the original if I have a problem with the phone.
slubberry said:
No, I am s-on. I don't want to s-off the phone through HTC because it will void the warrantee and I want to be able to revert back to the original if I have a problem with the phone.
Click to expand...
Click to collapse
Revolutionary...
There is a sticky in dev section. Inside there is a guide how to get S-ON back. So don't worry
Swyped from my HTC Sensation
Related
Here is the commands I used:
cd\
cd androidsdk\tools
adb push try3.dat /data/local
adb shell chmod 0755 /data/local/try3
adb shell
/data/local/try3 /system/bin/sh
mount -o rw,remount /dev/st9 /system
chmod 04755 /system/bin/sh
cat /sdcard/su.dat > /system/bin/su1
cat /sdcard/su.dat > /system/bin/su
chmod 04755 /system/bin/su
su
cat /system/bin/playlogo > /system/bin/playlogo_real
/system/bin/chmod 0755 /system/bin/playlogo_real
echo “#!/system/bin/sh
/data/local/try3.dat /system/bin/sh
mount -o rw,remount /dev/st9 /system
chmod 04755 /system/bin/sh
cat /system/bin/su1 > /system/bin/su
chmod 04755 /system/bin/su
/system/bin/playlogo_real” > /system/bin/playlogo
exit
exit
exit
adb install Superuser.apk
adb shell reboot
It said Superuser.apk installed successful. When I tried to reboot it said permission denied.
Here is the CMD pasted. Please help me I have no idea what I am doing wrong.
C:\AndroidSDK>cd\
C:\>reboot
'reboot' is not recognized as an internal or external command,
operable program or batch file.
C:\>cd\
C:\>cd androidsdk\
C:\AndroidSDK>adb shell
error: device not found
C:\AndroidSDK>adb shell
error: device not found
C:\AndroidSDK>adb shell
$ su
su
su: permission denied
$ exit
exit
C:\AndroidSDK>adb devices
List of devices attached
SGH-T939 device
C:\AndroidSDK>adb shell
$ su.dat
su.dat
su.dat: permission denied
$ exit
exit
C:\AndroidSDK>adb shell
$ su
su
su: permission denied
$ su.dat
su.dat
su.dat: permission denied
$ exit
exit
Figured out how to temp root my friends nextbook and get titanium backup working. Basically i followed this thread
http://forum.xda-developers.com/showthread.php?t=1173690
Download the htc flyer 16/32gb file and use that one. After you run the Run_ME_fre3vo_Root.bat File go to terminal and type su then hit enter.
You will get the notice that terminal has been granted superuser permission and you will be all set. Download titanium backup and install it .But remember everytime you reboot you will have to run the .bat again.
Thanks to Eugene373 for creating this tool. And thanks to #Teamwin
Htc Evo 4g rooted s-off cyanogenmod 7
Htc Flyer 16gb wifi rooted s-off Flyhigh rom
If i helped in anyway feel free to hit the thanks button
Or just use z4root. That's what I did on my Next6 while dumping the stock image.
By chance could I get a copy of the Next7's stock image?
temp root
tried z4root, i had no luck with gingerbread.
temp root
here is the system dump for nextbook7p
http://www.multiupload.com/6BY8BVS5BJ
Ok i followed the steps on there but im kinda confused on hoqw you managed to get it to work. The next book 7p always shows as a mountable disk when connected to my computer. On the link it says u need to change it to charge only. I tried ignoring that because the nexbook 7p cant charge via usb. But when i click run_me_fr3vo_root the terminal opens and it says wait-for-devices and thats all. So would u kind giving a more detailed explanation? Id aporeciate it alot cause ive been wanting to root this thing foreverrrrr (3 months lol)
krisf29 said:
Figured out how to temp root my friends nextbook and get titanium backup working. Basically i followed this thread
http://forum.xda-developers.com/showthread.php?t=1173690
Click to expand...
Click to collapse
This method did not work with my NextBook 7:
Code:
C:\RW_HTC_Flyer(1)>adb wait-for-device
C:\RW_HTC_Flyer(1)>adb push fre3vo /data/local/tmp
3188 KB/s (9796 bytes in 0.003s)
C:\RW_HTC_Flyer(1)>adb shell chmod 777 /data/local/tmp/fre3vo
C:\RW_HTC_Flyer(1)>adb shell /data/local/tmp/fre3vo
fre3vo by #teamwin
Please wait...
This device either does not support the fre3vo exploit, or this
account lacks permission to access the required devices.
An error has occured.
C:\RW_HTC_Flyer(1)>adb wait-for-device
C:\RW_HTC_Flyer(1)>adb shell /data/local/tmp/fre3vo
fre3vo by #teamwin
Please wait...
This device either does not support the fre3vo exploit, or this
account lacks permission to access the required devices.
An error has occured.
C:\RW_HTC_Flyer(1)>adb wait-for-device
C:\RW_HTC_Flyer(1)>adb shell sleep 5
C:\RW_HTC_Flyer(1)>adb remount
remount failed: Operation not permitted
C:\RW_HTC_Flyer(1)>adb shell mount -o rw,remount rootfs /
mount: Operation not permitted
C:\RW_HTC_Flyer(1)>adb shell mount -o remount,suid /dev/block/mmcblk0p29 /data
mount: Operation not permitted
C:\RW_HTC_Flyer(1)>adb shell rm -r /vendor
rm failed for /vendor, Read-only file system
C:\RW_HTC_Flyer(1)>adb shell mkdir /system/vendor
mkdir failed for /system/vendor, Read-only file system
C:\RW_HTC_Flyer(1)>adb shell mkdir /system/vendor/bin
mkdir failed for /system/vendor/bin, No such file or directory
C:\RW_HTC_Flyer(1)>adb shell chmod 777 /system/vendor
Unable to chmod /system/vendor: No such file or directory
C:\RW_HTC_Flyer(1)>adb shell chmod 777 /system/vendor/bin
Unable to chmod /system/vendor/bin: No such file or directory
C:\RW_HTC_Flyer(1)>adb shell chmod 4755 /system/bin/sh
Unable to chmod /system/bin/sh: Read-only file system
C:\RW_HTC_Flyer(1)>adb push sqlite3 /system/vendor/bin
failed to copy 'sqlite3' to '/system/vendor/bin': No such file or directory
C:\RW_HTC_Flyer(1)>adb push libext4_utils.so /system/lib
failed to copy 'libext4_utils.so' to '/system/lib/libext4_utils.so': Read-only f
ile system
C:\RW_HTC_Flyer(1)>adb push libfuse.so /system/lib
failed to copy 'libfuse.so' to '/system/lib/libfuse.so': Read-only file system
C:\RW_HTC_Flyer(1)>adb shell chmod 655 /system/lib/libext4_utils.so
Unable to chmod /system/lib/libext4_utils.so: No such file or directory
C:\RW_HTC_Flyer(1)>adb shell chmod 000 /system/lib/libfuse.so
Unable to chmod /system/lib/libfuse.so: No such file or directory
C:\RW_HTC_Flyer(1)>adb push default.prop /default.prop
failed to copy 'default.prop' to '/default.prop': Read-only file system
C:\RW_HTC_Flyer(1)>adb push init.rc /init.rc
failed to copy 'init.rc' to '/init.rc': Read-only file system
C:\RW_HTC_Flyer(1)>adb push init.flyer.rc /init.flyer.rc
failed to copy 'init.flyer.rc' to '/init.flyer.rc': Read-only file system
C:\RW_HTC_Flyer(1)>adb shell chmod 755 /default.prop
Unable to chmod /default.prop: Read-only file system
C:\RW_HTC_Flyer(1)>adb shell chmod 755 /init.rc
Unable to chmod /init.rc: Read-only file system
C:\RW_HTC_Flyer(1)>adb shell chmod 755 /init.flyer.rc
Unable to chmod /init.flyer.rc: No such file or directory
C:\RW_HTC_Flyer(1)>adb push fixit /system/vendor/bin
failed to copy 'fixit' to '/system/vendor/bin': No such file or directory
C:\RW_HTC_Flyer(1)>adb push su /sbin
failed to copy 'su' to '/sbin/su': Permission denied
C:\RW_HTC_Flyer(1)>adb push su /system/vendor/bin
failed to copy 'su' to '/system/vendor/bin': No such file or directory
C:\RW_HTC_Flyer(1)>adb push busybox /system/vendor/bin
failed to copy 'busybox' to '/system/vendor/bin': No such file or directory
C:\RW_HTC_Flyer(1)>adb shell chmod 4755 /sbin
Unable to chmod /sbin: Read-only file system
C:\RW_HTC_Flyer(1)>adb shell chmod 4755 /sbin/su
Unable to chmod /sbin/su: Permission denied
C:\RW_HTC_Flyer(1)>adb shell chmod 4755 /system/vendor/bin/su
Unable to chmod /system/vendor/bin/su: No such file or directory
C:\RW_HTC_Flyer(1)>adb shell chmod 4755 /system/vendor/bin/fixit
Unable to chmod /system/vendor/bin/fixit: No such file or directory
C:\RW_HTC_Flyer(1)>adb shell chmod 4755 /system/vendor/bin/busybox
Unable to chmod /system/vendor/bin/busybox: No such file or directory
C:\RW_HTC_Flyer(1)>adb shell chmod 755 /system/vendor/bin/sqlite3
Unable to chmod /system/vendor/bin/sqlite3: No such file or directory
C:\RW_HTC_Flyer(1)>adb shell /system/vendor/bin/busybox --install -s /system/ven
dor/bin
/system/vendor/bin/busybox: not found
C:\RW_HTC_Flyer(1)>adb shell rm -r /system/vendor/bin/ls
rm failed for /system/vendor/bin/ls, No such file or directory
C:\RW_HTC_Flyer(1)>adb shell rm -r /system/vendor/bin/reboot
rm failed for /system/vendor/bin/reboot, No such file or directory
C:\RW_HTC_Flyer(1)>adb shell rm -r /system/vendor/bin/chmod
rm failed for /system/vendor/bin/chmod, No such file or directory
C:\RW_HTC_Flyer(1)>adb shell rm -r /system/vendor/bin/chown
rm failed for /system/vendor/bin/chown, No such file or directory
C:\RW_HTC_Flyer(1)>adb install Superuser.apk
5818 KB/s (196640 bytes in 0.033s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\RW_HTC_Flyer(1)>adb install androidterm.apk
6039 KB/s (92780 bytes in 0.015s)
pkg: /data/local/tmp/androidterm.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\RW_HTC_Flyer(1)>adb shell ln -s /system/vendor /vendor
link failed File exists
C:\RW_HTC_Flyer(1)>adb wait-for-device
C:\RW_HTC_Flyer(1)>adb shell sync
C:\RW_HTC_Flyer(1)>pause
Press any key to continue . . .
Same here. I tried all of the methods that I could come across on the web with no luck. You would think that it would be a way to root the original factory rom and just flash the device with the rooted rom. That seems to be the only way.
pls help me to get it rooted
i tried Zroot and gingerbreak without sucess
after i tried superoneclick
without sucess
i have a bextbook next8P
pls help
Hi,
I found a nice exploit for Xperia which works fine for Nexus one too ( the DooMLoRD exploit ).
I modified the script to flash the recovery without unlocking the bootloader, so you can flash the rom you like
The exploit works fine on Nexus one 2.3.4 GRJ22 with stock rom and locked bootloader, if you don't have a nexus one:
- remplace files/recovery.img with the right one!
- modify the line in script with the right system partition path.
here's the linux script to do the trick :
2shared.com/file/4uu5h2NH/zergRush_automated_Linux_roott.html
i'm sure someone will port it to windows
NB : backup data, and apps, when you flash a new rom, all data are deleted ( except SD Card).
Automatic installation using the script :
tar -xjvf zergRush_automated_Linux_root.tar.bz2
cd zergRush_automated_Linux_root/
chmod a+x runme-linux
sudo ./runme-linux
Manual installation :
tar -xjvf zergRush_automated_Linux_root.tar.bz2
cd zergRush_automated_Linux_root/
./files/adb kill-server
./files/adb wait-for-device
./files/adb shell rm -r /data/local/tmp
./files/adb shell mkdir /data/local/tmp
./files/adb push ./files/zergRush /data/local/tmp/
./files/adb shell chmod 755 /data/local/tmp/zergRush
./files/adb shell /data/local/tmp/zergRush
./files/adb wait-for-device
./files/adb push ./files/busybox /data/local/tmp
./files/adb shell chmod 755 /data/local/tmp/busybox
./files/adb shell /data/local/tmp/busybox mount -o remount,rw /system
./files/adb push files/busybox /system/xbin
./files/adb shell chown root.shell /system/xbin/busybox
./files/adb shell chmod 04755 /system/xbin/busybox
./files/adb shell /system/xbin/busybox --install -s /system/xbin
./files/adb shell rm -r /data/local/tmp/busybox
./files/adb push ./files/su /system/bin/su
./files/adb shell chown root.shell /system/bin/su
./files/adb shell chmod 06755 /system/bin/su
./files/adb shell rm /system/xbin/su
./files/adb shell ln -s /system/bin/su /system/bin/su
./files/adb push files/Superuser.apk /system/app/
./files/adb shell rm -r /data/local/tmp
./files/adb push files/flash_image /data/flash_image
./files/adb shell chmod 755 /data/flash_image
./files/adb push files/recovery.img /data/recovery.img
./files/adb shell /data/flash_image recovery /data/recovery.img
./files/adb shell rm /data/flash_image
./files/adb reboot recovery
In less than a minute, your phone will reboot to amonRA recovery, flash the rom you want, and Enjoy!
I recently watched a video on YouTube on how to root the HTC Amaze. I followed the directions and unlocked the bootloader successfully but when I ran the ZergRushTempRoot.bat to root it, I got the following:
C:\Zerg rush root>adb wait-for-device
C:\Zerg rush root>adb push zergRush /data/local/
1328 KB/s (21215 bytes in 0.015s)
C:\Zerg rush root>adb shell chmod 777 /data/local/zergRush
C:\Zerg rush root>adb shell rm /data/local/tmp/*sh
C:\Zerg rush root>adb shell /data/local/zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00017118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
C:\Zerg rush root>adb wait-for-device
C:\Zerg rush root>adb shell sleep 1
C:\Zerg rush root>adb remount
remount failed: Operation not permitted
C:\Zerg rush root>adb shell mount -o rw,remount rootfs /
mount: Operation not permitted
C:\Zerg rush root>adb shell mount -o remount,suid /dev/block/mmcblk0p29 /system
mount: Operation not permitted
C:\Zerg rush root>adb shell chmod 4755 /system/bin/sh
Unable to chmod /system/bin/sh: Read-only file system
C:\Zerg rush root>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Zerg rush root>adb push ./su /system/bin
failed to copy './su' to '/system/bin/su': Read-only file system
C:\Zerg rush root>adb push ./busybox /system/bin
failed to copy './busybox' to '/system/bin/busybox': Read-only file system
C:\Zerg rush root>adb shell chmod 4755 /system/bin
Unable to chmod /system/bin: Read-only file system
C:\Zerg rush root>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Zerg rush root>adb shell chmod 4755 /system/bin/su
Unable to chmod /system/bin/su: No such file or directory
C:\Zerg rush root>adb push ./Superuser.apk /system/app
failed to copy './Superuser.apk' to '/system/app/Superuser.apk': Read-only file
system
C:\Zerg rush root>adb install ./androidterm.apk
2904 KB/s (92780 bytes in 0.031s)
pkg: /data/local/tmp/androidterm.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\Zerg rush root>adb wait-for-device
C:\Zerg rush root>adb shell sync
C:\Zerg rush root>pause
Press any key to continue . . .
If anyone can help me get this phone rooted, I would appreciate it.
Thanks,
George
[email protected]
root htc amaze 4g
i am in canada. useing mobilicity on this phone. i am also facing same problem. i am also waiting for root. after i readable my indian language. thanks
anybody plz help me.
Hello,
Thank you for this post. I also have the exact same issue.
Similar to kapil1878, I am also on Mobilicity in Canada.
Same issue here! Amaze t-mobile.
rooting
having the same problem about rooting. t-mobile usa
remount fails
So, one thing at a time.
First off remount fails. Why? Lets look at the script. I've numbered the lines for reference:
1 :cd %:h
2 adb wait-for-device
3 adb push zergRush /data/local/
4 adb shell chmod 777 /data/local/zergRush
5 adb shell /data/local/zergRush
6 adb wait-for-device
7 adb shell sleep 1
8 adb remount
9 adb shell mount -r -w -o remount rootfs /
10 adb shell mount -o remount,suid /dev/block/mmcblk0p29 /system
11 adb shell chmod 4755 /system/bin/sh
12 adb push ./su /system/bin
13 adb push ./su /system/bin
14 adb push ./busybox /system/bin
15 adb shell chmod 4755 /system/bin
16 adb shell chmod 4755 /system/bin/su
17 adb shell chmod 4755 /system/bin/su
18 adb push ./Superuser.apk /system/app
19 adb install ./androidterm.apk
20 adb wait-for-device
21 adb shell sync
22 pause
Line 8 is what fails first, probably causing a chain reaction of failures. This is because there's a critical spot on the device we need to write to that we can't write to for some reason.
I executed:
adb devices
The above command provides the serial numbers of all connected Android devices. I needed this for the next command which was:
adb -s [put serial number here] shell
This gave me access to the command line on the device. Then I executed:
mount
The above command tells you what file systems are active and usable, i.e. file systems that are mounted and ready for action. I think "file system" in this case may be synonymous with partition.
Now... looking up the remount command in the reference material shows that it is supposed to (and this is cut from the manual) :
adb remount - remounts the /system partition on the device read-write
However the result from our mount command a minute ago shows this for the /system mount. Note that there's a bunch of crap I've cut out but we are only interested in /system for now, anyway:
rootfs / rootfs ro,relatime 0 0
.
.
.
/dev/block/mmcblk0p29 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
.
.
.
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
So... guessing based on my previous Unix experience, ro probably means that this partition is mounted read only. That means we have to find a way to remount it "rw". Problem is that I can't figure out what the command is. We already know remount doesn't work.
Here are some of my attempts:
$ mount -t ext4 -o rw,relatime,barrier=1,data=ordered /dev/block/mmcblk0p29 /system
mount -t ext4 -o rw,relatime,barrier=1,data=ordered /dev/block/mmcblk0p29 /system
mount: Operation not permitted
$ mount -t ext4 -o remount,rw,relatime,barrier=1,data=ordered /dev/block/mmcblk0p29 /system
mount -t ext4 -o remount,rw,relatime,barrier=1,data=ordered /dev/block/mmcblk0p29 /system
mount: Operation not permitted
Now, then. We don't have permissions require to execute remount and for mount we get the above. The only thing I can think of at this point is that I need to elevate the permissions of the user I am logged in as. Anybody know how to do that on Android? How do I know who I am logged in as? Is there more than one user even?
everyone should check out the thread below, Binary100100 does an excellent job in explaining how to root...
http://forum.xda-developers.com/showthread.php?t=1426179?referrerid=922386
check it out :
http://tabletrepublic.com/forum/ain...ance-root-guide-not-newbies-697.html#post6351
I have managed to root my Novo 7 advance.
Follow theese steps and you will be fine
I used ADB, you must follow it in this exact order
ADB root
ADB shell mount -o remount,rw /system
ADB push su-3.0.3.2-efghi-signed /system/xbin/su
ADB shell chown 0.0 /system/xbin/su
ADB shell chmod 04755 /system/xbin/su
ADB shell mount -o remount,ro /system
ADB install -r Superuser-3.0.7-efghi-signed.apk
ADB shell mount -o remount,rw /system
ADB push su-3.0.3.2-efghi-signed /bin/su
ADB shell chown 0.0 /bin/su
ADB shell chmod 04755 /bin/su
all files and apk you need can be downloaded from here :
http://www.mediafire.com/?bx0y51nqbu4iptj
This method works on other devices as well !
Working on fixing the Market, I will publish a guide as soon as I got it to work...
I tried this, but root access is denied. The SuperOneClick completes everything, but when I installed SetCPU & RootExplorer apps, they are denied root access. Have you tried with these apps as well ?
gurung_vishwas1 said:
I tried this, but root access is denied. The SuperOneClick completes everything, but when I installed SetCPU & RootExplorer apps, they are denied root access. Have you tried with these apps as well ?
Click to expand...
Click to collapse
Don't run SuperOneClick, type in the commands manually, and it'll work.
Possibly a typo in the commands above (?), this is what I used:
ADB root
ADB shell mount -o remount,rw /system
ADB push su-3.0.3.2-efghi-signed /system/xbin/su
ADB shell chown 0.0 /system/xbin/su
ADB shell chmod 04755 /system/xbin/su
ADB shell mount -o remount,ro /system
ADB install -r Superuser-3.0.7-efghi-signed.apk
ADB shell mount -o remount,rw /system
ADB push su-3.0.3.2-efghi-signed /system/bin/su
ADB shell chown 0.0 /system/bin/su
ADB shell chmod 04755 /system/bin/su
Big thanks, finally got my device rooted. (Novo7 Advanced2)