Related
I have been reading and trying to get this figured out for a few days now. I have an HTC one from Bell Mobility that won't boot up. It is S-ON and there does not seem to be an RUU for the Bell variant.
I am looking for a way to set S-ON so I can install CWM and flash the nandroid backup that I did find..
The phone's battery went dead last week and it would not boot after that. The first htc splash screen(white) has bars horizontal at the bottom and then the HTC logo with the beats logo at the bottom just hangs on the phone.
I can get to download mode and fastboot works. Adb doesn't work(but I think that is because it never boots into android)
How can I fix this thing? it isn't under warranty, I bought it used..
Oh, I have done factory reset, tried recovery mode, rebooted many many times, tried everything I came across...
Any ideas? I am at the end of my rope!
cdn_traveller said:
I have been reading and trying to get this figured out for a few days now. I have an HTC one from Bell Mobility that won't boot up. It is S-ON and there does not seem to be an RUU for the Bell variant.
I am looking for a way to set S-ON so I can install CWM and flash the nandroid backup that I did find..
The phone's battery went dead last week and it would not boot after that. The first htc splash screen(white) has bars horizontal at the bottom and then the HTC logo with the beats logo at the bottom just hangs on the phone.
I can get to download mode and fastboot works. Adb doesn't work(but I think that is because it never boots into android)
How can I fix this thing? it isn't under warranty, I bought it used..
Oh, I have done factory reset, tried recovery mode, rebooted many many times, tried everything I came across...
Any ideas? I am at the end of my rope!
Click to expand...
Click to collapse
First off try force reboot:
Press and hold POWER + VOL DOWN (under a bright light), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)
Can you post a fastboot getvar all
Is your bootloader unlocked?
Sent from my HTC One using Xparent Skyblue Tapatalk 2
I unlocked my bootloader from the HTC website. Here is a getvar. I removed the serial and IMEI.
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4A.23.3263.28
version-cpld: None
version-microp: None
version-main: 4.19.666.8
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: BM___001
battery-status: good
battery-voltage: 4215mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4dab9d12
hbootpreupdate: 11
gencheckpt: 0
To get that, I had to go to fastboot on the screen with the diagnostics info on it that says HBOOT and allows fastboot, recovery, factory reset, etc...
I appreciate the help, I am getting frustrated
bored_stupid said:
First off try force reboot:
Press and hold POWER + VOL DOWN (under a bright light), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)
Can you post a fastboot getvar all
Is your bootloader unlocked?
Sent from my HTC One using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
cdn_traveller said:
To get that, I had to go to fastboot on the screen with the diagnostics info on it that says HBOOT and allows fastboot, recovery, factory reset, etc...
I appreciate the help, I am getting frustrated
Click to expand...
Click to collapse
HBOOT screen is your bootloader and that is where fastboot commands are run from.
Adb only works within a working os or in recovery.
I am looking for a way to set S-ON so I can install CWM and flash the nandroid backup that I did find..
.
S-On/S-Off has nothing to do with flashing a recovery, only bootloader has to be unlocked , so....
Enter bootloader
Connect phone to PC.
Put the CWM recovery in your fastboot/adb folder.
Press shilft and right mouse
Scroll down to....
Open command prompt
Then fastboot devices
Once some numbers are shown
fastboot flash recovery filename.img
( filename is name of recovery)
fastboot erase cache
fastboot reboot-bootloader
Scroll down to recovery and press power
You should now be able to restore your backup.
PS. If your S-Off. Stay S-Off.. it can sometimes be your only hope of restoring a bricked phone.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Click to expand...
Click to collapse
[Q] AT&T HTC One M7 soft-bricked. Fastboot works, can't boot to recovery [Concluded]
Wondering if I can get somebody to weigh in on this one. Trying to help a friend of a friend out--I don't know the back story of what happened to this, but sounded like a 'bricked his phone doing dangerous things without enough knowledge' kind of situation.
The phone is stuck in a boot loop, just the HTC wordmark on a white background. You can enter the bootloader just fine, and fastboot can read and send commands just fine, flash recovery just fine, etc. The device cannot, however, enter recovery mode. It just says "entering recovery..." at the top, with the same HTC wordmark and white background. It displays for 30 seconds, then the screen goes black for 4-5 seconds, then back to the HTC logo.
Some info about the phone:
AT&T HTC One M7
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.19.3263.13
version-cpld: None
version-microp: None
version-main: 3.17.502.3
version-misc: PVT SHIP S-ON
serialno: [redacted]
imei: [redacted]
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 3838mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-2da61e5e88
hbootpreupdate: 11
gencheckpt: 0
Things I have tried already:
The first thing I did was I re-locked the bootloader and flashed the RUU exe, thinking that might be the quickest fix. The exe took the expected length of time and said it was successful, and rebooted the phone.
Still looping.
I then got the unlock token, unlocked the bootloader again, erased the cache, and fastboot flashed CWM recovery-clockwork-6.0.4.3-m7att.img - Attempted to reboot to recovery.
Still looping.
Cleared the cache, flashed openrecovery-twrp-2.7.1.1-m7.img - Attempted to reboot to recovery.
Still looping.
What's Next?
So that's about where I am now, I have functional bootloader and fastboot, but something is corrupted and I just absolutely can't get into recovery no matter what I try. I really thought the RUU would be a simple way to fix it, and was surprised when it didn't work.
From the reading I've done it sounds like there's some sort of emmc partition corruption possibly? Am I going in the right direction? I did post the fastboot getvar all results above--perhaps that can tip somebody off? I don't know quite enough to be able to spot trouble there at a glance, unfortunately.
I don't personally have a lot invested in getting this running, its owner already replaced it and I'm just doing it for the fun and challenge of the learning experience. But I may be out of my depth at this point, I've exhausted my barely-passable knowledge when it comes to this stuff.
Thanks for any comments or guidance you can provide!
Thanks to all for your help. I've come to believe the issues were hardware related, and have returned the phone.
matt314159 said:
Wondering if I can get somebody to weigh in on this one. Trying to help a friend of a friend out--I don't know the back story of what happened to this, but sounded like a 'bricked his phone doing dangerous things without enough knowledge' kind of situation.
The phone is stuck in a boot loop, just the HTC wordmark on a white background. You can enter the bootloader just fine, and fastboot can read and send commands just fine, flash recovery just fine, etc. The device cannot, however, enter recovery mode. It just says "entering recovery..." at the top, with the same HTC wordmark and white background. It displays for 30 seconds, then the screen goes black for 4-5 seconds, then back to the HTC logo.
Some info about the phone:
AT&T HTC One M7
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.19.3263.13
version-cpld: None
version-microp: None
version-main: 3.17.502.3
version-misc: PVT SHIP S-ON
serialno: [redacted]
imei: [redacted]
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 3838mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-2da61e5e88
hbootpreupdate: 11
gencheckpt: 0
Things I have tried already:
The first thing I did was I re-locked the bootloader and flashed the RUU exe, thinking that might be the quickest fix. The exe took the expected length of time and said it was successful, and rebooted the phone.
Still looping.
I then got the unlock token, unlocked the bootloader again, erased the cache, and fastboot flashed CWM recovery-clockwork-6.0.4.3-m7att.img - Attempted to reboot to recovery.
Still looping.
Cleared the cache, flashed openrecovery-twrp-2.7.1.1-m7.img - Attempted to reboot to recovery.
Still looping.
What's Next?
So that's about where I am now, I have functional bootloader and fastboot, but something is corrupted and I just absolutely can't get into recovery no matter what I try. I really thought the RUU would be a simple way to fix it, and was surprised when it didn't work.
From the reading I've done it sounds like there's some sort of emmc partition corruption possibly? Am I going in the right direction? I did post the fastboot getvar all results above--perhaps that can tip somebody off? I don't know quite enough to be able to spot trouble there at a glance, unfortunately.
I don't personally have a lot invested in getting this running, its owner already replaced it and I'm just doing it for the fun and challenge of the learning experience. But I may be out of my depth at this point, I've exhausted my barely-passable knowledge when it comes to this stuff.
Thanks for any comments or guidance you can provide!
Click to expand...
Click to collapse
Try to download TWRP 2.6.3.3 from here http://techerrata.com/browse/twrp2/m7 . When it has downloaded put it in your fastboot folder, plug your phone into your computer, open a command window, and type "fastboot devices" to make sure it recognizes your phone. If it doesn't you will need the drivers, if it does recognize it type "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img" . That is the same file and procedure I just used a week ago, hope it helps you.
chuckwago88 said:
Try to download TWRP 2.6.3.3 from here http://techerrata.com/browse/twrp2/m7 . When it has downloaded put it in your fastboot folder, plug your phone into your computer, open a command window, and type "fastboot devices" to make sure it recognizes your phone. If it doesn't you will need the drivers, if it does recognize it type "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img" . That is the same file and procedure I just used a week ago, hope it helps you.
Click to expand...
Click to collapse
Thanks for the suggestion, but it's still no joy: TWRP 2.6.3.3 acts the same as TWRP 2.7.1.1 and CWM 6.0.4.3
I'm starting to think this thing is toast.
matt314159 said:
Thanks for the suggestion, but it's still no joy: TWRP 2.6.3.3 acts the same as TWRP 2.7.1.1 and CWM 6.0.4.3
I'm starting to think this thing is toast.
Click to expand...
Click to collapse
I noticed that you have 3.17.502.3 firmware, you might try to flash this RUU 4.18.502.7 it is a higher version and might correct what I suspect is a mismatch between your version and the hboot. If this is successful, you might think about this AT&T 5.12.502.2 Guru Reset. Read the entire OP for both, it might give you some insight.
Hmm... With this RUU, I get as far as "Updating 1/5 Checking headers" at 5% and never any further. Thought I might just need to be more patient, so I left it through three episodes of Trailer Park Boys season 8, and a subsequent afternoon nap before powering off the handset and killing the windows process. Tried it again and it seems to be doing the same thing. The MD5 matched so I don't think it was a bad download, so I wonder if there are any workarounds.
I'm running windows 7 x64, have the proper drivers installed, HTC Sync has been removed, and I've used this PC successfully on another HTC One when I needed to get it back to factory stock to send in for warranty work just a couple of weeks ago. So I'm pretty sure it's nothing to do with my setup...
Can you find the same firmware (or extract from ota) and flash it?
matt314159 said:
Hmm... With this RUU, I get as far as "Updating 1/5 Checking headers" at 5% and never any further. Thought I might just need to be more patient, so I left it through three episodes of Trailer Park Boys season 8, and a subsequent afternoon nap before powering off the handset and killing the windows process. Tried it again and it seems to be doing the same thing. The MD5 matched so I don't think it was a bad download, so I wonder if there are any workarounds.
I'm running windows 7 x64, have the proper drivers installed, HTC Sync has been removed, and I've used this PC successfully on another HTC One when I needed to get it back to factory stock to send in for warranty work just a couple of weeks ago. So I'm pretty sure it's nothing to do with my setup...
Click to expand...
Click to collapse
Those 4.xx.502 RUU are crap...
Are you sure the 3.x.502 RUU completed ? I have never seen a phone bootloop after flashing that RUU.
clsA said:
Are you sure the 3.x.502 RUU completed ? I have never seen a phone bootloop after flashing that RUU.
Click to expand...
Click to collapse
Fairly sure, anyway? It takes the expected length of time (about 10 minutes), the progress bars march through their steps on the computer screen and phone screen, and the RUU exe congratulates me and says it's going to reboot the phone now when it's finished.
Can I try fastboot flashing a zip RUU, or does it require S-Off for that?
matt314159 said:
Fairly sure, anyway? It takes the expected length of time (about 10 minutes), the progress bars march through their steps on the computer screen and phone screen, and the RUU exe congratulates me and says it's going to reboot the phone now when it's finished.
Can I try fastboot flashing a zip RUU, or does it require S-Off for that?
Click to expand...
Click to collapse
it's no different ..if the EXE RUU worked and your still in bootloop you have a corrupt partition and will need expert advice. Maybe @nkk71 will have some time to help you
clsA said:
it's no different ..if the EXE RUU worked and your still in bootloop you have a corrupt partition and will need expert advice. Maybe @nkk71 will have some time to help you
Click to expand...
Click to collapse
Okay, thanks. I'm going to be taking this back to my colleague at work tomorrow, so I probably don't want nkk71 to spend much time on it unless he thinks it's something quick I can do tonight to get it running again.
Just on a lark, I also flashed twrp-recovery-2.7-m7-nobcb.img from This thread.--no change. Although my symptoms were different, it sounded like it might be worth a shot, but no dice.
matt314159 said:
Okay, thanks. I'm going to be taking this back to my colleague at work tomorrow, so I probably don't want nkk71 to spend much time on it unless he thinks it's something quick I can do tonight to get it running again.
Just on a lark, I also flashed twrp-recovery-2.7-m7-nobcb.img from This thread.--no change. Although my symptoms were different, it sounded like it might be worth a shot, but no dice.
Click to expand...
Click to collapse
@clsA is quite right about those 4.xx RUUs, they do work, but are very sensitive (for lack of a better word), about PC configuration, USB ports, etc... no clue what is the defining problem.
though all this sounds strange indeed, usually when the emmc is fried, "fastboot oem rebootRUU" will throw an error.
can you extract the ROM.ZIP from the 3.17.502.3 RUU.EXE and try flashing it using fastboot commands:
run the RUU.EXE, once you're at the welcome screen, it would have extracted all the files into %TEMP%/<weird long numbered folder name> (use sort by date modified to find the newest folders), in it you should find a 1.5GB or so ROM.ZIP <- that's an encrypted/signed ruu.zip) copy it to your fastboot folder, exit the RUU.EXE, and flash the ROM.ZIP (it will give a lot more output):
relock bootloader (since you are S-On):
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip ROM.ZIP
fastboot flash zip ROM.ZIP <- yes twice, the first one only does the hboot preupdate
fastboot reboot-bootloader
and copy/paste the command prompt output here, make sure to set the command prompt buffer size to a large enough size (at least 500+ lines)
obviously, if we had some background as to what happened previously, it would/could help too
nkk71 said:
@clsA is quite right about those 4.xx RUUs, they do work, but are very sensitive (for lack of a better word), about PC configuration, USB ports, etc... no clue what is the defining problem.
though all this sounds strange indeed, usually when the emmc is fried, "fastboot oem rebootRUU" will throw an error.
can you extract the ROM.ZIP from the 3.17.502.3 RUU.EXE and try flashing it using fastboot commands:
run the RUU.EXE, once you're at the welcome screen, it would have extracted all the files into %TEMP%/<weird long numbered folder name> (use sort by date modified to find the newest folders), in it you should find a 1.5GB or so ROM.ZIP <- that's an encrypted/signed ruu.zip) copy it to your fastboot folder, exit the RUU.EXE, and flash the ROM.ZIP (it will give a lot more output):
relock bootloader (since you are S-On):
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip ROM.ZIP
fastboot flash zip ROM.ZIP <- yes twice, the first one only does the hboot preupdate
fastboot reboot-bootloader
and copy/paste the command prompt output here, make sure to set the command prompt buffer size to a large enough size (at least 500+ lines)
obviously, if we had some background as to what happened previously, it would/could help too
Click to expand...
Click to collapse
Thank you for the clear instructions. I followed them over my lunch hour. My only problem was getting the command prompt buffer to stick, I changed it to 999 but it kept truncating the output anyhow. So I ran the commands a second time and snagged the output a few times throughout the process and cobbled it back together.
Here's the output at pastebin: http://pastebin.com/dNKaKKtd (note that it does not show the lock command as this was the second iteration that I captured)
presently, the phone is still looping.
I still have the phone for another night, so I'll keep going with this if you have more suggestions or instructions.
Many Thanks!
matt314159 said:
Thank you for the clear instructions. I followed them over my lunch hour. My only problem was getting the command prompt buffer to stick, I changed it to 999 but it kept truncating the output anyhow. So I ran the commands a second time and snagged the output a few times throughout the process and cobbled it back together.
Here's the output at pastebin: http://pastebin.com/dNKaKKtd (note that it does not show the lock command as this was the second iteration that I captured)
presently, the phone is still looping.
I still have the phone for another night, so I'll keep going with this if you have more suggestions or instructions.
Many Thanks!
Click to expand...
Click to collapse
Well that output looks just fine, the ruu is successfully flashed, and has put everything back to stock. So unfortunately i can't really think of anything else, my only two guesses would be:
1- hardware problem
2- if he did flash something into p19 (the active cmdline overflow error), then maybe try the older cwm 6.0.2.8 recovery which seems to sometimes work for s-on users
you should first try to find out from your friend if this was the result of him flashing something, or if it happened by itself (in the latter case, it would be a hardware problem for sure)
nkk71 said:
Well that output looks just fine, the ruu is successfully flashed, and has put everything back to stock. So unfortunately i can't really think of anything else, my only two guesses would be:
1- hardware problem
2- if he did flash something into p19 (the active cmdline overflow error), then maybe try the older cwm 6.0.2.8 recovery which seems to sometimes work for s-on users
you should first try to find out from your friend if this was the result of him flashing something, or if it happened by itself (in the latter case, it would be a hardware problem for sure)
Click to expand...
Click to collapse
Thanks so much for your help! Nothing ended up working, so I gave the phone back. My colleague wasn't sure the history of it, but I'm willing to bet hardware issue. I appreciate your guidance, though! This was good learning experience for me. I feel a lot more at home with a lot of the basic fastboot commands and that kind of thing, so it wasn't a total loss on my part. I'm usually having to look up tutorials just to remember basic syntax!
Anyway thanks to all who chimed in. If mods want, they can close this thread, otherwise I'll just let it sink to its grave.
So I have been an absolute fool, broken every rule that xda set out + tried to root my phone + commit all sorts of shindiggery over a period of months. After various roms, fails, bootloops + catastrophes we arrive at the present day. My phone will randomly say; press the power button to restart in 3, 2,1... then just turns off, bootloops over and over until I somehow get the right power click + it loads correctly. Its continuously doing this, I have since got it to a stable point (it has been on + working for about 2 hours this morning). But I havent fixed anything so I assume the problem is still there.
I also have noticed, if I try and add files, like music and stuff, to my phone from my computer, they wont move across. It glitches out and says the device is no longer recognised.
Another interesting point, I believe I have both clockwork mod and twrp installed, which confuses me because I thought you only needed one.
At the moment my phone (HTC one M7) has these attributes:
Android - 4.2.2
Kernel - [email protected]#1 SMP PREEMPT
Baseband version: 4A 17.3250.14_10.39.1150.04L
Build number: 2.24.771.3 CL211355 release keys.
Can someone please help, im in big doo doos!
gzaajoyce said:
So I have been an absolute fool, broken every rule that xda set out + tried to root my phone + commit all sorts of shindiggery over a period of months. After various roms, fails, bootloops + catastrophes we arrive at the present day. My phone will randomly say; press the power button to restart in 3, 2,1... then just turns off, bootloops over and over until I somehow get the right power click + it loads correctly. Its continuously doing this, I have since got it to a stable point (it has been on + working for about 2 hours this morning). But I havent fixed anything so I assume the problem is still there.
I also have noticed, if I try and add files, like music and stuff, to my phone from my computer, they wont move across. It glitches out and says the device is no longer recognised.
Another interesting point, I believe I have both clockwork mod and twrp installed, which confuses me because I thought you only needed one.
At the moment my phone (HTC one M7) has these attributes:
Android - 4.2.2
Kernel - [email protected]#1 SMP PREEMPT
Baseband version: 4A 17.3250.14_10.39.1150.04L
Build number: 2.24.771.3 CL211355 release keys.
Can someone please help, im in big doo doos!
Click to expand...
Click to collapse
Ok well looks like your on H3G but just so I know exactly what I'm dealing with here can you post the output of
Code:
fastboot getvar all
Please remove your imei and serial numbers before posting.
And try to confirm which recovery you have. It's not possible to have CWM and TWRP recovery. Ideally you want TWRP though.
Danny201281 said:
Ok well looks like your on H3G but just so I know exactly what I'm dealing with here can you post the output of
Code:
fastboot getvar all
Please remove your imei and serial numbers before posting.
And try to confirm which recovery you have. It's not possible to have CWM and TWRP recovery. Ideally you want TWRP though.
Click to expand...
Click to collapse
I will have to wait till tomorrow, to use a windows comp, nor sure how to do it on mac.
Also when I do put my phone into recovery, it is the clockworkmod recovery I have, although Ive definitely had TWRP before...
thanks for offer of help aswell
gzaajoyce said:
I will have to wait till tomorrow, to use a windows comp, nor sure how to do it on mac.
Also when I do put my phone into recovery, it is the clockworkmod recovery I have, although Ive definitely had TWRP before...
thanks for offer of help aswell
Click to expand...
Click to collapse
No problem post the getvar when your able and we'll take it from there :good:
Hi,
Think ive got the info here..
(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.771.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4170mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
gzaajoyce said:
Hi,
Think ive got the info here..
(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.771.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4170mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Ok cool, thanks. So first we are gonna need twrp recovery. Download it here http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.8.5.0-m7.img
Put the Image file in your fastboot folder and flash recovery.
Code:
fastboot flash recovery openrecovery-twrp-2.8.5.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
Now we are going to need to format the device. If you have any files on the device you want to save use MTP in TWRP to copy them to your pc. Select recovery from the bootloader menu to load TWRP.
When your happy you have everything you want to keep backed up, Select "Wipe" from the TWRP menu then " Format Data" you will be prompted to type yes to confirm. When it's done Select "Reboot" then Reboot Recovery.
You will see a message "No OS Installed" reboot anyway and say no when twrp asks if you want to install root. :good:
Ok so now you have a clean formatted device lets install a new Rom. For clarity sake we'll start with the stock Rom.
Download this http://settlecruise.org/Dovo?q=Guru_Reset_M7_2.24.771.3.zip
Using MTP in recovery again copy the Rom to your internal storage. And install it with TWRP. During the install choose these options
Code:
Stock Radio = Yes
Stock Recovery = No
Root = No
When the install is done Reboot the phone. It may stick at the HTC boot splash screen for 15 mins+ as this is a complete clean install.
Let me know how that goes :good: any questions just ask
Okay, so I did what you said, up until 'now we are going to need to format the device . If you have any files on the device you want to save use MTP in TWRP to copy them to your pc. Select recovery from the bootloader menu to load TWRP.'.
After I flashed the new recovery image?, erased cache and rebooted the bootloader. something weird happened though, it took me to a weird menu cant remember the options but recovery wasnt offered. Then I clicked bootloader, it then offered me recovery, clicked that, it started going into recovery but then my phone immediately turned off and started bootlooping again.
Managed to get it to turn on, then rebooted into recovery. Recovery started, TWRP logo up + and it started flashing something i guess, but then it turned off again + started bootlooping.
Then when I turned it on again, all my files were gone + i had to go through all the set up stuff again.
Not sure where to go from here
Danny201281 said:
Ok cool, thanks. So first we are gonna need twrp recovery. Download it here
Put the Image file in your fastboot folder and flash recovery.
Code:
fastboot flash recovery openrecovery-twrp-2.8.5.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
Now we are going to need to format the device. If you have any files on the device you want to save use MTP in TWRP to copy them to your pc. Select recovery from the bootloader menu to load TWRP.
When your happy you have everything you want to keep backed up, Select "Wipe" from the TWRP menu then " Format Data" you will be prompted to type yes to confirm. When it's done Select "Reboot" then Reboot Recovery.
You will see a message "No OS Installed" reboot anyway and say no when twrp asks if you want to install root. :good:
Ok so now you have a clean formatted device lets install a new Rom. For clarity sake we'll start with the stock Rom.
Download this
Using MTP in recovery again copy the Rom to your internal storage. And install it with TWRP. During the install choose these options
Code:
Stock Radio = Yes
Stock Recovery = No
Root = No
When the install is done Reboot the phone. It may stick at the HTC boot splash screen for 15 mins+ as this is a complete clean install.
Let me know how that goes :good: any questions just ask
Click to expand...
Click to collapse
gzaajoyce said:
Okay, so I did what you said, up until 'now we are going to need to format the device . If you have any files on the device you want to save use MTP in TWRP to copy them to your pc. Select recovery from the bootloader menu to load TWRP.'.
After I flashed the new recovery image?, erased cache and rebooted the bootloader. something weird happened though, it took me to a weird menu cant remember the options but recovery wasnt offered. Then I clicked bootloader, it then offered me recovery, clicked that, it started going into recovery but then my phone immediately turned off and started bootlooping again.
Managed to get it to turn on, then rebooted into recovery. Recovery started, TWRP logo up + and it started flashing something i guess, but then it turned off again + started bootlooping.
Then when I turned it on again, all my files were gone + i had to go through all the set up stuff again.
Not sure where to go from here
Click to expand...
Click to collapse
Ok that doesn't sound right at all. Seems like something is really messed up.
I'm a little confused about were the device is at now though. You say you had to complete the first time use setup so the Rom did boot?
But your still not able to get into recovery?
Hi, sorry I get confused with all the terminology. The issues i was having yesterday have seemed to resolve themselves ,I tried it again and it worked up until putting the Guru_reset+.zip.dmg file on my phone. I use MTP, it comes up on my computer as 'One' with a folder called TWRP in it, when I put the the .zip.dmg file on it I cant find it on the phone?!
I am looking in internal storage, sdcard, TWRP, have selected view Zips + I still cant see it..
Unsure what to do now.
Okay, worked it out, for some reason it was downloading it with .dmg on the end, so it wasnt working as a zip, I changed the file name but then it doesnt flash properly . I get to the 'swipe to confirm flash' page and it reboots instantly to the TWRP logo then back into recovery... not sure what to do now
gzaajoyce said:
Hi, sorry I get confused with all the terminology. The issues i was having yesterday have seemed to resolve themselves ,I tried it again and it worked up until putting the Guru_reset+.zip.dmg file on my phone. I use MTP, it comes up on my computer as 'One' with a folder called TWRP in it, when I put the the .zip.dmg file on it I cant find it on the phone?!
I am looking in internal storage, sdcard, TWRP, have selected view Zips + I still cant see it..
Unsure what to do now.
Click to expand...
Click to collapse
it should have only a .zip extension. Did you download it from the link I posted? I just checked the link it seems to be bad
http://www.htc1guru.com/dld/guru_reset_m7_2-24-771-3-zip/ or use a previous copy of you have one. But it should be named guru_reset_m7_2-24-771-3.zip if your sure the file is ok try deleting the .dmg from the file name :good:
---------- Post added at 05:26 PM ---------- Previous post was at 05:15 PM ----------
gzaajoyce said:
Okay, worked it out, for some reason it was downloading it with .dmg on the end, so it wasnt working as a zip, I changed the file name but then it doesnt flash properly . I get to the 'swipe to confirm flash' page and it reboots instantly to the TWRP logo then back into recovery... not sure what to do now
Click to expand...
Click to collapse
Did you do the data format? If you got that download from the first link I posted try downloading it from the second in my above post. :good:
Danny201281 said:
Ok that doesn't sound right at all. Seems like something is really messed up.
I'm a little confused about were the device is at now though. You say you had to complete the first time use setup so the Rom did boot?
But your still not able to get into recovery?
Click to expand...
Click to collapse
Hi!
Well I decided to install viper+rom, as I couldnt get the old one to function and so far it seems to be working all right ! Thanks again for bearing with me through this Cheers!
gzaajoyce said:
Hi!
Well I decided to install viper+rom, as I couldnt get the old one to function and so far it seems to be working all right ! Thanks again for bearing with me through this Cheers!
Click to expand...
Click to collapse
Ok sweet, if it's working great. :good:
For future reference I have a thread here for Stock files for H3G branded phones with s-on. If you ever need anything
http://forum.xda-developers.com/showthread.php?t=3028559
Danny201281 said:
Ok that doesn't sound right at all. Seems like something is really messed up.
I'm a little confused about were the device is at now though. You say you had to complete the first time use setup so the Rom did boot?
But your still not able to get into recovery?
Click to expand...
Click to collapse
Hi Danny,
Oh dear, its since gone from bad to worse. I have a definite hardware issue, at least im 90% certain. Now Im gonna have to send it off for repairs, but I wont be quoted until the engineers have it + its gonna come to at least 30 quid.
They know I've tampered with the phone + opened the bootloader, so warranty doesnt cover it. Is there anyway to reset this, to hide to 3/HTC that ive accessed the forbidden fruit + messed my phone up?
Thanks,
George
gzaajoyce said:
Hi Danny,
Oh dear, its since gone from bad to worse. I have a definite hardware issue, at least im 90% certain. Now Im gonna have to send it off for repairs, but I wont be quoted until the engineers have it + its gonna come to at least 30 quid.
They know I've tampered with the phone + opened the bootloader, so warranty doesnt cover it. Is there anyway to reset this, to hide to 3/HTC that ive accessed the forbidden fruit + messed my phone up?
Thanks,
George
Click to expand...
Click to collapse
How bad is it? Do you still have a functioning Rom?
You can return it to stock so it looks Untampered but you will need s-off to do it. And to get s-off you need a functioning Rom.
Danny201281 said:
Ok that doesn't sound right at all. Seems like something is really messed up.
I'm a little confused about were the device is at now though. You say you had to complete the first time use setup so the Rom did boot?
But your still not able to get into recovery?
Click to expand...
Click to collapse
Danny201281 said:
How bad is it? Do you still have a functioning Rom?
You can return it to stock so it looks Untampered but you will need s-off to do it. And to get s-off you need a functioning Rom.
Click to expand...
Click to collapse
Okay, well as it stands it wont turn on. I have charged + it constantly bootloops. Not sure how to proceed from here? Danny have I truly f**ked it ?
gzaajoyce said:
Okay, well as it stands it wont turn on. I have charged + it constantly bootloops. Not sure how to proceed from here? Danny have I truly f**ked it ?
Click to expand...
Click to collapse
Sorry for the wait my weekend was very busy. So the device no longer powers on (no sign of life) or is bootlooping on boot screen?
It does seem like maybe there is a hardware issue here, sorry if I already asked this but Do you have warranty? Maybe return to stock and send it for repair. It will need to boot to a somewhat stable Rom to get s-off though.
Hi there,
I bought a 2nd hand phone [HTC M7] off ebay with Revolution 90.1 / Android 5.02 / Build No. 7.15.401.1
Everything works great...but I can't make or receive calls. I figured this was the same issue that struck HTC phones in Dec, but from my understanding 7.15.401.1 is more recent than the official HTC fix (6.10.531.10) & Rev. 90.1 already has this fix included also. I've also installed Viperone 7.02 (fix incl.), but no difference, so I'm now back to Rev. 90.1. I've also cleared google caches, froze HTC lockscreen etc etc but now I've run out of ideas.
Can anybody help?!
Thanks..!
Dial tone on a mobile phone... Whaaat? Bring the phone to your service provider, which is advice I never really give out, but from what you wrote, I think your missing something, like installing the SIM card or provisioning the phone correctly. Do you even have service and signal on it?
Sent from my HTC One using Tapatalk
synt3k said:
Dial tone on a mobile phone... Whaaat? Bring the phone to your service provider, which is advice I never really give out, but from what you wrote, I think your missing something, like installing the SIM card or provisioning the phone correctly. Do you even have service and signal on it?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Sorry - Dial tone meaning when I call I don't hear a ring [orig post now edited].
Data/Wifi works & I get signal. If people call me my phone rings, I can pick up but then silence
Tinky24 said:
Sorry - Dial tone meaning when I call I don't hear a ring [orig post now edited].
Data/Wifi works & I get signal. If people call me my phone rings, I can pick up but then silence
Click to expand...
Click to collapse
can you post the fastboot getvar all of the phone please, remove imei and serial number before posting
Seanie280672 said:
can you post the fastboot getvar all of the phone please, remove imei and serial number before posting
Click to expand...
Click to collapse
:
I can't get Min. Adb & Fastboot to see my device [ adb devices just prints "List of Devices" then a blank line], which suggests I'm missing drivers
I've done both routes suggested on technobuzz.net/fastest-easiest-method-setup-adb-fastboot-windows/ and no luck. I've uninstalled and reinstalled my HTC m7 drivers, to no avail.
Tinky24 said:
:
I can't get Min. Adb & Fastboot to see my device [ adb devices just prints "List of Devices" then a blank line], which suggests I'm missing drivers
I've done both routes suggested on technobuzz.net/fastest-easiest-method-setup-adb-fastboot-windows/ and no luck. I've uninstalled and reinstalled my HTC m7 drivers, to no avail.
Click to expand...
Click to collapse
which version of windows are you using ?
also have a look in device manager whislt your phone is plugged in and phone in bootloader with fastbootUSB showing on the screen, see if device manager is seeing your device, it should say MyHTC under Android Devices (post a pict of device manager if possible)
fastboot commands only whilst in bootloader, adb wont work, adb is only for booted rom and recovery.
Just had a look at the link you posted, The adb and fastboot files are fine, I use those ones myself, the drivers are probably too far out of date, download HTC sync manager and install it, then goto add remove programs and remove HTC sync only, you will see the driver package just above it, leave that there, then plug your phone in and try fastboot devices or fastboot getvar all again.
Seanie280672 said:
which version of windows are you using ?
also have a look in device manager whislt your phone is plugged in and phone in bootloader with fastbootUSB showing on the screen, see if device manager is seeing your device, it should say MyHTC under Android Devices (post a pict of device manager if possible)
fastboot commands only whilst in bootloader, adb wont work, adb is only for booted rom and recovery.
Just had a look at the link you posted, The adb and fastboot files are fine, I use those ones myself, the drivers are probably too far out of date, download HTC sync manager and install it, then goto add remove programs and remove HTC sync only, you will see the driver package just above it, leave that there, then plug your phone in and try fastboot devices or fastboot getvar all again.
Click to expand...
Click to collapse
Right, getting somewhere, thanks for clarifying the fastboot/adb difference:
fastboot getvar all
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.14.3250.13
version-cpld: None
version-microp: None
version-main: 1.29.401.2
version-misc: PUT SHIP S-OFF
meid: 000000000000
product: my_url
platform: HBOOT-8064
modelid: PN710000
cidnum: 11111111
battery-status: good
battery-voltage: 4250mv
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
[Windows 7 btw]
Tinky24 said:
Right, getting somewhere, thanks for clarifying the fastboot/adb difference:
fastboot getvar all
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.14.3250.13
version-cpld: None
version-microp: None
version-main: 1.29.401.2
version-misc: PUT SHIP S-OFF
meid: 000000000000
product: my_url
platform: HBOOT-8064
modelid: PN710000
cidnum: 11111111
battery-status: good
battery-voltage: 4250mv
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
[Windows 7 btw]
Click to expand...
Click to collapse
dont change to windows 8 you will have all sorts of problems due to your HBOOT, you are on a very early firmware there and as you are s-off, that helps alot, I think you really need to bring your phone back up to speed to be sure thats not whats causing the issues your having, bear with me whilst I find the link of 401 firmwares. (version-main: 1.29.401.2)
If there is anything on the phone you need to keep, pictures, photo's music etc, please back it up now as firmware flash can wipe the device in some cases.
OK heres the link to the firmwares, you need to flash them one at a time, starting with the earliest 2.24.401's then the 3xxxxxx's then the 4xxxxx's then the 5xxxxxx and finally the 6xxxxxx's,: http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/ this issue you experiencing was fixed in the 7xxxxxx firmware which i'll find the link for shortly.
Do you know how to flash the firmware ?
Thanks so much.
I've found a guide
Tinky24 said:
Thanks so much.
Is it the same way as flashing a ROM i.e. Recovery > Install?
Click to expand...
Click to collapse
no, heres a good guide on how to do it: https://trjlive.com/guide-install-firmware-htc-one-m7/
if your phone is already in fastbootUSB mode, then skip the first 2 commands, also something not mentioned in the guide is the firmware.zip file MUST be in the same folder as your adb and fastboot files on your computer, when you download the firmware files (one at a time) they will be named as per the name on the site, just rename them to firmware.zip for ease, once you've finished flashing each one and the phone has finished booting, delete it and download the next then follow the prceedure once again.
your battery must be 50% or more before proceeding, but I can see yours is good at the moment at 4250mv
If you check yourself, no need to post each one, you should notice the version main number going up, the HBOOT version going up, you will also have stock recovery (a red triangle with an exclamation mark)
do not skip any steps and you'll be fine, report back after the first flash and let us know how it went, any problems, just ask.
Ok all done, getvar now gives me:
version-main: 6.09.401.12
HBOOT 1.57
Tinky24 said:
Ok all done, getvar now gives me:
version-main: 6.09.401.12
HBOOT 1.57
Click to expand...
Click to collapse
perfect, as long as it still says your s-off, ps, never go s-on, you'll regret it, you can do one of the following.
You can flash this firmware https://www.androidfilehost.com/?fid=95897840722644637 (unsigned) not official yet, but will work for you as your s-off, if you go s-on your phone will brick, and then test your rom, your issue should be fixed.
Or you can do this which is what I did: http://forum.xda-developers.com/htc-one/general/guide-convert-m7-developer-edition-t2840311 This is official
I rebooted after finishing the v6 updates, then got the red triangle thing - do I now factory reset?
"can not mount SD card"
Tinky24 said:
I rebooted after finishing the v6 updates, then got the red triangle thing - do I now factory reset?
Click to expand...
Click to collapse
hold down the power button with the volume down, keep holding whilst the home and back bottuns on the bottom flash about 15 times, when they stop flashing, release the power button, but continue to hold down the volume down, the phone should boot to the bootloader, factory reset is in the list, use the volume button up / down to highlight it and power button to select, why do you want to factory reset ?
---------- Post added at 08:19 PM ---------- Previous post was at 08:18 PM ----------
cannot mount sdcard is a normal error if you have entered recovery, there is no sdcard.
Sorry ignore the fact. reset bit.
I've now uploaded the last firmware zip you gave me. Can I just System reboot or is there something left to do?
Tinky24 said:
Sorry ignore the fact. reset bit.
I've now uploaded the last firmware zip you gave me. Can I just System reboot or is there something left to do?
Click to expand...
Click to collapse
yeah just system reboot, the lollipop rom's do really require Lollipop firmware which is what you just flashed in order toi work properly, your firmware was about 2 years out of date.
Reboot brings up the white HTC screen...then the screen returns to Stock Recovery Triangle...
Tinky24 said:
Reboot brings up the white HTC screen...then the screen returns to Stock Recovery Triangle...
Click to expand...
Click to collapse
The firmware flash may of messed up your rom, did you flash android revolution 90.1 yourself ?
No it came with Rev. Should I reflash it?
Tinky24 said:
No it came with Rev. Should I reflash it?
Click to expand...
Click to collapse
yes, or a rom of your choice, you will need a custom recovery first, so download this:
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.8.5.0-m7.img
put your phone into fastbootUSB mode on the screen again by holding down the volume down and power button method again as I described earlier, this is the white screen not the black screen with silver HTC logo.
rename the download above to recovery.img and place it in the same folder as adb and fastboot again and with your phone plugged in issue these commands one at a time:
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
then enter recovery, as long as your drivers are working correctly, this recovery supports MTP so the computer should see the internal storage, just downlaod and copy the rom you want to flash straight to the internal storage, unplug your phone and install it, its recommended to install option with full wipe, dont worry, internal storage isnt touched, just wipes data and system.
Sorry i know this has been done a million times before but i cant seem to find anything that helps in my particular situation already. ill explain a bit what happened first exactly, my phone recently crapped itself and i sent it to the carrier for repair, they gave me a refurbished one that is faulty (gets really hot after about 20 min of use and restarts itself). anyways after a big headache of trying to send it back which is not really important here, i gave up and decided since i dont care enough about this phone to pay to fix it i can try and root it and hopefully install a rom that might keep the cpu cool and not reset so often (not sure if possible but it seemed harmless to try). anyways i unlocked the bootloader, installed CWM and not sure why but when i restarted the phone itll start up fine as if the first tiem you ever use the phone but you couldnt do anything after the set up. it just links to some site and you cant move at all or click anything its stuck. so i thought id install a ROM and hopefully fix it (decided on Maximus HD) im pretty sure i downloaded from here too so hopefully legit and now i cant even get into the menu at all. it gets stuck on the HTC boot logo unless i get into the bootloader which i still thankfully can and also into recovery. anyways i flashed TWRP just now in the hopes i can get an option in that to fix it that CWM doesnt have but still cant find anything and lot of the stuff i tried picking said "unable to flash s:" or somethng like that. same thing since isntalling TWRP though if i try restarting phone just to get into menu it hangs on the HTC logo screen i can only get into bootloader/recovery mode. what can i do? I still have s-on if thats relevant (probably that was the problem to begin with?)
misticknight1 said:
Sorry i know this has been done a million times before but i cant seem to find anything that helps in my particular situation already. ill explain a bit what happened first exactly, my phone recently crapped itself and i sent it to the carrier for repair, they gave me a refurbished one that is faulty (gets really hot after about 20 min of use and restarts itself). anyways after a big headache of trying to send it back which is not really important here, i gave up and decided since i dont care enough about this phone to pay to fix it i can try and root it and hopefully install a rom that might keep the cpu cool and not reset so often (not sure if possible but it seemed harmless to try). anyways i unlocked the bootloader, installed CWM and not sure why but when i restarted the phone itll start up fine as if the first tiem you ever use the phone but you couldnt do anything after the set up. it just links to some site and you cant move at all or click anything its stuck. so i thought id install a ROM and hopefully fix it (decided on Maximus HD) im pretty sure i downloaded from here too so hopefully legit and now i cant even get into the menu at all. it gets stuck on the HTC boot logo unless i get into the bootloader which i still thankfully can and also into recovery. anyways i flashed TWRP just now in the hopes i can get an option in that to fix it that CWM doesnt have but still cant find anything and lot of the stuff i tried picking said "unable to flash s:" or somethng like that. same thing since isntalling TWRP though if i try restarting phone just to get into menu it hangs on the HTC logo screen i can only get into bootloader/recovery mode. what can i do? I still have s-on if thats relevant (probably that was the problem to begin with?)
Click to expand...
Click to collapse
s-on is nothing to do with it, as long as your bootloader is unlocked, that's enough to flash custom roms.
TWRP is required to flash custom sense based roms, which version of TWRP depend on which rom you are trying to flash, so Lollipop based sense roms require TWRP 2.8.6.0, whereas the later ones require TWRP 2.6.3.3
after flash recovery, be sure to erase the cache and reboot the bootloader before trying to enter recovery, this clears anything that the previous recovery may of left behind, reboot bootloader is basically for changes to take effect, so your commands should look like this:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
when you enter recovery, personally in your situation, I would go into wipe, and select the format data button, this will wipe everything off your phone including the internal storage, so be sure to backup anything you need first, you can do this with the adb pull /sdcard/0 command from the recovery main screen. once the format is complete, reboot back into recovery again, and adb push or copy a rom to your internal storage, be sure to unplug your phone now and then flash it, also be sure to select full wipe during the installation.
you can only really use lollipop based custom roms if you are on lollipop firmware, people on lower firmware are reporting problems like no wifi, Bluetooth etc, so it would be helpful if you post your fastboot getvar all without your imei and serial number.
how do i get that? and i am using twrp 2.8.6.0.
misticknight1 said:
how do i get that? and i am using twrp 2.8.6.0.
Click to expand...
Click to collapse
well you know how to use fastboot commands, so with the phone booted in the bootloader and fastbootUSB showing on the screen and plugged into the computer the command is fastboot getvar all post the output here without imei and serial number.
Sorry took so long to respond to my own topic i was at work. heres the results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.21.980.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 3831mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Bump
Sorry i know this is annoying but one more bump before i let it die just want to know if its even possible to fix my phone.
misticknight1 said:
Sorry i know this is annoying but one more bump before i let it die just want to know if its even possible to fix my phone.
Click to expand...
Click to collapse
First step go into TWRP / Wipe / Advanced / Format Data ... type yes
when it's done go to Reboot / Recovery
now download and install this Rom >> https://www.androidfilehost.com/?fid=23991606952602541
during install choose Wipe system
the phone will take almost 10 min to boot ..wait on it and be patient
I'm trying to copy the zip file onto the phone but even though the computer reads it it says "cannot copy device has either stopped working or been removed".
misticknight1 said:
I'm trying to copy the zip file onto the phone but even though the computer reads it it says "cannot copy device has either stopped working or been removed".
Click to expand...
Click to collapse
unplug and replug in the phone and start over ... don't let it sleep
Nevermind found out it hadn't completed properly, redownloading now hopefully it should be alright.
Thanks heaps it worked
misticknight1 said:
Thanks heaps it worked
Click to expand...
Click to collapse
Great !!
Spoke a bit too soon used it for a bit now it still resets I guess that's a hardware problem for sure now though and not much I can do about it unless I take it to a pro.