When i bought the player which is the 4.0 us player i rooted it and put steves kernel on it thats it. Today my wife said it was bootlooping so i looked at it and sure enough it is. Checked the memory and there is nothing on it. So i download a new rom put it on and wipe then install and it is still bootlooping the original logo even though the new rom has a different boot screen.
erawtik said:
When i bought the player which is the 4.0 us player i rooted it and put steves kernel on it thats it. Today my wife said it was bootlooping so i looked at it and sure enough it is. Checked the memory and there is nothing on it. So i download a new rom put it on and wipe then install and it is still bootlooping the original logo even though the new rom has a different boot screen.
Click to expand...
Click to collapse
Yes people were experiencing bootloops with steve's 3.0. Try installing the klin's R3 custom kernel or Dark_balor's terra silent.
When i installed the kernel it was back in December and it has been working just fine untill today. Still think it is kernel?
You didn't make a cwm nandroid backup, did you? Because that is what bootlooped mine using Steve's. All I did to solve it is: flashed my own backup, that turned out to be no good, and ended in a full brick (epic facepalm, I know!). Then I flashed kwipper's recovery rom found in the development. After a data/cache wipe, it worked fine. Hope you figure it out!
Sent using Tapatalk
erawtik said:
When i installed the kernel it was back in December and it has been working just fine untill today. Still think it is kernel?
Click to expand...
Click to collapse
That depends of the kernel's version. Also has your wife do something wrong?
ok just flashed new kernel then tried 2 different roms with no luck it flashed the kernel fine but the roms will not flash and when i check the mem card it is empty other than my rom zips and .androidsecure which is an empty folder.
erawtik said:
ok just flashed new kernel then tried 2 different roms with no luck it flashed the kernel fine but the roms will not flash and when i check the mem card it is empty other than my rom zips and .androidsecure which is an empty folder.
Click to expand...
Click to collapse
Well you can always use the full recovery method to get back to normal (note that you will lose all your data. Not on the sdcard though but all of your settings and apps.)
well iv already wiped so everything is gone anyway im not sure how you do the full recovery? I have no nand so if that is what your talking about that is out of the question. Found fixing bootloop which has recovery file so im gonna try that.
erawtik said:
well iv already wiped so everything is gone anyway im not sure how you do the full recovery? I have no nand so if that is what your talking about that is out of the question. Found fixing bootloop which has recovery file so im gonna try that.
Click to expand...
Click to collapse
It seems that you already have an android device before however samsung devices are different from other android devices (or maybe you did have a samsung device too.). They use odin/heimdall flashing with .tar/.img/.rfs files. The recovery method I talk about is at that link:
http://forum.xda-developers.com/showthread.php?t=1531850
worked thanks............. ya i have a hero, evo, evo 3d, and evo shift. As for phones dont think i could leave htc every time i do i come right back. I wanted a new mp3 player and knew i would not get a pos apple so this player was perfect.
erawtik said:
worked thanks
Click to expand...
Click to collapse
No problem. Also I recommend using either klin's kernel or terra silent.
ya just did a nand and flashed new kernel and now changing roms.
Related
I unlocked the bootloader and rooted it okay... then I flashed a ROM, that also worked fine. I tried to flash a kernel and now it just gets stuck on the HTC screen. I tried restoring my back up, still the same issue. Tried reflashing the ROM, same issue. Not sure how to get it back to normal at this point.
It sounds like the kernel you flashed is either a 2.3.3 kernel that doesn't work on 2.3.4, or it was a bad flash. You should be able to fix this by holding volume down when booting up (opens HBOOT) then choose Recovery and from the recovery you can then either enable USB Mass Storage device and transfer a stock kernel over USB to your SD card then flash the stock kernel, or if you already have a stock kernel on your SD card, you can just select it from the install from zip menu and flash.
This Kernel should work fine (it's stock with CIQ spyware removed):
http://forum.xda-developers.com/showthread.php?t=1224659
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Coriolis3ffect said:
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Click to expand...
Click to collapse
ROMs usually have kernels. You could just wipe Dalvick cache and cache and flash your original rom (which has it's original kernel). and that should work.
There's a sea of roms. You could try posting on a rom's thread whether a particular kernel is compatible. Just follow the spin of things. Saves from just going round in circles.
Coriolis3ffect said:
and after I flash this kernel it should be back to normal.... or should I try to flash a ROM all over again as well? As long as it can definitely be fixed then that's quite alright.... this phone compared to the Epic (which I came from) seems like it's much less fail safe to me.
Click to expand...
Click to collapse
Here's a scenario: If you installed a rooted stock 2.3.4 rom then decided to install Silverneedle kernel, your phone will get stuck in this boot-loop because the silverneedle kernel is not compatible with 2.3.4 yet. So by flashing a stock kernel over what is already on there, it should fix the problem. Before you flash the stock kernel clear cache and dalvik. After that flash the kernel and reboot the phone. Chances are it will boot normally. I doubt you will have to reflash a ROM to fix this.
Just cleared the dalvik and the cache, reflashed the ROM hoping to start completely fresh and its still getting stuck...
Coriolis3ffect said:
Just cleared the dalvik and the cache, reflashed the ROM hoping to start completely fresh and its still getting stuck...
Click to expand...
Click to collapse
Then flash a stock kernel. I have had the same problem before. I flashed a ROM, installed a kernel and stuck at HTC boot screen. The fix is to either install a stock kernel through bootloader or flash another ROM in recovery. If you want the best chance of it working the first time, then flash the stock rooted 2.3.4 ROM by xhausx. If you want to try other ROMs and kernels, make sure that your ROM and kernel are compatible. Also use the synergy wipe zip file before flashing to make sure everything is formatted properly. Also, did you flash the extra firmwares that came with the 2.3.4 update? If not, make sure you flash those along with the new radio that just came out.
Sent from my PG86100 using Tapatalk
Take it you didn't do a nandroid before flashing?
Sent from my PG86100 using xda premium
Tried to get my nandroid and it still got stuck..
Perhaps I should've also mentioned that my bootloader still says S-ON and I unlocked it using the HTC unlock method.
sn0b0ard said:
Then flash a stock kernel. I have had the same problem before. I flashed a ROM, installed a kernel and stuck at HTC boot screen. The fix is to either install a stock kernel through bootloader or flash another ROM in recovery. If you want the best chance of it working the first time, then flash the stock rooted 2.3.4 ROM by xhausx. If you want to try other ROMs and kernels, make sure that your ROM and kernel are compatible. Also use the synergy wipe zip file before flashing to make sure everything is formatted properly. Also, did you flash the extra firmwares that came with the 2.3.4 update? If not, make sure you flash those along with the new radio that just came out.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Not sure about any extra firmwares actually.... currently going to try flashing xhaus' ROM and hope that works...
Flashed the superwipe before flashing the ROM, then flashed the ROM... it went to the HTC screen for a second then just vibrated and then turned black.
When I go into the bootloader when it is loading up the images.... it kept saying "No Image!" for all of them. I'm not having any luck with this at all.
Coriolis3ffect said:
When I go into the bootloader when it is loading up the images.... it kept saying "No Image!" for all of them. I'm not having any luck with this at all.
Click to expand...
Click to collapse
Do you have it named exactly PG86IMG.ZIP?
Sent from my PG86100 using xda premium
Okay... you mentioned something about firmwares to flash... which ones are they?
I'm kinda lost at this point because I'm not sure about the specific order in which you are supposed to do things.
Which version of hboot do you have?
Sent from my PG86100 using xda premium
1.50.000 or whatever
Just follow this guide easy. Easy step by step.
http://forum.xda-developers.com/showthread.php?t=1231249
jayharper08 said:
Just follow this guide easy. Easy step by step.
http://forum.xda-developers.com/showthread.php?t=1231249
Click to expand...
Click to collapse
+1 on this. RUU method should be bullet proof
Coriolis3ffect said:
Okay... you mentioned something about firmwares to flash... which ones are they?
I'm kinda lost at this point because I'm not sure about the specific order in which you are supposed to do things.
Click to expand...
Click to collapse
It's in the post that xhausx made for the stock rooted 2.08.651.2 ROM.
URL: http://forum.xda-developers.com/showthread.php?t=1223979
List of new firmwares for the 2.08.651.2 update:
(If you do the RUU method, you should have all the firmwares installed automatically btw...)
Radio & PRI Updates Radio 0.97.10.0808 PRI 1.24_003
PG86IMG_radio_pri.zip (MD5: E28414AAC6F91CE9D7B3615B2999AD3A)
RPM Possible fix for Black SOD
PG86IMG_rpm.zip (MD5: DE69396C8922FAD3AC82E5F836EE95FB)
SBL Secure Bootloader?
PG86IMG_sbl.zip (MD5: 5604349AD611241CF1AC152FD3B0DE45)
TZ Trusted Zone - Not sure of it's purpose
PG86IMG_tz.zip (MD5: 75749FBCCE1331A5A85D2A154E15B276)
PG2F2_SPCUSTOM - No idea what it is
PG86IMG_pg2f2_spcustom.zip (MD5: 7A7DE8659A0771919A14B0C299CA18CC)
Click to expand...
Click to collapse
The link posted is for the GSM Evo 3D... will it work on CDMA?
Anyone try this full touch recovery yet? https://plus.google.com/u/0/103583939320326217147/posts/N9FpGn2Rq7a
troyboytn said:
Anyone try this full touch recovery yet? https://plus.google.com/u/0/103583939320326217147/posts/N9FpGn2Rq7a
Click to expand...
Click to collapse
Ya there is a thread all about it a page back . has a few minor bugs usb mount doesn't work battery doesn't charge while in recovery. Kinda nice tho touch screen part .
i was just messing with it again and the only rom it would let me flash was clean 2.0 de.. every other rom i tryed to flash it wouldnt work?? this is the 2 time i tryed it the last time was yesturday and it made my phone reboot and my phone never does that.. so im deff sticking with twrp 2.0.. twrp has never gave me a problem yet..
evod3 said:
i was just messing with it again and the only rom it would let me flash was clean 2.0 de.. every other rom i tryed to flash it wouldnt work?? this is the 2 time i tryed it the last time was yesturday and it made my phone reboot and my phone never does that.. so im deff sticking with twrp 2.0.. twrp has never gave me a problem yet..
Click to expand...
Click to collapse
Twrp 2.0 had issue with themes not applying and apk files that were cooked into a rom not showing up. A bunch of folks had issues with it.
Last night, every time I went to flash zips that worked fine in TWRP (format all zip, ViperROM 2.5, etc.), I got a "status 1" error and they wouldn't flash in CW Touch. I bought the app in the market, so I'll check it again when they release a couple new revisions.
Just a heads up, I was pretty taken by the fact that it wasn't working as I've had nothing but good luck with CWM in the past. I went back and verified that the MD5's on my ROM zips were good, so I'm pretty sure there's an issue there. Oh well, either wait for Phoenix or a newer revision of CWM.
Hey,
I've had a really big problem with Siyah Kernel V3.1 rc6, i flashed it not long ago because i was going to go from CheckROM v6 to HyDrOG3N 18/04, but i didn't get hard bricked by the Kernel as people have been experiencing, I got a Soft Brick, so I went back into CWM and i couldn't flash anything, anything i tried to flash anything it would give me the error "failed ro:getprop I9100" or something along the lines of that, so i started messing around, hoping for anything to work, and creating a second ROM through the dualboot settings and deleting it somehow worked, but now I can't connect to my service provider (T-Mobile UK) regardless of what i have flashed on my phone, this is a really big problem for me as this phone is my day to day phone and i dont have a backup at all, if anybody has any suggestions at all as to what it could be and how I can combat this as soon as possible, I would be really appreciative
TIA Guys
Beans
N
bbeanss said:
Hey,
I've had a really big problem with Siyah Kernel V3.1 rc6, i flashed it not long ago because i was going to go from CheckROM v6 to HyDrOG3N 18/04, but i didn't get hard bricked by Kernel as people have been experiencing, I got a Soft Brick, so I went back into CWM and i couldn't flash anything, anything i tried to flash anything it would give me the error "failed ro:getprop I9100" or something along the lines of that, so i started messing around, hoping for anything to work, and creating a second ROM through the dualboot settings and deleting it somehow worked, but now I can't connect to my service provider (T-Mobile UK) regardless of what i have flashed on my phone, this is a really big problem for me as this phone is my day to day phone and i dont have a backup at all, if anybody has any suggestions at all as to what it could be and how I can combat this as soon as possible, I would be really appreciative
TIA Guys
Beans
Click to expand...
Click to collapse
Try flash stock rom(ics) with odin with full wipe or try formatting system,maybe deleting your dualboot roms and flash rom from cwm.
zodiaxe66 said:
N
Try flash stock rom(ics) with odin with full wipe or try formatting system,maybe deleting your dualboot roms and flash rom from cwm.
Click to expand...
Click to collapse
I currently don't have access to a PC that i can use to flash my phone via odin, im at college currently, which is more only access to the internet being as my phone isnt working, everything i would flash would be done with CWM, so right now, all i have to work with is N.E.A.K ics kernel,Siyah ICS v3.1 rc6 and GB 2.1.4 Kernel, HyDrOG3N 18/04 and CM7 nightly 116 which is a real pain in the ass, ill still have a go at formatting my system partition and dualboot etc. though
Thanks
Beans
bbeanss said:
I currently don't have access to a PC that i can use to flash my phone via odin, im at college currently, which is more only access to the internet being as my phone isnt working, everything i would flash would be done with CWM, so right now, all i have to work with is N.E.A.K ics kernel,Siyah ICS v3.1 rc6 and GB 2.1.4 Kernel, HyDrOG3N 18/04 and CM7 nightly 116 which is a real pain in the ass, ill still have a go at formatting my system partition and dualboot etc. though
Thanks
Beans
Click to expand...
Click to collapse
Have u tried flashing stock cm9 kernel? I faced that issue. Happened on mine due to a change in build.prop file permission. I guess it was caused my LCD Density Changer
Sent from my GT-I9100 using xda premium
override182 said:
Have u tried flashing stock cm9 kernel? I faced that issue. Happened on mine due to a change in build.prop file permission. I guess it was caused my LCD Density Changer
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
hey, i havent got access to download the stock ics kernel as it stands, the only way i was able to download and flash Kernels/recoveries/roms was through my phone as my pc was stolen a while back and havent gotten enough money together to get a new one yet, because im at college i cant download anything that isnt coursework related without being kicked off my course, my teacher is turning a blind eye to me being on here because hes got a HTC sensation xl
Beans
You could purchase mobile odin off the market, and data limit allowing, download the cm9 ressurection edition (ie cm9 flashable through odin). that would be my best advice
^ cause you wouldn't need a pc then
DreadPirateDan said:
You could purchase mobile odin off the market, and data limit allowing, download the cm9 ressurection edition (ie cm9 flashable through odin). that would be my best advice
^ cause you wouldn't need a pc then
Click to expand...
Click to collapse
Cheers, ill give it a go on my lunch break, ill have to find an open wifi connection somewhere
Beans
the best way is full wipe
reza1reza1 said:
the best way is full wipe
Click to expand...
Click to collapse
Already tried full wipe mate, no cigar, still no signal :/
Beans
Hi there,
i tried a lot of word combinations to get a thread with my specific problem but i didnt manage it to find one.
So here is the deal:
i have german galaxy s 2 (9100, bought in september 2011) and i flashed it last year with darkyrom HD something gingerbread-style.
so it was rooted and all that stuff.
it worked pretty fast and it was stable and it looked sleak.
Last year in November i put Ressurrection remix 3.x (dont know which version of it) on my phone.
It had a lot of crashes, freezes and while playing ingress it always drained around 20% of the battery within 10-20minutes.
So i stopped it. I put the last version of it 3.1.3. of it onto my phone with a full wipe, cache partition, factory reset onto my phones and the problems went keep going.
As an example:
-I couldnt access options where i can select ringtones or to see what is on the sd. it crashed and went back to the "main screen".
-Yesterday i tried around 15 roms, and nearly everything except militant rom keep crashing while iam installing them.
-Sometimes it crashes already while iam installing the rom, sometimes its after a couple of hours, that i cant access the rom any more.
-The newest problem is, that sometimes the power button doesnt respond, when i push it (in jelly bam)
Please explain, what iam missing or is my phone just broke?
It never fell down, no water or anything freaking other things.
I hope you can help me.
should i send it back or what is wrong?
i dnt knw bt samsung.. bt may b it happens coz of when ur changing ur rom gb to i cs or jb whole operating system is diff so u hav to format ur sd card to make it working.
Try that way too
Sent from my Xperia Neo V using xda app-developers app
Try changing kernel
Sent from my GT-i9100
sreehari.007 said:
i dnt knw bt samsung.. bt may b it happens coz of when ur changing ur rom gb to i cs or jb whole operating system is diff so u hav to format ur sd card to make it working.
Try that way too
Sent from my Xperia Neo V using xda app-developers app
Click to expand...
Click to collapse
so what do i have to do to make it work flawlessly?
i cant boot it right now without the power plug.... and the battery is at 90%....
so something is completely broken within the system....
jootanen said:
Try changing kernel
Sent from my GT-i9100
Click to expand...
Click to collapse
i thought the kernel is already included when you're installing one of the roms?
which one should i take?
or how wipe the whole system to have it like "out of the box"?
flash a stock ROM and see how it behaves.
Sent from the little guy
Sakujou_Kei said:
i thought the kernel is already included when you're installing one of the roms?
which one should i take?
or how wipe the whole system to have it like "out of the box"?
Click to expand...
Click to collapse
if you are rooted, you can try flashing NeatROM lite 4.2 based on LS8 and see how it behaves else flash official JB 4.1.2 using odin.
kmaq said:
if you are rooted, you can try flashing NeatROM lite 4.2 based on LS8 and see how it behaves else flash official JB 4.1.2 using odin.
Click to expand...
Click to collapse
ok, ill try that right now..
if not using odin and try to do something with my nand???
after cleaning and putting a stock rom on it and afterwards rooting it with cwm still the same problem: boot loop or while the first installation, it crashes.
so what to do?
just hang around with the stupid official one?
If you did everything from Factory reset to changing kernel, and everything is still bad like that. I think that there's something with your phone's hardware.
Sakujou_Kei said:
ok, ill try that right now..
if not using odin and try to do something with my nand???
after cleaning and putting a stock rom on it and afterwards rooting it with cwm still the same problem: boot loop or while the first installation, it crashes.
so what to do?
just hang around with the stupid official one?
Click to expand...
Click to collapse
after flashing the ROM via odin, reboot into recovery, wip/factory reset and then go in to mount & storage, make sure system, data and sd cards (internal & external if any) are all mounted if not mount it and reboot.
kmaq said:
after flashing the ROM via odin, reboot into recovery, wip/factory reset and then go in to mount & storage, make sure system, data and sd cards (internal & external if any) are all mounted if not mount it and reboot.
Click to expand...
Click to collapse
well, i tried that. still nothing. it crashes or i have a bootloop.
so whats up with this phone?
so except the stock rom, where i can boot into it, all custom firmwares just crash or work for a while and then they'll crash.
i dont get this.
it started just days ago, now i dont even can use anything....
Sakujou_Kei said:
well, i tried that. still nothing. it crashes or i have a bootloop.
so whats up with this phone?
so except the stock rom, where i can boot into it, all custom firmwares just crash or work for a while and then they'll crash.
i dont get this.
it started just days ago, now i dont even can use anything....
Click to expand...
Click to collapse
just as an example, when i tried to put on the neatrom-lite on my phone, it crashes while iam selecting the country. and this is just 2-3seconds after booting into the fresh and new system.
something is completely ****ed up....
so right now, i have the militant rom on my phone, got booted up, but the power button doesnt work.... when the phone is on...
so everytime, when i want to switch of the screen, i have to wait, or take of the battery. and switching on is only possible with the home button.
whats wrong?
Given you have the same problems on stock, hardware problem. Back to stock, reset counter, send it in for warranty service (if you have warranty), if not, take it to local mobile repair shops.
reseting the counter... with stock? how to do that? i thought this is only possible with root? and i thought, as soon as i root, there is something already on the counter?
Sakujou_Kei said:
reseting the counter... with stock? how to do that? i thought this is only possible with root? and i thought, as soon as i root, there is something already on the counter?
Click to expand...
Click to collapse
You have two option. Either flash a custom kernel (siyah, for example), then reset the counter using triangle away app. Then flash a stock firmware using odin. This wont increase the counter.
Or, if you have a USB jig, flash an older bootloader (have to careful here), then simply plug in the jig.
Sent from my GT-I9100 using xda app-developers app
hey, i got the problem:
i transferred a few files between the sd card and the internal storage of my device, and i realised, that the device is not able to fully transfer the files. it says after 40-50% that its done. is there a flash the roms via ODIN? or how to do that? just put the rom.zip as PDA?
Sakujou_Kei said:
hey, i got the problem:
i transferred a few files between the sd card and the internal storage of my device, and i realised, that the device is not able to fully transfer the files. it says after 40-50% that its done. is there a flash the roms via ODIN? or how to do that? just put the rom.zip as PDA?
Click to expand...
Click to collapse
Unzip first.
I'd advice you to read about flashing with odin and watch a couple of videos on youtube before you put yourself up to it or else you're gonna have a bad flash, and that means trouble.
Sent from the little guy
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