Develop Bugs

From Samsung to Sony and confused about Bootloader unlocking.

Im thinking of buying a Z5P and while i have searched a lot, i just cant seem to find the answer to a question i have maybe someone here can help. On Sonys developer website there is instructions on how to unlock the bootloader and the last line of the instructions are as follows, note the part in blue text.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.[/B]
My question is how/where do i buy a Z5P that will definitely be Bootloader unlock allowed yes, surely its not just a case of random devices are unlockable is it? I was going to buy this from carphone its sim free so im expecting to be allowed to unlock the bootloader but dont want to buy it only to find i cant.
http://www.carphonewarehouse.com/phones/sony-xperia-z5-premium/handset?colourCode=BLACK

If the phone has no SIM lock, it's bootloader should be unlockable. I say "should" since I am not aware of other factors that keep the bootloader locked, but there might as well be.
On another note, unless you are a fairly advanced user and are set on flashing your device with a custom kernel, I would not recommend a bootloader unlock before root or an option to back up of TA becomes available.
It contains your device's DRM which gets irreversibly lost which makes your camera perform worse(BIONZ stops working), among other things.

CPW is the place to go for unlockable fones. I got my Z5P from there.
Sent from my SGP311 using XDA Free mobile app

As mentioned elsewhere, IN GENERAL (rare exceptions) - if it's SIM-unlocked it'll be bootloader-unlockable. If it's SIM-locked, the bootloader is almost guaranteed to be perma-locked.
While SIM locks and bootloader locks are technolgically independent, in the case of Sony devices (This rule of thumb can NOT be applied to any other manufacturer), SIMlocked devices have a permanent bootloader lock, devices sold without a SIM lock can have bootloader unlocked. Note that in the case of phones sold with a SIM lock that are later unlocked with a PIN - the bootloader lock is still disallowed.

Cheese for the replys everyone I got the phone from the carphone and its boot loader unlock allowed yes
I got the regular z5 instead though.

Hey, Dunno if I have an option or not, but my phone says Bootloader Unlock Allowed: No.
I imagine that it's a no, but is there any way to unlock the BL? If not I may consider swapping the Z5P out for something else, dunno if I can live without root

NJ72 said:
Hey, Dunno if I have an option or not, but my phone says Bootloader Unlock Allowed: No.
I imagine that it's a no, but is there any way to unlock the BL? If not I may consider swapping the Z5P out for something else, dunno if I can live without root
Click to expand...
Click to collapse
Try flashing another firmware through flashtool that is allowed.

KbaB.BroS said:
Try flashing another firmware through flashtool that is allowed.
Click to expand...
Click to collapse
Worth a punt, didn't think about that. The only concern is that Flashtool isn't supported for the Z5p according to Sony's site.

NJ72 said:
Worth a punt, didn't think about that. The only concern is that Flashtool isn't supported for the Z5p according to Sony's site.
Click to expand...
Click to collapse
As long as you use flashmode there is no need to be supported, because the program doesn't know which phone it is in that state. I flashed my Z5P once using flashtool about a week ago.

KbaB.BroS said:
As long as you use flashmode there is no need to be supported, because the program doesn't know which phone it is in that state. I flashed my Z5P once using flashtool about a week ago.
Click to expand...
Click to collapse
OK, cool, thanks.
Where do I get the firmware from for Flashtool? Can I flash something like AurRom using Flashtool?
Sorry for the idiot questions, but I haven't used Flashtool very much at all. Much more familiar with ODIN, ADB and flashing through recovery...

NJ72 said:
OK, cool, thanks.
Where do I get the firmware from for Flashtool? Can I flash something like AurRom using Flashtool?
Sorry for the idiot questions, but I haven't used Flashtool very much at all. Much more familiar with ODIN, ADB and flashing through recovery...
Click to expand...
Click to collapse
Install flashtool from "flashtool.net"
It comes bundled with Xperifirm where you can download ftf files for every Xperia device. You access Xperifirm through the Flashtool program.
You cannot flash AurROM through flashtool because it's not a ftf file. Flash a stock rom and try unlocking the Bootloader afterwards.
And don't worry about asking "stupid questions". This thread is made for every kind of questions, as long as it's about the device.

KbaB.BroS said:
Install flashtool from "flashtool.net"
It comes bundled with Xperifirm where you can download ftf files for every Xperia device. You access Xperifirm through the Flashtool program.
You cannot flash AurROM through flashtool because it's not a ftf file. Flash a stock rom and try unlocking the Bootloader afterwards.
And don't worry about asking "stupid questions". This thread is made for every kind of questions, as long as it's about the device.
Click to expand...
Click to collapse
Thanks very much.
One final question, in the UK I have EE WiFi calling currently - if I install non-carrier specific firmware I will most likely lose this. Is there any way I can backup the existing software so I can revert whether the flashtool flash works or not?

