Develop Bugs

[LWX49K&LDZ22D&LCA43] Rooting made easy

I'm not believing my eyes just yet, but honestly...
Want root? Well, then I have some good news for you:
THERE IS NO REASON TO UNLOCK YOUR BOOTLOADER TO ROOT YOUR SMARTWATCH 3!
The fastboot mode is available on locked bootloader...
And the best news I can come up with right now? It allows hot booting custom kernels! :victory:
Code:
~$ adb reboot bootloader
~$ fastboot oem unlock
...
(bootloader) : WARNING: Unlocking your device will void your warranty
(bootloader) : and erase your personal data from the device.
(bootloader) : Run "fastboot oem unlock" again to confirm.
(bootloader) : Device still locked.
OKAY [ 0.008s]
finished. total time: 0.008s
~$ fastboot reboot
rebooting...
finished. total time: 0.001s
~$ adb shell
[email protected]:/ $ su
[email protected]:/ #
I can't believe it myself, but it's TRUE! :victory:
I have rooted my device using the TWRP from this thread, this is what I did:
Made sure I had the developer options enabled;
Enabled the ADB debugging option;
Made sure the device accepted my PC as authorized;
download the TWRP image from this thread (for 5.0.2) or from this post (for 5.1.1);
Download Wear-SuperSU-v2.46.zip;
adb reboot bootloader, saw it actually boot to fastboot... this is how I looked at that time: http://images.sodahead.com/polls/001047815/gobsmacked-15792349304_xlarge.jpeg;
fastboot boot unofficial-twrp-2.8.3.0-tetra.img (incredibly I saw it boot TWRP! Well... this is like the face my colleagues where watching me pull at that moment: http://mcp53.files.wordpress.com/2012/11/gobsmacked.jpg?w=500);
adb push Wear-SuperSU-v2.46.zip /sdcard/ (installed the zip in recovery);
Reboot to system from TWRP;
Did root test;
Was seriously gobsmacked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm investigating the possibility to have recovery on the locked device right now, which is actually something I did for many Xperia Z series devices already :angel:

What can we make of new after this?

Elpatii said:
What can we make of new after this?
Click to expand...
Click to collapse
Well, the good thing is, you can have root while you won't lose your warranty. Because unlocking bootloader === lost warranty.
What else we can do, the sky is basically the limit... or, the resolution is, of course

[NUT] said:
Well, the good thing is, you can have root while you won't lose your warranty. Because unlocking bootloader === lost warranty.
What else we can do, the sky is basically the limit... or, the resolution is, of course
Click to expand...
Click to collapse
Oh nice!
And with root in this Smartwatch, what do you think that we can make of more?

Elpatii said:
Oh nice!
And with root in this Smartwatch, what do you think that we can make of more?
Click to expand...
Click to collapse
Well, one of the things we might be able to do is create an app or a ROM modification, which will run on the phone smartwatch itself, allowing you access to the internal storage by USB cable, because that's not possible without a phone right now. Knowing Google, it was done by design, but it won't be hard to update the ROM to allow access to the internal storage through USB.
I'll be trying to get a recovery working on the device without overwriting the one in the recovery partition, which should then allow us to easily flash ROM modifications.

[NUT] said:
Well, one of the things we might be able to do is create an app or a ROM modification, which will run on the phone smartwatch itself, allowing you access to the internal storage by USB cable, because that's not possible without a phone right now. Knowing Google, it was done by design, but it won't be hard to update the ROM to allow access to the internal storage through USB.
I'll be trying to get a recovery working on the device without overwriting the one in the recovery partition, which should then allow us to easily flash ROM modifications.
Click to expand...
Click to collapse
Oh yeah, it's would be nice!
Continue to share your discovery

[NUT] said:
Well, the good thing is, you can have root while you won't lose your warranty. Because unlocking bootloader === lost warranty.
What else we can do, the sky is basically the limit... or, the resolution is, of course [emoji14]
Click to expand...
Click to collapse
Dude Great to see you here, i am very excited now as our SW3 will go in right direction, i have Asked Jerpelea about the Development of SW3 and he said it will start soon.
Also its a request Plz make a custom Kernel for this watch to Calibrate the Colors saturation and Gamma as its same yellowish Display as Honami had.

abbychauhan said:
Dude Great to see you here, i am very excited now as our SW3 will go in right direction, i have Asked Jerpelea about the Development of SW3 and he said it will start soon.
Also its a request Plz make a custom Kernel for this watch to Calibrate the Colors saturation and Gamma as its same yellowish Display as Honami had.
Click to expand...
Click to collapse
+1
Sent from my Xperia Z3

Is there a way to unlock the kernel and all four cores in the processor on latest LDZ22D build for Smartwatch 3?

[NUT] said:
I'm not believing my eyes just yet, but honestly...
Click to expand...
Click to collapse
Thanks for sharing your discovery!
I wrote an article that explores the bootloader vulnerability: http://spectrastudy.com/no-data-protection-on-sony-smartwatch-3-android-wear/
An Android Wear dev advocate at Google is now informed of it, it really should be fixed as it makes stealing data far too easy.

[NUT] said:
I'm not believing my eyes just yet, but honestly...
Want root? Well, then I have some good news for you:
THERE IS NO REASON TO UNLOCK YOUR BOOTLOADER TO ROOT YOUR SMARTWATCH 3!
The fastboot mode is available on locked bootloader...
And the best news I can come up with right now? It allows hot booting custom kernels! :victory:
Click to expand...
Click to collapse
Hi ive been trying to work this out above you said that there is away to root the watch on locked bootloader could you explain how? I can get into fastboot but theres no way to install TWRP on locked bootloader how would I flash the superuser zip on locked bootloader. Can it be done? Your method you explained is an unlocked bootloader method and with the stock recovery you can only sideload update.zips correct me if im wrong. Can you please explain the locked bootloader method??? Can it not be done on the latest build LCA43???

RJASSI21 said:
Hi ive been trying to work this out above you said that there is away to root the watch on locked bootloader could you explain how? I can get into fastboot but theres no way to install TWRP on locked bootloader how would I flash the superuser zip on locked bootloader. Can it be done? Your method you explained is an unlocked bootloader method and with the stock recovery you can only sideload update.zips correct me if im wrong. Can you please explain the locked bootloader method??? Can it not be done on the latest build LCA43???
Click to expand...
Click to collapse
fastbooting hotboot only. no flashing of custom recovery. only flash wear supersu after hotbooting.
˜xperia z3,d6653,5.1.1,v71,tapatalk

jemfalor said:
fastbooting hotboot only. no flashing of custom recovery. only flash wear supersu after hotbooting.
˜xperia z3,d6653,5.1.1,v71,tapatalk
Click to expand...
Click to collapse
Ok thanks for that
---------- Post added at 03:00 AM ---------- Previous post was at 02:28 AM ----------
jemfalor said:
fastbooting hotboot only. no flashing of custom recovery. only flash wear supersu after hotbooting.
˜xperia z3,d6653,5.1.1,v71,tapatalk
Click to expand...
Click to collapse
Just one other thing how can I check I have successfully rooted my device?

sideload an app and use its root feature. es explorer or terminal emulator
˜xperia z3,d6653,5.1.1,v71,tapatalk

RJASSI21 said:
Ok thanks for that
---------- Post added at 03:00 AM ---------- Previous post was at 02:28 AM ----------
Just one other thing how can I check I have successfully rooted my device?
Click to expand...
Click to collapse
jemfalor said:
sideload an app and use its root feature. es explorer or terminal emulator
˜xperia z3,d6653,5.1.1,v71,tapatalk
Click to expand...
Click to collapse
Or use ADB Shell to use the su command to gain root access.

[NUT] said:
Or use ADB Shell to use the su command to gain root access.
Click to expand...
Click to collapse
Ok thank you both the root features in es are very limited so its hard to tell I will try the su command later on thanks for that NUT
Edit: I did try TWRP on the latest firmware in the end LCA43 and it was successful im still yet to see if root was successful I dont have a superuser app is this normal?

This all works on the latest Android Wear build as well

RJASSI21 said:
Ok thank you both the root features in es are very limited so its hard to tell I will try the su command later on thanks for that NUT
Edit: I did try TWRP on the latest firmware in the end LCA43 and it was successful im still yet to see if root was successful I dont have a superuser app is this normal?
Click to expand...
Click to collapse
Yes, there is no app for wear (yet).

karl0ss said:
This all works on the latest Android Wear build as well
Click to expand...
Click to collapse
I will update the OP and subject after I confirmed it myself...

[NUT] said:
Or use ADB Shell to use the su command to gain root access.
Click to expand...
Click to collapse
Hi I dont think my smartwatch is rooted I ran the command but it just prints nothing I also tried system app mover app but it just keeps showing the looking for root message I cant grant root how do I do this I flashed the zip 4 times and moved it over twice what am I doing wrong?

Repair HTC One M9

Hey,
I have set S-ON through fastboot, and have a relocked bootloader. I cannot enter recovery ("failed to boot to recovery mode. Press volume up or down to back to menu"). I cannot boot to my OS, because it is stuck to bootloop (wanted to install xposed arm).
Firmware is 2.10.401.1 and Android 5.1.
So I cannot flash unlocktoken with fastboot, because it is not enabled in developer settings.
How do I repair this phone?
Thanks in advance for any help.

Try installing the twrp again using fastboot. Then restore or uninstall xposed maybe?
Also go to lollipop xposed thread, they have multiple files and uninstaller there so make sure you get the right one. For me it's sdk21 64 bit.
(I'm just an average consumer so it's up to you if you'd give this a try.)
Edit: I missed the point where you got a relocked bootloader. Idk the solution to that though.

I can now boot to my OS.
So in order to run sunshine I need to uninstall xposed.
Can I uninstall xposed from there?
Any flashing app? Flash Gordon does not uninstall xposed.
Other idea is to restore nandroid backup via nandroid manager. But this says "Warning: This recovery is a partial backup. It is recommended that you restore this backup via your recovery because some recoveries are not able to restore partial backups". Is that safe, because the warning supposes not.
It is "HIMA_UHL_TWRP_Nandroid_2.10.401.1" from the internet.
Edit: Or should I wait for RUU and flash original recovery and RUU from flashify?

They have uninstaller zips in the xposed lollipop thread.

You need SDK22 64bit by rom racer... Or The 64bit uninstaller in the original thread.

Thanks. But how do I run the uninstaller? I cannot boot to recovery.

Ok, problem solved.
Here's what I did: Since I enabled bootloader unlock in developer settings, I forgot to generate a new unlock_code. With the new code from HTCdev I was able to unlock bootloader and boot to recovery.
Thanks to everyone who helped in this and all other threads!

How did you get a new unlock_code?
I error, with cmd
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

nerlim said:
How did you get a new unlock_code?
I error, with cmd
Click to expand...
Click to collapse
@nerlim: I also used cmd.
When you're running Android 5.1 please make sure that oem unlocking is enabled in developer settings.
Is bootloader locked or relocked?
I assume you have S-On?

Simon_TB said:
@nerlim: I also used cmd.
When you're running Android 5.1 please make sure that oem unlocking is enabled in developer settings.
Is bootloader locked or relocked?
I assume you have S-On?
Click to expand...
Click to collapse
The smartphone does not start .Stuck screen fastboot
I can not access the os
there is a way to do it with cmd enabled in developer settings?

nerlim said:
The smartphone does not start .Stuck screen fastboot
I can not access the os
there is a way to do it with cmd enabled in developer settings?
Click to expand...
Click to collapse
Please give us more information, so we can help you better:
Bootloader locked/relocked?
Which Firmware?
What ROM installed?
What Recovery installed?
Can you start Recovery?

No, it does not start in recovery

Sorry for the late reply.
Unfortunately I don't know a way of how to set the enable unlock flag via fastboot. If you're able to do so, please let us know how. Then get a new unlock_token and after you unlocked the bootloader flash twrp.
If this is not possible you should flash RUU. Your version isn't published yet. However you could try the previous RUU. This might cause problems with your firmware. You're responsible for what you do!
Otherwise I don't see any other option than wait for a new RUU.
Btw: What have you done to your device? No unlocked bootloader and S-ON... Looks like no major changes from your side.

Did you ever figure out how to fix your phone?
I also have my phone "LOCKED with S-ON", can't access it with USB programming, and its stuck in a Boot loop.

i had this problem too
all i did was :ENTER RECOVERY MODE MANUALLY
even thou the phone goes there automatically, when in the "automatic" recovery mode go to reboot, press select(power) then hold down volume and it should reboot into recovery mode(it looks a bit different from the one you're on now) and then you can unlock your bootloader again
i was looking for a solution too because i couldn't go to developer mode because the phone kept rebooting in recovery mode so i decided to play with the buttons a bit
that's how it worked in my case just a moment ago

need to get root w/o losing data

Hi, guys, I'm on an HTC 10 with Stock Oreo, I need to install root so I can recover deleted text messages, the problem I am having is that I cannot install TWRP without using HTC DEV and HTC DEV wipes the phone. If anyone has a workaround I need it badly

Mozze3291 said:
Hi, guys, I'm on an HTC 10 with Stock Oreo, I need to install root so I can recover deleted text messages, the problem I am having is that I cannot install TWRP without using HTC DEV and HTC DEV wipes the phone. If anyone has a workaround I need it badly
Click to expand...
Click to collapse
If your software is old enough (Marshmallow) you would be able to s-off with Sunshine without unlocking your bootloader, and then root the device. You'd have to pay $25 for it in that case.
The only other option I can think of is to ask the Sunshine team if they'd be able to manually s-off your phone without wiping it. That would require you to mail them your device (and pay the $25), so it depends on how desperate you are. You'd have to ask them if that's even possible.
Else, not much you can do.

Tarima said:
If your software is old enough (Marshmallow) you would be able to s-off with Sunshine without unlocking your bootloader, and then root the device. You'd have to pay $25 for it in that case.
The only other option I can think of is to ask the Sunshine team if they'd be able to manually s-off your phone without wiping it. That would require you to mail them your device (and pay the $25), so it depends on how desperate you are. You'd have to ask them if that's even possible.
Else, not much you can do.
Click to expand...
Click to collapse
So I checked this phone I bought it off swappa and havent really looked at it much. The phone is S-Off and it is running oreo also I believe it says the bootloader is unlocked, but im not sure if the unlocked part just means that it has been sim unlocked

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

my htc 10 bootloader

Having trouble posting the image
<img src="https://thumb.ibb.co/d4jqzx/CYMERA_20180407_101106.jpg" alt="CYMERA_20180407_101106" border="0">

Mozze3291 said:
Having trouble posting the image
<img src="https://thumb.ibb.co/d4jqzx/CYMERA_20180407_101106.jpg" alt="CYMERA_20180407_101106" border="0">
Click to expand...
Click to collapse
Your bootloader being unlocked is not related to sim/network unlocking. The bootloader was unlocked prior to the s-off process. You can leave it as it is.

Woot best news I have heard all day. Will installing twrp erase any data on the phone?

Mozze3291 said:
Woot best news I have heard all day. Will installing twrp erase any data on the phone?
Click to expand...
Click to collapse
No.

So I have gotten TWRP installed and I cannot for the life of me get SuperSU installed. I tried to install Magisk first and it failed or it's on there and does nothing. I have followed a few different videos but for whatever reason I cannot get SUperSu to install. Any ideas? I have tried installing from TWRP and also tried installing from adb sideload both "worked" but no SU Icon and no root?

Solved the Issue, I stopped trying to install SuperSu and did an adb sideload of Magisk and got Root. Thanks guys for all your help

Hi to all,
I would like to know how to root HTC without wipe and losing any data.
Thank you very much to all.
Enrico

EnricoTV said:
Hi to all,
I would like to know how to root HTC without wipe and losing any data.
Thank you very much to all.
Enrico
Click to expand...
Click to collapse
You cant, when you unlock the bootloader to be able to flash TWRP all data will be wiped. No choice there.

Mr Hofs said:
You cant, when you unlock the bootloader to be able to flash TWRP all data will be wiped. No choice there.
Click to expand...
Click to collapse
Thanks for the answer...so... are there any solutions to recover deleted photos and pictures without root my htc10? I tried some app but nothing to do...

EnricoTV said:
Thanks for the answer...so... are there any solutions to recover deleted photos and pictures without root my htc10? I tried some app but nothing to do...
Click to expand...
Click to collapse
No idea never needed to use any so can't give any insight on that. I always use Google photos with cloudsync or onedrive. Works great and no worries about lost pictures.

Already S-off and bootloader unlocked. How to get root without erasing data?

w69 said:
Already S-off and bootloader unlocked. How to get root without erasing data?
Click to expand...
Click to collapse
Flash magisk

Question Downgrade to Android 12

I'm having issues trying to downgrade to Andriod 12 from andriod 13 beta 3.
1. I've opted out of Beta
2. Software update notification received
3. Click on download and install
4. After a couple of mins get error message couldn't update 'Installation problem'
The screen remains on the update screen.
What am i doing wrong please help?
Device state: locked
edit:actually now I'm stuck in Fastboot Mode
Phone keeps rebooting back to Fastboot mode

With a locked bootloader, your only option to get fixed is to try sideloading an OTA - usually, the OTA has to be either the same as what you were most recently running or newer. Click the yellow How To Guide quick filter at the top of the list of threads for one of the root guides. Even though you're not rooting, one or two of them should tell how to sideload an OTA - just ignore things that reference root.
This is why the instructions for the Beta program say you should have an unlocked bootloader, as without an unlocked bootloader your choices to fix the situation are much more limited.

roirraW edor ehT said:
With a locked bootloader, your only option to get fixed is to try sideloading an OTA - usually, the OTA has to be either the same as what you were most recently running or newer. Click the yellow How To Guide quick filter at the top of the list of threads for one of the root guides. Even though you're not rooting, one or two of them should tell how to sideload an OTA - just ignore things that reference root.
This is why the instructions for the Beta program say you should have an unlocked bootloader, as without an unlocked bootloader your choices to fix the situation are much more limited.
Click to expand...
Click to collapse
thanks for that, any advice on how to ota pls?
Can't find any instructions sorry.

riz157 said:
thanks for that, any advice on how to ota pls?
Click to expand...
Click to collapse
You're welcome. Since I never do the OTA process, I always flash the full firmware zip (which you can't do with a locked bootloader), I can't advise any further than what I said about using the quick filter for the How To Guides. At least one or two of these threads should help you, although they may concentrate on doing so with rooting, as long as you ignore the root parts to the OTA method, you can still follow the instructions. You'll get better help to any questions in one of the threads that give OTA sideload instructions:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

roirraW edor ehT said:
Yo
You're welcome. Since I never do the OTA process, I always flash the full firmware zip (which you can't do with a locked bootloader), I can't advise any further than what I said about using the quick filter for the How To Guides. At least one or two of these threads should help you, although they may concentrate on doing so with rooting, as long as you ignore the root parts to the OTA method, you can still follow the instructions. You'll get better help to any questions in one of the threads that give OTA sideload instructions:
View attachment 5642011
Click to expand...
Click to collapse
much appreciated yes want to avoid root or unlocking the bootloader, why does google have it to make it so difficult to downgrade. Maybe take a leaf out of apple's book

To sideload you need USB debugging enabled. Reboot the device to recovery, either by powering off the device and holding power and volume up, let go of power when the phone vibrates, on the the android with an exclamation mark, tap on volume up I think it is. Or by typing in terminal
Code:
fastboot reboot recovery
since it's stuck in fastboot. In recovery tap on 'apply update from adb'
Then download the ota package from here.
Grab the platform tools (Google for it) and unzip it to c:\platform-tools if you're running windows. Open a terminal in the platform tools folder and type
Code:
adb sideload /path_to_ota.zip
Let it do its thing and you should be up and running. I wouldn't try to downgrade from the a13 beta, but you can try. Good luck!

riz157 said:
thanks for that, any advice on how to ota pls?
Can't find any instructions sorry.
Click to expand...
Click to collapse
Just a few things. You don't need USB debugging enabled for OTA updates (you can't boot into Android to enable it anyway).
Just be aware that with OTA's, you can't downgrade - only reinstall the same version or upgrade, so you need to make sure you're on Android 13 to reinstall ota version 13 (recovery mode will tell you your version).
Here's a video to help with the ota update.

