[Q] How do I fix my m4?

[png666]

Hey guys, you've helped me in the past and I am forever grateful,

I've been googling for a few days now, trying to fix my htc one mini. I need to do a full re-install (roms + firmware+ am I missing something?), I guess.
What I do have:
- Adb acces
- Bootloader menu
- Acces to recovery (CWM recovery)
- No OS
- S-On

What's the problem?
I can't use my phone, and I am unable to install ROMs (unable to mount /XXX/ see below). I am able to install firmware packages and apps. I am able to push files to /data/media/0 but I can't find that folder with either TWRP (2.7) or CM Recovery. I was able to find them before, but they failed installing.

Here's the full story:
I tried to flash CM11 Nightly by H8rift, it failed, and 'accidentaly' I deleted all storage and everything necessay to be able to operate my phone.
Basically all is wiped, and when I try to flash a new ROM I get a lot of different error messages.
Some say .zips can't be opened, android.txt is missing, installation aborted, and so on.
I pushed .zips to my device, but when I try to install these, they just stop and fail.

What I've tried:
Google, a lot (over 8 hours today, 3 yesterday, 12 hours for the past week).
Pushing zips and installing them with recovery. -> failed 9/10 times
Bootload install/flash .zips. -> failed with unknown errors 99
Use TWRP instead of CMW Recovery -> failed too
Back to CWM Recovery -> version 6.0.3.6
Tried installing Codename lungo ROM
Tried Insertcoin ROM
Tried CM11 Rom
Tried Sense 6 Firmware (original, with the original rom) -> I was able to install the ROM, but not the firmware. Message: installation aborted.

Error messages:
Unknown errors (a lot)
Installation aborted (a lot)
Error in /sdcard/0/XXXXX (whatever zip I try, except for firmware)
Installing update... Installation aborted

This is what my screen says:
***TAMPERED***
***UNLOCKED***
M4-UL PVT SHIP S-ON
HBOOT-2.21.0000
RADIO-1.23.40e.00.26
OpenDSP V19.2.0268.0927
OS-2.12.114.2
eMC-boot 1024MB

After all this googling, I just don't know what to do/flash/push anymore. And I'm here to beg you on my bare knees for help. I just need you guys to tell me what to flash/install and in what way to get my phone working again. Or if you need any extra information, please just ask, I'll try to put it up here.

I will not forget to hit the THANK button if you are helpfull, and I will take the effort to check out your projects. I like what you guys are doing here!

 

[shivasrage]

Hey guys, you've helped me in the past and I am forever grateful,

I've been googling for a few days now, trying to fix my htc one mini. I need to do a full re-install (roms + firmware+ am I missing something?), I guess.
What I do have:
- Adb acces
- Bootloader menu
- Acces to recovery (CWM recovery)
- No OS
- S-On

Here's the full story:
I tried to flash CM11 Nightly by H8rift, it failed, and 'accidentaly' I deleted all storage and everything necessay to be able to operate my phone.
Basically all is wiped, and when I try to flash a new ROM I get a lot of different error messages.
Some say .zips can't be opened, android.txt is missing, installation aborted, and so on.
I pushed .zips to my device, but when I try to install these, they just stop and fail.

What I've tried:
Google, a lot (over 8 hours today, 3 yesterday, 12 hours for the past week).
Pushing zips and installing them with recovery. -> failed 9/10 times
Bootload install/flash .zips. -> failed with unknown errors 99
Use TWRP instead of CMW Recovery -> failed too
Back to CWM Recovery -> version 6.0.3.6
Tried installing Codename lungo ROM
Tried Insertcoin ROM
Tried CM11 Rom
Tried Sense 6 Firmware (original, with the original rom) -> I was able to install the ROM, but not the firmware. Message: installation aborted.

Error messages:
Unknown errors (a lot)
Installation aborted (a lot)
Error in /sdcard/0/XXXXX (whatever zip I try, except for firmware)
Installing update... Installation aborted

