I am trying to recover my HTCone m7 from this stuck logo screen upon lunch. At this point I want to get s-off in order to RUU my phone. The bagillion potential fixes online have lead me to believe that i need to push Android Rev HD in order to add firewater which will grant me s-OFF, allowing me to run the RUUexe. following>>>>>htc-one.wonderhowto.com/how-to/set-your-htc-one-s-off-using-firewater-any-computer-015123
NOW i need to use abd but it wont connect for s--t. I'm guessing its because my computer is referencing the drivers from system32 but when i move my platform-tools folder to systems32 i get "...adbwinapi.dll file missing" or somethiing like that.
My question. How do i get ADB working from system32?
tacoDawg said:
NOW i need to use abd but it wont connect for s--t. I'm guessing its because my computer is referencing the drivers from system32 but when i move my platform-tools folder to systems32 i get "...adbwinapi.dll file missing" or somethiing like that.
My question. How do i get ADB working from system32?
Click to expand...
Click to collapse
Don't know why you think you have to do this. Adb doesnt have to be executed from system32. You can execute it from anywhere as long that all files are in the same folder (adb.exe, fastboot.exe and their related dynamic link library like adbwinapi.dll and adbwinusbapi.dll)
You also need your HTC drivers correctly installed on your computer.
ADB commands will only work from a custom recovery or from a booted OS with usb debug enabled.
Fastboot commands are used from bootloader mode.
Jxt. said:
Hello there, you do not need to have your adb folder in your system 32 folder in order to work. Instead, try moving it to the root of your Hard drive, so that it looks like C:/adb then try it from there. Tell me if that works
Click to expand...
Click to collapse
well moving the abd folder to the C drive did get fastboot working without the "adbwinapi.dll file missing" error but adb just wont connect. Its showing up in device manager as "ACER composite ADB Interface" and in Driver File Details its pulling files from system32.
Jxt. said:
Hello there, you do not need to have your adb folder in your system 32 folder in order to work. Instead, try moving it to the root of your Hard drive, so that it looks like C:/adb then try it from there. Tell me if that works
Click to expand...
Click to collapse
alray said:
Don't know why you think you have to do this. Adb doesnt have to be executed from system32. You can execute it from anywhere as long that all files are in the same folder (adb.exe, fastboot.exe and their related dynamic link library like adbwinapi.dll and adbwinusbapi.dll)
You also need your HTC drivers correctly installed on your computer.
ADB commands will only work from a custom recovery or from a booted OS with usb debug enabled.
Fastboot commands are used from bootloader mode.
Click to expand...
Click to collapse
i thought the adb.exe and the driver needed to be in the same place for some reason... Ive switched out the htc drivers a gazillion times i dont think thats the issue..or maybe it is..... all i know is ADB refuses to cooperate.
tacoDawg said:
i thought the adb.exe and the driver needed to be in the same place for some reason... Ive switched out the htc drivers a gazillion times i dont think thats the issue..or maybe it is..... all i know is ADB refuses to cooperate.
Click to expand...
Click to collapse
You might try and start over.
** Uninstall the HTC driver from your computer and reboot.
** Download and install the latest HTC drivers. Do not install Sync or remove it after it installed.
** Download and install ADB & Fastboot in your root drive
** Assuming you can boot your phone normally, check Settings >> Developer options >> USB Debugging must have a check by it showing it is enabled.
** Now connect the phone to the computer and type the following in a cmd window:
Code:
adb devices
You should see your serial number in the cmd window.
Now type:
Code:
adb reboot bootloader
You should see the bootloader screen on your phone.
** Using the pwr and vol buttons select Recovery assuming a custom recovery is installed
** While at Recovery's main screen, type:
Code:
adb devices
You should see your serial number and next to it recovery Now you should be able to run the adb commands that you desire.
You mention that you want to run a RUU and that is why you want to s-off! If the RUU is the same version or higher you can run it as long as your bootloader is locked/relocked. If it is lower or a different version then you need s-off.
majmoz said:
You might try and start over.
** Uninstall the HTC driver from your computer and reboot.
** Download and install the latest HTC drivers. Do not install Sync or remove it after it installed.
** Download and install ADB & Fastboot in your root drive
** Assuming you can boot your phone normally, check Settings >> Developer options >> USB Debugging must have a check by it showing it is enabled.
** Now connect the phone to the computer and type the following in a cmd window:
Code:
adb devices
You should see your serial number in the cmd window.
Now type:
Code:
adb reboot bootloader
You should see the bootloader screen on your phone.
** Using the pwr and vol buttons select Recovery assuming a custom recovery is installed
** While at Recovery's main screen, type:
Code:
adb devices
You should see your serial number and next to it recovery Now you should be able to run the adb commands that you desire.
You mention that you want to run a RUU and that is why you want to s-off! If the RUU is the same version or higher you can run it as long as your bootloader is locked/relocked. If it is lower or a different version then you need s-off.
Click to expand...
Click to collapse
ive tried starting from scratch.. i have this RemoveOldHTCDriver3.exe that ive run but i dont know if that does the trick.. also what about the adb drivers? how would i remove those?
my phone is stuck at the launch screen, RUU seems like it would fix this.. so if i dont need s-off when i run the RUU why dose it stick at sending evvvvverrrrryyyyyyyyy eeeeffffiiiinnnnggggggg time?
Im going to try downloading another newer RUU maybe that will work..
thanks btw.
tacoDawg said:
ive tried starting from scratch.. i have this RemoveOldHTCDriver3.exe that ive run but i dont know if that does the trick.. also what about the adb drivers? how would i remove those?
my phone is stuck at the launch screen, RUU seems like it would fix this.. so if i dont need s-off when i run the RUU why dose it stick at sending evvvvverrrrryyyyyyyyy eeeeffffiiiinnnnggggggg time?
Im going to try downloading another newer RUU maybe that will work..
thanks btw.
Click to expand...
Click to collapse
To remove the HTC drivers go into Control Panel >> Programs and Features >> find HTC Drivers and highlight then select uninstall. To remove the adb and fastboot just delete the folder but save your files that are to be flashed or pushed to another folder first. When you download the newer RUU make sure it is for your variant and the version number is higher than what you presently have.
majmoz said:
To remove the HTC drivers go into Control Panel >> Programs and Features >> find HTC Drivers and highlight then select uninstall. To remove the adb and fastboot just delete the folder but save your files that are to be flashed or pushed to another folder first. When you download the newer RUU make sure it is for your variant and the version number is higher than what you presently have.
Click to expand...
Click to collapse
did everything you suggested.. got further than before kinda. I feel asleep at like 2am with the RUU app still sending.. I woke up around 5 something and it was still sending so i just shut down my computer and went back to sleep... when i wake up again the phone says RUU failed or something.
I re-run the app thinking maybe it was because i didnt 'run as administrator' two hours later its still sending...........................
this is the ruu im using: RUU_M7_UL_JB43_SENSE50_MR_TMOUS_3.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2(2)
maybe that bracketed 2 is throwing something off, i dont know.
is there an alternative to RUUexe.... maybe adb push a zip?
majmoz said:
To remove the HTC drivers go into Control Panel >> Programs and Features >> find HTC Drivers and highlight then select uninstall. To remove the adb and fastboot just delete the folder but save your files that are to be flashed or pushed to another folder first. When you download the newer RUU make sure it is for your variant and the version number is higher than what you presently have.
Click to expand...
Click to collapse
Jxt. said:
Hey taco, so all you are trying to do is flash an RUU?
if so you might want to check that you have the proper model id and matching RUU file, afterwards type "fastboot oem rebootRUU" capital sensitive.
Then start the RUU, If that's not what your trying to get done then tell me what you are trying to do.
Click to expand...
Click to collapse
Yes im trying to RUU, i ran it and after forever it still said sending. I shut the computer down and the phone booted to bootloader with no options to chose from, all it said was "RUU, RUU zip transfer failed" or something like that.. i rebooted and am trying the ruu ran as administrator.
Jxt. said:
Okay so you are getting a flashing error.
Are you in RUU mode when flashing this? (black screen, silver logo of HTC).
You have the correct RUU? (Can you give me a link of where you got it?)
Can you take a screenshot of your pc when you get the error?
That should let me know whats going wrong.
Click to expand...
Click to collapse
my computer just restarted out of nowhere so i lost the cmd prompts from the last attempt but after like 3 hours of sending (ruu app says sending........ and the phone has silver htc w/ blk bkg) i entered fastboot rebbotRUU and the phone reboots to the stuck launch green htc logo screen.. on my computer the ruu app says successful transfer or something... im guessing it didnt work.
ruu:
http://forum.xda-developers.com/showthread.php?t=2496074
phone says: relocked ***security warning***, hboot 1.56
htcONE m7 tmobile....
tried RUU for the 5th time... force rebooted the HTC after 2 hours, got 'ruu 155 unknown error'
results of fastboot getvar all:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA425W909681
(bootloader) imei: ******1457712
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(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
all: Done!
finished. total time: 0.068s
tacoDawg said:
tried RUU for the 5th time... force rebooted the HTC after 2 hours, got 'ruu 155 unknown error'
results of fastboot getvar all:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: removed
(bootloader) imei: removed
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(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
all: Done!
finished. total time: 0.068s
Click to expand...
Click to collapse
You are trying to run a RUU that is a lower version than your phone. Give this one a try is should be the same version or higher.
Jxt. said:
You might want to edit your last post and delete your imei, you don't want to show that around !
---------- Post added at 10:53 PM ---------- Previous post was at 10:50 PM ----------
Another thing, you should be s-off or at least have a stock recovery. One of the two.
Click to expand...
Click to collapse
damn, how stupid of me...thanks. yea, i was trying to get s-off but they suggest ruu.
majmoz said:
You are trying to run a RUU that is a lower version than your phone. Give this one a try is should be the same version or higher.
Click to expand...
Click to collapse
MY GOD I COULD KISS YOU! I have been struggleing with this phone for liike 3 months now and you just broke the case like it was nothing. If you ever need to hide a body, consider me down, I owe you one.
tacoDawg said:
MY GOD I COULD KISS YOU! I have been struggleing with this phone for liike 3 months now and you just broke the case like it was nothing. If you ever need to hide a body, consider me down, I owe you one.
Click to expand...
Click to collapse
You are welcome glad I could help. If you could put [Solved] on the title of your first post that would be great. Happy flashing!!!
majmoz said:
You are trying to run a RUU that is a lower version than your phone. Give this one a try is should be the same version or higher.
Click to expand...
Click to collapse
Jxt. said:
Yeah, tell me how that works
Click to expand...
Click to collapse
s***s working now, thanks for looking out.
Related
Hi
Please help me or I will possibly be killed by my wife!
She has a HTC One which was bought 2nd hand months ago. This morning there was a alert popped up on screen saying there was a OTA update. I pressed it and it took me into a recovery system called "Team Win Recovery Project V2.6.3.0".
Ive gone into this and pressed the "wipe" button and "format data" thinking this would do a full factory reset for this update.....I was wrong!
I now have no OS on the phone and she is seriously P!ssed at me!
I have been on with this for the past 4 hours and still no further forward.
I have managed to download a RUU and side load it onto the phone but when it updates I get the following error
"set_metadata_recursive: some changes failed
E : Error executing updater binary in zip '/sdcar
Error flashing zip '/sdcard/sideload.zip'
Updateing partition details..."
Can any1 help? could it be the RRU I have downloaded is corrupt? or the wrong one?
When I go into the bootload the following info is there......
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.61.1
eMMC-boot 2048MB
Jun 21 2013, 23:33:16.0
I don't know if the phones jailbroke/rooted etc. She isn't wanting any of that, just to be able to get the updates and that's it.....once again,
PLEASE HELP! lol
Thankyou in advance!
Dave
Are you familiar with fastboot commands? While booted to the white Bootloader screen connect phone to pc, then open a command prompt in whichever folder you have fastboot.exe in by holding the shift key down and right click the mouse anywhere in the folder fastboot is in. Then choose "open command prompt here"
In the black command prompt window please type
fastboot getvar all
Then hit enter. Copy and paste the info it spits out here please. This will give us more info about your devices firmware. If you had s-off you could flash any ruu, but since you are s-on we can only flash an ruu that is the same as current firmware or upgrade to a higher version (then you have to hope there is an ruu available)
This will help put you back to complete stock. The issue before was that you had twrp recovery installed when you tried to ota update. You can only update via OTA if you have stock recovery. Then the real issue is when you formatted data and wiped your firmware off phone.
Since your bootloader is unlocked it is possible to just push a stock rom through sideboard and then flash in recovery but you still couldn't accept updates since you have twrp installed. This would be the quicker fix but if the wife wants complete stock we need to look for the correct RUU.
Hope this helps!
Sent from my SGH-I337 using xda app-developers app
ive done as you asked and it just says < waiting for device >
Ive read somewhere that fastboot doesn't work correct with windows 8.1
dave mckenzie said:
Hi
Please help me or I will possibly be killed by my wife!
She has a HTC One which was bought 2nd hand months ago. This morning there was a alert popped up on screen saying there was a OTA update. I pressed it and it took me into a recovery system called "Team Win Recovery Project V2.6.3.0".
Ive gone into this and pressed the "wipe" button and "format data" thinking this would do a full factory reset for this update.....I was wrong!
I now have no OS on the phone and she is seriously P!ssed at me!
I have been on with this for the past 4 hours and still no further forward.
I have managed to download a RUU and side load it onto the phone but when it updates I get the following error
"set_metadata_recursive: some changes failed
E : Error executing updater binary in zip '/sdcar
Error flashing zip '/sdcard/sideload.zip'
Updateing partition details..."
Can any1 help? could it be the RRU I have downloaded is corrupt? or the wrong one?
When I go into the bootload the following info is there......
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.61.1
eMMC-boot 2048MB
Jun 21 2013, 23:33:16.0
I don't know if the phones jailbroke/rooted etc. She isn't wanting any of that, just to be able to get the updates and that's it.....once again,
PLEASE HELP! lol
Thankyou in advance!
Dave
Click to expand...
Click to collapse
the RUU is run from the PC not the phone
here are some directions to flash "rom.zip":
Quote:
if youre working with a booted,operational phone,you can flsh the file in the following manner:
-open a cmd window
-change to adb/fastboot directory
cd c:\foldername
(cd c:\mini-adb if youve used any of my guides )
-place the zip file you want to flash into adb/fastboot directory
-enable usb debug,disable fastboot,plug in phone
-check for connectivity
adb devices (should return serial number)
-boot to fastboot
adb reboot bootloader
-check for connectivity again
fastboot devices
-flash the file
fastboot erase cache
fastboto oem rebootRUU (will put you in ruu mode,black screen silver htc letters)
fastboot flash zip zipfilename.zip (will send and flash the file. dont interupt it while the cmd window shows its writinging,and the green status bar is moving on the phone screen)
*sometimes a file will fail with a pre-update error. this is normal,just enter again:
fastboot flash zip zipfilename.zip
and this time it will finish
-when you get "finished" and "OK"
fastboot reboot-bootloader (takes you back to fastboot)
-reboot back to the OS
fastbooot reboot
you can use this if you dont have an operational phone as well. you just need to manually put the phone in fastboot(select from hboot menu) then skip the "adb" commands and start with fastboot devices
to answer your other question,yes,you will need to re-unlock and re-install recovery after running the RUU. an ruu is designed as an "unroot" solution, or emergency fix,if other attempts have not made the phone operational.
Click to expand...
Click to collapse
I am running windows 8.1 and it wont pick up the phone at all in fastboot mode.....
dave mckenzie said:
I am running windows 8.1 and it wont pick up the phone at all in fastboot mode.....
Click to expand...
Click to collapse
well theirs your problem, your going to need a windows 7 pc
try sideloading one of these
http://www.htc1guru.com/downloads/stock-rom-downloads/
dave mckenzie said:
ive done as you asked and it just says < waiting for device >
Ive read somewhere that fastboot doesn't work correct with windows 8.1
Click to expand...
Click to collapse
Yes sometimes fastboot does not play nice with win8.1 you need to get fastboot drivers working before you could fastboot oem rebootRUU anyways, plus you will need to make sure you have the correct RUU.
Do you have access to another pc that doesn't have win8.1? It would make this process much quicker. If not then let me fire up my pc to get you a few proper links to help you get fastboot working on current pc (on my phone right now).
Sent from my SGH-I337 using xda app-developers app
I have a MacBook but all pcs in this house has win8.1, I can only reply once every 5mins due to some restriction on my account on here so sorry for not replying straight away.
Last login: Sat Dec 28 16:00:02 on ttys000
Dave-McKenzies-MacBook-Pro-15:~ davemckenzie$
Dave-McKenzies-MacBook-Pro-15:~ davemckenzie$
Dave-McKenzies-MacBook-Pro-15:~ davemckenzie$
Dave-McKenzies-MacBook-Pro-15:~ davemckenzie$ cd
Dave-McKenzies-MacBook-Pro-15:~ davemckenzie$ cd /Users/davemckenzie/Desktop/andriod
Dave-McKenzies-MacBook-Pro-15:andriod davemckenzie$ ./fastboot getvar all
< waiting for device >
(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.61.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA33VW904059
(bootloader) imei: ************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3958mV
(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
all: Done!
finished. total time: 0.044s
Dave-McKenzies-MacBook-Pro-15:andriod davemckenzie$
(bootloader) version-main: 2.24.61.1
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
Click to expand...
Click to collapse
This is all I can find for you phone
http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-orang001-2-24-61-1-zip/
Extract this to the folder fastboot/adb is in, in a folder called backup
To use – download the latest version of the needed recovery and install it via fastboot:
fastboot flash recovery TWRP.img - you already have this
Then enter recovery either by holding power and vol down button until bootloader displays and then select recovery
Now perform a test backup and allow it to complete. Then make a note of the folder in which the backup was created. Now copy the downloaded stock Nandroid into that same folder so that recovery will see the backup and allow you to restore it.
Click to expand...
Click to collapse
to accomplish this you going to adb push the file to your phone
this is how it looks on my phone
C:\fastboot>adb devices
List of devices attached
HT********** recovery <-- You need this Number in the command below not the word recovery
C:\fastboot>adb push backup /data/media/0/TWRP/BACKUPS/Your number here HT**********/backup
1 file pushed. 0 files skipped.
3881 KB/s (28795564 bytes in 7.245s)
Click to expand...
Click to collapse
In the above example I named the folder the files are in backup
after it copy's you go back to the phone in recovery and choose restore
the folder backup should be their for you to choose
wil these be the same commands on mac?
thankyou for your help btw, every1 has been brilliant
Once this has got working, will I be able to update over wifi etc?
dave mckenzie said:
wil these be the same commands on mac?
thankyou for your help btw, every1 has been brilliant
Once this has got working, will I be able to update over wifi etc?
Click to expand...
Click to collapse
No most likely this is a Stock rooted backup
You phone will never get OTA updates while your on custom recovery. Until theirs a RUU for your device it will be tough getting full stock for OTA
Sent from my HTC One using Tapatalk
Hi all
I have a mates HTC One (M7) he had installed a custom rom and then i dont know how wiped the lot.
So at the moment I have a Unlocked but Tampered bootloader
HB 1.56.000
S-ON
No Root
and NO OS
I have managed to install TWRP and have ADB installed (windows 8.1 x64)
In fastboot i get fastboot usb although adb commands do not appear to work although fastboot commands do.
I have tried to sideload using TWRP but no luck.
I have tried to use Fastboot flash zip recovery.zip to flash the GURU Reset from HTCGuru but that doesn't work
Tried to get s-off but with the adb issues I am having no luck.
Any help would be great....i have spent nearly 20 hours straight on this and have now lost the will to live
fastboot getvar all
Windows 7
We need these
from HTC One
yatindroid said:
fastboot getvar all
Windows 7
We need these
from HTC One
Click to expand...
Click to collapse
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH36LW904423
(bootloader) imei: 357864056120981
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4327mV
(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
all: Done!
remove imei and serial from your output above, its dangerous to post them.
you need TWRP 2.6.3.3 on your phone.
enter recovery on your phone then place the guru reset file you downloaded in the same folder as adb and fastboot on your computer, (windows 8.1 is fine) and rename it to rom.zip for ease.
make sure your phone is plugged into your PC, open a command window in your adb/fastboot folder and type adb push rom.zip /sdcard/
takes a while so sit back and wait, it will tell you on the CMD window when its done.
make sure your battery is 50% or more, unplug your phone, and then flash it from within recovery, select install and find rom.zip in the list, swipe to confirm flash.
Cheers will try and report back
Sent from my LG-D802 using XDA Free mobile app
lspec230 said:
Cheers will try and report back
Sent from my LG-D802 using XDA Free mobile app
Click to expand...
Click to collapse
remove your serial number and IMEI number from you above post.
---------- Post added at 08:07 PM ---------- Previous post was at 08:05 PM ----------
during the installer, select wipe data, flash stock recovery but don't flash stock radio.
Ok got TWRP 2.6.3.3 on there
When I try the adb push command I get Error: Device not Connected
I wish I knew why he didn't S-Off in the first place.
I am guessing the only way to do this now is to get an OTG cable and try and move the .zip that way.
Is there a way to use a the fastboot commands to push the file across rather adb as i seem to be able to use fastboot ok
do you have the latest drivers installed ?
do you have the latest adb and fastboot ?
strange that fastboot works but adb doesn't, you are in recovery main screen when you issue the push command ?
Seanie280672 said:
do you have the latest drivers installed ?
do you have the latest adb and fastboot ?
strange that fastboot works but adb doesn't, you are in recovery main screen when you issue the push command ?
Click to expand...
Click to collapse
Yeah latest drivers reinstalled ADB/SDK tools yesterday adb version 1.0.31
Went through the windows 8.1 pain of ensuring my USB Drivers were intel rather than the default windows one as well.
I have tried the adb push in Recovery and Fastboot USB and also tried using adb sideload utility in TWRP
If I use fastboot to relock the bootloader and with s-on will I be able to use a stock RUU.exe??
yup you can do that, or if that fails then pull the rom.zip from the RUU and flash through fastboot rebootRUU mode.
Will try pulling the rom first will I have to look the bootloader first.?
Tried last night with the ruu.exe but kept getting 155 error
Sent from my LG-D802 using XDA Free mobile app
lspec230 said:
Will try pulling the rom first will I have to look the bootloader first.?
Tried last night with the ruu.exe but kept getting 155 error
Sent from my LG-D802 using XDA Free mobile app
Click to expand...
Click to collapse
155 error = relock your bootloader first, use the command fastboot oem lock
when you run the RUU it first unpacks itself, leave the installer open but don't do anything else with it.
you need to show hidden files and folders on your PC
then goto c:\users\username\AppData\Local\TEmp then one of those folders you see at the top of the list with lots of letters and numbers will have rom.zip in it, copy and paste it to your adb and fastboot folder, it should be pretty much the same file size as the whole RUU itself, once that's done you can close the RUU installer.
Thanks for all the help everyone... Relocked bootloader and used the 4.4 ruu.exe
Think someone owes me beer for soft bricking his phone then throwing at me to fix
Sent from my LG-D802 using XDA Free mobile app
Hello,
My phone is not rooted. It was still on factory setting, with no custom roms. I've been keeping up w/ the updates and i don't recall anything "special" happening before it was bricked yesterday night.
I tried accessing the fastboot screen (vol down + power button), and tried recovering, rebooting, and factory resetting, and they all sent it back to a freezing boot screen.
Using Hasoon2000's HTC One All-In-One Toolkit, I tried to boot it into bootloader, after a couple of hours, I saw a black screen w/ a red triangle in the middle, and after that, it just went back to being frozen at the Htc boot screen.
I have no idea what to do, any suggestions would help.
Thank You
-George Kayogre
Edit: Some specs in HBOOT:
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
George Kayogre said:
Hello,
My phone is not rooted. It was still on factory setting, with no custom roms. I've been keeping up w/ the updates and i don't recall anything "special" happening before it was bricked yesterday night.
I tried accessing the fastboot screen (vol down + power button), and tried recovering, rebooting, and factory resetting, and they all sent it back to a freezing boot screen.
Using Hasoon2000's HTC One All-In-One Toolkit, I tried to boot it into bootloader, after a couple of hours, I saw a black screen w/ a red triangle in the middle, and after that, it just went back to being frozen at the Htc boot screen.
I have no idea what to do, any suggestions would help.
Thank You
-George Kayogre
Edit: Some specs in HBOOT:
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
Click to expand...
Click to collapse
Since, it is completely stock and you didn't change anything, it might be a hardware issue. I would return it to HTC or your carrier for repair. The black screen with the red triangle is the stock recovery screen. The other thing you might try is run a RUU if available. Can you post a fastboot getvar all with the imei and serialno removed?
George Kayogre said:
Hello,
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
Click to expand...
Click to collapse
don't make duplicate posts
I answered you here >> http://forum.xda-developers.com/htc-one/help/htc-one-soft-bricked-idea-to-t2851592
clsA said:
don't make duplicate posts
I answered you here >> http://forum.xda-developers.com/htc-one/help/htc-one-soft-bricked-idea-to-t2851592
Click to expand...
Click to collapse
Sorry about the other thread, i was instructed to make another one in the correct section, but then a mod also moved my old post to this section...making it 2...
Anyway, I'm unable to get my device recognized, all it shows is "waiting for device" for ever.
majmoz said:
Since, it is completely stock and you didn't change anything, it might be a hardware issue. I would return it to HTC or your carrier for repair. The black screen with the red triangle is the stock recovery screen. The other thing you might try is run a RUU if available. Can you post a fastboot getvar all with the imei and serialno removed?
Click to expand...
Click to collapse
I'm trying to get the fastboot getvar from Hasoon's program, but it's returning an "error: device not found".
George Kayogre said:
Sorry about the other thread, i was instructed to make another one in the correct section, but then a mod also moved my old post to this section...making it 2...
Anyway, I'm unable to get my device recognized, all it shows is "waiting for device" for ever.
I'm trying to get the fastboot getvar from Hasoon's program, but it's returning an "error: device not found".
Click to expand...
Click to collapse
first of all, if you are not returning your device to your carrier or htc like majmoz suggested above and you want to troubleshoot it yourself, you will need to get rid of that toolkit and learn how to use ADB and FASTBOOT from a command window. Toolkits aren't the best thing when troubleshooting. They often comes with outdated stuff.
Install your HTC drivers correctly on your computer
download and install the Android SDK or Minimal ADB and FASTBOOT
do the commands cIsA told you on your other thread and post the results. The output of "fastboot getval all" could also be useful
alray said:
first of all, if you are not returning your device to your carrier or htc like majmoz suggested above and you want to troubleshoot it yourself, you will need to get rid of that toolkit and learn how to use ADB and FASTBOOT from a command window. Toolkits aren't the best thing when troubleshooting. They often comes with outdated stuff.
Install your HTC drivers correctly on your computer
download and install the Android SDK or Minimal ADB and FASTBOOT
do the commands cIsA told you on your other thread and post the results. The output of "fastboot getval all" could also be useful
Click to expand...
Click to collapse
Tried that, but still can't get my pc to recognize the device in bootloader, althought HTC sync does pop up every time i connect it.
When i type "fastboot devices" in the command prompt, nothing happens, then "fastboot clear cache" just shows "waiting for device".
I have downloaded the latest drivers, currently updating HTC Sync, hoping it'd affect something
George Kayogre said:
Tried that, but still can't get my pc to recognize the device in bootloader, althought HTC sync does pop up every time i connect it.
When i type "fastboot devices" in the command prompt, nothing happens, then "fastboot clear cache" just shows "waiting for device".
I have downloaded the latest drivers, currently updating HTC Sync, hoping it'd affect something
Click to expand...
Click to collapse
uninstall htc sync and try again
alray said:
uninstall htc sync and try again
Click to expand...
Click to collapse
Tried w/ and w/o HTC sync, ensured drivers were installed...and "fastboot devices" still has no effect.
George Kayogre said:
Tried w/ and w/o HTC sync, ensured drivers were installed...and "fastboot devices" still has no effect.
Click to expand...
Click to collapse
try another usb cable, another usb port. If the drivers are correctly installed, and the usb port/cable are ok and you still can't use fastboot commands from bootloader, it might be an hardware issue.
alray said:
try another usb cable, another usb port. If the drivers are correctly installed, and the usb port/cable are ok and you still can't use fastboot commands from bootloader, it might be an hardware issue.
Click to expand...
Click to collapse
Finally got my device to be recognized, all I did was plug in my phone, boot in into bootloader...again and again...till it was recognized
majmoz said:
Since, it is completely stock and you didn't change anything, it might be a hardware issue. I would return it to HTC or your carrier for repair. The black screen with the red triangle is the stock recovery screen. The other thing you might try is run a RUU if available. Can you post a fastboot getvar all with the imei and serialno removed?
Click to expand...
Click to collapse
This is what "fastboot getvar all" returned:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.110
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *erased*
(bootloader) imei: *erased*
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4078mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
clsA said:
Unzip this to your desktop and open a command window from it's folder (right click - command prompt here)
plug in your phone to the pc boot to the bootloader with power + volume down
type fastboot devices
your phone serial number should be listed
now type fastboot erase cache
it should say something about formatting cache
now fastboot reboot
hopefully your phone will boot back up
Click to expand...
Click to collapse
I did run these commands, they were performed successfully, but my phone is still getting frozen on the boot screen
George Kayogre said:
Finally got my device to be recognized, all I did was plug in my phone, boot in into bootloader...again and again...till it was recognized
This is what "fastboot getvar all" returned:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.110
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *erased*
(bootloader) imei: *erased*
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4078mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I did run these commands, they were performed successfully, but my phone is still getting frozen on the boot screen
Click to expand...
Click to collapse
have you tried to perform a factory reset from the bootloader?
alray said:
have you tried to perform a factory reset from the bootloader?
Click to expand...
Click to collapse
Yep, that was the first thing i tried to do, but i was still stuck w/ the same problem.
George Kayogre said:
Yep, that was the first thing i tried to do, but i was still stuck w/ the same problem.
Click to expand...
Click to collapse
if your phone is still under warranty, send it for repair because the next actions will void the warranty:
You'll probably have to unlock the bootloader, flash a custom recovery and flash a rom.
Not sure why this happened on a 100% stock phone. Normally, users get in this situation when flashing custom roms
alray said:
if your phone is still under warranty, send it for repair because the next actions will void the warranty:
You'll probably have to unlock the bootloader, flash a custom recovery and flash a rom.
Not sure why this happened on a 100% stock phone. Normally, users get in this situation when flashing custom roms
Click to expand...
Click to collapse
Here's something new: after unlocking my phone, and having confirmed that i wanted all my "personal data erased", it just booted up normally and it worked, but then, while using it, t=it simply crashed...and got stuck in the bootloop again, which kinda points in the arrow of hardware issue again. I'm gonna try installing a rom (after i figure out how) and see where that leads me.
Update: Flashed CM11, phone still on boot loop, sending to repair soon.
Everyone, thanks for the help anyway, I really appreciate it.
Hello
I'm struggling since some days with my One M7 and since I'm not an expert I'm asking for some help..
I have unlocked the phone, installed twrp and by mistake wiped the os, so the phone doesn^t boot anymore. I would like to restore the original settings before trying again to root and install a custom rom.
The problem is that my phone is currently recognized only by fastboot and not by adb, tried several times with different usb cables and os (Win and mac) without success.
my understanding is that the only way to restore the os is via an official RRU.exe (as the device is s-on),am i correct?
Here the details
hboot 1.57.0000
radio 4t.28.3218.04
Opendsp v32.120.274.0909
I downloaded a RUU.exe but getting a security fail message in bootloader, again my understanding is that the image signature is wrong ? which ruu.exe can I use to successfully restore my device ?
many thanks in advance and best regards
Michele
zzmike76 said:
Hello
I'm struggling since some days with my One M7 and since I'm not an expert I'm asking for some help..
I have unlocked the phone, installed twrp and by mistake wiped the os, so the phone doesn^t boot anymore. I would like to restore the original settings before trying again to root and install a custom rom.
The problem is that my phone is currently recognized only by fastboot and not by adb, tried several times with different usb cables and os (Win and mac) without success.
my understanding is that the only way to restore the os is via an official RRU.exe (as the device is s-on),am i correct?
Here the details
hboot 1.57.0000
radio 4t.28.3218.04
Opendsp v32.120.274.0909
I downloaded a RUU.exe but getting a security fail message in bootloader, again my understanding is that the image signature is wrong ? which ruu.exe can I use to successfully restore my device ?
many thanks in advance and best regards
Michele
Click to expand...
Click to collapse
Right first of all adb commands wont work in the bootloader so stop trying different cables etc as your wasting your time, adb is only for when your in a booted rom or in recovery, fastboot commands are for the bootloader.
Next please post your fastboot getvar all without imei and serial number.
also, if you intend on going to a custom rom, there is no point flashing an RUU, you are already halfway there to flashing a custom rom, so which rom do you want to flash ?
hello
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP110
(bootloader) battery-status: good
(bootloader) battery-voltage: 4310mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
thanks and regards
michele
zzmike76 said:
hello
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP110
(bootloader) battery-status: good
(bootloader) battery-voltage: 4310mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
thanks and regards
michele
Click to expand...
Click to collapse
I can tell you now with a CID of VODAP110 there is no RUU for your phone, I used to have a TWRP backup for vodaphone, that was a long time ago before I got s-off, i'll have a look through and see if I can find it, which custom rom do you want to flash ?
Seanie280672 said:
I can tell you now with a CID of VODAP110 there is no RUU for your phone, I used to have a TWRP backup for vodaphone, that was a long time ago before I got s-off, i'll have a look through and see if I can find it, which custom rom do you want to flash ?
Click to expand...
Click to collapse
well, actually I would be happy to have my mobile booting again
as I'm not an expert I would kindly ask you for any suggestion for custom roms
thanks a lot!
Michele
zzmike76 said:
well, actually I would be happy to have my mobile booting again
as I'm not an expert I would kindly ask you for any suggestion for custom roms
thanks a lot!
Michele
Click to expand...
Click to collapse
Rom suggestions are not allowed.
Put TWRP 2.6.3.3 on your phone if you don't already have that version, it must be that version, I know its a bit old but its still the best for sense based rom's, you can get it from here: http://techerrata.com/browse/twrp2/m7
place the img file in the same folder as your adb and fastboot files on your computer then open a command windows from there and with your phone plugged in and fastbootUSB showing on your phone, issue the following commands
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
then download this file, this is stock unbranded rom: http://www.androidrevolution.org/downloader/download.php?file=One_6.09.401.12_odexed.zip re-name it to rom.zip and place it in the same folder as adb and fastboot on your computer, then enter recovery on your phone, just the main screen no sub menu's, and then open a cmd window on your computer from the adb/fastboot folder and with your phone plugged into the computer type this command:
Code:
adb push rom.zip /sdcard/
it will appear unresponsive for quite a while, just leave it alone, takes about 5 mins to push the file but it will let you know when its done.
unplug your phone and flash the rom, when its finished reboot your phone and set it all up.
when everything is done that you want done to it, boot back into recovery and select reboot - system, it will say your rom is not currently rooted, do you want to install SuperSU now, select yes if you want root, your phone will then boot back up, follow the instructions on your phone screen when it boots back up, simple as that to root.
thanks for the information, i downgraded twrp to the suggested version but when entering recovery mode i cannot see the phone with the command adb devices...i noticed that when i plug the phone in windows for few seconds show the phone in device manager with name My HTC under android usb devices but then it disappears
i installed the latest htc drivers but still no phone detection
zzmike76 said:
thanks for the information, i downgraded twrp to the suggested version but when entering recovery mode i cannot see the phone with the command adb devices...i noticed that when i plug the phone in windows for few seconds show the phone in device manager with name My HTC under android usb devices but then it disappears
i installed the latest htc drivers but still no phone detection
Click to expand...
Click to collapse
that's strange that it pops up and then disappears, are you using the original HTC cable, or try a different one, also make sure HTC Sync is uninstalled, just leave the drivers on your computer, you will need to restart after uninstalling HTC Sync.
Sounds more like a computer issue to me than the phone.
Do you have a USB OTG cable you can use ?
original cable (tried also with another one), htc synch uninstalled 8and rebooted), driver version is 2.0.7.23
strang ething it appens on mac as well
i have no otg cable, if i buy one could it solve the issue ?
zzmike76 said:
original cable (tried also with another one), htc synch uninstalled 8and rebooted), driver version is 2.0.7.23
strang ething it appens on mac as well
i have no otg cable, if i buy one could it solve the issue ?
Click to expand...
Click to collapse
yes, you just copy the rom.zip to a memory stick, plug it into one end of the otg cable and the other end into your phone, does away with the use for a computer.
my driver is 2.0.7.28
could be your adb and fastboot, you could always try mine, link below
just find it very strange that it see's it, and then it disappears, ive never experienced anything like this happening to me, yet fastboot works fine, its got to be your drivers, you may have to force your driver in device manager whilst in recovery on your phone, are you using windows 8 ?
Seanie280672 said:
yes, you just copy the rom.zip to a memory stick, plug it into one end of the otg cable and the other end into your phone, does away with the use for a computer.
my driver is 2.0.7.28
could be your adb and fastboot, you could always try mine, link below
just find it very strange that it see's it, and then it disappears, ive never experienced anything like this happening to me, yet fastboot works fine, its got to be your drivers, you may have to force your driver in device manager whilst in recovery on your phone, are you using windows 8 ?
Click to expand...
Click to collapse
no windows 7 , this evening will try with an old xp laptop..but on the mac as well i can only see the device in fastboot
is there away to reformat the sdcard from twrp ? maybe it is damaged
zzmike76 said:
no windows 7 , this evening will try with an old xp laptop..but on the mac as well i can only see the device in fastboot
is there away to reformat the sdcard from twrp ? maybe it is damaged
Click to expand...
Click to collapse
inside twrp you can select wipe and then format data, that will wipe everything all partitions etc, you shouldn't be having any problems with windows 7 though.
update..bought an otg cable and was able to restore the image you sent me...MANY THANKS !!
still the device does not show on windows (there must be some driver issue), but now adb commands work on my mac (yesterday they didn't) so i have a working environment
need to understand how to s-off on mac , is it possible or windows is required ?
thanks again for your support!
zzmike76 said:
update..bought an otg cable and was able to restore the image you sent me...MANY THANKS !!
still the device does not show on windows (there must be some driver issue), but now adb commands work on my mac (yesterday they didn't) so i have a working environment
need to understand how to s-off on mac , is it possible or windows is required ?
thanks again for your support!
Click to expand...
Click to collapse
the only way to s-off on your current HBOOT is to use sunshine, your best off connecting your phone to wifi and download it straight to your phone as its an apk file actually for your phone, not to be run from the computer, it will check your phone first to see if it can be s-off'd and if it can then you'll have to pay $25 though paypal etc, it will then proceed, its well worth it, you can get rid of that vodaphone branded rubbish straight away and flash any RUU should you come stuck again, I paid to have mine done in a shop in Sheffield before sunshine came about and firewater didn't work.
http://theroot.ninja/
Seanie280672 said:
the only way to s-off on your current HBOOT is to use sunshine, your best off connecting your phone to wifi and download it straight to your phone as its an apk file actually for your phone, not to be run from the computer, it will check your phone first to see if it can be s-off'd and if it can then you'll have to pay $25 though paypal etc, it will then proceed, its well worth it, you can get rid of that vodaphone branded rubbish straight away and flash any RUU should you come stuck again, I paid to have mine done in a shop in Sheffield before sunshine came about and firewater didn't work.
http://theroot.ninja/
Click to expand...
Click to collapse
another update....it seems that after a while the phone is entering the usb host adapter mode and refuses to charge/being detected by mac/pc..at least i now can see the warning within the phone..now reading this thread http://forum.xda-developers.com/showthread.php?t=2481211
will try again to wipe everything and reinstall to see whether windows can detect it just for s-offing the phone
Hi there, I must have flashed the wrong sense ROM. I am extremely noobish, so bare with me.
I tried following this amazing guide: http://forum.xda-developers.com/showthread.php?t=2739126 but have had no luck when it comes to flashing the recovery indicated.
"C:\adb>fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img
error: cannot load 'twrp-recovery-2.7-m7-nobcb.img'"
It looks like I entered it right...
My phone will power on and function OK with data and text, but cannot make calls. Sometimes it'll reboot into hboot when I plug it into USB/AC. I have access to fastboot, but not adb, nor recovery.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: `
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35...
(bootloader) imei: 3559...
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4118mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-331585dd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thank you for your time, XDA!
Have you selected the Fastboot option in bootloader before you flash that?
Sent from my HTC One using Tapatalk
cyrusct82 said:
Have you selected the Fastboot option in bootloader before you flash that?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Yes and it shows under "fastboot devices"
It's now managed to have gotten worse and will only boot into the spash screen, then Fastboot (not Hboot).
If I remove the sim card, it will boot up normally (unless it's plugged into USB/AC). If I insert the sim, or plug in the microUSB, it will shortly thereafter crash into fastboot.
1- error: cannot load -> means the filename is wrong
2- Are you able to get to any kind of stable (or at least semi-stable) part; ROM or TWRP?
3- can you please provide the link (thread and file please) of what you flashed; so that we can look what was corrupted
nkk71 said:
1- error: cannot load -> means the filename is wrong
2- Are you able to get to any kind of stable (or at least semi-stable) part; ROM or TWRP?
3- can you please provide the link (thread and file please) of what you flashed; so that we can look what was corrupted
Click to expand...
Click to collapse
1) I tried simplifying the name to TWRPnbc.img and it's still says failed
2) I was able to boot into the ROM, make texts and use data reliably for a bit, once this issue started, but now it is so bad I can only access fastboot (including presence in "fastboot devices" of fastboot commands). Hboot does not acknowledge USB, adb devices shows nothing (device manager shows nothing in Hboot mode) and attempting to load the ROM kicks me back to Fastboot (not Hboot). Recovery kicks me back to Fastboot as well :crying:
3)It was a while ago that I flashed this ROM and it WAS stable for nearly 6 months, but I think it was just the first ROM of the list for the GURU resets, here:
http://www.htc1guru.com/downloads/stock-rom-downloads/
The version of TWRP I was trying to flash, if you are interested, is in the guide/link in the OP.
Thank you for your time and attention, nkk71!
Enigmatic Fart said:
1) I tried simplifying the name to TWRPnbc.img and it's still says failed
2) I was able to boot into the ROM, make texts and use data reliably for a bit, once this issue started, but now it is so bad I can only access fastboot (including presence in "fastboot devices" of fastboot commands). Hboot does not acknowledge USB, adb devices shows nothing (device manager shows nothing in Hboot mode) and attempting to load the ROM kicks me back to Fastboot (not Hboot). Recovery kicks me back to Fastboot as well :crying:
3)It was a while ago that I flashed this ROM and it WAS stable for nearly 6 months, but I think it was just the first ROM of the list for the GURU resets, here:
http://www.htc1guru.com/downloads/stock-rom-downloads/
The version of TWRP I was trying to flash, if you are interested, is in the guide/link in the OP.
Thank you for your time and attention, nkk71!
Click to expand...
Click to collapse
1- renaming the file is no problem, but you probably ended up with <NAME>.img.img (double extension due to Windows hiding known extensions), hence the use for Windows Command Prompt - DIR command and TAB-completion
2- you being able to boot (to some extent is good-ish)
3- the htc1guru files are meant for the HTC One M7, so nothing wrong there
i'll need to catch up with you tomorrow, as i'm off for tonight, take it easy
nkk71 said:
1- renaming the file is no problem, but you probably ended up with <NAME>.img.img (double extension due to Windows hiding known extensions), hence the use for Windows Command Prompt - DIR command and TAB-completion
2- you being able to boot (to some extent is good-ish)
3- the htc1guru files are meant for the HTC One M7, so nothing wrong there
i'll need to catch up with you tomorrow, as i'm off for tonight, take it easy
Click to expand...
Click to collapse
Cool man, I'll run through and try to flash it again in the meantime and edit this post with results.
Thanks again for your help! Peace!
EDIT: OK, I see what the issue was, but a new one popped up. So I was attempting to flash the recovery I placed in my phone's storage. I now have "TWRP.img" (latest TWRP) and "TWRPnbcb.img" (the no bcb one from that guide) in my adb folder (where fastboot is) on my PC and have attempted to flash both recoveries for S&Gs.
Here are the results:
"C:\Windows\system32>cd C:\adb
C:\adb>fastboot devices
HT35xxxxxx... fastboot
C:\adb>fastboot flash recovery TWRPnbcb.img
sending 'recovery' (11278 KB)...
FAILED (command write failed (No such device or address))
finished. total time: -0.000s
C:\adb>fastboot flash recovery TWRP.img
sending 'recovery' (12534 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.016s"
Last ditch bump! I don't want my phone retire in a junk drawer!
Enigmatic Fart said:
Last ditch bump! I don't want my phone retire in a junk drawer!
Click to expand...
Click to collapse
please post a "fastboot oem last_dmesg", after trying to flash something
@alray, might be able to decipher that
(sorry for the ping)