Database Develop

[Q] Solved-

Delete

unlocking the bootloader will wipe the device, you should have read the disclaimer on the HTCDev website and backed up the files before unlocking

IINexusII said:
unlocking the bootloader will wipe the device, you should have read the disclaimer on the HTCDev website and backed up the files before unlocking
Click to expand...
Click to collapse
Ahhh I totally forgot about that. Thanks.

[HowTo] Fastboot Mode on LG G Watch R

The simpliest way to boot you LG G Watch R into Fastboot:
Turn off the Watch
Turn the watch on normally
While LG logo is displayed and before the screen dims, swipe your finger from the top-left (10:30) position to the bottom-right (4:30) position.
Done
From Fastboot Mode you can easy enter the Recovery Menu of your G Watch R
here is a Video i created:

To connect your LG G Watch R with your PC:
be sure you have the latest SDK (ADB & Fastboot) installed
on your Watch enable Developer Options
"OK Google" -> Settings - about Device
Tab Build Number 7 times
go back to main Settings
enter Developer Options
enable ADB Debugging
Connect your watch with the Charging Dock to your PC
In Shell/Terminal/cmd
type
adb devices
Click to expand...
Click to collapse
to check if your Device is there
Now you can use ADB and Fastboot:
adb reboot bootloader
Click to expand...
Click to collapse
-> will bring you easy in Fastboot mode
adb reboot recovery
Click to expand...
Click to collapse
-> reboots the watch into Recovery Mode
ATTENTION:
fastboot oem unlock
Click to expand...
Click to collapse
-> opens the info to unlock your Bootloader Unlock will VOID your Warranty
fastboot oem lock
Click to expand...
Click to collapse
-> will lock the bootloader agian confirmed by @dclaw_fantum
I have tested this: It does lock the bootloader back to locked status. The little lock icon on the LG logo also goes away when the command is executed successfully.
Click to expand...
Click to collapse
Disclaimer
Your warranty is now void as soon the Bootloader is unlocked.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Thanks @eSportler for the tip

Have you tested unlocking the bootloader on your LG G Watch R ?

kashortiexda said:
Have you tested unlocking the bootloader on your LG G Watch R ?
Click to expand...
Click to collapse
Yes, but i haven't confirmed the Unlock yet (coz for me there is no need right now and there is nothing to flash yet) - thats why I know that there is an confirmation message.
Edit:
Pictures added

What is the watchface on the video?

alexxandro84 said:
What is the watchface on the video?
Click to expand...
Click to collapse
It's called Aviator, you can get in from PlayStore

bluedragon1982 said:
It's called Aviator, you can get in from PlayStore
Click to expand...
Click to collapse
Thank you

Anyone allready unlocked his Bootloader and tried to relock him? So we could mark this command as tested too

alexxandro84 said:
Thank you
Click to expand...
Click to collapse
bluedragon1982 said:
It's called Aviator, you can get in from PlayStore
Click to expand...
Click to collapse
Careful someone else reported screen burn after a few days with that exact watch face. It's in the general section of this forum....
Sent from my GT-I9505 using XDA Premium 4 mobile app

Hawke84 said:
Careful someone else reported screen burn after a few days with that exact watch face. It's in the general section of this forum....
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No problems here, but i dont use allways-on mode, my display is off when i dont need it, best way to safe battery

Can we expect to see some micro roms or something here?

alextdarling said:
Can we expect to see some micro roms or something here?
Click to expand...
Click to collapse
The Android Wear source code should be released alongside AW 5.0 Lollipop - which is expected in early December
once AOSP is available, custom roms should become a thing

Is this akin to the Nexus products in terms of the warranty? On Nexus devices, the bootloader is irrelevant to warranty, as relocking the bootloader restores your warranty. Is this the case here? Also, is the GWR as "unbrickable" as the Nexus line? The bootloader is obviously unlocked, so images can be flashed from fastboot, but to my knowledge no factory images or anything exist. In other words, if a partition gets screwy, can it be fixed like on a Nexus? Thanks!

