Related
This thread is just going to be EXTRA NOOB friendly versions of other guides. Its also going to be like an index where all/most of the guides will be. Please ask you questions on original threads .
you can skip down to the Second Post Which is my First Guide about Downloading and Installing the SDK so you can use ADB.
I decided to make this guide because I too am a noob (not as much as i was before) and i know how frustrating it is when you dont understand something. even though xda make complicated things seem easy sometimes its not easy enough and im not saying its anyones fault thats why there are so many helpful members on the forum, i know i asked my fair share of questions
I will be gearing these guides to Windows XP. For many reasons, one i dont have a Mac, two Vista sucks , three not many have Windows 7 and i think its going to suck too , four I have ubuntu linux and it takes some knowledge to really know how to use it so you shouldnt be an EXTRA NOOB. Also Please use firefox because it saves files to desktop and easy to find and follow my instructions.
Downloading and Installing the SDK
This is my First Guide so bear with me
Downloading and Installing the SDK v1
First step is rooting you G1
Original Post:
http://forum.xda-developers.com/showthread.php?t=442480
Follow Koush's post it is pretty self explanatory PM if you need a MORE detailed version.
- download and install Winzip or Winrar
- go here and download the latest SDK:
http://code.google.com/android/download_list.html
- when download finishes right-click on the file and click "extract here"
- an new folder should come up rename it to: SDK
- open the folder; you should see a folder inside named tools and - some other stuff that dont matter right now
- open the tools folder, you should see two files named adb.exe and AdbWinApi.dll copy and paste those files to your system32 folder (go to my computer->local disk->windows->system32)
Next downloading and installing Drivers and getting adb to work
-Turn on "USB Debugging" on your device.
- Press Home-> press menu->select settings-> select Applications -> go down to Development then enable USB debugging
- dont plug phone in yet, if plugged unplug.
-go here and download the adb drivers now right-click and extract here
NOW plug in your phone
- the Found New Hardware Wizard will come up
- select No, not this time and click Next.
- Select Install from a list or specified location and click Next.
- Select Search for the best driver in these locations
- now find the folder: android_usb_windows and look in side and select android_usb.inf
Now we will check if everything works
- on your computer press start then go to run... and type in cmd
- first type in adb to make sure you got it working, you should see: Android Debug Bridgeversion 1.0.20
-now type adb devices, you should see something like this:
List of devices attached
HT844G****** device
The Hard Part is over.
Apps on sdcard (Magic 4.5 also)
For those with the new 4.5 rom u need to install busybox
Download this file to the root of your sdcard
http://androidfanatic.com/cms/unofficial-app-repo.html?func=startdown&id=14
then do folowinf commands from terminal emmulator or adb shell:
mkdir /data/busybox
cat /sdcard/busybox > /data/busybox/busybox
chmod 4755 /data/busybox/busybox
cd /data/busybox
./busybox --install
export PATH=/data/busybox:$PATH
then skip to STEP 2 of this post
Some people wanted a more simple Guide to installing apps on their sdcard
Original Post
http://forum.xda-developers.com/showthread.php?t=468959
First thing first go here and download and install Paragon Partiton Magic its a 90day trial chances are you'll only need to use it once.
http://www.download.com/Paragon-Partition-Manager-Personal-/3000-2248_4-10495078.html?tag=mncol
- conect your phone to computer via USB and mount it.
- and programs that may be using the phone: adb, windows explorer, mediaplayer etc
- open it up Paragon and click on create a partition, then click next
- you should see something like:
Basic Hard Disk 2 (HTC Android Phone USB Device)
- click on it and hit next
- move the slider to set how big you want you new partition to - be move left to make it smaller and right to make it bigger
I set mines to 1gb, some set theres to 2gb it also depends on how big you sdcard is if you have the 1gb that came with the phone i wouldn't advise doing this because of size and because their transfer rate are slower and could cause lag. 500mb is more than enough room it all depends on you i had 90 apps and only used 42mb.
- anyways when you select the size hit next
- in partition type select Linux Ext2 leave everything else the - way it was
- now select yes and hit next, the process should start
- it may tell you that you computer needs to restart hit yes and - let it restart
** MAKE SURE YOU DONT UNPLUG YOUR PHONE OR TURN IT OFF, DONT TOUCH IT AT ALL UNTILL THE OPERATION IS COMPLETEY FINISHED**
- when the computer boots up before getting to the logon screen paragon will finish partitioning.
now go here:
http://forum.xda-developers.com/showthread.php?t=468959
download and unzip, rename the folder it extracts to to: mod
now cut and paste the folder: mod that contains the two files to the root of your hard drive (my computer->local disk and paste them there)
if you tried this mod before and was unsuccessful make sure you wipe before you try again, you mountd and init files can be corupted, i would advice a wipe and then reinstallation of JF 1.4.1
- connect you phone to your computer if its not already, go to comand prompt (start->run... type cmd) copy and paste everything after $ into command prompt
$ adb devices
- make sure that you see you device connected
$ mkdir /backup
$ adb pull /system/etc/mountd.conf /backup
$ adb pull /system/init.rc /backup
- you just backed up those two files to a folder named backup thats on the root of your harddrive check and make sure they are there.
$ adb remount
$ adb shell mkdir /system/sd
$ adb shell ls /system
- make sure that you see sd in the list of things that come up
$ adb push /mod/mountd.conf /system/etc/mountd.conf
$ adb push /mod/init.rc /system/init.rc
$ adb shell reboot
$ adb remount
$ adb shell
STEP 2 htc magic users start here
$ busybox df -h
- make sure you see a line ending in /system/sd
$ busybox cp -a /data/app /system/sd
$ rm -r /data/app
$ ln -s /system/sd/app /data/app
$ busybox cp -a /data/app-private /system/sd/app-private
$ rm -r /data/app-private
$ ln -s /system/sd/app-private /data/app-private
if you want to move data
$ busybox cp -a /data/data /system/sd/data
rm -r /data/data
$ ln -s /system/sd/data /data/data
$ adb shell reboot
now you are finished, there are undu instructions on the original post also a way to copy yout /data/data/ (folder where caches and other stuff are saved) to sdcard i advice not if you dont have a class 5 or 6 card or artleast class 4
hope this helps
actually i really appreciate someone made this guide. this was the only guide that actually worked for me i appreciated it. now i finally have 58 mb internal storage to play with thanks a lot.
Do you have any plans on creating an extra noob guide for installing cupcake? Thanks again for all the help. Carguy1973.
Thank you, sometimes it's nice to get just the details too I am very happy to have apps on SD card in 4.5 thanks to ur help.
I have a question about the busybox install..... it worked fine for me, but the busybox PATH is broken after re-boot. After much searching I found this page here but I could not tell if it was solved as the thread sort of petered out after.
The solution was to pull intit.rc and edit it by adding this with no indent
export PATH /system/bin:/data/busybox:$PATH
Click to expand...
Click to collapse
after pushing back the edited init.rc to Android with adb I rebooted but my busybox PATH is still broken and I have to go into an adb shell and re-input "export PATH=/data/busybox:$PATH" every time the device is rebooted just to make busybox work, do you know a solution to this. Thanks again
update
I noticed on haykuro's twitter page that the update he is going to post later today will include busybox.
haitiankid4lyf said:
three not many have Windows 7 and i think its going to suck too ,
Click to expand...
Click to collapse
Windows 7 in based on the windoes vista source but eddited, its 10 times better than Xp Just to let you know
But this thread is a good idea
how do u do all of this on vista??
g1junky said:
how do u do all of this on vista??
Click to expand...
Click to collapse
Vista and xp are basicly the same to do if its based around CMD (Comand prompt for the noobs) So.. Dont worrie, Just follow it the same, Most guides for xp work on vista unless it states it needs an xp specific thing that vista wont let you do.. Dont worrie im on windows 7, Almost everything that works on vista works on xp and vice versa when it comes to CMD
Why don't you add this to the wiki?
Mast3rmatt said:
Why don't you add this to the wiki?
Click to expand...
Click to collapse
Because, The Wikkis old and outdated maybe? I dont think anyone has updated it in a while
I use both Linux and Windows 7 for accessing the phone and they work equally as well for most tasks.
For windows 7 just install the Vista USB Driver (if it is 64 bit, download the Vista 64 bit USB Driver) and either add adb and fastboot to your Windows path... OR you can put the files in Windows/system32.
ben29pickett said:
Because, The Wikkis old and outdated maybe? I dont think anyone has updated it in a while
Click to expand...
Click to collapse
That Might be a idea. Sure its outdated, why doesn't everyone want to build it. Make it strong so that many of the ''noobs'' will stop asking the same question.
pixel-painter said:
I use both Linux and Windows 7 for accessing the phone and they work equally as well for most tasks.
For windows 7 just install the Vista USB Driver (if it is 64 bit, download the Vista 64 bit USB Driver) and either add adb and fastboot to your Windows path... OR you can put the files in Windows/system32.
Click to expand...
Click to collapse
I was gonna say this, But obviously some one beat me to my seccond post
Yeh, What this dude said, Altho i have noticed, Sometimes it does tend to uninstall the driver, If it stops workin reinstall the driver in device manager
Lol at the 5 people who said stop waisting space.. I think the threads a good idea
Mast3rmatt said:
That Might be a idea. Sure its outdated, why doesn't everyone want to build it. Make it strong so that many of the ''noobs'' will stop asking the same question.
Click to expand...
Click to collapse
Maybe a fair point? But i dont belive noobs know what a wikki is let alone even bother to read one, They just want a .exe program like the ziphone program
ben29pickett said:
Maybe a fair point? But i dont belive noobs know what a wikki is let alone even bother to read one, They just want a .exe program like the ziphone program
Click to expand...
Click to collapse
Well, If you haven't seen what allshadow.com wiki is has is becoming then your in for a ride. I was hoping if we can make it sorta like the shadows on allshadow.com. Its really easy to use and has all the information ever needed.(Also Keeps the forums less clutter with TUTs everywhere.
http://wiki.allshadow.com/index.php/Main_Page
ben29pickett said:
I was gonna say this, But obviously some one beat me to my seccond post
Yeh, What this dude said, Altho i have noticed, Sometimes it does tend to uninstall the driver, If it stops workin reinstall the driver in device manager
Click to expand...
Click to collapse
Thanks another kind of related thing.... in Vista and Windows 7 you have to disable Digital Driver Signing. To do this you can hit F8 when you boot into Windows and select it from the Advanced Boot Menu.
The USB Driver will NOT install otherwise, and will NOT work after it is installed unless you do this.
I was reading the threads in the dream forum and found his progress and instructions. I added them to my wiki so they can be continually edited and updated as new methods are found. I did not have any part in this but I noticed that there was not a formal post here about it yet so I decided to make one.
http://android-dls.com/wiki/index.php?title=Magic_Rooting
Please feel free to thank him with some nesquik if you find this helpful!
I was pasting the new instructions here every time they changed but they seem to change often. Please visit the above url to see the current instructions. They were placed on the the wiki so anyone could make edits and changes to them, which is useless if this post needs to be updated each time. I wish vbulletin had some sort of wiki quote that could auto read that page and insert it here for me
Great!
If would be great if this post were a sticky. It also would be nice it the post was updated to include the instructions here as well.
Thanks,
Anders
Just quoting the solution here..
First of all, everyone owes Haykuro a great big thanks for working on this and helping create the solution without even owning a magic. The following is his method just reworded slightly.
1. To gain root access on your HTC Magic/Sapphire you will need to download the magic-root-boot.img zip file and unzip it so that you have boot-new.img in a location you can find.
2. On your device, enter the bootloader by trying one of the following
* Turn off your device and while it is off hold down home while you press power.
* Turn off your device and while it is off hold down volume down while pressing power
3. Make sure your usb cable is inserted and you have Fastboot installed and ready to use.
4. Type the following commands on your desktop (not on the device):
Code:
fastboot boot boot-new.img
5. wait for the following to flash and the phone to reboot:
Code:
downloading 'boot-new.img'... OKAY
Code:
booting... OKAY
6. make sure you have ADB installed and run the following commands from your desktop (not on the device):
Code:
adb push boot-new.img /sdcard/boot-new.img
Code:
adb shell flash_image boot /sdcard/boot-new.img
anyone tried this?
I was going to post the actual text here but the reason for doing it in the wiki is because the methods seem to change very often (the g1 method changed almost daily for a while). I would still recommend viewing the instructions on the wiki before performing the method to be sure they are the same at the time of use.
Full procedure so far!
1. Download boot-new.img.zip from http://www.droiddeveloper.com/hrbuilds/boot-new.img.zip
2. extract boot-new.img to computer.
3. Download recovery-new.img.zip from http://www.droiddeveloper.com/hrbuilds/recovery-new.img.zip
4. extract recovery-new.img to computer.
5. power off device
6. hold BACK+POWER (or VOLUME_DOWN+POWER) to boot into bootloader.
7.
Code:
[b]fastboot boot boot-new.img[/b]
wait for device to boot.
[b]adb push boot-new.img /sdcard/boot-new.img[/b]
[b]adb push recovery-new.img /sdcard/recovery-new.img[/b]
[b]adb shell flash_image boot /sdcard/boot-new.img[/b]
[b]adb shell flash_image recovery /sdcard/recovery-new.img[/b]
[b]adb shell reboot[/b]
you now have root build, and can flash whatever build you like (test keys and all)
First post and wiki updated to show these changes in more detail.
Hi,
I have a french Magic and I test this solution.
I have a problem, when I use the adb shell, I am "root", but when I use a terminal shell on the phone I'm not "root". I use "id" for my test.
How can I do ?
Thanks.
Edit : Ok I found the problem.
I make these commands after in adb shell:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cd system
# cd bin
# cat sh > su
# chmod 4755 su
# sync
# reboot
Thanks
n00b here
can we flash ROMs for dream too or need to wait for magic ROMs ?
it's possible to backup the current firmware of my magic (with or without root), before flashing a new one?
thank you for rooting the magic
thank you for your help
ok i have a big problem when i put (fastboot boot boot-new.img) the phone is restarting every time in htc presentation :S
i put the phone in recovery mode ( fastboot usb ), but then i have the same problem, when i put fastboot boot boot-new.bin, the phone restart always with "boot.bin" , no with "boot-new.bin"...
i try to give the complete path, but always the same result
hello i have a problem.
if i write fastboot boot boot-new.img the console says: the comand "fastboot" is incorrect or bla bla ...
i have a german magic.
sr-ha said:
hello i have a problem.
if i write fastboot boot boot-new.img the console says: the comand "fastboot" is incorrect or bla bla ...
i have a german magic.
Click to expand...
Click to collapse
do you have installed de SDK ¿?
hmm no i dont
should i install it the android sdk 1.5 windows ??
i hve downloadet it but i cant find a icon or sth. to install the sdk
nicola_it said:
it's possible to backup the current firmware of my magic (with or without root), before flashing a new one?
thank you for rooting the magic
thank you for your help
Click to expand...
Click to collapse
nandroid backup 2.1, avaible in recovery mode, doesn't works
sr-ha said:
hmm no i dont
should i install it the android sdk 1.5 windows ??
i hve downloadet it but i cant find a icon or sth. to install the sdk
Click to expand...
Click to collapse
unrar de SDK, and in the "tools" directory you have the ADB and FASTBOOT aplications ( use in the console mode )
Works perfectly with XP, not with vista or win7
sorry but i dont understand what schould i do.
with use in thee console
i think i have to install fastboot or open it. but i cant do nothing of both. if i click on the fastboot exe it blobs open and fast close again.
under windows xp all ok
under windows vista no!!!
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?
This will be the custom recovery beta thread for Micromax a60 recovery. Split from main thread to keep it on topic.
Test Version: Note I do not have this phone and was asked to add this to my recovery lineup.
Directions:
Download this recovery and copy to root of sdcard
see post 162 for latest http://forum.xda-developers.com/showpost.php?p=14393032&postcount=162
download flash_image.zip and unzip and copy to root of sdcard
flash_image.zip
Download this and copy to root of sdcard (do not unzip)
signed_test_flash.zip
commands to flash recovery
from adb shell or terminal (requires root # prompt)
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak (notice this file install-recovery.sh may not be on your device if it gives an error or file not found move on)
flash_image recovery /sdcard/recovery-a60-gnm.img (or name of recovery.img)
sync
then power off device and boot holding "HOME" key
Please test nandroid backup/restore by using the nandroid backup and restore option
Please test usb mass storage in recovery
Please test flashing of signed-test_flash.zip which if successful will place test-flash_file in /system/bin
Please test key mapping if if it is wrong use keycode debugging under other menu and send me keymapping and keycodes. IE. vol-up is keycode 000 etc
Key mapping is Vol-up & Vol-down move selection up & down. Back is backup a menu. Menu key is to select.
This is a test version I'll do full release soon after bugs (if any) are worked out.
For debugging use the move recovery-log to sd option under other and please upload it with feedback.
Appreciate the thanks guys. However, its been nearly 2 days now with no feedback. Can someone try and test to make sure everything is working as intended?
vijkap,His phone does not boot up.
I think now borax12 only having full working mobile.
He will online at above 2:30GMT.
I tested but the text on the recovery was not readable. It was only responding to volume up-down, ( as you have said now only I read the instruction ). I tried to select options with menu key, even a level down text was not readable.
I got an error "mtd: not writing bad block at 0x002c0000" one time I tried
Code:
flash_image recovery /sdcard/recovery-a60-gnm.img
The first time I tried
Code:
cat /sdcard/flash_image > /system/bin/flash_image
I got /sdcard/flash_image: No such file or directory, just added for documentation. Thanks to @drellisdee and others. Should I try once more, pls let me know.
Seems like options are working. My phone reset to default or something when I selected an option (not readable!) and my installed apps are missing
victor px5 said:
Seems like options are working. My phone reset to default or something when I selected an option (not readable!) and my installed apps are missing
Click to expand...
Click to collapse
Sounds like it. Seems you selected data wipe. Please setup adb drivers if you havent already. In recovery do this to test nandroid. Adb shell nandroid-mobile.sh --backup
Can someone verify the resolution of this device ie. Wvga, hvga etc. It need to look at resolution for the ui stuff.
When you say text isnt readable do you mean its not there or to small or jumbled to read. Try to take screen shot with adb shell ddms or adb shell ./ddms
qvga (240x320)
Its Resolution is QVGA.
Sorry for Double post.
Text is not small. Looks like the frequency is not correct, that is my guess.
I too got the same thing. It's unreadble. resolution problem may be. It should be QVGA 240x320. Thats what i think.
Installed this custom recovery through an app called "recovery flasher", which can be downloaded from the market.
Maybe the recovery screen should look like this
drellisdee, please rework on custom recovery to suit qvga. Meanwhile I'm still struggling with my phone. I'll be taking it to micromax support for a fix.
rushank2112 said:
Maybe the recovery screen should look like this
Click to expand...
Click to collapse
Yes that's similar to what its supposed to look like. Can someone give me a nandroid boot.Ingram upload and include a md5sum. If wondering if the rexocovery dump I used got corrupted in the uploading/downloading as it had no md5sum. I've never had a result like that and made 10+ recoveries.
drellisdee said:
Yes that's similar to what its supposed to look like. Can someone give me a nandroid boot.Ingram upload and include a md5sum. If wondering if the rexocovery dump I used got corrupted in the uploading/downloading as it had no md5sum. I've never had a result like that and made 10+ recoveries.
Click to expand...
Click to collapse
Does this link contains any useful stuff for Micromax A60.
http://code.google.com/p/android-roms/downloads/list
rushank2112 said:
Does this link contains any useful stuff for Micromax A60.
http://code.google.com/p/android-roms/downloads/list
Click to expand...
Click to collapse
https://github.com/packetlss/android_bootable_recovery
I think he does not ask that.
He asked boot.img and recovery.img with md5sum.
rushank2112 said:
Does this link contains any useful stuff for Micromax A60.
http://code.google.com/p/android-roms/downloads/list
Click to expand...
Click to collapse
I hope this will work? Sorry for the earlier post. Actually i'm a newbie. I thought i should help.
http://www.receptorblog.com/wordpress/nandroid-gets-working-new-recovery-image/
Sorry guys if i'm making some blunders out here, but my intention is just to help you.
drellisdee said:
Yes that's similar to what its supposed to look like. Can someone give me a nandroid boot.Ingram upload and include a md5sum. If wondering if the rexocovery dump I used got corrupted in the uploading/downloading as it had no md5sum. I've never had a result like that and made 10+ recoveries.
Click to expand...
Click to collapse
drellisdee here is the link. Hope you find it useful.
http://www.multiupload.com/VZPRKLQH3T
vijkap said:
drellisdee here is the link. Hope you find it useful.
http://www.multiupload.com/VZPRKLQH3T
Click to expand...
Click to collapse
Hey dude, the link which you have posted is the link for Stock ROM. I extracted the content of the zip and i found stock boot.img and stock recovery image. Its not a nandroid boot image or recovery image. They are stock images.
THanks to TEAMWIN!!!!!!!!!!!!!!
UPDATE to UPDATE- advanced users only that can understand my instructions please. I tried to make it newb friendly but this takes alot more time than I ever imagined ... (PROPS to ALL DEVS and POSTERS taking the time to share with us that which they spent hours testing!!!!)
so,
also download build.prop
place it in /data/bin
chown to root.root
chmod to 644
you only have to do this once, of course
Now reboot and run (updated and attached here at same time as the build.prop; so if you don't have the build.prop, you need to redownload daddy'stemproot.bat s it has been updated) daddy'stemproot.bat from wherever you downloaded it to.
http://dl.dropbox.com/u/7393616/build.prop
good luck!
UPDATE:
Just wanted to upload what I have been using since the original instructions are out of date.
have tested the following Windows script for 2 days without rebooting and retain full functionality on all root apps.
Instructions:
instead of doing copy/paste, once you have put fre3vo,su,busybox,and sqlite3 into /data/bin and set permisions/ownership, as per original instructions below,
if you have been using another script, just move everything to /data/bin and set permissions/ownership as per below;
and after every reboot, (or after doing the set-up for the first time users)
simply run this script:
(personally, after plugging my phone into my PC, and opening a command prompt, I always do "adb reboot"
then wait until the soft keys at bottom of screen light up (this means the phone is finishing all start up processes but for all extents and purposes the phone has booted) and then double click the file below. the command prompt will open and close itself, when closed, you are good to go until reboot)
Download and save this .bat to anywhere you want and run from anywhere you wish(mine is on my desktop for easy access):
LATEST VERSION Directly below:
http://dl.dropbox.com/u/7393616/daddy%27stemproot.bat
ORIGINAL Instructions:
Just wanted to give back so I will share how I have been getting functional su for on phone term apk and visible /data on root explorer and Superuser prompts for every root app (just because you allow at the prompt and Superuser allows an apk, doesn't mean it will alwasy work; if you open SetCpu more then once a boot it stops working. Bloatware Remover, though given root priveledges, doesn't work, I think becasue when trying to mount system, the apk uses the wrong partition in its script. etc.)
anyways
first get fre3vo, then the latest versions of su, busybox, sqlite3.
via shell from PC:
cd (directory where your 4 files are located)
push above files to /data/local/tmp (follow instructions in other threads)
get temp root via fre3vo
now with temp root do :
adb remount
adb shell mount -oremount,suid /dev/block/mmcblk0p23 /data
adb shell mkdir /data/bin
adb shell chown root.shell /data/bin
adb shell chmod 755 /data/bin
adb push (all 4 files, one at a time, to /data/bin)
adb shell chown root.shell /data/bin/su
adb shell chown root.shell /data/bin/busybox
adb shell chown root.shell /data/bin/sqlite3
adb shell chmod 6555 /data/bin/su
adb shell chmod 4555 /data/bin/busybox
adb shell chmod 755 /data/bin/sqlite3
adb shell chmod 755 /data/bin/fre3vo
now, set up is done, you don't have to do any of that again (unless you mesed up of course)
copy and paste the following lines into shell on PC and viola!
adb shell /data/bin/fre3vo
adb wait-for-device
adb remount
adb shell mount -o remount,suid /dev/block/mmcblk0p23 /data
adb shell ln -s /data/bin/su /system/xbin/su
adb shell ln -s /system/xbin/su /system/bin/su
adb shell ln -s /data/bin/busybox /system/xbin/busybox
adb shell ln -s /data/bin/sqlite /system/xbin/sqlite
adb shell mkdir /system/xbin/bb
adb shell /data/bin/busybox install /system/xbin/busybox /system/xbin/bb/
adb shell sync
So, everytime you reboot,
open a shell on your PC and copy and paste, and then you are free to live with root, until you reboot, and of course with limitations; but I personally can live with this until Fre3dom is complete.
Take your time boys(TEAMWIN) we love you!!!!
hope this helps somebody. I don't have much bandwith to check back to answer questions, but I am confident if any arise, that the community will step up as always. enjoy your root apps
Can somebody please explain to me what he means by latest version of su, busybox, and sqlite3? Apk or like files if anybody would be kind enough to post a zip file of all three?
xSunny said:
Can somebody please explain to me what he means by latest version of su, busybox, and sqlite3? Apk or like files if anybody would be kind enough to post a zip file of all three?
Click to expand...
Click to collapse
You can pull them files out of any rooted android phone.......
Why doesnt the OP just create a script and have it run with one click from the phone??
Thanks..
Sent from my HTC Sensation Z710e using XDA App
Mikey1022 said:
You can pull them files out of any rooted android phone.......
Why doesnt the OP just create a script and have it run with one click from the phone??
Click to expand...
Click to collapse
Commands to pull please?
xSunny said:
Commands to pull please?
Click to expand...
Click to collapse
Try the "Search" command here, if that fails hit Alt+f4.
KillaHurtz said:
Try the "Search" command here, if that fails hit Alt+f4.
Click to expand...
Click to collapse
How about you stop being a prick and answer the question if u dont want to answer then stop running your mouth like a little 2 years begging your mommie for ice cream.. Thank you.. Maybe you should hold the Alt+F4 button =] And dont come attacking me again please..
xSunny said:
How about you stop being a prick and answer the question if u dont want to answer then stop running your mouth like a little 2 years begging your mommie for ice cream.. Thank you.. Maybe you should hold the Alt+F4 button =] And dont come attacking me again please..
Click to expand...
Click to collapse
Wow your general lack of knowledge despite having a long list of devices is disturbing and sad. I guess referring you to the best, and most timely manner to find an answer is an attack ? LOL
xSunny said:
Commands to pull please?
Click to expand...
Click to collapse
adb pull /sdcard/yourfile /whereveryouwantit
or setup an FTP server on your phone (https://market.android.com/details?id=org.swiftp) and download what you're looking for through that.
xSunny said:
How about you stop being a prick and answer the question if u dont want to answer then stop running your mouth like a little 2 years begging your mommie for ice cream.. Thank you.. Maybe you should hold the Alt+F4 button =] And dont come attacking me again please..
Click to expand...
Click to collapse
KillaHurtz said:
Wow your general lack of knowledge despite having a long list of devices is disturbing and sad. I guess referring you to the best, and most timely manner to find an answer is an attack ? LOL
Click to expand...
Click to collapse
What is it with this forum??!??!?! I used to have a HD2 and the forum there was awesome! So many helpful and friendly people creating a productive and welcoming community! But here in the Sensation forum every second thread is full of people *****ing at each other and behaving like children! What the hell is wrong with you guys???
KillaHurtz said:
Wow your general lack of knowledge despite having a long list of devices is disturbing and sad. I guess referring you to the best, and most timely manner to find an answer is an attack ? LOL
Click to expand...
Click to collapse
Lmao.. Thats all im going to say to end this conversation anyways thanks for posting the commands to pull via adb
How do you push more than one file at a time?
adb push (all 4 files, one at a time, to /data/bin)
Click to expand...
Click to collapse
Thanks
Thanks Daddyroot ! the commands have really worked for me. Now I have a sensation with Temp root till I restart. All other scripts in the forum was not helping me.
Best solution I found so far. Not losing root till reboot anymore.
A++ would install again
Really glad to be able to give back to the community.
I wish I had more time when I posted this to check back and reply but I'm a single parent and time is short. After playing for a couple hours and finally seeing and being able to edit the /data folder, I knew it would be with it to make the time if I could help just one person to not waste the time figuring out what I could share. Nothing quite like the feeling you get on an unrooted phone when you first see the superuser prompt to allow or deny!!!
Thank you all who hit the thanks button!
And God bless TEAMWIN and (insert your favorite dev here)!!!
I will try to check back at least once a day...
Wisefire said:
How do you push more than one file at a time?
Click to expand...
Click to collapse
You don't... that's why he said "ONE, at a time"...