guys
i want to flsah stock firmware MM for m8
can anyone guide me????
Mohamed Elhadad said:
guys
i want to flsah stock firmware MM for m8
can anyone guide me????
Click to expand...
Click to collapse
First question........Have you ever flashed a rom before? If not, I wouldn't try this until you read the Stickys at the beginning of this forum, General Forum and, Development Forum. This will save you a lot of headaches in the long run. I can not guarantee that you will not brick your phone but, it will help you to not make some of the more common mistakes.
Second question(Two parts actually)............Do you have htc sync and drivers installed on your PC? Also, do have the proper ADB files install on your PC?
Third question..........Have you searched the forum on the process? There is a lot of information on how to do this.
In addition without any information on what version of M8 you have, it will be hard to point you in the right direction. Also, the guys here like to see that you have exhausted all your resources before you ask for help. Many of us have done tons of research to get this far and are glad to share information. But you have to do some of the leg work first. (Hope you understand and don't take offense. That is not my intention.)
If you have the htc drivers, htc sync, and proper ADB files already on your PC. Also make sure you have developer options and usb debugging enabled on your phone. Connect your phone to your PC. Once this is done, open your command prompt and cd (change disk) to your adb location. Then type adb devices into the prompt. This is to verify that your are connected. If you are connected it will give you a series of numbers and letters identifying your phone. If it does not give you this, install htc sync w/drivers and download the most up to date adb zip file you can find and extract it to the root of your C drive. Also, rename it ADB. Once your phone is identified in the command prompt, type adb reboot bootloader. Wait for your phone to get into bootloader mode. Once there, select fastboot and wait for your phone to connect. The screen should say FASTBOOT USB if connected. Once connected, then in the command prompt type fastboot getvar all and press enter. This will tell you everything about your phone. Cut that and paste here leaving out your IMEI and serial number. From there someone can begin to help you. I hope this provided some help..........Good Luck
Related
Ok, I have a T-Mobile locked and branded Desire and so trying to create a Goldcard but it just gives me Permission Denied when trying to get the CID, what am I doing wrong? I have followed the steps to the T
try the goldcard program?
YES!! Please seriously need help aswell with this. Have a sim free desire and I get to the line of code in the command prompt with
"ADB shell cat/sys/class/mmc_host/mmc1/mmc1:*/CID" and it just says device not found.
I am new to android so i'm pretty clueless with this. Any help would be greatly appreciated.
Kleptomaniac said:
... and it just says device not found.
I am new to android so i'm pretty clueless with this.
Click to expand...
Click to collapse
So about 'device not found'. I had this 'issue' when rooting mine a few weeks ago, so here's what I had to do.
When rooting, you're gonna be using the ADB tools to interface with your phone through USB. This would mean that the computer needs specific drivers for ADB to work properly, which for some reason, did not install well. I'm running Win7 x64 and had a hard time setting it up initially.
SO what you want to do is to first go to Device Manager on the PC and uninstall the drivers for anything related to the phone - it'd probably show up under 'Other devices' with a driver issue. Do that and unplug the phone.
Next, go to install PdaNet. Just run the exe and it will install the drivers you need for ADB to work! Once this is all done you can uninstall the PdaNet program if you don't use it - the drivers will still remain.
When you plug in your phone (it might prompt during the installation, I don't remember) and head to device manager now, you'll see a new entry at the top called Android Phone, with a device called Android ADB Interface. Once you see this, then you're good to go with the rest of the goldcard instructions you were following.
Just to be sure, reboot the PC and go to the Android SDK\Tools in a cmd prompt and type in adb devices. It should return with the serial number of your phone.
That's it, hope it helps!
Thanks alot man its nice to know people here are willing to help. I didn get the drivers but I used HTC sync instead to get them up and running, then after awhile of it still not working I found the goldcard program and it worked! Now all I have to do is wait for this root download to finish...
While I want to downgrade my Desire HD which is 2.2.1, I follow tutorials! Most ppl state they can access their phone during "charge only" mode in cmd! BUT I really can't!
In the cmd, I typed C:, then it prompt me: device is not ready!
I re-installed the HTC Sync, got the latest update.
I installed the Android SDK Manager, got all updated.
I installed JAVA SE...
All can't help...I really need help here...I have been working on it for hours *crying*
Is USB Debugging enabled in your phone?
Are you sure you got the Android USB driver correct installed, this was my problem when I was trying to do the same.
It ended up with that I because I'm running win7 64 bit had to modify the driver, and manually move som files to get it to work. Check that you Android phone pops up in device management when you connect it.
I'm new to this my self, and others may have others sollution. But I was stuck at this my self for a couple of days before I got it working with help of massive google searches about the subject
Dear All, yes...I am sure sure and sure my usb debugging is enabled...
I am using Windows 7 too...I wish someone can give me some advice that can solve my situation right now...
danielandroid said:
Dear All, yes...I am sure sure and sure my usb debugging is enabled...
I am using Windows 7 too...I wish someone can give me some advice that can solve my situation right now...
Click to expand...
Click to collapse
connect ur phone with charge only and usb debuging ticked,.unzip the file in my attachments and put the folder in drive c and type the following command
cd c:\adb (press enter)
then ull see c:\adb>
then type adb devices
if u see the serial number of your phone it means ur phone is connected
Thanks for your reply!!! Leather|Face!
1. I extracted your files into D: and make it D:\ADB
2. typed adb devices
>>List of devices attached
> HTXXXXXXXXX device
I got the serial number here!!! Thanks!!
I think I did made a very simple but serious mistake, while all tutorial using C:\ to extract the adb file and services, I am doing the SAME but my C: is my Android Device...my windows drive is D:
I think that's why I got stucked and I keep trying to play my cmd C: to access my phone in a charge only mode...
danielandroid said:
Thanks for your reply!!! Leather|Face!
1. I extracted your files into D: and make it D:\ADB
2. typed adb devices
>>List of devices attached
> HTXXXXXXXXX device
I got the serial number here!!! Thanks!!
I think I did made a very simple but serious mistake, while all tutorial using C:\ to extract the adb file and services, I am doing the SAME but my C: is my Android Device...my windows drive is D:
I think that's why I got stucked and I keep trying to play my cmd C: to access my phone in a charge only mode...
Click to expand...
Click to collapse
no probs buddy... just hit the thanks button ... good luck with unlocking ur phone and flashing custom roms... u will be amazed how awesome it is.. back 15 jan 2011... i didnt knew jack about anything whatsoever... now i know almost everything lol.. thanks to the great community of Xda and its dev's ,,, HATS OFF TO ALL ,, MY GREATEST RESPECT TO THEM
Really Thanks!!! I am going to figure out another problem...CID incorrect...
danielandroid said:
Really Thanks!!! I am going to figure out another problem...CID incorrect...
Click to expand...
Click to collapse
for that you have to radio s-off.. lemme knw if u want all link... i will give u complete guide .. top to feet
Hello friends,
How to get into fastboot to relock the bootloader, if my volume button is dead? By dead, I mean the ribbon has been ripped off of the mobo (it was soldered onto mobo).
Since I'm a brand-new noob, the only way I know of and have done is to get into fastboot mode and lock it back up like what I did when I unlocked it. Any other way to lock it, ideally within the Android OS? Since my volume buttons are completely dead, I doubt that I can get into any "mode" other than OS right now..
TIA!
adb reboot bootloader.
I've seen that command in a post from search earlier, but there was no response after that post.
Would you explain the procedure? I am afraid that I might do anything wrong on top of these disasters i've gone thru with this phone
I also saw another line during earlier search: "if they don't know how to setup an adb command, they probably shouldn't unlock their phones"... Looks like I've done what I shouldn't..?
I would say doing whatever ripped the volume button cable out was what you shouldn't have been doing If you unlocked the phone you have the software you used to unlock, right? What software/guide did you use/follow? Are you using Windows/Linux/Mac? The only way to get to the bootloader w/o the volume buttons (afaik) is to use adb via usb. If you provide more details I can try to help you.
cswithxda said:
I've seen that command in a post from search earlier, but there was no response after that post.
Would you explain the procedure?
Click to expand...
Click to collapse
Once you're in adb reboot bootloader, do fastboot oem lock. Opposite of how you unlocked it in the first place
cswithxda said:
I've seen that command in a post from search earlier, but there was no response after that post.
Would you explain the procedure? I am afraid that I might do anything wrong on top of these disasters i've gone thru with this phone
Click to expand...
Click to collapse
navigate your cmd line to the folder with adb and fastboot in it. Hook the phone up to the computer and type:
Code:
adb reboot bootloader
which will make your phone reboot into the bootloader mode. You can then proceed with what you need to do.
I also saw another line during earlier search: "if they don't know how to setup an adb command, they probably shouldn't unlock their phones"... Looks like I've done what I shouldn't..?
Click to expand...
Click to collapse
I agree with whoever said that. This is another example of people messing with things before reading and learning how they work.
Thanks for your help guys!
btw, anyone found xdadevelopers to load extremely slower in Firefox when compared to Chrome? (just offtopic)
Anyway, I unlocked the bootloader when I was switching to yakju cmd and this folder called "fastboot-and-adb" in which there is both adb.exe and fastboot.exe. I used command "fastboot unlock bootloader" or something alike.
I'll do some more search and learn. Don't want you guys to think of me as a lazy bone who unlocked their bootloader using 1-click toolkit
p.s. edit: in my other thread, someone suggested using quickboot app.
Thanks for your replies guys!
martonikaj said:
navigate your cmd line to the folder with adb and fastboot in it. Hook the phone up to the computer and type:
Code:
adb reboot bootloader
which will make your phone reboot into the bootloader mode. You can then proceed with what you need to do.
I agree with whoever said that. This is another example of people messing with things before reading and learning how they work.
Click to expand...
Click to collapse
Somehow it says device not found
I do have proper driver (Naked Driver Beta 0.5 by 1wayjonny) that my phone was able to be recognized under bootloader at the time when I could actually get into bootloader. My phone is also being recognized as media device now... I have also turning usb debug on...
Try adb remount
The ad devices
This should list the serial number
Then all commands should work
Sent from my Galaxy Nexus using xda premium
cswithxda said:
Somehow it says device not found
I do have proper driver (Naked Driver Beta 0.5 by 1wayjonny) that my phone was able to be recognized under bootloader at the time when I could actually get into bootloader. My phone is also being recognized as media device now... I have also turning usb debug on...
Click to expand...
Click to collapse
You need to turn USB debugging on, and then type "adb devices" and see if it shows up. It may not using the Naked Driver; I had to install the full Samsung USB driver package before ADB would see my Galaxy Nexus.
If it does show up, then you type "adb reboot-bootloader" and it should boot into fastboot. Then just type "fastboot oem lock" and it will wipe the storage partitions and restore the bootloader lock.
Thanks for the help at late night guys. I finally got into the bootloader, thru a mac tho Kinda ironic that I am a supporter of Windows, well, at least a firm user of Windows.
Tried adb remount, it still says device not found
synaesthetic said:
You need to turn USB debugging on, and then type "adb devices" and see if it shows up. It may not using the Naked Driver; I had to install the full Samsung USB driver package before ADB would see my Galaxy Nexus.
If it does show up, then you type "adb reboot-bootloader" and it should boot into fastboot. Then just type "fastboot oem lock" and it will wipe the storage partitions and restore the bootloader lock.
Click to expand...
Click to collapse
I believe that you quoted my "I have turned USB debug on" ;p
Gave up on trying Windows drivers. When I was flashing the Yakju, I tried Samsung full driver, and it didn't work on my machine, i.e., the phone can't be detected in bootloader mode, while the beta 0.5 driver worked. So I decided not to mess with it anymore.
It looks like when the phone is not under bootloader, windows recognize it fine as MTP devices and install proper samsung driver from the internet directly. This allows me to open it up in explorer to browse files and such, but the phone won't show up under adb devices somehow.
Looks like MTP device (when the phone is in Android OS) and the fastboot mode use two kinds of drivers. This is just my assumption, though.
Anyway, finally got into bootloader now with Mac, and it's pretty funny I have to do everything thru command as the volume rockers are dead
And most importantly, thank you guys for your help!
Just another update
It's real funny now that the bootloader is locked, I can't unlock it again cuz I don't have the volume button working, so I couldn't choose YES on the phone.
I'm not trying to unlock it again, but just to confirm if there's really no work around, in case I encounter this situation again in the future
Lucky that locking the bootloader won't erase everything, or I won't be able to flash a ROM with it locked... :cold sweating:
Hey all, trying to push gtalk library files to MildWild 4.3 system dir has turned into a massive headache.
ADB doesn't recognize I have my device connected. Commands always return "error:device not found". "adb devices" command returns blank.
From the tutorials I've read in these forums, I was under the impression HTC Sync drivers in fastboot mode are needed to use ADB. No dice. I've tried other drivers I've found in the forms as well: "android-usb-driver.zip" from unrevoked and "adb_driver_htc.zip" (found this in the sim unlock utility thread).
Any suggestions on how to troubleshoot this further?
What is the proper name of the device in device manager? Right now I'm using HTC Sync drivers in fastboot and the name is: Android USB Devices > My HTC.
The guides I've read never touch on this issue, they always skip it and assume the device is connectable.
Thanks in advance
JT-on said:
Right now I'm using HTC Sync drivers in fastboot and the name is: Android USB Devices > My HTC.
Click to expand...
Click to collapse
To use ABD you need to be connected in recovery or a booted device.
nlooooo said:
To use ABD you need to be connected in recovery or a booted device.
Click to expand...
Click to collapse
Brilliant. Like you said, ADB recognized my device in both booted OS and recovery. However, I needed to be in recovery to push files to the system directory. Thanks.
You're welcome. You can push in booted device you just need to enable superuser rights in adb shell.
Sent from my HTC Desire using Flashes and Thunders
JT-on said:
Hey all, trying to push gtalk library files to MildWild 4.3 system dir has turned into a massive headache.
ADB doesn't recognize I have my device connected. Commands always return "error:device not found". "adb devices" command returns blank.
From the tutorials I've read in these forums, I was under the impression HTC Sync drivers in fastboot mode are needed to use ADB. No dice. I've tried other drivers I've found in the forms as well: "android-usb-driver.zip" from unrevoked and "adb_driver_htc.zip" (found this in the sim unlock utility thread).
Any suggestions on how to troubleshoot this further?
What is the proper name of the device in device manager? Right now I'm using HTC Sync drivers in fastboot and the name is: Android USB Devices > My HTC.
The guides I've read never touch on this issue, they always skip it and assume the device is connectable.
Thanks in advance
Click to expand...
Click to collapse
90% of the time the problem is with the drivers etc. Use this tutorial to fix that : http://goo.gl/OS3Vi
If you still encounter the problem then you can use ADBwireless available at google play to wirelessly connect your device to the computer
Hope it helps :highfive:
Unchecking MTP did it. Thanks!!
Why is that necessary on the N7Flo but not my old N7 or the N4 (or any other device I've had contact with for that matter)?
Also, anyone know how I can get devices to show up as a folder...you know...like a thumb drive?
rmp5s said:
Unchecking MTP did it. Thanks!!
Why is that necessary on the N7Flo but not my old N7 or the N4 (or any other device I've had contact with for that matter)?
Also, anyone know how I can get devices to show up as a folder...you know...like a thumb drive?
Click to expand...
Click to collapse
You can't. Both the n4 and the n7 have their memorys formatted as ext4, partition type that windows can't access normally. MTP was the only sollution google had.
I have an HTC One M8, bought from UAE. I rooted it and it all went well. Now I want to get OTA updates on the phone and I want to unroot for the moment. The problem is that I connect my phone to my laptop run adb but it doesnt do anything. All it says is list of devices attached and thats it. Nothing else at all. I cant give my phone commands or anything of the sort. I want to update my phone to the latest android version with sense 7 and I would prefer that I have a stock rom hence the OTA but without getting my phone recognised with ADB I dont know how to do it. Please help!
P.s. I am running windows 7 and my CID is HTC__J15
I got the CID from an app from the app store, dont know if its legit but I the gulf region uses this CID so I guess its safe to assume its correct.
P.s.s. Yes I have tried reinstalling HTC drivers and it hasnt done anything. The device manager doesnt have any unknown device listed either. Yes USB Debugging is also on and I get the notification on the phone as well but my computer doesnt recognise it.
P.s.s.s. Is there anyway to get the latest OTA without hooking my phone up to the computer? I'm not a tech guy so I need help. A step by step would be very nice. Thanks
Boot into bootloader and perform the "fastboot getvar all" command. Post the output here without IMEI and serial no. as the software number is needed to provide further instructions and identify the correct RUU and/or backup you'd need.
Send by the swarm intelligence of my coffee machine ?.
flamingpenguin said:
The device manager doesnt have any unknown device listed either.
Click to expand...
Click to collapse
Meaning the device doesn't show up at all in Device Manager (HTC, Android phone, etc.)?
If you boot the phone into bootloader-fastboot mode, any response to fastboot commands (fastboot devices, etc.). Sometimes fastboot works, when adb doesn't. And fastboot is the really critical one you want.
HTCNerdYoda said:
Boot into bootloader and perform the "fastboot getvar all" command. Post the output here without IMEI and serial no. as the software number is needed to provide further instructions and identify the correct RUU and/or backup you'd need .
Click to expand...
Click to collapse
I tried booting into fastboot mode and then hooking it up with the computer. I enter the fastboot getvar all command and all I get is < waiting for device > it just stops there for as long as I wait and it doesnt do anything. Please help!!! I've tried different cables as well. Also a different laptop. I'm not sure whats wrong. The sync manager doesnt work either. Doesnt detect my phone :crying:
redpoint73 said:
Meaning the device doesn't show up at all in Device Manager (HTC, Android phone, etc.)?
If you boot the phone into bootloader-fastboot mode, any response to fastboot commands (fastboot devices, etc.). Sometimes fastboot works, when adb doesn't. And fastboot is the really critical one you want.
Click to expand...
Click to collapse
Media Transfer Protocol works. I just get a new drive with my phones internal and external storage. I can transfer files but thats the only response my computer gives to the phone. Help please :crying:
flamingpenguin said:
Media Transfer Protocol works. I just get a new drive with my phones internal and external storage. I can transfer files but thats the only response my computer gives to the phone. Help please :crying:
Click to expand...
Click to collapse
Did you activate the developer options and if so USB debugging as well. Did you try installing Sync Manager to install the needed HTC drivers, uninstall it (as it interferes with adb/fastboot sometimes) to just keep the drivers? Which adb/fastboot are you using?
Send by the swarm intelligence of my coffee machine ?.
flamingpenguin said:
Media Transfer Protocol works. I just get a new drive with my phones internal and external storage. I can transfer files but thats the only response my computer gives to the phone. Help please :crying:
Click to expand...
Click to collapse
Try this: Go into Windows Device Manager, find the device, pick the option to manually select the drivers. Then pick the generic Android MTP device drivers (or some such name like that). I often have to do this to get my home computer to pickup my phone via adb/fastboot, while MTP works just fine.
HTCNerdYoda said:
Did you activate the developer options and if so USB debugging as well. Did you try installing Sync Manager to install the needed HTC drivers, uninstall it (as it interferes with adb/fastboot sometimes) to just keep the drivers?
Click to expand...
Click to collapse
I have both developer options and USB debugging on. I also tried drivers that came with the phone via the sync manager. Tried after getting rid of the sync manager but it still doesnt work. I can get my software number from setting>about etc no? My CID and Software number is all I need to unroot the phone and install the stock recovery, if I'm not mistaken? I am completely dumb at this tech thing. I'm a civil engineer. I understand concrete and rebar
redpoint73 said:
Try this: Go into Windows Device Manager, find the device, pick the option to manually select the drivers. Then pick the generic Android MTP device drivers (or some such name like that). I often have to do this to get my home computer to pickup my phone via adb/fastboot, while MTP works just fine.
Click to expand...
Click to collapse
I cant find my device in the Device Manager at all =/
flamingpenguin said:
I cant find my device in the Device Manager at all =/
Click to expand...
Click to collapse
I'd suggest downloading the drivers again and first of all try with another USB data cable. If it doesn't show up at all, it sounds as if you got a connection problem. So could also be caused by a defective cable and/or USB port on your phone.
I'd check the following:
1) try connection to another USB port
2) try with another data cable
3) download latest HTC drivers from HTC.
Send by the swarm intelligence of my coffee machine ?.
I had this happen to me and to resolve it I went into the C: drive of my computer and in the program files folder I located the HTC folder. Once there I looked for the apk files that allow you phone to connect to HTC sync. If I remember correctly, I copied apk file #2 to my phone and installed it. Once it was install that issue went away. To be on the safe side, copy and install each apk file one at a time(there should be 5 of them) to your phone. Only one of them will install the others will not. This will help you to locate and install the correct apk file. Once you have found and installed the correct one, you can removed the other apk files that wouldn't install and reboot your phone. After that connect your phone to your computer, and htc sync and adb should recognize your device. There is a thread on this but I can not remember where to locate it.