Database Develop

Phone starts with moving halo and "wissen"... "Is it wiping my phone?"

Phone starts with moving halo and "wissen"... "Is it wiping my phone?"
Just now I took my Nexus 6 out of my pocket because it was very warm.
The screen was all black with in the middle a big Halo moving with the disturbing message "wissen" beneath it.
"wissen" is Dutch for wiping, deleting or removing...
Turning the phone off is possible by holding down the power button for 6 seconds, but then it turns on again after 3 seconds showing that same screen again.
After some fiddling I was able to find a method to turn it off.
I can start the phone by holding down the power button and the volume button (down) which will start the recovery program.
There I can turn it off.
Although I have unlocked the phone and ran modded firmwares I switched to standard factory Nexus 2 years ago and haven't had a rooted phone for all that time.
Recently I installed the 7.1 OTA updated.
I'm afraid this is something like a remote wipe.
It also doesn't ask me to give my PIN which is normal for it to do.
What is happening?
Some more info: Yesterday I bought the "AIO All-in-one Toolbox " after using the free one for 3 weeks. Could that be involved?

It may be formatting and encrypting your data partition.

Yes, but why?
It just went into my pocket this morning....
I came one step further.
As I was still able to get it into fastboot loader I exited with "volume up"
Then it went into an almost normal boot. This didn't require the pin it normally needed.
The device went into a full factory reset.
I thought I would be up and running fast, but after entering my new gmail account/password I got the message that I needed to wait another 24 hours because I did a password reset.
I did this password reset of my Google account out of safety. Now I'm being punished for this....
Luckily I have a spare Motorola G3 with its own SIM, so I can at least use my phone.
I can't even use my Nexus as a phone nor can I go to settings. Maybe if use another Google-account.

Did some more research...
The last Exchange sync was while cycling to work.
Didn't use the phone then nor later.
Because my Google-account is locked I can't do anything with my Phone (not even phone), so I decided to flash an alternate rom on it.
I flashed lineagos and also rooted the device again.
Although I did root my Nexus 6 in the beginning this is the first custom ROM I have on it. I still need to install gapps.
Now I can start using my Titaniumbackup again that I bought several years ago.
I still have no idea how it could have gone into wiping. I put the phone in my pocket while it was screenlocked. The device needs a pincode to unlock.....
I am still unable to use Google Apps. I can run the app, but it doesn't let me install apps.
On the stock rom I was just stuck (stuck rom, haha)..... at the installation screen unable to even make a phone call....
Does someone have any idea???

frater said:
...
Does someone have any idea???
Click to expand...
Click to collapse
My idea is that you have the N6 unprotected in your pocket. Moving or cycling caused activation of a factory reset.

Note 4 Reboot Problem with Weird Temporary Solution

