Database Info

Phone Kinda Bricked

I have HTC Panache. I tried to install Ice Cream Sandwitch on my Phone
http://forum.xda-developers.com/showthread.php?t=1341847&page=17
The phone rebooted using ROM manager. it was extracting. I believe I pressed the power button. Anyways, the phone rebooted and now its just showing the MI logo and a sound that indicates that its a new rom but doesnot goes futher..
I tried to reboot using adb . But when I go into the Clockwork mod recovery, it just shows a hat with a yellow round arrow underneath it. My Clock work mod recovery version is 5.0.2.0

Just discovered
My version is as follows. Is it some thing to be worried ?
<6>[ 6.091674] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB

Your recovery is corrupt. Assuming you have s-off, you can try flashing cwm recovery through bootloader via adb. Search the forum and you will find instructions on how to do that.

chem.manish said:
Your recovery is corrupt. Assuming you have s-off, you can try flashing cwm recovery through bootloader via adb. Search the forum and you will find instructions on how to do that.
Click to expand...
Click to collapse
find the recovery file, rename to "recovery.img" for easy typing, and put it in your adb tools folder.
reboot your phone into bootloader (volume down/power), and connect to computer. when connected to the computer, the phone should automatically switch into fastboot USB mode
type:
Code:
fastboot devices
to make sure device is seen. if it is, proceed. if not, get the drivers.
TYPE THIS EXACTLY!!!
Code:
fastboot flash recovery recovery.img
it should give you a # of bytes sent or something like that
then type
Code:
fastboot reboot recovery
and welcome back to clockworkmod recovery!
if this helped, hit the thanks button.

saranhai said:
find the recovery file, rename to "recovery.img" for easy typing, and put it in your adb tools folder.
reboot your phone into bootloader (volume down/power), and connect to computer. when connected to the computer, the phone should automatically switch into fastboot USB mode
type:
Code:
fastboot devces
to make sure device is seen. if it is, proceed. if not, get the drivers.
TYPE THIS EXACTLY!!!
Code:
fastboot flash recovery recovery.img
it should give you a # of bytes sent or something like that
then type
Code:
fastboot reboot recovery
and welcome back to clockworkmod recovery!
if this helped, hit the thanks button.
Click to expand...
Click to collapse
Correction, first command should be-
fastboot devices

Ok. I did flashboot the recovery. then it installed the rom automatically. Now I am on MyTouch4g T-Mobile ROM. I Installed ROM Manager but following are the errors now
Flash ClockWorkMod :- An Error occured while attempting to run privileged command !
Same happens when I click on Install ROM. In start, it says that No Super User found. Though, I am sure I rooted the phone. Thats why I have a new ROM on my phone
--
When I write Fastboot it says, it is not a recognizable command

ahaseeb said:
Ok. I did flashboot the recovery. then it installed the rom automatically. Now I am on MyTouch4g T-Mobile ROM. I Installed ROM Manager but following are the errors now
Flash ClockWorkMod :- An Error occured while attempting to run privileged command !
Same happens when I click on Install ROM. In start, it says that No Super User found. Though, I am sure I rooted the phone. Thats why I have a new ROM on my phone
--
When I write Fastboot it says, it is not a recognizable command
Click to expand...
Click to collapse
Do you have superuser installed on your phone?
Do you have adb installed on your computer?
Sent from my HTC Glacier Sense 3.5 using xda premium

saranhai said:
Do you have superuser installed on your phone?
Do you have adb installed on your computer?
Sent from my HTC Glacier Sense 3.5 using xda premium
Click to expand...
Click to collapse
He sure has adb if he sees that privileged command error.
I would suggest now you find full pd15img.zip which has rom, recovery and flash thru bootloader. Once you are up and running stock, re-root the device.

He has S-OFF, but he doesn't have engineering bootloader. Which makes him unable to run fastboot commands. That's the standard bad news for those who root and don't flash engineering bootloaders.
But, his phone boots to adb, which is good enough - so the engineering bootloader could be flashed by adb, or at least the recovery could be flashed by adb. The last one can be done using flash_image executable while in adb root shell.

Off topic but what the engineer bootloader what the differences between are regular boot loader ?
Sent from my Tweaked out RCmix3D myTouch 4G via xda premium !

Tez MyTouch said:
Off topic but what the engineer bootloader what the differences between are regular boot loader ?
Sent from my Tweaked out RCmix3D myTouch 4G via xda premium !
Click to expand...
Click to collapse
eng bootloader you can use fastboot with, and you can change more stuff.
correct me if i'm wrong...

