Database Info

Bricked Moto G XT1032

So my friend gave me her old first gen Moto G (XT1032 from Telus in Canada) because it stopped working for her. She told me nothing special happened before and she did not try to do an update. I have no way to know what version of Android the device was running before it bricked. I am familiar with Android devices but mostly Nexus phones so I thought I could try to fix it myself. So right now, here is what it does :
- If I try to turn it on, it stays stuck on the Motorola logo
- If I try to go in the bootloader, I can see it and it says the version number is 41.18 (also the device is locked and was never rooted or anything)
- When in the bootloader, if I try to Normal startup it reboots and stays stuck on the Motorola logo
- If I try to go to recovery or factory reset, the phone just shuts down and nothing happens
I have seen other posts on XDA which seem to relate to the same problem but none of them could fix the one I have. Any help would be much appreciated.
Thanks

Unstable hardware. It happened to me too after throwing on the floor for the 1000th time. The screen is still 100% healthy LoL.
Try returning it if it's still in warranty. If not, try unlocking the bootloader and flashing the latest GPE
Sent from my XT1562 using Tapatalk

Hi,
Seems like firmware goes away... **** happens, even without "throwing" it on the floor a thousand times Unlock it, install a custom recovery (latest Twrp is 2.8.7.0) and flash firmware you want...
If you get an error when flashing, maybe due to your bootloader version... Latest roms require latest bootloader (41.1A). There is a bootloader upgrader tool available in the general section of Moto G forum.
Sorry if I don't give you direct links but I'm on my phone Don't worry, you'll find easily...
Let us know evolution

