Develop Bugs

Is ICS update started by LG Update tool?

Is ICS update started by LG Update tool?

avee02000 said:
Is ICS update started by LG Update tool?
Click to expand...
Click to collapse
Yes. I did it last night and it works great.

oxyehho said:
Yes. I did it last night and it works great.
Click to expand...
Click to collapse
Thanks for reply, i will update it now.

Will the update through the lg mobile tool wipe everything ( apps etc ) ? Is it recommended to do a factory reset after the upgrade?
Thanks.

esqwav said:
Will the update through the lg mobile tool wipe everything ( apps etc ) ? Is it recommended to do a factory reset after the upgrade?
Thanks.
Click to expand...
Click to collapse
Yes, it will erase everything. I'm guessing a factory reset wouldn't be necessary since I think it starts you with a clean slate to begin with after installing it, but if you prefer to do it, it wouldn't hurt I suppose.

LG Update tool
LG Update Tool or whatever you call it. I used it yesterday for update from official first update (vj10?) to official ICS. It leaved all contacts, messages and WiFi access codes intact.
Everything as it is described on LG page (remove spaces, add www in front)
lg . com/us/ NitroHD-Upgrade
1. Install driver
2. reboot
3. install Tool
4-and-5. connect phone and run tool
In ~25 minutes I've got ICS installed.
The only issue I have is the battery life. My usage mode is "Mostly idle" and battery lasts 1 day +. Now it is running out 10% per hour. Not sure what is the problem.

There is my issue, I cannot get the tool to see my phone is connected? Where in CM9 do I activate the "PC Software" mode or have the USB connection menu come up?

In my case (Stock ROM) that was in phone's Settings -> Connectivity -> USB settings then it was a menu { Mass Storage, Charge only, PC Software, MTP something } and "Always Ask" (I'm Paranoid ). I'm not familiar with CM, so check other threads. May be it's easier to get stock ROM first.

drumist said:
Yes, it will erase everything. I'm guessing a factory reset wouldn't be necessary since I think it starts you with a clean slate to begin with after installing it, but if you prefer to do it, it wouldn't hurt I suppose.
Click to expand...
Click to collapse
No, it won't erase everything. just start LG Update tool & connect your phone and start updating. after everything is done you will see your installed apps are still there even call log sms everything remains there.

blaineball said:
There is my issue, I cannot get the tool to see my phone is connected? Where in CM9 do I activate the "PC Software" mode or have the USB connection menu come up?
Click to expand...
Click to collapse
Follow this link-
http://www.lg.com/us/mobile-phones/ATT_Update/index.jsp

avee02000 said:
No, it won't erase everything. just start LG Update tool & connect your phone and start updating. after everything is done you will see your installed apps are still there even call log sms everything remains there.
Click to expand...
Click to collapse
Fail on LG's part. In that case, I'd suggest that everyone who installs this ROM perform a factory reset after installing it.

drumist said:
Fail on LG's part. In that case, I'd suggest that everyone who installs this ROM perform a factory reset after installing it.
Click to expand...
Click to collapse
Not a fail at all... It backs up your info before doing the update.
Personally, I find this to be a huge win. I find it very cumbersome and annoying to have to go through and download my apps and customize the settings.
Way to go LG!

mattman86 said:
Not a fail at all... It backs up your info before doing the update.
Click to expand...
Click to collapse
No, it doesn't back anything up. It's just means it's not clearing your data partition at all during the update. It's the same as not doing "facory reset/wipe data" from CWM before installing a ROM.
The problem is that can lead to all kinds of weird problems once you're in the new ROM. It's probably why some people report bad battery life and others don't, etc.

drumist said:
No, it doesn't back anything up. It's just means it's not clearing your data partition at all during the update. It's the same as not doing "facory reset/wipe data" from CWM before installing a ROM.
The problem is that can lead to all kinds of weird problems once you're in the new ROM. It's probably why some people report bad battery life and others don't, etc.
Click to expand...
Click to collapse
I have upgraded and my data & apps and everythings are as it is. should i factory reset/wipe data now? or should i re updrade? my battery back up is worst at present, 10 hours light use only.