I'll try to make this short.....
I am using N910T3. Phone was charging in car while using (stop by roadside). Out of sudden it shutdown and went into reboot loop and the phone is extremely hot. I took the battery out for soft reset and try to turn on again. Phone will freeze at different screen (Lock Screen, Home Page, Samsung Logo, Powered by Android) and give two separate vibration before reboot.
I thought it is battery problem so I bought a new battery to try, but still the same problem. So I went on to backup all file before I perform hard reset. While doing that, I find out the phone can be use for longer before reboot if it was stay off for a long time. So I have this crazy idea: put it in a fridge. Surprisingly it works! The phone will not reboot anymore and I can manage to backup all file before doing anything else. Also, the phone will not charge if you plug in right after a few reboot.
Then, along with the fridge method, I perform factory reset through normal android setting. Now it will just stuck at powered by android screen while in reboot loop. I then try to flash with Odin, multiple times. Flash by Odin is complete, phone restart, then it freeze and reboot, at different screen (Installing system update, Erasing, powered by android).
Out of frustration I try with the fridge method to flash, and IT WORKS AGAIN!!!. The phone can now boot to welcome screen where you first setup your phone. However, it will then freeze again and reboot while doing so.
There was only this one time, where I left the phone off for a day after flash with a previous stock ROM, turn it on and skip as much setup as I can, finally reach the homepage screen, then will stay on without any reboot issue. I thought I finally fix it. I then power off the phone, put in my Sim Card and SD Card, power it on, then again, reboot issue appear.
I tried flash with latest stock ROM, previous stock ROM (one updates away), flash any stock ROM with pit file. I sometimes will get error code on device after flash (can't remember the exact error). I also cannot boot into recovery mode without flashing a twrp. Sometimes if success, I will get straight to Lock Screen without going through the phone welcome setup process. But again, none of these I tried can solve the reboot loop.
I may went too far and mix up all steps to the phone. Does anyone have any idea how to fix this? Or is my phone, as I believe, has a faulty motherboard that cause the reboot loop? Thanks in advance for reading through my problem!

Hello there, I had a Tmo Note 4 which I loved it until the end, it's a hardware problem and there is no fix for it unless you replace the board, by the time you buy the board and what you need to pay for labor you're going to expend a few hundred dollars, I also tried the freezer method but it finally the phone gave up, it does not turn on anymore. That was my experience. Good luck bud.

oscarmaldonado said:
Hello there, I had a Tmo Note 4 which I loved it until the end, it's a hardware problem and there is no fix for it unless you replace the board, by the time you buy the board and what you need to pay for labor you're going to expend a few hundred dollars, I also tried the freezer method but it finally the phone gave up, it does not turn on anymore. That was my experience. Good luck bud.
Click to expand...
Click to collapse
Seems like that's the case I guess.....But if anyone has any suggestion please do tell so I can give it a shot.

jackgan said:
Seems like that's the case I guess.....But if anyone has any suggestion please do tell so I can give it a shot.
Click to expand...
Click to collapse
Try a firmware flash before newsest. Then take the ota

anyone know if a 910t3 mother board will fit in a 910t frame? Asking cuz I wanna switch them out.

Xiaomi MI A2 turns off when unplugging

Hi.
Today appeared some problems with my A2. When I woke up and unlocked phone it turned off. Yesterday everything worked perfectly fine. I tried like 20 times, everytime the same scenario- turns on, but when I type PIN, home screen is loading, and phone goes down. It may look like bootloop, but its not typical, cuz it goes farther than just booting screen. So I tried to fix, wiped phone, set lang. to Polish, and it dumps again, but I've read somewhere, that it might be language issue, so I wiped it once more and set English. It seemed to be working, but then I unplugged it from my PC (charging only) and it turned off immediately. Worth mentioning is fact, that battery is 92%. What may cause this? Is this some soft problem? Or more like battery issue?
Update: Phone works unplugged, but only on lock screen. Turns down when I unlock.

Ashu14 said:
Hi.
Today appeared some problems with my A2. When I woke up and unlocked phone it turned off. Yesterday everything worked perfectly fine. I tried like 20 times, everytime the same scenario- turns on, but when I type PIN, home screen is loading, and phone goes down. It may look like bootloop, but its not typical, cuz it goes farther than just booting screen. So I tried to fix, wiped phone, set lang. to Polish, and it dumps again, but I've read somewhere, that it might be language issue, so I wiped it once more and set English. It seemed to be working, but then I unplugged it from my PC (charging only) and it turned off immediately. Worth mentioning is fact, that battery is 92%. What may cause this? Is this some soft problem? Or more like battery issue?
Update: Phone works unplugged, but only on lock screen. Turns down when I unlock.
hi i have the same problem with my mi a2. i can turn it on when is on charger but when i want to unlock the screen and to move something on screen is turning off. when i unplug the charger turning off too. do you found solution on your problem ?
Click to expand...
Click to collapse

Hello, I have the same problem. I now have to carry an external battery with me, because plugging it in is the only thing that wakes up my phone. If I don't have a charger, then I have to hold power for 30; seconds to force reset. It's really annoying, causing me to miss calls and alarms. Anyone know of any fixes? Thanks

Hey,
I am facing the exact same problem. Though I had an additional problem. My phone didn't charge when I plugged it in until I restarted it. Factory resedidn't help either.

In both your cases the problem is your wifi even if you dont understand it ...
if you can unlock your phone quickly and toggle off wifi the phone wont reboot or loop
your persist partition is damaged from changing between pie and android 10 ..
look around for a flashable zip to repair your persist ( it does it exist )
or take the long root and use miflash to flash persist by modifying certain files in stock fastboot rom folder
but next time explain your problem better
--- what did you do -- change version ( update or downgrade ) -- did you root -- do you have twrp -- what version of android-- did you return to stock from custom or vice versa --- etc etc etc

KevMetal said:
In both your cases the problem is your wifi even if you dont understand it ...
if you can unlock your phone quickly and toggle off wifi the phone wont reboot or loop
your persist partition is damaged from changing between pie and android 10 ..
look around for a flashable zip to repair your persist ( it does it exist )
or take the long root and use miflash to flash persist by modifying certain files in stock fastboot rom folder
but next time explain your problem better
--- what did you do -- change version ( update or downgrade ) -- did you root -- do you have twrp -- what version of android-- did you return to stock from custom or vice versa --- etc etc etc
Click to expand...
Click to collapse
tried with wifi toggle off but didn't work.
didn't tried persist partition
tried update software but still didn't work.
if there any hardware issue please let me know.

Recovery without losing data

I have a Moto G6 XT1925-5 (64GB version) which doesn't want to start up. It's all totally stock, been updated to Android Pie.
It gets as far as the boot animation, and does that for about 2 minutes, then it boot loops and starts all over again. When it bootloops it gets stuck at the first Moto logo screen (not the animated one) for about 3 minutes before carrying on to the boot animation...
This happened once or twice before, we left it overnight and eventually it started up normally. But it's now been five days and it still hasn't started.
I'm not very experienced with Android hacking/modding, etc but willing to try anything. I managed to get into recovery mode and at the top it says (I presume this indicates the firmware version):
motorola/ali_retail/ali
9/PPSS29.55-37-7-6/16c5a7
Unfortunately USB debugging is not enabled. Is there anything that we can do to recover the data that was on the phone before we wipe it - or is there another method we can try to get it to start up? I saw there's a command adb logcat which looks like it might be useful to diagnose the problem but that also requires USB debugging.
Thanks in advance for any suggestions

There is no chance for you to recover your data in this mode.

WoKoschekk said:
There is no chance for you to recover your data in this mode.
Click to expand...
Click to collapse
Thanks for getting back to me so quickly.
There are several other modes available from the bootloader BP Tools, QCOM, etc but I can't work out how any of them are supposed to work.
One question - on the recovery menu, there is an option 'Mount /system'.
I pressed it and it says at the bottom /system mounted, but then there don't seem to be any obvious ways to access anything.
Is there a way to use this to access OS/kernel logs which might give a clue as to what is going wrong?
Thanks again

Step by step...
The first level of the system, which is accessible for you, is called bootloader menu (fastboot menu). From here you can boot into recovery, system, bootloader itself and some other options you mentioned in your post.
None of these options would help you to solve your problem. These are developer's options.
This level is more or less a one way data connection. The main advantage of this menu is to flash single partitions of your device. But there is no way to get a data output of any partition.
In recovery menu you find the options to wipe your data and to mount /system. Mounting /system won't help you, too. This partition doesn't store anything of personal data. It's read only and not writable for anyone. To be honest, nobody knows exactly the meaning of it in this context. Also you won't access any logs from here.
Generally you can't access the system logs. These informations are only buffered data which is cleared with every reboot. The error message of e.g. the kernel log produced by your system when having a bootloop, is only accessible while your device is looping/freezing. The next reboot erases the logs. They aren't stored somewhere on your device. Even for developers it's very tricky to view the log in such cases.
But what would you do if you get the reason for looping? You are not able to access any system partition. You need root user permissions for that. But rooting your phone will erase all data.
Apart from all that your data is encrypted and remains encrypted until you unlock your screen by fingerprint, PIN or password. No chance to get any useful data as a "third person" outside. It would take several years to decrypt it without the matching key for it.

Thanks so much for this detailed explanation, I really appreciate that you took the trouble to answer the questions in detail and explain what the various options are for.

phone5774 said:
Thanks so much for this detailed explanation, I really appreciate that you took the trouble to answer the questions in detail and explain what the various options are for.
Click to expand...
Click to collapse
No problem!
Maybe you'll find some of your personal data in your Google Drive account...

How the story ended
Thought I'd come back and post in case it's useful for anyone else:-
Due to a religious festival, we left the phone switched off for three days. After the festival ended, we switched it on, and immediately it did the same thing that it had been doing all along (spend a long time on the initial boot screen then a while on the boot animation before boot looping). Bizarrely even though it had been off it did not prompt for the PIN code.
We then held the power button as though to turn it off (but for some reason, throughout the usual power button never actually turn the phone off, it always attempted to restart immediately) and then next time it came on it asked for the PIN and started up normally!
So all in all that was a grand total of 9 days after the problem first happened. Very inconvenient not to be able to use it for 9 days, but it's now working again. We haven't dared to try to restart it since!
Some closing thoughts:
The storage is very full (99%), we wonder if that had something to do with this problem
We have now enabled USB debugging and bootloader unlocking to make recovery easier in future

phone5774 said:
Thought I'd come back and post in case it's useful for anyone else:-
Due to a religious festival, we left the phone switched off for three days. After the festival ended, we switched it on, and immediately it did the same thing that it had been doing all along (spend a long time on the initial boot screen then a while on the boot animation before boot looping). Bizarrely even though it had been off it did not prompt for the PIN code.
We then held the power button as though to turn it off (but for some reason, throughout the usual power button never actually turn the phone off, it always attempted to restart immediately) and then next time it came on it asked for the PIN and started up normally!
So all in all that was a grand total of 9 days after the problem first happened. Very inconvenient not to be able to use it for 9 days, but it's now working again. We haven't dared to try to restart it since!
Some closing thoughts:
The storage is very full (99%), we wonder if that had something to do with this problem
We have now enabled USB debugging and bootloader unlocking to make recovery easier in future
Click to expand...
Click to collapse
When I read this last post, I immediately think of a sticky power button, because if you keep holding the power button after the phone has booted it will turn off again, and start up again. And it would also explain the weird behavior you just described of not turning off but rebooting straight away. I'd say: see if you are able to clean de button with a very thin needle or a crafts- or surgical knife around the edges, is might just solve your problem...

mcremco said:
When I read this last post, I immediately think of a sticky power button...
Click to expand...
Click to collapse
Thanks for that suggestion. Interesting, not something I'd thought of.
For now the phone is working perfectly, provided that have to restart it (i.e. we make sure not to shut it down or let the battery run out) but I'll definitely bear this in mind if the issue happens again.
The power button is working normally to turn the screen on or off meanwhile.
Thanks again for your input which is really appreciated.

First time trying to restart after the above
Since posting the above messages the phone has been kept on all the time and not restarted.
Today for the first time we accidentally let the battery run out and the phone shut itself down.
We nervously plugged it in and tried to switch it back on... and it started properly first time, so perhaps the underlying problem was simply that the storage somehow got too full (in the meanwhile we have transferred many photos and other media to the computer and deleted them off the phone to free up space).
Posting this in case it helps someone else experiencing a similar problem.

Mi 9 Touchscreen does not work (likely software issue), is there a way to get my data?

Hello,
my Mi 9 (stock rom, locked bootloader, never touched anything) recently got into a boot-loop apparently for no reason. After some tinkering it turned on again. Sadly the touch screen does not respond for some reason. The problem is the last backup of the phone is not so recent and I would really like to get all the photos of that phone.
What I already tried:
Connect Mouse and Keyboard via an OTG cable => not recogniced
Letting the battery drain completeley hoping it would reset itself
Fully charging the battery
Connect ADB => cannot authorize without touch
Connect Xiaomi PC Sync software => does not connect probably needs authorization as well
Stock Recovery does not allow to wipe caches
Last resort was to open up the phone and disconnect the battery and reconnect after a couple of minutes (touch did not work before that)
What is not working:
Touch
Face Unlock
USB OTG Peripherals
USB connection to download photos to PC
What had happened:
Phone randomly went into a boot-loop aparently for no reason
At first booting into Safe Mode worked but not for long
Draing the battery completely did not and fully recharging it => Now the phone turns on again in normal mode as well as Safe Mode
Assuming the initial issue was related to a very weak battery
Battery was already weak before everything happened
Now battery only holds charge for a couple of hours in standby
Sadly after booting the things mentioned above did not work anymore
Maybe failing to boot so often has done anything to the software or the cache on the device
Also storage was already pretty full before everything happened, might play into it
Tried many things, last resort was to open the phone and disconnect the battery for a few minutes => did not work
Touch malfunctioned already before that, so it is unlikely that I caused any hardware damage
What i am looking for:
To get my pictures back, I know if I had done a proper backup we would not be in that situation.
Have not yet tried:
I don't know if there is a way to flash the stock ROM via fastboot or if this could help
Could this help?
Can it be done when the bootloader is locked?
Can it be done without loosing data, screen lock pattern is enabled on the phone.
If you have any more ideas please let me know, I already tried everything I could think of and nothing worked.
Thank you a lot

Also I read something about EDL and EDL Pins, would this help me to download the data partition or clear the cache? Would clearing the cache help? Could the data partition be somehow decrypted outside of the phone?