Hello!
I've changed digitizer but now it doesn't react on any touch. I tried to make GoldCard, but I can't enter to menu to change connection to debug mode. There is any other solution to make the GoldCard?
Thx for help.
haller said:
Hello!
I've changed digitizer but now it doesn't react on any touch. I tried to make GoldCard, but I can't enter to menu to change connection to debug mode. There is any other solution to make the GoldCard?
Thx for help.
Click to expand...
Click to collapse
Hi, did you solve the problem? I have the exact same problem.
If you have, please let me know how.
jocke888 said:
Hi, did you solve the problem? I have the exact same problem.
If you have, please let me know how.
Click to expand...
Click to collapse
I have had the same problem with the screen and the debugging, I did however find a kind of workaround for the debugging issue.
I searched for hours and hours for posts on how to enable debugging via ADB command line. The bottom line is that you can't. When I say you I mean "us plebs" can't. I have read the arguments about security and I say cool fair enough. I also noticed that when you run the RUU with the phone connected via USB the RUU activates "USB Debugging" on the handset irrespective of if it was enabled via the handset menu. I can understand this is done for obvious reasons as the RUU is supposed to be an easy way for end users to update their ROM's. It does however beg the question of how a stock ROM can alter the USB debugging switch on the phone via software/usb interface and the rest of the internet claims it is not possible via ADB/command line. Anyone who seems to ask about it is immediately suspected of being a phone thief and the forum responses become a mud slinging match.
So I did some experimenting with the HTC Wildfire S:
Basically I ran the RUU and left it on the Readme page running in the background I could then access the handset via ADB. I don't know ADB well but I was able to see the device listed using adb devices where as before I got nothing. When in Fastboot mode I saw that the handset was also receiving data via the Console on the PC using the fastboot reboot type commands.
It didn't really help me too much as all I wanted to do was update the stock ROM to see if it resolved my touchscreen issue. Unfortunately it didn't. So I'm still stuck with a fully functional handset minus the touchscreen.
I then decided to try and unlock the bootloader so that I could try with a custom ROM. Following the process on HTCdev I got a "Radio" update for the handset. At first I couldn't load it because the base ROM was too old. I found the latest update. It failed with a USB connection error. I found an older version about halfway back between what I had (X.1.33.X) and the new (X.2.16.X) this was (X.1.66.X). It worked but the "Radio" update still needed the latest version. I re-ran the latest RUU and it failed with the same error.
Determined to get it done here is what I did:
1. Re-Ran the (X.2.16.X) Installer
2. At Readme screen I navigated to the standard %TEMP% directory (it helps if u empty this first then you will see the dir the install creates easily)
3. I copied the entire contents to a folder on my desktop
4. Closed the (X.2.16.X) Installer and re-ran the (X.1.66.X) Installer
5. At the Readme screen I navigated back to the %TEMP% directory (it helps if u empty this first then you will see the dir the install creates easily)
6. I pasted and replaced all the files back. Now you get a lot of failures because the Intaller is runnning so I just skipped those files.
7. Went back to the installer running in the background and completed the process.
I used the older installer to flash the newer ROM. I have no idea which files (apart from the rom.zip) were critical but if you copy only the rom.zip it fails on the device when checking the security certificates.
After that I successfully flashed the "Radio" update. The next step in the HTCdev process is to get a device ID via a Flashboot command. I still couldn't do this because the touchscreen still wasn't working after the update. So I Re-Ran the (X.1.66.X) Installer and left it in the background. The phone went into debug mode and I could run the command. I got the info and completed the process with HTCdev. This gave me a unique file to unlock the boot loader.
I then used the same method to get into debug mode and used the HTC Wildfire S All-In-One Toolkit (http://forum.xda-developers.com/showthread.php?t=1809751) to unlock the bootloader with the file HTC sent me.
I now have an HTC Wildfire S with the latest stock ROM, Bootloader unlocked and still no working touchscreen. This took me the better part of 10 hours. When I have the energy to continue I'll try a installing Root and custom ROM.
I apologise in advance for the RUU version number above being severely shortened but they have so many versions of the RUU depending on where you are and who your provider is and such, you will need to do your own research on the specific RUU's you will need and where to get them. The method to get debug I have illustrated should not change if you use a different version of RUU. If you're lucky your stock ROM is also updated and you can skip that part or the RUU you do download works without the tweaking l had to do.
jocke888 said:
Hi, did you solve the problem? I have the exact same problem.
If you have, please let me know how.
Click to expand...
Click to collapse
You have to install a custom recovery (CMW). If you enter recovery mode you can choose mounts and storage, and then mount USB storage. This way you enable usb mass storage. now you are able to get your CID
Related
hey guys,
once every serveal months i check for updates for my rom, my recovery, and some apps.
yesterday i wanted to update tp the latest recovery (1.52)
now, the phone connected, driver was installed correctly (windows 7 32-bit)
i used the adb commands as posted in the recovery topic.
now it updated it, but after a few minutes using and wiping the phone, the usb-connection will not come to live (in any way, not even a "unknown device") and when the phone booted it gave a message: "SD removed, please place sd-card." while it has a 8 gb on there. luckily i backed up all data i needed from the sd before i flashed. so i used recovery to recreate partitions and wipe sd. but nothing works anymore... when i select ANY option in recovery wich needs SD access it immediatly gives errors.
also tried a nother microsd of 1 gb which did also not work...
about the usb-connection, it also does not work in Recovery.
but in the bootloader, it installs without any problems the well known "My HTC" device. using fastboot to boot to recovery image works, but again: no usb connection
please guys... help me... without sd-card i find my phone completely useless. (because of many documents and pictures for my work.)
I've had this problem and I had to send my Hero for repair, but it could be difficult if you have custom software in there, thry to flash original rom. Not sure though if it can be done through fast boot.
Also if you have to send it back, pretend to be an idiot and say it just went wrong. "I didn't do anything" could work.
Use fastboot to revert to a stock ROM (update.zip)
This sounds very similar to this issue on Modaco - http://android.modaco.com/content-page/299174/no-adb-no-sd/
Still ongoing, as I (pulser) am trying to guide the OP through making the goldcard (need to find another android phone to do this) and then we need to try an RUU somehow???
adwinp said:
Use fastboot to revert to a stock ROM (update.zip)
Click to expand...
Click to collapse
ok, and how?
thanks for reply.
i was thinking of letting it be repaired, but as you all say, unlocked spl, recovery image, custom rom. it does not look so good when they disver that.
but i am a stupid guy, so pretending to be stupid should be easy for me
If you are just interested in getting it back to stock for returning under guarantee to HTC, here is what I would suggest.
(No guarantees, as I haven't had to try this, and won't, for obvious reasons)
Get the stock RUU file from the hero that you have. I would recommend the oldest one that is available for you. (eg. a 1.73 one).
DISCONNECT your phone, and run the exe file(Yes, sounds strange, but bear with me).
Wait till the splash screen for the RUU is up, asking you to accept the EULA etc.
Now browse in my computer to your temp directory (C:\Users\Username\AppData\Temp in Vista/7, C:\Documents And Settings\Username\Application Data\temp in XP)
Sort the folders/files by date modified, and the most recently modified (or one of the most recently modified) folder should contain the RUU stuff. Inside a subfolder is a file called rom.zip. Copy this file to the desktop or another safe place. Once file is copied, close the RUU.
Now get your phone plugged in and booted into fastboot. (hold back + power)
Then use the command
Code:
fastboot flashall C:\Users\Username\Desktop\rom.zip
No guarantees, but it should get you back to the stock recovery, system and boot (NOT HBOOT or SPL, the actual boot.img that android uses to boot the kernel)
can i also flash custom rom with fastboot? to test if something is wrong with the rom?
That would depend on what version of SPL/HBOOT you have. If it is security off, then maybe. Otherwise I doubt it. You usually need an original, HTC signed file to flash using that method.
Feel free to give it a go, but I don't think it would work.
Hi Guys,
This is my first post and its only in desperation.
I have a HTC Desire. I upgraded to 2.3.3. After reading how unrevoked doesn't work on this, I created a Goldcard and managed (all on my own) to turn the phone to s /off.
Now Im stuck, many threads explain the process in different ways (as most of them related to pre 2.3.3). So do I load a custom rom onto the Goldcard and flash from there? Also, do I need to install a rollback program first or after?
Really sorry for starting a new thread, but you will see by my profile, Ive been at this for two days .
[Takes cover for flaming session]
im no expert, indeed i have only rooted only a few days ago. I was lucky to have a unlocked phone.
I guess to help the more expert in here is maybe if you detail what now shows on the Bootscreen, eg VOL Down + Power button.
Have you now got a custom Recovery installed, the common one is Clockwork Recovery?
I believe, that Revolutionary.io is able to handle 2.3.3... anyway it what i used to Root, and it installed CWR and from recovery i was able to point it to the ROM zip file and it all installed fine.
Now i didnt need a goldcard so i cant really say if there some additional steps involved first.
u need revolutionary to make s-off, then u can root it flashing the super user zip from the documentation, u don't need the goldcard, it will also install a custom recovery
official revolutionary site: http://revolutionary.io
official revolutionary doc: http://unrevoked.com/rootwiki/doku.php/public/revolutionary
complete guide: http://wiki.rootzwiki.com/index.php/HTC_Desire
don't worry about it, we are all here to help so let me explain some things.
A goldcard is a tool that allows you to use an unbranded RUU on a branded phone, effectively de branding it, as the RUU (Rom Update Utility) ignores the CID (Customer ID) of the device.
To flash different ROM's, you will need to flash something called "recovery", there are many versions, each arguably, or questionably better than the next. In order to flash recovery, you need to download a recovery image.
Download the above file, rename it to "recovery.img" for simplicity, and put it in your C:\
now the flashing process, there are many tools and utilities you can use, but for now, let's just use command prompt as it does not require you to install anything, just as long as you get the commands right. (you'll also need the file I attached [fastboot.exe], just unzip it into your C:\)
Ok, once you've done the steps stated above, turn your phone off. With it off, PRESS AND HOLD the RETURN/BACK key on your phone, and while still holding it, press the POWER key. This will boot you into "fastboot" mode.
Plug your phone in via USB to your PC.
Open command prompt (start menu, accessories, command prompt)
type the following:
Code:
cd\
fastboot flash recovery recovery.img
Congratulations, you have now flashed recovery. This now allows you to flash ROM's.
Put whatever ROM you would like on your SD-CARD, I recommend CyanogenMod (for No Sense) or MIUI (For something completely different) or RCMixS for Sense (sense 2.1) (all comes with preference)
To boot into recovery, boot into bootloader, (while powered off, press and hold VOLUME DOWN, and POWER), use the volume keys to navigate, and the power key to select. Navigate to RECOVERY and hit power.
When you are booted into recovery, before flashing a new rom IT IS VERY IMPORTANT TO BACK UP!!. You can do this in the "backup and restore" menu.
Once you are backed up, go to "mounts and storage" and use "format [partition]" option, to format boot, system, and userdata.
Then, go to "flash zip from sdcard", and find the ROM you have chosen, and wait for it to finish flashing.
Good luck to you
Wow guys, cant thank you enough
I actually had a small amount of brain oozing out of my ears at one point Thanks for the custom info, like I said, the tuts are excellent, but being new, they are a bit irrelevant if you half way through the process. Trust me to upgrade to an 'unrootable' system a week before I decide to root it
I will remove my flame-proofing now
Thanks again
PP
@bortak
Thats only when he have s-off...If i not wrong he have the stock 2.3.3 with no root an s-on
EDIT: nevermind..i didn't read the post properly..
Hi guys
Im getting an error on fastboot :
This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem.
Click to expand...
Click to collapse
Ive tried a different version ,but that came up with the same error. I have android SDK installed in the same directory, is this interfering with it?
Thanks again
PP
palm_pilot said:
Hi guys
Im getting an error on fastboot :
Ive tried a different version ,but that came up with the same error. I have android SDK installed in the same directory, is this interfering with it?
Thanks again
PP
Click to expand...
Click to collapse
Okay, put "fastboot.exe" in c:\android-sdk\platform-tools\
and then before issuing fastboot commands, type:
Code:
cd c:\android-sdk\platform-tools\
this *should* fix it for you
Hi Guys,
This isnt going very well for me
Ive downloaded the .img file tried to flash it. Re-downloaded another copy (in case it was corrupt) , tried to flash that. Changed the file name back to the original (along this command text) to see if it was a recognition issue
On all occasions Im geting :
error: cannot load 'recovery-clockwork-2.5.0.7-bravo.img'
Click to expand...
Click to collapse
Any ideas fellas?
PP
Maybe download 'recovery-clockwork-2.5.0.7-bravo.img' and then select that from unrevoked ?
palm_pilot said:
Hi Guys,
This isnt going very well for me
Ive downloaded the .img file tried to flash it. Re-downloaded another copy (in case it was corrupt) , tried to flash that. Changed the file name back to the original (along this command text) to see if it was a recognition issue
On all occasions Im geting :
Any ideas fellas?
PP
Click to expand...
Click to collapse
Please tell me what code you put before getting that error - or the whole cmd from start to getting that error
BigMrB said:
Please tell me what code you put before getting that error - or the whole cmd from start to getting that error
Click to expand...
Click to collapse
Hi
Im using :
\cd (enter)
Then :
android-sdk\platform-tools\fastboot flash recovery recovery.img
I have revolution installed, can I flash from within this ie. loading the image to the SD and running from within the phone itself?
ATB
PP
cd C:/android-sdk/platform-tools/
fastboot flash recovery recovery.img
(providing you changed the name of your recovery to recovery.img)
So I've got a weird problem...
I've got a Mac, so I had a shop in China root my phone. It's now rooted. The problem is that I can't install ClockworkMod or any ROM. It just won't take. I can't do it either via the ClockWorkMod app or the All-in-One Toolkit.
So I set up HTC One V Toolkit in VirtualBox and the phone won't be seen via USB in the bootloader. It never stops searching for the device at the command line. I tried the same thing on a normal Windows laptop and I've got the same problem. This happens with both the Toolkit and doing "fastboot devices" in the command line.
When I get into the bootloader, it looks for a file called PK76DIAG.zip with a few image files in it and gives me a few fail notices because I don't have it. I found exactly one copy online and the zip file won't unzip on my Mac and the One V doesn't like it either. No luck finding other versions of this file on the English or Chinese internet. My working theory is that perhaps PK76DIAG is some sort of USB driver or an SD-based recovery, which is why it won't connect.
So...
Any ideas on how to either (a) relock the bootloader so I can at least get HTC's OTA updates, or (b) get ClockworkMod and/or ROMs installed?
EDIT: I did go back to the shop and ask them to help install ClockWorkMod and encountered way to large a language barrier. They did pull up a recovery, somehow, that I haven't found. My assumption again being it was somehow based on that PK76DIAG file on their SD card.
The files that fail is normal, it happens to EVERYONE...so sorry i just blew your working theory out of the water..btw PK76DIAG.zip is a rom, it's an alternative way to RUU your phone.
HI all. I am in serious need of help please.
My wifes M9 is stuck on a screen with only a backlight. How this came about is after several failed attempts of updating the system via Wi-Fi. South Africa does not have a RUU available and only over the air updates are available
After about 2 days on the net, searching and reading and trying and failing I have determined the following.
What I have tried
1. Boot to Bootloader and tried recovery. This give me an Error - "Failed to boot to recovery"
2. Tried a Official RUU from HTC, this failed due to CID - Error wrong Customer ID
3. Learned a bit of ADB but this is no use as It seems USB debugging is disabled on the phone
4. Tried Custom ROM's via the SD card but this is blocked as the phone is **Locked** and **S-On**
5. Fastboot sees the phone as I can push reboot commands but because of locked status I can not do much
6. I can not get a unlock token as OEM is locked and this must be unlocked for ADB command to get token to get unlock.bin from HTCDEV
Basically it seems like I am at a dead end as it appears that I need to get into a boot status to enable debugging and enable developer mode from phone settings to be able to work from ADB
So here is the Million dollar question, How can I "wipe" the phone with a SD card boot image/loader or does any one know of a RUU-.exe for South Africa CID_016 that I could flash the phone with or possibly any other methods to get a ROM on it that we can use it again
I repeat, phone goes to blank screen with only backlight after HTC Logo, S-on, USB debugging seems to be disabled and it is in Locked status. I am able to boot in download mode and bootloader and fastboor does see the device. ADB devices does not see the phone, even after trying loads of different drivers, ADB USB ADB Interface etc etc
Please I need help
I'm suffering from the same fate. Except I had rooted it before, then I tried to update it to 5.1 and I relocked my bootloader. Android 5.1 loaded successfully but it got stuck while booting and now I can't unlock my bootloader. I have tried EVERYTHING!
https://www.google.com/url?q=https:...261000&usg=AFQjCNEBlBxkVmymaiJO1eaxKcHsKsE-wg
1.download this zip file
2. Rename the file to 0PJAIMG.zip (zero not O)
03. Copy the file to the root directory of a SD card which is formatted to fat32
04. Put the card into your phone and boot to Download Mode.
05. You will be asked whether you want to flash the file. Confirm with the volume up button.
06. Your phone will reboot at least one time. Depending on your current firmware version it may reboot to Android instead of rebooting to Download Mode. If this happens you just need to shut your phone down and manually boot it to Download Mode.
07. Flashing may take some time.
08. At the end you will be asked to push the power button. You phone will shut down if you do so.
09. Wait some seconds and then turn your phone on, again.
10. First boot may take a while.
11. Congrats! thanks to flippy
YES!!! OP I tried this and it works!!! My phone is finally alive again thanks to flippy's instructions.
Maybe I missed it, but I spent an entire day yesterday trying to find THIS solution. I didn't know it was this particular one, but I would have tried it first if I could have found it somewhere obvious. It really should be stickied as a "How to unscrew what though hast screwed"!
Thank you so much for taking the time to answer this Degerli43! I know virtually every answer possible is available on this forum, but finding it is the trick!
Note to anybody else doing this, be sure to locate the correct image file for your provider and area, as the link above and the one below may not be the correct one for you. I am a T-Mobile US customer and used this one -
https://www.androidfilehost.com/?w=...6ce7fb817fc1524b58f67fe05270f032107d2306abcd4
This worked perfectly after I could not boot or enter TWRP recovery. Anybody who can still access Android Recovery the Downloader should be able to use it to get un-bricked to a clean carrier state if the image file will take.
ksnax said:
Maybe I missed it, but I spent an entire day yesterday trying to find THIS solution. I didn't know it was this particular one, but I would have tried it first if I could have found it somewhere obvious. It really should be stickied as a "How to unscrew what though hast screwed"!
Click to expand...
Click to collapse
Did you ever visit the general section? :silly: There's a sticky thread with stock files and linked instructions for recovering TWRP backups and flashing RUUs. Read the OP, follow it's instructions to my google sheet and you will see where the steps that helped you out are taken from.
Sent from my HTC One S using XDA Labs
Hi,
i just got an HTC One M8s and i think its propably bricked. I don't know whats owner of that phone done here. Its Software status : Modified, Bootloader: Locked, and S-ON.
I can't turn on the phone, i just can go to bootloader option and cant access recovery bc its popably didn't exist anymore.
I was trying to flash RUU for my CID T-MOB009 but htc_fastboot says "data length is too large" and sometimes "remote:signature verify fail", and i was trying to unlock this bootloader with HTCDev, but when i clicked yes it looks like that(means 1st photo) and just reboot to fastboot in bootloader and it's still locked
Is there's a way to unbrick this phone ? I just spend like 4 hours of trying some tips but it doesn't work for it.
Some screens (remove spaces cause i can't post link before 10posts):
s14.postimg .org/b35qjqt6p/DSC_0001_1.jpg
s22.postimg .org/iiihlx2tt/DSC_0002_1.jpg
image.prntscr .com/image/85f19f6602fe4776b993affe62e959c1.png
Please understand my bad english, it's not my primary language
Mikkal said:
Hi,
i just got an HTC One M8s and i think its propably bricked. I don't know whats owner of that phone done here. Its Software status : Modified, Bootloader: Locked, and S-ON.
I can't turn on the phone, i just can go to bootloader option and cant access recovery bc its popably didn't exist anymore.
I was trying to flash RUU for my CID T-MOB009 but htc_fastboot says "data length is too large" and sometimes "remote:signature verify fail", and i was trying to unlock this bootloader with HTCDev, but when i clicked yes it looks like that(means 1st photo) and just reboot to fastboot in bootloader and it's still locked
Is there's a way to unbrick this phone ? I just spend like 4 hours of trying some tips but it doesn't work for it.
Some screens (remove spaces cause i can't post link before 10posts):
s14.postimg .org/b35qjqt6p/DSC_0001_1.jpg
s22.postimg .org/iiihlx2tt/DSC_0002_1.jpg
image.prntscr .com/image/85f19f6602fe4776b993affe62e959c1.png
Please understand my bad english, it's not my primary language
Click to expand...
Click to collapse
Yeah maybe there's a problem with the "Security warning" it shouldn't be there. What you can do is to reflash the RUU. But not with fastboot but from your sdcard.
Probably this is the firmware that you should use. I'm not sure though you can go one directory back and search for another one if that doesn't suit to you.
Now to flash it follow the steps
1) Download it and if you can check the md5sum so as to ensure it has downloaded correctly.
2) Rename it to 0PKVIMG.zip (note the first character is a zero and not a O
3) Take out the sdcard of your phone.
4) Insert it on your pc and format it to Fat32 or exfat.
5) Copy the above file into your sdcard.
6) Power off your phone and insert the sdcard
7) Go into the bootloader mode. It should automatically detect the firmware
8) When it asks you if you want to install choose "Yes"
9) Wait until it is done. It will flash multiple times the system partion. WAIT patiently
10) Hope that fixed it!
PS: When you enter fastboot you probably see some green letters. This means the hboot is searching for the software file i said above. If it finds it's ok. I had problems copying the file with windows though.
root-expert said:
Yeah maybe there's a problem with the "Security warning" it shouldn't be there. What you can do is to reflash the RUU. But not with fastboot but from your sdcard.
Probably is the firmware that you should use. I'm not sure though you can go one directory back and search for another one if that doesn't suit to you.
Now to flash it follow the steps
1) Download it and if you can check the md5sum so as to ensure it has downloaded correctly.
2) Rename it to 0PKVIMG.zip (note the first character is a zero and not a O
3) Take out the sdcard of your phone.
4) Insert it on your pc and format it to Fat32 or exfat.
5) Copy the above file into your sdcard.
6) Power off your phone and insert the sdcard
7) Go into the bootloader mode. It should automatically detect the firmware
8) When it asks you if you want to install choose "Yes"
9) Wait until it is done. It will flash multiple times the system partion. WAIT patiently
10) Hope that fixed it!
PS: When you enter fastboot you probably see some green letters. This means the hboot is searching for the software file i said above. If it finds it's ok. I had problems copying the file with windows though.
Click to expand...
Click to collapse
Yeah thanks for that great advice man! Unfortunately i was trying to copy this on Windows and when i try to Hboot that it just skip process (but stops for sec on a 0PKVIMG.zip) and going back to bootloader. Any advice how to do that properly on windows ? I checked md5 on sd card and its the same as on my computer disk and same as on this site what youre sent to me . Thanks for replies
Mikkal said:
Yeah thanks for that great advice man! Unfortunately i was trying to copy this on Windows and when i try to Hboot that it just skip process (but stops for sec on a 0PKVIMG.zip) and going back to bootloader. Any advice how to do that properly on windows ? I checked md5 on sd card and its the same as on my computer disk and same as on this site what youre sent to me . Thanks for replies
Click to expand...
Click to collapse
I couldn't get it that done on windows. Dunno what's going wrong. Hopefully i had a linux distro installed and i copied the file from there. Maybe you can do that.
If you haven't installed any linux then create a live cd and boot it up.
root-expert said:
I couldn't get it that done on windows. Dunno what's going wrong. Hopefully i had a linux distro installed and i copied the file from there. Maybe you can do that.
If you haven't installed any linux then create a live cd and boot it up.
Click to expand...
Click to collapse
Okay so now its the trick. I have done copied that properly, bc it start to loading when i put sd card. I click yes for update, and its start to flashing. Some of first steps failed so it wasn't look good. It called ROM failed to flashed click POWER to restart, and when i clicked it phone goes off and now its propably close to hardbricked cause i cant turn on bootloader. When i take it to charger there is no battery on screen informating its already charging. Only LED is working when charging and sound on windows when plug it on and off. Any suggestions guys? I'am scared now
Similar situation
Hi,
I appear to be in a similar situation with my M8 that I tried to convert to GPE. Something went wrong and although the ROM booted, I kept getting told my data was corrupt or encrypted... Tried a few reboots, and refreshed but still got the same...
A thread on here suggested formatting one of the partitions from TWRP which just returned an error, since then the phone appears to be 'hard bricked'.
No display, no charging indication, not recognised in ADB, and I can't force boot into recovery or fast boot.
However, I do still get the notification sound when I plug it into my PC...
It appears in the Device Manager as Qualcomm Mass Storage Device, and Windows shows ~20 drives most of which are unformatted, a few of which seem to contain system info...
I was wondering, would it be possible to re-image the Device? Given that the PC recognises the partitions, would anyway know what -should- be on them?
Alternatively, can anyone provide an image of a stock drive, partitions etc which I could apply?
Apologies if this is nonsense, but I'd imagine the reason it can't boot is the Bootloader partition is 'missing' or corrupted.
The same may be true for your device Mikkal.
Thanks in advance,
Mikkal said:
Okay so now its the trick. I have done copied that properly, bc it start to loading when i put sd card. I click yes for update, and its start to flashing. Some of first steps failed so it wasn't look good. It called ROM failed to flashed click POWER to restart, and when i clicked it phone goes off and now its propably close to hardbricked cause i cant turn on bootloader. When i take it to charger there is no battery on screen informating its already charging. Only LED is working when charging and sound on windows when plug it on and off. Any suggestions guys? I'am scared now
Click to expand...
Click to collapse
Exactly the same problem here, I followed the same steps as you, and had same errors as you.. Is there any help for this?
funjai said:
Exactly the same problem here, I followed the same steps as you, and had same errors as you.. Is there any help for this?
Click to expand...
Click to collapse
What is your CID , software version
No idea mate.. I can't turn on the phone so I can't check that..
For those who can't flash a RUU, unlock the bootloader install TWRP recovery, and install a custom ROM. Voila!
LoneWolfO2Se said:
For those who can't flash a RUU, unlock the bootloader install TWRP recovery, and install a custom ROM. Voila!
Click to expand...
Click to collapse
Oh really? You never noticed that there are no custom roms for M8S ?
funjai said:
Oh really? You never noticed that there are no custom roms for M8S ?
Click to expand...
Click to collapse
You sure about that ?
Hi can you paste info from your phone use this command in fasboot
fastboot getvar all
also tell me what software did you try to flash
Regards