I had been running rooted rom (Darth Stalked) 5.0.1, COD6... for months, no problems. I had TWRP 2.8.4.0 installed... So today I downloaded TWRP 2870 from the official web site, and ACCIDENTALLY installed the one for NOTE 4 EDGE (and I have a regular NOTE 4 SM-910T)
So afterwards I realized all the margins for the touchscreen were off, I would have to touch a little HIGHER UP on the screen to hit the button
1 2 3
4 5 6
7 8 9
as an example, think of having to press between the 3 and 6 to actually press 9.
Well, the stylus (s-pen) still seemed to work, so I was able to correctly navigate back to twrp site, download 2870 for note 4 t-mobile (the one I needed). but the touchscreen is still messed up (still not touching where I touch with my finger, but the s-pen works and does hit where it touhces)
I restored a nandroid backup, no change
I factory reset, no change
I reflashed twrp 2840, no change
I reflashed twrp 2870, no change
I wiped cache and dalvik, no change
So, trying to press my finger on the touchscreen registers too high or innaccurate, but the s-pen seems to work. THIS ALL STARTED AFTER I MISTAKENLY INSTALLED THE NOTE 4 EDGE TWRP 2870 and I can't figure out how to UNDO whatever it did.
I am still on COD6, have TWRP 2870 installed, I reverted back to an older nandroid I made with TWRP from about 4-5 months ago, but the touchscreen is still not accurately activating where I press with my finger... PLEASE HELP ME.
http://forum.xda-developers.com/note-4-tmobile/help/touch-screen-issues-root-t2986883
found a solution
dial *#2663# and update the touch FW by pressing "TSP FW update (General)".
All credit goes to charlieb620 on this post:
http://forum.xda-developers.com/show....php?t=2144166
Here i thought this post would be the solution to the nightmare i've been undergoing trying to get this Note 4 of mine fixed. But when i go to update the touchscreen FW version i get an error and nothing happens.
"ic's f/w is higher than bin's f/w" is what it says. Someone please help me.
Related
Picked this tablet up from a coworker who said he hadn't used it for awhile. Powered it on and played with it for a bit, then got a notice that there was a firmware update.
Went ahead and installed the firmware (which took forever...like hours). When it rebooted from installing, it is now stuck at the following screen. No sequence of keypresses or anything will get it past it. I can power it on/off, but that's it.
Note that this was an Asus OTA firmware update, nothing crazy or wild that I tried. Any help would be appreciated!
ms960 said:
Picked this tablet up from a coworker who said he hadn't used it for awhile. Powered it on and played with it for a bit, then got a notice that there was a firmware update.
Went ahead and installed the firmware (which took forever...like hours). When it rebooted from installing, it is now stuck at the following screen. No sequence of keypresses or anything will get it past it. I can power it on/off, but that's it.
Note that this was an Asus OTA firmware update, nothing crazy or wild that I tried. Any help would be appreciated!
Click to expand...
Click to collapse
Power off - Volume Up + Power = Droidboot = factory reset using fastboot erase data and fastboot erase userdata
Anybody found it the answer?? I have 7 hours searching the soluion
This also happened to me. Power off the tablet, hold volume up while powering on again and you should be in droidboot. Insert micro sd into computer and download needed files on it. Then use Tethered CWM recovery and flash WW 182. Than go to this link: http://translate.googleusercontent....JrhhhS1Q6KFTsV91ahquu2I9SfKsViw#entry32744050 and download 201 CWM backup. Restore the backup and you should be on kitkat again. If you are like me and want lollipop, just send it for RMA, becouse it looks like there is no other solution
hI
HERE
http://forum.xda-developers.com/memo-pad-7/general/5-0-brick-solution-asus-memo-pad-7-t3134814
I am currently stuck for 45+ minutes at the google reboot splashscreen (4 colorful spinning dots that eventually should turn into the word android once reboot is complete).
I followed an update procedure that I have used many times (last done November 16), although some of the files involved are somewhat old.
Starting from November 16 update for Marshmallow:
1 - Fastboot-Flashed that March 2017 factory image for Marshmallow (yes, there is still a Marshmallow... I dont' want Nougat yet). Flashed all partitions except data and recovery.
2 - Reboot directly into TWRP (I believe it is TWRP 3.0.2... I haven'te changed it recently)
3 - In TWRP: Flash superuser BETA-SuperSU-v2.65-20151226141550 i
4 - In TWRP: Clear space from app/system by deleting foreign language directories (to make room for xposed)
5 - IN TWRP: Flash xposed xposed-v79-sdk23-arm
6 - In TWRP - initiate reboot to system.
7 - As system rebooted, I entered my PIN.
That's where I am now. Note I never saw a screen for "optimizing apps" that was expected. I
Note I never rebooted to android system, so I'm not sure which step caused the problem (it was a method I developed to update quicker although in retrospect rebooting each step to check would be smarter).
I have some ideas of what to do eventually: (retry my flash one step at a time)
BUT, I don't know how to do anything with a phone that is stuck on the splashscreen:
* It does not respond to key combination on/volume-down (which normally goes to fastboot)
* When plugged into pc, it does not respond to fastboot devices
* There is no battery pull option on this phone.
What to do next to get control of my phone... let the battery run out on the splash screen?
Hmmm. Weird. Just held power-on and vol-down and it took me briefly to a different screen (android?) and then promprted for PIN, then back to splashscreen.
I kept pressing that combo and eventually did get into fastboot.
Now I'll flash again.
electricpete1 said:
I kept pressing that combo and eventually did get into fastboot.
Now I'll flash again.
Click to expand...
Click to collapse
Hello. Not sure what caused your problem. Also, i don't use Xposed...
Just a heads up... Your SuperSU is really really old. Just use this one:
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
Good luck...
The version of SuperSU he used likely was the cause of the bootloop.
5.1 said:
Hello. Not sure what caused your problem. Also, i don't use Xposed...
Just a heads up... Your SuperSU is really really old. Just use this one:
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
Good luck...
Click to expand...
Click to collapse
I reflashed the system and then flashed newer files:
SR3-SuperSU-v2.79-SR3-20170114223742.zip
xposed-v87-sdk23-arm
(with a reboot between flashing SU and flashing xposed).
Everything booted up fine.
Problem solved.
Thanks for the help!
Aren't you supposed to fastboot boot, not flash the su with marshmallow?
So I have a very odd problem, and I'm fairly experienced with repairing, rooting, and reverting phones to stock which have custom roms, in this case I have a completely stock note 5 which was experiencing a boot loop error at the note 5 model number screen. Going through the motions I normally would, hard reset, nope, safe mode, nope, wipe cache, nope, master reset, nope, so I flash the firmware with a stock rom, which worked, but resulted in the same problem, rebooting at the model number screen just before the samsung logo every few seconds, tried 3 other firmware versions and downloads, also no. Not sure whats up with this thing, but anyone have any ideas? I personally know the user, family, phone wasnt physically damaged or exposed to water. I'm also getting no command just before entering recovery and failed to mount/ preload (no such file or directory) during the master reset. Its been forever sense I've meddled with a note 5 and cannot remember if these are normal, or related to the issue, I dont ever remember seeing these with my own note 5.
I ran into this exact same problem weeks ago on my S7. I tried flashing 7.0 on my 930V and for whatever reason the phone went into the exact same bootloop showing the Samsung logo every few seconds, vibrating, etc. I got back into download mode but wasn't able to fix it. Then went into Recovery and it only said in blue letters in the top left "Recovery rebooting" and kept flashing that message. Lucky for me I was under warranty and sent it to Samsung. They replaced it free of charge. I ended up trading for a Note 5. I kept running into issues with my S7 and network issues so I traded it.
Anyway, I'm like you in the fact I'm pretty comfortable rooting, repairing devices etc. But I still don't know what I did to mess up that S7 in Odin. Just wanted to share that I had a similar situation. Hope you were able to get a new phone or fix your issue.
sinkableelk said:
So I have a very odd problem, and I'm fairly experienced with repairing, rooting, and reverting phones to stock which have custom roms, in this case I have a completely stock note 5 which was experiencing a boot loop error at the note 5 model number screen. Going through the motions I normally would, hard reset, nope, safe mode, nope, wipe cache, nope, master reset, nope, so I flash the firmware with a stock rom, which worked, but resulted in the same problem, rebooting at the model number screen just before the samsung logo every few seconds, tried 3 other firmware versions and downloads, also no. Not sure whats up with this thing, but anyone have any ideas? I personally know the user, family, phone wasnt physically damaged or exposed to water. I'm also getting no command just before entering recovery and failed to mount/ preload (no such file or directory) during the master reset. Its been forever sense I've meddled with a note 5 and cannot remember if these are normal, or related to the issue, I dont ever remember seeing these with my own note 5.
Click to expand...
Click to collapse
My suggestion is this..
Download the latest version of TWRP
Boot to Download Mode
Odin flash TWRP
Boot to TWRP Recovery
Full wipe including internal storage x 2
Format DATA x 2
Odin flash the latest firmware for your device
(All 4 - BLUE, AP, CP, CSC)
OR
Use Smart Switch Emergency Recovery to restore the firmware.
Hope this helps. Good luck and happy flashing! Let's us know what happens.
Sent from my Samsung SM-G955U using XDA Labs
So recently i bought note 5 N920T T-mobile variant and after few days i encounter a weird problem that i can't figure out what exactly is going on.
Once a sudden my phone freeze and touch screen stop responding then phone goes black screen and a strong white led light turn on while screen is black.
Then after pressing 3button together volume down+home+power the phone reboot normally
Then after few seconds again and again same thing happens.
I was on stock rooted 6.0.1 marshmallow rom with arter kernel permissive since i bought this device.
Things i tried
Factory reset from twrp (didn't change a thing)
I flashed stock rom marshmallow and nougat both via odin (got worse now more freezing and rebooting can't even complete setup )
Again tried flashing 4 files recovery firmware BL+AP+CP+CSC via odin this time with PIT FILE re-partition checked in odin. everything Pass smoothly without errors in odin but again freezing black screen on setup. (same issue)
Tried factory reset+wipe cache after flashing (still same)
At last i tried flashing custom rom "kongloi s8 port final repacked" from twrp after clean wipe it worked finally now no reboots or blackscreen freezing nothing everything works perfect for 2 days.
Then i thought now my phone is fixed so why not try stock again.then again same problem came back.
1 thing i realize that when i run custom kernel specifically a permissive kernel my phone runs without issues.
currently stuck with khongloi rom s8 port this is the only rom working on.my device and cant go back to marshmallow.
I am looking on Google and xda constantly from many days but can't find correct answer.
So please please someone point me out what is this issue
Sorry for the long post TIA
Hi, I've recently bought a Samsung Note 9, secondhand, yet still new condition. Courier dropped the delivery and I was impressed with what I received, unboxing through to switching it on. Awesome display, features, speed, etc.. unfortunately, it didn't last long. Went through the initial setup, google acc, personal preferences, up to the point where security features needed to be activated. As I wanted to enroll fingerprints, it asked for passkey before biometrics could be recorded. I entered a 5 digit code, again to confirm, and then it was set. Then the trouble started. Phone locked by pressing the power button then refused to unlock with the passcode that I've just saved. After a while of trying to enter the key I've used, as well as some alternative combinations for in case I've made a mistake (twice?), I've resorted to boot into recovery mode by switching off the device and pressing bixby+vol up+pwr. Booted into recovery, chose factory reset and let it run.
It finished in less than a second, before I chose to reboot device. Only to see the screen stay dark with red words top left corner of screen: Only official firmware to be installed something something. And that's what I kept on getting, did abovementioned step again, same issue, tried formatting cache, same issue, tried lacking storage boot, same issue, tried flashing custom rom via Odin, same issue, tried to find official firmware and installed that same issue. I've noticed that none of the packages I try to install works due to an error stating that Signature Verification Failed. Every time, whether I try sideloading via adb, updating via sdcard or flashing with Odin, I get the same result. Last try was flashing the bootloader with an recovery zip I found somewhere and now it just bootloops the Samsung Galaxy Note 9 startup screen, vibrates, restarts and same screen again. Even if I let it loop, it keeps on forever. I can still access bootloader, recovery and Download mode with pressing the button combinations, but nothing I try of the options available resolves the problem.
I'm really at a point where I don't know what to do or try, please advise. Here's some additional info that might help:
Samsung Galaxy Note 9 SM-N960F Crownlte.
Support SINGLE-SKU
Block-Based OTA
Supported API: 3
samsung/crownltexx/crownlte9/PPR1.180610.011/N960FXXU3CSI3
After a few of my flashing attempts, abovementioned line now reads:
Block-Based OTA
Supported API: 3
samsung/crownltexx/crownlte9/PPR1.180610.011/N960FXXU3CSF9
Its the Exynos version of the Note 9. Any direction or help will be much appreciated.
Thanx
Sdejager2 said:
Hi, I've recently bought a Samsung Note 9, secondhand, yet still new condition. Courier dropped the delivery and I was impressed with what I received, unboxing through to switching it on. Awesome display, features, speed, etc.. unfortunately, it didn't last long. Went through the initial setup, google acc, personal preferences, up to the point where security features needed to be activated. As I wanted to enroll fingerprints, it asked for passkey before biometrics could be recorded. I entered a 5 digit code, again to confirm, and then it was set. Then the trouble started. Phone locked by pressing the power button then refused to unlock with the passcode that I've just saved. After a while of trying to enter the key I've used, as well as some alternative combinations for in case I've made a mistake (twice?), I've resorted to boot into recovery mode by switching off the device and pressing bixby+vol up+pwr. Booted into recovery, chose factory reset and let it run.
It finished in less than a second, before I chose to reboot device. Only to see the screen stay dark with red words top left corner of screen: Only official firmware to be installed something something. And that's what I kept on getting, did abovementioned step again, same issue, tried formatting cache, same issue, tried lacking storage boot, same issue, tried flashing custom rom via Odin, same issue, tried to find official firmware and installed that same issue. I've noticed that none of the packages I try to install works due to an error stating that Signature Verification Failed. Every time, whether I try sideloading via adb, updating via sdcard or flashing with Odin, I get the same result. Last try was flashing the bootloader with an recovery zip I found somewhere and now it just bootloops the Samsung Galaxy Note 9 startup screen, vibrates, restarts and same screen again. Even if I let it loop, it keeps on forever. I can still access bootloader, recovery and Download mode with pressing the button combinations, but nothing I try of the options available resolves the problem.
I'm really at a point where I don't know what to do or try, please advise. Here's some additional info that might help:
Samsung Galaxy Note 9 SM-N960F Crownlte.
Support SINGLE-SKU
Block-Based OTA
Supported API: 3
samsung/crownltexx/crownlte9/PPR1.180610.011/N960FXXU3CSI3
After a few of my flashing attempts, abovementioned line now reads:
Block-Based OTA
Supported API: 3
samsung/crownltexx/crownlte9/PPR1.180610.011/N960FXXU3CSF9
Its the Exynos version of the Note 9. Any direction or help will be much appreciated.
Thanx
Click to expand...
Click to collapse
1. Install official stock rom from sammobile from this link (doesn't matter which you download):
https://www.sammobile.com/samsung/galaxy-note9/firmware/#SM-N960F
2. Load up Odin, put corresponding files to their slots, AP to AP, BL to BL, etc..
3. Boot into download mode (phone powered off, press and hol volume down + bixby button and insert cable to computer)
4. Flash it, wait for it to boot up.
Ok, I'll try that today and hopefully my next reply will be me posting from the Note. Let's hold thumbs.
Thanx
How did you solve the problem.. Same here.. Stuck at bootloop
Am unable enter in to download mode.. Tried hundreds of times
Minzlife said:
Am unable enter in to download mode.. Tried hundreds of times
Click to expand...
Click to collapse
try this
Plug your phone to pc
Hold power button + volume down for a few seconds
Then right before the phone logo shows, bixby + volume down
Now download mode shows. Flash stock rom