Related
Hi everyone
Yesterday I've installed Android 6.0. Tesla ROM after downgrading to Stock Android 5.1. (Stock 6.0. was slow as hell)
When I was beginning to install Android 5.1. stock fastboot had said that it cant install gpt.bin file. I've read that it's possible to do the install without it. Restarting or turning on after completely successful install it shows every time the bootloader and I always have to press START. I've decided to install Tesla ROM thinking it will fix that. But the problem remains still. I've tried to re-lock my bootloader but it says Please fully flash the signed build before locking phone. What do I have to do now to fix it? Thanks in advance
Check your phone box, there is a sticker that should say "XT 1541 retXX" so you know wich region is right for your phone, then download the fw from the filefacory repo http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=50 and flash it whit mfastbootV2
PS
Your phone have a dedicated section --> http://forum.xda-developers.com/2015-moto-g
edrpomidor said:
Hi everyone
Yesterday I've installed Android 6.0. Tesla ROM after downgrading to Stock Android 5.1. (Stock 6.0. was slow as hell)
When I was beginning to install Android 5.1. stock fastboot had said that it cant install gpt.bin file. I've read that it's possible to do the install without it. Restarting or turning on after completely successful install it shows every time the bootloader and I always have to press START. I've decided to install Tesla ROM thinking it will fix that. But the problem remains still. I've tried to re-lock my bootloader but it says Please fully flash the signed build before locking phone. What do I have to do now to fix it? Thanks in advance
Click to expand...
Click to collapse
Use mfastboot v2, and try to flash a 5.1 firmware from the same region (if your phone was from Latin America use retLA, if it's from asia use retasia, for the US use retUS, etc.)
benjausen said:
Use mfastboot v2, and try to flash a firmware FROM THE SAME REGION. Did you change motoboot.img? If so then skip 5.X gpt.bin and motoboot.img flashing.
Click to expand...
Click to collapse
No I didn't
deleted
benjausen said:
Use mfastboot v2, and try to flash a 5.1 firmware from the same region (if your phone was from Latin America use retLA, if it's from asia use retasia, for the US use retUS, etc.)
Click to expand...
Click to collapse
I've done everything you said (gpt.bin has been installed!), showing of bootloader is gone.
But the problem with blocking of bootloader exist yet... However, thanks
C:\Users\\Desktop\ADB and Fastboot>fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.047s]
finished. total time: 0.052s
C:\Users\\Desktop\ADB and Fastboot>fastboot oem lock begin
...
(bootloader) Please fully flash the signed build before locking phone!
OKAY [ 0.015s]
finished. total time: 0.017s
or in mfastboot-v2
C:\Users\\Desktop\Новая папка>mfastboot oem lock begin
...
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.020s
C:\Users\\Desktop\Новая папка>mfastboot oem lock
...
(bootloader) Please flash valid signed images just after lock begin
(bootloader) command!
OKAY [ 0.032s]
finished. total time: 0.035s
edrpomidor said:
I've done everything you said (gpt.bin has been installed!), showing of bootloader is gone.
But the problem with blocking of bootloader exist yet... However, thanks
C:\Users\\Desktop\ADB and Fastboot>fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.047s]
finished. total time: 0.052s
C:\Users\\Desktop\ADB and Fastboot>fastboot oem lock begin
...
(bootloader) Please fully flash the signed build before locking phone!
OKAY [ 0.015s]
finished. total time: 0.017s
or in mfastboot-v2
C:\Users\\Desktop\Новая папка>mfastboot oem lock begin
...
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.020s
C:\Users\\Desktop\Новая папка>mfastboot oem lock
...
(bootloader) Please flash valid signed images just after lock begin
(bootloader) command!
OKAY [ 0.032s]
finished. total time: 0.035s
Click to expand...
Click to collapse
Try to flash a 6.0 firmware for your region after the lock. Might not be the best, but at least you will have a working phone. It seems you relocked it, so you won't be able to use other images or to root and install custom ROMS. My XT1072 runs 6.0.1 CM13 and the touchscreen is lagged plus a reduced gaming perfomance, but the phone works.
benjausen said:
Try to flash a 6.0 firmware for your region after the lock. Might not be the best, but at least you will have a working phone. It seems you relocked it, so you won't be able to use other images or to root and install custom ROMS. My XT1072 runs 6.0.1 CM13 and the touchscreen is lagged plus a reduced gaming perfomance, but the phone works.
Click to expand...
Click to collapse
Now I have stock Android 6.0.1 RETEU XT1541, working phone with unlocked bootloader, so if I want, I can flash other ROMs.
edrpomidor said:
Now I have stock Android 6.0.1 RETEU XT1541, working phone with unlocked bootloader, so if I want, I can flash other ROMs.
Click to expand...
Click to collapse
Try flashing CM12.1 then.
Install TWRP recovery
First of all, the phone must be bootloader unlocked, if you didn't do that please unlock the bootloader first, you can find many guide for that.
https://www.htcdev.com/bootloader/
And one thing, there is a switch called "OEM Unlock" in developer options menu, make it turn on or you will fail to get unlock token.
Now you have a bootloader unlocked device right?
Please download this TWRP recovery
https://twrp.me/htc/htcdesire10lifestyle.html
Let phone reboot to bootloader and switch to fastboot mode then use the command to boot the recovery.
(Temporary)
Code:
fastboot boot twrp-3.2.1-0-a56dj.img
If you want install TWRP as main recovery please use the command
Code:
fastboot flash recovery twrp-3.2.1-0-a56dj.img
Okay, If everything are work in right way, your device should be in TWRP recovery, you can do everything you want.
I recommend to use Magisk to get root :good:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
can you help me. i cant unlock the bootloader cos the command is not working getting this message
M:\HTCRoot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.042s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/platform/mtk-msdc.0/11230000.msdc
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 0.132s
need help guys..
I am really tired, its been a month, tried every possible combination of unlock codes but this device bootloader is not going to be unlocked. Tried on 03 different PC's.
Any help will be appreciated.
Below is the log
PS D:\Cell Phones\HTC> fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1602400000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.006s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/platform/mtk-msdc.0/11230000.msdc
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.033s
Haroon_ said:
I am really tired, its been a month, tried every possible combination of unlock codes but this device bootloader is not going to be unlocked. Tried on 03 different PC's.
Any help will be appreciated.
Below is the log
PS D:\Cell Phones\HTC> fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1602400000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.006s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/platform/mtk-msdc.0/11230000.msdc
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.033s
Click to expand...
Click to collapse
U didnt swiched on "OEM Unlock" in developer options menu, turn it on or it will fail to flash the unlock token.
after i unlocked bootoader.....
I cann't Enter to fastboot or bootloader by pressing on volume down + turn on or volume up + turn on while my device turned off
I have broken the bootloader lock but i couldn't root my htc lifestyle
please please developers.... i want to root my device to be able to setup new version of android after 6.0.1
If you know the couse help me plz
I am waiting ... bro
Hi OP,
The link given for TWRP recovery is not working ; "404 not found' is shown.
Plz help.
Eversmile23 said:
Hi OP,
The link given for TWRP recovery is not working ; "404 not found' is shown.
Plz help.
Click to expand...
Click to collapse
I've made desire 10 lifestyle officially supported on TWRP website, download TWRP recovery here.
https://twrp.me/htc/htcdesire10lifestyle.html
a56dj?
sabpprook said:
I've made desire 10 lifestyle officially supported on TWRP website, download TWRP recovery here.
https://twrp.me/htc/htcdesire10lifestyle.html
Click to expand...
Click to collapse
Thank you very much for letting me get the required link. I just wanted to know what is 'a56dj', is it the code for HTC Desire 10 Lifestyle? How can I get stock boot image for my device, which I think is required while using "magisk" to get root?
Prasanna
adb can help.
tyten said:
I cann't Enter to fastboot or bootloader by pressing on volume down + turn on or volume up + turn on while my device turned off
I have broken the bootloader lock but i couldn't root my htc lifestyle
please please developers.... i want to root my device to be able to setup new version of android after 6.0.1
If you know the couse help me plz
I am waiting ... bro
Click to expand...
Click to collapse
If you know adb, then you can connect your device to the PC/Laptop and use the command ' adb reboot-bootloader' to get into fastboot mode. I am also trying to root my device. I will flash 'twrp' and then see what I can do for rooting. But, I have to be careful. I must be able to flash stock recovery.
Getting error in flashing TWRP.
Hi Op,
The command 'fastboot flash twrp-3.2.1-0-a56dj.img' is not working on my device in fastboot mode. It says ' unknown partition twrp-3.2.1-0-a56dj.img' in the second line it says : can not determine image filename for 'twrp-3.2.1-0-a56dj.img'. But I tested the same '.img' file by booting into the TWRP recovery on my mobile through the 'fastboot boot ................... ' command. What is the cause of the error. Plz help.
Eversmile23 said:
Hi Op,
The command 'fastboot flash twrp-3.2.1-0-a56dj.img' is not working on my device in fastboot mode. It says ' unknown partition twrp-3.2.1-0-a56dj.img'......
Click to expand...
Click to collapse
oops, the command to flash recovery is missing partition name, try this please.
Code:
fastboot flash recovery <image>
sabpprook said:
I've made desire 10 lifestyle officially supported on TWRP website, download TWRP recovery here.
https://twrp.me/htc/htcdesire10lifestyle.html
Click to expand...
Click to collapse
Much appreciated, works perfect where the older test versions were having touch issues or at least for me a56dj-dugl
Hi OP,
I am really happy as I could gain root access on my HTC through your valuable guidance.
Help required for busybox.
Hi OP,
Can you guide me to any forum/tutorial for dealing with problems in installing busybox ? Busybox installation fails repeatedly on my device -- through 'busybox installer' & flashing zip file through recovery-- both not successful. Is it because SeLinux enforcing? Do I have to go for S-Off, then only I can install busybox? Plz help.
Sir I have HTC desire 10 compact
I have to flash custom recovery
Plzz help me
HTC Desire!0 LifeStyle Very Bad phone No more Update OS for Last TWO years
That TWRP (twrp-3.2.3-0-a56dj.img) file can't be mounted or is not valid.
Hi, does anybody know working custom rom for HTC Desire 10 Lifestyle? Thanks
Hi all,
I'm trying to understand what did I do wrong.
I bought my device with an unlocked bootloader miui V8 (global rom).
I tried to flash TWRP recovey and MIUI PRO rom. I follow the steps that are mentioned here
and got soft brick - the device got stuck on the mi logo (with the unlock sign), even when I wait in patience the device just turned off.
- At the beginning I flashed the TWRP recovery by xuefer, boot into it and flashed the dm-verity disabler (as mentioned in the guide) and got error 1.
I reboot the device and it didn't boot.
- I boot to the recovery again and wipe the data - didn't boot.
Boot to recovery again and wipe to factory
-I flashed the MIUI PRO rom and the device still didn't boot.
I tired to flash the TWRP recovery by iscle - now the dm-verity disabler succeed but the device still didn't boot.
made the wiping steps as above again - and the device still got stuck at the mi logo.
At any step I manged to boot into the TWRP recovery and fastboot mode.
My lest option was to go back to the global stock rom using MiFlash
Now I'm on Global MIUI 9 with locked bootloadr
What did I do wrong?
I want to unlock the bootloader and to get back my control on my device.
Please advice
Thanks
Download the latest TWRP on this forum. Flash it. After, go to twrp, wipe data, cache, flash MIUI PRO rom, and after flash also flash the latest SuperSU zip. Then try again and see if it's gonna boot up.
how sure were you that the device had an unlocked bootloader when you purchased it? if it was brand new, certainly its bootloader is locked.
Do you have an open padlock when your phone is booting ?
Remember to boot to twrp just after flashing and before booting to the rom.
Thank you all for your answers!
Thank you all for your answers!
ekin_strops said:
Download the latest TWRP on this forum. Flash it. After, go to twrp, wipe data, cache, flash MIUI PRO rom, and after flash also flash the latest SuperSU zip. Then try again and see if it's gonna boot up.
Click to expand...
Click to collapse
This is exectly what I've done. and I't didn't worked.
Can you please point me to exact TWRP that you meant?
What about the dm-verity disabler ? it isn't necessary?
ondoy1943 said:
how sure were you that the device had an unlocked bootloader when you purchased it? if it was brand new, certainly its bootloader is locked.
Click to expand...
Click to collapse
I've checked the bootloader status in the Dev menu and with fastboot (fastboot oem device-info).
In addtion to all I had the open padlock sign when the turned on the device.
lightman33 said:
Do you have an open padlock when your phone is booting ?
Remember to boot to twrp just after flashing and before booting to the rom.
Click to expand...
Click to collapse
I had the open padlock sign.
Now unfortunately I flashed with MiFlash the global rom and my bootloader is locked.
I want to know the mistake I've done - so I don't fail with it again after I'll get the approval to open my bootloader.
Thanks
no mistake, they are three batches files in the rom zip. One of them is relocking the bootloader.
Flash_all with without erase data
Flash_all with wipe data
Flash_all with relock bootloader
I don't know miflash interface but you unfortunately choose the third choice. You need now to unlock your bootloader again (maybe by creating a new xiaomi account, not sure of this).
lightman33 said:
no mistake, they are three batches files in the rom zip. One of them is relocking the bootloader.
Flash_all with without erase data
Flash_all with wipe data
Flash_all with relock bootloader
I don't know miflash interface but you unfortunately choose the third choice. You need now to unlock your bootloader again (maybe by creating a new xiaomi account, not sure of this).
Click to expand...
Click to collapse
I'm sorry if you miss understood me, but I meant to the mistake I've made with the TWERP and rom flashing.
I can't figured out what I've did wrong.
Sorry if was not clear but the problem could be here :
Now unfortunately I flashed with MiFlash the global rom and my bootloader is locked.
II think you choose in Mi Flash tool an option to flash with re-lock the bootloader (don"t know how it's designed in the app because I flashed my phone manually, using one of the 3 batch files).
Hope it will help you.
lightman33 said:
Sorry if was not clear but the problem could be here :
Now unfortunately I flashed with MiFlash the global rom and my bootloader is locked.
II think you choose in Mi Flash tool an option to flash with re-lock the bootloader (don"t know how it's designed in the app because I flashed my phone manually, using one of the 3 batch files).
Hope it will help you.
Click to expand...
Click to collapse
Thank you for your answer.
I will open my bootloader,
I'm just trying to understand which TWRP version to flash for the miui pro rom (or any other)
And what is the process (or "the correct steps") to :
* Flash the TWRP recovery
* And to flash any other different rom from the miui stock.
Thanks
I took the TWRP from this forum, this is my md5 if you want to check yours :
f52ff052971b67df097d4cfa8a2ec162 twrp-3.2.0-0-oxygen.img
And this is my howto :
$ sudo fastboot flash recovery twrp-3.2.0-0-oxygen.img
target reported max download size of 536870912 bytes
sending 'recovery' (16196 KB)...
OKAY [ 0.504s]
writing 'recovery'...
OKAY [ 0.095s]
finished. total time: 0.600s
$ sudo fastboot boot twrp-3.2.0-0-oxygen.img
downloading 'boot.img'...
OKAY [ 0.487s]
booting...
OKAY [ 0.576s]
finished. total time: 1.063s
For the ROM, I took file here : http://bigota.d.miui.com/7.12.8/oxy....8_20171208.0000.00_7.1_global_93a8045184.tgz
Filename : oxygen_global_images_7.12.8_20171208.0000.00_7.1_global_93a8045184
From forum : http://en.miui.com/thread-1273027-1-1.html
and the command to flash was (after unzip the file) :
$ sudo ./flash_all_except_storage.sh
Beginning of the log :
product: oxygen
erasing 'boot'...
OKAY [ 0.027s]
finished. total time: 0.027s
erasing 'sec'...
OKAY [ 0.021s]
finished. total time: 0.021s
target reported max download size of 536870912 bytes
sending 'crclist' (0 KB)...
OKAY [ 0.040s]
writing 'crclist'...
OKAY [ 0.020s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'sparsecrclist' (0 KB)...
OKAY [ 0.040s]
writing 'sparsecrclist'...
Hope it will help you...
ymca said:
Thank you for your answer.
I will open my bootloader,
I'm just trying to understand which TWRP version to flash for the miui pro rom (or any other)
And what is the process (or "the correct steps") to :
* Flash the TWRP recovery
* And to flash any other different rom from the miui stock.
Thanks
Click to expand...
Click to collapse
Hi! As others have already told you,
What I would do is to completely format the phone with Mi Flash (download the latest global stable fastboot version from http://en.miui.com/a-234.html), then flash it to the phone using the Flash All option, then flash my recovery or the one from xuefer (the one you prefer, both work), if you are flashing miui pro I think there is no need to flash the dm-verity file, so just wipe system + data + cache and flash miuipro.zip
Thank you all for your replais !
I will try and update right after I'll get the bootloader unlock approval.
Meanwhile you all have a great day !
Hello. So, I got my Moto G5s Plus around the last week of October or beginning of November. It is a great device, but I learned about the camera flaws by Motorola and unlocked the bootloader to fix it by following this XDA thread here for camera fixing and the Chromatix mod. I learned that I could edit build.prop without flashing the TWRP recovery but using it temporarily following the guide here. build.prop edit would enable cam2api for third party cam apps. The Chromatix mod threads/posts were for the G5 Plus, which I didn't realize at the time and didn't backup original Chromatix files. However, That went successfully and I could still use my phone with better camera quality. Note that prior to doing this fix and before unlocking the bootloader (I believe) I had updated my device from Nougat to Oreo. My bootloader is indeed unlocked.
Now, when the 1 October OTA Update came I was hesitent because I had came across some rooting/custom rom/custom recovery/mod articles while learning about unlocking the bootloader. Yet and before reading more to get educated on this, I applied the update to my phone. I was hoping it wouldn't brick it or that it would fail if it didn't work. It failed (because of the modification on the stock ROM) at the last bit of the update and rebooted my phone. My phone worked and it let me know nothing was changed by the failed update. However, my phone since then has shown as if it is up-to-date in system updates.
So, basically I have been trying to flash TWRP for my Moto G5s Plus after that was done. I want to see about backing up my stock ROM (or the most important parts) possibly getting a good custom ROM installed (which I believe they have their own official Android security updates from Google?). However flashing TWRP hasn't worked. I get the following in PowerShell (cmd):
PS C:\Android SDK\platform-tools> fastboot flash recovery twrp.img
Sending 'recovery' (10236 KB) OKAY [ 0.407s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.172s]
Finished. Total time: 0.594s
Note that I renamed twrp-3.1.1-sanders.img to twrp.img as it was a suggestion I followed at the time. This I heard is normal, but when I go to Recovery Mode on my phone I see this:
Start Up Failed:
Repair message stuff
AP Fastboot Flash Mode (Secure)
Fastboot Reason: UTAG *bootmode* configured as fastboot
~~~
Error: failed to load kernel!
~~~
I also tried to find the latest stock ROM to flash because I believe I read I may need to do that. I found SANDERS_RETAIL_8.1.0_OPSS28.65-36-3_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and tried to use "Apply update from ADB" from the stock Recovery (when it was working normally after powering off and not with kernel errors because of this). It failed.
I couldn't find the right answer(s). Thank you to anyone that can help me or others who have done the same!!
EDIT (11/19/2018):
So, last night I tried wiping my data in stock recovery and then I tried to do this again. It still didn't work. I also tried to apply the same stock zip as well as boot_magisk.img from this thread here https://forum.xda-developers.com/moto-g5s-plus/development/stock-kernel-prerooted-8-1-0-t3863301.
PS C:\Android SDK\platform-tools> fastboot flash boot boot_magisk.img
Sending 'boot' (10702 KB) OKAY [ 0.391s]
Writing 'boot' (bootloader) Image not signed or corrupt
OKAY [ 0.141s]
Finished. Total time: 0.563s
It all still fails. However, now when I boot up my phone it goes straight to the bootloader instead of loading the OS right away. I can select START to start the phone normally from there.
I got all this resolved through XDA's Telegram group (& specific group for G5s Plus/sanders)! I have TWRP (Treble) and custom rom working after getting an official stock rom from them flashed using fastboot commands!
I don't know if I should or a mod can close/erase this thread now?
Try typing fastboot oem fb_mode_clear while in bootloader
Coala990 said:
Try typing fastboot oem fb_mode_clear while in bootloader
Click to expand...
Click to collapse
Thanks for the suggestion/tip. I will probably try that if I reflash twrp treble (or another version of twrp for Sanders) again. This has been resolved.
Hey all, new poster but long time user of the site, just never needed an account until today lol. Anyways, just got a Pixel 5a5G that I am trying to install LineageOS on. I am following the instructions from here, and once I get to the point of flashing the vendor_boot partition, I receive this:
Code:
PS C:\Windows\system32> fastboot flash vendor_boot C:\Users\bobby\Downloads\vendor_boot.img
target reported max download size of 268435456 bytes
sending 'vendor_bootb' (98304 KB)...
OKAY [ 2.225s]
writing 'vendor_bootb'...
FAILED (remote: Not allowed to flash (vendor_bootb))
finished. total time: 2.307s
When running fastboost unlock bootloader, I receive this:
Code:
PS C:\Windows\system32> fastboot flashing unlock
...
(bootloader) Device already unlocked
OKAY [ 0.055s]
finished. total time: 0.056s
I have reflashed the stock firmware with the Android Flashing Tool to 13.0.0, both keeping the bootloader locked and unlocked. I have tried unlocking and relocking the bootloader. I used the utility's "full-flash" feature to flash both partitions, all to no avail. Research on here seems to point that the bootloader is locked, but fastboot says it isn't, settings is greyed out saying the bootloader is already unlocked, and fastboot mode on the phone says Device state: unlocked.
Any ideas?
Did you remove your screenlock and Google account before flashing?
Leberkuchen said:
Did you remove your screenlock and Google account before flashing?
Click to expand...
Click to collapse
Yes. I've flashed from a factory install with no passcode or account ever set. Same issue
From the output it's trying to write vendor_bootb??? Some combination of this should fix it:
-Make sure to use platform tools r33.0.3, the latest r34 has at least one known problem with fastboot and I don't trust it
-If you're using powershell you have to run the command as .\fastboot flash you can only run fastboot flash if you are in cmd
-Make sure both slots are on latest February firmware (probably not really necessary but a last ditch effort)