Database Develop

G1 Home Button not working - ROM installation help!

Well, the home button on my unlocked G1 stopped working about a week or so ago. No big deal, but the problem I now face is that I am unable to install any new roms.
I am able to boot into recovery mode (cyanogen v1.4) using ADB, however once there, I am unable to install a new rom since my home button does not work.
Is there any way around this either using the phone or through my computer (I am using MAC OS 10.5). Any help would be GREATLY appreciated.
- Thomas

fastboot.
10char

evilkorn said:
fastboot.
10char
Click to expand...
Click to collapse
For the life of me, I cannot seem to get fastboot to work for me on my mac. Maybe it is just me and I am unable to follow directions, but for some reason I cannot get it to work under Mac OS10.5 and I have no Window PC to try it out there.

You could try everything from adb shell. I don't know why fastboot wouldn't work if adb is working as they go hand-in-hand. I don't have the shell commands to flash, but I'm sure they are around here somewhere.
http://developer.htc.com/google-io-device.html
They have the fastboot binary if you wanted to try that instead what you have.

evilkorn said:
You could try everything from adb shell. I don't know why fastboot wouldn't work if adb is working as they go hand-in-hand. I don't have the shell commands to flash, but I'm sure they are around here somewhere.
Click to expand...
Click to collapse
Decided to remove and reinstall adb again. For some reason now, fastboot does work even though I did the exact same things as before.
Thanks for the help evilkorn

Less than an hour after you posted... I'd say it's a pretty fast solution. =p

As stated, got flashboot to work, I now have another problem. When I try to install the rom using flashboot, I get this error;
Dell:tools szuba$ fastboot update jacheroski2.2a.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Dell:tools szuba$
Any way around this?

New solution. Flash amon ra's 1.2.2 recovery, that version had verify with send, instead of home. The link in my sig has the download for the current and past version.

dude you can still boot into recovery. go into terminal emultaor and type su then reboot recovery

pistol4413 said:
dude you can still boot into recovery. go into terminal emultaor and type su then reboot recovery
Click to expand...
Click to collapse
Read his first post... The problem is the home key to OK the flash.

szuba said:
Well, the home button on my unlocked G1 stopped working about a week or so ago. No big deal, but the problem I now face is that I am unable to install any new roms.
I am able to boot into recovery mode (cyanogen v1.4) using ADB, however once there, I am unable to install a new rom since my home button does not work.
Is there any way around this either using the phone or through my computer (I am using MAC OS 10.5). Any help would be GREATLY appreciated.
- Thomas
Click to expand...
Click to collapse
One of Amon's recovery versions using the green "call" button to confirm actions (rather than the home button).

Must be my luck... installed Amon's previous recovery img but now my green (send/call) button doesn't seem to be working either.
For some reason, both my green (send/call) and home buttons do not work so both methods do not work for me. The only option that I can think of is to someone create a boot.img, data.img, and system.img from a rom and do a fastboot nandroid backup from those. Now if only I can find away to do that... anyother ideas?
And thanks for the help so far

Do the alt+ commands ask you to verify the update with home?

evilkorn said:
Do the alt+ commands ask you to verify the update with home?
Click to expand...
Click to collapse
Yes, the alt+ commands still requires you to verify with the home (or green) key.
Any chance there is away to do it through the console with code? Tried to do a search, but didn't come up with anything in regards to that.
Totally lost for ideas now... but the help is greatly appreciated evilkorn

--update_package=SDCARD:update.zip" > /cache/recovery/command
Try that

B-man007 said:
--update_package=SDCARD:update.zip" > /cache/recovery/command
Try that
Click to expand...
Click to collapse
Where exactly do I try that?
When I enter;
--update_package=SDCARD:update.zip" > /cache/recovery/command
in the recovery console, nothing happens, just goes to the next line.

Rogers HTC Dream died, plz Help!

