Problems after rooting / flashing my phone - G1 Q&A, Help & Troubleshooting

Hey everyone,
Sorry to be creating a new topic on this but I have literally spent the last 3 hours trying to figure this out and have searched the entire forum looking for answers and couldn't find any.
Here's the deal. I was following this guide on rooting my phone and got all the way to the image part. I was going to install this build which mentioned I needed the DangerSPL. Went ahead and followed this guide on how to install the DangerSPL and got to the flashing DangerSPL part, where I was supposed to install the CM 5.0. (Note: When trying to install the CM 5.0 I also get the e: can't find update script as well)
There's where the problem happened. After getting that in my phone will not go any further than the T-Mobile G1 screen. It just freezes there and there it stay. I tried updating the CM 5 but it always gives me the message e:can't find update script, and that's downloading straight from the website and then renaming it to update.
So as of right now I don't know where to go, I'm pretty stuck at this point. I don't know if I should be doing something to prevent the can't find the update script message or what, or how to get past the G1 screen.
Any help will be deeply appreciated as I'm stuck without a phone at the moment.
Thanks a lot in advance.
Edit:
Update: By returning to "factory" settings I was able to at least start up the phone, so that's a positive. Negative is that it is now a 1.0 version of the droid, so I would much rather be able to install something slightly better but I still have been running into the error can't find update script on several different builds.

Ouch.... I feel your pain... 1.0 is pretty old. Few questions before troubleshooting:
1. What phone do you have: G1, Dream, Roger's Dream.. etc
2. What does it say in your H/F boot (power up using camera and power button and copy 4 lines that you will see)
3. What build are you on right now (Menu-Setting-About phone)
Once we have that - we can proceed.

Edit:
After going through the steps again as I restored factory settings the rooting and upgrading finally did work. Go figure.
Thanks for the help, it was really appreciated.

Related

This can't be happening... [SOLVED]

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.

Need help.

Okay for those of you who don't know, I totally bricked my phone based on a dumb decision last time and not knowing what I was doing.
I am thinking off trying to root my phone again, any advice on what rom I should root to and which is the best and most stable for the G1.
Kaos Chase said:
Okay for those of you who don't know, I totally bricked my phone based on a dumb decision last time and not knowing what I was doing.
I am thinking off trying to root my phone again, any advice on what rom I should root to and which is the best and most stable for the G1.
Click to expand...
Click to collapse
u should really go with cyanogens roms
Cyanogen's latest is pretty sweet. As long as you follow the steps correctly to root your phone, you shouldn't have any problems flashing any of the roms available. Then you can test them out, and see what you like.
does anyone know any good tuts to use to do so?
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
melterx12 said:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
Click to expand...
Click to collapse
Thank you so much everyone! You all were a huge help. I have rooted my phone successfully this time and I love it!
I followed the instructions from the link on this thread to put cyanogen on my g1 but after the skateboarding android logo faded all I got was a illuminated phone I let it sit that way for 25 minutes hoping something would happen but nada so I restored a backup. Can anyone tell me what went wrong and how I can get cyanogen working?
Nobody can tell you what went wrong since we don't know what step you skipped/didn't do right based off that statement. All we can say is follow the guide to a T. The guides are the best the communitty has to offer/has produced on how to do what you want to do. If you can't follow the guide, sadly there is nothing we can do to help beyond repeating what the guide already says.
I've got cm recovery 1.4 so that step and the ones leading to it are done right, right? Then I ran the recovery, made a back up, wiped data, applied zip drc83 defanged, applied
Cm update 4.2.13 (I think 13, whatever stable version the "latest version" link give you), applied ota radio, and rebooted (automatically took me back to recovery) rebooted again, got g1 logo followed by the cyanogen android logo once that faded all the lights on my phone came on and stayed on and I had no display (apart from the backlight).
I tried multiple times with no luck. I downloaded the cm update from my phone could that of caused a problem? Everything else was dl'ed from a pc.
What's the differance between drc83 and signed dream devphone should I try that instead?
http://forum.xda-developers.com/showthread.php?t=563679
Follow the guide to a T, since you are partialy there I will tell you what you have left:
1. Download the developer recovery ROM (This is different than drc83 by a lot)
2. Download the latest CM
3. Put both on the root of your SD card
4. Boot into recovery mode, flash the developer ROM, then flash the latest CM
5. Use the "Home" and "Back" buttons to reboot the phone
6. Tada! Success!
7. Never, ever, do anything the guide doesn't tell you to do. If it says flash file X don't flash file Y because you think it is close enough. Never do extra stuff, ie if it doesn't say flash a radio by itself, don't flash a radio by itself because it seems like a good idea.

