Clockword Mod I/O Error - HTC One X

I flashed Cyanogen Mod 10.1 beta 5 (latest one when I flashed) on my One X and all was working fine for a few days, then the system randomly shutdown and on reboot got stuck into bootloop. I opened up clockwork mod but occasionally I get this message
Failed to open cache/recovery/log_data
(I/O Error)
Also if I go into "Advanced" and try to mount data, cache, sd card, etc I get an error saying that it can't
This happens around once a day and the only way I can get out of bootloop is to factory reset my phone
I've flashed new roms, even gone back to Android 4.1 but I still get the same error message.
I've reasearched and found nothing on this and have no clue what to do and help will be greately appreciated

You didn't answer me here, or even let me know that you solved. I think that its rude.......are you gonna do the same on this new thread again
http://forum.xda-developers.com/showthread.php?t=2164336
Tried to update the recovery ?

Mr Hofs said:
You didn't answer me here, or even let me know that you solved. I think that its rude.......are you gonna do the same on this new thread again
http://forum.xda-developers.com/showthread.php?t=2164336
Tried to update the recovery ?
Click to expand...
Click to collapse
I looked at newer version of Clockwork mod but didn't know if they were device specific and didn't want to risk flashing the wrong one on my device

Flash this one
http://db.tt/Krlm4dPs
But you must not go into mounts and storage and mount the caches and stuff yourself. No need to do that for anything

Mr Hofs said:
Flash this one
http://db.tt/Krlm4dPs
But you must not go into mounts and storage and mount the caches and stuff yourself. No need to do that for anything
Click to expand...
Click to collapse
There is no harm in manually mounting partitions how the op describes.
I make quite a few framework edits and it can cause problems changing the framework while android is running.
I quite often manually mount system in cwm as its easier than doing "adb shell mount /system"
But for the average user there is little need to do it as the installer scripts automatically mount the partitions that they need
Sent from my HTC One X using xda app-developers app

And thats what i ment. Sorry for the confusion Mr Bag

Mr Hofs said:
Flash this one
But you must not go into mounts and storage and mount the caches and stuff yourself. No need to do that for anything
Click to expand...
Click to collapse
That is the version that I am currently running

Try TWRP recovery maybe. Don't really know what to think of this. When you flash the new recovery also do
Fastboot erase cache

Mr Hofs said:
Try TWRP recovery maybe. Don't really know what to think of this. When you flash the new recovery also do
Fastboot erase cache
Click to expand...
Click to collapse
Edit: reflashed and it worked but I get an error message
E: Can't open/dev/block/mmcblk0p17
(No such file or directory)
E:Can't mount /cache/recovery/command

So you flashed cwm 5.8.4.0 while you where already running that....???
Did a fastboot erase cache ?
Can you give more details
Hboot ?
Version-main ? (Fastboot getvar version-main)
Edit on your edit : it looks like you have some sort of memory corruption .....

Mr Hofs said:
So you flashed cwm 5.8.4.0 while you where already running that....???
Did a fastboot erase cache ?
Can you give more details
Hboot ?
Version-main ? (Fastboot getvar version-main)
Edit on your edit : it looks like you have some sort of memory corruption .....
Click to expand...
Click to collapse
Hboot: 1.39
CID: Orang001
Version-main: 3.14.206
Is there anyway to to fix a memory corruption?

My best guess was a ruu but i can almost say for 99% its not leaked yet.
Can actually still flash a rom ? Or does it stall somewhere in the process ?

Mr Hofs said:
My best guess was a ruu but i can almost say for 99% its not leaked yet.
Can actually still flash a rom ? Or does it stall somewhere in the process ?
Click to expand...
Click to collapse
I've tried looking and all the RUU are for older versions
Phone just rebooted and can no longer access recovery, get a white screen then boots into fastboot
Edit: Rebooted phone and recovery is back working, and just flashed ViperX 3.2.0, but stopped on installing gapps

Tgank you for all your help but I'm going to give up trying to fix it myself and hopefully someone better equipped than me can fix fit

I hope you get it sorted somehow.....as my knowledge stops here too

Related

[Q] please help me error after upgrading hbot

