Database Develop

Help!!..i lost my recovery(i think) and i don't have a rom!!!!

hi
i need help on getting a rom on my g1(any rom at all)
i lost my recovery or i think i did..wot happened was i was changing recovery and i was moving from RA's to Cyanogen's recovery...i moved from RA's to RA's b4 and i did it by going to console in recovery then typing "mount -a" then "flash_image recovery /sdcard/(the name of the recovery)" so i tryed to get cm recovery by doing the same thing(btw it was a .zip if thats any help)but i got the "error no space on device" or something like that...then i removed the battery to get out of console (like i always do coz i don't know any other any) but then when i tryed to go to recovery mode again i just get the T-Mobile G1 screen then a black screen comes but no recovery...what now i need a new recovery to get a rom...i searched and got something called fastboot but i don't know wot it is when i press power n back i go to screen with 3 lil androids on the bottom(i believe this is fastboot mode)...can i use that to get a new recovery?any help pls

mazinxd said:
hi
i need help on getting a rom on my g1(any rom at all)
i lost my recovery or i think i did..wot happened was i was changing recovery and i was moving from RA's to Cyanogen's recovery...i moved from RA's to RA's b4 and i did it by going to console in recovery then typing "mount -a" then "flash_image recovery /sdcard/(the name of the recovery)" so i tryed to get cm recovery by doing the same thing(btw it was a .zip if thats any help)but i got the "error no space on device" or something like that...then i removed the battery to get out of console (like i always do coz i don't know any other any) but then when i tryed to go to recovery mode again i just get the T-Mobile G1 screen then a black screen comes but no recovery...what now i need a new recovery to get a rom...i searched and got something called fastboot but i don't know wot it is when i press power n back i go to screen with 3 lil androids on the bottom(i believe this is fastboot mode)...can i use that to get a new recovery?any help pls
Click to expand...
Click to collapse
You obiously don't know what the Q&A section is either.
But anyways, it was a zip? If it was then that wasn't the recovery image, the recovery image is a .img file. Did you try extracting the zip?

no...but now i just wana get a recovery..any so i can flash a rom

mazinxd said:
no...but now i just wana get a recovery..any so i can flash a rom
Click to expand...
Click to collapse
even if you borked your recovery you should still be able to get into SPL. reboot your phone with camera+power, after it finishes checking, press "back" button to go into hboot, then connect your phone, and fastboot flash recovery recovery.img (make sure you already extracted it). You should be good to go

when i connect my mobile to the pc its not recognize,setup wizard come's up and i can't install the software drives(did i tell u i'm a noop and all i know is how to flash roms using my g1 mainly)

how do i make it reconzie my g1? and were do i typ flash recovery recovery.img

Have you installed the android sdk on your pc? If not, search the developement forum for it or do a google search for android sdk.

mazinxd said:
hi
i need help on getting a rom on my g1(any rom at all)
i lost my recovery or i think i did..wot happened was i was changing recovery and i was moving from RA's to Cyanogen's recovery...i moved from RA's to RA's b4 and i did it by going to console in recovery then typing "mount -a" then "flash_image recovery /sdcard/(the name of the recovery)" so i tryed to get cm recovery by doing the same thing(btw it was a .zip if thats any help)but i got the "error no space on device" or something like that...then i removed the battery to get out of console (like i always do coz i don't know any other any) but then when i tryed to go to recovery mode again i just get the T-Mobile G1 screen then a black screen comes but no recovery...what now i need a new recovery to get a rom...i searched and got something called fastboot but i don't know wot it is when i press power n back i go to screen with 3 lil androids on the bottom(i believe this is fastboot mode)...can i use that to get a new recovery?any help pls
Click to expand...
Click to collapse
This is excatly the reason you should read,research and always follow the directions.
There are plenty of tutorials on how to use fastboot here on xda so research.read and follow the directions and you will be fine

Here is what you need to do.
1) Follow these instructions word for word, step by step
http://forum.xda-developers.com/showthread.php?t=502010
2) Now you should have adb installed. With adb you can plug your phone into your pc through USB and use command lines to manipulate your phone. To use commands in windows go to start, run and type cmd, enter
3) Now if it worked correctly you should have your phone plugged in and type adb remount. If it successfully mounted then adb is working.
4) now unzip Ra's recovery image and rename it to recovery.img (for simplicity) and place it on your desktop
5) now with your phone plugged into the pc power down the phone and reboot, before it starts up hold the camera button. You should see some droids on skateboards.
6) Now press the back button
7) now go to the cmd as I mentioned earlier and type: cd desktop
8) now type fastboot flash recovery recovery.img when it is done type adb shell reboot and your phone will reboot.
9)before it boots up hold the home button and if you did everything correctly you should be in Ra's recovery.
from the recovery you can always hold call, menu, end to reboot instead of pulling the battery.
Good luck. I suggest you flash a rom to get back up and going, and then spend a few weeks reading about everything android that you can find on xda before you mess with it anymore. In the future you probably won't find anyone else willing to give you instructions like this, so I would search and read ALOT before posting a bunch of how to messages....

