Develop Bugs

New (hybrid) Hero root method

I have a slightly different Hero root method that persists the unlocked boot.img so you can do 'adb remount' to remount RW the file system... this was a key requirement for me!
Details:
http://android.modaco.com/content/h...oting-the-hero-step-by-step-my-hybrid-method/
Kudos to those who have gone before... I plan to add more stuff to the update.zip used here going forward.
P

yeah, adb as root is a must. it's the first thing i did when i received my hero
maybe it's better if you include wlan.ko in the update, because if someone who uses the update had a different kernel version wifi will not work

I´m receiving my HERO in a couple of hours. I´m going to use the 2Gb card that comes with the phone untill my new 16Gb class6 card arrives next week.
One question, do I need to "re-root" my device when I swap the cards next week?
I read something about that I have to have a card inserted during the root proccess.
I guess it is only used during the job...?!

modaco said:
Details:
http://android.modaco.com/content/h...oting-the-hero-step-by-step-my-hybrid-method/
Click to expand...
Click to collapse
To confirm, you do step 4 without the Hero connected to the PC?
Also, once rooted, what are my benefits? I understand I can move apps to the SD card? Is this done through the phone?

Well spotted, rejigged the instructions!
P

It seems to work...Thnx! no we will wait for a rom

Weird.. I keep getting "error: device not found" while in Device Manger I have a directory called "ADB Interface" with a device called "HTC Dream". Shouldn't that be "HTC Hero"?
So I do have a ADB device connected, but there's a fault somewhere..
EDIT: Found what I was doing wrong. I updated the driver for the SD card instead of the actual phone.. Stupid me. Great tutorial, but not fool-proof yet

As I enter 'adb push update-hero-signed.zip /sdcard/update.zip' I get the following error -
The program can't start because AdbWinApi.dll is missing from your computer. Try reinstalling the program to fix this problem.
What have I done wrong?
Okay, while typing this I realise I actually need to go to the folder I unzipped this too and then into the Hero folder. Maybe add this to instructions? Or is it just me being stupid?

Okay, seemed very easy (how do I check it worked).
I'm now looking at this about how to move apps to the SD card -
http://android-dls.com/wiki/index.php?title=Haykuro_Apps_to_SD
What does it refer to when it says "Setup in 5.0.1 onwards"?
Looks a little complex to me
I assume there are no custom ROM's out just yet...?

What is the difference with that method? Why hybrid? What is adb remount for?

Problem with "fullproof" card

So for the past week or so ive been trying to root my incredible to no avail... ive used every method posted and none work..
The two cards i tried are the 2gb card that came with my droid incredible.. formatted Fat32 1024 byte size with nothing on the card, and it didnt work on ANY method.. so then i tried my transcend 8gb class 6 card that was previously formatted to Fat32 awile ago and had a bunch of stuff on it, and nothing worked with that one either..
So then i said screw this, i went out and bought the holy card that supposidly has a 100% success rate... the Kingston 4gb class 4 card.. put that bad boy in and it dosent work either! what the hell can i do... the Kingston is brand new.. nothing on it, formatted Fat32 1024 byte size

did you format it in the phone?
Sent from my ADR6300 using XDA App

I formatted it via my PC.. Windows7 i used the format tool in My Computer... i didnt do quick format either i did the full format Fat32 1024 byte size

format it in your phone once and give it a few tries
Sent from my ADR6300 using XDA App

is this done in recovery or Hboot or what?

while phone is fully booted. menu > settings > sdcard and phone storage
scroll down to the bottom
Sent from my ADR6300 using XDA App

Just formatted the card via phone then went back into recovery and tried and no go.. ive tried it about 35 times now with this *100% successrate card* and gotten zero, also keep in mind that the design of this particular card makes it impossible to click in and out in rapid succession, it keeps getting stuck like the stock verison 2gb card does while my transcend 8gb has no problems clicking rapidly

my guess is you are doing something wrong or something is not set up right
Sent from my ADR6300 using XDA App