NJ72 said:
Thanks very much.
One final question, in the UK I have EE WiFi calling currently - if I install non-carrier specific firmware I will most likely lose this. Is there any way I can backup the existing software so I can revert whether the flashtool flash works or not?
Click to expand...
Click to collapse
You can try this guide:
http://m.youtube.com/watch?v=F0bSsGxFdks

NJ72 said:
Thanks very much.
One final question, in the UK I have EE WiFi calling currently - if I install non-carrier specific firmware I will most likely lose this. Is there any way I can backup the existing software so I can revert whether the flashtool flash works or not?
Click to expand...
Click to collapse
What you want to do is follow sonys instructions on how to check if your phone is able to unlock bootloader here: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
If you can unlock your bootloader, which you will know after performing the simple steps provided by sony, then you need to install android studio along with required drivers etc, before you can actually unlock the bootloader.
Android studio can be found here: http://developer.android.com/sdk/installing/index.html?pkg=studio
Read everything throughly, it is important to get all the details regarding usage and installation.
After installing Android studio, you should download all the required SDK's found inside android studio->Configure->SDK Manager.
On the left side you will see several options in the navigation menu.
First go to Appearance & Behavior->System settings->Android SDK. Then in the "window" you have, make sure the first tab is selected (SDK Platforms).
Here you need to check all the android versions your phone(s) run.
Then go to the second tab (SDK Tools) and download:
Android SDK Build Tools
Android SDK Tools 24.4.1
Android SDK Platform-Tools 23.1
Google USB Driver
Android NDK
I am not sure if you really need the NDK one, but the rest I think is required. You can do as I did and choose all if you want.
On the last tab (SDK Update Sites) I have checked everything.
When you have done all of this, you should install Flashtool and go to the install directory and open the Driver folder, where you will find a .exe file. Run this and click next untill you can choose a few items from a list, in this list you should check Fastboot drivers, and USB drivers, and any other options that are relevant to your use, then finish the installation. (The entire installation of Flashtool should be done with 100% admin rights on the user).
After this is done, connect your phone to your pc and go to device management on your pc and you will likely find something similar to this:
If you have this yellow exclamation mark triangle thingy, then you will need to manually install your USB drivers.
Download your driver here: http://developer.sonymobile.com/downloads/drivers/
Then right click the yellow exclamation mark triangle thingy device in device management, and select update driver, then select "Browse my computer for driver software".
On the next window, select "Let me pick from a list of device drivers on my computer".
In the list that appears, select "Show All Devices" and click next.
Click the "Have Disk" button, then navigate to the driver you downloaded, and you will get 3 options in the window on you screen, select "Android ADB Interface" and click next.
Confirm by pressing "Yes" Then press "Install".
If completed without problems you should see "Windows has successfully updated your driver software".
*NOTE* On the above steps, you can also navigate to the folder where you installed android studio, which should be something similar to this: C:\Program Files(x86)\Android\android-sdk\extras\google\usb_driver OR it can be found your USER folder.
and here you can install the usb_driver aswell, which should make most phones support USB debugging and ADB on via your pc.*NOTE*
now reconnect your phone and the exclamation mark triangle thingy should be gone, good!
Next thing you can do is navigate to the installation folder of Android studio, and go to the Platform-Tools folder.
Inside the folder, hold down shift, while right clicking any white empty space inside the folder, and click open terminal here.
In the terminal, type: "adb devices" /Without the " marks. then it should say something about daemon not running etc, when its done, do the same command again, and you should se you device listed. Good, at this point you are ready to unlock bootloader!
If you have succeeded in every step so far, then go ahead and unlock bootloader following sonys instructions!
When you are done, you can simply follow the guides provided in the custom Rom thread itself most of the time.
If not, then a simple way to do it is:
Get all the files you need for the rom flash. That means Kernel, rom img, and a custom recovery like TWRP and SuperSU.
It is REALLY important that all files are for your device specifically!
Put the SuperSU.zip and the custom Rom.zip on your sd card and put it in the phone.
To avoid any trouble, do as I did and save all those files in the Platform-Tools folder, because you need to open the terminal as shown earlier in the post, by holding shift and right clicking in the same folder as the files, this is a must.
Open the terminal from the same folder as the rom, kernel and recovery.
type:
Code:
fastboot flash boot NAMEOFYOUR_KERNEL.img (This is usually boot.img)
fastboot flash recovery NAMEOFYOUR_RECOVERY.img (Usually contains TWRP in name)
fastboot reboot
You should now press volume up key when a led lights up while you see the sony logo, a orange light, not the red one, this will bring you into recovery, from here choose install, then navigate to your SuperSU.zip and install it.
Reboot your phone and you are now rooted, if you also have a custom rom, then place it on your sd card like the SuperSU.zip, but make sure the custom rom is a ZIP file!
Boot into recovery and install the custom rom, wipe cache and dalvick cache.
Congratulations on your custom rom!
Hope this helps a bit, sorry for any errors, but this is exactly how I did it, as far as I can remember!
Btw, this can seem like alot of work, especially when and if you encounter any problems while installing. I know I did encounter ALOT of them, but hopefully with my simple guide you can avoid them!
Luckily, this is just something you have to do once if you do it 100% right!

