I did the most stupidest thing and tried to place a boot animation zip from the nexus 4 onto my phone. I renamed it ATT_Bootanimation.zip (like the normal bootanimation) and placed it in system/customize/resource. Now the phone wont boot. I tried going to TWRP's file manager, deleting the new zip and copying the old zip back but it still doesn't work. Can anyone help me please?
Edit: It also appears that TWRP can't mount sd card onto my computer so I can't place the ROM file onto my phone to flash. Can someone confirm this or teach me another way to fix this?
JustinBieber said:
I did the most stupidest thing and tried to place a boot animation zip from the nexus 4 onto my phone. I renamed it ATT_Bootanimation.zip (like the normal bootanimation) and placed it in system/customize/resource. Now the phone wont boot. I tried going to TWRP's file manager, deleting the new zip and copying the old zip back but it still doesn't work. Can anyone help me please?
Edit: It also appears that TWRP can't mount sd card onto my computer so I can't place the ROM file onto my phone to flash. Can someone confirm this or teach me another way to fix this?
Click to expand...
Click to collapse
Reflash rom without wipe using adb sideload command. Vitrual sdcard on this phone can't be mounted in recovery yet, so you have chose ADB Sideload in TWRP and use the command
Code:
adb sideload name_of_your_rom_file.zip
May take some minutes for your computer to recognize your phone in adb sideload state, so be patient.
reaper90 said:
Reflash rom without wipe using adb sideload command. Vitrual sdcard on this phone can't be mounted in recovery yet, so you have chose ADB Sideload in TWRP and use the command
Code:
adb sideload name_of_your_rom_file.zip
May take some minutes for your computer to recognize your phone in adb sideload state, so be patient.
Click to expand...
Click to collapse
Thank you for helping me! So I only have the rom.zip on my computer and not on my phone, will the cmd command still work? since the command prompt does not seem to use file location.
Edit: I started ADB Sideload on my phone and it's stuck at 'starting ADB slideload feature..." for about 30 minutes
JustinBieber said:
Thank you for helping me! So I only have the rom.zip on my computer and not on my phone, will the cmd command still work? since the command prompt does not seem to use file location.
Edit: I started ADB Sideload on my phone and it's stuck at 'starting ADB slideload feature..." for about 30 minutes
Click to expand...
Click to collapse
you have to put the rom.zip file into your adb folder.
maybe you want to read this:
http://forum.xda-developers.com/showthread.php?t=2066390
reaper90 said:
you have to put the rom.zip file into your adb folder.
maybe you want to read this:
http://forum.xda-developers.com/showthread.php?t=2066390
Click to expand...
Click to collapse
I am actually trying that right now. My phone's adb sideload is still in the "starting adb feature.." so it isn't working.
Also when I press the ADB slideload on the toolkit, the command prompt opens and says
Code:
'C:\Documents' is not recognized as an internal or external command, operable program or batch file.
How do you place the rom.zip into the adb folder?
I'm still stuck, do you think flashing a kernel will help?
JustinBieber said:
I am actually trying that right now. My phone's adb sideload is still in the "starting adb feature.." so it isn't working.
Also when I press the ADB slideload on the toolkit, the command prompt opens and says
Code:
'C:\Documents' is not recognized as an internal or external command, operable program or batch file.
How do you place the rom.zip into the adb folder?
I'm still stuck, do you think flashing a kernel will help?
Click to expand...
Click to collapse
you have to place the toolkit into some path without spaces, or it won't work. best is to copy the toolkit folder to the root of any of your drives.
reaper90 said:
you have to place the toolkit into some path without spaces, or it won't work. best is to copy the toolkit folder to the root of any of your drives.
Click to expand...
Click to collapse
I placed the toolkit on the root of C:. Pressing the adb sideload on the toolkit launches the command prompt showing a bunch of adb shortcuts and help, but nothing happens on the phone (I attached a picture of the command prompt)
JustinBieber said:
I placed the toolkit on the root of C:. Pressing the adb sideload on the toolkit launches the command prompt showing a bunch of adb shortcuts and help, but nothing happens on the phone (I attached a picture of the command prompt)
Click to expand...
Click to collapse
did you start adb sideload on your phone too in before? also was your phone recognized in adb sideload state by your computer?
i have to admit that i did not use the toolkit for adb sideload...
you can set up your adb/fastboot files on your computer using this:
forum.xda-developers.com/showthread.php?t=2213910
then copy your rom to this folder, rename it to something simple, for example "rom.zip".
connect your phone to your computer, start adb sideload in recovery.
open a command prompt (navigate to your adb/fastboot folder if necessary), type "adb devices". if your device is not listet there, wait a few minutes and type adb devies again, repeat this until you see your device has been recognized by your computer, it should then be listed as in sideload state under your latest "adb devices" command.
now you can type "adb sideload rom.zip" and you should get progress of sideload displayed in %.
when sideload is complete, your phone should automatically start installation of this rom. if it does not, the rom.zip is now saved on your phone's internal memory as "sideload.zip"
hope this helps!
reaper90 said:
did you start adb sideload on your phone too in before? also was your phone recognized in adb sideload state by your computer?
i have to admit that i did not use the toolkit for adb sideload...
you can set up your adb/fastboot files on your computer using this:
forum.xda-developers.com/showthread.php?t=2213910
then copy your rom to this folder, rename it to something simple, for example "rom.zip".
connect your phone to your computer, start adb sideload in recovery.
open a command prompt (navigate to your adb/fastboot folder if necessary), type "adb devices". if your device is not listet there, wait a few minutes and type adb devies again, repeat this until you see your device has been recognized by your computer, it should then be listed as in sideload state under your latest "adb devices" command.
now you can type "adb sideload rom.zip" and you should get progress of sideload displayed in %.
when sideload is complete, your phone should automatically start installation of this rom. if it does not, the rom.zip is now saved on your phone's internal memory as "sideload.zip"
hope this helps!
Click to expand...
Click to collapse
After command prompt has successfully listed my device with its code, I typed in adb sideload (therom).zip and it says * cannot read 'sideload' * The tutorial that you posted doesnt have sideloading a rom
Edit: Okay, I installed SDK Manager did those things and this link really helped me on pushing files through adb. I will test to see if dirty flashing the rom will allow the phone to boot
Edit 2: Damn.. had to wipe everything and do a clean install. Never replace a bootanimation from another phone cause it ****s up your phone and time
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
JustinBieber said:
I did the most stupidest thing and tried to place a boot animation zip from the nexus 4 onto my phone. I renamed it ATT_Bootanimation.zip (like the normal bootanimation) and placed it in system/customize/resource. Now the phone wont boot. I tried going to TWRP's file manager, deleting the new zip and copying the old zip back but it still doesn't work. Can anyone help me please?
Edit: It also appears that TWRP can't mount sd card onto my computer so I can't place the ROM file onto my phone to flash. Can someone confirm this or teach me another way to fix this?
Click to expand...
Click to collapse
Tried factory reset? That might solve the issue...
Or use adb sideload to copy the ROM?
Addicted2xda said:
Tried factory reset? That might solve the issue...
Or use adb sideload to copy the ROM?
Click to expand...
Click to collapse
Yep, I downloaded SDK manager and opened the folder in command prompt, that was the only way I could sideload any files into my phone. I sideloaded the rom, reset everything (including system) and fresh install of the rom. Idk what went wrong the only thing I changed was the boot animation zip, which is very peculiar
But I have to thank reaper90 for helping me tons though
ive stumpled on upon a quite annoying problem..i have an HTC ONE X+ which i unlocked my bootloader on and everything went smooth until i wanted to start recovery via hboot.
it did not start and i tried several times and restarted etcetc, i then tried to flash in another recovery and then tried more and more but nothing..
then i cant remember now exaclty how i did it, but i have several RUU, kernel, recovery, boot and roms n such items downloaded
so i tried to feed in another flash or rom or whatever its called to get the recovery funtion to work (i am not very pro at this) and then when i wanted to start my phone normally it all of a sudden wont boot properly.
it freezes on the bootscreen.. i can turn off and go in to bootloader but i cant do ANYTHING from there, i cant do a factory reset (wich i also tried when the recovery did not want to work) i cant do **** there. tried to lock and unlock bootloader.. feels like im out of options..
the only thing i can do now is command the phone via cmd and the toolkit i use from here "Hasoon2000s htc one x AIO kit"
using this guide on this thread mostly..
ive tried so many things now, searched this and other forums since friday and i still can not get anywhere... starting to think this is what the definition of a bricked unit is??
if you need any more info please just ask.. i bought the phone a week ago so kinda sucks if it would be useless for me right away haha..
i would appreciate som help and tips... please
Sincerely Jeff
Did u flash the recovery after unlocking the bootloader.....?????
Sent from my One X+ using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:22 PM ----------
VivaSativa said:
ive stumpled on upon a quite annoying problem..i have an HTC ONE X+ which i unlocked my bootloader on and everything went smooth until i wanted to start recovery via hboot.
it did not start and i tried several times and restarted etcetc, i then tried to flash in another recovery and then tried more and more but nothing..
then i cant remember now exaclty how i did it, but i have several RUU, kernel, recovery, boot and roms n such items downloaded
so i tried to feed in another flash or rom or whatever its called to get the recovery funtion to work (i am not very pro at this) and then when i wanted to start my phone normally it all of a sudden wont boot properly.
it freezes on the bootscreen.. i can turn off and go in to bootloader but i cant do ANYTHING from there, i cant do a factory reset (wich i also tried when the recovery did not want to work) i cant do **** there. tried to lock and unlock bootloader.. feels like im out of options..
the only thing i can do now is command the phone via cmd and the toolkit i use from here "Hasoon2000s htc one x AIO kit"
using this guide on this thread mostly..
ive tried so many things now, searched this and other forums since friday and i still can not get anywhere... starting to think this is what the definition of a bricked unit is??
if you need any more info please just ask.. i bought the phone a week ago so kinda sucks if it would be useless for me right away haha..
i would appreciate som help and tips... please
Sincerely Jeff
Click to expand...
Click to collapse
After unlocking the bootloader....boot in hboot connect the phone in fastboot usb mode to the computer and then if u flash the recovery via cmd by typing "fastboot flash recovery TWRPrecovery.img" (the TWRPrecovery.img will be ur recovery file) u should get the message saying success.
Now u can disconnect the phone from the computer and use the volume down to choose the recovery and hit power button........
the TWRP logo is the one u ll be seeing.....that means all worked as it should......:good:
I dont knw whether u have tried the same but try this would work perfectly......
Danny Samuel said:
Did u flash the recovery after unlocking the bootloader.....?????
Sent from my One X+ using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:22 PM ----------
After unlocking the bootloader....boot in hboot connect the phone in fastboot usb mode to the computer and then if u flash the recovery via cmd by typing "fastboot flash recovery TWRPrecovery.img" (the TWRPrecovery.img will be ur recovery file) u should get the message saying success.
Now u can disconnect the phone from the computer and use the volume down to choose the recovery and hit power button........
the TWRP logo is the one u ll be seeing.....that means all worked as it should......:good:
I dont knw whether u have tried the same but try this would work perfectly......
Click to expand...
Click to collapse
well i tried that before and it still didnt want to work, like it was priorotizing the first one i put in there or something.. but now i came to a wall... since i waited so long to find a sulution i had the device completely empty and just in bootloader.. it seems i dont have the driver or such for it to charge.. so i plugged it into the wall for a while whilst in fastboot thinking it was charging which it was not..
Now it is completely dead i cannot charge it and my computor cant detect it anymore.. seems i found the meaning of a bricked device
Related
I've searched everywhere i can thing and havn't found quite the answer for my problem:
My wife's stock, fully updated photon crapped out the other day and we just got the refurb replacement. The problem is that i can't get adb access to the phone so i can't pull the pictures off of it. I did find one way to pull it for a rooted GNex but before i try it i'd like to check if it will work on a stock, unrooted, mopho.
"Boot up CWM and then pull the files. Step-by-step:
1) Download CWM, rename it to cwm.img and place it in the same directory as your fastboot executable;
2) Reboot you device into fastboot mode and connect to your computer;
3) Make sure your computer sees your device by typing: fastboot devices
4) Boot CWM by typing: fastboot boot cwm.img
5) Pull all the files from /sdcard by typing: adb pull /data/media"
Any and all help would be appreciated and thank you in advance!
my GF has a moto phone and to get into fsstboot i power off, hold volume down, then you'll see fastboot. plug your phone into your computer, then press volume up. i don't know if ADB will be able to pull out the files you want without rooting, but it's worth a try.
good luck!!
Sent from my HTC Glacier using xda premium
I can access fastboot, and control the phone thru fastboot, but I don't know how to get access to the internal memory. I guess i'll try to boot a stock recovery and ADB from there?
cruxanyra said:
I've searched everywhere i can thing and havn't found quite the answer for my problem:
My wife's stock, fully updated photon crapped out the other day and we just got the refurb replacement. The problem is that i can't get adb access to the phone so i can't pull the pictures off of it. I did find one way to pull it for a rooted GNex but before i try it i'd like to check if it will work on a stock, unrooted, mopho.
"Boot up CWM and then pull the files. Step-by-step:
1) Download CWM, rename it to cwm.img and place it in the same directory as your fastboot executable;
2) Reboot you device into fastboot mode and connect to your computer;
3) Make sure your computer sees your device by typing: fastboot devices
4) Boot CWM by typing: fastboot boot cwm.img
5) Pull all the files from /sdcard by typing: adb pull /data/media"
Any and all help would be appreciated and thank you in advance!
Click to expand...
Click to collapse
Without unlocking the bootloader your not going to be able to use cwm.
cruxanyra said:
I've searched everywhere i can thing and havn't found quite the answer for my problem:
My wife's stock, fully updated photon crapped out the other day and we just got the refurb replacement. The problem is that i can't get adb access to the phone so i can't pull the pictures off of it. I did find one way to pull it for a rooted GNex but before i try it i'd like to check if it will work on a stock, unrooted, mopho.
"Boot up CWM and then pull the files. Step-by-step:
1) Download CWM, rename it to cwm.img and place it in the same directory as your fastboot executable;
2) Reboot you device into fastboot mode and connect to your computer;
3) Make sure your computer sees your device by typing: fastboot devices
4) Boot CWM by typing: fastboot boot cwm.img
5) Pull all the files from /sdcard by typing: adb pull /data/media"
Any and all help would be appreciated and thank you in advance!
Click to expand...
Click to collapse
When you say "crapped out" I'm guessing you mean it won't boot at all? What is the phone that you need the pictures off of capable of doing at the moment?
celloevan said:
When you say "crapped out" I'm guessing you mean it won't boot at all? What is the phone that you need the pictures off of capable of doing at the moment?
Click to expand...
Click to collapse
I'm sorry, yes. By crapped out I mean wont boot. I can get it to "Failed to boot 1" and "Failed to boot 1-Fastboot" I can control it with Fastboot from my Ubuntu 12.04 laptop but can't get ADB to take hold or use fastboot to load the internal storage as UMS.
Recovering the phone isn't an issue, we have an insurance policy. But I can't unlock it and then send it in b/c they might charge us for the phone.
A few ideas I've had are:
Boot into stock recovery.img using fastboot and ADB from there
Use a script using fastboot -c to mount the internal storage as UMS
I just read something about getting into recovery from fastboot using the down volume but I haven't tried it yet
Failed to boot 1 is a issue with the bootloader.
I installed R3 rom but my wifi cant be turned on. Latest I found that also my USB internet passthrough is not working. I got hint from one member but I absolutely dont know how to perform this.
flash the boot.img inside the R3's zip file using fastboot.
Commands:
fastboot erase cache
fastboot flash boot boot.img
How to flash something inside zip file? do I have to extract it and put it into root?
How to execute commands at all? Where to put them? What do I need to perform? I am total noob and every simple step I ever done took me a day. Now I am stuck. IF someone knows how to make this, please help.
Thank you.
First question do you have ADB installed?
Then you need to unpack boot.img from rom.zip.
When I get my answer we'll go further.
nlooooo said:
First question do you have ADB installed?
Then you need to unpack boot.img from rom.zip.
When I get my answer we'll go further.
Click to expand...
Click to collapse
I should have ADB, because I was rooting my phone month ago and ADB was required. How do I find out? I have SDK tools and i have adb.exe, adbwinapi.dll, fastboot.exe, recovery.img in C\Android. Actually I was trying to connect phone through USB and start adb.exe but it just popped out, scrolled down fast and closed (it was looking like command prompt- black window).
And I unpacked boot.img from R3.zip to my sdcard
Copy boot.img to android folder (where you have SDK platform tools installed), reboot phone to fastboot, connect it to PC and issue commands:
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
And then reboot your phone.
Copy boot.img to android folder (where you have SDK platform tools installed), reboot phone to fastboot, connect it to PC and issue commands:
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
And then reboot your phone.
Actually I tought this is the way, but let me tell you what is happening:
1.Turned phone off
2.entered fastboot on my phone
3.opened adb.exe in my Android-sdk/platform-tools folder
4.the adb window just opened for a 1second, everything scrolled down fast
5.adb window closed.
This is the reason why I need help, but really thank you for taking care
janickonajkrajsi said:
Copy boot.img to android folder (where you have SDK platform tools installed), reboot phone to fastboot, connect it to PC and issue commands:
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
And then reboot your phone.
Actually I tought this is the way, but let me tell you what is happening:
1.Turned phone off
2.entered fastboot on my phone
3.opened adb.exe in my Android-sdk/platform-tools folder
4.the adb window just opened for a 1second, everything scrolled down fast
5.adb window closed.
This is the reason why I need help, but really thank you for taking care
Click to expand...
Click to collapse
You shouldn't click the adb. exe, open cmd and type the commands there.
Sent from my awesome fridge
I'm just wandering how did you manage to unlock bootloader at all.
MaartenXDA said:
You shouldn't click the adb. exe, open cmd and type the commands there.
Sent from my awesome fridge
Click to expand...
Click to collapse
yeah, I also did this according to this post http://forum.xda-developers.com/showthread.php?t=1752270
and this post http://forum.xda-developers.com/showthread.php?t=860421
but Cmd could not recognize this. I tried "fastboot devices" and this was not recognized too.
Then I reinstalled HTC drivers and then tried again. So then I was trying to open adb.exe and then you told me to issue command through cmd and here we are. sorry I am real noob in android things. I was using iphone and everything worked like magic
Isnt there a way to perform this "boot.img flashing" through recovery mod? I mean without the usb connection and without the cmd black hole
janickonajkrajsi said:
yeah, I also did this according to this post http://forum.xda-developers.com/showthread.php?t=1752270
and this post http://forum.xda-developers.com/showthread.php?t=860421
but Cmd could not recognize this. I tried "fastboot devices" and this was not recognized too.
Then I reinstalled HTC drivers and then tried again. So then I was trying to open adb.exe and then you told me to issue command through cmd and here we are. sorry I am real noob in android things. I was using iphone and everything worked like magic
Click to expand...
Click to collapse
First use the command "cd C:\Android"
After that do the commands again.
Be sure you've uninstalled HTC Sync (NOT the drivers) before doing this.
Sent from my awesome fridge
nlooooo said:
I'm just wandering how did you manage to unlock bootloader at all.
Click to expand...
Click to collapse
He didn't get your point...
Sent from my toaster using TapaToast HD
Thank you guys, now it is working.
Quote:
Originally Posted by nlooooo View Post
I'm just wandering how did you manage to unlock bootloader at all.
He didn't get your point...
Yeah it was meant like "hod did this stupid noob even managed to unlock bootloader at all. I got his point, and the right answer was "step by step guide" so actually You didnt got my point.
Dont forget that things that are automatic and obvious to you, are not obvious to everyone. My grandma is learning to work with computers and when she asks me how to send an email, I have to tell her "grab a mouse, then move it there........"
)))))))
Does not matter, thank you guys!
Once you learn to use adb and fastboot it's always the same, so my point was that you've never learned how to use it, you just typed what you saw, without any wish to learn.
Point is to try and learn, not to ask again.
Nobody said you're stupid, just lazy.
Cant get the R3 working. HTC Sense UI crashed error at lock screen
I flashed the sense revolution r3 today but could not get it working.
The following are the issues faced.
1) It starts without installing the mods package, but lacks the full sense widgets like htccontacts, htc calender etc.
2) when i flashed the r3 mod package, it gets stuck at the lock screen. The Sense UI crashes.
3) Without the mods, i faced another bug in people widget. it crashes when i click the phone dialer from it.
I am currently on sense r3.
Please help me install it in full.
I looked all over the internet for help with this phone. I rooted it for a friend and a week later, he said he restarted the phone and everything started force closing.
I troubleshot all day, and came to figure out that my only known to me as of now, is flashing CWM to it, via ADB. I am having several issues with setting up ADB, and getting the phone to communicate with my computer. Device manager DOES show that there is an ADB device installed correctly, so what would my next move be? I got the phone into FTM mode, (fastboot?) and I know that that is what I need to do to get ADB to communicate with my phone.
halp pls
Really no one can help???
bamp
cammiso94 said:
bamp
Click to expand...
Click to collapse
ADB Drivers for Windows Vista/7
Tutorial- http://www.youtube.com/watch?v=RDA8PpPSFuk
If you havn't found this yet...
Your answer is here: androidforums.com/flash-all-things-root/ Good luck!:good:
CWM Beta
From Android Forums ... Thanks to Junkie2100
this is an unfinished copy of cwm, tested to be almost completely functional
standard warnings apply, use at your own risk, you try to blame me for breaking your phone i will laugh at you
instructions:
fastboot method is possible, but i will go through the terminal/adb method
download the recovery file, and put it on the root of your sd. no folders, just directly on the sd
get your phone rooted and get a copy of terminal emulator or connect to it through adb on your computer, adb will require zte drivers and the adb program on the pc. the choice is yours
fire up adb by typing
Code (Text):
adb shell
in the command prompt, if its not working you dont have adb in the directory youre in, just copy adb.exe and the two .dll files to c:\windows\system32\ and itll work from anywhere, or learn how command prompt works
or fire up terminal emulator on the phone
on adb shell or terminal emulator type
Code (Text):
su
dd if=/sdcard/flash_cwm_test2.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
you will then need to run
Code (Text):
reboot recovery
and then hit reboot when cwm comes up, if it asks to disable recovery flashing press yes or it will put stock recovery back next time the rom boots
known bugs:
unmounting doesnt work
downloads:
w.ww.4shared.com/file/2qBR2Kfr/flash_cwm_test2.html
i apologize for it being 4shared, if someone wants to make a mirror ill put it up
Hi guys. I have an HTC OX+... I tried to flash a rom but something went wrong and I erased everything... Now I managed to switch my phone on in fastboot and in recovery mode. How can I sort the problem out?
My recovery is TWRP 2.7.1.0
lorenk93 said:
Hi guys. I have an HTC OX+... I tried to flash a rom but something went wrong and I erased everything... Now I managed to switch my phone on in fastboot and in recovery mode. How can I sort the problem out?
My recovery is TWRP 2.7.1.0
Click to expand...
Click to collapse
I assume your PC has all drivers installed so go to command prompt, there go to your folder where adb and fastboot are.
It should be like this, cd C:\folder_where_adb_is
Now go to recovery mode on the phone and search for Sideload, it can be in install zip from your recovery, click it when you found it.
Go to your Pc and put the ROM to the folder where adb and fastboot are.
Then make sure your phone says it's in adb sideload mode,
On the PC write
Code:
adb sideload file_name.zip
And wait until it's finished
Let's say that's done, but you can't boot, it keeps restarting forever.
In this case, go to your rom.zip open it on the PC and there will be a file called boot.img
Extract boot.img to your folder where fastboot and adb are.
Now on your phone, force it to close by holding power, open fastboot
Again open cmd on the PC and point it to your folder where fastboot and adb are.
Then write
Code:
fastboot flash boot boot.img
oziboy said:
I assume your PC has all drivers installed so go to command prompt, there go to your folder where adb and fastboot are.
It should be like this, cd C:\folder_where_adb_is
Now go to recovery mode on the phone and search for Sideload, it can be in install zip from your recovery, click it when you found it.
Go to your Pc and put the ROM to the folder where adb and fastboot are.
Then make sure your phone says it's in adb sideload mode,
On the PC write
Code:
adb sideload file_name.zip
And wait until it's finished
Let's say that's done, but you can't boot, it keeps restarting forever.
In this case, go to your rom.zip open it on the PC and there will be a file called boot.img
Extract boot.img to your folder where fastboot and adb are.
Now on your phone, force it to close by holding power, open fastboot
Again open cmd on the PC and point it to your folder where fastboot and adb are.
Then write
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
When I write adb sideload file_name.zip, it
returns "error: closed". why?
lorenk93 said:
When I write adb sideload file_name.zip, it
returns "error: closed". why?
Click to expand...
Click to collapse
file_name.zip is your ROM name, for example if you have arhd it can be ARHD_V8.zip or something, just see what name the zip file of your rom has
if this is not the case try
ADB usb before trying adb sideload
oziboy said:
file_name.zip is your ROM name, for example if you have arhd it can be ARHD_V8.zip or something, just see what name the zip file of your rom has
if this is not the case try
ADB usb before trying adb sideload
Click to expand...
Click to collapse
so... I have to write "ADB usb file_name.zip". tath's right?
lorenk93 said:
so... I have to write "ADB usb file_name.zip". tath's right?
Click to expand...
Click to collapse
No, you have to write only "adb usb".
Then try "adb sideload yourrom.zip" again.
if that didn't work, then reboot into recovery and go to command prompt, and write
Code:
adb kill-server
adb usb
adb push yourromname.zip /sdcard
that should work if nothing else works. im having kinda the same issue right now :/
oziboy said:
No, you have to write only "adb usb".
Then try "adb sideload yourrom.zip" again.
if that didn't work, then reboot into recovery and go to command prompt, and write
Code:
adb kill-server
adb usb
adb push yourromname.zip /sdcard
that should work if nothing else works. im having kinda the same issue right now :/
Click to expand...
Click to collapse
I don't know why, but when I write adb usb it returns "error: device not found"
lorenk93 said:
I don't know why, but when I write adb usb it returns "error: device not found"
Click to expand...
Click to collapse
I just fixed this on my phone, now to to control panel - uninstall a program and delete htc sync manager (only sync manager, not the drivers)
Then try again, if nothing, go to here and install that.
If installed, go to fastboot mode, plug in your phone and in that program, when you open it, it says install drivers, flash rom and such...
Now on the right there is flash TWRP recovery, flash that, if your device is an LTE variant (ATT, Telus) install the ones for that and international for international version, make sure you got the correct one.
Then go to recovery, on the lower-right side there is an "advanced" button, hit that and there should be adb sideload somewhere, click that and swipe left to right to enable.
Go to your PC and repeat the sideloading steps as I said before.
oziboy said:
I just fixed this on my phone, now to to control panel - uninstall a program and delete htc sync manager (only sync manager, not the drivers)
Then try again, if nothing, go to here and install that.
If installed, go to fastboot mode, plug in your phone and in that program, when you open it, it says install drivers, flash rom and such...
Now on the right there is flash TWRP recovery, flash that, if your device is an LTE variant (ATT, Telus) install the ones for that and international for international version, make sure you got the correct one.
Then go to recovery, on the lower-right side there is an "advanced" button, hit that and there should be adb sideload somewhere, click that and swipe left to right to enable.
Go to your PC and repeat the sideloading steps as I said before.
Click to expand...
Click to collapse
I did it... Thanks to you... So thank you so much...
lorenk93 said:
I did it... Thanks to you... So thank you so much...
Click to expand...
Click to collapse
No problem, I had almost the same problem and just told what I did xD
So I have had my Droid DNA for a few months and I've been messing around with it and doing fine. Since I installed TWRP it allows me to delete internal storage...
Oops, there goes my ROM I had saved. Now I'm stuck in either bootloader or recovery. I can't get ADB to recognize my DNA to save my life. It's really really irritating.
I've tried flashing a zip with fastboot since fastboot can recognize my device but ADB can't and it didn't work.
I have Minimal ADB installed and HTC sync manager, but i installed sync after i messed it up so idk if it installed the drivers.
I need a step by step instruction guide to get this to work. I can't find it anywhere. I keep getting no ADB devices and it saying server out of date and what not. I've been searching for hours and hours.
I can't get this to work. I even bought a new phone in the meantime to get me by and that's not exactly what I wanted to do... Any help would be appreciated. Thank you very much!!
No one?
Pretty quite.. I recently had this happen as well.. No fear tho.. If you have twrp already installed your golden.. Download a rom 2 your computer and on twrp goto advanced and sideload.. Command prompt on your computer.. Easiest if found is running xp. Get to your folder of adb hit control and right click poem command prompt here.. adb devices, then adb sideload rom(name). zip.. Your computer will find your device then , and if it didn't send it will allow you to file Explorer.. Throw a rom on your internal reboot into twrp and flash
Æaa..\../
I am lucky I switched to TWRP before this happen, but alas, it's hanging at starting ADB Sideload, doesnt show up in devices either. How do I make it visible so i can just use file explorer from my PC to sideload it?
dyllysoilly said:
I am lucky I switched to TWRP before this happen, but alas, it's hanging at starting ADB Sideload, doesnt show up in devices either. How do I make it visible so i can just use file explorer from my PC to sideload it?
Click to expand...
Click to collapse
You can restrt the phone. Hold down power and volume down together. Then you can reaccess the bootloader from there. If you have twrp you can just go through the file manager instead of messing with sideload.