Database Info

Question about rooting and flashing recovery image..

Just curious, what happens if I follow the rooting steps in the other thread but only do this:
adb push /directory_you_placed_asroot2/asroot2 /data/local/
adb shell
chmod 0755 /data/local/asroot2
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
At this point, what state is the phone in? Do I have full root access to the file system? What are the issues/concerns if I don't proceed with flashing the recovery image. Just trying to understand the process and what each step is for. I understand the part above but can't understand why you have to flash a recovery image and can't just use the phone after root is achieved.
Thanks in advance. FYI...all I want to do with root access is delete some system files, nothing more.

mobilehavoc said:
Just curious, what happens if I follow the rooting steps in the other thread but only do this:
adb push /directory_you_placed_asroot2/asroot2 /data/local/
adb shell
chmod 0755 /data/local/asroot2
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
At this point, what state is the phone in? Do I have full root access to the file system? What are the issues/concerns if I don't proceed with flashing the recovery image. Just trying to understand the process and what each step is for. I understand the part above but can't understand why you have to flash a recovery image and can't just use the phone after root is achieved.
Thanks in advance. FYI...all I want to do with root access is delete some system files, nothing more.
Click to expand...
Click to collapse
You don't have to flash the recovery image. I believe from that code you would have root and can run programs that require root. However, you would be unable to flash a new rom or any other update.zip (which means no auto apps2sd), partition your sd card easily or backup your phone in case something goes wrong. I suppose you are probably just asking for the sake of asking and knowledge but this is why a recovery image is HIGHLY recommended.

