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.
Related
Anybody figure out how to fix this? I can find people having this problem flashing 4.4 but I can't flash anything. I've tried to flash mf1 firmware, a 4.3 carbon nightly, and a 4.3 pac nightly. All with the same results. Here is exactly what I did -
I flashed PhilZ recovery earlier on a earlier version of TWRP.
kept getting a "failed" in PhilZ
Flashed latest TWRP via Odin
Tried flashing the above mentioned zips all with the error message.
Restored my hyper drive rls16 backup (4.1.2)
Installed latest TWRP via goomanager app
Edit : my phone is flashed to PagePlus so I kinda have to be careful I'm afraid of using Odin to go back to stock/rooted but my luck that's what it'll take. When I get home I'm going to try it with a older version of TWRP that's the only other thing I can think to try.
Any suggestions or info is appreciated.
delete
anyone ? please ?
Supposedly the update binary here is generic, you could try replacing the one in the rom zip with it
http://forum.xda-developers.com/showthread.php?t=2492496
Sent from my SCH-I535 using XDA Premium 4 mobile app
I've tried CWM PhilZ and TWRP all latest versions, and still can't get rid of this.
I Cannot install any rom, whatsoever. I did manage to install a MF1 radio zip, but that's it. I can't install 4.3 or even 4.2 ..
I've replaced the update-binary inside the zips, and edited the update-script and removed the stuff used for recognizing the device, still no dice ..
I ended up flashing a full mf1 img via Odin and then used casual to root/unlock/recovery install - and I STILL get the error. Not sure where to go from here. Seems like nobody else is having this problem unless they're not on the latest recovery and trying to flash KitKat.
Thought I'd share the rest of my story ..
edit: I was able to restore a old backup of 1.7 carbon ...lol. better than nothing or a TW rom, that's for sure.
When you replaced the update binary did you get the same error or a different one? Also, have you tried flashing from internal and external SD?
Sent from my SCH-I535 using XDA Premium 4 mobile app
dpeeps74 said:
When you replaced the update binary did you get the same error or a different one? Also, have you tried flashing from internal and external SD?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry I didn't get a notification for this.
I did get the same error. I did get a error 6 once or twice but it was because I edited the update-script file and used word or word pad I downloaded note++ and it stopped and went back to error 7 :banghead:
Sent from my SCH-I535 using Tapatalk
cjmcsw87 said:
Sorry I didn't get a notification for this.
I did get the same error. I did get a error 6 once or twice but it was because I edited the update-script file and used word or word pad I downloaded note++ and it stopped and went back to error 7 :banghead:
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
OK, I have one for you to try, use the original rom zip (don't edit the update-script), when you flash in recovery and it failed, select boot and boot back into recovery, then reflash again. Try it with the latest TWRP 2.6.3.2.
SOLVED ! only took a week ...
I had been using an update-binary file that was posted in a thread.
I took the file from PhilZ recovery ( which I had been able to flash, just nothing else ) and used that one. Imagine that, it worked.
**DUH** :silly:
cjmcsw87 said:
SOLVED ! only took a week ...
I had been using an update-binary file that was posted in a thread.
I took the file from PhilZ recovery ( which I had been able to flash, just nothing else ) and used that one. Imagine that, it worked.
**DUH** :silly:
Click to expand...
Click to collapse
Nice, glad you have a happy ending!!
buhohitr said:
Nice, glad you have a happy ending!!
Click to expand...
Click to collapse
Me too buddy, let me tell ya ..
I appreciate the advice along the way. Thank you.
now I just have to decide if I want carbon or pac as my daily driver for awhile.. Carbon is what i've almost always used after I figured out how bloated and laggy TW is.. Best of all my PagePlus flash is perfectly fine, didn't have to add APN's or mess with anything else to get data to work.
I hope this thread helps somebody else.
I am having the same issue with HTC One.
Could you please let me know how you solved this. Maybe it can help with my device as well. had no luck in our threds..
Thank you
umka83 said:
I am having the same issue with HTC One.
Could you please let me know how you solved this. Maybe it can help with my device as well. had no luck in our threds..
Thank you
Click to expand...
Click to collapse
If you're getting a status 7 error you have to replace the update binary with the latest nightly from cm11 in anything you want to flash. The update binary is universal and will work on anything you want to flash. If it is throwing another error then this won't work.
This will probably only work with cwm or philz.
BadUsername said:
If you're getting a status 7 error you have to replace the update binary with the latest nightly from cm11 in anything you want to flash. The update binary is universal and will work on anything you want to flash. If it is throwing another error then this won't work.
This will probably only work with cwm or philz.
Click to expand...
Click to collapse
Hello, thanks for reply,
1) I am not getting a STATUS 7 error, only this one:
Code:
E: eror eexecuting updater binary in zip /sdcard/zipfilename.zip Error flashing zip /sdcard/zipfilename Updating partition details Failed
Could you please let me know how can I replace the update binary with the latest nightly from cm11? Do you need to open zip from latest Nities and put it into my ZIP?
2) I have tried both cwm or philz and I am getting this error
Code:
this package is for m7wlj devices this is dlx
My device is m7wlj for sure. But somehow recovery thinks it is DLX
THANK YOU
umka83 said:
Hello, thanks for reply,
1) I am not getting a STATUS 7 error, only this one:
Code:
E: eror eexecuting updater binary in zip /sdcard/zipfilename.zip Error flashing zip /sdcard/zipfilename Updating partition details Failed
Could you please let me know how can I replace the update binary with the latest nightly from cm11? Do you need to open zip from latest Nities and put it into my ZIP?
2) I have tried both cwm or philz and I am getting this error
Code:
this package is for m7wlj devices this is dlx
My device is m7wlj for sure. But somehow recovery thinks it is DLX
THANK YOU
Click to expand...
Click to collapse
It's a recovery version problem, so either update your recovery or use an older one until you find something that works.
Problem Solved
umka83 said:
Hello, thanks for reply,
1) I am not getting a STATUS 7 error, only this one:
Code:
E: eror eexecuting updater binary in zip /sdcard/zipfilename.zip Error flashing zip /sdcard/zipfilename Updating partition details Failed
Could you please let me know how can I replace the update binary with the latest nightly from cm11? Do you need to open zip from latest Nities and put it into my ZIP?
2) I have tried both cwm or philz and I am getting this error
Code:
this package is for m7wlj devices this is dlx
My device is m7wlj for sure. But somehow recovery thinks it is DLX
THANK YOU
Click to expand...
Click to collapse
After conducting my own research with this same problem I discovered a much simpler method of correcting the issue. When flashing KK roms with older versions of custom recoveries, the recoveries did not have sufficient instructions to to handle some of the file system changes in KK. I tried replacing the updater binaries from multiple ROMs to no avail. After about 24 hours of trial and error I managed to successfully flash Cyanogenmod cm-11-20140709-NIGHTLY-d801 and GAPPs aokp_gapps-kk-20140517 to my LG G2 D801. All that had to be done is to update TWRP from 2.6.3.2 to version 2.7.1. This version of TWRP had the necessary instructions to support a KK version custom ROM.
Good Job
Sent from my SM-G900F using XDA Free mobile app
Fixed
buhohitr said:
Nice, glad you have a happy ending!!
Click to expand...
Click to collapse
I had same issue, installed newest TWRP. Fixed! Used Odin to install.
I had the same issue as the OP. I was trying to flash a rom from the external SD card. I moved it to the Internal SD and it worked.
J
So i've been trying to put a custom rom on my one s i was trying the source v2 rom with sense 5 i have s-off hboot 2.16 bootloader is unlocked but i do not have supercid as i could not get fastboot to change it and no other options have worked and im not sure if thats apart of my problem im still on the stock rom im not stuck in a boot loop or anything but my internal sdcard space now has a maximum space of 49mb which isnt enough to hold a custom rom im not sure if the hboot has changed the partition when i go to storage in settings it seems as if it has given all my internal space to app storage which i dont know if i can mount that to my pc or not im on the latest twrp recovery and i have tried sideloading a rom but keep getting an error at 10 percent i have not tried any other roms yet. any help would be appreciated
edit: ok i now have supercid and still the same problem
That has to be a firmware problem. I guess you couldn't install firmware correctly. Download installation package from maksimusHD thread, enter bootloader, then ruu mod, flash firmware and flash firmware again immediately when you see the remote:90 error and flash the recovery. After that you should be able to adb sideload source rom
Sent from my HTC One S
ka_55 said:
That has to be a firmware problem. I guess you couldn't install firmware correctly. Download installation package from maksimusHD thread, enter bootloader, then ruu mod, flash firmware and flash firmware again immediately when you see the remote:90 error and flash the recovery. After that you should be able to adb sideload source rom
Sent from my HTC One S
Click to expand...
Click to collapse
Did you ever figure out the answer to your problem? I am having the same issue. To prep for the Maximus ROM I updated to TWRP and flashed the hboot 2.16. Now my phone only sees just under 49 mb of space. I don't have enough space to upload a ROM to reflash. Not sure what to do!
frankienap said:
Did you ever figure out the answer to your problem? I am having the same issue. To prep for the Maximus ROM I updated to TWRP and flashed the hboot 2.16. Now my phone only sees just under 49 mb of space. I don't have enough space to upload a ROM to reflash. Not sure what to do!
Click to expand...
Click to collapse
Try wiping your sdcard via TWRP. That should solve the problem
Sent from my One S
I had the same problem, and I just want back to latest RUU and after that everything was OK.
You can try this if you want.
coma_white said:
I had the same problem, and I just want back to latest RUU and after that everything was OK.
You can try this if you want.
Click to expand...
Click to collapse
I ended up downloading the official tmobile ruu.exe and returning to stock. That fixed the issue. I was then able to successfully install Maximus ROM following the instructions online. Thanks!
frankienap said:
Did you ever figure out the answer to your problem? I am having the same issue. To prep for the Maximus ROM I updated to TWRP and flashed the hboot 2.16. Now my phone only sees just under 49 mb of space. I don't have enough space to upload a ROM to reflash. Not sure what to do!
Click to expand...
Click to collapse
Before to update to hboot 2.16, first time copy maximushd rom to internal card, flash from TWRP, reboot your phone in fastboot, flash the firmware after the guide u have in MaximusHD thread, and after flashing firmware flash TWRP 2.6.1.0 reboot your phone and enjoy.
coma_white said:
I had the same problem, and I just want back to latest RUU and after that everything was OK.
You can try this if you want.
Click to expand...
Click to collapse
can confirm going back to RUU fixes partition problems and probably nearly everything else lol
Hi all, I tried to install this rom without success several times:
"http://download.mokeedev.com/?device=saga&type=unofficial" (I found it her "http://forum.xda-developers.com/htc-desire-s/development/rom-mokee-opensource-project-t2817875")
I downloaded the zip several times and the result is always the same:
"set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard
Error flashing zip 'sdcard/MK44.4-saga-20140722
Updating, partition details..."
I have Team Win Recovery v2.6.3.0 an HBOOT-2.00.0002
I can install other roms like flinny 4.2.2 however with the alpha 5 failure also occurs
Could anyone help me?
Thanks!
You need to update your recovery to flash 4.4 Roms.
Either twrp 2.7 or latest 4ext touch will work
teadrinker said:
You need to update your recovery to flash 4.4 Roms.
Either twrp 2.7 or latest 4ext touch will work
Click to expand...
Click to collapse
Hi, thanks for your answer.
I updated recovery (TWRP 2.7.1.0 from, "http://forum.xda-developers.com/showthread.php?t=2248688") and I get to finish the installation without errors. But I have a new problem, when I reboot the phone, the screen goes black with small flashes (display go off and on at intervals of 3/4 seconds, but always black).
What may be happening now? Is this still a problem caused by recovery?
Thanks
Are u S-On.. if yes Flash boot.img file which came with the zip file... it may help also check if yrs is a hitachi panel, there a thread in development Section for it...
zeus.lny said:
Are u S-On.. if yes Flash boot.img file which came with the zip file... it may help also check if yrs is a hitachi panel, there a thread in development Section for it...
Click to expand...
Click to collapse
Thanks, you were right, I had s-on and therefore I had to use fastboot to flash boot.img, and now runs the rom on my phone and I tested without problems, only minor bugs that comes standard so I will use 4.2.2 because it gives me the feeling that 4.4.4 is still not stable for desire s
Thanks again!
zeus.lny said:
it may help also check if yrs is a hitachi panel, there a thread in development Section for it...
Click to expand...
Click to collapse
What would happen if I have that panel?. Would it affect the performance of the rom?
It wouldn't even boot
It has been initiated MMDI kernel project in HTC Desire S Rebirth Project thread, since then no progress had been made.
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?
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