Related
please..
i have problem with bootloader version 41.1A
i want to Downgrade to version 41.18 or 41.19
anyone know ..??
please share it
thank you
Up
Me too
My bootloader v 41.1A I downgrade 41.18 Help
Why do you need to downgrade? Messing with Bootloaders can destroy your phone.
even i want to downgrade... I cant flash custom recovery on 41.1A
poran123 said:
even i want to downgrade... I cant flash custom recovery on 41.1A
Click to expand...
Click to collapse
Bootloader cannot be downgraded. You're stuck on w/e version you have currently installed.
Okay so I'm stuck on 41.1A and my phone will continue to restart itself and then stuck in bootloop till the battery dies... and then when I connect it to the charger boot's up normally...
@lost101
Can you please let me know how to check bootloader version?
I am using Moto G XT1033 model(Asia).
It was updated to Lollipop 5.0.2 by Motorola Stock Lollipop update.
Later on I had unlocked bootloader and downgraded it to Kitkat 4.4.4 using this thread.
I don't have any clue about current version of bootloader in my Moto G.
I want to try Lollipop 5.1 Optimized stock rom link here, so just wanted to ensure compatibility of bootloader so that my phone works after flashing it.
kalpesh.fulpagare said:
@lost101
Can you please let me know how to check bootloader version?
Click to expand...
Click to collapse
Enter bootloader (hold volume-down while turning it on), read text on screen (second line).
I too want to know if there is a way to downgrade or at least reflash my damaged bootloader which is causing weird behaviour.
Sent from my Nexus 6P using Tapatalk
I have the exact same problem.
Stuck on 41.1A
Was on a slim6 rom before. Tried to return to STOCK_ASIA_RETAIL. All fastboot commands successfully executed but no apparent change. I have the exact same wallpaper, the same layers RRO navbars, everything. I would not need to go to STOCK but since the slim installation is unstable and everything force closes, the phone is unusable.
Additional note: Somehow even TWRP is stuck in the splash screen, so cant flash any other ROM. Even tried to access TWRP using adb, but the TWRP service fails to start.
I fastboot flashed phillz recovery, stock recovery & newer TWRP versions, but nothing happens. Phone still stuck in TWRP screen.
To my surprise I was able to pull my personal files from the internal SD using ADB (which still works btw).
But I'm left with a phone in a zombie unusable condition, it just doesn't react to anything.
Any help from the XDA community would be greatly appreciated. I am still keeping my fingers crossed, so that one day a guide comes up to brick my device (STOCK 5.1 bootloader) and unbrick it using some sort of unbrick tool.
Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too
SLATE21&MOTOG said:
Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too
Click to expand...
Click to collapse
Creating such a zip is possible, but flashing it may either not work or hard brick your phone.
How to install working recovery on 41.1A bootloader
I had the situation on my Moto G XT1039 where I had formatted the partitions on my phone (using my old CWM recovery), then flashed the 41.1A bootloader, but 41.1A would not allow me to flash any recovery.
So I had a working bootloader, but no recovery and no OS. And apparently no way to install a recovery, to install an OS...
I got the phone back like this:
- Flashed 4.4.4 stock manually using the bootloader (if you do this, DO NOT flash the 4.4.4 motoboot.img, according to everything on here that will permanently brick your phone; I am not sure about partition gpt.bin - I flashed this, but I was already on the 4.4.4 partition layout anyway). Do flash boot.img, that is the OS boot.
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
From there I now had the correct recovery in place to flash the 5.1 Optimized distro (which I would definitely recommend - clean, stable, excellent battery life!).
Yay!
Bmju said:
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
Click to expand...
Click to collapse
Why didn't you simply fastboot flash a TWRP image?
_that said:
Why didn't you simply fastboot flash a TWRP image?
Click to expand...
Click to collapse
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.
Bmju said:
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.
Click to expand...
Click to collapse
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.
_that said:
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.
Click to expand...
Click to collapse
Thanks! I definitely tried that first! Maybe this bit I didn't make clear in my post, but actually:
- fastboot boot was only working for me with older recovery ROMS, i.e. the older CWM recovery which I mentioned, which I had lying around from when I first rooted my phone on 4.4.4, and also - not that it's much use - with the recovery in the 4.4.4 image, which just brings up the dead Android logo
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.
Bmju said:
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
Click to expand...
Click to collapse
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Bmju said:
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
Click to expand...
Click to collapse
That doesn't make any sense. Not that I don't believe you, I just can't explain how fastboot could fail writing recovery but succeed in writing a different partition.
Bmju said:
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.
Click to expand...
Click to collapse
Thanks for sharing your experience though, maybe it will help someone who has the same weird issue.
_that said:
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Click to expand...
Click to collapse
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)
Bmju said:
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)
Click to expand...
Click to collapse
Yes, I've got that one too, but my flashed recovery then worked fine. However I upgraded my bootloader by installing the complete 5.1 stock ROM, maybe your bootloader update was somehow incomplete.
I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.
mattlokk said:
I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.
Click to expand...
Click to collapse
Did you set:
Allow oem unlock in dev opt.
Fastboot protocol into BL?
Twrp app & manager need root to work.
Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link
thanks for the help, i'll try and work through this soon.
fpozar said:
Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link
Click to expand...
Click to collapse
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.
mattlokk said:
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.
Click to expand...
Click to collapse
Okay so I'm guessing you have stock ROM.
To flash TWRP you have to enter fastboot mode (vol down + power I believe) and flash the twrp image with fastboot flash recovery twrp.img (rename the shield tablet twrp to just twrp.img and place it into your easy adb and fastboot folder)
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck
fpozar said:
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck
Click to expand...
Click to collapse
Agreed. This is probably what is happening (as described on the TWRP webpage here:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Alternately, immediately rooting (flash SuperSU or Magisk) right after flashing TWRP, will prevent TWRP from being replaced with stock recovery.
Although the inconsistent fastboot connection, and how much trouble you had flashing TWRP initially, is a bit worrisome. Try using a different cable (maybe the one you are using is not connecting well?) try another USB port on the computer, and don't use a USB hub (connect direct to the PC).
Well, like they say: persistence is key. I kept pushing and trying new things until eventually.... I bricked the device. No, not really, it's working great now on LineageOS.
Thanks again to everyone who helped me out :good:. I'm still not sure exactly what caused TWRP to stop working on my device, however following this guide helped me fix it: https://forum.xda-developers.com/shield-tablet/help/help-stuck-nvidia-boot-screen-t3076462
The "flash-all.bat" restored everything to stock (including the recovery mode) and after that I was able to flash the latest TWRP and install Lineage.
I have a Honor 6x (BLN-L24) with EMUI 5+, Android Nougat, all updated. It is the U.S. edition. I unlocked the Bootloader, installed ADB / Fastboot tools and can flash the correct TWRP recovery image (3.1.1-0-berlin.img) but everytime I try to reboot into recovery, the standard EMUI recover overwrites TWRP and I just end up in the EMUI recovery.
I've looked at every forum I can find, articles, etc... but can't wrap my head around this one. If anyone with a similar experience and/or with a solution could help, I'd be most grateful.
Thank you!
I agree with with Rommco05. He IS correct, as I wondered the same thing till I realized to try unplugging it. Also make sure its the Power AND up buttons at same time. If you happen to hold only the up button it will take you to the erecovery feature where it trys hooking to WiFi for updates , which wont help you either.
Still doesn't work
Thanks for the responses. Unfortunately, unplugging doesn't do it either with the key combination you suggested. The following article is helpful for key combinations but alas, it still won't load into TWRP.
It is really strange as I can't even get past "Your device has been unlocked and can't be trusted" screen now. It just stays there...
Super frustrating. I didn't know if it had anything to do with my model being the BLN-L24 US version. I bought it at BestBuy unlocked.
Also, when I try to download "Latest Version and Recovery" from "Huawei eRecovery", I'm getting "Getting package info failed". I
Try OpenKirin twrp from recoveries section here on 6X forums
etmartinkazoo said:
Super frustrating. I didn't know if it had anything to do with my model being the BLN-L24 US version. I bought it at BestBuy unlocked.
Click to expand...
Click to collapse
That's not the cause. My phone is also a BLN-L24 purchased from Best Buy and I have no issues using TWRP. What did you do after you install TWRP? Did you let the phone just reboot or did you try to go into TWRP before rebooting?
This is straight from TWRP website:
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
Key combination timing?
galapagos said:
That's not the cause. My phone is also a BLN-L24 purchased from Best Buy and I have no issues using TWRP. What did you do after you install TWRP? Did you let the phone just reboot or did you try to go into TWRP before rebooting?
This is straight from TWRP website:
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
Click to expand...
Click to collapse
This is helpful, thank you. I found a page "Key Combinations Clarified for Honor 6x" which has a number of key combinations but nothing is helpful in my case that I know of. Do I use these key combinations imediately after the flash?
Is there a specific tutorial or guide that was helpful for you? I'd be grateful for any further assistance.
Thanks.
Rommco05 said:
You need enter to recovery? TWRP?
Click to expand...
Click to collapse
That is the problem, I'm unable to enter TWRP after flashing it, unplugging the usb cable, holding power/volume up...
Finally got Twrp installed. Rooted and installed custom Rom (lineageos) but when I reboot after flash screen, it's just blank...
If I were you, I would go completely back to stock and start over. Once you fastboot flash TWRP, it is imperative that you reboot back into TWRP before booting into the OS. Also, bootloaders don't overwrite recoveries. They are separate partitions, so your title is a bit misleading.
Regardless, you must still have stock recovery on your device since it is "defaulting" to that instead of TWRP. Like I said, it is extremely important to boot into recovery after you first flash it.
fastboot flash recovery recovery.img
let it do it's thing.
fastboot reboot recovery OR you can do it manually in TWRP right after the flash.
Have you tried rebooting to recovery from the system?
Connect your device to your computer, enable USB Debugging, and run
Code:
adb reboot recovery
from Windows CMD or Linux Shell, or any other one you prefer.
If this works, then you are doing the recovery key combination wrong.
Cheers
I'm having the same issue as OP. I have a BLN-L24 from Best Buy in the US. Reverted to emui 4.1 and android 6, unlocked bootloader, flashed twrp-3.2.1-0-berlin.img, and it keeps booting into huawei erecovery.
I didn't get any info on what the OP actually did to get twrp installed.
FWIW, there is no "fastboot reboot recovery"
FWIW2, you can't turn off the honor 6x from the bootloader. the best you can do is a hard reboot.
etmartinkazoo said:
That is the problem, I'm unable to enter TWRP after flashing it, unplugging the usb cable, holding power/volume up...
Click to expand...
Click to collapse
I'm having your exact same problem. I can get into fastboot mode, flash TWRP berlin, but I cannot enter TWRP after flash. It just goes back to the normal warning screen "this phone is unlocked", boot normally or go to EMUI recovery.
What worked for you?
hexag1 said:
I'm having your exact same problem. I can get into fastboot mode, flash TWRP berlin, but I cannot enter TWRP after flash. It just goes back to the normal warning screen "this phone is unlocked", boot normally or go to EMUI recovery.
What worked for you?
Click to expand...
Click to collapse
RedSkull fixed my problem!
Had a bad idea this morning and decided to try to root the phone, leagoo t5. The last time Im going to go messing with a phone that wasnt broken! after spending 10hrs trying to sort it! I downloaded adb tools and and twrp. I unlocked the bootloader with fastboot and installed twrp. However when I rebooted the phone it just booted straight into twrp. I cant get it to boot normally. I reinstalled the firmware but it will still not boot. I can get into recovery and factory modes but thats it. what can I do? Thanks
pcfreeze said:
Had a bad idea this morning and decided to try to root the phone, leagoo t5. The last time Im going to go messing with a phone that wasnt broken! after spending 10hrs trying to sort it! I downloaded adb tools and and twrp. I unlocked the bootloader with fastboot and installed twrp. However when I rebooted the phone it just booted straight into twrp. I cant get it to boot normally. I reinstalled the firmware but it will still not boot. I can get into recovery and factory modes but thats it. what can I do? Thanks
Click to expand...
Click to collapse
Have you tried factory resetting in recovery?
ktmom said:
Have you tried factory resetting in recovery?
Click to expand...
Click to collapse
Yes I did. No Joy. When I power on I just get the leagoo logo coming on and off repeatedly. Pressing the power button then will not turn the phone off again. I can switch it off by pressing vol- and pwr together though.
Is the problem caused by unlocking the bootloader with fastboot or that the firmware I installed is not suiting? Rebooting the phone after unlocking the bootloader before reflashing the firmware caused the leagoo logo to come on and off repeatedly accompanied by this message in very small text "Orange State - Your device has been unlocked and can't be trusted, Your device will boot in 5 seconds". After flashing the firmware with Sp Flash Tool this message is not being shown. Does reflashing firmware undo the action of unlocking the bootloader?
What your are describing is a bootloop. It sounds like the device can not find the system kernel to boot to. Did you boot the device after unlocking but before doing anything else?
Where did you get the TWRP recovery from?
Isn't this a mediatek chipset? If so, I think you need to use SP Flash Tool*to install.
I would look for a stock ROM for this device to revert to.
I'm not experienced on mediatek devices, but maybe @SubwayChamp could help.
pcfreeze said:
Yes I did. No Joy. When I power on I just get the leagoo logo coming on and off repeatedly. Pressing the power button then will not turn the phone off again. I can switch it off by pressing vol- and pwr together though.
Is the problem caused by unlocking the bootloader with fastboot or that the firmware I installed is not suiting? Rebooting the phone after unlocking the bootloader before reflashing the firmware caused the leagoo logo to come on and off repeatedly accompanied by this message in very small text "Orange State - Your device has been unlocked and can't be trusted, Your device will boot in 5 seconds". After flashing the firmware with Sp Flash Tool this message is not being shown. Does reflashing firmware undo the action of unlocking the bootloader?
Click to expand...
Click to collapse
Then to unlock bootloader is not normal that Android refuses to boot normally but when you flash a custom recovery or modify other partition this usually could happen so either or both you have to do a factory resetting/format data as @ktmom said or/and flash a kind of DM-verity for your device, this last avoids that bootloader checks the integrity of the partitions and can boot normally to system.
The warning message is normal then to unlock bootloader and reflashing the stock rom doesn´t relock it, you have to relock it at similar way that you unlocked it via fastboot command, most commom is "fastboot oem relock" but there are other variants and keep in mind that you have to return completely to stock before to apply it.
SubwayChamp said:
Then to unlock bootloader is not normal that Android refuses to boot normally but when you flash a custom recovery or modify other partition this usually could happen so either or both you have to do a factory resetting/format data as @ktmom said or/and flash a kind of DM-verity for your device, this last avoids that bootloader checks the integrity of the partitions and can boot normally to system.
The warning message is normal then to unlock bootloader and reflashing the stock rom doesn´t relock it, you have to relock it at similar way that you unlocked it via fastboot command, most commom is "fastboot oem relock" but there are other variants and keep in mind that you have to return completely to stock before to apply it.
Click to expand...
Click to collapse
I relocked the boot loader with the command "fastboot flashing lock". small white text dialogue on phone screen stated bootloader was locked successfully. rebooted phone then and it was still stuck in the boot loop. For a few seconds in between the leagoo logo a strange circular graphic was displayed on the phone with word "erasing" under it. What does this mean?
Can you tell me more about how to flash DM-verity?
pcfreeze said:
I relocked the boot loader with the command "fastboot flashing lock". small white text dialogue on phone screen stated bootloader was locked successfully. rebooted phone then and it was still stuck in the boot loop. For a few seconds in between the leagoo logo a strange circular graphic was displayed on the phone with word "erasing" under it. What does this mean?
Can you tell me more about how to flash DM-verity?
Click to expand...
Click to collapse
Ok, then to relock bootloader I guess that you did successfully boot to system again, right?
When you unlocked bootloader first then device is formatted to avoid a new user can access to the user´s data and when you relock it again the same happens.
As for DM-verity, newer devices strictly since nougat can´t boot to system after any partition was modified like happened when you flashed a custom recovery on it, here is when DM-verity can be useful, is used to avoid bootloader checks the integrity and allow a modified device can perform a reboot and more custom actions not officially permitted. You had to flash it through a custom recovery, sometimes flashing only Magisk is enough but not always.
You *might* be able to use this universal dm-verify script. It can be flashed only in a custom recovery and I'm not certain that is available to you.
ktmom said:
You *might* be able to use this universal dm-verify script. It can be flashed only in a custom recovery and I'm not certain that is available to you.
Click to expand...
Click to collapse
Good news and bad news! I got the phone to boot! I reinstalled twrp and the "magisk","no verity opt encrypt" and "disable dm verity" zips from the ext sdcard with fastboot. Twrp stated the zips installed ok but there were also some red line failure lines in the dialogue as they were being installed. I rebooted the phone via fastboot but this just resulted in it booting direct to twrp as before. I tried normal boot from twrp but it still booted straight back to twrp. I then tried selecting normal boot from the fastboot, normal, recovery option menu accessed on the Leagoo T5 by powering off the phone and then pressing the pwr and vol+ buttons together but this still resulted in it booting straight to twrp. I then decided to uninstall twrp by flashing the stock firmware recovery image to try to boot from stock recovery. I did same and rebooted from fastboot and it booted to system.
The bad news is there is an imei failure message and the sim is not connecting to the network.I googled imei failure and saw that its can happen when firmware is changed. I installed the "mobileuncle" app but according to a youtube video I watched, when I tap "Engineer Mode" there should be 2 further options available, one being MTK Mode. I am only getting one option "Engineering Mode (Android) which when I select just results in being returned to the previous menu. please say this is not a major problem!
@pcfreeze you quoted me, but as I said earlier, I'm not experienced with mediatek devices. You'd be better off quoting @SubwayChamp
pcfreeze said:
Good news and bad news! I got the phone to boot! I reinstalled twrp and the "magisk","no verity opt encrypt" and "disable dm verity" zips from the ext sdcard with fastboot. Twrp stated the zips installed ok but there were also some red line failure lines in the dialogue as they were being installed. I rebooted the phone via fastboot but this just resulted in it booting direct to twrp as before. I tried normal boot from twrp but it still booted straight back to twrp. I then tried selecting normal boot from the fastboot, normal, recovery option menu accessed on the Leagoo T5 by powering off the phone and then pressing the pwr and vol+ buttons together but this still resulted in it booting straight to twrp. I then decided to uninstall twrp by flashing the stock firmware recovery image to try to boot from stock recovery. I did same and rebooted from fastboot and it booted to system.
The bad news is there is an imei failure message and the sim is not connecting to the network.I googled imei failure and saw that its can happen when firmware is changed. I installed the "mobileuncle" app but according to a youtube video I watched, when I tap "Engineer Mode" there should be 2 further options available, one being MTK Mode. I am only getting one option "Engineering Mode (Android) which when I select just results in being returned to the previous menu. please say this is not a major problem!
Click to expand...
Click to collapse
It could be many reasons why device didn´t boot to system. Then to flash it you had to format data + flash DM-verity. Also is possible that this TWRP version is not completely suitable for your device or is unable to mount/unmount partitions correctly, you have to check from where you downloaded it and if some users are experiencing similar issues with it.
As per you IMEI lost, better is ever take a backup of the NVRAM through TWRP before to go further then it´ll be easy to recover it. In almost all firmwares for mediatek devices you´ll fnd inside the zips SPFT and SN Writer that is to recover your IMEI. Your IMEI is not really lost only got actually covered by blank codes due to a bad/incorrect flashing/wrong sequence firmware, so be careful what you do with Mobile Uncle tool if you´re not experimented with otherwise you´ll lost permanently.
SubwayChamp said:
It could be many reasons why device didn´t boot to system. Then to flash it you had to format data + flash DM-verity. Also is possible that this TWRP version is not completely suitable for your device or is unable to mount/unmount partitions correctly, you have to check from where you downloaded it and if some users are experiencing similar issues with it.
As per you IMEI lost, better is ever take a backup of the NVRAM through TWRP before to go further then it´ll be easy to recover it. In almost all firmwares for mediatek devices you´ll fnd inside the zips SPFT and SN Writer that is to recover your IMEI. Your IMEI is not really lost only got actually covered by blank codes due to a bad/incorrect flashing/wrong sequence firmware, so be careful what you do with Mobile Uncle tool if you´re not experimented with otherwise you´ll lost permanently.
Click to expand...
Click to collapse
I got into engineering mode via dialer code. CDS option was missing from connectivity. I installed https://m.apkpure.com/cds-mobile/com.doubleapaper.cds.cds_mobile but CDS is still missing from engineering mode
pcfreeze said:
I got into engineering mode via dialer code. CDS option was missing from connectivity. I installed https://m.apkpure.com/cds-mobile/com.doubleapaper.cds.cds_mobile but CDS is still missing from engineering mode
Click to expand...
Click to collapse
Sorry, just realised that this is the wrong app! nothing to do with cds in engineering mode! I triedhttps://apkcombo.com/common-data-service/com.mediatek.connectivity/
but got message that the file was corrupted and it would not install
I'm trying to install lineage OS 16 on my Sony Xperia Tablet Z LTE, in order for it to be up to date and able to use modern apps. I'm really not that tech savvy, but this far I've managed to unlock the bootloader, root the device and I believe I've managed to flash the recovery drive with the TWRP file meant for my device. I tried to flash the recovery from my windows PC, but every time I received "Failed "remote command not allowed" despite the device being unlocked at the bootloader and it is an A partition. So instead I went ahead and rooted the device and afterward flashed the tablet from the official TWRP app. At the end of the flash, I got "Flash completed successfully" which leads me to believe that I've flashed it correctly.
Now the issue is that no matter what I try, I can't boot into recovery mode. Every time I try, it just boots up regularly. I've tried via ADB terminal, through the TWRP app, and physically with the power button+volume down button, but everytime I get the same result.
This has me wondering, could I just download the Lineage image to my device and flash it directly to the boot partition or would this not work? Also what could be the reason I can't boot into recovery mode?
Sorry if this is not the forum for this topic, i just can't imagine who else would be able to advise me on this
luka0954 said:
I'm trying to install lineage OS 16 on my Sony Xperia Tablet Z LTE, in order for it to be up to date and able to use modern apps. I'm really not that tech savvy, but this far I've managed to unlock the bootloader, root the device and I believe I've managed to flash the recovery drive with the TWRP file meant for my device. I tried to flash the recovery from my windows PC, but every time I received "Failed "remote command not allowed" despite the device being unlocked at the bootloader and it is an A partition. So instead I went ahead and rooted the device and afterward flashed the tablet from the official TWRP app. At the end of the flash, I got "Flash completed successfully" which leads me to believe that I've flashed it correctly.
Now the issue is that no matter what I try, I can't boot into recovery mode. Every time I try, it just boots up regularly. I've tried via ADB terminal, through the TWRP app, and physically with the power button+volume down button, but everytime I get the same result.
This has me wondering, could I just download the Lineage image to my device and flash it directly to the boot partition or would this not work? Also what could be the reason I can't boot into recovery mode?
Sorry if this is not the forum for this topic, i just can't imagine who else would be able to advise me on this
Click to expand...
Click to collapse
Just to be sure, do you have USB debugging enabled?
Droidriven said:
Just to be sure, do you have USB debugging enabled?
Click to expand...
Click to collapse
I do, and of course I went and enabled it again after I bootloaded the device
Droidriven said:
Just to be sure, do you have USB debugging enabled?
Click to expand...
Click to collapse
You said you tried volume down+power, on most devices, that is the combination to boot into bootloader mode, fastboot mode or download mode, depending on the device. Volume up+power is generally the combination to boot into recovery mode. This doesn't seem to be your issue though. Are you sure you flashed TWRP to the correct partition? If your device is an A/B partitioned device, you may have flashed to one of these partitions when you needed to flash to the other partition.
Try flashing a copy of your stock recovery then see if that repairs the recovery partition and allows stock recovery to boot. If it works correctly after flashing stock recovery, you may not be flashing TWRP correctly or the actual flash might be being blocked by something that you're overlooking. Are you certain that your bootloader is unlocked?