Related
For the past 5 months I have been using cm7 with no problems. But in the last month or so problems have been slowly coming up. It started with phone freezes then it slowed down greatly, then I got fc on EVERY APP! So then I switched to synergy hoping to fix the problems but there still there. I need help quick because I can't even make calls with out it freezing.
Sent from my Synergy Rom using XDA Premium App
monkey10120 said:
For the past 5 months I have been using cm7 with no problems. But in the last month or so problems have been slowly coming up. It started with phone freezes then it slowed down greatly, then I got fc on EVERY APP! So then I switched to synergy hoping to fix the problems but there still there. I need help quick because I can't even make calls with out it freezing.
Sent from my Synergy Rom using XDA Premium App
Click to expand...
Click to collapse
have you wiped everything (data, cache, dalvik) in recovery BEFORE flashing?
I just went through the same thing with the stock rom (rooted without the verizon crapware).. Had it since Day 1 of availability.. then a few days ago.. force closing all the time..
Even when switching roms. Even when NOT restoring with titanium.. Did everything fresh (ugh.. you have no idea how many hours).... and photos were disappearing from it
My first thoughts were "frak... I really screwed up something" (my niece dropped in on the floor a few days earlier.)
Then the IT in me decided to fall back on my experience. K.I.S.S. (keep it simple stupid).....
If even changing roms didn't fix it.. what did everything have in common? The SD Card.
So I formatted the card making sure to take everything off I needed. Put it back in.. and put a fresh rom on.
No problems since. I'm guessing the file system of the SD card went a little wonky after a year of putting files on.. taking off.. putting on.. etc
Yep I cleared everything, data, cache
D cache and batt stats. Im going to try the SD card thing right now
Sent from my Synergy Rom using XDA Premium App
Just gonna throw this out there. Try also formatting /system in the "mounts and storage" menu.
So far so good. The SD trick worked. But I want to put my titanium backup folder back on my SD card to get my apps back but I am not sure if that was the problem.
Also about the format /system l, I was thinking about that too. But if I can't get things working in the end I will format the system, data and cache.
Sent from my ADR6300 using XDA Premium App
monkey10120 said:
So far so good. The SD trick worked. But I want to put my titanium backup folder back on my SD card to get my apps back but I am not sure if that was the problem.
Also about the format /system l, I was thinking about that too. But if I can't get things working in the end I will format the system, data and cache.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
Glad it worked.. after 3 very frustrating days for me and trying multiple roms and losing a few pics... glad I was able to at least past the info on to someone else
I am having this problem now with apps that are not installed on my SD card (which I just upgraded to larger size). All the Google apps are fc and some other ones here and there.
Were the fc apps all installed on SD?
I was thinking about a fresh gapps flash but may try the SD card first.
sent from my Dinc running CM7
Glad I found this thread! I've been having same problem and couldn't figure out if it was a rogue app or not. It seemed like right after I flashed a new rom it would run great but after a few days I would start having trouble and eventually I'd have to flash another new one or try same one again.
I have a question though....I know most things on sd card are ok to delete since any app will put new folder on there if it needs to (obviously keeps pics, titanium backups, rom backups etc.)
But I don't have a way of formatting the sdcard OUTside of the phone. I don't have a card reader on my computer. Would it be ok to do this while the phone is plugged in? (something tells me no but...)
My only other option would be to put the sdcard in my old HTC ozone and try it that way...
You can just plug your phone into your PC, mount your SD card and reformat it that way. It works for me.
jackbtha1 said:
You can just plug your phone into your PC, mount your SD card and reformat it that way. It works for me.
Click to expand...
Click to collapse
This ^^
OR
Random thought
You can try to repair the SD card before you format( if the repair doesn't work). Mount SD card to the computer via usb. Right click, properties, tools tab. Run error check. Just like a computer files get corrupted.
Sent from my ADR6300 using XDA Premium App
Hey all,
So I've had these problems for a while now (noticed it ever since I rooted a year ago) but they haven't really mattered before, as I am now trying to update my radio.
Issue one:
When I boot into HBOOT, the green text "SD Checking" takes FOREVER. Like a minute and a half going through each one. I've seen other G2 go through this dialog and its always instant for others.
Issue two:
When I actually have the PC10 whatever zip on the sd card root, it doesn't see it - this may be a function of the next issue though.
Issue three:
This happens probably 1/3rd of the time I boot into recovery. Whether using 4ExT or cwm (both the stable versions), occasionally recovery is unable to mount E:/sdcard. Reboot usually fixes this. Never have I ever had a problem accessing my sdcard from running my rom, no matter how many reboots I go through.
Can someone help me fix at least 2 or 3? Not sure what's happening. I have s-off, cid 11111111 and have flashed custom roms via recovery with no problems (aside from the cannot mount sdcard error pretty often) dozens of times.
Thanks much so!
Sent from my T-Mobile G2 using xda premium
Herro? Anybody?
The pc10whatever(haha) is on root of sd card not a folder called root right?
I'm not talking smack lol just want to make sure.
Also why do you want to change radio?
Sent from my HTC Vision using xda premium
Spastic909 said:
The pc10whatever(haha) is on root of sd card not a folder called root right?
I'm not talking smack lol just want to make sure.
Also why do you want to change radio?
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Hahaha yeah it's on the root of the sd card, not a folder called root - probably should have been more specific there.
I get a lot of echoes on G-Lite 2.0.1 b/c I am not on the recommended radio for that rom, so I am changing radios to recommended one!
However I just used fastboot instead to take care of it and now no more echoes! But I'd still like to know what's up with my hboot and recovery!
seems strange to me, id say if your worried just reflash your hboot and recovery and hope it fixes this. personally i skip the recovery almost altogether, fastboot is safer and fastboot wipe is cleaner then any superwipe.zip out there. i come from the land of the g1s and we were screwed on fastboot flashing ever since the updated spl came out and we couldnt use fastboot to flash anything! im much happier now
captainreynolds said:
Hey all,
So I've had these problems for a while now (noticed it ever since I rooted a year ago) but they haven't really mattered before, as I am now trying to update my radio.
Issue one:
When I boot into HBOOT, the green text "SD Checking" takes FOREVER. Like a minute and a half going through each one. I've seen other G2 go through this dialog and its always instant for others.
Issue two:
When I actually have the PC10 whatever zip on the sd card root, it doesn't see it - this may be a function of the next issue though.
Issue three:
This happens probably 1/3rd of the time I boot into recovery. Whether using 4ExT or cwm (both the stable versions), occasionally recovery is unable to mount E:/sdcard. Reboot usually fixes this. Never have I ever had a problem accessing my sdcard from running my rom, no matter how many reboots I go through.
Can someone help me fix at least 2 or 3? Not sure what's happening. I have s-off, cid 11111111 and have flashed custom roms via recovery with no problems (aside from the cannot mount sdcard error pretty often) dozens of times.
Thanks much so!
Sent from my T-Mobile G2 using xda premium
Click to expand...
Click to collapse
I had a similar problem with my sdcard taking forever to read and it turns out that my fat32 partition on the sdcard wasn't aligned properly so I had to reformat it. That could be the cause of a couple of your problems
Sent from my HTC Desire Z using XDA
This is a very sad story about my NoteII going bad.
I would describe myself as computer savvy and moderately experienced with Android. I equipped half of the family with various ROM-customized Android phones and am an enthusiastic Note user since it came out in 2011. Until now, I never had to ask a question in the forum.
Let me start in December 2012 when my NoteII arrived. I updated it, then came cwm and the monxdified ROM. For about a month I was a very, very pleased NoteII user.
Then, one day in Mid-January, I installed an app called "(root) Uninstaller pro", which began to auto-backup up all my apps to internal SD in a background process while I didnt notice. I only realized something had gone wrong when apps began to FC because no space was left on sdcard0. I removed the app and all the backups.
From the day after that , Play Store began to "randomly" refuse to update or install apps, because of "Not enough storage space available". Which was bull****. I literally had Gigabytes of free space on internal and external storage. For example, Play Store would refuse to update my tiny TB Pro key apk for "Not enough space" reasons but then happily install Asphalt7 and update Titanium Backup and Dolphin for me. Moreover, every affected app also does not install "manually" from apk. When removed, it can not be reinstalled, except via update.zip from the recovery.
Of course, I googled the error. I found no root cause explanation, just a bunch of hints. I deleted all app data from play store and various store-related apps. I deleted and re-setup my Play Store account. The usual suspects, cache and dalvik, got their wipe. Nothing helped. I downloaded the latest monx ROM and updated it from TWRP. Problem still there. Then my job required my full attention so I left the thing running with only partial updates for several weeks. After all, it still worked petty well.
Then, lately, I decided to tackle the issue again. I went to Settings and did a full factory reset WITH internal SD reformat. In TWRP, I did another factory reset and full wipe, then I flashed the latest (DMB2) monx ROM and restored from my TB backup.... "Not enough storage space available".
A friend suggested I should try "Fix permissions". Boy, what a bad Idea. From that moment, LBE Security guard caused a Hot Reboot every time I tried to use Active Protection. Many resets and wipes later, it still does today. I can only install it via update.zip, though, not properly reinstall it: "Not enough storage space available".
But all this still is only the beginning. I decided it was time to clean up the mess and factory resetted again (no SD wipe this time, after all it didnt help last time), took good old ODIN and completely reflashed with Stock XXDMB2. Result: Boot Loop. TWRP told me "cannout mount /data" and claimed internal and external SD to be empty (which was not the case). So I reverted to cwm6 and did a fullwipe/reset. Only after that, the newly flashed Stock DMB2 suddenly booted. I went on and reinstalled monxdified DMB2 (the very same zip that had worked before!). But regardless of what I tried, all I got was another boot loop.
Back to Odin, Stock again. This time (and every time after) it booted right away without needing help from cwm, BUT on the very first GUI ("choose country") it told me that UIDs were wrong and suggested to reformat /data. Wait, wasnt that what Odin just did? Instantly after this error, com.google.gapps did an FC. CWM to the rescue. This time, "fix permissions" seemed to actually fix them.
To make this long story a bit shorter, I reiterated though quite a number of futile attempts to install a booting custom ROM until 2am, and failed. Now I am on Stock DMB2 with a non-working LBE and only a handful of the most important apps restored. The "Not enough storage space available" problem is still here.
I wonder how the "Not enough storage" problem was able to survive so many flashes and resets. I am utterly helpless about how a Stock ROM, flashed from Odin can expose UID problems and FCs on first boot. Could this be a sign of a malfunction on the internal flash storage? If so, how would I be able to find out? Or could it be that this "uninstaller" did something nasty to the secure storage system of JB (which I dont have any idea of how it works and what it needs at all), at a point that all my wipes and flashes did not actually reach?
What else could I do to really, really reset every possible bit on this otherwise wonderful piece of hardware and possibly get rid of all those pesky problems (and back into a Custom ROM)?
Please help me to make this baby shine again!
Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Ive read your story and i feel really bad for you. Good luck m8, if I had some knowledge id help you for sure but im new to android ) goodluck! Dont give up x
Sent from my GT-N7100 using xda premium
Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Do a mega wipe with recovery. Then install stock rom and nothing else. Don't restore stuff. Instead download them from play store.
Sent from my GT-N7100
Re: MegaWipe
UtkarshGupta said:
Do a mega wipe with recovery. Then install stock rom and nothing else. Don't restore stuff. Instead download them from play store.
Click to expand...
Click to collapse
Ok. So I found MegaWipe and put it on my SD-Card. I started it and the aroma Installer presented to me the Mega Wipe Option which I chose. A text screen appeared which said, that several partitions had been wiped but it happened in less than a second which I foudn to be suspicious. Then, when tapping "Next" again in the MegaWipe Aroma Tool, I found out Aroma was frozen and the recovery system did not react to any key press or tap anymore. I had to press the Power button for a while to get back into recovery where I flashed a ROM, then rebooted.
Guess what: all my apps were still present, the SMS history and Launcher fully intact. Dalvik had been wiped apparently (all apps re-optimized), though, and my Wifi AP settings were gone. Of course, the "not enough memory" problem is still here, too!
It appears like whatever problem I have, it also prevents me from using MegaWipe properly. Any more ideas?
Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Try again.
Sent from my GT-N7100
Re: MegaWipe
UtkarshGupta said:
Try again.
Click to expand...
Click to collapse
Tried again. Twice. Internal SD contents were gone. Froze again after "Installation complete". Maybe that "Mega Wipe" took two seconds instead of one this time. The second time I tried flashing Omega after the wipe just for the kicks and that (full wipe Option in Aroma) apparently took my user data away, finally.
To my not-so-big surprise it greeted me with "Inconsistend System UIDs" right after startup, completely with the gapps FC I had already seen with stock so many times, now. This does not feel like real progress.
I have read around a bit. Maybe I should try to flash a multipart ROM in Odin with repartition? Appears to be pretty dangerous, though, and I dont know where to find one that matches my "DBT" CSC properly...
Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Flash latest stock rom for your country.
Sent from my GT-N7100
Flashing stock that wipe ur internal and format sdcard.
Some stock rom dont wipe fully internal thus issue still exist even u flashing stock rom.
Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
u use CWM? i had a problem with cwm if i use aroma it always freeze use a other recovery and do the megawipes?? iam not very good at this but i wish you all the luck ..
Sent from my GT-N7100 using xda app-developers app
Re: MegaWipe
UtkarshGupta said:
Flash latest stock rom for your country.
Click to expand...
Click to collapse
XXDMB2 *is* the latest Stock ROM for my country. In my first post I described how I flashed it and it did not work out very well.
nameejokerx said:
Flashing stock that wipe ur internal and format sdcard.
Some stock rom dont wipe fully internal thus issue still exist even u flashing stock rom.
Click to expand...
Click to collapse
Yes, and which one would be such a ROM? I was not very adventurous with ROMS until now and did never flash multipart ROMs. I am afraid bad things could happen if I flash something with wrong CSC. Where exactly should I look for such a ROM and what do I have to take care of? Of course HOWTO pointers are welcome, too.
Sorry if this sounds too clueless but I really dont want to make things even worse.
Maybe SDS
Hi all,
after some more wiping and flashing, fiddling and tiddling and basically reinstalling everything from scratch, mostly without help from Titanium, I got my NoteII back to work. I only restored my most important app data, all apks reloaded from play store instead from backup, made several backups with twrp during this process. Two times, the "no space" problem came back and both times I basically reverted back to the last working backup from twrp. This way, I managed to turn it back into a usable system.
Not for long though, because two hours ago, in the midde of buying an ebook in kindle, my NoteII screen went black and now the whole thing is completely dead. I took out the battery for 10 minutes, but it won't come back on again; not even a download screen or battery loading animation.
So my problems might just have been the harbingers of its future death. I just read that "SDS" also affects some Note2 models and it has something to do with the internal storage which would be sort of a match for the symptoms I experienced. Looks like I'll have to send it in. Because of all the flashing and restoring I had not yet encrypted my internal storage and will have to change all passwords. Duh
I really should have stayed with my trusty old Note1 which never failed on me...
I have an ongoing issue with Galaxy W phone and CM.
The problem is that the phone spontaneously decides to not boot.
I had run CM10 from first Alpha, and on a couple of occasions it would, after several days or weeks use, stay on the CM spinning logo, and refuse to go to interface.
I got around this by keeping a couple of Nandroids handy and just restored them when the boot issue occurred.
On subsequent fresh install, I ran for a couple of weeks with virtually no app installations, to see if something I was running was causing the issue. Turns out no relationship.
I have just flashed Alpha 7 of CM 10 and now its doing it again. This is a fresh install.
I re-downloaded the ROM from the second mirror, and tried flashing with that, but get the same result.
Is it possible the flash memory in my phone is faulty? On a PC if you install an OS - fresh install - and it wont boot, generally its either RAM or HDD. Given this is a recurring issue, I wonder if its the phone, rather than the OS thats causing the problem - as I have tried with several of the Alphas and both download locations of the most recent Alpha and its still happening.
Can anyone suggest?
Is there a chkdsk option for phone flash memory?
thanks
Jim
[edit] just installed CM9 (last beta) and its doing the same thing - stuck at boot animation and will not get to desktop.
Anyone? Any ideas how to fix this?
Sv: [Q] CM10 A7 ongoing boot issue
Flash stock rom and see if the problem still exists. If not, flash cm again. If it does, get a new phone.
Sent through time and space from my s3mini.
16kzx81 said:
I have an ongoing issue with Galaxy W phone and CM.
The problem is that the phone spontaneously decides to not boot.
I had run CM10 from first Alpha, and on a couple of occasions it would, after several days or weeks use, stay on the CM spinning logo, and refuse to go to interface.
I got around this by keeping a couple of Nandroids handy and just restored them when the boot issue occurred.
On subsequent fresh install, I ran for a couple of weeks with virtually no app installations, to see if something I was running was causing the issue. Turns out no relationship.
I have just flashed Alpha 7 of CM 10 and now its doing it again. This is a fresh install.
I re-downloaded the ROM from the second mirror, and tried flashing with that, but get the same result.
Is it possible the flash memory in my phone is faulty? On a PC if you install an OS - fresh install - and it wont boot, generally its either RAM or HDD. Given this is a recurring issue, I wonder if its the phone, rather than the OS thats causing the problem - as I have tried with several of the Alphas and both download locations of the most recent Alpha and its still happening.
Can anyone suggest?
Is there a chkdsk option for phone flash memory?
thanks
Jim
[edit] just installed CM9 (last beta) and its doing the same thing - stuck at boot animation and will not get to desktop.
Anyone? Any ideas how to fix this?
Click to expand...
Click to collapse
What do you mean by clean install?
wipe data and cache?
Try to format /system /data /cache and /sdcard (backup your internal storage first)
MiguelPT said:
What do you mean by clean install?
wipe data and cache?
Try to format /system /data /cache and /sdcard (backup your internal storage first)
Click to expand...
Click to collapse
Thanks guys, very much for your replies
By "clean install" I have gone to wipe menu of CWM and wiped everything, then CM with wipes, then Gapps.
Ok so I need to try to flash with stock ROM. I had considered that but could not find an Australian ROM in the I8150 section of the Forum. Can anyone tell me where I can get one from?
- or -
-- maybe its ok to flash with any English ROM - will achieve the same thing? - sorry if this is a dumb question - I just dont want to make the situation any worse
Try Removing all SD Card,SIM and battery. Then reinsert battery after 15 minutes and reflash the CM10/Stock ROM. It will boot up
miki2o said:
Try Removing all SD Card,SIM and battery. Then reinsert battery after 15 minutes and reflash the CM10/Stock ROM. It will boot up
Click to expand...
Click to collapse
Ok. Thanks for the suggestion. I did that and its stuck on the Logo still. No change.
You can get stock ROM for Australian (Vodafone) from here http://www.hotfile.com/dl/187592956/3abb3c5/I8150TDULM1_I8150TVAULG1_VAU.zip.html
arya_ruby said:
You can get stock ROM for Australian (Vodafone) from here http://www.hotfile.com/dl/187592956/3abb3c5/I8150TDULM1_I8150TVAULG1_VAU.zip.html
Click to expand...
Click to collapse
Thanks very much for the link I have downloaded it
So I noticed something else thats kinda weird.
When I go to /sdcard, its not showing the content of the sd card
So if I swap out the card, it still loads the same folder, not the stuff from the sd card I have inserted.
I have a few of these. All read fine in the PC, but the phone does not seem to recognise the files, as they dont change if I reboot with a different card/different content in.
/sdcard
Code:
../
.android_secure/
Android/
LOST.DIR/
RZR/
Video/
cm-10-2013~ancora-alpha7.zip
gapps-jb-~signed.zip
SD card contents when read from PC
Code:
I8150TDULM1_I8150TVAULG1_VAU.zip
Its as though it has a partition called /sdcard, and can't mount the content of the physical card itself. Anyone seen this before? Is there a way to re-partition internal memory?
16kzx81 said:
Thanks guys, very much for your replies
By "clean install" I have gone to wipe menu of CWM and wiped everything, then CM with wipes, then Gapps.
Ok so I need to try to flash with stock ROM. I had considered that but could not find an Australian ROM in the I8150 section of the Forum. Can anyone tell me where I can get one from?
- or -
-- maybe its ok to flash with any English ROM - will achieve the same thing? - sorry if this is a dumb question - I just dont want to make the situation any worse
Click to expand...
Click to collapse
Just do full wipe you'll not wipe cwm!
My suggestion: Go the Pristine™ Way.
(thread in the General forum)
Sent from my GT-I8150 using xda app-developers app
arya_ruby said:
You can get stock ROM for Australian (Vodafone) from here http://www.hotfile.com/dl/187592956/3abb3c5/I8150TDULM1_I8150TVAULG1_VAU.zip.html
Click to expand...
Click to collapse
I tried that zip, but it started to install and the phone shut down/restarted at beginning of install (just after wipes)
Can anyone else confirms this file actually works?
Is there a Tread source I can refer to?
pepoluan said:
My suggestion: Go the Pristine™ Way.
(thread in the General forum)
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the suggestion. I tried but the problem persists.
Hey guys,
For months now, I've constantly been chopping and changing the ROM around on my DHD, without any issues. All ROMs used to install without errors, and they would all boot to a usable level.
Recently, for the past week or 2, I have only been able to successfully install JellyTime 4.2.2 R11.
Every other ROM I have tried (and trust me, I've tried a fair few), all successfully install, but then become frozen at the boot HTC logo.
I have had a look around the forum to find a solution to this, however most issues similar to this seem to be S-ON, or an issue installing all ROMs.
I am yet to find someone with the same issue as I am having, making it super difficult to find the solution.
That's where you guys can come in...
I'd really appreciate the help. I've just this week turned down the offer of the HTC One, on favour of keeping my now 3 year old DHD, and I'd love to be able to keep modding it for years to come.
So please, help me to have some more fun with my DHD before they finally are obsolete..
Sent from my Inspire 4G using xda app-developers app
Go to the Recovery and wipe then install the rom again
Gesendet von meinem HTC One X mit Tapatalk 2
Alkerino said:
Hey guys,
For months now, I've constantly been chopping and changing the ROM around on my DHD, without any issues. All ROMs used to install without errors, and they would all boot to a usable level.
Recently, for the past week or 2, I have only been able to successfully install JellyTime 4.2.2 R11.
Every other ROM I have tried (and trust me, I've tried a fair few), all successfully install, but then become frozen at the boot HTC logo.
I have had a look around the forum to find a solution to this, however most issues similar to this seem to be S-ON, or an issue installing all ROMs.
I am yet to find someone with the same issue as I am having, making it super difficult to find the solution.
That's where you guys can come in...
I'd really appreciate the help. I've just this week turned down the offer of the HTC One, on favour of keeping my now 3 year old DHD, and I'd love to be able to keep modding it for years to come.
So please, help me to have some more fun with my DHD before they finally are obsolete..
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
Some of the sense ROM's come with kernels that can be flashed only with s-off.
otherwise, make sure you use 4ext recovery.Wipe all except sdcard, then go to the tools menu and format>ext4 menu>wipe data, system,cache, all with ext4.I've had an issue again with CWM/TWRP, where it gave me Encryption Unsuccesful error on boot, and it did so on every ROM onwards.Switched back to 4ext, all is working fine.
In the long run, the S-Off is worth it.
I've tried that. A fair few times...
I've wiped and formatted /system, /data and /cache, as well as wiping the dalvik cache before clean installing each ROM.
I have quite the OCD when it comes to residual files and such, so I wouldn't dream of installing a ROM without a full wipe first.
For me, this still wouldn't explain why I can still install JellyTime without any issues. If anything, JellyTime is working better than any of the previous ROMs I've tried, I'd just like to open up the possibility to explore further..
Is it likely to be a problem with the SD card? The one I'm using is as old as the handset (3 years), and I've named this as the cause of some alight lag issues in the past, but I've never come across this problem before...
Nothing against the ROM, but I wouldn't want to be stuck on JellyTime indefinitely..
Sent from my Inspire 4G using xda app-developers app
Steam. said:
Some of the sense ROM's come with kernels that can be flashed only with s-off.
otherwise, make sure you use 4ext recovery.Wipe all except sdcard, then go to the tools menu and format>ext4 menu>wipe data, system,cache, all with ext4.I've had an issue again with CWM/TWRP, where it gave me Encryption Unsuccesful error on boot, and it did so on every ROM onwards.Switched back to 4ext, all is working fine.
In the long run, the S-Off is worth it.
Click to expand...
Click to collapse
Yeah, I'm on S-Off (Altogether, this seemed like the simplest Root form when I first began exploring, and I've kept it that way since).
But I'm having the same issue when I try to install ROMs that I've used without problems before, on the same handset, so I can't understand what's changed?
Sent from my Inspire 4G using xda app-developers app
Alkerino said:
I've tried that. A fair few times...
I've wiped and formatted /system, /data and /cache, as well as wiping the dalvik cache before clean installing each ROM.
I have quite the OCD when it comes to residual files and such, so I wouldn't dream of installing a ROM without a full wipe first.
For me, this still wouldn't explain why I can still install JellyTime without any issues. If anything, JellyTime is working better than any of the previous ROMs I've tried, I'd just like to open up the possibility to explore further..
Is it likely to be a problem with the SD card? The one I'm using is as old as the handset (3 years), and I've named this as the cause of some alight lag issues in the past, but I've never come across this problem before...
Nothing against the ROM, but I wouldn't want to be stuck on JellyTime indefinitely..
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
Hi I got the same problem six months back. I format the SD card then I tried to install other ROMs. It was successful. So try Good Luck.:good:
UPDATE - After trying over 10 different ROMs without success, I resigned to buying a new SD card, eventually deciding that this simply MUST be the source of the problem.
I bought a new 32GB SD, partitioned it, and flashed a ROM at random.
No issues at all.
I've tried a fair few since, including ones I had problems with before, all without any trouble whatsoever
Cheers for your help guys!
Sent from my Desire HD using xda app-developers app