my one x is HTC_622 hboot 1.36
now, my one x cant get into the android
before the error, my one x is android 4.0 custom rom
and i want to upgrade to 4.1
and i tried this one http://forum.xda-developers.com/showthread.php?t=1660807
and i tried http://forum.xda-developers.com/showthread.php?t=2009525
unfortunately, i forgot the ruu will clear my sdcard. and i dont have the zip file in the sd card
i cant trun on my phone into android, so i cant put the zip to sd card
so i run the ruu of radio 2.12 again in order to get back the stock rom
but it failed.
how to slove this problem.
kelvin1hui said:
my one x is HTC_622 hboot 1.36
now, my one x cant get into the android
before the error, my one x is android 4.0 custom rom
and i want to upgrade to 4.1
and i tried this one http://forum.xda-developers.com/showthread.php?t=1660807
and i tried http://forum.xda-developers.com/showthread.php?t=2009525
unfortunately, i forgot the ruu will clear my sdcard. and i dont have the zip file in the sd card
i cant trun on my phone into android, so i cant put the zip to sd card
so i run the ruu of radio 2.12 again in order to get back the stock rom
but it failed.
how to slove this problem.
Click to expand...
Click to collapse
1.Flash custom recovery http://download.clockworkmod.com/rec...-endeavoru.img ( Fastboot flash recovery nameofrecoveryfile.img) make sure youre in fastboot folder.
2.Go to Fastboot mode holding power and volume button simultaneously.
3. Select recovery mode.
4. Go to mount and storage < Mount usb storage.
Copy the ROM of your choice.
5. Flash the boot.img - fastboot flash boot boot.img
Note: Use any custom JB rom of your choice
Hope it helps.
thx
but another problem happened
after i installed viper 3.2, i cant get any phone signal, that means i cant connect to internet wif hspa or cant phone
do you know how to slove this? i cant use viper3.2 in hong kong?
kelvin1hui said:
thx
but another problem happened
after i installed viper 3.2, i cant get any phone signal, that means i cant connect to internet wif hspa or cant phone
do you know how to slove this? i cant use viper3.2 in hong kong?
Click to expand...
Click to collapse
have you flashed the rom's boot.img?
matt95 said:
have you flashed the rom's boot.img?
Click to expand...
Click to collapse
yes, i confirmed twice
kelvin1hui said:
yes, i confirmed twice
Click to expand...
Click to collapse
Try flashing the boot.img only, make sure to clean cache and dalvik cache.
Under mobile network try to do a manual search.
ashishchandra said:
Try flashing the boot.img only, make sure to clean cache and dalvik cache.
Under mobile network try to do a manual search.
Click to expand...
Click to collapse
fastboot erase cache?
kelvin1hui said:
fastboot erase cache?
Click to expand...
Click to collapse
That's always good to do, but Matt means the cache and dalvik cache that you can wipe in the recovery
kelvin1hui said:
fastboot erase cache?
Click to expand...
Click to collapse
yes from fastboot as well as from recovery !!
Hmmm i am starting to lose the confidence in the hboot firmware update. I am seeing more and more reports of this problem. My opinion :
its always the best thing to update officially with a nandroid backup !
This way you avoid radio/ril problems ..... but its to late for that now, the solution ..... I don't have it
Try to flash from scratch again, wipe ALL from recovery even format the sdcard and copy only the rom.zip back on it.
Flash the boot.img and install this script right before you install the rom !
http://db.tt/eLoVUcRc
(Install it the same way as a rom - install zip from sdcard and continue to install it)
Then the rom, and also choose in the aroma full wipe and also very important (this might be the problem!!!) The question about the custom kernel ....choose NO !
You could try getRIL from play store.
Sent from my One X
:laugh::laugh::laugh:
every problem solved now ,after i follow all steps that you guys recommend
now im using viper 3.2 now
i hope i dont need to upgrade hboot again when 4.2 or 5.0 released
Nice !
kelvin1hui said:
:laugh::laugh::laugh:
every problem solved now ,after i follow all steps that you guys recommend
now im using viper 3.2 now
i hope i dont need to upgrade hboot again when 4.2 or 5.0 released
Click to expand...
Click to collapse
Good Luck mate, you will learn a lot from all . :good:

HELP Recovery required

