Deleted OS//No Drivers//OTG Don't work - One (M7) Q&A, Help & Troubleshooting

Hello.
I wanted to flash CM12.1 to friends One(M7) but while flashing I have some kind of error.
I removed OS .. there is just TWRP 2.5.0.0 which seems don't recognize OTG USB.
Drivers for ADB or Fastboot while I'm in bootloader seems don't work I have windows 10 and only 3.0 USB Ports.
So now is there TWRP without nothing and I don't know what to do.. I have only 2 days for fix it.
//EDIT// It was unlocked and rooted so I just wanted to flash ROM like in others phones but like I'm reading more and more forums with HTC it's quite difficult and I'm not sure if everything is as it should be. Whats is S-ON/OFF?? What is RUU and how I know if "my" One is the right for which I can flash ROM. (But theses questions aren't important)
I see lot of theard with same problem but I can't find any real solution. I hope someone help me :fingers-crossed:

What happens when you type "fsstboot devices" in bootloader menu?

donkeykong1 said:
What happens when you type "fsstboot devices" in bootloader menu?
Click to expand...
Click to collapse
Typo, should be "fastboot devices".

in ur devices no os??? maybe can't flash because corrupt emmc..,.. sory for bad english

Fastboot devices don't show nothing
How to fix corrupt emmc? Without os or possibility connection with pc

dasti555 said:
Fastboot devices don't show nothing
How to fix corrupt emmc? Without os or possibility connection with pc
Click to expand...
Click to collapse
Hard to suggest much without knowing specifics of the phone but I think we are a long way from assuming the emmc is corrupt.
Try this link to get your drivers working, then give us the output of "fastboot getvar all"
http://forum.xda-developers.com/showthread.php?t=2317790

if ur device can bootloader it's means u can repair emmc maybe
I have experienced 0gb on my EMMC , but can bootloader ,it can repair EMMC with emmcblkp.zip , but I forgot his link
sory for bad in english

1-the rom did not flashed because you are using the wrong recovery version. You need at least 2.7.1.1 to flash Cyanogenmod roms (assuming your phone is a M7_UL variant)
2- Since you are using such an old recovery, it would make sense to me that it was flashed on the phone back in 2013 so maybe the phone never got any Ota updates and the hboot version is still 1.44? If yes you won't be able to get fastboot connectivity using Win8/10, only with win7/linux/OSx. That might be the problem.
3-can you write down all the information you see when in bootloader, with this we should at least be able to confirm what I said above
---------- Post added at 04:35 PM ---------- Previous post was at 04:32 PM ----------
bintang456 said:
if ur device can bootloader it's means u can repair emmc maybe
I have experienced 0gb on my EMMC , but can bootloader ,it can repair EMMC with emmcblkp.zip , but I forgot his link
sory for bad in english
Click to expand...
Click to collapse
There is nothing pointing to a bad emmc for now. He is at step 1 (getting the phone detected) and you are talking about a "possible" step 20.... Not saying you're wrong but it's way too early to assume a bad emmc

alray said:
1-the rom did not flashed because you are using the wrong recovery version. You need at least 2.7.1.1 to flash Cyanogenmod roms (assuming your phone is a M7_UL variant)
2- Since you are using such an old recovery, it would make sense to me that it was flashed on the phone back in 2013 so maybe the phone never got any Ota updates and the hboot version is still 1.44? If yes you won't be able to get fastboot connectivity using Win8/10, only with win7/linux/OSx. That might be the problem.
3-can you write down all the information you see when in bootloader, with this we should at least be able to confirm what I said above
---------- Post added at 04:35 PM ---------- Previous post was at 04:32 PM ----------
There is nothing pointing to a bad emmc for now. He is at step 1 (getting the phone detected) and you are talking about a "possible" step 20.... Not saying you're wrong but it's way too early to assume a bad emmc
Click to expand...
Click to collapse
One more thought on this phone. Did you also wipe the data partition? If not are you sure that the person that originally installed twrp didn't leave a nandroid backup on the device. Have you looked under restore in twrp? LIkely too simple but worth a shot!!

Yes you are absolutelly right!
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
Apr 20 2013, 15:46:23-1
So what should I do now?
I wanted to install today Windows7 but it failed and I ****ed it and I removed my old windows so I must 2 hours searching for new windows. Now I'm finally at Windows10 again.
So.. Maybe Windows7 in virtual box? Anyway one guy have Linux at his computer what can I do now?

sorry for my assume...

dasti555 said:
Yes you are absolutelly right!
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
Apr 20 2013, 15:46:23-1
So what should I do now?
I wanted to install today Windows7 but it failed and I ****ed it and I removed my old windows so I must 2 hours searching for new windows. Now I'm finally at Windows10 again.
So.. Maybe Windows7 in virtual box? Anyway one guy have Linux at his computer what can I do now?
Click to expand...
Click to collapse
Windows 7 in a virtualbox won't work afaik. Better to use a live Ubuntu usb/cd, setup adb and fastboot then you'll be able to update your twrp recovery and flash the rom. Also worth to post a "fastboot getvar all" at the same time. Maybe we could update the firmware easily (depending what the getvar all returns) and fix that connectivity problem at the same time.
Here is aguide how to use Ubuntu without having to install it on your computer: http://forum.xda-developers.com/showthread.php?t=2606577
It was writted for a different purpose so just ignore the steps talking about rumrunner.
---------- Post added at 10:59 AM ---------- Previous post was at 10:57 AM ----------
bintang456 said:
sorry for my assume...
Click to expand...
Click to collapse
No need to be sorry, everyone tries their best, thats what matters :good:
---------- Post added at 11:03 AM ---------- Previous post was at 10:59 AM ----------
Btw here is the reference for the minimum recovery requirement to flash CM:
TWRP recoveries with version greater than or equal to 2.7.0.8 support this fstab change.* If you have a favorite recovery maintainer, encourage them to incorporate "block: by-name" support into their recovery kernels!
Official 2.7.1.0 for m4, m7, m7spr/m7wls, and m7vzw/m7wlv mistakenly did not include the necessary fstab support, so 2.7.1.1 was released for these devices, addressing the issue.
More recent unofficial builds of TWRP can be found at android.cmphys.com. You'll find source code for all these devices linked there as well.
Click to expand...
Click to collapse
https://wiki.cyanogenmod.org/w/HTC_fstab_updates

So what I have to do now is
Connect phone to PC with Ubuntu then write in terminal "fastboot getvar all" and then write here again? Or Just "fastboot flash recovery.img"
Well ... I'm at Ubuntu and when we try "fastboot flash recovery recovery.img" then just waiting for devices .. need i some kind of fastboot drivers for ubuntu or what?
We tried download some kind of" # sudo apt-get install android-tools-adb android-tools-fastboot "
but phone is still not recognized

mb_guy said:
Typo, should be "fastboot devices".
Click to expand...
Click to collapse
Sorry, big fingers, small keyboard on my phone [emoji20]

