Develop Bugs

Question about AOSP roms

Every non-Aosp rom I've ever flashed (Acs, bonsai, midnight, simply aosp, viper, et..) have always ended up freezing and forcing me to remove the battery to re-boot, I've followed instructions, re-downloaded the roms etc. CM7 and MIUI, both Aosp, have never had that problem, always flashed right the first time, never had to flash twice. I guess I'm just curious if anyone can explain why aosp roms work fine (minus mms, 4g, and the other aosp bugs) and every rom based off of official releases always seem to end up failing?
Sent from my Samsung-SPH-D700 using XDA App

wrong section man, this is not development (it will be moved soon).
If you are following instructions to the point in ROM guides, I have no idea. Sorry. But more specifics on your problems would help us help you

Its because most of the non aosp roms are backing up and restoring your data. If your coming from a clean flash you have to flash the rom twice before it will boot up properly.
And yes this belongs in the q&a forum
GituSum Epic 4G

GituSum said:
Its because the non aosp roms are backing up and restoring your data. If your coming from a clean flash you have to flash the rom twice before it will boot up properly.
And yes this belongs in the q&a forum
GituSum Epic 4G
Click to expand...
Click to collapse
Not to sound like an ass, but that's not entirely true. I have never had to flash non-aosp roms more than once.

djbacon06 said:
Not to sound like an ass, but that's not entirely true. I have never had to flash non-aosp roms more than once.
Click to expand...
Click to collapse
Even after an odin? Cause I've had to every time. If I'm just going between two roms I don't. Maybe my phone is just picky
GituSum Epic 4G

GituSum said:
Maybe my phone is just picky
Click to expand...
Click to collapse
I think that's it for sure. This phone literally has a mind of its own and every one is different. Just like people???
But yeah, even after clean ODIN installs it works fine first flash. Did that today as a matter of fact

djbacon06 said:
I think that's it for sure. This phone literally has a mind of its own and every one is different. Just like people???
But yeah, even after clean ODIN installs it works fine first flash. Did that today as a matter of fact
Click to expand...
Click to collapse
Then ya mine is picky. I flashed EE03 last night and used odin to go back to froyo today and had to flash twice before it booted up. No big deal just an extra couple minutes to flash and boot up
GituSum Epic 4G

GituSum said:
Then ya mine is picky. I flashed EE03 last night and used odin to go back to froyo today and had to flash twice before it booted up. No big deal just an extra couple minutes to flash and boot up
GituSum Epic 4G
Click to expand...
Click to collapse
Haha you're not the only one! On DK28 I had to flash twice everytime! And then for a little while on EB13. I don't know what changed though. But I havent had to do it for a longtime. Maybe it's because I never boot into stock before flashing?

It mainly jas to do with us having a crappy recovery.
Sent From My Evo Killer!

djbacon06 said:
I think that's it for sure. This phone literally has a mind of its own and every one is different. Just like people???
Click to expand...
Click to collapse
UH OH are you ACS guys developing AI and secretely putting it in our phones? hahaha

Even from a fresh odin, all other roms end up freezing, CM7 or MIUI I can flash over anything, and they always work, everytime.
Sent from my Samsung-SPH-D700 using XDA App

Flash srf and then vision 1.1 over it. Post in the right sub-forum.
Sent from my SPH-D700 using XDA App

Skimp Killah said:
Even from a fresh odin, all other roms end up freezing, CM7 or MIUI I can flash over anything, and they always work, everytime.
Sent from my Samsung-SPH-D700 using XDA App
Click to expand...
Click to collapse
I experience this to an extent as well.. w/ SRF 1.0.2 it flashes first time and works flawlessly..
What I've found is that all devices aren't created equal. Some work really well others are finicky.
What I've found that works for me is immediately after a flash, I can tell if it's gonna be wonky or work. After the flash, if it 'delays' before popping back up to the recovery menu, it's gonna fail. If the recovery menu pops up right away I'm good.
When it 'fails'.. I'll reboot system.. on the white samsung screen, pull the battery. boot back into recovery, then re-flash. boot system if it doesn't auto boot and you're good.
Not sure why it's like this, but it works for me. MY device doesn't always play nice w/ every version of every ROM and rather than whining in all of the ROM threads about why the rom sucks and I can't use it.. I've figured out a way to use them through troubleshooting and process of elimination using some of the 'fixes' that are posted in the different threads.
all Epics are not created equal. Just gotta figure out what works for yours.
EDIT: now that I think about it, (not that it's a big deal) I'm gonna go find noobnl's thread about checking for bad blocks on the ONEnand... just curious if journaling is trashing my NAND (I don't think it is, but ya never know)
EDIT: Still only 3 bad blocks. Nothing to worry about for me