riz157 said:
I'm having issues trying to downgrade to Andriod 12 from andriod 13 beta 3.
1. I've opted out of Beta
2. Software update notification received
3. Click on download and install
4. After a couple of mins get error message couldn't update 'Installation problem'
The screen remains on the update screen.
What am i doing wrong please help?
Device state: locked
edit:actually now I'm stuck in Fastboot Mode
Phone keeps rebooting back to Fastboot mode
Click to expand...
Click to collapse
Any luck with your device?

Alekos said:
Any luck with your device?
Click to expand...
Click to collapse
No luck finally contacted Google who will have this sorted.

riz157 said:
No luck finally contacted Google who will have this sorted.
Click to expand...
Click to collapse
What happened with the OTA updates? Did it complete? Getting the windows driver and fastboot/adb (platform-tools) to all work can be tricky..

what about the https:// flash.android .com/build/8151327?target=raven-user&signed=true Website?

jlede18 said:
what about the https:// flash.android .com/build/8151327?target=raven-user&signed=true Website?
Click to expand...
Click to collapse
Flash.android uses fastboot, which requires the bootloader to be unlocked. User can't unlock it since Android won't boot..

I don't think I'll be flashing beta version again lol, too much hassle to downgrade.
In the end decided to send in to Google to repair.
I think they will give me a replacement instead of repairing it.
Did anyone notice any major bugs with android 13, can't say I did?

