Hi all, I have a ME170C (K017) that has entered demo mode but as there is no demo mode content on this model it just stops every few seconds (Demomode has stopped working), never actually entering demo mode proper. For this reason I cannot use the "press the back button for 10 seconds" method to reset my tablet. This is a known problem and Asus have a webpage where you can download the content for every tablet that this effects except for the ME170C!!
My question is this, does anyone KNOW how to reset this tablet when affected by this problem? I can enter recovery mode and load firmware but demo mode just overwrites or hijacks the firmware after reboot.
Bump
chrissyboyhat said:
Hi all, I have a ME170C (K017) that has entered demo mode but as there is no demo mode content on this model it just stops every few seconds (Demomode has stopped working), never actually entering demo mode proper. For this reason I cannot use the "press the back button for 10 seconds" method to reset my tablet. This is a known problem and Asus have a webpage where you can download the content for every tablet that this effects except for the ME170C!!
My question is this, does anyone KNOW how to reset this tablet when affected by this problem? I can enter recovery mode and load firmware but demo mode just overwrites or hijacks the firmware after reboot.
Click to expand...
Click to collapse
If you know how to use adb (or terminal emulator) you can use getprop to see if there is anything APD related. There should be at least one system property present affecting this. Then use setprop to set it to 0 / false or whatever opposite to what it is. If you have APD partition, I can send you the files needed. Also if you have root you may just delete the demo app as it cannot stop working if it's not present right?
Related
Hi all,
Whenever I go to use a program for the first time that requires root, my screen goes black and processes start freezing. Eventually, a box comes up saying that the "Activity SU Request" process has frozen.
Any idea what's causing it (could it be the amount of apps i've installed?) and/or how to remedy it?
EDIT: found this:
@Androidandy the easiest way to get it working seems to be:
turn on your phone by holding the home+end(power) key
press alt+x to enter the recovery console and then press enter when it asks you
next type:
mount data
rm /data/data/com.koushikdutta.superuser/databases/superuser.sqlite
if you have the problem where it says this file does not exist, type:
rm /data/data/koushikdutta.superuser/databases/superuser.sqlite
Click to expand...
Click to collapse
Sorry for asking without looking completely thoroughly first, a mod can close this thread if they like.
blakew said:
Hi all,
Whenever I go to use a program for the first time that requires root, my screen goes black and processes start freezing. Eventually, a box comes up saying that the "Activity SU Request" process has frozen.
Any idea what's causing it (could it be the amount of apps i've installed?) and/or how to remedy it?
EDIT: found this:
Sorry for asking without looking completely thoroughly first, a mod can close this thread if they like.
Click to expand...
Click to collapse
Or...... dear lord, why.... you could just go to Settings>Applications>Development and enable "USB debugging". It's a known problem with the current SuperUser.apk
Usb debugging simply isn't working with my stupid windows computer, and I'm too lazy to boot it into linux. I found out the hard way that the recovery console doesn't work on my phone, I must have forgotten to update the phone somehow. I was fiddling with all the key combinations, conveniently forgetting alt + w = wipe.
Managed to get an old backup working, and the SU popup is working again.
Hi,
I'm using a TMobile 4G DS7 in Europe (no SIM card); last week as I restarted it (battery was very low) I started receiving error messages (Email app has stopped unexpectedly, then Gmail and you name it...) and was sent back to the setup wizard.The DS7 was running on the original setup, no OS upgrade had been done.
I tried a factory reboot which didn't change anything.
I started reading this forum and tried the 3 options which are described
1- updating with a 306 .pkg file on the SDCard
the following takes place
Booting kernel recovery Image
Blue text
Finding update package
Opening update package
Verifying update package
Install modem error . System will upgrade again. (90% bar)
Screen turns black then reboots
and back to square one !
Trying other packages results in an error message, process stops at verifying update package .
2- Fastboot mode
I downloaded and installed the drivers
I put DS7 in fastboot mode and get the fwg :
Username : cmbuild hostname : ***** buildnumber : ******
Build on Mar 11 2011 17:19:36
Starting Fastboot USB download protocol
On PC I go to the directory where the fastboot.exe is stored .
When I type < Fastboot devices>
I get <? fastboot> which seems to indicate that no device is identified ( under Config panel in Windows I can see that the device is recognized as an Android device) ....
3- NVFlash mode
I put the DS7 in NVFlash mode connected it to my PC . The config panel showed there was a prob (yellow triangle). I installed the driver .... and now the device does not even appear when I go Config panel / System
So I get nowhere under any of the 3 options ; can I just throw away my DS7 or is there still some hope ? things I haven't done correctly ?
Any help suggestion would be most appreciated.
Thx in advance to whoever wil read this thread.
FG
the ???? Device under fastboot is normal
ONce you put the device into NVFlash mode and you install the drivers, open up Device Manager and look under the USB section, you should see something about Nvidia recovery mode.
giveen said:
the ???? Device under fastboot is normal
ONce you put the device into NVFlash mode and you install the drivers, open up Device Manager and look under the USB section, you should see something about Nvidia recovery mode.
Click to expand...
Click to collapse
You're right. I flashed everything went all right but after "pinbooting" no change still stuck.
FGMareil said:
You're right. I flashed everything went all right but after "pinbooting" no change still stuck.
Click to expand...
Click to collapse
You might be in read-only mode, which can only be fixed by Dell
giveen said:
You might be in read-only mode, which can only be fixed by Dell
Click to expand...
Click to collapse
The OP stated that the battery was low which is one reason some have claimed to cause this.
Sister says she was driving and phone suddenly factory reset (android recovery icon with text saying erasing, or something along those lines). After the process completes you are greeted with the setup screen to select your language and continue setup. Took a while to get past this since this process somehow also turned on voice assistant. If anyone else experiences this, you need to use two fingers to scroll and tap the item you want, then double tap it to select. (Ex: when you get to a keyboard, to type the letter "a" you need to tap a to highlight it, then double tap "a" to actually send the letter to the textbox. Powered off and jumped into recovery menu which showed a system update progress bar then displayed the following:
LMY47X.G920TUVU3DOJ7
....
(Recovery Menu Options)
....
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : TMB
Successfully applied multi-CSC.
I found a post elsewhere about CSC which indicated it had to do with regional codes which will identify the firmware to issue to the device. The post also said after updating the code your device will reset. So, any thoughts on why this would randomly happen? Phone lock screen was secure so accidental taps/presses seems unlikely. I wasn't present at the time of the incident so I cant be certain of each step that took place before it randomly factory reset.
NOTE: Device is fully stock, never rooted or attempted to root. The phone is up an running so this is not a post requesting help for that, just to share experience with others that may run into this issue and possibly find out what caused it.
Hi there,
last morning my G Watch R rebooted and after that there was some kind of bootloop, the Google animation started and after some time just stopped and the watch rebooted. I put it in Fastboot mode and charged it for some time, then i picked it up and noticed it already rebooted and this time it was working... But now I have the Problem that bluetooth is not workng anymore, in System Settings it shows the device name without the 4 numerical characters just as 'G Watch R'... After enabling developer mode and starting an ADB shell I did a 'logcat' and there seems to be an issue with the file '/data/misc/bluedroid/bt_config.conf, which can't be accessed to start the bluetooth stack. So I installed TWRP on the watch and went to the mentioned path just to see there is no single file in there... I looked on my phone in the same path and there are 3 files, 1. bt_config.conf, 2. bt_config.bak and 3. bt_fw_version.txt. Does anyone know how I could restore those files, I already tried flashing the latest firmware but I guess those files are not included in the updates because they contain data like MAC Address and so on. May be someone can take a look at his files on the watch and post them here without data like MAC and so, so I can try to put them back to where they belong with my own data... I guess my flash somehow got corrupted and so the files are gone.
Druidster
The phone doesn't start after installing EdXposed and the Riru Core Magisk module.
I want to enter Safe mode, but it doesn't work. I somehow managed to enter safe mode previously out of pure coincidence (no idea what I did, I pressed some buttons and i got there during a boot sequence, but it was nothing like the tutorial that Google gives you on how to do it properly).
So, I read you can do it like this:
https://support.google.com/pixelphone/answer/2852139?hl=en
However, this doesn't work for me, here's my boot process:
Power on
Unlocked bootloader warning (I skip it)
Google logo shows up
Screen color calibration changes slightly
Google animation starts (i press volume down)
Google animation ends
Normal Google logo stays there for a few seconds
Loading bar appears
Loading bar stayed there overnight (phone doesn't get hot or anything)
Is there any way to:
Enter safe mode properly
Start a terminal in recovery mode (like TWRP) to use the mm module to disable Magisk
Have an on device file manager (like TWRP) to manually delete the app
Delete files using adb
Get a normal adb shell (not sideload)
EDIT 1:
Starting "rescue mode" via fastboot shows the bootloader warning again, then the Google logo and then it's stuck (no color shift, no animation). Same for "recovery mode".
I cannot connect via adb/fastboot while the Logo is showing.
EDIT 2:
I managed to start "rescue mode" by doing the following:
Press power button
Press power button again (Entry selected: "Start")
Press both volume buttons and don't release them (I'm getting desperate here lol)
Bootloader warning (not skipped)
Rescue mode shows up (opened up Android, says "No command")
I can connect via adb, but "adb shell" or any other useful command says "error: closed"
EDIT 3:
Wtf, I got an adb shell by doing the following inside rescue mode:
"adb shell" -> Error
"adb pull /system/" -> Error
"adb pull /etc/hosts" -> Error
Phone restarted
Bootloader warning (skipped it)
Google logo, Animation & loading bar
adb connected
EDIT 4:
I entered the adb shell and used "setprop persist.sys.safemode 1" (source) (which registered correctly), but after rebooting, the phone still loads forever.
EDIT 5:
Turns out Safe mode didn't work because of Magisk/Riru/EdExposed or whatever, so I disabled Magisk by "touch /cache/.disable_magisk" (source) and now I successfully booted into safe mode.
Can you type up a more coherent guide to what you did? I'm facing the same problem and hoping to fix it without having to wipe my phone again! Thanks!
cubsrule93 said:
Can you type up a more coherent guide to what you did? I'm facing the same problem and hoping to fix it without having to wipe my phone again! Thanks!
Click to expand...
Click to collapse
Using this will most likely get you booted up to fix what you need...
https://forum.xda-developers.com/pixel-4-xl/themes/magisk-modules-disabler-booting-magisk-t3990557
cubsrule93 said:
Can you type up a more coherent guide to what you did? I'm facing the same problem and hoping to fix it without having to wipe my phone again! Thanks!
Click to expand...
Click to collapse
Where are you stuck?