Related
So I've had two incredible's now fall in to a boot loop
(wiped, pulled battery, RUU'd, went back to s-on - nothing worked)
first one I had for about 8 months with no issues until now. they did
send me a replacement XD and it did the same thing!
Now my wifes phone is doing it :\
I'm just verifying - if I RUU/S-on/remove sd card - then it HAS to be a hardware issue right? nothing that I could have done?
[Further info if needed]
All had CWR 3.0.0.5 and were rooted via unrevoked
h0x90 said:
So I've had two incredible's now fall in to a boot loop
(wiped, pulled battery, RUU'd, went back to s-on - nothing worked)
first one I had for about 8 months with no issues until now. they did
send me a replacement XD and it did the same thing!
Now my wifes phone is doing it :\
I'm just verifying - if I RUU/S-on/remove sd card - then it HAS to be a hardware issue right? nothing that I could have done?
[Further info if needed]
All had CWR 3.0.0.5 and were rooted via unrevoked
Click to expand...
Click to collapse
Were you using the same ROM or kernal each time?
It's the new cwm. It uses a different gscript setup. To a restore or flash incredible reengineered 2.3.1
If not that then I don't know. Did it happen after a Rom flash?
Sent from my Incredible using XDA App
well the first one was running Evervolv and had been for about 3 weeks.
it crashed during a phone call and never booted all the way again. (boot loop)
The second (This ones replacement) was running cm7 (Flashed it right as I got it) and worked fine the first day I had it (but I wasn't using it much that day) then it died while using the browser and fell victim to boot loopage.
The third one (my wifes phone) died about an hour later while using the browser but would still boot - but not stay on for very long. Especially if any sort of data was going on (like syncing with gmail). I figured since it was kind of working maybe it was the rom so I flashed s-on went back to stock 2.2 (ruu) where it now dies upon lock screen.
(or before sometimes)
[Ninja edit] Wifes phone had been running evervolv the amount same time as my first phone
all three were running latest CWM and had the default kernel for the rom they had. Also all 3 were flashed ruu and s-on including a clear storage for good measure (Verizon also had me do a factory reset come to think of it - before they would ship replacements)
Ianxcom said:
It's the new cwm. It uses a different gscript setup. To a restore or flash incredible reengineered 2.3.1
If not that then I don't know. Did it happen after a Rom flash?
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
could cwm leave something behind that would continue the boot loop after ruu?
That would suck because I've already sent in one phone would hate for them
to find something like that ><
have you tryed downgrading? i know i was having alot of issues with the new cwm. im running chingys rom and after the downgrade everything is running smooth again. cwm 2.5.1.2 seems to be working better...
HandsomeRob2310 said:
have you tryed downgrading? i know i was having alot of issues with the new cwm. im running chingys rom and after the downgrade everything is running smooth again. cwm 2.5.1.2 seems to be working better...
Click to expand...
Click to collapse
I've went complete stock everything (including recovery) and it didn't fix anything.
Have an update on the situation as well.
Verizon shipped me another 2 phones - both broken out of the box.
The first one just reboots over and over again and can't even enter recovery.
On the second device the speaker is blown -.-
Are you using the same or different SD card(s) amongst these failing devices?
The one you had running for 8 months, was that SD card at end of life?
Asking, as AOSP ROMs interact quite a bit more w/ the SD card than do Sense ROMs, so if your issues are all with AOSP ROMs, I suspect wonky SD card(s).
smtom said:
Are you using the same or different SD card(s) amongst these failing devices?
The one you had running for 8 months, was that SD card at end of life?
Asking, as AOSP ROMs interact quite a bit more w/ the SD card than do Sense ROMs, so if your issues are all with AOSP ROMs, I suspect wonky SD card(s).
Click to expand...
Click to collapse
I got that SD back when I got the phone so I hope its not
at the end of its life span.
I've actually didn't bother putting the SD cards in this last batch
because they were showing issues immediately (without any modding)
Thanks for the info on AOSP roms that could help diagnose future problems
That would explain a lot, actually, as AOSP ROMs call the sd during boot.
Sent from my ADR6300 using XDA App
Whatever I try, using System Recovery/Clockwork Recovery, when I boot up the phone it's still UK 3.4.3-11 Froyo, but now with a red motorola logo (Nordic firmwire I flashed I suppose) .
When wiping in recovery I get these errors: "can't mount /dev/block/mmcblk0p2 (File exists)" and "error mounting /sd-ext/!".
I've create a FAT (should this be FAT32?), Ext2 and Linux Swap partition on my SD Card.
My original aim was to install CM7 from Quarx. Here's what I did:
Stock Defy UK (Other than root)
Used clockwork recovery to wipe and update to CM7
Booted fine (CM7/2.3), tried to then install gapps as an update.zip, then got stuck on boot at "M" screen on every boot
Used RSD lite to flash 3.4.3-11 UK with Blur
Superoneclick etc., tried to install CM7 again, had no effect
Used RSD lite to flash 3.4.2_177 Nordic - comes up with red logo, but hasn't updated to the actual blurless froyo
Tried again to install CM7, had no effect, still have the 2 errors on wiping
I've also found that when using stock recovery, it no longer does anything when I press the bottom right of the screen, it just stays at the green robot screen, I have to remove the battery.
I did get an app2sd error, which was why I partitioned the SD card using Clockwork recovery (bad move?), I then did it on my PC instead with an SD card adapter.
The phone's not bricked, since I've got a working 2.2 rom, however I've no clue what I've done to make it like it is now, and I can't install CM7 using clockwork recovery and the default recovery doesn't work.
I think fixing those errors might do the trick? Any help would be appreciated.
I am also not able to install quarx rom, tried several times it does not boot and I had to reflash the sbf to get the phone working. Btw I do no have sd partition.
What I did was from cloclwork I tried restore, shall it be install from zip. No idea why I cannot get it running. I have nordic 005 at the moment
Sent from my MB525 using XDA App
...maybe you guys should start to read a little more before attempting flashing any ROM...
If you would have done that, maybe you would have noticed that some people warned about some mounting of the SD card problems in some instances (I don't remember the specifics at this time..I beleive had to do with Super1click version used to root)
And most importantly:
that for CM7 installation instructions ask you to use '2ndinit' recovery and NOT CWM.... In fact you should even avoid having CWM recovery installed before starting the process...
I'm a noob too guys, I sometimes appreciate the help I can get from a post here. But I try my best to find existing answers and read as much as I can on the subject first. Obviously, you guys did not do your homework on this one.
[] AL [] said:
...maybe you guys should start to read a little more before attempting flashing any ROM...
If you would have done that, maybe you would have noticed that some people warned about some mounting of the SD card problems in some instances (I don't remember the specifics at this time..I beleive had to do with Super1click version used to root)
And most importantly:
that for CM7 installation instructions ask you to use '2ndinit' recovery and NOT CWM.... In fact you should even avoid having CWM recovery installed before starting the process...
I'm a noob too guys, I sometimes appreciate the help I can get from a post here. But I try my best to find existing answers and read as much as I can on the subject first. Obviously, you guys did not do your homework on this one.
Click to expand...
Click to collapse
I did in fact read around before I started, obviously in the wrong places or not enough. I've been pretty naive but all the guides I saw recommended that recovery, I must have missed the posts about 2ndinit (which sounds a lot easier). In fact I hardly read the actual CM7 thread since it's around 190 pages long.
It's interesting you noted superoneclick as the first time it worked and I used z4root.
I think for now I'll just use what I've got, which is ultimately better than what I started with (2.1), it's just a bit worrying as those errors I'm getting seem to suggest I've messed up the internal storage; and the default recovery won't work.
Probably installing a beta CM7 wasn't the best idea anyway since I'm very new to this.
Thanks al
I tried with cw recovery only. Tonight will try with 2ndinit. my sys info nordic 177_005 will I be able to get beta4 straight installing the zip
Sent from my MB525 using XDA App
Hi al[]
I tried booting into 2nd init boot but nothing comes up. Just blank screen any idea
Sent from my MB525 using XDA App
binodnepal said:
Hi al[]
I tried booting into 2nd init boot but nothing comes up. Just blank screen any idea
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Have you read this one:
http://forum.xda-developers.com/showthread.php?t=1043420
and for the recovery:
http://forum.xda-developers.com/showthread.php?t=1032212
Other than that, I will leave it to others to guide you on this...they'll do a better job than I would.
Sorry if I sound/ed rude in my post above...but was before 1st coffee of the day
Last note: on my side, I'm waiting (more or less) patiently...
As seen here http://forum.xda-developers.com/showthread.php?t=1033654&highlight=CM7
CyanogenMod 7 for Motorola Defy
Status Beta4:
Works:Wifi, SD-Card, 3D, Auto-Brightness, LED, Photo Camera with Flash, Video Camera(H264), GSM/3G, Bluetooth +Headset + HID, Sensors, GPS(have bugs)
Not works: aGPS, FM-radio, 720p & WVGA Recording.
BugList:
- some people say that they have wifi problems <---
- DroidWall/Iptables - not work <--- <--- <---
====>>>> So I will wait for that "tiny detail" [DroidWall/IP Tables] to get fixed before testing out any CM7 on my phone.
I like DroidWall apk and I also like to have a relative control on which app can access the internet...
Some of my apks 'might' not be so 'official' [..let say] and who knows what kind of party they're having in my phone....
I got it working and its quite fast. GPS works for me. Camera photo works but not the video. Will test other later. Quadrant score is very high not sure if it is correct. I got 2200
Sent from my MB525 using XDA App
Anyone having issues with music player stopping after few songs in cm7 beta4
Sent from my MB525 using XDA App
Seen this yesterday. Anyone use it yet? Goods/bads?
http://www.androidpolice.com/2011/0...to-5-roms-on-one-device-flashaholics-rejoice/
I would sooo use that but I'm too cheap(internet broke) to buy that. I've always been plagued with having to choose a rom. I end up sticking with one for a while. Like just today I went to MIUI after a month of Synergy.
EDIT: I might be getting this app soon
Sounds like the devs on the app are committed to helping their customers iron out the kinks. When I get my evo back from being flashed I am going to install it and post back to this thread. Thanks for the heads up.
Just installed decks and the express roms.
Booted in to decks, set it up, no issues. The first boot seems to take a while.
Now switching to express.
UPDATE 1 -
After switching to the express rom, I was not really able to use the rom. I decided you pull up the application to switch back to the phone rom.
The application kept force closing. It did this on the phone rom and decks.
I then followed the instructions to flash the update.zip file to get back to the original rom. Now Im stuck on the bootloader screen. When the phone reboots it comes right back to the bootloader.
UPDATE 2 -
Wiped the cache, delvik and rebooted same issue.
Reflashed the phone rom - same issue.
Wiped the cache, delvik, reflashed the phone rom, rebooted - same issue
Wiped the cache, delvik, flashed decks from rom1, rebooted - BACK IN BUSINESS.
It seems that the initial phone rom is corrupt.
UPDATE 3 -
Trying to get back to the original rom from decks.
Went back to BootManager, selected phonerom from the list of installed roms - same issue as before.
Followed the same steps as in update 2 and Im back in decks
I hope to get a chance to email the developers. Takes hours for it to "load" a rom. Then when I try to run it, I get an error saying that the rom is not there. Very annoying. Nothing has worked on it yet. Waste of money thus far.
Sent from my PC36100 using XDA Premium App
Sent an email, hope to get an answer back soon. Has the app worked for anyone?
Sent from my PC36100 using XDA Premium App
I have tried 2 different synergy ROM's and have yet to be able to boot into either. After the install process I try to boot into them and it gives a boot.img failed to flash error. Click on the ROM's individually gives a message that there is no ROM installed in the slots.
No response from my email yet, hopefully we can get some answers.
I gave it a try, installed and loaded a rom, it was so slow, I could have flashed n restored back to my original rom 10x it took for this app to do it, it worked the way it was supposed to but takes to long
Sent from my PC36100 using XDA App
I tried it for about 10 mins could not get it to work just FC's so hit refund.
Not so sure if its the ROM im running but was not happy with it
Sorry for the delay. After several emails to and from the developer, I flashed CWM recovery :shutters:. I tired to manually restore just the boot.img of the phone rom and still no luck. I then tried using adb to manually insert the boot.img into the nand as the developer instructed. This still did not work. I uninstalled and politely asked for a refund that was granted.
Its a great idea, just needs more work on the original backup of the phonerom, apparently this is a known issue. I lost everything (my fault I know, but i was excited) but I did like decks so much that I flashed it as my daily rom.
I e-mailed their support staff on Saturday evening & got a response on Sunday, which impressed me, so I thought I'd share with you guys what they said.
When trying to install a Synergy Rom, I got the message asking whether this ROM was sd-ext2 or sd-ext4, & never could get them to install (which I'd assume is b/c they all run using ext3), so I shot over an e-mail asking if they had any advice, & here was their response.
Currently apps2sd or data2sd will not work. If you are somewhat savvy with this stuff you can move the files that would go on the sd-ext back to the system or data folder in the zip where they should go. Then make your system.img size big enough to hold all the files of the bigger rom in menu/settings/manually set variables. I'm working on some solutions to do some of this automatically for some of the devices.
Click to expand...
Click to collapse
ncadden said:
I e-mailed their support staff on Saturday evening & got a response on Sunday, which impressed me, so I thought I'd share with you guys what they said.
When trying to install a Synergy Rom, I got the message asking whether this ROM was sd-ext2 or sd-ext4, & never could get them to install (which I'd assume is b/c they all run using ext3), so I shot over an e-mail asking if they had any advice, & here was their response.
Click to expand...
Click to collapse
That being said, which ROM's are supposed to work then? I wish I would have gotten a reply to my email. I still haven't heard anything back from them.
ncadden said:
they said....
When trying to install a Synergy Rom, I got the message asking whether this ROM was sd-ext2 or sd-ext4, & never could get them to install (which I'd assume is b/c they all run using ext3), so I shot over an e-mail asking if they had any advice, & here was their response.
Click to expand...
Click to collapse
I have dta2sd and not about to spend time to undo that for this app. However I hold out hope that they will support a2sd in the future (since i bought it... LOL). And I think that they should state that fact up front in the app description.
On the other hand I'd pay/support somebody $3 to develop this kind of app. There are so many cool ROMS out there that I'd love to try out.
Right now I am running MIUI latest and love it.
I have no problem paying for apps. I only ask for the simple things like the app working properly. I have yet to recieve an email from the developer. I hope that they see this thread. Actually, I may send this link to them. I read somewhere that one of the developers is on XDA.
I just want a working app, or a refund. I don't think that is to much to ask.
*edit
Here is the auto-response I just got.
This is an automatic email sent from [email protected] Emails about unsupported devices will no longer receive answers we are receiving too many emails to reply to these if you have a device you would like supported please submit it to http://init2winitapps.com/submit_device.html and support will be added as soon as possible thank you for the continued interest in boot manager and we look forward to supporting your devices. Having issues? check out the manual while you wait for our reply it is located at http://init2winitapps.com/stories/BMManual.html Issues will usually receive replies that day if it has been a few days and you have not received an email we may have missed you so send a friendly reminder Thank you for the continued support in boot manager Init 2 Winit Apps
Whelp no luck. Few emails back and forth. Not working on my phone. Hopefully they get it working. Refunded.
Sent from my phone using XDA Premium App. Blah
I bought this app...
I bought boot manager two days after release and I have had no real problems yet, I flash a new test ROM almost every day. At first I had some "user errors" and twice on the first day I had to flash the phoneROMs update.zip b/c I forgot that CM needed a flash of google apps... and the app CANT run without authentication from the market... ("Herp DERP")
other than that, I've seen some ROMs run slow. but I figured that was b/c they where sense based and running from the sdcard.
Anyone know how to flash kernels?
Sent from my PC36100 using XDA Premium App
Best app so far. Love it. Triple booting synergy rls1 as phone ROM with salvagemod and cm7 in slots. It only takes about a minute to switch between roms too.
There was a thread that got moved to q&a for reason, and the developer did respond.
Will try to flash kernel tomorrow
FYI - I could not get synergy + godmode to work. Without GM works fine
Sent from my PC36100 using XDA App
alaman68 said:
Best app so far. Love it. Triple booting synergy rls1 as phone ROM with salvagemod and cm7 in slots. It only takes about a minute to switch between roms too.
There was a thread that got moved to q&a for reason, and the developer did respond.
Will try to flash kernel tomorrow
FYI - I could not get synergy + godmode to work. Without GM works fine
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
agreed. best app.
Although not officially supported for the Droid Incredible 2 (not even on the list), it seems to work! Messing around with it now, but I was able to boot OMGB without any issues. Still some things that I need to figure out though, particularly with the GAPPS..
Sorry if this is a stupid question, but what is boot manager?
Sent from my ADR6350 using XDA App
ExNight said:
Sorry if this is a stupid question, but what is boot manager?
Sent from my ADR6350 using XDA App
Click to expand...
Click to collapse
Not a stupid question at all! Basically, allows for dualbooting your phone. Right now, I'm currently running RMK's GingerSense on the phone, and working on dual booting (well, up to 4 other ROM's) OMGB and OMFGB. Playing around though, since they don't officially support it...nor unofficially for that matter.
Not for the feint of heart at the moment though. To get back to the phone ROM, you have to use recovery to flash the backup of boot.img. Read what to do in the market app description.
is this a phone app or computer app...i wanna try it on the blown out dinc2 i gotta send bak
Sent from my ADR6350 using Tapatalk
Pay for play phone app. Works well so far too.. Root is required though.
Been bouncing back and forth between GingerSense (on the phone) and OMGB (SD) all night.. Surprisingly fast even on stock microSD. As far as I can tell, everything seems to be working properly, but that isn't to say there isn't any underlying bugs. Very nice though being able to dual boot like that. My only concern though is how fast the microSD could die because of all the reads/writes.
This is very interesting. I would love to hear more reports for those who have tried this. Gingersense is my daily driver, but I would like to keep a CM7 build up to date simultaneously.
Sent from my ADR6350 using XDA Premium App
Damn! I was looking forward to this when I had my rooted Inc2, but now I'm stuck with it's replacement that's GB If anyone has a friend or knows someone that has an XTC Clip near Pasadena/Burbank/or San Bernadino County PM me!
Seems to work well so far. They are having issues with Sense-based ROMs running off the SD card though. I tried installing rmk's GingerSense a few times, was never able to get it to boot. AOSP ROM's seem to work just fine though.
sk0t said:
Seems to work well so far. They are having issues with Sense-based ROMs running off the SD card though. I tried installing rmk's GingerSense a few times, was never able to get it to boot. AOSP ROM's seem to work just fine though.
Click to expand...
Click to collapse
I was using it on my Inc and Sense 2.x roms ran okay, it was just the Sense 3.0 roms that had trouble. MIUI also ran very well. it is a great tool.
caleris said:
I was using it on my Inc and Sense 2.x roms ran okay, it was just the Sense 3.0 roms that had trouble. MIUI also ran very well. it is a great tool.
Click to expand...
Click to collapse
I only tried one Sense ROM, but it would freeze. Talked to one of the devs, and they were also having issues with other HTC devices and Sense. Sounds like they may have it fixed though for the next release, but I won't say that with any certainty.
Tried 1.3 which officially supports Inc 2, but couldn't pass the boot.img installation. Hmmmm
xHoLyx said:
Tried 1.3 which officially supports Inc 2, but couldn't pass the boot.img installation. Hmmmm
Click to expand...
Click to collapse
Same here. Idk what's up either.
Sent from my Incredible 2 using XDA App
Bootmanager
Guys if it's failing to make the boot.img first make sure your using the market version....others have released cracked versions of our app which they broke...if your using the actual market version just send me a pm or email [email protected] and send your log.txt from BootManager folder on sdcard and we'll get it straightened out. Thanks.
Damn! Wanted to buy it but I only have 2.50 on my debit card :/ Anychance of a sale sometime soon?
Definitely make sure you guys are getting in touch with their devs.. They've been real responsive for me.
I am using bootmanager v1.3 on an htc incredible 2 & I am having problems installing the google addons
After loading cryanogenMod 7.1 into slot 1 & booting into that just fine, I open ROM manager & dl the google addon for cm 7.1 then boot into recovery to load the addons, I can find the addons in the download folder & i select it but it never flashes & I dont have the market to authenticate bootmanager or put my apps on the cm rom & have to load the original phone image back on
Do I need to put google addons zip on the root of the SD card & flash it from there?
Thanks
Don't flash GAPPS from within Recovery.. Flash it from within BootManager itself. I do it right after installing the ROM I'm putting into whatever slot I'm putting it in. If you flash from Recovery, it flashes it to the ROM on the phone itself.
Thanks sk0t,
The bootmanager support emailed me back within 10 minutes, I emailed them then posted here.
Everything is working great now.
Here is what the developer wrote "You need to flash google add on's or any other ad on's from with in the
bootmanager app. Recovery will only affect your phones rom. The
bootmanager app is the "recovery" for all sd rom's. When flashing
something like gapps you flash it just like you flashed the rom only DO
NOT select any of the wipe checkboxes."
On my way to the market now to give app a review, 5 stars, ultra fast support, would have developers back in a bar fight!!!
Thanks again
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