is it possible to relock bootloader while using custom rom and recovery installed ?
i am asking this because it will make phone more secure while running it on custom recovery as all of us know how to remove screen lock with use of custom recovery
put password on recovery so no one can open it and if we relock bootloader then no one can reflash recovery in it and then there will less chance that our data may get out from phone or can be used if it get stolen or lost.
I am also trying to get rid of the annoying bootloader prompt that says the security of the device might have been compromised....
Please explain how...
Yes i have already flashed the device.
No. Just no.
If you want to brick your phone, just do it.
No, unlocking the bootloader is what allows you to run a custom ROM, that's why the phone is okay with it being custom. You can't just delete a password if you have an encrypted data partition.
Locked bootloaders only accept roms from vendor by certificate.
So If you lock is you will brick your device.
Not sure if hardbrick tools will work...?
This does kind of exist for the OnePlus 5T; see here. It is quite complex, but once you have root under a locked bootloader you can reflash everything (with SIGNED recoveries and boot images). If you fail to sign everything correctly your phone will become more bricked than usual, with no possibility of reflashing except using the MSM Download Tool.
However, before you get any ideas, hold on. The OnePlus 7 is not only an A/B device, but a system-as-root device, neither of which the 5T is. There is no recovery partition that you can easily overwrite. I believe it's still possible to get a twrp-installer zip to do your bidding, if you're able to get Magisk correctly with a locked bootloader. And before you ask, I don't know if it's possible to sign the boot.img with Magisk/TWRP already installed.
This is all pure speculation on my part and I've yet to try any of this with my 7 Pro. I know that no matter what happens, I can always use MSM Download Tool to restore my phone to working software. Then I'll have to start over, installing Magisk and then TWRP to restore my backup. I'm waiting for more input on this from people who know what they are doing, before attempting anything myself.
This was possible on the Redmi Note 3 pro. Someone created a mod where you could flash recovery directly using the MiFlash tool (Xiaomi's equivalent of MSTOOL). This was great because I had a locked bootloader and used orange fox recovery to lock the recovery... A theoretically fully secure rooted device
The anwser is no. You can try it like I did but it will tell you you have to format the device. I just learned the button combo. Thats what my problem was. Everytime I wanted to restart my phone I would always forget to shutdown completly because you have to do the button combo to enter rooted state. I just got used to it.
Edit: but I did manage to stop upgrade to the ugly Andriod 11 and managed to get my gear sport to work on my rooted rom. Thats all I wanted was Call recorder and for my watch to work.
So far no,I have been working on it and rebuilt a ops file with patched boot.and get this new error lol. If any one knows what I should try let me know. I am able to fully unpack and repack the ops files and flash.have been able to disable quite a few checks in the flashing with MSM tool.
{
"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"
}
Related
Hello everyone.
PROBLEM : Not booting up to the Android lock-screen
DEVICE INFO :
Phone Model : Moto G XT 1033 Dual SIM (India)
No Root.Bootloader is UNLOCKED.No customizations.
ADB Debugging disabled (default).
Moto G XT1033(Black, 16 GB)
Using : Android Lollipop (the latest update done by OTA as part of System Update)
Upgraded : 2-3 weeks after the update was released.
Info from Motorola Device Manager
Current version:N/A
What happened:
Phone ran outta charge at 0%.
Plugged it in,on restarting,after the usual startup animation,I was greeted by a dead screen ,much to my horror.
Like this:
{
"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"
}
Tried a hard reset and several reboots.nothing worked.
I can access:
The bootloader
The recovery mode
Also put in CWM (without touch)
ADB is able to recognise the device.
P.S: My case was exactly that of @ravibhat here in this thread:http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492
Initially,my bootloader was locked and everytime I tried recovery it kept saying "boot failed" ,just like in ravi's case.
I unlocked the bootloader using the Motorola website and installed CWM after reading up on it.
Tried flashing stock firmware but in vain.
Went to the service center where I was told my phone has a motherboard defect and needs to be replaced( which I do not believe).
What I want:
My phone restored to normalcy.
Losing data is not an issue.
Bootloader image:
MotoG Bootup Problem - Recovery Mode failed
i have same problem in Moto G XT1033 Dual SIM ( Android Lollipop )
i haven't done anything in phone
I want My phone restored to normalcy
@spanda12 and @M.Mostafa :
I still haven't flashed stock ROM using TWRP in the proper way since i wanted to recover my data.Will be doing this soon.
Few questions :
are you able to mount /data partition in TWRP?
are you able to successfully flash any custom recovery or only able to boot up from it?
in my case,if i flash twrp recovery using "flash" command it still loads default Android recovery but i am able to boot it up using "boot" command.
syntax example :
"mfastboot boot twrp.img" or "mfastboot boot philztouch.img" works
"mfastboot flash recovery twrp.img" or "mfastboot flash recovery philztouch.img" not working.
But here are a few steps that you could follow :
Use the .img file in this zip (attached),boot up using this and then try flashing the STOCK ROM and post the log here.
Hope you're flashing the Official XT1033 5.0.2 STOCK ROM and not something else.
Also,tell us the exact tutorial/steps you followed to flash.
I see that your bootloader is LOCKED.
I suggest you to UNLOCK it first so that flashing becomes easy.
Data MAYBE lost while doing this.
If you want to try and recover your data,refer my thread and maybe try the things i did.
Also,i suggest you open a different thread since this one is for spanda12's issue.
It'll help you document,receive specific responses and resolve your issue in a better way.
M.Mostafa said:
i have same problem in Moto G XT1033 Dual SIM ( Android Lollipop )
i haven't done anything in phone
I want My phone restored to normalcy
Click to expand...
Click to collapse
Hello guys! I'm on a G 2015 bike to find a way around it. Good tried the procedures without unlocking the bootloader, but without success! Then I went and I was able to unlock Bootloader and repeat the process to install Roo Stock. But to no avail as well. Does anyone have any tips for solving this problem?
I would guess it stops in bootloader because it doesn't like the rom you've flashed.
Did you flash TWRP?
Boot to TWRP and clean flash something else.
Else flash TWRP and then do that.
Hi there! I had the same problem, but the solution was just wait. It took a full 5 minutes to boot since the warning appeared, but it worked fine. Give it a try, wait 5 minutes (literally) and see what happens. If it still stuck, then try the solution above.
KrisM22 said:
I would guess it stops in bootloader because it doesn't like the rom you've flashed.
Did you flash TWRP?
Boot to TWRP and clean flash something else.
Else flash TWRP and then do that.
Click to expand...
Click to collapse
Hi. I tried to do the way you said it, but it did not work. Take a look at the picture
I follow this GUIDE for install
https://forum.xda-developers.com/moto-g/general/guide-custom-recovery-moto-g-xt1033-t2972905
{
"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 don't think your bootloader is unlocked.
Have you unlocked your bootloader using the Motorola site? No other method will work.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
which recovery are you using - copy/paste full module name.
The bootloader has been unlocked by the motorola website! When I insert the cell phone, the message appears that the bootloader is unlocked.
Jdoria said:
The bootloader has been unlocked by the motorola website! When I insert the cell phone, the message appears that the bootloader is unlocked.
Click to expand...
Click to collapse
"when you insert the cell phone" into what?
EDITED POST FOR WINDOWS:
for windows I think type cmd in search bar, right click on cmd.exe and choose administrative (you may have to enter a password) and do everything in that window.
fastboot flash recovery twrp.img
but first tell me exactly which twrp you are using - one is bad.
Better than that just grab the latest from squid and use that. I know it's good.
When it flashes successfully, DO IT AGAIN - don't ask why, just do it - same command.
THEN boot to TWRP and backup your stock if you still have one.
Then and only then, wipe and flash whatever your heart desires.
@Jdoria Please attach the output of "fastboot getvar all"
@KrisM22 "sudo" wont do anything, this is WINDOWS, not Linux.
acejavelin said:
@Jdoria Please attach the output of "fastboot getvar all"
@KrisM22 "sudo" wont do anything, this is WINDOWS, not Linux.
Click to expand...
Click to collapse
Yeah I put a note at the bottom of that post for that. My bad.
Hi I ran cmd.exe in managed mode. Is there any method to format the data of the phone and install everything from scratch?
Jdoria said:
Hi I ran cmd.exe in managed mode. Is there any method to format the data of the phone and install everything from scratch?
Click to expand...
Click to collapse
You need to run it in administrative mode.
Hello,
I downgraded my H830 to 20a, unlocked the bootloader, flashed TWRP and then LineageOS/OpenGapps.
When I re-locked the bootloader it wipes everything again and then the phone gives an error that it's corrupt and can't boot. It's a variant of this message, but it says it "can't boot" and simple loops through that screen every few seconds.
{
"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 can re-unlock the bootloader, but then the phone doesn't boot anymore and I have to go back to LGUP and reflash 20a.
I'm trying to re-lock the bootloader so I can use AndroidPay again.
What step am I missing, do I need to flash the verity patch? Do I need to use supersu to remove root (which I think is included in the default LineageOS signed package) before I re-lock?
Thanks for your help,
Doug
DougWare said:
Hello,
I downgraded my H830 to 20a, unlocked the bootloader, flashed TWRP and then LineageOS/OpenGapps.
When I re-locked the bootloader it wipes everything again and then the phone gives an error that it's corrupt and can't boot. It's a variant of this message, but it says it "can't boot" and simple loops through that screen every few seconds.
I can re-unlock the bootloader, but then the phone doesn't boot anymore and I have to go back to LGUP and reflash 20a.
I'm trying to re-lock the bootloader so I can use AndroidPay again.
What step am I missing, do I need to flash the verity patch? Do I need to use supersu to remove root (which I think is included in the default LineageOS signed package) before I re-lock?
Thanks for your help,
Doug
Click to expand...
Click to collapse
Once you install TWRP and root, you can NOT re-lock your bootloader. You need to unlock bootloader, get TWRP back if you lost it, go into TWRP and format data (not wipe) (make sure you have everything you want backed up, it will erase everything on internal), install no force encrypt zip (dm verity), install lineage os and opengapps, install magisk root and reboot. Magisk will hide root and hide that your bootloader is unlocked and Android pay will work.
Hi, i've been using the Mi Mix 3 (chinese ver.) for the past few months as my main device and today i tried to install the Pixel Experience rom but it didn't go well.
I'm now stuck on a bootloop, all i get is a black screen that says "Mi" and "unlocked" at the bottom of the screen.
I can still access fastboot and twrp but i can't get anything to work with either, installing any rom through twrp gets me back to the bootloop and i can't get the chinese rom to install through fastboot.
I also tried to install back the chinese rom with MiFlash but everytime i'm prompted with this error:
{
"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 not sure what to do at this point and could use some detailed help
here's a list of what i did btw:
- unlock the device with Mi Unlock
- install twrp with fastboot
- boot into twrp and installed pixel experience rom
hopefully i didn't make my phone a useless slab of glass and ceramic
Did you wipe data?
raven213 said:
Did you wipe data?
Click to expand...
Click to collapse
Yes pretty sure i did
Mel35 said:
Yes pretty sure i did
Click to expand...
Click to collapse
Wiping isn't enough, you need to format data in twrp to remove encryption
Mackay53 said:
Wiping isn't enough, you need to format data in twrp to remove encryption
Click to expand...
Click to collapse
done that and i'm still stuck on the same screen
i could use a step by step guide because i'm not sure what i could've messed up at this point
Mel35 said:
done that and i'm still stuck on the same screen
i could use a step by step guide because i'm not sure what i could've messed up at this point
Click to expand...
Click to collapse
Possibly using the wrong vendor, seems to be common in the PE thread
Mel35 said:
Hi, i've been using the Mi Mix 3 (chinese ver.) for the past few months as my main device and today i tried to install the Pixel Experience rom but it didn't go well.
I'm now stuck on a bootloop, all i get is a black screen that says "Mi" and "unlocked" at the bottom of the screen.
I can still access fastboot and twrp but i can't get anything to work with either, installing any rom through twrp gets me back to the bootloop and i can't get the chinese rom to install through fastboot.
I also tried to install back the chinese rom with MiFlash but everytime i'm prompted with this error:
I'm not sure what to do at this point and could use some detailed help
here's a list of what i did btw:
- unlock the device with Mi Unlock
- install twrp with fastboot
- boot into twrp and installed pixel experience rom
hopefully i didn't make my phone a useless slab of glass and ceramic
Click to expand...
Click to collapse
Did you flashed miui ROM before flashing PE stable rom 2 seems to be working
i tried to install twrp , root and degoogle my galaxy a12, i have no experience at all and nearly bricked my phone
i unlocked my bootloader, go into download mode, i tried flashing twrp 3.7.0 image i downloaded on the official website, it didn't work and everytime i reboot it got into download mode again
i flashed the stock rom again, go to the support thread of twrp on the galaxy 12 here, i did like the tutorial but i cannot flash the rom with the re partition and nand erase because odin will just froze and the progress bar wont appear
after that i tried flashing it like the post said. put the twrp image in the AP box, and the vbmeta.img.md5(i extracted the vbmeta.zip file since i cannot put the zip file into the box) into userdata box, then start, restarted the phone and after that it got the "An ERROR Has Occured While Updating Device Software" with the teal background, i freaked out but luckily i fixed it with the frp hijack software.
after that i'm just too scared to continue, does anyone know what i did wrong? my guess is that it's at the vbmeta file but the support post give that file only and i just extracted it and put the md5 file in the userdata box.
I assume that you flashed twrp recovery with vbmeta and you had One Ui 4.0 (Android 12) on stock. It's just that I had a similar thing when I flashed it on TWRP.
Note: WHEN YOU HAVE INSTALLED THE VBMETA AND TWRP FILE AND YOU ARE USING THE STOCK FIRMWARE THEN DO NOT LOGIN TO YOUR SAMSUNG ACCOUNT. YOUR PHONE WILL BE BLOCKED. AND WHEN TURNED ON, IT WILL PROVIDE THE FOLLOWING.
{
"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"
}
lil_kyrick said:
I assume that you flashed twrp recovery with vbmeta and you had One Ui 4.0 (Android 12) on stock. It's just that I had a similar thing when I flashed it on TWRP.
Note: WHEN YOU HAVE INSTALLED THE VBMETA AND TWRP FILE AND YOU ARE USING THE STOCK FIRMWARE THEN DO NOT LOGIN TO YOUR SAMSUNG ACCOUNT. YOUR PHONE WILL BE BLOCKED. AND WHEN TURNED ON, IT WILL PROVIDE THE FOLLOWING.
View attachment 5789287
Click to expand...
Click to collapse
no, it is the android 11 version with the A127FXXU5AVC4 stock firmware (vietnam region) and no i didn't login to anything after unlocking bootloader, and the warning shows something like this image here
but without the 2 last line, instead it has a korean and japanese translation below that first 2 english lines
i think i messed up at the vbmeta part, i though my phone was hard bricked but i managed to fix it and flashed a the stock firmware again
Oh ****. So connect your phone to your computer and use the "Emegency Software Recovery" function in the Smart Switch program.
What was your mistake? Yes, the fact is that you have SM-A127F, and you set it for SM-125F. And you need to repair the device now, otherwise, contact the nearest service center. Here is a link to the guide you need for your device.
lil_kyrick said:
Oh ****. So connect your phone to your computer and use the "Emegency Software Recovery" function in the Smart Switch program.
What was your mistake? Yes, the fact is that you have SM-A127F, and you set it for SM-125F. And you need to repair the device now, otherwise, contact the nearest service center. Here is a link to the guide you need for your device.
Click to expand...
Click to collapse
ah i already fixed it myself with frp hijacker, thank you for your consideration
az_r08 said:
ah i already fixed it myself with frp hijacker, thank you for your consideration
Click to expand...
Click to collapse
Can you send a ss of the odin you are using and the settings?
What I assume is you need to use patched odin or you device is encrypted.