Vodafone UK Radio - myTouch 3G, Magic Android Development

Hi,
So I recently tried to do some modding, and I followed the guide (so I thought) for putting the Google ION firmware on my HTC Magic. The guide said, recovery image, I flashed recovery image.
Apparently I've flash the radio too...and they didn't mean recovery image they meant system image.
Is there a way to resolve this?
I'd really appreciate the help, I'd like to get my hands on the VFUK Radio or complete recovery image.

Could use this too

Orig Voda UK Nandroid backup
I've got my CRA71C nandroid backup I made after I got my Magic on the 3rd May. I found out shortly after buying it that it was a dev build firmware that should never have been released into the wild (already rooted) if that's any use?

Not 100% sure, but at the moment I'm willing to try anything, and I can get onto the recovery and get to Nandroid, so should help. I just need to find the right image to flash.

i thought they have same radio? being both 32B?

They are the same radio, as I've just discovered.
But for some reason it didn't work at all, but I followed some guide about reverting to a 32B Radio. So I wiped the whole thing, boot, recovery, system, etc. Installing the OTA update, and amon_RAs recovery, same problem again, but instead of booting into the system, I rebooted it into fastboot, flashed radio.img from the radio download on the HTC site, and it worked.
Not sure exactly what the problem was, but it's resolved now, thankfully.

Related

Newbie, please help, nandroid problems...

