Develop Bugs

Endless bootloop. Can't get into recovery even with fastboot commands

Been stuck with this one for days. Endless searches gets me as far as loading the bootloader (button longpress method) and flashing the usual images with fastboot. I used both the preview and post preview developer images. After successfully flashing (indivisually and clicking flash-all), the phone reboots over and over- never into the system or recovery. Any insight is extremely appreciated. Warranty is recently expired too so that's not an option unfortunately.

kt006 said:
Been stuck with this one for days. Endless searches gets me as far as loading the bootloader (button longpress method) and flashing the usual images with fastboot. I used both the preview and post preview developer images. After successfully flashing (indivisually and clicking flash-all), the phone reboots over and over- never into the system or recovery. Any insight is extremely appreciated. Warranty is recently expired too so that's not an option unfortunately.
Click to expand...
Click to collapse
Wait, so you can get into the fastboot menu, but you can't get into the recovery menu? What happens when you select the recovery menu from the fastboot menu?
As for the problem, the only thing I can think of that might be causing this is if you changed your data partition to f2fs for use with the Negalite custom rom. You'll need to change it back to ext4 either by using TWRP, formatting with the stock recovery menu or using the command fastboot erase userdata.

When trying to enter recovery mode, either with Fastboot command or button press, the phone just restarts and bootloops. I'll try your method later tonight.

TheSt33v said:
Wait, so you can get into the fastboot menu, but you can't get into the recovery menu? What happens when you select the recovery menu from the fastboot menu?
As for the problem, the only thing I can think of that might be causing this is if you changed your data partition to f2fs for use with the Negalite custom rom. You'll need to change it back to ext4 either by using TWRP, formatting with the stock recovery menu or using the command fastboot erase userdata.
Click to expand...
Click to collapse
Tried the fastboot erase userdata and followed with flash-all.bat. What's frustrating is that all the fastboot commands finish with no reported errors. Until it tries to boot into recovery and starts bootlooping again. It's like the watch can't access the recovery. Tried flashing twrp and fastboot boot twrp.img- still bootlooped.

kt006 said:
Tried the fastboot erase userdata and followed with flash-all.bat. What's frustrating is that all the fastboot commands finish with no reported errors. Until it tries to boot into recovery and starts bootlooping again. It's like the watch can't access the recovery. Tried flashing twrp and fastboot boot twrp.img- still bootlooped.
Click to expand...
Click to collapse
Very strange. Did you make any sort of modifications before this started happening? Custom rom, root, etc?

TheSt33v said:
Very strange. Did you make any sort of modifications before this started happening? Custom rom, root, etc?
Click to expand...
Click to collapse
Only the bootloader was unlocked and the developer preview was flashed.
Edit* This is what I get when using getvar all. Anyone notice anything unusual that might be the cause?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version:0.5
(bootloader) boardid:7N3BDH15BJ065725
(bootloader) macbt:2400BA712168
(bootloader) macwlan:2400BA712167
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4134mV
(bootloader) variant:
(bootloader) off-mode-charge:0
(bootloader) unlocked:yes
(bootloader) secure:yes
(bootloader) version-bootloader:STURGEONV3.8
(bootloader) version-baseband:N/A
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x3d00000
(bootloader) partition-type:boot:emmc
(bootloader) partition-size:boot: 0x1400000
(bootloader) partition-type:recovery:emmc
(bootloader) partition-size:recovery: 0x1400000
(bootloader) partition-type : oem:ext4
(bootloader) partition-size: oem: 0x9678000
(bootloader) partition-type : cache:ext4
(bootloader) partition-size: cache: 0x20000000
(bootloader) partition-type : userdata:ext4
(bootloader) partition-size:userdata: 0x94ffbe00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x20000000
(bootloader) serialno:MQB*************
(bootloader) kernel:lk
(bootloader) product:sturgeon
all:
finished. total time: 0.078s

