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:
Related
Hi everyone.
I'm pretty new to android, but I'm quite good at following instructions. Basically I've tried doing a nandroid backup with ROM Manager and everytime it reboots to make a backup it goes to a black screen with a phone in the middle of the screen with a red warning sign next to it. I've always tried booting into recovery and I get the same result. I first found this out while trying to follow the instructions for replacing the status and battery icons. Has anyone else had this issue?
I'm using ROM Manager v3.0.0.1 on a stock HTC MySense ROM from TMO running Android v2.2.1.
Thanks in advance for anyone that knows what I'm apparently doing wrong.
when you opened ROM Manager did you select "Flash ClockworkMod Recovery"? if not try that, it's the only time mine has what your's is doing. I got a little excited to flash Iced-Glacier when I first got the phone and accidentally skipped that step and had same issue
Yeah I first clicked on Flash ClockworkMod Recovery and it currently says Current Recovery: ClockworkMod 2.5.1.2. I just redid the flash and tried to boot into recovery mode and I'm still getting that error picture upon reboot.
Is there a setting on the phone somewhere that would cause this?
I am not positive 100% but I think I know what you mean; and I had it once due to very low battery charge. See if it is the problem or not.
infraled said:
Yeah I first clicked on Flash ClockworkMod Recovery and it currently says Current Recovery: ClockworkMod 2.5.1.2. I just redid the flash and tried to boot into recovery mode and I'm still getting that error picture upon reboot.
Is there a setting on the phone somewhere that would cause this?
Click to expand...
Click to collapse
The phone with the triangle is the stock recovery image. Others have had to try flash the ClockworkMod Recovery several times. You may need to as well.
this is what i did, not sure if your doing the same thing or not. i clicked on Flash ClockworkMod Recovery, MY4G came up and i clicked that and then clicked on backup current rom.
Alright so I've tried it with a full battery and I had the same result. I also tried reflashing several times with the current version and rebooting. I even tried to load some of the older versions of clockwork through ROM Manager and everytime I tried it spits out an error. I don't understand how I could be having such a hard time with something everyone seems to be able to do effortlessly.
Sent from my HTC Glacier using XDA App
R u sure u r rooted with S-off? If u r then u may have to flash recovery from ADB. Some people have not been able to get recovery to stick through ROM manager. There is a thread in the development section that explains how to do this.
Sent from my HTC Glacier using XDA App
Really? I have not heard that...I'll have to check up on that. It seems that this problem would be more common, but I guess not as I have had little luck in finding information on my own about this problem.
Just in case anyone is following this thread with the same problem as me, this is the post that the previous poster was referring to:
http://forum.xda-developers.com/showthread.php?t=852905&highlight=recovery
UPDATE:
Ok I figured out what was wrong. Apparently although I had root access on my phone and able to run things like Titanium Pro and Adfree and others with root privileges it wasn't good enough.
I followed the instructions here on how to permaroot your phone by pushing gfree to it. Once I did that I attempted to manually flash clockworkmod, which I ended up running into other issues. On a lark I tried installing clockworkmod through ROM Manager after permarooting and it finally installed it properly!
I love doing stuff like this, thanks to everyone for their input as it guided me to finally solving this. I'm off to do a nandroid backup now.
krypto16 said:
R u sure u r rooted with S-off? If u r then u may have to flash recovery from ADB. Some people have not been able to get recovery to stick through ROM manager. There is a thread in the development section that explains how to do this.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I have NEVER been able to flash Recovery with ROM manager. It says it does it but corrupts if everytime! Note: There has been some recent updates to ROM Manager and I haven't tried lately.
krypto16 said:
R u sure u r rooted with S-off? If u r then u may have to flash recovery from ADB. Some people have not been able to get recovery to stick through ROM manager. There is a thread in the development section that explains how to do this.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
IIRC the security protocol doesn't have to be off to flash clockwork ROM you do have to be rooted, VISONary.apk of course. I've turned my S=on just to make sure and it [clockworkROM] works pretty flawlessly.
Hey hey, it's great to see infraled out here! I am rooted/S=Off via the first VISIONary thread that was posted...
http://forum.xda-developers.com/showthread.php?t=834225
I installed Clockwork, flashed Clockwork Recovery and was expecting to have to do it twice, as outlined in this thread...
http://forum.xda-developers.com/showthread.php?t=858021
It only took one shot for me and it worked perfectly. The very first try, I powered off, powered on w/ vol down, went into Recovery and wham, there was Clockwork in its green glory. I figured I was just lucky and that once I rebooted, it would be lost and I'd have to flash again. Not so. Did a backup right away, worked flawlessly.
Looking forward to Iced Glacier, eVil and Cyanogen over the holiday break...
shlongwoodian said:
Looking forward to Iced Glacier, eVil and Cyanogen over the holiday break...
Click to expand...
Click to collapse
Cyanogen Gets my vote... But i've always loved T/DB's ROMS.
Recently rooted My new MyTouch 4G, downloaded the paid version of rom manager. I didn't understand why there are none of the current roms like the iced glacier, roms made by evil and several others listed as possible roms for flashing. The only roms are the cyanogenmod nightly builds. The cyanogenmod 6.1.2 RC2 isn't listed either. Do I need to do anything to get those listed or is that just the way it is???
Thank you,
Vinny
Yesterday i installed Kaosgingerbread rom to my eris and it worked sucessfully...but i found out that all of my apps are gone EVEN MY APP MARKET the only app i have is superuser so now there is no market to get rom manager.! WHAT DO I DO?! i need help asap please if you are reading this help me an and if anyone knows what to do reply or something!!!!!!!!!!! thank you so much//// o yea and also my messeging works but when i try to add a gmail account it wont load successfully to..
You need to find the appropriate gapps zip file and flash it along with the new ROM to get market back. Flashing a new ROM will almost always delete everything on the phone.
OK i am kind of new to this sorrry for being a pain in the butt but can you explain it more because i really like the rom and all but besides the fact that i dont have the marketplace it sucks...so if its possible can you explain step by step and if not would it be possible to contact you through something like xbox or maybe email?
Funkinmonkyy said:
OK i am kind of new to this sorrry for being a pain in the butt but can you explain it more because i really like the rom and all but besides the fact that i dont have the marketplace it sucks...so if its possible can you explain step by step and if not would it be possible to contact you through something like xbox or maybe email?
Click to expand...
Click to collapse
In the [GINGERBREAD] KaosGingerbread V8 thread Punk.Kaos says (attention to the very last sentence):
V8
Sensors working now(except light sensor) partially based on code by Petr Havlena
Improved GPS libs that should make GPS work more consistently.
V7
Forward port of Cyanogen Froyo copybit libs partially based on code by ezterry and bypass23 which fixes graphical slowness in OpenGL.
HUGE speed improvements!
V6
Rolled up to AOSP 2.3.1
Speed improvements
Working OpenGL
Fixed a stability issue with Bionic
Merged latest SU
Fixed Wifi
Fixed Bluetooth
Gapps is having an issue when rolled in currently. for now flash http://www.mediafire.com/?bupx532u98cfrj9 after flashing V6.
Click to expand...
Click to collapse
Most, but not all of the time anymore when you flash new ROMs you have to flash the GAPPs (Google Apps) package immediately after flashing the ROM, before you reboot into the ROM. Otherwise things like Market and GMail aren't there and you have a crippled phone.
You have to start over from scratch from recovery doing a factory reset/data and cache wipe and then flash the ROM and then the GAPPs.
Enjoy!!!
roirraW "edor" ehT said:
In the [GINGERBREAD] KaosGingerbread V8 thread Punk.Kaos says (attention to the very last sentence):
Most, but not all of the time anymore when you flash new ROMs you have to flash the GAPPs (Google Apps) package immediately after flashing the ROM, before you reboot into the ROM. Otherwise things like Market and GMail aren't there and you have a crippled phone.
You have to start over from scratch from recovery doing a factory reset/data and cache wipe and then flash the ROM and then the GAPPs.
Enjoy!!!
Click to expand...
Click to collapse
Not really true. When i flashed my rom I reboot to homescreen, then flash gapps from recovery. No need to reflash the rom.
Sent from my TastyBreadBuild using XDA App
spc_hicks09 said:
Not really true. When i flashed my rom I reboot to homescreen, then flash gapps from recovery. No need to reflash the rom.
Sent from my TastyBreadBuild using XDA App
Click to expand...
Click to collapse
AFAIK, this advise given by most of the devs in their ROM threads was based on some reports, from time to time, that people who hadn't flashed the GAPPs before booting the ROM, and flashing it after caused their phones to not behave correctly. Flashing it immediately eliminates any possibility that someone might have a problem with that particular part of it, so it's wiser to be cautious and just give the blanket advise to do it immediately than to chance that with some ROMs or some phones, problems might arise.
yea well.. anyone wanna post a tut. on how to do this or something
Funkinmonkyy said:
yea well.. anyone wanna post a tut. on how to do this or something
Click to expand...
Click to collapse
Download the gapps file from kaos thread. Place gapps zip along with the Rom zip to the root of your sd card. Reboot into recovery. Wipe/factory reset. Wipe dalvik. Flash Rom. Flash gapps. Reboot. Enoy.
That is very true. You'll get the jist of things when u flash roms more often
wait i havent done anything yet but is there a way to restore my phone just back to factory settings?
OK WELL I AM TRYING TO INSTALL GAPPS ONTO MY PHONE FROM MY COMPUTER BUT IT WONT RECOGNIZE MY "DEVICE"/ USB PLUG IN so now what do i do?
Funkinmonkyy said:
OK WELL I AM TRYING TO INSTALL GAPPS ONTO MY PHONE FROM MY COMPUTER BUT IT WONT RECOGNIZE MY "DEVICE"/ USB PLUG IN so now what do i do?
Click to expand...
Click to collapse
Reboot both devices (with the phone unplugged from the computer to start with) and try again. Also, you can mount the SD card via USB directly from Amon RA or Clockwork Mod Recovery. Something like Mount USB-MS in Amon. In Clockwork Mod, it's in the partitions menu.
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 just did the newest OTA for MeanBean 2.8. I was having issues with crashing. I also tried a fresh install of MeanBean 2.8 after a full wipe and it seems to have gotten worse for me. I know it isn't the ROM itself because MeanBean is just pure awesome. On the fresh install, I was getting as far as entering my account information for Dropbox during the first time setup and during typing the white text boxes would turn black and the screen would start to sort of dim/flick. I re-installed the previous version of MeanBean 2.71 and all of my problems have vanished.
I would have posted this in the MeanBean ROM thread but I'm not allowed to yet.
seansratigan said:
I just did the newest OTA for MeanBean 2.8. I was having issues with crashing. I also tried a fresh install of MeanBean 2.8 after a full wipe and it seems to have gotten worse for me. I know it isn't the ROM itself because MeanBean is just pure awesome. On the fresh install, I was getting as far as entering my account information for Dropbox during the first time setup and during typing the white text boxes would turn black and the screen would start to sort of dim/flick. I re-installed the previous version of MeanBean 2.71 and all of my problems have vanished.
I would have posted this in the MeanBean ROM thread but I'm not allowed to yet.
Click to expand...
Click to collapse
No issues here. Flashed it about 45 minutes ago and all is good. You might try going into recovery and flashing the sticky settings .zip file in the MeanBean folder. This will bring up the Aroma installer where you can make changes to the ROM. You might want to choose the option to overvolt. Some phones just like to play differently when it comes to overclocking and voltages. You might also try a clean install instead of a dirty one.
Sent using my HTC EVO LTE and a magic wand
yea its running perfect for me also
You probably got a bad download. Just redownload the Rom
Sent from my EVO using xda premium
Try fix permissions, you may need to wipe and start fresh if apps keep crashing
Like mentioned above, you could turn on the option to overvolt, or you may just want to turn off overclocking entirely. I haven't had problems with it but some people's phones seem to not do well with overclocking.
I'd try redownloading the Rom, then in recovery wipe everything so fully clean install. Then flash Rom, and before you boot into Rom for the first time flash the sticky settings and just put all to pretty much stock then boot. If all works you can always go back and flash sticky settings again.
Sent from my EVO using xda premium
won't flash
I have HTC Evo 4g lte rooted and s-off
With super jelly milestone ROM
Twrp 2.4
I've clean wipe and it just won't flash mean bean 2.9
It go's back to fastboot
Please help
Might be the new TWRP that's causing the problem?
Sent from my Nexus 7 using xda app-developers app
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