Database Info

[Q] Help to get a custom ROM an a rooted HTC Magic

Hi guys,
For the last 2 nights I´ve been trying to get a CG Mod 6.1 on my HTC Magic 32B.
I have rooted it with onclick-root method and tried a bunch of things like ROM Manager and flashing via fastboot (brings up "remote not allow" error). Nothing worked out.
Here are the facts:
HTC Magic with OTA upgrade to 2.2.1
hboot: 1.33.0013
radio: 2.22.28.25
Rooted with Oneclick method
Do I need a goldcard? How do I do that? What hboot Version do I need? What Radio do I need? What do I have to do first?

Are you certain the Root took? Are you seeing the Superuser icon in your app drawer?
When you were using Rom Manager did you flash, or attempt to flash a custom recovery, and if so did it install ok?
What happened when you tried to flash a ROM using Rom Manager?
I'm sure we'll get to the bottom of this

Yes, rooting has worked...Icon is there everything looks fine.
With the Rom Manager i tried to install "update-cm-6.1.0-DS-2708port_S" aswell as the "update-cm-6.1.0-DS-signed". Both did not work.
I still can boot to my standard OTA 2.2.1

Try wiping your phone in recovery and then install the rom

hang on a minute...
it sounds like you haven't installed a custom recovery before trying to flash the rom. Can you clarify...have you actually done this yet?
The process should go root/recovery/nandroid backup/rom in that order.

yeah you re right...i dont have a custom recovery
i just tried to load "recovery-RA-sapphire-v1.7.0G.img" on the console
su
# flash_image recovery /sdcard/recovery.img
does not work, i get: flash_image: not found
USB debugging is enabelde
3rd party software is enabeled
is there another way to get flash the recovery ?

Rom Manager!
At the top you should have the option to flash clockworkmod recovery. Select that; it will run and then the phone should reboot. I usually do it again to confirm. If it installed correctly the first time you'll get a pop up saying that it is installed.
If all goes to plan select 'backup current rom' from within Rom Manager. This is a nandroid backup and can be re-installed from recovery any time you wish to return to stock.
NOW you are free to install a custom ROM of your choice
Post back if you encounter any issues.

I have tried that. It flashes, gives my a popup that it installed correctly.
But it does not reboot.
When i choose restart in recovery mode it boots up the phone an gets stuck on the vodafone logo. BatteryOut reboot and i am back at the good old 2.2.1 OTA
do i have to wait long?!? cant be, right? do i need to hold down any buttons?

If you try the backup option now you'll soon find out if the recovery did indeed install ok. (it won't backup if the recovery isn't installed)

i restarted...flashed the recovery again. got popup confirmation. then chose backup rom and got stuck at the vodafone logo

You must be pretty frustrated by now. It might be time to start asking for more help in the dev section of the Magic forum HERE.
I hope that somebody has the answer!

Thanks for your help...i ll see if someone else has any ideas.

roodee said:
yeah you re right...i dont have a custom recovery
i just tried to load "recovery-RA-sapphire-v1.7.0G.img" on the console
su
# flash_image recovery /sdcard/recovery.img
does not work, i get: flash_image: not found
USB debugging is enabelde
3rd party software is enabeled
is there another way to get flash the recovery ?
Click to expand...
Click to collapse
Are you are aware that the command you need to type will be
flash_image recovery /sdcard/recovery-RA-sapphire-v1.7.0G.img
The command points to the exact file name on your sd card so if you just wrote flash_image recovery /sdcard/recovery.img and the recovery file was not called "recovery.img" it would not know what to look for.
I'm not sure if this is what you have or whether you just copied and pasted from a guide, but I just thought I'd put it out there in case that is the case.
Hope this helps.

[Q] I might have bricked my TF101G finally - Please help!