Hi
Have updated to latest jb rom and hboot on 3 (1.39) and decided to try out cm10.1.
Downloaded latest update and didn't realise battery level was lower than I thought.
Ended up using batch to charge up phone and now I cant find a recovery or ruu to restore phone back as shows as a black screen
Have used twrp for jb and a custom made cwm 6 but both have no usb mount facility.
Help greatly appreciated!!!!
passion8059 said:
Hi
Have updated to latest jb rom and hboot on 3 (1.39) and decided to try out cm10.1.
Downloaded latest update and didn't realise battery level was lower than I thought.
Ended up using batch to charge up phone and now I cant find a recovery or ruu to restore phone back as shows as a black screen
Have used twrp for jb and a custom made cwm 6 but both have no usb mount facility.
Help greatly appreciated!!!!
Click to expand...
Click to collapse
Can you access your booloader? If so, and providing that you keep your recovery somewhere on your PC:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
should do the trick.
Recovery problems are mostly solved by erasing the cache
Fastboot erase cache
[email protected]|-|oR said:
Can you access your booloader? If so, and providing that you keep your recovery somewhere on your PC:
should do the trick.
Click to expand...
Click to collapse
can access bootloader but latest cwm 5.8.40 results in blank screen using fastboot erase cache does nothing and there is no jb ruu for H3G_001 that I can find.
Is your screen replaced/repaired ?
Mr Hofs said:
Is your screen replaced/repaired ?
Click to expand...
Click to collapse
yes
Hmm its starting to become a pretty common thing with people who got a screen replacement......
Please search for it ..... there is a whole thread dedicated to this issue
Mr Hofs said:
Hmm its starting to become a pretty common thing with people who got a screen replacement......
Please search for it ..... there is a whole thread dedicated to this issue
Click to expand...
Click to collapse
would u be knid enough to give me an idea what to look for pls?
Can't find it at the moment, and im at dinner
Do a search with the search button.....its there for a reason
Search for black screen recovery.....etc .... etc
Mr Hofs said:
Can't find it at the moment, and im at dinner
Do a search with the search button.....its there for a reason
Search for black screen recovery.....etc .... etc
Click to expand...
Click to collapse
THANKS

[Q] Don't know what RUU to use (softbricked)