Alekos said:
What happened with the OTA updates? Did it complete? Getting the windows driver and fastboot/adb (platform-tools) to all work can be tricky..
Click to expand...
Click to collapse
Decided against that, off to Google to fix

Alekos said:
Flash.android uses fastboot, which requires the bootloader to be unlocked. User can't unlock it since Android won't boot..
Click to expand...
Click to collapse
Copy that. Would of probably just been easier to reflash the beta back save everything, unlock the bootloader and then flash android 12

jlede18 said:
Copy that. Would of probably just been easier to reflash the beta back save everything, unlock the bootloader and then flash android 12
Click to expand...
Click to collapse
Yup, very easy to flash ota, but op didn't feel comfortable doing it unfortunately.

Might seem dumb but I used the web browser tool and flashed back to stock via that from 13 B3 it unlocks bootloader and flashes and re locks bootloader , back on stable 12 working fine then opted out of 13 beta

The way I did it was downloading the entire firmware from google and then changing the config to remove- w so your data doesn't get wiped. Then running the .su or .bat depending on your is. It worked for me. Cheers

Question how to relock bootloader rog 6 ?

if using qualcomm tools it need mbn file . i cant find that mbn file in the firmware folder . urgent hlp

fastboot oem asus-csc_lk

Andrologic said:
fastboot oem asus-csc_lk
Click to expand...
Click to collapse
Command not working