chem.manish said:
He sure has adb if he sees that privileged command error.
I would suggest now you find full pd15img.zip which has rom, recovery and flash thru bootloader. Once you are up and running stock, re-root the device.
Click to expand...
Click to collapse
You mean I should follow all the steps of rooting once again ?
Jack_R1 said:
He has S-OFF, but he doesn't have engineering bootloader. Which makes him unable to run fastboot commands. That's the standard bad news for those who root and don't flash engineering bootloaders.
But, his phone boots to adb, which is good enough - so the engineering bootloader could be flashed by adb, or at least the recovery could be flashed by adb. The last one can be done using flash_image executable while in adb root shell.
Click to expand...
Click to collapse
So you mean, I should install bootloader using adb again ?
What was the command flash ... ?
When I type reboot recovery, it goes into the bootloader and a phone appears.. Thats all

When your phone is booting, run "adb shell" and watch. The "#" sign should appear.
If the shell stays and doesn't drop out when the phone is bootlooping (the sign is still there after 2-3 minutes) - you're good to go.
WARNING: YOU'LL BE FLASHING BOOTLOADER. WRONG MOVE - AND YOUR PHONE IS A BRICK.
Since you're already running a rooted OS, "adb shell" should present you with "#" sign.
The thread below has steps to flash engineering bootloader. Don't use those steps, but download the bootloader and check the md5sum (do me a favor and don't ask how to do it, simple googling will spill you 200000000 answers). Put the bootloader into your ADB directory.
http://forum.xda-developers.com/showthread.php?t=858996
Direct link to the file: http://www.megaupload.com/?d=NN5726Z8
md5sum: df4fd77f44993eb05a4732210d2eddc6
Now, to flash engineering bootloader while you're in the ADB root shell, use these steps:
Open Windows' Command prompt in the ADB directory (DO NOT enter ADB shell yet!).
Type (EXACTLY as below):
adb push hboot_dhd.nb0 /data/local/
adb shell
("#" should appear)
cd /data/local/
dd if=hboot_dhd.nb0 of=/dev/block/mmcblk0p18
You should see something like: 2048 bytes in 2048 bytes out 1048576 bytes copied blah blah blah
Now reboot into bootloader, see that you have 0.85.2007 version, enter FASTBOOT mode (select FASTBOOT with volume keys and press power button), and from there you can follow the suggestion above to fastboot flash the recovery, or anything you want.
And on the side note: you won't see any ICS in MIUI that you've attempted flashing. You should have read the thread - it clearly says "all the ICS changes are under the hood, visually it's just a regular MIUI".

I do not see # sign when i type adb shell..
Means I have to root again ?

What do you see? "$"?
In that case, try typing "su" and see if it brings you root.
If it doesn't - you can try to achieve temp root like when downgrading, using fr3vo.
For instructions - section "gain temp root" from the following thread:
http://forum.xda-developers.com/showthread.php?t=1178912
In case it doesn't help you - you'll need to apply PD15IMG in bootloader as suggested to bring you back to stock, and then re-root.

this link returns me error
an error occured while running the exploit <-1> errno 25..
Probbaly because its already exploited may be ?
I am stuck and confused..
Dont know what to do :S

Jack_R1 said:
In case it doesn't help you - you'll need to apply PD15IMG in bootloader as suggested to bring you back to stock, and then re-root.
Click to expand...
Click to collapse
This.
Please google up "mt4g return to stock" or "mt4g apply pd15img", I'm sure there are enough guides to find.

Though applying pd15img.zip is pretty simple, there is even a simpler way for you to return to stock - just find the panache ruu executable in dev section, connect your phone to pc and run that exe.

Is this the file you are referring to ?
http://dl.dropbox.com/u/25823285/RUU...466_signed.exe
I have heard about phones being bricked. So do I need to be extra careful ?

It worked. Great. Now I am on HTC Sense. 2.1 !
Sounds great
Now should i start from zero again ?

[Q] Boot loop after failed boot.img replacement

Edit: solution to the problem in post #4
I have accidentally replaced my boot.img with fastboot - now the phone is stuck in a boot loop/freeze
the bootloader is unlocked
it is S-ON
it is an unlocked (not branded phone)
running twrp 2.6.0.0
both adb and fastboot appear to work
the phone is not rooted (that was where the problem started...)
I have access to hboot and recovery, but that is it​
I have erased everything (cache, system, dalvik, sd) several times and tried a number of suggestions found on other threads describing similar problems.
I can't get access to the SD card from a PC, and fastboot flash or adb push both fail to transfer a stock RUU (JmzM4StockRootedDeOdex-WWE-1.22.401.1.zip) to the phone.
I have replace the kernel (and flashed the appropriate boot.img with it) to get out of the boot loop.
Any suggestion would be greatly appreciated! gettting desperate now...
Thanks, K
----------
the recovery screen reads:
***TAMPERED***
***UNLOCKED***
M4_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.22.40e.00.07
OpenDSP-v15.2.0268.0819
OS-1.40.401.1
eMMC-boot 1024MB

