*** 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
Related
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
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
I have had my HTC ONE for about 5 months now and as soon as i got the phone i rooted it and installed Teamwin's recovery program. Today i got a notification that there is a system update (4.4.2). What steps do i need to take for updating this phone considering that its rooted and has Teamwins recovery program?
BlockABoots said:
I have had my HTC ONE for about 5 months now and as soon as i got the phone i rooted it and installed Teamwin's recovery program. Today i got a notification that there is a system update (4.4.2). What steps do i need to take for updating this phone considering that its rooted and has Teamwins recovery program?
Click to expand...
Click to collapse
if you have made no changes to the OS just install the stock recovery for your os version.
Stock recovery's
if your using custom roms you need to RUU back to stock then take the update
find your RUU here >> http://www.androidruu.com/index.php?developer=M7
use fastboot getvar all to find your phones information
Ok have used adb and this if my phones info......
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3************
(bootloader) imei: 354***************
(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: 3868mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.060s
What stock recovery image do i need to use? from the link you sent me above, recovery 2.24.401.8.img??
Will i lose all the data on my phone installing the stock recovery??
BlockABoots said:
Ok have used adb and this if my phones info......
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3**********
(bootloader) imei: 354**************
(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: 3868mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.060s
What stock recovery image do i need to use? from the link you sent me above, recovery 2.24.401.8.img??
Will i lose all the data on my phone installing the stock recovery??
Click to expand...
Click to collapse
Edit your previous post and remove serial no and IMEI
yes that's the recovery you need and no it won't erase your phone
clsA said:
Edit your previous post and remove serial no and IMEI
yes that's the recovery you need and no it won't erase your phone
Click to expand...
Click to collapse
Thanks for the pointer.
So these are the steps i need to do:
1. Download 'recovery 2.24.401.8.img'
2. Rename 'recovery 2.24.401.8.img' to 'recovery.img'
3. Place 'recovery.img' in my adb/fastboot folder (C:\Adb)
4. Open Command Prompt and navigate to your adb folder
5. Type 'adb reboot bootloader' to get into fastboot on the HTC ONE
6. And then flash the recovery img by typing 'fastboot flash recovery recovery.img'
Is the above all correct?
Yep that's it
Sent from my HTC One using Tapatalk
uarbie
clsA said:
Yep that's it
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
OK thanks, it doesnt matter than i have S-ON then?
After i type, 'fastboot flash recovery recovery.img'
its says, 'waiting for device' and just sits there, any ideas why this happens?
probably drivers.
check device manager and make sure you have a proper driver loaded
fastboot devices should show your device.
If your on windows 8/8.1 it has trouble with fastboot on older hboot versions. ADB works fine but fastboot doesn't work. I think newer hboot's resolve this so it will work after the update.
Might need to just use a win7 pc or VM to flash stock recovery.
BlockABoots said:
OK thanks, it doesnt matter than i have S-ON then?
After i type, 'fastboot flash recovery recovery.img'
its says, 'waiting for device' and just sits there, any ideas why this happens?
Click to expand...
Click to collapse
ipfreelytech said:
probably drivers.
check device manager and make sure you have a proper driver loaded
fastboot devices should show your device.
If your on windows 8/8.1 it has trouble with fastboot on older hboot versions. ADB works fine but fastboot doesn't work. I think newer hboot's resolve this so it will work after the update.
Might need to just use a win7 pc or VM to flash stock recovery.
Click to expand...
Click to collapse
Ah yeah i am on Windows 8.1. I'll have to use my laptop then. What drivers do i need to be downloading?
Also can 4.4.2 be rooted yet?
I use the universal naked driver pack and usually just choose google nexus bootloader interface for the driver.
Sure, you root it the same as anything else: unlock bootloader, flash cwm/twrp recovery, flash SuperSU.zip
BlockABoots said:
Ah yeah i am on Windows 8.1. I'll have to use my laptop then. What drivers do i need to be downloading?
Also can 4.4.2 be rooted yet?
Click to expand...
Click to collapse
ipfreelytech said:
probably drivers.
check device manager and make sure you have a proper driver loaded
fastboot devices should show your device.
If your on windows 8/8.1 it has trouble with fastboot on older hboot versions. ADB works fine but fastboot doesn't work. I think newer hboot's resolve this so it will work after the update.
Might need to just use a win7 pc or VM to flash stock recovery.
Click to expand...
Click to collapse
ipfreelytech said:
I use the universal naked driver pack and usually just choose google nexus bootloader interface for the driver.
Sure, you root it the same as anything else: unlock bootloader, flash cwm/twrp recovery, flash SuperSU.zip
Click to expand...
Click to collapse
Ok have managed to flash the stock recovery back to the phone, and have update to 4.4.2. But when i turned the phone back on i had to go through all the setup process and now all my contact and text messages and apps have gone!!. I though i wasnt going to lose all my data?
Your bootloader was already unlocked? or was it locked and you just unlocked it? When you perform a bootloader unlock it does wipe the data as a "safety measure".
BlockABoots said:
Ok have managed to flash the stock recovery back to the phone, and have update to 4.4.2. But when i turned the phone back on i had to go through all the setup process and now all my contact and text messages and apps have gone!!. I though i wasnt going to lose all my data?
Click to expand...
Click to collapse
ipfreelytech said:
Your bootloader was already unlocked? or was it locked and you just unlocked it? When you perform a bootloader unlock it does wipe the data as a "safety measure".
Click to expand...
Click to collapse
It should of already been unlocked, as it was rooted and had TWRP install previously
So theres no way for me to get this stuff back then, pictures, messages, contacts etc?
Um, there's some missing information here.
Short answer, if you in fact "unlocked" the phone recently, you wiped all personal data and there is absolutely no way to go back.
There are other ways data can get erased however.
As you pointed out, the phone was likely unlocked previously. Not sure how it would have become relocked forcing you to unlock again, which you don't seem to remember doing anyway.
Also you didn't originally say you lost your pictures. Did you or didn't you? Losing texts and contacts is normal when flashing a ROM. There are backup apps for texts and most people keep their contacts in the cloud do you normally just resync and you're done.
But pictures is something else. Sounds like someone did a factory reset and/or formatted the entire /data partition in recovery.
Normally most recoveries know that when you "format" data, you are really just selectively erasing everything in /data *except* /data/media. You don't usually do an actual format. The stock recovery does not make this distinction, and even custom recoveries often have an advanced features that lets you truly format all of /data. So you might have nuked your pictures in recovery somehow, no unlocking necessary.
You need to go into more detail.
But if you are saying your pictures are gone, they're probably totally gone.
One last possibility, the version-main you posted suggests you may have been using android 4.2 originally.
But I suppose it's possible the original ROM you were using was actually 4.1. Maybe your stuff was at the top level of /data/media and never got moved to /data/media/0
This surprised quite a few people during the transition from Android 4.1 to 4.2
So *if* you didn't unlock *and* didn't totally format everything *and* your old ROM was 4.1, well.. get a file browser and have a look around. Maybe you got lucky.
Sent from my HTC One using xda app-developers app
Well before i flashed the recovery image bootloader had 'Tampered' and 'unlocked' listed at the top of the sceeen, just like it does now so im not really sure what happened. But as soon as i flashed the 'recovery 2.24.401.8.img' back onto my phone and then downloaded the 4.4.2 system update and installed it, when the phone restarted again it was like it was back to factory default in that i had to go through the whole setup screens!, so not sure whats happened.
But on closer inspection even though i have downloaded and installed system update 4.4.2, if i go in settings>about>Software information> it says im on Android version 4.3 and software number 3.62.401.1, isnt this wrong as ive updated to 4.4.2???
You have two separate issues here. You lost your data and you're not running 4.4.2
Apparently you're not worried about your data.
To get 4.4.2 you either need to a) get to a place that is so "stock" that OTA's will take you the rest of the way or b) manually flash a 4.4.2 ROM. The b) option usually requires S-OFF and a suitably recent recovery compatible with KitKat.
If you are already S-OFF of course b) is way simpler. But you're not. In fact you have HBOOT 1.56 which can make S-OFF less certain. If you can get S-OFF that's the way I would go. I personally never screw around chasing OTA's.
You may be in an awkward place right now.
Time for someone with more patience than me to get involved I guess.
Sent from my HTC One using xda app-developers app
No please don't get me wrong I am certainly worried about my lost data, especially the pictures, but from what you said I there's no real way to recover them, is that correct or is there a way at all?
Probably gone, but I would still use adb shell or a file explorer app to look in
/data/media
Your most recent personal data (the stuff you made in the last day or two, not the lost files you are looking for) will be in
/data/media/0
You're checking to see if there is useful stuff *outside* the " 0 " folder.
Don't delete anything unfamiliar (for instance if you see clockworkmod, leave that alone -it's nandroid backups). Just look for orphaned folders full of personal stuff like "DCIM" or " Music" or whatever.
Sent from my HTC One using xda app-developers app
NxNW said:
Probably gone, but I would still use adb shell or a file explorer app to look in
/data/media
Your most recent personal data (the stuff you made in the last day or two, not the lost files you are looking for) will be in
/data/media/0
You're checking to see if there is useful stuff *outside* the " 0 " folder.
Don't delete anything unfamiliar (for instance if you see clockworkmod, leave that alone -it's nandroid backups). Just look for orphaned folders full of personal stuff like "DCIM" or " Music" or whatever.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Sadly there is nothing in /data/media there are 3 folder, 0, legacy. obb and a file .htc_layout_version none hold any of my old photos . I have even tried the program, Wondershare Dr.Fone and that doesnt find any of my old photos either...so i guess there lost for ever, bugger.
I guess i need to get this phone back to stock and then try the update and see if it takes this time?, so ill need to remove the root, TWRP recovery and SuperSU?
Yesterday, I attempted to install a new rom. I had been using CM11 nightlies up till this point, and after being annoyed about certain aspects of my phone not working. I wanted to try something new.
I found ViperOne, and went to install it, thinking that it'll be the standard, run-of-the-mill install with no problems to be had. After getting through the install procedure and attempting to reboot to system, my phone dropped me back off at the bootloader. Thinking that I had forgotten to wipe something, I went into the recovery, wiped data, dalvik cache, and the cache, and attempted the install again. Once again, my phone dropped me off at the bootloader.
I thought, maybe I had a bad download. Re-downloaded the rom, same result. "Oh, I'll just try something else then". I found a Google Play Edition rom for my device, and decided to try that. It got stuck in a bootloop. After some googling, I attempted wiping the data/cache/dalvik cache again hoping it would help. Nope, still stuck in bootloop.
At this point (and after having running into a very similiar situation before) I decided to go for broke. I did a full wipe of the phone, and sideloaded CM10.1.3 (only stable CM rom for this device afaik). As it was installing, I noticed an error. "Unable to mount /data". I've had this problem before, and the way I fixed it last time was to install and run a stock rom. At this point in time, I was also getting frustrated and decided to put the stock rom back on my phone so it would at least be functional.
I found a stock rom and installed it just fine. The phone didn't even get stuck in a bootloop either. However, once the phone had finally booted up, I found that the touchscreen was unresponsive. I remember having this issue the last time I tried to use a stock rom. After a little bit of research, I had found that the problem stems from installing the wrong version of the rom. It was suggested on one of the websites to put "fastboot getvar version-main" into adb to find out what version I needed. It returns "version-main: ".
It was at this point that I remembered that I had made a backup of my phone before I attempted rooting. After some searching around, I managed to find it. That being said, I have no idea what to do with it. The folder where I made the backup contains a handful of .win files and some md5 checksums.
Since then I have been attempting seemingly random RUU versions in hopes of stumbling across the right one. It's been 5 hours, and I haven't had any success.
I would greatly appreciate any and all help that can be provided. If you guys need additional information (I'm not sure what I should include), let me know. I know some of the more basic ADB commands and their functions, so bear with me if I ask some questions about how to do certain things.
Boot into bootloader/fastbootusb and type the below command and post the readout here.
fastboot getvar all
BD619 said:
Boot into bootloader/fastbootusb and type the below command and post the readout here.
fastboot getvar all
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4323mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-005bf6a40e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
You can try one of the RUU's found here or follow the guide
Sidenote: don't use the 4.06.651.4 RUU unless you flash the 4.06.651.4 s-on firmware first.
BTW I removed
serialno:
imei:
meid:
BD619 said:
You can try one of the RUU's found here or follow the guide
Sidenote: don't use the 4.06.651.4 RUU unless you flash the 4.06.651.4 s-on firmware first.
Click to expand...
Click to collapse
I've tried several different RUU's, including the one's I could find here, and none of them have worked. Not sure if it really matters, but I attempted the 4.06.651.4 RUU earlier, but it failed.
BD619 said:
BTW I removed
serialno:
imei:
meid:
Click to expand...
Click to collapse
Why shouldn't those be shared? Are they considered sensitive information?
Ooops for got the link
http://forum.xda-developers.com/showthread.php?t=2503646
Yes they could be considered sensitive.
BD619 said:
Yes they could be considered sensitive.
Click to expand...
Click to collapse
I have no idea what those numbers represent. Why are important?
crazy-asian said:
I have no idea what those numbers represent. Why are important?
Click to expand...
Click to collapse
I have always been told not to include those...could be a way for someone to hack your device but that's just my guess.
http://en.wikipedia.org/wiki/Mobile_equipment_identifier
I had this happen to me also. Ends up i had to flash a new firmware on the phone and it booted right up. Also make sure you are using twrp recovery when you flash this rom. I used cwm and think that is where all my problems started. Hope ya get it worked out and may not be your problem but is exactly what happened to me and have i fixed it.
BD619 said:
http://forum.xda-developers.com/showthread.php?t=2503646
Click to expand...
Click to collapse
I had tried all but one of those in that list. That one that I hadn't used yet appears to be working. Thank you so much for the help.
Oh god, now I'm back on the stock rom... Any recommendations for a good rom? I enjoy the stock look and feel of android, but running the CM nightlies has been giving me a headache.
crazy-asian said:
Oh god, now I'm back on the stock rom... Any recommendations for a good rom? I enjoy the stock look and feel of android, but running the CM nightlies has been giving me a headache.
Click to expand...
Click to collapse
I'm running BadSeed Sixth Sense
But it's all personal preference everyone will have a different opinion.
Fastboot, on the phone side, isn't connecting to my computer.
crazy-asian said:
Fastboot, on the phone side, isn't connecting to my computer.
Click to expand...
Click to collapse
Are you in bootloader?
BD619 said:
Are you in bootloader?
Click to expand...
Click to collapse
Yes, and it is in fastboot mode.
crazy-asian said:
Yes, and it is in fastboot mode.
Click to expand...
Click to collapse
When you type fastoot devices you don't get a response?
BD619 said:
When you type fastoot devices you don't get a response?
Click to expand...
Click to collapse
correct
crazy-asian said:
correct
Click to expand...
Click to collapse
Ok go back to my guide and you can get the proper drivers and instructions to get them installed correctly
BD619 said:
Ok go back to my guide and you can get the proper drivers and instructions to get them installed correctly
Click to expand...
Click to collapse
Didn't solve the problem, phone still isn't in "fastboot USB"
crazy-asian said:
Didn't solve the problem
Click to expand...
Click to collapse
Try a different port(usb2 are best)
Try a different cable
Different PC
If you have android sdk setup try updating it.
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.