thanx
bhilgeman said:
Here is what you need to do.
1) Follow these instructions word for word, step by step
http://forum.xda-developers.com/showthread.php?t=502010
2) Now you should have adb installed. With adb you can plug your phone into your pc through USB and use command lines to manipulate your phone. To use commands in windows go to start, run and type cmd, enter
3) Now if it worked correctly you should have your phone plugged in and type adb remount. If it successfully mounted then adb is working.
4) now unzip Ra's recovery image and rename it to recovery.img (for simplicity) and place it on your desktop
5) now with your phone plugged into the pc power down the phone and reboot, before it starts up hold the camera button. You should see some droids on skateboards.
6) Now press the back button
7) now go to the cmd as I mentioned earlier and type: cd desktop
8) now type fastboot flash recovery recovery.img when it is done type adb shell reboot and your phone will reboot.
9)before it boots up hold the home button and if you did everything correctly you should be in Ra's recovery.
from the recovery you can always hold call, menu, end to reboot instead of pulling the battery.
Good luck. I suggest you flash a rom to get back up and going, and then spend a few weeks reading about everything android that you can find on xda before you mess with it anymore. In the future you probably won't find anyone else willing to give you instructions like this, so I would search and read ALOT before posting a bunch of how to messages....
Click to expand...
Click to collapse
thanx alot man ryt now its late here so i'll do it 2moro...thanx again..btw i love ur moto
edit:wait i can't turn on my g1 so i can't turn on debug mode...will that be a prob

mazinxd said:
thanx alot man ryt now its late here so i'll do it 2moro...thanx again..btw i love ur moto
edit:wait i can't turn on my g1 so i can't turn on debug mode...will that be a prob
Click to expand...
Click to collapse
no that wont be a problem

wots
mv ~/Desktop/sdk/tools/adb /usr/bin/adb abd
and
cd ~/Phone/tools/android-sdk/tools ???? sorry don't speak codes?

Completely confused with upgrade progress.. help please.

Hey all, completely lost as to where I am with my g1 haha, let me explain:
I installed v4.2.15.1 cyanogen mod a few months ago.
Then today I wanted to try and upgrade it, or just reset to standard android, didn't mind.
So I pressed camera/power button, and then installed the DREAIMG.nbh as I guessed this would reset it to RC7 (Which it did).
Then I tried gaining root access through telnetd, then using telnet to try and use a new recovery.img... this is where my problem starts.
I typed: "flash_image recovery /sdcard/recovery.img" (recovery-RA-dream-v1.7.0.img or better for CM5) and got a file not found error.
Tried it a number of different ways, but just wouldn't work.
Then tried booting into recovery mode (using home and power) but just got a white triangle/orange !.
From here I have no clue what to do, I'm just stumped as I can't use the recovery mode, and can't seem to do anything in telnet?
My phone is still useable, just stuck with android 1.0...
Any help please how i can either just get it back to a completely standard 1.5, or the newest cyanogen mod ?
P.s, this is what my about phone status are:
model number: T-mobile G1
firmware version: 1.0
baseband version: 62.33.20.08U_1.22.12.29
kernel version: 2.6.25-01843-gfea26b0android-build(at symbol)apa27 #6
build number; kila_uk-user 1.0 TC5-RC7 112931 ota-rel-keys,release-keys

Try to fastboot it. The triangle screen is the stock recovery.
Btw, why would you unroot just to install CM5?

r3s-rt said:
Try to fastboot it. The triangle screen is the stock recovery.
Btw, why would you unroot just to install CM5?
Click to expand...
Click to collapse
Will give the fastboot a go.
And uhh.. not sure why I "unrooted" it really, did this as a spur of the moment thing, and from what I read you couldn't upgrade directly from 4.x cyan to a 5 version :/
Thanks for the help so far though .

