Related
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
I've flash with a froyo rom , and now, I just want to get back to eclair or a baked froyo, that rom is full of problem : not a real android market(htc market) chinese apps, and the worst : I can't use the web browser but I can get my emails.
So if someone got an idea to root that rom or to roll back to a previous version , I'm open to your propositions.
I've already try with unrevoked/an other RUU rom (with and without a goldcard).
I used the froyo rom from shipped-roms
You need to do a full wipe from recovery before flashing the new rom.
thanks for the idea ;
I've tried, but the recovery mod doesnt load properly.
unrevoked shows that somes files aren't found while it's pass from HBOOT to HBOOT USB PLUG , and i'm not able to select recovery with the volume button in the HBOOT menu.
I think you have to wait for alpha rev :/
Same thing happened to me. Now my phone is not syncing Google or facebook contacts. The rom is very much limited. What i foundout was, the ruu update. Has also upgraded the hoot to version .83 from .80. That is the reason other ruus and unrevoke crash. Downgrading the hboot will do the trick. There are methods avaiable for desire but im not. sure they will work with. Wildfire. If the hoot is same for desire and wildfire rename the zip file. As PC49IMG.zip should downgrade the hoot. Any help is apnpreciated.
alparev will not help cos u need root for it, least on website is info Requirements:
The only requirement right now is that the ROM you're running is rooted.
adrienlm said:
unrevoked shows that somes files aren't found while it's pass from HBOOT to HBOOT USB PLUG , and i'm not able to select recovery with the volume button in the HBOOT menu.
Click to expand...
Click to collapse
yes, becos adbd is in other place, not in system.img as usual but in boot.img and adbd is different from every other adbd
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.
Today I accidently turned it on (the thing in the bootloader) and now I can't turn it off no matter what so I can do a revert to stock .img, I used the PDI15.img or w.e that would revert back to stock forgetting that I had the newest radio and now I can't revert to stock or turn S-OFF. Please help
Current Configurations:
GLACIER PVT SHIP S-ON
HBOOT - 0.86.0000
MICORP - 0429
RADIO - 26.09.04.26_M
eMMC - BOOT
More Info:
When I use a PDIMG or w/e file it errors out as being old
Can you still boot? Like into your rom? If so just try rooting using visionary and using a root explorer to push the gfree files to data/local/ then just follow the normal rooting procedure
Sent from my HTC Glacier using XDA Premium App
Nicgraner said:
Can you still boot? Like into your rom? If so just try rooting using visionary and using a root explorer to push the gfree files to data/local/ then just follow the normal rooting procedure
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Yeah I can still boot into my rom, bootloader, and recovery and okay will try that
EDIT: Okay I did, I tried turning S-OFF but it says something about eMMC power cycle failed
XxKOLOHExX said:
Yeah I can still boot into my rom, bootloader, and recovery and okay will try that
EDIT: Okay I did, I tried turning S-OFF but it says something about eMMC power cycle failed
Click to expand...
Click to collapse
dude! I noticed this also this morning. I am rooted(using setcpu and root explorer just fine) but in hboot it says s=on. I was also wanting to flash the stock .img and start fresh. thought I was the only one having this problem. tried everything you did and got the same results.
What ROM are you on? AFAIK, gfree, requires the stock kernel to do what it does. How on earth did you turn S-ON? That sort of thing shouldn't just happen out of nowhere.
How is the progress on fixing your phone?
jdkoren said:
What ROM are you on? AFAIK, gfree, requires the stock kernel to do what it does. How on earth did you turn S-ON? That sort of thing shouldn't just happen out of nowhere.
Click to expand...
Click to collapse
currently on Evil D mTGB v1.0, Faux 0.0.7 CFS lv leak kernel. everything works fine, no FC's or anything. just having the same issues as XxKOLOHExX. I really have no idea how it turned on by itself, I dont remember doing anything out of the ordinary
I was trying to get back to stock from the rom i was on. (MIUI) and when I used the stock .img though the bootloader it went all good till it rebooted, then it said failed because the file was old and now I am stuck with s-on and I don't know how to turn it off
How did you get to the stock bootloader? Did you have eng bootloader at one point? What meth of root did you use? Alot of info missing.
Now download the stock radio.img and push it via adb or just download the PD15IMG.zip (radio only not rom included). Once this is done you can revert back to stock rom/radio using standard PD15IMG.zip (radio+rom). Now depending on the type of root you used it would depend if you still have radio flag on/off even if your reverted back to stock bootloader.
PS: You can get PD15IMG.zip (stock radio) from master radio thread and PD15IMG.zip (stock radio/rom) by doing search.
PermROOT said:
How did you get to the stock bootloader? Did you have eng bootloader at one point? What meth of root did you use? Alot of info missing.
Now download the stock radio.img and push it via adb or just download the PD15IMG.zip (radio only not rom included). Once this is done you can revert back to stock rom/radio using standard PD15IMG.zip (radio+rom). Now depending on the type of root you used it would depend if you still have radio flag on/off even if your reverted back to stock bootloader.
PS: You can get PD15IMG.zip (stock radio) from master radio thread and PD15IMG.zip (stock radio/rom) by doing search.
Click to expand...
Click to collapse
It flashed the bootloader when I flashed the PD15IMG.zip, it just stop when I did the whole procedure. Nope never flashed an Engineer Bootloader. I used theunlockr.com sites method
I tried that, it uziped then tried to flash the radio then just went back to the original menu for the bootloader
If you used the VISIONary+ (TempROOT) and root.sh (PermROOT) meth then you already had engineering hboot (0.85.2007) pushed though terminal on "/dev/block/mmcblk0p18". Now you did something in between is what I would like to know.
As you flashed new radio (26.09.04.26_M) which I am clear. But what I like to know is how did you end up with default hboot (0.86.0000)? If you had S=OFF you didn't lose it via flashing new radio. Which PD15IMG.zip did you install? Now when you say PD15IMG.zip what do you mean? It can be anything as its default mt4g system based image. Stock PD15IMG.zip = (Sense 2.2.1 Rom/Radio 26.03.02.26_M). Did you install leaked PD15IMG.zip from Panache? or GB2.3.3S?
Are you not 1 of the Royal dev's? who try to take over Silence's IG if I recall. I am just assuming here but this is why you do "NOT" dump system image via hboot. What you should have done was do complete total system wipe (format /data; /system) and then flash new edify based CWMR flashable rom.
PermROOT said:
If you used the VISIONary+ (TempROOT) and root.sh (PermROOT) meth then you already had engineering hboot (0.85.2007) pushed though terminal on "/dev/block/mmcblk0p18". Now you did something in between is what I would like to know.
As you flashed new radio (26.09.04.26_M) which I am clear. But what I like to know is how did you end up with default hboot (0.86.0000)? If you had S=OFF you didn't lose it via flashing new radio. Which PD15IMG.zip did you install? Now when you say PD15IMG.zip what do you mean? It can be anything as its default mt4g system based image. Stock PD15IMG.zip = (Sense 2.2.1 Rom/Radio 26.03.02.26_M). Did you install leaked PD15IMG.zip from Panache? or GB2.3.3S?
Are you not 1 of the Royal dev's? who try to take over Silence's IG if I recall. I am just assuming here but this is why you do "NOT" dump system image via hboot. What you should have done was do complete total system wipe (format /data; /system) and then flash new edify based CWMR flashable rom.
Click to expand...
Click to collapse
Yeah I know that, I Was trying to go back to stock everything using the unrooting method(PD15IMG.zip). Using this file I was able to get through the first step and it rebooted, then it went back to bootloader and now it won't take the PD15IMG.zip saying that it is an older file. Yes I am one of the devs, That's why before posting I tried everything I could think of, gfree, old unrooting methods, etc. I didn't use a dump lol I'm not that noobish haha
Thats where you got owned as the PD15IMG.zip (stock rom/radio) just reverted back to hboot (0.86.0000) from eng hboot (0.85.2007). While you attempted to go further you couldn't do to security turning on (S=ON). Now this normally wouldn't be problem but since you had newer radio (26.09.04.26_M) it wouldn't replace it with old.
All you had to do was follow few simple meths which you should have learned it over the years. Go back same way you came by first reverting back to original radio image and then after doing complete system wipe you should have reverted back to original factory based via stock pd15img.
Ill post back with solution soon let me think this out. I don't want to brick your phone trying to manually push the radio.img nor the eng_hboot.img. As if you try to push radio now would fail on write and give you hard brick. Since S=ON and if you try to push eng_hboot.img who knows what will happen as no R/W access on mmcblk could could also fail thus giving bad flash which can also brick the device. Ill see what happens and post back at... you folks just made more extra work for me.
PermROOT said:
Thats where you got owned as the PD15IMG.zip (stock rom/radio) just reverted back to hboot (0.86.0000) from eng hboot (0.85.2007). While you attempted to go further you couldn't do to security turning on (S=ON). Now this normally wouldn't be problem but since you had newer radio (26.09.04.26_M) it wouldn't replace it with old.
All you had to do was follow few simple meths which you should have learned it over the years. Go back same way you came by first reverting back to original radio image and then after doing complete system wipe you should have reverted back to original factory based via stock pd15img.
Ill post back with solution soon let me think this out. I don't want to brick your phone trying to manually push the radio.img nor the eng_hboot.img. As if you try to push radio now would fail on write and give you hard brick. Since S=ON and if you try to push eng_hboot.img who knows what will happen as no R/W access on mmcblk could could also fail thus giving bad flash which can also brick the device. Ill see what happens and post back at... you folks just made more extra work for me.
Click to expand...
Click to collapse
Thank you so much for the help
PermROOT said:
Thats where you got owned as the PD15IMG.zip (stock rom/radio) just reverted back to hboot (0.86.0000) from eng hboot (0.85.2007). While you attempted to go further you couldn't do to security turning on (S=ON). Now this normally wouldn't be problem but since you had newer radio (26.09.04.26_M) it wouldn't replace it with old.
All you had to do was follow few simple meths which you should have learned it over the years. Go back same way you came by first reverting back to original radio image and then after doing complete system wipe you should have reverted back to original factory based via stock pd15img.
Ill post back with solution soon let me think this out. I don't want to brick your phone trying to manually push the radio.img nor the eng_hboot.img. As if you try to push radio now would fail on write and give you hard brick. Since S=ON and if you try to push eng_hboot.img who knows what will happen as no R/W access on mmcblk could could also fail thus giving bad flash which can also brick the device. Ill see what happens and post back at... you folks just made more extra work for me.
Click to expand...
Click to collapse
lol sorry for the extra work, just dont wanna have the chance of bricking my phone but like XxKOLOHExX I wanted to revert back to stock from mTGB using the stock PD15IMG_Glacier_TMOUS_1.17.531.2_Radio_12.28b.60.140e_26.03.02.26_M_release_155771_signed. everything he described is happening to me also, step by step. I rooted with the visionary+ and permroot method(unlockr). I did download and flash the 26.08.04.30 radio. heres what I see in hboot
GLACIER PVT SHIP S-ON
HBOOT-0.86.0000
MICROP-0429
RADIO-26.08.04.30_M3
eMMC-boot
Sep 27 2010, 11:12:59
so what youre saying is that we should try flashing the stock radio first, wipe the whole phone(including sdcard?), then flash the stock PD15IMG? Ill give it a shot real quick, thanks
*edit* hboot wont even let me flash the stock radio, itll say checking but wont actually let me update it
Well clarknick27 the problem here is that root.sh to gain PermROOT via VISIONary+ just push the 0.85.2007 eng hboot and giving temporary S=OFF, the true security flag as we know it is controlled in the radio. So when you try to revert back using stock PD15IMG (rom/radio) it reverted back to the stock 0.86.0000 hboot thus turning on the security flag on.
What you all should have done is reverted back same way you installed it. Which would have been first use PD15IMG.zip (stock radio) and then use stock PD15IMG.zip (radio/rom). I still need some sleep lol I just wokeup after sleeping 2hours.
The MT4G I tested on I rooted it via VISIONary+ and then flashed GB Leak rom not the PD15IMG.zip (leak radio/rom) which contained the 0.89.0005 hboot. So after flashing stock radio PD15IMG.zip (radio 26.03.02.26_M) I was able to flash stock PD15IMG.zip (rom/radio) without problem. Which is same as I suspected even after S=ON due to same version radio no problem. If I had newer radio after that point it would be locked out. Let me go to sleep and wakeup and ill see what happens from there. As I have clean MT4G ill have to reroot it first.
BTW XxKOLOHExX and clarknick27 just in case my account gets disabled. Do the following and report it here and ill see from there.
1) Which working rom you currently have installed on the device?
I know trying to reroot using gfree may give you similar result as my test: http://forum.xda-developers.com/showthread.php?t=1066966 < not important but unable to root on newer rom.
2) What happens when you try to reroot it using VISIONary+ (TempROOT) and root.sh (PermROOT)?
Did you try it? If so what is the end result? so post back. Ill check and go from there.
PermROOT said:
BTW XxKOLOHExX and clarknick27 just in case my account gets disabled. Do the following and report it here and ill see from there.
1) Which working rom you currently have installed on the device?
I know trying to reroot using gfree may give you similar result as my test: http://forum.xda-developers.com/showthread.php?t=1066966 < not important but unable to root on newer rom.
2) What happens when you try to reroot it using VISIONary+ (TempROOT) and root.sh (PermROOT)?
Did you try it? If so what is the end result? so post back. Ill check and go from there.
Click to expand...
Click to collapse
1) currently running Evil D's mTGB v1.0 rom with Faux's 0.0.7 CFS LV leak kernel. tried rooting with visionary and terminal first, no success. I then tried out the gfree method, and got "Attempting to power cycle eMMC...failed. Module failed to load: No such file or directory."
2) I installed Visionary using Astro file manager, then run Visionary. I click on "temproot now" and it starts, but then the screen goes black and doesnt do anything. I have let it sit on the black screen for well over 15mins before with no luck. I can click on "attempt to permroot" and it will ask for permissions and reboot and everything. my s=on but I still have root access and 0.86.000 bootloader. this is what I see using terminal before rebooting to see if s=off
Did you do the Radio S=OFF using gfree? If so that would explain why you still have root as security is disabled on the device totally. If thats the case then just push the eng bootloader manually via adb or though terminal and reboot. For now XxKOLOHExX is locked lets see what I find ill post back for him.
PermROOT said:
Did you do the Radio S=OFF using gfree? If so that would explain why you still have root as security is disabled on the device totally. If thats the case then just push the eng bootloader manually via adb or though terminal and reboot. For now XxKOLOHExX is locked lets see what I find ill post back for him.
Click to expand...
Click to collapse
thanks for taking the time to help out, Ill give it a shot
*edit* just tried pushing the eng bootloader through adb and it didnt stick or flash, rebooted into hboot and it still says 0.86.0000, s=on, 26.08.04.30_M3 radio
Device doesn power on after pwr off. on power on vibrates 3 times & orange LED flash
ok. here goes.
On rebooting my phone last night it doesnt come back on. It vibrates 3 times and the LED flashes orange.
The only way it comes back on is if i take out the battery for a while and then power it on again.
here is a chronology of what happens.
reboot or power down
devices powers off but doesnt restart. vibrates 3 times and the LED flashes orange.
pull out the battery and SDCARD and wait a minute.
After this I can now boot into CM7
Reboot or power off to restart. same thing happens again
this happens everytime i power down the device
things i have noticed
on plugging it into my PC it recognises my device as a qualcomm_cdma_technologies msm desire and tries to install drivers for it.
this is the first time i have seen this. My device is GSM based and i am on tmobile UK.
Device can never power back on immediately from power off. just vibrates 3 times, LED flashes. Only comes back when i pull battery and SD and wait a few seconds before powering it back on
What i have tried but they all dont solve it
flashing a new cwm recovery. i am able to flash a new one from rom manager but doesnt solve the problem. currently on Rom manager 4.2.0.2 and CWM 3.0.2.6
formatting my SDCARD through ROM Manager.
doing a full wipe and reflashing stable CM7.
all of these completed successfully with no errors
What i can do successfully
i can boot into bootloader and recovery from commandprompt or using the power+volume down combination. doesnt always power on because of the no boot (start) problem .
i can do "adb devices" and successfully see my device as HT0****** in the list of devices
On the terminal app, on typing "su" it gains root permission successfully.
i can succesfully access my SDCARD using astro and also using mount usb storage in recovery.
device information
HTC DEsire hd.
CM7.0.3 stable, previously on nightly CM_ace_full 83
ROM manager version 4.2.0.2
CWM 3.0.2.6
Radio 26.09.04.11_M2
hdboot-0.85.2007 (PD9810000)
ACE PVT ENG S-OFF
USBdebugging always on
please let me know if any further information is needed and how to get it.
I really need some help. I have trawled the forums and i am starting to believe that i have a partially bricked device or a usb brick. I havent seen any real solutions or any post with a problem like mine so i want to be sure that that is the issue before trying the fixes there. Is there any thread for fixing a Desire HD USB brick, because all the ones i have seen do not have a definite fix.
Hi,
I think you maybe close to hardware failure. I would perform a full backup of apps & data and restore a HTC RUU (1.32.405.6). Then if your problem still persists send it away for repair.
andyharney said:
Hi,
I think you maybe close to hardware failure. I would perform a full backup of apps & data and restore a HTC RUU (1.32.405.6). Then if your problem still persists send it away for repair.
Click to expand...
Click to collapse
Thanks andy.
In flashing the HTC RUU. is that the process of removing root?. because i was thinking of removing root and then sending it back. but thought there might be a software fix for it i could try first.
Yes, flashing via RUU will remove root and ENG S-OFF. It will not restore Radio S-ON. It's probably advisable to use jkoljo's Radio S-OFF tool again to restore it and CID:HTC__001.
andyharney said:
Yes, flashing via RUU will remove root and ENG S-OFF. It will not restore Radio S-ON. It's probably advisable to use jkoljo's Radio S-OFF tool again to restore it and CID:HTC__001.
Click to expand...
Click to collapse
im vey sorry andy. im now so scared of making this worse.
i have found jkoljos post here http://forum.xda-developers.com/showthread.php?t=857537 and i am going to try the instructions there but i do not understand the CID part. because after flashing the ruu i am supposed to do a temp root. id i remember correctly temp rppt reverts back to stock after reboot. or do i have to flash the RUU again.
sorry for the questions. havent had any sleep all night because of this and i am quite scared i will make it worse. i am going to do it now and will let you know.
santet said:
im vey sorry andy. im now so scared of making this worse.
i have found jkoljos post here http://forum.xda-developers.com/showthread.php?t=857537 and i am going to try the instructions there but i do not understand the CID part. because after flashing the ruu i am supposed to do a temp root. id i remember correctly temp rppt reverts back to stock after reboot. or do i have to flash the RUU again.
sorry for the questions. havent had any sleep all night because of this and i am quite scared i will make it worse. i am going to do it now and will let you know.
Click to expand...
Click to collapse
I recently had to send mt phone back to HTC. What I did was flash the RUU, temproot and revert to stock CID (don't know why I didn't do this first) then flash the RUU again just to make absolutely sure that all was well.
Yeah I would use the tool to change Radio S-OFF to ON and restore the CID before you run the RUU. You will save yourself a lot of time and effort.
ok. on first try i already have a problem. i downloaded the easy radio tool.
connected my device with usb debugging on. run the application as administrator. clicked on Stock CID (my device is unbranded desire hd) started up, notified as pushing file to sd. reurned with unknown error, probably connection.
i tried the same with Radio S-On. same response.
i am doing this before flashing the new RUU i downloaded which is version RUU_Ace_HTC_WWE_1.32.405.3_Radio_12.28b.60.140e_26.03.02.15_M3_release_155032_signed.zip.
what have i done wrong?
Don't panic your ok,
It just means you will have to run the RUU first then run Visionary+(r14) to get temp root then run the Radio S-OFF tool.
I have gone through all the steps with no glitches. How do i verify that my device no more has radio S-On and is fully returned to stock enough so as not to voide warranty. I have the stock ROM installed.
I also want to try updating using the recent OTA update and use the device a while to see if the problem returns before returning it to HTC.
If you temp rooted, then ran the Radio S-OFF tool to go back to S-ON and CID: HTC__001 then you are good to go. You are completely stock, do some testing to see if your reboot problem persists.
andyharney said:
If you temp rooted, then ran the Radio S-OFF tool to go back to S-ON and CID: HTC__001 then you are good to go. You are completely stock, do some testing to see if your reboot problem persists.
Click to expand...
Click to collapse
Funny enough no more problem of being unable to reboot.
I have installed titanium.
i want to update to the latest OTA 2.3 update for the desirehd. do you know if the visioinary root and the the easy radio tool for s-off work after that update which i believe is the latest one.
I will use the device in its stock condition for two mpore days and if i do not have any more issues then im going to install a custon rom once again.
Thanks loads for all the help.
If you upgrade to 2.3 (2.36.405.x) then Visionary+ no longer works, you have to use GingerBreak instead. You can still downgrade to an earlier firmware.
I tried rooting again using visionary. got the same problem after applying permroot and then using the easy radio tool for S-OFF. After applying permroot it booted fine. But after applying S-OFF and SUperCID it goes back to same error and doesnt boot again. It seems then that it has something to do with the rooting process.
I will post a new thread asking if anyone has been unable to complete the S-OFF and SUPERCID process .
Why did you apply permroot? I said temproot, you don't want to make persistent changes. See if you can undo the permroot, there is a button to do it.
andyharney said:
Why did you apply permroot? I said temproot, you don't want to make persistent changes. See if you can undo the permroot, there is a button to do it.
Click to expand...
Click to collapse
I did exactly as you said using temproot so as to be able to turn apply S-OFF and the stock CID.
but after i did that and it worked i just tried rooting once again permanently and had the same issue. I have updated to the OTA update and i will use that for a while as when reading the gingerbreak threads people do not seem to trust that it works fine.
I just re-read my last post, sorry if I came across as a d*ck, that was not the intent.
I would remain stock for a few days to see if that has an affect. If rooting is the cause of your issue, I doubt HTC will repair it because it has booting problems once rooted.