OK. This is an older TF101G, which was running ICS, but needed to go back to stock.
My first mistake was to follow a thread which installed the stock WW HC image, but with an US stock recovery. There, I could not get updates.
I tried to fix this by rooting this monster with nachoroot. I rooted successfully. My second mistake was to use RomManager to install CWM. Though it says it has the right image, this does not work. You can boot into it, but it cannot mount the sdcard, nor can it install any zip. The machine still boots into ICS.
To recover from this, I did my third mistake. I followed an advice to insert a blob from this web page with dd to mmcblk0p4. The blob is the boot blob from CM9.1. However, now this boot blob cannot start the ICS system. It hangs at the boot logo. I can still boot into CWM, however.
To recover from this, I tried booting as far as it goes, and starting adb shell. The screen is showing a boot logo of the Transformer at that time. But the su command now longer works and hangs the shell. This beats me. Otherwise I would have tried the blob from the ICS version I installed.
Is there any way to get out of this mess?
Update:
I tried re-rooting with nachoroot. But trying to push nachoroot.bin to /data/local fails because of "permission denied". Pushing to /mnt/sdcard works. But I am not permitted to chmod to 777 there.

I solved this for the moment
Sorry, I solved it myself. Glad to see that I am still faster than the people here
I followed an advice in a posting to install the universal drivers on Windows. Simply download the drivers and updated the device drives in the hardware manager. Then I boot into CWM. There adb shell magically goes to a root shell. Probably because I rooted the phone before. Then I used dd to push the blob of the original android firmware to mmcblk0p4. The device now reboots into HC!
It remains to find out how to get a working CWM recovery to this device, so I can put an ICS ROM on it.

mga010 said:
Sorry, I solved it myself. Glad to see that I am still faster than the people here
I followed an advice in a posting to install the universal drivers on Windows. Simply download the drivers and updated the device drives in the hardware manager. Then I boot into CWM. There adb shell magically goes to a root shell. Probably because I rooted the phone before. Then I used dd to push the blob of the original android firmware to mmcblk0p4. The device now reboots into ICS!
It remains to find out how to get a working CWM recovery to this device.
Click to expand...
Click to collapse
Use PERI.
It will push a working CWM via ADB.
Works with the TF101g
Be advised the version it uses only seers the internal storage to flash ROMs.

frederuco said:
Use PERI.
It will push a working CWM via ADB.
Works with the TF101g
Be advised the version it uses only seers the internal storage to flash ROMs.
Click to expand...
Click to collapse
Yeah, thanks, I used this tool to flash a working recovery when I was on ICS.
Now I am on rooted HC and a useless CWM. I could use the recoveryblob in the PERI tool and do the same dd trick I did with the boot blob. But I want to make sure this recovery will cooperate with my HC system. At least there should be a way to revert.

I don't see why it wouldn't work with HC.

Experience?
frederuco said:
I don't see why it wouldn't work with HC.
Click to expand...
Click to collapse
There are users which report on the PERI thread about problems with HC.

No Ideas
So nobody knows how to update my Transformer? The remaining problem is that I have HC (stock) running with a disfunctional CWM recovery.
Maybe I will live with it for a while and open a new thread later.

Solved, I hope!
Ok. I solved this too. I found TWPR 2.2 on the net and took the recoveryblob out of it. Then copied this to /dev/block/mmcblk0p4 with
dd if=recoveryblob of=/dev/block/mmcblk0p4
Reboot, and got my new recovery. I hope I can install and decent ROM now.

[Q] Botched TWRP upgrade, now lost root access

While attempting to switch to CM11 I tried upgrading TWRP from 2.4.4 to the newest 2.6+ and it messed up my recovery. Then, while trying to re-flash an older TWRP, I accidentally installed SuperSU over an existing install, and lost root. Tried re-rooting the device using motochopper and it gets to the last part, "rooting device" and it says "failed". Device the reboots, I try to open SuperSU and it says "no SU binary installed". All I'm trying to do is put back TWRP 4.2.2 so I can restore my device. Please help
EDIT: Tried using fastboot to install image, everything looks good, then my tablet freezes up. I do a power cycle, it reboots, and the recovery didn't flash.
UPDATE: Recovery flashed and wiped EVERYTHING. I am back on recovery 4.2.2.0 but nothing is mounted and I can't mount anything, I can't make backups or restore images, and ADB Sideload does not work. Any help would be really, really awesome. I have SDK Manager, and I can currently use ADB on my computer, I just don't know what commands, blobs, or images to use.

