I disassembled my phone lately for maintenance reasons, The battery was out for about 30 minutes, (My phone already had a trouble keeping the clock even though the battery was taken out for a short period), after assembling the phone, it booted up properly till the lock screen appeared and it all became black. software and hardware buttons were working properly, but the LCD itself was totally black.
I booted-up the phone in recovery mode and wiped everything from system, data, to cache, and then installed the newest version of Lineage. After booting the system gave me "process system isn't responding" and close and wait options with infinite bootloops.
I tried installing the full stock Rom and it gave me "setting has stopped working" and "google play services has stopped working".
My guess then was the time on the device, so I went back into recovery opened a shell session and fixed the time using "date" and "hwclock", but it never worked.
After searching online I found that this might be a battery issue, so I bought a new one, and guess...It didn't work either.
I really need help with this device! :crying:
_____________________________________
Solved it by installing the NJ2:
Wiped everything, then installed the stock rom using odin 3.10, after that the system kept telling me the same messages, so I went back and installed twrp 3.10 .. I guess .. then wiped everything except for the system and internal memory, then I corrected my clock using this method:
https://forum.xda-developers.com/galaxy-s3-sprint/help/how-to-edit-time-hardware-time-using-t3621875
and frankly it worked! and booted up normally.
Sadly I wasn't able to install any linage version! ... I hope that I find the solution so soon!
Related
I have been using ai.keyboard for a long while. There's been an update and 2 more because the first "update" messed the app up, and 2 more Fixes have still not gotten things working right with the app. The phone now boots up and displays a box "Unfortunately, the process com.android.phone has stopped." and the pone won't boot any further.
I have reversed the system using CWM to an earlier version where it worked fine, and for a while things were ok. after a reboot, the updates took over and self updated many apps, and the phone requested a reboot.
Poof! same "unfortunately" message came up.
I reversed the system again to 4 previous KNOWN GOOD, Working well backups, and I still cannot boot the phone.
I can boot into recovery and do all that is allowed, but cannot get it to boot now without that message.
I wanted to fix permissions, but I notice it's no longer in CWM or in "Phills Touch" recovery.
I'm stuck at this point, and would appreciate any help.
I'm on Stock T-Mobile 4.2.2 Rooted and it's a Samsung Galaxy S4 - white
Thank you!
Aloha-
Update-
Flashed a CWM 6.0.3.2 which included "Fix Permissions" but it did not make any difference with the problem at hand.
Operation restored - Phew!
Since I had no alternatives left, I decided to return to stock and see what the results would be.
After restoring to an out-of-the-box bachup, I rebooted, and was getting the same message. I did a Factory restore so that all the Root-required apps would be removed, and after the phone rebooted, the message came out only one time and I reset the phone to work with my google profile, and set all the requirements to make calls via T-mo.
I used the phone for a whie, and having no problems, I decided to try rooting it and see if it would work.... It worked fine!
after a few minutes, I flashed CWM Restore and booted to recovery and recovered my nandroid backup I had made just before all the problems started happening. I got an update message for Ai.Keyboard and did it. BAD IDEA!!!!!!! It farkled up, and then searching the internet I saw already that many users were too, having the same problem I was having! I uninstalled the app, and rebooted and reinstalled the app to see if it would work. It was like I first installed it a loooong time ago, and seemingly, most of the problems except for backing up it's settings worked. So, I'm now re-conficuring the settings manually and the phone is acting normal.
Keeping my fingers crossed!
This is the SECOND time I have gone to such drastic measures. The first time, the problem was that I just could not make or get calls,
and the T-Mobile "Tech" in the store said it was not fixable, and suggested I call support and send it back to repair.
well, maybe the third time I'll have to.......
I am sure it has to do with app.
Sent from my HTC Flyer P510e using xda app-developers app
I went through from 4.1.1 to 4.1.2, no problems, phone ran fine after update. Then went to 4.3, same thing. The phone was running fine so I booted back into recovery and removed Knox as well as manually rerooted by flashing SuperSU. Rebooted after that and still no problems, phone was running great. I then make a backup so I have a restore point of stock 4.3, rooted, and without Knox. I then go on and try to flash Dandroid and get a status 7 error and the phone was acting up after I rebooted.
At this point I go back to my backup and simply restore it and reboot again. The phone boots up, so that's a good thing. The problem is the GApps will not run and it continuously has a pop-up notification. The phone is rendered unusable like this. I got lucky once and was able to try and launch ROM Manager to see if fixing permissions would work, but it also closed. I tried flashing a 4.3 GApps package with no success and even tried reflashing the 4.3 update but got a status 6 error.
I'm at a loss here, does anyone have any ideas on this?
Not sure if this will help much, but even when plugged in via USB my computer will not recognize the device. The S3 states that it is connected and it does show up in Device Manager, it just won't show up as any kind of readable memory.
Trying to ADB sideload a rooted stock 4.3 ROM now. Any advice at all would be a help.
EDIT: I took a video (https://www.youtube.com/watch?v=tJ-eaQ_9mVI) of the problem so everyone can see what I'm talking about and I also found a fix.
I'm not sure what was causing it, but after a solid day of researching it online the closest thing I got was resetting app preferences and also trying to clear any data of Google apps. This seemed to sometimes slow the popups down for me or create a longer gap before they just came right back in full force. So, going off that small success I had managed to navigate my way over to Settings -> Accounts -> Backup and reset -> Factory data reset and ran that. The first boot after that took a very long time, I'd say a solid twenty minutes but it did work. No more error and everything has been going smooth for me since. A restore of apps with Titanium Backup also did not bring the problem back up again, so the device seems to be good as new again.
I apologize if any of these is out of line, I just thought I would follow up with a solution in case anyone else has this problem and can't seem to fix it. Maybe this will help them.
Hello guys
I decided to re-flash CM 11 because in these days my phone started to freeze continously and reboot.
I followed the usual procedure (wipe system, data, cache, dalvik) but the problems seemed to multiply, e.g. the phone couldn't get any signal with the SIM inside.
Then I tried with another rom (Paranoid 4.6 beta 6) with no results and I reflashed CM 11.
Unfortunately after my last installation the phone stuck on the Google screen.
As last resource I restored my phone with an old backup which i made previously but the phone is still stuck in the Google text screen.
Because the things seem to get worse, i decided to write this thread.
Do you have any tip? Do you think it could be an hardware problem?
Thanks in advance
Extra information
I forgot to say that fastboot mode is available, in fact I can easily access to TWRP. However even though I reflash the rom, the phone is still stuck in the Google boot screen.
Hi All,
Having some issues with my Galaxy Note 10.1 which I've had for quite a while now. It's rooted but with Android 5.0 stock rom and a custom kernel.
Just now (like 20mins ago) I tried to enable Adblock plus app, the app said it can't automatically change the settings - even though SuperSU was installed and had no issues with it previously. So like all things thought I'd give it a reboot that ought to clear it out. That didn't work, so tried clearing cache (Dalvik/ART/Cache), Still no joy.
I'm a s/w engineer, but not and android/bootloader expert, so I've tried to grab the dmesg and boot logs which I've attached, I've got some stuff on the internal SD (app data) which I'd like to keep, hence I'm not going for the full wipe.
Please take a look at the logs and see if you can determine how to fix this issue, my initial thoughts were there are some issues with the flash storage (bad sectors/partition table?), if I could grab the image and dd the image again I'd be OK - but I don't know much about about android boot loader/kernel etc so can't say.
Ok it has been fixed by wiping data - but I've lost my data and installed apps!
Is there anyway to find out which file/app is causing the boot loop so I can restore data, delete the offending file?
Well, I shall give a bump to this topic, with a little more info. Though probably not really useful.
First I had stock 5.1.1 deodex pre root etc ROM that, after I tried to insert a nano sim card (mine is a 601 3G model) that got stuck, it entered on a bootloop, I had to open it, take the sim card out, and it was still on a boot loop. Tried to install another image, still bootloop, tried to reinstall the original one I had, still bootloop, wiped data, worked fine.
Then almost 2 weeks later, everything worked fine, went to watch a video, the sound was mute, tried to turn it on but everything looked fine, decided to restart because it would probably fix the problem. Got a bootloop. Wiped the data, everything was fine again.
Now, a little more than 2 weeks later, seems like the wifi is not working, thought all my other devices are, guess it's the same problem, decided to restart it, and bootloop again. I'm currently trying to update my TWRP, and gonna try a different ROM, and wait to see if something like that happens, until then, I wonder what could be happening... I remembered an Asus Device that I had that had different firmware versions for 4.4 and 4.1, so if I tried to flash a 4.4 on a 4.1 firmware it wouldn't work, and for downgrade, the same problem happened, and wondered if Samsung has some difference between versions 4 and 5.
ssj4maiko Let me know if you find a more stable rom - I went back to pretty much stock, but with root as I wanted to use all the Samsung apps, but this constant random bootloops are annoying!
Yesterday I did a dirty flash of Oxygen OS 9.0.10 on my OnePlus 5T which was initially running Oxygen OS 5.1.7 with Oreo 8.1.0. After that I flashed latest Magisk zip. After booting into system, then after the final setup of the update, I flashed franco kernel from TWRP.
Everything went smooth. All apps were functioning fine. Today in the evening, while watching YouTube, the touch stopped responding. I restarted my phone, cleared cache, dalvic, still the touch wasn't responding.
I booted in TWRP, the touchscreen wasn't responsive, therefore I used my mouse to decrypt then copied full zip of OOS 9.1.0 zip via adb from my laptop. After clearing cache, dalvic, I flashed the zip file.
After booting into system, my phone is showing the message, "phone is starting" with animated strip below it. This has been since past 45-50 minutes.
The touch is not functioning even now.
What should I do to resolve this trouble?
Has you debloat something from /system/app or priv-app? On my tablet it prevents to boot completely and stucks in this Android update loop.
Also not everytime a good idea to dirty flash to another Android major version (Oreo > Pie)!
Try a fresh install.
OxygenOS 9.0.10
No-Verity v4 (if a decrypted phone)
Boot.
Then back to TWRP
Magisk & Custom Kernel
Boot.
Restore maybe from Titanium user apps only (except Whatsapp/Threema/Telegram.. GCM/FCM notifications problems).
Flash Magisk modules.
Sent with much love and Android.
I have been having persistent problems with the touchscreen on my 5T becoming unresponsive at random times for no apparent reason for a while now (see this This thread for more info there).
I have found that when the touch screen stops responding, the ONLY thing that will get it working again is flashing back to stock firmware - I have been using 9.0.9 (didn't even realise .10 was out). Sometimes it doesn't work the first go, and I have to reflash again over the top (maybe even a couple of times) but I've never failed to get it working after a few goes.
Problem (on my phone at least) is that phone then hangs on the "just a sec" screen at first boot, but once the screen works again I do a clean flash of LineageOS so the setupwizard hanging is not a problem for me per se, except that the touch screen inevitably flakes out again - sometimes it takes a few days, sometimes it happens within minutes, but nothing I have tried has made it go away completely. I'd say it was a hardware problem except that reflashing the stock OOS ROM can bring it back to life... maybe it's some weird hard+firmware combination that is triggering it.
Anyway, reflash stock a few more times and see if that helps.