Database Develop

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.

Help! I cant flash Amons recovery

Okay so i unlocked my bootloader, that went well (as if thats hard)
and then i used Modacos superboot to root, it rooted (except for some reason the super user application opens to just a black screen). After that i continued to flash the recovery so that i can flash Cyanogen. When i try to flash the recovery i keep on getting the error 'cannot load'. i've tried like 4 different recovery roms. Not sure what im doing wrong
Oh and this has been tried on 2 different computers. One win7 and one XP. both gave the same output

_-..zKiLLA..-_ said:
Okay so i unlocked my bootloader, that went well (as if thats hard)
and then i used Modacos superboot to root, it rooted (except for some reason the super user application opens to just a black screen). After that i continued to flash the recovery so that i can flash Cyanogen. When i try to flash the recovery i keep on getting the error 'cannot load'. i've tried like 4 different recovery roms. Not sure what im doing wrong
Oh and this has been tried on 2 different computers. One win7 and one XP. both gave the same output
Click to expand...
Click to collapse
what commands are you using to flash Amon_RA's recovery image? i also assume you're at the white bootloader screen when trying to flash Amon_RA's recovery image. also, to confirm root access, download the N1 Torch app and if it works, you're rooted.

Yes the screen is white. And i am using "fastboot flash recovery recovery-RA-nexus-v1.7.0-cyan.img"

Cannot load what - fastboot or the ROM .img file? Do you have fastboot-windows.exe in the same directory as the rom image?-(not necessary if fastboot command works for you)
Type fastboot devices to double check your link between pc and phone. If not check usb cable & drivers.
Make sure ur unlock is right before flashing Amon. If you've rooted then you should see an unlocked-lock image (the the google Xscreen) while booting, or the N1 torch app method as mentioned above.

_-..zKiLLA..-_ said:
Yes the screen is white. And i am using "fastboot flash recovery recovery-RA-nexus-v1.7.0-cyan.img"
Click to expand...
Click to collapse
Make sure you got to that white screen by pressing the trackball and not the volume rocker.

I renamed the recovery image to "recovery-RA-nexus-v1.7.0.img"
Code:
fastboot flash recovery recovery-RA-nexus-v1.7.0.img
Make sure you check
Code:
fastboot devices
and get your device number and also make sure you put it in the tools folder of the Android SDK

Make these steps
Boot ur phone into bootloader
1 Rename the img to recovery.img
2 Place the file in ur toolfolder where u have ur fastboot
3 Rightclik on toolfolder+Shift choose open cmd here
4 write fastboot devices to be shure u are connected
5 then write fastboot flash recovery recovery.img

hi,I have the problem too.I try many times but still stuck TRIANGLE WITH !.when I do recovery image
the screen come up "sending 'recovery"3948 kb.....ok
writing' recovery'......ok

sending 'recovery"3948 kb.....ok
writing' recovery'......ok
Click to expand...
Click to collapse
Code:
fastboot reboot

Finally got Amon_Ra's recovery to install
I started with a stock N1 with froyo
had a few stumbles along the way and lots of searching...lots and lots lol
using the how-to on the cyanogen page I went to the letter as ive never used ADB
So I installed the Latest Android SDK to get the ADB and Fastboot.
verified connection with "adb devices" command and so on
when I tried to flash amons the first time I got an error saying it couldn't open the file.
I checked to see if i had Super user with the LED flashlight app and I did not so I downloaded Super boot and it worked like a charm
tried again and got the same cannot open error.
I renamed the recovery image back to the original file name and triple checked everything else which didnt help.
at this point it was late and i was exhausted so my memory is fuzzy
but i had a few more issues and finally I installed the clock work app and installed clockwork recovery i then used that to flash amons because that is what i was familiar with from my G1 days.
I do remember I had to go into fast boot and select clear storage. I think thats what caused my N1 to hang on reboot after the ROM was flashed.
But It may have even been what caused my issues with the recovery image.

[HELP] Cannot boot or flash (remote: image update error)