ilchkai said:
I have accidentally replaced my boot.img with fastboot - now the phone is stuck in a boot loop/freeze
the bootloader is unlocked
it is S-ON
it is an unlocked (not branded phone)
running twrp 2.6.0.0
both adb and fastboot appear to work
the phone is not rooted (that was where the problem started...)
I have access to hboot and recovery, but that is it​
I have erased everything (cache, system, dalvik, sd) several times and tried a number of suggestions found on other threads describing similar problems.
I can't get access to the SD card from a PC, and fastboot flash or adb push both fail to transfer a stock RUU (JmzM4StockRootedDeOdex-WWE-1.22.401.1.zip) to the phone.
I have replace the kernel (and flashed the appropriate boot.img with it) to get out of the boot loop.
Any suggestion would be greatly appreciated! gettting desperate now...
Thanks, K
----------
the recovery screen reads:
***TAMPERED***
***UNLOCKED***
M4_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.22.40e.00.07
OpenDSP-v15.2.0268.0819
OS-1.40.401.1
eMMC-boot 1024MB
Click to expand...
Click to collapse
Hi! If you still need help, PM me and we'll get it sorted, no problem.....

nelvinchi said:
Hi! If you still need help, PM me and we'll get it sorted, no problem.....
Click to expand...
Click to collapse
excellent - thanks, pm sent