[Q] Android Newbie in desperate need of help...

I recently received a Nexus One from a friend. The bootloader is unlocked and I believe it is rooted. When I got it it kept generating some sort of process error and the phone randomly rebooted. I tried reinstalling a ROM and then the phone just sat with the "X" boot screen. 3 days later and I managed to find a ROM that makes the phone usable (22607-ERD79-update-nexusone-stock-signed). The phone ran fine with that but it is now 2 generations old and I want to update to Gingerbread. Every attempt I have made has ended with the phone just sitting there with the "X" screen after 20 mins. Clearly the updates aren't working. I'm completely confused by all of this.
I'm coming from an iPhone that I was able to jailbreak and hack with no problems. I also have experience with WinMo phones. Never had these issues.
Most of the updates seemed to install correctly. The log screen completes all the steps and ends with "Install from sdcard complete."
Running RA-nexus-v1.5.3
Please help me with this. I want Gingerbread!
First, what versions of Radio and HBoot you use?
How would I tell? Where would I find this info?
Sounds like you are not wiping data.
Whenever you change to a different rom (other than upgrading the same rom) you need to wipe the data partition, otherwise you could get bootloops, stuck at X, unstable systems, etc.
Sometimes not wiping works out okay, but in this case it sounds like it didn't.
I have tried the wiping. As I understand it, I should wipe before flashing the new ROM?
THe baseband is 32.41.00.32U_5.08.00.04
Found them!
HBOOT = 0.35.0017
radio = 5.08.00.04
so I've now upgrade to recovery-RA-supersonic-v2.3.img
supersonic is the wrong phone.....
OK. What is the correct one?
So apparently I was provided the wrong recovery. I did a little research and believe I have the correct one now. recovery-RA-passion-v2.2.1.img
Now should it work...
Still not working. I have no idea what I'm doing wrong. This is really getting under my skin.
Can anyone offer any more info on this? Maybe walk me through it. I have to believe that I am doing something wrong as the phone seems to work otherwise.
Return to a completely stock image. Follow the unroot/restore method from the wiki, using passimg and the FRG33 image...
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_%26_Tutorials#Unroot_.2F_Restore_your_Nexus
Sent from my Nexus One using XDA App
OP I had a similar issue. Wiped, installed, wiped, installed. No ROM was stable. It constantly rebooted.
Luckily it was under warranty and HTC replaced it. The new device is rock solid but has burn-in (Pandora buttons always visible and I don't even have Pandora installed).
They are replacing this one as well.
Hope it's under warranty. If so, HTC is great, even with an unlocked bootloader.

[Q] HTC Hero looping on the boot screen. How can this be fixed?

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...

Need help to flash back to donut :)

