Database Develop

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.

[Guide] One-Click Root for Rogers HTC Dream

EDIT: I've recently discovered a snag to using the default method of rooting and installing CyanogenMod on the Rogers HTC Dream. If you follow the regular instructions you will end up with radio version 2.22.19.26I. Your phone will work, but if you are in EDGE coverage areas your data speed will end up in the toilet (avg. 25-35kbps). I've recently been directed to a wiki on the CyanogenMod web site that guides you to installing CyanogenMod while keeping the 3.22.20.17 radio. The link is here Full Update Guide - Rogers Dream EBI1 to CyanogenMod - CyanogenMod Wiki and if you choose to follow it you can pretty much ignore this tutorial. The only caveat is that this method installs a custom kernel and you may not be able to use other themes and/or roms that change the kernel.
There is also now a port of Amon Ra's Recovery rom for the Rogers Dream. You'll no doubt find that a lot of the recovery roms out there won't boot after flashing the 3.22.20.17 radio. That's because the Dream, while EBI1, is not 32A. This new version is from Amon Ra himself and is fully functional with working console. Download it here. It appears recently purchased Rogers HTC Dreams are starting to show up with SPL version 1.33.0010, a 'perfect' SPL that disables remote booting recovery.img files used to install the 1.33.2005 SPL.
Needless to say, this makes rooting your phone a little difficult
I found a solution to this problem after foolishly installing the Rogers update for the HTC Dream (the update, in addition to un-rooting your phone, installs the 1.33.0010 SPL). After several fruitless tries root with flashrec, I tried running it with a different recovery image than what is built-in to the app.
Keep in mind, I have only attempted this on a Rogers HTC Dream 32B. I cannot guarantee good results on other revisions or the Magic.
There, with that caveat out of the way:
1. Download Haykuro's root kit here.
2. Extract the recovery.img and update.zip files from the download and copy them to the root of your sdcard's fat32 partition (if you haven't partitioned your card yet for A2SD, then just the root of the card itself).
2. Last time I checked, the one-click root app, flashrec, has been pulled from the Market, so download it here.
3. Install the app and start it, it will look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Tap 'Backup Recovery Image', in some cases the app will fail to backup the image. This shouldn't be a problem, but if it works, it's always nice to have a backup.
5. In the blank above the greyed-out button enter '/sdcard/recovery.img' without the quotes. If you were successful in making the backup, the top button should change to white and say 'Flash Custom Recovery Image'. If not, don't worry, there is a hidden button to the right of the backup button that will bypass the backup requirement. Like so:
6. Press 'Flash Custom Recovery Image'. If you get a flash failed message, try flashing with your phone unplugged from USB.
7. Power your phone down.
8. Power up your phone while holding the home button. You should get the older 1.2 Recovery Menu. If your phone hangs at the Rogers logo, remove your battery, re-install or try the 3-finger salute (Phone, menu, and power button together) and try again. If it still hangs on the Rogers logo, reboot without the home key, this will bring you back to normal boot. You won't be rooted but you won't be bricked.
9. Once you're at the recovery menu, choose the second option, apply sdcard:update.zip. In some cases you may get an error something like E: not found. If you choose the second option again, it should find the update.zip alright and then press home to continue.
10. Now click on reboot (Home & Back). Press and hold the camera button and you should boot into the new 1.33.2005 SPL.
11. If all has gone well and you see hboot 1.33.2005, you can safely follow the rest of the rooting instructions in this thread. There's also a great set of instructions for installing Cyanogen's 4.2.X roms in the same thread. The post is here.
Of course, these instructions may be rendered moot if Rogers chooses to fix the vulnerability that allows one-click root at which point we'll have to hope someone manages to find a way around the so-called 'perfect' SPLs.
If after a couple attempts you remain stuck at the Rogers logo, remove the battery, reinstall it and then power up normally. You should then boot back to the unrooted phone and it will restore the default recovery. You may not be rooted, but at least you're not bricked.
Good luck, and happy flashing!

Thanks Charrion. As usual, battery is dead, so I will try tommorow and post results.
Also, how do I install Flashrec from desktop to Dream?

jake_gt said:
Thanks Charrion. As usual, battery is dead, so I will try tommorow and post results.
Also, how do I install Flashrec from desktop to Dream?
Click to expand...
Click to collapse
The same way you install almost any .apk (meaning not core system apps) by putting it on the sdcard and installing with package installer

