So i had custom rom installed by previous owner, but which i did not like, so i wanted to go stock.
After following some guide i managed to flash new rom into my DZ using CWM and all hell broke loose.
My DZ refused to boot, only gives me the white htc screen and vibrates once.
From hboot i tried go back into recovery, which gives me same white screen with htc logo and vibrates once. Same goes for Factory reset option.
After week of browsing xda forums and google, i finally gave up. Thou i managed once to reboot into G2 os after attempted flash trhu PC10IMG method or from recovery as first attempt, not sure. Which i thougt was supposed to be DZ rom, but was not. This rom might have reduced my system partition, i dont know how to confirm this.
Fastboot works, but no adb since i have no OS running atm.
Fastboot getvar all gives me this:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\User>fastboot devices
SH0B5RT09144 fastboot
C:\Documents and Settings\User>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.84.2000
(bootloader) version-baseband: 26.02.01.15_M2
(bootloader) version-cpld: None
(bootloader) version-microp: 0425
(bootloader) version-main: 1.22.531.8
(bootloader) serialno: SH0B5RT09144
(bootloader) imei: 352212045345548
(bootloader) product: vision
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PC1011000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3781mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: adbd7a75
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
C:\Documents and Settings\User>
At this point i dont want to go solo anymore, so im crying out for help on this one... I want to save this awesome Desire Z
Edit: I am able to flash recovery using fastboot flash recovery recovery.img but recovery option is still useless (does the white screen htc logo vibrating once thingy)
Boot to bootloader and write down all on that screen here
Then in bootloader choose image CRC and write down all that (may take 5min to run)
Then we will go from there
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Boot to bootloader and write down all on that screen here
Then in bootloader choose image CRC and write down all that (may take 5min to run)
Then we will go from there
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
RADIO-26.02.01.15_M2
eMMC-boot
Sep 8 2010 , 15:56:38
Then i have Fastboot, recovery,factory reset, simlock, system info and image crc in this order.
In image CRC i have:
hboot : 0x2A125CF4
boot : 0xD28A4324
recovery : 0x26A3CD9C
system : 0x0
Then it promts me to press power key to go back
Alright, you are looking good and most likely this isn't a brick, should be easy to recover
Do these steps
Go to fastboot mode and run
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now you want the most recent recovery, probably latest 4ext (see this thread for recovery links - http://forum.xda-developers.com/showthread.php?t=2348266
In second post along with lots of other good links
Now take this image and
fastboot flash recovery nameofrecovery.img
fastboot reboot-bootloader
Now choose recovery
If this gets you there flash ROM of choice (and gapps if needed) in this new recovery
Reboot
If anything fails or you can't find links let me know
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
C:\Documents and Settings\User>fastboot erase system -w
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
erasing 'system'...
OKAY [ 0.344s]
erasing 'userdata'...
OKAY [ 0.266s]
erasing 'cache'...
OKAY [ 0.109s]
finished. total time: 0.719s
C:\Documents and Settings\User>fastboot erase boot
erasing 'boot'...
OKAY [ 0.125s]
finished. total time: 0.125s
C:\Documents and Settings\User>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.156s]
finished. total time: 0.156s
C:\Documents and Settings\User>fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
C:\Documents and Settings\User>cd C:\android-sdk_r11-windows\platform-tools
C:\android-sdk_r11-windows\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (5342 KB)...
OKAY [ 0.891s]
writing 'recovery'...
OKAY [ 0.594s]
finished. total time: 1.484s
C:\android-sdk_r11-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.156s]
finished. total time: 0.156s
C:\android-sdk_r11-windows\platform-tools>
Did all that but still cannot access recovery :/ does the white screen thing.
Now im having hard time booting into hboot / fastboot
Edit: Okay, got in after a while Image crc as follows:
hboot 0x2A125CF4
boot 0x0
recovery 0x4C2506F5
system 0x0
http://forum.xda-developers.com/showthread.php?t=2348266
The second post in this thread you will find a section on adb and fastboot, the how to why to link brings you to a guide on fastboot
Flash the dz hboot from there (be sure to check md5sum)
I'm under the impression you have a corrupt partition right now so
fastboot flash hboot hboot.img
fastboot reboot-bootloader
Now start over with the same fast boot erase and flash commands from prior
Sent from my Nexus 7 using XDA Premium 4 mobile app
Still no luck.
I flashed hboot_7230_0.82.0000_100902.nb0, which i got from the PC10IMG.zip mentioned in thread.
Image CRC from hboot did not change after flash, so i guess i had the exact same hboot.
I repeated all the steps you mentioned and it gave me same error messages.
Still willing to help me?
You should have the .84.2000 according to your bootloader
Maybe try flashing the dz pc10img.zip in post 30 of that thread, many have said it fixed similar problems for them
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
You should have the .84.2000 according to your bootloader
Maybe try flashing the dz pc10img.zip in post 30 of that thread, many have said it fixed similar problems for them
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did that and repeated all again. Did not do anything :/ only recovery crc changed, but flashed recovery did not work so i flashed the 4ext again, still no access to recovery
Any ideas? Maybe im stuck with G2 system size since i flashed G2 rom back then, which i got to boot. Should i try that again? If so, any hints to do it properly?
Unzip that pc10img.zip that was linked in post 30 from the fastboot thread, use the dz one and flash just the bootloader with fastboot
There is an issue somewhere and I'm under the impression that if we can successfully flash this bootloader all will be good
Otherwise try this
Boot to bootloader
fastboot rebootRUU
fastboot flash update dzpc10img.zip
Of course replace with whatever the proper name is (forget off hand)
And then note all input/output from cmd here
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Unzip that pc10img.zip that was linked in post 30 from the fastboot thread, use the dz one and flash just the bootloader with fastboot
There is an issue somewhere and I'm under the impression that if we can successfully flash this bootloader all will be good
Otherwise try this
Boot to bootloader
fastboot rebootRUU
fastboot flash update dzpc10img.zip
Of course replace with whatever the proper name is (forget off hand)
And then note all input/output from cmd here
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Flashing the hboot from zip changes nothing and for some reason fastboot rebootRUU gives me list of commands
C:\android-sdk_r11-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.156s]
finished. total time: 0.156s
C:\android-sdk_r11-windows\platform-tools>fastboot rebootRUU
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, and if found,
recovery, tos
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\android-sdk_r11-windows\platform-tools>
Should i try to manually format system partition? If so, how and how large?
Sorry, the command is
fastboot oem rebootRUU
Sent from my Nexus 4 using XDA Premium 4 mobile app
Do you mean fastboot update DZPC10IMG.zip since fastboot flash update DZPC10IMG.zip gives unknown partition error.
Sounds right, its been probably at least a year or two since I've worked on this, take a look at my threads and you'll see two comprehensive guides on fastboot which will have all the proper steps
Sent from my Nexus 4 using XDA Premium 4 mobile app
I was able to flash stock rom extracted from RUU.
I used fastboot oem rebootRUU and then fastboot flash zip rom.zip and everything went OK.
However, i still cannot access recovery nor boot my phone.
Atm my hboot is 0.85.0013 SHIP S-OFF
Radio 26.10.04.03_M
Image CRC :
osb1: 0x7EE4ED8C
amss: 0xB7A63815
hboot: 0x887F7ABB
boot : 0x4CB9BC27
recovery 0xCFD60F9D
system 0xC46F8680
Any leads where to go from here?
Um, what RUU did you use? Did you use the one I made from my post? You should have a different bootloader if so
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Um, what RUU did you use? Did you use the one I made from my post? You should have a different bootloader if so
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was able to flash DZPC10IMG.zip from rebootRUU but that did no good either so i tried to flash this rom from this RUU RUU_Vision_Gingerbread_S_HTC_WWE_2.42.405.2_Radio_12.56.60.25_26.10.04.03_M_release_199043_signed.exe
Which i believe is supposed to be latest stock rom from DZ... correct me if im wrong
The problem with flashing a random PC10IMG.zip is that it will change your hboot, recovery, radio, etc
Not all this firmware is 100% compatible and can cause issues depending on your phones current state
Can you link the guide you followed originally by the way? Want to see if I can figure out what happened to your phone
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
The problem with flashing a random PC10IMG.zip is that it will change your hboot, recovery, radio, etc
Not all this firmware is 100% compatible and can cause issues depending on your phones current state
Can you link the guide you followed originally by the way? Want to see if I can figure out what happened to your phone
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have no idea where that guide is now, but if my memory serves me well, i flashed PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip from cwm recovery. After that i was able to boot into G2 rom for a while, thou my onscreen buttons didnt work (back and home etc) after that, no idea.
Edit: I do have my old DZ with working CWM v3.0.2.4 recovery. Can i use that in my advantage somehow?
Here is some data if its helpfull. My backup cid seems to be blank. Im under impression it should be like y_13 or so.
C:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D087B50
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x25209
(bootloader) TAG:hero panel = 0xF
(bootloader) TAG:engineerid = 0x4
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is
(bootloader) setting->cid::
(bootloader) serial number: SH0B5RT09144
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =456
(bootloader) active commandline: board_vision.disable_uart2=0 board_visio
(bootloader) n.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0
(bootloader) board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidbo
(bootloader) ot.emmc=true androidboot.baseband=26.13.04.19_M androidboot
(bootloader) .cid= androidboot.batt_poweron=good_battery androidboot.carr
(bootloader) ier=COMMON androidboot.mid=PC1011000 androidboot.keycaps=qwe
(bootloader) rty androidboot.mode=normal androidboot.serialno=SH0B5RT0914
(bootloader) 4 androidboot.bootloader=0.84.2000 no_console_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) aARM_Partion[6].name=devlog
(bootloader) aARM_Partion[7].name=pdata
(bootloader) partition number=8
(bootloader) Valid partition num=8
(bootloader) jump_to_kernel: machine_id(2245), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:657379 msec
FAILED (status read failed (Unknown error))
finished. total time: 222.922s
Related
Ok so, I decided the custom rom thing I was doing was getting boring so I wanted to get back to my stock rom. Y'know, htc one x, 4.2.2 Sense 5 that all cool stuff.
I got instructions and I tried my best in the following order.
Getting fastboot
putting boot and recovery in fastboot
flashing them and erasing cashe
relocking bootloader and erasing cashe
booting to fastboot mode again
starting RUU exe
now the RUU exe had a problem. I did a fastboot getvar cid to find i needed the following: CID HTC__J15
from here: http://forum.xda-developers.com/showthread.php?t=1975140
now that thread linked me to a .rar file that didn't have an exe file in it so i was super confused.
So i googled and i found this file:
RUU_ENDEAVOR_U_ICS_40_HTC_ARA_1.29.415.11_Radio_1.1204.105.14_release_260742_signed.exe
(^I lost the link lol, but thats the file name)
which matched what i needed. I think.
When i ran that, it said I had the wrong RUU for that device. Do i? I'm not really sure. Can someone link me to the right one?
Problem is also that I can't get past the bootloader screen now. Turning it off and on just brings me back to the bootloader.
Shiverfire said:
Ok so, I decided the custom rom thing I was doing was getting boring so I wanted to get back to my stock rom. Y'know, htc one x, 4.2.2 Sense 5 that all cool stuff.
I got instructions and I tried my best in the following order.
Getting fastboot
putting boot and recovery in fastboot
flashing them and erasing cashe
relocking bootloader and erasing cashe
booting to fastboot mode again
starting RUU exe
now the RUU exe had a problem. I did a fastboot getvar cid to find i needed the following: CID HTC__J15
from here: http://forum.xda-developers.com/showthread.php?t=1975140
now that thread linked me to a .rar file that didn't have an exe file in it so i was super confused.
So i googled and i found this file:
RUU_ENDEAVOR_U_ICS_40_HTC_ARA_1.29.415.11_Radio_1.1204.105.14_release_260742_signed.exe
(^I lost the link lol, but thats the file name)
which matched what i needed. I think.
When i ran that, it said I had the wrong RUU for that device. Do i? I'm not really sure. Can someone link me to the right one?
Problem is also that I can't get past the bootloader screen now. Turning it off and on just brings me back to the bootloader.
Click to expand...
Click to collapse
post the result from command fastboot getvar all and delete your S/N and IMEI from the info
plzzzzz help i have same problem
plzzzzz help i have same problem
nima619 said:
plzzzzz help i have same problem
Click to expand...
Click to collapse
Read along and do the same
Sent from my HTC One X using XDA Premium 4 mobile app
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.73.0000
(bootloader) version-baseband: 5.1204.167.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.415.3
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 3730mV
(bootloader) devpower: 56
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.954s
Only way to go back to stock rom is a nandroid backup. Ruu does not exist with that number.
I am hosting one here
Nandroid backup HTC__J15 - 4.20.415.rar - 614.05 MB
Flash the recovery.img AND the boot.img from the nandroid backup. Then mount the sdcard in the recovery and unpack the .rar file to the designated path.
Probably clockworkmod\backup\time and date folder\nand backup files in img and tar files etc etc
Then make a full wipe in the recovery (wipe ALL you can EXCEPT the sdcard)
Then restore the nand.
Sent from my HTC One X using XDA Premium 4 mobile app
ok i did that and:
\Fastboot>fastboot flash boot boot.img
sending 'boot' (8192 KB)...
OKAY [ 1.030s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 1.240s
\Fastboot>fastboot flash recovery recovery.img
sending 'recovery' (8192 KB)...
OKAY [ 1.118s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.325s
It won't let me go into recovery. Just comes back to bootloader. I can't mount the nandroid backup into the device
Shiverfire said:
ok i did that and:
\Fastboot>fastboot flash boot boot.img
sending 'boot' (8192 KB)...
OKAY [ 1.030s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 1.240s
\Fastboot>fastboot flash recovery recovery.img
sending 'recovery' (8192 KB)...
OKAY [ 1.118s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.325s
It won't let me go into recovery. Just comes back to bootloader. I can't mount the nandroid backup into the device
Click to expand...
Click to collapse
Are you UNLOCK your bootloader via htcdev.com?
Yeah it's locked or relocked
Sent from my HTC One X using XDA Premium 4 mobile app
In the first step I said I relocked my bootloader cause it was a step I read in a tutorial to go back to stock. It says ***RELOCKED*** on top.
Unlock it.......
Sent from my HTC One X using XDA Premium 4 mobile app
ok this is really annoying. my phone cant complete unlocking the bootloader cause its battery is too low. i put it on charge for 2 hours and its still low cause i cant turn the screen off or turn the phone off. When i turn the phone off without the charger, it stays off, but as soon as i put it in, it turns on. Ughhh
Use the batt script in fastboot mode to charge the battery
https://www.dropbox.com/s/aaah8gqz8j024xz/Batt script.bat
Phone in fastboot mode, script in fastboot folder and execute it with admin rights !
Sent from my HTC One X using XDA Premium 4 mobile app
Got it charged and fixed! Restoring now!
.-. nvm it got stuck when when i chose recovery in bootloader
Got stuck how ?
Sent from my HTC One X using XDA Premium 4 mobile app
when i go into recovery (i tried with rom manager too) it stops at the HTC screen
Fastboot flash the recovery.img from the nand backup. Also do :
Fastboot erase cache
After the recovery.img flash !
P.s. ditch rommanager ....it's useless on the hox !
Sent from my HTC One X using XDA Premium 4 mobile app
Ok tried restoring and it said MD5 was a mismatch.
Go here for that
http://forum.xda-developers.com/showthread.php?t=2579568
Sent from my HTC One X using XDA Premium 4 mobile app
So I am new to the posting aspect of xda but have been around checking out other peeps info for a while. Basically I've gotten into a weird situation, and have no idea now how to fix it. Sorry if there is already a thread for this issue, but I have been looking for 2 days, and decided I was in over my head.
I have a HTC One M7 Verizon (blue Best Buy model) which I got AFTER HTCDev had locked Verizon from unlocking bootloader via their website.
One a exploit was found to unlock the bootloader and gain root, I jumped and ran through the process using a CWM recovery and a Cyanogenmod as my ROM. Everything was peachy until a few days ago when an update, auto updated over night, and created a problem where my phone would reboot show the lock screen, but when I swiped up to unlock it, the green HTC came back up and eventually the thing would reboot.
So I started looking around to see what other ROM's were out there at the moment and flashed ViperOne, all was well, updated my radio, firmware, and such. However, every-time my phone would go into a regular boot after setting up the ViperOne ROM, it would freeze.
So desperate for a fix I hurriedly wiped the system, used CWM recovery to reinstall the stock rom.
Upon doing this I decided I should take advantage of the stock status of the phone and get the OTA's. This is where I became stupid!!!!!
Apparently doing such a thing re-locks your bootloader. Since I wiped the system SU was not longer installed and I lost root as well. Now I cannot issue ANY fastboot FLASH commands from my adb/fastboot CMD.
HELP, pretty, pretty please!!!
I really don't like sense at all, and think that Blinkfeed is the largest piece of #[email protected]*&^% I have ever seen.
Thanks in advance for even reading!
***Edit***
Forgot to mention what's currently running on my phone:
Build/OS: 4.3 JB CL278010 2.10.605.1
Kernal: 3.4.10-g40851b1
[email protected] #1
Baseband v. (Radio) : 1.12.41.1112_2
Basically stock jelly bean, used a stock RUU version flashed via fastboot flash command. Once phone rebooted with stock then applied the 2 previous OTAs I had missed coming from 1.10.605.10 (4.2)
Are you s-off? You could always just do the 2.10.605.1 ruu, hopefully it works and boots. Then use firewater to get unlocked again. Or does the fastboot oem rebootRUU cmd not work?
cmlusco said:
Are you s-off? You could always just do the 2.10.605.1 ruu, hopefully it works and boots. Then use firewater to get unlocked again. Or does the fastboot oem rebootRUU cmd not work?
Click to expand...
Click to collapse
Yes I am still s-off, thank goodness!
I just can't get any flash commands to work, even in oem rebootrRUU.
I can try going through the process your suggesting and see if it works, will update with results.
What errors do you get when trying fastboot cmds?
"What errors do you get when trying fastboot cmds?"
Once I am in bootloader and go into fasbootusb this is what I have tried:
fastboot oem rebootRUU (phone flashes and comes up with the silver HTC on the screen)
Send the command for recovery:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery-clockwork-touch-6.0.4.7-m7vzw.img
target reported max download size of 1526722560 bytes
sending 'recovery' (8786 KB)...
OKAY [ 1.159s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.199s
If I try to flash a zip:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip superuser.zip
target reported max download size of 1526722560 bytes
sending 'zip' (4538 KB)...
OKAY [ 0.697s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 0.972s
It will respond (obviously) when I give it:
fastboot reboot-bootloader
But am not able to enter any adb commands as there isn't a recovery installed!!
Here is the info from the phone:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.12.41.1112_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.605.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxx
(bootloader) imei:xxxxxxx
(bootloader) meid:xxxxxxxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4242mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3c88cdd7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.073s
The fastboot system will let me do things like, change my CID from VZW_01 to a super CID11111111 and back again, no errors, but not sure how much help that is...
I worry about trying to flash a new RUU because I can't back anything up right now....also just to be sure I heard I shouldn't upgrade further to Kit-Kat as there isn't a unlocked bootloader exploit yet...correct? (Obviously if I was still unlocked, and not relocked it wouldn't be an issue)
Click to expand...
Click to collapse
Yeah dont upgrade to kk or your sol on rooting. Try to flash twrp with fastboot. http://vzw1files.dyndns.org/RECOVERIES/twrp/Twrp_2.6.3.4_RUU_Mode.zip
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
fastboot reboot-bootloader
Then see if you can enter twrp recovery.
cmlusco said:
Yeah dont upgrade to kk or your sol on rooting. Try to flash twrp with fastboot.
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip nameoffile.zip
fastboot reboot-bootloader
Then see if you can enter twrp recovery.
Click to expand...
Click to collapse
YAY!!!! That worked
:good:
Thank you for all of your help!! I really appreciate it, I knew there was probably a way to get a custom recovery installed, I just had run out of plays in my own knowledge book!!
I will now be able to do a nandroid b/u and get rid of the stupid sense Blinkfeed, belch! lol
Is there a way to sim unlock my htc one v?
I've unlocked the bootloader, rooted the device, put it on s-off, installed CyanogenMod Android 4.1.2, kernel version 3.0.16-HELLBOY; i flashed the kernel and rom; i tried to upgrade the ruu but it returned me the error 131 which reffered to some incompatibility ruu, even tho it was the most appropiate one.
another thing i tried was to hack into the mmcblk0p6 and take the un_lock_code but the unlock.sh returned me this error:
[email protected]:/ # IMEI:
[email protected]:/ # UN_Lock_code:
[email protected]:/ # /system/unlock.sh[34]: + + : unexpected 'end of expression'
my radio is 3831.19.00.120. The network is locked on O2, UK. I've tried a lot of things, but nothing worked.
Can you help me guys?
Thanks in advance!
XTZY23 said:
Is there a way to sim unlock my htc one v?
I've unlocked the bootloader, rooted the device, put it on s-off, installed CyanogenMod Android 4.1.2, kernel version 3.0.16-HELLBOY; i flashed the kernel and rom; i tried to upgrade the ruu but it returned me the error 131 which reffered to some incompatibility ruu, even tho it was the most appropiate one.
another thing i tried was to hack into the mmcblk0p6 and take the un_lock_code but the unlock.sh returned me this error:
[email protected]:/ # IMEI:
[email protected]droid:/ # UN_Lock_code:
[email protected]:/ # /system/unlock.sh[34]: + + : unexpected 'end of expression'
my radio is 3831.19.00.120. The network is locked on O2, UK. I've tried a lot of things, but nothing worked.
Can you help me guys?
Thanks in advance!
Click to expand...
Click to collapse
That depends on what fastboot commands your hboot supports. If you have an eng hboot you can remove simlock with fastboot. But I cannot remember the command off hand. Connect up to the pc in fastboot mode and issue the.command fastboot oem h and it will output all the options available. Post them here for us all to learn from please
Sent from my HTC Desire S using Tapatalk
htc one v_commands
heavy_metal_man said:
That depends on what fastboot commands your hboot supports. If you have an eng hboot you can remove simlock with fastboot. But I cannot remember the command off hand. Connect up to the pc in fastboot mode and issue the.command fastboot oem h and it will output all the options available. Post them here for us all to learn from please
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
this is what it returned:
C:\Fastboot>fastboot oem h
...
(bootloader) command list
(bootloader) get_identifier_token
(bootloader) checkKeycardID
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) erase_phone_storage
(bootloader) gotohboot
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloader) readmeid
(bootloader) lock
(bootloader) writesecureflag
(bootloader) readsecureflag
(bootloader) readsimlocktype
(bootloader) clearsimlocktype
(bootloader) readcid
(bootloader) writecid
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) read_sandisk_fw
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Fastboot>
XTZY23 said:
(bootloader) readsimlocktype
(bootloader) clearsimlocktype
(bootloader) readcid
(bootloader) writecid
Click to expand...
Click to collapse
I would use these 2 sets here. First make a nandroid backup, just incase
Then issue these fastboot commands one after another and copy the results.
Fastboot oem readcid
Fastboot oem readsimlocktype
All good? Now first we want to change your cid to super. So issue this command
Fastboot oem writecid 11111111
Fastboot reboot bootloader
Fastboot oem readcid
Your cid should now show up as 11111111, that's 8 1's
All good? Lastly we issue these commands.
Fastboot oem clearsimlocktype
Fastboot reboot
Now just check your simcard and all should be well you can now flash any ruu for any carrier without issue, but always check its compatible with your model type first!
Sent from my HTC Desire S using Tapatalk
fisrt step:
C:\Fastboot>fastboot oem readcid
...
(bootloader) cid: O2___001
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Fastboot>fastboot oem readsimlock
type
...
(bootloader) sdcc_init_memory_device done
(bootloader) Wait for AMSS ready
(bootloader) AMSS is ready
(bootloader) readsimlocktype: SimLockType: 0
OKAY [ 21.759s]
finished. total time: 21.760s
step 2:
C:\Fastboot>fastboot oem writecid 11
111111
...
(bootloader) AMSS is ready
(bootloader) buf_addr:4FC300,buf_size:200,start_sector:1739D
(bootloader) sdcc_init_memory_device done
(bootloader) Finish write sector address 1739D ...
(bootloader) writecid: successfully
OKAY [ 0.691s]
finished. total time: 0.692s
C:Fastboot>fastboot reboot-bootload
er
rebooting into bootloader...
OKAY [ 0.151s]
finished. total time: 0.153s
C:\Fastboot>fastboot oem readcid
...
(bootloader) cid: 11111111
OKAY [ 0.004s]
finished. total time: 0.005s
C:\Fastboot>fastboot oem clearsimloc
ktype
...
(bootloader) sdcc_init_memory_device done
(bootloader) Wait for AMSS ready
(bootloader) AMSS is ready
OKAY [ 21.758s]
finished. total time: 21.760s
C:\Fastboot>fastboot reboot
rebooting...
finished. total time: 0.155s
C:\Fastboot>
XTZY23 said:
fisrt step:
C:\Fastboot>fastboot oem readcid
...
(bootloader) cid: O2___001
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Fastboot>fastboot oem readsimlock
type
...
(bootloader) sdcc_init_memory_device done
(bootloader) Wait for AMSS ready
(bootloader) AMSS is ready
(bootloader) readsimlocktype: SimLockType: 0
OKAY [ 21.759s]
finished. total time: 21.760s
step 2:
C:\Fastboot>fastboot oem writecid 11
111111
...
(bootloader) AMSS is ready
(bootloader) buf_addr:4FC300,buf_size:200,start_sector:1739D
(bootloader) sdcc_init_memory_device done
(bootloader) Finish write sector address 1739D ...
(bootloader) writecid: successfully
OKAY [ 0.691s]
finished. total time: 0.692s
C:Fastboot>fastboot reboot-bootload
er
rebooting into bootloader...
OKAY [ 0.151s]
finished. total time: 0.153s
C:\Fastboot>fastboot oem readcid
...
(bootloader) cid: 11111111
OKAY [ 0.004s]
finished. total time: 0.005s
C:\Fastboot>fastboot oem clearsimloc
ktype
...
(bootloader) sdcc_init_memory_device done
(bootloader) Wait for AMSS ready
(bootloader) AMSS is ready
OKAY [ 21.758s]
finished. total time: 21.760s
C:\Fastboot>fastboot reboot
rebooting...
finished. total time: 0.155s
C:\Fastboot>
Click to expand...
Click to collapse
Did it simunlock OK?
Sent from my Nexus 7 using Tapatalk
Hmm, maybe yes maybe not
It passed the sim network locked screen, but now it says "no network available" and when im making a call, it says "mobile network unavailable" \
I REINSTALLED THE RUU i was trying to install it in the first place and it worked. so thanks for your help
PS: the new challenge is this error: mobile network unavailable because it is disconnected
************update***************
1.last night i put s-on on my phone...but
2.even on s-off i could not unlock the bootloader after installing the RUU_PRIMO_U_ICS_40A_HTC_Europe_2.22.401.1_Radio_20.76.30.0835U_3831.19.00.120_release_273801_signed
3. no bootloader unlock->no root->no s-off->no simlock
4. the message header is ****Relocked**** and the error the i receive when i try to unlock the bootloader again is:
C:\Fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.640s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.650s
***********fixed this one*************
HTC ONE toolkit 2.0-Squabbi-- saved me fro a lot o work! great thanks to squabbi!
XTZY23 said:
It passed the sim network locked screen, but now it says "no network available" and when im making a call, it says "mobile network unavailable" \
I REINSTALLED THE RUU i was trying to install it in the first place and it worked. so thanks for your help
PS: the new challenge is this error: mobile network unavailable because it is disconnected
Click to expand...
Click to collapse
http://www.sieempi.eu/blog/2011/09/22/universal-sim-unlock-for-s-offed-htc-devices-536 ok give this a bash pal. will hopefully fix the issue.
GSM problem/hardware problem
thanks heavy_metal_man for replies!
the config.dat file worked, partially i think, returning only one error: Open Cid file failed.
as i could see my phone does not react to find any mobile network available, even tho my phone is "reading" the simcard now. i can see contacts, messages, etc.
ps: i don't have the back cover. would that be the problem?
XTZY23 said:
thanks heavy_metal_man for replies!
the config.dat file worked, partially i think, returning only one error: Open Cid file failed.
as i could see my phone does not react to find any mobile network available, even tho my phone is "reading" the simcard now. i can see contacts, messages, etc.
ps: i don't have the back cover. would that be the problem?
Click to expand...
Click to collapse
The back cover for these kinds of phones usually have "antenna boosting" pads. My htc sensation gets no signal without the back cover on.
For anyone else I would recommend trying the linked website solution from sieempi before fastboot commands
Sent from my Nexus 7 using Tapatalk
I'll try my best to be as detailed as possible.
I have an HTC One M9 from Sprint. Custom rom on it, I believe it was either Viper Rom or BadBoyz. Running a TWRP PRE 3.0 recovery.
My phone had a pattern lock screen.
I had let the phone sit for about a month with out use, after which I attempted to turn it back on to use it, what I got was a continuous HTC loading screen. So I'm thinking no big deal, all I gotta do is boot into recovery and reflash it.
I boot into recovery, It won't format a number of partitions (I.E. data, system, cache) to allow the flash.
I follow instructions in this video:
with no luck, still won't flash.
So after a few hours of research and attempting different versions of twrp and cwm, it no longer has a bootable recovery. any TWRP 3.0 and up wouldn't run at all, no CWM recovery would run.
My understanding is that those partitions were encrypted and pre 3.0 for twrp can't handle the encryption or some such. I flash a few different versions, going from pre 3.0 to post 3.0, with post 3.0 still not booting but pre 3.0 booting.
THEN
After trying to flash back to a pre 3.0 twrp, it acts as it takes it, but when i go to boot into recovery i get:
"Failed to boot to recovery mode"
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery C:\Users\PropertyCO\twrp.img
target reported max download size of 800000000 bytes
sending 'recovery' (36288 KB)...
OKAY [ 3.063s]
writing 'recovery'...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.562s]
finished. total time: 5.629s
is what fastboot returns, yet it won't boot to recovery.
So, my next attempt was to run an RUU.
RUU_HIMA_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_3.41.651.41
I run it, starting with my phone in download mode, RUU sees it just fine, goes to reboot into bootloader. with out assistance when it reboots it just brings up a metalic HTC logo and sits there, so when it reboots i'll hold volume up and down to get it to the boot loader. after some processing from the RUU it gives me the error 170 - USB connection error. Me thinking it's either some drivers messing it up or the cable, i try another laptop, and a series of different cables, no luck there.
I find out that I have to have the bootloader locked to run a RUU, so I attempt to relock the bootloader to see if that fixes the error.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
(bootloader) RELOCK device
OKAY [ 0.286s]
finished. total time: 0.287s
phone reboots, i force it into bootloader cause it doesn't automatically go to it, still says "*** UNLOCKED ***" up at the top.
fastboot getvar all:
Code:
(bootloader) kernel: lk
(bootloader) product: htc_himawhl
(bootloader) version: 1.0
(bootloader) imei: XXXXXXXXXXXXXX
(bootloader) version-main: 3.41.651.4
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA20000
(bootloader) cid: SPCS_001
all:
finished. total time: 0.048s
Thanks in advance!
Edit:
Attempted the ZIP method in this forum and failed too:
https://forum.xda-developers.com/showthread.php?t=1928439
Your nand is corrupt. Dead phone.
Beamed in by telepathy.
hello! my new member to the rooting community and i'm looking to get some help. i have a htc one m8s that is softbricked, i can flash twrp to recovery but when i use fastboot reboot-bootloader and enter recovery, it just reboots back into stock recovery.
i tried this, https://forum.xda-developers.com/general/help/phone-booting-default-recovery-flashing-t3720282. didnt work for me, i put the twrp file in the adb folder, renamed it recovery and flashed it. however when i did fastboot boot recovery.img it just said downloading boot.img.
twrp file used: twrp-3.0.2-0-m8ql.img
getvar info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.11.161.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0b9a12e3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
any help is appreciated, thank you
redstonedudeHD said:
hello! my new member to the rooting community and i'm looking to get some help. i have a htc one m8s that is softbricked, i can flash twrp to recovery but when i use fastboot reboot-bootloader and enter recovery, it just reboots back into stock recovery.
i tried this, https://forum.xda-developers.com/general/help/phone-booting-default-recovery-flashing-t3720282. didnt work for me, i put the twrp file in the adb folder, renamed it recovery and flashed it. however when i did fastboot boot recovery.img it just said downloading boot.img.
twrp file used: twrp-3.0.2-0-m8ql.img
getvar info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.11.161.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0b9a12e3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
any help is appreciated, thank you
Click to expand...
Click to collapse
It isnt working for you because you have to boot directly into recovery, you can't let the device boot to any other mode, if you boot to any mode other than recovery, a device will revert back to stock recovery. You are rebooting to bootloader mode instead of recovery mode, this is causing the device to revert to stock recovery instead of booting into the TWRP that you flashed.
After flashing TWRP, instead of using the fastboot reboot-bootloader command, use the adb reboot command, enter it as soon as you are done flashing the recovery.
Use the adb command below:
adb reboot recovery
Then you should boot into TWRP.
Sent from my SM-S767VL using Tapatalk
hey, thanks for helping me out, but i cant get adb to detect my device, if tried multiple drivers for my phone and cant seem to get it to detect, any help with this one? thanks. also, fastboot can detect my phone just fine. ive tried the official htc drivers using sync manager, android bootloader interface, android adb composite interface and android adb interface. any help is appreciated, thank you!
as a side note, while trying to resolve this myself i found a post that said it was very hard to break the phone with s-on, which gives me hope.
redstonedudeHD said:
hey, thanks for helping me out, but i cant get adb to detect my device, if tried multiple drivers for my phone and cant seem to get it to detect, any help with this one? thanks. also, fastboot can detect my phone just fine. ive tried the official htc drivers using sync manager, android bootloader interface, android adb composite interface and android adb interface. any help is appreciated, thank you!
as a side note, while trying to resolve this myself i found a post that said it was very hard to break the phone with s-on, which gives me hope.
Click to expand...
Click to collapse
Ok, let's take a couple of steps back. Do you know if your bootloader is unlocked? Flashing TWRP won't work if the bootloader is locked.
@xunholyx, could there be something that is HTC specific that they are overlooking?
Sent from my SM-S767VL using Tapatalk
bootloader is unlocked
redstonedudeHD said:
bootloader is unlocked
Click to expand...
Click to collapse
Try flashing the TWRP using the fastboot flash recovery command
Then try using this command:
fastboot boot recovery (name of your recovery file)
Sent from my SM-S767VL using Tapatalk
flashed twrp using the fastboot command returns this:
c:\adb>fastboot flash recovery recovery.img
target reported max download size of 16777216 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 6096896 is not a multiple of the block size 4096
sending sparse 'recovery' (14415 KB)...
error: write_sparse_skip_chunk: don't care size 6096896 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 6096896 is not a multiple of the block size 4096
OKAY [ 1.541s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.560s
using the htc_fastboot returns this
c:\adb>htc_fastboot flash recovery recovery.img
sending 'recovery' (30006 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 3(s)
but both htc_fastboot and fastboot both return this
c:\adb>htc_fastboot boot recovery recovery.img
cannot load 'recovery': No error
c:\adb>fastboot boot recovery recovery.img
cannot load 'recovery': No such file or directory
@Droidriven any idea what i can do?
double send
redstonedudeHD said:
hey, thanks for helping me out, but i cant get adb to detect my device, if tried multiple drivers for my phone and cant seem to get it to detect, any help with this one? thanks. also, fastboot can detect my phone just fine. ive tried the official htc drivers using sync manager, android bootloader interface, android adb composite interface and android adb interface. any help is appreciated, thank you!
as a side note, while trying to resolve this myself i found a post that said it was very hard to break the phone with s-on, which gives me hope.
Click to expand...
Click to collapse
Do you have USB debugging turned on in developer options? ADB commands won't work if you don't.
---------- Post added at 11:55 AM ---------- Previous post was at 11:50 AM ----------
redstonedudeHD said:
flashed twrp using the fastboot command returns this:
c:\adb>fastboot flash recovery recovery.img
target reported max download size of 16777216 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 6096896 is not a multiple of the block size 4096
sending sparse 'recovery' (14415 KB)...
error: write_sparse_skip_chunk: don't care size 6096896 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 6096896 is not a multiple of the block size 4096
OKAY [ 1.541s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.560s
using the htc_fastboot returns this
c:\adb>htc_fastboot flash recovery recovery.img
sending 'recovery' (30006 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 3(s)
but both htc_fastboot and fastboot both return this
c:\adb>htc_fastboot boot recovery recovery.img
cannot load 'recovery': No error
c:\adb>fastboot boot recovery recovery.img
cannot load 'recovery': No such file or directory
Click to expand...
Click to collapse
It seems to have flashed properly with htc_fastboot.
Try flashing it again, then
htc_fastboot reboot bootloader
then select boot to recovery from the bootloader menu on your phone from there.
It should take you to TWRP
hey @xunholyx there is no command for that in the htc fastboot, just brings up the help menu for fastboot. would normal reboot from fastboot work? or would twrp be overwritten by stock recovery? thanks for the help.
redstonedudeHD said:
hey @xunholyx there is no command for that in the htc fastboot, just brings up the help menu for fastboot. would normal reboot from fastboot work? or would twrp be overwritten by stock recovery? thanks for the help.
Click to expand...
Click to collapse
It should work with regular fastboot reboot bootloader then selecting recovery from there via your phone
EDIT: I have never had to use HTC's fastboot myself. It is necessary for flashing large files from your PC. I always flashed the large files (eg: RUUs) via the SD card method. But that wasn't for recovery.img s, it was for RUUs
EDIT #2: I'm going to request to the moderators to have this thread moved to a forum where you might find other help. You don't have to do anything about it. It will just get moved. The forum I'm moving it to is for the regular M8 and not the M8s, but people there will be able to offer help that you won't get here. I'll continue to monitor this thread there and offer help if I can.
hey @xunholyx, sorry i havent been active, got burnt out on trying to fix it lol, but im back again.
found a way to use the normal fastboot to flash recovery (i think im no genius) using this command
c:\adb>fastboot flash:raw recovery recovery.img
sending 'recovery' (30006 KB)...
OKAY [ 2.121s]
writing 'recovery'...
OKAY [ 0.745s]
however when i use fastboot reboot or fastboot boot-bootloader ect, recovery just brings me back to fastboot. anyone any ideas?
i still cant adb to detect my device either. i know this might sound stupid but does my phone have to be in a specific state to use adb commands? i can only access the stock recovery so anything other then that and im screwed lol, thanks for the help!
redstonedudeHD said:
hey @xunholyx, sorry i havent been active, got burnt out on trying to fix it lol, but im back again.
found a way to use the normal fastboot to flash recovery (i think im no genius) using this command
c:\adb>fastboot flash:raw recovery recovery.img
sending 'recovery' (30006 KB)...
OKAY [ 2.121s]
writing 'recovery'...
OKAY [ 0.745s]
however when i use fastboot reboot or fastboot boot-bootloader ect, recovery just brings me back to fastboot. anyone any ideas?
i still cant adb to detect my device either. i know this might sound stupid but does my phone have to be in a specific state to use adb commands? i can only access the stock recovery so anything other then that and im screwed lol, thanks for the help!
Click to expand...
Click to collapse
Sorry I haven't responded sooner.
I would suggest you run an RUU. The problem is, I don't know of any RUUs myself for your current firmware version, and since you are S-On, you can't roll back to an older version.
If you can find an RUU for 2.11.161.1 download it and flash it. The only ones I can find are from a previous Android version. (1.xx.xxx.x)
Also, there is a newer TWRP version than the one you are using. Maybe that might be the issue? I can't be sure about this, since I'm familiar with the HTC M8, but not the HTC M8s.
You can download the updated TWRP version from here.
I believe it was updated to work with 2.xx.xxx.x firmware. But I'm not positive. It can't hurt to try it out.
hey @xunholyx i found a one that matches my os and my cidnum, now what do i do with it? also, i found it on this website, hopefully it will help a few others, https://www.hardreset.info/devices/htc/htc-one-m8/faq/firmware/
redstonedudeHD said:
hey @xunholyx i found a one that matches my os and my cidnum, now what do i do with it? also, i found it on this website, hopefully it will help a few others, https://www.hardreset.info/devices/htc/htc-one-m8/faq/firmware/
Click to expand...
Click to collapse
There's two there. I don't know what the difference between "partial" and the other one is. I would assume the partial one has the boot.img and maybe the recovery.img removed?
Use the other one. There are two ways to flash it since it is an RUU.zip.
#1: In fastboot: fastbbot flash zip **drag and drop the zip here**
#2: Rename the zip by deleting everything in the name of it except for 0PKVIMG (and .zip of course) and place that onto your extSD card (must be formatted to FAT32)
Put that into your phone then bot to bootloader. It should find the file automatically. If it doesn't, boot to hboot from boot loader.
From there it's super easy. Follow the on screen prompts. Volume up to confirm the flash. Power button to reboot after the flash is done.
Good luck! I hope you get everything up and running again.