Related
Moto G 16GB, bought off Amazon.co.uk. Rooted and flashed 4.4.2 before it was pushed to the device (I think it was an image off US version, found it in these forums back when I got the phone). I've been getting a prompt to install some Motorola US update for a few weeks, it pops up every now and then, has gone away when I tapped "No, thanks" option. All was fine until this morning...this is a really weird problem.
I don't know if the phone updated itself overnight, but when I dismissed the alarm this morning I couldn't get past the lockscreen. I put in my lock code and the phone had the stock wallpaper, then cycled to black background, then back to stock wallpaper and then I got a pop up saying "Unfortunately, the process com.android.systemui has stopped." and I was bumped back to the PIN lockscreen. Tried again, same thing. Now it doesn't even say anything about androidui, just cycles between black background and stock wallpaper and kicks me out.
Tried hooking it up to a PC and Mac, but neither recognized it and the phone appeared to be just charging. Power cycled it a dozen times by holding down the power button for about 6 seconds and I always end up with the same problem of not getting past the lockscreen. Every time I boot the phone now it says "Android is upgrading... Optimizing app 1 of 1". This is why I thought maybe I was pushed some incompatible US update?
Underneath it all the phone works fine, got the alarm this morning, received an SMS, answered a phone call. I can even get to the camera from the lockscreen. Is there any other options besides complete wipe and starting from the beginning again?
Probably OT, but I've always had trouble with the launcher quitting, no matter what launcher I'm using, on Moto G and the previous GNex.
Any help is appreciated, I'm bummed.
Hi,
i've today the same, exactly the same problem. It's strange, because i can't reset my phone to factory default, i went to the recovery menu, then "factory", but it only rebooted...
My "solution":
I reinstalled the original firmware:
http://forum.xda-developers.com/showthread.php?t=2542219
Then all works fine.. No matter why this error occurs.. an automatic firmware update? ..i don't know...
the exact same thing happened to me today out of nowhere and i'm about to leave on a trip, i'm so angry!
Jeez...well, looks like I'm not the only one. WTF happened? I left on a weekend trip too and I'm P.O.'d. I haven't been too religious with my backups either, that's why I was trying to find a way to back things up before wiping it all, but it looks like I'm out of luck. Guess a full wipe is in order.
hmmm i'm a complete dufus when it requires ADB, i've followed the procedures at the link but everytime i try to enter an input cmd says "mfastboot is not a recognized command"
electrictimes said:
Jeez...well, looks like I'm not the only one. WTF happened? I left on a weekend trip too and I'm P.O.'d. I haven't been too religious with my backups either, that's why I was trying to find a way to back things up before wiping it all, but it looks like I'm out of luck. Guess a full wipe is in order.
Click to expand...
Click to collapse
my phone wasn't even rooted, pure stock kitkat, i'm taking my heavy ass old notebook with me and will spend my days off trying to fix this **** it seems
a.monteiro said:
hmmm i'm a complete dufus when it requires ADB, i've followed the procedures at the link but everytime i try to enter an input cmd says "mfastboot is not a recognized command"
Click to expand...
Click to collapse
Take a look:
c) If the firmware file you downloaded is a .xml.zip file then download Motorola Fastboot mfastboot-v2.zip (attached to this post) and extract the .exe into the same folder as the stock firmware files (the same folder as the .bin and .img files). If your firmware is a .tar.gz file then skip this step.
I'm debating if I should go ahead and restore the firmware OR wait for Motorola to right their wrongs!
a.monteiro said:
the exact same thing happened to me today out of nowhere and i'm about to leave on a trip, i'm so angry!
Click to expand...
Click to collapse
Same situation....
ifishy said:
Take a look:
c) If the firmware file you downloaded is a .xml.zip file then download Motorola Fastboot mfastboot-v2.zip (attached to this post) and extract the .exe into the same folder as the stock firmware files (the same folder as the .bin and .img files). If your firmware is a .tar.gz file then skip this step.
Click to expand...
Click to collapse
I... did that, but obviously not the correct way, i'm downloading the files on my note and will try again. Maybe I should unpack the firmware files at some specific place? The instructions said nothing about this so I did nothing.
zofari said:
I'm debating if I should go ahead and restore the firmware OR wait for Motorola to right their wrongs!
Click to expand...
Click to collapse
Just reminded me that my phone is still within warranty, doing this restore may void it?
a.monteiro said:
I... did that, but obviously not the correct way, i'm downloading the files on my note and will try again. Maybe I should unpack the firmware files at some specific place? The instructions said nothing about this so I did nothing.
Just reminded me that my phone is still within warranty, doing this restore may void it?
Click to expand...
Click to collapse
My phone is back working..at the cost of wiping out all my data.
zofari said:
My phone is back working..at the cost of wiping out all my data.
Click to expand...
Click to collapse
Guess this is the only way out of this, then. What a mystery... I wonder if this is the "Welcome to Lenovo" update 1.0 lol.
i'm getting a "missing AdbWinApi.dll" although i've installed all the applications required, any help?
edit: guess i also need the android sdk, right?
edit2: got it, just copy the dlls from the minimal adb directory into the firmware directory and it's good to go, just configuring my newly restored device, thanks all
I wonder why this happened? I was using google play store at the moment, updating the flipboard app...
a.monteiro said:
I wonder why this happened? I was using google play store at the moment, updating the flipboard app...
Click to expand...
Click to collapse
I guess It's the problem of flipboard app!
My father's phone is also experiencing this issue, I can't even reset the phone to factory settings.
This occurred when I was also updating the flipboard app... seriously I'll have to RMA this...
----------------------
So I also have an issue where when you unlock the screen, it just locks back up (no android dialogue saying that com.android.systemui has crashed, but the same result).
I'm also unable to go into bootloader -> Recovery to factory reset the phone.
I stupidly tried to uninstall the flipboard app and reinstall it and it killed the phone... it's now stuck and quite annoying.
I'm 99% sure it's Flipboard.
Looks like others are having issues with Flipboard too
http://forums.androidcentral.com/moto-g/391289-something-seriously-wrong-my-moto-g.html
----------------
I solved the issue by following the instructions here:
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97329/p/30,6720,9050
how could a flipboard update screw android so badly? what a strange day
edit: they seemed to have pulled the update back or fixed it though, during my restore flipboard installed without issues
Holy S*** I'm in the same situation. It's definitely the Flipboard update that caused everything. Support just acknowledged me but never gave me any solution. I'm running ART and I think that was contributing the problem. It's terrifying knowing how a single app can completely ruin your phone!!
Anyway guys, is there anyway I can save my pics and stuff before I wipe my data?
Good detective work, I now remember updating the Flipboard app w/ bunch of others as well when things were still all good. Could this be remedied if Flipboard would manage to push a working update? I really don't wanna wipe everything, and I'm not sure I can.
Word from Flipboard (via Twitter):
"Flipboard does not support the experimental OS ART at this time."
I cannot change the date and time on my phone, in the setting nor shell commands.
Date and TIme selections are selectable, but will not change on apply.
On TWRP 2.7.10 Recovery shows a correct date and time.
But was it rebooted to operation system, it show my date and time back in December 31, 1969.
I have tried restore back to stock 4.4 rom and recovery. Still no luck on changing it.
And I cannot downgraded with HouseOfMoto to 4.1.x. Will get a boot loop.
Any help!?
Thank You
Also, When I check all the system files ./. They are dated back in 1969-1970
Any Idea? Its the phone or software?
saranay said:
I cannot change the date and time on my phone, in the setting nor shell commands.
Date and TIme selections are selectable, but will not change on apply.
On TWRP 2.7.10 Recovery shows a correct date and time.
But was it rebooted to operation system, it show my date and time back in December 31, 1969.
I have tried restore back to stock 4.4 rom and recovery. Still no luck on changing it.
And I cannot downgraded with HouseOfMoto to 4.1.x. Will get a boot loop.
Any help!?
Thank You
Click to expand...
Click to collapse
what did you use to restore back to stock?
bweN diorD said:
what did you use to restore back to stock?
Click to expand...
Click to collapse
I used both RSD and DROID_RAZR_HD_Utility_1.41 KK to restore back to 4.4
saranay said:
I used both RSD and DROID_RAZR_HD_Utility_1.41 KK to restore back to 4.4
Click to expand...
Click to collapse
sorry, im not able to help you.
i just wanted to be sure you weren't using a backup to restore.
you mentioned flashing back to JB and having issues. i posted a [guide] in the general forum. there is an edited JB file in there near the bottom that will flash with rsd if you want to try that.
i dont expect it to fix your issue though.
Yes I have tried that and get a bootloop. cleared cache, reset everything. Couldn't get pass bootloop.
Now am back on CM11 4.4
Try to set RTC, "hwclock or date" commands
It shows RTC_SET_TIME: Invalid argument
Because of the date and time is offset. Now I cannot login or access on any google services on my phone.
Problem solved*
I use Windows 7, and USB driver is not update or installed correctly. I can't get a connection to USB 2.0+ on any ports.
Switched to my family computer and reflash. Got the phone boots up normal and Date & Time is corrected.
I want to update this post for anyone who might have the same issue.
If you have updated your phone to 4.4 KK and is showing incorrected date and time for more than 24 hours.
Then try to flash back to 4.1 JB stock. To see you can boot up your phone and change your date and time back to normal.
But if you get a bootloop and restart.
Then you might having a hardware/sensor failure somewhere on your phone.
Usually is an approximate sensor, or light sensor on the front housing of the phone.
This will cause a chain reaction to your phone.
Are you sure about this? Because my phone (xt925) has the proximity sensor broken and don't have date/time issues
DorianX said:
Are you sure about this? Because my phone (xt925) has the proximity sensor broken and don't have date/time issues
Click to expand...
Click to collapse
I have a front housing with 2 broken sensor; proximity and light sensitivity. Tested on 3 phones of my family
Are you on KK or JB?
Try to flash back to JB and then KK on sbf stock.
Edit: I figured out the problem. I was reading other posts on the web and one person said they had similar issue when they replaced the screen. So there is only two ribbons that attach to main board, I took it apart again and reset the cables. Powered on and date was set correctly. Big sigh of relief as I thought i would have to send the board back. :good:
its strange, I get this problem after doing a mainboard swap. It did a bootloop when I first started it, thought it may of been a corrupt system so just did the kitkat update, was able to root and unlock the bootloader on the new board and that is when I noticed the date. flashed back to JB with house of moto universal script and I get the same bootloop. My phone worked fine with the old mainboard. I just changed it because the sim card reader would go out. Either I got a bad board or something. I'll continue to investigate but any input would be appreciated.
yujikaido79 said:
its strange, I get this problem after doing a mainboard swap. It did a bootloop when I first started it, thought it may of been a corrupt system so just did the kitkat update, was able to root and unlock the bootloader on the new board and that is when I noticed the date. flashed back to JB with house of moto universal script and I get the same bootloop. My phone worked fine with the old mainboard. I just changed it because the sim card reader would go out. Either I got a bad board or something. I'll continue to investigate but any input would be appreciated.
Click to expand...
Click to collapse
Go download this app "Test Your Android", to test the hardware on your phone.
please how do we correct thid issue of time and date moving far behind to 1970's ?
thanks
thank you so much I had tried every solution on here for other devices also and then when I saw your post I took off the screen and replaced the front camera/earpiece/sensor assembly, put the screen back on and the clock resetted right away with the correct time and date..it seems the one I was using was damaged ..so it was the sensor ..I hope this helps others with this problem
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Jst flash a newer modem in recovery
mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.
Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.
My oneplus 6 A6000 is always crashing when something new is opened. Random apps make the phone freeze and it randomly reboots from boot animation and in splash screen. I cant update my software via local it always fails. I cant update my software via OTA it is says signature failure at 95%
my phone was recently bricked with a RED warning "your phone is corrupted...." I fixed the warning with MSM downloader tool. I am out of options.
I tried to flash a custom ROM but I Am stuck in step 1 that to flash OOS it says error 28
Updated via MSM tool Tried to go to 10.3.0 it crashes from Welcome Logo
via MSM tool Tried to go to 9.0.8 it crashes too
I also notice some lines in the screen. I had a chance to take a screenshot of it and it shows in the screenshot. it means its not an LCD problem.
please help me developers
Ok, so feels like you have some unofficial oos or firmware installed...can you tell me more about your situation?
What OOS you are using?
Are your bootloader unlocked?
Do you have root?
What firmware installed with MSM tool?
When in MSM tool you wiped everything or only data?
What twrp you are using?...
Please provide some info...and if you can, upload that screenshots so we can see that lines....maybe you phones battery is dead or maybe something with hardware i guess...
It all started when I updated to 9.0.9 pie it is stable version. I flashed oxygen os 5.1.5 via msm tool to remove the red warning. The only twrp I tried is for Android Q ( I updated my system to 10.3.0 via MSM tool). Yes I tried to unlock bootloader and try to flash a ROM I got stuck in a step where I need to flash an OOS the version is right. I dont know what causes the error. Pls ignore the 2nd error in screenshot I accidentally pressed that. Thank you I will get back to you for the screen DIAGONAL lines it is small I also notice if something new appear to the screen the phone freezes and restart.
Ok, what twrp version you are using?...and pls...try to format data withing twrp and then enable mtp and flash latest oxygen again...but your zip is not the latest one...it should be Oneplus6oxygen os 042...but format everything when it says type yes...try this and talk back...
And feels like it is hardware problem...
Here is the screenshot of lines appearing randomly.
I tried that nothing happend. Still that warning yes it is 042 and i am using EvolutionX rom it reboots but Not too much
Twrp is 3.3.1-17 Q
Did you try to format your phone?
PecanTastic said:
My oneplus 6 A6000 is always crashing when something new is opened. Random apps make the phone freeze and it randomly reboots from boot animation and in splash screen. I cant update my software via local it always fails. I cant update my software via OTA it is says signature failure at 95%
my phone was recently bricked with a RED warning "your phone is corrupted...." I fixed the warning with MSM downloader tool. I am out of options.
I tried to flash a custom ROM but I Am stuck in step 1 that to flash OOS it says error 28
Updated via MSM tool Tried to go to 10.3.0 it crashes from Welcome Logo
via MSM tool Tried to go to 9.0.8 it crashes too
I also notice some lines in the screen. I had a chance to take a screenshot of it and it shows in the screenshot. it means its not an LCD problem.
please help me developers
Click to expand...
Click to collapse
Sometimes issues like that occur when I change some things in mine and don´t wipe the data [Mine is an A6003]
Yes I did try to format data. I tried to install TWRP in. 8.1 oreo OOS 5.1.11 Blu spark twrp 3.2.3-x. "fastboot boot twrp.img" and it completes but stuck in oneplus logo fast boot mode.
I had only access to twrp in Q 10.3.0 twrp version 3.3.1-17-Q ( this is the only Custom recovery worked )
I tried pie 9.0.8 flash twrp "fastboot boot twrp.img" it is also stuck in oneplus logo fastboot mode
Maybe this will help? The package box of my phone
Problem started after Pie OTA update. Black screen and random reboots
it was sold with OxygenOS installed
Bump
Read and write speed
My read and write speed is 749mbps(read)
0mbps(write) any way to fix this? Maybe this is the problem
If those problems are purely software-related, and I think there's a good chance they are, I'd say one of the more critical partitions on your phone got corrupted at some point, somehow. Using MSMDownloadTool to fix this is a bit of an overkill imo, and the method below has always worked for me when I messed something up while switching between OOS and custom ROMs so I reckon it's pretty good. Also, full-proof. Essentially just do as follows:
0. Make a backup. Always!
1. Download the newest OOS version from this thread (direct link to 10.3.1)
2. Unpack the zip to whichever location on your PC suits you best.
3. One of the files inside will be an archive (also .zip if I recall correctly) with all the partition images. Unpack all its contents to the main directory where the rest of the files are.
4. There will also be a folder with different .bat files corresponding to what partitions you'd like to flash (as per the flasher advanced guide section in the thread from point 1) - grab the one named flash-all-partitions.bat and copy it to the main folder as well.
5. Boot the phone into fastboot mode and connect it to PC, and finally
6. Launch the script from point 4, agree to the data wipe, and wait. Flashing the whole thing will take a while, but hopefully it'll solve your problems
Hello, I followed all the steps still no luck. Random apps cause the phone to crash systemUi. Which leads to boot from bootanimation Anyone please help me too sad oneplus has no emergency download tool
PecanTastic said:
Hello, I followed all the steps still no luck. Random apps cause the phone to crash systemUi. Which leads to boot from bootanimation Anyone please help me too sad oneplus has no emergency download tool
Click to expand...
Click to collapse
MSMDownloadTool is the emergency download tool. Anyway, what you did is you literally just reflashed all of your phone's partitions, on both slots, so either the issue is hardware, or...I don't know. What happens when you boot your phone in safe mode (hold the reboot, err, icon that appears after holding the power button for a few seconds, until a popup with info about safe mode appears)? Do apps still crash?
Oh, one more thing (blind guess really, but yeah) - are you, by any chance, a beta tester for the Android System WebView app or Google Play Services? If you are, switch back to stable channel via Play Store and update the respective apps. Tell me, if that changed anything. (Also, if you could check the WebView implementation version in the settings, that would be great (just use search)).
Edit: out of curiosity, what happens when you try to update the phone via the local update function (to 10.3.1, just download the full OTA zip this time instead of the fastboot-compatible one)? Does it work without issues or not really?
One thing I noticed is writing speed is instant e.g. sending
OKAY [19.294]
Write[0.000]
Sometimes it is [-0.000]
i need a tool to reset internal partition or anything main slot for boot is "b"
It does not update via local.
I will try that playstore thing but I doubt it
McAwesomePL said:
MSMDownloadTool is the emergency download tool. Anyway, what you did is you literally just reflashed all of your phone's partitions, on both slots, so either the issue is hardware, or...I don't know. What happens when you boot your phone in safe mode (hold the reboot, err, icon that appears after holding the power button for a few seconds, until a popup with info about safe mode appears)? Do apps still crash?
Oh, one more thing (blind guess really, but yeah) - are you, by any chance, a beta tester for the Android System WebView app or Google Play Services? If you are, switch back to stable channel via Play Store and update the respective apps. Tell me, if that changed anything. (Also, if you could check the WebView implementation version in the settings, that would be great (just use search)).
Edit: out of curiosity, what happens when you try to update the phone via the local update function (to 10.3.1, just download the full OTA zip this time instead of the fastboot-compatible one)? Does it work without issues or not really?
Click to expand...
Click to collapse
Apps don't crash when Im in safe mode but i can only access system apps. Thank you for helping dude.
Maybe this will explain something?
PecanTastic said:
One thing I noticed is writing speed is instant e.g. sending
OKAY [19.294]
Write[0.000]
Sometimes it is [-0.000]
i need a tool to reset internal partition or anything main slot for boot is "b"
It does not update via local.
I will try that playstore thing but I doubt it
Click to expand...
Click to collapse
Some partitions are fairly small, so they should be transferred to the device pretty much instantly, although I'm not sure if the time should show null ([-0.000]).
If OTA still doesn't work however, then the problem seems to be somewhere else entirely, so the Playstore thing probably won't help, yes.
PecanTastic said:
Apps don't crash when Im in safe mode but i can only access system apps. Thank you for helping dude.
Click to expand...
Click to collapse
Heeeey, we're getting somewhere!
-------------------------------------------
Edit: wait, are the user apps the only ones crashing (when not in safe mode)? Or are system apps crashing too?
-------------------------------------------
The safe mode is designed in such a way that no services other than system ones can run while using it - it's mostly for troubleshooting, same as e.g. in Windows. Not sure where that leads us, but there is a chance one of your apps/widgets/whatever might be causing this issue in that case, although I'm not sure how an app would impact the OTA functionality. Regardless, what you can check is whether you're able to perform a local update while in safe mode. You can also download the OTA zip again just to be sure it's not corrupted and that if the installation fails, it's not the update package's fault (and remember to use the full 1.something GB zip, not just the delta package!).
One other thing to try if the above fails is to reflash the critical partitions using the fastboot-compatible update zip and an appropriate script from within it. No idea if that's going to help, especially considering the fact those partitions should have been reflashed along with the rest using the script I mentioned a few posts earlier, but I reckon it's worth a try if everything else fails - troubleshooting is a trial-and-error process, all in all.
...also, np - hope you manage to fix your phone's issues eventually!
---------- Post added at 02:26 PM ---------- Previous post was at 01:59 PM ----------
PecanTastic said:
Maybe this will explain something?
Click to expand...
Click to collapse
Not really, no, unfortunately - if I understand the information from the photo correctly, the only reasons for your device powering off were holding the power button [1] and using the keypad [3] (tapping the power off icon from the power menu?), which is, well, a normal way to turn a device off.
Pls just use MSMDownload tool insted....i can give you a link if you want but you can just google it
James Blode said:
Pls just use MSMDownload tool insted....i can give you a link if you want but you can just google it
Click to expand...
Click to collapse
He used it actually, as mentioned in the OP, but to no avail.
So 3 days ago I got bored of Android 4.4.2 on my 6 years old tablet. It worked fine for browsing the internet and watching youtube but I wanted more. I thought that was installing a new android an easy business but I was wrong. I downloaded TWRP and lineage os android 7.1. for my N8000.Then I flashed my recovery and later I download a sketchy rooting app from an internet called "iRoot". Then "iRoot" downloaded and installed an app with some Chinese characters. I wanted to delete that but there was no icon in "manage apps" tab
then I disabled it in other tabs and rebooted my device. when my device rebooted my touchscreen wouldn't work. I pulled my S-pen out and it worked perfectly fine (the device was never dropped). So I tried factory resetting my device and the problem was still there. I installed SuperSu app I thought that it would help me but when I open it it said ''binary occupied''. I was hopeless. Then I installed lineageOS and the problem was still there. I tried going back to my old android 4.4.2 but my sd card was corrupted. I installed Odin and flashed factory OS for my device. now I have the same problem. btw this was my first time doing this stuff so I made a lot of mistakes. I saw people fixing this problem simply by calling *#2663# but when I do that my screen flashes back and then it forwards me to my home screen. The problem was still there. Do you guys know the solution?
'
Its the rooting app that is your problem .
TWRP install via Odin wipe data system cache etc reboot to download mode .
JJEgan said:
Its the rooting app that is your problem .
TWRP install via Odin wipe data system cache etc reboot to download mode .
Click to expand...
Click to collapse
I wiped everything. I just installed Factory android 4.4.2 with Odin. Then I installed TWRP 2.8.4.0 via Odin and wiped everything. but my touchscreen still doesn't work even in TWRP. I was installing Lineage 14.0 from this thread https://forum.xda-developers.com/galaxy-note-10-1/development/rom-lineageos-14-1-t3848514 and I ran out of time. I will update you guys tomorrow. :fingers-crossed:
So *#2663# doesn't let you reflash the tsp firmware?
If not, your tsp ic need to get replaced.
html6405 said:
So *#2663# doesn't let you reflash the tsp firmware?
If not, your tsp ic need to get replaced.
Click to expand...
Click to collapse
What do you mean by that? Do I need to replace my digitizer, motherboard, or something else? I'm quite new in this type of stuff so I don't understand most of the things
Also, I tried installing multiple versions of official os and other versions of Lineage and Slimroms and my touch still doesn't work. I also tried reflashing firmware on all those versions but it still work.
This menu which appears, when you dial *#2663#, it let you update the touch screen panel firmware,
it flashes it directly to the chip.
If this fails or simply doenst work, you have to replace this chip (TSP IC) or your mainboard.
html6405 said:
This menu which appears, when you dial *#2663#, it let you update the touch screen panel firmware,
it flashes it directly to the chip.
If this fails or simply doenst work, you have to replace this chip (TSP IC) or your mainboard.
Click to expand...
Click to collapse
Thanks for your quick response. Basically, because this tablet is over 6 years old, and I am unable to find the correct motherboard in my country. I found tablets (used) like mine for something near 40 euros. I wanted to buy a whole motherboard and replace it, but it was like 30-40 dollars and shipping is an additional 50 - 60 euros. So I think that I should wait for a cheap broken one and then try to make Frankenstein from those two. Anyway thanks for your help!