Related
...It's pretty much been over half a year since I needed to root my phone again, but I just received a brand new one from tmob.
SO. I did the root deal, that went super smooth, I have JF1.51 CRB43 ADP to start with.
NOW, I am trying to update the radio, and it does not seem to be working. From what I remember and what I've read, all you do is flash it like you would any rom, rename to update.zip and recov alt+s, right? Well, when I check the radio version it still says the original, not what I flashed. So I re-downloaded and tried again, no luck.
....feel like a real idiot here haha, never had it not work before. Tried searching but I had no luck finding the solution. By all means if you have a link and this was a pointless post just tell me, else I just need some help!
which recovery image do you have installed
maruutah said:
...It's pretty much been over half a year since I needed to root my phone again, but I just received a brand new one from tmob.
SO. I did the root deal, that went super smooth, I have JF1.51 CRB43 ADP to start with.
NOW, I am trying to update the radio, and it does not seem to be working. From what I remember and what I've read, all you do is flash it like you would any rom, rename to update.zip and recov alt+s, right? Well, when I check the radio version it still says the original, not what I flashed. So I re-downloaded and tried again, no luck.
....feel like a real idiot here haha, never had it not work before. Tried searching but I had no luck finding the solution. By all means if you have a link and this was a pointless post just tell me, else I just need some help!
Click to expand...
Click to collapse
If your using Cyanogen's recovery, try to physically press the alt-s, and home + back to reboot
I believe it works like that for flashing the IPL (radio) and SPL
where did you get the radio from?
Sorry I left out the recov info, I know my signature is misleading...didn't change it yet..!
I'm using JF 1.43 recov, I remember that (not sure if it was ever fixed, all I know is that flashing the SPL with CM recov caused 'error at line ___' when flashing new roms) that you cannot flash the new SPL with cyanogen recovery, so I'm using JF's until I get the radio and spl flashed correctly.
I got the radio from where I usually have in the past, as well as the new SPL
http://sapphire-port-dream.googlecode.com/files/
(Of course I will not flash the latest SPL until the newest radio is flashed first!)
I just want my happy CM 3.9.7 back..! With the ability to flash the new hero roms when I get curious..
****I am now attempting to flash the radio with cm recov 1.4, will update on this if it works.
****no luck with cm either, didn't think it would make a difference but thought I would give it a shot. I still have 1.22.12.29 for my radio :/ agh!
So...Still can't update the radio for whatever reason, just does not take, and I still can't find anything in the forums about this either... :/ Anyone have any ideas at all?
get the radio from the htc website maybe you got a bad download. i have flashed radio and new spl with cyanogens recovery so i know it will do it. after flashing the radio press home and back to reboot. do not reboot from the recovery console because i have noticed that it will not write the image.
david1171 said:
get the radio from the htc website maybe you got a bad download. i have flashed radio and new spl with cyanogens recovery so i know it will do it. after flashing the radio press home and back to reboot. do not reboot from the recovery console because i have noticed that it will not write the image.
Click to expand...
Click to collapse
Thanks for the link ^-^ I will give it a shot. Good to her that the CM recov flashes the new SPL alright now..! I will post results...every time I flash it goes through the motions of writing the radio but just never shows that I have the new one..super frustrating.
** I also notice that whenever I have tried to flash the radio on the new phone, when I reboot it goes through the appropriate motions, yes, however it puts me back into recovery every time. I wonder if I should just completely start over (unroot, re-root) hope thats not the case..I just got it all set back up again :/
Nope, no matter where I download from and how many times I flash with different recoveries.. I still have the original radio 1.22.12.29 :/
This has always been so easy! I've never had issues with rooting, then updating the radio, then updating to the new SPL.. :/
maruutah said:
Thanks for the link ^-^ I will give it a shot. Good to her that the CM recov flashes the new SPL alright now..! I will post results...every time I flash it goes through the motions of writing the radio but just never shows that I have the new one..super frustrating.
** I also notice that whenever I have tried to flash the radio on the new phone, when I reboot it goes through the appropriate motions, yes, however it puts me back into recovery every time. I wonder if I should just completely start over (unroot, re-root) hope thats not the case..I just got it all set back up again :/
Click to expand...
Click to collapse
If you can, try rerooting, it will only be a few more steps.
B-man007 said:
If you ca try rerooting, it will only be a few more steps.
Click to expand...
Click to collapse
Yeah, I was hoping to not have to but I will in a bit here if I still can't figure it out. I have root just fine, running CM 3.9.9.1 even, which I usually only run his roms, however I do like to try the Hero roms as well as they come out..
bummer :/
maruutah said:
Yeah, I was hoping to not have to but I will in a bit here if I still can't figure it out. I have root just fine, running CM 3.9.9.1 even, which I usually only run his roms, however I do like to try the Hero roms as well as they come out..
bummer :/
Click to expand...
Click to collapse
I don't know why its not updating your radio, but everything else works fine. You should update the radio before updating to cupcake builds. maybe that will help?
gave up for a while, finally re-rooted
Re-rooted and still cannot update my radio, I have tried updating it after the very first rooting steps, after updating to JF RC33 as well, I still can't get the latest radio to get onto my phone. I have tried with JF recovery, CM recovery, as well as the original recovery image, and nothing. Notta. Zip. No idea why my phone simply will not take the new radio image.. I have re-downloaded it a million times as well, going in circles..don't get why the phone will let me root, unroot, all that jazz, and simply will not let me update the radio... driving me nuts!! I can use CM roms just fine of course but any other roms I am stuck with not trying cause of this annoyance!! Anything anyone can recommend would be great
o man still can't get it to work?
try flashing the official 1.5 OTA update, which contains the updated radio. see if it gives you an error message. if it does, take it to tmobile and tell them to replace your phone.
if it flashes...see if it updated your radio. if it did, you can use the one click root to root your phone
Thanks again buddy, I will try it out ^^
So, I unrooted, and applied the OTA updates from 29 to 30, 30 to 33, 33 to cupcake..and I still don't have the latest radio, still at 1.22.12.29. I got the ota cupcake here:
https://android.clients.google.com/updates/partner/signed-kila-ota-150275.53dde318.zip
i'm going to try flashing the ota radio update without root if it will let me..grr..this is so weird, there is no reason why it shouldn't take a simple radio update..hrm
***attempted the ota radio update, guess you can't without root which is what I figured, but frick, this makes no sense.. >>
so, this is a bit odd, at http://developer.htc.com/adp.html, one of the spots to DL the latest radio, when you hover over the radio link for 1.5 and 1.6, it says "ota-radio-1_22_14_11.zip" rather than "ota-radio-2_22_19_26I.zip", weird, eh? Wonder if it's simply not the right radio, and labeled wrong, I have no idea, but this is getting super old.
I'm actually having the same problem, can't seem to update the radio with the radio image the htc site provides. It's still stuck at 1.22.12.29
Anyone had this before? Any help would be appreciated
I can't get around it, and it's really frustrating, since the only rom I can use is a CM build..aside from a couple others, but CM is the best as far as universal SPL use goes..
So what I've tried so far:
- Updated to HardSPL
- Tried multiple Radio updates, new ones, old ones, even some from the forums.
- Tried a few complete updates that include the radio image
- Tried flashing directly from fastboot, not sure what partition I need to flash though, the radio partition gives me an error that it does not exist.
Still no go. The weird thing is that I come from a stock 1.5 installation updated from 1.0 via t-mobile. And I'm still at the original 1.0 radio image.
Please help!!! I started messing with my phone about a week ago and I install the Android 1.6 dev. It will not flash anything, not even an spl. What am I missing. I almost feel bad asking because all of you seem to have such knowledge of this stuff. Thank you very much
I don't wanna bring your hopes down thinking this was help lol but u prolly tried flashing cyanogens new rom and its funny cause i was JUST about to post this same shiet. but anyways. i was thinking about flashing the dream file but i dunno if that owuld brick my phone or not. and just to clarify its the htc 1.6 dev right? i mean if thats the only 1? lol
yup
That is exactly what happened! I don't understand how this isn't a major issue and posted everywhere. If you figure it out make sure you let me know and I will do the same. Take it slow!
Can you explain what the problem problem is? What have you been trying to flash? Do you get errors? What recovery image are you using?
Btw, if you're flashing an SPL or radio with Cyans recovery, you can't use the trackball. It must be an update.zip which you install by pressing alt-s and reboot using home+power. If you don't it wont be installed.
Well, I don'tk now about the original poster, but I've tried flashing the OTA cupcake rom to downgrade. renamed to update, went into recovery but it says its not authorized. and.. im afraid to put the dream.nbh or w/e cause it might brick the phone.
PS: This is 1.6 without root. this is the dev ver. so we have the exclamation point recovery not cyan.
lapalways05 said:
Well, I don'tk now about the original poster, but I've tried flashing the OTA cupcake rom to downgrade. renamed to update, went into recovery but it says its not authorized. and.. im afraid to put the dream.nbh or w/e cause it might brick the phone.
PS: This is 1.6 without root. this is the dev ver. so we have the exclamation point recovery not cyan.
Click to expand...
Click to collapse
okay first you need a app called flashrec it will dl cyan recovery image then you reboot.But you need root first also teh dreaimg.nbh file which is RC29.
1.5 cupcake rc30 or something and up was patched with the one click root, that's why we were trying to downgrade to 1.5..
nothing works
I can't use the flash rec because it won't back up the recovery image! Everything I try to flash just goes to installation aborted! I don't know what to do!
It's b ecause 1.5 rc30+up (including 1.6) patched up the 1 click, but an answer would be nice
flash the dream image and start from scratch. that takes everything back to stock, then you can re-root. This thread can walk you through it
http://forum.xda-developers.com/showthread.php?t=491350
it doesnt work
I already tryed that but it won't let me flash the spl!
i tried that too
I tried flashin the dreaimg too. I have ran jf1.5 before and flashed themes and everything. That's why I don't understand why I can't flash anything. The 1.6 work but the recovery image isn't letting me flash anything at all! Once I installed the 1.6 dev it flashed me from the 1.4 cyanogen image to the exclamation image with a differnt bootloader. Ever since then I can't flash anything.
i think he means using camera + power unroot it.but im guessing we don't flash the SPL since we can't, we just flash the dream.nbh?
After Factory Reset
Guys,
I did factory reset but now I can not work with HTC dream as it is requesting me to cerate a gmail account, and I can not cerate because I do nto have internet in my mobile operator.
Does anyone knwo how to bypass this mesage?
please help meee.
r,
bhowd u do the factory reset?
I did it!!!
I had to download sdk, get it working, fastboot the the cyanogen 1.4 recovery image. After the it let me install all of my updates. YAAAAYYYY!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
could you tell me the steps of what you did?
I'm stuck with ADP1 1.6 ><
Thanks a lot!!
This will work!!!
Trust me this will work because it took me hours to figure out. Install sdk, get it to work. They explain how to use the program on the forum. After you finally get into fastboot flash the cm 1.4 recovery image. After you do that you can bootup into that recovery and it will then read all of your zip files unlike that stupid exclamation recovery.
slightly confused
So you mean you used http://forum.xda-developers.com/showthread.php?t=502010 to figure out how to use the sdk right?
If not, can show me the link to that guide?
Many thanks!!!
yes
Yes, I used the sticky notes at the top of Dream Q&A to figure it out and it wasn't too fun.
I have been trying to flash my Nexus one with a the new cyanogenmod 6.0 RC 2 ROM but for some reason doesn't work, and I have updated my Nexus one with the newest radio img, wipe the phone before loading the ROM and everything else but it still will not boot up. The boot animation always freezes up and get stuck in a loop. I have never had trouble flashing ROMs on my Nexus one until this one so i don't know what the problem could be so I was hoping some one here could, help me figure out what the problem could be.
Check the MD5 sum of your download file.
I'm sorry I'm still new to a lot of this stuff, what does MD5 mean.
Devyne_one said:
I'm sorry I'm still new to a lot of this stuff, what does MD5 mean.
Click to expand...
Click to collapse
Google it, you'd need the files necessary to check anyways.
I've heard somewhere that Cyanogen's ROMs don't like new HBOOT 0.35.0017. And i think you got it (new HBOOT) after you updated radio. Here is the instruction how to revert HBOOT to previous version http://forum.xda-developers.com/showthread.php?t=726258
Hi all,
I have been around a long time though i have never had trouble like this before..
i got a Incredible S PG32130 - HBOOT 2.0000.00 - Australian Delivered OPTUS002
I tried to follow the downgrade path so i could get S-OFF found here:
http://forum.xda-developers.com/showthread.php?t=1373697
Everything went fine so i proceeded with the older RUU flash to get back to 1.13 so can then run revoutionary..
Though the older RUU flash failed leaving the device hanging quietly brilliant.
Tried a few methods to get it back online to no avail.
So i htcdev unlocked the bootloader.. worked fine. still couldnt flash anything though. so put on CWM Recovery 5.0.2.0 which also worked fine..
I could then install custom ROMS.. So i tried IceColdSandwich though that wouldnt boot.. flashed the X4 kernel without issue.. so i assume it's cause the radio is still old and from what i gather i cant flash a new radio without S-OFF (i have tried through CWM and via Fastboot and via PG32IMG autoload in the bootloader and all fail.
So i tried an AOSP GB ROM still no luck.. Though neither of these would actually flash. get an communication error.. (could that be because ADB is not working? - am i missing a driver?)
And even tried a of legit WWE and CM7 both fail to install as well.
RUU_VIVO_ICS_35_S_HTC_WWE_4.10.405.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266013_signed
From my limited knowledge Radio is independent of AOSP/Sense/GB/ICS though Kernel is dependant. Though the only thing i havent been able to flash is the radio.. will the wrong radio stop you booting?
What are my options here to get S-OFF? I cant adb the device no matter what i do though i do have working recovery and fastboot.
Little help would be greatly appreciated.
damn..
http://forum.xda-developers.com/showthread.php?t=1337105
this fixed me.. the manual flashing of the boot.img was the problem..
ffs.. i have spent hours and read so many guides and that one was the only one that mentioned that you had to manually flash boot.img.
thanks all.
Sage said:
damn..
http://forum.xda-developers.com/showthread.php?t=1337105
this fixed me.. the manual flashing of the boot.img was the problem..
ffs.. i have spent hours and read so many guides and that one was the only one that mentioned that you had to manually flash boot.img.
thanks all.
Click to expand...
Click to collapse
Do you still require s-off? What error message did the ruu return when it failed?
the RUU error is simply USB Connection ERROR though this happens after it has erased and sent the package to the phone.
I think it maybe due to not being able to use ADB.. so prob a driver issue. either way i dont really need S-OFF and after the hours i have spent on this i am reluctant to play more
It aint even my phone! Mine is Sensation which is already S-OFF'd
Thanks for the offer though.
MOD: please feel free to move this to Q&A, my bad.
I've tried PACman, I've tried CM10, I've tried tried the Stock ish. CM10 and PACman get to the initial setup screen where I choose a language and when I hit start, or activate USB mass storage, it freezes for a moment then reboots. On the Stock ish one it gets to the Beats logo or AT&T and freezes, then reboots. I've tried the RUU executable and it errors out (but all it says is there's an error, try the correct one executable). Does anyone know what's likely the cause of my problems, and how to fix it so I can just get my phone working? I've been working on it for 18 hours straight, I haven't even eaten anything in nearly 24 hours, and it has been stuck and incapable of rebooting for nearly 12 hours.
Additional details: I was attempting to install PACman and I had some issues, then I used the RUU for Gingerbread (because I didn't realize it was Gingerbread) and got my phone working again. The Bootloader is JB, and it's S-OFF.
this should have been posted in the q&a section. but your bootloader is jb? if you used the RUU for gingerbread it should all be gingerbread. you now have to use the ics RUU to upgrade because it will give you problems like it is now. Use the ics RUU and then flash an ics/jb rom
ZeRo2o9 said:
this should have been posted in the q&a section. but your bootloader is jb? if you used the RUU for gingerbread it should all be gingerbread. you now have to use the ics RUU to upgrade because it will give you problems like it is now. Use the ics RUU and then flash an ics/jb rom
Click to expand...
Click to collapse
Neither the ICS nor the GB RUU will work. It just says there was an error, and to please try the right RUU.
EDIT: So I'm guessing that basically I need to get the GB RUU to work, then OTA update to ICS, then continue with everything. How do I get the GB RUU to work? How do I even troubleshoot the fact that it's not working?
EDIT 2: I was wrong, it's giving ERROR [156]: IMAGE ERROR.
EDIT 3: I think I found the problem. The RUU is blank when it says what image ROM it's going to update the device to. Anyone know how to fix that?
EDIT 4: the RUU says its current version is the same as the ICS RUU.
have you tried downloading from a different source? try just using the ics RUU so you don't need to OTA update. maybe the download is just corrupted
Zero's got the right idea!
yup...that's exactly what I'd do, even if it were a stock AT$T RUU rom...better than nothing...
ZeRo2o9 said:
have you tried downloading from a different source? try just using the ics RUU so you don't need to OTA update. maybe the download is just corrupted
Click to expand...
Click to collapse
They both worked earlier today. The problem shouldn't be with the files.
EDIT: are JB HBOOT and WCX recovery both completely compatible with the stock ROM? Is there a way to replace WCX and JB HBOOT with the original versions of each just to try and get everything back to the way it was?
EDIT 2: That's weird. I downloaded a new copy of the ICS RUU and it worked. Thanks for all your help and time, everyone!
HopelesRomantc91 said:
They both worked earlier today. The problem shouldn't be with the files.
EDIT: are JB HBOOT and WCX recovery both completely compatible with the stock ROM? Is there a way to replace WCX and JB HBOOT with the original versions of each just to try and get everything back to the way it was?
EDIT 2: That's weird. I downloaded a new copy of the ICS RUU and it worked. Thanks for all your help and time, everyone!
Click to expand...
Click to collapse
I had a sneaking suspicion your original RUU was corrupt...Glad it all turned out
just a heads up if you are using Chrome to download these files.. i personally have had TONS of issues downloading large files with Chrome and would recommend using FireFox to download files bigger than 200MB maybe even smaller.. and the RUU's if i remember correctly are around 400MB.. just for future reference since you've already fixed your issue..