avee02000 said:
I have upgraded and my data & apps and everythings are as it is. should i factory reset/wipe data now? or should i re updrade? my battery back up is worst at present, 10 hours light use only.
Click to expand...
Click to collapse
I would suggest that you do a factory reset and see if the battery life improves after doing that. You'll have to set up the phone again though. Make sure your contacts are either stored to SIM or Google so that you don't lose them, etc.
If you don't know, you need to turn the phone completely off, then hold down volume down and power button at the same time -- keep holding until the text appears that asks if you want to factory reset. Then let go and follow the instructions.
There shouldn't be any reason to install the update a second time.

drumist said:
I would suggest that you do a factory reset and see if the battery life improves after doing that. You'll have to set up the phone again though. Make sure your contacts are either stored to SIM or Google so that you don't lose them, etc.
If you don't know, you need to turn the phone completely off, then hold down volume down and power button at the same time -- keep holding until the text appears that asks if you want to factory reset. Then let go and follow the instructions.
There shouldn't be any reason to install the update a second time.
Click to expand...
Click to collapse
Thanks for your useful point about factory reset. i did factory reset and downloaded about 30 apps which i installed earlier. now i will notice battery life. i will confirm it after using a day.

Does anyone know if this update could apply to P936? I'm currently on CM9-RC2 for P930...
Thanks in advance, cheers!
sent from my LG-P936

Possible to Unlock Bootloader on 4.2.1 without losing data?

Wondering if there is a root method for a GSM GN (locked BL). Then I could run a BL unlock from userland to retain data. Is this currently possible?

vbman213 said:
Wondering if there is a root method for a GSM GN (locked BL). Then I could run a BL unlock from userland to retain data. Is this currently possible?
Click to expand...
Click to collapse
I was just looking for the same information today as well. I think the answer is that you used to be able to do this through a security exploit but that has since been fixed in recent versions.

flintdragon said:
I was just looking for the same information today as well. I think the answer is that you used to be able to do this through a security exploit but that has since been fixed in recent versions.
Click to expand...
Click to collapse
I came to the same conclusion a few weeks ago and went ahead and unlocked and let it wipe my phone. As much as I hate having to reconfigure everything, it is always nice to start over fresh. Although now I'm unlocked and rooted I can create a backup to avoid this in the future.
Sent from my Galaxy Nexus using Tapatalk 2

Guide in my Sig...or stickied up top.
You can backup without root.

So .... I just found a way to unlock the bootloader without losing data.
I posted it up in a blog here http://plognews.wordpress.com/2013/02/07/how-to-unlock-android-nexus-bootloader-without-losing-data/ But I'll post here too..
---------
So many of you may be aware that you may unlock the bootloader on your Google Nexus Device. However, in doing so, the device is wiped clean and you must reinstall everything from scratch (or from backup).
Having an unlocked bootloader does provide benefits. It allows one to take full system backups, install unsigned updates, etc. There is one drawback that it allows for. it may allow an “attacker” to bypass Android securities and do bad things to your device.
I can understand why Google would force your device to be wiped, but there is a way around it without anything really special.
I’m going to try to make it as detailed as possible, but there are many great resources out there on how to do each of these things already. I will provide relatively high level instructions on how to carry this out. This is confirmed multiple times to work on the LG/Google Nexus 4.
You first need to download and install the Android SDK. This includes files in the platform-tools folder called “adb” and “fastboot”. Download the CWM Recovery image from here.
Steps:
1. Put your device in “USB Debug mode” and plug your phone into your PC.
2. Ensure your PC detects the phone by using “adb devices”. If nothing is listed, either you need to run the command as an administrator or you need to install the USB driver.
3. From your PC, use ”adb restart bootloader”
4. You should see a new screen with a bunch of text.
5. Run “fastboot oem unlock”. (from your PC)
6. Select “Yes”.. It will warn you that your device will be wiped. You will be brought back to that screen with the robot that’s open.
7. Run “fastboot flash recovery recovery-clockwork-touch…img” (from your PC).
8. Use the volume keys to change to “Recovery Mode” and click the power button to select. If you can’t select it, then you never flashed the recovery properly.
9. After you’re in the recovery screen, select “Reboot System Now”. It will ask you a question about preventing a reflash, select “Yes”.
10. Let it reboot.. The Google screen and the X will take a very long time and won’t get anywhere. Give it a few minutes at the “X” screen.
11. Hold down the power button until the screen turns off and let go.
12. Hold the volume down button until you’re brought back to the screen with the open robot.
13. “Wipe Cache Partition” and under Advanced, select “Wipe Dalvik cache”
This works on the LG/Google Nexus 4 phone, but there’s no reason this won’t work on other Nexus phones.
*** I will not be responsible for lost data, so ensure to still take a backup. ***

