Develop Bugs

no app2sd partition found (no help from search)

Hey all, so I've searched the "no app2sd partition found" topic and it seemed to be pretty popular. However, my situation is different than from what I have read thus far. Please read what I have to say instead of ignoring my post and assuming that my situation is the same as everyone else's and give me some stupid useless post like "google is your friend."
Here is my situation:
Normally running Baked Snack's ROM perfectly fine. I decided to try the miui ROM the other day and didn't like it too much so I went back to the ROM I've been using for the past few months, being Baked Snack's. That went perfectly fine. But then, today I tried the miui rom again just to show off to some friends. Day is over so I decide to go back to what I've been using. Now here's the problem, I wiped data, cache, dalvik the usual, but this time after I rebooted the phone, it went the the white HTC load screen and then it went back to the recovery. Now it keeps doing that. I've wiped data/cache/dalvik multiple times and I made sure of it. Upon wiping my data, I noticed that it said "No app2sd partition found. Skipping format of /sd-ext."
I've searched this topic but still unsure of what to do because my situation is different, I've already done this before multiple times and now it's not working. I would very much appreciate any help.

Seems you went from a non Darktremor A2sd rom to a darktremor a2sd compatible rom or vice versa.
Search on his a2sd thread and you'll learn all about it.

Thanks for the reply. I'm not too sure how that could have happened, though. I've done this before with the same exact ROM and had no problem getting my nand back up.
I don't exactly have all the time in the world to read through countless pages to try to figure what's wrong, especially when I have basically no idea what's going on. So if someone could help me out, it would be great

Try asking at wwwdotbakedsnackshackdotcom. If you went from an aps2sd rom to a non-aps2sd, then search trevor's post on how to use terminal emulator to empty the apps2sd partition back into the phone memory prior to loading the non-app2sd rom.
edit: I do think that is a standard recovery message, that it couldn't find an ext partition. You might try wiping twice then rolling back in the rom you want.

[Q] ROM/Theme/Mod Flashing Issues

I was wondering if anyone could help me out please. I've tried searching the forums, but I haven't been able to find my exact issue. Basically, I feel as if my phone seems to have increasing issues with flashing through Clockwork Recovery; here's the details:
I originally rooted my phone using the Odin flash method. I flashed the Juggernaut available at the time, wiping data/factory, cache, dalvik, and battery stats through clockwork first, and letting it chill for 15 minutes with the first boot. I follow the same steps each time I flash another rom ( I've read that I should also wipe /system, but Juggernaut seems to do that itself, so I haven't ). A month and a half ago, I wanted to add a few things, so I wiped, then flashed the latest Juggernaut, rebooted, let it settle,and then flashed the ICS Ultimate Theme, no wipe, then after another settle, flashed the Pdroid zip ( no wipe ) I made with the v1.27 auto-patcher. Everything seemed to work flawlessly for a month or so, then I started having issues that just kept getting worse: phone freezing while installing market apps then unfreezing, camera lagging, random freeze & reboots, etc. I tried fix permissions, and no luck. I wiped and tried reflashing everything the way I had, and the phone kept freezing after the faux kernel loading screen. Installing Juggernaut or another rom by itself, or a nandroid restore, is the only thing that got it past boot. Not even themes flashed over roms that they're made for get past boot. I restored my phone to stock using this method, wiped both SD cards, and re-rooted then flashed Juggernaut again, but this time I used clockwork's wipes and darkside's super wipe before flashing, but I still can't flash anything but the rom itself without a boot loop, even with fix permissions. I had a similar issue on my old mytouch Espresso; consecutive flashes seemed to almost eat away at my phone and make things worse, but that phone also had hardware issues. I'm using a new MicroSD since then. Also, if it means anything, I tried flashing the new clockwork touch from the zip on these forums after these issues started, and it never took, however, flashing through Rom Manager's after I purchased it worked fine.
Sorry about the long post, but I wanted to detail everything I've tried that I could think of before bothering anyone here. Does anyone know what could be the issue? I would really appreciate some help, because this issue is really frustrating, and I have no idea what's causing it.

Could someone help me with this please? I can try and get a log cat if needed. I'm just really hoping to get to the bottom of these issues.

I will be glad to help you out!
One big problem I see is that your not using Darkside Superwipe before flashing new roms.
So I would highly recommend you flash Darkside Superwipe first (clears all cache, partitions, ect very very thorughly) Better option than manually clearing cache and all that in clockwork mod.
Try Darkside Superwipe install the rom and see if you get any problems.
Here's how to use it if you dont know how to:

