Develop Bugs

Sigh.. (Stock boot loop)

So annoyed right now. For the second time, my phone has randomly gone in to a boot loop. Completely stock, never unlocked or rooted or anything. So bloody annoying because now I have to reflash stock with ODIN which will wipe my phone again.
I suppose to send it back under warranty I have to pay for shipping and wait a month for a replacement?

case0 said:
So annoyed right now. For the second time, my phone has randomly gone in to a boot loop. Completely stock, never unlocked or rooted or anything. So bloody annoying because now I have to reflash stock with ODIN which will wipe my phone again.
I suppose to send it back under warranty I have to pay for shipping and wait a month for a replacement?
Click to expand...
Click to collapse
If you know how to use Odin, you can figure out how to root, flash a ROM, and use a custom kernel.
See if that helps out your phone with the boot loops. If it doesn't you could always just flash back to stock and send it back.

You're right actually, I suppose I could use this as an excuse to root it. I've held off from doing it though because I always thought if I got a Nexus device I wouldn't need to bother with flashing new roms, but it would be quite nice to upgrade from 4.0.2 I guess.
At least then if it decides to do it again I'll have a nandroid. Still annoyed that this has happened for the second time though

case0 said:
You're right actually, I suppose I could use this as an excuse to root it. I've held off from doing it though because I always thought if I got a Nexus device I wouldn't need to bother with flashing new roms, but it would be quite nice to upgrade from 4.0.2 I guess.
At least then if it decides to do it again I'll have a nandroid. Still annoyed that this has happened for the second time though
Click to expand...
Click to collapse
Bootloops are usually software related, so rooting and flashing an entire new ROM will probably help you.
Just use the toolkit if you're not comfortable rooting
Oh, and since you were having boot loop issues
I would
Make nandroid
wipe data
wipe cache
wipe dalvik cache
Format System
Format Cache
Install Rom
Install Gapps (if required by your ROM)
Reboot and Enjoy
Oh, and then pick a kernel of your choice

I'm sorry you getting random bootloops, and I understand you're expecting them to go away merely by reflashing the same rom, but why are you using ODIN (a leaked, unsupported SAMSUNG flashing program), instead of FASTBOOT, officially supported by Google/AOSP?

bk201doesntexist said:
I'm sorry you getting random bootloops, and I understand you're expecting them to go away merely by reflashing the same rom, but why are you using ODIN (a leaked, unsupported SAMSUNG flashing program), instead of FASTBOOT, officially supported by Google/AOSP?
Click to expand...
Click to collapse
I'm assuming it's because he comes from an SGS/SGS2 and isn't ready yet to step out of his comfort zone. But I agree that learning how to use fastboot is the way to go. And that the process of repackaging the images for odin may actually be the source of the problem (although I know little about such things that I may be wrong).

The last time it happened I just searched for a thread to reflash stock and the first thing I came across was ODIN, what difference does it make? And what do you mean it's leaked? I got it from the Samsung website last time. It's not because it was out of my comfort zone hehe, I'm quite experienced using adb etc, even did a bit of theming before on my Hero.
As an update to my situation - I unlocked/rooted/installed AOKP this morning. Has some nice additions and seems a bit snappier, looking forward to seeing if I have better battery life with it. Oh and I used fastboot not the one-click program. It's only a couple of lines in the terminal after all.

Custom ROM infinite first boot

Firstly: I'm a total n00b for this. I have flashed custom ROMs before, but not for Nexus, so this is my first attempt, so far failing spectacularly.
That said, I'd appreciate advice on both what I did wrong and how to un-brick my phone.
I searched and my problem seems strictly linked to bad flashing, but all solutions are phone specific and I haven't found a thread for Galaxy nexus, so here goes:
I chose this firmware for my flash. I also used the toolkit from stickied post above.
I unlocked the bootloader and then ran (not installed) the CWM tools. Using them I flashed the image directly. The phone was not rooted though I later ran the rooting procedure and it finished without reporting any particular errors. Android naturally never booted during this procedure.
Anyway, my phone now stays in boot animation indefinitely. Recovery mode with fastboot works, but no android joy.
Help greatly appreciated.

More info is needed you didn't mention toro, toro plus, maguro. Ask you need to do is bout into bootloader and fastboot your images back to stick look in your models thread on how to do that so you can get the correct ones.
Sent from my Galaxy Nexus using xda premium

