Continuous reboots, device is almost a brick... Can you help me? - Samsung Galaxy Nexus

Hi guys,
I had already suffered in the past for sudden reboots, but at least i was able to use the phone for a decent amount of time and fix it. After last night, though, the situation seems desperate. When i woke up i was able to turn off the alarm clock, check my email, but then hell started...
My phone is a gsm Nexus (maguro i9250), with CyanogenMod11 snapshot M5 and the appropriate google apps (at least they were appropriate about 1 month ago). I recently had some minor issue with the Google+ app, after it was updated: it kept crashing, until i uninstalled it and reinstalled after downloading from the Play Store. Should i instead search for a newer gapps packet?
Now the situation is pretty awful. The phone will reboot after at most 2 minutes. I don't really know what makes it crash so bad.
I also have two weird problems. Whatever change i manage to make before the phone reboots doesn't get persisted. For example, the alarm clock will always start activated, no matter if i managed to deactivate it before the reboot.
I'm also not able to reset it to factory defaults. I am using ClockworkMod 6.0.4.7. If i try the reset procedure, the /data and /cache partitions are formatted, but not the sdcard one. Indeed, i get the following output:
Code:
Formatting /data
Formatting /cache
Formatting /sd-ext
E: unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure
Data wipe complete
When i reboot the phone after this procedure, everything is still there, and the phone will keep doing its reboots after 1-2 minutes.
What can i do? Is there an hardware way to hard-reset the phone? Is there a program i could use?
Thanks in advance!

Fried EMMC (memory)
Sent from my Galaxy Nexus using XDA Free mobile app

mrgnex said:
Fried EMMC (memory)
Click to expand...
Click to collapse
Maybe, but if everything is still there after a reboot, sounds doubtful.
Have you tried installing a different rom? Can you connect via adb? Do you have a nandroid?

Format /system under Mounts and Storage in CWM and reflash ROM and GApps?

Hi guys, thanks for your replies! Sorry for the late answer, i was pretty busy.
I spent last night trying everything i could, but i think my phone is gone
I used Skipsoft's Android Toolkit and Odin, with no success.
The first one seemed to succeed: i tried twice, with two different stock roms, but i always ended up with the same CM11, same apps, same everything.
Odin always failed (i tried at least 3 times, i honestly lost the count).
I did find a post in the forums regarding a guy with my same problem, and he was told about the eMMC as well. I am pretty sure that is my problem as well.
Further proofs of that:
1) I downloaded the latest CM11 nightly build, was able to push its zip file on the device using Eclipse (i swear it was there), but when i tried to flash it using CWM, the file wasn't there.....
2) With Android Toolkit i was able to boot into a different recovery tool (TWM, i think). I wiped everything with it, and i was starting to hope.... but the same darn CM11 appeared!
I don't have a nandroid, i formatted everything i could in Mounts in CWM (i got to a point that i formatted everything that was formattable). I also tried to reflash the rom and gapps. No luck, always ended up with the same situation.
I didn't really try a different rom. I didn't try to connect using adb on the terminal, but i think that Eclipse is based on that, so i think adb is working.
Oh well... Right now i'm using an old phone, but i have started looking for a new one, i am tempted by the Nexus 5

frabena said:
Hi guys, thanks for your replies! Sorry for the late answer, i was pretty busy.
I spent last night trying everything i could, but i think my phone is gone
I used Skipsoft's Android Toolkit and Odin, with no success.
The first one seemed to succeed: i tried twice, with two different stock roms, but i always ended up with the same CM11, same apps, same everything.
Odin always failed (i tried at least 3 times, i honestly lost the count).
I did find a post in the forums regarding a guy with my same problem, and he was told about the eMMC as well. I am pretty sure that is my problem as well.
Further proofs of that:
1) I downloaded the latest CM11 nightly build, was able to push its zip file on the device using Eclipse (i swear it was there), but when i tried to flash it using CWM, the file wasn't there.....
2) With Android Toolkit i was able to boot into a different recovery tool (TWM, i think). I wiped everything with it, and i was starting to hope.... but the same darn CM11 appeared!
I don't have a nandroid, i formatted everything i could in Mounts in CWM (i got to a point that i formatted everything that was formattable). I also tried to reflash the rom and gapps. No luck, always ended up with the same situation.
I didn't really try a different rom. I didn't try to connect using adb on the terminal, but i think that Eclipse is based on that, so i think adb is working.
Oh well... Right now i'm using an old phone, but i have started looking for a new one, i am tempted by the Nexus 5
Click to expand...
Click to collapse
You can try by downloading a clean google factory image and then flash it using bootloader and see it helps, it could be a bad script inside. If this doesn't help then you should totally get the Nexus 5. I got GNex only recently and its still a good device I reassure you. A little tweak and a little overclock makes it as good as a stock N4 minus the bad graphics.