Guys, i'm running a G1 with the latest cyanogen mod but it's been eating at my battery too much and it's way too slow. So i wish to downgrade to donut (1.6). Can anyone help me? I haven't flashed an android phone in a long while and i guess i forgot.
I appreciate it
PS: will that lock the phone back up? Or will i still be able to use it normally with any carrier?
Posting reply because the topic is...well in the lack of better words, invisible, both in my stats and on the forum...(the heck?)
The phone will still be unlocked.
You need to flash a new ROM.
Try superD. It's a donut rom.
http://forum.xda-developers.com/showthread.php?t=613809
Download: http://files.benbuchacher.com/Android-MT3G-G1 Archive/SuperD/SuperD 1.11/NoRamhack/
You'll need to wipe and flash it from recovery
The best ROM for G1 is probably froyobylaszlo. Its fast.
You'll need the 2708+ radio and spl though. And thats advanced to install
Figured it'd be easier to unroot it...couldn't wait anymore since it's my only phone and i need it.
But i really appreciate giving me the correct link for SuperD. I've been searching and i didn't know which one of the 2 available links to download.
BTW, when i do decide to root it again, i guess i'll be using SuperD, but what steps would i have to take to root and flash the new rom. I am asking you because it's an older rom and i am new to this.
u2020bullet said:
Figured it'd be easier to unroot it...couldn't wait anymore since it's my only phone and i need it.
But i really appreciate giving me the correct link for SuperD. I've been searching and i didn't know which one of the 2 available links to download.
BTW, when i do decide to root it again, i guess i'll be using SuperD, but what steps would i have to take to root and flash the new rom. I am asking you because it's an older rom and i am new to this.
Click to expand...
Click to collapse
http://wiki.cyanogenmod.com/wiki/HTC_Dream:_Rooting
Stop at "Flashing CyanogenMod"
Put the SuperD zip and this zip on the SDCard
Flash the DRC83 zip first then SuperD
Reboot and Enjoy
Thanks a lot I appreciate it
And again it's me. Having more problems. Got a Samsung Galaxy Trend as an early birthday present yesterday and now i want to completely restore my g1 back to stock (again). This is where things got complicated. I used a tutorial on "Unlockr" which obviously doesn't work. Managed to unroot and return to 1.0, then i managed to get to 1.5 where i started receiving errors with every single update i tried. So i re-downloaded 1.0 (rc29), i go into the bootloader (the red-green-blue-white screen) it starts checking something then pops out a "not allow" error, which then sends me back to the rainbow screen where i get the serial0 error.
I've tried downloading dreaimg.nbh from multiple sources but i always get that error.
Here's some info for you guys:
Hboot-0.95.0000
CPLD-4
Radio-2.22.19.26I
Now i honestly have no idea what to do. Can anyone give a fellow android user some assistance?
EDIT: I somehow managed to get my hands on the right files and went all the way up to 1.6. But now i can't activate the phone because i don't have a data plan and i can't use adb to activate wifi. Why must this be so ridiculously hard?
What can i do to flash back to rc29? I need to do that so i can activate the phone and then go back up to 1.6.
here a guide how to do it
u2020bullet said:
And again it's me. Having more problems. Got a Samsung Galaxy Trend as an early birthday present yesterday and now i want to completely restore my g1 back to stock (again). This is where things got complicated. I used a tutorial on "Unlockr" which obviously doesn't work. Managed to unroot and return to 1.0, then i managed to get to 1.5 where i started receiving errors with every single update i tried. So i re-downloaded 1.0 (rc29), i go into the bootloader (the red-green-blue-white screen) it starts checking something then pops out a "not allow" error, which then sends me back to the rainbow screen where i get the serial0 error.
I've tried downloading dreaimg.nbh from multiple sources but i always get that error.
Here's some info for you guys:
Hboot-0.95.0000
CPLD-4
Radio-2.22.19.26I
Now i honestly have no idea what to do. Can anyone give a fellow android user some assistance?
EDIT: I somehow managed to get my hands on the right files and went all the way up to 1.6. But now i can't activate the phone because i don't have a data plan and i can't use adb to activate wifi. Why must this be so ridiculously hard?
What can i do to flash back to rc29? I need to do that so i can activate the phone and then go back up to 1.6.
Click to expand...
Click to collapse
hey bro, I found this tutorial http://androidandme.com/2009/10/news/how-to-manually-install-the-official-t-mobile-android-1-6-on-your-g1/very effective on bringing your G1 back to stock. I've used this tutorial once before, so I thing this will help you too.
Good Luck :good:

Categories

Resources