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.
Related
It seems that I can't get a clean boot off anything other than the JF 1.5 or 1.51 US builds. I've tried cyanogen and even jf 1.51/1.5 ADP builds but it always boot loops. Any suggestions?
I've read through the questions threads, I've used search. I just can't seem to find anything relevant to my problem in specific. I've flashed to hardspl, I've updated the radio, tried various builds of the same developer to see what it could possibly be, but I'm pretty stumped.
Hmmmm... try re-flashing RC29, re-root, and try the update again... sounds like its not updating correctly
Tried that multiple times over the last few days. this time, I managed to get past a straight reboot loop, but I was stuck at the boot screen with sounds/alerts/sleepbutton as if I had changed my launcher.apk with a file from the wrong rom. Going to reflash to 29 again and try it again =P
As many times as I go through this long (well, not quite) and arduous (heh, sure) process, it's still fun
*edit* out of curiosity, how extensive are nandroid backups? I've tried some flashes using a nandroid restore from an rc29 with the OTA radio and cyanogen's restore img. Would that reflash me back to prior settings?
//Note not all of my installs are with nandroid restores. I have tried with pure fresh dreaimg.nbh/root/hardspl/radio installs.
hmmm, have you tried flashing the new recovery? Try Cyan's 1.3.1 Recovery Image, might work a little better.
just reboot looped again. order of operations for a freshie should be something like this;
1)dreaimg.nbh
2)root
3)cyan's recovery
4)ota radio
5)JF 1.51 ADP
correct?
*edit* in all honesty, I want to try cyan's newest build but if I can't even get past installing JF's ADP build... ya...
wahookasan said:
just reboot looped again. order of operations for a freshie should be something like this;
1)dreaimg.nbh
2)root
3)cyan's recovery
4)ota radio
5)JF 1.51 ADP
correct?
Click to expand...
Click to collapse
No... you're missing HardSPL between root and cyan's recovery.
lol, just did some more searching, and realized that I was misunderstanding what hardspl actually did for me. It was my understanding that Cyan's recovery img replaced hardspl (don't ask me how I got it mixed up, I just did, ok? xD). I just got into rooting my G1 recently, if you haven't noticed.
Thank you for your timely reply's and hopefully this helps me dive into what I was missing out on
Sorry for the double post but the issue isn't resolved.
the problem is persistant. even with hardspl in (could have sworn I had that in at some point anyway) I still can't use the ADP or cyan's latest
Did you perform a wipe before flashing ROMs? Not wiping may cause some boot loops with certain mods.
I've done a full wipe back to dreaimg.nbh (assuming that's what you mean). I've gone back to step 1 of the root process. Still no go
wahookasan said:
I've done a full wipe back to dreaimg.nbh (assuming that's what you mean). I've gone back to step 1 of the root process. Still no go
Click to expand...
Click to collapse
You should go ahead and wipe before all of the builds when your starting up. I believe DREAIMG.nbh is a US based rom, and the JF you are installing is ADP. You MUST wipe when switching from US based ROM to an ADP based ROM
im having the exact same problem i was able to get a rom other than the JF installed, i have tryed every damn way possible and mine will not work either. i use the Haykuro 1.5 Cupcake one, and it seems to work. My phone gets stuck whenever i try to load any hero, or Cynanogen roms. Its depressing, yeah fun at first but now i look at posts and cry hahahahha when these people have theres all bad ass! SOMEONE HELP USSS! email me at [email protected] if needed pleeeease i need HERO!
root, wipe, flash JF, wipe, update radio, wipe, update recovery image, wipe, flash whatever ROM you want.
Did you try that?
I apparently screwed some things up in my attempt to upgrade to Cyanogenmod 4.1.99 so I can move to 4.2.3. . . anyway, I now have the HTC bootloader up with fastboot, the standard Android recovery, and HTC ADP 1.6 DRC83 firmware installed, and its up and running. I don't have root, and I am completely lost as to how to get root back, get cm-recovery 1.4 back, and from there, I should be ok...
I do have DREAMING.nbh on my sd, and when i go into fastboot(pwr+camera) It gives me a list:
Parsing. . .[DREAMING.nbh]
[1] BOOTLOADER
[2] RECOVERY
[3] BOOT
[4] SPLASH1
[5] SYSTEM
[6] USERDATA
[7] RADIO_V2
Do you want to start update?
<ACTION> Yes
<Power> No
This is where I don't know if I should do anything without advice, as I don't want to brick my G1 any further
Anyone care to help out?
if you messed up like i did a few months back , and lost root because you flashed the htc recovery image and didn't flash cyan's rom on top of it then...i can help. i'm assuming you lost root on your rom because of that, and when you rebooted it took out cyan's recovery image as well, so you can no longer flash anything else into your phone. Alright! first thing's first, is we need to have a look at what spl you're using, take out that dreaming.nbh file from your sd, you won't need it, instead, put on a recovery image like cyanogen's 1.4 or amon ra's 1.2.3 (i suggest the latter)
anyways , you're gonna have to have the hard spl/ engineering spl/ or the haykuro "death/danger" spl installed on your phone. I'm going to assume you have at least one of these, because if you don't and you have the stock spl that's a different story. If you have the stock spl for some reason, you are gonna have to downgrade your phone like you did when you first got root. Research the forums , there are loads of guides on how to downgrade your phone, go to the section that specifically talks about using the bootloader to restore the dreaming.nbh file.
if you do have either the hardspl, death, or engineering's spl,
you need to search the forums on how to use fastboot and adb
you're gonna need to push the recovery image file (cyan's or amon_ra's)
into your phone and wahpow!
you're in the green, once you have the recovery image back in the phone, you can boot into it and flash w.e the hell you want
phamous said:
if you messed up like i did a few months back , and lost root because you flashed the htc recovery image and didn't flash cyan's rom on top of it then...i can help. i'm assuming you lost root on your rom because of that, and when you rebooted it took out cyan's recovery image as well, so you can no longer flash anything else into your phone. Alright! first thing's first, is we need to have a look at what spl you're using, take out that dreaming.nbh file from your sd, you won't need it, instead, put on a recovery image like cyanogen's 1.4 or amon ra's 1.2.3 (i suggest the latter)
Click to expand...
Click to collapse
You hit the nail on the head!
phamous said:
anyways , you're gonna have to have the hard spl/ engineering spl/ or the haykuro "death/danger" spl installed on your phone. I'm going to assume you have at least one of these, because if you don't and you have the stock spl that's a different story. If you have the stock spl for some reason, you are gonna have to downgrade your phone like you did when you first got root. Research the forums , there are loads of guides on how to downgrade your phone, go to the section that specifically talks about using the bootloader to restore the dreaming.nbh file.
if you do have either the hardspl, death, or engineering's spl,
you need to search the forums on how to use fastboot and adb
you're gonna need to push the recovery image file (cyan's or amon_ra's)
into your phone and wahpow!
you're in the green, once you have the recovery image back in the phone, you can boot into it and flash w.e the hell you want
Click to expand...
Click to collapse
I know that I had HardSPL on at one time, would everything that has happened somehow remove it, and how can I check if its still there?
I will likely use Cyanogen's recovery. If possible, link me to a good "howto" on loading Cyanogen from Fastboot.
alright, to check what spl you have, turn off your phone and hold camera and the power on button,
you'll go into your bootloader, and it will display what spl you're running
it's been a while since i remember what numbers belong to what spl, but as long as you don't see the multicolored spl, and you see like three little android bugs on the bottom, you're good to go
uhm i kinda saved random links to things that i used, you're gonna have to read all these documents and learn all about adb, it's worth it in the long run, and there's no better time to learn it now since it's your only hope of getting root back.
http://androidcommunity.com/forums/f10/adb-fastboot-for-rookies-18124/
http://forum.xda-developers.com/showthread.php?t=502010
BUT ANYWAYS
OMG i just found the best guide to your problem right here
http://wiki.cyanogenmod.com/index.php/RE-recovery-img
^^ that is GOLD!
hope this helps buddy!
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.19.261
Apr 20 2009, 15:30:43
Thats all it gives me, but there are 3 Androids on skateboards at the bottom, and its a all white screen.
I cant seem to get the SDK to work, let alone install on my PC here(Damnit Vista, I can't wait for my copy of Win7 Pro to get here!!!!) so I might just let it charge up overnight, check here in the morning and give it a whirl on my laptop with XP. Hopefully, I can get this all taken care of. You have been a world of help so far. Just keep an eye out for some updates here tomorrow.
SAME HERE wow, couldn't get the damn sdk to work on vista either
GO XP
that's what i did, worked instantly, find someone with xp and ask them to let you borrow it for about an hour
----
you have an appropriate spl btw, it'll be able to fastboot correctly
in the meantime, i'd read up on those links i sent you, especially the last one,
and you'll be good!
goodluck!
ok, looks like I got the SDK to work on here, and I have it updating right now. Its first update was the USB driver. If anyone has some time, and wants to send me a IM over AIM to help me out with this, please IM me.
I am going to let this update, and then hope that I can get it to flash cm-recovery back onto the phone.
cm-recovery 1.4 is BACK! OK! AWESOME
god this had me abit scared.
Ok, back to the prior task at hand. at this point, can I update to CyanogenMod 4.1.99 then update to 4.2.3, or can I update this directly to 4.2.3?
ok, you cant update directly to 4.2.3 XD
Ok, awesome, ive got cm-recovery 1.4, and Cyanogenmod 4.2.3.1 up and running. Time to give Cyanogen some credit. this firmware is FAST!
Also, I want to thank everyone that has helped out with my issue. you are all worthy of a beer...I just aint got any money to pay for a beer for you all right now XD
I just rooted my g1 and i'm having problems trying to install cms rom.
some info;
DREA100 PVT 32B
HSPL10.95.3000
CPLD-4
RADIO-2.22.19.26I
Oct 20 2008
I installed cm's recover 1.4 img and have access to the recovery screen no problem.
Tired installing AP1.6 but can't confirm it got installed.
I did this..
wipe
flashed signed-dream_devphone_userdebug-ota-14721
wipe
flashed cm 4.2.7.1
goes to the T-mobile screen, then it loads up cm's boot screen then after where it should take me to the setup screen, it turns gray/black and stays there.
please give me some imput on what i'm doing wrong.
Thanks!
You wipe, then you flash the ota update. Reboot and it will go back into recovery by itself. from there you install cm, without wiping. Reboot and you are good.
Ok i've done just that.
wiped
flashed ota, it goes back to recovery image
i flash cm 4.2.7.1
reboot and it does the same thing.
t-mo logo loads up. then cm's android bootscreen loads up.
then it goes gray/black and stays there.
i know im doing something wrong but not sure what... should i install a older cm rom first? since i'm coming from a fresh rooted g1? i was coming from rc29
RegulatorG1 said:
Ok i've done just that.
wiped
flashed ota, it goes back to recovery image
i flash cm 4.2.7.1
reboot and it does the same thing.
t-mo logo loads up. then cm's android bootscreen loads up.
then it goes gray/black and stays there.
i know im doing something wrong but not sure what... should i install a older cm rom first? since i'm coming from a fresh rooted g1? i was coming from rc29
Click to expand...
Click to collapse
it shouldn't make a difference. how much time did you wait? It could take up to 15 minutes for the first initial boot.
i've waited about 10mins. but even if it goes to the gray/black screen i should wait for it longer?
gonna redo this again and wait for a longer time. 20mins max and see where it goes from there.
Upgrade to amon_ra recovery 1.5
Then do this
Wipe
install ADP 1.6
flash cm rom right after flashing ADP without reboot
now reboot and it will go back to recovery mode
now reboot once again and wait my friend
I'm still waiting for about 20mins to see if it reboots good.
If not then i'll be doing the new amon_ra recovery 1.5 way.
should i install a older cm rom if coming from bare root?
or it doesn't matter if i'm flashing 1.6?
you might want to consider upgrading your spl while you're at it. Just a thought. I don't think it's necessary for running Cyanogen, but it'd be nice to have in case you ever want to run a hero rom to upgrade to the danger spl
where can i get the spl? I dont wanna install the danger one since I wont be installing hero on it. I just wanna run cm roms.
no luck still. but have another dumb question for you folks.
the spl i have is this. .. HSPL10.95.3000
is this ok to run cm or should i upgrade it? i know that there is a spl that is used to run hero roms but i'm not gonna be doing that so I thought that maybe there might be another spl out there that is a upgrade from the one i have?
gonna go search the forums for this btw. I dont wanna be a pain about this.
RegulatorG1 said:
no luck still. but have another dumb question for you folks.
the spl i have is this. .. HSPL10.95.3000
is this ok to run cm or should i upgrade it? i know that there is a spl that is used to run hero roms but i'm not gonna be doing that so I thought that maybe there might be another spl out there that is a upgrade from the one i have?
gonna go search the forums for this btw. I dont wanna be a pain about this.
Click to expand...
Click to collapse
I was wondering if it was your spl that could be preventing the rom to boot up. If you don't want to flash the danger spl, you can flash another one, like the HardSPL. I'm sure if you look in one of the sticky's or locked threads at the top of the forums in development you will probably be able to find a download link. It's worth a shot. Since you already have the latest radio, there is no reason to worry about upgrading the radio.
i was checking the forums and i have the hard spl.
or at least this says is the hard one. goes something like this..
hardspl =VER: HSPL10.95.3000
then
Engineering SPL=VER: HBOOT-0.95.3000
and last
G1 Original SPL=VER: HBOOT-0.95.0000
still no luck with installing cm's rom.. gonna look some more.
thanks for all the help guys! please if you think of something else let me know.
ok can't figure this crap out. gonna go bald lol
did a restore on my recovery and i'm back to this.
Model number: Android Dev Phone 1
Firmware version: 1.6
Baseband version: 62.50s.20.1H_2.22.19.26I
Kerner version: 2.6.29-00479-g3c7df37
[email protected] #19
Build number: dream_devphone-userdebug 1.6 DRC83 14721 test-keys
It does show the 1.6ADP
but what the hell lmao. I can't install cm though.
Not gonna touch the g1 right now till hopefully some of you can tell me how or what to do to upgrade my rom to hopefully cm4.2.7.1.
Again i'm really sorry for being soo needy.
oh crap. I think i lost root access again >_< crap
what's the best way to check to see if i still have root?
turned off phone and tried going into recovery but now it just shows the triangle ! and the phone pic. guess root is gone???
The newer Spl rearranges how mem is allocated so more is given to system partition on phone which allows larger roms to be installed(heros).Any SpL is fine for cyanogen/enom/dwang roms.
RegulatorG1 said:
oh crap. I think i lost root access again >_< crap
what's the best way to check to see if i still have root?
turned off phone and tried going into recovery but now it just shows the triangle ! and the phone pic. guess root is gone???
Click to expand...
Click to collapse
The triangle means root is no longer with you,young one.
ok, gonna root it again. i can get it to rc29 no problem but that's where the entire thing went wrong. will post later. wish me luck
ok rooted my g1 once again. gonna install the 1.4 recovery image now.
ok installed 1.4 recovery, now performing a backup for this point.
I think I have a old cm rom around somewhere.. .. its a 3.9.5cm should i update radio first then install this or visa versa?
+ok, installed 1.4 and flashed new radio. now gonna do what your saying and see where it goes. performing backups at each point >< lol
-ok i went to recovery and flashed the new radio and it's still formating cache... its been like 5mins already. should i reboot or wait longer?
i'm still needing to install the 1.6ADP and the rom still.
Don't reboot between the 2 zip files.
Boot to recovery
do a wipe
wipe it again for good measure
install from zip signed dev dream zip
install from zip Cyanogenmod 4.2.7.1
reboot
It will tell you it is writing radio then actually reboot
It will reboot to recovery mode
where it will tell you its writing cache...
wait till it offers reboot option again
Reboot
you shoul dget the G1 screen, than the cyanogen screen...
yes it might take a while on the second screen...I have never had it hang more than about 8 minutes.
Then you should be operational.
I do have a reoccuring issue with poor response after the initial boot to the desktop.
I usually just wait for it to stop all the background shuffling and then it smooths out.
YMMV
ok this is where i am so far...
have root
have hardspl
have recovery 1.4
have Radio Update 2.2.19.26I
now i'm gonna perform backup and do what you just said. hopefully since i did everything brand new there will be no issues.
I just got a replacement G1 from Tmobile, for free bless their hearts, cause my headset is going to the crapper. I'm trying to update my raido to the 2_22_19_26I, as I did before with my first G1, so I can install the DangerSPL. I have tried with the stock recovery, Cyan's 1.4, and Amon-RA's 1.5.2 to install it, and each time, it goes about the update process as normal, asks me to reboot, I see the picture of the chip and then it takes me back to recovery.
Each time, though, I'm still at the 1_22_12_29. I check by turning on the phone, then Settings --> About Phone, and also by going into the SPL, still at the 1.
Any ideas?
EDIT: also I'm using the radio on HTC's developer website, so it's legit.
Uh, i'm not XDA police but i'm pretty sure this goes in Q&A.
You need a custom recovery before you can even upgrade the radio but are you on 1.5 doing the one-click?
One-click:
http://theunlockr.com/2009/08/22/how-to-root-the-mytouch-3g-or-g1-in-one-click/
"I have tried with the stock recovery, Cyan's 1.4, and Amon-RA's 1.5.2"
I've tried with many different recovery's.
jordancrockett said:
"I have tried with the stock recovery, Cyan's 1.4, and Amon-RA's 1.5.2"
I've tried with many different recovery's.
Click to expand...
Click to collapse
When your in rec mode you must flash the radio while there, i heard the rec gets deleted if you dont update the radio when you install a recovery.
rec mode? please restate what you just said.
jordancrockett said:
rec mode? please restate what you just said.
Click to expand...
Click to collapse
rec=recovery mode
The guide says flash the radio while your in recovery mode not after.
i've done the recommended one-click method, even went back and let my phone update itself back up to stock, but i still have radio 1.
jordancrockett said:
i've done the recommended one-click method, even went back and let my phone update itself back up to stock, but i still have radio 1.
Click to expand...
Click to collapse
Can you load roms since you said you tried recoveries?
I can load everything, ROM's, SPL's, different recoveries, boot.img's.
I've tried updating the radio before I upgrade the SPL, after, with a stock recovery, or with Amon-RA's/Cyanogens. I don't know why it's not working.
jordancrockett said:
I can load everything, ROM's, SPL's, different recoveries, boot.img's.
I've tried updating the radio before I upgrade the SPL, after, with a stock recovery, or with Amon-RA's/Cyanogens. I don't know why it's not working.
Click to expand...
Click to collapse
Donut roms(1.6) dont need the Haykuro or Hard SPL you can load roms with the one you have now.If you want to use hero or eclair then you'll need the radio and SPL.
Also if the radio is anything like the spl, don't use the trackball while flashing it
Another user and I, have this same issue with no solution, we have threads in dream q&a and dream general. I also used recovery flasher to gain root when I was on cupcake. My radio is older than yours though =/ if you can't find the threads ill post the links tmw, as I'm abt to sleep now..good luck hopefully we can all find a solution, or at least identify the source of the problem..
not sure if this will be of much help, but you can always try to revert back to the stock firmware using the dreaimg.nbh file and stock spl.
i had a friend who, like with your radio, couldn't flash the more recent custom recoveries.
whatever the reason was, i suggested that he just "unroot" and go back to android 1.0, stock spl, stock radio , whatever, and just re-root from there
phamous said:
not sure if this will be of much help, but you can always try to revert back to the stock firmware using the dreaimg.nbh file and stock spl.
i had a friend who, like with your radio, couldn't flash the more recent custom recoveries.
whatever the reason was, i suggested that he just "unroot" and go back to android 1.0, stock spl, stock radio , whatever, and just re-root from there
Click to expand...
Click to collapse
ust make sure when unroot you follow the instructions...somehow i bricked my first G1 when I was unrooting. Dont ask me how I did that but I did ha
thenameismax said:
just make sure when unroot you follow the instructions...somehow i bricked my first G1 when I was unrooting. Dont ask me how I did that but I did ha
Click to expand...
Click to collapse
haha, good point! when in doubt, just follow the guide!
this one, if you don't already have it,
http://forum.xda-developers.com/showthread.php?t=442480
shows you how to "downgrade/un-root" your device.
happy flashing!
I apologize to sound rude, but I've been with XDA and the G1 rooting community since 1.0. I know these are good, helping tips and guides, but I've tried to explain that I've done everything like that already, gone back to stock, gone up to cyan's 4.2.13, gone back to stock, then up to a stock 1.6, even with the stock updates, when it says writing radio, radio doesn't update.
your replies are appreciated, just not really relevant or helpful.
I was setting up a friends g1 and same thing, he got the phone from warranty exchange and I was able to downgrade, gain root, change recovery image and flash enom's rom with no issue. But upon boot up I saw his radio image was .29 and tried to update the radio. I kept getting something like "line 2: getting prop(device = dream)"
So I started all over rc29, root, recovery image and every time I try to update radio, same issue. Even when use Cyan's method and try the developer's image with radio update, it fails.
In the end, since enom's rom can use any radio, he was ok with it. But really i wanted to get his g1 on the latest radio image. I feel your pain as I researched the errors as well and couldn't find anything. Good luck.
Fabe
mdafabe said:
I was setting up a friends g1 and same thing, he got the phone from warranty exchange and I was able to downgrade, gain root, change recovery image and flash enom's rom with no issue. But upon boot up I saw his radio image was .29 and tried to update the radio. I kept getting something like "line 2: getting prop(device = dream)"
So I started all over rc29, root, recovery image and every time I try to update radio, same issue. Even when use Cyan's method and try the developer's image with radio update, it fails.
In the end, since enom's rom can use any radio, he was ok with it. But really i wanted to get his g1 on the latest radio image. I feel your pain as I researched the errors as well and couldn't find anything. Good luck.
Fabe
Click to expand...
Click to collapse
Yeah, that's exactly what I'm going through, except it's not throwing up any errors or anything. it updates, says "writing radio image...", reboots with the HTC symbol, and goes back to Recovery and Formats the CACHE like always. *sigh* maybe T-mobile found a way to mess with us after all?
Just a question, when u rooted, did u do it the old way or new way. And by old way that I used, was the DREAIMG.nbh, then on home screen the type cd /sdcard blah blah...
I need help quick! Im stuck on rc29 and I cant update!!! Everytime i try to unzip the Update.zip folder it tells me Signature (302) failed or something like that. It feels like ive tried every single download possible. Ive tried to go rc29 to rc33. Ive also tried to go rc29 to rc30 but none of them seem to work or is it me? HELP!!!
thanks!
surely you have been here long enough to realise that you get no love when you ask in the wrong section
Did you rooted the device and installed custom recovery image???
It seems like you tried the roms without flashing the custom recovery image as the custom roms cannot be flashed with original recovery..
The best custom recovery is Amon Ra 1.6.2 for the dream and magic..
However you should be able to flash the official OTA updates like cupcake or donut.. straigt from RC29 without rooting the device too..
Thanks!
Moved as not Android Development.
sorry about posting in the wrong section...my bad!
and how would i force and OTA update?
i dont have a option for system updates..
oh and also, i always get the corrupt file with i try to flash a official update...any ideas?