invisiblek said:
my guess is you are doing something wrong or something is not set up right
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I wish that was the case but i have no problem using ADB in any setting, the drivers are definately set up right as i can use ADB fine while in android and i can even get an adb reboot recovery out of it before the phones fully booted up normally as in binnys method

http://www.youtube.com/watch?v=Z8mheIkQ-1o
dunno if u saw that yet, thats the video i made the night they got root
i have a kingston 4gb class 4 and thats the method i did there
this method works 100% of the time for me too

yeah. been trying that method for an hour just as in the video and its been 0% for me lol

There is no sdcard that is going to make the method foolproof. You need to reduce your variables. Windows driver scheme can become a mess very, very quickly. I recommend booting your PC with a Linux LiveCD like Linux Mint 9 Isadora or Ubuntu 10.04 Lucid Lynx. They're both free and both distros recognize the DI out of the box. I've attached the ./loop.sh that I've used successful to bring up the adb error you're looking for--just rename the file before you run it from linux terminal. Navigate your browser in linux and download the Linux Android SDK ho ~/Downloads, and once you do, extract it to ~/Downloads. Then, to be ultra-safe, use these commands:
Code:
*open terminal*
cd ~/Downloads/ # assuming you d/l'd my file/SDK file to your home Downloads folder in Linux
cd android-linux-sdk_86/tools
sudo ./android
# this will trigger the SDK installer, just tell it to fetch all packages, then close it
rename loop.sh.txt loop.sh
chmod a+x loop.sh
sudo ./loop.sh
# you'll get an infinite loop with "adb: device not found"
At that point, pop the back cover off your DI, power it down, connect the USB cable, boot into bootloader, eject the SDcard, making sure your terminal window is visible: select Recovery menu, then start counting from the boot vibrate. Count to seven seconds (as in: one-one-thousand, two-on-thousand ...), then insert the card exactly on 7 or when the white screen scanline flickers, whichever comes first.
Hint: I like to do this with the terminal window kinda small with a maximized "Computer" Nautilus file explorer window up in the background, showing all devices. You'll notice with this view that your android devices appear, in bootloader, disappear on recovery reboot, then reappear when recovery/black triangle screen is done loading. If you've missed the timing window and the card wasn't inserted right, you'll see those two volumes pop-up, but your adb shell error message won't have changed--and you know to pull the battery and start over. If the message does change when when the drives appear: success! You can "up vol-power" and continue with whatever rooting method you like, provided you know the slight (good) differences using linux introduces versus Windows.
Good luck, you only have to do this right once, then Unrevoked2 locks it in place!

Dude, it took me forever. In the end it was finding the right time to insert the SD card for me. I would start out with it in then right before I selected recovery I would pop it out and then I would push it back in as close to the same time as the 2nd "mount tone" as I could. I have only had success with class 6 cards but both an 8 gig and the infamous 2 gig PNDY card have worked for me. I also had a prob with getting the adb shell to work after a did the push payload witch turned out to be a bad download of the "tools folder". re-downloaded it with the phone still in recovery and it was smooth sailing from there.
Don't get discouraged and have a lot og free time when you start trying the next time.

Did you try downgrading? I had no much for a week then I downgraded ands got it on the very first try. Good luck
Sent from my ADR6300 using XDA App

I tried for DAYS to get this to work... I searched every android forum on the net for tricks... I gave up... I got pissed and started again... gave up again... and finally like magic I found the right combination of bull**** trickery to make it work.
How I did it:
1. Turn off the phone normally
2. Remove sd card (I used the 2g card that Verizon sent)
3 Boot up into recovery with the Vol- /Power button method (sd card out)
4. Let the phone do it's thing
5. Run loop.bat
6. The trick here- When you press the power button to select recovery have the sd ready to go in (sitting in the slot but not clicked into mounted position)... then when you hear the second usb "ding" push it in as fast as you can- almost simultaneously with the "ding".
This got me into the error message in about two tries (after possibly hundreds of failed attempts using other methods)- after that it's pretty much downhill.
No guarantees, but it worked for me and quite a few other frustrated souls.
Keep the faith- root is definitely worth the headache

