Database Users

So... I think I just bricked a G1. You tell me.

Reading the "How to root" thread here. I've rooted a few G1's and a MT3G in the past.
Anyways. I downgraded to RC29, downloaded Amon's recovery and Hard SPL.
Did the whole Telnetd, downloaded telnet from market and mount remount, flash yadda yadda as per stated.
Rebooted and applied the Hard SPL.
After that finished I rebooted and it just hangs on the G1 screen, Home/Power does nothing. Camera/Power does nothing. Trackball/Power just lights the LED up blue.
Will it live the rest of it's life as a door stop?

not being able to boot into anything is a brick but there have been many threads about people who have somehow reversed their brick so just search this forum and see if anything happends who knows it could happen. otherwise its a really shiny paper weight

Bummer. I'll search around a bit more and see if there might be a thread I missed. I don't want to dig into it and do the whole jtag crap since there is still a warranty on the phone.
This is the "How-to" thread I followed and has worked on every G1 I have rooted til this phone which is a brand new one from Tmo.
http://forum.xda-developers.com/showthread.php?t=442480
Searching more I have read about people not flashing a radio before the SPL and caused a brick. If that is true why doesn't it state this as a necessary step?

Flashing the Radio before the SPL is needed for DangerSPL (although I seem to recall a thread debating that - http://forum.xda-developers.com/showthread.php?t=655097 ), I didnt think it was needed for HardSPL, it sounds like a brick unfortunatly, but I am no expert.
It is thought that its safer to flash the SPL and radio ect via fastboot (see link above) , not that it helps to much now, but that is an old guide, it should be updated though

Yep. From what I have gathered is if you can't get into recovery (home+power) or fastboot (camera+power) and it hangs on the G1 boot screen. It's a brick.

-RotorDemon- said:
Yep. From what I have gathered is if you can't get into recovery (home+power) or fastboot (camera+power) and it hangs on the G1 boot screen. It's a brick.
Click to expand...
Click to collapse
its not a brick unless it doesn't turn on at all (depending on how you define the word "brick")
exact same thing happened to one of the G1 replacements my friend got sent to him...we sent it back and they sent him a new one

Nah it's not bricked, the HSpl isn't compatible with your ROM, try flashing he ROM again, or faulty ROM this happens a lot.
Howto fix:
1. Backup any files on your SD card that are valuable to you (you can copy them to your PC's hard drive)
2. Format your SD card to FAT32 ( put your SD in your PC)
Windows: Right-click on SD icon and select format
3. Download the RC29 / RC7 dreaimg.nbh file (don't rename it or your phone won't recognize it):
RC29 (US): http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
RC7(Europe):http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
4. Put the file you just downloaded onto your freshly formatted SD card (make sure it is named DREAIMG.nbh, the rc7 file downloads with .NBH which is wrong)
5. Turn your phone off.
6. Hold down the Camera button, and press the Power button until the bootloader starts.
Note: On some G1s it may require pressing the action button (trackball), while on others it may require pressing the power button.
7. Follow the on-screen instructions to flash the image.
8. When it's done, press the trackball.
9. Press the Call, Menu, and Power buttons at the same time to reboot. You may need to unplug your phone for this to work.
10. And you're done, your phone is in Manufacture default-settings.
If you want to flash a ROM follow a guide (start from the beginning)
Tell me if it worked or didn't worked!
Source: http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod

what tally said....
but on the one i described, just to let you know, i flashed the rc29 dreaimg.nbh like 15 times, it would never get off the G1 boot screen

tnpapadakos said:
what tally said....
but on the one i described, just to let you know, i flashed the rc29 dreaimg.nbh like 15 times, it would never get off the G1 boot screen
Click to expand...
Click to collapse
Try flashing the ROM again if you can go to the bootloader(Rainbow) screen try this:
1. take out the SD card
2. download this file ,open the folder and paste the dreaming.NBH file to the root of your SD card(use your pc or another phone to past this on your SD card).
2. you should get a gray screen once the card in placed back into the phone
3. then press power to start update
4. once the update is complete press the track ball then the rainbow(bootloader) screen should come back up,
5. pull out the battery and there you go your phone should work again
Note: If it didn't updated turn of your phone and turn it on by pressing (& holding) Power+Camera button.
Tell me if it worked

Lol, for some reason it double posted my previous post sorry.

He says in the first post Camera / Power dosent load the bootloader

vixsandlee said:
he says in the first post camera / power dosent load the bootloader
Click to expand...
Click to collapse
send it back

vixsandlee said:
He says in the first post Camera / Power dosent load the bootloader
Click to expand...
Click to collapse
Yes I know but if he connects it to he's PC and turns it off and on and then go to bootloader it will work.

tally114 said:
Yes I know but if he connects it to he's PC and turns it off and on and then go to bootloader it will work.
Click to expand...
Click to collapse
Interesting, I didnt know that.
Thanks for the info.

tally114 said:
Yes I know but if he connects it to he's PC and turns it off and on and then go to bootloader it will work.
Click to expand...
Click to collapse
Doesn't work either. Connected, disconnected, SD card in or out, SIM card in or out and any combination of that.
Logcat just sits and says "Waiting for device" while the phone just hangs on the G1 screen. So unless there is a different way to get into the bootloader besides using Camera+Power I'd like to know.
Camera+Power and Home+Power are unresponsive.

Well... it sounds like you've got yourself a fancy plastic brick, just remember for next time
1. Downgrade
2. Radio
3. Spl
-------------------------------------
Sent via the XDA Tapatalk App

G1 Reverted to RC29 stuck at "Android system recovery utility"

I have a (formerly) rooted G1 that I've attempted to revert to stock RC29 by following the "Full Downgrade Guide" at the CyanogenMod wiki.
My device had HBOOT-1.33.2005, so I used the suggested fastboot command to roll it back to HBOOT-1.33.2003 from the g1boot.zip file linked on that page. This seemed to go well, after which I rebooted into the fastboot (which was still the skateboarding androids screen) again and saw the new (old) HBOOT in the information.
Powered off the phone, inserted the SD card loaded with the DREAIMG.nbh linked in the page, and reflashed the phone. Rebooted with Send+Menu+End, and the phone kept rebooting at the T-Mobile G1 logo screen.
So, I attempted the flash again from the bootloader menu, which is now the "rainbow" style, and shows HBOOT-0.95.(something). It immediately picked up the DREAIMG.nbh file on the SD card and asked if I wanted to flash, chose yes. Same result again: a boot loop at the G1 logo.
I redownloaded the DREAIMG.nbh file without the download accelerator I'd used before, placed it on the SD card, and booted into the bootloader again, flashed, and still the same looping.
So, I attempted to access the "recovery mode" by pressing and holding menu while powering on. I got the G1 logo, then a black screen... pressing Alt-L showed "Android system recovery utility", and nothing else.
Now, the phone will do nothing BUT Android system recovery utility, regardless of what buttons I press or do not press, and I have to remove the battery to turn the damn thing off. Pressing Alt-S, Alt-W, Alt-X, or anything else does nothing.
Where should I look to try to figure out how to recover this thing?

Is a simcard in the phone? Can you get into recovery and wipe incase the partitions are confused?
(Edit, the hint was the sim card)

There's no SIM in the phone at the moment. I can't do anything at the system recovery, except turn the log on or off with Alt-L (which I guess means it's not frozen).
It isn't recognized by ADB anymore, since it has some bastardized version of the stock T-Mobile image that has USB turned off (right? I'm new at this. ).

A bit more info:
I can get into "blue light" mode, and the light is amber/green when plugged into a charger. Sometimes, when I plug the charger in the phone will turn on immediately; but not always.
When I start the phone up and it boots into the broken recovery console, Windows does see an "HTC Dream" device, but ADB doesn't see it.

ezterry said:
(Edit, the hint was the sim card)
Click to expand...
Click to collapse
Should I, or should I not have the SIM in? For what its worth, the phone behaves exactly the same either way.
Thanks for the help.

I just had this exact experience; have you made any progress, goatlordbob?

same happened to me.
cant fastboot, loop at G1 screen, and all i can see in recovery is: Android system recovery utility
some1 find some solution?

why doesnt there seem to b any help for this matter, smh

bull.. s**t
I'm in the exact same boat now. I followed those directions *to the letter* and it put my G1 in this state. Thanks to the wiki maintainer for such wonderful attention to detail. /s
Is there NO way to recover from this?

try to flash this nbh file.... http://www.4shared.com/file/9izdCbvo/DREAIMG.html

ldrifta said:
try to flash this nbh file.... http://www.4shared.com/file/9izdCbvo/DREAIMG.html
Click to expand...
Click to collapse
How? None of the key commands work. Like the OP I can hit Alt+L and it shows ""Android system recovery utility" but that's as far as it goes.

Anyone bothered booting using home + power?

shadowch31 said:
Anyone bothered booting using home + power?
Click to expand...
Click to collapse
Yes - T-Mobile G1 logo, then blank screen forever.

HTC Tattoo bricked? Doesn't boot, goes to fastboot...

Hey!
This is the issue: when I try to turn the phone on by just pressing the red button it goes directly to the fastboor menu. If I try to go to the recovery from there shows "TATTOO" for hours. If i try to go to the recovery dirctly by pressing HOME+ red button, it firsto shows the fastmenu for a second and tries to boot unsuccessfully. During this boot tries, I try to get some info with adb logcat, but the device is not casting anything. And well, if a picture is worth a thousand words, I guess a video is way better:
youtube.com/watch?v=zAejyMIVNGk (newbie, no urls!)
sorry for my english
And well, I have no idea how I got to this, this used to be my phone, but I bought a Nexus One and gave this to my sister, who has no idea what happened (as usual). Oh, this morning somehow I managed to get to the recovery menu, and booted until the android bootscreen, then vibrated and died again. I got to the recovery again, made a nandroid backup and wiped all data, it booted successfully, but the rom had no home application and ran really bad.
I was about to try to make a goldcard and install the stock RUU rom, but if I have no adb I cannot make one...
Any idea?
PS: the rom was nFinity 1.18 (2.2 Froyo) and the recovery was the lastest Clockwork.
PS2: I just realized that in every place I say fastboot I mean HBOOT, sorry again

sounds like recovery is still there, if you hold home + menu when phone if off , and then click red power button you should get recovery menu.
Then hopefully you can try full wipe and install a rom , rember the first time u boot a rom might take a few minutes
let me know how it goes

Yup, not using that method but I can manage to get to recovery sometimes. I'm trying to flash another ROM, but for some reason it doesn't let me. I've tried KalimochoAz (gingerbread) and HDCR (donut) and says something about assertion failed when checking if the device was click on the first case and in the second, complains about unsupported stuff...
I was about to try another roms by random but the SD does not refresh or even mounts, there must be something really messed up with this phone...

You can try to flash your stock rom from fastboot.
You don't need a goldcard, just run the update utility on pc, go to your temp directory and take the rom.zip file, rename it to CLICIMG.zip, copy it to sd card, put card on device and on fastboot menu pres vol down to start flashing the rom. I is the same version with the rom that device has before rooting, you will not get any errors.

I think there's a little misunderstanding here, mainly because of my confusion, it's not the fastboot menu qhat I get, but the HBOOT menu, and pressing the back button in order to access fastboot doesn't work...

oh I managed to boot something, I renamed the RUU exe to CLICDIAG.zip, because I could not find anything in C:\temp (is there where I have to look for the file?)
anyway, the zip appears to load on the phone, but once the progress bar completes, nothing happens... In my computer, the zip contains a .txt file and boot.img, but appears to be corrupt, and cannot extract any file (obviously, it's an exe)
so what do I do?

manutenfruits said:
oh I managed to boot something, I renamed the RUU exe to CLICDIAG.zip, because I could not find anything in C:\temp (is there where I have to look for the file?)
anyway, the zip appears to load on the phone, but once the progress bar completes, nothing happens... In my computer, the zip contains a .txt file and boot.img, but appears to be corrupt, and cannot extract any file (obviously, it's an exe)
so what do I do?
Click to expand...
Click to collapse
Of course will not work like this.
You must first run the RUU utility on pc and while is open to search your temp directory(maybe is inside another folder) for rom.zip file. This is the rom, the executable is an installation program which contain the rom and the app to flash the rom from pc packaged. You need only the rom.zip for flashing from sd card.

I've looked in the whole hard disk for that rom.zip after executing the RUU (I cannot get further than the step that tries to detect the tattoo, failing, so maybe it's not even created).
Apart from that, I managed to boot twice to what seems to be gingerbread, nFinity 1.18, but says in the lower left corner "Safe Mode" and I have no home application, no action on any button, just the notification bar and the lock screen. ADB doesn't work either.

manutenfruits said:
I've looked in the whole hard disk for that rom.zip after executing the RUU (I cannot get further than the step that tries to detect the tattoo, failing, so maybe it's not even created).
Apart from that, I managed to boot twice to what seems to be gingerbread, nFinity 1.18, but says in the lower left corner "Safe Mode" and I have no home application, no action on any button, just the notification bar and the lock screen. ADB doesn't work either.
Click to expand...
Click to collapse
You don't need to go so far. Just run the ruu utility and when the first screen appears go to temp dir(c:\users\you user's name\local\appdata\temp on windows 7). The executable is an encrypted package and when you run it extracts all included files and then starts the installation program. These files will deleted after this program exits(when the installation complete or an error occurs)

Cool! I just renamed it to CLICLIMG.zip and I finally loaded. The problem now is that when it finishes, instead of asking me to flash it, says
"CID Incorrect!
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No"
While running the RUU I made sure that it was for HTC Tattoo since it showed me the device during the steps. And I got it from a post describing the steps to flash it using the goldcard.
Furthermore, this error is something similar to what happened when I tried to flash from the recovery. This is REALLY weird...

Probably this isn't the sama as your device's stock rom. I think goldcard needed for flashing any htc original rom, but without goldcard only the device's version will be flashed successfully. Try to download other original roms if you don't know which you had before.
Here is a site with shipped roms for tattoo:
http://www.shipped-roms.com/index.php?category=android&model=Click

The RUU wasn't a problem, I tried now with a goldcard and flashed successfully! I could not get ADB connection to make it, but I once made one and still had the .img in my mail inbox.
But still nothing has changed...
pressing on drives me to the HBOOT screen, whose only options that work are "simlock" to flash CLICIMG.zip, and recovery (freezes on "TATTOO")
EDIT: does not freeze, but goes back to HBOOT after a while... ¬¬

You say that now you have the stock HTC rom and again you cannot boot it and instead the device reboots again to HBOOT?
Then maybe you have a hardware problem which leads to this behaviour.

OK, now I guess it still has warranty, but the problem is that I rooted it.
But now that I flashed somehow the original rom, should be no problem right?

Yes, if you successfully flash the stock rom, you're not root any more.

had that problem to, but theres easy fix for it without doing all whats being sayd here
Even tho phone dont boot annymore and stays on logo plug in the usb cable
and work with adb shell and reflash recovery (to be good tattoo-hack.ko etc tricks need to be done before doing it or you get errors)
http://forum.xda-developers.com/showthread.php?t=716282 step 1.5 and tools from step 1.3
and ether get Amon RA recovery or clockworkmod and use
Code:
./flash_image recovery /sdcard/recovery.img
then reboot into recovery
HTML:
adb shell "reboot recovery"
mount usb put in a custom rom and flash it
if all done well should work (had same problem)
bascly adb still work even if you think you bricked phone just have to let it "startup"
Greetings

I'm afraid that won't work. I've been trying all the time with adb logcat and adb devices unsuccesfully. I thought that the TATTOO bootscreeb would give me some feedback in all cases, but now doesn't seem to work...

I've had similar problems when trying to flash nfinityGB.
My problem was that I missed something on the way from
- creating a gold card
- rooting device
- installing recovery
- flashing rom
All I did was to download and execute "RUU_Click_HTC_WWE_1.67.405.6_WWE_release_signed_NoDriver.exe" (or any other ruu).
Be shure to have SDK with all drivers installed properly.
After this your device is in unrooted (original) state as dancer_69 already told you.
Now you can decide whether to claim warranty or properly follow the guides on xda to get root and flash custom roms.

I think I know from long ago what is happening here, just couldn't believe it. Maybe the keys are sticked or something, that would explain the always going into fastboot mode without pressing the VOL DOWN key. Now it boots 1 out of each 5 tries, and when it gets to the home app, it's on "safe mode" (achieved by pressing MENU key while booting).
I think they will take care for it back in the HTC support (well, I hope)

manutenfruits said:
I think I know from long ago what is happening here, just couldn't believe it. Maybe the keys are sticked or something, that would explain the always going into fastboot mode without pressing the VOL DOWN key. Now it boots 1 out of each 5 tries, and when it gets to the home app, it's on "safe mode" (achieved by pressing MENU key while booting).
I think they will take care for it back in the HTC support (well, I hope)
Click to expand...
Click to collapse
Something like this thought when I said that maybe is a hardware problem.

[Guide] How to [unlock/flash recovery/rom] on [Evo 4g 2.3.5] [Hboot 2.18.001]

THIS WILL BE USING THE CM 7.1 ROM. IT WORKS WITH OTHER ROMS TOO. JUST FOLLOW SAME PROCEDURE WITH YOUR ROM.
INTRODUCTION AND WARNINGS:
If you have an Evo 4g updated to android 2.3.5 with hboot 2.18.0001 and your wifi always randomly disconnects this guide is for you! The reason the server disconnects is because your router could be incompatible with your HTC phone. If it's just because of some wifi problems and some easy fixes could be made, I would go with that. But for those who have the same problem, not only will you get a cool Cyanogenmod 7.1 look... you'll be able to play PL with wifi.
I'll try to make it as easy to understand as possible... as I'm not good with this stuff either and it took time to understand the guides. Actually I used several guides but I'll kind of combine them.
This guide is for flashing Cyanogenmod 7.1 and what to do before. I am not responsible if there are any problems with your device. Use this guide at your own risk, although there's 99.99999% chance everything will go right if you follow the guide.
PART ONE:
First you'll want to install this file, you need winrar. Just unzip onto desktop so it's easier. You won't actually be using the tool but the root folder. Read the xda first post first though... http://forum.xda-developers.com/show...75&postcount=1
Here's link to download if you've read the post:
http://goo-inside.me/apps/frigid/
Then you'll want to go to www.htcdev.com.
You'll have to register there and use a real email address.
After you register login and click unlock boot loader. Where there's a scroll-down, choose "all other supported models"
Then click get started, the site will guide you through the next steps. Remember, this could void your warranty, I'm pretty sure there is a way to undo this all but remember do this at your own risk.
Tips: If you can't navigate to the right place remember to type "cd [insert name of root folder]"
To get the address, just go to root folder and click copy address at the top. (Right click on where it shows what folder you're in)
After you have successfully unlocked your boot loader you are ready for part 2.
PART TWO:
Enter fast boot on your phone again.
If you closed your command prompt, (which is fine) open it again.
Download this file and save it:
http://files.androidspin.com/downlo...ECOVERY/&file=recovery-RA-supersonic-v2.3.img
The file should appear in downloads.
Move the file into your folder titled root.
If the file is not named recovery rename it to that.
In your command prompt go the the root folder address like you did in part one.
Once you've successfully entered the "root" folder, type this in and hit enter:
fastboot flash recovery recovery.img
(Remember your phone should be connected to your computer with usb debugging on, with disk drive on, and it should be in fast boot)
Once the prompt finishes the command, go back to main boot loader screen. Then use the volume keys to go down to select recovery.
Press the power button to select recovery.
Once the recovery boots on your phone, select use the volume keys to select/highlight USB MS then press the power button.
Take this zip (don't unzip it) and place it into your sd card (just the root, not in any folders).
Zip: http://download.cyanogenmod.com/get/...nic-signed.zip
Press the power button to exit USB MS.
Now go back to main screen of recovery.
Highlight/select the choice flash zip from sd card and press the power button.
Select/highlight the zip you put in your sd card and press the power button to flash.
Press the power button again to confirm.
Once it's done flashing reboot your phone.
If your phone goes into boot loop (keeps rebooting at cyanogen logo thing) then go to your recovery again and select wipe and select wipe all data/factory reset.
OPTIONAL PART 2.5:
If you're looking for Google apps you might want to flash this too, same thing with the Cyanogen ROM, flash it same way.
http://cmw.22aaf3.com/gapps/gapps-gb...828-signed.zip

This working for everyone?

Do people actually read this? Did I post in wrong section?

Guide updated v1.1
Fixed link to Amon Ra Recovery. Last link worked but file was deleted.

Hey man, I have no need for the guide , but much thanks, sincerely. Thanks
sent from AOKP heaven

Ok... I guess...

so does using that htc super tool folder instead of android sdx not wipe everything while unlocking? Or does it still do a factory reset when you unlock?

Trying to figure out what I'm missing here. I have step one all finished. On step two I'm doing the part that says:
"Once you've successfully entered the "root" folder, type this in and hit enter:
fastboot flash recovery recovery.img"
I have the USB Debugging on and Disk Drive on, and the phone in Fast Boot. When I type the "fastboot flash recovery recovery.img" and hit enter it says Waiting for device. Should it say waiting in the command prompt area? Even with that saying waiting, if I use volume down and pick recovery, the screen shows the green circle and downloading logo, then I get the red exclamation screen. What's messing things up? I have the instructions followed exactly up to this point.

BigPimpin said:
Trying to figure out what I'm missing here. I have step one all finished. On step two I'm doing the part that says:
"Once you've successfully entered the "root" folder, type this in and hit enter:
fastboot flash recovery recovery.img"
I have the USB Debugging on and Disk Drive on, and the phone in Fast Boot. When I type the "fastboot flash recovery recovery.img" and hit enter it says Waiting for device. Should it say waiting in the command prompt area? Even with that saying waiting, if I use volume down and pick recovery, the screen shows the green circle and downloading logo, then I get the red exclamation screen. What's messing things up? I have the instructions followed exactly up to this point.
Click to expand...
Click to collapse
have to take it out of disk drive mode i believe and put it in charge only

evo4gnoob said:
have to take it out of disk drive mode i believe and put it in charge only
Click to expand...
Click to collapse
Tried doing that and it goes right to the red exclamation screen instead of the green first. The instruction say to have it in disk drive, so not sure what to do.
"Once you've successfully entered the "root" folder, type this in and hit enter:
fastboot flash recovery recovery.img
(Remember your phone should be connected to your computer with usb debugging on, with disk drive on, and it should be in fast boot)"

BigPimpin said:
Tried doing that and it goes right to the red exclamation screen instead of the green first. The instruction say to have it in disk drive, so not sure what to do.
"Once you've successfully entered the "root" folder, type this in and hit enter:
fastboot flash recovery recovery.img
(Remember your phone should be connected to your computer with usb debugging on, with disk drive on, and it should be in fast boot)"
Click to expand...
Click to collapse
when i did it to my phone i had it in charge only

This is my first time trying to do anything to my phone. What exactly does the recovery step I'm doing do? It is saving all my personal data on the phone? I could care less if the phone gets wiped. I have all my contacts in Gmail and re-installing apps take like 5 minutes, so wondering if I could just skip it?
This rooting thing is getting more and more confusing. I'm pretty good computer wise, but reading on this site to try and root this phone, I find topics which are like 100+pages long, and the topic I find link to other topics and it keeps going on and on, and not sure what to do after a while. This topic has gotten me closer to finally doing it then any other. Hopefully I can get it to work fully.

Tried disk drive on and off a couple times and still getting stuck on the red exclamation.

BigPimpin said:
This is my first time trying to do anything to my phone. What exactly does the recovery step I'm doing do? It is saving all my personal data on the phone? I could care less if the phone gets wiped. I have all my contacts in Gmail and re-installing apps take like 5 minutes, so wondering if I could just skip it?
This rooting thing is getting more and more confusing. I'm pretty good computer wise, but reading on this site to try and root this phone, I find topics which are like 100+pages long, and the topic I find link to other topics and it keeps going on and on, and not sure what to do after a while. This topic has gotten me closer to finally doing it then any other. Hopefully I can get it to work fully.
Click to expand...
Click to collapse
Recovery just puts a base place where you can flash roms and stuff.
And if you get a bootloop on CM7.1 yes you will have to wipe all.
As for the recovery flash problem, try putting it on charge only and usb debugging. Then power off phone or just take out battery and reboot into bootloader. Go into fastboot again and try to flash recovery on again. Then try it.

Did you rename the recovery img to recovery? Or if it's not saved as recovery.img rename it to that.

I have it named recovery like it's supposed to be. Still get the green screen then the red exclamation mark.
What should happen when you first go into the fast boot? The reason I ask that is, when it first goes into the fast boot screen it takes a second or so to do it's thing. I see some text going on the screen real quick, and from what I can read of the text I see something about no image and can't read much else, then it is ready to use the volume up and down to make selections. Is that normal, the text part and all about no image? My phone works fine, just can get the steps in this tutorial to work.

BigPimpin said:
I have it named recovery like it's supposed to be. Still get the green screen then the red exclamation mark.
What should happen when you first go into the fast boot? The reason I ask that is, when it first goes into the fast boot screen it takes a second or so to do it's thing. I see some text going on the screen real quick, and from what I can read of the text I see something about no image and can't read much else, then it is ready to use the volume up and down to make selections. Is that normal, the text part and all about no image? My phone works fine, just can get the steps in this tutorial to work.
Click to expand...
Click to collapse
When you go to the bootloader it scans for a PC36IMG.zip file. Normally if you were s-off that's how you would flash a recovery. Since your s-on unlocked the only thing that can be flashed in PC36IMG.zip format is a file signed by HTC like a RUU
Sent from my swiper using XDA App

I got a chance to see some of the names of the missing files it lists when going into boot load. The PC36IMG.zip is one of them that says no image. So guessing that file isn't even there at all. I searched for a PC36IMG.zip file and put it in there and got more then I have seeme before on that screen. I had a blue progress meter on the right side. When it got done it said something about being too old and unsuccessful.
Also, I tried starting all over, even going into the htcdev site again. When I did that all the step worked, but when it's supposed to get to the screen where it tells you it will wipe your phone, that screen never comes up. Now I'm wondering if I can just start all the way over. Can I go into my phone and of I select factory reset, will it make the phone a totally stock phone again and change anything I might have changed? Not that I'm sure I have even changed anything at all to this point.

Removed the batter over and over till I could see the message that comes up very quickly when fast book first starts up. It reads:
Loading...[PC36DIAG.ZIP]
No Image!!!
Loading...[PC36DIAG.NBH]
No Image!!! or Wrong Image!!!
Loading...[PC36IMG.ZIP]
No Image!!!
Loading...[PC36IMG.NBH]
No Image!!! or Wrong Image!!!
Know where I go from here to correct things?

BigPimpin said:
Removed the batter over and over till I could see the message that comes up very quickly when fast book first starts up. It reads:
Loading...[PC36DIAG.ZIP]
No Image!!!
Loading...[PC36DIAG.NBH]
No Image!!! or Wrong Image!!!
Loading...[PC36IMG.ZIP]
No Image!!!
Loading...[PC36IMG.NBH]
No Image!!! or Wrong Image!!!
Know where I go from here to correct things?
Click to expand...
Click to collapse
it shouldnt find a PC36IMG.zip file or the other. Only files in that can be flashed in that format is radios hboots splash screen RUUs recoveries. You shouldnt go around just flashing random things in the bootloader you can end up bricking your phone

Nexus 4 was boooting only in CWM. But now not even starting.

Hi,
Please help out
NOW I am not able to start mobile.. Plug in the charger and charge for 6 hours ... But mobile remained coool as ice... Only red light came for a second when i hook it in...... Pressing the vol down and power and then put charger was also no help.. Only in this case red light stayed longer........
Screwed ..dont know what to do...... ( (
Earlier I was doing this:
Was using your Nexus 4 rootkit.. Everthing was done and phone was rooted .
Now i wanted to update the CWM. I chose the option 11 boot or flash .img files to device. I chose the cwm mako version
and decide to flash it.
Now i am asked options such as boot, bootloader, radio etc.
Here I choose Boot..(This I think I have done wrong.)
Now. Phone only boots to recovery... No matter I with on , Off I cannot go anywhere.. I go directly to CWM.
I tried your toolkit again and this said Phone needs to go in adb .. It says waiting for device..
I cannot also mount the SD card so that i can put some images in the phone...
======================================
I had taken this of my thread from... http://forum.xda-developers.com/showthread.php?t=2058505
Just wanted to highlight this.. SO that I get more and more ideas and solution
If I had done wrong.. You can delete/close the thread...