Okay, I've searched and searched for someone else with this problem and just cannot find any threads. I've been flashing roms from these forums for a while now, starting with JF 1.30 and have never had any problems. However, I have not been able to flash anything newer than JF's 1.50 since I installed it. I've tried multiple hero builds, ion, even cm's build of 1.5. The only thing that'll get past the G1 screen is jf1.5. I have the latest radio and spl. I have my sd partitioned with about 650mb on the ext2. I have NO IDEA why they aren't working. Any ideas?
when all else fails, unroot and root again.
Basically what WDD said... reinstall the NBH file you used to unlock the phone and start over.
I had to do it once myself....
momentarylapseofreason said:
Basically what WDD said... reinstall the NBH file you used to unlock the phone and start over.
I had to do it once myself....
Click to expand...
Click to collapse
same here, i had to do it once early on my rooting days.
oh how i've learned since then...
My neighbor, he's running Hero, and I have actually both tried using my nph file to drop my phone back down to 1.29, then rerooted it, reinstalled the new radio and spl, and still, couldn't flash anything newer than JF1.5. Perhaps I am doomed to use cupcake until my phone dies.
thelivingrobot said:
My neighbor, he's running Hero, and I have actually both tried using my nph file to drop my phone back down to 1.29, then rerooted it, reinstalled the new radio and spl, and still, couldn't flash anything newer than JF1.5. Perhaps I am doomed to use cupcake until my phone dies.
Click to expand...
Click to collapse
Then there must be something wrong with the things you download. I always redownload files when im rooting or flashing recovery images or SPL's.
Related
I've been reading these forums for quite some time folowing H's and JF's builds and just seeing what the devolping community has been up to.
I've been wanting to root my g1 for some time but didnt ever make the jump till now. I read through the Helpful Thread / Build Round up started with in the beginning there was root as well as the How-to- Root, Hack, and Flashing your G1/Dream and decided i could do it. i followed all of hte steps with ease. had my phone rooted within 20 minutes the first thing i wanted to do was to get a new rom with cupcake but i also wanted to be sure not to mess it up so i read through nandroid and was a bit confused as to what all was needed so i figured the recovery img that the tutorial gave was fine since everything i had done was no problem. i then went to H's ion thread and saw that i needed a differen spl so i went and read about those and decided with hardspl got that applied no problem. i downloaded the ion rom renamed it to update.zip put it on my card and loaded up recovery mode pressed alt+s to apply it and everything went fine till it hung at the 2nd boot screen. a little disheartened i went into the spl using camera+power and flashed the recovery img. i read around the forums seeing if i did anything wrong and couldnt figure it out so i tried a different rom this time one of Jf's early roms i think it was rc33 i tried to apply that but i got a no signature verication failed at the recovery screen so i tried some others. JF's 1.51 and same problem. i read around some more and thought maybe it was because i didnt do alt+W so i tried that with JF's roms and both of the leaked hero roms (i know hero is extremely unstable but i just wanted to see if something entirely differnt would work.) by this time i go into the spl again and saw that the hard spl wasnt loaded any more (i guess the recovery img changes that) i reloaded the recovery img once more and tried to install a the 2nd Ion rom with H's root apps and still the same problem.
i really try to read and search before posting but after 4 hours of nothing i really just want some help. if someone could help me get a working rom on my phone preferably H's new Ion rom and tell me what im doing wrong i'd be endlessly great full.
Im guessing what happend was you did the switch of releasekeys to testkeys and then later redid the DREAIMG.nbh. If so you need to redo the steps involving testkeys. This is why it gives the no signature verification error.
In fact id suggest redoing the whole root process again. starting with the DREAIMG.nbh.
Hello,
I have a problem with my G1.
I got my G1 maybe a month ago. It had firmware 1.1 and radio module 1.22.12.29. Back then I did not realize it was a radio image compatible with firmware 1.0 as far as I gather from the HTC website.
At first, I did not intend to root it at all, a decision later I would regret. Well, it worked OK, only it was not updated. I was told I would receive the update over-the-air in 4 days. At first they said it would be to 1.5, but it turned out my operator started to upgrade straight to 1.6.
And so I did receive it in 4 days and the problems began.
Basically, the voice quality is so bad that half of what I say is ununderstandable. My voice sounds metalic and I cannot have a coherent conversation over the phone. It is a business phone, so you can imagine it is rather annoying when I have to struggle to be understood by clients.
Ok, so I checked the bootloader for the radio image version and I found out it was still version 1.22.12.29. As per the HTC website I should have 2.22.19.26I. So, obviously the radio firmware was not updated as it should be as per the HTC website. Thus, it seems the reason voice quality is so poor is the outdated radio firmware.
Since I did not plan to return my new phone to my operator (I had no time for it), I decided to root the phone and update the radio firmware myself. It seemed simple enough and I use Unix and Linux since 15 years, so it seemed it would pose no problem.
Quickly I learned that rooting 1.6 is not so simple. One-click method fails. Only goldcard worked and after a few days of struggle I finally got back to firmware RC7 and rooted the device.
Right after I updated the recovery image to CM 1.4, but before I flashed the CM ROM I attempted to update the radio firmware as was suggested by one tutorial I followed as well as the CM website.
Well, it all went smooth. After the update I pressed Home and Back, it rebooted, back to recovery CM1.4, one more time Home and Back and I was back to the working phone. I checked the radio firmware and lo and behold, it was still version 1.22.12.29. No errors, nothing, smooth update process and no result. I repeated it at least 5 times to no avail.
I decided to install CM 4.2.7.1 ROM and try to update the radio then. Before the CM ROM I updated the SPL to HardSPL with success to have fastboot and went to install CM. It went smooth and I booted into this new rooted G1 ROM with ease.
Again, I attempted to update the radio firmware from recovery CM1.4 and again no results.
So, I am back to square one. I have again firmware 1.6 only from CM instead of stock HTC, and I cannot use this phone for calling.
So, summarizing, I got the phone with firmware 1.1, but radio firmware from 1.0. Why it was not updated together with the system I do not know. Then I got an update to 1.6 and the radio firmware also did not upgrade. Then I went back to RC7 (firmware 1.0), rooted the phone, attempted the radio firmware update before installing CM ROM and failed. And finally, I installed HardSPL + HTC 1.6 recovery (as suggested on the CM website) + CM ROM and again failed to update the radio firmware to 2.22.19.26I. The update process is going without any errors. Verification, extracting, installation of radio image all go OK, the phone reboots but no radio updated.
Anybody any idea why it is like this? Why this phone refuses to update the radio from HTC website.
Any suggestions?
Oliwer
PS. One more thing, I was contemplating updating the radio via fastboot, but it seems after reading HTC website that fastboot is only for system and recovery image flashing. The radio has to go first adn from recovery console. Am I right on this?
I too have a problem updating to the 26i version. however i rooted at 1.5 using the one click root method and ive since switched from cyan 1.4 recovery and cyan roms to amon recovery and dwang roms. No matter which recovery i use, the 26 update flashes without an error but shows up as the same radio ive had all along (1.22.14.11) i made a thread about it but noone seems to have an answer. Sorry I couldnt help, but at least bumped up your thread and maybe someone can help us.
speedysilwady said:
I too have a problem updating to the 26i version. however i rooted at 1.5 using the one click root method and ive since switched from cyan 1.4 recovery and cyan roms to amon recovery and dwang roms. No matter which recovery i use, the 26 update flashes without an error but shows up as the same radio ive had all along (1.22.14.11) i made a thread about it but noone seems to have an answer. Sorry I couldnt help, but at least bumped up your thread and maybe someone can help us.
Click to expand...
Click to collapse
Thanks for sharing!
At least I know I am not alone here with this problem.
Since it's Christmas and I have some more time, I decided to do a Nandroid backup and wipe my phone back to the original rom with 1.0 firmware (RC7).
I used my goldcard and I flashed it in a few minutes. I logged back into 1.0 firmware with the original bootloader and recovery console.
Next I put everything on my goldcard, flashed the recovery CM1.4 from the terminal, went to the bootloader, flashed update.zip with the newest radio 2.x from HTC, everything went smooth. Reboot and again NO change of the firmware. Tried a few more times flash the radio and HardSPL together to no avail. I restored my backup and found myself back to square one.
One think I noticed, and I wonder if you get the same, is that when I flash the radio, the phone reboots back to the recovery console and shows "Formating Cache..." message. It does not tell me anything like Please reboot, just this message. Meanwhile I can move the cursor up and down the recovery menu, so the phone has not hang up. It just sits at the recovery until I reboot it. Once I waited 30 minutes to see if it reboots itself and it does not. So, I press Home+Back and then it reboots fully and after loging in I check the radio and NO change.
So, I wonder if your phone does the same?
Oliwer
PS.
T-Mobile G1 - w/ ROOT
DREA110 PVT 32B
HardSPL 10.95.3000
Recovery image: HTC Android 1.6 (from HTC website)
Class IV 8GB SD Card w/ Ext 4 Partition and Swap partition
That's a huge wall of text, and it's Christmas so I'm a little merry
When flashing the radio image w/ Cy's recovery you must flash as an update.zip using alt-s, press whatever key you need to press to confirm and reboot using home+back. If you use flash any zip or use the trackball to reboot the radio image (or SPL) will not reboot in the required way to complete installation.
AdrianK said:
When flashing the radio image w/ Cy's recovery you must flash as an update.zip using alt-s, press whatever key you need to press to confirm and reboot using home+back. If you use flash any zip or use the trackball to reboot the radio image (or SPL) will not reboot in the required way to complete installation.
Click to expand...
Click to collapse
I tried all possible ways. Just a few minutes ago I went to CM1.4 recovery, used the update from update.zip, pressed Home+Back, rebooted back to recovery console, pressed Home+Back again, booted to CM4.2.10, punched the PIN code, checked the About Phone section and I am still with 1.22.x radio firmware.
This phone simply refuses to update the firmware in any known way.
So, my plan now is to un-root it back to the state I got it 2 months ago and return it to the operator and request upgrade of radio, since Donut with an old radio is basically useless. People simply do not understand half of what I say even if I speak slowly and quietly.
Cheers,
Oliwer
You have to press
Cam+power and it will show radio
....
In settings that radio has nothing to do with one installed...Do you know that the radio does?
It allows custom roms like cyan to be installed while keeping root access. The rom allows some tmo apps like account to still be used here in the states.
yes oliwer i get the same formatting cache message but nothing else happens. i tried in cyans recovery and amons recovery using only button shortcuts and not the trackball. i always named the radio update.zip, but still no luck. Im not sure if the 26i radio requires a certain version before it can upgrade, like maybe i have to upgrade to another radio before i can get to 26i? im not quite sure...ive run out of ideas on what to do. I dont have a warranty or anything on my g1. does the fact im using a donut rom on a cupcake radio have anything to do with it? if i had a cupcake rom and upgraded the radio to 26i from there would it work? i know these might sound like dumb ideas but im still relatively new to the scene and im running out of ideas as to why this is happening or why i cant solve it..
bump? anyone have a solution for us? or advice?
i just realized that i had android 1.1 with the 1.22.14.11 radio when i first got my phone, when t-mobile gave me the 1.5 update, i was still stuck on the same radio for some reason. After that I used the one click method to root and ive been on dwang donut rom ever since with the same dated radio...Ive tried using cyans recovery to flash and still no luck, no error, it says its updated but when i check the baseband or stock spl its still the same radio. I never went for a danger spl when i rooted because i was afraid to brick so i cant fastboot a radio update. I asked in another topic if it was possible to use the "flash_image" command in terminal to flash the radio but i dnt think itll work and i dont wanna risk it. If anyone has any advice or a possible solution please keep us updated.
Thank you!
Turn your phone off, hold the camera button down, and power on your phone.
What do you see?
each time before and after the flashing of the radio using cyans or amons recovery image id get the same rainbow screen saying
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.14.11
Serial0
so im still stuck on the Android 1.1 radio.
speedysilwady said:
yes oliwer i get the same formatting cache message but nothing else happens. i tried in cyans recovery and amons recovery using only button shortcuts and not the trackball. i always named the radio update.zip, but still no luck. Im not sure if the 26i radio requires a certain version before it can upgrade, like maybe i have to upgrade to another radio before i can get to 26i? im not quite sure...ive run out of ideas on what to do. I dont have a warranty or anything on my g1. does the fact im using a donut rom on a cupcake radio have anything to do with it? if i had a cupcake rom and upgraded the radio to 26i from there would it work? i know these might sound like dumb ideas but im still relatively new to the scene and im running out of ideas as to why this is happening or why i cant solve it..
Click to expand...
Click to collapse
I do not know, really, why the radio refuses to upgrade. Since my last message I have read tons of posts on this issue and nearly ALL people can upgrade the radio firmware easily, just like the SPL. Somehow, I can upgrade the SPL to whatever I want, but not the radio. Very strange indeed and no luck so far.
Oliwer
speedysilwady said:
bump? anyone have a solution for us? or advice?
i just realized that i had android 1.1 with the 1.22.14.11 radio when i first got my phone, when t-mobile gave me the 1.5 update, i was still stuck on the same radio for some reason.
Click to expand...
Click to collapse
Exactly the same in my case. Except they upgraded straight to 1.6. Before the upgrade I have 1.1 firmaware and quality of voice was perfect. After the upgrade things went south.
speedysilwady said:
After that I used the one click method to root and ive been on dwang donut rom ever since with the same dated radio...Ive tried using cyans recovery to flash and still no luck, no error, it says its updated but when i check the baseband or stock spl its still the same radio.
Click to expand...
Click to collapse
Same thing with me.
speedysilwady said:
I never went for a danger spl when i rooted because i was afraid to brick so i cant fastboot a radio update.
Click to expand...
Click to collapse
Well, I installed HardSPL and it worked despite the old radio. HardSPL offers FASTBOOT and I use it at times. This is safe, at least for me.
speedysilwady said:
I asked in another topic if it was possible to use the "flash_image" command in terminal to flash the radio but i dnt think itll work and i dont wanna risk it.
Click to expand...
Click to collapse
Well, I did, but it does not work since flash_image updates partitions and G1 does not have radio partition. So, when you try to update the radio.img it tells you no radio partition. It is only possible for Roger G1 since it has radio partition unlike all other G1s and there you could upgrade the radio with flash_image.
speedysilwady said:
If anyone has any advice or a possible solution please keep us updated.
Thank you!
Click to expand...
Click to collapse
Yeap! I just practised how to un-root the phone straight to 1.6 with the original SPL and recovery and I was able to restore my phone to the state before rooting and I plan to give it back to my operator under warranty and ask to get this radio fixed. I will do it next week. I will report if the authorized service will be able to upgrade the radio.
Oliwer
Went to the new radio sent out by Flipz. Flipz you are great and all but the radio is not working out for me. I want to degrade back to the original. Suggestions.
You JUST made a topic about this.
TheBiles said:
You JUST made a topic about this.
Click to expand...
Click to collapse
I know I did. I tried to erase and make a my point a little bit more understandable. My bad.
yea give it a day or so to familiarize itself with your system and towers etc. i dont see how all these people are getting terrible results from it....and its not that hard to go back just ruu
You see I have tried to use the RUU wizard set up thru fresh. When I tried it I got an error.
there was a post a few days ago with the old radios in an update.zip format that you could flash from recovery, have you tried using that to downgrade yet?
Please read the following threads before trying anything. That way you are fully prepared.
http://forum.xda-developers.com/showthread.php?t=645002
http://forum.xda-developers.com/showthread.php?t=645435
http://forum.xda-developers.com/showthread.php?t=643796
http://forum.xda-developers.com/showthread.php?t=600720
http://forum.xda-developers.com/showthread.php?t=644417
http://forum.xda-developers.com/showthread.php?t=644004
People told me to flash the original radio in the same manner as the updated radio in nandroid. It did not work. Then they told me to RUU, that bricked or now semi-bricked my phone. I just think you should be prepared before you do anything. Running the RUU apparently does not work as well as some people think it does.
marcusva79 said:
Went to the new radio sent out by Flipz. Flipz you are great and all but the radio is not working out for me. I want to degrade back to the original. Suggestions.
Click to expand...
Click to collapse
What are your specific problems/issues with it?
crash447 said:
Please read the following threads before trying anything. That way you are fully prepared.
http://forum.xda-developers.com/showthread.php?t=645002
http://forum.xda-developers.com/showthread.php?t=645435
http://forum.xda-developers.com/showthread.php?t=643796
http://forum.xda-developers.com/showthread.php?t=600720
http://forum.xda-developers.com/showthread.php?t=644417
http://forum.xda-developers.com/showthread.php?t=644004
People told me to flash the original radio in the same manner as the updated radio in nandroid. It did not work. Then they told me to RUU, that bricked or now semi-bricked my phone. I just think you should be prepared before you do anything. Running the RUU apparently does not work as well as some people think it does.
Click to expand...
Click to collapse
So I am gonna take it from you man. I am pretty sure someone out there over the rainbow will make one to degrade the radio. i will settle with the radio for now, since I have no choice, well I already tried to use the RUU wizard, good thing I made a nandroid backup.
raadio flash is different than a regular flash nandroid wont get ya back to an older one
crash447 said:
People told me to flash the original radio in the same manner as the updated radio in nandroid. It did not work. Then they told me to RUU, that bricked or now semi-bricked my phone. I just think you should be prepared before you do anything. Running the RUU apparently does not work as well as some people think it does.
Click to expand...
Click to collapse
The problem is you are trying to use nandroid to flash an update.zip.
The radio will come as an update.zip format. Flash it like you would a new rom through recovery.
Nandroid does nothing for radio flashing. You can literally fry the phone's motherboard by flashing the wrong radio, I would know seeing as I did it to my first phone. lol
nbroneobi said:
raadio flash is different than a regular flash nandroid wont get ya back to an older one
Click to expand...
Click to collapse
I know that. Must be tired or something cause I am typing all weird. I did a nandroid recovery before I did the RUU wizard. And I glad I did. Cause I almost bricked my telefono.
willowmp said:
The problem is you are trying to use nandroid to flash an update.zip.
The radio will come as an update.zip format. Flash it like you would a new rom through recovery.
Nandroid does nothing for radio flashing. You can literally fry the phone's motherboard by flashing the wrong radio, I would know seeing as I did it to my first phone. lol
Click to expand...
Click to collapse
Maybe I shouldnt really do anything with the radio and just live it out with 2.1. I kinda of scared to fry or brick anything.
marcusva79 said:
I know that. Must be tired or something cause I am typing all weird. I did a nandroid recovery before I did the RUU wizard. And I glad I did. Cause I almost bricked my telefono.
Click to expand...
Click to collapse
how did making a nandroid recovery save you from bricking your phone??
okay so on the thread with the radios that Avalaunchmods posted, there was an error in the way he had his stock radio.img flash onto the phone. i'm attaching a signed stock radio that should flash correctly.
it SHOULD work. i don't see why it wouldn't work, because it is a CDMA radio and what it would do is just rewrite the old radio over the new radio. so i don't see a problem with this bricking any phones. but i don't take any liability if something goes wrong.
Just verify that you have the correct radio, and make sure it is coming from the CDMA Hero section and not the GSM section.
The real danger comes from flashing a GSM radio onto a CDMA hero. If you do this you will watch your phone kill itself.
I believe the radio was posted, though you could get it out of the RUU I think? Then you'd just need to request someone sign the zip and use it as an update.zip from recovery.
i took that radio.img from Avalaunchmod's thread. the radio that he got that out of was from the RUU, so yes, this is definitely a CDMA radio and its from the RUU.
justinisyoung said:
how did making a nandroid recovery save you from bricking your phone??
okay so on the thread with the radios that Avalaunchmods posted, there was an error in the way he had his stock radio.img flash onto the phone. i'm attaching a signed stock radio that should flash correctly.
it SHOULD work. i don't see why it wouldn't work, because it is a CDMA radio and what it would do is just rewrite the old radio over the new radio. so i don't see a problem with this bricking any phones. but i don't take any liability if something goes wrong.
Click to expand...
Click to collapse
Anyone want to try this. ARRRRRhj
just do exactly what you did to get the newer one on
justinisyoung said:
how did making a nandroid recovery save you from bricking your phone??
okay so on the thread with the radios that Avalaunchmods posted, there was an error in the way he had his stock radio.img flash onto the phone. i'm attaching a signed stock radio that should flash correctly.
it SHOULD work. i don't see why it wouldn't work, because it is a CDMA radio and what it would do is just rewrite the old radio over the new radio. so i don't see a problem with this bricking any phones. but i don't take any liability if something goes wrong.
Click to expand...
Click to collapse
Anyway to try this without nandroid. Since I am stuck in the "semi-bricked" limbo "fastboot oem boot" state.
justinisyoung said:
i took that radio.img from Avalaunchmod's thread. the radio that he got that out of was from the RUU, so yes, this is definitely a CDMA radio and its from the RUU.
Click to expand...
Click to collapse
Lol you posted before I finished my post.
Hi all, thanks in advance for any help and my apologies if this exact problem has already been resolved. I searched through this forum and found issues *similar* to my problem but nothing exact enough for me to find a solution.
My experience with Android is limited but have quite a bit of terminal UNIX experience...so I'm not a total noob and I can follow directions pretty well.
I purchased a MT3G from someone and everything seemed to be in order when I checked it out (and the price was good, so I figured I didn't have much to lose). He was running Cyanogen Mod on there but of course I wanted to restore to factory settings and build it up from scratch on my own. Thinking that I knew what I was doing, I booted into Recovery (Home/End key simultaneously) with no issues and ran the factory reset utility, thinking that this would just drop the phone back to factory settings and I could re-root it from there. When I turn the phone back on, it just hangs at the "splash" screen and runs the animation over and over again.
I can still boot into Recovery and I can get into Fast Boot so I hope I am not bricked.
Here is the output I get from Fast Boot (attached file).
I tried to restore with a SAPPIMG.zip that I found but it said wrong device...
Any help would be GREATLY appreciated. Thanks!
http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
If you get an error, you need to download an engineering spl, and then try. (Engineering 2010 SPL)
The link and instructions are around somewhere on XDA.
Thanks for the help!
Unfortunately I already tried that and it didn't work, so I guess I'll install the Engineering SPL when I get home.
Shouldn't I in theory just be able to flash another ROM over this one and have everything be back to normal?
Vontropnats said:
Thanks for the help!
Unfortunately I already tried that and it didn't work, so I guess I'll install the Engineering SPL when I get home.
Shouldn't I in theory just be able to flash another ROM over this one and have everything be back to normal?
Click to expand...
Click to collapse
Yes sir, that is the easy way!
there are plenty of 1.6, and 2.2 roms out there.
Just download to sdcard, boot into recovery, wipe and flash
Don't flash any SPLs. Your fine as long as you've got a custom recovery. Just flash another ROM from there and make sure you wipe data, dalvik-cache, and cache before flashing. I've been running CyanogenMod 5.0.8 since the summer (CM6 ran like crap) and I've been happy with it so far.
Sent from my HTC Magic using Tapatalk
Thanks for the advice guys.
Unfortunately I already flashed a different SPL and then un-rooted my device!
It works great, but now in order to get 2.2, I have to root it again which is a royal pain because I don't have a microSD reader and based on my research, the only way to root it it to make a goldcard!
Doh well! Learn something new everyday!
Vontropnats said:
Thanks for the advice guys.
Unfortunately I already flashed a different SPL and then un-rooted my device!
It works great, but now in order to get 2.2, I have to root it again which is a royal pain because I don't have a microSD reader and based on my research, the only way to root it it to make a goldcard!
Doh well! Learn something new everyday!
Click to expand...
Click to collapse
Not true you can root using the this app then use rom manager to install clockwork mod recovery. This is how I helped my friend root his device.
attached is the app
First of all, sorry if this is posted in the wrong place. Im pretty new to all this and don't really know how things work here.
I think im pretty buggered, and im pretty far out of my depth now. Im just posting to see if anything can be done or if it's already too late. Sorry if im missing something obvious that can fix this, however after 3 days of messing with this stuff my brain is starting to blur lol. Ok so here it is:
Tried updating to froyo via the OTA update pushed out recently. That failed and ive tried various ways of getting froyo to install over the last few days using Clockworkmod recovery. I ended up pushing a load of system files onto my phone via adb just to let the updater-script get past assert's. The point is, this was obviously a bad idea as I now have some kind of messed up copy of froyo installed which will not boot up past the HTC splash screen. Problem: the half-cocked update replaced the Clockworkmod recovery with the stock recovery so I now cannot use nandroid to push a backup back onto the phone
To make things worse when I boot into the stock recovery I also can't get into adb/shell, it detects the device but just says offline. Tried a lot of things to get round this but nothing has worked. So as ive got stock recovery and can't seem to get into adb anymore it would appear ive pretty much run out of options unless something can be done with fastboot... I don't know what im doing with that though so any help would be appreciated.
HTC Wildfire T-Mobile UK
S-ON
HBoot - 1.01.0001
Radio - 3.35.20.10
Recovery - Stock
Im at the end of the road here. If anyone has any ideas to try I would be very very grateful, otherwise il have to go see how much T-Mobile wants to repair it
Thanks in advance !
Undeadllama said:
First of all, sorry if this is posted in the wrong place. Im pretty new to all this and don't really know how things work here.
I think im pretty buggered, and im pretty far out of my depth now. Im just posting to see if anything can be done or if it's already too late. Sorry if im missing something obvious that can fix this, however after 3 days of messing with this stuff my brain is starting to blur lol. Ok so here it is:
Tried updating to froyo via the OTA update pushed out recently. That failed and ive tried various ways of getting froyo to install over the last few days using Clockworkmod recovery. I ended up pushing a load of system files onto my phone via adb just to let the updater-script get past assert's. The point is, this was obviously a bad idea as I now have some kind of messed up copy of froyo installed which will not boot up past the HTC splash screen. Problem: the half-cocked update replaced the Clockworkmod recovery with the stock recovery so I now cannot use nandroid to push a backup back onto the phone
To make things worse when I boot into the stock recovery I also can't get into adb/shell, it detects the device but just says offline. Tried a lot of things to get round this but nothing has worked. So as ive got stock recovery and can't seem to get into adb anymore it would appear ive pretty much run out of options unless something can be done with fastboot... I don't know what im doing with that though so any help would be appreciated.
HTC Wildfire T-Mobile UK
S-ON
HBoot - 1.01.0001
Radio - 3.35.20.10
Recovery - Stock
Im at the end of the road here. If anyone has any ideas to try I would be very very grateful, otherwise il have to go see how much T-Mobile wants to repair it
Thanks in advance !
Click to expand...
Click to collapse
You'll need a goldcard and an RUU. Look up how to make a goldcard and let me know when you have one
Wow, thanks for the quick reply
I did try creating a goldcard yesterday (using android.modaco.com/content/software/308798/pc-application-goldcardtool/). So assume I DO have one for the time being...
however if it doesn't work and I need to create a new goldcard:
Since I can't get into adb or boot up android and therefore can't access my sd card through my phone I presume il have to go out and buy a cheap card reader tomorrow.
Also, I have to run this command again:
adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
But if I can't get into adb how would I go about doing this, can I get the CID of the sd card from a card reader?
As for the RUU, there's many to choose from on shipped-roms.com, does this sound about right?
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35.15.19_release_130442_signed.exe
Thank you so much for your help.
This this a decent guide from Paul over at MoDaCo.
Ok disregard my last post about a card reader... I managed to borrow a friends android phone since it appears goldcard's are specific to the sd card, not the phone. So after following the instructions I now definitely have a goldcard.
Also have the RUU mentioned in the previous post.
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35. 15.19_release_130442_signed.exe
Is this right, and what do I do with these now to get them on my phone? Ive tried running the RUU whilst in Hboot and in recovery but it wont recognise my phone, presumably because adb isn't working.
Thanks again for the help.
There is another way to do it when it can only get into hboot. I'll look today for the method and let you know.
Sent from my HTC Wildfire using XDA App
Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system.
Only worked because T-Mobile's OTA was a slightly older version 2.21.110.2, thank god there was a newer version available on the interwebs.
Probably not the best way of doing it but im just glad ive got a working phone again.
Thanks for replying though.
Just on a side note... its bloody ridiculous that its so hard to downgrade android!!! It causes people like me, who don't really know what they're doing, large quantities of banging-head-against-wall sessions
Undeadllama said:
Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system.
Only worked because T-Mobile's OTA was a slightly older version 2.21.110.2, thank god there was a newer version available on the interwebs.
Probably not the best way of doing it but im just glad ive got a working phone again.
Thanks for replying though.
Just on a side note... its bloody ridiculous that its so hard to downgrade android!!! It causes people like me, who don't really know what they're doing, large quantities of banging-head-against-wall sessions
Click to expand...
Click to collapse
Yeah that's the method I was going to suggest, glad you sorted it out.
It's the fact that they lock out fastboot and stuff. If we had S-OFF from the factory, fixing these things would be so much easier
Hi,
how were you able to do this?
"Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system. "
Thanks