This is what my screen says:
***TAMPERED***
***UNLOCKED***
M4-UL PVT SHIP S-ON
HBOOT-2.21.0000
RADIO-1.23.40e.00.26
OpenDSP V19.2.0268.0927
OS-2.12.114.2
eMC-boot 1024MB

After all this googling, I just don't know what to do/flash/push anymore. And I'm here to beg you on my bare knees for help. I just need you guys to tell me what to flash/install and in what way to get my phone working again. Or if you need any extra information, please just ask, I'll try to put it up here.

I will not forget to hit the THANK button if you are helpfull, and I will take the effort to check out your projects. I like what you guys are doing here!

Have you tried to format (not only wipe) your sd card with TWRP?
Or flashing a stock recovery then wipe all.....could also be a solution...
After that try to push or sideload ROM..

greets

 

[png666]

Have you tried to format (not only wipe) your sd card with TWRP?
Or flashing a stock recovery then wipe all.....could also be a solution...
After that try to push or sideload ROM..

greets

Thanks Shivasrage,
However, TWRP doesn't open anymore. I'm left with CM Recovery.
"Warning: No File_contexts
Formatting /sdcard...
Done."

After that I tried to sideload Stock Sense 6 ROM (renamed ss2.zip)
Code || -> Response
adb devices -> found device in sideload mode
adb sideload ss2.zip -> * failed to write data 'protocol fault (no status)' *

Alright, without too much code/response info, I managed to find a stock recovery on a German page (thanks again XDA ), and managed to sideload it to my device. Thank god I speak German as well.
I rebooted the bootloader after installing. Now I'm back in CM recovery (is that what should happen?).

Trying to flash/push stock sense right now with CM recovery.
Will be back with update in a jiffy.

UPDATE 1

Rebooted fastboot.

adb fastboot flash zip stocksense6_firmware.zip
sending zip...
Sending
Sending
OKAY
Writing 'zip'... FAILnot allowed
FAILED <remote: not allowed>.

I will try to push it next, to see if it will work installing through CM recovery.

UPDATE 2

I am back to TWRP 2.7.0.6. I can choose: hold volume+screen= CM Recovery, or go to bootloader and pick Recovery for TWRP. Stock recovery hangs and reboots within a few minutes.

Can push files, but the directory is gone. Can't find files..

Tried to sideload CM11 ROM, which does work, however my phone says it's failed. FATALITY! lol.

E: Error executing updater binary in zip 'tmp/sideload.zip'
Updating partition details...
E: Unable to mount '/devlog'
E: Unable to mount '/cache'
E: Unable to mount '/data'
E: Unable to mount '/internal storage'

So, my future is in your hands, dear readers. I am about to throw this $570 piece of hardware against a wall. No, just kidding. I am poor. But I am getting frustrated since I am a noob when it comes to android, and I just can't see what's wrong.
I need someone to tell me: dude, wth, you did **Fill in** wrong, you're so stupid. Here's a link/explanation to your fix.

Ah venting.. Anyhow, thanks for reading.

 

[shivasrage]

This is what my screen says:
***TAMPERED***
***UNLOCKED***
M4-UL PVT SHIP S-ON
HBOOT-2.21.0000
RADIO-1.23.40e.00.26
OpenDSP V19.2.0268.0927
OS-2.12.114.2


I think the best ROM to flash with hboot 2.21.0000 and OS-2.12.114.2 is this:

https://mega.co.nz/#!lZkARZzR!fokyRmgNMy1BoMRcet8UO3j-7u1MhlZxZ-zVTEF3f74

It´s allways best when OS 2.12.xxx.x matches the ROM 2.12.xxx.x so you can be quite sure there are no
issues with partirion layout.
And I think for reanimation of the device it doesn´t matter if is´s booting up on 4.3 or 4.4.2..

 

[spin246]

i am having this same exact issue? did the tips work?

---------- Post added at 08:50 PM ---------- Previous post was at 08:43 PM ----------

what i think would be possible if someone could post a link to download their OS that they have backed up using the TWRP 2.7.0.6 recovery.

 

[png666]

i am having this same exact issue? did the tips work?

