Hello my Fellow s4 users,
Let me start off by saying I am looking for a little guidance here. I am fairly comfortable with rooting, modding, NANdroiding, Flashing, bricking, unbricking, following instructions and using the search button. I am a little dumbfounded on some of the issues I am having.
The issues seem to be isolated to touchwiz based roms only. GE and AOSP ROM's are not part of this problem.
My problem is that anytime I flash a TW based rom (For Example: The little Minions Rom, Infamous, or Wicked), which flash just fine, upon loading or the first time System UI always crashes. I click ok and let the phone sit for about ten minutes to settle. I reboot, and go through the setup wizard ( I have also done it where I skip the setup wizard altogether, with the same results.)
At this point everything is ok.
Until I try to do anything else. I experience extreme Lag, problems with apps Like the phone and Contacts, Titanium Backup is simply non-functional.
So at this point I assume it is user error.
So I Odin back to stock, run triangle away and start fresh.
I repeat this process, and root using the CF-Auto root, and reflash a rom with the same result.
The only thing I can think to do at this point is ODIN back again and try a different Root method.
Does anyone have any ideas or input?
Personally, I'm running Infamous S4 4.0 ROM w/BioShock 1.0 Kernel and 3.1.1 3Minit Framework. Have not experienced the issues you're describing though. You seem to have taken many of the appropriate steps to attempt to solve your issues.
The steps I'd do and some stuff I'd look at, whether related to your issues, and/or tried already are:
- if using TWRP Recovery 2.6.0.0, flash TWRP 2.5.0.2.
- if not already, format card, if 64gb, to Fat32, as some ROMs won't run ExFAT.
- Full Wipe and ODIN Samsung Stock Firmware.
- Save files needed and Full Wipe, including device memory, as you may have a conflict with certain files.
- with Infamous S4, it has Root, so it's not necessary to root via CF-AUTO-ROOT, but can't hurt I guess. CF-AUTO-ROOT is my preferred choice for rooting.
- Uninstall and reinstall TiBu if having issues after doing the above.
- Sometimes when there are issues after flashing ROMs, wiping Cache and Dalvik cache can rectify many issues.
- make sure running appropriate Kernel for the M919. Appropriate Radio goes without saying, although most ROMs don't have the Radio cooked in because the wrong Radio can Hard Brick.
Anyway, I'm sure I missed something which may turn out to be the Golden Challis :laugh:, but the above hopefully will help.
As a note, and possibly to get more feedbackffrom the source, you can post your inquiry regarding Infamous S4 in thetthread as all are extremely helpful, and the Developers offer excellent support. The same with Minions, as they are part of the Infamous Team. I don't run Wicked ROM but have heard excellent feedback, and their support appears to also be excellent.
Feel free to copy this post if you'd like to post it in Infamous S4 thread, as there'll be others to expand on my response
OP:
What phone?
What baseband?
What recovery?
I am M919 tmobile
MDL
CWM.
...and have no issues with Wicked 5.1.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SGH-M919 using Tapatalk 4 Beta
Def gonna give the downgrade of TWRP and some of the other things you said a shot. Thanks for the info, will head over to the infamous thread after.
Sent from my SGH-M919 using xda premium
ODIN Recovery tips
3r0k said:
Def gonna give the downgrade of TWRP and some of the other things you said a shot. Thanks for the info, will head over to the infamous thread after.
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
You may find TWRP 2.6.0.0 the cause of some issues, and that 2.5.0.2 will resolve them.
I'll post some ODIN Recovery tips, if you should need them:
Here's the TWRP 2.5.0.2 file:
https://hotfile.com/dl/230303459/7ce1553/openrecovery-twrp-2.5.0.2-jfltexx.tar.html
Install with ODIN.
Steps to follow........
Method #1 -
Place file in PDA box*
Uncheck all other boxes.
Press start.
When installation is complete, unplug usb cord and pull the battery.
Insert the battery but Don't turn on the phone.
Place phone in Recovery mode via the Power + Volume up buttons.
Method #2 -
The other way I've read to install TWRP Recovery is:
Place the TWRP 2.5.0.2 tar in the PDA box*
Check the auto reboot box and f time reset box.
Start the installation and let the phone reboot.
I believe the above method is the method of choice, but sometimes the Recovery doesn't take, so Method #2 above is recommended.
Here is an explanation why:
http://forum.xda-developers.com/showpost.php?p=41166759&postcount=28
Gunkk said:
OP:
What phone?
What baseband?
What recovery?
I am M919 tmobile
MDL
CWM.
...and have no issues with Wicked 5.1.
Sent from my SGH-M919 using Tapatalk 4 Beta
Click to expand...
Click to collapse
everything same as you except Im using twrp.
There's your sign...
Sent from my SGH-M919 using Tapatalk 4 Beta
Ok, getting home in a bit will keep you guys updates. thanks for the help.
3r0k said:
Ok, getting home in a bit will keep you guys updates. thanks for the help.
Click to expand...
Click to collapse
Sounds :good:
ODINing 2.5.0.2 I think will solve your issues.
Wipe cache and dakvik cache after booting into Recovery and prior to booting system.
If still issues, start with ODINing Samsung Stock Firmware and Full Wipe. Internal wipe most likely Not necessary.
Hopefully nothing else will need to be done after TWRP 2.5.0.2 is installed
Biker1 said:
Sounds :good:
ODINing 2.5.0.2 I think will solve your issues.
Wipe cache and dakvik cache after booting into Recovery and prior to booting system.
If still issues, start with ODINing Samsung Stock Firmware and Full Wipe. Internal wipe most likely Not necessary.
Hopefully nothing else will need to be done after TWRP 2.5.0.2 is installed
Click to expand...
Click to collapse
Yea, still gettting errors.
Even tried to switch to CWM, and that had issues with backing up.
Looks Like I am gonna ODIN Back and full wipe.
3r0k said:
Yea, still gettting errors.
Even tried to switch to CWM, and that had issues with backing up.
Looks Like I am gonna ODIN Back and full wipe.
Click to expand...
Click to collapse
Yes, ODIN the Samsung Stock Firmware and start with a clean slate.
ODIN TWRP 2.5.0.2 and you should be good to go.
If you have the Firmware downloaded already, and checked the md5 checksum to insure your download matches the file, it won't take you long at all.
20m all together;
Firmware.
Recovery
ROM/Kernel
Infamous S4 Roots you, so hopefully you'll be up & running i nno time.
Sometimes just flashing the Firmware and starting from there, saves much trouble shooting time, avoids unsuspected and inadvertently installed conflicts and simplifies things back to its basics.
In your case, TWRP 2.5.0.2 only was worth a shot
Biker1 said:
Yes, ODIN the Samsung Stock Firmware and start with a clean slate.
ODIN TWRP 2.5.0.2 and you should be good to go.
If you have the Firmware downloaded already, and checked the md5 checksum to insure your download matches the file, it won't take you long at all.
20m all together;
Firmware.
Recovery
ROM/Kernel
Infamous S4 Roots you, so hopefully you'll be up & running i nno time.
Sometimes just flashing the Firmware and starting from there, saves much trouble shooting time, avoids unsuspected and inadvertently installed conflicts and simplifies things back to its basics.
In your case, TWRP 2.5.0.2 only was worth a shot
Click to expand...
Click to collapse
Ok, some wierd developments here. I ODIN back to stock and everything goes fine. FLash the TWRP 2.5.0.2. Make a backup. Factory Reset, Wipe Data, Cahe, Dalvik, and System ( tried re odining back to stop reflashing everything and NOT wiping system just to see, same result.) flash infamous, when I get to the initial setup wizard, SystemUI still crahses then settings crash. Go back to Recovery, flash wicked, and now everything flashed fine on Wicked. No force closes or anything, running buttery smooth. I guess this solves half of my issue.
3r0k said:
Ok, some wierd developments here. I ODIN back to stock and everything goes fine. FLash the TWRP 2.5.0.2. Make a backup. Factory Reset, Wipe Data, Cahe, Dalvik, and System ( tried re odining back to stop reflashing everything and NOT wiping system just to see, same result.) flash infamous, when I get to the initial setup wizard, SystemUI still crahses then settings crash. Go back to Recovery, flash wicked, and now everything flashed fine on Wicked. No force closes or anything, running buttery smooth. I guess this solves half of my issue.
Click to expand...
Click to collapse
If you:
- did a Full Wipe
- ODINd Samsung Stock Firmware
- ODINd TWRP 2.5.0.2 Recovery
- checked your ROM download
- Flashed your ROM (with Kernel cooked in)
- Wiped cache and dalvik cache
and your still having issues, there must be an answer. I just don't have it, but I'd say the issue is a conflict with something that is installed or not installed on the S4.
Something to look into which will cause Boot-loops is if you have the wrong 3Minit app installed which is causing a conflict with 3Minit Framework. It happened to me with Alpha 6.0 because I didn't install the updated 3Minit app first after boot up, and attempted to use the older version I had installed on Infamous S4. I caused the issue in this instance.
Biker1 said:
If you:
- did a Full Wipe
- ODINd Samsung Stock Firmware
- ODINd TWRP 2.5.0.2 Recovery
- checked your ROM download
- Flashed your ROM (with Kernel cooked in)
- Wiped cache and dalvik cache
and your still having issues, there must be an answer. I just don't have it, but I'd say the issue is a conflict with something that is installed or not installed on the S4.
Something to look into which will cause Boot-loops is if you have the wrong 3Minit app installed which is causing a conflict with 3Minit Framework. It happened to me with Alpha 6.0 because I didn't install the updated 3Minit app first after boot up, and attempted to use the older version I had installed on Infamous S4. I caused the issue in this instance.
Click to expand...
Click to collapse
Followed that exactly. I cant even get to the point on the infamous to install the 3minit app. Everything crashes in the setup wizard.
3r0k said:
Followed that exactly. I cant even get to the point on the infamous to install the 3minit app. Everything crashes in the setup wizard.
Click to expand...
Click to collapse
At this point the only thing I can suggest is to:
- take a step back and a deep breath, and come back to the issue later on with a 'fresh set of eyes' so to speak.
I know that when I start troubleshooting any issue I may run into, Android or something else entirely different, I sometimes get frustrated and tunnel vision, and I keep making the same mistake each time, which of course doesn't resolve the issue.
I then come back to the issue and say, 'Hmmm, how'd I miss that?'
And there are times when I'm looking at an issue I'm having and I just can't see where the problem is, so I get 'another set of eyes' to view the issue and that person says 'here's your problem,' and I'm like, 'Wow, how'd I miss that? Thanks!'
I'm not saying that the above applies to you in your given situation, just mentioning it from the standpoint of my experiences and those of others.
Regarding troubleshooting, sometimes it does takes 'a fresh set of eyes' to look at the issue, as the person looking at the issue has a fresh aspect to what they are viewing, and not tunnel vision which can happen due to repetitiveness, frustration and many of other things. And more than not the solution ends up being a very simple one.
Sorry to be so long winded, But hopefully something in the above comments helps you to resolve the issues your having.
And you say this only happens on Touchwiz roms?
What about the stock touchwiz after you odin back to stock? Does that give you similar problems?
If so Im wondering if you have a faulty piece of hardware that touchwiz uses but aosp doesn't. So the hardware is still bad in aosp but its never activated so it doesn't cause the error. But if the stock rom works the that theory is shot....
Sent from your phone. You should be careful where you leave that thing.
Skipjacks said:
And you say this only happens on Touchwiz roms?
What about the stock touchwiz after you odin back to stock? Does that give you similar problems?
If so Im wondering if you have a faulty piece of hardware that touchwiz uses but aosp doesn't. So the hardware is still bad in aosp but its never activated so it doesn't cause the error. But if the stock rom works the that theory is shot....
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
Stock ROM works great.
Wicked is now working and running great also.
I cannot Get Inbfamous to boot with out a ton of force closes. Even after ODining back to stock. Then Flashing TWRP and then flashing Infamous.
I guess Ill have to stick with Wicked for now, not like thats a bad thing at all. Im just ticked off when things dont work for me but they do for everyone else.
Biker1 said:
At this point the only thing I can suggest is to:
- take a step back and a deep breath, and come back to the issue later on with a 'fresh set of eyes' so to speak.
I know that when I start troubleshooting any issue I may run into, Android or something else entirely different, I sometimes get frustrated and tunnel vision, and I keep making the same mistake each time, which of course doesn't resolve the issue.
I then come back to the issue and say, 'Hmmm, how'd I miss that?'
And there are times when I'm looking at an issue I'm having and I just can't see where the problem is, so I get 'another set of eyes' to view the issue and that person says 'here's your problem,' and I'm like, 'Wow, how'd I miss that? Thanks!'
I'm not saying that the above applies to you in your given situation, just mentioning it from the standpoint of my experiences and those of others.
Regarding troubleshooting, sometimes it does takes 'a fresh set of eyes' to look at the issue, as the person looking at the issue has a fresh aspect to what they are viewing, and not tunnel vision which can happen due to repetitiveness, frustration and many of other things. And more than not the solution ends up being a very simple one.
Sorry to be so long winded, But hopefully something in the above comments helps you to resolve the issues your having.
Click to expand...
Click to collapse
No apology needed, you have by far been the most helpful.
Maybe Ill just wait for a new build to come out and go from there.
Maybe Ill possibly look into a log cat to send the Dev. I dont know if the log can catch the errors in my process but maybe.
3r0k said:
Stock ROM works great.
Wicked is now working and running great also.
I cannot Get Inbfamous to boot with out a ton of force closes. Even after ODining back to stock. Then Flashing TWRP and then flashing Infamous.
I guess Ill have to stick with Wicked for now, not like thats a bad thing at all. Im just ticked off when things dont work for me but they do for everyone else.
Click to expand...
Click to collapse
Are you restoring data from other installs? Like are you using titanium to restore your apps and stuff?
If you are, and you are letting Titanium restore system data like settings and what not, that could be causing your issue. You can use titanium to restore things like data usage and wifi passwords because custom roms don't typically modify those parts of touchwiz so the data is still valid. But if you restore some other system data from one rom to another for things that have been modified you will cause failures like you are getting.
If you are doing this, try installing Infamous and not restoring any data at all. Just use it like it comes out of the box for an hour and see if youn still have the closes.
Sent from your phone. You should be careful where you leave that thing.
Skipjacks said:
Are you restoring data from other installs? Like are you using titanium to restore your apps and stuff?
If you are, and you are letting Titanium restore system data like settings and what not, that could be causing your issue. You can use titanium to restore things like data usage and wifi passwords because custom roms don't typically modify those parts of touchwiz so the data is still valid. But if you restore some other system data from one rom to another for things that have been modified you will cause failures like you are getting.
If you are doing this, try installing Infamous and not restoring any data at all. Just use it like it comes out of the box for an hour and see if youn still have the closes.
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
If I did restore any other system data it would be coming from other touchwiz ROMS, however I am not. The problem is at least on the ROMS I am having difficulty with I cant get far enough to reinstall TiBu anyways. The systemUI crashes immediately as soon as the setup wizard loads, then when I get to the Wi-Fi password screen, the settings force close and the Setup Wizard starts all over again.
Related
Hey there everyone,
I am honestly at a bit of a loss.
I have an AT&T GS3, and I noticed that all the bloatware was SERIOUSLY draining the battery and hogging up RAM, so I thought it would be a great idea to get a custom rom to enhance my phone.
I used the GS3 Toolkit to flash TWRP recovery. - All went well
I read up on some different Roms, and i chose to install http://forum.xda-developers.com/showthread.php?t=2089821
I installed RLS16
I followed the instructions,
Wipe data/factory reset
Wipe dalvik cache
Wipe /system
I went through the Aroma installer and chose to install the Developer's Pick.
This includes a bunch of little addons like 4.2 camera, gallery, keyboard, etc.
but it also installs lean kernel.
The install went fine, nothing said it failed
but once i was in the rom. Things got terrible.
My phone randomly crashed and shut off, like within minutes each time, camera would crash the phone, causing it to shut off, etc.
So i went through the GS3 toolkit, downloaded and reflashed the stock Rom and recovery.
Once it booted, I keep getting "Unfortunately Messaging has Stopped" and I cannot receive or send text messages, even through other texting programs like Handcent SMS.
No matter what, it keeps crashing (the messaging, not the rom). I factory reset, wiped, everything. Nothing will fix it.
I thought that maybe the stock rom doesnt include stock kernel? So i went online, downloaded the stock kernel, flashed, reflashed stock rom, and STILL the same thing. Messaging has stopped working.
Also as a side note, when i tried to do a google voice search. I get a page saying Sorry and that my computer or phone might be sending network requests or something along those lines.
I cannot think of anything else I can do....
If anyone has any idea, please let me know...
Thanks!
eternalcold said:
Hey there everyone,
I am honestly at a bit of a loss.
I have an AT&T GS3, and I noticed that all the bloatware was SERIOUSLY draining the battery and hogging up RAM, so I thought it would be a great idea to get a custom rom to enhance my phone.
I used the GS3 Toolkit to flash TWRP recovery. - All went well
I read up on some different Roms, and i chose to install http://forum.xda-developers.com/showthread.php?t=2089821
I installed RLS16
I followed the instructions,
Wipe data/factory reset
Wipe dalvik cache
Wipe /system
I went through the Aroma installer and chose to install the Developer's Pick.
This includes a bunch of little addons like 4.2 camera, gallery, keyboard, etc.
but it also installs lean kernel.
The install went fine, nothing said it failed
but once i was in the rom. Things got terrible.
My phone randomly crashed and shut off, like within minutes each time, camera would crash the phone, causing it to shut off, etc.
So i went through the GS3 toolkit, downloaded and reflashed the stock Rom and recovery.
Once it booted, I keep getting "Unfortunately Messaging has Stopped" and I cannot receive or send text messages, even through other texting programs like Handcent SMS.
No matter what, it keeps crashing (the messaging, not the rom). I factory reset, wiped, everything. Nothing will fix it.
I thought that maybe the stock rom doesnt include stock kernel? So i went online, downloaded the stock kernel, flashed, reflashed stock rom, and STILL the same thing. Messaging has stopped working.
Also as a side note, when i tried to do a google voice search. I get a page saying Sorry and that my computer or phone might be sending network requests or something along those lines.
I cannot think of anything else I can do....
If anyone has any idea, please let me know...
Thanks!
Click to expand...
Click to collapse
When you flashed stock, did you flash the one for your carrier? (It should flash the kernel at the same time)
Did you try clearing the messaging app's data/cache?
Did you try flashing another custom ROM to see if you still get the errors? If not, could give 4.2.1 a shot.
BWolf56 said:
When you flashed stock, did you flash the one for your carrier? (It should flash the kernel at the same time)
Did you try clearing the messaging app's data/cache?
Did you try flashing another custom ROM to see if you still get the errors? If not, could give 4.2.1 a shot.
Click to expand...
Click to collapse
Yeah i flashed the one for my carrier. And i figured it would do the kernel, but just in case i tried flashing it separately....
and yeah i did try wiping the data/cache, but i will try it again.
and I could always try flashing another custom rom. Do you have any suggestions? i just want one that works quickly, is stable, and has messaging lol
eternalcold said:
Yeah i flashed the one for my carrier. And i figured it would do the kernel, but just in case i tried flashing it separately....
and yeah i did try wiping the data/cache, but i will try it again.
and I could always try flashing another custom rom. Do you have any suggestions? i just want one that works quickly, is stable, and has messaging lol
Click to expand...
Click to collapse
Look in my sig I don't give suggestion per say cause it's up to the user's preference but I'll always be running something that works.
BWolf56 said:
Look in my sig I don't give suggestion per say cause it's up to the user's preference but I'll always be running something that works.
Click to expand...
Click to collapse
I might try that one out. I was looking at some reviews, someone said there may be Bluetooth issues. I just bought the Moga, and i need BT to work perfecty...
Any input on that?
eternalcold said:
I might try that one out. I was looking at some reviews, someone said there may be Bluetooth issues. I just bought the Moga, and i need BT to work perfecty...
Any input on that?
Click to expand...
Click to collapse
Best thing to do is to read changelogs but for now I'll give you the answer, it has been fixed a few releases ago in Task650's AOKP.
BWolf56 said:
Best thing to do is to read changelogs but for now I'll give you the answer, it has been fixed a few releases ago in Task650's AOKP.
Click to expand...
Click to collapse
Alright, i'll flash that one, i'll post to here when it's finished. Thanks!
Did you check your IMEI?
xBeerdroiDx said:
Did you check your IMEI?
Click to expand...
Click to collapse
Just checked, my IMEI is there.
Also, i found this thread
http://forum.xda-developers.com/showthread.php?t=1804782
but their images wont show. Any idea what route they are taking to solve this??
eternalcold said:
Just checked, my IMEI is there.
Also, i found this thread
http://forum.xda-developers.com/showthread.php?t=1804782
but their images wont show. Any idea what route they are taking to solve this??
Click to expand...
Click to collapse
That guy flashed the bootloaders. I'm not sure what the pictures are supposed to be but they don't seem to lead to anything.
My take on it: Don't play with bootloaders, it's the only way to really brick your phone (if something goes wrong that is).
BWolf56 said:
That guy flashed the bootloaders. I'm not sure what the pictures are supposed to be but they don't seem to lead to anything.
My take on it: Don't play with bootloaders, it's the only way to really brick your phone (if something goes wrong that is).
Click to expand...
Click to collapse
Understood, I wont mess with them.
I really just want to understand a couple things.
1. Why did the ROM I installed before work for everyone else except me? and i followed the instructions.
and 2. after flashing to stock, how am I unable to fix this?
mainly to just learn what went wrong.
Sometimes the reason just...you had a bad flash or something broke down in there. I did the CF easy root method and flashed TWRP in goo manager and then started flashing. I've never tried the toolkit but like anything many times it just depends on the download you got or a bad flash. We've all had several...just hate when it involves rooting or using ODIN.
hednik said:
Sometimes the reason just...you had a bad flash or something broke down in there. I did the CF easy root method and flashed TWRP in goo manager and then started flashing. I've never tried the toolkit but like anything many times it just depends on the download you got or a bad flash. We've all had several...just hate when it involves rooting or using ODIN.
Click to expand...
Click to collapse
Thanks,
Is there any way to repair it?
Alright, so....
I think i have figured out what the issue was. Or by random chance got it fixed.
I was going to try to install the Synergy Rom. And while going through the custom setup, i noticed "Install AOSP Messaging" and "Install TW Messaging"
I chose the TW messaging, and went through the rest of the installer.
For some reason i kept hanging at the "Samsung Galaxy S3" logo, and it would not boot.
(Honestly, i've used custom roms since the HTC Touch Pro 2, and i've NEVER had such issues. And i personally think the TP2 was way more difficult lol)
So I ONCE AGAIN flashed to stock. and randomly the messaging works!
I only can guess that even when flashing the stock rom, it doesnt change something regarding the messaging app. I'm not sure. All i know is that i'm on stock again and everything is working. I highly doubt i'm going to try another custom rom for a while until i have a full understanding of what happened.
But in case anyone else was having this problem, i hope this helped.
NEED HELP RIGHT AWAY! WORK PHONE DEAD IN WATER!
My battery died during a boot and the phone is still stuck at the Samsung S screen. The boot sound plays and the samsung animation plays continuously but never gets further. I left it for 20+ minutes and rebooted trying several times without success.
I can still access TWRP recovery. I tried fix permissions and clear caches but same problem exists. I mounted the internal and external sd and did full backups to my PC but I do not have a current full backup in TWRP or nandroid I may have an older TWRP backup from just after flashing the ROM but does not have apps or data.
Is there anything I can do to repair the boot without reflashing the ROM? What would happen if I flashed the same ROM over the current ROM? Just want to know if there is a possibility that I would not have to completely resetup the phone.
I have been on here before but just created a new account to ask for help. I have read the ENTIRE Jedi Mind Trick Rom thread before but dont remember seeing anything that would help this and I really could use a solution ASAP!
Thanks in advance. Any help is very appreciated!!
DirtyBreakz said:
NEED HELP RIGHT AWAY! WORK PHONE DEAD IN WATER!
My battery died during a boot and the phone is still stuck at the Samsung S screen. The boot sound plays and the samsung animation plays continuously but never gets further. I left it for 20+ minutes and rebooted trying several times without success.
I can still access TWRP recovery. I tried fix permissions and clear caches but same problem exists. I mounted the internal and external sd and did full backups to my PC but I do not have a current full backup in TWRP or nandroid I may have an older TWRP backup from just after flashing the ROM but does not have apps or data.
Is there anything I can do to repair the boot without reflashing the ROM? What would happen if I flashed the same ROM over the current ROM? Just want to know if there is a possibility that I would not have to completely resetup the phone.
I have been on here before but just created a new account to ask for help. I have read the ENTIRE Jedi Mind Trick Rom thread before but dont remember seeing anything that would help this and I really could use a solution ASAP!
Thanks in advance. Any help is very appreciated!!
Click to expand...
Click to collapse
I think you would have to reflash, sorry . You should:
1.) Delete cache
2.) Delete dalvik cache
3.) Delete data/factory reset
4.) Flash new ROM
5.) Flash GApps (if not included in the ROM).
You might be able to salvage some data back by going into download mode, but I'm not to knowledgeable in that area. Good luck.
If you flash over your current rom with same rom you will still have your apps and data. All a dirty flash does is install new system apps from the rom itself so your data should not be effected.
Sent from my SGH-T989 using Tapatalk
Still wont boot
richardlibeau said:
If you flash over your current rom with same rom you will still have your apps and data. All a dirty flash does is install new system apps from the rom itself so your data should not be effected.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Ok, I thought I remembered hearing that. I just reflashed the ROM over the old one without clearing any caches. Unfortunately the phone still gets stuck at the Samsung S boot screen. The animation continues and it does not appear frozen but it never goes anywhere.
I am thinking of wiping the system/factory reset then reinstall the ROM. before I do that though, is there any way to copy over files from the system partition before flash and then copy them back overwriting the current ones after flashing the ROM. Will this work since it is the same ROM? I dont care if its stable. Just want to recoup my data and backup and then I will completely redo the ROM again.
Thanks for your input guys!
Restore a backup
----------------------------------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm full of great idea's, but don't have the time to create them or learn the coding to create them. If you want to make one of my ideas a reality just message me and I will give you my idea as specific as possible.
ideas:
-launcher/lock screen
-line rider type game where you control the character
-2d fighting game like art of fighting for the SNES
-multiplayer fps where you create your own map with a creative mode (minecraft style)
-roller coaster tycoon style game
-many more!
Just message me which idea you want info on and I'll tell you!
----------------------------------------------
DirtyBreakz said:
Ok, I thought I remembered hearing that. I just reflashed the ROM over the old one without clearing any caches. Unfortunately the phone still gets stuck at the Samsung S boot screen. The animation continues and it does not appear frozen but it never goes anywhere.
I am thinking of wiping the system/factory reset then reinstall the ROM. before I do that though, is there any way to copy over files from the system partition before flash and then copy them back overwriting the current ones after flashing the ROM. Will this work since it is the same ROM? I dont care if its stable. Just want to recoup my data and backup and then I will completely redo the ROM again.
Thanks for your input guys!
Click to expand...
Click to collapse
Do a full back up now then wipe the whole phone, Flash new rom then boot into recovery and go to advanced restore and you can just restore system or data instead of the whole back up. But it sounds like your problem is in your system somewhere though since it is not booting all the way. Do you have scripts that clash? Tweaks etc. Try flashing a new kernel and see if it boots up.
richardlibeau said:
Do a full back up now then wipe the whole phone, Flash new rom then boot into recovery and go to advanced restore and you can just restore system or data instead of the whole back up. But it sounds like your problem is in your system somewhere though since it is not booting all the way. Do you have scripts that clash? Tweaks etc. Try flashing a new kernel and see if it boots up.
Click to expand...
Click to collapse
Ok. I flashed the same rom over top of the current one and got the same results. I then booted into recovery, wiped system, flashed the rom again and got the same results.
One thing I noticed is that when I ran fix permissions both before I reflashed and after, it was super quick to finish lasting only a couple seconds where normally it takes a couple minutes for fix permissions.
I did a backup in TWRP right after the crash. I will try flashing a kernal as a last attempt before doing a full wipe and flash. I have to find which kernel it is. Do you recommend flashing the same kernel or a specific kernel?
DirtyBreakz said:
Ok. I flashed the same rom over top of the current one and got the same results. I then booted into recovery, wiped system, flashed the rom again and got the same results.
One thing I noticed is that when I ran fix permissions both before I reflashed and after, it was super quick to finish lasting only a couple seconds where normally it takes a couple minutes for fix permissions.
I did a backup in TWRP right after the crash. I will try flashing a kernal as a last attempt before doing a full wipe and flash. I have to find which kernel it is. Do you recommend flashing the same kernel or a specific kernel?
Click to expand...
Click to collapse
What rom and os are you on ics or jb? Same kernel is ok but a new one might be better
Sent from my SGH-T989 using Tapatalk
richardlibeau said:
What rom and os are you on ics or jb? Same kernel is ok but a new one might be better
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I'm running Jedi Mind Trick x4 (JMTx4) ICS with its kernel. It looks like it uses Faux kernel. Not sure where to get it or one that will work. I was just looking through the thread here and also googled it but didnt get much. I went to the Faux repository but it was a bit confusing. I have never downloaded or flashed a separate kernel. Always just used the one packaged with the rom. Please direct me to a link to place to download the kernels that I could use with this rom.
DirtyBreakz said:
I'm running Jedi Mind Trick x4 (JMTx4) ICS with its kernel. It looks like it uses Faux kernel. Not sure where to get it or one that will work. I was just looking through the thread here and also googled it but didnt get much. I went to the Faux repository but it was a bit confusing. I have never downloaded or flashed a separate kernel. Always just used the one packaged with the rom. Please direct me to a link to place to download the kernels that I could use with this rom.
Click to expand...
Click to collapse
Any of these will work. I can't find faux right now. Just flash and reboot.
richardlibeau said:
Any of these will work. I can't find faux right now. Just flash and reboot.
Click to expand...
Click to collapse
I ended up having to do a full wipe and flash to boot again. I did try an advanced restore afterwards like you mentioned restoring just DATA, the phone stopped booting again so I assume that is where the corruption is. I am going to try the kernel now as well and see if it changes anything.
Thank you very much for all you help.
DirtyBreakz said:
I ended up having to do a full wipe and flash to boot again. I did try an advanced restore afterwards like you mentioned restoring just DATA, the phone stopped booting again so I assume that is where the corruption is. I am going to try the kernel now as well and see if it changes anything.
Thank you very much for all you help.[/QU
Corruption is usually in the system somewhere so that's odd. Hopefully one of the kernels will help you.
Click to expand...
Click to collapse
richardlibeau said:
DirtyBreakz said:
I ended up having to do a full wipe and flash to boot again. I did try an advanced restore afterwards like you mentioned restoring just DATA, the phone stopped booting again so I assume that is where the corruption is. I am going to try the kernel now as well and see if it changes anything.
Thank you very much for all you help.[/QU
Corruption is usually in the system somewhere so that's odd. Hopefully one of the kernels will help you.
Click to expand...
Click to collapse
Ok. I restored data again and confirmed no boot, then flashed the new kernel and still no joy
Looks like something is corrupted in the data. Do you know of anything else I can try before fully wiping/reflashing again?
Click to expand...
Click to collapse
Not at this point sorry. Seems that something really weird. Best just to reflash now and be glad it's not fully bricked.
Sent from my SGH-T989 using Tapatalk
richardlibeau said:
Not at this point sorry. Seems that something really weird. Best just to reflash now and be glad it's not fully bricked.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Right on! Thanks again for all the advice. Just a quick question before I am off to reflash again...
Is it possible to recover any information from the data in the twrp backup once I have reflashed? Mainly looking for text notes from Note Everything and SMS messages.
If it's a tar file you can through a file explorer that can open tar files like winrar, winzip. etc. You just extract what you want. So yes you can salvage things that way.
Sent from my SGH-T989 using Tapatalk
file and data recovery
DirtyBreakz said:
I ended up having to do a full wipe and flash to boot again. I did try an advanced restore afterwards like you mentioned restoring just DATA, the phone stopped booting again so I assume that is where the corruption is. I am going to try the kernel now as well and see if it changes anything.
Thank you very much for all you help.
Click to expand...
Click to collapse
I know I'm about two weeks after this one, but here are some thoughts on accessing the data in the backup.
My arsenal includes Root Explorer, FX Explorer by nextapp (File Explorer is the name that shows up in google play), ROM Manager, and Titanium Backup.
I do not use Root Explorer nearly as much as I use FX. To me, FX is easier to use, runs in the background, and can run multiple operations at the same time.
FX Explorer can extract .tar files so you can pull individual files from the archive, but it extracts the entire contents of the archive. FX Explorer can also mount read/write of the /system if the phone is rooted. You will get a little nag screen every time you mount r/w, but that's about it.
Yes, it's worth paying the couple of bucks in Google Play for the full versions of these apps. The only caveat with FX Explorer is that in order to get FULL app functionality, you have to install it in modules. I think there are a total of 4, maybe 5 modules for the app. The main app which is free, the root module which is NOW free, there is a paid module for media, and a paid module for network functionality which includes hosting a file server on the phone as well as accessing Google Drive, skydrive, and other cloud based storage solutions.
Titanium Backup can also pull individual app apk's out of a Clockwork Nand backup, but it will miss /lib files that some apps like swype need.
FYI, I just installed JMTX4 for my T989, and wanted the Swype from the stock rom. Turns out, installing JUST the swype apk out of the backup wasn't enough. Using FX, I extracted the system .tar portion of the backup, and extracted the two files I needed, including the swype apk, and using FX, I pasted them into the /system/app and /system/lib directories as the link I found said to do, only I did it directly on the phone without having to use the adb interface from my pc.
Not to revive an old thread but I wanted to update so others may be able to use the info.
Found out that the reason for the crashes was a hardware (power button) issue. The power button would get stuck in several different positions causing the phone to reboot or boot loop and not boot at all. T-mo was nice enough to replace my phone out of warranty for me after a little haggling so no more issues
I have since updated and running Jedi Mind Trick JBv4 now. I actually think I like JMTv4 better. It runs great. I'm just not entirely fond of some of the new Android changes in JB.
DirtyBreakz said:
Not to revive an old thread but I wanted to update so others may be able to use the info.
Found out that the reason for the crashes was a hardware (power button) issue. The power button would get stuck in several different positions causing the phone to reboot or boot loop and not boot at all. T-mo was nice enough to replace my phone out of warranty for me after a little haggling so no more issues
I have since updated and running Jedi Mind Trick JBv4 now. I actually think I like JMTv4 better. It runs great. I'm just not entirely fond of some of the new Android changes in JB.
Click to expand...
Click to collapse
my phone is doing the same thing. what did you say to tmobile?
adamwithane said:
my phone is doing the same thing. what did you say to tmobile?
Click to expand...
Click to collapse
Call tech support and tell them you are having problems with your power button. Hopefully you will get a helpful rep. If not, call back and try again. If you are in warranty it should be no issue.
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
Hello, I am totally new to rooting and etc.
I am trying out the wicked sensations v4.1 for galaxy s 3 and every time I attempt to load up my titainium backup to restore my apps my phone hard resets to the prompt and etc. I don't know whats the cause and I would appreciate every bit of info I could get.
Sometimes it does it on its own just a hard reboot for no particular reason. Any info on this? I wiped my dalvik (sp) cache and did a factory reset before I started the rom. I had it rooted to an earlier model of Blaze. I wanted the multiwindow function but if there is an easy way to get this I am willing to change the rom to something with Premium suite on it. Any info guys? will thank who ever contributes.
also I tried to search for similar. Nothing that i found or the search engine found was really point on. sorry if I offend you old-heads..
love.
M F Money said:
Hello, I am totally new to rooting and etc.
I am trying out the wicked sensations v4.1 for galaxy s 3 and every time I attempt to load up my titainium backup to restore my apps my phone hard resets to the prompt and etc. I don't know whats the cause and I would appreciate every bit of info I could get.
Sometimes it does it on its own just a hard reboot for no particular reason. Any info on this? I wiped my dalvik (sp) cache and did a factory reset before I started the rom. I had it rooted to an earlier model of Blaze. I wanted the multiwindow function but if there is an easy way to get this I am willing to change the rom to something with Premium suite on it. Any info guys? will thank who ever contributes.
also I tried to search for similar. Nothing that i found or the search engine found was really point on. sorry if I offend you old-heads..
love.
Click to expand...
Click to collapse
Does the phone reboot when you restore any app, or only certain ones? I know that some (if not all) system apps shouldn't be restored through titanium backup, as differing versions and mods will affect these differently. Below I have quoted a simple guide I wrote up a while ago to help someone else with TiBu issues. Hopefully it helps you understand TiBu more.
Ok, first I'll describe what you did and how that (most likely) messed up your phone. Then I'll describe what you can do to fix it.
Problem
It seems like your original flash of CM10.1 went smoothly. It must have been something to do with your Titanium Backup (TiBu) restores. More than likely, you tried to restore too much. In TiBu, the different apps have different colors: Red, Yellow, Green, and White. In the menu, you can see the following Legend:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
White: User Application. These are apps that you installed from the Play Store or sideloaded by directly installing an apk. These are safe to restore.
Red: System Application. These are system files that heavily rely on which Android version (4.1.x vs. 4.2.x) and whether you're on TW or AOSP. I always try to avoid restoring these backups (even when just upgrading to a newer version of the same Rom). Some people will say that you can restore the Data only for these, but my motto is: caution will help prevent mistakes (ground-shaking, I know).
Green: System Service with Useful Data: These are system apps that have useful information (such as User Accounts, etc.). I treat these the same as Red Backups, but am a bit more likely to restore the data of them (green means go, right?).
Yellow: These backups are system data that can be restored as an xml file. These are inherently safer than the red and green ones, and I say restore away (I always restore my Call Log, Messages, and Wi-Fi Access Points).
The reason you were getting FCs was restoring a red or green backup. This can sometimes work, but has a lot of potential for issues when switching between TW and AOSP Roms. Most likely something in your /system folder is messed up due to restoring an app. Even when you flash a new Rom, it just overwrites items in your System folder, it doesn't wipe /System. So whatever is wrong in your /System folder is still there, regardless of what you flash.
Click to expand...
Click to collapse
My thought is that restoring system apps/data is what's causing the reboots. Steer clear of those and you should be fine.
Hope this helps!
Thanks!
I have been trying g to get back to you for 20minutes. It just kept restarting without me doing anything. It's a blessing this went thru. But I think something is wrong with this room. The smart rotation and the other things was turned on.
I turned them off and now it doesn't seem to want to restart.
Problem is now that I gotta find a room with the full capabilities That I wanted in this rom, I really wanted to show this off any advice?
Sent from my SPH-L710 using xda app-developers app...
update:
it just reset again i jumped to pc for a second. im getting ready to goto work, i have the app installed i jst hope i didnt wreck my phone any advice is appreciated
Usually when I flash a rom and it just blasts off with random reboots right after i restore apps from TiBa, it's probably a bad download / Custom Kernel being wonky
or you're coming from AOSP JB to TW JB Vise Versa.
I'd suggest re-downloading the rom on PC w/ Lan connection, using the original USB Cable to transfer files from PC to Device.
Underclocking your devices max speed to 1026, or 1242. Usually coming from a different JB Based Rom, AOSP to TW or TW to AOSP, its best NOT to restore
data of apps when you restore from Titanium Backup, App Data from AOSP JB can really conflict with App Data on TW JB whether or not
you've wiped Dalvik Cache, or Cache. At least that was the issue with me when i switched between the two and im talking normal installed apps
and not system apps.
Usually if your coming from DeOdexed to Odexed roms, some apps / system apps FC because of the files being built on one or the other with different type of
data being restored as well.
So something like... SecLauncher2.apk and SecLauncher2.Odex, If you went from TW DeOdexed to TW Odexed, and restored data on the apk, it'll start force
closing.
Most of the times if you are restoring system type apps, Titanium Backup would Hot Reboot, or quick reboot, at least that would happen to me.
Hopefully this info helps the least bit to trying out your ROM.
Has to be something your doing because I know first hand there isn't anything wrong with the wicked rom
Sent from my SPH-L710 using Tapatalk 2
To be my wifi because when I'm up connected to 4G damn right around town there's nothing wrong with my connection in doesn't force close I was just at a buddies house and it just kept going left n right kept force closing they would you still for a whole 10 minutes
Sent from my SPH-L710 using xda app-developers app
Not to bash any developers, but when I tried out Wicked Sensations I experienced an amalgam of bugs. Even after troubleshooting.
Sent from my SPH-L710 using xda app-developers app
Ok I switched to the new phantom blaze. And even it is restarting. I really don't know whats going on. Is there a way I can go back to straoght up sprint stock and start the whole process over? Its just becoming a headache with the constant restarts and ****.
Sent from my SPH-L710 using xda app-developers app
There is a rooted version of sprint stock rom in the android development section. Are you clearing cache/factory reset between flashes? I've flashed both those roms recently and have had no issues.
Sent from my SPH-L710 using xda app-developers app
Yeah man I do all three matter fact I'm tired of losing numbers because I'm doing the factory reset / flash and the Dalvik cache wipe. I don't understand. Is my clockwork dated?
Sent from my SPH-L710 using xda app-developers app
Good chance of it, I've used twrp since I started flashing roms. The touch interface is nice and I haven't had any issues with it. If yiu haven't tried that recovery yet that's the next step I would take.
Sent from my SPH-L710 using xda app-developers app
Look for SXTapes thread on the full AIO stock ROM ODIN-OCs.
Use the Rooted DeOdexed MD4 that resets user data. After
you've completed Odin flashing let the device auto reboot and let it
sit and optimize for 10 minutes. Power off and
pull the battery and wait 15 seconds. Put the battery back in and
turn on your device, look for an application made by chain fire called Mobile
Odin lite v3.65 on xda forums. Download and install on device and accept
root permissions. Accept extra download package content.
Now look for TWRP 2.5.0.0 tar file and download it to the root
of your internal sdcard ( preferred to find it easier )
Open up your recents s app list ( Hold home button )
Select Mobile Odin Lite. Scroll down and select Open file
then select internal SD Card. Select the twrp tar file.
Scroll down and select Flash Firmware. It should auto boot you
into Custom Recovery. If not power off device and hold volup+home+power.
Once that is all done. Nandroid ( Backup ) your stock ROM. It'll take awhile
so be patient.
Reboot device.
Transfer Wicked sensation to device.
Reboot to recovery.
Once done go to wipe > advanced wipe
Check mark the following
- Dalvik cache
- System ( Data is also wiped )
- Cache
Do this 2x times to make sure those parts are fully cleared and wiped.
Then install Wicked and have it boot up all the way. Have it sit
for 10 mins to optimize. Then reboot.
Run it like you would any other day. If it reboots on its own then reboot
to recovery wiped dalvik twice. Reboot.
If it keeps rebooting on its own again, reboot to recovery.
Restore stock nandroid.
If it keeps on rebooting when your on stock ROM then your
phone probably has an issue with flashing ROMs / being rooted.
Or just plain bad luck defective.
Sounds doable I'm gonna try this when I'm off..not having my gps on delivery
Is a pain
Sent from my SPH-L710 using xda app-developers app
Spark91 said:
Once done go to wipe > advanced wipe
Check mark the following
- Dalvik cache
- System ( Data is also wiped )
- Cache
Click to expand...
Click to collapse
Correction: Data is NOT wiped when you wipe system. You need to wipe it separately.
So @M F Money, you need to wipe system, data (dalvik is part of data partition) and cache for it to be a FULL, CLEAN wipe.
Ops thank you for that CN.
What I meant was dalvik, system, data, cache. OR factory reset ( data also wiped )
Cache, dalvik ( CWMR ). I was typing on phone at 650 am, I was tired ._.
After doing multiple data, cache, and system wipes. I can successfully say my GS3 is holding the wicked sensations v.4 awesomely. It works...thanks to all people posted in this thread. You all helped me whether I had to research terms you used and etc. Thanks for helping me learn more.
Sent from my SPH-L710 using xda premium
M F Money said:
After doing multiple data, cache, and system wipes. I can successfully say my GS3 is holding the wicked sensations v.4 awesomely. It works...thanks to all people posted in this thread. You all helped me whether I had to research terms you used and etc. Thanks for helping me learn more.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
The restarts are back...It happens when I am at home most frequently yesterday I was out on the town for about 10 good hours and not a single hard random reset. As soon a I got close to my Wi-Fi (even though I turned it off and was running 4g) it hard resets like crazy. I mean it loads..then instantly hard resets before i can even swipe my screen to open my menu. This is really annoying. and I have no Idea why it is doing this.
some of the steps Above are a little to advanced. to the point where I created another thread asking how to update CWRM 6.0.1.2 because some one said that that could be an issue. This is a step that I don't know how to do. Again any help is greatly appreciated. Like this S.O.B will charge all night and as soon as i get ready to do something to the phone it Hard Resets. none of this makes sense and it makes me want to rage on my phone lol
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!