xirt0n said:
What you want to do is follow sonys instructions on how to check if your phone is able to unlock bootloader here: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
If you can unlock your bootloader, which you will know after performing the simple steps provided by sony, then you need to install android studio along with required drivers etc, before you can actually unlock the bootloader.
Click to expand...
Click to collapse
The problem he has is that his stock ROM (or the phone itself) doesn't allow bootloader unlocking, probably because of SIM and carrier lock. Therefore he first needs to find a way to make the phone unlockable.

KbaB.BroS said:
The problem he has is that his stock ROM (or the phone itself) doesn't allow bootloader unlocking, probably because of SIM and carrier lock. Therefore he first needs to find a way to make the phone unlockable.
Click to expand...
Click to collapse
I am no expert on this, but doesnt the carrier decide if its locked or not?
I've seen people solve it by flashing different and unbranded firmware, but not for this particular phone tho, but I dont think it's officially possible.

xirt0n said:
I am no expert on this, but doesnt the carrier decide if its locked or not?
I've seen people solve it by flashing different and unbranded firmware, but not for this particular phone tho, but I dont think it's officially possible.
Click to expand...
Click to collapse
At this point he could at least try, he's got nothing to lose. I have never had this problem, because I buy my phones unlocked no carrier involved, so these are only suggestions.

KbaB.BroS said:
At this point he could at least try, he's got nothing to lose. I have never had this problem, because I buy my phones unlocked no carrier involved, so these are only suggestions.
Click to expand...
Click to collapse
Yeah, what I would try is first just try to do a full restore of your phone via PC Companion, and if that doesnt work then id try downloading an unbranded firmware from XperiFirm (If I am not mistaken, those named CUSTOM or something are unbranded) and then flash that via flashtool and see if that works, if not then your last hope is to get it replaced by warranty, which I'd say is fraud if the device isnt actually malfunctioning.

xirt0n said:
Yeah, what I would try is first just try to do a full restore of your phone via PC Companion, and if that doesnt work then id try downloading an unbranded firmware from XperiFirm (If I am not mistaken, those named CUSTOM or something are unbranded) and then flash that via flashtool and see if that works, if not then your last hope is to get it replaced by warranty, which I'd say is fraud if the device isnt actually malfunctioning.
Click to expand...
Click to collapse
I don't think PC Companion works at all, because the only thing it does is downloading identical firmware like the one on the phone. So Flashtool only choice.
I replaced mine with one from flashtool that has a lot less bloatware it originally came with.

KbaB.BroS said:
I don't think PC Companion works at all, because the only thing it does is downloading identical firmware like the one on the phone. So Flashtool only choice.
I replaced mine with one from flashtool that has a lot less bloatware it originally came with.
Click to expand...
Click to collapse
Ok, I never personally used PC companion so I didnt know what it does, I just saw people suggest it around

Posible bootloader unlock?

Ok I am not a guru or noting but since I received my phone today I decided to try some adb.
1) enable oem unlock under developer option
2) booted into fastboot
3) run adb command fast oem unlock
4) my phone restarted and it was wipe and not when I boot it say "device software can't not be checked for curuption"
5) run a adb bootloader check and it doesn't say unlock or lock so I am stuck lol any suggestions?

Pics

Your phone boots back up just fine? That message was implemented with Android 6.0 Marshmallow.

HtcOnekid said:
Ok I am not a guru or noting but since I received my phone today I decided to try some adb.
1) enable oem unlock under developer option
2) booted into fastboot
3) run adb command fast oem unlock
4) my phone restarted and it was wipe and not when I boot it say "device software can't not be checked for curuption"
5) run a adb bootloader check and it doesn't say unlock or lock so I am stuck lol any suggestions?
Click to expand...
Click to collapse
Does your LG G5 boot fine into Android now after your actions?