Here is the solution to the above problem, no guarantees – just thought I share it here if anyone else is in the same predicament… I was walked through this by nelvinchi - many thanks for that !!!!
(n.b. I can't post urls yet as I am a noobie here, so that you will need to find the required files in the forum somewhere - maybe someone can leave links to the appropriate files in a post below)
Required files:
1. ABD (get the smaller version from the forum)
-> download this and extract to a folder called c:\adb\
2. Updated Super SU "UPDATE-SuperSU-v1.86.zip"
3. Rom (Stock2.12.401.1Deodex(tr1gg3r84).zip)
-> SuperSU and Rom, into the same folder as above (c:\adb\)
(4. TeamWinRecoveryProject recovery, here version 2.6.0.0)​
Procedure:
[NB.: I had access to bootloader (unlocked) & recovery (twrp 2.6.0.0); the phone was S-ON]
Open a command prompt from the folder (shift+right click somewhere in the window and choose “open command window here”, or WIN+R and enter cmd and press enter and navigate to the folder where the files and adb are located)
Boot phone to recovery
Go to the mount menu, check system and data [data was not selectable, thus I had to: Go to wipe menu, Format data, Type yes, after that reboot to recovery, and mount menu, check system and data…]
Back to main menu
Plug your phone into computer (mine was plugged in all along, so no worries)
In the cmd prompt (on PC) type: adb devices [phone should be found and indicated by the serial number and the status, in this case it should say recovery after the number – proceed if phone is found]
Type: adb push Stock2.12.401.1Deodex(tr1gg3r84).zip /sdcard/
[there is no indication of progress when pushing, just be patient – it will take a few minutes. And, just in case – if you need to interrupt/cancel the push process it can be done with Ctrl+c]
Type: adb push UPDATE-SuperSU-v1.86.zip /sdcard/
On the phone, in recovery, Go to install
Choose the NEW rom (Stock2.12.401.1Deodex(tr1gg3r84).zip)
Choose add more zips and add the SuperSU zip
Confirm flash
When done, DON'T reboot, go back, reboot menu, reboot recovery
On the PC, open the ROM zip, and extract boot.img to the folder (c:\adb\) [this will need you to have 7zip or Winrar or similar installed on your computer]
Reboot menu and select Reboot bootloader
Select fastboot (fastboot should be indicated by fastboot USB)
On the PC type fastboot flash boot boot.img
Choose bootloader, then recovery
In recovery: Go to wipe, Advanced wipe, Check cache and dalvik, and wipe!
Go to Reboot menu, and Reboot system
Now, don't panic – it will take some time to do its thing… the phone should be fine after that and normal setup process should start.
!!! Massive thanks to nelvinchi, who walked me through this process!!!

Links
A little late, but:
SuperSU: http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip?retrieve_file=1
Stock Flashable zip: https://mega.co.nz/#!8d0jhQTS!N2V5KTty4spxzNOwU-43vzqd3BF_ektVbH_TuHec26c
TWRP: http://forum.xda-developers.com/showthread.php?t=2418938
ADB: http://forum.xda-developers.com/showthread.php?p=42407269 (i think you ment this one, right?)
Yaaay, fixed my mini. Thx for these instructions!
:laugh:

ilchkai said:
Here is the solution to the above problem, no guarantees – just thought I share it here if anyone else is in the same predicament… I was walked through this by nelvinchi - many thanks for that !!!!
(n.b. I can't post urls yet as I am a noobie here, so that you will need to find the required files in the forum somewhere - maybe someone can leave links to the appropriate files in a post below)
Required files:
1. ABD (get the smaller version from the forum)
-> download this and extract to a folder called c:\adb\
2. Updated Super SU "UPDATE-SuperSU-v1.86.zip"
3. Rom (Stock2.12.401.1Deodex(tr1gg3r84).zip)
-> SuperSU and Rom, into the same folder as above (c:\adb\)
(4. TeamWinRecoveryProject recovery, here version 2.6.0.0)​
Procedure:
[NB.: I had access to bootloader (unlocked) & recovery (twrp 2.6.0.0); the phone was S-ON]
Open a command prompt from the folder (shift+right click somewhere in the window and choose “open command window here”, or WIN+R and enter cmd and press enter and navigate to the folder where the files and adb are located)
Boot phone to recovery
Go to the mount menu, check system and data [data was not selectable, thus I had to: Go to wipe menu, Format data, Type yes, after that reboot to recovery, and mount menu, check system and data…]
Back to main menu
Plug your phone into computer (mine was plugged in all along, so no worries)
In the cmd prompt (on PC) type: adb devices [phone should be found and indicated by the serial number and the status, in this case it should say recovery after the number – proceed if phone is found]
Type: adb push Stock2.12.401.1Deodex(tr1gg3r84).zip /sdcard/
[there is no indication of progress when pushing, just be patient – it will take a few minutes. And, just in case – if you need to interrupt/cancel the push process it can be done with Ctrl+c]
Type: adb push UPDATE-SuperSU-v1.86.zip /sdcard/
On the phone, in recovery, Go to install
Choose the NEW rom (Stock2.12.401.1Deodex(tr1gg3r84).zip)
Choose add more zips and add the SuperSU zip
Confirm flash
When done, DON'T reboot, go back, reboot menu, reboot recovery
On the PC, open the ROM zip, and extract boot.img to the folder (c:\adb\) [this will need you to have 7zip or Winrar or similar installed on your computer]
Reboot menu and select Reboot bootloader
Select fastboot (fastboot should be indicated by fastboot USB)
On the PC type fastboot flash boot boot.img
Choose bootloader, then recovery
In recovery: Go to wipe, Advanced wipe, Check cache and dalvik, and wipe!
Go to Reboot menu, and Reboot system
Now, don't panic – it will take some time to do its thing… the phone should be fine after that and normal setup process should start.
!!! Massive thanks to nelvinchi, who walked me through this process!!!
Click to expand...
Click to collapse
I followed these instrutions to a T but im still getting boot loopat the HTC screen
I am Unlocked bootloader
S-Off
cid-CWS__001
hboot 2.19.0000
radio 1.19.40d.00.14
any suggestion?

please help
romy134 said:
I followed these instrutions to a T but im still getting boot loopat the HTC screen
I am Unlocked bootloader
S-Off
cid-CWS__001
hboot 2.19.0000
radio 1.19.40d.00.14
any suggestion?
Click to expand...
Click to collapse
I'm having the same problem.
I've followed those instructions over and over with different roms but TWRP always tells me that there is no OS installed when I do the final reboot. I am stuck at the white HTC screen and can't get any rom to load up. Please help.
This is what my bootloader says:
--TAMPERED--
--UNLOCKED--
M4_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
RADIO-1.25.40G.00.19
OPENDSP-V19.2.0268.0927
OS-3.10.502.3
eMMC-boot 1024mb
I can flash recoveries and boot.img. ADB works to push roms into /sdcard/, can also sideload. I'm suspecting my filesystem/ partition data is all screwed but but can't figure out why Roms won't load.
I got the phone yesterday and it was untouched, stock. I tried to follow this guide (http://forum.xda-developers.com/showthread.php?t=2789272) to get it rooted and install a custom rom. I got stuck at getting S-OFF. rumrunner was giving me the "Fatal: download latest package" error. I also could not get su in the shell to try firewater. At this point I was reading that people had luck getting S-OFF after installing JmzM4StockRootedOdex-WWE-1.22.401.1 custom rom and kernel. I tried to do that but I wasn't sure what I was doing and ended up with no OS and a bootloop at the white HTC screen. I have a bit of Android experience from messing with the HP touchpad tablet but I'm rusty and this phone has me beat right now.
Thanks for your help.

...
try replacing TWRP with an older version (mine was 2.6.0.0) and reset/clear/delete/format everything from there and restart the process outlined above
and apparently S-Off is pointless and very risky on this model, there is no reason to do it - it will just cause problems
good luck and I hope some else who has actual knowledge about this will get back to you

ilchkai said:
try replacing TWRP with an older version (mine was 2.6.0.0) and reset/clear/delete/format everything from there and restart the process outlined above
and apparently S-Off is pointless and very risky on this model, there is no reason to do it - it will just cause problems
good luck and I hope some else who has actual knowledge about this will get back to you
Click to expand...
Click to collapse
Thanks.. I've been using TWRP 2.7.1.0 because I read that I have the newer partion scheme with HBOOT 2.22 but I'm not really sure.
When I try TWRP 2.7.1.1 ADB doesn't work and I get a different /sdcard/ than in 2.7.1.0. Not sure what's going on there either.
The only reason I tried S-off is because I blindly followed that guide on how to get the HTC one mini up to date and that was the 2nd step. I should have skipped it and paid more attention to the custom rom flashing aspect.
I'll try TWRP 2.6.0.0 as I don't have many other options at this point.. I also tried to use CWM recovery but it couldnt flash a rom either.
Thanks for your input.

[Q] Bricked...Sorta....

Hi there, long time reader, possibly posted before but I cant remember my account name so I suppose I am a newbie.
1) Unlocked boot loader fine
2) Installed TWRP fine
3) Rooted fine
4) Installed CM11 and Gaaps
5) Restored all my apps from Titanium
Yaaaay ready to rock or so I thought. Only to be faced with "mobile network not available" so my intention was to flash another CM11 or other CM if it was possible to get it actually working to make phone calls. In my attempts to do this I cleared everything, so no OS. I can get into the bootloader and recovery mode still but that
ADB thing refuses to work. So as of now my PC cannot see the device to copy the rom files onto it.
Am I right in thinking if I get a USB OTG and put a rom on it, I can flash it from there??
I would settle for any custom rom at this stage that functions and doesnt have bloatware.
Failing that, would it be allowed here to ask for an image of a working htc one mini m4 to be uploaded somewhere that I can work with?
I wont be able to do anything until i get the USB OTG. Ive tried everything with ADB.
Your help would be so much appreciated.