AmeNahar said:
Command not working
Click to expand...
Click to collapse
How is it not working? What do you get?

Andrologic said:
How is it not working? What do you get?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

AmeNahar said:
View attachment 5831065
Click to expand...
Click to collapse
Wrong fastboot. Do it from the bootloader page: 'fastboot reboot bootloader' or just turn on the device in bootoader mode without navigating to fastboot/fastbootd. Then use the same command. Should help.

Andrologic said:
Wrong fastboot. Do it from the bootloader page: 'fastboot reboot bootloader' or just turn on the device in bootoader mode without navigating to fastboot/fastbootd. Then use the same command. Should help.
Click to expand...
Click to collapse
i got <waiting for device> (side charger port) .can u give the actuall usb device driver ? if using fastbootd can detect . but from fastboot reboot bootloader just waiting for device

AmeNahar said:
i got <waiting for device> (side charger port) .can u give the actuall usb device driver ? if using fastbootd can detect . but from fastboot reboot bootloader just waiting for device
Click to expand...
Click to collapse
Same problem did you find any solution?!

I just found the solution
You should use side usb port for update just connect to the pc reboot to fast boot and run the command

havard20009 said:
I just found the solution
You should use side usb port for update just connect to the pc reboot to fast boot and run the command
Click to expand...
Click to collapse
cool. sorry for late reply.. my solution is change the usb cable ..i always use side port btw ..i flashed raw and flash A13 now . bcs i want to play new state(not working on rooted devices and bootloader unlocked) . thats the reason why im relocking my bootloader