Koopa777 said:
Is this akin to the Nexus products in terms of the warranty? On Nexus devices, the bootloader is irrelevant to warranty, as relocking the bootloader restores your warranty. Is this the case here? Also, is the GWR as "unbrickable" as the Nexus line? The bootloader is obviously unlocked, so images can be flashed from fastboot, but to my knowledge no factory images or anything exist. In other words, if a partition gets screwy, can it be fixed like on a Nexus? Thanks!
Click to expand...
Click to collapse
Almost everything is fixable if we have access to fastboot. Now if you accidently flash something incorrectly to the boot partition you might be in serious trouble. SO be weary of flashing bootloaders.

bluetooth on my watch is not work. Please download the backup System.

So just to confirm, fastboot oem lock will relock the bootloader? Just making sure, because if that works, warranty shouldn't be an issue. A simple relock should allow you to send it in for warranty if need be.

bluedragon1982 said:
Anyone allready unlocked his Bootloader and tried to relock him? So we could mark this command as tested too
Click to expand...
Click to collapse
I have tested this:
Code:
fastboot oem lock
It does lock the bootloader back to locked status. The little lock icon on the LG logo also goes away when the command is executed successfully.

dclaw_fantum said:
I have tested this:
Code:
fastboot oem lock
It does lock the bootloader back to locked status. The little lock icon on the LG logo also goes away when the command is executed successfully.
Click to expand...
Click to collapse
Thanks for the info, I updated the post with your info.

Just flashed all stock images by fastboot in bootloader mode and locked oem. Is it right if I want to send it in warranty? My screen is strangely flickering even after an all reset without any added app.

Never mind, I posted my question in another thread.

Manual update P10?

Anyone succeed with manually updating P10? I have tried with no sucess.
Old method is not working.
Thanks

No but did you made the dload folder with the update.app file and then booted into the stock recovery mode?
I woudnt know any other way since they removed that from update settings : |

I tried that, does not work.

You can't manual update the P10 or P10 Plus, since it requires an online check.
They removed the ability to manual update via dload methode.
The only way at this moment is to use FunkyHuawei!

Forsaked said:
You can't manual update the P10 or P10 Plus, since it requires an online check.
They removed the ability to manual update via dload methode.
The only way at this moment is to use FunkyHuawei!
Click to expand...
Click to collapse
What about Firmware finder? I've tried this as well but I only get download failed, even everything is done as it should.