Edit: Disregard. I didn't see that rynosaur had already posted detailed steps above.
Windows needs to see the device as too many different things during the different stages (i.e. HBOOT, Recovery, Fully booted). I did it under Linux and didn't have to worry about that. If you have a Linux partition or a Linux Live Distro, try it there. The commands are basically the same except you need to preceed the adb commands with ./ as in ./adb reboot recovery

DobbsianYeti said:
I tried for DAYS to get this to work... I searched every android forum on the net for tricks... I gave up... I got pissed and started again... gave up again... and finally like magic I found the right combination of bull**** trickery to make it work.
How I did it:
1. Turn off the phone normally
2. Remove sd card (I used the 2g card that Verizon sent)
3 Boot up into recovery with the Vol- /Power button method (sd card out)
4. Let the phone do it's thing
5. Run loop.bat
6. The trick here- When you press the power button to select recovery have the sd ready to go in (sitting in the slot but not clicked into mounted position)... then when you hear the second usb "ding" push it in as fast as you can- almost simultaneously with the "ding".
This got me into the error message in about two tries (after possibly hundreds of failed attempts using other methods)- after that it's pretty much downhill.
No guarantees, but it worked for me and quite a few other frustrated souls.
Keep the faith- root is definitely worth the headache
Click to expand...
Click to collapse
the sdcard usb ding timing is key

So heres what happened, my first Kingston 4gig card didnt work after like 40 tries, so i said screw this and returned it, and then i went somewere else and picked up a second 4gb kingston
Went home, put it in my phone, rebooted recovery and got it to work instantly... got the recovery flashed... removed cityid.. pushed the update.zip and su and superuser all on my phone
however my phone would NOT chmod no matter what i did.. i tried everything, i copied and pasted the directions exactly as on the screen and it would never work, when i got to the last line that starts of 1n - or something like that it would say permission denied even though i was in su...
So anyway i said maybe it had worked, so i rebooted the phone.. i saw that superuser.apk was in my app drawer as an installed app.. then i went into terminal emulator and typed in "su" and it said permission denied.. the root didnt stick because the stupid Chmod did not work for me...
Oh and to top it off guess what else happens? Obviously when i try to go back into recovery it DOES NOT work... tried it about 35 times again now and it wont go back in whatsoever after doing it the first time.. also for me in recovery my second usb ding happens MANY seconds into the black screen.. if you start counting right when you press the power button for recovery and the white screen turns to black at like 5 seconds.. my second usb ding dosent happen until like 10 seconds... deep in the black screen

Joe92T said:
Oh and to top it off guess what else happens? Obviously when i try to go back into recovery it DOES NOT work... tried it about 35 times again now and it wont go back in whatsoever after doing it the first time.. also for me in recovery my second usb ding happens MANY seconds into the black screen.. if you start counting right when you press the power button for recovery and the white screen turns to black at like 5 seconds.. my second usb ding dosent happen until like 10 seconds... deep in the black screen
Click to expand...
Click to collapse
What's the difference now? Look at the root directory of the card. There's files there now. You need to re-format the card. The most effective formatting I (and others) have found is a split 2gig ext4 partition (linux fs), followed by a fat32 @ 1024k block allocation, long format. As soon as Android boots, it starts writing your card.

rynosaur said:
What's the difference now? Look at the root directory of the card. There's files there now. You need to re-format the card. The most effective formatting I (and others) have found is a split 2gig ext4 partition (linux fs), followed by a fat32 @ 1024k block allocation, long format. As soon as Android boots, it starts writing your card.
Click to expand...
Click to collapse
How can i format it like that using windows? The easy format tool you find when right clicking on the drive under my computer dosent have those functions

Moving Files From SD Card To Internal Memory Possible?

