I don't know if you guys are aware of this but evertime I flash something its been with Rom manager. I got very sick of killing WiFi so I started all over again with BAMF beta 5 and flashed the few fixes and a new kernel. Same as I always did but this time I only used recovery and it worked. Haven't killed WiFi at all. Tried a bunch of times and still good to go. Also this only applies to GINGERBREAD ROMS!
Sent from a cellular telephone
You mean flash in recovery?
I had a similar experience but I think it was a coincidence.
Sent from my ADR6400L using XDA App
You should always flash through recovery... ROM manager likes to break things. Glad you got it working though.
yeah. Flash in recovery.. and I don't think its a coincidence. But who knows. Been working great this way
Sent from a cellular telephone
bking_soda said:
You should always flash through recovery... ROM manager likes to break things. Glad you got it working though.
Click to expand...
Click to collapse
Yeah. Ha. I guess so. I'm never using Rom manager again. Lol
Sent from a cellular telephone
I usually flash in recovery because my old OG Droid didn't like rebooting into recovery from ROM Manager. My T-bolt doesn't seem to have that issue and any time I have used Rom Manager to flash several zips at once, usually multiple patches or whatnot, I haven't had any issues. I have yet to flash an entire ROM in ROM Manager though.
So are you saying that ROM Manager is good for nothing but flashing the recovery image and getting CM7 Nightlies when they come out?
I knew I shouldn't have paid for it!
I flashed the bamf2 beta 5 update with ROM manager and my WiFi got messed up. I read this thread, rebooted into recovery, wiped cache and reflashed bamf2 beta 5. Wifi now works
Sent from my ADR6400L using XDA App
Uh ok lol
Sent from my ADR6400L using XDA Premium App
So has anyone let Koush know so he could look into this issue?
rom manager = junk for gingerbread roms i guess. it was amazing on froyo though, maybe they will update
RM updated to 4.2.2.0
CWR updated to 3.1.0.1
Had the same problem with flashing from rom manager. I do not use it anymore
ROM Manager
I was addicted to ROM Manager on my D1, even with Gingerbread ROMS (CM7). I haven't really used it for ROM installation on the Thunderbolt though. I paid for it on the Android Market and have absolutely no regrets, and as the ROMS mature for the Thunderbolt, so will the means for installing them.
Flash away I say.
Used it to flash BAMF 1.6.3 Remix, worked great.
i used it for das bamf 1.6.3 remix and had issues through rom manager. When i flashed through recovery everything went smoothe as butter. This time things were debloated.
tegan_ca said:
Used it to flash BAMF 1.6.3 Remix, worked great.
Click to expand...
Click to collapse
I had problems using it to flash remix, had to use recovery to get it to work correctly. It seemed like it wasn't fully wiping the cache/data before the flash, whereas recovery did.
Newb here, is it possible to download through RM but not trigger the auto-flash-sequence? Every time I d/l something through RM it tries to flash immediately after downloading.
tegan_ca said:
Used it to flash BAMF 1.6.3 Remix, worked great.
Click to expand...
Click to collapse
I had problems using it to flash remix, had to use recovery to get it to work correctly. It seemed like it wasn't fully wiping the cache/data before the flash, whereas recovery did.
My D1 never did like RM or CWM. And its nands were huge. I haven't rooted my Bolt yet... need to get around to that, I desperately miss Titanium and Root Explorer.
Related
Birgertime has done a great job getting EDT ROMs available via Rom Manager (I may have bugged him a couple of times). I was a bit shocked when I was reading the thread and saw people were having issues when they updated using Rom Manager. I think the consensus was that Rom Manager was not properly wiping.
This is what I did:
I was on Trigger 2.9.3 *I try every ROM and I just felt like being old school.
I opened Rom Manager and downloaded the latest Trigger 3.2,
I used the KB1 Modem, KB5 kernel, I selected a few of the apps I wanted (bloater, titanium, maybe a couple others)
I told Rom Manger to wipe and do a backup by clicking the two boxes.
Once the download was completed I proceeded.
It went into CWR and it did a backup... immediately it did a wipe (it showed the steps in CWR like normal)... and then it flashed the ROM and it rebooted perfectly. I have had NO issues with the ROM. It's perfect in my opinion.
What I want to know, for those who had issues... what was different?
Did you get rebooted into the red voodoo recovery (I was at the normal CWR)? I don't understand how it can work perfectly for me, and not others. I would like to know exactly what went wrong so we can go to @koush and try and get both Rom Manager and Clockwork Recovery working better for us.
Between this, Fix Permissions, Partitions F'ing people, stats not working (for the dev's) I think our phone needs this amazing app to be better, and I know koush can do it.
** If there are other things wrong with Rom Manager/CWR, please post... it would be nice to have a list of things to work on.
I can put up a test version on rom manager. The current Trigger 3.2 up there will wipe regardless of what you tell ROM manager.
PS: who rated it 1 star?
birgertime said:
PS: who rated it 1 star?
Click to expand...
Click to collapse
Team Whiskey
EDIT, were you going to fix the prop so it showed 3.2, not 3.1? =)
Im confused. You said you used CWR to wipe and flash the ROM. What exactly did you use ROM Manager for?
s15274n said:
Team Whiskey
EDIT, were you going to fix the prop so it showed 3.2, not 3.1? =)
Click to expand...
Click to collapse
I think I did when I uploaded the vvm fixed version
androidmonkey said:
Im confused. You said you used CWR to wipe and flash the ROM. What exactly did you use ROM Manager for?
Click to expand...
Click to collapse
To download it
Sent from my SGH-T959 using XDA App
duboi97 said:
To download it
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Ah, ok. I dont see why downloading it with RomManager would make a difference, unless its not completely downloading. The safest is like birgertime says in the Trigger thread, download on PC and check Hash.
androidmonkey said:
Ah, ok. I dont see why downloading it with RomManager would make a difference, unless its not completely downloading. The safest is like birgertime says in the Trigger thread, download on PC and check Hash.
Click to expand...
Click to collapse
Rom Manager is the most convenient way to do this. it also checks the MD5 before it flashes the ROM. Trust me when I say I know the process...
I just want to know from those who had issues with using Rom Manager to download/wipe/flash, what went wrong?
I flashed it using Rom manager.
I chose KB5 modem and KB5 Kernel.
along with things like Bloater and swype.
it rebooted into red recovery and seemed to go fine from there.
when it first booted up it seemed ok at first, I let it sit for a while like usual.
and then rom manager force closed.
from there it was just force close after force close.
So I rebooted back into recovery and wiped data and dalvik.
then I rebooted.
and everything works just fine, with the exception of it never installed any of the extras I chose (swype,Bloater, etc...)
but I had those in titanium backup just in case anyways so it wasn't a big deal.
Its been running beautifully ever since.
Pretty much same thing happened to me, it went to red recovery and seemed to flash just fine. then when it rebooted i kept getting force closes everywhere. rebooted to clear cahce, dalvik, and fix permissions and has been fine ever since. it didnt wipe my apps which i found a bit odd
Alright, so as I expected... it sounds like it was
THE RED VOODOO RECOVERY AS THE PROBLEM.
Anyone able to prove that wrong?
I mean, it makes sense, it's not the recovery Rom Manager expects to see.
So, how do we fix it? This would not be koush now, I do not think.
Where did the red voodoo recovery initiate? I remember it just showed up one day. was it supercurio?
I installed BAMF 1.6.3 remix and I noticed that I don't have some of the features that were listed in his OP.
For ex. I still have my location icon in my status bar, when I press on the themed rosie button on the right it still opens up the personalize settings no matter what icon I chose to put there. I don't have the 6 bar signal strength. I don't have the power control settings in my pull down menu, but I do have the power control settings apk in my drawer. Don't have widget picker, Don't have the extra power options when the power button is pressed, reboot, hibernate, etc.... Also when a call is missed it doesn't show the number in my pulldown menu only that I had 3 missed calles from*86 and something about CDMA on the missed call icon.
These are the few that I noticed in the couple hours of it being on my phone. I am just wondering if this is normal or what I may have did wrong and how to get these working as I thought they were part of the ROM itself.
Thanks
Did you flash the rom in rom manager??? If so, thats most likely what created the missing issues.
You have to flash the rom thru CWR for you to get everything up and running fully.
Yeah I downloaded from the forum then installed using ROM manager. I will re-install using CWR. I will post my results. Thanks for the quick response. Oh yeah I noticed my post was at like 1:34 am? It's only 8:47 where im at?
So I re-flashed the ROm and everything seems to be like it should. I wonder why the differnece from Rom Mgr? It's not like I downloaded the file through RM, And It flashed using CWM? Oh well, I will know from now on to flash manually. I don't have the paid version, but if you can't fully flash a rom then what's the point of having/paying for Rom Mgr?
MomentFreak said:
Yeah I downloaded from the forum then installed using ROM manager. I will re-install using CWR. I will post my results. Thanks for the quick response. Oh yeah I noticed my post was at like 1:34 am? It's only 8:47 where im at?
So I re-flashed the ROm and everything seems to be like it should. I wonder why the differnece from Rom Mgr? It's not like I downloaded the file through RM, And It flashed using CWM? Oh well, I will know from now on to flash manually. I don't have the paid version, but if you can't fully flash a rom then what's the point of having/paying for Rom Mgr?
Click to expand...
Click to collapse
Sometimes it works, sometimes it doesn't. Full blown roms I will always try to do in CWR from now on. If its something small like a theme or extra or add on, Rom Manager usually works well.
Glad the reflash worked well thru CWR.
New here , just wanted to ask under this post.
Kind of the same topic.
I came from the dx used droidx bootstrap and dx2 bootstrap.
New the the TB I seen some post saying Rom manager.
So I installed Bamf 1.6 and 1.6.3 remix from Rom manager.
But I hit the flash Rom manager button, success.
Then hit boot into recovery.
Is that what you guys mean when you type. CWR.
Checking to make sure I am doing it correct.
Thank you
tanium said:
New here , just wanted to ask under this post.
Kind of the same topic.
I came from the dx used droidx bootstrap and dx2 bootstrap.
New the the TB I seen some post saying Rom manager.
So I installed Bamf 1.6 and 1.6.3 remix from Rom manager.
But I hit the flash Rom manager button, success.
Then hit boot into recovery.
Is that what you guys mean when you type. CWR.
Checking to make sure I am doing it correct.
Thank you
Click to expand...
Click to collapse
Well you need Rom Manager to Install CWR which stands for ClockworkMod Recovery, Which is where you can make what they call Nandroid backups, which is a backup of your current system and setup including apps and data. So it's always good do backup before making any changes ex, flashing rom's. But there are many things you can do with it and to me is one of the most important parts of having a rooted phone is having recovery. Hope this clears some stuff up.
Yes thank you.
But this is all done from inside Rom manager correct.
I mean I open Rom manager and clicked boot into recovery.
This is how I flashed Bamf 1.6 remix.
I installed no other program or app to get recovery.
Yes I see now , went and looked.
I was following instructions before.
I had to hit flash clockworkrecovery.
That is what installed that I guess.
See learning all the time.
I used droidx bootstrap before never new Rom manager was so cool.
That guy rocks.
I also had this problem. Installing from Rom manager doesn't seem to be enough. You seem to need to boot into recovery and install it manually from cwr.
Sent from my Verizon Wireless 4G LTE Thunderbolt
Definitely noticed that things can come up missing unless you wipe all three Data/Davlik/Cache and use clockwork to do it all. For some reason just flashing and wiping using ROM manager doesnt cut it.
Alright, we will start with a story - I am a fairly experienced root user. I had a fascinate, droid x, and now I have a thunderbolt. I had all three rooted and never had problems until now.
I have root access as well as a custom ROM on my thunderbolt. (I am currently using liquid 3.2).
The problem is that when I try to flash any other rom (I tried two: CM7.2 by ThunderShed and Infected by Virus) they do not work at all. I flash data, davik, and all that stuff. Infected gets stuck on HTC logo and CM7 gets further but freezes on startup after initial setup shows up.
My friend recomended flashing all different radios and I did that, but still having an issue. (I have 1.48.... and 0.0178... on now).
A few things.....check the md5 when you download. Wiping........wipe data/factory reset, then wipe cache, then go advanced and wipe dalvik cache, then go format/mount and format /system. Then install the .zip. If that doesn't do it, I have no idea, never had a problem flashing ROMs, only have problems once I start messing with them on my own.
I had to change to different recovery
Sent from my ADR6400L using xda premium
First, the roms do flash - just not boot up after. Both go through the process fairly well. Like I said - the only that actually works is Liquid 3.2, both Infected and CM 7.2 flash just get stuck at a different stage when booting up.
I'm going to download yet another rom and see whether that does it.
The recovery that I have is 5.0.2.1. I was going to install touch recovery and see if that was more reliable. I'll post later and see whether it was just the two roms possibly being bad (both downloaded from RootzWiki and not XDA).
Run superwipe after you wipe everything, then flash your rom.
Sent from my ADR6400L using XDA
Try flashing a stock kernel first.
I also had the droid, droidX, droidx2, incredible2, thunderbolt, and now the galaxy tab. Also fairly familiar with rooting and flashing, and I had the same problem and couldn't figure it out. My clockwork was out of date. Updated, and everything was right in the world again. Check your Recovery. I didn't think if the update during flash took that it was my recovery but I was wrong.
flashing problem...
did you make sure usb debugging is on, and allow mock locations and non market downloads, and try deleting the current infected rom and re-download it just to make sure it was a clean download...i love the infected roms, especially eternity with darkhorsetheme. if that doesn't do it idk man. best of luck and try to get a hold of a developer maybe
Thank you guys!
Alright, so first off - I made sure my recovery was up to date.
I did wipe format /system and that caused infected to load, but after about an hour of using it - it froze and then when I pulled the battery, it wouldn't go past HTC logo.
I did load CM 7.1 and that works well.
I'll keep digging at it and see if I can figure it out. Thank you everyone!
Did you ever find a solution? I am having the same problem. I have tried 3 roms. It starts the boot screen and then after a minute it reboots into recovery.
It's the recovery folks.
Cwm = fail
4ext = win
donnyp1 said:
Run superwipe after you wipe everything, then flash your rom.
Sent from my ADR6400L using XDA
Click to expand...
Click to collapse
Using super wipe fixed this issue for me. Even after triple wiping dalvik didn't work, super wipe did. :good:
i am stuck. i tried to flash super charged hatka 320 dpi and i have gone in the wrong direction because my dna doesnt boot up properly. after super hatka gets past the boot i am able to get to the lock screen and once i swipe to unlock, it says unfortunately settings have stopped working. my launcher doesnt work. i cant operate the phone what so ever except for looking at the settings. when i get a text message i can reply, but thats pretty much it. i have experience in rooting and flashing the htc g2, gs2, and the gnexus. but this htc dna is something different and i am having extreme difficulties. i can go into much more detail if someone has the moment to help me out
Maybe if you try to re-install the Rom will all be ok....it might solve the problem...did you do a proper wipe before flashing...and did you create a nandroid backup if so restore it in Recovery and then flash the Rom again...if. not first do a proper wipe and then reflash the Rom....I use viperdna so I don't know if you have after the install to flash any kernel,fix or something???check it first and then procceed with the other things..hope to helped yiu
Sent from my HTC Droid DNA
If you came from another ROM or Stock, Factory Data Reset from recovery is advised ... you could also try flashing another custom ROM to get moving
Djmk4 said:
Maybe if you try to re-install the Rom will all be ok....it might solve the problem...did you do a proper wipe before flashing...and did you create a nandroid backup if so restore it in Recovery and then flash the Rom again...if. not first do a proper wipe and then reflash the Rom....I use viperdna so I don't know if you have after the install to flash any kernel,fix or something???check it first and then procceed with the other things..hope to helped yiu
Sent from my HTC Droid DNA
Click to expand...
Click to collapse
i have tried to reinstall it, same problem. this happenes when aroma was finishing the install of the rom
<..simmer down..>
.
..
removing old init.d files...
sqlite3 exists
set_perm:some changes failed
installation failed
error
senseless slim super charged hatka dna v2.1.0
install failed
installer status: 7
i want to install a different rom, idc what rom, but i cant download anything, i tried chrome and iE but none of them will download any roms. does anyone have an alternate link to a rom that isnt linked here on xda?
and i was coming from stock. i certainly wiped cache and factory reset before flashing the rom. i used flash image gui to flash the bootimg and then wiped everything in cwm, the flashed module zip and then flashed the rom. thats pretty much what i did, i do appreciate your replies
dj2muchxx said:
i have tried to reinstall it, same problem. this happenes when aroma was finishing the install of the rom
<..simmer down..>
.
..
removing old init.d files...
sqlite3 exists
set_perm:some changes failed
installation failed
error
senseless slim super charged hatka dna v2.1.0
install failed
installer status: 7
i want to install a different rom, idc what rom, but i cant download anything, i tried chrome and iE but none of them will download any roms. does anyone have an alternate link to a rom that isnt linked here on xda?
Click to expand...
Click to collapse
What's happening mate...really can't help you...the only thing I suggest to write exactly what you wrote here in hatka's Rom thread...maybe the dev that made the Rom....can help you or someone might had the same issue
Sent from my HTC Droid DNA
What recovery are you using? I had an issue with twrp at first and switched to cwm touch. And no issues. I've had issues though by going back after getting stuck at boot and wiped then installed Rom with full wipe. But if its an error not installing might try fastboot flashing a different recovery
Sent from my HTC6435LVW using xda premium
dj2muchxx said:
and i was coming from stock. i certainly wiped cache and factory reset before flashing the rom. i used flash image gui to flash the bootimg and then wiped everything in cwm, the flashed module zip and then flashed the rom. thats pretty much what i did, i do appreciate your replies
Click to expand...
Click to collapse
I think it might be a problem with the download I will fix it later today
Sent from my HTC6435LVW using xda app-developers app
fixed
i may have had a bad download. i was using the 320 dpi senseless rom, my phone was unusable like i had stated, but i managed to get it running.
here is what i did to fix it:
in the settings, i linked my dna with my google account, and as i expected, i received play store notifications about updates, so i chose the notification and it took me to a fully functioning play store.
i downloaded apex launcher and it installed properly. pressed the home button and it automatically set itself as the default launcher and bam! my dna was beginning to function.
downloaded xda app and went to the super charged thread and downloaded the slim version of the rom instead of the senseless rom.
flashed the boot.img, flashed the modules, then flashed the slim rom and i didnt get any errors or failed messages this time.
i dont want to point fingers and i would never do that here on a fantastic community, but the senseless rom was giving me issues, maybe it just needs some more work. anyways phone is functioning like normal now, everything works and the battery is outstanding so far.
thank you to those for the advice. i was getting ready to call it quits and send this thing back to amazon wireless.
MustafaHadaKing said:
I think it might be a problem with the download I will fix it later today
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
i think it was just the rom, if u need a guinea pig to test out your rom or anything, im in. i am enjoying super charged hatka very much:good:
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