Related
'hey guys/girls.
Im new at installing custom ROMS and all that.
I got my desire rooted with unrevoked 3.0 and it worked fine.
I installed a custom ROM and it worked fine,but i didnt like it so I tried a new one.
I can´t remember the name of it but I didnt like that either. Again i found a new ROM i´d like to try but when I turn off my phone and turn it on again trying to get to Hboot/recovery mode or what its called nothing happens i just stay turn off until i remove my finger from volume down buttom, then it just start then phone normally.
Do any one know what to do?
There are a couple of ways.
Way 1
1) Turn off your phone
2) Hold vol down + power until it loads the bootloader
3) When it's finished checking SD card, move to recovery using volume keys and press power to select recovery
4) It should load into recovery
Way 2
1) Have the Android SDK installed with the platform-tools downloaded and working
2) Make sure you plug your phone cable in your phone and PC
3) Open up command prompt or terminal (depending on your OS)
4) Type "adb reboot recovery" (no quotes) and it will reboot to recovery.
i have similar problem, cant access recovery anymore. that happened after installing a custom rom (leedroid). when i try to access recovery phone just hangs up on that red triangle. to turn it on again i have to pull of the battery. btw, phone works normaly itself only problem is that i cant access recovery to install some other rom :/
Drunk Moose said:
i have similar problem, cant access recovery anymore. that happened after installing a custom rom (leedroid). when i try to access recovery phone just hangs up on that red triangle. to turn it on again i have to pull of the battery. btw, phone works normaly itself only problem is that i cant access recovery to install some other rom :/
Click to expand...
Click to collapse
The red triangle is the stock recovery, so you're actually in recovery there.
Download a recovery and read this. Should get recovery back on your phone again.
but i had normal recovery i installed dozens of custom roms :/ and now phone just stucks in that screen with phone and triangle :/
How the hell can you install custom roms with the stock recovery.
thats the point, i had normal recovery and now i cant access it im using custom roms from the times desire was released and now almost after a year this **** happened :/
Ok... 2 posts ago I linked you to an article that can get the a custom recovery back onto your phone.
can u explain me info in that link a little? what .zip file do i need and where to get it? and WTF is terminal?
1) Download Clockwork Recovery or if you have PVT4 download Amon_RA (GSM)
2) Put it on your SD card
3) Download terminal emulator from the market
4) Type "su" (without quotes) and press allow when it comes up
5) Type "flash_image recovery /sdcard/recovery.img" (without quotes) and it will write the file to your phone.
To check which PVT you have, boot into bootloader. Turn off phone and hold vol down + power.
installed better terminal emulator pro. downloaded img, renamed it to recovery, inserted it to sdcard in terminal typed:
su (enter)
flash_image recovery /sdcard/recovery.img (enter)
and terminal says:
flash_image: not found
Did you put the img into a folder?
no, in the root of sd card
Weird. I don't know. Just tinker around with it. I tried it once and it worked for me. Check spelling, check in a file manager to see if the file is there.
i think i get this. thing is my rom does not have flash_image. now looking how to get it.
yep, there is no flash_image in system.
Are you using the new Sense ROMS/Gingerbread? If so 'Fast Boot' mode will screw with getting into recovery. I have to hold down volume while replacing the battery or turn off fast boot from within settings....
OFC if you have no recovery image anymore this won't help one little bit
KYI
yes im using new leedroid gb. i turned off that fast boot, its not that :/ now trying to push flash_image through adb, but it says "failed to copy....bla bla bla...: out of memmory" getting little desperate
If I was you I would back everything up. Contacts, SMS all that good stuff. I would then use an RUU and get the stock rom back on and just root that. Could of done it by now really.
Ok 2 problems:
1. to the topic starter. The reason you can't access recovery is that your rom uses fast boot up(sleep mode). When this is activated the phone doesn't really shut down when you tell it to, so it also cannot actually enter recovery or fastboot. Just turn it off in the settings menu and you'll be fine.
2. to Drunk Moose.
You have the original htc-recovery installed. I bet that you rooted back before unrevoked, and you probably have been using fakeflash since then. Try making rom manager dl cwm and choose reboot to recovery from rom manager. It should enter clockwork mod. If that is the case, this means that your phone have a modified version of the stock recovery, which allows test-keys. if that is not the case, and you still get the triangle, you somehow overwrote your recovery with a stock one.
Either way to fix this, you need to replace the recovery image with a cwm one. This can only be done in 2 ways for the desire:
1. Use unrevoked even though your phone is rooted and it'll flash it using a known exploit.
2. run alpharev to gain s-off. When you have s-off you will be able to flash the recovery through fastboot or from the system like described by meaple.
The reason it doesn't work for you when you do like meaple descriped, is that the commands tell the phone to use a custom binary called flash_img and passes it the parameters "recovery" and the "recovery.img" file. Then the binary will tell the android system how to write the img file to the recovery partition(it cannot do this entirely by itself). However this bynary is very unlikely to be included on your rom(like you figured out yourself ), so you need to place it somewhere you can access it from the terminal. And even if you had had the file, you wouldn't have been able to do so, as the recovery partition is write-protected doing runtime, when you are s-on.
So I'll recommend that you do one of the 2 mentioned solutions(I'll be glad to provide further help)
edit: and for god sake don't just flash a ruu every time you are in doubt... There are almost certainly an easier solution, and by doing s-off, you can avoid ever having to run a ruu again, as you can restore the system 1 partition at a time if you feel like it.(sorry this was not directed at you but people in general, as meaple just suggested doing so)
in fact i was just trying to use unrevoked bu it stucks on bootloader, tells to check for drivers, despite the drives is installed. :/
p.s. and yes i have rooted my desire almost a year ago there was no unrevoked
any other suggestions? or just try to install ruu?
and about the rom manager, it gets me to the same red triangle. btw the recovery was fine till i installed leedroids rom about a month, and i noticed it only few days ago, when i tryed to update my rom.
Hello,
I've been rooted for over a year now. Have flashed back and forth roms around hundreds of times now. Unfortunately an hour after flashing synergy godmode and some of the godmode tweaks, my phone rebooted while idling and bootloops.
Now i am stuck in hboot and can not enter recovery. I am using hboot 0.76.2000 (pc3610000) and s-off. I have tried flashing seperate clockwork and amon-ra embedded pc36img.zip, these say that they will complete updating but then will bootloop after i try to enter recovery. I have tried these updates with a different sd card (as my current sd card w/godmode may be an ext2 partition?) but that has not changed anything either.
As i understand, I can only push files with adb through recovery; which i can not get into.
If anyone can please help it would be very much appreciated.
Thank you in advance
try this way? its how i flash my recoveries when im switching or testing...
remove any pc36img.zip files from your sd and boot to your bootloader...
when you bootloader boots up let it scan for the pc36img whatever thing and let it say not found...
now highlight fastboot and click the power button and wait for FASTBOOT USB to show up...
then type in these codes...
Code:
fastboot devices
it should output some info, if you get some serial number then your good
then type in...
Code:
fastboot flash recovery *whatever the name of the recovery your using is*
so like for amon_ra 2.3 (which is what i use is)
Code:
fastboot flash recovery recovery-RA-supersonic-v2.3.img
just make sure that the recovery img file is in the same directory as the fastboot.exe file on your comp (its should be with all your other sdk stuff like adb.exe and such)
if all goes well then itll say
pushing recovery OKAY
writing recovery OKAY
and the amount of time it took...
then click back into your bootloader and go to the newly written recovery
(i apologize in advance if you already tried this with no avail)
I've set up fastboot usb and done this. Everything wrote ok and finished, however i still bootloop when trying to access recovery. I have tried multiple recoveries including clockwork 3, recovery-RA-supersonic-v2.3.img, and doing entire nandroid restores using nandroid recovery batch script. In both cases everything passes and nothing seems to be functional afterwards.
Any other ideas?
dunno man.. im just trying to visualize how it bootloops going to recovery.. it should be the white htc screen (or any other splash you may have set on there) and then boink recovery... does it like just sit there on the splash and thats it?
try letting it boot normal and then when it goes to the rom loading screen type in
Code:
adb reboot recovery
other than that something is totally askew bro
When booting, i'll get the white htc screen for 4-5 seconds, then it'll power off and reboot, unless i boot to hboot. When i hit recovery, it goes black for a second, then reboots to htc screen and repeats.
I've also tried complete wiping recovery and reloading using fastboot commander, and doing full pc36img.zip that include hboot, radio wiimax updates etc http://forum.xda-developers.com/showthread.php?t=830153&highlight=wimax
I may just go into a sprint store today. Was trying to avoid it as I really don't want to be stock again.
This may be a little progress....
I updated to hboot 0.93.0000
Now when i try to flash recoveries by hboot they pass and bootloop still, but when i try to flash recoveries by fastboot via pc -
"writing recovery..
FAILED (remote: not allowed)
does this provide any insight? going to try downgrading hboot again
the only hboot that allows fastboot commands is 0.76 unfortunately
try running an ruu maybe? other than that i havent the slightest idea
I used this RUU - http://forum.xda-developers.com/showthread.php?p=7529500
It passed every step, but still bootloops when booting to ROM and Recovery.
I'm out of ideas....
I'm going to go with hardware problem.
Sent from my PC36100 using XDA Premium App
bad sector on the internal flash memory ?
My brother has the same problem and i have been trying to fix it with no luck. When i boot the phone up its beeps/vibrate 5 times, then sits on a black screen. I can get into hboot and load pc.....whatever files, it says they work but still reboot, 5 beep, ect. I was going to try an RUU next i see that didnt work for op.
i just ran into this problem today. I was at work when it randomly rebooted and now is stuck in a bootloop. i have tried everything even using the latest RUU. it finished but still bootloops. I am also not able to get into recovery. Sucks because im out of warranty.
So let me get this straight...you can't go into recovery because there's no recovery? You've installed drivers and ran RUU and still nothing? That seems weird because i had the same issue when i first rooted my phone with unrevoked, all i did was run the RUU and it restored my phone back to "stock" and i re-rooted again but this time using z4 root. You might just have to take the phone back to Sprint
Same issue but worse
I'm having the same issue as the OP except that my buttons (power and volume up/down) will not respond. I have scoured these and other forums for a situation like mine and have found none.
I have tried flashing recoveries, RUU's and jsut about anything someone says.
First screen says:
supersonic evt3 ship s-off
hboot-2.10.0001
touch panel atmelc03_16ac
oct 15 2010 12:01:00
hboot
fastboot
recovery
clear storage
simlock
hboot usb
then it scans the sd card for the pc36img zip. It will load but will freeze on the next screen:
parsing...... [sd zip]
1. boot loader
2. radio
3. boot
4. recovery
5. system
6. user data
7. splash
8. wimax
it will stick here and I am completely lost. My old Palm Pre will only suffice for a day.... max.
If anyone has come across a situation like this that might help me, would you please point me in the right direction. Thanks!
kdbrown5 said:
This may be a little progress....
I updated to hboot 0.93.0000
Now when i try to flash recoveries by hboot they pass and bootloop still, but when i try to flash recoveries by fastboot via pc -
"writing recovery..
FAILED (remote: not allowed)
does this provide any insight? going to try downgrading hboot again
Click to expand...
Click to collapse
If you look in autoroot thread in my sig the "tools" zip has something that will let you flash different partitions from fastboot. If you use that to flash the PC36IMG from here it will give you the eng hboot back and possibly reflash whatever got corrupted.
Keep in mind, that will only work properly if you are not using one of the 2.xx hboots. Only phones with a 0.9x hboot will let you use it.
Hi, My DHD volume buttons no longer work and I've been reticent to send it off to get fixed as I can do with out the volume controls as opposed to being without a phone for 2-3 weeks.
However I used Rom manager to boot into CWR and was in the process of upgrading to revolution 5.2.4 from 5.1.8.
I ran the full wipe script then my fat fingers rebooted the phone rather than flashing the rom.
I now cant get back into CWR to flash the new rom. It just sits at the boot logo, obviously as all other partitions have been wiped.
Is there any other way I can force the phone to boot into CWR, perhaps using the sdk tools or similar?
I've tried adb devices, but it doesnt show up. Is there an external way to force the phone into flashing a new ROM or booting into CWRM ?
Thanks
Ron
I would like to help, first lets try using adb, command would be adb reboot recovery
Hi, thanks for the help.
As mentioned in OP. I have powered the phone on and have have already attempted this, but the device is not recognised by adb.
tools>adb reboot recovery
error: device not found
My question is how to get the device to be recognised if its simply sitting at the boot image?
R
Sorry I over looked that, it seems to me if adb (which is an sdk tool) won't recognize the device as being attached, i don't see any other sdk tool doing any different, also as far as I know there is no alternate method to scrolling through the boot loader that would allow you to choose recovery and flash a zip other then the volume keys , so it seems the solution is, to send the phone off, get the volume keys fixed, and then you will be able to get back into the boot loader, and select recovery, and reflash a rom. Other than that, I don't see any other method, if adb doesn't recognize the device as being plugged in, I am assuming you attempted to boot into boot loader as well, and see if adb recognized the device?
EDIT: stupid question you can't boot into boot loader without volume key
I just want to confirm that I need do nothing else other than configure the sdk and ENV path etc, such that if i can run adb and get the deafult output, eg switches fr command line options etc...
then all I should need to do is turn phone on and connect via usb to computer. I dont need to edit any config files for specific phone versions or whatnot?
If not then Ill try and bring it to a vodaphone shop and see if they can fix the volume button...
R
if you get the volume buttons fixed, we don't even need adb, I was simply thinking adb since your volume buttons are broken. Once the volume buttons are fixed, you simply need to boot into boot loader, then to recovery, mount USB mass storage, put a new rom on there, wipe the phone, flash the rom and your good
Good luck mate, do some mediation meanwhile and learn to keep patience, so when your phone is back, you can treat it gently while in the recovery.
You will be alright once your vol keys are fixed.
Hi Y'all, sometime lurker, first time poster.
I got an HTC One V (CDMA, Virgin Mobile) today and given the relative ease of rooting my old Droid Inc I thought it would be a breeze to do this phone as well, but I did not do enough research and messed it up. Here is what I did as best as I can recall:
I unlocked the bootloader without a problem using Fastboot.
Then I flashed CWM recovery through hasoon2000's all in one tool, but it didn't work. I believe I did not flash the correct CWM (CDMA). I tried reflashing stock recovery, and then CDMA CWM recovery, but I couldn't get past the white HTC with the red warning message.
Because I couldn't get recovery to work, I thought maybe I should flash the kernel. I was using hasoon2000's all in one tool, but I did not realize that it would try to boot into recovery in the middle of flashing the kernel (yeah, I'm a noob and an idiot).
So now it won't load into the standard ROM anymore, it just gets stuck on the HTC White screen with the Red Warning. I can get it to load the bootloader, and I tried flashing the kernel from the all in one tool through fastboot, but it didn't work.
Is there any way I can save my phone or am I out of luck?
Thanks for any help you can provide.
Get the stock boot.img and put it in your fast boot folder and go to cmd prompt and type
C:\fastboot
Fast boot flash boot boot.IMG
Make sure your in fastboot
Sent from my One V using xda app-developers app
Thanks XxlemonxX. I did that a few times and it didn't seem to stick.
But! While I was fastloading I went ahead and did the Superboot step found here:
http://forum.xda-developers.com/showthread.php?t=1598964
And the phone restarted! Huzzah! Now I just have to see if I can get a recovery actually working...
OK, so things got a little strange.
The phone booted up just fine, so I tried flashing CWM recovery again. It worked, and restarted into CWM recovery. The power button didn't seem to work for selecting various options for a while, it would just go to the screen with the cog and the top hat, until I held it down for a few seconds, after which the bottom buttons flashed, and at the bottom it said "back button enabled". Then the power button worked for selecting various options. (I'm not sure if this is how CWM recovery is supposed to work for the One V, as I can't find any definitive answers...). Anyways, ran a backup through recovery, but afterwards the phone wouldn't reboot again.
Since it worked before I ran the Superboot app through windows and bam, starts up again. Did a factory reset just to see if that would clear the rebooting problem, but it didn't. It did change, however. Now it goes to the white HTC screen with the red warning for a second, goes back to black, then goes to a really dark black with just the red warning barely visible for about 7~ seconds, then it powers down. The only way I can get a reboot into the ROM is to redo the Superboot app...
I'm a little nervous at this point. I tried flashing an MIUI rom through the CWM app but there was an error (I didn't write it down, sorry), and I can't find a reliable link to the stock RUU VM PrimoC Rom (jmz's links are down as far as I can tell). I just want a rom that will reboot without freezing, haha. Thanks again for any help.
tl;dr Phone only boots when Superboot app is flashed, try a different rom?
jimmymcsnakes said:
OK, so things got a little strange.
The phone booted up just fine, so I tried flashing CWM recovery again. It worked, and restarted into CWM recovery. The power button didn't seem to work for selecting various options for a while, it would just go to the screen with the cog and the top hat, until I held it down for a few seconds, after which the bottom buttons flashed, and at the bottom it said "back button enabled". Then the power button worked for selecting various options. (I'm not sure if this is how CWM recovery is supposed to work for the One V, as I can't find any definitive answers...). Anyways, ran a backup through recovery, but afterwards the phone wouldn't reboot again.
Since it worked before I ran the Superboot app through windows and bam, starts up again. Did a factory reset just to see if that would clear the rebooting problem, but it didn't. It did change, however. Now it goes to the white HTC screen with the red warning for a second, goes back to black, then goes to a really dark black with just the red warning barely visible for about 7~ seconds, then it powers down. The only way I can get a reboot into the ROM is to redo the Superboot app...
I'm a little nervous at this point. I tried flashing an MIUI rom through the CWM app but there was an error (I didn't write it down, sorry), and I can't find a reliable link to the stock RUU VM PrimoC Rom (jmz's links are down as far as I can tell). I just want a rom that will reboot without freezing, haha. Thanks again for any help.
tl;dr Phone only boots when Superboot app is flashed, try a different rom?
Click to expand...
Click to collapse
That is an old cwm. thats how it operates. Once your booted into the system you can install rom manager from play store and then you can update cwm so you wont have to enable the power button for use. But anyway seems you cant boot into a stable system right now. So If you are willing to follow theses instructions you can get back to factory conditions.
1. get the fastboot package if you dont have it. http://www.mediafire.com/?4dx982z93w8z7wk and put those files in a folder in the C drive.
2. Get the ruu from here its the top one if you are virgin mobile US. http://www.filefactory.com/f/0eafb9c43276c308/ look for RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed.exe
3. This is how your going to get the stock recovery and stock kernel. run the ruu but dont do anything with it just yet. After the ruu is opened and is at the welcome screen just click and drag the window down out of the way and open ANY folder and type %temp% in the address bar of that folder and press enter. You will see a bunch of folders with titles like this "{B2B09672-51AB-4EF6-BDDF-50CB9719052B}" This is just an example. While in that temp folder just do a search for rom.zip and when you find it you can copy that file to your desktop and then just click cancel in the ruu welcome screen for now.
4. Open the rom.zip file with 7zip. You must use 7zip. The built in windows zip program wont work. Once its opened with 7zip, extract these two files 'recovery_signed.img' and 'boot_signed.img'. This is your stock recovery and stock kernel. Extract those to the fastboot folder.
5. You must somehow get your device into the bootloader again. I had the same symptoms as you did with the dark screen and dim red text. I just kept playing with the volume down during boot and eventualy got there. DO NOT USE VOLUME UP!!
6. Once your in the bootloader choose fastboot and plug your device in and it should now say fastboot usb at the top of the bootloader screen. Now run theses commands.
7. Commands to run.
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
8. Now while in bootloader fastboot usb still just run the ruu and follow all instructions. Make sure you have atleast 30% battery while performing this. And if all goes well you will be back to square one.
hello android geniuses first of sorry about this once my phone is working again i will not mess with it anymore
okay so i was feeling cool and rooted my htc one m7 from verizon then i turned s-off and unlocked bootloader
then i flashed a custom rom it was paranoid android everything worked except i wasnt getting any service on the phone so i was told to flash a verizon htc one rom so i went and flashed viper 6.2 but the phone got stuck in a bootloop so for some reason i thought that doing a factory reset/wipe from the recovery would fix it....it didnt and now i cant reflash the rom either....i tried to sideload but adb wont recognize my device while fastboot recognizes the phone adb wont
what am i to do?
Well im not sure of any other methods to try but i had loads of problems myself pushing files to the SDcard threw twrp and cwm recoveries, so the way I went about it was doing a decrypted RUU to return the phone to stock then once it loaded up in Android I pushed the Rom to the SDcard card then rebooted and started over.
Goto this thread http://forum.xda-developers.com/showpost.php?p=46506621&postcount=2
All the way at the bottom you should see some links for RUU's, I used the one labeled "1.10.605.15 Decrypted RUU" You will flash this the same way as you would a firmware update, if you dont know how thats done that post will explain it all. After you flash the RUU reboot and it should be back to the day you got it, but you will still be s-off, at that point just put a custom recovery back on and flash away, however that RUU will downgrade your firmware so you might wanna update your firmware after you get the phone booted up and your rom placed back on the sdcard
fLaWx said:
Well im not sure of any other methods to try but i had loads of problems myself pushing files to the SDcard threw twrp and cwm recoveries, so the way I went about it was doing a decrypted RUU to return the phone to stock then once it loaded up in Android I pushed the Rom to the SDcard card then rebooted and started over.
Goto this thread http://forum.xda-developers.com/showpost.php?p=46506621&postcount=2
All the way at the bottom you should see some links for RUU's, I used the one labeled "1.10.605.15 Decrypted RUU" You will flash this the same way as you would a firmware update, if you dont know how thats done that post will explain it all. After you flash the RUU reboot and it should be back to the day you got it, but you will still be s-off, at that point just put a custom recovery back on and flash away, however that RUU will downgrade your firmware so you might wanna update your firmware after you get the phone booted up and your rom placed back on the sdcard
Click to expand...
Click to collapse
What he said. Good post dude.
When you enabled adb sideload, what command did you use? Because you don't push files that way. You type "adb sideload Rom.zip", then it will send the file and after it sends immediately start the install. So you will need to wipe in recovery first to make sure it's clean.
Sent from my Lunar Ecliptic One.
i followed your steps i got to the part where fastboot asks to flush the zip again i typed "fastboot flash zip firmware.zip" and it said waiting for device and that never went away so i rebooted into bootloader and now fastboot wont recognize the device however if i go to device manager it says my htc is plugged but has a little yellow icon...the drivers are up to date this is driving me nuts i just want my phone to work
Ruu
sound like you may need to ruu back to total stock there are instruction on doing it here and I do not want to give you the wrong steps. found this but make sure you have the decrypted ruu
1. Download VZW RUU.zip from the following thread 1. Download VZW RUU.zip from the following thread (http://forum.xda-developers.com/show....php?t=2428276)
2. Rename to "ruu.zip"
3. Enter fastboot mode
4. enter "fastboot oem rebootRUU" - You should not see a silver HTC logo on your device.
5. enter "fastboot flash zip ruu.zip" - The first time you execute this command, it only prepares the flash
6. As soon as the flash is done preparing, enter the same exact command again "fastboot flash zip ruu.zip"
7. Now you'll see a little green progress bar on your phone. This does not need to reach 100%. As soon as your command window is finished, you can just "fastboot reboot".
8. You should be set back to fully stock HTC One.
http://www.htc1guru.com/dld/ruu-zip-m7_wl_jb_50_vzw_1-10-605-10_decrypted-zip/
I also use cut and paste when doing this as it stops my crappy spelling from getting in the way
The problem now is that fastboot wont recognize the device, when i type "fastboot devices" its blank
i think i screwed up the firmware becouse in fastboot it says in red os-3.11.605.1 (1.10.605.15) in red
before i remember it was green that spot...oh crap i wont be able o buy a new phone in a long time this is terrible....i still have teamwin recovery can i do anything through that?
quadracorn said:
The problem now is that fastboot wont recognize the device, when i type "fastboot devices" its blank
i think i screwed up the firmware becouse in fastboot it says in red os-3.11.605.1 (1.10.605.15) in red
before i remember it was green that spot...oh crap i wont be able o buy a new phone in a long time this is terrible....i still have teamwin recovery can i do anything through that?
Click to expand...
Click to collapse
You could always use a USB-OTG, place a rom on a flash drive and try to install that way. There may be a simpler way, but that's all i can think of for now.
i guess i have to order an otg cable....oh well...ill have to live without a phone a bit longer until cable shows up haha XD w
quadracorn said:
The problem now is that fastboot wont recognize the device, when i type "fastboot devices" its blank
i think i screwed up the firmware becouse in fastboot it says in red os-3.11.605.1 (1.10.605.15) in red
before i remember it was green that spot...oh crap i wont be able o buy a new phone in a long time this is terrible....i still have teamwin recovery can i do anything through that?
Click to expand...
Click to collapse
Does pc see device in computer?if so down load room onto pc place Rom on root of ad card or in download and reboot phone into recovery ahs flash zip..I also had problem where adb would not see devices cause I had miniadb and the full version of adb and it was a conflict,just my two cents
I don't know if this will help, but I had an issue of my devices not being found so I followed this guy's guide: http://zacktutorials.blogspot.com/2013/04/adb-is-not-recognized-as-internal-or.html
and was able to get my device recognized. Also which recovery are you using? I don't know if it's still an issue but when I was on viper I got stuck in a bootloop with TWRP so I switched to Philz.
If you're able to get into fastboot, follow post #4 http://forum.xda-developers.com/showthread.php?t=2677015 and basically start from the beginning.
Make sure you have the latest recovery, the latest firmware (radios and such), and the correct ROM..
good luck
bregga said:
sound like you may need to ruu back to total stock there are instruction on doing it here and I do not want to give you the wrong steps. found this but make sure you have the decrypted ruu
1. Download VZW RUU.zip from the following thread 1. Download VZW RUU.zip from the following thread (http://forum.xda-developers.com/show....php?t=2428276)
2. Rename to "ruu.zip"
3. Enter fastboot mode
4. enter "fastboot oem rebootRUU" - You should not see a silver HTC logo on your device.
5. enter "fastboot flash zip ruu.zip" - The first time you execute this command, it only prepares the flash
6. As soon as the flash is done preparing, enter the same exact command again "fastboot flash zip ruu.zip"
7. Now you'll see a little green progress bar on your phone. This does not need to reach 100%. As soon as your command window is finished, you can just "fastboot reboot".
8. You should be set back to fully stock HTC One.
http://www.htc1guru.com/dld/ruu-zip-m7_wl_jb_50_vzw_1-10-605-10_decrypted-zip/
I also use cut and paste when doing this as it stops my crappy spelling from getting in the way
Click to expand...
Click to collapse
Hi All,
Do you know is RUU 4.4 has surfaced? please help