spyder09 said:
UH OH are you ACS guys developing AI and secretely putting it in our phones? hahaha
Click to expand...
Click to collapse
LOL, I am by no means developing anything for ACS. I'm not a developer, just an advocate
And knowing how k0nane does things, there would be absolutely no trace of something like that in ACS roms

Try ec05plus its an odin tar, and it will work from the first boot...
Sent from my SPH-D700 using XDA App

GituSum said:
Its because the non aosp roms are backing up and restoring your data. If your coming from a clean flash you have to flash the rom twice before it will boot up properly.
And yes this belongs in the q&a forum
GituSum Epic 4G
Click to expand...
Click to collapse
That's not true. He mentioned Simply which I know for a fact doesn't backup/restore data.
1.) Odin back to EC05
2.) Re-root and Install CWM3
3.) Let it convert you to EXT4
4.) Upgrade to CWM 3.0.2.5
5.) Wipe data.
6.) Go to Advanced/Mounts and hit Format /system
7.) Flash the rom of your choice
8.) If it fails again wipe data x3 and then system x3 for good measure, try try again.
Hope that helps.
Pst make sure to use the proper section next time

Still not sure why this is in development.

k0nane said:
Still not sure why this is in development.
Click to expand...
Click to collapse
Won't be for long, about to pm impaler unless you already have.
Sent from my SPH-D700 using XDA App

TheDub said:
That's not true. He mentioned Simply which I know for a fact doesn't backup/restore data.
1.) Odin back to EC05
2.) Re-root and Install CWM3
3.) Let it convert you to EXT4
4.) Upgrade to CWM 3.0.2.5
5.) Wipe data.
6.) Go to Advanced/Mounts and hit Format /system
7.) Flash the rom of your choice
8.) If it fails again wipe data x3 and then system x3 for good measure, try try again.
Hope that helps.
Pst make sure to use the proper section next time
Click to expand...
Click to collapse
Iv'e tried everything listed other than upgrading to the newest CMW, I'm thinkin I'm just gonna have to wait for CM7 or MIUI to have mms and what not.
Sent from my Samsung-SPH-D700 using XDA App

Moved to Q&A.

[Q] Flash ROM & Theme before rebooting

I've had my GSII T-989 a little over a month, and it's been rooted for a couple of weeks and after reading many many posts I've finally decided on my first ROM - Tuesday Blu Ray. (I'm sure I'll be trying out many others too)! My question is; is it okay to flash the ROM and the MODs/fixes and that awesome theme 'Blu Pulsar' before my first reboot in CWR, or should I flash the ROM, let it settle for the recommended 10 minuets, then go back and flash the MODs/fixes and the theme?
I also created an update.zip of Titanium Backup; can I flash that right after flashing the ROM, or should I reboot before flashing anything else?
Thanks guys...I've spent many hours reading a lot of posts here and I'm excited to start trying out these ROM's. If not just a little anxious my first time too

I personally wait 10 minutes before I do ANYTHING else with the phone. I don't think it'll hurt it if you flash them before you boot for the first time but I wait. Just to be safe
Sent from my SGH-T989 using XDA

P.s. warfare is a beast
Sent from my SGH-T989 using XDA

hiz99 said:
I personally wait 10 minutes before I do ANYTHING else with the phone. I don't think it'll hurt it if you flash them before you boot for the first time but I wait. Just to be safe
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Flash rom, flash updates/themds and reboot, ignore the n00bs, flashing a theme for the rom replaces apps like SYSTEMUI and framework, wont cause issues and actually a good idea..
At above, why double post for that? n00b..

doug36 said:
Flash rom, flash updates/themds and reboot, ignore the n00bs, flashing a theme for the rom replaces apps like SYSTEMUI and framework, wont cause issues and actually a good idea..
At above, why double post for that? n00b..
Click to expand...
Click to collapse
He was actually right Mr.Doug
You run the risk of a bootloop if u flash a theme or u run the risk of unlimited forcecloses at boot.
Its like this.
Wipe
Flash Tom
Fix perms
Reboot and let the system settle
Then flash extras.
M&S

