Database Develop

Stuck on G1 startup screen after installing theme.

I posted about this in another thread, and thought I'd start a new one. I couldn't figure out how to delete my first post about it, sorry, guys.
Anyway, I tried to install a theme, and now I'm stuck on the G1 boot screen (the first one). It just hangs there, doing nothing. I Tried to go over it with the JF 1.3 update.zip in recovery, but it didn't work, the phone just hangs. Does anyone have any ideas? I'm traveling for the next few months, and I'm seriously screwed without a phone.
Thanks!

If you can't boot and can't get into recovery your only recourse is to flash the NBH file from the bootloader and start from scratch. Also, you really probably should not be performing modifications and hacks on your main phone without some kind of a backup. GL

jashsu said:
If you can't boot and can't get into recovery your only recourse is to flash the NBH file from the bootloader and start from scratch. Also, you really probably should not be performing modifications and hacks on your main phone without some kind of a backup. GL
Click to expand...
Click to collapse
I can get into recovery- that's how I managed to try to reapply the JFV1.3 update.
I probably should have been more clear about that.

Did you try a wipe in recovery? Alt+W

jashsu said:
Did you try a wipe in recovery? Alt+W
Click to expand...
Click to collapse
Yeah. No dice.
Perhaps the update didn't work because there was already an update.zip (the theme I tried to install) on my sdcard? When in recovery, what exactly do I type from adb to copy an update.zip from my sdk/tools directory to the sdcard? Do I need to have deleted the update.zip that was already on the card beforehand? I can't find a way of deleting anything from recovery.
Here's what I typed:
adp push update.zip /sdcard
I also tried:
adb push update.zip /sdcard/update.zip
I tried alt + s after both, and it went through the updating process, but I have no way of knowing if it tried to update using what I'd just pushed onto the sd card, or the old update that screwed up my phone. Did I at least put the update on the sdcard correctly?
Hope I'm making sense.

It sounds like you are applying the theme again. You need to try to delete that file from your sd card. The easiest way would be to get a card reader and delete what is on your card then put the new update.zip on it. If you can't get a card reader then you will have to find the linux commands to delete a file and use adb shell to execute the command. Good luck, you should be able to get your phone back.

zackmpls said:
I posted about this in another thread, and thought I'd start a new one. I couldn't figure out how to delete my first post about it, sorry, guys.
Anyway, I tried to install a theme, and now I'm stuck on the G1 boot screen (the first one). It just hangs there, doing nothing. I Tried to go over it with the JF 1.3 update.zip in recovery, but it didn't work, the phone just hangs. Does anyone have any ideas? I'm traveling for the next few months, and I'm seriously screwed without a phone.
Thanks!
Click to expand...
Click to collapse
same thing happened to me had to use JF rom to get it to work again. idk the linux command but i got an idea! if you dont have a card reader or another g1... you can try installing cupcake thru eng bootloader then convert back to JF's rom. Try that maybe it will work.

rm filepath/filename.extension
should be liek this
rm /sdcard/update.zip

If you are stuck in a loop, it's most likely due to using an ADP1 theme on an RC30 version of JesusFreke's release.
If that doesn't fix it, you will need to remove your apps manually through ADP, but let's take it one step at a time. Download and install JF's standard RC30.

