I was on 4.4.2, rooted. I did a factory reset, flashed stock 4.4.2 (system, recovery, and boot), then got the 4.4.4 OTA.
Still says "unlocked bootloader."
I installed Titanium -- no root.
I rebooted to bootloader, tried flashing TWRP with:
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.1-ghost.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8220 KB)...
OKAY [ 0.774s]
writing 'recovery'...
OKAY [ 1.228s]
finished. total time: 2.002s
Rebooted to recovery -- got 'dead andy' with 'No Command' below.
Tried:
Code:
fastboot boot openrecovery-twrp-2.7.1.1-ghost.img
downloading 'boot.img'...
OKAY [ 0.775s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.875s
Also tried flashing `UPDATE-SuperSU-v1.94.zip` from stock recovery ... got
Code:
qe 0/1
-- Install /data/media/0 ...
Finding update package...
Opening update package...
Verifying update package...
Installation aborted.
I also then tried all of the above with `mfastboot` -- same result.
What do I do now?
d0g said:
I was on 4.4.2, rooted. I did a factory reset, flashed stock 4.4.2 (system, recovery, and boot), then got the 4.4.4 OTA.
Still says "unlocked bootloader."
I installed Titanium -- no root.
I rebooted to bootloader, tried flashing TWRP with:
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.1-ghost.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8220 KB)...
OKAY [ 0.774s]
writing 'recovery'...
OKAY [ 1.228s]
finished. total time: 2.002s
Rebooted to recovery -- got 'dead andy' with 'No Command' below.
Tried:
Code:
fastboot boot openrecovery-twrp-2.7.1.1-ghost.img
downloading 'boot.img'...
OKAY [ 0.775s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.875s
Also tried flashing `UPDATE-SuperSU-v1.94.zip` from stock recovery ... got
Code:
qe 0/1
-- Install /data/media/0 ...
Finding update package...
Opening update package...
Verifying update package...
Installation aborted.
What do I do now?
Click to expand...
Click to collapse
The issue is that you have to IMMEDIATELY reboot into custom recovery. Do this (from bootloader screen):
fastboot flash recovery twrp_file_name.img
fastboot reboot-bootloader
Now VOL DOWN to recovery, and VOL UP to select it.
If you don't do it this way, TWRP doesn't 'stick'. As long as you successfully boot into TWRP, click exit and it will offer to root for you.
samwathegreat said:
If you don't do it this way, TWRP doesn't 'stick'. As long as you successfully boot into TWRP, click exit and it will offer to root for you.
Click to expand...
Click to collapse
AHA! Thank you thank you!
samwathegreat said:
The issue is that you have to IMMEDIATELY reboot into custom recovery. Do this (from bootloader screen):
fastboot flash recovery twrp_file_name.img
fastboot reboot-bootloader
Now VOL DOWN to recovery, and VOL UP to select it.
If you don't do it this way, TWRP doesn't 'stick'. As long as you successfully boot into TWRP, click exit and it will offer to root for you.
Click to expand...
Click to collapse
I notice you help out on almost every thread and have helped me more then a few times. Just thought id say thanks from all us that are trying to lose are noob status lol
Sent from my XT1058 using Tapatalk
Hi there.. Am also using moto x and running stock 4.4.4... And i want to Unlock my bootloader and get Root... Can u pls guide me through the steps and file i need? Thank you
Hey guys,
I dun goofed when trying to do a routine backup.
First off, I'm trying to recover this without wiping, as I have some 2FA apps and other things that have secret keys that can't be recovered unless I can decrypt the darned thing
Rebooted into TWRP in order to do an image backup before I upgrade from arter97's kernel r13 to r14.
When TWRP comes up, it surprises me with a password prompt (instead of pattern unlock which is what it should be)
Reboot to system to remove encryption and then fix the password issue, greeted by "To start Android, enter your password" prompt, again instead of pattern unlock
Tried the numbers-to-pattern trick, no luck. Basically locked out of the phone now
Booted back into TWRP, while looking around for other options, accidentally chose "Slot A" which has gotten me stuck back on the old recovery
fastboot commands no longer work properly (see below)
Sometimes the commands hang, and I need to ctrl+c and re-run. I get very inconsistent results, as you'll see below
Code:
D:\adb>fastboot.exe boot twrp-3.2.1-0-cheryl.img
Sending 'boot.img' (23120 KB) FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
Trying to re-flash the kernel just hangs:
Code:
D:\adb>fastboot.exe flash boot arter97-kernel-r14-20200428.img
Tried switching to Windows Terminal/Powershell and got slightly different error:
Code:
PS D:\adb> .\fastboot.exe boot .\twrp-3.2.1-0-cheryl.img
Sending 'boot.img' (23120 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
PS D:\adb> .\fastboot.exe flash boot .\arter97-kernel-r14-20200428.img
Sending 'boot' (30176 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
PS D:\adb> .\fastboot.exe getvar all
getvar:all FAILED (Write to device failed (Unknown error))
Finished. Total time: 5.004s
PS D:\adb> .\fastboot.exe --set-active=a
PS D:\adb> .\fastboot.exe --set-active=b
fastboot: error: Device does not support slots
PS D:\adb> .\fastboot.exe --set-active=q
Slot q does not exist. supported slots are:
a
b
PS D:\adb> .\fastboot.exe --set-active=a
Setting current slot to 'a' FAILED (remote: 'Invalid Slot')
fastboot: error: Command failed
PS D:\adb> .\fastboot.exe --set-active=b
Setting current slot to 'b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
I'm sure the TWRP image is still there in slot b, but I can't get it to switch back.
Update:
I tried running the `fastboot --set-active=b` on a different (older) system which did finally work and allowed me to switch back over to TWRP, but I'm still having that decryption issue.
Anyone know why the encryption would suddenly switch from pattern unlock to "password" and how I could fix it?
Edit: After doing some more research on here, it sounds like my phone may have OTA'd itself to MR3 which may be the cause for the password issue.
Got an idea that I hope will work, which is to use the factory MR2 image, and comment out the lines for wiping data. Maybe that will bring it back?
Lineage 17.1 for the Sony Xperia 10 II
Please note this is currently for the dual-sim model ONLY. When you need a single-sim variant leave a comment, so we can work an that...
Code:
/*
* Disclaimer - your warranty may be void.
*
* I'm not responsible for bricked devices, dead OTGs 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.
*/
Features
OTA updates - always delayed for 1 day (to prevent broken rollouts); when you want it immediately, checkout my GitLab pipelines
Increased volume steps to 25
Over-provisioned system image (580MiB), to allow install of OpenGApps and other stuff
Open Source (it is based on SODP, you can view all my patches and ci scripts here or here)
Package signature spoofing (needed by MicroG)
What does not work?
Stock camera app with wide and zoom cameras, you may use Open Camera to circumvent that.
Notification LED blinking - kernel driver bug (see here)
LiveDisplay
You tell me...
Download
There you have multiple options:
To get the complete package (both including the ota and imgparts; only needed for the initial setup) visit...
AndroidFileHost
GitLab (make sure to download the artifacts from the master branch)
To get ONLY the OTA package to update your system later on, visit (or open up the LineageOS Updater) ota.simonmicro.de - please note that only the last recent 14 days are accessible there.
Changelog
2021-02-28
Fixed wifi hotspot.
2020-12-18
Fixed cameras.
2020-11-27
Fixed ADB security.
2020-11-25
Added SELinux support.
2020-11-20
Added OpenGApps support.
2020-11-17
Initial release.
How to install your system
The following guide assumes, you have setup adb and fastboot already (make sure to always use the latest version of the toolkit, otherwise you'll may get problems during flashing) - for that take a look into the internet. Also you should already downloaded the complete package from above!
Unlock the bootloader - a "how to" is here...
Download the oem binaries from here, make sure to use exactly that version!
Boot into the bootloader (hold "Volume up + Insert the USB cable" until led lights blue) and then update the oem partition:
Code:
fastboot flash oem_a [EXTRACTED_OEM_IMAGE_FILE]
fastboot flash oem_b [EXTRACTED_OEM_IMAGE_FILE]
Flash now the Lineage recovery partition as well as the dtbo partition (they are inside the img folder of the complete package):
Code:
fastboot flash recovery [EXTRACTED_RECOVERY_IMAGE_FILE]
fastboot flash dtbo [EXTRACTED_DTBO_IMAGE_FILE]
Disable the verity checks for now, as your new recovery violates the Sony verity profiles of the Stock ROM:
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
fastboot flash --disable-verity --disable-verification vbmeta_system vbmeta_system.img
Okay, you are now ready to boot the first time into the Lineage recovery, unplug the phone NOW!
To boot into recovery: Hold "Volume down + Power" until it vibrates...
You should now be booted into the recovery. We now clean any old data from Sonys Stock ROM - this is just to make sure you have a really clean install: Choose the "Factory reset" option.
The phone is now clean and ready to accept the new system. You now can either install just the OTA package and be done or flash every .img from the full package manually - the coice is yours. When you plan to flash the images manually, make sure to include boot, system, product, vendor, vbmeta_system, as these are normally part of the OTA update (I extracted the payload.bin to verify this!). For the latter approach you may orient yourself on my flashall.sh. I'll choose the simpler OTA-sideload approach for now.
Select "Apply update -> Apply from ADB" (now make sure the adb server runs as root - may use adb kill-server && sudo adb start-server to fix that) and execute (the OTA zip is inside the ota subdir):
Code:
adb sideload [OTA_SYSTEM_UPDATE_ZIP_FILENAME]
Something went wrong - help!
(Step 7-8) When you now see a device corrupt error
Don't panic!
You messed up the verity disable step from before - try again.
Try to switch the current boot slot (get current fastboot getvar current-slot and set new fastboot --set-active=, you can choose between a and b) and retry disableing verity disable again!
When your device fails to boot too many times (and crashes) the current slot could also get marked as corrupt. To reset that counter you'll need to reflash the boot partition - to see what is going on, try fastboot getvar all and look out for something like a unbootable flag.
(Step 9) When you get Operation not permitted during flashing
This is commonly caused by relocking and then reunlocking the bootloader (yay - buggy firmware). You'll need to relock, restore (and boot) the device with Flashtool using Sonys original ROM and start from fresh.
(Step 10) When you get the kDownloadPayloadPubKeyVerificationError error
Well, that's caused by using an other recovery than the provided one, as I use my own private keys to sign the build the recovery must also know them. Using an other recovery than the one from
the img folder of the complete package will most likely not include them (and when they do - I am in big trouble), and therefore fail. But you are in luck: It seems that the recovery writes
the data to the currently inactive slot and then fails. You could simply switch the system slot like described above!
Want to install Magisk?
Install the Magisk zip like the OTA system update by using adb sideload [MAGISK_FILE_NAME].
Want to install OpenGApps?
Make sure to use the pico-variant, as the system partition is even with over-provisioning really small (as the installer extracts some more stuff on the first boot) - then install the OpenGApps zip like the OTA system update by using adb sideload [OPENGAPPS_FILE_NAME].
Credits
As much I would like, I can't do everything by myself. A huge thank you to...
@MartinX3 for the used local_manifests and his device tree from his LineageOS organization
...the team behind @sonyxperiadev, for their great work (and their kernel sources)!
XDA:DevDB Information
LineageOS 17.1 for pdx201, ROM for the Sony Xperia 10 II
Contributors
Simonmicro, MartinX3
Source Code: https://gitlab.simonmicro.de/android/lineage/lineage-pdx201
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Sony OEM Package
Based On: AOSP
Version Information
Status: Beta
Hey,
as you guys may have already noted, I have stopped the active development phase for this LOS port a while ago. This was caused by me just not having enough time to do everything and additionally maintain a LOS port.
Today I'll upload the last maintenance build to the OTA server and mirrors. Of course I somehow included a little bug, which causes the system to complain about "an internal problem", which seem to be caused by some interaction with the OpenGApps package installer. Now, it is a feature. I'll may post one more update, if I figure this one out.
Nevertheless, I'll shut down the OTA service at 2022-06-01 (see https://status.simonmicro.de) and will then archive all project data. It was a great time to learn many (new/nasty) things about Android and how everything works. I have to say "thank you" to everyone, who supported me and was on board with this project.
See you next time,
simonmicro
-> https://forum.xda-developers.com/t/...r-xperia-10-ii-ota-sodp.4191601/post-86352693 <-
Reserved
First
At last The guide, source code looks great! Will install, check it next
hmm, i flashed everything according to the instructions, but the system still looks the same as Sjll's ROM and there is no updater in settings>system. anyone else getting this?
EDIT: nevermind, all is well, i was on the wrong slot.. : / wish we wouldn't have to deal with this, TWRP+lineage+one slot was perfect. this is not about the ROM though, it's awesome.
bamdadkhan said:
hmm, i flashed everything according to the instructions, but the system still looks the same as Sjll's ROM and there is no updater in settings>system. anyone else getting this?
EDIT: nevermind, all is well, i was on the wrong slot.. : / wish we wouldn't have to deal with this, TWRP+lineage+one slot was perfect. this is not about the ROM though, it's awesome.
Click to expand...
Click to collapse
- you made my day. Now I know which ROM you used before
No serious: Did you follow the guide step-by-step or did you altered it in some way (maybe forgot to reboot after switching slots) - as it should normally flash both slots (when using ota), even when not you should be at least on the right slot after flashing?!
Simonmicro said:
- you made my day. Now I know which ROM you used before
No serious: Did you follow the guide step-by-step or did you altered it in some way (maybe forgot to reboot after switching slots) - as it should normally flash both slots (when using ota), even when not you should be at least on the right slot after flashing?!
Click to expand...
Click to collapse
lol it's easy to know when the ROM in question is the only available aside from yours xd
seriously: i followed all the steps to the letter. flashed the SW binaries on both oem_a and oem_b. really everything.
i have a theory though. i originally flashed your ROM when 'side b' had previously been set active. if this persists across reboots - i really don't know, this whole 'dual ROM' concept is new to me - then there's your answer: the lineage install script probably has a command to use 'side a' for flashing. is completed successfully, but then i went ahead and booted the 'side b', which still had Sjll's ROM on it.
bamdadkhan said:
lol it's easy to know when the ROM in question is the only available aside from yours xd
seriously: i followed all the steps to the letter. flashed the SW binaries on both oem_a and oem_b. really everything.
i have a theory though. i originally flashed your ROM when 'side b' had previously been set active. if this persists across reboots - i really don't know, this whole 'dual ROM' concept is new to me - then there's your answer: the lineage install script probably has a command to use 'side a' for flashing. is completed successfully, but then i went ahead and booted the 'side b', which still had Sjll's ROM on it.
Click to expand...
Click to collapse
Well, I also tested my guide to the letter - and there i saw on my device screen that the ota flashed on both partitions. Did you also used my recovery? When you did: Lets see if others also have that problem... :angel:
Simonmicro said:
Well, I also tested my guide to the letter - and there i saw on my device screen that the ota flashed on both partitions. Did you also used my recovery? When you did: Lets see if others also have that problem... :angel:
Click to expand...
Click to collapse
Great job, thank you. Can I install NikGapp? Or does it also cause bootlaps?
Thapsus-cz said:
Great job, thank you. Can I install NikGapp? Or does it also cause bootlaps?
Click to expand...
Click to collapse
On their website:
Code:
OpenGapps Team (for base package and providing Open Gapps)
Therefore is a really good chance that the installer has the same problems like OpenGApps - but I can't say that for sure, I guess you'll need to try it out (when is does bootloop / never starts, please send me a adb logcat -b all for further diagnostics).
Done till the step 9.
Tried the second way first (flashing images). Please see the log for this below.. Then tried OTA way. OTA way did with 0 exit status (it sent files) but when I boot device it writes "Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds". How to fix?
Also when I load into recovery it writes this:
E: Failed to bind mount /mnt/staging/mulated/media/0 to /storage/emulated: NO such file or directory.
E: emulated failed to bind mount /mnt/stagingemulated/media/0 on /storage/meulated: No such file or directory.
Click to expand...
Click to collapse
See full log for flashing images:
sudo fastboot flash boot boot.img
sudo fastboot flash system system.img
sudo fastboot flash product product.img
sudo fastboot flash vendor vendor.img
sudo fastboot flash vbmeta_system vbmeta_system.img
[sudo] пароль для :
Sending 'boot_b' (65536 KB) OKAY [ 2.441s]
Writing 'boot_b' OKAY [ 0.358s]
Finished. Total time: 2.812s
Sending sparse 'system' 1/2 (785636 KB) OKAY [ 29.722s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'product' (432072 KB) OKAY [ 16.440s]
Writing 'product' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vendor' (48084 KB) OKAY [ 1.725s]
Writing 'vendor' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vbmeta_system' (4 KB) OKAY [ 0.005s]
Writing 'vbmeta_system' OKAY [ 0.003s]
Finished. Total time: 0.016s
❯ sudo fastboot flash boot boot.img
sudo fastboot flash system system.img
sudo fastboot flash product product.img
sudo fastboot flash vendor vendor.img
sudo fastboot flash vbmeta_system vbmeta_system.img
❯ sudo fastboot flash boot boot.img
sudo fastboot flash dtbo dtbo.img
sudo fastboot flash product product.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash super_empty super_empty.img
sudo fastboot flash system system.img
sudo fastboot flash vbmeta vbmeta.img
sudo fastboot flash vbmeta_system vbmeta_system.img
sudo fastboot flash vendor vendor.img
Sending 'boot_b' (65536 KB) OKAY [ 2.438s]
Writing 'boot_b' OKAY [ 0.378s]
Finished. Total time: 2.831s
Sending 'dtbo' (8192 KB) OKAY [ 0.302s]
Writing 'dtbo' OKAY [ 0.046s]
Finished. Total time: 0.357s
Sending 'product' (432072 KB) OKAY [ 16.212s]
Writing 'product' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'recovery' (98304 KB) OKAY [ 3.699s]
Writing 'recovery' OKAY [ 0.557s]
Finished. Total time: 4.265s
Sending 'super_empty' (4 KB) OKAY [ 0.011s]
Writing 'super_empty' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending sparse 'system' 1/2 (785636 KB) OKAY [ 29.755s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Sending 'vbmeta' (4 KB) OKAY [ 0.009s]
Writing 'vbmeta' OKAY [ 0.003s]
Finished. Total time: 0.021s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.003s]
Writing 'vbmeta_system' OKAY [ 0.004s]
Finished. Total time: 0.014s
Sending 'vendor' (48084 KB) OKAY [ 1.770s]
Writing 'vendor' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
Click to expand...
Click to collapse
xdauserart said:
Done till the step 9.
Tried the second way first (flashing images). Please see the log for this below.. Then tried OTA way. OTA way did with 0 exit status (it sent files) but when I boot device it writes "Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds". How to fix?
Also when I load into recovery it writes this:
See full log for flashing images:
Click to expand...
Click to collapse
I had the same problem yesterday with the same results. I struggled with it until morning. Eventually I downloaded the latest version of adb, flashed the stock rom again and started over. It was done in twenty minutes. Try the latest version of adb (I guess version 35 for Windows)
xdauserart said:
Done till the step 9.
Click to expand...
Click to collapse
...
Code:
Sending sparse 'system' 1/2 (785636 KB) OKAY [ 29.722s]
Writing 'system' FAILED (remote: 'No such partition.')
fastboot: error: Command failed
This indicates you tried to use the bootloader (which also has fastboot support) to flash the images. I made sure to write the guide the way that it states you should use the fastbootd service of the recovery. I have the dumb feeling that many more will go your way and fail. Damn it.
Code:
E: Failed to bind mount /mnt/staging/mulated/media/0 to /storage/emulated: NO such file or directory.
E: emulated failed to bind mount /mnt/stagingemulated/media/0 on /storage/meulated: No such file or directory.
Is fine, as you just erased all data - this also kills the partion so it cant be mounted anymore (that's the errors). This is indeed intentional as the system is now forced to really start fresh!
xdauserart said:
Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds"
Click to expand...
Click to collapse
Did you tried the help of my guide? When you failed that and your device rebooted too many times (or it just could not boot and crashed too many times) you'll need to reflash the boot partition to reset the counter (and therefore the failure message).
Two PR to fix back triple cam. But front cam is still broken.
https://github.com/sonyxperiadev/device-sony-seine/pull/29
https://github.com/sonyxperiadev/device-sony-pdx201/pull/15
--------------EDIT-----------------
Switch to CAF powerhal, better performance we have.
https://github.com/sjllls/device-sony-common/commit/de3b2bbbc33130891263d9e81ea2178a0f6783c4
https://github.com/sjllls/device-sony-sepolicy/commit/72059258eb0ff2c854996a05a5a23a8b73b55459
--------------EDIT-----------------
Renmember to let users flash with latest platform-tools, or they could not boot because of logical partition is not resized.
https://developer.android.com/studio/releases/platform-tools
Simonmicro said:
On their website:
Code:
OpenGapps Team (for base package and providing Open Gapps)
Therefore is a really good chance that the installer has the same problems like OpenGApps - but I can't say that for sure, I guess you'll need to try it out (when is does bootloop / never starts, please send me a adb logcat -b all for further diagnostics).
Click to expand...
Click to collapse
I can confirm that Opengapps pico can now be installed without a bootloop. I'm at work and I don't have adb. I installed them directly as an update from the sd card using recovery. Everything works fine.
Can we get OpenGapps Nano support?
I know that OpenGapps pico are supported, but most people use the nano package as it contains some functions that aren't possible to obtain in any other way
so is that possible?
KriiXOne said:
I know that OpenGapps pico are supported, but most people use the nano package as it contains some functions that aren't possible to obtain in any other way
so is that possible?
Click to expand...
Click to collapse
As I already drastically over-provisioned the system partition, I guess it could be possible that the nano package already works: In that case try it for yourself! When it goes wrong you can just switch over to your slot used before flashing the bad OpenGApps zip. Please PN me about your result, so I could extend the guide!
Simonmicro said:
As I already drastically over-provisioned the system partition, I guess it could be possible that the nano package already works: In that case try it for yourself! When it goes wrong you can just switch over to your slot used before flashing the bad OpenGApps zip. Please PN me about your result, so I could extend the guide!
Click to expand...
Click to collapse
I'll try tomorrow after the math test that i'm studying for today, and will let ya know ^^'
Simonmicro said:
...
Did you tried the help of my guide? When you failed that and your device rebooted too many times (or it just could not boot and crashed too many times) you'll need to reflash the boot partition to reset the counter (and therefore the failure message).
Click to expand...
Click to collapse
Fixed it Just repeated the steps from the first one and used OTA on step 9. Thanks!
FIRST READ THIS>>>>Use this guide only if you are 100% sure about the risks involved in flashing your device. I'm not responsible for any damage caused by using this guide on this thread. !!!!!!!! If you are not expert don't read this guide!!!
What you need:
1-windows 10 on a PC
2-Motorola Razr 5g full charged
3-Usb Driver Motorola
4- Adb and Fastboot Tools
5- Enable developer option :Head over to the Settings app of your device via the notification shade or app drawer.
Enable developer options
Scroll down and tap on 'About phone. '
Find an entry labeled 'Build number. ' Keep on tapping until you see a prompt that says 'You are now a developer! '. ...
Then Enable USB debug and unlock bootloader options
Step A Unlock Bootloader (make a backup ! > you lost ALL your data!!!
1- First take a full backup of your phone as unlocking the bootloader on Motorola Razr 5G will wipe all the data.
2- To connect devices you need some drivers, so install ADB & Fastboot drivers and Motorola USB Driver on your PC.
3- Open Settings and go to About Phone. Tap 7-8 times on Build Number, and it will show ‘You are now a developer.’
4- After enabling the developer options, go back to Settings and then go to System > Developer Options. In Developer options, enable OEM Unlocking and also enable USB Debugging.
5- Turn off your device. Press & hold Volume Down + Power button together to boot Motorola Razr 5G into Fastboot Mode.
6- And when the Fastboot screen appears on the phone, release both buttons. Connect your phone to your PC after booting into Fastboot.
7- Now open the Command window or CMD on your computer. Open Command window from Platform Tools location in case of macOS and Linux.
8- Enter the below command in the Command/PowerShell window
fastboot oem get_unlock_data
9- It will display 5-line code. Copy the code and make it in one line, use notepad for convenience. Remember not to copy (bootloader) in case of windows and Info in case of Mac.
10- Go to Motorola unlock page and click next and login with the Motorola account.
11- Copy the one-line code that you just adjusted in Notepad and paste it into the Motorola unlock page.how to unlock bootloader of motorola razr 5g
12- Click on ‘Can my device be unlocked’ and then click ‘Request Unlock Key’ (make sure to select I Agree).
13- Then you will receive a code via mail (Motorola account ID). Copy the code and paste in place of ‘code’ without inverted commas in the below command and press Enter
fastboot oem unlock 'code'
14- Entering the above command will unlock bootloader of Motorola Razr 5G. It will erase all the data on your phone. After unlocking the bootloader, reboot, and set up your device.
Once you unlock the bootloader of Motorola Razr 5G, you can check for it by going to Developer Options and OEM Unlocking. It should be enabled. After unlocking bootloader of Motorola Razr 5G, you can proceed with rooting your phone. Also make sure to go through the requirements.
Step B - Root with Magisk modify file boot.img
You can root your phone using Magisk in different ways such as flashing Magisk Zip or installing a Patched boot image. Since you need a custom recovery to flash Magisk, you need to first install custom recovery. Here in this guide, we will share how to root Motorola Razr 5G with a patched boot image.
1-Copy the Motorola Razr 5G firmware to your computer. And then extract the firmware using 7Zip or WinRAR.
2-Open the extracted folder and copy the boot.img file to your phone storage.
3-Install the Magisk Manager app on your phone.
4-After installing, open the Magisk Manager app and click on the first Install and again click on Install.
5-It will ask for the method, so choose ‘Select and Patch a File’ from the option
6-Now browse and select the boot.img file, and it will start patching the boot image.
7-The output file will be stored in the download folder with the name magisk_patched.img.
8-Copy the patched boot image file to your computer in folder C:\adb. Also, rename the patched file to boot.img.
9-Reboot your Motorola Razr 5G to Fastboot mode and connect it to your computer. Follow the steps given in the unlock bootloader guide above.
10-In the C:\adb folder (or platform-tools folder) press Shift + Right click on an empty area and select ‘Open Command window here’ or ‘Open PowerShell window here.’
11-Enter the below command in the Command/PowerShell window to check the device is connected or not, entering command should return some number id.
fastboot devices
12-Now enter the below command to flash Magisk and root Motorola Razr 5G.
fastboot flash boot boot.img
13-After that, reboot your device to the system.
14-If the Magisk Manager is not installed on your phone, then install the app. Skip if the app is already present.
15-Complete the in-app instructions, and the device will automatically reboot into the system.
Step C - Flash firmware (if you flash oly boot.img bbe sure to download the SAME FIRMWARE YOU HAVE ON YOUR PHONE)
Boot your device into bootloader mode. Phone off > press and hold at the same time :volume down and power on buttons
Connect your Motorola Razr 5g to the PC using the USB Cable.
Download Stock ROM/Firmware and extract it inside the adb and fastboot folder
Inside the ADB folder, open the command window and enter the following command
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash radio radio.img
fastboot flash logo logo.bin
Now toggle to fastbootdfastboot reboot fastboot
fastboot reboot fastboot
Flash the following command
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7 and 8 ,9 etc....
Toggle back to bootloader
fastboot reboot bootloader
fastboot erase carrier
fastboot erase metadata
fastboot erase ddr
(Optional except you want to wipe) fastboot erase userdata
fastboot reboot
Now your device will reboot into bootloader with the firmware you installed.
you can flash only boot.img (modified) file!
You can flash other country firmware, i try with india and italy firmware...
I find very important info from these Links:
How to Root Motorola Razr 5G and Unlock Bootloader
Want to root Motorola Razr 5G with Magisk? Here's how to root Motorola Razr 5G along with guide to unlock bootloader.
www.ytechb.com
Motorola XT2052-1 Firmware Flash File (Stock ROM)
Here we have shared the latest stock ROM for Motorola Moto E 2020 XT2052-1 (ginna). You can download and flash the firmware file on your Motorola XT2052-1 using the flash…
droidfilehost.com
Motorola unlock bootloader link
https://motorola-global-portal.custhelp.com/cc/cas/sso/redirect/standalone%2Fbootloader%2Funlock-your-device-c
Official site to download Magisk
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Firmware:
Motorola Razr 5G XT2071-4 Stock ROM Firmware (Flash File)
Download the official Motorola Razr 5G XT2071-4 Stock Firmware (Flash File) for your Motorola Smartphone. We also provide all other Motorola Stock Firmware.
motostockrom.com
or (better!!) Telegram bot: Moto Updates Tracker >> t.me/motoupdatestracker
Adb and Fastboot Tool:
Download ADB and Fastboot tool 15 seconds ADB Installer v1.5.6
ADB or Android Debug bridge is used to establish a successful connection (bridge) between your device and PC. Once this connection is established, you could carry out plenty of tweaks,…
droidfilehost.com
Usb Motorola Driver
Where can I download the USB drivers for my device?| Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.Where can I download the USB drivers for my device?
support.motorola.com
I hope i've been helpful...
Is there currently any way to revert back to stock from this?
KOAO said:
Is there currently any way to revert back to stock from this?
Click to expand...
Click to collapse
I don't know, I'm not try. If you lock bootloader and load official firmware i think is possible.
Will this work on the T-mobile variant?
icedventimocha said:
Will this work on the T-mobile variant?
Click to expand...
Click to collapse
You have to find your firmware version on telegram here:
https://t.me/motoupdatestracker
i think the way is always the same, pay attention to every step....
didn't work for me...
the patched boot.img created by magisk did not work...
my phone got bricked at step c
C:\Users\Danz\Desktop\Temp\platform-tools\moto>fastboot flash partition gpt.bin
target reported max download size of 805306368 bytes
sending 'partition' (206 KB)...
OKAY [ 0.007s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.302s]
finished. total time: 0.312s
C:\Users\Danz\Desktop\Temp\platform-tools\moto>fastboot flash bootloader bootloader.img
target reported max download size of 805306368 bytes
sending 'bootloader' (12800 KB)...
OKAY [ 0.297s]
writing 'bootloader'...
(bootloader) Validating 'default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'default.xml'
FAILED (remote failure)
finished. total time: 0.408s
C:\Users\Danz\Desktop\Temp\platform-tools\moto>fastboot flash bootloader bootloader.img
target reported max download size of 805306368 bytes
sending 'bootloader' (12800 KB)...
OKAY [ 0.302s]
writing 'bootloader'...
(bootloader) Validating 'default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'default.xml'
FAILED (remote failure)
finished. total time: 0.412s
C:\Users\Danz\Desktop\Temp\platform-tools\moto>fastboot flash bootloader bootloader.img
target reported max download size of 805306368 bytes
sending 'bootloader' (12800 KB)...
OKAY [ 0.297s]
writing 'bootloader'...
(bootloader) Validating 'default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'default.xml'
FAILED (remote failure)
finished. total time: 0.407s
C:\Users\Danz\Desktop\Temp\platform-tools\moto>fastboot flash bluetooth BTFM.bin
target reported max download size of 805306368 bytes
sending 'bluetooth' (188 KB)...
OKAY [ 0.006s]
writing 'bluetooth'...
OKAY [ 0.011s]
finished. total time: 0.020s
C:\Users\Danz\Desktop\Temp\platform-tools\moto>fastboot flash dsp dspso.bin
target reported max download size of 805306368 bytes
sending 'dsp' (65536 KB)...
OKAY [ 1.423s]
writing 'dsp'...
OKAY [ 0.172s]
finished. total time: 1.596s
C:\Users\Danz\Desktop\Temp\platform-tools\moto>fastboot flash radio radio.img
target reported max download size of 805306368 bytes
sending 'radio' (151933 KB)...
OKAY [ 3.335s]
writing 'radio'...
(bootloader) Validating 'radio.default.xml'
(bootloader) Committing 'radio.default.xml'
(bootloader) - flashing 'NON-HLOS.bin' to 'modem'
(bootloader) - flashing 'fsg.mbn' to 'fsg'
(bootloader) - erasing 'modemst1'
(bootloader) - erasing 'modemst2'
OKAY [ 0.494s]
finished. total time: 3.835s
C:\Users\Danz\Desktop\Temp\platform-tools\moto>fastboot flash logo logo.bin
target reported max download size of 805306368 bytes
sending 'logo' (3332 KB)...
OKAY [ 0.075s]
writing 'logo'...
OKAY [ 0.016s]
finished. total time: 0.093s
I have a Moto G6 Forge Cricket that I forgot the password to. I have been trying to boot into another image without data loss in order to go in and delete the password config files, but have not been able to get anything to work. USB debugging doesn't seem to be on, the bootloader is locked, and I have no idea if it's possible. I can access fastboot and android recovery. Fastboot says the product variant is "jeter XT1922-9", leading me to believe that it's just a reskinned moto g6 Play.
I have tried recovery loading update aroma file manager from SD card, which failed signature check. Updating over adb doesn't work, as the phone doesn't show up in adb at all, only fastboot.
I tried flashing TWRP recovery for the moto g6, and got the following output on PC:
C:\Android\SDK\platform-tools>fastboot flash recovery twrp.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (17626 KB) OKAY [ 0.559s]
Writing 'recovery' (bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
On the phone, I see a series of yellow cmd log lines leading up to "cmd: flash:recovery" followed by pink "Mismatched partition size (recovery)" Some posts said that this was an ignorable error and to just proceed into recovery, but when I did it just went to the normal android recovery.
I also tried just using fastboot boot, but that obviously didn't work due to the locked bootloader.
C:\Android\SDK\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (17626 KB) OKAY [ 0.563s]
Booting (bootloader) permission denied!
FAILED (remote: '')
fastboot: error: Command failed
I'm out of ideas and out of google search results that aren't SEO spam to read. If anyone knows something else I could try I would be happy to hear it. Thank you so much!
The only thing I can think of is using the factory recovery to erase the user partition / factory reset.