Related
The phone received the OTA update this afternoon. After it was updated, every time I try to swipe in at the lock screen, the phone reboots. Based on the lock screen, I can see the phone works just fine. There's notifications, I can scroll to the lock screen widgets and I can even answer phone calls.
The phone was stock/rooted prior to the update. What to do?
Same. Update seems to have finished, bootloops after inputting user password to unlock screen. It's a short boot right back to the password screen again.
Was stock, rooted, unlocked, 4.3 was OTA update
sucinimad said:
The phone received the OTA update this afternoon. After it was updated, every time I try to swipe in at the lock screen, the phone reboots. Based on the lock screen, I can see the phone works just fine. There's notifications, I can scroll to the lock screen widgets and I can even answer phone calls.
The phone was stock/rooted prior to the update. What to do?
Click to expand...
Click to collapse
I was having miscellaneous issues after the 4.3 update as well. I'm starting to think that some of these people who insist on un-rooting your phone prior to system updates might have made a good point. I don't use a lock screen, but I couldn't uninstall any applications or the phone would reboot. Even trying to modify some of the settings would force reboot as well.
I ended up giving up on it and wiping it / flashing 4.3 stock. If anyone is reading this and hasn't updated to 4.3 yet, I would suggest unrooting your phone, but keeping an unlocked bootloader before updating (the update will break root anyway... and OTA Rootkeeper doesn't work). To get root back use TWRP to load SuperSU and you should be back in business.
deusfaux said:
Same. Update seems to have finished, bootloops after inputting user password to unlock screen. It's a short boot right back to the password screen again.
Was stock, rooted, unlocked, 4.3 was OTA update
Click to expand...
Click to collapse
I got really lucky somehow, in getting the phone to work and managing to keep my data.
I don't remember every step in order, as I'm sure lots of them didn't do anything, but eventually I just reflashed every part of the factory images EXCEPT userdata.img as I (correctly?) figured that would erase my ****.
Wiped cache a few times from recovery as well.
Had a couple scares - at one point the LED turned RED during a couple bootup attempts.
First time after the 3rd round of flashing (including system.img) it would not boost past the X. Had to wipe cache in recovery again.
deusfaux said:
I got really lucky somehow, in getting the phone to work and managing to keep my data.
I don't remember every step in order, as I'm sure lots of them didn't do anything, but eventually I just reflashed every part of the factory images EXCEPT userdata.img as I (correctly?) figured that would erase my ****.
Wiped cache a few times from recovery as well.
Had a couple scares - at one point the LED turned RED during a couple bootup attempts.
First time after the 3rd round of flashing (including system.img) it would not boost past the X. Had to wipe cache in recovery again.
Click to expand...
Click to collapse
In the end, I went through almost the exact experience (including red LED). Running on stock 4.3 image now. Thanks.
my phone is reboot today.
there might be problem with rooted stock kernel?
there are someone has same problem?
Acuity said:
I was having miscellaneous issues after the 4.3 update as well. I'm starting to think that some of these people who insist on un-rooting your phone prior to system updates might have made a good point. I don't use a lock screen, but I couldn't uninstall any applications or the phone would reboot. Even trying to modify some of the settings would force reboot as well.
I ended up giving up on it and wiping it / flashing 4.3 stock. If anyone is reading this and hasn't updated to 4.3 yet, I would suggest unrooting your phone, but keeping an unlocked bootloader before updating (the update will break root anyway... and OTA Rootkeeper doesn't work). To get root back use TWRP to load SuperSU and you should be back in business.
Click to expand...
Click to collapse
i got the same issue, look here: http://forum.xda-developers.com/showthread.php?t=2380546
Hello all,
This is yet another bootloop story, although I haven't found anything quite like it yet, hence the idea to post it here for reference and in case some of you have interesting ideas to explore...
This is gonna be a bit long, but TL;DR: After my phone got "spontaneously" stuck into a bootloop, I find that only the stock 4.2.2 rom works, and no other.
So, tuesday I get back home with an empty battery and a Nexus 4 (running latest OTA) that has switched itself of after a day of somehow intense usage. No worries, I plug the AC adapter, let it charge for a bit and switch it back on. Booting seems a bit long, but I have to take care of a few home chores so I let it do its thing before coming back to it a few hours later. Only to find it still displaying the animated nexus logo. After a few switch off/switch on cycles, I understand its pretty stuck and I need to be more radical about it. So I enter the bootloader menu, and OEM unlock the phone (I had never needed to do that) hoping the full wipe associated with that will clear things up.
Well, it didn't. So I guess I'll need to flash a stock rom, and so I do. Since 4.4 is available on Google's stock roms page I try that, the animated logo changes but the end result is the same. So I try again with the latest JB (4.3) and still the same result. I get more than a bit frustrated but it's late and I need some sleep.
The next day, I call Google's warranty desk in France. They tell me that since the phone fell a few month ago, they cannot take it under the warranty program, and so I have to ask LG. Knowing there's no reasoning that will get me past the clerk that answered the phone I hang up after saying I'll get back to them via snail mail. Which I'll probably do soon, because I'm very disappointed with the way that warranty desk works.
Once at work, everytime I have a few spare minutes, I try to reflash with a new tool just in case it does more than automate what I did manually (nexus root toolkit being the one I tried most). It doesn't change a thing and my phone is still a nice animated paperweight.
I don't know why I ended up trying that, but I finally tried flashing the original 4.2.2 rom, and lo and behold, my phone finally got to the SIM code screen ! Everything worked nice after that, so once back at home, I go for the offered OTA upgrade to 4.3. Well, guess what, back to paperweight. Before reflashing 4.2.2, I took the time to flash CWM and activate adb by modifying /system/build.prop in the 4.3 image. This showed a recurrent problem with "system_server" segfaulting at launch (and it might have been caused by hal_sensors_get_list not returning anything, I have no clue). Trying the same on 4.4 yielded the same result.
Back to 4.2.2 and everything works fine, but I get nagged by the OTA notification, and more than that I'm wondering if there's any hope I might understand and fix the problem with my phone.
So, ladies and gentlemen, any clue that would help me is very welcome !
I plan to try a CM rom this week-end to see if it has the same problems as the stock one, but I have little confidence it doesn't. My guess is I have a hardware problem that's non-critical except it triggers a bug in 4.3+...
Thanks for reading !
--
Alain Perry
Same case, mi phone is totally stock and stuck on logo
KRT16S: no luck
I only had the time to try KRT16S this week-end, and this latest update doesn't change a thing. Same symptoms. So I guess I'm stuck on JB 4.2 for the coming week...
Got my S4 4 days ago sprint 4.2.2 MF9 and rooted using odin 1.85, CF-Autoroot by chainfire (CF-Auto-Root-jfltespr-jfltespr-sphl720), CWM flash, then MF9 Odexed hotspot mod (MD5: b1f54ecf82719255ff39eb88d0095ccd). All went well with no error's or issue's, so I did same on 2nd new S4 - same 4.2.2 MF9 for my wife. Made CWM images of both on SD cards. Installed link2sd and foldermount, did nothing else but move movable apk's to SD with link to SD, never used foldermount (yet).
4 day's later my phone froze while texting and re-booted, froze while making a phone call 5 minutes later and re-booted (by itself). After about 6 re-boots it failed to boot and went into a boot loop, making it to the Sprint screen at first and then only to the Samsung logo screen upon subsequent re-boots. Removed battery after the 2nd re-boot (early on), and tried leaving it out for 10 minutes and then half an hour after 6 or 7 re-boot's - no change. Tried restoring from CWM image, showed success but same boot loop. Even tried image from other S4, same results.
Read as many posts as I could, and after study re-flashed stock recovery and stock firmware. Phone still will not boot, but is stuck in boot loop, now with stock recoevry. Other phone with same done to it, same programs (apk's), all exaclty the same is fine. Is it possible that the phone has a hardware problem?! Since I rooted I have 'Custom' now in Download mode so am afraid to take it back for replacement and can't get to boot so triangle away is not possible. Any suggestions, or have I just lost?! Need a phone for work, so don't have much time to play with it, have tried for 2 days now to remedy - but very...well upset :crying: Any thoughts or suggestions?! Thank you!
JJ2013 said:
Got my S4 4 days ago sprint 4.2.2 MF9 and rooted using odin 1.85, CF-Autoroot by chainfire (CF-Auto-Root-jfltespr-jfltespr-sphl720), CWM flash, then MF9 Odexed hotspot mod (MD5: b1f54ecf82719255ff39eb88d0095ccd). All went well with no error's or issue's, so I did same on 2nd new S4 - same 4.2.2 MF9 for my wife. Made CWM images of both on SD cards. Installed link2sd and foldermount, did nothing else but move movable apk's to SD with link to SD, never used foldermount (yet).
4 day's later my phone froze while texting and re-booted, froze while making a phone call 5 minutes later and re-booted (by itself). After about 6 re-boots it failed to boot and went into a boot loop, making it to the Sprint screen at first and then only to the Samsung logo screen upon subsequent re-boots. Removed battery after the 2nd re-boot (early on), and tried leaving it out for 10 minutes and then half an hour after 6 or 7 re-boot's - no change. Tried restoring from CWM image, showed success but same boot loop. Even tried image from other S4, same results.
Read as many posts as I could, and after study re-flashed stock recovery and stock firmware. Phone still will not boot, but is stuck in boot loop, now with stock recoevry. Other phone with same done to it, same programs (apk's), all exaclty the same is fine. Is it possible that the phone has a hardware problem?! Since I rooted I have 'Custom' now in Download mode so am afraid to take it back for replacement and can't get to boot so triangle away is not possible. Any suggestions, or have I just lost?! Need a phone for work, so don't have much time to play with it, have tried for 2 days now to remedy - but very...well upset :crying: Any thoughts or suggestions?! Thank you!
Click to expand...
Click to collapse
Go into stock recovery and hit wipe/factory reset and see if boots up after.
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
BIGSAMDA1ST said:
Go into stock recovery and hit wipe/factory reset and see if boots up after.
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
Click to expand...
Click to collapse
+1.
If doesn't work I suggest to try the one click mf9. You can find it on development section and do a factory reset after. Also that should bring Odin status to normal. It did for me.
Sent from my SPH-L720 using Tapatalk
Further details of whats been tried
BIGSAMDA1ST said:
Go into stock recovery and hit wipe/factory reset and see if boots up after.
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
Click to expand...
Click to collapse
Yes, I neglected to include that I tried wiping cache first, then re-boot attempt, then cleared cache and factory reset, then tried to boot, then wiped cache and factory reset followed by CWM recovery then boot attempt, then cleared cache, re-boot attempt, then all over again and flashed stock - all with no change - boot loop prevailed. What troubles me is that with no other changes the phone froze and re-booted on stock firmware?? And weirder still that once it re-booted the first time it stayed alive for 5 minutes, then 2 minutes, then less than 1, to 'that's all folks' and continued to decrease how far it even went in boot attempt. To the 'slightly informed' like me that seems strange - that's why I was wondering if it could be a hardware failure causing ROM or RAM to be corrupted further with each boot attempt - or - with time 'on'.??
Will try one click mf9 and post back
rimgarciag said:
+1.
If doesn't work I suggest to try the one click mf9. You can find it on development section and do a factory reset after. Also that should bring Odin status to normal. It did for me.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I had not tried that - put myself under the assumption that is was the same as what I had done 'manually' with oden so didn't also try that. With your suggestion I will however - what have I got to loose at this point?! Will post back with results - have to wait until later, meetings call
Downloading it from rwilco12 in the meantime, both rooted no data restore and stock factory restore versions. I will obviously try the stock factory version first as I have wiped already and have no data to loose.
JJ2013 said:
I had not tried that - put myself under the assumption that is was the same as what I had done 'manually' with oden so didn't also try that. With your suggestion I will however - what have I got to loose at this point?! Will post back with results - have to wait until later, meetings call
Downloading it from rwilco12 in the meantime, both rooted no data restore and stock factory restore versions. I will obviously try the stock factory version first as I have wiped already and have no data to loose.
Click to expand...
Click to collapse
This is why when you get new phones always test them out on their full capacity for a week or so. So that you know you dont have a defective device.
Sent from my SPH-L720 using xda app-developers app
Very wise advise
ROMANTiC KiD said:
This is why when you get new phones always test them out on their full capacity for a week or so. So that you know you dont have a defective device.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
The title say's it all - but this is very wise advise for us all! Electronics can suffer from infant mortality issue's, and I would agree 101% with you!
Just curious...By any chance could it be possible that the 4.3 update snuck into your phone and your trying to download MF9?
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
No to 4.3
BIGSAMDA1ST said:
Just curious...By any chance could it be possible that the 4.3 update snuck into your phone and your trying to download MF9?
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
Click to expand...
Click to collapse
I am actually sure it was on 4.2.2 the day it died - still had the notification nag that update was downloaded. I was going to look for how to remove that 'nagging' notification but hadn't yet. Since I rooted the day I got it and installed CWM any OTA update (4.3) should have failed even 'if' I accidently hit the 'system update downloaded' prompt on my notifications screen, which I didn't. The phone had been on for about 4 hours when it first locked and re-booted while texting - and had it updated it would have had to re-boot which I think I would have heard/seen/witnessed some kind of evidence that it had. I think you are going in a good direction though, looking at all possibilities. I know from root checker it rooted successfully and since I made a CWM backup I know stock recovery was gone - so very unlikely 4.3 found it's way in.
Have you tried to boot without the micro SD card installed? The card might have corrupted after you used foldermount and now the phone would t boot.
Sent from my GT-N5110 using Tapatalk 4
Will try removing SD card
cruise350 said:
Have you tried to boot without the micro SD card installed? The card might have corrupted after you used foldermount and now the phone would t boot.
Sent from my GT-N5110 using Tapatalk 4
Click to expand...
Click to collapse
No, I only installed but never opened or set up folder mount so that never even crossed my mind. I just got home and have a few things to try - and I think the first and simplest is removing the SD card! OK, tried that to no avail - boot loop get's to samsung logo and repeats. Tried to clear cache and factory reset with card removed and tried again after battery removal for 2 minutes. Same situation - nothing has changed. Will try 1 step restore next. Downloaded on my laptop but had to leave that with a co-worker for data aquisition project - have to download again here at home.
This is off track, but I have never asked for help and//or participated in a forum like this before. I am happily suprised by the intelligent, thoughtful responses I have recieved so far. Didn't expect anything, but am glad I asked - and even though I am still 'stuck' I have had incredibly good input into potential resolutions for this issue. Thank you all for the assistance so far
The best thing for you to do at this point is to odin a full tar and do a factory reset. To make sure you load the correct one we need to confirm your version. Enter download mode by holding volume down and power. Once it loads, select volume up to enter download mode. The should be a bunch of text lines in the upper left. Look for a line that says knox warranty. If you have that line you are on the mja update. If you don't have that line than you are on mf9. Goto sammobile.com and download the full mf9 tar file through odin and it should return you to full stock unrooted. You may need to do a factory reset in the stock recovery if it doesn't boot all the way. If you do have the knox warranty line than your phone updated to MJA and you need to install that tar instead. Good luck.
Sent from my GT-N5110 using Tapatalk 4
Verified through download mode - no Knox line present
cruise350 said:
The best thing for you to do at this point is to odin a full tar and do a factory reset. To make sure you load the correct one we need to confirm your version. Enter download mode by holding volume down and power. Once it loads, select volume up to enter download mode. The should be a bunch of text lines in the upper left. Look for a line that says knox warranty. If you have that line you are on the mja update. If you don't have that line than you are on mf9. Goto sammobile.com and download the full mf9 tar file through odin and it should return you to full stock unrooted. You may need to do a factory reset in the stock recovery if it doesn't boot all the way. If you do have the knox warranty line than your phone updated to MJA and you need to install that tar instead. Good luck.
Sent from my GT-N5110 using Tapatalk 4
Click to expand...
Click to collapse
Didn't know that line would appear on MJA, but as suspected that line is not in download mode screen's top left verbiage so that gives me confirmation that device didn't sneek from mf9 to MJA.
Late last night I tried both rooted no data restore and stock factory restore 1 click versions from rwilco12. Both appeared to go without a hitch and still after flash and clear cache and factory reset neither allowed the phone to go past the Samsung logo screen. I even tried removing the battery and replaced with that from my wife's S4 to rule out any weird voltage induced issue, but no luck.
I am downloading the L720VPUAMF9_L720SPTAMF9_SPR.zip from sammobile per your suggestion and will give that a whirl. I borrowed a cell phone from a friend who has an extra month of contract with another carrier he is leaving - so actually have a phone to use during this 'downtime' for emergencies - but am begining to wish I had kept my old EVO 3D which never missed a beat. Okay, not really - I like my wifes functioning S4 so far, and her has been fine. I don't even want to think about how stressed I would be right now if it had been her phone that took the dump instead of mine! She simply wants to turn it on and have it work and only appreciates any modifications when every now and then she uses something in front of one of her friends who comments 'cool' I wish I could have/do that with my phone (like hotspot on the boat to a kids tablet).
No luck - bricked or dead phone...
JJ2013 said:
Didn't know that line would appear on MJA, but as suspected that line is not in download mode screen's top left verbiage so that gives me confirmation that device didn't sneek from mf9 to MJA.
Late last night I tried both rooted no data restore and stock factory restore 1 click versions from rwilco12. Both appeared to go without a hitch and still after flash and clear cache and factory reset neither allowed the phone to go past the Samsung logo screen. I even tried removing the battery and replaced with that from my wife's S4 to rule out any weird voltage induced issue, but no luck.
I am downloading the L720VPUAMF9_L720SPTAMF9_SPR.zip from sammobile per your suggestion and will give that a whirl. I borrowed a cell phone from a friend who has an extra month of contract with another carrier he is leaving - so actually have a phone to use during this 'downtime' for emergencies - but am begining to wish I had kept my old EVO 3D which never missed a beat. Okay, not really - I like my wifes functioning S4 so far, and her has been fine. I don't even want to think about how stressed I would be right now if it had been her phone that took the dump instead of mine! She simply wants to turn it on and have it work and only appreciates any modifications when every now and then she uses something in front of one of her friends who comments 'cool' I wish I could have/do that with my phone (like hotspot on the boat to a kids tablet).
Click to expand...
Click to collapse
Downloaded and tried L720VPUAMF9_L720SPTAMF9_SPR.zip from sammobile. Odin process went flawlessly as always, no errors, started process after clear cache and factory reset - followed by battery removal for 10 minutes, then turned on phone directly into download mode and odin''d. Re-boot revealed same behavior, tried clearing cache and factory reset again, then battery removal, no luck - looks like I have an unrecoverable phone :crying: At this point I have samsung recovery and firmware so it's going back. I will give my replacement a good week to wring itself our before trying anything with it. On a positive note, my wife's S4 which was an exact replica of this unit continues without missing a beat. This gives me some confidence that it wasn't CF root process or CWM recovery that caused this issue. I am still very nervous going forward but after 6 phones and 3 tablets successfully rooted with custom recovery and no other issues over the last 2 1/2 years i would like to think this really was a hardware failure.
JJ2013 said:
Downloaded and tried L720VPUAMF9_L720SPTAMF9_SPR.zip from sammobile. Odin process went flawlessly as always, no errors, started process after clear cache and factory reset - followed by battery removal for 10 minutes, then turned on phone directly into download mode and odin''d. Re-boot revealed same behavior, tried clearing cache and factory reset again, then battery removal, no luck - looks like I have an unrecoverable phone :crying: At this point I have samsung recovery and firmware so it's going back. I will give my replacement a good week to wring itself our before trying anything with it. On a positive note, my wife's S4 which was an exact replica of this unit continues without missing a beat. This gives me some confidence that it wasn't CF root process or CWM recovery that caused this issue. I am still very nervous going forward but after 6 phones and 3 tablets successfully rooted with custom recovery and no other issues over the last 2 1/2 years i would like to think this really was a hardware failure.
Click to expand...
Click to collapse
I haven't tried this and not sure of the possibility of it working but if you could establish a connection via fastboot or download mode to a computer running adb you could be able to pull the log from dev/log/ and see exactly what is going wrong.
Look here http://stackoverflow.com/questions/12995030/how-to-use-adb-pull-command for info on pulling files in adb
Sent from my SPH-L720 using XDA Premium 4 mobile app
Returned phone, Sprint tried to factory reset and a few other things they didn't seem to want me to see and then declared phone dead. Updating this post on my replacement S4 which I plan on using heavily for a couple weeks before doing anything with!! At that time I guess I will use CF root and CWM only because that's what I have used on my wife's without issue...have to say I am quite nervous after what happened, mostly because I don't have a solid idea of what in the world happened!...I see many are using Phil's touch but don't see any reason to try something different based on my 'issue'. If anyone is still following this post and has an opinion on the safest route other than what I did take I'm open to suggestions! Thanks for checking back...
Sent from my SPH-L720 using xda app-developers app
HELP
JJ2013 said:
Returned phone, Sprint tried to factory reset and a few other things they didn't seem to want me to see and then declared phone dead. Updating this post on my replacement S4 which I plan on using heavily for a couple weeks before doing anything with!! At that time I guess I will use CF root and CWM only because that's what I have used on my wife's without issue...have to say I am quite nervous after what happened, mostly because I don't have a solid idea of what in the world happened!...I see many are using Phil's touch but don't see any reason to try something different based on my 'issue'. If anyone is still following this post and has an opinion on the safest route other than what I did take I'm open to suggestions! Thanks for checking back...
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
ing same issue
So you didnt fix it?, im having same issue, after battery died it wouldnt turn on again and got stuck in a boot loop, i was running G.E. 4.4.2 and i had CWM philz touch, now i did everything, f reset wipe all cache, tried without sd card, restored via CWM to 4.4 stock, restored via odin to 4.4 now i did to touchwiz cause i thought it may has been ROM problem, and still stuck in boot logo, anyone? i think i lost warranty causa its was rooted cant return it
mndbtt said:
ing same issue
So you didnt fix it?, im having same issue, after battery died it wouldnt turn on again and got stuck in a boot loop, i was running G.E. 4.4.2 and i had CWM philz touch, now i did everything, f reset wipe all cache, tried without sd card, restored via CWM to 4.4 stock, restored via odin to 4.4 now i did to touchwiz cause i thought it may has been ROM problem, and still stuck in boot logo, anyone? i think i lost warranty causa its was rooted cant return it
Click to expand...
Click to collapse
No garantee, but I had rooted mine before it went haywire and bootlooped. When I took it in they had the phone for 15 minutes in the back out of my site - expect they went into download mode and could see it was not original (rooted) but replaced it anyway without any fanfare. BTW, after 3 weeks with the new device I rooted it as before - this time using TWRP becouse I had recently helped a friend root a tablet and used TWRP recovery - liked it so... In any case, I have had my rooted S4 (#2) running without issue ever since.
Hey guys, let me start off by telling you I was running stock 12b rooted with the 1.5 Furnace kernel. Been running that for 2 weeks solid, no problems. I added 2 Xposed modules last night, swiftkey something and the one to remove the "full battery notification". I rebooted last after enabling them and the phone was fine. Charged phone last night, took it off charger (working fine) and decided to reboot it. Big mistake! It just bootlooped. It would start for 10 seconds, no wifi no data and then restart. I honestly did nothing......
I got into recovery and tried to restore my nandroid backup but same issue. Right now I am flashing 12b from the LG Flash Tool. Will that fix it? Is there another way?
Thanks for all your expertise
Tried to use the LG Flash Tool and it didn't work. Anyone got any ideas how to get my phone to stay working? It boots, for 10 seconds then reboots
If you think it's something to do with xposed why not flash the xposed disabler zip in recovery? Also have you tried a simple wipe of cache and dalvik?
Sent from my LG-D802 using Tapatalk
I finally got the Flash tool to work and got 11a loaded on. So now I am fully stock and unrooted. But, the phone keeps rebooting. Doesn't make any sense. Anyone have any ideas?
tattooz305 said:
I finally got the Flash tool to work and got 11a loaded on. So now I am fully stock and unrooted. But, the phone keeps rebooting. Doesn't make any sense.
you ned to clear cash on stock you can only do that by do a factory hard reset.
https://www.youtube.com/watch?v=3ogBvzbPikc&feature=youtube_gdata_player
Click to expand...
Click to collapse
tumebone said:
tattooz305 said:
I finally got the Flash tool to work and got 11a loaded on. So now I am fully stock and unrooted. But, the phone keeps rebooting. Doesn't make any sense.
you ned to clear cash on stock you can only do that by do a factory hard reset.
https://www.youtube.com/watch?v=3ogBvzbPikc&feature=youtube_gdata_player
Click to expand...
Click to collapse
Thanks for replying. I did a factory reset. Phone boots and hangs on activation for a couple seconds then reboots. Any other ideas?
Click to expand...
Click to collapse
I have a similar problem when restart the phone gets in bootloop. when the phone is operating normally burst without rebooting or any other problems. I'm all factory on it's still 802 10b and does not offer me the option to update the phone. I think it's a software error I have a warranty but I can not wait 30 days to fix my phone
I hope you understand this is a google translate
Sent from my Nexus 7 using Tapatalk
tattooz305 said:
tumebone said:
Thanks for replying. I did a factory reset. Phone boots and hangs on activation for a couple seconds then reboots. Any other ideas?
Click to expand...
Click to collapse
Any luck fixing this? I Have the exact same issue with my ls980(Sprint Variant). I've flashed multiple roms, kernels, and radios with no luck. Used LG Flash tool and it always fails at 94%( when it reboots the phone). However, my phone does say unrooted afterwards. I've also tried wiping all data/ factory reset. No luck.... The phone comes on and doesn't recognize any touch for a long time. Finally, it unlocks, and reboots minutes later. No apps or widgets work. The phone only stays on for so long because I turned on the stay always awake option in developer options. Any help would be greatly appreciated!
Click to expand...
Click to collapse
Unfortunately, I did not find a solution. Amazingly, the only rom that would load was Madallus so that is what I am running. You could try that and see if it will load.
Verizon Note 3 here, I received the Lollipop ota today and thought no harm in taking it as I was already stuck without root on 4.4.4.
It worked ok for the first couple minutes, then a reboot, then same thing, about 5 minutes and a reboot. Sometimes ~2 minutes, seems using it in any situation made the reboots happen. I did a factory reset thinking that would clear things up. Unfortunately now it is even worse, as it's rebooting anywhere from the first touch to the screen, to about 15 seconds of activity, literally dozens of reboots.
I downloaded the update on my pc and installed via Odin hoping that the ota was just corrupted or some bad luck like that. Nothing changed at all.
It will idle after booting just fine, I just can't do much of anything, every touch of the screen feels like a roll of the dice. Every few reboots or so I can make it to settings maybe but haven't been able to actually change much of anything, not that it would seem to matter here.
I've flashed via Odin twice, cleared the cashe many times, factory reset 3 or 4 times. Am I screwed here? What else to try?
*UPDATE* I flashed back to 4.4.4 with Odin and no more issues. It appears that my device alone is completely incompatible with the new firmware.
I should also note that I tried airplane mode, safe mode, and removing the sd card with no improvements.
After hours of messing with this thing and nearly giving up, not half an hour after I post here for help, I seem to have found a solution, although hopefully not a permanent one. The problem was happening when I would touch the screen, not scrolling ever, but making selections. On a whim I turned off sound and bam, no crashes.
I would still love it if someone had some insight about this problem, or better yet a solution.
I'm not sure yet if it is just the keypress sound that is killing it, or all sounds. I never did have any issues with the stock keyboard clicks now that I think of it, only the menu press sound. In any case it's not every time it made the sound, just half the time or so. Anything anybody could add to this would be appreciated.
*Edit* Not a solution, but it did help.
Well it's not as stable as I'd hoped. More like before the first factory reset now, but still not good at all. The various sounds definitely trigger crashes quickly(menu options, volume pings, mp3 songs from sd card), but regular silenced menu presses do sometimes as well still. Phone also bootloops several times often before it can get booted stable and 100% always crashes immediately if I try to unlock the screen in the first 5-10 seconds after booting up. Not sure if I'll be able to call or text as it's too late to test that atm. I'll update tomorrow, any insight appreciated.
I would say a bad download but I don't remember if ODIN checks MD5 sums (pretty sure it does). I would do a full wipe and reflash the stock image with odin
I am 100% stock not rooted never been rooted 5.0 vzw and I have had a couple of reboots. Never ever had one on this phone before. My old note 3 was rooted but I got this replacement after the root exploits had all been closed.
ehh not all have been closed
What is the root exploit for Verizon Note 3 with 5.0?
recDNA said:
What is the root exploit for Verizon Note 3 with 5.0?
Click to expand...
Click to collapse
None at the current time but CVE-2014-8609 seems like it could be some use
I spoke too soon when I said the phone was usable now. At best 5 minutes of light use as anything seems to crash it now. I did get a fresh image and used it with Odin with exactly the same result which makes me think its my phones hardware or something. Just seems crazy that it was working just fine before the update. The reason I pushed to 4.4.4 and lost root is because my phone suddenly started an issue where it would crash when making or receiving calls. It wasn't caused by any new apps or anything, just out of nowhere. I tried everything then updated as a last resort, carelessly I went to 4.4.4 instead of staying at 4.4.2 and lost chance of root, but it solved the problem I was having. I wonder if the issue is related somehow.
I was able to odin back to 4.4.4 and it's working fine so far, I assumed that you would not be able to revert back like the last ota and just tried it as a nothing to lose last effort. This is very important news to anybody that is having major issues with 5.0. Maybe, just maybe I'll try it again if they make an update patch for reported issues.
But for now, 4.4.4 it is for me.
VZW Note 3 update to Lollipop
I just finished the Lollipop update and my phone is working great for the past 30 minutes. Seems a little slower then usual but have had no issues besides my phone locking up after downloading the update, may have been due to my phone running down to 14%, but after removing the battery for 20 secs and putting it back on, phone came back on, I plugged into charger and started the update. Will post later if I have any issues.
I have been trying unsuccessfully through odin to downgrade but it keeps failing in odin, I downloaded the official firmware from sammobile.
Just curious if u r tried reinstalling newer odin? Try different USB port and cable. At this point maybe even try different pc if u have access to 1