Master&Slave™ said:
He was actually right Mr.Doug
You run the risk of a bootloop if u flash a theme or u run the risk of unlimited forcecloses at boot.
Its like this.
Wipe
Flash Tom
Fix perms
Reboot and let the system settle
Then flash extras.
M&S
Click to expand...
Click to collapse
I hope Tom likes whatever you're flashing him.
But yeah you need the ROM to settle with the original files first. Why? Our phones are stubborn *****es.
Sent from my SGH-T989 using xda premium

Teo032 said:
But yeah you need the ROM to settle with the original files first. Why? Our phones are stubborn *****es.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
^That's funny right there lol

Thanks! That's what I needed to know. Flashing tonight after work... Can't wait now!
Sent from my SGH-T989 using Tapatalk

Weird, I usually always end up having to reflash some part of the ui when I do a new build, I've never had issues..
Only issue I got this time around (was a fresh flash via CWM and reflash updated framework and systemUI, aswell as additional stock apps I forgot to put into build. Such as keis and a few others..) is simply my screencaptureservice.apk didnt compile right, and only mod I did was changing directory, which I've done before xD never had issues just flashin an update after installing

doug36 said:
Flash rom, flash updates/themds and reboot, ignore the n00bs, flashing a theme for the rom replaces apps like SYSTEMUI and framework, wont cause issues and actually a good idea..
At above, why double post for that? n00b..
Click to expand...
Click to collapse
Yeah solo...you're the noob
Sent from my SGH-T989 using XDA

doug36 said:
Weird, I usually always end up having to reflash some part of the ui when I do a new build, I've never had issues..
Only issue I got this time around (was a fresh flash via CWM and reflash updated framework and systemUI, aswell as additional stock apps I forgot to put into build. Such as keis and a few others..) is simply my screencaptureservice.apk didnt compile right, and only mod I did was changing directory, which I've done before xD never had issues just flashin an update after installing
Click to expand...
Click to collapse
yeah there are times when something breaks or it just goes into bootloop, especially if the ROM is using a different launcher or something.
one time I was missing my status bar lol. It doesn't happen much on this device, but it did once. However, it happens a lot in other devices.

removal of moderated material
Your method of flashing may work but its not the ideal way. If you flash a new rom that way and have issues you will not be able to figure out the root cause. Also its not a good idea to keep calling some one a noob for a simple reply of what they suggest. If I see it again from you, you will be reported. Its this kind of attitude that's bringing down a community that's supposed to be helpful and respectful to everyone new or not.
Even though he called you one back the point is you started it.

[Q] Paranoid Android ROM Help!

Hello all. I wish I could post this in the actual thread, but I am a new user with less than 10 posts haha! But I am having an issue with Paranoid Android ROM booting. I have tried like every way imaginable. Here is the logcat form my phone: h t t p :// pastebin.com/mukxdDDM. So does anyone have any sort of idea as to what is goin on? I'm starting to learn my way around Android code and I still don't have much of a clue. Thanks for your help!

Flash cm9 sign in the works.. I then wipe everything format system and flash are u on mtd or what?
Sent from my SPH-D700 using xda premium

I'm having the same problem, friend.

I am. I have been on cm9 for a long time. I tried flashing cm9 clean first and flashing PA but to no avail.

I had this problem when I tried restoring to the paranoid. I fixed it by clean installing aokp with nyan v5, then clean installing paranoid and Google apps nothing else in twrp recovery and it booted. It should work in cwm also but I have not used cwm for a while because twrp is easier although a bit buggier.

My recommendation would be odin back to stock and then odin cwm and flash

I got it to boot once, but it was missing the notification bar. I redownloaded it, but now it gets stuck at the boot animation, and the phone gets warm to the touch.
Edit: Tried CM9 first twice after fully wiping. I hope to get this working, because it looked pretty cool...

WBaumgartner said:
I got it to boot once, but it was missing the notification bar. I redownloaded it, but now it gets stuck at the boot animation, and the phone gets warm to the touch.
Edit: Tried CM9 first twice after fully wiping. I hope to get this working, because it looked pretty cool...
Click to expand...
Click to collapse
Not sure why there are so many problems just to get it to boot. If one way works for the majority of people, shouldn't it work for everyone if the steps are followed exactly?
Sent from my SPH-D700 using xda app-developers app