Wow, rogers threw you guys the perfect spl, that is some major suckness, why do providers just let us power users do what we do, it's stuff like custom roms that advance the os and get people hooked to stay with the os, just let us do our thing, damn it

gridlock32404 said:
Wow, rogers threw you guys the perfect spl, that is some major suckness, why do providers just let us power users do what we do, it's stuff like custom roms that advance the os and get people hooked to stay with the os, just let us do our thing, damn it
Click to expand...
Click to collapse
My guess is it was a support decision. Fewer people rooting their phones, fewer support calls from people who bricked their phones claiming it's 'defective'.
Sucks, but I can understand why they choose to do so. I wonder if they would provide a means to replace the perfect SPL with a flashable one once the contract and/or warranty expires.

I need help installing flashrec. I copied flashrec-20090815 to the root on my SD card. I have a path to tools and e:\ but when I try install command from SDK it returns
"can't find 'flashrec-20090815' to install" I have removed and re-installed drivers but same result
Thanks for any advice...

jake_gt said:
I need help installing flashrec. I copied flashrec-20090815 to the root on my SD card. I have a path to tools and e:\ but when I try install command from SDK it returns
"can't find 'flashrec-20090815' to install" I have removed and re-installed drivers but same result
Thanks for any advice...
Click to expand...
Click to collapse
If you're using adb to install it, you need to have the apk in the directory from which you are running the adb command. To install it from the sdcard use a file explorer like Astro, browse to the sdcard's root and tap the apk there.

Yeah I guess but an unrooted gphone is boring, the android os is so bland that it needs a lot of help, I mean a tremendous amount, without great devs like drizzy, jac and cyanogen I would have done gave back my phone

gridlock32404 said:
Yeah I guess but an unrooted gphone is boring, the android os is so bland that it needs a lot of help, I mean a tremendous amount, without great devs like drizzy, jac and cyanogen I would have done gave back my phone
Click to expand...
Click to collapse
True 'dat. I went from liking my phone to loving my phone by installing CM and Ted's Hero theme. But then I came from a background in computers and have some Linux experience, the rooting and modding wasn't too difficult and what problems I had I was able to work out by hunting around XDA and the net at large.
Some of the people attempting to root their phones now are a little out of their league and probably shouldn't be making the attempt without a little more knowledge and really shouldn't be messing with the experimental roms.
I don't mind helping people out from time to time but I'd hate to be a support person for any one of the carriers dealing with someone who bricked their phone.

Hey,
I just followed your steps and it booted into the custom recovery.img. I'm using and HTC dream with 1.33.0010 SPL.
Thanks a TON for these instructions by the way, but I have one more question. If it boots into custom recovery, do I still need to change my SPL to 1.33.2005 or can I just go ahead and flash a custom ROM?
_________
Rogers HTC Dream 32B (Black)
SPL 1.33.0010

tahnok said:
Hey,
I just followed your steps and it booted into the custom recovery.img. I'm using and HTC dream with 1.33.0010 SPL.
Thanks a TON for these instructions by the way, but I have one more question. If it boots into custom recovery, do I still need to change my SPL to 1.33.2005 or can I just go ahead and flash a custom ROM?
Click to expand...
Click to collapse
If you want to use any of the mainstream roms like Cyanogen's without using the Rogers customized one, then yes because you also have to flash the radio image mentioned in haykuro's rooting thread. If, however, you wish to stay with the Rogers specific Cyanogen rom or any rom specifically for Rogers phones you should be able to stick with the 1.33.0010 SPL.
But, having said that, I've never tried it myself so I don't know for sure. I do know that if you plan on using any other non-custom rom you have to replace the SPL among other things.

Finally root
Thanks for the thread Charrion, I finally rooted last night. Had to force the apk extension on flashrec (for some reason my PC downloads the file as a zip)
after that, your instructions worked without any problems.
Let me buy you a beer!

Hey.
I'm new, so silly question. How do you find out which SPL you have?
Also, why do people make 'Rogers' ROM's when rooting your phone allows you to install any ROM you want? Right? Isn't that how it works?

