mototorloa edge (XT2063-2) Android 10 Build QPD30.114-23-2
Posting this info to hopefully make someones life a little easier if they are attempting to recover from a hard brick xt2063:
Was using this as my main guide to root:
https://www.rootingsteps.com/root-motorola-edge/
This process unlocked my boot loader:
https://myphoneupdate.com/unlock-bootloader-motorola-edge/
Success getting TWRP installed using these as guide:
https://twrp.me/motorola/motorolamotoedge.html
https://dl.twrp.me/racer/
I successfully gained root (tried magisk and SuperSU methods), not sure which one worked for me)
I was exploring (learning) in TWRP and while in the Reboot menu, switched current slot to B, then clicked "Reboot System"
Hard bricked.
Screen went blank. No key combo would bring anything back to screen.
Using these as my main guide, I was able to get the phone to boot again:
https://www.techswizz.com/motorola-moto-edge-5g-xt2063-stock-rom-firmware-flash-file/
https://mirrors.lolinet.com/firmware/moto/racer/
I used a win10 machine, many tries running the bat script. I ended up extracting the official retail zips into the blank flash directory to get past the ERROR :
**** Log buffer [000001] 2022-02-15_09:44:25 ****
[ -0.000] Opening device: \\.\COM5
[ 0.002] Detecting device
[ 0.003] ...cpu.id = 286 (0x11e)
[ 0.003] ...cpu.sn = (edited out)
[ 0.003] Opening singleimage
[ 0.161] Loading package
[ 0.164] ...filename = pkg.xml
[ 0.165] Loading programmer
[ 0.165] ...filename = programmer.elf
[ 0.166] Sending programmer
[ 0.258] Handling things over to programmer
[ 0.258] Identifying CPU version
[ 0.258] Waiting for firehose to get ready
[ 3.317] ...SM_SAIPAN 2.0
[ 3.318] Determining target secure state
[ 3.322] ...secure = yes
[ 3.401] Configuring device...
[ 3.408] Skipping UFS provsioning as target is secure
[ 3.408] Configuring device...
[ 3.575] Flashing GPT...
[ 3.575] Flashing partition with gpt.bin
[ 3.577] ERROR: do_package()->do_recipe()->do_flash()->flash_simg()->find_first_package()->not found
[ 3.577] Check qboot_log.txt for more details
[ 3.577] Total time: 3.580s
[ 3.578]
[ 3.578] qboot version 3.86
I also tried this guide but it doesn't work on my motorola edge XT2063-3 help plss https://ibb.co/NSH6WYz
Yeah. Don't try to install the Android 12 Pixel Experience on this phone. It hard bricked mine to the point of not even having a fastboot mode. This guide didn't work either. No way to get back a bootloader mode. Just a brick now.
If someone here knows how to use the mmcblk0.img I've gotten we can prolly unbrick our phones guy
jeddy877 said:
Yeah. Don't try to install the Android 12 Pixel Experience on this phone. It hard bricked mine to the point of not even having a fastboot mode. This guide didn't work either. No way to get back a bootloader mode. Just a brick now.
Click to expand...
Click to collapse
I'm in the same predicament. I tried LOS 19.1 and I think it updated the bootloader and now I am hardbricked and get the same error. How do you fix fastboot/restore stock?
Update- fixed here:
Moto Edge (racer) Stock Firmware
Moto Edge XT2063 racer Firmware Rescue and Smart Assistant (LMSA) https://mirrors.lolinet.com/firmware/moto/racer/official/ https://t.me/s/MotoUpdatesTracker?q=#racer [Index] Motorola Stock Firmware Blankflash...
forum.xda-developers.com
Make sure you use Copy A/B script again before flashing a new from after restoring from LMSA
skuppej said:
I'm in the same predicament. I tried LOS 19.1 and I think it updated the bootloader and now I am hardbricked and get the same error. How do you fix fastboot/restore stock?
Click to expand...
Click to collapse
I'm getting confused what you guys mean by brick and hardbrick here because for me as I know hardbrick, because my phone is stuck in edl/ Qualcomm mode and nothing I'm doing is able to even boot it into fast boot or bootloader that's what hardbrick means but I'm seeing here clear as day you've been able to restore your phone using lmsa, was your phone doing the same thing mine is right now? and you were still able to use lmsa? If not then I think you were just normal soft bricked
ninjakira said:
I'm getting confused what you guys mean by brick and hardbrick here because for me as I know hardbrick, because my phone is stuck in edl/ Qualcomm mode and nothing I'm doing is able to even boot it into fast boot or bootloader that's what hardbrick means but I'm seeing here clear as day you've been able to restore your phone using lmsa, was your phone doing the same thing mine is right now? and you were still able to use lmsa? If not then I think you were just normal soft bricked
Click to expand...
Click to collapse
correct I was softbricked and I was able to restore using a blankrom + lmsa back to stock... HOWEVER, I am now hard bricked because I didn't flash A/B again after bringing it back to stock and flashing LOS 18.1.. and now it is not even working using blankflash
skuppej said:
correct I was softbricked and I was able to restore using a blankrom + lmsa back to stock... HOWEVER, I am now hard bricked because I didn't flash A/B again after bringing it back to stock and flashing LOS 18.1.. and now it is not even working using blankflash
Click to expand...
Click to collapse
It's going to be a long wait for a working blank flash then because apparently for the latest stock firmware Motorola changeed the bootloader so the current recent blank flash that is there on mirrors is just repackaged and it uses an old fire hose programmer, we need a new fire hose programmer which can only be signed from Motorola and can only be got for Motorola so I'd cut the loss my guy and get a new phone, our device is also ufs so using the mmcblk0.img method won't work either because it needs to be an emmc device, I personally can suggest the Moto edge 2021 minus the LCD display (most of the other displays I have in my personal life like my TV and other things use LCD anyway so I'm used to it) it's pretty good lol there is no official Twrpor unofficial twrp and there is no custom roms yet for it, best root method is using the patched boot.img method
ninjakira said:
It's going to be a long wait for a working blank flash then because apparently for the latest stock firmware Motorola changeed the bootloader so the current recent blank flash that is there on mirrors is just repackaged and it uses an old fire hose programmer, we need a new fire hose programmer which can only be signed from Motorola and can only be got for Motorola so I'd cut the loss my guy and get a new phone, our device is also ufs so using the mmcblk0.img method won't work either because it needs to be an emmc device, I personally can suggest the Moto edge 2021 minus the LCD display (most of the other displays I have in my personal life like my TV and other things use LCD anyway so I'm used to it) it's pretty good lol there is no official Twrpor unofficial twrp and there is no custom roms yet for it, best root method is using the patched boot.img method
Click to expand...
Click to collapse
Yeah I figured it had something to do with it being a new bootloader. I got my replacement device (same phone) since I need the expandable MMC (2021 version does not have this..) and I've taken all the OTA's and I am going to try unlocking, running the A/B script, and flashing Official LOS 18.1 again. Do you know if it is safe to take up to the latest OTA (RPDS31.Q4U-39-26-14-10) before doing so?
skuppej said:
Yeah I figured it had something to do with it being a new bootloader. I got my replacement device (same phone) since I need the expandable MMC (2021 version does not have this..) and I've taken all the OTA's and I am going to try unlocking, running the A/B script, and flashing Official LOS 18.1 again. Do you know if it is safe to take up to the latest OTA (RPDS31.Q4U-39-26-14-10) before doing so?
Click to expand...
Click to collapse
The 2020 is also ufs not mmc so using the mmcblk0.img method won't work either unfortunately
Blankflash file `blankflash_racer_retail_rebuild_RPDS31.Q4U-39-26-14-10.zip` does exist here so I am hopeful that we are covered on the latest firmware/patch level....
And I just wound up getting the 2021 edge I still do have my 2020 edge it's just an edl Qualcomm mode still lol and I will say it's safe as long as you don't think going into twrp and changing the partition from a to b or vice versa, because that's what cause me to get a hardbrick, if you think your Ina bootloop jsut boot back to bootloader and reflash, don't mess with twrp lol
skuppej said:
Blankflash file `blankflash_racer_retail_rebuild_RPDS31.Q4U-39-26-14-10.zip` does exist here so I am hopeful that we are covered on the latest firmware/patch level....
Click to expand...
Click to collapse
That's the problem, the latest blankflash for the latest firmware won't work, thats the one that needs a new firehose programmer so watch it
It's jsut a repacked blankflash using the old fire hose programmer, and unless moto or someone is able to get a new one that's signed, our hardbricks are gonna be sitting for AWHILE unfortunately
OK I see. Yikes I'm scared lol.
SO- just to confirm, when I unlock and then flash, it will flash to the inactive slot B, and then when it is done I should make sure I boot into B and never back into A or else I will be bricked again..correct?
Or will my stock rom still be present on A and I can boot back into that freely?
skuppej said:
OK I see. Yikes I'm scared lol.
SO- just to confirm, when I unlock and then flash, it will flash to the inactive slot B, and then when it is done I should make sure I boot into B and never back into A or else I will be bricked again..correct?
Click to expand...
Click to collapse
For me personally I see no use in using twrp anymore topjohnwu even has his magisk with recovery instructions as deprecated and he doesn't recommend it but I get that you still need it for custom roms and stuff still (I think) but I jsut do the patched boot.img method I don't feel the need to have to install a custom rom anymore our device is 8 GB of RAM and 256 GB of storage so I jsut don't see the need for a custom rom anymore lol when it's time to do an OTA you just go to magisk hit uninstall option, hit restore images, take the ota let it download and install and go through its process but don't reboot once it says to, go back to magisk and hit install then hit install to inactive slot, let it do its thing then reboot from magisk and you should boot back to new updated firmware with magisk installed, it does take a little bit for it to boot back and that was my problem, I didn't wait long enough (like literally a minute or two) and assumed i was bootlooped so gice it good 5-10 minutes, if it still hasnt booted, jsut use the button combo to boot to bootloader and reflash or flash the latest
Learn from my mistakes lmao
skuppej said:
Or will my stock rom still be present on A and I can boot back into that freely?
Click to expand...
Click to collapse
Man given that are hard bricks happen from switching the partitions I would not mess with it till we have a blankflash that actually works
Related
Hi people. I was trying to install a new ROM on my TF701, 'cause I was very sad to keep that stock 4.4.2.
Of course, I did a mess.
1st thing, I tried to unlock the boot with the Asus apk, but I was struck (it asked for google permission, I tried to give my correct password, but it rejected it. I saw - only too late - that maybe, if I had fully removed my google account before to use that tool, all should have been go right...).
Then, I used an utility to gain root (KingRoot4.1-release-20150703-for-xda.apk). It did the trick, but now I understand that maybe gaining the root rights it's different from "unlocking the boot". Sigh.
Then I used an utility (Flashify if my memory serves me right), to put a clockworkmod in my TF701.
I got the clockworkmod from a droidbasament link (db-blog/?p=3568).
I selected "boot" when the utility asked me what kind of img I was trying to flash... maybe I chose the wrong type again... However, it flashed the img. But now when I boot the device, I get a Signature Mismatch. Booting failed. Unrecoverable bootloader error (0x00000008), with the ASUS logo.
If I reboot with Power + Vol Down, I can get the fastboot USB download protocol, with the 3 icons in the middle of the screen.
I installed the Android SDK. I tried to take the clockworkmod recovery.img and move it in the tablet with:
fastboot boot recovery.img
but I get:
downloading 'boot.img'...
OKAY [ 0.932s]
booting...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.982s
So... the Bootloader is still locked, I imagine. Can I try to return to a full stock ROM, maybe using the microSD?
I tried to download TF701T_11.4.1.30_WW_Boot_TWRP_2870_signed.zip , put on the microSD, and launched RCK. It starts to install, but after a while I get the error broken droid picture.
I tried to rename the file to T4_SDUPDATE.zip, but I get the same results.
Am I screwed? Any help is welcome. Also, if I can fix the problem, I'll offer you a big beer! (paypal?)
Team, so I have a P9, I'm in Australia and about a week or so ago I followed this guide http://www.stechguide.com/root-and-install-twrp-recovery-on-huawei-p9/ to unlock my bootloader, install TWRP and gain root access. It all went well and I enjoyed root access using the stock Huawei ROM. I then decided to flash http://forum.xda-developers.com/p9/development/beta-android-nougat-7-0-emui-5-0-eva-t3497470 this ROM. Now, in the thread it says that to get back the things that had been missing like the camera, torch and clock apps to flash the second update. I did.
Now, this has knocked out my TWRP install and my root access, and apps like the camera etc. didn't come back the way they should have. So I think that I might either go back to a Stock ROM or to a different one all together - that is until the above mentioned process no longer works to install TWRP or gain root (through SuperSU).
What happens is that I connect my phone to my laptop, run
Code:
adb reboot bootloader
then fastboot the TWRP.img recovery file, then do a
Code:
fastboot reboot
. When the device boots back up, it displays the phone is untrusted message and sits there, doesn't do anything, same thing as if I force power cycle it, boot to Android then
Code:
adb reboot recovery
. To me, that says that TWRP isn't installed?
Anyone able to give me some help?
Okay, to make it easier to help me (lol) I just followed this process:
Powered on, I rebooted into the bootloader by entering adb reboot bootloader
Then I installed TWRP by entering fastboot flash recovery twrp-recovery.img - there were no errors within the Command Prompt or anything else stating that something hadn't worked
I then rebooted the device by entering fastboot reboot
Then let the phone reboot and load into Android - I then turned the device off and pressed VolUP+Power until the vibration, then let go of the power button
It's now sitting on the black screen reading "Your device has been unlocked and can't be trusted" (so the bootloader is unlocked) then the link to the mod=restore page, then at the bottom "Your device is booting now" - now I assume it's trying to boot into TWRP, I just don't understand why it can't. Help?
Bump, I really need help guys cause I've lost Bluetooth as well!
Do you try twrp for nougat? Marsmallow twrp useless with nougat. We dont have root for nougat yet.
master' said:
Do you try twrp for nougat? Marsmallow twrp useless with nougat. We dont have root for nougat yet.
Click to expand...
Click to collapse
Good point. I don't know if I've tried that. I did go onto the twrp website and download the version for my phone, but that wouldn't be nougat would it? It'd be marshmallow. I'll start there!
When I've got time tonight after my little one goes to sleep, I'm going to try this guide; https://www.gizdev.com/twrp-recovery-root-huawei-p9/ and hopefully that'll give me the recovery, at which point I'll jump to another ROM, maybe one that's a little more stock.
http://forum.xda-developers.com/p9/how-to/twrp-3-0-2-0-n-t3506947
master' said:
http://forum.xda-developers.com/p9/how-to/twrp-3-0-2-0-n-t3506947
Click to expand...
Click to collapse
I think I'll try my guide first, as the one you've linked seems a little bit doom and gloom to be honest.
So, by way of update, I tried this;
Downloaded the TWRP from https://dl.twrp.me/eva/twrp-3.0.2-0-eva.img.html
Installed through ADB on the PC
And got this result;
C:\Phone\ROOT-TWRP-HUAWEI P9(GizDev.Com)\ROOT-TWRP-HUAWEI P9(GizDev.Com)\TWRP\data>fastboot flash recovery twrp-3.0.2-0-eva.img
target reported max download size of 471859200 bytes
sending 'recovery' (22368 KB)...
OKAY [ 0.526s]
writing 'recovery'...
OKAY [ 0.173s]
finished. total time: 0.700s
Issue closed
Okay, so the issue is now solved. Details below; hopefully it'll help someone else out in the future.
Situation recap; my P9 had been unlocked, rooted and installed with TWRP recovery. Installed a the [BETA] Android NOUGAT 7.0 EMUI 5.0 (EVA-L09C432B322) ROM which lost me more than I cared to lose, such as Bluetooth, Torch, Recovery, ROOT, Clock, Huawei Camera and some more. I couldn't get recovery working back on my device to change ROM or anything - I feared all hope was lost.
I then found http://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818 which is the stock ROM installable through the force install, or three button method (Vol Up + Vol Down + Power). I downloaded this, created a folder on my SDCard named dload, copied it to there and proceeded with the three button method. Within 5 minutes, the stock ROM was installed and I was in business! I then proceeded with the standard http://www.stechguide.com/root-and-install-twrp-recovery-on-huawei-p9/ method of bootloader unlocking (as throughout the process it had locked again), TWRP install and ROOT access. There is a little bit of help that I can provide for when you're trying to find the bootloader unlock screen from within the Huawei website (as it's been moved or mislinked etc.) To get the bootloader unlock key:
Navigate to http://www.emui.com/en/
Click the Download link in the top nav bar
Click the Unlock Bootloader link
Agree to the T&C's
Enter in the data points it asks for
After that, continue through the process (note that after you unlock the bootloader, your phone will wipe) and you'll have a unlocked bootloader, with recovery installed and root access!
I'm not sure what you did wrong but I'm running the nougat beta and all the problems you mentioned about it doesn't happen to me.
Works great as a daily driver. Did you flash both the nougat zip and the camera zip? Meaning there was supposed to be two zip files to flash before rebooting because once you zip nougat, twrp disappears and you won't be able to flash the other zip.
Hi, I have the same issue.
The problem is mine is EVA L-19.
Can I follow your steps tho?
Hello Guys,
My R1 HD Amazon prime version got 8.4 update, since them WiFi and Bluetooth connectivity is broken/unstable. Their 8.3 has also the same issue.BLU support is also not that great.
I want to roll back the my phone to 7.4, with 8.4 on I cannot root or unlock the boot loader with tools and procedures posted earlier in the forum.
Can any one help me?
Appreciate your help.
Thanks
Gags
gags_bd said:
Hello Guys,
My R1 HD Amazon prime version got 8.4 update, since them WiFi and Bluetooth connectivity is broken/unstable. Their 8.3 has also the same issue.BLU support is also not that great.
I want to roll back the my phone to 7.4, with 8.4 on I cannot root or unlock the boot loader with tools and procedures posted earlier in the forum.
Can any one help me?
Appreciate your help.
Thanks
Gags
Click to expand...
Click to collapse
I have an Idea that I wanted to try but I cannot, because I cannot re-lock my boot loader.
It gives me lock failed error..
So the idea is as follows if you are willing and able to try it out.
I believe with a locked bootloader you are supposed to be able to boot "official" images.
So if you "fastboot boot v6.1-boot.img" android will not exactly boot into visual interface but will give adb access. And from there will be kernel before they patched dirty cow. So maybe the unlock tool will work.
UPDATE
I did complete my test and dirty-cow did work on 8.4 when I "fastboot boot 6.1-boot.img" even though the screen stayed on the frozen boot animation the whole time.
That leaves the last part of the idea needing testing , and that is the fact that fastboot supposed to allow official images to boot. And if the copy of boot.img is accepted as official.
mrmazak said:
I have an Idea that I wanted to try but I cannot, because I cannot re-lock my boot loader.
It gives me lock failed error..
So the idea is as follows if you are willing and able to try it out.
I believe with a locked bootloader you are supposed to be able to boot "official" images.
So if you "fastboot boot v6.1-boot.img" android will not exactly boot into visual interface but will give adb access. And from there will be kernel before they patched dirty cow. So maybe the unlock tool will work.
UPDATE
I did complete my test and dirty-cow did work on 8.4 when I "fastboot boot 6.1-boot.img" even though the screen stayed on the frozen boot animation the whole time.
That leaves the last part of the idea needing testing , and that is the fact that fastboot supposed to allow official images to boot. And if the copy of boot.img is accepted as official.
Click to expand...
Click to collapse
Thanks mrmazak, for your response. I am relatively new to fast boot and adb. I am happy to test if you can post the steps to follow. I have adb and fastboot utilities on my machine and can communicate to my R1 HD from my machine.
Thanks
Gags
gags_bd said:
Thanks mrmazak, for your response. I am relatively new to fast boot and adb. I am happy to test if you can post the steps to follow. I have adb and fastboot utilities on my machine and can communicate to my R1 HD from my machine.
Thanks
Gags
Click to expand...
Click to collapse
the test i propose is only to see if the image of 6.1 boot i have willl boot on locked bootloader.
If test works out good, then some type of update to the unlock tool will follow
1. open terminal
2. type "adb reboot bootloader"
3. type "fastboot boot v6.1_stock_boot.img"
I have made batch file that does those steps.
1. unzip files to location of your choice
2. connect usb cable to phone, make sure adb is enabled
3, click the "test_boot-6.1.bat"
I get the below error : -(
C:\Gags\Other\R1HD\R1-HD-Tool-V11\Tool-V11>fastboot boot v6.1-stock-boot.img
downloading 'boot.img'...
OKAY [ 1.589s]
booting...
FAILED (remote: oem unlock is false)
finished. total time: 1.589s
Note: I do not have "OEM Unlock" option in developers options.
-Gags
gags_bd said:
I get the below error : -(
C:\Gags\Other\R1HD\R1-HD-Tool-V11\Tool-V11>fastboot boot v6.1-stock-boot.img
downloading 'boot.img'...
OKAY [ 1.589s]
booting...
FAILED (remote: oem unlock is false)
finished. total time: 1.589s
Note: I do not have "OEM Unlock" option in developers options.
-Gags
Click to expand...
Click to collapse
was afraid of that. the image I have is untouched, and original, but because it was read back from device it is missing the signature.
or because the signature is below v8.4 it is rejected.
Wonder if there is a way to apply the signature file from the 8.4 update to that older boot.img.
so for now there is still no way to roll you back to older version rom.
Is it even possible to ... make it a bare metal and install everything from scratch? Similar to how we would install OS on a PC.
The situation I am in w.r.t BLU R1 HD, is something like BIOS is locked and hence I cannot boot PC from other media , in PC world?
gags_bd said:
Is it even possible to ... make it a bare metal and install everything from scratch? Similar to how we would install OS on a PC.
The situation I am in w.r.t BLU R1 HD, is something like BIOS is locked and hence I cannot boot PC from other media , in PC world?
Click to expand...
Click to collapse
The system app "settings" is what is missing the OEM unlock switch. A while ago @vampirefo patched the settings app for v17. The patched app returns the toggle. That settings app still works in v8.4 to give back the toggle. Problem is , as with most of rooting methods, stock recovery will not install unsigned packages.
It's the standard "catch 22" of rooting (if I could only.......)
Same issue as OP
I have the same issue, does anyone have a solution? I am stuck on 8.4 with slow wifi, I want to revert the update
brandex07 said:
I have the same issue, does anyone have a solution? I am stuck on 8.4 with slow wifi, I want to revert the update
Click to expand...
Click to collapse
Factory reset seems to have worked for me , I would give couple of more days to conclude.
gags_bd said:
Factory reset seems to have worked for me , I would give couple of more days to conclude.
Click to expand...
Click to collapse
Since the day I did factory reset it is working for me.
Hi Guys
A friend has given me a table he "bricked" a few months ago. Its a fire 7. I got it to run an old Lineage ROM back in 2017. I think it was on 5.1.1 when I got it.
He tried to flash a different ROM using flashfire and it failed, he says it gave an error about storage space - I am assuming he didn't wipe first.
Now the tablet wont boot. It powers on, shows the amazon splash then reboots, over & over.
I can get to the Amazon recovery holding the vol down button and from there into fastboot - can I recover this unit? I'm wondering if I can use adb to go from fastboot to TWRP then flash a new ROM and it will boot again?
I know a bit but not much about adb etc. Can anyone point me in the right direction?
EDIT: While messing about I have tried the info in this thread: https://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548
I can push the TWRP to the device with fastboot but it fails to boot it with error: (remote: unknown command)
I assume this means its on the locked 5.1.X bootloader and not 5.0.X
Any other options to flash a new bootable ROM to it from the Amazon recovery/fastboot?
Thanks.
cardyology said:
Hi Guys
A friend has given me a table he "bricked" a few months ago. Its a fire 7. I got it to run an old Lineage ROM back in 2017. I think it was on 5.1.1 when I got it.
He tried to flash a different ROM using flashfire and it failed, he says it gave an error about storage space - I am assuming he didn't wipe first.
Now the tablet wont boot. It powers on, shows the amazon splash then reboots, over & over.
I can get to the Amazon recovery holding the vol down button and from there into fastboot - can I recover this unit? I'm wondering if I can use adb to go from fastboot to TWRP then flash a new ROM and it will boot again?
I know a bit but not much about adb etc. Can anyone point me in the right direction?
EDIT: While messing about I have tried the info in this thread: https://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548
I can push the TWRP to the device with fastboot but it fails to boot it with error: (remote: unknown command)
I assume this means its on the locked 5.1.X bootloader and not 5.0.X
Any other options to flash a new bootable ROM to it from the Amazon recovery/fastboot?
Thanks.
Click to expand...
Click to collapse
You'll need to reload FireOS and start over as if it were a new device. If you're certain of the bootloader build reinstall FireOS 5.3.1 to avoid a potential hard brick. You'll then need to root with KingRoot, migrate to SuperSU, find a working build of FlashFire and hope the same thing doesn't happen again. All while making sure the device doesn't take an OTA update from Amazon. In short, a royal PiTA.
Note: there is an evolving hardware hack that may prove easier once it is a bit more mature. Involves cracking open the case (very easy) and shunting a point on the mainboard to ground. At present the exploit needs to run from a Linux based host but I suspect a Windows varient will soon be available. You'll find several threads discussing current progress.
The easiest way to fix this now is to follow the instructions in this thread here. This is the second method mentioned in the above post. This will reinstall the bootloader files and give you a 5.01 bootloader, defeating anti-rollback protection in the process. Afterwards you can load TWRP from fastboot.
As you probably have a 5.1.1 preloader now you should not need to open the case to enter download mode, holding down the left volume button when plugging in the USB cable should be enough.
Davey126 said:
You'll need to reload FireOS and start over as if it were a new device. If you're certain of the bootloader build reinstall FireOS 5.3.1 to avoid a potential hard brick. You'll then need to root with KingRoot, migrate to SuperSU, find a working build of FlashFire and hope the same thing doesn't happen again. All while making sure the device doesn't take an OTA update from Amazon. In short, a royal PiTA.
Note: there is an evolving hardware hack that may prove easier once it is a bit more mature. Involves cracking open the case (very easy) and shunting a point on the mainboard to ground. At present the exploit needs to run from a Linux based host but I suspect a Windows varient will soon be available. You'll find several threads discussing current progress.
Click to expand...
Click to collapse
Thank you for this - I read the hardware hack but also the option to reload fire OS & considered this to be the best option but like a ****, I flashed the tablet with Fire 5.1.2 - I now have an unbootable device. Black screen.
Anything I can do from this point?
MontysEvilTwin said:
The easiest way to fix this now is to follow the instructions in this thread here. This is the second method mentioned in the above post. This will reinstall the bootloader files and give you a 5.01 bootloader, defeating anti-rollback protection in the process. Afterwards you can load TWRP from fastboot.
As you probably have a 5.1.1 preloader now you should not need to open the case to enter download mode, holding down the left volume button when plugging in the USB cable should be enough.
Click to expand...
Click to collapse
As mentioned above, I tried to use the Amazon bootloader to flash FireOS back to the device and start again with it - I flashed 5.1.2 like an idiot and the tablet is now "dead" - I cant seem to even power it on.
Would the method described here recover the brick I now have? : )
Thanks again for the replies guys ! I think I can do the hardware hack if it will help - nothing to lose at this stage really.
cardyology said:
Thank you for this - I read the hardware hack but also the option to reload fire OS & considered this to be the best option but like a ****, I flashed the tablet with Fire 5.1.2 - I now have an unbootable device. Black screen.
Anything I can do from this point?
Click to expand...
Click to collapse
Your device is recoverable - and you may not even have to crack the case. This is the thread you'll want to follow. Still no Windows support but the process as fairly easy once you get past the prerequisites.
cardyology said:
As mentioned above, I tried to use the Amazon bootloader to flash FireOS back to the device and start again with it - I flashed 5.1.2 like an idiot and the tablet is now "dead" - I cant seem to even power it on.
Would the method described here recover the brick I now have? : )
Thanks again for the replies guys ! I think I can do the hardware hack if it will help - nothing to lose at this stage really.
Click to expand...
Click to collapse
The hack I was talking about has evolved a bit now: see here. This will reset anti-rollback protection so should unbrick the tablet. You won't even have to open the case: start with the tablet off and hold down the left volume button and plug in the USB cable as described in the post. You will end up with TWRP installed on the device and fully unlocked fastboot.
MontysEvilTwin said:
The hack I was talking about has evolved a bit now: see here. This will reset anti-rollback protection so should unbrick the tablet. You won't even have to open the case: start with the tablet off and hold down the left volume button and plug in the USB cable as described in the post. You will end up with TWRP installed on the device and fully unlocked fastboot.
Click to expand...
Click to collapse
Nice, I will give that a try now.
Thanks.
Hello XDA Community,
I recently purchased a Motorola Edge 20 for just 150€, which seems like a great deal. However, there's a catch: the display shows "Motorola confidential property, not for sale." The device had developer mode on and an open bootloader by default, and some features were still buggy. Since all the hardware components matched the retail version, I decided to try and flash the retail OS to get a more stable system.
I first tried to flash the system via a ZIP file, but I encountered a signature issue, which I now realize was due to my limited knowledge and inexperience in flashing ROMs. Next, I attempted to flash a recovery file that I found online by running the command "fastboot flash recovery recovery.img." The process seemed successful, but it resulted in my device getting stuck in a boot loop.
After more research and troubleshooting, I found a script on XDA forums that I ran with firmware that was supposed to be original, and that got my device back into a boot loop. The recovery.img is not present in that firmware. When I try to boot the phone now, it displays "booting into recovery mode" at the top and then reboots (possibly because the recovery file is broken). I tried other firmware files such as LineageOS and PixelExperience recovery, but I always encountered errors while attempting to upload the recovery file.
While attempting to flash the PixelExperience recovery, I encountered the following error message:
Code:
C:\Users\marti\platform-tools>fastboot.exe flash recovery PixelExperience_Plus_berlin-13.0-20230112-1838-OFFICIAL.img
Warning: skip copying recovery image avb footer (recovery partition size: 0, recovery image size: 100663296).
Sending 'recovery' (98304 KB) OKAY [ 2.377s]
Writing 'recovery' (bootloader) Invalid partition name recovery
FAILED (remote: '')
fastboot: error: Command failed
It appears that the bootloader reports an "Invalid partition name recovery" error. I suspect this might be related to the device being a "confidential property" version of the Motorola Edge 20, which might have a different partition layout or naming convention. The bootloader is still unlocked.
With all this information, I hope that someone can help me understand what went wrong and how to fix this issue. I would appreciate any guidance on flashing the retail OS to my Motorola Edge 20 without causing further problems or finding a compatible recovery file that will allow me to boot the device successfully.
Thank you in advance!
Hi, this problem was because there is no sector named "recovery" in Edge 20. I followed the LintageOS instructions again and got the phone into LintageOS recovery. However, after installing and updating the phone via ADB, I got the phone hard-bricked. Honestly, I don't know why, but I might have broken something much earlier in the process. Tip for future me: prepare in advance.
Sounds like you got your hands on a dev device of some sort. Try making your own update script, follow these instructions (you will need to add a few more script lines depending on your system version):
If for some reason you cannot boot into recovery mode at all, there is a Qualcomm recover tool that I found out about the hard way after bricking my device too. If you plug your phone into your computer and the computer makes a sound that it recognizes a new device then you can probably recover it. I don't remember where to find it since I too found it by chance after desperately searching the internet, so you're on your own for that.
I forgot to mention you can get ROMs on sites like lolinet but I can't guarantee integrity. Also, if it is a dev device then the IMEI might not be valid, so it might be illegal to use or it might not be functional with any SIM card, so careful what you do with it. I don't know how to check for IMEI. Maybe try the RSA tool and input your IMEI there and see if it gives you a software to download (the IMEI can be found on the inside of your SIM tray).