Hi,
I hope this is in the right section....
I have recently put the QTEK 1.6 Hero ROM on my Sapphire (UK MAGIC), and its ok but I preferred the stock ROM.
I have obviously done a nandroid backup using the RAV1.2.1G recovery image, using the one-click method (http://theunlockr.com/2009/08/29/how-to-root-the-htc-magic-in-one-click/).
I want to revert back to the stock ROM using my nandroid backup. I have follwed the instructions on these forums on how to do it, but I keep getting a problem.
I use the flashboot flash system system.img, it says sending, then writing, but when it comes to verifying info something or other, it says failed, something and something about unable to verify signature (happens on data and boot imgs too).
Is this something to do with SPL, do I need to update my SPL to restore, I have downloaded HARDSPL (version?) but have not gone any further as I dont want a brick....
Any help would be much appreciated.....
Thank you
If you were able to make a nandroid backup with your current SPL, then i assume thats not the problem.
Are you sure the files of your backup is still on your SD-card, and its (foldername "nandroid") location is root on SD-card..?
Hi,
Thanks for your reply.
Yes the nandroid folder is on the root of the sdcard, i've managed to get it working. Very strange??
What I did was to ignore the windows way of restoring, I just booted into recovery and selected nandroid restore, pressed green and hey presto, it worked? Now I tried that before and it said use adb in windows... maybe i missed a file or didnt press something correctly, at least I have my stock and apps back now...
Will try tinkering again though...got to be done... QTEKs rom has a few bugs, want to try Cyanogens, but i cant find his rom anywhere (i realise the issues with google)
Then i guess your SD-card wasnt ready mounted the moment you tried to recover.
He didn't recover via recovery, but via SPL.
so, do 1clickroot again, but instead of flashing a rom in recovery, select: restore nandroid recovery.
What if
What if we never created a Nandroid backup of the OEM ROM from our phone?
Will we still be able to return to the original ROM if we'd like for warranty purposes? I have flashed a Hero ROM and the OEM Tmo for Root Users and AmonRA Recovery. I haven't flashed any Radios or SPLs or anything though.
Just curious, thanks.
I downloaded the Unroot IMage which is exactly the release I used to have, COC10, is this the ROM I need for warranty purposes?

i want to convert my phone back to oem

i accidently flashed my phone with deathspl, and a new radio so i could run CyanogenMod 5.0.7 - Eclair 2.1 rom, reading feather into it i didnt need to do everything i did in order to run that rom.
my phone will not get past the mytouch boot screen, i can run my root program, which is a ras_dream
i need some help or direction please
You flashed death spl and new radio? I'm assuming your phone is bricked.
Can you at least get into fastboot or recovery. I have no idea what your "root program" is, I assume that's recovery. If that's so, then wipe your phone and flash another rom....
That's why it pays to read everything first before you get all trigger happy.
KAwAtA said:
You flashed death spl and new radio? I'm assuming your phone is bricked.
Can you at least get into fastboot or recovery. I have no idea what your "root program" is, I assume that's recovery. If that's so, then wipe your phone and flash another rom....
Click to expand...
Click to collapse
i can get into recovery, i understand how to do things, just not the terminology.
try another rom?
got any good sugestions?

Desire s stuck after 2.3.5 update

i tried to update via phone (after the notification), but after green bar was full, my phone rebooted and stuck in white screen with htc logo... if i try to enter in recovery i see this
h*tp://i39.tinypic.com/xdxnc5.jpg
it seems to be s-off (i bought it used) ...what have i to do for make it work again??
tnx.. and sorry for my bad english
same problem here, help is needed!
A golden rule: never update OTA on a modified device (custom ROM even modified Stock one, custom Recovery, Revolutionary hboot!, etc.)
How to fix:
do not pull battery!
flash a custom recovery (e.g. 4EXT) with the fastboot command (search for a how-to)
reboot to recovery, wipe all partitions and install custom ROM
Ok, to late with the battery, have already pulled that one out!
I also have S-Off on my phone, really dont understand the how to fix a recovery??
And is it really neccessary to flash a new ROM for this?
An official release that screwes the phones up?
I think the general issue is that an 'Official' OTA upgrade should not screw up your phone - enough testing by HTC should make sure of that.
Hoever, if you have modified your phone (e.g. by rooting it, installing custom recovery etc) then you can not expect to blame HTC when their upgrade doesn't work as expected. They can't be held responsible for problems caused by modifications you make to the phone.
But all I have done is S-Off, I have not installed another ROM or anything else?
So the update should work I really think!
Can I install a custom recovery without have to be able to start the phone?
Akerhage said:
But all I have done is S-Off, I have not installed another ROM or anything else?
So the update should work I really think!
Can I install a custom recovery without have to be able to start the phone?
Click to expand...
Click to collapse
The OTA flashes a new hboot also.
If you S-OFFed with Revolutionary your hboot has to be version 6.98.000x. This hboot has a protection and cannot be overwritten. This is the point where the update process is interrupted. The result is a bootloop, because the new system is incomplete.
If you can boot to bootloader (hboot) you should be able to flash a custom recovery with the fastboot command (in the 4EXT Recovery thread there is an attachement - a zip file that contains recovery.img). Extract the archive and flash it with this command from cmd (there is a guide how to make fastboot working in my signature):
Code:
fastboot flash recovery {path to file on your PC}/recovery.img
If this works reboot to recovery, wipe all partitions and flash a custom ROM. Then your phone should be working again.
Then if you want the OTA flash a 0.98.2000 hboot, then use the 1.47.401.4 RUU (if you are using European unbranded) or the corresponding for your brand/region to return back to complete Stock and S-ON. Then you will be prompted to update and you will have the latest OTA on your device
Okay, I have now fixed the 4EXT Recovery and it is working!
Do I have to put a new ROM on the SD-card or is there another way to install a ROM (from cmd with the ROM on the computer etc?)
I dont have an adapter to the SD-card, but maybe I can put the ROM on the sdcard with a command in cmd aswell?
What ROM do you recommend to use? (sense, no sense doesnt matter)
Edit: I did a backup as well, thinking that I should do that...
Can you link to zip file you used for recovery i have exactly same issue and same software versions as you have.
@ Mooler. First of follow the guide that was posted here regarding the adb-drivers.
After that download this: http://forum.xda-developers.com/attachment.php?attachmentid=631186&d=1308596026
Then install that one as described with the cmd-command.
After that just put a custom ROM or a shipped ROM on the SD-card, wipe data/cache and install the ROM you want. That solved the problem for me!
Good Luck and thanks for the help I got here! Xda always delivers
Damn this phone! After hours of fixing with this problem!
I managed great, installed new kernels, radios, ROMs etc. And the first thing I did was to drop it on the floor so the whole damn display cracked!
Thanks for both of you.
I managed to restore the phone quickly after i got the correct recovery file. 30 mins and custom ROM was up and running. Good bye official update.
Akerhage: sad to here, it really was hours of reading and trying before you get it right.

No operating system left after GPE flash fail - plz help!

After literally two weeks of reading thread after thread attempting to understand this , I tried to go from a sense ROM to a GPE ROM and I tried to flash the GPE firmware following Digital high's instructions here..
Things did not work out as instructed I'm afraid and that is probably due to my not understanding enough....nevertheless following DH instructions left me with repeated flash failures. Finally the following flashes got me from firmware 5.0.1- the firmware I was already on- to this:
fastboot flash zip VZWm8LfirmwareTWRP.zip - success; followed by the same ' flush" flash - again, success:
then:
fastboot flash zip 5.1_6_firmware+hboot.zip - and again another "flush" flash with success
From the way I read it we are then to reboot to bootloader and proceed further with recovery flashing the rom, blah, blah.... , however, my little android guy is overlaid with a black screen (instead of white) and he is dead. I rebooted to recovery to see if I could flash the sinless GPE ROM which is my goal in the first place (yes I realize it is a 4.4.4 but NOTHING flashes in recovery now) but now I m out of ideas. I have no workable phone and I have to get my ass to a new job in the afternoon. Can anyone help with either finishing my goal to install the sinless ROM or restore back to the adrenaline ROM I was running? I don't want to restore as I am afraid I may have altered the firmware and thus brick if I do restore...PLEASE HELP!!!! PLEASE!
right now my phone is sitting on the charger on the dead android screen. i don' dare touch it. What should i do?
Update: I am flashing digital highs GPE_5.1-multi_dh_051215.zip and I am getting a bootloader remote 24 "parsing android info fail". Does anyone know what that means or how to fix?
Update again: Figured out this needs to be flashed in recovery and not fastboot. Now I have been booting for about five minutes now. Hope I'm not bootlooped. ....
Figured it out
Got it figured out.
Mods, could you please close the thread. thanks!
kerryh said:
Got it figured out.
Mods, could you please close the thread. thanks!
Click to expand...
Click to collapse
Rather than end things with a statement that you figured it out, could you elaborate on the solution and/or describe what went wrong to cause the problem (if you happened to figure that out while finding your fix)? Someone else could come here with your same problem and you are likely poised to help them out with your newly found solution.
cntryby429 said:
Rather than end things with a statement that you figured it out, could you elaborate on the solution and/or describe what went wrong to cause the problem (if you happened to figure that out while finding your fix)? Someone else could come here with your same problem and you are likely poised to help them out with your newly found solution.
Click to expand...
Click to collapse
Believe me, I thought about trying to do just that. That's when I realized I am not sure that I totally understood what it was I did wrong in the first place. I believed the underlying issue might have been the order in which I flashed but I can't be sure because I ended up flashing files that probably shouldn't have been flashed to begin with . What I do know is that some firmware files needed to be flashed in RUU mode while others in regular fastboot and the GPE zip flashed through recovery, not regular fastboot as I thought it needed to be. And all that even being understood I still wasn't sure if I needed the firmwares with the hboot, without hboot, with or without recovery/boot .img's....
Going back and looking at my cmd window it appears the following worked in the following order:
FastbootRUU flash 5.0.1 firmware
fastboot VZWm8Lfirmware.zip
fastboot write superCID
fastbootRUU flash 5.1 firmware
reboot to hboot (dead android here) then reboot to recovery
Recovery flash GPE_5.1_muliti_dh_date.zip
Follow the promps to install and then reboot to glory...
I am still not clear on as to whether or not I can go back to my nandroid backups as those were taken on different firmwares obviously. Instinct tells me I would brick but idk...Looks like I am stuck on GPE for a while...
That probably confused more people than helped...See why I didn't post it?
kerryh said:
Believe me, I thought about trying to do just that. That's when I realized I am not sure that I totally understood what it was I did wrong in the first place. I believed the underlying issue might have been the order in which I flashed but I can't be sure because I ended up flashing files that probably shouldn't have been flashed to begin with . What I do know is that some firmware files needed to be flashed in RUU mode while others in regular fastboot and the GPE zip flashed through recovery, not regular fastboot as I thought it needed to be. And all that even being understood I still wasn't sure if I needed the firmwares with the hboot, without hboot, with or without recovery/boot .img's....
Going back and looking at my cmd window it appears the following worked in the following order:
FastbootRUU flash 5.0.1 firmware
fastboot VZWm8Lfirmware.zip
fastboot write superCID
fastbootRUU flash 5.1 firmware
reboot to hboot (dead android here) then reboot to recovery
Recovery flash GPE_5.1_muliti_dh_date.zip
Follow the promps to install and then reboot to glory...
I am still not clear on as to whether or not I can go back to my nandroid backups as those were taken on different firmwares obviously. Instinct tells me I would brick but idk...Looks like I am stuck on GPE for a while...
That probably confused more people than helped...See why I didn't post it?
Click to expand...
Click to collapse
When compared to the steps I took to flash the 6/15 build as cleanly as I could manage, here's what jumps out to me as strange or unnecessary:
-I don't know what the '5.0.1 firmware' is but I suspect it's the same as the 'VZWm8Lfirmware.zip' you flashed next. I chose to run the 5.0.1 RUU and considered that as complete of verizon 5.0.1 firmware as there is.
-I don't think that superCID has been necessary for DHs GPE for some time. I don't know that it would necessarily cause a problem but I've never gone to superCID and have had no problems
-flashing DH's carrier-agnostic 5.1 firmware is stated as optional in his OP and I think DH himself admitted a little while back that it may actually be the cause of some folks' wi-fi issues
Regarding restoring old nandroids to a system with updated firmware, I can say that each time a new official software has been released, I've flashed tigerstown's firmware-only zips alongside whatever custom rom I was running at the time with no issues. This points to a trend of successfully running roms on top of newer firmwares without issues. I know of many 5.x roms saying that you must update firmware but I've never read about a 4.x rom having issues with 5.x firmware. I don't think there's much risk of flashing a custom rom (or restoring a nandroid) from recovery that doesn't match the firmware beyond a possible bootloop.

[Q] Unable to restore Nandroid Backup and boot

Hi guys,
nice to say hello to all of you.
I have been reading xda for a while and finally started playing with my old HTC Desire S. Kind of training in case I wanted to play with my actual device.
I wanted to unlock it thorugh htcdev, test some roms and back to stock version. Everything was fine but the last step.
At the beginning, I wanted to backup the system as it was, that's with the stock recovery. So I booted a custom recovery (not flashed) and made a nandroid backup with clockwork touch 5.8.1.5. Everything went fine.
After that, I started flashing custom recoveries and ROMs, just for fun. Some problem with that ROM, some with another, but I managed to run a couple or three.
Ok, end of the game. I want my copy back so I am restoring the nandroid.
I wipe everything, restore the nandroid through the same recovery, process finishes and says it's OK. Go back to fastboot and flash stock boot.img.
The result is I am stuck at htc logo.
I have tried flashing recovery.img also, fastboot deleting cache, relocking the bootloader...
I am pretty sure I am missing something with the booting process, but I have tried everything I know.
BTW, I have already tried RUU, but I am not capable of finding one with my CID, radio, etc.
I know it's an old device, but I would really love to solve it (because I am so f***ing pigheaded )
Thanks!!!
Grauchi said:
Hi guys,
nice to say hello to all of you.
I have been reading xda for a while and finally started playing with my old HTC Desire S. Kind of training in case I wanted to play with my actual device.
I wanted to unlock it thorugh htcdev, test some roms and back to stock version. Everything was fine but the last step.
At the beginning, I wanted to backup the system as it was, that's with the stock recovery. So I booted a custom recovery (not flashed) and made a nandroid backup with clockwork touch 5.8.1.5. Everything went fine.
After that, I started flashing custom recoveries and ROMs, just for fun. Some problem with that ROM, some with another, but I managed to run a couple or three.
Ok, end of the game. I want my copy back so I am restoring the nandroid.
I wipe everything, restore the nandroid through the same recovery, process finishes and says it's OK. Go back to fastboot and flash stock boot.img.
The result is I am stuck at htc logo.
I have tried flashing recovery.img also, fastboot deleting cache, relocking the bootloader...
I am pretty sure I am missing something with the booting process, but I have tried everything I know.
BTW, I have already tried RUU, but I am not capable of finding one with my CID, radio, etc.
I know it's an old device, but I would really love to solve it (because I am so f***ing pigheaded )
Thanks!!!
Click to expand...
Click to collapse
You can't flash roms from the recovery because you are not s off. If you have unlocked your bootloader then you have to flash using fastboot commands like the boot.img?
lilsafbig said:
You can't flash roms from the recovery because you are not s off. If you have unlocked your bootloader then you have to flash using fastboot commands like the boot.img?
Click to expand...
Click to collapse
Thank you @lilsafbig. In fact, I tried both, fastboot and recovery, and nothing worked.
Finally, I managed to create a Goldcard and install a new ICS version for my device. Was the only way I could recover a "stock" ROM, although it wasn't Orange one...

Categories

Resources