Related
gtab wifi, stock tw3.2., cwm 5.8.3.1
i've tried flashing several roms using cwm and through rom manager. every time i get stuck on the the samsung screen after reboot, which takes about 30 seconds after initiating flash. i've never had a problem installing anything on my phones or my nook color. it's been nothing but a paper weight for the last year and it's going to the landfill if i can't figure it out soon.
Did you try to wipe data/factory reset/ wip cachd and wipe dalvik?
all of it. follow directions for each rom exactly. i always end up in the same spot
burnitdown said:
all of it. follow directions for each rom exactly. i always end up in the same spot
Click to expand...
Click to collapse
How much you wait? After I flashed the Galaxy Task 14 room earlier this day it took several minutes to load.
Certain ROMS require an older version of CWM, such as CM9. If that is the latest version you have installed it may not work. Maybe try using ODIN to flash the recommended version (you can easily find that in the CM9 Nightly threads or simply by searching around)?
bar_rodoy
Click to expand...
Click to collapse
i let it sit long enough.
this_is_nick6
Click to expand...
Click to collapse
i'm using the most up to date cwm. right now i'm trying to flash aokp m4
burnitdown said:
gtab wifi, stock tw3.2., cwm 5.8.3.1
i've tried flashing several roms using cwm and through rom manager. every time i get stuck on the the samsung screen after reboot, which takes about 30 seconds after initiating flash. i've never had a problem installing anything on my phones or my nook color. it's been nothing but a paper weight for the last year and it's going to the landfill if i can't figure it out soon.
Click to expand...
Click to collapse
Can you link us to the CWM 5.8.3.1 recovery your using???
As far as I know this is the latest version of CWM http://droidbasement.com/db-blog/?p=2655 as of 6/30 and it's only 5.5.0.4.
As far as Googling is telling me...
1. It may be a touch recovery?
2. I couldn't find a many search returns that mentioned it being for Tab10.1s
3. The search returns I did find that mentioned Galaxy Tabs were in languages I don't read.
Just curious don't ya know...
Sent From My Galaxy10.1 Class Starship....
Questions go in the Q&A section
my recovery is listed on the cwm site under rom manager. it's not touch
now i'm curious as to what version everyone else is using
okay. so i flashed 5.5.0.4 through odin then flashed aokp m4 plus gapps. all seemed to go well until boot time. i've been sitting at the samsung screen for a full 20 minutes now. i suppose my next course of action would be to revert to stock via odin and start the process over? i'd really like to use this thing but absolutely can't stand tw
you may have gotten a corrupt partition somewhere. I'd odin back to stock and start fresh. fwiw, I wouldn't trust ROM Manager for the latest recovery, it doesn't always have the correct file for your device. For example, for may particular phone Rom Manager had never worked properly and soft-bricks the phone every time.
Always check here on XDA for the proper recovery files for this device first.
that's all i needed to hear. now, can anyone point me in the direction of the file i need? my searches all point to S0ckM0nk3y's link which results in a 404 error
disregard my last post. i flashed sam's ics via odin. i'll play with it and try to like it. thank you sir
huh. still can't flash a custom rom...
Well, I don't know what I did but i was able to get MapleSyrup's CM10 preview to run. I'm happy for now
Are you doing a factory reset and wiping the cache in CWM before you flash? I always do that and then use titanium backup to restore my apps.
Also, what version of recovery are you using? I'm on CWM 5.5.0.4 which I've used to flash a couple of different roms, including the latest stock ICS from Toldo I think.
you can get it here and use ODIN to flash. Just make sure you download the correct version for your device:
http://droidbasement.com/db-blog/?p=2668
i had the same problem. i flash stock ics rom for my 7510. at first it looks fine until i try to reboot my tab. it starts to hang at the bootscreen. i try to reflash the rom via recovery but fail. try to install nandroid backup and also fail. the last resort is to do clean flash from odin. this thing happened 5 times in 3 days. one time after i install all the apps and try to restart my tab then it happened again, stuck at bootcscreen.
Why do I have such a problem with recovery on my phone. It seems that regardless of what I'm flashing I have a problem with the phone rebooting into recovery. At least since ICS first came out, maybe earlier, when I'd flash a rom, alot of the time it would reboot into recovery and I'd have to ODIN back to stock and reflash. I flashed PB 3 without any problems but I tried PB4 and it would not boot beyond recovery. It seems to do it in CWM and Devil. I restored to a backup of AOKP and still recovery, which is currently Devil. What am I doing wrong or what do I need to do? I also have a problem keeping it from booting into safe mode, when it does boot. Any suggestions?
From what I can gather from your post it really appears that you are flashing things wrong. First things first, read droidstyle's guide on hoe to flash rooms properly. Couple other notes to keep in mind, once you are on cm7, ics, or jellybean you cannot just go into recovery and flash a touchwiz rom. You also cannot three finger boot into recovery anymore.
Sent from my SCH-I500 using Tapatalk 2
shelby04861 said:
From what I can gather from your post it really appears that you are flashing things wrong. First things first, read droidstyle's guide on hoe to flash rooms properly. Couple other notes to keep in mind, once you are on cm7, ics, or jellybean you cannot just go into recovery and flash a touchwiz rom. You also cannot three finger boot into recovery anymore.
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
I haven't gone back to TW in a long time. As far as flashing wrong, I may be but I'll download the rom, boot into recovery, wipe, wipe, and sometimes wipe again. Then flash rom. When I do ODIN back I push the stock EC09 I think it is (I'm on a different computer), Atlas 2.2. Let it fully boot, shut it down. Then push CWM fixed for CM7. Immediately boot into recovery with the 3-finger method (the only time I use the 3-finger). I flash THS ICS Version 2. Allow it to boot then flashed whatever AOKP is latest. What have I been doing wrong?
At what point does it get stuck in recovery, is it after you flash aokp or after you try to restore a backup?
Sent from my SCH-I500 using Tapatalk 2
shelby04861 said:
From what I can gather from your post it really appears that you are flashing things wrong. First things first, read droidstyle's guide on hoe to flash rooms properly. Couple other notes to keep in mind, once you are on cm7, ics, or jellybean you cannot just go into recovery and flash a touchwiz rom. You also cannot three finger boot into recovery anymore.
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
shelby04861 said:
At what point does it get stuck in recovery, is it after you flash aokp or after you try to restore a backup?
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
Usually after I flash aokp, or another rom. If all I'm doing is doing a restore it's ok. Now I've flashed jt's JB and I can't keep it from booting in safe mode.
This morning after a full charge I booted into recovery to wipe battery stats because I was having poor battery life. I'm running JT's JB by the way. When I rebooted it booted into safe mode. I tried pulling the battery and still safe mode. It took me rebooting 8 times before it did not go into safe mode. What could be causing it? I must be doing something wrong.
It could be a hardware issue or corrupt files. I know this may sound obvious, but I would Odin back to stock a d follow droidstyles guide exactly and start over. Do a fresh install of everything and reinstall all apps. Don't restore backups or anything. This will give you some clues.
Sent from my SCH-I500 using Tapatalk 2
That may be part of my problem. I've read and re-read that and the only thing I'm not doing is checking repartition when I Odin to stock. When I do, Odin hangs up at the beginning and will not do anything else. It works fine when I uncheck repartition. I'm doinloading a new copy of Odin on a different computer and am going to try.
Toddw said:
That may be part of my problem. I've read and re-read that and the only thing I'm not doing is checking repartition when I Odin to stock. When I do, Odin hangs up at the beginning and will not do anything else. It works fine when I uncheck repartition. I'm doinloading a new copy of Odin on a different computer and am going to try.
Click to expand...
Click to collapse
Are you flashing gapps in the same session after flashing rom?
Sent from my SCH-I500 using xda app-developers app
To make a long story short.
I bought this phone yesterday, dedcided to root, flashed cwm through odin, got a failure so the whole night trying to figure out whats going on and still haven't figured it out yet till now. I kept getting the firmware kies upgrade issue with the yellow triangle.
I posted a help thread on the SGH-1727 section and thats where I also got my guide. The whole time I have been putting in SGH-1727 skyrocket drivers and using odin app for that phone. Since there are a few type of galaxy SII on this forum i got confuse.
My goal is to root the phone, get the nicest JB rom and also a nice kernel which I can port over to this phone. I am not going to even start which best roms or even best kernel,but i just want to get back on track on how to fix my problem first.
As of now im stuck on firmware upgrade kies screen. Which Odin should I use to flash? Should I flash a stock rom first or CWM?
First and foremost: You do NOT flash CWM on this phone, it is included in the custom kernels and each ROM is packaged with one. You can change the kernel afterwards if you so desire. Also, DO NOT use any app labeled CWM or ROM Manager... Just don't. You're likely to create problems for yourself. Nothing against you, it's just the way this phone works.
If you can get back to complete stock, I would do so. After that, read the stickies. After that, read them again. TWICE!
Once you're done with that, use Google to search any questions you may still have. End your search queries with: I777 xda - ALL the information you need is here in these forums and can be found by simply searching. Some things you may have to dig a little, but for the basics, it's easily found.
Trust me, I'm being nice. I'm trying to keep you from being flamed... not guaranteeing its gonna work.
Oh, if you don't find it on these boards, don't use the info.
Clay
Team Pirate
Sent from my Buttery Smooth PINK SGH-i777
clay101eve said:
First and foremost: You do NOT flash CWM on this phone, it is included in the custom kernels and each ROM is packaged with one. You can change the kernel afterwards if you so desire. Also, DO NOT use any app labeled CWM or ROM Manager... Just don't, your likely to create problems for yourself. Nothing against you, it's just the way this phone works.
If you can get back to complete stock, I would do so. After that, read the stickies. After that, read them again. TWICE!
Once you're done with that, use Google to search any questions you may still have. End your search queries with: I777 xda - ALL the information you need is here in these forums and can be found by simply searching. Some things you may have to dig a little, but for the basics, it's easily found.
Trust me, I'm being nice. I'm trying to keep you from being flamed... not guaranteeing its gonna work.
Oh, if you don't find it on these boards, don't use the info.
Clay
Team Pirate
Sent from my Buttery Smooth PINK SGH-i777
Click to expand...
Click to collapse
Well the ODIN 1.85 for the skyrocket stated a failure setup,but after taking the battery out of the download mode and turning it back on i keep getting the kies issue triangle error.
I'll try to go back to stock
Please do some searching for this. If you find ANYTHING with "creepyandcrawly" as the user, read it.
Clay
Team Pirate
Sent from my Buttery Smooth PINK SGH-i777
clay101eve said:
Please do some searching for this. If you find ANYTHING with "creepyandcrawly" as the user, read it.
Clay
Team Pirate
Sent from my Buttery Smooth PINK SGH-i777
Click to expand...
Click to collapse
Lesson learned. I feel bad even one of the people that helped me remote access my laptop to resolved the issue that wasn't resolved.
I managed to go back to stock thanks to creepyncrawler guides. Now basing it off a lot of what I see. This phone has a lot of one click programs. I am so used to HTC builds,but not on Samsung.
I don't even know the first step and there are so much information everywhere on here. Don't know where to start. If someone can guide me and not bag on me telling me I'm lazy and don't what to search stuff please I don't need that.
I just don't want to end up like this guy http://forum.xda-developers.com/showthread.php?t=1757972&page=2
Z33type said:
I managed to go back to stock thanks to creepyncrawler guides. Now basing it off a lot of what I see. This phone has a lot of one click programs. I am so used to HTC builds,but not on Samsung.
I don't even know the first step and there are so much information everywhere on here. Don't know where to start. If someone can guide me and not bag on me telling me I'm lazy and don't what to search stuff please I don't need that.
I just don't want to end up like this guy http://forum.xda-developers.com/showthread.php?t=1757972&page=2
Click to expand...
Click to collapse
That was the only case of confirmed emmc damage that I have seen on this forum. If you want to avoid this possibility, then from stock Gingerbread, which I assume you have if you followed my guide, then flash a custom firmware of your choice. The kernels packaged with the custom firmwares all are safe.
Read and follow the first guide linked in my signature, and you can flash custom firmware without taking weeks to study and learn.
creepyncrawly said:
That was the only case of confirmed emmc damage that I have seen on this forum. If you want to avoid this possibility, then from stock Gingerbread, which I assume you have if you followed my guide, then flash a custom firmware of your choice. The kernels packaged with the custom firmwares all are safe.
Read and follow the first guide linked in my signature, and you can flash custom firmware without taking weeks to study and learn.
Click to expand...
Click to collapse
I'm on my final step flashing a rom. I followed your guide to rooting the phone and flashing a gingebread kernel Siyah 2.6 w/ CWM SUCCESSFULLY!! Now my next question is would I able to flash this super nexus rom with my current kermel or flashing this rom overwrite it and ad their own custom kernel?
You have an awesome write up which took me 2hrs to really read read and read make sure i dont eff up
Z33type said:
I'm on my final step flashing a rom. I followed your guide to rooting the phone and flashing a gingebread kernel Siyah 2.6 w/ CWM SUCCESSFULLY!! Now my next question is would I able to flash this super nexus rom with my current kermel or flashing this rom overwrite it and ad their own custom kernel?
You have an awesome write up which took me 2hrs to really read read and read make sure i dont eff up
Click to expand...
Click to collapse
Kernels are always included when you flash a rom, which you can use to flash any other rom.
Sent from Team Pirate! Using Tapatalk 2
Nick281051 said:
Kernels are always included when you flash a rom, which you can use to flash any other rom.
Sent from Team Pirate! Using Tapatalk 2
Click to expand...
Click to collapse
I did a backup, wipe cache, dalvik cache, flashed super nexus rom and google app like im suppose to, rebooted and now im stuck on the nexus boot screen for more than 10 minutes now.
What am I missing? Should I wipe data/factory reset as well next?
Always follow the OPs instructions for installing their ROM.
Faryaab said:
Requirements:
Clockworkmod Recovery (CWM)/Any custom recovery
Wipe if coming from any other ROM
Instructions:
Copy Google Apps and SuperNexus ROM to your internal SD Card
Enter Recovery
Do a Wipe/Factory Reset (Necessary if coming from a different ROM)
Flash SuperNexus ROM
Flash Google Apps
Reboot your device!
Voila!
Click to expand...
Click to collapse
With that being said, NEVER assume that you will be able to use your phone after a flash. Not trying to deter or scare you, but always have everything backed up and anything you really want off the phone (pics etc.) - Some say a FULL WIPE us need between every flash. I agree. It GREATLY reduces your chance of having a bad flash.
So, in short, yes. You seem to be catching on, but in your spare time read up on some more helpful threads and I think you'll be a flashaholic on your S2 soon enough
Also, this device is vastly different than any other. If you have experience with other phones, that's great, but not always helpful.
Clay
Team Pirate
Sent from my Buttery Smooth PINK SGH-i777
Z33type said:
I did a backup, wipe cache, dalvik cache, flashed super nexus rom and google app like im suppose to, rebooted and now im stuck on the nexus boot screen for more than 10 minutes now.
What am I missing? Should I wipe data/factory reset as well next?
Click to expand...
Click to collapse
Always wipe data/factory reset & wipe cache when flashing a different rom than the one you currently have (sometimes when updating a rom to newer version of the same rom, some say data wipe is not needed). Go back into recovery mode by holding volume - & + and the power button and release when you see the second samsung splash screen. You will be able to wipe data and then reboot into SuperNexus if all goes well, if not then re-flash the rom and gapps. Also to prevent lock-ups on SuperNexus I recommend using Siyah 4.1.4 (in siyah thread) or Siyah 4.1.5 (in the semi thread) for a kernel. To do that just go back to recovery and flash the kernel (wiping cache & dalvik) then reboot. Also SuperNexus comes with ROM manager but do not use it, Siyah will install CWM recovery. These are the steps I followed when doing this on my I777.
You should always full wipe when switching roms. Initial boot can take awhile, though. If you hit 30, re try with full wipe
Sent from my broken screen beast machine
Cmoore0965 said:
You should always full wipe when switching roms. Initial boot can take awhile, though. If you hit 30, re try with full wipe
Sent from my broken screen beast machine
Click to expand...
Click to collapse
U don't have to wait 30 minutes. I've never had a rom take more than 5 to fully boot up. And as stated always wipe data cache and system when coming from a different rom base or upgrading to a new base.
Sent from Team Pirate Headquarters.
30 is just my "****s definitely not happening" cut off. The anticipation of potentially having screwed something up leads me to sweat the boot time. I've had a handful of 10-15 minute boots back during broken ics days. Call it fire and forget stress management lol
Sent from my broken screen beast machine
Hi there,
I tried to flash a new rom and it some how is stuck on the reboot screen.
Any help in what to do, would be great!
Thanks!
Pull the battery, put it back. Hold button combo to boot to recovery. Flash the ROM again but do not wipe. Reboot and you should be good.
FFR please list which ROM you are coming from and the ROM you are flashing.
Sent from my SCH-I535 using xda premium
Thanks, for your help!
I ended up taking out the battery, and then rebooting it, and it went to the Recovery mode.
I actually did wiped everything all over again, like you were doing it from the start originally, and it seemed to work fine.
I cant even remember what I was coming from, I had it on my Phone for almost two years, and it was old and the battery life was terrible.
I tried RemlCS-JB its not bad, but I think I am going to try another one. Any suggestions? I have been away from this forum for over a year, so anything recent with good battery life and good GPS is ideal.
The rom did not seem to come with an app downloader such as google play, or Clockwork manager.
Anyone know how to get into reboot recovery mode without clockworkmanager?
When I try to download clockworkmanager online it does not let me really download it.
When I try to install a new Auxura rom it states the following:
It says Installation aborted
Above that, it states please switch Edify scripting
Anyone know, if I have to do something else? I am just doing a normal Clockwork Flash.
I wiped the data/factory set, then tried to install the rom
molson24 said:
When I try to install a new Auxura rom it states the following:
It says Installation aborted
Above that, it states please switch Edify scripting
Anyone know, if I have to do something else? I am just doing a normal Clockwork Flash.
I wiped the data/factory set, then tried to install the rom
Click to expand...
Click to collapse
Did you Odin back to stock before trying to flash a ROM that is a previous version of android? It could cause a lot of problems if you don't Odin back to stock first!
Did you flash gapps on the ROM that you said was missing apps etc?
Gapps is a package of Google apps that devas can't include in the ROM.
I wouldn't use ROM manager, in most ROMs, there is an option to reboot to recovery in power menu. You can also power down and use button combo to boot to recovery.
I highly suggest reading through some of the dev threads for any ROMs you are interested in. It will answer most of your questions and prevent future issues.
Sent from my GT-P5113 using xda premium
Oh yeah, it said to flash GAPPS after, but I never did. Where do you get GAAPS?
No, I dont even have ODIN installed on my computer and all of those drivers, so It is something I do not want to do.
It has been 2 years since, I switched, so I randomly flashed to this new one, but I want to try a different one, but seems to get an error.
Ill try a few other roms to see if they work though.
molson24 said:
Oh yeah, it said to flash GAPPS after, but I never did. Where do you get GAAPS?
No, I dont even have ODIN installed on my computer and all of those drivers, so It is something I do not want to do.
It has been 2 years since, I switched, so I randomly flashed to this new one, but I want to try a different one, but seems to get an error.
Ill try a few other roms to see if they work though.
Click to expand...
Click to collapse
You can get the gapps from the op of the ROM thread or go to www.goo.im/gapps
As far as Odin etc
If you are on an ICS or JB ROM and want to go back to a froyo or GB ROM, you need to odin to stock first.
General rule of thumb, you can flash up but to flash down, Odin to stock first.
Sent from my SCH-I535 using xda premium
Anyone have an idea why every time I install an aosp rom it glitches at the Samsung boot screen then just goes black and I have to pull the battery? I've installed clean, jelly beans and jedi Rom without issue. Any help is appreciated.
Update your twrp then try again. Make sure your doing full wipes and flashing gapps
Sent from my SCH-I605 using Tapatalk 2
hopesrequiem said:
Update your twrp then try again. Make sure your doing full wipes and flashing gapps
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Just updated my TWRP to 2.4 and did what you suggested with the wiping and same problem.
The Samsung Galaxy screen glitches to half way off the screen, then goes off, then comes back on then the whole thing goes black and nothing.
I'm going to try another rom and see if it still does it as well.
dudeicles said:
Just updated my TWRP to 2.4 and did what you suggested with the wiping and same problem.
The Samsung Galaxy screen glitches to half way off the screen, then goes off, then comes back on then the whole thing goes black and nothing.
I'm going to try another rom and see if it still does it as well.
Click to expand...
Click to collapse
Even with another ROM it doesn't seem to want to work. It's really weird, because any Touchwiz ROM works fine, it only does it on AOSP roms..... I'm hoping someone knows what the fix for this is.
dudeicles said:
Even with another ROM it doesn't seem to want to work. It's really weird, because any Touchwiz ROM works fine, it only does it on AOSP roms..... I'm hoping someone knows what the fix for this is.
Click to expand...
Click to collapse
Odin to stock then re unlock and try this all again? I'm not sure what else you can try. I flip between aosp and tw almost daily
Sent from my SCH-I605 using Tapatalk 2
The Note 2 that couldn't...
Sent from my SCH-I605 using Tapatalk 2
1ManWolfePack said:
The Note 2 that couldn't...
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Heh I think I can I think I can...I was thinken are you trying to flash the file that the post links to because thats not the right one you need to get the note 2 lte one tolte..just a though I downloaded the wrong one first but caught it
http://changelog.bbqdroid.org/#t0lte/cm10.1/next
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Acery said:
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Click to expand...
Click to collapse
Yeah it can't hurt even if they don't say that
Sent from my SCH-I605 using Tapatalk 2
Acery said:
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Click to expand...
Click to collapse
Would it help in any way to change to CWM when flashing my AOSP roms?
dudeicles said:
Would it help in any way to change to CWM when flashing my AOSP roms?
Click to expand...
Click to collapse
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.
dudeicles said:
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.
Click to expand...
Click to collapse
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
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!!
spydersilk said:
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
Click to expand...
Click to collapse
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
slinky42 said:
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
Click to expand...
Click to collapse
This is standard on 4.2.2 ROMs. It is related to the multi-user implementation.
slinky42 said:
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
Click to expand...
Click to collapse
Did you ever get your phone to install the AOSP Roms? Mine worked when l just let the phone sit. Now it works fine all the time.
Sent from my SCH-I605 using xda app-developers app