So I had an unlocked H8 with LOS. As I wanted to install EMUI, I put the proper restore Update.app into the dload folder and started Huawei's recovery. Everything went well, I formated data and wanted to install the EMUI 4.1 ROM using the same method.
Unfortunately my H8 is bootlooping and there is now way into erecovery nor any other recovery. It simply reboots on every single known vol up or down key pressing combination. The only thing I can go to is fastboot mode when holding down vol down and plugging in usb wire. But, it says frd locked and I can't install nor boot twrp. It's simply gone and reboots all the time.
Any hints? I can't even turn it off.
I wanted to give away that phone that's the reason. Last time I did it this way, I could flash the EMUI 4.1 since it's signed. But not this time.
Interesting part is, that although fastboot says frd locked, I still get the "phone unlocked" warning on every reboot. dload method isn't working, as it simply keeps rebooting.
It's my hardest brick so far I ever encountered
the same thing happened to me.....on my phone lock/unlocked frp and bootloader were tweaked for some reason(I mean that what was written wasn't the reality) so how did I fix it? I kept on to flash rollback package many times and I tried to unlock/relock bootloader again, at the end the phone let me to flash the firmware, I didn't know how but the phone allowed me to flash things throw recovery(using dload method). At the begin I only could access to erecovery and fastboot. I suppose that I broke system and data partition and while I looked/unlocked the bootloader, the wipe fixed the partition table. Sorry I'm tired and I know that my English sucks, I hope you understand what I have written.
How did you enter erecovery as this isn't working for me.... What did you flash over fastboot?
Have you tried flashing the firmware separately using adb on computer?
For this you just need to extract the Update.app using the firmware extractor for huawei. Then flash them individually using adb commands in cmd.
I can't access any state that would allow to do adb.
faeArai said:
How did you enter erecovery as this isn't working for me.... What did you flash over fastboot?
Click to expand...
Click to collapse
sorry. I'll try to explain better, however on Huawei/honor devices there are not one but two recoveries, so one is the normal recovery flashed in recovery partition, the second one is the Huawei recovery that is flashed in recovery2 partition, so if you didn't touch recovery2 partition, your erecovery is still there, now, if you press VOL+ VOL- and POWER it will reboot to recovery2 and it starts to flash something from dload in your sd card, so in my opinion you should do this things, first try this method to flash rollback package(this is the transition package from 7 to 6 and you will find it on honor site) if this is still not working try locking and unlocking again your bootloader(I hope this fix partitions of your device) then try to enter recovery and do a wipe and then boot your device, if this doesn't work flash rollback package(now it would work) and then flash an emui 4 full firmware image, always using dload method. trust me... I did the same... and it worked for me. let me know if it works for you :good:
faeArai said:
So I had an unlocked H8 with LOS. As I wanted to install EMUI, I put the proper restore Update.app into the dload folder and started Huawei's recovery. Everything went well, I formated data and wanted to install the EMUI 4.1 ROM using the same method.
Unfortunately my H8 is bootlooping and there is now way into erecovery nor any other recovery. It simply reboots on every single known vol up or down key pressing combination. The only thing I can go to is fastboot mode when holding down vol down and plugging in usb wire. But, it says frd locked and I can't install nor boot twrp. It's simply gone and reboots all the time.
Any hints? I can't even turn it off.
Click to expand...
Click to collapse
I ran into this issue not that long ago. What you have to do is relock your bootloader using ADB. The ADB commands and instructions can be found in this thread.
Just a FYI, do not use the links to the software listed in that thread as it is a little outdated. The method still works but the software will probably not work. Just be sure to get the most recent/appropriate version of SuperSU and TWRP via their official threads (This is if you want to re-root). There are Honor 8 specific TWRP files if I remember correctly, so be sure to check around the Honor 8 forums for the correct files.
A quick summary of what I did:
1) Power your phone off and then boot into fastboot by holding Vol down + Power; as soon as it boots up, plug your phone into your combuter via your usb cord.
2) With ADB running, type:
Code:
fastboot oem relock [COLOR="LightBlue"]################[/COLOR]
NOTE: The '#' should be replaced with your unique unlock code that you obtained to unlock your bootloader.
3) Wait for it to format and reset your phone and go through the setup. BE SURE TO BYPASS all google registration; skip everything you can to get into the phone itself. If you do register, it will reactivate FRP and you'll have to start over again.
4) Turn on USB Debugging and every other setting that enables developer administrative navigation and control just to be safe. USB Debugging being the most important one, though.
5) Restart your phone and boot into fastboot again using Vol down + Power.
6) Unlock your phone again with:
Code:
fastboot oem unlock [COLOR="LightBlue"]################[/COLOR]
7) Once the command is entered, it'll reset your phone once more and - as stated before - bypass/skip all google (FRP) registration.
8) Enable developer options and USB debugging again and make sure that OEM Unlocked is checked and grayed out.
9) Reboot into fastboot mode to confirm that FRP is disabled and you should be able to install TWRP now via ADB.
@Numerics thanks. The thing is, that I can't boot anything. I can't even go into eRecovery. Nor can I flash a stock EMUI 4.1. It just boot loops all the time and I can only access fastboot.
If you can flash twrp..........Install los or other Rom ..................Go back to stock.......you must flash b360 ober adb...... because los is 7.1...............if you on b360 you can usw the rollback for emui 4.1........,..............sry for bad english
I can easily go to fastboot. But I can't flash anything. I extracted the img from the update.app but can't flash. It simply says that it's not permitted.
faeArai said:
I can easily go to fastboot. But I can't flash anything. I extracted the img from the update.app but can't flash. It simply says that it's not permitted.
Click to expand...
Click to collapse
With my method, you don't need to flash anything. Just relock your bootloader via adb in fastboot mode and let it reset. Unless I'm not understanding your issue entirely.
@Numerics as I said, in won't boot anything as it is constantly boot looping. There is no way to access any kind of recovery nor erecovery. There is no boot into Android. The only thing accessible right now is fast boot (which is not ADB). But even in fast boot I can't do anything als operations are not permitted.
after boot looping and starting fast boot mode, I can see a "Android reboot reason" section saying:
AP_S_PANIC
data is invalid
There is still a lineageos installed on system as firmware but as I tried to get rid of it by going back to stock EMUI, I guess Huawei's rollback did something wrong and killed recovery (although I did it in the past successfully).
I tried to run HiSuite to recover my phone, but it just says, that my phone is not supported.
Speaking of this, Huawei messed up with that whole fastboot locking bull****.
faeArai said:
@Numerics as I said, in won't boot anything as it is constantly boot looping. There is no way to access any kind of recovery nor erecovery. There is no boot into Android. The only thing accessible right now is fast boot (which is not ADB). But even in fast boot I can't do anything als operations are not permitted.
after boot looping and starting fast boot mode, I can see a "Android reboot reason" section saying:
AP_S_PANIC
data is invalid
There is still a lineageos installed on system as firmware but as I tried to get rid of it by going back to stock EMUI, I guess Huawei's rollback did something wrong and killed recovery (although I did it in the past successfully).
I tried to run HiSuite to recover my phone, but it just says, that my phone is not supported.
Speaking of this, Huawei messed up with that whole fastboot locking bull****.
Click to expand...
Click to collapse
No, I know ADB isn't Fastboot. What I'm trying to say is that you should be able to still run ADB via CMD on Windows when you're in fastboot mode to relock your bootloader with the directions I gave in my previous post. It'll force-restore your phone to a non-bricked/vanilla state. At least that is how I fixed mine.
Like... You can't even try using the 'fastboot oem relock ################' function via the ADB console while in fastboot?
yes boy trust us, you haven't a working OS so it is a normal thing that your phone reboot, you cannot access to recovery because some partitions are corrupted (data partition) , so these are the steps that could help you:
1) using fastboot, relock your boot loader
2)using fastboot, unlock your boot loader (partition table would be ok now, and you would be able to use load method to flash things trow stock recovery)
4)put inside your sd card \dload\update.app(use rollback package)
3) press all the buttons while your device is rebooting(do this before the blue screen logo appear), your phone is now looking for something inside your sd card
5) if the next step doesn't work do a factory reset from recovery that now would be working
6) put inside your sd card a full android 6 (emus 4) update.app and pressing all buttons it will install the firmware
7) your device now is locked and back to stock, maybe without cust partition or maybe in test mode but it is certainly alive
8) do a factory reset and reinstall the firmware
9) your phone is now ok
You don't lock the bootloader via ADB but via fastboot.
As I said, northing was restored and nothing is booting and I can't unlock my bootloader again. As I said, recovery is not working so the file in dload is not loaded and used. Which is strange.
Locking bootloader didn't do anything besides locking the bootloader. Device is still dead and I still can only access fastboot.
faeArai said:
You don't lock the bootloader via ADB but via fastboot.
As I said, northing was restored and nothing is booting and I can't unlock my bootloader again. As I said, recovery is not working so the file in dload is not loaded and used. Which is strange.
Locking bootloader didn't do anything besides locking the bootloader. Device is still dead and I still can only access fastboot.
Click to expand...
Click to collapse
Which model do u own?
Sent from my Honor 8 using XDA Labs
The European one.
faeArai said:
You don't lock the bootloader via ADB but via fastboot.
As I said, northing was restored and nothing is booting and I can't unlock my bootloader again. As I said, recovery is not working so the file in dload is not loaded and used. Which is strange.
Locking bootloader didn't do anything besides locking the bootloader. Device is still dead and I still can only access fastboot.
Click to expand...
Click to collapse
This is not the truth.....locking bootloader will erase all your data and fix partitions....and with fixed partition you can access to recovery ......trust me the only thing that you can do is to lock your bootloader......you can't flash anything from fastboot and boot recovery or system now...... lock your bootloader and then unlock it again, try using "fastboot OEM lock *****" or "fastboot OEM relock *******" (try cmd runned as admin, people say that this makes the difference) then unlock your device again and .....magic your recovery will boot......the same thing happened to me and I fixed my phone using this trick, however, even if you had frp unlocked it would say you that isn't possible to write anything because you broke some partition, and that's the reason why you can't boot recovery, wait one second and think: why doesn't my recovery boot?
It has nothing to do with trust. I did it and device is still a full stone brick. Nothing changed by locking the bootloader besides that now I can't unlock the bootloader anymore.
Related
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!
Hello
I have a Google pixel 128 GB device but recently it got bricked after an ota update. Unfortunately my phone is not rooted or unlocked. So I could not do anything under fastboot, also adb is crashed.
So the phone is bricked. But it can be rectified using QPST is edl mode I suppose. But as of now there is no such development for qpst for Google pixel.
But there are many users they face the same issue recently.
Is there any chance of development for it?
you said bootloader ! you mean the phone can boot into bootloader mode ! after that you said edl mode ? i dont understand. please explain. i may help !
*The Phone Goes into Fastboot with no problems.
*In Fastboot Mode if i try to go to Recovery, The Phone Reboots and does not go to the Recovery But it Keeps on Rebooting.
So the Recovery Partition of the Phone might be Corrupted.
So im looking for ways to Flash the Recovery partition with QPST or any other methods.
Fastboot Doesn't Help Because the Bootloader is locked.
senthil19 said:
*The Phone Goes into Fastboot with no problems.
*In Fastboot Mode if i try to go to Recovery, The Phone Reboots and does not go to the Recovery But it Keeps on Rebooting.
So the Recovery Partition of the Phone might be Corrupted.
So im looking for ways to Flash the Recovery partition with QPST or any other methods.
Fastboot Doesn't Help Because the Bootloader is locked.
Click to expand...
Click to collapse
Download factory image, open up the .sh script as text, copy the fastboot commands about wiping and clearing userdata, cache , etc into a terminal using fastboot
Xdevillived666 said:
Download factory image, open up the .sh script as text, copy the fastboot commands about wiping and clearing userdata, cache , etc into a terminal using fastboot
Click to expand...
Click to collapse
I do believe I've tried this to no avail on a Verizon g-2pw4100-022-b (the "b" probably stands for "brickable").
I'm stuck in the same situation:
Power+vol down - bootloader
Bootloader to recovery - boot loop
Bootloader to barcodes - barcodes show
Edit: power on only leads to constant screen flashing unless you hold volume down for bootloader, at which point you can vol up once and power down.
Can't flash a recovery, can't flash an OTA since that requires adb sideload, which is part of recovery, and can't flash a factory image with the bootloader locked, which is only unlocked under development tools.
One thing to note is that in the bootloader screen, both "b/l" and the one below it (radio?) both say "n/a", which leads me to believe the December update from Verizon could be the cause.
Suggestions as to how to proceed are greatly appreciated.
senthil19 said:
Hello
I have a Google pixel 128 GB device but recently it got bricked after an ota update. Unfortunately my phone is not rooted or unlocked. So I could not do anything under fastboot, also adb is crashed.
So the phone is bricked. But it can be rectified using QPST is edl mode I suppose. But as of now there is no such development for qpst for Google pixel.
But there are many users they face the same issue recently.
Is there any chance of development for it?
Click to expand...
Click to collapse
I have a Reddit thread how to activate qpst .
You can also "adb reboot edl" if your PC can recognize your phone at least.
If not, power button and volume up(or down, I don't remember) for at least forty seconds sometimes brings it up
But then you'd need firmware to flash with qpst and I'm not sure how to go about doing that
---------- Post added at 07:44 AM ---------- Previous post was at 07:42 AM ----------
PoXFreak said:
I do believe I've tried this to no avail on a Verizon g-2pw4100-022-b (the "b" probably stands for "brickable").
I'm stuck in the same situation:
Power+vol down - bootloader
Bootloader to recovery - boot loop
Bootloader to barcodes - barcodes show
Edit: power on only leads to constant screen flashing unless you hold volume down for bootloader, at which point you can vol up once and power down.
Can't flash a recovery, can't flash an OTA since that requires adb sideload, which is part of recovery, and can't flash a factory image with the bootloader locked, which is only unlocked under development tools.
One thing to note is that in the bootloader screen, both "b/l" and the one below it (radio?) both say "n/a", which leads me to believe the December update from Verizon could be the cause.
Suggestions as to how to proceed are greatly appreciated.
Click to expand...
Click to collapse
Can you fastboot boot twrp ?
Are there any solutions to enter EDL Mode in google pixel without adb?
Hey guys, my Honor is in brick state. I pushed a rollback package while I was in marshmallow (but with wrong ROM, so I was trying to rollback again and retry the procedure) and the phone got stuck in Honor blue screen at loop.
It won't let me power off, it justs turns on again. All button combinations won't work apparently. I can't get to recovery or e-recovery.
I tried depleting the battery. But as soon as I connect to the charger, it powers on. If I try the button combination before putting charge, it also doesn't work.
After the first successful rollback to MM, I think the bootloader got locked.
adb and fastbook can't seem to list the device.
I can get to fastboot and rescue mode, but I don't know the procedure from there.
So, is this a unsolvable brick? Or is there anything else that can be done to save this phone?
Thanks a lot for your feedback.
use dc unlocker to flash unlock bootloader and after dc flasher
valp88 said:
Hey guys, my Honor is in brick state. I pushed a rollback package while I was in marshmallow (but with wrong ROM, so I was trying to rollback again and retry the procedure) and the phone got stuck in Honor blue screen at loop.
It won't let me power off, it justs turns on again. All button combinations won't work apparently. I can't get to recovery or e-recovery.
I tried depleting the battery. But as soon as I connect to the charger, it powers on. If I try the button combination before putting charge, it also doesn't work.
After the first successful rollback to MM, I think the bootloader got locked.
adb and fastbook can't seem to list the device.
I can get to fastboot and rescue mode, but I don't know the procedure from there.
So, is this a unsolvable brick? Or is there anything else that can be done to save this phone?
Thanks a lot for your feedback.
Click to expand...
Click to collapse
It's easy. I had a similar problem too. Just when your phone attempts to boot, hold the Volume Down button and immediately connect it to the PC (within 1-2 second). It should go into fastboot mode. Now, open Huawei Multi Tool and unlock your bootloader then use the tool to unbrick your phone, start with flashing stock recovery and then the correct firmware.
SirDarknight said:
It's easy. I had a similar problem too. Just when your phone attempts to boot, hold the Volume Down button and immediately connect it to the PC (within 1-2 second). It should go into fastboot mode. Now, open Huawei Multi Tool and unlock your bootloader then use the tool to unbrick your phone, start with flashing stock recovery and then the correct firmware.
Click to expand...
Click to collapse
Thanks for repying. I unlocked my bootloader through fastboot and I'm trying to get multi-tool now!
i'm getting 404 from xda for the download link though.
SirDarknight said:
It's easy. I had a similar problem too. Just when your phone attempts to boot, hold the Volume Down button and immediately connect it to the PC (within 1-2 second). It should go into fastboot mode. Now, open Huawei Multi Tool and unlock your bootloader then use the tool to unbrick your phone, start with flashing stock recovery and then the correct firmware.
Click to expand...
Click to collapse
I flashed extracted and flashed images for B131 and B360, without luck. Stuck on the unlocked warning now: "Your device is booting now".
I can't seem to get to erecovery. Please let me know if you have any ideas.
valp88 said:
I flashed extracted and flashed images for B131 and B360, without luck. Stuck on the unlocked warning now: "Your device is booting now".
I can't seem to get to erecovery. Please let me know if you have any ideas.
Click to expand...
Click to collapse
If you're stuck on "Your device is booting now". This probably means your recovery is screwed. Don't worry, flash stock recovery and erecovery using Multi-Tool.
Then try the dload method. If the problem persists, then flash the correct TWRP then use HuRUpdater to flash the ROM you want. This will definitely fix the issue.
SirDarknight said:
If you're stuck on "Your device is booting now". This probably means your recovery is screwed. Don't worry, flash stock recovery and erecovery using Multi-Tool.
Then try the dload method. If the problem persists, then flash the correct TWRP then use HuRUpdater to flash the ROM you want. This will definitely fix the issue.
Click to expand...
Click to collapse
The recovery images from Multi-Tool servers seem to work! Thanks a lot. I was able to get to erecovery, now I'll proceed as decribed by you! :good::good::good:
Edit: dload failed at 99%, but I was able to factory reset and get to the system after all!
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?