Hi all
My Note 4 screen has started locking up (i.e. continuing to work in the background and the screen is still responding to system events (SMS notifications etc) but it is not responding to touch.
I have tried several factory resets, after which the screen stays responsive for about 3 or 4 pages, then locks up again.
Background: the phone was rooted about a year ago, to get around the SD card restriction, and has worked fine up until the last week. I gave the phone to a friend who put CWM-based recovery manager and the latest Samsung Android 5.1.1 on it. After setting the phone up successfully and downloading all my apps on to it and getting everything running perfectly, I used CWM to back up the OS image onto the SD card.
Phone worked great for about a day, then started freezing. Wiping the caches / restoring / factory resets and all permutations of these have so far proved ineffective...
Any pointers or suggestions gratefully received :fingers-crossed:
Vaughan
v00n said:
Hi all
My Note 4 screen has started locking up (i.e. continuing to work in the background and the screen is still responding to system events (SMS notifications etc) but it is not responding to touch.
I have tried several factory resets, after which the screen stays responsive for about 3 or 4 pages, then locks up again.
Background: the phone was rooted about a year ago, to get around the SD card restriction, and has worked fine up until the last week. I gave the phone to a friend who put CWM-based recovery manager and the latest Samsung Android 5.1.1 on it. After setting the phone up successfully and downloading all my apps on to it and getting everything running perfectly, I used CWM to back up the OS image onto the SD card.
Phone worked great for about a day, then started freezing. Wiping the caches / restoring / factory resets and all permutations of these have so far proved ineffective...
Any pointers or suggestions gratefully received :fingers-crossed:
Vaughan
Click to expand...
Click to collapse
You do have a Developer Device , right?
Sent from my SM-N910V using Tapatalk
jpcalhoun said:
You do have a Developer Device , right?
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Not sure what you mean.. I am not a developer yet, just an interested amateur.
I took the phone in to a repair shop last night, the guy reckoned the problem was down to a poor screen replacement, and they hadn't used the correct bonding cement, and that the screen had separated from the LCD such that capacitance couldn't do its thing.
However if this were the case, the screen would not work at all, even briefly after a system reset.
v00n said:
I took the phone in to a repair shop last night, the guy reckoned the problem was down to a poor screen replacement, and they hadn't used the correct bonding cement, and that the screen had separated from the LCD such that capacitance couldn't do its thing..
Click to expand...
Click to collapse
I should add that the repairer is simply dismantling and rebuilding the phone to see if it's a loose/dirty connector somewhere. He's not going to try to fix it with firmware/software.
v00n said:
I should add that the repairer is simply dismantling and rebuilding the phone to see if it's a loose/dirty connector somewhere. He's not going to try to fix it with firmware/software.
Click to expand...
Click to collapse
The retail version of the Note 4 cannot be rooted, only the Developer Edition of the Note 4 can be rooted and only the Developer Edition has an unlocked bootloader which will allow the installation of a custom recovery like twrp and root. There are a couple of ways to tell if you have a developer device but the fastest is to remove the battery and see if the words "Developer Device" is printed on the phone's casing. If you don't see "Developer Device" printed then you don't have a developer device so you cannot root the phone, you cannot install twrp or other custom recovery and you cannot install a custom ROM.
jpcalhoun said:
The retail version of the Note 4 cannot be rooted, only the Developer Edition of the Note 4 can be rooted and only the Developer Edition has an unlocked bootloader which will allow the installation of a custom recovery like twrp and root. There are a couple of ways to tell if you have a developer device but the fastest is to remove the battery and see if the words "Developer Device" is printed on the phone's casing. If you don't see "Developer Device" printed then you don't have a developer device so you cannot root the phone, you cannot install twrp or other custom recovery and you cannot install a custom ROM.
Click to expand...
Click to collapse
I posted this question in the wrong forum. I am in the UK, I bought the phone directly from Samsung UK the day it came out. It is not a Verizon phone. If I could find a way to delete or lock off this thread I would.
I have now re-posted the question in the main Note 4 forum.
Related
I attempted a root on Samsung Note 2 Sprint version (in white). Followed all steps, however phone got stuck in a reboot loop right after I put the option 2 (root only) Odin step in. Sprint ver LPH889 (I believe that is what Odin is calling it, option 72). Toolkit used was ADB 4.1.0.
Original symptoms were that the Android updater was looping trying to load everything; being new I made it worse and tried recoveries and reloads which also failed. Now it boots, goes to splash, circling blue oval image and...it stays there.
Good news: I have access to download mode and recovery reset mode (including sideloading).
Bad news: every thread I've followed has given me an issue.
I have recovery access but I need some idea of where to go from here and searches have shown near but not exact symptoms. I have unplugged it from the pc, removed the battery, done a factory reset, attempted to reflash via Odin (root) attempted to reflash stock via Odin and so far I am still stuck in a reboot loop. Windows detects the phone but shows a problem in device manager because possibly it won't stop rebooting. Any help you can provide is appreciated and if at all possible I need to recover some form of working phone here, and soon. My girl needs it for work and Sprint's network in my area barely works from day to day (which they admit but don't credit my account for). This phone has problems sending/receiving calls, they claim it's fine, and I was forced to try a root to get some form of working device. That failed too.
I'm a newb at this...it's been years since I flashed a phone (Razor v3), so...any help would be appreciated, otherwise I have to crawl to sprint/samsung and get it replaced, which I don't want to do. Thanks.
doesitwork? said:
I attempted a root on Samsung Note 2 Sprint version (in white). Followed all steps, however phone got stuck in a reboot loop right after I put the option 2 (root only) Odin step in. Sprint ver LPH889 (I believe that is what Odin is calling it, option 72). Toolkit used was ADB 4.1.0.
Original symptoms were that the Android updater was looping trying to load everything; being new I made it worse and tried recoveries and reloads which also failed. Now it boots, goes to splash, circling blue oval image and...it stays there.
Good news: I have access to download mode and recovery reset mode (including sideloading).
Bad news: every thread I've followed has given me an issue.
I have recovery access but I need some idea of where to go from here and searches have shown near but not exact symptoms. I have unplugged it from the pc, removed the battery, done a factory reset, attempted to reflash via Odin (root) attempted to reflash stock via Odin and so far I am still stuck in a reboot loop. Windows detects the phone but shows a problem in device manager because possibly it won't stop rebooting. Any help you can provide is appreciated and if at all possible I need to recover some form of working phone here, and soon. My girl needs it for work and Sprint's network in my area barely works from day to day (which they admit but don't credit my account for). This phone has problems sending/receiving calls, they claim it's fine, and I was forced to try a root to get some form of working device. That failed too.
I'm a newb at this...it's been years since I flashed a phone (Razor v3), so...any help would be appreciated, otherwise I have to crawl to sprint/samsung and get it replaced, which I don't want to do. Thanks.
Click to expand...
Click to collapse
What method are you using to root.....I used the "toolkit" and had no problems at all.
http://forum.xda-developers.com/showthread.php?t=1957155....try this if you haven't already
vel7wil said:
What method are you using to root.....I used the "toolkit" and had no problems at all.
http://forum.xda-developers.com/showthread.php?t=1957155....try this if you haven't already
Click to expand...
Click to collapse
I thought it would to but I did not want to dig through 70+ pages of the thread when searching failed...unless I really needed to. Most of it is old and doesn't apply.
I was directed by the referenced Youtube vid. I used the options referenced for the phone in this thread with that toolkit. I backed up existing files (not as one unit, but internal files and I think OS), went for the option 2, followed the instructions and things went great through odin...until android went to update and started looping with the 'updating files' percentages. At that point I tried to restore to basic and started clearing caches and such and that is how I got to where I am.
When that failed I started looking at the leaked stock flash and that failed on shoot.ini which that guy never addressed because he thought his international version was all versions (that's why I choose 'doesitwork?' as screen name ). So i'm down to sideloading or something. I really need guidance, and I emailed the toolkit author but I'm still waiting on a reply.
Any thoughts?
doesitwork? said:
I thought it would to but I did not want to dig through 70+ pages of the thread when searching failed...unless I really needed to. Most of it is old and doesn't apply.
I was directed by the referenced Youtube vid. I used the options referenced for the phone in this thread with that toolkit. I backed up existing files (not as one unit, but internal files and I think OS), went for the option 2, followed the instructions and things went great through odin...until android went to update and started looping with the 'updating files' percentages. At that point I tried to restore to basic and started clearing caches and such and that is how I got to where I am.
When that failed I started looking at the leaked stock flash and that failed on shoot.ini which that guy never addressed because he thought his international version was all versions (that's why I choose 'doesitwork?' as screen name ). So i'm down to sideloading or something. I really need guidance, and I emailed the toolkit author but I'm still waiting on a reply.
Any thoughts?
Click to expand...
Click to collapse
When used the toolkit a year ago, I found that I had to turned off all firewalls and antivirus apps for it to work properly. Once I did that it worked fine....give it a shot...can't hurt......might even be able to repair what you've done so far.....Good Luck!!!
I'll give this my best shot...download a rooted rom from the development section and place it on your SD card.
Download toolkit from here (I take no credit for this) http://d-h.st/iu0
Put phone in download mode.
Open ODIN and uncheck "auto reboot". Then click "PDA" and add the .tar file (recovery).
Plug phone into PC (make sure to have samsung drivers installed).
Once ODIN sees the phone you can click "start".
When the recovery flash is complete, pull your battery to ensure power down.
Boot into recovery : volume up, home, power all at the same time.
Flash rooted rom.
Toolkit is an extra and unnecessary step.
http://rwilco12.com/downloads.php?d...ung Galaxy Note II (SPH-L900)/Stock ROMs/MC2/
Grab the one click flavor of choice. Use the one with 1090526 in the name as that's the full version.
Open in windows, put phone in download mode and flash. Easy Peasy.
Let me know if you have any issues with this.
Sorry for the late reply, I had some issues with the "catchpa".
The one click fix worked like a charm, thank you! I will soon be making a contrib to the site. It's a shame I couldn't root as easily :laugh: .
I know the level of work that goes into this stuff and the desire to keep on top of new gear while maintaining support for the old and I appreciate the community coming to my aid, so again, thank you!
---------- Post added at 08:14 AM ---------- Previous post was at 07:36 AM ----------
[/COLOR]
doesitwork? said:
Sorry for the late reply, I had some issues with the "catchpa".
The one click fix worked like a charm, thank you! I will soon be making a contrib to the site. It's a shame I couldn't root as easily :laugh: .
I know the level of work that goes into this stuff and the desire to keep on top of new gear while maintaining support for the old and I appreciate the community coming to my aid, so again, thank you!
Click to expand...
Click to collapse
It is usually a pretty common courtesy to hit the "thanks button" when someone helps you out.
I am not at all trying to be mean, just letting you know.
garwynn said:
Toolkit is an extra and unnecessary step.
http://rwilco12.com/downloads.php?d...ung Galaxy Note II (SPH-L900)/Stock ROMs/MC2/
Grab the one click flavor of choice. Use the one with 1090526 in the name as that's the full version.
Open in windows, put phone in download mode and flash. Easy Peasy.
Let me know if you have any issues with this.
Click to expand...
Click to collapse
hello @garwynn im trying to do this same thing.. its been so long since ive odin'd, how would i put TWRP on this now after these steps? i tried goomanager and that didnt work. (couldnt find recovery) and i tried flashing in stock recovery and got a fail . im kind of lost right now and am wondering if there is another way or do i have to do the toolkit? thanks
edit: for some reason, the tool kit links have been pulled by a mod. ..but this video helped me get twrp back. phew. zedomax to the rescue.. http://www.youtube.com/watch?v=7leb9OznhqY
I just got this tablet a couple of days ago and I am having a lot of problems with it. None of the sprint apps are installed, and the "preparing network" thing just sits at the top of the screen and will not go away. I want to go and get it replaced, but it is hard to find a sprint store where I can park a 75 foot long truck. So I thought that the issues might be due to the firmware having errors or maybe a bad flash at the factory. I also am unable to update the PRL or the profile. I have been searching for answers to this problem for 2 days now.
Somebody please help!
ewkabel said:
I just got this tablet a couple of days ago and I am having a lot of problems with it. None of the sprint apps are installed, and the "preparing network" thing just sits at the top of the screen and will not go away. I want to go and get it replaced, but it is hard to find a sprint store where I can park a 75 foot long truck. So I thought that the issues might be due to the firmware having errors or maybe a bad flash at the factory. I also am unable to update the PRL or the profile. I have been searching for answers to this problem for 2 days now.
Somebody please help!
Click to expand...
Click to collapse
no but if you are flashing stock why not just use kies? Kies will def. not trip it..
NJ_RAMS_FAN said:
no but if you are flashing stock why not just use kies? Kies will def. not trip it..
Click to expand...
Click to collapse
I think that I finally resolved the issue. I had to do a complete factory reset.
***WARNING***
You will loose all of your data when you do the following reset.
I had to use a utility to retrieve the MSL. (I found it in another thread, but don't remember which one.)
Next I entered the following into the calculator app to get to the factory mode screen:
(+30012012732+
Then in the factory mode app I typed:
##786#
Then I entered the MSL and followed the prompts to reset.
The tablet rebooted, did an erase in recovery, rebooted again, then went through the initial setup and activation process. After that everything was good. I am waiting for all of my apps to reinstall now.
I was going to flash with Oden but my laptop is down now too. So the above mentioned method is the best.
Just so that everyone knows, by resetting the tab to bare bones and flashing the OEM Rom, it will set the tab to as new state, meaning you will have to enter all the information that was require when you first powered up the tab. So, if one were to go to download mode it will show original.
Here's the issue, that I've resolved, but I'm looking for a reason why this happened.
Have a Galaxy Note 10.1 (2014 Edition) running Android 5.11, rooted and running xposed.
Arrived home a few days ago and my PIN is no longer recognized to unlock the device. I been using the same pin for months and nothing of any significance had changed on the device. A couple of days earlier I had upgraded busybox and a certificate I use for an email account had expired, but I've restarted the device and used the lock screen pin multiple times after both events. Very strange that the device just stopped recognizing the pin as the correct one.
Anyway I was, fortunately, able to find a way to get into the device and authorize adb connections and took care of the issue (without having to reflash anything).
Anyone have any ideas why the device would just stop allowing the pin to unlock the device?
Mark
mlutzow said:
Here's the issue, that I've resolved, but I'm looking for a reason why this happened.
Have a Galaxy Note 10.1 (2014 Edition) running Android 5.11, rooted and running xposed.
Arrived home a few days ago and my PIN is no longer recognized to unlock the device. I been using the same pin for months and nothing of any significance had changed on the device. A couple of days earlier I had upgraded busybox and a certificate I use for an email account had expired, but I've restarted the device and used the lock screen pin multiple times after both events. Very strange that the device just stopped recognizing the pin as the correct one.
Anyway I was, fortunately, able to find a way to get into the device and authorize adb connections and took care of the issue (without having to reflash anything).
Anyone have any ideas why the device would just stop allowing the pin to unlock the device?
Mark
Click to expand...
Click to collapse
Can you please point me in the direction of a good guide to follow to root my p607t on official 5.1.1?
I've looked all over the place and there's no real confident answer out there and I'm afraid to mess anything up, cause boot loops, ect. I've got lots of experience rooting Androids in the past but this specific T-Mobile modem sounds like it is super picky.
Much thanks to anybody who can help :good:
Galaxy_Guardian_S said:
Can you please point me in the direction of a good guide to follow to root my p607t on official 5.1.1?
I've looked all over the place and there's no real confident answer out there and I'm afraid to mess anything up, cause boot loops, ect. I've got lots of experience rooting Androids in the past but this specific T-Mobile modem sounds like it is super picky.
Much thanks to anybody who can help :good:
Click to expand...
Click to collapse
Sorry for the delay in response, autoroot works great. Just find the closet match to the lt...
I feel like this should be obvious, but I'm unable to find the OEM Unlock switch under Developer Options on a Galaxy Tab Pro 8.4, SM-T320.
I must have found it once before because I rooted and installed Android 7.1 on the same model (different tablet) last fall. But for whatever reason, it's eluding me on this one. Apparently, on Samsung devices, that switch is hidden; to reveal it, you need to turn off automatic downloads and auto date and time, restart, open Developer Options, and so on, but there is no switch for automatic date and time anywhere on this menu, which is unlike any other I've seen on an Android device.
I have USB Debugging checked, but the tablet won't root, and it seems that unlocking the bootloader is the sticking point. And it's driving me nuts. As noted, I must have done this with the other tablet, but I can't find that switch on that tablet either -- and it would look different anyway, since it's not the tablet's stock Android.
Please help? Any suggestions will be appreciated.
I found another web page on which it simply says to check USB Debugging. I had done this before, but unchecked and rechecked it to be sure. Then I tried to root once more, using the file:
CF-Auto-Root-mondrianwifi-mondrianwifixx-smt320.tar
...which worked on my other tablet last fall and again tonight. Still, the tablet isn't rooted. I cannot figure out what I'm missing.
Well, a few more hours and attempts later, the tablet still wasn't rooting, so I started the tablet in recovery mode and reset it to factory before trying it again. This time, it worked! Clearly, there was something (an app, perhaps?) that was getting in the way. I still don't know where that OEM Unlock switch is, but I no longer care.
From feeble memory, I recall having one tablet (only one, an SM-T520) that would only do what I wanted by first flashing it back to stock. From there, everything was fine. I have another SM-T520 and a couple of SM-T320's, any of which couldn't care less what I do to them.
I guess that's the fail-safe position. Since I was installing a newer build anyway, it didn't matter. It just seemed odd since the other SM-T320 rooted just fine without that extra step. I wish I'd thought of it sooner, but that's water under the bridge.
BTW, if those other tablets work and you're interested in selling one of them, drop me a PM. And if not, no worries; I just thought I'd ask.
Do you have a link as to where I can download twrp flash recovery for tab pro 8.4? It seems like it needs a tar.md5 file.
Thank you!
wcerin said:
Do you have a link as to where I can download twrp flash recovery for tab pro 8.4? It seems like it needs a tar.md5 file.
Thank you!
Click to expand...
Click to collapse
Look here: https://eu.dl.twrp.me/mondrianwifi/
3.4.0-0 available as tar file.
Hi,
I have applied firware update for years without problems but today I am stumped.
I tried to update todate from 6ETLL firmware to the newer 6FUBD both Android 11.
Set up Odin using 3.14.4 and started ok.
Then I had the install stopping and disconnecing to the phone.
Eventually I disconnected the phone lead and it now wont boot passed the error message -
An error has occurred while updating the device software.
Use the Emmergency recovery function in the Smart Switch PC software.
So I installed this on my pc it it fails to recognise the phone even in Emmergency recovery mode.
I have tried all methods of trying to reboot the phone but it always comes back to the above arror message and wont go into recover mode or download mode.
I did not but this from O2 but directly from Samsund and its just out of warrantee.
I dont know wheer the service center is in the Uk and thats a lst resort anyway.
Any suggestions please.
Repaste from my other reply on the UI3 update :
"
Odin hates thunderbolt - If you plan on using a USB-C port make sure it's not thunderbolt. It will fail half way in and freeze. Get a well rated cable and do it via USB concentrator directly
If you get stuck and you cannot access recovery via key combo or smartswitch emergency recovery use Odin
Open options and select get device info - It will reboot directly to the recovery if it was previously written (check the log). After that disable the get device info option and reconnect the cable (select files for flashing again - should go smoothly.
If after the reboot and setup you get a moisture warning on the USB port - this does not make nay sense but it works - Turn off the Note, plug in a usb cable on the PC and reboot the phone connected to the cable - It will reset the sensor warning and should work flawlessly.
Hope to have helped - Had a bit of a jarring adventure setting this one up this time.
The lag in the animation is there, however, I think it's the animation timer that is set higher (slower) it's not slow "per se" but it shows. "
Bomm,
I must say.... I dont know how to thank you. Your post saved my Note 10.
I emailed Samsung repair and after 2 days they said phone xxxxx if you need it repaired under warrantee.
I waited a week for the phone to lose its battery and when booted back on charge cane up with the same error.
So I went back on xda and you had kindly posted the exact fix I needed. I didn't expect that. I know now if I have the same issue again. It was my pc I think using usb-c to usb-c like you said. Thank you so much.
I didn't get any warnings at all. booted up fine.
Johny1fin said:
I didn't get any warnings at all. booted up fine.
Click to expand...
Click to collapse
had the same issue. I was stumped at first too
I've tried all the posts but when I say start in odin, the phone restarts and gives an error
As you say you are super, my friend, I applied it step by step, the phone entered the download mode.
Not sure why you want Q or above on the 10+.
I'm still running on Pie/One UI. Fast, very stable and zero issues. Last reload was back in June.
If the OS is running well and fulfilling its mission let sleeping dogs lie.
One issue is if we don't keep up to date then at some point Samsung will stop support on a particular phone and the phone can be years out if date.
They may then be on a version unsupported by the apps suppliers and will be more difficult to sell if you want to buy a new phone.
Johny1fin said:
One issue is if we don't keep up to date then at some point Samsung will stop support on a particular phone and the phone can be years out if date.
They may then be on a version unsupported by the apps suppliers and will be more difficult to sell if you want to buy a new phone.
Click to expand...
Click to collapse
No problem here. All my PCs, their XPx64/W7 OSs as well as my Androids Kitkat/Pie OSs are now unsupported.
No issues and all continue to fulfill their missions.
Forced learning curves waste my time and offer little in return. My last learning curves were from Kitkat to Pie and XPx64 to W7.
I stopped updating with the best versions of both MS and Android. I don't rat's arse if it stays like that for the next 10 years... or if my Windows machines mutate into Pie or Linux machines
Whatever works best for me.
It's not just the bugs that won't get fixed it's the vulnerabilities as well, then the apps stop working. I actually enjoy upgrading my kit and amon Windows 10 21h1. Anti virus packages mat stop working as well.
Johny1fin said:
It's not just the bugs that won't get fixed it's the vulnerabilities as well, then the apps stop working. I actually enjoy upgrading my kit and amon Windows 10 21h1. Anti virus packages mat stop working as well.
Click to expand...
Click to collapse
I've never had a malware or virus issue that required a factory reset in over 7 years of using Android. More than half of the time was using out of date OS's. My current Pie OS is over a year out of date.
99% of rootkits, viruses etc are uploaded by the user. There's no protecting the stupid.
I have redundant complete backups so a factory reset will cost me normally 2 hours and at worst case 6-8 hours if I need to restore the SD card.
You waste far more time then this fighting with the bugs, the learning curve and the forced factory reset that a major firmware update requires.
I get to use the OS of my choice... you get whatever they throw at you and the ride that comes with it.