precurse said:
5. Run “fastboot oem unlock”. (from your PC)
6. Select “Yes”.. It will warn you that your device will be wiped. You will be brought back to that screen with the robot that’s open.
Click to expand...
Click to collapse
you didnt read the post.
it clearly says you will lose your data with fastboot oem unlock.
also, thread necro!

Zepius said:
you didnt read the post.
it clearly says you will lose your data with fastboot oem unlock.
also, thread necro!
Click to expand...
Click to collapse
I know it's supposed to .... But it never did when I overwrote the recovery partition this particular way. I believe it may do the actual "wipe" on reboot after you've unlocked the bootloader. However, overwriting the recovery partition may confuse it and so it doesn't format it...
It worked for me this way (confirmed twice), and so I'm providing the steps I took.

precurse said:
I know it's supposed to .... But it never did when I overwrote the recovery partition this particular way. I believe it may do the actual "wipe" on reboot after you've unlocked the bootloader. However, overwriting the recovery partition may confuse it and so it doesn't format it...
It worked for me this way (confirmed twice), and so I'm providing the steps I took.
Click to expand...
Click to collapse
It's not a sure way that data won't be lost. Not sure if you're aware but there are a select number of gnex and even n4 units which did not experience data loss with that method. If memory serves me right there wasn't a clear explanation as to which units were lucky. Some time several months ago those that came from play store didn't experience data loss from unlocking bootloader. Those that originally came with takju were those. However it's not a hundred percent accurate because some still did lose data. Recovery doesn't have anything to do with it. The simple act of unlocking the bootloader erases data but some "lucky" units didn't experience it
Sent from my Galaxy Nexus using Tapatalk 2

Interesting. Well, this apparently doesn't affect my Nexus 4 that I received from Google yesterday.
I'll try the same directions with my Galaxy Nexus after I get home today as well and report back.

precurse said:
Interesting. Well, this apparently doesn't affect my Nexus 4 that I received from Google yesterday.
I'll try the same directions with my Galaxy Nexus after I get home today as well and report back.
Click to expand...
Click to collapse
Check out this thread for the gnex http://forum.xda-developers.com/showthread.php?t=1650830
For the n4 there have been mentions of some units not wiping data as well
Sent from my Galaxy Nexus using Tapatalk 2

showthread.php?t=2016628
Search next time......................................

[Q] SPH-D710 FK23 (FK23 Modem/Kernel/ROM - Root/Stock) - Question

Hello All, This is my first time posting so could not post directly into http://forum.xda-developers.com/showthread.php?t=2021640&page=23.
I’ve been having a problem with SPH-D710 FK23 and from what I’ve read and searched, it doesn’t seem to be common but would like to ask the experts. I’ve installed FK23 from the above thread [LINK][ROM][ODIN][TAR]SPH-D710 FK23 (FK23 Modem/Kernel/ROM - Root/Stock), trying first the Rooted_Nodata but then using Rooted_Restore. I’ve redone the phone three times now using Rooted_Restore and the first thing that seems very odd is that the internal USB did not get wiped. After it completed and booted, the items on the internal USB (such as in the downloads directory) were still present. Once I entered my Google account, the apps reinstalled from Google.
Aside from not seeming to completely wipe the device, there didn’t appear to be any problem until I turned on Bluetooth. Once Bluetooth was turned on and paired with my BlueAnt Q2 v.1.1, the device would freeze and reboot. At this point, I’m not able to turn off Bluetooth as even after rebooting (including a battery pull) the system only responds to touch during the initial few moments of boot while showing scanning and/or initializing SD. After a few moments, no screen interaction will respond other than vibration feedback when pressing any of the four bottom buttons. Volume up/down is not responsive though the power button will still blank or turn the screen on. Aside from that the device appears locked than will eventually reboot itself.
Has anyone seen similar and/or any suggestions?

