Develop Bugs

[Q] [DHD, BICKED BUT STILL BREATHING] I need help

Dear Xda's
I Have An DHD, i tried for te first time to Flash/Root/S-OFF/HBOOT and changing ROM. it went not good
Yesterday i have flashed new rom, as it said on multiple thread in here, but today i dared to change kernel on my phone (i like car tuning, so i tryed tuning my phone
But now, i came to the point of no return(for me). My phone will only show HTC logo on the white backround, thats it, no bootloader, no recovery noting... I ave
read every thread abour Rom/Root/S-Off, Eng S-OFF, i'm sure every thing. I can only turn the phone, by taking the battery off... I have formated my SD card, because of i thought that i ave used CMW partition, before the fix...
And now i will be glad with a stock Rom, Kernel a.s.o...
Please help me, some one... i really don't know what to do...
I so sure that i have read twise before starting to change stuff on my phone.
I had HTC HD2 before, and taht was much easier to flash...

Anis2002 said:
Dear Xda's
I Have An DHD, i tried for te first time to Flash/Root/S-OFF/HBOOT and changing ROM. it went not good
Yesterday i have flashed new rom, as it said on multiple thread in here, but today i dared to change kernel on my phone (i like car tuning, so i tryed tuning my phone
But now, i came to the point of no return(for me). My phone will only show HTC logo on the white backround, thats it, no bootloader, no recovery noting... I ave
read every thread abour Rom/Root/S-Off, Eng S-OFF, i'm sure every thing. I can only turn the phone, by taking the battery off... I have formated my SD card, because of i thought that i ave used CMW partition, before the fix...
And now i will be glad with a stock Rom, Kernel a.s.o...
Please help me, some one... i really don't know what to do...
I so sure that i have read twise before starting to change stuff on my phone.
I had HTC HD2 before, and taht was much easier to flash...
Click to expand...
Click to collapse
download full wipe from xda.. google it "full wipe 1.3 xda" put the zip in ur sdcard.. put the rom(watever rom ur using) in sdcard as well ..
now take battery off ur phone.. back in.. press and hold vol down + power key.. u will go into bootloader.. then click on recovery.. ur phone will boot into CMW recovery > install zip fro sdcard.. 1st do a full wipe.. then flash the rom again.. u will be fine

i'll try now, so happy some one can help, i havent sleept for hours

Else if that does not work ( when i try to boot into recovery that way my phone vibrates, shows a green light and does nothing.. )
connect the phone to your computer and in ADB type: " reboot recovery "

I agree with leather face, I haven't tried this method but I have heard this will solve your problem, when I had the same sort of problem I downloaded the ace stock rom the placed the file on my SD card then took my battery out then reinserted it & powered back on while holding down the volume down button then once in bootloader select fastboot then it will ask to load zip, select yes now it will say done, reboot then you should be back at the beginning again with a working phone start again from scratch but this time do a wipe from recovery and make sure you are using the correct clockwork with the correct rom ie clockwork 2.*.*.* with Cyanogen 6 & clockwork 3.*.*.* with Cyanogen 7 & then you should be just fine mate

now i've tried... it says it cant find recovery file? in CWM loader
it says wrong image...
edit: signature is wrong (or some thing like that) should i rename the .zip file?

or sould i generate a Goldcard for MD98IMG.zip?

Anis2002 said:
or sould i generate a Goldcard for MD98IMG.zip?
Click to expand...
Click to collapse
You'll only need a goldcard if your phone is branded.
With something like a T-Mobile Bootscreen or else.
The Filename should be PD98IMG.zip and it should be in the root folder of your SD.

i think i need to change my system recovery? right? please somewone confirm, if you know... i miss many calls, and dont have any back up phone

Anis2002 said:
i think i need to change my system recovery? right? please somewone confirm, if you know... i miss many calls, and dont have any back up phone
Click to expand...
Click to collapse
does anybody know how to flash CWM, not with ROM manager?
i hope some one will help...

Anis2002 said:
does anybody know how to flash CWM, not with ROM manager?
i hope some one will help...
Click to expand...
Click to collapse
Dude,DON'T PANIC!
Download the attached CWM 2.5.1.3 rar and unrar it.
Now,do you have ADB setup on your pc?If not,search for a guide(Google is your friend),there are many.Supposing you have ADB setup,place the downloaded CWM .img file inside the folder where fastboot is.Open CMD in windows(Type cmd in RUN on your start menu) and there type "cd" and navigate to the folder where fastboot is,like "cd C:/YourPc'sName/android/tools" without the quotes.If it changes folder(it will if you type everything correctly) type without the quotes "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img".The you will be able to boot in recovery through fastboot.
Else,you can use Fastboot commander which is supposed to have a nice GUI and make things easier,but I haven't used it.
Hope I helped!

FIXED,
Fith Fastboot commander (putting my phone in FASTBOOT USB)
Flashing CWM tool, after that I'm da king (Thanks to all, specially mimilover)
Installed Rom, kernel and now nunning 1300Mghz trying it out...

any way to revert back to stock rom?

installed CM7 port 7.2 yesterday, and it seemed to all go fine, but whenever i need to reboot the phone, i get loads of FC's, the calendar doesn't work, my FB and twitter accounts don't get any notifications sync'd, and their accounts are actually totally removed from the sync and accounts section upon every reboot.
overall, considering this is supposed to be the most "stable" of the custom roms, i'd rather just go back to the stock, at least it works, even if i have less space and it eats up battery a bit quicker...at the moment, the phone is pretty useless :s

go to http://forum.xda-developers.com/showthread.php?t=1074445, choose the stock rom for your device and flash it.

it's that simple? awesome! thanks so much
::EDIT::
not working
it keeps bringing up an error when trying to install the rom :s
also tried to install using the rom.zip by choosing install from zip in recovery menu...no joy
::EDIT::
trying a completely fresh install of CM7, wipe everything, format and repartition Sd card, totally start from scratch...as this is the only thing i seem to be able to do at this point....none of the RRU's are installing....wish I hadn't tried this CM7 now :s

My cm7 is completely stable and much more responsive and less bloated than any stock rom
Dunno where your problems are coming from but I don't have any.

I'd recommend doing a full wipe and reflash of CM7. Some bugs appear at first.
Make sure you wipe dalvik, cache and full wipe before flashing.

ok guys, just completely restarted everything from scratch, wiped everything, reformated everything, cleared every possible option.
this time i installed CM7, then the google pack, then DATA2SD (before anything i partitioned the sd card 1GB/256MB)...
seems to be working a bit better...my facebook and twitter accounts are still signed in and show under the sync and accounts settings etc...
i haven't got all those FC's at boot so far....but then i didn't initially yesterday either....so we'll see how it plays out tomorrow :s
however the calendar still doesn't work well, and infact if i open it, goto menu then select calendars, i still get FC on that app :s
maybe i should just get another calendar app?
i think alot of the preview errors might have been due to the fact that i had just manually chose the "move to sd" option for all my apps instead of installing data2sd (which tricks the phone into thinking the 1gb partition on the sd card is the internal memory?)
so fingers crossed it will hold up a bit better now. like i said, i actually can't go back from CM7 now, since none of the RUU's will install. but so far so good, hopefully it will last more than a day this time :s

Gloris said:
installed CM7 port 7.2 yesterday, and it seemed to all go fine, but whenever i need to reboot the phone, i get loads of FC's, the calendar doesn't work, my FB and twitter accounts don't get any notifications sync'd, and their accounts are actually totally removed from the sync and accounts section upon every reboot.
overall, considering this is supposed to be the most "stable" of the custom roms, i'd rather just go back to the stock, at least it works, even if i have less space and it eats up battery a bit quicker...at the moment, the phone is pretty useless :s
Click to expand...
Click to collapse
Give it one more shot but in CWM do this:
Factory reset
Then Mounts/ Format System
Then Advanced/Wipe Dalvik Cache
Then install zip and gapps zip.
See if that clears up any ghosts in the machine. That behaviour shouldn't happen Gloris. I can assure you I've been running the release 1218 since well...1218 and it's been a pleasure.

Same as d33ps1x this is a great rom.
Everything's working fine with no force closing
If your problems continue follow d33ps1x instructions carefully and all should be fine.
Are you using the latest nightly or RC version?

using the nightly version....was all going ok, but now, not only is the calendar still FCing, but i can no longer download ANYTHING from the market...i just get error 492....
I wish i'd never tried this damned CM7, totadl waste of time.
Yes, i've got 1GB of "internal storage", but what's the use if i can't add any more apps???
anyone got any more suggestions for how to go back to stock?
I've tried the RUU, and tried it with goldcard via the .exe installed and via recovery (install from .zip), both with no luck.
I wish i could just go back to stock, these custom roms are a total waste of time

Gloris said:
using the nightly version....was all going ok, but now, not only is the calendar still FCing, but i can no longer download ANYTHING from the market...i just get error 492....
I wish i'd never tried this damned CM7, totadl waste of time.
Yes, i've got 1GB of "internal storage", but what's the use if i can't add any more apps???
anyone got any more suggestions for how to go back to stock?
I've tried the RUU, and tried it with goldcard via the .exe installed and via recovery (install from .zip), both with no luck.
I wish i could just go back to stock, these custom roms are a total waste of time
Click to expand...
Click to collapse
this is the reason why you should have made a nand backup of your rom with cwm BEFORE installing a custom rom.

Gloris said:
using the nightly version....was all going ok, but now, not only is the calendar still FCing, but i can no longer download ANYTHING from the market...i just get error 492....
I wish i'd never tried this damned CM7, totadl waste of time.
Yes, i've got 1GB of "internal storage", but what's the use if i can't add any more apps???
anyone got any more suggestions for how to go back to stock?
I've tried the RUU, and tried it with goldcard via the .exe installed and via recovery (install from .zip), both with no luck.
I wish i could just go back to stock, these custom roms are a total waste of time
Click to expand...
Click to collapse
Have you got the unlocked bootloader if so extract the ruu an flash the boot and system images via fastboot
Sent from my HTC Wildfire S using xda premium

eoghan2t7 said:
Have you got the unlocked bootloader if so extract the ruu an flash the boot and system images via fastboot
Sent from my HTC Wildfire S using xda premium
Click to expand...
Click to collapse
can you elaborate on that and give the exact commands

Gloris said:
can you elaborate on that and give the exact commands
Click to expand...
Click to collapse
Downloaded my PG76IMG.zip version.
Unzip it with 7zzip.
put the boot.img and system.img in the same directory as fastboot
Start your phone with vol down/power after removing and replacing the battery
Choose fastboot
Connect usb cable
issue fastboot commands:
fastboot flash boot boot.img
fastboot flash system system.img

dont forget fastboot -w to wipe the data of the previous rom

d33ps1x said:
Downloaded my PG76IMG.zip version.
Unzip it with 7zzip.
put the boot.img and system.img in the same directory as fastboot
Start your phone with vol down/power after removing and replacing the battery
Choose fastboot
Connect usb cable
issue fastboot commands:
fastboot flash boot boot.img
fastboot flash system system.img
Click to expand...
Click to collapse
I can confirm this working.
if you flash recovery, too from the zip, you can return to stock from cwm.
then apply "fastboot oem lock" and the bootloader will be locked again.
This can be used as a way back to warranty maybe, since then everything is stock again

d33ps1x said:
Downloaded my PG76IMG.zip version.
Unzip it with 7zzip.
put the boot.img and system.img in the same directory as fastboot
Start your phone with vol down/power after removing and replacing the battery
Choose fastboot
Connect usb cable
issue fastboot commands:
fastboot flash boot boot.img
fastboot flash system system.img
Click to expand...
Click to collapse
thanks, do you have the link?

eoghan2t7 said:
dont forget fastboot -w to wipe the data of the previous rom
Click to expand...
Click to collapse
fastboot -w is not allowed.
>fastboot -w
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.004s
Click to expand...
Click to collapse

also, the only RUU i have in rom.zip format is the gingerbread 2.3.5 update....the others are all .exe only...how do i extract those? as i'm not sure the zip i have will work as it's 151Mb (i think the phone only has a genuine 150Mb total internal storage?)

for extracting from ruu exe:
- clear temp folder on windows
- run ruu.exe until first dialog
- go to temp files
- search in the folders for a rom.zip
- extract
- flash

this method is definitely not working
tried flashing the using fastboot, and not my phone won't even boot, it just starts up in recovery mode (it's actually lucky the recovery mode is there or else i'd have a definite brick on my hands).....for those that are wanting to back to stock, DO NOT TRY THIS....NOT WORKING!

System format mistake, Help!!!please

hi, My friend tried to flash with low battery ,then to solve the problem, he entered recovery and Format system...
What can he does to get to life his phone
We we are trying is this..
"If you DON'T have custom rom or Nandroid backup on internal SD card
Originally Posted by torxx View Post
So here a method which always works (many people have issues with flashing RUU's etc. having a bootlop.)
Download a RUU from here, thanks to Football!
Now open the .exe and make sure that it fully started.
Don't click anything, just go to windows icon and search for %temp%.
You will now find some folders, just search through these folders for the ROM.zip.
If you found it, you can copy it to your desktop or somewhere else.
Extract it with WinRar,7-zip or something like that and take the boot_signed.img and system.img.
Now copy the two files into the folder where the fastboot.exe is placed (if you have installed the Android SDK, it should be in platform-tools)
Plug in your One X, go into the bootloader and go into fastboot mode.
Navigate with the cmd in the folder with the fasboot.exe and the two .img's.
Now type in that:
Code:
fastboot flash boot boot_signed.img
After that:
Code:
fastboot flash system system.img
If everything worked, just reboot:
Code:
adb reboot "
Just trying different sort of things,
thanks in advance!!!!
Cheers

If you have the latest version of CWM:
You can just enter recovery again and charge from the recovery screen. RUU's need 30% to initiate but you're better off just leaving it overnight to charge. From there run your RUU, plug in the phone and wait. The RUU will work from fastboot so I don't see why you would need to extract the rom from your %temp% files. You're just adding more risk.
If you do not have the lastest version of CWM (i.e. the one from march to early april):
Search the forum for the charging scheme. I'm not 100% but I'm pretty sure it went something like plugging it into your computer quite a few times over and over to get it to build up a little charge.
Honestly though, your friend should read the guides before flashing. I'm assuming this is his first experience flashing, but for further reference always have at least 75% battery and a nandroid backup.
Good luck

jdunne said:
If you have the latest version of CWM:
You can just enter recovery again and charge from the recovery screen. RUU's need 30% to initiate but you're better off just leaving it overnight to charge. From there run your RUU, plug in the phone and wait. The RUU will work from fastboot so I don't see why you would need to extract the rom from your %temp% files. You're just adding more risk.
If you do not have the lastest version of CWM (i.e. the one from march to early april):
Search the forum for the charging scheme. I'm not 100% but I'm pretty sure it went something like plugging it into your computer quite a few times over and over to get it to build up a little charge.
Honestly though, your friend should read the guides before flashing. I'm assuming this is his first experience flashing, but for further reference always have at least 75% battery and a nandroid backup.
Good luck
Click to expand...
Click to collapse
I know, i m in Grupoandroid helping people, and there is not like here, so people do things without reading, he wanted to Wipe data/factory ...but did format system, i m just trynig to help him only,
Well .. tomorrow we will try to run Ruu, now phone is in recovery, last with charging fix, so tomorrow I wil tell
Thank you very much for ur help
My idea is to pass him my nandroid backup, cause we are same region x.xx.707.xx
But we ll see tomorrow, noe "chraging time"
Thanks agian mate a see you tomorrow!!!!

Ok, good news, sent him my nandroid backup...phone running again...
Using charging fix recovery he could fill bayery 100% over the night, then flash my nandroid, now he has not only his phone working but last firmware too.
Mod can close thread...and very thanks for the Help!!!
Enviado desde mi HTC One X usando Tapatalk 2

[Q] Wildfire S [Marvelc] Stuck on opening update package

Hello all, for the past few days I have been trying to install android 4.0 ICS on my HTC Wildfire S CDMA phone, currently connected to youtube. on one instance I accidently formatted my backup so at this point im prettty scared.
I have already tried full resets, clearing memory, batttery, cache etc. I am stuck using CWM because TWRP touch screen doesnt seem to work at all. All help will be greatly appreciated. thank you.
I have also tried most of what is on other forums such as kernel update, redownloading.
I also find that if while installing, the phone restarts on its own. at first I thought the installation was done but to my dismay, it wasnt....

I'm not sure I can help but I would suggest you try to clarify what you are asking and trying to do. You state that you're doing an install of ICS 4.0 on your WFSc. I don't think any WFS, gsm or cdma got the ICS update unless you mean as Cyanogen Mod 9 or some other ROM? You also said something about being connected to You Tube now...that doesn't make sense.
That being said, if you meant you were trying to install the ICS theme then you might get a quicker more focused response if you posted in this forum:
http://forum.xda-developers.com/showthread.php?t=1504935

Clarification
I got a second wildfire s from my cousin. exact same model and was bought the exact time as my current one and it successfully installed the cynanogen 9 with the only failure being that the touchscreen is inoperable but I will work on that another time. also when I said connected to youtube, I meant I tried to look on youtube for fixes but never found one. anyway the main problem is that my phone stops midway through the "installin updates" to either freeze or restart to a blank operating system "meaning its stuck on the htc logo". I hope this clarifies what I was trying to convey in the previous post and I promise to keep a closer eye for any other messages. I also thank you for answering.

Instead of potentially aggravating you with 20 questions, I'll just briefly run thru the steps, FWIW. I see you mention CWM.
-So, you probably unlocked the booloader at HTC dev and are S-on.
-Installed CWM, so you have the adb files and htc sync on your computer.
-Rooted, although flashing CM will root.
-Battery charged.
-Downloaded the correct CM9 for your WFS, i.e., gsm or cdma, and moved it to your sd card after extracting the boot.img file and putting it into the folder on your computer with the adb, fastboot, etc. files for later.
-Booted into CWM and wiped the cache, dalvik-cache, and data/factory reset.
-Selected the CM9 file on your zip, and started the install.
I'm a little unsure what you are saying happens next, but normally you would:
-after CM9 is flashed go to fastboot in the bootloader or reboot into recovery>fastboot.
-Attach the USB cable from the computer to the phone and with the command prompt at that folder where you have those adb files type:
fastboot flash boot boot.img and press enter
-Then reboot and CM9 should load...unless now both of us have missed something ::yikes!::
For some reason most guides seem to skip that part about extracting the boot.img file and flashing it after the ROM install, which is needed if the phone is still S-on. Typically seen when stuck on the HTC logo after flashing the ROM and rebooting, and you mentioned being stuck on the HTC logo. If the phone is S-off, the boot.img gets flashed from within the ROM during the install.
Hope I found the missing step and that it installs successfully.

romemo two
MiCeltic said:
Instead of potentially aggravating you with 20 questions, I'll just briefly run thru the steps, FWIW. I see you mention CWM.
-So, you probably unlocked the booloader at HTC dev and are S-on.
-Installed CWM, so you have the adb files and htc sync on your computer.
-Rooted, although flashing CM will root.
-Battery charged.
-Downloaded the correct CM9 for your WFS, i.e., gsm or cdma, and moved it to your sd card after extracting the boot.img file and putting it into the folder on your computer with the adb, fastboot, etc. files for later.
-Booted into CWM and wiped the cache, dalvik-cache, and data/factory reset.
-Selected the CM9 file on your zip, and started the install.
I'm a little unsure what you are saying happens next, but normally you would:
-after CM9 is flashed go to fastboot in the bootloader or reboot into recovery>fastboot.
-Attach the USB cable from the computer to the phone and with the command prompt at that folder where you have those adb files type:
fastboot flash boot boot.img and press enter
-Then reboot and CM9 should load...unless now both of us have missed something ::yikes!::
For some reason most guides seem to skip that part about extracting the boot.img file and flashing it after the ROM install, which is needed if the phone is still S-on. Typically seen when stuck on the HTC logo after flashing the ROM and rebooting, and you mentioned being stuck on the HTC logo. If the phone is S-off, the boot.img gets flashed from within the ROM during the install.
Hope I found the missing step and that it installs successfully.
Click to expand...
Click to collapse
Thanks again for the reply. you have given me quite a lot of information and 90% of it was correct and dead on, but where you misunderstand is that while using CWM and flashing ANY Rom onto the phone, it either freezes at "installing updates" or restats if it ever gets to the next step. The confusing part of this is that the other phone which is the exact same model was able to be flashed with all the roms that I tried on my own phone with no problem.
To make things easier. after this I will adress the phones differently:
My phone (Not working Flash) is Marvelc 1
My cousins phone (working flash) is Marvelc 2

This is particularly challenging because you keep emphasizing that you are doing exactly what (you did?) on the other WFS, and I presume they have identical hboots (which they'd have to if you unlocked using htcdev). You also say that you re-downloaded the different files (recovery, CM9) and double checked that their for the MarvelC, and re-did then, re-tried, re-tried, re-tried...and I'm presuming that when you were re-trying that you didn't skip any steps, like the wipes. Oh, and most of all that everything worked on this phone before you started unlocking - flashing the recovery - and rooting. I thought about htc sync and adb, but the fail point is not when the computer is hooked up.
So all that being re-hashed, I'm looking for something concrete, a clue from what you've said or hinted at and right now I'm curious about your SD card. That is most likely not common to both phones and you did say, "on one instance I accidently formatted my backup..." Did you get everything formatted OK with no errors...that SD especially, as Fat32, shouldn't need an ext partition at this time. It could be corrupted and failing at some point when it's unpacking CM9, or whatever. You might re-do formatting that, including doing it on a computer if you have an adapter or a card reader, if not in CWM. It wouldn't hurt to put it in another phone and see if you can read it there and/or on a computer when that other phone is hooked up as a disk drive. Then put a fresh copy of whichever CM9 your flashing on it and try EVERYTHING one more time (back in your phone of course) ::haha:: be sure to leave the battery out for at least 30 sec. after all this and before trying the flash just to be sure any residual static in the phone has dissipated.
If it fails again, leave on and hook up to the computer and run: "adb logcat" from the prompt where you have your adb files and see if it will show you anything. You can exit logcat with the Ctrl + C keys. What do you think?
Oh, and while you're doing all that, who's CM9 are you trying to install. Do you have a link so I can look at it out of curiosity?

It took me awhile to absorb all that but after trying all.those steps,.there was no progress. Furthermore the microsd card I use is for both of my HTC's. And lastly the adb logcat or any adb script for that matter won't work unless the phone is in debug mode with a working o.s.
Thanks for hanging with me and I look forward to your next suggestion.
Sent from my HTC-PG762 using xda app-developers app

I wasn't sure whether there would be some kind of script running in a buffer of the install that might be captured with something like: logcat -b event > /sdcard/logcat.txt
so it was a shot in the dark and I don't know what's left, but perhaps someone else that is reading the post might have some ideas, or experience with this specific issue and jump in with a solution.
I was writing a macro once and couldn't get it to work and spent too much time over 3 days trying to figure it out. When I finally asked someone else to look at it, I was just missing a semi-colon or some one simple thing. You sound pretty knowledgeable, sorry I couldn't be the second set of eyes to come up with the missing thing. If I can think of anything more, I'm subscribed to this thread and I'll surely suggest it.

Thank you for trying, I hope to find an answer soon enough.
Sent from my HTC-PG762 using xda app-developers app

[Q] (Help) HTC One M8 Wiped System files / no recovery / no OS

Hi everyone let me start by saying this: I know what I did was a stupid stupid stupid nOOb mistake, but please understand It did not occur due to lack of reading or negligence to the formation of good understanding prior to rooting and flashing roms etc.
I should also point out that I have read as many other threads and articles on this subject as I can and have resorted to making my own thread ONLY because it is specifically unique to all those I have found elsewhere (including on this site).
Anyway, heres how hellish my last two days have been:
Rooted phone, went perfectly.
Flashed Cyanogenmod Nightly, went perfectly
Decided I wanted go back to stock until stable Cyanogenmod was released as it was too bug ridden for my usage.
This is where it got bad. I cannot remember for the life of me WHY I thought I needed to do this but when I went into Advanced Wipe (TWRP) options i ticked pretty much everything (I am extremely embarrassed and ashamed of this idiotic and reckless action *hangs head in shame*)
Needless to say, at this point I no longer had an OS, so I went about restoring the lot from my backup in TWRP:
Boot Restored fine
DATA restored fine
Cache Restored fine
System FAILED again and again no matter what I tried (literally 20 plus attempts)
At this point I tried flashing back to Cyanogenmod out of desperation but was met only with FAILED and words to the effect of "cannot read .zip file", I found the same message appearing no matter what ROM I tried to flash (I tried a variety of the more popular/stable roms to rule out corrupt data)
At this point I tried sideloading RUU which failed in a similar manner although I cannot remember the exact message)
Then after more pulling my hair out and reading everything I could about other people having similar problems, someone suggested I relock Bootloader before flashing an RUU. This didnt help at all and now I cant unlock Bootloader again, which leaves me unable to access Recovery
I am now at the point of mental breakdown (only slightly exaggerating here) after HOURS of reading and troubleshooting and now a full two days without a phone. I only got the phone 3 days ago so you can imagine how crappy I feel right now.
If any of the resident magicians can help me here I would be grateful beyond words One more thing, In one of the threads I read on another site, someone was suggesting to the OP that since RUU and ROM flashing wernt working, he may have "corrupted NVRAM (internal Storage), If my memory serves me correctly Im sure one of the Advanced Wipe option tick boxes was indeed 'internal storage'
Thanks for any advice. Tommy.

nOOb HTC Guy said:
Hi everyone let me start by saying this: I know what I did was a stupid stupid stupid nOOb mistake, but please understand It did not occur due to lack of reading or negligence to the formation of good understanding prior to rooting and flashing roms etc.
I should also point out that I have read as many other threads and articles on this subject as I can and have resorted to making my own thread ONLY because it is specifically unique to all those I have found elsewhere (including on this site).
Anyway, heres how hellish my last two days have been:
Rooted phone, went perfectly.
Flashed Cyanogenmod Nightly, went perfectly
Decided I wanted go back to stock until stable Cyanogenmod was released as it was too bug ridden for my usage.
This is where it got bad. I cannot remember for the life of me WHY I thought I needed to do this but when I went into Advanced Wipe (TWRP) options i ticked pretty much everything (I am extremely embarrassed and ashamed of this idiotic and reckless action *hangs head in shame*)
Needless to say, at this point I no longer had an OS, so I went about restoring the lot from my backup in TWRP:
Boot Restored fine
DATA restored fine
Cache Restored fine
System FAILED again and again no matter what I tried (literally 20 plus attempts)
At this point I tried flashing back to Cyanogenmod out of desperation but was met only with FAILED and words to the effect of "cannot read .zip file", I found the same message appearing no matter what ROM I tried to flash (I tried a variety of the more popular/stable roms to rule out corrupt data)
At this point I tried sideloading RUU which failed in a similar manner although I cannot remember the exact message)
Then after more pulling my hair out and reading everything I could about other people having similar problems, someone suggested I relock Bootloader before flashing an RUU. This didnt help at all and now I cant unlock Bootloader again, which leaves me unable to access Recovery
I am now at the point of mental breakdown (only slightly exaggerating here) after HOURS of reading and troubleshooting and now a full two days without a phone. I only got the phone 3 days ago so you can imagine how crappy I feel right now.
If any of the resident magicians can help me here I would be grateful beyond words One more thing, In one of the threads I read on another site, someone was suggesting to the OP that since RUU and ROM flashing wernt working, he may have "corrupted NVRAM (internal Storage), If my memory serves me correctly Im sure one of the Advanced Wipe option tick boxes was indeed 'internal storage'
Thanks for any advice. Tommy.
Click to expand...
Click to collapse
are you using the all in one tool kit to do all of this?

skinsfanbdh said:
are you using the all in one tool kit to do all of this?
Click to expand...
Click to collapse
Yes and btw Ive regained access to Recovery which is a step in the right direction, but still have all the same problems ie nothing will flash and cannot restore system etc.

nOOb HTC Guy said:
Yes and btw Ive regained access to Recovery which is a step in the right direction, but still have all the same problems ie nothing will flash and cannot restore system etc.
Click to expand...
Click to collapse
So you managed to unlock your bootloader again as well?

try using the all in one program to sideload a rom

Yer ive managed to unlock bootloader again. I have tried sideloading a variety of roms including the RUU and cyanogenmod. When attempting to sideload cyanogen mod, terminal simply bought up a loud of command lines and their meanings :S RUU however at least came up with the "sideloading" and percentage, gets to 100% and appears to finish, but nothing beyond that (I may be missing something im totally new to all of this) Cheers.

nOOb HTC Guy said:
Yer ive managed to unlock bootloader again. I have tried sideloading a variety of roms including the RUU and cyanogenmod. When attempting to sideload cyanogen mod, terminal simply bought up a loud of command lines and their meanings :S RUU however at least came up with the "sideloading" and percentage, gets to 100% and appears to finish, but nothing beyond that (I may be missing something im totally new to all of this) Cheers.
Click to expand...
Click to collapse
A ruu.exe is executed from the pc and not from the phone. Its useless to sideload it.
Sent from my HTC One_M8 using XDA Premium 4 mobile app

nOOb HTC Guy said:
Yer ive managed to unlock bootloader again. I have tried sideloading a variety of roms including the RUU and cyanogenmod. When attempting to sideload cyanogen mod, terminal simply bought up a loud of command lines and their meanings :S RUU however at least came up with the "sideloading" and percentage, gets to 100% and appears to finish, but nothing beyond that (I may be missing something im totally new to all of this) Cheers.
Click to expand...
Click to collapse
If you got the a list with commands and their meanings then either a) You're not in sideloading mode or b) you didn't type the command properly.
I'm assuming you're still using TWRP, if so, Got to Advanced >>> ADB Sideload >>> Swipe to start sideload ...
Open a command prompt and change directory to adb.exe & fastboot.exe folder / or hold shift and right click in folder where adb.exe/fastboot.exe is and then choose open command window here. Make sure your device is connected to PC and then type adb devices to make sure your device gets picked up, should show you the serial number for device AS WELL as "sideload" next to it, if so then you are hooked up right. If you're "hooked" up right and you can see the device serial number + sideload next to it, type adb sideload name_of_zip.zip wait until fully finished, once done reboot back into recovery and flash rom.
If sideload fails for one or other reason you can also try to push it. Reboot to recovery again, type adb devices to make sure device gets picked up, type adb push name_of_zip.zip /data/media/0/ or adb push name_of_zip.zip /sdcard/ ...I think you could use either, anyways, when finished flash as per usual.

BerndM14 said:
If you got the a list with commands and their meanings then either a) You're not in sideloading mode or b) you didn't type the command properly.
I'm assuming you're still using TWRP, if so, Got to Advanced >>> ADB Sideload >>> Swipe to start sideload ...
Open a command prompt and change directory to adb.exe & fastboot.exe folder / or hold shift and right click in folder where adb.exe/fastboot.exe is and then choose open command window here. Make sure your device is connected to PC and then type adb devices to make sure your device gets picked up, should show you the serial number for device AS WELL as "sideload" next to it, if so then you are hooked up right. If you're "hooked" up right and you can see the device serial number + sideload next to it, type adb sideload name_of_zip.zip wait until fully finished, once done reboot back into recovery and flash rom.
If sideload fails for one or other reason you can also try to push it. Reboot to recovery again, type adb devices to make sure device gets picked up, type adb push name_of_zip.zip /data/media/0/ or adb push name_of_zip.zip /sdcard/ ...I think you could use either, anyways, when finished flash as per usual.
Click to expand...
Click to collapse
Okay so I tried sideloading with your instructions, which came up "failed" but actually had put "sideload.zip" in the directory, but when I tried to flash it I got the same old "error flashing zip"
Next I tried to push file, which comes up with terminal message "error: closed".
It seems that the phone will not flash ANYTHING atall........

