I restored my boot.img from within Magisk because I need to OTA update. Now the phone will only boot into the bootloader with the message
AP Fastboot Flash Mode(Secure)
No Bootable A/B Slot
Failed to Boot Linux, falling back to fastboot
Nothing will work through fastboot. I've tried switching slots, re-flashing the boot.img, and re-flashing the ROM, but the flashing won't even start. Every command I try to run brings up a code on the phone that says "cmd: getvar:slot-count." My phone can be found by the fastboot devices command.Has anyone encountered and fixed this before?
doodalydoo said:
I restored my boot.img from within Magisk because I need to OTA update. Now the phone will only boot into the bootloader with the message
AP Fastboot Flash Mode(Secure)
No Bootable A/B Slot
Failed to Boot Linux, falling back to fastboot
Nothing will work through fastboot. I've tried switching slots, re-flashing the boot.img, and re-flashing the ROM, but the flashing won't even start. Every command I try to run brings up a code on the phone that says "cmd: getvar:slot-count." My phone can be found by the fastboot devices command.Has anyone encountered and fixed this before?
Click to expand...
Click to collapse
Just re-flash the system back manually from fastboot. You can find instructions all over the place.
johnjingle said:
Just re-flash the system back manually from fastboot. You can find instructions all over the place.
Click to expand...
Click to collapse
It won't work. When I input the fastboot command into cmd, it doesn't proceed and then I get a code on my phone that says "cmd: getvar:slot-count." No fastboot commands will work, even though my phone is detected as a fastboot device. I don't get it.
doodalydoo said:
It won't work. When I input the fastboot command into cmd, it doesn't proceed and then I get a code on my phone that says "cmd: getvar:slot-count." No fastboot commands will work, even though my phone is detected as a fastboot device. I don't get it.
Click to expand...
Click to collapse
That doesn't sound fun.
Have you tried:
fastboot getvar all
or
fastboot boot ****.img (TWRP image.)
just to see if fastboot can output the details about your phone?
johnjingle said:
That doesn't sound fun.
Have you tried:
fastboot getvar all
or
fastboot boot ****.img (TWRP image.)
just to see if fastboot can output the details about your phone?
Click to expand...
Click to collapse
I turned "Tools mode" on and now I actually get the progress of the fastboot command.
C:\adb>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-suffi: not found
(bootloader) slot-suffixes: not found
(bootloader) max-download-sizestem: not found
target didn't report max-download-size
sending 'system' (524284 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.016s
C:\adb>fastboot flash system system.img_sparsechunk.1
(bootloader) slot-suffi: not found
(bootloader) max-download-: not found
target didn't report max-download-size
sending 'system' (524284 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.016s
C:\adb>fastboot flash system system.img_sparsechunk.2
(bootloader) slot-countad-: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) partition-: not found
target didn't report max-download-size
sending 'system' (524284 KB)...
It freezes after this.
C:\adb>fastboot getvar all
(bootloader) allt-count: not found
getvar:all FAILED (remote failure)
finished. total time: 0.000s
C:\adb>fastboot boot twrp-3.2.3-1-payton.img
downloading 'boot.img'...
OKAY [ 0.642s]
booting...
(bootloader) Failed to load/authenticate boot image: Not Found
FAILED (remote failure)
finished. total time: 0.658s
This is what it says when I try to run the commands you suggested.
Edit: My bootloader was unlocked before this happening, I just want to make sure it didn't relock and that's the problem. When it says "flashing_unlock" in recovery mode, that means the bootloader is unlocked right?
Ok a weird thing happened. Somehow the phone went from a soft brick to a hard brick. It didn't hard brick during the whole time I was trying to fix it. The last thing I did was put it on the charger and when I took it off the charger, it was hard bricked. This actually turned out to be exactly what I needed because it put the phone in the position where I could use the blankflash file. My phone is now working!
Ok it's back to not working again! I managed to get the phone booted, but it kept crashing so I booted into TWRP to wipe the system so I could do a clean install. Now none of the fastboot commands are working again. The recovery mode looks like it supposed to now unlike last time. I'm also able to sometimes run "fastboot getvar all" now, but it doesn't work all the time. I have no clue what is going on.
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-0e6e7ce-190305
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB MICRON S0J97Y RV=08 PV=10 FV=4E5630304D483333
(bootloader) ufs: N/A
(bootloader) ram: 3GB MICRON LP4 DIE=12Gb M5=FF M6=02 M7=10 M8=0C
(bootloader) cpu: SDM630 1.0 (2)
(bootloader) serialno: ZY2253DPJK
I've managed to get the phone to boot up again, but the fastboot commands have also stopped working again. I don't know what to do at this point and I'm also afraid the next thing I do will just break the phone again.. If the phone is booting up properly, why aren't the fastboot commands working?
doodalydoo said:
Ok it's back to not working again! I managed to get the phone booted, but it kept crashing so I booted into TWRP to wipe the system so I could do a clean install. Now none of the fastboot commands are working again. The recovery mode looks like it supposed to now unlike last time. I'm also able to sometimes run "fastboot getvar all" now, but it doesn't work all the time. I have no clue what is going on.
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-0e6e7ce-190305
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB MICRON S0J97Y RV=08 PV=10 FV=4E5630304D483333
(bootloader) ufs: N/A
(bootloader) ram: 3GB MICRON LP4 DIE=12Gb M5=FF M6=02 M7=10 M8=0C
(bootloader) cpu: SDM630 1.0 (2)
(bootloader) serialno: ZY2253DPJK
I've managed to get the phone to boot up again, but the fastboot commands have also stopped working again. I don't know what to do at this point and I'm also afraid the next thing I do will just break the phone again.. If the phone is booting up properly, why aren't the fastboot commands working?
Click to expand...
Click to collapse
Try downloading mfastboot, don't use a script, manually install each file and see what happens after each flash, etc.
For example:
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot reboot-bootloader
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash bluetooth BTFM.bin
mfastboot flash dsp dspso.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system_b system_other.img
mfastboot flash oem oem.img
mfastboot erase carrier
mfastboot erase userdata
mfastboot erase ddr
---------- Post added at 06:34 PM ---------- Previous post was at 06:27 PM ----------
doodalydoo said:
Ok it's back to not working again! I managed to get the phone booted, but it kept crashing so I booted into TWRP to wipe the system so I could do a clean install. Now none of the fastboot commands are working again. The recovery mode looks like it supposed to now unlike last time. I'm also able to sometimes run "fastboot getvar all" now, but it doesn't work all the time. I have no clue what is going on.
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-0e6e7ce-190305
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB MICRON S0J97Y RV=08 PV=10 FV=4E5630304D483333
(bootloader) ufs: N/A
(bootloader) ram: 3GB MICRON LP4 DIE=12Gb M5=FF M6=02 M7=10 M8=0C
(bootloader) cpu: SDM630 1.0 (2)
(bootloader) serialno: ZY2253DPJK
I've managed to get the phone to boot up again, but the fastboot commands have also stopped working again. I don't know what to do at this point and I'm also afraid the next thing I do will just break the phone again.. If the phone is booting up properly, why aren't the fastboot commands working?
Click to expand...
Click to collapse
Also, did you have anything like this at the bottom of that fastboot command?
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(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
johnjingle said:
Try downloading mfastboot, don't use a script, manually install each file and see what happens after each flash, etc.
For example:
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot reboot-bootloader
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash bluetooth BTFM.bin
mfastboot flash dsp dspso.bin
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash system_b system_other.img
mfastboot flash oem oem.img
mfastboot erase carrier
mfastboot erase userdata
mfastboot erase ddr
---------- Post added at 06:34 PM ---------- Previous post was at 06:27 PM ----------
Also, did you have anything like this at the bottom of that fastboot command?
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(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
Click to expand...
Click to collapse
The phone is working again and I think for good this time. Getting the fastboot commands to work was just a matter of luck I guess. I had no method, I was just randomly unplugging, plugging in, holding different keys, and powering on and off until I was lucky enough to get it to work. Once the fastboot started working, I just wiped the phone completely and clean flashed the newest ROM. I haven't had any problems since then. I think what caused all of this was I was dirty flashing improperly. I tried picking out the commands I thought were necessary from the ROM flashing commands, but wouldn't erase my data. I must have left out critical flash commands. Just so I'm sure and I don't have to go through this again, will running the ROM flash commands you posted except "mfastboot erase userdata" work to properly flash the ROM while leaving my data intact?
doodalydoo said:
The phone is working again and I think for good this time. Getting the fastboot commands to work was just a matter of luck I guess. I had no method, I was just randomly unplugging, plugging in, holding different keys, and powering on and off until I was lucky enough to get it to work. Once the fastboot started working, I just wiped the phone completely and clean flashed the newest ROM. I haven't had any problems since then. I think what caused all of this was I was dirty flashing improperly. I tried picking out the commands I thought were necessary from the ROM flashing commands, but wouldn't erase my data. I must have left out critical flash commands. Just so I'm sure and I don't have to go through this again, will running the ROM flash commands you posted except "mfastboot erase userdata" work to properly flash the ROM while leaving my data intact?
Click to expand...
Click to collapse
The only line I "usually" usually leave out is the erase "mfastboot user data", unless I am coming from a ROM or want a completely fresh start.
Related
I got this used HTC one. I had google edition ROM on it when I got it. Then I flashed AR HD Rom on it. Everything was going fine till I decided to flash the latest firmware since I wanted to go to ARHD 30 and everyone seems to recommend to flash the new firmware.
I was going thru the normal steps and saw that I need to relock my device. I did this:
C:\Program Files\Android\sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.110s
After this I noticed that I had relocked written in fastboot mode even though it said failed. So tried the next step:
C:\Program Files\Android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.036s]
finished. total time: 0.040s
C:\Program Files\Android\sdk\platform-tools>fastboot flash zip firmware.zip
sending 'zip' (28338 KB)...
OKAY [ 2.566s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 5.843s
And any step that I try it fails. The most unfortunate thing is I can only boot in fastboot & bootloader mode. I can't go in recovery neither can I boot normally. These are my phone details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4137mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.057s
I looked up online tried flashing recovery but now any step that I try to do in fastboot fails with following message:
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
I saw in some places people mentioned to use RUU. Not sure what it is but if some one can point me to a correct RUU or let me know any other steps it would be greatly appreciated. My phone is almost bricked now since i can't go past fastboot/bootloader.
awaitforitb said:
(bootloader) version-bootloader: 1.44.0000
Click to expand...
Click to collapse
You have no idea how lucky you are. Before you do anything, get S-OFF using revone. Just go into CWM (or re-flash recovery) so you can use adb. Once you have s-off, follow my guide :
This guide requires S-OFFImportant
*** If there are files you need to keep, you can always use adb pull to get them out before hand (let's say a nandroid backup or something important)
This guide assumes you have knowledge about how adb and fastboot command work and that your HTC drivers are up to date.
I am in NO WAY responsible for any possible damage that may happen to your phone, I am only trying to help
Start your phone in bootloader by typing
Code:
adb reboot bootloader
or by other means.
Select "Fastboot" so that it appears in red instead of HBOOT
On your computer, make sure fastboot sees your device, then type
Code:
fastboot erase cache
Type
Code:
fastboot erase cache
Type
Code:
fastboot erase userdata
Type
Code:
fastboot erase system
Type
Code:
fastboot erase linux
Type
Code:
fastboot erase recovery
Type
Code:
fastboot erase cache
Type
Code:
fastboot reboot-bootloader
Download the new firmware.zip
Type
Code:
fastboot oem rebootRUU
Once it's rebooted on a silver HTC logo, type :
Code:
fastboot flash zip [pathonyourcomputer/firmware.zip]
Wait until it is done on your computer. The green line on the phone will never reach the end.
Type
Code:
fastboot reboot-bootloader
Reflash your recovery (I recommend CWM). Might as well play it safe.
Code:
fastboot flash recovery [pathonyourcomputer/recovery.img]
Reboot into recovery (select the option in fastboot)
Wipe data/factory reset (you will loose everythng)
Select "Wipe Cache partition"
Select "Advanced -> Wipe Dalvik Cache"
Now you have 2 options :
Push (Preferred)
While in recovery, type
Code:
adb push [path/rom.zip] /sdcard/rom.zip
Select "Install zip"
Select "Choose zip from sdcard"
Voila ! You should be good to go !
Sideload (If you can't push for some reason)
Select "Install zip"
Select "Install zip from sideload"
Type
Code:
adb sideload [path/rom.zip]
Voila ! You should be good to go !
attanasi0 said:
You have no idea how lucky you are. Before you do anything, get S-OFF using revone. Just go into CWM (or re-flash recovery) so you can use adb. Once you have s-off, follow my guide :
Click to expand...
Click to collapse
@awaitforitb:
I agree with the S-Off part, just check the date of your bootloader it has to be pre June 2013. Also, in order for revone to work you need a functioning ROM (4.1.2... 4.3 will NOT work). Do you have one functioning device, or are you "stuck in bootloader" as the title says.
You could run the RUU found on androidruu http://www.androidruu.com/?developer=M7, I believe yours would be http://www.androidruu.com/getdownlo....20_10.40.1150.04_release_326691_signed_2.exe
That's an exe you run directly from your PC, and it will walk you through the steps, this will wipe your phone completely! and restore everything back to 100% stock.
After that you should get S-Off, and then proceed to whatever your end goal is.
@attanasi0 just a couple of questions, why do you recommend all the "fastboot erase userdata/linux/system/recovery" ?
Also, please remember that when using "fastboot flash zip <name of firmware>.zip", in most cases, you have to do it twice after each other, the first will push the zip and say "failed, flush image again" (or something along those lines), the second flash will actually start the installation and should report success.
I usually use firmwares from @vomer's guide: http://forum.xda-developers.com/showthread.php?t=2365506 as they have the dzdata files removed, as well as the stock boot.img and recovery.img removed.
nkk71 said:
@attanasi0 just a couple of questions, why do you recommend all the "fastboot erase userdata/linux/system/recovery" ?
Also, please remember that when using "fastboot flash zip <name of firmware>.zip", in most cases, you have to do it twice after each other, the first will push the zip and say "failed, flush image again" (or something along those lines), the second flash will actually start the installation and should report success.
I usually use firmwares from @vomer's guide: http://forum.xda-developers.com/showthread.php?t=2365506 as they have the dzdata files removed, as well as the stock boot.img and recovery.img removed.
Click to expand...
Click to collapse
You're about pushing the zip at first, forgot about that.
I honestly don't know why I recommend that. I guess it's to make sure the phone is a clean slate and no conflict will be created TL;DR : Paranoia
Hi
I flashed my HTC One M7 firmware to OS-7.19.401.2 (Unfrotunately wasn't in S-Off when I did it).
This is what it looks lke at the moment:
*** RELOCKED ***
M7-UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
OS-7.19.401.2 (7.19.401.2)
I did it after I tried to update to Lollipop from Android 4.4.3 which crashed on me. Being impatient I terminated the update after taking so long.
I tried relashing but am not having any luck getting it to return to normal(when I do reflash it the second time with the same command it stalls at the silver htc logo screen), I do have the unlock.bin file but it's not working and I can't access the SDcard on the phone either.
Thanks for any help!
klaymeb said:
Hi
I flashed my HTC One M7 firmware to OS-7.19.401.2 (Unfrotunately wasn't in S-Off when I did it).
This is what it looks lke at the moment:
*** RELOCKED ***
M7-UL PVT SHIP S-ON RH
HBOOT-1.61.0000
RADIO-4T.35.3218.16
OpenDSP-v35.120.274.0718
OS-7.19.401.2 (7.19.401.2)
I did it after I tried to update to Lollipop from Android 4.4.3 which crashed on me. Being impatient I terminated the update after taking so long.
I tried relashing but am not having any luck getting it to return to normal(when I do reflash it the second time with the same command it stalls at the silver htc logo screen), I do have the unlock.bin file but it's not working and I can't access the SDcard on the phone either.
Thanks for any help!
Click to expand...
Click to collapse
seems your using a custom firmware, try this one >> https://www.androidfilehost.com/?fid=95916177934533542
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
So I changed the zip folder name to firmware, And reflashed it again as per above instructions, And it worked...
The only thing is I keep ending back at the same point again, of the phone not going back into Anfroid (I haven't put a Sim card back in yet)...
What else do I need to do to get it back into Android? Stuck in Bootloader....
klaymeb said:
So I changed the zip folder name to firmware, And reflashed it again as per above instructions, And it worked...
The only thing is I keep ending back at the same point again, of the phone not going back into Anfroid (I haven't put a Sim card back in yet)...
What else do I need to do to get it back into Android? Stuck in Bootloader....
Click to expand...
Click to collapse
This is my fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3688mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
klaymeb said:
This is my fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3688mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
!!!!read all steps first!!!!
1. unlock your bootloader
2. flash custom recovery TWRP 2.8.5.0 ("fastboot flash recovery twrp.img" then "fastboot erase cache" finally "fastboot reboot-bootloader")
3. download this rom https://basketbuild.com/dl/devs?dl=Artur0588/M7_7.19.401.2.zip and put it on the fastboot/adb folder
4. extract firmware.zip (thread #2) and copy boot.img in the fastboot folder
5. extract from the firmware.zip (that you've downloaded in thread #2) recovery.img and paste in the fastboot/adb folder
6. "adb devices" to verify that your device is connected, then "adb push rom.zip /sdcard/" it will take about 5 min.
7. now "fastboot flash boot boot.img" then "fastboot reboot-bootloader"
8. enter to recovery mode and make full wipe (data/dalvick/chache)
9. choose install >> select rom.zip and swipe.
10. when installation finish up flash the stock recovery "fastboot flash recovery recovery.img" , "fastboot erase cache" , "fastboot oem lock" and "fastboot erase cache"
Thanks for that...:good:
When I have tried to flash it again after the first firmware install it stalls...
I'm finding it difficult to unlock the bootloader, It's still in Relocked mode and S-On and just boot loops back to the bootloader.
I just have basic flashing knowledge.
I'm using Win 8.1 64bit, the ports I'm connecting with are USB 3 and using Minimal ADB and Fastboot for flashing the phone.
klaymeb said:
Thanks for that...:good:
When I have tried to flash it again after the first firmware install it stalls...
I'm finding it difficult to unlock the bootloader, It's still in Relocked mode and S-On and just boot loops back to the bootloader.
I just have basic flashing knowledge.
I'm using Win 8.1 64bit, the ports I'm connecting with are USB 3 and using Minimal ADB and Fastboot for flashing the phone.
Click to expand...
Click to collapse
Write the unlock command that you are using here, and the error message too.
klaymeb said:
Thanks for that...:good:
When I have tried to flash it again after the first firmware install it stalls...
I'm finding it difficult to unlock the bootloader, It's still in Relocked mode and S-On and just boot loops back to the bootloader.
I just have basic flashing knowledge.
I'm using Win 8.1 64bit, the ports I'm connecting with are USB 3 and using Minimal ADB and Fastboot for flashing the phone.
Click to expand...
Click to collapse
Are you using the correct drivers for Windows 8.1?
In your device manager is your phone detected?
When your phone is in bootloader is it detected by fastboot? Type fastboot devices into your command prompt and it should list the serial no of your device.
Also, use USB 2.0 rather than 3.0
VoynichJimmy said:
Write the unlock command that you are using here, and the error message too.
Click to expand...
Click to collapse
fastboot flash unlocktoken Unlock_code.bin (as per HTCdev instructions)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1492578304 bytes
error: cannot load 'Unlock_code.bin': No error
klaymeb said:
fastboot flash unlocktoken Unlock_code.bin (as per HTCdev instructions)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1492578304 bytes
error: cannot load 'Unlock_code.bin': No error
Click to expand...
Click to collapse
The command looks like it's ok. The unlock code is definitely in your fastboot folder
When you go to device manager when your phone is connected at the bootloader screen is your phone detected there? Does the command fastboot devices show your serial no?
stovie_steve said:
Are you using the correct drivers for Windows 8.1?
Driver Version: 2.0.7.27
In your device manager is your phone detected?
Yes.
When your phone is in bootloader is it detected by fastboot? Type fastboot devices into your command prompt and it should list the serial no of your device.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
FA426W904521 fastboot
Also, use USB 2.0 rather than 3.0
Click to expand...
Click to collapse
Ok Thanks, I thought that might be the case with it.
stovie_steve said:
The command looks like it's ok. The unlock code is definitely in your fastboot folder
When you go to device manager when your phone is connected at the bootloader screen is your phone detected there?
Does the command fastboot devices show your serial no?
Click to expand...
Click to collapse
Only thing I can think of if your drivers are working, fastboot detects your phone and you are running the right command is to start it again and request a new unlock code
stovie_steve said:
Only thing I can think of if your drivers are working, fastboot detects your phone and you are running the right command is to start it again and request a new unlock code
Click to expand...
Click to collapse
I just tried that, but no luck...
This is what I'm getting at the moment:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1514139648 bytes
error: cannot load 'Unlock_code.bin': No error
I think the SDCard is not working.
klaymeb said:
I just tried that, but no luck...
This is what I'm getting at the moment:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1514139648 bytes
error: cannot load 'Unlock_code.bin': No error
I think the SDCard is not working.
Click to expand...
Click to collapse
The sdcard wouldn't have any effect on this working...
The unlock code should be in your adb folder on your PC
stovie_steve said:
The sdcard wouldn't have any effect on this working...
The unlock code should be in your adb folder on your PC
Click to expand...
Click to collapse
I have put it in a ADB_Windows folder which was created when I installed Minimal ADB and Fastboot software, so I'm not sure why it's not running at this stage.
Do I need to reinstall ADB and Fastboot on the PC again and create a new folder for it?
klaymeb said:
I have put it in a ADB_Windows folder which was created when I installed Minimal ADB and Fastboot software, so I'm not sure why it's not running at this stage.
Do I need to reinstall ADB and Fastboot on the PC again and create a new folder for it?
Click to expand...
Click to collapse
What is the folder directory where you have your adb and fastboot files?
stovie_steve said:
What is the folder directory where you have your adb and fastboot files?
Click to expand...
Click to collapse
Just figured out that I wast trying to use the Unlock file in the wrong place, This is what I've just done now:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unloc
k_code.bin
target reported max download size of 1514139648 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.143s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.151s
klaymeb said:
Just figured out that I wast trying to use the Unlock file in the wrong place, This is what I've just done now:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unloc
k_code.bin
target reported max download size of 1514139648 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.143s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.151s
Click to expand...
Click to collapse
And I just tried this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.033s]
finished. total time: 0.034s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (551346 KB)...
OKAY [ 20.471s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 72.998s
klaymeb said:
And I just tried this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.033s]
finished. total time: 0.034s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (551346 KB)...
OKAY [ 20.471s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 72.998s
Click to expand...
Click to collapse
As you are s-on, your bootloader needs to be locked to flash firmware, unlock it after the flash, but just to be sure, as you struggled to even unlock your bootloader, which firmware are you trying to flash, because if its the wrong one, you'll hard brick your phone.
if your looking to upgrade to Lollipop, just flash this, it will make you full stock Lollipop, it will also wipe your device, so make sure you backup anything you want to keep
https://www.androidfilehost.com/?fid=95916177934537475
just rename the file once its downloaded to RUU and put it in the same folder as adb, fastboot, your unlock code etc on your computer and then follow these instructions:
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip RUU.zip - fully automated so no need to do it twice
fastboot reboot-bootloader
fastboot reboot
after your first setup, you can do what you want, unlock your bootloader at this point, flash a custom recovery, root etc.
Seanie280672 said:
As you are s-on, your bootloader needs to be locked to flash firmware, unlock it after the flash, but just to be sure, as you struggled to even unlock your bootloader, which firmware are you trying to flash, because if its the wrong one, you'll hard brick your phone.
if your looking to upgrade to Lollipop, just flash this, it will make you full stock Lollipop, it will also wipe your device, so make sure you backup anything you want to keep
https://www.androidfilehost.com/?fid=95916177934537475
just rename the file once its downloaded to RUU and put it in the same folder as adb, fastboot, your unlock code etc on your computer and then follow these instructions:
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip RUU.zip - fully automated so no need to do it twice
fastboot reboot-bootloader
fastboot reboot
after your first setup, you can do what you want, unlock your bootloader at this point, flash a custom recovery, root etc.
Click to expand...
Click to collapse
So this is what I did, And I still end up back at the bootloader.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
< waiting for device >
...
(bootloader) Device was already locked!
OKAY [ 0.001s]
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.036s]
finished. total time: 0.037s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.032s]
finished. total time: 0.033s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip RUU.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1264453 KB)...
OKAY [ 41.892s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 122.212s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.034s]
finished. total time: 0.035s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.033s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Device is stuck in fastboot mode
screen shows
Device is LOCKED: Status code: 0
IMEI : 00000000000
SKU: 00000
Serial number shows values
Date being shown as 01-01-1970
Bootloader logs shows
fastboot reason: failed to initialize partition table
any advise on how to recover from this?
Fastboot erase userdata plus cache
Sent from my Nexus 6 using XDA-Developers mobile app
get error on erase
MacBook-Pro:~ user$ fastboot devices -l
994f3b10 fastboot usb:337641472X
MacBook-Pro:~ user$ fastboot erase cache
erasing 'cache'...
(bootloader) Invalid partition name cache
FAILED (remote failure)
finished. total time: 0.067s
MacBook-Pro:~ user$ fastboot erase userdata
erasing 'userdata'...
(bootloader) Invalid partition name userdata
FAILED (remote failure)
finished. total time: 0.066s
MacBook-Pro:~ user$
fastboot flash bootloader. Are you trying to flash N Preview?
reagan1998 said:
fastboot flash bootloader. Are you trying to flash N Preview?
Click to expand...
Click to collapse
my device was running fine with 5.1 and not sure what caused to get into this stuck where its stuck in fastboot boot
i am just trying to flash factory images from https://developers.google.com/android/nexus/images#shamu
Given the suddenness of your problem as well as the symptoms, I believe the internal memory has failed, meaning a service call. However, I hope I'm wrong.
Regardless, flashing factory images won't work because your bootloader is locked. Assuming this is a software issue you may be able to restore the system by sideloading the Android N OTA through recovery. If you can successfully do that, head to Developer Options in the N preview and enable OEM unlock. From there, unlock the bootloader, so you can flash factory images.
Strephon Alkhalikoi said:
Given the suddenness of your problem as well as the symptoms, I believe the internal memory has failed, meaning a service call. However, I hope I'm wrong.
Regardless, flashing factory images won't work because your bootloader is locked. Assuming this is a software issue you may be able to restore the system by sideloading the Android N OTA through recovery. If you can successfully do that, head to Developer Options in the N preview and enable OEM unlock. From there, unlock the bootloader, so you can flash factory images.
Click to expand...
Click to collapse
- I read some threads on sideload, they need device booted with adb access, since mine is stuck in fastboot, i don't have access to device via adb, would side load still work?
- still looking for zip for side load for nexus 6, if you have pointer for it, please let me know
To sideload the Android N OTA, which is the only thing that will help you here, you need to be able to get into recovery and set the recovery to adb sideload mode. If you cannot get into recovery, you definitely have a hardware problem and will need to get the internal storage chip replaced. As for the Android N OTA zip, check in the General subforum. Of course you could also simply do a quick Google search for "Android N OTA Brick" and get to Google's page of OTA zips that way.
Strephon Alkhalikoi said:
To sideload the Android N OTA, which is the only thing that will help you here, you need to be able to get into recovery and set the recovery to adb sideload mode. If you cannot get into recovery, you definitely have a hardware problem and will need to get the internal storage chip replaced. As for the Android N OTA zip, check in the General subforum. Of course you could also simply do a quick Google search for "Android N OTA Brick" and get to Google's page of OTA zips that way.
Click to expand...
Click to collapse
Android N has a new bootloader, so sideloading it will probably make the device not boot into Android.
---------- Post added at 08:24 PM ---------- Previous post was at 08:23 PM ----------
Have you tried flashing a TWRP recovery and maybe flashing a custom ROM to see if it is a storage issue? This phone is not even two years old, it should not be having internal storage issues.
The Android N OTA I'm talking about includes the bootloader, as it is a full system image. Flashing TWRP will not work as the device has a locked bootloader. But since the device apparently has no partitions at all, the exercise I believe is moot. This is a hardware issue.
Run 'fastboot format cache' and 'fastboot format userdata', then run the most holy words in android 'fastboot oem unlock'. Check this: http://forum.xda-developers.com/nexus-6/help/solution-stuck-bootloop-locked-t3053783 it really helped me out of a deep hole.
The only way that will work is if the OP enabled OEM Unlocking in Developer Options prior to the device forgetting its partitions. I hope he did, as having the option enabled doesn't affect the ability to get OTAs from Google. If however his device's EMMC chip failed as I believe, it won't help him resolve this issue.
reagan1998 said:
Run 'fastboot format cache' and 'fastboot format userdata', then run the most holy words in android 'fastboot oem unlock'. Check this: http://forum.xda-developers.com/nexus-6/help/solution-stuck-bootloop-locked-t3053783 it really helped me out of a deep hole.
Click to expand...
Click to collapse
apologies for delayed response, i didn't realize there was second page in replies and you guys are still trying to help
here is outout
sh-3.2# fastboot devices
994f3b10 fastboot
sh-3.2# fastboot format cache
Formatting is not supported for filesystem with type ''.
sh-3.2# fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.002s
sh-3.2# fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-apq8084-71.08(*)
(bootloader) product: shamu
(bootloader) board: shamu
(bootloader) secure: yes
(bootloader) hwrev: 0x83A0
(bootloader) radio: 0x6
(bootloader) emmc: 32GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 3072MB Elpida S8 SDRAM DIE=6Gb
(bootloader) cpu: APQ8084 ES1.1
(bootloader) serialno: 994f3b10
(bootloader) cid: 0xFFFF
(bootloader) channelid: 0xDEAD
(bootloader) uid: 7858B30111000000000000000000
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 8
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sdi.git: sdi.git
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) aboot.git: git=MBM-NG-V71.08-0-g32b8854
(bootloader) qe:
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.040s
sh-3.2#
If it's failing to initialize the partition table, there's nothing you can do here. It needs to go to Motorola for warranty service.
EDIT: How I can tell? The date was set to 1/1/70. That's the beginning date of the Unix clock, which means something got screwed up internally. That plus the lost IMEI and the failure of the device to find its partitions means a bad device.
Sorry to be the bearer of bad news here, but this isn't something software can fix.
Strephon Alkhalikoi said:
If it's failing to initialize the partition table, there's nothing you can do here. It needs to go to Motorola for warranty service.
EDIT: How I can tell? The date was set to 1/1/70. That's the beginning date of the Unix clock, which means something got screwed up internally. That plus the lost IMEI and the failure of the device to find its partitions means a bad device.
Sorry to be the bearer of bad news here, but this isn't something software can fix.
Click to expand...
Click to collapse
Thanks for looking in, warranty must be void since i had open the back cover .
EDIT: Bad advice given.
Strephon Alkhalikoi said:
I would try anyway. The worst that will happen is they will want to charge you.
Click to expand...
Click to collapse
Which is considered fraud and not condoned by xda.
@zelendel: Echh. I'm not looking to get myself or XDA in trouble. I'll edit my post appropriately. Thank you for the reminder.
Strephon Alkhalikoi said:
@zelendel: Echh. I'm not looking to get myself or XDA in trouble. I'll edit my post appropriately. Thank you for the reminder.
Click to expand...
Click to collapse
Not a worry. I know a lot of people advise it but we don't condone it. This is why the disclosure in the OP of every rom thread. We accept what we do might mean killing our device and having to buy a new one. It's a risk of the hobby.
Been a long time away from xda (stock android's come a long way). Back with a messed up Moto X. Here's the rundown.
Moto X 2014 dev edition XT1095
Purchased May 2015
Bootloader unlocked upon arrival
Rooted and TWRP for a while, no custom roms, eventually flashed back to stock with firmware image from Motorola
Have received multiple OTA updates since - running latest version
Have encrypted since
Ever since the marshmallow and subsequent updates my phone has been acting strangely - weird periods of rapid battery drain, misreported battery life, etc. Thought it might be a good time for a wipe, so after backing up the few pieces of data I wanted I rebooted to recovery.
Wipe cache appeared to execute properly.
Wipe userdata did not. It failed with an error that I remember including "blkdiscard on partition failed", or something along those lines, and messages about not being able to access recovery logs. Subsequent tries produced the same error. Reboot resulted in a boot loop on the initial warning bootloader unlocked boot animation, would sometimes progress past for a few seconds and freeze on the moto globe animation, and twice got a few seconds past that to a screen that explained my encrypted data was corrupted and I would need to reset my phone, with a big reset button that, when pressed, told me it would reset and restart my phone but simply turned it off.
At this point I figured I had some corrupted partitions, and what better way to repair that than start over and reflash clean? Problem is I naively assumed moto would have the latest and greatest on their firmware page, didn't pay attention to version numbers and just downloaded the highest version on there for the XT1095 - later found it was 5.1, which is obviously a downgrade and not what I wanted. Flashing that image with mfastboot produced an error during each part, starting with gpt.bin. Couple examples.
Code:
C:\Users\Dan\Desktop\motox>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.011s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.092s
Code:
C:\Users\Dan\Desktop\motox>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.399s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.545s
A little troubleshooting led to the realization that I was flashing an old android version, so I found the latest - VICTARA_TMO_XT1095_6.0_MPE24.49-18_cid9_CFC.xml.zip - at the firmware.center website. This produced the same errors.
Here's where I stand.
I've tried fastboot, mfastboot, rsdlite and windroid, nothing works
I can no longer access recovery - attempting to do so produces a red message - "Invalid boot image header!"
Whenever I try to flash an img my phone displays a pink message - "version downgraded for primary gpt", or primary recovery, etc
Attempting to format or erase partitions through fastboot produces a remote failure as well
Motorola Device Manager reports no updates for my device, current version is 24.201.3.victara_tmo.tmo.en.us
Currently my phone is in a fastboot bootloop, but fastboot appears functional - I can reboot-bootloader
The result of getvar all is:
Code:
C:\Users\Dan\Desktop\motox>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6018
(bootloader) product: victara
(bootloader) secure: yes
(bootloader) hwrev: 0x82BF
(bootloader) radio: 0x1
(bootloader) emmc: 32GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 2048MB Hynix S8 SDRAM DIE=8Gb
(bootloader) cpu: MSM8974AC ES1.1
(bootloader) serialno: TA44909E26
(bootloader) cid: 0x0000
(bootloader) channelid: 0x85
(bootloader) uid: 7A05AE100B000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei: prefer not to share, but matches
(bootloader) meid:
(bootloader) date: 05-06-2015
(bootloader) sku: XT1095
(bootloader) iccid: prefer not to share, but matches
(bootloader) cust_md5: 48718E6D7332FB353113EE5EA0335438
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Aug 30 5:20:21 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/victara_tmo/victara:6.0/M
(bootloader) ro.build.fingerprint[1]: PES24.49-18-3/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.3.victara_tmo
(bootloader) ro.build.version.full[1]: .tmo.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband[0]: MSM8974BP_42352121.25.09.24R VICTARA_T
(bootloader) version-baseband[1]: MO_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g7820355 ([email protected]
(bootloader) kernel.version[1]: ilclbld71) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri May 20 02:41:33 CDT 2016
I'm thinking either my emmc was corrupted to begin with and there was no coming back, or there was a chance at recovering but I bricked after accidentally attempting to downgrade the bootloader, even though it seemed like nothing actually flashed. If anyone has any thoughts I would be grateful, I've been down the rabbit hole today and don't have any answers. If not I suppose it's time for a new phone - or a moto claim, if possible?
try https://mirrors.lolinet.com/firmware/moto/victara/official/TMO/VICTARA_TMO_6.0_MPES24.49-18-3_cid9_CFC.xml.zip
Follow the flashing steps in the .xml file that was included in the package.
A typical flashing sequence includes all these partitions, but might vary depending on your product - so please use the sequence in the .xml file in your package.
E.g:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set oem
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Good luck.
kyo167 said:
try https://mirrors.lolinet.com/firmware/moto/victara/official/TMO/VICTARA_TMO_6.0_MPES24.49-18-3_cid9_CFC.xml.zip
Follow the flashing steps in the .xml file that was included in the package.
A typical flashing sequence includes all these partitions, but might vary depending on your product - so please use the sequence in the .xml file in your package.
E.g:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set oem
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Good luck.
Click to expand...
Click to collapse
Thanks for the quick reply but I'm getting a 403 Forbidden on that download.
Never mind I figured out how to access the file. Downloading now, will report the results. Thanks again.
kyo167 said:
try https://mirrors.lolinet.com/firmware/moto/victara/official/TMO/VICTARA_TMO_6.0_MPES24.49-18-3_cid9_CFC.xml.zip
Follow the flashing steps in the .xml file that was included in the package.
A typical flashing sequence includes all these partitions, but might vary depending on your product - so please use the sequence in the .xml file in your package.
E.g:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set oem
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Good luck.
Click to expand...
Click to collapse
Little different result this time, but the ending is still the same and all flashes fail. No more pink "version downgraded for primary gpt" messages though. Here's the output from the gpt flash. Any thoughts?
Code:
[email protected]:~/Desktop/motox$ sudo fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 5.099s
Next command (fastboot flash motoboot motoboot.img) throws "(bootloader) Failed to erase partition" or not?
kyo167 said:
Next command (fastboot flash motoboot motoboot.img) throws "(bootloader) Failed to erase partition" or not?
Click to expand...
Click to collapse
Yes.
Code:
[email protected]:~/Desktop/motox$ sudo fastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (2022 KB)...
OKAY [ 0.082s]
writing 'motoboot'...
(bootloader) flashing sbl1 ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash sbl1
FAILED (remote failure)
finished. total time: 5.258s
Try again with https://mirrors.lolinet.com/firmware/moto/victara/official/TMO/XT1095_VICTARA_TMO-RETUS_6.0_MPES24.49-18-7_cid9_CFC.xml.zip
If no luck, try
https://firmware.center/firmware/Motorola/Moto%20X%20%282nd%20gen-2014%29/Stock/XT1095/VICTARA_TMO_XT1095_6.0_MPE24.49-18_cid9_CFC.xml.zip
Hello,
Model: XT1900-1 (originally android one 9.0 - retail)
Rom: ionOS 10.0
I recently installed ionOS without any issues. I had Lineage 16.0 installed before ion.
The last few days ion was getting very slow. I rebooted and got stuck after the google logo came up. Nothing happens after the google logo it just goes to a black screen. I can reboot into the bootloader but am not able to load recovery. I am also not able to fastboot into recovery via flash or temporarily.
Bootloader is unlocked
Commands and errors
Code:
fastboot boot recovery.img
Code:
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
downloading 'boot.img'...
Code:
C:\adb>fastboot flash recovery.img
(bootloader) slot-counttyp: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-su: not found
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
Code:
C:\adb>fastboot erase recovery
(bootloader) slot-co: not found
(bootloader) slot-suffi: not found
(bootloader) partition-typ: not found
erasing 'recovery'...
(bootloader) Invalid partition name recoveryon-typ
FAILED (remote failure)
finished. total time: 0.008s
Any help on restoring recovery would be greatly appreciated. Once I can get to recovery I'll flash it back to stock (9.0)
Thanks!!!
Damien
This has been resolved. The error messages just werent making any sense so after a little more digging a tried a different usb port and commands started to respond as expected.
I gor twrp running via
Code:
fastboot boot recovery.img
and then cleaned everything out. Now let see if can get the wifi and sim to work on this rom.
Thanks!