hi,..
So first I´m not quite sure if an otg will work but it´s really worth to try it...
But after a (maybee) sucsessful flashing of a ROM via OTG there is no way around to get adb and fastboot to work.
Next I have to say is you should post some information about your phone.
h-boot Version
OS version
CID-Number if you know.
Only with this information sombody here can help you to find the right ROM.zip for flash trough recovery.
(if the firmware and the ROM do not match you are running in to multiple issues)
greets

Thank you
*** tampered ***
*** unlocked ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.24.40e.00.26
OpenDSP-V19.2.0268.0927
OS--
eMMC-BOOT 1024MB

So,.....
It would be very interessting what firmware was on your device..
But as we can see the bootloader shows "OS- " so I suppose with h-boot 2.21.0000 it was 3.10.xxx.x.
I ran in same Problem a few weeks ago.
Recovery write: Can´t mount sd card and can´t mount data
I formated data in TWRP-recovery....(formated not only wipe...deletes everything on device).
As far as I remember after that adb returns to work and I sideloaded a new system.
I recommend you to flash first a stock or stock "near" system then and try to get s-off (to get rid of your problems)
But your first goal is to get a working OS on your device and get adb to work
A little help could be:
In fastboot mode :
"fastboot erase cache"
then reflash TWRP 2.7.1.1 with "fastboot flash recovery recoveryname.img"
If this don´t work out the only way is USB-OTG cable.
greets
edit: honestly I think the CM11 thing is a story after getting device back to life...
an other question ....what do you get if you type in adb when device is in recovery mode: "adb devices"
If needed here you can find a working sense 5.5 rooted stock rom (should work with your frimware) to start with:
http://androidfiles.org/getdownload...Jmz_M4_StockRooted_KK_Odex_WWE_3.10.631.5.zip
could help also:
http://forum.xda-developers.com/htc-one-mini/general/adb-fastboot-device-try-t2800519

shivasrage said:
So,.....
It would be very interessting what firmware was on your device..
But as we can see the bootloader shows "OS- " so I suppose with h-boot 2.21.0000 it was 3.10.xxx.x.
I ran in same Problem a few weeks ago.
Recovery write: Can´t mount sd card and can´t mount data
I formated data in TWRP-recovery....(formated not only wipe...deletes everything on device).
As far as I remember after that adb returns to work and I sideloaded a new system.
I recommend you to flash first a stock or stock "near" system then and try to get s-off (to get rid of your problems)
But your first goal is to get a working OS on your device and get adb to work
A little help could be:
In fastboot mode :
"fastboot erase cache"
then reflash TWRP 2.7.1.1 with "fastboot flash recovery recoveryname.img"
If this don´t work out the only way is USB-OTG cable.
greets
edit: honestly I think the CM11 thing is a story after getting device back to life...
an other question ....what do you get if you type in adb when device is in recovery mode: "adb devices"
If needed here you can find a working sense 5.5 rooted stock rom (should work with your frimware) to start with:
http://androidfiles.org/getdownload...Jmz_M4_StockRooted_KK_Odex_WWE_3.10.631.5.zip
could help also:
http://forum.xda-developers.com/htc-one-mini/general/adb-fastboot-device-try-t2800519
Click to expand...
Click to collapse
Thanks. adb devices will sometimes show the serial number I think, adb push CMupdate.zip I get "cannot read cmupdate.zip"
Fastboot flash recoery recovery.img works.
I have ordered a USB OTG so hopefully by friday I will have it. Im not sure how to show you the firmware? I thought I listed everything needed?

