Develop Bugs

[Q] What keeps happening to my phone??

So here's the situation and this is literally the 3RD time this phone has done this. I'll be on a ROM on my rooted unlocked galaxy nexus, and randomly I'll be opening my texts or contacts or something and my phone will reboot. No big deal right? But then it just boot loops. Endlessly. If I try to restore a nandroid from a different ROM, it'll get almost done then won't be able to restore /data. I know it's not a bad nandroid backup cuz I switch back and forth between them all the time. I can't flash any rom, it'll be a boot loop, can't restore a nandroid,so I always have to end up flashing a stock image and start from scratch again.
I've seen this problem before after it happened the first time and found that flashing stock img fix. I have two questions: Why does it do this randomly every month? It's like my bootloader goes MIA or something for no reason. What would cause it to do this and literally, almost once every 30 days?
Second question: Is this a stable phone? I'm coming from the nearly unbrickable Captivate and I've done some crazy stuff to that phone and always managed to recover it, a couple times when it shouldn't have even worked at all. But yet this thing breaks down almost every month. Didn't flash anything new, didn't flash anything incompatible, nothing. Everything was running smooth. Then all of a sudden reboot, boot loop, backups dead, roms on SD card are useless.
Can someone please fill me in on what's going on with this? lol this is my 5th rooted android phone, not a developer or a themer or anything, but I know quite a bit about what would cause a phone to do whatever. Any insight would be great. Thanks guys!

Wich roms are you trying? Wich rooting methods? Wich flashing method? Are you using adb and fastboot?
Edit: does the issue happens on stock?
So far my phone its rock solid stable and buttery smooth fast after 3/4 months
Galaxy Nexus AOKP m5 Franco kernel m3

It first happened on liquid rom. I rooted via Samsung gnex toolkit. It happened again on gummy 1.2.0 honestly I wasn't on stock long enough to see how stock ran lol I don't use adb or fastboot often. Just to root and recently, to flash a stock image every time this happens
Sent from my Galaxy Nexus using XDA

I'd try rooting properly by using fast boot and flashing a superuser.zip. It may be that the toolkit is not working properly and you have a bad recovery. Something is wrong if this is happening. Its not too hard...
Sent From My Sprint Galaxy Nexus via XDA Premium

Nexus probably bricked - HELP

hi guys, this is my problem. I'd really appreciate it, if somebode could help me here!
so, i got a galaxy nexus, rooted it and started flashing roms. A lot. Then i heard of "Android Boot Manager" (awesome app btw) and set it up like this: aokp - milestone5 as "original"-rom because i knew it would always work. then i heard of the "paranoid android"-rom (also awesome) and flashed/installed it over the BootManager. Now when i wanted to boot back to milestone5, it wouldn't let me and the app instead kept crashing. so i uninstalled it and reinstalled it from market and then it wouldn't even recognize that the original rom was milestone5. so i uninstalled it again and from now on, it's stuck on bootscreen everytime i turn on my nexus.
when i try to get into recovery mode, in comes the oh-so-famous odin mode with "downloading, don't turn off target". So all i want is to have a working phone again, so to say, a factory reset. i don't care if i lose my root or my data (made a backup), i just want to have my phone working again
Many thanks in advance for reading my "novel" i wrote up here..

I heard of this...
Something being wrong with boot manager if I remember correctly.
I'll update if I find the link.
Definitely not bricked, though.
And you're holding volume up AND down AND power, right?
Edit:
This MAY be relelvant.
But isn't how I remember the error...so I haven't exactly heard of this one.
http://rootzwiki.com/topic/24978-boot-manager-ugh/page__hl__+boot++manager

Thanks for replying, got it working again. I flashed the original factory image (4.0.4) again. Now I'm busy rooting again, but doesn't matter, my phone works again!
btw, can't really recommend BootManager at all. It's a nice idea, but it can fu** things horribly up

If u could get into recovery. U can browse to the boot manager folder. Inside it there's an update.zip folder. If u were to flash that it would boot up in your case, the aokp m5. You can read more about this on their official website.
Sent from my Galaxy Nexus using XDA

And the only rom so far that would mess up was paranoid if you check it would only show 1gb available..so in some way it wasn't mounting storage correctly but if you install paranoid as main phone rom it's fine.....you over reacted it was easy fix by going into recovery from the paranoid rom and flashing the aokp rom again.....but good you fixed it the app is great though you should try it again
I thought it was app to begin with but all other roms I tried worked fine miui, dianXin, cm9 , etc ...but for some reason paranoid would not mount sd right as an extra rom but was fine as phone rom
Sent from my Sprint Galaxy Nexus CDMA using Xparent ICS Blue Tapatalk 2