I follow this instruction
http://forum.xda-developers.com/showthread.php?t=558301
I flashed the rom by another custmer firmware (same process as magic before)
after i update the rom, then i restart it, but I just get stuck with the ROGERS logo loading screen and nothing else after that.
I got this message when it is in fastboot(in red color) mode.
DREAM PVT 32B ENG S-OFF
HBOOT -1.33.2005 (DREA21000)
CPLD-4
RADIO 3.22.20.17
Apr 20 2009, 15:30:43
(camera step2)HBoot Mode
(back) Reset Device
(Action)Restart to HBoot
(Menu) Power Down
I wait 1 hour, it still shows Rogers Logo on the sreen, nothing happend. I tried all the combination keys. ( it either shows flashboot mode or get stuck with the Rogers logo. I have even no chance to flash another rom again.
So is anyway to fix it please? great appreciate for any kind helps.

You need to flash your radio. Go here, grab the radio "ota-radio-2_22_19_26I.zip."
Put the zip file onto the root of your SD card, and flash from recovery.
Edit: Wait I misunderstood all that. Can you get to recovery?

FaJu said:
You need to flash your radio. Go here, grab the radio "ota-radio-2_22_19_26I.zip."
Put the zip file onto the root of your SD card, and flash from recovery.
Edit: Wait I misunderstood all that. Can you get to recovery?
Click to expand...
Click to collapse
Thanks for your fast reply. Mr.Faju
so download it and rename to update.zip, then put it into the memory card?
but I cannot get into the recovery mode any more.

Ah okay. But you can get to fastboot so all you need to do is take the recovery.img you downloaded from this zip file and put in the "tools" folder of your sdk. Then:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
This should give you back your recovery partition. Reboot while holding the home button after doing this and see if you can get to recovery. If you can then yeah just use that radio update and flash anything.

FaJu said:
Ah okay. But you can get to fastboot so all you need to do is take the recovery.img you downloaded from this zip file and put in the "tools" folder of your sdk. Then:
This should give you back your recovery partition. Reboot while holding the home button after doing this and see if you can get to recovery. If you can then yeah just use that radio update and flash anything.
Click to expand...
Click to collapse
Hi Faju, thanks again for your reply. i just downloaded the android-sdk_r3-windows, and as you said, i put recovery.img into the tools folder. once i click the sDK Setup, the dos window automatic gone. I have no chance to enter the code.. by the way, i am using windows 7, no sure if is that matter?

Oh no don't do it that way. Open a dos window and navigate to the tools folder inside the sdk. So if your your sdk was in "C:\Android\sdk" you would do the command
cd C:\Android\sdk\tools
Click to expand...
Click to collapse
Once you've navigated to the tools folder, put your phone into fastboot mode, and on the dos screen on your conputer type that command I quoted in my last message. Once you enter the command you'll see a progress bar on the top right corner of the white bootloader screen on your phone. Once it finishes, reboot your phone while holding home.

FaJu said:
Oh no don't do it that way. Open a dos window and navigate to the tools folder inside the sdk. So if your your sdk was in "C:\Android\sdk" you would do the command
Once you've navigated to the tools folder, put your phone into fastboot mode, and on the dos screen on your conputer type that command I quoted in my last message. Once you enter the command you'll see a progress bar on the top right corner of the white bootloader screen on your phone. Once it finishes, reboot your phone while holding home.
Click to expand...
Click to collapse
great. you are the man Mr.Faju. now i can get into the recovery utility mode again. IT shows: CyanogenMod V1.2 + JF. is that okay to upgrade the radio on that? because I saw v1.4 would be better.
I just did update the ratio, but i cannot get into any fastboot or recover mode( it always shows Rogers logo). i tried all the combination keys... any idea plz? Thanks a lot

Uh you can't get to fastboot?
**** I remember you had to flash radio but it wasn't the one from HTC. It was Haykuro's. Could you try reflashing the Rogers RUU again? The one that gives you the 1.33.0010 spl. At least that will get you back to stock and get your phone restarted. Then redo everything with the flashrec application from your first post.
This time do the same thing to get back your recovery partition but flash the radio from this file. This is haykuro's Rogers root from his thread. This is what worked for me before. This zip also has the 1.4 recovery.

FaJu said:
Uh you can't get to fastboot?
**** I remember you had to flash radio but it wasn't the one from HTC. It was Haykuro's. Could you try reflashing the Rogers RUU again? The one that gives you the 1.33.0010 spl. At least that will get you back to stock and get your phone restarted. Then redo everything with the flashrec application from your first post.
This time do the same thing to get back your recovery partition but flash the radio from this file. This is haykuro's Rogers root from his thread. This is what workede for me before. This zip also has the 1.4 recovery.
Click to expand...
Click to collapse
e
no. I cannot get into any fastboot or recovery mode any more. i cannot use the RUU since it requiest it can get into the system at least. I did a search, and found it died, and cannot be fixed so far. I will try to talk with the Rogers tech support guy tomororrow morning to see if i can have the replacement even i get the phone from my friend. It is okay Mr.Faju, at least i know what is the problem and know how to use the sdk now. Thanks again for your time. you teached me a lot.

[Q] Fastboot.

Tried to install Cyanogen 6.1... It failed.
From there the device booted up normally on a fresh start, but I tried to recover my backup and that is where everything got all messed up.
Im stuck on the G1 screen.
Ive gotten it to the fastboot mode and Im downloading what I think I need to get my phone working again. Ive downloaded the Andriod 1.6 image from the HTC website. Do I need the recovery? I just want 1.6 until I have time to try and get Cyanogen installed.
Im currently installing JDK for the Andriod SDK.
Am I headed in the right direction?
I was using ROM Manager with Clockwork Mod. My old ROM was Super E... Not sure what version, but it was Andriod 2.1

What radio/spl do u have?

johnson8cyl said:
What radio/spl do u have?
Click to expand...
Click to collapse
2.22.19.26I

Tbry said:
2.22.19.26I
Click to expand...
Click to collapse
And spl? Do u have and eng spl? (S-off). If so u could fastboot erase your system and try to flash the rom through recovery. And fastboot flash a recovery of your choice first. Have u tried going on ezterry's thread with the new radio/spl and going that route?

Not sure what the version of the SPL is, but I know it is off. I'll check his thread out and give it a try. I might end up finding someone who actually knows what they are doing, or buying the Nexus S.

Ok. If u follow his thread exactly and fastboot flash the radio/recovery/spl u should end up with everything as described in the thread and be able to move on with cm6 with appropriate kernel. Alternatively u could boot into fastboot and open up your terminal on your computer and type in code to fastboot recovery of your choice (after it's download and put in sdk/tools folder on your PC) he has amonra link in his thread for download . Then type fastboot erase system -w (hit enter). When it's done type fastboot erase boot (hit enter). Then power down. Power back into recovery with the rom on your sdcard and flash away.

That is actually what I'm trying to do. Its just about my only option at this point.
Im having problems getting everything set up correctly though.

What are u having problems setting up?

I installed Andriod SDK, seems to be working.
Downloaded the drivers, which seems to have stopped my computer from seeing the phone.
I downloaded the Fastboot.exe, tried to run it but it cannot find ADB.dll ( Pretty sure thats what it was.)
I was basically following the steps on the cyanogen wiki.
When I have some time, I will try the Fastboot for noobs guide.

I think I followed a guide in androiddevelopers.com or something like that. If I find it again ill post a link. I don't think I ran a fastboot exe file though. Just have it in my androidsdk/tools folder. Added the variable to my paths and was good to go. Not at my PC currently though.
Edit: developer.android.com/sdk/
I believe is what I followed

http://forum.xda-developers.com/showthread.php?t=532719
Following this for fastboot.
I cannot update anything. Home + power doesnt do anything.
Only thing I can access is fastboot mode.
Fortunately my radio is up to date, so I assume my SPL is as well.
Going to attempt to try the fastboot step, once I can get the SDK working correctly
edit: I knew if I spent enough time working at it that I'd get it working.
Only problem now is getting my device to be listed.
Edit2: at first when I entered fastboot mode, I would get the "Add new hardware" for the device "Andriod 1.0"
It now says "andriod bootloader interface"
I feel like I'm so close. I'm going to keep playing with it, but what can I do to get my device listed when I type the command "Fastboot devices"?
Edit 3: Awesome. I got fastboot to work and my phone is recognized. Only problem now is getting my SD card reader to work so I can put the proper files on
Final edit: MY phone is killing SD cards for some reason. Don't know what to do
Got the SD cards to work, for some reason though, some of the commands are not working. When I type fastboot shell, I just get the usage doc.
When I do fastboot update, I get the following: error: failed to load 'update.zip'

What are u trying to do in fastboot?
Sent from my T-Mobile myTouch 3G using XDA App

Well, I fixed my phone. Back to its original state.
I guess my only question at this point my only question is if I switch to Cyanogen 6.1, will it be less buggy than my Super E ROM?
For anyone wondering, Holding home + end for about 25 seconds is what I did. From there I just went to nandriod and tried to recover the same backup that gave me the problem.

I would say no. It will not be less buggy. U can always flash and try different roms though for experiment sake. Glad u got it back up
Sent from my T-Mobile myTouch 3G using XDA App

RevoToolkit...clockwork install?

tried to install clockwork recovery and Im getting a FATAL ERROR The MD5sum of the installed recovery and the stored MD5sum do not match! DO NOT REBOOT YOUR PHONE Please contact TheCubed ASAP! So any help here would be appreciated.
I used the new one click root for ginger bread which included the Revo toolkit and i tried to install clockwork recovery using 4.0.0.2-pr1, after it failed with the aboved message i tried the revostock option and got the same message, so what do i do now?
please help me TheCubed!

leppricon said:
tried to install clockwork recovery and Im getting a FATAL ERROR The MD5sum of the installed recovery and the stored MD5sum do not match! DO NOT REBOOT YOUR PHONE Please contact TheCubed ASAP! So any help here would be appreciated.
I used the new one click root for ginger bread which included the Revo toolkit and i tried to install clockwork recovery using 4.0.0.2-pr1, after it failed with the aboved message i tried the revostock option and got the same message, so what do i do now?
please help me TheCubed!
Click to expand...
Click to collapse
Try the 4.0.0.2-pr1 again and again until it goes through. DO NOT REBOOT YOUR PHONE UNTIL IT SUCCEEDS, IT WILL RESULT IN YOU BEING STUCK IN FASTBOOT!!!!!

Try deleting mlk file and reinstalling recovery
Sent from my VS910 4G using XDA App

Installed rom manager
I installed rom manager to use to back up phone it rebooted to run the back up and it got stuck in fast boot, so i did some searching and found the page on fixing that. i used the second posters method instead of thecubed (because he said it was easier and thecubed agreed) and now all i get is an lg start screen. do not follow the other guys post it is for another phone completely i had to find it out the hard way. so any ideas on how i can get back to working phone?

The file you deleted was the mmcbik0p8 backup found on your ext card. When reinstalling the recovery CWM should have rewritten it with the correct version.
Try removing your card and mounting it on a pc go in and manually delete file and try to boot the phone. I had to do this to make my revolution boot.

This is how i fixed it
adrenaline_rush said:
Its not hard to fix at all, you will have to install the Java JDK, Android SDK, and three files AdbWinApi.dll, fastboot.exe, and CWMrecoveryrevolution.img which is the clockwork recovery for our phone.
Here are the files in .rar format.
http://www.mediafire.com/?eb3219cy0lbc71m
Android SDK
Java JDK
The first version should work
1. Install the Android SDK to your C: drive. Make sure the SDK and all the files are in C:\androidSDK. This will make things easier later.
2. Open the SDK and install the additional AndroidSDK platform tools package
3. Install the Java JDK
4. Unzip the .rar to c:/androidSDK/tools
5. Open command prompt, start> type "cmd"> press enter
6. Plug in phone
6. Assuming you placed everything in the right folders, type the following into the command prompt
Code:
cd c:/androidSDK/tools
7. You should now be in the correct folder, paste this command next:
Code:
fastboot erase recovery
then:
Code:
fastboot flash recovery CWMrecoveryrevolution.img
If that succeeds then type the final command:
Code:
fastboot reboot
Hopefully this works and is understandable
Click to expand...
Click to collapse

Don't work
Yeah this method don't work any more I tried yesterday and today with the revolution file. Fast boot does not find the phone. Cmd is <waiting for device>. Going to Verizon tomorrow to get new phone.
Edit: why it doesn't work is because I used the easy method that the other user posted, i did not check the phone version of the flash file, so now my phone has the wrong firmware on it and wont boot. Also it does not get recognized by my pc.

leppricon said:
Yeah this method don't work any more I tried yesterday and today with the revolution file. Fast boot does not find the phone. Cmd is <waiting for device>. Going to Verizon tomorrow to get new phone.
Edit: why it doesn't work is because I used the easy method that the other user posted, i did not check the phone version of the flash file, so now my phone has the wrong firmware on it and wont boot. Also it does not get recognized by my pc.
Click to expand...
Click to collapse
You tried the volume up + power to get to the recovery?

Tried that too.
The only way the Vol. up and power button works if I have the battery out and the usb hooked up, and then the screen says do not detach download in progress. I left it this way for about two hours thinking it would magically fix it self but it didn't. Called Verizon about an hour ago and I going to get my new phone in the afternoon tomorrow. they over-nighting it to me, they said any new tech with 4g they try to get it fixed as fast as possible. I then asked when 4g would be coming to my area he said spring of 2013... lol

Oh, you could have flashed the .tot system file over, but I guess it does take some time to get the program set up, and they're already replacing it..

Tried
I had all the above programs installed and working properly, that is how i got to a non-working phone, I flashed it with the wrong firmware which bricked it. Its not detected in any of the programs because all the programs are looking for a revo and i flashed to something else.
This was posted in the revo fastboot fix thread, I followed it and it bricked my phone.
hello everyone, im pretty sure i was the first one to run into this issue since it happened twice on two different phones. but for an extremely easy fix just look here, believe me it doesn't get any easier than this. this is another way it was explained, but both are pretty much the same. im only posting this in case someone doesn't understand the directions posted by thecubed, not saying the ones i post it are better, just explained differently, not trying to step on anyone's shoes here http://forum.xda-developers.com/show....php?t=1088046
Last edited by zr0ko0l; 23rd June 2011 at 03:03 AM.
this is the reply from thecubed: Dont' worry about my toes
If you've got a better explanation, go for it! I'm not the best at writing instructions.

Still no CWM
I rooted my Revo using adb and zergrush. I'm running v6 and cannot get CWM to work using adb, RevoToolKit or even on a command line on the phone itself. So far all I've done is reload my phone. It stays rooted, but no CWM. Md5's all check out on mmcblk0p14 before I restart, using adb and a terminal on the phone. The checksum is right when I dl the recovery-cwm-pr1.img in the zip, also.
I did do an OTA update after I rooted. Could that be the problem? Should I unroot and reroot?

meandmine said:
I rooted my Revo using adb and zergrush. I'm running v6 and cannot get CWM to work using adb, RevoToolKit or even on a command line on the phone itself. So far all I've done is reload my phone. It stays rooted, but no CWM. Md5's all check out on mmcblk0p14 before I restart, using adb and a terminal on the phone. The checksum is right when I dl the recovery-cwm-pr1.img in the zip, also.
I did do an OTA update after I rooted. Could that be the problem? Should I unroot and reroot?
Click to expand...
Click to collapse
Why run V6 when V7 (aka GingerBread) is out?

meandmine said:
I rooted my Revo using adb and zergrush. I'm running v6 and cannot get CWM to work using adb, RevoToolKit or even on a command line on the phone itself. So far all I've done is reload my phone. It stays rooted, but no CWM. Md5's all check out on mmcblk0p14 before I restart, using adb and a terminal on the phone. The checksum is right when I dl the recovery-cwm-pr1.img in the zip, also.
I did do an OTA update after I rooted. Could that be the problem? Should I unroot and reroot?
Click to expand...
Click to collapse
DId you manually use adb and Zergrush or use a different method? Did you use my all in one package with the root.bat? More info would be greatly appreciated.

Issues activating 4G LTE
Hello all,
First post so woot! but, kind of bad news at the same time. My friend and I were rooting/CWM'ing/ROM'ing his phone and we hit this road block. Everything went find up to the flashing of Gingervolt. It boots up and starts the initial setup sequence, but after the step where it ask for language, it sits and spins it's wheels for a while before saying that it cannot find the SIM card. There is also a small SIM card icon with a question mark next to the signal bar meter. This step is keeping us from being able to move forward and was wondering if there is any hope to get this thing to activate.
Things we've tried:
1) Reboot, restore, wiped all the caches
2) Did a nandroid restore of before we flashed it with Gingervolt
3) Downloaded a stock/rooted ROM (and received the same results)
4) Calling Verizon's activation hotline (told us nothing)
5) Taking out/Putting back the SIM card and seeing if that maybe would reset something. (I guess not)
It would be really cool if I could figure this out so he doesn't have to bring it in to big red :3
Thanks and you all rock!
canti-sama

