I got a 6a today, with the intent of learning about rooting. I've never rooted before, but was pretty involved with iOS jailbreaking so kinda a similar vein.
I wanted to get to Android 13 to get a fresh start (as opposed to rooting on A12 and upgrading), so i downloaded the factory image. I used the flash-all.sh script, but it got stuck on "Rebooting into fastboot." It then booted into the "Your Device Is Corrupt" screen, and would get stuck on the Google logo when it was booting. I finally got the A13 factory image to boot, but the "Your Device Is Corrupt" screen still showed every time i boot *as long as the bootloader is unlocked*. When I lock the bootloader it seems to be fine. After talking to a couple friends that have been rooting for a while, they somewhat think that I've done something to the NAND and should send back the device for a replacement. I'm not sure what to do now. Any suggestions?
You're fine...all androids have a warning screen after being unlocked.
Zaxx32 said:
You're fine...all androids have a warning screen after being unlocked.
Click to expand...
Click to collapse
I hear you, but this is a prompt that showed before the typical bootloader warning. It says "Your device is corrupt. It can't be trusted and may not work properly. Visit this link on another device: https://g.co/ABH"
If I click the power button it continues on the the regular bootloader warning
My friends who have been rooting for years say that this is irregular and shouldn't happen aside from the first boot. It happens every single boot as long as the bootloader is unlocked
CobreDev said:
I hear you, but this is a prompt that showed before the typical bootloader warning. It says "Your device is corrupt. It can't be trusted and may not work properly. Visit this link on another device: https://g.co/ABH"
If I click the power button it continues on the the regular bootloader warning
My friends who have been rooting for years say that this is irregular and shouldn't happen aside from the first boot. It happens every single boot as long as the bootloader is unlocked
Click to expand...
Click to collapse
That specific "corrupt" message you are getting when your bootloader is unlocked sounds more ominous than it really is. If you peruse through the Pixel 6 and 6 Pro forums you'll see that many people have encountered this message without any negative side effects and there are a few ways to get rid of it. In the simplest terms it's basically just a hash mismatch.
One method that seems to work well is to sideload the OTA during the next update. Even just updating via the "normal" OTA may get rid of the corrupt message.
Lughnasadh said:
That specific "corrupt" message you are getting when your bootloader is unlocked sounds more ominous than it really is. If you peruse through the Pixel 6 and 6 Pro forums you'll see that many people have encountered this message without any negative side effects and there are a few ways to get rid of it. In the simplest terms it's basically just a hash mismatch.
One method that seems to work well is to sideload the OTA during the next update. Even just updating via the "normal" OTA may get rid of the corrupt message.
Click to expand...
Click to collapse
Ah interesting, so probably not corrupted NAND then. One friend told me to go ahead and sideloaded the Android 13 OTA (I’m on Android 13 currently), but i noticed in the root guide it specifically said *don’t* sideloaded the ota before rooting. If i sideloaded the A13 OTA now will i mess up anything for rooting, or should i just live with the error until the next update?
CobreDev said:
Ah interesting, so probably not corrupted NAND then. One friend told me to go ahead and sideloaded the Android 13 OTA (I’m on Android 13 currently), but i noticed in the root guide it specifically said *don’t* sideloaded the ota before rooting. If i sideloaded the A13 OTA now will i mess up anything for rooting, or should i just live with the error until the next update?
Click to expand...
Click to collapse
Nah you NAND is fine.
The very first thing you should do before doing anything is make sure you have flashed the A13 bootloader to both slots to avoid having problems with the new ARB and bricking your device, if you haven't already.
Not sure what root guide you are referring to and in what context they are saying that, but sideloading an OTA shouldn't mess anything up relating to being able to root. It's really up to you what you do. You can live with that message for another couple of weeks (Sept. 6 is when the next stable update should be released), sideload the OTA or even dirty flash the factory image again (that might get rid of the message).
But whatever you decide to do, don't forget to flash the A13 bootloader to both slots before anything!!! I've seen a handful of people already brick their phone because they did not do this.
Lughnasadh said:
Nah you NAND is fine.
The very first thing you should do before doing anything is make sure you have flashed the A13 bootloader to both slots to avoid having problems with the new ARB and bricking your device, if you haven't already.
Not sure what root guide you are referring to and in what context they are saying that, but sideloading an OTA shouldn't mess anything up relating to being able to root. It's really up to you what you do. You can live with that message for another couple of weeks (Sept. 6 is when the next stable update should be released), sideload the OTA or even dirty flash the factory image again (that might get rid of the message).
But whatever you decide to do, don't forget to flash the A13 bootloader to both slots before anything!!! I've seen a handful of people already brick their phone because they did not do this.
Click to expand...
Click to collapse
Alright, i’ll try sideloading the OTA. I’ve tried flashing the factory image several times and it hasn’t fixed it.
To flash the bootloader to both slots, i follow the instructions on the Factory Image download page where it says:
# If your active slot is ‘a’
fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot set_active b
fastboot reboot bootloader
fastboot set_active a
fastboot reboot bootloader
fastboot reboot
# If your active slot is ‘b’
fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot set_active a
fastboot reboot bootloader
fastboot set_active b
fastboot reboot bootloader
fastboot reboot
Is that correct? Thanks for your help!
CobreDev said:
Alright, i’ll try sideloading the OTA. I’ve tried flashing the factory image several times and it hasn’t fixed it.
To flash the bootloader to both slots, i follow the instructions on the Factory Image download page where it says:
# If your active slot is ‘a’
fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot set_active b
fastboot reboot bootloader
fastboot set_active a
fastboot reboot bootloader
fastboot reboot
# If your active slot is ‘b’
fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot set_active a
fastboot reboot bootloader
fastboot set_active b
fastboot reboot bootloader
fastboot reboot
Is that correct? Thanks for your help!
Click to expand...
Click to collapse
No problem and yep, that's correct. Just make sure you don't boot into the slot which still has A12 on it. Good luck!
CobreDev said:
Alright, i’ll try sideloading the OTA. I’ve tried flashing the factory image several times and it hasn’t fixed it.
To flash the bootloader to both slots, i follow the instructions on the Factory Image download page where it says:
# If your active slot is ‘a’
fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot set_active b
fastboot reboot bootloader
fastboot set_active a
fastboot reboot bootloader
fastboot reboot
# If your active slot is ‘b’
fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot set_active a
fastboot reboot bootloader
fastboot set_active b
fastboot reboot bootloader
fastboot reboot
Is that correct? Thanks for your help!
Click to expand...
Click to collapse
Slight correction in case you haven't done it already. They instruct you to go use "adb reboot fastboot" at the beginning. That is wrong because that will put you in fastbootd and you can't flash the bootloader from fastbootd. Instead, at the beginning use "adb reboot bootloader". This is if you use Option 2 in their directions.
Lughnasadh said:
Slight correction in case you haven't done it already. They instruct you to go use "adb reboot fastboot" at the beginning. That is wrong because that will put you in fastbootd and you can't flash the bootloader from fastbootd. Instead, at the beginning use "adb reboot bootloader". This is if you use Option 2 in their directions.
Click to expand...
Click to collapse
Figured that out, thanks. Unfortunately sideloading the OTA didn't fix it, so i'll wait for the september update to see if that fixes it. Thanks everyone for the help!
CobreDev said:
Figured that out, thanks. Unfortunately sideloading the OTA didn't fix it, so i'll wait for the september update to see if that fixes it. Thanks everyone for the help!
Click to expand...
Click to collapse
Did you manage to solve the problem? If you still have not got it I will tell you that the same thing happened to me and I tried to flash in all ways and in both slots without getting it and in the end I managed to solve it by flashing the latest rom with the pixel flasher, checking the option to flash in both slots and checking the two boxes "disable verity and disable (anotherone)", at the end of the flashing I did not get back what was corrupt, I hope it helps you, greetings and good luck!
dannyzamora said:
Did you manage to solve the problem? If you still have not got it I will tell you that the same thing happened to me and I tried to flash in all ways and in both slots without getting it and in the end I managed to solve it by flashing the latest rom with the pixel flasher, checking the option to flash in both slots and checking the two boxes "disable verity and disable (anotherone)", at the end of the flashing I did not get back what was corrupt, I hope it helps you, greetings and good luck!
Click to expand...
Click to collapse
i haven’t fixed it yet, because the September update hasn’t come out for Pixel 6a.
I’ll keep that in mind, thanks for the tip!
CobreDev said:
i haven’t fixed it yet, because the September update hasn’t come out for Pixel 6a.
I’ll keep that in mind, thanks for the tip!
Click to expand...
Click to collapse
Try with the last update
CobreDev said:
i haven’t fixed it yet, because the September update hasn’t come out for Pixel 6a.
Click to expand...
Click to collapse
??? It came out earlier this week. https://developers.google.com/android/images#bluejay
Ah, must've missed that thanks
CobreDev said:
Ah, must've missed that thanks
Click to expand...
Click to collapse
Did you manage to solve it?
dannyzamora said:
Did you manage to solve it?
Click to expand...
Click to collapse
I did, though fixed it by accidentally wiping it out. Oh well, it’s fixed now
CobreDev said:
I did, though fixed it by accidentally wiping it out. Oh well, it’s fixed now
Click to expand...
Click to collapse
Good news! Congratulations
Just got, just rooted, now on A13 Oct. and looking to "fix" this screen shouting to anyone who sees my phone boot, "come and get lunch".
Is this still the way?
ty
jackfrost909 said:
Just got, just rooted, now on A13 Oct. and looking to "fix" this screen shouting to anyone who sees my phone boot, "come and get lunch".
Is this still the way?
ty
Click to expand...
Click to collapse
Unless there's an FBI agent out to get you, nobody will care. Most people won't even know what an unlocked bootloader is. If you're scared of hackers so much, reflash stock and relock
Related
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
spacezork said:
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
Click to expand...
Click to collapse
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
the ljubich said:
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
Click to expand...
Click to collapse
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
spacezork said:
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
Click to expand...
Click to collapse
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
the ljubich said:
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
Click to expand...
Click to collapse
Sorry for my confusion with adb/sideload - from what I understand I need both to be able to connect to my device (correct me if im wrong). In the bootloader menu I see "flashing_unlocked" which I believe confirms my bootloader being unlocked, but then at the top of the text right under the dead android guy I see "AP Fastboot Flash Mode (Secure)" could that be an issue?
I can retry downloading the recovery from the TWRP site, but I know I'm downloading the official one already, just can't put my finger on why I'm getting that error message if others are doing it successfully.
thanks for helping :good:
Do you have the Verizon model?
samwathegreat said:
Do you have the Verizon model?
Click to expand...
Click to collapse
I have the canadian BELL model XT1650-03
spacezork said:
I have the canadian BELL model XT1650-03
Click to expand...
Click to collapse
You're at the bootloader, it says Flashing Unlock so yes your bootloader is unlocked and you should be able to flash TWRP no problem.
Did you recently install this .45 firmware? Are you sure that TWRP wasnt actually flashed? I see lots of errors like this from the bootloader and its usually just rubbish.
The twrp does not show the actual memory value of my cell phone and does not let me paste ROM backup, from insufficient memory? how to support it?
I updated my phone to .45 when I bought the phone I believe 1-2 weeks ago, it's definitely NOT flashed as the flashing process runs for 0.2 seconds and fails. I can even boot in the stock recovery afterwards confirming that nothing flashed. I wish I knew what I was doing wrong? possibility of drivers not installed properly?
Before I try and flash recovery I check USB debugging, OEM is unlocked, don't verify ADB files and accept Unknown sources. Is there anything I'm missing?
What if fastboot boot twrpname.img
It's really weird anyway...
enetec said:
What if fastboot boot twrpname.img
It's really weird anyway...
Click to expand...
Click to collapse
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
spacezork said:
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
Click to expand...
Click to collapse
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
enetec said:
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
Click to expand...
Click to collapse
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
spacezork said:
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
Click to expand...
Click to collapse
Right, bootloader screen. Enter on it by key-comb... not by command...
Even the real flash take same time... Sending seems to work, is something on verify that doesn't "like" it...
Try to download again recovery and/or check its MD5...
if reading correctly (and what I told you yesterday) command is
fastboot flash recovery recovery.img
and not
fastboot flash recovery.img
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Troll amiga said:
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Click to expand...
Click to collapse
try following this instructions: http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
and download eu rom from here: https://mirrors.lolinet.com/firmware/moto/griffin/official/RETEU/
i don't know from which ROM you are coming, don't know if downgrading works, but this was onl RETEU ROM i could find.
I have the exact same phone and I've upgraded to Nougat but I got my TWRP working. You need an unlocked bootloader and after upgrading to nougat, the option "unlock OEM" need to be enabled again.
I've used this TWRP : https://dl.twrp.me/griffin/twrp-3.0.2-0-griffin.img.html
Also I tried to only boot on it at first with the command fastboot boot twrp.img then I saw it was working, I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
cilk said:
...I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
Click to expand...
Click to collapse
Yeessss... I don't know how could I forgot it!!! :silly:
The message (I forgot I received too...) is *only* to indicate that recovery is not signed! But before there is a clear "Done" confirming the flash!
Just boot on it!
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.
Hey guys, so I recently tried re-locking my bootloader in hopes it would just factory reset my device so I could start fresh.
I used
Code:
fastboot oem lock
to lock the bootloader but now I'm stuck at the fastboot screen with this message:
Code:
"ERROR: Slot Unbootable: Load Error"
I cannnot boot into recovery or anything.
Not sure if this means anything but when I use:
Code:
fastboot flashing unlock_critical
I get:
Code:
FAILED (remote: Device already : unlocked!)
But when I try flashing or changing boot slots it says its locked?
Update: I tried using https://forum.xda-developers.com/pixel-xl/development/tool-skipsoft-android-toolkit-google-t3482767 Skipsoft's tool to unlock the bootloader but it says its already unlocked... but when I try to check if it is locked with the same tool it says it locked...?
Anyways I want to see if I can get this fixed, if not I'll try to get it RMA'd. But I really want to fix it. Thanks!
QUICK UPDATE:
Google Issued an RMA on Jan 25th
Jan 31, Received new sealed Pixel 2
VmX5 said:
Hey guys, so I recently tried re-locking my bootloader in hopes it would just factory reset my device so I could start fresh.
I used
to lock the bootloader but now I'm stuck at the fastboot screen with this message:
I cannnot boot into recovery or anything.
Not sure if this means anything but when I use:
I get:
But when I try flashing or changing boot slots it says its locked?
Update: I tried using https://forum.xda-developers.com/pixel-xl/development/tool-skipsoft-android-toolkit-google-t3482767 Skipsoft's tool to unlock the bootloader but it says its already unlocked... but when I try to check if it is locked with the same tool it says it locked...?
Anyways I want to see if I can get this fixed, if not I'll try to get it RMA'd. But I really want to fix it. Thanks!
Click to expand...
Click to collapse
What version?
D3RP_ said:
What version?
Click to expand...
Click to collapse
Thanks for replying,
I was running Android 8.10 the Januaray update, I had the default recovery, and the latest version of ADB.
For Skipsoft's program it was the latest version on their website.
I would try to flash the factory image using the flash-all batch script in an unlocked state.
enzyne said:
I would try to flash the factory image using the flash-all batch script in an unlocked state.
Click to expand...
Click to collapse
I'm not sure how to get to that unlocked state, the device can't flash anything with the bootloader locked.
VmX5 said:
I'm not sure how to get to that unlocked state, the device can't flash anything with the bootloader locked.
Click to expand...
Click to collapse
Just go into the bootloader then run the flash-all from Google factory image
ahoslc said:
Just go into the bootloader then run the flash-all from Google factory image
Click to expand...
Click to collapse
I have, the script ends up saying operation is not allowed in locked state
VmX5 said:
Hey guys, so I recently tried re-locking my bootloader in hopes it would just factory reset my device so I could start fresh.
I used
Code:
fastboot oem lock
to lock the bootloader but now I'm stuck at the fastboot screen with this message:
Code:
"ERROR: Slot Unbootable: Load Error"
I cannnot boot into recovery or anything.
Not sure if this means anything but when I use:
Code:
fastboot flashing unlock_critical
I get:
Code:
FAILED (remote: Device already : unlocked!)
But when I try flashing or changing boot slots it says its locked?
Update: I tried using https://forum.xda-developers.com/pixel-xl/development/tool-skipsoft-android-toolkit-google-t3482767 Skipsoft's tool to unlock the bootloader but it says its already unlocked... but when I try to check if it is locked with the same tool it says it locked...?
Anyways I want to see if I can get this fixed, if not I'll try to get it RMA'd. But I really want to fix it. Thanks!
Click to expand...
Click to collapse
Try Deuces Tool. May work.
I had all sort of weird fastboot failures when my Pixel 2 was connected to a USB Type C port, when I changed to a Type A port, fastboot started working again. Maybe it's your case as well?
D3RP_ said:
Try Deuces Tool. May work.
Click to expand...
Click to collapse
Thanks for replying,
I've tried that, it's a great script btw. But still doesn't work, still can't flash with bootloader locked.
paulomario77 said:
I had all sort of weird fastboot failures when my Pixel 2 was connected to a USB Type C port, when I changed to a Type A port, fastboot started working again. Maybe it's your case as well?
Click to expand...
Click to collapse
Thanks for replying, Good suggestion but can't be. On my laptop there are 2 USB 3.0 ports and 1 USB 2.0 port the Pixel only connects when I use the USB 2.0 port and won't work when I use the USB 3.0 port.
VmX5 said:
Thanks for replying,
I've tried that, it's a great script btw. But still doesn't work, still can't flash with bootloader locked.
Thanks for replying, Good suggestion but can't be. On my laptop there are 2 USB 3.0 ports and 1 USB 2.0 port the Pixel only connects when I use the USB 2.0 port and won't work when I use the USB 3.0 port.
Click to expand...
Click to collapse
Hmm. Try
Code:
Fastboot flashing lock_critical
It will wipe your device if it works. But you'll be unbricked.
D3RP_ said:
Hmm. Try
Code:
Fastboot flashing lock_critical
It will wipe your device if it works. But you'll be unbricked.
Click to expand...
Click to collapse
Already tried that, I'll get this message:
Code:
FAILED (remote: Device already : unlocked!)
Which is kinda weird...
VmX5 said:
Hmm. Try
Already tried that, I'll get this message:
Which is kinda weird...
Click to expand...
Click to collapse
Can you boot TWRP? Or do you at least have it installed?
D3RP_ said:
Can you boot TWRP? Or do you at least have it installed?
Click to expand...
Click to collapse
Didn't have it installed, kinda hoped default recovery was enough.
And can't boot into TWRP, says XXX Failed in locked state.
Anyways thanks for the help so far man, I spoke to a Google rep and said they'd RMA it. I just dropped it off at the post office. I'm kinda disappointed I couldn't fix this one by myself but whatever. Thanks man.
VmX5 said:
Didn't have it installed, kinda hoped default recovery was enough.
And can't boot into TWRP, says XXX Failed in locked state.
Anyways thanks for the help so far man, I spoke to a Google rep and said they'd RMA it. I just dropped it off at the post office. I'm kinda disappointed I couldn't fix this one by myself but whatever. Thanks man.
Click to expand...
Click to collapse
Oh aw, well alright. At least you're gonna have a working phone again, and this time it won't be locked
D3RP_ said:
Oh aw, well alright. At least you're gonna have a working phone again, and this time it won't be locked
Click to expand...
Click to collapse
Haha yea, Now just gotta wait about a week
But thanks for all the help man! Really appreciate it!
Rooting the Pixel 6a is just about as easy as any other factory unlocked pixel, but because so many people have had issues with unlocking their bootloaders, I figured I'd post my exact personal steps I took when a Pixel 6a came into my tech shop to be rooted, and I discovered the current bug with Rooting
What You'll Need:
- June 2022 Firmware OTA Update Installed at least: Do this on device. Do Not download the OTA update from google's firmware website.
- ADB/Fastboot/Google Drivers for Windows: I use this to install- ADB 15sec Installer
- Magisk Manager APK: Github - Magisk Github Releases
- Firmware Matching Currently Installed: Google FW page - Google Official Firmware Downloads - you need this for the boot.img file
- A Windows Computer
- A USB-C cable to connect to your phone to the computer
OEM Unlock Bug
With early units sold by Google, they're shipping with a bug where OEM Unlock stays grayed out. Here's the only way I got around this issue
1.) Log out of any Google Account on the device
2.) Connect to Wifi, check for updates without your sim card in the device. There is a bug where it will potentially download the update for your carrier sim
3.) At minimum, you should get the June 2022 security patch update. Run the update and remember which update it is for when you download the firmware to get boot.img
4.) When the update is finished, Factory Reset your device either from settings or Android recovery
5.) Go through Android setup without sim card in, and don't connect to wifi, finish setup without logging into a google account or anything
6.) When setup is done, connect to wifi and put your sim back in.
7.) Pay attention in your notifications for "Preparing your Device" notification.
8.) When that notification pops up, enable Developer options (tap build number a bunch of times)
9.) OEM Unlock should be possible to enable now. Also enable USB Debugging
Pre-Root Setup
1.) Install Magisk Manager from Github
2.) Use 7zip (or any other ZIP opening program) to extract the boot.img from your firmware download from google
-- the boot.img is inside another zip file that's in the download from google. very easy to get
3.) Put the Boot.img on your phones internal storage
4.) Open Magisk Manager, and select your Boot.img from internal storage. Patch the boot.img to make it a rooted boot.img
5.) With your phone connected to the computer, move the magisk_patched.img from sdcard/downloads to your computer
6.) If USB debugging is properly enabled, now you can open CMD and reboot to bootloader with
Code:
adb reboot bootloader
Unlocking the bootloader
1.) With the device connected, OEM Unlock enabled, and booted to bootloader, you can unlock the bootloader with the following command
Code:
fastboot flashing unlock
-- If nothing changes on your phone screen, use Device Manager to make sure the device is recognized via google drivers: vid here on that - Quick Fastboot Drivers Install Tutorial
2.) On your phone, use the volume keys to select Unlock Bootloader, then hit the power button, device should reboot back to bootloader
3.) flash the boot partition with the magisk patched boot.img
Code:
fastboot flash boot magisk_patched.img
4.) Now you can reboot back into your device and you should be rooted!
Code:
fastboot reboot
Congrats! Now you're bootloader unlocked and rooted! GrapheneOS is already available if you want a degoogled rom, haven't seen another rom pop up yet
all done from there
updating your device when rooted
I do not have a pixel 6a specifically for this right now to confirm this will work, but on every other device with OTA's, this has been my process.
1.) Download your OTA using the system update part of Settings
2.) When it pops up and is ready to restart to finish installing the update, DO NOT CLICK RESTART IN SETTINGS/SYSTEM UPDATE
3.) Go to Magisk Manager, and select Install next to Magisk
4.) Select "Install to Inactive Slot (After OTA)
5.) When its done patching the boot partition, hit restart in Magisk
Your OTA Update is now rooted
To save time and effort here is the magisk patched boot.img for June 2022 patch level, Carrier Unlocked 6a from the Google Store. Make SURE you are on build SD2A.220601.003 before flashing!
To get the `OEM Unlock` option in Developer Options to work, it's simpler to just manually flash 12.1.0 (SD2A.220601.004, Jun 2022, Verizon, Verizon MVNOs) and then wipe.
Even though it's label as Verizon, it should work for all carriers.
Hello, if we have already unlocked the bootloader, we just have to do this: start cmd then fastboot flash boot magisk_patched.img then restart the phone?
jejemc said:
Hello, if we have already unlocked the bootloader, we just have to do this: start cmd then fastboot flash boot magisk_patched.img then restart the phone?
Click to expand...
Click to collapse
Correct, though I would probably fastboot boot first just to make sure it boots up ok. When it does you can reboot to recovery and flash it.
these instructions sound like "the usual process", but for the 6a isn’t there something to patch regarding vbmeta as well?
(never had a phone that "needed" this, but in my understanding it "should" be necessary with the 6a? won’t have time to try out myself before the weekend, just asking ..)
ctfrommn said:
Correct, though I would probably fastboot boot first just to make sure it boots up ok. When it does you can reboot to recovery and flash it.
Click to expand...
Click to collapse
here it is and does and works perfectly well thank you for everything.
Im starting work on my custom kernel now so hopefully MVK for Bluejay will be ready in the coming days/weeks.
Zaxx32 said:
To save time and effort here is the magisk patched boot.img for June 2022 patch level, Carrier Unlocked 6a from the Google Store. Make SURE you are on build SD2A.220601.003 before flashing!
Click to expand...
Click to collapse
As this thread ages, not everyone will have the June 2022 update. That's why I suggested/put the steps in to do it themselves with matching firmware to what their device is on.
benji said:
To get the `OEM Unlock` option in Developer Options to work, it's simpler to just manually flash 12.1.0 (SD2A.220601.004, Jun 2022, Verizon, Verizon MVNOs) and then wipe.
Even though it's label as Verizon, it should work for all carriers.
Click to expand...
Click to collapse
This DID NOT work for me. That's why I wrote this up the way I did.
jejemc said:
Hello, if we have already unlocked the bootloader, we just have to do this: start cmd then fastboot flash boot magisk_patched.img then restart the phone?
Click to expand...
Click to collapse
If you're bootloader is already unlocked, you just have to flash the patched magisk boot img, correct. I wrote this up for those having issue with not having the ability even if it is an unlocked from google device
frank93 said:
these instructions sound like "the usual process", but for the 6a isn’t there something to patch regarding vbmeta as well?
(never had a phone that "needed" this, but in my understanding it "should" be necessary with the 6a? won’t have time to try out myself before the weekend, just asking ..)
Click to expand...
Click to collapse
Correct, these are basically the usual steps. There's nothing regarding vbmeta flashing in this case of just rooting stock firmware. You only need to do that with ROMs (GSI's mainly)
KaptinBoxxi said:
3.) flash the boot partition with the magisk patched boot.img
Code:
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
Just a heads up. As already told by ctfrommn, it's always a better approach to first boot the magisk patched boot file. And if everything works well and good, you could then Direct Install it via Magisk.
Although directly flashing should also work, but its always better to be on the safer side.
KaptinBoxxi said:
Correct, these are basically the usual steps. There's nothing regarding vbmeta flashing in this case of just rooting stock firmware. You only need to do that with ROMs (GSI's mainly)
Click to expand...
Click to collapse
I followed your steps to a T. Still can't unlock. I'm convinced there is a fault with my device itself at this point.
stormcrank said:
I followed your steps to a T. Still can't unlock. I'm convinced there is a fault with my device itself at this point.
Click to expand...
Click to collapse
they will warranty replace if it for sure fails still. Its a silly situation, but mistakes happen
binary**# said:
Just a heads up. As already told by ctfrommn, it's always a better approach to first boot the magisk patched boot file. And if everything works well and good, you could then Direct Install it via Magisk.
Although directly flashing should also work, but its always better to be on the safer side.
Click to expand...
Click to collapse
I may not be very active on XDA, but have been rooting and rom'ing devices since the palm pre, first android phone was the droid x. I've never heard of this step, its never been needed. Its an extra pointless step that is just tethered root. You don't need to do it. As long as you don't download a random Boot.img, like the one for some reason attached to a reply on this thread and get it yourself from the firmware matching your device OR flashing Magisk via TWRP/Lineage Recovery with adb sideload, there's no reason to fastboot boot the boot.img.
You may have never run into an issue flashing a boot image but I've built thousands of roms and kernels and have learned the hard way more than once to measure twice, cut once.
That said, as long as you're simply patching a stock boot.img it's likely not an issue.
Followed all steps, on SD2A.220601.003SD2A.220601.003. OEM unlock still greyed
Nice work, Kaptinboxxi. Everything worked fine. How should we handle updates after rooting? Will a security patch break root? If so, what is the best process to root it again?
Voxilli said:
Nice work, Kaptinboxxi. Everything worked fine. How should we handle updates after rooting? Will a security patch break root? If so, what is the best process to root it again?
Click to expand...
Click to collapse
Yes, each update will require reflashing a patched kernel for the new build.
You can also do the "Install to Inactive Slot" method in Magisk to update and keep root. This has been a bit of a hit and miss for some people on the Pixel 6 series, though. The misses may be in large part be due to people having modified their partitions or not restoring the necessary images while being on a custom kernel.
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io
Lughnasadh said:
You can also do the "Install to Inactive Slot" method in Magisk to update and keep root.
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
Good call...I guess I've never messed with that as I flash so many kernels anyway.
Lughnasadh said:
You can also do the "Install to Inactive Slot" method in Magisk to update and keep root. This has been a bit of a hit and miss for some people on the Pixel 6 series, though. The misses may be in large part be due to people having modified their partitions or not restoring the necessary images while being on a custom kernel.
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
That's what I've done with my OnePlus 7T for the last three years. Any repercussions for doing it this way versus patching the kernel?
after download and reboot apprear this error..refer photo..
Try shutting it down, entering fastboot mode and flashing it from here.
bfsr83 said:
Try shutting it down, entering fastboot mode and flashing it from here.
Click to expand...
Click to collapse
ok thanks..no need unlockboot loader rite?
Boi. said:
ok thanks..no need unlockboot loader rite?
Click to expand...
Click to collapse
You can't flash anything with a locked bootloader
ctfrommn said:
You can't flash anything with a locked bootloader
Click to expand...
Click to collapse
ok thanks..hmmm..
Boi. said:
ok thanks..no need unlockboot loader rite?
Click to expand...
Click to collapse
For Android Flash Tool you need to have OEM unlocking enabled in developer options, but don't need to actually have the bootloader unlocked beforehand. The tool will unlock your bootloader during the process (assuming you are able to unlock the bootloader, e.g. not a Verizon model). It will also lock it afterwards if you choose to do so.
bfsr83 said:
Try shutting it down, entering fastboot mode and flashing it from here.
Click to expand...
Click to collapse
already try..still not work
Boi. said:
already try..still not work
Click to expand...
Click to collapse
You probably need to be more specific. What exactly happened after using Android Flash Tool? How did you initially try to install QPR1B1? Are you using the latest Platform Tools? Do you have the latest USB drivers installed? Have you tried using an A to C cable using a USB 2.0 port?
If you're flashing environment is set up correctly, you can also try sideloading the OTA image.
bfsr83 said:
Try shutting it down, entering fastboot mode and flashing it from here.
Click to expand...
Click to collapse
Thank you!
For the last 4 years I was updating my Pixels by downloading full official image and flashing without -w option, then patching boot.img via magisk and this process worked flawlessy every time. Tried same method with my new Pixel 6a on bluejay-tp1a.220624.021.a1 and every time I'd flash September's update bluejay-tp1a.220905.004.a2 my phone wouldn't boot and I would get "Your device is corrupt. It can't be trusted" error followed by google boot image and then boot loop. OK I thought, I'll wait until I've got time for a clean flash and that will solve it. To my surprise, it did not... Flashed clean image with full wipe and still same issue So now I did it via Android Flash Tool and it worked! For curiosity, then flashed the same image I had issues with via ADB and it also works now So what was the cause of the problem remains a mistery to me...
Pakabidu said:
Thank you!
For the last 4 years I was updating my Pixels by downloading full official image and flashing without -w option, then patching boot.img via magisk and this process worked flawlessy every time. Tried same method with my new Pixel 6a on bluejay-tp1a.220624.021.a1 and every time I'd flash September's update bluejay-tp1a.220905.004.a2 my phone wouldn't boot and I would get "Your device is corrupt. It can't be trusted" error followed by google boot image and then boot loop. OK I thought, I'll wait until I've got time for a clean flash and that will solve it. To my surprise, it did not... Flashed clean image with full wipe and still same issue So now I did it via Android Flash Tool and it worked! For curiosity, then flashed the same image I had issues with via ADB and it also works now So what was the cause of the problem remains a mistery to me...
Click to expand...
Click to collapse
Update:
I think I was able to flash that image with ADB after doing with Android Flash Tool first is because it was the same image. Later tried flashing next month's update via ADB and had same issue again. So today decided to sideload November's update via ADB instead of flashing full image and that worked.
Just wonder what did I mess up for me not to be able to flash with ADB...
Pakabidu said:
Update:
I think I was able to flash that image with ADB after doing with Android Flash Tool first is because it was the same image. Later tried flashing next month's update via ADB and had same issue again. So today decided to sideload November's update via ADB instead of flashing full image and that worked.
Just wonder what did I mess up for me not to be able to flash with ADB...
Click to expand...
Click to collapse
That is really weird behaviour for a Pixel device. I update using the stock rom method for all my pixels and never had issues. I have the Pixel 6 and the only instance I got the device is corrupt when I tried to roll back the November update to the October update causing a bootloop.
I wonder if there is something wrong with the 6A and some people having issues with the oem unlocking being greyed-out. Hopefully, Google will fix the issue with a future patch or monthly update.