After reading the news that a new method had been found for Verizon/EE-UK Google Pixel (Sailfish) Phones to unlock the Bootloader - I decided to do so and then proceed to flash Magisk for root and other benefits however as there was recently a new update which was showing as 'Failed to Install'.
Of cause I wanted to update the device so I attempted to re-lock the Bootloader using 'fastboot flashing lock' and proceeding to select Yes from the prompt. Which seemed to be acceptable and worked to lock the Bootloader.
Now my phone is stuck in a crazy boot-loop where by the phone will turn on - flash the Google logo on the white background for a split second then shut itself down and repeat.
Does anybody have any tips for me to recover the phone from this awful state?
Mr Ian said:
After reading the news that a new method had been found for Verizon/EE-UK Google Pixel (Sailfish) Phones to unlock the Bootloader - I decided to do so and then proceed to flash Magisk for root and other benefits however as there was recently a new update which was showing as 'Failed to Install'.
Of cause I wanted to update the device so I attempted to re-lock the Bootloader using 'fastboot flashing lock' and proceeding to select Yes from the prompt. Which seemed to be acceptable and worked to lock the Bootloader.
Now my phone is stuck in a crazy boot-loop where by the phone will turn on - flash the Google logo on the white background for a split second then shut itself down and repeat.
Does anybody have any tips for me to recover the phone from this awful state?
Click to expand...
Click to collapse
Man, when you lock the bootloader you need to make sure you're 100% back on stock without any modifications flashed. Seems to me you tried locking while having magisk flashed.
Try to see if you're able to get into recovery. Get into bootloader menu by pressing power button+volume down and the press volume upp until you get to recovery and then press power button. If you're able to get into recovery then download the full ota image for Google pixel sailfish from here https://developers.google.com/android/ota and then while you're in there should be an option to update using adb. You need to adb sideload the update from your computer to your phone. I know this should work on a non Verizon phone but I hope and assume that is what's needed this time. If you're not able to get into recovery and your bootloader is still locked then you pretty much have a bricked device.
Arju said:
Man, when you lock the bootloader you need to make sure you're 100% back on stock without any modifications flashed. Seems to me you tried locking while having magisk flashed.
Try to see if you're able to get into recovery. Get into bootloader menu by pressing power button+volume down and the press volume upp until you get to recovery and then press power button. If you're able to get into recovery then download the full ota image for Google pixel sailfish from here removed-link and then while you're in there should be an option to update using adb. You need to adb sideload the update from your computer to your phone. I know this should work on a non Verizon phone but I hope and assume that is what's needed this time. If you're not able to get into recovery and your bootloader is still locked then you pretty much have a bricked device.
Click to expand...
Click to collapse
At the minute I've taken it to a Phone shop hoping they will be able to figure a way to get to the recovery menu - baring in mind I had TWRP flashed.
Yeah, It will go to the Bootloader menu but when trying to go into recovery it will just repeat the same process as before where by it will flash the Google splash-screen then restart. Any notes on how to go about hard flashing the image?
have you tried fastboot boot twrp.img? does it bootloop aswell? if so, you might have hard bricked your pixel... last solution is to try flash stock image and then try again with stock recovery / twrp img.
Mr Ian said:
At the minute I've taken it to a Phone shop hoping they will be able to figure a way to get to the recovery menu - baring in mind I had TWRP flashed.
Yeah, It will go to the Bootloader menu but when trying to go into recovery it will just repeat the same process as before where by it will flash the Google splash-screen then restart. Any notes on how to go about hard flashing the image?
Click to expand...
Click to collapse
If you can't access stock recovery and your bootloader is locked then your device is pretty much hard bricked unfortunately. Don't think the phone shop would figure it out, they might change the motherboard as a solution if they don't have the right tools to reflash on a deeper level. Hope they figure it out. Please let us know if they managed to fix it. If not then someone else might have some suggestions. I'll try to think of something else.
Try either of these commands to see if you can unlock the bootloader again:
fastboot oem unlock
or
Code:
fastboot flashing unlock
And then try what the post above me suggests.
Hey, did you ever figure out a solution to this? I did the same thing to myself today...
any solution??
---------- Post added at 03:49 PM ---------- Previous post was at 03:48 PM ----------
Mr Ian said:
After reading the news that a new method had been found for Verizon/EE-UK Google Pixel (Sailfish) Phones to unlock the Bootloader - I decided to do so and then proceed to flash Magisk for root and other benefits however as there was recently a new update which was showing as 'Failed to Install'.
Of cause I wanted to update the device so I attempted to re-lock the Bootloader using 'fastboot flashing lock' and proceeding to select Yes from the prompt. Which seemed to be acceptable and worked to lock the Bootloader.
Now my phone is stuck in a crazy boot-loop where by the phone will turn on - flash the Google logo on the white background for a split second then shut itself down and repeat.
Does anybody have any tips for me to recover the phone from this awful state?
Click to expand...
Click to collapse
Did you managed to unlock it???
You can unlock the bootloader with htc-fastboot if you have a bricked android 7-8.
They patched it on Android 9.
On android 9 your only chance is to reflash it in edl mode. Anyone here who can help me to enter edl mode with my pixel?
Related
Hi, I really need your assistance for my pixel. I locked my bootloader after unrooting my phone. This process totally bricked my phone(I can't even get to the booting process of the phone) (I get a message saying that my phone is corrupt). I am able to gain access to my fastboot. So I was wondering if there was a way for me to flash the factory image to my phone and get it to work again. Please of there is anything you can do, please help me.
Its_joey_k23 said:
Hi, I really need your assistance for my pixel. I locked my bootloader after unrooting my phone. This process totally bricked my phone(I can't even get to the booting process of the phone) (I get a message saying that my phone is corrupt). I am able to gain access to my fastboot. So I was wondering if there was a way for me to flash the factory image to my phone and get it to work again. Please of there is anything you can do, please help me.
Click to expand...
Click to collapse
I'm really afraid there's nothing you can do. Before relocking the bootloader, you must go back to an approved stock firmware. (See, when you rooted it, you changed it.)
quangtran1 said:
I'm really afraid there's nothing you can do. Before relocking the bootloader, you must go back to an approved stock firmware. (See, when you rooted it, you changed it.)
Click to expand...
Click to collapse
I unrooted my device, so then after I can lock my bootloader. I'm just wondering if that's how I was supposed to do it.
If you have downloaded the full image from Google servers, try if you can fastboot using the boot image from the full image. It that boots your phone, you could try enabling unlock, get into fastboot to unlock for flashing. You can then flash the full image from unlocked fastboot
hackworks said:
If you have downloaded the full image from Google servers, try if you can fastboot using the boot image from the full image. It that boots your phone, you could try enabling unlock, get into fastboot to unlock for flashing. You can then flash the full image from unlocked fastboot
Click to expand...
Click to collapse
Is there any way you could lead my step by step. I don't want to screw up my phone even more. + I'm new to the community and don't know much.
You can use the fastboot continue command.
This will boot up your phone normally and then you will be able to go to developer settings and enable oem unlocking again.
After this you will be able to unlock from fastboot again.
http://forum.xda-developers.com/pixel/help/accomplished-hardbricked-pixel-d-t3516717
Its_joey_k23 said:
Is there any way you could lead my step by step. I don't want to screw up my phone even more. + I'm new to the community and don't know much.
Click to expand...
Click to collapse
If you can put your phone in fastboot mode, you're not bricked yet.
hackworks said:
If you have downloaded the full image from Google servers, try if you can fastboot using the boot image from the full image. It that boots your phone, you could try enabling unlock, get into fastboot to unlock for flashing. You can then flash the full image from unlocked fastboot
Click to expand...
Click to collapse
You saved my life! Thank you.
Hi guys.
My issue: I had TWRP 3.0.2.1 on my honor and decided to update to latest version. Big error.
I have the TWRP app installed and I followed the procedure to flash recovery with that app. It seemed everything was fine, because it said ""recovery flashed".
Now when I try to enter recovery, my phone gets stuck at logo "your device is booting now".
I have to reboot in EMUI recovery to go out from that stuck page and to load normally the phone.
So I decided to flash recovery in the old ADB fashioned way: now when I get to "fastboot flash recovery twrp.img", the phone tells me "FAILED (remote: Command not allowed)"
Practically now I have no TWRP and I do not know how to proceed.
Some good Samaritan out there?
Thanks.
My firmware is latest Nougat (BLN-L21C432B360).
I tried to flash TRWP 3.1.1. Before this try, I had version 3.0.2-1 as written above. I flashed twrp when I still had Android 6 with EMUI 4.
Regarding the way to enter TWRP, yes, I know the method and I do it.
The problem is my phone don't enter twrp but remain stuck at logo.
It seems that the recovery is not present or has problems.
I've tried even to reflash the old recovery, just in case. Nothing.
Try this-
flash stock recovery for your model.
boot normally.
flash TWRP latest.
Now I try and post later.
What a mess. I should leave the old 3.0.2 which was working good...
I was already on nougat and the 3.0.2 was still working perfectly. I had flashed that twrp when I was still on 6.0 and after the update with firmware finder it was still working.
Moreover I used the official TWRP app to update and it failed miserably even if it said flash successful at the end of operation....
Then I used the classic way with ADB and still nothing.
I can see on the Windows shell "failed: command not allowed"
Rommco05 said:
Frp in fastboot is unlocked?
Click to expand...
Click to collapse
AFAIK, Factory Reset Protection is linked to account protection in case someone steals the phone. In this way it should be more difficult to wipe completely the phone and use it.
Anyway, just checked in fastboot and no, FRP is locked. I just had a look in developer options and I noticed that "Enable OEM unlocked" is greyed out. But it should not have nothing to do with flashing the recovery.
Or not?
Let's see
Diamantes said:
Hi guys.
My issue: I had TWRP 3.0.2.1 on my honor and decided to update to latest version. Big error.
I have the TWRP app installed and I followed the procedure to flash recovery with that app. It seemed everything was fine, because it said ""recovery flashed".
Now when I try to enter recovery, my phone gets stuck at logo "your device is booting now".
I have to reboot in EMUI recovery to go out from that stuck page and to load normally the phone.
So I decided to flash recovery in the old ADB fashioned way: now when I get to "fastboot flash recovery twrp.img", the phone tells me "FAILED (remote: Command not allowed)"
Practically now I have no TWRP and I do not know how to proceed.
Some good Samaritan out there?
Thanks.
Click to expand...
Click to collapse
Unlock your boot loader
Bootloader is unlocked.
For some reason, my "OEM unlocked" option turned greyed out, and FRP is locked again.
I will try this eve to lock bootloader again and restart the unlocking operation from scratch.
Will see
Diamantes said:
Bootloader is unlocked.
For some reason, my "OEM unlocked" option turned greyed out, and FRP is locked again.
I will try this eve to lock bootloader again and restart the unlocking operation from scratch.
Will see
Click to expand...
Click to collapse
In emui 5 OEM unlock option is not there and can only be found in MM or Emui 4.x
you mean that even if I can't access TWRP, this should be still there and I cannot lock bootloader?
And you advice to do a factory reset first.
If this doesn't work? Then?
shashank1320 said:
In emui 5 OEM unlock option is not there and can only be found in MM or Emui 4.x
Click to expand...
Click to collapse
You mean that I couldn't even see the option?
I have nougat and emui 5, the option is present but greyed out
Diamantes said:
You mean that I couldn't even see the option?
I have nougat and emui 5, the option is present but greyed out
Click to expand...
Click to collapse
Yeah exactly. See SS
This was there till emui 4
So how can I solve the problem?
Someone told me the only way is to lock bootloader in order to have again this option available to be turned on... And so start the process again.
At the moment I cannot access TWRP nor flash it through ADB. Practically even if bootloader is unlocked, I have a rooted phone with no possibility to do anything else... Regarding flashing of course.
Thank you for your replies.
Anyway I really know now that I cannot buy honor for flashing.
I just tried a factory reset from advanced options.
After all the pin request etc, the phone rebooted and get stuck on the initial window (your phone has been unlocked and cannot be trusted-your phone is booting now...).
So I had to press usual buttons to enter in emui recovery, the only way I can get the rebooting option from this state.
Of course the phone is not reset.
I give up. This crappy phone is taking too much time of my life.
I will keep it like this. And I'm not sure at all I will get future OTA update.
I never EVER had these issues with Samsung phones or HTC, and believe me that I was flashaholic... I flashed tens and tens of ROMs, I rooted and unlocked all my previous phones with no glitches or whatever..,
This time I tried honor for the price.
Never again for flashing or playing around.
Just for normal, classic phone use, hoping it will last some other month before I purchase another brand.
Thank you all.
Of course my thoughts about this ****ty phone were all right.
I received the ota update for version b365, downloaded and OF COURSE STUCK at boot logo after automatic restart...
I will never be able to install anything else because the recovery is corrupted.
I am condemned to stay with b360 until this cursed phone will die for natural causes...
No comment
Diamantes said:
Of course my thoughts about this ****ty phone were all right.
I received the ota update for version b365, downloaded and OF COURSE STUCK at boot logo after automatic restart...
I will never be able to install anything else because the recovery is corrupted.
I am condemned to stay with b360 until this cursed phone will die for natural causes...
No comment
Click to expand...
Click to collapse
But recovery can be changed mate. Try twrp with new thread in my signature and follow steps, it won't be a trouble. Try once in free time as i know you already are frustrated with trying all ways.
The TWRP on official TWRP site sadly won't work for our berlin devices, i neither know why it is still there sincerely. Personally i can't recommend the usage of TWRP official app for our phone as it downloads a wrong version... you have to get the OpenKirin edition from here https://forum.xda-developers.com/honor-6x/development/twrp-t3583413 and flash that via adb fastboot. Be sure to have "USB debug" on by developer options menu, and to have installed HiSuite (just to have all the functional drivers)
I thank you all for your patience and replies.
But as Shashank said, I'm really frustrated because I tried everything in the past.
Now I'm rooted (luckily) but with FRP locked. It seems the reason why I cannot flash nothing.
In any case I will try again the suggestion of redskull. The last hope!
Thanks.
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?
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
Tried to follow this guide to root my pixel 4a and completed all steps up to 3.4. My phone is now stuck in fastboot mode and I can't get into recovery mode to do a factory reset. Not sure what to do, I'm a little lost. I accidentally used this or this image for Android 10 when I think I should have used this image for Android 11.
Any help would be very appreciated.
Maybe you can use this guide:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
And start on this line in "First Step" section:
Plug the phone into a usb port of your pc.
Then complete all the tasks in "Second Step" section to get your phone at least booting in android 10.
ifixibrick said:
Tried to follow this guide to root my pixel 4a and completed all steps up to 3.4. My phone is now stuck in fastboot mode and I can't get into recovery mode to do a factory reset. Not sure what to do, I'm a little lost. I accidentally used this or this image for Android 10 when I think I should have used this image for Android 11.
Any help would be very appreciated.
Click to expand...
Click to collapse
Run the online flash tool from bootloader screen bro. Make sure you install adb and fastboot tools.
Raj Pandiyan said:
Run the online flash tool from bootloader screen bro. Make sure you install adb and fastboot tools.
Click to expand...
Click to collapse
How do I do that? I seem to be stuck in fastboot mode.
ifixibrick said:
How do I do that? I seem to be stuck in fastboot mode.
Click to expand...
Click to collapse
Is it bricked? Cannot flash stock Android to remove ArcaneOS
I recently purchased a used Pixel 4a, and I now understand why the seller was offering such good price for it and why he refused to respond to me now I have it. This phone has ArcanseOS 10 installed, which has only 3 apps installed... Setting...
forum.xda-developers.com
reboot to recovery, press volume up + power to bring up the recovery settings, turn on sideloading
then adb sideload the factory image.
jawz101 said:
reboot to recovery, press volume up + power to bring up the recovery settings, turn on sideloading
then adb sideload the factory image.
Click to expand...
Click to collapse
Hello. Currently stuck in fastboot mode. Using the volume buttons to select recovery mode and pressing the power button to go into it doesn't take me to recovery mode. The screen briefly goes dark before entering fastboot again. I think the phone is trying to restart but not getting past fastboot mode.
ifixibrick said:
Hello. Currently stuck in fastboot mode. Using the volume buttons to select recovery mode and pressing the power button to go into it doesn't take me to recovery mode. The screen briefly goes dark before entering fastboot again. I think the phone is trying to restart but not getting past fastboot mode.
Click to expand...
Click to collapse
Can you type fastboot reboot recovery and get into recovery mode? You'll see a little Android guy with a red thing if you're in there.
If that doesn't work- it almost sounds as though your recovery partition is deleted or something. You can reflash the recovery from fastboot.
Hey, I had the same problem. I've got it resolved now and wasn't able to find any help on how to resolve it, but this thread is as close as it came, so in the off chance that somebody else comes along, I thought I'd write up the steps I took.
Because it was in fastboot mode, I was able to easily restore my phone to factory settings by running flash factory image script I downloaded here.
My original image was sunfish-rq3a.210605.005-factory-be541467 which I followed the steps with but couldn't get it to work. I got to the Google logo with a status bar that just ran forever. But the flash-all.sh script worked to get the phone booting again.
So what I did to get Magisk to work was to use that same factory image site to download an older version. I used a version that was listed in a different root guide with the idea that maybe the version I tried before wasn't compatible with magisk, but presumably the one from the guide was. So I tried sunfish-rq1a.210105.002, ran the flash-all in fastboot, and confirmed that it booted--it did.
Next I redid 2.2 through 3 and it worked, and the boot completed with Magisk installed. Everything seems to be working fine now.