chuckhriczko said:
You don't have to flash the recovery image. I believe from that code you would have root and can run programs that require root. However, you would be unable to flash a new rom or any other update.zip (which means no auto apps2sd), partition your sd card easily or backup your phone in case something goes wrong. I suppose you are probably just asking for the sake of asking and knowledge but this is why a recovery image is HIGHLY recommended.
Click to expand...
Click to collapse
thanks. So if I don't flash the recovery image, I can't update to cooked ROMs or do the stuff you suggested but will the phone otherwise function normal? i.e. I can update to a Sprint/HTC update, I can factory reset the phone (assuming that'll kill root), etc.? I may do the whole process with the recovery image later but don't need it right now.
I only need to do this as a stopgap until Sprint/HTC releases an update.

mobilehavoc said:
thanks. So if I don't flash the recovery image, I can't update to cooked ROMs or do the stuff you suggested but will the phone otherwise function normal? i.e. I can update to a Sprint/HTC update, I can factory reset the phone (assuming that'll kill root), etc.? I may do the whole process with the recovery image later but don't need it right now.
I only need to do this as a stopgap until Sprint/HTC releases an update.
Click to expand...
Click to collapse
Well, I wouldnt recommend doing a sprint update either. That will cause you to lose root most likely. The only way then to keep root is wait until we get a dump of the update and then cook a rom that includes root, in which case you would need to flash the recovery image. Updates usually fix the exploits we use to gain root.

chuckhriczko said:
Well, I wouldnt recommend doing a sprint update either. That will cause you to lose root most likely. The only way then to keep root is wait until we get a dump of the update and then cook a rom that includes root, in which case you would need to flash the recovery image. Updates usually fix the exploits we use to gain root.
Click to expand...
Click to collapse
What he said...but yes, at the steps you quoted, mobilehavoc, you are capable of root access (you don't actually have it until you run that "su" command ). That allows you to read and modify otherwise locked away files and tweak to your hearts content!

Ive rooted and played around some but very little and followed everyones instructions very closely ( thank you for teaching a newbie ). Now how do I go back to original state that I backed up ( think I did ).
When I press the power and volume down button I get to the droid on skateboard, then I press the Home for recovery. I get the screen with all the options and I go to nandroid v2.2 restore and press trackball. It says restore latest backup press home to confirm. I do that and get the following error
Error : run 'nandroid-mobile.sh restore' via console.
What does this mean? Do i have to be tethered to PC and run this command from cmd prompt?
I am now lost again, any help is appreciated

Grinder16 said:
Ive rooted and played around some but very little and followed everyones instructions very closely ( thank you for teaching a newbie ). Now how do I go back to original state that I backed up ( think I did ).
When I press the power and volume down button I get to the droid on skateboard, then I press the Home for recovery. I get the screen with all the options and I go to nandroid v2.2 restore and press trackball. It says restore latest backup press home to confirm. I do that and get the following error
Error : run 'nandroid-mobile.sh restore' via console.
What does this mean? Do i have to be tethered to PC and run this command from cmd prompt?
I am now lost again, any help is appreciated
Click to expand...
Click to collapse
Just to confirm since it wasn't mentioned, you did a Nandroid backup earlier right? can you confirm that there's a folder on your sdcard called "nandroid"?

thecodemonk said:
Just to confirm since it wasn't mentioned, you did a Nandroid backup earlier right? can you confirm that there's a folder on your sdcard called "nandroid"?
Click to expand...
Click to collapse
Dont see that folder - I guess that is not good. Any ideas?

Grinder16 said:
Dont see that folder - I guess that is not good. Any ideas?
Click to expand...
Click to collapse
You must do a backup BEFORE you can do a restore..

To clarify for everyone, here's a breakdown of the steps:
adb push /directory_you_placed_asroot2/asroot2 /data/local/
This copies the asroot2 program to the /data/local folder on your phone.
adb shell
This logs you into the phone. From here on out, you are no longer executing Windows commands from a DOS shell - you are actually executing Linux commands on the phone.
chmod 0755 /data/local/asroot2
This changes the permissions on the asroot2 program so that it can be executed.
/data/local/asroot2 /system/bin/sh
This actually runs the root exploit and creates a file called /system/bin/sh that we will later turn into su.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
This unmounts the /system partition and remounts it as writeable.
cd /system/bin
This puts you into the /system/bin folder.
cat sh > su
This creates the su program.
chmod 4755 su
This changes the persmissions on the su file to allow it to be executed.

theresthatguy said:
You must do a backup BEFORE you can do a restore..
Click to expand...
Click to collapse
I thought I had. What are the steps? I have a flash recovery image on my SD card. I have followed all instructions that I could find

Grinder16 said:
I thought I had. What are the steps? I have a flash recovery image on my SD card. I have followed all instructions that I could find
Click to expand...
Click to collapse
Boot to the recovery image then select "nandroid backup"

jonnythan said:
Boot to the recovery image then select "nandroid backup"
Click to expand...
Click to collapse
Can you provide those steps? Sorry but complete newbie here

"I get the screen with all the options and I go to nandroid v2.2 restore and press trackball. It says restore latest backup press home to confirm. I do that and get the following error"
Go there but select Backup instead of Restore.
Turn the phone off, hold the Home key, and turn it on. When you get to the screen with the green text select nandroid backup.

[DEV] Apps2SD and Darchstar-2.1 ROM

The focus of this thread is to sort out the Apps2SD issue in cyanogenmod-darch 2.1 ROM (like the title says). Please do not post here unless it relates to this issue.
That being said, here is where I was at in the original darchstar 2.1 thread:
watzone69 said:
Taken from the instructions darchstar gave in the first post of his thread...
Code:
adb remount
adb push e2fsck /system/bin
adb shell
cd /system/bin
chmod a+x e2fsck
a2sd
reboot
First, the "chmod a+x e2fsck" command doesn't work for me (EDIT: I discovered that it WILL work in recovery mode). I had to use "chmod 777 e2fsck". After entering "a2sd" it gets enabled. After rebooting, apps2SD is NOT enabled anymore. I realized this by doing this test:
Code:
adb shell
cd /data/app
pwd
If your apps2sd is enabled, you will get "/system/sd/app" returned to you.
If you get "/data/app" returned instead then apps2sd is NOT enabled!
Click to expand...
Click to collapse
Gbhil then replied...
gbhil said:
After you restart, can you re-enable a2sd by running a2sd from a terminal as root?
If so, do all your apps still appear and are they usable?
If the above is true, try adding this to the end of gumbo.sh
Code:
su -C a2sd
for a quick fix.
Start a thread (to keep things less cluttered) about it and I'll help you guys dig into the boot image and see why it's not sticking.
Click to expand...
Click to collapse
So, I rebooted and tried to run "a2sd" from the android terminal but it spits out a long string of errors:
Code:
--- Checking ext filesystems
e2fsck 1.41.6 (30-May-2009)
ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determining whether /dev/block/mmcblk0p2 is mounted.
/dev/block/mmcblk0p2: clean, 13/249856 files, 31387/499713 blocks
mount: permission denied. (are you root?)
chown: /system/sd: Read-only file system
chmod: /system/sd: Read-only file system
mkdir failed for /system/sd/app, Read-only file system
chown: /system/sd/app: No such file or directory
chmod: /system/sd/app: No such file or directory
cp: cannot create '/system/sd/app/android.tether.apk': No such file or directory
cp: cannot create '/system/sd/app/android.tether.usb.apk': No such file or directory
cp: cannot create '/system/sd/app/at.abraxas.mountusb.apk': No such file or directory...
(etc.)
...rm: cannot remove '/data/app/org.gmote.client.android.apk': Permission denied
rm: cannot remove '/data/app/org.hermit.substrate.apk': Permission denied
rm: cannot remove '/data/app/org.iplatform.android.apk': Permission denied
rm: cannot remove '/data/app/org.mikeyin.livewallpaper.apk': Permission denied
mkdir failed for /system/sd/app-private, Read-only file system
chown: /system/sd/app-private: No such file or directory
chmod: /system/sd/app-private: No such file or directory
cp: can't open '/data/app-private/com.android.aldiko.apk': Permission denied
cp: can't open '/data/app-private/com.protocol.x.su.fbs.apk': Permission denied
cp: can't open '/data/app-private/com.rerware.android.MyBackupPro.apk': Permission denied
rm: cannot remove '/data/app-private/com.android.aldiko.apk': Permission denied
rm: cannot remove '/data/app-private/com.protocol.x.su.fbs.apk': Permission denied
rm: cannot remove '/data/app-private/com.rerware.android.MyBackupPro.apk': Permission denied
ln: /data/app/app: Permission denied
ln: /data/app-private/app-private: Permission denied
+++ Apps-to-SD successfully enabled
So, there is no "app" or "app-private" in the "system/sd". Is a2sd supposed to generate those directories or are they supposed to be there before hand?
Anyway, the result is that I lose all of my shortcuts to the apps and market shows them as not installed even though they are.
BTW, I am not a dev or even that great at code or linux but I can usually pick stuff up fairly quickly. Just want to help fix this!
EDIT: The only thing I have found to work is to flash this kernel:
http://forum.xda-developers.com/showpost.php?p=5712377&postcount=1406
However, some people get stuck in a boot loop after flashing this.

Running into the same issues as Watzone so I can confirm that he is doing it correctly. =P

Here are all of the related commands that have been suggested whenever the question of apps2sd has come up in the darchstar 2.1 thread.
Code:
adb remount
adb shell
mkdir /system/sd
Code:
adb remount
adb shell
busybox --install /system/xbin
a2sd
Code:
cd C:\android-sdk-windows\tools
adb remount
adb shell
chown system.system /data/app
chmod 0771 /data/app
For the next command, boot into recovery and do the following:
Code:
adb shell
mount /system
exit
adb push e2fsck /system/bin
adb shell
cd /system/bin
chmod 777 e2fsck
Now, boot normally and go back to your CMD prompt...
Code:
adb remount
adb shell
a2sd
EDIT: In other threads I have seen the command...
Code:
apps2sd on
...used to enable apps2sd.
Doing all of these WILL allow the final "a2sd" command to enable (testing with the "pwd" command) but it all goes KAPUT after a reboot.

why it's not being enabled at boot time is because the init.rc isn't calling /system/etc/init.d/04apps2sd . I'll be sure that we fix that in my next release

And there you go.
It works here, but now I know why. I'm still using an old version of the boot image that looks for /system/bin/a2sd to load it, and an older version of the ROM. No sense in me to keep flashing fixes until I'm done tweaking the kernel. When darch says the kernel is good, then I'll catch up lol.
We might as well use this thread to learn to play with the boot image though, that is if you guys want to.

Awesome can't wait for the next release then! Lotsa apps out there calling out to me! Thanks guys =)

gbhil said:
We might as well use this thread to learn to play with the boot image though, that is if you guys want to.
Click to expand...
Click to collapse
You bet. It's about time I got my hands dirty.

I'm game let me know if you need me to test anything!

Cool deal. You need Linux to extract and compress the boot.img, and you need to be current with Perl and running jre5 or higher.
Ubuntu 9.04+ is set up out of the box, but any version can be made to work.
Then grab these files from Lox -
http://forum.xda-developers.com/attachment.php?attachmentid=231902&d=1254004933
http://forum.xda-developers.com/attachment.php?attachmentid=234040&d=1254622769
and extract them into your sdk/tools dir. (or any dir in your path)
get all that, then pick a boot.img from a rom and put it in a work folder.
Holler when you get that far, or if you have any q's.

I wanna learn myself. This should apply to mac os as well?

I have Mint on another machine. Gimme a bit to get caught up...

david279 said:
I wanna learn myself. This should apply to mac os as well?
Click to expand...
Click to collapse
Darwin might work. Never tried
watzone69 said:
I have Mint on another machine. Gimme a bit to get caught up...
Click to expand...
Click to collapse
np. I'm @work so going slow is better anyway lol.

ok i just ran the files in terminal. so i guess it might work.

I'm back
Inisde the work folder you dropped the boot.img into, run this from a term:
extract-kernel.pl boot.img
extract-ramdisk.pl boot.img
it will give you several files and a new directory. That dir is the unpacked ramdisk. The init.rc file is the one we're looking for. Open it with a Unicode editor and read it. It has it's own syntax, but it's almost like bash and not too hard to figure out. Hopefully you loaded a bootimg that has a2sd in it. Look near the bottom of the file for the a2sd start up line. It will have a2sd, apps2sd, a2sd004 or something like that. Once you find it so you can see the name used, search the rest of the file for that name.
Those lines will show you how a service gets declared and called at boot time.

I'm up and running now. I downloaded python 2.6.4. Do I need to install it or just extract it somewhere? Please forgive my linux noobness.
The other 2 zip files are extracted and in my tools folder. I'm getting the boot.img now.

idk if this will work as i too am a newb to android and the way they deal with the boot process is somewhat a bit different from what i'm used to, but heres a new boot.img if you guys want to flash it to see if apps2sd works. note, this is not a zip, remove that suffix.
to flash it to your phone just move the boot image to your sdcard then reboot into recovery. from there go into adb and mount your sdcard, then flash the new boot image.
Code:
adb shell
mount /sdcard
flash_image boot /sdcard/newBoot2.img
reboot
tell me if it fixes your apps2sd problem or not.

watzone69 said:
I'm up and running now. I downloaded python 2.6.4. Do I need to install it or just extract it somewhere? Please forgive my linux noobness.
The other 2 zip files are extracted and in my tools folder. I'm getting the boot.img now.
Click to expand...
Click to collapse
try it without doing anything to Python first....especially since I meant perl
Just try my last post and see if it works for ya. I'll edit my first post

gbhil said:
try it without doing anything to Python first....especially since I meant perl
Just try my last post and see if it works for ya. I'll edit my first post
Click to expand...
Click to collapse
Nope, I got "command not found" both times.

darchstar said:
idk if this will work as i too am a newb to android and the way they deal with the boot process is somewhat a bit different from what i'm used to, but heres a new boot.img if you guys want to flash it to see if apps2sd works. note, this is not a zip, remove that suffix.
to flash it to your phone just move the boot image to your sdcard then reboot into recovery. from there go into adb and mount your sdcard, then flash the new boot image.
Code:
adb shell
mount /sdcard
flash_image boot /sdcard/newBoot2.img
reboot
tell me if it fixes your apps2sd problem or not.
Click to expand...
Click to collapse
Thanks darchstar, I'll try that in a bit.

watzone69 said:
Nope, I got "command not found" both times.
Click to expand...
Click to collapse
you gotta make it executable
inside the directory with the perl scripts do this
Code:
chmod a+x ./

How to root the Droid 2

All credit for the binary goes to Sebastian Krahmer at http://c-skills.blogspot.com/. Please see fit to donate via Paypal to [email protected]
If you want a simpler 'one-click' process, go to this thread: Easier 1-2-3 Droid 2 Root for Windows / Linux / Mac
***NOTE: Proceed at your own risk. I and the providers of this code are not responsible for anything you do to your phone!***
Setup:
- Install adb (here) and Motorola drivers for windows(32-bit or 64-bit)
- Download attached archive
- Extract to a directory, I used c:\Droid2Root
- Make sure you have USB degugging enabled
- Change connection to PC Mode
Process:
- Open command prompt
- cd c:/wherever-your-sdk-tools-folder-is
- adb devices (to verify the connection)
- cd c:/Droid2Root
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push su /sdcard/su
- adb push busybox /sdcard/busybox
- adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
- adb shell
- cd data/local/tmp
- chmod 0755 rageagainstthecage-arm5.bin
- ./rageagainstthecage-arm5.bin
- let the process run until it 'kicks' you out (may take a minute or two) to c:/Droid2Root
- cd c:/wherever-your-sdk-tools-folder-is
- adb kill-server
- adb devices (to verify the connection)
- adb shell (you should now have a # prompt, if not return to ./rage step above)
- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
- cp /sdcard/Superuser.apk /system/app/Superuser.apk
- cp /sdcard/su /system/bin/su
- cp /sdcard/busybox /system/bin/busybox
- chmod 4755 /system/bin/su
- chmod 4755 /system/bin/busybox
- mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
- exit
- exit
I'm sure there are certain steps that could be streamlined or eliminated, so please feel free to make a suggestion and I'll edit the post.
Additional thanks to @rainabba and AllDroid.org for their excellent Droid X rooting tutorial, which assisted me greatly in this process.

waiting for a recovery, glad to see its rooted

Android n00b here, I can remove the Verizon crapware with this right? And tether?

thelolotov said:
Android n00b here, I can remove the Verizon crapware with this right? And tether?
Click to expand...
Click to collapse
yes and yes

thelolotov said:
Android n00b here, I can remove the Verizon crapware with this right? And tether?
Click to expand...
Click to collapse
I wouldn't remove anything yet since we don't have a sbf file to recover from partial bricks. However, tethering and any other apps that require root can be used now.

I'm new to doing this all the adb way.
When you say extract to a directory what do you mean to extract. After it downloads the achive files its done.....
i understand the rest of the commands but im lost there

Hmm, alright, that's still worth it, will I lose my data/have to hard reset to root?

Right click the downloaded archive and "extract files". You need to do this so adb can push them to the phone.

thelolotov said:
Hmm, alright, that's still worth it, will I lose my data/have to hard reset to root?
Click to expand...
Click to collapse
Nope, it just gives you access. Nothing deleted.

I'm retarded i didnt realize it was attached to the post, i thought it was what adb downloaded when i first opened it cause it called them archives.

cannot access
I got as far as pushing super user su and busy box onto my phone but it says that system in read only.. how do i fix this?

Anybody actually try this?

Hello,
I am following your directions and when I get to the "adb push Superuser.apk" step I receive the following error:
"failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file system"
I get this same error for the other adb push steps that follow.
Edit: To verify, I get a # shell.
Edit 2: I tried pushing the Superuser.apk to /data/local/tmp then cp to /system/app/, this also popped up a read-only file system error.

I'm currently trying it.
I have a 64 bit driver on my computer that i used to use for my D1 but it doesn't recognize my D2 when doing adb devices and i cant install the 32 bit driver

GSletta said:
I got as far as pushing super user su and busy box onto my phone but it says that system in read only.. how do i fix this?
Click to expand...
Click to collapse
Did you verify you have the # prompt three steps before that?

Yeah i get the # but it wont let me push superuser su and busybox

GSletta said:
Yeah i get the # but it wont let me push superuser su and busybox
Click to expand...
Click to collapse
Weird.. I didn't need to mount the system manually, but let me if there's a step I left out.

and some more screens (feel free to use in first post):
http://i.imgur.com/nPllt.jpg
http://i.imgur.com/COTEA.jpg
http://i.imgur.com/open3.jpg

djh816 said:
and some more screens (feel free to use in first post):
http://i.imgur.com/nPllt.jpg
http://i.imgur.com/COTEA.jpg
http://i.imgur.com/open3.jpg
Click to expand...
Click to collapse
Did you add any steps to mount the system? I don't believe I did, but it seems others are finding it to be read-only.

jerseyh22accord said:
I'm currently trying it.
I have a 64 bit driver on my computer that i used to use for my D1 but it doesn't recognize my D2 when doing adb devices and i cant install the 32 bit driver
Click to expand...
Click to collapse
Don't know if it will help you, but if it's anything like the DInc, you could just use the SDK's drivers and add a few device identifier lines to the INF file before installing them.

[GUIDE] How to Flash a ROM WITHOUT an SD Card

How to Flash a ROM Without an SD Card
​
This is for all those who don't have a working sdcard, sdcard slot, etc. but want still to flash a new rom
Prerequisites:
Flash an Amon_RA recovery if you're using Clockwork - I recommend Darch's unofficial (CDMA Hero refer to my signature if you need it)
Access to a computer that had AndroidSDK tools on it - you'll be using ADB
Put whichever ROM.zip you want to flash in your android-sdk\tools folder - I would rename it to something simple. (My example which I'll be using for this tut is: C:\AndroidSDK\toosl\ROM.zip)
Directions:
Reboot into the Amon_RA recovery
Wipe data/factory reset, cache, and dalvik via the recovery menu
Open up cmd/terminal on your computer
Navigate to your android-sdk\tools directory
Enter the following in cmd/terminal:
Code:
adb shell
mount data
*wait a second or two* You may or may not get the "/ #" line returned.
Despite what happens press "Ctrl+C" to break the command and get back to the standard AndroidSDK\tools> directory
Enter the following in cmd/terminal:
(replace "ROM.zip" with the name you're using)
Code:
adb push ./ROM.zip /data/
*this will take anywhere from 30sec to a min depending on the rom.zip size*
Then we do this in cmd:
Code:
adb shell
recovery --update_package=DATA:ROM.zip
Wait for it to finish flashing/updating
Reboot
ENJOY
Brief rundown of what we just did:
Wiped /data/ to free up space for the zip
Put our ROM.zip onto the /data/ partition since we don't have an SD Card to work with.
Told the recovery to flash from our /data/ partition instead of /sdcard/
I did some digging around the AmonRA github to look for the commands it actually performs while in recovery I figured out exactly how to do what I wanted.
(namely THIS PAGE for those of you who are interested in seeing the exact page I found them on)

Good knowledge man. Thanks for the guide
Root-Hack-Mod-Always™

I got excited when i read the title having lost my sdcard, unfortunately my lap top in Frys customers service n i never went back for it, bs they said it was water damage lol idiots are wrong so my guarantee didnt cover it,anyways i think most of us knew this method, thnkz anyways........WHAT I WANT TO KNOW IS HOW OR IF POSSIBLE TO CHANGE THE PATH TO THE STOCK BROWSER DOWNLOADS TO INTERNAL STORAGE????????????? PLS IF ANY1 KNOWZ LET ME KNOW

gotablunt said:
I got excited when i read the title having lost my sdcard, unfortunately my lap top in Frys customers service n i never went back for it, bs they said it was water damage lol idiots are wrong so my guarantee didnt cover it,anyways i think most of us knew this method, thnkz anyways........WHAT I WANT TO KNOW IS HOW OR IF POSSIBLE TO CHANGE THE PATH TO THE STOCK BROWSER DOWNLOADS TO INTERNAL STORAGE????????????? PLS IF ANY1 KNOWZ LET ME KNOW
Click to expand...
Click to collapse
/sigh. I'd try to help if I knew what this post was even about. All I got was something about a laptop at Frys.
Anyway, nice post OP.

gotablunt said:
I got excited when i read the title having lost my sdcard, unfortunately my lap top in Frys customers service n i never went back for it, bs they said it was water damage lol idiots are wrong so my guarantee didnt cover it,anyways i think most of us knew this method, thnkz anyways........WHAT I WANT TO KNOW IS HOW OR IF POSSIBLE TO CHANGE THE PATH TO THE STOCK BROWSER DOWNLOADS TO INTERNAL STORAGE????????????? PLS IF ANY1 KNOWZ LET ME KNOW
Click to expand...
Click to collapse
Fail. Put the blunt DOWN.
+1 OP

You first mentioned
kyouko said:
My example which I'll be using for this tut is: C:\AndroidSDK\toosl\kyoukoROM.zip
...
Code:
adb push ./kyoukoROM.zip /data/
Click to expand...
Click to collapse
But later, you use this:
Code:
adb shell
recovery --update_package=DATA:mau5.zip
Click to expand...
Click to collapse
I am confused on whether we use 'mau5.zip' as it is in the final command or change it to the name of our rom, which would be kyoukoROM.zip in your case?

HQRaja said:
You first mentioned
But later, you use this:
I am confused on whether we use 'mau5.zip' as it is in the final command or change it to the name of our rom, which would be kyoukoROM.zip in your case?
Click to expand...
Click to collapse
It would be the name of the file you are trying to flash.

How do you flash the recovery without an SD card tho?
EDIT: I figured it out. I will post my steps later.

Here is what I did:
Rooted phone
Attempted to push Flash_image - failed due to filesystem permissions
Steps for Flash_Image:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system/bin
chmod 777 /system/bin
exit/ctrl+c
adb shell
adb push flash_image.zip /system/bin/flash_image
adb shell chmod 0755 /system/bin/flash_image
Flashing Recovery:
adb push Recovery.img /system/bin/
adb shell
flash_image recovery /system/bin/Recovery.img
rm /system/bin/Recovery.img
reboot recovery
Then proceeded to follow the steps in this guide successfully

Stuke00 said:
Here is what I did:
Rooted phone
Attempted to push Flash_image - failed due to filesystem permissions
Steps for Flash_Image:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system/bin
chmod 777 /system/bin
exit/ctrl+c
adb shell
adb push flash_image.zip /system/bin/flash_image
adb shell chmod 0755 /system/bin/flash_image
Flashing Recovery:
adb push Recovery.img /system/bin/
adb shell
flash_image recovery /system/bin/Recovery.img
rm /system/bin/Recovery.img
reboot recovery
Then proceeded to follow the steps in this guide successfully
Click to expand...
Click to collapse
tip: use 'adb remount' instead of the manual mount commands. Do that before you adb shell. Just saves a bit of typing.
good work!

HQRaja said:
in the final command or change it to the name of our rom, which would be kyoukoROM.zip in your case?
Click to expand...
Click to collapse
I changed the OP to make it more consistent.
But see the quote below
sirmx said:
It would be the name of the file you are trying to flash.
Click to expand...
Click to collapse
Stuke00 said:
How do you flash the recovery without an SD card tho?
EDIT: I figured it out. I will post my steps later.
Click to expand...
Click to collapse
Good to hear you got it. I realized later that I should have mentioned how to flash it without an SD card

Cool! Favorited in case I ever need it. Really useful I would imagine!

sirmx said:
tip: use 'adb remount' instead of the manual mount commands. Do that before you adb shell. Just saves a bit of typing.
Click to expand...
Click to collapse
So would that be like this:
Code:
adb remount
adb shell
adb push flash_image.zip /system/bin/flash_image
adb shell chmod 0755 /system/bin/flash_image
Just confirming because I am about to feature this method on the blog I write for (with credit to Stuke00 and a link to his post) and don't wanna mess up. =)
EDIT: Forgot to mention that you rock! Thanks for the earlier help too.
EDIT 2: Nevermind, did some reading on what 'adb remount' does and found out it remounts /system with read+write access so I guess this is it. Though please do correct me if I am still wrong (which I am often).

Covered this method
Oh and in case you guys are interested in seeing my coverage of your methods, here it is...
The original method by kyouko: http://www.addictivetips.com/mobile/how-to-install-a-rom-to-an-android-phone-device-without-sd-card/
The recovery method by Stuke00: http://www.addictivetips.com/mobile/how-to-flash-a-recovery-to-an-android-device-without-sd-card/
Thank you guys, I can't do my work and earn my living without you. Keep it up! =)
EDIT: I'll have this last line as a part of my signature now.

Is this possible with Clockwork?

refthemc said:
Is this possible with Clockwork?
Click to expand...
Click to collapse
Dunno, I don't have plans for using it ever again nor have I looked at Clockwork's github - if there is one.
But it should be able to if you can find out what scripts/commands are run when you use the menu. If you want to you can check the github link I have in the OP to see where I found the commands that are run, and then look for something similar in clockwork's source.
You'd be looking for something similar to:
Code:
--update_package=root:path - verify install an OTA package file

Thanks for the awesome guide! Saves me a lot of trouble, I don't have to take out my sdcard or manually enable USB in recovery anymore!

for me
for me it did not work in data but it worked in cache

kyouko said:
Brief rundown of what we just did:
Wiped /data/ to free up space for the zip
Put our ROM.zip onto the /data/ partition since we don't have an SD Card to work with.
Told the recovery to flash from our /data/ partition instead of /sdcard/
Click to expand...
Click to collapse
Hi, I try to install a ROM from CACHE but I'm getting this in my command line:
recovery --update_package=CACHE:rom.zip
sh: /sbin/postrecoveryboot.sh: not found
Click to expand...
Click to collapse
And my phone do nothing, how many time it take to install? normally using sdcard took no more than 5 minutes but using ADB nothing happens. Any help?

reynierpm said:
Hi, I try to install a ROM from CACHE but I'm getting this in my command line:
And my phone do nothing, how many time it take to install? normally using sdcard took no more than 5 minutes but using ADB nothing happens. Any help?
Click to expand...
Click to collapse
what recovery are you using?

1.55.531.3 rom?

Hello all.
I looked and can't find but is there a rooted 1.55.531.3 rom for the device anywhere.
Rooted the phone tried the ICS from sensation and kinda want to go back but not unroot.

I could send you my recovery if you have the ability to flash
rooted 1.55.531.3 with clockwork recovery and SU

M9x3mos said:
Hello all.
I looked and can't find but is there a rooted 1.55.531.3 rom for the device anywhere.
Rooted the phone tried the ICS from sensation and kinda want to go back but not unroot.
Click to expand...
Click to collapse
yeah, what you are looking for doesn't exist at the moment. i too thought about making a nandroid of the the new ROM for people to flash, but since the new setup comes with a new radio, new kernel, new HBOOT, etc., i'm not sure how it would fly if someone just flashed the nandroid?

Hboot n radio would be the only thing missing... Kernels sits in recovery....
rooted 1.55.531.3 with clockwork recovery and SU

I know I made a flashable package out of the Google Talk apk file, and either did or meant to make some out of the other apps in it - I'm not sure which thread it's in.
I can check later and link it. Not sure what else anyone did with it, if wifi calling wasn't pulled forward from it I'll have a package for that sometime soon anyway.
I also never did get a chance to check what the gps changes were I remember being in it.
Edit:
Link to Gtalk flashable zip package from that update.
Sent from my Bulletproof_Doubleshot using xda premium

nlarge said:
I could send you my recovery if you have the ability to flash
rooted 1.55.531.3 with clockwork recovery and SU
Click to expand...
Click to collapse
Do you have the stock rom for 1.55.531.3 that I can flash on my mt4gs? I would really appreciate it

http://forum.xda-developers.com/showthread.php?t=1484679
http://forum.xda-developers.com/showthread.php?t=1433805

It would be flashed as if restoring a nandroid. I would flash the above link. If you really want it I can send it
rooted 1.55.531.3 with clockwork recovery and SU

Thanks. Okay, this is where I am:
Unlocked bootloader with htcdev
s-on
hboot 1.45.0013
software 1.55.531.3
Would like to achieve root so that I can flash custom roms/use titanium backup. From what I can tell, nlarge was able to accomplish this. (http://forum.xda-developers.com/showthread.php?t=1474933&page=6). However, couldn't post on that thread because I have less than 10 posts....sorry.
Cannot use temproot (FR3VO) method because says needs s-off and/or adb mount issue:
An error occurred while running the exploit (-1) (errno: 22)
c:\Android>adb wait-for-device
c:\Android>adb remount
remount failed: Operation not permitted
c:\Android>adb shell mount -o rw,remount rootfs /
mount: Operation not permitted
c:\Android>adb shell mount -oremount,suid /dev/block/mmcblk0p23 /data
mount: Operation not permitted
c:\Android>adb shell mkdir /vendor/bin
mkdir failed for /vendor/bin, Read-only file system
c:\Android>adb shell chown root.shell /vendor/bin
Unable to chmod /vendor/bin: No such file or directory
c:\Android>adb shell chmod 755 /vendor/bin
Unable to chmod /vendor/bin: No such file or directory
c:\Android>adb push ./sqlite3 /vendor/bin
cannot stat './sqlite3': No such file or directory
c:\Android>adb push ./su /vendor/bin
cannot stat './su': No such file or directory
c:\Android>adb push ./busybox /vendor/bin
cannot stat './busybox': No such file or directory
c:\Android>adb shell chown root.shell /vendor/bin/su
Unable to chmod /vendor/bin/su: No such file or directory
c:\Android>adb shell chown root.shell /vendor/bin/busybox
Unable to chmod /vendor/bin/busybox: No such file or directory
c:\Android>adb shell chown root.shell /vendor/bin/sqlite3
Unable to chmod /vendor/bin/sqlite3: No such file or directory
c:\Android>adb shell chmod 6555 /vendor/bin/su
Unable to chmod /vendor/bin/su: No such file or directory
c:\Android>adb shell chmod 4555 /vendor/bin/busybox
Unable to chmod /vendor/bin/busybox: No such file or directory
c:\Android>adb shell chmod 755 /vendor/bin/sqlite3
Unable to chmod /vendor/bin/sqlite3: No such file or directory
c:\Android>adb shell busybox --install -s /vendor/bin
busybox: permission denied
c:\Android>adb shell sync
c:\Android>adb shell chmod 6555 /vendor/bin
Unable to chmod /vendor/bin: No such file or directory
c:\Android>adb install ./Superuser.apk
can't find './Superuser.apk' to install
c:\Android>pause
Press any key to continue . . .​
So, I understand, permission denied/operation not permitted, I assume because I don't have root.
When I look at superuser, it says "su binary voutdated" and when I tap to check for updates, automatic update fails and error message "su was not updated. A zip file (su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary.
Can't boot into recovery mode, phone just sits on mytouch 4g slide screen. Again, I assume because no root. Same thing happens if I try to factory reset, just stays on the mytouch 4g slide screen.
Anyone have any suggestions? I am going crazy trying to get this phone to work. I would really appreciate the help!

Flash clock work recovery... I think I linked it somewhere... Or Google will help
rooted 1.55.531.3 with clockwork recovery and SU

Now find yourself a nice recovery image (CWM), boot phone into fastboot mode, "fastboot flash recovery recovery.img".
When this is done you will have a free and open recovery image, and can use that to write/install the su binary and apk (either with flashable zip or through adb shell, either will work).
rooted 1.55.531.3 with clockwork recovery and SU

nlarge said:
Now find yourself a nice recovery image (CWM), boot phone into fastboot mode, "fastboot flash recovery recovery.img".
When this is done you will have a free and open recovery image, and can use that to write/install the su binary and apk (either with flashable zip or through adb shell, either will work).
rooted 1.55.531.3 with clockwork recovery and SU
Click to expand...
Click to collapse
Have tried flashing new and old versions of cwr and the earlier links from blue with no luck. Trying to do it manually through the computer with fastboot, results in 'waiting for device' message. All drivers installed, usb debug, have tried charge only/mount as disk drive options. Neither work. Have tried flashing manually by converting .img to .zip without compression and flashing through phone. No error message but nothing changes.
Cannot use cwm to flash because not error message says not rooted. Not sure what else to do. BTW, you guys are awesome for helping me out Thanks!

Put your phone in fastboot. Pull battery, hold down and power then try again
rooted 1.55.531.3 with clockwork recovery and SU

How to fastboot flash recovery
Return to Contents Page - doubleshot Developers Reference
Boltinghouse said:
Have tried flashing new and old versions of cwr and the earlier links from blue with no luck. Trying to do it manually through the computer with fastboot, results in 'waiting for device' message. All drivers installed, usb debug, have tried charge only/mount as disk drive options. Neither work. Have tried flashing manually by converting .img to .zip without compression and flashing through phone. No error message but nothing changes.
Cannot use cwm to flash because not error message says not rooted. Not sure what else to do. BTW, you guys are awesome for helping me out Thanks!
Click to expand...
Click to collapse
(hah, thanked but meant to hit quote)
What you need to do is go here: http://clockworkmod.com/rommanager
Scroll down the list and find the recovery for our device (5.0.2.7 for the myTouch 4G Slide) - download this.
Put it in the same folder as 'fastboot.exe' on your computer. Rename it to recovery.img
On your phone, turn off 'fastboot' in power options.
Power off the phone.
Now, give it a minute to power off - then hold the volume down button and press power.
Now it will boot up to the hboot menu. The list presented will have you highlighted on the word 'fastboot' - press power to choose this.
Now you are presented with the fastboot menu. It should say fastboot with a red highlight around it near the top.
At this time you should plug the USB cord from your computer into the phone. It will update to say fastboot USB in red highlight now.
-okay-
We have the phone booted up in fastboot, attached to the computer, and ready to work with.
Open up your command prompt, and navigate to the folder where you have the fastboot command. This is the same folder that you have the new clockworkmod recovery.img in from before.
In your terminal now type:
Code:
fastboot devices
This will come back with your device, serial number, and show you it is connected and ready to go. (if it is not something is wrong)
Now type:
Code:
fastboot flash recovery recovery.img
Let's break this down:
fastboot = activates the fastboot.exe command, and says that what's typed next uses the definitions in that fastboot.exe file.
flash = command that says write to
recovery = destination (name of partition) being written to
recovery.img = file written to previously defined location.
----
Since you have the new clockworkmod recovery file in the same folder as fastboot.exe, and you renamed it to recovery.img, then the previously shown command will overwrite your stock recovery with the new image you are providing it.
At this point you should have clockworkmod recovery in place of your stock recovery when you boot the device to hboot menu and select recovery.
Let us know if you have any other problems.

Good explanation blue.... It sounded like he knew what he was doing, hence my quick correction...
Hate typing a lot out from phone!
rooted 1.55.531.3 with clockwork recovery and SU

OMG! Thats awesome. FINALLY ROOTED!!!!! yay! So happy. Thank you guys so much. nlarge and blue, you two are the best!
Thanks again
~Brandi~

Oops... Sorry I called you a he...LOL... Most of us nerds are guys
We help where we can
Boltinghouse said:
OMG! Thats awesome. FINALLY ROOTED!!!!! yay! So happy. Thank you guys so much. nlarge and blue, you two are the best!
Thanks again
~Brandi~
Click to expand...
Click to collapse
rooted 1.55.531.3 with clockwork recovery and SU

nlarge said:
Oops... Sorry I called you a he...LOL... Most of us nerds are guys
We help where we can
rooted 1.55.531.3 with clockwork recovery and SU
Click to expand...
Click to collapse
It's all good, I know being a chick I'm in the minority here. Either way, thank you so much.

So it looks like both nlarge and boltinghouse rooted s-on phones. Is there any reason not to go ahead and root that way? Is there any reason you need/want s-off?

it depends on what you want to do with your phone...
If you just want to be able to make recovery and flash ROMS than you dont need s-off
If you want to play with other stuff(radios and mounts) then you need s-off.
I personally like doing things to my phone so I would like to get to s-off. I am ok with it for now, but S-off will give me the full control I want.
qwerty3656 said:
So it looks like both nlarge and boltinghouse rooted s-on phones. Is there any reason not to go ahead and root that way? Is there any reason you need/want s-off?
Click to expand...
Click to collapse