dasti555 said:
So what I have to do now is
Connect phone to PC with Ubuntu then write in terminal "fastboot getvar all" and then write here again? Or Just "fastboot flash recovery.img"
Click to expand...
Click to collapse
I'll copy/paste from the guide linked above the step you need only:
(1) a copy of 32bit Ubuntu. NOT 64!! http://www.ubuntu.com/download/desktop
(2) no need to install-boot into it as if trying it (IMAGE 3)
(4) drivers NOT needed
I know others have had zero issues but some of us have had nothing but nightmares. This is who I'm sharing this for.
I hope it helps... Even just one!
Have fun all!
IF BY CHANCE YOU ARE HAVING ISSUES WITH ADB OR FASTBOOT IN UBUNTU SEEING YOUR DEVICE, TYPE sudo BEFORE YOUR COMMANDS. IT WANTS PERMISSION TO ACCEPT YOUR COMMANDS. WHEN YOU TYPE sudo THEN YOUR PASSWORD YOU ARE GRANTING THOSE PERMISSIONS. SOMETIMES THE ISSUE WON'T APPEAR TIL YOU GET INTO FASTBOOT. SO CHECK FIRST BY TYPING IN adb devices WHEN YOU FIRST OPEN THE TERMINAL. IF YOU GET A SERIAL NUMBER YOU SHOULD BE FINE. AFTER YOU GET INTO BOOTLOADER, TYPE fastboot devices IF YOU GET A "no permission" ERROR THEN YOU NEED TO TYPE sudo BEFORE all INSTRUCTIONS. SOME VERSIONS OF LINUX HAVE AN SU TERMINAL. THAT WOULD BE THE BEST TO USE AS IT REQUIRES ROOT/PERMISSION TO EVEN START AND WILL MAINTAIN THOSE PERMISSIONS THROUGHOUT.
UBUNTU STEPS.....
Image 3- Boot into Ubuntu
Image 7- Open Terminal in Ubuntu (Top left gear like symbol, click it and a search bar will appear, start typing terminal, it will appear below the bar, just select it)
Image 8- You need to install adb fastboot these are the instructions you need to type in the terminal you just opened. Type one line at a time and press enter after each. Allow Ubuntu to do it's stuff.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
Image 9-12 Shows how the terminal should look as it finds, downloads and install the appropriate files.
Image 13- After the downloads are finish you can check to make sure things were installed correctly. Type “adb” and your screen should look like this
Image 14- Type “fastboot” and this is the information that should appear.
Image 15- To make sure your device is seen type “fastboot devices” and it should show devices with a serial number.
then you can use "fastboot getvar all' and "fastboot flash recovery <file_name>.img"

We made all this now .. fastboot devices command not show nothing just new line which is waiting for command and when we try fastboot flash recovery recovery.img then <waiting for device>
we still dont have drivers or what?

dasti555 said:
We made all this now .. fastboot devices command not show nothing just new line which is waiting for command and when we try fastboot flash recovery recovery.img then <waiting for device>
we still dont have drivers or what?
Click to expand...
Click to collapse
You don't need drivers on linux. Is the phone booted in bootloader and in the fastboot menu? You should see "fastboot usb" in red when in the correct mode to use fastboot commands.
like on this image:
{
"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"
}

yes it is
its like transfer isnt working but charging is
edit : uh no :/ there is only fastboot in red not fastboot usb I should boot there while I'm connected via cable? // booting there while cable is pluged-in and still only fastboot in red

dasti555 said:
yes it is
its like transfer isnt working but charging is
edit : uh no :/ there is only fastboot in red not fastboot usb I should boot there while I'm connected via cable? // booting there while cable is pluged-in and still only fastboot in red
Click to expand...
Click to collapse
are you using the original usb cable? some cheap cable are only providing power but no data connection. I also just have noticed from your first post that you are using usb 3.0. You have to use a 2.0 port to avoid problems. you should have "fastboot usb" in red when there is a connection as opposed to "fastboot" only if there is none.
bootib there before or after doesnt matter

@alray We are trying it with different PC which have Ubuntu and also Kali Linux as dualboot.
Have only 2.0USB Ports..
I will try different cable.... Nope .. Still only fastboot without USB
My OnePllus One with same cable find but this HTC no :/

Related

Total Noob - need to install generic HTC software