Yes it does

That's the same message that appears on my 6p when I unlocked my bootloader
Sent from my Nexus 6P using Tapatalk

george_harris said:
That's the same message that appears on my 6p when I unlocked my bootloader
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
AWESOME!, many THX for the confirmation & WELCOME TO XDA-DEVELOPERS! :good:

KOLIOXDA said:
AWESOME!, many THX for the confirmation & WELCOME TO XDA-DEVELOPERS! :good:
Click to expand...
Click to collapse
I foresee a new phone crossing Kolio's path...

CafeKampuchia said:
I foresee a new phone crossing Kolio's path...
Click to expand...
Click to collapse
Yeah, there's a good chance I'll be stopping by T-Mobile later today...

It's still locked from what I can tell, regardless the device does not accept unsigned firmware images via flashboot boot or flashboot flash.
It should accept unsigned system images, HOWEVER dm-verity is enabled, so they will not boot at all.
Looks like you're in the same boat as the Qualcomm S7's.

jcadduono said:
It's still locked from what I can tell, regardless the device does not accept unsigned firmware images via flashboot boot or flashboot flash.
It should accept unsigned system images, HOWEVER dm-verity is enabled, so they will not boot at all.
Looks like you're in the same boat as the Qualcomm S7's.
Click to expand...
Click to collapse
Sad day today
Sent from my LG-H830 using Tapatalk

jcadduono said:
It's still locked from what I can tell, regardless the device does not accept unsigned firmware images via flashboot boot or flashboot flash.
It should accept unsigned system images, HOWEVER dm-verity is enabled, so they will not boot at all.
Looks like you're in the same boat as the Qualcomm S7's.
Click to expand...
Click to collapse
on S7 Thread you have posted a solution to dm-verity off.
Can you here ?

wolfgart said:
on S7 Thread you have posted a solution to dm-verity off.
Can you here ?
Click to expand...
Click to collapse
turning dm-verity off requires an unlocked device. the G5 is a locked device.
dm-verity is enabled in the boot image via fstab. by changing the boot image, you trigger qualcomm secure boot.
your device will not be able to boot with a modified boot image, nor will it be able to boot with a modified system image.
we'll just have to keep waiting for a manufacturer that is reasonable.
it's a shame that the linux kernel can't save us here. linus torvalds and the maintainers of linux only care about software freedom and not hardware freedom.
the biggest difference between GPLv2 and GPLv3 is that GPLv3 provides hardware freedom.
the linux kernel will always be GPLv2.

jcadduono said:
turning dm-verity off requires an unlocked device. the G5 is a locked device.
dm-verity is enabled in the boot image via fstab. by changing the boot image, you trigger qualcomm secure boot.
your device will not be able to boot with a modified boot image, nor will it be able to boot with a modified system image.
we'll just have to keep waiting for a manufacturer that is reasonable.
it's a shame that the linux kernel can't save us here. linus torvalds and the maintainers of linux only care about software freedom and not hardware freedom.
the biggest difference between GPLv2 and GPLv3 is that GPLv3 provides hardware freedom.
the linux kernel will always be GPLv2.
Click to expand...
Click to collapse
agree with you.
It's really shame to see Android devices with hardware lock !!! iOS now is more freedom ....
I want webOS come back from Dead ....

Has anyone contacted LG about this?

matteosaeed said:
Has anyone contacted LG about this?
Click to expand...
Click to collapse
You can ask them on their developer forum here : http://developer.lge.com/community/forums/RetrieveForumContentList.dev?forumId=FR00000001

wolfgart said:
You can ask them on their developer forum here : http://developer.lge.com/community/forums/RetrieveForumContentList.dev?forumId=FR00000001
Click to expand...
Click to collapse
I tried to send them some feedback but their website does not allow me to send must be disabled at the moment.

wolfgart said:
You can ask them on their developer forum here : http://developer.lge.com/community/forums/RetrieveForumContentList.dev?forumId=FR00000001
Click to expand...
Click to collapse
i wouldnt even bother. reading that forum they havent replied to any questions and they also state they only bootloader unlock the european market devices. so USA ones they dont touch.

Downgrade to original 7.1.2

Hi,
Is it possible to downgrade to 7.1.2 and have my phone completely stock?
I mean like it was, no rooted or something else..
Now I have the latest oreo version from google.
Thanks

thanasisglt said:
Hi,
Is it possible to downgrade to 7.1.2 and have my phone completely stock?
I mean like it was, no rooted or something else..
Now I have the latest oreo version from google.
Thanks
Click to expand...
Click to collapse
Yes just flash latest 7.1 bullhead image and then relock bootloader and you will have your device like stock but why would you downgrade?!

