I keep trying all these codes and cant seem to get it to work.....anyone know like the exact steps and full code to put in cmd for "moto-fastboot"? Ive downloaded and extracted the img file for CWM recovery to my external sd as well and cant get that going....i think i just keep inputting the commands wrong or something i havent messed with this much yet....
help please? lol
From http://forum.xda-developers.com/showthread.php?t=1139303
This method worked for me
I don't know if I am the only one who realized there's su binary already in the build. Anyway, this is a shorter route to have root working on your phone. This only works with the HKTW 2.3.4 build! And this instruction have only be tested by me. So, do take precautionary measures.
DOWNLOAD: http://dl.dropbox.com/u/6418171/SuperUser.zip
INSTRUCTIONS:
1. Extract the zip to your internal storage (i.e. /sdcard)
2. Get into the phone shell i.e.
adb shell
3. Then, type and press enter:
su
4. Lastly, copy and paste these whole chunk to your phone shell and press enter:
mount -o remount,rw /dev/block/mmcblk0p12 /system && cp /sdcard/SuperUser/su /system/bin/su && chmod 6755 /system/bin/su && cp /sdcard/SuperUser/SuperUser.apk /system/app/SuperUser.apk && mv /system/xbin/su /system/xbin/dosu
If there's no error with the output, you should have root access on your phone now. Tada! Do report of this works for you!
try this
http://forum.xda-developers.com/showthread.php?t=1139303
extract that zip and put it in your internal sd card.
then type this in cmd
C:\Users\Your Name>cd C:\android-sdk-windows\tools
then type "adb shell"
then "su"
then copy and paste this
mount -o remount,rw /dev/block/mmcblk0p12 /system && cp /sdcard/SuperUser/su /system/bin/su && chmod 6755 /system/bin/su && cp /sdcard/SuperUser/SuperUser.apk /system/app/SuperUser.apk && mv /system/xbin/su /system/xbin/dosu
and then hit enter. sometimes it does not work, just keep trying make youre youre on usb connection "none" not mass storage or phone portal.
also make sure usb debugging is on. if you get any type of error, its probably that adb is not coming up in this case just do the afterupdate bat. but you should be fine. just so you know i had to try that method like 3 or 4 times before it work. but it does work. credit goes all to arctu.
After doing root above I followed instructions from
http://forum.xda-developers.com/showthread.php?t=1138541
to get CWM Recovery working
Thanks, this method didnt work for me but it did get me on the right track. I had to go to http://briefmobile.com/motorola-atrix-4g-root and follow the cmd instructions for adb and it worked like a charm
Thanks again!
mburlingame said:
From http://forum.xda-developers.com/showthread.php?t=1139303
This method worked for me
I don't know if I am the only one who realized there's su binary already in the build. Anyway, this is a shorter route to have root working on your phone. This only works with the HKTW 2.3.4 build! And this instruction have only be tested by me. So, do take precautionary measures.
DOWNLOAD: http://dl.dropbox.com/u/6418171/SuperUser.zip
INSTRUCTIONS:
1. Extract the zip to your internal storage (i.e. /sdcard)
2. Get into the phone shell i.e.
adb shell
3. Then, type and press enter:
su
4. Lastly, copy and paste these whole chunk to your phone shell and press enter:
mount -o remount,rw /dev/block/mmcblk0p12 /system && cp /sdcard/SuperUser/su /system/bin/su && chmod 6755 /system/bin/su && cp /sdcard/SuperUser/SuperUser.apk /system/app/SuperUser.apk && mv /system/xbin/su /system/xbin/dosu
If there's no error with the output, you should have root access on your phone now. Tada! Do report of this works for you!
Click to expand...
Click to collapse
Everytime i try this i get "error cannot load recovery-en-goapk.img"
mburlingame said:
After doing root above I followed instructions from
http://forum.xda-developers.com/showthread.php?t=1138541
to get CWM Recovery working
Click to expand...
Click to collapse
ShawnXVIII said:
Everytime i try this i get "error cannot load recovery-en-goapk.img"
Click to expand...
Click to collapse
Are you in the right folder?
Sent from my MB860 using Tapatalk
I ran beforeupdate.dat and afterupdate.dat to root mine.
Here is the root thread in the dev section. I was unable to get the OP's method to work in that thread but I did link the 2 .dat files I used to root.
http://forum.xda-developers.com/showthread.php?t=1139303
ShawnXVIII said:
I keep trying all these codes and cant seem to get it to work.....anyone know like the exact steps and full code to put in cmd for "moto-fastboot"? Ive downloaded and extracted the img file for CWM recovery to my external sd as well and cant get that going....i think i just keep inputting the commands wrong or something i havent messed with this much yet....
help please? lol
Click to expand...
Click to collapse
[ROOT]The FLASHABLE zip file for ROOTing Atrix 2.3.4 HKTW(12)
http://forum.xda-developers.com/showthread.php?t=1140110
Related
i'm totally new to this so please bare with me.
have a HTC HERO
model: T-mobile G2 Touch
Firmware 1.5
Baseband
63.18.55.06u_6.35.04.25
Kernal 2.6.27-a5504199
Buil 1.76.110.6 146733 cl#47214 release-keys
Software 1.0.0.A6288
i downloaded android-sdk_r04-windows.zip
& followed the SDK vid setup: http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
i've got my device attached & the serial No has come up
now after entering this command > adb push asroot2 /data/local/ > i get an error as listed below ? help please what have i done wrong .
C:\AndroidSDK\tools>adb push asroot2 /data/local/
cannot start 'asroot2' : No such file or directory
C:\AndroidSDK\tools>
C:\AndroidSDK\tools>adb push asroot2 /data/local/
cannot start 'asroot2' : No such file or directory
C:\AndroidSDK\tools>adb shell chmod 0755 /data/local/asroot2
Unable to chmod /data/local/asroot2: No such file or directory
C:\AndroidSDK\tools>adb shell
$ /data/local/asroot2 /system/bin/sh
/data/local/asroot2 /system/bin/sh
/data/local/asroot2: not found
$ mount -o remount,rw -t yaffs2 /dev/block/mtbblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount: Operation not permitted
$ cat sh > su
cat sh > su
cannot create su: read-only file system
$chmod 4775 su
chmod 4775 su
Unable to chmod su: No such file or directory
$
anyone with some help it 11:30PM here i'm hoping to get this done before i go to work @ 5AM
what your computer is trying to tell you is that it can not find the file "asroot2". make sure it is in the same directory where you try to execute the command, or give it an absolute path like this:
C:\AndroidSDK\tools>adb push c:\whatever\asroot2 /data/local/
kendong2 said:
what your computer is trying to tell you is that it can not find the file "asroot2". make sure it is in the same directory where you try to execute the command, or give it an absolute path like this:
C:\AndroidSDK\tools>adb push c:\whatever\asroot2 /data/local/
Click to expand...
Click to collapse
ok thanks
i'll have another go
mind telling us the result?
all done
after chmod 4775 su (then hit enter)
do i do anything else to save ? or just unplug the USB all done ?
kendong2 said:
mind telling us the result?
Click to expand...
Click to collapse
it helps if i do this
1. Download the following file and then unzip
it.
AsRoot2
2. Take the unzipped file and save it into the Tools folder of your AndroidSDK.
after chmod 4775 su (then hit enter)
do i do anything else to save ? or just unplug the USB all done ?
how to obtain asroot2
hi i was wondering how to get a hold to the asroot2 file so i can contiue the steps to root properly
lilfizz said:
hi i was wondering how to get a hold to the asroot2 file so i can contiue the steps to root properly
Click to expand...
Click to collapse
it amazes me every time: in two weeks it is 2010, and yet there are so many people out there not being able to use a search engine...
going through the entire 1.5 to 2.1 root tutorial to a tee, but once i get to the recovery image, this happens (following is an entire copy/paste of what I went through, incase i did something wrong before i hit the point)
Code:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Lemcott>cd C:\android-sdk-windows\tools
C:\android-sdk-windows\tools>adb shell mount -o rw,remount /dev/block/mtdblock3
/system
adb server is out of date. killing...
* daemon started successfully *
C:\android-sdk-windows\tools>adb shell mount -o rw,remount /dev/block/mtdblock3
/system
C:\android-sdk-windows\tools>adb push recovery.img /sdcard
1192 KB/s (3926016 bytes in 3.215s)
C:\android-sdk-windows\tools>adb push flash_image /system/bin/flash_image
448 KB/s (9640 bytes in 0.021s)
C:\android-sdk-windows\tools>adb shell flash_image recovery /sdcard/recovery.img
flash_image: permission denied
C:\android-sdk-windows\tools>
EDIT: I am a complete ass hat. nothing to see here, move a long. mods delete this if you please.
P.S. Everyone else: ALWAYS DOUBLE CHECK BEFORE POSTING FOR HELP. *ahem* now be on your way.
try programming thru fastboot. press call + vol down and select the fastboot option and use this command from the pc
fastboot flash recovery recovery.ing
Sent from my Evil Eris v1.1 using the XDA mobile application powered by Tapatalk
It looks like you forgot the step where you modify the flash_image's permissions
Code:
adb shell chmod 755 /system/bin/flash_image
I had the same thing but I just kept reentering
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
and after maybe 4 iterations it worked.
I have a very simular problem:
(moto droid with android 2.1)
$su
su
Permission denied
Click to expand...
Click to collapse
I have try to use chmod the file but it said permission denied on chmod... please help T_T
note this is rooted, of course, when i'm in the phone type su, it'll pop up ask for me to allow or not, allowed, everything seems fine, but when i try to modify files in /system/etc/wifi (trying to make it work for ad hoc) it said permission denied....(even in su???) I tried in adb and it's the same, very very frustrating, any help is appreciated, Thanks.
edit: here's what it looks like using chmod...
>adb shell chmod 755 /system
unable to chmod /system: Read-only file system
>
Click to expand...
Click to collapse
penthoy said:
I have a very simular problem:
(moto droid with android 2.1)
I have try to use chmod the file but it said permission denied on chmod... please help T_T
note this is rooted, of course, when i'm in the phone type su, it'll pop up ask for me to allow or not, allowed, everything seems fine, but when i try to modify files in /system/etc/wifi (trying to make it work for ad hoc) it said permission denied....(even in su???) I tried in adb and it's the same, very very frustrating, any help is appreciated, Thanks.
edit: here's what it looks like using chmod...
Click to expand...
Click to collapse
make it read/write
penthoy said:
I have a very simular problem:
(moto droid with android 2.1)
I have try to use chmod the file but it said permission denied on chmod... please help T_T
note this is rooted, of course, when i'm in the phone type su, it'll pop up ask for me to allow or not, allowed, everything seems fine, but when i try to modify files in /system/etc/wifi (trying to make it work for ad hoc) it said permission denied....(even in su???) I tried in adb and it's the same, very very frustrating, any help is appreciated, Thanks.
edit: here's what it looks like using chmod...
Click to expand...
Click to collapse
I wouldn't try to flash anything you find here to a Moto Droid.
This is for the HTC Droid Eris.
Otherwise, and if I'm misunderstanding you, good luck with your problem.
archmagus said:
It looks like you forgot the step where you modify the flash_image's permissions
Code:
adb shell chmod 755 /system/bin/flash_image
Click to expand...
Click to collapse
I've been bashing my head in ALL day trying to get past this and finally found this thread! This worked perfectly!
theboo7 said:
make it read/write
Click to expand...
Click to collapse
How should i make is read/write?????
i cant get it to work at all.. need help plz.
Hello Guys
why cant i mount that **** together, i have the root permission, but also i dont..somehow
Code:
Microsoft Windows [version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. Alle rettigheder forbeholdes.
C:\Users\Rasmus H. G. Johnsen>d:
D:\>cd android\tools
D:\android\tools>adb devices
List of devices attached
HT9B7LG00092 device
D:\android\tools>adb shell mount -o rw,remount /dev/block/mtdbloc3 /system
mount: Operation not permitted
D:\android\tools>adb shell
$ ls
ls
sqlite_stmt_journals
cache
sdcard
etc
system
sys
sbin
proc
logo.rle
init.rc
init.goldfish.rc
init.bahamas.rc
init
default.prop
data
root
dev
$ exit
exit
Also if I go on and try to do this:
Code:
D:\android\tools>adb push flash_image /system/bin
failed to copy 'flash_image' to '/system/bin/flash_image': Read-only file system
I know that the flash_image fil and my recovery.img file is in this library and also on my sdcard, but I cant push the gotdamn flas_image file in the /system/bin catalog.
Can some one please help me ?
PS. I have the USB-debugging turned ON.
How do you know that you have root? Or, how did you gain root?
doogald said:
How do you know that you have root? Or, how did you gain root?
Click to expand...
Click to collapse
I have the app called androot from google market, ang i have run it to get root.
wfdi said:
I have the app called androot from google market, ang i have run it to get root.
Click to expand...
Click to collapse
I'm not aware of that app, and cannot find it in the market myself (do you have a link?)
However, one way to check for sure if you truly have root is run the adb command adb shell and, when you get a prompt, type the command "su". If it returns with a "#" prompt (rather than the "$" prompt that you are seeing), then you have root on the phone.
Most people these days root with either jcase's 1click root for eris: https://market.android.com/details?id=net.andirc.erisrooter or they use the procedure here: http://androidforums.com/eris-all-things-root/127861-universal-eris-root-dummies.html
You may be able to use the steps here as well, since you seem pretty comfortable with adb and have that working already: http://androidforums.com/eris-all-things-root/125436-detailed-leak-root-tutorial.html
Guys new I found another solution (tested on u8150)
First make sure that you are rooted first.
Open adb shell
Type in su.
Remount the system partition as read write.
Change the owner of system from root to system via chown root system
the exit the shell and push flash_image to system/
also push clockworkmodrecover.img into the system partion dont forget the last /.
then exit.
use a file manager, I used rootbrowser.apk without a memory card and installed recovery.
with rootbrowser copy flash_image to the bin directory.
don't forget to change the owner back to root to the system partition after you finish with rootexplorer or whatever u use even adb can work.
then the rest follows.
The above works only if your'e rooted and have adb.
Goodluck
haha am a genius Installing ROM +Recover without sdcard on u8150
all you have to do is:-
1. Make sure u have installed clockwork mode recovery on your device and have su binary.
2. Open adb with the device normally on.
3. Remount the data partition as read write using mount remount in adb .
4. use adb and push the cynogenmode.zip or any rom that fits into the data partition using
adb push romname.zip /data/
5. Reboot into clockworkmod recovery using the various options available.
6. This is what to do if you don't have a sdcard.
open adb with phone connected and run
adb shell
mount /data /sdcard
then go back to the main recovery menu and wipe dalvik cache only
then choose update from sdcard
flash your rom and tadaaa.
your'e done.
NB:CAUTION MAKE SURE TO FLASH A ROM THAT DOES NOT WRITE INTO THE DATA PARTION
THIS CAN BE DONE BY LOOKING FOR A FILE CALL UPDATE SCRIPT IN THE zip OF THE ROM U WANT TO INSTALL
Am going to make a post about this later.
Goodluck
Lol, 3 and a half year break between responses.
The problem with flash_image & dump_image is that it doesn't work on devices devices which use emmc (recent phones)and have
mmcblk0
and cat /proc/mtd won't work here either.
This means that you have to use dd to write to this devices.
I wonder how guys determine the partitions to use on such devices, and someone should hint as to what is going on since it seems manufacturers seriously don't want people to exploit their devices.
All credit goes to the orig guy who made the d2 exploit
If you feel the need to donate money then he deserves it [email protected]
I made an easier to follow tutorial over here with pics. Sorry but I am tired of going back and forth so just go there if you are having problems. If you can follow simple adb commands just follow the directions below
Download and Install Samsung Drivers
64bit:
http://www.wikifilez.com/root files/epic4g/usb_drivers_GalaxyS_x64.zip
32bit:
http://www.wikifilez.com/root files/epic4g/SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe
1 Click Root Method
http://forum.androidcentral.com/fascinate-roms-hacks/33899-how-root.html
Manual Method
cd C:\android-sdk\tools
adb push C:\fascinate\su /sdcard/su
adb push C:\fascinate\rage.bin /data/local/tmp/rage.bin
adb push C:\fascinate\busybox /sdcard/busybox
adb shell
cd /data/local/tmp
chmod 0755 rage.bin
./rage.bin
wait....
when it brings you back to your original shell in windows then follow these commands
adb shell (you should see # this time instead of $ this is exactly what we want)
mount -t rfs -o remount,rw /dev/block/stl9 /system
cd /system/xbin
cat /sdcard/su > su
cat /sdcard/busybox > busybox
chmod 4755 su
chmod 4755 busybox
exit
adb install C:\fascinate\Superuser.apk
This is permanent.
I just updated the files here with the latest su / superuser.apk / busybox
Also check out my tutorial to fix the memory/lag issues for this phone
http://forum.xda-developers.com/showthread.php?p=8086738#post8086738
Dirrk said:
All credit goes to the orig guy who made the d2 exploit
I feel naked without my droid lol this phone is so light
adb push su /sdcard/su
adb push rage.bin /data/local/tmp/rage.bin
adb push busybox /sdcard/busybox
adb shell
cd /data/local/tmp
chmod 0755 rage.bin
./rage.bin
wait....
when it brings you back to your original shell or windows cmd promt
adb shell
mount -t rfs -o remount,rw /dev/block/stl9 /system
cd /system/xbin
cat /sdcard/su > .
cat /scard/busybox > .
chmod 4755 su
chmod 4755 busybox
exit
adb install Superuser.apk
Please let me know if I posted something wrong.
Click to expand...
Click to collapse
does it stick after reboot?
Its supposed to be a temporary root so i doubt it will.
This works on any android phone up to 2.2. I have confirmed this works on my epic, so th same sould work here.
Sent from my SPH-D700 using XDA App
see below.
confirmed root.
Had to use Superuser.apk 2.3.6.1 and the su binary in the package, but the rest worked.. except for that cat command? Why would you cat binary files instead of copying them? (not complaining, just curious). I just adb pushed them to /system/xbin, and adb shell chmod'd them.
You also have a typo near the end "scard" instead of "sdcard".
You can also use mv or cp. I just happen to use cat because I used it the other day rooting my friends stock 2.2 droid. Which required me to use cat.
And yes this is permanent
Cool, i tried using rm -rf to get rid of a directory I created accidentally, and was getting some syntax errors, so I wasn't sure how compatibile the command line on android was to linux.
Glad it's pretty close. Being very familiar with linux makes this pretty easy to understand. Day 1 with an android device was pretty darn fun. I think I'm glad I went this direction.
I just followed this and used the same files I had from my Droid 2 (just updated the Superuser.apk from this sites thread for it) and works perfectly. Rebooted phone did "adb shell" and "su" and still have root, so it is permanent
side note: steps say "/system/xbin" and assume you meant "/system/bin" like Droid 2 was. That's where I put them and it worked.
cliffr39 said:
I just followed this and used the same files I had from my Droid 2 (just updated the Superuser.apk from this sites thread for it) and works perfectly. Rebooted phone did "adb shell" and "su" and still have root, so it is permanent
side note: steps say "/system/xbin" and assume you meant "/system/bin" like Droid 2 was. That's where I put them and it worked.
Click to expand...
Click to collapse
It works either way, both are executable system folders. Glad you it worked for you, hopefully we can get some roms cooking soon and play catch up to the other galaxy s phones
doesnt work for me, i get an error device not found
ive type adb devices - device not found. usb debugging on, usb conneced on port 5037
xirnibor said:
doesnt work for me, i get an error device not found
ive type adb devices - device not found. usb debugging on, usb conneced on port 5037
Click to expand...
Click to collapse
Your USB mode might be set wrong. Flip it to whatever it's not at, and try again.
i forgot this laptop didnt have the updated usb drivers from android sdk, downloading then will try again. i have tried so far with the sdcard mounted and unmounted, while in usb debugging mode. will post after updates
How long do you actually have to wait after the execting the rage.bin file?
itznfb said:
How long do you actually have to wait after the execting the rage.bin file?
Click to expand...
Click to collapse
I dunno, ~20-30 seconds? Assuming sound is enabled you should hear the same USB device connected/disconnected sounds.
If you want to be 100% sure just wait like 90 seconds. I'm pretty sure it killed my shell though, so if it does that, you're good to go.
ok, adb recognizes the device *see below, however when i type adb push su /sdcard/su i get cannot stat 'su': no such file or directory. ?
C:\downloads\android\android\tools>adb devices
List of devices attached
I500a2d0087a device
namebrandon said:
I dunno, ~20-30 seconds? Assuming sound is enabled you should hear the same USB device connected/disconnected sounds.
If you want to be 100% sure just wait like 90 seconds. I'm pretty sure it killed my shell though, so if it does that, you're good to go.
Click to expand...
Click to collapse
ok... running the rage.bin locked up my device twice but on the third try it worked. another fascinate rooted
xirnibor said:
ok, adb recognizes the device *see below, however when i type adb push su /sdcard/su i get cannot stat 'su': no such file or directory. ?
C:\downloads\android\android\tools>adb devices
List of devices attached
I500a2d0087a device
Click to expand...
Click to collapse
su is a file (for our purposes right here, anyway). Unless you explicity specify its path, it needs to be in the same directory you're running the adb command from.
If you installed the Android SDK per guidelines, adb should be in your PATH environment variable, and you should be able to execute it from any directory. If you didn't do that, then for the sake of simplicity, copy all the files referenced in the original steps to your working directory. From your post above, it appears that is c:\downloads\android\android\tools\
I got stuck at cat /sdcard/su > . Is that supposed to be > .? It won't let me enter that...There's not something else that's supposed to be there?
EDIT: I get the same error faspalma
I'm stuck at that point too. cat /sdcard/su > . returns "cannot create .: is a directory"
Okay, we discovered that having the Webtop over HDMI breaks the OTA update.
So to update you're going to have to undo that mod, and possibly any others.
If you backed up your original files great, go restore them, clear the dalvik-cache and you're fine.
Otherwise, use the attached files and these steps to recover:
Credit: _unknown for the original posted instructions I'm using as a template
Please let me know if there are any adjustments that need to be made to the code, as I'm pulling this from memory and had stored the backups on my phone and was restoring from there.
Requirements:
Be rooted
Be able to work with adb
First, unpack the attached zip-file.
Go into the correct directory for your version.
Now run (in a terminal)
Code:
# I use /data/tmp as the storage location, you can also use /sdcard/
adb push DockService.apk /data/tmp
adb push PortalApp.apk /data/tmp
adb push DockService.odex /data/tmp
adb push PortalApp.odex /data/tmp
adb shell
# you are now in the phone shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
# you could mv these files to backups if you intend on doing the mod
# again after the update
rm /system/app/DockService.*
rm /system/app/PortalApp.*
rm /data/dalvik-cache/*DockService* /data/dalvik-cache/*PortalApp*
# move the files from /data/tmp to /system/app
mv /data/tmp/DockService.* /system/app/
mv /data/tmp/PortalApp.* /system/app/
reboot
NOTE: This zip will not in any way help you to obtain root! You must be rooted prior to attempting to apply this patch, or it will not work!
pksublime said:
Okay, we discovered that having the Webtop over HDMI breaks the OTA update.
So to update you're going to have to undo that mod, and possibly any others.
If you backed up your original files great, go restore them, clear the dalvik-cache and you're fine.
Otherwise, use the attached files and these steps to recover:
Credit: _unknown for the original posted instructions I'm using as a template
Please let me know if there are any adjustments that need to be made to the code, as I'm pulling this from memory and had stored the backups on my phone and was restoring from there.
Requirements:
Be rooted
Be able to work with adb
First, unpack the attached zip-file.
Go into the correct directory for your version.
Now run (in a terminal)
Code:
# I use /data/tmp as the storage location, you can also use /sdcard/
adb push DockService.apk /data/tmp
adb push PortalApp.apk /data/tmp
adb push DockService.odex /data/tmp
adb push PortalApp.odex /data/tmp
adb shell
# you are now in the phone shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
# you could mv these files to backups if you intend on doing the mod
# again after the update
rm /system/app/DockService.*
rm /system/app/PortalApp.*
rm /data/dalvik-cache/*DockService* /data/dalvik-cache/*PortalApp*
# move the files from /data/tmp to /system/app
mv /data/tmp/DockService.* /system/app/
mv /data/tmp/PortalApp.* /system/app/
reboot
NOTE: This zip will not in any way help you to obtain root! You must be rooted prior to attempting to apply this patch, or it will not work!
Click to expand...
Click to collapse
mv /data/tmp/PortalApp.* /system/app/
# mv /data/tmp/DockService.* /system/app/
mv /data/tmp/DockService.* /system/app/
failed on '/data/tmp/DockService.apk' - Cross-device lin
# mv /data/tmp/PortalApp.* /system/app/
mv /data/tmp/PortalApp.* /system/app/
failed on '/data/tmp/PortalApp.apk' - Cross-device link
Okay working on it...
try using cp instead of mv
Thank you. Will do this tonight
cp worked instead of mv
was able to update, thankyou.
lcpl said:
cp worked instead of mv
Click to expand...
Click to collapse
thanks, i updated the instructions
at least the important part was getting the files up for people, most can figure it out from there
Has anyone that has updated to the newer OTA version been able to re-hack the Webtop / HDMI output using the original method?
Thanks!
alohajeff said:
Has anyone that has updated to the newer OTA version been able to re-hack the Webtop / HDMI output using the original method?
Thanks!
Click to expand...
Click to collapse
You rave to re-root after the update, but yeah, it's the same thing.
Haven't got that far yet, I'm just starting.
Give me a bit and I'll tell you how it went.
Update 1:
Installed the update with out a hitch, save for a line of code
"rm /data/dalvik-cache/*DockService* /data/dalvik-cache/*PortalApp*"
I had to change to
"rm /data/dalvik-cache/*.*"
The dalvik chache is rebuilt at the next reboot, so there isn't much harm wiping the whole thing.
And Yeah, i had to change that the "mv" to"cp"
Update 2:
Rooted just fine using :/showthread.php?t=1217416
Update 3:
Followed : /showthread.php?t=1199443
But as of again, I changed
"rm /data/dalvik-cache/*DockService* /data/dalvik-cache/*PortalApp*"
to
"rm /data/dalvik-cache/*.*"
and
"mv" to"cp"
Works just as well as before. Even with 9/12's update
I had some trouble before, but It looks like I just had to re apply the hack one again. It's all good now. Dockless webtop on the latest OTA.
It's not working for me for the 10/12 update. Any ideas? Do the odex files have to be renamed to .bak?
Airwolf79 said:
It's not working for me for the 10/12 update. Any ideas? Do the odex files have to be renamed to .bak?
Click to expand...
Click to collapse
Yes.
Sent from my MB855 using Tapatalk
John Kotches said:
Yes.
Sent from my MB855 using Tapatalk
Click to expand...
Click to collapse
So what is the easiest way to go about this? Do I have to rename them before I push, or once they're installed?
Hi all, i added some files into the system directory of my kindle fire hdx 7'.. when i restarted it is stuck in a boot loop on the animated Kindle Fire boot screen, i can ADB onto it, and i attempted to remove the files, but "ADB su" isn't working for me, and I'm unable to access the system directory over ADB... and i don't have custom recovery.
Any ideas on this one? is there a way of restoring the Kindle?
Thanks
osmorgan said:
Hi all, i added some files into the system directory of my kindle fire hdx 7'.. when i restarted it is stuck in a boot loop on the animated Kindle Fire boot screen, i can ADB onto it, and i attempted to remove the files, but "ADB su" isn't working for me, and I'm unable to access the system directory over ADB... and i don't have custom recovery.
Any ideas on this one? is there a way of restoring the Kindle?
Thanks
Click to expand...
Click to collapse
what you get on
Code:
adb shell
su
?
thanks for the reply. when i
adb shell
su
Click to expand...
Click to collapse
it returns to 1:[email protected] where it should show [email protected] any ideas?
osmorgan said:
thanks for the reply. when i
it returns to 1:[email protected] where it should show [email protected] any ideas?
Click to expand...
Click to collapse
after that use
Code:
mount -o rw,remount /system
if you wil get permission denied you need to do hard reset from recovery and try again
after that you could change files in /system
great, i will try this later.. any guides on doing a hard reset?? keeping in mind that i don't have custom recovery..
thanks again.
osmorgan said:
great, i will try this later.. any guides on doing a hard reset?? keeping in mind that i don't have custom recovery..
thanks again.
Click to expand...
Click to collapse
you could get into stock recovery by holding power+volume up
all of this suggesting that you are at 4.5.2 and rooted
for 3.2.X hard reset will delete su - file
You're a star. Thanks. I'll get onto this after work.
ONYXis said:
you could get into stock recovery by holding power+volume up
all of this suggesting that you are at 4.5.2 and rooted
for 3.2.X hard reset will delete su - file
Click to expand...
Click to collapse
No luck :/ was unable to mount, and hard reset via recovery still results in boot loop :/ any other ideas?
Could you post output?
and pls what is your firmware and root method?
Seems no way to recover(sorry
How do I provide the output? I was 4.5.2 and rooted with CVE
copy-paste output from cmd
like:
Code:
adb shell
su
....
ahh i see what you mean.. ive run s uagian after factory reset and its now giving me the root prompt! great! im just about to follow this guys steps
http://forum.xda-developers.com/showthread.php?t=2793253
thanks for your help.. i may be back.
any idea if this method works with stock recovery?
ONYXis said:
copy-paste output from cmd
like:
Code:
adb shell
su
....
Click to expand...
Click to collapse
nope.. that didnt work for me.. do you know how i can push a deb to reflash?
Pls post output to see that exactly doesn't work.
to use that manual you need to use 4.5.3 bin btw
I see, I was having permissions errors when pushing the file to the sdcard, I had mounted the data partition. I am unable to write anything as shell user, but fine as root. Any ideas?
Thanks
adb shell
[email protected]:/ $ su
[email protected]:/ # mount -o rw,remount /cache
[email protected]:/ # mkdir /cache/recovery
mkdir failed for /cache/recovery, File exists
[email protected]:/ # echo install /cache/kindleupdate.bin > /cache/recovery/openrecoveryscript
[email protected]:/ # chmod 0777 /cache/recovery/openrecoveryscript
[email protected]:/ # exit
[email protected]:/ $ exit
Mac-miniownloads $ adb push update-kindle-13.4.5.3_user_453011120.bin /cache/kindleupdate.bin
failed to copy 'update-kindle-13.4.5.3_user_453011120.bin' to '/cache/kindleupdate.bin': Permission denied
What do you think?
ONYXis said:
what you get on
Code:
adb shell
su
?
Click to expand...
Click to collapse
ONYXis said:
Pls post output to see that exactly doesn't work.
to use that manual you need to use 4.5.3 bin btw
Click to expand...
Click to collapse
osmorgan said:
Mac-miniownloads $ adb push update-kindle-13.4.5.3_user_453011120.bin /cache/kindleupdate.bin
failed to copy 'update-kindle-13.4.5.3_user_453011120.bin' to '/cache/kindleupdate.bin': Permission denied
What do you think?
Click to expand...
Click to collapse
You cant do this at that way
you need :
Code:
adb push update-kindle-13.4.5.3_user_453011120.bin /sdcard/update.zip
adb shell
su
mount -o remount,rw /cache
cd /sdcard
cp update.zip /cache
chmod 777 /cache
chmod 777 /cache/recovery
cd /cache/recovery
echo "--update_package=/cache/update.zip" > command
exit
exit
adb reboot recovery
thank you but i still get permissions issues -
failed to copy 'update-kindle-13.4.5.3_user_453011120.bin' to '/sdcard/update.zip': Permission denied
ONYXis said:
You cant do this at that way
you need :
Code:
adb push update-kindle-13.4.5.3_user_453011120.bin /sdcard/update.zip
adb shell
su
mount -o remount,rw /cache
cd /sdcard
cp update.zip /cache
chmod 777 /cache
chmod 777 /cache/recovery
cd /cache/recovery
echo "--update_package=/cache/update.zip" > command
exit
exit
adb reboot recovery
Click to expand...
Click to collapse
osmorgan said:
thank you but i still get permissions issues -
failed to copy 'update-kindle-13.4.5.3_user_453011120.bin' to '/sdcard/update.zip': Permission denied
Click to expand...
Click to collapse
Hmm....Strange. Are you see Fire as mtp device on you Pc (for Mac you need https://www.android.com/filetransfer/)?
If "yes" - try to copy update.zip manual into Fire's internal storage.