kdean7 said:
Hello All, This is my first time posting so could not post directly into http://forum.xda-developers.com/showthread.php?t=2021640&page=23.
I’ve been having a problem with SPH-D710 FK23 and from what I’ve read and searched, it doesn’t seem to be common but would like to ask the experts. I’ve installed FK23 from the above thread [LINK][ROM][ODIN][TAR]SPH-D710 FK23 (FK23 Modem/Kernel/ROM - Root/Stock), trying first the Rooted_Nodata but then using Rooted_Restore. I’ve redone the phone three times now using Rooted_Restore and the first thing that seems very odd is that the internal USB did not get wiped. After it completed and booted, the items on the internal USB (such as in the downloads directory) were still present. Once I entered my Google account, the apps reinstalled from Google.
Aside from not seeming to completely wipe the device, there didn’t appear to be any problem until I turned on Bluetooth. Once Bluetooth was turned on and paired with my BlueAnt Q2 v.1.1, the device would freeze and reboot. At this point, I’m not able to turn off Bluetooth as even after rebooting (including a battery pull) the system only responds to touch during the initial few moments of boot while showing scanning and/or initializing SD. After a few moments, no screen interaction will respond other than vibration feedback when pressing any of the four bottom buttons. Volume up/down is not responsive though the power button will still blank or turn the screen on. Aside from that the device appears locked than will eventually reboot itself.
Has anyone seen similar and/or any suggestions?
Click to expand...
Click to collapse
Actually think I have an answer for this now... and it has to do with the change to the storage structure and/or mount points. Before the main mount point for /sdcard was... /sdcard. Now looks like it's /storage/sdcard0. That's the only reason I can think of why it would fail - the script is still triggered so only if it didn't find /sdcard would it skip.

garwynn said:
Actually think I have an answer for this now... and it has to do with the change to the storage structure and/or mount points. Before the main mount point for /sdcard was... /sdcard. Now looks like it's /storage/sdcard0. That's the only reason I can think of why it would fail - the script is still triggered so only if it didn't find /sdcard would it skip.
Click to expand...
Click to collapse
Any idea on the unresonsiveness and rebooting?

kdean7 said:
Any idea on the unresonsiveness and rebooting?
Click to expand...
Click to collapse
Think it's part of the nodata flash effects still lingering.
Try this:
1) Flash FI27 full restore (rooted)
2) Reboot to Odin
3) Flash FK23 full restore (rooted)
That should fix it if it's old data not playing nice.
If it still happens after this the next step we'll do is check your battery.

garwynn said:
Think it's part of the nodata flash effects still lingering.
Try this:
1) Flash FI27 full restore (rooted)
2) Reboot to Odin
3) Flash FK23 full restore (rooted)
That should fix it if it's old data not playing nice.
If it still happens after this the next step we'll do is check your battery.
Click to expand...
Click to collapse
Is it possible that kdean7's problems are because of restoring Google's backup during the initial configuration process?

garwynn said:
Think it's part of the nodata flash effects still lingering.
Try this:
1) Flash FI27 full restore (rooted)
2) Reboot to Odin
3) Flash FK23 full restore (rooted)
That should fix it if it's old data not playing nice.
If it still happens after this the next step we'll do is check your battery.
Click to expand...
Click to collapse
Not sure if what i've done is the same outcome as above but did this yesterday before this was posted. Booted to recovery mode and wiped device / factory restore then flashed FK23 full restore (rooted). SInce then, I've added back my google account, added my Samsung account, added one exchange email and one pop3 email and have been letting the device self-update and reinstall the apps from the Play store. Made one test call and a couple txt messages. I've been waiting until no further updated occur before turning bluetooth back on but so far have't seen any random reboots though don't think I've used it long enough to see any screen locking. More to come as I test further this morning.

kdean7 said:
Not sure if what i've done is the same outcome as above but did this yesterday before this was posted. Booted to recovery mode and wiped device / factory restore then flashed FK23 full restore (rooted). SInce then, I've added back my google account, added my Samsung account, added one exchange email and one pop3 email and have been letting the device self-update and reinstall the apps from the Play store. Made one test call and a couple txt messages. I've been waiting until no further updated occur before turning bluetooth back on but so far have't seen any random reboots though don't think I've used it long enough to see any screen locking. More to come as I test further this morning.
Click to expand...
Click to collapse
Don't recall if the factory reset wipes USB storage, that would be the only possible difference.
Hope that gets you back into shape, will be checking during the day to see if you need any further help!