honestly do search take away a part of your soul...
jamieownsu said:
Hey.
I'm new, so silly question. How do you find out which SPL you have?
Also, why do people make 'Rogers' ROM's when rooting your phone allows you to install any ROM you want? Right? Isn't that how it works?
Click to expand...
Click to collapse
you honestly have no clue what searching is at all... camera and power for bootloader which will tell you what spl you have.
edit: Charrion said why below me why rogers rom have to be cooked. Thank you Charrion
one more time... i don't even have a rogers phone or well know anything about rogers other than the name but for reason i came across that info... search!

jamieownsu said:
Also, why do people make 'Rogers' ROM's when rooting your phone allows you to install any ROM you want? Right? Isn't that how it works?
Click to expand...
Click to collapse
No, simply rooting a Rogers phone doesn't allow you to install 'any' ROM.
The main reason is that the Rogers phones use a different radio image than the others. Using a standard rom will not work with the default radio images the Rogers phones use. Therefore, you have two options, you can flash your radio to match phones like the T-Mobile G1, etc. or you can use the roms customized for Rogers specific radio image.
The main argument is that because the customized rom works with the radio image supplied by Rogers you shouldn't experience problems with 3G, sms, etc and it's easier to return to the stock rom. However, with the standard roms, you don't have to wait for someone to cook a custom rom for your Rogers phone.

Thank you
Thank you so much Charrion.
I applied this and it works on my Dream
was: 1.33.0010
now: 1.33.2005
I was hopeless since the goldcard method did not work for me.
Thank you.

jisri said:
Thank you so much Charrion.
I applied this and it works on my Dream
was: 1.33.0010
now: 1.33.2005
I was hopeless since the goldcard method did not work for me.
Thank you.
Click to expand...
Click to collapse
Good to hear. I tried just about everything after I foolishly installed the update with its dreaded 1.33.0010 SPL, even the goldcard. I just hope Rogers next update doesn't include the kernel patch that blocks one-click. I'm sure someone will find a way around that too, but it's a pain.

Thanks for your reply Charrion. That cleared it up perfectly for me.
As for david1171, see the following:
fo⋅rum
–noun, plural; fo⋅rums; /ˈfɔrəm, ˈfoʊrəm/ [fawr-uhm, fohr-uhm]
an assembly, meeting place, television program, etc., for the discussion of questions of public interest.

Charrion said:
The main argument is that because the customized rom works with the radio image supplied by Rogers you shouldn't experience problems with 3G, sms, etc and it's easier to return to the stock rom. However, with the standard roms, you don't have to wait for someone to cook a custom rom for your Rogers phone.
Click to expand...
Click to collapse
Thanks Charrion for the info but do you know what problems are people experiencing?

beav_35 said:
Thanks Charrion for the info but do you know what problems are people experiencing?
Click to expand...
Click to collapse
Some people in 3G coverage areas have claimed they don't get 3G when they use the non-Rogers roms but I'm not sure of the veracity of that claim.
Sadly, I'm not in an area that gets 3G, yet. I do know that I've used the non-custom Cyanogen roms since 3.6.8.1 and haven't experienced any problems thus far.

[Q] Activate or Locked? Which one my phone is?

Hi,
I'm not sure what should i do now with my G1. I just received this from my cousin. It is 1.5
Here is my device.
DREA100 PVT 32B
HSPL10.95.3000
CPLD-4
RADIO-1.22.12.29
Oct 20 2008
i want to flash rom with 2.2 do i need to do the following first?
-Do i need to get back to RC29 (1.0) to activate the phone first??
-Can I go ahead and update Radio/SPL ? and which one i should use?
-With my Radio I should go for not "DangerousSPL" ?
Thanks for help

is your phone alredy rooted? if it is flash either one of these radios: http://forum.xda-developers.com/showthread.php?t=831139 (that has 2 radios) or the one in http://sapphire-port-dream.googlecode.com/files/ota-radio-2_22_19_26I.zip (direct download) . (the thread with the rom will tell you which radio to use). if you use the radios provided in the first link, use the spl provided in the op (it ends with 0013d) i have also uploaded that. if your rom needs the old radio (the second link), use the spl provided.
Rom bible: http://forum.xda-developers.com/showthread.php?t=668090
This has many of the roms for the g1 but the newer ones (gingerbreads, senselx etc) arnt in this. just look in the development section.
G1 root: http://wiki.cyanogenmod.com/wiki/HTC_Dream (i used this method to root. Follow the steps carefully)
----edit----
i forgot to ask if this is a u.s dream bought in the us or a different g1 (rogers, orange, etc.)

