I am trying to return my HTC one to stock using this guide
http://forum.xda-developers.com/showthread.php?t=2541082
I have rooted my phone on a previous occasion a few months ago so I could install some root required apps. Apps installed and everything was fine.
Rumrunner runs, then says I do not have root access.
Weaksauce tells me 'already rooted'.
In hboot I have these for the top two lines
***tampered***
***unlocked***
I have s-on and need to get s-off before I can continue, can anyone help?
chris9486 said:
I am trying to return my HTC one to stock using this guide
http://forum.xda-developers.com/showthread.php?t=2541082
I have rooted my phone on a previous occasion a few months ago so I could install some root required apps. Apps installed and everything was fine.
Rumrunner runs, then says I do not have root access.
Weaksauce tells me 'already rooted'.
In hboot I have these for the top two lines
***tampered***
***unlocked***
I have s-on and need to get s-off before I can continue, can anyone help?
Click to expand...
Click to collapse
start by posting a "fastboot getvar all" (excluding IMEI and s/n), and what ROM are you running?
I am running stock ROM I think. It was a while back when I rooted it and can't remember installing a custom rom. I like the original HTC rom, it is fast and I never get any lag. I just wanted to add the tap to wake features that had been ported from the m8, I just needed a rooted phone.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3884mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Pretty sure rumrunner won't work on 1.57. Either Firewater or sunshine
chris9486 said:
I am running stock ROM I think. It was a while back when I rooted it and can't remember installing a custom rom. I like the original HTC rom, it is fast and I never get any lag. I just wanted to add the tap to wake features that had been ported from the m8, I just needed a rooted phone.
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-main: 5.11.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
Click to expand...
Click to collapse
@nateboi81 is right, your only options are:
a) sunshine (costs $25) on stock rom
or
b) firewater (free) on rooted ROM (and possibly bulletproof kernel)
if firewater gives you "whelp this sucks, etc" error then only sunshine will work
chris9486 said:
I am trying to return my HTC one to stock using this guide
http://forum.xda-developers.com/showthread.php?t=2541082
I have rooted my phone on a previous occasion a few months ago so I could install some root required apps. Apps installed and everything was fine.
Rumrunner runs, then says I do not have root access.
Weaksauce tells me 'already rooted'.
In hboot I have these for the top two lines
***tampered***
***unlocked***
I have s-on and need to get s-off before I can continue, can anyone help?
Click to expand...
Click to collapse
I s-off my rooted htc one hboot 1.57 using firewater. Must be on custom rom I think. Download link in case you need it, other links didn't work for me;
Firewater
- adb reboot <-- Important
- adb wait-for-device push firewater /data/local/tmp <--- When the phone restarts enter this
- adb shell
- su
- chmod 755 /data/local/tmp/firewater
- /data/local/tmp/firewater
Wait for prompt and type Yes, must be capital 'Y'
Thanks for the replies. I have just spent the best part of the last hour going through the guide I posted a link to. The links for htc1 guru do not work, keep timing out. And a lot of the stuff I don't understand which steps I need to take. The guide is great but not well structured for the less confident. I will just turn off the system updates on my phone and delete the update so it doesn't keep bugging me.
Firewater didn't work. It said I need to run it as SU or FU. I followed all the commands on the firewater s-off site.
From Firewater attempt. I am aware that $ in adb shell means it is not rooted. So I think there's just a big issue with if it is or not rooted. Like the original post, one says I am and one says I am not. So I am giving up!
C:\adb>adb devices
List of devices attached
S**************0 device
C:\adb>adb reboot
C:\adb>adb wait-for device push firewater /data/local/tmp
C:\adb>adb shell
[email protected]:/ $ su
su
1|[email protected]:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ $ /data/local/tmp/firewater
/data/local/tmp/firewater
error, run firewater as root. su or FU!!!!!!
1|[email protected]:/ $
chris9486 said:
Thanks for the replies. I have just spent the best part of the last hour going through the guide I posted a link to. The links for htc1 guru do not work, keep timing out. And a lot of the stuff I don't understand which steps I need to take. The guide is great but not well structured for the less confident.
Click to expand...
Click to collapse
Any recommendations on what should be written better?
I have mirrors of many of the files, for you (once s-off), you can use ruu.zip method using this ruu.zip: https://www.androidfilehost.com/?fid=23329332407584993
chris9486 said:
Firewater didn't work. It said I need to run it as SU or FU. I followed all the commands on the firewater s-off site.
From Firewater attempt. I am aware that $ in adb shell means it is not rooted. So I think there's just a big issue with if it is or not rooted. Like the original post, one says I am and one says I am not. So I am giving up!
C:\adb>adb devices
List of devices attached
S**************0 device
C:\adb>adb reboot
C:\adb>adb wait-for device push firewater /data/local/tmp
C:\adb>adb shell
[email protected]:/ $ su
su
1|[email protected]:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]:/ $ /data/local/tmp/firewater
/data/local/tmp/firewater
error, run firewater as root. su or FU!!!!!!
1|[email protected]:/ $
Click to expand...
Click to collapse
install a custom ROM, i've heard that ARHD 31.6 should work: http://forum.xda-developers.com/showthread.php?t=2183023
then try firewater
EDIT: or if you don't wanna waste time, just use sunshine (it costs $25, but definitely works, whereas firewater only has a limited chance)
nkk71 said:
Any recommendations on what should be written better?
I have mirrors of many of the files, for you (once s-off), you can use ruu.zip method using this ruu.zip: https://www.androidfilehost.com/?fid=23329332407584993
install a custom ROM, i've heard that ARHD 31.6 should work: http://forum.xda-developers.com/showthread.php?t=2183023
then try firewater
EDIT: or if you don't wanna waste time, just use sunshine (it costs $25, but definitely works, whereas firewater only has a limited chance)
Click to expand...
Click to collapse
Sorry, I didn't mean to offend you. The article is great like I said. Just sometimes there's some information about something else and I just couldn't work out if it applies or not. A little bit more description would help.
I thought about doing that but I am reluctant to fiddle about too much now. I'm being super cautious with all things technology wise. I lost a hard drive last week and then the backup of it two days later when I tried to put it on a new drive. Through no fault of my own and it's costing £540 for it to be recovered by a professional company. I don't want to f-up anything else because I can't afford another phone. My contract is up in Jan so I'll just stay on this till I can upgrade. My phone hasn't prompted me to upgrade ota again yet. So it's not a necessity to return to stock.
chris9486 said:
Sorry, I didn't mean to offend you. The article is great like I said. Just sometimes there's some information about something else and I just couldn't work out if it applies or not. A little bit more description would help.
Click to expand...
Click to collapse
I wasn't offended at all, just wondering what should be written differently.
chris9486 said:
I am running stock ROM I think. It was a while back when I rooted it and can't remember installing a custom rom. I like the original HTC rom, it is fast and I never get any lag. I just wanted to add the tap to wake features that had been ported from the m8, I just needed a rooted phone.
Click to expand...
Click to collapse
To get the wake gestures, you would need a custom kernel such as elementalX (possibly in conjunction with Xposed + Sense6Toolbox).
nkk71 said:
I wasn't offended at all, just wondering what should be written differently.
Click to expand...
Click to collapse
I like to think I am not stupid. But sometimes when I am using something new like adb, then I just daren't do something, since I have the possibility to wreck my phone.
This confused me. I didn't know if I had to reboot my phone or whether I needed to type reboot bootloader/fasboot usb into adb.
Reboot to bootloader/FASTBOOT USB, then:
fastboot getvar all
Then this confused me. I didn't know if I needed to do these?
Common downloads for all methods:
download CWM from here: recovery-clockwork-touch-6.0.4.5-m7ul.img 8.5 MB
..... MD5: D6DCFEA904E5A3B90ED320AC438BA5F3
rename the file to CWM.img (careful about .img.img in Windows)
this is originally from: http://forum.xda-developers.com/show....php?t=2173863
I'm using the 6.0.4.5 version because I've noticed that some versions (I've tested 6.0.3.2 and 6.0.4.6) have problems with adb commands when used in "fastboot boot CWM.img" mode.
download Guru Bootloader Reset from here: http://www.htc1guru.com/dld/guru_boo...reset_1-0-zip/ (this is the thread http://forum.xda-developers.com/show....php?t=2527194)
----> if Guru Bootloader Reset gives you a hard time (freezes), use alternate method from FAQ #8
nkk71 said:
To get the wake gestures, you would need a custom kernel such as elementalX (possibly in conjunction with Xposed + Sense6Toolbox).
Click to expand...
Click to collapse
I realised after installing xposed and sense6toolbox that I needed a custom kernel. I was lost in a world of roms, roots, custom recovery, xposed and just gave up because I couldn't find out what I needed to do re. the kernel.
I am downloading ARHD and I am ready to flash it, I will try to s-off with firewater. If it doesn't work, I will just keep ARHD on and be fine till I can upgrade to a new phone. Not sure which one yet. Torn between Z2 and M8.
nkk71 said:
Any recommendations on what should be written better?
I have mirrors of many of the files, for you (once s-off), you can use ruu.zip method using this ruu.zip: https://www.androidfilehost.com/?fid=23329332407584993
Click to expand...
Click to collapse
Can I ask, is this the correct ruu for my phone mid and cid?
nkk71 said:
Any recommendations on what should be written better?
I have mirrors of many of the files, for you (once s-off), you can use ruu.zip method using this ruu.zip: https://www.androidfilehost.com/?fid=23329332407584993
install a custom ROM, i've heard that ARHD 31.6 should work: http://forum.xda-developers.com/showthread.php?t=2183023
then try firewater
EDIT: or if you don't wanna waste time, just use sunshine (it costs $25, but definitely works, whereas firewater only has a limited chance)
Click to expand...
Click to collapse
I downloaded arhd 31.6. Flashed. Cleared cache. Now I am stuck in a bootloop, cannot get into recovery and none of my computers will recognise the phone in ADB even though they did before!
I get nothing under adb devices.
:crying:
chris9486 said:
I like to think I am not stupid. But sometimes when I am using something new like adb, then I just daren't do something, since I have the possibility to wreck my phone.
This confused me. I didn't know if I had to reboot my phone or whether I needed to type reboot bootloader/fasboot usb into adb.
Reboot to bootloader/FASTBOOT USB, then:
fastboot getvar all
Click to expand...
Click to collapse
Thanks for the feedback.
by bootloader/FASTBOOT USB, I mean this screen:
{
"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"
}
because that's where you issue fastboot commands, and the "fastboot getvar all" command is one every user should be familiar with, as it gives you the necessary information to know what your phone is.
I'll probably edit the box and make a copy/paste of the actual command prompt.
chris9486 said:
Then this confused me. I didn't know if I needed to do these?
Common downloads for all methods:
download CWM from here: recovery-clockwork-touch-6.0.4.5-m7ul.img 8.5 MB
..... MD5: D6DCFEA904E5A3B90ED320AC438BA5F3
rename the file to CWM.img (careful about .img.img in Windows)
this is originally from: http://forum.xda-developers.com/show....php?t=2173863
I'm using the 6.0.4.5 version because I've noticed that some versions (I've tested 6.0.3.2 and 6.0.4.6) have problems with adb commands when used in "fastboot boot CWM.img" mode.
download Guru Bootloader Reset from here: http://www.htc1guru.com/dld/guru_boo...reset_1-0-zip/ (this is the thread http://forum.xda-developers.com/show....php?t=2527194)
----> if Guru Bootloader Reset gives you a hard time (freezes), use alternate method from FAQ #8
Click to expand...
Click to collapse
Not sure what's confusing here, it does say "Common downloads for all methods" -> so yes, you need these.
Maybe I'll just put them at the beginning of each method instead (when I get a chance to rewrite and add the mirrors)
chris9486 said:
I realised after installing xposed and sense6toolbox that I needed a custom kernel. I was lost in a world of roms, roots, custom recovery, xposed and just gave up because I couldn't find out what I needed to do re. the kernel.
Click to expand...
Click to collapse
You would need ElementalX kernel for wake gestures, and since ARHD 71.1 is "Sense 6 Android 4.4.2" you would need version 14.12 of ElementalX.
chris9486 said:
Can I ask, is this the correct ruu for my phone mid and cid?
Click to expand...
Click to collapse
yes, that RUU is for your model:
Code:
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
but it is a lower version and decrypted, so only flashable with S-OFF
---------- Post added at 01:18 PM ---------- Previous post was at 01:13 PM ----------
chris9486 said:
I downloaded arhd 31.6. Flashed. Cleared cache. Now I am stuck in a bootloop, cannot get into recovery and none of my computers will recognise the phone in ADB even though they did before!
I get nothing under adb devices.
:crying:
Click to expand...
Click to collapse
did you check md5 on the download? also which recovery are you using (name and version)
adb only works in custom recovery, or booted up ROM with USB debugging enabled.
why can't you get to recovery?
B) Force reboot
Press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)
then enter RECOVERY
nkk71 said:
Thanks for the feedback.
by bootloader/FASTBOOT USB, I mean this screen:
because that's where you issue fastboot commands, and the "fastboot getvar all" command is one every user should be familiar with, as it gives you the necessary information to know what your phone is.
I'll probably edit the box and make a copy/paste of the actual command prompt.
Not sure what's confusing here, it does say "Common downloads for all methods" -> so yes, you need these.
Maybe I'll just put them at the beginning of each method instead (when I get a chance to rewrite and add the mirrors)
You would need ElementalX kernel for wake gestures, and since ARHD 71.1 is "Sense 6 Android 4.4.2" you would need version 14.12 of ElementalX.
yes, that RUU is for your model:
Code:
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
but it is a lower version and decrypted, so only flashable with S-OFF
Click to expand...
Click to collapse
Did you see my post above? I have now bricked my phone and a little stuck on how to get out of it. Please can you help?
I can enter bootloader. Go into fastboot. Connect to PC (W7). PC beeps, fastboot usb appears on the phone. ADB shows no devices! Rebooted pc on numerous occasions. Still no luck. I have uninstalled the drivers, installed HTC ones, reinstalled ADB etc, still nothing. It worked fine yesterday in ADB.
I cannot enter recovery either. I don't know what to do.
chris9486 said:
Did you see my post above? I have now bricked my phone and a little stuck on how to get out of it. Please can you help?
I can enter bootloader. Go into fastboot. Connect to PC (W7). PC beeps, fastboot usb appears on the phone. ADB shows no devices! Rebooted pc on numerous occasions. Still no luck. I have uninstalled the drivers, installed HTC ones, reinstalled ADB etc, still nothing. It worked fine yesterday in ADB.
I cannot enter recovery either. I don't know what to do.
Click to expand...
Click to collapse
I already answered above
nkk71 said:
Thanks for the feedback.
by bootloader/FASTBOOT USB, I mean this screen:
because that's where you issue fastboot commands, and the "fastboot getvar all" command is one every user should be familiar with, as it gives you the necessary information to know what your phone is.
I'll probably edit the box and make a copy/paste of the actual command prompt.
Not sure what's confusing here, it does say "Common downloads for all methods" -> so yes, you need these.
Maybe I'll just put them at the beginning of each method instead (when I get a chance to rewrite and add the mirrors)
You would need ElementalX kernel for wake gestures, and since ARHD 71.1 is "Sense 6 Android 4.4.2" you would need version 14.12 of ElementalX.
yes, that RUU is for your model:
Code:
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
but it is a lower version and decrypted, so only flashable with S-OFF
---------- Post added at 01:18 PM ---------- Previous post was at 01:13 PM ----------
did you check md5 on the download? also which recovery are you using (name and version)
adb only works in custom recovery, or booted up ROM with USB debugging enabled.
why can't you get to recovery?
B) Force reboot
Press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)
then enter RECOVERY
Click to expand...
Click to collapse
I've never checked md5 in my life of using computers and the internet. I am an idiot I know.
ADB was working on fastboot USB in the bootloader yesterday. I didn't enter recovery once yesterday.
When I try to go to recovery (cwm) it just flashes for a second then reboots.
I will try the force reboot but not confident.
Do I try the force reboot when the phone is off, in the boot loop or in the bootloader. Because all three just send me back to the bootloader after about 10 seconds and none cause the phone to reboot.
nkk71 said:
I already answered above
Click to expand...
Click to collapse
Sorry I crossed posts, I wasn't sure if you'd seen it.
When it is in the bootloop it tries to enter recovery itself, it says something like no context file or something. It flashes for a second and that's it, it returns to a bootloop. It does the same if I try enter recovery from the bootloader.
When do I do the force reboot. No matter what I try it just enters the bootloader screen.
chris9486 said:
Sorry I crossed posts, I wasn't sure if you'd seen it.
When it is in the bootloop it tries to enter recovery itself, it says something like no context file or something. It flashes for a second and that's it, it returns to a bootloop. It does the same if I try enter recovery from the bootloader.
When do I do the force reboot. No matter what I try it just enters the bootloader screen.
Click to expand...
Click to collapse
please change your recovery to twrp 2.6.3.3 as mentioned below:
A) Having Problems? Rule #1: check MD5 on all your downloads; one single corrupt download can keep you trying for hours on end for nothing!
https://www.google.com/#q=MD5 ; Basically (in our context), MD5 checksums are to verify that the file you downloaded isn't corrupt
on Mac, Linux, and Android terminals it's already built in:
Mac: in terminal, just type md5 <name of file>
----> MD5 (<name of file>) = 12345678901234567890123456789012
Linux: in terminal, just type md5sum <name of file>
----> 12345678901234567890123456789012 <name of file>
Android: in "adb shell", just type md5sum <name of file>
----> 12345678901234567890123456789012 <name of file>
Windows (seems not built-in!?!?): you can use programs such as http://winmd5.com/ , http://implbits.com/hashtab.aspx , http://www.pc-tools.net/win32/md5sums/ or any other one of your choosing.
C) Problems installing a ROM (in particular 4.4+ versions, and getting permission/set_metadata errors)
for M7_U/UL models, get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
Note: at the time of this writing these are the most reliable versions, even the 2.7.x.x series seem to still have problems
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]fastboot devices[/COLOR][/B]
HT34xxxxxxxx fastboot [I][SIZE="1"]<- you are in bootloader[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.120s]
finished. total time: 0.120s
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.160s]
finished. total time: 0.160s
-> enter RECOVERY and install the ROM
Related
Hi All,
I'm a noob when it comes to this stuff, but I've learned a lot over the last day. I soft bricked my HTC One Developer Edition while trying to do the most recent OTA update to 4.4.
What happens:
When booting normally, it goes initially to the normal white HTC screen, then to a "pink" screen (it's mostly pink, but it's really just messed up graphics), then goes to the HTC One loading screen (except BEATS is blue instead of red). Then it just freezes on that loading screen.
I can boot into the bootloader and recovery (currently TWRP, but was stock when doing the OTA update)
What I've tried:
I've used Fastboot to flash TWRP, so that part is good. Within TWRP, I've wiped the cache, system, Dalvik.
I've tried using Fastboot to flash the RUU Zip file (first one in the list here) in both Windows and OSX, while in "FASTBOOT USB" mode and in RUU mode. Each time, it starts sending, but around 43-44 secs it fails with "remote:not allowed: For reference, the top of the bootloader screen says TAMPERED, then UNLOCKED. I'm running HBOOT 1.55 and have S-ON (but unlocked bootloader). OS shows 3.22.1540.1
I can't get past the remote:not allowed issue, and I'm not such an expert to know what to try next. Can anyone please give me some tips on what to do next? I've tried searching, but I don't know what exactly to search for.
Thank you all!
awer25 said:
Hi All,
I'm a noob when it comes to this stuff, but I've learned a lot over the last day. I soft bricked my HTC One Developer Edition while trying to do the most recent OTA update to 4.4.
What happens:
When booting normally, it goes initially to the normal white HTC screen, then to a "pink" screen (it's mostly pink, but it's really just messed up graphics), then goes to the HTC One loading screen (except BEATS is blue instead of red). Then it just freezes on that loading screen.
I can boot into the bootloader and recovery (currently TWRP, but was stock when doing the OTA update)
What I've tried:
I've used Fastboot to flash TWRP, so that part is good. Within TWRP, I've wiped the cache, system, Dalvik.
I've tried using Fastboot to flash the RUU Zip file (first one in the list here) in both Windows and OSX, while in "FASTBOOT USB" mode. Each time, it starts sending, but around 43-44 secs it fails with "remote:not allowed: For reference, the top of the bootloader screen says TAMPERED, then UNLOCKED. I'm running HBOOT 1.55 and have S-ON (but unlocked bootloader). OS shows 3.22.1540.1
I can't get past the remote:not allowed issue, and I'm not such an expert to know what to try next. Can anyone please give me some tips on what to do next? I've tried searching, but I don't know what exactly to search for.
Thank you all!
Click to expand...
Click to collapse
Please post the output of ''fastboot getvar all'' minus your IMEI and serial no. And please post the commands your were using to flash the ruu.zip or a screenshot of your command prompt
alray said:
Please post the output of ''fastboot getvar all'' minus your IMEI and serial no. And please post the commands your were using to flash the ruu.zip or a screenshot of your command prompt
Click to expand...
Click to collapse
Thanks! The command prompt was fastboot flash zip rom.zip (I renamed it to that). For TWRP it was fastboot flash recovery recovery.img
GETVAR is attached.
EDIT: I added the command prompt and fail as well.
awer25 said:
Thanks! The command prompt was fastboot flash zip rom.zip (I renamed it to that). For TWRP it was fastboot flash recovery recovery.img
GETVAR is attached.
Click to expand...
Click to collapse
ok, first you can't flash that ruu you linked above (first in the list) because its a decrypted ruu. Decrypted ruu.zip require s-off and you are s-on. Whit s-on you can only flash signed ruu.
and btw did you enter ruu mode before ''fastboot flash zip rom.zip'' ?
---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------
awer25 said:
Thanks! The command prompt was fastboot flash zip rom.zip (I renamed it to that). For TWRP it was fastboot flash recovery recovery.img
GETVAR is attached.
EDIT: I added the command prompt and fail as well.
Click to expand...
Click to collapse
There is a 3.22.1540.1 RUU.exe on htcdev.com you could use to restore your phone. But it will not work using windows 8.1. what is your computer OS?
alray said:
ok, first you can't flash that ruu you linked above (first in the list) because its a decrypted ruu. Decrypted ruu.zip require s-off and you are s-on. Whit s-on you can only flash signed ruu.
and btw did you enter ruu mode before ''fastboot flash zip rom.zip'' ?
Thank you for that explanation. I got into RUU mode by doing fastboot oem rebootRUU, which took me to a black screen with silver HTC. That may not be RUU mode...I'm just guessing.
---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------
There is a 3.22.1540.1 RUU.exe on htcdev.com you could use to restore your phone. But it will not work using windows 8.1. what is your computer OS?
edit: Wait, there is also a 3.22.1540.1 ruu.zip on htcdev.com so try it first.
fastboot oem rebootRUU
fastboot flash zip <name_of_file>.zip
fastboot flash zip <name_of_file>.zip
fastboot reboot
Click to expand...
Click to collapse
Amazing! Thanks - I'll try this and let you know how it goes. I have Windows 8.1, but with fastboot and a zip file it should work, right? If not, I have a Windows 7 laptop at home.
awer25 said:
Amazing! Thanks - I'll try this and let you know how it goes. I have Windows 8.1, but with fastboot and a zip file it should work, right? If not, I have a Windows 7 laptop at home.
Click to expand...
Click to collapse
yes ruu.zip should work flawlessly with windows 8.1. but do not attempt the ruu.exe with 8.1, will work fine on 7.
alray said:
yes ruu.zip should work flawlessly with windows 8.1. but do not attempt the ruu.exe with 8.1, will work fine on 7.
Click to expand...
Click to collapse
I saw that I already had the 3.22.1540.1 zip file on my computer, so I tried. It got a lot further, but still failed with a remote:not allowed (see attached pic).
My next tries will be to re-download the file and try again, and if that fails, to try the RUU.exe file on the Windows 7 laptop. Is this correct, or is there something else I should try?
I'm leaving work now, so I won't be able to answer for another hour or so but thank you for your help thus far!
awer25 said:
I saw that I already had the 3.22.1540.1 zip file on my computer, so I tried. It got a lot further, but still failed with a remote:not allowed (see attached pic).
My next tries will be to re-download the file and try again, and if that fails, to try the RUU.exe file on the Windows 7 laptop. Is this correct, or is there something else I should try?
I'm leaving work now, so I won't be able to answer for another hour or so but thank you for your help thus far!
Click to expand...
Click to collapse
the ruu you have from the link you posted above is DECRYPTED it will not work with s-on!!!
alray said:
ok, first you can't flash that ruu you linked above (first in the list) because its a decrypted ruu. Decrypted ruu.zip require s-off and you are s-on.
Click to expand...
Click to collapse
And does the phone was in ruu mode? I don't see any ''fastboot oem rebootRUU'' from your screenshot...
alray said:
the ruu you have from the link you posted above is DECRYPTED it will not work with s-on!!!
And does the phone was in ruu mode? I don't see any ''fastboot oem rebootRUU'' from your screenshot...
Click to expand...
Click to collapse
Sorry I didn't explain better - the file I meant was the one from HTCDevs - I downloaded it a while ago when I had a different issue. I just renamed it to rom1 or whatever. Is this then the correct file?
Also, the phone was not in RUU mode - it was in regular fastboot mode ("FASTBOOT USB"). I'll try again in RUU mode.
awer25 said:
Sorry I didn't explain better - the file I meant was the one from HTCDevs - I downloaded it a while ago when I had a different issue. I just renamed it to rom1 or whatever. Is this then the correct file?
Also, the phone was not in RUU mode - it was in regular fastboot mode ("FASTBOOT USB"). I'll try again in RUU mode.
Click to expand...
Click to collapse
you can not flash ruu with fastboot. you MUST reboot phone in ruu mode using ''fastboot oem rebootRUU'' it will then reboot with a black screen and the htc logo. so:
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_ruu.zip
fastboot flash zip name_of_ruu.zip <------ yes again!
fastboot reboot
When in ruu mode you'll have a screen similar to this:
then proceed with ''fastboot flash zip...................''
alray said:
you can not flash ruu with fastboot. you MUST reboot phone in ruu mode using ''fastboot oem rebootRUU'' it will then reboot with a black screen and the htc logo. so:
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_ruu.zip
fastboot flash zip name_of_ruu.zip <------ yes again!
fastboot reboot
When in ruu mode you'll have a screen similar to this:
then proceed with ''fastboot flash zip...................''
Click to expand...
Click to collapse
Ok, I booted into RUU mode and flashed the file twice as per your instructions. Both times it failed. Screenshot is attached. (I even tried it a 3rd time but it still failed with the same message)
Also, I renamed the zip file to rom1.zip just to make typing it easier, but it is the file from HTCDevs, "3.22.1540.1 Developer Edition", Zip (not RUU).
Thank you!
awer25 said:
Ok, I booted into RUU mode and flashed the file twice as per your instructions. Both times it failed. Screenshot is attached. (I even tried it a 3rd time but it still failed with the same message)
Also, I renamed the zip file to rom1.zip just to make typing it easier, but it is the file from HTCDevs, "3.22.1540.1 Developer Edition", Zip (not RUU).
Thank you!
Click to expand...
Click to collapse
Try the ruu.exe on windows 7.
alray said:
Try the ruu.exe on windows 7.
Click to expand...
Click to collapse
Ok, I tried it on the Windows 7 laptop and got another error (155 - unknown error). Pic is attached. It was in RUU mode btw.
I'm currently downloading the older 1.29.xx version (Android 4.1) and will try again with that.
Just for my own knowledge - how many "parts" (partitions?) of the system are there? As in, there's the recovery partition, the "main" ROM, etc. Are those the only two? I only ask because I wonder if I messed up something in another part that makes the phone think it's not the Developer Edition? (the errors seem to point to using the wrong image, but I got it directly from HTCDevs and have now tried both the RUU and Zip versions.
awer25 said:
Ok, I tried it on the Windows 7 laptop and got another error (155 - unknown error). Pic is attached. It was in RUU mode btw.
I'm currently downloading the older 1.29.xx version (Android 4.1) and will try again with that.
Just for my own knowledge - how many "parts" (partitions?) of the system are there? As in, there's the recovery partition, the "main" ROM, etc. Are those the only two? I only ask because I wonder if I messed up something in another part that makes the phone think it's not the Developer Edition? (the errors seem to point to using the wrong image, but I got it directly from HTCDevs and have now tried both the RUU and Zip versions.
Click to expand...
Click to collapse
I got it! I had to relock my bootloader for some reason. Then, the Windows RUU installed fine.
Thank you alray for your help!
Is being stuck at the booting screen (Htc one with beats audio (red color)) same as this scenario ? Is it soft bricked or boot looped or what's it called?
I'm S-off, rooted, stock rom, hboot is 1.56 w/ CWM. At some point the phone just rebooted on its own (I was even in a different place at that time!!!) and got stuck forever at that screen. Rebooting would just make it get stuck there again. bootloader, custom recovery all work.
what do?
-marco- said:
Is being stuck at the booting screen (Htc one with beats audio (red color)) same as this scenario ? Is it soft bricked or boot looped or what's it called?
I'm S-off, rooted, stock rom, hboot is 1.56 w/ CWM. At some point the phone just rebooted on its own (I was even in a different place at that time!!!) and got stuck forever at that screen. Rebooting would just make it get stuck there again. bootloader, custom recovery all work.
what do?
Click to expand...
Click to collapse
Mine did get stuck there, but after a weird messed up pink screen (and the Beats text was blue, not red for some reason). If I was in your boat, I'd just flash a fresh rom and be done.
awer25 said:
Mine did get stuck there, but after a weird messed up pink screen (and the Beats text was blue, not red for some reason). If I was in your boat, I'd just flash a fresh rom and be done.
Click to expand...
Click to collapse
thanks !
but which one? And how?
also getvar !
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.707.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3867mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-59adc32b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s
-marco- said:
thanks !
but which one? And how?
also getvar !
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-main: 4.20.707.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
finished. total time: 0.066s
Click to expand...
Click to collapse
-marco- said:
I am at work in the office and at some point I look at my phone and I see it rebooted on its own. now it's stuck forever on the HTC one beats audio loading screen.
I didn't even touch anything before. Tried to reboot but it just gets stuck there.
Click to expand...
Click to collapse
1- Please also post a screenshot of bootloader.
2- So you're on completely stock ROM?
3- are you able to enter recovery?
4- have you simply tried "fastboot erase cache" and tried booting?
nkk71 said:
1- Please also post a screenshot of bootloader.
2- So you're on completely stock ROM?
3- are you able to enter recovery?
4- have you simply tried "fastboot erase cache" and tried booting?
Click to expand...
Click to collapse
Thanks man!
Let's get this started:
1- done, see attached.
2- yes, up to latest OTA but i was rooted.
3- yes , CWM
4- done, still gets stuck at the same screen.
now: million $ question - is there a way to get out of this stupid problem without having to lose any data at all ? one gets quite sick at having to wipe and restore backups everytime there's a booting problem with the phone. i remember with the SGS2 i just had to reflash with odin the rom i was using and boom, back in order!
-marco- said:
Thanks man!
Let's get this started:
1- done, see attached.
2- yes, up to latest OTA but i was rooted.
3- yes , CWM
4- done, still gets stuck at the same screen.
now: million $ question - is there a way to get out of this stupid problem without having to lose any data at all ? one gets quite sick at having to wipe and restore backups everytime there's a booting problem with the phone. i remember with the SGS2 i just had to reflash with odin the rom i was using and boom, back in order!
Click to expand...
Click to collapse
Well first I would recommend you update recovery to TWRP
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
since they are more compatible when flashing 4.4 ROMs (make sure to check MD5 on the files, that site doesn't play nice with download managers!)
Code:
[B]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader[/B]
-> enter recovery
Second, in TWRP, make a nandroid backup, you may need it later *** (please check below)
Third, put a ROM on the phone (in custom recovery):
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HT34xxxxxxxx recovery <- you need to be in recovery
[B]adb push <name of rom>.zip /sdcard/[/B] <- this will take about 5 mins without any progress
and install the ROM, don't select WIPE during installation, and you should have your million $ question solved... all apps, data, etc should be there, but if you get apps crashing it's because of the "dirty-flash"
As to which ROMs you can use for the above procedure, there's is a 100% stock version of 4.19.401.9 here: http://forum.xda-developers.com/showthread.php?t=2224752
I'm personally using ARHD 52.0 from here: http://forum.xda-developers.com/showthread.php?t=2183023 (stock but with improvements, and rooted)
I haven't checked if there's a 100% stock 4.20.707.6 ROM around, so you could do some googling and see.
Hope that helps
*** once you've done the backup, you can try wiping "data, cache, dalvik", and then restore the nandroid... sometimes that works
if not keep the nandroid, as it has all the information, and you can use Nandroid Manager (in play store) to extract individual information, if need be.
Good Luck
Hi, I need help FAST!
I have an AT&T (sim unlocked - done so because I live in Europe, not US) HTC One.
So, a few days ago I was playing smart and decided to install custom ROM to my device.
I've done everything as said until the S-ON procces. I ran the Rumrunner but I obviously messed up something
without knowing so it was left S-ON. So I went on to the install of dustom ROM wich I did, but I 've got stuck in a boot loop and I could only enter my recovery and bootloader. And to make matters worse I somehow succeded to delete al my files from "sd card", HTC One doesn't have SD card slot, as you know, (it has internal storage) so I deleted all my personal files ( I backed up photos, and other personal stuff to my PC in case something like this happens )
and my SuperSU and custom ROM zip files. Then I found out about flashing stock ROM, so I relocked my device to do so but the proper RUU has prooved very hard to find, I 've tried 4-5 RUUs from htc1guru.com for Cingular (AT&T) bot none worked. Maybe I should look for SIM unlocked RUU because I 've SIM unlocked it from AT&T. Now I am really annoyed and angry because of being so stupid and trying something I obviously couldn't achieve so please don't write down trere " Oh you are a noob for doing that " because I know that and I don't need any extra comments for playing smart and bricking my device. SO PLEASE IF ANYONE ON THIS FORUM CAN HELP ME, DO SO!! If i don't manage to finally fix this somehow I'm going to pay someone to fix this.
Torcidas1950 said:
Hi, I need help FAST!
I have an AT&T (sim unlocked - done so because I live in Europe, not US) HTC One.
So, a few days ago I was playing smart and decided to install custom ROM to my device.
I've done everything as said until the S-ON procces. I ran the Rumrunner but I obviously messed up something
without knowing so it was left S-ON. So I went on to the install of dustom ROM wich I did, but I 've got stuck in a boot loop and I could only enter my recovery and bootloader. And to make matters worse I somehow succeded to delete al my files from "sd card", HTC One doesn't have SD card slot, as you know, (it has internal storage) so I deleted all my personal files ( I backed up photos, and other personal stuff to my PC in case something like this happens )
and my SuperSU and custom ROM zip files. Then I found out about flashing stock ROM, so I relocked my device to do so but the proper RUU has prooved very hard to find, I 've tried 4-5 RUUs from htc1guru.com for Cingular (AT&T) bot none worked. Maybe I should look for SIM unlocked RUU because I 've SIM unlocked it from AT&T. Now I am really annoyed and angry because of being so stupid and trying something I obviously couldn't achieve so please don't write down trere " Oh you are a noob for doing that " because I know that and I don't need any extra comments for playing smart and bricking my device. SO PLEASE IF ANYONE ON THIS FORUM CAN HELP ME, DO SO!! If i don't manage to finally fix this somehow I'm going to pay someone to fix this.
Click to expand...
Click to collapse
Relax, no payment is required
What you need to do is get a rom onto the phone, RUU isn't required.
You will get a ROM onto the phone using the 'adb sideload' tool. The tutorial is here:
http://forum.xda-developers.com/showthread.php?t=2318497
I recommend that you use the latest ARHD ROM
I have the same exact problem... Only when I try side loading from adb I get an error message saying "device not found" is my HTC one lost forever?
Sent from my Nexus 5 using XDA Free mobile app
mayaakel said:
I have the same exact problem... Only when I try side loading from adb I get an error message saying "device not found" is my HTC one lost forever?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Didn't mean to thank you.. Using my phone to write this
Read the Q&As here to get your phone recognised
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
After that, install these files to a folder called htc one on your desktop.
http://koush.com/post/universal-adb-driver
Sent from my HTC One using XDA Premium 4 mobile app
Thanks will do
Sent from my Nexus 5 using XDA Free mobile app
raghav kapur said:
Relax, no payment is required
What you need to do is get a rom onto the phone, RUU isn't required.
You will get a ROM onto the phone using the 'adb sideload' tool. The tutorial is here:
http://forum.xda-developers.com/showthread.php?t=2318497
I recommend that you use the latest ARHD ROM
Click to expand...
Click to collapse
Done as you have said and installed ARHD. Now I get only the HTC logo on boot and in Hassons2000 toolkit for almost anything it says something about "more than one device and emulator"
Torcidas1950 said:
Done as you have said and installed ARHD. Now I get only the HTC logo on boot and in Hassons2000 toolkit for almost anything it says something about "more than one device and emulator"
Click to expand...
Click to collapse
okay, let's stop using toolkits for a while and do it the old fashioned way, and start at the basics.
so first get this http://www.androidfilehost.com/?fid=23329332407585867
and extract the files into a simple folder, maybe something like C:\ADB
then go to bootloader/FASTBOOT USB, and copy/past the output of "fastboot getvar all" (excluding IMEI and s/n).
nkk71 said:
then go to bootloader/FASTBOOT USB, and copy/past the output of "fastboot getvar all" (excluding IMEI and s/n).
Click to expand...
Click to collapse
I get this:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34xxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4183mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Torcidas1950 said:
I get this:
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
Click to expand...
Click to collapse
okay that looks more or less OK, is your bootloader unlocked, and which custom recovery do you have (name and version number please)?
And what is really your ultimate goal? It wasn't very clear in your first post....
Maybe just to get the phone up and running for now?
nkk71 said:
okay that looks more or less OK, is your bootloader unlocked, and which custom recovery do you have (name and version number please)?
And what is really your ultimate goal? It wasn't very clear in your first post....
Maybe just to get the phone up and running for now?
Click to expand...
Click to collapse
ClockWork Mod Recovery 6.0.4.3
Bootloader is unlocked
My ultimate and only goal is to make the phone run again normally after i fix this (if i fix this) I will never touch any system file on this or any other phone
Torcidas1950 said:
ClockWork Mod Recovery 6.0.4.3
Bootloader is unlocked
My ultimate and only goal is to make the phone run again normally after i fix this (if i fix this) I will never touch any system file on this or any other phone
Click to expand...
Click to collapse
and that was the problem, wrong recovery and you tried to probably flash a 4.4 ROM (such as ARHD 53.0)
so get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
2.7.0.4b: http://forum.xda-developers.com/showthread.php?t=2708134
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery, and install 53.0
the first boot can take anywhere from a few minutes to 15 minutes.
my personal experience (m7_ul)... after a clean flash (ie wiping userpartition during the installer, and before rebooting wiping dalvik & cache [a bit redundant, but i do it anyways]):
during the first bootup, the screen brightness changes after 3~5 minutes, then i know i'm not in a bootloop, and wait another 5~20 minutes.... more than 20 minutes (as in... "i left it overnight") is unreasonable.
PS: we can fix everything else later
nkk71 said:
and that was the problem, wrong recovery and you tried to probably flash a 4.4 ROM (such as ARHD 53.0)
so get TWRP
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery, and install 53.0
the first boot can take anywhere from a few minutes to 15 minutes.
my personal experience (m7_ul)... after a clean flash (ie wiping userpartition during the installer, and before rebooting wiping dalvik & cache [a bit redundant, but i do it anyways]):
during the first bootup, the screen brightness changes after 3~5 minutes, then i know i'm not in a bootloop, and wait another 5~20 minutes.... more than 20 minutes (as in... "i left it overnight") is unreasonable.
PS: we can fix everything else later
Click to expand...
Click to collapse
Yes, I was trying to flash ARHD 53.0 . I will try this method in an hour or so and I will contact you after I'm done. Thank you for your help
Torcidas1950 said:
Yes, I was trying to flash ARHD 53.0 . I will try this method in an hour or so and I will contact you after I'm done. Thank you for your help
Click to expand...
Click to collapse
no problem, and just in case (to avoid more unnecessary headaches) verify MD5 sum on all your downloads, and you should be good to go
Good Luck
nkk71 said:
no problem, and just in case (to avoid more unnecessary headaches) verify MD5 sum on all your downloads, and you should be good to go
Good Luck
Click to expand...
Click to collapse
How can I push the custom ROM zip file to the recovery so it can install it?
Torcidas1950 said:
How can I push the custom ROM zip file to the recovery so it can install it?
Click to expand...
Click to collapse
either:
1- OTG cabe
2- adb push
3- adb sideload
here's an example of push:
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM
.
nkk71 said:
either:
1- OTG cabe
2- adb push
3- adb sideload
here's an example of push:
Code:
C:\ADB3>[B][COLOR="Blue"]adb version[/COLOR][/B]
Android Debug Bridge version 1.0.31
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [B][I]<- yes, it took over 5 mins,
without showing any progress[/I][/B]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM
.
Click to expand...
Click to collapse
when I type "adb devices" my HTC One doesn't show up
Torcidas1950 said:
when I type "adb devices" my HTC One doesn't show up
Click to expand...
Click to collapse
go here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
FAQ#2
nkk71 said:
go here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
FAQ#2
Click to expand...
Click to collapse
When i pushed the ARHD.zip and tried to install it started and said fail, I tried with another version of TWRP and it said fail again.
Torcidas1950 said:
When i pushed the ARHD.zip and tried to install it started and said fail, I tried with another version of TWRP and it said fail again.
Click to expand...
Click to collapse
sounds like a bad download, please check the MD5 on the ARHD.zip file
nkk71 said:
sounds like a bad download, please check the MD5 on the ARHD.zip file
Click to expand...
Click to collapse
Maybe I will try tomorrow, now I'm going to sleep
Hi, I have an issue as well. It appears my M7 is bricked.
Completed so far was unlocked the phone. Then flashed CWM. Then attempted to flash Android Revolution HD Google Edition, but it started to do a boot loop. Issue being, it appears that S-OFF needs to be set, and that is the root cause. However, I cannot make it S-OFF as adb is not functioning correctly, I have a feeling that when I flashed the new ROM USB Debugging was turned off.
Attempted to factory reset in CWM. Wiped all caches. Attempted to re-flash ROM. Attempted to fastboot oem lock, but still no change.
Please assist if at all possible. Can contact me on Skype as well. Fastboot details are below...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36AW910839
(bootloader) imei: 3544xxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4061mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Many thanks!
timex321321 said:
Completed so far was unlocked the phone. Then flashed CWM. Then attempted to flash Android Revolution HD Google Edition, but it started to do a boot loop. Issue being, it appears that S-OFF needs to be set, and that is the root cause.
Click to expand...
Click to collapse
You must be S-OFF to flash ARHD GPE edition otherwise it will bootloop like its doing now.
However, I cannot make it S-OFF as adb is not functioning correctly
Click to expand...
Click to collapse
ADB is only working from a booted rom or from a custom recovery
I have a feeling that when I flashed the new ROM USB Debugging was turned off.
Click to expand...
Click to collapse
Of course, ADB debugging is set to off by default so if you ahve flashed a rom, it will be off unless you turn it on from the dev option menu. Anyway USB debug is only to use ADB when booted in the OS. You can still use ADB from custom recovery even if USB debug is turned off.
Attempted to factory reset in CWM. Wiped all caches. Attempted to re-flash ROM.
Click to expand...
Click to collapse
Will not work unless you s-off the phone first
Attempted to fastboot oem lock, but still no change.
Click to expand...
Click to collapse
Why have you re-locked the bootloader on a bootlooping phone? unlock it again...
Please assist if at all possible. Can contact me on Skype as well. Fastboot details are below...
Click to expand...
Click to collapse
You'll need to flash a rom that doesn't require S-OFF (basically all roms except GPE). Then if you still want to use a GPE rom, achieve S-OFF on a Sense rom (ARHD 81 for example) and flash your GPE rom after.
If you are gonna flash a Sense rom (ARHD 81), get rid of CWM and flash TWRP 2.6.3.3.
timex321321 said:
Hi, I have an issue as well. It appears my M7 is bricked.
Completed so far was unlocked the phone. Then flashed CWM. Then attempted to flash Android Revolution HD Google Edition, but it started to do a boot loop. Issue being, it appears that S-OFF needs to be set, and that is the root cause. However, I cannot make it S-OFF as adb is not functioning correctly, I have a feeling that when I flashed the new ROM USB Debugging was turned off.
Many thanks!
Click to expand...
Click to collapse
According to the OP:
Android Revolution HD 6.1 Google Edition
You need S-OFF, otherwise you'll experience boot-loop!
You need TRWP 2.6.3.3 custom recovery!
Flash TWRP 2.6.3.3
Install AHRD 81.0
If you want to flash GPe ROM, then obtain S-OFF!
ADB only needs USB Debugging when in the OS; it works just fine in Recovery Mode without USB Debugging. You can use alray's method to push the ROM to your phone:
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 anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt 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
I knew most of that already, but how can I flash a new ROM from fastboot? adb will not work. Any suggested ROM as well?
timex321321 said:
I knew most of that already, but how can I flash a new ROM from fastboot? adb will not work. Any suggested ROM as well?
Click to expand...
Click to collapse
See my post #3 above yours!
timex321321 said:
I knew most of that already, but how can I flash a new ROM from fastboot? adb will not work. Any suggested ROM as well?
Click to expand...
Click to collapse
read the first post. Particularly what said about ADB or at least take the time to read the instructions Majmoz just posted...
Flash twrp 2.6.3.3, boot into it and then use adb push or adb sideload commands to push or install a ROM.
Thanks for the information. I re-unlocked, and flashed TWRP. When trying to push firewater for S-OFF it just hangs. The good news is that the device is now being recognized when doing adb devices. Any ideas?
timex321321 said:
Thanks for the information. I re-unlocked, and flashed TWRP. When trying to push firewater for S-OFF it just hangs. The good news is that the device is now being recognized when doing adb devices. Any ideas?
Click to expand...
Click to collapse
You need a working ROM on your phone for firewater to work. Push ARHD 81.0 first and boot into it. After you know it is working then try firewater!
majmoz said:
You need a working ROM on your phone for firewater to work. Push ARHD 81.0 first and boot into it. After you know it is working then try firewater!
Click to expand...
Click to collapse
Doesn't that ROM require S-OFF? Hence why I am trying to install Firewater.
timex321321 said:
Doesn't that ROM require S-OFF? Hence why I am trying to install Firewater.
Click to expand...
Click to collapse
ARHD 81.0 requires S-ON and an unlocked bootloader. You really need to read the OP:
You need:
HTC One unlocked with htcdev.com (S-ON) or S-OFF
Custom recovery
Firmware package from here (recommended but not needed for now)
Read this flashing guide - [GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock
majmoz said:
ARHD 81.0 requires S-ON and an unlocked bootloader. You really need to read the OP:
You need:
HTC One unlocked with htcdev.com (S-ON) or S-OFF
Custom recovery
Firmware package from here (recommended but not needed for now)
Read this flashing guide - [GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock
Click to expand...
Click to collapse
Even on base 4.4.2 still go to ARHD 81.0? Or will I have to upgrade my base?
timex321321 said:
Even on base 4.4.2 still go to ARHD 81.0? Or will I have to upgrade my base?
Click to expand...
Click to collapse
You will be alright with your current base.
Big thanks to all the posters here. Issue has been solved successfully with your help! :good::good::good:
Here's the details. Phone was rooted in 2013. I have my unlockcode.bin file saved from then.
I wanted to install a new ROM and reaslied I needed to be on a new kernal for it to work.
I tried to update using the standard options menu on the phone, didn't work, just looped.
So I backed up my media to PC, at present I can happily lose everything on the phone and go back to square 1.
I ended up looking at Team Win recovery project V2.6.3.3 which is what was used when I originally rooted it, I decided the best thing to do is was to select wipe all.
Looks like I removed the OS too as it just shows the logo when I boot normally, but I can access the bootloader menu and team win recovery menu.
Phone is connected to my PC and I have the Android SDK working and can connect to my phone using the CMD promt.
Please help, I'm computer literate but useless with phones.
Thanks
Is the phone s-off? Did you make any backups with twrp before you wiped?
ANGRY_robert said:
Is the phone s-off? Did you make any backups with twrp before you wiped?
Click to expand...
Click to collapse
I don't know what S-off means.
I did have backups on the phone but they've obviously been wiped. I have a file called backup.ab on my computer so I hope I can somehow use that
Look at your bootloader screen. At the very top under "unlocked" it will either say M7_Ux PVT SHIP S-ON or S-OFF.
You did have backups, but never copied any to a pc......
Niall44 said:
I don't know what S-off means.
I did have backups on the phone but they've obviously been wiped. I have a file called backup.ab on my computer so I hope I can somehow use that
Click to expand...
Click to collapse
download a rom and push it to your phone, then install it using twrp. Instructions posted below:
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 anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt 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
ANGRY_robert said:
Look at your bootloader screen. At the very top under "unlocked" it will either say M7_Ux PVT SHIP S-ON or S-OFF.
You did have backups, but never copied any to a pc......
Click to expand...
Click to collapse
It says M7-UL PVT SHIP S-ON RH
I take it this is bad.
As for the backups, are you saying the backup.ab file on my PC is useless?
alray beat me to it. Follow the instructions in his post. S-ON is not bad, it's standard (security on). Just can be a bit limiting depending upon the situation.
alray said:
download a rom and push it to your phone, then install it using twrp. Instructions posted below:
Click to expand...
Click to collapse
Looks promising, I will try this now. Will my choice of rom be affected by the fact my phone was on an old kernal? Something like 4.1.1 iirc
Niall44 said:
Looks promising, I will try this now. Will my choice of rom be affected by the fact my phone was on an old kernal? Something like 4.1.1 iirc
Click to expand...
Click to collapse
I think you are not correctly using the term "kernel". Kernel is boot.img and is included in every roms (when speaking about the HTC one M7)
Maybe you are talking about your Firmware version? If a rom require the firmware to be updated to a specific version, then yes updated it.
Better to post the output of "fastboot getvar all" minus your imei/sn so we can help you determine what you need to do with your firmware before flashing roms.
When you say kernel 4.1.1, I think you mean android os jellybean and not kernel. I'm trying to not confuse you here. Try and find an older rom on here that is based off jellybean and go from there.
---------- Post added at 06:38 PM ---------- Previous post was at 06:36 PM ----------
alray beat me again. I think I'll leave you in his hands.
alray said:
I think you are not correctly using the term "kernel". Kernel is boot.img and is included in every roms (when speaking about the HTC one M7)
Maybe you are talking about your Firmware version? If a rom require the firmware to be updated to a specific version, then yes updated it.
Better to post the output of "fastboot getvar all" minus your imei/sn so we can help you determine what you need to do with your firmware before flashing roms.
Click to expand...
Click to collapse
ANGRY_robert said:
When you say kernel 4.1.1, I think you mean android os jellybean and not kernel. I'm trying to not confuse you here. Try and find an older rom on here that is based off jellybean and go from there.
---------- Post added at 06:38 PM ---------- Previous post was at 06:36 PM ----------
alray beat me again. I think I'll leave you in his hands.
Click to expand...
Click to collapse
Understood about kernals, I'm used to modded xbox's so I assumed the term would translate.
Having trouble reading the info, it keeps crashing or just hanging with "waiting for device".
I think it's more a problem my end with faulty USB ports. I'll have to try it on another PC
alray said:
I think you are not correctly using the term "kernel". Kernel is boot.img and is included in every roms (when speaking about the HTC one M7)
Maybe you are talking about your Firmware version? If a rom require the firmware to be updated to a specific version, then yes updated it.
Better to post the output of "fastboot getvar all" minus your imei/sn so we can help you determine what you need to do with your firmware before flashing roms.
Click to expand...
Click to collapse
Got it.
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.61.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4075mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.063s
Niall44 said:
Got it.
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.61.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4075mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.063s
Click to expand...
Click to collapse
There is not much useful files on the web fo orange (x.xx.61.x). If you want to update your firmware to the latest version to ensure the best stability with newer Roms, you could flash an older rom and s-off your phone using Revone. Then you'll be free to flash a newer firmware even if its not based on x.xx.61.x, the latest x.xx.401.x firmware should do the job ( I think its 6.09.401.11 or .12)
alray said:
There is not much useful files on the web fo orange (x.xx.61.x). If you want to update your firmware to the latest version to ensure the best stability with newer Roms, you could flash an older rom and s-off your phone using Revone. Then you'll be free to flash a newer firmware even if its not based on x.xx.61.x, the latest x.xx.401.x firmware should do the job ( I think its 6.09.401.11 or .12)
Click to expand...
Click to collapse
Thanks for looking, so I need to find a rom with x.xx.61.x or lower in the title and install that to get started?
Niall44 said:
Thanks for looking, so I need to find a rom with x.xx.61.x or lower in the title and install that to get started?
Click to expand...
Click to collapse
no and you won't find roms based on x.xx.61.x anyway there are usually based on x.xx.401.x (international version)
arhd 31.6 will work fine on your current firmware version,
Then if you want to achieve S-OFF, all you will need is to follow instructions in Revone thread.
alray said:
no and you won't find roms based on x.xx.61.x anyway there are usually based on x.xx.401.x (international version)
arhd 31.6 will work fine on your current firmware version,
Then if you want to achieve S-OFF, all you will need is to follow instructions in Revone thread.
Click to expand...
Click to collapse
Marvelous. I got the ROM installed and working. I'll start on the S-Off, updating and fancy new ROM tomorrow. But it's way past my bedtime.
Thank you very much for being patient
Glad we, uhm .... I mean alray could help.
ANGRY_robert said:
Glad we, uhm .... I mean alray could help.
Click to expand...
Click to collapse
your help is also appreciated mate :good: keep up good work
Can't seem to get Revone to work. File is in the correct directory but I'm getting error 1 when I try "./revone -P"
I saw in another thread that installing another ROM would help, but it didn't. So I've reflashed the arhd 31.6 ROM I was given but can't seem to get any headway into getting it to work.
Trying to achieve s-off has different methods. Each method is a little different. It all depends on what hboot version you are running. Your hboot version is displayed on the bootloader screen.
Examples: 1.44, 1.54, 1.56, 1.57
See what your version is and report back.
So I'm trying to update my firmware so I can get android 5.1 working on my phone to try it out. But I am running into trouble with adb finding my phone.
When I enter "adb devices" it returns a list of nothing, entering kill-server and start-server doesn't help.
My phone says fastboot USB when I plug it in and my computer says HTC One is found and working in the device manager (on my windows 8 machine it had a yellow exclamation next to it saying unknown device so I switched to a windows 7 machine which picks it up instantly)
I also tried using Squabbi's HTC one toolkit to s-off (I have hboot 1.44) as that is needed to update the firmware however it cannot connect to my phone either (same adb problem)
adb is seemingly installed correctly, I've tired all usb 2 and usb 3 ports on my laptop and tried multiple usb cables. I've tried uninstalling and reinstalled different HTC drivers, I also tried installing the google usb drivers.
I need helps
Cofffey said:
So I'm trying to update my firmware so I can get android 5.1 working on my phone to try it out. But I am running into trouble with adb finding my phone.
When I enter "adb devices" it returns a list of nothing, entering kill-server and start-server doesn't help.
My phone says fastboot USB when I plug it in
Click to expand...
Click to collapse
If your phone says "fastboot usb" then it its booted in bootloader / fastboot mode.
ADB only works from a booted rom with usb debugging turned on or from a booted custom recovery (no matter if usb degug is on/off)
when in bootloader / fastboot usb mode, use fastboot commands, in this case "fastboot devices" will work.
and my computer says HTC One is found and working in the device manager (on my windows 8 machine it had a yellow exclamation next to it saying unknown device so I switched to a windows 7 machine which picks it up instantly)
I also tried using Squabbi's HTC one toolkit to s-off (I have hboot 1.44)
Click to expand...
Click to collapse
hboot 1.44 isn't compatible with windows 8, use windows 7 or the windows 8 drivers fix. Will work fine after hboot is updated.
I also tried using Squabbi's HTC one toolkit to s-off (I have hboot 1.44)
Click to expand...
Click to collapse
To achieve s-off on hboot 1.44 use Revone
as that is needed to update the firmware
Click to expand...
Click to collapse
S-OFF is only needed if you flash a custom firmware.
adb is seemingly installed correctly, I've tired all usb 2 and usb 3 ports on my laptop and tried multiple usb cables.
Click to expand...
Click to collapse
Always use usb 2.0 ports.
Post the outpuf of "fastboot getvar all" remove imei and sn before posting and also tell us what you want to do exactly, what firmware are you trying to flash?
I need helps[/QUOTE]
alray said:
If your phone says "fastboot usb" then it its booted in bootloader / fastboot mode.
ADB only works from a booted rom with usb debugging turned on or from a booted custom recovery (no matter if usb degug is on/off)
when in bootloader / fastboot usb mode, use fastboot commands, in this case "fastboot devices" will work.
hboot 1.44 isn't compatible with windows 8, use windows 7 or the windows 8 drivers fix. Will work fine after hboot is updated.
To achieve s-off on hboot 1.44 use Revone
S-OFF is only needed if you flash a custom firmware.
Always use usb 2.0 ports.
Post the outpuf of "fastboot getvar all" remove imei and sn before posting and also tell us what you want to do exactly, what firmware are you trying to flash?
I need helps
Click to expand...
Click to collapse
[/QUOTE]
Thanks for the reply!
I was following this video https://www.youtube.com/watch?v=ybu7fZa41so
using the fastboot commands listed which would result in cmd saying "waiting for device" forever. I didn't know adb and fastboot were different commands, adb works now that I know how to use it. Fastboot is still giving me trouble always waiting.
Should I update Hboot? I have my phone connected to a win7 laptop so that isn't a problem. Are there benefits other than windows 8?
C:\Users\Coffey>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.666.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *****************
(bootloader) imei: ******************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4063mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
When I flash a 5.1 rom, I get stuck in a loop of updating apps, it will update all the apps then restart and do it again forever.
I'm trying to install the firmware and rom from this page http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927
It says I must have the latest firmware which they have provided, I'm using the second firmware they have linked https://www.androidfilehost.com/?fid=23991606952599455
Do I need s-off for this firmware?
Thanks you for your time.
Edit: It just clicked that I was able to get fastboot imformation when before it would just wait, now when running fastboot oem rebootRUU it just produces 3 dots and becomes unresponsive
Cofffey said:
Thanks for the reply!
I was following this video https://www.youtube.com/watch?v=ybu7fZa41so
using the fastboot commands listed which would result in cmd saying "waiting for device" forever. I didn't know adb and fastboot were different commands, adb works now that I know how to use it. Fastboot is still giving me trouble always waiting.
Should I update Hboot? I have my phone connected to a win7 laptop so that isn't a problem. Are there benefits other than windows 8?
C:\Users\Coffey>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.666.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *****************
(bootloader) imei: ******************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4063mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
When I flash a 5.1 rom, I get stuck in a loop of updating apps, it will update all the apps then restart and do it again forever.
I'm trying to install the firmware and rom from this page http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927
It says I must have the latest firmware which they have provided, I'm using the second firmware they have linked https://www.androidfilehost.com/?fid=23991606952599455
Do I need s-off for this firmware?
Thanks you for your time.
Edit: It just clicked that I was able to get fastboot imformation when before it would just wait, now when running fastboot oem rebootRUU it just produces 3 dots and becomes unresponsive
Click to expand...
Click to collapse
The linked firmware is a custom firmware and requires s-off to be flashed. Why not simply updating your phone normally via ota updates from 1.29.666.5 to the latest Bell mobility version 7.17.666.7 and then you'll be able to flash 5.0+ custom roms.
If you want s-off better to achieve it now, its an easy task when on hboot 1.44 (revone s-off), newer hboot version will requires to use paid methods like sunshine s-off.
alray said:
The linked firmware is a custom firmware and requires s-off to be flashed. Why not simply updating your phone normally via ota updates from 1.29.666.5 to the latest Bell mobility version 7.17.666.7 and then you'll be able to flash 5.0+ custom roms.
If you want s-off better to achieve it now, its an easy task when on hboot 1.44 (revone s-off), newer hboot version will requires to use paid methods like sunshine s-off.
Click to expand...
Click to collapse
I had to install a 4.4.2 rom in order to s-off which I did, how would I go about getting an ota update?
Cofffey said:
I had to install a 4.4.2 rom in order to s-off which I did, how would I go about getting an ota update?
Click to expand...
Click to collapse
you are s-off now?
alray said:
you are s-off now?
Click to expand...
Click to collapse
Yea, currently running 4.4.2 Maximus HD 11.0.0
I tried to flash the custom firmware but ran into another error: failed (remote 42 custom id check fail)
Cofffey said:
Yea, currently running 4.4.2 Maximus HD 11.0.0
I tried to flash the custom firmware but ran into another error: failed (remote 42 custom id check fail)
Click to expand...
Click to collapse
Change your CID to GOOGL001:
boot in bootlaoder / fastboot usb mode
using fastboot enter these commands:
Code:
fastboot oem writecid GOOGL001
fastboot reboot-bootloader
Then confirm your cid is now GOOGL001:
Code:
fastboot oem readcid
output must be "GOOGL001"
reboot in ruu mode:
Code:
fastboot oem rebootRUU
flash this firmware, not the one you have linked above:
Code:
fastboot flash zip m7_GPE_5.1_FULL_firmware.zip
fastboot flash zip m7_GPE_5.1_FULL_firmware.zip
fastboot reboot-bootloader
then reflash twrp:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
Boot in recovery, push the GPE rom to your phone and flash it. Reboot and your phone should boot in the 5.1 rom (first boot can take up to 10-15 mins, will be stuck at htc splash screen)
Dont forget to backup your important files before, the firmware flash will wipe your phone.
alray said:
Wait, I'll make some modification to the firmware so it can be flashed on your phone and I'll send it to you in a few minutes.
Click to expand...
Click to collapse
I couldn't find the bell firmware anywhere online, would I be able to use 5.1 roms on another firmware?
Cofffey said:
I couldn't find the bell firmware anywhere online, would I be able to use 5.1 roms on another firmware?
Click to expand...
Click to collapse
see edited post above. (#8)
alray said:
see edited post above. (#8)
Click to expand...
Click to collapse
Thanks for all the help, downloading all the files now
Quick question how do I push the 5.1 rom while in twrp? With adb?
Cofffey said:
Thanks for all the help, downloading all the files now
Quick question how do I push the 5.1 rom while in twrp? With adb?
Click to expand...
Click to collapse
If you flash the latest twrp version (2.8.7.0), you'll be able to see your phone storage from your computer when booted in twrp main menu. Copy your rom (drag and drop) from its current location to "My computer --> HTC One --> internal storage --> your rom.zip here"
or you can use adb push
Phone must be booted in twrp main menu and the rom.zip mus tbe in the same folder where adb is installed:
Code:
adb push your_rom.zip /sdcard
the command window will be unresponsive as long as the transfer is not completed (around 10 min)
alray said:
If you flash the latest twrp version (2.8.7.0), you'll be able to see your phone storage from your computer when booted in twrp main menu. Copy your rom (drag and drop) from its current location to "My computer --> HTC One --> internal storage --> your rom.zip here"
or you can use adb push
Phone must be booted in twrp main menu and the rom.zip mus tbe in the same folder where adb is installed:
Code:
adb push your_rom.zip /sdcard
the command window will be unresponsive as long as the transfer is not completed (around 10 min)
Click to expand...
Click to collapse
Everything is up and running! Thanks for all the help!
One last question though haha, would you flash something like ElementalX on top of this 5.1 rom?
Cofffey said:
Everything is up and running! Thanks for all the help!
One last question though haha, would you flash something like ElementalX on top of this 5.1 rom?
Click to expand...
Click to collapse
If you need some of elementalX features then yes flash it, you can always revert back to the previous kernel that comes with the rom by extracting it from the rom.zip and flashing it using fastboot:
Code:
fastboot flash boot boot.img
fastboot erase cache
fastboot reboot
ElementalX kernel must be flashed in recovery.