Nope...too many variables. Every phone is different, bad downloads, bad flashes. If everyone Odin'd to FC09 stock then rooted with cwm 5.0.2.7 then flashed CM9 98% would be fine but still 2% would have trouble.
Sent from my SPH-D700 using xda premium

Ah ok. Thats a bit disappointing haha.
Sent from my SPH-D700 using xda app-developers app

Just in case anyone stumbles upon this thread, the booting issue for this ROM has been solved by the ROM porter. Anything passed the June 30 build has this issue resolved.

Also, anyone willing to help me with another issue? Or should I start a new thread? I want to post all these in the main thread, but I can't for 5 more posts. My issue is that I can get this whole ROM running, but I have no statusbar at all. I am not sure why. Can anyone be of assistance?

JustKojack said:
Also, anyone willing to help me with another issue? Or should I start a new thread? I want to post all these in the main thread, but I can't for 5 more posts. My issue is that I can get this whole ROM running, but I have no statusbar at all. I am not sure why. Can anyone be of assistance?
Click to expand...
Click to collapse
Just keep posting here and you'll have the post you'll need
Sent from my SPH-D700 using XDA Premium App

Thanks! But I have no statusbar while running the Paranoid Android ROM. And I'm not really sure why. Any help?

JustKojack said:
Thanks! But I have no statusbar while running the Paranoid Android ROM. And I'm not really sure why. Any help?
Click to expand...
Click to collapse
Which one of the updates did you flash? Most likely you got a bad download.
Sent from my SPH-D700 using XDA Premium App

masaidjet said:
Which one of the updates did you flash? Most likely you got a bad download.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
I got the June 30 download. I now flashed cm9 and then PA and I have statusbar. Not sure why.

JustKojack said:
I got the June 30 download. I now flashed cm9 and then PA and I have statusbar. Not sure why.
Click to expand...
Click to collapse
Did you do a clean wipe ? Sometimes when wipes aren't performed things like no statusbar happen. And until the dev work out the kinks I would stay away from the rom. I really like Paranoid Android myself
sent via brain

masaidjet said:
Did you do a clean wipe ? Sometimes when wipes aren't performed things like no statusbar happen. And until the dev work out the kinks I would stay away from the rom. I really like Paranoid Android myself
sent via brain
Click to expand...
Click to collapse
I just did a full wipe, installed june 30th build and no status bar for me either, I will try installing over cm9 and see what happends.

Jshugzda said:
I just did a full wipe, installed june 30th build and no status bar for me either, I will try installing over cm9 and see what happends.
Click to expand...
Click to collapse
The way I did it was full wipe including wiping /system, then I installed cm9 and correct gapps, then did not install any extra apps, then installed PA and correct gapps, and all went well!

masaidjet said:
Did you do a clean wipe ? Sometimes when wipes aren't performed things like no statusbar happen. And until the dev work out the kinks I would stay away from the rom. I really like Paranoid Android myself
sent via brain
Click to expand...
Click to collapse
I did and full wipe and no statusbar, but then i did cm9 and it worked! haha! I am loving PA though! And once you get it to be a stable booting rom it so far is working well.

[Q] Anything other than a TW and my camera just wont work, Help?

Hi there!
I have had an s3 for a few days now and love it!.
Any TW rom and my camera works just fantastic.
Any cm10/aokp/miui/etc rom and I just cant use the camera no matter what app I use to try it, whether it be the built in app or camera360/etc.
Driving me nuts and would love someone to help me. Anyway research I have done hasnt told me what I'm doing wrong.
I wipe cache/dalvik/factory reset/system before each rom. I have tried different kernels but nothing has helped.
Any gurus out there have any ideas on what I can do to fix this?

Your install process would be and please link the files you are flashing... I'll try and help you. I've seen a few people mention this the past couple days.