frabena said:
Hi guys, thanks for your replies! Sorry for the late answer, i was pretty busy.
I spent last night trying everything i could, but i think my phone is gone
I used Skipsoft's Android Toolkit and Odin, with no success.
The first one seemed to succeed: i tried twice, with two different stock roms, but i always ended up with the same CM11, same apps, same everything.
Odin always failed (i tried at least 3 times, i honestly lost the count).
I did find a post in the forums regarding a guy with my same problem, and he was told about the eMMC as well. I am pretty sure that is my problem as well.
Further proofs of that:
1) I downloaded the latest CM11 nightly build, was able to push its zip file on the device using Eclipse (i swear it was there), but when i tried to flash it using CWM, the file wasn't there.....
2) With Android Toolkit i was able to boot into a different recovery tool (TWM, i think). I wiped everything with it, and i was starting to hope.... but the same darn CM11 appeared!
I don't have a nandroid, i formatted everything i could in Mounts in CWM (i got to a point that i formatted everything that was formattable). I also tried to reflash the rom and gapps. No luck, always ended up with the same situation.
I didn't really try a different rom. I didn't try to connect using adb on the terminal, but i think that Eclipse is based on that, so i think adb is working.
Oh well... Right now i'm using an old phone, but i have started looking for a new one, i am tempted by the Nexus 5
Click to expand...
Click to collapse
Well I got bad news well not really bad but kinda. If you wiped efs data while you were wiping your phone will never properly connect to the network anymore. That obviously won't matter unless you somehow get out of this bootloop.

Related

[Q] Cyanogen 10.1 mod gone wrong.

AT&T Galaxy S3
Mac OSX 10.8
I know I can get my device back, I'm just not sure how. I successfully rooted using CASUAL, no problems there. Got the normal root applications installed, did the Clockwork backup, everything was great.
I then decided to try a custom ROM - the Cyanogen 10.1. It downloaded fine, and I selected to also install Google Apps, then it rebooted and the Cyanogen boot screen with the spinning circle came up. However, this lasted way longer than I thought it should, so I looked it up, and what I got from the research is that I had the wrong gapps on there.
So, I followed the instructions in this thread (same problem as me), and wiped the system. However, I believe I used the wrong list item, and now everything I had is gone. I can't boot from recovery because it doesn't exist, and when booting into CM I just get the same error message that setup has stopped working. I thought maybe I could put a new ROM on the sd card or phone harddrive and boot from that, but both are inaccessible through USB on my Mac.
I can get it into ODIN mode (where it says "Downloading... Do not turn off target!"), which I'm thinking is what I want, and I have Heimdall installed and it runs and recognizes my device, but I cannot for the life of me find a tar.gz file to use.
If anyone can offer any sort of help, I would super appreciate it.
chazbot7 said:
AT&T Galaxy S3
Mac OSX 10.8
I know I can get my device back, I'm just not sure how. I successfully rooted using CASUAL, no problems there. Got the normal root applications installed, did the Clockwork backup, everything was great.
I then decided to try a custom ROM - the Cyanogen 10.1. It downloaded fine, and I selected to also install Google Apps, then it rebooted and the Cyanogen boot screen with the spinning circle came up. However, this lasted way longer than I thought it should, so I looked it up, and what I got from the research is that I had the wrong gapps on there.
So, I followed the instructions in this thread (same problem as me), and wiped the system. However, I believe I used the wrong list item, and now everything I had is gone. I can't boot from recovery because it doesn't exist, and when booting into CM I just get the same error message that setup has stopped working. I thought maybe I could put a new ROM on the sd card or phone harddrive and boot from that, but both are inaccessible through USB on my Mac.
I can get it into ODIN mode (where it says "Downloading... Do not turn off target!"), which I'm thinking is what I want, and I have Heimdall installed and it runs and recognizes my device, but I cannot for the life of me find a tar.gz file to use.
If anyone can offer any sort of help, I would super appreciate it.
Click to expand...
Click to collapse
Your recovery shouldn't be affected by a wipe (unless you flashed something over it) as ROMs don't flash recovery, therefor vol up + home + power should get you in it. If you success to, You should be able to mount through recovery.
As for Heimdall, it just got S3 support (last week I believe), therefor it might not be easy to find a stock file for it. That being said, if you have access to any Windows pc, that'd be the easiest solution here (using Odin).
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.
BWolf56 said:
Your recovery shouldn't be affected by a wipe (unless you flashed something over it) as ROMs don't flash recovery, therefor vol up + home + power should get you in it. If you success to, You should be able to mount through recovery.
As for Heimdall, it just got S3 support (last week I believe), therefor it might not be easy to find a stock file for it. That being said, if you have access to any Windows pc, that'd be the easiest solution here (using Odin).
Click to expand...
Click to collapse
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.
chazbot7 said:
Yes, I can still get into the recovery menu, but when I use "backup and restore>restore" it says No files found. Is there anything I can do to just get a working OS running? Or am I just doing it totally wrong, I'm new to the rooting stuff. The Windows computer will be my last resort haha.
Click to expand...
Click to collapse
Windows pc is definitely the easiest option here but you try mounting your SD from recovery, redownload the ROM and Gapps you wanna use, put them on your device and flash them after a factory reset.
If you wiped your SD card, it's normal that you don't have a backup anymore.
BWolf56 said:
Windows pc is definitely the easiest option here but you try mounting your SD from recovery, redownload the ROM and Gapps you wanna use, put them on your device and flash them after a factory reset.
If you wiped your SD card, it's normal that you don't have a backup anymore.
Click to expand...
Click to collapse
It's aaaliiiiiiive! Grabbed an extra micro SD I had, threw Cyanogen 10.1.0 RC4 on it, and installed it just fine. Now updating to RC5. My only question now is how to get Google Apps on there. Does this need to be done beforehand, or can it be done after?
chazbot7 said:
It's aaaliiiiiiive! Grabbed an extra micro SD I had, threw Cyanogen 10.1.0 RC4 on it, and installed it just fine. Now updating to RC5. My only question now is how to get Google Apps on there. Does this need to be done beforehand, or can it be done after?
Click to expand...
Click to collapse
You usually flash the Gapps right after flashing the ROM, before rebooting.
P.S.: fully reading the instructions helps before flashing
Sent from my SGH-I747 using xda app-developers app
BWolf56 said:
You usually flash the Gapps right after flashing the ROM, before rebooting.
P.S.: fully reading the instructions helps before flashing
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Gotcha, sorry about that. Thanks for all the help good sir. This is actually way faster than my stock ROM, I'm pretty stoked on it, Google Apps or not.
chazbot7 said:
Gotcha, sorry about that. Thanks for all the help good sir. This is actually way faster than my stock ROM, I'm pretty stoked on it, Google Apps or not.
Click to expand...
Click to collapse
No need to apologize. Glad you got it back up! And it was mostly to keep you from making similar mistakes in the future
Sent from my SGH-I747 using xda app-developers app
also one thing you need to know
First boot after you flash will always take longer than normal. After that, it's fine

