I'm currently running cherryblur 0.4
I have atrocious touchscreen issues with the screen sometimes locking up and not registering my touches. Vice versa with my buttons as well.
I noticed this problem on kenneth's gingerbread beta as well. Could it be something to do with the PDS partition? I have a back up saved on my desktop.
Should I try flashing back to stock first?i never had these issues until I flashed the gingerbread betas.
Thanks
Sent from my semi de-blurred atrix using telepathy and Tapatalk
I get this problem also
I do not get these issues. I flashed stock .img files first then installed Kenneth's beta 4.
Related
How I got to this...
Rooted
Wiped,,,wiped davlik.
Installed stock N1 rom.
Installed MT Update.
Installed highmem kernel update.
Ever since then Im getting random reboots.
Ive been able to replicate the reboots when downloading podcasts via app or videos via browser.
Can anyone give me a clue as to what may be going on ?
I dont know how to work logcat to get a txt file so I pasted a screen cap.
I opened up doggcatcher and commensed update. Then crash.
I had the same issue happen after i installed the himem with the new update from MoDaCo. Mine rebooted when i copied around 50megs+ to my storage card from the computer.
I wiped, installed Enomthers Official then flashed the himem kernel with no problems.
Yep, me too . But I can only see the problem when copying large files from my SD.
I had the issue of random reboots before, but thats not happening very often since Google's latest update.
I want to know how to get rid of the HIMEM bootloader now. Any ideas ?
Guys.....any replies regarding this is really appreciated !!
I really need to know how to get rid of the freakin HIMEM bootloader, I cant copy new music to my phone this way.
Please let me know which bootloader to use now, since im on the latest update from google with a stock rom.
Im using enom with high-mem and no problems at all
Wiped reflashed with newest Modaco.
Formatted sd card.
Now I have issues with Gallery lol. No super steady Roms yet I gues.
not having any of these problems at all with Cyan's Beta4. No reason for me to try b5 since there isn't anything wrong with b4. I would say try and flash Cyan's B5 or download B4 and see if that fixes your guys problems.
Prod1702 said:
not having any of these problems at all with Cyan's Beta4. No reason for me to try b5 since there isn't anything wrong with b4. I would say try and flash Cyan's B5 or download B4 and see if that fixes your guys problems.
Click to expand...
Click to collapse
I also have Cyanogen's beta 5 with no problems whatsoever! Works and runs great!
I had issues with both recoveries now so which one is everyone using? I am currently using CM3.05 or something like that and I tried restoring a backup and it freezes on the startup screen. So I'm a little irritated now and am wondering what everyone is using and if they're having problems.
Used to just backup and no matter what happened do a restore and no problem...
Moved to general
Shouldn't be in development...
Sent from my PG06100 using XDA App
Bahhh I'm slow...
I've got the same question. Clockwork isn't fully functional and there's the annoying bug that doesn't let you charge your phone when it's off.
This in addition to the fact that the Wimax keys don't get backed up automatically and that no one seems to know how to restore the Wimax keys when they are backed up manually is why I am holding off on flashing roms for now. I am real happy just having my phone rooted though.
Been using CW 2.5 with no problems. It will boot into recovery when plugged in with the phone off but you quickly learn to just deal with it. I've backed up and restored at least a dozen times already without any errors.
^ Shift Faced
I can also add that I've been using 2.5 and created several backups and restored successfully as well as flashed bc's oc kernel successfully. I've only heard bad things about v3+.
2.5.x.x. because that's what is in the "official" rooting thread.
It really depends. You will need to use 2.5.xxx for any Sense based 2.2 ROMs and 3.0.xxx for any GB based ROMs.
Thanks all! 2.5 is working good for me. It even restored my 3.0.5 backup when 3.0.5 wouldn't.
OK, so I am new to the epic 4g (it belongs to a friend, I have a cappy). I've flashed to stock, upgraded to E05, rooted with the latest one-click, and all that goes perfectly!
When I install bonsai 4.0.1 the installation goes flawless, but on bootup it keeps doing the FC vibrate and boot loops. I've tried 3 fresh installs but I am getting nowhere. I have also tried it doing the 3x wipes and without. I'm familiar with odin, so I know it's not something there. Any thoughts?
Having the same issue. Sadly.
*One thing I'll note is to ensure you are using ClockWorkMod 3, not 2.5. Wanna make sure you have the correct file type (EXT4).
I have tried to install Bonsai 4.0.0 & 4.0.1 multiple times and have had the same boot loop issue.
I love the Bonsai (3.0) Rom, which worked just fine w/ EB13, but has not worked at all since upgrading to EC05. I want to keep EC05 as bluetooth actually works.
I always odin back to Stock DI18 and update to EC05, then root using CMW 3, wipe date/cache/dalvik 3X, then install Bonsai 4 (and 4.0.1 one another attempt). The install seems to be successful, but I end-up stuck in the boot loop. I tried to re-flash the ROM after netting the bootl oop, but it errors-out in CWM.
Any ideas are greatly appreciated. I am crazy frustrated as there must be something simple I am missing...?
If you follow the instructions exactly you can't go wrong. Forget what you think you know. Bonsai is totally different than other roms out there...
Sent from my SPH-D700 using Tapatalk
I was having problems after installing bonsai, force closes, no call sounds, ect. I copied all the files on the sd card to pc and formated th sd card. I only put the bonsai rom on the sd card and then flashed. Put files that I wanted back on card after and everything is great. If all else fails try it, I have seen it work on several different epics.
Sent from my Premium Epic, bliatch.
Aron1980 said:
OK, so I am new to the epic 4g (it belongs to a friend, I have a cappy). I've flashed to stock, upgraded to E05, rooted with the latest one-click, and all that goes perfectly!
When I install bonsai 4.0.1 the installation goes flawless, but on bootup it keeps doing the FC vibrate and boot loops. I've tried 3 fresh installs but I am getting nowhere. I have also tried it doing the 3x wipes and without. I'm familiar with odin, so I know it's not something there. Any thoughts?
Click to expand...
Click to collapse
Did you update to EC05 with the "over the air" update? If so, there has been a lot of issues with that.
Yes, best to go back to eb13 prerooted with CWM3 and then go to Bonsai.
So am I reading that Bonsai 4 is incompatible w/ EC05?
I have gotten Bonsai up an running while on EB13, but no such luck since upgrading to EC05. I am not using the OTA update.
I have also heard that there may be issues w/ CWM 3 and EC05?
Any insights?
mrjuboy said:
I have gotten Bonsai up an running while on EB13, but no such luck since upgrading to EC05. I am not using the OTA update.
I have also heard that there may be issues w/ CWM 3 and EC05?
Any insights?
Click to expand...
Click to collapse
Bonsai 4.0.0+ is a EC05 ROM. It uses Framework and kernel source of EC05(heavily modded of course just like the other EC05 ROM's). But I too have been reading many reports from folks having issues flashing ROMs from stock EC05. Not sure if Sprint/Samsung has thrown some kind of roadblock in there or if it's something we are missing here, but it doesn't matter how you get there. If you are on EB13 when you flash Bonsai 4.0.1+ it will update the modem for you, so it's not necessary to be on EC05 when you flash the ROM.
As far as CWM goes, the Epic community is in need of an official version of CWM 3.
I got it to work!
Odin'd back to stock, completed stock upgrade to EB13, then installed CMW 3 and flashed Bonsai 4.0.1.
I did have to reflash Bonsai once in CWM, but I am now up and running on Bonsai 4.0.1 on the EC05 Kernal and loving it!
Thank you very much for your assistance.
I flashed the Deodexed .596 onto my phone back when it came out. Is there anything newer to flash too? I have constant problems with .596 it is terrible, it lags like crazy, will literally stop responding to my inputs for 30 seconds randomly reboot it just never ends.
I do use Launcher Pro and have nothing but problems sometime I will go to my app drawer and it will be empty etc. I have had to put some of my shortcuts on my main screen since sometimes I cant get them from app drawer. Half the time when it boots it crashes LP and Force Closes it.
Any help would be great.
The latest OTA version is .605.
I would recommend SBFing to .596 (just to be safe) then taking the OTA. This will make sure that everything is right where it's supposed to be.
Sent from my DROIDX using XDA App
The newest sbf is actually 602... You can do that... And no real need to ota to 605... In my opinion anyways... because the only real difference is a keyboard fix for the stock keyboard
Post script: 602 is way better then 596... I wasn't able to stand that build... Or even the roms that were based off of it
We have nothing to feat but running out of beer
Is there a Rom I can flash to get to .602?
If you have either premium versions of Rom Manager or Rom Toolbox from the android market...
There are .zips to take you from any kernel up to .602.
You'll have to do that or SBF to 602 (my recommendation) before flashing any 602/605 based rom.
hi again guys as you have prob' seen in my last post i recently updated to the v7 bootloader and 1.7thor recovery.
since i updated the bootloader, ive had a few probs like the unreadable files showing up in my internal memory, my sd card deleting most of it contents, google play showing tracks i no longer have on the tablet.
i have also noticed that google music has begun to flash/glitch and last night g-music totally blacked out my screen after a load of flickering i was worried but the tab seemed to work fine just the app went crazy.
another issue is i tried to install a game (nova 3) and when i clicked install it said i did not have enough memory,,....but i have 22gb free?
so i tried another .apk and installed fine,.. could it be the .apk thats the problem? its just weird because you would think the game just wouldn't play, not give insufficient memory warning before installing?
another question i have is, if i made a nandroid backup using the teamwin recovery 2.x can i restore the nandroid that ive flashed the thor 1.7 recovery?
flexreaper R12.5
v7 bootloader skrillax
1.7 thor recovery
version?
I am not sure if the version of flexreaper you have installed supports the ICS bootliader...? Are you?
m.
You need to update your rom, you are about 20 revisions old and I don't think you have the right boot.img installed to make your bootloader compatible with the FR 12.5 rom you are running. You should have stuck with the HC bootloader if you are using such an old rom.
cruise350 said:
You need to update your rom, you are about 20 revisions old and I don't think you have the right boot.img installed to make your bootloader compatible with the FR 12.5 rom you are running. You should have stuck with the HC bootloader if you are using such an old rom.
Click to expand...
Click to collapse
i was on v2 ics bootloader before? and civato recommends using a ics bootloader for flexreaper? also the boot.img was replaced by civato .....sooooooooo i dunno?
note/update:
i found the files in the internal it was in a download folder from torrentz4android, i deleted them and got all space back and play music now displays all the correct information had to delete a lot individually . the nova 3 install problem was found to be a glitch with ICS actually , i cleared dalvik-cache and the apk install no problem
update
ok i seem to still be experiencing problems from the touchscreen once becoming unresponsive to apps freezing and my back/home buttons disappearing?
can using a new bootloader produce these problems or could it be a bad titanium backup?
hope this information helps others who come by this problem.