Related
okay guys this is weird. til now i have only read the forums and did think about rooting my phone to install a custom rom because the latest htc update made my phone so horrible. but now anything changed cause this just happened:
i got an sms (using the preinstalled sms app) and answered to it. send the phone to "sleep" (?) by pressing power button once, like always. laying the phone back on the table, continuing playing darksiders2. maybe 5 minutes later the display brightens up by itself like if an incoming call but nothing happens. i grab the phone and try to press anything or swipe to see whats going on, but no input gets recognized. plus the button row doesnt get lighten up like normally. confused i tried to press the power button but even that shows no reaction. it just stayed that way, nothing i could do. because i had one freeze under 2.3.5 or so i took the battery out to do a hard reset. booting up again gets me now into the screen i only read here before: where you have to go to install roms from zips etc. but i have booted normally, without pressing the volume keys. the title row says: locked, security warning. rebooting the phone out of this only gets me back here. i dont get it. i mean i know this version is messed up but what is this? my phone is broken and i havent even tried to unlock or anything else it... my god. i dont know what to do. next week is coming up and i dont have multiple phones.
has anyone any idea? please help!
ps: please forgive me any language flaws, english isnt my mother tongue.
Possible solutions
- Wipe the data from recovery if you can, or from bootloader
- Install the ruu when you had before
What country are you/the phone from?
And give us the output of the command
Fastboot getvar all
Sent from my HTC Incredible S using xda app-developers app
hello, thank you for your replies!
i bought the phone over amazon.de and i'm from germany.
where do i have to write "Fastboot getvar all"? do i need to install something and connect the phone to usb or anything like that? i mean i read about some incS roms on the forums but never tried anything myself so i have to look into that first on how to set things up..
edit: so i finally managed to setup android sdk adb and get this command running. yay!
C:\Windows\system32>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.02.0002
(bootloader) version-baseband: 3831.18.00.11_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.10.405.1
(bootloader) serialno: XXXX
(bootloader) imei: XXXX
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3213000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4069mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: d41e50e7
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.030s
Click to expand...
Click to collapse
I think your best option is to just run the ruu http://d-h.st/7UC
ok i have a question: im downloading the exe right now. is this an extracting archive and do i have to do anything with it or is it a real exe and a like precompiled autorun thing? btw what am i downloading here? is this the latest unmodified original htc system for my phone?
and yeah: how do i need to apply it?
benutzer001 said:
ok i have a question: im downloading the exe right now. is this an extracting archive and do i have to do anything with it or is it a real exe and a like precompiled autorun thing? btw what am i downloading here? is this the latest unmodified original htc system for my phone?
and yeah: how do i need to apply it?
Click to expand...
Click to collapse
It is an executable program. Just run it on a Windows PC and follow the instructions.
ouch. so everything will be gone? i mean a have the sd and sim out but okay..
btw: i just dont get what this is. have you any clue on what happened here and/or why? this just makes no sense to me. how can it corrupt itself?
benutzer001 said:
ouch. so everything will be gone? i mean a have the sd and sim out but okay..
btw: i just dont get what this is. have you any clue on what happened here and/or why? this just makes no sense to me. how can it corrupt itself?
Click to expand...
Click to collapse
I don't know why this happen but yes everything will be gone.
i doesnt work.. great..
program runs, checks version, newest version and version on phone are the same, i click okay patch anyway, phone reboots and progress bar shows up on pc. phone boots right to the locked-security warning menu and the pc bar gets stuck at waiting for bootloader. stays there 2 minutes and then aborts patching.
benutzer001 said:
i doesnt work.. great..
program runs, checks version, newest version and version on phone are the same, i click okay patch anyway, phone reboots and progress bar shows up on pc. phone boots right to the locked-security warning menu and the pc bar gets stuck at waiting for bootloader. stays there 2 minutes and then aborts patching.
Click to expand...
Click to collapse
Try it again.
error 171 usb connection error
edit: i found that the fastboot var gives an answer if the phone is connected but (as of my understanding) a basic command like adb devices shows up nothing. is says showing list of devices but the space stays blank. but the fastboot command gets an answer so there must be some sort of communication between phone and pc..
benutzer001 said:
error 171 usb connection error
edit: i found that the fastboot var gives an answer if the phone is connected but (as of my understanding) a basic command like adb devices shows up nothing. is says showing list of devices but the space stays blank. but the fastboot command gets an answer so there must be some sort of communication between phone and pc..
Click to expand...
Click to collapse
Do you have the HTC Sync app installed on your PC? If so, make sure it is not running in the System Tray or remove it all together and try again.
If you don't have HTC Sync installed, then install it to get the current drivers and then you can uninstall it and try it again.
which parts do i uninstall after installing the sync package? i have the following:
htc sync
htc driver installer
htc bmp usb driver
do i just need to uninstall htc sync and keep the rest or uninstall everything?
edit: i only uninstalled htc sync keeping the rest. same error.
benutzer001 said:
which parts do i uninstall after installing the sync package? i have the following:
htc sync
htc driver installer
htc bmp usb driver
do i just need to uninstall htc sync and keep the rest or uninstall everything?
edit: i only uninstalled htc sync keeping the rest. same error.
Click to expand...
Click to collapse
You can extract the Rom.zip file that the ruu is using and update manually.
Start the ruu software and stay on the first screen.
In your Start>Search programs and files box type %temp% and press enter. A temp window should appear.
search for rom.zip in that window and copy this file to your fastboot dir.
Now you have 2 options. Flash through fastboot
Code:
fastboot oem rebootRUU
fastboot flash zip rom.zip
or rename rom.zip to PG32IMG.zip, copy to your sdcard root, reboot bootloader(hboot mode) and let the bootloader detect the zip and install.
Nonverbose said:
and copy this file to your fastboot dir.
Click to expand...
Click to collapse
where is my fastboot dir? for the adb commands i've setup an android-sdk-windows folder in C: but nothing else.
just running the "fastboot oem rebootRUU" command from somewhere gets me this:
C:\Users\XXXX>fastboot oem rebootRUU
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(730): error 2
OKAY [ 0.052s]
finished. total time: 0.055s
Click to expand...
Click to collapse
i am doing all this with my bare phone, no sd and sim card inserted. is it necessary to backup my sd card and insert it?!
and does everything needs to be done in an elevated cmd?
Looks like hardware failure. Try the PG32IMG.zip method but I don't like your chances. From what I see, you did everything right.
so you think it just died? when i try to send the rom.zip in an not elevated cmd over usb it sends correctly, then tries to apply it but aborts with an error saying smth. like flashing over remote is not allowed.
funny thing is that i dont have any other access to my microsd (32gig btw) other than my phone. and right now i cant access it or is there a cmd way? i dont think so because the phone os would be needed to unmount the sd card so that windows can access it, right?
benutzer001 said:
so you think it just died? when i try to send the rom.zip in an not elevated cmd over usb it sends correctly, then tries to apply it but aborts with an error saying smth. like flashing over remote is not allowed.
funny thing is that i dont have any other access to my microsd (32gig btw) other than my phone. and right now i cant access it or is there a cmd way? i dont think so because the phone os would be needed to unmount the sd card so that windows can access it, right?
Click to expand...
Click to collapse
I think you have fried emmc chip. Some batches of incS are notorious for it. It commonly occurs by powering down by removing the battery, but It's possible that it just died.
If you have another sdcard, I would try that before giving up hope. You should be able to copy the pg32img.zip by entering hboot USB mode.
edit: I had look back at your previous posts and noticed you didn't have sdcard inserted. It should be installed in the phone.
Hello,
I have a HTC One S-On with bootloader unlocked.
I have installed Android Revolution HD, it worked fine for 2-3 months and suddenly the phone was not detected by any computer, and it was only charging when OFF.
I tried to restore with a stock rom and it was the same.
Then I have tried to format everything with CWM and to reflash with a new stock rom.
Now the problem is that when I plug the phone in fastboot mode it shows "fastboot USB", and it's well detected by computers, but when I start CWM or TWRP and when I try to mount USB storage, computers detect it for 1 or 2 seconds only and the USB storage never appear in the computer.
:crying:
So Im stuck can someone please help !!!
fenix71230 said:
Hello,
I have a HTC One S-On with bootloader unlocked.
I have installed Android Revolution HD, it worked fine for 2-3 months and suddenly the phone was not detected by any computer, and it was only charging when OFF.
I tried to restore with a stock rom and it was the same.
Then I have tried to format everything with CWM and to reflash with a new stock rom.
Now the problem is that when I plug the phone in fastboot mode it shows "fastboot USB", and it's well detected by computers, but when I start CWM or TWRP and when I try to mount USB storage, computers detect it for 1 or 2 seconds only and the USB storage never appear in the computer.
:crying:
So Im stuck can someone please help !!!
Click to expand...
Click to collapse
Your drivers are probably not up to date. Install HTC Sync Manager, connect phone to the manager, uninstall HTC SM. Otherwise check that USB Debugging is enabled.
If that doesn't work, get S-OFF, flash an RUU and see if it fixes it.
attanasi0 said:
Your drivers are probably not up to date. Install HTC Sync Manager, connect phone to the manager, uninstall HTC SM. Otherwise check that USB Debugging is enabled.
If that doesn't work, get S-OFF, flash an RUU and see if it fixes it.
Click to expand...
Click to collapse
I have just installed new HTC Sync Manager, I connect my phone via USB (fastboot USB), it install fine the driver (My HTC) then HTC SYnc Manager tells me that : Phone is not available, please reconnect it.
If I go back to bootloader and then fastboot USB HTC Sync tells me that again.
I can't get S-OFF because I have no OS installed
Please help !
fenix71230 said:
I have just installed new HTC Sync Manager, I connect my phone via USB (fastboot USB), it install fine the driver (My HTC) then HTC SYnc Manager tells me that : Phone is not available, please reconnect it.
If I go back to bootloader and then fastboot USB HTC Sync tells me that again.
I can't get S-OFF because I have no OS installed
Please help !
Click to expand...
Click to collapse
can you post a "fastboot getvar all" (remove IMEI and s/n), and which ROM you are/were using. (you say no OS installed, how did you wipe it?) post more details so we can figure out where you are at.
(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.1020.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__247
(bootloader) battery-status: good
(bootloader) battery-voltage: 3625mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.051s
I was with Anroid Revolution HD 30.0
I wiped all with CWM with format system, cache, data
fenix71230 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.1020.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__247
(bootloader) battery-status: good
(bootloader) battery-voltage: 3625mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.051s
I was with Anroid Revolution HD 30.0
I wiped all with CWM with format system, cache, data
Click to expand...
Click to collapse
OK, no problem. A couple of notes:
1- ARHD 30/31 is based on Android 4.3; and Android 4.3 is known to have (sometimes) connectivity issues (MTP and adb), these are usually solved by a combination of updated HTC drivers and/or updated firmware.
2- You are still on firmware 1.29.1020.2 and S-On, so you cannot flash unsigned firmware.... Are you interested/willing/able to getting S-Off (what's the date of you hboot)?
3- to get a ROM to your phone, you should enter CWM recovery, "adb" would work from there, you can either
------ "adb push <name of rom>.zip /sdcard/"
------ adb sideload
------ OR if you have an OTG cable, you can use that
nkk71 said:
OK, no problem. A couple of notes:
1- ARHD 30/31 is based on Android 4.3; and Android 4.3 is known to have (sometimes) connectivity issues (MTP and adb), these are usually solved by a combination of updated HTC drivers and/or updated firmware.
2- You are still on firmware 1.29.1020.2 and S-On, so you cannot flash unsigned firmware.... Are you interested/willing/able to getting S-Off (what's the date of you hboot)?
3- to get a ROM to your phone, you should enter CWM recovery, "adb" would work from there, you can either
------ "adb push <name of rom>.zip /sdcard/"
------ adb sideload
------ OR if you have an OTG cable, you can use that
Click to expand...
Click to collapse
Yes I am interested by installing S-Off but how can I do without OS and in CWM adb doesn't detect my phone.
My hboot date is 11 March 2013.
I don't have an OTG cable yet but I have order one.
fenix71230 said:
Yes I am interested by installing S-Off but how can I do without OS and in CWM adb doesn't detect my phone.
My hboot date is 11 March 2013.
I don't have an OTG cable yet but I have order one.
Click to expand...
Click to collapse
adb should work in CWM (I had one version that didnt, but the rest should), so just because it works for me, can you download the following one:
recovery-clockwork-touch-6.0.3.2-m7--v2.img (7.2 MB)
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
MD5: 1c6afb14db3f305b0ad7d85d5af80bef
Once you've downloaded and verified MD5:
fastboot erase cache
fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY
and confirm "adb devices" now shows you are connected. we'll proceed from there.
BTW: hboot 11 March 2013 is good for revone, I'll PM you a link for a ROM that works for that when you confirm adb is working.
EDIT: can you copy/paste you command prompt as you do the above mentioned fastboot commands.
All done but when I launch CWM it shows :
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
Pc has well installed USB composite device, Mass storage USB device, won't install Android Phone : device disconnected, well installed HTC Android Phone USb Device
When I type adb devices it detect nothing I fear a hardware failure?
C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>fastboot erase cache
erasing 'cache'...
OKAY [ 0.063s]
finished. total time: 0.064s
C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>fastboot flash recovery recov
ery.img
sending 'recovery' (7422 KB)...
OKAY [ 1.143s]
writing 'recovery'...
OKAY [ 0.649s]
finished. total time: 1.794s
C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>fastboot erase cache
erasing 'cache'...
OKAY [ 0.053s]
finished. total time: 0.053s
C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.048s
C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>
I had pretty much the same problem as you for a long time and did the following:
Uninstalled everything to do with HTC - drivers, sync etc
Downloaded a program called USBDEVIEW (google it) and then install it. Make sure you run it as administrator. It will load all the drivers installed. At this point make sure the phone is not connected. Select all the HTC drivers and delete - anything that says android usb, htc, mtp device etc
Once thats done I went to C:\windows\system32\driverstore and theres a file there I think called info cache. Right clich and change the security so that you can edit the file and then delete. Restart the computer
Try then inserting the phone to a USB 2.0 port and allow the drivers to install. Make sure you are using the HTC cable!
This is how I fixed it anyways, hope it works for you!
fenix71230 said:
All done but when I launch CWM it shows :
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
Click to expand...
Click to collapse
This is normal.
fenix71230 said:
C:\Users\cyril\Downloads\One_All-In-One_Kit_v\data>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.048s
Click to expand...
Click to collapse
Did you enter Recovery after that? Can you see CWM recovery screen? adb will not work in bootloader.
nkk71 said:
This is normal.
Did you enter Recovery after that? Can you see CWM recovery screen? adb will not work in bootloader.
Click to expand...
Click to collapse
Yes i can enter and see CWM, that's when my PC have detected it but won't install Android phone
stovie_steve said:
I had pretty much the same problem as you for a long time and did the following:
Uninstalled everything to do with HTC - drivers, sync etc
Downloaded a program called USBDEVIEW (google it) and then install it. Make sure you run it as administrator. It will load all the drivers installed. At this point make sure the phone is not connected. Select all the HTC drivers and delete - anything that says android usb, htc, mtp device etc
Once thats done I went to C:\windows\system32\driverstore and theres a file there I think called info cache. Right clich and change the security so that you can edit the file and then delete. Restart the computer
Try then inserting the phone to a USB 2.0 port and allow the drivers to install. Make sure you are using the HTC cable!
This is how I fixed it anyways, hope it works for you!
Click to expand...
Click to collapse
I've done all that and after my PC won't install : USB MTP device, Android Phone
fenix71230 said:
Yes i can enter and see CWM, that's when my PC have detected it but won't install Android phone
Click to expand...
Click to collapse
Ok, that's either a driver version and/or adb version problem. get the latest HTC drivers and adb sdk. Are you on Win 8 or 8.1 by any chance? Maybe try a different PC.
Search the threads (or google), there are plenty of answers for that. Here's one, but I can't confirm it as I havent tried it:
http://forum.xda-developers.com/showthread.php?p=45415030#post45415030
http://forum.xda-developers.com/showthread.php?t=2256359
PS: don't forget to hit the thanks button if someone helped!
nkk71 said:
Ok, that's either a driver version and/or adb version problem. get the latest HTC drivers and adb sdk. Are you on Win 8 or 8.1 by any chance? Maybe try a different PC.
Search the threads (or google), there are plenty of answers for that. Here's one, but I can't confirm it as I havent tried it:
http://forum.xda-developers.com/showthread.php?p=45415030#post45415030
http://forum.xda-developers.com/showthread.php?t=2256359
PS: don't forget to hit the thanks button if someone helped!
Click to expand...
Click to collapse
I have tried with 3-4 different PC, using WIndows 7 64, WIndows 8, 8.1, always the same end (adb won't detect it)
Here on my PC I am on Windows 7 x64.
Maybe it's a phone hardware problem, I don't know what to do please help :crying:
fenix71230 said:
I have tried with 3-4 different PC, using WIndows 7 64, WIndows 8, 8.1, always the same end (adb won't detect it)
Here on my PC I am on Windows 7 x64.
Maybe it's a phone hardware problem, I don't know what to do please help :crying:
Click to expand...
Click to collapse
That worked ouff thanhs for all :
I have uninstall all HTC driver and HTCF Sync Manager, downloaded the latest HTC Sync Manger, installed it then uninstalled it, just remain new HTC drivers.
Then I took adb from HTC all_in_one kit 1.2, redo the commands and I pushed my rom on my sdcard.
Thanks a lot !!! :good:
fenix71230 said:
That worked ouff thanhs for all :
I have uninstall all HTC driver and HTCF Sync Manager, downloaded the latest HTC Sync Manger, installed it then uninstalled it, just remain new HTC drivers.
Then I took adb from HTC all_in_one kit 1.2, redo the commands and I pushed my rom on my sdcard.
Thanks a lot !!! :good:
Click to expand...
Click to collapse
:good::good:, glad everything worked out. Could I ask you to update the main thread title to include [SOLVED] so that others know is solved when they refer to it.
nkk71 said:
:good::good:, glad everything worked out. Could I ask you to update the main thread title to include [SOLVED] so that others know is solved when they refer to it.
Click to expand...
Click to collapse
How can I update the title ?
fenix71230 said:
How can I update the title ?
Click to expand...
Click to collapse
go to your first post and EDIT it, at the bottom of the edit window there's GO ADVANCED, once you click that you can see the main thread title and change it to include [SOLVED]
stovie_steve said:
I had pretty much the same problem as you for a long time and did the following:
Uninstalled everything to do with HTC - drivers, sync etc
Downloaded a program called USBDEVIEW (google it) and then install it. Make sure you run it as administrator. It will load all the drivers installed. At this point make sure the phone is not connected. Select all the HTC drivers and delete - anything that says android usb, htc, mtp device etc
Once thats done I went to C:\windows\system32\driverstore and theres a file there I think called info cache. Right clich and change the security so that you can edit the file and then delete. Restart the computer
Try then inserting the phone to a USB 2.0 port and allow the drivers to install. Make sure you are using the HTC cable!
This is how I fixed it anyways, hope it works for you!
Click to expand...
Click to collapse
THANK YOU THANK YOU THANK YOU!
Fixed finally!
Hello, I have a big problem on my htc one.
My phone reconnecting with vibration. I tried to install RUU, firmware... ADB is not working, I can only use Fastboot.
I tried to install clockworkmod recovery, but ADB is not working....
Please help me..
NedasAndrius said:
Hello, I have a big problem on my htc one.
My phone reconnecting with vibration. I tried to install RUU, firmware... ADB is not working, I can only use Fastboot.
I tried to install clockworkmod recovery, but ADB is not working....
Please help me..
Click to expand...
Click to collapse
What does "reconnecting with vibration mean"? The phone stopped vibrating?
aooga said:
What does "reconnecting with vibration mean"? The phone stopped vibrating?
Click to expand...
Click to collapse
No, phone show HTC one logo and restart...
NedasAndrius said:
No, phone show HTC one logo and restart...
Click to expand...
Click to collapse
Oh okay. If ADB isn't working, are you sure you installed the right drivers? You should be able to go into RUU mode and flash the RUU once the drivers are installed. Just search for the drivers here on XDA.
aooga said:
Oh okay. If ADB isn't working, are you sure you installed the right drivers? You should be able to go into RUU mode and flash the RUU once the drivers are installed. Just search for the drivers here on XDA.
Click to expand...
Click to collapse
I am installed HTC sync drivers.
Code:
adb devices
ADB error:device not found
NedasAndrius said:
I am installed HTC sync drivers.
Code:
adb devices
ADB error:device not found
Click to expand...
Click to collapse
can you check FAQ #2 in my guide if that's the problem.
fastboot devices only works in bootloader
adb devices only work in custom recovery or a booted ROM with USB debugging enabled
nkk71 said:
can you check FAQ #2 in my guide if that's the problem.
fastboot devices only works in bootloader
adb devices only work in custom recovery or a booted ROM with USB debugging enabled
Click to expand...
Click to collapse
But I have s-on...
NedasAndrius said:
But I have s-on...
Click to expand...
Click to collapse
i was only referring to FAQ #2 about how to fix drivers, so i don't need to post all if it again, but here you go (this applies to not only Win7, it's a general thingy when the drivers don't get installed properly in Windows):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
2) Q: I'm using Windows 7 what should I worry about
A: when you issue the command "fastboot boot CWM.img" (now only in CWM/TWRP restore method) there's a high chance drivers won't correctly install
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
-------------------------------------------------------------------------------------------------------------------------------------------
nkk71 said:
i was only referring to FAQ #2 about how to fix drivers, so i don't need to post all if it again, but here you go (this applies to not only Win7, it's a general thingy when the drivers don't get installed properly in Windows):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
2) Q: I'm using Windows 7 what should I worry about
A: when you issue the command "fastboot boot CWM.img" (now only in CWM/TWRP restore method) there's a high chance drivers won't correctly install
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
-------------------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
ADB don't working... Help me.
NedasAndrius said:
ADB don't working... Help me.
Click to expand...
Click to collapse
you need to clarify, ^^ that statement doesn't explain much.
when you are in custom recovery (TWRP or CWM), check Windows Device Manager -> does it show up correctly?
-> if yes, adb devices doesn't give you any output?
nkk71 said:
you need to clarify, ^^ that statement doesn't explain much.
when you are in custom recovery (TWRP or CWM), check Windows Device Manager -> does it show up correctly?
-> if yes, adb devices doesn't give you any output?
Click to expand...
Click to collapse
Enable the USB into your computer and turn off the phone. Only in this way come into recovery mode, and see my device maneger:
Enable fastboot mode, connect a USB and see:
What's problem?
NedasAndrius said:
Enable the USB into your computer and turn off the phone. Only in this way come into recovery mode, and see my device maneger:
Enable fastboot mode, connect a USB and see:
What's problem?
Click to expand...
Click to collapse
Well the screenshot of fastboot mode is good, but the other doesn't even show any connected device (was that taken while the phone was in recovery?)
Which recovery (name and version please) are you using?
nkk71 said:
Well the screenshot of fastboot mode is good, but the other doesn't even show any connected device (was that taken while the phone was in recovery?)
Which recovery (name and version please) are you using?
Click to expand...
Click to collapse
*** TAMPERED ***
*** UNLOCKED ***
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35AW923426
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4148mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Turning off the phone, I plug in a USB - phone is charging and automatically switches to recovery mode...
Going to bootloader >> recovery - DON'T WORKING! I have ping letters "Entering to recovery", but phone restarting...
I'm flashing ClockworkMod Recovery v6.0.3.3 (touch don't working), but recovery working.
I flashing openrecovery-twrp-2.6.3.3-m7 but don't working I see battery charging, but recovery does not turn - but I have:
Also newest clockworkmod recovery versions..
Also philz_touch_6.08.9-m7ul, but recovery working and i have unknown devices, but ADB don't working...
I click this image and see:
Unknown device in here:
NedasAndrius said:
*** TAMPERED ***
*** UNLOCKED ***
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35AW923426
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4148mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Turning off the phone, I plug in a USB - phone is charging and automatically switches to recovery mode...
Going to bootloader >> recovery - DON'T WORKING! I have ping letters "Entering to recovery", but phone restarting...
I'm flashing ClockworkMod Recovery v6.0.3.3 (touch don't working), but recovery working.
I flashing openrecovery-twrp-2.6.3.3-m7 but don't working I see battery charging, but recovery does not turn - but I have:
Also newest clockworkmod recovery versions..
Also philz_touch_6.08.9-m7ul, but recovery working and i have unknown devices, but ADB don't working...
I click this image and see:
Unknown device in here:
Click to expand...
Click to collapse
only reason I asked is cause TWRP 2.7.0.0 seems to have problems with adb, the other ones should work
now update that "Unknown USB device" as I mentioned before (by manually selecting My HTC)
BTW, USB 2 ports are preferred!
nkk71 said:
only reason I asked is cause TWRP 2.7.0.0 seems to have problems with adb, the other ones should work
now update that "Unknown USB device" as I mentioned before (by manually selecting My HTC)
BTW, USB 2 ports are preferred!
Click to expand...
Click to collapse
I can't update drivers:
NedasAndrius said:
I can't update drivers:
Click to expand...
Click to collapse
Don't use "have disk", just unselect "Show compatible hardware", then Android USB Devices -> My HTC
nkk71 said:
Don't use "have disk", just unselect "Show compatible hardware", then Android USB Devices -> My HTC
Click to expand...
Click to collapse
I can not find "Android USB Devices":
NedasAndrius said:
I can not find "Android USB Devices":
Click to expand...
Click to collapse
in that window, go to HTC ..... -> My HTC
nkk71 said:
in that window, go to HTC ..... -> My HTC
Click to expand...
Click to collapse
I know, but there is nothing related to HTC or ANDROID.
NedasAndrius said:
I know, but there is nothing related to HTC or ANDROID.
Click to expand...
Click to collapse
Question 1: so nothing like this:
and question 2: the instructions in post #8 don't work?
.
Android wear runs, well android.
I would like to request that someone that has a wear to dump the rom that is preinstalled on it, and to make note if there it prompts for an ota on first setup.
I don't know how to enable adb on it, but I would expect that it would be available, for the moment merely doing a
Code:
adb pull /system
will be as much as anyone can expect.
In the event it actually supports fastboot, I'd also like to request a
Code:
fastboot get-var all
Enabling debugging is pretty simple:
Settings -> About -> Tap the build number 7 (I think) times.
Enable debugging.
Allow debugging from the prompt that appears on the paired device.
I was able to do a system dump and will post it as soon as I have developer status on Android File Host.
I was unable to run the fastboot command though. It seems you need to have the device actively connected in order to authorize adb access.
Here's a link to the dump: http://www.androidfilehost.com/?fid=23501681358554418
unkillable_thrill said:
I was unable to run the fastboot command though. It seems you need to have the device actively connected in order to authorize adb access.
Click to expand...
Click to collapse
If you already have adb access, you can also do
Code:
adb shell getprop ro.boot.bootloader
for the same results.
Could you also list the model number?
It's SM-??? something, there's pictures of the back of the device, but the ones I saw were too blurry to make it out.
Here is the first part of the build.prop and the bootloader. It just says "NF5"
Code:
> adb -s localhost:4444 shell getprop ro.boot.bootloader
NF5
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KMV78N
ro.build.display.id=KMV78N
ro.build.version.incremental=1245698
ro.build.version.sdk=20
ro.build.version.codename=REL
ro.build.version.release=4.4W
ro.build.date=Mon Jun 23 21:00:37 UTC 2014
ro.build.date.utc=1403557237
ro.build.type=user
ro.build.user=android-build
ro.build.host=kpfk1.cbf.corp.google.com
ro.build.tags=release-keys
ro.product.model=Gear Live
ro.product.brand=samsung
ro.product.name=sprat
ro.product.device=sprat
ro.product.board=SPRAT
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Samsung
ro.wifi.channels=
ro.board.platform=msm8226
# ro.build.product is obsolete; use ro.product.device
ro.build.product=sprat
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=sprat-user 4.4W KMV78N 1245698 release-keys
ro.build.fingerprint=samsung/sprat/sprat:4.4W/KMV78N/1245698:user/release-keys
ro.build.characteristics=nosdcard,watch
# end build properties
I can do a dump, but it takes far too long and i have a busy day today, if I have time later ill try to do a full dump and put it up on Mega
I would appreciate if either if you two could do a dump, if it means having to wait that's perfectly acceptable.
Edit:
Daegalus said:
Code:
ro.build.date=Mon Jun 23 21:00:37 UTC 2014
Click to expand...
Click to collapse
Do you know if your gear live/the one you had access too had an ota? that's very new for a rom, it seems like it already recieved an ota due to the age
I don't know. I got it an Google I/O on Thursday. Also when I first turned it on, I think it got an update of some sort when it did the first sync so I think it had some kind of initial OTA applied.
I think i might have some time in a bit to do a full dump of /system I'll try to get it done quickly.
[Edit] I will also try to get it into Fastboot and see if I can do a proper full dump. Im just a little hesitant as I wouldn't know how I would interface with fastboot as the watch requires a connection through the phone's bluetooth to do ADB. I don't know if I can connect a USB directly to it through the adapter and do actual fastboot operations.
Daegalus said:
I don't know. I got it an Google I/O on Thursday. Also when I first turned it on, I think it got an update of some sort when it did the first sync so I think it had some kind of initial OTA applied.
Click to expand...
Click to collapse
If anyone happens to get a gear live that has not been turned on yet, could you attempt to get the rom before it connects to the internet?
I have no idea what the pair process is, so I cant provide any advice to that end.
TheManii said:
If anyone happens to get a gear live that has not been turned on yet, could you attempt to get the rom before it connects to the internet?
I have no idea what the pair process is, so I cant provide any advice to that end.
Click to expand...
Click to collapse
If I remember the pair process right, I don't think you will be able to. Its before you get a chance to turn on any sort of debugging mode. It force updates the device and reboots it. You'd have to find a way to make it kill the pair process and fall to the home screen. Got to about, tap the build number 7 times, then turn on Debug over bluetooth, turn on debug over bluetooth on the app, then do it.
Neither of these options are available until the full pairing process completes, which is after the update.
Daegalus said:
If I remember the pair process right, I don't think you will be able to. Its before you get a chance to turn on any sort of debugging mode. It force updates the device and reboots it. You'd have to find a way to make it kill the pair process and fall to the home screen. Got to about, tap the build number 7 times, then turn on Debug over bluetooth, turn on debug over bluetooth on the app, then do it.
Neither of these options are available until the full pairing process completes, which is after the update.
Click to expand...
Click to collapse
That sounds effectively like the setup for the 2013 N7, you need to modify the rom to bypass that, or make it think you already finished the setup process.
Both of which requires fastboot to bypass via a custom recovery. I expect that you can eventually flash a custom recovery on a wear, but not simply with fastboot.
Well once i finish this system dump, I will try to get it into fastboot with "adb reboot bootloader" or something. Hopefully Samsung hasnt done the usual thing and locked it down like a high security prison.
---------- Post added at 05:04 PM ---------- Previous post was at 04:16 PM ----------
I did this dump on Windows, I just replaced my macbook so I havent got it setup to do any of this, so I resorted to my windows machine. Heads up incase it causes file permissions to be off.
Samsung Gear Live /system dump: https://mega.co.nz/#!SVACgawC!sFYfSgvLOIdwlDyP_r-7voggecZNwRkrnarQ4Y_SZkU
fastboot getvar all:
Code:
PS C:\Users\Yulian\Desktop\SamsungGearLive> fastboot getvar all
(bootloader) console:disable
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:true
(bootloader) unlocked:false
(bootloader) secure-boot:yes
(bootloader) version-baseband:NONE
(bootloader) version-bootloader:SPRAT.NF5
(bootloader) version-hardware:4
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:persist:ext4
(bootloader) partition-size:persist: 0x700000
(bootloader) partition-type:recovery:ext4
(bootloader) partition-size:recovery: 0xa00000
(bootloader) partition-type:boot:ext4
(bootloader) partition-size:boot: 0xa00000
(bootloader) partition-type:aboot:ext4
(bootloader) partition-size:aboot: 0x200000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xc800000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xc14abe00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x10000000
(bootloader) serialno:R3AF600G54J
(bootloader) kernel:lk
(bootloader) product:sprat
all:
finished. total time: 1.251s
I will see if I can dump anything from fastboot.
---------- Post added at 05:17 PM ---------- Previous post was at 05:04 PM ----------
For anyone else with a Samsung Gear Live, here are the steps to get it setup.
1. Enable Debug over Bluetooth.
2. Enable debugging in the Android Wear app on your phone.
3. Use the instructions here: https://developer.android.com/training/wearables/apps/bt-debugging.html to setup a connection to the watch through the phone BT.
4. You should have adb access now, and you can run 'adb reboot bootloader'
5. Once booted into the bootloader you, you can connect the USB adapter to the back of the watch and hook it up directly to a computer and run normal fastboot commands on it. Including 'fastboot oem unlock'. I havent run this yet, but wouldn't see why it couldn't be done. This should allow flashing of custom recoveries.
The watch has a standard android recovery and bootloader enhanced with touch support so you can navigate them with swipes. I'll post pictures once my phone charges a bit.
Daegalus said:
If I remember the pair process right, I don't think you will be able to. Its before you get a chance to turn on any sort of debugging mode. It force updates the device and reboots it. You'd have to find a way to make it kill the pair process and fall to the home screen. Got to about, tap the build number 7 times, then turn on Debug over bluetooth, turn on debug over bluetooth on the app, then do it.
Neither of these options are available until the full pairing process completes, which is after the update.
Click to expand...
Click to collapse
Is adb over USB expected to work? I tried in the pre-pair state, and two different computers both failed to detect the device as a USB device at all.
I kind of suspect that, before the initial pairing, the device has an extremely limited image installed. But there are five USB pins, so presumably the device contains USB gadget hardware.
I have not been able to do ADB over USB. It does have data bit. I did fastboot over usb, as there is no bluetooth when in the bootloader. So it is possible to do data over usb, not just power.
The issue is, when you are booted into android, it doesn't let you do ADB over USB, at least not by default or with the options given to you. I can only do over Bluetooth.
I think what Manii said earlier applies. We won't be able to do anything to bypass the forced update or hookup adb unless we get custom recovery on it and do a custom bypass like the 2013 N7
Here is an image of the bootloader:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm not at all surprised that it has a standard android recovery, as it's a goog rom device.
The issue is if you can return to fastboot without adb, what if you broke the rom and cant boot.
If anyone seriously want to dump the initial rom though: you'd both have to wait until a recovery is ported (whenever that is, due to dev interest) and also obviously cant pair it until then.
We have dumps of the initial roms for the 2013 n7 and N5 this way, but I dont really expect as many wear users.
Also @TheManii , you mentioned earlier you wanted the model off the back. Its SM-R382 on mine.
Can someone please make a quick port of this to the Original gear? It's pretty much the same and I would be willing to test. Had to ask here since there is not much going on in the Gear Forums.
uvbeenzaned said:
Can someone please make a quick port of this to the Original gear? It's pretty much the same and I would be willing to test. Had to ask here since there is not much going on in the Gear Forums.
Click to expand...
Click to collapse
I second this... Would love it on my OG Gear
Sent from my Nexus 5 using Tapatalk
Ep3n3wp said:
I second this... Would love it on my OG Gear
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I would love this to!
By the looks of it the Gear 1 originally ran 4.2.2 (JDQ39), the Gear live runs 4.4W (KMV78N).
The Gear 1 also has an exynos 4 and the Gear live is a snapdragon S400.
They're different enough that it's like asking to port KK to any abritrary android device.
You may as well be asking someone to port tizen to the N10.
It's not impossible for either case, but it's nowhere as easy as it sounds.
TheManii said:
By the looks of it the Gear 1 originally ran 4.2.2 (JDQ39), the Gear live runs 4.4W (KMV78N).
The Gear 1 also has an exynos 4 and the Gear live is a snapdragon S400.
They're different enough that it's like asking to port KK to any abritrary android device.
You may as well be asking someone to port tizen to the N10.
It's not impossible for either case, but it's nowhere as easy as it sounds.
Click to expand...
Click to collapse
Well could you do it for us? You sound like you know what you're doing. There can be a PayPal donation involved.
Sent from my Nexus 5 using Tapatalk
The system doesn't matter nearly as much as the kernel.
OK. I'm looking for any ideas from anyone who either hasn't previously had some kind of input on this topic, or who has a new idea for me to try to fix my problem. NOTE: Not trying to be rude here. Just looking for some fresh perspectives.
I have a Sprint HTC One m7 (m7wls). I am currently using tdhite's TWRP version 2.7.1.3. I've tried TWRP versions all the way back to 2.6.3.0. Backup and restore functions work fine for me, but I have been unable to flash any ROMs (4.4.4 variants, 4.3 variants and even 4.2 variants, including Sense-based ROMs and AOSP ROMs) since soft bricking my phone this past weekend and restoring with an RUU.
The bricking appeared to have happened when I installed tdhite's TWRP 2.7.1.3, though it was honestly a late night and it is equally possible I accidentally erased my internal storage after installing tdhite's TWRP 2.7.1.3. I do remember definitely that after flashing TWRP 2.7.1.3, my phone rebooted itself and started up as if it was brand new out of the box with a fresh install. I turned the phone back off as I planned to flash a custom ROM I had downloaded, but when I got back into TWRP either the internal drive had already been wiped or I accidentally wiped it when selecting options in the advanced wipe menu.
Either way, the bricking happened and was resolved, but now after unlocking the bootloader and flashing various versions of both TWRP and CWM, I am unable to flash any ROMs, Kernels, radios, etc. The only thing I have been able to flash is the UPDATE.zip file generated by Avast Anti-Theft (Rooted).
I've gone back as far as TWRP 2.6.3.0 (since I read it is still the most stable version for the m7wls), and none of them are useful, except for creating nandroid backups and for restoring. Backup and restore functions work just fine.
This is the error it throws everytime:
Updating partition details...
Full SELinux support is present
Setting performance mode ON.
E: Unable to open zip file.
Setting performance mode OFF.
Error flashing zip '/sdcard/Download/(file name)
Updating partition details
Here is the information that shows when I am in Fastboot USB mode:
M7_WLS PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-1.01.20.0515
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
May 15, 2014, 16:31:22.0
So for now, I'm stuck on stock 4.4.2. I'm rooted and using Xposed framework to get by, but I really miss playing around with ROMs and Kernels.
I've read something about possibly the file system being corrupted, but don't know for sure if that is the case. Everything seems to be working fine in stock 4.4.2.
Any comments, thoughts or general scolding for something dumb I may have done would be greatly appreciated as long as it winds up being productive. Thanks to all you folks at XDA in advance. I know if there's a problem, it is likely to be solved here.
Supplemental information:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0515
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXXXXXXXXX
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4127mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Anything particularly wrong with your other threads??
MarkBell said:
Setting performance mode ON.
E: Unable to open zip file.
Setting performance mode OFF.
Click to expand...
Click to collapse
Don't know about "performance mode", but the one in red indicates a bad zip, have you checked MD5?
MarkBell said:
OK. I'm looking for any ideas from anyone who either hasn't previously had some kind of input on this topic
Click to expand...
Click to collapse
Noted
nkk71 said:
Anything particularly wrong with your other threads??
Don't know about "performance mode", but the one in red indicates a bad zip, have you checked MD5?
Noted
Click to expand...
Click to collapse
nkk71: Not a huge fan of your negative attitude, but I can understand your annoyance for the multiple threads and lack of information in the other couple posts. I felt like starting this one off on the right foot so anyone helpful could have all the pertinent information from the get-go. I guess I could have edited my first post in the other threads, but one of them had gotten off topic (my own fault actually so understand annoyance about that, too). I basically wanted to simplify it here. I appreciate your willingness to help, but I would rather have someone who is courteous (like clsA) instead of someone with a superiority complex who makes assumptions that anyone who asks a question is an idiot who doesn't know anything.
I know how to flash ROMs through TWRP. I know how to unlock and relock bootloaders, I know how to push things through ADB. I know how to flash recoveries through TWRP. I know how to check MD5s. I know how to recover from soft bricks with RUUs. I've been lurking on XDA for years, but never really started posting much until very recently now that I have run into a problem. I've described the problem above in great detail.
I'm not here to attention seek. I'm here to learn because I can admit I don't know everything.
I'm here to get help with my problem, and the majority of folks I've come across on XDA are very nice while giving great advice to fix problems.
Please be courteous and don't assume, and I promise I will be thankful for any productive advice you may give, and supply you with any information you need. Hope you are mature enough to admit you've had kind of a nasty attitude from the outset and that we can move past this and get to work on the problem. I am mature enough for ask for your forgiveness for anything that I may have done to upset you and/or offend you.
I should note that it is not just ROMs that I'm having trouble flashing. I also can't flash radios or kernels.The same radios and kernels and ROMs I was able to flash prior to the soft bricking this past weekend, I can now no longer flash.
MarkBell said:
nkk71: Not a huge fan of your negative attitude
, but I can understand your annoyance for the multiple threads and lack of information in the other couple posts. I felt like starting this one off on the right foot so anyone helpful could have all the pertinent information from the get-go. I guess I could have edited my first post in the other threads, but one of them had gotten off topic (my own fault actually so understand annoyance about that, too). I basically wanted to simplify it here. I appreciate your willingness to help, but I would rather have someone who is courteous (like clsA) instead of someone with a superiority complex who makes assumptions that anyone who asks a question is an idiot who doesn't know anything.
I know how to flash ROMs through TWRP. I know how to unlock and relock bootloaders, I know how to push things through ADB. I know how to flash recoveries through TWRP. I know how to check MD5s. I know how to recover from soft bricks with RUUs. I've been lurking on XDA for years, but never really started posting much until very recently now that I have run into a problem. I've described the problem above in great detail.
I'm not here to attention seek. I'm here to learn because I can admit I don't know everything.
I'm here to get help with my problem, and the majority of folks I've come across on XDA are very nice while giving great advice to fix problems.
Please be courteous and don't assume, and I promise I will be thankful for any productive advice you may give, and supply you with any information you need. Hope you are mature enough to admit you've had kind of a nasty attitude from the outset and that we can move past this and get to work on the problem. I am mature enough for ask for your forgiveness for anything that I may have done to upset you and/or offend you.
I should note that it is not just ROMs that I'm having trouble flashing. I also can't flash radios or kernels.The same radios and kernels and ROMs I was able to flash prior to the soft bricking this past weekend, I can now no longer flash.
Click to expand...
Click to collapse
yep, sorry if i came across as a negative attitude person, with a superiority complex, immature, and made the impression of implying you are "an idiot" --> I DID NOT!!
i do not think anybody is an idiot, and am very convinced most (if not all) people can accomplish all this by themselves, just sometimes need a nudge in the right direction.
i didn't mean to belittle you by suggesting an MD5 check, but from the error message you posted above, it looked like a bad zip; maybe it's not even a flashable zip, but given I don't know what you are flashing (hence i mentioned posting a link), i can't really say.
anyway, it's obvious, we started out on the wrong foot here, and i'm not welcome here. (i can't blame you), but wish you good luck!!
@clsA @alray @SaHiLzZ, @Danny201281, @Seanie280672, @majmoz , can you help him out
thanks
nkk71 said:
yep, sorry if i came across as a negative attitude person, with a superiority complex, immature, and made the impression of implying you are "an idiot" --> I DID NOT!!
i do not think anybody is an idiot, and am very convinced most (if not all) people can accomplish all this by themselves, just sometimes need a nudge in the right direction.
i didn't mean to belittle you by suggesting an MD5 check, but from the error message you posted above, it looked like a bad zip; maybe it's not even a flashable zip, but given I don't know what you are flashing (hence i mentioned posting a link), i can't really say.
anyway, it's obvious, we started out on the wrong foot here, and i'm not welcome here. (i can't blame you), but wish you good luck!!
@clsA @alray @SaHiLzZ, @Danny201281, @Seanie280672, @majmoz , can you help him out
thanks
Click to expand...
Click to collapse
@nkk71: I am sorry, too. I can be a bit sensitive. Especially since I've been sleep deprived for the last several months. I am actually scheduled for a sleep study in a couple of weeks because I've been falling asleep throughout the day, lucid dreaming and having terrifying episodes of sleep paralysis. Not to mention waking several times per night. This is why I kind of second guess whether tdhite's latest TWRP for the Sprint m7 really caused the problem or if maybe I, while half asleep, erased my internal storage.
All of this has made me a bit irritable to say the least and very sensitive to things I wouldn't normally be sensitive, too. Let's chalk this up to a bad start and get things going in the right direction. I would more than appreciate your help now that we have cleared the air.
Here are the zips I've tried to flash:
LiquidSmoothv.3.2 for m7spr: http://forum.xda-developers.com/showthread.php?t=2647850
Beanstalk for m7spr: http://forum.xda-developers.com/showthread.php?t=2443156
The latest radio (even though I know I already have it because I got the dialer process error on one startup and thought it might help to flash it again. It has not recurred, though.
Latest Pacman rom nightly and the old 4.3RC1 based version: http://forum.xda-developers.com/showthread.php?t=2443156
ViperOne ROM 7.0.
Prior to my soft bricking the phone, I used liquidsmooth and beanstalk with no problems except for a GPS issue. I've used SlipperySlothv2 Kernel with both liquidsmooth and beanstalk in the past and liked it, but was looking forward to trying out this GPS fix I've read about with those ROMS (the one where you just boot up a stock ROM and make sure you have GPS enabled before your restart into recovery and wipe and flash the new ROM you want to use).
ElementalX for sense 6, 4.4.2 I tried flashing but could never get it to stick, even before the soft bricking. I think it is because I didn't have S-off, though and I was using the stock 4.4.2 ROM when I tried flashing it.
nkk71 said:
yep, sorry if i came across as a negative attitude person, with a superiority complex, immature, and made the impression of implying you are "an idiot" --> I DID NOT!!
i do not think anybody is an idiot, and am very convinced most (if not all) people can accomplish all this by themselves, just sometimes need a nudge in the right direction.
i didn't mean to belittle you by suggesting an MD5 check, but from the error message you posted above, it looked like a bad zip; maybe it's not even a flashable zip, but given I don't know what you are flashing (hence i mentioned posting a link), i can't really say.
anyway, it's obvious, we started out on the wrong foot here, and i'm not welcome here. (i can't blame you), but wish you good luck!!
@clsA @alray @SaHiLzZ, @Danny201281, @Seanie280672, @majmoz , can you help him out
thanks
Click to expand...
Click to collapse
Well I guess I'm out of ideas too as he ask for a fresh perspective. @MarkBell I accept the compliment but i really am Stumped at this point. I guess the good part is you do have a working phone, just not the exact way you want it.
clsA said:
Well I guess I'm out of ideas too as he ask for a fresh perspective. @MarkBell I accept the compliment but i really am Stumped at this point. I guess the good part is you do have a working phone, just not the exact way you want it.
Click to expand...
Click to collapse
That is very true and I am grateful to you, as well. I can always backup and restore. Maybe the next TWRP that comes out down the road will rectify. I wonder if someone made a backup of liquidsmooth or beanstalk with a custom kernel if I could restore it to my phone through TWRP? If so, I could try to find a buddy with an HTC One m7 in my area. lol. It would have to be someone trustworthy though. haha.
Well as nk771 suggested this error normally means a bad zip, so assuming you've checked the md5 and it is correct. This can also occur with a zip sitting in a bad memory block on your phone.
Have you tried using the Format Data option in TWRP to reformat your flash partitions. (warning this will wipe everything from your phone, Including Rom and and Internal Storage(sd card).
Then push and try flashing your rom.
Also using e2fsck to check your partitions could be an option. And probably worth trying first as it may solve the problem without needing to Format Data.
With the phone in recovery, connect usb and unmount all partitions then type
Code:
adb shell
e2fsck -fvy dev/block/mmcblk0p37
e2fsck -fvy dev/block/mmcblk0p38
e2fsck -fvy dev/block/mmcblk0p39
exit
This should repair any bad blocks allowing you to store and flash to error free memory.
Edit:- Didn't see the other posts guess you probably already tried these suggestions. I'll take a look through your other threads but if these guys are stumped it's not looking good.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
MarkBell said:
Not a huge fan of your negative attitude
I would rather have someone who is courteous instead of someone with a superiority complex who makes assumptions that anyone who asks a question is an idiot who doesn't know anything.
Click to expand...
Click to collapse
WOW Seriously!? nkk71 is one of the most helpful guy in this forum, spending many hours each day here to help people. He have written the most comprehensible and detailed guide on this forum to help "idiot who doesn't know anything" restoring their phones. I don't think someone with a "superiority complex" will be here spending that huge amount of time and effort to help ppl unbrick their phones, write and maintain guides and share knowledge. No disrespect mate but maybe (probably) you have misinterpreted something he said...
Danny201281 said:
Well as nk771 suggested this error normally means a bad zip, so assuming you've checked the md5 and it is correct. This can also occur with a zip sitting in a bad memory block on your phone.
Have you tried using the Format Data option in TWRP to reformat your flash partitions. (warning this will wipe everything from your phone, Including Rom and and Internal Storage(sd card).
Then push and try flashing your rom.
Also using e2fsck to check your partitions could be an option. And probably worth trying first as it may solve the problem without needing to Format Data.
With the phone in recovery, connect usb and unmount all partitions then type
Code:
adb shell
e2fsck -fvy dev/block/mmcblk0p37
e2fsck -fvy dev/block/mmcblk0p38
e2fsck -fvy dev/block/mmcblk0p39
exit
This should repair any bad blocks allowing you to store and flash to error free memory.
Edit:- Didn't see the other posts guess you probably already tried these suggestions. I'll take a look through your other threads but if these guys are stumped it's not looking good.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
When trying that in command prompt, I am getting error device not found. Tried switching USB ports and the issue persists. Is this any different than using the repair function available in TWRP? I have tried that to no effect, unfortunately. I double checked my drivers and they appear to be installed correctly.1.0.0.17
alray said:
WOW Seriously!? nkk71 is one of the most helpful guy in this forum, spending many hours each day here to help people. He have written the most comprehensible and detailed guide on this forum to help "idiot who doesn't know anything" restoring their phones. I don't think someone with a "superiority complex" will be here spending that huge amount of time and effort to help ppl unbrick their phones, write and maintain guides and share knowledge. No disrespect mate but maybe (probably) you have misinterpreted something he said...
Click to expand...
Click to collapse
Agreed, apologized profusely and posted explanation above.
I haven't tried using the Format Data option in TWRP to reformat yet. The problem is I can never get either my Mac or PC to recognize my phone while in ADB sideload.
MarkBell said:
When trying that in command prompt, I am getting error device not found. Tried switching USB ports and the issue persists. Is this any different than using the repair function available in TWRP? I have tried that to no effect, unfortunately. I double checked my drivers and they appear to be installed correctly.
Click to expand...
Click to collapse
The repair function in twrp uses e2fsck, you can even run the commands in the twrp terminal. But if it finds a major problem. The twrp terminal will tell you it can't carry out interactive repairs, please use a pc with adb terminal. Or something like that.
So running it from the pc is a better option.
Have you tried Linux to use adb/fastboot on your phone. Linux doesn't require drivers. And can be booted from a usb stick so you don't need to alter your Windows installation at all.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
---------- Post added at 09:41 PM ---------- Previous post was at 09:39 PM ----------
MarkBell said:
I haven't tried using the Format Data option in TWRP to reformat yet. The problem is I can never get either my Mac or PC to recognize my phone while in ADB sideload.
Click to expand...
Click to collapse
Don't format data if adb isn't working and you don't have an otg. You will lose your backup.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
MarkBell said:
I haven't tried using the Format Data option in TWRP to reformat yet. The problem is I can never get either my Mac or PC to recognize my phone while in ADB sideload.
Click to expand...
Click to collapse
you should follow step two of the FAQ here >http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
to get adb working on your windows PC
Danny201281 said:
The repair function in twrp uses e2fsck, you can even run the commands in the twrp terminal. But if it finds a major problem. The twrp terminal will tell you it can't carry out interactive repairs, please use a pc with adb terminal. Or something like that.
So running it from the pc is a better option.
Have you tried Linux to use adb/fastboot on your phone. Linux doesn't require drivers. And can be booted from a usb stick so you don't need to alter your Windows installation at all.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
---------- Post added at 09:41 PM ---------- Previous post was at 09:39 PM ----------
Don't format data if adb isn't working and you don't have an otg. You will lose your backup.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
I'll get a Linux bootable and try the repair function and report back. I actually back up my backups to my PC now. Learned that lesson the hard way. I'll never lose a backup completely ever again. I even back it up to my Cloud services.
MarkBell said:
I'll get a Linux bootable and try the repair function and report back.
Click to expand...
Click to collapse
Look here
http://forum.xda-developers.com/showthread.php?p=54272479
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Danny201281 said:
Look here
http://forum.xda-developers.com/showthread.php?p=54272479
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
Thanks! Using a dual boot Mac running Windows 7 32-bit and Mavericks so I guess I'll need the i386 architecture, right? Or does it even matter?
MarkBell said:
Thanks! Using a dual boot Mac running Windows 7 32-bit and Mavericks so I guess I'll need the i386 architecture, right? Or does it even matter?
Click to expand...
Click to collapse
yes the x86 is preferred
MarkBell said:
Thanks! Using a dual boot Mac running Windows 7 32-bit and Mavericks so I guess I'll need the i386 architecture, right? Or does it even matter?
Click to expand...
Click to collapse
To be honest I don't know a lot about Mac's but as far as I'm aware you can boot a Linux live usb on a Mac.
Hopefully someone can clarify ?
@MarkBell http://www.howtogeek.com/187410/how-to-install-and-dual-boot-linux-on-a-mac/
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Danny201281 said:
Well as nk771 suggested this error normally means a bad zip, so assuming you've checked the md5 and it is correct. This can also occur with a zip sitting in a bad memory block on your phone.
Have you tried using the Format Data option in TWRP to reformat your flash partitions. (warning this will wipe everything from your phone, Including Rom and and Internal Storage(sd card).
Then push and try flashing your rom.
Also using e2fsck to check your partitions could be an option. And probably worth trying first as it may solve the problem without needing to Format Data.
With the phone in recovery, connect usb and unmount all partitions then type
Code:
adb shell
e2fsck -fvy dev/block/mmcblk0p37
e2fsck -fvy dev/block/mmcblk0p38
e2fsck -fvy dev/block/mmcblk0p39
exit
This should repair any bad blocks allowing you to store and flash to error free memory.
Edit:- Didn't see the other posts guess you probably already tried these suggestions. I'll take a look through your other threads but if these guys are stumped it's not looking good.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
OK. This unfortunately didn't work. Any next steps?
Here is the log:
Code:
~ # e2fsck -fvy dev/block/mmcblk0p37
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
2593 inodes used (2.18%)
35 non-contiguous files (1.3%)
4 non-contiguous directories (0.2%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 2508
450462 blocks used (94.81%)
0 bad blocks
0 large files
2426 regular files
81 directories
0 character device files
0 block device files
0 fifos
0 links
77 symbolic links (77 fast symbolic links)
0 sockets
--------
2584 files
~ # e2fsck -fvy dev/block/mmcblk0p38
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
dev/block/mmcblk0p38: ***** FILE SYSTEM WAS MODIFIED *****
18 inodes used (0.04%)
0 non-contiguous files (0.0%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 10
5266 blocks used (3.21%)
0 bad blocks
0 large files
5 regular files
4 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
9 files
~ # e2fsck -fvy dev/block/mmcblk0p39
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
37742 inodes used (2.21%)
2017 non-contiguous files (5.3%)
26 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 37281/37
2411604 blocks used (35.38%)
0 bad blocks
1 large file
33245 regular files
4057 directories
0 character device files
0 block device files
6 fifos
0 links
418 symbolic links (403 fast symbolic links)
7 sockets
--------
37733 files
~ # exit