No, its not your fault...
Normaly firmware ist listed in bootloader under OS-3.10.401.3 (for example).
But sometimes after a bad flash when the partitions are messed up or so OS dissapears from bootloader like we can see in your case.
I know from HTC ONE M_7 that there are also some releases of TWRP-recovery that make dissapear OS-Numer from bootloader
but I don´t know if this is similar to the HTC One Mini.
If you get a a serial nuber from adb in recovery mode.. adb should work.....
Do you know how to sideload a ROM via adb and have you allready tried it?
greets

shivasrage said:
So,.....
It would be very interessting what firmware was on your device..
But as we can see the bootloader shows "OS- " so I suppose with h-boot 2.21.0000 it was 3.10.xxx.x.
I ran in same Problem a few weeks ago.
Recovery write: Can´t mount sd card and can´t mount data
I formated data in TWRP-recovery....(formated not only wipe...deletes everything on device).
As far as I remember after that adb returns to work and I sideloaded a new system.
I recommend you to flash first a stock or stock "near" system then and try to get s-off (to get rid of your problems)
But your first goal is to get a working OS on your device and get adb to work
A little help could be:
In fastboot mode :
"fastboot erase cache"
then reflash TWRP 2.7.1.1 with "fastboot flash recovery recoveryname.img"
If this don´t work out the only way is USB-OTG cable.
greets
edit: honestly I think the CM11 thing is a story after getting device back to life...
an other question ....what do you get if you type in adb when device is in recovery mode: "adb devices"
If needed here you can find a working sense 5.5 rooted stock rom (should work with your frimware) to start with:
http://androidfiles.org/getdownload...Jmz_M4_StockRooted_KK_Odex_WWE_3.10.631.5.zip
could help also:
http://forum.xda-developers.com/htc-one-mini/general/adb-fastboot-device-try-t2800519
Click to expand...
Click to collapse
shivasrage said:
No, its not your fault...
Normaly firmware ist listed in bootloader under OS-3.10.401.3 (for example).
But sometimes after a bad flash when the partitions are messed up or so OS dissapears from bootloader like we can see in your case.
I know from HTC ONE M_7 that there are also some releases of TWRP-recovery that make dissapear OS-Numer from bootloader
but I don´t know if this is similar to the HTC One Mini.
If you get a a serial nuber from adb in recovery mode.. adb should work.....
Do you know how to sideload a ROM via adb and have you allready tried it?
greets
Click to expand...
Click to collapse
Yes side load does not work.

I have a serious headache now. I tried so many roms and none of them let me make or recieve calls. The 3g mobile data is working. Would this work if the IMEI was blocked?
I also tried to update the firmware and ran into problems error 155 and error 132. I am really close to giving up.

[Need Fast Help Please!] Softbrick? Wiped everything with TWRP (System,Bin,Data)