Thank you very much.
My phone is rooted with 1.5 Android on it. I did follow someone's instruction on xda to hard reset successfully. It asked for the activation. But since i want to flash a new rom I'm not sure whether i have to activate it first or just flash the new rom?
Also, what is the different between Hboot and HSPL ? Some rom's thread said it require hboot but is it the same with my current rom?
There're so many abbreviate words -.-'
About my G1, I'm not sure what is the different between US or the other. But on the top front of it has "T-Mobile" branding print on it. on the back there is the words "with Google" when boot with Sim card it can change 2 languages "English" and "Spanish"
Thanks

okay, you have the us version. give me a link of a rom you want to flash and i will tell you what to do. hboot and spl are the same thing. by activate do you mean the setup screen where it says touch the android? If you have a data plan just sign into your google account easy. if not and you have an sd card reader, download the rom (from your computer) and put it on the sdcard. still on the setup screen boot into recovery and flash. Reply with more description and i will try to help.

Thank again.
Here is the rom I want to flash.
http://forum.xda-developers.com/showthread.php?t=929678
I have sd-card reader, so i will go for the copy to card method.
Thank you for your kindness.

ok, download the rom first. this rom requires one of the radios in this link: http://forum.xda-developers.com/showthread.php?t=831139 (I use 28.25)
For the spl use the one i provided in my first post hboot0013d.
once you have downloaded them onto your pc put them on the sdcard. Is your sd card already partitioned? and what recovery are you using? clockworkmod or amon ra or stock. to check hold home and power at the same time while the phone is off and look at the text near the bottom of the entire screen.

Hi, Thanks again,
I did partition my card, Fat32,Ext3,Swap
but with the Home + Power boot i can see the yellow alert on the screen. No text at all. So i press Alt-L to view Log and here is what i see.
"Android system recovery utility
E: Can't open /cache/recovery/com
mand
Home+Back - reboot system now
Alt+L - toggle log text display
Alt+S - apply sdcard:update.zip
Alt+W - wipe data/factory reset"
and the background is the warning
Also, Here is the information from "About Phone" menu in settings
Model number : T-Mobile G1
Firmware version : 1.5
Baseband version : 62.33.20.08H_1.22.12.29
Kernel version :
2.6.27-00392-g8312baf
[email protected] #2
Build number : CRB43
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

if you have wifi or data plan, go to the market and search for rom manager.
When you open the app it says flash clockworkmod recovery. scroll down to where it says flash alternate recovery, ra recovery 1.7.0. click on that. now you have a rooted recovery. SO if you downloaded froyobylaszlo, and radio 2708 or 2825, and hboot0013d and put them on your sdcard, you should now be able to flash them. hold home + power and you will see a new menu. scroll down
to the wipe part and wipe everything. Then scroll to flash zip from sdcard and click the radio. it will take a while and reeboot into a different screen. when it comes back to recovery, flash the hboot and it will do the same thing but it will take way shorter amount of time. then wipe everything again and flash rom. after you reeboot it will take about 5-15 minutes to get to the setup screen. if you had apps before you wiped and want to back them up, use titanium backup on the market. then when you set up your new rom, just install titanium backup and restore from there

this link might help u...
androidcommunity.com/forums/f8/please-help-me-cant-update-anything-19009/
u r rooted....right?
so what's the reccovery u r using??

alokated said:
this link might help u...
androidcommunity.com/forums/f8/please-help-me-cant-update-anything-19009/
u r rooted....right?
so what's the reccovery u r using??
Click to expand...
Click to collapse
he has stock.

Hi,
I can't download clockwork. I can't find it on the market. When i try to search 'Rom Manager', there're only games stuff emulator. The word 'Clockwork' doesn't get anything close to Rom Manager. So i download directly on my computer and try to installed it via file manager but it saids 'clockwork can't install on this device'.
Urr.. Stock rom? I though stock rom is android 1.0 but mine is 1.5 ?

see...ur radio is outdated for ur android version.
u need to upgrade that...about spl(10.95.3000) i'm not really sure...will try looking for that...
but, r u rooted???
in that case u should change into amon ra recovery....
also,get a new/different sd card...format FAT32...and add all files u need into the root of the card....and if u have amon ra installed u need not change names into update.zip every now and then.....
for 1.5 android, 2.22.19.26 would be the ideal radio....
check out other topics on xda too...
u can search for what u need....
luck