for anyone looking for twrp for t520 10.1 wifi only

It is auto loaded when you load flashify. Then u can select wether u want twrp or cw recovery.
Hope this helps someone as twrp. Wifi t520 is not available on twrp site.
+1 confirmed it worked on mine (t520).
Can also be retrieved here if you want to flash via Odin.
http://goo.im/devs/OpenRecovery/picassowifi
I fond myself in a situation where my tablet wouldn't boot and I needed to install a custom recovery, so I had to flash via Odin.
I was just going to post a thread about this. Flashify app is the easiest way I have ever used to install custom recovery!
More details?
All,
I rooted my 10.1 yesterday, since ROMS are starting to come out. I used TWRP and CWM on a Toshiba Thrive prior to own the tab pro.
Anyways...I rooted last night with Odin, but still only have the stock recovery.
Please tell me how to get TWRP installed, without messing up the tablet (it is an expensive device, just want to make sure I don't brick it!)
Just flash the zip from the stock recovery?
Unroot and re-root using flashify or Odin?
I can't wait to get rid of all the Samsung crap!!! (but want to backup first)
Thanks a lot,
Damien
Re twrp for t520 and roms
Wish there was some way to help young 14 year old ik4ver [written first custom rom for our device]...some deadbeat loser keeps sabotaging his account now hijacked to extort a rom for the 12.2!!! I have never seen anything like this...hopefully karma works her magic on this scumbag!
I know right...I fortunately got his v3 rom yesterday before his posts got hacked again.
Tried to flash his rom today and almost bricked the tab, twrp couldn't mount ./system. Got stuck on the Samsung logo after this. Fortunately after 3 tries my twrp backup finally restored properly.
Does anyone know the exact steps to follow in twrp before flashing his rom?
Before not being able to mount system, it was saying can't mount cache, which seems to have resolved itself. Weird...
Sent from my SM-T520 using Tapatalk
rom thread back up
Can't help yet ..I haven't had balls to flash rom yet lol. Looks like his rom thread is back up and running for now.
MrBungle67 said:
I know right...I fortunately got his v3 rom yesterday before his posts got hacked again.
Tried to flash his rom today and almost bricked the tab, twrp couldn't mount ./system. Got stuck on the Samsung logo after this. Fortunately after 3 tries my twrp backup finally restored properly.
Does anyone know the exact steps to follow in twrp before flashing his rom?
Before not being able to mount system, it was saying can't mount cache, which seems to have resolved itself. Weird...
Sent from my SM-T520 using Tapatalk
Click to expand...
Click to collapse
when u figure out can you post solution? would be helpfull
perhaps young ik4evr will surface with a suggestion.
MrBungle67 said:
I know right...I fortunately got his v3 rom yesterday before his posts got hacked again.
Tried to flash his rom today and almost bricked the tab, twrp couldn't mount ./system. Got stuck on the Samsung logo after this. Fortunately after 3 tries my twrp backup finally restored properly.
Does anyone know the exact steps to follow in twrp before flashing his rom?
Before not being able to mount system, it was saying can't mount cache, which seems to have resolved itself. Weird...
Sent from my SM-T520 using Tapatalk
Click to expand...
Click to collapse
I did...have balls
spton said:
Can't help yet ..I haven't had balls to flash rom yet lol. Looks like his rom thread is back up and running for now.
Click to expand...
Click to collapse
Yep...I tried again...
So, in order, I...
- Rooted using Odin
- Install TWRP using Flashify (thanks to K8108 for the earlier post)
- Went to recovery
- Went to "Mount" and made sure all was checked
- Went to "Wipe", "Advanced"
- Checked everything except internal and external storage
- Install ik4evr's ROM
- Rebooted...
Tablet booted no problem (it stays on "SAMSUNG" for a little bit, which worried me...)
All Samsung apps are gone!!!
that's awesome thanks for the procedure details!
Actually it was young ik4evr that let me know bout twrp being auto loaded in flashify .. that's why I started thread as it's kinda confusing as twrp site doesn't list t520 wifi only.
Good work!
spton said:
Actually it was young ik4evr that let me know bout twrp being auto loaded in flashify .. that's why I started thread as it's kinda confusing as twrp site doesn't list t520 wifi only.
Good work!
Click to expand...
Click to collapse
This all forum is freaking confsuing, as it is about 6 (8?) different devices, where some are kinda similar, and others completely different (thinking especially of Exynos vs Qualcomm).
Plus there is no real guide, and takes hours trying to figure out if this thread/recovery/rom applies to our device or not.
Plus 8.4 became modrian, and 10.1 picasso.
Yay, confusing is the right word!!!
well I've loaded Treo with flashify and done full stock rooted rom
Backup. Now have to grow a pair and flash ver3 of ik4evrs rom! So you have zero issues and everything working?
I was going to wait at least till his thread gets sorted out...hmmm...i voided warranty anyway at this point lol
MrBungle67 said:
This all forum is freaking confsuing, as it is about 6 (8?) different devices, where some are kinda similar, and others completely different (thinking especially of Exynos vs Qualcomm).
Plus there is no real guide, and takes hours trying to figure out if this thread/recovery/rom applies to our device or not.
Plus 8.4 became modrian, and 10.1 picasso.
Yay, confusing is the right word!!!
Click to expand...
Click to collapse
Treo = twrp
Dang spell correction!
spton said:
Backup. Now have to grow a pair and flash ver3 of ik4evrs rom! So you have zero issues and everything working?
I was going to wait at least till his thread gets sorted out...hmmm...i voided warranty anyway at this point lol
Click to expand...
Click to collapse
Zero issue wouldn't the word lol! I did have a bit of a cold sweat yeterday...
I'd say as long as you have the stock rom backup go for it!
I actually started a thread separated from here. I wonder if "wipe internal storage" ok or not...what I can see is that bunch of folders remained from apps installed before flashing the rom.
As far as the steps listed above, I just did it this morning and all went well. As far as deep testing to see if everything is still working, I can't answer yet (at work, no time to play with it).
Let me know if you have any issue...
Ball grown yet?
Alright...so:
- Went to recovery
- Went to "Mount" and made sure all was checked
- Went to "Wipe", "Advanced"
- Checked everything except external storage
- Install ik4evr's ROM
- Rebooted...
Just reflashed the rom, this time wiping the internal storage as well.
After apps update, 472mb used, 11Gb free (was 6gb used before wiping the internal storage).
So far, the only issue is something I read on a post somewhere, but contacts aren't syncing.
I am sure a V4 will be here soon!!
Everything else seems to be working.
MrBungle67 said:
Yep...I tried again...
So, in order, I...
- Rooted using Odin
- Install TWRP using Flashify (thanks to K8108 for the earlier post)
- Went to recovery
- Went to "Mount" and made sure all was checked
- Went to "Wipe", "Advanced"
- Checked everything except internal and external storage
- Install ik4evr's ROM
- Rebooted...
Tablet booted no problem (it stays on "SAMSUNG" for a little bit, which worried me...)
All Samsung apps are gone!!!
Click to expand...
Click to collapse
I did the same. All worked.
Unfortunately I cannot restore apps succesfully from Titanium backup. The restore seems to be ok, but I only get FC's. The apps will not start. I cannot find the cause of the errors.
Something in directions of maps destination changed? Knox?
I do not understand it.
I had a hard time with TB also. Had to get most of my apps back from the play store. Lost some data. Oh well. My contacts are syncing from Google, tho.
k8108 said:
I had a hard time with TB also. Had to get most of my apps back from the play store. Lost some data. Oh well. My contacts are syncing from Google, tho.
Click to expand...
Click to collapse
I always reinstall from the play store... I like it clean and fresh, and I don't have that many apps to restore.
Now...How did you get your contacts? I just installed google+, and my circles finally synced in the contact app. As far as all other contacts (gmail), can't sync them...
Sent from my SM-T520 using Tapatalk
I don't know why my contacts are syncing. The only difference I can see is that in our flashing the rom, I didn't do the advanced wiping. I just did factory reset and cache wipe. I left my system unwiped. I'm not real savvy on this stuff - I have just been a good instruction follower for the past few years and have spent lots of hours reading here on XDA. I am heavily addicted to my tablets and use them for several hours a day so I have over 100 apps. It's a real pain for me to have to go thru the play store for a restore
Sent from my SM-T520 using XDA Premium 4 mobile app

What the What?!

Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
kojam said:
Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Bass_Man25 said:
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Click to expand...
Click to collapse
Thanks bud.
Oh, I got the phone up and running on the Cyanogen dated dec/2013.
ODIN? Never thought of it. Been such a long time. I do need to get stock on here so I can all the latest official radios etc, then put custom ROMs.
Been such a loooooong time since used ODIN though. Shouldn't be hard to get back on the horse.
Thanks for the suggestion!!!
any idea why this happened? anyone?
as an fyi, I tried to put the lastest SlimROM on but same difference. (i'm really pressed for time always. so I decided this is the quickest thing to try). seems the only thing that will flash is my Cyanogen from December. Strange...
Will have to give ODIN a try if I can ever get the time some day..
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
DocHoliday77 said:
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
Click to expand...
Click to collapse
What's up, Doc? Sorry for that...
I downloaded Odin this morning. I should have gotten the link from XDA. The site i got it from looked official, however, tons of endless pop-ups after I installed it. Freak!!!
Then found the xda links. Not sure which version to get because i didn't see which one handles the S3. The latest version (3.09) should, no?
As well, where do i get the stock ROM from? Forgive me for all these questions. Been extremely busy with work these past few months. No time to play around with my phone everything. I'm forgetting more than I know.
A full wipe was done. In TWRP, system was check (it's always checked) automatically when wiping to flash a new ROM.
Thanks again!
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
DocHoliday77 said:
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
Click to expand...
Click to collapse
Thanks!
S.O.S!!!
kojam said:
Thanks!
Click to expand...
Click to collapse
Downloaded the rooted firmware from your link and the ODIN (3.09)...
Flashed the firmware (making sure to get the correct one for WIND)...ODIN did it's thing...got a green pass...the phone rebooted...got the Samsung symbol, little swoosh animation, and the accompanying sound effect that goes with the swoosh-thing...THE PHONE NEVER BOOTED UP AN O/S!
Did it at about 11:30 last night, left it, got up this morn, and phone STILL in same status!
Found out that site where I downloaded the firmware had an issue last night. They posted this morn, apologizing to people about a D.O.D attack that may have caused dropped downloads. I downloaded the firmware again this morn, flashed with ODIN, got a pass....SAME THING!!! Phone
Had to quickly pack up my laptop to bring with me to the office. Will try the official, non-rooted firmware to see if I can get it to go.
Problems' that my team went from 12 to 2 people...my partner's off today...and I got a LOUD MOUTH across from me who WILL NOT leave me alone, no matter what I say or do. LOL.
Any suggestions?
In the words of George Costanza:
"I'm BACK, babyyyyyyy!!!!!"
The official firmware worked!
Phone's back online. Thanks for all your help. Will have to see about rooting later...as well, want to see how the battery operates on stock firmware. I've tried EVERYTHING under the sun to preserve batt life and NOTHING worked!!!
Tried EVERY KERNEL noted to be good on battery life, tried TONS of apps that were supposed to help, turned off as much as I could, etc....
batt still not good. I give up. Every diagnostic app says batt is very good. I dunno...
Earplugs! Lol! I definitely feel for you about your work status! Been there!
About the firmware though, if the download had been corrupted, it would've failed the initial check done by Odin. You are probably ok. Dont worry just yet!
If it is hanging up at the Samsung screen, you probably just need to factory reset. Almost always fixes this. (It happens due to incompatible data left from your previous rom)
This will wipe internal sdcard though, so if you haven't backed up yet, the next thing to fo is flash TWRP via Odin. You can then use its built in file manager to copy whst you need first. Or you can then flash an insecure kernel and use adb if you're familiar with that.
The Doc is in!
if the download had been corrupted, it would've failed the initial check done by Odin
Click to expand...
Click to collapse
That's EXACTLY my thought too. That was really perplexing...
I am up again...
Facotry Reset? How do I do that if stuck at the Samsung splash though?
Now that i know the official firmware works, maybe i'll, try again with the rooted firmware, try to factory reset when stuck, and continue to flash TWRP as you described above. Don't mind factory resetting. I've taken everything I need.
Oh!!!!
I noticed that all the apps I had before flashing the firmware are STILL on my phone. I would have thought that they would have been wiped out completely when lord ODIN was doing her thing.
....and battery life is STILL pretty bad...
Phone's been charging...became fully charged...unplugged it..it was down to 84% after only about 30/mins.
Will see how it goes after doing the factory wipe.
Again, how do i do a factory wipe if stuck at the Samsung swoosh after I re-flash the rooted firmware ?
Maybe your battery is dying. it happens. That would explain a big drop from the start.
To factory reset if you're stuck at boot up, turn the phone off, then boot up into recovery. Hold volume up, home and power. After it vibrates, release power only, continue holding the other two until you see recovery booting up.
If stock recovery is installed, choose factory reset.
In TWRP (probably similar in cwm) go to Wipe and choose factory reset there. In TWRP and CWM, factory resetting does not wipe your internal sdcard. Stock recovery will.
And as for Odin, it doesn't actually touch the user data partition, so all your apps and data are preserved. This is great when just upgrading from one build to the next, but is the reason a factory reset is required if coming from a non touchwiz rom.
---------- Post added at 03:59 PM ---------- Previous post was at 03:53 PM ----------
How old is your battery? The S3 is at the age where people who bought it when it was first released will start to notice the battery is beginning to degrade.
You can also get an app called Better Battery Stats here on xda (paid version in the play store). Its the goto utility for investigating problems with battery drain. Run it for a day after a full charge and then check its logs for persistent wakelocks. The app thread should explain its use better than I can, but if you are having trouble you can always post your bbs log here for one of us to look over. (This isnt my strongest area, but there are a few others around that may also be able to help. )

[Q] Gnex restarts constantly, can't do factory reset, can't reflash

Hello, there.
Get prepared for a lot of bad bad stuff..
So, my Galaxy Nexus was running on a CM-11 Snapshot build, with AOSP kernel. Yesterday, out of the blue, the phone started to get terribly slow and not responsive at all. After a few minutes, it restarted, only to do the same. A couple of minutes maybe, booting up, then get slow and reboot - it did this constantly, and it still does.
I have tried to go into clockworkmod recovery - wiped cache, wiped dalvik cache, wipe user data (factory reset). The phone booted up again, but my apps, etc. were still there! Nothing had happened. I did it a couple of times, but nothing at all.
Then, I have found a .zip file that was still on my memory, with the latest snapshot I had installed. I tried installing it with the install from sd card option, but when it loaded up again, I was still seeing the same apps, background etc.! Nothing had happened and no error message.
Decided to leave the "custom" days behind, I downloaded the stock image for my Gnex. However, since it is a yakjuxw build, I had to flash the yakju option - so not the ideal "stock" package. Using the google installer, I was unable to proceed, since the bootloader number was different than the one that the installer expected, so it exited.
I have found online the amazing Nexus Root Toolkit from WugFresh. I tried to flash it from there, enabling the "force flash" option.
It started out ok.. But when it went to the "system" portion, it took 25 minutes (!) to complete and then in the "user data" portion, it said "write failure".
Still, rebooted and I was still seeing my apps etc. What on earth is happening?
Honestly, I would expect that it would be bricked by now, with all these rom flashes and factory resets. I even tried flashing the stable CM version for it, but still nothing had changed.
Any help would be greeeeatly appreciated.
Yeah im pretty sure your emmc is fried. So you have two options: buy a new phone or a new motherboard. You van check by locking the bootloader if its still unlocked upon reboot your emmc is fried..
Sent from my Galaxy Nexus using XDA Free mobile app
I runned "fastboot oem lock' from my command line, and I got the status "OK".
Then I pressed "restart bootloader" on my phone, but it still says "lock state - unlocked".
So I suppose, I should let it rest in piece, or change the motherboard?
I think a motherboard is more expensive than a new phone. If it is just let it die. If it isnt you can buy a new motherboard and swap it. But I dont think that is a smart move now. The moto g for example is a awesome phone for (i think) almost the price of a new mobo.
Sent from my Galaxy Nexus using XDA Free mobile app
same problem here
It makes me wonder, I'm having the exact same issue just a couple of days later. Is this the planned obsolescence thing?
withend said:
Hello, there.
Get prepared for a lot of bad bad stuff..
So, my Galaxy Nexus was running on a CM-11 Snapshot build, with AOSP kernel. Yesterday, out of the blue, the phone started to get terribly slow and not responsive at all. After a few minutes, it restarted, only to do the same. A couple of minutes maybe, booting up, then get slow and reboot - it did this constantly, and it still does.
I have tried to go into clockworkmod recovery - wiped cache, wiped dalvik cache, wipe user data (factory reset). The phone booted up again, but my apps, etc. were still there! Nothing had happened. I did it a couple of times, but nothing at all.
Then, I have found a .zip file that was still on my memory, with the latest snapshot I had installed. I tried installing it with the install from sd card option, but when it loaded up again, I was still seeing the same apps, background etc.! Nothing had happened and no error message.
Decided to leave the "custom" days behind, I downloaded the stock image for my Gnex. However, since it is a yakjuxw build, I had to flash the yakju option - so not the ideal "stock" package. Using the google installer, I was unable to proceed, since the bootloader number was different than the one that the installer expected, so it exited.
I have found online the amazing Nexus Root Toolkit from WugFresh. I tried to flash it from there, enabling the "force flash" option.
It started out ok.. But when it went to the "system" portion, it took 25 minutes (!) to complete and then in the "user data" portion, it said "write failure".
Still, rebooted and I was still seeing my apps etc. What on earth is happening?
Honestly, I would expect that it would be bricked by now, with all these rom flashes and factory resets. I even tried flashing the stable CM version for it, but still nothing had changed.
Any help would be greeeeatly appreciated.
Click to expand...
Click to collapse
Google's secret weapon to make us buy the new Nexus 6.
I don't know why that happens though - dual core processor, with this amount of RAM. Tech-specs-wise, GNex has nothing to be jealous about than mid-range smartphones right now.. Unless, the CPU architecture from 2012 is so bad that it can't run properly today's apps.
Hey guys, I have these problems too. Just bought the Galaxy Nexus from a friend for €15 (cracked screen) and from the moment I turn it on, (sometimes at Nexus logo, sometimes on lockscreen.. ) it reebot itself. Again and again.
Unlocked the bootloader by toolkit or manually by fastboot but after the reboot it's locked again, as you said. I've tried Odin too with same results. The strange thing it's that it took time to do things but after the reboot, it's like I haven't done anything. I mean, even if I delete an app, or wipe data from recovery (not custom), when it turns on, it's always the same.
It's like a challenge to me. Anyone can help? I can't just give up >.<
Inviato dal mio Nexus 4
What the hell, just finished answering another thread with same issue (forum.xda-developers.com/galaxy-nexus/help/wipe-flash-restarting-help-t2908788). Happened to me last week, very same, never touched the phone, always stock.
What the hell is going on here???
Is there any way to get any log files to determine what the hell is going on?
Mine opens up for a few minutes, maybe 3-4 and it seems to be working well.. It gradually gets unresponsive and ultimately restarts.. So, if there is anything to do during these 3-4 minutes, I would be glad to know..
If you have backed up your sdcard data to your computer, and are prepared to start from scratch (i.e. flashing bootloader and recovery via fastboot, etc.), you can do a full erasure with "fastboot -w" in fastboot mode. This has worked for me in the past to fix data corruption, of which it sounds like you may be a victim. See if that works, but make sure you've backed up your sdcard backups and other data you want to keep first!!!!!!!!
7175 said:
If you have backed up your sdcard data to your computer, and are prepared to start from scratch (i.e. flashing bootloader and recovery via fastboot, etc.), you can do a full erasure with "fastboot -w" in fastboot mode. This has worked for me in the past to fix data corruption, of which it sounds like you may be a victim. See if that works, but make sure you've backed up your sdcard backups and other data you want to keep first!!!!!!!!
Click to expand...
Click to collapse
Already tried, uneffective. Everything, no matter how low level (e.g. Odin) has no effect, like the memory is write-protected. I've read elsewhere this means the eMMC is fried, but if you go backwards in this forum you see many ppl had the very same problem in the past few days/weeks. Very strange indeed.
I'm having exactly the same issue, was running CM11 mod too. Could it be a cyanogen fail?
Atreb92 said:
I'm having exactly the same issue, was running CM11 mod too. Could it be a cyanogen fail?
Click to expand...
Click to collapse
No. I've always been on stock.
fabrice79 said:
No. I've always been on stock.
Click to expand...
Click to collapse
But could it really be a hardware fail? It's pretty strange tho that multiple device have the same hardware issue in such a short time difference
Atreb92 said:
But could it really be a hardware fail? It's pretty strange tho that multiple device have the same hardware issue in such a short time difference
Click to expand...
Click to collapse
That's what I say, but just go backwards and have a look at older post. I subscribed to ~10 posts until 15 Oct then I got tired of browsing backwards...
I'm allready looking at older posts thats why i'm saying it's pretty strange that there is a massive hardware fail for this many devices. If it's a software fail there must be a solution somehow.
Same problem by 31th December...
Yeah, i have the same problem since august 2014. This thread confirmes for me, that my Gnex is really dead. It is sad, it served my very well and i wanted to use it as secondary phone and as mobile hotspot.
Same for me at the beginning of december
This problem I've faced one time and that meant that EMMC is fried, as fellow members said earlier.
If you overwrite the storage and reboot then everything's the same means that you can't write (somehow) thus emmc is dead. Write failure also means that EMMC is dead.
It's really sad, but that's it

phone says its full?

Hey guys Im running stock rooted and for some reason my phone SD is saying im full. I have literally nothing on it. Any ideas?
I tried once to install a ROM but it borked so I went back to a backup I had and it was fine.
Via windows it says my SD only has around 8 gigs used but android is saying 24?!?!?!?
WTF MATE?
Try wiping userdata in twrp.
Illogi.xbone said:
Try wiping userdata in twrp.
Click to expand...
Click to collapse
thanks, I was about to try and just redo the device with a ROM. Clear cahces and such.
I was actually wrong, every time I go into the phone in windows its giving me different storage use #'s. One time its 8 then 17 then 23 then 9. its weird. I think when I tried dirty flashing it just screwed it all up. I have nothing on the SD I care about really so maybe Ill just back up what I want (TWRP backup and titanium apps) and start from scratch if I Cant solve this.
That might be the best. Try backing up to an OTG then completely wiping and installing a fresh ROM. After backing up apps and such.
ugh IM having trouble using any roms on my 5x. No matter the way I install the phone always boots to "internal problem with device"
Ive tried installing different roms (I only like stock style ones) and the vendor.zip and it just doesnt work for me. Ive gone back to my backup for the moment until I figure this out. Never had these issues with my nexus 5
this is odd now my pattern no longer work since my restore back to my TWRP backup! GOD DAKNIT!
let me do the start patttern fine for android then when unlocing the phone it tells me "pattern needed to start device"
what the hell man!
tevil said:
this is odd now my pattern no longer work since my restore back to my TWRP backup! GOD DAKNIT!
let me do the start patttern fine for android then when unlocing the phone it tells me "pattern needed to start device"
what the hell man!
Click to expand...
Click to collapse
Try 1st: Completely wipe device, System, data etc. Including Internal Storage and flash a new rom. If that does not fix the issue try flashing stock firmware and start from scratch. Use THIS guide to flash the stock images.
Flash vendor.img that matches your rom base. MMB29Q is the February OTA base. February AOSP roms are based on MMB29U master code but MMB29Q vendor file works fine.
For password issues after TWRP restore, do this: http://forum.xda-developers.com/showthread.php?t=3245070
Sent from my Nexus 5X using Tapatalk
SERIOUS ISSUE!
Bricked the phone!
CRAP, this whole thing went downhill. Can get into TWRP, and get the android crash logo (triangle) was trying to restore back to stock to start fresh and it bombed completely!
Any tips!!!
Been a while since I used ADB or fast etc, but man if I have to relearn I will

Categories

Resources