It's a big operation if you never did it
Upload your boot.img (get it via nandroid) and I'll root it and repack it in a update.zip so you just have to apply it.
Just to confirm : Your Magic has "with google" on the back cover, right?
It's a big operation if you never did it
Upload your boot.img (get it via nandroid) and I'll root it and repack it in a update.zip so you just have to apply it.
Just to confirm : Your Magic has "with google" on the back cover, right?
Then its very kind of you Amon_RA. Thank you Can you tell me in a short description how youre doing it?
Here's my boot.img http://www.usb3.no/boot.img
No, its the one with HTC on the back cover...
Can you tell me in a short description how youre doing it?Here's my boot.img http://www.usb3.no/boot.img
No, its the one with HTC on the back cover...
Then its very kind of you Amon_RA. Thank you
Here's my boot.img http://www.usb3.no/boot.img
No, its the one with HTC on the back cover...
Download this, rename to update.zip, copy it to your SDcard, and update it via RAv1.0 recovery.
I unpacked your boot.img, set ro.secure=0,ro.debuggable=1 and
persist.service.adb.enable=1 in default.prop, repacked boot.img, made an update.zip, signed it, and uploaded it.
I did NOT add busybox, SU app, etc... I'll leave that up to you now that you have root.
I followed your instructions on my Google Ion phone:
This is only thing that happned is that phone turns black, and got stuck. Had to put out the battery to start it again.
Then I tried to start it with HOME + Power.. And it's the same old menu.
Do I really need to flash the SPL? And in that case, how do I do that?
Edit:
Ok.. I discovered that the img file was corrupted (a few kb was missing).. despite downloading it twice.
Today it worked fine though.
Could you please make it habit to add MD5/CRC strings when uploading roms/systems files.
Thank you.
Edit 2:
Now when I flashed it, after entering "adb shell flash_image recovery /sdcard/recovery-RAv1.0H.img" it gave me:
Is this normal?
However, when I then rebooted into HOME+Power, the modded recovery seems to be there permanently... Should I expect it to work properly even though the error messages?
This is only thing that happned is that phone turns black, and got stuck. Had to put out the battery to start it again.
Then I tried to start it with HOME + Power.. And it's the same old menu.
Do I really need to flash the SPL? And in that case, how do I do that?
Edit:
Ok.. I discovered that the img file was corrupted (a few kb was missing).. despite downloading it twice.
Today it worked fine though.
Could you please make it habit to add MD5/CRC strings when uploading roms/systems files.
Thank you.
Edit 2:
Now when I flashed it, after entering "adb shell flash_image recovery /sdcard/recovery-RAv1.0H.img" it gave me:
Code:
mtd: erase failure at 0x000c0000 (I/O error)
mtd: erase failure at 0x000c0000 (I/O error)
mtd: skipping write block at 0x000c0000However, when I then rebooted into HOME+Power, the modded recovery seems to be there permanently... Should I expect it to work properly even though the error messages?
Last edited:
Hi
First of all, excuse my bad english...
I got a strange problem with my sdcard, after I successfully replaced my recovery.img as specified in this thread, when I boot the recovery (home+power) nandroid can't mount /dev/block/mmcblk0 (no such file or directory) on first time, If I select the nandroid backup menu again, it's working.
The first time I'd used nandroid to backup my device (it was rogers stock non rooted), It was working on the first attempt but I was using fastboot to load the recevery.img file. I retried that route with fastboot but now I always get that error on my first attempt.
Any idea?
First of all, excuse my bad english...
I got a strange problem with my sdcard, after I successfully replaced my recovery.img as specified in this thread, when I boot the recovery (home+power) nandroid can't mount /dev/block/mmcblk0 (no such file or directory) on first time, If I select the nandroid backup menu again, it's working.
The first time I'd used nandroid to backup my device (it was rogers stock non rooted), It was working on the first attempt but I was using fastboot to load the recevery.img file. I retried that route with fastboot but now I always get that error on my first attempt.
Any idea?
I find I get that if I don't give the device enough time to fully boot. Trying waiting a full minute or two and see what happens.
@ Amon-ra
-rwxrwxrwx 1 0 0 2396160 Jun 27 19:15 recovery-RAv1.0H.img
/sdcard # flash_image recovery /sdcard/recovery-RAv1.0H.img
/sdcard #
How can I verify if all works fines ?
Witch mod can I install on my Magic with hero interface please ?
Code:
Can you try this and list the output :
1. Boot the device in fastboot mode.
2. Connect the device to your machine over USB.
3. $fastboot boot recovery-RAv1.0H.img
Wait for a minute or two..
$adb shell mount -a
Ignore the failed mounts...
$adb push recovery-RAv1.0H.img /system/recovery.img
$adb push recovery-RAv1.0H.img /sdcard/recovery-RAv1.0H.img
$adb shell
#cd /sdcard
#ls -l
See if you can see recovery-RAv1.0H.img on your sdcard.
If you see it then :
#flash_image recovery /sdcard/recovery-RAv1.0H.img-rwxrwxrwx 1 0 0 2396160 Jun 27 19:15 recovery-RAv1.0H.img
/sdcard # flash_image recovery /sdcard/recovery-RAv1.0H.img
/sdcard #
How can I verify if all works fines ?
Witch mod can I install on my Magic with hero interface please ?
Last edited:
Is there any reason to use the command Amon_RA gave of 'adb shell flash_image recovery /sdcard/recovery-RAv1.0H.img' instead of 'flashboot flash recovery recovery-RAv1.0H.img'? Just trying to wrap my head around some of the differences between various flashing steps I see around.
I have followed all the given instructions provided in this forum. i used daldroid update and recovery.img. that replaced stock rogers rom with a generic htc rom. this rom has no rogers apps and provides access with app to paid apps on the market place. i then saw this thread and ... In the end, i did the hole su, recovery flashing, etc. I just want to know, how do you know when this thing is rooted? i'm able to flash different roms, i can fastboot recovery img without having it installed on my memory card. just need someone to clarify a few things. i have read and read. saffire thread is lacking noob section as many people had a g1 and thus have a yr of experience. thanks in advance.
Last edited:
after flashing this last command: $adb shell flash_image recovery /sdcard/recovery-RAv1.0H.img. it just returns to cd:\android\tools. does that mean i was successful? the other commands gave some digits and stuff.
When i boot, i was told to press power and home button at same time. \if it boots to your image, you have succeeded.
tried it and it works. so i answered my own ?
can i reinstall my nandroid backup from this mode?
thanks.
edit: answered my own ?'s
When i boot, i was told to press power and home button at same time. \if it boots to your image, you have succeeded.
tried it and it works. so i answered my own ?
can i reinstall my nandroid backup from this mode?
thanks.
edit: answered my own ?'s
Last edited:
I tried to flash recovery image from terminal on phone doing it like this:
flash_image recovery sdcard/recovg.img <----- changed name to a shorter one
Get the following error:
mtd_read error at 0x(lots of numbers) (out of memory)
any clue why this happens? Tried different recovery images.
My computer doesn't discover the phone properly in fastboot mode (adb devices) so no contact that way.
Have the .2005 engeneering spl and phone is rooted.
Hope anyone can help me.
flash_image recovery sdcard/recovg.img <----- changed name to a shorter one
Get the following error:
mtd_read error at 0x(lots of numbers) (out of memory)
any clue why this happens? Tried different recovery images.
My computer doesn't discover the phone properly in fastboot mode (adb devices) so no contact that way.
Have the .2005 engeneering spl and phone is rooted.
Hope anyone can help me.
any one got this flashed and working on PVT32A running Fatal1tys 1.2 Hero rom (modded for PVT32A by skittleguys)? I can flash it and all seems well, but back+power gives me the old skateboarding recovery. Also I just tried to go into HBOOT-mode and it gave me a bunch of errors saying a bunch of files where gone/wrong. What can I do? (I fastbooted this recovery and checked /system/ for recovery.img but there is none there, even tho init.rc states it flashes /system/recovery.img) I'm running engineering SPL, FYI.
:edit: The files shown as missing when entering HBOOT mode are named something like this SAPPDIAG.ZIP SAPPDIAG2.NBH SAPPIMG.NBH
Okay so I just learnt how to boot into recovery mode, I thought fastboot = recovery, home + power was the solution!
:edit: The files shown as missing when entering HBOOT mode are named something like this SAPPDIAG.ZIP SAPPDIAG2.NBH SAPPIMG.NBH
Okay so I just learnt how to boot into recovery mode, I thought fastboot = recovery, home + power was the solution!
Last edited:
You wouldn't by any chance be running ubuntu jaunty? If so there seems to be some problem with the rules files.
http://groups.google.com/group/android-developers/msg/5c679d04aa6713d3
Solves it tho. If this is not the case, I can only hope you'll get it back up.
G'day mate- i don't actually have my magic yet- i am just researching all this as much as possible before i get it (as i did my G1 back in january)....
Have you thought about pimping out the recovery image like Cyanogen has the G1 recovery? http://xdaforums.com/showthread.php?t=523558
thanks for all your awesome work....
Have you thought about pimping out the recovery image like Cyanogen has the G1 recovery? http://xdaforums.com/showthread.php?t=523558
thanks for all your awesome work....
Well, 50 minutes with my phone and it's bricked. I don't mean, a little bit either. It only boots to the htc magic screen, vibrates once, then does nothing. I cannot enter bootmode by any means. I guess this is what a bricked magic is really like. Too bad there're no unbrickers.
Caid.
444
Caid.
444
Will Nadroid 2.1.1 be able to restore files made with Nandroid 2.1?
Great work with this recovery image.
Great work with this recovery image.
thanks Amon_RA,
flashed recovery v1.1 just fine using your steps. However, in your steps:
$adb push recovery-RAv1.1H.img /system/recovery.img
is that really necessary? I dont see the point in that since dont you need to just push the recovery on the sd and then flash? besides, it fails every time i try to attempt it so i just moved on and it works.
flashed recovery v1.1 just fine using your steps. However, in your steps:
$adb push recovery-RAv1.1H.img /system/recovery.img
is that really necessary? I dont see the point in that since dont you need to just push the recovery on the sd and then flash? besides, it fails every time i try to attempt it so i just moved on and it works.
I was under the impression that you type in the $fastboot commands in the ADB command prompt in windows while the phone is in fastboot mode. Although when I type "ADB Devices" in ADB it will not find the device. Although in the OS itself ADB recognizes the device. What am I doing wrong?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
13This is a custom recovery based on Cyanogen's recovery source with a lot of things added by me. The purpose of this recovery is to avoid using adb by accessing all features directly from the menu.
All source code is available at github.
This recovery if for the HTC Magic/MT3G only, if you have an :
- HTC Dream/G1 you should go here.
- HTC Hero you should go here.
- HTC Sprint Hero you should go here.
- HTC Eris you should go here.
- HTC Tattoo you should go here.
- HTC Nexus One you should go here.
Important notes
- 32A users with SPL 1.76.x should flash the Hero version! (Will be updated to v1.7.0 soon!!)
- Always check recovery.log before posting your issues!
You can do this by doing :- "cat /tmp/recovery.log" OR "cat /cache/recovery/log" right after you had the issue.
- Use the "move log to sd" option in the "others" menu right after you had the issue. This will move the log to /sdcard/recovery.log so you can easily open it with a text editor.
Features
Use the trackball (up+down) to navigate through the menu, press the trackball to select items.
You can also use the volume keys (vol-up + vol-down) to navigate, and the CALL-ANSWER key to select items (in case your trackball is broken).
- full ADB access in recovery mode
- Busybox v1.15.3
- HW-Key navigation (volume keys + CALL-ANSWER) option
- Extended menu (with keyboard-shortcuts):
- Reboot system now :: reboot your phone
- USB-MS Toggle :: enable/disable USB mass storage (use when the phone is connected to your PC)
- Backup/Restore (recovery partition not included!)
- Nand backup :: Make a Nand backup
- Nand + ext backup :: Make a Nand + ext backup
- Nand restore :: Restore a Nand backup
- BART backup :: Make a BART backup (Nand + ext)
- BART restore :: Restore latest BART backup
- Bck Google files :: Makes a backup of the Google proprietary system files in /cache/google
- Rst Google files :: Restores the Google proprietary system files from /cache/google
- Flash zip from sdcard :: Flash a zip update file from your sdcard
- Wipe
- Wipe data/factory reset :: Wipe /data and /cache
- Wipe cache :: Wipe /cache only
- Wipe Dalvik-cache :: Wipe /cache/dalvik-cache
- Wipe SD:ext partition : Wipe the ext partition on your sdcard
- Wipe battery stats : Wipe the battery stats in /data
- Wipe rotate settings : Wipe the sensor settings in /data
- Partition sdcard
- Partition SD :: Interactive SD partitioning
- Repair SD:ext :: Repair the ext partition
- SD:ext2 to ext3 :: Convert ext2 to ext3
- SD:ext3 to ext4 :: Convert ext3 to ext4
- Other
- Fix apk uid mismatches :: Does extacly that
- Move recovery.log to SD :: Moves the recovery log file to your sdcard. (Use when you want more detailed recovery log information)
- Power off :: Powers off your phone
- Scripts available via adb :
- Nandroid v2.2.1 : enter "nandroid-mobile.sh" to start.
- BART v1.3.1 (Backup and Restore Tool) : enter "utility" or "u" to start.
- switchrom.sh V1.1 : enter "switchrom" to start.
- sdparted v0.6 : enter "sdparted" to start.
Install
- There are several ways to install a custom recovery, choose the one that suits you most (I probably forgot a few).
- You don't need to enter "mount -a" if your partitions are already mounted.
- Use the H/G version if your Magic is HTC branded (PVT 32A board)/Google branded (PVT 32B board).
via fastboot :
- Requires engineerings SPL!
Code:Copy recovery-RA-sapphire-v1.7.0G.img to a location where fastboot can find it. Boot your G1 into fastboot mode (boot while holding BACK) Connect your G1 via usb to your pc/mac/... fastboot devices (to make sure that fastboot "sees" your device) fastboot flash recovery recovery-RA-sapphire-v1.7.0G.img
via adb :
- Requires a custom recovery (with test-keys) like Cyanogen's v1.4 or my previous recovery
- Do NOT follow these steps from a terminal application on the phone, make sure that you've booted into a custom recovery first!!!
Code:Copy recovery-RA-sapphire-v1.7.0G.img to the root of your sdcard Boot into your current custom recovery (boot while holding HOME) Connect your G1 via usb to your pc/mac/... adb shell #mount -a (this can give back an error if you don't have an ext partition, don't worry about it and just proceed) #flash_image recovery /sdcard/recovery-RA-sapphire-v1.7.0G.img
via terminal application installed on the phone :
- Requires root
[*]DO NOT use this method with CM5.0.7, there are currently some memory issues while flashing, use the above methods (preferably the fastboot method) instead until the issue is fixed in CM5.0.7!
Code:Copy recovery-RA-sapphire-v1.7.0G.img to the root of your sdcard start the terminal app #flash_image recovery /sdcard/recovery-RA-sapphire-v1.7.0G.img
Download
- ALWAYS check the md5sum to make sure the zip isn't corrupted.
- Click on the Mirror-link if you don't like rapidshare
- Use the H/G version if your Magic is HTC branded (PVT 32A board)/Google branded (PVT 32B board).
- recovery-RA-sapphire-v1.7.0G.img - MD5Sum: 8b3b5ff90575eba0c5bfc13c0fa6b8ea
- recovery-RA-sapphire-v1.7.0G-cyan.img - MD5Sum: 8846b53e3184d688e3e8a628ad81074f
- recovery-RA-sapphire-v1.7.0H.img - MD5Sum: f78bc0ff51f233666a9a5f72b56aabec
- recovery-RA-sapphire-v1.7.0H-cyan.img - MD5Sum: 1ed8363e05b3515d7f976a8764cfad51
Change-log :
v1.7.0
Code:- Fixed some minor bugs - Recovery and scripts use /sd-ext instead of /system/sd as mountpoint to support the new apps2sd method (implemented mostly by Chris Soyars) - Added an option to backup/restore Google proprietary Android system files (backuptool.sh written by Cyanogen) - Removed "move apps2sd"-option as it's not needed anymore with the new apps2sd method - Updated BART to v1.3.1 (updated by Dumfuq to support /sd-ext) - Added a wipe cache only option - Nandroid now backups/restores /cache again by default - Dalvik-cache wipes /cache/dalvik-cache now - Removed SDCARD: prefix in output when chosing zip to flash - Added Cyan version (There's no difference with the normal version, only the wallpaper and textcolor changed)
v1.6.2
Code:- Added power off menu item - New unyaffs binary patched by Koushik Dutta and Packetlss to fix the "losing root"-issue and incorrect file-time after a Nandroid restore - New dump_image binary (by Brainaid) patched by Packetlss to fix the "bad blocks"- Nandroid restore issue. [COLOR="Red"][B](This will not fix old corrupted Nandroid backups! Please make new backups!!)[/B][/COLOR] - New mkyaffs2image binary - New flash_image binary - Updated busybox to v1.5.3 - Nandroid menu options will NOT backup or restore recovery, cache, misc, splash1+2 (to avoid issues) - Fixed wipe option not wiping when ext was not present - Created carebear versions after the idea of packetlss - Switched the Nexus logo to a Green Carebear with Nexus One logo (Thanks Montalbert!)
Special thanks to :
- packetlss for all the hours of support and awesome coding skills, THANKS man ^^, donate to Haiti
- Koushik Dutta for the unyaffs binary code fix and help ^^
- pensive for adding awesome features to Nandroid
- Bkmo for his utility script!
- Devsk for his switchrom script!
- 51dusty for his sdparted script!
- k4str0 for his fix_permissions v2.03 update.
- Devsk, Dumfuq, Overground for creating BART
- Androidappcritics for the reboot idea in BART
- rikupw for the ideas and toggle_ums script.
- MLIGN for the idea to port my recovery to the Dream.
- http://theunlockr.com for all the awesome video’s ^^
- JesusFreke for his awesome JFv1.43's recovery , donate
1I think its because the stock spl has signiture checking on. Change the spl though and...1But there says "Only flash recovery-RA-hero-v1.6.2.img if you have a 32A Sapphire with 6.35.x.x radio and 1.76.x SPL, recovery-RA-hero-v1.7.0.1.img will NOT boot! I'll create a new Sapphire version soon."
Thanks.