So I did a full wipe and then installed Rodriguezstyle FroYo rom (http://forum.xda-developers.com/showthread.php?t=692609). It was fine but I missed too many CM features and NeXTheme.
I did a wipe, reflashed CM5.0.7.1 and then restored my nandroid (+ext). Now I cannot get the device to boot!
I can get into bootloader and thought I should replace the radio as I know the FroYo one is a problem in non-FroYo roms but while it copies ok, when installing it says FAILED (remote:image update error)
Please please help me. Give me steps to do to get back to a clean CM5.0.7.1 and I can sort the rest out!
Fastboot won't let me flash anything! I am unlocked though!

There's no need to post your question in multiple forums.
Someone will answer when they know how to help.
That said, all I can suggest is maybe trying a different radio image? Or maybe see if you can load up one of the 2.1 ROMs and deal with the radio issue once it's up and running?

Sorry, got a bit desperate
I have tried several radios, the problem is that I cannot flash anything for some reason. I cannot even flash Amon_Ra's recovery to try and get a different rom working

So even booting to fastboot (press and hold trackball during power-on) your computer is unable to connect via fastboot? So "fastboot devices" doesn't return anything?
Just booting normally, what happens? Does it get stuck on the Android bootloader screen or what? Any chance of connecting to it via adb?
I haven't broken my stuff hard yet, so I'm kinda guessing here lol. Trying to help though!

I appreciate the help, thanks.
I can get to fastboot and issue fastboot commands (fastboot devices returns the model number (?) as normal). It's just that if I try to fastboot flash recovery I get that "image update error"
I can't get as far as a recovery image to issue adb commands. When I try to boot normally, the phone vibrates once as the X comes up, then several quick vibrations which seem like some kind of error code.
Also, by way of some extra info in case it helps, the following is displayed on my bootloader:
NEXUSONE PVT SHIP S-ON
HBOOT_0.33.0012
MICROP-0b15
TOUCH PANEL-SYNT0103
Radio-4.02.02.14
Dec 17 2009,13:05:23

3Shirts said:
I appreciate the help, thanks.
I can get to fastboot and issue fastboot commands (fastboot devices returns the model number (?) as normal). It's just that if I try to fastboot flash recovery I get that "image update error"
I can't get as far as a recovery image to issue adb commands. When I try to boot normally, the phone vibrates once as the X comes up, then several quick vibrations which seem like some kind of error code.
Also, by way of some extra info in case it helps, the following is displayed on my bootloader:
NEXUSONE PVT SHIP S-ON
HBOOT_0.33.0012
MICROP-0b15
TOUCH PANEL-SYNT0103
Radio-4.02.02.14
Dec 17 2009,13:05:23
Click to expand...
Click to collapse
What is the EXACT command are you typing to flash recovery?

3Shirts said:
I appreciate the help, thanks.
I can get to fastboot and issue fastboot commands (fastboot devices returns the model number (?) as normal). It's just that if I try to fastboot flash recovery I get that "image update error"
Click to expand...
Click to collapse
Have you tried this --> http://forum.xda-developers.com/showthread.php?t=614850
It is a sticky..... Anyways, I would also try the official .zip image (PASSIMG.zip) if you can find a thread on that someplace. That loads through fastboot I believe so check it out.....
Also try "Fastboot boot recovery.img" (recovery.img being c:\PATHTOFILE) and see if it will boot into recovery that way......

martin0285 said:
Have you tried this --> http://forum.xda-developers.com/showthread.php?t=614850
It is a sticky..... Anyways, I would also try the official .zip image (PASSIMG.zip) if you can find a thread on that someplace. That loads through fastboot I believe so check it out.....
Also try "Fastboot boot recovery.img" (recovery.img being c:\PATHTOFILE) and see if it will boot into recovery that way......
Click to expand...
Click to collapse
The command I am typing is: fastboot flash recovery recovery.img <- this being the name of the Amon_Ra recovery image file located in the same folder I am in when issuing the command
I have tried that post's instructions but I get "remote: not allowed" when trying to erase userdata and I was getting "remote: image update error" when trying to do any of the flash commands. I say WAS becasue I have just tried sticking the original PASSIMG on sd card and updating that way and, while it gave me partition update errors on boot and system, it has changed something because now when I do the fastboot flash commands I get a different error: "remote: signature verify fail"
I know the files are not corrupt though as I have checked the md5s
EDIT: I also tried doing a fastboot boot to the recovery image but it loads to the X then I get prompted by windows to install a Qualcomm CDMA driver which it can't find?!!

the first case of semi-brick?
like on the G1

JKshowman said:
the first case of semi-brick?
like on the G1
Click to expand...
Click to collapse
Don't say that

Thread Moved.

3Shirts said:
Don't say that
Click to expand...
Click to collapse
no, its just i had a semi-brick problem on the G1 and i solved it quickly enough by reflashing a recovery, but in this case.........
try to see if other flashboot commands work

3Shirts said:
Don't say that
Click to expand...
Click to collapse
Try downloading the recovery image again. It could be corrupt. Also, I am assuming you unlocked your phone first.

No I have confirmed the MD5s on everything I downloaded including the recovery image. Yeah I've been unlocked and rooted from day one.

Does anyone have an hboot image I can try flashing

Well it looks like i'm f***ed then.
I can't adb and can't boot to any kind of terminal so with only fastboot available, and that not allowing me to flash much, I can't fix this
I guess it's off to HTC, see what hey can/will do and if that fails... no more Nexus One
EDIT: Booked it in with HTC for collection tomorrow afternoon (UK time). I'll update again to provide a definitive answer to the question: What is the price for effing up your Nexus One through your own stupidity

The command I am typing is: fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I realize this, but fastboot BOOT recovery.Img is a different command to just "boot" the image and not "flash" permanently... worth a shot....

martin0285 said:
I realize this, but fastboot BOOT recovery.Img is a different command to just "boot" the image and not "flash" permanently... worth a shot....
Click to expand...
Click to collapse
I have tried that too. It just sits at the X. Doesn't get into recovery

3Shirts said:
I have tried that too. It just sits at the X. Doesn't get into recovery
Click to expand...
Click to collapse
****ty, well good luck with HTC.....

Just to update for anyone interested in the process:
I called HTC on 2nd June and booked collection for the following afternoon.
Picked up by courier (I packed it in original box and jiffy bag with battery but no SD or Sim cards) at 2pm on 3rd June
Received confirmation of arrival with HTC (Milton Keynes as I'm in the UK) at 1.43pm on 4th June
Next step is to wait for a call regarding the repair that can be done and associated cost.

Need help, HTC DREAM

I was trying to do the post 911 rogers root on my htc phone, i got to the point where I Amon_ra's 1.7 recovery booted but then the home button wouldn't respone which is weird as it was used to boot into recovery.
after this I researched a bit and found that an eailer version of Amon_ra's recovery used the "Send" key instead of home, flashed that on and booted into it however it still asked me for "Home" to comfirm.
I then downloaded clockworks recovery and flashed it onto my phone but now the phone is stuck(waited 3 hours) at the ROGERS boot screen. I can boot into fastboot and my computer sees it as:
"list of device
HLXXXXXXXXXXXXXX fastboot"
x=numbers/letters
but whenever I try to do a fastboot command i get an error stating that remote is not allowed.
I am worried that this phone super derpped on me

What radio and SPL do you have? It will say in fastboot mode on the device. Also, can you still get into the ROM?

thanks for the reply the spl and radio are:
spl: 1.33.0010(?)
radio: 3.22.26.17
heres what it all says
"DREAM PVT 32B SHIP S-On d
HBOOT-1.33.0010 (DREA21000)
CPLD-4
RADIO-3.22.26.17
Jun 2 2009, 21:33:16"
no I can't get into the system rom, it is stuck at the bootspalsh screen.

You have a 3.xx (EBI1) radio but clockwork recovery only works with 2.xx (EBI0) radios.
I don't know if this will work but give it a shot:
1) Download: orange-1.58.73.2.nbh (MD5: aca4dee0c1ece7e9773f2ecbdfbba7c0) (mirror)
2) enter fastboot and run 'fastboot flash nbh orange-1.58.73.2.nbh'
3) wait for the entire nbh to flash
4) boot into the bootloader again (it will be an engineering SPL 1.42.2000)
5) You can now re-flash the radio/hboot/recovery via fastboot that you wish to have installed.
Click to expand...
Click to collapse