[Q] /Data partition possibly corrupt, Someone please help

In the past couple of weeks I had jedi 3.x rom installed on my i317 from att, with asylumcore kernel at 1.92ghz overclock and no fsync(). Had it fully themed from various theme mods around the forum and everything was running great till i found a AOSP lockscreen mod that i decided i really wanted to put on here. I flashed the mod and my phone would load up show the TW lockscreen for 1 second then reboot again over and over. I was stupid and did not make a backup before flashing the lockscreen. could not get phone to stop resetting w/o pulling battery. after flashing the new jedi rom and kernel my phone still continued to bootloop, but without ever getting to the bootanimation. I had a cm rom on the sd card that i kept to try on a "rainy day". after flashing that the phone was able to fully boot and was working but this rom is very buggy for me. i realized that i had forgot to format /data before or after flashing and thought this could be the issue. went into recovery and now every time i try to format it the recovery reboots. tried flashing teamwinrecovery and it only loads the splash image then a blank screen. So i went back into cm and used the app Rom Toolbox Pro to see if it could clear out all of /data, and mentioned that my version of cwm had to be done with rom manager but with the option to try anyway? i answered yes. phone booted into recovery and now automatically tries to clear /data but keeps rebooting and repeating the process. Now i can't flash anything becuase rom toolbox is automating the whole thing.
So I ask, does anyone please know of anyways that i can mount my phone to my computer for editing without being booted up into the rom or recovery? or is there a way to use Odin to somehow clear all the partitions so that i can start new?
Sorry for long post but right now my phone is a $650 brick.

U just answered ur own question.......odin bacjk to complete stock
Sent from my SAMSUNG-SGH-I317 using xda premium

I live outside of any major city and the only real internet i could get was through my phone via tethering. so i was on dialup to even write the previous post. But I went into town and borrowed the local restaurant's cable internet and downloaded the stock firmware and I believe everything is in working order

[Q] Any possible ways to unbrick a softbricked SGH-I747

So here's the deal,
My ATT Galaxy S3 is half dead, and by that I mean soft bricked and I still believe there is hope in fixing this thing. Here's the entire story, everything was fine before I updated to CM 10.1 via ClockworkMod Recovery. At the time I was running the stable CM10. So I grabbed a copy of GAPPS, The CM10.1 nigthly, and a lean kernel to help improve battery life. I did the factory reset setting in CWM, then flashed CM10.1, Gapps, then the kernel. Then I did the usual after you flash a kernel, clean the cache, dalvik cache, and fix permissions. When I rebooted, the Galaxy S III boot logo was purple and glitchy, and my thought was, "Oh nooooo I bricked my phone." I had a backup saved, but after that glitch, everything was gone, so I had no backup and now I was panicking. I put my ext sd card in my reader on my PC and put the stable CM10 zip file on it, so i flashed it in CWM. My phone booted up normally. But here's the catch, no keyboard. Everything worked fine except my keyboard which kept saying, "Android Keyboard(AOSP) has encountered and error" or something like that every few seconds and would disappear just as fast. But here's the even funnier catch, everything that was my phone was still there except in a folder called 0, and in that folder another folder called 0, and in that contained a 'snapshot' of my phone as it was. CWM would not read the backup folder, or any of the files. So then I put my phone in download mode and flashed the stock ICS Samsung/ATT Rom called I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 to try to revive my phone fresh. It passed in ODIN, and now it boots up like normal except it gets stuck on the last Samsung label of the boot animation with the notification light a solid blue. Any help would be so much appreciated, I know of nothing else to do but I believe this can be fixed.