techfanatic9 said:
I will be glad to help you out!
One big problem I see is that your not using Darkside Superwipe before flashing new roms.
So I would highly recommend you flash Darkside Superwipe first (clears all cache, partitions, ect very very thorughly) Better option than manually clearing cache and all that in clockwork mod.
Try Darkside Superwipe install the rom and see if you get any problems.
Here's how to use it if you dont know how to:
Click to expand...
Click to collapse
I'd like to point out that he does in fact use tdjs super wipe.
OP: have you tried other ROMs or kernels. In my past experiences, faux kernel did not meet my expectations so I moved along to another one. Give my configuration a go (refer to my signature) and let me know of the problem persists
Sent from my Galaxy Nexus using Tapatalk 2

Thanks for the replies!
techfanatic9 - I originally just wiped through clockwork ( before darkside superwipe was standard ), but now I use that too, and I'm still having those issues. I watched through the entire video just in case, and I'm doing it just like they say to.
iLeopard - I have tried Digital Warfare, but I still have the same issue when flashing things over it ( ICS Theme and/or PDroid ), even if it's supposed to be compatible, though I haven't tried kernels yet. I'll give your sig's setup a try and report back.
Meanwhile, could anything else be the issue? As you can probably tell, I've tried almost every mistake I could think of, and since my last phone had the same issue, a similar hardware issue seems unlikely.

All right, I've been running that ROM and kernel combo for a few days now. I don't seem to have any issues when I just flash the ROM and kernel, but I get stuck at the boot screen if I try to flash something else on top of it. Also, when I try to restore my text message backups through Gosms ( around 9800 texts that I want to keep ), the phone freezes halfway through the restore, and from that point on, the phone will freeze 5-10 minutes after rebooting, unless I reflash. I make sure I don't have the phone running and I leave it alone while restoring, and it doesn't help. I've only had this gosms issue since my flashing issue, and sometimes it restores fine.
Does anyone know what could be causing that?

[Q] Problems with flashing roms

So I have had my phone since October. I've gone through at least 20 roms from then till now. I was using the MOAR rom and it was sketchy at times in a sense of the launcher shutting down for no reason. data connectivity wasn't always the greatest even though its suppose to be good. I decided to go back to using the darthstalkers rom. did a full wipe. formated the system like it said to do if i was still using clock work. then flashed it like i normally do. then i have the recovery tell me that it could not load up the rom and aborted the installation. thought it was a glitch. so i tried to redo the moar rom. same thing. then i downloaded 3 more roms and uploaded them to my sd card. tried all of them. still the same end result. i bricked my phone in the process and went back to stock and rerooted. even after i rerooted, i still have the same problem. any ideas?

turboed dragon said:
So I have had my phone since October. I've gone through at least 20 roms from then till now. I was using the MOAR rom and it was sketchy at times in a sense of the launcher shutting down for no reason. data connectivity wasn't always the greatest even though its suppose to be good. I decided to go back to using the darthstalkers rom. did a full wipe. formated the system like it said to do if i was still using clock work. then flashed it like i normally do. then i have the recovery tell me that it could not load up the rom and aborted the installation. thought it was a glitch. so i tried to redo the moar rom. same thing. then i downloaded 3 more roms and uploaded them to my sd card. tried all of them. still the same end result. i bricked my phone in the process and went back to stock and rerooted. even after i rerooted, i still have the same problem. any ideas?
Click to expand...
Click to collapse
You didn't brick your phone first of all. What are you downloading the ROMs on and how are you transferring them. After you wipe data you wipe the cache and dalvick too, right? You didn't mention that part in your statement. You might want to try Twrp recovery if you haven't. Also it could be your sd card if that's where you are putting the ROMs and they constantly are failing. Also I have been running MOAR with none of the issues you described. As far as signal that would probably be Sprint or your modem or prl etc. Not the ROM.
Sent from my SPH-L710 using Tapatalk 2

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

kenny - sorry about that. thanks for moving it for me.
giantjay - my bad. semi bricked. i could not get it to load the original moar rom.
I did a full wipe. system, data, cache, and dalvick.
I have been having alot of problems flashing twrp on my phone. its been like that since i have had my phone. it was alot easier when i had my evo.
I download roms directly to my phone. the files i have are on the internal card. not to sure why it will be failing from there in the 1st place.

Storage issues help