Yes just flash latest 7.1 bullhead image and then relock bootloader and you will have your device like stock but why would you downgrade?!
Click to expand...
Click to collapse
My device is slower than 7.1.2 and also I don't like the layout.
Is there any guide how to do that?
Thanks

thanasisglt said:
My device is slower than 7.1.2 and also I don't like the layout.
Is there any guide how to do that?
Thanks
Click to expand...
Click to collapse
Sorry to answer hours after but I didn't got any notifications...
So, download,
platform tools : https://developer.android.com/studio/releases/platform-tools
Latest 7.1.2 build : https://dl.google.com/dl/android/aosp/bullhead-n2g48c-factory-45d442a2.zip
Then exctract the content of the 7.1.2 build in the platform tools folder then connect you smartphone to your PC in bootloader mode (vol down + power button).
Finally in the platform tools folder you will find a file named flashall.bat, simply execute it and you are done, your device will be on stock 7.1.2
PS: This guide was done assuming you know how to lock and unlock your bootloader if not...tell me ? (kidding happy to help ? ).

francos21 said:
Sorry to answer hours after but I didn't got any notifications...
So, download,
platform tools : https://developer.android.com/studio/releases/platform-tools
Latest 7.1.2 build : https://dl.google.com/dl/android/aosp/bullhead-n2g48c-factory-45d442a2.zip
Then exctract the content of the 7.1.2 build in the platform tools folder then connect you smartphone to your PC in bootloader mode (vol down + power button).
Finally in the platform tools folder you will find a file named flashall.bat, simply execute it and you are done, your device will be on stock 7.1.2
PS: This guide was done assuming you know how to lock and unlock your bootloader if not...tell me (kidding happy to help ? ).
Click to expand...
Click to collapse
Thanks a lot for the guidance!
Unfortunately, I don't know how to unlock and lock the bootloader. I 've never done this before and always had my device stock. Any advice would be helpful!
Thanks

thanasisglt said:
Any advice would be helpful!
Click to expand...
Click to collapse
Read the instructions.

thanasisglt said:
Thanks a lot for the guidance!
Unfortunately, I don't know how to unlock and lock the bootloader. I 've never done this before and always had my device stock. Any advice would be helpful!
Thanks
Click to expand...
Click to collapse
NOTE : unlocking bootloader will erase all your data!!!
NOTE 2 : If you lock your bootloader without the factory image flashed you will brick your device so no more usable!!!!! So personnaly I don't recommand you to do that because you don't need that to return on Android 7 it's just a "security" for your data.
NOTE 3 : read this guide too because it's more complete and what you are going to do is a bit risky(I speak for locking bootloader) , really! Don't want a message saying "you forgot this line, my device is lost ? ...".
So let's start fun things ?
Go in developer options and enable oem unlock and USB debugging.
Then reboot in bootloader mode and connect your device to your computer.
After that open the prompt command from the extracted platform tools folder by right clicking in this folder with the maj key down.
In this command windows write the following line:
fastboot oem unlock
Or .\fastboot oem unlock if your are on windows 10 (windows is blue instead of black).
When the bootloader is unlocked you can flash a custom recovery then instal a ROM/kernel or flash the factory image.
When you have flashed the factory image (stock ROM...) you can lock the bootloader with this line(same method)
fastboot oem lock (add .\ for windows 10).
Tell me if you need further help ? .

francos21 said:
NOTE : unlocking bootloader will erase all your data!!!
NOTE 2 : If you lock your bootloader without the factory image flashed you will brick your device so no more usable!!!!! So personnaly I don't recommand you to do that because you don't need that to return on Android 7 it's just a "security" for your data.
NOTE 3 : read this guide too because it's more complete and what you are going to do is a bit risky(I speak for locking bootloader) , really! Don't want a message saying "you forgot this line, my device is lost ...".
.
Click to expand...
Click to collapse
Thanks again!
I have to lock the bootloader if I downgrade because bank apps don't work if the device is not stock as far as I know..
other than that I don't mind to be unlocked and playing with custom roms..

thanasisglt said:
Thanks again!
I have to lock the bootloader if I downgrade because bank apps don't work if the device is not stock as far as I know..
other than that I don't mind to be unlocked and playing with custom roms..
Click to expand...
Click to collapse
That's actually not true, at least I think as I don't use bank apps that don't accept that my bank app is accepting root too ?
But seriously, from where did you catch the info?

