After searching and searching and searching I need to post a few questions.
I "accidentally" wiped the internal storage on my HTC One, and I have been trying to side load a new rom for 3 hours with no luck at all.
I hit adb sideload in TWRP it just sits at starting adb side load feature... and does nothing.
On my mac I have ADB installed and it pops up as usual in a terminal window, but when I search for devices, it shows no devices found.
Any suggestions other than to search the forums, because I have had no luck.
allhailcardiel said:
Hopefully this thread can be moved then.
Yes, I have the phone in recovery when searching.
that is really all I can do with the phone currently is boot to recovery.
Click to expand...
Click to collapse
I'm not familiar with Mac and what you need. Did adb work before on that Mac with your HTC one?
Sent from my HTC One using Tapatalk 4
xcrazydx said:
I'm not familiar with Mac and what you need. Did adb work before on that Mac with your HTC one?
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
I finally figured it out, and I can't tell you why this worked.
As I said I could not do anything with my device other than boot into recovery. So I started looking everywhere in TWRP in and out of the different menus, and for some reason decided to wipe the system again.
After I wiped the system again I connected my device to my mac, and punched a couple commands. Next thing I know I hit enter with my fingers crossed, and my serial number pops up.
after that happened I was able to side load a ROM, and I am now currently back up and running slightly ashamed, and fully aware never to check the system button on a device without an external SD slot.
allhailcardiel said:
I finally figured it out, and I can't tell you why this worked.
As I said I could not do anything with my device other than boot into recovery. So I started looking everywhere in TWRP in and out of the different menus, and for some reason decided to wipe the system again.
After I wiped the system again I connected my device to my mac, and punched a couple commands. Next thing I know I hit enter with my fingers crossed, and my serial number pops up.
after that happened I was able to side load a ROM, and I am now currently back up and running slightly ashamed, and fully aware never to check the system button on a device without an external SD slot.
Click to expand...
Click to collapse
Glad it worked, I don't use Mac so I didn't know what all was needed to run adb or if you had it working previous to the wipe.
Sent from my HTC One using Tapatalk 4
allhailcardiel said:
After searching and searching and searching I need to post a few questions.
I "accidentally" wiped the internal storage on my HTC One, and I have been trying to side load a new rom for 3 hours with no luck at all.
I hit adb sideload in TWRP it just sits at starting adb side load feature... and does nothing.
On my mac I have ADB installed and it pops up as usual in a terminal window, but when I search for devices, it shows no devices found.
Any suggestions other than to search the forums, because I have had no luck.
Click to expand...
Click to collapse
I doubt you will ever wipe your internals again after this experience, but its always good to have an OTG cable that you can buy online for like $3.. You can install from usb flash using this cable in twrp recovery like its an external sd card. Its also useful for other simple transfer type of work.
Thread has been moved to Q&A. :good:
Help me
allhailcardiel said:
I finally figured it out, and I can't tell you why this worked.
As I said I could not do anything with my device other than boot into recovery. So I started looking everywhere in TWRP in and out of the different menus, and for some reason decided to wipe the system again.
After I wiped the system again I connected my device to my mac, and punched a couple commands. Next thing I know I hit enter with my fingers crossed, and my serial number pops up.
after that happened I was able to side load a ROM, and I am now currently back up and running slightly ashamed, and fully aware never to check the system button on a device without an external SD slot.
Click to expand...
Click to collapse
Hey man, I am on the same boat right now. Can you please tell me the exact steps you took to recover?
I am fairly new at this and kinda freaking out.
Thanks.
Good news, I just managed to do it!
So here is how it goes on Mac OS X (I personally use 10.7.5.).
Before you begin with your computer:
- go into recovery
- advanced
- reboot into recovery
If it reboots straightaway, you're ready to go. But it might wait, and offer you to root your phone. Do that, otherwise it won't work!
I would also restart the computer, just for a clean start. I also wiped my phone once again (factory reset).
On your Mac:
- make sure your rom (*.zip) is inside the platform-tools folder (this is inside the android sdk, where adb is)
- your phone should be disconnected and in recovery mode
1. open Terminal
2. type: cd (press space)
3. pull the platform-tools folder onto the terminal, press enter (this is here: /android/sdk/platform-tools)
4. type: ./adb kill-server (enter)
5. type: ./adb usb (enter) -> now it should say that "error: device not found"
6. connect your phone to the computer with the usb
7. type: ./adb devices -> it should show your phone, recovery mode
8. in your phone enter sideload mode (either in advanced, or in install zip option)
9. type: ./adb devices -> check if your phone is connected in sideload mode
10. type: ./adb sideload + <full name of the rom, including .zip, without brackets>
It should work, for me everything went perfectly.
Press thanks if it helped! Good luck :good:
*edit: Don't forget to logout in the end (just type logout and hit enter)
If the Terminal keeps saying that daemon can't be started, restart the computer and it should work.
Danvid113 said:
Good news, I just managed to do it!
So here is how it goes on Mac OS X (I personally use 10.7.5.).
Before you begin with your computer:
- go into recovery
- advanced
- reboot into recovery
If it reboots straightaway, you're ready to go. But it might wait, and offer you to root your phone. Do that, otherwise it won't work!
I would also restart the computer, just for a clean start. I also wiped my phone once again (factory reset).
On your Mac:
- make sure your rom (*.zip) is inside the platform-tools folder (this is inside the android sdk, where adb is)
- your phone should be disconnected and in recovery mode
1. open Terminal
2. type: cd (press space)
3. pull the platform-tools folder onto the terminal, press enter (this is here: /android/sdk/platform-tools)
4. type: ./adb kill-server (enter)
5. type: ./adb usb (enter) -> now it should say that "error: device not found"
6. connect your phone to the computer with the usb
7. type: ./adb devices -> it should show your phone, recovery mode
8. in your phone enter sideload mode (either in advanced, or in install zip option)
9. type: ./adb devices -> check if your phone is connected in sideload mode
10. type: ./adb sideload + <full name of the rom, including .zip, without brackets>
It should work, for me everything went perfectly.
Press thanks if it helped! Good luck :good:
*edit: Don't forget to logout in the end (just type logout and hit enter)
If the Terminal keeps saying that daemon can't be started, restart the computer and it should work.
Click to expand...
Click to collapse
PHP:
Having same problem. Did you have to install eclipse or can i just install sdk?
lankyboy29 said:
PHP:
Having same problem. Did you have to install eclipse or can i just install sdk?
Click to expand...
Click to collapse
Just the sdk. At least for me it worked ok
Danvid113 said:
Just the sdk. At least for me it worked ok
Click to expand...
Click to collapse
PHP:
ok i got through the side load steps. I did the side load yet on my phone it does nothing while in side load mode that is. Does it supposed to say anything once I side load the .zip or do I just hit cancel after and reboot.
Thanks.
---------- Post added at 01:52 PM ---------- Previous post was at 01:39 PM ----------
Do you know what mount does? because only data and cache were selected. do i need system checked as well?
lankyboy29 said:
ok i got through the side load steps. I did the side load yet on my phone it does nothing while in side load mode that is. Does it supposed to say anything once I side load the .zip or do I just hit cancel after and reboot.
Thanks.
Click to expand...
Click to collapse
ok, so what should happen is that your computer shows that it is transferred. After it is done, your phone should install the program. Sometimes it doesn't show anything for me. These times i just wait until something happens, if still nothing either hit cancel or back. It worked for me every time; if you still have problems, you should upload a video of the whole procedure, so I can have some idea of what is going wrong (send a youtube link in pm)
Danvid113 said:
Good news, I just managed to do it!
So here is how it goes on Mac OS X (I personally use 10.7.5.).
Before you begin with your computer:
- go into recovery
- advanced
- reboot into recovery
If it reboots straightaway, you're ready to go. But it might wait, and offer you to root your phone. Do that, otherwise it won't work!
I would also restart the computer, just for a clean start. I also wiped my phone once again (factory reset).
On your Mac:
- make sure your rom (*.zip) is inside the platform-tools folder (this is inside the android sdk, where adb is)
- your phone should be disconnected and in recovery mode
1. open Terminal
2. type: cd (press space)
3. pull the platform-tools folder onto the terminal, press enter (this is here: /android/sdk/platform-tools)
4. type: ./adb kill-server (enter)
5. type: ./adb usb (enter) -> now it should say that "error: device not found"
6. connect your phone to the computer with the usb
7. type: ./adb devices -> it should show your phone, recovery mode
8. in your phone enter sideload mode (either in advanced, or in install zip option)
9. type: ./adb devices -> check if your phone is connected in sideload mode
10. type: ./adb sideload + <full name of the rom, including .zip, without brackets>
It should work, for me everything went perfectly.
Press thanks if it helped! Good luck :good:
*edit: Don't forget to logout in the end (just type logout and hit enter)
If the Terminal keeps saying that daemon can't be started, restart the computer and it should work.
Click to expand...
Click to collapse
Thank you so much for this ,,i tried everything with no success. This worked for me.You are the best. Im bookmarking this so if it happens again. Bang I know where to look.
I'm also using Mac (10.9.x) and had the same problem - accidentally wiped my HTC One sdcard and had no ROM, nothing and sideload didn't work (when I give the adb sideload command in terminal, it exits within a few secs and nothing changes on the phone).
The quickest solution for me was to just stay in TWRP with USB connected and....
1) Manually copy the ROM binary in terminal ie. :
adb push <path_to_ROM> /sdcard/
2) After above completes, in TWRP, just select "Install zip from sdcard" and select the file copied above from /sdcard/
Your description worked for me. Thanks you!
But I also had issues with adb . If anyone ever looking for a solution go to stackoverflow and search "Installing ADB on MAC OS X"
and then apply Danvid113s solution.
xcrazydx said:
Glad it worked, I don't use Mac so I didn't know what all was needed to run adb or if you had it working previous to the wipe.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Im on the same boat. what did you do exactly?
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 everyone! Please help me. I've accidentaly typed in Terminal Emulator commad "stop" with SU permissions and my phone first freezed then don't want to boot up. How can i start my phone? I can access only recovery and fastboot.
Edit: Also i can run adb commands. So the question, what command i need to run for start phone?
If you have access to fastboot you could simply use RSD Lite to reflash your phone to stock.
DeathChaos said:
If you have access to fastboot you could simply use RSD Lite to reflash your phone to stock.
Click to expand...
Click to collapse
I don't want to flash stock then again set everything i need. I just need a correct command to run thru adb for start.
It's like "adb start" or "adb shell start", i don't know.
Abstractionist said:
I don't want to flash stock then again set everything i need. I just need a correct command to run thru adb for start.
It's like "adb start" or "adb shell start", i don't know.
Click to expand...
Click to collapse
Honestly, i never heard of the command "stop".
You could check the documentation for adb.
Edit: There is a command called start which "restarts execution of an emulator/device instance."
Abstractionist said:
Hi everyone! Please help me. I've accidentaly typed in Terminal Emulator commad "stop" with SU permissions and my phone first freezed then don't want to boot up. How can i start my phone? I can access only recovery and fastboot.
Edit: Also i can run adb commands. So the question, what command i need to run for start phone?
Click to expand...
Click to collapse
Can also connect that bad boy of yours to comp and run start command in terminal. I have done this too. I also ran bootanimation in android terminal, continous bootloop. But fun is had running those xbin/bin commands. Lol
XT912 RaZR SpYdEr CDMA
hit ThAnKs if I was helpful!!!
I have done this stop command too but my phone still boots up normally it just goes blank and my touch buttons are lit up and all I did was power off by holding power button for 6 seconds and power back on and booted up normally ? I'm alittle scared to play with commands now because I was just typing all random root user commands and I went through a bootloop like 5 times and I reflashed through RSD lite but I know now that I shouldn't play with those cmds now??
Okay so as we all know Bootloader was unlock and they specify the steps, but im not able to do the command prompt section.(Below)
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/twrp-2.8.0.0_vs985-signed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I have the twrp image on my storage, but i used mtp not Ethernet due to the reason that Ethernet mode won't read my phone.
Can anyone help me on how to void my warranty and get CP working
Please no hating, barely learning this stuff
Thanks!!
You need to have USB debugging enabled on your phone, adb installed on your computer and the LG drivers installed. If you have all that the steps to unlock are quite clear.
Also your phone needs to be on and you need to keep an eye on it as you will have to enable a couple of things when they pop up on your phone, one is to allow your computer to see your phone in debugging mode and the other is to Grant super user permission.
batsup606 said:
Okay so as we all know Bootloader was unlock and they specify the steps, but im not able to do the command prompt section.(Below)
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/twrp-2.8.0.0_vs985-signed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I have the twrp image on my storage, but i used mtp not Ethernet due to the reason that Ethernet mode won't read my phone.
Can anyone help me on how to void my warranty and get CP working
Please no hating, barely learning this stuff
Thanks!!
Click to expand...
Click to collapse
You need to be able to get the phone operating in Ethernet mode; otherwise the computer cannot pass it commands. Alternatively, you can use a terminal emulator ON your phone itself. That's what I did as I didn't want to boot my desktop rig up before I left. It works exactly the same, except you don't type "adb shell", just open the term emu and start with the SU line.
It works fine if you do it from a terminal emulator on ur phone just fyi
laxattack said:
It works fine if you do it from a terminal emulator on ur phone just fyi
Click to expand...
Click to collapse
Can confirm. This is the way I did it since I don't have access to a computer until later tonight. Just type the exact commands (except for adb shell) in a terminal emulator and you are done.
I can also confirm this is working.
I had to download the LG updater or whatever (when you first plug the phone in; says installer) despite Win7 saying it had autoinstalled the drivers then ADB could see the device when in ethernet mode.
Also the last command didn't work (guess I didn't have the TWRP in the right place) and was forced to do a battery pull after the Factory Reset (didn't erase my data or settings), booted fine and then I just flashed the recovery with Flashify (and now can get into recovery) but YMMV.
FLASHIFY
Hey whats up the easiest way to install this is an app called Flashyify in play store works great im unlocked without using adb. Let the roms begin. Thanks for the hard work that everyone put in. Just put twrp image on phone before you open flashyify and open and install and recovery will be installed
airintak25 said:
Hey whats up the easiest way to install this is an app called Flashyify in play store works great im unlocked without using adb. Let the roms begin. Thanks for the hard work that everyone put in. Just put twrp image on phone before you open flashyify and open and install and recovery will be installed
Click to expand...
Click to collapse
+1