Hi,
I have a mi note 3, with global ROM. Yesterday, it received an OTA upgrade to 10.4.2.0, and immediately after the install, when the phone booted, it started showing errors about Find My device crashing. I managed to enable developer mode (this phone was unrooted and stock recovery with locked bootloader) and using adb I could stop the find my device crash by removing the package (so it wouldn't reboot) and backup about half of its contents. It did reboot though, and then It just would not boot at all to the system and would just keep boot looping (i never got the home screen).
Having tried a few things with ADB, I decided to do something a bit more drastic and I used ADB sideload to install the same ROM again using the recovery mi assistant option. That worked but still the phone wouldn't boot, so I decided to erase user-data (which according to the xiaomiadb does remove all apps but not pictures and all other stuff). Then the phone did boot, but It got stuck again, this time on the android setup screen where it says something like 'wait a second while we setup your device...' and getting again the same error about Find My Device crashing.
Is there any hope on recovering the data in the phone? I had two ideas but I have no idea if they are stupid or if they have any chance of working:
1-. Unlock bootloader using the Xiaomi app, in fastboot, but instead of rebooting, after unlocking using fastboot to load twrp and then trying to save the data via twrp
2-. Wait for another global rom update, apply that via recovery and see if it does fix the issue with Find My Device
Is any of those ideas realistic? If not, is there any chance to save the data from the phone? even if it implies opening it and so?
Thanks!
The first option seems extremely risky, unlocking the bootloader will format all data - maybe before reboot. The second needs patience, most probably that was the last miui 10 stable. Don't you have a miui account? Most of your stuff is there, you could login from your browser and check it out.
Thanks dpikros. Yes, I have access to the mi account, but I never trusted mi cloud with my data, so I had all sync to mi cloud disabled unfortunately.
I tried installing the previous MIUI, but it's based on Android 8.1 and the sideload won't allow me to use it. I think same will happen with developer ROM.
Does anybody know if the data format happens before or after reboot when unlocking? I was thinking, unlock bootloader and then use fastboot to boot the twrp image (without even flashing it) but not sure if the Xiaomi unlock app will automatically reboot the phone or if it will somehow delete if from unlock directly.
Thanks
Related
I am running stock ROM and have bootloader unlocked and TWRP already installed. The phone was rooted without problems. I was getting an error from Super SU, so I looked up how to fix it online and the suggestion was to install an older version and then try to upgrade it. It was hard to find a zip from a legitimate source but once I found it, TWRP did not show the directory I was looking for (this was previously available when I rooted it). This is where I did something stupid and looked around in the settings and found the Slot A / Slot B option. I switched from B to A and the phone got stuck on the boot animation for several minutes after rebooting. I decided to reboot into TWRP and switched the slot back to B. This brought the phone back but WiFi is off by default and whenever I try to turn it on, it doesn't change.
I have seen a couple of other people mention similar issues about losing wifi after a root or changing the slot. What's the fix? I am wondering if there is anything else "broken" after the slot change and if I should do a factory reset (I would hate to do that as I was almost finished setting up this device). I have also received the error message saying "Process System isn't responding" in the settings menu a few times. It also seems like the finger print scanner isn't recognizing fingerprints any more and face unlock isn't working
One possibility is, that SuperSU isn't that compatible anymore. Magisk does a wonderful job and no problems so far. Maybe you should give it a try and switch from using SuperSU to Magisk.
shagexpert said:
I am running stock ROM and have bootloader unlocked and TWRP already installed. The phone was rooted without problems. I was getting an error from Super SU, so I looked up how to fix it online and the suggestion was to install an older version and then try to upgrade it. It was hard to find a zip from a legitimate source but once I found it, TWRP did not show the directory I was looking for (this was previously available when I rooted it). This is where I did something stupid and looked around in the settings and found the Slot A / Slot B option. I switched from B to A and the phone got stuck on the boot animation for several minutes after rebooting. I decided to reboot into TWRP and switched the slot back to B. This brought the phone back but WiFi is off by default and whenever I try to turn it on, it doesn't change.
I have seen a couple of other people mention similar issues about losing wifi after a root or changing the slot. What's the fix? I am wondering if there is anything else "broken" after the slot change and if I should do a factory reset (I would hate to do that as I was almost finished setting up this device). I have also received the error message saying "Process System isn't responding" in the settings menu a few times. It also seems like the finger print scanner isn't recognizing fingerprints any more and face unlock isn't working
Click to expand...
Click to collapse
I had the same issue when I first got my 6 when I was playing around with the slots. Also my original TWRP install for some reason would crash and reboot whenever I plugged in the data cable while in TWRP. I ended up flashing back to stock OOS 5.1.5 through fastboot (used the flash-all command) and then reinstalled TWRP and everything has been working great since then.
MickyFoley said:
One possibility is, that SuperSU isn't that compatible anymore. Magisk does a wonderful job and no problems so far. Maybe you should give it a try and switch from using SuperSU to Magisk.
Click to expand...
Click to collapse
The instructions I followed already installed Magisk to the phone. I wanted Super SU because some of the other chainfire apps like Liveboot and rooted apps like Titanium backup said Super SU is needed (Titanium said Magisk will work but may not be reliable for some newer versions of the ROM). I can live without liveboot but really need Titanium to reliably transfer data from my older phone.
To be honest I didn't know they did the same thing (magisk and Super SU). I am curious now, what if I factory reset my phone and attempted to install Super SU instead of Magisk this time?
If I do a factory reset (let's say I want it just like it was out of the box and I format the data partition as well), will I need to root the phone again? I am asking because I don't know which part of the instructions I should ignore. I am sure TWRP will already be installed after the reset so I would only need to install the extra apps...
You don't have to format data. Just factory reset it. Then use "fastboot boot twrp.img", don't allow modifications, flash a kernel you want (if you want one - I really recommend ElementalX) and then the latest version of Magisk (16.4 BETA currently). Did so - all fine. And yes: Even Titanium Backup works without any issue with Magisk.
We had similar problems with TWRP on the Razer Phone when it was new. We solved the problem by using the TWRP boot image to flash the stock boot image and then flashing a TWRP zip. I just got the OnePlus 6 yesterday and haven't really messed with it yet but everything sounds the same to me so far.
I read more about TWRP and realized what I was doing wrong when the directory with zip files wasn't showing up. When TWRP showed up I was supposed type in my regular unlock password to decrypt storage. When I did that the folder I was looking for showed up. I made a backup through recovery (which took like an hour, may be because the external flash drive I attached was really slow - and the size of the backup was about 12GB). After that I installed the zip file for Super SU, just to see if it worked - it showed the installation was successful but the app was still missing from the app drawer. Now I wanted to factory reset the device and start over.
I went into wipe and there was nothing listed under the wipe screen. I went into Advanced wipe and wiped whatever was selected by default. The selected items were Dalvik / ART Cache, System, Data. There was also "Internal Storage and USB Storage" that wasn't selected.
I swiped to wipe, it wiped everything. Then asked reboot, I rebooted, got a blank screen with white LED for a long time. When I plugged it into the computer it recognized the device as Qualcomm HS-USB Diagnostics 900E (COM4). I rebooted it by holding Power + Volume Up + Volume Down. I tried to boot into boot loader next. This brought me to another blank screen. The computer still makes a noise when it reboots but screen stays black. The only message that shows up is the one saying boot loader is unlocked. Did I brick my phone? This keeps getting progressively worse.
shagexpert said:
I read more about TWRP and realized what I was doing wrong when the directory with zip files wasn't showing up. When TWRP showed up I was supposed type in my regular unlock password to decrypt storage. When I did that the folder I was looking for showed up. I made a backup through recovery (which took like an hour, may be because the external flash drive I attached was really slow - and the size of the backup was about 12GB). After that I installed the zip file for Super SU, just to see if it worked - it showed the installation was successful but the app was still missing from the app drawer. Now I wanted to factory reset the device and start over.
I went into wipe and there was nothing listed under the wipe screen. I went into Advanced wipe and wiped whatever was selected by default. The selected items were Dalvik / ART Cache, System, Data. There was also "Internal Storage and USB Storage" that wasn't selected.
I swiped to wipe, it wiped everything. Then asked reboot, I rebooted, got a blank screen with white LED for a long time. When I plugged it into the computer it recognized the device as Qualcomm HS-USB Diagnostics 900E (COM4). I rebooted it by holding Power + Volume Up + Volume Down. I tried to boot into boot loader next. This brought me to another blank screen. The computer still makes a noise when it reboots but screen stays black. The only message that shows up is the one saying boot loader is unlocked. Did I brick my phone? This keeps getting progressively worse.
Click to expand...
Click to collapse
OK good news! I tried one more time and fast boot showed up. I was able to get into recovery. I have the backup so I will try to restore that. I don't know what to do after that. I am thinking wiping without getting into advanced mode.
shagexpert said:
OK good news! I tried one more time and fast boot showed up. I was able to get into recovery. I have the backup so I will try to restore that. I don't know what to do after that. I am thinking wiping without getting into advanced mode.
Click to expand...
Click to collapse
When your phone booted straight into that mode with black screen and the led, then you bricked it. Same happened to me 2 days ago. The solution was to use the Msmtool from another thread and it worked great. Just follow the guide. But it will wipe your device. And you have to install oxygenos manually via "local upgrade". If you have a question, just ask
What I ended up doing was restoring from the backup I had. This was the "bad backup" without WiFi and broken finger print and facial recognition. After the restore, I did a normal wipe (not advanced). This reset the phone to factory settings. Once I configured WiFi and signed into my Google account, Google offered to recover from a cloud backup of my One Plus - I didn't know Google made these backups. It downloaded all the apps automatically. I don't know yet if I have sign into all of them all over again.
The bad back up saved my ass, I wasn't even planning on making it. I was just testing the backup feature. That's why you should always do a backup, even if the device isn't in ideal configuration.
shagexpert said:
The instructions I followed already installed Magisk to the phone. I wanted Super SU because some of the other chainfire apps like Liveboot and rooted apps like Titanium backup said Super SU is needed (Titanium said Magisk will work but may not be reliable for some newer versions of the ROM). I can live without liveboot but really need Titanium to reliably transfer data from my older phone.
Click to expand...
Click to collapse
I rooted my phone with Magisk and installed the 5.1.6 via OTA (and reroot via installed Magisk Manager). So no need to install TWRP so far.
Titanium Backup runs flawlessly with Magisk (already on my OP 3T and my OP 5).
So give Magisk a try, I never had such an easy and reliable update as the one from 5.1.5 to 5.1.6
Helium is a great alternative to titanium.
My stock Nexus 5 hardlocked today while attempting to connect to a wifi network. Upon restart, the boot-up animation took longer than usual, then displayed the 'Optimizing Apps' screen (which is not typical). It completed optimization on 5 apps, claimed to be starting Android, and then reset back to the boot-up animation, continuing the same cycle.
Unsuccessfully tried to boot into safe mode, although I can access Recovery Mode. Wiping system cache did not help. Installed ADB/Fastboot and sideloaded the original OTA without any improvement.
At this point, I'm hoping for either another path to get the device to boot or a way to extract some critical data (SMS, docs, etc.) off the device before doing a factory reset.
If the bootloader is unlocked, you could try flashing TWRP, booting into TWRP, and pulling off the data.
audit13 said:
If the bootloader is unlocked, you could try flashing TWRP, booting into TWRP, and pulling off the data.
Click to expand...
Click to collapse
Sadly no, fully stock phone.
Gave up and pulled the trigger on factory reset. We'll see if it helps.
On the plus side, this incident has motivated me to unlock and root my phone, hopefully expanding my options for the next time this happens.
Yup, an unlocked bootloader is definitely a plus in these situations.
I always unlock the bootloader unless it voids the warranty on the phone. Once the warranty is over, I unlock it if possible.
Factory reset seemed to work. Now unlocked and rooted!
hello, recently i bought myself a new op6, as it was good for modding and such. unlocked the bootloader, flashed twrp, and rooted it the day after, used it for a couple of days, before I installed elementalX. was happy with that for some days. then I decided I wanted to try out lineageOS, in order to de-google my self, in my quest for privacy.
TL;TR:
mtp is not working after flashing, neither is twrp, cant even access it through fastboot with booting the .img file.
does this have something to do with the a/b partition thing on these phones, perhaps?
I would guess that I flashed lineageOS the wrong way, and that is the issue, but since I cant access twrp, I cant restore and reflash the correct way.
more detailes below
--------------------------------------
backed up before installing elementalX, to have something to go back to, in case of failure
rebooted into twrp, and wiped everything, exept internal storage (i looked this up several places, prior to flashing, that this was the way to do it, so assumed this was the correct way)
flashed lineageOS 15.1
wiped dalvik and rebooted
took ages to boot, so figured id reboot again a couple of times, with no succsess
tried to boot to twrp, to restore back state prior to flashing, but ended up in lineageOS' own recovery.
tried to boot from fastboot, and reflash twrp
goes out of bootloader and screen turns black, led turns on, and nothing. tried waiting for a bit, but nothing seems to happen
have to manually turn of phone, and reboot. tried this several times, but same result.
after reboot i turned to the recovery to look after any solutions there, but nothing
started adb, just to check, and it says "device unauthorized"
sortof gave up, so figured I could atleast get going installing apks, but after downloading f-droid, I couldnt get it to install
found out this was some sort of permission issue, so had to move it to internal storage to get it to install
after installing some apks, I was going to transfer my contacts from my pc, but cant get mtp working..
if someone know a soulution to this, I would be really greatfull, as Im at a loss. cant seem to find anyone who has had a simillar issue..
You can always use EDL and MsmDownloadTool. Check that thread
thanks, will definetly check that out.
now it apears that I have another issue, the key for adb is no longer valid. i did get the prompt when I connected the usb, but that didnt appear to do anything. have tried to revoke it, reanable, reboot both phone and pc, also delete the keys on my pc. I have no root access anymore, so cant really enter the root on my phone, to pull out the keys there, neither can i push my own keys, as it seems atleast. I may be doing it wrong too, for all i know..
If you can enable debugging and see your phone with adb devices, you can adb push /sdcard/<romfile>.zip
I am able to enable debugging mode, yes. Will this enable me to push my own key, or any other existing key for that matter, to remove the unauthorized label?
Id also like to at that i done goofed when flashing lineageOS. Ive come to and understanding that I have to flash OOS 1.5.1 (i think that was it) on both slots, before then flashing the custom rom onto the device, and reflashing twrp after that. Which i did not do. I also were running pie at that time, so theres another mistake I made to begin with. Neither was I really aware of the concept of a/b partition system at hand..
Can i switch slots in fastboot, and then boot inton twrp, and reflash back to OOS 1.5.1, on both slots, and then reflash LOS 15.1? And ofcource reflash twrp and root afterwards, which totally slipped my mind..
Hi, I was trying to update the phone by OTA with an official firmaware, but something went wrong and now it goes in bootloop with the MI logo that keeps appearing on the screen.
I want to flash a clean firmaware to solve this thing, but without unlocking the bootloader it seems impossible.
So now i'm trying to unlock the bootloader, but using the Mi Unlock Tool I need to give some permission that I can't, because I can't turn the phone on!
It asks me to add my account on the phone (that was wiped during those steps)
How to solve this?!
Just to complete this thread. Now the phone turned on, only God knows how.
I did nothing, nor charging, it just turned on when I press the power button. That's a miracle.
But, the question is still there... If this happens again, how can I solve it?
That's a common problem with the MIUI 11 update, the phone takes too much time to charge system files while updating, and that results in a bootloop that isn't really a bootloop, bootloader tries to recover the phone and solves the problem automatically but requires to reboot some times, after that the phone seems to work normally but is recommended to do unlock process with mi unlock after successful update, and after that do a clean flash with fastboot method using mi flash tool
I found the phone in my bag with a discharged battery and does not want to boot all the way. It shows the animated MIUI logo for about 1 minute and then restarts, sometimes showing the menu to switch to 'wipe data' and 'assistant'.
It's all stock, locked, up-to-date, I think still on Android 10 or which one it is. I did not install any new apps and don't even use the phone for anything other than gaming.
I've tried connecting with PC Suite but it doesn't see the phone. Fastboot anything does not work since the bootloader is locked. I know I can wipe data and be done with it, just wondering if there is anything else I can do.
EDIT: I've wiped the data and reinstalled the phone but would like to know if there is a way to avoid this in the future.
Unlock bootloader. This is very important. Then you have full control over the device.
For example the other day I had hard brick because fastboot flash was interrupted. And I still managed to unbrick the device thanks to unlocked bootloader and custom recovery.
It's really hard to hard brick this device. I love Xiaomi <3