Same thing happening still
garwynn said:
Don't recall if the factory reset wipes USB storage, that would be the only possible difference.
Hope that gets you back into shape, will be checking during the day to see if you need any further help!
Click to expand...
Click to collapse
Same symptoms happened again. I am going to make another attempt based on the the previous method starting back at ics.

garwynn said:
Think it's part of the nodata flash effects still lingering.
Try this:
1) Flash FI27 full restore (rooted)
2) Reboot to Odin
3) Flash FK23 full restore (rooted)
That should fix it if it's old data not playing nice.
If it still happens after this the next step we'll do is check your battery.
Click to expand...
Click to collapse
This will sound like a very basic NOOB question but I want to ensure I do this exactly as suggested. I've flashed using SPH-D710_FI27_CL1127689_Rooted_Restore.
For reboot to Odin; Is that mean to boot by holding the Down Vol + Pwr then just powering down from that screen? Or possibly boot by holding Up + Vol and selecting one of those options?
I would also like to say THANK YOU to everyone who has been working on the D710. I've been following postings on this device and the knowledge everyone shares is simply amazing!!!

Still Freezing
kdean7 said:
This will sound like a very basic NOOB question but I want to ensure I do this exactly as suggested. I've flashed using SPH-D710_FI27_CL1127689_Rooted_Restore.
For reboot to Odin; Is that mean to boot by holding the Down Vol + Pwr then just powering down from that screen? Or possibly boot by holding Up + Vol and selecting one of those options?
I would also like to say THANK YOU to everyone who has been working on the D710. I've been following postings on this device and the knowledge everyone shares is simply amazing!!!
Click to expand...
Click to collapse
After installing SPH-D710_FI27_CL1127689_Rooted_Restore.exe, booting into odin mode, then installing SPH-D710_FK23_549262_Rooted_Restore.exe, I provided account information for Google and Samsung but this time did not allow the automatic reinstall of apps from the play store. The phone seemed to not exhibit any issues until after the apps shown as needing updates from the play store and the installation of IP Cam Viewer Pro, the phone again started freezing and became unresponsive.
I appreciate the suggestions but will move back to FI27 for a while.

kdean7 said:
After installing SPH-D710_FI27_CL1127689_Rooted_Restore.exe, booting into odin mode, then installing SPH-D710_FK23_549262_Rooted_Restore.exe, I provided account information for Google and Samsung but this time did not allow the automatic reinstall of apps from the play store. The phone seemed to not exhibit any issues until after the apps shown as needing updates from the play store and the installation of IP Cam Viewer Pro, the phone again started freezing and became unresponsive.
I appreciate the suggestions but will move back to FI27 for a while.
Click to expand...
Click to collapse
Think one of your apps may not like the JB build. You could try installing 1-2 at a time and see when it starts acting up to get a better idea of which one it may be...
Sent from my SPH-D710 using Tapatalk 2

Found app causing crash
Looks like I may have found the app causing the crash. Breaking News Newtork (BNN). I saw that it crashed after installing that app last time as I was taking everything very slow and testing after individual apps. It wasn't immediate upon install, only after a reboot. So far without that being reinstalled, things are still working. Still running with minimal apps but so far so good.

[Q] New OS update bricked my Fire. Any quick fixes?

My rooted KF got bricked by the new OS update that was released last night. It boots as normal, gets to the locker screen, and whether you unlock it or not, reboots about 15 seconds later to a screen showing the Android guy and an exclamation point in a yellow triangle. Then, if you start touching the screen, 4 buttons will show up on the side, up/down, select, and back... but they do nothing. Reboot again and it takes me to TWRP.
I know how to wipe my KF and reinstall everything, but I was hoping that someone might know of a fix for this. Especially because I just got a new computer and am still in the process of getting my normal apps installed, let alone Android SDKs that I use once in a blue moon. Plus, I have a few games that I would rather not lose my progress on.
BTW, I rooted my dad's KF the exact same way as mine and his just lost root access with the update, everything else is fine. Kinda weird.
TIA

What OS update? Your new computer will not need sdk. Also you will not escape having to wipe if something has gone amuck, unless you get lucky to be able to flash the prior system to revert the defect. You could just flash modaco http://forum.xda-developers.com/showthread.php?t=1439916 no more losing root from OTA`S. You may also get lucky and be able to flash modaco if you`re on rooted stock or previously rooted stock 6.3.1 without wiping.

