I haven't used my Nexus in about a month and the last time I used it, I had flashed a new rom with the wrong gapps. It was a fresh factory reset and whenever it booted up, I would get error messages and I wouldn't be able to do the initial set up. At the time, this was nothing I couldn't fix, but I had to put it aside because I was busy.
Fast forward to present day, I completely forgot about it. I locked the device, flashed stock recovery and did another factory reset. Now whenever I try to turn it on I get stuck at a black screen with error messages (I can't do initial setup). I can't install a new rom because the device is locked and I can't unlock it because it's OEM locked and I can't get into the OS.
Am I screwed or can I still pull off a miracle?
Wug's Nexus Root Toolkit! There are tons of video tutorials on YouTube that should help.
Sent from my Nexus 6 using Tapatalk
Go_Radio said:
I haven't used my Nexus in about a month and the last time I used it, I had flashed a new rom with the wrong gapps. It was a fresh factory reset and whenever it booted up, I would get error messages and I wouldn't be able to do the initial set up. At the time, this was nothing I couldn't fix, but I had to put it aside because I was busy.
Fast forward to present day, I completely forgot about it. I locked the device, flashed stock recovery and did another factory reset. Now whenever I try to turn it on I get stuck at a black screen with error messages (I can't do initial setup). I can't install a new rom because the device is locked and I can't unlock it because it's OEM locked and I can't get into the OS.
Am I screwed or can I still pull off a miracle?
Click to expand...
Click to collapse
Hi, Go_Radio...
Probably screwed ... sorry, I don't mean to be glib or flippant. I've experienced something similar myself, late last year, and I had to return my Nexus 9 for a replacement, so I know what a pain in the backside this problem is.
-----
But to be clear, if I read and understand your post correctly, you're looking to run fastboot flash commands (either directly yourself, or allow a toolkit to run them for you) in order to either...
----
a) Fastboot Flash back to Google Factory Stock.
~ or ~
b) Fastboot Flash TWRP, and via TWRP, flash some Custom ROM.
----
...but cannot do either...
...because the bootloader is locked, and attempts unlock it with fastboot oem unlock fail.
And it fails because the option in SETTINGS>>DEVELOPER OPTIONS>>OEM unlocking (allow the bootloader to be unlocked) has not be enabled, or has been disabled.
This damnable nuisance problem, at the moment, can only be resolved in one of two ways... Either by returning your device for repair or replacement...
Or by the method described here...
[INFO] Nexus 6 / Nexus 9 Enable OEM Unlock [GUIDE] Unlock via TWRP/CWM
http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
...unfortunately for this to work, you do need TWRP installed, in order for the necessary files to be copied over to your Nexus 9, as the stock recovery doesn't allow for ADB connections (I know, I've tried )
And since Android won't boot, for whatever reason, you're locked out, and you can't enable the 'Allow OEM unlocking' setting in Developer Options in order to allow the bootloader to be unlocked, in order to fastboot flash TWRP. You're caught in a Catch 22 situation .
I wish I had some better options for you... .
Rgrds,
Ged.
Related
So i ticked the oem unlock and my phone reeboted, after the the wipe the option is nkt there anymore and when i try to flash twrp with odin i get this "Only Official released binaries are allowed to be flashed(RECOVERY)"
Fmikati said:
So i ticked the oem unlock and my phone reeboted, after the the wipe the option is nkt there anymore and when i try to flash twrp with odin i get this "Only Official released binaries are allowed to be flashed(RECOVERY)"
Click to expand...
Click to collapse
Same thing happened with me. I switched on the OEM unlock and did the factory reset. After that the OEM unlock was gone. However, 7 days later (This morning) the OEM switch is back and it is switched on, which means I can go ahead and root now, so you will need to wait the additional 7 days and then you should be good
Thanks for the reply, let me know if the root works and which/who's method did you use.
tfaletau said:
Same thing happened with me. I switched on the OEM unlock and did the factory reset. After that the OEM unlock was gone. However, 7 days later (This morning) the OEM switch is back and it is switched on, which means I can go ahead and root now, so you will need to wait the additional 7 days and then you should be good
Click to expand...
Click to collapse
Fmikati said:
Thanks for the reply, let me know if the root works and which/who's method did you use.
Click to expand...
Click to collapse
OK, so I was able to flash TWRP using ODIN - Use the guide by @dr.ketan
He has a zip you can download and flash after flashing TWRP, but I did not use that, I immediately flashed the TGP ROM, which has an Aroma installer and includes Magisk root, then before rebooting, I flashed the RMMstate_bypass. The ROM loaded fine, but I was getting systemui fcs, which was due to setting up intelliscan. I disabled that, but still had systemui fcs, so I needed to reboot. I checked developer options and the OEM unlock switch was gone again, however, I had to reboot. When I did, the rom rebooted fine and worked perfectly. Since then, I have rebooted more than 10 times with no issue. The OEM unlock option is still not available, but that does not matter as it is obviously unlocked. Bottome line, you should see the OEM unlock again after 7 days and you should be able to root.
So my phone works fine but I decided to try my first rooting job on it a few months back and I screwed up somewhere. My intent of rooting was to install a custom rom like Lineage OS. I decided not to flash Lineage OS at the time because I wanted to use the phone rooted right away and I was not patient enough to go through that process so I put it off but I intended to eventually get off stock. Then a new update came out for stock and would continually throw me out of apps and could not install because of the unlocked bootloader (I didn't know about turning off auto-updates in developer options. Must have skipped past it.) so I decided to finally flash Lineage. I got a new computer in the mean time since first root and decided to try and flash Lineage on my phone from it and realized that my TWRP was no longer installed so putting a custom rom had to wait until I reinstalled TWRP. I then tried to re-flash TWRP and realized that only two fastboot commands would NOT freeze up or throw up an error: fastboot devices and fastboot reboot bootloader. So then I realized I am stuck. I cannot, at least as far as I know, flash custom roms OR stock ones without those fastboot commands.
I first thought the issue was my new computer which had only USB 3.0 ports and the original root happened from a USB 2.0 port so I assumed it was an incompatibility with the ports but my old computer threw up the same errors so that wasn't it. I then thought it was an issue with the drivers and that wasn't it either because I must have tried 10 different configurations with the same exact error. So my new thought was to look at the error signs again. Almost all "fastboot flash recovery recovery.img" with TWRP nash img file gave an error similar to max-download-size exceeded. Or just froze. The most common error was "remote: unknown command" but one error was interesting and is why I decided to post here. I don't have it logged because I forgot to paste it out of my clipboard but it went along the lines, "Warning: Device A/B support is outdated. Bootloader update required."
What can I do about this? Buy another phone? Send it to a repair shop? I am exhausted trying all the advice I found online and I am extremely frustrated that I messed up and I don't know how to fix it. This phone was relatively inexpensive but I would love to spend that money elsewhere.
Hey guys:
I did unlock bootloader unload/root according to this guide.
First Wifi worked.
Then I did try to figure out OTA issues, could not uninstall Magisk, so temporary flashed stock image back.
From here on out - no matter, if stock, or Magisk_patched image: No chance to turn WiFi on.
In the WiFi-Menu, if I touch "turn on", it will show for one second: Turning Wi-Fi on", and then just return to the WiFi off-setting...
I did do factory reset from recovery - no success, flashed again (stock and patched) - no success.
I can't figure it out! Anybody an idea?
Are you sure that you are using correct boot.img version? It must be the same version as your system - build number and EU/GB variant must match.
Yes. I did, unless I had an older Version on a different slot and somehow did change slots and started messing around there. Could be an explanation.
Got tired of messing with it. Did download the whole stock rom, flashed it and will stay "unrooted" for now. Not worth the hassle to me.
BUT: What a mess that these manufacturers make it so hard to have working and rooted phone.
My guess would be that you flashed incorrect stock boot image.
Also how come that you couldn't uninstall Magisk?
Rooting is pretty straightforward, even if Mi A3 has a slight complication with missing "fastboot boot" command support, but otherwise it's nothing special. Take the correct boot.img, patch it, flash it and you're done.
First take your phone into fastboot mode. write fastboot set_active a .unzip stock rom and you will see flash_all.bat click it and you will succesfully have brand new rom with no issue. Note:If anything bad happens or goes wrong im not responsible. Its all your decision to do it
_mysiak_ said:
My guess would be that you flashed incorrect stock boot image.
Also how come that you couldn't uninstall Magisk?
Rooting is pretty straightforward, even if Mi A3 has a slight complication with missing "fastboot boot" command support, but otherwise it's nothing special. Take the correct boot.img, patch it, flash it and you're done.
Click to expand...
Click to collapse
Magisk said: no backup. tht's why I did install the original boot.img back, and this is where the WiFi-issue started.
I wanted to go this route, but did not manage it after several hours, so gave up and went stock:
https://forum.xda-developers.com/mi-a3/how-to/guide-create-manual-backup-stock-boot-t3988345
WorstCases said:
Magisk said: no backup. tht's why I did install the original boot.img back, and this is where the WiFi-issue started.
I wanted to go this route, but did not manage it after several hours, so gave up and went stock:
https://forum.xda-developers.com/mi-a3/how-to/guide-create-manual-backup-stock-boot-t3988345
Click to expand...
Click to collapse
Yeah, you need to create first backup manually. The guide works perfectly, I tested all methods (otherwise I wouldn't mention them ). What issues did you have?
The system is probably installed in b partition, you need to set partition a as active and reinstall rom via mi flashtool
Hello,
I was installing different custom ROMS for this phone, then reverted back to Stock ROM. It updated itself, and IMEI got erased somehow.
Is there any way possible to flash a custom ROM, or even custom recovery using MSMDownloadTool? I had a global version N10, so it was sim unlocked and bootloader unlockable, and I do actually have my IMEI on the back of my box, but can't put it into my phone as I have to root it. But I can't root it because the bootloader is now locked, and the bootloader is now locked because there is no IMEI......
This leaves me locked out of fastboot, so the only option is edl, which works just fine. However, only MSMDownloadTool is compatible with this mode, and it only installs Stock ROMs.
I tried extracting the .OPS files, replacing the stock recovery with twrp (and then renaming it to recovery.img), repacking the .ops then installing it. It installs, but then never boots and is just stuck in edl mode until I reflash the normal stock rom with the stock recovery.
What Do I do?
Thanks
CrustyBurger33 said:
Hello,
I was installing different custom ROMS for this phone, then reverted back to Stock ROM. It updated itself, and IMEI got erased somehow.
Is there any way possible to flash a custom ROM, or even custom recovery using MSMDownloadTool? I had a global version N10, so it was sim unlocked and bootloader unlockable, and I do actually have my IMEI on the back of my box, but can't put it into my phone as I have to root it. But I can't root it because the bootloader is now locked, and the bootloader is now locked because there is no IMEI......
This leaves me locked out of fastboot, so the only option is edl, which works just fine. However, only MSMDownloadTool is compatible with this mode, and it only installs Stock ROMs.
I tried extracting the .OPS files, replacing the stock recovery with twrp (and then renaming it to recovery.img), repacking the .ops then installing it. It installs, but then never boots and is just stuck in edl mode until I reflash the normal stock rom with the stock recovery.
What Do I do?
Thanks
Click to expand...
Click to collapse
If your bootloader was relocked, encryption and partition checking were enabled again.
TWRP would only cause your phone to register as modified and lock itself...and due to streamlining of a lot of functions, you can't even use the dialer to enter the menu needed.
Best you can do is totally wipe everything on your phone and generate a new android ID. (You have to do this from the actual OS instead of recovery though. Recovery format uses predetermined instructions. The format option from the android settings panel has a different set of instructions and one of them is to generate a new android ID, which includes IMEI)
Thanks for the reply, although im kinda confused by your answer. How do I generate a new android ID? (what does that even mean lol). I checked in my settings and I can't find any "format option"
CrustyBurger33 said:
Thanks for the reply, although im kinda confused by your answer. How do I generate a new android ID? (what does that even mean lol). I checked in my settings and I can't find any "format option"
Click to expand...
Click to collapse
Android ID is what determines your phone is the phone it claims to be when pinging google services.
Move any files you want to keep to somewhere safe. Format your phone, android will push you a new id number. It won't fix your IMEI, but it'll keep your phone from being absolutely useless in the process.
After your phone is formated and has booted back into the OS, you can enable adb. Adb into fastboot, use fastboot to determine if your device is still bootloader unlocked using the fastboot oem device-info command
ninjasinabag said:
After your phone is formated and has booted back into the OS, you can enable adb. Adb into fastboot, use fastboot to determine if your device is still bootloader unlocked using the fastboot oem device-info command
Click to expand...
Click to collapse
I tried everything you said, reset everything, still no IMEI, and even if the Android ID is different it hasn't really changed anything. Just to be clear, when I flashed the stock ROM earlier, everything worked as intended apart from the SIM card (which doesnt work at all) and the WiFi (which keeps dropping after 5 seconds of connection). Those problems persist even now.
Guess I'll be messing around with the SMT mode in MSMDownloadTool since I've already lost my IMEI, see what I can do from that. If there's anything I do actually end up finding out, I'll post it on xda.
Update
I installed an update by download a zip, installed update via settings. System rebooted to complete update, and somehow the oem unlock option opened!!
From this point, fixing it will be pretty straight forward I think
Thanks for your help
CrustyBurger33 said:
Update
I installed an update by download a zip, installed update via settings. System rebooted to complete update, and somehow the oem unlock option opened!!
From this point, fixing it will be pretty straight forward I think
Thanks for your help
Click to expand...
Click to collapse
Nice! If everything is working properly besides the IMEI at this point, there's a couple of PC applications you can use.
I'd recommend write dual imei, not gonna post a link since IMEI fudging is against the rules (even if you're just trying to repair your IMEI)
Use the IMEI that's on your device sticker or on your phone packaging specifically.
Either way, hoping you get your phone back up to 100%.
As it turns out, it's not easy at all. My WiFi has exactly the same issue... keeps dropping, No SIM card, no baseband version. What's crazy is that I have rooted, and even repaired the IMEI via a tool. If I read the IMEI via the tool (and different ones just to be sure), they will all show the IMEI the same as the one that I wrote (which were the original ones).
But for some reason the phone still doesnt recognize it. I reboot it. Same story. The tool recognizes, the phone doesn't. I know for a fact that the issue cannot be hardware, at least for WiFi. If it was, it wouldn't connect to any network, but it does, and then disconnects after a few seconds. I think I have been all over every post on the internet regarding this issue, but still no luck.
Honestly, check with OnePlus if you're under the 1 year warranty window. This sounds like an issue that can really only be fixed with a replacement device.
CrustyBurger33 said:
As it turns out, it's not easy at all. My WiFi has exactly the same issue... keeps dropping, No SIM card, no baseband version. What's crazy is that I have rooted, and even repaired the IMEI via a tool. If I read the IMEI via the tool (and different ones just to be sure), they will all show the IMEI the same as the one that I wrote (which were the original ones).
But for some reason the phone still doesnt recognize it. I reboot it. Same story. The tool recognizes, the phone doesn't. I know for a fact that the issue cannot be hardware, at least for WiFi. If it was, it wouldn't connect to any network, but it does, and then disconnects after a few seconds. I think I have been all over every post on the internet regarding this issue, but still no luck.
Click to expand...
Click to collapse
Hi I have a similar problem.. My phone oneplus 8t is stuck in 'SMT Download failed error' mode. I was tryimg out custom roms which has caused this. My phone says can only be fixed via SMT Download mode. Can you help me out using the SMT download mode? I have tried MSM Tool normally to unbrick my phone but it doesn't work.
hello @nightfury04
If you have a Oneplus 8T you have to download the appropriate MSMDownloadTool (specifically for it) and make sure the version is correct too. Is your phone global/ locked to a carrier?
I know there's some other threads about this already but my situation seems to be somewhat unique and the other solutions I've found haven't worked so I'm hoping someone may have other ideas.
When I boot my Pixel 6 which has unlocked bootloader and rooted with Magisk, I'm getting the RED message saying "your device is corrupt. it cant be trusted and may not work properly" and requiring me to push the power button a second time to continue booting. This is different than the YELLOW warning about unlocked bootloader, which comes after this.
This error started when I tried to install the April update the way I usually do, by downloading the factory image, and using flash-all.bat without the -w to avoid wiping. I was using a new computer though and so I downloaded the latest platform-tools (34.0.1) without realizing that version apparently has an issue. The update failed with the error about "FAILED (Sparse file is too large or invalid)" so I downgraded to platform-tools 33.0.3 and updated successfully. Except now that error is happening on boot.
Googling about the error I find that the main solution is factory reset and reinstall using the Pixel Flash Tool online and let it lock the bootloader and everything. I tried this and the error went away! But as soon as I unlocked the bootloader (NO other modification yet whatsoever, just unlocked the bootloader, the error is back.
I can't find anything about this online where it comes back from just unlocking the bootloader after a fresh stock install and everything back to factory.
Any ideas? It is still under warranty so if this seems like a hardware fault, I can probably get it replaced. Google support assured me that the factory reset would help, and when it didn't, they told me to take it to the local UBreakIFix store. I just want to see if I have any other course of action before doing that.
Thanks!
Oh, and the other solution I found which was this adb command: "
adb reboot "dm-verity enforcing" doesn't seem to help either. If I try to run the command I get this error "/system/bin/reboot: too many arguments". This is being run on Windows 11 and I am including the quotes around dm-verity enforcing so I don't see why that should be too many arguments.
ms4sman said:
I know there's some other threads about this already but my situation seems to be somewhat unique and the other solutions I've found haven't worked so I'm hoping someone may have other ideas.
When I boot my Pixel 6 which has unlocked bootloader and rooted with Magisk, I'm getting the RED message saying "your device is corrupt. it cant be trusted and may not work properly" and requiring me to push the power button a second time to continue booting. This is different than the YELLOW warning about unlocked bootloader, which comes after this.
This error started when I tried to install the April update the way I usually do, by downloading the factory image, and using flash-all.bat without the -w to avoid wiping. I was using a new computer though and so I downloaded the latest platform-tools (34.0.1) without realizing that version apparently has an issue. The update failed with the error about "FAILED (Sparse file is too large or invalid)" so I downgraded to platform-tools 33.0.3 and updated successfully. Except now that error is happening on boot.
Googling about the error I find that the main solution is factory reset and reinstall using the Pixel Flash Tool online and let it lock the bootloader and everything. I tried this and the error went away! But as soon as I unlocked the bootloader (NO other modification yet whatsoever, just unlocked the bootloader, the error is back.
I can't find anything about this online where it comes back from just unlocking the bootloader after a fresh stock install and everything back to factory.
Any ideas? It is still under warranty so if this seems like a hardware fault, I can probably get it replaced. Google support assured me that the factory reset would help, and when it didn't, they told me to take it to the local UBreakIFix store. I just want to see if I have any other course of action before doing that.
Thanks!
Click to expand...
Click to collapse
Two things you can try to get rid of the message:
1. Flash the previous month's boot image (your device likely won't boot but that's ok), then flash the boot image of your current month's build.
or
2. Flash the factory image of the previous month and then flash the current factory image.
The message is quite innocuous. You can also safely ignore it and wait until May's security patch is released, install that and the message should go away.
In a nutshell, the bootloader is looking for a new/updated OS without corruption errors so it will go back to restart mode rather than being stuck in the RED eio mode which displays that message.
Verifying Boot | Android Open Source Project
source.android.com
Boot Flow | Android Open Source Project
source.android.com
Lughnasadh said:
Two things you can try to get rid of the message:
1. Flash the previous month's boot image (your device likely won't boot but that's ok), then flash the boot image of your current month's build.
or
2. Flash the factory image of the previous month and then flash the current factory image.
The message is quite innocuous. You can also safely ignore it and wait until May's security patch is released, install that and the message should go away.
In a nutshell, the bootloader is looking for a new OS without corruption errors so it will go back to restart mode rather than being stuck in the RED eio mode which displays that message.
Verifying Boot | Android Open Source Project
source.android.com
Boot Flow | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
Thanks for the suggestions! I'll give it a try.
I'm curious though, is there a known issue with the April update or something?
Otherwise, since I completely factory reset it and installed the latest image using the Pixel Flash Tool and let it lock the bootloader and everything, wouldn't that have replaced any corrupt images? Why does JUST unlocking the bootloader trigger that warning now when it didn't used to?
Thanks!
ms4sman said:
Thanks for the suggestions! I'll give it a try.
I'm curious though, is there a known issue with the April update or something?
Otherwise, since I completely factory reset it and installed the latest image using the Pixel Flash Tool and let it lock the bootloader and everything, wouldn't that have replaced any corrupt images? Why does JUST unlocking the bootloader trigger that warning now when it didn't used to?
Thanks!
Click to expand...
Click to collapse
Not sure why just unlocking the bootloader caused that message (I haven't seen that before), but there really wasn't a need to re-lock your bootloader in the first place as far as I'm aware of.
The error was likely originally caused by using Platform Tools 34 and encountering the error you did. I've seen plenty of people update to April without a problem.
Lughnasadh said:
Not sure why just unlocking the bootloader caused that message (I haven't seen that before), but there really wasn't a need to re-lock your bootloader in the first place as far as I'm aware of.
The error was likely originally caused by using Platform Tools 34 and encountering the error you did. I've seen plenty of people update to April without a problem.
Click to expand...
Click to collapse
Yeah it's very strange indeed. I just did some more testing. Just to confirm things, I just used the Pixel Flash Tool and flashed the latest stock image for the phone onto both slots just to be safe, then locked the bootloader. At this point, the phone should be EXACTLY as it was from the factory, right?
But as soon as I unlocked the bootloader and rebooted, it goes right back to the corrupt message. I locked it again, and bang, error gone. Unlocked, error back.
JUST unlocking the bootloader shouldn't cause any issue or trigger this error right?
ms4sman said:
Yeah it's very strange indeed. I just did some more testing. Just to confirm things, I just used the Pixel Flash Tool and flashed the latest stock image for the phone onto both slots just to be safe, then locked the bootloader. At this point, the phone should be EXACTLY as it was from the factory, right?
But as soon as I unlocked the bootloader and rebooted, it goes right back to the corrupt message. I locked it again, and bang, error gone. Unlocked, error back.
JUST unlocking the bootloader shouldn't cause any issue or trigger this error right?
Click to expand...
Click to collapse
As I stated earlier, the bootloader is looking for a new/updated OS without corruption errors. So try doing one or both of the two things I suggested earlier. Sounds like you are just flashing the same factory image which isn't actually updating to a new/updated OS.
All this locking and unlocking is causing factory resets.
Why bother?
Easiest way to make the red corruption message go away is to extract the vbmeta image from the factory image zip and do this -
Code:
fastboot --disable verity flash vbmeta vbmeta.img
Voila! Red warning gone and no factory reset.
Next month continue flashing as you usually do.
No need to disable verity next time because the corruption message is gone and an updated OS will be installed.