Related
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.
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
Hi guys, hopefully I'm not in too much trouble here, I seem to have flashed my radio improperly... I'm using the Rogers Magic+ w/ Amon_RA recovery 1.7.
Here were my steps:
- Started on the Old Radio (I switched to it using the Radio Switcher batch file from this forum)
- Decided to go back to the New Radio
- Flashed ONLY the new radio 6.35.10.18 in fastboot (not changing anything else, it didn't occur to me I needed to change hboot etc as well :S) In other words, I'm on radio 6.35.10.18, but HBOOT 1.33.2010
- Tried to boot into Recovery, but my phone kept rebooting
- Booted into fastboot and ran the Radio Switcher batch to do it properly this time
- Radio was sent fine, but now my phone is stuck writing the radio (at 90%). It's just sitting there right now for 5+ minutes, I don't want to reboot in case I do more damage
What should I do? How can I safely restart the radio switch process?
Thanks guys!
*phew* disaster averted it seems...
I had to remove the battery, but then booted back into fastboot successfully. From there I re-ran the radio switcher batch and it successfully completed all operations.
Then I could boot into recovery and install a new rom. Here's hoping everything still works properly :S
Just in case anyone else reads this and wonders - DON'T FLASH THE RADIO WITHOUT FLASHING THE CORRECT HBOOT AS WELL! Unless you're 1000% sure of what you're doing, use the Radio Switch tool to remove any guessword!
Moved to General since it's not about ROM Development.
I recently got back a warranty swap Nexus One with an old version of android (2.2) and thought to myself "Hell, I might as well try rooting for once since it the 1-click method doesn't unlock the bootloader and you can always go back right?" Wrong
Well, I updated the radio as part of the Cyanogen 6.1 installation to radio version 5.12.00.08 and now that I don't want to be rooted anymore I can't seem to get the radio version back to normal to what it should be on 2.2.1
The 2.2.1 radio should be: Baseband version 32.36.00.28U_4.06.00.12_7
But when I updated to 2.2.1 it stayed the same: Baseband version 32.50.00.32U_5.12.00.08
Have I screwed up my radio? I just want to get my phone back to normal please help
ap3604 said:
I recently got back a warranty swap Nexus One with an old version of android (2.2) and thought to myself "Hell, I might as well try rooting for once since it the 1-click method doesn't unlock the bootloader and you can always go back right?" Wrong
Well, I updated the radio as part of the Cyanogen 6.1 installation to radio version 5.12.00.08 and now that I don't want to be rooted anymore I can't seem to get the radio version back to normal to what it should be on 2.2.1
The 2.2.1 radio should be: Baseband version 32.36.00.28U_4.06.00.12_7
But when I updated to 2.2.1 it stayed the same: Baseband version 32.50.00.32U_5.12.00.08
Have I screwed up my radio? I just want to get my phone back to normal please help
Click to expand...
Click to collapse
Does the phone still function? Making calls, sending texts.. etc?
If so, then whats the problem? The radio update was probably included in the ROM you flashed, if you're experiencing problems, search the forum for the Radio you want and instructions on how to flash
Be careful though, you can brick your phone when flashing a radio.. so make sure you read the instructions..
Good Luck
S_Dot said:
Does the phone still function? Making calls, sending texts.. etc?
If so, then whats the problem?
Click to expand...
Click to collapse
2 things I am worried about:
1. Before I rooted and changed the radio, I could check for system updates and it would say I could to update to 2.2.1 ota... Now, after I unrooted and got it back to stock 2.2, I would check system updates and it no longer gave me the option to update to 2.2.1 (I had to manually do this)
This worries me since I don't want to miss out on all future ota updates if my radio has been screwed up when I flashed one earlier.
2. Radio has been slower since upgrading manually to 2.2.1 but still having the old radio in place.
Isn't the each radio optomized for the particular android build?
Also what about rooting causes the phone not to get the new ota update? Is it the changing of its radio?
What country is yor phone? And with what build did it came after warranty?
My guess the radio is just part of the update (if you flashed a stock rom)
I recently bought my nexus in holland it came with FRF91
And 5.08.00.04 radio so
Radio isn't per build.
There was a major change to adjust to Froyo in 4.06 radio, all the above are compatible with it, all the 4.04 and below are compatible with Eclair and not suitable for Froyo.
2.2.1 includes 5.08 anyway. Your not getting OTA doesn't have anything to do with radio.
You can flash any radio you want when you're rooted, using the guide found in Wiki.
Yeah I've benefited from newer radios. Dont sweat it your rooted, this is good.
Sent from my Nexus One using XDA App
ap3604 said:
Also what about rooting causes the phone not to get the new ota update? Is it the changing of its radio?
Click to expand...
Click to collapse
It's the rom and recovery.
I really would not get stressed out about this. Worst case scenario is that you have to come on xda every so often and flash the update manually.
LOL, if ur on CM6 u already have 2.2.1 and worrying about future otas, root user update to latest version normally before unrooted people and u should have to problem updating, if u want to revert back to the old boring stock version just flash one of the shipping roms in bootloader by renaming them to PASSIMG.zip
ap3604 said:
I recently got back a warranty swap Nexus One with an old version of android (2.2) and thought to myself "Hell, I might as well try rooting for once since it the 1-click method doesn't unlock the bootloader and you can always go back right?" Wrong
Well, I updated the radio as part of the Cyanogen 6.1 installation to radio version 5.12.00.08 and now that I don't want to be rooted anymore I can't seem to get the radio version back to normal to what it should be on 2.2.1
The 2.2.1 radio should be: Baseband version 32.36.00.28U_4.06.00.12_7
But when I updated to 2.2.1 it stayed the same: Baseband version 32.50.00.32U_5.12.00.08
Have I screwed up my radio? I just want to get my phone back to normal please help
Click to expand...
Click to collapse
1) From where did you upgrade to 2.2.1?
if you upgraded from rom manager or any ROM given by developer, they remove the radio and provide it as a separate update file.
http://www.tap3w0rm.com/hosted/android/radios/nexus-1/FRF50-radio-4_06_00_12_7.zip is the update for radio you want.
2) However, Radio update is not what you want. "Recovery" is what you want. Recovery is a piece of software that allows you to flash custom ROMS. did you install Amon's recovery or Clockwork (from ROM Manager) recovery?
You will not get OTA if you have one of these custom recoveries. you will need the stock recovery.
3) In short, you need to flash your phone with a completely stock google ROM.
follow these instructions
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
hmmm interesting...what makes you wanna unroot besides OTA? From what I see that's virtually no advantage to go back to stock rom
If you really want official OTAs, just make sure you check xda often when those are pushing out. There will be stock OTA updates hanging around.
Try this:
http://djmcnz.batteryboss.org/Kang-o-rama/froyo/radio/froyo-radio-update-signed.zip
Flash it from custom recovery. It will reboot, unpack the radio, reboot again in a few minutes, and you should end up back on the 4.06 radio. For what it's worth.
If you want to go back to totally stock unrooted, the most complete way to do so is using a PASSIMG file.
arkavat said:
However, Radio update is not what you want. "Recovery" is what you want. Recovery is a piece of software that allows you to flash custom ROMS. did you install Amon's recovery or Clockwork (from ROM Manager) recovery?
You will not get OTA if you have one of these custom recoveries. you will need the stock recovery.
Click to expand...
Click to collapse
I installed Clockwork recovery when I first did the Cyanogen flash so how do I know if I still have it on my phone blocking OTA updates?
I had an old 2.2.1 update.zip on my SDcard from an old Nexus One that I sent in through a warranty swap.
Then I powered off and did the whole Volume Down + Power button.
I get the screen with the 3 androids on skateboards and clicked on Recovery
I press on recovery
When I see the triangle with exclamation mark I press power button + volume up and the only options I see are reboot system now, install update.zip from sd card, factory reset, wipe cache
I click on install update.zip (2.2.1) and reboot system now so the phone reboots but I still am stuck with the old radio. How do I know if I have stock recovery and will get OTA updates from now on?
arkavat said:
In short, you need to flash your phone with a completely stock google ROM.
follow these instructions
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Click to expand...
Click to collapse
I tried the steps exactly (PASSIMG.ZIP on sd card) but when I do the power + volume down step 7 doesnt happen. There isn't any screen looking for update files. I get the screen with the 3 skateboarding androids instead and no way to get the PASSIMG.ZIP file to work.
Can't you download a unrooted 2.2 rom from rom manager and then ota once its installed? Dont quote me though I've never actually tried to unroot
Sent from my Nexus One using XDA App
ap3604 said:
I tried the steps exactly (PASSIMG.ZIP on sd card) but when I do the power + volume down step 7 doesnt happen. There isn't any screen looking for update files. I get the screen with the 3 skateboarding androids instead and no way to get the PASSIMG.ZIP file to work.
Click to expand...
Click to collapse
On my phone this is what I get in bootloader mode...
I start up the phone holding down the trackball, and I get the Fastboot with the skateboards. The first menu option, BOOTLOADER, is highlighted. I press Power and I get to the HBOOT screen (also with skateboarding androids). I wait 5-10 seconds and it checks for a PASSIMG on SD. Since I don't have one, it finds nothing and returns me to HBOOT.
Or alternately I boot while holding volume down and I get HBOOT directly. In 5-10 seconds it checks for PASSIMG. The only time it won't do that is if my SD is not installed.
You're saying that on yours it doesn't check for PASSIMG at all?
I am in a somewhat similar boat (though not exactly), a colleague of mine purchased a used Nexus One off of fleebay and it came rooted running Cyanogen 6 with Clockwork Recovery (for the Recovery Image).
My colleague wants it to be completely stock (which I do not understand as I find Cyanogen 6 to be far better) and asked me the resident Android guy if I could help.
I figured PASSIMG.zip was the way to go and downloaded the stock rom from developer.htc.com and renamed it PASSIMG.zip. I put the PASSIMG.zip file on his SD card and booted into the bootloader. It checks the PASSIMG.zip image but does not offer me option to install it. It simply checks it and then offers me the normal 4 options.
Any thoughts?
Dan
Read the Wiki, it has specific reference to FRG83 stock ROM now, which refuses to work in PASSIMG mode.
dan1431 said:
I am in a somewhat similar boat (though not exactly), a colleague of mine purchased a used Nexus One off of fleebay and it came rooted running Cyanogen 6 with Clockwork Recovery (for the Recovery Image).
My colleague wants it to be completely stock (which I do not understand as I find Cyanogen 6 to be far better) and asked me the resident Android guy if I could help.
I figured PASSIMG.zip was the way to go and downloaded the stock rom from developer.htc.com and renamed it PASSIMG.zip. I put the PASSIMG.zip file on his SD card and booted into the bootloader. It checks the PASSIMG.zip image but does not offer me option to install it. It simply checks it and then offers me the normal 4 options.
Any thoughts?
Dan
Click to expand...
Click to collapse
Try as update.zip through custom recovery? Then clear the custom recovery by flashing stock one...then delete superuser.apk + unroot?
liam.lah said:
It's the rom and recovery.
[snip]
Click to expand...
Click to collapse
Actually, it's just the ROM. Even if you have a custom recovery: a rooted, stock ROM will still receive OTA updates...
Yes but on quite a few custom recoveries, it will fail to install due to the signature.
Rusty! said:
Yes but on quite a few custom recoveries, it will fail to install due to the signature.
Click to expand...
Click to collapse
True. If you are using anything earlier than Amon_RA 1.8 or the latest ClockworkMod, it won't install.
I feel like I have looked everywhere but forgive me if I missed a thread that may answer this.
I don't know if this is a hardware or software issue.
I installed HSPL 2.08 successfully
I then installed MAGLDR 1.13 successfully
Flashed my phone with HD2_Core_Droid_Desire_HD_V1.5_NAND_ONLY_LEO1024_TMOUS successfully
Android booted fine and worked for about a day and a half. My phone froze up and had to remove battery. Now it only boots to white screen.
I have attempted to reinstalled MAGLDR without success
I have attempted to change my HSPL back to SPL to install OEM Rom without success HSPL says it was successful but bootloader screen says different.
I read in a thread that it could be a radio conflict (though I don't know why it would work for a day and then stop) but I can't install a radio ROM. I get Error 207 Image file corrupted.
I have read threads about flashing from the SD card by extracting the signed_RUU.nbh file from the stock ROM, but I have no idea how to do that. I do not have the extract option on the exe file of the stock ROM I download...and I have downloaded several versions.
Please help.
Hookwitz said:
I feel like I have looked everywhere but forgive me if I missed a thread that may answer this.
I don't know if this is a hardware or software issue.
I installed HSPL 2.08 successfully
I then installed MAGLDR 1.13 successfully
Flashed my phone with HD2_Core_Droid_Desire_HD_V1.5_NAND_ONLY_LEO1024_TMOUS successfully
Android booted fine and worked for about a day and a half. My phone froze up and had to remove battery. Now it only boots to white screen.
I have attempted to reinstalled MAGLDR without success
I have attempted to change my HSPL back to SPL to install OEM Rom without success HSPL says it was successful but bootloader screen says different.
I read in a thread that it could be a radio conflict (though I don't know why it would work for a day and then stop) but I can't install a radio ROM. I get Error 207 Image file corrupted.
I have read threads about flashing from the SD card by extracting the signed_RUU.nbh file from the stock ROM, but I have no idea how to do that. I do not have the extract option on the exe file of the stock ROM I download...and I have downloaded several versions.
Please help.
Click to expand...
Click to collapse
I have no idea what is happening with your phone and why is it happening... But I can tell yoy one thing. Whenever I had any problems when phone would not go further one step, I would do TASK29 and follow all the steps all over again. TASK29 is sth like wiping everything off your NAND. Hope it helps.
I kind of think this is a hardware issue... My boys did the same thing... Never got it back up and running.
Sent from my HTC HD2 using XDA App
what about the radio ?
do task 29 and flash radio if you haven't (ignore if you did it earlier) then install MAGLDR and flash the rom from within MAGLDR or follow whatever instructions the developer has posted in his thread.
I too have tried everything and although magldr and wm6.5 both flash from sd, still wsod. My advice is take it to tmobile, and talk them into admitting its a hardware problem ;-)
Sent from my HTC HD2 using XDA App
I forgot to mention I did try the Task29 and it too failed. So I am thinking it is a hardware issue.
UPDATE: I figured out where to find the .nbh files in my temp folder and was able to copy and paste them to the SD card. I have also gotten to the image load screen to flash the leoimg.nbh file. However all of them fail at RADIO and subsequently fail the update. I have tried new and old stock ROM and the Radio ROM by itself. I also used the Task29 nbh file and was successful in flashing that from my SD card ... but the HSPL is still there at the boot loader screen.
I can't seem to figure out what is causing the fail.
Thoughts anyone?
Sorry
HD2_Core_Droid_Desire_HD_V1.5_NAND_ONLY_LEO1024_TM OUS successfully
Did you check is this version quiet similar to your phone's hardware configuration
Ram 1024
My version is compatible. Again, it was running fine. In fact, I have a phone previous that I installed it and it worked beautifully but I dropped and shattered the screen. When I got this new one (same model) I performed the installation the exact same way. It worked a day and a half and then froze.
Based on other searches, it looks like I may have bricked my radio.
UPDATE:
I think I was able to solve this and hopefully I won't be as cryptic as someone else who had a similar problem. Don't Give Up is good advice however attempting the same time over and over is probably not the best.
This is what I did ... after banging my head at the redundancy.
I used NBHExtract from the NBHExtract forum on the Stock ROM T-Mobile_HD2_MR_Software_2.13.531.1 that I downloaded from T-Mobile. This extracted all the .nb files and thankfully they were well labeled.
I then used the NBH Creator from the NBH Creator forum (yes you will have to register to download this application.)
In the NBH Creator I used the settings provided to me in the NBHExtract window and used the SPL, Splash, and OS only ... leaving the Radio blank.
I created the leoimg.nbh file and put that on a blank 2Gig FAT32 formated SD card.
Booted the phone in Bootloader.
The update failed however it uninstalled the HSPL
From here I did a Hard Reset to clear the ROM Update failure message on the tri-color screen.
I attempted to update the ROM via USB to the 3.14 version (again downloaded from T-Mobile's site). This got to 4% and failed. I now had the warning triangle symbol on my screen indicating the Software Update failed and to try again.
I tried again however this time with the 2.13 version (the ROM I extracted at the beginning) via USB. This time is successfully installed.
This is probably not a fool-proof nor verified option, however it worked for my phone model PB8112000. It might work for you.
I am tempted to try Android again, however, I don't know if the radio issue was hardware or software.