Hi everyone. Long story short, a relative let her phone fall on the floor. It made her phone turn off, if I got it right.
Since then, the phone is in a bootloop: the Huawei logo comes, and then vanishes, and the phone reboots. That prevents her from retrieving some very very very important documents of hers .
Sometimes (but I don't really get what causes this to happen), it boots into "Huawei eRecovery EMUI". But if I choose "Download latest version and recovery", and then connect to the local wifi, I get "Getting package info failed".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sometimes (but I don't really get what causes this to happen), I can make it boot to Fastboot&Rescue mode (by holding Vol-).
From there, fastboot does work; examples:
Code:
>fastboot getvar rescue_phoneinfo
rescue_phoneinfo: BAC-L21C185B170
>fastboot oem get-product-model
(bootloader) BAC-L21
>fastboot oem get-build-number
(bootloader) BAC-L21 8.0.0.354(C185)
>fastboot oem get_hwnff_ver
(bootloader) Ver2.3
>fastboot oem get-bootinfo
(bootloader) locked
>fastboot oem check-image
(bootloader) secure image verify fail
>fastboot oem battery_present_check
(bootloader) 0
So, I'd be very grateful to anyone giving me pointers on how to get access to the phone content. I can't stress enough how important these documents are.
Many, many thanks in advance.
Unless you can get it to boot into safe mode you are likely boned.
Sometimes Android will eventually do this after a couple bootup attempts when boot looping.
However this is not a normal boot loop; hardware damage is likely.
Always redundantly backup all critical data to at least 2 hdds that are physically and electronically isolated from each other and the PC.
Otherwise you will lose data... been there, done that.
blackhawk said:
Unless you can get it to boot into safe mode you are likely boned.
Sometimes Android will eventually do this after a couple bootup attempts when boot looping.
However this is not a normal boot loop; hardware damage is likely.
Click to expand...
Click to collapse
Indeed, I can't get it to boot too safe mode. And yes, hardware damage is a certainty, since I won't get anything to happen on the phone when it's not plugged.
However, do you think someone with physical access and ninja skills could make some miracle happen? If so, I'll search for one in my area (France).
blackhawk said:
Always redundantly backup all critical data to at least 2 hdds that are physically and electronically isolated from each other and the PC.
Otherwise you will lose data... been there, done that.
Click to expand...
Click to collapse
Word. That's what I've kept telling her...
mll2 said:
Indeed, I can't get it to boot too safe mode. And yes, hardware damage is a certainty, since I won't get anything to happen on the phone when it's not plugged.
However, do you think someone with physical access and ninja skills could make some miracle happen? If so, I'll search for one in my area (France).
Click to expand...
Click to collapse
Sort of physically accessing the internal memory chipset I don't see it happening.
It maybe a loose ribbon connector. If you pull the rear cover you can also try gently flexing the mobo a little bit at different points while trying to boot. It maybe a fractured solder joint. Even if you can't find it wedging the mobo at the right spot might let you get what you want.
mll2 said:
Word. That's what I've kept telling her...
Click to expand...
Click to collapse
This might have enlighten her... but I wouldn't say she was charmed.
Someone here might have a better plan for you.
For big bucks a data recovery specialist might be able to salvage the data if the internal memory chipset itself hasn't been damaged. High G loading impacts can internally damage chipsets and ICs.
One reason you should always use a good case; it spreads out the G loading spike/intensity and makes a drop survivable.
Related
Dear XDA Community,
This post will be as detailed as possible for those who enjoy detail.
It’s about the problems my EVO has been experiencing over the past 3 months and, after trying to fix the problems though IRC it seems that the attention should be brought to the forums for a larger audience. It was 3 months ago when I flashed a rom ( cannot remember the rom ) and my EVO took a turn for the worst.
What Happened :
When the rom was flashed and booted for the first time everything seemed normal but, the rom started to freeze at random. At first I though it was a normal process due to new ROM’s installs but, it kept repeating it over and over until it went into a boot loop syndrome.
Prior to these problems I did my daily clean/wipe dalvik rituals for ROM consumptions.
After 15 - 30 boot-loops my battery dies and the crusade begins.
I begin looking for another ROM to flash, to rid the sickness the previous ROM infected my EVO with. I installed my favorite (SalvageMod) and, the problems began to show. Salvage installed perfectly fine (as always) but, my phone started to lag, the speed was reduced to about 35 - 50%. It’s noticeable big time. The camera stopped working and everything seemed to be falling apart.
(RECENT)In panic I started looking for ways to RUU so I can avoid any other problems. This is when I noticed that usb was not accessible. I couldn’t mount my device; [CLICK HERE FOR VIDEO], so I used a SD card reader to RUU my phone and get it back to stock.
Phone is back on stock settings but, no root and, without usb support revolutionary.io is lightyears ahead of my time.
Problems :
Not mountable through usb cable [SD Card Reader option / Software Error]
System lag noticeable slower (BestBuy rep even confirmed its unresponsiveness)
Device will not charge when on [Either mount / Software Error],
Camera problems.
[Click Here For Second Video]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So can you guys help a member get his EVO back in business, my wallet would greatly appreciate it.
Thanks,
samthewildone
Aspiring Mathematician
Well, the easy way out is that now that you're back on stock and a rep has agreed the phone is not working properly and you have no USB, trade it in
I would right click on that device and uninstall the drivers. then hook the phone up to the PC and see if it automatically installs the correct drivers or find better drivers.
This may have been covered, and it looks like there's a lot more going on then just drive issues, but to get this phone into a state in which you can root it and wipe it again, you need to eliminate that variable.
Not saying that the USB drivers are even an issue, but its something worth exploring first and foremost.
Tried that, as in my thread. I uninstalled and reinstalled drivers and, it just keeps showing what that picture shows above. The phone isn't damaged but, the software is borked due to a bad bad kernel or ROM flash.
Not a solution to your problem, but if you are still s-off then you don't need Revolutionary. You can put a PC36IMG of a (reliable, ie Amon Ra) recovery on your SD card. From there you can wipe thoroughly and try flashing something else.
Unfortunately it seems like some sort of hardware failure, so the only fix could be getting a replacement.
Supersonic Evo 4G | MIUI | Tapatalk
Seems like you've gone through the same steps I would've gone through to fix it. Apart from the possible driver issue the phone should still charge when plugged into a wall charger. The fact that it doesn't, in tandem with the inability to access USB via computer, tells me that most likely you've got a hardware failure. Take it to Sprint and get a replacement. Problem solved.
TL;DR: Really three questions
What kind of effort can/should we expect from Google Support?
Is there an escalation support path for real troubleshooting?
What's the best course of action to attempt to determine root cause?
The Setup
While driving to work this morning my stock Pixel 2 XL (locked, not rooted etc.) entered a boot loop then settled on this error (image):
Code:
Android Recovery
Can't 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
I couldn't do much since I was driving but I selected 'Try again' a number of times when traffic stopped before giving up.
When I arrived at work I continued fiddling with it for a few hours, select 'Try again', power off, power on, fastboot etc.
Although debugging was enabled prior, could only see a device in fastboot or when in adb sideload mode.
When I attempted to go into recovery mode it would just take me back to the same screen.
I just assumed I'd have to wipe and start over
About 2 hours ago I was getting ready to factory reset/wipe the phone but thought I'd try fidgeting once more like I had been doing all day.
I don't know what I did but it booted to a screen displaying this error:
Code:
No valid operating system could be found.
The device will not boot.
Visit this link on another device
g.co/ABH
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then the phone turned off.
I turned it back on, and I don't think I did anything differently, and suddenly it booted normally.
The only unusual thing I saw was a notification stating that Android was finishing up system updates - or something to that effect.
With the phone up, I backed up what little data had not yet been backed up, booted into safe mode then booted back into normal mode.
So far so good...?
My Complaint
I contacted Google support earlier in the day and the experience was just sad.
The person said that I would need to factory reset my phone.
But then quickly said that before doing so I would need to backup my data.
So I asked "How?" and they said "plug it into your machine and you can see it on your computer"
I went along with their script, specifically asking for detailed step by step instructions on what to do, how to do it and what to look for.
When I said it didn't work they said I would have to take it to a repair center first to get it repaired then once fixed I could back it up then perform the factory reset.
*smh*
Later, about 2.5 hours ago now, once the phone came back up, I backed up what little data needed backing up and contacted support a second time.
This time, the person said: "Now, if we need to restart the phone and check if the boot looping is triggered or not. If it does, then we need to do some troubleshooting steps here."
So I naturally asked "What are the troubleshooting steps if it enters into that state again?" but they couldn't provide any.
I just want to know root cause. Since this was an OS boot problem, surely there's a log somewhere that might reveal what happened or at the very least provide a clue. Right?
this is my pop's phone, he said he forgot how he got here, but…
here it is, nothing really works. cannot boot to android or recovery, cannot even see the bios(?) logo.
booting to bootloader is fine, but somehow it's like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
the BL and Baseband are both N/A.
tried these methods:
fastboot update system.zip
return "FAILED (remote: flash write failure)"
fastboot flash bootloader bootloader.img
return "FAILED (remote: Verify bootloader image failed on production device.)"
fastboot boot twrp.img
return "FAILED (status read failed (No such device))"
any ideas?
It's probably nuked some partitions on the UFS chip, judging by the "no such device" error. Your best bet is desoldering that UFS chip and repartitioning it.
Its the 128GB model with the Toshiba chipset. These chipsets are notorious for dying out of the blue. Most likely the chip is dead. As the user above says it nuked a partition, this seems wrong because even if the whole chip was written over with zeroes, the BL would still be able to be identified. This is the chipsets job to identify the BL version. My suggestion is to get a RMA for a new one and see if its possible that you can refuse the 128 gb model. These models are completely unstable and Google should be ashamed of it.
djared704 said:
Its the 128GB model with the Toshiba chipset. These chipsets are notorious for dying out of the blue. Most likely the chip is dead. As the user above says it nuked a partition, this seems wrong because even if the whole chip was written over with zeroes, the BL would still be able to be identified. This is the chipsets job to identify the BL version. My suggestion is to get a RMA for a new one and see if its possible that you can refuse the 128 gb model. These models are completely unstable and Google should be ashamed of it.
Click to expand...
Click to collapse
RMA?
Homeboy76 said:
RMA?
Click to expand...
Click to collapse
I have one last resort solution. This seems very mis-typical as I don't see it working. Keep pressing "Reboot bootloader" until you see at least a "Baseband = (Code)" It could be hundreds of times. If you dont see it after constantly rebooting, try to keep booting the stock recovery. Over and over. I just dealt with a user that had a 32gb pixel with a issue like yours, except he had a valid baseband code. If this doesnt work you may have to go to the shop and get it fixed or RMA.
djared704 said:
I have one last resort solution. This seems very mis-typical as I don't see it working. Keep pressing "Reboot bootloader" until you see at least a "Baseband = (Code)" It could be hundreds of times. If you dont see it after constantly rebooting, try to keep booting the stock recovery. Over and over. I just dealt with a user that had a 32gb pixel with a issue like yours, except he had a valid baseband code. If this doesnt work you may have to go to the shop and get it fixed or RMA.
Click to expand...
Click to collapse
thanks for the replies... somehow i didn't receive notifications about the replies, i thought i didn't get any reply
i actually tried rebooting so many times, and nothing changed. so i just got him a new phone, problem solved.
I am helping someone with this phone, so I don't have all the details, but I know the phone was rooted and most likely it was running stock Android 10. It had been working fine until a factory reset (from Android settings I am assuming) was done on it.
1. Now when it turned on, it displays the "Bootloader unlocked" warning:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. After the message, it goes to the Google logo for a second and then to the TEAMWIN splash screen, and it just stays there. I have to long-press the power button to power it off.
3. I can get into the bootloader using the power and volume-down keys, and the "Barcodes", "Restart bootloader" and "Power off" option work, but "Start" and "Recovery mode" just take me back to step 1 and then 2.
So, I cannot get into "Recovery mode". I have also connected the phone to my pc (Ubuntu), but the OS does not detect it, so I cannot use fastboot either.
Any ideas on how to fix this?
If you cant connect to it via fastboot while its in bootloader mode things are grim, thats your best bet at fixing it...
Connect to PC and flash the Android 10 stock ROM by running flash-all.bat while phone is at bootloader
Without editing the flash-all.bat file to remove the -w flashing stock ROM will format user data
Thats it
The state of the phone in the pic does not inspire confidence....
Im starting to think the two things are related....
73sydney said:
If you cant connect to it via fastboot while its in bootloader mode things are grim, thats your best bet at fixing it...
Connect to PC and flash the Android 10 stock ROM by running flash-all.bat while phone is at bootloader
Without editing the flash-all.bat file to remove the -w flashing stock ROM will format user data
Thats it
The state of the phone in the pic does not inspire confidence....
Im starting to think the two things are related....
Click to expand...
Click to collapse
After connecting a working and identical phone to my PC, I found out that the reason my PC didn't detect this phone was that the USB port on phone was dirty and the connector didn't go all the way in.
After I cleaned the USB port I was able to flash the stock ROM to it. I was getting an error mid-way through, so I removed the "-w" as per your advice, tried again and it worked. The phone works now. Thank you 73sydenay!
I would like to mark this thread as solved, but I am not sure how to do that, I don't see an option to edit the title.
droidmart said:
I would like to mark this thread as solved, but I am not sure how to do that, I don't see an option to edit the title.
Click to expand...
Click to collapse
Hi,
You could press edit > advanced and edit your title with:
[SOLVED] Pixel 2 XL (rooted) bootlooping to TEAMWIN splash after factory reset
Cheers...
Sébastien.
I am very sorry to hijack a different device's forum, but XDA mods have neglected the F4 GT and we don't have a device forum of our own.
Hopefully the devices are similar enough (that being a modern Qualcomm SoC and running A12 based MIUI13) that you guys can help me solve my issue.
What happened is that I've been trying to enable voWiFi and make it stick while on airplane mode (WiFi re-enabled of course).
After a lot of back and forth with my carrier they did a kind of hard reset on my phone line. I didn't get 4/5G service for a long while, even after restarting multiple times, so I went to the test mode tool (dialing *#*#4636#*#*, which I've done several times before) and tried changing the preferred network type.
Out of desperation, after I nearly selected every other option, I selected TDSCDMA only, which is the only thing I've done differently compared to other times, and I got 4G and 5G working right after my phone did some funky radio reset (maybe a warning sign), but still no voWiFi. Decided to restart and that's when I lost the second sim slot, along with the voWiFi toggle, though it seems to connect just fine now.
Setting the preferred network type to anything else didn't solve the issue, even after several restarts the second SIM is still nowhere to be found.
After that happened the CIT menu shows both IMEI numbers as the same. (Had to censor it, but they are indeed the same).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've read that a factory reset might solve this, but I'd prefer another solution in the meantime. I will factory reset when an AOSP based ROM is released but I don't really want to go through the huge trouble of setting up my device again if I can avoid it.
All other suggestions involve messing with some partitions on TWRP, and while I'm unlocked, rooted and have TWRP installed I don't see why I should go that route when I was using built in tools of Android/MIUI. I'm not entirely aware to the ways that test tool works, but I can't see any where it corrupted anything besides a configuration file somewhere, certainly not messing with any other partitions' files.
I've also read that some AT commands might fix this without messing with anything, but I can't wrap my head around what I have to do (I do know where I can issue those commands, just not the commands themselves and what each does). The page I read mentions it's a temporary fix and it doesn't persist after a factory wipe, but that's kind of what I need right now.
While I don't currently own 2 sims, I was going to get one soon, and if this is a deeper issue, I'd like to know ASAP so that I can restore my phone as it came from Xiaomi and send it to warranty.
And yes, I tried inserting my current SIM in the second slot and it's not detected at all.
Is there some config file I can delete/modify that will solve this? I've already re-flashed my current ROM (as it was also suggested somewhere) and nothing happened. I haven't tried flashing through fastboot, but I don't think it's going to be different, right? Is there something related to this that fastboot would flash that a recovery zip wouldn't? Also, not going to have access to a PC where I could do this for a while (I have a Ryzen PC and it doesn't play well with my phone/fastboot).
Hope you guys can help me.
Oh, no one? Maybe I should post this again on a more general sub-forum.
Or would it be better if it was moved by a moderator?
If you don't want to factory reset everything, why not flash system partition then only and keep app data?
dagoban said:
If you don't want to factory reset everything, why not flash system partition then only and keep app data?
Click to expand...
Click to collapse
Well I tried that and the problem persists; that's one of the many reasons I suspect it has something to do with some config file on the data partition.
I'm thinking on doing the factory reset anyway and try a GSI ROM through DSU, MIUI really gets to my nerves, though I'm still a bit on the fence
Reflash the modem files, that should fix it. If you make changes with QPST it also changes the modem partitions.
Can a moderator move this to the freshly created ingres device forum please?