Hello I made a big mistake on my Moto G6 Plus
I was using a Custom ROM so I decided to lock the bootloader.
But after blocking my Smartphone does not start anymore.
When trying to start Android the following error appears.
---
Your device is corrupt. it will not be trusted and will not boot
---
I've tried installing the ROM Stock but it always gives an error.
Please help me!
(Translated by Google )
dangelfire said:
Hello I made a big mistake on my Moto G6 Plus
I was using a Custom ROM so I decided to lock the bootloader.
But after blocking my Smartphone does not start anymore.
When trying to start Android the following error appears.
---
Your device is corrupt. it will not be trusted and will not boot
---
I've tried installing the ROM Stock but it always gives an error.
Please help me!
(Translated by Google )
Click to expand...
Click to collapse
- First, download TWRP for Evert and save it into your Fastboot folder in your PC;
- Boot your device into Bootloader screen (holding power and vol - ), connect it into your computer and execute the following command:
fastboot boot (name of the image of TWRP ex: twrp-evert.img). Your mobile should boot into TWRP Recovery;
- Execute a full wipe (internal included);
- Back to the TWRP home screen, click reboot and select "Bootloader". A warning message will be displayed saying that No OS is installed. Just go ahead.
- Then flash stock rom again;
Good Luck.
I tried this but it did not work.
Enviado de meu LM-X210 usando o Tapatalk
Have you tried using blank flash?
https://forum.xda-developers.com/g6-plus/how-to/guide-unbrick-moto-g6-plus-t3789635
Also remember a relocked bootloader is useless.
Sent from my G6 Plus using XDA Labs
Thank's my bootloader os locked.
Enviado de meu LM-X210 usando o Tapatalk
dangelfire said:
Thank's my bootloader os locked.
Enviado de meu LM-X210 usando o Tapatalk
Click to expand...
Click to collapse
Blank flash should work
Sent from my Motorola Moto G6 Plus using XDA Labs
RokCruz said:
Blank flash should work
Sent from my Motorola Moto G6 Plus using XDA Labs
Click to expand...
Click to collapse
I'm going to do the procedure tomorrow, because at the moment I'm without the device.
Thank's
Enviado de meu LM-X210 usando o Tapatalk
After much struggle, I gave up trying and sent for assistance, thanks to everyone for the tips.
Enviado de meu LM-X210 usando o Tapatalk
There was no way I had to send for assistance, arrived today!
Enviado de meu moto g(6) plus usando o Tapatalk
raphap.oliveira said:
- First, download TWRP for Evert and save it into your Fastboot folder in your PC;
- Boot your device into Bootloader screen (holding power and vol - ), connect it into your computer and execute the following command:
fastboot boot (name of the image of TWRP ex: twrp-evert.img). Your mobile should boot into TWRP Recovery;
- Execute a full wipe (internal included);
- Back to the TWRP home screen, click reboot and select "Bootloader". A warning message will be displayed saying that No OS is installed. Just go ahead.
- Then flash stock rom again;
Good Luck.
Click to expand...
Click to collapse
I did exactly this and returned "FAILED (Status read failed (too many links))
Any other suggestions or ideas for me to try?
chptr0 said:
I did exactly this and returned "FAILED (Status read failed (too many links))
Any other suggestions or ideas for me to try?
Click to expand...
Click to collapse
Bootloader unlocked => flash any ROM
bootloader locked => you can't boot TWRP! Flash the stock ROM and use the same build version as currently installed on your device!! Use "fastboot getvar all" to get the build version.
WoKoschekk said:
Bootloader unlocked => flash any ROM
bootloader locked => you can't boot TWRP! Flash the stock ROM and use the same build version as currently installed on your device!! Use "fastboot getvar all" to get the build version.
Click to expand...
Click to collapse
Sorry for this simple question, but im new this.
what line is about currently version?
I used the command and haved this
Kernel: uefi
Version-Bootloader: MBM-3.0-evert-retail-8ca64c4-190507
product: evert
board: evert
meid: {be blank} Be correct???
date: 09-17-2018
iccid: {be blank}
cust_md5: {be blank}
ro.build.version.full[0]: Blur_version.29.371.27.evert.reta
ro.build.version.full[1]: il.en.US
slot-successfull:a_: no
slot-successfull:b_: no
slot-unbootable:a_: yes
slot-unbootable:b_: no
I so need help with this... If can help i so grateful.
chptr0 said:
Sorry for this simple question, but im new this.
what line is about currently version?
I used the command and haved this
Kernel: uefi
Version-Bootloader: MBM-3.0-evert-retail-8ca64c4-190507
product: evert
board: evert
meid: {be blank} Be correct???
date: 09-17-2018
iccid: {be blank}
cust_md5: {be blank}
ro.build.version.full[0]: Blur_version.29.371.27.evert.reta
ro.build.version.full[1]: il.en.US
slot-successfull:a_: no
slot-successfull:b_: no
slot-unbootable:a_: yes
slot-unbootable:b_: no
I so need help with this... If can help i so grateful.
Click to expand...
Click to collapse
There shoukd be some more lines of output...
On fastboot screen you can see the model no. XT....
This is also helpful.
Have a look at this post for example:
https://forum.xda-developers.com/showpost.php?p=82989337&postcount=1
I need to know the output for line "fingerprint".
WoKoschekk said:
There shoukd be some more lines of output...
On fastboot screen you can see the model no. XT....
This is also helpful.
Click to expand...
Click to collapse
I needed buy a new board. I install all the ROM's RETBR and RETAIL of the my cellphone Moto G6 Plus and at all ocorred same problem "Device is corrupt".
=/
But thanks for all helps that give me.
chptr0 said:
I needed buy a new board. I install all the ROM's RETBR and RETAIL of the my cellphone Moto G6 Plus and at all ocorred same problem "Device is corrupt".
=/
But thanks for all helps that give me.
Click to expand...
Click to collapse
Your hardware is not damaged, your boot.img is corrupt.
All you need is exactly the same firmware build as currently installed.
Neither a RETBR with another build no. nor a RETAIL might help you!! Your device only accepts the same build as installed. That's the meaning of a locked bootloader.
WoKoschekk said:
Your hardware is not damaged, your boot.img is corrupt.
All you need is exactly the same firmware build as currently installed.
Neither a RETBR with another build no. nor a RETAIL might help you!! Your device only accepts the same build as installed. That's the meaning of a locked bootloader.
Click to expand...
Click to collapse
Hi, i did install the blueprint version, but i got the same message, device is corrupt.
Sovietico21 said:
Hi, i did install the blueprint version, but i got the same message, device is corrupt.
Click to expand...
Click to collapse
What does blueprint version mean?
Sovietico21 said:
Hi, i did install the blueprint version, but i got the same message, device is corrupt.
Click to expand...
Click to collapse
In my case the only solution was to change the logic board. I tried everything I found on the internet, in addition to testing all ROM's and none of them worked.
dangelfire said:
Hello I made a big mistake on my Moto G6 Plus
I was using a Custom ROM so I decided to lock the bootloader.
But after blocking my Smartphone does not start anymore.
When trying to start Android the following error appears.
---
Your device is corrupt. it will not be trusted and will not boot
---
I've tried installing the ROM Stock but it always gives an error.
Please help me!
(Translated by Google )
Click to expand...
Click to collapse
Same here with Moto G8 Power. Does anybody has another solution?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
For those who are stuck at bootlogo, the problem is the same as the one when we tried before downgrading from 4.4.4 to 4.4.2 it is with the partition table, the version in the ota is older that the one we have on our devices, I dunno how the hell is that but it is what happened to most of us, though the easy fix, flash the attached gpt through fastboot command:
fastboot flash partition gpt.bin
Hope this fixed everything
Thanks very much for the information!
I recently tried flashing the 4.4.4 GPE firmware onto my XT1032 and I got an error when trying to flash the GPT.bin partition using mfastboot. It said "failed". I got nervous and went back to the retail US firmware just in case. We need more people to confirm that this fix will work.
OP do you know if it's safe to flash your GPT partition before installing the OTA update on the 4.4.4 GPE ROM?
It works!
I cant flash any rom to my phone and everything failed on half proces and with this file i rescued my phone i flashed 4.4.4 gpe and than 5.0.1 ota (by sideload) !
My Moto Gpe was brick!! And now it works again!!!! Thanks!!!!
Yes I can confirm, I faced this issue myself and used this fix for it )
Yeah!!! this work very well, you save my phone, thanks man
seriusly that was all? i had 2 moto g at home and when the first one got the ota it got hard bricked, but stupid me got back to 4.4.2 and at the 4.4.4 ota the phone hard bricked, i think that the bootloader is corrupted and now i have to wait for the full 5.0 rom to be aviabable. Thanks man i appreciate it (i had another moto g and just got the ota and booted because of this)
can't use that, i've got the 41.18 bootloader so i have to wait a 5.0 original firmware :/
or am i doing something wrong?
Bad news
ssalamon said:
can't use that, i've got the 41.18 bootloader so i have to wait a 5.0 original firmware :/
or am i doing something wrong?
Click to expand...
Click to collapse
We have the same problem fella. We must wait the firmware with the image of new bootloader...Maybe in one month we take a solution...
So, with new bootloader is not possible to apply OTA. I have received 5.0.1 OTA on my 4.4.4 GPE converted XT1032, but this failed to start after latest try to update
sebadomaitis said:
We have the same problem fella. We must wait the firmware with the image of new bootloader...Maybe in one month we take a solution...
Click to expand...
Click to collapse
The original GPE firmware has a bootloader version older than that of the 4.4.4 "again I don't know why" the only fix is by flashing the gpt file included, if you flashed the android lollipop and it didn't work, flash this and give it a shot .
"bear in mind also that this fix is for devices stuck at bootlogo not bootanimation, not a fix for bootloop"
ruphert said:
So, with new bootloader is not possible to apply OTA. I have received 5.0.1 OTA on my 4.4.4 GPE converted XT1032, but this failed to start after latest try to update
Click to expand...
Click to collapse
I faced exactly what you are facing now, flash this and everything will go smooth
Rostomania said:
I faced exactly what you are facing now, flash this and everything will go smooth
Click to expand...
Click to collapse
Thanks for you reply. After sideload 5.0.1 and stucking and google logo should I flash only your gptfix.zip and reboot?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Phone is stucking after reboot.
ruphert said:
Thanks for you reply. After sideload 5.0.1 and stucking and google logo should I flash only your gptfix.zip and reboot?
Phone is stucking after reboot.
Click to expand...
Click to collapse
No man, do the following:
1- Reboot Into bootloader and connect your device via usb.
2- In your adb folder paste the gpt file I included and press right click and shift in any white space in the folder and choose start command prompt.
3- type fastboot flash partition gpt.bin and your problem should be fixed.
Rostomania said:
No man, do the following:
1- Reboot Into bootloader and connect your device via usb.
2- In your adb folder paste the gpt file I included and press right click and shift in any white space in the folder and choose start command prompt.
3- type fastboot flash partition gpt.bin and your problem should be fixed.
Click to expand...
Click to collapse
Thanks a lot, you rocks!
Code:
sudo fastboot flash partition gpt.bin 12:02
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.036s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.320s]
finished. total time: 0.356s
sudo fastboot reboot
Phone is booting now
boot stuck
Hi, I've stucked on "android logo with unlocked lock icon".
Originally I had xt1033 asian, which was converted to 4.4 GPE one sim. Today I've tried to flash the 5.0.1 lollipop via adb, and as many of you guys, stucked on boot.
I've already tried your fix, and tried to downgrade following this thread http://forum.xda-developers.com/moto-g/general/guide-xt1033-downgrade-lollipop-5-0-to-t2969729
but still phone doesn't boot, just "Google" and lock icon...
can you help me, at least boot it, android version doesn't metter
** UPDATE **
So, I've managed to boot phone thatks to this thread http://forum.xda-developers.com/moto-g/general/guide-restore-softbricked-phone-t2965459
Gonna make a backup and try installing 5.0.1 again
sebadomaitis said:
We have the same problem fella. We must wait the firmware with the image of new bootloader...Maybe in one month we take a solution...
Click to expand...
Click to collapse
Not exactly, my XT1033 had 41.18 bootloader when i applied the 5.0.1 ota, it just worked with the following tutorial. I didn't even use the gpt file here.
http://forum.xda-developers.com/moto-g/general/guide-convert-brazilian-firmware-gpe-5-t2969472
awesome.. this works like wonder.. but now i am not getting the network .. any idea what to do?
ghost9685 said:
awesome.. this works like wonder.. but now i am not getting the network .. any idea what to do?
Click to expand...
Click to collapse
Look at this tread
http://forum.xda-developers.com/moto-g/general/gpe-ota-lrx21z-5-0-1-xt1033-xt1032-t2969847
1st post
Step 5
Maybe it could work
My Own devices is a XT1032, and this fix has nothing to do with the XT1033 converted to GPE .
I can also confirm that this works. But my phone was already converted to GPE and had 4.4.4 before I did the OTA update.
Giovani's guide works if you're stuck on the bootlogo after updating to 4.4.4 and then lollipop through OTA (on a gpe converted device of course). I used the second method in that thread.
Here is a guide on updating your branded/unbranded non developer edition HTC ONE M8 to the developer edition android 5.0 (lollipop) update and also converting your device to a developer edition device by modifying the MID and CID of your device.
(this will also get you new updates as soon as HTC releases them as your phone is now a developer edition phone)
REQUIRES S-OFF AND POSSIBLY UNLOCKED BOOTLOADER
GPE CONVERTED DEVICES NEED TO GO BACK TO SENSE FIRST
HTC Drivers - https://mega.co.nz/#!9cpz0Soa!rZH0H5djENbFN2xkS9S7yUlXzX_vcC5yOHhmUR55kUM
ADB + Fastboot - https://drive.google.com/file/d/0B1S0LCuXCnnmOWhnUk1ZWVdQakE/view
First thing you want to do is boot the device and enable adb then type the below lines
Code:
adb shell
su
DO NOT MESS UP THE BELOW COMMAND - COPY AND PASTE IT - ENTERING IT WRONG COUlD BRICK YOUR DEVICE
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
Code:
adb reboot bootloader
fastboot oem writecid BS_US002
fastboot reboot-bootloader
Download this file RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.16.1540.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_411207_signed_2.exe
(STOCK LOLLIPOP 5.0 RUU FOR UNLOCKED + DEVELOPER EDITION HTC ONE M8 [this is what you have now since you changed CID and MID])
CRC32: 665CF81E
MD5: FDB3C48A40F1D42165783D75CFF4B846
SHA-1: 0B3C785F7735133ED11852E2FFAD29949A514DB1
Once it is downloaded, type the following commands
Code:
fastboot oem rebootRUU
FLASHING RUU'S WILL WIPE YOUR INTERNAL SD (/DATA/MEDIA)
Run RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.16.1540.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_411207_signed_2.exe and just press next/confirm etc. ignore the usb connection instructions, once that is done, the device will reboot and you will be on lollipop
CLICK FOR OLD METHOD
Download this file - http://dl3.htc.com/application/RUU_..._2G_20.63.4196.01_release_394319_signed_2.exe (Mirror)
(STOCK RUU FOR UNLOCKED + DEVELOPER EDITION HTC ONE M8 [this is what you have now since you changed CID and MID])
CRC32: 79E8DE54
MD5: 5040B8D54D0ADA150531C66D899ABBE9
SHA-1: A1E39A089A23417DDF5A682BB6A23C9BDE77025B
Once it is downloaded, type the following commands
Code:
fastboot oem rebootRUU
flashing the RUU will most defintely wipe your internal sd (/data/media)
Run RUU_M8_UL_K444_SENSE60_MR_BrightstarUS_WWE_3.28.1540.5_Radio_1.21.21331147A1.19_2G_20.63.4196.01_release_394319_signed_2.exe and just press next/confirm etc. ignore the usb connection instructions
once that is done, the device will reboot and you will be able to check for updates and find the lollipop update.
OPTIONAL Zip file for the OTA https://docs.google.com/uc?id=0B0lhP19GCj8fVDNCeE9WZUI5ZTQ&export=download - Boot to stock recovery, press vol+ and vol- and power when at the triangle thingy, then select the zip
This method isn't the quickest if you are already on a compatible version but if your not then this will get you sorted, i spent multiple hours getting this sorted.
Credit for the mid/cid stuff goes to this thread http://forum.xda-developers.com/htc-one-m8/general/change-wwe-m8-to-dev-edition-ota-t2826567
ROOT: Either flash TWRP and let it do it's thing when u go to exit without root or flash a SuperSU Flashable ZIP!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
great guide! will this guide if altered [or not] work for cdma [Verizon] version working. thanks
Does this work if I converted to GPe earlier?
Just wanted to get one thing clear. If I have SuperCID, I don't need to change my CID to the one provided above, right?
Stupid question ahead: Will my data be whiped during the RUU flashing? Or will it just update it, with keeping everything in place. I just don't want to reinstall everything I am already S-Off and unlocked BL
mzrdisi said:
*nevermind*
Click to expand...
Click to collapse
OK
pavankvn said:
Does this work if I converted to GPe earlier?
Click to expand...
Click to collapse
I never tested on GPE device or GPE converted device sorry.
Jamal Ahmed said:
Just wanted to get one thing clear. If I have SuperCID, I don't need to change my CID to the one provided above, right?
Click to expand...
Click to collapse
Not sure try it if you want. it's not difficult to change it though.
Tilgi said:
Stupid question ahead: Will my data be whiped during the RUU flashing? Or will it just update it, with keeping everything in place. I just don't want to reinstall everything I am already S-Off and unlocked BL
Click to expand...
Click to collapse
I believe it will wipe all data including internal sd (atleast it did for me)
Not working, the Updater complains that the ID isn't a match, i updated it to the one you provided and it does NOT work.
---------- Post added at 03:02 PM ---------- Previous post was at 02:57 PM ----------
maxupp said:
Not working, the Updater complains that the ID isn't a match, i updated it to the one you provided and it does NOT work.
Click to expand...
Click to collapse
And another thing: Why do you link a Brightstar RUU? Shouldn't this be an unbranded RUU?
OP,
Please add big warning in your post about dangers of changing MID. You must specifically warn about not messing up any character in command line. :good::good:
09Ram said:
OP,
Please add big warning in your post about dangers of changing MID. You must specifically warn about not messing up any character in command line. :good::good:
Click to expand...
Click to collapse
And he should change it to Super CID to be on the safe side.
---------- Post added at 03:52 PM ---------- Previous post was at 03:35 PM ----------
Adding to my statement above:
Using the RUU posted in the OP, it is NOT possible to install the 5.0.1 update.
I just downloaded it and was informed that i cannot update because the OS has been modified.
Please remove this entire thread or update the OP to be correct.
No problem with OP, follow instructions and everything works like a charm. Wish I had known RUU's wipe internal memory though
Many, many thanks! It worked out just perfectly! There is the OTA notification, great
Well, ill try this on a different computer because after doing "fastboot oem rebootRUU", tried to run the exe file but nothing happened (it kinda installed but it closes without any warning or any confirmation) . Now im stuck at the bootloader only saying RUU. Any tips?
maxupp said:
Not working, the Updater complains that the ID isn't a match, i updated it to the one you provided and it does NOT work.
---------- Post added at 03:02 PM ---------- Previous post was at 02:57 PM ----------
And another thing: Why do you link a Brightstar RUU? Shouldn't this be an unbranded RUU?
Click to expand...
Click to collapse
Works perfectly fine, Obviously did something wrong. Brightstar RUU is unbranded. and only 1 i could find for Developer Edition.
09Ram said:
OP,
Please add big warning in your post about dangers of changing MID. You must specifically warn about not messing up any character in command line. :good::good:
Click to expand...
Click to collapse
Done!
maxupp said:
And he should change it to Super CID to be on the safe side.
---------- Post added at 03:52 PM ---------- Previous post was at 03:35 PM ----------
Adding to my statement above:
Using the RUU posted in the OP, it is NOT possible to install the 5.0.1 update.
I just downloaded it and was informed that i cannot update because the OS has been modified.
Please remove this entire thread or update the OP to be correct.
Click to expand...
Click to collapse
Super CID didn't work for me, Using the RUU in OP it work's fine, i did it myself and others confirmed it worked. Make sure you don't have a custom recovery and haven't modified the system. the screenshots in the 2nd post is from the RUU that is linked on OP the MID and CID from the OP aswell!
bazzi12 said:
No problem with OP, follow instructions and everything works like a charm. Wish I had known RUU's wipe internal memory though
Click to expand...
Click to collapse
Thanks, glad it worked, Added to OP about wiping RUU (although i did mention it in a previous post already). leave a press on the thanks if you haven't already
Tilgi said:
Many, many thanks! It worked out just perfectly! There is the OTA notification, great
Click to expand...
Click to collapse
Thanks, Glad it worked, leave a press on the thanks if you haven't already
--------------------
maxupp said:
Please remove this entire thread or update the OP to be correct.
Click to expand...
Click to collapse
ADDITIONALLY I AM NOT SOME NOOB ON XDA SO DON'T TREAT ME LIKE ONE AND INSTEAD RESPECT OTHER MEMBERS. DO NOT TELL ME WHAT TO DO! JUST CUZ IT DIDN'T WORK FOR YOU DOESN'T MEAN IT DOESN'T WORK FOR EVERYONE ELSE
diogoribeiro said:
Well, ill try this on a different computer because after doing "fastboot oem rebootRUU", tried to run the exe file but nothing happened (it kinda installed but it closes without any warning or any confirmation) . Now im stuck at the bootloader only saying RUU. Any tips?
Click to expand...
Click to collapse
disable anti-virus and run as admin. official HTC software so no risk of virus.
It worked fine for me.
Installed easily and took 5.0.1 OTA right after setup was complete.
Only problem I'm having now is that I am unable to boot TWRP through ADB to backup recovery.
After running cmd "fastboot boot TWRP.img" It downloads fine, then command says booting, but nothing happens and phone is stuck on bootloader screen. Any suggestions?
HBoot 3.19
I tried to follow your instructions and below was my result when i tried changing the MID to developer. I was on developer edition rom already, but i had the international MID. my phone is an AT&T variant. I changed MID's so x.xx.401.x stock rom would accept OTA's without a problem. i changed my MID back when i was on either 1.12 or 1.54 base, i dont remember. Now the OTA for 4.16 does not install. installing from android, it keeps saying download is corrupt. installing from recovery simply throws an unknown error. my guess is the MID being messed up. any information is greatly appreciated. in the meantime, im on 3.28 and the phone functions correctly for now at least.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.1540.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT********** [edited for obvious reasons]
(bootloader) imei: xxxxxxxxxxxxxxx [also edited]
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000n.satn tnwo ot53
amns
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
Click to expand...
Click to collapse
chevyjohn01 said:
It worked fine for me.
Installed easily and took 5.0.1 OTA right after setup was complete.
Only problem I'm having now is that I am unable to boot TWRP through ADB to backup recovery.
After running cmd "fastboot boot TWRP.img" It downloads fine, then command says booting, but nothing happens and phone is stuck on bootloader screen. Any suggestions?
Click to expand...
Click to collapse
you can't fastboot boot twrp any more you will need to fastboot flash recovery twrp.img
fma965 said:
disable anti-virus and run as admin. official HTC software so no risk of virus.
Click to expand...
Click to collapse
Well, couldnt make it work on this computer. Used another and everything went smothly, maybe i had a bad download or something on my computer was blocking the program from even starting. Thank you for your quick reply and for your amazing job i really appreciate it.
diogoribeiro said:
Well, couldnt make it work on this computer. Used another and everything went smothly, maybe i had a bad download or something on my computer was blocking the program from even starting. Thank you for your quick reply and for your amazing job i really appreciate it.
Click to expand...
Click to collapse
Great, glad you got it working hit the thanks button if you want
Hello, i have a problem flashing custom recovery TWRP on ZUI.
below are the details of the problems:
ZUI Version: 1.2.040
Unlock Bootloader: YES (I feel a bit sketch on this part, because the process does not wipe any data)
Custom recovery to be installed: Un-Official 2.8.7.0 TWRP Recovery for ZUK Z1 by Breadcrust
1. when i try to flash the recovery on fastboot mode, it gives me this:
writing 'recovery'...
FAILED (remote : Invalid data)
finished. total time" 0.418s
2. when i try boot the recovery on fastboot mode, it also gives error:
downloading 'boot.img'...
OKAY [0.362s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.369s
* For the solution, i have tried kingroot to allow root access ---> NOT SUCCESFULL
** For 2nd solution, i have tried downgrading the ZUI version ----> NOT SUCCESFULL (cannot get into qdloader mode long enough).
*** I also have tried re-downloading the recovery image without using download accelarator (IDM) ---> NOT SUCCESFULL
edit: please... if somebody know the problem, please teach me how to overcome the problem. thank you (* sorry bad english)
Unlock your bootloader and retry.
Already retried to unlock the bootloader.. But no luck.. Thanks for the tips btw
I have found the solution.. I will post it in the weekend
luqmanhans said:
I have found the solution.. I will post it in the weekend
Click to expand...
Click to collapse
when u post please tell my in the praivte
[email protected]
Kingroot worked for me bit only after the second try
Tengo10 said:
Kingroot worked for me bit only after the second try
Click to expand...
Click to collapse
can u explain me please how u do it with king root??
eyalyagel said:
can u explain me please how u do it with king root??
Click to expand...
Click to collapse
I coud've offered more direct support if you messaged me or replied to my thread.
Have you found any solution?
Breadcrust said:
I coud've offered more direct support if you messaged me or replied to my thread.
Click to expand...
Click to collapse
can u give me please the link or explain may the way????
thank u very much
eyalyagel said:
can u give me please the link or explain may the way????
thank u very much
Click to expand...
Click to collapse
Did you do fastboot -i ox2b4c oem unlock?
Breadcrust said:
Did you do fastboot -i ox2b4c oem unlock?
Click to expand...
Click to collapse
yes,
FAILED (remote: Oem unlock is not support)
finished. total time: 0.008s
and i allow the oem in the developer option....
also i have the same phone in my home but the difrrent bitween them:
1. have only home press in the bottom
the ather phone have home, back,manu, bottom this phone can be unlocked and i sucsses to instal twrp
I have the same problem like it desribed by the OP.
I have the chinese version of the ZUK.
The Bootloader seems to be unlocked. When i check it, it says Unlocked: true.
When i did the Unlock, it didnt wipe something. When I do the unlock, it says ok, but there is no reboot.
But somehow, i cant boot or flash a recovery. Every time I have the error, Invalid data or not signed.
Root does also not work.
I have the latest version of ZUI installed. Is this the problem?
I read the problem several times, but nobody posted a solution for this.
xnoobx said:
I have the same problem like it desribed by the OP.
I have the chinese version of the ZUK.
The Bootloader seems to be unlocked. When i check it, it says Unlocked: true.
When i did the Unlock, it didnt wipe something. When I do the unlock, it says ok, but there is no reboot.
But somehow, i cant boot or flash a recovery. Every time I have the error, Invalid data or not signed.
Root does also not work.
I have the latest version of ZUI installed. Is this the problem?
I read the problem several times, but nobody posted a solution for this.
Click to expand...
Click to collapse
I'm also facing the same problem with my ZUK Z1
ZUI 1.2 locked the bootloader.If the TWRP recovery image file is twrp.img,You can try to do these:
Code:
fastboot -i 0x2b4c boot twrp.img
then you will boot into a temporary TWRP recovery.Now you can do everything here utill it reboots or shutdown.
if you want to flash a permanent recovery, I suggest to you to convert your ZUI to COS.
hfutxqd said:
ZUI 1.2 locked the bootloader.If the TWRP recovery image file is twrp.img,You can try to do these:
Code:
fastboot -i 0x2b4c boot twrp.img
then you will boot into a temporary TWRP recovery.Now you can do everything here utill it reboots or shutdown.
if you want to flash a permanent recovery, I suggest to you to convert your ZUI to COS.
Click to expand...
Click to collapse
Dear
I was using CM12 new version till last week and i have lots of problems, specially with mobile signal during the calls voice is dropping signal is too week as well. So i have decided to move to ZUI version and it's perfect so far i'm not facing any problem. Only the vulnerable is there some kind of malware and GPS having some bugs i have checked with bbs.zuk forms and they are suppose to fix it with next update. so i was trying to install the stagefright fix via recovery.remaining everything is smooth and faster than CM12.
hfutxqd said:
ZUI 1.2 locked the bootloader.If the TWRP recovery image file is twrp.img,You can try to do these:
Code:
fastboot -i 0x2b4c boot twrp.img
then you will boot into a temporary TWRP recovery.Now you can do everything here utill it reboots or shutdown.
if you want to flash a permanent recovery, I suggest to you to convert your ZUI to COS.
Click to expand...
Click to collapse
I also tried to boot. But it also denies this action :/.
So with the latest version my boot loader is locked. Sounds wonderful.
luqmanhans said:
Hello, i have a problem flashing custom recovery TWRP on ZUI.
below are the details of the problems:
ZUI Version: 1.2.040
Unlock Bootloader: YES (I feel a bit sketch on this part, because the process does not wipe any data)
Custom recovery to be installed: Un-Official 2.8.7.0 TWRP Recovery for ZUK Z1 by Breadcrust
1. when i try to flash the recovery on fastboot mode, it gives me this:
writing 'recovery'...
FAILED (remote : Invalid data)
finished. total time" 0.418s
2. when i try boot the recovery on fastboot mode, it also gives error:
downloading 'boot.img'...
OKAY [0.362s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.369s
* For the solution, i have tried kingroot to allow root access ---> NOT SUCCESFULL
** For 2nd solution, i have tried downgrading the ZUI version ----> NOT SUCCESFULL (cannot get into qdloader mode long enough).
*** I also have tried re-downloading the recovery image without using download accelarator (IDM) ---> NOT SUCCESFULL
edit: please... if somebody know the problem, please teach me how to overcome the problem. thank you (* sorry bad english)
Click to expand...
Click to collapse
In this case, you need flash fw Z1_CN_OPEN_USER_Q4275715.1_L_ZUI_1.0.050_ST_150910 via sd card ( root internal memory/creat sdfuse folder), after turn off fone and boot phone via factory mode recovery ( voulme down + power ). If phone flash ok, version is 1.0.050. So, phone can flash twrp recovery and rom CyanogenMod 12.1 .
Goodluck
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
luqmanhans said:
I have found the solution.. I will post it in the weekend
Click to expand...
Click to collapse
It is weekend now.
Can you please tell us the solution? I have the same problem & I have tried a lot of things with no luck!!! :crying:
hristos13gr said:
It is weekend now.
Can you please tell us the solution? I have the same problem & I have tried a lot of things with no luck!!! :crying:
Click to expand...
Click to collapse
First you must downgrade the ZUI from 1.2.040, just search this topic in this forum: how-to-flash-zuk-z1-zui-version-t3265741
After that you can boot with TWRP recovery. But if you failed to flash Cyanogen, use Modaco steps: 375804-convert-z1-from-zukui-to-cyanogen-os/
When your ZUK Z1 already use Cyanogen, you can flash to other recovery or ROMs easier .
First, Unlock Bootloader
Install TWRP for Le X626
Download Magisk or SuperSU
Put Magisk or SuperSU in internal storage
Reboot to TWRP
Install from zip
Choose Magisk (Recommended) or SuperSU
Reboot
source : tickernel.tk
Can you please post something similar for rooting Le2 X526 model?
I would like to install Magisk instead of supersu as I have heard the former is better.
How to install TWRP for x626 according to the site the OP recommends.
From the same website, only without the adlinks. No guarantees from me, if you go through the instructions from the OP you will end up getting the same information.
– Make sure your Bootloader is Unlocked, if you don’t know how to Unlock the Bootloader then please go to here and Unlock the Bootloader of your Device.
– Download the Latest TWRP Recovery Image from https://dbr.ee/TKKC
– Reboot into Fastboot/Bootloader Mode.
– Run The Following Command from a Command Prompt in the Same Folder in which you downloaded the TWRP Recovery Image (Change twrp le x626.img to recovery.img):
fastboot flash recovery recovery.img
fastboot boot recovery.img
Click to expand...
Click to collapse
onlytanmoy said:
Can you please post something similar for rooting Le2 X526 model?
I would like to install Magisk instead of supersu as I have heard the former is better.
Click to expand...
Click to collapse
I can't, because it's have different chipset
okay, thanks for your response and clarification...cheers to that.
Hello,
I followed the instructions but I get this error message while install twrp, anyone have any ideas please?
C:\Users\Administrator\Downloads\fastboot>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending ‘recovery’ (20480 KB)…
OKAY [ 9.809s]
writing ‘recovery’…
(bootloader) Fastboot oem devices is lock
(bootloader) Start unlock flow
(bootloader) Unlock Pass…continue to fastboot
OKAY [ 36.298s]
finished. total time: 53.258s
C:\Users\Administrator\Downloads\fastboot>fastboot boot recovery.img
downloading ‘boot.img’…
OKAY [ 7.198s]
booting…
(bootloader) Fastboot oem devices is unlock
(bootloader) Fastboot oem devices is unlock
(bootloader) Start lock flow
(bootloader) Lock Pass…continue to fastboot
FAILED (status read failed (Invalid argument))
finished. total time: 40.336s
C:\Users\Administrator\Downloads\fastboot>
tomfoley said:
Hello,
I followed the instructions but I get this error message while install twrp, anyone have any ideas please?
C:\Users\Administrator\Downloads\fastboot>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending ‘recovery’ (20480 KB)…
OKAY [ 9.809s]
writing ‘recovery’…
(bootloader) Fastboot oem devices is lock
(bootloader) Start unlock flow
(bootloader) Unlock Pass…continue to fastboot
OKAY [ 36.298s]
finished. total time: 53.258s
C:\Users\Administrator\Downloads\fastboot>fastboot boot recovery.img
downloading ‘boot.img’…
OKAY [ 7.198s]
booting…
(bootloader) Fastboot oem devices is unlock
(bootloader) Fastboot oem devices is unlock
(bootloader) Start lock flow
(bootloader) Lock Pass…continue to fastboot
FAILED (status read failed (Invalid argument))
finished. total time: 40.336s
C:\Users\Administrator\Downloads\fastboot>
Click to expand...
Click to collapse
Unlock bootloader first
What rom do u use?
Hi Tickernel, and thank you for replying
I unlocked the bootloader as per Step 1 above and that completed successfully.
Moving on to Step 2 I got the recovery image following your links which led me to 'twrp le x626.img' (20MB), which I renamed to recovery.img.
There are two commands to execute in step 2, the first went ok, the second did not succeed
tickernel said:
Unlock bootloader first
What rom do u use?
Click to expand...
Click to collapse
Please see screenshot...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
tickernel said:
Unlock bootloader first
What rom do u use?
Click to expand...
Click to collapse
tomfoley said:
Please see screenshot...
Click to expand...
Click to collapse
Have u tried boot to recovery?
Press vol up + power
Hi again Tickernel and thank you for your patience
I haven't tried boot to recovery, what would I need to do exactly? I'd need an update.zip file right? Any one in particular??
tomfoley said:
Hi again Tickernel and thank you for your patience
I haven't tried boot to recovery, what would I need to do exactly? I'd need an update.zip file right? Any one in particular??
Click to expand...
Click to collapse
After you flash the twrp, then boot into recovery by pressing vol up + power
You don't need update.zip
Hi Tickernel, so you're suggesting recovery in the sense of a total erasing of all apps and data? I'm willing to do it, but will make certain I have a backup first . Just want to confirm that this is what you think needs to be done.
tomfoley said:
Hi Tickernel, so you're suggesting recovery in the sense of a total erasing of all apps and data? I'm willing to do it, but will make certain I have a backup first . Just want to confirm that this is what you think needs to be done.
Click to expand...
Click to collapse
I'm not suggesting to erase all your data, i'm just suggesting after you flash the twrp but don't straight go to recovery then press vol up + power. That's it
Glad I asked My issue is it will not flash TWRP. It fails on the step 'fastboot boot recovery.img'
tomfoley said:
Glad I asked My issue is it will not flash TWRP. It fails on the step 'fastboot boot recovery.img'
Click to expand...
Click to collapse
Command 'fastboot boot recovery.img' is going boot to twrp. If you fail to do that, then just press vol up + power
Progress!! I switched to loading TWRP from a Windows OS to a Linux one and Fastboot completed without error. I have yet to complete the remainder of the steps but will do as soon as I get a chance. I'll report back. Thanks again Tickernel, looking forward to having a rooted device soon !
tomfoley said:
Progress!! I switched to loading TWRP from a Windows OS to a Linux one and Fastboot completed without error. I have yet to complete the remainder of the steps but will do as soon as I get a chance. I'll report back. Thanks again Tickernel, looking forward to having a rooted device soon !
Click to expand...
Click to collapse
Yeah, you're welcome
Don't suppose kingroot or similar works? I'm very lazy lol
I also have this problem were it fails in "fastboot boot recovery.img" but not in commanding "fastboot flash recovery recovery.img"
what to do?? :crying:
thanks for the help
Hi my name is Akul and i have a moto g5 plus aka potter my phone was hard bricked and i used blank flash to recover its bootloader mode then i started flashing stock rom through bootloader mode it even got flashed but it is not booting up it is stuck on the first logo and it is kind of stuck in the bootloop then i tried to flash custom recovery like twrp(btw no recovery mode was opening before) even it got flashed but it is not booting into it. I am stuck with a fastboot mode with nothing getting flashed into it and it is so frustrating. Please somebody help me. Please.
Akul Gaind said:
Hi my name is Akul and i have a moto g5 plus aka potter my phone was hard bricked and i used blank flash to recover its bootloader mode then i started flashing stock rom through bootloader mode it even got flashed but it is not booting up it is stuck on the first logo and it is kind of stuck in the bootloop then i tried to flash custom recovery like twrp(btw no recovery mode was opening before) even it got flashed but it is not booting into it. I am stuck with a fastboot mode with nothing getting flashed into it and it is so frustrating. Please somebody help me. Please.
Click to expand...
Click to collapse
What is the bootloader version?
riyan65 said:
What is the bootloader version?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
????
riyan65 said:
What is the bootloader version?
Click to expand...
Click to collapse
I am writing what is displaying on the bootloader screen
AP Fastboot Flash Mode (Secure)
BL: C0.C5 (sha-aa1c1, 2017-04-01 21:52:26)
Baseband: M8953_8000.128.06.42e POTTER_INDIADSDS_CUST
Product/Variant: potter XT1686 32GB P3B
Serial Number: ZY223V9R3G
CPU: MSM8953
eMMC: 32GB SAMSUNG RX14MB RV=08 PV=07 FV=0000000000000007
DRAM: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
Console [NULL]: null
Tools Mode Config: Disabled
flashing_unlocked
Software status: Official
Connect USB Data Cable
Akul Gaind said:
I am writing what is displaying on the bootloader screen
AP Fastboot Flash Mode (Secure)
BL: C0.C5 (sha-aa1c1, 2017-04-01 21:52:26)
Baseband: M8953_8000.128.06.42e POTTER_INDIADSDS_CUST
Product/Variant: potter XT1686 32GB P3B
Serial Number: ZY223V9R3G
CPU: MSM8953
eMMC: 32GB SAMSUNG RX14MB RV=08 PV=07 FV=0000000000000007
DRAM: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
Console [NULL]: null
Tools Mode Config: Disabled
flashing_unlocked
Software status: Official
Connect USB Data Cable
Click to expand...
Click to collapse
What does it give if you flash anything??? Recovery,boot,logo.....
riyan65 said:
What does it give if you flash anything??? Recovery,boot,logo.....
Click to expand...
Click to collapse
Nothing but the screen which shows bootloader is unlocked and your phone cannot be trusted it always appear when you start the phone or go to recovery before and nothing goes ahead of it. Please help me faster as it is a brick nothing else.
Akul Gaind said:
Nothing but the screen which shows bootloader is unlocked and your phone cannot be trusted it always appear when you start the phone or go to recovery before and nothing goes ahead of it. Please help me faster as it is a brick nothing else.
Click to expand...
Click to collapse
I mean in pc what does it give when you flash recovery,boot....
riyan65 said:
I mean in pc what does it give when you flash recovery,boot....
Click to expand...
Click to collapse
It shhows that it is flashed successfully.
Akul Gaind said:
It shhows that it is flashed successfully.
Click to expand...
Click to collapse
Sorry for late reply, could you post the getvar.
Command:- fastboot getvar all
And your device bootloader is nougat not oreo try flashing oreo bootloader and then recovery,boot... If it still didn't work then post getvar.
riyan65 said:
Sorry for late reply, could you post the getvar.
Command:- fastboot getvar all
And your device bootloader is nougat not oreo try flashing oreo bootloader and then recovery,boot... If it still didn't work then post getvar.
Click to expand...
Click to collapse
How to flash oreo bootloader?
Akul Gaind said:
How to flash oreo bootloader?
Click to expand...
Click to collapse
Here is the thread to flash stock oreo:-https://forum.xda-developers.com/g5...stboot-flash-stock-oreo-t3848433/post77752702
You can get the latest oreo firmware from here:-
https://mirrors.lolinet.com/firmware/moto/potter/official/
Didn't work
riyan65 said:
Here is the thread to flash stock oreo:-https://forum.xda-developers.com/g5...stboot-flash-stock-oreo-t3848433/post77752702
You can get the latest oreo firmware from here:-
https://mirrors.lolinet.com/firmware/moto/potter/official/
Click to expand...
Click to collapse
Tried this. My phone has the same problem as he described. Its still in bootloop and the device is recognised in my PC as " fastboot potter S".
Zangruver said:
Tried this. My phone has the same problem as he described. Its still in bootloop and the device is recognised in my PC as " fastboot potter S".
Click to expand...
Click to collapse
Didn't you try the above method?
riyan65 said:
Didn't you try the above method?
Click to expand...
Click to collapse
Ya I did. Nothing changed.
Zangruver said:
Ya I did. Nothing changed.
Click to expand...
Click to collapse
What does it give?
riyan65 said:
Sorry for late reply, could you post the getvar.
Command:- fastboot getvar all
And your device bootloader is nougat not oreo try flashing oreo bootloader and then recovery,boot... If it still didn't work then post getvar.
Click to expand...
Click to collapse
Nothing changed can you tell me a new method
Akul Gaind said:
Nothing changed can you tell me a new method
Click to expand...
Click to collapse
You can use lenovo moto smart assistant app to flash it.
riyan65 said:
You can use lenovo moto smart assistant app to flash it.
Click to expand...
Click to collapse
already done before
riyan65 said:
What does it give?
Click to expand...
Click to collapse
He was asking you to post the results from
run
Code:
fastboot getvar all
Product = codename
securestate = bootloader locked or unlocked
carrier_sku = Model #
ro.carrier = Software Channel
Please post it here after you remove the IMEI line
Sent from my ali using XDA Labs