Hi Guys,
Figured I will ask the experts here. My mate dropped his S5 Mini a few days ago, since then the touch screen does not work so he can't put in a pattern to unlock the phone. New screen prices in South Africa is ridiculous, especially for a 3 year old phone. I want to help him get his photo's off the phone but the we can't do the pattern unlock and S5 mini does not support OTG cables, so we can't use a PC mouse etc. Also can't enable USB debugging obviously.
I'm thinking of trying via the Recovery loader or whatever you all it. The stock recovery does not seem to allow mounting of the various partitions via ADB from what I have read, so will I need to flash a custom Recovery like TWRP 3.0.0? Also see you need to have an unlocked bootloader in order to flash a custom recovery. I presume rooting the device with CF-Auto-Root will unlock the boot loader? I can then load the custom recovery after doing the root?
Rough process would be.
1. Boot Download mode -> Flash CF-auto-root -> Reboot | From what I have read this is safe and does not trash any data as its a separate partition?
2. Boot Download mode -> Flash custom recovery -> Reboot | From what I have read this is safe and does not trash any data as its a separate partition?
3. Boot Recovery Mode
Any help would be appreciated as I really dont want to trash his data.
Cheers
Jacques
Related
I was poking around in recovery mode and wanted to see what bootloader looked like.
My phone won't allow me into bootloader mode and it ust boots right up. Is this normal? I am rooted.
I can get into Recovery mode fine (by using Quickboot Android App) and if I select bootloader (from Quickboot or Recovery) it just boots right up.
If you look at the announcement from LG on the 815 model about the unlocked bootloader then direct the user to get into bootloader mode.
Someone asked if this bootloader unlock will be released to US models and the reply was that they are not technically setup to be unloackable due to some technical issue.
I wonder if the fact that I can't get into bootloader mode is the reason it will never be possible to unlock? Even if they did decide to allow it.
same here via adb on a new 815H ! *_*
The only way to get into bootloader, is to first backup and then nuke (zero out) your LAF partition. This will force the phone into bootloader mode. I have tested our bootloader on Lollipop and found nothing useful and limited commands. You have to use the bootloader mode to put back your LAF partition when you are done.
/.
Hi Guys,
Figured I will ask the experts here. My mate dropped his S5 Mini a few days ago, since then the touch screen does not work so he can't put in a pattern to unlock the phone. New screen prices in South Africa is ridiculous, especially for a 3 year old phone. I want to help him get his photo's off the phone but the we can't do the pattern unlock and S5 mini does not support OTG cables, so we can't use a PC mouse etc. Also can't enable USB debugging obviously.
I'm thinking of trying via the Recovery loader or whatever you all it. The stock recovery does not seem to allow mounting of the various partitions via ADB from what I have read, so will I need to flash a custom Recovery like TWRP 3.0.0? Also see you need to have an unlocked bootloader in order to flash a custom recovery. I presume rooting the device with CF-Auto-Root will unlock the boot loader? I can then load the custom recovery after doing the root?
Rough process would be.
1. Boot Download mode -> Flash CF-auto-root -> Reboot | From what I have read this is safe and does not trash any data as its a separate partition?
2. Boot Download mode -> Flash custom recovery -> Reboot | From what I have read this is safe and does not trash any data as its a separate partition?
3. Boot Recovery Mode
Any help would be appreciated as I really dont want to trash his data.
Cheers
Jacques
A locked bootloader will prevent cf-auto-root from even flashing.
The rest is correct.
gsmDabbler said:
A locked bootloader will prevent cf-auto-root from even flashing.
The rest is correct.
Click to expand...
Click to collapse
Thanks!
Hi,
I have the same problem (phone is pin-looked instead of pattern) and i would love to use your solution.
Could someone give me a little bit more information to the mentioned steps?
Hello, after unsuccessful OTA update my phone doesnt boot into Android any more.
I had an original, untouched xiaomi system (not a custom one, not rooted etc).
Bootloader locked like default.
I think update.zip could be faulty - I have no idea how.
I am able to run Fastboot but due locked BL I cannot do much there.
I deasemble phone, pull out the battery, connected EDL pinouts with a wire, and all this togetcher connecter to PC.
Phone is visible by PC.
Downloaded ROM, and tried to flash via MI Flash..
On last moment I am getting error with information that my mi.com account is not athourised to do such a thing.
I tried also Mi Flash Pro founded on Cyanogenmod forum, but without luck - still getting same error.
Does anyone know how to get out from this situation or should I rather open warranty process in Gearbest?
sabbath88 said:
Hello, after unsuccessful OTA update my phone doesnt boot into Android any more.
I had an original, untouched xiaomi system (not a custom one, not rooted etc).
Bootloader locked like default.
I think update.zip could be faulty - I have no idea how.
I am able to run Fastboot but due locked BL I cannot do much there.
I deasemble phone, pull out the battery, connected EDL pinouts with a wire, and all this togetcher connecter to PC.
Phone is visible by PC.
Downloaded ROM, and tried to flash via MI Flash..
On last moment I am getting error with information that my mi.com account is not athourised to do such a thing.
I tried also Mi Flash Pro founded on Cyanogenmod forum, but without luck - still getting same error.
Does anyone know how to get out from this situation or should I rather open warranty process in Gearbest?
Click to expand...
Click to collapse
Just flash a custom recovery, the device even had the offical twrp. So?? Just not into fastboot and then flash the recovery by the -- command
fastboot flash recovery recovery.img
(You have to rename the twrp file to recovery or whatever, just write the image file name instead of recovery in the second one. Ex fastboot flash recovery 123.img)
Then command
Fastboot reboot
(Hold the power up button for booting into twrp before hitting enter)
Download a miui recovery rom for your device from anywhere, I don't know I'm lazy.
And before flashing, go into mount select vendor and system if not selected.
And then select wipe
Advanced wipe
Select vendor system data cache.
Swipe to clean
Move the rom to your device
(If your device does not show up in your pc, then go into mount (twrp) select enable MTP if it's disabled, if it shows disabled then enable it again)
After that just flash your rom and then a permissive patch you can ask anyone. Or just flash pitchblack recovery. Fixed my problem of not not booting.
Sorry for the wrong format, wrote it on mobile, as I am a lazy bum.
Wut bruh.
Something similar happened to my friend's Poco F1. It was locked and I only could boot into fastbook, looked everywhere for a solution and found this lifesaving tool . It may work for Redmi 8 too.
ChakibDEV said:
Something similar happened to my friend's Poco F1. It was locked and I only could boot into fastbook, looked everywhere for a solution and found this lifesaving tool . It may work for Redmi 8 too.
Click to expand...
Click to collapse
thanks so much, that helped
Hi everyone,
I have retrieved a Samsung Tab 3.7.0 SM-T210. The OS was the old KitKat 4.4.2, very slow and buggy. I tried to flash a new recovery and OS and spent the 3 last days getting fails. I think I have read the all internet about this situation and would like to make a last try with your help.
When I got the tablet, I was surprised that in download mode it was indicated custom and custom binary and not official as it has not, I think, been flashed in the past by the people owning it. With HW rev 0x5 at the end.
The first thing I wanted to do was to unlock the bootloader, however, I could not find any option in developer mode talking about OEM bootloader, neither Auto Update. After reading some people on forumes saying that this device might not have a locked bootloader, I finally thought that this tablet did not have its bootloader locked. Then I decided to go further with the flash of a TWRP recovery.
At the beginning the stock recovery was working. I am under archlinux, I have fastboot and heimdall. To do it as right as possible I installed a VM with Windows 10 and tried to flash a custom TWRP corresponding to the tablet with Odin. But the process got stuck at the SetupConnection step. I installed Windows 7 too, tried 5 different Windows OS, tried 4 different USB cables, reinstalled the USB drivers, tried 5 different Odin versions, tried different archives, just recoveries and all stock system. Still getting stuck at the SetupConnection.
I finally decided to try heimdall thinking that the VM could be the problem. With heimdall I run flash commands such as heimdall flash --RECOVERY twrp-3.2.3-0-lt02ltespr.img --no-reboot and got it doing something, the shell was saying it's 100% done and the tablet, in download mode, was showing a complete blue bar. Then, the recovery was just broken. Could not access it anymore, the Samsung Tab3 logo showing up and staying when trying to access it. I tried to flash some others archives, I opened it off and remove the battery for 5 minutes, still the same thing.
The operating system was still accessible and buggy, applications saying connection issues, etc. I did a factory reset from the running KitKat android OS and now have the Samsung Tab3 logo showing up and staying when trying to access it.
Now, I can only access the download mode and that's all. I have the impression that I am not the first one having these kind of trouble with this tablet. Is it a hardware issue on all these tablets ? Should I try something more advanced with heimdall, dd ?
Does someone have a solution in this situation ?
Thanks for your time and help.
I finally used heimdall and was able to flash all the partitions with the stock images. Now I am back in stock version. I would like to flash a TWRP recovery.
Can someone tell me if I have to unlock the bootloader with this device ? If it is, how can unlock it ? I can not find anything in the settings developer section, and can not use a call number input in order to enter a system code as it's a tablet. Do I have to wipe something from the stock recovery in order to see it ?
Thanks for your time.
Hi -yo-.
You don't need to do OEM unlock as this device is so old.
Also twrp-3.2.3-0-lt02ltespr.img is NOT for this device.
For recovery look from here and for ROM here.
Thanks jonezy82 for the answer. Indeed, I figured all of that out.
I decided to get it back stock and not trying to flash anything custom.
Thanks for your time.
Hello,
I am not going to lie to you and tell you my goal.
My father committed suicide and the police "succeeded" in taking my father's data but he refuses to tell us its content, not even to my mother. I am of age and therefore "old enough" to understand the risks etc.. But I would like to have answers and be able to access the memory of my father's phone or bypass the android code.
I have started to learn how an Android works (ADB, ROM, Nethunter with HID for brute force) I am motivated by my approach but I don't have enough knowledge to reach my goal and I need you. Could you help me?
It is a samsung Galaxy A71 without active ADB.
Thanks !
Im sorry to that you can install twrp and acces the devices memory. After you install twrp enter twrp mode press mount and mount data and cache after that connect the phone to your pc and you should see the phones internal storage if this dosent work you can use twrp adb and use adb on your pc and pull all the phone contents using "adb pull storage/emulated/0" please be carefull if you dont install twrp properly you could lose all the phones contents. If i helped you make sure to leave a like
Thank you for your answer! it makes me believe a little more in the chances of success. I will try to install twrp on a samsung A40 which is currently used as a test. But I can't do it. Do you have any links or tutorials to help me understand how it works or how to install twrp without ADB or oem unlock ?
Many thanks
mypomme said:
Thank you for your answer! it makes me believe a little more in the chances of success. I will try to install twrp on a samsung A40 which is currently used as a test. But I can't do it. Do you have any links or tutorials to help me understand how it works or how to install twrp without ADB or oem unlock ?
Many thanks
Click to expand...
Click to collapse
You can't install twrp with adb the only way is using odin here is a video that should help you understand better
and here is the link for twrp for a40 https://twrp.me/samsung/samsunggalaxya40.html
Sloobot said:
You can't install twrp with adb the only way is using odin here is a video that should help you understand better
and here is the link for twrp for a40 https://twrp.me/samsung/samsunggalaxya40.html
Click to expand...
Click to collapse
Thanks,
I intentionally left the oem block on and did not activate the develloper mode to put myself in the same situation as my father's phone. And ODIN tells me FAIL.
So I think that if we have no access to the phone with the code to access the developer options we can not do anything.
mypomme said:
Thanks,
I intentionally left the oem block on and did not activate the develloper mode to put myself in the same situation as my father's phone. And ODIN tells me FAIL.
So I think that if we have no access to the phone with the code to access the developer options we can not do anything.
Click to expand...
Click to collapse
Did you flash the vbmeta disabler before hand? https://forum.xda-developers.com/t/recovery-official-twrp-for-galaxy-a40-a405fn.4025587/
This is my problem I don't know how to do with Odin :/
Sloobot said:
Did you flash the vbmeta disabler before hand? https://forum.xda-developers.com/t/recovery-official-twrp-for-galaxy-a40-a405fn.4025587/
Click to expand...
Click to collapse
mypomme said:
This is my problem I don't know how to do with Odin :/
Click to expand...
Click to collapse
Try this
If you are starting from scratch:
Go to Developer Settings and enable "OEM Unlock" option
Power off the device and boot in download mode
In download mode, you will see the long press and volume up option to unlock the bootloader
Unlock the bootloader. That will wipe your device so be sure you made a backup of your data
After bootloader unlock, boot up the phone and make sure it is connected to the internet or it will trigger rmm prenormal
Setup the phone without google account and others
Reboot in download mode and flash the recovery and vbmeta images
Boot to TWRP
Format data in TWRP
Flash the Multidisabler zip
Now you can reboot
Try this without oem unlock and formating data in twrp