*deleted.

Does relock the bootloader on official rom will give error and need to flash official rom again?
I want to root my Batman edition but scared it will give bootloop after relock bootloader in future. As the Batman official rom is never be found on the net, I would lose the Batman theme if flashed to normal version.

deddo86 said:
Does relock the bootloader on official rom will give error and need to flash official rom again?
I want to root my Batman edition but scared it will give bootloop after relock bootloader in future. As the Batman official rom is never be found on the net, I would lose the Batman theme if flashed to normal version.
Click to expand...
Click to collapse
It may give you a device corrupt error after re-lock that requires a factory reset or RAW flash meaning you may risk losing your Batman stuff - whatever that is. Best to root and leave it unlocked (you can still unroot it), or leave it alone...

Andrologic said:
It may give you a device corrupt error after re-lock that requires a factory reset or RAW flash meaning you may risk losing your Batman stuff - whatever that is. Best to root and leave it unlocked (you can still unroot it), or leave it alone...
Click to expand...
Click to collapse
The only reason I want to root it to take out the Batman theme. It's in Zip file inside the Asus Theme folder, I can extract it but all files are unreadable. Where's photos and videos are in .enc format and APKs cannot be open, even changed to .zip format.
It seems all Asus themes are like this not only for Batman theme. So my plan is to root it and take out the theme that may be inside System folder that only can be reach via root. Then relock the bootloader before selling it later.

