adb cli is working. USB debug and allow to override boodloader is enabled. But if i reboot the device with adb reboot bootloader
the device reboot into the bootloader and is waiting for download the image. But if i enter the command: fastboot flash recovery twrp-3.5.2_9-0-gts4lvwifi.img
nothing is happen.
And if i scan with adb for devices, no devices were found. So what i’am doing wrong?
Ok, found that i must using heimdall to flash samsungphones. So have done the same again, but get an error on handshake: heimdall print-pit
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
ERROR: Failed to send handshake!ERROR: Protocol initialisation failed!
Releasing device interface...
Have you flashed the proposed vbmeta before or when flashing TWRP ?
According from twrp
If you wish to install TWRP without rooting, there are numerous pitfalls to consider. For example, a stock device is protected by Android Verified Boot. This is implemented as a vbmeta partition that contains cryptographic digests for verifying the integrity of boot.img, recovery.img and other partitions/images. Flashing TWRP without first flashing a vbmeta image with verity disabled will render your device unable to boot.
This is, if i would like to intall twrp 3.5.2 on the tablet. This little vbmeta.img has worked, but i have no idea what this minifile is doing. What also has worked i can boot into android owns recovery image.
With Linux Heimdall Gui (tested too) i can’t even download the PIT file. There is still something wrong.
Power off the device, and boot it into download mode:
With the device powered off, plug in the device while holding Volume up + Volume Down + Power.
Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”, and insert the USB cable into the device.
Device will restart, repeat steps 1 and 2.
Verify that “OEM Unlock” is still enabled and continue to step 5
Download and install the necessary drivers.
Download the newest Samsung drivers from here. You will need to create a Samsung account and login to download them.
Run Odin3 v3.13.1 found in the newly extracted “Odin_3.13.1” folder.
Check the box labeled next to the button labeled “AP”, and then click the “AP” button.
In the menu that pops up, select the newly downloaded custom VBMeta .tar file.
10.check*
11.TIP:* The filename may very depending on your device, and version of TWRP.
Check in the top left of thne Odin window that you see a valid device, it will show up as something like COM0.
13.check*
14.TIP:* The COM port, or the number succeeding COM, may be any valid number.
A blue transfer bar will appear on the device showing the recovery image being flashed.
Your device will reboot, you may now unplug the USB cable from your device.
The device will demand you format userdata, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu
After flashing VBMeta, boot to stock. It’ll likely ask you to wipe data, if so do that
Connect to WiFi network and make sure OEM Unlock in developer options is still checked
Now you can flash TWRP ( https://dl.twrp.me/gts4lvwifi ) in Odin ( use AP slot once again ), for convenience you can hold volume up while flashing it so that you boot to recovery right after it’s flashed
Install Lineage × whatever else you need ( gapps, addon-su, … )
Format data
Reboot ( make sure to not install TWRP app when TWRP asks you to )
Yes adb reboot donwload is the same, coming from system mode or recovery mode,
but outing from download mode and going to recovery mode (to validate the TWRP install),
you will need to use the buttons combination and the good timing
I am finally one step further. The bootloader is unlocked. The key combination was quite different: “Volume UP/Down” and while pressing these buttons plugin the USB cable.
I have an S5e, so normaly TWRP it should work. But if you see my screenshot, it would not. So i loaded with odin only the VBMETA.
Maybe the problem is “secure download enable”. I did not find any option for this on the tablet.
2 questions:
Is anything else missing?
Or may I put e/OS without TRWP, probably a bad idea because if something goes wrong I can throw away the tablet?
In your Download mode screen I see
KG status Prenormal.
I think we really need to account for the reason for seeing that.
This can happen when the phone is being used now in a country different from the one it was intended to be used in when Samsung sent it out. Put another way it has been imported in a slightly irregular way.
Could that be the case here? Do you have all the original labels and packaging? Edit, or alternatiely that it has not been used with a local SIM card in the local country for a specified time to “lift” the restriction.
I just looked at the original packaging. Apparently, the device was originally intended for France. I am in Austria. The device does not have a SIM card slot. Only MicroSD
This also explains why after I unlocked the bootloader, the language was set to French. But what does the country have to do with the fact that it can’t be flashed? What if I were in France right now? It’s the same planet…
Sure that was just a first guess. Here is a Knox Guard page for the UK.
Sounds quite benign, really. But Knox is a security suite to do all sorts, including what I guessed a Regional lock. (It might well be a different lock!)
Some form of trade restriction? but within EU seems strange.
Step one would be to find what magic would release the Regional lock, edit, unknown.
Did you use it for a while “normally” after you first got it? Any labels to tell you what is required?
Yes I used it normally for 2 days, played with it a little. The first time I turned it on it came with the wizard and suggested German language, then I connected it to my wifi here.
Other than that I haven’t noticed anything unusual or important unfortunately.
If it was new from a Samsung dealer, this would be for their support staff.
“Prenormal” seems to be used to tell the device that it is not yet open for “normal” business until some event has happened to release it. We have seen a label saying that you must make 5 minutes of calls on phones in EU.
Ok, i created an test google and test samsung account, connect with my WLAN with Country US / Language US because it is easier with tutorials and findout menu positions. So i let the tablet only with GPS and do all nice Updates, after that i will reboot into downloadmode again. Maybe the status will be changed.
USA is where this problem really hits! Will UK setting work for you in case geo-location is very important to the release! A Samsung account might be a very good idea,
Hi @piero my feeling is that that method stopped working with Android 10. When you read the recent contributions, it has still worked for some, but we do not always see the cause of the “lock” and the Android version.
It is definitely worth reading (and opening and inspecting the patch) to help understand how these locks are triggered and potentially released.
After all, it has worked now with the file vbmeta.tar.
Now i see on the screen “Android Recovery”
Can’t load android system your data may be corrupt. If you contiue you get this message, you may need to perform a factory data reset and erase all user data stored on this device.