Thepooch said:
What OS update? Your new computer will not need sdk. Also you will not escape having to wipe if something has gone amuck, unless you get lucky to be able to flash the prior system to revert the defect. You could just flash modaco http://forum.xda-developers.com/showthread.php?t=1439916 no more losing root from OTA`S.
Click to expand...
Click to collapse
About 3am last night, I found my KF bricked after just using it about 30 minutes before (the wifi was on and it was hooked up to the charger). Today, I checked on my dad's KF and he has his wifi turned off. I turned it on and it instantly rebooted to just a "command line" screen saying that it was installing an update. Took about 10 minutes and then rebooted and worked fine, except that it was unrooted. I read somewhere in the Amazon Forums today that they did roll out an update and plan on spending 2 weeks doing it to keep from bogging down their network. Granted, their Software Update page doesn't say anything about it yet.
BTW, thanks for the other info, I'll have to check it out. Sounds like I'll have to wipe it (or at least restore from a 2-3 month old backup and see how the update goes again). But that's cool that I won't need to install the Android SDK.

Explains why some are instantly being unrooted or like in your case bricked strange thing is that it doesn`t change the system version it`s still 6.3.1 figures that Amazon would pull something like this.

Hey, I did manage to find a quick fix!
In the recovery mode, I decided to try using the Fix Permissions option. Still had the same problem.
I then just used the Clear Cache option and my KF was back up and running... and still rooted.
The only issue I have found so far is that I had to change the permission to allow changing the wallpaper, just uncheck the "write" permissions, (which was probably reset by the Fix Permissions option I ran). Other than that 2 second fix, everything is fine.
Granted, I'm waiting for Amazon to do an auto-check for some file that was in the cache that told it that it had installed the latest upgrade, and since I wiped that, it may install it again. If it does, I'll post it in this thread that my quick fix didn't work. But so far so good.

It turns out that my quick fix is only a temp fix.
Twice tonight I had to clear the cache again via the recovery menu. The first time it happened, I had just finished reading and hit the power button to put it in sleep mode, which caused it to instantly reboot and then do the same thing as I mentioned above. It boots up, and within 5 second of getting the locker screen, whether you unlock it or not, it starts shutting down and reboots ending up with the screen in the attached pic (those dots are just dust that appear super bright for some weird reason because you can't see them except in the pic).
So I cleared the cache again, everything was fine, and then about an hour later I found it sitting on that screen again. Clearing the cache fixed it again, but obvious this is a reoccurring problem.
Anyone have any ideas?
I'm reluctant to do a reinstall yet because I'm afraid I'll just end up with the same problem... along with none of my apps installed.

I have the same issue my temp solution is turn off wifi asap after lock-screen appear, wait abt 1-2 minutes then I can turn on wifi and use as normal.
Everything will fine for few hours. Any permanent solution plz? I remember that it occurred after i update something from Amazon app store, maybe : apps...
Sent from my Kindle Fire using xda premium

The permanent solution is to flash another rom preferably modaco if you want the stock experience. Full wipe, your apps can all be redownloaded that is the least of your worries at this point. probably a really good time to upgrade your bootloader and recovery if you haven`t flash both of these zips as zips in twrp if are behind the curve http://forum.xda-developers.com/showpost.php?p=30780737&postcount=180 and http://forum.xda-developers.com/showthread.php?t=1632375 only get them from where I`m directing you or use smirkit http://forum.xda-developers.com/showthread.php?t=1500935.

thanks for your help. This is done with the below solution
1) Copy the update bin file to the /sdcard as update.zip
Download stock ROM : https://s3.amazonaws.com/kindle-fire-updates/update-kindle-6.3.1_D01E_4107920.bin
copy update-kindle-6.3.1_D01E_4107920.bin into Kindle Fire and re-name to update.zip
2) From the main menu of CWM, "Wipe cache from partion" to remove the existing files in the data and cache partitions
3) From the main menu of CWM, press the "Install update.zip" button to flash the stock software onto your device.
no data/application lost accept FFF and CWM

