Related
I'm trying to install Cyanogen 4.1.99, but I think I screwed up. According to Fingerlickin I need to install cyanogen's recovery image. First, before I even tried this endeavor, I was running Cyanogen 4.11.1 with the EnochXTra theme. I flashed the recovery image as instructed but, when I rebooted (probably where I messed up) I didn't see the usual recovery mode menu, just some triangle with a "!" in it facing a phone/pda (and NO text). Now I can't flash update.zip files. (Yes I tried ALT+S).
Also Fingerlickin pointed me towards fastboot. I know it's the key right now, but I don't know where to go from here. I think I still have root because I have adb running and could "su" without any complaints.
(I decided to start a new thread because the one I was in had a different problem. Also I would search the forum but I don' know what to search for.)
Tactical Fart said:
I'm trying to install Cyanogen 4.1.99, but I think I screwed up. According to Fingerlickin I need to install cyanogen's recovery image. First, before I even tried this endeavor, I was running Cyanogen 4.11.1 with the EnochXTra theme. I flashed the recovery image as instructed but, when I rebooted (probably where I messed up) I didn't see the usual recovery mode menu, just some triangle with a "!" in it facing a phone/pda (and NO text). Now I can't flash update.zip files. (Yes I tried ALT+S).
Also Fingerlickin pointed me towards fastboot. I know it's the key right now, but I don't know where to go from here. I think I still have root because I have adb running and could "su" without any complaints.
(I decided to start a new thread because the one I was in had a different problem. Also I would search the forum but I don' know what to search for.)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=523558
instructions are in the OP. if you can boot into the rom, use
Code:
flash_image recovery /sdcard/cm-recovery-1.4.img
after putting the new recovery on your SD card
if that doesnt work
Code:
fastboot erase recovery
fastboot flash recovery cm-recovery-1.4.img
with fastboot
instructions to set up fastboot
http://forum.xda-developers.com/showthread.php?t=532719
you shouldnt need to flash the SPL if you have HardSPL or DangerSPL already. Just make sure you have the right drivers, and use the 1.6 SDK since its already out
If you have any others questions or need clarification, post here again
When I was in the rom, I used the terminal emulator, and when I tried to use "su" it said "uid 10031 not allowed to su". I tried "flash_image recovery /sdcard/cm-recovery-1.4.img" under adb and that flopped. Under fast boot I get "Error: cannot load 'cm-recovery-1.4.img'.
*Is nervous*
Tactical Fart said:
When I was in the rom, I used the terminal emulator, and when I tried to use "su" it said "uid 10031 not allowed to su". I tried "flash_image recovery /sdcard/cm-recovery-1.4.img" under adb and that flopped. Under fast boot I get "Error: cannot load 'cm-recovery-1.4.img'.
*Is nervous*
Click to expand...
Click to collapse
what spl do you have and is the recovery.img in the folder you are using fastboot from?
david1171 said:
what spl do you have and is the recovery.img in the folder you are using fastboot from?
Click to expand...
Click to collapse
He has the DangerSPL
and do as david said. the cm recovery image must be in the same folder as the fastboot executable
B-man007 said:
He has the DangerSPL
and do as david said. the cm recovery image must be in the same folder as the fastboot executable
Click to expand...
Click to collapse
reading fail, that's what little sleep for the past few days does
i have a android folder on my C:\ drive with fastboot.exe, adb.exe, and the AdbWinApi.dll so that is the folder i use whenever i need fastboot, i keep the adb.exe and AdbWinApi.dll file in my system32 folder so i can use adb easier.
david1171 said:
reading fail, that's what little sleep for the past few days does
i have a android folder on my C:\ drive with fastboot.exe, adb.exe, and the AdbWinApi.dll so that is the folder i use whenever i need fastboot, i keep the adb.exe and AdbWinApi.dll file in my system32 folder so i can use adb easier.
Click to expand...
Click to collapse
O dont worry he didnt mention it in this thread, it was in the other thread.
I do the same thing haha
@Technical Fart
Don't worry to much, your phone is still booting, its not bricked. Just take it slow and read everything carefully. since you got fastboot already set up, the hardest part is over.
Problem Fixed!!! I didn't know that you had to have the image in that same directory that you had the fastboot command in. Thank-you so much! It feels good to be in a cyanogen rom again.
Tactical Fart said:
Problem Fixed!!! I didn't know that you had to have the image in that same directory that you had the fastboot command in. Thank-you so much! It feels good to be in a cyanogen rom again.
Click to expand...
Click to collapse
NP
Can you please put [SOLVED] in the title?
B-man007 said:
NP
Can you please put [SOLVED] in the title?
Click to expand...
Click to collapse
How do I do that?
Tactical Fart said:
How do I do that?
Click to expand...
Click to collapse
select edit, go advanced, edit the title to include [SOLVED]
ADB working...not so much for fastboot
Hey guys,
I can't seem to get fastboot up and running. My adb is running fine but in all my noobishness I don't know how to get the recovery image running using adb. Is there anyway to do it or am I gonna have to figure out how to get the fastboot going?
to get fastboot going, you phone has to be in bootloader, in fastboot usb mode, and you need to be operating from a folder that has the fastboot.exe, adb.exe and the AdbWinApi.dll (for windows at least). then whatever you are wanting to transfer via fastboot needs to be in that folder as well.
I have all of those things in the tools file. Fastboot shows on my phone but when I type fastboot devices it shows nothing. Also, I tried doing the fastboot commands and it said it is waiting for the device.
When I type fastboot shell to get in to su it gives me the option list as if I just typed in fastboot.
Should I redo the whole adb install process?
Ok, tried going another method and downgrading or changing my rom...no go. Looks like it keeps aborting each installation. This is getting really lame really fast.
Edit: I fixed the problem with my fastboot finally. Apparently when I plugged up my phone in fastboot it recognized it as a mass storage device so I had to uninstall those drivers at startup and reinstall the adb drivers. I think I've spent 4 hours total on trying to fix what happened after this rom and sadly enjoyed the challenge.
simplyTravis said:
Ok, tried going another method and downgrading or changing my rom...no go. Looks like it keeps aborting each installation. This is getting really lame really fast.
Edit: I fixed the problem with my fastboot finally. Apparently when I plugged up my phone in fastboot it recognized it as a mass storage device so I had to uninstall those drivers at startup and reinstall the adb drivers. I think I've spent 4 hours total on trying to fix what happened after this rom and sadly enjoyed the challenge.
Click to expand...
Click to collapse
good to see you got the answer yourself
trust me, those long seemingly pointless hours troubleshooting pays off in the long run. you have a better understanding of how everything works
Hi - I have flash_image in the sdk tools folder but when I do:
ad push flash_image /system/bin is says cannot stat no such file or directory.
Please help!
Erris Bueller said:
Hi - I have flash_image in the sdk tools folder but when I do:
ad push flash_image /system/bin is says cannot stat no such file or directory.
Please help!
Click to expand...
Click to collapse
did you mount the /system directory?
from CMD:
adb shell
#mount -a
then try it.
afterwards then
#umount -a
Hello gentleman, i'm new to this forum and android issues, read a lot of threads but today i got registered. hahaha
OK. First of all, im using ubuntu 12.04. Got my phone rooted yesterday with ICS using unlockroot with starter thread help on windows, today im trying to install CM10 and i really don't know what i'm doing wrong or if is missing something. Let's see...
On android sdk platform-tools in terminal mode, i started adb server with sudo to check if the problem is with permission:
Code:
sudo ./adb start-server
and verified if device is connected as well:
Code:
adb devices
the device is identified and another step i made was:
Code:
adb push /home/anon/Downloads/cm10.0.0-p970.zip /media/8184-18FE/
doing this i got my first error step receiving a message like: "no such file or directory error."
ps: this folder on /media/8184-18FE/ is the local to sdcard on device connected on usb using mass storage mode.
looking for some awnsers on other threads, people say to run adb as root using:
Code:
adb root
when i do this command line i get another message error: "adbd cannot run as root in production builds."
what is the difference of start adb on sudo mode or start adb on root mode? I thought it was about previleges, but seems equal for me.
I really don't know im missing or doing wrong, but still can't tranfer the rom to sdcard to upgrade my android.
As begginer on android, any help is welcome. Thank you!
Sv: [Q] adb problems
When you push it type adb push *directory* and the where you want it like /sdcard
So it is,
adb push /home/name.zip /sdcard
Or just enable mass storage and move it that way.
But you can't flash it since you have ics that you can't use cwm on
Cheers
Daniel
RomWiz said:
When you push it type adb push *directory* and the where you want it like /sdcard
So it is,
adb push /home/name.zip /sdcard
Or just enable mass storage and move it that way.
But you can't flash it since you have ics that you can't use cwm on
Cheers
Daniel
Click to expand...
Click to collapse
I realized that adb push command was wrong, but tryed it and now im receiving the error message: permission denied.
searched on another threads and figured out that the kernel that i have on official ICS is insecure, maybe that's why i can't flash like you said
but now my mind is a mess, i can't use the cwm because it cannot reboot in recovery mode like i saw on another threads?
what i do now? install a custom kernel and gingerbread, them root and install cm10 on recovery mode?
Sv: [Q] adb problems
cleitonpp said:
I realized that adb push command was wrong, but tryed it and now im receiving the error message: permission denied.
searched on another threads and figured out that the kernel that i have on official ICS is insecure, maybe that's why i can't flash like you said
but now my mind is a mess, i can't use the cwm because it cannot reboot in recovery mode like i saw on another threads?
what i do now? install a custom kernel and gingerbread, them root and install cm10 on recovery mode?
Click to expand...
Click to collapse
You flash a modded GB ROM with sft and install the ROM.
Cheers
Daniel
RomWiz said:
You flash a modded GB ROM with sft and install the ROM.
Cheers
Daniel
Click to expand...
Click to collapse
HAHAHA im such a dumb ass. Dont know why i tryed reboot into recovery mode on CWM, now i ****ed up my bootloader or bricked. XD
Sv: [Q] adb problems
Just flash a gb rom with sft
Cheers
Daniel
RomWiz said:
Just flash a gb rom with sft
Cheers
Daniel
Click to expand...
Click to collapse
Less than 5 days with my first android, i bricked 1 time...
i flashed, installed cm10, gapps and superuser, im so happy that i dont bricked permanently LOL
now im testing cm10 jelly bean =D
Thank you Daniel
Cheers :good:
well while rooting my phone, installing the recovery and custom rom.. i made a slight (big) mistake towards the ending of root kit process by hasoon. When we are about to flash the custom rom, we're supposed to wipe everything so there wouldn't be any problems later on. We all know a fresh install always gives the best results. When i was wiping everything, i forgot to put Android Revolution HD on my sd so now i have recovery but i can't install a stock rom, custom rom, and i can't restore my phone. please someone help me.. i unfortunately have to go to work in 20 mins but when i get out of work i would greatly appreciate it if i had a few answers that can help me out with my situation. I don't care if its a hard process. this isn't my first phone i root so im not that noobie (at least i don't think so) so all im asking is to be pointed in the right direction and i would greatly appreciate that. Please and thanks for the help everyone. Hope we're all enjoying this amazing phone
Use the all-in-one toolkit in the dev forum to sideload the ROM from your PC. Rename the ROM something simple like arhd.zip on your PC to make it easier.
This helped me with a similar problem.
Sent from my HTC One using xda premium
thanks for getting me on the right track.. i honestly feel really close to having a phone again but now cwm is messing me up now. whenever i try to sideload.. i keep getting "failed to open driver control: No such file or directory" then it says "restarting adbd..." and then it just repeats with the no driver control. did this happen to u? :-/
Josh112191 said:
thanks for getting me on the right track.. i honestly feel really close to having a phone again but now cwm is messing me up now. whenever i try to sideload.. i keep getting "failed to open driver control: No such file or directory" then it says "restarting adbd..." and then it just repeats with the no driver control. did this happen to u? :-/
Click to expand...
Click to collapse
I have exactly the same problem. ADB sideload isn't working for me as the device isn't showing up in adb when booted into recovery... I've been doing this for years... I don't know how I could have done something so stupid :'(
EDIT:
I managed to fix this by installing CWM touch recovery and using LINUX to sideload the ROM .zip for installation. Good look sorting it out!
No didn't get anything like that. Maybe if you can get a USB OTG cable and try load the ROM that way through CWM from a USB or micro sd adapter?
I'm not sure if this would work as I haven't tried it - just a suggestion to try.
Sent from my HTC One using xda premium
Sideload from CWM Recovery
Just went through the whole boot loop due to Aroma freezes at the beginning of the installation, but CWM Recovery is still accessible so I went the ADB Sideload method and push the file to be installed because I didn't have any backup on the internal memory.
Just a couple of guides from the guys at XDA that got me back:
make sure you have the most up to date ADB Tools
From your phone go to Recovery>install zip from sideload
From CMD prompt, check that adb can see your device by 'adb devices' command, it should show your device number with sideload next to it.
If it doesn't see it, try 'adb kill-server' and then 'adb start-server'
Then 'adb sideload custom.zip' (custom= name of ROM zip file)
You should see the percentage completion then it will start the installation on your phone.
I am also newbie at this, was panicking and looked around here having this bricked phone next to me for 24hrs, but I asked around and they got me back in.
Good luck.
boot to recovery and push rom to phone....
'adb push /path/to/ROM/on/your/computer /path/on/device' (without quotes)
xdracco said:
boot to recovery and push rom to phone....
'adb push /path/to/ROM/on/your/computer /path/on/device' (without quotes)
Click to expand...
Click to collapse
I'd be interested to see an example of the command for future reference??
For example, the ROM is saved in C:\fastboot
Thanks.
xdracco said:
boot to recovery and push rom to phone....
'adb push /path/to/ROM/on/your/computer /path/on/device' (without quotes)
Click to expand...
Click to collapse
This is what I was going to suggest.
Sent from my HTC One using xda app-developers app
redbull123 said:
I'd be interested to see an example of the command for future reference??
For example, the ROM is saved in C:\fastboot
Thanks.
Click to expand...
Click to collapse
Code:
adb push C:\fastboot\My_Rom.zip /sdcard/Download/
Try to have no spaces in the file name. linux based systems hate that.
Then when you boot into recovery, head over to:
install zip from sdcard -> choose zip from sdcard -> Download/
You'll find your ROM there.
HTH
What model do u have?
Sent from my HTC One using xda app-developers app
Hi,
I'm currently trying to use adb to push some data into my phone but i always get "error: closed". I'm using windows 7 x64 and im running it from cmd.
Almost everything i tried using adb (push, shell, remount) returns this. I've searched over the forums and tried "adb devices" as well to see if my phone is connected, but what is different from the others is i am getting
List of devices attached
XXXXXX host
instead of what most other people got
List of devices attached
XXXXXX device
Is this a problem? What am i missing? Thanks a lot for ur time in reading this
Try:
Code:
adb usb
then
Code:
adb devices
or
Code:
adb kill-server
then
Code:
adb start-server
then
Code:
adb devices
Guich said:
Try:
Code:
adb usb
then
Code:
adb devices
or
Code:
adb kill-server
then
Code:
adb start-server
then
Code:
adb devices
Click to expand...
Click to collapse
Thank you! Although after doing these commands it still returned error:closed it listed my device as being in sideload mode so all sideload commands worked after that including sideloading a rom .zip
Did you update the SDK Manager??? Try updating that, my ADB problem were gone after i updated them.....
xlxcrossing said:
Thank you! Although after doing these commands it still returned error:closed it listed my device as being in sideload mode so all sideload commands worked after that including sideloading a rom .zip
Click to expand...
Click to collapse
I've got the same situation with "error closed" message. I ran the suggestions above but am still getting the error message.... Thoughts?
jflora1 said:
I've got the same situation with "error closed" message. I ran the suggestions above but am still getting the error message.... Thoughts?
Click to expand...
Click to collapse
Try to download this, un-zip and try the tips with this
Guich said:
Try to download this, un-zip and try the tips with this
Click to expand...
Click to collapse
I downloaded the zip but haven't had any success, still getting an error:closed message
ozo012 said:
I downloaded the zip but haven't had any success, still getting an error:closed message
Click to expand...
Click to collapse
which recovery are you on? (name and version number please)
nkk71 said:
which recovery are you on? (name and version number please)
Click to expand...
Click to collapse
This is actually the only place I've found that might have had a solution to my problem (different device: Nexus 7, Stock 4.3 JWR66Y, unrooted, I'm attempting to sideload the 4.4 update but continually get this error:closed message.
ozo012 said:
This is actually the only place I've found that might have had a solution to my problem (different device: Nexus 7, Stock 4.3 JWR66Y, unrooted, I'm attempting to sideload the 4.4 update but continually get this error:closed message.
Click to expand...
Click to collapse
isnt "error closed" something to do with out of date adb?
ozo012 said:
This is actually the only place I've found that might have had a solution to my problem (different device: Nexus 7, Stock 4.3 JWR66Y, unrooted, I'm attempting to sideload the 4.4 update but continually get this error:closed message.
Click to expand...
Click to collapse
Some people had solved the issue with the command:
Code:
adb usb
and after a reboot of device.
But seems don't work for all.
nkk71 said:
isnt "error closed" something to do with out of date adb?
Click to expand...
Click to collapse
Umh, no, i don' think
Guich said:
Some people had solved the issue with the command:
Code:
adb usb
and after a reboot of device.
But seems don't work for all.
Umh, no, i don' think
Click to expand...
Click to collapse
I haven't tried rebooting the device seems to be the only thing I left out.
I was having the same problems. Couldn't sideload. When I would run "adb devices" , my device would be listed. If I ran "adb usb" I would get "error: closed" . The sideload command would just bring up a list of commands. This may help someone, I installed a new version of adb. Not sure if I can post links but the file name was adb-setup-1.1.exe. This installs the needed files, the installer didn't notify me where the files were installed but they installed right to my C:\ drive. This seemed to eliminate the problem for me. I did a lot of searching and couldn't find anyone with this specific issue, so if anyone finds themselves with this problem give this a try.
worked for me
i had the same problem
i coulnt send anyfile to my htc one but after updating plate-form tools and replacing the old adb and fastboot files with the new ones
i entered the commend adb sideload rom.zip and it started sending the rom
and the phone was on twrp recovery-advanced-sideload
morheb said:
i had the same problem
i coulnt send anyfile to my htc one but after updating plate-form tools and replacing the old adb and fastboot files with the new ones
i entered the commend adb sideload rom.zip and it started sending the rom
and the phone was on twrp recovery-advanced-sideload
Click to expand...
Click to collapse
Yay. That Just worked for me using Crunchbang Debian. Thanks morheb that little tweak of using 'sideload' was the key
Can anyone help me push vold.fstab file with adb?
Stock Recovery on mediatek platform. with adb i got same error as this thread. Error:closed
KoolAidBigMan said:
I was having the same problems. Couldn't sideload. When I would run "adb devices" , my device would be listed. If I ran "adb usb" I would get "error: closed" . The sideload command would just bring up a list of commands. This may help someone, I installed a new version of adb. Not sure if I can post links but the file name was adb-setup-1.1.exe. This installs the needed files, the installer didn't notify me where the files were installed but they installed right to my C:\ drive. This seemed to eliminate the problem for me. I did a lot of searching and couldn't find anyone with this specific issue, so if anyone finds themselves with this problem give this a try.
Click to expand...
Click to collapse
Perfect - worked for me - exact same issue - adb wasnt recognising my phone was in sideload and sideload command wouldnt work but push would - plus getting error closed message on adb usb command. Googled the above adb file, downloaded, 15 second install and now sideloading is working on my SG2 with CWM recovery 6.0.2.9 (kitkat). I was obviously using an outdated ADB driver (1.0.29).
Thanks a lot KoolAidBigMan !! Big up...
Jimbo
EDIT : Spoke too soon - now getting another error when trying to sideload.. will google it.. failed to write data 'protocol fault (no status)'
EDIT : Sorted. Ended up getting round it by pushing the files instead - found instructions on Cyanogenmod forums. Thanks once again.
http://forum.xda-developers.com/sho...wQFjAA&usg=AFQjCNGgPmMne0aYCd9RojZZhy89cQjnCw
Try this
Sent from my C6916 using XDA Free mobile app
Link not working?? Im ok now anyway.. Time to test my screen casting to my Chromecast.. :fingers-crossed:
mtk6572 have same error
I have same error.. but I know that my phone's usb debugging is not enable.. so I got this error:close..
My phone is on bootloop so I can't enable the usb debugging.. Is there any way to enable the usb debugging using adb commands? I trying to push the framework-res.apk on my phone.. because it is the cause of the bootloop.
i'm a nood
Ok so on my HTC One I loaded TWRP recovery and had a rom installed. I wanted to wipe it out and reinstall a newer version of the rom, and in the process I thought I had a "virtual SD" that wouldn't be wiped out. Boy was I wrong. Now I can get into TWRP and I am reading about "adb sideload" to load a rom zip file to the phone.
I have Windows 8 and I used the trick of installing Windows 7 drivers, but now for some reason the computer shows "Android Device" with an exclamation point. I google'd and found a Windows 8 HTC driver, and now the device shows up "Android USB Devices - MyHTC". So it appears I have drivers installed.
Now I read tutorials and have been searching for hours and I cannot get this to work. I have the ADB Fastboot folder on my desktop and the rom I want to load in that folder. I bring up the command prompt and type in "adb devices". It returns with this:
List of devices attached
FA34PS904380 host
I type in (without quotes) "adb sideload rom.zip" which is in the same directory. It returns with all the possible commands (like a help menu) of how you can use adb.
I'm stuck. Any ideas?
Thanks
Nurmi_CEO said:
Ok so on my HTC One I loaded TWRP recovery and had a rom installed. I wanted to wipe it out and reinstall a newer version of the rom, and in the process I thought I had a "virtual SD" that wouldn't be wiped out. Boy was I wrong. Now I can get into TWRP and I am reading about "adb sideload" to load a rom zip file to the phone.
I have Windows 8 and I used the trick of installing Windows 7 drivers, but now for some reason the computer shows "Android Device" with an exclamation point. I google'd and found a Windows 8 HTC driver, and now the device shows up "Android USB Devices - MyHTC". So it appears I have drivers installed.
Now I read tutorials and have been searching for hours and I cannot get this to work. I have the ADB Fastboot folder on my desktop and the rom I want to load in that folder. I bring up the command prompt and type in "adb devices". It returns with this:
List of devices attached
FA34PS904380 host
I type in (without quotes) "adb sideload rom.zip" which is in the same directory. It returns with all the possible commands (like a help menu) of how you can use adb.
I'm stuck. Any ideas?
Thanks
Click to expand...
Click to collapse
Try moving the files to your Android-SDK/platform-tools folder
bigdaddy619 said:
Try moving the files to your Android-SDK/platform-tools folder
Click to expand...
Click to collapse
PERFECT! Thanks a ton!
download Hassoon's tool and side load if you are having issues
thread : http://forum.xda-developers.com/showthread.php?t=2236814
and the thread that would have saved you from making this one... http://forum.xda-developers.com/showthread.php?t=2258809
Nurmi_CEO said:
PERFECT! Thanks a ton!
Click to expand...
Click to collapse
I'm guessing that worked?
bigdaddy619 said:
I'm guessing that worked?
Click to expand...
Click to collapse
Yes it did. Instantly after that. I was searching and trying stuff for hours, gave up and decided to post. Thanks for the help.
Nurmi_CEO said:
Yes it did. Instantly after that. I was searching and trying stuff for hours, gave up and decided to post. Thanks for the help.
Click to expand...
Click to collapse
No worries glad you got it
Nurmi_CEO said:
PERFECT! Thanks a ton!
Click to expand...
Click to collapse
Hitting the thanks button for someone who helps is proper etiquette
IMHO anyways :good:
budeone said:
Hitting the thanks button for someone who helps is proper etiquette
IMHO anyways :good:
Click to expand...
Click to collapse
No worries I don't do it for the thanks I do it because I enjoy helping when I can
Sent from my Liquid Smooth Nexus 7