Related
Left with a bricked Wileyfox Swift that was originally running CM13. Tried to update to the nightly build from 20161118 and now have a bricked device which I can only access in fastboot (no recovery, no adb, no boot)
According to fastboot oem device-info I get this:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
I attempted to flash files one by one via fastboot using this guide:
http://forum.xda-developers.com/wileyfox-swift/help/stupid-bricked-phone-access-fastboot-t3414437/post67663025#post67663025
Got stuck on the last 4 files which are not in the cyanogen installer zip.
Can anyone tell me where I would find the last 4 files in that guide?
Cheers
LG-dudey said:
Left with a bricked Wileyfox Swift that was originally running CM13. Tried to update to the nightly build from 20161118 and now have a bricked device which I can only access in fastboot (no recovery, no adb, no boot)
According to fastboot oem device-info I get this:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
I attempted to flash files one by one via fastboot using this guide:
http://forum.xda-developers.com/wileyfox-swift/help/stupid-bricked-phone-access-fastboot-t3414437/post67663025#post67663025
Got stuck on the last 4 files which are not in the cyanogen installer zip.
Can anyone tell me where I would find the last 4 files in that guide?
Cheers
Click to expand...
Click to collapse
There are two Zips on the site one is for install by recovery the other by fastboot the two zips are not the same you need the fastboot one
Here is the new thread for brand new logos for our beloved condor.
Instructions
1-Rename file to logo.bin
2-Place logo.bin file to fastboot folder
3-Reboot to bootloader
4-Type the following command:
fastboot flash logo logo.bin
fastboot reboot
5-Thats it.
Credits
1-Motorola
Me
Download
MotoE1stGEN
Note:
You guys can request as per your requirement and I'll try to fulfill your desire as I'll have a spare time.
Thank You.
Hi Guys! I appreciate any help or orientation to find out how should I proceed,
I don't know why my phone just got Brick yesterday, it was running fine for two months since the last Room's flash, suddenly I notice an estrange behavior of the system, then the capacitive buttons were not responding nor its backlit appear when I touch them, the home button and the fingerprint and everything else was working fine, so I think that with a simple Reboot it will be back to normality. For my disgrace, it enter in a Bootloop in the HTC logo screen and for my surprise when I manage to get to the Bootloader and try to enter to the Download and Recovery mode get me to the same HTC logo Bootloop!!
The principal suspect for me is that like 15 days ago a installed the TotallyFreeVPN app to see some Japanese Netflix
To complicate the things I want to make my phone thefts proof, so I disable usb debugging and OEM unlocking and installed Cerberus with the option of block usb debugging and also in security I enable the encrypted data option for every reboot or when enter in recovery.
My only hope is that you know if something can be done from the Bootloader to unbricked?
I attach the only two screens I have access right now
HTC 10
Firmware 2.41.401.4
Leedroid V3.6.1
Unlocked Bootloader
S-OFF
TWRP 2.8.4
I manage to run some fastboot commands from Bootloader, getvar all give me the following:
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:HT64EBN02616
flash a stock ruu
If your phone will still power on, it's not bricked.
BrianKuo1853 said:
flash a stock ruu
Click to expand...
Click to collapse
I wish I could, but I can´t enter in download mode, recovery or oem rebootRUU, all send me to the bootloop, after looking around I find this post that manage to solve a similar brick
https://forum.xda-developers.com/showpost.php?p=69874694&postcount=18
But in the last step when I put the micro sd card with the RUU file, nothing happens in my case, I thinks is because I didn't have USB debugging before the brick happen, but meaby the solution works for others.
I´ll keep trying
Thanks for any other ideas :good:
ALOMAJEMO said:
I wish I could, but I can´t enter in download mode, recovery or oem rebootRUU, all send me to the bootloop, after looking around I find this post that manage to solve a similar brick
https://forum.xda-developers.com/showpost.php?p=69874694&postcount=18
But in the last step when I put the micro sd card with the RUU file, nothing happens in my case, I thinks is because I didn't have USB debugging before the brick happen, but meaby the solution works for others.
I´ll keep trying
Thanks for any other ideas :good:
Click to expand...
Click to collapse
with s-off you can flash all images in bootloader of a firmware.
Flash the images in that order:
Code:
fastboot flash aboot aboot_signed.img
fastboot flash adsp adsp.img
fastboot flash apdp apdp-8996-1.img
fastboot flash cache cache.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cota cota.img
fastboot flash devcfg devcfg-8996-1.img
fastboot flash dsp dsp.img
fastboot flash fsc fsc.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8996-1.img
fastboot flash keymaster keymaster.img
fastboot flash lksecapp lksecapp.img
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8996-1.img
fastboot flash rcdata rcdata.img
fastboot flash recovery recovery.img
fastboot flash rfg rfg_3.img
fastboot flash rpm rpm-8996-1.img
fastboot flash slpi slpi.img
fastboot flash tz tz-8996-1.img
fastboot flash venus venus.img
fastboot flash xbl xbl-8996-1.img
fastboot flash radio radio.img
Grab the firmware.zip from @Sneakyghost Thread..ensure you take the one you were on
Yeah and use the full version, not the NoWipe...
I am wondering if you were able to solve it... I am having the same issue. Tried the same you tried (although as I am s-on I could only flash hosd like the guy on the other post) but no luck at all. The funniest thing is that I've never tocuhed this phone (no s-off, no unlock, no custom recovery, just updated via OTA to get Nougat), it just ran out of battery during the night and got the boot loop the morning after when I plugged it in to charge. Cant believe it could turn into a f''ing brick by itself.
j to the 4n said:
with s-off you can flash all images in bootloader of a firmware.
Flash the images in that order:
Code:
fastboot flash aboot aboot_signed.img
fastboot flash adsp adsp.img
fastboot flash apdp apdp-8996-1.img
fastboot flash cache cache.img
fastboot flash cmnlib32 cmnlib32.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash cota cota.img
fastboot flash devcfg devcfg-8996-1.img
fastboot flash dsp dsp.img
fastboot flash fsc fsc.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8996-1.img
fastboot flash keymaster keymaster.img
fastboot flash lksecapp lksecapp.img
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8996-1.img
fastboot flash rcdata rcdata.img
fastboot flash recovery recovery.img
fastboot flash rfg rfg_3.img
fastboot flash rpm rpm-8996-1.img
fastboot flash slpi slpi.img
fastboot flash tz tz-8996-1.img
fastboot flash venus venus.img
fastboot flash xbl xbl-8996-1.img
fastboot flash radio radio.img
Grab the firmware.zip from @Sneakyghost Thread..ensure you take the one you were on
Click to expand...
Click to collapse
Sneakyghost said:
Yeah and use the full version, not the NoWipe...
Click to expand...
Click to collapse
Thank for your tips guys,
I follow exactly the order you suggest my good j to the 4n, and I download the firmware from your useful thread Sneakyghost, but still, I can not get it out of the Bootloop my friends
Dont you think my case is very strange?
If it serves for any other suggestion, I I add the following details
-The only image that is not flashing is rcdata, everything else is flashing OK
-I buy a microsd card class 10 of 32GB only to discard that the old microsd card of 3GB was not reading the RUU zip file.
-I optained the zip file, from the RUU.exe with the same version of the firmware 2.41.401.4 (the full version) and I copying it from the Temp files in Windows.
-With the microSD in FAT32 format I put the RUU zip file with the 2PS6IMG.zip name
-After flashing all the img files and rebooting to bootloader, then I inserted the card and select Download mode, where is supposed should appear the screen that jichuan89 mention to flash the RUU, but again nothing happen.
-Also I should say that I try also with the firmware and RUU version 2.41.617.3 (the corresponding for my model 2PS6500 in the back) but the last I have was the 2.41.401.4 with superCID and cidnum change it to HTC-001.
-And also among the hundreds of attempts I have executed fastboot erase userdata, erase cache, erase system, to try to clean any corrupt file.
Do you think there is any hope yet?
Once again thank you for your support guys!:good::good:
singlemalt said:
I am wondering if you were able to solve it... I am having the same issue. Tried the same you tried (although as I am s-on I could only flash hosd like the guy on the other post) but no luck at all. The funniest thing is that I've never tocuhed this phone (no s-off, no unlock, no custom recovery, just updated via OTA to get Nougat), it just ran out of battery during the night and got the boot loop the morning after when I plugged it in to charge. Cant believe it could turn into a f''ing brick by itself.
Click to expand...
Click to collapse
Not yet, but I start to think that having s-off or s-on makes no difference in the weight of our bricks If humor is any good LOL
ALOMAJEMO said:
Not yet, but I start to think that having s-off or s-on makes no difference in the weight of our bricks If humor is any good LOL
Click to expand...
Click to collapse
Haha...we have two bricks for the wall now...do you know if Donald would cover shipping costs from Argentina?
curious if anyone know how to view the firmware if cannout access downlad mode
venom55521 said:
curious if anyone know how to view the firmware if cannout access downlad mode
Click to expand...
Click to collapse
Dude, I'm answering your questions as we speak and still making new threads. Didn't you get the total picture about cross posting. If you never posted anywhere you should open a Q&A, I'm on it and i see this.
I'm pretty much done i guess........
Mr Hofs said:
Dude, I'm answering your questions as we speak and still making new threads. Didn't you get the total picture about cross posting. If you never posted anywhere you should open a Q&A, I'm on it and i see this.
I'm pretty much done i guess........
Click to expand...
Click to collapse
my bad,i was looking around for info and ideas and just had a question when i was reading it
venom55521 said:
my bad,i was looking around for info and ideas and just had a question when i was reading it
Click to expand...
Click to collapse
Please pick up a sledgehammer and smash your device....... it's the best for all of us.
Mr Hofs said:
Please pick up a sledgehammer and smash your device....... it's the best for all of us.
Click to expand...
Click to collapse
i realize you help a lot people out which is appreciated ,but being rude is pointless
venom55521 said:
i realize you help a lot people out which is appreciated ,but being rude is pointless
Click to expand...
Click to collapse
Your interpretation of the situation. I'm honest, not rude.
Flashing signed stock firmware:
You need:
Latest signed stock firmware:
Europe (RETEU):
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
India (RETIN):
https://mirrors-obs-2.lolinet.com/f...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
US (RETUS):
https://mirrors-obs-2.lolinet.com/f...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
All other firmwares and locations:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Also:
flashallO.bat:
https://drive.google.com/file/d/1Ne7Kps25heUO7wsJ0Z4_X43eKQYRegoa/view?usp=sharing
Motorola drivers (Device Manager - former LMSA):
Motorola Device Manager
Motorola Device Manager, free download for Windows. Program to transfer data between Motorola devices and computers, update software and backup files.
motorola-device-manager.en.lo4d.com
Tiny ADB & Fastboot v1.4.0 signed;
Tiny_ADB_&_Fastboot_v1.4.0-signed.exe | Tool by K3V1991 for Misc. Software & Hardware Resources
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
1) Download the 8.1.0_OPS28.85-17-6-2 firmware for your region (it's the last one for the Moto G5+ (potter), there won't be any updates anymore, so no risk of bootloader downgrading)
2) Install Tiny ADB & Fastboot (best place is the root directory of C: or wherever your OS resides).
3) Extract the firmware to that ADB & Fastboot folder.
4) Download my "flashallO.bat" and move it to that folder too.It removes the need for you to manually flash all partitions, just double-click it and it'll run all the commands for you.
5) Download and install Motorola device drivers.The program is called "Motorola Device Manager".
6) Reboot your phone to the bootloader. To do this, turn it off, then hold down the power and volume down buttons until you see a bugdroid undergoing open-heart surgery.
7) Connect the phone to your PC with your USB cable. Type
Code:
fastboot devices
to check if your device is connected. A serial number should be shown.
8) Run the flashallO.bat script. (Caution: This will wipe your device completely!) It will take some time to flash, just be patient and don't worry.
If the command window appears for a brief moment and then disappears, the device drivers may not be installed correctly. You can ask me in that case, there are some special drivers that may solve that.
9) Once the command window closes, it should have completed the flashing process and you are safe to press the power key on the phone to start Android. Just make sure that the text near the buttons reads "START".
That's it.
You can save your (internal) data when you open the flashallO.bat and delete the command
Code:
fastboot erase userdata
so that it will be omitted.
I won't recommend it but it's possible.
Rooting:
You need:
Magisk 24.1:
https://github.com/topjohnwu/Magisk/releases/download/v24.1/Magisk-v24.1.apk
If you have problems with the newer Magisk builds (since v24) you may try
Magisk 23:
https://github.com/topjohnwu/Magisk/releases/tag/v23.0
or
Magisk 20.4: https://github.com/topjohnwu/Magisk/releases/tag/v20.4
TWRP 3.5.2_9-0:
https://eu.dl.twrp.me/potter/twrp-3.5.2_9-0-potter.img
Maybe you'll need:
Disable_Dm-Verity_ForceEncrypt.zip:
https://yadi.sk/d/HLr5vjnkA8gaqw
- Download TWRP from the above link and place it in your ADB & Fastboot folder.
- Download magisk.zip (and Magisk Manager APK if you use version 20.4) and place it in your internal storage.
- Turn the phone off again and reboot to bootloader using previously mentioned key combination.
- Navigate to the folder where you placed the TWRP image.
- Hold down the "shift" key and right-click anywhere in the Explorer window,it should give you an option to "Open command window here."
- Now input the command:
Code:
fastboot flash recovery [filename].img
, where [filename] is the name of your TWRP image file. Tap Enter and it will take a few seconds to flash the new recovery.
- Alternatively, you can use "fastboot boot [filename].img" to temporarily boot TWRP for the purpose of flashing Magisk. This retains the stock recovery.
- Now that TWRP has been flashed, press the volume down key until you see the label on the side change to read "RECOVERY." At that point you can press the power button and you will boot right into TWRP.
- If you decide to decrypt your device:
In that case go to "Wipe" in TWRP and use "format data" (the option where you have to confirm with "yes"). Just wipe data is not enough!
- If you want your device to stay encrypted skip that step.
- Now press the "Install' button in TWRP and navigate to the location where the magisk.zip is located. Simply tap it and "Swipe to install."
- If you decided to decrypt your device normally magisk should take care that it doesn't get encrypted again.
Magisk only disables the enforced encryption flag, the device will still be encrypted and that's why a wipe of data is necessary to remove the encryption.
If that's not the case and you get problems to reboot flash Disable_Dm-Verity_ForceEncrypt.zip after magisk.zip.
More information about decryption/encryption:
https://didgeridoohan.com/magisk/Magisk#hn_Disabling_dm-verity_and_forced_encryption
- Reboot your device, if the Magisk Manager isn't installed already (it should) install the Magisk Manager APK.
Thanks to @Jrhotrod for parts of the rooting tutorial.
Edit: Updated Links again.(1-2022)
My 3 year old Moto G5 Plus running android 8 suddenly restarted a few days ago and went into Start up failure. It no longer shows My product or IMEI number. It just shows potter 000000000000000 32GB P3B
Bootloader logs read " Start up failure. Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant" written in red.
I have my IMEI and product numbers saved on my pc in a notepad file, but the LMSA software does not recognise my device to even try to rescue it. I want to retrieve files from my phone before attempting a factory reset.
On using the LMSA, it says "lmsa doesn't match appropriate firmware. you can try to select a firmware manually" but then it has no option to select anything manually. I have my phone previously registered on the software on my PC.
I have not rooted my phone, nor used anything other than stock android. My bootloader is locked. I cannot remember if I had Developer options selected or not, most probably not.
On trying to go to recovery mode it says the same message " Start up failure. Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant"
When I connect the phone to the computer, it recognises it (I hear a notification sound) and under Devices it shows under Unrecognised as "Fastboot potter s"
I've never flashed my phone but would it be possible to recover the files in the internal storage of the phone by installing TWRP (in a non rooted, bootloader locked phone) without data loss?
How does it work?
Please help! I really need to recover my photos and notepad notes. Is there any way? Any software?
Is there any way to flash stock ROM without losing data? I haven't attempted anything in the off chance that there is a way to recover internal storage data. It's absolutely essential to me. I don't care about the phone, I'm gonna replace it anyway.
If I can even switch on the phone for long enough to backup data from the phone, it will be enough.
I read in another thread that downgrading a Moto with a locked bootloader will hard brick the device. This thread. My bootloader/oem is locked. I've attached a screenshot from when I once connected my phone to LMSA a few weeks before it crashed, it showed my current version I was running at the time. I never got around to taking a backup of the phone, then.
These are the screens I get. I try to charge the phone in fastboot every day to keep it from dying completely.
I'm desperate.
Also Lolinet seems to be down. I tried to download RETIN firmware from the link you provided, but I only get
404 Not Found
nginx
What to do now?
I downloaded the firmware from Motorola Stock Room. Will that do?
I downloaded the firmware from Motorola Stock Room. Will that do?
[/QUOTE]
DwightKBrute said:
Also Lolinet seems to be down. I tried to download RETIN firmware from the link you provided, but I only get
404 Not Found
nginx
What to do now?
I downloaded the firmware from Motorola Stock Room. Will that do?
Click to expand...
Click to collapse
I also recognised that lolinet.mirrors has some problems but it seems it's been working on it (see attached screenshot).
The firmware from Motorola Stock ROM should work, it's the same build and also the last firmware for the Moto G5+ so no risk of bootloader downgrading.
Let me know if you were successful.
{
"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"
}
Edit: No way to save your data from an unroofed device with locked bootloader, I'm sorry.
You can omit the "fastboot erase userdata" command (see above thread) to save your internal storage when flashing the firmware but as you have problems with your device a complete clean start may be the only solution. But you can give it a try.
Wolfcity said:
I downloaded the firmware from Motorola Stock Room. Will that do?
Click to expand...
Click to collapse
I also recognised that lolinet.mirrors has some problems but it seems it's been working on it (see attached screenshot).
The firmware from Motorola Stock ROM should work, it's the same build and also the last firmware for the Moto G5+ so no risk of bootloader downgrading.
Let me know if you were successful.
View attachment 5162915
[/QUOTE]
I will follow your instructions on this post.
The download from the Motorola stock room has adb, flashboot and everything else (including a .bat file) in its folder.
How can I use your .bat file (from the link you provided) instead of the one from Motorola Stock Room?
Also I want to preserve the internal storage, so I can erase the fastboot erase userdata command. But how do I open the .bat file? There is no open with option.
Also since I'm missing my IMEI and SKU, should I keep the erase modemst1 and fastboot erase modemst2 commands in the file?
DwightKBrute said:
I also recognised that lolinet.mirrors has some problems but it seems it's been working on it (see attached screenshot).
The firmware from Motorola Stock ROM should work, it's the same build and also the last firmware for the Moto G5+ so no risk of bootloader downgrading.
Let me know if you were successful.
View attachment 5162915
Click to expand...
Click to collapse
I will follow your instructions on this post.
The download from the Motorola stock room has adb, flashboot and everything else (including a .bat file) in its folder.
View attachment 5162925
View attachment 5162923
How can I use your .bat file (from the link you provided) instead of the one from Motorola Stock Room?
Also I want to preserve the internal storage, so I can erase the fastboot erase userdata command. But how do I open the .bat file? There is no open with option.
View attachment 5162927
[/QUOTE]
Copy this content and put it into a notepad:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Delete the fastboot erase userdata line and save it as .bat file (if your notepad has no option to save it as .bat save it as .txt and change the ending from .txt to .bat by hand).
And deactivate your Windows Defender when doing that and also when using the .bat file.
Wolfcity said:
I will follow your instructions on this post.
The download from the Motorola stock room has adb, flashboot and everything else (including a .bat file) in its folder.
View attachment 5162925
View attachment 5162923
How can I use your .bat file (from the link you provided) instead of the one from Motorola Stock Room?
Also I want to preserve the internal storage, so I can erase the fastboot erase userdata command. But how do I open the .bat file? There is no open with option.
View attachment 5162927
Click to expand...
Click to collapse
Copy this content and put it into a notepad:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Delete the fastboot erase userdata line and save it as .bat file (if your notepad has no option to save it as .bat save it as .txt and change the ending from .txt to .bat by hand).
And deactivate your Windows Defender when doing that and also when using the .bat file.
[/QUOTE]
So let me just recheck the steps.
1. Downloaded the firmware from Motorola Stock Room
2. Downloaded and installed Mini Adb.
3. Extracted the firmware to the same folder as the mini adb
4. Deleted the .bat file already present in the extracted firmware folder from MSR. Replaced that with the .bat file you have provided.
5. Erase userdata command removed.
6. Run the .bat file.
7. Wait for flashing to complete
Yes?
DwightKBrute said:
I also recognised that lolinet.mirrors has some problems but it seems it's been working on it (see attached screenshot).
The firmware from Motorola Stock ROM should work, it's the same build and also the last firmware for the Moto G5+ so no risk of bootloader downgrading.
Let me know if you were successful.
View attachment 5162915
Click to expand...
Click to collapse
I will follow your instructions on this post.
The download from the Motorola stock room has adb, flashboot and everything else (including a .bat file) in its folder.
View attachment 5162925
View attachment 5162923
How can I use your .bat file (from the link you provided) instead of the one from Motorola Stock Room?
Also I want to preserve the internal storage, so I can erase the fastboot erase userdata command. But how do I open the .bat file? There is no open with option.
View attachment 5162927
[/QUOTE]
Download (or copy) my flashallO.bat file delete,the erase userdata line
DwightKBrute said:
Copy this content and put it into a notepad:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Delete the fastboot erase userdata line and save it as .bat file (if your notepad has no option to save it as .bat save it as .txt and change the ending from .txt to .bat by hand).
And deactivate your Windows Defender when doing that and also when using the .bat file.
Click to expand...
Click to collapse
So let me just recheck the steps.
1. Downloaded the firmware from Motorola Stock Room
2. Downloaded and installed Mini Adb.
3. Extracted the firmware to the same folder as the mini adb
4. Deleted the .bat file already present in the extracted firmware folder from MSR. Replaced that with the .bat file you have provided.
5. Erase userdata command removed.
6. Run the .bat file.
7. Wait for flashing to complete
Yes?
[/QUOTE]
Sounds ok. The bat file has to be copied into the ADB & Fastboot folder (mini ADB) too.
Deactivate Defender and start the bat file.
Be patient.
And collect as many data from the flashing process as possible (screenshots etc.)
Well. I wasn't able to get many screenshots, it happened too quickly. But the phone is still stuck on fastboot, but this time the fastboot reason is given as: Last time flashing failed.
Oh well. I'll try again without removing the flashboot erase userdata?
failed to validate recovery image
DwightKBrute said:
Well. I wasn't able to get many screenshots, it happened too quickly. But the phone is still stuck on fastboot, but this time the fastboot reason is given as: Last time flashing failed.
Oh well. I'll try again without removing the flashboot erase userdata?
failed to validate recovery image
Click to expand...
Click to collapse
Seems your device has problems to erase partitions before flashing new stuff to them. Maybe search for blankflash files.
Where to find the blankflash file?
DwightKBrute said:
Where to find the blankflash file?
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/potter/
Hello. I have a rooted Moto G5 Plus (Magisk) and I have also installed a Custom ROM with TWRP. I want to unroot the device and return it to absolute stock. Will this guide work in that case? If no, can anyone direct me to the correct guide?
DEJAVU54 said:
Hello. I have a rooted Moto G5 Plus (Magisk) and I have also installed a Custom ROM with TWRP. I want to unroot the device and return it to absolute stock. Will this guide work in that case? If no, can anyone direct me to the correct guide?
Click to expand...
Click to collapse
The above guide https://forum.xda-developers.com/t/guide-moto-g5-plus-flashing-stock-firmware-rooting-2021.4205293/ should be helpful for you. Flashing the latest signed stock firmware as described in the first part will take you to absolute stock.
A few points to take care of:
- Make sure that you chose the correct firmware for your location.
- Don´t delete the fastboot erase userdata command from the flashallO.bat so that it will be omitted because some parts of Magisk or other root apps may reside at that location.
- You have to erase everything to be on the safe side.
- So save your internal userdata like pictures, documents, music etc. to a PC or a SD card before you start the
process!
- Flashing stock will overwrite the recovery.img (TWRP) and the boot.img (Magisk) so you don´t have to unroot or reflash stock recovery.
If you want to relock your bootloader too (remember that you won´t get to the "nerver unlocked" state again, the device will flag the bootloader as "has been unlocked" even when you lock it):
-After flashing stock firmware open a command prompt in the ADB & Fastboot folder again and give the following commands one by one or use the attached relockO.bat file. the same way you did it with the flashallO.bat:
relockO.bat:
relockO.bat
drive.google.com
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash boot boot.img
fastboot oem lock
You can do that anytime, it hasn´t to be right after the firmware flash.
I flashed the ROM today and everything went well, except the IMEI is 0 and I cannot use VoLTE. What can I do?
DEJAVU54 said:
I flashed the ROM today and everything went well, except the IMEI is 0 and I cannot use VoLTE. What can I do?
Click to expand...
Click to collapse
What does getvar all say?
post it here after you remove imei line.
Code:
fastboot getvar all
sd_shadow said:
What does getvar all say?
post it here after you remove imei line.
Code:
fastboot getvar all
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY2244FVLG
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 10E5EE5600000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) meid:
(bootloader) date: 05-23-2017
(bootloader) sku: XT1686
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Aug 30 2:39:28 UTC 1973"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:8.1.0/O
(bootloader) ro.build.fingerprint[1]: PSS28.85-13-3/72e4:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.201.4.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8953_41.50.07.82u POTTER_INDIADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g70fa69f (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Wed Oct 10 11:58:58 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VC0.92-0-gd009c3b
(bootloader) rpm.git: git=92e5e21-dirty
(bootloader) tz.git: git=26cc248-dirty
(bootloader) devcfg.git: git=26cc248-dirty
(bootloader) keymaster.git: git=26cc248-dirty
(bootloader) cmnlib.git: git=26cc248-dirty
(bootloader) cmnlib64.git: git=26cc248-dirty
(bootloader) prov.git: git=26cc248-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retin
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.062s
DEJAVU54 said:
I flashed the ROM today and everything went well, except the IMEI is 0 and I cannot use VoLTE. What can I do?
Click to expand...
Click to collapse
Have you ever flashed someone else's persist file?
Wolfcity said:
Have you ever flashed someone else's persist file?
Click to expand...
Click to collapse
No I have not. Only the PixelExp zip and now, the stock rom.
Anyways, after panicking a bit yesterday, I flashed the custom rom again and my IMEI and LTE returned, but I cannot place/receive calls. What can be done if I wanted to stay on the ROM but gain calling capabilities?
EDIT: I'd prefer to have everything working on the stock ROM if possible.
Motorola Moto G Power (2022)
XT2165-5 US Retail Variant
Codename: Tonga
{
"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"
}
Rooting GuideOVERVIEW:
This guide outlines simple step-by-step instructions for rooting the Moto G Power (2022). To alleviate some of the legwork, and to cater this guide to new and inexperienced members, I have provided boot images pre-patched for the Magisk v26.1 systemless root solution. In addition, for those members who prefer the Android 11 stock ROM over Android 12, I am providing patched boot images for both the Android 11 and Android 12 firmware builds. (It has been reported that upgrading to Android 12 breaks Widevine L1 and reverts to Widevine security level L3.)
When downloading a patched boot image per the below instructions, be sure to choose the boot image that corresponds with both your installed Android version and firmware build number.
COMPATIBILITY:
The supplied Magisk patched boot images in the downloads section below are from both the Android 11 and Android 12 based firmware builds for the XT2165-5 US Retail Tonga variant. In theory, these boot images may work on rooting other variants as well, but I have only tested them on the referenced retail variant. To ensure compatibility, unless you are rooting this particular retail variant, procure the boot image from your variant and firmware build. Tonga official firmware for all carrier models and variants is available from the Lolinet repo here Tonga Official Firmware: Lolinet Repo
PREREQUISITES:
In order to root your Moto G Power (2022), you will need an unlocked bootloader and a Windows PC or laptop with the ADB & fastboot tools installed. I have included a link in the downloads section below for the latest Minimal ADB & Fastboot tools for Windows. This procedure can be carried out on a Mac or Linux setup as well; however, for purposes of this guide, I will focus on a Windows setup. Windows 7/8.1/10/11 will suffice. You will also need the factory supplied, or a quality equivalent USB-A to USB-C syncing/charging cable.
If you have not yet unlocked your bootloader, head on over to this tutorial and do so.
Motorola Bootloader Unlocking Tutorial
Please be sure and thank XDA Recognized Contributor @sd_shadow for his comprehensive and easy-to-follow tutorial on bootloader unlocking Motorola mobile devices. It is, hand down, the most thorough and detailed guide on this procedure, and is highly recommended to those members who are unfamiliar with the topic.
Keep in mind that not all carrier variants of the Tonga are supported for bootloader unlocking. For example, if you own the Verizon, AT&T or TracFone branded Moto G Power (2022), among some other carrier variants, your bootloader is not officially supported for unlocking and, as such, rooting may not to be an option. However, it should be noted that most MediaTek chipset models can be exploited by a reverse engineering tool called MTK Client which, among many other things, can force the bootloader into an unlocked state. Whether the MTK Client exploit can be used on any of these locked down Tonga models & variants is unknown to me. It wouid, perhaps, be worth researching more if you own such a variant of the Tonga.
The tutorial link I provided above will help you make the determination as to whether your variant is officially supported for unlocking. If you own a Retail variant, your bootloader can be unlocked via Motorola's official support portal. Again, the link I posted above will guide you in this regard. Simply return here once you have successfully unlocked your bootloader.
ANDROID VERSIONS & FIRMWARE BUILDS
The boot images provided in the downloads section below have been patched with Magisk v26.1 for systemless root support. The Android 11 boot image corresponds with the last official firmware released prior to the Android 12 update rollout. The patched boot image for Android 12 corresponds with the latest firmware build available for the Tonga at the time of posting. Specifically,
The Android 11 boot Image corresponds with firmware build no. RRQS31.03-68-153-2
The Android 12 boot image corresponds with firmware build no. S3RQ32.20-42-10-9-4
To prevent boot loops, bugs and potential issues with compatibility, flash only a patched boot image that matches the firmware version presently installed on your Tonga. Hence, if your installed firmware build version differs from the version of the patched boot image referenced above, it is highly advised that you obtain a stock boot image that corresponds with your firmware version, patch the image with the latest Magisk app, then flash it to your Tonga via the fastboot commands outlined below.DISCLAIMER:
Rooting an Android-based mobile device is a task that encompasses inherent risks. Failure to follow the instructions as written, for example, could result in your device being rendered inoperable, stuck in a boot loop, etc. Rooting will also void any active Motorola warranty you may have on your smartphone. (However, as set forth on the Motorola support portal, your warranty is void once you complete the bootloader unlocking procedure.)
By proceeding further, you are assuming full responsibility and sole liability for the integrity and operability of your Moto G Power (2022). I am hereby absolved of any responsibility or civil liability in the event something goes wrong. Follow the instructions carefully, employ some patience, and things should go smoothly. I encourage members to read this guide in its entirety PRIOR to actually starting the steps.
INSTRUCTIONS:
Download the Minimal ADB & Fastboot tools from the link below and install it on your Windows PC or laptop. Next, open Windows File Explorer, open This PC and double click on your C: drive. Locate and open the Program Files x86 folder and locate the Minimal ADB & Fastboot folder. Copy the folder and paste it to your desktop. (Copying the folder to your desktop is not mandatory, but is recommended. This configures your ADB & Fastboot directory to a more convenient location from which to work.);
Download the Motorola Device Manager software from the link below, in accordance with your Windows OS architecture (32 or 64 bit), and install it on your PC or laptop. This software installs the most current USB device drivers for your Moto device;
Download the patched boot image below that corresponds with the Android OS & firmware build version currently running on your device. Save the image inside the ADB & Fastboot directory on your PC or laptop;
Boot your device into AP Fastboot Mode by first powering off your smartphone and then pressing Power + Volume Down simultaneously for about 8 seconds, or until AP Fastboot Mode appears on your phone display;
Connect your Tonga to your Windows computer using the OEM supplied, or a quality equivalent USB-A to USB-C data syncing/charging cable;
Open the Minimal ADB & Fastboot folder you copied to the desktop in Step 1. Double click the cmd-here file to launch a command window;
To verify proper fastboot communication between your phone and computer, execute this command:
Code:
fastboot devices
If properly connected, the command window will return with an alphanumeric string that corresponds with your device serial number;
If your serial number isn't displayed, or if you receive a Waiting message, there is an issue with fastboot mode communication between your phone and PC/laptop. Try changing USB ports, try another data syncing cable, and/or update the fastboot drivers on your PC or laptop. If your phone remains unrecognized by fastboot, skip down to the next section titled Fix Fastboot Recognition Issues, and follow those steps.
Once a proper connection has been verified, it's time to flash the patched boot image to your phone. Execute this command:
Code:
fastboot flash boot patched_boot.img
Take note that the patched boot images linked below are both named patched_boot.img. These instructions assume that you leave the filename unchanged.
Upon reboot to the Android OS, go to your app drawer and open the Magisk app or its placeholder stub. Grant any permissions requested, and follow any prompts to upgrade Magisk to the full version and complete setup of the root environment. Magisk may reboot your device to finalize the setup. If you do not see the Magisk app or the stub, download the Magisk v26.1 APK from the official Magisk GitHub repo I have linked below, and install it on your Tonga.
That's it. You should now be rooted via the Magisk systemless root solution.
FIX FASTBOOT RECOGNITION ISSUES:
This section is provided to assist members with troubleshooting device recognition issues via fastboot mode. If you have already tried a different USB-A to USB-C data syncing/charging cable, as well as a different USB port, and your Tonga persists to be unrecognized in fastboot mode, follow these steps:
Keeping your device connected to your Windows PC/laptop from Step 8 above, and ensuring your device is still in fastboot mode, right click your Windows Start icon and select Device Manager. Locate your Tonga in the menu. It will likely be located under either the Portable Devices or Android Device heading;
Right click your device and select Update Driver. Next, select Browse My Computer for Drivers. On the next screen choose the option for Let Me Pick From a List... Now you will see a list of drivers to select from. Depending on the manner in which Windows recognized your Tonga in the Device Manager menu, the driver selection list can vary. If you see an option for Android Device or Android Phone, select either option, and then select either Android Composite ADB Interface or Android Bootloader Interface. Or, you may be directly presented with options for Android Bootloader Interface, Android ADB Interface and Android Composite ADB Interface. In any event, choose Android Composite ADB Interface or, in the alternative, Android Bootloader Interface, and then click Next. Click Yes in the Update Driver Warning dialogue screen, at which time the drivers will be installed.
Return to your command window and again execute the fastboot devices command. If your serial number is displayed, your drivers are now properly installed. Return to the instructions in the previous heading and proceed to Step 9.
DOWNLOADS:
• Motorola Device Manager V2.5.4
• Minimal ADB & Fastboot Tools v1.4.3
• Official GitHub Magisk Releases
• Patched boot.img (Android 11 Stock OS)
• Patched boot.img (Android 12 Stock OS)
• Official Tonga Firmware / All Variants
THANKS & MENTIONS:
A big thanks to @sd_shadow for his excellent tutorial on Unlocking/Relocking Motorola bootloaders. Also, thanks to @jhjhjhjhjhjh for his comprehensive thread on the Moto G Power (2022), packed with specs, general info, mods & some other valuable resources for Tonga owners. Check out his thread here Moto G Power (2022)
Last but not least, a big thanks to @Needsimunlocked, for Magisk patching and sharing the stock boot image corresponding with firmware build S3RQ32.20-42-10-9-4. My Tonga is presently hard bricked, so this was of great help in my efforts to keep this guide up to date with a patched boot image from the latest available firmware package.
Nice detailed Guide! Just want to point out that you don't need to flash boot a and b with magisk. Just fastboot flash boot boot.img.
Also, Updating to 12 will break widevine L1. If you don't mind L3, go ahead. Personally it pisses me off.
Every version of firmware has the same apps on it. They're all full of carrier apps and bloat so flashing retail firmware won't change anything like the older Moto phones. I personally have deleted maybe 200 apps from stock including their corresponding overlays. If you use EX kernel manager there is a Hexicore mode on a12. You won't find this on other kernel managers. Also, I suggest deleting the live wallpaper app as it will make the device ridiculously slow
Yeedatoy said:
Nice detailed Guide! Just want to point out that you don't need to flash boot a and b with magisk. Just fastboot flash boot boot.img.
Also, Updating to 12 will break widevine L1. If you don't mind L3, go ahead. Personally it pisses me off.
Every version of firmware has the same apps on it. They're all full of carrier apps and bloat so flashing retail firmware won't change anything like the older Moto phones. I personally have deleted maybe 200 apps from stock including their corresponding overlays. If you use EX kernel manager there is a Hexicore mode on a12. You won't find this on other kernel managers. Also, I suggest deleting the live wallpaper app as it will make the device ridiculously slow
Click to expand...
Click to collapse
Great feedback. Thanks for sharing. I believe my next project will be fully debloating.a retail firmware package and then posting a guide for installing it via fastboot. Yes, I agree that flashing to boot_a & boot_b is not required. However, I have encountered instances where members are using way outdated fastboot binaries that don't automatically flash the active slot, so I got into the habit of instructing for both slots as a precaution. ( Even though I do provide a link for a fairly recent fastboot binary, not every member follows instructions.)
That's good info on Widevine L1 breaking on the Windows 12 update. I sure didn't know that. Thanks for the tip on a12 EX Kernel Manager as well.
Thanks again for your valuable feedback & input. I'll certainly use this info on my debloated firmware project, including that cursed live wallpaper app. Hate that RAM consuming thing.
In fact, if you could dump a super.img on your debloated setup, I would of course credit the work to you in my upcoming guide. Thanks again.
.im following everything to the T but when i flash patched_boot.img i get
i also tried flashing it while on the previous fastboot screen , and i get the same but the fail reason is no such file or directory
im using the patched boot img supplied on post for android 12
how do i fix this?
keezeysqueezey said:
.im following everything to the T but when i flash patched_boot.img i get
View attachment 5878959
i also tried flashing it while on the previous fastboot screen , and i get the same but the fail reason is no such file or directory
im using the patched boot img supplied on post for android 12
Click to expand...
Click to collapse
No such file
Viva La Android said:
No such file
Click to expand...
Click to collapse
Seems like an error with the fastboot path. But out of curiosity, what version of fastboot are you using? And I do need to ask, are you certain that your bootloader is in an unlocked state?
Viva La Android said:
Seems like an error with the fastboot path. But out of curiosity, what version of fastboot are you using? And I do need to ask, are you certain that your bootloader is in an unlocked state?
Click to expand...
Click to collapse
not sure fastboot version ? whichever comes on moto g power , and yes bootloader is unlocked 100%
keezeysqueezey said:
not sure fastboot version ? whichever comes on moto g power , and yes bootloader is unlocked 100%
Click to expand...
Click to collapse
I meant, did you install the Minimal ADB & Fastboot tools from the link I provided, or are you using another configuration of tools?
well the minimal fastboot u posted says corrupted , but im using the same version from elsewhere ...wait a sec....leme try something....... ok so, if i try to open the patched boot img , it also says corrupted
keezeysqueezey said:
well the minimal fastboot u posted says corrupted , but im using the same version from elsewhere ...wait a sec....leme try something....... ok so, if i try to open the patched boot img , it also says corrupted
Click to expand...
Click to collapse
You can't open an Android boot.img using the native Windows File Explorer. You need an image extractor such as Carliv Image Kitchen or SuperR's Kitchen. Also, both patched boot images have been thoroughly tested and verified with md5 checksums. I double-checked all files available on the links I posted. No files are corrupt.
I just downloaded and installed the Minimal ADB & Fastboot tools from my link as well with no problems.Not sure why it's showing corrupt on your system.
Ok, did you follow Step 1 entirely and copy the Minimal ADB & Fastboot folder from your C: drive and paste it to your desktop? This is the folder where you must save the patched boot image you downloaded from the link I provided.
While connected in fastboot mode, execute the following command and post the command prompt output here.
Code:
fastboot getvar all
This will let me know why fastboot is returning an Invalid partition name for the /boot partition.
< waiting for device >
(bootloader) cpu-abi:arm64-v8a
(bootloader) snapshot-update-status:none
(bootloader) super-partition-name:super
(bootloader) is-logical: preloader_raw_b:no
(bootloader) is-logical: preloader_raw_a:no
(bootloader) is-logical: vendor_boot_a:no
(bootloader) is-logical : vendor_boot_b:no
(bootloader) is-logical: para:no
(bootloader) is-logical: misc:no
(bootloader) is-logical: boot_b:no
(bootloader) is-logical: metadata:no
(bootloader) is-logical: userdata:no
(bootloader) is-logical: mmcblk0:no
(bootloader) is-logical: boot_a:no
(bootloader) is-logical: md_udc:no
(bootloader) is-logical: super:no
(bootloader) is-logical: system_ext_a:yes
(bootloader) is-logical: product_a:yes
(bootloader) is-logical: vendor_a:yes
(bootloader) is-logical:system_a:yes
(bootloader) is-logical:system_ext_a-cow:yes
(bootloader) is-logical: product_a-cow:yes
(bootloader) is-logical: vendor_a-cow:yes
(bootloader) is-logical: system_a-cow:yes
(bootloader) battery-voltage:0
(bootloader) treble-enabled:true
(bootloader) is-userspace:yes
(bootloader) partition-size:reloader_raw_b:0x3FF800
(bootloader) partition-size:reloader_raw_a:0x3FF800
(bootloader) partition-size:vendor_boot_a:0x4000000
(bootloader) partition-size:vendor_boot_b:0x4000000
(bootloader) partition-size: para:0x80000
(bootloader) partition-size: misc:0x80000
(bootloader) partition-size: boot_b:0x2000000
(bootloader) partition-size: metadata:0x2000000
(bootloader) partition-size: userdata:0xC26CF8000
(bootloader) partition-size: mmcblk0:0xE8F800000
(bootloader) partition-size: boot_a:0x2000000
(bootloader) partition-size: md_udc:0x169A000
(bootloader) partition-size: super:0x220000000
(bootloader) partition-size: system_ext_a:0x36CD4000
(bootloader) partition-size: product_a:0x13312B000
(bootloader) partition-size: vendor_a:0x1F6DB000
(bootloader) partition-size: system_a:0x3B5BF000
(bootloader) partition-size:system_ext_a-cow:0x132EB000
(bootloader) partition-size: product_a-cow:0x12DF6000
(bootloader) partition-size: vendor_a-cow:0x13FD1000
(bootloader) partition-size: system_a-cow:0x213B5000
(bootloader) version-vndk:31
(bootloader) has-slot: preloader_raw:yes
(bootloader) has-slot: vendor_boot:yes
(bootloader) has-slot: para:no
(bootloader) has-slot:hw:no
(bootloader) has-slot: prodpersist:no
(bootloader) has-slot: utagsBackup:no
(bootloader) has-slot: cid:no
(bootloader) has-slot: misc:no
(bootloader) has-slot:l ogs:no
(bootloader) has-slot:frp:no
(bootloader) has-slot:boot:yes
(bootloader) has-slot:metadata:no
(bootloader) has-slot:utags:no
(bootloader) has-slot:userdata:no
(bootloader) has-slot:mmcblk0:no
(bootloader) has-slot:md_udc:no
(bootloader) has-slot:super:no
(bootloader) has-slot:system_ext:yes
(bootloader) has-slot: product:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:system:yes
(bootloader) has-slot:system_ext_a-cow:no
(bootloader) has-slot: product_a-cow:no
(bootloader) has-slot:vendor_a-cow:no
(bootloader) has-slot:system_a-cow:no
(bootloader) security-patch-level:2023-02-01
(bootloader) vendor-fingerprint:motorola/tonga_g/tonga:12/S3RQS32.20-42-1
(bootloader) 0-9-2/2e26e:user/release-keys
(bootloader) hw-revision: PVT
(bootloader) current-slot:a
(bootloader) serialno:ZY22GB5PSJ
(bootloader) product:tonga
(bootloader) version-os:12
(bootloader) first-api-level:30
(bootloader) slot-count:2
(bootloader) max-download-size:0x10000000
(bootloader) version:0.4
(bootloader) version-baseband:
(bootloader) secure:yes
(bootloader) dynamic-partition:true
(bootloader) system-fingerprint:motorola/tonga_g/tonga:12/S3RQS32.20-42-1
(bootloader) 0-9-2/2e26e:user/release-keys
(bootloader) version-bootloader:MBM-2.1-tonga_g-794044bf81-230129
(bootloader) unlocked:yes
all:
finished. total time: 1.691s
So your active boot slot is slot _a. Use this command to flash the patched boot image.
Code:
fastboot flash boot_a patched_boot.img
Viva La Android said:
So your active boot slot is slot _a. Use this command to flash the patched boot image.
Code:
fastboot flash boot_a patched_boot.img
Click to expand...
Click to collapse
awesome, thank u ! it worked , thanks again
keezeysqueezey said:
awesome, thank u ! it worked , thanks again
Click to expand...
Click to collapse
No problem friend. The problem was, the version of fastboot tools you were using does not automatically detect and flash your active slot. In such a scenario, the active slot must be specified during flashing. I realize you had trouble installing the fastboot tools I linked above and had to find tools elsewhere.
Anyway, glad you got it.
The Minimal ADB/Fastboot Tools version is very, very outdated! You should use the link to Google's platform tools. The page is currently not available but should be online in the next hours.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
WoKoschekk said:
The Minimal ADB/Fastboot Tools version is very, very outdated! You should use the link to Google's platform tools. The page is currently not available but should be online in the next hours.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Click to expand...
Click to collapse
The Minimal ADB & Fastboot tools, while outdated, are fully sufficient for tasks such as bootloader unlocking and flashing Magisk patched boot images to achieve root. If this threat involved more in-depth command lines, such as those used in the newer dynamic FastbootD userspace mode, the platform tools would surely be needed. But for the rudimentary tasks encompassed in this guide, Minimal ADB & Fastboot works great.
I also have problems with the installation of your ADB/Fastboot Tools. Execution of the file leads to:
Yes, you are right. This version will flash any device as good as the current version. But every user will get the same error as in post #4 because this version of fastboot can't handle A/B slots and many other functions released since 2013.
see MOD EDIT at the end of the post:
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
WoKoschekk said:
I also have problems with the installation of your ADB/Fastboot Tools. Execution of the file leads to:
View attachment 5880235
Yes, you are right. This version will flash any device as good as the current version. But every user will get the same error as in post #4 because this version of fastboot can't handle A/B slots and many other functions released since 2013.
see MOD EDIT at the end of the post:
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for your feedback and reporting the issue with the fastboot tools. I'll upload another copy and change the link.
Minimal ADB & Fastboot does indeed support A/B partitioning and automatically flashes your active boot slot without the need to specify boot_a or boot_b. That particular member had issues because he didn't use Minimal ADB & Fastboot. He used another fastboot tools implementation because, like you, he was unable to install the Minimal tools due to an error. @WoKoschekk , if you don't mind doing so, I would ask you to validate my position on this and flash your device using Minimal ADB & Fastboot using the exact instructions I have outlined. I'm 99% certain on my position but I need to be 100% sure when providing instructions in tutorials. I'm traveling and cannot test this myself or I would do it. I will post a new link for the tools shortly. Thanks again for your valuable feedback and for validating this, if you don't mind doing it. It would be a huge help.
Minimal ADB & Fastboot has been fixed and an updated link posted.
thx, can now be installed without problems