trmacdonal said:
It sounds like you are applying the theme again. You need to try to delete that file from your sd card. The easiest way would be to get a card reader and delete what is on your card then put the new update.zip on it. If you can't get a card reader then you will have to find the linux commands to delete a file and use adb shell to execute the command. Good luck, you should be able to get your phone back.
Click to expand...
Click to collapse
That's what I was thinking, too. I managed to get to a reader this morning, and I was able to put rc30 on there, no problem. I'm up and running again!
I'm wondering why ADB didn't work to push the update to my card in recovery. Did I input the wrong commands? It acted as if it worked (took a couple minutes, showed the "28374 bytes blah blah" message".
Thanks a lot, everyone. I'm so relieved to have my phone again, and I've learned my lesson about modifying without backing up first.

i have the same problem what can i do !! ?
--------------------------------------------------------------------------------
i have downloaded and install themes on G1 !!
i have downloaded the file (Theme) and copy to my card and switched off my phone and then i have pressed home+on button then i have apply update from sd card !! it installed successfully but now i have started g1 after that g1 logo i can only see a blank screen !!
I am using CyanogenMod 4.1.999 !!! i have downloaded Theme from this page http://forum.xda-developers.com/show...talling+themes
Steampunk !!! ( as i said i have downloaded this file and rename it to update.zip and copy to my sd card then i have just applyd from my sd card since then when i start my phone i see T-Mobile G1 logo then all disappear and i can only see a light without anything !!!

Kuulthag said:
i have the same problem what can i do !! ?
--------------------------------------------------------------------------------
i have downloaded and install themes on G1 !!
i have downloaded the file (Theme) and copy to my card and switched off my phone and then i have pressed home+on button then i have apply update from sd card !! it installed successfully but now i have started g1 after that g1 logo i can only see a blank screen !!
I am using CyanogenMod 4.1.999 !!! i have downloaded Theme from this page http://forum.xda-developers.com/show...talling+themes
Steampunk !!! ( as i said i have downloaded this file and rename it to update.zip and copy to my sd card then i have just applyd from my sd card since then when i start my phone i see T-Mobile G1 logo then all disappear and i can only see a light without anything !!!
Click to expand...
Click to collapse
To fix your problem just reflash your ROM. It's always a good idea to keep it on your card even after flashing.
Only install themes that support the ROM you're on...

i tried installing a theme on cm's v.4.999, and also got stuck on the bootscreen, however i just rewiped my phone and stalled the rom again. am currently running kingklick hero 2.0

zackmpls said:
Yeah. No dice.
Perhaps the update didn't work because there was already an update.zip (the theme I tried to install) on my sdcard? When in recovery, what exactly do I type from adb to copy an update.zip from my sdk/tools directory to the sdcard? Do I need to have deleted the update.zip that was already on the card beforehand? I can't find a way of deleting anything from recovery.
Here's what I typed:
adp push update.zip /sdcard
I also tried:
adb push update.zip /sdcard/update.zip
I tried alt + s after both, and it went through the updating process, but I have no way of knowing if it tried to update using what I'd just pushed onto the sd card, or the old update that screwed up my phone. Did I at least put the update on the sdcard correctly?
Hope I'm making sense.
Click to expand...
Click to collapse
You simply need to rename the one you DON'T want to use- or if in recovery, choose "select zip", not "update zip" from the list of options. Did you do a Nandroid backup before flashing? if so, you can do a restore from that working backup. And again, to re-iterate what another responder said, make sure you do a wipe before flashing again.- anytime I have experienced your problem ( and I have more than once) I have done a wipe from recovery than chosen a known good rom from my card after that to get up and running. I always keep a "rock solid" rom on my card for this reason, such as xRom 1.5r4. - chris aka [email protected]
Also- I am a bit confused; are you doing this from the phone while at the recovery screen, or with adb from your pc. You can also take out your sd card, put it into a card reader, and do your re-naming, loading of a rom, etc., then put the card back into your phone-cc

AMAZONMP3!?!?

I Now have the jf1.5 and for some reason It doesn't come with the amazonmp3 app. I need this, can some please post it so I can download the apk

mimic1011 said:
I Now have the jf1.5 and for some reason It doesn't come with the amazonmp3 app.
Click to expand...
Click to collapse
ADP builds of Android do not have TMobile apps such as Amazon MP3. This has been discussed ad nauseum if you had bothered to search.
mimic1011 said:
I need this, can some please post it so I can download the apk
Click to expand...
Click to collapse
It's a protected app. If you need it that bad that I suggest you go back to an RC build and do research before blindly flashing whatever build of Android is at the top of the forum.

mimic1011 said:
I Now have the jf1.5 and for some reason It doesn't come with the amazonmp3 app. I need this, can some please post it so I can download the apk
Click to expand...
Click to collapse
If you still have the RC firmware you can just unzip it copy the amazon apk out and install it into the adp the amazon works. I dont think anyone has the IM app working though

We should have an official rc update from tmobile real soon, which will have amazon mp3, myfavs, etc...

Just open a RC33 update.zip and extract the file from /system/app. Then you can install it by adb push.

Verified as working. I just added it to the app folder of Dudes 1.1 build and then did the update and it works just great. Purchased and downloaded a song to verify.

Here it Is
http://droiddeveloper.com/com.amazon.mp3.zip
enjoy it works for me...

Really Bad,
In Germany it cannot charge my creditcard... It has enough money on it.

I have the dude's 1.5 version, and cant seem to get it running. It forces closed upon trying to open. Any thought? It is saved to my SD in the app folder.
TIA

Read my guide
http://forum.xda-developers.com/showthread.php?p=3763025

TY SolemnWishing, this is how I got the app on my SD card to begin with - yours is a very helpful thread for a n00b like me. Unfortunately, I was never able to get the app to open. I am not sure how I could have messed it up - pretty simple, I navigate to the app folder on my SD and click the apk file which proceeds to install Amazon MP3. No go.
If you have any ideas on what the problem might be I would appreciate the input.
Thanks again for your great tutorial

Hmm... I assume you deleted the .zip and renamed it to .apk, what firmware are you using?

I am using firmware 1.5. Yes I renamed to apk. I wants to work, just force closes before it fully loads. I also have this problem with oi music player. It used to work, now no longer loads. I wonder if my SD card is the problem. It is 8 gb, but I am sure only like a class 2 card.

Strange. I have JF 1.5 and installed the Amazon app the normal way for any app on the G1 and have rebooted several times. The app still works. I thought if you did not push the app to the G1 it would need to be reinstalled each time you reboot the device?

Well, I am pretty positive it was my SD card - after writing my post this morning I pulled the SD card and have not been anble to get the phone back since. This thread pretty accuratly describes what is going on...long story short, i think I fried my SD card and as a result am stuck on Splash 2. I have wiped several times...
http://forum.xda-developers.com/showthread.php?t=516874
uggg...all for mp3's!!!! any thoughts and lots of luck would be appreciated.
K

Ahh I did the same thing. Here is what you need to do, you will need to force format it. Windows will NOT detect the card, and it may even freeze your computer. Put the phone into another device, such as a palm pilot or another cell phone and format it from there. It shouldn't take very long, and when it is completed, it will likely say the memory card only has 5Kb or so of memory on it. NOW insert the card into your computer and reformat it into a FAT32 format (+Ex2 for apps to SD) and you should be good! Of course, you will need to reload all your files though. That will fix your SD card. As for your phone... you will need to completely reflash a new firmware onto it, as right now starting up your phone is looking for items on your SD card which it may need, which no longer exist.
edit: if that doesn't work, completely start from the beginning by flashing the dreamimg.nbh file for rooting.

I was able to reformat the SD card, lost all my backups of course, and had to reflash dreaming.nbh and start from scratch. No biggy, at least i still have my phone.
thanks for all the tips...once i get my card re-partioned, I will try the Amazon.apk again.
K

I got it to load - thanks for all your help.
K

No problem at all, glad I could help.

[tut] flash rom without pc (sd card method)

0. Make sure phone is hard-spl first
1. Make sure SD card is formatted with fat-32
2. rename the image file (ruu_signed.nbh) to rhodimg.nbh, then copy that to the ROOT OF THE MICRO SD CARD, Insert card into phone
3. Set your phone in bootloader (Hold the "volume down" and hold the power on button until you see the tri-color screen.
4. Then follow the on-screen instruction
5. (OPTIONAL) -after flash, make sure to hardreset (pull battery, insert battery then hold green and red PHONE buttons (send/end) and hold powerbutton) follow onscreen instruction.

thanks for the info

I've tried the above and somehow it won't work on my TP2, it stays at "Serial" text in the white box, I'm assuming it already went past the SD slot then? Checking for the image.
I have the Energy rom loaded on the SD card, named as explained in the first post in this topic, it is placed in the root of the SD card, no folders or other files exist on that card. I removed the SIM card from the phone just to be sure. Is there anything I am missing, or is there anyone else who actually used this method to flash his or her device?
Info:
SPL: OliNex 0.85
ROM: |RHOD|6.5|ROM|WWE| ★ EnergyROM "Warhawk" (23016) ★ | Built Aug 21 |Manila 2.5 / 2.1|
SD Card: 4GB MicroSDHC (No brand on card, supplied with the branded T-Mo TP2 (Vario V)
Formatted: fat-32
Thanks

The nbh file needs to be in capital letters! RHODIMG.nbh
And step 5 isnt to be done until the "Tap screen to set up device" screen!
Just reset when your phone says Update successful!

And done, name changed to the correct format. No luck. Reformatting the card now to see if that changes anything. Update in a few.
And that too didn't work sadly. Either someone here notices I'm doing something wrong, or I'll just wait till I get near a machine natively running Windows Running Mac OS here so can't run the executable, and read that it's not quite a good idea to flash it from a virtual OS.

PositiveCreep said:
And done, name changed to the correct format. No luck. Reformatting the card now to see if that changes anything. Update in a few.
And that too didn't work sadly. Either someone here notices I'm doing something wrong, or I'll just wait till I get near a machine natively running Windows Running Mac OS here so can't run the executable, and read that it's not quite a good idea to flash it from a virtual OS.
Click to expand...
Click to collapse
You will want to partition your card so the nbh image is in a partion of at the largest 1G, anything larger makes it hard for the phone to find and read the nbh file! I have a 1G card just for flashing and it works perfect! And it also may be the mac, they never play nice with windows!

It's not the mac screwing it up in this case as I am using a virtual Windows OS to work on the card. (MacOS leaves some folders on the card that I don't want on it)
Will try partitioning the card, cheers. I'll update when I know more. ANd thanks for the help ^_^
Update:
Partioned the MicroSD card to 0.5GB, no change sadly.

thanks for information

Ok, SD update worked now, however, step 5 won't go (Oh crap...) Have the grey screen with "Update Complete" and "UPDATE SUCCESS" However, it won't do anything if I hold down Send/End/Power at the same time for over 10 seconds. How long should that take normally? What's my best option right now? Can't see any other than to unplug the phone and take out the battary, however, will this brick it?

PositiveCreep said:
Ok, SD update worked now, however, step 5 won't go (Oh crap...) Have the grey screen with "Update Complete" and "UPDATE SUCCESS" However, it won't do anything if I hold down Send/End/Power at the same time for over 10 seconds. How long should that take normally? What's my best option right now? Can't see any other than to unplug the phone and take out the battary, however, will this brick it?
Click to expand...
Click to collapse
When is says "UPDATE SUCCESS", just rest with the stylus.
Dave

Thanks for the swift reply! Done it, it's booting up as I am typing this. Didn't quite have the guts to just do that without having read I could when flashing from SD. (Was unsure how the device would react to soft reset then a first booth with the SD present etc)
Anyways, rambling. Thanks!

these post are telling me how to flash while the rom is already on the phone, but i'm missing the step on how to get the rom file on the phone in order to move it to the sd card.......... how do i get the file to the phone? do i put it onto the phone from the computer or do i go to my browser on my phone and download it from there to the phone

htctpII said:
these post are telling me how to flash while the rom is already on the phone, but i'm missing the step on how to get the rom file on the phone in order to move it to the sd card.......... how do i get the file to the phone? do i put it onto the phone from the computer or do i go to my browser on my phone and download it from there to the phone
Click to expand...
Click to collapse
Everything you need to know is HERE. I really suggest you fully read the instructions so you avoid bricking your phone by mistake.

In re: making sure you're hardspl'd first, does that still apply if you're flashing an official ROM? Or just for user cooked ROMs?
I'm about to update my Verizon TP2 with the newly released official 6.5 from verizon. I'm not hard spl'd, and honestly, know very little about that particular modification.

not for official
I dont think you have to be hard SPL'd for an official ROM. I think everything is included in the ROM package. (at least for T-Mobile it is)
btw the .nbh does not have to be named in all capitals. I have personally done it both ways with no problems at all. RHODIMG.nbh works just as well as rhodimg.nbh

kwambewright said:
I dont think you have to be hard SPL'd for an official ROM. I think everything is included in the ROM package. (at least for T-Mobile it is)
Click to expand...
Click to collapse
Thanks for the quick response!
Sadly, the way the install file is set up to work, I can't get to the nbh file. It insists on installing that via an active sync connection. I was hoping it would extract from the exe and schedule it for active sync installation, then I could hunt down the ROM, copy it to my SD card, and run it from there.

fortunz said:
Thanks for the quick response!
Sadly, the way the install file is set up to work, I can't get to the nbh file. It insists on installing that via an active sync connection. I was hoping it would extract from the exe and schedule it for active sync installation, then I could hunt down the ROM, copy it to my SD card, and run it from there.
Click to expand...
Click to collapse
hmm.. sorry for kicking this post, but you can unpack the exe-file with winrar. just grab the biggest file you can find (RUU_signed.nbh, and rename it to rhodimg.nbh), copy it to your root-folder (fast way for accessing bootloader is to also copy the "EnterBootLoader.exe" -file to your SD-card, and to start that file after copying both the files). Now just enter the bootloader, and it works! (don't be scared when the screen goes black for a moment, and the bootloader has reloaded. It's meant to do that )
I still have a little question by the way: is it possible to flash the hardSPL this way? or should i rename it to something else?

No, Hard SPL needs to be done from the PC as it checks IMEI online and IP address. You only get 1 licence, can ask for more or purchase more licences, but it can't be done any other way...

ultramag69 said:
No, Hard SPL needs to be done from the PC as it checks IMEI online and IP address. You only get 1 licence, can ask for more or purchase more licences, but it can't be done any other way...
Click to expand...
Click to collapse
Yeah, it's a pity this has been done (though I understand why...)
My device cannot connect to PC anymore, so cannot use HSPL anymore!

InjecTioN said:
hmm.. sorry for kicking this post, but you can unpack the exe-file with winrar. just grab the biggest file you can find (RUU_signed.nbh, and rename it to rhodimg.nbh), copy it to your root-folder (fast way for accessing bootloader is to also copy the "EnterBootLoader.exe" -file to your SD-card, and to start that file after copying both the files). Now just enter the bootloader, and it works! (don't be scared when the screen goes black for a moment, and the bootloader has reloaded. It's meant to do that )
Click to expand...
Click to collapse
Much obliged. I've actually been scared off the official vzw 6.5 because of issues upgraders have reported, but someday I'll put that to use.

Easiest Step-By-Step Android Tutorial for the Vogue (NAND Method/Internal Memory)

I have created this post because I was honestly baffled by the NAND install threads for the Vogue that I found, that claimed to be "straightforward" and simple, but the people who wrote them leave a lot of gaps that you have to figure out. Perhaps they have been doing it for so long now, that they just 'assume' you will know stuff, so here are step-by-step instructions for someone who has zero experience with Android, and all they know is that they have a Window mobile phone.
So, Here is the NAND install process (will install Android to your internal memory, which is much better than running from the SD card) for the HTC Vogue (240x320), CDMA or GSM. I believe this is the most straightforward tutorial on this entire site, and all files you need are provided in this post; no file-hunting necessary like with other tutorials. Keep in mind, this process will wipe your internal memory and replace it with Android, so you should backup any personal files you have stored on the phone. If you have a CDMA phone (Verizon, Sprint, etc.) then you should make sure to backup your Contacts using a 3rd party program. GSM phones however (ATT, T-Mobile, etc.), typically store their contacts to a SIM card, which is not altered by this process. You do not need to backup your SD card, since it is also not altered when installing Android.
Dependencies: This process works for any ROM release that provides an "androidinstall.tar" file in their download package.
First and foremost, make sure you have unlocked your phone ("2.31 CoKe" HardSPL for CDMA Vogues). If you have ever flashed a custom Windows ROM from this site or ppcgeeks.com, to your device, then you most likely already have an unlocked phone. If not, perform the steps HERE first, before continuing AND flash to a custom Windows Mobile ROM (non-stock) and make sure your phone is provisioned (you can get and receive calls), and that you can use data (if you have a data plan).
1. Wipe your SD card, and make sure it is formatted FAT32
2. Create a new folder in the root of the SD card called "andboot"
3. Download the ROM release package of your choice (for example, you can download the 240x320 version of Myn’s Warm Donut - [RLS 5 - 04/24/2010] HERE)
4. Extract files from STEP 3 and put ONLY the "androidinstall.tar" file in the andboot folder on the SD card, by itself (no other files are needed)
5. You are DONE putting files on your SD card. At this point, put the SD card into your phone.
6. Download the latest NBH file that begins with "voguimg-240x320-..." (needed for all Vogue Android ROMs): HERE
7. Download the RUU Update Utility (needed for all Vogue Android ROMs): HERE
8. Rename the NBH file to from STEP 6 to "RUU_signed.nbh" and place it inside the folder with all the other files from STEP 7
9. Now, put your Vogue in bootloader mode: Hold down power, camera, and the small reset hole (with your stylus), until you see the tri-color screen, and it says "Serial" at the bottom
10. Plug your phone into your computer, and the "Serial" text should change the "USB"
11. Now, run the "ROMUpdateUtility.exe" from STEP 7, and click the "Next" or "OK" buttons to go through the flash/ROM update process, until your phone shows a progress bar on its screen and is updating.
12. As soon as that progress bar finishes the phone will automatically reboot; at this point unplug the phone from the computer
13. Now, watch carefully during the Linux boot process...there will be a quick message that says "Hold down Volume Up or D Pad". Just press and hold the center D-Pad button until you see the screen change to the installer menu. If you happen to miss it, and it continues loading, then just use your stylus to press the reset button (it will not hurt the phone or any files to try again as many times as you need to.)
14. You will now see a black and white menu. Select option 1, to "Install..."
15. Select "Yes" on the recommended prompt that follows
16. Once it says the Install process is complete and it returns you to the menu, just reboot your phone with the reset button
17. At this point just WAIT. Do NOT press the volume up button again, and do not do anything until you see the Android desktop. You may get an error saying that it could not find a file or something like that, but just ignore it...do not get impatient! Pretty soon the Android progress bar will show on the screen (might take up to 5 minutes), then the Android desktop will load.
DONE. Enjoy Android on your Vogue! You can now delete all the files on the SD card if you wish...Android will recreate anything it needs on boot-up each time.
MASS STORAGE FIX (USB to PC): You can get the Mass Storage fix HERE so that your storage card will show up as a drive on your computer. This is a widget, and not ROM specific, so should work for any Android ROM.
KAISER WI-FI FIX (for the Kaiser phone ONLY!): Download the Wi-Fi fix HERE (intended for use with 'myn's Warm Eclair RLS1', linked in STEP 3)
I do not ask for donations, just say 'Thanks' if this helped you.
***
UPDATE: This Thread is now featured on Wired.com's News Site!! Link: http://www.wired.com/gadgetlab/2010/04/windows-mobile-android/
***

please elaborate on step 8. what are we extracting here

Great post. Just some clarifications I thought would be helpful.
1. reminder to all - you can use SDHC cards for this, those being greater than 2gb, but make sure you format them to FAT32.
5. in some instances there are androidupdate.tar files that go with the build too, in which case that too needs to be placed in the same andboot folder
8. clarification, you'll be replacing the RUU_signed.nbh file with the 320 nbh file you download. So, you'll have to delete the ruu_signed.nbh that came with the update utility, and rename your downloaded 320 nbh to ruu_signed.nbh and place it in the update utility folder so it uses that file instead.
9. to enter bootloader mode you have to press those 3 buttons down for about 2 seconds, not just a quick tap. This bootloader is your failsafe fallback to reinstall if your operating system goes funky.
13. If volume up isn't working for you, try holding down the button in the middle of the directional pad. The last nbh file I used required this instead of the awkward volume-up. Regardless, be sure to do this quickly as soon as the phone reboots itself.
16. After the install process is complete you'll be brought back to the same menu you arrived at by holding down the button on startup, you may then select "update" or "upgrade" from that same menu to activate the androidupdate.tar file you may have copied to your andboot folder. Once done, just select "exit" or reset.
17. He's not kidding, first boot can take a very long time.
If you run into problems and just need a functional phone for a bit, download the nfsfan rom (or any other custom roms), put phone into bootloader and run the nfsfan rom utility from your windows desktop. Don't reinstall a locked carrier-specific rom that you might have used to update your radios otherwise I understand your Coke bootloader gets wiped out and you'll have to do that again. Alternatively, there is an older, dummy-proof Android ION build that will install the entire ION build through the rom update utility to your nand at http://sourceforge.net/projects/androidhtc/files/2009-12-17/androidinstall.zip/download
I'm no super-expert so if I have any misinformation in my post, or there are other shortcuts, please feel free to edit it or let me know and i'll modify it.

MikeMurphy said:
Great post. Just some clarifications.
8. clarification, you'll be replacing the RUU_signed.nbh file with the 320 nbh file you download. So, you'll have to delete the ruu_signed.nbh that came with the update utility, and rename your downloaded 320 nbh to ruu_signed.nbh and place it in the update utility folder so it uses that file instead.
Click to expand...
Click to collapse
where is this file?

CasopoliS said:
where is this file?
Click to expand...
Click to collapse
You're looking for the vogue 320 files, not the vogue eclair 320 files unless you're installing an eclair (2.x) build.
The .nbh files are usually referenced on the build thread in the forums, but if they are not head over to http://sourceforge.net/projects/androidhtc/files/ and download the latest.
(NOTE: I suggest you run at least the Feb 23 build at http://it029000.massey.ac.nz/vogue/files/?C=M;O=D as it enables the openGL support)

MikeMurphy said:
You're looking for the vogue 320 files, not the vogue eclair 320 files unless you're installing an eclair (2.x) build.
The .nbh files are usually referenced on the build thread in the forums, but if they are not head over to http://sourceforge.net/projects/androidhtc/files/ and download the latest.
Click to expand...
Click to collapse
the latest isnt there its here
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D

now now, gents, you're both right - dzo's latest are in one spot, vilord's latest are in the other, and they don't always contain everything the other does. vilord mentioned trying to get them in one spot but I don't know if there's been any progress on that.

it keeps hanging up at the progress bar and both stay at 0% it looks like the active sync is gone once in bootloader it goes gray and then its gone from tray in bottom right corner. it seems like once in bootloader mode i have no active sync connection it just hangs Then the updater goes into its recovery any help please

razorr69 said:
it keeps hanging up at the progress bar and both stay at 0% it looks like the active sync is gone once in bootloader it goes gray and then its gone from tray in bottom right corner. it seems like once in bootloader mode i have no active sync connection it just hangs Then the updater goes into its recovery any help please
Click to expand...
Click to collapse
go into bootloader before plugging your phone in by pressing and holding power button, camera button, and then use stylus to hit reset button.
once you get into bootloader, plug your phone in and then run the rom update

incubus26jc said:
go into bootloader before plugging your phone in by pressing and holding power button, camera button, and then use stylus to hit reset button.
once you get into bootloader, plug your phone in and then run the rom update
Click to expand...
Click to collapse
that is the way that i have been doing it as per the instructions, Any other suggestions? I just did a hard reset and restored the phone to out of the box if that helps out any.
thanks

razorr69 said:
that is the way that i have been doing it as per the instructions, Any other suggestions?
thanks
Click to expand...
Click to collapse
the only reason i said that is because active sync should have nothing to do with it. i dont think active sync should come up or shut down during this process. Do you have the RUU_signed.nbh named properly?

razorr69 said:
that is the way that i have been doing it as per the instructions, Any other suggestions?
thanks
Click to expand...
Click to collapse
Activesync has nothing to do with updates via the rainbow screen bootloader and will not sync.
You have already install the Coke bootloader? What OS are you running?

Thank you so much. Been needing something like this since the other NAND tutorials for Android didn't tell you what files to use or had outdated/non-working links.

MikeMurphy said:
Activesync has nothing to do with updates via the rainbow screen bootloader and will not sync.
You have already install the Coke bootloader? What OS are you running?
Click to expand...
Click to collapse
6.1. I followed the inst.
put the tar in andboot folder on sd
renamed the voug img file put it in the androidinstall folder on my desktop
put the rest of the files from myns donut into the androidinstall folder
then bootloader plug in usb then rom updater
everything goes fine intil it hangs on the progress bar at 0%

razorr69 said:
6.1. I followed the inst.
put the tar in andboot folder on sd
renamed the voug img file put it in the androidinstall folder on my desktop
put the rest of the files from myns donut into the androidinstall folder
then bootloader plug in usb then rom updater
everything goes fine intil it hangs on the progress bar at 0%
Click to expand...
Click to collapse
What OS are you running on your computer?
The ROM update utility really just installs the .nbh file which is somewhat of a front-end loader mechanism. Once that file is installed, then the phone resets, you hold down a button and you enter into the menu that lets you actually install android from the androidinstall.tar file in your andboot folder.
Here is a fail-proof method that I think will resolve your goofy androidinstall folder.
Download this
http://74.53.45.2/~evadmin/nfsfan/Public Releases/Vogue 6.5/ROMS/NFSFAN's WM6.5 1.00 FINAL ROM.rar
Then replace the .nbh file with the vogue 320 nbh. Then, run it when your phone is already in the bootloader screen.

Excellent post
I'm linking this from Warm Donut on the first post.

MikeMurphy said:
What OS are you running on your computer?
The ROM update utility really just installs the .nbh file which is somewhat of a front-end loader mechanism. Once that file is installed, then the phone resets, you hold down a button and you enter into the menu that lets you actually install android from the androidinstall.tar file in your andboot folder.
Here is a fail-proof method that I think will resolve your goofy androidinstall folder.
Download this
http://74.53.45.2/~evadmin/nfsfan/Public Releases/Vogue 6.5/ROMS/NFSFAN's WM6.5 1.00 FINAL ROM.rar
Then replace the .nbh file with the vogue 320 nbh. Then, run it when your phone is already in the bootloader screen.
Click to expand...
Click to collapse
Thank you will try it now. Running xp pro on my desktop

razorr69 said:
Thank you will try it now. Running xp pro on my desktop
Click to expand...
Click to collapse
XP Pro always worked well for me. I'm running Win7 x64 ultimate and recently my phone was recognized as a USB Sync Device in the bootloader mode which doesn't work for the rom update utility. This was occurring both with and without the installation of the MS Mobile Device Center app. To solve this I installed XP Mode and attached the usb device to the XP Mode and it recognized correctly as the Qualcomm MSM thing.
Just an FYI.

MikeMurphy said:
XP Pro always worked well for me. I'm running Win7 x64 ultimate and recently my phone was recognized as a USB Sync Device in the bootloader mode which doesn't work for the rom update utility. This was occurring both with and without the installation of the MS Mobile Device Center app. To solve this I installed XP Mode and attached the usb device to the XP Mode and it recognized correctly as the Qualcomm MSM thing.
Just an FYI.
Click to expand...
Click to collapse
when i go into my computer it just says mobile device

razorr69 said:
when i go into my computer it just says mobile device
Click to expand...
Click to collapse
same result error 262 update error. i dont get it this is so simple. 1 of the 4 steps is establish a connection with active sync dont know how to do that once im in bootloader mode it's like there is no connection but the phone shows the progress bar

[Q] Over clocking DIY thread...

I have searched a lot, spent time trying to figure everything out.
I have Hero that I am trying to make BA for my little bro. I have the evo now. Rooted and tethering. Not much else I need to mess with on it. Fast enough for me. But my old hero is now rooted and has the app to tether. I can't figure out how the heck to over clock it. It is slow and I want to kick it up a couple notches for him.
I have searched and all the codes that you guys use at the top throw the searches off, or maybe I am searching for the wrong thing.
Any links to other threads would be great. That way when someone else searches just over clocking like I did it will come to this thread and then link to the useful threads.
Thanks in advanced.

I see you are rooted already, is the phone running a stock rom? If so think about installing [ROM] cyanogenMod 6.1 stable (<<<<search). Then you flash a [Kernel] [GPL] DecaFuct [2.6.29.6] (<<<<search) and install a app called OverClock Widget, it is easier to use than the other one you can use called SetCPU. Thats pretty much it, somebody may chime in that can put a few links up but I am on my phone right now so I cant.

DecaFuct Max 768Mhz Kernel
DecaFyct Max 698Mhz Kernel
Decad3nce's Kernel OP Thread
These are JayBob's CM6.2 ROM Downloads.

Okay, so I need to back up my phone? Can I use the app on the android market MyBackup by Rerwarre, LLC? Then I need to download the files you linked me to in this thread? And then what?

Okay. I am sure you are all tired of hearing from me. But I am going to flash a ROM that has a over clock on it. I have a question tho. When I download the files. It unzips them. By that I mean I can open the folder and explore all of the files. Does this make it impossible to load that ROM? Thanks for your quick responses in advanced.

You dont want the file unzipped. Leave it zipped and put it on the root of SD card, that means just on the SD card, not in another file. Then reboot into recovery by powering phone off, then hold down the power button and the home button at the same time, keep them down until recovery comes on. If a white page comes up instead of recovery that says clear storage, pull battery and try again. Once in recovery you should see a few options. Nandroid, select this by clicking track ball while highlighted, this will back up your current system. After that choose install zip from SD card, then select the rom you loaded on SD card. After is says done, choose reboot system now. Then find Gapps 12-18-2010, I think those are the latest ones. Put them on root of SD like you did the rom and reboot into recovery the same way, choose the install zip from SD and select the Gapp file. Then reboot system amd you will set phone up with google like you did when it was new. You can then install one of the kernels linked for you, I recommend the 768 one, download OverClock Widget from the market and set it to 748, if your phone reboots for no reason lower that to 729, 710, wherever it becomes stable for you.

Okay, I did nandroid, I cleared everything, and I loaded the zip'd file ( I was trying to say earlier it is my mac's default action to un zip the file when it downloads. So I re compressed it. This might be attributing to my later problems) ANd then I rebooted. And it looks and behaves exactly the same as before.
Any pointers or ideas why it did this?

oefootball_70 said:
Okay, I did nandroid, I cleared everything, and I loaded the zip'd file ( I was trying to say earlier it is my mac's default action to un zip the file when it downloads. So I re compressed it. This might be attributing to my later problems) ANd then I rebooted. And it looks and behaves exactly the same as before.
Any pointers or ideas why it did this?
Click to expand...
Click to collapse
Since you re compressed it, it may need to be resigned before flashing. I could be wrong though

What does resigned mean?

ANybody have any idea why my ROMS arent loading at all?

Not quite sure if this will work on mac, you may need to find a XP pc to do this from. Here is a link to a zip signer though, http://forum.xda-developers.com/showthread.php?t=805766&highlight=zip+signer
Another thought...
Can you download the rom using the phone, then move file from download folder to root of SD card, using a file manager such as Astro or even better E Strongs File Explorer? I have read where some members have rooted, installed roms, kernels, theme, with no PC at all.

awesome idea on doing it from my phone. I didn't know it was a Mac problem. I can just run boot camp and boot up my mac with windows OS and try it on that. Thanks again.

Okay, i am trying to do it all from the phone. But the file is too large for the phones memory. And I can't figure out how to download righto the SD card. Any pointers here?

oefootball_70 said:
Okay, i am trying to do it all from the phone. But the file is too large for the phones memory. And I can't figure out how to download righto the SD card. Any pointers here?
Click to expand...
Click to collapse
That's weird it should. I have my applications checked to be installed to external memory but I don't know if that makes a difference or not. Mine go to sd

How would I click that option.

oefootball_70 said:
How would I click that option.
Click to expand...
Click to collapse
Ok what rom are you running again?
I just go to settings then cyanogenmod settings then application settings & it will let you choose

The factory ROM trying to get the first custom one loaded.

use the xda app and navigate to the thread that has the rom you want to install. from there click the link of the rom and it will go to SD card in a file called downloads. after completed plug phone into PC/mac and move that file/rom to root of SD card. Then reboot recovery and flash, done. There are literally 100+ threads on installing a rom, search, read, learn. What recovery do you have installed?

Okay downloading it to my Windows 7 bootcamp worked like a charm. I did the red dawn ROM. Isn't that one already over clocked?

oefootball_70 said:
Okay downloading it to my Windows 7 bootcamp worked like a charm. I did the red dawn ROM. Isn't that one already over clocked?
Click to expand...
Click to collapse
I believe it is, 710 maybe not to sure I have never ran it. There are faster smoother roms to run, why that one when we have Froyo for the Hero