I'm suddenly having storage issues with every ROM that I flash after running a ROM with some script that isn't widely used.
First I'll give you a brief idea of my problem. I"m running out of storage and get notifications from the market saying as much after I download and reasonable amount of apps. The thing is... It show's I have used 738MB of ext4 out of 1.5 so that isn't the issue. The problem is internal memory. My phone won't move dalvik cache for some reason. When I run any ROM with a2sd or m2sd they both say that there is a problem and leave the dalvik cache where it is.
I think my internal folders are jacked up from 40ad2sdx or a zip that was used to clear memory before the ROM. There was a ext4 superwipe cleaner to load before the ROM. I did that without researching first. When I did go looking for the thread about it, it plainly said that it was for one phone only, and it wasn't my phone. I believe it was the Galaxy S3, but I can't be certain. It was a week ago. It was advised not to use it on any other phone because part of what it did was reset the internal folders. Does this mean I can now flash a ROM for the galaxy s3? Lol Just kidding.... Seriously, the second part is all my speculation and I have been wrong many times concerning android. Will somebody help me get my phone back in oem condition please?

Okay, I'm not even sure what you did here, because not knowing the script, anything could have happened.
Try wiping everything and flashing stock rooted here, then go from there with other roms after that.
If that doesn't work. Here's what I would do. It might be a major pain, but it is almost a surefire fix.
Unroot and return to stock, then root again.
[UNROOT]
[ROOT]
For future reference, NEVER flash anything that is meant for another device. (Obviously, if it's a port then you're ok.)
ALSO EXTREMELY IMPORTANT: Backup your SD card, and wipe that puppy clean!! Only partition using Amon-RA recovery, otherwise it will screw you up quite often. I repeat, if you do not have the partition done correctly, then odds are that A2SD or equivalent won't work.

nate234 said:
Okay, I'm not even sure what you did here, because not knowing the script, anything could have happened.
Try wiping everything and flashing stock rooted here, then go from there with other roms after that.
If that doesn't work. Here's what I would do. It might be a major pain, but it is almost a surefire fix.
Unroot and return to stock, then root again.
[UNROOT]
[ROOT]
For future reference, NEVER flash anything that is meant for another device. (Obviously, if it's a port then you're ok.)
ALSO EXTREMELY IMPORTANT: Backup your SD card, and wipe that puppy clean!! Only partition using Amon-RA recovery, otherwise it will screw you up quite often. I repeat, if you do not have the partition done correctly, then odds are that A2SD or equivalent won't work.
Click to expand...
Click to collapse
I did the wipe and flash to stock earlier today, then flashed the Pac man ROM but the issue is still there. I had looked at unrooting my phone earlier today also. I'm glad to read this because it lets me know that I do have some idea of what to do. Thanks for the reply. I'll post here again with the results. Check back soon.
EDIT----> Man, my phone is okay. I loaded up a fairly recent ROM by Tronit, and it worked fine. It was the ROMs. Just to be sure, I went back to the last two ROMs just to see, and they did the same thing again. Now I'm on the AOKP Unnoffical and it's working just fine. The a2sd is working perfectly like it should, and my dalvik cache is moving to ext4. It was just coincidental that the last three ROM's I loaded all have issue with the a2sd. It's funny how nobody else see's problems but me. I looked in the bin file of one of them and it's missing part of the a2sd file. The other two have weird init.d files that I don't know anything about. I'm assuming the a2sd problem is related to that. It's funny how I see lots of problems, and report them, but I get blown off by some people as a noob who is making mistakes. I am a noob, and I do make mistakes, but I know some of my theories about problems are correct...... I gotta get me some respect by compiling my own ROMs.

Status update..... My phone is jacked up for sure. It does work with the AOKP Unofficial by Tronit, but this morning when I cleared my cache with Smelkus Recovery, it had major problems with almost every app. Clearing the cache in recovery is something I've done with every ROM and this has never happened. I uninstalled all the apps and reinstalled them. Got them working again. Everything seemed to be okay. However, when I cleared my cache with Android Tuner, again it ruined every app. I've used android tuner every day for two months to clear the cache and never had problems like this. Something is very wrong.
*****edited and deleted for the sake of peace*****
Long story short, I flashed something made for another phone. I can't explain why I did this without taking up lots of pages, and it doesn't even matter really. Lets just focus on the solution. Here is the link. I flashed both of the zips in the link.
http://forum.xda-developers.com/showthread.php?t=1477955
So I think my permissions for the files on my phone are out of whack. Is that what I"m reading is the possible outcome of flashing these if your phone is not the one listed? Please post your thoughts. I need them.

Try backing up your SD card on a computer and format you SD card and repartion it
Sent from my PC36100 using Tapatalk 2

