[HELP] I replaced my HTC One Launcher And Now I Think I bricked It - Sprint HTC One (M7)

please delete thread
deleted

good news is, is that your not bricked. Assuming you have twrp installed, go back into recovery, then advanced, then ADB sideload. On your computer (assuming you have sdk installed), open a command prompt and navigate to your platform tools folder (or where ever adb is located) - (cd C:\where ever the folder is ), then make sure you have a rom (viper or stock) in the same folder as adb and in the command prompt do adb sideload nam_of_rom.zip (may take a few minutes)

jcwxguy said:
good news is, is that your not bricked. Assuming you have twrp installed, go back into recovery, then advanced, then ADB sideload. On your computer (assuming you have sdk installed), open a command prompt and navigate to your platform tools folder (or where ever adb is located) - (cd C:\where ever the folder is ), then make sure you have a rom (viper or stock) in the same folder as adb and in the command prompt do adb sideload nam_of_rom.zip (may take a few minutes)
Click to expand...
Click to collapse
...what he said, or just use the RUU to go back go stock.
---------- Post added at 10:36 AM ---------- Previous post was at 10:34 AM ----------
Either way it sounds like you'll be just fine but make sure there's juice in your battery before trying any of the solutions.

ADB Can't find the device :/
deleted

Wipe and reflash rom
Sent from my HTCONE using Tapatalk 4 Beta

raphyv23 said:
I tried to sideload it but adb would not recognize my HTC One. I have installed the drivers correctly on Windows 8 and its recognized as Android ADB Interface under Android Devices on my device manager. when i type adb devices on adb it doesnt come up with anything. I also tried using my Windows 7 Laptop but the drivers wont install on windows 7
Please help :/
Click to expand...
Click to collapse
your cmd window needs to be in the folder with the adb tool, normally something like c:adroid sdk\platform tools navigate to this directory in windows explorer the hold shift and right click on and empty part of the window and select "open command prompt here"

Still wont work
deleted

raphyv23 said:
Thats where it is and it wont work my device is attached to the pc as you can see on the picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
in your recovery, when your in advanced, did u swip to start sideload? even if it doesnt recognize it, try to sideload a rom anyways, should give u a %

raphyv23 said:
Thats where it is and it wont work my device is attached to the pc as you can see on the picture
Click to expand...
Click to collapse
are you running as administrator, try typing after that adb reboot bootloader and see what you get
another thing are you using a 3.0 usb port??

It worked thank you
deleted

Related

[Q] Is there a way to let my computer have root access to my phone?

