Hello,
i have here a Xiaomi M1903F10G from a good friend, which stuck in a boot loop: phone seems to boot normal, home screen is visible for roundabout 1 second and the phone reboot immediately. Do we have a chance to get the user data (family photos etc.) ?
With Vol+ + Power button i get a "main menu mi-recovery 3.0" with the following options:
Reboot
Wipe Data
Connect with MIAssistant
With Vol- and Power button i can enter Fastboot mode, here are some info:
Bash:
[email protected]$ fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.001s]
Finished. Total time: 0.001s
I can successful enter the EDL mode (i think) via shorting the pins on the main pcb, then phone shows up as "Qualcomm HS-USB QDLoader 9008 (COM6)". According to [GUIDE] How to dump and write back the storage on most of Qualcomm devices i should then use the right firehose file and try to open the partition manager. I tried many different firehose files(see attachments)/storage settings/2 computers(win10x64)/cables(usb-a 2.0/usb-a 3.0/usb-c), i can never successfully open the partition manager.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now the question:what i can do to recover the user data for my friend ? I know i could oem unlock and try to boot into twrp, but as far as i know unlock would wipe all user data. (My friend has also the bill from when he bought the device if that helps).
there is not much you can do on locked bootloader. you can dump raw partitions, that's it. it isn't of any use because of encryption. all you could try is check file system for possible errors (if not metadata encrypted)
have you found loader that worked? try this python script in linux
https://github.com/bkerler/edl
Hello Alecxs,
thanks for your reply. Unfortunately, in the meantime i had to give the phone back to my friend. She told me, she want to try her luck with a commercial data recovery store. Hopefully they are lucky and are able to recover the photos.
Best,
Marcel
Recover photos? Aren't photos synchronised with Google?
Nope.
Then, all data should be backuped. No way to retrieve as data is encrypted anyway
yaro666 said:
Then, all data should be backuped. No way to retrieve as data is encrypted anyway
Click to expand...
Click to collapse
That is not correct, but thanks anyway.
Related
So i was searching around and couldnt find actual answers on how to get rid of that annoying ass sticky bit factory fastboot menu when phone powers up. So i decided to take matter in my own hands and learn a little bit about adb and fastboot commands etc.. Typed in some commands in a certain order and BOOM sticky bit no longer gets in the f-ing way ^^ this should work on any android powered phone seeing how it doesnt go to any specific phone. So far i learned that it works on the xpirea (how ever you spell it) and the droid razr m consumer and dev edition. so here we go.
MAKE SURE YOU HAVE USB DEBUGGING ENABLED
Files to download:
Android.zip: http://www.mediafire...0imf9xv2uicwkbh
Latest usb drivers: http://www.motorola....motodev_lp.html
STEPS
1. Power up your phone completely.
2. extract the folder in the android.zip file to your local disk. just drag the folder to local C: or whatever your main HD is
3. hold left shift and right click on the folder and click on pen command window here"
4. plug in your phone if you havnt done so already
5. in the command window type: adb devices ( this makes sure your phone is connected and it'll show its serial number under List of devices attached.
6. once it shows the serial number type in these commands ( these are in order)
adb reboot bootloader
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
fastboot erase userdata
fastboot erase cache
fastboot reboot
and walla phone will reboot like when you first got it ^^
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Your links are broken.
This seems cool. But I don't know what menu you are talking about, perhaps more clarity, as I'd like to know what causes this menu to be shown and if I am just missing it somehow. Curious to know if this fix may aid me in the future. As probably are some other users.
Also probably helpful for you to note that fastbooylt erase userdata will clear user settings.
Sent from my XT907 using xda app-developers app
Thank you...
Your steps got me out of the sticky mess...
I had to reinstall Win 10 on my computer and now I'm not able to connect to my 6T in order to root it.
The boot locker is unlocked, I can see it at phone boot. It was unlocked also before last update to OxygenOS 10.3.7.
Debug USB in enabled. When I connect to the phone to the computer it is deceted and I can transfer files.
Whit ADB devices phone is deteted (picture is from all in one tool, using command prompt same result)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
using fastboot devices the phone is not detected.
installed last official usb drivers (google and oneplus)
Any idea, suggestion or further test that can help?
Thanks
Same problem here. Please help.
Finally I found a working solution.
If you have a laptop you have to disable secure boot.
Then you have to disable signature verification on windows 10 ( How to Enable or Disable Driver Signature Enforcement in Windows 10 | Tutorials (tenforums.com) ).
I used option 3.
Download Oneplus usb drivers ( Download Latest OnePlus USB Drivers for Windows and Mac (getdroidtips.com) ).
Then connect your phone in fastboot mode & open Device Manager on Windows & look for Other > Android device. If it is found, this means windows 10 is not having proper drivers to recognize fastboot device. Now install "OnePlus_USB_Drivers_Setup.exe" & it will show pop up for installing driver & after accepting(this is blocked due to signature verification in normal situation), Android device will be recognized in fastboot mode.
Thanks man, it worked for me.
Just to complete, after istalling the drivers you can restore signature verification and secure boot on Win 10.
Everything will work fine.
Hello wonderful people, here is my drama:
yesterday I updated my Xiaomi Mi A1 (tissot) with Android ONE to V10.0.24.0.PDHMIXM from the Android system menu. Android downloaded the update, rebooted, installed it and since then I can no longer access my phone, it is stuck at boot time showing the message:
Can't load Android System. Your data may be corrupt.
- Try again
- Factory data reset
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I no longer care about this phone, but only about all the data that I have inside, photos since more than 2 years (I know I am super stupid for not making backups, I am feeling like trash right now), so factory reset is not an option because will destroy and re-encrypt the /data partition which is what I want to mount in the PC.
What I tried:
- I accessed Android Recovery and launched "Apply update from SD card" for installing again the same version miui_TISSOT_V10.0.24.0.PDHMIXM_bcbbe1fad4_9.0.zip but after launching the install it shows the message: E:Error in /sideload/package.zip (Status 1). Installation aborted. and does not solve anything.
The current status of my phone:
- I can not boot into Android, but I can access the Android Recovery and fastboot screens
- I am a normal user, so I never activated hacker options, so I have:
-> Default bootloader that came with the phone
-> No root access
-> No USB debugging option activated
-> No Developer options activated
I have read a lot of tutorials on the Internet and posts in this forum about recovery with tools like adb and fastboot, but all seem to need one or many of the hacker options activated in order to work.
Is there guys anything that I can do for activating the hacker options and then trying something else to mount /data in my PC or boot Android?
Thanks so so much in advance.
If my upgrade fails, how do I boot from the slot that I installed the crap on the inactive slot from so the phone boots to the old version before the update?
I wanted to know and found the answers. I'll post here in case anyone wants to know cause I found nothing on these forums:
How to Check if Partition Slot A or Slot B is Currently Active?via https://krispitech.com/check-partition-slot-a-b/
Make sure the smartphone is connected to the PC with a USB cable
Now boot the smartphone into Fastboot Mode
This process will vary from device to device but usually involves holding certain button(s) down during the boot cycle.
Open up a Command Prompt, Windows PowerShell, or a Terminal in the same folder as your ADB and Fastboot files
Type out the following command. . .
fastboot getvar all
. . .then press Enter on the keyboard
Wait for a lot of text to finish scrolling and look for the (bootloader) current-slot text
This should actually be toward the bottom without the need to scroll up.
The letter after this text will be the currently active partition slot for your device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In this instance, my device was currently using partition slot B.
How to Boot from One Active Partition Slot to Anothervia https://krispitech.com/change-active-partition-slot/
Boot the smartphone or tablet into Fastboot Mode
Connect the device to the PC with a USB cable
Open a Command Prompt, PowerShell, or Terminal and type out the following command. . .
fastboot --set-active=a
OR
fastboot --set-active=b and then press Enter on the keyboard
Make sure you get a successful OKAY response before restarting the device
So if my updates go pear-shaped, I should be okay. And if not, well, I'm not buying a OnePlus ever again cause I've had it with all the extra steps, headaches, and disappointments with this model.
Excellent guide, I like it.
Think check out TWRP too, I think ( not 100% ) but I think it can change slots for you too.
Hi everyone,
(Sorry if my english is bad) I recently saw Crosscall device must have a key to unlock their bootloader with fastboot (common way), and most of Crosscall devices are SnapDragon except the S4 Core, because there's an universal way for MTK to unlock the bootloader, without waiting time and key needed.
Requirements :
PC or Laptop (at least running Windows 10)
Crosscall Core S4
USB cable
/!\IMPORTANT/!\ : THIS PROCESS WILL WIPE ALL YOUR DATA, SO IF YOU HAVE IMPORTANT FILES BACKUP THEM BEFORE DOING THIS
Ready ? Go !
First : Install USBDK (depends on your processor arch download x64 for 64 bits and x86 for 32 bits)
Download MTKClient extract it and copy the extracted folder on your C: drive folder
Ok now open a Powershell session (if you're on W11) or a cmd session (if you're on W10)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now type pip3 install -r requirements.txt and hit enter
Now type python mtk e metadata,userdata,md_udc hit enter - This command wipes data
Then power off your phone and hold both volume buttons and connect usb cable (DON'T LEAVE THE BUTTONS, KEEP THEM HOLDING THROUGHOUT THE PROCESS) - This boots device into BROM mode
Now type python mtk da seccfg unlock This will unlock the bootloader (If you face waiting for device issue then unplug the device and plug in the device again with holding volume buttons, also don't leave the buttons)
After this unplug your phone and turn it on (It'll show your device dm verity corrupted and first boot might take 20-25 mins, don't panic)
Now your bootloader is unlocked