Tunameltsalad said:
While attempting to switch to CM11 I tried upgrading TWRP from 2.4.4 to the newest 2.6+ and it messed up my recovery. Then, while trying to re-flash an older TWRP, I accidentally installed SuperSU over an existing install, and lost root. Tried re-rooting the device using motochopper and it gets to the last part, "rooting device" and it says "failed". Device the reboots, I try to open SuperSU and it says "no SU binary installed". All I'm trying to do is put back TWRP 4.2.2 so I can restore my device. Please help
EDIT: Tried using fastboot to install image, everything looks good, then my tablet freezes up. I do a power cycle, it reboots, and the recovery didn't flash.
UPDATE: Recovery flashed and wiped EVERYTHING. I am back on recovery 4.2.2.0 but nothing is mounted and I can't mount anything, I can't make backups or restore images, and ADB Sideload does not work. Any help would be really, really awesome. I have SDK Manager, and I can currently use ADB on my computer, I just don't know what commands, blobs, or images to use.
Click to expand...
Click to collapse
Can you use fastboot to reflash the stock ROM?

[Q] Stuck in recovery some time after flashing cwm

Actually it might be a little more complicated...
Full story: I was trying to flash cyanogenmod so I unlocked the bootloader and flashed cwm and SuperSU. Until this point everything worked just fine. I copied the CM-zip to the root of my phone. When trying to install CM however I got an error saying "Some changes failed" (Status 7), basically this. Also I started having trouble booting the system normally. The phone would either get stuck at the bootloader unlocked screen or just boot into recovery. I had done a backup at some point (not prior to starting to try to flash CM, I didn't really think I'd need one since the phone was brand new and I didn't there was any data on it I'd miss... yeah, well...) and sometimes restoring it would enable me to boot normally. However, after the factory reset before my nth attempt to install CM, that was gone as well. After doing a bit of research I found this thread. Since I had version 6.0.13 of cwm as well, I flashed twrp v2.7.1.2 instead. The interface is a little friendlier, but other than that there have been no changes.
Now I can't boot the system normally, not even by selecting "System" when rebooting it from recovery, it will just keep booting into recovery. I can still fastboot, though. My CM-zip is gone since that infamous factory reset and I can't get it back on the phone, or anything else for that matter, since my pc only detects the phone when it's booted normally. I tried pushing CM with adb but when I try to mount any partition I get an error saying E: Unable to find storage partition to mount to USB.
Any ideas how I could fix this mess? Or suggestions on how to avoid ****ing it up any further...

If you can adb, you can adb push... You are just adb push'ing to the wrong place I suppose.
Code:
adb push blah.zip /sdcard/
Should work...
Or even better, just sideload (put phone in recovery & 'sideload mode' before running):
Code:
adb sideload blah.zip
Either way, CWM for our device is ancient and does not support the latest ROM's. The version of TWRP should work fine, as should the latest OpenRecovery (2.09 IIRC).

Sideload worked perfectly! Thank you so much!

cm11 working only TWRP here , with cwm appears same error

mmichaelalves said:
cm11 working only TWRP here , with cwm appears same error
Click to expand...
Click to collapse
Did you not read my post?
arrrghhh said:
Either way, CWM for our device is ancient and does not support the latest ROM's. The version of TWRP should work fine, as should the latest OpenRecovery (2.09 IIRC).
Click to expand...
Click to collapse

Multiple recoveries installed

