Related
The solution is very simple and ive tested it on more then 5 different senarios when i get the bug.
1. install TWRP recovery (you can even sideload it with fastboot if you dont wanna install it on phone(if you got stock recovery etc.), with this command "fastboot boot openrecovery-twrp-2.7.1.0-m8.img"
2. make a full wipe, check all boxes except external SD :highfive:, that will erase /data/media and also /data where the encryption bug lies.
3. install your ROM or restore your ROM from backup.
4. then reboot recovery and flash the recovery you want (or sideload it with the command above).
5. done, now the encryption bug is gone :good:
if this still dont work, try the solution given by maxrdlf95 in his thread here http://forum.xda-developers.com/showthread.php?t=2773203
smaberg said:
The solution is very simple and ive tested it on more then 5 different senarios when i get the bug.
1. install TWRP recovery (you can even sideload it with fastboot if you dont wanna install it on phone(if you got stock recovery etc.), with this command "fastboot boot openrecovery-twrp-2.7.1.0-m8.img"
2. make a full wipe, check all boxes except external SD :highfive:, that will erase /data/media and also /data where the encryption bug lies.
3. install your ROM or restore your ROM from backup.
4. then reboot recovery and flash the recovery you want (or sideload it with the command above).
5. done, now the encryption bug is gone :good:
if this still dont work, try the solution given by maxrdlf95 in his thread here http://forum.xda-developers.com/showthread.php?t=2773203
Click to expand...
Click to collapse
So, what youre basically saying is wipe data? I think the point is most people dont wanna do that, and doesnt the other fix allow you to fix the issue without wiping? Just trying to understand...
mikeyinid said:
So, what youre basically saying is wipe data? I think the point is most people dont wanna do that, and doesnt the other fix allow you to fix the issue without wiping? Just trying to understand...
Click to expand...
Click to collapse
Make a full backup of your ROM first, then my steps (cwm, philz won't work).
Then Restore backup...
Philz and cwm won't wipe the important parts, so with them the bug will still be there. So twrp with all options check will do the trick.
This method worked for me. I selected all options except external sd card when wiping. Wiping failed. Then I went to format data, typed in "yes" and formatted my internal storage. I then went back to select all option to wipe everything and surprisingly "It Worked", I was able to wipe everything and restore my rom successfully.
Thanks for this!!! (AT&T User!)
Sorry...wrong thread
My phone Isn't Rooted nor has the bootloader is Unlocked
smaberg said:
The solution is very simple and ive tested it on more then 5 different senarios when i get the bug.
1. install TWRP recovery (you can even sideload it with fastboot if you dont wanna install it on phone(if you got stock recovery etc.), with this command "fastboot boot openrecovery-twrp-2.7.1.0-m8.img"
2. make a full wipe, check all boxes except external SD :highfive:, that will erase /data/media and also /data where the encryption bug lies.
3. install your ROM or restore your ROM from backup.
4. then reboot recovery and flash the recovery you want (or sideload it with the command above).
5. done, now the encryption bug is gone :good:
if this still dont work, try the solution given by maxrdlf95 in his thread here http://forum.xda-developers.com/showthread.php?t=2773203
Click to expand...
Click to collapse
Hello, I have the same Issue, just that my bootloader is locked, the phone has never been rooted, here's an image of the phone, also here's a getvar from the phone.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.26.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.24.709.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: F********500
(bootloader) imei: 3*************5
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 59ee16dd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.027s
I also tried to manually format userdata, flash recovery, flash boot and this is what I get:
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.005s
target reported max download size of 1826410496 bytes
sending 'recovery' (16050 KB)...
OKAY [ 1.475s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.056s
erickobain said:
Hello, I have the same Issue, just that my bootloader is locked, the phone has never been rooted, here's an image of the phone, also here's a getvar from the phone.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.26.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.24.709.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: F********500
(bootloader) imei: 3*************5
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 59ee16dd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.027s
I also tried to manually format userdata, flash recovery, flash boot and this is what I get:
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.005s
target reported max download size of 1826410496 bytes
sending 'recovery' (16050 KB)...
OKAY [ 1.475s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.056s
Click to expand...
Click to collapse
Unlock the bootloader.
It wont let me...
erickobain said:
It wont let me...
Click to expand...
Click to collapse
Nobody is going to know what that means. You need to provide details and specifics on what you tried, what exact step you got stuck, including details on error messages or other results on the phone's screen, computer screen, etc.
Responding with one sentence like you did, and expecting anyone to be able to help, is not the proper way to post or ask for help.
You can't install TWRP with a locked bootloader. You need to unlock the bootloader via HTCDev.com. If you had problems with the bootloader unlock process, you need to be specific on what step, and what errors you encountered; of you expect us to advise you.
Hello,
The first day I got my moto x style (XT1572) I started to root, everything was more or less well until I tried to install the SU when I finished installing the binary from the TWRP custom recovery-3.0.2-0- clark you say yes to install the root since the phone would not start and remains in boot loop.
After much look I followed some tutorial XDA (http://forum.xda-developers.com/moto-x-style/help/brick-downgrade-6-0-to-5-1-heeeeelp-t3253716) to return to flash the phone with the rom that theory came from factory cbox1s_XT1572_CLARK_RETEU_6.0_MPHS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml after following all the steps mobile and well lit and seems it was all sorted.
Well, I went back to the load to make root and remove the message that the bootloader was unlocked this time all fu well, except now every time I reboot I enter into fastboot mode and have to select START to boot normal to me.
Any ideas or suggestions to fix it?
regards,
PD: Sorry for my google translate english i'am spanish a my english level is very bad :crying:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
same problem with Motorola z xt1650-03 , unlocked bootloader , every time I start up remain stuck in fastboot mode , after ,push the power button for start , and start normal.
I try to reload stock firmware 7.0 with fastboot mode but when try to flash partition.gpt he say bad key .
now I used like this ,
sagutxo97 said:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
Click to expand...
Click to collapse
What? how do you do it? can you tell me how to do it more specific? I'm new so I don't understand what you mean and how you do it :/
thank you.
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
acejavelin said:
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
Click to expand...
Click to collapse
You saved my [email protected]#! Thanks.
I'm trying help a friend with her Moto X Style. The buttoms RETURN, HOME and APP is not working. I'm trying upload a ROM, but I got errors everytime and the fastboot was entering every boot.
acejavelin said:
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
Click to expand...
Click to collapse
I did this several times and it set continues it say fasboot reason reboot mode set to fastboot and I tried fastboot oem fb_mode_clear but it just says boot loader slot count not found and etc
Sam to me. Any help?
ninormalen said:
Sam to me. Any help?
Click to expand...
Click to collapse
Yea I do need help, I had flashed a custom rom with twrp recovery on my phone but every time I reboot I either loads into recovery or boot loader if I fb mode clear or not. Even if theirs a system to boot, I have to manually boot into through boot loader and start. If I go to bootloader logs it just says reboot mode set to fastboot.
typo - fastboot, not fasboot
fastboot oem fb_mode_clear
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
When I type this commend, I get the following error:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Can someone tell me whats is the problem?
lucas.passos said:
When I type this commend, I get the following error:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Can someone tell me whats is the problem?
Click to expand...
Click to collapse
There is no problem... The Moto X does not have A/B software slots, the messages above are merely informational and completely normal.
With mfastboot there is no messages like this. Only "OKAY" one
However it didn't help with my Moto G (falcon).
What helped was checking the kernel. My "smartness" told me to flash Nouagt when I had Pie rom...
Dunken415 said:
Yea I do need help, I had flashed a custom rom with twrp recovery on my phone but every time I reboot I either loads into recovery or boot loader if I fb mode clear or not. Even if theirs a system to boot, I have to manually boot into through boot loader and start. If I go to bootloader logs it just says reboot mode set to fastboot.[/QUOTE
same problem here brother did you find any solution to it?? please help me brother.
Click to expand...
Click to collapse
sagutxo97 said:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
Click to expand...
Click to collapse
How'd you do that? i have the same problem how do switch back to normal powerup?
XT-1570 "bootmode-recovery"
Dunken415 said:
I did this several times and it set continues it say fasboot reason reboot mode set to fastboot and I tried fastboot oem fb_mode_clear but it just says boot loader slot count not found and etc
Click to expand...
Click to collapse
I am having the same issue. Would appriciate any help.
E:\fastboot oem fb_mode_clear
...
OKAY [ 0.000s]
finished. total time: 0.016s
PS E:\Backup\Android - XT1570> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.43
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: no
(bootloader) hwrev: 0x82A0
(bootloader) radio: 0x3
(bootloader) emmc: 64GB Toshiba REV=07 PRV=00 TYPE=57 PNM=064G38
(bootloader) ram[0]: 3072MB SK Hynix S8 SDRAM DIE=6Gb M5=x6 M6=x3 M7=x0
(bootloader) ram[1]: M8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: LX7C2xxxxx
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0xDEAD
(bootloader) uid: EFFA2C001E000000000000000000
(bootloader) unlocked: Not supported
(bootloader) securestate: Engineering
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 1
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 35550006xxxxxxx
(bootloader) meid:
(bootloader) date: 04-30-2015
(bootloader) sku: XT1570
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jul 18 7:57:55 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retasia_ds/clark_ds
(bootloader) ro.build.fingerprint[1]: :6.0.1/MPHS24.107-58-5/4:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.5.clark_retas
(bootloader) ro.build.version.full[1]: ia_ds.retasia.en.03
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-gb67345b (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goo
(bootloader) kernel.version[2]: gle 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Sep 29 00:24:52 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VA0.43-0-g8cea836
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=16279de-dirty
(bootloader) hyp.git: git=16279de-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.43-0-g8cea836
(bootloader) aboot.git: git=MBM-NG-VA0.43-0-gde54c6f
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.172s
C:\fastboot oem fb_mode_clear
...
OKAY [ -0.000s]
finished. total time: -0.000s
Hello, I am totally lost... I've been trying to solve this problem but no luck... I relocked my bootloader. Since that day, I can only access : fastboot.
It seems I can flash recovery with fastboot, but the phone never boots into recovery (stuck on ZTE logo B2017G ).
I've tried to put my device in EDL mode with DeepFlash cable but without success.
###########
fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.017s
##############
any one can help me plz.
anyone can help
t.zennad said:
anyone can help
Click to expand...
Click to collapse
I'm also in the same condition...
fastboot not accessible...
Help!!!
Axon 7 mini 7.1.1 build B2017gV1.2.0B14
Still waiting too.
Get a stock recovery (not TWRP), flash it with fasboot flash recovery recovery.img
I think tdm has a thread with all stock images, flash the one for your country
https://forum.xda-developers.com/axon-7-mini/development/firmware-stock-firmware-t3696538
If this doesn't work, maybe the verity check fails, making the device unable to boot, then go ahead and flash system and boot via fastboot.
fastboot flash system system.img
fastboot flash boot boot.img
Good luck
just a hailmairy here but...
"(bootloader) Charger screen enabled: 'false'"
in Advanced Settings ->Developer Options->Stay Awake (while charging) [ ]
should possible be switched on as it does mentions that charging screen set to off?
Probably would only sort one item though but you never know and if it does your one more step forward.
sonnettie
HEEEEELP! From Liquid tried to flash Lineage16.....flashed bootloader...I'm stuck on fastboot. The down volume key is broken. Only up volume works but not in fastboot. Tried to adb/flash a sock recovery....only can reboot in fastboot dialogue. Any solution? Thank you.
Hello
any one can help please, i am still in same problem
fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3447000
(bootloader) variant:TULIP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x12c00000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5ebb79e00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x100000000
(bootloader) serialno:bc13c89a
(bootloader) kernel:lk
(bootloader) product:TULIP
all:
finished. total time: 0.022s
------
fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.007s
-------
I relocked my bootloader. Since that day, I can only access : fastboot.
It seems I can flash recovery with fastboot, but the phone never boots into recovery (loop on ZTE logo B2017G ).
I've tried to put my device in EDL mode with DeepFlash cable but without success.
Thanks
I tried to unlock my b2017g with fastboot commands but not luck, i tried use Hydra too... i hope will find a solution soon :/
Hi Everybody, I think I have a similar issue. After many years with regular stock system I decided to change to a custom ROM, hoping I can use my phone with my native language, which was not in the stock rom.
But now I stucked in the fastboot, and I can not get out of it. I can access my phone via fastboot, I have already flashed the TWRP, but the phone can not boot into the recovery and the system. How can I fix this? Please help me, I like this phone, I would like to get it back to life.
I bricked my Axon mini n2015 by flashing No verity boot.img and a custom recovery. Now phone is stuck in fastboot mode. Help guys, what do i do?
Looks like no solution
Hey community,
i bought the watch to be able to use kali linux on it. It is the model "TicWatch Pro 3 Ultra LTE".
Therefore, I have made myself directly to the work:
* DIY USB Data cable built - check
* Flashed Kali Nethunter (https://www.kali.org/docs/nethunter/installing-nethunter-on-the-ticwatch-pro3/) according to instructions - check to point "2.12 - Flash Disabler with “adb sideload".
(No backup made via TWRP - first mistake)
"Flash Disabler with “adb sideload” led to an error message because no volume button was pressed. (Question of the setup if disk quota should be changed).
From there it went off....
* Restarted the watch (probably another mistake:/)
* Afterwards booted into recovery and copied the "Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip" to /sdcard via `adb push`.
* With "install ZIP" successfully installed
* Reboot = Bootloop
Now I only get into the "fastboot". Neither booting into the recovery nor into the OS is possible and the watch restarts continuously.
I have tried the following without success:
* Via fastboot flash the recovery and restart ".\fastboot.exe flash recovery rover_recovery.img".
* Via fastboot directly into the recovery boot ".\fastboot.exe boot rover_recovery.img"
* Via fastboot clear userdata and cache "./fastboot.exe -w"
It remains unchanged: Bootloop + only boot into fastboot is possible.
I have refrained from trying other things, because I do not want to destroy the watch irretrievably.
Is there someone who can help me to bring the watch back to life?
I am grateful for any help, because I really despair.
Greets TCL7070x
Hello together,
tried different ways to get live back into the watch.. without success.
Even flashing the stock rom from https://wear.revtechs.me/en/download (scroll to the end of the page) via fastboot did not work and the watch stucks in the bootloop. I've done
* fastboot flash boot boot.img
* fastboot flash recovery recovery.img
* fastboot flash system system.img
* fastboot flash vendor vendor.img
and even tried
* fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Does anyone have an idea and would share it with me?
Thanks in advance!
Greets TCL7070x
TCL7070x said:
Hello together,
tried different ways to get live back into the watch.. without success.
Even flashing the stock rom from https://wear.revtechs.me/en/download (scroll to the end of the page) via fastboot did not work and the watch stucks in the bootloop. I've done
* fastboot flash boot boot.img
* fastboot flash recovery recovery.img
* fastboot flash system system.img
* fastboot flash vendor vendor.img
and even tried
* fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Does anyone have an idea and would share it with me?
Thanks in advance!
Greets TCL7070x
Click to expand...
Click to collapse
Hey buddy, I made this account just to reply to this thread lol
I bought a Ticwatch pro 3 ultra GPS (despite having read your post beforehand, thinking it wouldn't happen to me), and ended up getting stuck on an infinite boot screen.
Once the recovery was installed, I was able to boot after these steps:
Flash OneOS with adb sideload
Flash Mobvoi Apps with adb sideload
But once I did these steps, I could no longer boot into OneOS, I just got an "infinite" loading screen:
Make a copy of your Magisk apk file to Magisk-v24.3.zip
Flash Magisk with adb sideload
Flash Disabler with adb push disabler.zip /sdcard/ and Install via TWRP
I don't know why those steps need to be peformed because the OneOS help page doesn't mention it.
Note - it is totally possible that I was too impatient during the first boot & f*cked everything up by not waiting long enough for it to boot. I just saw that the OneOS help page says:
- Restart the system each reboot / first start will take longer than normal, it is because of the deodex.
Once in the bootloader, I am able to get into the TWRP recovery by using the buttons of the watch.
I made a backup before doing all of this so I will try to restore it and see if that let's met boot again, or start from scratch. I just need to re-solder the wires of my USB cable, since they fell off whilst fooling around last night.
I can send you my backup files so you can restore them, there is no personal data on them, it's just a backup of the default storage; which was performed the first time I was able to get into TWRP.
Hold both watch buttons for 10 seconds to get into the bootloader mode.
Press the bottom button to change option selection until you see "recovery mode".
Press the top button to enter/execute selection & boot into recovery mode.
If that doesn't work, maybe you could try:
fastboot boot rover_recovery.img
That should load twrp.
Also, take a look at this thread:
[Solved] Bootloop on FP4 after a wrong "fastboot boot twrp.img"
Hello! I was doing several experiments with TWRP on FP4, always booting it temporally with the “fastboot boot twrp.img” command. Then I did something stupid, I didn’t pay attention and I tried to boot on a FP2 TWRP image that unluckily was still in the same directory (from last month trials...
forum.fairphone.com
Hey @HarmlessHacker,
happy to hear that you've registered just to reply. Welcome @ xda-developers
I've tried so many things that i can't bring it into the right order. But:
One thing i've tried was your mentioned TWRP flashing: `fastboot boot rover_recovery.img`
The closest state i got was that TWRP booted and about 1 to 2 sec. after that the watch restarted right away. The watch "does not care" what is booting... after the bootloader "unlock warning" was displayed it takes another 2 to 3 seconds. Then the watch vibrates and restarts immediately.
Depending on what I flash, still happens the following sequence:
* TicWatch Logo -> Bootloader -> Black Screen -> Vibration (Reboot).
and directly after that
* TicWatch Logo -> Bootloader -> Vibration (Reboot)
It looks like the watch tries to start something for a short time. But afterwards discard this directly, regardless of success (as described above the display of TWRP).
I would be very happy to receive the backup. Even if it is the firmware for the GPS mode. I guess worse than "bootloop of death" isn't possible. And maybe it's worth a try
it can't be that this doesn't work ;D
Can you try the fastboot boot rover_recovery.img with the --verbose or -v option and share the output?
I'm new to android modding, but I noticed some fastboot options that might help (fastboot --help)
Code:
--slot SLOT Use SLOT; 'all' for both slots, 'other' for
non-current slot (default: current active slot).
--set-active[=SLOT] Sets the active slot before rebooting.
--verbose, -v Verbose output.
POTENTIALLY DANGEROUS IDEA (use with options above):
You might be able to try to force boot of the image (don't use with flash comand, only boot):
--force Force a flash operation that may be unsafe.
You can get more info about your current slots and all other variables use this:
fastboot getvar all
...look for (bootloader) current-slot: in the output
If it looks something like this:
Code:
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:yes
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
maybe try something like this:
fastboot --set-active=b --verbose
Source:
[Solved] Bootloop on FP4 after a wrong "fastboot boot twrp.img"
Here hidden is the full getvar all <details><summary>getvar all</summary>fastboot getvar all (bootloader) parallel-download-flash:yes (bootloader) hw-revision:10000 (bootloader) unlocked:yes (bootloader) off-mode-charge:0 (bootloader) charger-screen-enabled:0 (bootloader)...
forum.fairphone.com
Of course, i can:
Here is the output from booting via fastboot with verbose mode ('.\fastboot.exe boot ..\..\..\rover_twrp.img --verbose'). Unfortunately no change between verbose and non-verbose mode:
Code:
Sending 'boot.img' (26682 KB) OKAY [ 0.843s]
Booting OKAY [ 11.621s]
Finished. Total time: 12.561s
and this is the output of all vars ('.\fastboot.exe getvar all'):
Code:
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3770009
(bootloader) variant:QRD eMMC
(bootloader) unlocked:yes
(bootloader) secure:no
(bootloader) version-baseband:
(bootloader) version-bootloader:rover-03.02.38.03.16
(bootloader) logical-block-size:0x200
(bootloader) erase-block-size:0x200
(bootloader) display-panel:
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) max-download-size: 0x1feffc00
(bootloader) partition-type:userdata:f2fs
(bootloader) partition-size:userdata: 0x12d0e8e00
(bootloader) partition-type:btlver:raw
(bootloader) partition-size:btlver: 0x400
(bootloader) partition-type:dpo:raw
(bootloader) partition-size:dpo: 0x2000
(bootloader) partition-type:msadp:raw
(bootloader) partition-size:msadp: 0x40000
(bootloader) partition-type:apdp:raw
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:mcfg:raw
(bootloader) partition-size:mcfg: 0x400000
(bootloader) partition-type:mdtpbak:raw
(bootloader) partition-size:mdtpbak: 0x2000000
(bootloader) partition-type:mdtp:raw
(bootloader) partition-size:mdtp: 0x2000000
(bootloader) partition-type:dip:raw
(bootloader) partition-size:dip: 0x100000
(bootloader) partition-type:limits:raw
(bootloader) partition-size:limits: 0x8000
(bootloader) partition-type:oem:raw
(bootloader) partition-size:oem: 0x1000000
(bootloader) partition-type:config:raw
(bootloader) partition-size:config: 0x8000
(bootloader) partition-type:keystore:raw
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc: 0x100000
(bootloader) partition-type:persist:raw
(bootloader) partition-size:persist: 0x2000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x4000000
(bootloader) partition-type:keymasterbak:raw
(bootloader) partition-size:keymasterbak: 0x100000
(bootloader) partition-type:keymaster:raw
(bootloader) partition-size:keymaster: 0x100000
(bootloader) partition-type:cmnlib64bak:raw
(bootloader) partition-size:cmnlib64bak: 0x100000
(bootloader) partition-type:cmnlib64:raw
(bootloader) partition-size:cmnlib64: 0x100000
(bootloader) partition-type:cmnlibbak:raw
(bootloader) partition-size:cmnlibbak: 0x100000
(bootloader) partition-type:cmnlib:raw
(bootloader) partition-size:cmnlib: 0x100000
(bootloader) partition-type:vendor:raw
(bootloader) partition-size:vendor: 0x20000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x60000000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo: 0x100000
(bootloader) partition-type:recovery:ext4
(bootloader) partition-size:recovery: 0x2000000
(bootloader) partition-type:boot:raw
(bootloader) partition-size:boot: 0x2000000
(bootloader) partition-type:vbmetabak:raw
(bootloader) partition-size:vbmetabak: 0x10000
(bootloader) partition-type:vbmeta:raw
(bootloader) partition-size:vbmeta: 0x10000
(bootloader) partition-type:dtbobak:raw
(bootloader) partition-size:dtbobak: 0x800000
(bootloader) partition-type:dtbo:raw
(bootloader) partition-size:dtbo: 0x800000
(bootloader) partition-type:abootbak:raw
(bootloader) partition-size:abootbak: 0x100000
(bootloader) partition-type:aboot:raw
(bootloader) partition-size:aboot: 0x100000
(bootloader) partition-type:splash:raw
(bootloader) partition-size:splash: 0xb00000
(bootloader) partition-type:sec:raw
(bootloader) partition-size:sec: 0x4000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg: 0x180000
(bootloader) partition-type:DDR:raw
(bootloader) partition-size:DDR: 0x8000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2: 0x180000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1: 0x180000
(bootloader) partition-type:dspbak:raw
(bootloader) partition-size:dspbak: 0x1000000
(bootloader) partition-type:dsp:raw
(bootloader) partition-size:dsp: 0x1000000
(bootloader) partition-type:devcfgbak:raw
(bootloader) partition-size:devcfgbak: 0x40000
(bootloader) partition-type:devcfg:raw
(bootloader) partition-size:devcfg: 0x40000
(bootloader) partition-type:tzbak:raw
(bootloader) partition-size:tzbak: 0x200000
(bootloader) partition-type:tz:raw
(bootloader) partition-size:tz: 0x200000
(bootloader) partition-type:rpmbak:raw
(bootloader) partition-size:rpmbak: 0x80000
(bootloader) partition-type:rpm:raw
(bootloader) partition-size:rpm: 0x80000
(bootloader) partition-type:sbl1bak:raw
(bootloader) partition-size:sbl1bak: 0x80000
(bootloader) partition-type:sbl1:raw
(bootloader) partition-size:sbl1: 0x80000
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd: 0x2000
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc: 0x400
(bootloader) partition-type:modem:raw
(bootloader) partition-size:modem: 0x5400000
(bootloader) hw-revision:10000
(bootloader) serialno:<REDACTED>
(bootloader) kernel:lk
(bootloader) product:rover
all:
Finished. Total time: 0.350s
The behavior of the watch directly after trying to boot into the recovery:
It is looping through these stages:
* Logo -> Bootloader -> Logo ~8sec -> Vibration (Reboot) and black screen
(does not reach the TWRP screen at all)
Based on the video you sent me: I understand that vbmeta is a "mini os" that is responsible for verifying the other partitions, including the boot partition. If I understand correctly, vbmeta uses the key stored on the device in the keymaster partition (?)?
By flashing vbmeta with `.\fastboot.exe --disable-verity --disable-verification flash vbmeta vbmeta.img` this cryptographic verification is turned off, right?
All in all, it sounds like it's related to vbmeta blocking the boot process? Or I understand it completely wrong ;D
Anyway, thanks for going through this with me
There has been an update to the documentation from OneOS. They changed domains, I think mobvoi is being hostile towards 3rd party developers (based on the fact that they removed they removed the data pins from the included charger)
https://wear.lunawolf.es/en/ayuda
To force the watch to get into the bootloader, hold both buttons until you see the menu, from there you should be able to use the fastboot command to flash the recovery image again
Make sure to wipe the "data" partition when finished or you will not be able to boot
Hey, every time you answer, i get a bit hope back ;-)
Thanks for the new link to wearOS. Didn't see that.
Another day.. another try... I've tried to boot into TWRP again and followed the steps at the website + your recommendation to clean the data patition:
Code:
.\fastboot.exe erase userdata
.\fastboot.exe erase cache
.\fastboot.exe flash recovery fresh_downloaded_from_wearos_twrp_rover.img
.\fastboot.exe --disable-verity --disable-verification flash vbmeta fresh_downloaded_from_wearos_vbmeta.img
.\fastboot.exe reboot recovery
Another try was, to use the boot.img of the current OneOS release, because i've tried the same with the stock rom:
Code:
.\fastboot.exe flash boot .\OneOS-21.10.8_rover\boot.img
.\fastboot.exe erase cache
.\fastboot.exe erase userdata
.\fastboot.exe reboot recovery
Without any luck :/
No change in it's behavior - even between both tries.
i am confused and do not know what to do :/
It feels that everything i try won't work at all
Make sure that you are flashing the correct recovery and custom rom from https://wear.lunawolf.es/en/descargar
There might have been updates since you last downloaded them. There are many warnings about not being able to boot if done incorrectly.
Can send me a video of the bootloop and your attempt to get into the recovery mode using these steps:
Hold both watch buttons for 10 seconds to get into the bootloader mode.
Press the bottom button to change option selection until you see "recovery mode".
Press the top button to enter/execute selection & boot into recovery mode.
if that doesn't work, maybe try this:
Factory reset from recovery on Ticwatch E? - Wear OS by Google Community
--------------------------------------------------------------------
OneOS news updates:
• NEWS • ONE Projects
ONE Team Projects News Channel Spanish Group: ETASOON English Group: ETASOON MIUI (END OF LIFE): Downloads: @OneOS_Weekly Stable Base: @OneOS_Stable PayPal: https://PayPal.me/badwolfalfa WEB: http://one.revtechs.me System Status: ESTASOON
t.me
https://twitter.com/RevOSTechs
Everything is hackable... you got this.
Also, be careful with "Disable DM Verity"
RECOMMENDED TO DO UNDER CLEAN INSTALL OR DEVICE MAY NOT START
(dont flash it twice)
I don't think you got that far yet, but I just wanted to give you a heads up!
You might also be able to flash the stock rom and hopefully get it out of the boot loop:
Descargar | OneOS Wear
wear.lunawolf.es
Try fastboot boot rover_recovery.img (without the "flash" option) to boot the recovery as a troubleshooting step or fastboot reboot recovery
I also noticed that it helps to store the files on the ticwatch rather than the PC, I forget exactly which one was problematic.
This video helped me figure it out:
Adb useful commands list
Adb useful commands list
Adb useful commands list. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
Good Luck!
HarmlessHacker said:
You might also be able to flash the stock rom and hopefully get it out of the boot loop:
Descargar | OneOS Wear
wear.lunawolf.es
Try fastboot boot rover_recovery.img (without the "flash" option) to boot the recovery as a troubleshooting step or fastboot reboot recovery
I also noticed that it helps to store the files on the ticwatch rather than the PC, I forget exactly which one was problematic.
This video helped me figure it out:
Adb useful commands list
Adb useful commands list
Adb useful commands list. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
Good Luck!
Click to expand...
Click to collapse
Nice video
TCL7070x said:
Hey community,
i bought the watch to be able to use kali linux on it. It is the model "TicWatch Pro 3 Ultra LTE".
Therefore, I have made myself directly to the work:
* DIY USB Data cable built - check
* Flashed Kali Nethunter (https://www.kali.org/docs/nethunter/installing-nethunter-on-the-ticwatch-pro3/) according to instructions - check to point "2.12 - Flash Disabler with “adb sideload".
(No backup made via TWRP - first mistake)
"Flash Disabler with “adb sideload” led to an error message because no volume button was pressed. (Question of the setup if disk quota should be changed).
From there it went off....
* Restarted the watch (probably another mistake:/)
* Afterwards booted into recovery and copied the "Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip" to /sdcard via `adb push`.
* With "install ZIP" successfully installed
* Reboot = Bootloop
Now I only get into the "fastboot". Neither booting into the recovery nor into the OS is possible and the watch restarts continuously.
I have tried the following without success:
* Via fastboot flash the recovery and restart ".\fastboot.exe flash recovery rover_recovery.img".
* Via fastboot directly into the recovery boot ".\fastboot.exe boot rover_recovery.img"
* Via fastboot clear userdata and cache "./fastboot.exe -w"
It remains unchanged: Bootloop + only boot into fastboot is possible.
I have refrained from trying other things, because I do not want to destroy the watch irretrievably.
Is there someone who can help me to bring the watch back to life?
I am grateful for any help, because I really despair.
Greets TCL7070x
Click to expand...
Click to collapse
Bro inbox me i will help u
If i not responding here
Text me o whatsappWasap.my/60142222872
@TCL7070x
According to this thread: Factory reset from recovery on Ticwatch
You can actually boot into recovery by fastboot oem reboot-recovery but it only displays a big exclamation mark and nothing else.
Click to expand...
Click to collapse
Go to 6:24 to see how to get to bypass that exclamation mark
TCL7070x said:
Hey, every time you answer, i get a bit hope back ;-)
Thanks for the new link to wearOS. Didn't see that.
Another day.. another try... I've tried to boot into TWRP again and followed the steps at the website + your recommendation to clean the data patition:
Code:
.\fastboot.exe erase userdata
.\fastboot.exe erase cache
.\fastboot.exe flash recovery fresh_downloaded_from_wearos_twrp_rover.img
.\fastboot.exe --disable-verity --disable-verification flash vbmeta fresh_downloaded_from_wearos_vbmeta.img
.\fastboot.exe reboot recovery
Another try was, to use the boot.img of the current OneOS release, because i've tried the same with the stock rom:
Code:
.\fastboot.exe flash boot .\OneOS-21.10.8_rover\boot.img
.\fastboot.exe erase cache
.\fastboot.exe erase userdata
.\fastboot.exe reboot recovery
Without any luck :/
No change in it's behavior - even between both tries.
i am confused and do not know what to do :/
It feels that everything i try won't work at all
Click to expand...
Click to collapse
@nelikp told me that he was able to use my backup to recover from his bootloop
TicWatch Pro 3 Ultra GPS (Rubyfish) [Complete Stock TWRP Backup]
I heard that many people need the stock backup files for the TWP3 Ultra GPS so here you go! Note, this is the "PMRB.220111.001" base version https://mega.nz/file/1AlCDJ7S#GoX8tWbfkZ7EALwA3gDvX7lOCKPms6oQVogEo5Th32E Enjoy my friends!!
forum.xda-developers.com
I'm in a similar predicament - stuck in a boot loop. I own a TWP3 Ultra LTE and think the reason I have ended up this way is because I've attempted to flash a custom ROM (OneOS-21.10.8_rover.zip) which is only suitable for the TWP3 LTE running build PMRL.210414.002, and is not suitable for the TWP3 Ultra LTE running build PMRL.220111.001.
I also didn't make a backup in TWRP prior to installing the custom ROM, and so I feel your pain Even if I had, I'm not entirely sure it would solve my problems at this point.
I can get TWRP to load, but after a few seconds, the watch restarts, so there's not actually enough time for me to do anything. The only thing that is working ok is fastboot. The watch doesn't restart upon entering fastboot, and I can communicate fine with it (ie issue fastbook commands) via a command window.
I'm not overly optimistic, but perhaps the good folk here might be able to help out and perhaps there is a solution. If someone were to provide me with the stock ROM, and if there is a way to flash that using fastboot rather than TRWP, maybe that would be one way out of this. All thoughts / ideas very warmly welcomed and sorry for the newbie mistake!
I've tried some things again.. even `fastboot oem reboot-recovery`. But this command throws back as non existent, so i am not able to use it. .. but i don't wanna give up. Just nothing positive for now to share. ;-)
Thanks for sharing
On the OneOS Wear site (https://wear.lunawolf.es/en/descargar) there is a PMRB.220111.001 stock ROM available under rubyfish, but no equivalent PMRL.220111.001 stock ROM available under rover. I don't know if they will be releasing one eventually for rover, but I think if we were to get hold of PMRL.220111.001 stock ROM for rover there would at least be some chance.
How quickly are you looking to get back and running? I guess one option is buy a second TWP3 Ultra LTE, make a backup using TWRP, and then use this backup in an attempt to unbrick the first one using fastboot to flash the stock image. Do others think this is likely to work? Obviously requires some outlay £/$ though with no guarantee of success
[GUIDE/TUTORIAL/HOWTO] Motorola Moto G5 Stock to Android 11
[GUIDE/TUTORIAL/HOWTO] Motorola Moto G5 (cedric) Stock Android 11/LineageOS 18.1
Complete guide to install Android 11 on your Motorola Moto G5.
This tutorial only applies to this model, to check the correct version:
in Android, go to Settings > System > About phone, make sure it is one of these models:
- XT1670
- XT1671
- XT1672
- XT1675
- XT1676
- XT1677
Netflix and Disney+ are working.
See all my tutorials at https://github.com/djibe/Android-tutorials
CHANGELOG
v3. Magisk config for Netflix and Disney+
v2. Remove Warning Bootloader Unlocked Message (thx @Jospe)
v1. Initial release
1) WHAT YOU NEED
- djibe Moto G5 pack: https://bit.ly/motoG5djibepack
(Contains link to Motorola Bootloader unlock + TWRP Recovery 3.5.2_9-0 + Magisk root + Motorola USB drivers x32/64 + fastboot + logo.bin
+ latest modem firmware)
+ ROM LineageOS Official 18.1: https://forum.xda-developers.com/t/rom-official-cedric-11-lineageos-18-1.4260293/
Download latest build here: https://download.lineageos.org/cedric
+ BitGApps ARM64 11: https://github.com/BiTGApps/BiTGApps-Release
+/- extra apps: https://bitgapps.github.io/addon/ARM64.html
+ a microSD card formatted in FAT32: copy ROM, GApps (and Magisk). Insert it in phone
+ Charge phone to 100%
2) INSTALL DRIVERS
Install Motorola 64 bits drivers (32 or 64 bits depending on your Windows version).
Then plug Moto G5 to PC and let the install go on.
3) BACKUP YOUR DATA
When your phone is connected to Windows, search for all .jpg, .mp3, .mp4 files on your phone and make copies on your PC.
Then, with an app like Backupyourmobile, backup all your SMS, MMS, contacts.
Make sure the backup is located on microSD card.
4) UNLOCK BOOTLOADER
Update your Moto G5 to the latest official Android 8.1 Oreo.
In Android, go to Settings > System > System updates. Make sure you have latest version.
### If blocked with Android 7: read this https://forum.xda-developers.com/t/...ficial-stock-oreo-8-1-0.3823598/post-77219479
Go to Settings > System > About phone.
Tap 7 times on Build number to unlock Developer options.
Go to Settings > System > Developer options.
Switch ON "OEM onlocking"
### OEM Unlocking is disabled ? Reset phone to factory settings and start all over.
Then, go to Motorola website (shortcut in my archive or right below):
Sign in to Motorola - Motorola Mobility LLC
Sign in to Motorola
accounts.motorola.com
Subscribe using your Google Account or email.
Shut down phone.
Power it on in fastboot mode: Hold Power et Volume- during 3-4 secondes and release.
Screen is black with lines of text, starting with AP Fastboot Flash Mode (Secure).
Connect phone to USB, wait for fastboot drivers to install.
In Windows, select the /flash subfolder you unzipped from my archive.
On keyboard, make a combo Shift + right click > Open command windows here.
(or type cmd in Address bar and then hit Enter)
Write this command in Windows terminal :
Code:
fastboot oem get_unlock_data
confirm using Enter.
Command sends back a message like this :
Code:
$ fastboot oem get_unlock_data
(bootloader) 3A15680508256597#
(bootloader) 5A59333232324C373354004D6F746F2047200000#
(bootloader) 73FAD5B03353BBDAB1B0DCF7AC5D45AD99CB7DD8#
(bootloader) 348B937F00000000000000000000000
OKAY [ 0.016s]
Select all text > right click > select all.
Open a notepad editor, and paste text.
Rework the text to get it on 1 line, and remove all spaces and "(bootloader)" messages.
It should look like this : 3A15680508256597#5A59333232324C373354004D6F746F2047200000#73FAD5B03353BBDAB1B0DCF7AC5D45AD99CB7DD8#348B937F000000000000000000000000
Now, copy this line and paste it in Motorola website: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
Below, click on "Can my device be unlocked?" button.
Wait and then go to bottom of page.
I agree to be bound by the terms of the legal agreement: select Yes and click on "Request Unlock key"
You get the unlock key by email, looking like: C2L3N73RV6BUR7RT4ZTY
Use this unlock key in the following Windows command:
Code:
fastboot oem unlock YOUR_UNLOCK_CODE
Terminal asks for a second run of the same command:
Code:
fastboot oem unlock YOUR_UNLOCK_CODE
Confirm with enter and wait a moment ... till success is confirmed : " Bootloader is unlocked! Rebooting phone".
Keep Windows command opened.
4) FLASH RECOVERY
Now enter this command:
Code:
fastboot flash recovery twrp-3.5.2_9-0-cedric.img
Confirm with Enter.
Terminal confirms : "Finished. Total time: 0.670s".
### For future TWRP updates, TWRP.img can be flashed from TWRP recovery itself (Install > Install Image).
To remove bootloader unlock warning:
Code:
fastboot flash logo logo.bin
Back to the phone (still in fastboot/bootloader mode).
Press Volume- to select "RECOVERY MODE". Confirm by pressing Power.
Welcome to TWRP 3.5 recovery.
TWRP asks for Data partition password.
Tap on Cancel button.
### Well you already did a backup isn't it ?
TWRP asks for Keep System Read Only ? Swipe to Allow Modifications.
### You don't see this warning screen? Then you'll get "TWRP unable to mount storage" while trying to wipe partitions.
### > in TWRP, go to Reboot > Recovery so Recovery will refresh and popup the partition writing privilege.
In TWRP home screen, go to Wipe > Format data.
This will remove encryption.
Type yes and confirm to format partition.
Go to Reboot > Recovery.
Back to TWRP, go straight to Backup menu.
Select System, System Image, Boot, Vendor, Vendor image, persist_img and EFS partitions.
Tap on Select Storage and set Micro SD card.
Swipe to Backup and wait during backup.
### If MicroSD card is too small. Backup on data partition and after backup has ended, go to Mount and connect phone to PC to retrieve TWRP backup folder.
### Store this backup (aka nandroid backup) somewhere safe before going further.
5) WIPE PARTITIONS
Go to Wipe and Swipe to Factory reset.
6) FLASH ROM, BITGAPPS +/- MAGISK
Back to TWRP Home menu. Then tap on Install > choose lineage*.zip,
(if you don't see the files, tap on Select Storage and make sure Micro SDCard is active).
then Add more Zips > BiTGApps*.zip,
then Swipe to confirm Flash.
Wait for operation to end.
### You probably get this error: ERROR: This package requires firmware from an Android 8.1 based stock ROM build. Please upgrade firmware and retry!
### Your modem doesn't seem to be latest one (even though all official updates were stated as installed on my phone).
### Restart to fastboot mode (bootloader) and enter this new command:
Code:
fastboot flash modem NON-HLOS.bin
### Then go back to the beggining of this chapter.
Then tap Wipe cache/dalvik, swipe to confirm,
then Reboot System.
Android 11 is installed !
Wait for the phone to boot during 10 minutes.
7) ROOT WITH MAGISK (OPTIONAL)
### Only if you flashed Magisk via TWRP recovery
Configure Android as you like.
Magisk root starts with Android.
You can manage permissions and extra modules with Magisk Manager app.
If Magisk Manager doesn't download apk. Download official apk here: https://github.com/topjohnwu/Magisk/releases
10) OTHER APPS
- You can use GPS Status & Toolbox for faster GPS fix.
- Developer options
Settings > About phone.
Tap 7 times on build number.
Back to Settings > System > Advanced > Developer options
Select USB Configuration > set MTP
Set Windows animation scale, Transition animation scale and Animator duration scale to .5x
11) NETFLIX, DISNEY+
For Netflix and Disney+, follow this tutorial, all required files are included in my pack: https://www.droidwin.com/how-to-hide-root-from-apps-via-magisk-denylist/
Netflix is available as an APK from my pack.
Even though CTS profile match didn't work, both apps work.
That's it.
Enjoy ;-)
djibe
Thanks: @JarlPenguin, LineageOS team, TWRP team, BitGapps team, TopJohnWu (Magisk), @Jospe (Bootloader warning)
I thought updating to anything after Nougat meant installing new firmware i.e. if I want to use Lineage 18.1 on a Moto G5 currently running Nougat then I HAVE TO first upgrade to stock Oreo or later? Could someone please clarify. Thanks!
KeithSJS said:
I thought updating to anything after Nougat meant installing new firmware i.e. if I want to use Lineage 18.1 on a Moto G5 currently running Nougat then I HAVE TO first upgrade to stock Oreo or later? Could someone please clarify. Thanks!
Click to expand...
Click to collapse
Hi, yes you have to update to Oreo.
djibe89 said:
Hi, yes you have to update to Oreo.
Click to expand...
Click to collapse
Thanks but where does that feature in your guide? Or do you assume a level of knowledge?
KeithSJS said:
Thanks but where does that feature in your guide? Or do you assume a level of knowledge?
Click to expand...
Click to collapse
I wrote this: In Android, go to Settings > System > System updates. Make sure you have latest version.
I couldn't test more because my phone was already Oreo.
djibe89 said:
I wrote this: In Android, go to Settings > System > System updates. Make sure you have latest version.
I couldn't test more because my phone was already Oreo.
Click to expand...
Click to collapse
Okay, but I don't think it's that straightforward. Going from Nougat to Oreo is more involved than that I think, particularly if you are currently running a custom ROM and first have to go back to stock to perform the update. But I could go be wrong.
For anyone interested this may be of use:
[STOCK][OREO] Upgrade to Official Stock Oreo 8.1.0
DISCLAIMER: I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. YOU are choosing to make these modifications, and if you point the finger at me for messing up your...
forum.xda-developers.com
My dude you are amazing. My only issue is where were you 3 months ago when I was first setting up my Moto G5...
Also would be awesome to integrate the Moto G5 Fingerprint Reader Gestures.
when i want to flash recovery i get the following error
C:\Users\ACER\Desktop\djibe\flash>fastboot flash recovery twrp-3.1.1-0-cedric.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (14668 KB) OKAY [ 0.656s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.484s]
Finished. Total time: 1.219s
what am i doing wrong
maserati2011 said:
what am i doing wrong
Click to expand...
Click to collapse
Please post the output of fastboot getvar all.
Also you should use the latest version of TWRP (twrp-3.5.2_9-0) https://twrp.me/motorola/motorolamotog5.html
WoKoschekk said:
Please post the output of fastboot getvar all.
Also you should use the latest version of TWRP (twrp-3.5.2_9-0) https://twrp.me/motorola/motorolamotog5.html
Click to expand...
Click to collapse
I did try the newer versions but i got the same error, heres the output of getvar all:
C:\Users\ACER\Desktop\djibe\flash>fastboot flash recovery twrp-3.5.2_9-0-cedric.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (15822 KB) OKAY [ 0.781s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.500s]
Finished. Total time: 1.359s
C:\Users\ACER\Desktop\djibe\flash>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-B8.31
(bootloader) product: cedric
(bootloader) board: cedric
(bootloader) secure: yes
(bootloader) hwrev: P5
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG RE1BMB RV=08 PV=0D FV=000000000000000D
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8937
(bootloader) serialno: ZY32237NG2
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 2687B5F600000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 351865085012939
(bootloader) meid:
(bootloader) date: 04-16-2017
(bootloader) sku: XT1676
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Mar 5 2: 4:13 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/cedric/cedric:8.1.0/OPP28
(bootloader) ro.build.fingerprint[1]: .85-19-4-2/3447de:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.301.2.cedric.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8937_46.42.02.75R CEDRIC_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gea366bb-0001
(bootloader) kernel.version[1]: 6-g6e15bdb ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Mon Mar
(bootloader) kernel.version[3]: 4 18:13:35 CST 2019
(bootloader) sbl1.git: git=MBM-NG-VB8.31-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=3f87a46
(bootloader) devcfg.git: git=3f87a46
(bootloader) keymaster.git: git=3f87a46
(bootloader) cmnlib.git: git=3f87a46
(bootloader) cmnlib64.git: git=3f87a46
(bootloader) prov.git: git=3f87a46
(bootloader) aboot.git: git=MBM-NG-VB8.31-0-g0b9dae9
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.109s
maserati2011 said:
Writing 'recovery' (bootloader) Image not signed or corrupt OKAY [ 0.500s] Finished. Total time: 1.359s
Click to expand...
Click to collapse
I think that's not an error message telling you the image wasn't flashed correctly. It's only a warning message that can be ignored. Try to boot TWRP, it should work without any errors.
WoKoschekk said:
I think that's not an error message telling you the image wasn't flashed correctly. It's only a warning message that can be ignored. Try to boot TWRP, it should work without any errors.
Click to expand...
Click to collapse
you are correct, i rebooted directly into twrp after flashing recovery and it worked, thanks .