A few days ago, I received a notification on my N5 for a new system update of size 10.1 MB. When I choose to install the update, the phone reboots as expected, shows the "Google" startup logo, shows a screen that indicates that it is installing the update for a few seconds, and then finally ends at an "Error" screen (please see the attached image).
The phone stays on this screen for quite a while (more than a minute), then finally the device restarts and the system update notification is still present.
I've tried rebooting the phone manually and installing the update again, both when charging and when off the charger, but this has not helped. I've also searched to see if others have been having this problem, but I haven't been able to find anything. Has anyone else been experiencing this issue with the latest update, or are there any suggestions for how I can go about getting the update to install properly?
I would suggest you flash the system.img and boot.img using fastboot. The latest factory image ends in 48i, Google nexus factory image and download that image, extract it and inside is another zip file, in there you'll find the system and boot images.
Sent from my Nexus 9 using XDA Free mobile app
Thank you for your speedy reply! I will do as you've suggested and respond with my results.
I get the same error when trying to update the OTA Update (from LMY48 to LMY48I). Is it possible to install the next update ignoring this one or will I only be able to install it after sucessfully updated this update?
Why don't you just do what jd1639 suggested?
Sent from my Nexus 5 using Tapatalk
So, I'm coming back to admit that I still haven't attempted the solution proposed by jd1639, with the reason being that I don't quite have the time to deal with flashing and clean-wiping my phone, then setting everything up again. I know it's a simple process, but right now I don't want to do anything that could jeopardize my having a working phone. I doubt there's any better option than flashing the latest update, however, so I'm waiting until I have the time and the patience to do so.
I must say that I'm still curious as to why something like this would happen. I'm inclined to assume that it is a problem with my phone in particular, since I haven't been able to find any other complaints about this problem with this particular OTA update (although cj182 seems to be having the same problem as I am). I suppose anything can go wrong with a system update, especially on a Linux-based system, but I would like to figure out why such a small and seemingly inconsequential update would fail to install on my phone when past updates of much larger sizes and complexity seemed to install without issue.
cj182 said:
I get the same error when trying to update the OTA Update (from LMY48 to LMY48I). Is it possible to install the next update ignoring this one or will I only be able to install it after sucessfully updated this update?
Click to expand...
Click to collapse
I must admit that I'm interested in the answer to this question, as well, though my intuition tells me that the answer is no because I would think that Google releases each OTA update assuming that the device is on the latest version of Android up until that point. I do not know if Google releases separate updates that would allow one to "skip" a version in between a previous version and the latest, though I may certainly be incorrect.
TomCatullo said:
So, I'm coming back to admit that I still haven't attempted the solution proposed by jd1639, with the reason being that I don't quite have the time to deal with flashing and clean-wiping my phone, then setting everything up again. I know it's a simple process, but right now I don't want to do anything that could jeopardize my having a working phone. I doubt there's any better option than flashing the latest update, however, so I'm waiting until I have the time and the patience to do so.
I must say that I'm still curious as to why something like this would happen. I'm inclined to assume that it is a problem with my phone in particular, since I haven't been able to find any other complaints about this problem with this particular OTA update (although cj182 seems to be having the same problem as I am). I suppose anything can go wrong with a system update, especially on a Linux-based system, but I would like to figure out why such a small and seemingly inconsequential update would fail to install on my phone when past updates of much larger sizes and complexity seemed to install without issue.
I must admit that I'm interested in the answer to this question, as well, though my intuition tells me that the answer is no because I would think that Google releases each OTA update assuming that the device is on the latest version of Android up until that point. I do not know if Google releases separate updates that would allow one to "skip" a version in between a previous version and the latest, though I may certainly be incorrect.
Click to expand...
Click to collapse
If your bootloader is unlocked just flashing the system and boot images does not wipe your device. If everything goes right there will be no re-setting up required, you will have to re-root if you're rooted but that's just a matter of flashing supersu in a custom recovery.
Sent from my Nexus 5 using XDA Free mobile app
Or try recovery (stock) and find the flash update from cache (might work)
Sent from my LG-D722 using XDA Free mobile app
That doesn't work. The update checks for changes to the system (root, etc.) and needs stock recovery to install.
I'm also having the same exact problem!
jd1639: Are you sure that will not wipe the data?
It doesn't wipe your data... many of us have done it.
jrosado said:
I'm also having the same exact problem!
jd1639: Are you sure that will not wipe the data?
Click to expand...
Click to collapse
It does wipe your data. However,I strongly suggest you backup first in case something goes wrong, that's just good practice.
Sent from my Nexus 9 using XDA Free mobile app
Telyx said:
It doesn't wipe your data... many of us have done it.
Click to expand...
Click to collapse
jd1639 said:
It does wipe your data. However,I strongly suggest you backup first in case something goes wrong, that's just good practice.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Now i'm confused...it wipes or not? I'm referering to just flashing the boot and system files.
jrosado said:
Now i'm confused...it wipes or not? I'm referering to just flashing the boot and system files.
Click to expand...
Click to collapse
Sorry about that, I meant it DOES NOT wipe the device.
Sent from my Nexus 9 using XDA Free mobile app
I'm sorry to say that it wipes all data and applications
jrosado said:
I'm sorry to say that it wipes all data and applications
Click to expand...
Click to collapse
Did you flash just the system.img and boot.img? Just doing that will not wipe your data. I do that with every update. If you flashed other images, userdata.img, then you device will be wiped
Sent from my Nexus 9 using XDA Free mobile app
Only system and boot..don't know why, but it wiped all
jrosado said:
Only system and boot..don't know why, but it wiped all
Click to expand...
Click to collapse
You didn't have to unlock the bootloader did you? That's the only other reason I can think of that would have wiped your device.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You didn't have to unlock the bootloader did you? That's the only other reason I can think of that would have wiped your device.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, i had to do it..otherwise it would not write the firmware..is there any way to do it without unlock the bootloader?
This is why the first thing you should do when you get a nexus is unlock the bootloader...
Related
Just wondering. I have some friends who are not rooted who said they got update.
Friends on T-Mobile? I believe only AT&T got it.
Sent from my LG-D801 using XDA Premium HD app
that is something im looking for now as well. once its live ill download the whole new file and reroot the thing. bye bye bloat and hello knock code. hopefully this update will fix the random mms issue i have been experiencing lately.
Beginning June 30, the G2 received a software update to Android KitKat 4.4.2/ D80120e. This update provides features and improvements
New Features
Adds KnockOn Security feature
Improvements
Battery expectations: Android 4.4 KitKat
Google Wallet improvements
Google security fixes
Auto brightness improvements
Visual voicemail improvements
Wi-Fi calling improvements
from support.t-mobile.com/
-Sources are available on LG
I got the tmobile update. Had to use lg tool.
Sent from my LG-D801 using XDA Free mobile app
I'm rooted with TWRP and I received a notification that the update was downloaded and ready to install. I'm going to update it manually using the LG Mobile Support Tool just to make sure I don't brick my phone.
Howie Dub said:
I'm rooted with TWRP and I received a notification that the update was downloaded and ready to install. I'm going to update it manually using the LG Mobile Support Tool just to make sure I don't brick my phone.
Click to expand...
Click to collapse
can you let me know if you 1) lose root and 2) lose recovery please?
I just got prompted for the update, but I do not want to download it yet.
frigginmike said:
can you let me know if you 1) lose root and 2) lose recovery please?
I just got prompted for the update, but I do not want to download it yet.
Click to expand...
Click to collapse
In my experience, updating via LG Support Tool wipes everything. I am backing up all my data right now. Hopefully towelroot still works on this version.
EDIT: So I just finished the update via LG Support Tool. My data was left intact, but stuff was broke anyways - probably from using system cleaner app and then not having root after the update. So I am doing a factory reset anyway and will start all over. I expected it to be wiped anyway.
frigginmike said:
can you let me know if you 1) lose root and 2) lose recovery please?
I just got prompted for the update, but I do not want to download it yet.
Click to expand...
Click to collapse
I ended up using the LG Mobile Support Tool to install the update. I wasn't able to install the OTA; it booted into TWRP, then when I rebooted the system, it said I was up to date, even though I was still on 10a. I lost root, but was able to re-root with towelroot. Everything was still there when I booted, although I don't have TWRP recovery. Not sure if I want to do that since I read somewhere that I will lose Knock Code. Make sure you back up your data just in case things don't go smoothly.
rebar71 said:
In my experience, updating via LG Support Tool wipes everything. I am backing up all my data right now. Hopefully towelroot still works on this version.
EDIT: So I just finished the update via LG Support Tool. My data was left intact, but stuff was broke anyways - probably from using system cleaner app and then not having root after the update. So I am doing a factory reset anyway and will start all over. I expected it to be wiped anyway.
Click to expand...
Click to collapse
See if re-rooting with towelroot will fix anything that's broken before you do a complete wipe.
Howie Dub said:
See if re-rooting with towelroot will fix anything that's broken before you do a complete wipe.
Click to expand...
Click to collapse
too late. i thought about that right after i initiated the factory reset.
rebar71 said:
too late. i thought about that right after i initiated the factory reset.
Click to expand...
Click to collapse
But towelroot worked on the new image?
scottricketts said:
But towelroot worked on the new image?
Click to expand...
Click to collapse
yessir. :good:
rebar71 said:
yessir. :good:
Click to expand...
Click to collapse
Oh nice. No downgrade to root process again.
and I do like the knock code functionality. :cyclops:
Hey guys how would you go about doing a fresh install with this or can we not unless we have the full kdz file?
Some cool new stuff. Seems a little boggy... Lookout was killing me so I went to disable it and was greeted by a app management screen. nice
fishman0919 said:
Some cool new stuff. Seems a little boggy... Lookout was killing me so I went to disable it and was greeted by a app management screen. nice
Click to expand...
Click to collapse
If I use KDZ to flash the update, will I loose TWRP? Or do you think a flashable zip file will be made in the future?
I just updated my NON ROOTED d801 g2 and now my touch screen does not work at all. No errors during installation.
I ran into this problem before when I tried to update the touchscreen firmware through the menus via
3845#801#
My screen would go unresponsive, but after 10 mins and a couple of reboots, it would work back (my guess is that it reverted to the old touch firmware).
This time though, the touchscreen seems to be permanently disabled. Anyone else running into this issue?
mackster248 said:
If I use KDZ to flash the update, will I loose TWRP? Or do you think a flashable zip file will be made in the future?
Click to expand...
Click to collapse
Yes, but I believe the new route that's it still works.
Sent from my LG-D801 using XDA Free mobile app
mackster248 said:
If I use KDZ to flash the update, will I loose TWRP? Or do you think a flashable zip file will be made in the future?
Click to expand...
Click to collapse
Yes you will lose TWRP, if you're concerned about that, hold out for the flashable zip, which I'm sure is coming in the next few days.
Hi everyone.
I have the following problem with a Nexus 5: During an update, the system crashed. The phone is now stuck in an endless bootloop, trying to install the update. When left long enough, the update screens eventually come up, but you are immediately blasted with a ton of errors and no matter what you do, you are unable to complete the update. This, however, is not the problem.
I have tried various utilities in order to flash the phone back to factory settings. I have made use of Unified Android ToolKit, as well as Nexus Root Toolkit, but a problem with the phone itself is preventing me from flashing it and the problem is as follows: I can access the phone via USB, as well as the bootloader, but when I unlock the bootloader to start the flashing, it immediately locks itself again and I'm unable to start the flash process.
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Mystical_Titan said:
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Click to expand...
Click to collapse
If the lock state reverts on a reboot, 99 times out of 100, it means the internal memory has an issue. RMA.
rootSU said:
If the lock state reverts on a reboot, 99 times out of 100, it means the internal memory has an issue. RMA.
Click to expand...
Click to collapse
Thanks for the fast response. :good:
Mystical_Titan said:
Thanks for the fast response. :good:
Click to expand...
Click to collapse
No probs. Sounds like the update got stuck at the bootloader flash and corrupted. It's probably not a fatal NAND issue, rather corrupt partition or two but it usually means sending it in.
You can try the LG flashtool as a last resort before doing so though, as you never know...
You can find a link to it in the sticky thread in my signature. Best to stay away from actual "toolkits" though and either use fastboot manually or LG flash tool, although fastboot probably cant help you here - just saying for future ref...
Mystical_Titan said:
Hi everyone.
I have the following problem with a Nexus 5: During an update, the system crashed. The phone is now stuck in an endless bootloop, trying to install the update. When left long enough, the update screens eventually come up, but you are immediately blasted with a ton of errors and no matter what you do, you are unable to complete the update. This, however, is not the problem.
I have tried various utilities in order to flash the phone back to factory settings. I have made use of Unified Android ToolKit, as well as Nexus Root Toolkit, but a problem with the phone itself is preventing me from flashing it and the problem is as follows: I can access the phone via USB, as well as the bootloader, but when I unlock the bootloader to start the flashing, it immediately locks itself again and I'm unable to start the flash process.
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Click to expand...
Click to collapse
happened to me while installing the new SNAPSHOT version of Cyanogenmod, I wiped everything and reflashed it and it works
BruKnowsBest said:
happened to me while installing the new SNAPSHOT version of Cyanogenmod, I wiped everything and reflashed it and it works
Click to expand...
Click to collapse
Can anyone suggest some steps for me to try before I RMA the phone? Although, being unable to unlock the bootloader probably limits my options.
Mystical_Titan said:
Can anyone suggest some steps for me to try before I RMA the phone? Although, being unable to unlock the bootloader probably limits my options.
Click to expand...
Click to collapse
I was stuck in the boot animation and when it opened there was a lot of system errors and it would reboot by itself over and over again.
what fixed it was to do a wipe cache and dalvik and reinstall it
BruKnowsBest said:
I was stuck in the boot animation and when it opened there was a lot of system errors and it would reboot by itself over and over again.
what fixed it was to do a wipe cache and dalvik and reinstall it
Click to expand...
Click to collapse
I tried the 'wipe cache' as well, but it returns a bunch of errors as well. I'm starting to think the NAND is screwed. What is dalvik?
Mystical_Titan said:
I tried the 'wipe cache' as well, but it returns a bunch of errors as well. I'm starting to think the NAND is screwed. What is dalvik?
Click to expand...
Click to collapse
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I completely forgot that you mentioned the LG Flashtool, I feel like such an idiot. I'll try that tomorrow as a last resort.
No worries
Sent from my Nexus 5 using Tapatalk
rootSU said:
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i thought about LG FLASHTOOL but decided to try reinstaling the rom cuz i had no other option since i forgot to leave a backup rom on the device. So I did it as if I was installing a brand new rom Wiped dalvik, cache and system then reflashed the rom and then the gapps. Even tho it was the same ROM file I had a different outcome. It's working fine now but I did go back to the nightlies after it started working again just to be safe.
Now... people may have a different outcome when trying to solve this issue but this actually worked for me after having a minor heart-attack thinking I was gonna lose all my stuff
BruKnowsBest said:
i thought about LG FLASHTOOL but decided to try reinstaling the rom cuz i had no other option since i forgot to leave a backup rom on the device. So I did it as if I was installing a brand new rom Wiped dalvik, cache and system then reflashed the rom and then the gapps. Even tho it was the same ROM file I had a different outcome. It's working fine now but I did go back to the nightlies after it started working again just to be safe.
Now... people may have a different outcome when trying to solve this issue but this actually worked for me after having a minor heart-attack thinking I was gonna lose all my stuff
Click to expand...
Click to collapse
Yes, but your issue is different to the OP's. His bootloader lock state reverts whenever he changes it. This is a pretty much "fatal" issue. What you did cannot help him unfortunately.
rootSU said:
Yes, but your issue is different to the OP's. His bootloader lock state reverts whenever he changes it. This is a pretty much "fatal" issue. What you did cannot help him unfortunately.
Click to expand...
Click to collapse
oh ok, I misunderstood
rootSU said:
No worries
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It speaks about a KDZ file. What is it and where would I find it?
Mystical_Titan said:
It speaks about a KDZ file. What is it and where would I find it?
Click to expand...
Click to collapse
Not sure, never used it. Are you following the Nexus 5 LG Flash tool guide? If not, have a look. You can get to it via my signature
rootSU said:
Not sure, never used it. Are you following the Nexus 5 LG Flash tool guide? If not, have a look. You can get to it via my signature
Click to expand...
Click to collapse
Well, that's that. This phone is done.
Yup. RMA
Sent from my Nexus 5 using Tapatalk
So I'm running completely stock, never rooted Android 5.0 on my Nexus 5. I got the 5.0.1 update today and when I go to install, it gives me the dead android pic with "error". Anybody else having the same issue? Also, would me enabling developer options have anything to do with it?
P.S. Already cleared my cache partition and it's still giving me the error.
Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.
beekay201 said:
Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.
Click to expand...
Click to collapse
or just give it out so we noobs can easily be guided?
beekay201 said:
Oh sweet jesus, how many more threads like this we going to have.
You modified /system in some way. Read one of the million threads already here on the forum with similar problem.
Click to expand...
Click to collapse
Except, like I said, I didn't. I did not root or unlock the bootloader or play around with the phone at all, strictly for this reason. I didn't want to go through the struggle of factory resetting my device every now and then. The closest thing to "modifying" the phone was me unlocking developer settings and I was asking if that could have something to do with it.
Every other thread on the forums has to do with people rooting so no, it's not like one of the millions of other threads.
Describe more.
The best way to update is by flashing the factory image in fastboot, i don`t trust/hate OTA`s personaly
I updated from kitkat to Lollipop with no issues from the OTA update. That was really recent and I haven't changed anything having to do with the system since then. Yet the 5.0.1 update is giving me the error message.
I'm trying to avoid doing a factory reset as that was the main reason that I've kept the phone completely stock. I figured not rooting the phone would let me update in peace and, since it's a nexus, it's been enough to handle my needs without any customization.
kubus908 said:
I updated from kitkat to Lollipop with no issues from the OTA update. That was really recent and I haven't changed anything having to do with the system since then. Yet the 5.0.1 update is giving me the error message.
I'm trying to avoid doing a factory reset as that was the main reason that I've kept the phone completely stock. I figured not rooting the phone would let me update in peace and, since it's a nexus, it's been enough to handle my needs without any customization.
Click to expand...
Click to collapse
Is your bootloader unlocked? I don't know why the ota isn't working but something must have changed on your device
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Is your bootloader unlocked? I don't know why the ota isn't working but something must have changed on your device
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Just double checked and nope, bootloader is locked. Yeah :/ I was trying to see if it's an issue with anybody else on completely stock devices. So far mine is a no go, even though the 5.0 update worked flawlessly. Why would the 5.0 update go through, yet the 5.0.1 believes the system has been modified..?
kubus908 said:
Just double checked and nope, bootloader is locked. Yeah :/ I was trying to see if it's an issue with anybody else on completely stock devices. So far mine is a no go, even though the 5.0 update worked flawlessly. Why would the 5.0 update go through, yet the 5.0.1 believes the system has been modified..?
Click to expand...
Click to collapse
Well, there's a way to get the ota but it is going to be tedious. It involves rooting with towelroot, then using bootunlocker from the play store. That'll allow you to unlock the bootloader without wiping your device. Then you'll need to flash the system, boot, and recovery image with fastboot from the 5.0 factory image. Then do the ota.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Well, there's a way to get the ota but it is going to be tedious. It involves rooting with towelroot, then using bootunlocker from the play store. That'll allow you to unlock the bootloader without wiping your device. Then you'll need to flash the system, boot, and recovery image with fastboot from the 5.0 factory image. Then do the ota.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
May as well skip the ota if you're going to go through this process.
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
digitLIX said:
or just give it out so we noobs can easily be guided?
Click to expand...
Click to collapse
Or wait for the next time the question is asked.
Should be any minute now.
Thanks! I may just wait until the next update and see if there's a chance it'll work. Or I may just have to do a fresh new install which I am not looking forward to at all Lol. But thank you for your help!
Uhhhh, ok. So I'm not exactly sure what happened. I figured I'd give the OTA another try because why not...and it worked I noticed it downloaded a bigger file too, 30ish mb as opposed to the 13mb OTA that would give me an error. Not sure if I got sent a wrong update file or what, but if your issue comes close to what I experienced, just keep trying the OTA update. I'm also on T-Mobile (phone bought directly from T-Mobile) in case that makes any difference.
Hi all,
So I've decided to root my Exynos International Galaxy Note 3 (SM-N900) using Chainfire's CF-Auto-Root. Problem is, Odin gets stuck at cache.img, then fails after a couple of minutes. Phone then displays BSOD whenever I try to boot. I can access download mode again, but not recovery. My phone is stock 4.2.2.
It's the first time I have such a problem, I flashed a couple of phones before without any trouble. I searched XDA for a solution and tried other Odin versions, different cable/ports, even tried on another computer, still doesn't work.
My first concern is not to lose any data as I didn't back anything up. Any help would be greatly appreciated. Feel free to ask about any missing info.
Thanks!
I see. It didn't say on the XDA thread it was only for Lollipop, but I checked in CF's website and you're right. I've wanted to update to LL ages ago but I didn't get it through OTA. The only LL release that's available for SM-N900 in SamMobile is Russian :/ I don't know if I should flash that one...
Would it be safe to flash back my stock 4.2.2 to at least get my phone back working? Or would the Russian release work for me (assuming it has language choice)?
Also, once I choose which ROM to use, would I loose my data when I flash it? I assume it is flashed the same way than root.
Thanks!
Hi, thank you for using XDA Assist. I assume you've seen this,http://forum.xda-developers.com/showthread.php?t=2466423. In regards to flashing a Rom you should always clear data, dalvic cache and cache before flashing. That will erase data so backup first. You should look into titanium backup on the play store.
jd1639 said:
Hi, thank you for using XDA Assist. I assume you've seen this,http://forum.xda-developers.com/showthread.php?t=2466423. In regards to flashing a Rom you should always clear data, dalvic cache and cache before flashing. That will erase data so backup first. You should look into titanium backup on the play store.
Click to expand...
Click to collapse
Yes, that is the thread I've used to flash the root. Now I have a BSOD phone and need to fix it without losing data :/ I didn't back up so I guess flashing ROM is out of the question. Any suggestions ?
GST_Diandre said:
Yes, that is the thread I've used to flash the root. Now I have a BSOD phone and need to fix it without losing data :/ I didn't back up so I guess flashing ROM is out of the question. Any suggestions ?
Click to expand...
Click to collapse
You're not going to like it, but you need to flash the stock firmware in Odin and lose your data. It's the only way to get your device working again.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You're not going to like it, but you need to flash the stock firmware in Odin and lose your data. It's the only way to get your device working again.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I'm surprised. Can you at least explain why the root didn't work? I did everything as stated in the tutorial. I didn't expect a simple root operation would result in me losing everything on my phone; some data I cannot afford to lose.
Also, the phone says that using Kies in recovery mode is what should be done. Kies doesn't recognize the phone as needing repair. Any info?
Thanks !
GST_Diandre said:
I'm surprised. Can you at least explain why the root didn't work? I did everything as stated in the tutorial. I didn't expect a simple root operation would result in me losing everything on my phone; some data I cannot afford to lose.
Also, the phone says that using Kies in recovery mode is what should be done. Kies doesn't recognize the phone as needing repair. Any info?
Thanks !
Click to expand...
Click to collapse
Sorry, but live and learn. Always backup before doing any thing new on your phone. Especially rooting and flashing roms as they sometimes go wrong and rooting bypasses some of the safe guards the manufacture builds into the phone to avoid problems. Kies is crap. Learn to use Odin, if your rooting and roming you'll need it sooner or later. And you're at the sooner stage.
Edit, I'd really try asking your question here, http://forum.xda-developers.com/galaxy-note-3/help. I'm not sure on your device if you can go back to nb1, 4.4.4, firmware. I'm assuming there is no 5.x firmware for your device at this time. You can check at sammobile.com. But Samsung has updated the bootloader with each update and you have to flash the firmware with the same bootloader version. You can't go backwards.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Sorry, but live and learn. Always backup before doing any thing new on your phone. Especially rooting and flashing roms as they sometimes go wrong and rooting bypasses some of the safe guards the manufacture builds into the phone to avoid problems. Kies is crap. Learn to use Odin, if your rooting and roming you'll need it sooner or later. And you're at the sooner stage.
Edit, I'd really try asking your question here, http://forum.xda-developers.com/galaxy-note-3/help. I'm not sure on your device if you can go back to nb1, 4.4.4, firmware. I'm assuming there is no 5.x firmware for your device at this time. You can check at sammobile.com. But Samsung has updated the bootloader with each update and you have to flash the firmware with the same bootloader version. You can't go backwards.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I will, thank you. I can't afford losing anything as of now. Really hope there's a way of getting it to boot back up.
GST_Diandre said:
I will, thank you. I can't afford losing anything as of now. Really hope there's a way of getting it to boot back up.
Click to expand...
Click to collapse
SOLVED. I can't believe how easy it was. I was about to flash it over from scratch but then it struck me.
Chainfire ships Odin with all its root bundles, a version where you cannot untick "Auto Reboot". Because of Auto Reboot being ticked, Odin freezes at "cache.img". It might not freeze for some people but for me, having Auto Reboot activated causes the freeze
Downloading a different version of Odin (any version, I used 3.09) that allows changing parameters and LEAVING EVERYTHING UNTICKED BUT F. RESET TIME works like a charm.
Don't forget to reboot your phone after Odin displays PASS or RESET (Long press power).
I'm going to PM Chainfire about this, and tell a max of people about it.
Thank you for your support
EDIT: Also going to NANDroid my phone. I'm tired of panicking over failed roots
This is an upgrade pathway that worked well for me in upgrading to 5.0.1 originally from KK as I described in THIS post. All the same thanks go out for the original ideas and guidance to: dottat, Dees Troy, and Darth.
The same method works. Even if you're S-OFF, the trick is following the S-ON instructions...that's it.
Find the latest S-ON RUU and instructions HERE.
The latest TWRP (for the HTC One M8) HERE.
The latest SuperSU per the instructions HERE.
Install the S-on 5.0.1 RUU by whatever method you chose from the link above. I used the fastboot method and it did a great job upgrading the stystem. Most importantly, it did NOT wipe my data. You can also use the htc_fastboot.exe in it's extraction directory for all subsequent fastboot operations [highly recommended]. It will reboot and take at least 5 minutes to update all of your applications. At first, it looks like it hangs on the Verizon splash for a minute or three, then it shows you the upgrade of your applications with a count up. How long it takes depends on how many applications you have and how large they are.
Follow the guides to install TWRP and reinstall SuperSU for root. (step 5) I went to the new TWRP page (step 2) and loaded mine by fastboot, then used the new TWRP to flash SuperSU as described.
If you haven't taken the OTA, that should take care of the upgrade nag screens and keep your data intact. If you have, keep reading.
REMINDER: to reflash any tweaks. My favorite package is HERE at the bottom of the links list. It has just about everything I like.
ADDITIONAL INFO FROM dotatt
You also would be wise to note if the user was already getting nagged for the ota they will still be nagged about it even after upgrading this way. Couple more steps needed
Click to expand...
Click to collapse
AND HIS DESCRIPTION VIA PM
If the user doesn't download the OTA and defer it they might be able to get away with it. Once the file is downloaded (and it goes in /cache) the user will need to wipe cache to delete the actual file as well as go into app manager and clear data on the htcdm app. When they enter the software update screen again it should check and show no updates available instead of asking when to install the deferred update.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
If you need to get rid of the nag screen, the update files, and clear htcdm data, you may be able to use THIS (M8vzw OTA Killer updated for Lollipop) tool.
I have a problem and need help, maybe you can help. I was stock but was s-off and took the stage fright update and phone did all the update and when the phone booted it did not go past the Verizon bootup screen, can anybody help me with this? Thanks you.
Sent from my Nexus 6 using Tapatalk
luvtorev01 said:
I have a problem and need help, maybe you can help. I was stock but was s-off and took the stage fright update and phone did all the update and when the phone booted it did not go past the Verizon bootup screen, can anybody help me with this? Thanks you.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I answered your other post. Please only post for help in one thread. Thanks.
Sent from my Nexus 6 using Tapatalk
Thanks for keeping your eyes open, dottat. Good reminder that he'll have to reflash TWRP and SuperSU though. And, he'll have to reflash any tweaks.
homers1 said:
Thanks for keeping your eyes open, dottat. Good reminder that he'll have to reflash TWRP and SuperSU though. And, he'll have to reflash any tweaks.
Click to expand...
Click to collapse
You also would be wise to note if the user was already getting nagged for the ota they will still be nagged about it even after upgrading this way. Couple more steps needed ?
Sent from my Nexus 6 using Tapatalk