A couple of months back I was using Carbon 4.4 on my phone. I realized that I grabbed the wrong model number and install an galaxy s3.
Everything was working fine for a while before I knew that I messed up. Then one day app started messing up and that when I saw that it was wrong. I tried flashing the Note 2 version of the ROM and got stuck in a boot loop. Which resulted in a battery pull and booting back into recovery. Only SlimKat has worked for me now. Carbon, Liquid Smooth, Pac Man don't work. They all get stuck in booting image and spin forever.
Is there anything I can do to get these roms working again?
superdusto said:
A couple of months back I was using Carbon 4.4 on my phone. I realized that I grabbed the wrong model number and install an galaxy s3.
Everything was working fine for a while before I knew that I messed up. Then one day app started messing up and that when I saw that it was wrong. I tried flashing the Note 2 version of the ROM and got stuck in a boot loop. Which resulted in a battery pull and booting back into recovery. Only SlimKat has worked for me now. Carbon, Liquid Smooth, Pac Man don't work. They all get stuck in booting image and spin forever.
Is there anything I can do to get these roms working again?
Click to expand...
Click to collapse
Would flashing it to stock via odin fix any errors I might have created?
Yeah, typically if you Odin back to stock, and reroot. Choose the correct package though, don't want 4.3 Odin, or you end up locked tight.
Sent from my SCH-I605 using Tapatalk
JeramyEggs said:
Yeah, typically if you Odin back to stock, and reroot. Choose the correct package though, don't want 4.3 Odin, or you end up locked tight.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Do you have a recommended one?
Related
so i succesfully put aokp on my friends fascinate, it booted fine, worked for like 3 months. today, i booted into recovery, nandroided, then rebooted into system and it worked fine. but later, i rebooted back into recovery, did nothing, then tried to boot back into system, but it just booted back into recovery. i tried restoring from the nandroid i made earlier, still no luck, tried flashing another rom, kept booting right back into recovery... i have no idea what the problem is. has anyone else had this and is there any way to fix it without odin as i dont have a windows handy?
Did you three-finger into recovery the second time? If you did, this is a known issue. You can't three-finger into CWM on MTD filesystems (CM7 or ICS) or you will bootloop. See Droidstyle's guide in the General section for instructions on how to escape.
I would seriously update your friends phone as a lot has changed with all the roms in 3 months. Heck, a lot happens in 3 weeks.
Sent from my SCH-I500 using Tapatalk
shelby04861 said:
I would seriously update your friends phone as a lot has changed with all the roms in 3 months. Heck, a lot happens in 3 weeks.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
bingo.....
I finally bricked my first phone.Its been a long ride but it caught up to me. I have had three different android phones within about 4 years and have successfully rooted all three myself and have successfully flashed them over and over close to 1000 times between all three phones including modems, kernals, gapps, themes etc. So what gives? Why today? To be honest I don't know. But here is what happened...
The past few days I have been going back and forth between different kernals for this device to try to get something that won't freeze up. ( I liked browsing on this phone but I would get freeze ups and therefore would flash something new to try and resolve it.) Today my phone froze so I tried a simple reboot. The boot then did a freeze on the kernal's "intro" picture. It wasn't a bootloop it just frooze. (I was on XWLPT with Skyfire Kernal). I decided to reboot into recovery and flash a different kernel. I flashed NEAK The flash went halfway then stuck and froze. I rebooted to try to get back to the phone's main screen. This time it would not boot. I couldn't tell if it was in bootloop or was froze. I went back into recovery. Here I should of wiped everything but in the back of my mind I thought I could just do it in odin if I lost recovery. So I tried flashing Siyah for sammy roms. This is when I lost everything. It froze in cmw on the flash again but this time when I tried going back into recovery it stayed on the Galaxy SII screen. So I put the phone in download mode and started Odin up. When trying to flash anything in Odin I got stuck on nand write start! I never heard of this. I thought Odin would work as this is how I rooted the phone when I first got it. Last thing I did was install kies which couldn't even connect to the phone. So all I am left with is download mode and taking way more caution when flashing. I think it may have been a case of the brickbug. Even though I was on a I9100 rom and using "safe" kernels I believe something happened to lock me out from writing anything to the phone.
U already posted this in another thread. I posted a response there for ya
Sent from my SGH-I777 using Tapatalk 2
Sad.
I got my galaxy s2 bricked twice
Double posting is no bueno.:thumbdown:
Sent from my SGH-i777 using XDA
anup123456 said:
I got my galaxy s2 bricked twice
Click to expand...
Click to collapse
Not really related.. (Yes I know my post isn't related either)
I bricked my sgs2 not to long ago At&t could not fix so in one last attempt I tried to flash back to Pics stock it took some time but finally recoverd using odin
Sent from my SGH-I777 using xda premium
VICIOUSVIC1 said:
I bricked my sgs2 not to long ago At&t could not fix so in one last attempt I tried to flash back to Pics stock it took some time but finally recoverd using odin
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
what's pics stock?
Sent from my SGH-I777 using xda premium
Phalanx7621 said:
what's pics stock?
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Pics stock is when you're typing and not paying attention then the auto complete changes pics stocks to pics stock. Got it?
Revert to stock using Odin and download mode probably or the guys and (sorry if I hurt anyone's feelings) but the guys at mobile tech videos offer a service to unbrick your phone.
Sent from my GT-I9100 using xda app-developers app
bocephus007 said:
Revert to stock using Odin and download mode probably or the guys and (sorry if I hurt anyone's feelings) but the guys at mobile tech videos offer a service to unbrick your phone.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Yeah I know . But its just a front man! They receive the bricked device, then send it to some Chinaman named Finchenzo. And he fixes em all and sends em back to mobile tech! Then you get your device back! Poor Finchenzo
Sent from my SGH-I777 using Tapatalk 2
paulfrankie said:
I finally bricked my first phone.Its been a long ride but it caught up to me. I have had three different android phones within about 4 years and have successfully rooted all three myself and have successfully flashed them over and over close to 1000 times between all three phones including modems, kernals, gapps, themes etc. So what gives? Why today? To be honest I don't know. But here is what happened...
The past few days I have been going back and forth between different kernals for this device to try to get something that won't freeze up. ( I liked browsing on this phone but I would get freeze ups and therefore would flash something new to try and resolve it.) Today my phone froze so I tried a simple reboot. The boot then did a freeze on the kernal's "intro" picture. It wasn't a bootloop it just frooze. (I was on XWLPT with Skyfire Kernal). I decided to reboot into recovery and flash a different kernel. I flashed NEAK The flash went halfway then stuck and froze. I rebooted to try to get back to the phone's main screen. This time it would not boot. I couldn't tell if it was in bootloop or was froze. I went back into recovery. Here I should of wiped everything but in the back of my mind I thought I could just do it in odin if I lost recovery. So I tried flashing Siyah for sammy roms. This is when I lost everything. It froze in cmw on the flash again but this time when I tried going back into recovery it stayed on the Galaxy SII screen. So I put the phone in download mode and started Odin up. When trying to flash anything in Odin I got stuck on nand write start! I never heard of this. I thought Odin would work as this is how I rooted the phone when I first got it. Last thing I did was install kies which couldn't even connect to the phone. So all I am left with is download mode and taking way more caution when flashing. I think it may have been a case of the brickbug. Even though I was on a I9100 rom and using "safe" kernels I believe something happened to lock me out from writing anything to the phone.
Click to expand...
Click to collapse
Send it to MobileTechVideo.com. I sent my bricked SG2 in and a week later and at a cost of only $50, it was returned fully functional.
Sent it to MTV. Mobile Tech Video said this...The device's onboard EMMC controller was in a non-responsive state.
I never flashed anything that wasn't specifically made to be flashed for an i777.
Everything I had ever flashed was on the i777 development thread.
My advice ...beware of the brickbug. Also don't flash anything when the phone is hot. This happened when my phone was hot and maybe a reason why it froze while flashing in cwm.
And for a recap... What did you flash right before tie happened and what were you coming from?
Clay
Team Pirate
Sent from my PINK SGH-I777
Specifically the rom booted fine with Shostock-XWLPT. When using the rom sometimes it would freeze up so I flashed NEAK kernal over it. Froze in cmw during halfway through the flash.Rebooted after about 5 minutes wating for cmw to finish. (it never did) Phone bootlooped. Pressed hardbuttons to get to recovery. Recovery worked went into NEAK cwm. Instead of wiping and starting fresh here decided I would take a shortcut and flashed a Siyah for i777 over that. CWM froze again halfway through flashing the Siyah. After waiting 5 minutes again decided to reboot. Phone bootlooped. No more hardbutton recovery. Phone bricked. I Can still go into download mode but even MTV could not unbrick it. Said EMMC controller was in unresponsive state. Don't know what that means but know its now a paperweight.
Got it back today I still can get into download mode. Odin will recognize phone. When I try to flash a kernal it follows through until right before it actually writes and says NAND Write Start. I believe the internal memory either is filled with bad sectors or someting like brickbug locked anything from writing to EMMC.
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
Ok, been away from the note 2 for a min. Anyone want to give me the low down on all this 4.3 stuff? I'm seeing roms say that MJ9 has to be flashed in Odin before a the rom can be flashed? Is this a one time deal or does it have to be done every time I want to flash a tw rom? Do I have to do anything to go back to an aosp rom? I'm sure I could figure all this out on my own but I'm impatient. Lol. TIA
Sent from my SCH-I605 using Tapatalk
KBizzle said:
Ok, been away from the note 2 for a min. Anyone want to give me the low down on all this 4.3 stuff? I'm seeing roms say that MJ9 has to be flashed in Odin before a the rom can be flashed? Is this a one time deal or does it have to be done every time I want to flash a tw rom? Do I have to do anything to go back to an aosp rom? I'm sure I could figure all this out on my own but I'm impatient. Lol. TIA
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
You have to flash MJ9 firmware that has the tz, params and modem in it.. This allows wifi to work.. then flash away! Just do not flash MJ9 official OS KIES bc you'll lock your bootloader..
Once your done flashing the firmware you can flash in between roms no problem doesn't matter what version,4.1.2, 4.3 or aosp 4.4.2:good:
Edit: here's the thread http://forum.xda-developers.com/showthread.php?t=2578458
lacoursiere18 said:
You have to flash MJ9 firmware that has the tz, params and modem in it.. This allows wifi to work.. then flash away! Just do not flash MJ9 official OS KIES bc you'll lock your bootloader..
Once your done flashing the firmware you can flash in between roms no problem doesn't matter what version,4.1.2, 4.3 or aosp 4.4.2:good:
Edit: here's the thread http://forum.xda-developers.com/showthread.php?t=2578458
Click to expand...
Click to collapse
Thank you. It's been a while.
Sent from my SCH-I605 using Tapatalk
Alright, got one more question. So I thought I had bricked my phone last night. Accidentally flashed an S4 stock rom. I know, dumb. Anyway, after 3 hours of trying to Odin multiple stock roms, I finally got one to take and the phone booted. So I immediately went and used casual to root the device. Everything went fine there. I went ahead and updated TWRP to the latest and proceeded to flash aokp. It locked up at the boot animation. So I then tried to flash a 4.1.2 tw rom. This is where it got weird. It flashed fine but then it never booted. Just a black screen after the Samsung splash screen. I then decided to try and Odin a rooted 4.1.3 rom. Still nothing. So last ditch effort I odin'd the pit file. Back in business on an unrooted tw rom. Now when I try to use casual, it won't download the proper driver to root again. Gives a perpetual error and requests the driver be installed over and over until I pull the USB cable. Is there something I'm missing?
Sent from my SCH-I605 using Tapatalk
Try this. With the phone booted, go into device manager on your computer and uninstall the driver. Then boot the phone into download mode and uninstall the driver for it in device manager. Boot phone back up and try casual again. Also make sure your Antivirus is off before you run casual.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Soooo.... I rooted my Samsung Galaxy S4 (SCH-I545), then I decided to install a custom ROM since the default TouchWiz rom is slower than a turtle stuck in a pile of wax. I installed Safestrap 3.71 (TWRP v2.6.3.1) and by mistake flashed my stock rom. Now my phone won't boot into any ROM since that is corrupt, but it still boots into recovery (that's a good thing I suppose). I have tried a number of Safestrap compatible roms (omni, cm, beanstalk) but they either end up giving me a black screen or a very weird looking pixelated blue/cyan screen. I have to remove the battery to reboot my phone. I tried using adb to wipe the data aswell but nothing works beyond recovery.
I have to rely on adb to push and pull data to and from the phone.
I was hoping if anyone had any idea what I should try to do next?
Probably best just to restart by flashing the stock firmware back to it with Odin.
Make sure you don't try to downgrade the firmware vs what you have now, as that can create a lot more issues than you want to deal with.
Snake2k said:
Soooo.... I rooted my Samsung Galaxy S4 (SCH-I545), then I decided to install a custom ROM since the default TouchWiz rom is slower than a turtle stuck in a pile of wax. I installed Safestrap 3.71 (TWRP v2.6.3.1) and by mistake flashed my stock rom. Now my phone won't boot into any ROM since that is corrupt, but it still boots into recovery (that's a good thing I suppose). I have tried a number of Safestrap compatible roms (omni, cm, beanstalk) but they either end up giving me a black screen or a very weird looking pixelated blue/cyan screen. I have to remove the battery to reboot my phone. I tried using adb to wipe the data aswell but nothing works beyond recovery.
I have to rely on adb to push and pull data to and from the phone.
I was hoping if anyone had any idea what I should try to do next?
Click to expand...
Click to collapse
Have you cleared cache?
If you are not able to flash a custom rom, I would recommend you to flash a stock rom and begin from new. Also if you are on Android 4.4 you cannot use any recovery.
Sent from my GT-I9505 using XDA Premium 4 mobile app
es0tericcha0s said:
Probably best just to restart by flashing the stock firmware back to it with Odin.
Make sure you don't try to downgrade the firmware vs what you have now, as that can create a lot more issues than you want to deal with.
Click to expand...
Click to collapse
I'm just gonna give the Hyperdrive ROM a go, if that doesn't work, I'll definitely just go back to Stock I suppose and see what happens next. Thanks!
ikuni123 said:
Have you cleared cache?
If you are not able to flash a custom rom, I would recommend you to flash a stock rom and begin from new. Also if you are on Android 4.4 you cannot use any recovery.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep I cleared everything, weird problem lol. Its not 4.4 cus Verizon never released any for their S4s, but I'll definitely just head back to stock after I give Hyperdrive a chance Thanks!
Snake2k said:
I'm just gonna give the Hyperdrive ROM a go, if that doesn't work, I'll definitely just go back to Stock I suppose and see what happens next. Thanks!
Yep I cleared everything, weird problem lol. Its not 4.4 cus Verizon never released any for their S4s, but I'll definitely just head back to stock after I give Hyperdrive a chance Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2634408
According to that, only 13 is supported. I dunno if the that thread hasn't been updated or whatever, but something to consider.