kt006 said:
Only the bootloader was unlocked and the developer preview was flashed.
Edit* This is what I get when using getvar all. Anyone notice anything unusual that might be the cause?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version:0.5
(bootloader) boardid:7N3BDH15BJ065725
(bootloader) macbt:2400BA712168
(bootloader) macwlan:2400BA712167
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4134mV
(bootloader) variant:
(bootloader) off-mode-charge:0
(bootloader) unlocked:yes
(bootloader) secure:yes
(bootloader) version-bootloader:STURGEONV3.8
(bootloader) version-baseband:N/A
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x3d00000
(bootloader) partition-type:boot:emmc
(bootloader) partition-size:boot: 0x1400000
(bootloader) partition-type:recovery:emmc
(bootloader) partition-size:recovery: 0x1400000
(bootloader) partition-type : oem:ext4
(bootloader) partition-size: oem: 0x9678000
(bootloader) partition-type : cache:ext4
(bootloader) partition-size: cache: 0x20000000
(bootloader) partition-type : userdata:ext4
(bootloader) partition-size:userdata: 0x94ffbe00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x20000000
(bootloader) serialno:MQB*************
(bootloader) kernel:lk
(bootloader) product:sturgeon
all:
finished. total time: 0.078s
Click to expand...
Click to collapse
My readout looks exactly the same except in fields where one would expect it to be different (serial number, mac addresses). The only exception is that I'm on bootloader version 4.2. I'm currently running the most recent official firmware version (the post-preview version is an older version than the most recent. I took several OTAs after I flashed it when I decided I didn't like the wear 2.0 preview), but I don't see why that would matter or cause the problem you're having since your bootloader is unlocked and should therefore not be enforcing anything. When you flash the wear 2.0 preview, does your bootloader version change?

Yes, when flashing the preview it changes to 4.1. I'm looking into kernels. Hopefully it'll get me somewhere

kt006 said:
Yes, when flashing the preview it changes to 4.1. I'm looking into kernels. Hopefully it'll get me somewhere
Click to expand...
Click to collapse
If the kernel was the problem, it would dump you into the fastboot menu instead of bootlooping. Or if it did bootloop, it would be at the bootanimation and not at the initial Huawei screen. The boot logo (not animation) is stored somewhere in the bootloader for many android devices (with some exceptions, but I've never heard of it being stored on /system or anything like that). Also, you flash the kernel at the same time as everything else when you double click on flash-all, so whatever kernel is there should match whatever you flashed. The fact that it isn't loading anything except fastboot and the boot logo makes me think that your bootloader is pretty pissed off. My theory is either it didn't get the memo when you unlocked it and it's still trying to enforce whatever version was on the phone when you did that, or it's totally borked and has lost the ability to understand that all the partitions have officially signed images on them.

TheSt33v said:
If the kernel was the problem, it would dump you into the fastboot menu instead of bootlooping. Or if it did bootloop, it would be at the bootanimation and not at the initial Huawei screen. The boot logo (not animation) is stored somewhere in the bootloader for many android devices (with some exceptions, but I've never heard of it being stored on /system or anything like that). Also, you flash the kernel at the same time as everything else when you double click on flash-all, so whatever kernel is there should match whatever you flashed. The fact that it isn't loading anything except fastboot and the boot logo makes me think that your bootloader is pretty pissed off. My theory is either it didn't get the memo when you unlocked it and it's still trying to enforce whatever version was on the phone when you did that, or it's totally borked and has lost the ability to understand that all the partitions have officially signed images on them.
Click to expand...
Click to collapse
The strangest thing happened. I disconnected the internal battery overnight. When I reconnected it the watch booted into the system perfectly fine. Then after restarting the watch because of a pairing error, I'm back to square one again.

Help! I cannot unlock the bootloader on my tmo z2 force

I recently replaced my previous z2 after it was damaged. I got my replacement and as always I attempted to unlock the bootloader. Every time I run fastboot oem get_unlock_data regardless if it be on Linux or windows, fastboot or mfastboot it fails. It says <bootloader> Failed to get unlock data. I have tried reinstalling drivers, installing alternate drivers, and reflashing the phone to the latest firmware. I saw someone with a similar thread for the z2 but their solution did not work. I have been using Motorola phones for a long time and had unlocked the bootloader on my previous z2 with no problems. The only thing I didn't do yet is trying to format the userdata partition. I highly doubt that will help anyway. Any help will be greatly appreciated.
Thanks,
vibraniumdroid

vibraniumdroid said:
I recently replaced my previous z2 after it was damaged. I got my replacement and as always I attempted to unlock the bootloader. Every time I run fastboot oem get_unlock_data regardless if it be on Linux or windows, fastboot or mfastboot it fails. It says <bootloader> Failed to get unlock data. I have tried reinstalling drivers, installing alternate drivers, and reflashing the phone to the latest firmware. I saw someone with a similar thread for the z2 but their solution did not work. I have been using Motorola phones for a long time and had unlocked the bootloader on my previous z2 with no problems. The only thing I didn't do yet is trying to format the userdata partition. I highly doubt that will help anyway. Any help will be greatly appreciated.
Thanks,
vibraniumdroid
Click to expand...
Click to collapse
go to bootloader mode and execute 'fastboot getvar all' w/o quotes, post the results but not you imei

41rw4lk said:
go to bootloader mode and execute 'fastboot getvar all' w/o quotes, post the results but not you imei
Click to expand...
Click to collapse
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-641a15b-180420
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA_UMTS
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224CQPCT
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 5786D2FB
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: (removed for privacy)
(bootloader) meid:
(bootloader) date: 08-05-2017
(bootloader) sku: XT1789-04
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4385
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_tmo_c/nash:8.0.0/OCX
(bootloader) ro.build.fingerprint[1]: S27.109-51-7/9:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.241.9.nash_tmo_c.
(bootloader) ro.build.version.full[1]: tmo.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998TMO_20207.117.02.41.01R NUS
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g2c64ab8 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Apr 20 09:21:37 CDT 2018
(bootloader) git:abl: MBM-3.0-nash_tmo-641a15b-180420
(bootloader) git:xbl: MBM-3.0-nash_tmo-9869834-180420
(bootloader) gitmic: MBM-3.0-nash_tmo-9869834-180420
(bootloader) git:rpm: MBM-3.0-nash_tmo-b13e14f-180420
(bootloader) git:tz: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:hyp: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:devcfg: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:cmnlib: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:cmnlib64: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:keymaster: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:storsec: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) gitrov: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: tmo
(bootloader) current-slot: _b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
finished. total time: 0.242s

wtf xda turned some of it into emojis

Everything looks legit, weird. Make sure you have oem unlocking enabled in developer options, grab the utilities zip from the return to stock thread (since it has known good adb/fastboot), unzip, shift+right click to open a command window from inside the folder. Reboot to bootloader mode, verify connection 'fastboot devices", then try to get the unlock data again.

41rw4lk said:
Everything looks legit, weird. Make sure you have oem unlocking enabled in developer options, grab the utilities zip from the return to stock thread (since it has known good adb/fastboot), unzip, shift+right click to open a command window from inside the folder. Reboot to bootloader mode, verify connection 'fastboot devices", then try to get the unlock data again.
Click to expand...
Click to collapse
I have the oem unlock enabled in Dev options

41rw4lk said:
Everything looks legit, weird. Make sure you have oem unlocking enabled in developer options, grab the utilities zip from the return to stock thread (since it has known good adb/fastboot), unzip, shift+right click to open a command window from inside the folder. Reboot to bootloader mode, verify connection 'fastboot devices", then try to get the unlock data again.
Click to expand...
Click to collapse
Also can u link the thread u were talking about.

vibraniumdroid said:
I have the oem unlock enabled in Dev options
Click to expand...
Click to collapse
Make sure your fastboot file is up to date (or use the one in the utilities zip in the return to stock thread), and try using a direct 2.0 usb port off the mobo. Might seem superficial, but it does cause problems for some.
*Linked to the other thread.

41rw4lk said:
Make sure your fastboot file is up to date (or use the one in the utilities zip in the return to stock thread), and try using a direct 2.0 usb port off the mobo. Might seem superficial, but it does cause problems for some.
Click to expand...
Click to collapse
thnx a lot I really appreciate the help

41rw4lk said:
Make sure your fastboot file is up to date (or use the one in the utilities zip in the return to stock thread), and try using a direct 2.0 usb port off the mobo. Might seem superficial, but it does cause problems for some.
*Linked to the other thread.
Click to expand...
Click to collapse
Will let u know if I make any progress

41rw4lk said:
Make sure your fastboot file is up to date (or use the one in the utilities zip in the return to stock thread), and try using a direct 2.0 usb port off the mobo. Might seem superficial, but it does cause problems for some.
*Linked to the other thread.
Click to expand...
Click to collapse
Did not work

vibraniumdroid said:
Did not work
Click to expand...
Click to collapse
What does it say under the oem unlock switch in developer options? You also mentioned that you had reflashed firmware previously but with a locked bootloader you shouldn't have been able to. Are you able to boot and install twrp? If your bootloader is truly locked, you shouldn't be able to.

41rw4lk said:
What does it say under the oem unlock switch in developer options? You also mentioned that you had reflashed firmware previously but with a locked bootloader you shouldn't have been able to. Are you able to boot and install twrp? If your bootloader is truly locked, you shouldn't be able to.
Click to expand...
Click to collapse
You are able to reflash the latest stock firmware USING FASTBOOT on a locked bootloader IF it is signed by Motorola and this is a well known fact.

41rw4lk said:
What does it say under the oem unlock switch in developer options? You also mentioned that you had reflashed firmware previously but with a locked bootloader you shouldn't have been able to. Are you able to boot and install twrp? If your bootloader is truly locked, you shouldn't be able to.
Click to expand...
Click to collapse
I will try to flash twrp also I have the oem unlock switch checked in Dev options

vibraniumdroid said:
I will try to flash twrp also I have the oem unlock switch checked in Dev options
Click to expand...
Click to collapse
Remember when installing TWRP for the first time you must first 'BOOT" TWRP and then flash the TWRP Installer zip. There are a few other steps to follow after installation so please read the guide if you are unfamiliar with the process. Good luck and happy flashing!
Sent from my Moto Z2 Force using XDA Labs

vibraniumdroid said:
You are able to reflash the latest stock firmware USING FASTBOOT on a locked bootloader IF it is signed by Motorola and this is a well known fact.
Click to expand...
Click to collapse
Not always. There have been instances where the phone has relocked itself and won't flash anything, even official signed. Usually the oem unlock switch is greyed out as well with a message near it, that's why I was curious about the oem unlock switch. Usually there is a status message near the switch itself. In this scenario the phone seems locked but is more in some hybrid lock that doesn't allow much of anything.

fast69mopar said:
Remember when installing TWRP for the first time you must first 'BOOT" TWRP and then flash the TWRP Installer zip. There are a few other steps to follow after installation so please read the guide if you are unfamiliar with the process. Good luck and happy flashing!
Click to expand...
Click to collapse
I know. As I mentioned earlier this is my second z2

41rw4lk said:
Not always. There have been instances where the phone has relocked itself and won't flash anything, even official signed. Usually the oem unlock switch is greyed out as well with a message near it, that's why I was curious about the oem unlock switch. Usually there is a status message near the switch itself. In this scenario the phone seems locked but is more in some hybrid lock that doesn't allow much of anything.
Click to expand...
Click to collapse
Also the switch isn't grayed out. do u think a factory data reset would help? Cuz I don't want to do it if I don't need to.

vibraniumdroid said:
Also the switch isn't grayed out. do u think a factory data reset would help? Cuz I don't want to do it if I don't need to.
Click to expand...
Click to collapse
At this point you don't have much of an option. Everything seems in order, you're able to flash, fastboot commands work, except oem unlock. I would.

41rw4lk said:
At this point you don't have much of an option. Everything seems in order, you're able to flash, fastboot commands work, except oem unlock. I would.
Click to expand...
Click to collapse
Okay I will try tomorrow

Boot to BLANK screen with "fastboot boot twrp-3.2.3-0-nitrogen.img" command !!

Boot to BLANK screen with "fastboot boot twrp-3.2.3-0-nitrogen.img" command !!
I'm trying to flash TWRP through ADB in fastboot mode!
And I'm up to "fastboot boot twrp-3.2.3-0-nitrogen.img", but that booted into a BLANK screen...
I'm stuck again :crying:
Code:
Z:\>fastboot boot twrp-3.2.3-0-nitrogen.img
downloading 'boot.img'...
OKAY [ 8.293s]
booting...
OKAY [ 0.076s]
finished. total time: 8.371s
*** the recovery twrp-3.2.3-0-nitrogen.img has been checked with md5 both from official site, aOK!!
Any help is appreciated!

Hi!
1. What do you want to accomplish by executing that? Because you can just press and hold power and vol up together to go to recovery.
2. What command did you run prior? Im asking because you may typed a diff command that could've affected this?

xgneilx said:
Hi!
1. What do you want to accomplish by executing that? Because you can just press and hold power and vol up together to go to recovery.
2. What command did you run prior? Im asking because you may typed a diff command that could've affected this?
Click to expand...
Click to collapse
1. I'm using that command to make sure TWRP is not replaced by original recovery.
* according to the official instruction: https://twrp.me/xiaomi/xiaomimimax3.html , I tried the hard reboot to twrp by holding pwr+vol-up, but it got stuck in Miui logo. So, I tried to use the flash boot command instead to make sure the twrp works correctly, but it isn't on my Mi Max 3 somehow.
2.
> adb reboot bootloader
> fastboot flash recovery twrp-3.2.3-0-nitrogen.img
> fastboot boot twrp-3.2.3-0-nitrogen.img OR > fastboot reboot && pwr+vol-up buttons
I have googled and found similar situation on different devices, and all seems to solved by a working twrp.
Mine max3 is 4G+64G, not sure if that makes a difference, also it's an official global version that comes with 9.6.4.0
Here's the getvar:
Code:
(bootloader) DP:0x0
(bootloader) token:V...4=
(bootloader) crc:1
(bootloader) cpuid:0x8xxxxxxx
(bootloader) board_version:4.19.0
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3905
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM EMMC
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xC7F7FBE00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xC0000000
(bootloader) secure:yes
(bootloader) serialno:4xxxxxxx
(bootloader) product:nitrogen
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi

Mine came also with official global but with 9.6.7.0. Anyways, there are several other recovery app here, have you tried any of it? When you are able to flash other recovery and boot using it, you may flash twrp from it.

xgneilx said:
Mine came also with official global but with 9.6.7.0. Anyways, there are several other recovery app here, have you tried any of it? When you are able to flash other recovery and boot using it, you may flash twrp from it.
Click to expand...
Click to collapse
Great, can you give me some suggestions? I'm not sure which to try, cause after my x10, it's always TWRP.
Is yours a 4+64 model?

totalz said:
Great, can you give me some suggestions? I'm not sure which to try, cause after my x10, it's always TWRP.
Is yours a 4+64 model?
Click to expand...
Click to collapse
Use OrangeFox. It's one of the better ones.

totalz said:
Great, can you give me some suggestions? I'm not sure which to try, cause after my x10, it's always TWRP.
Is yours a 4+64 model?
Click to expand...
Click to collapse
yup. 4x64 model. Read above post for recommendation.

Lenovo P2 USA bands.

Hi,
I need Yours HELP. Because I reading very conflicting information.
And I am green with flash phones.
I must re-flash my P2... It seems good idea to my problem.
At the moment I have ROM: p2a42_s251_171107_row - last OTA.
Bootloader is LOCK, I uses factory ROM.
But I changed... APN on USA band and I am not make calls.
I know it was big mistake !!!! after the fact.
When I try install rom from SD, installation returns error about 50%. And finish...
P2a42_S062_170117_ROW_TO_P2a42_S232_170320_ROW_WC00AFB1F4a
and chenge name on: update.zip
I read it re-fash ROM, can resolve problem...???
What can I do?
What I make wrong?

I tryed...,
Fastboot oem device-info
(bootloader) slot-count: not found
(bootloader) slot suffixes: not found
(bootloader) slot-suffixes: not found
....
(bootloader) Device Secure boot: yes
(bootloader) Device tampered: false
(bootloader) Devive unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charher screen enabled: false
(bootloader) Display panel:
OKAY [0,080s]
finished. total time 0,081s
I found:
https://forum.xda-developers.com/g5/how-to/recovering-2g-3g-set-radio-band-to-usa-t3668767
Can I make those commands?

forum_dyskusyjne said:
I tryed...,
Fastboot oem device-info
(bootloader) slot-count: not found
(bootloader) slot suffixes: not found
(bootloader) slot-suffixes: not found
....
(bootloader) Device Secure boot: yes
(bootloader) Device tampered: false
(bootloader) Devive unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charher screen enabled: false
(bootloader) Display panel:
OKAY [0,080s]
finished. total time 0,081s
I found:
https://forum.xda-developers.com/g5/how-to/recovering-2g-3g-set-radio-band-to-usa-t3668767
Can I make those commands?
Click to expand...
Click to collapse
yes, you can use erase modem commands and erase cache command too, they are safe.
make sure you have a proper backup of everything in case something goes wrong :fingers-crossed:
and as for your post goes, you can't directly flash an old ota to a newer firmware, you have to first fully downgrade to S233 that's 7.0, before doing that make sure you wipe everything from recovery wipe data, format data, etc options available in the stock recovery.
Then, try upgrading to S244, S251, S252.
Hit the like button!

(SOLVED)Need somebody really expert on unlock bootloader on this phone, please halp

So i brough this weird phone, and i guess i will need somebody really expert on this unlock bootloader thing this time.
0 - Locked bootloader, but in motorola software says it have root
1 - I can boot to system normaly, use sim, imeis are all ok (but there is no gapps and no way to flash it)
2 - LineageOS Pie rom
3 - i can acess fastboot (that says is locked)
4- i cannot acess recovery (when select this option, returns to fastboot)
5 - there is no "oem unlock" option in "developer options"
6 - my phone is elegible to unlock, so i already got the motorola code through the site (to use with "fastboot oem unlock CODE", but when i do the command line, says that i need to turn on the oem unlock option that doesnt exist in "developer options"
7 - If i try to boot any twrp img in fastboot mode (to flash twrp zip), the phone reboot to fastboot again (as i said, i have no acess to recovery)
8- If i update the magisk (comes with lineageOS), the system wont boot anymore, and says its corrupt, shows a recovery red window but only with "factory format" option (and if i do, the phone just format as it was in the beginning)
9 - if i try to flash anything in fastboot, i will fail coz of couse, its locked.
10- i have the box, original items, papers and documents (but its out of warranty).
11 - tried Lenovo Moto Smart Assistant, but when i put my model and awaits to fastboot, says that cannot do nothing.
I just want to use stock oreo, nothing more, is too much to ask? :crying: :crying: :crying:
Please dont ask me what the previous owner did to this phone, i dont know(he neighter, said only that after trying to install custom rom, bricked the phone, but somehow could install this lineageOS :crying: :crying:
Any help to this poor soul? Thanks already :crying: :crying:

What is the model, what does it say by the charger port? XT1789-??
In fastboot issue 'fastboot getvar all' w/o quotes and post that info here -minus your imei# that will give an idea of what firmware you need to flash to get back to stock and unlock.

41rw4lk said:
What is the model, what does it say by the charger port? XT1789-??
In fastboot issue 'fastboot getvar all' w/o quotes and post that info here -minus your imei# that will give an idea of what firmware you need to flash to get back to stock and unlock.
Click to expand...
Click to collapse
Thanks thanks for comment <3
its a XT1789-05, and the info you asked:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-43c7c77-190608
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: ROW
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: MSM8998 2.1 (4)
(bootloader) serialno: 0049486108
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 5291F1FC
(bootloader) securestate: flashing_locked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 03-22-2019
(bootloader) sku: XT1789-05
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) battery-voltage: 4051
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:9/PPX29.159-19/
(bootloader) ro.build.fingerprint[1]: 02844:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.11.19.nash.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-06500-sdm660.0
(bootloader) version-baseband: M8998_50.71.02.95R NRD
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-gf9e16d5 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Sat Jun 8 12:34:38 CDT 2019
(bootloader) git:abl: MBM-3.0-nash_retail-43c7c77-190608
(bootloader) git:xbl: MBM-3.0-nash_retail-4fc2afc-190608
(bootloader) gitmic: MBM-3.0-nash_retail-4fc2afc-190608
(bootloader) git:rpm: MBM-3.0-nash_retail-404f7ba-190608
(bootloader) git:tz: MBM-3.0-nash_retail-3537781-190608
(bootloader) git:hyp: MBM-3.0-nash_retail-3537781-190608
(bootloader) git:devcfg: MBM-3.0-nash_retail-3537781-190608
(bootloader) git:cmnlib: MBM-3.0-nash_retail-3537781-190608
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-3537781-190608
(bootloader) git:keymaster: MBM-3.0-nash_retail-3537781-190608
(bootloader) git:storsec: MBM-3.0-nash_retail-3537781-190608
(bootloader) gitrov: MBM-3.0-nash_retail-3537781-190608
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.453s

From what I see what I've been able to confirm, it looks like your phone was updated to pie at some point. So going back to oreo isn't an option since the modem won't jive. Everything seems to be retail Brazil firmware, so you need the retbr 9.0 firmware. The only thing concerning is the previous owner and whatever they did, especially since it resulted in a brick and they jimmied up this concoction. Just to verify, when you boot to os you do have a signal and all that correct? If that is correct then retbr modem works for you and you should be able to flash stock pie and everything should work. Then you'll be able to unlock and all that.
So if your signal is there then jump to this forum and follow the directions to flash retbr pie. Feel free to ask questions about flashing there. They seem to have retbr sorted and working there.
https://forum.xda-developers.com/z2-force/how-to/update-android-pie-t3893509/page72

41rw4lk said:
From what I see what I've been able to confirm, it looks like your phone was updated to pie at some point. So going back to oreo isn't an option since the modem won't jive. Everything seems to be retail Brazil firmware, so you need the retbr 9.0 firmware. The only thing concerning is the previous owner and whatever they did, especially since it resulted in a brick and they jimmied up this concoction. Just to verify, when you boot to os you do have a signal and all that correct? If that is correct then retbr modem works for you and you should be able to flash stock pie and everything should work. Then you'll be able to unlock and all that.
So if your signal is there then jump to this forum and follow the directions to flash retbr pie. Feel free to ask questions about flashing there. They seem to have retbr sorted and working there.
https://forum.xda-developers.com/z2-force/how-to/update-android-pie-t3893509/page72
Click to expand...
Click to collapse
Yes all works fine, sim cards, wifi, etc. But i already tried to flash stock oreo but the phone dont even allow any file flash because of locked bootloader. The pie files will bypass that? Anyways thanks thanks again to your answer, i will try what you said and follow the link (since i fix my notebook psu that screew up just now )

41rw4lk said:
From what I see what I've been able to confirm, it looks like your phone was updated to pie at some point. So going back to oreo isn't an option since the modem won't jive. Everything seems to be retail Brazil firmware, so you need the retbr 9.0 firmware. The only thing concerning is the previous owner and whatever they did, especially since it resulted in a brick and they jimmied up this concoction. Just to verify, when you boot to os you do have a signal and all that correct? If that is correct then retbr modem works for you and you should be able to flash stock pie and everything should work. Then you'll be able to unlock and all that.
So if your signal is there then jump to this forum and follow the directions to flash retbr pie. Feel free to ask questions about flashing there. They seem to have retbr sorted and working there.
https://forum.xda-developers.com/z2-force/how-to/update-android-pie-t3893509/page72
Click to expand...
Click to collapse
not worked :crying:
did all he said : Unzip the 2 files (flashall ... and firm ...) and place them in a folder
Click on "Preparation.bat", you must generate a "flash.bat file", double click with the phone in download mode
It's all, really clean installation
It was what I did, I am not responsible for damage to your equipment
but nothing can be flashed because of bootloader locked:
C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT
_regulatory-DEFAULT_CFC.xml>echo off
max-sparse-size: 268435456
finished. total time: 0.003s
...
OKAY [ 0.009s]
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ 0.050s]
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.229s]
finished. total time: 0.281s
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.384s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.546s
target reported max download size of 536870912 bytes
sending 'modem_a' (78412 KB)...
OKAY [ 4.390s]
writing 'modem_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 4.417s
any more ideas ? :crying: :crying: :crying:

brunojborges said:
not worked :crying:
did all he said : Unzip the 2 files (flashall ... and firm ...) and place them in a folder
Click on "Preparation.bat", you must generate a "flash.bat file", double click with the phone in download mode
It's all, really clean installation
It was what I did, I am not responsible for damage to your equipment
but nothing can be flashed because of bootloader locked:
C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT
_regulatory-DEFAULT_CFC.xml>echo off
max-sparse-size: 268435456
finished. total time: 0.003s
...
OKAY [ 0.009s]
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ 0.050s]
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.229s]
finished. total time: 0.281s
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.384s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.546s
target reported max download size of 536870912 bytes
sending 'modem_a' (78412 KB)...
OKAY [ 4.390s]
writing 'modem_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 4.417s
any more ideas ? :crying: :crying: :crying:
Click to expand...
Click to collapse
well, I recommend that you download the Lenovo moto application, something like that is the name, after installing it, connect the terminal in Lenovo moto app in fastboot mode, click on the Flash option and then where it says to recover, complete the information that asks you wait for it to finish, an official ROM flashed, and from there you can start with the bootloader unlock

