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.
Related
About 2 weeks ago, I unlocked the bootloader to my Nexus 9. I installed TWRP and a CyanogenMod nightly. After deciding the only availible Cyanogen builds for the Nexus 9 (the nightlies) are far too unstable for general use, I tried today to flash the recovery ROM. I flashed the rom with an error:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(893,0xa04ae1d4) malloc: *** mach_vm_map(size=1816023040) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1814205204 bytes
error: update package missing system.img
I then made the ridiculous mistake of locking my bootloader again (fastboot oem lock) which ran successfully, but then got me stuck in a recovery boot loop (teamwin splash screen). After about a minute of this, the screen went black and the device is now a $399 paperweight. I cannot use any key combinations to get the screen on. It won't show up in fastboot either. I have no hopes of getting a repair from HTC for three main reasons:
1. I got the device from somebody who attended a conference at Google and received the device for free. Does it affect my warranty?
2. If there is a custom recovery, I have surely voided what warranty I would've had.
3. I live in a Central American country, where it is extremely difficult to ship items to the United States, especially items of high value.
Is my wonderful device that was so kindly given to my now an HTC branded brick?
[UPDATE] I have been able to get into fastboot, but I still get the error? I got the firmware from the official Google page, and I am 100% sure I downloaded the correct rom :/
You're most likely sol. Read this thread, http://forum.xda-developers.com/showthread.php?p=59677447
Sent from my Nexus 9 using XDA Free mobile app
With the error you get when trying to flash factory image through adb . Have you tried first to unzip the images from inside the file downloaded from google and flash individually? You've already flashed the bootloader/radio when you started installing the factory image, I wonder if you flash the image files inside the zip inside the factory tgz if you might escape? look here, http://forum.xda-developers.com/nexus-9/general/guide-nexus-9-to-stock-guide-unbrick-t2975668 if you can still fastboot this might help?
nrsmac said:
About 2 weeks ago, I unlocked the bootloader to my Nexus 9. I installed TWRP and a CyanogenMod nightly. After deciding the only availible Cyanogen builds for the Nexus 9 (the nightlies) are far too unstable for general use, I tried today to flash the recovery ROM. I flashed the rom with an error:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(893,0xa04ae1d4) malloc: *** mach_vm_map(size=1816023040) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1814205204 bytes
error: update package missing system.img
I then made the ridiculous mistake of locking my bootloader again (fastboot oem lock) which ran successfully, but then got me stuck in a recovery boot loop (teamwin splash screen). After about a minute of this, the screen went black and the device is now a $399 paperweight. I cannot use any key combinations to get the screen on. It won't show up in fastboot either. I have no hopes of getting a repair from HTC for three main reasons:
1. I got the device from somebody who attended a conference at Google and received the device for free. Does it affect my warranty?
2. If there is a custom recovery, I have surely voided what warranty I would've had.
3. I live in a Central American country, where it is extremely difficult to ship items to the United States, especially items of high value.
Is my wonderful device that was so kindly given to my now an HTC branded brick?
[UPDATE] I have been able to get into fastboot, but I still get the error? I got the firmware from the official Google page, and I am 100% sure I downloaded the correct rom :/
Click to expand...
Click to collapse
First of all why the HELL did you lock your bootloader?? Secondly, every single person who has tried to flash these factory images from google using the built in script got this same exact error, including me. All you had to do was manually "fastboot flash system system.img" and thats it. Problem solved. Unless you can manage to get the bootloader unlocked again, its bricked. Good luck
bynarie said:
First of all why the HELL did you lock your bootloader?? Secondly, every single person who has tried to flash these factory images from google using the built in script got this same exact error, including me. All you had to do was manually "fastboot flash system system.img" and thats it. Problem solved. Unless you can manage to get the bootloader unlocked again, its bricked. Good luck
Click to expand...
Click to collapse
I made the mistake of blindly following the advice on the Google page (which did tell me to lock the device). Google needs to fix that script, and get us 5.1 on our nexus devices!!!
I'd like to start off by saying that I have NEVER rooted this device and have been 100% stock since day 1.
The only thing I did was enable developer options to unlock the bootloader so I could sideload OTA updates in the event they take too long to hit my device... No custom recoveries, no custom roms, no custom kernels, no exposed framework... NOTHING.. pure stock.
I started getting the 5.0.2 upgrade notification yesterday. Everytime I download and install, about 30% of the way through the installation I get the android icon showing ERROR. When I open the last recovery log it mentions not being able to open /cache/update.zip with a status 7 error. .. All I can do it reboot and return back to 5.0.1
I did some reading and it was recommended to wipe / format the CACHE partition. So I went into the stock recovery and tried this but to no avail.
I REALLY don't want to factory reset (or flash a factor image) and lose all the progress on the various games I have been playing.
Is there anything else I can try ??
you can try sideloading the update, grabbing the factory image and manually flashing the partitions (except userdata). you can try the factory image and just edit the flash-all.bat file to not wipe the device (sometimes the flash all file gave me an issue forcing me to do the partitions manually)
Thanks for the feedback... I can try this but IMO it's more of a workaround than a solution.
What I'm trying to get at is..... How in the heck would Google or HTC expect the average consumer to resolve such an issue.
Needing to have a PC, have special drivers installed, etc.., is understandable for those who want to step away from STOCK but what about the average consumer who just purchased the tablet to use as is, continues to receive a notification that an update is available, but fails every time it is applied ? Surely there is something that can be done so allow the update to take without having to factory reset or RMA the device...
y2whisper said:
you can try sideloading the update, grabbing the factory image and manually flashing the partitions (except userdata). you can try the factory image and just edit the flash-all.bat file to not wipe the device (sometimes the flash all file gave me an issue forcing me to do the partitions manually)
Click to expand...
Click to collapse
From the sounds of it there is an issue with the OTA file. But I agree you shouldn't be having to do this. I worry about the non xda'ers of the world when this stuff happens
Mine is doing the same crap. Also unmodified Nexus 9. This is nonsense.
Same issue here. Error every time I hit Restart & Install after downloading the update. Have to long press the power bottom to get it to boot back again. Tried a factory reset, didn't work. Still getting same error.
Thanks for sharing that you tried a factory reset. I am trying to avoid this for reasons mentioned in my 1st post.
I have tried numerous times now wiping cache and waiting for the upgrade to reappear but it continues to error out that the same place during the upgrade each time. Fortunately it's not bricking the device but IF this update is required as a stepping stone for subsequent updates then it will be extremely disappointing if Google doesn't address this issue.
I still cannot imagine google / htc not being able to resolve this WITHOUT having to make a user connect to a PC and manually flash imagess (or worse.. RMA the device). Hoping someone on XDA comes up with a magical sequence to allow the OTA to prcess properly.
In addition to wiping cache through recovery I have also ensured that I didn't have any apps / process or services disabled.
This is also being reported in google support forums:
https://productforums.google.com/fo...ter#!category-topic/nexus/nexus-9/MzHmJu4glkQ
I still haven't tried sideloading the OTA but at this point I don't think it would make a difference as the OTA does download properly and says it was verified.
kurtis.austin2 said:
Same issue here. Error every time I hit Restart & Install after downloading the update. Have to long press the power bottom to get it to boot back again. Tried a factory reset, didn't work. Still getting same error.
Click to expand...
Click to collapse
the.teejster said:
Thanks for sharing that you tried a factory reset. I am trying to avoid this for reasons mentioned in my 1st post.
I have tried numerous times now wiping cache and waiting for the upgrade to reappear but it continues to error out that the same place during the upgrade each time. Fortunately it's not bricking the device but IF this update is required as a stepping stone for subsequent updates then it will be extremely disappointing if Google doesn't address this issue.
I still cannot imagine google / htc not being able to resolve this WITHOUT having to make a user connect to a PC and manually flash imagess (or worse.. RMA the device). Hoping someone on XDA comes up with a magical sequence to allow the OTA to prcess properly.
In addition to wiping cache through recovery I have also ensured that I didn't have any apps / process or services disabled.
This is also being reported in google support forums:
https://productforums.google.com/fo...ter#!category-topic/nexus/nexus-9/MzHmJu4glkQ
I still haven't tried sideloading the OTA but at this point I don't think it would make a difference as the OTA does download properly and says it was verified.
Click to expand...
Click to collapse
I found this -> http://www.telekom-presse.at/apps/n...sht_update_auf_version_5-1_fehlt.id.33675.htm. There is a comment claiming to have fixed the issue by sideloading the OTA. I have yet to try it myself though.
On a side note,
Google has apparently finally released 5.1.1 for our device so it should be making it's way out soon.. HOPEFULLY we can go straight from 5.0.1 to 5.1.1 without having to worry about 5.0.2.
adstro said:
I found this -> http://www.telekom-presse.at/apps/n...sht_update_auf_version_5-1_fehlt.id.33675.htm. There is a comment claiming to have fixed the issue by sideloading the OTA. I have yet to try it myself though.
Click to expand...
Click to collapse
the.teejster said:
On a side note,
Google has apparently finally released 5.1.1 for our device so it should be making it's way out soon.. HOPEFULLY we can go straight from 5.0.1 to 5.1.1 without having to worry about 5.0.2.
Click to expand...
Click to collapse
Have you seen any evidence of this unicorn? Just curious...
Reported on the official Google+ page :
https://plus.google.com/+Nexus/posts/2hB9k5r2Z7T
But I can't find any reports of anyone actually receiving it yet. IF 5.0.2 needs to act as a stepping stone then maybe they delayed to get the 5.0.2 issue resolved 1st.. It seems to be getting more and more attention out there now.
cam30era said:
Have you seen any evidence of this unicorn? Just curious...
Click to expand...
Click to collapse
FWIW.
I went into recovery, wiped cache and tried to side load the 5.0.2 OTA update manually and got the same error. The error displayed approx. 40% into the upload process from the PC.
I'm getting frustrated I can't get 5.0.2 to install. This is ridiculous
When I get the error, Power/Vol+ switches to the recovery log - there is a warning about (from memory) a partition having been mounted R/W, and a suggestion to re-flash the device first.
All I can remember changing from stock is permitting bootloader-unlock from dev options (never got round to unlocking, so far as I remember).
Not too worried, will hang on for the next major update (or 6.x if there is a preview, maybe) - however, it seems 5.0.2 is a fix to allow 5.1.1 to download (from comments on the G+ thread)
My error is an SHA mismatch on /dev/block/platform/sdhci-tegra.3/by-name/APP. I have
47e96f7e7daa360947b456eca9dc5a8e45573b30
@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
cam30era said:
@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
Click to expand...
Click to collapse
How do I do this? Need adb from a computer?
kurtis.austin2 said:
How do I do this? Need adb from a computer?
Click to expand...
Click to collapse
Yes you need ADB and Fastboot. Follow this guide and don't hesitate to ask questions > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
cam30era said:
Yes you need ADB and Fastboot. Follow this guide and don't hesitate to ask questions > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Click to expand...
Click to collapse
Thank you ? very kind of you
kurtis.austin2 said:
Thank you ? very kind of you
Click to expand...
Click to collapse
Welcome
Please read the OP.
cam30era said:
@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
Click to expand...
Click to collapse
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.
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?
So,
This may seem mundane to some of you, and I apologize. But I'm hitting a wall with this Pixel. I cannot use Fastboot normally because I can't get access to any of the internal partitions. I have a list of them that I looked up, but fastboot will not allow me to use any fastboot flash or flashing commands that I need to flash a new ROM.
I've unlocked bootloader - Duh - (been doing this a little while)
Rebooted
Reenabled ADB - #adb reboot bootloader (works fine)
Sending files --> ADB and fastboot both will serve the image or file to the phone, but the phone fails on "partition does not exist" on every time.
I have tried re-flashing this device with the android flashing tool through Google (works fine and I'm currently running the 13 Beta T3B3). Would straight flashing from a zip file help?
I want to be running LoS but I cannot get even the vendor_boot or boot image to flash. Everything seems to be software/firmware locked and I've tried the fastboot commands to unlock certain partitions and things like that from what I can tell in the changes to fastboot. So my question is:
What am I missing? I have even got it to boot into LoS and things worked, but you could tell something was very wrong with the flash and major app/gapp issues. This was accomplished with the flash tool flashing the partitions "boot" and "vendor_boot" and "dtbo" for me to get me into the LoS recovery. From there I reset and installed via sideload like normal, flashed the rest of the partitions listed with LoS and I cannot get a working build without major app issues and major stability issues. CLI will also not give me any info on why these can't be flashed, of course, but that's not how this should work. I know it should be more stable than it is just because it's a Pixel (one would think - has been in the past) It's a Global model GB7N6 and I don't understand what the hold up is.
Any help or suggestions would be greatly appreciated! Thanks!
You need to flash the regular factory image first, not the beta!!
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
See instructions
To be fair, I just flashed the beta as a last ditch. Every try I've done was with production software.
I will absolutely try this though. Anything to straighten this mess out.
XGX5309 said:
To be fair, I just flashed the beta as a last ditch. Every try I've done was with production software.
I will absolutely try this though. Anything to straighten this mess out.
Click to expand...
Click to collapse
Hi friend
If prior attempts to fix the problem in GetSimple CMS failed, it could be worthwhile to try the beta version as a last resort. A alternative strategy can occasionally assist in solving the issue Free Fire