I downloaded the NBH file but I can't send the file to the phone it gives me this
nbh orange-1.58.73.2.nbh
sending 'nbh' (88683 KB)... FAILED (remote: not allow)
finished. total time: 0.005s
Click to expand...
Click to collapse
EDIT*: After following this guide http://wiki.cyanogenmod.com/index.php?title=Full_Downgrade_Guide_-_HTC_Dream I can now boot past the Rogers screen but its followed by a caution triangle. Recovery doesn't work "home"+power.
EDIT**: Further inspection i can get into recovery via atl+L at the triangle screen the load then rogers rom so I can make calls. The "home button" doesn't work so i can't flash or do anything in recovery mode as it ask for the "home" key to comfirm. Also home key is useless in normal boot(doesn't return me to home) which is wierd as my phone has never been dropped or water damaged, not even a scratch. Another thing since home key is now defucnt I can't reboot my phone or it will give me the error splash screen

Thats great news that you can get into recovery. You should try to get an unlocked spl before you do anything else. It looks like the home button not working is a hardware problem. If you feel comfortable doing it you could open the device because something might just not be contacting properly. You can find a service manual if you search for it.
You could try to use flash_image to flash img files in recovery through adb without the need for the home button.
http://wiki.cyanogenmod.com/index.php?title=Flash_image
Be sure to update to the latest radio before flashing your spl. This is very important!!!

[Q] Trying to flash drunk- failed. Now what?

Ok guys, so I was trying to flash the software on my Sprint HTC One with a custom one, while drunk. Needless to say it didn't work. I suspect that chrome f*cked up downloading the rom, because it was only 800mb, and should have been about 1gb. Now, the phone isn't working. When I try to turn it on it shows the htc logo and then boots up in fastboot. Fastboot still receives cmd commands, but I still havent found a way to flash an RUU on it. Tryed with twrp as a recovery- cant mount to computer. Tryed sending the file to phone through cmd- some error about not working radio came through. I'm cutting corners explayning all the methods I tryed to make it work, but there were a lot of them and I dont remember all. I have flashed the boot and the recovery back to the stock ones, bootloader IS unlocked. Phone vertion (as shown in the bootloader screen):
***TAMPERED***
***UNLOCKED***
M7_WLS PVT SHIP S-ON RH
HBOOT- 1.44.0000
OpenDSP-v31.120.274.0617
eMMC- boot
Jul 5 2013,17:19:22:-1
My question is how do I return it to stock condition (or unlocked to all networks if possible)? Please, I've been trying to fix it on my own for over a week now, and am getting desperate. If possible please give links to step-by-step tutorials and/or files I'll need. Thank you in advance.
PS.: Also, for some reason my computer does fails to install the HTC MTP device driver. Could it be from that, and if it is- will using a different computer solve the problem (tryed a million times to fix that as well- no luck)?

drobalqk said:
Ok guys, so I was trying to flash the software on my Sprint HTC One with a custom one, while drunk. Needless to say it didn't work. I suspect that chrome f*cked up downloading the rom, because it was only 800mb, and should have been about 1gb. Now, the phone isn't working. When I try to turn it on it shows the htc logo and then boots up in fastboot. Fastboot still receives cmd commands, but I still havent found a way to flash an RUU on it. Tryed with twrp as a recovery- cant mount to computer. Tryed sending the file to phone through cmd- some error about not working radio came through. I'm cutting corners explayning all the methods I tryed to make it work, but there were a lot of them and I dont remember all. I have flashed the boot and the recovery back to the stock ones, bootloader IS unlocked. Phone vertion (as shown in the bootloader screen):
***TAMPERED***
***UNLOCKED***
M7_WLS PVT SHIP S-ON RH
HBOOT- 1.44.0000
OpenDSP-v31.120.274.0617
eMMC- boot
Jul 5 2013,17:19:22:-1
My question is how do I return it to stock condition (or unlocked to all networks if possible)? Please, I've been trying to fix it on my own for over a week now, and am getting desperate. If possible please give links to step-by-step tutorials and/or files I'll need. Thank you in advance.
Click to expand...
Click to collapse
It sounds like you have the same problem that a lot of people are getting into around here, myself included. You tried to flash a non-cdma compatible rom onto your phone.
There are numerous postings about how to fix this, however, it depends on the condition of your phone which step you take.
If you have recovery installed and you have access to recovery you will take different steps than if you only have access to fastboot.
You need to have a recovery installed and you need to relock your phone to fastboot ruu. Once that is done you basically start from scratch and unlick your phone again and then you can reinstall the recovery and then flash the correct cdma compatible roms.

MrFixit007 said:
It sounds like you have the same problem that a lot of people are getting into around here, myself included. You tried to flash a non-cdma compatible rom onto your phone.
There are numerous postings about how to fix this, however, it depends on the condition of your phone which step you take.
If you have recovery installed and you have access to recovery you will take different steps than if you only have access to fastboot.
You need to have a recovery installed and you need to relock your phone to fastboot ruu. Once that is done you basically start from scratch and unlick your phone again and then you can reinstall the recovery and then flash the correct cdma compatible roms.
Click to expand...
Click to collapse
The recovery I can install in a matter of seconds, same with relocking. I have the lastest vertions on both TWRP and Clockwork. Which one do I install and how do I proceed after? Thank you

drobalqk said:
The recovery I can install in a matter of seconds, same with relocking. I have the lastest vertions on both TWRP and Clockwork. Which one do I install and how do I proceed after? Thank you
Click to expand...
Click to collapse
do you have adb access? or only fastboot access?

MrFixit007 said:
do you have adb access? or only fastboot access?
Click to expand...
Click to collapse
adb- Im not sure. How do I check? Fastboot- I think so. It accepts my cmd commands for flashing recovery and rom (although when I tryed to flash rom it failed).

drobalqk said:
adb- Im not sure. How do I check? Fastboot- I think so. It accepts my cmd commands for flashing recovery and rom (although when I tryed to flash rom it failed).
Click to expand...
Click to collapse
In your command window in the same directory you run fastboot from, you should be able to run adb.
The easiest way to check is to type: adb devices
this should return a value if you are booted into recovery.
it will give you nothing if you aren't in recovery.
if you cannot get into recovery then you need to make sure your phone is unlocked and then fastboot a recovery onto your phone.

MrFixit007 said:
In your command window in the same directory you run fastboot from, you should be able to run adb.
The easiest way to check is to type: adb devices
this should return a value if you are booted into recovery.
it will give you nothing if you aren't in recovery.
if you cannot get into recovery then you need to make sure your phone is unlocked and then fastboot a recovery onto your phone.
Click to expand...
Click to collapse
I currently have the stock recovery flashed on it. Is that one going to work or should I flash TWRP/ Clockwork?

drobalqk said:
I currently have the stock recovery flashed on it. Is that one going to work or should I flash TWRP/ Clockwork?
Click to expand...
Click to collapse
as long as you can boot into recovery, it should work. i personally favor twrp, but any recovery should work.
try out some adb commands and see.
adb sevices
adb shell
if you get anywhere with those while booted into recovery you should be ok.

MrFixit007 said:
as long as you can boot into recovery, it should work. i personally favor twrp, but any recovery should work.
try out some adb commands and see.
adb sevices
adb shell
if you get anywhere with those while booted into recovery you should be ok.
Click to expand...
Click to collapse
adb devices returns no values
adb services returns big list of commands
adb shell returns error device not found.
I'm into TWRP v.2.6.1.0 start screen.

drobalqk said:
adb devices returns no values
adb services returns big list of commands
adb shell returns error device not found.
I'm into TWRP v.2.6.1.0 start screen.
Click to expand...
Click to collapse
did those adb errors or no devices found occur while your phone was showing the twrp start screen?
if yes, then we need to reboot into the bootloader-- to fastboot.
if no then try adb shell again while showing the twrp start screen.

MrFixit007 said:
did those adb errors or no devices found occur while your phone was showing the twrp start screen?
if yes, then we need to reboot into the bootloader-- to fastboot.
if no then try adb shell again while showing the twrp start screen.
Click to expand...
Click to collapse
Yes, I was IN TWRP recovery home screen. I'll try the commands in fastboot as soon as I come back from work. Thank you for the time you spend trying to help me, I do very much apreciate it.

drobalqk said:
Yes, I was IN TWRP recovery home screen. I'll try the commands in fastboot as soon as I come back from work. Thank you for the time you spend trying to help me, I do very much apreciate it.
Click to expand...
Click to collapse
It seems like you need to fastboot flash recovery onto your phone again.
Here are the steps as I think they should work to get you back up and running.
**Make sure your phone is unlocked. (it should display ***UNLOCKED*** at the top of the bootloader screen)
if you ARE unlocked do the following(+++see below if you are NOT unlocked+++)
1. from bootloader select fastboot - connect phone to computer. fastboot should change to fastboot usb when you have a good connection.
on your computer:
2. open a command window and navigate to the folder where adb and fastboot are located
3. type in "fastboot flash recovery xxxxxxxx.zip" where xxxxxxxx.zip is the name of recovery zip file without quotes. Make sure you download a good copy appropriate for your phone. I would use this one: http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.6.1.0-m7wls.img
4. type fastboot reboot
on your phone:
5. once it is rebooted and in bootloader select recovery and boot into recovery.
on your computer:
6. once your phone shows recovery main screen then typeat the command prompt: adb shell
7. no matter what the prompt looks like type: echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
8. no matter if it errors or not type: adb reboot bootloader
9. type: fastboot oem lock
10. type: fastboot oem rebootRUU
11. type fastboot flash zip xxxxxxxxxxxxx.zip where xxxxxxxxxxxxx.zip is the name of the ruu.zip file. i would use this one: http://www.androidfilehost.com/?fid=22926241640219526
12 reboot your phone once that is successful!! If you get the "flush image again immideately" error message then repeat step 11. then reboot your phone.
you should now be running a stock sprint phone.
you can now unlock your phone again and reinstall a recovery.
to unlock your phone the second time:
13. boot your phone into bootloader then go to fastboot - make sure the phone is connected to the computer
14. on your computer type in: fastboot flash unlocktoken Unlock_code.bin
15. on your phone select unlock with volume rocker and press power once unlock is selected
16. on computer type: fastboot flash recovery xxxxxxxxx.zip where xxxxxxxxxx.zip is the same recovery zip file we used above in step 3
17. reboot your phone and you are now unlocked and you have a custom recovery installed and you can download a CDMA compatible rom to your phone and install it with the recovery like normal. or you can continue to run stock.
MAKE SURE YOU ONLY DOWNLOAD CDMA COMPATIBLE ROMS FROM THE SPRINT HTC ONE FORUMS.
enjoii!!
+++if you are NOT unlocked+++
try the following:
step 13
step 14
step 15
step 16
step 4
step 5
step 6-17
make sure you complete all the way through 17 after you do step 6. good luck and let me know what your results are.

MrFixit007 said:
It seems like you need to fastboot flash recovery onto your phone again.
Here are the steps as I think they should work to get you back up and running.
**Make sure your phone is unlocked. (it should display ***UNLOCKED*** at the top of the bootloader screen)
if you ARE unlocked do the following(+++see below if you are NOT unlocked+++)
1. from bootloader select fastboot - connect phone to computer. fastboot should change to fastboot usb when you have a good connection.
on your computer:
2. open a command window and navigate to the folder where adb and fastboot are located
3. type in "fastboot flash recovery xxxxxxxx.zip" where xxxxxxxx.zip is the name of recovery zip file without quotes. Make sure you download a good copy appropriate for your phone. I would use this one: http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.6.1.0-m7wls.img
4. type fastboot reboot
on your phone:
5. once it is rebooted and in bootloader select recovery and boot into recovery.
on your computer:
6. once your phone shows recovery main screen then typeat the command prompt: adb shell
7. no matter what the prompt looks like type: echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
8. no matter if it errors or not type: adb reboot bootloader
9. type: fastboot oem lock
10. type: fastboot oem rebootRUU
11. type fastboot flash zip xxxxxxxxxxxxx.zip where xxxxxxxxxxxxx.zip is the name of the ruu.zip file. i would use this one: http://www.androidfilehost.com/?fid=22926241640219526
12 reboot your phone once that is successful!! If you get the "flush image again immideately" error message then repeat step 11. then reboot your phone.
you should now be running a stock sprint phone.
you can now unlock your phone again and reinstall a recovery.
to unlock your phone the second time:
13. boot your phone into bootloader then go to fastboot - make sure the phone is connected to the computer
14. on your computer type in: fastboot flash unlocktoken Unlock_code.bin
15. on your phone select unlock with volume rocker and press power once unlock is selected
16. on computer type: fastboot flash recovery xxxxxxxxx.zip where xxxxxxxxxx.zip is the same recovery zip file we used above in step 3
17. reboot your phone and you are now unlocked and you have a custom recovery installed and you can download a CDMA compatible rom to your phone and install it with the recovery like normal. or you can continue to run stock.
MAKE SURE YOU ONLY DOWNLOAD CDMA COMPATIBLE ROMS FROM THE SPRINT HTC ONE FORUMS.
enjoii!!
+++if you are NOT unlocked+++
try the following:
step 13
step 14
step 15
step 16
step 4
step 5
step 6-17
make sure you complete all the way through 17 after you do step 6. good luck and let me know what your results are.
Click to expand...
Click to collapse
Nope, adb still doesn't work. Could it be something wrong with the drivers my computer installs? Because when I'm in recovery my computer detects the device in "Other Devices" as "M7WLS", and I don't have a driver for that and neither does microsoft update. Any suggestions?

drobalqk said:
Nope, adb still doesn't work. Could it be something wrong with the drivers my computer installs? Because when I'm in recovery my computer detects the device in "Other Devices" as "M7WLS", and I don't have a driver for that and neither does microsoft update. Any suggestions?
Click to expand...
Click to collapse
Did you install HTC Sync or did you install the naked drivers from here?
Otherwise, where in the process did you get stopped?
EDIT: You can always PM me your teamviewer info and I can work on it.