francos21 said:
That's actually not true, at least I think as I don't use bank apps that don't accept that my bank app is accepting root too
But seriously, from where did you catch the info?
Click to expand...
Click to collapse
I have read comments from developers to advice users whose apps are not functional that the devices should not be rooted and generally should be stock.
Anyways..I will think it again if I continue to the procedure..
PS: I hate the layout of oreo..these white (like LG) squared app icons are simply terrible!

thanasisglt said:
I have read comments from developers to advice users whose apps are not functional that the devices should not be rooted and generally should be stock.
Anyways..I will think it again if I continue to the procedure..
PS: I hate the layout of oreo..these white (like LG) squared app icons are simply terrible!
Click to expand...
Click to collapse
Android layout can be changed easily and having latest Android security offer security and latest features and performances patchs, anyway it's your decision.

thanasisglt said:
I have read comments from developers to advice users whose apps are not functional that the devices should not be rooted and generally should be stock.
Anyways..I will think it again if I continue to the procedure..
PS: I hate the layout of oreo..these white (like LG) squared app icons are simply terrible!
Click to expand...
Click to collapse
Just keep in mind that unlocking the bootloader and flashing the original rom will NOT result in a rooted phone. If you do the this and relock the bootloader, then your phone will be in a totally stock NON ROOTED state. So any concerns that you have regarding root don't apply here.

I am still on 7.1.2 too because of the performance/lag issues in 8.1
... I never upgraded... Is it still really that bad in 8.1 ? Or better with latest patches?
Sent from my [device_name] using XDA-Developers Legacy app

_giwrgos_ said:
Just keep in mind that unlocking the bootloader and flashing the original rom will NOT result in a rooted phone. If you do the this and relock the bootloader, then your phone will be in a totally stock NON ROOTED state. So any concerns that you have regarding root don't apply here.
Click to expand...
Click to collapse
Hi,
my device got bootlooped. Warranty expired 20 days ago and the cost was too high to repair.
So, I followed an online tutorial, flashed my phone and came back to life.
The issue is that the bootloader is unlocked and I cannot use android pay (it says that the device is somehow altered)
Although banking apps work normally.
Is it ok to relock the bootloader?
(what if the device get bootloop again? / is it possible to brick my device? / could I use another way to bypass and activate android pay?)
Thanks

thanasisglt said:
Hi,
my device got bootlooped. Warranty expired 20 days ago and the cost was too high to repair.
So, I followed an online tutorial, flashed my phone and came back to life.
The issue is that the bootloader is unlocked and I cannot use android pay (it says that the device is somehow altered)
Although banking apps work normally.
Is it ok to relock the bootloader?
(what if the device get bootloop again? / is it possible to brick my device? / could I use another way to bypass and activate android pay?)
Thanks
Click to expand...
Click to collapse
Firstly let me tell you that I am assuming that you have flashed an official stock rom, if you didn't then just ignore what I am saying!
I never heard of anyone bricking the device just by locking the bootlader. The worst thing that can happen is to get a bootloop indeed, but if you just unlock the bootloader again then it should be fixed. Bricking the device just by locking the bootloader sounds totally impossible to me at least. I don't know if there is another way to bypass this and activate android pay but even if there is personally I will not have trusted it.

twrp/root A70

hi,
A70 is now widely sold, i try to buy one soonest but just waiting for root and twrp. it is still empty here on xda...
i found a link show how to root and install
https://myphoneupdate.com/samsung-galaxy-a70-twrp-recovery/
can i ask if some one already tried as above? looks like a copy method for all kind of phones ...
tks.

Most likely fake, the article was published a month ago. A70 only got released on 26th March.

I would definitely wait until someone posts a technique here; I tend to trust the experts here, but not so much everywhere else on the internet. I would prefer to wait a few weeks and put with an unrooted device, rather than possibly end up with a bricked (or hijacked) device.
Andre

ok i will wait...
it was like this, waited for s10+, came twrp but didnot like camera hole and waiting for A70, then waiting for twrp, then oneplus7pro release, then wait a bit for its twrp, till then note 10 pro comes soon, then wait for twrp of it....
and after 2+ year still using note8 LOL

amk said:
hi,
A70 is now widely sold, i try to buy one soonest but just waiting for root and twrp. it is still empty here on xda...
i found a link show how to root and install
https://myphoneupdate.com/samsung-galaxy-a70-twrp-recovery/
can i ask if some one already tried as above? looks like a copy method for all kind of phones ...
tks.
Click to expand...
Click to collapse
First thing I tried ofcourse, rooting the A70, but... follow the steps in the manual yourself, and you'll see that you get stuck on step 3:
3.) After That Download TWRP Recovery https://twrp.me File On Your PC And Renamed The Downloaded Recovery File Name To twrp.img.
But there is no TWRP Recovery available for the A70
I also tried the A50 manual, but that also fails (stuck on OEM lock). I can install CROM Service, but it crashes.

