General InformationFrom time to time while While Looking Through The Question & Answering Section I See At lest 3-5 Threads Talking About "How Do I get Back To Stock" Or "How Do I Run A Ruu" Now Most (Hopefully) Already Know How To Do This But To Those Who Don't Or Just Want To Review On What To Do Then To Day Is Your Lucky Day
Prerequisites
HTC One S (This Guide Can Be Used For Most HTC Phone Just Don't Use The Stock Recovery )
Ruu For Your Phone Or What Ever Floats Your Boat
Stock Recovery
Windows Computer
Fastboot Drivers
Android USB Cable
Over 50% Battery Life
About 15-30 Min Of Your Time
Getting the RUU
Let's Start Of By Getting Your Ruu
I Would Get RUU From Here Android RUU
Get The RUU That matches your carrier If you are S-Off/SuperCID,
you can run any RUU. Otherwise it must match those or it will not run.
So Grab Your Ruu For Your Phone Then Proceed To The Next Step
Testing FastBoot So For Your Phone To Go In To Ruu Mode To Go Back To Stock You Will Need Fastboot Hopefully You Have It Installed Already But If Your Doubtful And Don't Think You Have It Then...
Boot in To Bootloader With VolDown+Power Button
Go To Your FastBoot Folder Click On The Folder With CTRL And Right Clicking The Mouse And And Type The Following Commands
Code:
Fastboot devices
You Should Get This
Code:
HT24RW406168 fastboot
Or some Thing Along Those Lines If Not Then DownLoad HTC Drivers I will Provide You With A Link On Where To Find Them
Flashing Stock RecoveryNOTE If You Have No Custom Recovery Then And You Are On Stock Recovery Then You Do Not Need This Step
Now We Will Need To Flash Stock Recovery For The Ruu To work Good Thing For You It Is In The Zip I Have Provided For You
Look For The Zip At The Bottom Of The Thread And Flash It In Recovery After You Have Flashed It In recovery Then Reboot To Bootloader
Running Your RuuNow IF You Have Gotten This Far Then Its Time For You To Run Your Ruu So
Have Your Phone In Bootloader > Fastboot Then Double Click The Ruu And Let It Run
Now it May Take Some Time For It To Load Up Complete Normal After It Has Gone In To
It Will Give You Some Info Just Go Past It And Once You Get To The End With Your Phone
Plugged In Give It The Finely OK And Let The Ruu Do Its Magic
Now Your Phone Is In A Delicate State So If You Remove The Cable OR Any Thing Should Happen Your Phone Will BRICK
Once It Is Done It Will reboot Your Phone And You Will Be Stock Again.
Files/InfoHTC Drivers
Stock Recovery For Ville Only
Go Back To **LOCKED*
yes posttwobandit striks again awesome
Thanks a lot! This guide is very useful.
I got stuck when trying to install the Flash Stock Recovery. I currently have a TWRP v2.4.1.0. When I flash the zip file of the stock rom you provided I got the following error messages (see also the attached screenshot):
Code:
E:Unable to mount '/sdcard'
E:Unable to recreate android secure folder.
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
Updating partition details...
E:Unable to mount storage.
E:Unable to mount /sdcard during GUI startup.
E:Unable to mount /sdcard when trying to read settings
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
Error flashing zip '/sdcard/StockRecovery.zip'
Updating partition details...
E:Unable to mount '/sdcard'
E:Unable to mount storage.
Any idea on how I could fix this?
krige said:
Thanks a lot! This guide is very useful.
I got stuck when trying to install the Flash Stock Recovery. I currently have a TWRP v2.4.1.0. When I flash the zip file of the stock rom you provided I got the following error messages (see also the attached screenshot):
Code:
E:Unable to mount '/sdcard'
E:Unable to recreate android secure folder.
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
Updating partition details...
E:Unable to mount storage.
E:Unable to mount /sdcard during GUI startup.
E:Unable to mount /sdcard when trying to read settings
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
Error flashing zip '/sdcard/StockRecovery.zip'
Updating partition details...
E:Unable to mount '/sdcard'
E:Unable to mount storage.
Any idea on how I could fix this?
Click to expand...
Click to collapse
looks like your SD is corrupted if so you will have to wipe it
Sent from my One S using Tapatalk
krige said:
Thanks a lot! This guide is very useful.
I got stuck when trying to install the Flash Stock Recovery. I currently have a TWRP v2.4.1.0. When I flash the zip file of the stock rom you provided I got the following error messages (see also the attached screenshot):
Code:
E:Unable to mount '/sdcard'
E:Unable to recreate android secure folder.
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
Updating partition details...
E:Unable to mount storage.
E:Unable to mount /sdcard during GUI startup.
E:Unable to mount /sdcard when trying to read settings
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
Error flashing zip '/sdcard/StockRecovery.zip'
Updating partition details...
E:Unable to mount '/sdcard'
E:Unable to mount storage.
Any idea on how I could fix this?
Click to expand...
Click to collapse
If your on HBOOT 2.16, use the TWRP use the recovery that came with Maximus or this recovery. For HBOOT 2.15, use the latest TWRP on their page
dd98 said:
If your on HBOOT 2.16, use the TWRP use the recovery that came with Maximus or this recovery. For HBOOT 2.15, use the latest TWRP on their page
Click to expand...
Click to collapse
I am on HBOOT 2.15 with TWRP 2.4.1.0. Following your suggestion I downloaded "twrp-2.7.0.8-ville.img" from here and flashed it using fastboot.
Once in TWRP 2.7.0.8 I was able to successfully flash cm-11-20140609-SNAPSHOT-M7-ville.zip and gapps-kk-20140606-signed.zip but once I boot the phone I get into a screen with thin blue lines and some blinking cyan lines (I believe that's CM logo corrupted animation). See the attached screenshot.
Trying to wipe the cache and dalvik cache and flashing again didn't fix it.
Any other suggestion?
krige said:
I am on HBOOT 2.15 with TWRP 2.4.1.0. Following your suggestion I downloaded "twrp-2.7.0.8-ville.img" from here and flashed it using fastboot.
Once in TWRP 2.7.0.8 I was able to successfully flash cm-11-20140609-SNAPSHOT-M7-ville.zip and gapps-kk-20140606-signed.zip but once I boot the phone I get into a screen with thin blue lines and some blinking cyan lines (I believe that's CM logo corrupted animation). See the attached screenshot.
Trying to wipe the cache and dalvik cache and flashing again didn't fix it.
Any other suggestion?
Click to expand...
Click to collapse
Yeah that happened to me before, not sure why but I dont know how to fix it, maybe someone else does
Furthermore, my computer doesn't seem to recognize the phone with the new TWRP: when I plug it to it a message dialog says the drivers where not successfully installed. I tried installing HTCDriver_4.2.0.001.exe and HTC_BMP_USB_Driver_x64_1.0.5375.msi from here and even the full HTC Sync Manager from the HTC web site but none of them solved the problem. I've run out of ideas...
Same results with CWM 6.0.4 and TWRP 2.7.1.0a, no drivers found and thin blue lines after flashing CM.
I have extracted the img file from the zip of the stock kernel linked in the first post and flashed it through fastboot. Then I followed the instructions to install the stock ROM in the first post, using the RUU RUU_Ville_U_TIM_IT_1.78.901.6_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_261961 , but the procedure never ended. I left it running the whole night but when I checked it in the morning the application was still running and the phone was displaying the HTC logo (see the attached screenshots).
I have just noticed my phone is S-ON (see the attached screenshot).
As the instructions in the first post suggest to "Get The RUU That matches your carrier If you are S-Off/SuperCID", what should we do if we are S-ON? Should we get to S-Off first?
Here is the fastboot getvar all output:
Code:
version: 0.5
version-bootloader: 2.15.0000
version-baseband: 1.15.50.05.29
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
product: vle
platform: HBOOT-8960
modelid: PJ4010000
cidnum: VODAP102
battery-status: good
battery-voltage: 4167mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-64bedd38
hbootpreupdate: 11
gencheckpt: 0
Summing up these are the current problems I am having:
- Windows does not recognize the phone when it is plugged to it in recovery mode because it can't find the drivers (the phone is recognized under Linux though)
- the phone is S-ON: I am not sure which procedure I should follow as all the guides I find around are for S-Off versions, I don't know whether I should first get into S-Off first (if that is even possible)
- I don't know how to choose the right RUU for my phone. I gathered I should choose the RUU according to my CID, that is VODAP102 but none of the files in the Android RUU page mentioned in the first post seems to match it.
- There seems to be no RUU for VODAP102 only a Nandroid Backup. I managed to copy it on the phone from a computer with Linux, in the sdcard directory, but I don't know how exactly I am supposed to install it. On CWM there is a "backup and restore" entry: when I choose "restore from /storage/sdcard0" it tells me "No files found" (see the attached screenshot). Am I supposed to extract the content of the zip file?
- I don't know whether the phone should be locked or unlocked while running the RUU nor whether that really matters.
if you can, go s-off and change your CID to HTC__001 (EU CID). Assuming your vodafone in europe, you should have no problems with mobile networks, if your not in EU then don't do this
I have tried obtaining the supercid following this guide but I got stopped at step 3 because of the following error:
Code:
dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4
dd: can't open '/sdcard/mmcblk0p4': No such file or directory
I tried with sdcard0 and sdcard1 but nothing changed.
cat /etc/fstab
Code:
/dev/block/mmcblk0p34 /cache ext4 rw
/dev/block/mmcblk0p35 /data ext4 rw
/dev/block/mmcblk0p33 /system ext4 rw
I tried mounting the sdcard from the recovery (CWM 6.0.4.8) but I got another error:
Code:
error mounting /stoarge/sdcard0
Here is the output of dmesg.
I have been told there is 99% chance the flash is burned because of the following two lines:
Code:
<6>[ 5.190538] mmc0: new high speed DDR MMC card at address 0001
<6>[ 5.196337] mmcblk0: mmc0:0001 MAG2GA 14.5 GiB
That's because the HTC One S apparently uses a Samsung flash, model MAG2GA, which has a known bug similar to the S3 one.
Do you concur? Should I trash the phone?
Any insight would be highly appreciated.
but the bootloader should not be " locked" ?
Hi! I'm on hboot 2,16...do i need to revert to 2,15 to run a RUU?
Other info:
S-off
Supercid
TWRP
I need to pass the phone to my father, want to give him stock
Thanks
Sent from my Nexus 5 using XDA Free mobile app
Jeeza said:
Hi! I'm on hboot 2,16...do i need to revert to 2,15 to run a RUU?
Other info:
S-off
Supercid
TWRP
I need to pass the phone to my father, want to give him stock
Thanks
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
No you should be good if you get a error it maybe from your cid all you would have to do is just change it to the ruu your running
I reverted to 2.15 prior to running the ruu and everything went fine..thanks for the guide!
Sent from my Nexus 5 using XDA Free mobile app
Thanks man! this help me a lot, I didn't know how to do this :laugh:
Does it works in all the CIDs?
Slayz08 said:
Does it works in all the CIDs?
Click to expand...
Click to collapse
Umm All you have to do is apply it with the ruu you have if it needs a certain cid then run a different one
Related
hi,
I tried upgrading my tf300t from cm10.1 to cm10.2 . after a few failed attempts during which I am not exectly sure what I did wrong i got the device into a condition in which it only boots directly into CWM v6.0.2.3 without any option to do anything else. pressing power+volume down does not stop it from directly booting into recovery.
inside the recovery it says:
"E:Can't mount / cache/recovery/command/
E:Can't mount / cache/recovery/log/
E:Can't open / cache/recovery/log/
E:Can't mount / cache/recovery/last_log/
E:Can't open / cache/recovery/last_log/",
and i cannot mount any partition on the device. trying to access it from fastboot\adb has not been successful.
Any help would be appreciated.
thanks a lot,
guy
I now recall that at some point after trying to flash cm10.2 didn't work I tried flashing the offical asus firmware blob. after that the device successfully booted but when I tried to return to the recovery mode I still could not mount the /data partition. after that I tried some more flashing which brought me to the current situation.
new development -
after installing the universal naked driver i was able to boot into the boot loader using adb and I even can boot the device to the os, though no change when inside the recovery mode. if the device reboots it automatically goes into recovery and to reboot it I have to use adb again.
Ghtm said:
new development -
after installing the universal naked driver i was able to boot into the boot loader using adb and I even can boot the device to the os, though no change when inside the recovery mode. if the device reboots it automatically goes into recovery and to reboot it I have to use adb again.
Click to expand...
Click to collapse
Flash the updated stock ROM again via fastboot to reset it back to stock. then flash the correct TWRP and then flash the CM 10.2 ROM you wanted.
cmendonc2 said:
Flash the updated stock ROM again via fastboot to reset it back to stock. then flash the correct TWRP and then flash the CM 10.2 ROM you wanted.
Click to expand...
Click to collapse
how do i flash a rom using fastboot?
Ghtm said:
how do i flash a rom using fastboot?
Click to expand...
Click to collapse
like this:
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/
Code:
fastboot -i 0x0B05 flash system blob
cmendonc2 said:
like this:
Code:
fastboot -i 0x0B05 flash system blob
Click to expand...
Click to collapse
I've tried that and the device does not seem to be responding to the idea. in fact I dont think it gets anything I've tried to flash at all. the files do transfer but do not seem to install. after starting a flash with fastboot the device stops responding.
Ghtm said:
I've tried that and the device does not seem to be responding to the idea. in fact I dont think it gets anything I've tried to flash at all. the files do transfer but do not seem to install. after starting a flash with fastboot the device stops responding.
Click to expand...
Click to collapse
plus, the bootloader screen does not show the usb icon at all. I am flashing when the device is in the bootloader.
at the bootloader screen there is a message: "key driver not found"
Ghtm said:
I've tried that and the device does not seem to be responding to the idea. in fact I dont think it gets anything I've tried to flash at all. the files do transfer but do not seem to install. after starting a flash with fastboot the device stops responding.
Click to expand...
Click to collapse
OK you said it can boot into Android though. Use terminal emulator to install the TWRP and then flash the stock ROM from inside TWRP. Just make sure the TWRP matches your bootloader.
---------- Post added at 04:52 PM ---------- Previous post was at 04:51 PM ----------
Ghtm said:
plus, the bootloader screen does not show the usb icon at all. I am flashing when the device is in the bootloader.
at the bootloader screen there is a message: "key driver not found"
Click to expand...
Click to collapse
That means you are on the 4.2.1 or 4.2.2 bootloader. That bootloader doesnt have a USB icon, it goes directly to fastboot if it is detected and that is completely normal.
cmendonc2 said:
OK you said it can boot into Android though. Use terminal emulator to install the TWRP and then flash the stock ROM from inside TWRP. Just make sure the TWRP matches your bootloader.
---------- Post added at 04:52 PM ---------- Previous post was at 04:51 PM ----------
That means you are on the 4.2.1 or 4.2.2 bootloader. That bootloader doesnt have a USB icon, it goes directly to fastboot if it is detected and that is completely normal.
Click to expand...
Click to collapse
it says permission denied (cause i do not have root access?)
Ghtm said:
it says permission denied (cause i do not have root access?)
Click to expand...
Click to collapse
Oh i thought you still had CM10.1 on it. Can you flash ROMs from that CWM or is the /data thing messing it up.
cmendonc2 said:
Oh i thought you still had CM10.1 on it. Can you flash ROMs from that CWM or is the /data thing messing it up.
Click to expand...
Click to collapse
the /data prevents me from accessing anything on the sdcard so i cant flash anything from inside the recovery itself.
so, after doing as the guy in this thread - http://forum.xda-developers.com/showthread.php?t=2425581 says, I managed to make the device successfully reboot to the os by default and even make it reinstall the stock rom and than twrp recovery. the problem no is when entering recovery, it asks for a password which i do not know. when choosing cancel it gets me in but now it displays:
"E: unable to find partition size for /misc
E: unable to find partition size for /staging
E: unable to find partition size for /data
E: unable to find partition size for /recovery
E: unable to find partition size for /boot
updating partition details...
E: unable to mount /system
E: unable to mount /cache
E: unable to mount /cache
E:TWFunc::copy_log -- cant open destination log file: /cache/recovery/log
E:unable to set emmc bootloader message
E: unable to mount /cache"
when trying to install a different rom the recovery mode fails to access the internal/external sdcard.
thanks in advance,
guy
Ghtm said:
so, after doing as the guy in this thread - http://forum.xda-developers.com/showthread.php?t=2425581 says, I managed to make the device successfully reboot to the os by default and even make it reinstall the stock rom and than twrp recovery. the problem no is when entering recovery, it asks for a password which i do not know. when choosing cancel it gets me in but now it displays:
"E: unable to find partition size for /misc
E: unable to find partition size for /staging
E: unable to find partition size for /data
E: unable to find partition size for /recovery
E: unable to find partition size for /boot
updating partition details...
E: unable to mount /system
E: unable to mount /cache
E: unable to mount /cache
E:TWFunc::copy_log -- cant open destination log file: /cache/recovery/log
E:unable to set emmc bootloader message
E: unable to mount /cache"
when trying to install a different rom the recovery mode fails to access the internal/external sdcard.
thanks in advance,
guy
Click to expand...
Click to collapse
that means you probably flashed the wrong version of TWRP. Are you on the stock 10.6.1.8 or on a later version of bootloader? Those are different.
cmendonc2 said:
that means you probably flashed the wrong version of TWRP. Are you on the stock 10.6.1.8 or on a later version of bootloader? Those are different.
Click to expand...
Click to collapse
stock rom version 10.6.1.27.5 (build number JOP40D.US_epad-10.6.1.27.5-20130902)
TWRP 2.6.3.0
are those not compatible?
*
trying TWRP 2.5.0.0 or 2.4.2.0 made no difference.
Ghtm said:
stock rom version 10.6.1.27.5 (build number JOP40D.US_epad-10.6.1.27.5-20130902)
TWRP 2.6.3.0
are those not compatible?
*
trying TWRP 2.5.0.0 or 2.4.2.0 made no difference.
Click to expand...
Click to collapse
Using twrp 2.6.3.0 -4.2 ? Or -jb?
cmendonc2 said:
Using twrp 2.6.3.0 -4.2 ? Or -jb?
Click to expand...
Click to collapse
I do not remeber which I've tried. which one should it be?
*
I tried them both again. both require a password at start and both fail mounting the partitions, showing
"E: unable to find partition size for /misc
E: unable to find partition size for /staging
E: unable to find partition size for /data
E: unable to find partition size for /recovery
E: unable to find partition size for /boot
updating partition details...
E: unable to mount /system
E: unable to mount /cache
E: unable to mount /cache
E:TWFunc::copy_log -- cant open destination log file: /cache/recovery/log
E:unable to set emmc bootloader message
E: unable to mount /cache"
Ghtm said:
I do not remeber which I've tried. which one should it be?
*
I tried them both again. both require a password at start and both fail mounting the partitions, showing
"E: unable to find partition size for /misc
E: unable to find partition size for /staging
E: unable to find partition size for /data
E: unable to find partition size for /recovery
E: unable to find partition size for /boot
updating partition details...
E: unable to mount /system
E: unable to mount /cache
E: unable to mount /cache
E:TWFunc::copy_log -- cant open destination log file: /cache/recovery/log
E:unable to set emmc bootloader message
E: unable to mount /cache"
Click to expand...
Click to collapse
Use the 4.2 one. The jb will result in a very bad brick.
cmendonc2 said:
Use the 4.2 one. The jb will result in a very bad brick.
Click to expand...
Click to collapse
seems to be working! thank you very much, I really appreciate the help! :laugh::victory:
Ghtm said:
seems to be working! thank you very much, I really appreciate the help! :laugh::victory:
Click to expand...
Click to collapse
No problem, Merry Christmas!
.
Good day everyone,
Please Help Me. Im not to sure what exactly i have done .but heres what information i do know.
I have a boost mobile k2_cl 4.2.2 sense 5 . While trying to root i seem to have deleted my internal sd and no longer have an operating system. i do have access to : bootloader which shows the following
TAMPERED
UNLOCKED K2_CL PVT Ship On RL
hboot 2.21.000
Radio 1.12.50.0516
Open DSD V10.2.0268.0401
OS
EMMC boot 1024 MB
I am also able to access fastboot as well as my recovery TWRP version 2.7.1-k2_cl. I was in the process of rooting it. I used the HTC.com guide to unlock the boot loader and using a "Mini-SDK" from Android Forums flashed the previously mentioned TWRP recovery. This was a three or four hour project for me to get this far and I was fairly beat by then but,
The only thing that did not go according to directions was that I had used a generic USB cable which was a loose fit into the phone. Near the end of my task I bumped the phone and the "kadink" "kadink" beeps that signal that something is either being plugged or unplugged from the PC did about 6 beeps. When I finally found an OEM cable and plugged it in there was no longer an operating system on the phone. Furthermore, the TWRP recovery would not function and perform any commands. Whether a back up or Format the SC card or to Wi pe anything, all options of the TWRP recovery produced the same results. the log reads when I tried the Repair function -
E: unable to mount 'int_sd'
E: unable to mount '/int_sd'
Updating partition details
E: unable to mount '/cache'
E: unable to mount'/data'
and E: unable to mount 'int_sd' and also unable to mount the following: internal storage, /int_sd during gui start up, /cache, then it says,
Full SELinux is present then,
E: unable to mount "/cache', /cache, int_sd/twrp when trying to read setting file. Then
Repairing ext_sd card using dosfsck...
Unable to repair '/sd card
Error repairing file system
But I also get about the identicle message, about being unable to mount anything it tries to mount with all the options of TWRP. Is there someone to tell me what to do to fix this? I have a nandroid back up with the stock RUU to put back on it, or if you know of a better version of something could you advise me what to do?
Thanks a million guys,
mike
2 weeks ago, my oneplus stucked in a bootloop. it just restarted itself and after the oneplus logo, endless bootanimation
Infos: Oneplus china version 64 GB black, not rooted, before error no twrp installed
I think I tried everything, different versions of twrp and via adb sideload tried to flash different official .zip versions of cygnmod. always the same error:
E: Unable to mount '/cache'
E: Unable to mount '/cache'
E: Unable to mount /data/meida/TWRP/ . twrps when trying to read settings file.
E: No valid storage partitions found for MTP.
E: Unable to mount '/data'
E: Unable to mount '/data'
I also tried different toolboxes (chinese omnipotent toolbox; oneplus one toolkit) flashing process was ok, but then it restarted and still bootloop.
does anyone know this problem and has a solution? thanks in advance...
+1
n J o y said:
+1
Click to expand...
Click to collapse
This sounds serious,
@timmaaa @timmaaa
waterdaan said:
This sounds serious,
@timmaaa @timmaaa
Click to expand...
Click to collapse
E: Unable to mount ' /data'
E: Unable to mount ' /cache'
E: Unable to mount storage.
E: Unable to mount /data/media during GUI start up.
and in fastboot trying to flash userdata (or anything)--> "FAILED (remote: failed to erase partition)".
The phone works only in fastboot or recovery, also with otg.
I think that OPO needs a script to recreate the partition in storage (?)
This is way over my head, you should wait for timmaaa to respond
n J o y said:
E: Unable to mount ' /data'
E: Unable to mount ' /cache'
E: Unable to mount storage.
E: Unable to mount /data/media during GUI start up.
and in fastboot trying to flash userdata (or anything)--> "FAILED (remote: failed to erase partition)".
The phone works only in fastboot or recovery, also with otg.
I think that OPO needs a script to recreate the partition in storage (?)
Click to expand...
Click to collapse
Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
Follow the instructions in Section 8.
timmaaa said:
Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
Follow the instructions in Section 8.
Click to expand...
Click to collapse
Thank you very much for helping everybody out
Much appreciated!!!
You're the best
timmaaa said:
Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
Follow the instructions in Section 8.
Click to expand...
Click to collapse
If i try to flash something on fastboot it says --> "FAILED (remote: failed to erase partition)".
hi,
i already have 2 opos with this issue, one which is my own and one i ordered for a friend. the phone just rebooted itself at some point and was stuck in a bootloop. access to recovery and fastboot work, but recovery cant mount /system, /data, /persist, and /firmware. formatting doesnt help, flashing factory images gets stuck when flashing either system.img or userdata.img,
the first phone is already shipped out for rma and the second one will soon be shipped out.
maybe there is a problem with the memory chips themselves?
n J o y said:
If i try to flash something on fastboot it says --> "FAILED (remote: failed to erase partition)".
Click to expand...
Click to collapse
Ok, you might need to try one of these:
http://forum.xda-developers.com/showthread.php?t=2970390
http://forum.xda-developers.com/showthread.php?t=2991851
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Transmitted via Bacon
Hi everyone,
today i tried to update my CM11 to the newest CM12 Version. I booted into TWRP recovery and made a full Wipe. While doing this, my device had something like power loss, so the wipe could not finish.
Now the device doesn't boot anyway, after Power on it's booting into fastboot mode. The recovery isn't able to start. It is possible to use ADB and Fastboot. Using "fastboot boot /....../recovery.img it is possible to boot an recovery. The TWRP Recovery displays:
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/boot'
E:Unable to find partition size for '/misc'
E:Updating partition details
E:Unable to mount '/cache'
E:Unable to mount '/data'
E:Unable to mount '/sytem'
...done
E:Unable to mount storage
E:Unable to mount /sdcard during GUI startup
E:Unable to mount '/cache'
Full SELinux support is present
E:Unable to mount '/cache'
E:Unable to set emmc bootloader message.
E:Unable to mount /'cache'
E:Unable to mount /sdcard/TWRP/.twrps when trying to read settings file.
MTP Enabled
The "repair file system" option in TRWP Recovery doesnt work.
After several hours reading threads about similar problems i don't know what to do.
How can i repair the file system tables to reinstall the CM12 or any other ROM?
Hopefully
DragonGuard
I think, i have an idea.
What about to rewrite the complete partitions on my Sensation using adb shell and then rewrite with the partitions? Could that work?
I read an article with an similar problem here: cyanogenmod.org
The problem was that I managed to screw up the partitions on my internal storage card, so basically nothing would work properly. I could still get into recovery, though. That's key.
Here's what you'll need:
Working recovery, basic knowledge of adb & the shell
Parted (download here)
stock PB31IMG.zip
Note also that I had run unrevoked forever (so my phone was S-OFF) ... I'm not sure if that's required or not.
So, grab parted from the link above. Now you need to extract the individual binaries from the .zip (the 6 files in the sdparted folder within the zip), ideally to your android-sdk\tools directory. Now push all 6 files (adb push [file] /sbin/). Next, we need to make them useable, so go into the shell (adb shell). Change to your /sbin/ directory, and run: chmod 0755 <file> on each of the 6 files.
Now, we need to fix the partitions. This is assuming that the partitions are there, just the wrong format (which is what happened to me .. I accidentally made them FAT32 instead of ext). So, run the following: parted /dev/block/mmcblk0 mkfs ext2. It will ask if you want to continue, hit yes. When it asks for the partition number, enter 1. Next, when it asks for the format, enter ext2. Let it do its thing. Now, once it's done, run parted again. This time, enter partition 2 (everything else is the same).
Once all that's done, your recovery program should be able to mount both the /data and /cache partitions. If that's true, you're pretty much done! One thing I found was that I couldn't directly install a new OS (I tried both Cyanogen and Ultimate). In both cases, it would look for stuff in the davik-cache that it couldn't find, so something wasn't installing correctly I think. So, if that happens, flash back to the stock PB31IMG.zip (put it in the root of your /sdcard/ and let hboot install it), and then root your phone anew. That's what I ended up doing.
Again, huge credit for this goes to -Steveo- and ciwrl for helping me figure out which partitions were the right ones (and for supplying parted, which I hadn't been able to find anywhere). If something doesn't end up working, just drop me a pm and we'll see what we can do.
Click to expand...
Click to collapse
Today i would need parted for ext4 partitions and i need to know where on the internal storage i have to write which partition. Is this a possible way to repair the partitions?
Hopefully
Bump
I'm having the same problem, my recovery log shows exactly the same. Have you found a solution yet?
Hi,
i am sorry, but i haven't found any solution yet. I am looking for an HTC Sensation to pull the emmc Data system Files and rewrite it on my broken HTC Sensation. I need the /dev/block/mmcblk0 etc. files to try. In my /dev/block/ folder are only "loop" files located, i think they are part of my problem.
Greetz
i had a spare sensation i was going to use as a backup.
earlier today it was running 4.4.4 , decided i would try 5.0.x clearly i made a mistake somewhere.
i have no access to /cache + /data
was using twrp 2.8.5.0
if i try and flash i get the following
e: could not mount / data and unable to find crypto footer.
e:unable to mount /cache
e:unable to mount /data
Seen a few simliar threads.... but am going in circles.
i can get phone into Fastboot USB and access if from the pc via adb. they i am lost.
Any suggestions gratefully received.
Hi,
i also have this problem. See my thread "[Q] Partition destroyed after power loss" below.
It looks like a problem with twrp2.8.5.0. on the HTC Sensation.
I've got the idea, to create new partitions on the device, but i haven't the time to do it. If you get any results, tell me please :=)
Greetz
DragonGuard
stirnpanzer said:
i had a spare sensation i was going to use as a backup.
earlier today it was running 4.4.4 , decided i would try 5.0.x clearly i made a mistake somewhere.
i have no access to /cache + /data
was using twrp 2.8.5.0
if i try and flash i get the following
e: could not mount / data and unable to find crypto footer.
e:unable to mount /cache
e:unable to mount /data
Seen a few simliar threads.... but am going in circles.
i can get phone into Fastboot USB and access if from the pc via adb. they i am lost.
Any suggestions gratefully received.
Click to expand...
Click to collapse
Try with latest 4ext recovery.
tom0769 said:
Try with latest 4ext recovery.
Click to expand...
Click to collapse
I started a RUU of stock and it kept sticking a about 45% ......
All i can get phone to do now is switch on with HTC in the centre of the screen with a Triangle in each corner.
Vol up/down make no effect at power on.
If i try and run 4ext install from pc , it reboots phone and fails on "writing recovery" by saying "remote: not allowed"
So im sort of stuck now ...