download a recovery from cumputer to sdcard and see if there's an app called terminal emulator in market. there are many apps just choose one http://forum.xda-developers.com/showthread.php?t=566669 amon ra recovery, gives guide on how to install. if terminal emulator is available, use that method provided in the link.

Hi, Thanks cripgballerkundikusu11
I did update RA Recovery via the terminal. I download radio from the link you mention and copy it along with your hboot but when i try to flash zip from sdcard and select radio. It always failed. It said
Can't Install Radio
Your Radio Series: 1.22
is not 2.22
The link about SPL lead me to (for my 10.95.3000 )
http://forum.xda-developers.com/showpost.php?p=6510019&postcount=76
Does it mean that i have to update SPL first before I can update radio?
Is it neccessary to update that? Or i can go ahead with your hboot0013d-signed.zip ??
Thank again

spl 1.33..2003 right? dont go for .2005 as that is suitable only for 2. radios....
also...did u format ur sdcard?
and using amon ra recovery u dont have to rename anything....

Ok. Thank you everyone especially "cripgballerkundikusu11" for providing very helpful.
I think G1 is the most difficult I've ever done. I did some on wm phone without any difficulty. I guess it because of hboot,radio varieties. So I don't know if this will help other people or not but hope it does.
Here what i did. (Thank to cripgballerkundikusu11, I made through it.)
1. I did update RA_Recover from Terminal Emulator follow the instruction from here
http://forum.xda-developers.com/showthread.php?t=566669
2. Update Radio dream_magic.radio-2.22.23.02-signed.zip it restart automatically
3. Update Radio update_2.22.28.25_S.zip it will restart automatically NOTE! It will ask you to confirm because it detect something about bad HBOOT. If your device's firmware and settings everything same as mine , u may continue. else, read more/ search more for the option.
4. Update HBoot from cripgballerkundikusu11 NOTE! it won't automatically reboot. Must reboot with HOME+Back or Menu button only else it won't installed.
5. Install ROM
6. Pray hard and it works!! yeah it works i've Froyo now.
I think it lack of document on how to update radio from 1x to 2x. For myself, im very scare to force install 2.22.23.02 radio before install 2.22.28.25 but it went well. Lucky me.
Anyway, thank you all people for helping me out. Thank again "cripgballerkundikusu11" giving me a big help.
Hope this thread help other.

im glad it worked. and that's what xda's for.

but remember....there's always a risk when u flash spl via recovery....
u'll find that warning EVERYWHERE....
and G1...not all that tough.....
and i'd suggest u move in for one of the gingerbreads.....
luck!!!

alokated said:
but remember....there's always a risk when u flash spl via recovery....
u'll find that warning EVERYWHERE....
and G1...not all that tough.....
and i'd suggest u move in for one of the gingerbreads.....
luck!!!
Click to expand...
Click to collapse
yeah mr alok is very right saar. right. there are many stable gingerbreads now, they have more features

Ummm Gingerbreads. -.-'
I think i will stick with froyo for the while.
Anyway, I never know that Qualquamm72001 is this slow. I can't play angry bird on it. Quite a shame.
But word, excel, email are work fine. And the screen is very clear compare to my friend's Apanda A60 screen. I think HTC screen is much more better than the other. Might be placebo.
Thank everyone.

[Q] Wifi problem with Froyo