g2435 said:
Try backing up your SD card on a computer and format you SD card and repartion it
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
I did that. Both with Smelkus, and Mini partition wizard. Same problems. I just tried to fix permissions with smelkus 4.3 on the AOKP Unofficial ROM and it took a minute for it to do it's thing. The line of dots was two full rows. So when It loaded back up, I suddenly see the same disk Icon in my notification bar, and now this ROM says it it out of memory. Man, it was working fine. I had twenty more apps on it too and I uninstalled them. It was working fine then, so with twenty less apps, it shouldn't suddenly say "Running out of Storage space."

I have told you this already: Please do not flash things meant for other phones, it could mess up. If it's meant for another device, it might screw yours up. To stay on the safe side: If it's not generic (works for every Android phone) or phone specific (exclusive to the Evo 4G) then don't flash it.

nate234 said:
I have told you this already: Please do not flash things meant for other phones, it could mess up. If it's meant for another device, it might screw yours up. To stay on the safe side: If it's not generic (works for every Android phone) or phone specific (exclusive to the Evo 4G) then don't flash it.
Click to expand...
Click to collapse
I flashed this about a eek ago, when I was looking for the ext4 wipe. I thought it was the same thing as another zip despite what it said. Stupid... I know. I think this may be the cause of my problems, but I can't be sure. I don't know at all really. Just speculations. I reflashed the CWM touch and used to flash a stock ROM. Gonna try that again. I ran the test on CWM touch and it said that the
/sys/class/android_usb/android0 was missing and unable to perform the test. Can this be the cause of my problems?

Don't beat yourself up man, it was an honest mistake, just learn from it and you'll be alright.
Now the optimal recovery for this device would be the Amon-RA recovery, and I recommend redoing what I said in my first post once you have Amon-RA installed. Amon-RA is an awesome recovery, and it's super easy to install. Check out this easy-to-follow video on how to install by clicking here.
Do that, then do what I said in the previous posts. Let me know what happens, because I'm almost certain this should work.

nate234 said:
Don't beat yourself up man, it was an honest mistake, just learn from it and you'll be alright.
Now the optimal recovery for this device would be the Amon-RA recovery, and I recommend redoing what I said in my first post once you have Amon-RA installed. Amon-RA is an awesome recovery, and it's super easy to install. Check out this easy-to-follow video on how to install by clicking here.
Do that, then do what I said in the previous posts. Let me know what happens, because I'm almost certain this should work.
Click to expand...
Click to collapse
I tried loading the Pacman ROM again with CWM and it wouldn't even load. It gets stuck in a bootloop. After that I flashed smelkus and went back to the Stock Rom.
*****edited and deleted for the sake of peace****

RADIO EDIT------
Sent from my PG86100 using xda app-developers app

edited and deleted for the sake of peace

As I stated in my pm give me a day or so till I get back home and I will check into a fix for you. Only don't expect any one on one help. If the fix works cool if not I will dig further. TNN strives to help with any issue no matter who is at fault. I will look at the wipe script you flashed and see if it can be undone. Just be prepared of the possibility that your phone may never work correctly again.
Sent from my PG86100 using xda app-developers app

I was finally able to get my phone straightened out. I loaded up a stock ROM then decided to use my SD Maid to look around. I found a file with completely different dates on it, but it wouldn't let me remove it. I ended up copying everything else in the subfolder and then deleted the parent folder. Then added everything else back. Wah lah.... magic. I don't know what that file was or where it came from but it was killing my internal memory. I'm wondering how it stayed from ROM to ROM. I dunno, but it's gone, and the Pacman ROM is lovely now. BOOM!!!!