deddo86 said:
The only reason I want to root it to take out the Batman theme. It's in Zip file inside the Asus Theme folder, I can extract it but all files are unreadable. Where's photos and videos are in .enc format and APKs cannot be open, even changed to .zip format.
It seems all Asus themes are like this not only for Batman theme. So my plan is to root it and take out the theme that may be inside System folder that only can be reach via root. Then relock the bootloader before selling it later.
Click to expand...
Click to collapse
Or unlock it and take a full system image backup with TWRP or something else and keep it stored. That way you can roll back and re-lock in case you want to sell the device one day.
You could also switch your active slot and leave one with the Batman theme on the inactive, but need to be very careful not to overwrite the Batman slot. Requires strickt manual management of where system updates are installed. Not recommended but possible.

AmeNahar said:
cool. sorry for late reply.. my solution is change the usb cable ..i always use side port btw ..i flashed raw and flash A13 now . bcs i want to play new state(not working on rooted devices and bootloader unlocked) . thats the reason why im relocking my bootloader
Click to expand...
Click to collapse
Excuse me can you share the raw file link and version information?

sorankira said:
Excuse me can you share the raw file link and version information?
Click to expand...
Click to collapse
sorry for late reply...the links and info availble on rog 6's forum

sorankira said:
Excuse me can you share the raw file link and version information?
Click to expand...
Click to collapse
[TOOL] RAW Firmware for ROG Phone 6 - can be used for CN -> WW converting
Too many people are trying to use firmware to make money, so I decided to release them for free! I got them from a site that distributes them for $10. DOWNLOAD Password is: https://androplus.org How to flash: Plug the USB Type-C cable into the...
forum.xda-developers.com

Can i relock and unlock after?

Effizio01 said:
Can i relock and unlock after?
Click to expand...
Click to collapse
Yes. I already 3 times unlock .root and relock bootloader