Posted this in the wrong place... so here I go again.
Alright as the Title says I got a problem with Froyo.
First of all, this is the first time i ever tried anything with a cellphone, although so far it went well (took me long though).
First I removed an old version of cyanogenmod from the old user.
Then I followed this guide: http://forum.xda-developers.com/show....php?t=1098899
Then I installed Froyo by Laszlo 5.2
http://forum.xda-developers.com/showthread.php?t=929678
Now to my ultimate surprise, I actually got this all done and it works perfectly, except for one thing. Wifi does not work. When I turn it on it starts scanning for networks, then gives the message "unable to scan for network" and Wifi automaticly gets turned off again. Before installing this I always found 2 networks from the point I'm sitting now.
I simply got no clue what it could be.
Some info. Following the guide for radio and boot I got the correct information in the bootloader as mentioned in step 3:
Dream PVT 32b SHIP S-on
HBOOT 1.33.0013d (drea10000)
CPLD-4
RADIO 2.22.28.25
OCT 21,2009,22:33:27
About Phone:
Android version 2.2.1
Baseband version 62.50SJ.20.17U_2.22.28.25
Kernel version 2.6.34.8-froyobylaszlo [email protected] #1
Mod version FroyoByLaszlo-5.2
If you need more info, just ask.
And thanks in advance,
Greetings,
Noddahead
edit:
Little update here. On some forums I found that a file bcm_supp.conf in /data/wifi caused a problem like mine. When I plug in my phone in my pc I only see the sd card. Therefore I installed sdk/adb thing, connected with my phone (correctly). and I manually tried to remove the file via cmd. This resulted in the notification that the file did not exist.
Hence, back to nothing. Any way I can make my internal memory show up again?
All in all it seems like I got the same problem as many people had with Froyo. But it seemed solved for everyone after a certain patch. My Froyo version is obviously more recent. And no one seems to have this problem with this version of Froyo (in the Froyo by Laszlo thread page 97ish and forth)

Alright. I'm trying my very best but I'm really clueless right now.
After not getting this wifi to work I tried the COS-DS mod. Installing it and everything went fine, except for one thing: the settings menu would not open.
Not being able to do anything on that I went on to the next to the next rom: Cyanogenmod 7 Magpie. Once again, most things work, but some do not. I started out with an input.latin error, which I somehow fixed. I do not have a status bar, and I think I'm missing some other things too... for example, the android market does not appear. Wifi does work now though.
I have no clue what's going on... do I just need to start over from scratch? Trying Froyo again? I could really use some advise.
Noddahead

Have you tried wiping properly before flashing the new roms because I've never had a wi-fi issue unlees it was broken in the kernel which is rare these days.

Thank you for replying.
I am back to Froyo by Laszlo now, seems the best option. Before installing that I wiped cache, wiped data/factory reset, and I used Ohsaka Superwipe. But no Wifi.

Using another Kernel with Froyo by Laszlo did not help.

Well, last update here. Never got it to work, now having succes with GingerYoshi. This topic can be locked.

try everything???? re partition and re format sd card, try ezbifftest 2708 kernel, i had best luck with laszlo rom

First of all, thank you for your guide.
I had not actually partioned before installing froyo, and I did partition before using Ginger right now.
If I would repartion right now, and then reformat... can I then instantly install froyo laszlo and the kernel? And what values for the partioning?

you can flash a rom whenever you want, as long as you wipe all data from previous rom or mod first,so i would repartition to this
96-128mb=swap
512mb=ext
than flash the ohsaka superwipev2, power off device than reboot back to recovery.
flash the rom you want and enjoy!!
re-partitioning/re-formatting does not have to be done everytime.. it's just good to do every once in a while because you never know what could be happening in there... you or a developers rom could have done something somewhere that caused a bug in your sd partitions so its always good to wipe them at some point...
the ohsaka superwipe i do reccomend using everytime!! I also recommend wiping it manually sometimes... also another good known method is a fastboot wipe 'i forget the cmd for it' lol but do these every once in a while...

Did exactly as you said, unfortunately I still get the same problem: Cannot scan for networks.
I will stick to Gingeryoshi for the moment.
Thank you for your time and help.

wow, thats a bummer... i never had that issue with laszlo's rom at all... i wonder what could be wrong. sorry i couldn't help.. just out of curiosity what device do you have? is it a dream or magic?
possibly if you are using a magic, you may need a kernel with wlan.ko modules included for the specific kernel(would be icluded in kernel.zip file)... different kernels wont work with different drivers...

It is a Dream

[Q] - Simple route to GB bootloaders from ICS w/Froyo BL

The title pretty much says it all. I've been reading for days and my eyes are burning yet I still haven't found anything exactly like what I'm asking...and I don't want to keep asking stupid questions in the dev section.....
I was on a custom Froyo ROM for a long time and finally got around to trying out SlimICS 4.2 a couple of weeks ago. The instructions called for a CM9 flash first, then SlimICS. It all worked perfectly and I love the ROM.
I've never tried GB and am still on Froyo bootloaders. I would like to switch to GB bootloaders, maybe for no good reason at all. I figure in the long run it will be a good idea. (different rom, kernel, JB, whatever)
I was told that trying to use Odin to simply flash GB bootloaders over an ICS rom and kernel might be a bad idea. I'm hoping someone has successfully done this but most of my reading has got me feeling a bit cautious about bootloaders...
I'm looking for a simple, logical sequence to get me back exactly where I am (ICS) but with GB bootloaders. Perhaps back to a custom Froyo rom/kernel then flash GB bootloaders then back to ICS? I'm guessing that cwm will be able to restore the state of my current rom after all that. I'm so sick of setting up everything from scratch and Titanium can only do so much....
Thanks