---------- Post added at 08:50 PM ---------- Previous post was at 08:43 PM ----------

what i think would be possible if someone could post a link to download their OS that they have backed up using the TWRP 2.7.0.6 recovery.

I'm working on it, downloading all the files and I will try to flash/push and install them. The mega link above your comment is a 'os' of some sort. As far as I know you can backup/restore with every version of TWRP. I don't know the specifics, but I guess it would be handy if there was a 'standard' way of backing up. At least, if I were to write a backup and recovery program (which I can't) I would make newer versions support older backups.

I'm trying Shivasrages' suggestions as wel speak, I will update in about 45 minutes (slow internet). With what I've done, and the results.
:good:

Update 1:
Steps:
Updated twrp to 2.7.1.1 through fastboot flash recovery.
Rebooted to recovery.
Reinstalled drivers (somehow they got lost, I'm using the samsung driver from the SDK)
Pushed ROM file from Shivasrage comment, to /data/media/0
Used TWRP to install.
TWRP says: Succesfull!
This is the most hopefull message I've had in the past few days. Rebooting system...
YES YES YES!!!! I see the welcome message, android is back on, my phone has come back to life thanks to Shivasrage!

I won't be tampering with my phone anytime soon, but this worked! Nice!

 

[shivasrage]

I'm working on it, downloading all the files and I will try to flash/push and install them. The mega link above your comment is a 'os' of some sort. As far as I know you can backup/restore with every version of TWRP. I don't know the specifics, but I guess it would be handy if there was a 'standard' way of backing up. At least, if I were to write a backup and recovery program (which I can't) I would make newer versions support older backups.

I'm trying Shivasrages' suggestions as wel speak, I will update in about 45 minutes (slow internet). With what I've done, and the results.
:good:

Update 1:
Steps:
Updated twrp to 2.7.1.1 through fastboot flash recovery.
Rebooted to recovery.
Reinstalled drivers (somehow they got lost, I'm using the samsung driver from the SDK)
Pushed ROM file from Shivasrage comment, to /data/media/0
Used TWRP to install.
TWRP says: Succesfull!
This is the most hopefull message I've had in the past few days. Rebooting system...
YES YES YES!!!! I see the welcome message, android is back on, my phone has come back to life thanks to Shivasrage!

I won't be tampering with my phone anytime soon, but this worked! Nice!

Next phone back to life....yessss!
Have a nice evening...

 

[spin246]

im still getting devices not found when i try pushing the rom to sd card

 

[shivasrage]

im still getting devices not found when i try pushing the rom to sd card

@spin246

I read some of your posts and I honestly think this is not the way you
will your problems get sorted here on XDA.
Sorry but altough this is a help & troubleshoot section nobody is here to spoonfeed you.

Further it would be good if you list things you have allready tried and to
make a copy of your bootloader output and post it here.

BUT.....for example:

"I have done the adb push romname.zip and still nothing"

or

"Im still getting devices not found when i try pushing the rom to sd card"

is much to less for others to help you...this must be said.

So if you really need help pull a friendly request and write exactly what your problem is
with all specs of ROM, hboot, etc..also the things you have tried yet and where you get stuck.(detailed information)
So you get a much higher chance that somebody is motivated to help you.
You can take post #1 in this tread from png666 as a good example....

peace

 

[png666]

im still getting devices not found when i try pushing the rom to sd card

I had the same problem, it were the drivers that were suddenly gone -> see my

Reinstalled drivers (somehow they got lost, I'm using the samsung driver from the SDK)

. Check your pc-drivers and make sure it's the right one. If not, try another.
If the drivers are malfunctioning, you can't find the device through usb. I had that for about 3 times since this whole circus of reinstalling started.
Also try to make sure you do a restart of cmd.exe every time you're done with something. Just to make sure you are not in the wrong directory or something.

That's all the tips I can give. The driver issue was pretty hard to find for me, but when it was fixed, everything worked as a charm.

Being more specific should help though:
- are your drivers up to date?
- is the usb cable still working?
- is the device's battery full? (I couldn't find it when below 20%)

 

[redwolf056]

Hey png66, thanks for posting this thread and all the work you've done to solve. I ran into the same problem last night trying to install this -

http://forum.xda-developers.com/showthread.php?t=2721870

Now I've got a brick that only loads into bootloader, no OS, etc. I can flash and use custom recoveries but no zip will install (including a CM11 nightly I had previously installed without issue). The failure started when I tried to push the OTA zip onto sdcard and it said there wasn't enough space (firmware install had worked though). I then tried a sideload and it failed, and after trying various things (incl CWM, TWRP, stock recovery) I now can't even use adb (but can use fastboot). Kept getting the same mounting failures you mentioned. I tried using the RUU posted here http://forum.xda-developers.com/showthread.php?t=2546757 without success (error code 155). Formatting and mounting data, cache, system, media didn't work. At this point, TWRP wouldn't even format but CWM would. Wondering if I have some partition issue after turning S-OFF.

I'm guessing the adb failure is related to drivers. Do you have a suggestion for that? I just want to get any OS working so I can push the recovery backup I made to the phone and recover. How did the ROM Shivasrage suggested work? Any advice would be greatly appreciated. Thanks!

Currently-

*** UNLOCKED ***
M4_UL PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.22.0000
RADIO-1.19.40d.00.14
OpenDSP-v13.2.0268.0620
OS-1.32.502.3 (3.10.502.3) [RED]
eMMC-boot 1024MB

I had the same problem, it were the drivers that were suddenly gone -> see my . Check your pc-drivers and make sure it's the right one. If not, try another.
If the drivers are malfunctioning, you can't find the device through usb. I had that for about 3 times since this whole circus of reinstalling started.
Also try to make sure you do a restart of cmd.exe every time you're done with something. Just to make sure you are not in the wrong directory or something.

That's all the tips I can give. The driver issue was pretty hard to find for me, but when it was fixed, everything worked as a charm.

Being more specific should help though:
- are your drivers up to date?
- is the usb cable still working?
- is the device's battery full? (I couldn't find it when below 20%)

 

[shivasrage]

@redwolf056

First of all I recommend you to solve your bootloader issue.
If you want to know whats going on with the red OS inside the (...) read this: (post #8 +#9)

http://forum.xda-developers.com/showthread.php?t=2516681

this is the very first what you should do... after that you can carry on...:good:

greets

 

[redwolf056]

Thanks @shivasrage, after some of the help I've seen you give on this forum I was hoping you'd come to the rescue. Very kind of you to provide the thread and not make me hunt it down . I'll give this a shot tonight and see what happens. I definitely only ran the firmware flash once and think I saw an error message, so hopefully that will be it. If not, hopefully you or someone else can further assist.

@redwolf056

First of all I recommend you to solve your bootloader issue.
If you want to know whats going on with the red OS inside the (...) read this: (post #8 +#9)

http://forum.xda-developers.com/showthread.php?t=2516681

this is the very first what you should do... after that you can carry on...:good:

greets

 

[shivasrage]

Thanks @shivasrage, after some of the help I've seen you give on this forum I was hoping you'd come to the rescue. Very kind of you to provide the thread and not make me hunt it down . I'll give this a shot tonight and see what happens. I definitely only ran the firmware flash once and think I saw an error message, so hopefully that will be it. If not, hopefully you or someone else can further assist.

Ok

If you see this screen if you flash a firmware.zip you are on the right way:



First it´s making a pre update and it write failed...it´s normal ..wait to phone to reboot in "HTC" mode tip your arrow up key and
hit enter..(flash same zip again).
After many screen "bla,bla" it hopfully writes ..SUCCSESS only then reboot with fastboot reboot-bootloader
and if all went fine you could see new firmware in bootloader.

P.S.:
If you have an error don´t reboot you could brick !
Flash other firmware or look for troubleshooting in firmware threads for help. (Only wan´t this have said)


If you want to thank somebody don´t write... hit the button this is what he is made for...

cheers

 

[redwolf056]

Ok, will see how it goes.

And I was reserving the thanks button clicking til after I finished bugging you

Ok

If you see this screen if you flash a firmware.zip you are on the right way:

View attachment 2902698

First it´s making a pre update and it write failed...it´s normal ..wait to phone to reboot in "HTC" mode tip your arrow up key and
hit enter..(flash same zip again).
After many screen "bla,bla" it hopfully writes ..SUCCSESS only then reboot with fastboot reboot-bootloader
and if all went fine you could see new firmware in bootloader.

P.S.:
If you have an error don´t reboot you could brick !
Flash other firmware or look for troubleshooting in firmware threads for help. (Only wan´t this have said)


If you want to thank somebody don´t write... hit the button this is what he is made for...

cheers

 

[spin246]

I had the same problem, it were the drivers that were suddenly gone -> see my . Check your pc-drivers and make sure it's the right one. If not, try another.
If the drivers are malfunctioning, you can't find the device through usb. I had that for about 3 times since this whole circus of reinstalling started.
Also try to make sure you do a restart of cmd.exe every time you're done with something. Just to make sure you are not in the wrong directory or something.

That's all the tips I can give. The driver issue was pretty hard to find for me, but when it was fixed, everything worked as a charm.

Being more specific should help though:
- are your drivers up to date?
- is the usb cable still working?
- is the device's battery full? (I couldn't find it when below 20%)

Where would i find the drivers? can you provide a link

 

[thecos77]

Where would i find the drivers? can you provide a link

Drivers are in the the HTC Sync package on the HTC website.

 

[redwolf056]

Shivasrage, you saved me. Your advice worked, I reflashed the firmware, got adb working again, and then was able to install CM11 (couldn't do the OTA I originally was trying to do, but who cares). Phone... unbricked!

Ok

If you see this screen if you flash a firmware.zip you are on the right way:

View attachment 2902698

First it´s making a pre update and it write failed...it´s normal ..wait to phone to reboot in "HTC" mode tip your arrow up key and
hit enter..(flash same zip again).
After many screen "bla,bla" it hopfully writes ..SUCCSESS only then reboot with fastboot reboot-bootloader
and if all went fine you could see new firmware in bootloader.

P.S.:
If you have an error don´t reboot you could brick !
Flash other firmware or look for troubleshooting in firmware threads for help. (Only wan´t this have said)


If you want to thank somebody don´t write... hit the button this is what he is made for...

cheers

 

[shivasrage]

Shivasrage, you saved me. Your advice worked, I reflashed the firmware, got adb working again, and then was able to install CM11 (couldn't do the OTA I originally was trying to do, but who cares). Phone... unbricked!

Ah a good massage 10 min after I get up.....awsome !:laugh:

Have a nice Day...

P.S.: If you flash the right firmware I´m quit sure
every ROM made for our M4 will work for you

In consequence to many requests in this direction I think about to eventually write
an "resurrection" thread but I think my english isn´t good enough for such a "mission"

 

[redwolf056]

A resurrection thread sounds like a great idea to me. If anything it would be useful because there is a lot of advice already on this forum, but not always so easy to find or figure out which is the right answer. A guide that points to the best threads for a variety of issues would be very useful (especially if it pointed to the best posts in a thread... some can be quite long and full of useless stuff). Or a guide that just says the answer .

Right now I'm facing the problem I had last time I flashed to CM11 - phone gets stuck on WCDMA preferred so I can't get LTE. I had read that happens sometimes when you mess with APN settings so I left them alone and last night it had no issues (even after power down, restart, etc). Today I started the phone in a non-LTE available area and it looks like it's stuck again. Hopefully it will revert when I get home, else I might need to revert to my original backup. Most posts have said a factory reset will get it working again, but that is only a temp fix. More searching ahead of me... sigh.

Ah a good massage 10 min after I get up.....awsome !:laugh:

Have a nice Day...

P.S.: If you flash the right firmware I´m quit sure
every ROM made for our M4 will work for you

In consequence to many requests in this direction I think about to eventually write
an "resurrection" thread but I think my english isn´t good enough for such a "mission"