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
a clear and easy setup and command use guide needs to be put in place in the dev threads
any one can at least post what commands to use to flash system and boot img
..............
Hellzya said:
http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/ use this to install sdk and the necessary tools and drivers. Once you do that you will need to install the drivers stored on your sdcard. Run these commands to flash boot2 and system in a cmd prompt. You need to rename the .img to boot2 and system. They need to be placed in the directory you created for sdk
Fastboot flash boot boot2.img
Fastboot flash system system.img.
This has been discussed in numerous threads btw. A little searching would have lead you to what you needed
sent from my streak7
Click to expand...
Click to collapse
well i should of said i am working on a soft brick i am stuck in apx mode
also adb is not the issue i clearly stated nvflash guide not adb
also i would apprciate if you would stay away from this thread i already see people like you telling others to search and you didnt even answer my question ,...not even related so that post was not needed
Hey no problem man.
sent from my streak7
I just noticed it now, grab it here:
S-OFF
recovery-clockwork-5.0.2.0-buzz.img
S-ON / fake-flash
recovery-clockwork-5.0.2.0-buzz.zip
Haven't tested it, try it at your own risk but should be safe
S-OFF: flash with fastboot with
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img
S-ON: simply rename to update.zip and put it on your SD card
Eh!!! Confused!!!!! cwm 5.0.2.0 been around for ages????
"sent from me2u"
I just didn't see it posted lol, did a search and didn't see the official 5.0.2.0, only older and customized versions
Can anyone help me install it?
I've installed v4.0.1.4, but I can't install it
I want install from Ubuntu please...
Regards!!
Cwm can be flashed when s-on?
I don't have wildfire... my friend has...
If it works ill flash it from his s on hboot...
Edit: his hboot is 1.01.0002
Sent from my MB525 using xda premium
So...what's new in this version?
(Also, is there a way to change the color of text in the recoveries, I want the orange color back )
Qarl said:
Can anyone help me install it?
I've installed v4.0.1.4, but I can't install it
I want install from Ubuntu please...
Regards!!
Click to expand...
Click to collapse
Assuming you have S-OFF, install the Android SDK and just boot into the bootloader, then select fastboot and use the command in the first post...
nogoodusername said:
Cwm can be flashed when s-on?
I don't have wildfire... my friend has...
If it works ill flash it from his s on hboot...
Edit: his hboot is 1.01.0002
Sent from my MB525 using xda premium
Click to expand...
Click to collapse
With S-ON, you can only use the fake flash by renaming the .zip to update.zip and "flash" it from the stock recovery to launch CWM...
nejc121 said:
So...what's new in this version?
(Also, is there a way to change the color of text in the recoveries, I want the orange color back )
Click to expand...
Click to collapse
No idea
Kwen said:
Assuming you have S-OFF, install the Android SDK and just boot into the bootloader, then select fastboot and use the command in the first post...
Click to expand...
Click to collapse
Yes, I've S-OFF.
Turn ON my device on Fastboot, it's connected to computer obviously!
If I run:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-legend.img
The console says that "fastboot" isn't a valid command.
If I am in Android SDK directory and run:
Code:
./adb devices
The console don't found any device.
Where is the problem?? Is this usable on Ubuntu? I'm use it.
Regards and sorry my bad English
See http://developer.android.com/guide/developing/device.html
"If you're developing on Ubuntu Linux, you need to add a udev rules file that contains a USB configuration for each type of device you want to use for development. In the rules file, each device manufacturer is identified by a unique vendor ID, as specified by the ATTR{idVendor} property. For a list of vendor IDs, see USB Vendor IDs, below. To set up device detection on Ubuntu Linux:"
Qarl said:
Yes, I've S-OFF.
Turn ON my device on Fastboot, it's connected to computer obviously!
If I run:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-legend.img
The console says that "fastboot" isn't a valid command.
If I am in Android SDK directory and run:
Code:
./adb devices
The console don't found any device.
Where is the problem?? Is this usable on Ubuntu? I'm use it.
Regards and sorry my bad English
Click to expand...
Click to collapse
This word in'valid
Change Legend to buzz
fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img
Click to expand...
Click to collapse
If you're on Windows, have you that in the recovery installation folder?:
AdbWinApi.dll, adb.exe, fastboot.exe and recovery-X.img
Good call, copy paste error
Also if you don't have the fastboot command, you'll need to download the "Android SDK Platform Tools" (under "Tools") from the SDK manager (how did you get adb working though without the platform tools?!)
Should be under the same directory...
Just rename the zip to pc49img.zip making sure you DONT name it pc49img.zip.zip place it on the root of your sdcard (ie.not in any folders) boot your phone into hboot via volume down and power whilst phone is off and when prompted press volume up to update then reboot into recovery to see your new cwm. SIMPLES.
"sent from me2u"
First, I go to "android-sdk/platform-tools" with the terminal.
Then, run this command:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img
And the terminal return this:
Code:
< waiting for device >
What's happen? If I run "adb devices", my HTC Wildfire is founded.
Regards!
Did you highlight fastboot in the bootloader/hboot and pressed power to select it?
It should say fastboot usb plug or something like that
Kwen said:
Did you highlight fastboot in the bootloader/hboot and pressed power to select it?
It should say fastboot usb plug or something like that
Click to expand...
Click to collapse
Problem solved!!!
I believed that the device reboots to fastboot when the command executed it.
Sorry ¬¬
Thank you very much!
slymobi said:
Just rename the zip to pc49img.zip making sure you DONT name it pc49img.zip.zip place it on the root of your sdcard (ie.not in any folders) boot your phone into hboot via volume down and power whilst phone is off and when prompted press volume up to update then reboot into recovery to see your new cwm. SIMPLES.
"sent from me2u"
Click to expand...
Click to collapse
I think you'll need a flashable zip, the one koush provides is just a img and a fake flash .zip
@Kwen, yes copy/past error xD
how can i call the yes/no event in this recovery with an updater-script?
other phones have recovery that have a list of comand,that you can add to an updater-script to call some recovery functions.
also this?
slymobi said:
Just rename the zip to pc49img.zip making sure you DONT name it pc49img.zip.zip place it on the root of your sdcard (ie.not in any folders) boot your phone into hboot via volume down and power whilst phone is off and when prompted press volume up to update then reboot into recovery to see your new cwm. SIMPLES.
"sent from me2u"
Click to expand...
Click to collapse
How do I do this if the OS itself is crashed and I get a white screen and HTC logo???
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..
Here is the story in a nutshell I flashed xdabbeb's bootstack, then his rom. Then I did something stupid such as wipe everything folks, I mean everything. So my phone then restarted and I am able to get into recovery twrp 2.7.
I have tried in twrp to sideload, mount neither which work.
I have my drivers installed it says in device manager when I plug the phone up for download mode
android- galaxy nexus adb
and under ports it says LGE AndroidNet for VZW ADB Interface com41
I tried lg flash tool, tried with old vs98010b rom
pid:
imei:
model:
dll: vs980
bin: vs98010b_13.tot
swv:
swov:
model information check fail!
00000000
I really need help guys, are there any adb commands I can type or are there any drivers I need to install
Ok when i hold the up and plug in it takes me to fastboot
[500] fastboot mode started
[550] udc_start()
[720] reset
[730] portcharge
[740] reset
[750] portcharge
and the device only registers as android under other on my computer
i've installed lg drivers
How can you fastboot flash? When I hold up and plug in for fastboot my computer wont register a driver just shows android what are the commands and how do I use fastboot
timenewton said:
How can you fastboot flash? When I hold up and plug in for fastboot my computer wont register a driver just shows android what are the commands and how do I use fastboot
Click to expand...
Click to collapse
Download mode is not going to work because the laf partition (this allows for download mode to work) is wiped when you flash xdabbeb's bootstack in favor of fastboot mode.
I suggest you pm xdabbeb; he will guide you on the steps to using the necessary fastboot commands to get your phone working again. He's already helped a few people that were in the same situation as you are in right now.
Fastboot is good because you can write certain partitons at a time without having to .tot and wipe your whole phone.
You could also flash his xdabbeb_vs98024a_laf.zip http://www.androidfilehost.com/?fid=23329332407586639 file in TWRP 2.7 to restore download mode, but you will end up wiping your whole phone by using the LG Flash Tool, even your sd card when you restore your phone.
You said you "wiped everything", I'm not sure if that means your sd card too, if so, then that might be the easiest thing to do since you still have access to recovery. You will need an otg cable and a flash drive to mount the flash drive in TWRP 2.7 and flash the file, unless you can side load the file with adb.
Either way, like I mentioned earlier, it might be a good idea to pm xdabbeb first.
Hey my phone is already wiped even sdcard, but the thing is i cant flash that file because I can not get it on my phone. So ill ask xdabbeb the fastboot commands. Yeah and I read about the otg cable, ordered one of those babies should be here this saturday and hopefully it will mount my flash drive in that case id be golden untill then ill see what mr xdabbeb has to say.
cant sideload
everytime i try to sideload the file it just says cant read file or something like that
And I really appreciate you responding. Always nice to get support from somebody when your just sitting here and your phone seems like it hasnt been working for an eternity. Almost depressing not hearing from anyhbody and just seeing all the views but no replys. Thank you
Hey there...Fastboot is about as basic/simple/reliable as it comes. If you have adb/fastboot set up properly then command is:
fastboot flash <partition> <filename>
for example:
fastboot flash recovery recovery.img
In your case, you claim to have a working recovery (twrp 2.7), but are unable to copy files from your computer to your phone. It sounds like you don't have the proper drivers installed so that you can use adb from recovery. This is a common/known issue with windows and I believe I replied to you in the rom thread already about this, but you need to install/use Koush's universal adb driver and simply copy the rom file over to your phone using the following command:
adb push <filename> /sdcard/
After you have the file there you can flash it as normal in recovery.
If you want to use a kdz/tot method to restore your phone, just download the laf zip file from my thread, extract the laf.img file from the zip, and use the following command to put it in place:
fastboot flash laf laf.img
Then you can go about the tot restore method described in the thread here. You don't need to put the tot file itself on your phone. It just needs to be on your computer.
I get to sdk and open cmd
type adb devices it says
List of devices attached
0215817d960ce580 sideload
Then I type adb push rom.zip /sdcard/
error: closed
When phone is plugged in for adb device manager says under android device- Google galaxy Nexus ADB Interface
I have universal drivers installed and I goto device manger to update drivers where clockworkmod is installed and it doesnt do anything
Fastboot it says in other devices in device manager
Android
PCI Data Acquisition and Signal Processing Controller
I type fastboot flash recovery laf.img
<waiting for device>
timenewton said:
I get to sdk and open cmd
type adb devices it says
List of devices attached
0215817d960ce580 sideload
Then I type adb push rom.zip /sdcard/
error: closed
When phone is plugged in for adb device manager says under android device- Google galaxy Nexus ADB Interface
I have universal drivers installed and I goto device manger to update drivers where clockworkmod is installed and it doesnt do anything
Fastboot it says in other devices in device manager
Android
PCI Data Acquisition and Signal Processing Controller
I type fastboot flash recovery laf.img
<waiting for device>
Click to expand...
Click to collapse
Wait, I'm confused here a little bit. Are you trying to do sideload mode in TWRP or are you using fastboot mode?
And the command you typed is not correct fastboot flash recovery laf.img...you don't want to do that...this would flash the laf.img in your recovery partition.
xdabbeb referenced two methods to you...one was pushing a Rom to your sdcard and then flashing that Rom in TWRP to get your phone booting...the other was to flash the laf.img file and do a .tot if that's what you prefer.
It seems like you want to do a .tot restore, so do the second method xdabbeb suggested.
Get into fastboot mode and type fastboot flash laf laf.img
Make sure you use the correct laf.img...you can extract it from the zip in my previous post/link.
After this your download mode should be working again.
I was trying either one
For fastboot I downloaded xdabbebs laf
the image file in his file is laf.img, if thats not the right file then where is the recovery.img
So the recovery.img would have been one that i made?
and laf is so I can us lg tool to tot flash?
Even when i try to flash the laf it keeps saying waiting for device. I have the drivers koushu installed and lg
timenewton said:
I was trying either one
For fastboot I downloaded xdabbebs laf
the image file in his file is laf.img, if thats not the right file then where is the recovery.img
So the recovery.img would have been one that i made?
and laf is so I can us lg tool to tot flash?
Click to expand...
Click to collapse
Yes, download xdabbeb's laf.img, it's the link I gave you originally. You will have to take out the laf.img file from the zip file that is called xdabbeb_vs98024a_laf.zip
The recovery command he gave was just an example, there was no need for you to use it.
Yes, flashing the laf.img will fix your download mode and you will be able to do the .tot method.
What am I suppose to do about it saying wiating for device, its not detecting it
timenewton said:
What am I suppose to do about it saying wiating for device, its not detecting it
Click to expand...
Click to collapse
That sounds like a driver issue. Reboot your computer and turn off the phone and start again. See if that helps. You can also remove the drivers and re-install...I suggest you reboot your computer every time you install new drivers.
EDIT:
Are you using a newer adb.exe from your android sdk? If you have ioroot25 installed on your computer I suggest you use the folder/files from there. It has a newer adb.exe in there; put your laf.img file in that folder too if you do use that instead, and run the command prompt from within that folder.
Ok when my phone is plugged into my comp, im on win 7 it shows up as android under other devices when started in fastboot mode. When I browse to the driver location to load for the android it says no driver found for it.
Yes i just installed the sdk like 2 days ago so I know its current.
As far as the driver situation, why would I need to uninstall if it isnt even installing a driver.
This is terrible
timenewton said:
Ok when my phone is plugged into my comp, im on win 7 it shows up as android under other devices when started in fastboot mode. When I browse to the driver location to load for the android it says no driver found for it.
Click to expand...
Click to collapse
timenewton said:
Yes i just installed the sdk like 2 days ago so I know its current.
As far as the driver situation, why would I need to uninstall if it isnt even installing a driver.
This is terrible
Click to expand...
Click to collapse
For me it shows up under "ADB Interface", but I don't have the universal driver installed.
I didn't realize it wasn't installing the driver for you.
You have to get that driver going or you won't be able to get your phone fixed. Maybe try a different usb port or a different computer.
Man yeah mine doesnt look at all like that. Im uninstalling lg driver and universal one and clearing temp folder. Then restart and reinstall maybe that will work. So its just the koushu driver that works for fastboot and adb right?
timenewton said:
Man yeah mine doesnt look at all like that. Im uninstalling lg driver and universal one and clearing temp folder. Then restart and reinstall maybe that will work. So its just the koushu driver that works for fastboot and adb right?
Click to expand...
Click to collapse
Yeah, it should work. I've read posts by others stating that it works.
Yep just reinstalled the universal drivers, plug phone up into fastboot and still get the same result
Can you perhaps send me that driver you have? Because I know if you have that one and it works for you it SHOULD work for me. Murphs law is killing me. I can pm you my email address