Here ya go...
U cannot flash the GB Bootloaders while you are running a Rom that has the mtd/yaffs or yaffs2 partition, that is, a CM, MIUI, ICS, JellyBean and such like. U will need to be on a bml/rfs partition, that is, a Stock Rom or at least a Dev Rom based from a stock firmware.
Do an Nandroid Backup on what you are running currently.
Backup everything you do want to save...apps, contacts, messages, emails, pics, efs folder, etc.
Then you will need to flash back to Stock GB Firmware with Bootloaders included. The i897ucKK4 is the latest official. Here is Stock I897UCKK4 Android 2.3.5 One Clicks. Use the Odin or Heimdall version that includes the GB Bootloaders. If you have a newer Captivate that does not like using the One Clicks, then see this thread for the .tar package of the i897ucKK4... [ROM] I897UCKK4 [17.11.2011][Android 2.3.5]. With this you will probably have to wipedata/factory reset first. Then use regular Odinv3 1.83 or similar to flash it. **Note: Flashing Bootloaders is risky. So be sure you have a trust worthy micro usb/usb cable, constant power source, etc. You don't want to loose power or connection during the few seconds that the bootloaders are being flashed. Bad bootloader flash = hard brick.
Once you are successfully back on Stock KK4, then go to this thread... [KERNEL][KK4][1/28/11] Corn Kernel and use the regular Odin to flash the .tar 7.0A version of this kernel. This will give you the CWM Recovery that you need.
Then reboot into CWM and reinstall the ICS Rom you were on before per that Rom's install instructions.
Once you are booted up on that ICS Rom, reboot into the Recovery of that Rom and then you can Restore your backup that you did at the beginning of this process.
You should be good now.
For issues along the way with connections to the pc, download mode, etc. please see this thread... Captivate Connection Issues and Download Mode Help

The most direct route would be to flash a Gingerbread-based Stock rom with bootloaders from your current setup. This will put you back at stock (including your partitioning), so you'll have to flash as if you're going to CM-based roms for the first time when you go back to ICS/JB.
Obviously, there's all the normal cautions of backing up, bootloader dangers, etc.

@ jmtheiss... I Ninja'd ya by a few minutes. Lol
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

They both said it better than I could have but what it comes down to is there is no "simple" way to go about what you are wanting to do...
Sent from my SGH-I897 using xda app-developers app

I don't think a lousy "thanks" even begins to cover it. I really appreciate when someone puts that much effort into helping somebody out. Cheers!
And that definitely qualifies as "simple" enough...better than something requiring rooting again and getting a functional recovery, etc. A couple of Odin sessions and a couple of cwm flashes are fine.
Thanks again guys.

bcflyfisher said:
I was told that trying to use Odin to simply flash GB bootloaders over an ICS rom and kernel might be a bad idea. I'm hoping someone has successfully done this but most of my reading has got me feeling a bit cautious about bootloaders...
Thanks
Click to expand...
Click to collapse
I have done it successfully a couple of times without any issues. I have only done it when absolutely necessary since they do say there's some risk there.
What I don't understand is how you *could* run ICS without GB bootloaders? I didn't think that was possible.

I'm living proof. I was hesitant but their instructions said if coming from Froyo flash CM9 first then SlimICS. I flipped a coin and it worked fine. The developer of Slim (krarvind) knows I'm on Froyo bootloaders and didn't seem too phased by it. Whether or not I'd be able to jump to JB with whatever kernel is unknown so I'm going to backtrack a little and do what I probably should have in the first place.

