Related
Are there any other secret options for restoring a bricked phone other than RSD and ADB fastboot?
See here, post #45 & #49 for a synopsis: http://forum.xda-developers.com/showthread.php?t=2095536&page=5
Basically during the failed flashes my phone ID changed and now it won't verify with ADB or RSD, the device name is no longer XT987 or whatever, now the device name is "fastboot Asanti_C S" and even though the phone and pc recognize they are connected, the connection doesnt verify.
Any workarounds? Edit the XML file maybe?
Please help, desperate.
matt2k12 said:
Are there any other secret options for restoring a bricked phone other than RSD and ADB fastboot?
See here, post #45 & #49 for a synopsis: http://forum.xda-developers.com/showthread.php?t=2095536&page=5
Basically during the failed flashes my phone ID changed and now it won't verify with ADB or RSD, the device name is no longer XT987 or whatever, now the device name is "fastboot Asanti_C S" and even though the phone and pc recognize they are connected, the connection doesnt verify.
Any workarounds? Edit the XML file maybe?
Please help, desperate.
Click to expand...
Click to collapse
Device recognized by RSD Lite as "fastboot Asanti_C S" while booted to bootloader UI is completely normal.
Adb not working while booted to bootloader UI is completely normal (adbd is not running on the phone).
Does fastboot work?
What's the response to this command?
Code:
fastboot devices
I guess when I said ADB isnt working I should have said ADB fastboot isnt working. It doesnt read any commands. It just says device not connected or whatever, USB read error, something like that maybe "fails to recognize", I forget the exact term. The computer makes the chime noise for connection/de-connection and the fastboot menu on the phone says usb connected, and also RSD lite reads the device. It just fails on step 1 of the flash, USB error. The devices acknowledge that they are there, or that something is plugged in/into, but its like they can't agree on what the phone is or is supposed to be called or located or whatever.
The sprint store guy says he couldn't fix it. I don't know what I am paying $48 a year for service and repair for.
Hopefully I'm just noobing out real bad and someone can help me out but I don't think thats the case.
I will try that command when I get my phone back in about an hour. I know there is always hope but.... I dunno. I unbricked before with RSD and it was easy money. I even used ADB or whatever to push my recovery, so I am familiar with the basics, typing in some really basic code in xml or fastboot or whatever.... but as far as ADB fastboot and RSD, I think they are toast. I've restarted the computer, the programs, etc. Re-installed drivers.
kabaldan said:
Device recognized by RSD Lite as "fastboot Asanti_C S" while booted to bootloader UI is completely normal.
Adb not working while booted to bootloader UI is completely normal (adbd is not running on the phone).
Does fastboot work?
What's the response to this command?
Code:
fastboot devices
Click to expand...
Click to collapse
The response is: T069503WI4 fastboot
Well, your phone seems like being far from a brick to me, according to the info you've provided so far.
The crucial question is if you're still able to use the fastboot command to interact with the phone or not.
great.
extract the system.img and cdrom from 4.1.2 sprint FXZ and try to flash them:
Code:
fastboot flash cdrom cdrom
fastboot flash system system.img
fastboot oem fb_mode_clear
kabaldan said:
Device recognized by RSD Lite as "fastboot Asanti_C S" while booted to bootloader UI is completely normal.
Adb not working while booted to bootloader UI is completely normal (adbd is not running on the phone).
Does fastboot work?
What's the response to this command?
Code:
fastboot devices
Click to expand...
Click to collapse
After being so bummed out and missing half an important day of work and not being in contact with anyone, I just went to pick up my phone from the Sprint store... and they are going to replace it for free! It has to ship from somewhere. They also let me keep this old one, of course, cuz I bought it, but still I had no insurance only the equip protection plan and they could have asked me to swap. It does kill my plans of using the MPQ on a road trip next week unless it gets here Monday but overall I am supremely satisfied with the customer service of Sprint. Think about it: I bricked my phone on my own free will, voided the warranty, screwed it up and all this stuff.... and they are going to replace it for free with no insurance, no deductible, no cost of any kind to me! I really don't know why. I just went in and told them it bricked on the jellybean update but that I tried to fix it and I could do no more. Then when I called to check in they told me it was bricked, and I would need a new one, and by the way, you dont have insurance. I asked them if there was any warranty or anything and they said no since it had been rooted. After that I went to a meeting and then stopped by both Radio Shack and Best Buy where the phone is still selling for $550-600+ outright with the intentions of buying one and billing it to one of my jobs which I hate to do. But I came back to my office instead knowing there would be an insightful post from one of the members here and read kabaldan's post so I figured I should go get the phone and try it out. What do I have to lose right? Well, I went in and asked for my phone back and they had me waiting for a few minutes. When they came out with the phone they said "We found another option and we can give you a new replacement for $50 but you would have to sign up for insurance as part of the deal." And I was like, well sure, sign me up! So they went back to the back and I was all happy about only having to pay $50 and all this. Then next thing I know the guy comes up to me and tells me not only is it going to be free, but that the insurance he mentioned isn't mandatory either. So no change in phone bill, no change in my bank account, and Sprint makes a customer extremely happy when they didn't even have to. Only downside is the shipping time. Its not like I went in there and acted irate or made threats of leaving or anything. I have been a customer for 10 years now so it feels like a nice present. They always take care of me. When I was asking the tech why they were giving it to me for free he was kinda at a loss for words, I dont know why, maybe they didnt want everyone in the store to know they were hooking me up. So I started laughing to myself and said to him "Maybe its Sprint giving me credit back for all that LTE service I've been paying for the last 2 years huh?" (we dont have LTE in the area) And he said "They're not that nice." HAHA! So I guess the store just overrided the system or something, hooked me up on their own, I dunno. But there is one happy Sprint customer here! Thats for sure.
Now what to do with this bricked MPQ? I would love to get it running. I can't describe how much I would love that as I don't see any good qwerty sliders coming anytime in the near or far future. As you can see I always need a back up, if its not from damage its me bricking them. Worst case scenario, how much is it worth in parts? I just feel like there has to be something.that can fix it cuz its at least showing fastboot. Something is going on in there.....
kabaldan said:
great.
extract the system.img and cdrom from 4.1.2 sprint FXZ and try to flash them:
Code:
fastboot flash cdrom cdrom
fastboot flash system system.img
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Does it matter where I extract them to? Or just that they are decompressed?
Thank you for your help. I feel that if I hadn't read you post, if you hadn't posted, I might have not went back for the phone today, and maybe the same crew wouldnt have been working there, and probably I wouldnt have gotten the free phone out of the deal. It already turned from a net loss into a gain, and if you can help me with this other one it will be a great blessing in disguise. Crazy.
Sorry with all the quoting I wasn't trying to quote so many times. I know it sends an email every time.
matt2k12 said:
Does it matter where I extract them to? Or just that they are decompressed?
Thank you for your help. I feel that if I hadn't read you post, if you hadn't posted, I might have not went back for the phone today, and maybe the same crew wouldnt have been working there, and probably I wouldnt have gotten the free phone out of the deal. It already turned from a net loss into a gain, and if you can help me with this other one it will be a great blessing in disguise. Crazy.
Click to expand...
Click to collapse
The extracted cdrom and system.img files have to be placed in the directory from which you run the fastboot command.
Ok thanks I might not get to it tonight so I will report back tomorrow. Thanks again.
matt2k12 said:
The response is: T069503WI4 fastboot
Click to expand...
Click to collapse
kabaldan said:
great.
Click to expand...
Click to collapse
matt2k12 said:
Ok thanks I might not get to it tonight so I will report back tomorrow. Thanks again.
Click to expand...
Click to collapse
Yea man, if you get a serial number and 'fastboot' showing up in fastboot devices, you are golden. No brick
kabaldan said:
great.
extract the system.img and cdrom from 4.1.2 sprint FXZ and try to flash them:
Code:
fastboot flash cdrom cdrom
fastboot flash system system.img
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Ok well when I try to extract the files, there is an error on both files. They won't extract! The progress bar goes to about 60 or 80 percent then fails and the 7Zip message says "CRC failed in 'asanti_.....' File is broken." !
When I type in the "fastboot oem fb mode clear" command it says OKAY 0.007s finished. Total time 0.009s
I guess my fastboot is working and the file is broken. Maybe its a bad fzx file from Sprint? And thats why the store couldn't fix it either? I am going to try and re-download the fzx from that link and see if those files fail again.
matt2k12 said:
I guess my fastboot is working and the file is broken. Maybe its a bad fzx file from Sprint? And thats why the store couldn't fix it either? I am going to try and re-download the fzx from that link and see if those files fail again.
Click to expand...
Click to collapse
This was going to be my suggestion. I flashed with the 4.1.2 FXZ, so I doubt the download itself is bad... perhaps just your download was bad...
arrrghhh said:
This was going to be my suggestion. I flashed with the 4.1.2 FXZ, so I doubt the download itself is bad... perhaps just your download was bad...
Click to expand...
Click to collapse
Any pointers on fastbooting the whole thing? I'm still and always will be a noob, obviously. Or is it just those things 3 or 4 things you told me earlier?
matt2k12 said:
Any pointers on fastbooting the whole thing? I'm still and always will be a noob, obviously. Or is it just those things 3 or 4 things you told me earlier?
Click to expand...
Click to collapse
Well I need to do a bit more research on manually fastbooting. I'm betting if you look at that XML file you can figure out the commands it is sending, and send those same commands... This is probably where kabaldan found those other commands.
Give me a minute.
matt2k12 said:
Any pointers on fastbooting the whole thing? I'm still and always will be a noob, obviously. Or is it just those things 3 or 4 things you told me earlier?
Click to expand...
Click to collapse
Well, by your description, the process has been interrupted when you've been flashing system.
Therefore almost everything is already in place and what's missing is to flash the system and the cdrom.
Code:
fastboot flash cdrom cdrom
fastboot flash system system.img
And unset the sticky bit that tells the phone to always boot to fastboot.
Code:
fastboot oem fb_mode_clear
kabaldan said:
Well, by your description, the process has been interrupted when you've been flashing system.
Therefore almost everything is already in place and what's missing is to flash the system and the cdrom.
Code:
fastboot flash cdrom cdrom
fastboot flash system system.img
And unset the sticky bit that tells the phone to always boot to fastboot.
Code:
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Reading the XML, these are the only remaining steps after system.img is flashed other than erasing. It erases tombstones, cache and userdata, then does the fb_mode_clear.
Good luck matt2k12.
Hey guys, wanted to follow up since I let this thread sizzle...
I got the phone running on Friday. I think the Sprint store was just lazy. They had done something to the phone but it was still stuck in fastboot. Well when I got it back to my office and started messing with fastboot it restarted back on my ICS twisted ASANTI build without me even flashing or doing anything. It was almost like a failsafe mode or automatic restore or something. But there was a problem. It still had the security credentials from JB while running ICS. So it was shutting the phone down constantly, as soon as they verified.
What I ended up doing was pulling the security file from the JB zip file and placing it in the ICS zip file. Then I went to a clean ICS flash with the JB security file. Then I could do a clean upgrade to JB from there.
Did it all with RSD lite. Edited the zip files with 7zip. The security file I am referring to is gpt_main0 or whatever.
Well that's good, glad to hear you're back up and running.
So long as fastboot works and your device is recognized by a PC, I don't think you're ever really bricked. It's honestly difficult to truly and completely "brick" one of these phones, trust me...
Hey guys, I bricked it real good this time, and now my title is true. RSD doesnt show the device, and Fastboot won't work. Details:
Last night I downloaded CM10.1 at home and was going to flash it before I went to bed. Well it was a bad download or something so I was going to restore a TWRP back up I made earlier in the day. Well apparently that backup didn't flash properly and so the only thing I could get the phone to do last night was get to fastboot mode. TWRP was gone or not working. So I left it in fastboot all night and left it on the charger so I could flash it with RSD lite this morning. Everything was going good until I got to my work computer, phone still in fastboot mode, and when I plugged the phone into my computer's USB, the screen went black and fastboot went away. Now there is just a green LED showing when its plugged into the computer, or charger, and an audible noise on PC. Every now and then the "Warning Bootloader Unlocked" screen will come up and just stay there. It never goes away unless I hard reset (Power + Vol Dwn).
However, fastboot does not show the device serial number upon typing "fastboot devices". It just skips a line and doesnt do anything, just sets up another command prompt. No response. No serial #. Also when I type "adb reboot fastboot" of course it says "device not found".
I have work to do today so I am going to let it sit. Sometimes funny things happen with this phone when you let it sit for a while. Also when it runs out of batteries and gets restarted sometimes it helps. Very temperamental phone.
Any pointers? Any way to get this thing going? I'm going to let the battery drain and see if that helps but it could be 6 or 8 hours from now. Also going to clear up my computer and shut it down and restart it so I have a good working station.
Hi all,
Just having right now a BIG problem with my all new N5. I have received it a few hours ago.
I have just turned it on one time: the phone downloaded and installed an update, and I have configured my google account. After that, and before installing any app, I decided to unlock my bootloader.
Here is exactly what I have done se far:
- downloaded the ZIP archive by chainfire (CF-Auto-root tool) from this thread
- unzipped it,
- I just ran then: sudo chmod +x tools/fastboot-mac
- Then, I boot the N5 in fastboot mode
- And finally: sudo tools/fastboot-mac oem unlock
So, here, my phone asked me (on the screen) if I was sure to unlock the bootloader. I clicked on yes, and then :
- the screen turned off,
- I got on the shell:
... ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
Since, my phone does not respond to anything, the power button has no effect. It just seems off, and I can not turn it on.
So, any idea on what has just happened? I was just unlocking the bootloader through fastboot, so no heavy tweaking here...
Any help would be buch appreciated, but I have the feeling that my N5 is now a (pretty) brick...
Did you have all the drivers?
Can you get to bootloader?
pert_S said:
Did you have all the drivers?
Click to expand...
Click to collapse
Up to my knowledge, no driver is required on a mac.
pert_S said:
Can you get to bootloader?
Click to expand...
Click to collapse
No, and that's what makes me think my Nexus is dead. The device does not respond to the power button at all.
sylar12 said:
Up to my knowledge, no driver is required on a mac.
No, and that's what makes me think my Nexus is dead. The device does not respond to the power button at all.
Click to expand...
Click to collapse
Oh I see. I've never used a Mac for these things before but have you asked for help in the CF thread?
Do you see the battery icon when you plug your phone in? Try it a few times and see if the icon will show up.
pert_S said:
Oh I see. I've never used a Mac for these things before but have you asked for help in the CF thread?
Click to expand...
Click to collapse
Yep. No response so far, but the problem appears a few hours ago only.
I'm pretty sure my bootloader is corrupted. But does that prevent the device to power on?
Any other idea?
sylar12 said:
Any other idea?
Click to expand...
Click to collapse
If you can't do anything to it, then RMA. Google won't know you did something to it, because they won't be able to boot it too.
abaaaabbbb63 said:
If you can't do anything to it, then RMA. Google won't know you did something to it, because they won't be able to boot it too.
Click to expand...
Click to collapse
I have contacted google, RMA should be OK.
But I would like to understant what happened: is this because I tried to unlock from a mac? A what is the meaning of:
... ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
Just in case it could allow people to not have the same problem
sylar12 said:
Hi all,
Just having right now a BIG problem with my all new N5. I have received it a few hours ago.
I have just turned it on one time: the phone downloaded and installed an update, and I have configured my google account. After that, and before installing any app, I decided to unlock my bootloader.
Here is exactly what I have done se far:
- downloaded the ZIP archive by chainfire (CF-Auto-root tool) from this thread
- unzipped it,
- I just ran then: sudo chmod +x tools/fastboot-mac
- Then, I boot the N5 in fastboot mode
- And finally: sudo tools/fastboot-mac oem unlock
So, here, my phone asked me (on the screen) if I was sure to unlock the bootloader. I clicked on yes, and then :
- the screen turned off,
- I got on the shell:
... ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
Since, my phone does not respond to anything, the power button has no effect. It just seems off, and I can not turn it on.
So, any idea on what has just happened? I was just unlocking the bootloader through fastboot, so no heavy tweaking here...
Any help would be buch appreciated, but I have the feeling that my N5 is now a (pretty) brick...
Click to expand...
Click to collapse
Have you created a path for adb (in for windows) system/system variables/path/ commands to be recognized on your Mac (if this is needed off course)? I`am not xperienced with Macs but i guess they also need a path for passing on commands.
sylar12 said:
I have contacted google, RMA should be OK.
But I would like to understant what happened: is this because I tried to unlock from a mac? A what is the meaning of:
... ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
Just in case it could allow people to not have the same problem
Click to expand...
Click to collapse
Wait. Try this:
Press and hold the power button + BOTH volume buttons AT THE SAME TIME for about 15 seconds, then try booting.
It seems that the USB connection got interrupted, but that wouldn't normally brick your phone, nor corrupt the bootloader. Maybe it just got stuck.
Please keep us updated if you find out why this happened. I am waiting for my Nexus 5 to arrive on Monday and I was planning on doing exactly what you did.. Boot it up, configure Google account to check if everything is fine and then unlock the bootloader on a Mac. I've never used fastboot before on a mac as I only have one recently, but from what I remember of using fastboot in a windows machine, as long as we could run "fastboot devices" and got a response, everything should be fine. Isn't this the same in Macs?
Cheers.
gee2012 said:
Have you created a path for adb (in for windows) system/system variables/path/ commands to be recognized on your Mac (if this is needed off course)? I`am not xperienced with Macs but i guess they also need a path for passing on commands.
Click to expand...
Click to collapse
This is not "directly" required on mac. And the fastboot binay has been recognized by the shell, since the unlocking procedure started (my phone asked me if it was ok for unlocking the bootloader).
abaaaabbbb63 said:
Wait. Try this:
Press and hold the power button + BOTH volume buttons AT THE SAME TIME for about 15 seconds, then try booting.
It seems that the USB connection got interrupted, but that wouldn't normally brick your phone, nor corrupt the bootloader. Maybe it just got stuck.
Click to expand...
Click to collapse
I already tried this: nothing happens... I guess the phone is really bricked.
eddie_gordo said:
Please keep us updated if you find out why this happened. I am waiting for my Nexus 5 to arrive on Monday and I was planning on doing exactly what you did.. Boot it up, configure Google account to check if everything is fine and then unlock the bootloader on a Mac. I've never used fastboot before on a mac as I only have one recently, but from what I remember of using fastboot in a windows machine, as long as we could run "fastboot devices" and got a response, everything should be fine. Isn't this the same in Macs?
Cheers.
Click to expand...
Click to collapse
It should be the same, yes. Fastboot is very easy to use usually, it's the first time I have such a problem. And I have no idea why the unlocking has got wrong. 2 solutions imho:
- a phone harware problem which only reveals during the unlocking process;
- a fastboot problem/mac related problem.
Just trying to figure out which one is the correct answer.
El Daddy said:
Do you see the battery icon when you plug your phone in? Try it a few times and see if the icon will show up.
Click to expand...
Click to collapse
Sorry, just noticed your post right now.
No, nothing happens when I plug the phone in.
sylar12 said:
Sorry, just noticed your post right now.
No, nothing happens when I plug the phone in.
Click to expand...
Click to collapse
Congrats!
You have managed to be the first xda user to really brick their Nexus 5.
I'm sorry, but you'll have to rma.
sylar12 said:
Sorry, just noticed your post right now.
No, nothing happens when I plug the phone in.
Click to expand...
Click to collapse
I think you got really unlucky. Possibly a bad cable or USB port but some connection got lost while you were flashing. RMA is your best option right now. Sorry bro
abaaaabbbb63 said:
Congrats!
You have managed to be the first xda user to really brick their phone.
Click to expand...
Click to collapse
Yessssss, I did it!
...
:crying:
abaaaabbbb63 said:
I'm sorry, but you'll have to rma.
Click to expand...
Click to collapse
It should be OK I think. I just hope they will not notice I tried to unlock the phone (but if the N5 is really dead, I don't think they will).
sylar12 said:
Yessssss, I did it!
...
:crying:
It should be OK I think. I just hope they will not notice I tried to unlock the phone (but if the N5 is really dead, I don't they will).
Click to expand...
Click to collapse
You'll be fine on the rma. Been there done that on another device
sylar12 said:
Yessssss, I did it!
...
:crying:
It should be OK I think. I just hope they will not notice I tried to unlock the phone (but if the N5 is really dead, I don't think they will).
Click to expand...
Click to collapse
Maybe the XDA award for the1st N5 bricker is a new Nexus 5 32GB
abaaaabbbb63 said:
Congrats!
You have managed to be the first xda user to really brick their Nexus 5.
I'm sorry, but you'll have to rma.
Click to expand...
Click to collapse
Sorry to disappointed you but I was the first one. Last week I bricked mine
(SOLVED)
hi all. i screwed my tab up pretty bad. i think i flashed a corrupt backup.
when i turn it on, it stays on the factory Asus on image. don't know if thats the right term for it, but it's the image BEFORE boot animation starts. It will stay on that til battery dies.
when i try to go into twrp, it says "unrecoverable bootloader error" in red letters. i believe fastboot still works since when plugged into laptop, if i type "fastboot devices", it lists tablet serial number.
i think i need to flash bootloader, recovery, and rom through fastboot, BUT, never had to use fastboot and cannot find directions for it.
if it's listed somewhere, very sorry and can you point me towards it?
if not, any smart cookies wanna help me with my screw-up?
much appreciated.
I hope this helps:
http://lmgtfy.com/?q=fastboot+tutorial
Good luck!
redheadplantguy said:
hi all. i screwed my tab up pretty bad. i think i flashed a corrupt backup.
when i turn it on, it stays on the factory Asus on image. don't know if thats the right term for it, but it's the image BEFORE boot animation starts. It will stay on that til battery dies.
when i try to go into twrp, it says "unrecoverable bootloader error" in red letters. i believe fastboot still works since when plugged into laptop, if i type "fastboot devices", it lists tablet serial number.
i think i need to flash bootloader, recovery, and rom through fastboot, BUT, never had to use fastboot and cannot find directions for it.
if it's listed somewhere, very sorry and can you point me towards it?
if not, any smart cookies wanna help me with my screw-up?
much appreciated.
Click to expand...
Click to collapse
Took several days, but was finally able to get tablet working again.
long drawn out procedure, but worked, thankfully.
used this
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
thread can be closed unless it's helpful to anyone else
redheadplantguy said:
Took several days, but was finally able to get tablet working again.
long drawn out procedure, but worked, thankfully.
used this
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
thread can be closed unless it's helpful to anyone else
Click to expand...
Click to collapse
Yes that is very useful information and everyone should keep a copy somewhere
Glad you got your problem resolved. :good:
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 instructions​The 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 instructions​The 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.
So for the last three months I've been using my rooted phone with the Pixel Experience ROM, and today I decided to switch back to the stock rom. I first tried to uninstall Magisk, but when I checked the app it was already uninstalled, which I think was a bit strange. Then I downloaded the global 14.0.1 MIUI and tried to flash it via recovery mode using adb, and it failed at the end of the flashing process. So I went to try to install it using fastboot, but after using the command fastboot devices, my phone was not listed. Then I went to the recovery mode again (I was using orange fox when doing so) and tried to reboot into fastboot mode. Doing so didn't change anything when using the command to list the devices, but MiFlash had it listed, so I tried using it. I selected the rom, and selected the "clean and lock" IIRC, it started to flash and said it finished without any errors, however my phone showed some errors that I can't remember now. I tried to reboot the phone, and it went back to recovery mode, so I tried to flash it again. In this time, I tried to stop the flashing process by removing the usb because I thought I should look for the errors first, and then I remembered that I shouldn't do it (I have a very bad short term memory), so I tried to put the usb back and flashing it again. This time the Miflash showed an error, and I realized I was using the flash command while in recovery mode, not fastboot (I accidentaly pressed "adb" in the recovery), so I tried to reboot my phone to change it and it turned off. There's no more battery charging screen, fastboot or recovery. After a lot of research, I found out that my phone is in ETL mode, it shows in the device manager on my pc and also shows in the miflash as "COM3" or "COM4".
Can someone please help me? I tried so many things so far, and I still don't want to send it to repair
If you selected clean and lock and it finished, that means you locked your bootloader, and with locked bootloader, you can't flash anything. And you also yanked usb out of your phone in the middle of flashing process? My bet, you screwed up partition or two, and now your phone is in EDL, my man... Just take it to a service centre, before it's completely destoryed
When I was writing the thread I was wondering how could I be that stupid. I think I'll really need to send It to a service center.
seiguisage said:
When I was writing the thread I was wondering how could I be that stupid. I think I'll really need to send It to a service center.
Click to expand...
Click to collapse
I would be surprised if they would be of any help, except maybe to ask you to change the motherboard completely.
TheMystic said:
I would be surprised if they would be of any help, except maybe to ask you to change the motherboard completely.
Click to expand...
Click to collapse
So probably It really is just a paperweight now
seiguisage said:
So probably It really is just a paperweight now
Click to expand...
Click to collapse
If it shows signs of life, you may be able to resuscitate it. But I doubt an official service centre would be of any help here, except as stated above.
Just do some more research. You may find a way. All the best.
TheMystic said:
If it shows signs of life, you may be able to resuscitate it. But I doubt an official service centre would be of any help here, except as stated above.
Just do some more research. You may find a way. All the best.
Click to expand...
Click to collapse
Since my gf gave me her old Mi 9 I think I'll make this a new hobby lol
TheMystic said:
I would be surprised if they would be of any help, except maybe to ask you to change the motherboard completely.
Click to expand...
Click to collapse
What are you talking about. if he has access to EDL mode he can fix everything. Even if your UFS was completely wiped and had no partitions. EDL is a completely separate thing. However you can't reflash the software using EDL because only service centers have the authorisation to do that (some people have that access too, and you can reflash your phone if you pay them). Another way to do it is open the phone up, and short some pins to get access to unauthorised EDL.
TheMystic said:
If it shows signs of life, you may be able to resuscitate it.
Click to expand...
Click to collapse
Yeah, mouth-to-usb always helps.