Hi everybody,
I'm in deep poop right here.. I messed around with the roms a little bit and now I'm stuck with an ampty sdcard and clockworkmod.
I've tried pushing a rom through adb, but somehow it won't work on my phone/pc. So now I'm planning to go back to stock using RUU.
I've been trying several RUU's, but with no avail. I really don't know what to use right now so I'm asking for your help guys.
Here's some information I got:
CID: HTC__E11 (Dutch)
Main number: 4.18.401.2
Radio-5.1204.167.31
HBOOT: 1.72.0000
I also found this thread: http://forum.xda-developers.com/showthread.php?t=2663718
But I wouldn't have the slightest idea on how to go back to stock 4.1.1. like they suggest here.
Please help me out guys you're my only hope!:crying::crying::crying::crying:
Why don't u this TWRP http://www.androidfilehost.com/?fid=23329332407579463
UMS works, but be patient and wait for a minute or two until it mounts.
Also, this recovery can flash JB and KK roms.
aleksandar.1 said:
Why don't u this TWRP
UMS works, but be patient and wait for a minute or two until it mounts.
Also, this recovery can flash JB and KK roms.
Click to expand...
Click to collapse
Yeah, done that. But unfortunately it's a common One x problem that the touchscreen doesn't work and the version without touch doesn't have the ADB/USBmount capabilities.
I've also been troubleshooting for a few hours on why the ADB doesn't work on my device as well, but again, to no avail.
Installing via RUU is pretty much my only option here I think :/
ogradish said:
Yeah, done that. But unfortunately it's a common One x problem that the touchscreen doesn't work and the version without touch doesn't have the ADB/USBmount capabilities.
I've also been troubleshooting for a few hours on why the ADB doesn't work on my device as well, but again, to no avail.
Installing via RUU is pretty much my only option here I think :/
Click to expand...
Click to collapse
Did u even try the twrp from the link ??? I also have hboot1.72 and touchscreen works.
And you have no ruu for sense 5.
aleksandar.1 said:
Did u even try the twrp from the link ??? I also have hboot1.72 and touchscreen works.
And you have no ruu for sense 5.
Click to expand...
Click to collapse
Sorry man, you're right, I should've tried it.
I just flashed it, but like the last time, the touch screen still doesn't work.
This might sound retarded, but if there's no RUU for sense 5, can't I just use one for sense 4?
Flash this recovery :
https://www.dropbox.com/s/qp21ubo10xetcvn/Philz recovery 5.15.9.img
And then install this rom
http://forum.xda-developers.com/showthread.php?t=1546970
Mr Hofs said:
Flash this recovery :
https://www.dropbox.com/s/qp21ubo10xetcvn/Philz recovery 5.15.9.img
And then install this rom
http://forum.xda-developers.com/showthread.php?t=1546970
Click to expand...
Click to collapse
Will try!
Thanks
I'll give an update once I've done that
Mr Hofs said:
Flash this recovery :
https://www.dropbox.com/s/qp21ubo10xetcvn/Philz recovery 5.15.9.img
And then install this rom
http://forum.xda-developers.com/showthread.php?t=1546970
Click to expand...
Click to collapse
I just flashed the recovery. I try to mount USB storage, but nothing shows up on my computer, the same goes for when I use the comman "adb devices"
Mr Hofs said:
Flash this recovery :
https://www.dropbox.com/s/qp21ubo10xetcvn/Philz recovery 5.15.9.img
And then install this rom
http://forum.xda-developers.com/showthread.php?t=1546970
Click to expand...
Click to collapse
Nevermind, This did work for me!!!!
I just had to give it a little time though
ADB doesn't work but that's got to do with windows 8.1
It also won't recognize the system storage, but it's allright as long as I can put a rom on it now.
Thanks for all the support everybody!
In the Philz recovery I made sure system and sdcard said "unmount" and went into "mount usb"
If you want to get system storage to work or for some reason the mass storage isn't working you should check this out : http://forum.xda-developers.com/showthread.php?t=2232799
I flashed back to clockworkmod to flash a Nandroid backup I found on the internet which can be found here: http://forum.xda-developers.com/showthread.php?t=1975140 (make sure you unpack it when it's in your clockworkmod/backup folder
Yeah i know the collection thread ...... also for the M8 now

modified changes revert back after rebooting the device