The most recent I tried to flash was Illusion v1.1.18 - (d2tmo, d2att & d2vzw) - 1|18|13 from this thread:
http://forum.xda-developers.com/showthread.php?t=2037028
I downloaded Illusion-v1.1.18-d2tmo.zip and gapps-jb-20121212-signed.zip.
I went into recovery which is twrp and the most recent version. I installed it with the goo.im app.
When in recovery I did:
1) Factory Wipe
2) Wipe Cache
3) Wipe Dalvik
4) Wipe System
I would then click Install and select the rom file, and after it succesfully flashed I would then flash the gapps file. All were successful.
I would then reboot and the rom would boot up fine. I setup my google account and all that then for the heck of it I would reboot.
I then would try the camera app and it would complain that it couldnt connect to the camera basically. I went into the play store and tried a free version of camera 360, puddle camera, etc and all would not work.
I went back into recovery, wiped cache and dalvik again, hopped on one foot, faced east, and clicked my heels together. Upon reboot the camera does not work.
I have wiped all that and tried to install [Kernel][JB] Leankernel: Minimalistic Kernel for D2TMO/D2ATT (AOSP) v2.3 [1/17/13] which flashed fine. Upon reboot I could change voltages to undervolt, mess with governors but cameras still do not work.
I have a backup of two TW roms (one stock) and both of the those roms work beautifully with whatever camera I try, including the built in/stock camera.
I hoped I didn't leave out something. If there is something I missed than I'm an idiot because it seems like I am really missing something.
Thanks for your help.

I don't see any reason your steps lead to that, the exact steps I take every time to flash. I'm researching but in the mean time, go to app manager and wipe cache and data from gallery... Are you using the same Gapps over and over on each try? Might wanna try a different set.