Wow, not a clue where to start with this fastboot thing, think I'll have to wait till tomorrow when I can have a proper sit down and do it.

Wigster said:
Will give the fastboot a go.
And uhh.. not sure why I "unrooted" it really, did this as a spur of the moment thing, and from what I read you couldn't upgrade directly from 4.x cyan to a 5 version :/
Thanks for the help so far though .
Click to expand...
Click to collapse
Yes, you can directly update with nothing more than a simple wipe and reflash.
Wigster said:
Wow, not a clue where to start with this fastboot thing, think I'll have to wait till tomorrow when I can have a proper sit down and do it.
Click to expand...
Click to collapse
Well, when fastbooting recovery, about the worse I've ever pulled off is fastbooting the H recovery instead of the G recovery (I'm on a myTouch) and had to fo back and reflash the G recovery to be able to get into recovery. Not to mention its a quick hop from bootloader to recovery to see if it worked and doesn't require a working ROM.

I need a rooted phone for fastboot though, do I not? and as I couldn't load the recovery, I do not think my phone is rooted?

Wigster said:
I typed: "flash_image recovery /sdcard/recovery.img" (recovery-RA-dream-v1.7.0.img or better for CM5) and got a file not found error.
Click to expand...
Click to collapse
I don't want to insult your intelligence, but you did place the file on the root of the sdcard and rename it to recovery.img didn't you..? If you didn't rename it, you'd obviously have to type "flash_image recovery /sdcard/recovery-RA-dream-v1.7.0.img"

goldenarmZ said:
I don't want to insult your intelligence, but you did place the file on the root of the sdcard and rename it to recovery.img didn't you..? If you didn't rename it, you'd obviously have to type "flash_image recovery /sdcard/recovery-RA-dream-v1.7.0.img"
Click to expand...
Click to collapse
Yes I did rename it, and checked and double checked, even reformatted card and tried again, but to no avail.
Thanks for asking though .

Was the sd definitely mounted? If you didn't unmount it from the PC after copying the file, it wouldn't be accessible to android..

goldenarmZ said:
Was the sd definitely mounted? If you didn't unmount it from the PC after copying the file, it wouldn't be accessible to android..
Click to expand...
Click to collapse
Yup, just double checked says:
"error opening /sdcard/recovery.img: No such file or directory"
Also, when I try "su", it says: "su:not found".
Utterly baffled .

Wigster said:
Yup, just double checked says:
"error opening /sdcard/recovery.img: No such file or directory"
Also, when I try "su", it says: "su:not found".
Utterly baffled .
Click to expand...
Click to collapse
Sounds to me exactly like the sdcard isn't mounted.
Mounting has to do with being joined with the running filesystem.
Provide the output of "mount".
As for fastboot... you will need to install the SPL 0.95.3000, or even better 1.33.2003 (that ends in a *THREE* --- very important).

Wigster said:
Will give the fastboot a go.
And uhh.. not sure why I "unrooted" it really, did this as a spur of the moment thing, and from what I read you couldn't upgrade directly from 4.x cyan to a 5 version :/
Thanks for the help so far though .
Click to expand...
Click to collapse
I lol'd at that part.

