Related
I updated my phone's SPL to "Danger SPL" and now my phone wont turn back on! I press power and the black Android screen with the little green android next to it comes up but wont boot my phone! The only thing I can do is get the white screen with the 3 android's skateboarding by pressing camera + power.
Ontop of that, I had tried to update my phone's recovery image too, and I erased the old one and now it would let me upload the NEW one! So not only do I have NO PHONE but NO RECOVERY either!
What do I do!? HELP!
can you get into fastboot? (back+power)
if you can, get adb running and flash your recovery image with fastboot
you are gonna have to fast boot in the screen with the three androids on it, either a rom or a recovery
guess you betta learn how to use adb
Yea I can get into fastboot, thats the ONLY thing I can get into. How do I flash my recovery image?
http://forum.xda-developers.com/showthread.php?t=566669
boot your phone into fastboot. plug in your usb cable to your pc. this should change the fastboot icon on the screen to fastboot usb. from there, load up adb on your pc and make sure you have the fastboot option available by typing fastboot devices. it should list your phone. once that is good, type:
fastboot flash recovery and the correct name of your recovery file.
for example:
fastboot flash recovery recovery-RA-dream-v1.2.3.img
**also note...put the recovery image in your android sdk\tools folder**
this should give you a recovery to boot into.
if you dont have adb on your pc, read this and follow the instructions
http://forum.xda-developers.com/showthread.php?t=532719
I did that already, it wont work.
C:\Android>fastboot flash recovery recovery123.img
error: cannot load 'recovery123.img'
i am gonna be the one to ask this question but did you put .s between 123 like 1.2.3.
you need to be in the tools directory, not the android directory.
c:\Android\tools>fastboot flash recovery recovery-RA-dream-v1.2.3.img
and you need the recovery file IN your tools folder for it to be found as well.
No I didn't put .'s between each number I renamed my file recovery123.img so thats the way I put it in.
ok, so go to the correct directory and input what you had the first time, WITH the file IN that same folder. and then report back.
i justed rename my recovery the shortest way i can like for amon ra"s i just put amon, less typing is always better
It says C:\Android\tools is not recognized as an internal or external command, operable program or batch file.
from your c:\> prompt type this:
cd c:\android\tools
(this is assuming you have the android sdk in the c:\android folder on your pc)
if it is saying its not a folder, then that is not where you installed the android sdk.
knowfear said:
and you need the recovery file IN your tools folder for it to be found as well.
Click to expand...
Click to collapse
This is not true. You can have it anywhere as long as you can cd to it and you have your fastboot.exe in the system32 folder.
Look... this is so easy I'm wondering why this has gone on for more than 1 page.
First thing is first. I'm betting that you don't have the new ADB driver for the Danger SPL.
If you refer to this page:
http://sapphire-port-dream.googlecode.com/
it states:
If you use the above SPL you will need new drivers for Windows. They are located here.
Click to expand...
Click to collapse
Then put your fastboot.exe in c:\windows\system32 directory.
Whatever recovery file you're trying to use rename it to "recovery.img" and put it on C:\ then open command prompt (start > run > cmd > enter)
cd c:\
fastboot flash recovery recovery.img
and it should show a progress bar in the top right corner.
While the dos screen shows 'sending' and then 'writing'.
After you see ...done a second time then type:
fastboot reboot
and it should reboot just fine... but you may need to do that "3 finger solute" (talk, end, menu) while holding the camera button down to get into your recovery. You should be able to flash your rom. Just make sure the rom doesn't have a radio update (unless it's the 2.22.19.26I).
what he said.
Binary100100 said:
This is not true. You can have it anywhere as long as you can cd to it and you have your fastboot.exe in the system32 folder.
Look... this is so easy I'm wondering why this has gone on for more than 1 page.
First thing is first. I'm betting that you don't have the new ADB driver for the Danger SPL.
If you refer to this page:
http://sapphire-port-dream.googlecode.com/
it states:
Then put your fastboot.exe in c:\windows\system32 directory.
Whatever recovery file you're trying to use rename it to "recovery.img" and put it on C:\ then open command prompt (start > run > cmd > enter)
cd c:\
fastboot flash recovery recovery.img
and it should show a progress bar in the top right corner.
While the dos screen shows 'sending' and then 'writing'.
After you see ...done a second time then type:
fastboot reboot
and it should reboot just fine... but you may need to do that "3 finger solute" (talk, end, menu) while holding the camera button down to get into your recovery. You should be able to flash your rom. Just make sure the rom doesn't have a radio update (unless it's the 2.22.19.26I).
Click to expand...
Click to collapse
^just follow this step-by-step. You should be good to go.
Nice, succinct response binary.
innerspace said:
^just follow this step-by-step. You should be good to go.
Nice, succinct response binary.
Click to expand...
Click to collapse
No problem. I just hate it when something this simple drags onto multple pages. Call it a peev. So many people get intimidated by the "Danger SPL" because they don't want to risk bricking their phones. The odds of bricking your phone are extremely small if you follow directions and read everything. And sure the possibility of accomplishing this by different means exists. But when you try to tell someone to put this file in that folder and type in the full names of the files to include all the dots and dashes, it's going to get confusing and intimidating and thus these posts keep popping up.
If someone follows those very short and simple directions they shouldn't have any problems. Granted that "**** happens" and things don't always go as they should. So in that case, search for your answer. If you've searched on XDA then search Google. Out of the MILLIONS of G1's that have been sold, I am fairly certain that someone out there has had a similar problem. If not then you and your phone are literally "1 in a million" (technically it was 1 in 1.5 million a year ago so you can bet that it's well over 2 if not 3 million by now). And if you really fall into that catagory then please post a new thread (in the appropriate catagory of course) .
well the good news is u didnt brick ur phone but try a enter adb and do a nadroid back up if u hav 1 that will bring u back 2 the way u want it
either flash a nadroid or flash dreaming.nbh....i had the same problem and a nadroid worked just fine
well i happened to have some problems with a theme i was using that made the icons appear themed even in cyanogens roms , and i was told that i needed to flash the htc adp image to fix that
the problem comes here i flashed the htc adp image but i forgot to read what cyanogen said that i had to flash his rom before rebooting
so i just found that cyanogen gives us something to follow just in case it happens what happened to me here http://wiki.cyanogenmod.com/index.php/RE-recovery-img
i went to ''if you currently have an engineering or a Hard SPL'' and followed all the procedures until i got to number 4 where it asks me to Change directory to where you have saved your recovery image..i've tried lots of paths but none seems to work...ADB NOOB HERE so please help
when you didnt follow the process, you lost root.
you have to start from scratch.
.............................................................................
i typed
cd C:\recovery-RA-dream-v1.5.2.img
and it tells me the directory name is invalid what am i doing wrong?
recovery image is not a directory, it'a file. What are you trying to do?
borodin1 said:
recovery image is not a directory, it'a file. What are you trying to do?
Click to expand...
Click to collapse
im trying to flash amon ra recovery via fastboot
Easier to do it from adb
Code:
adb remount
adb shell flash_image recovery C:\recovery-RA-dream-v1.5.2.img
reboot
Just a tip: I usually rename files into something easier to type, like ra152.img. Up to you though.
You can also do it from terminal (place file on the root of sdcard)
Code:
su
flash_image recovery /sdcard/filename.img
reboot
If you must do it via fastboot
Start your phone in fastboot mode (camera/power)
Code:
fastboot flash recovery recovery-RA-dream-v1.5.2.img
fastboot reboot
borodin1 said:
Easier to do it from adb
Code:
adb remount
adb shell flash_image recovery C:\recovery-RA-dream-v1.5.2.img
reboot
Just a tip: I usually rename files into something easier to type, like ra152.img. Up to you though.
You can also do it from terminal (place file on the root of sdcard)
Code:
su
flash_image recovery /sdcard/filename.img
reboot
If you must do it via fastboot
Start your phone in fastboot mode (camera/power)
Code:
fastboot flash recovery recovery-RA-dream-v1.5.2.img
fastboot reboot
Click to expand...
Click to collapse
i would do this..but i cant since i messed up when flashing the htc adp image im following cyanogens tutorial http://wiki.cyanogenmod.com/index.php/RE-recovery-img and it says that i have to flash the new recovery through fastboot , and the part im stuck at is step 4 where he says that i need to Change directory to where you have saved your recovery image
if you can get into the main phone operating system via a boot up then use linda file manager to move them
when i type this
fastboot recovery recovery-RA-dream-v1.5.2.img
i get this message "error: cannot load 'recovery-RA-dream-v1.5.2.img
then i changed the directory to where the recovery image was and when i tried to flash i got this message
'fastboot' is not recognized as an internal or external command, operable program or batch file
Not sure, I'm not anywhere near my computer. Try putting your recovery image into different locations (i always put it on desktop) and rename it to something simpler, without any punctuation or special characters (i suggest rec.img). Also... make absolutely sure that you're NOT naming it rec.img.img . Make sure that your PC is not hiding your extensions.
Then, connect your phone to the computer, start your phone in fastboot mode (not Hboot or serial, if you see serial or Hboot on your screen then tap return button)
In command line type
Code:
fastboot devices
to make sure that you're connected
then type
Code:
cd desktop
your directory should change to something like C:\user\desktop (make SURE there are no spaces anywhere in user name, fastboot has problem with that. I had to rename my account to "EugeneAndLiz"a from "Eugene and Liza" because of that)
then type
Code:
fastboot recovery rec.img
fastboot reboot
and let us know how did it go for you. I'l be lurking around here for a while, hopefully we can resolve this.
Good luck
borodin1 said:
Not sure, I'm not anywhere near my computer. Try putting your recovery image into different locations (i always put it on desktop) and rename it to something simpler, without any punctuation or special characters (i suggest rec.img). Also... make absolutely sure that you're NOT naming it rec.img.img . Make sure that your PC is not hiding your extensions.
Then, connect your phone to the computer, start your phone in fastboot mode (not Hboot or serial, if you see serial or Hboot on your screen then tap return button)
In command line type
Code:
fastboot devices
to make sure that you're connected
then type
Code:
cd desktop
your directory should change to something like C:\user\desktop (make SURE there are no spaces anywhere in user name, fastboot has problem with that. I had to rename my account to "EugeneAndLiz"a from "Eugene and Liza" because of that)
then type
Code:
fastboot recovery rec.img
fastboot reboot
and let us know how did it go for you. I'l be lurking around here for a while, hopefully we can resolve this.
Good luck
Click to expand...
Click to collapse
im going to tell you step by step what i do
turn the phone off
hold power and back
i see the androids on skateboards and it says fastboot in red letters
i connect my phone via usb then the name changes to fastboot usb
run the cmd
once there i type where adb is located which is cd C:\android-sdk-windows\tools
then when i type fastboot devices
i see the serial number of my phone
now when i type cd desktop i get this message "the system cannot find the path specified"
and if i ignore that and try to flash
fastboot flash recovery rec.img (yes i did rename the recovery image)
it says that it cant load 'rec.img'
Got it! Put your image file into the "tools' folder and once you see your device in the fastboot just flash it from there
Code:
cmd
cd C:\android-sdk-windows\tools
fastboot devices
fastboot flash recovery rec.img
fastboot reboot
Sorry about all this complication... the main idea is that your recovery needs to be in the same directory as you're when you're flashing. So if earlier you went to tools folder then your file needs to be there as well.
Try it out.
it worked...it said sending 'recovery' <4456 KB>... okay
writting 'recovery'...okay
fastboot reboot
then when i go to the system recovery..its the same htc adp one
i tried to flash amon ra's recovery and cyanogens
oh nevermind..instead of rebooting the phone i just unpluged the device and wnet directly into the system recovery and YES i have cyanogens recovery thank you so much borodin1
hmmmm that's weird because you got confirmation....
1. Did you download right recovery? You had to becaue you tried 2 of them and you can only make the same mistake once lol
2. AmonRA's recovery has the same image in the background as HTCs, are you sure that it's still HTC's recovery?
Other then that... I'm clueless
Can you get su in the adb shell? Try flashing it from adb....
You got me stomped on this.... Anyone else wants to take a shot at this????
i dont know what happened but when i flashed the recovery image on fastboot and then rebooted the phone...then turn off the phone and went to the system recovery and the htc adp recovery appeared...blue letters and the scrolling options..but when i did not reboot the phone after flashing the image and went directly to the system recovery i had the recovery i flashed...then i applyed the updateand everything is good now
weird uh?
will that new recovery stick?... I'm starting to remember something but it's vague... give me few minutes Reboot couple of times into recovery and back for now and see what happens...
it did stick..i just rebooted into recovery and i have the new recovery..haha
Great! Happy modding!
Well, long story short my friend royally screwed up his phone.
He screwed up the kernel and even the Recovery. Don't ask how.
We even connected the phone and ADB didn't work on bootloader. But after we went into fastboot and tried a restart it worked. So.. we used fastboot to restore the phone.
Notes before you start: Use command prompt and cd to the directory for your sdk tools. In my case, I simply used the 'data' folder for the Toolkit that was released here that had the sdk tools like adb.exe and fastboot.exe . MAKE SURE you copy the associated recovery zips and ROM zips to the very same folder to prevent complications and for the commands to work like a charm. Finally, uninstall the drivers for your phone and reinstall them (if you need to only, as we had connection issues.. yep he royally screwed up).
Boot into bootloader then select fastboot and hit the power button. Keep it on the fastboot screen. Now you can proceed.
Here is what I did:
fastboot erase cache
fastboot flash recovery recovery.zip *rename your recovery zip to 'recovery.zip' and make sure it's in the same folder as the sdk tools*
You can now then boot into recovery and write the ROM or even use fastboot to write it with the following:
fastboot flash zip rom.zip *once again, rename your ROM zip to rom.zip*
I only put this out there to help those who screwed up their recovery and can't even get the Toolkit to execute commands using ADB.
Good luck!
Yeah, fastboot on pc then in command you clear cache and install recovery. I got into a boot cycle and this fixed it.
lopuandroid said:
Yeah, fastboot on pc then in command you clear cache and install recovery. I got into a boot cycle and this fixed it.
Click to expand...
Click to collapse
Glad it worked. Yeah, for some reason my friend's computer was being really fussy. It wouldn't detect the phone or anything, and ADB was rendered useless. We reinstalled the drivers so many times.. And used 2 different laptops.. Thank God fastboot worked. Hopefully this helps anyone else in the same **** zone. I know the heart sinking feel when your Recovery won't work and you only get the bootloader to work..
Hi guys. I wanted 2 restore my HTC One firmware through RUU. I followed nkk71's guide to do so. So i downgraded the bootloader to 1.44 to flash the RUU. However, after the downgrade, my One isnt recognized by fastboot. Whenever i type any command, its Waiting for device........... I have installed HTC Sync and tried uninstalling also. No success.
But this laptop has both USB 3.0 ports and is on Win 8.1 Is the USB 3.0 port the problem??
But on HBOOT 1.54, the phone was easily recognized.'
Thanks sincerely for any help
You need the newer hboot with Windows 8.1.
An alternative is a Linux live CD.
raghav kapur said:
Hi guys. I wanted 2 restore my HTC One firmware through RUU. I followed nkk71's guide to do so. So i downgraded the bootloader to 1.44 to flash the RUU. However, after the downgrade, my One isnt recognized by fastboot. Whenever i type any command, its Waiting for device........... I have installed HTC Sync and tried uninstalling also. No success.
But this laptop has both USB 3.0 ports and is on Win 8.1 Is the USB 3.0 port the problem??
But on HBOOT 1.54, the phone was easily recognized.'
Thanks sincerely for any help
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2610783&page=2
nkk71 said:
http://forum.xda-developers.com/showthread.php?t=2610783&page=2
Click to expand...
Click to collapse
thanks a lot for your suggestion. Win7 did the trick. But I have another question. Wen im doing the push adb command for installing the guru bootloader reset zip, its not happening.
What I've done is:
1) Put the guru bootloader reset zip in fastboot folder
2) adb push xxxx.zip (Ive just dragged the zip file from fastboot folder to command prompt)
3) Then I get a whole huge bunch of letters
Is it possible 2 simply drag the zip file to my virtual sd card and then flash from CWM, the way its done for flashing a rom
Or could you please tell me what command to put to flash the guru bootloader reset from command prompt
Really sorry if im irritating you
You should paste your results from adb push to get a better answer
raghav kapur said:
thanks a lot for your suggestion. Win7 did the trick. But I have another question. Wen im doing the push adb command for installing the guru bootloader reset zip, its not happening.
What I've done is:
1) Put the guru bootloader reset zip in fastboot folder
2) adb push xxxx.zip (Ive just dragged the zip file from fastboot folder to command prompt)
3) Then I get a whole huge bunch of letters
Is it possible 2 simply drag the zip file to my virtual sd card and then flash from CWM, the way its done for flashing a rom
Or could you please tell me what command to put to flash the guru bootloader reset from command prompt
Really sorry if im irritating you
Click to expand...
Click to collapse
you should look at the guide in a little bit more detail (including post 7, which has "visuals" both of the command prompt and the screenshots, so you can see what kind of output you get.
the command is "adb push <name of file>.zip /data/media/" <- yes, you need to mention the destination
here's a little trick it seems many are missing: in the command prompt type:
Code:
C:\ADB3>adb push g
then press TAB, and looky here:
Code:
C:\ADB3>adb push Guru_Bootloader_Reset_1.0.zip
then you can continue and type "<space>/data/media/"
if there is more than one file that starts with "g" press TAB again (and again) until the correct file is displayed.
nkk71 said:
you should look at the guide in a little bit more detail (including post 7, which has "visuals" both of the command prompt and the screenshots, so you can see what kind of output you get.
the command is "adb push <name of file>.zip /data/media/" <- yes, you need to mention the destination
here's a little trick it seems many are missing: in the command prompt type:
Code:
C:\ADB3>adb push g
then press TAB, and looky here:
Code:
C:\ADB3>adb push Guru_Bootloader_Reset_1.0.zip
then you can continue and type "<space>/data/media/"
if there is more than one file that starts with "g" press TAB again (and again) until the correct file is displayed.
Click to expand...
Click to collapse
i keep getting device not found error
nkk71 said:
you should look at the guide in a little bit more detail (including post 7, which has "visuals" both of the command prompt and the screenshots, so you can see what kind of output you get.
the command is "adb push <name of file>.zip /data/media/" <- yes, you need to mention the destination
here's a little trick it seems many are missing: in the command prompt type:
Code:
C:\ADB3>adb push g
then press TAB, and looky here:
Code:
C:\ADB3>adb push Guru_Bootloader_Reset_1.0.zip
then you can continue and type "<space>/data/media/"
if there is more than one file that starts with "g" press TAB again (and again) until the correct file is displayed.
Click to expand...
Click to collapse
can I just copy the bootloader reset zip to my internal storage through ES File Explorer and then flash using CWM ?
raghav kapur said:
i keep getting device not found error
Click to expand...
Click to collapse
are you in recovery or booted up rom (with USB debugging enabled?), anyway if you can see your phone with MTP in Windows, then fine just drag it onto the phone.
nkk71 said:
are you in recovery or booted up rom (with USB debugging enabled?), anyway if you can see your phone with MTP in Windows, then fine just drag it onto the phone.
Click to expand...
Click to collapse
It initially wasn't working thru adb. So I just decided 2 boot the phone after that. The phone is booting fine. So this is what I plan to do :
1) Copy the boot loader zip to internal storage
2) Boot CWM
3) Flash the zip
4) Lock the Boot loader and remove tampered
5) Run RUU when the phone is in fastboot
Is this the correct procedure ?
raghav kapur said:
It initially wasn't working thru adb. So I just decided 2 boot the phone after that. The phone is booting fine. So this is what I plan to do :
1) Copy the boot loader zip to internal storage
2) Boot CWM
3) Flash the zip
4) Lock the Boot loader and remove tampered
5) Run RUU when the phone is in fastboot
Is this the correct procedure ?
Click to expand...
Click to collapse
yep, sounds good.
STAY S-OFF
nkk71 said:
yep, sounds good.
STAY S-OFF
Click to expand...
Click to collapse
REALLY THANKS A LOOT. I really don't know how to thank you enough. My phone is back to normal
One last question: HTC UAE has told me that the phone has to be S-ON to be repaired for free. So simply running that command provided in the guide will get it S-ON right ?
raghav kapur said:
REALLY THANKS A LOOT. I really don't know how to thank you enough. My phone is back to normal
One last question: HTC UAE has told me that the phone has to be S-ON to be repaired for free. So simply running that command provided in the guide will get it S-ON right ?
Click to expand...
Click to collapse
yes as mentioned in the guide, however you have to do this before updating to 3.xx because hboot 1.55 is patched for that (as mentioned in the guide)
so if you're just sending to repair, and think it's necessary go ahead with s-on. after that you can take OTA updates... then again why bother, i'm sure they'll update it in the repair center.
So I downloaded the stock from from the HTC site and for some reason it won't work when I try to recover it. The install works and all but when I go try an it starts to install, it says that I have the wrong RUU. Even though my phone is 2.27.651.6 and the ROM is 2.27.651.6, it says I have the wrong one. I don't understand it. Can someone help me out? I'm US.
The RUU's are a complete headache and won't work if your firmware has even started to lose it's factory fresh scent. Your best bet will be extracting the rom.zip from the RUU and proceeding from there. There's a lot of methods I've seen to go about extracting, but some of them make things difficult when they don't have to be.
Just start the RUU and let it do its longgggg startup and just leave it be when the actual program's interface is visible.
Now just open up Task Manager and find the process on the first page relating to the RUU.
Simply right-click and "open file location." Then, copy and paste all the goodies you want to a folder and directory of your choosing.
The rom.zip is all that is necessary, but I just used the whole folder as a my new default directory since it has everything you will ever need when working with your HTC.
This will reset everything to complete stock so backup anything important to you because it will be gone. Also, don't worry about un/locking your bootloader. It doesn't matter and just adds wasted time.
Plug your phone in to your PC and open the folder with all the RUU pieces, or at least a folder that has all the fastboot tools and the rom.zip.
Shift right-click in blank space and open a command prompt and enter-----
fastboot oem rebootRUU
wait for the reboot to the black RUU loader screen and then enter----
fastboot flash zip rom.zip
Let it do it's thing and you should be set.
seanc1991 said:
The RUU's are a complete headache and won't work if your firmware has even started to lose it's factory fresh scent. Your best bet will be extracting the rom.zip from the RUU and proceeding from there. There's a lot of methods I've seen to go about extracting, but some of them make things difficult when they don't have to be.
Just start the RUU and let it do its longgggg startup and just leave it be when the actual program's interface is visible.
Now just open up Task Manager and find the process on the first page relating to the RUU.
Simply right-click and "open file location." Then, copy and paste all the goodies you want to a folder and directory of your choosing.
The rom.zip is all that is necessary, but I just used the whole folder as a my new default directory since it has everything you will ever need when working with your HTC.
This will reset everything to complete stock so backup anything important to you because it will be gone. Also, don't worry about un/locking your bootloader. It doesn't matter and just adds wasted time.
Plug your phone in to your PC and open the folder with all the RUU pieces, or at least a folder that has all the fastboot tools and the rom.zip.
Shift right-click in blank space and open a command prompt and enter-----
fastboot oem rebootRUU
wait for the reboot to the black RUU loader screen and then enter----
fastboot flash zip rom.zip
Let it do it's thing and you should be set.
Click to expand...
Click to collapse
OK but when I get to the TOS on the RUU installer, and I click NEXT, it...crashes.