mt3g said:
I don't see any reason your steps lead to that, the exact steps I take every time to flash. I'm researching but in the mean time, go to app manager and wipe cache and data from gallery.
Click to expand...
Click to collapse
I did that earlier with no luck.
I just force stopped on gallery, wiped cache/data, rebooted, and I tried the camera only to get the same message.
Thank you for that tip but I will continue my research also.
Just because I looked at about phone.
Model of phone is SGH-T999 (just in case someone thinks I'm in the wrong forum"
Baseband version is T999UVDLJA
Kernel is of course 3.0.59-leanKernel
AOKP Version is Illusion v1.1.18 d2tmo
Build number is aokp-d2tmo-userdebug 4.2.1 (I truncated the rest)

mt3g said:
Are you using the same Gapps over and over on each try? Might wanna try a different set.
Click to expand...
Click to collapse
I have downloaded this gapps twice for the last rom http://goo.im/devs/itsmikeramsay/gapps-jb-20121212-signed.zip.
For the miui rom there was a gapps that was specific to miui and had miui in the name. The miui rom's camera didnt work.
I'll look for a different gapps if that might be the problem but since I have tried a couple roms and a few different gapps I feel that might not be the issue.
I still will give it another try though. Just have to find another gapps to try.

try these just in case they're corrupted. http://d-h.st/dtk these are the ones I use

mt3g said:
try these just in case they're corrupted. http://d-h.st/dtk these are the ones I use
Click to expand...
Click to collapse
I redid the entire install process from scratch using that gapps and the camera is still not working.
Ugh. Thanks for the link.
WIll keep trying :/

run a log cat and post it. Other then that maybe bad firmware...
did you update your phone to stock JellyBean via Over the Air or Odin? it updates the partitions which could be the issue, mmayyybbeee???!?!? Shots in the dark right now, just trying to help as I've never seen this issue before solved.

mt3g said:
run a log cat and post it. Other then that maybe bad firmware...
did you update your phone to stock JellyBean via Over the Air or Odin? it updates the partitions which could be the issue, mmayyybbeee???!?!?
Click to expand...
Click to collapse
It had JB on it when I got it almost 2 days ago. I tried to do an OTA when I got it but it said I was up to date.
Let me do a restore to stock and see what version it is.
Edit: Restored stock. Says android version 4.1.1, Kernel 3.0.31-370274se.infra, Build number JR003L.T999UVDLJA

Was it already rooted?
Sent from my SGH-T999 using xda premium

mt3g said:
Was it already rooted?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
It was new, out of the box. I watched the guy unrap it. It is one of the newer grey metal color looking ones. It was not rooted. I did that. Should I do an Odin to bring the device back to complete stock and start from scratch?
Will take a while since I have no idea where to start with all that

Thats the best suggestion I have. Maybe someone else will step in with an idea.
Sent from my SGH-T999 using xda premium

mt3g said:
Thats the best suggestion I have. Maybe someone else will step in with an idea.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
You have been helpful. In a bit ill reflash a cm/aokp rom and logcat it.

This is happening a couple of threads above you haha http://forum.xda-developers.com/showthread.php?p=36899130
Sent from my SGH-T999 using xda premium

mt3g said:
This is happening a couple of threads above you haha http://forum.xda-developers.com/showthread.php?p=36899130
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Hey thanks again for your help. I ended up falling asleep but installed Wicked V6 (tw based rom) and liking it enough that I will wait on a aokp/cm10.x rom until I get up the motivation to try again.
I'm sure I'll get an itch for a different rom in about a week though

dccoh said:
Hey thanks again for your help. I ended up falling asleep but installed Wicked V6 (tw based rom) and liking it enough that I will wait on a aokp/cm10.x rom until I get up the motivation to try again.
I'm sure I'll get an itch for a different rom in about a week though
Click to expand...
Click to collapse
All good, just hope the thread I pointed to will work out once you do want to give it another go.
Sent from my SGH-T999 using xda premium

mt3g said:
All good, just hope the thread I pointed to will work out once you do want to give it another go.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I backed up Wicked and loaded up my original rom that I wanted to try.
The fix in the said thread fixed me right up, camera works fine.
All this trouble because of one 350ish kb file
Thanks for checking on my issue.

dccoh said:
I backed up Wicked and loaded up my original rom that I wanted to try.
The fix in the said thread fixed me right up, camera works fine.
All this trouble because of one 350ish kb file
Thanks for checking on my issue.
Click to expand...
Click to collapse
Most definitely sir. I don't understand why that file was getting screwed over. Glad it all got worked out for you.
Sent from my SGH-T999 using xda premium

Can't get past the boot animation when flashing aosp roms

So I've done the whole rom flashing thing a bunch. Hd2, infuse, note 2, mytouch and I've never had this happen.
I can flash any tw rom I want amd no problems at all. But no matter what aosp or non tw rom, I can never pass the bootanimation.
I've tried PA, carbon, liquid, and beanstalk. All of them with gaps and without gaps, Tried multiple downloads of each.
Let the boot animation run for 15 minutes. I did download straight to my phone as I don't have access to a computer.
To be honest I was just wanting to play around with 4.2.2 but when I couldn't get it to run it pissed me off and now I'm on a mission.
Don't know what else to try and amy help would be appreciated.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

What steps are you taking when trying to flash. I have never had that problem and have flashed all of the aosp Roms and have also gone back and forth between them and tw roms
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

csandman1977 said:
So I've done the whole rom flashing thing a bunch. Hd2, infuse, note 2, mytouch and I've never had this happen.
I can flash any tw rom I want amd no problems at all. But no matter what aosp or non tw rom, I can never pass the bootanimation.
I've tried PA, carbon, liquid, and beanstalk. All of them with gaps and without gaps, Tried multiple downloads of each.
Let the boot animation run for 15 minutes. I did download straight to my phone as I don't have access to a computer.
To be honest I was just wanting to play around with 4.2.2 but when I couldn't get it to run it pissed me off and now I'm on a mission.
Don't know what else to try and amy help would be appreciated.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Please provide more information so we can better help you as the post above said. I've not had a problem switching back and forth either.
Sent from my CLEAN Note ll

brandonarev said:
Please provide more information so we can better help you as the post above said. I've not had a problem switching back and forth either.
Sent from my CLEAN Note ll
Click to expand...
Click to collapse
I download the roms and the gaps. Boot into twrp and do all my wipes 3 times. System, dalvik, cache. Install rom. Install gaps. Reboot.
I've tried without the gaps. I've wiped dalvik after that also like some roms suggest.
I chalked it up to bad download at first but all of them? I may try again with a different browser.
Tried boat browser and Firefox. Both hang at boot animation
I'm on cleanrom 4.7 now. Glad I made a backup!
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

I figured it out. I had grabbed the new beanstalk build before it was pulled. For some reason when I tried to flash it, it added a seperate folder in my internal sdcard and moved every file into it. For some reason trying to flash from that new folder wouldn't work. Twrp wouldn't see anything in the old folder.
I moved the ROM and gapps to the external card and everything flashed perfectly.
Weird.
Sent from my GT-N7105 using xda app-developers app

That hidden folder is a legacy folder. .
It's placed as a safeguard during the flash process. ..in the event that data/media...or other important files get deleted. .
The TWRP recovery will prevent deletion of the media files. ..but CWM does not. .
You can still delete your EFS and other critical partitions with TWRP..but they warn you first where CWM does not. .
The legacy folder can be used to restore deleted data later if a problem occurs. ..And should be left there when using roms with modified file structures like CM....g

Thank you for the info. Was just weird that I can't flash from that folder anymore.
Sent from my GT-N7105 using xda app-developers app