Related
I have been trying to root my honor 7a (AUM-l29). I get stuck with the following message:
Code:
C:\Users\XXX\Downloads\New folder (2)>fastboot flash /recovery recovery.img
target reported max download size of 535822336 bytes
sending '/recovery' (26188 KB)...
OKAY [ 0.849s]
writing '/recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.854s
Yes, OEM unlock is on.
Yes, bootloader is unlocked.
Yes, HiSuite is installed.
If I remove the / from recovery, it says that the partition is not found. /boot doesn`t work either. I have tried every guide ever made. Thanks for your time!
What is the FRP status?
shashank1320 said:
What is the FRP status?
Click to expand...
Click to collapse
the frp status is "unlock"
I solved the issue. Had a guy from OneClickRoot remote into my computer, h used the following line:
Code:
fastboot flash ramdisk *whateverimageheused*
it seems that by hitting the ramdisk he was able to install Magisk and root
CaptainCrash said:
the frp status is "unlock"
I solved the issue. Had a guy from OneClickRoot remote into my computer, h used the following line:
Code:
fastboot flash ramdisk *whateverimageheused*
it seems that by hitting the ramdisk he was able to install Magisk and root
Click to expand...
Click to collapse
You were using incorrect command. For oreo commands have changed. Anyways, glad it is working for you now
CaptainCrash said:
the frp status is "unlock"
I solved the issue. Had a guy from OneClickRoot remote into my computer, h used the following line:
Code:
fastboot flash ramdisk *whateverimageheused*
it seems that by hitting the ramdisk he was able to install Magisk and root
Click to expand...
Click to collapse
Hi, i am looking for twrp right image and a metod for unlock all on aum-l29 can u helpme?
HONOR 7A USER; #Helpless; #Need_TWRP
Unlocked bootloader of my HONOR 7A(AUM-AL20),because of treble suppport,I am able to flash GSI Treble images(ROMs) through fastboot,(able to root also by patching ramdisk using magisk manager).Flashing process is only being done through fastboot.Customization is limited due to lack of developer support.No custom recovery yet.(Meaning; If you need GAPPS on your device with a custom rom,then GAPPS included GSIs are the only way.If a "Vanilla" image is flashed,then no way to avail the facility of GAPPs.GAPPS couldn't be sideloaded through ADB,which could have been done on previous android versions).Tried copying GAPPS content manually to each specific folder by extracting,moving,replacing etc..,following some guides,but no luck.,device crashes with 'ANRs'(app not responding errors).Currently on Lineage OS(GAPPS included)after trying many GSI Treble ROMs,coz they are the only available ones,as there is no development support for Huawei/Honor devices,mostly which are not of Kirin Socs.Tried contacting developers,in vain.They have no interest at all in helping Honor/Huawei device owners.Tried uploading recovery and details to the TWRP Flutter(An unofficial TWRP support,which develops TWRP for devices which doesn't have TWRP support officially)And PIE GSIs which support Oreo 8.0 vendor might be supported,I haven't tried that yet.Anyway,apart from VOLTE,almost everything else seems to work on(LINEAGE OS 15.1 by phhusson).There are patches available for the VOLTE fix,but maybe not for HONOR devices,even if there might be a patch,it ought to be flashed,but without a custom recovery,I don't think it might be possible.So I have done almost everything by searching over google,developer's blog,XDA.,but no hope.So if you think I missed doing something.,please help.
#[email protected]
#Note: I am not a developer,just a guy interested in customization,and values the same interest of others in this matter.
Screenshots attached are from the 'TWRP Builder(Flutter)' app.
Thank you
#DAMY.
Here is an honor 7A twrp build : (flash it in recovery_ramdisk)
gdfgfdghttps://cdn.discordapp.com/attachments/535927794740232194/569181811209404436/TWRP-3.2.3-honor-7a-To-Flash.imggdfgfd
can you please give me the link of twrp and proper root guide for honor 7A AMU-AL20??
TWRP Honor 7A
You'll need an unlocked bootloader to flash anything on your device.You'll have to acquire the bootloader unlock key from the service centre(possible chance/for educational purpose).
It might cost around 500 INR.
After acquiring the code,goto device developer setting(first activate the developer option by tapping on the build number 8 times in the about phone inside system setting)Then goto the developer option inside the system setting and turn on OEM unlocking to enable FRP Unlock.Then power off your device,hold the VOLUME- button and connect the data cable while it is connected either to the computer or charger,you'll be in fastboot mode then.Enter the below command in the Command Prompt to unlock bootloader.
•fastboot<>oem-unlock<>code got from Service center
if successful,phone will restart after wiping internal data.
To flash TWRP ,
•fastboot<>flash<>recovery_ramdisk<>path to the downloaded recovery
Mail me if you need help.,
I'm running stock EMUI with updated security patch and removed bloatware.I'm satisfied.
dammelee18 said:
You'll need an unlocked bootloader to flash anything on your device.You'll have to acquire the bootloader unlock key from the service centre(possible chance/for educational purpose).
It might cost around 500 INR.
After acquiring the code,goto device developer setting(first activate the developer option by tapping on the build number 8 times in the about phone inside system setting)Then goto the developer option inside the system setting and turn on OEM unlocking to enable FRP Unlock.Then power off your device,hold the VOLUME- button and connect the data cable while it is connected either to the computer or charger,you'll be in fastboot mode then.Enter the below command in the Command Prompt to unlock bootloader.
•fastboot<>oem-unlock<>code got from Service center
if successful,phone will restart after wiping internal data.
To flash TWRP ,
•fastboot<>flash<>recovery_ramdisk<>path to the downloaded recovery
Mail me if you need help.,
I'm running stock EMUI with updated security patch and removed bloatware.I'm satisfied.
Click to expand...
Click to collapse
Dcunlock isnt working for me
I am trying to unlock an Android phone that has stopped taking the correct password after a auto-restart. I know the PIN, I have not changed it in a long while. The phone stopped accepting the PIN after the sudden auto-restart so I am just clueless what may work. Hard reset is not an option for this device without backing up the data so willing to try anything that may help.
Additional information:
1. The phone does not have USB debugging enabled.
2. It is recognized by ADB only in sideload mode.
3. When I try to get into Recovery mode pressing volume up and power button, it goes directly to the black screen that shows image of a phone and USB cable.
4. I have not been able to get to the stock recovery screen where different options like mounting can be chosen.
Any suggestion or guidance would be hugely appreciated. Thanks a ton for your time.
Thank you.
This is just brainstorming not a tutorial!
i don't know if it works like this, but you can try..
requirements
- stock ROM (in case you brick device)
- magisk manager (in case twrp does not work)
- AIK from osm0sis
- Qualcomm HS-USB QDLoader 9008 Driver
- fastboot_edl.7z
- twrp-3.3.1-0-mido.img (or ZCX TWRP from cofface)
- Appender-v4-rec.zip
- QSaharaServer.exe
- fh_loader.exe
- prog_emmc_firehose_8953_ddr.mbn
- splash.img from xaacnz
steps
- prepare twrp.img (you must patch twrp manually)
- prepare splash.img
- prepare hack_splash.xml (tricky/dangerous)
- prepare twrp.xml (tricky/dangerous)
- install qualcomm drivers
- boot in EDL mode from fastboot
- check com port
- initialize firehose connection with QSaharaServer.exe
- flash splash.img with fh_loader.exe
- flash twrp.img with fh_loader.exe
- reboot into recovery
- check if twrp is able to decrypt userdata
if decryption unsuccessful, you can't backup data. but you could still enable usb-debugging even with root permissions by patching default.prop
- patch boot.img with magisk manager (set advanced - keep force encryption)
- unpack boot.img with AIK
- enable usb-debugging in default.prop
- repack, rename to boot.emmc.win
- restore boot.emmc.win from twrp
- install Appender-v4.zip
- reboot
- adb root
- adb pull /dev/block/dm-0
you might find this confusing, it is! do not try anything above without knowing what you do! i don't own this device. nothing is tested. i can't write tutorial with exact steps, this is your task. You are the one who will figure out solution and write tutorial. we can just assist and answer questions (you can ask any question for each single step, one after one)
after all, there is no guarantee it works for your device. also please note @xaacnz is not available and won't help on this.
there might be easier methods i don't know, please do your own research how to temporary by-pass or unlock bootloader without permission from xiaomi, there are plenty much tutorials for QFIL / EDL mode for other devices, maybe one of this methods works
if you decide to continue, be aware this is last option only and there might no way back to recover your data..
please read
Exploiting Qualcomm EDL Programmers (1): Gaining Access & PBL Internals
Bypass bootloader lock of Redmi 5A(riva) without permission from xiaomi
the tricky/dangerous part is to find the right offsets and sizes for partitions. you might get some info from fastboot getvar all
Thank you for your reply! These steps are indeed a overwhelming for me but I can try one step at a time.
I was thinking of a basic solution like using Aroma File Manager to delete lock-information-storing files from the device.
However, when I reboot into recover mode it takes me directly to a screen that looks like this: https://i.ytimg.com/vi/AJICnDxnXEo/maxresdefault.jpg
I cant find a recovery page like this one which may allow me to install Aroma from SD card: https://i.ytimg.com/vi/0zntvnVEIYQ/hqdefault.jpg
I was wondering is flashing an OTA image from adb may solve this. The device is recognized by adb only in sideload mode.
If flashing a new OTA image can take me to recovery menu that allows installing Aroma from SD card perhaps that will work?
Sorry if these questions are too basic for you. I have no real technical knowledge on these stuff. Just trying to learn from scratch to save data on the device.
Thank you so much for your time.
aIecxs said:
This is just brainstorming not a tutorial!
i don't know if it works like this, but you can try..
requirements
- stock ROM (in case you brick device)
- magisk manager (in case twrp does not work)
- AIK from osm0sis
- Qualcomm HS-USB QDLoader 9008 Driver
- fastboot_edl.7z
- twrp-3.3.1-0-mido.img
- Appender-v4-rec.zip
- QSaharaServer.exe
- fh_loader.exe
- prog_emmc_firehose for your device
- splash.img from xaacnz
steps
- prepare twrp.img (you must patch twrp manually)
- prepare hack_splash.xml (tricky/dangerous)
- prepare twrp.xml (tricky/dangerous)
- install qualcomm drivers
- boot in EDL mode from fastboot
- check com port
- initialize firehose connection with QSaharaServer.exe
- flash splash.img with fh_loader.exe
- flash twrp.img with fh_loader.exe
- reboot into recovery
- check if twrp is able to decrypt userdata
if decryption unsuccessful, you can't backup data. but you could still enable usb-debugging even with root permissions by patching default.prop
- patch boot.img with magisk manager (set advanced - keep force encryption)
- unpack boot.img with AIK
- enable usb-debugging in default.prop
- repack, rename to boot.emmc.win
- restore boot.emmc.win from twrp
- install Appender-v4.zip
- reboot
- adb root
- adb pull /dev/block/dm-0
you might find this confusing, it is! do not try anything above without knowing what you do! i don't own this device. nothing is tested. i can't write tutorial with exact steps, this is your task. You are the one who will figure out solution and write tutorial. we can just assist and answer questions (you can ask any question for each single step, one after one)
after all, there is no guarantee it works for your device. also please note @xaacnz is not available and won't help on this.
there might be easier methods i don't know, please do your own research how to temporary by-pass or unlock bootloader without permission from xiaomi, there are plenty much turorials for QFIL / EDL mode for other devices, maybe one of this methods works
if you decide to continue, be aware this is last option only and there might no way back to recover your data..
please read
https://github.com/alephsecurity/firehorse
https://forum.xda-developers.com/xiaomi-redmi-5a/how-to/bypass-bootloader-lock-redmi-5ariva-t3772381
the tricky/dangerous part is to find the right offsets and sizes for partitions. you might get some info from fastboot getvar all
Click to expand...
Click to collapse
there is no usual recovery for xiaomi. even if, you can't install aromafm from stock recovery because only oem signed files accepted. you can try via sideload you will see it fails.
i don't think OTA will fix anything, but of course you can try. i will meanwhile prepare xml files for you, but give me time.. i am a newbie to this, too.. maybe on weekend i have time
i am not sure if this method does wipe data (i can not see the "erasing userdata" message on this fastboot screenshot)
@BushraXiaomi
Is your RN4 with Qcom SoC or MTK (mido or nikel)?
Did you enable device encryption (did you have to enter password before the lock screen would appear)?
@Alecxs Thanks a lot again! Let me try out the codes you provided screenshot of. I will give you an update on what I see.
And I tried editing out the original block quotation. The changes are not being saved after repeated attempts. Sorry about that.
@Alecxs Thanks a lot again! Let me try out the codes you provided screenshot of. I will give you an update on what I see.
And I tried editing out the original block quotation. The changes are not being saved after repeated attempts. Sorry about that.
Mine is on QCom. And I did have an old lock screen password. I didn't change it but the phone suddenly stopped taking the correct PIN after an auto-restart.
mirfatif said:
@BushraXiaomi
Is your RN4 with Qcom SoC or MTK (mido or nikel)?
Did you enable device encryption (did you have to enter password before the lock screen would appear)?
Click to expand...
Click to collapse
@Alecxs so based on the discussion here I am guessing unlocking bootloader will result in the data getting erased
link: https://forum.xda-developers.com/moto-x/moto-x-qa/unlocking-bootloader-wipe-data-t2739564
BushraXiaomi said:
Mine is on QCom. And I did have an old lock screen password. I didn't change it but the phone suddenly stopped taking the correct PIN after an auto-restart.
Click to expand...
Click to collapse
Encryption is different than lock screen. I'm asking this because if your device is encrypted and the password is changed/corrupted/not working, it's almost certain that your data is not recoverable, even if you manage somehow to flash TWRP and/or unlock bootloader without wiping data.
---------- Post added at 06:25 PM ---------- Previous post was at 06:17 PM ----------
BushraXiaomi said:
@Alecxs so based on the discussion here I am guessing unlocking bootloader will result in the data getting erased
link: https://forum.xda-developers.com/moto-x/moto-x-qa/unlocking-bootloader-wipe-data-t2739564
Click to expand...
Click to collapse
Data wipe on unlocking bootloader is the expected behavior and Google strongly recommends this behavior to OEMs. However bootloader is not a part of Android (AOSP), so not all OEMs fulfill all requirements. And therefore there are very rare chances that unlocking may not erase data.
Secondly, as mentioned earlier, many Qualcomm devices (including a long list from Xiaomi) have an exploit in Emergency Download mode. EDL is a bootloader mode which operates even below the usually called bootloader (ABOOT; the one which provides "fastboot" protocol). It can be hacked to get a dump of whole storage chip or flash a partition e.g. recovery (TWRP) without going through proper channel of bootloader unlocking. Note that a locked botloader won't boot a custom "boot" or "recovery" partition which is not signed by OEM's private key (like TWRP is). It's part of Chain of Trust on Android devices.
However (somehow achieved) access to "userdata" partition will be of no use if the partition is encrypted as I explained. TWRP won't be able to decrypt it without correct PIN/password (if it was set). However if it wasn't encrypted or "default_password" was used for encryption (and not the one you set), data recovery is very probable.
I hope it clarifies the basic scenario for you.
There are few things that must be known:
1. Which soc? qcom or mtk, if mtk go to service centre and don't waste time here.
2. Do you have permission to unlock bootloader? If you have permission to unlock then you can easily just unlock, note that unlocking itself doesn't wipe data, it is wiped after it. There are some tricks you can do so that data is not wiped after unlock and you must search them on your own.
3. Is your device encrypted? If it is then which encryption FBE or FDE? If it is encrypted then most likely data can't be recovered.
If you have qcom soc, don't have permission to unlock bootloader then you can do this...
From what you said it looks like recovery is corrupted, you could try flashing stock recovery from *edl but stock recoveries are useless but you can still backup your important data maybe, I am not sure because I have not been into recoveries for past 4 years.
The following method is not tested for your device but might work since the bootloader bug might be present in your device too. Improving alecxs answer you can do this:
1. Grab twrp for your device
2. Append 4k blocks using this command on any Linux based distro or termux (Android app) or BusyBox 1.31.
Code:
printf '\x30\x83\x19\x89\x64' | dd of=/path/to/twrp.img ibs=4096 oflag=append conv=sync,notrunc
3. Flash the recovery using edl
4. Directly boot into recovery and see if it boots.
5. If it boots then delete password file of Android and boot into OS.
6. Password should be removed now.
*edl: you must learn to use edl
@mirfatif @saurabh6377 thanks to both of you! I was reading up to understand the steps suggested by @Alecxs
let me try out the different options suggested by you and I will let you know how it goes.
@mirfatif no I did not use any extra encryption apart from setting the regular lock screen
@saurabh6377 1. qcom
2. I dont think I have the permission. Never needed to check it until now and never needed to ask for the permission so guessing I don't have it by default
3. I didn't have any extra layer of encryption apart from the lock screen
so your device is most likely encrypted with FDE and default_password as a lot of older xiaomi devices. lets hope the issue is just with screen lock - however there is not really a good explanation (why unlocking screen fails) other than broken encryption. in such case your data is not recoverable.
please note xiaomi removed the fastboot edl command since oreo 8.1 and there might be downgrade protections, so do not update to later version than 8.0
Please just try to boot your device in EDL mode and report back
Hi all, just wanted to update you that I don't have any result yet. Reading up on each of the steps so I can execute as suggested. I will get back to you when I have some results. Thanks again
follow the link behind fastboot_edl.7z and try to boot into EDL mode with modified fastboot.exe
@Alecxs Just to double check, I am directly following the steps mentioned here: https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Is that ok? Doing this first before anything else?
yes. if it works, you can proceed with installing Qualcomm HS-USB QDLoader 9008 Driver (and tell us the COM port from windows device manager)
if fastboot_edl not working, you must find another way to boot into EDL aka shortcircuiting data pins on usb-connector (deep flash cable) or find a test point on the physical motherboard on youtube
found offsets and sizes for partitions in rawprogram0.xml
i have copied all required files from Xiaomi_Redmi_Note_4_V9.0.5.0.NCFMIEI_20171113.0000.00_Global_7.0_XFT and tried to patch the files. in the modified splash.img string SPLASH!! is replaced with HACKED!! hopefully this works. also i have patched default.prop to make adb insecure in case twrp does not work.
there are differences in files when appending manually or with Appender-v4-rec.zip, so actually i have flashed twrp-3.3.1-0-mido.img to another device (Redmi 5), patched with Appender-v4-rec.zip and created a copy of recovery partition afterwards. the result you can find in twrp-hack.zip (this is the only zip file you need)
for debugging purposes i have uploaded boot-insecure.zip and twrp-3.3.1-0-mido.zip which contains all three files: original, manually patched, patched with appender (you don't need this)
@Alecxs I am trying. Sorry I don't have any result yet This is so out of my depth, league, width etc. etc.
Buttttt I am committed to save the data so I will keep going over the steps you suggested until I feel confident to execute them. Really sorry for how slow I am being about it.
I really, really, really appreciate all your help. THANK YOU SO MUCH!
Here was a Guide. Someone said people don't care about Me or My Work so...
This was posted 18-Jan? I was just looking around to buy this phone. I'm assuming this works with the recent updates to the phone (update the fixes the heating issue).
vman00 said:
This was posted 18-Jan? I was just looking around to buy this phone. I'm assuming this works with the recent updates to the phone (update the fixes the heating issue).
Click to expand...
Click to collapse
Sorry i was late. But Sure, Updates doesnt really Play a Role!
You can Always unlock If Your Device allows it.
Have fun!
Miustone said:
Sorry i was late. But Sure, Updates doesnt really Play a Role!
You can Always unlock If Your Device allows it.
Have fun!
Click to expand...
Click to collapse
Thank you for the quick response. And no worries, I always hold off from getting new phones for a root guide.
Thread / Guide updated
Miustone said:
Thread / Guide updated
Click to expand...
Click to collapse
Has anyone installed a GSI ROM on this device? I'd love to know how the cameras performed.
thatguy222 said:
Has anyone installed a GSI ROM on this device? I'd love to know how the cameras performed.
Click to expand...
Click to collapse
A General System Image does not touch any of the Drivers or the Kernel since its an System Image non related to this Things. So it's the same as on Stock... (Except You would flash AOSP Vendors and Kernels as Base)
After i got a Xperia 1 III gifted by a Supporter i have checked how actual Android work. I have updated the Guides and fixed the issues for everyone hopefully... Enjoy!
Hi there I am coming from another phone where I was flashing AIO images for my updates. How does updating work with an Xperia Pro I once it has been rooted?
Also I am getting a 'no' on the bootloader unlock. What options do I have?
Miustone said:
Introducing this GuideHello there and welcome to My Guide for Your Xperia Smartphone. This Guide will walk with You thru the whole Process of installing Drivers, getting an unlock Key for Your Bootloader, rooting with Magisk and even flashing GSI Custom ROMs up to re-locking Your Bootloader and re-flashing Stock for the total Factory Reset. This Thread/Guide is not meant as Wiki n'or will it teach You about Android at all. Inform Yourself using Google to enjoy the total Freedom and Customization of Android... If You can't solve Problems Yourself, by communicating and research, don't touch Your Bootloader!
IMPORTANT:
2020+ Xperias are using fastbootd, and equivalent to fastboot which runs in Userspace (Same as Recoveries).
You can access Your Recovery on Your Xperia by holding VolumeDown (-) & the Powerbutton (Your Device needs to be turned off before ofc). Release the Powerbutton after the Display turned on and hold VolumeDown (-) until You see the Recovery Screen. From there, You can enter fastbootd and fastboot. Labled as "Fastboot" for fastbootd and "Bootloader" which is the old fastboot. You can flash Kernels, Recoveries and other stuff from fastboot. Everything else like System Images (GSIs for example), Product Images, System_ext Images and any Userspace stuff has to be flashed from fastbootd. 2019 Xperias are still using fastboot only...
Fastboot and Fastbootd has nothing to do with SONYs Flashmode on Xperias!
INDEX:
Requirements
Installing Drivers
Firmware Flashing
Bootloader Unlocking & Magisk Root
GSI ROM flashing with Fastboot (Optional)
Bootloader Re-Locking (TheWayBack)
Firmware Restoring after Re-Locking
1. Requirements:
Read! Inform Yourself about the Tools You use...
Xperia Basics:
Your Device is turned Off...
Blue LED=Fastboot (Hold VolumeUp (+) & Connect to USB)
Green LED=Flashmode (Hold VoumeDown (-) & Connect to USB)
Windows 10/11 for Firmware flashing & downloading
Xperia Bootloader Unlock Key (From HERE)
Platform Tools alias ADB and Fastboot (From HERE)
Fastboot and Flashmode Drivers (From HERE and HERE)
EMMA for Firmware Updates (From HERE)
XperiFirm for Firmware Downloads (From XDA)
Unsin to extract the Kernel .sin from XperiFirm (From XDA)
Magisk Manager to patch the extracted Kernel .sin (From GitHub)
A working Android System for the Magisk Kernel patching
GSI & vbmeta Image (From Google) (Optional)
A Backup of Your Internal Devices Storage (Optional)
2. Installing Drivers:
Download the Drivers from the Links above and extract them
Install the downloaded and extracted Drivers by right clicking on the ***.inf Files "Install"
3. Flashing Firmwares with EMMA:
Download EMMA and install it
Start EMMA and connect Your Device to USB (Flashmode)
3.1. Downloading Firmwares with XperiFirm:
Download and extract XperiFirm from the link above
Run XperiFirm and Download the right Firmware for Your Device
4. Bootloader Unlocking and Magisk Root:
Note: Since You are going to unlock Your Bootloader, You may surely want to get Root. So let's start with Magisk or it will take more Time afterwards...
Download UnSin from the link above and extract it somewhere
Download the "Platform Tools" from Google and extract it to the root of Your main Windows Drive
Download and install the Magisk Manager on Your Android Device
Extract the File boot_********.sin (60MB+ File) with the Unsin Exe (Drag and drop the Image on the Exe)
You will get a .img File which You can patch now with the Magisk Manager on Your Android Device
Open the Magisk Manager and Install Magisk by selecting the Image File You just got from UnSin
Copy the magisk_patched.img in /download from Your Device to the Platform Tools Folder
Grab Your Device again, go to "About Phone" in the Settings and tap several Times on the build Version
Go now to the Developer Settings under "System" and enable "OEM-Unlock" and "USB-Debugging"
Use now the Platform Tools with this Commands (In Powershell):
Type now (Step by Step):
Code:
cd\
cd platform-tools
Note: To use the Platform Tools Folder as environment for Fastboot and ADB. Or hold Shift and Make a right Click in the Platform Tools Folder to open the Command prompt there...
Type now:
Code:
adb reboot bootloader
You will get a prompt on Your Xperia Device. Your Device will Reboot afterwards...
Now Your Bootloader Unlock Code:
Code:
fastboot oem unlock 0xYOURKEY
Wait for it... And type now:
Code:
fastboot reboot
Wait for Your Device to Wipe and Start. Once in the Android System, turn Your Device off without USB Connected
Press and hold now the VolumeUp (+) Button while connecting to USB to enable the fastboot Mode
Continue with flashing the Images for Root (Step by Step):
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Wipe and Reboot:
Code:
fastboot -w
fastboot reboot
Note: Your are unlocked and rooted now! Enjoy Your Unleashed Device
5. GSI flashing with Fastboot:
Note: GSI ROMs can be found around the Web. Like here...
Treble-Enabled Device Development A/AB ROMS
Treble-Enabled Device Development A/AB ROMS
forum.xda-developers.com
Not all GSIs require the vbmeta change. You can use all GSIs that are made for ARM64 + A/B Devices. Play around. Systems can't damage Your Device since You keep the Stock Vendor & Kernel! You can use any Android Version! Don't forget to make backups if needed. You are going to Format Your Device!
Download a GSI Zip from Google
Extract the system.img and the vbmeta.img to Your Platform-Tools
Connect Your Device in Fastboot Mode and use Fastboot with:
(On 2020+ Xperias run: "fastboot reboot fastboot" first after You booted into fastboot)
Code:
fastboot flash system_a system.img
fastboot flash system_b system.img
[Optional] fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
[Optional] fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
fastboot -w (This does Format Your Device and is needed everytime You change the GSI!)
fastboot reboot
6. Bootloader Re-Lock:
Flash the latest Firmware for Your Device with EMMA
Erase all Userdata before You continue (like with fastboot -w or via Recovery)
Just go into Fastboot mode and type in the command prompt (like before in this Guide):
Code:
fastboot oem lock
Wait for Your Device and disconnect it from USB
Done... Continue with Step 7.
7. Firmware Restoring after Re-Locking:
Download and Install the "Xperia Companion" from SONY
Open the Xperia Companion and select Software Repair
Select that Your Device can't get recognized (or is a Smartwatch 3 lol)
Go to the next Page and select the Xperia Smartphone Option
Continue and wait for the Initialization
Press and hold Volume DOWN while connecting to USB (You will see the Green Flashmode LED again)
Continue once Your Device gets recognized and let the Xperia Companion do his work...
Done. Your Bootloader is locked again and almost all of Your DRMs are restored.
That helped? Leave a Thanks! <3
Donations are actually also really welcome!
Pay Marius Kopp using PayPal.Me
Go to paypal.me/miustone and type in the amount. Since it’s PayPal, it's easy and secure. Don’t have a PayPal account? No worries.
www.paypal.com
BTC: 3A93fjg2KxZJEHUpBExs7rVgivfAUumQoJ
ETH&ERC20-USDT: 0xD27860248B7E51720DDf9CA5a1f861CA1029c14A
ERC20: 0xD27860248B7E51720DDf9CA5a1f861CA1029c14A
Click to expand...
Click to collapse
Thanks for this information. I was just wondering if you know of anyone who has actually opened the bootloader on a Pro-I. When I go to the Sony website provided in your guide and tap Service info > Configuration > Rooting, Status, it returns "no" and that's as far as I get. Any suggestion will be appreciated.
When I do adb reboot bootloader I get no prompts but get thrown to fastboot (a black screen and blue LED).
After that any interaction will not work - after some digging it seems that my drivers work for ADB but not for fastboot. Device manager shows a device "other > android" which apparently means that the fastboot drivers are not working. I have tried disabling driver signatures and then installing them again with the phone connected in fastboot mode but that didin't help - am I trying to install the right drivers? I got the OEM drivers from Sony, a 2019 driver which installs from "sa0200adb.inf" that I got from https://developer.sony.com/file/download/xperia-pro-i-driver/
Kind of stuck here, but I've managed to solve a few roadblocks already so maybe I'll crack this one too, later...
Any help will be appreciated. ^^
(edit - figured out some basic stuff I got wrong, did more research and updated my issue acccordingly)
Tsuchimursu said:
When I do adb reboot bootloader I get no prompts but get thrown to fastboot (a black screen and blue LED).
After that any interaction will not work - after some digging it seems that my drivers work for ADB but not for fastboot. Device manager shows a device "other > android" which apparently means that the fastboot drivers are not working. I have tried disabling driver signatures and then installing them again with the phone connected in fastboot mode but that didin't help - am I trying to install the right drivers? I got the OEM drivers from Sony, a 2019 driver which installs from "sa0200adb.inf" that I got from https://developer.sony.com/file/download/xperia-pro-i-driver/
Kind of stuck here, but I've managed to solve a few roadblocks already so maybe I'll crack this one too, later...
Any help will be appreciated. ^^
(edit - figured out some basic stuff I got wrong, did more research and updated my issue acccordingly)
Click to expand...
Click to collapse
just didn't read my fastboot driver installation instructions carefully enough. Banged my head against a wal lfor a long while because I clicked the wrong thing in this step... Stupid newbie mistake but dropping my solution here anyway incase someone searches for this stuff with similar symptoms.
{
"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"
}
Garech said:
Thanks for this information. I was just wondering if you know of anyone who has actually opened the bootloader on a Pro-I. When I go to the Sony website provided in your guide and tap Service info > Configuration > Rooting, Status, it returns "no" and that's as far as I get. Any suggestion will be appreciated.
Click to expand...
Click to collapse
I have succesfully unlocked and installed magisk root on my Pro-I. Should work unless you have some weird version or haven't updated to latest firmware?
Try entering *#*#7378423*#*# in the dialer and it should state whether bootloader unlocking is allowed (and if it is currently unlocked).
Tsuchimursu said:
I have succesfully unlocked and installed magisk root on my Pro-I. Should work unless you have some weird version or haven't updated to latest firmware?
Try entering *#*#7378423*#*# in the dialer and it should state whether bootloader unlocking is allowed (and if it is currently unlocked).
Click to expand...
Click to collapse
Nothing weird - just a regular US model XQ-BE62. This is great news! You are the only person I have heard of that has rooted this phone. I may have mentioned this, but I am not into custom mods just for fun. In fact I'm kind of nervous about rooting, but I am beta testing an experimental app made for filming RAW video. Some other brands of phone are working, but the Pro-I throws a lot of dropped frames and has some restrictions on filming speed that I know the phone can handle. The devs say the issue is caused by Sony's restrictions on third party video apps and the Pro-I should function properly if rooted. Magisk appeals to me because (I think) I can unroot if I want to. I'll follow in your footsteps and see if I can do it.
Thanks very much.
Garech said:
Nothing weird - just a regular US model XQ-BE62. This is great news! You are the only person I have heard of that has rooted this phone. I may have mentioned this, but I am not into custom mods just for fun. In fact I'm kind of nervous about rooting, but I am beta testing an experimental app made for filming RAW video. Some other brands of phone are working, but the Pro-I throws a lot of dropped frames and has some restrictions on filming speed that I know the phone can handle. The devs say the issue is caused by Sony's restrictions on third party video apps and the Pro-I should function properly if rooted. Magisk appeals to me because (I think) I can unroot if I want to. I'll follow in your footsteps and see if I can do it.
Thanks very much.
Click to expand...
Click to collapse
I have a UK/EU model so we do have a difference, however it went easily for me except for own stupidity in fastboot driver installation.
I haven't done much yet beside root with magisk and purge facebook and google off my phone, but plan on playing some more in the future.
Tsuchimursu said:
just didn't read my fastboot driver installation instructions carefully enough. Banged my head against a wal lfor a long while because I clicked the wrong thing in this step... Stupid newbie mistake but dropping my solution here anyway incase someone searches for this stuff with similar symptoms.View attachment 5708441
Click to expand...
Click to collapse
I hope you don't mind helping me a bit. Here's what I get when I click Let me pick . . .
What did you do next?
Garech said:
I hope you don't mind helping me a bit. Here's what I get when I click Let me pick . . .
View attachment 5709903
What did you do next?
Click to expand...
Click to collapse
Oh, I just googled some guides on fastboot drivers... but you click "have disk" and then browse for google the USB driver .inf file
Garech said:
I hope you don't mind helping me a bit. Here's what I get when I click Let me pick . . .
View attachment 5709903
What did you do next?
Click to expand...
Click to collapse
by the way I'm a total noob so don't trust me blindly xD
One other thing that came to mind was that wipe from fastboot fails at metadata partition due to lack of permissions, and you'll get a loopboot and be thrown to recovery and there you can do a factory wipe and it will succesfully wipe the rest. That's what happened to me anyway.
Tsuchimursu said:
by the way I'm a total noob so don't trust me blindly xD
One other thing that came to mind was that wipe from fastboot fails at metadata partition due to lack of permissions, and you'll get a loopboot and be thrown to recovery and there you can do a factory wipe and it will succesfully wipe the rest. That's what happened to me anyway.
Click to expand...
Click to collapse
That's good to know. And I'm a noob too. I have rooted three phones over a period of time years ago and my heart was pounding the whole time. It is comforting to know that someone else has rooted this phone. As I said I am a beta tester for an experimental video app (MotionCam Pro - it's on the Play Store.). There's a small group of us who have the Pro-I and I have stupidly volunteered to try to root. One guy has already given up and returned his phone. I want to find out how this app can work with my phone. Filming in RAW (without dropped frames and lens errors) would be epic. I also DON'T WANT TO BRICK MY PHONE! Thanks for any help you can offer.
One question. I assume that Sony web site that tells me my phone can't be rooted is irrelevant if I have a working bootloader code, right?
Garech said:
That's good to know. And I'm a noob too. I have rooted three phones over a period of time years ago and my heart was pounding the whole time. It is comforting to know that someone else has rooted this phone. As I said I am a beta tester for an experimental video app (MotionCam Pro - it's on the Play Store.). There's a small group of us who have the Pro-I and I have stupidly volunteered to try to root. One guy has already given up and returned his phone. I want to find out how this app can work with my phone. Filming in RAW (without dropped frames and lens errors) would be epic. I also DON'T WANT TO BRICK MY PHONE! Thanks for any help you can offer.
One question. I assume that Sony web site that tells me my phone can't be rooted is irrelevant if I have a working bootloader code, right?
Click to expand...
Click to collapse
yeah it's scary, especially with low volume devices.
I'll have to look into that app, I'm a hobbyist photographer (surprise, given my choice of phone...)
I am a bit confused what page says your can't root a Sony pro-I, but their website will give you an unlock code with an imei of a pro-I and it sure worked for me...
You checked your service menu and your phone stated itself that the bootloader can be unlocked, right?
Also if you can't tick the oem unlocking toggle in dev options after updating firmware but not doing anything else yet, your device might need a factory reset.
I assume you've also backed up all your data and settings etc, you'll be wiping your phone while rooting.
Hi, I am currently on Stock android 12 and there is nothing I can do to reboot to Bootloader.
I tried all combinations of keys and adb reboot bootloader with differents drivers, usb ports, and adb versions.
Every time it boot into something with tiny letters for 1 sec and then instanly boot the system.
Any ideas ?
This is the tiny message I have
serial doesn't match
fastboot verify fail
Try searching. You're not the first one :]
Serial is not match fastboot unlock verify fail??
I am not able to open fastboot mode there is no fastboot mode available and showing this error in OnePlus Nord 2 5g
forum.xda-developers.com
Hey found THE solution to have fastboot and BROM. There is a rollback package to OOS 11 here. It works for all versions after C.05
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
community.oneplus.com
follow instructions from this video but use package from oneplus community
you need to have enabled developer options to see the local update button
Here's a simple guide on how to root a Moto X40/Edge 40 Pro for those who need root on their phones:
1. Download and install Motorola USB drivers here:
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?
en-us.support.motorola.com
2. Download and install Minimal ADB and Fastboot:
[TOOL]Minimal ADB and Fastboot [2-9-18]
Introduction ADB and Fastboot are arguably two of the most indispensable tools used when working with Android devices. If you really want to modify, debug, and tweak along with their countless uses in rooting, and other procedures ADB and...
forum.xda-developers.com
3. Download the ROM file and extract the init_boot.img file:
https://mirrors.lolinet.com/firmware/motorola/rtwo_retcn/official/RETCN/ (if you are running CN ROM)
https://mirrors.lolinet.com/firmware/motorola/rtwo/official/RETEU/ (if you are running EU ROM, or if you have converted your X40 to Edge 40 Pro)
4. Unlock bootloader through this site:
https://en-us.support.motorola.com/app/answers/detail/a_id/87215/~/what-devices-are-supported-by-the-bootloader-unlock-program?
Make sure to enable OEM unlocking through developer settings before unlocking the bootloader
Note: this will erase all data on your device, so take a data backup before doing so
5. On your device, download and install Magisk Manager:
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
6. Transfer the extracted init_boot.img file onto your phone and launch the Magisk app.
7. Tap the install button next to Magisk, and tap 'Select and Patch a file'.
8. Select the init_boot.img file you have extracted and transferred, and tap 'Let's Go' to patch init_boot.img.
9. The patched init_boot.img will be stored in the Downloads folder of your device. Transfer the init_boot.img to a convenient location on your PC.
10. Power down the device, and press and hold down the volume down and power button until fastboot mode appears
11. Connect a USB cable to the phone and a PC. Now open Minimal ADB and Fastboot.
12. Type:
Code:
fastboot devices
and press Enter. You should see your device ID appear, and if not try reinstall the USB drivers.
13. Type:
Code:
fastboot flash init_boot_a /path/to/patchedmagisk.img
Code:
fastboot flash init_boot_b /path/to/patchedmagisk.img
Code:
fastboot reboot
Your device should reboot and check for root by using Root Checker. If root is not working do try to repatch and reflash init_boot.img.
sooyong94 said:
3. Download the ROM file and extract the init_boot.img file:
https://mirrors.lolinet.com/firmware/motorola/rtwo_retcn/official/RETCN/ (if you are running CN ROM)
https://mirrors.lolinet.com/firmware/motorola/rtwo/official/RETEU/ (if you are running EU ROM, or if you have converted your X40 to Edge 40 Pro)
Click to expand...
Click to collapse
New firmware with April Patch released yesterday.
RETEU T1TR33.43-20-28
4.39 GB file on MEGA
mega.nz
or
RETEU_XT2301-4-DS 13 EURO 1 RTWO_G_T1TR33.43-20-28_subsidy-DEFAULT_regulatory-DEFAULT_cid50_CFC.xml.zip
drive.google.com
Source: https://www.stockrom.net/2023/05/xt2301-4-reteu-13-t1tr33-43-20-28.html