my device has been running cm11 unofficial version for quite sometime now.. the 20140921 version.. but recently I've started having a problem that the phone restarts suddenly.. so., i tried doing a fresh flash again.. but i keep getting the assert error. and the phone restarts. I have the recovery image which grarak had posted in the thread. But i donno how to use it. And now the problem has worsened because once I install any new app, the phone restarts on its own and after which it restores it back to the time when the app wasnt there.. I'm not able to make any new nandroid backups too coz the device restarts again.. I thought it might be a CWM error, so I tried flashing TWRP.. but its again an img file which i donno what to do.. sighs. .. and also, if i try to do a fresh flash of the official version of cm11 now, using the recovery i have now, will it show the assert error again?? thanks a lot in advance... hope someone can get me out of this mess..
mids1810 said:
my device has been running cm11 unofficial version for quite sometime now.. the 20140921 version.. but recently I've started having a problem that the phone restarts suddenly.. so., i tried doing a fresh flash again.. but i keep getting the assert error. and the phone restarts. I have the recovery image which grarak had posted in the thread. But i donno how to use it. And now the problem has worsened because once I install any new app, the phone restarts on its own and after which it restores it back to the time when the app wasnt there.. I'm not able to make any new nandroid backups too coz the device restarts again.. I thought it might be a CWM error, so I tried flashing TWRP.. but its again an img file which i donno what to do.. sighs. .. and also, if i try to do a fresh flash of the official version of cm11 now, using the recovery i have now, will it show the assert error again?? thanks a lot in advance... hope someone can get me out of this mess..
Click to expand...
Click to collapse
Download an app called Rashr. It can be used to flash the img file.
FoxyDrew said:
Download an app called Rashr. It can be used to flash the img file.
Click to expand...
Click to collapse
actually this problem is much more serious than that.... my device has kinda frozen in the present state... if i uninstall any apps and then restart the device the app remains there itself.. and if I try to install a new app, after restart, the app is nowhere to be seen.. so, in short, i cant install any new apps or make modifications to the previous ones... I'm not even able to install any other recovery due to this... it seems like there is some problem with the R/W rights.
mids1810 said:
actually this problem is much more serious than that.... my device has kinda frozen in the present state... if i uninstall any apps and then restart the device the app remains there itself.. and if I try to install a new app, after restart, the app is nowhere to be seen.. so, in short, i cant install any new apps or make modifications to the previous ones... I'm not even able to install any other recovery due to this... it seems like there is some problem with the R/W rights.
Click to expand...
Click to collapse
Youll have to boot into fastboot and flash the recovery. Press and hold volume up + power until the phone shuts down, then hold volume down + power until you get into Hboot. Then scroll down with the volume keys and select fastboot.
Check this out for how to flash the img files in fastboot http://androidforums.com/cdma-evo-3...lash-recovery-image-via-fastboot-sd-card.html
FoxyDrew said:
Youll have to boot into fastboot and flash the recovery. Press and hold volume up + power until the phone shuts down, then hold volume down + power until you get into Hboot. Then scroll down with the volume keys and select fastboot.
Check this out for how to flash the img files in fastboot http://androidforums.com/cdma-evo-3...lash-recovery-image-via-fastboot-sd-card.html
Click to expand...
Click to collapse
everything went well during the flashing process.. i had flashed a TWRP img.... but even this didnt solve the problem, even now its CWM as it was before.... Its just as it was before
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 1298444288 bytes
sending 'recovery' (10540 KB)...
OKAY [ 1.528s]
writing 'recovery'...
OKAY [ 0.532s]
finished. total time: 2.065s
mids1810 said:
everything went well during the flashing process.. i had flashed a TWRP img.... but even this didnt solve the problem.... Its just as it was before
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 1298444288 bytes
sending 'recovery' (10540 KB)...
OKAY [ 1.528s]
writing 'recovery'...
OKAY [ 0.532s]
finished. total time: 2.065s
Click to expand...
Click to collapse
Try a clean flash of the official CM11. If that doesn't work, tell me which variant your using.
FoxyDrew said:
Try a clean flash of the official CM11. If that doesn't work, tell me which variant your using.
Click to expand...
Click to collapse
tried that too quite many times.. it shows that "assert error thing", tried it with both the unofficial and official ones, and also I cant factory reset the device, if i do a factory reset and restart without flashing the rom, I'm stuck with the same rom, cant modify it whatsoever...
I'm using the a5dwg dual sim Indian variant
mids1810 said:
tried that too quite many times.. it shows that "assert error thing", tried it with both the unofficial and official ones, and also I cant factory reset the device, if i do a factory reset and restart without flashing the rom, I'm stuck with the same rom, cant modify it whatsoever...
I'm using the a5dwg dual sim Indian variant
Click to expand...
Click to collapse
Use THIS recovery.img file. Flash that in fastboot, reboot into recovery, then do a full wipe (factory reset, cache, dalvik cache, /system, /boot) and reflash the newest official CM11 nightly.
FoxyDrew said:
Use THIS recovery.img file. Flash that in fastboot, reboot into recovery, then do a full wipe (factory reset, cache, dalvik cache, /system, /boot) and reflash the newest official CM11 nightly.
Click to expand...
Click to collapse
this is the error which i get:
Installing update.....
assert failed: run_program("/system/bin/makelinks.sh") == 0
E: Error in / sorage/sdcard1/cm-11-20141025-NIGHTLY-a5_2.zip
(Status 7)
Installation aborted.
mids1810 said:
this is the error which i get:
Installing update.....
assert failed: run_program("/system/bin/makelinks.sh") == 0
E: Error in / sorage/sdcard1/cm-11-20141025-NIGHTLY-a5_2.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Are you sure you flashed the recovery I linked you too. That's the EXACT error you get if you don't flash that recovery.
FoxyDrew said:
Are you sure you flashed the recovery I linked you too. That's the EXACT error you get if you don't flash that recovery.
Click to expand...
Click to collapse
Yes... I had tried using the recovery which you linked.. Is this problem in any ways related to this thread?
http://forum.xda-developers.com/showthread.php?t=2707378
I tried to add the wp_mod.ko file too... but there's no folder called as "modules" in the bin folder...
I feel its because of some problem with the read write issue.. since I'm not able to bring about any change in the system whatsoever except for changes made in the sd card.. they all get reverted after the reboot
mids1810 said:
Yes... I had tried using the recovery which you linked.. Is this problem in any ways related to this thread?
http://forum.xda-developers.com/showthread.php?t=2707378
I tried to add the wp_mod.ko file too... but there's no folder called as "modules" in the bin folder...
I feel its because of some problem with the read write issue.. since I'm not able to bring about any change in the system whatsoever except for changes made in the sd card.. they all get reverted after the reboot
Click to expand...
Click to collapse
In CM you can read and write to everywhere with no problem. You problem is weird, flash a RUU.
hmm...cant find a RUU for my variant though...
mids1810 said:
hmm...cant find a RUU for my variant though...
Click to expand...
Click to collapse
Well, try this Philz recovery, its the same one I'm using, and flash the newest build, which is the same one I'm using. If that doesn't work I honestly don't know what to tell you.
FoxyDrew said:
Well, try this Philz recovery, its the same one I'm using, and flash the newest build, which is the same one I'm using. If that doesn't work I honestly don't know what to tell you.
Click to expand...
Click to collapse
the same as before... cant get out of CWM..
mids1810 said:
Yes... I had tried using the recovery which you linked.. Is this problem in any ways related to this thread?
http://forum.xda-developers.com/showthread.php?t=2707378
I tried to add the wp_mod.ko file too... but there's no folder called as "modules" in the bin folder...
I feel its because of some problem with the read write issue.. since I'm not able to bring about any change in the system whatsoever except for changes made in the sd card.. they all get reverted after the reboot
Click to expand...
Click to collapse
@mids1810
Ok let's see, so your saying that the device won't allow to read or write, meaning 1 of 2 things.
Either you lost root access by uninstalling or modifying something, or
your device has accumulated too much background information / app data and it won't allow it to make any more changes due to limited or in other words, there's no space.
If you have CWM 6.0.4.7 then you will get the assert error every time. This is just to make sure you do have it flashed.
First thing's first.
-Go into your bootloader and go into fastboot mode. Plug it into the PC and it will say fastboot USB.
-Now download and run this .exe:
https://www.dropbox.com/s/7nn4a5xzx2pw7as/CWM_Recovery_en.exe?dl=1
-This will flash the latest 6.0.5.1 CWM automatically.
1. Now that you have the latest recovery installed,
-Boot into the recovery and wipe the CACHE and go into advanced options and wipe DALVIK CACHE. Do not press factory restore.
-Hit reboot device and test by installing an app to see if this fixes the issue.
2. If it still reboots after installing an app then download this .zip:
http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip?retrieve_file=1
-Put this zip on your SD card/internal storage
-Go into CWM and flash this .zip.
-Reboot the device and test again.
3. If BOTH of these steps failed then you will need to freshly install CM11.
-While the device is still on, put the latest CM11 on your device or recycle the same one that your using if you prefer its stability.
-Boot back into CWM and do a factory restore.
Factory restore is almost ALWAYS necessary for every time you flash CyanogenMod unless it is an update that specifically states it can be "dirty flashed" which is just a way of saying you flashed it without wiping all your information - data/cache/dalvik off of it.
Let me know how this goes for you. :laugh:
jaysoblitzed said:
@mids1810
Ok let's see, so your saying that the device won't allow to read or write, meaning 1 of 2 things.
Either you lost root access by uninstalling or modifying something, or
your device has accumulated too much background information / app data and it won't allow it to make any more changes due to limited or in other words, there's no space.
If you have CWM 6.0.4.7 then you will get the assert error every time. This is just to make sure you do have it flashed.
First thing's first.
-Go into your bootloader and go into fastboot mode.
Yeah i already had the CWM 6.0.5.1 running on my device, but I flashed it again just in case.... That didnt solve the issue.
Next I flashed the Super SU zip from my SD card(since anything I place in my internal storage vanishes once I reboot... even if rebooted in my recovery) That again didnt solve the problem
I did a fresh install of CM11, 20140921 which I am running at present due to the stability issue you mentioned.. (have tried with the official nightly a couple of times to no avail)... It shows the assert error just as before, all the time.
And yes, all the apps I uninstalled came back again, as always Completely out of any more ideas... And also I get quite many error messages often " so and so app stopped responding" and stuff
Click to expand...
Click to collapse
mids1810 said:
jaysoblitzed said:
@mids1810
Ok let's see, so your saying that the device won't allow to read or write, meaning 1 of 2 things.
Either you lost root access by uninstalling or modifying something, or
your device has accumulated too much background information / app data and it won't allow it to make any more changes due to limited or in other words, there's no space.
If you have CWM 6.0.4.7 then you will get the assert error every time. This is just to make sure you do have it flashed.
First thing's first.
-Go into your bootloader and go into fastboot mode.
Yeah i already had the CWM 6.0.5.1 running on my device, but I flashed it again just in case.... That didnt solve the issue.
Next I flashed the Super SU zip from my SD card(since anything I place in my internal storage vanishes once I reboot... even if rebooted in my recovery) That again didnt solve the problem
I did a fresh install of CM11, 20140921 which I am running at present due to the stability issue you mentioned.. (have tried with the official nightly a couple of times to no avail)... It shows the assert error just as before, all the time.
And yes, all the apps I uninstalled came back again, as always Completely out of any more ideas... And also I get quite many error messages often " so and so app stopped responding" and stuff
Click to expand...
Click to collapse
Did you try wiping JUST the Cache and the Dalvik cache WITHOUT doing a factory restore? These options are in CWMR.
Also, what is your device model? (a5_dug/chl/dwg/ul etc.)
If your not sure it says it at the top when your in the bootloader.
Click to expand...
Click to collapse
jaysoblitzed said:
mids1810 said:
Did you try wiping JUST the Cache and the Dalvik cache WITHOUT doing a factory restore? These options are in CWMR.
Also, what is your device model? (a5_dug/chl/dwg/ul etc.)
If your not sure it says it at the top when your in the bootloader.
Click to expand...
Click to collapse
yeah.. I did try.. without any difference in the results.
My device is the a5dwg dual sim Indian variant
Click to expand...
Click to collapse
jaysoblitzed said:
mids1810 said:
Did you try wiping JUST the Cache and the Dalvik cache WITHOUT doing a factory restore? These options are in CWMR.
Also, what is your device model? (a5_dug/chl/dwg/ul etc.)
If your not sure it says it at the top when your in the bootloader.
Click to expand...
Click to collapse
Follow this guide and restore your phone back to stock.
http://forum.xda-developers.com/desire-816/general/rombackup-t2811252
Its an TWRP nandroid backup of the original software, and if you have an updated version it will be able to update as well if you flash the stock recovery.
Click to expand...
Click to collapse