Re: [Q] Any possible ways to unbrick a softbricked SHGI747
MeatwadGetTheHunniesG said:
So here's the deal,
My ATT Galaxy S3 is half dead, and by that I mean soft bricked and I still believe there is hope in fixing this thing. Here's the entire story, everything was fine before I updated to CM 10.1 via ClockworkMod Recovery. At the time I was running the stable CM10. So I grabbed a copy of GAPPS, The CM10.1 nigthly, and a lean kernel to help improve battery life. I did the factory reset setting in CWM, then flashed CM10.1, Gapps, then the kernel. Then I did the usual after you flash a kernel, clean the cache, dalvik cache, and fix permissions. When I rebooted, the Galaxy S III boot logo was purple and glitchy, and my thought was, "Oh nooooo I bricked my phone." I had a backup saved, but after that glitch, everything was gone, so I had no backup and now I was panicking. I put my ext sd card in my reader on my PC and put the stable CM10 zip file on it, so i flashed it in CWM. My phone booted up normally. But here's the catch, no keyboard. Everything worked fine except my keyboard which kept saying, "Android Keyboard(AOSP) has encountered and error" or something like that every few seconds and would disappear just as fast. But here's the even funnier catch, everything that was my phone was still there except in a folder called 0, and in that folder another folder called 0, and in that contained a 'snapshot' of my phone as it was. CWM would not read the backup folder, or any of the files. So then I put my phone in download mode and flashed the stock ICS Samsung/ATT Rom called I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 to try to revive my phone fresh. It passed in ODIN, and now it boots up like normal except it gets stuck on the last Samsung label of the boot animation with the notification light a solid blue. Any help would be so much appreciated, I know of nothing else to do but I believe this can be fixed.
Click to expand...
Click to collapse
This one should be easy, if you got a pass in ODIN, the hard part is over.
Go into stock recovery, wipe cache and perform factory reset. Reboot and report back. This generally fixes that bug. Its very common after an ODIN flash.
Sent from my SGH-I747 using xda app-developers app

RPelham said:
This one should be easy, if you got a pass in ODIN, the hard part is over.
Go into stock recovery, wipe cache and perform factory reset. Reboot and report back. This generally fixes that bug. Its very common after an ODIN flash.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Oh wow, thank you so much. That worked and everything is as it should be, just like when I got it out of the box. I thought I was screwed for a moment, I even had an upgrade and got a HTC One VX a couple days ago haha. Wow. Again, thank you. :highfive:

MeatwadGetTheHunniesG said:
Oh wow, thank you so much. That worked and everything is as it should be, just like when I got it out of the box. I thought I was screwed for a moment, I even had an upgrade and got a HTC One VX a couple days ago haha. Wow. Again, thank you. :highfive:
Click to expand...
Click to collapse
No problem at all =) Its pretty hard to completely brick your device unless you flash something made for a different phone lol. As long as your phone can see any signs of life (even a faint vibration), let us know and we are more than happy to help!
Sent from my SGH-I747 using xda app-developers app

I once spent four hours trying to hard brick a Galaxy S2 phone (science experiment).
I'd flash ROM's for other phones.
Kernel's.
Recoveries.
Took forever to finally hard brick it.

S.O.S. Phone is completely wiped only dowload mode and recovery work.
Okay so I think I kind of put myself in a sticky situation. I tried to flash a custom rom onto my phone but in the process deleted my modem file everything worked fine except for the fact that I couldnt make calls or text messages. Basically a $400 dollar multimedia device. At this point I just want to put my phone back to the way it was when I got it at the AT&T store. My phone model is SGH-i747 Galaxy S3 that came with JB 4.1.1 pre installed.

I once spent four hours trying to hard brick a Galaxy S2 phone (science experiment).
I'd flash ROM's for other phones.
Kernel's.
Recoveries.
Took forever to finally hard brick it.
Click to expand...
Click to collapse
Out of curiosity, how did you finally manage to brick it?
Sent from my Nexus 7 using xda app-developers app

solution
MeatwadGetTheHunniesG said:
So here's the deal,
My ATT Galaxy S3 is half dead, and by that I mean soft bricked and I still believe there is hope in fixing this thing. Here's the entire story, everything was fine before I updated to CM 10.1 via ClockworkMod Recovery. At the time I was running the stable CM10. So I grabbed a copy of GAPPS, The CM10.1 nigthly, and a lean kernel to help improve battery life. I did the factory reset setting in CWM, then flashed CM10.1, Gapps, then the kernel. Then I did the usual after you flash a kernel, clean the cache, dalvik cache, and fix permissions. When I rebooted, the Galaxy S III boot logo was purple and glitchy, and my thought was, "Oh nooooo I bricked my phone." I had a backup saved, but after that glitch, everything was gone, so I had no backup and now I was panicking. I put my ext sd card in my reader on my PC and put the stable CM10 zip file on it, so i flashed it in CWM. My phone booted up normally. But here's the catch, no keyboard. Everything worked fine except my keyboard which kept saying, "Android Keyboard(AOSP) has encountered and error" or something like that every few seconds and would disappear just as fast. But here's the even funnier catch, everything that was my phone was still there except in a folder called 0, and in that folder another folder called 0, and in that contained a 'snapshot' of my phone as it was. CWM would not read the backup folder, or any of the files. So then I put my phone in download mode and flashed the stock ICS Samsung/ATT Rom called I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 to try to revive my phone fresh. It passed in ODIN, and now it boots up like normal except it gets stuck on the last Samsung label of the boot animation with the notification light a solid blue. Any help would be so much appreciated, I know of nothing else to do but I believe this can be fixed.
Click to expand...
Click to collapse
There's another thread called stuck on boot screen with same issue. Had same issue with simular Rom had to boot in recovery and clear cache and user settings. And no longer an issue

