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
Related
Hey!
So I just got my HTC One yesterday and I'm currently stock on the HTC logo boot screen. I spent the last 2 days on the internet trying to figure out how to fix that issues. It seems that the phone doesn't have any Rom or firmware install on it. I kind don't know how everything work. I don't mind if my phone is root or unroot all I want is to make it work. I followed different method on Youtube none of the seem to work. From what I know it seems that the device is a Rogers device but when I try to unroot it I got a 12 signature fail. Every other thread have broken links and kinda don't fix my issues. Please help me I'm really desperate.
Thank you,
Can you access the boot loader?
Is it locked or unlocked?
Do you have a custom recovery?
What were you trying to do when you got stuck in the bootloop?
The more info you can give us the more we can help.
Sent from my HTC One using XDA Premium 4 mobile app
Hey Cory!
Thanks for answering to my post.
To answer your question,
Yes I do have access to bootloader, fastboot and recovery.
I can use command on my pc to run some fastboot command also.
When I try to use recovery I got stuck at the red triangle alert.
I do not have any backup of my device. Also I dont have Cwm on the device.
It looks like a completely emptu phone. i cant even manage to use it as a disk mode to put a file on it.
I was only trying to unroot it to put back the android stock that came with the HTC One when you purchase it.
Also at the moment I'm able to unlock or lock the device.
Thanks for your help. i have to be honest I'm noob with android.
Thanks,
vedgebill said:
Hey Cory!
Thanks for answering to my post.
To answer your question,
Yes I do have access to bootloader, fastboot and recovery.
I can use command on my pc to run some fastboot command also.
When I try to use recovery I got stuck at the red triangle alert.
I do not have any backup of my device. Also I dont have Cwm on the device.
It looks like a completely emptu phone. i cant even manage to use it as a disk mode to put a file on it.
I was only trying to unroot it to put back the android stock that came with the HTC One when you purchase it.
Also at the moment I'm able to unlock or lock the device.
Thanks for your help. i have to be honest I'm noob with android.
Thanks,
Click to expand...
Click to collapse
can you go to fastboot, and then run "fastboot getvar all", and post the results here to see the details of your device (remove the IMEI and serial number before posting)
nkk71 said:
can you go to fastboot, and then run "fastboot getvar all", and post the results here to see the details of your device (remove the IMEI and serial number before posting)
Click to expand...
Click to collapse
Here's what I got
(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.631.17
(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: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4297mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Any Idea what I can do to make it work?
Thanks,
There's a Nandroid backup you can use here:
http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-roger001-1-29-631-17-2013-06-03-zip/
Can you help with a step by step how to restore?
There are guides on here already so just read them
EddyOS said:
There are guides on here already so just read them
Click to expand...
Click to collapse
Sorry I'm really bad with forums. Any guides in particular cuz I cant find the right one there too many.
Thanks I really appreciate
How about the nice, big, sticky thread in General?
http://forum.xda-developers.com/showthread.php?t=2358738
Search properly next time
So I manage to have clockworkmode on my HTC One.
I'm not stuck at the point of putting a firmware. I don't mind which one I just want my phone to work.
Bootloader is Unlocked.
When I plug the device to my computer I can't manage to put anything on it and dab doesn't seems to work properly.
I'm a noob so maybe I don't do it properly.
Thanks,
If you're a n00b why did you even attempt it in the first place? Surely you should know what you're doing before jumping in blind?
Actually the reason why I jump into it is cuz I got it from a friends for a couple of hundred dollar and it was like that.
I'm just trying to fix it and also try to understand and learn.
But thanks for the comment
If you manages to get cwm working you can adb push a ROM.
Download any stock ROM from the android development section of the One.
Android Revolution HD or InsertCoin are two favorites.
Put the .zip file in the same folder as your adb and fastboot files. I'm assuming you got adb and fastboot set up since you have cwm now, if not I can elaborate.
Rename the file rom.zip.
Open a command prompt in the folder that has adb and fastboot.
(Hold shift and right click, select open command prompt here)
Connect the phone while its booted into recovery.
Type "adb devices"
You should see your phones serial and the word recovery.
Now type "adb push rom.zip /sdcard/"
It will look like its frozen, leave it alone, it can take up to fifteen minutes or more.
Eventually it will tell you its done.
Unplug the phone and select full wipe or factory reset (inside cwm, not in the boot loader).
Also wipe both caches under advanced wipe.
Select flash or install from SD card, and pick ROM.zip.
Let it do its magic, or follow the prompts if it has an aroma installer. The more mods you choose, the farther from stock it will be, and the more likely it is to have bugs.
Good luck.
Sent from my HTC One using XDA Premium 4 mobile app
*** SOLVED - Problem was my own stupidity ***
Got the HTC One a couple of days ago. Came back to Android after a few months on iPhone. Figured I'd jump right back into rooting and flashing custom ROMs.
Anyway, unlocked the phone, wanted to install Android Revolution 51, tried to upgrade firmware, and that's when things went sideways. Now, I can't do anything. Can Fastboot, but can't ADB. Have tried to load every driver in the book, but to no avail. CID is CWS_001 if that helps. Have been at this for a day and a half now. I need ideas.
thoughts?
Does it get detected on your window device manager when you plug it in?
sent from my mobile device
SaHiLzZ said:
Does it get detected on your window device manager when you plug it in?
sent from my mobile device
Click to expand...
Click to collapse
Yes. It shows up under Android USB Devices and says "My HTC"
diceman725 said:
Yes. It shows up under Android USB Devices and says "My HTC"
Click to expand...
Click to collapse
Then you should be able to restore it with ADB... No idea how yet, but as far as I know your not completely dead here.... I may however be completely out to lunch here...
Iz3man said:
Then you should be able to restore it with ADB... No idea how yet, but as far as I know your not completely dead here.... I may however be completely out to lunch here...
Click to expand...
Click to collapse
Would be very grateful. I agree, it would seem logical that I could ADB my way out, but at the moment, ADB doesn't recognize the device.
It does sound more like a recognition issue than a hardware problem to me. Also, correct me if I'm wrong but wouldn't you be using fastboot rather than adb to get out of this situation? Adb is pretty much only usefull with a booted rom in my experience.
Sent from my HTC Desire using Tapatalk 2
Zedrox said:
It does sound more like a recognition issue than a hardware problem to me. Also, correct me if I'm wrong but wouldn't you be using fastboot rather than adb to get out of this situation? Adb is pretty much only usefull with a booted rom in my experience.
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
I don't have a ROM loaded in the Virtual SD. And unless I'm mistaken, I can really only use ADB sideload at this point to load one up
Can you get into basic HTC recovery on the phone? I'm assuming you can if you can get fastboot working.
If so can't you just reflash a actual recovery from there, and then a rom from that? Apologies if this is completely irrelevant, I base all my android knowledge off my Desire.
Sent from my HTC Desire using Tapatalk 2
Adb reboot
sent from my mobile device
Zedrox said:
It does sound more like a recognition issue than a hardware problem to me. Also, correct me if I'm wrong but wouldn't you be using fastboot rather than adb to get out of this situation? Adb is pretty much only usefull with a booted rom in my experience.
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
Yeah now it does. I know if windows can see it you should be OK.
Try adb reboot recovery or adb reboot bootloader
Right be able to get into something there.
Iz3man said:
Yeah now it does. I know if windows can see it you should be OK.
Try adb reboot recovery or adb reboot bootloader
Right be able to get into something there.
Click to expand...
Click to collapse
Problem is I can't get into ADB. It doesn't recognize the device. Going to try to flash a recovery and see if that works.
diceman725 said:
Problem is I can't get into ADB. It doesn't recognize the device. Going to try to flash a recovery and see if that works.
Click to expand...
Click to collapse
OK I'm lost here Can you boot into recovery? Or do you have a blank screen from the start?
Either way I hope you get it, its a pain when they do that!
Iz3man said:
OK I'm lost here Can you boot into recovery? Or do you have a blank screen from the start?
Either way I hope you get it, its a pain when they do that!
Click to expand...
Click to collapse
I can get into recovery, yes...
If you can boot to recovery, are you not able to boot to OS? How does it look dead??
sent from my mobile device
SaHiLzZ said:
If you can boot to recovery, are you not able to boot to OS? How does it look dead??
sent from my mobile device
Click to expand...
Click to collapse
There is no OS. Somehow I blew it away. When I get home I am going to try to flash a zipped RUU. Hopefully that works.
diceman725 said:
There is no OS. Somehow I blew it away. When I get home I am going to try to flash a zipped RUU. Hopefully that works.
Click to expand...
Click to collapse
No luck on flashing the RUU file. It sends successfully, but fails on the write.
You need to post an output of fastboot getvar all (imei /sn removed)
sent from my mobile device
also nearly bricked
..
Please make a new thread.
sent from my mobile device
SaHiLzZ said:
You need to post an output of fastboot getvar all (imei /sn removed)
sent from my mobile device
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(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: 4088mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
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?
I did a stupid thing: I unlocked my AT&T m7 (which I thought also made it S-OFF). I then installed a recovery and wiped the phone. After CM11 wouldn't install I realized that the phone was still S-ON. I have no OS on it to boot into. Any ideas on how I can get an HTC ROM on there so I can run the revone and grant it S-OFF? Thanks in advance!
Adam
niphoet said:
I did a stupid thing: I unlocked my AT&T m7 (which I thought also made it S-OFF). I then installed a recovery and wiped the phone. After CM11 wouldn't install I realized that the phone was still S-ON. I have no OS on it to boot into. Any ideas on how I can get an HTC ROM on there so I can run the revone and grant it S-OFF? Thanks in advance!
Adam
Click to expand...
Click to collapse
Well if you have a custom recovery, just flash any rom. Or did I misunderstand something?
aooga said:
Well if you have a custom recovery, just flash any rom. Or did I misunderstand something?
Click to expand...
Click to collapse
I can't transfer a ROM (CM11, Viper, etc) to the device. I can't get ADB sideload to work. I've installed the universal adb drivers and no dice.
niphoet said:
I can't transfer a ROM (CM11, Viper, etc) to the device. I can't get ADB sideload to work. I've installed the universal adb drivers and no dice.
Click to expand...
Click to collapse
Ah okay. When you connect your phone to your computer in recovery, what does "adb devices" give you? Nothing?
aooga said:
Ah okay. When you connect your phone to your computer in recovery, what does "adb devices" give you? Nothing?
Click to expand...
Click to collapse
Correct, I get nothing.
niphoet said:
Correct, I get nothing.
Click to expand...
Click to collapse
If even after re-flashing the TWRP.img it doesn't work, I would just do an RUU and go from there. Bad thing about not having an SD card slot
aooga said:
If even after re-flashing the TWRP.img it doesn't work, I would just do an RUU and go from there. Bad thing about not having an SD card slot
Click to expand...
Click to collapse
I've tried RUU but it keeps failing. Can you recommend a specific RUU to try?
niphoet said:
I've tried RUU but it keeps failing. Can you recommend a specific RUU to try?
Click to expand...
Click to collapse
Do you have Super cid or still the att one?
aooga said:
Do you have Super cid or still the att one?
Click to expand...
Click to collapse
I've tried:
RUU_M7_UL_JB_50_Cingular.exe
---and---
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe
niphoet said:
I've tried:
RUU_M7_UL_JB_50_Cingular.exe
---and---
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe
Click to expand...
Click to collapse
This one seems to work for everyone I give it to.
http://androidruu.com/getdownload.p...13_10.38j.1157.04_release_334235_signed_2.exe
aooga said:
This one seems to work for everyone I give it to.
http://androidruu.com/getdownload.p...13_10.38j.1157.04_release_334235_signed_2.exe
Click to expand...
Click to collapse
I'll try it and report back in the morning. Thanks for all the help so far!
niphoet said:
I'll try it and report back in the morning. Thanks for all the help so far!
Click to expand...
Click to collapse
Sure.
---------- Post added at 08:57 PM ---------- Previous post was at 08:54 PM ----------
niphoet said:
I'll try it and report back in the morning. Thanks for all the help so far!
Click to expand...
Click to collapse
Just to let you know, that rom is pretty old. You'll need to do some updating. If you don't want to do that, you can also download this one :
DOWNLOAD
But it might not work. It's worth a try though.
aooga said:
Sure.
---------- Post added at 08:57 PM ---------- Previous post was at 08:54 PM ----------
Just to let you know, that rom is pretty old. You'll need to do some updating. If you don't want to do that, you can also download this one :
DOWNLOAD
But it might not work. It's worth a try though.
Click to expand...
Click to collapse
Neither of those worked. Here is the error I get: Link.
I guess my next step is to try to find my otg cable and try to load a rom from there, right?
------
EDIT:
I managed to get adb working in recovery using a 32-bit VM (I now remember the problems I've had in the past with x64 and adb). I installed Viper, used rumrunner to achieve S-OFF. I am still unable to flash cm11. PhilZ/CWM gives me Status 0 and TWRP just says failed. Any idea what my next step should be?
ANOTHER EDIT:
Okay, I'm able to install an older m7att build but i can't install any of the unified m7 roms.
Have you got fastboot working?
http://koush.com/post/universal-adb-driver
Read here...
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Post a fastboot getvar all when working
Sent from my Nexus 7 using XDA Premium 4 mobile app
niphoet said:
Neither of those worked. Here is the error I get: Link.
I guess my next step is to try to find my otg cable and try to load a rom from there, right?
------
EDIT:
I managed to get adb working in recovery using a 32-bit VM (I now remember the problems I've had in the past with x64 and adb). I installed Viper, used rumrunner to achieve S-OFF. I am still unable to flash cm11. PhilZ/CWM gives me Status 0 and TWRP just says failed. Any idea what my next step should be?
ANOTHER EDIT:
Okay, I'm able to install an older m7att build but i can't install any of the unified m7 roms.
Click to expand...
Click to collapse
You should be able to install any rom. Try flashing TWRP again? Whats the exact error in TWRP.
bored_stupid said:
Have you got fastboot working?
http://koush.com/post/universal-adb-driver
Read here...
http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Post a fastboot getvar all when working
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT36LW912065
(bootloader) imei: 354439051648014
(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: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.240s
aooga said:
You should be able to install any rom. Try flashing TWRP again? Whats the exact error in TWRP.
Click to expand...
Click to collapse
I tried TWRP 2.6.3.3 and 2.7.0.0. Here is the error in TWRP: Link
EDIT: See this. Under the section "Recovery Update" I flashed the unofficial TWRP 2.7.0.8 and it flashed the latest nightly. I guess I'm good to go now. Thanks to all for all of the help!!
niphoet said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
......!!
Click to expand...
Click to collapse
Just to let you know, the error when it says "Too many links" happens when you use a USB 3 port. Android and adb don't play very nice with usb 3.
hi, im trying to get my htc one m7sprint back to stock. I haven't used it recently and am thus very confused on how to get back to stock recovery and rom.
heres's some information about the phone
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.00.20.0913_3
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.04.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Mod Edit
(bootloader) imei: Mod Edit
(bootloader) meid: Mod Edit
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4102mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-371c4f408e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Mod Edit = removed sensitive material
Easiest way would be to RUU...they can be found in Android Development, use 3.04.651.2 or higher.
when you say use 3.04 or higher could you tell me if this would work?
http://forum.xda-developers.com/showthread.php?t=2250904
I don't see a version number in this one
amskhan1 said:
when you say use 3.04 or higher could you tell me if this would work?
http://forum.xda-developers.com/showthread.php?t=2250904
I don't see a version number in this one
Click to expand...
Click to collapse
That one is older(version 1.29.651.10) then what you are currently on...so no you cannot use it.
This one matches what you are currently on.
http://forum.xda-developers.com/showthread.php?t=2508907
The higher the number the newer it is.
They can all be found HERE.
Hi, im having trouble running the ruu i'm getting the 170 error and my phone is still in fastboot usb mode. also when i try to reboot the phone into normal android it goes straight into bootloader. Do you know how to solve these problems? i found this information online, but i don't know how to get the drivers considering my phone is stuck in fastboot and isnt rebooting
https://sites.google.com/site/communityhelpsareebro/how-to-fix-error-170-usb-connection-error
amskhan1 said:
Hi, im having trouble running the ruu i'm getting the 170 error and my phone is still in fastboot usb mode. also when i try to reboot the phone into normal android it goes straight into bootloader. Do you know how to solve these problems? i found this information online, but i don't know how to get the drivers considering my phone is stuck in fastboot and isnt rebooting
https://sites.google.com/site/communityhelpsareebro/how-to-fix-error-170-usb-connection-error
Click to expand...
Click to collapse
Try installing HTC Sync Manager it will install drivers needed.
Once it's installed you no longer need it so you can uninstall from your PC if you wish.
BD619 said:
Try installing HTC Sync Manager it will install drivers needed.
Once it's installed you no longer need it so you can uninstall from your PC if you wish.
Click to expand...
Click to collapse
thanks
Hey im, still getting error 170, with ruu version 2.0.5.2013. I already installed htc sync manager. I get to the part where it says verifying info on your pda phone.... please wait.
but after that it says error 170, usb connection error.
My phone is tagged with ****tampered*** , relocked, and security warning
Do you have any suggestions. (I have another htc one if i need to install some driver on my pc.
When i start my phone it only boots into bootloader. do i need an os on the phone for this?
amskhan1 said:
Hey im, still getting error 170, with ruu version 2.0.5.2013. I already installed htc sync manager. I get to the part where it says verifying info on your pda phone.... please wait.
but after that it says error 170, usb connection error.
My phone is tagged with ****tampered*** , relocked, and security warning
Do you have any suggestions. (I have another htc one if i need to install some driver on my pc.
When i start my phone it only boots into bootloader. do i need an os on the phone for this?
Click to expand...
Click to collapse
Only other things I can suggest are...
Make sure you are using the latest RUU.
Try a different cable OEM is best.
Try a different USB port (USB2 work the best).
Try a different PC.
BD619 said:
Only other things I can suggest are...
Make sure you are using the latest RUU.
Try a different cable OEM is best.
Try a different USB port (USB2 work the best).
Try a different PC.
Click to expand...
Click to collapse
kk thnx I'll try it
another question
amskhan1 said:
kk thnx I'll try it
Click to expand...
Click to collapse
I finally got the ruu to recognize my device, but it says from image version(3.04.651.2) to : image version then its just blank.
Is there supposed to be something there?
amskhan1 said:
I finally got the ruu to recognize my device, but it says from image version(3.04.651.2) to : image version then its just blank.
Is there supposed to be something there?
Click to expand...
Click to collapse
Yeah the version number of the RUU you are trying to flash.
Maybe you are using an older RUU?
I think i was using the 3_04_651_2 one that you suggested.
amskhan1 said:
I think i was using the 3_04_651_2 one that you suggested.
Click to expand...
Click to collapse
That one should work just fine...did you proceed and get an error or just stop when you saw the missing version?
BD619 said:
That one should work just fine...did you proceed and get an error or just stop when you saw the missing version?
Click to expand...
Click to collapse
I just stopped when i saw a missing version, didn't know if it would break the phone, so i should continue?
amskhan1 said:
I just stopped when i saw a missing version, didn't know if it would break the phone, so i should continue?
Click to expand...
Click to collapse
Yeah give it a shot.