Have you signed into a google account on the phone? Do you see developer options in settings? I know you said you didn't see oem unlocking so that's why I ask. We'll try to tackle those and get you unlocked. It's possible that you pbl and trust zone is messed up so a blankflash might be needed to sort that.
With a locked bootloader you should able to flash the same firmware version or newer, but if your chain of trust is compromised it's a little difficult, but not impossible.

41rw4lk said:
Have you signed into a google account on the phone? Do you see developer options in settings? I know you said you didn't see oem unlocking so that's why I ask. We'll try to tackle those and get you unlocked. It's possible that you pbl and trust zone is messed up so a blankflash might be needed to sort that.
With a locked bootloader you should able to flash the same firmware version or newer, but if your chain of trust is compromised it's a little difficult, but not impossible.
Click to expand...
Click to collapse
i cant sign into google accouts because there is no gapps pre installed on LineageOS, and i cant flash anything because the bootloader locked. There is developer options but only the adb debbug option, there is no "oem unlock" option (thats why when i try to fastboot oem unlock "CODE", the prompt says that i need to first activate the "oem unlock" option into the system, but as i said, there is no OEM option inside developer options. Maybe could be this "chain of thrust" thing. What should i do? thanks

brunojborges said:
i cant sign into google accouts because there is no gapps pre installed on LineageOS, and i cant flash anything because the bootloader locked. There is developer options but only the adb debbug option, there is no "oem unlock" option (thats why when i try to fastboot oem unlock "CODE", the prompt says that i need to first activate the "oem unlock" option into the system, but as i said, there is no OEM option inside developer options. Maybe could be this "chain of thrust" thing. What should i do? thanks
Click to expand...
Click to collapse
Can you not sign into google from accounts in settings? Also, you can download the playstore apk and install it manually. Usually to enable oem unlocking you have to be signed into google. So check accounts and see if you can sign in there, and/or d/l the apk and sign in there. Reboot and check dev options again for oem unlocking once you've signed in.

Heridg said:
well, I recommend that you download the Lenovo moto application, something like that is the name, after installing it, connect the terminal in Lenovo moto app in fastboot mode, click on the Flash option and then where it says to recover, complete the information that asks you wait for it to finish, an official ROM flashed, and from there you can start with the bootloader unlock
Click to expand...
Click to collapse
i need unlock bootloader just to revert to stock. I dont want to keep unlocked, or install custom stuff. If i just had the "oem unlock" option in developer options, i could fix that. And about moto smart assistant, when i put my phone and do this steps, after choosing my phone number and model, after the program detect my phone in fastboot mode, it shows a message, "this device is not supported".

41rw4lk said:
Can you not sign into google from accounts in settings? Also, you can download the playstore apk and install it manually. Usually to enable oem unlocking you have to be signed into google. So check accounts and see if you can sign in there, and/or d/l the apk and sign in there. Reboot and check dev options again for oem unlocking once you've signed in.
Click to expand...
Click to collapse
installed both, play store and services apk's from different sites. Tried clean cache, and anything else, but there is always a message forcing to close app. Cant open them.

(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
maybe isnt this messing this phone ?

Well the bottom line is you got a mismatched system, no recovery, a locked bootloader, no gapps; what a mess.
First I would hit fastboot and issue 'fastboot -w' w/o quotes. That will format data and get rid of potentially any bits of garbage. Once that is done reboot to system and you should have to do setup again. Part of setup is signing into google, so once that is done check dev settings again to see if oem unlocking has become available. It's odd that it's just not there. Most times it's there and possibly just greyed out.
If that doesn't yield any changes then a blankflash is the only option you have left to sort it, that's the dicey part that will either make it or break it. We'll worry about that if and when we get there. Just be warned this part will be the most dangerous so it's your decision to proceed from here. Whoever gave you that phone didn't do you any favors.

41rw4lk said:
Well the bottom line is you got a mismatched system, no recovery, a locked bootloader, no gapps; what a mess.
First I would hit fastboot and issue 'fastboot -w' w/o quotes. That will format data and get rid of potentially any bits of garbage. Once that is done reboot to system and you should have to do setup again. Part of setup is signing into google, so once that is done check dev settings again to see if oem unlocking has become available. It's odd that it's just not there. Most times it's there and possibly just greyed out.
If that doesn't yield any changes then a blankflash is the only option you have left to sort it, that's the dicey part that will either make it or break it. We'll worry about that if and when we get there. Just be warned this part will be the most dangerous so it's your decision to proceed from here. Whoever gave you that phone didn't do you any favors.
Click to expand...
Click to collapse
Please sr teach me how to do this blankflash thing, in the truth, i could bring back imeis erased from a axon 7 i had, making A LOT of crazy and dangerous moves (deleting partitions, backup binary files, editing and return back, etc), but im new with this motorola. Please teach me :crying: :crying:

41rw4lk said:
Well the bottom line is you got a mismatched system, no recovery, a locked bootloader, no gapps; what a mess.
First I would hit fastboot and issue 'fastboot -w' w/o quotes. That will format data and get rid of potentially any bits of garbage. Once that is done reboot to system and you should have to do setup again. Part of setup is signing into google, so once that is done check dev settings again to see if oem unlocking has become available. It's odd that it's just not there. Most times it's there and possibly just greyed out.
If that doesn't yield any changes then a blankflash is the only option you have left to sort it, that's the dicey part that will either make it or break it. We'll worry about that if and when we get there. Just be warned this part will be the most dangerous so it's your decision to proceed from here. Whoever gave you that phone didn't do you any favors.
Click to expand...
Click to collapse
C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT
_regulatory-DEFAULT_CFC.xml>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.012s
didnt worked. I have to do this blankflash.

brunojborges said:
Please sr teach me how to do this blankflash thing, in the truth, i could bring back imeis erased from a axon 7 i had, making A LOT of crazy and dangerous moves (deleting partitions, backup binary files, editing and return back, etc), but im new with this motorola. Please teach me :crying: :crying:
Click to expand...
Click to collapse
If you've already tried 'fastboot -w' and nothing has changed for you then you can try to blankflash and reflash the pie firmware you downloaded previously. Read the whole post before you try and just know that there is a real chance of failure. Plenty have recovered their phone, even with locked bootloaders, but it's not 100% success. I think the biggest problem you might face is finding the proper firmware to flash, but I would start with the pie firmware you already have since it seems that pie is already on your phone (sort of).
Here is the blankflash post. Follow the directions closely, read it all, and be warned what you do is your choice.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5

41rw4lk said:
If you've already tried 'fastboot -w' and nothing has changed for you then you can try to blankflash and reflash the pie firmware you downloaded previously. Read the whole post before you try and just know that there is a real chance of failure. Plenty have recovered their phone, even with locked bootloaders, but it's not 100% success. I think the biggest problem you might face is finding the proper firmware to flash, but I would start with the pie firmware you already have since it seems that pie is already on your phone (sort of).
Here is the blankflash post. Follow the directions closely, read it all, and be warned what you do is your choice.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
Click to expand...
Click to collapse
thanks, i will read 10x before do anytyhing, and will do carefully. i had nothing else to do. This will fix my phone or it will turn a paper weight. Im warned. Thank you sir, wish me luck and i will tell u if i have any sucess.

41rw4lk said:
If you've already tried 'fastboot -w' and nothing has changed for you then you can try to blankflash and reflash the pie firmware you downloaded previously. Read the whole post before you try and just know that there is a real chance of failure. Plenty have recovered their phone, even with locked bootloaders, but it's not 100% success. I think the biggest problem you might face is finding the proper firmware to flash, but I would start with the pie firmware you already have since it seems that pie is already on your phone (sort of).
Here is the blankflash post. Follow the directions closely, read it all, and be warned what you do is your choice.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
Click to expand...
Click to collapse
if i click on .bat file:
C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT
_regulatory-DEFAULT_CFC.xml>.\qboot.exe blank-flash
< waiting for device >
and if i do manually "fastboot oem blankflash":
C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT
_regulatory-DEFAULT_CFC.xml>fastboot oem blankflash
...
(bootloader) Command Restricted
FAILED (remote failure)
finished. total time: 0.012s
:crying: :crying: :crying: :crying: :crying: :crying: :crying:
there is any way to force hard brick and them enter in Qualcomm HS-USB QDLoader 900 mode? Maybe this way will be easier
:crying: :crying:

brunojborges said:
if i click on .bat file:
C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT
_regulatory-DEFAULT_CFC.xml>.\qboot.exe blank-flash
< waiting for device >
and if i do manually "fastboot oem blankflash":
C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT
_regulatory-DEFAULT_CFC.xml>fastboot oem blankflash
...
(bootloader) Command Restricted
FAILED (remote failure)
finished. total time: 0.012s
:crying: :crying: :crying: :crying: :crying: :crying: :crying:
there is any way to force hard brick and them enter in Qualcomm HS-USB QDLoader 900 mode? Maybe this way will be easier
:crying: :crying:
Click to expand...
Click to collapse
boot to os, make sure adb debugging is enabled, then open a cmd prompt and enter 'adb reboot edl' w/o quotes