I have encountered device corrupt error on my pixel 4Xl few days back.. In few instances device worked normally for few hours but kept on switching off and getting the same error as device corrupt. I did factory reset once when I could switch on the device as suggested but currently issue is still persistent. I am using original OS Android 12 with latest Nov security update installed. I have never sideloaded any apps or done any changes to my OS. Device is always upto date with updates available. Please help me with any resolution to fix this issue. Currently my phone is out of warranty by few months.
@Prudhvi89
Sounds like your bootloader is locked? If you have done a factory reset and the issue is still there it is more than likely a hardware issue you cannot fix. You could try flashing a full OTA image from recovery mode using adb on your computer. If this sounds like too much, I would still call Google. I have had my phone replaced twice, once outside the warranty. Just explain everything you have done so far (they may ask you to factory reset again to verify) but you may end up being covered out of warranty. It is definitely worth a try.
Hello,
did you do an OTA update before your problem ? If yes, it's not the right one that you used, in this case, you just have to update again with the right version.
Hey!
Did you try this tool form google: https://flash.android.com/welcome?continue=/?hl=pt-br
It allows you to flash firmware, even if the bootloader is locked. If the botloader is unlocked it allows to make a full firmware flash, if not it flashes only some partitions.
If it doesn't help, and you have the bootloader locked, you will need to use the EDL mode.
More on that on this thread!
Related
Hi,
So I wanted to prepare my unlocked Nexus 6 on T-mobile for my brother by completely un-rooting and then relocking to setup stock firmware. With the help of “Nexus Root Toolkit” it was a quick update. I simply picked up the latest firmware for t-mobile, then relocked - and off you go.
The Phone was ok for couple of days, but then google pushed new update – which would render my phone useless. After update Initially the phone went through the boot almost to the end, and then exception happened. Something about system UI crashing and then screen was unavailable. So I could not do anything on the phone.
I tried fixing with “Nexus Root Toolkit” (unlocking, rooting etc.), but at this point the phone is stock on booting (few colored dots signifying loading), but the phone never actually boots. Going to Factory reset or Recovery does nothing.
Is there anything else I can try please?
Thanks,
-Mariusz
keinam.ty said:
Hi,
So I wanted to prepare my unlocked Nexus 6 on T-mobile for my brother by completely un-rooting and then relocking to setup stock firmware. With the help of “Nexus Root Toolkit” it was a quick update. I simply picked up the latest firmware for t-mobile, then relocked - and off you go.
The Phone was ok for couple of days, but then google pushed new update – which would render my phone useless. After update Initially the phone went through the boot almost to the end, and then exception happened. Something about system UI crashing and then screen was unavailable. So I could not do anything on the phone.
I tried fixing with “Nexus Root Toolkit” (unlocking, rooting etc.), but at this point the phone is stock on booting (few colored dots signifying loading), but the phone never actually boots. Going to Factory reset or Recovery does nothing.
Is there anything else I can try please?
Thanks,
-Mariusz
Click to expand...
Click to collapse
There's not much you can do here. If you don't have TWRP or unlocked bootloader, you should just RMA the device direct through Motorola.
You could try to sideload the update you had received that caused this.
Other than that, RMA.
I was hoping not to hear RMA - but thanks for the reply.
I recently had to replace the motherboard on my Nexus 6. I could only find refurbished ones, and bought one on AliExpress, with item description clearly specifying as unlock. I installed it, and it appears it is actually locked status 2. Looks like demo version used in T-Mobile retail network. Some settings inaccessible u such as developer mode or Apps. Trying to get refund but both AliExpress and the vendor are in denial mode.
I have 7.0, NBD92G installed. Very hard to unlock as I cannot access developer mode to allow usb debug. Pressing build nr several times won't help. I get message "you're already a developer" but actually usb debug does not work.
Anybody can help?
Go download factory image from Google and flash it manually by using the command prompt.
@ShernDog: He can't as his bootloader is locked. He can however download an OTA and sideload it.
Strephon Alkhalikoi said:
@ShernDog: He can't as his bootloader is locked. He can however download an OTA and sideload it.
Click to expand...
Click to collapse
Thanks. You are right, bootloader is locked too. Would there be any instructions somewhere on your proposed solution (sorry I am rather inexperienced user).
FYBRU said:
Thanks. You are right, bootloader is locked too. Would there be any instructions somewhere on your proposed solution (sorry I am rather inexperienced user).
Click to expand...
Click to collapse
I think I figured out how to do this but the other question is whether I won't be stuck afterwards being requested to enter the only registered user's login which I do not have (I cannot register a second user, as this setting screen is locked too). Do I need to sideload the OTA corresponding to current version / build or can I sideload an older one?
Download the oldest OTA available, as long as it is a full system OTA (easily detectable by size). You're going to have to bypass Factory Reset Protection to be able to resolve this, and the older the OTA, the better.
If this doesn't work, you're going to have to fight with the place you got the motherboard from, and file a chargeback with your credit card company if need be.
Ultimately I can go for the refund, but there is no place where I can find 64 GB MBs outside China, which means I'll have to wait again for something like 3 weeks with poor backup device, and with no certainty I don't receive again a locked MB.
I tried with 6.0 OTAs (page with instructions I followed: https://developers.google.com/android/ota#shamu) and even with just older versions of 7.0, I got every time abortion after about 45% installation, with the msg that I cannot update with older versions.
I am a bit confused now, I just tried to install same build as what I had installed (https://dl.google.com/dl/android/aosp/shamu-ota-nbd92g-2b65257b.zip), it worked but it looks like absolutely nothing has changed on my phone. I thought it would have erased pretty much everything. Am I missing something?
OTA updates don't wipe system. That's why nothing changed.
Ultimately, I think you're going to have to go for the refund and take the risk that the next motherboard you get is going to be locked. Unless the version of Android you're on can have its FRP bypassed - and I don't think it can - you're stuck.
Thanks, bad news. Would it be worth trying wipe data / factory reset accessible from the recovery mode + power/volume up menu ?
You can try it, but it won't help. Doing a factory reset will cause Factory Reset Protection to kick in, meaning you'd need to know the original owner's account information.
Surprisingly it worked. I could log in with the google account I used before the reset. Everything works, but indeed I was expecting some more difficulties
@FYBRU: This is one of those times where I'm pleased to be wrong. LOL.
Glad you got it resolved.
Hi. So I decided it was time to move to EMUI 9 and after looking at various posts on here I believe the easiest way was to you EMUI Flasher to flash the ROM (coming from 8.1 rooted).
The phone restarted and went to EMUI installer but after 10% or so I got an error. It asked if I wanted to go to erecovery or reboot the device (I think). As far as I was concerned it was only checked that the ROM was OK and hadn't installed anything so I selected reboot. Now the phone won't come on. I've tried holding the power button for an inordinate period of time but it's not happening.
Is there anything I can do?
EDIT - I've tried a different USB port on my PC and can see something in the device manager now ---- Kedacom USB Device > Android Bootloader Interface ---- which gives me a sliver of hope this can be fixed.
EDIT2 - I could send img files through fastboot all day (phone was recognised even though it wouldn't turn on) but couldn't fix this. Gave DC Phoenix a try but no luck there either. Think I've killed it.
EDIT3 - Just in case anyone ever comes across this. I tried below but nothing would work so I contacted someone on Telegram who said the only option was to open the phone up and short it out. No way I was attempting that so I eventually contacted Huawei UK and told them it had died during an update, never let on that it was MY fault! Anyway, they sent out a prepaid envelope to send to a their repair partner. I won't name them here but they have terrible reviews on Yelp so I was a bit apprehensive. I know the phone arrived with them last Friday as I checked the post tracking but I never heard anything from them. Today out of the blue my phone has come back to me in full working order, repaired under warranty! Considering there was only one thing I was really using root for and it was only a slight convenience, I think I'll just leave it as is.
Are you able to flash anything in fastboot?
Are you able to boot to recovery via fastboot? Disconnect the cable after you give the reboot recovery command in fastboot.
You may be able to flash each component of emui, system, vendor, oeminfo, kernel etc. Seems that it's missing most or all of it.
Bootloader sounds like it's intact.
Btw. The easiest way to update to emui would be to wait for an OTA from Huawei.
Personally I don't see a point, pie is not as efficient as Oreo nor does it have any features to merit an upgrade, in fact you would lose features (4k zooming, functional TWRP)
--> From Motorola, but do at your own risk, as always! <---
Lenovo Motorola Smart Assistant - "lmsa"
I've played with, and done some more research on lmsa.
I am wondering if this would help some folks here.
Please report back success or failure and your particular symptom so others will know.
NOTE: my phone is bootloader unlocked XT1900-1 One fi which OTA'ed itself up from 8.1 to 9 Oct 1 '19 security.
If you are able to back anything up, do so before you do this - if successful, it will flash your phone.
go here
https://www.motorola.com/us/lenovo-motorola-smart-assistant
and download it.
Watch the video for software issues(lower left of that page).
Install it.
Start it up.
You want flash/ rescue.
follow the instructions and put your phone into fastboot mode and connect to PC via USB.
If it offers you something(takes a minute), click the little download arrow and when it's downloaded, click rescue.
This is what it looks like for me before I would click the download arrow.
I believe this tool is for people who have a locked bootloader, never unlocked? LMSA won't recognize my device. RSD lite won't either.
Persistent memory has some value that is not overwritten by Wipe All twrp? Of course I will never relock.... just a heads up to others.
I am one of the few.... 1900-1 Fi working fine on Aug Pie factory and wanted to try ionOS. Flashed fine and working good. Now 3 carriers in my area only US Cellular has service. T-Mob--, Sprin- coverage area 10 - 0% Found as I have before No ROM other than stock for ME can get Data services to work on all three carriers in my area. So for data services trying to reflash back to stock. NO factory image successfully flashed will have modems working. For me. Tried many forms of flash modems only via fastboot, nope.
Different flavors of ADB don't help. Now I haven't tried "Hardware tools loader" style because if wrong will brick it. Unless some one has? Various forms of flashing modems, flash all scripts, ADB versions, Hardware only flash from two ROMs (which is why I am here I think) the Wipe All needed for those two roms some how did it? No blame, just for some reason can't flash back to stock. Others have but....I can't. So hoping a forward update by Motorola Factory Image will do a complete modem working Flash.
kkjb said:
I believe this tool is for people who have a locked bootloader, never unlocked? LMSA won't recognize my device. RSD lite won't either....
Click to expand...
Click to collapse
My phone IS bootloader unlocked - I bought it used(ebay) and it came to me that way with a fresh 8.1 It gives the usual bootloader unlocked error message on boot. It has OTA updated itself to 9 Oct 1 '19 security. I have not tried to modify it because that would prevent me from getting future OTAs.
RSDlite latest (6.2.4) does not recognize my phone. That is RSDlite's fault. I don't think it is yet capable of an A/B phone, let alone a full Treble (ours, on 9, are not full Treble, only partial but DO have A/B sets of partitions).
From the attached pic you can see it was ready to flash my phone with the latest stock ROM appropriate for my device which is a 1900-1 One fi, even though it was unlocked.
I am guessing that Motorola invented lmsa to stem the flow of trashed phones to Moto factory repair. It wouldn't surprise me if it would auto blankflash if necessary.
Try it - it only takes a minute or 2 to test! The worst it can say is "no"!
Understand, tried all the options and LMSA needs I think a stock recovery, boot, fastboot flash mode. The various options show "phone not recognized" no mode available with twrp installed to goto Factory Flash as LMSA appears to wait for in Bootloader Mode. So the drop down box screen will not appear since not recognized.
This post was just a update as you had asked for others to give their results. So going to do hand flash of factory images again, see if try many times... and some how one works
kkjb said:
Understand, tried all the options and LMSA needs I think a stock recovery, boot, fastboot flash mode. The various options show "phone not recognized" no mode available with twrp installed to goto Factory Flash as LMSA appears to wait for in Bootloader Mode. So the drop down box screen will not appear since not recognized.
This post was just a update as you had asked for others to give their results. So going to do hand flash of factory images again, see if try many times... and some how one works
Click to expand...
Click to collapse
Thanks.
Bummer this didn't work for you.
Yeah phone definitely needs to be in fastboot mode.
Hopefully it will help others.
Yeah, back when RSDlite worked you could "sledge hammer" just about anything if it would boot to fastboot! Hopefully they will upgrade it...
No Thank You, you gave me some ideas about the a/b devices thoughts. We have the odd ball not 9.0 at release device so the a/b script is different than some devices. So with the newest ROMs using fastboot "flash all zip scripts" for a/b boot slots I think the problem is factory images want something else for the modems. Oddly the factory images flash fine with no errors just that no modems...imei, wifi, blutooth. 8.0,8.1,9.0 all. Its a weird problem.
kkjb said:
No Thank You, you gave me some ideas about the a/b devices thoughts. We have the odd ball not 9.0 at release device so the a/b script is different than some devices. So with the newest ROMs using fastboot "flash all zip scripts" for a/b boot slots I think the problem is factory images want something else for the modems. Oddly the factory images flash fine with no errors just that no modems...imei, wifi, blutooth. 8.0,8.1,9.0 all. Its a weird problem.
Click to expand...
Click to collapse
Yeah I was thinking a-/b prob
If you ran the "flash all fi bat" to install ionOS it would have worked well since, with Aug 9, you were in a 2 file system phone. so i am guessing
a) you would only have success flashing a 9 stock (fi or not)
b) you would probably have to do a preliminary flash with just the stock 9 bootloader etc (the stuff before the ping. as well as maybe the 2 modem erases later in the command stack - some playing needed there...) tons of guesswork and luck needed here!
c) I found it humorous that ionOS script made b active but I hope the dev knew what he/she were doing.
edit d) so what partitions set is active after you flash your tests? ie you flash something, but what are you then booting to - unless you set something active... I don't believe there is a default - just last successful - though I assume if one fails it will try the other. Perhaps endlessly.
But, yeah, I can see why that flash went well. But of course you are then stuck with the modems they flashed and how that particular opsys planed to use them. US cellular is apparently known to be iffy on the X4 since I saw that caveat on a number of ebay x4 sales - "not guaranteed for...". And Sprint, of course is cdma but is supposedly accessible as LTE by fi??? I have zero knowledge there!!!
WARNING WHEN DEALING WITH ME - I TEND TO MAKE A POST AND THEN KEEP EDITING IT ENDLESSLY>>> SORRY!
Most of the time I am the guy helping people out. This time I think I did something pretty dumb.
I have an old "beater" P9 plus that I was using as a casual gaming device. Most of the apps I was using were beginning to no longer be supported because for some reason the device NEVER updated. Any time I check for a possible update the phone stated it was up to date. After much searching I discovered that this device SHOULD have updated quite a few times.
I used firmware finder to find a supported update and the first one went somewhat unexpected. The firmware was downloaded and put in the correct folders but kept failing after 5%. I decided that the next thing to do was to find a cool rom and go through the process of unlocking and installing TWRP. I usually try to install the latest TWRP. This turned out not working at all so I went for an older version and it booted into TWRP, however it found the update and installed it!
I kind of wanted to keep it stock, but updated stock so I went for a bigger upgrade to Android 7 firmware. This only worked partially and (stupid and I know better) forgot to do a backup. I did not know that TWRP was gone and root was gone. The battery died and I rebooted like normal and there was a much improved interface. However, a good bit of stuff stopped working like bluetooth and the boot screen was in red stating the device can't be verified and ended up in something like a NOR905 test keys build. I did a backup, selected a downgrade package that was checked and "updated" to the downgraded firmware through Project Menu. It successfully stated it was 100% complete.
Now it is stuck on the boot screen for an unlocked device.
What works (or is possibly a good thing):
The hardware keys can get me to the bootloader (fastboot)
ADB recognizes the device is in fastboot
Phone is Unlocked
FRP is unlock
What doesn't work:
Everything else. All I have is fastboot and an unlocked bootloader. I can try to flash recovery but that never boots, it just stays suck on the recovery boot screen. The system will not boot at all.
UPDATE:
I broke down and spent the money to use the DC-Phoenix software to unbrick the phone. Several of the options for firmware did NOT work. The one file set that did work was to use this firmware:
VIE-L29_C900B101_Firmware_countryValue_Nonspecific_Android_6.0_EMUI4.1
Then use this as the customization:
update_data_C900B101_hw_default
The phone originally started out as VIE-L29C636B130. This changed it to VIE-L29C900B101 and is on EMUI 4.1 android version 6.
Now the fun part is going to see if I can find a version of TWRP that will work and see if I can root it. Maybe even try a custom ROM. We'll see though. The device is just an old beater for fun. But at least, she's not broken anymore. Guess I'll grab a beer and celebrate my "unbricked" device.