Related
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.
HI all,
I've flashed CWM5.5 from the recomended thread and installed Cyanogen 9 Alpha 1. Unfortunatly the phone seems to boot up but does never leave the boot animation screen (yes I've also flashed gapps after cyanogen).
Anyone can identify this pattern? On a normal device I could hook it up through a serial cable and try to debug the boot... Eventually how can I do that with a I8150?
Well, any help would be most welcome. I'm totally available for testing and I do have some experience with Linux even at a very low level/system space.
Install
Use CWM5.
Warning: Only use this recovery to flash CM9. Otherwise, you risk bricking your phone!
Wipe data and cache.
Flash update*.zip.
Flash gapps*.zip. You must flash gapps after every upgrade to CM9 since /system is formatted, wiping your previous add-ons.
Reboot phone.
After you setup your Google account, reinstall the three apps from Market in order to restore most of your apps, call log and SMS history.
Warning: Do not restore backup data of system apps!
If you restore a bad backup with cached settings in telephony.db in data/data/com.*.*.telephony it can break MMS.
It seems that restoring backups can also break Calendar sync.
read it thoroughly ...
1st you must flash update*.zip
2nd gapps*.zip
that just about it ....
what is your current kernel ?
That was pretty much it... I've restored not the original operator crap ROM, but instead the Value Pack ROM.
CyanogenMod9 seemed to install ok, but just looped and the phone didn't finished the boot. I'm not really sure on what happened. I'm just finishing restoring the stuff
I'm guessing you didn't wipe data/cache.
I did a factory reset, but sure, it might not have wiped the whole thing... Going to try again.
@argo68
True mate, the issue was not wiping the user cache. I've wiped the cache now from ClockWorkMod and it worked ok. Takes some time to boot compared to the stock samsung ROMs but it works fine
Anything you need tested ? I can most likely help.
I do have a problem with apps though, for example, GMAIL doesn't show the body of the message... as you can see on the screenshot, but I guess this is a app related issue maybe?
http://susepaste.org/images/39081870.png
After a reboot somehow it boots a bit faster and the gmail app is now displaying the body of the email and it seems a bit faster...
Good work, gonna ride this for a few days and see what happens.
@argo68
If you need beta testers, let me know. I'm off work this days but can't wait to get into my lab and check this stuff deeper
@argo68
he is arco68
just in case he takes offence, which I don't believe he would
Hopefully not, all the norwegians I knew personally were very nice people and always ready for some bear
ketheriel said:
Hopefully not, all the norwegians I knew personally were very nice people and always ready for some bear
Click to expand...
Click to collapse
reAdy for some BEAR ????
do you actually mean bear or beer ??
chocolemon said:
reAdy for some BEAR ????
do you actually mean bear or beer ??
Click to expand...
Click to collapse
Maybe it's the Nordic ascendance. They fight a bear with one hand while holding the beer with the other.
Hi I'm using this cyanogen mod for quite a few days now. The back side of the phone is always warm and the battery is drained very fast. Anyone have this similar problem?
I'm sure that I install the ROM correctly as i cleared everything on the phone with CWM 5.0.0.4 before and after. (Phone data / Cache Partition / Dalvik Cache / Battery Cache)
Any help would be appretiated
No such problem here. You should use an app to check what frequency the phone is running at in idle, and also how much load there is on the cpu.
How would you feel if you could make a Nandroid backup, wipe your device clean, flash a new ROM, restore all your personal apps (with settings, SMS messages, and call log intact), all in about 10 minutes?
Too good to be true? After all, you probably remember what they say about things that sound too good to be true. Normally you shouldn’t believe it. In this case, though, it’s real, and it works! Many people in the DIET ICS ROM thread have already tried it, with amazing success.
As always, there’s a caveat. You perform the following procedures at your own risk. I will not be held responsible for any damage, frustration, anger, sadness, or suicides that may result from your decision to implement this process.
CAUTION: This method of data recovery will work under a wide variety of situations; however, you must consider the following:
1) When going from a stock or stock-based ROM to another stock or stock-based ROM, this method should work very well. It doesn’t matter if it’s the same ROM as long as both are based on a stock ROM.
2) When going from a stock or stock-based ROM to an AOSP-based ROM, such as CM or AOKP, this method may/will not work. Similarly, when going from an AOSP-based ROM to a stock or stock-based ROM, this method may/will not work.
Use common sense, and always follow instructions provided by the ROM Developer.
This method also removes any concern as to whether or not you need to wipe because the process involves doing a full wipe, which only adds about 30 seconds to the procedure.
Here we go …
1. Boot into Recovery
2. Make a Nandroid backup
3. Wipe data/factory reset
4. Wipe cache partition
5. Wipe Dalvik Cache
6. Flash ROM
7. DO NOT REBOOT – STAY IN RECOVERY
8. Select backup and restore
9. Select advanced restore
10. Select the Nandroid backup you made above
11. Select Restore data
12. Select Yes – Restore data
13. WAIT!
14. REBOOT
If all goes according to plan, you will arrive at your home screen with all apps in place, and with all settings intact, including stored text messages, and your call log.
Shockingly easy, isn’t it? After all, it is ALWAYS suggested that you do a Nandroid before you flash any new ROM, so this procedure will ALWAYS have you completely up-to-date.
Okay, you can hit the thanks button now.
Peter
(formerly PeterHTC)
PeterGuru said:
How would you feel if you could make a Nandroid backup, wipe your device clean, flash a new ROM, restore all your personal apps (with settings, SMS messages, and call log intact), all in about 10 minutes?
Too good to be true? After all, you probably remember what they say about things that sound too good to be true. Normally you shouldn’t believe it. In this case, though, it’s real, and it works! Many people in the DIET ICS ROM thread have already tried it, with amazing success.
As always, there’s a caveat. You perform the following procedures at your own risk. I will not be held responsible for any damage, frustration, anger, sadness, or suicides that may result from your decision to implement this process.
This method works “perfectly” if you’re upgrading an existing ROM. However, I can’t see any reason why it wouldn’t work equally well even if you’re coming from another ROM. Either way, use common sense, and always follow instructions provided by the ROM Developer.
This method also removes any concern whether or not you need to wipe because the process involves doing a full wipe, which only adds about 30 seconds to the procedure.
Here we go …
1.Boot into Recovery
2.Make a Nandroid backup
3.Wipe data/factory reset
4.Wipe cache partition
5.Wipe Dalvik Cache
6.Flash ROM
7.DO NOT REBOOT – STAY IN RECOVERY
8.Select backup and restore
9.Select advanced restore
10.Select the Nandroid backup you made above
11.Select Restore data
12.Select Yes – Restore data
13.WAIT!
14.REBOOT
If all goes according to plan, you will arrive at your home screen with all apps in place, and with all settings intact, including stored text messages, and your call log.
Shockingly easy, isn’t it? After all, it is ALWAYS suggested that you do a Nandroid before you flash any new ROM, so this procedure will ALWAYS have you completely up-to-date.
Okay, you can hit the thanks button now.
Peter
(formerly PeterHTC)
Click to expand...
Click to collapse
Good to see you here from the one x. I'm glad to be back on Sammy. One x just had too many bugs for me and no memory card was a deal breaker.
This tutorial seems legit, I'm just concerned that doing this could overwrite mods the rom developer implements and cause issues. Any response to that concern?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Usually use Titanium Backup myself, so I can selectively select which apps to restore with data. If you're going from a stock based ROM( stock modified ) to AOSP ( CM, AOKP, or any of their kangs ) then I don't think I'd recommend this shotgun method of restoring. However Stock -> Stock this is very fast and shouldn't cause any issues.
About mods, not sure, most mods are going to be in /system so those should be fine, however anything themed will be overwritten I believe. ( CWM wipes and restores, not an additive restore correct? )
I completely agree ...
RubenRybnik said:
Usually use Titanium Backup myself, so I can selectively select which apps to restore with data. If you're going from a stock based ROM( stock modified ) to AOSP ( CM, AOKP, or any of their kangs ) then I don't think I'd recommend this shotgun method of restoring. However Stock -> Stock this is very fast and shouldn't cause any issues.
Click to expand...
Click to collapse
Yes, Titanium has the advantage of allowing you to selectively restore apps, etc.
RubenRybnik said:
About mods, not sure, most mods are going to be in /system so those should be fine, however anything themed will be overwritten I believe. ( CWM wipes and restores, not an additive restore correct? )
Click to expand...
Click to collapse
I completely agree. If you're sticking with a stock-based ROM, or up-dating almost ANY existing ROM, then this method should work just fine; however, like you said, I would not recommend it if going from stock to AOSP, or vice versa.
I would also agree concerning the mods, which are almost always in /system, and aren't the theme files anywhere BUT in the data folder? Please correct me if I'm wrong.
Peter
Same here ...
lessthanzach said:
Good to see you here from the one x. I'm glad to be back on Sammy. One x just had too many bugs for me and no memory card was a deal breaker.
This tutorial seems legit, I'm just concerned that doing this could overwrite mods the rom developer implements and cause issues. Any response to that concern?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I would have to agree. I had far too many little glitches with my ONE X and ONE XL that were just too annoying. So far I could not be happier with the S3.
Peter
Good tip, Peter. I never knew about that one and it will come in handy for me!
Am I the only one who also formats /system in Recovery?
thank you for this! im jumping from stock to diet ics and this tip helped a lot.
im also coming from about a months use of HTC One X. its only been one day with this sg3 and i already prefer it over the htc one x.
Is ROM Manager still advisable or did Koush move on and it is an abandoned project like some of the reviews suggest in the Google Play store? I used to use this to flash and manage my NANDROID's and it was super easy.
P8TRIOT said:
Is ROM Manager still advisable or did Koush move on and it is an abandoned project like some of the reviews suggest in the Google Play store? I used to use this to flash and manage my NANDROID's and it was super easy.
Click to expand...
Click to collapse
I just used his Rom manager to flash the AT&T recovery and it works great.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
PeterGuru said:
How would you feel if you could make a Nandroid backup, wipe your device clean, flash a new ROM, restore all your personal apps (with settings, SMS messages, and call log intact), all in about 10 minutes?
Too good to be true? After all, you probably remember what they say about things that sound too good to be true. Normally you shouldn’t believe it. In this case, though, it’s real, and it works! Many people in the DIET ICS ROM thread have already tried it, with amazing success.
As always, there’s a caveat. You perform the following procedures at your own risk. I will not be held responsible for any damage, frustration, anger, sadness, or suicides that may result from your decision to implement this process.
This method works “perfectly” if you’re upgrading an existing ROM. However, I can’t see any reason why it wouldn’t work equally well even if you’re coming from another ROM. Either way, use common sense, and always follow instructions provided by the ROM Developer.
This method also removes any concern whether or not you need to wipe because the process involves doing a full wipe, which only adds about 30 seconds to the procedure.
Here we go …
1. Boot into Recovery
2. Make a Nandroid backup
3. Wipe data/factory reset
4. Wipe cache partition
5. Wipe Dalvik Cache
6. Flash ROM
7. DO NOT REBOOT – STAY IN RECOVERY
8. Select backup and restore
9. Select advanced restore
10. Select the Nandroid backup you made above
11. Select Restore data
12. Select Yes – Restore data
13. WAIT!
14. REBOOT
If all goes according to plan, you will arrive at your home screen with all apps in place, and with all settings intact, including stored text messages, and your call log.
Shockingly easy, isn’t it? After all, it is ALWAYS suggested that you do a Nandroid before you flash any new ROM, so this procedure will ALWAYS have you completely up-to-date.
Okay, you can hit the thanks button now.
Peter
(formerly PeterHTC)
Click to expand...
Click to collapse
When I had my old Droid X2 (MB870), this is the method I used all the time, and it was very simple and straightforward, if I am understanding you correctly, this method is conditional in that you have to be coming from an existing flashed ROM? So for instance I just rooted yesterday through Odin but am still on stock, this method wouldn't work for me? It would be awesome if this could be utilized universally for what ever (rooted state), is this in fact the case or what exactly is the specific condition if any?
I will be adding a cautionary note to the first post ...
P8TRIOT said:
When I had my old Droid X2 (MB870), this is the method I used all the time, and it was very simple and straightforward, if I am understanding you correctly, this method is conditional in that you have to be coming from an existing flashed ROM? So for instance I just rooted yesterday through Odin but am still on stock, this method wouldn't work for me? It would be awesome if this could be utilized universally for what ever (rooted state), is this in fact the case or what exactly is the specific condition if any?
Click to expand...
Click to collapse
Although this will work under many different circumstances, there are a few very important restrictions, which I will add to the first post in a few minutes.
Peter
Not to with this but there is a software update be AT&T if installed will it take away root?
Sent from my SAMSUNG-SGH-I747 using xda premium
Carrier up-dates may be disabled ...
dahlem said:
Not to with this but there is a software update be AT&T if installed will it take away root?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Although I would like someone to confirm this, it is my belief that, if you root your device, then software up-dates from the carrier no longer work.
Peter
This works fine with ApOcAlYpSe 7_10_12 ROM
This method I can confirm works perfectly with the ApOcAlYpSe 7_10_12 ROM by smartguy044. I installed the Rom and restored everything from a previous stock setup that I did a nandroid of right before flashing. From start to finish the whole process took me less than the 10min as advertised. Just thought I would share just in case anyone was on the fence or concerned about using this with the ApOcAlYpSe 7_10_12 ROM.
Thank you for the confirmation ...
hkeyman said:
This method I can confirm works perfectly with the ApOcAlYpSe 7_10_12 ROM by smartguy044. I installed the Rom and restored everything from a previous stock setup that I did a nandroid of right before flashing. From start to finish the whole process took me less than the 10min as advertised. Just thought I would share just in case anyone was on the fence or concerned about using this with the ApOcAlYpSe 7_10_12 ROM.
Click to expand...
Click to collapse
Thank you for the confirmation.
I hope this helps those who are afraid to flash new ROMs because the entire process (from Nandroid to installing all apps and re-establishing settings), can take hours. I never really trusted Titanium, even though many do, so before hearing about this method, it would take me anywhere from 2-6 hours to get my device back to exactly how I want it, with all settings re-established. Flashing and installing apps wasn't the issue, which took me less than an hour. It's opening every single app and adjusting the settings that often took hours.
Peter
You really don't have to worry about restoring data if you flash a ROM that doesn't format the data partition. I have found that some/most don't wipe data. So you can just flash the ROM and reboot and go on your way. Of course do make a backup just in case.
I use TiBu 100% of the time. Never had it not work.
wgarrido said:
You really don't have to worry about restoring data if you flash a ROM that doesn't format the data partition. I have found that some/most don't wipe data. So you can just flash the ROM and reboot and go on your way. Of course do make a backup just in case.
I use TiBu 100% of the time. Never had it not work.
Click to expand...
Click to collapse
You are correct in your suggestion "If" the Rom installed does not wipe or format the data. This is obviously a alternate, fast method for restoration of user data if needed in a pinch or just as a normal way of getting your configuration and apps back to the way you had them configured previously (either stock or on another similar installed ROM).
I am not sure what you meant by you use TiBu and not have it work? When restoring from TiBu you should always just restore missings Apps with Data and avoid anything System related as it would most likely overwrite anything that a ROM customization may have just installed and will cause issues whether minor or even serious. I would suggest only messing with system restore items if you absolutely know what you are doing. That aside I agree with Peter as TiBu as good as a backup as it is, its time consuming...but its another precautionary backup method needed as a just in case.
hkeyman said:
You are correct in your suggestion "If" the Rom installed does not wipe or format the data. This is obviously a alternate, fast method for restoration of user data if needed in a pinch or just as a normal way of getting your configuration and apps back to the way you had them configured previously (either stock or on another similar installed ROM).
I am not sure what you meant by you use TiBu and not have it work? When restoring from TiBu you should always just restore missings Apps with Data and avoid anything System related as it would most likely overwrite anything that a ROM customization may have just installed and will cause issues whether minor or even serious. I would suggest only messing with system restore items if you absolutely know what you are doing. That aside I agree with Peter as TiBu as good as a backup as it is, its time consuming...but its another precautionary backup method needed as a just in case.
Click to expand...
Click to collapse
I was just saying that TiBu hasn't lost data or anything. I know about restoring system data. I have gotten away with restoring some of it in the past.
PeterGuru said:
Although I would like someone to confirm this, it is my belief that, if you root your device, then software up-dates from the carrier no longer work.
Peter
Click to expand...
Click to collapse
OTA's should work with root as long as you are on stock and haven't altered your build.prop. On that note, I haven't heard anything about a Rogers update?
I haven't heard anything from Rogers, either ...
David Dee said:
OTA's should work with root as long as you are on stock and haven't altered your build.prop. On that note, I haven't heard anything about a Rogers update?
Click to expand...
Click to collapse
I haven't heard anything from Rogers regarding an up-date, either.
And thank you for answering the OTA question.
Peter
Sorry if im a total noob at posting but spare me, when I have a chance ill change the specifics and have it in the appropriate forum but at the moment let me describe the issue at hand. Im currently using hyperdrive on my sprint galaxy s3 and at least more than 8 times a day I open a simple app or attempt to multitask. The phone freezes and I have to keep rebooting and rebooting until it finally works. Has anyone other than me had this issue?
Sent from my SPH-L710 using xda app-developers app
Anthonyl123 said:
Sorry if im a total noob at posting but spare me, when I have a chance ill change the specifics and have it in the appropriate forum but at the moment let me describe the issue at hand. Im currently using hyperdrive on my sprint galaxy s3 and at least more than 8 times a day I open a simple app or attempt to multitask. The phone freezes and I have to keep rebooting and rebooting until it finally works. Has anyone other than me had this issue?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Switch ROMs.
Maybe your phone just doesn't play nice with the Hyperdrive ROM. Try out a new one, or do a clean install of it and see if that fixes it!
Switch ROMs?
Well, I suppose it's a fix.
The thing is, what if you want Hyperdrive to work?
I have been getting random reboots, which led to boot looping. I have done a clean re-install, but mysteriously lost the multi-view launcher.
Any ideas? Besides switching ROMS...
Mr._Happy said:
Switch ROMs?
Well, I suppose it's a fix.
The thing is, what if you want Hyperdrive to work?
I have been getting random reboots, which led to boot looping. I have done a clean re-install, but mysteriously lost the multi-view launcher.
Any ideas? Besides switching ROMS...
Click to expand...
Click to collapse
The difficult thing when trying to troubleshoot Roms like Hyperdrive is that unless you document exactly what option you chose (which kernel, mod, theme, etc) in the Aroma installer, it'll be difficult to replicate your specific situation. Do you happen to know which settings you chose (maybe walk us through page-by-page in Aroma). Than we'd be able to help troubleshoot what's going on in your phone.
That being said, I'll walk you through some generic fixes for reboots/bootloops. You can try each one in order, and if #1 doesn't work, try #2, so on and so forth. They may work, but no guarantee.
Clear Cache & Dalvik Cache: This probably won't help, but there's a long shot that it would.
Fix permissions in TWRP or CWM: If it's a system app that somehow got installed incorrectly, this will help fix that issue.
Reinstall the Rom with a "so fresh and so clean clean" wipe: Wipe Cache, Dalvik Cache, /data, and /system. Make sure your rom zip file is in an accessible location, because wiping system erases your system (you won't be able to boot).
Reinstall the Rom without any mods: If you really want to take the time to flash the Rom multiple times, I'd say flash the Rom without any major mods. If nothing is broken, you can reinstall it again (after a so-fresh-and-so-clean-clean wipe) with another mod installed. It might takes hours, but if there's something inherently broken in the ROM, you'd be able to find the culprit if you do it this way.
Do not restore apps/data from TiBu: A lot of people have had issues because they've restored system apps/data through Titanium backup (TiBu). I still use TiBu for a lot of my backup needs, but I never restore system apps with it.
That's all I really got in terms of fixing the problem. I hope you can get your phone working the way you like.
topherk said:
The difficult thing when trying to troubleshoot Roms like Hyperdrive is that unless you document exactly what option you chose (which kernel, mod, theme, etc) in the Aroma installer, it'll be difficult to replicate your specific situation. Do you happen to know which settings you chose (maybe walk us through page-by-page in Aroma). Than we'd be able to help troubleshoot what's going on in your phone.
That being said, I'll walk you through some generic fixes for reboots/bootloops. You can try each one in order, and if #1 doesn't work, try #2, so on and so forth. They may work, but no guarantee.
Clear Cache & Dalvik Cache: This probably won't help, but there's a long shot that it would.
Fix permissions in TWRP or CWM: If it's a system app that somehow got installed incorrectly, this will help fix that issue.
Reinstall the Rom with a "so fresh and so clean clean" wipe: Wipe Cache, Dalvik Cache, /data, and /system. Make sure your rom zip file is in an accessible location, because wiping system erases your system (you won't be able to boot).
Reinstall the Rom without any mods: If you really want to take the time to flash the Rom multiple times, I'd say flash the Rom without any major mods. If nothing is broken, you can reinstall it again (after a so-fresh-and-so-clean-clean wipe) with another mod installed. It might takes hours, but if there's something inherently broken in the ROM, you'd be able to find the culprit if you do it this way.
Do not restore apps/data from TiBu: A lot of people have had issues because they've restored system apps/data through Titanium backup (TiBu). I still use TiBu for a lot of my backup needs, but I never restore system apps with it.
That's all I really got in terms of fixing the problem. I hope you can get your phone working the way you like.
Click to expand...
Click to collapse
Ive done options 1 and 2 but here is what I have installed on my phone
When I ran the aroma installer I chose the option to run a full installation with the devs choice of mods and stuff etc. So I have the tw launcher installed along with the multiwindow mod and pretty much everything else.
Sent from my SPH-L710 using xda app-developers app
Ok here it goes. my network service is off so i use my droin inc for games and such. running custom rom wildstang83 IceCream Scencless 1.0. im not sure what happened to my phone but i left for 3 days and come back to my phone being totally jacked up. It wot dl apps the google play reverted back to the old market icon. wont save my passwords for google sighn in. every time i go to youtube it says to re dl the google play services. im sure other stuff is messed up too. i have tried to flash another rom but when it gets loaded back up it keeps saying process. whatever failed and there a bunch of those that loop and i have to pull battery. when i try to factory reset it says everything was formatted but when i reboot phone its the sme as it was before apps and all. So is there anyone out there who can help me with this. Sorry if i posted in the wrong place or what not. i wasnt sure where to post it cuz its kinda an advanced question but not really a question just need help.
not a virus but it does sound like your phone might have exhausted all the space in the /data folder. I had a similar thing happen to me before I rooted and fixed my phone where i exhausted the space, itt went a factory reset and put the phone into an unusable state.
i don;t know anything about the rom you are running but are rooted and have CWM installed? if so, you should be able flash a new ROM to your device, GAPPS and optionally, the low space disk fix.
tekweezle said:
not a virus but it does sound like your phone might have exhausted all the space in the /data folder. I had a similar thing happen to me before I rooted and fixed my phone where i exhausted the space, itt went a factory reset and put the phone into an unusable state.
i don;t know anything about the rom you are running but are rooted and have CWM installed? if so, you should be able flash a new ROM to your device, GAPPS and optionally, the low space disk fix.
Click to expand...
Click to collapse
Yes i do have cwm but i tried to flash a new rom via the recovery section. after i choose the zip to flash everything goes as expected untill after the reboot and it goes into the setup part where u have to put gmail password and stuff in then it basically freezes up with unlimited process failures. but i will try again. cant hurt from where it is now.
if you are not doing so already, i would wipe cache and dalvik cache after flashing the rom. that may fix the FCs.
I would also suggest you run a newer jelly bean ROM like Tiny;s 5-16 with his version of GAPPS(4-05) version plus the low space disk fix so you can maintain parity with what is the latest.
I am currently using evervolve 6-25 and it is working well for me.
the reason I say that is these newer JB roms have the ability to let you skip the activation easily. I don;t know if it was some feature of GB roms but the activation wizard in the JB roms seem to be better my opinion.
When switching to a different ROM, it is crucial to wipe /system. This can be a source of FCs. Also, if switching, it is also a good idea to do factory reset.
tekweezle said:
if you are not doing so already, i would wipe cache and dalvik cache after flashing the rom. that may fix the FCs.
I would also suggest you run a newer jelly bean ROM like Tiny;s 5-16 with his version of GAPPS(4-05) version plus the low space disk fix so you can maintain parity with what is the latest.
I am currently using evervolve 6-25 and it is working well for me.
the reason I say that is these newer JB roms have the ability to let you skip the activation easily. I don;t know if it was some feature of GB roms but the activation wizard in the JB roms seem to be better my opinion.
Click to expand...
Click to collapse
I just flashed another rom i used in the past by the same dev and so this is my step by step. 1. choose zip from sd. 2. factory reset. 3. wipe dalvik cache. 4. wipe cache partition. If this doesnt work i will try jb roms but i would hate to have to dump the dev that im useing. there the most stabe roms i have come across so far
PonsAsinorem said:
When switching to a different ROM, it is crucial to wipe /system. This can be a source of FCs. Also, if switching, it is also a good idea to do factory reset.
Click to expand...
Click to collapse
what do u mean wipe /system. where do i find that. only reason i ask is cuz maybe ive never done that. but i have never had a problem withthe other 15 roms i have flashed before so thats why im so confused about what happened to my phone. all i did was shut it off and leave it home. nothing changed from my daily use before that and it was working top notch before i shut it off
im getting settings fc. youtube fc, my uploads fc, market fc, clock widget fc, internet fc, rss reader fc, htc sence fc, all those off of a fresh flash ad new sd card
Just lost my bckups that were saved on sd card so now i cant even get on it i dont get it. its not bricked but yet it i unstabe to run any rom but the preivious saved backup (now there deleted)
maybe the rom you downloaded is corrupt. worst case scenerio is that your phone is on it;s last legs.....
i would suggest you try downloading the JB rom and Gapps plus the low space fix.
http://forum.xda-developers.com/showthread.php?t=2050930
it;s kind of proven to work in my opinion. the 5-16 build is pretty stable.
what I do is flash the rom zip, gapps zip and low space zip, then wipe cache and dalvik. it probably should not make a difference but I am using TWRP as my recovery instead of CWM.
goodluck!
tekweezle said:
maybe the rom you downloaded is corrupt. worst case scenerio is that your phone is on it;s last legs.....
i would suggest you try downloading the JB rom and Gapps plus the low space fix.
http://forum.xda-developers.com/showthread.php?t=2050930
it;s kind of proven to work in my opinion. the 5-16 build is pretty stable.
what I do is flash the rom zip, gapps zip and low space zip, then wipe cache and dalvik. it probably should not make a difference but I am using TWRP as my recovery instead of CWM.
goodluck!
Click to expand...
Click to collapse
Thank u and its still not working. probably just takeing a dump on me now it is just bootlooping.
when i do a factory reset i get a wipe completed. but it says "no app2sd partition found. Skipping format of /sd-ext" could that be part of the issue?? ive never noticed that before
i don;t know if switching to TWRP might help you but it might be worth a try. maybe a coincidence but the last time I had a screw up on my Dinc installing a ROM, i was using CWM. I switch right after that. I think i did read something about TWRP specifically supporting the EXT4 Low space fix.
maybe someone more knowledgable can chime in.
tekweezle said:
i don;t know if switching to TWRP might help you but it might be worth a try. maybe a coincidence but the last time I had a screw up on my Dinc installing a ROM, i was using CWM. I switch right after that. I think i did read something about TWRP specifically supporting the EXT4 Low space fix.
maybe someone more knowledgable can chime in.
Click to expand...
Click to collapse
i will try it but it is doing the same thing on every rom i have tried to flash. ive tried 6 different roms so far and i have ran them all in the past so im incined to think its jacked. and is there a specific twrp for the different roms or can i just dl the latest version and it will work