MattyG Mods, Userjf Mods, AudioBoost Kernel,
Data Throttle Removal Mods, Camera Shutter Sounds,
CMW3-Flashable Boot Animations, BootLoader Splash Screens... And More!
All Files Can Now Be Found Here:
http://www.mediafire.com/?5ch2853xcxvi0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EVERYTHING YOU DO IS AT YOUR OWN RISK. I TAKE NO RESPONSIBILITY FOR WHAT YOU DO.
DATA THROTTLE REMOVAL:
This removes the throttle files from the rom. The files removed are actually named "throttle", by the way.
AUDIOBOOST KERNEL:
This is simply the stock kernel with all audio levels boosted. Other than that, it is the stock kernel. This will work with any nightly or rc build of cm7.
CAMERA SHUTTER SOUND:
A lower volume, more pleasant, camera shutter sound. Flash with recovery, works with any cm7 version.
CM3-FLASHABLE BOOT ANIMATIONS:
These are boot animations that I have ported to be CWM2 and CWM3 flashable.
SPLASH SCREENS:
Rename exactly to PB31IMG.zip and put on root directory of FAT32 sdcard, not in any folders. You might have to use a blank card with this being the only file... it works for some people better that way. It shouldn't hurt to try it either way though. It will either work or do nothing.
Once the file is on your card and the card is on your phone, with the phone OFF, hold down the vol.down and power button. Hold them down until the bootloader is up. After a few seconds, it should ask you if you want to apply the update. Choose yes.
Once it is loaded, it will be there permanently until you change it again. You don't have to reflash it ever.
BATTERY MODS:
I have continued the popular work "Mattyg battery and clock mods". Mattyg kept these current when he had a Droid Incredible, and he even kept them current for quite some time after he no longer had the phone. We are all thankful to him for putting these together.
These type of flash mods are specific to a particular build of cm7. If you flash one of these to the wrong nightly, it will work only if the cm7 framework has not changed. Otherwise, your phone will be unstable at best, and boot loop at worst. The files have the nightly number at the end, so there is never any confusion about which file goes with what nightly.
If your phone boot loops after flashing, you can easily fix this by reflashing cm7. This is also the method used to "uninstall" these mods if you want to go back to the stock original clock and battery icons.
These are built for CWM3, but they should also work with CWM2 and RA recoverys.
To flash, simply flash them with recovery. Rom Manager will probably work too, but I don't use it.
You can flash the battery mods over each other. The most recent flash will be on the phone, and will overwrite any previous battery mod. There is no need to flash back to stock between changing between these battery mods.
The RemoveClock mod is independent of the battery mods. You can flash clock and battery or either one. They do not interfere with each other in any way.
There is no need to wipe cache or dalvik when you flash these. You can if you want, and it won't hurt anything, but it is not required.
For safety, always have a known good working backup before you flash these, or before you flash anything for that matter.
Enjoy!
RC1 mods have been added, but they are not tested. I have moved past RC1, and you should too! There are CM7 fixes in Nightly #39, and there will continue to be more fixes in the following CM7 builds.
All Files Can Now Be Found Here:
http://www.mediafire.com/?5ch2853xcxvi0
userjf said:
Several people have said they would take over Mattyg's battery and clock mods... but so far no one has... until now!
These will work with cwm recovery 3 (and 2), and they are all tested on the nightly number at the end of the filename (currently #39)
As always, be safe and nandroid!
Enjoy
Click to expand...
Click to collapse
The GB circle bootloops with RC1.
cam30era said:
The GB circle bootloops with RC1.
Click to expand...
Click to collapse
RC1 is NOT 39!!! Flash 39 and you will be good... or wait until tonight and get the #40's.
userjf said:
RC1 is NOT 39!!!
Click to expand...
Click to collapse
Yes, I know. Thought I would give it a try anyway.
So which of those is the stock look with the percentage inside? "stock39"? Or is there one?
RyanTX said:
So which of those is the stock look with the percentage inside? "stock39"? Or is there one?
Click to expand...
Click to collapse
Stock = original
StockPercent = stock + percentage
userjf said:
Several people have said they would take over Mattyg's battery and clock mods... but so far no one has... until now!
These will work with cwm recovery 3 (and 2), and they are all tested on the nightly number at the end of the filename (currently #39)
As always, be safe and nandroid!
Enjoy
Click to expand...
Click to collapse
are you running into any issues with these? i put them all together, but was getting FC's after flashing. not MAJOR FC's, but enough that i didnt want to release them until i figured it out. Mostly CM settings when attempting to change anything and ROM manager.
lol ive been working on it all day.
AdhvanIt said:
are you running into any issues with these? i put them all together, but was getting FC's after flashing. not MAJOR FC's, but enough that i didnt want to release them until i figured it out. Mostly CM settings when attempting to change anything and ROM manager.
lol ive been working on it all day.
Click to expand...
Click to collapse
Let me check, I didn't modify any of Mattyg's actual coding other than compiling into the new framework.
Yup, you are right about that, I tried a few other things, but not that. Very interesting... I'll take a look..., and you take a look... and we will see who figures it out first
userjf said:
Let me check, I didn't modify any of Mattyg's actual coding other than compiling into the new framework.
Yup, you are right about that, I tried a few other things, but not that. Very interesting... I'll take a look..., and you take a look... and we will see who figures it out first
Click to expand...
Click to collapse
Problem found! I'll be putting up new files shortly.
userjf said:
Let me check, I didn't modify any of Mattyg's actual coding other than compiling into the new framework.
Yup, you are right about that, I tried a few other things, but not that. Very interesting... I'll take a look..., and you take a look... and we will see who figures it out first
Click to expand...
Click to collapse
boot loops on green circle-after clean install of #39. what did you find about the FC issues? i have a logcat of what i get with my files.. but no idea how to read it and fix it. lol
userjf said:
Stock = original
StockPercent = stock + percentage
Click to expand...
Click to collapse
That stockpercent was not there when I posted.
Thanks though.
Is there any possibility you could do a cyan colored circle battery?
Sent from my ADR6300 using Tapatalk
cmo220 said:
Is there any possibility you could do a cyan colored circle battery?
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
FC issues should be resolved.
Download the GBCircle39-fixed.zip file and try it.
Post back here if it works well or not.
Only flash them to the build they are intended for (like 39 at this point)
Once these are proven to be good, I can make other colors.
userjf said:
FC issues should be resolved.
Download the GBCircle39-fixed.zip file and try it.
Post back here if it works well or not.
Only flash them to the build they are intended for (like 39 at this point)
Once these are proven to be good, I can make other colors.
Click to expand...
Click to collapse
Stuck in a boot loop...
These are all working fine for me now... I have flashed them over and over on my phone, I have had no boot loops, and no FC. I never had a boot loop during any of these.
Boot loop has always been a a symptom of flashing over the wrong nightly, even when Mattyg was releasing these. Make sure you have the right nightly (currently 39, not RC1.)
If anyone else has tried these, successfully or unsuccessfully since the fixes, please let me know.
userjf said:
These are all working fine for me now... I have flashed them over and over on my phone, I have had no boot loops, and no FC. I never had a boot loop during any of these.
Boot loop has always been a a symptom of flashing over the wrong nightly, even when Mattyg was releasing these. Make sure you have the right nightly (currently 39, not RC1.)
If anyone else has tried these, successfully or unsuccessfully since the fixes, please let me know.
Click to expand...
Click to collapse
Works now.
Reflashed #39, rebooted, cleared cache's and then flashed Mod. Everything seems to be working.
Great work bringing these back to life!! Much appreciated!!
I'm a stock percent kinda guy but I don't see the fixed file in the OP.
hokieputter said:
Great work bringing these back to life!! Much appreciated!!
I'm a stock percent kinda guy but I don't see the fixed file in the OP.
Click to expand...
Click to collapse
I downloaded the stock percent and flashed it and it works great. Im not sure what you mean by 'fixed file' though.
I'm not seeing StockPercent attached to the post either
I thought I had put that one on there. I can't load attachments from my phone but I'll put it on there shortly when I get back to my computer.
Sent from my telephone device thing.
Related
I have some issues with my G2X, and I'm honestly not quite sure if they are my specific phone (it's my first smartphone) or problems with smartphones in general.
Basically, the overall performance occasionally really sucks. The screen will become unresponsive and laggy. Programs will just kind of lock up. Sometimes it just seems to lock up completely for a minute, and then suddenly start working normally again. I haven't done anything odd or fancy with the phone, it's completely stock, with the GB update from LG. No root, no nothing.
So, does this just boil down to the fact that smartphones are honestly still pretty new? Low memory, slower processors? Or is this a problem with my G2X specifically.
Try to flash a custom ROM. It'll really help. If you're not comfortable with that try installing a different launcher, I suggest launcher pro.
Irishdoom said:
I have some issues with my G2X, and I'm honestly not quite sure if they are my specific phone (it's my first smartphone) or problems with smartphones in general.
Basically, the overall performance occasionally really sucks. The screen will become unresponsive and laggy. Programs will just kind of lock up. Sometimes it just seems to lock up completely for a minute, and then suddenly start working normally again. I haven't done anything odd or fancy with the phone, it's completely stock, with the GB update from LG. No root, no nothing.
So, does this just boil down to the fact that smartphones are honestly still pretty new? Low memory, slower processors? Or is this a problem with my G2X specifically.
Click to expand...
Click to collapse
Still pretty new? And slow processor? Many apps can cause slow downs, and so can stock software. Some will tell you that rooting and ROMing is the only way to fly, I would agree. Give it a try, you'll thank your self later.
mine runs nearly perfectly, zero slowdowns etc.
honestly since it's stock you're not getting the full potential of this phone. i recommend flashing Eaglesblood 1.08 (2.3.5) and trinity UV11 kernel. gps works fine, amazing battery life, no bluetooth though
I agree with the first response. Downloading Launcher Pro from the market (there is a free version) will speed up and smooth out all your home screen scrolling and stuff like that. For a more complete smooth experience just start flashing roms. CM7 is the most popular and updated on a more frequent basis than the rest but media streaming via Bluetooth is broken and honestly may never work.
The reason the phone is so slow running stock is because LG's development team supposedly can't code their way out of a wet paper bag.
Sent from my LG-P999 using Tapatalk
You really need to install a custom rom. Miui, CM7, Eaglesblood, Weapon, all of them are loads better than stock. LG really aren't very good at this.
Sent from my Nexus Prime using XDA Ultimate App
Sometimes, the very basic tip works the best. T-Mobile recommends all smartphones to be manually restarted once a week.
I've never experienced any lag, even on stock. Try a factory reset before anything.
Sent from my LG-P999 using xda premium
I'd been thinking about trying to mod it anyhow, so I gave it a go. Currently running the slightly tweaked pre-rooted GB build. Also trying launcher pro, we'll see how it goes.
If I were a new user, I would stick with resetting the data on the phone first before attempting to flash custom roms. Custom roms will have their own set of problems that the stock rom will not have.
Do this:
Uninstall all the apps that you don't use, then perform a factory install.
If you don't uninstall potentially crappy apps first before performing a factory reset, they will just automatically reinstall themselves upon reformat.
My girlfriend and I both have the G2x. She is on her 3rd replacement for the same issues as the OP is having. I as well had the same issues. I installed CM7 and I now do not have any issues what so ever. This phone is very responsive and just flies on command. I suggest doing that. If you're on the GB update, you can still flash CM7. I love this phone now!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
( T-Mobile G2x - CM7 )
erikikaz said:
If I were a new user, I would stick with resetting the data on the phone first before attempting to flash custom roms. Custom roms will have their own set of problems that the stock rom will not have.
Do this:
Uninstall all the apps that you don't use, then perform a factory install.
If you don't uninstall potentially crappy apps first before performing a factory reset, they will just automatically reinstall themselves upon reformat.
Click to expand...
Click to collapse
This post is primarily inaccurate.
Not only inaccurate, but downright absurd. The "crappy" apps that are most likely causing the issues are the bloatware apps put on the phone by Tmobile, and you CANNOT uninstall them without having root access in the first place.
So that's your first step towards freedom, is rooting the phone. So that you can get Titanium Backup or Bloatware Freezer, or something like that, and freeze or uninstall all of that garbage.
There's a reason why most of the custom roms have bloatware removed. Right now, since you're on 2.3.3 stock gingerbread, I would recommend flashing clockwork recovery first: there's the program and tutorial here: http://forum.xda-developers.com/showthread.php?t=1056847
Then flash one of the custom roms built for 2.3.3 if you want to keep full functionality of stereo bluetooth and hdmi. Or flash a 2.3.5 CM7 based rom if you want a bit more customizability, and can do without the hdmi settings and stereo bluetooth. Personally, I'm running 2.3.3 Weapon G2x, and I love it. These roms can be found in the Android Development section of this forum.
Hope this helps. But before you do anything, READ, READ, READ...
Inaccurate?
Depending on which custom rom he chooses, he can and will run into potential problems like APN-drops, slow-to-lock GPS, early shutdown issues, wake issues after calls, amongst other issues which I have seen, but have yet to encounter personally. I have yet to encounter any of these with a good working phone running stock GB.
If this person is having issues with his first smartphone, wouldn't it be smarter to determine his problem through the easiest way first?
1) Rule out rouge apps via uninstalling and data reset.
2) If fresh gingerbread is still temperamental , then you know it's either your hardware or something faulty with the GB that's loaded
3) At this point, you can warranty your phone or you can load a custom ROM. It would still be in your interest to warranty your phone either way because if you ever decide to sell your phone, you know for a fact that your phone will work normally under stock conditions if you choose to demonstrate it to the purchaser. A custom rom would only patch things up.
Throwing a custom rom with it's own potential issues before you attempt step #1 is not "inaccurate" or "absurd," it's downright stupid and is an illogical process for determining the problem.
And guess what, if he does install a custom rom and STILL has these issues and needs to invoke the warranty, guess what he'd have to do before he sends it back in-return the phone back to stock. I'd take a quick data reset before having to uninstall clockwork via nvflash anyday.
erikikaz said:
Inaccurate?
Depending on which custom rom he chooses, he can and will run into potential problems like APN-drops, slow-to-lock GPS, early shutdown issues, wake issues after calls, amongst other issues which I have seen, but have yet to encounter personally. I have yet to encounter any of these with a good working phone running stock GB.
If this person is having issues with his first smartphone, wouldn't it be smarter to determine his problem through the easiest way first?
1) Rule out rouge apps via uninstalling and data reset.
2) If fresh gingerbread is still temperamental , then you know it's either your hardware or something faulty with the GB that's loaded
3) At this point, you can warranty your phone or you can load a custom ROM. It would still be in your interest to warranty your phone either way because if you ever decide to sell your phone, you know for a fact that your phone will work normally under stock conditions if you choose to demonstrate it to the purchaser. A custom rom would only patch things up.
Throwing a custom rom with it's own potential issues before you attempt step #1 is not "inaccurate" or "absurd," it's downright stupid and is an illogical process for determining the problem.
And guess what, if he does install a custom rom and STILL has these issues and needs to invoke the warranty, guess what he'd have to do before he sends it back in-return the phone back to stock. I'd take a quick data reset before having to uninstall clockwork via nvflash anyday.
Click to expand...
Click to collapse
Perhaps "misleading" is a more appropriate word than "inaccurate". Custom roms typically remove the bloatware that was preinstalled and the source of some of the issues people are having. User installed apps and settings are wiped with a factory reset. They are only automatically reinstalled if you select to let Google backup your settings and apps, and in my experience that auto backup/restore is not very reliable.
Yes a complete wipe is a good place to start but our experience with the G2X has been that getting away from stock setup fixes most issues for most people that post here.
I did go through the process of flashing a custom ROM. First, I tried to just root the phone following the procedure here, but then ran into that issue where you can't root if you're on the GB OTA update.
I then followed the guide to install Clockwork Mod recovery without rooting, and was able to get that done. I then elected to install one of the closer to stock ROMs, the slightly modded, pre-rooted GB update. The phone does seem significantly more responsive. I may try CM7 soon.
One question. I downloaded the CM7 nightly, and the guide says to then install "update.zip", but I see no file with that name from what I downloaded. Am I missing a step? Or do I just install that zip I downloaded?
Irishdoom said:
I did go through the process of flashing a custom ROM. First, I tried to just root the phone following the procedure here, but then ran into that issue where you can't root if you're on the GB OTA update.
I then followed the guide to install Clockwork Mod recovery without rooting, and was able to get that done. I then elected to install one of the closer to stock ROMs, the slightly modded, pre-rooted GB update. The phone does seem significantly more responsive. I may try CM7 soon.
One question. I downloaded the CM7 nightly, and the guide says to then install "update.zip", but I see no file with that name from what I downloaded. Am I missing a step? Or do I just install that zip I downloaded?
Click to expand...
Click to collapse
Just install the zip you downloaded. Clockworkmod recovery allows you to select any zip on your sdcard, just make sure there aren't any spaces in the name of the zip folder.
I hate to turn this into a support thread, but it seems easier than tackling one of the giant CM7 threads.
So I ran into this problem when trying to install my first ROM using CWM recovery. (Which I flashed using NVFlash, as per the guide here - I had to install some stuff for an APX device, turn the phone on with the battery out, etc.) When I try to locate the zip file, I'm not finding it. I even put it in multiple locations. The "SD" that CWM seems to be looking at just doesn't seem right. It's just plain not showing all my folders and files, not even close.
I've heard maybe I have the wrong version of CWM, I've heard about different "colors." I can tell you the text on the tool is kinda orange.
Are you putting the zip on your SD card?
Yes. I was eventually able to get it up and running by using Rom Manager, and booting to recovery through that, which seemed to take me to a DIFFERENT version of CWM, through that utility I was able to find my zips on the internal memory. I installed CM7, then had to go through getting the Gapps installed, and then elected to go back to the more vanilla modded GB ROM I had been running. I didn't really see how CM7 helped me, and it was actually acting skittish. Maybe I'll try it again later on a more stable 2nd release candidate.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SILVER ROM ICS
15 toggle mod and kernel thanks to RomRacer
download link
ROM
Http://www.theandroidcollective.org/i727/SilverRom/silver_cream_sammywich.zip
SuperSU
Http://www.theandroidcollective.org/i727/SilverRom/CWN-SuperSU-v0.87.zip
if you do not want transparent pop up menus flash this
http://www.theandroidcollective.org/i727/SilverRom/notrans.zip
Here are instructions.
Download bothzips
Put on sd card
Wipe/data/cache/dalvik cache
Flash rom
Flash supersu.zip
Boot system.
After boot is complete.
Shutdown. Wipe data/cache/dalvik and fix permissions.
Sign in google.
Sign in g+
Open the supersu ap. It will update binary.
You will not loose root.
Power options work.
For later.................
Screenshots.........nnnnnn
For later..............
Is TiBu working yet? And can I install this over another ICS Rom?
Love your rom. I tried the new ics but had tons of fc. Not only did tibu but also with waze and a few others. I went back to collective 3 for now. Patiently waiting for your next masterpiece
Skyrocket,
I was trying to follow your other thread ( no data loss gb rom ) and got lost...
Needless to say, I'm glad you've created a new one.
My question is: Is THIS rom your current 4.0.3 project? I'm still running 2.3.6 (NexusMod4) and would love to try out a stable (or at least somewhat stable) ICS rom.
Thanks in advance, and as always - thanks for the hours of time you and other devs put into these masterpieces!
yes this is my current ics android 4.0.3 rom
link has been removed from op
uploading updated version with changes ......tibu has been fixed so be patient i will update the op with new link asap
you can flash this from gb without wiping anything
yeah i accidentally added back the preloadinstaller
thats what causes the force closes and tibu not to work
silver03wrx said:
yes this is my current ics android 4.0.3 rom
you can flash this from gb without wiping anything
Click to expand...
Click to collapse
Well, I just attempted to flash it (without wiping first) and got stuck in a boot loop.
Any suggestions?
EDIT:
As I let it attempt to boot several times, it seems to get a little further into the boot animation. I've now seen just a little bit of blue swirls behind the earth.
TwiztedDotNet said:
Well, I just attempted to flash it (without wiping first) and got stuck in a boot loop.
Any suggestions?
EDIT:
As I let it attempt to boot several times, it seems to get a little further into the boot animation. I've now seen just a little bit of blue swirls behind the earth.
Click to expand...
Click to collapse
Yea same thing happen to me coming from NexusMod4 Im still trying to get it to not bootloop errgh
Sent from my SAMSUNG-SGH-I727 using xda premium
Yes restore yourbackup and wait for new upload
probs with the theme
I was running fine on the ICS rom (ics3.zip) and installed the theme. Now I'm getting lots of apps unable to run (handcent, lookout, juice defender, ROM manager). Ran fix perms in recovery (couldn't get into ROM mgr to try there) and didn't help... Just wanted to let you know.
I flashed mhx Superlite 4.5 over the previous version (ics3 I think) of Silver ICS and it fixed the freeze at shutdown issue for me. That rom has a wipe script too but that one wipes and formats data (also aligns disc partitions--not sure if yours does that).
I'm wondering if the freeze at shutdown issue has something to do with data not getting fully wiped.
I'm going to try flashing your latest rom over Superlite and see if I get the shutdown freeze again. I'll report back with results...
(I should mention that one person posted that they flashed mhx's rom and got the freeze at shutdown for the first time, so who the hell knows...)
I don't like being impatient, but I'm seriously sitting here biting my nails waiting for the download link to come back (with the latest version).
The suspense is killing me!!!
F5...F5...F5... ;-)
Sent from my SAMSUNG-SGH-I727 using xda premium
silver03wrx said:
download link
http://www.theandroidcollective.org/i727/silverrom/silverics.zip
Click to expand...
Click to collapse
Uhm.. OK I give... Where's the link exactly?
robinsonj said:
Uhm.. OK I give... Where's the link exactly?
Click to expand...
Click to collapse
It's not currently available.
We're all "patiently" waiting for his latest release to be linked...
...and I almost have no finger nails left!
Having an issue with the ViperXL 3.2.6 rom from Venom.
Quite frequently I receive a call, and before the call can connect and show ringing the phone reboots. The phone will light up and immediately go to the ViperXL logo.
I have flashed 3.2.6 twice, once via updates OTA and the second time a clean flash and wiping the phone. So this determines its a ROM specific problem and not my device as it worked fine with 3.2.5.
Anyone have any suggestions?
Mods please move to QA if needed. I tried to post there, but for some reason that didn't work. Thanks!
LOGCAT !!!!!! LOG CAT
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jd101506 said:
Having an issue with the ViperXL 3.2.6 rom from Venom.
Quite frequently I receive a call, and before the call can connect and show ringing the phone reboots. The phone will light up and immediately go to the ViperXL logo.
I have flashed 3.2.6 twice, once via updates OTA and the second time a clean flash and wiping the phone. So this determines its a ROM specific problem and not my device as it worked fine with 3.2.5.
Anyone have any suggestions?
Mods please move to QA if needed. I tried to post there, but for some reason that didn't work. Thanks!
Click to expand...
Click to collapse
Do you use the AOSP lockscreen with the incoming call workaround? I had this problem. Just turn off the incoming call workaround and use Tasker to unlock the phone when a call comes in.
RollTribe said:
Do you use the AOSP lockscreen with the incoming call workaround? I had this problem. Just turn off the incoming call workaround and use Tasker to unlock the phone when a call comes in.
Click to expand...
Click to collapse
I'll give that a shot. Should this not work, is there a good guide on here to relock, unroot, and flash the original rom? Should I need to go back for a warranty reason I'd like to know I have the ability to do it. SuperCID, unlocked, and on 3.2.6 currently. I do not have a backup of my original ROM as when I was flashing that particular backup it erased the SD card. Which was awesome. haha.
I did use the AOSP unlock method with the autounlock feature enabled since last week. Its odd, sometimes it worked, sometimes it didn't. Prior to updating to 3.2.6 I never had any problems.
Thanks!
CheesyNutz said:
LOGCAT !!!!!! LOG CAT
Click to expand...
Click to collapse
I can paste the whole Log if you want but... I only have three "red" issues it seems.
"E/Trace (29702): error opening trace file: No such file or directory (2)" x 5
"E/hwcomposer( 237): void qhwc::QueuedBufferStore::unlockBuffer(private_handle_t*) Invalid Handle" x 1
"E/SQLiteLog(29830): (5) statement aborts at 1: [PRAGMA journal_mode=TRUNCATE;]" x1
Have you tried a dirty flash of the Rom? Agree that it is most likely aosp lockscreen issue. Could also be too little voltage. Do a nandroid backup, and then try a dirty flash(only wipe dalvik and cache).
Sent from the HOXL dimension of S-OFF
c5satellite2 said:
Have you tried a dirty flash of the Rom? Agree that it is most likely aosp lockscreen issue. Could also be too little voltage. Do a nandroid backup, and then try a dirty flash(only wipe dalvik and cache).
Sent from the HOXL dimension of S-OFF
Click to expand...
Click to collapse
I did a dirty flash of the ROM prior to this current one. I have disabled the AOSP lockscreen and gone back to the stock one and it seems to be fine. I have received three calls on it so far with no random reboots, so far so good. Will report back if I have it again and i'll try a dirty flash if so.
Does anyone have a good step by step guide to bring the phone back to ATT spec? Supercid, relock, the stock rom etc? Assuming this guide will do me? http://www.youtube.com/watch?v=owjiYLQNbnI
At some point in the future I'll need to reformat in order to upgrade and I'd like to be ready for it.
Thanks everyone.
jd101506 said:
I did a dirty flash of the ROM prior to this current one. I have disabled the AOSP lockscreen and gone back to the stock one and it seems to be fine. I have received three calls on it so far with no random reboots, so far so good. Will report back if I have it again and i'll try a dirty flash if so.
Does anyone have a good step by step guide to bring the phone back to ATT spec? Supercid, relock, the stock rom etc? Assuming this guide will do me? http://www.youtube.com/watch?v=owjiYLQNbnI
At some point in the future I'll need to reformat in order to upgrade and I'd like to be ready for it.
Thanks everyone.
Click to expand...
Click to collapse
It depends what state your phone is in now. Is it SuperCID? If so, and you're S-ON the RUU will brick your phone. The safest way to RUU is with S-OFF. Are you planning on selling the phone? If so, I would just leave it S-OFF and bootloader unlocked and just run the RUU. This way, the phone is stock but if the next person wants to root it they can.
exad said:
It depends what state your phone is in now. Is it SuperCID? If so, and you're S-ON the RUU will brick your phone. The safest way to RUU is with S-OFF. Are you planning on selling the phone? If so, I would just leave it S-OFF and bootloader unlocked and just run the RUU. This way, the phone is stock but if the next person wants to root it they can.
Click to expand...
Click to collapse
Thanks for the information. Ironically a lot has happened since I last posted.
Unrooted and relocked the phone yesterday. After running the RUU, it booted up and I all was well. Phone was perfect coming out of the gate, and I installed all my apps and customization. Unfortunately, when I updated to the stock JB image using the OTA update from ATT it erased all my data. Puzzling. I tried updating again and it bricked the device. No power, no screen image, no charge LED, nothing.
Took it to ATT and my replacement is out for delivery today. I guess that's one way to do it...
Thanks to the community for all the help. Might end up rooting this new phone once I get sick of ATTs junkware.
I have installed 4.1.2 on atrix 2 (leaked)...
Are there any roms that are out for MB865 which i can install with stock rom using BMM...
please give the links (CM10.1, MIUI etc.)
Thank you in advance...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Kexec ROMS
If you wanna use roms based on ICS kernel you'll need downgrade to ics. Only kexec roms are working on JB kernel....
For etc. Mokee ROM: http://forum.xda-developers.com/showthread.php?t=2305303 & my post to improve battery life on kexec - http://forum.xda-developers.com/showpost.php?p=42689041&postcount=230.
BMM questions
Thanks for quick reply...
I don't know more about BMM...
so where i can get the information about BMM for installing BMM roms & also for uninstalling. (on atrix 2) any tutorial video
& also i want to ask can i install atrix 2 official roms 4.1.2, 4.0.4 or 2.3.6 on phone with multi-boot or i can just install one of these & other roms based on it's kernel ???
Thanks in advance...
Tech-G.ONE said:
Thanks for quick reply...
I don't know more about BMM...
so where i can get the information about BMM for installing BMM roms & also for uninstalling. (on atrix 2) any tutorial video
& also i want to ask can i install atrix 2 official roms 4.1.2, 4.0.4 or 2.3.6 on phone with multi-boot or i can just install one of these & other roms based on it's kernel ???
Thanks in advance...
Click to expand...
Click to collapse
A word to the wise: If you're asking these kinds of questions, it would be in your best interest to do some reading/research before try to do anything. Not trying to sound like a jerk, but the #1 thing that will brick your phone is a lack of knowledge. After you've read everything a few times and are starting to feel like you understand, then read it all again. Then if you still have questions, feel free to ask. Good luck, and most importantly, have fun! :thumbup::thumbup:
Brought to you by time and relative dimensions in space.
Yes I am interested...
I get information & I installed 3 Roms that day...
but didn't get information , how to completely remove one rom from installed rom...
bcoz we factory reset then all roms will vanish...
but while flashing one widget zip my phone breaks & it couldn't helped me at all....
it just disappear from boot & i get boot-loop...
Tech-G.ONE said:
Yes I am interested...
I get information & I installed 3 Roms that day...
but didn't get information , how to completely remove one rom from installed rom...
bcoz we factory reset then all roms will vanish...
but while flashing one widget zip my phone breaks & it couldn't helped me at all....
it just disappear from boot & i get boot-loop...
Click to expand...
Click to collapse
Did you even read what 1BadWolf posted? The reason why we ask you to search, read, and ask questions before jumping into flashing roms is because the Atrix2 has a locked bootloader and there are many different versions.
Sent from my MB865
Waiting4MyAndroid said:
Did you even read what 1BadWolf posted? The reason why we ask you to search, read, and ask questions before jumping into flashing roms is because the Atrix2 has a locked bootloader and there are many different versions.
Sent from my MB865
Click to expand...
Click to collapse
OK. I get information about deleting completely...
Yes but Rom are working on my phone... some phone shows blank screen but my phone showing boot animation...
sometimes BMM do weared things... like when it can't boot in other roms & restarts... but otherwise manytimes it works perfect...
Thank you...
Tech-G.ONE said:
OK. I get information about deleting completely...
Yes but Rom are working on my phone... some phone shows blank screen but my phone showing boot animation...
sometimes BMM do weared things... like when it can't boot in other roms & restarts... but otherwise manytimes it works perfect...
Thank you...
Click to expand...
Click to collapse
Haha, it doesn't exactly do weird things. Some phones cannot boot or run kexec roms. Some phones can run kexec but often have "weird" things happen. It's perfectly normal and it shouldn't happen too much from now onwards. If the reboots/black screen do become a great issue, try a non-kexec rom or try flashing the kexec rom after a clean wipe. If your rom only shows a boot animation that goes on forever it is called a bootloop. D a clean wipe and reflash to get rid of the bootloop! In future, try reading some comments too. They usually include a question just like yours, with an answer just like mine . Hope this answered your question !
Dbstudioz said:
Haha, it doesn't exactly do weird things. Some phones cannot boot or run kexec roms. Some phones can run kexec but often have "weird" things happen. It's perfectly normal and it shouldn't happen too much from now onwards. If the reboots/black screen do become a great issue, try a non-kexec rom or try flashing the kexec rom after a clean wipe. If your rom only shows a boot animation that goes on forever it is called a bootloop. D a clean wipe and reflash to get rid of the bootloop! In future, try reading some comments too. They usually include a question just like yours, with an answer just like mine . Hope this answered your question !
Click to expand...
Click to collapse
you not get it correct...
It works perfect many times...
but sometime while going in system 3,4 or 5 ... it just restart phone 1 or 2 times but later again it works perfectly ...
so i said it weird... it is not bootloop ... it is loading problem but why it occus don't know...
& it is showing new error.... after using other installed rom without rebooting, after 1 day it shows sim card inserted please reboot ur phone....???
so I said it shows some different errors, why don't know...
I installed it on fresh rom 4.1.2... so that is not issue...
The multiple reboots used to be common before BMM. It isn't anything new and/or surprising. Most people only had it with bootstrap but nonetheless don't be worried. It doesnt mean a thing and shouldn't affect Roms. As for the Sim card problem, you need to be a lot clearer with that. What error message are you getting exactly? Sim card is inserted? Or isn't? That could be a physical error, it could be a loose Sim card. Please give us all some more information, we're just trying to help
Update:
Omg. While switching systems, you have 3 seconds to pick a different system to boot. If you don't, your phone will automatically boot to system 1 (unless you change the settings in BMM). That's probably why!
Sent from my MB865 using xda app-developers app
wasnenc maximum
Hi GuysPlease help me with this, i have an Indian Atrix 2 with Official jellybean4.1.2. I wanted to try custom ROMs so used BMM method but without any success.
I started by installing BMM, activated system 2, created system, cache & data partitions in system 5. Cleared data.etc. clicked install zip package & installed PACman (Kexec) rom. Rebooted in system 5, but i only get black screen + green LED
Thought this as a problem with kexec ROMs & installed PACman(non-kexec) ROM in the same way. Now instead of green LED i get black screen + red LED, nothing else.
What m i doing wrong, please help me, i'm really frustrated
aki2cool said:
Hi GuysPlease help me with this, i have an Indian Atrix 2 with Official jellybean4.1.2. I wanted to try custom ROMs so used BMM method but without any success.
I started by installing BMM, activated system 2, created system, cache & data partitions in system 5. Cleared data.etc. clicked install zip package & installed PACman (Kexec) rom. Rebooted in system 5, but i only get black screen + green LED
Thought this as a problem with kexec ROMs & installed PACman(non-kexec) ROM in the same way. Now instead of green LED i get black screen + red LED, nothing else.
What m i doing wrong, please help me, i'm really frustrated
Click to expand...
Click to collapse
Have you edited the recovery.fstb file?
Dbstudioz said:
The multiple reboots used to be common before BMM. It isn't anything new and/or surprising. Most people only had it with bootstrap but nonetheless don't be worried. It doesnt mean a thing and shouldn't affect Roms. As for the Sim card problem, you need to be a lot clearer with that. What error message are you getting exactly? Sim card is inserted? Or isn't? That could be a physical error, it could be a loose Sim card. Please give us all some more information, we're just trying to help
Update:
Omg. While switching systems, you have 3 seconds to pick a different system to boot. If you don't, your phone will automatically boot to system 1 (unless you change the settings in BMM). That's probably why!
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
both are not big issues of BMM...
If the kernel not loaded it reboots the phone... I think it is common for all...
but about that error msg i don't know...
I am damn sure it is not physical error... because I am using this phone from 8 months... & I changed card to 3g because it is more suitable with phone so it is using from 7 months... before 7 days it is not showing this type of msg...
after installing BMM & roms... I get that msgs...
If i am not reboot my phone for long time then it show like that... I am just uploading snapshot of it with this msg...
I thing CID corrupted & contact to customer care error is known error...
& for this error i will say we can just press back button & use rom as it is ... so it is not big issue ...
but i don't why it is show like that... what's the problem... because as everyone knows in atrix 2, without pulling battery we can not remove sim card...
While i am listening songs it shown this msg... I just take snapshot of it.. & pressed back button ... network work fine also after that....
aki2cool said:
Hi GuysPlease help me with this, i have an Indian Atrix 2 with Official jellybean4.1.2. I wanted to try custom ROMs so used BMM method but without any success.
I started by installing BMM, activated system 2, created system, cache & data partitions in system 5. Cleared data.etc. clicked install zip package & installed PACman (Kexec) rom. Rebooted in system 5, but i only get black screen + green LED
Thought this as a problem with kexec ROMs & installed PACman(non-kexec) ROM in the same way. Now instead of green LED i get black screen + red LED, nothing else.
What m i doing wrong, please help me, i'm really frustrated
Click to expand...
Click to collapse
On which version of PAC man u get that problem...
When I installed 12 june version (I think) i get that problem (kexec)...
But on 22 june update i cannot get that problem... so try to install new version...
& u r on 4.1.2 so u cannot install non-kexec roms on phone, like me... so u have to install kexec roms...
try other roms... search & installed other kexec roms... (because if other roms r installing then ur bootloader is OK)
If u want, i will give my installed kexec roms link...
If u think this information is helpful for u then just HIT below THANKS Button...
Happy Multi-booting...
THANKS
deveshmanish said:
Have you edited the recovery.fstb file?
Click to expand...
Click to collapse
Devesh once again, but i edited recovery.fstb file, i think, i got a kexec reject phone
P.S. is there any chance in future for my phone to run kexec ROMs??
aki2cool said:
Devesh once again, but i edited recovery.fstb file, i think, i got a kexec reject phone
P.S. is there any chance in future for my phone to run kexec ROMs??
Click to expand...
Click to collapse
If that's the case then your only chances are the non kexec ROMs as of now.
But yeah work is going on to make kexec boot for everyone.Have patience
Thanks
Tech-G.ONE said:
On which version of PAC man u get that problem...
When I installed 12 june version (I think) i get that problem (kexec)...
But on 22 june update i cannot get that problem...so try to install new version...
& u r on 4.1.2 so u cannot install non-kexec roms on phone, like me... so u have to install kexec roms...
try other roms... search & installed other kexec roms... (because if other roms r installing then ur bootloader is OK)
If u want, i will give my installed kexec roms link...
If u think this information is helpful for u then just HIT below THANKS Button...
Happy Multi-booting...
Click to expand...
Click to collapse
I have the latest PAC, i think I've to fxz back to ics & install PAC (non-kexec)
Thanks anyways
BTW to the OP
I don't see the meaning of this thread.
Why would you create a thread to just ask about custom ROMs when you can just search for them and especially when there already is a thread(here) having the solution to your problem in the first place.
Search before posting and creating new threads dude.Posts like these clutter up the forum and then you say there's too much stuff to go through and become confused.
Act responsibly and follow the rules.
deveshmanish said:
If that's the case then your only chances are the non kexec ROMs as of now.
But yeah work is going on to make kexec boot for everyone.Have patience
Click to expand...
Click to collapse
Thanks devesh, we have faith in you devs, till something comes up, will fxz back to ics to try PAC (by Ravi)
aki2cool said:
Thanks devesh, we have faith in you devs, till something comes up, will fxz back to ics to try PAC (by Ravi)
Click to expand...
Click to collapse
OK. you installed botstrap before BMM installation ?
& u checked other roms (kexec) ???
for BMM, watch the video which I made on my Atrix 2... I am going to delete it... I will delete it later...
Just watch video & check whether u missed something or not...
& if you correctly followed all step then I think it is phone problem...
Video thread : click HERE
If u think this information is helpful for u then just HIT below THANKS Button...
So i'm having some trouble here.
Anything such as CM10.1 or any CM or related custom rom I install gets unstable after x amount of days.
And any CM based rom has the poorest battery life I could ever imagine. I've wiped everything multiple times. I've attempted to full restore and start over on a fully "reset" phone. It's killing me - as I'm an active college student who doesn't have time to sit around a wall outlet anymore [like I use to] to always have a good phone charge.
Anything else either turns out to be;
Unstable -or
Laggy -or
Fail to flash correctly -or
Camera and/or Gallery either isn't there, won't load, crashes, or fails to even hint about being usable.
I honestly am about to just dump this phone, as the screen is already cracked. And development slowed to a halt it seems.
I said screw it the other night, and went to install CleanRom 6.5, only to find that it starts installing [after clicking through my options in Aroma] andd loads for 1-4 seconds then says "DONE" with 0% completed and says everything installed perfectly. However when I go to reboot TWRP notified me I had no OS installed which made sense considering I've never had a rom install in <5 seconds.
Moving on though, anyone have any suggestions? And I do mean any? I've used the OneX tool for everything, AND done the usual [root/unlock/recovery/s-off -> custom rom] with that and manually to have no success between the two. Do I just have a busted device? Something faulty perhaps in the circuit board? I honestly haven't a clue. But all I know is, CM is and probably will forever be my favorite. However my phone died yesterday after 3 hours of sitting in my pocket and today I barely touched it compared to my normal use on sense based or other roms which I'll get 8+ hours out of. I just don't know what to do anymore. I use to consider myself a flash-a-holic where I'd be reinstalling ROM after ROM just to see what all the amazing and different features they have - then running new kernels. But now it isn't even usable.
My signal has also been in the toilet. A friend of mine has the same exact phone and we can put them right next to each other, he'll have full bars on AT&T and i'll have one or two [if i'm lucky]. I've flashed every radio up and down - back and forth. Flashed the radio and all else EXACTLY like his phone and I quickly found myself stuck in a hole with a better paperweight than phone. My last effort was to do wipe after wipe and battery calibration apps hoping that may be my problem and I'm stupid for over thinking it. But... if anything it made it worse.
Should I dump it? or is there hope. . .
I don't see how it could be my battery considering.. well... roms OTHER than those based on CM have been perfect on battery life just like they were when I first got the phone. But they don't have operable camera and/or gallery. I also uploaded a picture of my past 8~ hours with this phone. Note the past 2/3 hours. I know I've noticed some "slight" change..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What Hboot?
What recovery/version?
S-ON or S-OFF?
You said you'd tried wiping, have you tried RUU?
Edit: that said, don't just go flashing running RUUs, unless you're s-off.
As for battery drain, disable Google location services while you are on wi-fi. It really kills aosp roms For other issues see Exad's reply above. Easier to help with more information.
Sent from my HTC One X using xda premium
exad said:
What Hboot?
What recovery/version?
S-ON or S-OFF?
Click to expand...
Click to collapse
HBoot- 2.14.0000
TWRP- [tried the past couple versions, hoping maybe its just a bug with one but stuck with] 2.5.0.0
S-OFF
Venomtester said:
As for battery drain, disable Google location services while you are on wi-fi. It really kills aosp roms For other issues see Exad's reply above. Easier to help with more information.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Alright, I'll try that - even though I rarely use any GPS or related service.
RollTribe said:
You said you'd tried wiping, have you tried RUU?
Edit: that said, don't just go flashing running RUUs, unless you're s-off.
Click to expand...
Click to collapse
Yup.
TKTAB911 said:
HBoot- 2.14.0000
TWRP- [tried the past couple versions, hoping maybe its just a bug with one but stuck with] 2.5.0.0
S-OFF
Alright, I'll try that - even though I rarely use any GPS or related service.
Yup.
Click to expand...
Click to collapse
download twrp 2.6: http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.6.0.0-evita.img
Check md5
fastboot flash recovery OpenRecovery/evita/openrecovery-twrp-2.6.0.0-evita.img
fastboot reboot bootloader
fastboot erase cache
select bootloader on phone screen
select recovery on phone screen
Wipe
Advanced
Select everything, except sd card unless you want to wipe your sd card
check md5 of your rom on your pc.
copy and flash your rom.