OKAY BREAKTHROUGH lol instead of sitting here twiddling my thumbs waiting for replies, I thought I'd spend the time trying to sideload Cyanogenmod, IT WOOOOORRRKKEED and im in a good mood for the first time today thanks to you! My only problem now is that I cannot seem to restore from my backup, it always fails at system :S

nOOb HTC Guy said:
OKAY BREAKTHROUGH lol instead of sitting here twiddling my thumbs waiting for replies, I thought I'd spend the time trying to sideload Cyanogenmod, IT WOOOOORRRKKEED and im in a good mood for the first time today thanks to you! My only problem now is that I cannot seem to restore from my backup, it always fails at system :S
Click to expand...
Click to collapse
I'll be back in around 2 hours or so, off to work now. At least a breakthrough of some sorts, will check on this thread later, hopefully you don't have to wait so long for your device to be fixed :fingers-crossed:
:victory:

if your using a different recovery or a different version of the same recovery your backups may not work unless you flash the recovery you made the backups with

Guys, Im still stuck with cyanogen mod, nothing else will flash or sideload successfully. Also, what I thought was the ruu for my phone was not, can anyone find the correct ruu for mine? Htc one m8 on vodafone uk, cant find an ruu anywhere
Also, cannot obtain s-off since I get "permission denied" message when trying to adb shell and "su" through terminal..... Dont know if I require s-off to flash roms or ruu? thanks.

Ok it doesnt look there is an ruu for mine yet. So maybe I should focus on trying to get my own stock backup to restore, but nothing works! Its always the system bit that fails, boot data cache all restore successfully, any ideas? Would be absolutely amazing if I could just restore to the backup successfully! :good:

success!
YES YES YES YES YES!!!!! NOOOOOBBB POOWWWEERRR!!!!! Sorted it finally!!!!
For anyone else who has had problems restoring from backups, try restoring with files on phone memory and not sd card! Thats what worked for me.
Guys, thankyou all so much for your help I am eternally grateful and more relieved than you can imagine. Finally have a phone again