LONG STORY SHORT ROOTED MY PHONE HAD A CUSTOM ROM I WANTED A DIFFERENT ROM THE ROM I HAD REPLACED MY TWRP WITH THEIR RECOVERY AND I COULDNT INSTALL THE NEW ROM USING THEIRS SO I FACTORY RESET THE PHONE NOW I I CANT GET OUT OF FAST BOOT EVERYTHING I CLICK JUST SAYS N/A AND PUTS ME IN BOOTLOADER LOGS
C:\Program Files (x86)\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' (23420 KB)...
OKAY [ 0.505s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.515s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
cannot load 'recovery.img': No such file or directory
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
OKAY [ 0.504s]
booting...
FAILED (remote failure)
finished. total time: 1.251s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.129s]
finished. total time: 0.130s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot format system
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
Formatting is not supported for file system with type 'raw'.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:data: not found
erasing 'data'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.008s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.018s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.140s]
finished. total time: 0.141s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase partition
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
erasing 'partition'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.007s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot format partition
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
Formatting is not supported for file system with type ''.
C:\Program Files (x86)\Minimal ADB and Fastboot>
IS WHAT I HAVE SO FAR NOTHING WORKS. I SPENT 600 ON THIS PHONE PLEASE SOMEONE HELP!!!!!!!!
First of all, the rom had it's OWN recovery? That is a rom that should not be flashed. It looks like the rom or recovery completely wiped the partitions on your phone. Have you tried getting into download mode?
Your mistake was factory resetting the phone on a custom rom. Don't EVER factory reset unless it is a STOCK based rom and you're doing it through the phones settings or you are doing it through recovery to flash a new rom.
Maybe try using Google's Android SDK? Maybe there is an issue with Minimal ADB.
I'm just trying to list some options.
Download the stock Firmware for your device, extract the files in your adb/fastboot folder.
Download that file https://drive.google.com/open?id=0B134drJ4-Ed0MHQ5aE1wUmp5eFk
and place it in your adb/fastboot folder. Run the batch fail and wait for complete. If that don't work, your partition table is broken.
yea it has its own recovery like it wasn't twrp when I booted in to recovery it just said recovery on top and said apply update and advanced and that's it. it wasn't twrp at all and ill try the listed options obove and update thread thanks you guys I'm a noobie to this
when I click your link it says url invalid
what is that file u linked in because it will not let me go to that url
Do u need stock firmware for US Addison? I had a tough time finding it but have it in my Dropbox if you need it. Along with fastboot TWRP etc. https://www.dropbox.com/sh/ndo7qz1h41rsv8i/AABeNwCnJojSGQuF4REAOCd3a?dl=0
https://drive.google.com/open?id=0B134drJ4-Ed0MHQ5aE1wUmp5eFk
Sorry copied the wrong link. Now it should work.
bro you are a life saver this twrp was exactly what I needed so I could flash twrp and get stock nougat it still tells me just n/a on the boot up but after 5-10 it boots like normal thanks man
That's a batch file to flash a complete stock firmware file. For me works the Link fine.
Hi,
I have XT1635-03, when i try to unlock bootloader got following message
fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found ...
(bootloader) Unlock data:
(bootloader) cid_get_cid_data: Version 0 datablock
(bootloader) Failed OKAY [ 0.012s] finished. total time: 0.014s
How to fix it? want to install custom rom, its chinese set without playstore, tried couple of methods to install
playstore put also they fail. any help plz?
thx
kami2k said:
Hi,
I have XT1635-03, when i try to unlock bootloader got following message
fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found ...
(bootloader) Unlock data:
(bootloader) cid_get_cid_data: Version 0 datablock
(bootloader) Failed OKAY [ 0.012s] finished. total time: 0.014s
How to fix it? want to install custom rom, its chinese set without playstore, tried couple of methods to install
playstore put also they fail. any help plz?
thx
Click to expand...
Click to collapse
For unlocking bootloader please follow this guide : https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
For installing custom recovery please follow this : https://forum.xda-developers.com/moto-z-play/how-to/correct-rooting-moto-z-play-feb-17-t3560268
Its the 2nd step, I am falling at 1st step, thanks anyway
Hi,
I am stuck, and figured I need to ask you guys some questions.
As I have done previously with other phones, I bought a used Moto Z2 Force to fix up. I bought a bricked phone with no hardware problems. The previous user said he updated it in Stock to Android Pie, and after the update the phone wouldnt boot anymore, so he sold it. I figured I would just debrick it and use it with LineageOS.
But I didnt succeed, and dont know what else to try, so Im asking you.
It is a XT-1789-06 bought in Germany.
So: When I start the phone up, it says: "Your device is corrupt. it cant be trusted and will not boot." and that I should turn to the official Motorola unlocking portal.
I did that, followed the instructions, was able to boot into fastboot mode, and got the Code, and with that the one from motorola, but when I try the
Code:
fastboot oem unlock XXXXXXXXXXXXXX
I get the following:
Code:
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.008s]
finished. total time: 0.008s
Obviously I cant do that, because the phone wont boot up. But event though it says OKAY, there is no change to the variable: securestate: flashing_locked, and i still cant flash anything, and the startup error remains the same. When I try "fastboot flashing unlock" I get the same message.
So, the next thing I tried was the LMSA software. It did the Flash-> rescue-> choose model XT1789-06 -> and flash, and it downloaded the NASH_PPX29.159_23_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml.zip ROM, and apparently did something to the phone, but it didnt change the outcome, still the phone shows the same error on bootup.
Then I did a fastboot -w, after which the phone didnt show anything anymore on bootup, just blank screen, and the tried both steps described above again, stil no change.
Then I tried to boot into the newest Twrp image with "fastboot boot twrp.....img" but it fails with the error: too many links.
Then I tried all of the above in Ubuntu, then on windows with the fastboot files given in the guide in this forum, and then with the mfastboot, that I found somewhere else. Same outcome.
Then I tried just flashing the Stockrom that LMSA downloaded with the flashall method from the same guide, but flashing fails with: Permission denied.
So, do you have any ideas what more I can try to unbrick this phone? I will be happy to give you any further information. I will append fastboot getvar all as soon as I reboot my PC in 2 min.
Edit:
Code:
F:\motoz2force>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-cd73d31dc
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EMEA
(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
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224ZCL4C
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 81C2C8EF
(bootloader) securestate: flashing_locked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: XXXXXXXXXXXXXXXXXX
(bootloader) meid:
(bootloader) date: 05-17-2018
(bootloader) sku: XT1789-06
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4120
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:8.0.0
(bootloader) ro.build.fingerprint[1]: 9-34-21/21:user/release-
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.481.21.
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998_20207.117.02.41-01.02R NE
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g3c2
(bootloader) kernel.version[1]: [email protected]) (gcc version 4
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SM
(bootloader) kernel.version[3]: Fri Nov 2 11:29:48 CDT 2018
(bootloader) git:abl: MBM-3.0-nash_retail-cd73d31dc-180828
(bootloader) git:xbl: MBM-3.0-nash_retail-9869834-180828
(bootloader) git:pmic: MBM-3.0-nash_retail-9869834-180828
(bootloader) git:rpm: MBM-3.0-nash_retail-b13e14f-180828
(bootloader) git:tz: MBM-3.0-nash_retail-22c9393-190327
(bootloader) git:hyp: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:devcfg: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:cmnlib: MBM-3.0-nash_retail-22c9393-190327
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:keymaster: MBM-3.0-nash_retail-7d478e6-180828
(bootloader) git:storsec: MBM-3.0-nash_retail-22c9393-190327
(bootloader) git:prov: MBM-3.0-nash_retail-22c9393-190327
(bootloader) qe: "qe 1/1"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(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: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 1
all: listed above
finished. total time: 0.177s
Edit 2: While I can boot into fastboot mode, when I try to start recovery mode from there, I get the same "Your device is corrupt", so no adb for me.
Edit3:
"fastboot -w" results in:
Code:
F:\motoz2force>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
It's odd that it says 'a' is unbootable, most updates and roms usually go to 'b' so if there was trouble I'd expect it to be on 'b' slot.. Anyways, it's possible that the chain of trust is corrupt and you can try to blankflash to remedy that and hopefully be able to flash (even with a locked bootloader). You can follow this guide to try and blankflash, if successful then you can try to flash your firmware again. *Note - with a locked bootloader you can only flash the same firmware or newer, that means you should try the one that was downloaded by lmsa. Also, look by your charger port to verify that it is indeed an -06 variant and not just saying -06 because that was what was flashed.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
If no success all around, you can try switching slots and making 'a' the active slot. Once it is active, try to boot it and see if it will, if not, try flashing the firmware you have on that slot.
Thank you for your help. Unfortunatley it didnt get me very far. I installed the drivers on my Vista-PC. When I executed the blank-flash.bat It just said <waiting for device>. Then I removed Motorola and te qualcomm drivers, rebooted, installed the qualcomm-drivers again, rebooted, but then in the device manager the phone just showed up as "Fastboot nash S" without proper drivers. I couldnt get the qualcomm drivers to recognize the device. blank-flash.bat still showed the same thing.
Other ports, same behaviour.
Then I reinstalled moto drivers to test the other commands.
When I tried "fastboot oem blankflash" I got:
Code:
(bootloader) Command Restricted
FAILED (remote failure)
finished. total time: 0.005s
Then I tried
Code:
F:\motoz2force>fastboot set_active a
Setting current slot to 'a'...
FAILED (remote failure)
finished. total time: 0.008s
I checked next to the charging port, it is really a XT1789-06.
Stuck again. Any other pointers? that would be so great. thanks in advance. I am still learning a lot here, even without progress.
I'm in the same situation, but with an xt1789-05, but it turns on normal, but I don't have Wi-Fi and no data network, and I've tried everything to remove the OEM lock, but without success, and whenever I try a ROM new, it gives me bootloader failure or error.
I'm sure your command to set the other slot is wrong fastboot --set-active=a
As for the blankflash, you need to be in edl mode which isn't always the easiest to get into manually and it's even harder when your system is jumbled. (You think it would be easier since that's when you need it). Either way, that's why blankflash isn't running.
When I wanted to get into edl mode I was holding volume up+power while connecting USB to PC.
OK, thanks for your further tips.
So my goal is to get the phone into edl/blankflash mode, correct?
I would consider myself successful if theres a device showing up in the windows device manager thats called "Qualcomm HS-USB QDLoader 9008" or something similar, correct? Alternatively if the QFIL-Tools recognizes a port.
What I tried:
"fastboot oem blankflash" in fastboot mode, unsuccessful, results shown in a previous post.
Pressing Volume up + power while plugging the phone in, nothing happens.
And I even tried this: https://www.youtube.com/watch?v=DexLELi04XY, but nothing happens, neither the phone showing anything, nor the PC recognizing any device.
... to bad.
I tried to follow this Guide: https://www.droidsavvy.com/unbrick-qualcomm-mobiles/ , but when I try to set the variables in the admin terminal for the first step, it says (translated) "The storage for the startup-configuration files could not be opened. The system could not find the files."
I am close to giving up here. A shame, I really had my hopes up, but I am kind of out of my league here.
You should try running the lmsa tool again. Were you ever successful in switching slots? If you're unsure of the syntax, type fastboot --help that should show you the proper way. Blankflash should be your last option.
wolzotan said:
OK, thanks for your further tips.
So my goal is to get the phone into edl/blankflash mode, correct?
I would consider myself successful if theres a device showing up in the windows device manager thats called "Qualcomm HS-USB QDLoader 9008" or something similar, correct? Alternatively if the QFIL-Tools recognizes a port.
What I tried:
"fastboot oem blankflash" in fastboot mode, unsuccessful, results shown in a previous post.
Pressing Volume up + power while plugging the phone in, nothing happens.
And I even tried this: https://www.youtube.com/watch?v=DexLELi04XY, but nothing happens, neither the phone showing anything, nor the PC recognizing any device.
... to bad.
I tried to follow this Guide: https://www.droidsavvy.com/unbrick-qualcomm-mobiles/ , but when I try to set the variables in the admin terminal for the first step, it says (translated) "The storage for the startup-configuration files could not be opened. The system could not find the files."
I am close to giving up here. A shame, I really had my hopes up, but I am kind of out of my league here.
Click to expand...
Click to collapse
Hi There I have same situation as you, did you fix your phone?
and how you fixed your phone?
I have XT1789-05, please help me, thanks a lot
hi AHMN48, i saw your posts around and figured you have the same problem. I have not yet found a solution unfortunately.
I have tried some more suggestions made here:
Code:
F:\motoz2force>fastboot --set_active=_a
Setting current slot to 'a'...
FAILED (remote failure)
finished. total time: 0.016s
Code:
F:\motoz2force>fastboot set_active a
Setting current slot to 'a'...
FAILED (remote failure)
finished. total time: 0.016s
Code:
F:\motoz2force>fastboot reboot emergency
rebooting into emergency download (EDL) mode...
OKAY [ 0.000s]
finished. total time: 0.000s
I got really excited when that happened, but it just came up in fastboot mode again.
this is my screen, if it helps anything
and I tried those commands on all of my usb ports, and most of the ports on my docking station. Its a Lenovo W520, and I have windows 7 and Ubuntu 18.04 available.
Anyways, the only thing I can do to the phone that apparently does something ist the rescue-flash with LMSA. When I do that, It shows the whole "Your device is corrupt"-Thing, and the yellow line from the fastboot screen linked above that says "Software status: modified" vanished. This line reappears as soon as I try to send any of the above fastboot commands, be it the slo-switching-thing or "fastboot -w", doesnt matter. As soon as this happens, the phone also doesnt show the "Your device is corrupt"-alert anymore too, just a black screen. then I rescue flash with LMSA again, and so on.
I tried RSD lite, and it recognizes a device called "fastboot nash S" and status "connected...", but when I try to flash anything, it tells me: "The phone failed to switch to fastboot mode" even though it still is in fastboot mode from the beginning. But Im also not sure if Im doing it right, because i dont know which of the decompressed files from the stock-rom Im supposed to choose for a flashfile
wolzotan said:
Anyways, the only thing I can do to the phone that apparently does something ist the rescue-flash with LMSA. When I do that, It shows the whole "Your device is corrupt"-Thing, and the yellow line from the fastboot screen linked above that says "Software status: modified" vanished. This line reappears as soon as I try to send any of the above fastboot commands, be it the slo-switching-thing or "fastboot -w", doesnt matter. As soon as this happens, the phone also doesnt show the "Your device is corrupt"-alert anymore too, just a black screen. then I rescue flash with LMSA again, and so on.
I tried RSD lite, and it recognizes a device called "fastboot nash S" and status "connected...", but when I try to flash anything, it tells me: "The phone failed to switch to fastboot mode" even though it still is in fastboot mode from the beginning. But Im also not sure if Im doing it right, because i dont know which of the decompressed files from the stock-rom Im supposed to choose for a flashfile
Click to expand...
Click to collapse
RSD is a bit antiquated and we use a flashall.bat in the command prompt to do the same thing. In your OP you posted your getvar output and it looks like it still has oreo on it. Whether lmsa has actually done anything and flashed pie, it would appear not according to you. Run fastboot getvar all again and look at your build fingerprint, if it is still oreo 8.0 then lets try flashing the last oreo version instead of trying to jump to pie.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
ok. Thanks so much 41rw4lk, for walking me through this. Still no luck unfortunately.
I ran the following commands on a new laptop, new windows 10, that I hadnt tried before. However the outcome was identical, as far as i see.
I did download the firmware you linked. I ran the preparation.bat, and then the flashfile.bat. this is the log. It shows the same error messages, that I got with the Pie firmware.
Code:
max-sparse-size: 268435456
finished. total time: 0.000s
...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ 0.016s]
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.234s]
finished. total time: 0.250s
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.547s]
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.656s
target reported max download size of 536870912 bytes
sending 'modem_a' (97411 KB)...
OKAY [ 6.896s]
writing 'modem_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 6.896s
target reported max download size of 536870912 bytes
sending 'fsg_a' (5600 KB)...
OKAY [ 0.297s]
writing 'fsg_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.312s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4496 KB)...
OKAY [ 0.219s]
writing 'bluetooth_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.234s
target reported max download size of 536870912 bytes
sending 'dsp_a' (16384 KB)...
OKAY [ 0.828s]
writing 'dsp_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.844s
target reported max download size of 536870912 bytes
sending 'logo_a' (3524 KB)...
OKAY [ 0.172s]
writing 'logo_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.187s
target reported max download size of 536870912 bytes
sending 'boot_a' (23353 KB)...
OKAY [ 1.172s]
writing 'boot_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 1.172s
target reported max download size of 536870912 bytes
sending 'system_a' (516200 KB)...
OKAY [ 30.593s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 30.608s
target reported max download size of 536870912 bytes
sending 'system_a' (522116 KB)...
OKAY [ 26.218s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 26.233s
target reported max download size of 536870912 bytes
sending 'system_a' (519014 KB)...
OKAY [ 25.927s]
writing 'system_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 25.927s
target reported max download size of 536870912 bytes
sending 'system_a' (516292 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 126.811s
target didn't report max-download-size
sending 'system' (523200 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s
target didn't report max-download-size
sending 'system' (413555 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
target didn't report max-download-size
sending 'system_b' (515182 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
target didn't report max-download-size
sending 'system_b' (319593 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s
target didn't report max-download-size
sending 'oem' (163061 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
erasing 'modemst1'...
FAILED (command write failed (No error))
finished. total time: -0.000s
erasing 'modemst2'...
FAILED (command write failed (No error))
finished. total time: 0.000s
erasing 'carrier'...
FAILED (command write failed (No error))
finished. total time: -0.000s
erasing 'cache'...
FAILED (command write failed (No error))
finished. total time: 0.000s
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: -0.000s
erasing 'ddr'...
FAILED (command write failed (No error))
finished. total time: 0.000s
target didn't report max-download-size
sending 'fsg' (5600 KB)...
FAILED (command write failed (No error))
finished. total time: 0.016s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4496 KB)...
OKAY [ 0.270s]
writing 'bluetooth_a'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.290s
...
OKAY [ -0.000s]
finished. total time: -0.000s
-------------------------------------------------------------------------
please scroll up and check your flash for any errors
-------------------------------------------------------------------------
And then a current flashboot getvar all:
Code:
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-43c7c77-190705
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EMEA
(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 (0)
(bootloader) serialno: ZY224ZCL4C
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 81C2C8EF
(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: XXXXXXXXXXXXXX
(bootloader) meid:
(bootloader) date: 05-17-2018
(bootloader) sku: XT1789-06
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3922
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:8.0.0/OPXS27.10
(bootloader) ro.build.fingerprint[1]: 9-34-21/21:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.481.21.nash.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998_20207.117.02.41-01.02R NED
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g3c2ab17 (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 Nov 2 11:29:48 CDT 2018
(bootloader) git:abl: MBM-3.0-nash_retail-43c7c77-190705
(bootloader) git:xbl: MBM-3.0-nash_retail-4fc2afc-190705
(bootloader) git:pmic: MBM-3.0-nash_retail-4fc2afc-190705
(bootloader) git:rpm: MBM-3.0-nash_retail-404f7ba-190705
(bootloader) git:tz: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:hyp: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:devcfg: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:cmnlib: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:keymaster: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:storsec: MBM-3.0-nash_retail-3537781-190705
(bootloader) git:prov: MBM-3.0-nash_retail-3537781-190705
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 4
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.147s
It seems at some point some command was successful in switching the slots. Strange... I am really fishing in the dark here.
Still the Phone says: Device corrupted, and to unlock the bootloader, and when I try t unlock the bootloader in fastboot, it still tells me to check "OEM Unlocking" in the developer options.
You won't be able to unlock the bootloader until you're able to boot, sign in, and enable oem unlocking in dev options. Since it changed a few things around, try running the lmsa tool again.
NOthing new here. Ran LMSA again, it says "flash successful", but on reboot: "Device corrupt, wont boot, unlock bootloader". Then I tried "fastboot -w", but it showed the same results again as above. Then again LMSA, same behaviour again.
I think Ill just try to sell this thing again.
What kind of stupid error message is this? I shall unlock the bootloader because its bricked, but I have to boot it into OEM to unlock the bootloader?
wolzotan said:
NOthing new here. Ran LMSA again, it says "flash successful", but on reboot: "Device corrupt, wont boot, unlock bootloader". Then I tried "fastboot -w", but it showed the same results again as above. Then again LMSA, same behaviour again.
I think Ill just try to sell this thing again.
What kind of stupid error message is this? I shall unlock the bootloader because its bricked, but I have to boot it into OEM to unlock the bootloader?
Click to expand...
Click to collapse
Make sure you're running lmsa and such as an admin, some users depending on their pc have had to pay attention to this, while most don't.
Yeah I did that.
Hi all. I'm a complete newb to this, so please excuse any incorrect terminology. I appreciate any help given!
Here's the situation in brief:
This Moto E (XT2052-1) is completely unmodded. Nothing rooted, nothing unlocked, nothing flashed before. About 1.5 years in use.
It goes through a bootloop, and then "falls through to fastboot."
It reports "No bootable A/B slot" and fastboot getvar current slot yields "not found". I can't get it to switch to either slot.
can't find current slot
Code:
C:\platform-tools>fastboot getvar current slot
(bootloader) current: not found
getvar:current FAILED (remote: '')
fastboot: usage: unknown command slot
can't assign a slot
Code:
C:\platform-tools>fastboot set_active a
Setting current slot to 'a' (bootloader) Command is not allowed
FAILED (remote: '')
fastboot: error: Command failed
I think flashing stock ROM (specifically the boot image?) will fix the issue, but I'm running into problems
doesn't let me flash boot image, needs vbmeta image
Code:
C:\platform-tools>fastboot flash boot_a boot.img
Sending 'boot_a' (32768 KB) OKAY [ 0.764s]
Writing 'boot_a' (bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing boot image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
trying boot with boot image without flashing
Code:
C:\platform-tools>fastboot boot boot.img
Sending 'boot.img' (32768 KB) OKAY [ 0.765s]
Booting (bootloader) permission denied!
FAILED (remote: '')
fastboot: error: Command failed
And then flashing the boot image again after flashing the vbmeta image (... successfully? not sure)
Code:
C:\platform-tools>fastboot flash boot_a boot.img
Sending 'boot_a' (32768 KB) OKAY [ 0.768s]
Writing 'boot_a' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
I'm not sure if I'm missing a step, or if I need to change toggle a setting somewhere, or what.
I don't want to wipe it, but I understand it might prove to be necessary.
Here are the nitty gritty details:
It started bootlooping and then "falling back to fastboot" about 3 days ago. I don't think there was any damage or instigating event. It says to connect to a computer to fix it with "Software Repair Assistant" (which doesn't seem to exist). Here's the "Bootloader logs" text after turning it on and attempting to start it:
Start Up Failed:Your device didn't start up successfully.Use the Software Repair Assistant on computer to repair your device.Connect your device to your computer to get the Software Repair Assistant.you can try to press powerkey in failure interface to fix it [sic]If you try to fix it, Please try it at least 6 times [sic]
AP Fastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux,falling back to fastboot
Fastboot Reason: Fall-through from normal bootmode
No bootable A/B slot
Failed to boot Linux,falling back to fast bootmoode
Boot up failed
Click to expand...
Click to collapse
Many guides say to use LMSA to detect and fix, but I've also seen people warning of it flashing incorrectly, so I'm wary of it.
The problem seems to be with the A/B slot, so I've done research to understand what that means. I found this guide from droidwin.com useful, and have managed to do the following:
Downloaded and unzipped SDK platform tools.
I'm barely familiar with command line, but fastboot has been fine.
Tried fastboot set_active a, as well as b and other
Found appropriate (I think) stock ROM from here. It has the boot image, as well as many other files. I'm not familiar with how ROM is packaged.
Tried to flash the boot image from the stock ROM. It said I needed to flash the vbmeta image first.
Flashed the vbmeta image, onto both vbmeta_a and vbmeta_b (after much trial and error)
This took a while because I actually got ahold of and downloaded... let's say several stock ROM packages. Cycled through until I found one that was actually accepted.
Tried flashing the boot, but now Preflash validation failed
Here are all the relevent outputs from the command line
Code:
C:\platform-tools>fastboot devices
[...omitted...] fastboot
C:\platform-tools>fastboot getvar all
[...Let me know if I omitted something important...]
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ginna_retail-b0c61b8e633-220530
(bootloader) product: ginna
(bootloader) board: ginna
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: [...omitted...]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 101ECD4600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: [...omitted...]
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 11-10-2020
(bootloader) sku: XT2052-1
(bootloader) carrier_sku: XT2052-1
(bootloader) battid: SB18C66367
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Apr 6 2:44:35 UTC 2021" [idk why it says that time]
(bootloader) ro.build.fingerprint[0]: motorola/ginna_retail/ginna:10/QPG
(bootloader) ro.build.fingerprint[1]: S30.82-141-15-2/e9f0a:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.2.r1-06600-89xx.0
(bootloader) version-baseband: M632_19.00.03.50.04R GINNA_GWLC_CUST
(bootloader) kernel.version[0]: Linux version 4.9.206-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (gcc version 4.9.x 20150123 (
(bootloader) kernel.version[2]: prerelease) (GCC) ) #1 SMP PREEMPT Fri A
(bootloader) kernel.version[3]: pr 1 01:56:14 CDT 2022
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-ginna_retail-b0c61b8e633-220530
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retus
(bootloader) current-slot:
(bootloader) running-boot-lun: 0
(bootloader) running-slot:
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: No
(bootloader) slot-bootable:_b: No
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
(bootloader) pcb-part-no: SB28C75450
(bootloader) is-userspace: no
(bootloader) is-logical:
all: listed above
Finished. Total time: 0.233s
C:\platform-tools>fastboot set_active a
Setting current slot to 'a' (bootloader) Command is not allowed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot set_active other
Setting current slot to 'a' (bootloader) Command is not allowed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot set_active b
Setting current slot to 'b' (bootloader) Command is not allowed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot getvar current slot
(bootloader) current: not found
getvar:current FAILED (remote: '')
fastboot: usage: unknown command slot
C:\platform-tools>fastboot getvar product
product: ginna
Finished. Total time: 0.003s
C:\platform-tools>fastboot flash boot_a boot.img
Sending 'boot_a' (32768 KB) OKAY [ 0.764s]
Writing 'boot_a' (bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing boot image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot: error: Failed to identify current slot
C:\platform-tools>fastboot getvar has-slot:vbmeta
has-slot:vbmeta: yes
Finished. Total time: 0.005s
C:\platform-tools>fastboot flash vbmeta vbmeta.img
fastboot: error: Failed to identify current slot
C:\platform-tools>fastboot boot boot.img
Sending 'boot.img' (32768 KB) OKAY [ 0.765s]
Booting (bootloader) permission denied!
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot boot_a boot.img
fastboot: usage: unknown command boot_a
C:\platform-tools>fastboot boot_b boot.img
fastboot: usage: unknown command boot_b
C:\platform-tools>fastboot flashing unlock
(bootloader) This command requires you to first unlock the bootloader.
(bootloader) A unlock code may be required.
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot getvar iswarrantyvoid
iswarrantyvoid: no
Finished. Total time: 0.004s
[--WITH WRONG ROM--]
C:\platform-tools>fastboot flash vbmeta_a vbmeta.img
Sending 'vbmeta_a' (4 KB) OKAY [ 0.011s]
Writing 'vbmeta_a' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
[--WITH CORRECT ROM--]
C:\platform-tools>fastboot flash vbmeta_a vbmeta.img
Sending 'vbmeta_a' (4 KB) OKAY [ 0.011s]
Writing 'vbmeta_a' OKAY [ 0.006s]
Finished. Total time: 0.064s
C:\platform-tools>fastboot flash boot_a boot.img
Sending 'boot_a' (32768 KB) OKAY [ 0.768s]
Writing 'boot_a' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash boot_b boot.img
Sending 'boot_b' (32768 KB) OKAY [ 0.759s]
Writing 'boot_b' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash vbmeta_a --disable-verity --disable-verification vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (4 KB) OKAY [ 0.010s]
Writing 'vbmeta_a' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash vbmeta_b --disable-verity --disable-verification vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_b' (4 KB) OKAY [ 0.010s]
Writing 'vbmeta_b' (bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash vbmeta_b vbmeta.img
Sending 'vbmeta_b' (4 KB) OKAY [ 0.010s]
Writing 'vbmeta_b' OKAY [ 0.006s]
Finished. Total time: 0.063s
C:\platform-tools>fastboot BE NORMAL PLEASE
fastboot: usage: unknown command BE
That's about what I've got so far. At one point I did fastboot reboot fastboot and got into fastbootd, but I had no idea what I was doing there and promptly left.
I'm almost ready to give in and try factory resetting it, but I feel like I'm just missing a piece of the puzzle. Maybe several. I don't know. I have so many tabs open.
Again, any help you can give is welcome! Please keep in mind, I only started learning about any of this yesterday (brand new words in my repertoire: image, flash, bootloader, fastboot, slot, stock, ROM, RETUS, NFC, and much, much more!). I may not be the most articulate, but I'm certainly trying :^)
[Edit: and let me know about any formatting faux pas I may have committed! With text color or code blocks or whatever it may be. I messed with the options probably a little more than I should have, heh]
Alright, I've done some more reading and tried a couple other things.
This post with a similar problem suggested that it was a faulty partition, and to run:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot oem fb_mode_clear
This is what I got
Code:
C:\platform-tools>fastboot oem fb_mode_set
OKAY [ 0.002s]
Finished. Total time: 0.004s
C:\platform-tools>fastboot flash partition gpt.bin
Sending 'partition' (45 KB) OKAY [ 0.009s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.121s]
Finished. Total time: 0.252s
C:\platform-tools>fastboot oem fb_mode_clear
OKAY [ 0.002s]
Finished. Total time: 0.005s
C:\platform-tools>fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.008s
But it just did its normal bootloop after rebooting. [Oh wait, that's different... oh never mind. Just now, as I was writing, it stayed on one of the flashing screens for a significant amount of time, but then continued looping again]
WAIT OKAY, something happened! After the reboot from flashing gpt.bin, I tried flashing the boot image again.
Code:
[...directly after the previous commands...]
C:\platform-tools>fastboot flash boot_a boot.img
Sending 'boot_a' (32768 KB) OKAY [ 0.764s]
Writing 'boot_a' (bootloader) *****************************************************
(bootloader) WARNING: Flashing vbmeta image is required prior to
(bootloader) flashing boot image.
(bootloader) *****************************************************
(bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash vbmeta_a vbmeta.img
Sending 'vbmeta_a' (4 KB) OKAY [ 0.012s]
Writing 'vbmeta_a' OKAY [ 0.007s]
Finished. Total time: 0.054s
C:\platform-tools>fastboot flash boot_a boot.img
Sending 'boot_a' (32768 KB) OKAY [ 0.763s]
Writing 'boot_a' OKAY [ 0.908s]
Finished. Total time: 1.734s
It accepted the boot image! No more "Preflash validation failed"!
I immediately fastboot getvar all, and I really should have done so after flashing gpt.bin, but oh well. There are some changes!
Code:
C:\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ginna_retail-b0c61b8e633-220530
(bootloader) product: ginna
(bootloader) board: ginna
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QD63MB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: SDM632
(bootloader) serialno: [...omitted...]
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 101ECD4600000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: [...omitted...]
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 11-10-2020
(bootloader) sku: XT2052-1
(bootloader) carrier_sku: XT2052-1
(bootloader) battid: SB18C66367
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Apr 5 23:52: 0 UTC 2021"
(bootloader) ro.build.fingerprint[0]: motorola/ginna_retail/ginna:10/QPG
(bootloader) ro.build.fingerprint[1]: S30.82-141-15-2/e9f0a:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.2.r1-06600-89xx.0
(bootloader) version-baseband: M632_19.00.03.50.04R GINNA_GWLC_CUST
(bootloader) kernel.version[0]: Linux version 4.9.206-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (gcc version 4.9.x 20150123 (
(bootloader) kernel.version[2]: prerelease) (GCC) ) #1 SMP PREEMPT Fri A
(bootloader) kernel.version[3]: pr 1 01:56:14 CDT 2022
(bootloader) sbl1.git: MBM-2.1-ginna_retail-054f0bdd8c-220530
(bootloader) rpm.git: MBM-2.1-ginna_retail-20f2cf34-220530
(bootloader) tz.git: MBM-2.1-ginna_retail-7b2dc18f40-220530
(bootloader) devcfg.git: MBM-2.1-ginna_retail-7b2dc18f40-220530
(bootloader) keymaster.git: MBM-2.1-ginna_retail-7b2dc18f40-220530
(bootloader) cmnlib.git: MBM-2.1-ginna_retail-7b2dc18f40-220530
(bootloader) cmnlib64.git: MBM-2.1-ginna_retail-7b2dc18f40-220530
(bootloader) prov.git: MBM-2.1-ginna_retail-7b2dc18f40-220530
(bootloader) aboot.git: MBM-2.1-ginna_retail-b0c61b8e633-220530
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retus
(bootloader) current-slot: b
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _b
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: No
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 7
(bootloader) pcb-part-no: SB28C75450
(bootloader) is-userspace: no
(bootloader) is-logical:
all: listed above
Finished. Total time: 0.753s
First I noticed that the slots information had changed. There is now an active slot, and slot b now reads "bootable" (which is odd, because I flashed boot_a ), and a retry count that isn't 0! Then I noticed a bunch of the git variables also changed, to MBM-2.1-ginna_retail-[yaddayadda-yadda]
I have no idea what this means, but I call it progress!
________________________________________________________________It still bootloops, but I'll keep poking at it.
A change I've notices, however, from even before I flashed gpt.bin, is an inconsistency of how it bootloops.
It either:
immediately falls through from normal bootmode
bootloops for a while and then goes into fastboot
bootloops and turns off
And I haven't really found a pattern why. I've taken to manually starting fastboot (with volume down) when before it would go there by itself. Who knows.
I'm sorry that I cant help with your situation but could you help me to understand these recovery options? My pc wont recognize the phone when connected in fastboot mode but the phone recognizes the pc....
what am I doing wrong? and are there any settings I'm supposed to have activated to facilitate the data transfer?
Here's my Forum post
Phone is completely stock btw
Heruktiang said:
I'm sorry that I cant help with your situation but could you help me to understand these recovery options? My pc wont recognize the phone when connected in fastboot mode but the phone recognizes the pc....
what am I doing wrong? and are there any settings I'm supposed to have activated to facilitate the data transfer?
Here's my Forum post
Phone is completely stock btw
Click to expand...
Click to collapse
Hi! Due to time constraints, I ended up fully flashing the stock ROM (thereby erasing userdata). I plan on updating this thread tonight with what I did, even though it just eventually led to erasing everything.
Hmm, as to your situation... I have to admit I am not familiar with all this (this was first time touching a bootloader, haha), but I took a quick look through your post. I can note a couple differences between our situations:
My recovery mode was inaccessible, as far as I could tell. If I tried to select it in the bootloader, I think it would give the same "No bootable A/B slot" error.
I never used the LMSA on the phone, but I did have it open when the phone was plugged in to the computer, and the bootloader logs indicated that some sort of communication was happening. I didn't record exactly what the commands were, but I think there were three, among them "getvar product" or some such.
Other than that, I have no insight on this. In my research, I found no way to get the userdata off a bootlooping phone that didn't have TWRP or some things (bootloader?) unlocked. Sorry I can't help much
I was wondering if the bootloop was prompted by a recent update, but there doesn't seem to be too many people affected
Thanks for the swift and detailed reply. I'm starting to think I was hacked. My gf admitted to hacking me before. Ill keep trying to get the pc to communicate with the phone.
GewdGrief said:
I plan on updating this thread tonight with what I did, even though it just eventually led to erasing everything.
Click to expand...
Click to collapse
Had you tried flashing with servicefile.xml from the your firmware archive? It flashes everything, but leaves userdata intact, so I think it would have been your best bet.