Database Develop

attempt to update spl and now nothing?

renamed spl to update.zip and placed in root of SD
did alt+s, think i pressed alt+w accidentally, now when booting / rebooting
trying to get my home + power screen to reload, get "ROGERS" with the red "FASTBOOT USB" at the top, according to this
Rogers, heres your real root
http://forum.xda-developers.com/showthread.php?t=544654
"(if you don't boot into recovery or accidentally rebooted, just pull the battery [if you notice top left it should read "FASTBOOT" or "FASTBOOT USB" if it's plugged in] you're not bricked, you just need to access recovery, not standard boot ;P)"
then alt+s to load the rom, well the rom isn't on there becausei was following
installing the new spl
http://forum.xda-developers.com/showthread.php?t=532719
anyway to load the actual rom some other way, can't access the SD card with the fastboot skateboard screen or the rogers with the red "Fastboot usb" screen.
Confused, and frustrated, some help would be wonderful if you have the time, Thanks !

Did you flash the SPL before you flashed the radio?

xsnipuhx said:
Did you flash the SPL before you flashed the radio?
Click to expand...
Click to collapse
what i was trying to do

note: when attempting to flash
fastboot flash radio radio.img
Error: FAILED <remote: signature verify fail>
fastboot erase system -w
-okay
fastboot erase boot
-okay
fastboot erase recovery
-okay
fastboot flash recovery recovery.img
Error: FAILED <remote: signature verify fail>

Try redownloading the recovery.img There may have been a corrupted file somewhere.

xsnipuhx said:
Try redownloading the recovery.img There may have been a corrupted file somewhere.
Click to expand...
Click to collapse
Just did, receiving same error as before
"FAILED <remote: signature verify fail>
?

Check the original thread and see if anyone else is having the same problem.