Thinking now that possibly my sdcard is b0rked somehow. My phone can see it and everything and I can read/write on my pc to it. But whatever I try the phone just keeps saying "error opening ########: No such file or directory" (Where ###= file name)

FAIL.
I renamed recovery.img, literally "recovery.img" and obviously it didn't need the .img tag in the filename.
Please disregard/lock this thread .

[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

[Q] Bricked phone?

I think I may have bricked my phone. It's a rooted htc hero cdma. I'm running cyogenmod on it and it was working fine, until using metamorph to apply some changes to the theme.
I went to reboot, and it now it won't load past the htc screen. Even when i try the key combination to put it into recover mode. I didn't install a nandroid backup, and i'd be fine with just completely wiping my phone. can someone please help me?

Have you tried flashing the ROM back over itself without wiping? Try that first, and if that won't work, do a full format and reflash the ROM and you should be good to go.
And just an FYI, you really can't fully brick your phone by flashing a ROM or theme. You can always get it back.

Do what ranger suggested.
To elaborate, I *think* as long as your phone turns on, it is not bricked. Specifically, as long as you can boot to recovery you can do whatever you need to do, be it make fixes or start from scratch again. (I think even if you can't boot to recovery, but it turns on, you can run the RUU ). The only way to brick is to flash a wrong/corrupt radio or anything below the radio level.

Wipe then reboot and wait. When you change the framework, initial boot takes longer.
Sent from my HERO200 using XDA Premium App

I can't even get to the recovery mode screen. it'll only take me to where i can select hboot, fastboot, or wipe. nothing else will load up past that.

What key combination are you using? Hold home then depress end key/power key until phone vibrates.
Sent from my HERO200 using XDA Premium App

Load the fast boot ruu flash
Done
zbach said:
I can't even get to the recovery mode screen. it'll only take me to where i can select hboot, fastboot, or wipe. nothing else will load up past that.
Click to expand...
Click to collapse
Sent from my HTC Hero CDMA using XDA App

mahalocat said:
Load the fast boot ruu flash
Done
Sent from my HTC Hero CDMA using XDA App
Click to expand...
Click to collapse
I can't select that option. Sorry for being kind of new at this, it just loads a bunch of green letters down really quick, telling me it can't find HERCIMG.zip/HERCDIAG.zip files. under that, it says no image or wrong image?

zbach said:
I can't select that option. Sorry for being kind of new at this, it just loads a bunch of green letters down really quick, telling me it can't find HERCIMG.zip/HERCDIAG.zip files. under that, it says no image or wrong image?
Click to expand...
Click to collapse
I am guessing you're not s-off, try this:
http://forum.xda-developers.com/showthread.php?t=958968

il Duce said:
I am guessing you're not s-off, try this:
http://forum.xda-developers.com/showthread.php?t=958968
Click to expand...
Click to collapse
I don't see the command to run "fastboot oem rebootRUU"

zbach said:
I don't see the command to run "fastboot oem rebootRUU"
Click to expand...
Click to collapse
It's a cmd prompt for windows. Open your command prompt from windows, with the phone plugged in usb, and then follow the steps in the OP of that thread.

il Duce said:
It's a cmd prompt for windows. Open your command prompt from windows, with the phone plugged in usb, and then follow the steps in the OP of that thread.
Click to expand...
Click to collapse
it keeps telling me fastboot is an unrecognized command. i have to be doing something wrong here.

zbach said:
it keeps telling me fastboot is an unrecognized command. i have to be doing something wrong here.
Click to expand...
Click to collapse
did you do the adb command first, like it says?

il Duce said:
did you do the adb command first, like it says?
Click to expand...
Click to collapse
yeah, it won't recognize that either. i'm selecting the right path to my C drive too. the driver just isnt recognized :/

You have to go further than just the C drive you have to specify the path all the way to the android-sdk-windows directory. If your on Vista, find the folder, hold the shift key and right click. Then select open a command line here.
EDIT: Yeah you need the drivers installed as well.
I had this happen to me a week ago. Luckily the phone rebooted and I was able to re-flash another recovery using the terminal emulator.

wild1z said:
You have to go further than just the C drive you have to specify the path all the way to the android-sdk-windows directory. If your on Vista, find the folder, hold the shift key and right click. Then select open a command line here.
EDIT: Yeah you need the drivers installed as well.
I had this happen to me a week ago. Luckily the phone rebooted and I was able to re-flash another recovery using the terminal emulator.
Click to expand...
Click to collapse
okay, i'm in now. i'm on the rebootRUU black and silver screen on my phone, but when i go to flash another .zip file, it says can't upload. do i need to download one from somewhere, or place it in a different folder?
I'm on my computer working through my command prompt by the way.

zbach said:
okay, i'm in now. i'm on the rebootRUU black and silver screen on my phone, but when i go to flash another .zip file, it says can't upload. do i need to download one from somewhere, or place it in a different folder?
I'm on my computer working through my command prompt by the way.
Click to expand...
Click to collapse
I've never actually done this fyi, but I think you need the RUU from htc.com, it would probably be under support, then hero cdma? DL that, and input the command "fastboot flash zip correctnameofhtcRUU.zip" in your cmd.

okay, i found and am currently downloading the file. so i should just have to root it to my SD, then flash it, right?
I'm really hoping this works.

il Duce said:
I've never actually done this fyi, but I think you need the RUU from htc.com, it would probably be under support, then hero cdma? DL that, and input the command "fastboot flash zip correctnameofhtcRUU.zip" in your cmd.
Click to expand...
Click to collapse
still nothing. it only tells me its and error, and cannot load the .zip file.

zbach said:
still nothing. it only tells me its and error, and cannot load the .zip file.
Click to expand...
Click to collapse
I don't know where the file should be located, but your posts in the other thread will yield better answers, jason knows the way better than me, given he started the thread. Wait for his response. I assume the error has something to do with where you have the ruu and what path you need to specify in the cmd. Wish I could be of more help. Once you fix it and get back to rooted and such, I HIGHLY recommend you get s-off, its basically like idiot-proofing your phone (no offense) so you can fix anything.
sent from a series of tubes.

TWRP 2.6 [stock on "swipe to unlock" in recovery]

I went to GooManager and downloaded the new version of TWRP. When I reboot to recovery my phone gets stuck on "swipe to unlock" and doesn't let me do anything but to restart my phone on fastboot. I can't flash any ROMs
Can someone please help me? Thanks in advanced. :crying:

chamo311 said:
I went to GooManager and downloaded the new version of TWRP. When I reboot to recovery my phone gets stuck on "swipe to unlock" and doesn't let me do anything but to restart my phone on fastboot. I can't flash any ROMs
Can someone please help me? Thanks in advanced. :crying:
Click to expand...
Click to collapse
did you install the correct version for the htc one sprint(wls)(spr)

Aldo101t said:
did you install the correct version for the htc one sprint(wls)(spr)
Click to expand...
Click to collapse
I was using the previous version (2.5) just fine and just went to GooManager and I assume that GooManager will download the right for me.
I opened GooManager and click on Menu then Install OpenRecoveryScript and then I manually rebooted to recovery once the download finished. And that's when I get stuck on "swipe to unlock"
Filename was "openrecovery-twrp-2.6.0.0-m7wls.img"

chamo311 said:
I was using the previous version (2.5) just fine and just went to GooManager and I assume that GooManager will download the right for me.
I opened GooManager and click on Menu then Install OpenRecoveryScript and then I manually rebooted to recovery once the download finished. And that's when I get stuck on "swipe to unlock"
Filename was "openrecovery-twrp-2.6.0.0-m7wls.img"
Click to expand...
Click to collapse
well, thats the right one, i would suggest that you manually download the file and install using adb fastboot.

I direct downloaded the file from their site and fast boot flashed after verifying MD5. There is definitely a problem with he recovery

Aldo101t said:
well, thats the right one, i would suggest that you manually download the file and install using adb fastboot.
Click to expand...
Click to collapse
Thank you sir! I am new to this so I am learning as I go. I read that these are the steps to follow to do an ADB Fastboot. Please correct me if I am wrong. Thanks again for your help.
1) Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to "twrp.img"
2) Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list.
3) Plug the device into your computer. Run the following command via the command line:
fastboot flash recovery "twrp.img"
Bless.

