Related
My unlocked R800i doesn't seem to be able to boot custom kernels! After flashing a kernel it will go to the splash screen before the screen turns black and the phone reboots. I have tried relocking and unlocking again but it doesn't seem to make a difference. The only kernels I can use are DoomLords, with any others such as FXP, Mjolnir and KeICS not booting.Can't figure out whats wrong, any ideas?
Unlocking
Code:
(bootloader) Unlock phone requested
(bootloader) Erasing block 0x00000d00
(bootloader) Erasing block 0x00000e00
(bootloader) Erasing block 0x00000f00
(bootloader) Erasing block 0x00001000
(bootloader) Erasing block 0x00001100
(bootloader) Erasing block 0x00001200
(bootloader) Erasing block 0x00001300
(bootloader) Erasing block 0x00001400
(bootloader) Erasing block 0x00001500
(bootloader) Erasing block 0x00001600
(bootloader) Erasing block 0x00001700
(bootloader) Erasing block 0x00001800
OKAY [ 2.974s]
finished. total time: 2.974s
Flashing a Kernel:
Code:
C:\Android>fastboot flash boot KeICSv2.img
sending 'boot' (6202 KB)...
(bootloader) USB download speed was 30829kB/s
OKAY [ 0.747s]
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 1.230s]
finished. total time: 1.978s
i think you need to get the most recent, the newest version of the kernel
and i suggest you to do a full wipe, also with the dalvik cache
yukarundeng said:
i think you need to get the most recent, the newest version of the kernel
and i suggest you to do a full wipe, also with the dalvik cache
Click to expand...
Click to collapse
I am using the latest version of Mjolnir and FXP, KeICS was just used as an example. I can't get into recovery to perform a wipe.
mcharga3000 said:
I am using the latest version of Mjolnir and FXP, KeICS was just used as an example. I can't get into recovery to perform a wipe.
Click to expand...
Click to collapse
doomlord/keiren = tap back button
cm7/cm9/ICX/MIUI/mjolnir/lupus = tap the vol down button
to enter the recovery mode when the kernel logo shows up
mcharga3000 said:
I am using the latest version of Mjolnir and FXP, KeICS was just used as an example. I can't get into recovery to perform a wipe.
Click to expand...
Click to collapse
Re-read the instructions for the kernel your using you probably have to use a different button to get into recovery, like volume button or something. Doomkernel is back button
Sent from my R800a using XDA App
I'm having a problem with ADB, when i try do search devices with "adb devices" doesn't show nothing, i've tryied to do "adb kill-server" & "adb start-server", reinstall all drivers and still doesn't work.
OEM is already unlocked.
Any solution to this?
i solved doing factory reset, but now i cant flash twrp.
ADB shows
Microsoft Windows [version 10.0.14393]
Minimal ADB and Fastboot>adb devices
List of devices attached
Minimal ADB and Fastboot>fastboot devices
0027249028 fastboot
Minimal ADB and Fastboot>fastboot flash recovery twrp.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' (26636 KB)...
OKAY [ 0.776s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.791s
enable USB Debugging in developer options.
timster01 said:
enable USB Debugging in developer options.
Click to expand...
Click to collapse
i did that but not work, i solved the problem doing factory reset.
Does anyone can help me?
My Pixel XL brick more than a week ago, and I couldn't. I was installing the 8.0.0 official image from the bootloader with fastboot (a "clean install"), apparently there was an error installing the recovery and I didn't realize, so I lock the recovery (with fastboot oem lock and Up Volume key). After that, I restarted the phone and now it doesn't start (it shows only a "Google" splash and it restarts again).
I can't use the recovery mode (to use adb sideload command), try enter to the recovery makes the phone start "bootlooping" too.
I seen another thread explaining my problem, but it has almost a year without activiy (I asked on it to the user if he could solve that this problem but it seems like he doesn't use xda anymore):
https://forum.xda-developers.com/pixel-xl/help/pixel-xl-soft-bricked-unlock-bootloader-t3540772
I live in Uruguay, so I can't RMA.
Summary:
- My phone is bricked.
- I can enter to bootloader, but it's locked.
- I can't enter to recovery mode.
- I can't RMA.
Useful logs:
fastboot getvar all:
Code:
(bootloader) version:0.5
(bootloader) hw-revision:PVT
(bootloader) mid:G-2PW2100
(bootloader) version-main:0.12.999.1
(bootloader) imei:352693081633543
(bootloader) ramdump-mode:false
(bootloader) boot-mode:FASTBOOT
(bootloader) has-slot:radio:yes
(bootloader) has-slot:bootloader:yes
(bootloader) has-slot:reserve5:no
(bootloader) has-slot:devinfo:no
(bootloader) has-slot:fsg:no
(bootloader) has-slot:mfg:no
(bootloader) has-slot:board_info:no
(bootloader) has-slot:reserve4:no
(bootloader) has-slot:metadata:no
(bootloader) has-slot:pg2fs:no
(bootloader) has-slot:pg1fs:no
(bootloader) has-slot:ramdump:no
(bootloader) has-slot:frp:no
(bootloader) has-slot:reserve3:no
(bootloader) has-slot:cdt:no
(bootloader) has-slot:ddr:no
(bootloader) has-slot:modemst2:no
(bootloader) has-slot:modemst1:no
(bootloader) has-slot:fsc:no
(bootloader) has-slot:dip:no
(bootloader) has-slot:dpo:no
(bootloader) has-slot:devinfobak:no
(bootloader) has-slot:sec:no
(bootloader) has-slot:persist:no
(bootloader) has-slot:ssd:no
(bootloader) has-slot:misc:no
(bootloader) has-slot:xbl:yes
(bootloader) has-slot:reserve0:no
(bootloader) has-slot:userdata:no
(bootloader) has-slot:system:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:apdp:yes
(bootloader) has-slot:msadp:yes
(bootloader) has-slot:modem:yes
(bootloader) has-slot:devcfg:yes
(bootloader) has-slot:hosd:yes
(bootloader) has-slot:boot:yes
(bootloader) has-slot:aboot:yes
(bootloader) has-slot:cmnlib64:yes
(bootloader) has-slot:cmnlib32:yes
(bootloader) has-slot:hyp:yes
(bootloader) has-slot:pmic:yes
(bootloader) has-slot:rpm:yes
(bootloader) has-slot:tz:yes
(bootloader) has-slot:keymaster:yes
(bootloader) has-slot:bootlocker:yes
(bootloader) slot-count:2
(bootloader) current-slot:a
(bootloader) slot-retry-count:b:0
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:2
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4240000
(bootloader) variant:US
(bootloader) secure:yes
(bootloader) unlocked:no
(bootloader) version-baseband:8996-012901-1702171013
(bootloader) version-bootloader:8996-012001-1704121145
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x635400000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0x80000000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0x80000000
(bootloader) partition-type:vendor_b:ext4
(bootloader) partition-size:vendor_b: 0x12c00000
(bootloader) partition-type:vendor_a:ext4
(bootloader) partition-size:vendor_a: 0x12c00000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0x2000000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0x2000000
(bootloader) serialno:HT7370201155
(bootloader) kernel:lk
(bootloader) product:marlin
all:
finished. total time: 2.243s
./flash-all.sh (8.0.0-stock-opr3.170623.007):
Code:
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32268 KB)...
OKAY [ 1.076s]
writing 'bootloader_a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.175s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.275s
target reported max download size of 536870912 bytes
sending 'radio_a' (57272 KB)...
OKAY [ 1.952s]
writing 'radio_a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 2.050s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.150s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
W/ziparchive(10452): Zip: unable to allocate 818872552 bytes at offset 0 : No space left on device
failed to extract 'system_other.img': I/O Error
W/ziparchive(10452): Zip: unable to allocate 263934088 bytes at offset 0 : No space left on device
failed to extract 'vendor.img': I/O Error
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
error: file_write: write: No space left on device
--------------------------------------------
Bootloader Version...: 8996-012001-1704121145
Baseband Version.....: 8996-012901-1702171013
Serial Number........: HT7370201155
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
FAILED
Device version-bootloader is '8996-012001-1704121145'.
Update requires '8996-012001-1706221457'.
finished. total time: 0.300s
./flash-all.sh (7.1.2-stock-njh47d):
Code:
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32380 KB)...
OKAY [ 1.088s]
writing 'bootloader_a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.187s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.247s
target reported max download size of 536870912 bytes
sending 'radio_a' (57240 KB)...
OKAY [ 1.924s]
writing 'radio_a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 2.022s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.250s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
W/ziparchive(10714): Zip: unable to allocate 1721085316 bytes at offset 0 : No space left on device
failed to extract 'system_other.img': I/O Error
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1704121145
Baseband Version.....: 8996-012901-1702171013
Serial Number........: HT7370201155
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.050s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boot_a' (26001 KB)...
OKAY [ 0.951s]
writing 'boot_a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.401s
zades9 said:
Does anyone can help me?
My Pixel XL brick more than a week ago, and I couldn't. I was installing the 8.0.0 official image from the bootloader with fastboot (a "clean install"), apparently there was an error installing the recovery and I didn't realize, so I lock the recovery (with fastboot oem lock and Up Volume key). After that, I restarted the phone and now it doesn't start (it shows only a "Google" splash and it restarts again).
I can't use the recovery mode (to use adb sideload command), try enter to the recovery makes the phone start "bootlooping" too.
I seen another thread explaining my problem, but it has almost a year without activiy (I asked on it to the user if he could solve that this problem but it seems like he doesn't use xda anymore):
https://forum.xda-developers.com/pixel-xl/help/pixel-xl-soft-bricked-unlock-bootloader-t3540772
I live in Uruguay, so I can't RMA.
Summary:
- My phone is bricked.
- I can enter to bootloader, but it's locked.
- I can't enter to recovery mode.
- I can't RMA.
Click to expand...
Click to collapse
I assume that you have tried fastboot boot with the correct twrp image?
I understand you locked the bootloader, however, maybe the stock images didn't flash correctly to reset the "allow oem unlocking" in the developer options..
If that's the case, try unlocking the bootloader again with "fastboot flashing unlock".
mikefnz said:
I assume that you have tried fastboot boot with the correct twrp image?
Click to expand...
Click to collapse
I get this log:
Code:
[cristian: PixelXL]$ fastboot boot twrp-3.0.2-0-alpha2-fastboot-marlin.img
downloading 'boot.img'...
OKAY [ 0.901s]
booting...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.001s
Pain-N-Panic said:
I understand you locked the bootloader, however, maybe the stock images didn't flash correctly to reset the "allow oem unlocking" in the developer options..
If that's the case, try unlocking the bootloader again with "fastboot flashing unlock".
Click to expand...
Click to collapse
Code:
[cristian: PixelXL]$ fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.043s
[cristian: PixelXL]$ fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.044s
I have no idea man... hopefully someone a lot more experienced than me comes around with a valid solution.
zades9 said:
Code:
[cristian: PixelXL]$ fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.043s
[cristian: PixelXL]$ fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.044s
Click to expand...
Click to collapse
I'm no expert but have you tried the Skipsoft Toolkit? https://forum.xda-developers.com/pixel-xl/development/tool-skipsoft-android-toolkit-google-t3482767
And checked this guide? https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478/page20
mikefnz said:
I'm no expert but have you tried the Skipsoft Toolkit? https://forum.xda-developers.com/pixel-xl/development/tool-skipsoft-android-toolkit-google-t3482767
And checked this guide? https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478/page20
Click to expand...
Click to collapse
I can't enable Bootloader Unlocking from the developer settings because the device is bricked.
@zades9 I have an idea. Try downloading an OTA image to 8.0 and flashing that from stock recovery if you can access it (twrp might be cool too idk). If it will not let you flash an ota because you're already on 8.... 8.1 is coming out soon lol Is your bootloader messed up somehow? Fastboot flashing unlock_critical unlocks the bootloader but I don't know much about it. Let me rephrase it allows the bootloader to be flashed over.
Yea I'd try:fastboot flashing unlock_critical
Is it possible to switch to the bootloader_b slot and reboot-bootloader... possibly flash the b slot?
comat0se said:
Yea I'd try:fastboot flashing unlock_critical
Is it possible to switch to the bootloader_b slot and reboot-bootloader... possibly flash the b slot?
Click to expand...
Click to collapse
[cristian: ~]$ fastboot flashing unlock_critical
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.044s
tdct12 said:
@zades9 I have an idea. Try downloading an OTA image to 8.0 and flashing that from stock recovery if you can access it (twrp might be cool too idk). If it will not let you flash an ota because you're already on 8.... 8.1 is coming out soon lol Is your bootloader messed up somehow? Fastboot flashing unlock_critical unlocks the bootloader but I don't know much about it. Let me rephrase it allows the bootloader to be flashed over.
Click to expand...
Click to collapse
For what I know, you can't flash anything if your bootloader is locked.
Code:
[cristian: ~]$ fastboot flashing unlock_critical
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.044s
I know about 6 months ago in the Nexus 6p forum, someone created a zip that could be flashed in recovery to toggle bootloader unlock in developer settings. It might be worth looking for to see if there's some sort of adb shell script that you could possibly use to toggle that switch. So you didn't boot after flashing factory image before locking? Also be sure to be using the most up to date adb and fastboot tools as that can cause issue too. IDK, I wish you luck!
Bryanx86 said:
I know about 6 months ago in the Nexus 6p forum, someone created a zip that could be flashed in recovery to toggle bootloader unlock in developer settings. It might be worth looking for to see if there's some sort of adb shell script that you could possibly use to toggle that switch. So you didn't boot after flashing factory image before locking? Also be sure to be using the most up to date adb and fastboot tools as that can cause issue too. IDK, I wish you luck!
Click to expand...
Click to collapse
If I could flash something in recovery mode I could flash the stock rom with "adb sideload file.zip", so I would not need unlock bootoader.
And yeah, I didn't boot after locking oem again :/
zades9 said:
For what I know, you can't flash anything if your bootloader is locked.
Code:
[cristian: ~]$ fastboot flashing unlock_critical
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.044s
Click to expand...
Click to collapse
Actually that's not true. You can flash factory ota updates on a locked bootlader from stock recovery, idk about twrp though.
zades9 said:
If I could flash something in recovery mode I could flash the stock rom with "adb sideload file.zip", so I would not need unlock bootoader.
And yeah, I didn't boot after locking oem again :/
Click to expand...
Click to collapse
I wasn't referring to flashing that zip file, but looking inside to see if it's an adb shell script, you have a booting phone with a working bootloader, the recovery is compromised. There has to be a way to get your phone fixed. Only when it's totally dead do you give up hope
Well, while we are grasping at straws, make sure your fastboot is the very latest version. The version I use is marked as
~$ fastboot --version
fastboot version -4022467
I would also give the November image a try.
Crap I bricked mine too! Was on rooted Stock with twrp. Did factory reset (to unroot), then relock bootloader (all done with Skipsoft Toolkit). Thought I'd be in the clear, but now it's just bootlooping a half second Google logo and then black. I can get into the bootloader but nothing else works, not recovery, nothing. Can't flash anything since bootloader is locked now. Tried adb commands like fastboot continue but nothing works... Any updates or ideas on this!?? Device is bricked! I bought mine new on Craigslist so may have some trouble with RMA.... Yikes!
Please let this be a lesson to people to stop locking their bootloader's, or know what the heck they are doing before they do. I'm tired of reading about this across all forums. Whoever is explaining the steps to unlock the bootloader, need to give explicit knowledge on what to do and not do. I honestly wish I could be of more help, but it's a pain to get sorted on devices with regular partitions, so on this device I have no clue. It would be great if you could somehow force it to boot using the alternate slot
To OP, it looks like you're using slot A. Can you try switching to slot B and thing to boot?
fastboot --set-active=_b
dictionary said:
Please let this be a lesson to people to stick locking their bootloader's, or know what the heck they are doing. I'm tired of reading about this across all forums. Whoever is explaining the steps to unlock the bootloader, need to give explicit knowledge on what to do and not do. I honestly wish I could be of more help, but it's a pain to get sorted on devices with regular partitions, so on this device I have no clue. It would be great if you could somehow force it to boot using the alternate slot
To OP, it looks like you're using slot A. Can you try switching to slot B and thing to boot?
fastboot --set-active=_b
Click to expand...
Click to collapse
Code:
C:\Users\cristian>fastboot --set-active=_b
Setting current slot to 'b'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.076s
C:\Users\cristian>fastboot --set-active=b
Setting current slot to 'b'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.292s
I posted my problem on the Pixel User Community, but that thread is dead: https://groups.google.com/a/googlep...forums.com?utm_medium=email&utm_source=footer
With the help of @Nirbhay2 I managed to block my bootloader, however what I wanted to share here is that to block the bootloader of the Brazilian variant it is necessary the last ROM with january security patch POTTER_NPNS25.137-92-4. Here you will find the guide to block your Brazilian device.
Have minimal ADB
Have Motorola drivers installed on your PC
Have the january patch ROM stock: https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Extract the ROM to any folder and paste the minimal ADB along with the extracted ROM.
Open a command prompt in the folder and with the device in fastboot mode make a flash of the entire ROM stock on your device, to facilitate copying all the commands at once and paste at the command prompt and it will install automatic to your ROM , then do the same with the commands to re-block the bootloader and at the end of this process your device will be started with bootloader locked.
Commands to re-lock bootloader, do this after the full ROM flash
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 boot boot.img
fastboot oem lock
Command link for flash ROM stock
https://pastebin.com/ZWTaWuyr
We thank @Nirbhay2 for this great guide.
I have a problem relocking bootloader:
...
[email protected] at 12:34:24 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.870s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.465s]
finished. total time: 1.335s
...
[email protected] at 12:36:36 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.002s]
finished. total time: 0.002s
So, bootloader remains unlocked.
Moreover:
[email protected] at 12:36:38 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot flash bootloader bootloader.img(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.271s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.551s
How can I flash original bootloader, boot and lock bootloader?
pss34 said:
I have a problem relocking bootloader:
...
[email protected] at 12:34:24 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.870s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.465s]
finished. total time: 1.335s
...
[email protected] at 12:36:36 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot oem lock
...
(bootloader) Still require signed boot.img
OKAY [ 0.002s]
finished. total time: 0.002s
So, bootloader remains unlocked.
Moreover:
[email protected] at 12:36:38 ~/tmp/potter/POTTER_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot flash bootloader bootloader.img(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.271s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image tz failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image devcfg failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.551s
How can I flash original bootloader, boot and lock bootloader?
Click to expand...
Click to collapse
friend, you need to use this ROM that I made available on the link, if you have a moto G5 plus brazilian you can get the lock, but use this link ROM.
Enviado de meu XT1683 usando Tapatalk
I tried the same thing.
I had TWRP and SuperSu on my phone a few days back. But weirdly, I lost network connectivity and after a botched attempt at installing V4A, the audio died as well. Even the camera and the flash had stopped working. More weirdly, the Root Checker app I had now showed me that root access was not properly installed.
SInce my phone was on the November patch (25-137-92), I found the stock ROM of it online and flashed it with the Moto G5 Plus ToolKit.
Now all the issues I've had are fixed. Everything works perfectly. TWRP has been removed along with SuperSu.
But the bootloader still shows me that software status is modified. The warning on boot-up which tells that the device has been unlocked is still there.
I don't know if it's related but I've got WiFi speed issues now, apps won't download quickly or is it my damn internet?
The bootloader IS locked, though. That I can say confidently because the bootloader unlock option in developer options is now not selected.
Moto G(5) Plus XT1686 4/32 GB Indian Version
Good evening everyone, I introduce myself my name is Eduardo de Mexíco, I want to contribute to help people who have problems with the Moto Z2 Force.
I have the Model XT1789-5, first unlock the bootloader with Motorola and upgrade to Android Pie.
Now I don't have IME, baseband and WIfi.
I have read a lot in this forum, but I cannot find the correct repair.
That's why I put this thread in order to give a repair to my cell phone.
Attach the "flash" with minimal ADB and fastbool tool.
Is the emmc damaged?
The blanck flash appears "waiting for devices" I have installed Motorola and Qualcomm drivers.
I can't change firmware.
Can you help me, please?
Microsoft Windows [Versión 10.0.17763.678]
(c) 2018 Microsoft Corporation. Todos los derechos reservados.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock begin
...
(bootloader) Already locked
OKAY [ 0.011s]
finished. total time: 0.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ 0.011s]
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.233s]
finished. total time: 0.248s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.306s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'xbl.elf' to 'xbl'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'abl.elf' to 'abl'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'pmic.elf' to 'pmic'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'storsec.mbn' to 'storsec'
(bootloader) - flashing 'prov64.mbn' to 'prov'
OKAY [ 0.209s]
finished. total time: 0.518s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem_a' (97407 KB)...
OKAY [ 2.885s]
writing 'modem_a'...
OKAY [ 1.040s]
finished. total time: 3.929s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg_a' (5600 KB)...
OKAY [ 0.173s]
writing 'fsg_a'...
OKAY [ 0.067s]
finished. total time: 0.247s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.006s]
finished. total time: 0.008s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash bluetooth BTFM.bin
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4496 KB)...
OKAY [ 0.140s]
writing 'bluetooth_a'...
OKAY [ 0.055s]
finished. total time: 0.199s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dsp adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp_a' (16384 KB)...
OKAY [ 0.487s]
writing 'dsp_a'...
OKAY [ 0.154s]
finished. total time: 0.646s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo_a' (3524 KB)...
OKAY [ 0.111s]
writing 'logo_a'...
OKAY [ 0.042s]
finished. total time: 0.157s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (23345 KB)...
OKAY [ 0.693s]
writing 'boot_a'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.878s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system_a' (516200 KB)...
OKAY [ 15.095s]
writing 'system_a'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.151s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system_a' (522116 KB)...
OKAY [ 15.404s]
writing 'system_a'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.449s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system_a' (519014 KB)...
OKAY [ 15.299s]
writing 'system_a'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.342s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system_a' (516292 KB)...
OKAY [ 15.112s]
writing 'system_a'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.163s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system_a' (523200 KB)...
OKAY [ 15.335s]
writing 'system_a'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.386s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system_a' (413387 KB)...
OKAY [ 12.137s]
writing 'system_a'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 12.182s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system_b system_b.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system_b' (515182 KB)...
OKAY [ 15.059s]
writing 'system_b'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 15.106s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system_b system_b.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system_b' (319601 KB)...
OKAY [ 9.336s]
writing 'system_b'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 9.377s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem_a' (163069 KB)...
OKAY [ 4.820s]
writing 'oem_a'...
(bootloader) *****************************************************
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 4.862s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase carrier
erasing 'carrier'...
OKAY [ 0.007s]
finished. total time: 0.009s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.765s]
finished. total time: 0.771s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase ddr
erasing 'ddr'...
OKAY [ 0.004s]
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) Already locked
OKAY [ 0.005s]
finished. total time: 0.007s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
I can't install the TWRP
I currently have the OPXS version 27.109-34-21 With this firmware it worked fine, but not now.
Beforehand
Thank you!!
You flashed pie, you can't go back to oreo, so you have to flash pie again. Since you have no baseband or imei, you must have flashed the wrong variant. Who is your provider, what was your software channel originally? What is the package name of the OREO firmware that worked for you in the past. This information will help determine what you need to flash in order to repair. Why is everyone obsessed with locking the bootloader? When you lock your bootloader, you dramatically reduce the options and tools available to fix your phone when things go wrong.
XDA Developers The BEST!!!
41rw4lk said:
You flashed pie, you can't go back to oreo, so you have to flash pie again. Since you have no baseband or imei, you must have flashed the wrong variant. Who is your provider, what was your software channel originally? What is the package name of the OREO firmware that worked for you in the past. This information will help determine what you need to flash in order to repair. Why is everyone obsessed with locking the bootloader? When you lock your bootloader, you dramatically reduce the options and tools available to fix your phone when things go wrong.
Click to expand...
Click to collapse
41rw4lk
* 41rw4lk
* 41rw4lk
You're the best!!!!!
Thank you!!!! IT WORKED!!!
Thanks for your support!!!!!!
I have IME, Baseband, all normal.
I got an update to PIE is the collection no. PPX29-159-23
I DIDN'T download it.
If I can download it?
regards
If everything is working normally, and you received an ota notification to update, then you should be able to update just fine. If it's some random firmware you came across, I wouldn't.
Pie
Hi good day.
I can't update Android Pie.
Tells me
Incorrect software update
My channel is OPMX.
The phone is company free
What I did was install the NASH RETAIL OPXS27 109 34 21 Firmware, this is what I had.
Then by fastboot install the NASH RETAIL PPX29 159 23 update.
But it is not updated, what can I do.
Recover the IMEI baseband and the phone works well.
lalo74 said:
Hi good day.
I can't update Android Pie.
Tells me
Incorrect software update
My channel is OPMX.
The phone is company free
What I did was install the NASH RETAIL OPXS27 109 34 21 Firmware, this is what I had.
Then by fastboot install the NASH RETAIL PPX29 159 23 update.
But it is not updated, what can I do.
Recover the IMEI baseband and the phone works well.
Click to expand...
Click to collapse
So just to confirm, everything is working on Retail pie right now yes?
Originally, you were on OpenMX firmware, and your software channel was/and is still OPMX yes?
Can you take a screenshot of the update being offered? OpenMX doesn't have pie yet, so if that is the update being offered then it will fail because you're on Retail firmware. So If you want to go back to OpenMX then we need to do a few things and it has to be a pie update being offered. Otherwise, you can update using any new Retail releases. Not Retin, Rebr, etc. Just plain Retail and you have the latest right now.
Pie
Hello
Thanks for your prompt response
It is currently in the openmix channel.
Before I was on the openmix channel the same.
The firmware was RETAIL.
So it was before the bootloader and flash unlock.
Now he is working fine without problems with
Openmix
NASH RETAIL Opxs27 109 34 21
I attach images
Can you help me please upgrade to Pie.
Photo
Good afternoon 41rw4lk
Look how is my phone
The firmware you download is this
NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml[IMG
https://ibb.co/7XM0t5Z
https://ibb.co/PC5dVs6
Good afternoon 41rw4lk
Look how is my phone
The firmware you download is this
NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
nash/official/RETAIL/NASH_RETAIL_9.0_PPX29.159-23_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
but it was not installed
What is the correct procedure to update again and what are the commands for the firmware through minimal ADB Fastboot tool
https://ibb.co/v1Jx5Mq
https://ibb.co/q7P5spt
https://ibb.co/34ZFnWZ
https://ibb.co/KmcGKY0
https://ibb.co/vjx9rwR
firmware
Do I install this version?
NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Hold on, we need to check a couple of things because I'm confused.
In your OP you mentioned pie upgrade, did you ever upgrade to pie at all? The reason I ask is because in your photo you're running oreo, which would leave you without a baseband if you upgraded to pie modems.
Long story short, if everything is working (mobile data, wifi, bluetooth) etc. Then you should enable oem unlocking and adb debugging and unlock your bootloader again if you haven't already. An unlocked bootloader won't stop otas, it just gives you more options to flash and fix your phone, plus if you want twrp and/or root you'll need to be unlocked.
This is the firmware you flashed to get oreo running on your phone currently right? NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Option A - If you flashed that Retail firmware and all is well. I would flash this firmware to upgrade to pie. You won't be able to take otas since your channel is OPMX, but you will have pie without any bloat.
Option B - As of now, there is no OpenMX pie firmware on lolinet, but it looks like that's the update being offered since you have OPMX as your software channel and from the photo you posted. So if you want proper OpenMX and the ability to take otas, you'll need to flash back to an OpenMX firmware then take your ota.
I would unlock your bootloader before anything, that way if anything goes wrong you have options. Don't flash any pie firmware until you know what you need. If you are unsure, ask questions. Pie isn't the friendliest firmware to flash and will cause problems if you flash the wrong variant.
Command
Good night 41rw4lk
The problem I think are the commands
First
I had this firmware NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml OK installed.
What I did was unlock the bootloader, with the steps of a YouTube video https://www.youtube.com/watch?v=cXxr-Y1ozSY
Then I updated Pie with this firmware Moto/nash/official/RETAIL/NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
It did not work. Back to the firmware of OREO OPXS27 109 34 21, this is where I no longer had the bace band NO IME no Wifi etc.
I was researching for a week ... but nothing worked. The OEM key did not respond, now it responds. I had the pleasure and miracle of meeting you and you tell me:
Go back to the firmware you had.
I do it and then upgrade to PIE PPX29 159 23 and it doesn't work.
Then I turn on the cell phone with OREO OPXS27 109 34 21 and IF the IMEI works the baseband and the Wifi.
Through OTA I get the update message, which is not installed.
Errors The commands I use to flash the firmware.
Now I am watching a YouTube video where they explain how to use the correct commands for each Firmware. What do you think?
The bad thing is that it is in Spanish
https://www.youtube.com/watch?v=a5PwF-qlAVc
What are the correct commands to update the firmware?
I will not flash until I agree with you.
Regards!!
I feel like we're going around in circles lol.
Does your phone work correctly right now? Does it have mobile signal and data, wifi, bluetooth etc?
If it does, what is the full name of the firmware you used to put it in working order?
41rw4lk said:
I feel like we're going around in circles lol.
Does your phone work correctly right now? Does it have mobile signal and data, wifi, bluetooth etc?
If it does, what is the full name of the firmware you used to put it in working order?
Click to expand...
Click to collapse
Hi good day
That's how the phone is working well; It has Wifi signal, IME, base band works 100%.
The firmware I am with now is:
NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
To flash, subject to your opinion I have this procedure:
Phone
Activate Android programmer
Activate OEM
Enable USB debugging
Activate flash mode Moto Z2 (volume - and power button)
Computer:
ADB minimal tool v1.43
In the adb folder install the fimware and extract rar files.
NASH_RETAIL_9.0_PPX29.159-23_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
In the cmd window write
flashboot deivices
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 bluetooth flash BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.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_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot reboot
As time?
How about?
Regards!!
This is your current firmware right? NASH_RETAIL_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
But when you flash NASH_RETAIL_9.0_PPX29.159-23_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip you lose baseband and imei?
If your bootloader isn't unlocked, I would unlock it so that you have some wiggle room if something goes wrong. With a locked bootloader you can only flash official signed, same version or higher, and that's not guaranteed.
As far as your flashing commands, it is best to use the preparation.bat from this thread to generate your own flashall for the firmware you have. Since we have different variants if you're not careful a flashall that you pickup around here might not flash everything you need to flash. So generate your own to be certain.
hello friends, i have a problem, i have a z2 force, with android 8.0.0, retbr software channel, security patch from january 1, 2018, installed version number is opxs27.109-34-4.
In fastboot mode I have baseband not found, I have BL: MBM-3.0-nash_retail-641a15b-180105, in product and variant I have: Nash radio2 64GB PVT and lastly I have Flashing_locked, can anyone help me with which firmware I can try to recover the cell phone ?