Related
I recently rooted my Sprint Nexus 6 and everything was going fine. But then I started to run into issues when running the disabling the decryption. I was able to resolve those and install Pure Rom and customize it to my liking before taking a backup. But I logged into my WiFi immediately when setting up that phone. Soon after I turned off the wifi when stepping out, and I saw an Exclamation Point show up next to what was previously a semi full signal strength meter. I tried calling a few numbers and nothing was working.
I updated my PRL to the latest prior to rooting, etc. I know that this is a risk when you root, but does anyone know a possible solution?
My Recovery, ADB, Fastboot and everything works, I just can't get the signal.
I have also tried to update with the factory image from google:
https://developers.google.com/android/nexus/images
It does seem to update the Radio and a few other things, but ultimately fails:
pkalaria-ltm:tools pkalaria$ bash ./flash-all.sh
< waiting for device >
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.121s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.378s]
finished. total time: 0.499s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (67170 KB)...
OKAY [ 2.109s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 0.905s]
finished. total time: 3.015s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(96115,0xa11b21a8) malloc: *** mach_vm_map(size=1681272832) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1679592636 bytes
error: update package missing system.img
pkalaria-ltm:tools pkalaria$
Click to expand...
Click to collapse
Any help is appreciated, thanks.
Pl2lNCE said:
I recently rooted my Sprint Nexus 6 and everything was going fine. But then I started to run into issues when running the disabling the decryption. I was able to resolve those and install Pure Rom and customize it to my liking before taking a backup. But I logged into my WiFi immediately when setting up that phone. Soon after I turned off the wifi when stepping out, and I saw an Exclamation Point show up next to what was previously a semi full signal strength meter. I tried calling a few numbers and nothing was working.
I updated my PRL to the latest prior to rooting, etc. I know that this is a risk when you root, but does anyone know a possible solution?
My Recovery, ADB, Fastboot and everything works, I just can't get the signal.
I have also tried to update with the factory image from google:
https://developers.google.com/android/nexus/images
It does seem to update the Radio and a few other things, but ultimately fails:
Any help is appreciated, thanks.
Click to expand...
Click to collapse
I'm also on Sprint and had the same issue myself, I thinking that since these ROMs are so new that maybe they need our APNs added or something.
Maybe there is another way around this issue for the time being but I didn't investigate it further, I just didn't have time.
Mistertac said:
I'm also on Sprint and had the same issue myself, I thinking that since these ROMs are so new that maybe they need our APNs added or something.
Maybe there is another way around this issue for the time being but I didn't investigate it further, I just didn't have time.
Click to expand...
Click to collapse
I found a workaround, you can manually flash the images inside image-shamu-lrx21o.zip:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
Click to expand...
Click to collapse
I just flashed the decrypted boot.img, system, userdata, and cache and I was good to go. Fresh install of Stock Rom without Envrcption., and I was able to Update the PRL/Device Config. Now just gotta get it set up and Root again.
Hi Folks,
Need some help here. I'm new to flash and other stuff.
I tried to install Lineage 15.1. I did fastboot oem unlock which erased everything. I'm stuck in AP fastboot Flash Mode.
I tried below things.
C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot.exe flash system lineage-15.1-20180402-nightly-shamu-signed.zip
< waiting for any device >
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (498496 KB)...
OKAY [ 18.385s]
writing 'system'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition system
FAILED (remote failure)
finished. total time: 18.400s
C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot.exe flash recovery twrp-3.2.1-0-shamu.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (12027 KB)...
OKAY [ 0.391s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.406s
C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot.exe boot twrp-3.2.1-0-shamu.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
OKAY [ 0.422s]
booting...
OKAY [ 0.031s]
finished. total time: 0.469s
[PHONE GETS TWRP RECOVERY SCREENS]
I tried adb sideload as suggested in one of the pages and got this
C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>adb sideload lineage-15.1-20180402-nightly-shamu-signed.zip
Total xfer: 0.01x
In Phone :
Starting ADB sideload feature ..
Installing zip file '/sideload/package.zip'
Warning: No file_contexts
Target : google/shamu/shamu:7.1.1/N6F27m/4299435:user/release-keys
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: Failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Invalid Argument
Failed to unmount /system : No such volume
script aborted (no error message)
Updater process ended with ERROR: 7
Finally, I tried with copying installer files in OTG Drive and tried to install from there. But couldn't mount it as I can't make OTG check in Mount in TWRP.
Please help .. How can I overcome this and install OS in my phone.
Can you boot into twrp?? When i flashed my shamu first time...i unlocked bootloader, flashed twrp, rooted and then via twrp flashed roms from zips, gapps and magisk. As far as i remember. Otg is some times really tricky...i tried several usb sticks and suddenly one worked and i got forward in flashing. Nowadays my pc recognise my shamu in twrp and i can move files in it (if needed). Hope that helps.
mal13 said:
Can you boot into twrp?? When i flashed my shamu first time...i unlocked bootloader, flashed twrp, rooted and then via twrp flashed roms from zips, gapps and magisk. As far as i remember. Otg is some times really tricky...i tried several usb sticks and suddenly one worked and i got forward in flashing. Nowadays my pc recognise my shamu in twrp and i can move files in it (if needed). Hope that helps.
Click to expand...
Click to collapse
Yes, I can boot into twrp using this command...
fastboot.exe boot twrp-3.2.1-0-shamu.img
This bringstwrp in my phone. But I can't move files to the phone. Even I tried adb push which pushes the files to the phone but while installing it got failed.. I'm not sure what I'm missing..
I think the problem is the fastboot you are using is not compatible with shamu. See if this minimal install works any better; [TOOL]Minimal ADB and Fastboot. Try one of the older releases, maybe 1.4 or 1.3.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
I think the problem is the fastboot you are using is not compatible with shamu. See if this minimal install works any better; [TOOL]Minimal ADB and Fastboot. Try one of the older releases, maybe 1.4 or 1.3.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Same issue with Minimal ADB. I used 1.4 ...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.2.1-0-shamu.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (12027 KB)...
OKAY [ 0.391s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.406s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system lineage-15.1-20180402-nightly-shamu-signed.zip
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (498496 KB)...
OKAY [ 15.628s]
writing 'system'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition system
FAILED (remote failure)
finished. total time: 15.644s
vigkumar said:
Same issue with Minimal ADB. I used 1.4 ...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.2.1-0-shamu.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (12027 KB)...
OKAY [ 0.391s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.406s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system lineage-15.1-20180402-nightly-shamu-signed.zip
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (498496 KB)...
OKAY [ 15.628s]
writing 'system'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition system
FAILED (remote failure)
finished. total time: 15.644s
Click to expand...
Click to collapse
Looks to me that my filesystem on is corrupt. Is there any commands to fix the filesystem. I tried with repair in TWRP but that is also not working.
vigkumar said:
Looks to me that my filesystem on is corrupt. Is there any commands to fix the filesystem. I tried with repair in TWRP but that is also not working.
Click to expand...
Click to collapse
When in doubt, my philosophy is to return to stock and start over. If you have any data on the user data partition, back it up through ADB and then try fastboot flashing the last google stock ROM. The instructions (if you need them) are on the Factory Image page. If Fastboot still fails, you can try sideloading through ADB an Full OTA.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
When in doubt, my philosophy is to return to stock and start over. If you have any data on the user data partition, back it up through ADB and then try fastboot flashing the last google stock ROM. The instructions (if you need them) are on the Factory Image page. If Fastboot still fails, you can try sideloading through ADB an Full OTA.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Thank you very much for your response. I tried both Fastboot and ADB. Both failed Well, I suppose if I could flash the right radio 'D4.01-9625-05.45+FSG-9625-02.117', I guess Fastboot would work. Am I right.
What is the right way to identify the correct radio file.
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.016s]
checking version-baseband...
FAILED
Device version-baseband is 'D4.01-9625-05.51+FSG-9625-02.118'.
Update requires 'D4.01-9625-05.45+FSG-9625-02.117'.
finished. total time: 0.094s
ADB devices produces nothing. Hence I booted in twrp and use ADB sideload from there.
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot boot twrp-3.2.1-0-shamu.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
OKAY [ 0.432s]
booting...
OKAY [ 0.038s]
finished. total time: 0.469s
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>adb sideload shamu-ota-n6f27m-df27bd83.zip
Total xfer: 0.01x
Even it got failed with the below error.
Installing zip file '/sideload/package.zip'
Target: google/shamu/shamu:7.1.1/N6F27M/4299435:user/release-keys
Patching system image unconditionally...
E1001: Failed to update system image.
Updater Process ended with Error 7.
vigkumar said:
Thank you very much for your response. I tried both Fastboot and ADB. Both failed Well, I suppose if I could flash the right radio 'D4.01-9625-05.45+FSG-9625-02.117', I guess Fastboot would work. Am I right.
What is the right way to identify the correct radio file.
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.016s]
checking version-baseband...
FAILED
Device version-baseband is 'D4.01-9625-05.51+FSG-9625-02.118'.
Update requires 'D4.01-9625-05.45+FSG-9625-02.117'.
finished. total time: 0.094s
ADB devices produces nothing. Hence I booted in twrp and use ADB sideload from there.
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot boot twrp-3.2.1-0-shamu.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
OKAY [ 0.432s]
booting...
OKAY [ 0.038s]
finished. total time: 0.469s
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>adb sideload shamu-ota-n6f27m-df27bd83.zip
Total xfer: 0.01x
Even it got failed with the below error.
Installing zip file '/sideload/package.zip'
Target: google/shamu/shamu:7.1.1/N6F27M/4299435:user/release-keys
Patching system image unconditionally...
E1001: Failed to update system image.
Updater Process ended with Error 7.
Click to expand...
Click to collapse
Radio makes no difference. You can run any radio from any release on any release. It affects only the data/cell connection and sometimes an older one forces better performance depending on carrier and location.
Try fastboot flashing with the sim card removed.
The manual steps to flash through fastboot are in the [GUIDE][HOW TO] Flash Factory Images thread. Scroll down to "Method 2 : (Long, but works always)".
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
vigkumar said:
C:\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot.exe flash system lineage-15.1-20180402-nightly-shamu-signed.zip
Click to expand...
Click to collapse
That was your first error! You can't flash a nightly via fastboot.
You need to boot into recovery and select it there to install.
ktmom said:
Radio makes no difference. You can run any radio from any release on any release. It affects only the data/cell connection and sometimes an older one forces better performance depending on carrier and location.
Try fastboot flashing with the sim card removed.
The manual steps to flash through fastboot are in the [GUIDE][HOW TO] Flash Factory Images thread. Scroll down to "Method 2 : (Long, but works always)".
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Both method failed. :crying::crying:
vigkumar said:
Both method failed. :crying::crying:
Click to expand...
Click to collapse
You are trying to fastboot flash the STOCK ROM I linked to earlier, right?
As @Elektroschmock pointed out -and I originally missed- your first mistake was trying to fastboot flash the lineage ROM. You also CAN NOT ADB sideload anything except the OTA stock image linked to earlier. That includes the stock ROM used to fastboot flash, or any custom ROM.
** If ** you really are trying to fastboot flash stock, and it doesn't work, what does:
Code:
fastboot devices
return?
The N6 is a simple device to work with and very forgiving, but you must use common sense and think about what your doing.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
You are trying to fastboot flash the STOCK ROM I linked to earlier, right?
As @Elektroschmock pointed out -and I originally missed- your first mistake was trying to fastboot flash the lineage ROM. You also CAN NOT ADB sideload anything except the OTA stock image linked to earlier. That includes the stock ROM used to fastboot flash, or any custom ROM.
** If ** you really are trying to fastboot flash stock, and it doesn't work, what does:
Code:
fastboot devices
return?
The N6 is a simple device to work with and very forgiving, but you must use common sense and think about what your doing.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Yes, I'm trying stock and followed links that you provided. Both installation methods failed.
Fastboot devices returns,
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\platform-tools>fastboot devices
ZX1G525DZX fastboot
Extract the zip file downloaded from the factory image page. For example, downloaded file is "shamu-n6f27h-factory-718e138f.zip" then when extracted I get a folder "shamu-n6f27h".
Navigate into the extracted folder (e.g "shamu-n6f27h")
Now copy the radio-shamu-XXXXXX.img (the x's are placeholders it depends on the radio version) to the location where your fastboot is then rename it to just "radio.img"
Back in the originally extracted folder ("shamu-n6f27h"), there will be another zip file, in my example it's "image-shamu-n6f27h.zip". Extract that and I end up with a folder "image-shamu-n6f27h".
Now copy the following files from the new folder (e.g. "image-shamu-n6f27h") to the location where your fastboot is;
boot.img
cache.img
recovery.img
system.img
userdata.img
Navigate on the PC to the location where the fastboot binary is.
Boot the phone into fastboot by pushing and holding the volume down and power buttons
Look on the phone's screen and there should be a message "Device is unlocked. Status Code 3" confirming the bootloader is unlocked.
Double check that "fastboot devices" returns your device.
Now type "fastboot reboot-bootloader", which will power off the phone and start it again in the same place. Just double checking that you are communicating correctly with the device.
Code:
1) flash the boot image (also called the kernel):
fastboot flash boot boot.img
reboot:
fastboot reboot-bootloader
2) If you want, you can flash the radio:
fastboot flash radio radio.img
reboot:
fastboot reboot-bootloader
3) flash recovery:
fastboot flash recovery recovery.img
reboot:
fastboot reboot-bootloader
4) flash system partition:
fastboot flash system system.img
reboot:
fastboot reboot-bootloader
5) flash userdata (which will wipe the internal storage:
fastboot flash userdata userdata.img
reboot:
fastboot reboot-bootloader
6) flash cache:
fastboot flash cache cache.img
Now we are done flashing all of the partitions on a N6 so reboot to system:
fastboot reboot
If any of these fail, or don't match what I described above, post the exact errors here, preferably formatted within CODE tags. They look like: [ CODE ] [ / CODE ] without any spaces inside the brackets. The spaces are necessary to prevent the forum from executing the example as formating tags.
Posting "it doesn't work" may be funny, but it does nothing to help others help you. You must be specific as to what you were doing and what happened.
ktmom said:
Extract the zip file downloaded from the factory image page. For example, downloaded file is "shamu-n6f27h-factory-718e138f.zip" then when extracted I get a folder "shamu-n6f27h".
Navigate into the extracted folder (e.g "shamu-n6f27h")
Now copy the radio-shamu-XXXXXX.img (the x's are placeholders it depends on the radio version) to the location where your fastboot is then rename it to just "radio.img"
Back in the originally extracted folder ("shamu-n6f27h"), there will be another zip file, in my example it's "image-shamu-n6f27h.zip". Extract that and I end up with a folder "image-shamu-n6f27h".
Now copy the following files from the new folder (e.g. "image-shamu-n6f27h") to the location where your fastboot is;
boot.img
cache.img
recovery.img
system.img
userdata.img
Navigate on the PC to the location where the fastboot binary is.
Boot the phone into fastboot by pushing and holding the volume down and power buttons
Look on the phone's screen and there should be a message "Device is unlocked. Status Code 3" confirming the bootloader is unlocked.
Double check that "fastboot devices" returns your device.
Now type "fastboot reboot-bootloader", which will power off the phone and start it again in the same place. Just double checking that you are communicating correctly with the device.
Code:
1) flash the boot image (also called the kernel):
fastboot flash boot boot.img
reboot:
fastboot reboot-bootloader
2) If you want, you can flash the radio:
fastboot flash radio radio.img
reboot:
fastboot reboot-bootloader
3) flash recovery:
fastboot flash recovery recovery.img
reboot:
fastboot reboot-bootloader
4) flash system partition:
fastboot flash system system.img
reboot:
fastboot reboot-bootloader
5) flash userdata (which will wipe the internal storage:
fastboot flash userdata userdata.img
reboot:
fastboot reboot-bootloader
6) flash cache:
fastboot flash cache cache.img
Now we are done flashing all of the partitions on a N6 so reboot to system:
fastboot reboot
If any of these fail, or don't match what I described above, post the exact errors here, preferably formatted within CODE tags. They look like: [ CODE ] [ / CODE ] without any spaces inside the brackets. The spaces are necessary to prevent the forum from executing the example as formating tags.
Posting "it doesn't work" may be funny, but it does nothing to help others help you. You must be specific as to what you were doing and what happened.
Click to expand...
Click to collapse
Thanks a lot for your assistance on this. I followed your exact instructions and it is given below.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>dir *.img
Volume in drive C is Windows8_OS
Volume Serial Number is 40E0-62B9
Directory of C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools
01-01-2009 00:00 8,686,822 boot.img
01-01-2009 00:00 6,398,184 cache.img
26-09-2017 16:53 118,279,680 radio.img
01-01-2009 00:00 14,206,186 recovery.img
01-01-2009 00:00 1,619,795,140 system.img
01-01-2009 00:00 142,201,816 userdata.img
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot devices
ZX1G525DZX fastboot
You're right. Initially it was DEVICE is UNLOCKED. Status Code 3.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot reboot-bootloader
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.085s]
finished. total time: 0.085s
Once reboots, it says DEVICE IS LOCKED. Status Code 2. I had to long press the power key, which unlocks the DEVICE.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (8483 KB)...
OKAY [ 0.285s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 0.338s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash radio radio.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:radio: not found
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.737s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash modem
FAILED (remote failure)
finished. total time: 3.774s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (13873 KB)...
OKAY [ 0.580s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.617s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash system system.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending sparse 'system' 1/4 (522524 KB)...
OKAY [ 18.848s]
writing 'system' 1/4...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 18.901s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash userdata userdata.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
target reported max download size of 536870912 bytes
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.037s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash cache cache.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
target reported max download size of 536870912 bytes
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.016s
vigkumar said:
Thanks a lot for your assistance on this. I followed your exact instructions and it is given below.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>dir *.img
Volume in drive C is Windows8_OS
Volume Serial Number is 40E0-62B9
Directory of C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools
01-01-2009 00:00 8,686,822 boot.img
01-01-2009 00:00 6,398,184 cache.img
26-09-2017 16:53 118,279,680 radio.img
01-01-2009 00:00 14,206,186 recovery.img
01-01-2009 00:00 1,619,795,140 system.img
01-01-2009 00:00 142,201,816 userdata.img
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot devices
ZX1G525DZX fastboot
You're right. Initially it was DEVICE is UNLOCKED. Status Code 3.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot reboot-bootloader
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.085s]
finished. total time: 0.085s
Once reboots, it says DEVICE IS LOCKED. Status Code 2. I had to long press the power key, which unlocks the DEVICE.
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (8483 KB)...
OKAY [ 0.285s]
writing 'boot'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition boot
FAILED (remote failure)
finished. total time: 0.338s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash radio radio.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:radio: not found
target reported max download size of 536870912 bytes
sending 'radio' (115507 KB)...
OKAY [ 3.737s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash modem
FAILED (remote failure)
finished. total time: 3.774s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (13873 KB)...
OKAY [ 0.580s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.617s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash system system.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending sparse 'system' 1/4 (522524 KB)...
OKAY [ 18.848s]
writing 'system' 1/4...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 18.901s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash userdata userdata.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
target reported max download size of 536870912 bytes
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.037s
Code:
C:\Users\Vignesh\Downloads\Nexus\platform-tools-latest-windows\Latest\platform-tools>fastboot flash cache cache.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
target reported max download size of 536870912 bytes
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.016s
Click to expand...
Click to collapse
Couple of questions.
You are working on a Nexus 6, right? Not a 6P or other device?
Did you reboot between each img flash? When you returned to the bootloader each time after rebooting, did you long press the power button because it still said "locked status 2"?
I have to say, this is the first I've ever heard of a reboot causing it to be locked then long pressing the power button to unlock. Either the bootloader is unlocked or it isn't.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
---------- Post added at 14:03 ---------- Previous post was at 14:00 ----------
Additional question, when you reboot using only the key combination, does it always show unlocked?
If yes to that, maybe it's back to my concern that the version of fastboot is not working well with the N6.
If you haven't, try with the minimal version you downloaded the other day.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
I
vigkumar said:
Both method failed. :crying::crying:
Click to expand...
Click to collapse
1] If u can get to twrp, use microUSB flash drive and move ROMs over to flash via TWRP. Must mount OTG drive in TWRP after plugin to recognize flash drive
2) if u can get to fastboot mode and your PC recognizes your device via "fastboot device" command, try using WUG NRT tool kit to restore back to stock, then root @ND put TWRP on there, then flash custom Roms via TWRP
novice here. screwed up my 6p and got in a similar place as you are. i started adb side load in my phone and linux pc terminal, adb start-server, then adb sideload [add a space] then i dragged and dropped the factory firmware to terminal then enter. i had to try a couple of googles angler firmware before it found the the right format. saved my bacon.
Good point. If fails on Windows, Linux PC may work
Is there any way to downgrade the anroid pie to oreo
Download this to PC, this using the second link https://forum.xda-developers.com/showpost.php?p=79122632&postcount=45
BECKHAM_OPWS28.70_47_8_subsidy_DEFAULT_regulatory_ DEFAULT_CFC.xml
Using these instructions https://forum.xda-developers.com/z3-play/how-to/firmware-oficial-9-0-0-pie-instalacion-t3911995 :good:
I am considering doing this and taking the official Pie OTA, the Pie download here wont allow for updates.
Is the process to go back to Oreo 8.0 the same as the installation of Android foot?
bruney.melo said:
Is the process to go back to Oreo 8.0 the same as the installation of Android foot?
Click to expand...
Click to collapse
I dont know what Android foot is?
But I just downgraded my phone from Pie to Oreo following the instructions.
https://forum.xda-developers.com/z3...l-9-0-0-pie-instalacion-t3911995#post79284837
Just change this line to all lower case or you will get an error
"fastboot erase DDR" I got an error unless I typed it in lower case "fastboot erase ddr."
I also heeded this warning, and you should do the same unless you have a TWRP backup of the partitions.
Notes:
- These commands can be omitted to avoid having problems with the telephone signal (it is unlikely to happen but it is good to prevent)
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
want to go back to Android Oreo. I'm following the thread you sent, but I'm having trouble using adb fastboot, always the error.
Droid_Nut said:
I dont know what Android foot is?
But I just downgraded my phone from Pie to Oreo following the instructions.
https://forum.xda-developers.com/z3...l-9-0-0-pie-instalacion-t3911995#post79284837
Just change this line to all lower case or you will get an error
"fastboot erase DDR" I got an error unless I typed it in lower case "fastboot erase ddr."
I also heeded this warning, and you should do the same unless you have a TWRP backup of the partitions.
Notes:
- These commands can be omitted to avoid having problems with the telephone signal (it is unlikely to happen but it is good to prevent)
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
need to have the bootloader unlocked? here says that the device was not found.
'' (bootloader) max-download-sizer: not found
target didn't report max-download-size
sending 'partition' (37 KB)...''
bruney.melo said:
want to go back to Android Oreo. I'm following the thread you sent, but I'm having trouble using adb fastboot, always the error.
Click to expand...
Click to collapse
Did you do an initial connected with the system booted, developer options>adb debugging, and connect to your PC by typing adb devices, and getting the prompt in your phone? And when you put the phone in fastboot mode, type fastboot devices to make sure your phone is connected, it will return the serial number.
---------- Post added at 06:29 PM ---------- Previous post was at 06:27 PM ----------
bruney.melo said:
need to have the bootloader unlocked? here says that the device was not found.
'' (bootloader) max-download-sizer: not found
target didn't report max-download-size
sending 'partition' (37 KB)...''
Click to expand...
Click to collapse
Not quite sure you need the bootloader unlocked, because you use a fastboot command to unlock it, before it is unlocked.
Droid_Nut said:
Did you do an initial connected with the system booted, developer options>adb debugging, and connect to your PC by typing adb devices, and getting the prompt in your phone? And when you put the phone in fastboot mode, type fastboot devices to make sure your phone is connected, it will return the serial number.
---------- Post added at 06:29 PM ---------- Previous post was at 06:27 PM ----------
Not quite sure you need the bootloader unlocked, because you use a fastboot command to unlock it, before it is unlocked.
Click to expand...
Click to collapse
Yes, I did exactly everything, but this message continues.,
{
C:\Users\brune\Desktop\BECKHAM_OPWS28.70-47-5_XT1929-5_8.1.0_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>adb devices
List of devices attached
C:\Users\brune\Desktop\BECKHAM_OPWS28.70-47-5_XT1929-5_8.1.0_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>adb reboot bootloader
error: no devices/emulators found
C:\Users\brune\Desktop\BECKHAM_OPWS28.70-47-5_XT1929-5_8.1.0_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot devices
0050538683 fastboot
C:\Users\brune\Desktop\BECKHAM_OPWS28.70-47-5_XT1929-5_8.1.0_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
(bootloader) max-download-sizer: not found
target didn't report max-download-size
sending 'partition' (37 KB)...}
bruney.melo said:
Yes, I did exactly everything, but this message continues.,
{
C:\Users\brune\Desktop\BECKHAM_OPWS28.70-47-5_XT1929-5_8.1.0_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>adb devices
List of devices attached
C:\Users\brune\Desktop\BECKHAM_OPWS28.70-47-5_XT1929-5_8.1.0_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>adb reboot bootloader
error: no devices/emulators found
C:\Users\brune\Desktop\BECKHAM_OPWS28.70-47-5_XT1929-5_8.1.0_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot devices
0050538683 fastboot
C:\Users\brune\Desktop\BECKHAM_OPWS28.70-47-5_XT1929-5_8.1.0_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
(bootloader) max-download-sizer: not found
target didn't report max-download-size
sending 'partition' (37 KB)...}
Click to expand...
Click to collapse
Looks like ADB is not reporting any devices, you wont be able to do anything until you get a PC connection. Try another USB cable.
Droid_Nut said:
Looks like ADB is not reporting any devices, you wont be able to do anything until you get a PC connection. Try another USB cable.
Click to expand...
Click to collapse
I managed to make adb recognize the device, but this error happens
''C:\Users\brune\Desktop\Nova pasta>fastboot flash bootloader bootloader.img
(bootloader) max-download-sizeot: not found
target didn't report max-download-size
sending 'bootloader' (9520 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.018s
C:\Users\brune\Desktop\Nova pasta>fastboot flash bluetooth BTFM.bin
(bootloader) slot-suffi: not found
(bootloader) max-download-: not found
target didn't report max-download-size
sending 'bluetooth' (4564 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.008s
C:\Users\brune\Desktop\Nova pasta>fastboot flash dsp dspso.bin
(bootloader) slot-countad-: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) partition-: not found
target didn't report max-download-size
sending 'dsp' (16384 KB)...''
:crying::crying::crying::crying::crying::crying::crying:
bruney.melo said:
I managed to make adb recognize the device, but this error happens
''C:\Users\brune\Desktop\Nova pasta>fastboot flash bootloader bootloader.img
(bootloader) max-download-sizeot: not found
target didn't report max-download-size
sending 'bootloader' (9520 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.018s
C:\Users\brune\Desktop\Nova pasta>fastboot flash bluetooth BTFM.bin
(bootloader) slot-suffi: not found
(bootloader) max-download-: not found
target didn't report max-download-size
sending 'bluetooth' (4564 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.008s
C:\Users\brune\Desktop\Nova pasta>fastboot flash dsp dspso.bin
(bootloader) slot-countad-: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) partition-: not found
target didn't report max-download-size
sending 'dsp' (16384 KB)...''
:crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
I assumed you authorized adb debugging check box on your phone, when you typed abd devices on your PC?
Is Pie still working? Not a lot of help on the Z3 section of this forum, this is getting out of my league without the phone in front of me.
Maybe link your thread to the Z2 Play section? It looks a lot more active.
Droid_Nut said:
I assumed you authorized adb debugging check box on your phone, when you typed abd devices on your PC?
Is Pie still working? Not a lot of help on the Z3 section of this forum, this is getting out of my league without the phone in front of me.
Maybe link your thread to the Z2 Play section? It looks a lot more active.
Click to expand...
Click to collapse
Yes, I authorized on the PC, all permissions have been given, the ADB Raboot Fastboot command works, the problem is running through the rom. Really JannaNsei more than doing
I don't know if Lenovo Smart Assist would allow you to flash a downgrade? It would not work with my phone, because I have an unlocked bootloader.
https://support.lenovo.com/us/en/downloads/ds101291
Droid_Nut said:
Download this to PC, this using the second link https://forum.xda-developers.com/showpost.php?p=79122632&postcount=45
BECKHAM_OPWS28.70_47_8_subsidy_DEFAULT_regulatory_ DEFAULT_CFC.xml
Using these instructions https://forum.xda-developers.com/z3-play/how-to/firmware-oficial-9-0-0-pie-instalacion-t3911995 :good:
I am considering doing this and taking the official Pie OTA, the Pie download here wont allow for updates.
Click to expand...
Click to collapse
Hello, will this downgrade method work on sprint z3 play?
I want to sim unlock it, but can't do on android 9.
Flashing ROM using fastboot MUST be done in Linux platform (Ubuntu is OK)
Hello,
Model: XT1900-1 (originally android one 9.0 - retail)
Rom: ionOS 10.0
I recently installed ionOS without any issues. I had Lineage 16.0 installed before ion.
The last few days ion was getting very slow. I rebooted and got stuck after the google logo came up. Nothing happens after the google logo it just goes to a black screen. I can reboot into the bootloader but am not able to load recovery. I am also not able to fastboot into recovery via flash or temporarily.
Bootloader is unlocked
Commands and errors
Code:
fastboot boot recovery.img
Code:
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
Code:
C:\adb>fastboot flash recovery.img
(bootloader) slot-counttyp: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-su: not found
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
Code:
C:\adb>fastboot erase recovery
(bootloader) slot-co: not found
(bootloader) slot-suffi: not found
(bootloader) partition-typ: not found
erasing 'recovery'...
(bootloader) Invalid partition name recoveryon-typ
FAILED (remote failure)
finished. total time: 0.008s
Any help on restoring recovery would be greatly appreciated. Once I can get to recovery I'll flash it back to stock (9.0)
Thanks!!!
Damien
This has been resolved. The error messages just werent making any sense so after a little more digging a tried a different usb port and commands started to respond as expected.
I gor twrp running via
Code:
fastboot boot recovery.img
and then cleaned everything out. Now let see if can get the wifi and sim to work on this rom.
Thanks!
FIRST READ THIS>>>>Use this guide only if you are 100% sure about the risks involved in flashing your device. I'm not responsible for any damage caused by using this guide on this thread. !!!!!!!! If you are not expert don't read this guide!!!
What you need:
1-windows 10 on a PC
2-Motorola Razr 5g full charged
3-Usb Driver Motorola
4- Adb and Fastboot Tools
5- Enable developer option :Head over to the Settings app of your device via the notification shade or app drawer.
Enable developer options
Scroll down and tap on 'About phone. '
Find an entry labeled 'Build number. ' Keep on tapping until you see a prompt that says 'You are now a developer! '. ...
Then Enable USB debug and unlock bootloader options
Step A Unlock Bootloader (make a backup ! > you lost ALL your data!!!
1- First take a full backup of your phone as unlocking the bootloader on Motorola Razr 5G will wipe all the data.
2- To connect devices you need some drivers, so install ADB & Fastboot drivers and Motorola USB Driver on your PC.
3- Open Settings and go to About Phone. Tap 7-8 times on Build Number, and it will show ‘You are now a developer.’
4- After enabling the developer options, go back to Settings and then go to System > Developer Options. In Developer options, enable OEM Unlocking and also enable USB Debugging.
5- Turn off your device. Press & hold Volume Down + Power button together to boot Motorola Razr 5G into Fastboot Mode.
6- And when the Fastboot screen appears on the phone, release both buttons. Connect your phone to your PC after booting into Fastboot.
7- Now open the Command window or CMD on your computer. Open Command window from Platform Tools location in case of macOS and Linux.
8- Enter the below command in the Command/PowerShell window
fastboot oem get_unlock_data
9- It will display 5-line code. Copy the code and make it in one line, use notepad for convenience. Remember not to copy (bootloader) in case of windows and Info in case of Mac.
10- Go to Motorola unlock page and click next and login with the Motorola account.
11- Copy the one-line code that you just adjusted in Notepad and paste it into the Motorola unlock page.how to unlock bootloader of motorola razr 5g
12- Click on ‘Can my device be unlocked’ and then click ‘Request Unlock Key’ (make sure to select I Agree).
13- Then you will receive a code via mail (Motorola account ID). Copy the code and paste in place of ‘code’ without inverted commas in the below command and press Enter
fastboot oem unlock 'code'
14- Entering the above command will unlock bootloader of Motorola Razr 5G. It will erase all the data on your phone. After unlocking the bootloader, reboot, and set up your device.
Once you unlock the bootloader of Motorola Razr 5G, you can check for it by going to Developer Options and OEM Unlocking. It should be enabled. After unlocking bootloader of Motorola Razr 5G, you can proceed with rooting your phone. Also make sure to go through the requirements.
Step B - Root with Magisk modify file boot.img
You can root your phone using Magisk in different ways such as flashing Magisk Zip or installing a Patched boot image. Since you need a custom recovery to flash Magisk, you need to first install custom recovery. Here in this guide, we will share how to root Motorola Razr 5G with a patched boot image.
1-Copy the Motorola Razr 5G firmware to your computer. And then extract the firmware using 7Zip or WinRAR.
2-Open the extracted folder and copy the boot.img file to your phone storage.
3-Install the Magisk Manager app on your phone.
4-After installing, open the Magisk Manager app and click on the first Install and again click on Install.
5-It will ask for the method, so choose ‘Select and Patch a File’ from the option
6-Now browse and select the boot.img file, and it will start patching the boot image.
7-The output file will be stored in the download folder with the name magisk_patched.img.
8-Copy the patched boot image file to your computer in folder C:\adb. Also, rename the patched file to boot.img.
9-Reboot your Motorola Razr 5G to Fastboot mode and connect it to your computer. Follow the steps given in the unlock bootloader guide above.
10-In the C:\adb folder (or platform-tools folder) press Shift + Right click on an empty area and select ‘Open Command window here’ or ‘Open PowerShell window here.’
11-Enter the below command in the Command/PowerShell window to check the device is connected or not, entering command should return some number id.
fastboot devices
12-Now enter the below command to flash Magisk and root Motorola Razr 5G.
fastboot flash boot boot.img
13-After that, reboot your device to the system.
14-If the Magisk Manager is not installed on your phone, then install the app. Skip if the app is already present.
15-Complete the in-app instructions, and the device will automatically reboot into the system.
Step C - Flash firmware (if you flash oly boot.img bbe sure to download the SAME FIRMWARE YOU HAVE ON YOUR PHONE)
Boot your device into bootloader mode. Phone off > press and hold at the same time :volume down and power on buttons
Connect your Motorola Razr 5g to the PC using the USB Cable.
Download Stock ROM/Firmware and extract it inside the adb and fastboot folder
Inside the ADB folder, open the command window and enter the following command
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash radio radio.img
fastboot flash logo logo.bin
Now toggle to fastbootdfastboot reboot fastboot
fastboot reboot fastboot
Flash the following command
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7 and 8 ,9 etc....
Toggle back to bootloader
fastboot reboot bootloader
fastboot erase carrier
fastboot erase metadata
fastboot erase ddr
(Optional except you want to wipe) fastboot erase userdata
fastboot reboot
Now your device will reboot into bootloader with the firmware you installed.
you can flash only boot.img (modified) file!
You can flash other country firmware, i try with india and italy firmware...
I find very important info from these Links:
How to Root Motorola Razr 5G and Unlock Bootloader
Want to root Motorola Razr 5G with Magisk? Here's how to root Motorola Razr 5G along with guide to unlock bootloader.
www.ytechb.com
Motorola XT2052-1 Firmware Flash File (Stock ROM)
Here we have shared the latest stock ROM for Motorola Moto E 2020 XT2052-1 (ginna). You can download and flash the firmware file on your Motorola XT2052-1 using the flash…
droidfilehost.com
Motorola unlock bootloader link
https://motorola-global-portal.custhelp.com/cc/cas/sso/redirect/standalone%2Fbootloader%2Funlock-your-device-c
Official site to download Magisk
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Firmware:
Motorola Razr 5G XT2071-4 Stock ROM Firmware (Flash File)
Download the official Motorola Razr 5G XT2071-4 Stock Firmware (Flash File) for your Motorola Smartphone. We also provide all other Motorola Stock Firmware.
motostockrom.com
or (better!!) Telegram bot: Moto Updates Tracker >> t.me/motoupdatestracker
Adb and Fastboot Tool:
Download ADB and Fastboot tool 15 seconds ADB Installer v1.5.6
ADB or Android Debug bridge is used to establish a successful connection (bridge) between your device and PC. Once this connection is established, you could carry out plenty of tweaks,…
droidfilehost.com
Usb Motorola Driver
Where can I download the USB drivers for my device?| Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.Where can I download the USB drivers for my device?
support.motorola.com
I hope i've been helpful...
Is there currently any way to revert back to stock from this?
KOAO said:
Is there currently any way to revert back to stock from this?
Click to expand...
Click to collapse
I don't know, I'm not try. If you lock bootloader and load official firmware i think is possible.
Will this work on the T-mobile variant?
icedventimocha said:
Will this work on the T-mobile variant?
Click to expand...
Click to collapse
You have to find your firmware version on telegram here:
https://t.me/motoupdatestracker
i think the way is always the same, pay attention to every step....
didn't work for me...
the patched boot.img created by magisk did not work...
my phone got bricked at step c
C:\Users\Danz\Desktop\Temp\platform-tools\moto>fastboot flash partition gpt.bin
target reported max download size of 805306368 bytes
sending 'partition' (206 KB)...
OKAY [ 0.007s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.302s]
finished. total time: 0.312s
C:\Users\Danz\Desktop\Temp\platform-tools\moto>fastboot flash bootloader bootloader.img
target reported max download size of 805306368 bytes
sending 'bootloader' (12800 KB)...
OKAY [ 0.297s]
writing 'bootloader'...
(bootloader) Validating 'default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'default.xml'
FAILED (remote failure)
finished. total time: 0.408s
C:\Users\Danz\Desktop\Temp\platform-tools\moto>fastboot flash bootloader bootloader.img
target reported max download size of 805306368 bytes
sending 'bootloader' (12800 KB)...
OKAY [ 0.302s]
writing 'bootloader'...
(bootloader) Validating 'default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'default.xml'
FAILED (remote failure)
finished. total time: 0.412s
C:\Users\Danz\Desktop\Temp\platform-tools\moto>fastboot flash bootloader bootloader.img
target reported max download size of 805306368 bytes
sending 'bootloader' (12800 KB)...
OKAY [ 0.297s]
writing 'bootloader'...
(bootloader) Validating 'default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'default.xml'
FAILED (remote failure)
finished. total time: 0.407s
C:\Users\Danz\Desktop\Temp\platform-tools\moto>fastboot flash bluetooth BTFM.bin
target reported max download size of 805306368 bytes
sending 'bluetooth' (188 KB)...
OKAY [ 0.006s]
writing 'bluetooth'...
OKAY [ 0.011s]
finished. total time: 0.020s
C:\Users\Danz\Desktop\Temp\platform-tools\moto>fastboot flash dsp dspso.bin
target reported max download size of 805306368 bytes
sending 'dsp' (65536 KB)...
OKAY [ 1.423s]
writing 'dsp'...
OKAY [ 0.172s]
finished. total time: 1.596s
C:\Users\Danz\Desktop\Temp\platform-tools\moto>fastboot flash radio radio.img
target reported max download size of 805306368 bytes
sending 'radio' (151933 KB)...
OKAY [ 3.335s]
writing 'radio'...
(bootloader) Validating 'radio.default.xml'
(bootloader) Committing 'radio.default.xml'
(bootloader) - flashing 'NON-HLOS.bin' to 'modem'
(bootloader) - flashing 'fsg.mbn' to 'fsg'
(bootloader) - erasing 'modemst1'
(bootloader) - erasing 'modemst2'
OKAY [ 0.494s]
finished. total time: 3.835s
C:\Users\Danz\Desktop\Temp\platform-tools\moto>fastboot flash logo logo.bin
target reported max download size of 805306368 bytes
sending 'logo' (3332 KB)...
OKAY [ 0.075s]
writing 'logo'...
OKAY [ 0.016s]
finished. total time: 0.093s