Hey,
I am working into this direction and got some promising results already. I am testing two more things during the next days (so that I can be sure my Stuff won't break your phones) and hope I can share my findings with you early next week.

Lukx said:
Hey,
I am working into this direction and got some promising results already. I am testing two more things during the next days (so that I can be sure my Stuff won't break your phones) and hope I can share my findings with you early next week.
Click to expand...
Click to collapse
Good to hear that. :good:

So, it is not possible to update, even the firmware matches your corrent model/brand?
I finally found the FW for VTR-L09C109, but when using dload method I get "Installation failed".

No, it is not possible. Huawei did something with emui 5.1.

ladodo said:
No, it is not possible. Huawei did something with emui 5.1.
Click to expand...
Click to collapse
Wrong you can now debrand for free and offline check this out https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108 can confirm it works

Does bootloader needs to be unlocked and twrp installed?

ladodo said:
Does bootloader needs to be unlocked and twrp installed?
Click to expand...
Click to collapse
Well, OP clearly says, that bootloader must be unlocked......

davebugyi said:
Well, OP clearly says, that bootloader must be unlocked......
Click to expand...
Click to collapse
It is not good since you loose warranty with bootloader unlocked.

ladodo said:
It is not good since you loose warranty with bootloader unlocked.
Click to expand...
Click to collapse
Not always correct. It depends on the local country laws you live in.

And also if you follow the instructions you end with LOCKED Bootloader so no warranty lost

crucky said:
And also if you follow the instructions you end with LOCKED Bootloader so no warranty lost
Click to expand...
Click to collapse
Is it same with P10 as it was with P9, tha it say relocked instead locked bootloader, when you lock it again?

nope : Phone LOCKED
FRP unlocked so they cant see the difference they can only find out if they check if you got the bootloader unlock code.but you also could request the code and dont use it.

Any progress here? The update has been out for months in other regions but I still haven't got anything here in Sweden :/

Is it possible to re-lock bootloader after official unlock?

I'm doing some research before I commit to unlocking my bootloader, and I can't find anything definitive on whether or not it's possible to re-lock after unlocking with the official tool. I have experience unlocking and re-locking bootloaders, flashing custom recoveries/ROMs/kernels etc but only with Nexus and Samsung phones, so I just want to make sure I'm clear on how Nokia's setup differs (If at all). Would also be interested to find out if Nokia will still offer me OTA's with unlocked bootloader.
Thanks for any help, and feel free to move or close the thread if it matches another one that I've missed.

Bb

2WildFirE said:
I'm really sure you can relock bootloader. Why not?
And yes ota works fine with open bootloader if you are on stock
Click to expand...
Click to collapse
Awesome, cheers for the assist ?

2WildFirE said:
I'm really sure you can relock bootloader. Why not?
And yes ota works fine with open bootloader if you are on stock
Click to expand...
Click to collapse
Nokia says that relooking isn't possible. Is there anybody who tried the command 'fastboot oem relock'?

And why says this text please lock ? the bootloader, if it is not possible?

2WildFirE said:
And why says this text please lock ? the bootloader, if it is not possible?
Click to expand...
Click to collapse
Dude, crop out that serial number?

Go to download mode
Run adb:fastboot oem lock
Choose lock bootloader in your phone

namle98 said:
Go to download mode
Run adb:fastboot oem lock
Choose lock bootloader in your phone
Click to expand...
Click to collapse
confirmed, i did it today

Since I also unlocked critical, I ran: fastboot oem lock_critical and then fastboot oem lock
Phone will factory reset both times.

Has anyone tried the re-lock with a custom kernel/ROM?

dimitar10 said:
Has anyone tried the re-lock with a custom kernel/ROM?
Click to expand...
Click to collapse
No, and nobody should do it. It will brick your device.
The point of a locked bootloader is to prevent unofficial software from running, and the point of unlocking it is to make that possible. So relocking the bootloader with unofficial software installed will make the phone think that the software got corrupted and rightfully lock down the device.

THMSP said:
No, and nobody should do it. It will brick your device.
The point of a locked bootloader is to prevent unofficial software from running, and the point of unlocking it is to make that possible. So relocking the bootloader with unofficial software installed will make the phone think that the software got corrupted and rightfully lock down the device.
Click to expand...
Click to collapse
Basically anyone should be able to do it and it shouldn't brick your device, as per Google's bootloader recommendations. However, manufacturers decide to cripple bootloaders not to support it in the verified boot chain (where kernel verification can be explicitly made against a custom root of trust set after the device has left the factory i.e. set by the user, instead of the original root of trust). As far as I know, only Pixel devices implement this, and can be achieved by issuing the command:
Code:
fastboot flash avb_custom_key <key_blob>
I'm sure there are lots of advanced users/modders that can find this feature beneficial (if implemented by the device vendors).

dimitar10 said:
Basically anyone should be able to do it and it shouldn't brick your device, as per Google's bootloader recommendations. However, manufacturers decide to cripple bootloaders not to support it in the verified boot chain (where kernel verification can be explicitly made against a custom root of trust set after the device has left the factory i.e. set by the user, instead of the original root of trust). As far as I know, only Pixel devices implement this, and can be achieved by issuing the command:
Code:
fastboot flash avb_custom_key <key_blob>
I'm sure there are lots of advanced users/modders that can find this feature beneficial (if implemented by the device vendors).
Click to expand...
Click to collapse
I accidently locked the bootloader and without locking critical with custom recovery in system.
now it's saying data is corrupt and phone can't be trusted.
that unlock key url got expired and there is no way i can get that unlock key .
is there any other way to fix my phone??
Code:
fastboot flash avb_custom_key <key_blob>
how to use this code? any specific key_blob for nokia 8 or is it supported on this phone?
help me guys ;(
Edit:
After so many tries, I went to service centre and they fixed the phone in few mins :highfive::silly:

Crazy Tweaks said:
I accidently locked the bootloader and without locking critical with custom recovery in system.
now it's saying data is corrupt and phone can't be trusted.
that unlock key url got expired and there is no way i can get that unlock key .
is there any other way to fix my phone??
Code:
fastboot flash avb_custom_key <key_blob>
how to use this code? any specific key_blob for nokia 8 or is it supported on this phone?
help me guys ;(
Edit:
After so many tries, I went to service centre and they fixed the phone in few mins :highfive::silly:
Click to expand...
Click to collapse
I have the same problem right now. May i ask how they fixed it and what did you tell them ?
---------- Post added at 03:31 PM ---------- Previous post was at 03:27 PM ----------
CommieTurtle said:
I have the same problem right now. May i ask how they fixed it and what did you tell them ?
Click to expand...
Click to collapse
Did they fix it for free since bootloader is locked? I'm going to service centre in few hours

CommieTurtle said:
I accidently locked the bootloader and without locking critical with custom recovery in system.
now it's saying data is corrupt and phone can't be trusted.
that unlock key url got expired and there is no way i can get that unlock key .
is there any other way to fix my phone??
I have the same problem right now. May i ask how they fixed it and what did you tell them ?
---------- Post added at 03:31 PM ---------- Previous post was at 03:27 PM ----------
Did they fix it for free since bootloader is locked? I'm going to service centre in few hours
Click to expand...
Click to collapse
Well it wasn't in warranty xD so just asked me this and boom it was not free after that but well yeah it doesn't matter if it's locked or unlocked lol as long as they are getting paid, they'll do it hahahha

Crazy Tweaks said:
Well it wasn't in warranty xD so just asked me this and boom it was not free after that but well yeah it doesn't matter if it's locked or unlocked lol as long as they are getting paid, they'll do it hahahha
Click to expand...
Click to collapse
lol my device was under warranty so I got it fixed for free

I can assume that, in service centers, they are able to reflash the entire firmware including the (secondary) bootloader. They would probably boot the device into EDL mode, and flash it with stock firmware, with a properly signed Qualcomm EDL programmer, and use Qualcomm's QFIL tool to do this.

CommieTurtle said:
lol my device was under warranty so I got it fixed for free
Click to expand...
Click to collapse
Glad to hear that

[SODP][ROM][AOSP] SonyAOSP 13 [Alpha]

The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!
Official site
Unofficial site
Source Code
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
This is the AOSP ROM for the Sony Xperia XZ3 (akatsuki)
This ROM build will always mainly based on Sony AOSP Code and maybe include cherry-picks.
I plan to make monthly builds, after a new security patch level, if there is no need for a critical hotfix.
FAQ:
fastboot & adb
https://developer.sony.com/develop/open-devices/get-started/flash-tool/useful-key-combinations/
https://wiki.lineageos.org/adb_fastboot_guide.html
https://developer.android.com/studio/releases/platform-tools
Stuck at SONY logo? Maybe you need to flash the OEM binary to oem_a and oem_b, while just oem is not enough.
Bugtracker:
SODP Bugtracker -> If you think the problem is in SODP
My Bugtracker -> If you think the problem is in my implementation
Bugreport:
A bugreport needs
Code:
logcat -b all
and a way to reproduce the issue.
A crash of the system requires the content of the /sys/fs/pstore folder as bug report
Be aware that a second reboot erases this folder
A crash to the recovery partition requires additionally the content of the /dev/block/by-name/misc partition
You get the content via `cat /dev/block/by-name/misc partition > /path/to/output/file.txt`
To rescue a not responding phone:
VOLUP+POWER for 3 Seconds -> RESTART with one Vibration.
VOLUP+POWER for 20 Seconds -> SHUTDOWN with 3 Vibrations.
VOLUP+POWER+CAMERA for 30 Seconds -> HARDWARE SHUTDOWN by discharging a capacitor.
Thank you very much for your help, code contribution & testing! (Random order):
@jerpelea, the sony employees and their volunteers (people like you and me) coding this wonderful piece of software
@dhacke for providing a download server
And many thanks to the few donators!
A telegram group for technical SODP stuff:
https://t.me/xda_tv

Download & Installation
Download ROM:
Android File Host
FTP-Server from @dhacke
Download Drivers:
OEM (Tama) binaries
GCAM Camera App:
GCAM Issue
Suggested GCams
Installation with a recovery:
fastboot flash oem _a oem_*.img (Only needed until the device receives mainline support by SODP)
Flash the ROM in a recovery
Reboot into recovery just to make sure you're on the new slot
OpenGapps (Requires TWRP or a custom ROM recovery)
Dual Sim Patcher (Requires TWRP or a custom ROM recovery)
(In case a modification prevents your device from booting) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Flash the ROM without a recovery:
Extract the payload.bin from the .zip file
Extract the .img files with the Playload Dumper
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot -w (Wipes your internal storage and the userdata; only if needed)
Now you got the AOSP recovery, to please continue with the normal installation
fastboot flash oem_a oem_*.img (Only needed until the device receives mainline support by SODP)
fastboot flash vendor vendor.img
fastboot flash system system.img

News
07.10.2022
android-13.0.0_r7 (October security patchlevel)
Click to expand...
Click to collapse
OTA.zip generation is working again
Click to expand...
Click to collapse
08.09.2022
android-13.0.0_r4 (September security patchlevel)
Click to expand...
Click to collapse
06.09.2022
android-13.0.0_r1 (August security patchlevel)
Click to expand...
Click to collapse

Hi MartinX3!
Thank you for your work!
I've tried to install this rom on my h9493 and it was bootloop. When it turns on only unlocked bootloader icon showing and after it only black screen. I did everything according to your instructions. But with the project on android 12.1 the situation is exactly the same.
Unfortunately, logcat is empty
Please feel free to contact me for any testing

nikonsok said:
Hi MartinX3!
Thank you for your work!
I've tried to install this rom on my h9493 and it was bootloop. When it turns on only unlocked bootloader icon showing and after it only black screen. I did everything according to your instructions. But with the project on android 12.1 the situation is exactly the same.
Unfortunately, logcat is empty
Please feel free to contact me for any testing
Click to expand...
Click to collapse
adb connection works? how can the logcat be empty?
What about the pstore?
12.1 did boot, maybe you need the newest stock 10 booted to the app screen once?
and maybe you flashed the oem wrong?
The new oem for A13 should appear this or next week.

I managed to make a system log!
log.txt
drive.google.com

Hello MartinX3! Thank you for putting your effort to develop this firmware. I've akatsuki (SOV-39 variant). Bootloader can't be unlocked. My question is simple, can I flash your firmware?

JD_9 said:
JD_9 said:
Hello MartinX3! Thank you for putting your effort to develop this firmware. I've akatsuki (SOV-39 variant). Bootloader can't be unlocked. My question is simple, can I flash your firmware?
Click to expand...
Click to collapse
no
Hello MartinX3! Thank for putting your effort to develop this firmware. I've akatsuki (SOV-39 variant). Bootloader can't be unlocked. My question is simple, can I flash your firmware?
Click to expand...
Click to collapse

JD_9 said:
Hello MartinX3! Thank you for putting your effort to develop this firmware. I've akatsuki (SOV-39 variant). Bootloader can't be unlocked. My question is simple, can I flash your firmware?
Click to expand...
Click to collapse
no

JD_9 said:
Hello MartinX3! Thank you for putting your effort to develop this firmware. I've akatsuki (SOV-39 variant). Bootloader can't be unlocked. My question is simple, can I flash your firmware?
Click to expand...
Click to collapse
Short answer:
No as long your bootloader is locked.
Long answer:
You won't be able to flash any rom without unlocking the bootloader. I come from sov39 as well, docomo phone bootloader can't be unlock through normal way. I gave up struggling to find ways to unlock it and pay for unlock tools to unlock the bootloader.
I would suggest to just use stock rom, the price for the tool is almost half the price of my xz3 when I bought it.
Find a reliable seller for the tool if you wish to proceed.
P.S. Dun ask me source, I don't want to hold any responsibility on it.
¯⁠\⁠_⁠ಠ⁠_⁠ಠ⁠_⁠/⁠¯

xanlimit said:
Short answer:
No as long your bootloader is locked.
Long answer:
You won't be able to flash any rom without unlocking the bootloader. I come from sov39 as well, docomo phone bootloader can't be unlock through normal way. I gave up struggling to find ways to unlock it and pay for unlock tools to unlock the bootloader.
I would suggest to just use stock rom, the price for the tool is almost half the price of my xz3 when I bought it.
Find a reliable seller for the tool if you wish to proceed.
P.S. Dun ask me source, I don't want to hold any responsibility on it.
¯⁠\⁠_⁠ಠ⁠_⁠ಠ⁠_⁠/⁠¯
Click to expand...
Click to collapse
It's not worth unlocking the XZ3 now. I'll use it with the stock firmware. Sony's version of Android 10 is just bad and even slower than heavily bloated firmware such as OneUI. That's why I wanted to try a different OS. Anyway, thanks for the reply!

JD_9 said:
It's not worth unlocking the XZ3 now. I'll use it with the stock firmware. Sony's version of Android 10 is just bad and even slower than heavily bloated firmware such as OneUI. That's why I wanted to try a different OS. Anyway, thanks for the reply!
Click to expand...
Click to collapse
why not root remove bloatware install and install some handy magisk module, that's what i use to run before i flash android 12

Alex5699 said:
why not root remove bloatware install and install some handy magisk module, that's what i use to run before i flash android 12
Click to expand...
Click to collapse
Wait, is there a way to root SOV39 without tampering with the bootloader? There's a way IK of but it's a temporary root solution which will phase out after rebooting the phone. I've removed all of the bloatware using adb shell. So, for me it's not worth paying $30. Don't you agree?

well my bl is unlocked and im also using a sov39 ( bought it unlock off ebay ) .
cant you root it using magisk ? get the stock boot.img patch it using magisk and then fastboot flash boot.img in the system ?? should work on lock bl. please correct me if im wrong as i know there is a way to root even if your bl is locked

JD_9 said:
Wait, is there a way to root SOV39 without tampering with the bootloader? There's a way IK of but it's a temporary root solution which will phase out after rebooting the phone. I've removed all of the bloatware using adb shell. So, for me it's not worth paying $30. Don't you agree?
Click to expand...
Click to collapse
i wish my bl wasnt unlock my camera suck now

Is there anyway to build sodp for sov39 ?

May I ask if the Rom has livedisplay ?

MartinX3 is this stable for daily use?​

07.10.2022
android-13.0.0_r7 (October security patchlevel)
Click to expand...
Click to collapse
OTA.zip generation is working again
Click to expand...
Click to collapse

MartinX3 said:
07.10.2022
Click to expand...
Click to collapse
I can't find new OTA version. I see only old SW_BINARIES_FOR_XPERIA_ANDROID_12_4.19_V3A_TAMA (updated date 27 July).
Is it the correct version?