Sensation info
***UNLOCKED***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
I have 4EXT recovery 1.0.0.6 RC3 Testing build 8
When I try to install Sultan's cm11 dated 20140725 (with full wipe), I get this
set_metadata_recursive: some changes failed.
E:Error in /sdcard/cm11-20140725-Sultan-pyramid.zip. (Status 7)
Installation aborted.
Of course now I have no working rom, only acces to recovery and fastboot usb works ok.
I read through several pyramid threads here describing similar situations, but their error was Status 0.
Any help and advice please?
014916 said:
Sensation info
***UNLOCKED***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
I have 4EXT recovery 1.0.0.6 RC3 Testing build 8
When I try to install Sultan's cm11 dated 20140725 (with full wipe), I get this
set_metadata_recursive: some changes failed.
E:Error in /sdcard/cm11-20140725-Sultan-pyramid.zip. (Status 7)
Installation aborted.
Of course now I have no working rom, only acces to recovery and fastboot usb works ok.
I read through several pyramid threads here describing similar situations, but their error was Status 0.
Any help and advice please?
Click to expand...
Click to collapse
redownload the rom or try a different one
Could you try the latest Slimkat for instance? I am on Slimkat 7.9 and had no issues installing it. Bootloader is the one you have as well.
rzr86 said:
redownload the rom or try a different one
Click to expand...
Click to collapse
I tried to install Albinoman's cm 10.1 20130806 (I had it before on this phone) using different sd card, rom and gapps flashed OK without error messages, but after reboot phone stops at htc start logo, green on white. Recovery and fastboot usb still work though.
I saved recovery log to sdcard, can it help?
wieman01 said:
Could you try the latest Slimkat for instance? I am on Slimkat 7.9 and had no issues installing it. Bootloader is the one you have as well.
Click to expand...
Click to collapse
I'll try that too. Thanks.
014916 said:
I saved recovery log to sdcard, can it help?
Click to expand...
Click to collapse
post it here to see so we can see if there is anything wrong
You have to be a little patient though, the HTC Logo stays in for a little while before you get to see the actual startup screen. So give it a few minutes...
recovery log
rzr86 said:
post it here to see so we can see if there is anything wrong
Click to expand...
Click to collapse
recovery.log attached in zip
OK, this may be a wild guess, but perhaps Albino's ROM is not compatible with 4EXT? The mounting oft system partitions dies not seem to work if I read this correctly.
014916 said:
recovery.log attached in zip
Click to expand...
Click to collapse
wieman01 said:
OK, this may be a wild guess, but perhaps Albino's ROM is not compatible with 4EXT? The mounting oft system partitions dies not seem to work if I read this correctly.
Click to expand...
Click to collapse
from a quick look 4ext can't mount some blocks in your emmc
i think your emmc is corrupted
4ext was your only recovery or did you have other one previously?
rzr86 said:
from a quick look 4ext can't mount some blocks in your emmc
i think your emmc is corrupted
4ext was your only recovery or did you have other one previously?
Click to expand...
Click to collapse
Previous recovery was TWRP 2.6.3? or 2.7.0.0, downloaded from xda, I believe it was shantur's, not sure though. I replaced it because in Sultan's thread about cm11 it was said that only 4ext can install kitkat rom on pyramid. I used it (TWRP) without problems to install Albinoman's cm 10.
By corrupted do you mean bad sectors or errors in partition table? (I don't know much about android partitioning, pardon if I sound like blowing it out).
Is it possible to "repartition" this emmc and assign labels via fastboot usb? Is it like using fdisk or parted? (Sure hope so!)
014916 said:
Previous recovery was TWRP 2.6.3? or 2.7.0.0, downloaded from xda, I believe it was shantur's, not sure though. I replaced it because in Sultan's thread about cm11 it was said that only 4ext can install kitkat rom on pyramid. I used it (TWRP) without problems to install Albinoman's cm 10.
By corrupted do you mean bad sectors or errors in partition table? (I don't know much about android partitioning, pardon if I sound like blowing it out).
Is it possible to "repartition" this emmc and assign labels via fastboot usb? Is it like using fdisk or parted? (Sure hope so!)
Click to expand...
Click to collapse
some sectors i think because 4ext couldn't mount mmcblk0p21, mmcblk0p23, mmcblkp024 if i remember well
did you ever perform any wipe from TWRP?
if yes then probably TWRP caused that
latest versions of TWRP caused a lot of issues to many users
read this thread too
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588
rzr86 said:
some sectors i think because 4ext couldn't mount mmcblk0p21, mmcblk0p23, mmcblkp024 if i remember well
did you ever perform any wipe from TWRP?
if yes then probably TWRP caused that
latest versions of TWRP caused a lot of issues to many users
read this thread too
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588
Click to expand...
Click to collapse
Yes, I did perform full wipe with TWRP at least twice, before installing Abinoman's cm10 and one of the old Vipers. But they both worked...
014916 said:
Yes, I did perform full wipe with TWRP at least twice, before installing Abinoman's cm10 and one of the old Vipers. But they both worked...
Click to expand...
Click to collapse
ok but unfortunately now you have corrupted emmc
from the thread i gave you check the last post
rzr86 said:
ok but unfortunately now you have corrupted emmc
from the thread i gave you check the last post
Click to expand...
Click to collapse
Reading it right now thanks.
That'll be quite a procedure.
rzr86 said:
ok but unfortunately now you have corrupted emmc
from the thread i gave you check the last post
Click to expand...
Click to collapse
Followed rmann's instructions regarding rom install to sd. Pyramid boots, telephony, wifi and sound work. No problems so far.
It's mmmagic.
Thanks!
Hi, guys
I think I have the same problem (eMMC), but I am not sure...
One mounth ago I install new ROM without any problems, and my phone works perfectly all this time. But today I format all from 4EXT recovery, than I try to install new ROM but my installation process aborted with "Status 0" error.
After that I change recovery several times as well as firmware, I lock and unlock my phone twice (i was a bit panicked), so finally the error persists as well as was.
And when I read this thread my heart was beating faster.
So please can anyone see my .log file? And if it is a eMMC problem, can I do a modified ROM for myself? Oh I am sorry, right question is: how I can patch ROM?
alexezeder said:
Hi, guys
I think I have the same problem (eMMC), but I am not sure...
One mounth ago I install new ROM without any problems, and my phone works perfectly all this time. But today I format all from 4EXT recovery, than I try to install new ROM but my installation process aborted with "Status 0" error.
After that I change recovery several times as well as firmware, I lock and unlock my phone twice (i was a bit panicked), so finally the error persists as well as was.
And when I read this thread my heart was beating faster.
So please can anyone see my .log file? And if it is a eMMC problem, can I do a modified ROM for myself? Oh I am sorry, right question is: how I can patch ROM?
Click to expand...
Click to collapse
no you don't have eMMC problem , you just need to update your 4EXT recovery to lattest one 1.0.0.6 RC3
the latest version of 4ext recovery touch
http://www.4shared.com/zip/WnSyLWMaba/4EXT_Recovery_Touch_v1006_RC3_.html
extract the recovery.img and flash it via fastboot command
fastboot flash recovery recovery.img
Mile_zdr said:
no you don't have eMMC problem , you just need to update your 4EXT recovery to lattest one 1.0.0.6 RC3
Click to expand...
Click to collapse
rzr86 said:
the latest version of 4ext recovery touch
link_was_here
extract the recovery.img and flash it via fastboot command
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Thank you, now my phone work well. But why I can't install my previous ROM, which I install a month earlier with the same recovery?
Related
Unlocked
Pyramid PVT Ship S-ON RL
HBOOT-1.27.0000
eMMc-boot
I installed the new viper 1.41 rom and then tried to flash one of the kernals. It said it was all done but then now I'm stuck in a continuous bootloop.
I can boot into recovery and have tried to flash another rom already but it stays in bootloop, also tried flashing different kernal and still doesn't work.
Tried to start from the beginning using cmd etc (adb etc) but cmd can't find a device when using the command adb devices.
What should I do? Please help !!1
mattyon9 said:
Unlocked
Pyramid PVT Ship S-ON RL
HBOOT-1.27.0000
eMMc-boot
I installed the new viper 1.41 rom and then tried to flash one of the kernals. It said it was all done but then now I'm stuck in a continuous bootloop.
I can boot into recovery and have tried to flash another rom already but it stays in bootloop, also tried flashing different kernal and still doesn't work.
Tried to start from the beginning using cmd etc (adb etc) but cmd can't find a device when using the command adb devices.
What should I do? Please help !!1
Click to expand...
Click to collapse
Hi,
Do you have 4EXT recovery installed?
If so ,enable smartflash.
malybru said:
Hi,
Do you have 4EXT recovery installed?
If so ,enable smartflash.
Click to expand...
Click to collapse
"Download 4EXT recovery (1.0.0.5!)" I have this on installed and smartflash is already enabled via recovery.
mattyon9 said:
"Download 4EXT recovery (1.0.0.5!)" I have this on installed and smartflash is already enabled via recovery.
Click to expand...
Click to collapse
Hi,
Unless you have it permanently enabled,you must enable it just before you flash anything.
malybru said:
Hi,
Unless you have it permanently enabled,you must enable it just before you flash anything.
Click to expand...
Click to collapse
Again I've already set smartflash before every flashing of roms. Just this time I'm stuck in a bootloop and can't do nothing about it?
mattyon9 said:
Again I've already set smartflash before every flashing of roms. Just this time I'm stuck in a bootloop and can't do nothing about it?
Click to expand...
Click to collapse
Hi,
Have you got a nandroid you can restore?
malybru said:
Hi,
Have you got a nandroid you can restore?
Click to expand...
Click to collapse
Unfortunately not
Also stuck in the same boat
Hi!
I too am stuck in a bootloop trying to flash CM10.
The problem is I thought I needed CWM to flash the firmware and am now stuck with the CM10 logo when I try and reboot the phone.
Doing more reading 4ext seems to be required to fully wipe the phone rather than CWM
I've found PG58IMG.zip which is recognised when I boot into recovery, but not apparently installed. Perhaps not surprisingly CWM won't install the zip.
Does anyone have any ideas what I can do to the installation?
Thanks
Kevin
mattyon9 said:
Unfortunately not
Click to expand...
Click to collapse
Hi,
You might therefore consider a RUU
Look HERE
---------- Post added at 06:43 PM ---------- Previous post was at 06:39 PM ----------
StockportGerbil said:
Hi!
I too am stuck in a bootloop trying to flash CM10.
The problem is I thought I needed CWM to flash the firmware and am now stuck with the CM10 logo when I try and reboot the phone.
Doing more reading 4ext seems to be required to fully wipe the phone rather than CWM
I've found PG58IMG.zip which is recognised when I boot into recovery, but not apparently installed. Perhaps not surprisingly CWM won't install the zip.
Does anyone have any ideas what I can do to the installation?
Thanks
Kevin
Click to expand...
Click to collapse
Hi,
Firmware is not dependent on a particular recovery.
4 EXT is a better choice ,because it gives you more options.
What PG58IMG.zip were you trying to flash?
S-on/off?
hboot?
radio?
ROM?
Kernel?
etc
etc
etc
More information is required...
Getting past the bootloop
After my plea for help yesterday regarding the bootloop after I had tried to update my HTC Sensation, I eventually found the answer to my problem. Also the response I had yesterday raised some questions which I note at the end
.
Firstly I was trying to update my stock firmware HTC Sensation to CM10; the build I was using was the AOKP / Kang build by bruce2728 dated 16th November as that seemed to be being actively maintained and the functionality I required was reportedly working fine. I read the rather cursory instructions and given I’ve updated several Android tablets before I thought this will be easy. FAIL!
I’ll document elsewhere the process I followed, however the problem I had was when I tried to apply the CM10 image using CWM. It seemed to write successfully but when I came to reboot the phone it was stuck in a boot loop with the cyanogenmod logo stuck on the screen until I pulled the battery out. I couldn’t install 4ext using the play store app as I’d trashed the android installation.
I eventually replace CWM with 4ext by downloading the correct recovery image to my PC (from the third post of http://forum.xda-developers.com/showthread.php?t=1666401, note that the recovery image is different for different phones and possibly operator.)
I then started the phone in bootloader (noting the phone was S-ON), plugged in the USB connection and pressed the power button, so fastboot was selected and then Fastboot usb was displayed on the phone.
From a command prompt on the PC after changing to the directory where I had placed fastboot and adb I typed “fastboot recovery recovery.img” and this replaced CWM with 4ext.
After rebooting the phone and getting back into the bootloader, I selected recovery. This time 4ext started. Before writing the new Android image I wiped user data and (I think it was in tools once you scrolled to the bottom) selected “enable 4ext superflash” before flashing the ROM and Google Apps and then successfully rebooting the phone. For reference the phone took less than 5 minutes to start up.
I now think my problem was trying to flash the ROM with S-ON and not using 4-ext superflash. Oh well
Following on from the response from malybru (Thanks)
Does writing a new rom change the radio? I’d understood it remained the same unless you made special efforts to change it and you were likely to wipe out the phone?
Thanks again
Kevin
maybe i am wrong but radio can be changed only when you are flashing different firmware and to do that you have to be S-OFF
StockportGerbil said:
After my plea for help yesterday regarding the bootloop after I had tried to update my HTC Sensation, I eventually found the answer to my problem. Also the response I had yesterday raised some questions which I note at the end
.
Firstly I was trying to update my stock firmware HTC Sensation to CM10; the build I was using was the AOKP / Kang build by bruce2728 dated 16th November as that seemed to be being actively maintained and the functionality I required was reportedly working fine. I read the rather cursory instructions and given I’ve updated several Android tablets before I thought this will be easy. FAIL!
I’ll document elsewhere the process I followed, however the problem I had was when I tried to apply the CM10 image using CWM. It seemed to write successfully but when I came to reboot the phone it was stuck in a boot loop with the cyanogenmod logo stuck on the screen until I pulled the battery out. I couldn’t install 4ext using the play store app as I’d trashed the android installation.
I eventually replace CWM with 4ext by downloading the correct recovery image to my PC (from the third post of http://forum.xda-developers.com/showthread.php?t=1666401, note that the recovery image is different for different phones and possibly operator.)
I then started the phone in bootloader (noting the phone was S-ON), plugged in the USB connection and pressed the power button, so fastboot was selected and then Fastboot usb was displayed on the phone.
From a command prompt on the PC after changing to the directory where I had placed fastboot and adb I typed “fastboot recovery recovery.img” and this replaced CWM with 4ext.
After rebooting the phone and getting back into the bootloader, I selected recovery. This time 4ext started. Before writing the new Android image I wiped user data and (I think it was in tools once you scrolled to the bottom) selected “enable 4ext superflash” before flashing the ROM and Google Apps and then successfully rebooting the phone. For reference the phone took less than 5 minutes to start up.
I now think my problem was trying to flash the ROM with S-ON and not using 4-ext superflash. Oh well
Following on from the response from malybru (Thanks)
Does writing a new rom change the radio? I’d understood it remained the same unless you made special efforts to change it and you were likely to wipe out the phone?
Thanks again
Kevin
Click to expand...
Click to collapse
Hi,
Flashing a ROM does NOT change the radio.
In fact,you cannot change the radio or firmware if you are s-on.
"Smartflash" is what I would have suggested if you had 4 EXT recovery and s-on.
It is all well documented HERE
malybru said:
Hi,
Flashing a ROM does NOT change the radio.
In fact,you cannot change the radio or firmware if you are s-on.
"Smartflash" is what I would have suggested if you had 4 EXT recovery and s-on.
It is all well documented HERE
Click to expand...
Click to collapse
Hi!
I think I read everything except that guide yesterday - thanks it is interesting.
Regards
Kevin
Hi guys,
My cousin from America came to visit yesterday, and he asked me if I could install CyanogenMod on his phone. It's an HTC One X from AT&T. So I set his CID to 111111, unlocked his bootloader with HTCDev, flashed TWRP 2.5.0.0 and then I rooted his phone. Afterwords, I did a backup via TWRP Recovery.
I looked for the CyanogenMod for this device and the stable build was cm-10.0.0-evita. I transfered it to the phone's TWRP folder, booted recovery and tried to install it but failed, the error message was: assert failed: getprop("ro.bootloader") == 2.1....and some more numbers and stuff
Stupid as I was, I thought "It's probably the stock ROM interfering with the installation, and I can always restore my backup" so I erased a couple of things from the phone: Dalvik Cache, Cache, Data, sdcard and System. Left Android Secure alone because I didn't know what it was or what it does.
Then it hit me. I formatted Data, my backup was gone! And so was the ROM I wanted to flash!
What do I do now? I don't have any operating system installed and can't boot into android! All I can do is boot into Recovery and Bootloader.
Here's what bootloader says:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.09.000
RADIO-0.16.32.09.01_3
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 2 2012, 21:08:24
My recovery is: TWRP 2.5.0.0
Any ideas?
It's ok, no need to panic
Download ROM to PC. Make doubly sure it's for this device, I think the error you experienced the first time was because you tried to flash an International One X ROM. Only get your ROMs from here, or here.
Boot into recovery.
Connect the phone to the PC.
Mount your sd/internal storage from your TWRP menu.
Copy ROM from PC to phone.
Wipe cache/dalvik/factory reset/system.
Flash ROM.
Reboot.
Enjoy.
Sent from my Evita
Alright, no problem, the error you got in TWRP was because you needed to have HBOOT 2.14 or above to install CM10.1 because of the kernel it uses. Never wipe /sdcard because it won't do you any good. Now, what you're gonna wanna do is, mount USB Storage in TWRP (under mount menu) when it's connected to your PC, download a ROM (not CM10.1 for now, we'll get to that soon enough) and make sure it's for this phone, drag and drop it to your phone from the PC, and flash it. Once you do that, if you still want to get CM10.1, we can help you with that too.
Edit: @timmaaa he won't be able to use CM10.1 because he's on hboot 1.09.
Your main problem, is that you are deleting/formatting things without having any clue what they are. This is an invitation for disaster. Your backups are deleted because your deleted the SD card, not because you deleted /data or /system.
/system = current ROM
/data = user data (phone storage), formatting is the same as factory reset
The only things that really need to be deleted when flashing a new ROM is /data (factory reset) and cache. Formatting /system is not necessary, as flashing a new ROM does this by default before installing the new ROM.
Connect the phone to your computer, mount USB in TWRP, and move the new ROM zip to the SD card, and flash from TWRP.
Its also a good idea to copy a backup to your computer or Dropbox. But that is probably not something that will help you at the moment. Just a bit of advice moving forward.
While in twrp, plug into your pc then go to mounts > mount usb storage. Then put whatever Rom on there. Make sure you get the right Rom for this device.
EDIT:
Oh wow just realized I was beat by like 3 people before I hit post lol
Sent from my HTC One X using xda premium
dragancla said:
Hi guys,
My cousin from America came to visit yesterday, and he asked me if I could install CyanogenMod on his phone. It's an HTC One X from AT&T. So I set his CID to 111111, unlocked his bootloader with HTCDev, flashed TWRP 2.5.0.0 and then I rooted his phone. Afterwords, I did a backup via TWRP Recovery.
I looked for the CyanogenMod for this device and the stable build was cm-10.0.0-evita. I transfered it to the phone's TWRP folder, booted recovery and tried to install it but failed, the error message was: assert failed: getprop("ro.bootloader") == 2.1....and some more numbers and stuff
Stupid as I was, I thought "It's probably the stock ROM interfering with the installation, and I can always restore my backup" so I erased a couple of things from the phone: Dalvik Cache, Cache, Data, sdcard and System. Left Android Secure alone because I didn't know what it was or what it does.
Then it hit me. I formatted Data, my backup was gone! And so was the ROM I wanted to flash!
What do I do now? I don't have any operating system installed and can't boot into android! All I can do is boot into Recovery and Bootloader.
Here's what bootloader says:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.09.000
RADIO-0.16.32.09.01_3
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 2 2012, 21:08:24
My recovery is: TWRP 2.5.0.0
Any ideas?
Click to expand...
Click to collapse
First off flash twrp 2.3.3.1 or 2.6 all others have issues.
Then mount usb storage from twrp
Copy Rom to sd card
Wipe cache and dalvik
If you're not s-off depending on hboot version the boot image will need to be flashed via fastboot.
Boot into rom.
Good luck.
Edit: just saw your on 1.09 no need to flash boot image first.
Sent from my HTC One XL using xda premium
Oh by the way, TWRP 2.5 is known to have issues, so try using TWRP 2.3.3.1 instead.
You'll need to change recovery versions before doing any of the steps I mentioned above.
Sent from my Evita
timmaaa said:
Oh by the way, TWRP 2.5 is known to have issues, so try using TWRP 2.3.3.1 instead.
You'll need to change recovery versions before doing any of the steps I mentioned above.
Click to expand...
Click to collapse
TWRP 2.6 has been recently released, and appears to have resolved the issues with 2.5. But yeah, 2.5 and 2.4 are known to cause some serious problems (many ROMs will fail to flash).
Lol. All together now.
Sent from my Evita
---------- Post added at 12:37 AM ---------- Previous post was at 12:31 AM ----------
redpoint73 said:
TWRP 2.6 has been recently released, and appears to have resolved the issues with 2.5. But yeah, 2.5 and 2.4 are known to cause some serious problems (many ROMs will fail to flash).
Click to expand...
Click to collapse
Yeah I've heard it's working well, I'm gonna give it a spin hopefully in the next few days. I just thought it'd be best to suggest something we know for sure is solid for right now.
Sent from my Evita
Wow, thanks for the quick responses!
First of all, I can't mount SD card from TWRP. I can mount cache, data and System, but the checkbox nextto sdcard can't be clicked, stays unchecked. I can mount USB Storage but my computer says it needs to format the drive to use it, and I'm using Windows not Linux.
Secondly, whenever i try to flash openrecovery-twrp-2.3.1.0-evita.img with adb fastboot it says "The filename, directory name, or volume syntax is incorrect".
What do I do? :S
Also, after I've done this, what ROM do you suggest I download to flash, given my bootloader and situation?
dragancla said:
Wow, thanks for the quick responses!
First of all, I can't mount SD card from TWRP. I can mount cache, data and System, but the checkbox nextto sdcard can't be clicked, stays unchecked. I can mount USB Storage but my computer says it needs to format the drive to use it, and I'm using Windows not Linux.
Secondly, whenever i try to flash openrecovery-twrp-2.3.1.0-evita.img with adb fastboot it says "The filename, directory name, or volume syntax is incorrect".
What do I do? :S
Click to expand...
Click to collapse
You must have done a factory reset from bootloader, which has corrupted your storage. So, mount usb storage then format it using Windows to fat32 format.
The error you're encountering while trying to flash recovery is most likely because you're giving adb incorrect or mistyped command. To make it easier on yourself, rename the recovery zip file on your pc to something simple like "twrp.img" then issue the following command exactly:
fastboot flash recovery twrp.img
Sent from my Evita
dragancla said:
First of all, I can't mount SD card from TWRP. I can mount cache, data and System, but the checkbox nextto sdcard can't be clicked, stays unchecked.
Click to expand...
Click to collapse
You didn't do a factory reset from bootloader did you?
RollTribe said:
You didn't do a factory reset from bootloader did you?
Click to expand...
Click to collapse
Looks like he did. Instructions given above.
Sent from my Evita
---------- Post added at 12:53 AM ---------- Previous post was at 12:52 AM ----------
dragancla said:
Also, after I've done this, what ROM do you suggest I download to flash, given my bootloader and situation?
Click to expand...
Click to collapse
You can flash pretty much any Sense ROM, and most aosp ROMs (just not the ones with the 3.4 kernel).
Sent from my Evita
RollTribe said:
You didn't do a factory reset from bootloader did you?
Click to expand...
Click to collapse
I did :S Thought it would help...
timmaaa said:
You must have done a factory reset from bootloader, which has corrupted your storage. So, mount usb storage then format it using Windows to fat32 format.
The error you're encountering while trying to flash recovery is most likely because you're giving adb incorrect or mistyped command. To make it easier on yourself, rename the recovery zip file on your pc to something simple like "twrp.img" then issue the following command exactly:
fastboot flash recovery twrp.img
Sent from my Evita
Click to expand...
Click to collapse
Thanks, it worked! I can mount sdcard now!
What's the next step?
dragancla said:
I did :S Thought it would help...
Yeah, never do that...
Thanks, it worked! I can mount sdcard now!
What's the next step?
Click to expand...
Click to collapse
Now you can flash any ROM you want as long as it isn't AOSP with 3.4 kernel. Unless you really want the 3.4 ROM, but then you'd first have to s-off and then run the RUU to 3.18.
The next step after what? What exactly have you achieved so far?
Sent from my Evita
RollTribe said:
Now you can flash any ROM you want as long as it isn't AOSP with 3.4 kernel. Unless you really want the 3.4 ROM, but then you'd first have to s-off and then run the RUU to 3.18.
Click to expand...
Click to collapse
Would this work? http://forum.xda-developers.com/showthread.php?t=2230754
Or can you link me any ROM that would work for me, please?
dragancla said:
Would this work? http://forum.xda-developers.com/showthread.php?t=2230754
Or can you link me any ROM that would work for me, please?
Click to expand...
Click to collapse
Yeah, that would work. It's a little outdated, but it should work just fine.
timmaaa said:
The next step after what? What exactly have you achieved so far?
Sent from my Evita
Click to expand...
Click to collapse
Well, I can now access the sdcard/internal storage on my PC when I connect the cable in TWRP Recovery. I just need a ROM.
Okay, I have the same problem as the guy in this thread: https://forum.xda-developers.com/showthread.php?t=2571779&highlight=wiped+all+partitions , but only have a few differences. I now have no sdcard or sdcard\ext partitions... Says zero megs. Thankfully I back my stuff up everytime I sync up to my pc. Anywho, I believe I need to run RUU mode and reinstall ICS factory. Here is what happened: I have had the phone rooted and S-OFF for about a week and have made a few backups. I went into recovery and made another backup. Rebooted into system, saved contacts, and rebooted back into bootloader by accident. Well when I went to hit "recovery" option, I went down one too any times and hit factory reset. Now, when I go into recovery, there is not any restore points, nor any sdcard options available. I cant mount up usb mass storage in TWRP because there is no sdcard partition...Hrmmmmm...... I guess the actual question is, "Do I need to run RUU and that will probably, maybe fix it?"
Tid Bits:
TWRP v2.6.3.0
***tampered***
***unlocked***
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT- 2.14.0000
RADIO- 0.24P.32.09.06
OpenDSP- v34.1.0.45.1219
eMMC-boot
Its a known issue that doing a factory reset in bootloader on a modded EVITA corrupts the SD card. Plug the phone into a Windows PC, go to device manager, find the SD and format it FAT32. Its that simple.
Question 16 in the FAQs: http://forum.xda-developers.com/showthread.php?t=2136172
at which point i should be able to push a rom to the phone and get my OS back, correct? as of right now, i have no OS, but full recovery.
That's right. Format it then copy a ROM across to flash.
Sent from my Evita
Just did that. Had to reflash superSU before flshing a rom. It will not flash the ROM, it says that E: Error executing updater binary in zip 'blah, blah,blah' It did this with the last ROM i tried flashing. Any ideas?
lil_phreek said:
Just did that. Had to reflash superSU before flshing a rom. It will not flash the ROM, it says that E: Error executing updater binary in zip 'blah, blah,blah' It did this with the last ROM i tried flashing. Any ideas?
Click to expand...
Click to collapse
What ROM are you trying to flash, and what recovery are you using?
Sent from my One X using XDA Premium 4 mobile app
TWRP 2.6.3
Illusion 4.4.2
lil_phreek said:
TWRP 2.6.3
Illusion 4.4.2
Click to expand...
Click to collapse
Are you using the modified version of 2.6.3.0? The official version won't flash 4.4 ROMs. Also, there's no need to flash any Superuser zip, but if there was you'd need to flash it after the ROM.
Sent from my Evita
lil_phreek said:
TWRP 2.6.3
Illusion 4.4.2
Click to expand...
Click to collapse
There have been multiple reports in that thread of failed flashings with the unofficial twrp. There are some CWM versions available for 4.4 Roms though. I think the first few pages of the Beanstalk thread should get you going with that.
Sent from my One X using XDA Premium 4 mobile app
"wishing I was Kenny right now" My mistake on not paying attention to the fine print....I will check out that other thread. Thanks. I will post in a bit and let you guys know how it works out for me.
Don't forget to click the "Thanks" button for any posts that you found helpful.
Sorry for the delay guys. Literally as soon as I got my phone fixed, my laptop, which I use for all my necessary phone needs, slowly closed all its windows down, shut off, and mysteriously lost its OS.... LOL, one thing fixed, another down. Oh well. Anyway, I did exactly as was said in the other thread, and it worked like a charm. I am currently running Beanstalk 4.4, and it is an amazing rom. Love it. And thanks for all the help. I am heading back over to the Infuse forum to try and fix the other phone....
My HTC One S is rooted and unlocked with S-ON. I have flashed ROMs several times before with no problems, until all of a sudden I have been unable to flash any ROMs. In CWM 6 I get:
Code:
E:Error in /sdcard/ROM.zip
(Status 0)
Installation aborted.
I have tried redownloading the ROM, trying ROMs which have previously worked - all of which return the same error.
I have also tried reflashing CWM to no avail, and I flashed TWRP and got the error
Code:
E:Mount: Unable to find partition for path '/sdcard'
I would appreciate it if anyone could help me figure out what to do?
On what HBOOT version are you on? It seems that you're trying to use a recovery for HBOOT 2.15 with a 2.16 phone.
kdd998 said:
On what HBOOT version are you on? It seems that you're trying to use a recovery for HBOOT 2.15 with a 2.16 phone.
Click to expand...
Click to collapse
Thanks for the reply - however I can confirm that I'm on HBOOT 2.15 and the recovery is compatible. Besides, I have previously been able to flash ROMs with the same recovery, which is the strange thing.
Did you check that your download is OK? Said another way, MD5 checksum OK?
kdd998 said:
Did you check that your download is OK? Said another way, MD5 checksum OK?
Click to expand...
Click to collapse
Yep, MD5 checksums match.
What exact version of TWRP you're using and what ROM are you trying to flash?
Sent from nowhere over the air...
Rapier said:
What exact version of TWRP you're using and what ROM are you trying to flash?
Sent from nowhere over the air...
Click to expand...
Click to collapse
Currently I am using Philz Recovery 6.19.3 based on CWM 6.0.5, however I have previously used CWM Touch 6.0.4.8 and TWRP 2.0.8.1 (both for ville) and returned the same errors I posted above.
I am trying to flash CandyKat 4.4.4 for HBOOT 2.15. To test that it is not the ROM, I have tried flashing PAC ROM 4.3 which is my current ROM, and that didn't work either. Both of these ROMs are stored in the root folder of my internal sd card.
Try to use TWRP 2.8.0.1...the official one
Sent from nowhere over the air...
Rapier said:
Try to use TWRP 2.8.0.1...the official one
Click to expand...
Click to collapse
mlazim14 said:
have previously used CWM Touch 6.0.4.8 and TWRP 2.0.8.1 and returned the same errors I posted above
Click to expand...
Click to collapse
Already have done - it is that which retrieved the error 'E:Mount: Unable to find partition for path '/sdcard'
Issue solved! I've fixed it by flashing the new TWRP 2.8.1.0 recovery which is necessary for KitKat ROMs and it works fine now.
I had a rooted htc one mini then i tried changing the firmware to ViperOne but I forgot to boot the boot.img before installing ViperOne through Clorckworkmod recovery. I continued the install then now im always stuck on the booting screen, I tried restoring my backup in Clockworkmod recovery but it always says "E: can't mount sdcard", it kept on saying "can't mount sdcard" on everything in clockworkmod. I also cant access the internal storage thourgh my pc. I have no idea what to do now, tried fixing with RUU but i cant find the one the matches my phone, please help give me the easiest way cause im still a beginner, i dont mind if its rooted or not when its fixed i just want it to work again
Thank you in advance
radster12795 said:
I had a rooted htc one mini then i tried changing the firmware to ViperOne but I forgot to boot the boot.img before installing ViperOne through Clorckworkmod recovery. I continued the install then now im always stuck on the booting screen, I tried restoring my backup in Clockworkmod recovery but it always says "E: can't mount sdcard", it kept on saying "can't mount sdcard" on everything in clockworkmod. I also cant access the internal storage thourgh my pc. I have no idea what to do now, tried fixing with RUU but i cant find the one the matches my phone, please help give me the easiest way cause im still a beginner, i dont mind if its rooted or not when its fixed i just want it to work again
Thank you in advance
Click to expand...
Click to collapse
How did you get Viper for the Mini???
These are likely the instructions for you, too.
http://forum.xda-developers.com/htc-one-mini/help/help-installing-stock-rom-htc-one-mini-t2959490
jollywhitefoot said:
How did you get Viper for the Mini???
These are likely the instructions for you, too.
http://forum.xda-developers.com/htc-one-mini/help/help-installing-stock-rom-htc-one-mini-t2959490
Click to expand...
Click to collapse
tried adb push the zip file but it kept saying adb is out of date, device not found.
UPDATE!
made it work kept loading foe a long time then protocol failure, what does that mean?
radster12795 said:
tried adb push the zip file but it kept saying adb is out of date, device not found.
UPDATE!
made it work kept loading foe a long time then protocol failure, what does that mean?
Click to expand...
Click to collapse
I think you have usb issues. You should either try working from a fresh install of Windows or Ubuntu from disc.
Here are instructions for booting to Ubuntu from disc:
http://forum.xda-developers.com/showpost.php?p=55070544&postcount=22
jollywhitefoot said:
I think you have usb issues. You should either try working from a fresh install of Windows or Ubuntu from disc.
Here are instructions for booting to Ubuntu from disc:
http://forum.xda-developers.com/showpost.php?p=55070544&postcount=22
Click to expand...
Click to collapse
Finally made it work, went to sdcard installed the zip it said successful then i rebooted it but it is still stuck in the booting screen -_-
and when i opened the bootloading screen it still says no OS
TAMPERED
UNLOCKED
M4_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.27.40e.00.11
OpenDSP-v19.2.0268.0927
OS-
eMMC-boot 1024mb
i think my phone doesnt have the firmware cause it said successful but it also said cant moutn /system at the end, any idea?
Thank you very much btw, for helping me, learned so much stuff
followed the other comments to install the sense6 firmware, my phone needs to be S-OF and superCID, finished superCID but i cant run rumrunner cause my phone dont have OS, is there a way to run rumrunner thourgh fastboot or recovery?
Dude. You have to use files intended for the mini. Install a recovery for the mini from here: http://techerrata.com/browse/twrp2/m4ul and then flash the Rom again
jollywhitefoot said:
Dude. You have to use files intended for the mini. Install a recovery for the mini from here: http://techerrata.com/browse/twrp2/m4ul and then flash the Rom again
Click to expand...
Click to collapse
oaky, i have installed twrp 2.7.1.1 and now adb pushing the rom and ill try to recovery install the rom again
Finished the zip install
Updating partition details...
E:Unable to mount '/system'
Full SELinux support is present.
Installing 'sdcard/Stock_Sense6M4_Deodexed-Rooted.zip'...
Checking for MD5 file..
Skipping MD5 check: no MD5 file found
->Mounting System & Data
->Extracting System
->Extracting Data
->Creating toolbox symlinks
->Creating additional symlinks
->Installing busybox
->Setting permissions
->Extracting kernel
Updating partition detail...
E: Unable to mount '/system'
It said successful but still no OS installed
sorry the problems just keep coming and coming
First, you can try wiping system and data partitions prior to installing (don't wipe sd card), but I think you need to update your firmware to install sense 6 Roms.
To do that you'll need to s-off first. Revone might work for you and rumrunner should work.
Or you can try installing this sense 5.5 rom. http://forum.xda-developers.com/showthread.php?p=50715903
jollywhitefoot said:
First, you can try wiping system and data partitions prior to installing (don't wipe sd card), but I think you need to update your firmware to install sense 6 Roms.
To do that you'll need to s-off first. Revone might work for you and rumrunner should work.
Or you can try installing this sense 5.5 rom. http://forum.xda-developers.com/showthread.php?p=50715903
Click to expand...
Click to collapse
Thank you for the past 2 days of helping, i have finally fixed it :highfive:
radster12795 said:
Thank you for the past 2 days of helping, i have finally fixed it :highfive:
Click to expand...
Click to collapse
No problem. Did flashing the ROM in post 8 work?
jollywhitefoot said:
No problem. Did flashing the ROM in post 8 work?
Click to expand...
Click to collapse
YES!! it worked perfectly, Thank you very much
thinking about upgrading to sense 6 now