Sorry for panicking too soon. Phone unbricked. Would still appreciate info on what I did wrong to brick it in the first place.

Beamer9408 said:
More info is needed you didn't mention toro, toro plus, maguro. Ask you need to do is bout into bootloader and fastboot your images back to stick look in your models thread on how to do that so you can get the correct ones.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Hm, I've been reading on toolkit and roms for a couple of days now and I still can't really say what toro or maguro is. In what way would they be important for my troubles?

velis74 said:
Hm, I've been reading on toolkit and roms for a couple of days now and I still can't really say what toro or maguro is. In what way would they be important for my troubles?
Click to expand...
Click to collapse
It's very important to know what type of google nexus you have. Majority of custom ROMs are only compatible to certain type of GNex. Maguro is for GSM GNex while TORO is for CDM/LTE GNex. Check the link below for more info:
https://groups.google.com/forum/#!msg/android-building/qzSxFEqWvNg/qanfxMkzXHMJ
One more thing, aside from Maguro and Toro, you still need to know what build or version of GNex you have (yakju or takju). This can also be considered when flashing new custom ROMs. I know majority (or all) of the ROMs works well with either yakju or takju, there is still a slight possibility that you will encounter an issue with the version. Check out the links below for more info regarding yakju and takju:
http://forum.xda-developers.com/showthread.php?t=1778543
http://forum.xda-developers.com/showthread.php?t=1617685

Oh, in that case, I have a GSM version, Maguro it would seem.
The ROM I downloaded doesn't specifically say, but the same developer posted another ROM for which he confirmed GSM compatibility.
So can I myself find out what ROM this is since I can't ask the question in the development thread (I don't have 10 posts yet)?

did you clear all the caches via custom recovery? Although I haven't hit issues with my nexus while flashing, past devices, a factory reset sorts the bootloop most often (unless it was a bad flash). Just note that factory resetting the nexus gets rid of ALL of your data since there isn't an external SD to house your files and keep them protected from a wipe.
I would recommend you making a nandroid backup now that you're up and running again btw
Just my 2 cents

Kohawk09 said:
did you clear all the caches via custom recovery? Although I haven't hit issues with my nexus while flashing, past devices, a factory reset sorts the bootloop most often (unless it was a bad flash). Just note that factory resetting the nexus gets rid of ALL of your data since there isn't an external SD to house your files and keep them protected from a wipe.
I would recommend you making a nandroid backup now that you're up and running again btw
Just my 2 cents
Click to expand...
Click to collapse
Yes, I cleared everything I found in main menu and advanced menu of CWM.
Do I *NEED TO* root my phone in order to install a custom ROM? I would think not, but one can't be sure. That's why I only unlocked bootloader before flashing.
Edit: Yes, I found about the factory reset the hard way. Executed full wipe, then tried to flash...

velis74 said:
Yes, I cleared everything I found in main menu and advanced menu of CWM.
Do I *NEED TO* root my phone in order to install a custom ROM? I would think not, but one can't be sure. That's why I only unlocked bootloader before flashing.
Click to expand...
Click to collapse
I would think you should have rooted... my logic is that you're flashing a zip, so you're making changes to /system, which requires root. I'm not technical enough to say whether or not installing a zip can work around not having root access, but I would think not. If you were flashing system images, I would think you could get by without rooting, but not for just a zip file.
Have you taken a look at the toolkit? Soon as I got my nexus I did the one click to unlock, root, install CWM. Took less than 10 min. I already knew fastboot commands, so no reason for me to do it manually if I can get it done automatically.

Kohawk09 said:
I would think you should have rooted... my logic is that you're flashing a zip, so you're making changes to /system, which requires root. I'm not technical enough to say whether or not installing a zip can work around not having root access, but I would think not. If you were flashing system images, I would think you could get by without rooting, but not for just a zip file.
Have you taken a look at the toolkit? Soon as I got my nexus I did the one click to unlock, root, install CWM. Took less than 10 min. I already knew fastboot commands, so no reason for me to do it manually if I can get it done automatically.
Click to expand...
Click to collapse
no to toolkits... just no...
you do not need root to flash custom roms, only an unlocked bootloader and CWM or TWRP for your recovery.

Zepius said:
no to toolkits... just no...
you do not need root to flash custom roms, only an unlocked bootloader and CWM or TWRP for your recovery.
Click to expand...
Click to collapse
Why all the hate for the toolkit? Probably the only confusing thing to me since moving to the nexus is why so many seem to be against its use... I think its a great and helpful tool.