I'm screwed. I attempted to install an updated TWRP, so i selected that option in ROM Toolbox Pro. Everything installed correctly (TWRP 2.7??). I decide let me see if TWRP installer will replace that with the updated 2.8.5. I run TWRP installer and it installs correctly. My assumption was that the TWRP installer would overwrite the ROM Toolbox version. Well, i reboot into the 2.8.5 recover (like it suggested) and i hit Reboot and then it reboots into 2.7. From there it thinks there is no OS installed. Rebooting from there just reboots me back in 2.7 recovery. I can get into Fastboot, and then back in 2.8.5 recovery. I flashed a new ROM, but that didn't fix it. I attempted to flash an RUU but i can't seem to get that working either. Am I completely screwed and should i call insurance on it?
Help me XDA, you're my only hope.

theoden144 said:
I'm screwed. I attempted to install an updated TWRP, so i selected that option in ROM Toolbox Pro. Everything installed correctly (TWRP 2.7??). I decide let me see if TWRP installer will replace that with the updated 2.8.5. I run TWRP installer and it installs correctly. My assumption was that the TWRP installer would overwrite the ROM Toolbox version. Well, i reboot into the 2.8.5 recover (like it suggested) and i hit Reboot and then it reboots into 2.7. From there it thinks there is no OS installed. Rebooting from there just reboots me back in 2.7 recovery. I can get into Fastboot, and then back in 2.8.5 recovery. I flashed a new ROM, but that didn't fix it. I attempted to flash an RUU but i can't seem to get that working either. Am I completely screwed and should i call insurance on it?
Help me XDA, you're my only hope.
Click to expand...
Click to collapse
To solve this, you could get phone into Fastboot and flash Dottat's RUU for the M8 - he made several versions.
For sure, add HTC_Fastboot.exe to your ADB folder and use it, NOT regular fastboot.
It will overwrite your previous recovery with stock and fix your phone. Then later, you could flash TWRP 2.8.7 thru Fastboot.

I put Dottat's RUU on my external SD card and it loaded, however, whenever it goes to reboot, it still goes back into the wrong recovery.

It's probably not necessary to run an RUU. You incorrectly flashed the new recovery to the wrong partition. Flash the new recovery VIA FASTBOOT, boot into it through the bootloader screen, and either flash a rom or restore a backup and you should be good to go. You definitely don't need to be worrying about an insurance claim for now.
Edit: by VIA FASTBOOT I mean with the command fastboot flash recovery <nameofrecoveryfile>.img

cntryby429 said:
It's probably not necessary to run an RUU. You incorrectly flashed the new recovery to the wrong partition. Flash the new recovery VIA FASTBOOT, boot into it through the bootloader screen, and either flash a rom or restore a backup and you should be good to go. You definitely don't need to be worrying about an insurance claim for now.
Edit: by VIA FASTBOOT I mean with the command fastboot flash recovery <nameofrecoveryfile>.img
Click to expand...
Click to collapse
I would flash firmware or ruu, if indeed he flashed recovery to wrong partition, that partition needs the correct one which firmware wlil do, and ruu will 100% do.
Personally I'd run ruu, go to stock recovery and run a factory reset.

theoden144 said:
I put Dottat's RUU on my external SD card and it loaded, however, whenever it goes to reboot, it still goes back into the wrong recovery.
Click to expand...
Click to collapse
Gotta use ADB and HTC_Fastboot.exe

Thanks for all the tips. I tried re-installing the old ROM after I ran the RUU and it worked. Hopefully it cleared out the incorrect recovery. Lesson learned: don't use apps to update the recovery!
Again thanks for all the help!

theoden144 said:
Thanks for all the tips. I tried re-installing the old ROM after I ran the RUU and it worked. Hopefully it cleared out the incorrect recovery. Lesson learned: don't use apps to update the recovery!
Again thanks for all the help!
Click to expand...
Click to collapse
Twrp manager is not a safe way to flash recovery because they aren't flashing by block name yet. They are still hard-coded to block number. The partitions have changed during ota already...so the app does hose things up a bit.
Sent from my Nexus 6 using Tapatalk