jlmancuso said:
As I stated in my pm give me a day or so till I get back home and I will check into a fix for you. Only don't expect any one on one help. If the fix works cool if not I will dig further. TNN strives to help with any issue no matter who is at fault. I will look at the wipe script you flashed and see if it can be undone. Just be prepared of the possibility that your phone may never work correctly again.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Whatever I did only fixed part of the issue. I'm left with in a situation where every time I go into recovery my downloaded apps stop working. It is cutting part of them off whether I clear cache or not. All I have to do is power off into recovery, and when I reboot, all of my downloaded apps begin giving messages that "Unfortuately such ans such has stopped." My phone becomes inoperable. The only way I can keep it working is to send a new launcher to my phone from the market, let it install, then open it up and uninstall all the downloaded apps. I'm pretty sure this is an easy fix for someone like you Mancuso. I have a logcat and it show LOTS of errors that I have never seen before on any of my other logcats. What are my options? Tell me what to do to get my phone back to absolute OEM and then I'll reroot. UNLESS you know of some fix.
I've supplied a logcat from Catlog if you or anybody else wants to have a look. I'd really appreciate some help here. I love my Evo and I love learning this stuff. If somebody can help me positively identify the problem, I can most likely figure it out from there. Please give me your suggestions here. I'm nothing without some guidance on this. It's way out of my scope.
I've included a link to the ext4 script wipe that I used. How I got to this page, I do not know. However, I ran it because this page said it COULD POSSIBLY work on other phones despite the fact that it was made for another phone.
http://www.xda-developers.com/android/darkside-super-wipe-easily-wipe-partitions-when-flashing-roms/
And I flashed both zips from the thread that the story links users to. Here is the link for the two zips.
http://forum.xda-developers.com/showthread.php?t=1477955
I'm not sure this is the problem. I'll try to find the Vold.fstat thread that I tried on my own before you came up with the 40ad2sdx solution for the MIUI ROM.
This is the memory fix I tried as mentioned above.
http://forum.xda-developers.com/showthread.php?t=2246909
Please note that you see before and after pics of sd storage. You can see that my pics clearly resemble the after pics shown in this thread. I believe this is my problem. How can I undo this?
This post reflects the only things I did outside of normal flashing. My problem is here somewhere...

The fix you used is for samsung devices. That could have caused your problems.

[Q] Reboot problem, but a little different

Okay, so I have been a flashaholic for the past couple of years and been on the AOKP nightlies for a very long time.
However, since the last month or so, every time I try to flash (clean and dirty) a new ROM or upgrade to a newer nightly, the flashing process goes on pretty smooth as expected. But, here is the thing.... after booting up fine, it starts to optimize the apps and I see it going through the entire cycle of apps. When all the apps are optimized, it says "Starting apps" and this is when I feel a vibrate and the phone reboots and does this over and over. My only way out of this is to boot it back into Recovery (TWRP 2.5) and restore my backup and sadly continue using what I had before this exercise.
I have tried various combinations of wipes, fix permissions, kernels, radios, etc. and am totally stumped here!!
Help please as it bugs me to no end when I see crazy new features the newer ROMs are dishing out and I cannot taste them

by clean what are your actual steps you mind elaborating a bit more of your steps, and with which ROM this happens on have you tried a stable as oppose to a nightly to see if it will fix your errors, as far as flashing do you ever format system in mounts and storage when you flash ROMs ???

Clean: Wipe Cache, Dalvik, Format System, Data. I haven't tried formatting the Internal SD or Preload partitions yet.
This happens with quite a few ROMs... I have tried SlimBean, CM 10.1, AOKP M2, PA so far. See the same behavior on nightlies or stables. I haven't tried Stock ROM yet... maybe should give that a try as well.
Let me know if I can give you more information to help me out.

since it seems to be happening on every ROM for you i would suggest you try going back to stock and re-root and try again, it doesn't take that long it just really sucks to do everything from scratch, but its the only way you are going to know where this problem is coming from also if you are on TWRP 6 that might be the problem everyone has been having lately it sometimes works sometimes doesn't have you tried opening ROM MANAGER and fixing permissions only from within the app...see if that squashes your bugs just trying to give some ideas ....

I would hate to go back to stock and re-root all over again. But if all else fails... I guess that remains as my only option.
I am on TWRP 2.5 for quite some time now and have successfully flashed using that numerous times before this problem started... not sure what you mean by TWRP 6 (you mean 2.6?)
I do not have ROM Manager on my phone, will give that a shot as well before resorting to the "Stock" option.
Thanks for your help!

yeah i ment 2.6 lol DOOHH!! and yeah you def sound like you know what you are doing so im sure you will figure it out just wanted to give you some ideas ... and for the record its always nice to take a break but good luck bro sorry i couldn't help you more

It was an issue with the Kernel I guess!!
Flashing SlimBean b8 + gapps followed by the UBER Kernel after wiping the hell out of everything as my last ditch effort I went past the "Starting apps" while I was feverishly holding onto the Vol UP + DN to get into recovery if it fails again.... to my surprise, it went past that screen and there was the start screen I have been looking forward to.... what drama )
I guess will follow all my flashes with the UBER kernel going forward.

awesome man!! glad you got it fixed - Like i said i knew you would figure it out good stuff man, now you got more knowledge and can help others if they run into the same issue happy flashing ! take care