Kohawk09 said:
Why all the hate for the toolkit? Probably the only confusing thing to me since moving to the nexus is why so many seem to be against its use... I think its a great and helpful tool.
Click to expand...
Click to collapse
go look at Q&A
everyday there are at least 5-10 threads saying "HELP I BRICKED MY NEXUS... i used this toolkit but i have no idea what happened to my phone"
if someone is too lazy to type in these 2 commands and then flash su.zip to their phone, they dont need to be dinking with custom ROMs
Code:
fastboot oem unlock
fastboot flash recovery nameofclockworkortwrp.img
nexus phones are some of the easiest phones to unlock and root. there is no real need for a toolkit.

I'm currently making another attempt, but this time I'm rooting the phone and trying an image that is confirmed GSM.

Zepius said:
go look at Q&A
everyday there are at least 5-10 threads saying "HELP I BRICKED MY NEXUS... i used this toolkit but i have no idea what happened to my phone"
if someone is too lazy to type in these 2 commands and then flash su.zip to their phone, they dont need to be dinking with custom ROMs
Code:
fastboot oem unlock
fastboot flash recovery nameofclockworkortwrp.img
nexus phones are some of the easiest phones to unlock and root. there is no real need for a toolkit.
Click to expand...
Click to collapse
makes sense.... agree its probably more of a hinder than a help for those without basic fastboot knowledge. Especially since that knowledge is needed for getting out of a bind many times. Was just curious why I see some much negativity towards it...I still think its a useful tool to save time, at least from my perspective, if you already have that background. The files are all downloaded together and it was more of a convenience thing for me at least. The driver piece is probably the most helpful, since they can be a real PITA if there are leftovers from previous devices...

Just thought I pop my head in and say you were bootlooped. Not bricked. Not even soft bricked as that would constitute you had no recovery, which you did have. Just getting you clear on the lingo we use here.
Sent From My Toro+ via SkyBlue Tapatalk

Seems I chose a bad ROM after all. Flashing to CdTDroid's other ROM worked immediately.
Well, almost: after flash it would continuously report "system UI stopped working" or some such. I had to perform another factory reset before it actually worked as it should.
Now to go test if my issues with this phone are finally over or not.

velis74 said:
Seems I chose a bad ROM after all. Flashing to CdTDroid's other ROM worked immediately.
Well, almost: after flash it would continuously report "system UI stopped working" or some such. I had to perform another factory reset before it actually worked as it should.
Now to go test if my issues with this phone are finally over or not.
Click to expand...
Click to collapse
before you install a rom, always wipe data/cache.

That's the problem: I thought I did. Anyway, it's working now. Will have another go at CM later. Since I'm on custom ROM I might as well go all the way
Sent from my Galaxy Nexus using xda app-developers app

velis74 said:
I'm currently making another attempt, but this time I'm rooting the phone and trying an image that is confirmed GSM.
Click to expand...
Click to collapse
You don't need to root, as flashing the ROM will wipe the root. Most ROMs come with root access already, so people don't notice when they flash.

Yeah, figured as much + stopped doing all the unnecessary crap. Turns out flashing takes few steps but I dare not be as careless to say it's easy.
I have now successfully flashed the CM10 ROM by CdTDroiD straight from stock 4.0.4.
Turns out I misinterpreted "wipe data/factory reset" in CWM. It doesn't clear the filesystem (/sdcard) as I thought. Seems I managed to delete my files some other way during the first flashing attempt. Not clearing data was the cause of bootloop as Über reminds me it's called.
I did all that plus kept the original ICS animation which I like better than JB one. I'm really happy thus far having used it for a couple of hours.

[Q] Boot Loop

I just entered the world of a rooted phone, all exciting and new. I used triangle away, and everything is well. I even turned off the debugging mode as i thought i was all done with things rooting and didn't need it.
The next day I realize there is update for supersu, so i accept, if gives me two choices in the update, i choose one, and now my phone is the in GTN7100 loop non stop. Seems of the two options, I choose wrongly. I can put it into download mode. I think I can put it into recovery mode too.
I used this method to boot.
galaxy-note2.wonderhowto.com/how-to/root-your-samsung-galaxy-note-2-using-odin-for-windows-so-easy-your-grandma-can-do-it-0146884
I did perform some basic backups with kies and i believe an app called my backup, so in the worst case, I believe i can recover everything if had to do some kind of reset that would erase all the data. (I am hoping to avoid that, as the recovery may be a learning process if any challenges with it)
its with 4.1.2 and I am not sure if any other details I should provide. so i feel proud i got this far, sad the supersu update made some kind of corruption. i know you guys may be extremely busy and i thank you so much in advance.

