Related
I'm running UnNamed 1.3.0 right now with no themes applied but I have everything setup the way I like it. I'd like to do a full 1.3.1 flash and try the Blue Monkey theme.
Is the best way to do this
A) backup apps with Titanium, backup with CWM, full wipe, flash 1.3.1 full, then flash blue monkey, restore apps with Titanium
B) backup with CWM, flash 1.3.1 over 1.3, then flash blue monkey theme
C) other
I'm unclear on whether I need to do a wipe going from 1.3 to 1.3.1 if it's a full flash and not the 1.3to1.3.1 update.
Thanks in advance for any help.
dont need to wipe. just flash it.
You can wipe cache and dalvik to clean up, but you don't need to wipe.
Alright, I did a backup then installed 1.3.1 and rebooted. Everything works fine and the phone looks exactly how I left it except in the about phone area it says I'm running 1.3.1 now.
Rebooted and backed up again.
Installed from zip the Blue Monkey theme and rebooted. I'm running Go Launcher Ex so I went in and cleared it as the default. Pressed the home button and chose TwLauncher. Everything looks fine but I'm not seeing the theme applied. I still have the same background live wallpaper and icons. The lock screen is still WidgetLocker.
Thoughts?
EDIT:
Apparently installing the theme a second time did the trick. I now see the new icons.
Knips178 said:
EDIT:
Apparently installing the theme a second time did the trick. I now see the new icons.
Click to expand...
Click to collapse
Right on. That's good advice for everyone. Sometimes things need more than one flash.
Sent from my páhhōniē
I had the same thing happen with that theme on 1.3.1. I knew something was up when it flashed really fast. A second flash took longer and worked properly.
Sent from my SAMSUNG-SGH-I777 using xda premium
Can anyone give a quick reply as to why that happens with flashing? Is it a problem with CWM, the zip files, or the process?
Knips178 said:
Can anyone give a quick reply as to why that happens with flashing? Is it a problem with CWM, the zip files, or the process?
Click to expand...
Click to collapse
Lol, I think alot of us wish we knew why. I don't think anyone has figured it out. It's not limited to our phone.
Sent from my páhhōniē
gr8hairy1 said:
Lol, I think alot of us wish we knew why. I don't think anyone has figured it out. It's not limited to our phone.
Sent from my páhhōniē
Click to expand...
Click to collapse
I think I have posted this twice today and the third time might...be the charm. You guys have to remember to check and mount your system and data in recovery before flashing ROM's or Themes. It should alleviate any re-flashing or multi-flash scenarios for you guys.
Additional: Also if some of you guys are having a bad or fast install you might want to re-download the Theme. I know in talking with Jivy26 (Blue Monkey Themer) the initial release of the update of 1.3 (For you quick and early adopters) had an issue and was pulled, repacked and posted again. Try a fresh copy.
hkeyman said:
I think I have posted this twice today and the third time might...be the charm. You guys have to remember to check and mount your system and data in recovery before flashing ROM's or Themes. It should alleviate any re-flashing or multi-flash scenarios for you guys.
Click to expand...
Click to collapse
Very true. But it's still only a 'should' not have to flash twice, not a certainty that it won't need the flash again.
It doesn't explain the times we do that and it still needs a reflash (usually cm7).
Sent from my páhhōniē
gr8hairy1 said:
Very true. But it's still only a 'should' not have to flash twice, not a certainty that it won't need the flash again.
It doesn't explain the times we do that and it still needs a reflash (usually cm7).
Sent from my páhhōniē
Click to expand...
Click to collapse
I used to see the same thing with flashing multiple times, thought it might have been a bad root install or something wrong with the ROM itself. Ever since implementing the mentioned procedure into my regimen of updates. I only flash once (Unless of course there is in fact something wrong with the package).
Okay I have been trying to get a CM9 rom to boot on my Atrix for about a week now. I am coming from Nottachtrix 1.3.1 on radio 37p with faux GB24 kernel. My bootloader is unlocked and I perform all necessary wipes before install. The furthest I have gotten any of the CM9 roms to boot is the screen that states Android Apps(or something) updateing. It then states starting system and boots back to the booting logo. I have tried fastboot -w. Formating data, cache, system, osh, pre install in mounts storage menu, and clearing both caches before and after install and I get the same results. This only happens with CM9 roms. I cannot get the CNA, Jokers, Turls, or Atrix tablet past the screen stated. I have tried with the latest rom racer from http://forum.xda-developers.com/showthread.php?t=1204500 and both recovery and touch recovery from rom manager and I get the same results. I have posted my issue in the dev section, but decided this was better as I did not want to clutter up the dev forum with my problems. Could it just be my Atrix or would the 37p radio have something to do with the bootlooping issue. Any help would be very much appreciated.
For some odd reason I decided to pull my external SD card before boot, and freaking BOOM BANG POW NO BOOTLOOP!
htcslic said:
Okay I have been trying to get a CM9 rom to boot on my Atrix for about a week now. I am coming from Nottachtrix 1.3.1 on radio 37p with faux GB24 kernel. My bootloader is unlocked and I perform all necessary wipes before install. The furthest I have gotten any of the CM9 roms to boot is the screen that states Android Apps(or something) updateing. It then states starting system and boots back to the booting logo. I have tried fastboot -w. Formating data, cache, system, osh, pre install in mounts storage menu, and clearing both caches before and after install and I get the same results. This only happens with CM9 roms. I cannot get the CNA, Jokers, Turls, or Atrix tablet past the screen stated. I have tried with the latest rom racer from http://forum.xda-developers.com/showthread.php?t=1204500 and both recovery and touch recovery from rom manager and I get the same results. I have posted my issue in the dev section, but decided this was better as I did not want to clutter up the dev forum with my problems. Could it just be my Atrix or would the 37p radio have something to do with the bootlooping issue. Any help would be very much appreciated.
Click to expand...
Click to collapse
Did you flash twice ?
Sent from my MB860 using XDA
I believe the problem is with the radio, I had this issue (on stock radio), then I upgraded to the newest CM9 Kang (0.4.4) and it went away. I then flashed the 37p radio in an attempt to fix a problem I've been having with my WiFi and bluetooth (they both don't work and cause reboots, I assume now it's a hardware problem) and the boot loop came back. I'm gonna try flashing some other radios to see if that works.
Yes flashed twice to no avail. Gonna try the 36p radio and stock to see if that fixes my issue.
Sent from my Wettest Dream Atrix!
giqbal said:
Did you flash twice ?
Sent from my MB860 using XDA
Click to expand...
Click to collapse
No need to flash any ROM twice. Not going to discuss other than to say its not require
OP......Not your phone or radio. There is something you are doing incorrectly. Quite possibly wipe procedure. If I remember when I am at my PC in the morning I will PM you exact instructions, start to finish, for flashing one of the CM9 builds.
Sent from my MB860 using xda premium
CaelanT said:
No need to flash any ROM twice. Not going to discuss other than to say its not require
OP......Not your phone or radio. There is something you are doing incorrectly. Quite possibly wipe procedure. If I remember when I am at my PC in the morning I will PM you exact instructions, start to finish, for flashing one of the CM9 builds.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Trust me, the CM9 kang (not turl's version, haven't tried that) didn't work unless you flashed it twice up to version 0.4.2 (I skipped 0.4.3 and installed 0.4.4 straight without wiping and only flashed once and it worked, so it's possible they fixed the bug). I don't think anyone knows why, but it's been confirmed many times.
CaelanT said:
No need to flash any ROM twice. Not going to discuss other than to say its not require
OP......Not your phone or radio. There is something you are doing incorrectly. Quite possibly wipe procedure. If I remember when I am at my PC in the morning I will PM you exact instructions, start to finish, for flashing one of the CM9 builds.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
That is what I am hoping, but I have tried every procedure I could find within the forums. Your start to finish is gonna be my last hope.
So I followed the same steps I use for other roms and managed to get this one working http://forum.xda-developers.com/showthread.php?t=1580449
Hey CaelanT any luck on getting me a step by step.
hitmannumber47 said:
Trust me, the CM9 kang (not turl's version, haven't tried that) didn't work unless you flashed it twice up to version 0.4.2 (I skipped 0.4.3 and installed 0.4.4 straight without wiping and only flashed once and it worked, so it's possible they fixed the bug). I don't think anyone knows why, but it's been confirmed many times.
Click to expand...
Click to collapse
Haven't had to do that with jokersax, turl, or CNA versions.
---------- Post added at 12:24 PM ---------- Previous post was at 12:24 PM ----------
htcslic said:
Hey CaelanT any luck on getting me a step by step.
Click to expand...
Click to collapse
Thanks for reminding me. Will get something to you here in a few!
<edit> Check your messages!
Gonna give it a shot soon as I get off work.
EDIT:
Unfortunately that was a no go as well. Followed everything to a tee and tried different kernels. I can only get the AOKP rom to boot, but its is currently without USB storage. Does anyone know a difference in the roms that would cause my Atrix to boot on one and not the other. I can also manage to get the MIUI to boot.
htcslic said:
Gonna give it a shot soon as I get off work.
EDIT:
Unfortunately that was a no go as well. Followed everything to a tee and tried different kernels. I can only get the AOKP rom to boot, but its is currently without USB storage. Does anyone know a difference in the roms that would cause my Atrix to boot on one and not the other. I can also manage to get the MIUI to boot.
Click to expand...
Click to collapse
I think something is going on with the kernel. You may have a bad processor. That's where my train of thought is right now. Sorry I couldn't get you up and running!
CaelanT said:
I think something is going on with the kernel. You may have a bad processor. That's where my train of thought is right now. Sorry I couldn't get you up and running!
Click to expand...
Click to collapse
Thanks for all you help. Finally got it to boot by removing external sd card.
[EDIT] Not sure but I believe the problem I had with m external sd is I still had an ext4 primary partition on it from when I was using Webtop2SD. Copying everything over to pc now and reformating external to see if my assumption is correct.
Looks like the ext4 partition on as was the culprit.
Sent from my Flipping ArtixTab!
I'm still new to the forum so I can't post anything in they development section but I tried flashing kitchen sink 1.3 but when it boots up it says UI system stopped pls if anybody knows a fix for that I would really appreciate if you can help me
Sent from my MB855 using xda premium
What options did you install? and was it MIUI or AOKP or CNA?
Dovigoldberger said:
I'm still new to the forum so I can't post anything in they development section but I tried flashing kitchen sink 1.3 but when it boots up it says UI system stopped pls if anybody knows a fix for that I would really appreciate if you can help me
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
dont wipe before flashing the zip it needs to be flashed directly on top of a working rom and also whjich rom and options did you pick
i installed it thru aroma installer i picked all default i picked cna and i added beats audio and i picked full wipe
Beats audio, I remember reading with beats, soft keys, or the ics reloaded, usually well give it a problem. As someone else said, install on top of a working ROM and leave those options off. Shouldn't have a problem.
Sent from my MB855 using xda premium
This is what I did and it works perfectly
Must be on 198_6 or 198_7 - I wasn't so I SBF'd to 198_6
Before SBF if on something else run a factory reset from within CWM.
SBF to 198_6 or 7
Factory Reset from CWM
Boot into stock, Don't setup account, just update PRL and Profile
Boot into CWM
I wiped cache and data ONLY
flashing w/o wiping - CNA needs somethings to work right
Flash again
Flash Gapps Reboot, set up accounts
Enjoy
Soft Keys and ICS reloaded will cause boot loops. I chose beats audio, but I don't see it anywhere.
So far everything is good for me.
My MoPho's in the kitchen sink!!
Hello
first off let me say thanks in advance to anyone who can help me shed some light on this matter.
im trying to follow forum rules (i have used them before) and used the search function. so if i missed it im sorry. but here is as much info as i can give.
so i have a Tmobile samsung galaxy s vibrant. great phone love it. it had eclair on it. i used samsung kies to update it to froyo 2.2. that was the most i knew you could update a phone. until i found out you can do more. so i instantly wanted to flash to a the best ROM i could find info and was directed to the jelly bean Rom. i initially wanted to try the helly bean ROM (not sure if there is a difference) but im new to this and went with the rom i could find the most info on. found this guy on youtube. since i can post out side links yet. he calls him self "DJ eddie one" who was also recommended by the team passion forum. again im new to this so bare with me. so i tried to go through the process. I'm sure you all know that you cant just go from froyo to another rom. so i had to go back to stock. i re flashed the phone back to eclair via Odin by the same guy in his "return vibrant back to stock" video no problem. back everything up and made it back to stock. touch screen has response and i can unlock the phone and use it like normal. here is the deal now. after i went through the whole process of flashing it and going from ICS to slim bean and then to jelly bean. the home screen comes up and says "swipe here" or "touch here" or "start" or what ever. the screen does not respond. the volume buttons raise the volume and the power button turns the screen off and if i hold the power power button i get the "airplane mode"/"power off" options but cannot select anything. i thought i had done something wrong so i did the process over again. 3 times. even stopped at each rom change just to check it out as i processed through the process. no change. flash back to Eclair stock. and it works fine.
please help. i hate elcair. im sick of it. i want my free mobile hot spot back so i can listen to NPR news ap on my ipod touch in my car cuz i dont have a radio. and froyo blows too. if you're wondering why i can afford a snazzy phone and ipod touch but not a car stereo its because i drive an RX7. Cheers please help! i sure hope its something stupid (almost always is with me) i tend to over think things. plus i work on PCs and MACs for a living. i setup freaking networks for Allah sake. its frustrating to get stuck on a some phone software. AAAAHHHHHAAA.. *end rant*
thanks again.
hysterically yours
:cyclops:
Bunta
Well if your running hellybean. It sounds like it might just be a bad flash. Don't Odin back to stock.
1.go into recovery and format system.
2. Wipe cache.
3. Go into advanced settings and wipe dalvik cache.
4 go into mounts and storage and format /boot and format /system.
Reflaah the hellybean allinone(it depends which hellybean build were you flashing)
5.flash the hellybean add on and reeboot
Sent from my SGH-T959 using xda app-developers app
skinzy98 said:
Well if your running hellybean. It sounds like it might just be a bad flash. Don't Odin back to stock.
1.go into recovery and format system.
2. Wipe cache.
3. Go into advanced settings and wipe dalvik cache.
4 go into mounts and storage and format /boot and format /system.
Reflaah the hellybean allinone(it depends which hellybean build were you flashing)
5.flash the hellybean add on and reeboot
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
ok,
so i did all that and still no change. but im pretty sure i must have missed something when i initially flashed the phone. cuz i have no idea what the hellybean add on is you speak of.
Go to the Helly Bean thread in the developers forum. Go to page one and it should have a link to the addon package.
I had a glitch like yours one time where the touch screen acted like it was unplugged (for lack of better way to describe it). I popped battery out and rebooted and it was fine.
If not, Odin back to stock and follow my guide I posted in the Status 7 error thread. Page 3 I think.
Sent from my SGH-T959 using xda app-developers app
Try flashing CM10 instead of Helly Bean. Helly_Bean's installation can be somewhat tedious, but CM10 is just one zip file. Here is a link:http://forum.xda-developers.com/showthread.php?t=1775271
ali1276 said:
Try flashing CM10 instead of Helly Bean. Helly_Bean's installation can be somewhat tedious, but CM10 is just one zip file. Here is a link:http://forum.xda-developers.com/showthread.php?t=1775271
Click to expand...
Click to collapse
Well now the hellybean ROM got its all in one finally. But seems you may need to somehow fix the calibration of the screen.
Sent from my SGH-T959 using xda app-developers app
Toast6977 said:
Go to the Helly Bean thread in the developers forum. Go to page one and it should have a link to the addon package.
I had a glitch like yours one time where the touch screen acted like it was unplugged (for lack of better way to describe it). I popped battery out and rebooted and it was fine.
If not, Odin back to stock and follow my guide I posted in the Status 7 error thread. Page 3 I think.
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Ok i just want to verify that i found the correct link you were talking about. there are so many in here with all them 4 million users.
Helly bean link. http://forum.xda-developers.com/showthread.php?t=1783064
and i cant seem to find that status 7 error thread you mentioned.
also one question. can i add the addon to the phones sd without having to flash back to stock?
ali1276 said:
Try flashing CM10 instead of Helly Bean. Helly_Bean's installation can be somewhat tedious, but CM10 is just one zip file. Here is a link:http://forum.xda-developers.com/showthread.php?t=1775271
Click to expand...
Click to collapse
Also thanks for your help. i may try this as well. i just want to get this thing working.
past namprefi
iKoolkid said:
Well now the hellybean ROM got its all in one finally. But seems you may need to somehow fix the calibration of the screen.
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
and how would i do that? i mean what would cause the screen not to work? i was fine when eclair was on it and fine when foryo was on it. i go through the process of flashing it to ICS Passion then to Slim Bean and then to Jelly Bean and the screen just stops? i even stopped at eat Flash cuz i wanted to see what they looked like before made it to jelly bean. and each one the screen did work. i was thinking some sort of kernel file handles that or driver? correct me if im wrong.
rotary_bünta said:
Ok i just want to verify that i found the correct link you were talking about. there are so many in here with all them 4 million users.
Helly bean link. http://forum.xda-developers.com/showthread.php?t=1783064
Click to expand...
Click to collapse
Well, that link is wrong, that is for the captivate, not the vibrant. Make sure that you are in the vibrant development section before flashing a rom. Here is the vibrant hellybean link: http://forum.xda-developers.com/showthread.php?t=1811241
rotary_bünta said:
Ok i just want to verify that i found the correct link you were talking about. there are so many in here with all them 4 million users.
Helly bean link. http://forum.xda-developers.com/showthread.php?t=1783064
and i cant seem to find that status 7 error thread you mentioned.
also one question. can i add the addon to the phones sd without having to flash back to stock?
Also thanks for your help. i may try this as well. i just want to get this thing working.
Click to expand...
Click to collapse
http://rootaxbox.no-ip.org/derteufel/Helly_Bean/addons/
That is the link for the addon package. Choose the one for Helly Bean. Its up to you whether its the regular or inverted. Should be able to just flash away.
http://forum.xda-developers.com/showthread.php?p=30237539
The second link is for the install method I used. It may be overkill, but its the only way that would work for me, and it gave me a good clean install. It looks like a lot but it really doesnt take long..
I'm sorry guys bare with me. while i try to grasp this. im currently running the recovery software CWM-based recovery V6.0.1.1
since i cant get the ROM to work the screen can i mount the phone to USB drive from that recovery? or do i need to Odin back to stock and start over? so that i can mount back the USB and transfer the files i need.
ali1276 said:
Well, that link is wrong, that is for the captivate, not the vibrant. Make sure that you are in the vibrant development section before flashing a rom. Here is the vibrant hellybean link: http://forum.xda-developers.com/showthread.php?t=1811241
Click to expand...
Click to collapse
Thank you for clearing up that link for me.
In that thread stated are the files i need to flash the phone. in there is this link (http://rootaxbox.no-ip.org/derteufel/Helly_Bean/) which i have been to before. i guess i got confused as to what files i needed from the link because there are a few directories in there with lots of other files and i wasnt sure which i needed. Example; in that link if i click on kernel link it takes me to the next directory with numbers. ( i assume these are versions) then if i click on 113 it takes me to another dir of files. i can only assume i want the one that is lableled "Devil3_1.1.3_HB_vibrant_CFS_BLN_VC_20120807.zip"
im just confused as to what files i do need and what i dont need. im sorry to be such a pest.
Toast6977 said:
http://rootaxbox.no-ip.org/derteufel/Helly_Bean/addons/
That is the link for the addon package. Choose the one for Helly Bean. Its up to you whether its the regular or inverted. Should be able to just flash away.
http://forum.xda-developers.com/showthread.php?p=30237539
The second link is for the install method I used. It may be overkill, but its the only way that would work for me, and it gave me a good clean install. It looks like a lot but it really doesnt take long..
Click to expand...
Click to collapse
thanks toast;
whats the difference of the inverted as apposed to the regular? if i try one can i go back to try the other?
in reference to your second link;
i can flash back to sock with odin no problem.
the rest of the items needed on the list though
Gingerbread bootloader installed
-Bionix V fishman ROM (2.2 with Bali kernel, any 2.2 ROM may do.. YMMV)
-latest CM9 nightly (ICS)
-latest Helly Bean All In One and Add-on package.
i can get this from the same link?
The rest of the items you'll need to search for. GB boot loaders has a whole sticky devoted to it, how to do it, etc.
You can find the bionix ROM and CM9 nighty (ICS) in the android development forum (hit your back button once and you should see the development forum)
You'll be fine, just download everything you need, follow instructions, and you'll be set.
I've never used inverted apps, I assume it changes the look of them.
Toast6977 said:
The rest of the items you'll need to search for. GB boot loaders has a whole sticky devoted to it, how to do it, etc.
You can find the bionix ROM and CM9 nighty (ICS) in the android development forum (hit your back button once and you should see the development forum)
You'll be fine, just download everything you need, follow instructions, and you'll be set.
I've never used inverted apps, I assume it changes the look of them.
Click to expand...
Click to collapse
Alright toast,
just verify with me that i found the right stuff here so i don't go on some wild goose chase.
Bionix V fishman ROM (2.2 with Bali kernel, any 2.2 ROM may do.. YMMV)
fond here http://forum.xda-developers.com/showthread.php?t=1441976
latest CM9 nightly (ICS)
http://forum.xda-developers.com/showthread.php?t=1575170
the Helly bean and add on package was post already
this one i think http://rootaxbox.no-ip.org/derteufel/Helly_Bean/addons/
Yep.. with the Bionix ROM, I download and flashed the package via CWM, I didn't use the Odin image. Either way should work fine. Your last link is directly to the add-on package, here is the link to the ROM http://rootaxbox.no-ip.org/derteufel/Helly_Bean/rom/
I would download and use the 8/13 build of Helly Bean. If you have any questions feel free to PM me.
Just don't forget to flash to GB bootloader. You may have done that already, if not read about and follow the instructions here: http://forum.xda-developers.com/showthread.php?t=1117990
Have fun!
The inverted gapps change white to black and black to white, for example in gmail the screen will be black and red with white writing.
There are two benefits from this
1. They look cool IMO.
2. It uses less battery, white screens draw more current.
sent from my magic box to yours
Rotary, just received your pm. Seems like your still in the same boat. Touch screen not working.
Can you confirm your status now? It appeared that your touch screen will work while on eclair, but on no other ROM. Is that still your current situation?
Hey toast just looking over the thread, don't know if he still needs it but the hellybean zip he posted is a kernel zip not the ROM.
Sent from my SGH-T959 using xda premium
Update on this thread:
Last night via GTalk Rotary_Bunta and I:
1) Odined to stock, booted up checked touch screen. Worked good.
2) Flashed Bionix V, booted, touch screen working good.
3) Flashed GB bootloader, reboot checked touch screen.. working good.
4) Flashed CM9 Nightly... touch screen not working.
5) decided to proceed to see if phone just hated the ICS ROM, and flashed Helly Bean. Flashed x2, installed add-ons and touch screen doesn't work. Boots up and cannot slide ring to unlock screen.
Toast6977 said:
Update on this thread:
Last night via GTalk Rotary_Bunta and I:
1) Odined to stock, booted up checked touch screen. Worked good.
2) Flashed Bionix V, booted, touch screen working good.
3) Flashed GB bootloader, reboot checked touch screen.. working good.
4) Flashed CM9 Nightly... touch screen not working.
5) decided to proceed to see if phone just hated the ICS ROM, and flashed Helly Bean. Flashed x2, installed add-ons and touch screen doesn't work. Boots up and cannot slide ring to unlock screen.
Click to expand...
Click to collapse
Flash CM7 and then tell me results of that.
Sent from my SGH-T959 using xda app-developers app
Update: He flashed CM7 = no touch screen response.
Tried different kernels. Power button won't even wake screen. Flash back to 2.1 or 2.2 and all is well. Touch screen and buttons work just fine.
Flashed Glitch kernel w/ cm7 to see if there were any changes at all, made no difference.
I just did the newest OTA for MeanBean 2.8. I was having issues with crashing. I also tried a fresh install of MeanBean 2.8 after a full wipe and it seems to have gotten worse for me. I know it isn't the ROM itself because MeanBean is just pure awesome. On the fresh install, I was getting as far as entering my account information for Dropbox during the first time setup and during typing the white text boxes would turn black and the screen would start to sort of dim/flick. I re-installed the previous version of MeanBean 2.71 and all of my problems have vanished.
I would have posted this in the MeanBean ROM thread but I'm not allowed to yet.
seansratigan said:
I just did the newest OTA for MeanBean 2.8. I was having issues with crashing. I also tried a fresh install of MeanBean 2.8 after a full wipe and it seems to have gotten worse for me. I know it isn't the ROM itself because MeanBean is just pure awesome. On the fresh install, I was getting as far as entering my account information for Dropbox during the first time setup and during typing the white text boxes would turn black and the screen would start to sort of dim/flick. I re-installed the previous version of MeanBean 2.71 and all of my problems have vanished.
I would have posted this in the MeanBean ROM thread but I'm not allowed to yet.
Click to expand...
Click to collapse
No issues here. Flashed it about 45 minutes ago and all is good. You might try going into recovery and flashing the sticky settings .zip file in the MeanBean folder. This will bring up the Aroma installer where you can make changes to the ROM. You might want to choose the option to overvolt. Some phones just like to play differently when it comes to overclocking and voltages. You might also try a clean install instead of a dirty one.
Sent using my HTC EVO LTE and a magic wand
yea its running perfect for me also
You probably got a bad download. Just redownload the Rom
Sent from my EVO using xda premium
Try fix permissions, you may need to wipe and start fresh if apps keep crashing
Like mentioned above, you could turn on the option to overvolt, or you may just want to turn off overclocking entirely. I haven't had problems with it but some people's phones seem to not do well with overclocking.
I'd try redownloading the Rom, then in recovery wipe everything so fully clean install. Then flash Rom, and before you boot into Rom for the first time flash the sticky settings and just put all to pretty much stock then boot. If all works you can always go back and flash sticky settings again.
Sent from my EVO using xda premium
won't flash
I have HTC Evo 4g lte rooted and s-off
With super jelly milestone ROM
Twrp 2.4
I've clean wipe and it just won't flash mean bean 2.9
It go's back to fastboot
Please help
Might be the new TWRP that's causing the problem?
Sent from my Nexus 7 using xda app-developers app