Hi,
Earlier on today I was trying to root my phone (Well at least put TWRP on so I could mount a rom) and somehow the bootloader got locked during the process this has prevented me to install any roms....
I know it's locked because of -
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.079s]
finished. total time: 0.080s
I've tried to recover it back to normal during the "Fastboot Mode" state but not had any luck I believe the phones bricked? -
C:\Users\Liam\Desktop\One Plus Recovery\A2001_14_A.03_150805>fastboot flash user
data userdata_64G.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.003s
I need this sorting as I don't have a phone to use, and would really apreiciate if someone could help me as i've spent like 8 hours today trying to sort it but not had any luck i've downloaded drivers (Qualcom), Android SDK, this Qualcom-download-tool for recovery and nothing seems to work
It will only boot into "Fastboot Mode"
i recommand you to ask this on OnePlus forums there is more people that answer
otherwize did you tried fastboot oem unlock and is your phone recognize by your computer ?
Use the Qualcomm recover method mentioned many times over in this forum.
try fastboot oem unlock.
did u enabled oem unlock option in dev settings while unlocking bl?
what exactly steps you followed?
Hello all,
I recently bought a OnePlus 2 and attempted to root it. I can only remember trying to root it with a locked bootloader (which caused the OnePlus startup to hang). Eventually, I put the OS back in. Now, in a second attempt to root my phone, the first step was to unlock the bootloader. Every time I type "fastboot oem unlock" it brings me back to TWRP. When boot back into fastboot and check device info, I get this:
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.070s]
finished. total time: 0.070s
Also, attempting to flash any recovery (or any other command) returns this:
target reported max download size of 536870912 bytes
sending 'recovery' (22032 KB)...
OKAY [ 0.719s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.742s
Any suggestions? I've tried searching so many different threads all over Google.
Files that I have available to use: stock recovery, TWRP recovery, latest full ROM from OPT
Follow this guide:
https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.345478/
I already tried this guide. The phone is fully functional. I just cannot unlock the bootloader.
Every time I type "fastboot oem unlock" it brings me back to TWRP.
Click to expand...
Click to collapse
How did you install TWRP if the bootloader is locked? Did you install TWRP previously and re-lock the bootloader?
I have no idea. I think so. But it's fine I somehow managed to unlock the bootloader (finally). I just found out that OxygenOS 3.1.0 doesn't allow root.
I have Moto X play XT1563. It was stuck in a boot loop - moto logo->circle and "erasing"->reboot
Fastboot and ADB works
I tried to flash new firmware (stock image) - failed:
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
based on that and research I decided to unlock bootloader, which ended up with:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
since phone is unalbe to boot I cannot go to dev options. Is there any way to have it done using adb or fastboot? even low level linux way to change something in the config?
or (easier way) - anyone aware where can I find new Bell firmware? now I have M8936_2020632.44.03.21.57R LUX_BELLCA_CUST
Appreciate any suggestions
Check here
https://github.com/motoxplay/stock
there is a bell firmware but is tagged with a BELL? so, don´t know if will it work
Cheers.
Thanks - checked that before - this one is 6.0.1 and I need 7.1.1
Version NPD26.48-21-1 to be exact
I also tried to boot into custom recovery (.img file from here:
https://forum.xda-developers.com/moto-x-play/orig-development/recovery-twrp-2-8-7-0-t3194656):
fastboot boot boot.img
failed:
downloading 'boot.img'...
OKAY [ 0.401s]
booting...
FAILED (remote failure)
finished. total time: 0.405s
stingu said:
I also tried to boot into custom recovery (.img file from here:
https://forum.xda-developers.com/moto-x-play/orig-development/recovery-twrp-2-8-7-0-t3194656):
fastboot boot boot.img
failed:
downloading 'boot.img'...
OKAY [ 0.401s]
booting...
FAILED (remote failure)
finished. total time: 0.405s
Click to expand...
Click to collapse
Do you have an unlocked bootloader?
Did you try to install TWRP ? It's not bootloader unlocked, is it ?
Bootloader is locked, while trying to unlock it I get:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Flashing and booting fails, for stock and TWRP
Not sure does this make sense, but by recovery mode is 7.1.1 and when I check image using fastboot command I get:
(bootloader) ro.build.fingerprint[0]: motorola/lux_retca/lux:6.0.1/MPDS2
(bootloader) ro.build.fingerprint[1]: 4.107-52-3-5/5:user/release-keys
is it possible to have recovery 7.1.1 and system 6.0.1?
Not sure does this make sense, but by recovery mode is 7.1.1 and when I check image using fastboot command I get:
(bootloader) ro.build.fingerprint[0]: motorola/lux_retca/lux:6.0.1/MPDS2
(bootloader) ro.build.fingerprint[1]: 4.107-52-3-5/5:user/release-keys
is it possible to have recovery 7.1.1 and system 6.0.1?
So after installing xposed and a few other things my phone crashed, and on reboot, I got boot image did not pass verification message or some such. Normally I would just flash stock then twrp and go from there, but it seems that somehow along the way my partition tables got corrupted. I can get into fastboot, but all fastboot commands fail. I tried to reflash the gpt partition and bootloader partitions first as some suggested, but it's not working
Code:
$ fastboot flash partition gpt.bin
Sending 'partition' (45 KB) OKAY [ 0.002s]
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...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote failure)
Finished. Total time: 0.059s
$ fastboot flash bootloader bootloader.img
Sending 'bootloader' (5115 KB) OKAY [ 0.114s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition aboot
FAILED (remote failure)
Finished. Total time: 0.309s
I also tried blankflash, but I am unsure how to make it work since everytime I connect a USB cable the device starts itself in bootloader/fastboot mode right away, and attempting to blank flash it then just hangs at
Code:
<waiting for device>
Flashing recovery results in
Code:
$ fastboot flash recovery twrp-3.2.3-1-potter.img
Sending 'recovery' (16316 KB) OKAY [ 0.351s]
Writing 'recovery' (bootloader) Image not signed or corrupt
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
Finished. Total time: 0.355s
Any help is appreciated!
Drkmatr1984 said:
So after installing xposed and a few other things my phone crashed, and on reboot, I got boot image did not pass verification message or some such. Normally I would just flash stock then twrp and go from there, but it seems that somehow along the way my partition tables got corrupted. I can get into fastboot, but all fastboot commands fail. I tried to reflash the gpt partition and bootloader partitions first as some suggested, but it's not working
I also tried blankflash, but I am unsure how to make it work since everytime I connect a USB cable the device starts itself in bootloader/fastboot mode right away, and attempting to blank flash it then just hangs at
Flashing recovery results in
Any help is appreciated!
Click to expand...
Click to collapse
Try erasing everything by using ADB codes then flash the latest bootloader and gpt then flash the stock ROM and lock the bootloader,and the flash the whole firmware again,so there will be no partition corrupted.after that you can unlock your bootloader.
Also, make sure to flash the latest stock firmware, being sure not to try and revert to an earlier version. Don't flash blankflash unless you are totally bricked, with just flashing light. Your device will never be the same if you do.
riyan65 said:
Try erasing everything by using ADB codes then flash the latest bootloader and gpt then flash the stock ROM and lock the bootloader,and the flash the whole firmware again,so there will be no partition corrupted.after that you can unlock your bootloader.
Click to expand...
Click to collapse
How do I use ADB if I can't get beyond fastboot? I can't load TWRP or flash TWRP to get into it to access ADB. And ADB commands don't work from the fastboot bootloader screen.
Doing "fastboot erase <partition name>" or "fastboot format:ext4 <partition name>" also fails same as the other fastboot flash commands so I can't erase my partitions from fastboot before re-flashing.
If all fastboot commands fail, including
Code:
fastboot devices
,
Code:
fastboot getvar all
I would uninstall, and reinstall adb/fastboot and all it's drivers. I would also reinstall the moto drivers. Try a different cable, and perhaps even a different pc. If the phone boots to bootloader mode, you should be able to execute those basic commands if it is communicating. If it is communicating, then try flashing the most recent stock firmware. Many gpt errors are from trying to downgrade.
[email protected] said:
If all fastboot commands fail, including
Code:
fastboot devices
,
Code:
fastboot getvar all
I would uninstall, and reinstall adb/fastboot and all it's drivers. I would also reinstall the moto drivers. Try a different cable, and perhaps even a different pc. If the phone boots to bootloader mode, you should be able to execute those basic commands if it is communicating. If it is communicating, then try flashing the most recent stock firmware. Many gpt errors are from trying to downgrade.
Click to expand...
Click to collapse
Ok, after trying 3 different USb cables, including a brand new one I just ordered, and after uninstalling all drivers on pc and rebooting, then reinstalling, I still get these same responses from fastboot devices and fastboot getvar all
Code:
C:\ProgramData\LMSA\Download\RomFiles>fastboot devices
ZY224262W9 fastboot
and
Code:
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.008s
Any other fastboot commands fail with similar errors. Trying to reflash OPSS28-85-17-2 results in
Code:
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot devices
ZY224262W9 fastboot
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot reboot bootloader
rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.005s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>OREO.BAT
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_set
FAILED (remote failure)
Finished. Total time: 0.003s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
Sending 'partition' (45 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.146s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.i
mg
Sending 'bootloader' (5115 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.009s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash logo logo.bin
Sending 'logo' (2186 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.009s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
Sending 'boot' (16384 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 6.967s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash recovery recovery.img
Sending 'recovery' (20580 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.009s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash dsp adspso.bin
Sending 'dsp' (16384 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.008s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash oem oem.img
Sending 'oem' (104608 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.012s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.0
Sending 'system' (256553 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.011s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.1
Sending 'system' (256617 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.007s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.2
Sending 'system' (254213 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.006s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.3
Sending 'system' (256710 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.009s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.4
Sending 'system' (256912 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.010s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.5
Sending 'system' (257861 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.009s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.6
Sending 'system' (260027 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.010s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.7
Sending 'system' (257601 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.006s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.8
Sending 'system' (257805 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.010s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash modem NON-HLOS.bin
Sending 'modem' (71921 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.011s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase modemst1
Erasing 'modemst1' FAILED (command write failed
(Unknown error))
Finished. Total time: 5.006s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase modemst2
Erasing 'modemst2' FAILED (command write failed
(Unknown error))
Finished. Total time: 5.006s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash fsg fsg.mbn
Sending 'fsg' (3012 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.011s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase cache
Erasing 'cache' FAILED (command write failed
(Unknown error))
Finished. Total time: 5.008s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase userdata
Erasing 'userdata' FAILED (command write failed
(Unknown error))
Finished. Total time: 34.761s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase customize
Erasing 'customize' FAILED (command write failed
(Unknown error))
Finished. Total time: 14.723s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase clogo
Erasing 'clogo' FAILED (command write failed
(Unknown error))
Finished. Total time: 5.008s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_clear
FAILED (command write failed (Unknown error))
Finished. Total time: 5.003s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot reboot bootloader
rebooting into bootloader FAILED (command write failed
(Unknown error))
Finished. Total time: 5.007s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>
Occasionally I can get a different message
Code:
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.i
mg
Sending 'bootloader' (5115 KB) OKAY [ 0.325s]
Writing 'bootloader' (bootloader) Validating 'boot
loader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
FAILED (status read failed (Too many links))
Finished. Total time: 0.533s
and
Code:
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
Sending 'partition' (45 KB) OKAY [ 0.005s]
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) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
Finished. Total time: 0.085s
But it always fails.
Drkmatr1984 said:
If all fastboot commands fail, including ,
Ok, after trying 3 different USb cables, including a brand new one I just ordered, and after uninstalling all drivers on pc and rebooting, then reinstalling, I still get these same responses from fastboot devices and fastboot getvar all
and
Any other fastboot commands fail with similar errors. Trying to reflash OPSS28-85-17-2 results in
Occasionally I can get a different message
and
But it always fails.
Click to expand...
Click to collapse
Why don't you try latest firmware version, as it is having latest bootloader and gpt.
Here is the link for latest version:-https://mirrors.lolinet.com/firmware/moto/potter/official/
riyan65 said:
Why don't you try latest firmware version, as it is having latest bootloader and gpt.
Here is the link for latest version:-https://mirrors.lolinet.com/firmware/moto/potter/official/
Click to expand...
Click to collapse
I am using the latest from lolinet, they do not have the latest (OPSS28.85-13-5) uploaded there yet. I did manage to find a copy here But I am at work on slow internet so it may take me all night to finish downloading it
At least it is communicating, so as riyan65 posted, you need the current firmware. You don't need blankflash, that will screw the pooch big time.
[email protected] said:
At least it is communicating, so as riyan65 posted, you need the current firmware. You don't need blankflash, that will screw the pooch big time.
Click to expand...
Click to collapse
I know, I am not inexperienced with this phone. Normally I would say that getting messages from fastboot at all is good, but the messages I am getting are all saying that my bootloader and gpt tables are write protected currently. I've actually already hard bricked this device once before, and was able to rescue with blank-flash and then flash the stock firmware. This time is different as it's not hard-bricked. I don't understand why I would "need the most recent firmware" as I was never on "the most recent firmware" I should only have to flash the most recent firmware I have had installed on this phone. I never took the december security update so I shouldn't in theory need the firmware he's recommending but Im giving it a shot anyway. I will update my reply when I get a chance to try flashing the december update.
Thanks for your help guys!
Drkmatr1984 said:
I know, I am not inexperienced with this phone. Normally I would say that getting messages from fastboot at all is good, but the messages I am getting are all saying that my bootloader and gpt tables are write protected currently. I've actually already hard bricked this device once before, and was able to rescue with blank-flash and then flash the stock firmware. This time is different as it's not hard-bricked. I don't understand why I would "need the most recent firmware" as I was never on "the most recent firmware" I should only have to flash the most recent firmware I have had installed on this phone. I never took the december security update so I shouldn't in theory need the firmware he's recommending but Im giving it a shot anyway. I will update my reply when I get a chance to try flashing the december update.
Thanks for your help guys!
Click to expand...
Click to collapse
Well, Still no success. The messages do not even change. At least if it was hard bricked I could try blank flash, but right now it's like all of the partitions are write protected, including the gpt tables themselves and the bootloader. Check out the logs here: The only fastboot commands that work are fastboot devices and fastboot reboot. I finally got fastboot getvar all to print more info out though:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: xxxxxxxxxx
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 6C657D3F00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Last time flashing failed
(bootloader) imei: xxxxxxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 03-28-2017
(bootloader) sku: XT1687
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 2 23:25:13 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: S25.137-33-11/11:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.211.2.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8953_41.50.07.85R POTTER_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-ElementalX-G5-3.00
(bootloader) kernel.version[1]: ([email protected]) (gcc version 4.9.4 201506
(bootloader) kernel.version[2]: 29 (prerelease) (crosstool-NG 1.20.0 - L
(bootloader) kernel.version[3]: inaro GCC 2015.06 - Cortex-A15) ) #1 SMP
(bootloader) kernel.version[4]: PREEMPT Mon Oct 1 22:31:26 EDT 2018
(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: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retus
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.010s
Is it because the secure boot is on?
You should edit your imei in your getvar output.
When you recovered from hard brick before, did you use Vache's for this device, or the albus blankflash for Addison?
I assume you are trying to get into recovery by using the volume button, but have you tried fastboot commands.
Code:
fastboot reboot recovery
sometimes works.
With a copy of TWRP in your adb/fastboot folder, try
Code:
fastboot boot image twrp.img
or
Code:
fastboot boot recovery twrp.img
where you have renamed your TWRP image to the twrp.img. This boots into twrp without installing, and has been reported to work with fubarred partition tables. If it boots, you then can access tools to repair gpt partition tables via adb.
Drkmatr1984 said:
Well, Still no success. The messages do not even change. At least if it was hard bricked I could try blank flash, but right now it's like all of the partitions are write protected, including the gpt tables themselves and the bootloader. Check out the logs here: The only fastboot commands that work are fastboot devices and fastboot reboot. I finally got fastboot getvar all to print more info out though:
Is it because the secure boot is on?
Click to expand...
Click to collapse
Before posting this kind of information it's better to remove IMEI ans serial number!
The previous message is a little wrong:
- it's possible to boot the recovery without flashing (and very often raccomanded) but the recovery (both original and TWRP) need a working boot partition!
- it' possible also to try to boot a boot.img: if the system it's ok Android can even start!
What is strange to me is the different behaviour in the same situation: it need investigation!
nicolap8 said:
Before posting this kind of information it's better to remove IMEI ans serial number!
The previous message is a little wrong:
- it's possible to boot the recovery without flashing (and very often raccomanded) but the recovery (both original and TWRP) need a working boot partition!
- it' possible also to try to boot a boot.img: if the system it's ok Android can even start!
What is strange to me is the different behaviour in the same situation: it need investigation!
Click to expand...
Click to collapse
Ok, thanks! and done!
I will give these new suggestions a try later tonight. I did hear about booting into TWRP before, but have had little luck with that. However, I think I have only tried fastboot boot twrp.img and not with recovery or image as keywords in there...
OK, so the two fastboot commands are not the correct syntax.
Code:
C:\Users\Hermes\Moto G5 Plus\TWRPs>fastboot boot image twrp.img
fastboot: error: cannot load 'image': No such file or directory
C:\Users\Hermes\Moto G5 Plus\TWRPs>fastboot boot recovery twrp.img
fastboot: error: cannot load 'recovery': No such file or directory
Doing this:
Code:
$ fastboot boot boot.img recovery.img
fastboot: error: cannot boot a boot.img *and* ramdisk
Almost works lol
"fastboot reboot recovery" just gives this:
Code:
C:\Users\Hermes\Moto G5 Plus\TWRPs>fastboot reboot recovery
fastboot: usage: unknown reboot target recovery
C:\Users\Hermes\Moto G5 Plus\TWRPs>fastboot reboot recovery
fastboot: usage: unknown reboot target recovery
Doing "fastboot boot twrp.img" works but it hangs at the "your device is not safe" screen and never actually loads. "fastboot getvar all" returns interesting things in the slot section. Those slots don't seem normal to me. Also, my ro.fingerprint looks like it's for nougat, but my bootloader is Oreo. I'm willing to break this phone to fix it if possible, so if anyone has any riskier suggestions for me to try I'm down as I've already gone 4 days without a phone and am about to buy a new one either way.
Drkmatr1984 said:
OK, so the two fastboot commands are not the correct syntax.
Click to expand...
Click to collapse
If you are not able to get the fastboot help you have not to try to flash anything!
nicolap8 said:
If you are not able to get the fastboot help you have not to try to flash anything!
Click to expand...
Click to collapse
What? I don't understand you.
I am reading this
And am trying to understand the fastboot boot command better. It requires a kernel image and a ramdisk image. So far I have tried by using zImage from ElementalX kernel as kernel and twrp.img as Ramdisk but the boot just hangs for a long time. Does anyone know the Correct command to boot into TWRP(and kernel) from USB on this device? (Confirmed working and tested, please!)
Here are all of my attempts so far:
Code:
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot elex.zImage twrp.img
creating boot image...
creating boot image - 26769408 bytes
Downloading 'boot.img' OKAY [ 0.563s]
booting OKAY [ 0.080s]
Finished. Total time: 0.860s
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot elex.zImage twrp.img
creating boot image...
creating boot image - 26611712 bytes
Downloading 'boot.img' OKAY [ 0.554s]
booting OKAY [ 0.073s]
Finished. Total time: 0.667s
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot linux-2.6/arch/arm/boot/zImage twrp.img
fastboot: error: cannot load 'linux-2.6/arch/arm/boot/zImage': No such file or directory
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot Ele
ElementalX-G5-3.00.zip elex.zImage
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot ElementalX-G5-3.00.zip twrp.img
creating boot image...
creating boot image - 29065216 bytes
Downloading 'boot.img' OKAY [ 0.606s]
booting OKAY [ 0.081s]
Finished. Total time: 0.764s
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot zImage twrp.img
creating boot image...
creating boot image - 23590912 bytes
Downloading 'boot.img' OKAY [ 0.496s]
booting OKAY [ 0.109s]
Finished. Total time: 0.642s
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot zImage
creating boot image...
creating boot image - 6883328 bytes
Downloading 'boot.img' OKAY [ 0.154s]
booting OKAY [ 0.079s]
Finished. Total time: 0.245s
Bump.
No one knows how to boot into TWRP from USB 100% tried and tested on this device?
Drkmatr1984 said:
Bump.
No one knows how to boot into TWRP from USB 100% tried and tested on this device?
Click to expand...
Click to collapse
fastboot boot twrp.img
craigl14 said:
fastboot boot twrp.img
Click to expand...
Click to collapse
That only works when you have a boot partition that is intact.
Since my partition tables are ****ed it just hangs at boot when I run that command. I need the full command with kernel option to make it boot so that I can edit the partitions from TWRP. However, I don't know enough about the kernel of this phone, or where to obtain its sources, or how to compile them, or any of that to make it work. I'm hoping one of the ROM devs will clue me in as I can't be the only person with this phone to ever Fubar their partition tables.
I found this :
Code:
To boot with a host-side kernel image (and rootfs image)
This command allows you to download a kernel image (and optional root filesystem image) and boot the phone with those, instead of using the kernel and rootfs in the boot flash partition. It is very useful while developing a kernel or modifying the rootfs.
fastboot boot <kernel> [ <ramdisk> ]
Ex: fastboot boot linux-2.6/arch/arm/boot/zImage root-image/recovery.img-ramdisk.cpio.gz
Which seems to suggest it's possible but I just need the correct kernel and rootfs image to boot TWRP.