Hey guys, I love this site and the outpour of support. This is really the first issue I've run into with my evo thus far.
I want to move some files I made into ringtones from my SD card into the internal memory in the location of the stock ringer sounds. I want to do this so if I ever take out or swap SD cards I never have to worry about losing my ringers. I have been using the astro file browser but it apparently does not let me move or copy and paste the file(s) where I want them.
Is there any way to do this?
thanks a lot!
Also follow up question. My SD Card always mounts when I plug my phone into my PC. Is there a way to stop this? even when I put the phone to charge only, the SD card shows up in Win7.

You need to have root and NAND unlock if you want to do anything like that, but it is possible.
If you have NAND unlocked, you can do it with your phone running normally, but I would use ADB in your particular situation. You can also use something like Root Explorer, but it costs money.
If you do not have NAND unlocked, but you have toast's root, you must go into recovery first.
If you know how to use ADB and you have full root (w/ NAND unlock), you should be able to use a command line in Windows to this effect.
For ringtones:
Code:
adb shell cat /sdcard/ringtone.mp3 > /system/media/audio/ringtones/
For notification sounds:
Code:
adb shell cat /sdcard/notification.mp3 > /system/media/audio/notifications/
For the files on your SD.
Otherwise you can push from the Windows itself. In command line, navigate to the area in Windows where you have the sounds and do something like this:
Code:
adb push ringtone.mp3 /system/media/audio/ringtones/
or
Code:
adb push notification.mp3 /system/media/audio/notifications/
If you do not have NAND unlocked, but you have root and a custom recovery, go into the custom recovery, then apply this command.
Code:
adb shell mount /dev/block/mtblock4 /system
After that, the commands above should work normally.

Is it possible to copy the 8GB SD files to your computer, insert a 16GB into the phone, and them paste the files from the computer to the new SD card? Will I have to re-root?
I'm currently running Damage Control (full root) along with other root tweaks.

@Jykinturah- Won't he need to mount the file system first?

dang, I was hoping to do it without rooting. I was seriously contemplating rooting my phone before 2.2 was announced to be coming out "soon" but I am a little hesitant to take the plunge knowing that we should all have froyo soon. I may still consider this or may try and do some more research. Thanks for the help though! It is greatly appreciated.

GumboChief said:
@Jykinturah- Won't he need to mount the file system first?
Click to expand...
Click to collapse
If you are booted into the OS, no. If you are in recovery, yes.
Code:
adb shell mount /dev/block/mtblock4 /system
Not usually a great idea to write to system when booted up, but if its just a ringtone or something, meh.
rockdrummersrock said:
dang, I was hoping to do it without rooting. I was seriously contemplating rooting my phone before 2.2 was announced to be coming out "soon" but I am a little hesitant to take the plunge knowing that we should all have froyo soon. I may still consider this or may try and do some more research. Thanks for the help though! It is greatly appreciated.
Click to expand...
Click to collapse
I am not the best person to ask about whether you MUST be rooted to do this, but I think you need to.
Not sure if you can write to /system in recovery without being rooted.

[GUIDE] Persistent Temp Root for G2 to SD Card

Problem: Changes to the system partition are lost when Linux flushes the disk cache: http://pastebin.com/cm75Z9UA
These instructions are a workaround to provide temp root like normal plus persistence because /system /data and /cache are partitions on your SD card. This lets you reboot and even factory reset, while being able to easily restore your settings and such by re-rooting and mounting your SD card partitions back over the internal partitions.
Prerequisites:
SD card partitioned with four partitions:
6GB as fat (for your data, can be bigger or small depending on your card size)
400MB ext3 for /system
1.3GB ext3 for /data
200MB ext3 for /cache
On the phone, enable "USB debugging" in Menu -> Settings -> Applications -> Development
On a PC with the Android SDK tools (adb) installed and working:
adb push Superuser.apk /data/local
adb push busybox /data/local
adb push rage /data/local
adb push resume /data/local
adb push root /data/local
adb push rsync /data/local
adb push setup /data/local
adb push su /data/local
adb install Term.apk
adb shell chmod 755 /data/local/busybox /data/local/rage /data/local/setup /data/local/resume /data/local/rsync /data/local/root
On the phone, open "Terminal Emulator" and type:
/data/local/rage
Wait for it to say "[+] Forked NNNN childs." then press the back button.
Open "Terminal Emulator" again and it should force close.
Open it one more time and the prompt should display "#". Then type:
/data/local/root
/data/local/setup
You may need to re-root after it reloads the GUI, but then it will stick. setup is a script that mounts your SD card partitions and copies the existing. It should only be run once unless you want to erase what you have there previously. This step wont work if you SD card is not partitioned properly.
On future power-ons, run this after temp-root instead of setup:
/data/local/resume
and you should get your Android back how it was.

