Develop Bugs

[Q] Evo 4G Doesn't Like to Boot in New ROMs

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.

Bootloops on every restart using CM 7.2

Hello everyone,
I got me a GIO for christmas and I'm quite content with this phone, but I've had frequent reboots due to a bug in the WLAN driver (as far as I have read). So I decided to install a custom ROM and I chose CM 7.2, which works great most of the time apart from one major annoyance: every time I restart the phone (had to switch it off during exams, the phone's misbehaving, whatever reason) I'm getting into bootloops. The only solution: wipe user data, reflash, wipe user data, restore all settings, etc.
I read that these bootloops aren't uncommon, but I feel that I should be able to reboot my phone without having to set everything up again.
So my questions are: a) Is it perfectly normal what I am experiencing? b) Is there something obvious I am doing wrong? c) What could I do better? Is there a good way to backup my user data and restore it into a fresh system without having to reboot? How could I possible get rid of those bootloops? How could I help the ROMs developer to help me get rid of the bootloops?
I'd be very thankful for any directions

Hpi said:
Hello everyone,
I got me a GIO for christmas and I'm quite content with this phone, but I've had frequent reboots due to a bug in the WLAN driver (as far as I have read). So I decided to install a custom ROM and I chose CM 7.2, which works great most of the time apart from one major annoyance: every time I restart the phone (had to switch it off during exams, the phone's misbehaving, whatever reason) I'm getting into bootloops. The only solution: wipe user data, reflash, wipe user data, restore all settings, etc.
I read that these bootloops aren't uncommon, but I feel that I should be able to reboot my phone without having to set everything up again.
So my questions are: a) Is it perfectly normal what I am experiencing? b) Is there something obvious I am doing wrong? c) What could I do better? Is there a good way to backup my user data and restore it into a fresh system without having to reboot? How could I possible get rid of those bootloops? How could I help the ROMs developer to help me get rid of the bootloops?
I'd be very thankful for any directions
Click to expand...
Click to collapse
a no
use titanium backup,
then flash the rom with clockworkmod
flash gapps
wipe data cache
reboot
restore titaniumbackup you made
done
thats all
sent from my Samsung Galaxy Gio using XDA premium

Hi voetbalremco,
Thank you for your prompt reply. I have installed Titanium Backup now, for all I have read that should at least make restoring my "system" after a re-flash more bearable. The only thing I'm worrying about is that the TB wiki states that I have to reboot the phone after restoring system settings, but thanks again for the hint. I'll tell you how it worked, when (hopefully if) I run into the need of a re-flash.

Hpi said:
Hi voetbalremco,
Thank you for your prompt reply. I have installed Titanium Backup now, for all I have read that should at least make restoring my "system" after a re-flash more bearable. The only thing I'm worrying about is that the TB wiki states that I have to reboot the phone after restoring system settings, but thanks again for the hint. I'll tell you how it worked, when (hopefully if) I run into the need of a re-flash.
Click to expand...
Click to collapse
You can make a full backup if you want in CWM
Sent from my GT-S5660 using xda premium

Maybe your download was corrupt or whatever... try re-downloading the latest CM7.2.

I doubt that the download was corrupt. I have had this problem for various versions now (CM7.1RC + subsequent patches, CM7.2 + patch). But just to make sure, are the md5 sums of the original files anywhere?
Is there a way I could turn off the boot animation and get debug output on the screen so I can see what's going on when it bootloops?

[Q] SGS2 memory problems

So the other day i go put on a new rom and boot into TWRP to wipe and install. so i do my normal thing (wipe data/system/cache then install rom and gapps then wipe cache again. then reboot. i let it do its 10 min thing. then start to use the phone again. same problem as before (launcher constantly crashing) so i do my wipe and install again. this time i notice i have significantly less room on my data partition. so i go and do another wipe and install to check. this time even less space. i do it a couple more times to see if maybe it will fill up the space and then maybe completely wipe everything. no such luck. no my phone is basically useless with no way to install an OS or boot into the current one. any help on actually doing a real full wipe so that i have room again? i prepared to use odin or whatever i need to do to revert back to full stock then start all over again with the root process just to refresh my skills and get everything brand new again.
please any info would be great since id like to have a working phone again (pulled out the old iphone 4 in the mean time)
thanks guys!

Did you try a full system wipe using Infamous or Dark side to begin with? Try that first before doing anything else and see what happens.

mlbinseattle said:
Did you try a full system wipe using Infamous or Dark side to begin with? Try that first before doing anything else and see what happens.
Click to expand...
Click to collapse
ok ill try that out and let you know
update: seems to have worked have a new rom installed. hopefully it keeps running without a hitch. thank you very much. i wish i had known twrp had a crappy delete function and that it could be cast aside in favor of darkside or infamous.

olyvaha said:
ok ill try that out and let you know
update: seems to have worked have a new rom installed. hopefully it keeps running without a hitch. thank you very much. i wish i had known twrp had a crappy delete function and that it could be cast aside in favor of darkside or infamous.
Click to expand...
Click to collapse
TWRP has a Dalvik cache wipe which, IMO, is basically a factory reset. There may be more to it than I'm aware of. I'm not a dev, so I really can't say one way or another. Infamous and Darkside both have the full wipe which does everything. Anytime I flash a new ROM, I'll run Infamous followed by the TWRP wipe. Haven't had a problem, yet.
Glad it all worked out for you. I know what it's like to be in a situation like that. Been there, myself, a couple of times.

Virus???? Idk but phone is messed up

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

Looking For some Guidance

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.