Try getting into recovery (CMW or Philz touch) and re-flash a ROM?

thank you bunglebp
bunglebp said:
Try getting into recovery (CMW or Philz touch) and re-flash a ROM?
Click to expand...
Click to collapse
Thank you so much for your reply bunglebp.
I believe I had the CMW when i rooted. Reflashing the ROM won't lose the data, or will? This is new territory for me, so I am going step be step.
Volume up - home - power, i think i understand this far. I just don't want to make any mistakes and follow to a T to bring the phone back up with least work at it if possible.

Macguyer2000 said:
Thank you so much for your reply bunglebp.
I believe I had the CMW when i rooted. Reflashing the ROM won't lose the data, or will? This is new territory for me, so I am going step be step.
Volume up - home - power, i think i understand this far. I just don't want to make any mistakes and follow to a T to bring the phone back up with least work at it if possible.
Click to expand...
Click to collapse
Yes your description of how to get into recovery is correct. But your description of your situation is light on details, hard to get a clear picture, but I feel your pain!
If you have a ROM sitting on your phone that you can reflash in recovery, do it. You won't lose any media on your internal memory e.g. pictured, movies. All your app settings will remain if you don't wipe anything in recovery prior to flashing - but in your situation I suggest a full wipe & reset to (hopefully) clear out any problems.
As for upgrading SU, I'm wondering what you mean by two options? Let us know how you get on. Also feel free to PM me if you're truly stuck, I've been there myself and received help that saved me untold stress.

tweeny80 said:
Yes your description of how to get into recovery is correct. But your description of your situation is light on details, hard to get a clear picture, but I feel your pain!
If you have a ROM sitting on your phone that you can reflash in recovery, do it. You won't lose any media on your internal memory e.g. pictured, movies. All your app settings will remain if you don't wipe anything in recovery prior to flashing - but in your situation I suggest a full wipe & reset to (hopefully) clear out any problems.
As for upgrading SU, I'm wondering what you mean by two options? Let us know how you get on. Also feel free to PM me if you're truly stuck, I've been there myself and received help that saved me untold stress.
Click to expand...
Click to collapse
When I was welcomed to update supersu, it had a left choice (normal) and a right side choice cwm/twrp (not sure the spelling) I choose the right.
I really want to first thank you so so much.
Which options within the recovery should i choose?
When I did try to repeat the original root process, I got a PIT message that just stayed and did not change. I was on slow machine, but I think it was because the debug usb was off or as i was starting to hear, the partition might be changed in the rooting process? Not sure how that would relate. likely because the debug was off
The pain and fear that broke the phone is really intense. Plus, I use it all the time, before this happened. what information do you need?

Macguyer2000 said:
When I was welcomed to update supersu, it had a left choice (normal) and a right side choice cwm/twrp (not sure the spelling) I choose the right.
I really want to first thank you so so much.
Which options within the recovery should i choose?
When I did try to repeat the original root process, I got a PIT message that just stayed and did not change. I was on slow machine, but I think it was because the debug usb was off or as i was starting to hear, the partition might be changed in the rooting process? Not sure how that would relate. likely because the debug was off
The pain and fear that broke the phone is really intense. Plus, I use it all the time, before this happened. what information do you need?
Click to expand...
Click to collapse
My assumptions are you were successfully rooted, I'm unsure if you are on stock ROM or custom ROM, you updated SU and ended up in bootloop. You are able to get into recovery - do you have a ROM already sitting on your phone, that you can flash/install? If yes, do that. But first, in recovery look for options named factory reset, do that. You suggested you have CWM recovery - there is option to wipe cache, then under advanced option, is wipe dalvik cache, do those. I hope I adequately described the menu structure, my phone is not with me right now to check.
Really, we just want to get you back into a functioning ROM, and stop the bootloops. As for updating SU, I assume you tried updating from recovery? If so, stick to the Play Store updates only.
Again lemme know how you get on, and confirm my assumptions so I can help further if needed.

