Htc One stuck on Logo, need 1.29.666.17 RUU to flash or another solution - One (M7) Q&A, Help & Troubleshooting

EDIT: This is the Htc One (M7) btw. Guess it was obvious because of the version it came with out of the box, but just to clear any confusion.
EDIT 2: Meant to say my Device was S-On* NOT S-Off. Sorry.
So I'm completely new to Android, and yesterday was the day I got my first ever Android device.
It came with Sense 5 and android 4.1.2 out of the box.
After a while of playing around with my new phone I started checking for updates to get it to the latest version. When I first check it showed that a small update was available and I started downloading it. I noticed that when this update was installing it would first go into that screen where it shows that phone with a green arrow and a download bar, and then all of a sudden it would restart and go back to the Htc One Logo. It did this a few times before finally completing the upgrade.
I checked for updates again and this time it showed me Android 4.3 + Sense 5.5. I downloaded and started installing the upgrade. It did the same thing as last time but I decided I'd power off the device (Figured out later this was what caused this whole problem) and power it on again. After I did that it was stuck on the Htc Logo.
I went on the bootloader and tried factory resetting but it just brought me back to the Htc Logo again.
I found a few threads telling me to hook up my device to the computer, load up fastboot and use cmd to clear the cache and it should work. That failed too however.
After talking with a few of my friends who happen to be android experts, they told me that I because I had turned off the device in the middle of the update I had somehow corrupted some system partition thing and I'd need to flash the stock rom on once again.
After almost 24 hours of research, I've gotten to a point where I've almost figured it out but I hit a bump. My device is not rooted and is S-On (Bootloader used to be locked but in the process of fixing it).
According to my friends because my device is S-On I won't be able to flash Custom roms and need a RUU file that is specific to my carrier. I found out that I basically need the RUU file that has the same number as 1.29.666.17
This apparently is almost non-existent on the web. This is the bump I've hit and I have no idea what I can do now.
Any help would be appreciated.
Also note that I am incredibly new to android. Never rooted or anything in my life before. I've had quite the learning curve in the past day though.

Can you post a fastboot getvar all using command prompt and remove your imei and serial no please?
Sent from my HTC One using xda app-developers app