Cannot mount system/cannot install rom

I just recently got an HTC one m7 that I've fully unlocked, s-off'd, and rooted and now when I try to install a Rom it fails or I should say it hangs on 1% never advancing. Furthest I've gotten is 7% on santod's nusensesixMAX Rom but it wouldn't finish. Is it my recovery? I'm on the latest TWRP. Anyone with any input please
Have you tried the No data Wipe RUU and see if it takes?
No I haven't
I would suggest doing that RUU. it is the one @dottat made where he says it will not wipe SD card that way you do not lose anything on the card. If it is a borked emmc chip and needs fixing, Dottat has some tricks up his sleeve that may work.
What's really weird is every time I boot into twrp I'm having issues with mounting system.
Do u have a link I can't seem to find it
eriknors said:
What's really weird is every time I boot into twrp I'm having issues with mounting system.
Do u have a link I can't seem to find it
Click to expand...
Click to collapse
Thanks to dottat!!!! It's here: http://forum.xda-developers.com/verizon-htc-one/help/exe-ruu-vzw-m7-4-4-3-s-users-t2919442
eriknors said:
What's really weird is every time I boot into twrp I'm having issues with mounting system.
Do u have a link I can't seem to find it
Click to expand...
Click to collapse
Update your twrp recovery to the latest. That is why system won't mount in recovery.

Categories

Resources