xsnipuhx said:
Check the original thread and see if anyone else is having the same problem.
Click to expand...
Click to collapse
seems like a few are having a similar issue , more or less the "stuck at rogers screen for a long ass time"
this is a little frustrating =( haha

JsnLlnd said:
seems like a few are having a similar issue , more or less the "stuck at rogers screen for a long ass time"
this is a little frustrating =( haha
Click to expand...
Click to collapse
If you're just trying to load the ROM, try booting into recovery (home+power) then press alt+x and type ums_enable that will allow you to transfer things over to your sdcard like you normally would.

h.nocturna said:
If you're just trying to load the ROM, try booting into recovery (home+power) then press alt+x and type ums_enable that will allow you to transfer things over to your sdcard like you normally would.
Click to expand...
Click to collapse
Tried, won't go into recovery. stays at the Rogers start screen.
Anything else?

Quick update, was able to get into
fastboot boot recovery.img
and it loaded cyanogen cf 1.5? did alt+s and alt+w but theres no rom on the sd card right? hence its not doing anything?
am i figuring this out correctly here?
when i type in the fastboot boot recovery.img
downloading 'boot.img'...OKAY
booting...OKAY
where is this thing and how do i do this right im confusing myself blahhh
--------
rebooted, now i can't get into fastboot -_-
is this thing bricked now ?
use my fastboot boot recovery.img and it goes fastboot real quick, see a loading bar, then bam back to plain rogers screen. gonna try different recovery.
possibly adb push ? im learning this all just now more or less, so a direct path from my c:\android\sdk1.5_r3\tools: adb push ??? what goes here?
as far as the alt+x option goes , i can do it , but ums_enable isn't doing anything , any more details on that so i can get that rom on the SD card, think i will be good to go after that.

[Q] Nexus one broken power button won't boot

I need some help here.
Power button broke on my n1 sometime ago. Recently I tried to flash a new kernel but forgot to wipe and it's basically stuck at the logo.
I'm able to get into the hboot screen via bqttry removal technique but cannot select any option because of bad power button.
Any ideas how to flash a new room? I tried connecting USB to pc but phone is not recognized while in hboot mode.
Any help would appreciated as it's my only phone
Thanks

Is your phone unlocked (ie do you have a lock symbol at the bottom of the 'X' screen)?
If so, I believe you can hold the trackball while booting up and that will take you into fastboot.
From there, I think you just issue the command
Code:
fastboot reboot recovery
If that doesn't work, you can just boot off a recovery file that is stored on your computer. Download either clockworkmod (I would recommend any v2.x as v3.x has some problems) or Amon_RA to a easy to type location on your computer. Then issue the command
Code:
fastboot boot recovery "c:\location to\recovery.img"

Ok, so I got it to boot in fastboot, but there's no option to
./fastboot-mac reboot recovery
Click to expand...
Click to collapse
also
./fastboot-mac boot recovery ../recovery-RA-passion-v2.2.1.img
Click to expand...
Click to collapse
I get:
cannot load 'recovery'
and I did this:
fastboot flash recovery /path/to/<recovery>.img
Click to expand...
Click to collapse
Is there a way reboot it into recovery?
Thanks!

Passimg back to stock, root, and try again...

jp2000 said:
I get:
cannot load 'recovery'
Click to expand...
Click to collapse
Is there any more into that error? Did you verify the md5sum to make sure the recovery isn't corrupted?
Also, if you have a recent nandroid backup saved on your sdcard, you can pull that off and flash the imgs directly
Code:
./fastboot-mac flash system /location/to/system.img
./fastboot-mac flash boot /location/to/boot.img
./fastboot-mac flash userdata /location/to/data.img
./fastboot-mac reboot
Where these files will be located depends on your recovery. I know with clockworkmod they are located in the backup folder under the clockworkmod folder on the sdcard. I don't know where they are stored for Amon_RA, but I would assume it would be similar.

Thanks to everyone for your suggestions.
Finally got my phone working!

Hi.
I have the same problem but whenever I try "fastboot flash" or "fastboot recovery" I end up with "FAILED (remote: signature verifiy fail)". I think this is due to that my bootloader is not unlocked, so I tried:
fastboot oem unlock
I got the option to unlock bootloader but I had to use my power button to select "unlock". My power button is broken so I don't know what to do.
Is there anything else I can do? Otherwise I think I have to open the phone and try to repair the button.

PASSIMG back to stock and root. Use "unroot/restore" section in Wiki.
If you're skilled enough with soldering tiny connectors - you can repair the button. There is a guide on this forum, showing the exact location to attach to.

Thanks. Now I can use the phone again!

Where is this repair guide...please let me know...
Sent from my Nexus One using xda premium

[Q] Stuck In Loop!

Hey guys, I need some major help!
I was trying to update my phone earlier today, when I flashed Android Revolution HD 40.3 something very bad happened!
For some reason the ROM did not install properly, and I can't get back into recovery. I was using TWRP and the loading screen comes up for it, but it never fully launches.
I can get into the bootloader, and I tried using the Toolkit under fastboot. It seems like my phone is detected, but when I try and flash anything it doesnt work. Ive flashed both TWRP and clockword. They seem to flash because it will show the loading screen of either one, but it never actually enters the recovery. What should I do?
My phone is S-ON, I am not sure if that is what caused the problem/is what is keeping this an issue.
Thanks for your help

SMGkrome said:
Hey guys, I need some major help!
I was trying to update my phone earlier today, when I flashed Android Revolution HD 40.3 something very bad happened!
For some reason the ROM did not install properly, and I can't get back into recovery. I was using TWRP and the loading screen comes up for it, but it never fully launches.
I can get into the bootloader, and I tried using the Toolkit under fastboot. It seems like my phone is detected, but when I try and flash anything it doesnt work. Ive flashed both TWRP and clockword. They seem to flash because it will show the loading screen of either one, but it never actually enters the recovery. What should I do?
My phone is S-ON, I am not sure if that is what caused the problem/is what is keeping this an issue.
Thanks for your help
Click to expand...
Click to collapse
Does the phone just reboot before it enters recovery? I would try manually flashing a custom recovery image. Here is a link to the exact image I used.
http://forum.xda-developers.com/showthread.php?t=2173863
It's very straightforward once you have fast boot setup. Don't worry I've been in your situation myself!

JasSingh93 said:
Does the phone just reboot before it enters recovery? I would try manually flashing a custom recovery image. Here is a link to the exact image I used.
http://forum.xda-developers.com/showthread.php?t=2173863
It's very straightforward once you have fast boot setup. Don't worry I've been in your situation myself!
Click to expand...
Click to collapse
Thanks for the response!
Was your phone S-ON?? It seems that there are fixes when it is S-OFF, but not S-ON

SMGkrome said:
Thanks for the response!
Was your phone S-ON?? It seems that there are fixes when it is S-OFF, but not S-ON
Click to expand...
Click to collapse
My phone was S-ON at the time, I recently gained S-OFF. You should still be able to flash a new recovery with S-ON. S-OFF is usually only needed for flashing new radios or firmwares.

JasSingh93 said:
My phone was S-ON at the time, I recently gained S-OFF. You should still be able to flash a new recovery with S-ON. S-OFF is usually only needed for flashing new radios or firmwares.
Click to expand...
Click to collapse
How did you flash the recovery? Like I've said, I tried flashing a new recovery via the Toolkit. They do seem to flash, but I cant access the recovery. I'm not sure if my bootloader was relocked or what, but it doesn't go past the intro screen for TWRP or Clockwork

SMGkrome said:
How did you flash the recovery? Like I've said, I tried flashing a new recovery via the Toolkit. They do seem to flash, but I cant access the recovery. I'm not sure if my bootloader was relocked or what, but it doesn't go past the intro screen for TWRP or Clockwork
Click to expand...
Click to collapse
It could be possible that the toolkit is installing an incorrect version maybe? Switch off your phone. Once off hold vol - and power the phone on. This should load up HBOOT and tell you the boot loader status.
This is how I flashed recovery. I entered fastboot and used the commands from that link to flash a new recovery image. Have you used fastboot commands before?

JasSingh93 said:
It could be possible that the toolkit is installing an incorrect version maybe? Switch off your phone. Once off hold vol - and power the phone on. This should load up HBOOT and tell you the boot loader status.
This is how I flashed recovery. I entered fastboot and used the commands from that link to flash a new recovery image. Have you used fastboot commands before?
Click to expand...
Click to collapse
To be honest, I'm pretty new to the fastboot commands. I usually follow guides to root, and flashing ROMs is pretty straightforward.

SMGkrome said:
To be honest, I'm pretty new to the fastboot commands. I usually follow guides to root, and flashing ROMs is pretty straightforward.
Click to expand...
Click to collapse
If you have fastboot setup and working, just boot the phone into fastboot mode and use the commands in that link I gave you.
From fastboot. Use command "fastboot erase cache"
From fastboot. Use command "fastboot flash recovery recovery.img"
Then simply highlight "recovery", tap the power button and the phone should load up clockwordmod recovery.
Easy

JasSingh93 said:
If you have fastboot setup and working, just boot the phone into fastboot mode and use the commands in that link I gave you.
From fastboot. Use command "fastboot erase cache"
From fastboot. Use command "fastboot flash recovery recovery.img"
Then simply highlight "recovery", tap the power button and the phone should load up clockwordmod recovery.
Easy
Click to expand...
Click to collapse
Is fastboot mode just when you hold power and volume down then select fastboot?

SMGkrome said:
Is fastboot mode just when you hold power and volume down then select fastboot?
Click to expand...
Click to collapse
It is

SMGkrome said:
Is fastboot mode just when you hold power and volume down then select fastboot?
Click to expand...
Click to collapse
This is going to make me sound incompetent, but to use fastboot commands I just need to install the ADT Bundle from google for developers?

SMGkrome said:
This is going to make me sound incompetent, but to use fastboot commands I just need to install the ADT Bundle from google for developers?
Click to expand...
Click to collapse
It doesn't make you sound incompetent at all! Yes its just the bundle, then the drivers should be installed with that too. If you're not 100% sure there are plenty of guides online on how to setup fastboot.
For example: http://techbeasts.com/2013/08/26/how-to-install-adb-fastboot-drivers-on-your-windows-pc-guide/
Or if you're lazy like me you can use this: http://forum.xda-developers.com/showthread.php?p=42407269

JasSingh93 said:
It doesn't make you sound incompetent at all! Yes its just the bundle, then the drivers should be installed with that too. If you're not 100% sure there are plenty of guides online on how to setup fastboot.
For example: http://techbeasts.com/2013/08/26/how-to-install-adb-fastboot-drivers-on-your-windows-pc-guide/
Or if you're lazy like me you can use this: http://forum.xda-developers.com/showthread.php?p=42407269
Click to expand...
Click to collapse
Ah, no dice. I followed all the steps, everything seemed to work (thanks for the guide). It flashed the recovery okay. When I restarted the phone, it goes into recovery, shows clockwork mod recovery, version XX and then proceeds to try and boot into my regular system

SMGkrome said:
Ah, no dice. I followed all the steps, everything seemed to work (thanks for the guide). It flashed the recovery okay. When I restarted the phone, it goes into recovery, shows clockwork mod recovery, version XX and then proceeds to try and boot into my regular system
Click to expand...
Click to collapse
Hm, that's really strange. So recovery tried to boot, but the phone restarts and tried to boot normally?
Did you try running the command "fastboot erase cache" in fastboot mode?

JasSingh93 said:
Hm, that's really strange. So recovery tried to boot, but the phone restarts and tried to boot normally?
Did you try running the command "fastboot erase cache" in fastboot mode?
Click to expand...
Click to collapse
Yeah, basically it goes back and forth between trying to get into recovery and try to boot normally but can't boot into either

SMGkrome said:
Yeah, basically it goes back and forth between trying to get into recovery and try to boot normally but can't boot into either
Click to expand...
Click to collapse
OK so new recovery flashed, I would try running "fastboot erase cache". This commonly fixed issues with recoveries failing to boot.

JasSingh93 said:
OK so new recovery flashed, I would try running "fastboot erase cache". This commonly fixed issues with recoveries failing to boot.
Click to expand...
Click to collapse
So I owe you a beer! I guess I must have forgotten that command. Worked perfectly, phone is all good now!
Thanks for all the help

SMGkrome said:
So I owe you a beer! I guess I must have forgotten that command. Worked perfectly, phone is all good now!
Thanks for all the help
Click to expand...
Click to collapse
No worries! Glad you got it working. Happy to help!

Locked bootloader and can't boot into ROM or Recovery. (Fixed!)

Well, I really did it this time. In my efforts of messing with the M Preview build and trying to eliminate the "verification failed" startup message I made the mistake of locking the bootloader. Now the phone will not boot into Android or into Recovery. I'm stuck in Bootloader and it won't let me "fastboot OEM unlock" the device because in order to do this you need to boot into Android and tick the box to allow OEM unlocking (which I also unticked before getting into this mess, like an idiot).
EDIT: Got it resolved!
In order to get into Recovery I had to use the following commands in the bootloader:
fastboot format cache
fastboot format userdata
After doing this I was able to boot into recovery. However, recovery showed 0MB available storage and wouldn't mount /data, which prevented me from installing anything. It also wouldn't allow me to copy anything to the SD card using Android File Transfer or ADB sideloading.
To solve this I went into "Wipe" while in recovery and did a full format (the one that requires you to type "yes" before proceeding"
After doing this and booting back into recovery, I had full storage space back and recovery was able to mount /data. At this point I just copy/pasted the 5.1.1 ROM onto the sdcard with Android File Transfer. Once installed, I flashed the ROM and it booted right up.
I then skipped through the setup to get to settings and in developer settings I ticked the box to allow OEM unlocking. After doing that, I booted back into the bootloader and used the fastboot command "fastboot oem unlock" to unlock the bootloader again.
Once that was done I was able to use fastboot commands to flash the M preview all over again.
Hopefully you don't find yourself in this mess, but if you do, I'm hoping the above solution works for you.

sn0warmy said:
Well, I really did it this time. In my efforts of messing the the M Preview build and trying to eliminate the verification failed startup message I really locked up the phone. I locked the bootloader and now the phone will not boot into either recovery or the ROM. It won't let me "fastboot OEM unlock" the device either because it requires me to go into settings and check the allow OEM unlock. However, since I can't boot into the ROM, I cannot do that.
I'm really stuck here. Any ideas?
Click to expand...
Click to collapse
Hope you can RMA it

akellar said:
Hope you can RMA it
Click to expand...
Click to collapse
Well.... s**t.

sn0warmy said:
Well.... s**t.
Click to expand...
Click to collapse
Is TWRP installed?

WAIT!!
I did the following:
- fastboot format cache
- fastboot format userdata
And the phone now boots into TWRP. It won't boot fully but it will boot into recovery. I'm trying to sideload a ROM now but I can't access the storage.
Edit: enabled ADB sideload so I can ADB push a ROM to the SD card to flash. Does anyone know the exact root folder name for the sd card to pusht he ROM to? Is it /data/media/?

I did something similar this past weekend while trying to do the 5.1.1 upgrade with the OTA files before the Factory images were available.
Try and use the WugFresh tool to wipe the cache and such, and try some of the other obvious settings in the tool.
It was late and I'm not 100% sure what I did but I do remember reflashing the LRX22C from the factory image using the tool. Everything I did was from the tool minus the 5.1 OTA that came through once I was able to get back into the device. From there I was able to unlock the bootloader again.
I was worried myself that I might have to send the phone back but I just kept trying, don't give up just yet. I've been told many times it's almost impossible to brick an android device now a days.
Good luck!

sn0warmy said:
WAIT!!
I did the following:
- fastboot format cache
- fastboot format userdata
And the phone now boots into TWRP. It won't boot fully but it will boot into recovery. I'm trying to sideload a ROM now but I can't access the storage.
Edit: enabled ADB sideload so I can ADB push a ROM to the SD card to flash. Does anyone know the exact root folder name for the sd card to pusht he ROM to? Is it /data/media/?
Click to expand...
Click to collapse
Enable MTP in TWRP then drag n drop.

rootSU said:
Enable MTP in TWRP then drag n drop.
Click to expand...
Click to collapse
Can't access device storage.
However, I was able to ADB push the ROM to the SDcard. But when I try and install the ROM it gives me a bunch of errors saying "unable to mount '/data'" and "unable to mount storage"
Ideas?

sn0warmy said:
Can't access device storage.
However, I was able to ADB push the ROM to the SDcard. But when I try and install the ROM it gives me a bunch of errors saying "unable to mount '/data'" and "unable to mount storage"
Ideas?
Click to expand...
Click to collapse
Assuming you tried ticking data in twrp mounts...
In twrp, try and format data again. If that fails, try to format it as another file system such as f2fs before formatting it back to ext4

rootSU said:
Assuming you tried ticking data in twrp mounts...
In twrp, try and format data again. If that fails, try to format it as another file system such as f2fs before formatting it back to ext4
Click to expand...
Click to collapse
Success!
TWRP was also reporting 0mb available storage. I went into Wipe and performed a full format. Booted back into recovery and storage was showingt he full amount again. I was then able to plug the phone in and enable MTP and drag/drop the 5.1.1 ROM onto the SD card. Just flashed it and it booted right up!
I'm going to update the OP with all this info just in case someone else runs into the issue and needs help.
Thanks for your help!

sn0warmy said:
Well, I really did it this time. In my efforts of messing with the M Preview build and trying to eliminate the "verification failed" startup message I made the mistake of locking the bootloader. Now the phone will not boot into Android or into Recovery. I'm stuck in Bootloader and it won't let me "fastboot OEM unlock" the device because in order to do this you need to boot into Android and tick the box to allow OEM unlocking (which I also unticked before getting into this mess, like an idiot).
Click to expand...
Click to collapse
Hi,
I faced the same condition like you experienced, with some differences:
- the phone stuck in "Google" logo
- stock recovery is accessible from bootloader
- I am unable to mount sdcard or install rom from sd card, but could conduct adb sideload
However, am stuck with verifying update package showing :
E: footer is wrong
E: signature verification failed
any ideas what to do next?
================ edited- add below info on how I got stuck
So my N6 was still on 5.0 (has not been updated to 5.1). I decided to try the M preview. I downloaded the preview, and began the process as follows:
1. reboot into bootloader
2. fastboot oem unlock
3. flash-all (success on loading the bootloader and radio, but error on updating the image)
4. hence i followed to flash individually:
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
5. and comes the stupid thing ! --> fastboot oem lock (really really regret why I did this)
6. and then once reboot, it stuck in Google logo forever
However, I am still able to access:
- bootloader (fastboot recognize the device, but wouldn't allow me to fastboot oem unlock)
- able to go to stock recovery, and as mentioned above:
I am unable to mount sdcard or install rom from sd card, but could conduct adb sideload
However, am stuck with verifying update package showing :
E: footer is wrong
E: signature verification failed
I tried to adb sideload the M preview image and 5.1 LMY47I but both showing the above error....
hope you can shed some light on this...

Please does anyone have a solution to this? please help me

Iambenqazy said:
Please does anyone have a solution to this? please help me
Click to expand...
Click to collapse
A solution to what? Keep in mind your problem may be different from the OP's issue, so if you want people to help you it's necessary to provide plenty of information, such as what you were trying to do, how you tried to do it, and any other information that you believe may be useful.

Strephon Alkhalikoi said:
A solution to what? Keep in mind your problem may be different from the OP's issue, so if you want people to help you it's necessary to provide plenty of information, such as what you were trying to do, how you tried to do it, and any other information that you believe may be useful.
Click to expand...
Click to collapse
.
OK What i was trying to do was to flash a stock recovery, i start it by running the flash-it all.bat file in the factory image zip, it changed the user interface of the bootloader after first reboot and and had an error for "archive: recovery.sig not found" (something like). the phone status shows Software Version: Modified and fastboot oem unlock dont give the confirmation.
and
now my phone wont even boot to the bootloader, everything turned black. please hellp!!!!:crying::crying:

If you can't even get into the bootloader (volume down and power) you may have to have the device serviced. Do you get a response when you type "adb devices"?

Iambenqazy said:
.
now my phone wont even boot to the bootloader, everything turned black. please hellp!!!!:crying::crying:
Click to expand...
Click to collapse
Maybe it just crashed at a black screen? Does a very long press of the power button (over 10 secs) cause it to react?
Or maybe the battery is empty? Try connecting the power supply for some time.

i did that but no response.

Iambenqazy said:
i did that but no response.
Click to expand...
Click to collapse
The very dead battery is a real possibility. The thing is, using the charger that came with the phone isn't going to help. If you think the battery being dead is a possibility, you would need to plug the phone into a USB port on a PC, that is a very slow charge. Leave it on there overnight then unplug and replug. If the led at the top of the screen lights or the battery icon shows on the screen, you have hope. At this point using the original charger should get the battery going again. In this case, plan on replacing the battery.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

Sprint htc m8 stuck at udating partition details

Stock Rom kitkat 4.4.2 rooted, unlocked, s-off. Was in recovery and accidentally hit the "middle button". Been stuck on "updating partition details" for 12 hours. I've searched and can't find the answer, but I'm relatively new so maybe I'm not looking for the right thing. Please be somewhat specific as the jargon is also something I am learning. I know nothing about partitions so I have no idea what my phone is even doing. Thanks guys. Love ya all and would be lost without you!!

kseawright76 said:
Stock Rom kitkat 4.4.2 rooted, unlocked, s-off. Was in recovery and accidentally hit the "middle button". Been stuck on "updating partition details" for 12 hours. I've searched and can't find the answer, but I'm relatively new so maybe I'm not looking for the right thing. Please be somewhat specific as the jargon is also something I am learning. I know nothing about partitions so I have no idea what my phone is even doing. Thanks guys. Love ya all and would be lost without you!!
Click to expand...
Click to collapse
What were you doing in recovery?
Have you tried holding the power button + volume up button to reboot the phone?

kseawright76 said:
Stock Rom kitkat 4.4.2 rooted, unlocked, s-off. Was in recovery and accidentally hit the "middle button". Been stuck on "updating partition details" for 12 hours. I've searched and can't find the answer, but I'm relatively new so maybe I'm not looking for the right thing. Please be somewhat specific as the jargon is also something I am learning. I know nothing about partitions so I have no idea what my phone is even doing. Thanks guys. Love ya all and would be lost without you!!
Click to expand...
Click to collapse
Hello,
I just tried the same thing in twrp...I had to press the Home button a few(maybe 10) times to get back to the main screen.
Phone booted normally afterwards.

Help..,.what if my phone dies!!!
Sloth said:
Hello,
I just tried the same thing in twrp...I had to press the Home button a few(maybe 10) times to get back to the main screen.
Phone booted normally afterwards.
Click to expand...
Click to collapse
Was trying to update firmware to Lolipop using FUU tool. 45 minutes later it still hadnt done anything so I ended task. Now HTC toolkit cant find device at all!!! Where do I start? What do I need to install/flash and where?? Is my device charging while connected to my pc or is it going to die and brick?????

kseawright76 said:
Was trying to update firmware to Lolipop using FUU tool. 45 minutes later it still hadnt done anything so I ended task. Now HTC toolkit cant find device at all!!! Where do I start? What do I need to install/flash and where?? Is my device charging while connected to my pc or is it going to die and brick?????
Click to expand...
Click to collapse
You were trying to update firmware using twrp?

First, I would suggest plugging your phone into a wall outlet and charging it until it's fully charged. You can get to the bootloader with the phone off by pressing power + volume down. Afterwards, I suggest running the latest RUU, not simply a FUU. This is done from the bootloader, not TWRP.

NO
sloth said:
you were trying to update firmware using twrp?
Click to expand...
Click to collapse
used generic fuu tool

Generic FUU
Magnum_Enforcer said:
First, I would suggest plugging your phone into a wall outlet and charging it until it's fully charged. You can get to the bootloader with the phone off by pressing power + volume down. Afterwards, I suggest running the latest RUU, not simply a FUU. This is done from the bootloader, not TWRP.
Click to expand...
Click to collapse
4.25.651.18 Full Firmware from RUU (fastboot flashable): https://www.androidfilehost.com/?fid=24052804347796613
Generic Firmware Update Utility (FUU)
These are what I used. Put phone in fastboot manually...maybe I flashed straight from bootloader and not fastboot? or am I being stupid and its the same?
ADB No Device Found
Recovery No Device Found (there was a recovery at first but I lost it after I tried to flash another image)
Fastboot No Device Found
Ok Cleaned up my computer and got someything out of fastboot:
List of devices attached
adb reboot bootloader
error: device not found
fastboot reboot bootloader
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
umm,.....huh? is it telling me what to do?

Firmware, boot image, or recovery
what do I do first?

Dont unplug
FUU utility told me if update fails not to unplug or it will brick but my battery is going to die...I'm panicking

Have Fastboot
Ok I have fastboot but no adb...now what? Im using htc toolkit...not sure if its up to date...

kseawright76 said:
Ok I have fastboot but no adb...now what? Im using htc toolkit...not sure if its up to date...
Click to expand...
Click to collapse
Run the latest RUU from bootloader.
For future reference adb works while booted to recovery or OS/rom
Fastboot works in bootloader/fastbootusb

RUU
Stock or updated firmware? My phone still runs 4.4.2... I tried everything I could think of...still no recovery or adb...Im not sure which ruu to use...please be a little more specific and thank you so much for responding. I was up until 3:30 am trying to figure this out...Im super tired, frustrated, and heartbroken.

How do i run it? Flash to where? Where should my sdk and adb be on my computer? Is there a more recent version of the tool kit? Do i want to flash from oem ruu? I used to have a bunch of different utilities on my computer and erased what I could fine but there is adb all over the place...I have a few phones...unfortunately. Do i need to relock bootloader? What about recovery? Can I create another account on my pc and avoid the other programs? Can I or do I need to sideload or push anything? I cant even tell if I still have drivers or good ones...phone is just sitting on black screen with silver htc on it

kseawright76 said:
How do i run it? Flash to where? Where should my sdk and adb be on my computer? Is there a more recent version of the tool kit? Do i want to flash from oem ruu? I used to have a bunch of different utilities on my computer and erased what I could fine but there is adb all over the place...I have a few phones...unfortunately. Do i need to relock bootloader? What about recovery? Can I create another account on my pc and avoid the other programs? Can I or do I need to sideload or push anything? I cant even tell if I still have drivers or good ones...phone is just sitting on black screen with silver htc on it
Click to expand...
Click to collapse
Was going through my sd card...i have twrp backups and Titanium backups but i dont know what to do with them. When boot into fastboot on the htc toolkit a number and "fastboot" come up on screen. That number is the folder my twrp backups are in.

Still stuck
Please help. I have tried flashing I dont know how many times and its not working. Im not sure what to flash or how. Tried in toolkit, command prompt, and fuu. Command prompt keeps telling me cant load file. I dont care what I lose or dont lose I just want my phone to work again. Still have fastboot and phone still says everything it should while booted into fastboot USB. I was on my computer all day yesterday until 4am today and had to be up to get kids to school. Im sooo tired and frustrated. PLEASE SOMEONE TAKE THE TIME TO HELP ME FIND THE RIGHT FILE AND TELL ME HOW AND WHERE TO FLASH IT. IM SORRY BUT IM STILL LEARNING