stovie_steve said:
Can you post a fastboot getvar all using command prompt and remove your imei and serial no please?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
(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.17
(bootloader) version-misc: PVT SHIP S-ON
(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: 4319mV
(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.047s

Als26 said:
(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.17
(bootloader) version-misc: PVT SHIP S-ON
(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: 4319mV
(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.047s
Click to expand...
Click to collapse
you phone is not s-off
your going to have to unlock the bootloader and flash custom recovery and a rom to attempt to get s-off so you can convert your phone to the international or developer version
instructions on how to convert here >> http://forum.xda-developers.com/showthread.php?t=2356401

clsA said:
you phone is not s-off
your going to have to unlock the bootloader and flash custom recovery and a rom to attempt to get s-off so you can convert your phone to the international or developer version
Click to expand...
Click to collapse
That was my mistake, I did mean to say S-On.
I did try to get the S-Off using an Htc One Toolkit (http://forum.xda-developers.com/showthread.php?t=2364445)
However right after Step 1a (downloading Firewater), I moved to step 1b (rebooting my device) it kept saying "adb reboot
error: device not found"
I googled this and it told I had to enable USB debugging, which I can only do through the settings of the phone apparently. And I can't access it so I'm not sure if I can still S-Off my device.

When you enable USB debugging does a pop up box come up on your phone when connecting to your computer to allow the computer to connect?
Sent from my HTC One using xda app-developers app

stovie_steve said:
When you enable USB debugging does a pop up box come up on your phone when connecting to your computer to allow the computer to connect?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
See that's the thing, I can't enable USB Debugging because my phone is stuck on the bootlogo.
I don't think there's a way for me to enable USB debugging without having access to there phone, or is there?

Als26 said:
See that's the thing, I can't enable USB Debugging because my phone is stuck on the bootlogo.
I don't think there's a way for me to enable USB debugging without having access to there phone, or is there?
Click to expand...
Click to collapse
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7ul
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot

clsA said:
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse
Alright so did what you said, successfully flashed the new recovery.
Sideloading seems to be giving me some trouble though.
After I "swiped to sideload" I get this
Updating partition details...
E: Unable to mount '/cache'
Full SELinux support is present.
E: Unable to mount '/cache'
E: Unable to mount '/cache'
Starting ADB sideload feature...
Been stuck at that for about 15minutes now.
About 5 minutes in I thought I was maybe supposed to use my pc to sideload, but cmd said "error: device not found".
Thanks again for your help by the way.

Als26 said:
Alright so did what you said, successfully flashed the new recovery.
Sideloading seems to be giving me some trouble though.
After I "swiped to sideload" I get this
Updating partition details...
E: Unable to mount '/cache'
Full SELinux support is present.
E: Unable to mount '/cache'
E: Unable to mount '/cache'
Starting ADB sideload feature...
Been stuck at that for about 15minutes now.
About 5 minutes in I thought I was maybe supposed to use my pc to sideload, but cmd said "error: device not found".
Thanks again for your help by the way.
Click to expand...
Click to collapse
Your going to have to get your drivers fixed on the pc
Try and install these
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe

clsA said:
Your going to have to get your drivers fixed on the pc
Try and install these
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
Click to expand...
Click to collapse
Didn't work. Ran the file, used device manager to manually locate the files in Program Files (x86) and double clicked "HTC". Just keeps saying it couldn't find the driver software for my device.
But if I understand correctly, all I have to do is find a way to update the drivers and I'll be able to sideload the Rom, and hopefully I'll have a working HTC One once again?

Als26 said:
Didn't work. Ran the file, used device manager to manually locate the files in Program Files (x86) and double clicked "HTC". Just keeps saying it couldn't find the driver software for my device.
But if I understand correctly, all I have to do is find a way to update the drivers and I'll be able to sideload the Rom, and hopefully I'll have a working HTC One once again?
Click to expand...
Click to collapse
yes or use a usb otg cable to load a rom to your phone from TWRP

clsA said:
yes or use a usb otg cable to load a rom to your phone from TWRP
Click to expand...
Click to collapse
Gave up trying to install new drivers and instead opted to pay a small fee to get it fixed.
Thanks again for the help, may have worked if I got those drivers installed.

Als26 said:
Gave up trying to install new drivers and instead opted to pay a small fee to get it fixed.
Thanks again for the help, may have worked if I got those drivers installed.
Click to expand...
Click to collapse
ok

clsA said:
ok
Click to expand...
Click to collapse
A few quick questions.
The rom will work even if I'm S-ON right?
Also if I do fix my phone using this method, is there a way for me to return it to the stock rom?

Als26 said:
A few quick questions.
The rom will work even if I'm S-ON right?
Also if I do fix my phone using this method, is there a way for me to return it to the stock rom?
Click to expand...
Click to collapse
Sounds like you haven't read anything about, rooting, S-Off, firmware,hboots,roms, etc..
Suffice to say most people on this forum have more trouble going back to full out of the box stock than anything else.. compared to that, unlocking bootloader, rooting and flashing roms is a doddle(very easy). Suggestion...Read first.
Sent from my HTC One using XDA Premium 4 mobile app

bored_stupid said:
Sounds like you haven't read anything about, rooting, S-Off, firmware,hboots,roms, etc..
Suffice to say most people on this forum have more trouble going back to full out of the box stock than anything else.. compared to that, unlocking bootloader, rooting and flashing roms is a doddle(very easy). Suggestion...Read first.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have not :/
I usually do my research before attempting to do anything to any of my devices, but since I had no intention of rooting/S-ff/Unlocking bootloaders I'm just incredibly clueless. Did some reasearch and it does look like sideloading Roms work on S-On devices. :good:
I have a question for you, or anyone else that knows, but the guy I sent my phone to repair told me the following:
Since I couldn't find the RUU specific to my device, I tried using a Nandroid backup that someone uploaded (This was for Bell Mobile). According to him, he says I must have tried flashing a corrupt rom or something so it's no longer an easy fix. He wants me to pay $130 so he can send it back to some factory to get it fixed. He's telling that this is no longer a soft-brick, but a hard-brick (note that the phone can still access the bootloader, recovery, etc).
I'm pretty sure this guys trying to milk me out of my money, so I told him I'd pick it up tomorrow and get back to him later.
I just want to make sure that what he's saying isn't true though, since I'm not exactly knowledgeable about this and I have a pretty good chance of being wrong.

Als26 said:
I have not :/
I usually do my research before attempting to do anything to any of my devices, but since I had no intention of rooting/S-ff/Unlocking bootloaders I'm just incredibly clueless. Did some reasearch and it does look like sideloading Roms work on S-On devices. :good:
I have a question for you, or anyone else that knows, but the guy I sent my phone to repair told me the following:
Since I couldn't find the RUU specific to my device, I tried using a Nandroid backup that someone uploaded (This was for Bell Mobile). According to him, he says I must have tried flashing a corrupt rom or something so it's no longer an easy fix. He wants me to pay $130 so he can send it back to some factory to get it fixed. He's telling that this is no longer a soft-brick, but a hard-brick (note that the phone can still access the bootloader, recovery, etc).
I'm pretty sure this guys trying to milk me out of my money, so I told him I'd pick it up tomorrow and get back to him later.
I just want to make sure that what he's saying isn't true though, since I'm not exactly knowledgeable about this and I have a pretty good chance of being wrong.
Click to expand...
Click to collapse
Sure sounds like a scam to me, I'm pretty sure we can get your phone working if your willing to read and learn

clsA said:
Sure sounds like a scam to me, I'm pretty sure we can get your phone working if your willing to read and learn
Click to expand...
Click to collapse
Definitely am. Going to pick up the phone tomorrow and try out sideloading through a USB Otg cable. I'll report back with the results. Really hoping this will work.

clsA said:
Sure sounds like a scam to me, I'm pretty sure we can get your phone working if your willing to read and learn
Click to expand...
Click to collapse
Fixed it!
I sideloaded the rom you linked me through a USB Otg Cable. Thanks a lot for your help!
Now I just want to get it back completley to stock.
If I backup my phone through this rom and then go back to stock, I'm assuming my backup file will restore all my contacts/settings/photos etc?

Related

BIG Trouble :(

Hi guys got myself into a bit of trouble with my HTC One
I unlocked the bootloader and rooted the phone today
Then my phone asked me to update and silly me accepted and tried to update WRONG choice
Now when i try to boot my phone all it comes up with is the HTC quietly brilliant screen with the development purpose text at the bottom.
I can get into fastboot and load TWRP recovery but my pc wont recognise my phone for me to install a custom stock rom onto the internal storage so i can flash it with TWRP
Is there anything i can do or have i bricked the phone?
Cheers guys
mimicuk said:
Hi guys got myself into a bit of trouble with my HTC One
I unlocked the bootloader and rooted the phone today
Then my phone asked me to update and silly me accepted and tried to update WRONG choice
Now when i try to boot my phone all it comes up with is the HTC quietly brilliant screen with the development purpose text at the bottom.
I can get into fastboot and load TWRP recovery but my pc wont recognise my phone for me to install a custom stock rom onto the internal storage so i can flash it with TWRP
Is there anything i can do or have i bricked the phone?
Cheers guys
Click to expand...
Click to collapse
Enter ADB Sideload from TWRP and push the rom using adb from your computer
nidus123 said:
Enter ADB Sideload from TWRP and push the rom using adb from your computer
Click to expand...
Click to collapse
Please can you tell me how to do that
mimicuk said:
Please can you tell me how to do that
Click to expand...
Click to collapse
http://m.androidcentral.com/android-201-10-basic-terminal-commands-you-should-know
http://forum.xda-developers.com/showthread.php?t=2141817
Sent from my HTC One using xda premium
cannot install the ADB drivers as i cant enable usb debugging on my phone
Follow what I said in my long post here:
http://forum.xda-developers.com/showthread.php?p=42607035
I'm guessing you don't have a nandroid, so download one from the links at the end of my post
Sent from my HTC One using xda app-developers app
mimicuk said:
cannot install the ADB drivers as i cant enable usb debugging on my phone
Click to expand...
Click to collapse
ADB is installed independently of the phone, you don't need a phone hooked up to install ADB
Bhavpreet said:
Follow what I said in my long post here:
http://forum.xda-developers.com/showthread.php?p=42607035
I'm guessing you don't have a nandroid, so download one from the links at the end of my post
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
But how do i push this with ADB if i havent got usb debugging enabled?
You're right. Without usb debugging..you can't push anything to your phone.
Hmm, since your phone can boot into hboot, you're not bricked.
Is there ANYTHING on your device that you might be able to flash in recovery? Have you tried factory resetting in hboot?
Sent from my HTC One using xda app-developers app
Bhavpreet said:
You're right. Without usb debugging..you can't push anything to your phone.
Hmm, since your phone can boot into hboot, you're not bricked.
Is there ANYTHING on your device that you might be able to flash in recovery? Have you tried factory resetting in hboot?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
ive tried factory reset but it does nothing and theres nothing on my device to flash
I thought USB debugging would be on by default when you are in recovery, I know my machine would sometimes throw the 'device failed' message or whatever, but unplugging it and plugging it back in usually worked for me.
Nevermind
i have these details if they mean anything to you
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4V.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.161.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH34NW902796
(bootloader) imei: 354436055515819
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4132mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.042s
DragnzKlaw said:
Down load a ROM from your phone and have it save on you sdcard. Then you should be able to flash from there. I always keep a ROM on sdcard for these situations.
╰(◣﹏◢)╯
Click to expand...
Click to collapse
i dont understand what you mean when you say save my rom on a sdcard, the htc one doesnt suport sdcards??
When you plug your phone into the PC, does it show up in your device manager? And if so, what does it show up as?
I realized that after posting. Sorry.
╰(◣﹏◢)╯
RuleOfSines said:
When you plug your phone into the PC, does it show up in your device manager? And if so, what does it show up as?
Click to expand...
Click to collapse
it shows up as Android USB Device then if i click on the + it says My HTC
Okay, did you end up installing the ADB drivers mentioned earlier? I think the phone would show up differently in device manager if the bridge was working.
mimicuk said:
ive tried factory reset but it does nothing and theres nothing on my device to flash
Click to expand...
Click to collapse
I really dont know what to say man..thats all i can think of.You could try to do what i said before and see if it works, maybe you did have usb debugging on, other than that..theres nothing else i know that you can do
RuleOfSines said:
Okay, did you end up installing the ADB drivers mentioned earlier? I think the phone would show up differently in device manager if the bridge was working.
Click to expand...
Click to collapse
you mean the universal adb drivers?
yes i went to install them but its not showing my device just the nexus and other google phones

i need help i think my device is bricked

okk so i was trying to flash a rom for the first time and i really went at it the wrong way. i didin't backup my original RUU and now my device is stuck on the bootloader screen and i really have no idea what to do. i just want to get an OS running on my phone right now cause im freaking out. my company carrier is rogers and this is what my phone is showing right now:
***tampered***
***relocked***
m7_ul pvt ship s-on rh
hboot-1,55,0000
radio-4a.20.3263.16
opendsp -v32,120.274.0909
os-
emmc-boot 2048mb
i try looking for another ruu to flash in my phone but i cant seem to find one that works with my phone..even when i try using the flashboot getvar command to check for the version this is all i got.. : C:\Users\david\Desktop\sdk-tools>fastboot getvar version-main
version-main:
finished. total time: 0.001s
any help at this point would be greatly appreciated i need to get my phone up working so i can receive my calls
i have managed to bring back recovery mode by re-unlocking it via htcdev..now when the phone boots it goes to the google logo and then the language selecting screen then restarts after 10 secs everytime
Instead of the fastboot command you typed, write:
Code:
fastboot getvar all
Then look for "CID". Search for a RUU for that CID. If you can't find one, we'll discuss other solutions.
fenstre said:
Instead of the fastboot command you typed, write:
Code:
fastboot getvar all
Then look for "CID". Search for a RUU for that CID. If you can't find one, we'll discuss other solutions.
Click to expand...
Click to collapse
this is what i got from the fastboot getvar all command :
C:\Users\david\Desktop\sdk-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA346W904162
(bootloader) imei: 354439050131335
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4290mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fe1214a4f2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.053s
cidnum says ROGER001? im i don't think ive seen cid what that number around
edit: could it be possible that this is what i need ? "M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17"
since i did not make a backup is there a chance i can restore this ? ive tried the method that suggest sideloading but it didn't work or maybe i didin't do it right but it didn't wanna recognize my phone when i tried the command'
edit 2: also, im using twrp instead of cwm if that information can help in any way.
If you can let us know which rom you attempted to install and what you managed to do. Did you install custom recovery etc.
gffmac said:
If you can let us know which rom you attempted to install and what you managed to do. Did you install custom recovery etc.
Click to expand...
Click to collapse
well all i was trying to do was install the goole play edition rom (bigxie_m7_GPe_KRT16S_odexed-signed.zip) but after the installation it kept restarting after the language selection screen. i used twrp to flash the rom. right now all im able to do is cycle through the booloader, the recovery screen and to the language selection screen
Unless you have another rom (4.3 rom) copied onto the storage on your phone you will probably have to flash stock recovery and recover by installing a stock RUU for your carrier/CID version.
---------- Post added at 11:59 AM ---------- Previous post was at 11:54 AM ----------
Out of curiosity try going into twrp and doing a factory reset (wipe) and reboot see if you have the same issue.
is there such thing as a stuck RUU for rogers in canada? ive been looking on the internet but i can't seem to find anything that could works for my phone. maybe you could point me in a direction so i could look ?
deerome said:
is there such thing as a stuck RUU for rogers in canada? ive been looking on the internet but i can't seem to find anything that could works for my phone. maybe you could point me in a direction so i could look ?
Click to expand...
Click to collapse
Cant see any for rogers
Just found this http://htconeroot.com/htc-one-tutorials/how-to-copy-files-to-htc-one-using-twrp-mount-and-adb/ if you can copy a rom to the phone it will probably work.
A nandroid backup for rogers is here http://forum.xda-developers.com/showthread.php?t=2207874 or you could flash a pre 4.4 rom. CWM needed to recover a CWM backup and backup would need to be in right directory.
You would need to unlock bootloader to do these things.
If I was you I would download a custom rom like Android Revolution HD 40.3 copy over via above process, do a wipe and install, without s-off you probably have to flash kernel via fastboot.
gffmac said:
Cant see any for rogers
Just found this http://htconeroot.com/htc-one-tutorials/how-to-copy-files-to-htc-one-using-twrp-mount-and-adb/ if you can copy a rom to the phone it will probably work.
A nandroid backup for rogers is here http://forum.xda-developers.com/showthread.php?t=2207874 or you could flash a pre 4.4 rom. CWM needed to recover a CWM backup and backup would need to be in right directory.
You would need to unlock bootloader to do these things.
If I was you I would download a custom rom like Android Revolution HD 40.3 copy over via above process, do a wipe and install, without s-off you probably have to flash kernel via fastboot.
Click to expand...
Click to collapse
thanks for your answers
i definitly am gonna try installing the android revolution hd rom to see if i can at least get an OS running on my phone. what command do i have to use to flash the kernel ?
also, i have tried sideloading/pushing the nandroid backup before but that didint seem to work, not sure if i did something wrong.
deerome said:
thanks for your answers
i definitly am gonna try installing the android revolution hd rom to see if i can at least get an OS running on my phone. what command do i have to use to flash the kernel ?
also, i have tried sideloading/pushing the nandroid backup before but that didint seem to work, not sure if i did something wrong.
Click to expand...
Click to collapse
To flash a kernel via fastboot 'fastboot flash boot boot.img'. Make sure the boot.img (if thats what its called) is in the same folder as fastboot. The corresponding kernel(boot.img) is inside the zip file of most roms.
gffmac said:
To flash a kernel via fastboot 'fastboot flash boot boot.img'. Make sure the boot.img (if thats what its called) is in the same folder as fastboot. The corresponding kernel(boot.img) is inside the zip file of most roms.
Click to expand...
Click to collapse
thanks to your help i was able to install an earlier version of android hd so after many hours of headache i somehow managed to install the android hd rom by sideloading it with cwm. what a pain in the arse -_-. nonetheless that was a great help, what should i do now so something like this don't happen again? i wanted to have the google edtion on my htc but i think im gonna wait until im better at this thing.
anyways thanks again man i really appreciate you have no idea how frustrated i was lol :good:
deerome said:
thanks to your help i was able to install an earlier version of android hd so after many hours of headache i somehow managed to install the android hd rom by sideloading it with cwm. what a pain in the arse -_-. nonetheless that was a great help, what should i do now so something like this don't happen again? i wanted to have the google edtion on my htc but i think im gonna wait until Im better at this thing.
Anyways thanks again man i really appreciate you have no idea how frustrated i was lol :good:
Click to expand...
Click to collapse
No probs glad you got it working again.
If you really want to try a Google Edition rom you would need to s-off your phone which is trickier than what you have done so far so may want to read up some more.
I had the exact same problem while i was flashing a GEdition ROM. The problem here is that my volume Keys dont work and i cant manage to enter recovery/bootloader over ADB. Tried all usb cords and porta. Still giving me Device not found. Any tricky way to access bootloader or recovery?
I've already sent it to warranty but without the original software.... Blablabla they told me that it would only work
with a board replacement... 180€
Any help?
Sent from my Desire HD using Tapatalk
deerxmoose said:
I had the exact same problem while i was flashing a GEdition ROM. The problem here is that my volume Keys dont work and i cant manage to enter recovery/bootloader over ADB. Tried all usb cords and porta. Still giving me Device not found. Any tricky way to access bootloader or recovery?
I've already sent it to warranty but without the original software.... Blablabla they told me that it would only work
with a board replacement... 180€
Any help?
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
You can get to bootloader and recovery via adb commands but thats from a running rom I presume http://forum.xda-developers.com/showthread.php?t=1853159
How come your volume keys dont work, did it come that way? I presume you have tried holding power and volume down for a prolonged length of time??
gffmac said:
You can get to bootloader and recovery via adb commands but thats from a running rom I presume http://forum.xda-developers.com/showthread.php?t=1853159
How come your volume keys dont work, did it come that way? I presume you have tried holding power and volume down for a prolonged length of time??
Click to expand...
Click to collapse
For no reason they stop working. And i think its a hardware malfunction. Besides that, i cant manage to enter bootloader or recovery to instala other ROM.
I guess with Samsung Phones there is a doubletap on the screen to enter bootloader.
Im really stressing here.
Sent from my Desire HD using Tapatalk
deerxmoose said:
For no reason they stop working. And i think its a hardware malfunction. Besides that, i cant manage to enter bootloader or recovery to instala other ROM.
I guess with Samsung Phones there is a doubletap on the screen to enter bootloader.
Im really stressing here.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
I would contemplate opening the phone up to check the behind the volume buttons but that is very risky.
gffmac said:
I would contemplate opening the phone up to check the behind the volume buttons but that is very risky.
Click to expand...
Click to collapse
Before trying that ill prefer to try Any other solutions. Anyone?
Sent from my Desire HD using Tapatalk
There is no bootloader in Samsung phones, and no doubletap. You need to hit the buttons as well. If you are able to boot into the phone and adb devices shows the device, you can do
adb reboot-bootloader or adb reboot recovery
SaHiLzZ said:
There is no bootloader in Samsung phones, and no doubletap. You need to hit the buttons as well. If you are able to boot into the phone and adb devices shows the device, you can do
adb reboot-bootloader or adb reboot recovery
Click to expand...
Click to collapse
Tried that over and over and it keeps saying device not found.
Sent from my Desire HD using Tapatalk
Then you should fix your computer/adb issues.

[Q] HTC One Bootlooping after Google Edition ARHD 6.0 installation

At this time I am pretty much hopeless... Seriously, nothing works, but if a miracle happens and I get my HTC One back to life it will be thanks to you guys.
So... This is my story:
Today I was using my HTC One M7_UL like any other day, I had Android OneDroid BETA 15 (a CyanogenMod with a few tweaks) installed and I got bored of it, so I decided to flash a Google Edition ROM. Came to the forum and looked for the thread with most replies on "Custom Android HTC One ROMs" and found the winner of the Google Edition ones, the ARHD 6.0 Google Edition. Fine, I thought, let's flash this [email protected]%#. So I started by downloading the latest version (roughly 550 MB) and connecting my HTC One to my Windows 8.1 Pro computer. The HTC drivers don't work with my 8.1 Pro Windows but since I only needed it to send the .zip file to my Internal Storage I gave it a shot. Copied everything, disconnected and proceeded to my recovery (TWRP) where I Wiped it up and flashed ARHD 6.0 GE. After installing, still on the recovery, restored the phone to factory presets and rebooted it. A Google logo appeared and some Nexus-like balls started to spin, some weird sh%t. Until there, everything absolutely fine, but it stood there with the balls spinning for 3~4 minutes and I thought it was normal because it was the first boot after flashing the new ROM. Got to Language Settings on the Android Welcome screen but then it quickly turned black and reeboted. HTC Logo appeared for roughly 1 second and it got black and rebooted again, this time starting back up but when I got to the Language setup it would do the same thing, over and over again.
So I started looking into it and didn't find many answers, then I decided to try and flash another Google Edition ROM, SkyDragon, but as I am a COMPLETE NOOB in this rooting and wobbly wobbly thingies I had no idea how I would get the .zip file to the Internal Storage, since the HTC One HAS NO SD CARD!!! I researched a bit and found sth called ADB Sideloading, which I am certain you know what it is, but the thing is, since my computer doesn't quite work with HTC Drivers I had to use my sister's PC, with Windows 7 and HTC One All-in-One kit. I could access my bootloader and recovery despite of the bootloop, which I think is a good thing, so I put it to fastboot mode, connected the cable to her computer and on the phone it changed from "fastboot" in red to "fastboot usb" in red also, so I thought, oh ok, it will work now. But when I tried ADB commands or tried any of the commands on the All-in-One thing it would just say "NO DEVICES FOUND" or something among those lines.
Anyway, if someone got this far I already thank you for trying to help but I am pretty certain I got a bricked device. I don't even now what to do, should I try to ADB Sideload this other ROM or should I try a Sense ROM, cuz I read somewhere that Google Edition ROMs only work when migrating from Sense ROMs, and if I am supposed to flash a Sense ROM how would I do so? Please try to be as simple as possible, I don't know much and I am pretty noob, anyways, thank you so much, and I hope you can help me!
(Also, before this bootloop it was S-OFF and now it shows as S-ON)
Waiting for a response,
John B.
You need TWRP 2.6.33 or newer.
You need to be S-Off.
You need to have wiped cache and dalvik and probably a full format (except sdcard) wouldn't go amiss before installing. It sounds to me like it wasn't wiped properly.
The device doesn't S-On on its own, you probably did it with the toolkit or something.
ADB doesn't work in fastboot mode, fastboot mode is for fastboot command, such as flashing recovery.
Are you still unlocked?
Give us the output of
fastboot getvar all
Without IMEI and Serial Number.
BenPope said:
You need TWRP 2.6.33 or newer.
You need to be S-Off.
You need to have wiped cache and dalvik and probably a full format (except sdcard) wouldn't go amiss before installing. It sounds to me like it wasn't wiped properly.
The device doesn't S-On on its own, you probably did it with the toolkit or something.
ADB doesn't work in fastboot mode, fastboot mode is for fastboot command, such as flashing recovery.
Are you still unlocked?
Give us the output of
fastboot getvar all
Without IMEI and Serial Number.
Click to expand...
Click to collapse
Yeah I am unlocked and untempered.
Here is my 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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxx
(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: 4309mV
(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.077s
And I am ABSOLUTELY SURE that before all of this it was S-OFF, ABSOLUTELY!
BenPope said:
You need TWRP 2.6.33 or newer.
You need to be S-Off.
You need to have wiped cache and dalvik and probably a full format (except sdcard) wouldn't go amiss before installing. It sounds to me like it wasn't wiped properly.
The device doesn't S-On on its own, you probably did it with the toolkit or something.
ADB doesn't work in fastboot mode, fastboot mode is for fastboot command, such as flashing recovery.
Are you still unlocked?
Give us the output of
fastboot getvar all
Without IMEI and Serial Number.
Click to expand...
Click to collapse
Also my TWRP is 2.6.3.3 so I should be good about that right?
Jvov said:
Also my TWRP is 2.6.3.3 so I should be good about that right?
Click to expand...
Click to collapse
Yes, but as far as I know, you need to be S-Off for GPE KitKat ROMs.
Do you really have no version-main?
If your hboot is 1.44 and dated prior to June, you should be able to use revone to S-Off, but you'll need a booting ROM of Android 4.2.2.
BenPope said:
Yes, but as far as I know, you need to be S-Off for GPE KitKat ROMs.
Do you really have no version-main?
If your hboot is 1.44 and dated prior to June, you should be able to use revone to S-Off, but you'll need a booting ROM of Android 4.2.2.
Click to expand...
Click to collapse
Can you explain exactly how can I do that?
Just flash back to another ROM for the moment that has root then use rumrunner to get S-OFF then flash ARHD GPE again. You'll be fine then.
Sent from my One using XDA Premium 4 mobile app
Also don't do a reset after flashing the rom. It will boot loop every time.
Bat cave One
zelendel said:
Also don't do a reset after flashing the rom. It will boot loop every time.
Bat cave One
Click to expand...
Click to collapse
Solved, thanks to all!

[Q] SOFT BRICKED HTC ONE. Tried Everything!!!

Hi there. This is my first thread in your great site. I have Installed custom roms hundreds of times on various handsets. Yesterday I purchased an HTC One and decided to stick a custom rom on there straight away.
Now I have a problem.....The only thing I can do is get into bootloader and recovery, I can get that far, what I cant do is install any kind of rom to get my phone working. It seems all my data has been wiped, cant mount usb using cwm or twrp so cant just stick a rom on there and flash it. Can't sideload using ADB, pretty much cant get any kind of rom on there at all. I tried using an RUU.exe to return to stock but that fails also (it stays at 5% 'headers' and goes no further)
I have literally been through every search option on google and tried every method I have found for the last 12-13 hours trying to get this solved and i'm now starting to think I have genuinelly done something terrible to my phone and that it is unrecoverable.
My final hope is that one of you genius wizardy type of guys that seem to frequent these forums could help. Im getting desperate now
EDIT: I think I flashed a rom for the M8 version like a fricking noob. Does this mean my phone is knacked?
terrypmarshall said:
Hi there. This is my first thread in your great site. I have Installed custom roms hundreds of times on various handsets. Yesterday I purchased an HTC One and decided to stick a custom rom on there straight away.
Now I have a problem.....The only thing I can do is get into bootloader and recovery, I can get that far, what I cant do is install any kind of rom to get my phone working. It seems all my data has been wiped, cant mount usb using cwm or twrp so cant just stick a rom on there and flash it. Can't sideload using ADB, pretty much cant get any kind of rom on there at all. I tried using an RUU.exe to return to stock but that fails also (it stays at 5% 'headers' and goes no further)
I have literally been through every search option on google and tried every method I have found for the last 12-13 hours trying to get this solved and i'm now starting to think I have genuinelly done something terrible to my phone and that it is unrecoverable.
My final hope is that one of you genius wizardy type of guys that seem to frequent these forums could help. Im getting desperate now [/B]
EDIT: I think I flashed a rom for the M8 version like a fricking noob. Does this mean my phone is knacked?
Click to expand...
Click to collapse
Why not start with
1- a "fastboot getvar all" (excluding IMEI and s/n),
2- what recovery you have (name and version number)
3- what were you trying to flash? link please
nkk71 said:
Why not start with
1- a "fastboot getvar all" (excluding IMEI and s/n),
2- what recovery you have (name and version number)
3- what were you trying to flash? link please
Click to expand...
Click to collapse
Yeah that would help wouldnt it sorry. im using TWRP 2.7.1.1
I was tring to flash HD revolution rom but it seems i downloaded and used the M8 version
(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) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4336mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
terrypmarshall said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) hbootpreupdate: 11
Click to expand...
Click to collapse
1- edit your post and remove IMEI,
2- use TWRP 2.6.3.3 or 2.6.3.4 (maybe 2.7.1.1 works, I haven't tested, but 2.7.0.0 does not)
3- ARHD 71.1 (m7_u/ul) is here http://forum.xda-developers.com/showthread.php?t=2183023
nkk71 said:
1- edit your post and remove IMEI,
2- use TWRP 2.6.3.3 or 2.6.3.4 (maybe 2.7.1.1 works, I haven't tested, but 2.7.0.0 does not)
3- ARHD 71.1 (m7_u/ul) is here http://forum.xda-developers.com/showthread.php?t=2183023
Click to expand...
Click to collapse
yep did that but had to wait the 5 mins b4 i could remove the imei lol.
I actually tried your fix here http://forum.xda-developers.com/showthread.php?t=2739126&page=2 just incase.
gonna try TWRP 2.6 now and see if i get any movement......
thank you for your help so far
terrypmarshall said:
yep did that but had to wait the 5 mins b4 i could remove the imei lol.
I actually tried your fix here http://forum.xda-developers.com/showthread.php?t=2739126&page=2 just incase.
gonna try TWRP 2.6 now and see if i get any movement......
thank you for your help so far
Click to expand...
Click to collapse
i'm checking the updater-script on the M8 version for possible damage...
EDIT: twrp 2.6.3.3 or .4
ok installed twrp 2.6.3.3 and still no luck in mounting storage via usb. I know the \sdcard\ section of the phone is empty through looking at file manager. I dont know if this has anything to do with it. In bootloader my OS listing is blank, like there is nothing there. I have used your fix for the Active Cmdline Overflow just incase it was that as i figured this kind of falls into that category.
At the moment, I have d/l an old RUU.exe for jellybean after relocking my phone and that is currently installing although it is stuck on 7% ''Checking Header'' and has been for a while now. I dont expect it to move on any further.
One word.....gutted, wish I had left it alone now ffs
terrypmarshall said:
ok installed twrp 2.6.3.3 and still no luck in mounting storage via usb. I know the \sdcard\ section of the phone is empty through looking at file manager. I dont know if this has anything to do with it. In bootloader my OS listing is blank, like there is nothing there. I have used your fix for the Active Cmdline Overflow just incase it was that as i figured this kind of falls into that category.
At the moment, I have d/l an old RUU.exe for jellybean after relocking my phone and that is currently installing although it is stuck on 7% ''Checking Header'' and has been for a while now. I dont expect it to move on any further.
One word.....gutted, wish I had left it alone now ffs
Click to expand...
Click to collapse
you need to chill and relax, you are now rushing things (aka panic mode), and you are going to get into trouble if you continue, let me when you are calm and relaxed.
apologies if that sounds not nice of me, but random flashing (including fixing something that doesn't need fixing), is not a good way to go.
I checked the updater-script of ARHD 7.0 for M8 and it probably hasn't touched any sensitive partitions on the m7
Take a break and come back, in a while, i'll post back
nkk71 said:
you need to chill and relax, you are now rushing things (aka panic mode), and you are going to get into trouble if you continue, let me when you are calm and relaxed.
apologies if that sounds not nice of me, but random flashing (including fixing something that doesn't need fixing), is not a good way to go.
I checked the updater-script of ARHD 7.0 for M8 and it probably hasn't touched any sensitive partitions on the m7
Take a break and come back, in a while, i'll post back
Click to expand...
Click to collapse
lol, yeah your right was in panic mode. I'm cool though, not touching it again until you tell me to hehehe. Im calm and relaxed. Just need reassurance that there will be a slim chance it can be fixed.
Let me know what you think when your ready mate, I appreciate the help a lot
terrypmarshall said:
lol, yeah your right was in panic mode. I'm cool though, not touching it again until you tell me to hehehe. Im calm and relaxed. Just need reassurance that there will be a slim chance it can be fixed.
Let me know what you think when your ready mate, I appreciate the help a lot
Click to expand...
Click to collapse
gimme 20 mins... kids want some attention before bed :laugh:
interesting side note though......When I plugged into usb and turned phone on, it is trying to download the drivers for HTC One_M8.......
fails, and also MTP USB Device driver download fails
terrypmarshall said:
interesting side note though......When I plugged into usb and turned phone on, it is trying to download the drivers for HTC One_M8.......
fails, and also MTP USB Device driver download fails
Click to expand...
Click to collapse
are you trying to boot the M8 ROM?? why??
so go back to TWRP 2.6.3.3 or 2.6.3.4 and completely format your phone:
To completely format the relevant partitions, you do the following in TWRP:
1) "Format Data", that will format /data and internal storage
2) Advanced Wipe -> /system and /cache, that will format /system and /cache
3) reboot to recovery
then follow the instruction here (though you should already be familiar with the FAQ sticky ) section 'D' to get the ROM onto your phone and install it: http://forum.xda-developers.com/showthread.php?p=53270352&postcount=21
nkk71 said:
are you trying to boot the M8 ROM?? why??
so go back to TWRP 2.6.3.3 or 2.6.3.4 and completely format your phone:
To completely format the relevant partitions, you do the following in TWRP:
1) "Format Data", that will format /data and internal storage
2) Advanced Wipe -> /system and /cache, that will format /system and /cache
3) reboot to recovery
then follow the instruction here (though you should already be familiar with the FAQ sticky ) section 'D' to get the ROM onto your phone and install it: http://forum.xda-developers.com/showthread.php?p=53270352&postcount=21
Click to expand...
Click to collapse
lol, no wasnt intentionally trying to boot the M8 rom, it was trying to do it itself. After the format data steps etc, I now have my system stuff back to normal (no longer states 0MB) couldn't mount with usb using recovery so cant drag and drop rom and install that way so currently trying to install using adb sideload.
If this works i will give you more kids rofl
failed to write data ' protocol fault (no data)
sigh......
oh well, its further than I have gotten all day thanks to you
btw....sorry for double posting all the time mods
you sir are a mod god.....used the push method and its installed the rom.
thank you so much for your help mate, i really do appreciate it. :laugh:

[SOLVED] Can't load RUU, no adb, fastboot remote not allowed

I'm truly stuck and could use your help guys. Here's the situation.
m7 Rogers canada edition.
No OS, no rom zips on the phone
Can't sideload because adb can't see the device
Fastboot often gives me an error when i try to flash an image
the phone boots into TWRP rather than attempting an OS
attempts at executing the RUU crashes the exe
I have NO idea how to get out of this.
My info
s-off
relocked
cid-roger001
I'm just trying to get back to stock at this point but nothing seems to work. Help me obi wan kinobi. you're my only hope.
With adb sideload, have a look in the device manager for 'one' and manually update the driver to the android device bridge driver.
craiglay said:
With adb sideload, have a look in the device manager for 'one' and manually update the driver to the android device bridge driver.
Click to expand...
Click to collapse
In device manager I only see My HTC under android devices, not ONE. ANd how do i update the drive to the adb driver? Where would i find that?
Thanks so much for getting back to me. Been on this for almost 24 hours and I have no idea how to fix this.
Thing is, the drivers were fine yesterday. So, somehow i don't think it's a driver thing. I think it's to do with somethign i messed up on the phone. I just reDLed the ADB + Fastboot + Drivers and I pointed the driver update to that folder (including subfolders) and windows says my drivers are up to date. Unless i should be selecting a specific file, i don't know if this solves my issue.
Nope, you were right. I now have adb access. So, what to do now? I'm afraid of trying to sideload cause that wasn't working before and I don't believe recovery is working. Somehow the phone think recovery is the OS. it boots into twrp but if i get into the bootloader and try to go into recovery, recovery won't load. So something's definitely wrong. Good thing is, i have adb now, so i'm sure i have more options, but if you could point me in the right direction, i'd really appreciate it.
Ugh. Actually, adb devices is still not listing my phone. WTF? I'm at a complete loss here.
adb/fastboot drivers from here
http://forum.xda-developers.com/showthread.php?t=2588979
and read here to get PC talking to phone
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Sent from my HTC One using XDA Premium 4 mobile app
thanks bored_stupid. I installed the ADB Installer v1.3 but still no go. List of devices remains blank when i run adb devices. the second link you posted, i don't really see anything that pertains to this issue. Am I missing something?
It's a FAQs. One will relate to your PC.
Sent from my HTC One using XDA Premium 4 mobile app
Ya, no, i know it's an FAQ, but it doesn't seem to cover the adb issue anywhere. At this point, i don't really care how i get back to stock whether via adb or fastboot or what, but as is, I have a completely bricked phone. I've done hours and hours of research, tried a whole slew of different things but nothing seems to work fastboot, adb and ruu.exe none of those options seem to be working. I have no external sd card that i could throw an img onto, so what options do i have here? Is there some other method you can think of that I could use to get the stock rom, hell or any rom onto this phone so i can at least have a proper recovery and OS installed? From there I'm sure i'll be able to get back to stock, but right now, as is, i am completely paralyzed. I appreciate your help man. THanks for taking the time.
vijn said:
Ya, no, i know it's an FAQ, but it doesn't seem to cover the adb issue anywhere. At this point, i don't really care how i get back to stock whether via adb or fastboot or what, but as is, I have a completely bricked phone. I've done hours and hours of research, tried a whole slew of different things but nothing seems to work fastboot, adb and ruu.exe none of those options seem to be working. I have no external sd card that i could throw an img onto, so what options do i have here? Is there some other method you can think of that I could use to get the stock rom, hell or any rom onto this phone so i can at least have a proper recovery and OS installed? From there I'm sure i'll be able to get back to stock, but right now, as is, i am completely paralyzed. I appreciate your help man. THanks for taking the time.
Click to expand...
Click to collapse
I think its more of a HTC one driver issue..
Download HTCSync. install then just delete HTCSync.. the drivers will remain..
I'm afraid if fastboot, adb or ruu's arent working, you have a driver issue or a completely bricked phone. Watch the device manager while you plug the phone into the computer. If you've enabled adb sideload in twrp, the device that appears needs to have the driver changed to android device bridge.
Installed Sync. Not sure how to delete it. You mean uninstall it? Either way, i closed htc sync, connected the phone. Ran adb devices and still list of devices attached is blank.
Is there no way you know of to completely wipe the phone, or use fastboot to install a rom or something. i can't even think clearly anymore. But i've been in worse situations with other phones, in terms of not even being able to turn the phone on, yet, I can't figure out what options i have left. Clearly, I'd love to get adb working, but i'm thinking maybe there's another way that I haven't considered. Though of course, as I mentioned, fastboot gives an error too most of the time. Thanks for following up.
craiglay said:
I'm afraid if fastboot, adb or ruu's arent working, you have a driver issue or a completely bricked phone. Watch the device manager while you plug the phone into the computer. If you've enabled adb sideload in twrp, the device that appears needs to have the driver changed to android device bridge.
Click to expand...
Click to collapse
Hey craig. When i connect the phone to the PC, My HTC (that's what it's called) shows up under Android USB Devices. I've tried updating the driver software. But I'm not sure how to change the driver to android device bridge. I assume you mean manually find a specific driver and install it, but what file am I looking for and where would i find it? I've installed a few driver packages and HTC sync. I can't imagine that i don't have the proper drivers installed, but I'm happy to try again if i know what i'm looking for.
Is 'my htc' happening in twrp? Ive seen it appear during boot before. To sideload, you need to boot into twrp, i think its in advanced then tap adb sideload.
Fastboot should be able to flash an ruu zip file from your desktop but i couldnt get it to work with 4.19.401.11. I got an error like 02 file too large..
vijn said:
Nope, you were right. I now have adb access. So, what to do now? I'm afraid of trying to sideload cause that wasn't working before and I don't believe recovery is working. Somehow the phone think recovery is the OS. it boots into twrp but if i get into the bootloader and try to go into recovery, recovery won't load. So something's definitely wrong. Good thing is, i have adb now, so i'm sure i have more options, but if you could point me in the right direction, i'd really appreciate it.
Click to expand...
Click to collapse
vijn said:
i can't even think clearly anymore.
Click to expand...
Click to collapse
Sorry, i know this is a pretty useless post, since I'm signing off, but:
1- post a "fastboot getvar all" (excluding IMEI and s/n)
2- a screenshot of your bootloader
3- How did you end up in this situation? did you "fastboot flash boot <name of recovery>.img"? what else did you flash?
and you sound kinda tired and fed up, may i recommend to take a break
Here's my getvar.
(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.631.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4324mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.071s
No idea how to get a SS of my bootloader, but here's what's written:
M7_UL PVT SHIP S-OFF RH
CID-ROGER001
HBOOT-1.57.0000
Radio-4T.27.3218.14
OpenDSP-v32.120.274.0909
OS-5.11.631.8
eMMC-boot 2048MB
May 9 2014,00:36:41.0
How i got into this? Hehe. I was on stock rooted and unlocked. I installed the latest network provided OTA. Then, I tried to get root back. From that point on, i really can't remember what happened. I was having issues with root, which i needed to get my backup root working. I read some research saying the latest OTA caused rooting issues. I then decided, why not try the GPE edition. Well, must have missed a step or something because from that point on, it was all downhill. I am fed up, but I rather just get this done to be honest. But thanks nkk.
@craiglay - My HTC is what's showing up in my device manager on my PC. I know i need to boot into TWRP to sideload, but it just doesn't work. Remember, i can't get into recovery from the bootloader. The only way to get into recovery is if i reboot and don't get into the bootloader. TWRP will boot up automatically instead of the OS (which is non-existant). I'd love to try to flash a RUU but i can't find a .zip version for the m7. Any chance you know where I can find one? In addition, i usually get a error: closed error when trying to flash via fastboot
Sorry, its been a long day, comprehension is failing!!
Try here for ruu zip files and instructions
Thanks craig but i"ve been there many times. Unfortunately all the RUUs are actually exe files. And when I try running the exe file, it crashes every time. http://forum.xda-developers.com/showthread.php?t=2428276 has some zipped RUUs but i'm not sure which i can use. And in fact, that's where I got the original GPE version. Thing is, even when i try to flash those, via fastboot, i get an error. ex:
F:\Downloads\Android\The ONE\FINAL ROOT&RECOVERY METHOD\HTCOneRoot>fastboot flash zip RUU-Zip-M7_Google-Edition_4.4_3.58.1700.5.zip
sending 'zip' (506183 KB)...
OKAY [ 21.294s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 21.800s
Or I'll get a remote: closed error.
I guess its because your CID is set to ROGER001 and not a Google Edition. I suggest running the ruu for your CID as it looks like you've tried to go to GE and missed a step. Edit: you've told me you have.. Its late..
There is a drop down box for zip files in downloads. I personally flashed a guru zip in twrp to return to stock.

Categories

Resources