Hi there, I currently have an HTC One M7 with Tmobile UK firmware and I am fed up waiting for update to KitKat and Sense 6. I understand that this is the correct place to ask a question on how to change the software so that it will take HTC official updates rather than tmob approved updates.
From what I have read I need to s-off with firewater first and flash a recovery. Is that correct? Does anyone have step by step instructions on what to do please as I do not want to brick my phone? I would like to install the "normal" HTC software and receive updates from HTC rather than wait for tmobile.
Thanks
BrownTrout said:
Hi there, I currently have an HTC One M7 with Tmobile UK firmware and I am fed up waiting for update to KitKat and Sense 6. I understand that this is the correct place to ask a question on how to change the software so that it will take HTC official updates rather than tmob approved updates.
From what I have read I need to s-off with firewater first and flash a recovery. Is that correct? Does anyone have step by step instructions on what to do please as I do not want to brick my phone? I would like to install the "normal" HTC software and receive updates from HTC rather than wait for tmobile.
Thanks
Click to expand...
Click to collapse
can you post your fastboot getvar all please ? remove imei and seial number beforeposting
Seanie280672 said:
can you post your fastboot getvar all please ? remove imei and seial number beforeposting
Click to expand...
Click to collapse
Hi Seanie, how do I do that? Sorry for the noobness but I really am new to this. Thank you for your help.
BrownTrout said:
Hi Seanie, how do I do that? Sorry for the noobness but I really am new to this. Thank you for your help.
Click to expand...
Click to collapse
do you have fastboot and adb installed on your computer ?
Seanie280672 said:
do you have fastboot and adb installed on your computer ?
Click to expand...
Click to collapse
No, I have downloaded adt-bundle-windows-x86.zip though, is this the correct thing?
easiest way is to download and install this, you need to run as administrator for it to work:
http://forum.xda-developers.com/showthread.php?t=2317790
---------- Post added at 11:57 AM ---------- Previous post was at 11:52 AM ----------
once installed, reboot your phone to fastboot mode, basically restart it and whilst its shutting down hold down the volume down button, you will enter the bootloader, plug it into the computer and select fastboot on the phone screen, if its not already there, its should now say fastboot usb.
Open a command window in the fastboot and adb window you have just installed on your computer, (control + shift + right mouse click on any white area in that folder, open command window here)
The type:
Code:
fastboot getvar all
post the output here minus imei and serial number
Seanie280672 said:
easiest way is to download and install this, you need to run as administrator for it to work:
http://forum.xda-developers.com/showthread.php?t=2317790
---------- Post added at 11:57 AM ---------- Previous post was at 11:52 AM ----------
once installed, reboot your phone to fastboot mode, basically restart it and whilst its shutting down hold down the volume down button, you will enter the bootloader, plug it into the computer and select fastboot on the phone screen, if its not already there, its should now say fastboot usb.
Open a command window in the fastboot and adb window you have just installed on your computer, (control + shift + right mouse click on any white area in that folder, open command window here)
The type:
Code:
fastboot getvar all
post the output here minus imei and serial number
Click to expand...
Click to collapse
Thanks, I have installed that and a DOS window has popped up and after entering the command it says "Waiting for device". Do I need to boot the phone pressing volume down to get this to work as I am currently on my "normal" boot i.e. what it looks like when phone is powered on.
BrownTrout said:
Thanks, I have installed that and a DOS window has popped up and after entering the command it says "Waiting for device". Do I need to boot the phone pressing volume down to get this to work as I am currently on my "normal" boot i.e. what it looks like when phone is powered on.
Click to expand...
Click to collapse
type adb reboot bootloader in that command window (DOS window)
{
"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"
}
BrownTrout said:
Click to expand...
Click to collapse
perfect :good:
Right your on hboot 1.55 s-off should be easy, boot back to android, type fastboot reboot in the command window (if you've not already rebooted that is)
use either rumrunner to s-off http://rumrunner.us/
or
Firewater to s-off http://firewater-soff.com/
Do not update before getting s-off, follow the instructions on each of the sites to use the tools, rumrunner is the easiest, just download the package, extract it and run the file, firewater is a little more complicated.
once done, report back here, there will only be 2 more steps to do after that, but keep adb and fastboot on your computer, do not remove them.
Many thanks, I am getting an error though
ahh ok try firewater temp root method, its the 3rd method down, you will have to download 2 files and put them in the same folder as fastboot and adb, where you open the dos window from, the whole thing is run from the dos window, so just copy and paste the commands one at a time as listed on the page.
ahh do you have USB debugging enabled on your rom ?
Thanks, it is attempting to acquire root just now. Will update when complete.
Thanks, I have temproot and s-off now.
excellent, now that you have s-off, you have to be very careful, if you flash the wrong thing, where the phone will stop you and tell you its wrong with some sort of error with s-on, it wont anymore, it will expect that you know what you are doing and still flash it, if its wrong it will brick.
---------- Post added at 01:19 PM ---------- Previous post was at 01:15 PM ----------
so fist all, if your phone is booted into android still, open a dos window again inside the fastboot / adb folder as before and again, type:
Code:
adb reboot bootloader
once there, make sure to says fastboot USB on the phone screen.
then be very careful with this one, CID is ALWAYS 8 characters long, bear that in mind with the next command, so the next command is 2 underscores not one inbetween the HTC and the 001. always capital letters, take note of your current cid though, you will need it for warranty purposes.
Code:
fastboot oem writecid HTC__001
when complete:
Code:
fastboot reboot-bootloader
---------- Post added at 01:28 PM ---------- Previous post was at 01:19 PM ----------
Its should now say this on your screen or something close to it:
M7_UL PVT SHIP S-OFF ??
CID-HTC__001
HBOOT-?????????
RADIO-??????????
OpenDSP-?????????
OS??????????
etc etc etc, can you confirm please ?
It's been hanging at < waiting for device > after I typed in the fastboot reboot bootloader command
BrownTrout said:
It's been hanging at < waiting for device > after I typed in the fastboot reboot bootloader command
Click to expand...
Click to collapse
the 3rd command or the 1st command ?
Managed to get it working.
BrownTrout said:
Managed to get it working.
Click to expand...
Click to collapse
so sorry, my bad, if it was the 1st command it should of been adb reboot bootloader not fastboot, ive edited the post above.
Seanie280672 said:
so sorry, my bad, if it was the 1st command it should of been adb reboot bootloader not fastboot, ive edited the post above.
Click to expand...
Click to collapse
I have manually rebooted and ran the commands that you mentioned and it appears to have worked as the phone displays what you have posted above.

[Q] Soft-Bricked? HTC One M7 AT&T - Need Help

Hey all, going to try to post as much information as possible I'm a noob with this sort of thing. I had Cyanogenmod 11 on here but had lots of battery issues and stability issues, passing this phone off to a friend before she travels internationally and want to just get stock OS back on it. I've tried to follow several guides but none have really gotten me all the way to due several issues on the way that aren't really covered in those guides so I'm stuck asking for help after a few days of struggling with this.
Phone Info:
For Fastboot info (I can't post outside links yet)...
imgur/dgOIaG6
For hboot info... (I can't post outside links yet)
imgur/7z0Bi6Z
Ideally I'd like to get stock sense back on the phone, or Google Play Edition.
Here are a few instances of it bombing during commands.
D:\Development\AndroidStudio\sdk\platform-tools>fastboot flash recovery twrp.img
sending 'recovery' (9434 KB)...
OKAY [ 1.168s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.575s
D:\Development\AndroidStudio\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[nothing]
All of the RUU's(I tried all of the Cingular ones) just say they're "Sending" and never get to a progress bar. They just leave my phone with an HTC logo and nothing else.
Console Output from HTC One Toolkit
adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adb shell /data/local/tmp/./revone -s 0 -u
error: device not found
adb shell /data/local/tmp/./revone -s 0 -u
error: device not found
adb push "D:\Development\AndroidStudio\sdk\platform-tools\TWRP.img" "File Destination...Use \ NOT / or // !"
At this point adb doesn't really appear to be working at all, and fastboot is the only response I'll get.
I'm down to actively work on this issue and follow any troubleshooting steps you guys throw at me.
Thanks in advance.
Phaymous said:
Hey all, going to try to post as much information as possible I'm a noob with this sort of thing. I had Cyanogenmod 11 on here but had lots of battery issues and stability issues, passing this phone off to a friend before she travels internationally and want to just get stock OS back on it. I've tried to follow several guides but none have really gotten me all the way to due several issues on the way that aren't really covered in those guides so I'm stuck asking for help after a few days of struggling with this.
Phone Info:
For Fastboot info (I can't post outside links yet)...
imgur/dgOIaG6
For hboot info... (I can't post outside links yet)
imgur/7z0Bi6Z
Ideally I'd like to get stock sense back on the phone, or Google Play Edition.
Here are a few instances of it bombing during commands.
D:\Development\AndroidStudio\sdk\platform-tools>fastboot flash recovery twrp.img
sending 'recovery' (9434 KB)...
OKAY [ 1.168s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.575s
D:\Development\AndroidStudio\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[nothing]
All of the RUU's(I tried all of the Cingular ones) just say they're "Sending" and never get to a progress bar. They just leave my phone with an HTC logo and nothing else.
Console Output from HTC One Toolkit
adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adb shell /data/local/tmp/./revone -s 0 -u
error: device not found
adb shell /data/local/tmp/./revone -s 0 -u
error: device not found
adb push "D:\Development\AndroidStudio\sdk\platform-tools\TWRP.img" "File Destination...Use \ NOT / or // !"
At this point adb doesn't really appear to be working at all, and fastboot is the only response I'll get.
I'm down to actively work on this issue and follow any troubleshooting steps you guys throw at me.
Thanks in advance.
Click to expand...
Click to collapse
your images arnt working, is your bootloader unlocked ?
adb commands wont work in the bootloader therefore type fastboot devices and see if you get a result, if so type: fastboot getvar all and post the result here, it will help us a lot, be sure to remove your imei and serial number from the output before posting.
if your typing adb devices inside recovery or a booted rom, then you have a driver issue, check device manager and also FAQ 2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Seanie280672 said:
your images arnt working, is your bootloader unlocked ?
adb commands wont work in the bootloader therefore type fastboot devices and see if you get a result, if so type: fastboot getvar all and post the result here, it will help us a lot, be sure to remove your imei and serial number from the output before posting.
if your typing adb devices inside recovery or a booted rom, then you have a driver issue, check device manager and also FAQ 2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Click to expand...
Click to collapse
you're correct, bootloader is relocked, here are the images:
{
"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"
}
@nkk71 thanks, how did you get those images up, I couldnt get them to show.
@Phaymous you need too unlock your bootloader to flash recovery, that's why its failing.
but before you do that, here's the RUU that you need to use, however, if you have a driver problem you will have to sort that out first, do not use the toolkits, most of the time they are out of date, once done, put your phone into fastboot USB mode and run the RUU.
http://www.htc1guru.com/dld/ruu_m7_...20_10-40-1150-04_release_326691_signed_2-exe/
you can try this for drivers and a better version of adb and fastboot: http://forum.xda-developers.com/showthread.php?t=2588979
Seanie280672 said:
@nkk71 thanks, how did you get those images up, I couldnt get them to show.
Click to expand...
Click to collapse
i just added the .com, since he's new here, he can't post links yet so imgur/7z0Bi6Z -> http://imgur.com/7z0Bi6Z
OP, Seanie280672 will guide you through this, remember to thank him :good:
PS: don't bother with revone, you have an ATT patched hboot, you can either use rumrunner, firewater, sunshine, or the att downgrade method
Seanie280672 said:
@Phaymous you need too unlock your bootloader to flash recovery, that's why its failing.
but before you do that, here's the RUU that you need to use, however, if you have a driver problem you will have to sort that out first, do not use the toolkits, most of the time they are out of date, once done, put your phone into fastboot USB mode and run the RUU.
you can try this for drivers and a better version of adb and fastboot: http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Seanie,
I unlocked the Bootloader and downloaded the RUU. However, it just fails with a 155 error:
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
Click to expand...
Click to collapse
I'm trying it again, but all I have is the "HTC" Logo screen on my phone while it's in progress, and on my PC it simply shows that it's "Sending..." indefinitely.
How can I confirm that I am not having driver issues in this mode? This is my driver setup currently: imgur/DqdOr3X (add the http and .com)
Again, fastboot works, but adb devices does not display the device information.
C:\Users\Justin\adb>adb devices
List of devices attached
C:\Users\Justin\adb>fastboot devices
HT38DW903440 fastboot
I've tried to follow the guide that you have listed and I downloaded the 'better version of adb and fastboot', it seems that it is still unsuccessful in running adb commands. While in the bootloader I should be in fastboot selection on phone while trying to run these adb commands correct? The .zip image guide of drivers doesn't exactly play out the same on my PC. I also tried to look for uninstalling the Google USB Driver and re-installing but couldn't find anywhere to uninstall it (it's certainly not in Control Panel), Android Studio/SDK Manager shows that I have the latest version of it installed, however. As for the picture guide that lists him selecting the ADB Driver, I don't have that driver / cannot select it, and it's not anywhere that I can see in his packages so I'm confused by that guide.
Seanie280672 said:
adb commands wont work in the bootloader therefore type fastboot devices and see if you get a result, if so type: fastboot getvar all and post the result here, it will help us a lot, be sure to remove your imei and serial number from the output before posting.
if your typing adb devices inside recovery or a booted rom, then you have a driver issue, check device manager and also FAQ 2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Click to expand...
Click to collapse
Now sure how to proceed, RUU's still failing, not sure if ADB Devices are supposed to work while in fastboot on phone.
Thoughts on how to proceed?
Thank you again.
Phaymous said:
Seanie,
I unlocked the Bootloader and downloaded the RUU. However, it just fails with a 155 error:
I'm trying it again, but all I have is the "HTC" Logo screen on my phone while it's in progress, and on my PC it simply shows that it's "Sending..." indefinitely.
How can I confirm that I am not having driver issues in this mode? This is my driver setup currently: imgur/DqdOr3X (add the http and .com)
Again, fastboot works, but adb devices does not display the device information.
C:\Users\Justin\adb>adb devices
List of devices attached
C:\Users\Justin\adb>fastboot devices
HT38DW903440 fastboot
I've tried to follow the guide that you have listed and I downloaded the 'better version of adb and fastboot', it seems that it is still unsuccessful in running adb commands. While in the bootloader I should be in fastboot selection on phone while trying to run these adb commands correct? The .zip image guide of drivers doesn't exactly play out the same on my PC. I also tried to look for uninstalling the Google USB Driver and re-installing but couldn't find anywhere to uninstall it (it's certainly not in Control Panel), Android Studio/SDK Manager shows that I have the latest version of it installed, however. As for the picture guide that lists him selecting the ADB Driver, I don't have that driver / cannot select it, and it's not anywhere that I can see in his packages so I'm confused by that guide.
Now sure how to proceed, RUU's still failing, not sure if ADB Devices are supposed to work while in fastboot on phone.
Thoughts on how to proceed?
Thank you again.
Click to expand...
Click to collapse
you need to have your phone in fastboot USB mode whilst running the ruu, not on the white screen with the green HTC logo
if your having trouble getting to this screen, then hold down the power button and volume down together whilst the lights on the bottom flash 10 to 15 times, when they stop flashing, release the power button, but continue to hold the volume down, it should take you to the bootloader, select fastboot in the list if its not already there and plug into your PC, it should now say fastboot USB on the screen.
your drivers look fine, it says MyHTC, that's fine.
bootloader needs to be locked / relocked for the RUU, or unlocked to flash a custom recovery, according to your output in your picture, that's your RUU.
adb commands will not work in the bootloader full stop, only fastboot commands, adb is only for when in recovery or booted rom.
---------- Post added at 09:31 PM ---------- Previous post was at 09:25 PM ----------
this is your version main: 1.26.502.15 basically the firmware version on your output, and that's the most needed and important number
and this is the RUU: RUU M7 UL JB 50 Cingular US 1.26.502.15 Radio 4A.17.3250.20 10.40.1150.04 Release 326691 Signed 2
it should work, check the MD5 of the RUU you downloaded to make sure its not corrupt, and also that the file size matches the size on the site you downloaded it from, if your not sure how to check MD5, refer to here: http://forum.xda-developers.com/showthread.php?t=1135620
Okay so it sounds like ADB is nothing I should be concerned about, nor my drivers.
Sorry for the confusion about my fastboot usb screen, I'm aware of how to get there, I was referring to while applying the RUU it just sits at a 'frozen' HTC logo page while it's attempting to deploy the RUU. I attempt the deploy from the fastboot USB screen.
Do I need to re-lock my bootloader? I thought I had to *unlock* my bootloader after the original post.
Now my phone shows:
***TAMPERED***
***UNLOCKED***
From Fastboot USB mode, I should be attempting to apply the RUU at this point, correct?
Thanks
Phaymous said:
Okay so it sounds like ADB is nothing I should be concerned about, nor my drivers.
Sorry for the confusion about my fastboot usb screen, I'm aware of how to get there, I was referring to while applying the RUU it just sits at a 'frozen' HTC logo page while it's attempting to deploy the RUU. I attempt the deploy from the fastboot USB screen.
Do I need to re-lock my bootloader? I thought I had to *unlock* my bootloader after the original post.
Now my phone shows:
***TAMPERED***
***UNLOCKED***
From Fastboot USB mode, I should be attempting to apply the RUU at this point, correct?
Thanks
Click to expand...
Click to collapse
for RUU flashes it needs to be Locked or Relocked
For custom recovery flashes it needs to be unlocked.
sorry about the confusion
How can I proceed to re-lock for RUU? Because originally I thought you guys had me unlock my bootloader?
Phaymous said:
How can I proceed to re-lock for RUU? Because originally I thought you guys had me unlock my bootloader?
Click to expand...
Click to collapse
open a command window in the same folder as your adb and fastboot on your computer, to do that hold control & shift & right mouse click in any white area of that window and select open command window here
plug your phone into the computer and make sure it says fastboot usb on the screen
then type: fastboot oem lock
then type fastboot reboot-bootloader
done.
I said in my 2nd post you need to unlock the bootloader to flash a custom recovery, but before you do that..............
Success! Thank you.
Phaymous said:
Success! Thank you.
Click to expand...
Click to collapse
your welcome, glad its sorted. :good:
Phaymous said:
How can I proceed to re-lock for RUU? Because originally I thought you guys had me unlock my bootloader?
Click to expand...
Click to collapse
To use official RUU relock the bootloader
put yur mobile into fastboot mode
open CMD command
Enter this command fastboot oem relock
official ruu http://www.htc1guru.com/downloads/ruu-file-downloads/
Seanie280672 said:
and this is the RUU: RUU M7 UL JB 50 Cingular US 1.26.502.15 Radio 4A.17.3250.20 10.40.1150.04 Release 326691 Signed 2
Click to expand...
Click to collapse
One last question for you Seanie (thanks again).
Software information shows Android Version 4.1.2, HTC Sense version 5.0, Software Number 1.26.502.15, HTC SDK API level 5.12.
Is there any way to force Google/HTC/AT&T to serve me up the latest version of Android OS? Will it receive 4.4 in time? I believe HTC One M7 came stock with KitKat iirc.
Thanks for your help.

[Q] TWRP 2.5.0.0 Unresponsive

Hello,
I while ago I decided to root my HTC to get some extra stuff. I used a guide on youtube that seemed to be reasonably well made and followed everystep of the process. But before I could root it I had to unlock the bootloader and install TWRP recovery. I got the latest version and proceeded to the next step, where I encountered my problem. After flashing the recovery everything seemed to be well except that my phone wasn't actually rooted. I decided to redo some of the last steps. This is where things get a bit tricky. I have done this quite a while ago (maybe 3-4 months) and don't exactly remember the steps that I repeated but I think I've also flashed TWRP a second time, as well as some other steps. And when it came to the part where I needed to use the recovery I found out that the recovery doesn't work. I can't press anything on the screen, I can however press the lock button and lock the device but when the *slide to unlock* appears it stops working again. I was running out of time and decided to leave it for another time but time has passed and I never really got the time to tinker with it any more since university started and I'm more busy then ever. This has left me with no ability to root or even update my phone.
This brings me to today, when I restored my phone completely forgetting what has happened. It got back to Android 4.1 and I can't do anything about it.
I hope to sort this out and finally root the phone. But even getting rid of TWRP to the original recovery so I could just update my phone would be very helpfull.
Thank you very much.
aleks945 said:
Hello,
I while ago I decided to root my HTC to get some extra stuff. I used a guide on youtube that seemed to be reasonably well made and followed everystep of the process. But before I could root it I had to unlock the bootloader and install TWRP recovery. I got the latest version and proceeded to the next step, where I encountered my problem. After flashing the recovery everything seemed to be well except that my phone wasn't actually rooted. I decided to redo some of the last steps. This is where things get a bit tricky. I have done this quite a while ago (maybe 3-4 months) and don't exactly remember the steps that I repeated but I think I've also flashed TWRP a second time, as well as some other steps. And when it came to the part where I needed to use the recovery I found out that the recovery doesn't work. I can't press anything on the screen, I can however press the lock button and lock the device but when the *slide to unlock* appears it stops working again. I was running out of time and decided to leave it for another time but time has passed and I never really got the time to tinker with it any more since university started and I'm more busy then ever. This has left me with no ability to root or even update my phone.
This brings me to today, when I restored my phone completely forgetting what has happened. It got back to Android 4.1 and I can't do anything about it.
I hope to sort this out and finally root the phone. But even getting rid of TWRP to the original recovery so I could just update my phone would be very helpfull.
Thank you very much.
Click to expand...
Click to collapse
The background information is helpful but you have given us nothing to go on.
Post a fastboot getvar all except remove the imei and serialno?
What are you trying to accomplish? Return to Stock? S-OFF?
majmoz said:
The background information is helpful but you have given us nothing to go on.
Post a fastboot getvar all except remove the imei and serialno?
What are you trying to accomplish? Return to Stock? S-OFF?
Click to expand...
Click to collapse
Tell me what background information do you need and I'll get everything.
The goal is to get a working recovery, which ever one it would be I don't really care. I just want to be able to update the firmware.
reboot into the bootloader. flash the latest twrp for your device using fastboot flash recovery recoverynamehere.zip
profit
jdgreat4 said:
reboot into the bootloader. flash the latest twrp for your device using fastboot flash recovery recoverynamehere.zip
profit
Click to expand...
Click to collapse
If you could give me a more detailed guide I would toatally do that, because I'm pretty noobish when it comes to this kind of stuff.
aleks945 said:
Tell me what background information do you need and I'll get everything.
The goal is to get a working recovery, which ever one it would be I don't really care. I just want to be able to update the firmware.
Click to expand...
Click to collapse
like he said before, post the output of "fastboot getvar all" except your IMEI and SERIALNO
---------- Post added at 11:06 AM ---------- Previous post was at 11:05 AM ----------
aleks945 said:
If you could give me a more detailed guide I would toatally do that, because I'm pretty noobish when it comes to this kind of stuff.
Click to expand...
Click to collapse
do you have adb and fastboot on your computer?
Do you have HTC drivers installed?
alray said:
like he said before, post the output of "fastboot getvar all" except your IMEI and SERIALNO
---------- Post added at 11:06 AM ---------- Previous post was at 11:05 AM ----------
do you have adb and fastboot on your computer?
Do you have HTC drivers installed?
Click to expand...
Click to collapse
I don't know what adb is, sorry. And no I don't, I had to do everything on my friend's laptop because it didn't seem to work on my machine (W8.1 compared to his W7).
Edit. But I do have acces to it pretty much all the time.
aleks945 said:
I don't know what adb is, sorry. And no I don't, I had to do everything on my friend's laptop because it didn't seem to work on my machine (W8.1 compared to his W7).
Click to expand...
Click to collapse
yes better to use windows 7
go ahead and download adb and fastboot from here: http://forum.xda-developers.com/showthread.php?t=2317790
download and install HTC sync from here: http://www.htc.com/us/support/software/htc-sync-manager.aspx
Once installed, uninstall HTC sync but keep the drivers installed
post back when done
alray said:
yes better to use windows 7
go ahead and download adb and fastboot from here: http://forum.xda-developers.com/showthread.php?t=2317790
download and install HTC sync from here: http://www.htc.com/us/support/software/htc-sync-manager.aspx
Once installed, uninstall HTC sync but keep the drivers installed
post back when done
Click to expand...
Click to collapse
The downloads are complete, just waiting on the instalation. The computer is quite old and slow unfortunatelly.
Thank you again
EDIT. Everything is done.
aleks945 said:
The downloads are complete, just waiting on the instalation. The computer is quite old and slow unfortunatelly.
Thank you again
EDIT. Everything is done.
Click to expand...
Click to collapse
ok so connect your phone with he usb cable to the computer, reboot it in bootloader mode (hold power and vol -). in bootloader select "fastboot"
then lauch the adb command prompt and type "fastboot getvar all". post the output here but edit out the imei and serialno before.
alray said:
ok so connect your phone with he usb cable to the computer, reboot it in bootloader mode (hold power and vol -). in bootloader select "fastboot"
then lauch the adb command prompt and type "fastboot getvar all". post the output here but edit out the imei and serialno before.
Click to expand...
Click to collapse
Here it is.
{
"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"
}
Link since image seems to be really tiny.
http://i.imgur.com/9cZZRA9.jpg
aleks945 said:
Here it is.
Link since image seems to be really tiny.
http://i.imgur.com/9cZZRA9.jpg
Click to expand...
Click to collapse
you can flash twrp 2.6.3.3
download the file and save it in the same folder where you have installed minimal adb and fastboot
then open the command prompt and with the phone in bootloader/fastboot mode enter these commands:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
What do you want to achieve then? Custom rooted rom? stock rooted rom (latest version)? or you simply what to root the rom you currently have?
alray said:
you can flash twrp 2.6.3.3
download the file and save it in the same folder where you have installed minimal adb and fastboot
then open the command prompt and with the phone in bootloader/fastboot mode enter these commands:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
What do you want to achieve then? Custom rooted rom? stock rooted rom (latest version)? or you simply what to root the rom you currently have?
Click to expand...
Click to collapse
Latest stock rooted ram would be the final goal.
aleks945 said:
Latest stock rooted ram would be the final goal.
Click to expand...
Click to collapse
you can flash this rom: http://www.androidrevolution.org/downloader/download.php?file=One_6.09.401.5_odexed.zip
its the stock rom for 6.09.401.5
alray said:
you can flash this rom: http://www.androidrevolution.org/downloader/download.php?file=One_6.09.401.5_odexed.zip
its the stock rom for 6.09.401.5
Click to expand...
Click to collapse
Doesn't my phone have to be rooted to be able to instal another rom?
aleks945 said:
Doesn't my phone have to be rooted to be able to instal another rom?
Click to expand...
Click to collapse
no just flash the rom from twrp recovery then you can root it if you want.

Phone keeps rebooting after ROM flash.

Hey. I got a problem with my beloved M7. Few days ago I gave a chance to CM12, but I got bored of it and tried to flash InsertCoin 4.0.5. Everything went well but now my phone boots up and locks the screen. If I unlock the screen, a green HTC logo on white background appears. After few seconds of showing the logo the phone reboots and locks the screen again. I can freely access the TWRP, but I have no backup and I lost CM12 installing files. Please can someone help me bring my lovely phone back to life?
P.S sorry for my English
Taurenom said:
Hey. I got a problem with my beloved M7. Few days ago I gave a chance to CM12, but I got bored of it and tried to flash InsertCoin 4.0.5. Everything went well but now my phone boots up and locks the screen. If I unlock the screen, a green HTC logo on white background appears. After few seconds of showing the logo the phone reboots and locks the screen again. I can freely access the TWRP, but I have no backup and I lost CM12 installing files. Please can someone help me bring my lovely phone back to life?
P.S sorry for my English
Click to expand...
Click to collapse
Just follow this guide, it should help:
Originally posted by @alrayHTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer,
either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"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"
}
You need TWRP recovery on your device.
We still recommend to use version 2.6.3.3 for all roms
except if another version is specified in the rom OP.
Use 2.7.1.1+ for roms that require "block:by-name" support (CM11)
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone any ways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didn't install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
Here is a list of the HTC M7 roms. Some other roms can be found here.
Connect your phone to computer using usb cable
(if not using the official HTC USB calble, make sure
you are using a USB data cable and not only a charging
cable. Data cables have 4 contacts: 5V, GND, DATA+, DATA-.
Charging cable only have 5V and GND contact and will not work)
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes (5-15) and there is no progress bar, the command prompt will be unresponsive for that duration. When the command prompt is responsive again and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Taurenom said:
Hey. I got a problem with my beloved M7. Few days ago I gave a chance to CM12, but I got bored of it and tried to flash InsertCoin 4.0.5. Everything went well but now my phone boots up and locks the screen. If I unlock the screen, a green HTC logo on white background appears. After few seconds of showing the logo the phone reboots and locks the screen again. I can freely access the TWRP, but I have no backup and I lost CM12 installing files. Please can someone help me bring my lovely phone back to life?
P.S sorry for my English
Click to expand...
Click to collapse
Sounds like another one with Unknown IMEI and baseband
Follow @alray guide as posted by @majmoz if the problem persists try flashing CM11 then go to Settings>About>Phone Identity and check your IMEI is displayed correctly there. Also check baseband in Settings>About>Software Information>More.
Danny201281 said:
Sounds like another one with Unknown IMEI and baseband
Follow @alray guide as posted by @majmoz if the problem persists try flashing CM11 then go to Settings>About>Phone Identity and check your IMEI is displayed correctly there. Also check baseband in Settings>About>Software Information>More.
Click to expand...
Click to collapse
I managed to somehow flash CM12 back. ^^ My baseband is 4A.17.3250.14_10.39.1150.04L. And here comes another question. How can I get back to 4.4.3 with Sense ROMs without reboots which happened earlier? I have seen that I have to flash certain firmware, but I am not sure which one.
P.S @majmoz Thanks for help, you saved my One!
Taurenom said:
I managed to somehow flash CM12 back. ^^ My baseband is 4A.17.3250.14_10.39.1150.04L and IMEI 3578640528003796. And here comes another question. How can I get back to 4.4.3 with Sense ROMs without reboots which happened earlier? I have seen that I have to flash certain firmware, but I am not sure which one.
P.S @majmoz Thanks for help, you saved my One!
Click to expand...
Click to collapse
First you should edit you post and remove your imei. You don't want to make that public
If you could post the output of
Code:
fastboot getvar all
it would be helpful you should also remove your imei and serial number before posting :good:
but the fact the imei and baseband don't display Unknown in settings is good
Danny201281 said:
First you should edit you post and remove your imei. You don't want to make that public
Click to expand...
Click to collapse
Got it done As I wrote earlier, I would like to get back to 4.4.3 Sense. I found a guide for m8
HTML:
http://forum.xda-developers.com/showthread.php?t=2733523
., which I guess would work on m7 too, but I'm not sure which firmware is required to make 4.4.3 properly work.
Taurenom said:
Got it done As I wrote earlier, I would like to get back to 4.4.3 Sense. I found a guide for m8
HTML:
http://forum.xda-developers.com/showthread.php?t=2733523
., which I guess would work on m7 too, but I'm not sure which firmware is required to make 4.4.3 properly work.
Click to expand...
Click to collapse
It depends on which variant of the HTC One you have, see the edit in my post above
Well, I struggled almost 2 hours in order to get "getvar all" logs and nothing happened. When I enter ADB command - "adb devices" it lists my phone below but as an offline device. I tried over and over using guides linked by majmoz and this one -
HTML:
https://www.youtube.com/watch?v=rfC9_HXaI_U
. Is there any other possible way to get logs excepting via ADB/fastboot on PC?
Taurenom said:
Well, I struggled almost 2 hours in order to get "getvar all" logs and nothing happened. When I enter ADB command - "adb devices" it lists my phone below but as an offline device. I tried over and over using guides linked by majmoz and this one -
HTML:
https://www.youtube.com/watch?v=rfC9_HXaI_U
. Is there any other possible way to get logs excepting via ADB/fastboot on PC?
Click to expand...
Click to collapse
To get the getvar info your Device should be in the bootloader in fastboot usb mode.
Then send the fastboot getvar all command.
@Danny201281 Yeah, I tried to do this in fastboot mode. Windows pop up says that there is unrecognized device connected, what shouldn't have even happened because I have the latest HTC drivers(2.0.7.27) from HTC Sync.
Taurenom said:
Yeah, I tried to do this in fastboot mode. Windows pop up says that there is unrecognized device connected, what shouldn't even happened because I have the latest HTC drivers(2.0.7.27) from HTC Sync.
Click to expand...
Click to collapse
See Q(2 in this faq post to fix the drivers http://forum.xda-developers.com/showthread.php?p=52135024
It's common for Windows drivers to fail like this. You can check in device manager you phone should be listed a "MY HTC"
Other than that try connecting to a different usb port. USB2.0 ports are best. :good:
Danny201281 said:
See Q(2 in this faq post to fix the drivers http://forum.xda-developers.com/showthread.php?p=52135024
It's common for Windows drivers to fail like this. You can check in device manager you phone should be listed a "MY HTC"
Other than that try connecting to a different usb port. USB2.0 ports are best. :good:
Click to expand...
Click to collapse
My hboot version is 1.54.0000; device manager lists the phone as "MY HTC" with exclamation mark in a triangle, and yes I'm using USB 2.0 port.
P.S won't this command work if I'm S-ON?
Taurenom said:
My hboot version is 1.54.0000; device manager lists the phone as "MY HTC" with exclamation mark in a triangle, and yes I'm using USB 2.0 port.
P.S won't this command work if I'm S-ON?
Click to expand...
Click to collapse
We need to know your CID, MID and Version Main which is all in the getvar. In any case you will need fastboot working to flash your firmware.
If your Device is s-off that's good you don't want to go back to s-on for any reason. In any case going back to s-on also requires fastboot. Try this http://forum.xda-developers.com/showthread.php?p=54272479
This is my guide for setting up Linux on a bootable usb pen drive. It will eliminate any driver issues
Danny201281 said:
We need to know your CID, MID and Version Main which is all in the getvar. In any case you will need fastboot working to flash your firmware.
If your Device is s-off that's good you don't want to go back to s-on for any reason. In any case going back to s-on also requires fastboot. Try this http://forum.xda-developers.com/showthread.php?p=54272479
This is my guide for setting up Linux on a bootable usb pen drive. It will eliminate any driver issues
Click to expand...
Click to collapse
I tried to follow your guide on virtual machine because I simply don't know how to boot from pendrive on my laptop. Now Linux can't even see my One After typing "sudo adb devices" command, there is blank list of devices attached, and when I typed "sudo adb reboot bootloader" an error popped up "error: device not found".
Taurenom said:
I tried to follow your guide on virtual machine because I simply don't know how to boot from pendrive on my laptop. Now Linux can't even see my One After typing "sudo adb devices" command, there is blank list of devices attached, and when I typed "sudo adb reboot bootloader" an error popped up "error: device not found".
Click to expand...
Click to collapse
Sorry i can't help with adb/fastboot problems when running Linux as a VM. I've never used linux as a virtual machine in windows, and your knowledge of Windows it's self is probably better than mine especially Windows 8. I'm confident there is no problem with your device this is a connectivity issue most probably caused by drivers. Hopefully @majmoz or @clsA can help you get it working on windows 8.
Although booting your laptop from a usb shouldn't be that difficult. You just need to change the boot order in the bios. The bios can be accessed normally by pressing "Delete" or "F2" during the first boot screen on your laptop. Then change the boot settings so that USB is the first boot device. What make is your laptop?
Danny201281 said:
Sorry i can't help with that adb/fastboot. I've never used linux as a virtual machine in windows, and your knowledge of Windows it's self is probably better than mine especially Windows 8. I'm confident there is no problem with your device this is a connectivity issue most probably caused by drivers. Hopefully @majmoz or @clsA can help you get it working on windows 8.
Although booting your laptop from a usb shouldn't be that difficult. You just need to change the boot order in the bios. The bios can be accessed normally by pressing "Delete" or "F2" during the first boot screen on your laptop. Then change the boot settings so that USB is the first boot device. What make is your laptop?
Click to expand...
Click to collapse
It's Lenovo y50-70; bios is completly hidden from the user - that's why I can't boot it from pendrive. I will try to follow your hints asap as I get access to my PC at home
Taurenom said:
It's Lenovo y50-70; bios is completly hidden from the user - that's why I can't boot it from pendrive. I will try to follow your hints asap as I get access to my PC at home
Click to expand...
Click to collapse
Ok cool, Sorry man i'm not big on Windows. I use linux as my main OS although my pc dual boot Windows 7 but I use that mainly for gaming. If linux got a little more gamer love I wouldn't use windows at all
As far as I know Windows 8 can bit a bit finicky when it comes to android phones although I know there are plenty that use it without any problems.
Taurenom said:
It's Lenovo y50-70; bios is completly hidden from the user - that's why I can't boot it from pendrive. I will try to follow your hints asap as I get access to my PC at home
Click to expand...
Click to collapse
Danny201281 said:
Ok cool, Sorry man i'm not big on Windows. I use linux as my main OS although my pc dual boot Windows 7 but I use that mainly for gaming. If linux got a little more gamer love I wouldn't use windows at all
As far as I know Windows 8 can bit a bit finicky when it comes to android phones although I know there are plenty that use it without any problems.
Click to expand...
Click to collapse
Their is only one problem using windows 8.1 and that is hboot 1.44 and that is still fixable with a little searching
My windows 8.1 PC only uses 3 files you can download and install them from here > http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337
And the HTC Driver from here >> https://mega.co.nz/#!9cpz0Soa!rZH0H5djENbFN2xkS9S7yUlXzX_vcC5yOHhmUR55kUM
I just did a brand new Blue HTC One on hboot 1.44 Last week with this setup ... It Works !
clsA said:
Their is only one problem using windows 8.1 and that is hboot 1.44 and that is still fixable with a little searching
My windows 8.1 PC only uses 3 files you can download and install them from here > http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337
And the HTC Driver from here >> https://mega.co.nz/#!9cpz0Soa!rZH0H5djENbFN2xkS9S7yUlXzX_vcC5yOHhmUR55kUM
I just did a brand new Blue HTC One on hboot 1.44 Last week with this setup ... It Works !
Click to expand...
Click to collapse
Thanks @clsA that's exactly why I tagged you in my post. I know from previous posts that you use Windows 8 without problems :good: I don't know where to start with Windows 8. Never used it and doubt I ever will. If it was in front of me I dare say I could figure it out. But over the forum I'm just poking around in the dark when it comes to windows 8

Help - cannot enter system after clean installation of Android Revolution

So aftter downloading the Android Revolution and wiping the data, I tried installing the ROM.
However it keeps booting into recovery mode. I have no idea how to fix this.
The phone tries to boot up normally, but fails to do so. It restarts and boots into recovery. (TWRP 2.5.0.0)
I have tried deleting installing a few times. Where I cleared both the cache and dalvik cache.
Still nothing. Is there any way to get another ROM onto my phone now? My computer doesn't recognize the device anymore.
After the installation it says complete, but shows an error: "set_metadata_recursive: some changes failed"
after this it says: "installation was succesful!" and tells me to do 1 full system boot before flashing mods.:crying::crying:
"Update, I found out I used a rom designed for M8 and not M7.
If anyone could help me getting ADB to work and a rom I can flash and pretty much a tutorial. I would be super grateful
So I found a m7 rom. But when trying to push it using ADB it takes a really long time and ends in protocol error.
Aisu64 said:
boots into recovery. (TWRP 2.5.0.0)
Click to expand...
Click to collapse
Here is one problem. You won't be able to flash any recent roms using twrp 2.5.0.0. Update your recovery first: https://dl.twrp.me/m7/
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
make sure you have the latest adb version (1.0.32) using the command:
Code:
adb version
If not update your android sdk-tools: https://developer.android.com/sdk/index.html#Other
Also make sure you have the latest htc drivers installed on your computer
With the latest twrp and drivers you'll be able to transfer a rom to your phone using MTP protocol when booted in twrp main menu (simply drag and drop your file from your computer to your phone storage).
If using newer roms (android 5.0.2) your phone must have a 7.xx.xxx.x firmware installed on it. Older firmware running new roms cam have issues. To determine your firmware version, use the command "fastboot getvar version-main" or "fastboot getvar all"
Finally pushed the files to the phone.
But after installing my phone still keeps entering recovery mode (twrp).
Aisu64 said:
Finally pushed the files to the phone.
But after installing my phone still keeps entering recovery mode (twrp).
Click to expand...
Click to collapse
Did you updated your twrp recovery?
alray said:
Here is one problem. You won't be able to flash any recent roms using twrp 2.5.0.0. Update your recovery first: https://dl.twrp.me/m7/
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
Can you help me a little bit? I can't see the device connected unless I'm in recovery. Can I flash a recovery in recovery?
Click to expand...
Click to collapse
Aisu64 said:
Here is one problem. You won't be able to flash any recent roms using twrp 2.5.0.0. Update your recovery first: https://dl.twrp.me/m7/
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
Can you help me a little bit? I can't see the device connected unless I'm in recovery. Can I flash a recovery in recovery?
Click to expand...
Click to collapse
afaik, not with 2.5.0.0. If you can't see the device when in bootloader / fastboot usb mode then you have drivers issues. make sur eyou have latest htc drivers installed. If needed download htc sync. This will install htc sync and the latest drivers. Then uninstall htc sync (but don't uninstall the drivers). You don't want HTC sync on your computer because it will interfere with fastboot / adb connectivity.
alray said:
Aisu64 said:
afaik, not with 2.5.0.0. If you can't see the device when in bootloader / fastboot usb mode then you have drivers issues. make sur eyou have latest htc drivers installed. If needed download htc sync. This will install htc sync and the latest drivers. Then uninstall htc sync (but don't uninstall the drivers). You don't want HTC sync on your computer because it will interfere with fastboot / adb connectivity.
Click to expand...
Click to collapse
I have tried deleting, restarting and reinstalling the drivers. But my phone wont show up under devices anymore. I really appreciate your help, but I really have to go to bed as I have a long day at work tomorrow.
Click to expand...
Click to collapse
Aisu64 said:
I have tried deleting, restarting and reinstalling the drivers. But my phone wont show up under devices anymore. I really appreciate your help, but I really have to go to bed as I have a long day at work tomorrow.
Click to expand...
Click to collapse
No problem, go take some rest and I'll help you later :good:
alray said:
No problem, go take some rest and I'll help you later :good:
Click to expand...
Click to collapse
So I've been playing around installing and reinstalling and deleting and restarting my computer.
My computer can see the device only in recovery. Everytime I'm in the bootloader/fastboot menu it dissapears from the device list in ADB.
Is it possible to flash the phone while in recovery?
Aisu64 said:
So I've been playing around installing and reinstalling and deleting and restarting my computer.
My computer can see the device only in recovery. Everytime I'm in the bootloader/fastboot menu it dissapears from the device list in ADB.
Click to expand...
Click to collapse
you won't get any adb connectivity when booted in bootloader / fastboot usb mode. ADB only works from a booted rom with usb debug turned on or from a custom recovery. In bootloader you must use fastboot commands. To see if your phone is detected by your computer when in bootlaoder / fastboot usb mode, use the command "fastboot devices"
If your phone isn't listed with this command, please post a screenshot of your Windows devices manager with the phone connected and booted in bootloader / fastboot usb mode. Also need to know what is your bootloader version? 1.44/1.54/1.55/1.56/1.57 or 1.61 ? You can see this info when booted in bootloader mode
Is it possible to flash the phone while in recovery?
Click to expand...
Click to collapse
You might want to read what I said again:
You won't be able to flash any recent rom using twrp 2.5.0.0
You can't flash a new recovery using twrp 2.5.0.0, you must use fastboot
:good:
{
"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"
}
It says Hboot - 1.44
atm I can't even get it to show up in recovery.
Screenshot: http://imgur.com/So88OLm
Aisu64 said:
It says Hboot - 1.44
atm I can't even get it to show up in recovery.
Screenshot: http://imgur.com/So88OLm
Click to expand...
Click to collapse
ok hboot 1.44 is the oldest one and have compatibility issues with windows 8 and 10. Do you have access to a windows 7 computer?
alray said:
ok hboot 1.44 is the oldest one and have compatibility issues with windows 8 and 10. Do you have access to a windows 7 computer?
Click to expand...
Click to collapse
Yes I do. A super ancient one.
Also this is how it looks like when I'm in recovery: http://imgur.com/SxW9p66
Aisu64 said:
Yes I do. A super ancient one.
Click to expand...
Click to collapse
Please setup everything on this computer (HTC drivers + Android sdk tools (adb and fastboot), this will be much easier to work with Win7 because of your 1.44 hboot. Later, once your hboot will be updated, you'll be able to use your Win10 computer without any problem but for now better to work with Win7. Once you got everything installed on your win7 computer, boot the phone in bootloader / fastboot usb mode and use the command "fastboot devices" to see if your phone is detected. If yes then use "fastboot getvar all" command. take a screenshot of this command output and post it here (censor the IMEI number and the SERIALNO number before uploading your picture). Don't update the recovery for now.
Also this is how it looks like when I'm in recovery: http://imgur.com/SxW9p66
Click to expand...
Click to collapse
Everything is fine here.
alray said:
Please setup everything on this computer (HTC drivers + Android sdk tools (adb and fastboot), this will be much easier to work with Win7 because of your 1.44 hboot. Later, once your hboot will be updated, you'll be able to use your Win10 computer without any problem but for now better to work with Win7. Once you got everything installed on your win7 computer, boot the phone in bootloader / fastboot usb mode and use the command "fastboot devices" to see if your phone is detected. If yes then use "fastboot getvar all" command. take a screenshot of this command output and post it here (censor the IMEI number and the SERIALNO number before uploading your picture). Don't update the recovery for now.
Everything is fine here.
Click to expand...
Click to collapse
You might aswell type the next part. Cuz this will be taking a few hours ^^
Aisu64 said:
You might aswell type the next part. Cuz this will be taking a few hours ^^
Click to expand...
Click to collapse
well I need to see your "fastboot getvar all" before i can tell anything more.
alray said:
well I need to see your "fastboot getvar all" before i can tell anything more.
Click to expand...
Click to collapse
My windows 7 computer keeps asking for a "android 1.0" driver, even though I installed the HTC one m7 driver package downloaded from HTC. I also tried installing HTC Sync, but it doesn't seem to help. Also it only shows "Android 1.0" while in fastboot so I assume this is the fastboot driver?
one more thing. I can't get it to show it's connected to ADB while in recovery.
Aisu64 said:
My windows 7 computer keeps asking for a "android 1.0" driver, even though I installed the HTC one m7 driver package downloaded from HTC. I also tried installing HTC Sync, but it doesn't seem to help. Also it only shows "Android 1.0" while in fastboot so I assume this is the fastboot driver?
one more thing. I can't get it to show it's connected to ADB while in recovery.
Click to expand...
Click to collapse
Strange, it should be easy to make it work on win7. You might want to try this drivers: http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339
alray said:
Strange, it should be easy to make it work on win7. You might want to try this drivers: http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339
Click to expand...
Click to collapse
I borrowed a friends win7 computer and fastboot works! After installing the drivers you linked me to. Here is a screenshot! http://imgur.com/CN0uLu6

Categories

Resources