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.
Related
Hi,
I am after some help trying to get my HTC One back up and running.
I unlocked the bootloader using the htcdev website and installed cyanogen mod.
This was working fine for quite some time, until I recently wanted to download an app that was only available on stock phones.
I tried editing the /system/build.prop file to change the version to fool the app store but that didn't work.
Then when I restored my backup build.prop, I think I got the permissions wrong or something and the phone rebooted and went into a boot loop.
Then I followed a guide to get twrp on the device which worked.
Then I followed another guide attempting the restore the device to stock using the commands
Code:
fastboot oem lock
and
Code:
fastboot oem rebootRUU
.
Now the phone is stuck in a boot loop. All I can do is hold down power and volume down to get to HBOOT and Fastboot. If I try and load recovery it reboots to the same menu.
What else can I try, or do I now have a new paperweight?
Thanks for any suggestions.
- gatamous
Also,
I have tried flashing the stock recovery but I get signature errors.
Code:
C:\Android\android-sdk-windows-r24.0.2\platform-tools>fastboot flash recovery recovery_2.24.980.2.img
target reported max download size of 1443966976 bytes
sending 'recovery' (8752 KB)...
OKAY [ 1.140s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.846s
OK,
Never mind.
I was unable to unlock my bootloader because I was typing fastboot flash unlock token Unlock_code.bin instead of unlocktoken being one word.
One I fixed that the twrp recovery started again.
Once I opened that the phone apeared on my PC as a storage device.
I copied a cyanogen mode zip to that directory then installed it via twrp.
Now I have cyanogenmod working again.
Yay - no longer a brick.
I guess I am out of luck with reverting it to stock if the RUU I need is not available for my carrier - is that right?
If so I'll stay on cyanogen mod and not worry about reverting to stock.
Next time I guess I'll take one of these nandroid backups while the phone is still stock. Hindsight.
- gatamous
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 !
I managed to brick a moto G7 plus to the point of not being able to recover from it (locked bootloader, no twrp, boots to fastboot)
I wanted to go back to 100% stock but failed badly.
My device is odd one. RETLA stream with XT1965-T hardware. Lenovo Rescue apparently don't work on these devices.
1) I flashed stock RETLA latest rom from Lolinet using a flash.bat I made
2) worked and booted fine.....twrp was still intact
3) I did factory reset when booted in.
4) To relock I flashed boot.img and sent lock command a few times
5) Bootloader is now locked but only boots to fastboot and get (YOUR DEVICE HAS LOADED A DIFFERENT OPERATING SYSTEM.
6) I cannot unlock with code because adb says says I need developer option etc.
To repeat: this is BOOTLOADER LOCKED, JUST BOOTS TO FASTBOOT and gives "your device loaded a different operating system) which is not the issue and I expected that.
Bankflash didn't do anything. I mostly get oermission denied with mostly flashing anythiine else.
Any suggestions on how to just get this thing at least bootable again to use?
Thanks.
I have the same problem, but I found a way to at least start the device.
I gave "fastboot boot file.img" with a boot.img patched via Magisk.
But then it stopped working, so I changed the boot.img file to LineageOS.
Anrito Kun said:
I have the same problem, but I found a way to at least start the device.
I gave "fastboot boot file.img" with a boot.img patched via Magisk.
But then it stopped working, so I changed the boot.img file to LineageOS.
Click to expand...
Click to collapse
------------------
I was only able to do what is here: https://forum.xda-developers.com/t/...oem-at-developer-option-moto-g7-plus.4201169/
Anrito Kun said:
------------------
I was only able to do what is here: https://forum.xda-developers.com/t/...oem-at-developer-option-moto-g7-plus.4201169/
Click to expand...
Click to collapse
Thanks for replying to my post. I tried your patched boot.img but when I try to flash it I get " (bootloader) fllash permission denied "
renamed it to boot.img and then....
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (21845 KB)...
OKAY [ 0.465s]
writing 'boot'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.479s
PROBLEM SOLVED. See my post.
https://forum.xda-developers.com/t/moto-g7-plus-no-service.4201229/post-84335207
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)
Hello everyone I have been havinng some issues with my realme 8 RMX 3085. I was planning to install Lineage OS and custom recovery. I followed tutorials on xda. Fortunately i unlocked bootloader with official method - deeptest.apk, to do this firstly I flashed rom with thailand one. Everything seems to be succesfull, in settings bootloader is unlocked.
fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (131072 KB)...
OKAY [ 5.336s]
writing 'recovery'...
OKAY [ 0.451s]
finished. total time: 5.788s
However after that I am not able to enter recovery (even stock one). I kept flashing recovery image via fastboot. Everything seems to be all right until I try to enter it. Using command fastboot reboot recovery nothing happens. Another one adb reboot recovery tries to enter recovery several times with no success, then reboot to os.
I read couple of threads about that issue, tried using different computers, with different os - still the same. Tried using different cables and usb ports also nothing changed.
Does anyone have any idea what can couse the problem? Appreciate any advices.
Same here, trying few days but nobody help
Ok..did you installed magisk by flashing magisk patched boot.img ? If yes..then you need to restore/flash stock boot.img to enter recovery..this problem occurs on android 12 only..
https://telegra.ph/Flash-LineageOS-on-Realme-8-06-05
try follow this tutorial, worked for me