Kraizk said:
I direct downloaded the file from their site and fast boot flashed after verifying MD5. There is definitely a problem with he recovery
Click to expand...
Click to collapse
That sucks! So should I do try adb fastboot or go back to the previous version (2.5)?
What sucks is that without 2.6 working properly, I won't be able to flash any ROM with the new android version (4.2)

Aldo101t said:
well, thats the right one, i would suggest that you manually download the file and install using adb fastboot.
Click to expand...
Click to collapse
Did the ADB and still the same problem. Should I go back to previous version of TWRP?

chamo311 said:
Thank you sir! I am new to this so I am learning as I go. I read that these are the steps to follow to do an ADB Fastboot. Please correct me if I am wrong. Thanks again for your help.
1) Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to "twrp.img"
2) Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list.
3) Plug the device into your computer. Run the following command via the command line:
fastboot flash recovery "twrp.img"
Bless.
Click to expand...
Click to collapse
no, thats not right, don't put on your sdcard, download the file, put it in your directory where yoy have fastboot(on your computer. cd to that directory, open command prompt, (administrative) type adb reboot bootloader, when in bootloader (fastboot usb) type fastboot flash recovery(name of file).img

Aldo101t said:
no, thats not right, don't put on your sdcard, download the file, put it in your directory where yoy have fastboot(on your computer. cd to that directory, open command prompt, (administrative) type adb reboot bootloader, when in bootloader (fastboot usb) type fastboot flash recovery(name of file).img
Click to expand...
Click to collapse
It is broken, several users are reporting it in the original TWRP post as well