is it suppose to scan through all apps on phone then reboot

Thanks muchly, I'll try this when my G2 arrives.
I have a question about this method. It looks to me that what setup does is copy the entire system, data, and cache to the SD card. Then, when you run resume, it uses rsync to bring the main system (in the onboard flash) up to date from the SDcard version, and then any changes, even if not actually written to the main system partition due to the HTC copy protection, get written to the sdcard copy of the system. Very clever (if I'm reading this write, otherwise, still clever, but me not so clever as I mis-understood).
The question is this: Are there any glitches or instabilities generated by suddenly changing the system files after the OS is already booted? Do I have to make sure to do this before I begin using my phone after boot or risk making changes that I will then loose when I run resume?
Thanks again for the work putting this together!
Sheep

Sheep, you understand almost completely. Setup does copy the existing data from the internal phone memory to the SD card. However, it then (like resume) doesn't copy anything back, it just mounts the system, data, and cache partitions from the SD card on top of the internal ones.
I had issues with the internal memory reverting back after I make changes to it. It seemed to happen over a short time, or was triggered by things like mounting the SD card to a computer.
I've been using this for about 24 hours with no problems. I've done a couple fresh boots and ran resume. But I didn't test the instructions from scratch, so if anyone tests and finds a problem, let me know!

Any performance hit because of running from SD?

I haven't really noticed any.

How does this impact battery life?
Sent from my T-Mobile G2 using XDA App

Can't say, I've had my phone hooked up most of the time through adb looking for root. Just did this for fun and because I was sick of re-rooting all the time.

looks interesting I'll try it out tomorrow
Sent from my T-Mobile G2

so your sd card has to be partitioned pryor to trying this

pre-partitioned card?
thatruth132 said:
so your sd card has to be partitioned pryor to trying this
Click to expand...
Click to collapse
yes it does

texasaggie1 said:
yes it does
Click to expand...
Click to collapse
and how do i do this on a non-rooted device

thatruth132 said:
and how do i do this on a non-rooted device
Click to expand...
Click to collapse
Use your G1 to partition the card.
Brad

You can also connect your phone to a Linux computer (a LiveCD would be fine) and use gparted or fdisk. Don't forget to backup the contents of your card first!

Pretty cool. But I think I'm gonna wait for a more permanent solution....

sheek360 said:
Pretty cool. But I think I'm gonna wait for a more permanent solution....
Click to expand...
Click to collapse
There are no roms available yet any ways, so to a non dev, non cook like me, the Root is pretty much useless

I'd read that the currently available root was good until a reboot, then I saw this thread that made rerooting after a reboot much easier. Since then I've seen some posts that seem to indicate that a root may spontaneously disappear even without rebooting. Is this the case, some permissions may be lost even if you don't reboot?
I was ready to pull the trigger on this permanent-temporary root until I read that. I'd like to be able to import my old wpa_supplicant.conf file and get my corp ipsec vpn working. I'd also like to be able to get wifi-tether working (although I rarely use it), but if root won't stay 100% until a reboot, then I'm not going to bother.

Dalamak said:
There are no roms available yet any ways, so to a non dev, non cook like me, the Root is pretty much useless
Click to expand...
Click to collapse
Not true. I'm not a dev or a cook, but there are things that you can make the phone do with root besides adding a theme or ROM.
wifi tether
ipsec vpn
backups
etc...

smasraum said:
I'd read that the currently available root was good until a reboot, then I saw this thread that made rerooting after a reboot much easier. Since then I've seen some posts that seem to indicate that a root may spontaneously disappear even without rebooting. Is this the case, some permissions may be lost even if you don't reboot?
I was ready to pull the trigger on this permanent-temporary root until I read that. I'd like to be able to import my old wpa_supplicant.conf file and get my corp ipsec vpn working. I'd also like to be able to get wifi-tether working (although I rarely use it), but if root won't stay 100% until a reboot, then I'm not going to bother.
Click to expand...
Click to collapse
With temp root on the internal system partition, writes would revert back after certain things (after mounting the sd card to a computer through the phone and disconnecting it, I'd always loose root). When running /system from an sd card, no writes can be reverted because none are made, so I've never had to re-root.

how to partition an SD card?
thatruth132 said:
and how do i do this on a non-rooted device
Click to expand...
Click to collapse
I used gparted in ubuntu to do mine. Like SAINTH said, the install disk for ubuntu is also a livecd so you dont even have to install ubuntu if u dont want to

Can't write to sdcard

Okay, I'm freaking out a little bit.
The one app I use more than any other is Doggcatcher. It been my most-used app since my first G1. Well, I recently flashed the AOKP Jelly Bean ROM on my VZW GN, and now it seems that Doggcatcher can no longer save anything to the sdcard directory (either sdcard or storage/sdcard0).
What did I do wrong? I had Jelly Bean working on my phone for a while, but my GN's charge port broke and I received a replacement. I believe I restored a nandroid backup of my previous Jelly Bean install (which was a different ROM), and that's when my problems started. When I installed the AOKP ROM I wiped everything, but I still can't get Doggcatcher to save a single file. It seems other apps have trouble storing anything on the phone too, which is clearly a huge problem.
So what do I do? Please help! I'll offer any information I can.

Seems like permission is bit messed up. Have you don't anything that might've changed the permission?
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz

kyokeun1234 said:
Seems like permission is bit messed up. Have you don't anything that might've changed the permission?
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
Click to expand...
Click to collapse
Certainly nothing on purpose. I just flashed these ROMs in the way I would have thought I was supposed to. I loaded ClockworkMod and flashed the zip file from AOKP.
I really have no idea what I might have done or what to do now. I'm completely fine with wiping my phone, I just need to know how to start over!

If you have any directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *

danger-rat said:
If you have any directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
Click to expand...
Click to collapse
My friend, you are a genius. THANK YOU SO DAMN MUCH!! Seriously, you rock like crazy.
I followed your instructions (I had to learn how to get into the adb shell but that wasn't too tough), restarted the phone, and immediately tried downloading a podcast episode. I then pumped my fist in the air when I saw it successfully downloading.
Again, thank you so much. You rock.

Just passing on info from others...

danger-rat said:
Just passing on info from others...
Click to expand...
Click to collapse
Still, you helped, solved my problem, and fixed a problem for me in a week that's been filled with nothing BUT problems in other parts of my life, so I can't tell you how much I appreciate that.

FYI, I also posted your answer, along with a link to this thread, on the Doggcatcher forums where I also asked for help on this issue, when I thought it was just a problem with that app. I quoted your answer and gave you the credit, in case there's ever a future breakdown in the link I used

danger-rat said:
If you have any directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
Click to expand...
Click to collapse
thanks, you saved me too

johnz said:
thanks, you saved me too
Click to expand...
Click to collapse
Dude, this thread was dead, all you needed to do was press the thanks button, no need to revive this.
Sent from my i9250

danger-rat said:
If you have any directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
Click to expand...
Click to collapse
thanks so much for this!
I was struggeling with this problem, because I couldn't create backups anymore.
before I executed your command I had a look at the current permissions for the files.. some folders were owned by root:root instead of media_rw:media_rw. No wonder apps couldn't create files in those folders..
Too bad this was only shown in the shell when in recovery. While the phone was in Android the permissions showed correctly as root:sdcard_rw .. that's why it never occured to me this was a real problem.