Here's an update of what I did just in case it's helpful to someone else down the road.......
I did my best to follow the suggestions given by 4-2ndtwin in the 2nd post. I generally have pretty good backups of everything done but I did new ones just for kicks. Nandroid, Titanium Backup, efs, SMS, call log, APN, and a few other things. I downloaded all the necessary files, and laid them all out sequentially on my screen so I wouldn't get distracted and screw up. In the end I'm pretty much exactly where I wanted to be but of course there were a few unexpected issues.
- The Heimdall One-Click of stock GB with bootloaders was very easy. I had Samsung drivers on the computer already but Heimdall insisted on installing new ones. After that it did its thing and I was on official KK4 with GB bootloaders.
- Next up was regular Odin flash of the Corn Kernel. When I connected the phone in download mode Odin didn't give me a yellow light. If I connected the phone while it was NOT in download mode Odin recognized it. I wasted at least an hour to discover that it was just a driver issue. The drivers that Heimdall wanted weren't "good enough" for Odin. Interestingly, neither was the original package I had on the computer. The one that worked was called "Samsung_USB_Driver_for_Mobile_Phones.zip" from the Samsung website. After installing that Odin saw my phone in download mode and I was able to install the Corn Kernel. Rebooting into recovery gave an option to root the phone.
- At this point everyone in the world decided they needed something from me so between work and phone calls/texts I ended up using the phone on GB for a while.
- My boot screens had been a total mess since my first custom rom so I decided to do the boot screen fix next - http://forum.xda-developers.com/showthread.php?t=1065743 - TRusselo added a bunch of good info to the thread and there's a good post on page 10 from irishvandal that explains the whole sequence of boot screens and what you can and cannot change.
- So the next step should have been to flash CM9 on my way back to SlimICS just like I did a month ago. I figured since I had been using the phone for a couple of hours I should wipe everything ... so I did the cache, data, format system, dalvik cache, and then I went to flash CM9 and noticed that for some reason I didn't have the zip file on the phone any more. I must have deleted it myself because nothing else spontaneously disappeared. When I rebooted normally to plug the phone in and transfer files I discovered that in wiping/formatting I messed something up and I kept getting stuck on the Corn Kernel boot screen. I could get into recovery or download mode just fine, just no normal boot. I was able to mount storage in recovery but when I tried to copy over the CM9 zip it kept hanging. After numerous attempts I decided to just go right back to the beginning.....
- Heimdall once again wanted its own drivers. No problem, I did that, then uninstalled them and reinstalled the drivers Odin likes, then got Corn again, did the boot screen fix again just to try a different image, then downloaded a new CM9 Nightly and copied it to the SD, flashed it with no issues, then flashed SlimICS (which actually has 2 zips plus addon packages) and I was back to ICS with GB bootloaders. It's amazing how fast things can be done when there are no more surprises!
- When the phone was rebooting into Slim ICS I got a message I don't remember seeing before - "Android is upgrading" or something similar. Weird. The next time I booted to recovery to try to restore the nandroid backup I ended up in CWMR Touch v5.5.0.4, which is weird looking and makes me feel strange. When I tried to do a full restore it encountered a few issues such as not being able to restore data normally. I don't recall the details but when I reinstalled Titanium Backup it would just FC so I couldn't restore any of my other apps. The "solution" was to reflash the Slim zips and do a restore of the system only. This set up all the tedious stuff for me. I got TiBu again and restored apps+data and that worked. Chose my launcher and it was back almost the way I wanted it. Interestingly, I had to replace the widgets but the shortcuts were all there in the right places.
- Voice search force closed. Slim doesn't include it in the base rom but it's available as an add-on and I had the zip on the sd from last time but flashing it didn't fix the problem (it had worked the first time I installed Slim). Some random sequence of freezing the Voice Search app, wiping its data, reflashing the Voice zip, unfreezing the app and it worked. In the process I noticed that in TiBu it was originally listed as Voice Search 2.x.x but then it was suddenly 3.x.x with a different icon. Then an hour later after all kinds of restoring (SMS, call log, etc) voice was force closing again. It was also listed as 2.x.x. This time it took me twice as long to randomly do things until it started working again (and at the same time it turned back into 3.x.x. It's been fine since...
So again a huge thanks for the advice! I got to spend the better part of a day fighting my way through minor issues but I learned a lot about my phone and got over my aversion to Odin for the last time. Hopefully someone else can benefit from something I've gone through. If nothing else, I feel a renewed sense of accomplishment.

^
If all ur ics and jb roms have run well...then i see no need to flash the bootloaders.
Sent from my SAMSUNG-SGH-I897 using xda premium