Soft bricked...
I'm currently dealing with a soft brick that I can't unbrick either. Got a replacement Sgh-i747 thru insurance. Rooted and decided to try twrp instead of cwm. Went to flash the ROM and didn't realize twrp didn't read ext SD cards until after i wiped my phone and OS. Tried reverting back to stock but Odin fails on the stock firmware every time. Tried flashing cwm and flashing a ROM but keep getting error 7 and no Roms flash. Any ideas as to where to start over with?

kinjo1023 said:
I'm currently dealing with a soft brick that I can't unbrick either. Got a replacement Sgh-i747 thru insurance. Rooted and decided to try twrp instead of cwm. Went to flash the ROM and didn't realize twrp didn't read ext SD cards until after i wiped my phone and OS. Tried reverting back to stock but Odin fails on the stock firmware every time. Tried flashing cwm and flashing a ROM but keep getting error 7 and no Roms flash. Any ideas as to where to start over with?
Click to expand...
Click to collapse
I think I did someting like that too nd now I cant install any ROM and TWRP complains that I have no OS inside the phone.I tried modifying the assert-script file but it then eventually ends up at STATUS 6 and not status 7 again.Pls and Pls help us

You have to be on twrp 2.7.x to install any kk ROMs.
Sent from my SGH-I747 using Tapatalk

[Q] CyanogenMod 10.1.3 on Rogers not showing internal SDcard files?

Ok, so I'm attempting to go from stock to CM 10.1.3, but I'm running into an odd issue. Note - I'm not a newbie to installing ROMS, having done so with my old Captivate quite regularly, but I *am* a newbie to installing them on my S3.
So, the issue is this: I am rooted, CWM (6.0.3.7) is installed, I have everything backed up with the latest version of TitaniumBackup Pro, and had it create a zip file so I could install it from CWM after doing the CM install (and I do a Nandroid backup as well). I install CM 10.1.3, install GAPPS, and install TitaniumBackup from CWM. I boot up CM, load up TitaniumBackup (sometimes I have to boot into CM first, go through setup, and THEN reboot to Recovery in order to get TitaniumBackup installed properly), and TitaniumBackup can't see *any* of the files in my internal SD card. Then I check with the file browser, and sure enough, it can't see *any* of my pre-CM files either. All of the folders are there, (not just stock file folders, but ones that I've created) but it can't see any files within those folders. I also can't see any of the files when I browse through USB on my computer, but all the folders are there. Has anybody experienced something like this? Is there something really simple and stupid that I'm missing/should be checking for?
Here's my setup, pre-CM install:
Rogers Galaxy S3 (i747M)
Android 4.1.2
Baseband I747MVLDMF1
Build number JZO54K.I747MVLDMF1
I rooted and installed CWM via the method in this thread (though I got the AT&T s3 version of CWM directly from the CWM page instead of using either of the ones linked in that thread).
Any help here would be greatly appreciated. I'm tired of the stock JB that Rogers provides, and wanted to give CM a chance, but not being able to see any of the files on my SD card is frustrating me, and making me leery of keeping the install there. Worst case scenario, I can install it, format the internal SD card, and then copy everything back over from my computer via USB, but that is a REAL hassle and I'd still be left wondering if there was something else broken.
Thanks!

Also: I do a standard wipe/factory reset before installing CM. When I restore my Nandroid backup, all is back to normal. I *did* google to see if anybody else had the same problem, but my google fu has failed me. Umm, I can't think of any other pertinent information I could offer.

http://forum.xda-developers.com/showthread.php?t=2274218
Try this...:good:

DMF1977 said:
http://forum.xda-developers.com/showthread.php?t=2274218
Try this...:good:
Click to expand...
Click to collapse
Perfect! I'll try that tonight. Thanks muchly! :good:

Upon further messing about, I've found that it's still a bit flaky/unreliable. Apps randomly crashing, files and folders inaccessible and/or not visible despite being in /data/media/0, etc etc. Decided just to go back to stock for now, I'll take another stab at it some other time.