Hey guy's only wanted to do a factory reset but I idiot just wiped everything...
So nothing was anymore on it. I downloaded this file:
OTA_M4_UL_K44_SENSE60_MR_HTC_Europe_4.09.401.3-3.10.401
As I have 4.09.401, CID-HTC__102...
So I was very lost and extracted firmware.zip out of it and flashed it over "fastboot oem rebootRUU" - "fastboot flash zip firmware.zip"
It is also now "Relocked" with S-OFF....
I'm stuck, I need my phone the next few days very often...
I dont know what to do anymore if I try to do the same with the OTA zip file it says FAILED (remote: 24 parsing android-info fail)
(When I tried before with TWRP ADB Sideload before I flashed the firmware.zip, it told me "file_getprop failed to stat /system/build.prop"
What can I do now to get my phone working again

Which version of hboot?
Which version of TWRP?
Are you able to connect to your phone via fastboot?
Are you able to connect to your phone via adb (from within TWRP)?

jollywhitefoot said:
Which version of hboot?
Which version of TWRP?
Are you able to connect to your phone via fastboot?
Are you able to connect to your phone via adb (from within TWRP)?
Click to expand...
Click to collapse
- HBOOT 2.22.000
- openrecovery-twrp-2.7.1.0-m4.img (It's the only version where I even can see my devices with "adb devices")
- Yes I am
- Not really I can go with ADB Sideload but using "adb sideload" does not work...
It tells me:
sending: 'rom.zip' 100%
On my phone it's saved under /data/media/sideload.zip but it tells me:
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error executing updater binary in zip '/data/media/sideload.zip'
Click to expand...
Click to collapse

I had a similar issue. Adb only seemed to work on older version of twrp, except in reality, it wasn't working at all. First thing you need to do is get adb working fully to where you can push a Rom to your phone. The problem is likely your Windows drivers and not your phone, so quit trying to flash firmware to fix your phone. For me, I installed a clean copy of Windows xp on an old computer and then set fastboot and Adb up on it. I've also gotten adb and fastboot working using ubuntu live CD. I'll try and find instructions for that method (it's super easy and will run on your CD drive, so you don't need to format hd out install anything).
Once adb works, you can just push any sense6 Rom and then install in twrp and you'll be good to go.
Edit: read posts 17 & 22 here for information on getting ubuntu live CD to work.
http://forum.xda-developers.com/htc-one-mini/help/help-urgent-os-recovery-t2859034/page2

jollywhitefoot said:
I had a similar issue. Adb only seemed to work on older version of twrp, except in reality, it wasn't working at all. First thing you need to do is get adb working fully to where you can push a Rom to your phone. The problem is likely your Windows drivers and not your phone, so quit trying to flash firmware to fix your phone. For me, I installed a clean copy of Windows xp on an old computer and then set fastboot and Adb up on it. I've also gotten adb and fastboot working using ubuntu live CD. I'll try and find instructions for that method (it's super easy and will run on your CD drive, so you don't need to format hd out install anything).
Once adb works, you can just push any sense6 Rom and then install in twrp and you'll be good to go.
Edit: read posts 17 & 22 here for information on getting ubuntu live CD to work.
http://forum.xda-developers.com/htc-one-mini/help/help-urgent-os-recovery-t2859034/page2
Click to expand...
Click to collapse
The problem is that I cant install the ROM.
I've push'ed it do the ROM but as you can see my post above TWRP only gives me error :/

LuvMyHTC21 said:
Hey guy's only wanted to do a factory reset but I idiot just wiped everything...
So nothing was anymore on it. I downloaded this file:
OTA_M4_UL_K44_SENSE60_MR_HTC_Europe_4.09.401.3-3.10.401
As I have 4.09.401, CID-HTC__102...
So I was very lost and extracted firmware.zip out of it and flashed it over "fastboot oem rebootRUU" - "fastboot flash zip firmware.zip"
It is also now "Relocked" with S-OFF....
Click to expand...
Click to collapse
just try to flash not OTA, but ROM
version 2 from here will be Ok

Sweet Jesus, finally after 9 hours (no joke) I got it working, thank you so much !

[Q] HTC One X (ATT) No OS

Long story short, I had an issue with my HTC One X that I received from a friend. It would load up and then immediately restart about 15 seconds after getting to lock screen. I was just stuck in a boot loop.
So I decided to flash a new rom onto the phone, but neither I nor my friend had created a backup so now my OS is wiped.
I can boot into recovery mode, though. I'm not sure what the first screen is called, but it's the one with the skating androids. It tells me:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.45.0622
eMMC-boot
Jun 11 2012,14:36:28
Click to expand...
Click to collapse
When I enter into recovery, it appears that I have TWRP v2.3.1.0.
In here, I cannot install any roms. They appear to fail. Installing says:
Zip Install Complete
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/sdcard/pac.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Error flashing zip '/sdcard/pac.zip'
Updating partition details...
Click to expand...
Click to collapse
Failed
Click to expand...
Click to collapse
I had read somewhere that I need to upgrade my TWRP in order to properly install roms, but at the current moment, running adb devices in a command prompt pointed at my adt bundle folder does not work. It just has a blank list.
Attached is a photo with what I think are the most relevant things I've downloaded/installed so far.
It does look like I can connect my phone to the computer via Mount USB Storage, but sideloader does not work since adb devices is blank.
Any thoughts?

kpxexpress said:
Long story short, I had an issue with my HTC One X that I received from a friend. It would load up and then immediately restart about 15 seconds after getting to lock screen. I was just stuck in a boot loop.
So I decided to flash a new rom onto the phone, but neither I nor my friend had created a backup so now my OS is wiped.
I can boot into recovery mode, though. I'm not sure what the first screen is called, but it's the one with the skating androids. It tells me:
When I enter into recovery, it appears that I have TWRP v2.3.1.0.
In here, I cannot install any roms. They appear to fail. Installing says:
I had read somewhere that I need to upgrade my TWRP in order to properly install roms, but at the current moment, running adb devices in a command prompt pointed at my adt bundle folder does not work. It just has a blank list.
Attached is a photo with what I think are the most relevant things I've downloaded/installed so far.
It does look like I can connect my phone to the computer via Mount USB Storage, but sideloader does not work since adb devices is blank.
Any thoughts?
Click to expand...
Click to collapse
The first screen with the skating Androids is your bootloader, FYI. Adb commands aren't used for flashing a recovery, fastboot commands are used. You do indeed need to update TWRP, the version you currently have installed isn't compatible with any current ROMs. Click the guide link in my signature, there are instructions on anything you need to do there.
Transmitted via Bacon

timmaaa said:
The first screen with the skating Androids is your bootloader, FYI. Adb commands aren't used for flashing a recovery, fastboot commands are used. You do indeed need to update TWRP, the version you currently have installed isn't compatible with any current ROMs. Click the guide link in my signature, there are instructions on anything you need to do there.
Transmitted via Bacon
Click to expand...
Click to collapse
I think I have my phone on Fastboot right now. I have the white screen that has FASTBOOT USB written on it with
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWERDOWN
Click to expand...
Click to collapse
underneath the control options. I've attached a picture below.
I Shift + Right Clicked to open command prompt in the folder with fastboot.exe and my recoveryfilename.img file.
In the command prompt, I enter in the command
Code:
fastboot flash recovery "recoveryfilename.img"
and it just stays on
Code:
< waiting for device >
I still can't figure out how to update my TWRP without an OS.

kpxexpress said:
I think I have my phone on Fastboot right now. I have the white screen that has FASTBOOT USB written on it with
underneath the control options. I've attached a picture below.
I Shift + Right Clicked to open command prompt in the folder with fastboot.exe and my recoveryfilename.img file.
In the command prompt, I enter in the command
Code:
fastboot flash recovery "recoveryfilename.img"
and it just stays on
Code:
< waiting for device >
I still can't figure out how to update my TWRP without an OS.
Click to expand...
Click to collapse
What OS are you running on your PC? Did adb/fastboot work at any point?

timmaaa said:
What OS are you running on your PC? Did adb/fastboot work at any point?
Click to expand...
Click to collapse
I'm running Windows 8.1 Pro. ADB worked once. I was able to get it to detect in recovery. ADB Devices would give me the customary string of numbers followed by "RECOVERY" and then I rebooted the phone for some reason and it stopped working. Oh, during that time I was also able to move stuff to the phone via ADB Sideload, but I would get pretty much the same errors when installing, which I later found out was because my TWRP was too old. I can't seem to get it to connect via ADB/Fastboot anymore. I can, however mount via TWRP.

kpxexpress said:
I'm running Windows 8.1 Pro. ADB worked once. I was able to get it to detect in recovery. ADB Devices would give me the customary string of numbers followed by "RECOVERY" and then I rebooted the phone for some reason and it stopped working. Oh, during that time I was also able to move stuff to the phone via ADB Sideload, but I would get pretty much the same errors when installing, which I later found out was because my TWRP was too old. I can't seem to get it to connect via ADB/Fastboot anymore. I can, however mount via TWRP.
Click to expand...
Click to collapse
There's your problem. Windows 8.1 isn't compatible with fastboot. You'll need to get access to a PC with a lower version of Windows so you can update TWRP.

timmaaa said:
There's your problem. Windows 8.1 isn't compatible with fastboot. You'll need to get access to a PC with a lower version of Windows so you can update TWRP.
Click to expand...
Click to collapse
Oh, really? Will 8 or 7 work?
I used a Windows 7 laptop and was able to update my TWRP to v2.7.0.8!
Seem to still be unable to detect devices via adb devices command.
Ok. Had to update my drivers.
I'm following your instructions on How To Install A ROM with TWRP Recovery, and now my issue is that it is saying
Code:
error flashing zip '/sdcard/pac.zip'
I've included a picture below.

kpxexpress said:
Oh, really? Will 8 or 7 work?
I used a Windows 7 laptop and was able to update my TWRP to v2.7.0.8!
Seem to still be unable to detect devices via adb devices command.
Ok. Had to update my drivers.
I'm following your instructions on How To Install A ROM with TWRP Recovery, and now my issue is that it is saying
Code:
error flashing zip '/sdcard/pac.zip'
I've included a picture below.
Click to expand...
Click to collapse
You're gonna need to get s-off so you can update your firmware. In order to get s-off you'll need to flash the Kickdroid ROM. Once you've flashed Kickdroid you can go to the Rumrunner s-off site and get s-off. Then follow the instructions in my guide thread to update your firmware.

timmaaa said:
You're gonna need to get s-off so you can update your firmware. In order to get s-off you'll need to flash the Kickdroid ROM. Once you've flashed Kickdroid you can go to the Rumrunner s-off site and get s-off. Then follow the instructions in my guide thread to update your firmware.
Click to expand...
Click to collapse
Alright, so I managed to get the Kickdroid ROM working! So right now I at least have a working phone that I can use! Thanks a TON for getting me this far.
Rumrunnner seems to not be working right for me. I'm in ADB recovery and can confirm an ADB connection, but it's still displaying
Code:
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on? Drivers?)
But it's a start. I'll have to make sure I'm following all instructions carefully.