So I was having the issue with the settings menu force closing after I rooted the device.
This morning I've done a factory data reset, gone to turn the tablet on, and I'm not getting "The application OLS (process com.sony.nfx.app.ols) has stopped unexpectedly. Please try again.
Can't access the device, tried another factory data reset, can't flash a firmware as I can't access the device.
Not very happy at all.
But any ideas please?
**I can get into the settings menu and when I press the home button is when I get the OLS force close, so I assume it's the home launcher, I did remove it when my device was working.....
I can't access device storage either, even when my device is on - or ADB, but I can access an SD Card through the boot menu.
Well factory reseting doesn't restore anything you deleted from system, but wipe anything else you installed.. so there's the big problem.
On my tab, I can force a boot loop by holding volume down when booting (hold vol down for what seems like an eternity/till you are satisfied that it is boot looping).
ADB seems to work here, so you could potentially push a different launcher apk and get it going that way.
Thanks for the response Dan,
What I can do is start the device, there's no launcher there, but inbetween the force closes I can get into the settings, there's no force closes when I'm in there.
I connect the USB, ADB Devices and it shows, I can pull from the /system but not push.
As soon as I type ADB Shell, then the commands, it tells me "error: device not found"
Exit out of ADB Shell, ADB Devices again, and it's there - but ADB Devices when inside ADB Shell shows nothing.
I've tried all of the OTA packages in the other thread and nothing - I'm at a bit of a loss, i doubt Sony would work with me on this one, so It looks like I've got £349 of paper weight. Any ideas on the ADB? At least then I could push a launcher in.
The issue clearly is becuase there's no launcher.
I remove the default launcher from the /system/app folder and install ADW, the factory reset obviously removed it, hence there's no launcher...
What if the APK for ADW was made into an update.zip?
Would it flash when I hold down power + volume+, Update System from zip?
bummer
Not really sure what can be done if you deleted them from the system and the reset does not reinstall them.
Perhaps someone who has rooted can send them to you, but not sure how that would work.
I'll get in touch with Sony tomorrow, now I know that this is my own fault, but under the warranty they are still abliged to fix it, I certainly won't be rooting it again, thats for sure.
I hope they will help me if I'm honest?
Did you have a look at if ADB works for you in the forced boot loop state I mentioned? It could possibly do some extras from there that you can't otherwise.
Also just try sending a third party launcher in so it's doesn't have to go to system, perhaps it will let you write the file then. And hopefully auto - detect it upon booting .
Tried it Dan, if I attempt ADB Install launcher.apk, it starts installation then;
[1] Killed pm install /data....
I'm getting permission denied in every ADB command when in the Boot Loop.
Thanks anyway - I've emailed them, and been totally honest about what I've done.
I could swear all day - I've fixed it, my tablets working again, what a bloody relief. Thanks ADB!
I tried to duplicate your problem with adb :-
Typed ADB Devices - reports attached device OK
Typed ADB Shell - prompt changes to $
Typed ls - shows root of tablet
Typed cd system - changed to system directory
Then ls again then cd app then ls again - shows all system apps
I then typed ADB devices again and lost the connection to the tablet
It would seem that on my tablet at least that typing ADB devices whilst within the ADB shell breaks the connection with the tablet
Thanks for testing it praed0r, I'm pleased to know that it's not just me that had that issue.
It may be of use to someone, but what I did was mount the /system partition as rw using busybox.
Code:
adb shell
su
busybox mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
From there I removed the app that kept forceclosing, in this case it was OLS (or something like that)
I then mounted the /data drive with;
Code:
busybox mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /data
Then using cp instead of ADB Push,
Code:
cp /sdcard2/golauncher.apk /system/app/golauncher.apk
Rebooted the device and it all worked fine, GoLauncher booted as my default launcher.
For some reason it didn't like adb push, and would give me permission errors, but mounting as busybox fixed it all....
I changed the build.prop so that it would system update, it indeed does, but all STOCK apps (Sony apps) force close, it could be becuase of the framework.jar from the other thread, so I'll try and source one from a kind individual. Then I'll do the update and my system will be OK.
I'd consider myself very lucky this time, lesson learnt not to tweak with things.
I'll stick to the build.prop/local.prop tweaks for now
Any idea why the system apps aren't working, i've retraced my steps to before it happened, the only notable thing that would have an affect was changing the framework.jar?
im having trouble wirh "reboot recovery" command in my terminal/adb shell
when i try to run in terminal, i get "not permitted!"
and "adb shell reboot recovery" returns [1] Segmentation fault reboot recovery
if i try running reboot -f in terminal or adb shell, i get "usage: reboot [-n] [-p] [rebootcommand]"
i've checked /system/bin, and the reboot bin is there
i've checked the permisssions, originally set to rwsr-sr-x
changing them to rwxr-xr-x makes no change
i found several threads with ppl having the same trouble:
http://forum.xda-developers.com/show...postcount=2040
http://forum.xda-developers.com/show....php?t=1280074
http://forum.xda-developers.com/showthread.php?t=935715
the only one i found useful is the 1st one
the only way i got reboot working is by deleting /system/bin/reboot, and using "reboot -f". without the -f switch nothing happens. if i do reboot recovery -f, it only rebots
but what i really want is to reboot into recovery. any idea on how to? i read in first linked post that the problem is in symlinked reboot to busybox, thats why deleting helped somewhat. anyone has an idea on how to get rebooting to recovery in terminal working?
oh, and my rom is rcmix 4.0. i've read that problem is rom related. but i dont want to switch, because it would defeat the purpouse in the first place....
get root permission first
did you try to "su root" first?
t0mas_ said:
im having trouble wirh "reboot recovery" command in my terminal/adb shell
when i try to run in terminal, i get "not permitted!"
and "adb shell reboot recovery" returns [1] Segmentation fault reboot recovery
if i try running reboot -f in terminal or adb shell, i get "usage: reboot [-n] [-p] [rebootcommand]"
i've checked /system/bin, and the reboot bin is there
i've checked the permisssions, originally set to rwsr-sr-x
changing them to rwxr-xr-x makes no change
i found several threads with ppl having the same trouble:
http://forum.xda-developers.com/show...postcount=2040
http://forum.xda-developers.com/show....php?t=1280074
http://forum.xda-developers.com/showthread.php?t=935715
the only one i found useful is the 1st one
the only way i got reboot working is by deleting /system/bin/reboot, and using "reboot -f". without the -f switch nothing happens. if i do reboot recovery -f, it only rebots
but what i really want is to reboot into recovery. any idea on how to? i read in first linked post that the problem is in symlinked reboot to busybox, thats why deleting helped somewhat. anyone has an idea on how to get rebooting to recovery in terminal working?
oh, and my rom is rcmix 4.0. i've read that problem is rom related. but i dont want to switch, because it would defeat the purpouse in the first place....
Click to expand...
Click to collapse
sure i did... there was something strange with the rom i was trying it on, there was several runnymede roms that had the problem
How to start a question huh?
how can restore data / system into the devices we do??
I did order
adb shell
# wipe system
it was a big mistake for me
anyone can help me?
I am what happens when I do a command?
adb shell
# wipe system
sorry for my bad english
Good morning,
I have the following problem with a tablet of a child's parents bought in December.
The boy was set to release by drawing on the screen. Now after he has made a number of attempts is displayed when the message "Too many attempts to enter the sequence" and requires the google account. The problem is that you do not remember your credentials, or because you do not connect to the wifi network is not able to validate credentials.
To get around this I did the following tests:
1) attempt to enter the recovery mode by pressing volume + and power
2) attempt via adb with the command "adb reboot recovery"
But every time you restart it is as if there is no recovery mode and starts normally and returns the usual screen that asks for credentials.
I also run this procedure:
> Adb-d shell
# Sqlite3 data / data / com.android.providers.settings / databases / settings.db
sqlite> update system set value = 0 where name = 'lock_pattern_autolock';
sqlite>. exit
# exit
but when I reboot I get the same error message with the introduction of the credentials.
Nobody can help me?....:crying::crying::crying:
Go to recovery and restore factory
If USB debugging is active, do this:
Code:
adb shell rm /data/system/gesture.key
let that finish then:
Code:
adb reboot
Your tablet will reboot, and you should be able to enter any code, and it will unlock.
thanks so much, with your help I solved the problem ............................ :good::good::good::good::good:
try to install the application "Screen Lock Reset" from google play
it may do the job for you
yiorgosc said:
try to install the application "Screen Lock Reset" from google play
it may do the job for you
Click to expand...
Click to collapse
without unlocking the phone, yeah right.
Temporarily haven't meet this situation.
?? Get Temp root, mount, as soon as I run "rm /data/su.img >NUL" phone reboots ??
I know little to anything. Maybe I am missing some attributes or a watchdog app I am not aware of? I have been trying to root a galaxy s6 SM-G920AZ it also has a locked bootloader as well. I have gotten to the point I have tried every root app including Chinese ones. I found "MobileGo" they go by many names and I tried one of the well-known ones and it got half root in 1 time. I give it a try within 30 seconds it says root. I start loading supersu and busybox and rebooted did some looking around came across this g920a and g925a root
A boot root does not work any longer for me. But the SuperSU manager .bat file looked good except a su here a cd there. I tried it as a batch no go. So I did it line for line and as soon as I get to "adb shell rm /data/su.img >NUL" within the batch file. Phone reboots and root is gone. What am I missing? Is there a watchdog app or am I mounting wrong? Below I will paste the commands I ran via adb I could run on a terminal. I never post but this is making want it even worse.
Phone is the SM-G920AZ I have it running 6.0.1, SP = June 1, 2016, Kernel Jun 8th 2016. Build = MMB29K.G920AZTUU4CPF2. Bootloader locked down. No Oem Unlock.
Procedure: Using a 1 click root pc app seems to get root after a wipe / reset within 45 seconds. I am getting 2-3 temp roots before I reset brings it back down to a minute or less. Then I connect via adb below are commands I have run than the last one phone reboots.
adb wait-for-device
adb shell
adb shell su
adb shell mount -o rw,remount /system
adb shell mount -o rw,remount rootfs /
adb shell cd data
adb shell rm /data/su.img >NUL <---- As soon as I send it the screen goes dark.
Like I said I do not know a lot. So it may be something basic or goog is throwing more roadblocks on the opensource I did the search here and on google but could not find much with a good timestamp. 2011 was a while back. Thanks for any info I am going to return to searching myself.