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?
So today i finally get the gusto mod my phone Android Dev 1. After downloading all the files and following the instructions here i can't get past the black g1 screen (#8). note i can also get the the rgb screen. thats it, but with so many different posts with similar issues, my brain is pounding. At this point if i can get beack to factory, ill live. what i'll hate is the fact that bricked my phone. i'll most likely get screamed on for not searching, but i think i may be searched out. any help would be appreciated.
thanks.
docfu.
first of all dont freak out lol. Download the dreaming.nbh or w/e file from the rooting instructions and place it at the root of the sdcard. Then get into the rgb screen (Camera + Power) and flash it. That should get you back to factory settings. If not, download the update.zip for w/e region you are in place it on your sd card. Enter recovery (Home + Power) and flash the update.
ok...so i tried the DREAMING file and it kept turning up no image found, alternatively i'm not sure what you mean by w/e region update. i ihavent come across that in my searches.
ok dreaming file did infact work. i feel better knowing that the phone isnt bricked. however after running the update when it prompts for action, i hit the trackball and i'm right back at the rgb screen..AGGGHHHH! sorry. i've been at this since 3pm this afternoon.
Chill. Don't freak. You can't just jump in and do something as soon as your read it. Read the whole thing and if you don't have the patients for this work on that before you work on this. bbreath.
I must say start by saying thanks guys. i stepped back, and actually took my [email protected]@ to bed. Rest does wonders. That said. I've accomplished the factory reset. so i back to a stock g1, and boy does it suck. As stated my phone WAS a dev 1. i've already started the upgrade process, my question at this point is where do you recommend i go from here. back to dev 1 or try one of the other roms. i've already installed the spl, and right now im stuck at the telnetd part of the root process. and this too may have me screaming by the end of the day...
any thoughts would be appreciated.
After the recovery image is installed you need to update the radio if you want to install a cupcake 1.5 ROM. You can get it here, rename 'update.zip', place on the SD card and boot in to recovery and flash. Then flash a ROM of your choice. You should be able to do that on RC 30, but I'm not sure if you need to install a rooted image first, so I'd wait for someone else's input before trying that.
I played it extra safe and used the rc29. as far as i know the proper radio is installed. i'll wait around before i do something stupid. thanks for the input tho. i'm trying to learn everything.
ok...so i went back to the original method for obtaining root. i was so frustrated last nite that i ended up trying to combine 2 slightly diff methods. at this point i call them the telnetd method and root.apk method. correct me if im wrong but niether one mentions the other. so i make it to the bootloader running the root.apk it runs thru the list and the fails at radio_v2. now im on the white screen wuth the skateboarders, the radio #says 1.22.12.29. so i run it again i
now im on the rgb screen at proceeds to attept the update again. this time the dreaimg.nbh fails. i'm not freaking out. im good. because i know im almost there. feedback appreciated. thanks in advance.
y'know i never thought about this..but if i reverted a dev phone to factory settings...did i relock everything? and for the record, i only have a mac. if that matters at all.
Future reference ^-^
In case you encounter this problem in the future, cause it can happen with flashing new roms if you skip a step:
You're only bricked if you are stuck at the G1 boot screen but can't get into recovery or fastboot, adb or anything. In cases where you can still get to other phone options to start over, rest assured your phone does still work, just need to step back and figure it out, which you did in this case with a little help ^-^ First few times doing anything to my phone, I went into panic mode a couple of times thinking I bricked until I read around and found out otherwise.
Just in case you didn't know these things, if you did, well, hope it was a nice read? ^-^
doctorfugazi said:
ok...so i went back to the original method for obtaining root. i was so frustrated last nite that i ended up trying to combine 2 slightly diff methods. at this point i call them the telnetd method and root.apk method. correct me if im wrong but niether one mentions the other. so i make it to the bootloader running the root.apk it runs thru the list and the fails at radio_v2. now im on the white screen wuth the skateboarders, the radio #says 1.22.12.29. so i run it again i
now im on the rgb screen at proceeds to attept the update again. this time the dreaimg.nbh fails. i'm not freaking out. im good. because i know im almost there. feedback appreciated. thanks in advance.
y'know i never thought about this..but if i reverted a dev phone to factory settings...did i relock everything? and for the record, i only have a mac. if that matters at all.
Click to expand...
Click to collapse
Well... if you actually purchased a dev phone it should not be sim locked.
Technically... after the rooting process, we all have dev phones with the exception of the sim lock.
So... what SPL are you using?
What ROM are you trying to install? Some roms you should consider partitioning your sdcard.
What radio do you have?
First thing is first.
Get the 1.4 recovery if you haven't done so already. 1.4 Recovery
Because this allows you to select any .zip file without having to rename it to update.zip. This saves on confusion so you don't try flashing a spl (like danger spl )before a radio (could brick your phone).
Second
You need the 1.5 radio to use cupcake. 2.22.19.26I
Third
Consider an spl. You have 4 choices. HARDSPL (Recommended), Eng SPL (what the dev phone defaults with.. skateboarding androids), the standard spl (nondev) and Danger SPL (risk bricking but worth it because you have more memory for your ROMs and can try HERO builds).
Fouth
Find your rom. NOTE: Read each post carefully! If it says you need a specific spl then get it! Otherwise it won't work. Some require the Danger SPL. If you chose a JF rom then you should be alright and don't even need to partition your card and it will work just like the OTA release. Some (such as Cyanogens 3.9.7) are experiemental and are not recommended for noobs.
Fifth (and probably the most important)
ALWAYS BACKUP WITH NANDROID!!!
In the event that you think that you've bricked your phone. I would say that there is a 90% chance that you didn't. As long as you have a nandroid backup and can get to the bootloader then you still have a phone. Just make sure the fastboot.exe file is in your sytem32 directory of your computer. Open CMD and cd to your fastboot backups saved on your computer. Simply
fastboot flash boot boot.img <enter>,
fastboot flash system system.img <enter>,
fastboot flash userdata data.img <enter>
fastboot reboot <enter>
and you should be back to where you were immediately after the point you backed up. Think of it as a system restore for Windows. It couldn't hurt to have a few backups stored.
If you have any questions or problems include information for us to read in a single post and edit as necessary.
Example:
AT&T
Cyanogen 3.9.7 Rom
Recovery 1.4
HARD SPL
Radio 2.22.19.26l
8GB class 4 sd card (7gb fat32/900mb ext3/100mb swap)
Theme version if any.
That way we know what we are working with.
Happy flashing.
rest assured i was in panic mode yesterday. but honestly the only thing i could really do was just step back for a while, meaning get some rest tackle it with a clean head. its frustrating for sure. this one guy tho who posted in the brick think tank thread...just cuz he couldnt figure things out in an hour he got pissed and started screaming waste of time this that and the other. total BI$CH! I was like whoa. I was at that point too. but Im not tryna be that guy.
Now, if could just figure out if i have to start from scratch, i just might be able to get my phone working again in time fro me to go to work tmrw morning.
So... what SPL are you using?
the hard SPL found here
What ROM are you trying to install?
Well i was trying to follow suggestion on something simple, like one of the early jesusfreke's. if i can step it up sure why not. but i'll pass on the partitioned sdcard setup for now.
actually I'll run with JesusFreke JFv1.51 US CRB43
What radio do you have?
radio number listed in my previous post.
Hey thanks by the way for taking the time out of your day to respond to this. i know u guys get your fair share of spazmiesters, so i appreciate it totally.
after doing research it seems that all the current roms require partitioning. or is that optional just for running apps to sd?
partitioning is optional of apps2sd for preformance. some like myself have three partitions, the third being for a linux swap
Ok ive final decided on the dudes cupcake 101. the ? i have now is do i start from scratch. im kind of in limbo as i'm stuck on the bootloader. if remember correctly i got half way thru the root process and it went down hill from there.
TMobile
RC29 / previously Dev 1
Recovery 1.4
HARD SPL
Radio currently 1.22.12.29 / trying to get to 2.22.19.26l
4gb card
(hope i did that right)
doctorfugazi said:
Ok ive final decided on the dudes cupcake 101. the ? i have now is do i start from scratch. im kind of in limbo as i'm stuck on the bootloader. if remember correctly i got half way thru the root process and it went down hill from there.
TMobile
RC29 / previously Dev 1
Recovery 1.4
HARD SPL
Radio currently 1.22.12.29 / trying to get to 2.22.19.26l
4gb card
(hope i did that right)
Click to expand...
Click to collapse
Okay... you have the recommended recovery and spl.
So all you need to do is get your rom and radio and store the zip files to the root of your sdcard. You don't need to rename them.
Just boot in recovery (power+home) and scroll down to:
[Alt+A] apply any zip from sd
And then you should see the zip files.
Upgrade your radio first.
Then your rom.
Another note... make sure you have a data plan once you've installed your rom. Depending on your rom version, you may not be able to sign in without one. If you can't sign in, you can't use your phone which is why most would recommend a custom rom or an adp rom.
Now... if I'm not mistaken... you do NOT have to partition your sdcard to install a rom (unless it's a HERO rom).
You may want to consider doing so however.
The advantages are that you can have virtually unlimited storage for apps and it's much easier to restore them after a wipe because they are still on your sdcard. Some apps will recognize the partitioned sdcard and automatically do all the apps2sd work for you by default. It is also recommended that you use at least a 2gb class4 card at MINIMUM. Any slower then a class 4 may result in system crashes and errors. Any less then a 2gb card is almost not worth all the effort since you'll likely be using at least a quarter of it for the apps2sd. I would suggest buying at least a 8gb class 6 card for less then $50 online. It's both fast and plenty of storage. With apps to sd, if you do need to wipe you still have all of your apps installed. A great advantage of having apps2sd.
Also... try different roms! There are DOZENS out there! Some have the htc music installed, some have myfaves, some have special cameras, etc. Don't be afraid to experiment. As long as you have a backup and can get to the bootloader (skateboarding androids) and a pc, you can't go wrong! If fact... with the 1.4 recovery you can store several different roms on your sdcard, backup your current rom, wipe, flash a new rom to try it, wipe, flash a different rom to try that one, etc. If you decide that you didn't like any of those... just restore back to your previous backup. Simple as that. No pc needed. However having a pc is handy to get logcat information if it's not booting for some reason.
Speaking of roms not booting... while your experimenting with various roms... you MUST have patience. Sometimes (based on my personal experience with about 10+ different roms) they can take up to 15 minutes to boot up. You can literally be staring at the ANDROID or HTC logo this entire time. Unless you are using ddms.bat or adb shell logcat, you will be clueless of whats going on. DO NOT do anything unless you get the infamous "boot loop". This will be obvious. It will stick at the ANDROID or HTC screen for a while and then blink and go back to the logo. If you see it blink and go back to the logo then try pressing power + talk + menu to restart it and then immediately press the home button to bo back to recovery. Wipe... try again. This time it should work. If it doesn't then restore your backup while you research on that partitcular rom. You may have skipped a step or not have the proper requirements (partitioned card, spl, etc).
With all of that said... good luck and you'll be posting help to other users like yourself before you know it.
Hey Doc, if I'm not mistaken (other guys correct me if I'm wrong), if all, and I mean ALL you have is a boot loader (AKA SPL. ie// skating androids or colored bars) you need to reflash dreaimg.nbh to get a system back.
This ALSO flashes your SPL and RADIO back to default so reflash your radio and SPL afterward. (IN THAT ORDER I HOPE)
Binary100100 is a gentleman and a scholar
nicely written response binary.
I can't stress enough how helpful it is to have the sdk working on a computer when flashing new roms. Get ADB working, it'll save you a ton of headaches.
innerspace said:
nicely written response binary.
I can't stress enough how helpful it is to have the sdk working on a computer when flashing new roms. Get ADB working, it'll save you a ton of headaches.
Click to expand...
Click to collapse
Thank you! I do what I can.
Hey everyone, I'm new to this forum. So...Hi
Anyways, I've got a problem with my Rogers Htc Dream. I was trying to root it and was following a guide on youtube. Then i realized rooting for T-Mobile G1s and Rogers HTC Dreams were different. Now i notice when i turn on my phone it shows a T-Mobile screen instead of the regular Rogers loading screen. I guess i installed the T-Mobile firmware on my phone. I checked in settings the current firmware im running is now 1.0. So, i'm wondering if anyone can help me put back on rogers firmware on my phone and also link me to a Rogers HTC dream rooting guide. Thanks in advance.
Slaii1030 said:
Hey everyone, I'm new to this forum. So...Hi
Anyways, I've got a problem with my Rogers Htc Dream. I was trying to root it and was following a guide on youtube. Then i realized rooting for T-Mobile G1s and Rogers HTC Dreams were different. Now i notice when i turn on my phone it shows a T-Mobile screen instead of the regular Rogers loading screen. I guess i installed the T-Mobile firmware on my phone. I checked in settings the current firmware im running is now 1.0. So, i'm wondering if anyone can help me put back on rogers firmware on my phone and also link me to a Rogers HTC dream rooting guide. Thanks in advance.
Click to expand...
Click to collapse
Yeah I have that too.
Not really an issue. I just too happy to care when I finally rooted my Dream.
Outblaze said:
Yeah I have that too.
Not really an issue. I just too happy to care when I finally rooted my Dream.
Click to expand...
Click to collapse
Okay so, the root worked for you? Everythings alright its just the start up screen that changed?
To get back to stock rogers firmware apply the update from rogers found here:
http://rogers.com/techsupport/
Then follow this guide to get your phone rooted and install cyanogenmod:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod
beav_35 said:
To get back to stock rogers firmware apply the update from rogers found here:
http://rogers.com/techsupport/
Then follow this guide to get your phone rooted and install cyanogenmod:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod
Click to expand...
Click to collapse
I'm abit scared to follow that guide because there seems to be some ifs about it, like it says avoid anything that writes to the kernel, otherwise you're dead. And it says you require a EBI1, how do I check if I have EBI1
"The Recovery Flasher utility will only work if you're on a version of Android that Rogers/HTC hasn't yet fixed.
If you are at the recovery screen, move on to the next step."
Well how do I know if they haven't fixed it? And if we can't use fastboot to flash images, as Rogers prevents it, then if this procedure goes south we're stuck? I can verify the MD5 of the SPL update ZIP 20 times, but that's not going to guarantee that when I flash it it's not going to brick my phone
edit: I booted with camera and power and it says hboot is 1.33.0009, does this mean I don't have to risk bricking when I root? The tutorial is for 1.33.0010.
I think that it makes it sound a bit worse than it is. I have never tried it but from what I have read if you boot a EBI0 kernel with a EBI1 radio it will just freeze. You will just have to pull out the battery, boot into recovery and then flash a EBI1 kernel on top.
Rogers is bad for releasing updates for their devices. All their Android devices still run cupcake, even the new LG Eve. This is to our advantage because none of the rogers firmwares are fixed. You can give the Recovery Flasher a try because the worst that will happen if you have a fixed rom is nothing.
If you have a 0009 spl you can follow the guide here to update your spl and recovery then start following the guide at Installing HTC System Image. You could also just use the method on the wiki for 0010, I cant see any reason that wouldn't work.
My phone is perfectly fine after the gaining root. So far not much of a difference, except for the virtual keyboard and two more screens and a few more apps and options.
beav_35 said:
I think that it makes it sound a bit worse than it is. I have never tried it but from what I have read if you boot a EBI0 kernel with a EBI1 radio it will just freeze. You will just have to pull out the battery, boot into recovery and then flash a EBI1 kernel on top.
Rogers is bad for releasing updates for their devices. All their Android devices still run cupcake, even the new LG Eve. This is to our advantage because none of the rogers firmwares are fixed. You can give the Recovery Flasher a try because the worst that will happen if you have a fixed rom is nothing.
If you have a 0009 spl you can follow the guide here to update your spl and recovery then start following the guide at Installing HTC System Image. You could also just use the method on the wiki for 0010, I cant see any reason that wouldn't work.
Click to expand...
Click to collapse
I really want to root so I can install applications to the memory card, and to get 1.6, but I'm really really really scared that it's going to break. I got the phone from ebay, so I'm pretty sure if it breaks I'm out $300 bucks. I'm really at a cross road here!
Ya i was kinda scared the first time too. Then I just bit the bullet and did it. Try to read through the forums as much as you can to learn as much as you can about how your phone works. Also make sure that you understand each step completely and what it is doing to your phone. This is what I did and it made me feel a lot better about the process.
The main risk is flashing the radio and spl once you are done that the chance of bricking is almost none of not none. If you have any questions that you can't find answers to by yourself just ask and me or someone else on the forum will answer them for you.
Yeah, if you're on the Rogers HTC dream, just follow the Rogers heres your real root thread, and all the guides he post. And follow it while filling in the rest with logic.
You'll probably get lost like I did, don't be afraid to ask around.
does anyone know the warranty if it bricks?
Hey everyone, thanks for the help. I went through with the root and everything seems to be working fine. I can make phone calls and everything. I'm running a hero rom. The only thing thats different is it shows a T-Mobile screen instead of Rogers. I don't think thats a big deal, is it?
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...
Phone: HTC Hero, CDMA
Carrier: Sprint
While others have reported of this problem, the solutions that worked for them dont work for me. Im really stuck.
I know, its an old and slow phone, but I was hoping to go to CM7 to get better performance out of it. Well, I must have done something wrong in the process. My current android version is 2.1-update1. I used z4root to root it and used the clockworkmod ROM manager to install a recent nightly after backing-up my current ROM. Installing the nightly failed, something to do with the zip, but my phone had already been wiped and rebooted in default factory mode. I tried doing the install again with the same nightly and a more recent one, but it kept failing due to a problem with the zips. After one of the reboots, the OS just wouldnt load; seems to be looping on the 'HTC quietly brilliant' screen. I am able to boot in recovery mode, but cant figure out how to get past this looping issue.
Ive tried booting using the back-up I created with no luck. Ive even tried going through the RUU process (cant post a link cause Im a new member here), which results in an error message stating that theres an incorrect bootloader.
I did figure out that I was trying to install CM7 using the wrong zip; had the GSM version. Ive tried installing CM7 with the correct zip, but, after reboot, it loops at the animation with the android on the skateboard and the blue arrow around it. Not sure what it means that the two different OSs loop at, what looks like, the same points.
I probably did something wrong, but Im hoping somebody with a better understanding of all thats involved can let me know if there is any way for me to fix this. Thanks in advance for the help.
grins1 said:
Phone: HTC Hero, CDMA
Carrier: Sprint
While others have reported of this problem, the solutions that worked for them dont work for me. Im really stuck.
I know, its an old and slow phone, but I was hoping to go to CM7 to get better performance out of it. Well, I must have done something wrong in the process. My current android version is 2.1-update1. I used z4root to root it and used the clockworkmod ROM manager to install a recent nightly after backing-up my current ROM. Installing the nightly failed, something to do with the zip, but my phone had already been wiped and rebooted in default factory mode. I tried doing the install again with the same nightly and a more recent one, but it kept failing due to a problem with the zips. After one of the reboots, the OS just wouldnt load; seems to be looping on the 'HTC quietly brilliant' screen. I am able to boot in recovery mode, but cant figure out how to get past this looping issue.
Ive tried booting using the back-up I created with no luck. Ive even tried going through the RUU process (cant post a link cause Im a new member here), which results in an error message stating that theres an incorrect bootloader.
I did figure out that I was trying to install CM7 using the wrong zip; had the GSM version. Ive tried installing CM7 with the correct zip, but, after reboot, it loops at the animation with the android on the skateboard and the blue arrow around it. Not sure what it means that the two different OSs loop at, what looks like, the same points.
I probably did something wrong, but Im hoping somebody with a better understanding of all thats involved can let me know if there is any way for me to fix this. Thanks in advance for the help.
Click to expand...
Click to collapse
I *think* your error, in general, was using a bunch of "easy" one click methods and not properly learning (READING) about what the proper steps are. Here is my advice (assuming you are still rooted) -
1.boot into recovery (power off phone, hold home button, press power)
2.wipe data/factory reset
3.mounts/storage - wipe system and boot
4.restore nand backup OR flash ROM/gapps (from the same thread)
5.reboot, and be patient, bootup could take 5-10 minutes.
Good Luck.
You are the man (or woman)! I believe the formatting of system and boot is what did it. Really appreciate the help.
grins1 said:
You are the man (or woman)! I believe the formatting of system and boot is what did it. Really appreciate the help.
Click to expand...
Click to collapse
It is important, as Il Duce said, that you definitely do a good amount of reading when you want to get involved in rooting your phone. You are opening yourself up to some great innovation and fun, but you can also cause yourself a lot of headaches.
Recovery is your friend. If you can get into that, at least you know things are ok. I like to wipe (or format) system, data, cache, and boot 3x just to make sure that clockwork recovery cleaned everything and there are no dingleberries from the last rom I was using.
Flashing the correct type of rom is even more important. Don't flash a gsm rom to a cdma phone and NEVER flash a gsm radio to a cdma phone. Once you delve into the reading aspect of XDA, you will see that is the sure way to brick your phone.
Some roms take longer than others to boot up. Let it run its course. Sometimes it will reboot right after installing. At some point, you might want to make a nandroid of the new rom you are running and go back to your stock (2.1 update 1) and update your PRL, baseband, etc. (if you haven't done an update in a while).
Have fun, that is the most important part and we seem to have a lot of it here in HeroC XDA land.
You know, I put in a fair share of reading about how to update the ROM on my phone and I was under the impression that it would be fairly simple. I figured that since this has been done for quite a while and all these tools have been developed, I wouldnt need to know what happens on the back end during a root or ROM install.
But I did get myself into a bind that I wasnt able to figure out on my own. And with the help of this forum, I was able to get past my problem. Im glad to say I now have a phone that is functioning very smoothly with CM7 and the apps I need.
Next step for me is figuring out how to save my apps to the SD card so that I can install from there if/when I update my ROM in the future.
Thanks again for the help!
Get titanium backup FTW.
BANG! from my shooter...