Originally Posted by dudeicles

Would it help in any way to change to CWM when flashing my AOSP roms?

I would try cwm, I had a gs3 that couodnt flash anything with cwm but could with twrp, my note was the opposite, cwm was awful on it.

Just ran into something very interesting . When I installed Rom Manager and flashed the CWM recovery, I rebooted and my boot screen did the exact same thing it was doing installing AOSP roms. It would seem my problem may just be CWM.

Re: [Q] can't flash AOSP ROMS

---

Originally Posted by dudeicles

Just ran into something very interesting . When I installed Rom Manager and flashed the CWM recovery, I rebooted and my boot screen did the exact same thing it was doing installing AOSP roms. It would seem my problem may just be CWM.

I've heard too many issues with cwm to even try it. Twrp has been flawless for me so why switch? If it ain't broke, don't fix it.

Sent from my SCH-I605 using Tapatalk 2

Ok, so update - Odin'd back to stock and re-rooted using the Casual method. I have the most recent TWRP installed and when i install the AOSP rom it does the exact same thing. I'm thinking about videotaping what the boot animation does and maybe someone can look at it and see what the cause may possibly be.

If anyone has any other suggestions i'm all ears. Again, any rom based on STOCK works without issue (Clean Rom, Jelly Beans and Jedi), but only AOSP roms (And CWM) crash the phone at "Samsung Galaxy Note II" screen on startup.

Thanks for the suggestions so far, just weird it's not working. I may have the single note 2 to never run AOSP roms. LOL

so... oddly enough i still have trouble installing AOSP roms. the only AOSP rom i have been able to install so far is Paranoid Droid. I am slowly trying each one just to see which one i can force to work. Am I the only person who can't just flash whichever rom I want whenever?

Anyone with other ideas on this? I was frequently flashing back and forth between TW and AOSP. The other day I tried to flash AOSP again and get a failed message in TWRP. Already using latest version of TWRP. I then restore a backup of TW. Download again, verify md5, get failed message again. And yes, I wiped everything...same thing I do everytime. Now I have tried to DL and flash multiple different AOSP roms and I get failed everytime. Decided to try CWM recovery and that just aborts. I have NO problems flashing TW roms though

Re: [Q] can't flash AOSP ROMS

---

Follow the advice to Odin back to stock and start over. Otherwise, get a replacement and tell them it's acting weird and slow haha.

Sent from my SCH-I605 using xda app-developers app

Same here!!

---

Originally Posted by spydersilk

Anyone with other ideas on this? I was frequently flashing back and forth between TW and AOSP. The other day I tried to flash AOSP again and get a failed message in TWRP. Already using latest version of TWRP. I then restore a backup of TW. Download again, verify md5, get failed message again. And yes, I wiped everything...same thing I do everytime. Now I have tried to DL and flash multiple different AOSP roms and I get failed everytime. Decided to try CWM recovery and that just aborts. I have NO problems flashing TW roms though

I currently have a Tmobile Note 2. And i recently ran into the same issue. I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb. I also notice that it changed my device id to an SGH-i317, which is an ATT Note 2. The rom was a port from an ATT rom of course, but if it was for ATT, it wouldn't work on my device right? I installed GOOmanager, and flashed the OPEN INSTALL SCRIPT. Which it flashed the ATT version. Everything still worked. I flashed back to stock, and updated OTA. Still nothing. I've also noticed that, if i can open the zip file on my pc, it will work on my phone. For some reason, The AOSP files read invalid. While the Touchwiz roms open like a regular zip file.


Any help is appreciated. Hope some of this info helps.

Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol

Originally Posted by slinky42

I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb.

Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol

This is standard on 4.2.2 ROMs. It is related to the multi-user implementation.