I'm running 1.7.0.1 hero on my magic right now, hope you don't mind amon_ra , I used my kernel with your sources, works very well compared to 1.6.2.
This is for 6.35 radio magic only http://www.multiupload.com/W03UU3NO6P
Last edited:
TMobile MyTouch 3G on Wind Mobile in Canada
Hi there,
I am stuck in the repeative Google Activation screen on my TMobile MyTouch3G. Add to that it seems that I can't get data on my Wind Mobile SIM.
My question is: is it possible to root the phone in this state? I haven't made a goldcard or backed up my phone?
Probably dumb questions, but I have start somewhere in my rooting education.
Thanks,
Andrew
Hi there,
I am stuck in the repeative Google Activation screen on my TMobile MyTouch3G. Add to that it seems that I can't get data on my Wind Mobile SIM.
My question is: is it possible to root the phone in this state? I haven't made a goldcard or backed up my phone?
Probably dumb questions, but I have start somewhere in my rooting education.
Thanks,
Andrew
Ok I have a HTC magic from T-Mobile but am using another provider CLARO PR and its run their 3G network on 1900/850 so is there a radio that I can install on my magic so the 3G works???
new OTA question
I was wondering which recovery will work for the MT3G 1.0 after the SPL/radio/boot OTA update. I tried clockwork recovery and it failed, so my guess is the mem map was reconfigured. Any ideas?
I was wondering which recovery will work for the MT3G 1.0 after the SPL/radio/boot OTA update. I tried clockwork recovery and it failed, so my guess is the mem map was reconfigured. Any ideas?
Hi Amon_RA, hope you can help us out here.
I've recently installed the T-mobile OTA 2.2.1 on my Magic 32B. As you probably aware it also flashes a new SPL and radio. Though the ROM works great and I've managed to root it without incident (SuperOneClick method) I'm yet to find a way to have your custom recovery stick on recovery boot. I have managed to flash 1.7 recovery ok and boot into it but everytime i reboot and reboot again into recovery it just reverts back to stock. quite annoying and i'm failing to understand why this is.
To install and boot into your recovery I've copied recovery to the root of the sdcard, then copied flash_image to both:
/data/local/tmp
(my first method, using:
cd /data/local/tmp
chmod 777 ./flash_image
./flash_image recovery /sdcard/recovery.img)
as well as to:
/system/bin
(second method, using:
cd /system/bin
./flash_image recovery /sdcard/recovery.img)
Afterwards I've also tried flashing through terminal (#flash_image recovery /sdcard/recovery.img) as well as through adb from inside your recovery.
Altough all of this have worked well - when i do reboot recovery it does boot into your custom recovery - if i reboot and then reboot again into recovery it reverts to the stock recovery v.3
Any ideas or suggestions on how to make the recovery stick in the system? Also, and i still haven't gone there yet, but what do you think it will be the best method to flash an eng. SPL and corresponding radio with the current settings? I'm thinking that it would probably be the same method as for the myTouch 1.2 (as it uses the same SPL) with the goldcard method but I'm not entirely sure. Suffice to say that fastboot commands are no go - "permissions denied".
Any help greatly appreciated and thanks in advance.
EDIT: Got ezterry's help here and custom recovery sticks in the system once removed /system/etc/install-recovery.sh
would still appreciate your input on how to flash eng. SPL and corresponding radio back to the device. Reckon it is possible to do it via custom recovery but would prefer to be sure before attempting it. I used to do both at the same time via fastboot but not possible with the current hboot.
I've recently installed the T-mobile OTA 2.2.1 on my Magic 32B. As you probably aware it also flashes a new SPL and radio. Though the ROM works great and I've managed to root it without incident (SuperOneClick method) I'm yet to find a way to have your custom recovery stick on recovery boot. I have managed to flash 1.7 recovery ok and boot into it but everytime i reboot and reboot again into recovery it just reverts back to stock. quite annoying and i'm failing to understand why this is.
To install and boot into your recovery I've copied recovery to the root of the sdcard, then copied flash_image to both:
/data/local/tmp
(my first method, using:
cd /data/local/tmp
chmod 777 ./flash_image
./flash_image recovery /sdcard/recovery.img)
as well as to:
/system/bin
(second method, using:
cd /system/bin
./flash_image recovery /sdcard/recovery.img)
Afterwards I've also tried flashing through terminal (#flash_image recovery /sdcard/recovery.img) as well as through adb from inside your recovery.
Altough all of this have worked well - when i do reboot recovery it does boot into your custom recovery - if i reboot and then reboot again into recovery it reverts to the stock recovery v.3
Any ideas or suggestions on how to make the recovery stick in the system? Also, and i still haven't gone there yet, but what do you think it will be the best method to flash an eng. SPL and corresponding radio with the current settings? I'm thinking that it would probably be the same method as for the myTouch 1.2 (as it uses the same SPL) with the goldcard method but I'm not entirely sure. Suffice to say that fastboot commands are no go - "permissions denied".
Any help greatly appreciated and thanks in advance.
EDIT: Got ezterry's help here and custom recovery sticks in the system once removed /system/etc/install-recovery.sh
would still appreciate your input on how to flash eng. SPL and corresponding radio back to the device. Reckon it is possible to do it via custom recovery but would prefer to be sure before attempting it. I used to do both at the same time via fastboot but not possible with the current hboot.
Last edited:
I'm running 1.7.0.1 hero on my magic right now, hope you don't mind amon_ra , I used my kernel with your sources, works very well compared to 1.6.2.
This is for 6.35 radio magic only http://www.multiupload.com/W03UU3NO6P
Boody hell!! Nice job
Bart as I told you on twitter, 1.7 is not cleaning dalvik cache
# mount -a
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or directory
/ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 95.9M 0 95.9M 0% /dev
/dev/block/mtdblock4 80.0M 33.4M 46.6M 42% /cache
/dev/block/mmcblk0p1 7.4G 2.6G 4.8G 35% /sdcard
/dev/block/mtdblock3 90.0M 83.2M 6.8M 92% /system
/dev/block/mtdblock5 295.8M 176.9M 118.8M 60% /data
and now after using wipe cache and dalvik-cache
/ # du -chs data/dalvik-cache/
29.6M data/dalvik-cache/
29.6M total
/ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 95.9M 0 95.9M 0% /dev
/dev/block/mtdblock4 80.0M 1.1M 78.9M 1% /cache
/dev/block/mtdblock3 90.0M 83.2M 6.8M 92% /system
/dev/block/mtdblock5 295.8M 176.9M 118.8M 60% /data
/dev/block/mmcblk0p1 7.4G 2.6G 4.8G 35% /sdcard
I need to manually rm it
Thanks in advance
# mount -a
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or directory
/ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 95.9M 0 95.9M 0% /dev
/dev/block/mtdblock4 80.0M 33.4M 46.6M 42% /cache
/dev/block/mmcblk0p1 7.4G 2.6G 4.8G 35% /sdcard
/dev/block/mtdblock3 90.0M 83.2M 6.8M 92% /system
/dev/block/mtdblock5 295.8M 176.9M 118.8M 60% /data
and now after using wipe cache and dalvik-cache
/ # du -chs data/dalvik-cache/
29.6M data/dalvik-cache/
29.6M total
/ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 95.9M 0 95.9M 0% /dev
/dev/block/mtdblock4 80.0M 1.1M 78.9M 1% /cache
/dev/block/mtdblock3 90.0M 83.2M 6.8M 92% /system
/dev/block/mtdblock5 295.8M 176.9M 118.8M 60% /data
/dev/block/mmcblk0p1 7.4G 2.6G 4.8G 35% /sdcard
I need to manually rm it
Thanks in advance
Bart as I told you on twitter, 1.7 is not cleaning dalvik cache
# mount -a
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or directory
/ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 95.9M 0 95.9M 0% /dev
/dev/block/mtdblock4 80.0M 33.4M 46.6M 42% /cache
/dev/block/mmcblk0p1 7.4G 2.6G 4.8G 35% /sdcard
/dev/block/mtdblock3 90.0M 83.2M 6.8M 92% /system
/dev/block/mtdblock5 295.8M 176.9M 118.8M 60% /data
and now after using wipe cache and dalvik-cache
/ # du -chs data/dalvik-cache/
29.6M data/dalvik-cache/
29.6M total
/ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 95.9M 0 95.9M 0% /dev
/dev/block/mtdblock4 80.0M 1.1M 78.9M 1% /cache
/dev/block/mtdblock3 90.0M 83.2M 6.8M 92% /system
/dev/block/mtdblock5 295.8M 176.9M 118.8M 60% /data
/dev/block/mmcblk0p1 7.4G 2.6G 4.8G 35% /sdcard
I need to manually rm it
Thanks in advance
Don't mount manually when you use the menu to wipe...
Or you use the menu to do stuff, or you do everything manually via adb, but don't mix both, this can give mount issues.
I did the following and it works just fine :
1. Unplug charger/usb cable
2. boot in recovery mode
3. select wipe, select wipe Dalvik-cache, and wait for it to finish
4. plug usb cable
5. adb shell
6. cd /data
7. ls => Notice that the whole dalvik-cache directory is erased
8. cd /cache
9. ls => Notice that the whole dalvik-cache directory is erased
Conclusion : wipe cache works fine
sorry Bart, but not true.
/data is not mounted so there is nothing to see there. ofc that would show as clean.
If you mount /data and then cd to it, i'm almost sure you will see still data in /data/dalvik-cache
i'll have to reboot and test dough.
Ah crap you are right, I was testing it on my Nexus and I notice that I didn't update the wipe script in v1.7.0 for the sapphire!
I'll post an updated version soon.
Thanks for reporting!
Last edited:
There is a full functional recovery-AR-magic+-1.7.0.1
for the HTC Magic 32A 6.35 radio and 1.76 spl
on this thread:
http://xdaforums.com/showthread.php?t=816345
i have not tested it. but i will as soon as my magic is back from the repair center.
for the HTC Magic 32A 6.35 radio and 1.76 spl
on this thread:
http://xdaforums.com/showthread.php?t=816345
i have not tested it. but i will as soon as my magic is back from the repair center.
Has this issue been resolved yet? It sure would explain issues I had in the past.
Hey i am doing theunlockr How To: Load a Custom ROM on Your HTC Magic this
there it says:
"I. Partition Your Memory Card for Apps2SD or Hero
1. Get into recovery mode by holding down Home and Power to turn on the phone (if you are not already there).
2. Click on Wipe Data. Once that is done, click on Format Fat32+Ext2+LinuxSwap and wait for it to format."
and in I can't find command "Format Fat32+Ext2+LinuxSwap" in RA-sapphire-v1.7.0H.img
What should I do, should I just miss this step???
there it says:
"I. Partition Your Memory Card for Apps2SD or Hero
1. Get into recovery mode by holding down Home and Power to turn on the phone (if you are not already there).
2. Click on Wipe Data. Once that is done, click on Format Fat32+Ext2+LinuxSwap and wait for it to format."
and in I can't find command "Format Fat32+Ext2+LinuxSwap" in RA-sapphire-v1.7.0H.img
What should I do, should I just miss this step???
Image not found
Alright,
Black, original myTouch 3g
Official Froyo - FRG83B
Temporary root via VISIONary
I'm trying to flash this recovery manually via terminal emulator. However, every time I submit
#flash_image recovery /sdcard/recovery-RA-sapphire-v1.7.0G.img
I receive a message saying "Image not found"
I have made sure there are no typos in the code, and the file is definitely on the root of my SD.
I have also tried flashing this recovery via ROM Manager and have even tried flashing the Clockwork Recovery but I have a feeling it is unsuccessful due to the temporary root.
1.) Is this even possible with temporary root?
2.) Does anyone know how to perma-root via VISIONary or any other root app designed for rooting Android version 2.2.1
p.s. I apologize if this information is already somewhere in the 100+ pages of this thread.
Thanks,
Ben
Alright,
Black, original myTouch 3g
Official Froyo - FRG83B
Temporary root via VISIONary
I'm trying to flash this recovery manually via terminal emulator. However, every time I submit
#flash_image recovery /sdcard/recovery-RA-sapphire-v1.7.0G.img
I receive a message saying "Image not found"
I have made sure there are no typos in the code, and the file is definitely on the root of my SD.
I have also tried flashing this recovery via ROM Manager and have even tried flashing the Clockwork Recovery but I have a feeling it is unsuccessful due to the temporary root.
1.) Is this even possible with temporary root?
2.) Does anyone know how to perma-root via VISIONary or any other root app designed for rooting Android version 2.2.1
p.s. I apologize if this information is already somewhere in the 100+ pages of this thread.
Thanks,
Ben
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.