tweeny80 said:
My assumptions are you were successfully rooted, I'm unsure if you are on stock ROM or custom ROM, you updated SU and ended up in bootloop. You are able to get into recovery - do you have a ROM already sitting on your phone, that you can flash/install? If yes, do that. But first, in recovery look for options named factory reset, do that. You suggested you have CWM recovery - there is option to wipe cache, then under advanced option, is wipe dalvik cache, do those. I hope I adequately described the menu structure, my phone is not with me right now to check.
Really, we just want to get you back into a functioning ROM, and stop the bootloops. As for updating SU, I assume you tried updating from recovery? If so, stick to the Play Store updates only.
Again lemme know how you get on, and confirm my assumptions so I can help further if needed.
Click to expand...
Click to collapse
[If you don't already have it, download and install the Samsung USB Drivers. Now, download and unzip the GalaxyNote2Root.zip file. Open the ODIN program by double-clicking the odin3 v1.85.exe application file.] from the website i followed. with this catchy title:
How to Root Your Samsung Galaxy Note 2 Using ODIN for Windows (So Easy Your Grandma Can Do It)
and it rooted with no problem...just that boot loop the next day when updating supersu...and using the google only site is a good idea.
I am having trouble to get the recovery mode on. I can go into download mode easily, but to go into recovery appears to be a trickier issue. I just can't get it. Can you guide me on this....

Simply reflash rom and reroot again.
Flashing stock rom won't erase data. So if after flashing rom device boot up normally, tour data will be there intact, incase it doesn't boot normally after flashing rom then you may need to wipe it.
Sent from my GT-N7100 using xda premium

Macguyer2000 said:
I just entered the world of a rooted phone, all exciting and new. I used triangle away, and everything is well. I even turned off the debugging mode as i thought i was all done with things rooting and didn't need it.
The next day I realize there is update for supersu, so i accept, if gives me two choices in the update, i choose one, and now my phone is the in GTN7100 loop non stop. Seems of the two options, I choose wrongly. I can put it into download mode. I think I can put it into recovery mode too.
I used this method to boot.
galaxy-note2.wonderhowto.com/how-to/root-your-samsung-galaxy-note-2-using-odin-for-windows-so-easy-your-grandma-can-do-it-0146884
I did perform some basic backups with kies and i believe an app called my backup, so in the worst case, I believe i can recover everything if had to do some kind of reset that would erase all the data. (I am hoping to avoid that, as the recovery may be a learning process if any challenges with it)
its with 4.1.2 and I am not sure if any other details I should provide. so i feel proud i got this far, sad the supersu update made some kind of corruption. i know you guys may be extremely busy and i thank you so much in advance.
Click to expand...
Click to collapse
Just to let you know I have used both sources of available update for super su.
And have never had any problems, I highly doubt your boot loop is anything todo with the su update. The guus on here at xda are superb and will have you back up and running no problem.
GT N7105 with XDA Premium......that is all......

bearusa said:
Just to let you know I have used both sources of available update for super su.
And have never had any problems, I highly doubt your boot loop is anything todo with the su update. The guus on here at xda are superb and will have you back up and running no problem.
GT N7105 with XDA Premium......that is all......
Click to expand...
Click to collapse
thank you for the positive thinking. but I think I have a serious problem here.
I can not get into recovery, as much as i try.
Before all this happened, i unticked usb debug.
I can however get into download mode.
I really feel that i have critically wounded my phone.

Macguyer2000 said:
thank you for the positive thinking. but I think I have a serious problem here.
I can not get into recovery, as much as i try.
Before all this happened, i unticked usb debug.
I can however get into download mode.
I really feel that i have critically wounded my phone.
Click to expand...
Click to collapse
Enter download mode and reflash the recovery using odin. Unticking debug should not put your phone into bootloop neither. . You have to make sure your flashing the correct recovery or rom for your phone model. Depending if you have n7100 or n7105..
GT N7105 with XDA Premium......that is all......

bearusa said:
Enter download mode and reflash the recovery using odin. Unticking debug should not put your phone into bootloop neither. . You have to make sure your flashing the correct recovery or rom for your phone model. Depending if you have n7100 or n7105..
GT N7105 with XDA Premium......that is all......
Click to expand...
Click to collapse
OK, let me make sure I understand correctly..I can put some of my fears/worries to rest.
Let me restate
My situation is a bootloop.
My usb debugging is off. (the day after the rooting, I didn't think I needed it on anymore, as I completed the root)
Later that day, just moment before the loop happened, I was updating SuperSu. (something the phone didn't like)
I found: I can go into download mode. I can not go into recovery mode.
(a phone with a bootloop, usb debugging is off, and download mode is accessible)
So:
(When rooting, I opened Odin, I selected the PDA option, choose the proper file, and pressed start. Yellow changed to Green and we were done)
So Now, I open Odin, select the PDA option, choose the correct file for my phone (GT N7100) from likely the samsung website, I see the Yellow, hit start, yellow turns to green, and we're ok?

That simple thing I said 24 hr ago, still you are here.
It has nothing to do with usb debugging.
If you keep it enable /disable, it won't make any difference in flashing.
Sent from my GT-N7100 using xda premium

Phone is OK now!
dr.ketan said:
That simple thing I said 24 hr ago, still you are here.
It has nothing to do with usb debugging.
If you keep it enable /disable, it won't make any difference in flashing.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
I want to say thank you to everyone. I flashed recovery and it told of bad install. I rebooted and everything is FINE!
Thank you so much!

[Q] Recovery bootloop after Odin/Kies/Heimdall STOCK flash, only boots to DL mode

Hi folks, long time reader, first time noob answer seeker.
I'm no stranger to rooting, flashing, hacking about and such - I even spend most of my day as a software engineer, and I've finally given up on this one - so here I am (rock me like a hurricane), please be kind.
SM-900T - It was rocking pretty darn well on Jedi Elite which I had flashed over rooted stock 4.3 MI7 - then (probably after one too many XPosed modules) it just kept rebooting randomly. Thinking it was no biggie, I thought I could just reflash to stock and call it a day. Thirteen or so flashes later, I gave up on 4.3 and figured I'd just take the thing up to 4.4.2 NB4 by upgrading everything to 4.4.2 via Kies.
That's when I first ran into the bootloop issue, read a lot about it, and managed to get it up(ish) on stock, rooted, with Philz 6.X... Couldn't flash a ROM to save myself and wound up with another soft brick.
Flash forward to Friday - decided to start from scratch again - attempted to flash stock 4.4.2 from Kies, from Odin, From Heimdall... Nothing seems to be able to get me out of the current state it's in:
Only boots to download mode. Flashes seem to work fine, but on that first reboot where it tries to go to stock recovery to finish up on the device itself, it never gets there - boot loops trying to load recovery no matter how it wants to get there. If I pull the battery and start up (either straight to system or by cancelling out of download mode), it boot loops trying to load system. Boots fine to download mode, where I attempt to flash again with the same results.
Yes, I've tried Odin 3.0.9, 3.0.7, 1.8.5, Heimdall on Mac, Heimdall on Windows, Kies on Mac, Kies on Windows - repartition via PIT and not. Installed, uninstalled, and reinstalled all software and drivers multiple times, tried multiple cables on multiple USB ports.... Most of the time it looks like it's going to be fine (sometimes the flash fails, usually through Kies), but never surivives that first reboot after the flash.
Every answer I've seen says to do the things I've already done or cannot do (flash stock via Odin, pull the battery and boot to stock recovery and do a factory reset - which I'd LOVE to do, but can't). No problem recognizing the sucker on the PC/Mac
Next step: try flashing a N9005 ROM...
Any other thoughts? I do have another N900T that's working but has a blacklisted IMEI, and I've been tempted to swap the IMEIs a last resort (although either I'm too dumb to make it stick, EFS pro says it succeeds in writing the IMEI after I do a EFS format, but it doesn't stick.... Either I'm missing something, or I need a UART cable) - is there a way of swapping just the radio hardware or just the internal storage? OR, is there a way of taking a full system image of my working phone and making an Odin-flashable tar from that?
Failing any of these options, perhaps I'll wait for an Odin-flashable 4.4.3 if such a thing exists - or, hope to get lucky and swap it out at a store praying they don't see I've tripped Knox.

Looks like you've tried almost everything. Take it in and have them swap it.
Sent from my SM-G900T using Tapatalk

Coming from you...
noobtoob said:
Looks like you've tried almost everything. Take it in and have them swap it.
Click to expand...
Click to collapse
Coming from you (I have read, and am quite thankful for, many of your posts), sounds like that might be the best option, however disconcerting.

bondidave said:
Coming from you (I have read, and am quite thankful for, many of your posts), sounds like that might be the best option, however disconcerting.
Click to expand...
Click to collapse
Well, I do have a few ideas... Got done questions though.
1. Do you have an external SD card?
2. It goes all the way through flash on 4.4 even with heimdall?
3. Is there anything you have left out? Even the smallest detail can help, and by the op you are detail oriented, so I just need to know.
Sent from my SM-G900T using Tapatalk

... is there a way of taking a full system image of my working phone and making an Odin-flashable tar from that?
Click to expand...
Click to collapse
Yes, but I don't have the details handy.
All your attempts suggest to me that you might have some damaged hardware which is causing data corruption during transfer. Open the back and take a good look at the USB port. Tighten the screws and try a transfer while firmly holding the cable in place -- don't move it while transferring.
If that doesn't work then let 'noobtoob' walk you through booting with the removable sdcard. Your second N900T will be needed to write the data to the sdcard. If this works then you can 'dd' write stock partitions to an sd card with #2 then 'dd' write them in #1.
If either of those works then unroot and take it in for warrenty exchange.
Frank

bondidave said:
... then (probably after one too many XPosed modules) it just kept rebooting randomly.
Click to expand...
Click to collapse
This also indicates data corruption, and this is what started it all. Since you have tried various cables and computers that leaves the device, probably the USB port.
Frank

probably the USB port.
Click to expand...
Click to collapse
Swapped the main board with the working phone to rule out the USB port - still no luck.
Definitely interested in trying the boot from external SD, I'll do my own search for it, unless you can quickly provide me with a link - but if it's as easy as it sounds (booting off of an SD in order to be able to send ADB commands to dd copy the partitions from the good phone to SD then from the booted SD back to internal) - I'm happy to give it a shot.
Tempted just to swing by TMO just to see if they'll swap it "under warranty" (despite picking it up from a private sale) - the only way they would notice it's been "tampered" with would be to check the knox counter by attempting to run download mode.
Oh, and yes, it does go all the way through with the flash (at least in Odin - I haven't tried a full flash through heimdall, just boot and recovery, Kies occasionally goes through to the end, but sometimes craps out at the same 57% point at which point the emergency restore screen shows up)
Thanks again guys

bondidave said:
Swapped the main board with the working phone to rule out the USB port - still no luck.
Click to expand...
Click to collapse
OK, but I still think the problem was initially caused by corruption. Maybe the files you have been flashing are corrupt.
Definitely interested in trying the boot from external SD, I'll do my own search for it, unless you can quickly provide me with a link - but if it's as easy as it sounds (booting off of an SD in order to be able to send ADB commands to dd copy the partitions from the good phone to SD then from the booted SD back to internal) - I'm happy to give it a shot.
Click to expand...
Click to collapse
This is the thread, it would be good to read the whole thing but if you need to save time begin at this message: http://forum.xda-developers.com/showpost.php?p=48685247&postcount=158
I have not tried this procedure yet but @noobtoob was actively involved in it.
Tempted just to swing by TMO just to see if they'll swap it "under warranty" (despite picking it up from a private sale) - the only way they would notice it's been "tampered" with would be to check the knox counter by attempting to run download mode.
Click to expand...
Click to collapse
Please try the SD-boot first so that we can add that experience to this newly developed procedure.
Oh, and yes, it does go all the way through with the flash (at least in Odin - I haven't tried a full flash through heimdall, just boot and recovery, Kies occasionally goes through to the end, but sometimes craps out at the same 57% point at which point the emergency restore screen shows up)
Click to expand...
Click to collapse
You have probably tried it, but if not, download fresh copies of everything and check the MD5 values.
Frank

Frank Westlake said:
OK, but I still think the problem was initially caused by corruption. Maybe the files you have been flashing are corrupt.
This is the thread, it would be good to read the whole thing but if you need to save time begin at this message: http://forum.xda-developers.com/showpost.php?p=48685247&postcount=158
I have not tried this procedure yet but @noobtoob was actively involved in it.
Please try the SD-boot first so that we can add that experience to this newly developed procedure.
You have probably tried it, but if not, download fresh copies of everything and check the MD5 values.
Frank
Click to expand...
Click to collapse
This was for hard brick method and no one has verified it works on 4.4 KK yet. There is an image in there though. My mediafire shows it was downloaded 11 times, but yet not a single "this works on KitKat" response. Located here you will find the kkunbrick.img. There is still a problem flashing anything through heimdall after updating to the 4.4 bootloader, so there is no way to tell if the phone actually took the recovery. I have had to switch to Odin for everything afterwards, and in personal experience 3.07 works best with my phone.
@bondidave I was thinking skipping the sd-card trick for now, and trying just a few other things first. Do you have a nandroid of any 4.4 ROMS saved anywhere? I was going to say try and flash the stock image. After it gets through flash and tries to boot into recovery, go back directly to download mode. Flash philz or twrp, whatever you need to. Try and perform a recovery boot, wipe everything, and nandroid restore of a 4.4 if you have one.
Also if you have an external find the efs fix zip and have handy on an sd-card, do the same steps above except the nandroid restore. Basically if we can get into a recovery we should be ok. I had a similar issue when it was just booting over and over into download mode and this was how I fixed it. I have never used the efs fix zip, but many others swear by it. I was able to recover fortunately enough.
Last resort try the sd-card boot. I don't necessarily think it will work with this particular case as you do not have the dreaded QHUSB_MODE and your phone is still recognized by the computer(s) you have been using.
As far as making a complete system backup of your current phone, I highly recommend against it, unless you just want to extract information from it and not re-write it. This could definitely cause some system corruption on a new device.
If none of these methods work, then try and have them swap it under warranty.

Frank Westlake said:
You have probably tried it, but if not, download fresh copies of everything and check the MD5 values
Click to expand...
Click to collapse
Yessirreeebobbyjimmy, tried several copies from several different places - that and Kies is a moron and redownloads it every time anyways.

noobtoob said:
My mediafire shows it was downloaded 11 times, but yet not a single "this works on KitKat" response.
Click to expand...
Click to collapse
I download these things just to have them handy if something fails.
Do you have a nandroid of any 4.4 ROMS saved anywhere? I was going to say try and flash the stock image. After it gets through flash and tries to boot into recovery, go back directly to download mode. Flash philz or twrp, whatever you need to. Try and perform a recovery boot, wipe everything, and nandroid restore of a 4.4 if you have one.
Click to expand...
Click to collapse
I don't think he got that far into installing 4.4, but I recommend not using anything that was saved after this problem began. If the problem was caused by corruption then the restore will reinstall the corruption.
Last resort try the sd-card boot. I don't necessarily think it will work with this particular case as you do not have the dreaded QHUSB_MODE and your phone is still recognized by the computer(s) you have been using.
Click to expand...
Click to collapse
If the problem is bad USB or other bad hardware causing corruption during transfer then the SD-card boot will get past that, then transferring the rest of the partitions by SD-card will continue to be corruption-free. He could then trade-in the phone.
But you are right -- he should try everything else before the SD-card boot. Because if something else succeeds then maybe the hardware is fine, and if he went immediately to SD-card boot he wouldn't know that.
Frank

Thanks for the advice guys - I'm going to try the backup from my other phone, then the efs fix, then the sd-card boot... I'll report back, wish me luck.

A nandroid previous failure, or a ROM install from external SD card was all I meant.
Sent from my SM-G900T using Tapatalk

I got some answers I was looking for here. Glad I read this thread.

Lorettaa said:
I got some answers I was looking for here. Glad I read this thread.
Click to expand...
Click to collapse
Glad something good came out of my frustration!
Here's a quick update: I've done everything but the boot from SD card with no luck (and actually thought I had hard(er?) bricked it for a while after trying to copy over a few images from the other phone - turns out it needed to stay with the battery out for at least 20 minutes).
Good news - walked into a TMO brick-and-mortar last night, showed the guy my endless bootloop, and a replacement is on its way to my house for an affordable $20 warranty service fee.
At this point, I'm thinking the internal flash memory is just bad - as a software engineer, I'm ok with chalking this one up to a hardware issue (as much as I was hoping that my first post on XDA would result in some new profound solution to a longstanding issue common to a few folks).
Oh well - new Note 3 on it's way, and a new S5 shortly behind it (didn't hold out much hope on TMO hooking me up, so I ordered an S5)... let the battle of the Samsungs begin!
Thanks again to you guys who helped out - and the whole XDA community in general, I am very grateful.

Finally you made it fix and enjoy the battle between your phones

Well, sucks it couldn't be fixed, but glad you got a replacement on the way. It pretty much sounded like the partitions were well over written before we attempted anything, but always worth a shot.
Sent from my SM-G900T using Tapatalk

Yes, but I don't have the details handy.
All your attempts suggest to me that you might have some damaged hardware which is causing data corruption during transfer. Open the back and take a good look at the USB port. Tighten the screws and try a transfer while firmly holding the cable in place -- don't move it while transferring. :good:

[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