Does this allow for superuser? I want my tethering back. Almost makes me wish I didn't sell my ADP1. Almost.
The Ion recovery image on the HTC site indeed contains a G1 RLE...
I recompiled the recovery myself and added the green HTC logo
, so no it didn't came that way.Ya the Rooted Magic Build may include SU access + Busybox flash it & use ur magic like adp with su access...
So is SU confirmed in this recovery image? And will I be able to use WiFi Tether for Root again, or will I need SU Whitelist?
Hello,
I have a small problem (PVT 32A board).
- I do the "Try it out WITHOUT making changes to your device (NO flashing):" and all works fine.
- I flash my SPL with de 32A file. No problem.
After that I reboot on fastboot mode and do the step for "Flash it permanently"
1. Boot the device in fastboot mode. (OK)
2. Connect the device to your machine over USB. (OK)
3. $fastboot boot recovery-RAv1.0H.img (OK)
Wait for a minute or two.. (OK)
$adb shell mount -a (OK)
Ignore the failed mounts... (OK)
$adb push recovery-RAv1.0H.img /system/recovery.img (OK)
$adb push recovery-RAv1.0H.img /sd-card/recovery-RAv1.0H.img (OK)
$adb shell flash_image recovery /sd-card/recovery-RAv1.0H.img (NOT OK)
I receive in return "/sbin/sh: flash_image: not found"
Anyone can Help me please ?
Thanks a lot,
Arcenik
PS: Sorry for my bad english .
I have a small problem (PVT 32A board).
- I do the "Try it out WITHOUT making changes to your device (NO flashing):" and all works fine.
- I flash my SPL with de 32A file. No problem.
After that I reboot on fastboot mode and do the step for "Flash it permanently"
1. Boot the device in fastboot mode. (OK)
2. Connect the device to your machine over USB. (OK)
3. $fastboot boot recovery-RAv1.0H.img (OK)
Wait for a minute or two.. (OK)
$adb shell mount -a (OK)
Ignore the failed mounts... (OK)
$adb push recovery-RAv1.0H.img /system/recovery.img (OK)
$adb push recovery-RAv1.0H.img /sd-card/recovery-RAv1.0H.img (OK)
$adb shell flash_image recovery /sd-card/recovery-RAv1.0H.img (NOT OK)
I receive in return "/sbin/sh: flash_image: not found"
Anyone can Help me please ?
Thanks a lot,
Arcenik
PS: Sorry for my bad english .
Oops, it's sdcard and not sd-card ! Thanks for noticing!
Try this :
$adb push recovery-RAv1.0H.img /sdcard/recovery-RAv1.0H.img
$adb shell flash_image recovery /sdcard/recovery-RAv1.0H.img
Is there a way to ($fastboot pull /system/recovery.img) ?
I need to be able to unroot this Mytouch 3G before I return it and put back the original recovery.img
I need to be able to unroot this Mytouch 3G before I return it and put back the original recovery.img
@ Amon_ra I have always the same problem.
$ adb shell flash_image recovery /sdcard/recovery-RAv1.0H.img
/sbin/sh: flash_image: not found
SO, it's not a problem with the sd-card to sdcard.
thanks
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
Weird....
I have a 32A board and I just flash the recovery img mentioned here. Works fine but I do a ./adb shell and then a cat /proc/meminfo and I get this:
MemTotal: 197144 kB
Shouldnt this be 288mb ?
EDIT: ok found the post about this
I have a 32A board and I just flash the recovery img mentioned here. Works fine but I do a ./adb shell and then a cat /proc/meminfo and I get this:
MemTotal: 197144 kB
Shouldnt this be 288mb ?
EDIT: ok found the post about this
Last edited:
I can get it to do all of these steps but they don't seem to stay applied. I did have to use some extra steps to get su access:
./adb push ./bin/su /system/xbin/su
./adb shell mount -a
./adb shell chmod 4755 /system/xbin/su
but once I've done that I can definitely access flash_image but upon reboot it still goes to the standard recovery boot screen. Is there some sort of commit or sync command I'm missing?
Edit 1:
According to this wiki 'Note: You must place the recovery image at /system/recovery.img. the init.rc boot script automatically flashes the recovery partition with that file every time you boot up the phone.'
So do I need to replace /system/recovery.img with recovery-RAv1.0H.img (obviously renamed)?
Last edited:
Correct, be aware that some custom ROMs might have changed this location (Like JF releases)... What's your current ROM and Magic model?
That's what you do in this step :
$adb push recovery-RAv1.0H.img /system/recovery.img
I did manage to flash the recovery to my phone. I had to update to SPL HBOOT-1.33.2005 (SAPP10000). That went well, you made me look like a pro
But im not getting root access via "adb root"...
root access in recovery mode or once your mobile is booted?
Oh, I didn't know that. I looked in the init.rc file but didn't see anything obvious (but I'm not sure of what I'd be looking for anyways). Right now I'm running nk02's ION Multi5 v4 repack. I've flashed my Rogers Magic SPL to the Engineering SPL HBOOT-1.33.2005. It was previously the following:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP50000)
CPLD-12
RADIO-3.22.20.17
MAY 8 2009, 21:02:32
so now it reads:
SAPPHIRE UNKNOWN 32A ENG S-OFF H
HBOOT-1.33.2005 (SAPP50000)
CPLD-12
RADIO-3.22.20.17
Apr 20, 2009, 15:30:43
Of course, I should have noticed that.
It's not the end of the world that it's not working. I can still get the ROM loaded, and I can still get root access. But it would be more convenient
Thanks for all the work you've done, and I appreciate the reply.
Last edited:
In recovery mode. All i get from ADB root is "Error:Closed"
HTML:
X:\Android\android-sdk-windows-1.5_r2\tools>adb devices
List of devices attached
HT95WKF08185 recovery
X:\Android\android-sdk-windows-1.5_r2\tools>adb root
error: closed
X:\Android\android-sdk-windows-1.5_r2\tools>
Last edited:
Just do "adb shell" and you will see the # root sign.
This recovery does NOT give your root when you fully boot your device, it's just a tool to make you backup your device via Nandroid.
If you want to have root on your device you'll need to enable root in your boot.img nandroid backup and reflash it.
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.
