Related
(Yes I know clean isn't spelled with a K)
Well, I've been working on my personal ROM for quite a while now, since there isn't much out there for us VZW users, I've decided to share. This might work on sprint, but I haven't tried. Sprint users should stay away unless they really know what they're doing. As normal, it's not my fault if you fubar your tab by flashing this or if zombies come and speedhump your cat. You've been warned.
Preamble
1. Don't ask me on how to install koush's recovery, that's what his thread is for. Laymen's terms- Did you do THIS? If you did, you're good to go, if not. do it.
2. I am not going to teach you how to use, or set up the applications that you need to use/flash this. I have included links to everything you need to know, just click and read for a second. If you are not willing to put out a little bit of effort to better your experience with your Tab, I am not going to waste even more of my time that could be dedicated towards making my ROM better. Also, if you aren't willing to give yourself the fundamental knowledge required for flashing this and something goes wrong, you will then have the required skill to fix it, instead of blaming me for bricking your Tab. I don't need that. I am willing to support my ROM and help with some confusion, but if you want me to do everything for you- lo siento.
About This ROM
There's not too much to say about it. It's DJ11 with almost 100MB of bloat ware, Verizon/Samsung crap and worthless other nonsense pulled out and the good bits updated with parts of the EURO updates/dumps. I have also done some other mods and optimizations.
Features
Updated Samsung apps from newer GSM ROMS! (The only way you can currently experience the updates on your CDMA device)
Deodexed
Zipaligned
Ad blocking hosts
Screen density of 180 (you can fit more stuff on the screen. Change with build.prop edit or LCD Density changer)
Transparent Notification bar
Gingerbread launcher
Minimal Touchwiz integration
Custom notification and ringtones (a la The PHJC)
More! (Really, there is more, but I can't think of it right now, I'll edit this post as I remember)
Installed Apps
3G Mobile Hotspot (wifi needs it to work)
Browser
Calendar
Camera
Chrome to Phone
Contacts
Email
Gallery
Gmail
Google Search
Latitude
Maps
Market
Connected Music Player (from Motorola, it's sweet)
Navigation
Places
Spare Part
Superuser
Talk
Task Manager
Titanium Backup
Video
Voices
Voice Search
Youtube
Removed
Verizon Boot Animation (That's why all you see is a black screen on first boot, just wait. I'm working on a custom one right now.)
Touchwiz Launcher!!!
Accessibility features. Note: you can still manually download them from the market.
lot of other crap, I can't remember, blockbuster, games, it goes on. I pulled out almost 100MB of apps, unneeded audio files, apps and such.
Changelog
v3 - Installation Update
Not much has actually changed about this ROM, I started to theme it, I stopped, I need to replace the zips with the stock again
CWM flashable zip install method has been uploaded for ease of flashing
v2 - Application Update
Lots of apps integrated from the GSM JMI Dump from Rotohammer. As usual I have deodexed and zipaligned the apks. There are some nice updates in the task manager, Contacts, Calendar, email and several other apps.
v1 - Initial Public Release
I was having some core issues with previous versions, but I've been running for well over 12 hours now without a problem.
If people paying for the data plans would report back to confirm all wireless cell activity still functions, that would be great (I only use wifi, but my VZW location service still works, so your data should too).
Known Issues
The notification/ringtones are duplicated in the selection windows, don't know why but there are no redundant files.
You will get core FC's and FC's in contacts, calendar and email until your Twitter/Facebook/Gmail accounts are fully synced, this is normal. Just give it a couple hours to fully sync (or turn up the sync interval to speed up the process).
If you are having any issues with the ROM loading on the first boot (it shouldn't take more than 4 minutes at the black screen) Turn the Tab off by holding down the power button until it powers off (9 seconds or so), Boot into recovery, select advanced --> reboot recovery. Once the secondary recovery loads, select format/factory reset and reboot.
Set picture as lockscreen wallpaper doesn't work.
Plans
I don't know, it's fast right now. Probably just more streamlining, accurate battery mod, shutdown options and a theme are all on the list too. This is really just to get me through until I finish some other things. You can make requests, but don't expect me to listen to them. I'm just sharing the ROM I've made for myself, so it is, and always will be, configured the way I like it. There's always the random good idea though. Let me know if you find any serious bugs too please.
Installation
Download the VZW bootstrapper or manually CWM your Tab (instructions HERE)
Download ROM
Factory Reset (BACK UP YOUR DATA FIRST! Should only be necessary if coming from stock)
Boot into recovery mode (power off, power button + volume up)
Select Install zip from sdcard
Select Select zip from sdcard
Browse to the location of the ROMs zip
Select yes and wait for the flash to complete
Reboot
Extras
Metamorph to change status bar black - DOWNLOAD
Metamorph to change status bar white - DOWNLOAD
Metamorph to change status bar transparent - DOWNLOAD
Note: Metamorph can be downloaded from the market HERE or if you prefer ninjamorph HERE.
Thanks
jt1134, Adrynalyne, rotohammer, TCMAN and everyone in IRC as usually is great help.
Lastly, if you like my work, donate to me so I can donate money to devs that make my world easier (and therefore yours).
Great Khas.
Had an issue with the Market, even though you said it was in the rom. I had to use unyaffs on my CWM backup and pull the Vending.apk there and then push it. Otherwise I'm loving it. Great job
Awesome. We have been waiting for someone to step up for us VZW guys. I will be flashing tonight. Thanks man
Im getting alot of fcs when adding a gmail account. Im not sure. Why.
Sent from my DROIDX using XDA App
Two Quick Questions
Hi Guys, I have my tab rooted but that was the extent of my knowledge. I apparently am unsure what this means exactly.
Can someone explain how to do this - YOU MUST HAVE AN EXT4 FORMATTED FILE SYSTEM TO USE
Can someone walk me through the steps of how to - Flash Via Heimdall
Thanks for this..
@ Boushh ,
I have 3 VZW Tablets...funny I got them all for Christmas Gift from One Vocal Wish at Shopping center with my Friends...LOL
I am glad to Try out your ROM, test bugs and other stuff!!
If you can just Post a Descriptive Instruction "How-To" step by step short and brief understandable, will be AWSOME!! All I care is IT Works!! and Functional 75% of Time it is ON!!
andermk said:
Hi Guys, I have my tab rooted but that was the extent of my knowledge. I apparently am unsure what this means exactly.
Can someone explain how to do this - YOU MUST HAVE AN EXT4 FORMATTED FILE SYSTEM TO USE
Can someone walk me through the steps of how to - Flash Via Heimdall
Thanks for this..
Click to expand...
Click to collapse
The easiest rout for you would be to download and install the "Verizon Tab Bootstrapper" (it costs a buck, also, not my app) from the market onto your tab. that will convert the necessary partitions to ext4. Alternatively you can follow the method to do it manually HERE
ekoandrew said:
@ Boushh ,
I have 3 VZW Tablets...funny I got them all for Christmas Gift from One Vocal Wish at Shopping center with my Friends...LOL
I am glad to Try out your ROM, test bugs and other stuff!!
If you can just Post a Descriptive Instruction "How-To" step by step short and brief understandable, will be AWSOME!! All I care is IT Works!! and Functional 75% of Time it is ON!!
Click to expand...
Click to collapse
No to come off as rude or anything, but I do have instructions on the first post. They are pretty much all you need, so what exactly are you not getting or would you like explained more in depth? Once I discover this I can update my instructions to where it would be more helpful for some of you.
Beginners Terms
No to come off as rude or anything, but I do have instructions on the first post. They are pretty much all you need, so what exactly are you not getting or would you like explained more in depth? Once I discover this I can update my instructions to where it would be more helpful for some of you. [/QUOTE]
Hey Boushh,
When you said:
YOU MUST HAVE AN EXT4 FORMATTED FILE SYSTEM TO USE
Use Koush's recovery to get there.
Do you mean just wipe data and cache in cwm or something more?
Also when you said to Flash Via Heimdall - Im just not sure how to use Hiemdall. Can you tell me what steps to take.
Sorry for the questions and thanks for your patience.
Hey boushh, would you mind listing out all the apps that you deleted out of the /system? I just want to make sure that some of the stuff like divx, mobile print, etc is still there.
Thanks for all your hard work!
Boushh,
Thank you so very much for this. I just flashed v2 and I'm in love with my tab all over again! I do have 3g enabled, and so far it seems to be working just as well as the stock ROM. So far I don't notice any issues and it's blazing fast. I'm also using your new kernel as well. Thanks again and keep up the awesome work!
steveo11284 said:
Boushh,
Thank you so very much for this. I just flashed v2 and I'm in love with my tab all over again! I do have 3g enabled, and so far it seems to be working just as well as the stock ROM. So far I don't notice any issues and it's blazing fast. I'm also using your new kernel as well. Thanks again and keep up the awesome work!
Click to expand...
Click to collapse
Im looking for some help, im not new to this completly as ive rooted and installed many roms on my phones but im new to this for the tab...
I downloaded the bootloader off the market. After i do the bootloader do i factory reset?
My question is with heimdall....when you have the screen up with all the different options(pda/code , kernal, etc) where do you put the rom to flash it?
EDIT* I got to the clockworkmod recovery screen. Can i wipe cache and install zip from there as im used to from my phone????
Thank again as any help is appreciated
Alright guys i need some help...The tab wont get pass the "samsung" when i try to boot. The only thing i did was run the bootstrapper from the market. I can get to download mode but i cant figure out how to install the rom from heimdall...
UPDATE: In Heimdall i got "flash successfully completed" but when the tab goes to boot it wont get past the samsung screen!!
---Deleted---
jkurl said:
I really hope you did a backup cause it you did then you can go into recovery and restore your system. If not you can still go into clockworkmod and reinstall the rom from there. that is where you should have installed the rom from.
Click to expand...
Click to collapse
Well after all morning trying to figure this out...i finally got it! Had to restore to factory settings and whatnot first and then i figured it out!! Thanks again
steveo11284 said:
Boushh,
Thank you so very much for this. I just flashed v2 and I'm in love with my tab all over again! I do have 3g enabled, and so far it seems to be working just as well as the stock ROM. So far I don't notice any issues and it's blazing fast. I'm also using your new kernel as well. Thanks again and keep up the awesome work!
Click to expand...
Click to collapse
Awesome, I'm so glad to hear 3G is still working! Thanks for letting me know that. Also, I'm glad you enjoy the ROM, I have some good things in store for it too.
newtonfb said:
Im looking for some help, im not new to this completly as ive rooted and installed many roms on my phones but im new to this for the tab...
I downloaded the bootloader off the market. After i do the bootloader do i factory reset?
My question is with heimdall....when you have the screen up with all the different options(pda/code , kernal, etc) where do you put the rom to flash it?
EDIT* I got to the clockworkmod recovery screen. Can i wipe cache and install zip from there as im used to from my phone????
Thank again as any help is appreciated
Click to expand...
Click to collapse
You factory reset, as I said in the instructions, also, there is no zip. You flash via Heimdall in download mode, as I said in the instructions. The ROM will not boot unless you factory reset
newtonfb said:
Alright guys i need some help...The tab wont get pass the "samsung" when i try to boot. The only thing i did was run the bootstrapper from the market. I can get to download mode but i cant figure out how to install the rom from heimdall...
UPDATE: In Heimdall i got "flash successfully completed" but when the tab goes to boot it wont get past the samsung screen!!
Click to expand...
Click to collapse
I would use the heimdall command prompt, the GUI doesn't always work right. Also, this has no verizon boot animation, so you will just see a black screen for a second once you get past the samsung screen.
jkurl said:
I really hope you did a backup cause it you did then you can go into recovery and restore your system. If not you can still go into clockworkmod and reinstall the rom from there. that is where you should have installed the rom from.
Click to expand...
Click to collapse
No, you don't install the rom from Clockworkmod. You should read the directions before spreading misinformation in the future.
Does this rom have the bluetooth drivers fixed?
No, you don't install the rom from Clockworkmod. You should read the directions before spreading misinformation in the future.
Click to expand...
Click to collapse
So what your saying is that you can't install this rom via clockwork mod?
http://www.youtube.com/watch?v=A_qwT7rTY4E
Above is a Video, how the ROM looks like after flashed with Hemidall.
I used Frontend instead of CMD, also purchased the VZW Bootstrapper!
This is 2nd Tried with Voodoo Kernel!
Everything moves pretty well as you can see. So far no Bugs, I just missed the good old File App from original stock rom.
Deleted as well no need to argue over a Rom. Now if you stole my beer than I can see.
@boushh is the CWM for vzw you using version 3 or a later version? Got some people asking me in another forum an I want to make sure I give them the correct info.
This is a guide I’ve put together from my (in)experience with flashing ACS. It mainly comes from the replies of k0nane and theimpaler747 in the SyndicateROM thread. However, since there’s so many pages that can be tricky to search for idiots like me who just throw up random posts for others to solve their problems, I thought it would be good to summarize it along with anything I happened to notice from flashing a couple of Epics. Consider it the FIBI guide.
Step 1: Read all posts by k0nane on page 1 of the SyndicateROM thread before doing a damn thing! http://forum.xda-developers.com/showthread.php?t=976194
Instructions for CWM are in this thread: http://forum.xda-developers.com/showthread.php?t=897612
Useful hotkeys:
Download mode - Hold down 1 on the keyboard when you power on the phone
Recovery mode - Hold Volume down+camera+power to power on the phone
Reset phone - Hold volume up+camera+power. This generally works when the phone is completely locked up.
Flashing:
When going between versions of ACS, check their notes to see if you need to do anything other than flash. You can go between some versions without wiping or losing anything. You can also flash between standard and fully loaded without wiping or losing anything.
Sdcard doesn’t mount in CWM, but shows up in Android - Format the sdcard in Android.
Boot hangs on the Samsung screen – Redownload, format your SD card and reflash
Boot screen flashed between different things – Wipe cache & data 3x and reflash
Journaling:
Enable journaling – In CWM, go to backup and restore. Backup, then restore using that backup. Journaling enabled!
Make it so you don’t need journaling – Keep a copy of the ROM on your phone at all times. Should you ever have data corruption, jump into CWM and flash the ROM again. It’s quick, no wipes needed.
If you restore a backup made in CWM and want to have non-journaled again – Flash the ROM after restoring.
Other issues:
FC in a specific app – Go into manage applications and clear data for that app
FC in several apps – In CWM > Advanced, try fixing permissions. Can also clear caches, and if that doesn’t work, reflash the ROM.
If you have any major issues that seem unresolved, Odin everything back to stock with EB13, format your sdcard in android, re-download everything, re-install CWM, re-read all of k0nane’s posts on page 1 and try again.
If you want ads back – Install adfree from market and hit revert
If your phone is freezing often - Flash either the vision kernel found here: http://forum.xda-developers.com/showthread.php?t=1012136 or the Twilight 1.0.4 kernel found here: http://forum.xda-developers.com/showpost.php?p=12504067&postcount=5904. I haven't had the freezing issues, but I'd recommend trying the vision kernel first as it has some other potential benefits.
Recommended tweaks and add ons:
Fugutweaks – This will smooth out a few random things on the phone. I’ve noticed more responsiveness on the lock screen and icons on my homescreen. Small, but nice. Install the ZIP in CWM, file can be found here: http://forum.xda-developers.com/showthread.php?t=981125
Impaled Keyboard – Makes the keyboard less likely to skip keys. Still have some, but they’ve gone down a lot. I use the Speed Demon Edition, still had a fair amount of dropped keys with standard one. Install the ZIP in CWM, file can be found here: http://forum.xda-developers.com/showthread.php?t=1025533&page=18
SetCPU – Handles scaling the CPU and overclocking. Use ondemand setting for smooth performance. If you have issues when the phone is idle or it doesn’t wake up properly, set minimum CPU to 200Mhz. Free for XDA members, APK can be found here: http://forum.xda-developers.com/showthread.php?t=505419
Battery Calibration – If you want to calibrate your battery without going into CWM, grab the app from this thread: http://forum.xda-developers.com/showthread.php?t=1024867. It’s now available from the Android Market.
Vision Kernel – Pretty much Twilight + gives you 1.4Ghz and Voodoo colour which improves balance when brightness is at 100%. Flash in CWM, wipe dalvik. Kernel can be found here: http://forum.xda-developers.com/showthread.php?t=1012136
And a final note that I'm now about 10 hours into testing... if you are using fully loaded and want better battery life, really try standard. It very easy to switch, it flashes over fully loaded with no wipes or data loss, the only thing you lose is that it resets your homescreens. But really, this is day 1 of it for me and 10 hours in I'm at 62% battery remaining. Usually by this time I'd be around 20%.
Great info! I recently installed the newest SyndicateROM 1.1.0 on my Epic and the only trouble I had was with the included Twilight 1.1.0 kernel. My phone kept freezing and I would have to pull the battery to reboot.
This is an issue that has been documented with the ROM and is said to be caused by the kernel and its adjustments to voltage and overclocking, not all phones handle this well.
To fix the issue I flashed the Twilight 1.0.4 kernel, as suggested by k0nane, and I am about a day into testing without any freezing issues. The only problem is that the Twilight 1.0.4 kernel has a known issue with video recording and it does not work.
Let me say that the performance increase from installing SyndicateROM and ext4 are well worth the trouble.
Have you tried the vision kernel? That might fix your freezing without breaking video recording.
is your brightness at 100%??? what was the difference between standard and fully loaded again??
VeNoM vZ said:
is your brightness at 100%??? what was the difference between standard and fully loaded again??
Click to expand...
Click to collapse
What does the brightness have to do with anything? And for the differences, here's from the SyndicateROM thread:
k0nane said:
SyndicateROM Standard includes LauncherPro. All Samsung and Sprint bloatware are completely gone!
SyndicateROM Fully Loaded - the choice of ACS team lead rjmjr69 - features TouchWiz instead of LauncherPro, and adds in Social Network Sync, Facebook, BuddiesNow, Program Monitor, and the stock live wallpapers. All the rest of the bloat is still gone!
Click to expand...
Click to collapse
Catalyst Shift said:
What does the brightness have to do with anything? And for the differences, here's from the SyndicateROM thread:
Click to expand...
Click to collapse
The brightness for battery life.
No, brightness is not at 100%. I generally use 0-25%, though I'll kick it to 100% when viewing photos or when I'm outside. Even with the lower brightness setting, I'd always have to recharge in the afternoon. I'm still doing a lot of testing for ways of having the battery last longer, today is longest it's ever gone for. I'll be adding more information when I feel like I've got a solid way of having it all setup.
OP, could you add the freezes and "terrible battery life" solutions? Namely, flash the kernel in the second post or VisionKernel. It's the most annoying one to answer multiple times daily.
Thanks much for this! Hopefully people read it.
I want to get the battery situation on my phone sorted out before adding it to the list. I was having pretty bad battery life, but switching to standard and removing gallery has made my phone last all day for the first time ever. I want to do some experiments between setcpu options, juicedefender and the vision kernel to see what works best. Hopefully by this weekend I'll have a more detailed idea as to how to get better battery life.
But for now, anyone having battery issues my current setup is using ACS standard and replacing gallery with quickpic. This has doubled my battery life.
Hey wassup everyone, first time writer long time viewer, and first let me say thanks to all the great people that have provided us with great roms for the epic and the syndicate team as well, Im currently using a Epic 4G with sindicate rom freeze 1.1.0 and i must say its awesome, aside from my battery dying really quickly when im runing it at 1.3ghz its actually great, usually i end up operatig it at 800mhz to actually save some battery life last me for 3 days at a time, and when i have it pluged in or show off my awesome epic i raise it back upto 1.3ghz, big difference cuz when i raise it up there my battery drains rather quickly like 3 percent a minute or so.....
well anyways now that, thats says, I have CWM 3..0.5 with syndicaterom twilight 1.1.0 and ive been sucessful at loading custom boot animation, but one thing is that im having trouble is loading the animation with sound? any idea onhow i can od that?, what are the steps, cuz so far ive been using root explorer to transfer and change bootanimation to load up on my screen, but i have no idea where to put the sound or how to even get it to load with the bootanimation any one have any ideas? please help, i do all his trought my phone, put the bootanimation on my sd and work from there and trasfer it to the system/media, most bootanimation that do have sound on them say to put it on the system/custimization/resources but i look every where and the syndicate rom doesnt have that archieve just the system/media, how can i load the sound into my boot? and how can i change the power off animation as wll?
Maybe someone should make a wiki "Trouble shooting guide" formatted like the ones found in the back pages of user manuals..
This might.. just maybe (crosses fingers) alleviate the never ending repeating of questions in the main sfr thread
Catalyst Shift said:
Have you tried the vision kernel? That might fix your freezing without breaking video recording.
Click to expand...
Click to collapse
Just tested Vision kernel 1.1 and ran into countless issues. My phone would not open camera, gallery, or music apps. And after that debacle I didnt even bother to find out if any other apps were misbehaving.
The first sign of trouble came when I installed a fresh version of SyndicateROM 1.1.0 and then flashed Vision kernel 1.1. The phone booted-up fine but when I went to shut down it immediately froze and I had to pull the battery.
Im going to stay on Twilight 1.0.4 kernel for a while until I find something else.
I have tested Twilight 1.0.4 kernel for about a day or two and have not had any problems so far. I even overclocked with SetCPU to 1.2GHz without any issues.
tmspyder said:
Maybe someone should make a wiki "Trouble shooting guide" formatted like the ones found in the back pages of user manuals.
Click to expand...
Click to collapse
I would be more than happy to contribute my experiences if this gets up and running. PM me with any updates to the "SyndicateROM [TSG] WiKi"
Please Help a Novice
I have installed this ROM, followed the directions and thought I did everything right. But when I rebooted the phone, I just get the Clockwork Recovery screen. Have I bricked my phone? How do I recover? Please please please help...Haven't even had my phone for a day...
By the way, the error I'm getting is:
ClockworkMod Recovery v2.5.1.0
E:Can't open /cache/recovery/log
I backed up before I installed this ROM, and Restore brings me back to this same screen / message
mercerma said:
I have installed this ROM, followed the directions and thought I did everything right. But when I rebooted the phone, I just get the Clockwork Recovery screen.
Click to expand...
Click to collapse
Please elaborate on the steps that you took to install the ROM and CWM.
What version of CWM are you running?
What modem do you have installed (...DK28, EB13, EC05)?
Have you transfered the SyndicateROM 1.1.0 onto your SD card before you installed CWM?
Did you wipe data, cache, and dalvik cache at least three times each before installing the .zip?
Your phone most likely is not bricked, that is a very hard to task to achieve. Worst case scenario you may have to do a clean wipe with odin and flash the stock ROM to start the process over. We can try to help you with any issues you may have but in the mean time try searching to the forum to find answers to these questions.
Hey, great idea for the thread.
Something I learned:
I was having AWFUL freezing problems. Tried all the fixes (vision kernel, old twilight) to no avail. If these don't fix your problems, try Genocide Kernel (on these forums). Solved my problems.
Catalyst Shift said:
But really, this is day 1 of it for me and 10 hours in I'm at 62% battery remaining. Usually by this time I'd be around 20%.
Click to expand...
Click to collapse
Ok, so im thinking of switching to the standard edition of he rom cuz im currently using the fully loaded added the 1.0 kernel vision on it to get the 1.4ghz, and its pretty smooth its stable at times so im keeping it at 1.3 for now until its set more stable..... however when u said that ure at 10 hours and u still have 62% whats the speed u have ure epic set at and whats the brightness?
Nolyrics2 said:
Just tested Vision kernel 1.1 and ran into countless issues. My phone would not open camera, gallery, or music apps. And after that debacle I didnt even bother to find out if any other apps were misbehaving.
Click to expand...
Click to collapse
Fix permissions in CWM/etc.
Kernels cannot cause that. It's that simple.
Nolyrics2 said:
Please elaborate on the steps that you took to install the ROM and CWM.
What version of CWM are you running?
What modem do you have installed (...DK28, EB13, EC05)?
Have you transfered the SyndicateROM 1.1.0 onto your SD card before you installed CWM?
Did you wipe data, cache, and dalvik cache at least three times each before installing the .zip?
Your phone most likely is not bricked, that is a very hard to task to achieve. Worst case scenario you may have to do a clean wipe with odin and flash the stock ROM to start the process over. We can try to help you with any issues you may have but in the mean time try searching to the forum to find answers to these questions.
Click to expand...
Click to collapse
I used the one step root process I found here to install CWM 2.5.1.0. I then downloaded the ROM, copied it to my SDcard, then used CWM to install the zip from my sdcard.
I don't know what modem I have, is there a way to check with my phone in it's current state?
I installed CWM previous to transferring the rom to my sd card
I did not the first time, but per instructions on the page where I downloaded the ROM, I reformatted my sd card, redownloaded the ROM, wiped everything 3x's and tried to reinstall. Same result. I keep getting the error on just about everything I do that states "E:Can't open /cash/recovery/log"
And thank you for your advise, any more would be greatly appriciated. I did search the forum, but there is so much information, hard to find what I really want, especially as a novice. I plan to not be a novice for long thanks to xda!
mercerma said:
I used the one step root process I found here to install CWM 2.5.1.0. I then downloaded the ROM, copied it to my SDcard, then used CWM to install the zip from my sdcard.
I don't know what modem I have, is there a way to check with my phone in it's current state?
Click to expand...
Click to collapse
I could probably answer that question, im still a noob, but from what i know u need to install CWM version 3.0.5/6 in order for u to run does roms, thats why ure having trouble flashing it, since Syndicate roms are EXT4 Base Roms anything lower then CWM3 wont support since they are RFS files, go here and follow the steps
http://forum.xda-developers.com/showthread.php?t=976194
download the CWM3 and root it again, u can run the CWM Root over the previous 1 so dont worry, i did it that way and i had no problems what so ever, as to check to see what modem u had, go to settings, about phone, under base band version check to see if the last 4 letters says EB13, or DK28, or if u have the ECO5 which is the newest stock base update that came out.
Also its best to know if ure phone is from stock, or if u updated from any of the first 2 version updates, EB or DK, if u where like me that waited for the update and stayed at Eclair then updated when the ECO5 OTA came out then u should be fine....
Just incase u are from a update of EB or DK here is the link for does 2 versions of CWM3
http://forum.xda-developers.com/showthread.php?t=897612
if im wrong then someone please correct me im still a noob learning.
EDIT: just noticed that u said ure phone is messed at that point, umm u can try to do a factory reset then restart ure phone see if that fixes the problem, then try follow the steps above, if that doesnt work, u will have to download odin, which is also in that link and reflash back to stock, everything is there so if u follow does instrunctions u wont have a problem.....its actually pretty easy.....
I have just flashed Jellytime R16 to my DHD but have a slightly damaged touch screen. Unfortunately the part of the touch screen that doesn't work is the bit where you have to press the start button to move off the screen where you select the language on first boot up.
Does anyone have any ideas how I could skip the first configuration screen of the Jellytime R16 ROM?
I don't think it's permanent maybe a bad zip? Did you check MD5 checksum before you flash? And did you full wipe?
Sorry, I don't think I made myself clear. I do have a damaged touch screen nothing to do with the rom. There is a section of the touch screen that just doesn't work. It is this part that sits exactly where the start button is. It is a shame these start screens don't rotate or the start button was slightly bigger.
So if I could skip this fisr language selection screen I would probably be ok for using the rest of the rom.
I had quite a bit of trouble earlier today installing R16 due to the screen not working at all after the bootup. Had to pull the battery 2 times in a row and make sure the charger was unplugged before the screen would react to touch. Maybe you're also experiencing this thing (several others are reporting it in the JT thread).
foxx1337 said:
I had quite a bit of trouble earlier today installing R16 due to the screen not working at all after the bootup. Had to pull the battery 2 times in a row and make sure the charger was unplugged before the screen would react to touch. Maybe you're also experiencing this thing (several others are reporting it in the JT thread).
Click to expand...
Click to collapse
As I said in my last post this is not a Rom problem I do have a damaged touch screen. I Just need a way of getting past the first setup screen or rotating th screen.
Skunkworx said:
As I said in my last post this is not a Rom problem I do have a damaged touch screen. I Just need a way of getting past the first setup screen or rotating th screen.
Click to expand...
Click to collapse
This is a horrible suggestion for any other use and goes against everything we know about proper flashing, but if all else fails maybe try dirty flashing it over another ROM in which you CAN go through the first boot settings (for example, an ICS ROM that doesn't require the START button in that location). If the unexpected problems that sometimes arise from dirty flashes don't come up, you might be able to get into Jelly Time without the first boot menus.
Obviously, all the problems with dirty-flashing different ROMs come with this "solution."
bananagranola said:
This is a horrible suggestion for any other use and goes against everything we know about proper flashing, but if all else fails maybe try dirty flashing it over another ROM in which you CAN go through the first boot settings (for example, an ICS ROM that doesn't require the START button in that location). If the unexpected problems that sometimes arise from dirty flashes don't come up, you might be able to get into Jelly Time without the first boot menus.
Obviously, all the problems with dirty-flashing different ROMs come with this "solution."
Click to expand...
Click to collapse
Thats an interesting suggestion but the question there is which ICS ROM would give the best results?
I think I would prefer to have a full wipe on installation. So having a way of skipping that first configuration screen, or remotly pressing the start button or even been able to force it to rotate the screen would do the trick. However untill you have got past those first configuration screen you are locked into not been able to run any applications.
I was wondering if there was any way via ADB command line to achive this?
Skunkworx said:
Thats an interesting suggestion but the question there is which ICS ROM would give the best results?
I think I would prefer to have a full wipe on installation. So having a way of skipping that first configuration screen, or remotly pressing the start button or even been able to force it to rotate the screen would do the trick. However untill you have got past those first configuration screen you are locked into not been able to run any applications.
I was wondering if there was any way via ADB command line to achive this?
Click to expand...
Click to collapse
Yes there is. You can use the "adb shell input keyevent <event_code>" command.
You'll probably want to send the DPAD_CENTER command to click that button. I think its event code is 23. Try typing "adb shell input keyevent 23".
Try the code for KEYCODE_ENTER as well.. its 66.
There is a whole list of keyevents at this link:
http://developer.android.com/reference/android/view/KeyEvent.html
Just lookup the "Constant Value" in the description of whatever KEYCODE_xxx you're trying to simulate and use that constant value as the event_code for the command.
I've tried simulating the DPAD_LEFT and DPAD_RIGHT keypress and they're working like a charm
---------- Post added at 04:34 PM ---------- Previous post was at 04:14 PM ----------
Yup. I've tried working with these Keycodes and they work fine.
Use event_codes 19 for UP, 20 for DOWN, 21 for LEFT, 22 for RIGHT to navigate to whatever button you need to press and then use 23 for pressing that button.
Should solve your problem.
Skunkworx said:
I have just flashed Jellytime R16 to my DHD but have a slightly damaged touch screen. Unfortunately the part of the touch screen that doesn't work is the bit where you have to press the start button to move off the screen where you select the language on first boot up.
Does anyone have any ideas how I could skip the first configuration screen of the Jellytime R16 ROM?
Click to expand...
Click to collapse
Hi, did you flash Gapps as well? I've moved from ARHD (which has the configuration start screen) to JellyTime and never got the language or any other configuration start screen (which I'm glad to get rid of). I always full wiped, clean flashed just the ROM, then booted into the OS for the first time to check it out. No Gapps and no language/configuration screen - it would always go straight to the lock screen where I would just swipe to the right and it would ask me to choose either the Nova or Trebuchet launcher. I'd then rebooted into recovery again and flashed Gapps. Hope this helps.
if4ctOr, Thanks for your suggestion this is what I was originally looking for however I didn't get around to trying it as the idea that divche put forward was a much easier approach.
Divche: Thanks, that did the trick perfectly. I am also comming from ARHD so I thought I give your idea a try. I was flashing the Gapps at the same time but booting into the OS first then flashing the Gapps after that prevented the configuration popup.
I am currently swapping between ARHD and Jellytime using the recovery backups as I still haven't got everything installed and setup in the new ROM yet. I didn't realise but I had quite a few of my contacts as phone contacts and not google contacts so they didn't sync into the new rom. So I am looking for a soloution to that and also a way to move my sms messages over.
Eventually I am planning on using the Jelly time as my full time ROM but there are alot of updates to it at the moment, which is a good thing in making it stable. However it takes quite a while to apply all the applications and settings I use after doing a full wipe. Do you need to do this when flashing a new version of JT over a previous one or is there an easy way of doing that? As I read in a lot of places that you should always do a full wipe and that titainum backup is not recomended?
Skunkworx said:
if4ctOr, Thanks for your suggestion this is what I was originally looking for however I didn't get around to trying it as the idea that divche put forward was a much easier approach.
Divche: Thanks, that did the trick perfectly. I am also comming from ARHD so I thought I give your idea a try. I was flashing the Gapps at the same time but booting into the OS first then flashing the Gapps after that prevented the configuration popup.
I am currently swapping between ARHD and Jellytime using the recovery backups as I still haven't got everything installed and setup in the new ROM yet. I didn't realise but I had quite a few of my contacts as phone contacts and not google contacts so they didn't sync into the new rom. So I am looking for a soloution to that and also a way to move my sms messages over.
Eventually I am planning on using the Jelly time as my full time ROM but there are alot of updates to it at the moment, which is a good thing in making it stable. However it takes quite a while to apply all the applications and settings I use after doing a full wipe. Do you need to do this when flashing a new version of JT over a previous one or is there an easy way of doing that? As I read in a lot of places that you should always do a full wipe and that titainum backup is not recomended?
Click to expand...
Click to collapse
For moving SMS, I'd suggest this app : https://play.google.com/store/apps/...mNvbS5yaXRlc2hzYWh1LlNNU0JhY2t1cFJlc3RvcmUiXQ..
And as far as flashing the updates of JellyTime are concerned... It is recommended to always full wipe but you might get away with flashing the update over the previous version without a wipe. In some updates the author of the ROM explicitly says that full wipe is needed... in those cases you must. In other cases you can flash the ROM without the wipe which will keep your apps and data intact. However, it would still be better to wipe your cache and dalvik cache atleast.
Using Titanium Backup is not recommended at all when you're switching between different Android versions.. however I personally think it works ok when used between updates of the same ROM.
Skunkworx said:
Divche: Thanks, that did the trick perfectly.
Click to expand...
Click to collapse
I never encountered the config screen, so it was more of a guess based on what I did, so I'm glad it helped!
I am currently swapping between ARHD and Jellytime using the recovery backups as I still haven't got everything installed and setup in the new ROM yet. I didn't realise but I had quite a few of my contacts as phone contacts and not google contacts so they didn't sync into the new rom.
Click to expand...
Click to collapse
I also had all my contacts as phone contacts too. I chose to convert my contacts (and my calendar as well) to google for ease of syncing later on, so I have no tried and tested suggestions on how to maintain them as phone contacts. What I did was let HTC Sync synchronise with Outlook (I created a new PST file for this, then specified it in HTC Sync), then used GO Contact Sync Mod (sorry I can't post links yet) to sync it with my gmail account.
If you really wanted to leave as phone contacts, you could try Titanium Backup - but since your phone contacts are saved as system data it's a bad idea - so I'd recommend against it. If you're backing up your nandroid for ARHD, you could always try TiBu and let us know how it went - I think it was labeled Dialer Storage - filter to system data and just look through all the green-colored items for something that says "CONTACTS" or "PEOPLE".
However it takes quite a while to apply all the applications and settings I use after doing a full wipe. Do you need to do this when flashing a new version of JT over a previous one or is there an easy way of doing that? As I read in a lot of places that you should always do a full wipe and that titainum backup is not recomended?
Click to expand...
Click to collapse
+1 to what if4!ct0r said regarding wiping before flashing.
There will always be some system settings that you will have to re-enter manually if you customize them a lot even when updating builds of the same ROM (probably because these are the system items that you shouldn't be restoring). These will depend on the ROM, but for me and JellyTime, the ones I had to redo were developer, lock screen, system/status bar, sound, display, language, as well as ringtone/sound notifications for alarms, messaging and calendar. Also you'll have to manually set up your widgets again - typically ones that require you to configure it as you place it.
As for TiBu not being recommended - personally I didn't have a problem with it when moving over to JellyTime. I actually purchased the Pro version just for this and for flashing new JellyTime builds. There are two things to consider when restoring via TiBu: 1) system data; and 2) app and app data.
System data: The main concern here is, when changing to a completely different ROM, do NOT restore any system data (unless you're aware whether it was updated in the new build or just experimenting). Even when you're updating to a new build of the same ROM, you should at least avoid restoring the red-coloured items and just stick to green and yellow items that may contain useful data such as contacts, sms, call logs, saved wifi access points, bookmarks, etc.
App and app data: I personally think it's ok to restore your apps themselves, but you could always record a list of what you had and download them manually again just to be safe - not a big deal unless you have over a hundred apps. When switching ROMs, try to avoid restoring the app's data unless you really wanted/needed it for certain apps - in that case, be conservative with what you choose. I'm not a programmer or developer, so I don't know how this would affect your system/app if switching to a ROM with a different Android version. Restoring app data between builds of the same ROM should be fine, as I've done it between all my JellyTime flashes with no issue even when it updated to Android 4.1.2.
Tip: after flashing the ROM, and doing your typical post-ROM-flash stuff (like fixing permissions, rebooting, wiping cache+dalvik, flashing Gapps, etc), and you've tested it and are happy with its stability, download TiBu again (or if you had the apk stored somewhere after you purchased it, just install it manually), boot to recovery and make a nandroid of the new ROM as it stands: nice and clean before any apps are installed. This way you've got a recovery option without having to go through the hassle of re-flashing the ROM build again, setting it up, etc if all you did was stuff up while experimenting with restoring data on TiBu.
As always, make a nandroid backup before flashing. As I mentioned, if you're initially happy with the ROM, I recommended also doing one after you flash while the system is fresh and clean. Sorry if this post is a bit wordy, but I thought more info would help, as it helped me in the past.
Skunkworx said:
So I am looking for a soloution ... to move my sms messages over.
Click to expand...
Click to collapse
if4ct0r said:
For moving SMS, I'd suggest this app...
Click to expand...
Click to collapse
+1 for SMS Backup & Restore; I also used it, but keep in mind AFAIK it doesn't save MMS. I also used Call Logs Backup & Restore, in case you're interested in backing this up too. But since I started using TiBu, I don't need either of these apps any more.
Maybe changing the digitizer could help asd
Sent from my Galaxy Nexus using xda app-developers app
In this thread you can post your experience, questions, and all other stuff that is not directly related to the RE-FLEXxx rom.
I do this to keep the dev thread clean.
Thank you for your understanding.
I will take a look into this thread from time to time but the main goal is so that users of the RE-FLEXxx rom can help out each other and that they can find help from each other in one place.
Regards, civ.
I installed 2.0 on my N5110 (coming from 1.9) and it is working well but the top of my tablet is non-responsive to touch. Happened on other releases but a reboot always fixed it. This time the problem remained, so I tried wiping cache, dalvik, fixing permissions, reboots, and all sorts of combinations. I did finally manage to fix the issue yesterday after one of those reboots but now the problem just reappeared and won't go away. Any suggestions?
Edit: Finally got it resolved with a full wipe of data, cache, and dalvik through cwm recovery. Then I flashed Civz reflexx Rom 2.1 and rebooted. The top of the screen still did not respond to touch, so I rebooted and now everything works perfectly. :thumbup:
anybody else still having SNote FC on them in 2.0? also the extended menu items will not work for me...setting fc
dpaik said:
anybody else still having SNote FC on them in 2.0? also the extended menu items will not work for me...setting fc
Click to expand...
Click to collapse
no snote and extended menu all working for me. Maybe you had a bad download? Otherwise try wiping and installing fresh.
dpaik said:
anybody else still having SNote FC on them in 2.0? also the extended menu items will not work for me...setting fc
Click to expand...
Click to collapse
yes, hd happened to me, I re downloaded and reflashed it again and is OK now..
well, I finally installed twrp, and backed up my stock rom, so I am getting ready to flash the first custom rom on any tablet I have had!
one quick question; I am a very experienced rom flasher; I see in TWRP, there are several options under the wipe menu, and, I know to check the first 4 options before flashing this rom; then, there are 2 more options, wipe internal card, and wipe external card.
I know not to wipe my external card, since all my "stuff" is there...should I wipe the internal card before flashing, or is that not necessary when flashing this rom from a stock rom?
I apoligize if this belongs in the the TWRP thread, but I thought since others have probably gone through this, I wanted to post the question here as well. I guess I should post it in the TWRP thread as well...
thank you!
wase4711 said:
well, I finally installed twrp, and backed up my stock rom, so I am getting ready to flash the first custom rom on any tablet I have had!
one quick question; I am a very experienced rom flasher; I see in TWRP, there are several options under the wipe menu, and, I know to check the first 4 options before flashing this rom; then, there are 2 more options, wipe internal card, and wipe external card.
I know not to wipe my external card, since all my "stuff" is there...should I wipe the internal card before flashing, or is that not necessary when flashing this rom from a stock rom?
I apoligize if this belongs in the the TWRP thread, but I thought since others have probably gone through this, I wanted to post the question here as well. I guess I should post it in the TWRP thread as well...
thank you!
Click to expand...
Click to collapse
This is my opinion on it.....I usually only wipe the internal card if I am starting completely over with flashing a device. Wiping data/cache is usually all that is needed but if there are a lot of apps that get installed over time their folders get left and every so often I like to wipe it to get rid of all the "orphaned" folders. If you are going to just restore all those apps anyways then it won't make a difference either way. If you are going from the stock rom to a TW custom based on the stock it shouldn't be necessary to flash internal.
thanks man, that is what I thought, but, since I have never flashed a custom rom on to any tablet I have owned, I wasnt sure if there was other "stuff" on the internal card that might be needed no matter what; and, yes, since I will just be restoring all of my apps pretty much once I flash this custom rom, I might as well just leave the internal card alone...
I appriciate your fast reply!
wase4711 said:
thanks man, that is what I thought, but, since I have never flashed a custom rom on to any tablet I have owned, I wasnt sure if there was other "stuff" on the internal card that might be needed no matter what; and, yes, since I will just be restoring all of my apps pretty much once I flash this custom rom, I might as well just leave the internal card alone...
I appriciate your fast reply!
Click to expand...
Click to collapse
Please take my advice with caution...I did not take your point into consideration because I have yet to do it on this particular tablet (only had the Note for 1 day). Never had a problem on any other tablets/devices but who knows. I wouldn't think there would be an issue. However, like you say probably no reason to wipe internal if you will just be restoring them back anyways.
CCallahan said:
Please take my advice with caution...I did not take your point into consideration because I have yet to do it on this particular tablet (only had the Note for 1 day). Never had a problem on any other tablets/devices but who knows. I wouldn't think there would be an issue. However, like you say probably no reason to wipe internal if you will just be restoring them back anyways.
Click to expand...
Click to collapse
no probs, it worked like a charm!!
just trying to figure out the easiest way to get a nav bar to show up, without having to lower the screen dpi, or to maually edit the buildprop..
thanks!
wase4711 said:
no probs, it worked like a charm!!
just trying to figure out the easiest way to get a nav bar to show up, without having to lower the screen dpi, or to maually edit the buildprop..
thanks!
Click to expand...
Click to collapse
Use the terminal command on my rom
su
softkey_on
all info is in rom thread OP.
thanks, I thought I had read every terminal command in the thread, but I guess I didnt!
tun.ko or tap.ko?
I'm trying to get openvpn to work on REFLEX2.0 in tap mode. Looks like I need a tap.ko kernel module for either the stock kernel or the CivZ-StormBorn_Rev2.0-OC kernel. Anyone know where I might find such a thing?
---------- Post added at 03:59 PM ---------- Previous post was at 03:54 PM ----------
I notice the CivZ-StormBorn_Rev2.0-OC kernel has no /proc/config.gz file. That means the kernel was not compiled with the CONFIG_IKCONFIG option. Is there a way to see what options are baked in to the kernel?
Problem with softtouch Key "back"
hi everyone. I enebled softtouch Keys, but softtouch Key "back" doesn't work correctly. sometimes, it doesn't work, and i must tap it a lot of times.
Why i have with problem?
thanks in advance.
USB Mass Storage Unexpectedly Removed Loop
Hi,
Not sure if I am posting this in the right spot but I am getting a mass storage device unexpectedly removed loop message whenever I attached my USB flash drive? I am using the V2.1 ROM and kernel so wondering if anyone else is facing this same issue? Thanks!
MrAlexey said:
hi everyone. I enebled softtouch Keys, but softtouch Key "back" doesn't work correctly. sometimes, it doesn't work, and i must tap it a lot of times.
Why i have with problem?
thanks in advance.
Click to expand...
Click to collapse
i have better luck if i tap at the bottom of the softkey. it's almost as if the icon is bigger than the actual location that the press registers.
Chrome screen bug solution
Basically the problem is the notification bar, combined with the lack of on-screen softkeys. In order to fix it, you need the following:
Xposed Framework:
http://mohammadag.xceleo.org/public/Android/XposedInstallerDownloadUnsigned.apk
How it works:
http://forum.xda-developers.com/showthread.php?t=1574401
App Settings manager:
http://mohammadag.xceleo.org/public/Android/Xposed/AppSettings_0.4.apk
I've been using this combination on my tablet for a while now. It lets me change the resolution for individual apps. For instance, I want the tablet mode of Gmail, but I want my tablet to run in phablet mode so that I get the top notification bar and no softkeys.
The Chrome fix is simple. The app settings for the Chrome executable should have the fullscreen option toggled, the DPI set to 160, and the screen resolution set to 800x1200. It then hides the notification bar on top while you're in the browser, and shifts the screen that quarter of an inch where it is offset due to the Chrome bug on tablets without softkeys. If you need to access the notification bar, simply swipe down on the screen from the top edge and it will pop up.
If the print size is too small, you can use the accessibility settings in Chrome to scale up the font size.
acfc81 said:
Hi,
Not sure if I am posting this in the right spot but I am getting a mass storage device unexpectedly removed loop message whenever I attached my USB flash drive? I am using the V2.1 ROM and kernel so wondering if anyone else is facing this same issue? Thanks!
Click to expand...
Click to collapse
Hi,
Please ignore my last message as the issue was using the wrong kernel on my part. Thanks!
Question
I'm thinking of flashing a new ROM having used stock for month or so now. My concern is regarding the apps I have installed and am currently using, specifically FolderMount.
If I flash a new ROM (either civs older 4.1 build or his newer 4.2 one depending on how he is progressing), will I lose the links?
I have about 25GB worth of game obb and data transferred over from my internal memory to my micro SD. I dont fancy using up all my download allowance having to re- download and install all of those (plus the time it takes to transfer them all over). I dont mind losing the layout of my homescreens as I'm thinking of shaking that up anyway.
I've only one past experience of flashing a Rom and that ended up with me having to reinstall and set up all my apps (jump from ICS to JB on my Asus TF101)
flex beam 4.2.2 download unsuccessful
flex beam 4.2.2 download unsuccessful
Please upload
Hey everyone,
Whenever I decide to step away from stock and try a new custom ROM (latest being cm11), my phone won't go a day(well, more like 5 hours) without rebooting and hanging at the boot animation. I'm not sure if its the number of apps i install (like 30 including gapps), or something I'm missing, but its not limited to just one rom. I've tried miui, dirty unicorns, revolt, paranoidandroid, all great ROMS, but they don't LAST!
I'm really sorry if I seem like I'm repeating an already-asked question, but I've researched this problem and tried suggestions such as going back to stock and retrying, using Darkside scripts to wipe, wiping cache and dalvik cache and rebooting, wiping android.secure or moving apps away from sd card, etc. Nothing works. So for now I'm back on stock and not enjoying it I just wanted to know if theres anyone that might have any idea how to fix this?
Thanks!
EDIT: To sum up the thread so far, now instead of wiping completely everytime this occurs, i just need to do a battery pull to fix it. However, its really annoying to do 3-4 times a day. Another thing I might note is that my device is refurbished(mentioned below). I did more research and found some fix perms script reccommended by Real_Pariah, which was supposed to fix the issue. It didn't. Also same problem does happen with stock, I've just never stuck with it long enough to find out. At UltimaniumX's suggestion, I did a logcat, which is attached on the last post. Thanks UltimaniumX for your help so far!
So the way I understand it, you've flashed different custom ROMs and they work fine, but after an unspecified amount of time they decide to reboot and hang?
What is the exact process you're using to flash the custom ROMs? As well, each ROM has a specific method to get it working on your phone.
What recovery are you using and what version is it?
What radio are you using?
UltimaniumX said:
So the way I understand it, you've flashed different custom ROMs and they work fine, but after an unspecified amount of time they decide to reboot and hang?
What is the exact process you're using to flash the custom ROMs? As well, each ROM has a specific method to get it working on your phone.
What recovery are you using and what version is it?
What radio are you using?
Click to expand...
Click to collapse
Yep, that's correct. As for exact process, usually I just full wipe everything but sd, then flash.
For my kitkat roms(paranoidandroid, cyanogenmod 11, beanstalk), i flashed used cwm recovery 6.0.4.3. For jelly bean i used either twrp 2.4.4.0 or cwm 5.x(this was in earlier attempts as that was the recovery a guide on galaxys2root instructed me to flash to root stock in the first place). All used radio UVMC6.
Even on stock it happened, but I was able to fix by wiping cache and dalvik plus removing external sd.
When I first rooted, my major issue was getting the rom to get past the animation screen while hanging, and that still occurs, though lately I've been having some success using rom manager from stock to get to cm11(without ext sd). However that does reboot eventually. The first time I was able to fix it by wiping system, android.secure, cache, and dalvik and then reflashing, but it just happened again and that method doesn't seem to be working...
It's interesting that it's happening to all different ROMS that you install. There's a possibility that it's hardware related and not software related. Though I may not be the best to offer advice (since I've only been here for about a year), I recently installed Beanstalk after going through several troubleshooting steps that I finally resolved.
I know that my friend and I both have an SG2. We installed Jedi Knight 6 (which is an older ROM now) but one of the most important steps that he missed, was that he didn't leave his phone idle for 10 minutes after booting it up for the first time. I recall he had issues with apps not working, force-closing, and irregular reboots on his phone. This may or may not been an issue for you, but for awareness sake I leave it here.
If you want you can give Beanstalk another try since I have some experience trying to get it to work. Beanstalk requires you to use a very specific recovery, and I used TWRP 2.6.1.0 straight from the author's post. I wouldn't suggest using a higher version just because KitKat is new.
- I used INFAMOUS wipe cache to clear everything, and then I did a full wipe (including preload) using TWRP.
- Install Beanstalk 4.4 and the 4.4 GAPPS
- Boot and let sit for 10 minutes.
Once you know for sure that it's been 10 minutes, run the "Android Terminal Emulator" and do a logcat. Here's how to do it:
- Type su
- Type logcat -d -f /sdcard/logcat.log , it will save a .log file where your sdcard is.
- At this point, I guess you would have to leave it running until your phone decides to reboot. Then take that file from your SD and examine it on your computer.
http://wiki.cyanogenmod.org/w/Doc:_debugging_with_logcat
See if that helps. Fixing Permissions may also help reset some of your system settings. If it does the reboot loop, try rebooting into recovery, Fix Permissions, and reboot it again.
Alright I'll try Beanstalk, nothing to lose except my cookie clicker progress
Funny same thing happened in stock but was fixed in stock recovery with simple data wipe. I remember about hearing someone downgrading to ics because of "jelly bean bugs", so if beanstalk doesn't work out I'll try that!
(Couldn't straight reply/quote cause I can't post links yet)
EDIT: can't find beanstalk thread, at least cant find one mention twrp, so i wasnt sure if i was on the right one
Alright Beanstalk up and running, waited 10 minutes, and ran logcat command, however, it went back to prompt after running, so I'm not sure if its running in the background or if it dumped the current log and stopped. I kept terminal running just in case.
Quick side question, do you know if beanstalk disables long press home for recent apps? When I try long-press home it brings up the bottom menu instead.
Also, thanks for your help
So Beanstalk was running all fine and dandy as usual when a random reboot occured. However this time it actually got past the bootanimation. But, it asked me to set the default launcher again and terminal wasn't working(no text on screen). So I rebooted and whaddya know, stuck at bootanimation. Tried fixing perms, didn't work.
I tried wiping cache and dalvik, and reinstalling(which after restarting twrp asked if i wanted root and i said no, maybe thats significant?), nope, now no bootanimation. :'(
I forgot to mention that it is refurbished, so maybe that's of significance? Honestly though, now I'm at a loss of ideas.
avbluestar14 said:
Alright Beanstalk up and running, waited 10 minutes, and ran logcat command, however, it went back to prompt after running, so I'm not sure if its running in the background or if it dumped the current log and stopped. I kept terminal running just in case.
Quick side question, do you know if beanstalk disables long press home for recent apps? When I try long-press home it brings up the bottom menu instead.
Also, thanks for your help
Click to expand...
Click to collapse
If you followed the logcat instructions, the file logcat.log is now saved in your sdcard. The Terminal Emulator would not show anything other than that the logcat has been created. Now all you need to do is go to your SD card and grab that file "logcat.log", it will contain a lot of information regarding the state that your phone is in. It's good that you kept the terminal emulator running otherwise the file would not populate with anything. If you can, attach the logcat so we can see it.
Beanstalk long-press home button should show recent apps like normal. I can't remember if the default launcher shows it, since I use Nova Launcher and can confirm that long-press still brings up recent apps.
avbluestar14 said:
So Beanstalk was running all fine and dandy as usual when a random reboot occured. However this time it actually got past the bootanimation. But, it asked me to set the default launcher again and terminal wasn't working(no text on screen). So I rebooted and whaddya know, stuck at bootanimation. Tried fixing perms, didn't work.
I tried wiping cache and dalvik, and reinstalling(which after restarting twrp asked if i wanted root and i said no, maybe thats significant?), nope, now no bootanimation. :'(
I forgot to mention that it is refurbished, so maybe that's of significance? Honestly though, now I'm at a loss of ideas.
Click to expand...
Click to collapse
Right, it seems like if this is occurring on all your ROMs, that may indicate something hardware-related. Again, it's difficult to diagnose. What happens when you go back to the stock rom? Is it T-Mobile's version and it works fine?
This may seem like a stupid question, but you have rooted your phone right?
UltimaniumX said:
If you followed the logcat instructions, the file logcat.log is now saved in your sdcard. The Terminal Emulator would not show anything other than that the logcat has been created. Now all you need to do is go to your SD card and grab that file "logcat.log", it will contain a lot of information regarding the state that your phone is in. It's good that you kept the terminal emulator running otherwise the file would not populate with anything. If you can, attach the logcat so we can see it.
Beanstalk long-press home button should show recent apps like normal. I can't remember if the default launcher shows it, since I use Nova Launcher and can confirm that long-press still brings up recent apps.
Right, it seems like if this is occurring on all your ROMs, that may indicate something hardware-related. Again, it's difficult to diagnose. What happens when you go back to the stock rom? Is it T-Mobile's version and it works fine?
This may seem like a stupid question, but you have rooted your phone right?
Click to expand...
Click to collapse
yeah, stock works fine. about the logcat..I had restarted to try and fix that home button issue like an hour after starting the logcat, which means i inadvertently stopped terminal. whoops. so, i will try beanstalk again, making sure to keep terminal running i guess. sorry about that! might as well see whats in the current logfile for now. also, yes phone is rooted.
I think we're out of options at this point. My last and only recommendation that I can think of is to just install TWRP 2.6.1.0 (and it HAS to be this), and do a full wipe of the phone.
That means:
- factory reset,
- wipe data
- wipe SYSTEM
- wipe cache
- wipe dalvik
- reinstall the same UVLC3 radio (you're on Tmobile I think right?)
- install Beanstalk, install the 4.4 GAPPS (make sure it's the 4.4 apps)
- reboot the phone from recovery.
- let sit for 10minutes
- run logcat to your sdcard,
- observe and post the logcat if the system reboots itself.
UltimaniumX said:
I think we're out of options at this point. My last and only recommendation that I can think of is to just install TWRP 2.6.1.0 (and it HAS to be this), and do a full wipe of the phone.
That means:
- factory reset,
- wipe data
- wipe SYSTEM
- wipe cache
- wipe dalvik
- reinstall the same UVLC3 radio (you're on Tmobile I think right?)
- install Beanstalk, install the 4.4 GAPPS (make sure it's the 4.4 apps)
- reboot the phone from recovery.
- let sit for 10minutes
- run logcat to your sdcard,
- observe and post the logcat if the system reboots itself.
Click to expand...
Click to collapse
right, isn't UVMC6 the latest? i already have beanstalk running after full wipe, if it don't work, im going to repartition with one of old gb roms and pit file and go from there. no reboot on beanstalk yet, logcat is running though. Googling it, a lot of gs2 have problem with this sort of thing it seems.
avbluestar14 said:
right, isn't UVMC6 the latest? i already have beanstalk running after full wipe, if it don't work, im going to repartition with one of old gb roms and pit file and go from there. no reboot on beanstalk yet, logcat is running though. Googling it, a lot of gs2 have problem with this sort of thing it seems.
Click to expand...
Click to collapse
well beanstalk restarted on friday, can't find anything significant in logcat except for sometimes a long list of apps with perm issues,,,even stock has this reboot problem, but a battery pull+cache wipe fixes it(i hope). After googling, many have this problem with jb... maybe ill try an ics rom or something
hmm, back on cyanogenmod 11, and when it stuck at boot, a battery pull did the trick...running logcat overnight.
Well, here's the logcat, perused through, not sure if the errors I'm seeing are normal or not...honestly I wouldn't know what's contributing to the random reboot, and I'm not reporting it to cyanogenmod because I'm not sure if its a fault of their rom, my phone, or me lol
I took a look at the logcat, and there doesn't seem to be anything that would show a fatal error of some sort. Unfortunately there isn't a guide on how to read logcats, so I'm going off of the little experience that I know. Did the logcat run up until the phone reboot?
Again this may seem like a stupid question, but you are sure that you're using an SGH-989 samsung galaxy s2 and not the I-1900 right?
UltimaniumX said:
I took a look at the logcat, and there doesn't seem to be anything that would show a fatal error of some sort. Unfortunately there isn't a guide on how to read logcats, so I'm going off of the little experience that I know. Did the logcat run up until the phone reboot?
Again this may seem like a stupid question, but you are sure that you're using an SGH-989 samsung galaxy s2 and not the I-1900 right?
Click to expand...
Click to collapse
Yep, logat was running up to reboot. It is a SGH-t989, ordered straight rom tmobile site refurbished. I still think its weird how a simple battery pull fixes it though, is it corrupted memory? or partitions? or some hardware on the device?
Sorry man, looks like there really isn't any other suggestions that I have.
There is another user who seems to be having the same issue as you.
http://forum.xda-developers.com/showthread.php?t=2573854
It looks like he was able to resolve it by slowly flashing ROMS starting from 4.1.2. You will have to ask him exactly how he did it, but his story of ROM issues seems exactly the same as yours.
UltimaniumX said:
Sorry man, looks like there really isn't any other suggestions that I have.
There is another user who seems to be having the same issue as you.
http://forum.xda-developers.com/showthread.php?t=2573854
It looks like he was able to resolve it by slowly flashing ROMS starting from 4.1.2. You will have to ask him exactly how he did it, but his story of ROM issues seems exactly the same as yours.
Click to expand...
Click to collapse
Ah I saw that thread, new plan of action:
1. Hard reset, go to stock, try it for a day, see if it randomly reboots.
2. If it does, get a replacement after Christmas since 90-day warranty. If it doesn't, try AOSP 4.1.2.
3. If AOSP 4.1.2 doesn't reboot, go from there.
Well, I'll make sure to update after I get through. Thanks again!
Well, RMA'ed and now everything's working fine, running latest beanstalk, so i guess some partitioning or hardware issue? Oh well, thanks for your help!