Related
First off, thanks for all the help so far, this site is the best!
I just rooted my Evo using the unrevoked3. Had a little bit of trouble, nothing major, and overall it was a success. I also installed ROM Manager and Titanium Backup, based on suggestions found here.
The problem is, I'm not quite getting how to flash the roms... I downloaded one through ROM manager, and it seemed to work, but I didn't notice a single thing different. I tried to install CyanogenMod, and it downloaded, but it would always fail during the install.
I tried downloading on my computer, then moving the .zip file to my sdcard. Then I select "install rom from sdcard" and everything seems to go ok, I end up having to go into recovery and "rollback" my phone to the stock rom, because twice now I've almost bricked my phone.
Really, what I'm wanting is a setup like that "Kuma Style" one (without the animal), and a different bootscreen. I have spent a lot of time searching around, and it seems simple enough, I just seem to be missing some integral part of the proccess.....
Any help is appreciated!
Mark_Hardware said:
First off, thanks for all the help so far, this site is the best!
I just rooted my Evo using the unrevoked3. Had a little bit of trouble, nothing major, and overall it was a success. I also installed ROM Manager and Titanium Backup, based on suggestions found here.
The problem is, I'm not quite getting how to flash the roms... I downloaded one through ROM manager, and it seemed to work, but I didn't notice a single thing different. I tried to install CyanogenMod, and it downloaded, but it would always fail during the install.
I tried downloading on my computer, then moving the .zip file to my sdcard. Then I select "install rom from sdcard" and everything seems to go ok, I end up having to go into recovery and "rollback" my phone to the stock rom, because twice now I've almost bricked my phone.
Really, what I'm wanting is a setup like that "Kuma Style" one (without the animal), and a different bootscreen. I have spent a lot of time searching around, and it seems simple enough, I just seem to be missing some integral part of the proccess.....
Any help is appreciated!
Click to expand...
Click to collapse
I am not familiar with Unrevoked, but just running unrevoked doesn't completely root your phone. You need to do the second parts of rooting which unlocks nand.
Ah, so there is more to do. Maybe that's the problem then.... *off in search of how to unlock nand
Mark_Hardware said:
Ah, so there is more to do. Maybe that's the problem then.... *off in search of how to unlock nand
Click to expand...
Click to collapse
Unlocking nand just unlocks something so that you can save full image backups. That wouldn't lead to your phone not installing a ROM right, it's just something you'll want just in case things go wrong. So still finish the root and get nand. But that's not what you're missing here.
Possible error: Did you wipe settings &factory reset and wipe cache in ClockworkMod before flashing the ROM? I think that could lead to some problems.
Try flashing the alternative Amon Ra recovery through rom manager (will state that rom manager won't be fully functional unless clockworkmod is installed) and loading the roms onto the sd card then reboot into recovery. Amon Ra seems to work better imo than clockworkmod. When you're talking about something like "kuma style," those are themes that are usually flashable in recovery also. The boot animation could alse be flashable in recovery but if not, there are instructions on how to adb push custom ones onto your phone.
rugedraw said:
I am not familiar with Unrevoked, but just running unrevoked doesn't completely root your phone. You need to do the second parts of rooting which unlocks nand.
Click to expand...
Click to collapse
just fyi, the latest unrevoked (3.21) unlocks nand so u dont need to do it.
"unrevoked3 will permanently unlock NAND write protection by default on the following phones:
*
Sprint EVO 4G"
i'd link the wiki but i cant cuz i'm a new user lol
Gah! So I downloaded the enamored theme, moved it to the sd card, then went to ROM Manager and selected "Reboot into Recovery"and selected the enamored.zip. It said the install was a success, but when I rebooted, the phone stuck on the bootanimation. I tried restarting a couple times, but it always gets stuck in the same place.
I booted into recovery (if thats waht you call the hold the volume button down while pushing the power button trick), and selected recover, then nandroid, then a time under yesterdays date. Phone recovered fine.
WtH am I doing wrong? I realize I am way out of my league, but I'm not completely retarded. Again, GAH!
Are u wiping data and cache when flashing a ROM? I have been stuck at the CM6 boot animation when coming from a different Rom and not wiping.
Sent from my PC36100 using XDA App
Mark_Hardware said:
Gah! So I downloaded the enamored theme, moved it to the sd card, then went to ROM Manager and selected "Reboot into Recovery"and selected the enamored.zip. It said the install was a success, but when I rebooted, the phone stuck on the bootanimation. I tried restarting a couple times, but it always gets stuck in the same place.
I booted into recovery (if thats waht you call the hold the volume button down while pushing the power button trick), and selected recover, then nandroid, then a time under yesterdays date. Phone recovered fine.
WtH am I doing wrong? I realize I am way out of my league, but I'm not completely retarded. Again, GAH!
Click to expand...
Click to collapse
When you flash a theme, it could take up to 2-5 minutes to finish. This occurs during the boot animation. I flash themes all the time and I notice it's usually around 2-3 minutes wait. Maybe faster for others but that's just been my experience. If it's over 5 minutes than there's probably something wrong with your zip file or maybe clockworkmod recovery doesn't flash it properly. Also, it could be an issue with the kernel you're using...I noticed on kingklick cfs #10, I was stuck on boot animation for about 7 minutes and so I reverted back to the stock kernel and the theme was applied within 3 minutes.
ok, apparently I've been missing that step...
where do I do that again?
mizzos4 said:
When you flash a theme, it could take up to 2-5 minutes to finish. This occurs during the boot animation. I flash themes all the time and I notice it's usually around 2-3 minutes wait. Maybe faster for others but that's just been my experience. If it's over 5 minutes than there's probably something wrong with your zip file or maybe clockworkmod recovery doesn't flash it properly.
Click to expand...
Click to collapse
I waited a good long time. Am I at least headed in the right direction? Sorry to sound whiny, it's just that there's a few little things I want to do, and I'm intimidated as hell by actually doing any command line, so I'm hoping to avoid that- aka riding someone else's coattails
First, which rom are you using and is it stock or custom kernel? Are you using clockworkmod recovery? Try flashing the alternative amon ra recovery in rom manager then boot into recovery and apply your selected theme.
if you are using a stock rom it must say stock 2.2 deodexed
if it is not a deodexed rom.. of any kind.. then themes will say they flashed but they will either brick your phone or not work at all.
and stop using clockwork.... just use amon ra
Sent from my PC36100 using XDA App
I could be way off here, but I've seen some people who rooted using unrevoked, and run into trouble flashing things (or maybe I'm thinking of trouble with terminal commands) and it turned out they couldn't find flash_image anywhere in there SD card, Which should be installed (someone please correct me if I'm wrong).
I saw a lot of reports of this in chainsDDs superuser thread, if I remember correctly. They had to install flash_image.img (which is a file available on toasts part 2 root tutorial)
I obviously could be wrong about this, I've never used unrevoked, I rooted via toast, and his method included everything.
@ V_lestat
Thanks for the heads up about themes having the ability to brick your phone if not deodexed, I never knew that. I flash roms and kernels a lotbut never messed with themes much.
At OP, have a look at virus Rom thread. It's a great ROM, and he has built some different themes to go with it. Beautiful stuff, great ROM, great thread.
Good luck
Sent from my PC36100 using XDA App
See, some people say use clockwork, some people say Amon.
I looked around a lot beforehand, and people kept saying to use unrevoked, so I did. Now people say I should have used Toast?
Thanks for everybodies help so far, I am reading everything and taking it all in.
I Don't Mean to add any Confusion to your situation. I am new to this also.. I went with unrevoked also and when I booted into recovery with clockwork mod. I did a nand back up first to make sure if anything went wrong I could just boot back into recovery and load my backup. Then I wiped my Data & Davlick Cache all of the caches. Then I installed my Rom and it worked like a charm. I will add it did take about 5 to 7 mins to boot only on the first time though. I hope that helps some as to the process and what to do first don't give up XDA rocks with the smartest mind on the planet.
Mark_Hardware said:
ok, apparently I've been missing that step...
where do I do that again?
Click to expand...
Click to collapse
If you are using ROM Manager to "install zip from card" it presents you with a dialog with two unchecked check boxes. One of them is "wipe data + cache". make sure you check it before hitting ok on that dialog.
If you are manually booting into recovery then in the recovery choices you will see one that says wipe data and one thats says wipe davlik cache. first do a nandroid back up then wipe those data and davlik then install the rom. By the way are you just installing a theme or a full rom that might be the issue i am just wondering maybe a senior member can help on wether you can install a theme over a rooted stock theme or not?
Success!
I went into ROM Manager, backed up current ROM, went into recovery manually, wiped the cache, then installed from zip, and it worked! I tried a cool theme I found, and I like it, but it seemed old. I just installed fresh, and the enamored theme, and all is working great!
A couple more questions,
1) how do I get my contacts back?
2) How do I get my apps back onto my phone? I have them backed up on appbrain, but I haven't been able to find how to get them back to the phone.
So far, I've tried a couple of ROM's (and/or themes) and I've ended up flashing back to my own "safe" one, until I figure these two things out.
A tremendous thanks to everyones help! I seriously couldn't have done it without you guys
Edit; Oh yeah, one other thing. How do I delete the other nand backups? There's like 5, and I need to free up some memory. I tried going in and selecting one to see if it gave me the option to delete, but I didn't see anywhere that it did.... Got it. Search feature to the rescue
Most of this info may be extraneous, but I'll throw it in here just in case.
A few days ago, I decided to root my Evo 4G from the stock, 2.2 OS (HTC Sense?) using the Unrevoked website (using a PC running XP). It worked fine and got me rooted. Trouble began to arise when I attempted to install new ROMs such as CM-6 and Salvage. I decided to fork out a few bucks and pay for the ROM Manager Pro app, thinking that it would save me considerable hassle. After downloading the most recent CyanogenMod 7.0.0-RC2 through the app, I selected the "Install Gapps as well" option but did NOT check "Wipe Data and Cache" before letting the app do its work of installing and flashing and whatever for me. Upon completion of the installation, my phone then automatically rebooted normally, but became stuck on the boot image of the android on the skateboard with the spinning arrow. I let that sit for about 6 hours (I went to bed) thinking it was just first-time setup before I battery-pulled and booted into recovery, restored my original settings, and started over. This time I did everything the same except remembered to check "Wipe Data and Cache," as an online tutorial told me I ought to when switching from stock to another ROM, and it installed and booted correctly. I ran CM-7 for a day before deciding to try out a different ROM, downloading and installing it through the same interface, ROM Manager Pro. Everything went well until it got stuck, again, at the boot image. After about 30 min I battery-pulled and tried to restore back to CM-7, only to be greeted by another endless boot image. I was able to restore back to my original backup, but am now back to square one. What the heck am I doing wrong?
EDIT: That original backup I mentioned was made immediately after rooting the phone in preparation to install CM-7.
Sorry my technical knowledge is grossly lacking, I just got into this game. Patience and any help is GREATLY appreciated.
When switching from one rom to another, it is always important to remember to wipe data and cache. There are a few rare cases that it is not necessary to do this, but I really recommend that if you are just starting out, wipe them both for good measure until you learn enough that you can tell when you can get away with not wiping. Also, I know that one common problem that people experience with Rom Manager is that Unrevoked contains the Amon_RA recovery image, and Rom Manager is designed to with with the Clockwordmod recovery. In Rom Manager, you should be able to see which one you are currently using, and you should also be able to use Rom Manager to download and flash the latest Clockworkmod recovery. I too use Rom Manager as a convenient way of making sure that my rom is up to date, and to download roms, but I recommend that when you want to change roms, you do it by booting into recovery mode, and performing the wipe and install manually, as I have found that this method will help prevent errors like boot loops. I hope this helps!
P.S. Feel free to PM me if you ever need any help.
Sent from my DESTROYED Evo using XDA Premium app
So, for example, if I wanted to restore back to my CM-7 backup, would I want to boot into recovery and just restore to the backup or re-flash the ROM, then boot into recovery and try to restore it? I'm still getting the endless boot image.
Oh, and I am running clockworkmod, as per the instructions for ROM Manager.
Thanks for the quick reply!
Move CM7-RC2.zip and the gapps.zip (or whatever its name; ex: filename.zip) to the root of your SD card by plugging it into your computer via USB and mounting it as a drive. Go ahead and exit all that.
Turn off your phone.
Hold volume down + power.
Go to Recovery.
Wipe the following: data/factory reset, cache, (in Advanced, accessed from same menu) wipe dalvik.
Go back.
Install .zip from SD.
Choose your .zip(s) [CM7, Gapps] from your card, flash, and presto!
I'm not too experienced with ROM Manager as I do not use it whatsoever, but I know the above stated method should work perfectly.
Furthermore,
I'm not sure if a format_all.zip should be used here with CM7. If someone who knows would like to chime in about this, that'd be great.
totalanonymity said:
Move CM7-RC2.zip (or whatever it's name; ex: filename.zip) to the root of your SD card by plugging it into your computer via USB and mounting it as a drive. Go ahead and exit all that.
Turn off your phone.
Hold volume down + power.
Go to Recovery.
Wipe the following: data/factory reset, cache, (in Advanced, accessed from same menu) wipe dalvik.
Go back.
Install .zip from SD.
Choose your .zip from your card, flash, and presto!
I'm not too experienced with ROM Manager as I do not use it whatsoever, but I know the above stated method should work perfectly.
Furthermore,
I'm not sure if a format_all.zip should be used here with CM7. If someone who knows would like to chime in about this, that'd be great.
Click to expand...
Click to collapse
This is the way I would flash any roms that you want from here on out.
I have used CM7 and have not had to use the format.zip from calk, so I don't think it is absolutely necessary, but it probably wouldn't hurt.
Sent from my DESTROYED Evo using XDA Premium app
I recommend flashing the format all zip whenever switching ROMs. It completely formats the various partitions and leaves a blank slate for the new ROM to be installed. I also recommend using ROM Manager to flash Amon_Ra recovery and do everything manually instead of using ROM Manager. People seem to have a lot less problems with Amon, and I have never had any issues flashing ROMs or kernels or anything with it.
You won't be able to restore a Clockwork backup with it but it never hurts to just flash a new ROM and restore your Titanium backups, assuming that you made them.
Wow, thanks all for the fast replies!
Ok, I now have Destroyer installed and working (finally!), but I am experiencing the apparently common black-on-black text box problem. I downloaded the .zip to be flashed to fix this, but am not sure how to proceed. Do I just do the exact same thing as flashing a new ROM entirely or is there something special I need to do to let the phone know that it is an update?
RossGoldenstein said:
Wow, thanks all for the fast replies!
Ok, I now have Destroyer installed and working (finally!), but I am experiencing the apparently common black-on-black text box problem. I downloaded the .zip to be flashed to fix this, but am not sure how to proceed. Do I just do the exact same thing as flashing a new ROM entirely or is there something special I need to do to let the phone know that it is an update?
Click to expand...
Click to collapse
Not sure with ROM Manager but you can flash that from recovery the same way you flash a ROM. I'm sure there is an option in ROM Manager to flash it, I just couldn't tell you where. Do not wipe anything before flashing that though. Only wipe when flashing ROMs and kernels.
Go back into Recovery and flash that .zip the exact same way you flashed the ROM. Minus the data wipe.
Others: Does he wipe cache/dalvik as well? I've seen some posts say to do that when flashing mods that are flashable .zip and some don't. I've done both ways and seen no negative consequences (as of yet).
Yeah, that last post was dumb, I clicked "Submit" before I tried anything on my own. Flashing it the exact same way minus data wipe worked perfectly, though the prediction boxes for input in the market app (when you hit "search" and start typing, the things that drop down to give suggestions) still appear to be black on black. Bleh.
Also, the Dalvic wipe before installing was a good idea; I don't know for sure if it made a difference but a good habit to get into.
EDIT: By the way, this has got to be the least grammatical/spelling errors in a forum thread I've ever seen. I think I may like this site...
Wiping the cache and dalvik most likely isn't necessary but it can never hurt.
RossGoldenstein said:
Yeah, that last post was dumb, I clicked "Submit" before I tried anything on my own. Flashing it the exact same way minus data wipe worked perfectly, though the prediction boxes for input in the market app (when you hit "search" and start typing, the things that drop down to give suggestions) still appear to be black on black. Bleh.
Also, the Dalvic wipe before installing was a good idea; I don't know for sure if it made a difference but a good habit to get into.
EDIT: By the way, this has got to be the least grammatical/spelling errors in a forum thread I've ever seen. I think I may like this site...
Click to expand...
Click to collapse
I'm really new to this stuff myself (rooted for the first time ~2 days ago) and so I'm unsure how to further fix the blacked out predictions in the Market. Perhaps you could try contacting those within the thread of the ROM you downloaded, specifically citing that you installed the initial blacked out fix so that they don't redirect you back to the fix you've already applied, testing your patience and furthering your wait for perfection.
Aye, this site has got to be full of some of the most fluent English-speaking persons I've found on the internet.
I've been following the ROM dev daily but I've been stuck in the hospital and not been able to flash any of them yet.
I'm getting out today and plan on checking one out asap and am curious as to which one I should go with.
I would appreciate any feedback on them that you can provide!!
scott0 said:
I've been following the ROM dev daily but I've been stuck in the hospital and not been able to flash any of them yet.
I'm getting out today and plan on checking one out asap and am curious as to which one I should go with.
I would appreciate any feedback on them that you can provide!!
Click to expand...
Click to collapse
I am still running rooted stock. One of the ROMs that had K9 Mail wouldn't work for me on Exchange 2K10. You could also look at the # of posts in each of the threads, that may ID where most of the peeps are headed.
I really wanted to say that I hope you are doing better. My phone haxoring started with a long hospital stay back during the Razor days.
I do like LG's native e-mail client. Only Samsung's e-mail client is better.
scott0 said:
I've been following the ROM dev daily but I've been stuck in the hospital and not been able to flash any of them yet.
I'm getting out today and plan on checking one out asap and am curious as to which one I should go with.
I would appreciate any feedback on them that you can provide!!
Click to expand...
Click to collapse
I currently only used the Domination HD ROM, and it has its goods n bads.
the Goods:
1) Lag is virtually gone! Phone runs really smooth and fast, with almost no stuttering.
2) Some extra visual improvements, like the Roboto Fonts and ICS wallpapers included (although it didn't show up on mine for some reason)
3) ICS sounds/notifications
the Bads:
1) Video Recording (camcorder) is borked as for now. You cannot record a video, the app just freezes at 00:00:00
2) Bootup time is significantly longer (might be closer to 2-3 min bootup time) but someone said that it might be due to the deodexing of files in the phone.
3) the claimed Bravia Engine and Xloud features implemented in the ROM just cannot be seen/heard. Supposedly it is there and running, but to some, nothing looks any different than the usual HD look of the phone and the sound is no louder than default. So those 2 features either are not working or just not noticeable enough.
That's my small review on the Domination HD ROM. I might have missed something and if I did, hopefully the next person will add to it.
SnoopDawg said:
I am still running rooted stock. One of the ROMs that had K9 Mail wouldn't work for me on Exchange 2K10. You could also look at the # of posts in each of the threads, that may ID where most of the peeps are headed.
I really wanted to say that I hope you are doing better. My phone haxoring started with a long hospital stay back during the Razor days.
I do like LG's native e-mail client. Only Samsung's e-mail client is better.
Click to expand...
Click to collapse
hey thanks Amigo! I hope all is well with you now as well.
I took your advice and flashed the kernalpan1c ROM and am checking it out now.
aquariuz23 said:
I currently only used the Domination HD ROM, and it has its goods n bads.
the Goods:
1) Lag is virtually gone! Phone runs really smooth and fast, with almost no stuttering.
2) Some extra visual improvements, like the Roboto Fonts and ICS wallpapers included (although it didn't show up on mine for some reason)
3) ICS sounds/notifications
the Bads:
1) Video Recording (camcorder) is borked as for now. You cannot record a video, the app just freezes at 00:00:00
2) Bootup time is significantly longer (might be closer to 2-3 min bootup time) but someone said that it might be due to the deodexing of files in the phone.
3) the claimed Bravia Engine and Xloud features implemented in the ROM just cannot be seen/heard. Supposedly it is there and running, but to some, nothing looks any different than the usual HD look of the phone and the sound is no louder than default. So those 2 features either are not working or just not noticeable enough.
That's my small review on the Domination HD ROM. I might have missed something and if I did, hopefully the next person will add to it.
Click to expand...
Click to collapse
super, Thank you eh. nice. I really want to try this one too. I got the impression from following the thread that the video cam issue can't be resolved. Perhaps I read it wrong, I will go back through the posts. I too want that vid cam on this phone. But I am very curious about that Bravia engine and Xloud and if/how much they make a difference on my device.
I am liking the kernalpani1c ROM, it does seem smooth, I uninstalled the GO launcher, sticking with Zeam after comparing the 2 with the new ROM, Zeam is noticeably faster & smoother for me.
The best thing about the custom ROMs for me is I had to use Malninion's unbricking method to fix this phone several weeks ago which uses the SU640, now I am back to the proper one.
I think I'll check out that Domination ROM next.
scott0 said:
hey thanks Amigo! I hope all is well with you now as well.
I took your advice and flashed the kernalpan1c ROM and am checking it out now.
super, Thank you eh. nice. I really want to try this one too. I got the impression from following the thread that the video cam issue can't be resolved. Perhaps I read it wrong, I will go back through the posts. I too want that vid cam on this phone. But I am very curious about that Bravia engine and Xloud and if/how much they make a difference on my device.
I am liking the kernalpani1c ROM, it does seem smooth, I uninstalled the GO launcher, sticking with Zeam after comparing the 2 with the new ROM, Zeam is noticeably faster & smoother for me.
The best thing about the custom ROMs for me is I had to use Malninion's unbricking method to fix this phone several weeks ago which uses the SU640, now I am back to the proper one.
I think I'll check out that Domination ROM next.
Click to expand...
Click to collapse
I might switch to kernelpanic's rom next week or so when I have the time to start fresh. I'm gonna format the /data partition so it will a be clean slate.
Well, like i've mentioned, me and some others don't really see any difference either the bravia engine or Xloud is doing to the phone. The image quality on the phone is the same, and the loudness is just as loud as stock. Shrugs, it might just be me I dont know lol. Feel free to try it and let us know what you think about it
aquariuz23 said:
I might switch to kernelpanic's rom next week or so when I have the time to start fresh. I'm gonna format the /data partition so it will a be clean slate.
Well, like i've mentioned, me and some others don't really see any difference either the bravia engine or Xloud is doing to the phone. The image quality on the phone is the same, and the loudness is just as loud as stock. Shrugs, it might just be me I dont know lol. Feel free to try it and let us know what you think about it
Click to expand...
Click to collapse
I was wondering about the clean slate starting fresh myself, does that make a difference?
I went to get the other ROMs and such but noticed their instructions were different than kernalpan1c, they did not state to clear caches and wipe system, etc so I stopped there.
so a question- it's safe and correct to always do the following 2 steps when flashing any ROM
3. Format /system in Mounts and Storage
4. Then "wipe cache partition" and "advanced > wipe dalvik cache"
thanks for the inputs
aquariuz23 said:
3) the claimed Bravia Engine and Xloud features implemented in the ROM just cannot be seen/heard. Supposedly it is there and running, but to some, nothing looks any different than the usual HD look of the phone and the sound is no louder than default. So those 2 features either are not working or just not noticeable enough.
Click to expand...
Click to collapse
why on earth would anybody need some st1nk'n bravia engine while there already is lg mobile engine in stock ROM? ther U go http://www.youtube.com/watch?v=KD3GSzOBuUo
scott0 said:
I was wondering about the clean slate starting fresh myself, does that make a difference?
I went to get the other ROMs and such but noticed their instructions were different than kernalpan1c, they did not state to clear caches and wipe system, etc so I stopped there.
so a question- it's safe and correct to always do the following 2 steps when flashing any ROM
3. Format /system in Mounts and Storage
4. Then "wipe cache partition" and "advanced > wipe dalvik cache"
thanks for the inputs
Click to expand...
Click to collapse
So far from what I have followed, the 2 steps you've mentioned are safe to follow. The only thing they've all mentioned is: "DO NOT WIPE/FORMAT /Data Partition" Just making it big, bold and bright so you don't miss it LOL. Kernelpanic figured out that it is some kind of a glitch in CWM that causes data corruption when you wipe/format the /Data partition.
Domination's ROM also states to wipe /system and dalvik cache, it's a standard thing i'm guessing. The only reason I want to start from a clean slate is that I don't want any bugs or system clash when I flash a new ROM over an existing ROM, so I think wiping /data will be essential.
Btw, Kernelpanic has suggested that if you do need to wipe /data, to please first flash back LG's default recovery using the image you've backed up prior to flashing CWM on the phone, and then formatting the phone back to factory settings using it. When factory reset is complete (which means /data is also wiped), you can then flash back CWM and then flash the new ROM.
Hopefully this will help you decide on your steps. Again, wiping /data is not necessary at all, it's just an option that technically should be done but right now is not so safe to do. Be careful and as always, we are not responsible for a gorgeous brick on your desk lol.
---------- Post added at 05:06 PM ---------- Previous post was at 04:58 PM ----------
Billy Madison said:
why on earth would anybody need some st1nk'n bravia engine while there already is lg mobile engine in stock ROM? ther U go http://www.youtube.com/watch?v=KD3GSzOBuUo
Click to expand...
Click to collapse
I like that commercial lol. That is very informative and interesting to watch. Very true wat you said about the Bravia engine. Tbh, like I previously mentioned, I do not see any benefit of the Bravia engine on this phone, and definitely not the Xloud feature. Thus, I'm thinking of trying another ROM that has all capabilities functioning, thus the Camcorder.
Just wondering, if you truly can replace the "visual engine (e.g. LG's engine with Bravia Engine), could that be the reason why the camcorder won't work? It's kinda weird that the camera works but the recording function doesnt.
well,
i flashed the domination ROM and it installed, I poked around and decided I needed the video camera, so shut down, booted in to CWM and flashed the other ROM, it said it installed, i rebooted it would not open, stuck on boot, so i shutdown, booted into cwm and restored the 1st ROM but now i am stuck on a boot loop and cannot access cwm.
derp.
update: flashed the su640 ROM so I am back in biz, gotta root and flash CWM.
so i guess this is a fresh flash after all!
i'm at 32% batt, superoneclick does not want to root atm , letting it charge a bit and will try to reroot.
scott0 said:
well,
i flashed the domination ROM and it installed, I poked around and decided I needed the video camera, so shut down, booted in to CWM and flashed the other ROM, it said it installed, i rebooted it would not open, stuck on boot, so i shutdown, booted into cwm and restored the 1st ROM but now i am stuck on a boot loop and cannot access cwm.
derp.
update: flashed the su640 ROM so I am back in biz, gotta root and flash CWM.
so i guess this is a fresh flash after all!
i'm at 32% batt, superoneclick does not want to root atm , letting it charge a bit and will try to reroot.
Click to expand...
Click to collapse
Yeah, that's what I feared, that when flashing another ROM over existing rom and not deleting /data might give an error. Which other Rom were you attempting to flash over Domination?
aquariuz23 said:
Yeah, that's what I feared, that when flashing another ROM over existing rom and not deleting /data might give an error. Which other Rom were you attempting to flash over Domination?
Click to expand...
Click to collapse
was trying to flash the RebelRom after the Domination. the switch from kernalpanic to domination went fine but the switch from Domination to Rebel FUBARed the phone, same exact steps followed. it also messes up the phone where a restore does not work then cwm is not accessible.
yup, serious issue that is not pointed out very well anywhere. the phone was ruined. in fact it's now stuck on the su640 ROM rooted but not recognized by adb so no su access, adb shell command returns a dollar sign and stalls, and the su640 wireless issue means no internet access on the phone so I can't get terminal emulator on it to move img files in to place.
ATT is sending me a replacement under the warranty.
my opinion atm on the custom CWM and the available ROMs is the ROI is not there.
The Roms don't perform any better than a rooted and debloated stocker IMO to justify the risk it takes checking them out.
scott0 said:
was trying to flash the RebelRom after the Domination. the switch from kernalpanic to domination went fine but the switch from Domination to Rebel FUBARed the phone, same exact steps followed. it also messes up the phone where a restore does not work then cwm is not accessible.
yup, serious issue that is not pointed out very well anywhere. the phone was ruined. in fact it's now stuck on the su640 ROM rooted but not recognized by adb so no su access, adb shell command returns a dollar sign and stalls, and the su640 wireless issue means no internet access on the phone so I can't get terminal emulator on it to move img files in to place.
ATT is sending me a replacement under the warranty.
my opinion atm on the custom CWM and the available ROMs is the ROI is not there.
The Roms don't perform any better than a rooted and debloated stocker IMO to justify the risk it takes checking them out.
Click to expand...
Click to collapse
Damn, seems like there is still some figuring out to do. A lot of the troubles keep pointing to CWM. What did you tell AT&T to get them to send you a warranted phone?
Kaiser_Beef said:
Damn, seems like there is still some figuring out to do. A lot of the troubles keep pointing to CWM. What did you tell AT&T to get them to send you a warranted phone?
Click to expand...
Click to collapse
i told them the phone was stuck on the LG boot screen and it would not turn off entirely. if I hold the power button down long enough the screen would flash off but it would instantly reboot itself again. the phone did finally fully boot to the su640 ROM but no data/internet access. then they had me do a factory reset which failed as well, after the reset the phone would still boot to main screen instead of to the setup screen.
It was a long telephone call. but ultimately I was transferred to the warranty dept, the 1st tech agent filled that warranty person in who then just checked a cople things and then agreed to ship me a replacement expedited, scheduled delivery is Monday.
scott0 said:
was trying to flash the RebelRom after the Domination. the switch from kernalpanic to domination went fine but the switch from Domination to Rebel FUBARed the phone, same exact steps followed. it also messes up the phone where a restore does not work then cwm is not accessible.
yup, serious issue that is not pointed out very well anywhere. the phone was ruined. in fact it's now stuck on the su640 ROM rooted but not recognized by adb so no su access, adb shell command returns a dollar sign and stalls, and the su640 wireless issue means no internet access on the phone so I can't get terminal emulator on it to move img files in to place.
ATT is sending me a replacement under the warranty.
my opinion atm on the custom CWM and the available ROMs is the ROI is not there.
The Roms don't perform any better than a rooted and debloated stocker IMO to justify the risk it takes checking them out.
Click to expand...
Click to collapse
So out of all the 3 ROMs you've tried which one did you like the most? Well, of course the rebelrom doesn't count cuz it borked your phone lol. Sorry to hear that though. I had this bad feeling when you mentioned that it froze after flashing that you flashed rebelrom, and yup that's what you did lol. Didn't you read through the thread though? Many of them got stuck in boot loops and not being able to recover after it.
yes, of course I read through the thread. I had the time to read through all the threads many times and did, even jotted notes down. I was fully aware of the risks involved and don't recall *****ing. I am patiently awaiting my replacement phone generously provided by ATT.
my conclusion was that none of the ROMs are worth the risk. The first one doesn't perform any better than a stock phone debloated + a better launcher, the second one has a very long boot time, then performs no better than a debloated stocker minus the video recorder.
scott0 said:
my conclusion was that none of the ROMs are worth the risk. The first one doesn't perform any better than a stock phone debloated + a better launcher, the second one has a very long boot time, then performs no better than a debloated stocker minus the video recorder.
Click to expand...
Click to collapse
I will say upfront to anyone looking at using my ROM, it is a de-odexed ROM minus bloat, a better launcher, some optimizations (ie ICS app process and system server, build.prop tweaks), and the carrier text removed from the status bar. With that said, de-odexed does run smoother than stock (odexed). CF-Bench scores are for example higher on my ROM than on stock.
We're not going to see dramatic speed improvements past that without custom kernels or CM/AOSP.
scott0 said:
yes, of course I read through the thread. I had the time to read through all the threads many times and did, even jotted notes down. I was fully aware of the risks involved and don't recall *****ing. I am patiently awaiting my replacement phone generously provided by ATT.
my conclusion was that none of the ROMs are worth the risk. The first one doesn't perform any better than a stock phone debloated + a better launcher, the second one has a very long boot time, then performs no better than a debloated stocker minus the video recorder.
Click to expand...
Click to collapse
lol scott, I never said anywhere that you were *****ing about bricking. I was just wondering why try when you know you have 80% of bricking? But anyways, it's great that you are getting a replacement from AT&T.
IM DESPERATE! I've searched and searched and I've found nothing that I could understand. Please, someone help!
I rebooted my phone after trying to install an .apk file & suddenly my phone is stuck on "ANDROID IS UPGRADING" screen. No matter the times I've reboot. I've installed the 4.2.2 ROM with S4 feel by ipromeh which is based on CM10.1 alpha 6 by arco. I don't want to do anything without consulting someone with more experience first. PLEASE SOMEONE HELP!!!
RaxToTheMax said:
IM DESPERATE! I've searched and searched and I've found nothing that I could understand. Please, someone help!
I rebooted my phone after trying to install an .apk file & suddenly my phone is stuck on "ANDROID IS UPGRADING" screen. No matter the times I've reboot. I've installed the 4.2.2 ROM with S4 feel by ipromeh which is based on CM10.1 alpha 6 by arco. I don't want to do anything without consulting someone with more experience first. PLEASE SOMEONE HELP!!!
Click to expand...
Click to collapse
Do you see that ANDROID UPGRADING is in progress? Maybe you have installed to many apps that is why it takes too looong to upgrrade.
Well if you think that your phone get stuck, try too reflash 4.2.2 ROM with S4, but if that would still persist, you have no choice but to format your phone.
tnx.
jakelq said:
Do you see that ANDROID UPGRADING is in progress? Maybe you have installed to many apps that is why it takes too looong to upgrrade.
Well if you think that your phone get stuck, try too reflash 4.2.2 ROM with S4, but if that would still persist, you have no choice but to format your phone.
tnx.
Click to expand...
Click to collapse
I don't think it's taking so long because of the amount of app because I barely have maybe 20 apps installed maybe even less (stock apps excluded).
When flashing the 4.2.2 ROM do I have to wipe/format anything? Like dalvik cache. Or do I just flash the .zip?
RaxToTheMax said:
I don't think it's taking so long because of the amount of app because I barely have maybe 20 apps installed maybe even less (stock apps excluded).
When flashing the 4.2.2 ROM do I have to wipe/format anything? Like dalvik cache. Or do I just flash the .zip?
Click to expand...
Click to collapse
Usually this happens only when you install apps that are ported on our device or mods like Awesome Beats, and one more when you flash a new kernel.
I tried that rom of yours, but i had the issues described in Ipromehs thread (i admire his work, but i'll wait till his rom will be more stable), and because of that i reverted to Ehndroix III wich works best for me with the new Skull kernel (flashed separately after installing rom). Perhaps you should try that.
For me all is working fine when i (ofcourse in Clockworkmod)do factory reset, then wipe cache, then wipe dalwik cache, then go to mounts and storage, format system, then cache, then data.... after that flash rom and finally reboot.
Never failed on that. You might try it if you'd like.
bhun said:
Usually this happens only when you install apps that are ported on our device or mods like Awesome Beats, and one more when you flash a new kernel.
I tried that rom of yours, but i had the issues described in Ipromehs thread (i admire his work, but i'll wait till his rom will be more stable), and because of that i reverted to Ehndroix III wich works best for me with the new Skull kernel (flashed separately after installing rom). Perhaps you should try that.
For me all is working fine when i (ofcourse in Clockworkmod)do factory reset, then wipe cache, then wipe dalwik cache, then go to mounts and storage, format system, then cache, then data.... after that flash rom and finally reboot.
Never failed on that. You might try it if you'd like.
Click to expand...
Click to collapse
Yeah it got stuck in boot mode when I rebooted my phone after attempting to install freedom.apk (for free in-app purchases).
But I understand that I most Likely will have to result to wiping everything and flashing the ROM once more. I'm thinking of just flashing Arcos CM10.1 alpha 7, what do you guys think?
I'd like to check out that Ehndroix III doe fingers crossed!
You can try that too, it is the source of many roms out here
But with that rom i have no experience so far...
bhun said:
You can try that too, it is the source of many roms out here
But with that rom i have no experience so far...
Click to expand...
Click to collapse
Well I ended up flashing Ehndroix III and phone is functioning once more. The ROM looks nice,fast too but idk there's something about the layout that just bothers me Haha. But at least I got my phone working again. Thanks guys
Sent from my GT-i8150 using xda app-developers app
RaxToTheMax said:
Well I ended up flashing Ehndroix III and phone is functioning once more. The ROM looks nice,fast too but idk there's something about the layout that just bothers me Haha. But at least I got my phone working again. Thanks guys
Sent from my GT-i8150 using xda app-developers app
Click to expand...
Click to collapse
I am glad that you could succed. There are some possibilities to change the looks, but do a nandroid backup before using them just in case.
Ehndroix has a Touchwiz looks package that you can download. It is not so nice like Ipromehs work, i have to admit that, but it can do the job.
For me it was unusual in the beginning, but with time i get use to it, and i began to love it. Same could happen to you also.
When you want the latest software, with the best looks, that's were you will not get guarantee, that both will be in one package since all of us have somewhat different taste.
I personally prefer things to work in the first place, after that i look into spicing things up a bit if possible.
Ipromehs roms will be soon good enough (i trust him that, because his hard work and many updates), perhaps you cold give his rom a try later.
So, enjoy your working phone! Cheers!
RaxToTheMax said:
IM DESPERATE! I've searched and searched and I've found nothing that I could understand. Please, someone help!
I rebooted my phone after trying to install an .apk file & suddenly my phone is stuck on "ANDROID IS UPGRADING" screen. No matter the times I've reboot. I've installed the 4.2.2 ROM with S4 feel by ipromeh which is based on CM10.1 alpha 6 by arco. I don't want to do anything without consulting someone with more experience first. PLEASE SOMEONE HELP!!!
Click to expand...
Click to collapse
I have a similar problem!!
Help needed please. I am totally NEW at THIS.
1. Fastboot.exe does not recognise my device.
2. In Android system recovery <3e>(vol.up+power) PC recognises device as 'unknown device'.
3. 'FASTBOOT'(vol.down+power) screen does not change to 'FASTBOOT USB' when device is plugged in via USB code.
4. In 'FASTBOOT' screen can only select 'BOOTLOADER', 'REBOOT', 'REBOOT BOOTLOADER' & 'POWER DOWN'.
5. All above selections reboots the phone except 'POWER DOWN'.
6. adb.exe recognises phone in 'FASTBOOT' screen but not fastboot.exe.
7. Phone is in debug mode.
8. After booting - 'HTC quietly brilliant' screen, then there is no 'Beats Audio' screen - but it's a black screen.
9. PC shows device as 'USB Mass Storage' in 'FASTBOOT', no Android phone shown. In windows explorer can see two 'Removable Disk', but not accessible.
10. If cache is cleared - phone stuck in 'Android is upgrading... Starting applications'.
11. Only adb.exe commands are working and NOT fastboot.
----------------------------------------------------------------------------
'FASTBOOT' screen shown as below:-
MARVEL PVT SHIP S-OFF RL
HBOOT-1.08.0000
MICROP-0451
RADIO-7.53.39.03M
Oct 31 2011.20:38:16
What stock ROM is required for above phone??
HTC One X or HTC S720e or HTC EndeavorU ???
------------------------------------------------------------------------------
The box in which the phone came has following details:-
Model: S720e
CPU: 1.5 GHz, Quad Core
Platform: Android with HTC Sense
1 GB RAM, 32 GB Storage
Serial No.-0123456789ABCDEF
HTC One X
-------------------------------------------------------------------------------
CPU Z showed device as: HTC Endeavor, G26
Most likely if I can get the correct ROM it can be solved. I can select 'apply update from sdcard' in android system recovery <3e> mode.
PLEASE HELP !!!!!!!!!!!!!!!!!!!!
Mate...you do know that this is the forum for the galaxy W? You appear to be asking for help with an HTC phone......
It's doubtful that anybody here has experience of HTC phones.
It would be best to redirect your question to the correct forum......
Sent from my Arco powered W via XDA developers app
keithross39 said:
Mate...you do know that this is the forum for the galaxy W? You appear to be asking for help with an HTC phone......
It's doubtful that anybody here has experience of HTC phones.
It would be best to redirect your question to the correct forum......
Sent from my Arco powered W via XDA developers app
Click to expand...
Click to collapse
Thanks
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!