Captain Beretta said:
First thing I tried ofcourse, rooting the A70, but... follow the steps in the manual yourself, and you'll see that you get stuck on step 3:
3.) After That Download TWRP Recovery https://twrp.me File On Your PC And Renamed The Downloaded Recovery File Name To twrp.img.
But there is no TWRP Recovery available for the A70
I also tried the A50 manual, but that also fails (stuck on OEM lock). I can install CROM Service, but it crashes.
Click to expand...
Click to collapse
don't follow some clickbait website's...
wait for a proper and trusted dev to release twrp. the phones has barely hit the market it will take a few weeks (if not months) at least till someone builds an twrp. one think you could provide us with would be some information. is the bootloader unlockable?

In devsettings is a possible to unlock oem. Try this before flashing twrp. If twrp flashed ok, I think need to wipe all data, include internal storage, then flash DM-VERITY, FORCE ENCRYPTION, AND DISC QUOTA DISABLER
zackptg5.com/android.php
I don't try it by myself. But you can try it, if you just buy the phone, and have not important data on it

What about this guide is it worth trying or not really possible? https://topjohnwu.github.io/Magisk/install.html

Avicohen21 said:
What about this guide is it worth trying or not really possible? https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
Need to try

hello everyone I find a good deal on galaxy a70 is anyone succeed in rooting?

celoxocis said:
... is the bootloader unlockable?
Click to expand...
Click to collapse
i have opened 2 sealed box of A70 and there was no OEM unlock option in developer mode. then got another with tick to choose. baterry is so good but look like i have touch panel issue. waiting for update and then root, twrp...

amk said:
i have opened 2 sealed box of A70 and there was no OEM unlock option in developer mode.
Click to expand...
Click to collapse
Mine (bought direct from Samsung UK) has the OEM Unlock option in the Developer Options menu. Not tried it yet, not really much point until there is a reliable and tested root out there.
Andre

Hey guys manegd to root with this guide https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
Seems to work good I'll notify if I'll notice any bugs. If you have twrp porting guide send me and I'll try to Port. If you want I can open a new thread with more details and upload the AP file I used. BTW I have the Israeli version SM-705FN

Avicohen21 said:
Hey guys manegd to root with this guide https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
Seems to work good I'll notify if I'll notice any bugs. If you have twrp porting guide send me and I'll try to Port. If you want I can open a new thread with more details and upload the AP file I used. BTW I have the Israeli version SM-705FN
Click to expand...
Click to collapse
make a topic please

sanakess said:
make a topic please
Click to expand...
Click to collapse
Ok when I get home I'll open a thread with detailed explanation of what I did

Samsung account
Hello. My dumbass bought used A70 with samsung account. I can't make a factory reset, because it needs password from old owner account which i don't know. But I have my Google account on that phone and Google find my device enabled. Will I need to enter samsung account information when I make a reset via Google find my device? So when reset is made, phone will be locked only by FRP? And then when I login in my old Google account can i create a new Samsung account or do I need to login in existing that was on that phone first? Sorry for offtopic.

Any news about TWRP? SuperSu or Magisk?
Hello All, still can't find TWRP for sm-a705fn
Can I flash TWRP for another Exynos phone, like Galaxy 9, to my A70 ?
Also, can I still use SuperSu with Pie/A70 ? I failed to root my previous Galaxy Tab8 with custom Pie using SuperSU, had to root with Magisk instead,
it worked just fine, but the link to topjohnwu mentioned in previous posts, tells scary things about Samsung/Pie/Magisk -
like, I have to switch between two recoveries... Is that really the case?
I haven't noticed any issue with Tab8/Pie/Magisk, but SuperSu would be still more familiar to me.

used2brick said:
Hello All, still can't find TWRP for sm-a705fn
Can I flash TWRP for another Exynos phone, like Galaxy 9, to my A70 ?
Also, can I still use SuperSu with Pie/A70 ? I failed to root my previous Galaxy Tab8 with custom Pie using SuperSU, had to root with Magisk instead,
it worked just fine, but the link to topjohnwu mentioned in previous posts, tells scary things about Samsung/Pie/Magisk -
like, I have to switch between two recoveries... Is that really the case?
I haven't noticed any issue with Tab8/Pie/Magisk, but SuperSu would be still more familiar to me.
Click to expand...
Click to collapse
No, you can't use twrp for a different device, and don't use SuperSU neither. It was sold by chainfire to a Chinese company years ago and have been basically abandoned since 2017. I'm pretty sure Magisk is the better choice on any device running android 5 - 9.
Sent from my motorola one vision