Can't flash recovery
satanas17 said:
Hi,
Seems like firmware goes away... **** happens, even without "throwing" it on the floor a thousand times Unlock it, install a custom recovery (latest Twrp is 2.8.7.0) and flash firmware you want...
If you get an error when flashing, maybe due to your bootloader version... Latest roms require latest bootloader (41.1A). There is a bootloader upgrader tool available in the general section of Moto G forum.
Sorry if I don't give you direct links but I'm on my phone Don't worry, you'll find easily...
Let us know evolution
Click to expand...
Click to collapse
OK So Im trying to flash TWRP (2.8.6.0) with fastboot but when I do I get 2 errors :
target max-sparse-size: 256MB
sending 'recovery' (8480 KB)...
OKAY [ 10.195s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 15.208s
It seems my recovery partition is not formatted or something. What should I do now ? Also Im on a MAC so I think there is now way for me to update the bootloader which is not at 41.18
I also tried to boot the recovery (both stock and twrp 2.8.6.0 and 2.8.7.0) instead of flashing it by doing this :
fastboot boot recovery.img
I get this :
downloading 'boot.img'...
OKAY [ 5.330s]
booting...
FAILED (remote failure)
finished. total time: 15.383s
Im not sure where the boot.img is supposed to come from. Am I doing something wrong?
Thanks!

Softbrick, can't unlock bootloader, that's why I cant unbrick it, pls help!

So hello! I need some help here. A friend of a friend gave me this oneplus one for repair and at first it seemed easy cause i thought oh it's only a softbrick. There is a bootloop and I can access the original recovery and Fastboot. Now when I followed the unbricking guides I could not clean install CM12S because appereantly the bootloader is not unlocked but do I need to have an unlocked bootloader to install a clean signed version of CM12S?
I am trying to solve the issue with bacon root toolkit 1.0.3. I put the OPO into fastboot mode and click on "back to stock", select a signed fastboot version cm12.1s and my device is detected as a fastboot device. But now i get these weird error codes in command prompt
" FAILED (remote: Device not unlocked cannot flash or erase)" and then just another bootloop.
So I tried to unlock the bootloader with the command "fastboot oem unlock" and it does something but then when i check it with "fastboot oem device-info" it displays
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.008s"
hmmm.. so it does not unlock the bootloader but what does device tampered mean?
How do i unlock the bootloader and ultimately unbrick this device?
any help would be greatly appreciated!

GriechischerYoghurt said:
So hello! I need some help here. A friend of a friend gave me this oneplus one for repair and at first it seemed easy cause i thought oh it's only a softbrick. There is a bootloop and I can access the original recovery and Fastboot. Now when I followed the unbricking guides I could not clean install CM12S because appereantly the bootloader is not unlocked but do I need to have an unlocked bootloader to install a clean signed version of CM12S?
I am trying to solve the issue with bacon root toolkit 1.0.3. I put the OPO into fastboot mode and click on "back to stock", select a signed fastboot version cm12.1s and my device is detected as a fastboot device. But now i get these weird error codes in command prompt
" FAILED (remote: Device not unlocked cannot flash or erase)" and then just another bootloop.
So I tried to unlock the bootloader with the command "fastboot oem unlock" and it does something but then when i check it with "fastboot oem device-info" it displays
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.008s"
hmmm.. so it does not unlock the bootloader but what does device tampered mean?
How do i unlock the bootloader and ultimately unbrick this device?
any help would be greatly appreciated!
Click to expand...
Click to collapse
Hi
Trying to help.
Your device might be tampered as the "fastboot oem device-info" result shows.
Follow the steps and see if it helps (all commands below are to be entered without quotes)
1. Download latest cm13 nightly or the cm12.1-snapshot and extract the "boot.img" from it.
2. Connect the phone in fastboot mode and check connection by "fastboot devices."
3. Enter the command "fastboot flash recovery boot.img" (the one extracted above).
4. Then enter "fastboot format cache".
5. After the boot.img is flashed, enter "fastboot reboot" to reboot the phone and the let the phone boot fully to homescreen. If stuck on bootscreen( i assume rom is not tampered with) try entering stock recovery and clear cache and dalvik-cache.
6. Now again enter bootloader by reboot or using combo and check connection by "fastboot devices".
7. Now enter "fastboot oem unlock".
8. Now check "fastboot oem device-info".
It should be unlocked like:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
Please do reply if it helped.

e1forall said:
Hi
Trying to help.
Your device might be tampered as the "fastboot oem device-info" result shows.
Follow the steps and see if it helps (all commands below are to be entered without quotes)
1. Download latest cm13 nightly or the cm12.1-snapshot and extract the "boot.img" from it.
2. Connect the phone in fastboot mode and check connection by "fastboot devices."
3. Enter the command "fastboot flash recovery boot.img" (the one extracted above).
4. Then enter "fastboot format cache".
5. After the boot.img is flashed, enter "fastboot reboot" to reboot the phone and the let the phone boot fully to homescreen. If stuck on bootscreen( i assume rom is not tampered with) try entering stock recovery and clear cache and dalvik-cache.
6. Now again enter bootloader by reboot or using combo and check connection by "fastboot devices".
7. Now enter "fastboot oem unlock".
8. Now check "fastboot oem device-info".
It should be unlocked like:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
Please do reply if it helped.
Click to expand...
Click to collapse
Thanks for the reply! I tried the steps but sadly it did not work.
I downloaded cm13, extracted it to my fastboot.exe folder and did enter the commands.
"c:\unlock>fastboot devices
9c50d771 fastboot"
So my device does show up which means drivers are properly installed aren't they?
"c:\unlock>fastboot flash recovery boot.img
target reported max download size of 1073741824 bytes
sending 'recovery' (7254 KB)...
OKAY [ 0.232s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.254s"
There is the error message again, I can't flash the stock recovery becaue the bootloader is not unlocked I think but I don't know what else to do.
then:
"c:\unlock>fastboot format cache
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
target reported max download size of 1073741824 bytes
erasing 'cache'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.068s"
I did that too, I can't tell if it formatted cache or not, I dunnoooo
and then i entered the two commands to unlock and then check the bootloader:
"c:\unlock>fastboot reboot
rebooting...
finished. total time: 0.005s
c:\unlock>fastboot devices
9c50d771 fastboot
c:\unlock>fastboot oem unlock
...
OKAY [ 10.102s]
finished. total time: 10.106s
c:\unlock>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.013s]
finished. total time: 0.014s"
sooooo it sadly did not work

GriechischerYoghurt said:
So hello! I need some help here. A friend of a friend gave me this oneplus one for repair and at first it seemed easy cause i thought oh it's only a softbrick. There is a bootloop and I can access the original recovery and Fastboot. Now when I followed the unbricking guides I could not clean install CM12S because appereantly the bootloader is not unlocked but do I need to have an unlocked bootloader to install a clean signed version of CM12S?
I am trying to solve the issue with bacon root toolkit 1.0.3. I put the OPO into fastboot mode and click on "back to stock", select a signed fastboot version cm12.1s and my device is detected as a fastboot device. But now i get these weird error codes in command prompt
" FAILED (remote: Device not unlocked cannot flash or erase)" and then just another bootloop.
So I tried to unlock the bootloader with the command "fastboot oem unlock" and it does something but then when i check it with "fastboot oem device-info" it displays
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.008s"
hmmm.. so it does not unlock the bootloader but what does device tampered mean?
How do i unlock the bootloader and ultimately unbrick this device?
any help would be greatly appreciated!
Click to expand...
Click to collapse
Hi I had the same problem a couple of weeks ago, if you're able to boot into a custom recovery, flash this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 it's an alternative way of getting bootloader unlocked. Hope it helps

smarttmd said:
Hi I had the same problem a couple of weeks ago, if you're able to boot into a custom recovery, flash this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 it's an alternative way of getting bootloader unlocked. Hope it helps
Click to expand...
Click to collapse
I have looked into that but how do I flash it?
I tried the commands "fastboot boot -image file-" but it says i cant do that cause once again the bootloader is locked
then there is "fastboot boot recovery -image file-" but then it says " cant find directory" or something like that..
could you please give me step by stepe instruction how you solved the issue?
I am getting very frustrated here.. beginning to think it's unsolveable.
sadly i can't boot into a custom recovery :C

GriechischerYoghurt said:
I have looked into that but how do I flash it?
I tried the commands "fastboot boot -image file-" but it says i cant do that cause once again the bootloader is locked
then there is "fastboot boot recovery -image file-" but then it says " cant find directory" or something like that..
could you please give me step by stepe instruction how you solved the issue?
I am getting very frustrated here.. beginning to think it's unsolveable.
sadly i can't boot into a custom recovery :C
Click to expand...
Click to collapse
You flash this zip in a custom recovery like any other mod. Luckily for me I still had my twrp installed so I managed to do it, but you should be able to temporarily boot from it. Is your custom recovery image in the active directory?

smarttmd said:
You flash this zip in a custom recovery like any other mod. Luckily for me I still had my twrp installed so I managed to do it, but you should be able to temporarily boot from it. Is your custom recovery image in the active directory?
Click to expand...
Click to collapse
yes it's in the directory from where i start command prompt

Try ColorOS fix if CM doesn't work. http://forum.xda-developers.com/one...neplus-one-t3013732/post58442392#post58442392
Edit: (Only if you can't get anything else to work, though)

meekrawb said:
Try ColorOS fix if CM doesn't work. http://forum.xda-developers.com/one...neplus-one-t3013732/post58442392#post58442392
Edit: (Only if you can't get anything else to work, though)
Click to expand...
Click to collapse
I tried that too. Here i

GriechischerYoghurt said:
I tried that too. Here i
Click to expand...
Click to collapse
Rough spot to be in then. Hopefully someone has some other ideas for you to try. Good luck bud.

meekrawb said:
Try ColorOS fix if CM doesn't work. http://forum.xda-developers.com/one...neplus-one-t3013732/post58442392#post58442392
Edit: (Only if you can't get anything else to work, though)
Click to expand...
Click to collapse
I tried that too.. Spoiler.. it did not work.
The drivers seem to work. I have my windows 10 set to testmode. The OPO is recognized by the Msm8974DownloadTool,, when I click on "start" the bar moves to 3/4 of the bar but then something happens and I get a "sahara" message". I tried it maybe over 10 times now. Sometimes it shows me the message immediately. Sometimes the green bar gets to 1/4 of the bar and then the "sahara" message. But sometimes the bar gets to 4/4 one time and then it says "(somethinsomething)usb(somethingsomething in chinese i guess)" and thats it. Only bootloop as a result. Maaaaan this is getting annoying.

I think where something might have gone wrong was trying to use a toolkit. Try this:
Download latest fastboot images from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Then go here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Scroll down to #8 and follow the instructions to flash all of the images using fastboot. Hopefully, you will be able to boot the phone after that. Good luck!

GriechischerYoghurt said:
I tried that too.. Spoiler.. it did not work.
The drivers seem to work. I have my windows 10 set to testmode. The OPO is recognized by the Msm8974DownloadTool,, when I click on "start" the bar moves to 3/4 of the bar but then something happens and I get a "sahara" message". I tried it maybe over 10 times now. Sometimes it shows me the message immediately. Sometimes the green bar gets to 1/4 of the bar and then the "sahara" message. But sometimes the bar gets to 4/4 one time and then it says "(somethinsomething)usb(somethingsomething in chinese i guess)" and thats it. Only bootloop as a result. Maaaaan this is getting annoying.
Click to expand...
Click to collapse
I think the last time I used the ColorOS tool was on Windows 7. Windows 8/10 seems to be a real nightmare.

ryanmat said:
I think where something might have gone wrong was trying to use a toolkit. Try this:
Download latest fastboot images from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Then go here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Scroll down to #8 and follow the instructions to flash all of the images using fastboot. Hopefully, you will be able to boot the phone after that. Good luck!
Click to expand...
Click to collapse
Thanks for the reply and trying to help! but as I stated in the title my bootloader is LOCKED so i can't write anything to it. The guide of Heisenberg states clearly "Prerequisites: unlocked bootloader." so I knew it would not work but I tried it anyway.. sadly it did not work.. this is what it's giving me:
"C:\Users\Abdulla\Desktop\cm-12.1-YOG7DAS2K1-bacon-signed-fastboot-bed37f2e18>fastboot flash modem NON-HLOS.bin
target reported max download size of 1073741824 bytes
sending 'modem' (57457 KB)...
OKAY [ 1.804s]
writing 'modem'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 1.804s
C:\Users\Abdulla\Desktop\cm-12.1-YOG7DAS2K1-bacon-signed-fastboot-bed37f2e18>"
funny thing is, it's "only" a softbrick but behaves like a hardbrick. I can't do anything and I don't know what to do at this point.

meekrawb said:
I think the last time I used the ColorOS tool was on Windows 7. Windows 8/10 seems to be a real nightmare.
Click to expand...
Click to collapse
I will try the ColorOS hardbrick method on a virtual XP machine and report back.

I tried it on a virtual XP machine but i can't get to mount the OPO, i get this error message.. now the first sentence is german and its says " the usb device Qualcomm CDMA Technologies MSM QHSUSB__BULK could not be mounted on the virtual mashine windows xp."
"Das USB-Gerät Qualcomm CDMA Technologies MSM QHSUSB__BULK konnte nicht an die virtuelle Maschine windows xp gebunden werden.
USB device 'Qualcomm CDMA Technologies MSM QHSUSB__BULK' with UUID {cdedf1ad-9235-40ef-80cf-efc72ba7678c} is busy with a previous request. Please try again later."
I don't even know if it's worth the effort trying to find a XP system and try it.. my hopes that it would work are very low at this point.. please let me know if you know a solution to this nightmare.

GriechischerYoghurt said:
I tried it on a virtual XP machine but i can't get to mount the OPO, i get this error message.. now the first sentence is german and its says " the usb device Qualcomm CDMA Technologies MSM QHSUSB__BULK could not be mounted on the virtual mashine windows xp."
"Das USB-Gerät Qualcomm CDMA Technologies MSM QHSUSB__BULK konnte nicht an die virtuelle Maschine windows xp gebunden werden.
USB device 'Qualcomm CDMA Technologies MSM QHSUSB__BULK' with UUID {cdedf1ad-9235-40ef-80cf-efc72ba7678c} is busy with a previous request. Please try again later."
I don't even know if it's worth the effort trying to find a XP system and try it.. my hopes that it would work are very low at this point.. please let me know if you know a solution to this nightmare.
Click to expand...
Click to collapse
When you do a fastboot oem unlock does it reboot you back into recovery?

I used HighOnAndroid's guide to unlock bootloader, flash a custom recovery, and root.
Tutorial Video
https://www.youtube.com/watch?v=vPv2DYnH3S8&index=9&list=PLB86F041EAFE4F3E5
Step-By-Step and Downloads
http://highonandroid.com/android-smartphones/how-to-root-oneplus-one/

Why don't you flash firmware in unlocked bootloader, if possible ( please refer in the forum, as i think there's a way to flash firmware and then you can unlock bootloader )

Go to an independent repair shop. They have the equipment to flash on the motherboard.

Unbrick moto g turbo

I have a bricked moto g turbo which is locked so i cant flash firmware files i tried getting bootloader unlock code but a error shows up to tick allow bootloader unlock in developer options but i can't turn on my phone so I cant enable that option. please help

You don't need to be unlocked to flash factory firmware. Just go to http://forum.xda-developers.com/showthread.php?t=3169639 and get the correct firmware and follow the instructions in http://forum.xda-developers.com/showthread.php?t=3187750 and flash your device.
Bootloader unlock is only needed for downgrading, root, and flashing custom ROMs and recovery. It is not needed to flash a full factory image that is the same or newer.
And for the record, if OEM Unlocking is not enabled, the bootloader cannot be unlocked.

fastboot flash partition gpt.bin
sending 'partition' (32 KB)... OKAY
writing 'partition'... (bootloader) Preflash validation failed
FAIL
FAILED (remote failure)
Execution time is 1(s)
getting error

Hi i have the same error. But my problem is with the módem. I cant take signal. I try flash the original rom and don't work

Do you have the log file?

Trying to root with Android 8.0

So I've been using this guide to finally try and root my Pixel on 8.0: {apparently I can't post links yet, but google "how to root google pixel droidviews" and it's the first link}
I'm able to get adb to recognize the phone, however, when I go to use the command "fastboot boot recovery twrpOreo.img", the console says "cannot boot 'recovery': No such file or directory". So then I did some googling and tried the command "fastboot flash recovery twrpOreo.img" to which the console spits out:
C:\adb>fastboot flash recovery twrpOreo.img
target reported max download size of 536870912 bytes
sending 'recovery' (26029 KB)...
OKAY [ 0.701s]
writing 'recovery'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.802s
All the while the screen on the phone says:
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
So it says the device is locked but I triple checked, and I unlocked the bootloader under developer settings? Can anyone help me out here?

Kew01 said:
So I've been using this guide to finally try and root my Pixel on 8.0: {apparently I can't post links yet, but google "how to root google pixel droidviews" and it's the first link}
I'm able to get adb to recognize the phone, however, when I go to use the command "fastboot boot recovery twrpOreo.img", the console says "cannot boot 'recovery': No such file or directory". So then I did some googling and tried the command "fastboot flash recovery twrpOreo.img" to which the console spits out:
C:\adb>fastboot flash recovery twrpOreo.img
target reported max download size of 536870912 bytes
sending 'recovery' (26029 KB)...
OKAY [ 0.701s]
writing 'recovery'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.802s
All the while the screen on the phone says:
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
So it says the device is locked but I triple checked, and I unlocked the bootloader under developer settings? Can anyone help me out here?
Click to expand...
Click to collapse
There is no recovery partition on a Pixel. It's now part of the boot partition. Make sure unlock is toggled in Dev settings. Remember, it will wipe your data. Then
fastboot flashing unlock
Follow the real directions here
https://developers.google.com/android/images

Kew01 said:
So I've been using this guide to finally try and root my Pixel on 8.0: {apparently I can't post links yet, but google "how to root google pixel droidviews" and it's the first link}
I'm able to get adb to recognize the phone, however, when I go to use the command "fastboot boot recovery twrpOreo.img", the console says "cannot boot 'recovery': No such file or directory". So then I did some googling and tried the command "fastboot flash recovery twrpOreo.img" to which the console spits out:
C:\adb>fastboot flash recovery twrpOreo.img
target reported max download size of 536870912 bytes
sending 'recovery' (26029 KB)...
OKAY [ 0.701s]
writing 'recovery'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.802s
All the while the screen on the phone says:
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
So it says the device is locked but I triple checked, and I unlocked the bootloader under developer settings? Can anyone help me out here?
Click to expand...
Click to collapse
You skipped a step. You also need to issue the fastboot command to unlock it.
This will WIPE your phone. No way around that.
fastboot flashing unlock

TonikJDK said:
You skipped a step. You also need to issue the fastboot command to unlock it.
This will WIPE your phone. No way around that.
fastboot flashing unlock
Click to expand...
Click to collapse
Damn, really? There's no way to preserve my data? I know I can back up my photos/docs and **** but I'd sacrifice a lot of app data/preferences by wiping.

Kew01 said:
Damn, really? There's no way to preserve my data? I know I can back up my photos/docs and **** but I'd sacrifice a lot of app data/preferences by wiping.
Click to expand...
Click to collapse
This is why you should unlock the phone as soon as you buy it.

So maybe a dumb question but I'm new to all this. Is there any way I could completely backup a clone of my phone's data, and then restore it after root, so that everything is just as it was, except now I have root privileges?

Kew01 said:
So maybe a dumb question but I'm new to all this. Is there any way I could completely backup a clone of my phone's data, and then restore it after root, so that everything is just as it was, except now I have root privileges?
Click to expand...
Click to collapse
No. You can do this once you are rooted and have TWRP but not before. Just back up your important data and go for it.

Kew01 said:
Damn, really? There's no way to preserve my data? I know I can back up my photos/docs and **** but I'd sacrifice a lot of app data/preferences by wiping.
Click to expand...
Click to collapse
Isn't app data automatically backed up on Google servers? Or am I recalling it wrongly?

Golf c said:
There is no recovery partition on a Pixel. It's now part of the boot partition. Make sure unlock is toggled in Dev settings. Remember, it will wipe your data. Then
fastboot flashing unlock
Follow the real directions here
https://developers.google.com/android/images
Click to expand...
Click to collapse
Whenever I click "Acknowledge" on the page, the page just reloads?

Golf c said:
There is no recovery partition on a Pixel. It's now part of the boot partition. Make sure unlock is toggled in Dev settings. Remember, it will wipe your data. Then
fastboot flashing unlock
Follow the real directions here
https://developers.google.com/android/images
Click to expand...
Click to collapse
Kew01 said:
Whenever I click "Acknowledge" on the page, the page just reloads?
Click to expand...
Click to collapse
**** nevermind I figured it out.

Golf c said:
There is no recovery partition on a Pixel. It's now part of the boot partition. Make sure unlock is toggled in Dev settings. Remember, it will wipe your data. Then
fastboot flashing unlock
Follow the real directions here
https://developers.google.com/android/images
Click to expand...
Click to collapse
Sorry for spamming you, but it looks like the official instructions only show you how to re-flash the system OS without root privileges? My goal is to re-flash with root.

Kew01 said:
Sorry for spamming you, but it looks like the official instructions only show you how to re-flash the system OS without root privileges? My goal is to re-flash with root.
Click to expand...
Click to collapse
1. Flash factory image
2. Boot system
3. Reboot bootloader
4. Fastboot Twrp 3.1.1.1
5. Flash Twrp 3.1.1.1 installer zip or not if you don't want permanent Twrp
6. Flash SuperSU or Magisk
7. Reboot system

Honor 6X - Can't flash recovery

Hello
I have a Honor 6X running EMUI 5.0.3 and BLN-L21C432B382. I unlocked my bootloader a long time ago using Huawei code.
Unfortunately, I can't flash the recovery anymore (I don't know why TWRP is not available anymore, I might have done something wrong), indeed, when I restart into fastboot mode, frp is unlock but phone is locked and when I run the flash command, I get the following error:
Code:
sudo fastboot flash boot Downloads/twrp-3.1.1-0-berlin.img
target reported max download size of 471859200 bytes
Sending 'boot' (24466 KB)...
OKAY [ 0.639s]
Writing 'boot'...
FAILED (remote: Command not allowed)
Finished. Total time: 0.706s
And it seems that the bootloader is locked:
Code:
sudo fastboot oem get-bootinfo
(bootloader) locked
OKAY [ 0.006s]
I have to say that I don't know what to do (I would like to install a newer version of Android on this phone).
Could you please help me
Thanks

Have you enabled OEM unlock in developer settings? And, how many time ago did ya unlocked the bootloader? In firmwares newer than a certain date (June 2018 if i don't remember bad) those geniuses at Huawei released builds that automatically relocked the bootloader (happened to me also), so you may have to unlock it again.
Anyway the correct command in fastboot is "fastboot flash recovery (nameofrecovery).img", not sudo flash boot because you'll end up flashing a recovery image to boot image, probably messing up stuff. Luckily this time your bootloader was locked, anyway pay attention because in Huawei's world it's easy to f**k up in a question of seconds!

Yes I enabled OEM Unlock in developer settings.
I think that you are right, I unlocked my bootloader a long time ago (probably 2 years ago). I read that Huawei does not deliver the code to unlock the bootloader anymore, is that right ? (I can't find my old code).
Regarding the command I ran, you're totally right, I tried first first fastboot flash recovery and as it was not working and wanted to make it work (.....) so I tried to run the flash on the boot (which was a pretty bad idea, I agree).
Thanks

Yeah if the unlock has been made 2 years ago, surely the bootloader is locked again now. Sadly yes, Huawei has stopped support about unlocking the bootloader last year, so unless you'll find it again you'll have to pay some third party service like DC-Phoenix/FunkyHuawei/ecc. to obtain it again.
And seriously, be careful about flashing one specific image to a different partition. This is an error that could lead to serious troubles in worst scenarios. Nothing hard to do dude, next time thank me with the dedicated button, it's there exactly for its purpose :highfive: