Related
Greetings! First of all, I would like to thank anyone who takes the time to help me diagnose and resolve this issues, let alone anyone who takes the time to read this thread.
I've been having issues with my Xoom (ICS 4.0.0) for about 3 weeks now.
A brief history of the issue's occurrence:
-I unrooted the device and returned it to stock.
-Everything was fine and dandy until one day it spontaneously said something along the lines of 'Android is upgrading..', and then performed a reset.
-Since resetting, it bootloops.
The device only turns on when plugged into a charger and hard reset.
The device only turns off when allowed to boot loop for minutes and then hard reset (it simply does not reset, and just turns off).
I'm not the most technically-savvy person with android devices but here are some things I've done/noted.
When trying to use adb commands, it does not recognize the device or properly issue commands.
I've tried wiping data/clearing cache to no avail.
EDIT: I've tried fastbooting, but the bootloader will not unlock. When trying to unlock, it simply resets and then acts as though it was never unlocked.
I have no idea how to return it to a stock image. All I know is that I have a micro-SD and some spare time.
Could anyone help me understand what exactly is going on with my Xoom?
If I can provide you with any more information, please let me know.
Thanks again. (=
If it was stock and spontaneously upgraded it sounds like a bad OTA upgrade. I've been rooted from the start so never have taken an OTA upgrade...don't you need to accept it or can it just upgrade on it's own?
Anyway, can you get it into fastboot mode?
Volume up and power, then at dual core screen, press volume down...if you see something like "entering fastboot mode" you're not bricked. You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
If you haven't done so, just google 'recovering Xoom using fastboot' and you should get some good information.
Good luck!
Remember to grab the MZ604 files if you have the Wifi only version of the Xoom.
http://developer.motorola.com/products/software/ <------ Grab the files here. The files are for the US version of the Wifi Xoom only.
Instructions to return it to stock
1) First you need the Moto Drivers - Read this thread to START you - http://forum.xda-developers.com/showthread.php?t=981578
Should have these drivers installed if you have rooted your Xoom before.
2) Make sure you have the latest SDK - adb and fastboot should be in /platform-tools -
http://developer.android.com/sdk/index.html
Should have the android SDK if you have rooted your Xoom before.
3) Place all the downloaded stock image files into the SDK Tools folder.
4) If you are booting up from scratch, you can get the Xoom in fastboot mode by doing the following. Use command prompt to perform the rest of the steps
Hold VolDown and Power button will boot unit for fastboot mode
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
If you Xoom is booted up already follow the commands below using command prompt to perform the steps
adb reboot bootloader <---- reboots the Xoom into fastboot mode.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
As Always If This Was Helpful Hit the Thanks!
Yeah, what Mjamocha said...
okantomi said:
Yeah, what Mjamocha said...
Click to expand...
Click to collapse
LOL Thanks.
okantomi said:
Anyway, can you get it into fastboot mode?
Click to expand...
Click to collapse
Yes, I can. But so far nothing has been successful in terms of fastboot commands.
okantomi said:
You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
Click to expand...
Click to collapse
When I try to execute fastboot commands such as 'fastboot flash boot boot.img'.. it says the following:
Device still locked. Device must be unlocked first. Failed to process command error(0x8)
Whenever I try to unlock the bootloader, it appears to be successful at first and then the device reboots. But it just reboots to a bootloop, and the bootloader still says its locked. Perhaps I made a mistake in communication. The bootloader is currently locked and will not unlock, as just described.
When I try to unlock it and it reboots, even if I access the fastboot menu right away, it still says the device is still locked.
Thoughts?
Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.
slacka-vt said:
Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.
Click to expand...
Click to collapse
Yes, I can get into android recovery. However, within a second of switching into recovery mode, the robot falls down and there appears to be a red triangle caution sign containing an exclamation point.
When trying to do a factory reset, it says all data is wiped (as normal). Upon rebooting, it continues to bootloop. So essentially the factory reset and cache clear options in the Android Recovery menu do not produce the expected results.
Pretty odd. I didn't mess with the Xoom at all prior to this issue.
Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.
slacka-vt said:
Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.
Click to expand...
Click to collapse
Yeah, just tried it to no avail. Thanks so much for your help anyway. (=
I'm not sure what to do now.
I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.
slacka-vt said:
I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.
Click to expand...
Click to collapse
I hear ya. I've tried 2 different cords and 3 different computers. I'm using a Mac (10.6.8) right now, but have used 2 PCs (Vista + 7).
Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?
slacka-vt said:
Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?
Click to expand...
Click to collapse
I got the 'device still locked' error. Weird, huh?
How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.
slacka-vt said:
How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.
Click to expand...
Click to collapse
Yeah I tried that. Won't lock or unlock successfully. Locking produces no difference, and unlocking produces the same 'device still locked' error. This is getting out of hand! Thanks so much for your advice. You think I should open it up?
I hate to be so persistently annoying about this, but could anyone possibly suggest a method of working around the locked bootloader?
Is there anything I can do with an SD card to remedy the device's stubborn foolery?
I think you should give it a try, I have bricked my xoom a few times and have always been able to flash the stock imagine to recover. You really have nothing to lose by pulling the battery pin just be careful.
Sent from my Xoom using xda premium
I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?
cherlamperter said:
I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?
Click to expand...
Click to collapse
I have looking for a utube how to guide but no luck, I just might make one for you so you will know what to expect. Give me a few and I will get back to ya.
Sent from my Xoom using xda premium
Installed the newest patch from Google April. I restarted the device after install and it wouldnt go through.
DEVICE IS NOT ROOTED
So I went into recovery mode
I tried clearing partition... it didnt work (did that 5 times)
I tried reboot system (didnt work)
I turned it off and on like 10 times and it didnt work
I tried Wipe data/factory reset....lost everything (which sucks because I had photos that never got backed up)
I am official lost, can someone help me? I am not sure what to do next!
I have a macbook, if someone can help me I will greatly appreciate it!
agentjucey said:
Installed the newest patch from Google April. I restarted the device after install and it wouldnt go through.
Click to expand...
Click to collapse
Hello. I have this same problem.
I can't start my phone.
I have no idea what happened. Phone was connected to charger and everything looked ok, but this s**t happend ...
On error screen I've pushed power + volup button
Wipe cache
wipe device ...
nothing helped ...
Still getting this same error ...
Are you getting an error message on the screen or is the phone stuck at the boot animation?
audit13 said:
Are you getting an error message on the screen or is the phone stuck at the boot animation?
Click to expand...
Click to collapse
Android with red triangle and exclamation mark inside ...
Same problem here. This was after applying OTA latest security patch for April.
Would try to boot ("Google" word) 2x then go back to Android bot with red "!" - no command.
Tried wiping cache; factory reset - both multiple times. Still the same.
Tried also draining battery, then full re-charge, still the same problem.
Hope somebody could figure this out.
Thanks in advance.
The red triangle screen is what you see before entering recovery. To get into recovery, press the power button and press volume up.
audit13 said:
The red triangle screen is what you see before entering recovery. To get into recovery, press the power button and press volume up.
Click to expand...
Click to collapse
I did that ...
wiped cache - no result
reset to factory - no result
Flash the factory image. If your phone is not bootloader unlocked do that first
GtrCraft said:
Flash the factory image. If your phone is not bootloader unlocked do that first
Click to expand...
Click to collapse
I never did that before ... is there any tutorial for absolute beginners which you could recommend?
tupper said:
I never did that before ... is there any tutorial for absolute beginners which you could recommend?
Click to expand...
Click to collapse
Yeah its here in the general section
Flash factory images from NRT tool
1 Unlock ur bootloader
2 flash latest factory image and clear ur internal memory also! Coz the tool has an option to clear internal memory or not to clear internal memory!
3 Done!
Hello, so i have a problem. I've installed KingRoot on my LG Spirit H-420 and it worked great, then i searched a bit about this and saw some bad reviews and decided to uninstall it. Then i started searching more and saw some tutorial for rooting with kingroot and then using app called super su-me that uninstalls kingroot and installs SuperSU. So i did this and after installing SuperSU and rebooting my device my signal bar was showing nothing and i was unable to enter settings. Basically when i clicked my settings cog it opened and immediatly closed saying "Unfortunatly settings has stopped working" so i was unable to make calls and access my settings (although i was able to access my wifi/bluetooth/location settings by clicking them in my taskbar). So i unrooted with my superSU and did hard reset by turning off the device and holding vol down and power button to do the factory defaults. After it there was android logo saying working (like always i did the factory reset through my settings) but then its stuck on the boot screen for 30mins, before it hardly took 1min to reset to factory. How ****ed is my device and is there a chance to get it back to working ?
If the bootloader is at least showing the animation, then I don't think you need to worry much. Try the following to begin with:
1. Charge your device for a few hours if it is underpowered.
2. After that, go to your OEM recovery (by long pressing UpVolume + Power buttons) and clear the cache (there usually is the option to do it).
This should solve most issues with bootloop, etc. Try this and report back.
Its not showing the animation, its stuck on the first screen, the one thats showing LG logo and on the bottom there is "Powered by android" and there are no animations in it.
a7ogpl said:
Its not showing the animation, its stuck on the first screen, the one thats showing LG logo and on the bottom there is "Powered by android" and there are no animations in it.
Click to expand...
Click to collapse
Did you try the following:
1. Long press UpVol+Power buttons and see if it goes to stock recovery.
2. Long press DnVol+Power buttons and see if it goes to Fastboot recovery.
Are any of these working?
(Remember charging your device for a few hours as the first measure).
prahladyeri said:
Did you try the following:
1. Long press UpVol+Power buttons and see if it goes to stock recovery.
2. Long press DnVol+Power buttons and see if it goes to Fastboot recovery.
Are any of these working?
(Remember charging your device for a few hours as the first measure).
Click to expand...
Click to collapse
upvol is not doing anything and dnvol is going into the reset to factory defaults menu wheere i can choose yes or no. I still have the warranty and as far as i know rooting is not voiding warranty but flashing rom with kdz can void my warranty.
a7ogpl said:
upvol is not doing anything and dnvol is going into the reset to factory defaults menu wheere i can choose yes or no. I still have the warranty and as far as i know rooting is not voiding warranty but flashing rom with kdz can void my warranty.
Click to expand...
Click to collapse
>> and dnvol is going into the reset to factory defaults menu wheere i can choose yes or no
Then why don't you simply do a factory-reset and start using the device? Is it the case that you want to backup existing app data before that or something?
prahladyeri said:
>> and dnvol is going into the reset to factory defaults menu wheere i can choose yes or no
Then why don't you simply do a factory-reset and start using the device? Is it the case that you want to backup existing app data before that or something?
Click to expand...
Click to collapse
The thing i did it and it got into bootloop. If i click yes then there is an android logo with caption "deleting" and then it goes into booting screen [the one with LG Powered by android without animations] and stays like this forever
What happens when you connect to pc using usb? Is something detected using "adb devices" or "fastboot devices"?
prahladyeri said:
What happens when you connect to pc using usb? Is something detected using "adb devices" or "fastboot devices"?
Click to expand...
Click to collapse
Its saying lg h420 when i connect it and it is in the booting screen (the phone), so i basically could be able to flash it but i dont have my computer and the one here is not powerful enough so i dont trust it. I decided i will just try to give it with warranty and if they refuse then i will flash it. There is no other way now to rvive it. Thanks for help tho
Backstory: I upgraded to android 10 a few weeks ago, aside from a few user apps breaking, there weren't any system issues. Recently, I received another update (seems like a patch ?) to android 10 and updated as well. I'm not sure if this recent update actually completed.
Last night, it seems like my phone went into a boot loop while I was sleeping. When I woke up the phone was hot, and each boot was so short that there was no opportunity to go into recovery mode. I pretty much had no choice other than to let the battery drain.
So I walked away and came back a while later to a peculiar recovery screen that said "Cannot load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device."
There's only 2 options: "Try again" and "Factory data reset". `adb devices` from the PC is unable to detect my pixel 3 here. "Try again" simply attempts to boot, and I just return to this same screen again (at least it doesn't loop now). I'm reluctant to factory reset as I want to at least have the chance to back up some data.
I am able to enter fastboot from this screen using Power + Volume Down. `fastboot devices` from the PC is able to detect the phone. However, because the bootloader is locked (haven't unlocked the bl since i started using nexus/pixel phones), I don't know if there's much i can do here.
My question is, is there anything that I can try at this point to boot into android 10, recover some data, then do a factory reset ?
From fastboot, what happens if you try entering recovery? If you can get into recovery, you could sideload the OTA. https://developers.google.com/android/ota
sliding_billy said:
From fastboot, what happens if you try entering recovery? If you can get into recovery, you could sideload the OTA. https://developers.google.com/android/ota
Click to expand...
Click to collapse
It's not the "normal" recovery mode. There was the message "Cannot load android system. Your data may be corrupt." Other only options are:
- "Try again" , basically a reboot, which eventually brings me back to this screen
- "Factory Data Reset"
adb is unable to detect the phone in this mode, so I am unable to sideload an OTA.
superc0w said:
It's not the "normal" recovery mode. There was the message "Cannot load android system. Your data may be corrupt." Other only options are:
- "Try again" , basically a reboot, which eventually brings me back to this screen
- "Factory Data Reset"
adb is unable to detect the phone in this mode, so I am unable to sideload an OTA.
Click to expand...
Click to collapse
Not knowing what is available with the BL locked... Is the new rescue mode option one of the power up/down choices from your BL/Fastboot screen? That rescue mode is supposed to allow ADB command to work. If not, you are going to have to do a factory reset and if that doesn't help contact Google and RMA. Ability to get out of bricks is the biggest reason to unlock your BL (if you purchased a Google unlockable BL phone) unless you purchased a Verizon phone and can't. In that case, back to the last comment about factory reset/RMA.
superc0w said:
It's not the "normal" recovery mode. There was the message "Cannot load android system. Your data may be corrupt." Other only options are:
- "Try again" , basically a reboot, which eventually brings me back to this screen
- "Factory Data Reset"
adb is unable to detect the phone in this mode, so I am unable to sideload an OTA.
Click to expand...
Click to collapse
Had this happen and I had to do a factory reset prior to unlocking bootloader ,which as was mentioned above is way easier to fix because you can reflash factory image without wiping all data
same thing happened to me; the previous comments gave me the outline of what was needed, so thank you. now for the op:
1. on the screen that offers try again or factory erase, choose "try again"
2. IMMEDIATELY press and hold volume down
3. when you reach the bootloader screen, you may release volume down
4. this is the standard bootloader screen for pixel 3. you should be able to cycle options do so to select 'recovery" (or whatever it says. I'm not going to reboot my phone to see exactly what it says, but I'm sure you get the idea)
Hi, I have encountered device corrupt error on my pixel 4Xl few days back, after reaching out to google support and waiting for 4hrs I haven't received any resolution. In few instances device worked normally for few hours but kept on switching off. I did factory reset once as suggested but currently issue is still persistent. I am out of warranty by few months so I cannot send it google support. Please help me in fixing this issue.
Prudhvi89 said:
Hi, I have encountered device corrupt error on my pixel 4Xl few days back, after reaching out to google support and waiting for 4hrs I haven't received any resolution. In few instances device worked normally for few hours but kept on switching off. I did factory reset once as suggested but currently issue is still persistent. I am out of warranty by few months so I cannot send it google support. Please help me in fixing this issue.
Click to expand...
Click to collapse
Sounds like this problem. https://forum.xda-developers.com/t/...xxxx_sn-xxxxxxxx.4205331/page-7#post-85981389
Prudhvi89 said:
Hi, I have encountered device corrupt error on my pixel 4Xl few days back, after reaching out to google support and waiting for 4hrs I haven't received any resolution. In few instances device worked normally for few hours but kept on switching off. I did factory reset once as suggested but currently issue is still persistent. I am out of warranty by few months so I cannot send it google support. Please help me in fixing this issue.
Click to expand...
Click to collapse
So we know you get the corrupt message, support isn't helping, that in a few instances it worked normally for short periods, a factory reset didn't help, and yer out of warranty.
But can u get to fastboot? Is OEM unlocking on? Can u turn oem unlocking on in one of the "few instances", if it's not on?
If u can do the above, i'd follow googles instructions to unlock the bootloader and use the flash-all script and flash the latest firmware.
AsItLies said:
So we know you get the corrupt message, support isn't helping, that in a few instances it worked normally for short periods, a factory reset didn't help, and yer out of warranty.
But can u get to fastboot? Is OEM unlocking on? Can u turn oem unlocking on in one of the "few instances", if it's not on?
If u can do the above, i'd follow googles instructions to unlock the bootloader and use the flash-all script and flash the latest firmware.
Click to expand...
Click to collapse
Hi, thanks for responding back. Yes OEM is enabled on my device. I did reach out to google forums as well for support, they redirected to XDA for support with respect to flashing device.
PS: I am not at all a tech person and have very limited understanding in this area, I am just trying to save my phone.
Prudhvi89 said:
Hi, thanks for responding back. Yes OEM is enabled on my device. I did reach out to google forums as well for support, they redirected to XDA for support with respect to flashing device.
PS: I am not at all a tech person and have very limited understanding in this area, I am just trying to save my phone.
Click to expand...
Click to collapse
so then first follow this link and choose which version of android you'd like to flash to your 4xl (probably the latest one).
On that site click 'link' next to the chosen version and it will download the firmware zip file (this is the latest generic version: SP1A.211105.002, Nov 2021 --- if you have verizon or other choose the latest for that carrier).
Then you'll need to follow the directions near the top of that page that starts with the following:
Flashing instructionsThe factory image downloaded from this page includes a script that flashes the device, typically named flash-all.sh (On Windows systems, use flash-all.bat instead).
etc etc etc.
If you have trouble, post back here and people will try to assist you.
cheers
AsItLies said:
so then first follow this link and choose which version of android you'd like to flash to your 4xl (probably the latest one).
On that site click 'link' next to the chosen version and it will download the firmware zip file (this is the latest generic version: SP1A.211105.002, Nov 2021 --- if you have verizon or other choose the latest for that carrier).
Then you'll need to follow the directions near the top of that page that starts with the following:
Flashing instructionsThe factory image downloaded from this page includes a script that flashes the device, typically named flash-all.sh (On Windows systems, use flash-all.bat instead).
etc etc etc.
If you have trouble, post back here and people will try to assist you.
cheers
Click to expand...
Click to collapse
Hi, thanks for quick response. I am getting below error, not sure how to correct it.
Prudhvi89 said:
Hi, thanks for quick response. I am getting below error, not sure how to correct it.
Click to expand...
Click to collapse
So you're getting an error indicating you're trying to do something but it can't do it because the boot loader is locked. Obvious.
but here's what's not obvious; what are u trying to do? and why are u trying to do it?
from the looks of the output, yer trying to switch slots? why? there's nothing in those instructions I referenced above that tells u to switch slots? All yer gonna do is first unlock the bootloader and then use the flash all script.
maybe yer reading the wrong directions? Look again what I posted, find those exact words in the directions, do what's under that heading, not any other heading.
Currently I am not able to switch on my phone !!!
AsItLies said:
So you're getting an error indicating you're trying to do something but it can't do it because the boot loader is locked. Obvious.
but here's what's not obvious; what are u trying to do? and why are u trying to do it?
from the looks of the output, yer trying to switch slots? why? there's nothing in those instructions I referenced above that tells u to switch slots? All yer gonna do is first unlock the bootloader and then use the flash all script.
maybe yer reading the wrong directions? Look again what I posted, find those exact words in the directions, do what's under that heading, not any other heading.
Click to expand...
Click to collapse
Currently I am not able to switch on the device !!
Prudhvi89 said:
Currently I am not able to switch on the device !!
Click to expand...
Click to collapse
That sounds ominous. You may now be afflicted with the pixel 'stuck in edl mode' problem, which unfortunately there's no solution for.
Try this; plug the device to pc using usb cable, then look in device manager, if you see the device connected with QUSB_BULK_CID (etc), that means it's in EDL mode.
if that's the case, follow this thread to learn more about that, but unfortunately there is no fix, as yet. And I've read just yesterday google is replacing devices with this issue for some.
Just an fyi, if your device is in this state, it's not anything you did, it's the fault of the device. Some believe it to be hardware failure, which seems the most plausible explanation.
AsItLies said:
That sounds ominous. You may now be afflicted with the pixel 'stuck in edl mode' problem, which unfortunately there's no solution for.
Try this; plug the device to pc using usb cable, then look in device manager, if you see the device connected with QUSB_BULK_CID (etc), that means it's in EDL mode.
if that's the case, follow this thread to learn more about that, but unfortunately there is no fix, as yet. And I've read just yesterday google is replacing devices with this issue for some.
Just an fyi, if your device is in this state, it's not anything you did, it's the fault of the device. Some believe it to be hardware failure, which seems the most plausible explanation.
Click to expand...
Click to collapse
Ok got it !! Thanks for your prompt response & support.
The "Cannot load Android system, Your data may be corrupt" error is known as Rescue Party. Fortunately, fixing it should be relatively simple.
Try dirty flashing the factory image. Do not attempt to flash a patched boot image; leave everything stock.
If that fails, select "Factory data reset". It will wipe your phone, but it should reboot into Android system.
That bootloader message "Your device is corrupt. It can't be trusted" means that the signed key for Verified Boot somehow got screwed up. In this case, I would also recommend reflashing the factory image.
In both cases, the easiest option is to use the Android Flash Tool. It's like a GUI for flashing the factory image.
This restore process is intended for the AT&T V60 (lmv600am) model and will WIPE your data so back it up if you want to keep it!
This process will restore the lmv600am to original factory state for the AT&T v60 v20q build (a11). I’ve dumped all the required partitions from a new replacement phone sent to me by LG. This process uses the Qfil utility and assumes you already have a working knowledge of Qfil and that you have already installed it on your Windows PC. If you don’t have that knowledge start reading. The internet is full of Qfil guides.
You can’t damage or fix your existing imei relevant partitions from this restore because they aren’t included in this download.
You are responsible for backing up your existing phone partitions. I’m not liable for you using my work product and you do so at your own risk. If you’re unsure of what you’re doing then read more about Qfil and what is does. Again, if you are a newby go slow. Taking your time will save you a lot of aggravation.
This process will not fix your erased or damage imei number problem. There are process out there but they are usually reserved for people with an expert level of knowledge on the subject.
This guide is for anyone who’s presently unable to boot or who just can’t access AT&T ota services and wishes to upgrade their lmv600am to a newer a11 build. I have only tried this when my phone was already on an Android 11 rom. That’s not to say it won’t work coming from a Android 10 rom but I haven’t tried it.
This process will not fix your erased or damage imei number problem.
Steps
Download “Lmv600am v20q Restore Partitions.7z” file from ??? and unzip. Remember the unzipped restore directory path.
Plug your phone into PC with USB cable and put you phone in EDL (9008) mode. Again, there are guides on how to do this everywhere.
Start Qfil and select the port of your phone’ connection. (See Windows device manager)
Select the v60 firehose (.elf) which is included in the unzipped directory.
Select storage type = ulf which is located at the bottom right of the Qfil dialog screen. I’m using Qfil 2.0.3.5 version.
Next click on the “load XML” button and group select “rawprogram0” thru “rawprogram6” which are also in the unzipped directory, then hit OK. Next it will ask for the Patch0.xml file, hit cancel as we’re not patching anything.
Wait a few seconds and then click on the “Download” button. Qfil will now resolve all the names of the partitions to be restore and then start the download process to the phone.
When complete phone reboots as I recall.
try first time, stuck at 88%, show a error
try second time, stuck at 55% for a whole night, no error
after, stuck at a random percent every time, no error
att a11 already crossflashed to EA
Why super.bin so big? 20GB stucking at flashing super every time
peterwode said:
try first time, stuck at 88%, show a error
try second time, stuck at 55% for a whole night, no error
after, stuck at a random percent every time, no error
att a11 already crossflashed to EA
Click to expand...
Click to collapse
My guess is your pc went to sleep. Other suggestions; change usb port... change cable... change PC. This procedure has been used by myself and others multiple times without failure. Qfil does nothing more than a simple read partition / write partition. There's no magic.
peterwode said:
Why super.bin so big? 20GB stucking at flashing super every time
Click to expand...
Click to collapse
The size of the super.bin (partitions system_a and system_b) is what it is. It's not like you have a choice. Hopefully, you do realize you're restoring both sides of the phone, slot a/slot b.
hooutoo said:
My guess is your pc went to sleep. Other suggestions; change usb port... change cable... change PC. This procedure has been used by myself and others multiple times without failure. Qfil does nothing more than a simple read partition / write partition. There's no magic.
Click to expand...
Click to collapse
Everything is changed, but the problem is the same, just stucked, progress no move forward, no error message , is the configuaration setting's problem? I am using the same configuaration with the crossflash guide
Finally figured out where the problem is , after upate qpst to the latest one, everything just ok now, thanks for your sharing and help
peterwode said:
Finally figured out where the problem is , after upate qpst to the latest one, everything just ok now, thanks for your sharing and help
Click to expand...
Click to collapse
You're welcome.
sorry for my mistake, not update , it is downgrade to 2.0.2.3, with 2.0.3.5 showing zero disk reading of qfil progress in the task manager, with 2.0.2.3 you can see qfil reading data from disk from computer , i don't know if it is bug or just a showing problem.
report one issue, cann't boot when changed to slot_a
did this. boots as cricket wireless and is just doing nothing but booting with the giant smiley face logo.
is there another step I need to do? Im surprised to see cricket and not ATT
chamilun said:
did this. boots as cricket wireless and is just doing nothing but booting with the giant smiley face logo.
is there another step I need to do? Im surprised to see cricket and not ATT
Click to expand...
Click to collapse
If you're seeing any boot logo and then getting stuck it usually means that the phone is trying to get to userdata. This restore does not include userdata for obvious reasons. My guess is you needs to reformat/wipe userdata.
The easiest way is probably by entering restore mode and selecting "reset to factory" which both reformats and wipes userdata.
As for the cricket logo, no telling where that's coming from or where your phone's been. But as per the Op description, these are 100% AT&T a11 v20q partitions.
phone wont get into the android boot screen for wiping cache/userdata/etc. kinda odd...
something tells me I need to write something additional. because my ATT model was crossflashed to the EU firmware
to bypass the fingerprint bug. however, they are shutting off 3G networks on the 22nd so cant keep using.
anyone else have any idea what I need to do?
Dude.... you don't need to be at boot screen whatever that is. You need to put your phone in recovery mode. Hold -vol and pwr until phone start to boot..... then release. Immediately press/hold +vol to put phone in recovery mode. Then select fastory reset which will rebuild (reformat/wipe) userdata . There are lots of guides on how to put a v60 into recovery mode.
If you can't get into recovery then put phone into edl mode (9008), start gfil and load the eng abl img to both abl_a and abl_b. Then restart phone and put it into fastboot mode, again guides all over internet on how to get to fastboot mode. From there try "fastboot -w" command from cmd prompt using adb/fastboot tools. If that doesn't work it has to be done from recovery mode.
Be sure you have all the proper drivers. For example when going into fastboot mode you will mostly likey have to manually load the adb bootloader driver so fastboot commands can access you phone.
hooutoo said:
eng abl img
Click to expand...
Click to collapse
hooutoo said:
Dude.... you don't need to be at boot screen whatever that is. You need to put your phone in recovery mode. Hold -vol and pwr until phone start to boot..... then release. Immediately press/hold +vol to put phone in recovery mode. Then select fastory reset which will rebuild (reformat/wipe) userdata . There are lots of guides on how to put a v60 into recovery mode.
If you can't get into recovery then put phone into edl mode (9008), start gfil and load the eng abl img to both abl_a and abl_b. Then restart phone and put it into fastboot mode, again guides all over internet on how to get to fastboot mode. From there try "fastboot -w" command from cmd prompt using adb/fastboot tools. If that doesn't work it has to be done from recovery mode.
Be sure you have all the proper drivers. For example when going into fastboot mode you will mostly likey have to manually load the adb bootloader driver so fastboot commands can access you phone.
Click to expand...
Click to collapse
all done. loaded eng abl. erased userdata in fastboot. still is on cricket startup screen and just stays there booting forever
does yours say "cricket wireless" when booting? so odd how this thing is behaving
got it finally to boot by resetting phone within recovery. fastboot -w command didnt do it. Now Im getting some type
of NT error that something doesnt match. but phone is working.
thanks!
Did you follow the steps, recovery mode and factory reset? Did it complete?
chamilun said:
got it finally to boot by resetting phone within recovery. fastboot -w command didnt do it. Now Im getting some type
of NT error that something doesnt match. but phone is working.
thanks!
Click to expand...
Click to collapse
Your welcome.
NT codes is a well know error so just google it. Also, maybe check with TG group.
hooutoo said:
Your welcome.
NT codes is a well know error so just google it. Also, maybe check with TG group.
Click to expand...
Click to collapse
everything worked but something is odd. its showing as cricket boot up, LG in settings. not ATT. and the NT error.
also the hidden code menu isnt working.
somehow Ive got a frankenstein phone now. was a pure ATT phone before I crossflashed. somehow I need to figure out
what to write to the phone to get proper version back. I do have the old backup. just need to figure out how we
did the crossflashing and kind of undo