cantibot said:
Hello all,
First post so woot! but, kind of bad news at the same time. My friend and I were rooting/CWM'ing/ROM'ing his phone and we hit this road block. Everything went find up to the flashing of Gingervolt. It boots up and starts the initial setup sequence, but after the step where it ask for language, it sits and spins it's wheels for a while before saying that it cannot find the SIM card. There is also a small SIM card icon with a question mark next to the signal bar meter. This step is keeping us from being able to move forward and was wondering if there is any hope to get this thing to activate.
Things we've tried:
1) Reboot, restore, wiped all the caches
2) Did a nandroid restore of before we flashed it with Gingervolt
3) Downloaded a stock/rooted ROM (and received the same results)
4) Calling Verizon's activation hotline (told us nothing)
5) Taking out/Putting back the SIM card and seeing if that maybe would reset something. (I guess not)
It would be really cool if I could figure this out so he doesn't have to bring it in to big red :3
Thanks and you all rock!
canti-sama
Click to expand...
Click to collapse
Was 4g turned on when you flashed? If nothing else you can flash the zv7 tot file through lgnspt.

Thanks so much for your quick reply,
I think that is going to be my next option. Thanks for reassuring me that is the right direction! And yes, I did have 4g (It was called LTE, I think it's the same thing.) enabled before flash.

cantibot said:
Thanks so much for your quick reply,
I think that is going to be my next option. Thanks for reassuring me that is the right direction! And yes, I did have 4g (It was called LTE, I think it's the same thing.) enabled before flash.
Click to expand...
Click to collapse
What version were you on before you flashed Gingervolt? If you were on v4 or v6 it will do that.
Sent from my Gingervolt-ed VS910 4G using xda premium

I rooted it with adb following root.bat. I run linux and am a terminal junkie. The rooting went fine. I then dl'ed recovery-cwm-pr1.img and adb'ed it over to the sdcard, ran all the checksums, from adb and on a root terminal on the phone. Then from adb, moved the image file to block mmcblk0p14, ran checksums again from both adb and the terminal on the phone. They both checked out fine, again.
After reboot, it just wiped, no CWM. It might be a permissions problem. I see no execute bit set. Should it be?
This is a response to post #14. I meant to post this with a quote. Instead, I posted a quick reply. Sorry.

meandmine said:
I rooted it with adb following root.bat. I run linux and am a terminal junkie. The rooting went fine. I then dl'ed recovery-cwm-pr1.img and adb'ed it over to the sdcard, ran all the checksums, from adb and on a root terminal on the phone. Then from adb, moved the image file to block mmcblk0p14, ran checksums again from both adb and the terminal on the phone. They both checked out fine, again.
After reboot, it just wiped, no CWM. It might be a permissions problem. I see no execute bit set. Should it be?
Click to expand...
Click to collapse
Not a permission problem, there are a couple of files in there that have to be removed otherwise it blocks it from booting into cwm with the key press combo. You have to boot into cwm using quick boot or the reboot into recovery option in the revotoolkit menu. If you flash GingerVolt you will then have reboot and recovery in the power menu, but also will be able to enter recovery through the button combo.
You will have to push the recovery image again first though.

[Q] Can't get recovery to flash

I recently tried to install a ROM on my HTC one and it seems to have soft bricked my device. I don't seem to have a recovery anymore so I tried to flash TWRP using fastboot. But everytime I try the command flash recovery, I get an error that says cannot open recovery.img. I have searched and found a few tutorials and i seem to be doing everything right but the recovery wont flash. Any help? My phone will not boot at all. Fastboot works but thats about it. When i click reboot it just goes blank then goes to the exact same screen. When I click on recovery it does the exact same thing.

Is recovery in the same folder you open the terminal in? If so make sure to type in "fastboot flash recovery recovery.img"
Sent from my HTC One Max using Tapatalk!

Yeah. Its in the same folder. It gives me an error every time. I can't figure out why it doesn't work.
Sent from my SPH-D710 using Tapatalk

Did you happen to use the CM Installer to unlock,root, ect?
If you did you won't be able to flash any other roms or recoveries without running an RUU.

2ndaccord said:
Yeah. Its in the same folder. It gives me an error every time. I can't figure out why it doesn't work.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
what recovery are you tring to install
if it's for sprint it should be: fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
the recovery img should be in your fastboot folder
you phone in bootloader fastboot usb.

Aldo101t said:
what recovery are you tring to install
if it's for sprint it should be: fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
the recovery img should be in your fastboot folder
you phone in bootloader fastboot usb.
Click to expand...
Click to collapse
hmmmm... fastboot folder? This person needs a bit more than that, seemingly.
So, first, there is some folder (directory) in which your "fastboot" program exists -- let's call that "FastbootDir" for this discussion. Do this:
1) Download the latest TWRP (2.7.0.x), you can use mine, or the standard release, your choice: my build (with enhancements) or the standard;
2) copy that file *exactly* as it is (quit the renaming game -- fastboot does not need that -- it could care less what the file name is) to your *FastbootDir* folder;
3) Open your file explorer and browse to that same directory (your FastbootDir folder);
4) Right click in the file area and open a command terminal *as administrator*;
5) now type this in the command window:
dir openrecovery*.img
If that says "file not found" or similar -- you either failed to copy the downloaded file to that directory, or, well, you renamed it (don't do that!);
If it tells you file name, *that* is the exact file name you must enter into the flash command. Let's say you chose my build, which will say "openrecovery-m7wls-2.7.0.2-03-13-2014.img" -- then to flash that you will type:
fastboot flash recovery openrecovery-m7wls-2.7.0.2-03-13-2014.img
If on the other hand you chose the standard build from TeamWin:
fastboot flash recovery openrecovery-twrp-2.7.0.1-m7wls.img
That should do it. Report back if you have troubles.

I finally got it flashed. Thanks for all the help. I am a newb with HTC devices. I installed the ROM that I had on the device but now it won't boot up. All i get is a white HTC screen and "process com.htc.htcdialer isn't responding". I have wiped several times and tried to install 2 different roms but i never get past the HTC screen. I can get to the lock screen but as soon as I unlock it the phone just reboots and I get stuck again. Any suggestions?

2ndaccord said:
I finally got it flashed. Thanks for all the help. I am a newb with HTC devices. I installed the ROM that I had on the device but now it won't boot up. All i get is a white HTC screen and "process com.htc.htcdialer isn't responding". I have wiped several times and tried to install 2 different roms but i never get past the HTC screen. I can get to the lock screen but as soon as I unlock it the phone just reboots and I get stuck again. Any suggestions?
Click to expand...
Click to collapse
Suggest you flash a such rooted ROM just to start at a place of sanity.

Did you check all of your md5, and using your exact ROM? Are you m7spr or m7wls?
Sent from my Rezound using xda-developers app. CyanogenMod 11. S-off

M7 wls. In not sure how to check the md5 sum. I was already on the bad boys rom so I know the rom was a good download. It just won't get past the htc screen.
Sent from my SPH-D710 using Tapatalk

2ndaccord said:
I finally got it flashed. Thanks for all the help. I am a newb with HTC devices. I installed the ROM that I had on the device but now it won't boot up. All i get is a white HTC screen and "process com.htc.htcdialer isn't responding". I have wiped several times and tried to install 2 different roms but i never get past the HTC screen. I can get to the lock screen but as soon as I unlock it the phone just reboots and I get stuck again. Any suggestions?
Click to expand...
Click to collapse
Sounds like you flashed a GSM rom at one point and messed up your partitions.
I would suggest running an RUU and starting fresh.

If he tried to flash ANYTHING gsm you pretty much have to RUU... Are you trying to go GSM or stay CDMA? I would suggest viper ROM flashing in twrp 2.7.0 just to see what that does and if you can get past screen
Sent from my Rezound using xda-developers app. CyanogenMod 11. S-off

BD619 said:
Sounds like you flashed a GSM rom at one point and messed up your partitions.
I would suggest running an RUU and starting fresh.
Click to expand...
Click to collapse
Why do people do that? Lol. Just ask our sanity keeper @BD619 before running down crazy paths .

tdhite said:
Why do people do that? Lol. Just ask our sanity keeper @BD619 before running down crazy paths .
Click to expand...
Click to collapse
Not trying to sound like a jerk or a know it all but....most folks don't take the time to read the OP

BD619 said:
Not trying to sound like a jerk or a know it all but....most folks don't take the time to read the OP
Click to expand...
Click to collapse
Very, very, very, VERY true. I go through xda on my phone through my "unread" section and see how many people are asking for help, then click on it and it has a link to the same exact problem plus like a hundred others lol, but op, try viper ROM great ROM, one of my friends with the wls is using it, great ROM make sure you're flashing a wls ROM and not a spr..... I've seen posts like that to....
Sent from my Rezound using xda-developers app. CyanogenMod 11. S-off

I had to ruu back because no Rom would boot. I tried different roms but they all would get to a blank HTC screen. I could unlock the phone but the HTC screen would be there. The the HTC dialer would force close a few times then the phone would reboot. That happened on 2 different roms. Bad boys and on viper Rom. But thanks to everyone for the help.?
Sent from my HTCONE using Tapatalk

tdhite said:
hmmmm... fastboot folder? This person needs a bit more than that, seemingly.
So, first, there is some folder (directory) in which your "fastboot" program exists -- let's call that "FastbootDir" for this discussion. Do this:
1) Download the latest TWRP (2.7.0.x), you can use mine, or the standard release, your choice: my build (with enhancements) or the standard;
2) copy that file *exactly* as it is (quit the renaming game -- fastboot does not need that -- it could care less what the file name is) to your *FastbootDir* folder;
3) Open your file explorer and browse to that same directory (your FastbootDir folder);
4) Right click in the file area and open a command terminal *as administrator*;
5) now type this in the command window:
dir openrecovery*.img
If that says "file not found" or similar -- you either failed to copy the downloaded file to that directory, or, well, you renamed it (don't do that!);
If it tells you file name, *that* is the exact file name you must enter into the flash command. Let's say you chose my build, which will say "openrecovery-m7wls-2.7.0.2-03-13-2014.img" -- then to flash that you will type:
fastboot flash recovery openrecovery-m7wls-2.7.0.2-03-13-2014.img
If on the other hand you chose the standard build from TeamWin:
fastboot flash recovery openrecovery-twrp-2.7.0.1-m7wls.img
That should do it. Report back if you have troubles.
Click to expand...
Click to collapse
I have the same exact problem and applied your advices. Nothing helps. I am frustrated because I have done this before an dnow I can't get it done. If you please can help me?

nossman said:
I have the same exact problem and applied your advices. Nothing helps. I am frustrated because I have done this before an dnow I can't get it done. If you please can help me?
Click to expand...
Click to collapse
See if this helps: http://forum.xda-developers.com/showpost.php?p=55452567&postcount=527
Don't respond there -- that's a dev thread, but honestly it's pretty easy. My suspect is you don't have the SDK (fastboot, adb, etc. properly setup). The fastboot program needs to be on your PATH, or you need to open a command window ***as administrator*** and make sure you are in the directory in which fastboot exists (e.g., type "dir fastboot*.*") and if it doesn't come back with something, you're not in the correct directory.

deleted, wrong thread.

QUOTE=nossman;55476580]Thank you! I have just installed brand new ADB tools etc. rebooted . . .[/QUOTE]
First -- could you *please* go delete the post you laid down in my TWRP development thread -- I specifically asked you *not* to do that. Dev threads are not support or Q&A threads and that post takes up a bunch of space totally unnecessarily. Sigh ...
Second -- if the command fails like that it means you have the wrong path to the file you downloaded. Do a file search for openrecovery*.* starting in C:\ and use the path it finds.