Hi all,
@THE company I work we found a htc one m8s that when I booted it went straight to bootloader menu.
I want to get it working again so I started reading here on the forums, download some stuff from ruu.lalleman.net that I found in one of the other treads. In the end i'm still stuck and i'm hoping to get some advice through this channel.
Here is my current status
when the devices is connected to the PC it boots ALWAYS straight to bootloader with the following info
software status : Modified
unlocked
m8QL_UL PVT SHIP S-ON
HBOOT-3.19.0.000
[email protected]
OS-1.16.401.10
eMMC-boot 2048MB
aug 13 2015
Fastboot USB with the normal stuff
when I try to load a RUU through the exe I reboot the device and then keeps waiting with in the end a disconnect (saying I need to connect my device) the device itself is already back in bootloader window.
when I try to use htc_fastboot to flash a recovery it gives me
fastboot flash recovery recovery.img
sending 'recovery' (6002 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 1(s)
but then on reboot it's straight back to bootloader menu no recovery
when I try to lock the device I get
fastboot oem lock
... (bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [ERR] Failed to disable wdog debug: 15
(bootloader) [INFO] Calling SCM to disable SPMI PMIC arbiter
(bootloader) [ERR] Cannot halt SPMI arbiter!!
(bootloader) [INFO] Rebooting device
(bootloader) [INFO] Rebooting device arbiter!!I PMIC arbitery-
FAILED (unknown status code)
Execution time is 1(s)
I did get it unlocked (as it was locked before but relocking is not working)
Also fastboot devices shows me the devices but adb devices shows nothing (tried both htc drives and general android ones)
These are my var all info
fastboot getvar all
(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: 1.16.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: HTC__031
(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: 1d456ef7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
all: Done!
Execution time is 28(ms)
Hoping on any help from here
Greetings
Tom
Little update:
I kept on trying different versions from recovery / boot / ruu's in the hope that one works but nothing so far.
In another topic somewhere I did found that as long as my device is unlocked it will not work to use RUU, so locking the device again will be my first step.
I did notice that when I ended my adventure yesterday evening I wasn't able to turn the phone off, I always rebooted (in like a millisecond) back to bootloader as long as it was connected to the pc. I had to remove the usb connection and then try couple of times with volume-up / power to turn it off.
I did do the 2 minutes bright licht / volume up + down + power button trick to reset the battery but that didn't change anything.
also as a last minute addition
when I do the fastboot -> image CRC i'm getting a 0X0 on sbl2 - sbl3 - boot and recovery so it seems that what ever I do with htc_fastboot flash is not sticking.
Going to look into trying to get it locked again now first in combination with trying to find out why I can't write to the damn phone (adb isn't working ether so maybe driver problem also ?)
The adventure continues
Tom
adb works only while on running OS or in custom recovery (don't know whether it works on stock recovery) not on fastboot/bootloader.
Only fastboot (generic) or htc_fastboot works on fastboot.
Is the RUU that you tried
0PKVIMG_M8_QL_UL_L50_SENSE60_HTC_Europe_1.16.401.1 [email protected]_15.00_016_F_release_450 409_combined_signed.zip ?
ckpv5 said:
adb works only while on running OS or in custom recovery (don't know whether it works on stock recovery) not on fastboot/bootloader.
Only fastboot (generic) or htc_fastboot works on fastboot.
Is the RUU that you tried
0PKVIMG_M8_QL_UL_L50_SENSE60_HTC_Europe_1.16.401.1 [email protected]_15.00_016_F_release_450 409_combined_signed.zip ?
Click to expand...
Click to collapse
That is indeed the RUU i tried, i got it based on the fastboot var all i did.
Still trying to get my Phone locked again as that is holding back the ruu upgrade now from what i see.
Have you tried using htc_fastboot to relock ?
It seems fastboot generic mostly not working for M8s.
ckpv5 said:
Have you tried using htc_fastboot to relock ?
It seems fastboot generic mostly not working for M8s.
Click to expand...
Click to collapse
Yhea i did it with the htc_fastboot version.
another update,
After some more trial and error while aiming for the locking of my phone i'm still stuck.
Both my boot and my recovery are empty it seems (the 0x0 from the image crc) and all the others still have 0xA.....B or what ever value in them
All the writing I do like
C:\tel>htc_fastboot.exe flash recovery recovery_signed.img
sending 'recovery' (30080 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 3(s)
seems to be working but that doesn't change the crc value's nether does it allow me to use the recovery from the hboot menu.
also when I type stuff like htc_fastboot oem rebootRUU it brings me straight back to the bootloader menu, no black screen to do htc_fastboot flash zip rom.zip.
What I didn't try yet is using a SD-card and see if that fixes it (I could put that card in my other phone, write stuff to it and use it in the M8s.
Anybody got any expereance for using a sdcard to flash the device back to stock.
@ this moment I will be kind of happy with anything that advances me a step
Tom
I got it to work
You may as well give up.
Android will continue to suck and be a deep state tool.
kruc Ire said:
I got it to work
You may as well give up.
Android will continue to suck and be a deep state tool.
Click to expand...
Click to collapse
How do you mean give up ?
is there no way arround based on your opinion from what i posted above ?
I Always hoped it was my lack of knowledge that was holding me back in fixing it ...
Ok if you wanna do it like i did you gotta use the sd card. It should work. Call it by its shortened name and relock the phone first. It can take a long time in several stages.
I was a bit down on android since google keeps screwing with it like taking away panoramio and adding miles upon miles of bloat and force resetting my permissions which I believe I have finally found a solution to in m8s.
If you wanna do it you can. Use that same 1.8 GB firmware we can find on the web. And rename it to the m8s required: 0PKVIMG.zip (i am going offa memory but this looks right to me???) and put it in the root of your microSD. The bootloader should be "relocked" anything I forgot? You don't have to reflash the std recovery first unless I forgot
Then once these things are inplace you should see a full flash after bootin ta bootloader.
kruc Ire said:
Ok if you wanna do it like i did you gotta use the sd card. It should work. Call it by its shortened name and relock the phone first. It can take a long time in several stages.
I was a bit down on android since google keeps screwing with it like taking away panoramio and adding miles upon miles of bloat and force resetting my permissions which I believe I have finally found a solution to in m8s.
If you wanna do it you can. Use that same 1.8 GB firmware we can find on the web. And rename it to the m8s required: 0PKVIMG.zip (i am going offa memory but this looks right to me???) and put it in the root of your microSD. The bootloader should be "relocked" anything I forgot? You don't have to reflash the std recovery first unless I forgot
Then once these things are inplace you should see a full flash after bootin ta bootloader.
Click to expand...
Click to collapse
I did those things and placed the file on the SD card ( 0PKVIMG.zip )
When I go to the phone then and run it it gives me the following error:
Device halted due to Large Image update fail!
press <power> to reboot.
I looked into that and seems I need to do a partial flash for that but didn't found more info on that yet.
Also i'm still stuck on the htc_fastboot OEM lock error i'm getting (see above)
Tom
TomBrunson said:
I did those things and placed the file on the SD card ( 0PKVIMG.zip )
When I go to the phone then and run it it gives me the following error:
Device halted due to Large Image update fail!
press <power> to reboot.
I looked into that and seems I need to do a partial flash for that but didn't found more info on that yet.
Also i'm still stuck on the htc_fastboot OEM lock error i'm getting (see above)
Tom
Click to expand...
Click to collapse
You need to have plenty of space. I have seen large image update fail at some time before. I'll see if I can find my photos from the flash on my m8 (I used the m8 to document the m8s firmware flash). It doesn't have to be "locked", "relocked" is enough
I made that video but if the F'N censors won't let me put up the lyrics of a song they HATE in their pinheads then I won't be posting their garbage they WOULD view.
I'll keep putting up large videos though just to chew up this sh!tty world's resources. If it's a world of creeps it's
Music videos mostly. Ooh how they HATE my beautiful music...and I can hear the little b##ch there in her fuzzy chair. Like she spoke directly into my head. And if it hadn't taken me so long to make a thumbnail she wouldn't have been able to install her trick. Literally FFFF youtube.
kruc Ire said:
You need to have plenty of space. I have seen large image update fail at some time before. I'll see if I can find my photos from the flash on my m8 (I used the m8 to document the m8s firmware flash). It doesn't have to be "locked", "relocked" is enough
Click to expand...
Click to collapse
Is there a different command to Relock as to Lock ?
I couldn't find anything else then htc_fastboot oem lock
Tom
Ok i'm over it. I attached a different (worse) song and reuploaded it. No censorship now.
HTC M8s firmware flash in photos:
Please note I only started making a video because I noticed that time bar on upper right about 15 minutes into the (uninterrupted) flash. So that took a long time and I was concerned about the messed up and overprinted text and made photos during every new screen between the third or fourth at the start (when I caught up with my camera) up till the time of video starting.
So yeah what I am trying to say is it seemed to take very long, with many seemingly false starts and failures. Only by waiting did it finally achieve correctness.
thank you for the video
Seems so that it's still the same issue for me as I don't get my phone locked or relocked
i'll keep on looking aint giving up that quick
TomBrunson said:
thank you for the video
Seems so that it's still the same issue for me as I don't get my phone locked or relocked
i'll keep on looking aint giving up that quick
Click to expand...
Click to collapse
Are you sure you have the correct command? There is a lot of bad info out there. Better get a 2nd source and third for commands. Did you be sure to enable adb bridge in dev options? Can't forget to do that. Go through the entire thing at HTC.dev and do all it says and download their fastboot. Then be sure to have adequate space on phone and storage. You have a nandroid? Then you could try wiping and starting from zero with the flash. This may have been what I done. I definitely did something like that similarly very recently and I think it was cause I was trying the new Los rom just before I gave up on it and decided to do this firmware.
kruc Ire said:
Are you sure you have the correct command? There is a lot of bad info out there. Better get a 2nd source and third for commands. Did you be sure to enable adb bridge in dev options? Can't forget to do that. Go through the entire thing at HTC.dev and do all it says and download their fastboot. Then be sure to have adequate space on phone and storage. You have a nandroid? Then you could try wiping and starting from zero with the flash. This may have been what I done. I definitely did something like that similarly very recently and I think it was cause I was trying the new Los rom just before I gave up on it and decided to do this firmware.
Click to expand...
Click to collapse
When I got the phone it was locked, I then did all the steps to unlock it as I hoped that would be the solution. Those steps did work but it didn't solve the problem. I think wanted to do the RUU thing but therefor the phone needs to be locked or relocked (htc_fastboot oem lock) but hat gives me errors as I posted before.
I'm still in the process of reading as much as possible to find different ways to lock or relock the phone in order to do the RUU update.
Greetings,
Tom
You have never gotten it to lock? I thought you said you couldn't get the zip to work?
---------- Post added at 06:53 PM ---------- Previous post was at 06:38 PM ----------
TomBrunson said:
When I got the phone it was locked, I then did all the steps to unlock it as I hoped that would be the solution. Those steps did work but it didn't solve the problem. I think wanted to do the RUU thing but therefor the phone needs to be locked or relocked (htc_fastboot oem lock) but hat gives me errors as I posted before.
I'm still in the process of reading as much as possible to find different ways to lock or relock the phone in order to do the RUU update.
Greetings,
Tom
Click to expand...
Click to collapse
What output does your cmd window give u? Can you show a screenshot of what your command is and the output.
I see. You are trying to put a lollipop. Still first ya gotta lock it does anyone remember the rules for firmware flash? Is it going to screw up the phone to flash the MM 60 sense 70 ? Dude are you in Europe? The 60 70 I flashed from my microSd was a EUROPE.
Related
Hi guys.
I rooted my 816 using CWM and SuperSU months ago. Now, there's an OTA update to Android 6.0 which will hopefully render the usefulness of root obsolete, as I mostly need it for link2sd (they also cite better RAM management as a new feature, which should get rid of the horrible lag on Lollipop).
I know I have to go back to full stock, and I read a simple guide somewhere, and I thought, why don't I give it a crack. So, it said I should just "fastboot oem lock" the phone and flash the correct .zip RUU. After much trouble with connectivity and driver issues between my computer (adb server is out of date. killing...; device offline; errors etc.) I FINALLY (after hours of troubleshooting) managed to go into fastboot via USB and lock the bootloader. Great. But, when I tried to flash the .zip, it just says waiting for device, indefinitely. Tried to go into recovery via the power buttons on the phone, but it shows an error and simply refuses to. As a sidenote, root still works, but the phone displays this in fastboot: Relocked, Security Warning.
Basically, I'm afraid to proceed because I think I'm on the wrong track, and could end up f'ing up my device altogether. I'm from Croatia so I downloaded the 5.0.1 EU version .zip from here: (can't post link, just search htcdev downloads, it's the first one).
I hate opening new threads because I'm sure someone has already had the problems I'm having, but I just can't keep searching the web for hours on end trying to find a solution. Forgive me for this guys, and please help a poor noob in need if you can.
Could you please post your device info? (Make sure to delete serialno. and imei!)
To get your device info, you'll need to make sure all drivers are up-to-date.(HTC Sync, Java and ADB)
After installing,
- Navigate to ADB folder and click on any free space while holding the shift Key
- Choose 'Open command window here'
- Once cmd is started use this command
Code:
fastboot devices
and check if your device is listed, then type
Code:
fastboot getvar all
and copy/paste code here.
nukaru said:
Could you please post your device info? (Make sure to delete serialno. and imei!)
To get your device info, you'll need to make sure all drivers are up-to-date.(HTC Sync, Java and ADB)
After installing,
- Navigate to ADB folder and click on any free space while holding the shift Key
- Choose 'Open command window here'
- Once cmd is started use this command
Code:
fastboot devices
and check if your device is listed, then type
Code:
fastboot getvar all
and copy/paste code here.
Click to expand...
Click to collapse
Oh great, you're from Germany, so you have an EU 816 too. It's an a5ul just like yours. I'll send the full info text as soon as i install SDK tools completely.
I noticed that in your guide you first flash the stock ROM, and only then lock the bootloader. In the guide I found it said to first lock the bootloader, and then flash the stock ROM. So right now, I have a locked bootloader and CWM recovery I can't get into. Is this going to be a problem?
No, you first flash the stock recovery, then relock bootloader. And if your flashed recovery works you flash the RUU.
running fastboot devices does literally nothing, just sends me to the next line.
running adb devices, on the other hand, lists my device.
great, so I messed up there. do you know how I can fix it?
Are you able to boot into fastboot USB? Have you tried the fastboot getvar all comand?
If yes, first you need to flash the stock recovery and check if the flash was a success. If you can get into recovery without any errors, relock bootloader and place the RUU file on sd-card. Boot to bootloader again and the flashing should start on its own.
nukaru said:
Are you able to boot into fastboot USB? Have you tried the fastboot getvar all comand?
If yes, first you need to flash the stock recovery and check if the flash was a success. If you can get into recovery without any errors, relock bootloader and place the RUU file on sd-card. Boot to bootloader again and the flashing should start on its own.
Click to expand...
Click to collapse
I managed to get the getvar command to work: here's the info
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.111011.20.0123
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *
(bootloader) imei: *
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a5_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P9C20000
(bootloader) cidnum: HTC__032
(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: 09813c97
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.054s
The files from my guide should work with your device.
so it doesn't matter that my bootloader is now locked? I can just follow your guide and it should work?
Have you flashed stock recovery BEFORE locking bootloader? You have to install stock recovery or the RUU won't flash. It's all in the guide.
No, i didn't. I locked the bootloader and then tried to flash the stock RUU. That's the problem.
I wish I'd seen your guide before I did anything. I assume trying to flash anything now won't work, and that I'll have to unlock the bootloader again?
edofot said:
No, i didn't. I locked the bootloader and then tried to flash the stock RUU. That's the problem.
I wish I'd seen your guide before I did anything. I assume trying to flash anything now won't work, and that I'll have to unlock the bootloader again?
Click to expand...
Click to collapse
Did you type this before flashing the RUU?
Code:
fastboot oem rebootRUU
Nope. I tried to flash the RUU with fastboot flash ... .zip but it just said: waiting for device; and nothing happened. So I'll try the rebootRUU command when I get home from classes.
You need to flash the stock recovery, otherwise you won't be able to flash any official RUU.
Unlock bootloader, flash stock recovery, relock bootloader and flash RUU.
The command won't work, since you have a custom recovery. You need to get rid of that first.
nukaru said:
You need to flash the stock recovery, otherwise you won't be able to flash any official RUU.
Unlock bootloader, flash stock recovery, relock bootloader and flash RUU.
The command won't work, since you have a custom recovery. You need to get rid of that first.
Click to expand...
Click to collapse
I unlocked the bootloader, and did everything your guide said. Everything worked perfectly.
I just have a problem right now flashing the 0P9CIMG.zip. I can't flash it over the computer (it says the data length is too large or something similar), and I can't move it to sd-card on my phone. I tried moving other files and other .zip files, and that works. I tried redownloading from mega.nz, nothing. I'm thinking the .zip gets corrupted when downloading. Can you maybe re-upload it or send it to me through a different medium?
edofot said:
I unlocked the bootloader, and did everything your guide said. Everything worked perfectly.
I just have a problem right now flashing the 0P9CIMG.zip. I can't flash it over the computer (it says the data length is too large or something similar), and I can't move it to sd-card on my phone. I tried moving other files and other .zip files, and that works. I tried redownloading from mega.nz, nothing. I'm thinking the .zip gets corrupted when downloading. Can you maybe re-upload it or send it to me through a different medium?
Click to expand...
Click to collapse
Use this HTC mini-SDK
Gibz97 said:
Use this HTC mini-SDK
Click to expand...
Click to collapse
Tried it.
Stumped by this:
Code:
C:\Users\Korisnik\Desktop\HTC mini SDK>fastboot flash zip 0P9CIMG.zip
sending 'zip'... (51060 KB) OKAY
sending time = 2.709 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 7(s)
edofot said:
Tried it.
Stumped by this:
Code:
C:\Users\Korisnik\Desktop\HTC mini SDK>fastboot flash zip 0P9CIMG.zip
sending 'zip'... (51060 KB) OKAY
sending time = 2.709 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 7(s)
Click to expand...
Click to collapse
First type this. It will reboot phone into a black screen with a silver HTC logo:
Code:
fastboot oem rebootRUU
then type:
Code:
fastboot erase cache
then type:
Code:
fastboot flash zip 0P9CIMG.zip
Sorry, I was looking for an sd-card adapter, I wasn't here.
Update: Moved the 09PCIMG.zip to the sd-card successfully this time and am flashing the img now from sd-card! Seems to be going well so far.
Success
Finally! Did it, works like a charm.
I'm still amazed by how fast the phone really is when it's stock.
Viele Dank, @nukaru, du wärst eine sehr grosse hilfe. Wenn du nach Kroatien kommst, melde mich an, du hast ein Bier und/oder Kaffe von mich (at least I tried, even without google translate)
Thank you too @Gibz97, really appreciate the effort.
If anyone reading this has the same questions I had, just follow nukaru's guide, it has all you need to know. If you have an A5_UL, it's gonna work.
Hello there!
I have now searched and searched and come upon many great threads in this massive forum however i have yet to find a solution to my current problem. Every time i have went here i have always managed to find something to help me fix my phones over the years but this this time I've hit a wall it seems.
What happened was that my phone started to crash the google apps like gallery etc. No big deal at first but then i decided to do a factory reset thinking that might fix the problem but then my phone just starts up to the HTC logo and throws several different error messages that Google.xxx.xxx could not start/has crashed. IF i click these away they appear after a while again and the phone will be stuck like that.
I can start the phone in fastboot mode to be able to use ADB etc..
The phone is currently bootloader unlocked and with S-on
Now this is what i have done:
First of all the phone wasn't in debugging mode when it crashed so I'm guessing its still not which might complicate the matter further.
* Using a TWRP.img file i managed to get the phone in to the TWRP mode on the phone. (Fastboot boot TWRPfilename.img)
I do not have any TWRP files on my phone nor any apps this was all from the files on the PC. I just mention this because thats the only sign of life the phone has given me so far.
*I tried to go in from the adb shell and enabling it using the following code:
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop"
reboot
I have no idea as to if it worked or not but the phone rebooted again.
* Tried to reflash with the right RUU for my phone with the right CID thanks to guides on this forum -- i get error 159 (this is because the CID is wrong from what ive read in other threads)
* Tried changing the CID to 11111111 but that did not work i got another error doing that:
C:\adb>fastboot oem writecid 11111111
...
(bootloader) SecuritySDInit: counter = 3
(bootloader) m8_init_sd, SD card already power on
(bootloader) [SPEW] GPIO 0 status is 0
(bootloader) sdhci_open: id=0
(bootloader) Initializing MMC host data structure and clock!
(bootloader) mmc slot#2 clock enabled
(bootloader) sdhci_set_clock: slot 2, freq 192000000
(bootloader) GPLL0 is enabled
(bootloader) clock_update_cfg_sd is done
(bootloader) sd clock set done
(bootloader) sdhci_set_bus_width: bus width 0
(bootloader) sdhci_clk_supply: freq 400000
(bootloader) Decoded CID fields:
(bootloader) Manufacturer ID: 2
(bootloader) OEM ID: 0x544d
(bootloader) Product Name: SA16G
(bootloader) Product revision: 1.1
(bootloader) Product serial number: 37A24E6D
(bootloader) Manufacturing date: 10 2013
(bootloader) sdhci_clk_supply: freq 50000000
(bootloader) sdhci_set_bus_width: bus width 1
(bootloader) Done initialization of the card
(bootloader) erase_grpsize: -16777216
(bootloader) erase_grpmult: 261077976
(bootloader) wp_grpsize: 0
(bootloader) wp_grpen: 0
(bootloader) perm_wp: 0
(bootloader) temp_wp: 0
(bootloader) [Tuxera][Error] No exFAT partition found
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 0.132s]
finished. total time: 0.132s
* Tried flashing from a .zip file with the fastboot commands.
ALL of these things I have tried with the bootloader locked and unlocked. (if this is any important info)
The phone ran the 6.12.401.4 version at the moment of the crash and that's what shows in the RUUs ive tried as well. Also the phone is not rooted.
Now is there a way to completely flush the phone out of any info and just reinstalling it like you can do with windows on a PC for example since whatever i try is met by an error message or a failed flash etc..?
some more info about the phone from getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__Y13
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.028s
1. remove your serial & imei no. on your post
2. http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
3. relock bootloader with command -
fastboot oem lock
fastboot reboot-bootloader
4. http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Thank you for your fast reply!
I have removed the lines from the post as you said and tried your links unfortunately without success. This is why im hoping you like a challange! hehe.
This is the result from the cmd when trying to flash the new RUU:
C:\Users\Genocide\Desktop\RUU>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.010s]
finished. total time: 0.011s
C:\Users\Genocide\Desktop\RUU>htc_fastboot flash zipp RUU.zip
sending 'zipp' (1687272 KB)... OKAY
writing 'zipp'... (bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
Execution time is 109(s)
C:\Users\Genocide\Desktop\RUU>htc_fastboot flash zipp RUU.zip
sending 'zipp' (1687272 KB)... OKAY
writing 'zipp'... (bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
Execution time is 109(s)
I followed your steps 1 by 1 downloaded all needed files and installs etc... Something is terribly wrong with my device it seems.
Any further ideas?
Did you skip no.3 ?
Why it is zipp not zip ?
Try again ..
If still fails, tomorrow I'll give you another method.. already in bed.
oh! ive done goofed!
It was my bad with some **** spelling there.
IT WORKED!!
I thank you sooooo much from the bottom of my heart I was sure my phone was unsaveable for a moment.
what was the difference with that RUU and the ones I've tried before? I must have tried like 4 different ones in the end out of desperation.
or was it the fastboot that was the trick?
I'm just curious on how you could spot the problem so that i can learn more about how it works.
Thanks again! Truly great work!
Sambeg said:
what was the difference with that RUU and the ones I've tried before? I must have tried like 4 different ones in the end out of desperation.
or was it the fastboot that was the trick?
Click to expand...
Click to collapse
We can't say if the RUUs you tried were correct or not, as you didn't give any specific on those (file names, where you found them, etc.).
But you do need the htc_fastboot to run the RUU.zip with fastboot command, the "generic" fastboot.exe does not work.
And you absolutely need to have a LOCKED or RELOCKED bootloader to RUU with s-on (this requirement is bypassed with s-off). So you were also compounding one wrong thing with another (when trying to flash RUU with bootloader UNLOCKED) making it even less likely you would have the successful combination of variables.
Unlocked bootloader is okay to OTA, so that is where I think some folks get confused on when to have the bootloader locked or not. But OTA and RUU are two very different things (with different requirement), and its important to remember that fact.
redpoint73 said:
We can't say if the RUUs you tried were correct or not, as you didn't give any specific on those (file names, where you found them, etc.).
Click to expand...
Click to collapse
I found them all in XDA guides/lists of stock roms, checked with my CID and European versions etc...
redpoint73 said:
But you do need the htc_fastboot to run the RUU.zip with fastboot command, the "generic" fastboot.exe does not work.
Click to expand...
Click to collapse
I think this is where all else failed since all the ones i tried had either the ADB or a file called only Fastboot.exe not this one that said HTC_fastboot.exe
redpoint73 said:
And you absolutely need to have a LOCKED or RELOCKED bootloader to RUU with s-on (this requirement is bypassed with s-off). So you were also compounding one wrong thing with another (when trying to flash RUU with bootloader UNLOCKED) making it even less likely you would have the successful combination of variables.
Click to expand...
Click to collapse
I tried all the solutions in both locked/relocked state just to be sure i had no real understanding of this before but I am now enlighten thanks to you
redpoint73 said:
Unlocked bootloader is okay to OTA, so that is where I think some folks get confused on when to have the bootloader locked or not. But OTA and RUU are two very different things (with different requirement), and its important to remember that fact.
Click to expand...
Click to collapse
Yeah those things are clear for me as well. I just had the problem with the RUU not working for me. Thanks again for all the help and the good information provided even after my problem has been solved
Sambeg said:
I found them all in XDA guides/lists of stock roms, checked with my CID and European versions etc...
Click to expand...
Click to collapse
That still doesn't tell me much about what RUUs you tried. What are the actual file names, version numbers, etc.?
Only if you are still curious why the RUUs didn't work, of course. I understand its somewhat of a moot (or purely academic) point, now that the phone is working.
redpoint73 said:
That still doesn't tell me much about what RUUs you tried. What are the actual file names, version numbers, etc.?
Click to expand...
Click to collapse
these two I've tried and it was the ones in most of the guides etc. However I tried a few more as well but i had them deleted now.
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417809_signed
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed
These 2 i just tried in the end when i had given up. I know they are not really for my phone.
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4
RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3
Sambeg said:
these two I've tried and it was the ones in most of the guides etc. However I tried a few more as well but i had them deleted now.
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417809_signed
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed
These 2 i just tried in the end when i had given up. I know they are not really for my phone.
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4
RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3
Click to expand...
Click to collapse
Somewhat as I figured. All those RUUs failed for good reason.
First and second ones: These RUUs are older (lower version number) than the main version that was on the phone (6.12.401.4), otherwise known as a "downgrade" in version. With s-on, that isn't allowed. You can only flash the same or higher version (later) RUUs; and the only way to bypass that requirement is with s-off.
Third RUU: As you know, this isn't for your phone. You can run it a million times, and it will still fail every time; as its intended to fail since the CID and MID on your device doesn't match what the RUU is looking for. The only way to run this RUU is to s-off and change your phone's CID and MID.
Forth RUU: Again, not for your phone. Plus, the Sprint version, which has partition differences from your M8 version (and most other M8 versions). You absolutely should stay away from any Sprint or Verizon firmware, as if they do manage to flash, will often lead to a radio brick on your device.
This would never flash anyway with s-on, and the safeguards of the CID and MID did their job and saved you, in this case.
So in short, you can only run RUUs that have the "401" in the spot x.xx.401.x as these are for your CID and MID. And you can only run versions equal or greater than 6.12.401.4, of which there is currently the only one (the one that worked - 6.12.401.4).
Hope that clears things up a bit for you.
redpoint73 said:
Somewhat as I figured. All those RUUs failed for good reason.
First and second ones: These RUUs are older (lower version number) than the main version that was on the phone (6.12.401.4), otherwise known as a "downgrade" in version. With s-on, that isn't allowed. You can only flash the same or higher version (later) RUUs; and the only way to bypass that requirement is with s-off.
So in short, you can only run RUUs that have the "401" in the spot x.xx.401.x as these are for your CID and MID. And you can only run versions equal or greater than 6.12.401.4, of which there is currently the only one (the one that worked - 6.12.401.4).
Hope that clears things up a bit for you.
Click to expand...
Click to collapse
Yes indeed this cleared up most of my suspicions as well as i said i knew the 3rd and 4th was wrong from the get go it was more of a test..
Thank you for all this good info i feel like im starting to get a good grip on whats good and whats working etc... I really appreciate it! Thumbs up indeed.
I have another question tho.... Why would it not let me change the CID to the supercid 11111111?
IS that due to the phone not being in debug mode or the S-on option perhaps since i know that is a security feature from the get go.
Sambeg said:
I have another question tho.... Why would it not let me change the CID to the supercid 11111111?
IS that due to the phone not being in debug mode or the S-on option perhaps since i know that is a security feature from the get go.
Click to expand...
Click to collapse
You can only change the CID (and also MID) with s-off.
redpoint73 said:
You can only change the CID (and also MID) with s-off.
Click to expand...
Click to collapse
Right as I thought then Well thanks again for helping out and clearing up my questions.
I shall now retire from this thread in peace
Hi Guys,
I have an interesting one here, which I have been battling for a couple of days!
My nephew some time ago decided to put some custom ROM’s on his M9. Recently he had some odd happenings relating to encryption (something about asking for passwords), he tried to recover it and bricked it slightly!
Twrp 3.0.2-0 is on the device, but I cannot flash anything to the recovery, even 3.0.1-0. I cannot lock/relock the bootloader and when I try to flash the Unlock_code.bin it hands in download mode and does not give me onscreen instructions. Twrp tells me it cannot mount any partitions with a crypto footer missing message. I have tired reformatting some partitions (cache and data) as well as writing zero’s to the start of the partition and they still cannot mount with an invalid argument message. It also boots straight to the bootloader (with a flash of the HTC logo screen) and I have dd’ed the boot partition off the device and it’s all zeros (not sure if some kind of protection is stopping this).
Together with this these issues, I need to hold volume up and volume down to get to the bootloader (without it flashing the htc logo), but documentation I have read says down and power. When I hold down the volume up, it boots to a white screen with HTC logo. When I hold down the volume down it boot loops the black HTC logo.
Download mode is version 3.35.401.12 and CID HTC__001.
Any help would be appreciated,
Thanks,
FlangeMonkey said:
Hi Guys,
I have an interesting one here, which I have been battling for a couple of days!
My nephew some time ago decided to put some custom ROM’s on his M9. Recently he had some odd happenings relating to encryption (something about asking for passwords), he tried to recover it and bricked it slightly!
Twrp 3.0.2-0 is on the device, but I cannot flash anything to the recovery, even 3.0.1-0. I cannot lock/relock the bootloader and when I try to flash the Unlock_code.bin it hands in download mode and does not give me onscreen instructions. Twrp tells me it cannot mount any partitions with a crypto footer missing message. I have tired reformatting some partitions (cache and data) as well as writing zero’s to the start of the partition and they still cannot mount with an invalid argument message. It also boots straight to the bootloader (with a flash of the HTC logo screen) and I have dd’ed the boot partition off the device and it’s all zeros (not sure if some kind of protection is stopping this).
Together with this these issues, I need to hold volume up and volume down to get to the bootloader (without it flashing the htc logo), but documentation I have read says down and power. When I hold down the volume up, it boots to a white screen with HTC logo. When I hold down the volume down it boot loops the black HTC logo.
Download mode is version 3.35.401.12 and CID HTC__001.
Any help would be appreciated,
Thanks,
Click to expand...
Click to collapse
Oofta. If there ever was a candidate for restoring to stock via RUU, this would be it. From the OS version you list, your SKU is 401. Head to the readme thread and follow the instructions there.
computerslayer said:
Oofta. If there ever was a candidate for restoring to stock via RUU, this would be it. From the OS version you list, your SKU is 401. Head to the readme thread and follow the instructions there.
Click to expand...
Click to collapse
Thank you for the reply, I have an RUU zip that doesn't flag any errors via SD card (not the same story via fastboot, as I get RU security errors). However when it reboots, it goes to the bootloader and not the expected rebootRUU. If I execute 'fastboot oem rebootRUU', it goes into a bootloop. I did some checking and although I could be wrong, it appears to need the boot strap to do RUU, which could be hosed.
FlangeMonkey said:
Thank you for the reply, I have an RUU zip that doesn't flag any errors via SD card (not the same story via fastboot, as I get RU security errors). However when it reboots, it goes to the bootloader and not the expected rebootRUU. If I execute 'fastboot oem rebootRUU', it goes into a bootloop. I did some checking and although I could be wrong, it appears to need the boot strap to do RUU, which could be hosed.
Click to expand...
Click to collapse
Have you tried the backup files in flippy's thread?
Beamed in by telepathy.
shivadow said:
Have you tried the backup files in flippy's thread?
Beamed in by telepathy.
Click to expand...
Click to collapse
Can you please point me to the thread your referring to?
edit: I think I have found what your refering to, I'm just looking at this (Stock_Backup_3.35.401.12.zip), I'll check it out and see if I can do anything with it.
So I tired the flippy "TWRP Backup Section II" and after the restore and selecting boot to system, it boots to the bootloader and it appears retain the original recovery, so it isn't restoring anything by the looks of it. I've also just found out that this phone is a M9u, if that makes any difference and the RUU that doesn't flag any errors is signed_2_4.
FlangeMonkey said:
So I tired the flippy "TWRP Backup Section II" and after the restore and selecting boot to system, it boots to the bootloader and it appears retain the original recovery, so it isn't restoring anything by the looks of it. I've also just found out that this phone is a M9u, if that makes any difference and the RUU that doesn't flag any errors is signed_2_4.
Click to expand...
Click to collapse
It makes a difference all right. Let's back up a step and get all of your phone's information straight. What is it's model and OS version? You can find out by running the command "fastboot getvar all" after installing the HTC adb drivers (via HTC Sync Manager) with your phone plugged into your computer.
Under fastboot:
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:*redacted*
Under Download Mode:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: *redacted*
(bootloader) version-main: 3.35.401.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__001
On the back of the phone it reads: 0PJA100... FCC... M9u
FlangeMonkey said:
(bootloader) product: htc_himauhl
(bootloader) version-main: 3.35.401.12
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__001
Click to expand...
Click to collapse
These are the pieces that I find most helpful. From everything provided, I can't see why the M9u shouldn't be able to accept the RUU under normal circumstances.
I notice that in the instructions for the SD card method there is this note in step 6:
"Depending on your current firmware version it may reboot to Android or the Bootloader instead of rebooting to Download Mode. If this happens you just need to manually boot it to Download Mode."
Have you given that a shot? That may solve the problem.
computerslayer said:
These are the pieces that I find most helpful. From everything provided, I can't see why the M9u shouldn't be able to accept the RUU under normal circumstances.
I notice that in the instructions for the SD card method there is this note in step 6:
"Depending on your current firmware version it may reboot to Android or the Bootloader instead of rebooting to Download Mode. If this happens you just need to manually boot it to Download Mode."
Have you given that a shot? That may solve the problem.
Click to expand...
Click to collapse
Yea I did try that as well as a slew of different modes and options, which none of seem to work. I just performed it again for good messure and it bootloops on rebootRUU. I've also found an old backup from the phone itself that was performed back in October with twrp and that has no effect.
I have performed backups using TWRP after restores and examined the images but they are all zeroed! Additionally I do recall seeing write speeds in DD at the 50mb mark, which is way to fast in my opinion and using twrp restore is quick.
It’s very much like nothing is being written, but I have no idea why or if it’s possible to fix.
Could it be possible that something is physically broken, which is preventing writes?
FlangeMonkey said:
Yea I did try that as well as a slew of different modes and options, which none of seem to work. I just performed it again for good messure and it bootloops on rebootRUU. I've also found an old backup from the phone itself that was performed back in October with twrp and that has no effect.
I have performed backups using TWRP after restores and examined the images but they are all zeroed! Additionally I do recall seeing write speeds in DD at the 50mb mark, which is way to fast in my opinion and using twrp restore is quick.
It’s very much like nothing is being written, but I have no idea why or if it’s possible to fix.
Could it be possible that something is physically broken, which is preventing writes?
Click to expand...
Click to collapse
Bummer - it would have been nice if it had been a simple fix there.
It's entirely possible that something is physically broken, but that would probably involve some sort of corrupt memory chip or something. I don't know how you would confirm that though, at least without a professional tearing the phone apart.
From posts I've read elsewhere, it may be possible to flash individual partitions, but that's beyond me. Apart from exploring that option, I'm afraid I'm at a loss.
computerslayer said:
Bummer - it would have been nice if it had been a simple fix there.
It's entirely possible that something is physically broken, but that would probably involve some sort of corrupt memory chip or something. I don't know how you would confirm that though, at least without a professional tearing the phone apart.
From posts I've read elsewhere, it may be possible to flash individual partitions, but that's beyond me. Apart from exploring that option, I'm afraid I'm at a loss.
Click to expand...
Click to collapse
I appreciate your efforts. I have tried flashing partitions via DD and fastboot, but its the same result. Unless anyone can tell me another means to try?
On another note, is it possible to s-OFF in this state (paid or otherwise)?
FlangeMonkey said:
I appreciate your efforts. I have tried flashing partitions via DD and fastboot, but its the same result. Unless anyone can tell me another means to try?
On another note, is it possible to s-OFF in this state (paid or otherwise)?
Click to expand...
Click to collapse
Maybe with a Java Clip. The common method (Sunshine) requires a working ROM
So this Saturday I was using my phone with low battery (it was plugged in), the buttons stopped responding so I restarted it and it has not booted since, I have tried the suggestions laid out in this thread - https://forum.xda-developers.com/htc-10/help/enter-download-mode-t3406529/page3 to no avail.
My phone is S-OFF and unlocked, I have tried flashing an RUU but it says the battery is too low and the phone will not charge, or at least it won't recognise it's charging even when left plugged in for hours.
I have tried flashing each partition individually from one of the firmware .zips on here with the same version it was on, apart from aboot as the thread said to not flash that.
And I have also tried flashing the RUU .zip from a freshly formatted FAT32 SD card but my download mode just shows the silver HTC logo for a while and then reboots into the boot loop. The only mode my phone will stay in is the bootloader, recovery doesn't work either and I have tried flashing TWRP as well as the stock one via fastboot to no avail.
My phone is under warranty so I don't want to disassemble it and it is S-OFF so I don't know if they will claim it's caused by this, although I was going to send it in for a repair as it has a bright spot on the screen anyway but it seems to have killed itself before I had a chance
I do not want to lose the contents of the internal storage either. So I have been searching online for a solution but nothing has worked so far.
I see that a lot of these posts relate to S-ON phones so I was wondering if this could be the reason it didn't work. But I don't want to S-ON my phone as there will be no way back without being able to boot into Android to run Sunshine.
Any help would be greatly appreciated as I'm really stuck.
Thanks.
Edit: GetVar commands get the following output (if this helps):
C:\Android\com>fastboot getvar cid
cid:
finished. total time: 0.010s
C:\Android\com>fastboot getvar mid
mid:
finished. total time: 0.036s
C:\Android\com>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA6xxxxxxxxx
all:
finished. total time: 0.387s
What about downloading the data partition in this state? Can it be done?
Man, this happened to me a month or 2 ago. Seems a lot of people are having similar issues. Haven't found a solution yet. Hopefully soon. Tired of using my old M8
Help, I'm in the same situation since yesterday, I think it's time to change the motherboard
I have the same exact issue. Anyone find a fix?
New motherboard, if it's unlocked and s-off wipe aboot (bricks the phone) and chance a warranty repair. I did, but apparently I had water damage which is bull**** but had it replaced by insurance instead in the end. I've never sent back a phone with an unlock showing so I don't know if they'd warrant it if they see it, but you have nothing to lose as if you moan enough they'll just send it back for free anyway as at least in the UK they can't keep it without consent...
Thanks alot for your response. I was hoping there was an easy fix, oh well (i also have s off and unlocked)... I think im done with HTC. It happened for no reason in my case. Is there a way to extract my files some way given its current condition?
I wasn't able to but maybe someone smarter may know a way. You should be able to get it warranted if you do as I said above as you have nothing to lose at this point
gr8icu said:
I have the same exact issue. Anyone find a fix?
Click to expand...
Click to collapse
Well i was in that bootloop, so i did this to access the htc download mode, plug your cable in pc, then power off phone, plug in the cable then keep presing volume down, he's gonna restart alot, just keep press the volume down till it boot in download mode.
hope you fix this
If that worked it's not the same issue as when the phone ends up in this state you cannot access download mode anymore. It seems to be a firmware/hardware issue specific to the 10.
Like the SD card corruption issue HTC never addressed, my U11 hasn't had a single SD card issue but on my 10 every few months I had to format it.
I'm really disappointed in HTC, I would've bought the U12 but the button issues majorly put me off.
Good luck to anyone with this issue though, I wish mine could've been saved as I lost some data.
same issue with my u ultra.
i also got it s.on bootloader unlocked. cant get to twrp .what should i do now i was on ressrction remix os
Supun_rupasingha said:
i also got it s.on bootloader unlocked. cant get to twrp .what should i do now i was on ressrction remix os
Click to expand...
Click to collapse
If you can ONLY access the bootloader a RUU.exe for your specific firmware could save you.
hopefully you know on what firmware your device is, not the resurrection rom numbers.
You can enter ruu mode from the bootloader and execute a ruu.exe ....... That would be an option
Hello!
A few years ago i got the HTC One M8 through my carrier here in sweden, 3 (tre).
All was good until my phone started crashing as soon as I opened my camera so i sent it to the 3s tech and they changed camera or smthn..
The phone was shipped back to me and it still did the same thing and now it showed error messages (stopped unexpectedly xx) on every app that was running. So I told them and then sent it back to them and they changed a bunch of **** and told me they couldnt recreate the issue.
I got the phone back again and started it up. Would barely start-up at all, stuck on HTC screen, after a while it started and i opened the camera, crashed. So I sent them an angry message of how hard it can be to open the camera and get a crash, since I myself did it so many times and it crashed every time.
Sent it back and they switched battery. Now the phone started to not get pass HTC even worse and needs a few restarts before it boots, it dies after maybe 1-2 hours from no battery and i get constantly spammed with errors from every app saying "stopped unepectedly".
Sent the phone back to them again (phone was sent back and forth for like 6 months) and they said the warranty had ran out. So i said **** you and got a new phone.
Now though.. I want to get my HTC One M8 running again, and im thinking that maybe it will run properly if i dont open the camera etc if i can flash it with a correct RUU since it now gets stuck on HTC and wont boot at all unless i restart it like 15 times.. But maybe its some weird outdated software issue and if i flash it with to start with the correct RUU it will run better again, if that doesnt work, maybe a custom ROM will? ..
I will post the getvar or w/e after my meeting now, but any ideas in the meanwhile?
Thanks beforehand
From Samsung Galaxy S8
Well, we can try to help you to find the right ruu, but we need a getvar all first.
lucyr03 said:
Well, we can try to help you to find the right ruu, but we need a getvar all first.
Click to expand...
Click to collapse
How do i do that? Ive never done **** with phones before and tried googling but nothing anywhere..
Czelious said:
How do i do that? Ive never done **** with phones before and tried googling but nothing anywhere..
Click to expand...
Click to collapse
I highly doubt that is a true statement. You either aren't searching the right terms (fastboot getvar all) or don't understand what you found, and want folks to spoon feed you the information.
You will find plenty of info on how to do this on both the XDA search function (recommended), or using Google.
I understand that working with these devices is new to you. But I would suggest starting with search, read and learn. The information is all here, if you take the time to look.
redpoint73 said:
I highly doubt that is a true statement. You either aren't searching the right terms (fastboot getvar all) or don't understand what you found, and want folks to spoon feed you the information.
You will find plenty of info on how to do this on both the XDA search function (recommended), or using Google.
I understand that working with these devices is new to you. But I would suggest starting with search, read and learn. The information is all here, if you take the time to look.
Click to expand...
Click to collapse
I figured it out, the issue for me is that my phone is wrecked by the Tech team at my carrier, so I look for several issues at the same time and that makes me overlook some info on the sites I find.
Before this I had an issue saying "protocol fault version (31) client (40)" or something and ended up deleting adb from my HTC Manager folder which removed that issue.
lucyr03 said:
Well, we can try to help you to find the right ruu, but we need a getvar all first.
Click to expand...
Click to collapse
Here it is
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.771.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xx
(bootloader) imei: xx
(bootloader) imei2: Not Support
(bootloader) meid: xx
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: H3G__G04
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
From what ive read, this is what i need?
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Post #3
CID H3G__001, H3G__106, H3G__402, H3G__G04
MID 0P6B10000
6.13.771.4
https://mega.nz/#!P4IVSALR!-tbQNWwnQI2U25Rd3wGYO6bYKOiLwKSJQs9FhEDAJHE
This happened though since I can't authorize my PC on the phone
C:\Users\totte\AppData\Local\Android\Sdk\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (20304 KB) OKAY [ 2.130s]
Writing 'recovery' (bootloader) signature checking...
FAILED (remote: signature verify fail)
Finished. Total time: 2.895s
Czelious said:
From what ive read, this is what i need?
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
This is different from an RUU. But I don't think your version has an official RUU, so the method you found is the best you can do. This just restores 2 partitions (system + boot.img) versus RUU which is a complete factory image (40+ partitions).
Czelious said:
This happened though since I can't authorize my PC on the phone
C:\Users\totte\AppData\Local\Android\Sdk\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (20304 KB) OKAY [ 2.130s]
Writing 'recovery' (bootloader) signature checking...
FAILED (remote: signature verify fail)
Finished. Total time: 2.895s
Click to expand...
Click to collapse
You need to unlock the bootloader to flash TWRP. Go to HTCDev. com and follow the process to unlock the bootloader.
redpoint73 said:
This is different from an RUU. But I don't think your version has an official RUU, so the method you found is the best you can do. This just restores 2 partitions (system + boot.img) versus RUU which is a complete factory image (40+ partitions).
You need to unlock the bootloader to flash TWRP. Go to HTCDev. com and follow the process to unlock the bootloader.
Click to expand...
Click to collapse
Ok thnx, ill try (Y)
Been wrestling with the issue to give my PC authority over my phone which seems impossible unless i could get my phone stable :/
If all of this doesnt work out, would a custom ROM be able to fix my issue? My activity bar and back/home buttons aint even working anymore.. since Everything the phone tries to start up "stopped unexpectedly"
Czelious said:
Been wrestling with the issue to give my PC authority over my phone which seems impossible unless i could get my phone stable :/
If all of this doesnt work out, would a custom ROM be able to fix my issue? My activity bar and back/home buttons aint even working anymore.. since Everything the phone tries to start up "stopped unexpectedly"
Click to expand...
Click to collapse
Processes "stopped unexpectedly" will usually be fixed by restoring the stock ROM, or flashing a custom ROM.
But if you have problems with the phone being stable even in bootloader, then you have bigger problems, that flashing a ROM won't fix.
redpoint73 said:
Processes "stopped unexpectedly" will usually be fixed by restoring the stock ROM, or flashing a custom ROM.
But if you have problems with the phone being stable even in bootloader, then you have bigger problems, that flashing a ROM won't fix.
Click to expand...
Click to collapse
Yeah its fixed, only issue now is that my phone keeps restarting on its own randomly, so must be a battery issue :/ Thnx for your help!
Nah, the bootloader was always fine just kept spamming unexpectedly stopped 24/7, and as i said in the original post i left it at the tech with that being the only issue, came back with that issue + random restarts + bad battery time of like 1 hour or so..
Only issue now seems to be the random restarts, havent tested battery time