Hello,
The problem with the post you mentioned is that there is no valid twrp attached. And I noticed that only Odin detects the fastboot mode of this device. If you enable USB debugging let's say, the command "adb devices" will detect the device and list it; whereas, if you reboot it to bootloader mode(fastboot), the command fastboot devices doesn't detect the phone. So in fastboot mode, only Odin will detect the device. Meaning, that the post of fake and not tested.
Regards,
Wael

amk said:
i have opened 2 sealed box of A70 and there was no OEM unlock option in developer mode. then got another with tick to choose. baterry is so good but look like i have touch panel issue. waiting for update and then root, twrp...
Click to expand...
Click to collapse
That's weird. I do have the Bootloader unlock option in the developer settings and can do/undo it just fine. Looks like Samsung is using different Firmware versions on the A70?

Need help getting back to stock from weird FW

Hello,
I bought a Fire HD 8 (2018) from ebay, but it gives me some headaches. There is almost nothing on it, no playstore (neither amazon nor google), no browser, only six basic apps like a calculator. And there is something called WebView Browser Tester. When I enter Recovery and do a factory reset it reverts to this exact stage. I was able to use adb to install VLC Player but it acts a little strange. But when I install Google Playstore (+ Framework, Account Manager, Services) it will crash. Rebooting after that will end in a bootloop, that can only be broken by several attempts trying to get into recovery and do a reset.
So, I think this device once belonged to a developer. It also identifies itself as "kayak" in recovery menu. So I assumed it was unlocked at some point. But when I try to use fastboot to flash it, it states "locked hw". ADB sideload is not available.
I don't know what to do right now. I spend last night doing research without much success. Pretty much all Unlock-Tutorials assume that you are on stock firmware, and the ones for getting back to stock assume you have twrp installed which is also not the case here.
Hope somebody can help me getting this thing working again.
Thanks in advance,
Scoop

Can you unlock the BL

Well, I'm not quite sure how to do that. I only started to dive into the topic by yesterday. Do I have to setup a linux system to do that or is there another way?

Bro…. What are you trying to do if you did not unlock the BootLoader. Just follow a normal guide. Google.

Google brought me here ^^ I wanted to aks if there is en easier way to unlock it then opening it up and setting up a linux boot drive, given that the device has clearly been tinkered with before. I thought, it might be a "known" custom rom that has been to it flashed before. Just trying not to brick it...
But thanks for your answer.

I meant using fast boot….

Now you got me confused. I'm really sorry, but could you be a bit more specific? When I try to use the unlock command I'm always getting the error "the command you input is restricted on locked hw".

scoop111 said:
Now you got me confused. I'm really sorry, but could you be a bit more specific? When I try to use the unlock command I'm always getting the error "the command you input is restricted on locked hw".
Click to expand...
Click to collapse
do these (not at the same time, wait to boot into bootloader then do second and third cmd)
Code:
adb reboot bootloader
fastboot flashing unlock
fastboot reboot

That's exactly what I did. I also tried fastboot oem unlock instead of fast flashing unlock. But I'm always getting the same error "command restricted on locked hw".
I read on some site that "OEM unlock" must be enabled in developer options to have this working, but there is no such option.

ohhhhhh. Then your device is not unlockable.

I managed to unlock it via the hardware mod, but I'm stuck after that. It won't boot into recovery. Is there a way to flash the firmware just with fastboot access?

scoop111 said:
I managed to unlock it via the hardware mod, but I'm stuck after that. It won't boot into recovery. Is there a way to flash the firmware just with fastboot access?
Click to expand...
Click to collapse
If you did the hardware unlock all the way through, you should have TWRP recovery. From that you can flash anything.

scoop111 said:
I managed to unlock it via the hardware mod, but I'm stuck after that. It won't boot into recovery. Is there a way to flash the firmware just with fastboot access?
Click to expand...
Click to collapse
Can you message me in Telegram?

Have you had any success?
I have the exact same issue, and this is pretty much the only topic that shows up when searching "Kayak".
Fire Toolbox v30.3 doesn't like it either
'Codename "kayak" isn't supported/recognized by the Toolbox. Please plug in a supported Fire tablet and try again.'

What model is on the back there are hardware revisions of the 8 2018 L5S83A: Normal OG revision K29A5E: Pre production model for patching CLK Exploit