Wiping cache doesn`t remove data in twrp its factory reset that you need to concern yourself with and unfortunately there is data loss. You may have succeeded but others put themselves in a position of needing a factory cable after not properly wiping when flashing stock. This is because the data is what the kindle has a tough time handling after a complete stock flash. Flashing modaco is far safer, truth is that it will leave your recovery and bootloader intact providing a far better safety net if something were to go wrong. Also if you create a backup before you flash if something does go wrong at least you can restore a half crap backup, wipeout recovery and this is no longer possible just saying. I see far more people fail to flash stock than I ever do flashing modaco.

Thanks for the info guys.
Considering the post in the Amazon Forums said this update was being pushed out over a 2 week period, I'm just going to keep my WiFi off (unless needed) and wait until everyone should have received the update and then see how it plays out. Considering it doesn't change the software version number, I'm thinking that this update may be just targeting rooted Fires. And BTW, it appears that the post was removed, because I can't find it again. Maybe they remove any that mention rooting? I just stumbled upon it via a Google search... 99% of the question in their forum are just idiotic.
Directv used to pull this stunt all the time to bust people with hacked cards that allowed them to get all their channels for free (usually a few hours before some big PPV event). They finally completely stopped the ability to hack cards by rolling out parts of their code over a long period of time, a year or so. When the final piece was put in place, the previous parts of their code had already been integrated into the hacked card software, because it appeared safe, and along with upgrading the type of cards they used during that same period of time, pretty much eliminated the ability to cheat Directv. I'm not saying that Amazon is going to those lengths to stop people from rooting their KFs,.. but who knows? It may be costing them too much with people bricking their KFs by trying to root them. Plus, they may also be losing revenue by people getting their free apps (with ads) from the Playstore instead of Amazon. And considering they pretty much sell their Fires for cost, they definitely rely on revenue generated by buying and using things via a stock KF.
BTW, this whole issue had almost perfect timing... I was planning on wiping my KF because it definitely is slower than when I first got it (which was day 1 of its release). I've read that Gingerbread doesn't clean up after itself too well, especially not as good as ICS (kinda like a Windows registry just gets filled with junk over time, and no cleaner beats a fresh install). It also appears that the ICS roms are actually working reliably these days, compared to the last time I checked. So, in a couple weeks, I'll get to have some fun. I am a Windows/Cisco System Engineer, so this kinda stuff is fun for me.

F.Y.I.
It seems that Amazon did do a incremental update on the Original Kindle Fire version
6.3.1_user_4107720, April 30 build to 6.3.1_user_4107920, November 27 build.
I looked thru the update and the only things I found changed are to do with the
Wifi driver, launcher icons, boot animation, and boot.img; attached the changed file below.
I have not tried to update mine, will attempt this weekend.

Thank you Tera Tike for the info at least this confirms that it's not just a fluke users of rooted stock should be warned appreciate your research. I do wonder why they would change boot animation and IMG seems a bit haneous.

Thepooch said:
Thank you Tera Tike for the info at least this confirms that it's not just a fluke users of rooted stock should be warned appreciate your research. I do wonder why they would change boot animation and IMG seems a bit haneous.
Click to expand...
Click to collapse
It seems they increased the resolution of the images in the file, but for me I can not see the difference.
For me I wonder what they changed in the WiFi driver file, tiap_drv.ko.

Kindle Fire Reboot Problem Solved - Install MoDaCo Rom
Thepooch said:
Wiping cache doesn`t remove data in twrp its factory reset that you need to concern yourself with and unfortunately there is data loss. You may have succeeded but others put themselves in a position of needing a factory cable after not properly wiping when flashing stock. This is because the data is what the kindle has a tough time handling after a complete stock flash. Flashing modaco is far safer, truth is that it will leave your recovery and bootloader intact providing a far better safety net if something were to go wrong. Also if you create a backup before you flash if something does go wrong at least you can restore a half crap backup, wipeout recovery and this is no longer possible just saying. I see far more people fail to flash stock than I ever do flashing modaco.
Click to expand...
Click to collapse
I took Thepooch's advice and installed MoDaCo rom on my KF. It was a snap. I had FireFireFire installed with TWRP. Just downloaded MoDaCo to PC copied to KF. Rebooted to FireFireFire Installed with Install Zip utility. Took a few minutes. Rebooted didn't loose any data , apps or functionality. Its still rooted. THANKS!

No problem you can find the entire uncomplicated method here http://forum.xda-developers.com/showthread.php?t=1923010 or at least a synopsis of the concept.

[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