Database Info

Twrp screen unresponsive of touch,power button,bolume buttons.

Hi guys greetings,(Hope everyone's doing good!)
I'm new here and on android, recently switched from ios,so bought a honor 3c international model and now I have emui 3.O on it and lurker 4.4.2.
And im really surprised by the android features and I like em and have decided to stick with android.
Root is one of its coolest features so I after some months using my phone decided to root and I was completely unaware of these terms like custom recovery, brick, boot loader,e.t.c.
After understanding the concepts I came to conclusion that I have to unlock boot loader first, then a custom recovery like twrp or cmw then that and that, so I followed the following link exactly like it is:
(Insert www)carbontesla.(insert com pls)/2014/08/guide-unlock-honor-3c-h30-u10-bootloader-using-sp-flash-tool/[/url]
After unlocking the boot loader I was "following" the procedure from link:
(Insert www pls)carbontesla.(insert com)/2015/06/root-honor-3c-on-emotion-ui-3-0-b320-firmware/[/url]
Code:
real problem now
After step 8 from the above link my phone does boots into the twrp recovery screen but becomes totally unresponsive of any touch or even the power, volume buttons. But it's screen turns off after 30 seconds(i think its that auto turn off screen to save power feature)when screen turns off by itself due to being idle THE POWER BUTTON WORKS bur after I once press power button the twrp recovery screen appears again and then again no touch, no power, volume button. I was so scared dafaq I have done to my phone so an idea flashed through my mind,i removed battery and connected phone to pc then i opened mkt_tools and installed super SU from there,then rebooted the phone(from mkt tools)and surprisingly my phone came back to its normal state,I swiped and found super su app,root manager opened su app and it said "not properly rooted"(of course I didn't expected it to be rooted because I wasn't able to go after step#8) and closes itself then another idea flashed through my mind so I went play store and updated super su and then opened it but it said no binary found and super su cannot install binary please root again properly...
I just want my twrp screen responding to touch or at least power/volume buttons because I have to reboot the device from the pc everytime(only if I take it to recovery)
After by help of you guys if I finally be able to get twrp screen then I can finally root the device by following the rest steps.
And my device isnot bricked I can use my phone still normal.
Another question I wanted to ask if I can replace twrp recovery with cmw recovery.
And can I remove this improper root somehow and start the whole root process again since I screwed with the mkt_tools
And the another damn mistake I made was to not made a complete backup.
I humbly request you guys to please help me, any help would be GREATLY appreciated,
Thank you very much,
Stay blessed,

bump

Galaxy amp 2 rootable?

Have done a little research trying to find any thing about an easy rooting for this device but no hits. I do know of some apps that can give root access haven't tried them but don't exactly trust them to much as have had them soft brick a few devices.
But any way here is device specs.
Carrier: cricket wireless
Phone name: Samsung Galaxy amp 2
Model number: Samsung-sm-j120az
Android version: 6.0.1
Baseband: J120AZTUU1APC4
if need any other info on it can supply it

I'm looking for the same thing. No roms no nothing.

@jasperjax Don't worry about it, there's not such thing as a flawless security system.
Universal rooting methods:
Warnings:
You are modifying your own phone on your own risk.
There is a slight chance that your phone may brick,
and if it does I will not be held responsible for whatever you do to your phone.
If you have a warranty, after rooting it will no longer be valid.
If your phone has a flash counter, some methods may trip it
resulting in a void warranty or a bricked phone (or both).
If your phone has KNOX, it may be tripped by some methods,
resulting in, once again, a void warranty.
If your phone is encrypted, the data partition
may be wiped for some methods.
There are more warnings specific to certain devices. Do your own research on your particular device model.
Click to expand...
Click to collapse
Computerless methods:
1. Framaroot
2. Towelroot
3. Kingroot for Android
4. Kingoroot for Android (Not recommended, but often works)
5. iRoot for Android
6. z4root
Methods requiring a computer:
1. iRoot
2. Root Master
3. Kingroot
3. Kingoroot (Not recommended)
4. CF-Auto-Root
Root Checker - Check if your device is correctly rooted
SuperSU - the recommended superuser application
ADB and fastboot drivers:
ADB and fastboot are (extremely simplified) a way for your computer to talk to your phone. And installing them may be a bit of a problem for some users.
To install it on windows there is a handy tool called the 15 Second ADB installer which will install pretty much everything you need.
On Ubuntu install with:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
On Fedora:
Code:
sudo dnf install android-tools
On OS X using Homebrew:
Code:
brew install android-platform-tools
Recovery:
A custom recovery is an important part of device unlocking. It's the best and the most convenient way to fix your device if something goes wrong.
Root is required (in most cases) for installing the recovery.
The two most popular recoveries are:
1. Clockworkmod recovery (CWM) - CWM is a very stable recovery with many useful features. You can use the link here to download and install the official version via the ROM Manager app.
2. Team Win Recovery Project (TWRP) - TWRP is a stable recovery with a very nice UI and many features such as the terminal, partition management, file browser and so on. I personally use TWRP because of it's functionality, but if you're starting out CWM would be a better choice because of it's stability and compatibility. Also TWRP is a tiny bit more difficult to install as there is no one click installer.
If your device is not officially supported you can get an unofficial version, however there is no grantee the unofficial version will work, it might even forever break your device. In most cases it does work, just look at what other people who tested it say.
To find unofficial recoveries Google:
[your phone model] cwm recovery
or
[your phone model] twrp recovery
After installing the recovery the first thing you should do it do a nandroid backup.
If you have any questions first try to Google the answer, but if you can't find it feel free to ask me here with a post (not a PM).
Also remember to quote me or tag me with @janekmuric if you want me to respond.

most of those do not work for 6.0 correct? Amp2 comes with 6.0 stock

Has anyone heard anything more about rooting the Cricket Galaxy amp 2?
Just bought it yesterday for a friend and would love to root and possibly unlock it?

i have tried all the computer less ways of trying for root. none have worked. haven't done much with the ones requiring computer to root But does not mean i wont try them at some point. right now this is mostly a Backup phone Just in case i kill my Galaxy s4 (running goldeneye lollipop 5.0.1 rom) other then that have not seen anything New pop up around the net about it still on my todo list tho

2nd update to this. have tryed iroot root master and kingroot pc version best i get is blacked out screen with phone not responding to anything. Almost like a hard brick. pull battery hold power for a few put battery back in then kicks on just fine like nothing happened. but saddly no root havnt tried CF-Autoroot as to well phone not being listed. much less figuring out how to unlock bootloader. (If its even Able to be unlocked)
Tho i have noticed something in dev options. a switch to allow for OEM Unlocking. yet booting into recovery and doing the good old "fastboot oem unlock" just gives me the waiting for device that sits there for the next hour. any takes on this @janekmuric ?

jasperjax said:
2nd update to this. have tryed iroot root master and kingroot pc version best i get is blacked out screen with phone not responding to anything. Almost like a hard brick. pull battery hold power for a few put battery back in then kicks on just fine like nothing happened. but saddly no root havnt tried CF-Autoroot as to well phone not being listed. much less figuring out how to unlock bootloader. (If its even Able to be unlocked)
Tho i have noticed something in dev options. a switch to allow for OEM Unlocking. yet booting into recovery and doing the good old "fastboot oem unlock" just gives me the waiting for device that sits there for the next hour. any takes on this @janekmuric ?
Click to expand...
Click to collapse
Sorry for not posting for 20 days. I've been of xda for a while. Anyways the reason why it's stuck there is because you are trying to run fastboot commands in recovery. You are supposed to run them in fastboot mode.
Just Google "[phone name] how to enter fastboot mode" or try pressing random buttons to boot the phone into fastboot. From there you should be able to run "fastboot oem unlock" (This will erase ALL data).
If it still doesn't work even if you are in fastboot mode then you have incorrectly installed fastboot drivers on your PC. Google is your best friend here.

janekmuric said:
Sorry for not posting for 20 days. I've been of xda for a while. Anyways the reason why it's stuck there is because you are trying to run fastboot commands in recovery. You are supposed to run them in fastboot mode.
Just Google "[phone name] how to enter fastboot mode" or try pressing random buttons to boot the phone into fastboot. From there you should be able to run "fastboot oem unlock" (This will erase ALL data).
If it still doesn't work even if you are in fastboot mode then you have incorrectly installed fastboot drivers on your PC. Google is your best friend here.
Click to expand...
Click to collapse
your fine this has been a slow moving project for me anyway. and yes i know about running fastboot in fastboot mode BUT heres my issue. i have download mode or recovery. thats about it. attempted this in download mode also for giggles and got same thing expected that honestly but worth a shot. from adb have tryed "adb reboot fastboot , adb reboot bootloader" and a few others just to get close to anything that would give me a different screen. as for key combo's nothing has worked. tryed with normal shutoff and turn on and with taking battery out holding power then popping battery back in with no luck. as for googling how to get into fastboot just some info that covers "Most" devices still not a whole lot about this device on how to root it much less anything more. heck half my searching brings up this forum thread as the top item. so this really has me stumped.

jasperjax said:
your fine this has been a slow moving project for me anyway. and yes i know about running fastboot in fastboot mode BUT heres my issue. i have download mode or recovery. thats about it. attempted this in download mode also for giggles and got same thing expected that honestly but worth a shot. from adb have tryed "adb reboot fastboot , adb reboot bootloader" and a few others just to get close to anything that would give me a different screen. as for key combo's nothing has worked. tryed with normal shutoff and turn on and with taking battery out holding power then popping battery back in with no luck. as for googling how to get into fastboot just some info that covers "Most" devices still not a whole lot about this device on how to root it much less anything more. heck half my searching brings up this forum thread as the top item. so this really has me stumped.
Click to expand...
Click to collapse
If your device doesn't have fastboot mode there is no point in trying to do anything with it. Anyways try downloading Poot and rooting with that. It's just an app that you install on your phone. I've tried it on my phones, it never worked, but a lot of people on the internet are saying it worked for them so you should try it.

janekmuric said:
If your device doesn't have fastboot mode there is no point in trying to do anything with it. Anyways try downloading Poot and rooting with that. It's just an app that you install on your phone. I've tried it on my phones, it never worked, but a lot of people on the internet are saying it worked for them so you should try it.
Click to expand...
Click to collapse
yeah poot has never worked for me on any device so far. always get (Ministro can not satisfy your application depedencies) error. just as this time around. but as i have located an "updated" rom for this device (and as i forgot to turn off device last night it took on the update on its own anyway Yay me) i may just try doing some light flashing. with odin at the ready just to be safe.

Anyone figure this out? I have a cricket samsung galaxy amp 2 (SM-J120AZ). I've tried every way possible to root it with no luck. I've tried all the methods above and none of them work for the amp 2.

@imagetrekker Not yet. another device very close to this one is the SM-J120A (Samsung Galaxy Express 3) everything matchs up besides the android version is comes with.(6.0) would think if they root that one this one would be able to be rooted same way or if this one gets rooted first should work on other.

Anyone figure out how to root this phone yet? I have never had a device that can't be rooted one way or another but this one is being really tricky...

I'd like to bump this too! I've tried many methods with no success. Any other options to try?

Bump

Where did you find that SM-J120AZ ROM ?
jasperjax said:
yeah poot has never worked for me on any device so far. always get (Ministro can not satisfy your application depedencies) error. just as this time around. but as i have located an "updated" rom for this device (and as i forgot to turn off device last night it took on the update on its own anyway Yay me) i may just try doing some light flashing. with odin at the ready just to be safe.
Click to expand...
Click to collapse
Hey man, this is very very important. You said you located an updated ROM for the Samsung Galaxy Amp 2 (SM-J120AZ Cricket). I've been searching high and low, so if you could direct me to where you found it, I would so very much appreciate it.

Can't format SD card for internal use
So I guess Samsung have saw fit to disable the ability to format an SD card for internal storage, which means you can't move any apps to the SD card. With the limited memory on this Galaxy Amp2 this makes it near useless!
We need to get root on this so maybe we can fix this...
adb shell sm set-force-adoptable true
Should fix it, but only with root...

sorry had some computer issues shortly after a thunderstorm but im back up and running so Sorry for the very late replys
MuzicSoulWorldly said:
Hey man, this is very very important. You said you located an updated ROM for the Samsung Galaxy Amp 2 (SM-J120AZ Cricket). I've been searching high and low, so if you could direct me to where you found it, I would so very much appreciate it.
Click to expand...
Click to collapse
@MuzicSoulWorldly was actualy able to get it from http://updato.com/firmware-archive-select-model?r=&v=&q=j120az&exact=1
Greywire said:
So I guess Samsung have saw fit to disable the ability to format an SD card for internal storage, which means you can't move any apps to the SD card. With the limited memory on this Galaxy Amp2 this makes it near useless!
We need to get root on this so maybe we can fix this...
adb shell sm set-force-adoptable true
Should fix it, but only with root...
Click to expand...
Click to collapse
@Greywire Not quite you can do it with out root. commands are as this
Code:
adb shell
sm list-disks
sm partition <DISK> private
reboot
<DISK> needs to be replaced with the output of the previous command. For example sm partition disk:179,64 private. That will format the entire SD card and adopt it. Another way would be to use sm partition <DISK> mixed <VALUE> replace <DISK> same as with other way but value would be in a % of disk you want adopted example "sm partition disk:179,64 mixed 50" would make adopt half your sd card.

thanks..
I actually discovered this right after I posted. Hopefully anybody else having this issue will see your posting though for the solution.
Still would be nice to get root on this phone. Any ideas on how to carrier unlock it?

HomTom HT50 root problem, unavilable fastboot...

Heloo,
I have this device and I have trying to root it for a whole month .....
It is HomTom HT50
3gb RAM
mt 6737
Android 7.0
First I tried to flash TWRP recovery and custom ROM with sp flash tool and I bricked phone. Totally it was dead. Not even charging led notification. Not any sign .But I gave it to service (under waranty ) and they fix it.
Very well but I lost all photos that are impotant to me. In order to bring photos back I must have rooted phone.
I tried everything. Root aplication -every one failed. It has locked bootloader.
I try to unlock with ADB console with no success. After command line "adb devices " it recognize phone.
But after command " adb reboot bootloader" phone goes to resatart and than it do not go to fastboot mode but shut off.
In every other way I have tried to go to fast boot i failed. Wired but I can not go to bootloader mode(combination of buttons)
It can go into stock recovery. Strange first show green android on back with red triangle and text no command and after several times of pressing power+volume up some how it enter recovery.
Please any help. There must be some way to root this stuff.

Hello, this kind of devices are very easy to root them but first of all it seems that your system partition is now very unstable so in order to restore its functionality you need to flash the stock rom.
Download stock rom and flash it using SPFlash tool v5.1748 would be fine and next I will give a try to guide you how to root it.

Any progress (10/August/2018)
I am wondering if there is a simple tutorial giving instruction on rooting the HomTom HT50 phone?
Thanks . . .

I would like to see that too. I have ht50 and I am very afraid to just flash twrp of other loaders that are similar to this phone and "should" work.
In the old days the chinese (tablets ) usually came rooted by default. Now I cannot root. which makes the phone rather useless to me. So any help would be appriciated.

Hans de Groot said:
I would like to see that too. I have ht50 and I am very afraid to just flash twrp of other loaders that are similar to this phone and "should" work.
Click to expand...
Click to collapse
FYI I did manage to both root & install TWRP onto the HT50. Unfortunately I did not document what I was doing. I'll try to remember & post back here.
I subsequently installed a Homtom (updated) stock ROM which overwrote what I had achieved.
I'll try to discover some time soon to try to dredge-up the fragmented memories of what I did.

I have my two phones and I have problems with the ignition, the way it turned on, let it be desired because they were in operation and at a certain moment when I turn them on for charging they turn off and only the red light turns on, I don't know how to repair it, there is a possibility repair and how to please

Root newbie

Hello,
Please help me. My samsung a8 updated to android 9 and the call recording is disabled. I need to root the phone, but help me please in the following questions:
1. Do i need custom rom?
2. Do i need custom kernel?
3. Will the android self update as now?
So what is the most importnt steps just to root the device?
In my whole life i paid for one software (callrecorder) which is not working now.

Unfortuently there is no clear tutorial to root this phone but you car read here: [GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018

Snypie said:
Hello,
Please help me. My samsung a8 updated to android 9 and the call recording is disabled. I need to root the phone, but help me please in the following questions:
1. Do i need custom rom?
2. Do i need custom kernel?
3. Will the android self update as now?
So what is the most importnt steps just to root the device?
In my whole life i paid for one software (callrecorder) which is not working now.
Click to expand...
Click to collapse
1. Do i need custom rom?
no
2. Do i need custom kernel?
no
3. Will the android self update as now?
if you flashed TWRP, no

1. Do i need custom rom? No
2. Do i need custom kernel? No
3. Will the android self update as now? depend on your settings
1-to root it the first thing is to have OEM Unlock available and enabled in Dev Options
if not keep the device fully on and with data on dont restart, power off or reset for at least 7 days continuously (or a bit more) and you should have it
if it's not shown dot bother with the rest
2-to have Dev Menu available go to settings >> about phone >> software information >> on build number tape multiple times 10 times i guess, you will have a pop up confirmation
once back at settings menu you will find a new choice at the very bottom "Develper Options"
3-next step with to plug ur phone with PC with usb cable
after installing SAMSUNG DRIVERS & ODIN and downloading TWRP (custom recovery)
in ODIN 2nd tab, untick "AUTO REBOOT" VERY VERY IMPORTANT
chose the TWRP file using AP button/option in ODIN
put your phone in download MOD power off completely >> power back on while holding vol+ and vol- at the same time
flash the file using ODIN to your phone
4- now here is the tricky part
after fklashing TWRP if you reboot normaly you will be locked again and you wont have that OEM Unlock option i talked about and you will be stuck
so, after flashing TWRP, press vol- + power button to reboot the phone
AT THE VERY PRECISE MOMENT WHEN PHONE TURN OFF BEFORE POWERING BACK ON WHEN IT BLINK
RELEAS POWER BUTTON AND VOL+ and PRESS POWER BUTTON + VOL+ AGAIN VERY VERY QUICKLY
if successful you should boot into TWRP directly
5-once you are in TWRP wipe everything then format the device (ALL DATA WILL BE LOST)
of course you need to have the needed files already copied in the SD CARD
from twrp after the wipe and formatiing
go to install and flash in that order RMM_Bypass_v3_corsicanu or RMM-State_Bypass_Mesa_v2
then no-verity-opt-encrypt-6.0
then at the end flash Magisk-v19.3
once its done reboot the phone normally, you will have your phone working as normal
once you are in, install Magisk APK MagiskManager-v7.3.2
reboot again
and voilaaa, you should have root and everything shoul be functional for you
allthow of course I will not be responsible for any kind of software or hardware damage, and certainly not ressponsible for any data loss
as it is completely you responsibility
I would like to attach all the files mentioned above, to help better but dnt sems to find how
so you will have to download and gather them from previous posts

Thank you very much, but i have a question. You wrote this:
"4- now here is the tricky part
after fklashing TWRP if you reboot normaly you will be locked again and you wont have that OEM Unlock option i talked about and you will be stuck
so"
I this will happen what csn i do?
The most afraiding thing is to me about rooting if i get a brick.

Snypie said:
Thank you very much, but i have a question. You wrote this:
"4- now here is the tricky part
after fklashing TWRP if you reboot normaly you will be locked again and you wont have that OEM Unlock option i talked about and you will be stuck
so"
I this will happen what csn i do?
The most afraiding thing is to me about rooting if i get a brick.
Click to expand...
Click to collapse
its virtually impossible to brick samsung devices these days. Well, perma-brick that is. I have spent entire evenings after work bricking phones just so i could figure out what caused the brick and then fix it. the worst thing that would happen if the FRP lock gets enabled again is that youd have to go re-disable it.
i guess i didnt really explain that clearly after re-reading it. So, when he says "stuck" he means with TWRP installed and no method of rooting. The phone will boot normally in the situation described in point #4

Problem with installing a custom recovery (custom binary blocked by OEM lock)

I have bought a used Samsung S10e (SM-G970F/DS) it came with Android 12 and it was reseted.
My goal is to install iodeOS. Even if the iodeOS website says "Update the stock firmware to the latest" I considered the instructions from LineageOS and installed the latest Android 11 version, following this (https://iode.tech/en/iodeos-installation/#1629185391421-4cf1f5c8-d900) uninstall instructions.
After Android 11 was installed I enabled the developer options. OEM-Unlock was not available. Therefore I followed these instructions (https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/) and the OEM-Unlock was available again.
Now it seemed that everything is ready to install iodeOS or LineageOS. Therefore I followed this instructions (https://wiki.lineageos.org/devices/beyond0lte/install). It worked fine until "Installing a cutom recovery using heimdall"
after the "heimdall flash --RECOVERY <recovery_filename>.img --no-reboot" command the S10e shows a bar which is filled from the left to the right and then it shows "Custom Binary (RECOVERY) Blocked By OEM Lock"
Now I have no clue what to do :-(
I would be glad for any help.
​

You need to unlock the bootloader. You've toggled the OEM Unlocking switch, so unlocking the bootloader is the next step.
Make sure you have the Samsung USB drivers installed on your PC.
Turn off your device.
While holding the Bixby and Volume Down buttons, connect your phone to your PC.
The device should start in Download Mode. Hold down Volume Up until you get a warning about unlocking the bootloader. Unlocking the bootloader will wipe your data. Click Volume Up to confirm.
Your device will wipe data, then reboot. At this point, you can reboot to download mode and flash a custom recovery using Odin or Heimdall.

Thanks a lot for all your help!
The problem was I entered the download mode by the adb command "adb reboot-bootloader" and this mode seems to be different to the one which can be accessed by pressing the keys.
Now everything worked fine

I have exactly the same problem here:
SM-A205G with OEM Unlock enabled
There is no unlock bootloader in the bootloader no option anymore
at least in the bootloder of this edition
And I suppose that if it is the bootloader that flashes everything, it is COMPLETELLY LOCKED, could be jailbroken by some new method, but until them... no option :sad:
V0latyle said:
You need to unlock the bootloader. You've toggled the OEM Unlocking switch, so unlocking the bootloader is the next step.
Make sure you have the Samsung USB drivers installed on your PC.
Turn off your device.
While holding the Bixby and Volume Down buttons, connect your phone to your PC.
The device should start in Download Mode. Hold down Volume Up until you get a warning about unlocking the bootloader. Unlocking the bootloader will wipe your data. Click Volume Up to confirm.
Your device will wipe data, then reboot. At this point, you can reboot to download mode and flash a custom recovery using Odin or Heimdall.
Click to expand...
Click to collapse

It seems that this <confirm> option in the bootloader is being removed by samsung, so... even if unlock oem is enabled... it will not work...
I can only reach the bootloader by going to recovery mode them selecting reboot bootloader, or by adb reboot bootloader, but it boots directly in download mode without the option to long-press volume up key
A flasher that doesn't flashes doesn't makes sense. Maybe samsung have hidden something new in there?...

Ok. I've found the solution
1 - Power the phone off
2 - Hold both volume up and down
3 - PLUG THE USB BUTTON WHILE YOU HOLD BOTH these buttons
4 - NO NEED TO PRESS POWER BUTTON
I guess this will work for all phones that don't have the option to start with power+down
Yes. A flasher that does not flash don't exists.
Good luck ! \o/
source:
HELP!!! Custom Binary (BOOT) Blocked By OEM Lock
Hi there, I've been having trouble rooting my Samsung Galaxy A20 - SM-A205GN for awhile now. I'm officially on Android Version 10 with One UI Version 2.0, I've followed the provided guide to root my device but it fails on Odin "all versions" when...
forum.xda-developers.com

wavedevice said:
Ok. I've found the solution
1 - Power the phone off
2 - Hold both volume up and down
3 - PLUG THE USB BUTTON WHILE YOU HOLD BOTH these buttons
4 - NO NEED TO PRESS POWER BUTTON
I guess this will work for all phones that don't have the option to start with power+down
Yes. A flasher that does not flash don't exists.
Good luck ! \o/
source:
HELP!!! Custom Binary (BOOT) Blocked By OEM Lock
Hi there, I've been having trouble rooting my Samsung Galaxy A20 - SM-A205GN for awhile now. I'm officially on Android Version 10 with One UI Version 2.0, I've followed the provided guide to root my device but it fails on Odin "all versions" when...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes, you don't unlock the bootloader VIA the bootloader in Samsung phones.

so you know what happened? I accidentaly reset my phone! I have gone into download mode and there was additional choices: to unlock bootloader holt volup, so I did, then again to confirm unlocking press volup. I did so and then there was for a brief moment android logo and "erasing" and then after about 2 minutes of just Samsung logo phone restarted and asked me to perform setup as it was new! WTH? There was nothing mentioned about deletion

DaHansi said:
I have bought a used Samsung S10e (SM-G970F/DS) it came with Android 12 and it was reseted.
My goal is to install iodeOS. Even if the iodeOS website says "Update the stock firmware to the latest" I considered the instructions from LineageOS and installed the latest Android 11 version, following this (https://iode.tech/en/iodeos-installation/#1629185391421-4cf1f5c8-d900) uninstall instructions.
After Android 11 was installed I enabled the developer options. OEM-Unlock was not available. Therefore I followed these instructions (https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/) and the OEM-Unlock was available again.
Now it seemed that everything is ready to install iodeOS or LineageOS. Therefore I followed this instructions (https://wiki.lineageos.org/devices/beyond0lte/install). It worked fine until "Installing a cutom recovery using heimdall"
after the "heimdall flash --RECOVERY <recovery_filename>.img --no-reboot" command the S10e shows a bar which is filled from the left to the right and then it shows "Custom Binary (RECOVERY) Blocked By OEM Lock"
Now I have no clue what to do :-(
I would be glad for any help.
​
Click to expand...
Click to collapse
I had the same problem on my samsung tab a10.1. That's why I had to flash the stock firmware 3 times. Every time I flashed twrp with odin, I got the error (custom binary blocked by oem lock).
I write what they should do in order.
1. Turn on the phone.
2. Open Developer mode
3. USB debugging mode - on
4. oem unlocking - on
5. then turn off the phone and disconnect from usb
6. Connect the phone to the PC with USB by holding down the volume up and volume down buttons at the same time. WITHOUT PRESSING THE POWER BUTTON
7. Press and hold the volume up button according to the instructions in the pop-up window.
oem unlocked

Sorry that, I had another problem. May I know how to unlock the OEM if my S10e phone can't turn on.
My device always on "samsung" display page, can't open to index. Do you know this issue? Expecting your reply.

Hi! I have the same issue on my Xiaomi Mi 11 Pro (It was Chinese) but it came unlocked with xiaomi.eu rom.
After i installed a global rom, and google wallet nfc pay did not work, so i thought okay i will lock it then so maybe wallet would accept it, (with the eu rom it worked before) so i put the device in fastboot and used fastboot oem lock on cmd...
And from then it stucks on miui recovery 5.0 screen, and says, this miui version can't be installed on this device...
I might not enabled oem unlocking before i shut if off, but i added it to my mi account so i dont know if after a week i can maybe unlock it. But i think the other possible solution would be to sideload the original chinese stock rom, which is for M2102K1AC, Mi 11 pro, codename mars, but i couldn't find it anywhere... If someone can upload a link to it, that would be a huge help! Or any idea! thx!

geraldmany said:
HI! i got a mi 11 pro 1 year ago, and it was offically chinese, but it came unlocked with Xiaomi.eu firmware, but i could't update it via the updater app, so i searched and found the global star version and just flashed it, everything worked, only now google pay nfc didnt work, it said that its probably because of the unlocked bootloader, so i got to fastboot and in cmd i sent fastboot oem lock, and since then my phone is stuck in miui recovery 5.0 screen and says that i cannot run this firmware on the device, i tried to unlock it but failed, maybe after a week, but i think that i didnt turn on oem unlocking on the phone itself before this... So im just hoping that after a week unlocking could be done... Or my other idea is, that i could install the original chinese rom with sideload, because i managed to install another global version on it since, but the result is still the same, the only problem is that i cannot find literally anywhere a mars codenamed firmware...
Click to expand...
Click to collapse
Anyone who might have the same situation, i found a simple, but effective solution, not sure if it works on every xiaomi device, but i will write down the steps here:
You need to use XiaomiADB, here is the download link and the description for how to use it -> https://xiaomiui.net/how-to-use-xiaomiadb-8044/ (if the page is not available, then feel free to msg me!)
For xiaomi adb, you need to go to 3rd option on the miui recovery screen, NOT THE FASTBOOT
So basically i went through the steps to “xiaomiadb sideload_miui <filename>”
And I tried to install a rom, BUT IT DIDNT ACCEPT IT!
The message was:
ERROR: This rom cannot be installed, server code -> 2001, server message -> Can't install unofficial rom
after trying 4 times all the same and: Installation of this rom via stock recovery is not allowed by Xiaomi
Says Installation failed, and then i just decided to download another rom so i PLUGGED OUT THE PHONE right after this, and went to another room to connect to wired network, to download and try a different rom... when i came back, to all my surprise, the phone was turned on, so i went to the setting dev ops and enabled bootloader unlocking, linked it to my account enabled adb and everything that is needed to flash another rom later, so then i rebooted and again, miui recovery 5.0 screen, but now i enabled unlocking, so i put the phone in fastboot, and tried MI UNLOCKER TOOL again, now it says: Please unlock 168 hours later. And do not add your account in MIUI again, otherwise you will wait from scratch.
So that means, after 7 days i wll be able to unlock it, until then, i can turn it on with the above method, in short try to sideload (copy and install) a rom to it, and then after it failed, plug it out and just wait like 10-20 maybe 30 seconds and bam your device is normally booted... I hope it helps to some of you, (i have been searching for the solution for almost a week, my other option was to pay someone who can MAYBE do it or send the phone back to china and pay the repairs, so im really happy with this method! If it helps to you, please reply so i and the others will know that it worked! Have a nice day!