I want to change the icons for all my apps and APK edit needs the .apk file. Unless there's an easier way to do this.
Adb shell
Would give u terminal
Then su.
Would give you root access
But you could also do ...
Adb pull /where/your/app/is/located
Sent from my SAMSUNG-SGH-I897 using XDA App
^ What he said. You can also use DroidExplorer but in my opinion it isn't the best thing to depend on.
For some reason I just couldn't get adb to work right. Every time I tried to launch it it screwed up and then closed again. I'll try DroidExplorer. If that doesn't help I'll try adb again. Thanks guys.
You have to use a command prompt. You don't just double click it to open.
Hm, when I tried to install DroidExplorer I got this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BigTortoise said:
Hm, when I tried to install DroidExplorer I got this:
Click to expand...
Click to collapse
Learn how to use adb or go home
Sent from my SAMSUNG-SGH-I777
you could use a root file explorer on your phone and copy all the apks to your sdcard, mount that to the pc, modify the apks, and then either drop all those back in with the same file explorer or make a flashable zip containing all of them...
studacris said:
you could use a root file explorer on your phone and copy all the apks to your sdcard, mount that to the pc, modify the apks, and then either drop all those back in with the same file explorer or make a flashable zip containing all of them...
Click to expand...
Click to collapse
adb pull /system/app/nameoffile.apk
or
adb pull /system/app/*
so much faster.
if you dont learn how to use ADB, you will find yourself up **** creek at some point, if you plan on doing ANY modifications/theming. especially theming, because if you screw up your framework-res.apk, you have no way of fixing it without adb access....
lets not take the lazy ass way out of it here. when you are doing anything to your phone, you should know basic adb commands. if you dont, you shouldnt be touching your phone
This page should help with learning the commands
>>HERE<<
This page is a thread where I had problems with adb on Ubuntu
>>HERE<<
And this is a page that Pirateghost recommends on getting you started with adb
>>HERE<<
Now, we have done about everything we can for at this point, short of coming to your home and doing it for you. Have fun, and be careful out there.

[Q] ADB Device not found but KFFA works

I'm sure there have been some other topics about this, but I haven't found a post that fixes my issue, or applies to my situation. I will gladly read though any linked posts to try to fix the problem.
All ADB commands that KFFirstAide does are successful, but when I try using ADB on my own (trying to install the bootloader) it can't find the device. What am I doing wrong?
I would use KFFirstAide to install the bootloader, but I'm running 7.3.0, and so I have to do it manually
I have been running it from the platform-tools directory. I thought that maybe because on windows 7 files in the C:\Program Files (x86)\ directory are somewhat protected, that I should copy the folder to the desktop. I did so, and it still cannot find the device when running "adb devices" command. I then tried using the admin command prompt, and it couldn't find the device either.
There are no yellow triangles in the device manager, and commands issued by KF First Aide work fine, so I'm not sure why it's not working manually...
Thanks in advance for any help!
I followed the tutorial rev Kyle have on getting adb working and have never had a problem... google rev Kyle kindle fire hd forum
Sent from my GT-P3110 using xda app-developers app
After watching this video, Rev Kyle suggested that the Android SDK might not be properly installed. I currently do not have good internet, so is there any way I can check to see if the SDK is properly installed without re-installing it?
Here is a pic of what is going on
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
kthedude said:
All ADB commands that KFFirstAide does are successful, but when I try using ADB on my own (trying to install the bootloader) it can't find the device. What am I doing wrong?
Click to expand...
Click to collapse
ADB works fine with my Kindle Fire HD 7". I'm using Windows 7. Try to kill ADB server from the Windows task manager, and run "adb devices" again. Also, try to connect/reconnect your device from USB a few times.
I've done all of this. The thing that puzzles me is that kindle fire first aide uses adb of its own, right? As you can see in my picture, KFFA finds the device using its adb, but when I run adb through the command prompt it cannot find the device. In the picture above, I used both programs within the same minute. How can it work one way but not the other?
Would wiping the kindle help in any way?
Sent from my KFTT using xda app-developers app
kthedude said:
I've done all of this. The thing that puzzles me is that kindle fire first aide uses adb of its own, right? As you can see in my picture, KFFA finds the device using its adb, but when I run adb through the command prompt it cannot find the device. In the picture above, I used both programs within the same minute. How can it work one way but not the other?
Would wiping the kindle help in any way?
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
Copy the adb.exe from the KFFA directory to the SDK platform-tools directory.
soupmagnet said:
Copy the adb.exe from the KFFA directory to the SDK platform-tools directory.
Click to expand...
Click to collapse
Thank you so much! Worked just fine!
Also, moving to C:\KFFirstAide and running adb from there works as well.

[ Help ] Device offline in ADB

Please,Someone help me fix this issue
Code:
C:\Users\MANH>adb devices
List of devices attached
FA364W914159 offline
THANKS ALL !
Stock 4.4.2 ,Fastboot uncheck,Usb debugging is enable.
Have you checked that USB debugging is switched on in the settings? Try restarting the adb server using "adb kill-server" and then "adb start-server".
JasSingh93 said:
Have you checked that USB debugging is switched on in the settings? Try restarting the adb server using "adb kill-server" and then "adb start-server".
Click to expand...
Click to collapse
the same issue in offline. already tried restart adb server, and reinstall HTC driver, and replug USB cable, and switch all USB port on my computer, even change my computer from windows to Mac, also remind me device offline.
BTW, already delete adb key file in the folder ".android", but there is no new key file generate. so I guess the problem is in my phone.
trying to download android sdk now, to make sure i use the latest version adb tool, I hope this can fix the problem.
I download latest sdk, and replace the adb tools I used with the version in platforms folder. then adb give me a different answer below:
C:\Users\fudaming\Downloads\unlock>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HC34YW904321 unauthorized
And a dialog box jump out, let me choose to agree the authorize the computer connect to the phone or not, I choose yes, then everything is ok.
C:\Users\fudaming\Downloads\unlock>adb devices
List of devices attached
HC34YW904321 device
adb devices offline
can anyone help me???
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Philips9 said:
can anyone help me???View attachment 3120300
Click to expand...
Click to collapse
turn off usb debugging on the phone
turn it back on and grant the key that pops up
clsA said:
turn off usb debugging on the phone
turn it back on and grant the key that pops up
Click to expand...
Click to collapse
That is the problem.... I've already turned off debugging usb, turned it back on, but no pops appeared
where i'm wrong?
Philips9 said:
That is the problem.... I've already turned off debugging usb, turned it back on, but no pops appeared
where i'm wrong?
Click to expand...
Click to collapse
you reboot the phone and the PC ?
clsA said:
you reboot the phone and the PC ?
Click to expand...
Click to collapse
Yes, I solved with another rom....but
Now I see my device with "adb devices" or reboot("adb reboot"), but I can't push or flash rom with adb in recovery....
This problem is the same when I tried to make S-off with Firewater
Philips9 said:
but I can't push or flash rom with adb in recovery....
Click to expand...
Click to collapse
What do you mean exactly? ADB outputs an error when trying to push the file?
This problem is the same when I tried to make S-off with Firewater
Click to expand...
Click to collapse
FIrewater is discontinued
alray said:
What do you mean exactly? ADB outputs an error when trying to push the file?
FIrewater is discontinued
Click to expand...
Click to collapse

[Q] Auto root not working for me

Hello, I have tried to follow the AIO guide that has a sticky, but I had no luck there. I ended up installing "adb-setup-1.4.2" by snoop05 on my windows PC and that got me started in the right direction (I think). I've unlocked my bootloader, it says device is UNLOCKED: status code 3. Awesome.
Now to use CF-Auto-Root. I have my phone in bootloader mode. I run "root-windows" batch file and the cmd prompt comes up (ran as admin), I press any key to continue and this happens:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://imgur.com/bcliyxO
I then press any key again, and nothing changes. No red android, no change.
What the f*** am I doing wrong?!
Please halp!
Thank you.
What I did was shift right click in the explorer window and you should see a option to open cmd window here. Then type in root-windows.bat and hit enter.
Basically the cmd prompt is not at the right directory. Which is causing the failure
Wow ok, I figured it out. Don't run as administrator, just run the batch file normally.
/facepalm.
kyrue said:
Wow ok, I figured it out. Don't run as administrator, just run the batch file normally.
/facepalm.
Click to expand...
Click to collapse
I don't know that administrator mode was the problem. Like Elevate08 wrote, just opening the batch file probably didn't work because adb wasn't in the same directory. I added adb/fastboot to the PATH variable so I can run it from anywhere. I don't use the explorer for this sort of thing though. I just open a command prompt.
He wasnt in the correct place to do what he did.....the files are in a folder called root and the batch file called cmd.exe from windows\system32
Open a command prompt in the root folder as administrator, then run the batch file from the command line. Or open the command prompt and then run the batch file as administrator which is the same difference
GL
Hey thanks everyone for the replies. I didn't do anything different other than running the windows batch file normally, instead of running as administrator. I'm sure it was cringe worthy to a lot of people on here but at least I got it done. I installed TWRP and did a backup, which I then transferred to my PC. downloading a custom ROM now, and going to give that a try too

Question [FIXED] fastboot.exe/Mi Unlock Tool won't recognize my device

Hello!
I wanted to unlock my bootloader on my Redmi Note 11, but I have ran into a problem. It won't detect it in fastboot.exe or the Mi Unlock tool. I already:
Installed the Google USB driver
Updated the Mi Unlock tool, My phone, Windows
Enabled USB debugging & OEM unlocking
Booted the device in fastboot mode (Orange text saying FASTBOOT)
Can anyone help? Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is the cable good and is there a normal connection for data exchange with the phone?
Are you using the USB port from the motherboard?
Does the adb devices command work and can you see the device?
ze7zez said:
Is the cable good and is there a normal connection for data exchange with the phone?
Are you using the USB port from the motherboard?
Does the adb devices command work and can you see the device?
Click to expand...
Click to collapse
Thanks for your reply
The cable is in perfect condition, it was shipped with my phone and it works.
No I am using the one on the case, I am not sure on how it will affect this in any way but I am gonna try it.
Nope, ADB doesn't report anything
yo!
this happened to me also, i did fixed it by installing the fastboot driver
1. download the attachment below.
2. then extract it, a folder called 'Fastboot driver' should appear.
3. now, press Win+R, and a Run window should appear.
4. copy paste this 'devmgmt.msc' (without the quotation) into it, press OK.
5. Device Manager should appear. On top left, go to Action -> Add Drivers.
6. Browse to the 'Fastboot driver' folder, select it, click OK and then click Next.
7. after 'Drivers successfully installed', click Close.
now if things goes right, fastboot should be detected by now.
if not, idk tbh
Thunderoar said:
yo!
this happened to me also, i did fixed it by installing the fastboot driver
1. download the attachment below.
2. then extract it, a folder called 'Fastboot driver' should appear.
3. now, press Win+R, and a Run window should appear.
4. copy paste this 'devmgmt.msc' (without the quotation) into it, press OK.
5. Device Manager should appear. On top left, go to Action -> Add Drivers.
6. Browse to the 'Fastboot driver' folder, select it, click OK and then click Next.
7. after 'Drivers successfully installed', click Close.
now if things goes right, fastboot should be detected by now.
if not, idk tbh
Click to expand...
Click to collapse
Thank you, I forgot to mention I already fixed this.
_matteodev said:
Thank you, I forgot to mention I already fixed this.
Click to expand...
Click to collapse
can you mention how you fixed it? i'm having the same problem

Categories

Resources