Kraizk said:
It is broken, several users are reporting it in the original TWRP post as well
Click to expand...
Click to collapse
Now that's some "good news" LOL! because I thought I screwed my phone and I wasn't going to be happy about it. I went back to v2.5 and everything works great!!
Thank you so much for all your help, guys!
Bless!!:good:

Kraizk said:
It is broken, several users are reporting it in the original TWRP post as well
Click to expand...
Click to collapse
that could be, thanks for the heads up

STUCK in TWRP Recovery
Aldo101t said:
that could be, thanks for the heads up
Click to expand...
Click to collapse
Completely stuck in Recovery. Can swipe to unlock screen but can not reboot even with Volume Down and Power button on Sprint HTC One. Just stuck. Phone is useless. Cant throw adb commands, nothing. WTF? What to do any ideas? Just watching the battery go down on the recovery screen...

Jason0071 said:
Completely stuck in Recovery. Can swipe to unlock screen but can not reboot even with Volume Down and Power button on Sprint HTC One. Just stuck. Phone is useless. Cant throw adb commands, nothing. WTF? What to do any ideas? Just watching the battery go down on the recovery screen...
Click to expand...
Click to collapse
just revert back to 2.5.0.0 and you are good to go

Jason0071 said:
Completely stuck in Recovery. Can swipe to unlock screen but can not reboot even with Volume Down and Power button on Sprint HTC One. Just stuck. Phone is useless. Cant throw adb commands, nothing. WTF? What to do any ideas? Just watching the battery go down on the recovery screen...
Click to expand...
Click to collapse
Did you just recently update your firmware to the new base? The reason I ask is because after I did I used the the firmware with the bootloader and recovery included. I had reflashed TWRP 2.5. Well I noticed that the method of holding down volume key and and power button would not work for me at all whether I was in the os, bootloader or recovery. So I flashed the Rom I was on again and it fixed it. So I am wondering this is what is happening to you. Maybe just let the phone lose charge then plug it in reboot to the os then into bootloader and flash the 2.5 TWRP recovery. Only thing I can think of your not bricked

Jason0071 said:
Completely stuck in Recovery. Can swipe to unlock screen but can not reboot even with Volume Down and Power button on Sprint HTC One. Just stuck. Phone is useless. Cant throw adb commands, nothing. WTF? What to do any ideas? Just watching the battery go down on the recovery screen...
Click to expand...
Click to collapse
Did you try holding the phone under a bright light then holding power and vol down to reboot. This works sometimes
Sent from my jacked HTC One!!

Aldo101t said:
just revert back to 2.5.0.0 and you are good to go
Click to expand...
Click to collapse
Given all the issues with 2.6 listed here, should I update from 2.5 to 2.6? Also, if TWRP says 2..5.0.0 at the top of the screen, how do I know this is the wls version?

mzel said:
Given all the issues with 2.6 listed here, should I update from 2.5 to 2.6? Also, if TWRP says 2..5.0.0 at the top of the screen, how do I know this is the wls version?
Click to expand...
Click to collapse
look at the zip file you download (openrecovery twrp-2.5.0.0-m7wls.img) m7wls tells you its for sprint.or m7spr whatever
there is a new version 2.6.0.1 but i don't know if it still has bugs or not, i'd stay at 2.5.0.0

Aldo101t said:
look at the zip file you download (openrecovery twrp-2.5.0.0-m7wls.img) m7wls tells you its for sprint.or m7spr whatever
there is a new version 2.6.0.1 but i don't know if it still has bugs or not, i'd stay at 2.5.0.0
Click to expand...
Click to collapse
I do not have a separate file. I think my TWRP came as part of some bigger ( root, recovery, permissions) package. I would think it was the Sprint version, but I keep having slight problems - those system apps try reboot after install, but in my case they do not. I have to boot manually, and after each recovery reboot I get a "reboot error notification". Can this be related?

mzel said:
I do not have a separate file. I think my TWRP came as part of some bigger ( root, recovery, permissions) package. I would think it was the Sprint version, but I keep having slight problems - those system apps try reboot after install, but in my case they do not. I have to boot manually, and after each recovery reboot I get a "reboot error notification". Can this be related?
Click to expand...
Click to collapse
that error is nothing don't worry about it, if you install a custom rom(make sure it's for sprint)that will go