Hi guys,
this is a nexus 7 that i saw on sale online, owner says it can't boot and stuck here
http://center.jeddahbikers.com/uploads/images/jb13928760421.jpg
Is this something that can be saved or not, since all the resources i found are for a different error, it's the first time i saw this one.
Can anybody pitch in before i buy the device ?
It's impossible to tell. The device on the photo is stuck during booting into Android, so technically it can be booted into bootloader mode and flashed with a proper factory image, BUT the cause of the error can be hardware related (damaged emmc).
Related
First of all i apologise if this has already been asked and solved, i have searched and each time i have drawn up a blank. I have been given the mission of reloading android back on a asus nexus 7 (2012) wifi tablet. So far i have been unsuccessful in reloading it. I have attached the details given to me by "fastboot gervar all" if it helps. all i know is it is not version 3.41 and when i attempt to flash any bootloader img i get errors. the tablet will load into fastboot mode no problem, i also get the white google image with an unlocked padlock. the unit charges showing the white charge symbol. I guess the main question is can i reload the tablet into working order, or with the errors and info provided do i give up and accept defeat?:crying:
Hello Everyone,
So I've got a friend's Nexus 7 (2012) that gets stuck at the google logo when booting up now.. I'm gonna go out on a limb and assume it's probably dead but I'm trying some things to see if I can get it to do anything.
The state of the Nexus:
Will Not Boot (Stuck on google logo)
USB debugging is //NOT// enabled
Bootloader is locked
OEM unlock is not enabled
Can get into bootloader and recovery options
Clearing /cache and /data just get stuck
Running KTU84P
My current line has been to try and update the OS through the recovery options adb sideload update with an OTA update from google, I've been using images from here https://forum.xda-developers.com/showthread.php?t=1745781 for KTU84P but when I run all of them they all just get stuck at
Code:
Verifying current system...
There are no error codes, no error messages and it stays there indefinitely.
I've looked around a bit and can't see anyone else having this issue (usually they at least get an error to help them along) if anyone has seen this issue happen before or has any ideas on anything I can do to try and get the nexus to be more than an expensive paperweight that'd be great. I have a feeling there's something wrong with the storage somewhere along the line but... No real idea.
Edit: Been running for about 6 hours now, still no change
Thanks,
P110
Alright. just to get this out of the way, I used to do tech support for HTC many moons ago. like back when they were *the* name in originating new tech to smart phones. I worked my ass off to get into the R&D team that handled all the new products that got released and to our product recovery team(the idiots that try to put a good light on a bad decision made by corporate). I have rooted and installed custom ROMS and recovery software on several phones from them as well as since then with the latest being my old galaxy S7 loaded up with TWRP and lineagoe OS(although i do not remember which version now)
But i did not do literally *ANY* of that with my Xiaomi MiA1. the phone functioned how i wanted it to out of the box and with the stock ROM, i had no need or desire to do anything with the ROM.
I have all but completely given up on doing this on my own now. I have gone over every guide on the MI forums for xiaomi and i think i may have even exhausted the ones that are available here now too. I am not sure WTH the problem at this point even is but here is the lowdown:
:fingers-crossed:
got the update near the end of December/beginning of January to update my MI A1 to the new android pie version that just came out OTA(i actually have two of these phones, one i have not updated since the first update to oreo, and this one that is hardbricked from after the PIE update)
At first when i got the OTA update, my phone started to act sluggish. simple apps like messenger, or google drive that had always worked flawlessly suddenly were taking ages to load. So like any sensible person, i pulled my info to my SD card, took it out, and then did a system recovery to restore factory defaults and start with a fresh OS again, just like when windows starts behaving poorly.
only this did not fix the problem. It persisted with poor performance after the factory data reset and upon my next reboot, my phone just stopped loading when it got to the MI logo on the screen. i literally let the phone sit on this screen overnight thinking just maybe it was being slow to boot after the reset. No luck and in the morning it remained at this screen.
just to make a note:
-phone was purchased off of amazon, i have reached out to the seller(it was a business)
-phone is in CANADA, so there are no service centers
-i CANNOT enter recovery mode(pwr + volup + voldn), it just freezes at the mi screen
-i CAN enter fastboot, but cannot flash room
-bootloader is locked and i have not yet found a method that will successfully unlock it
-the miflash tool does not work(on any version what-so-ever)
-the mi unlock tool gets to 50% and then fails, cannot unlock
-i have installed minimal adb for fastboot, none of the related commands succeed(yes system sees the phone:
c:\adb>fastboot devices
91c0963c0804 fastboot)
-i cannot unlock bootloader here and cannot install twrp or any other recovery image and it will not allow it even temporarily
I've gotten desperate enough to have even gone to the extreme and tried EDL mode by using test point to enter, computer recognizes the device even as the qualcom 9008, still no luck with any of the tools or ROMs provided on Xiaomi's website.
So be real with me here ladies and gents.... should i take this thing on my next trip up a telecomm tower and biff it as hard as i can at the ground(obviously in a snowless area for the most satisfaction) or can you saintly people actually offer me some support on this to turn my brick paperweight back into a phone again?
it is also worth mentioning that this is my first post here because i have never before had a problem with following any of he guides on here to accomplish any task i've ever set out to do with an android device, but this beastly lil mother is seriously making me consider becoming an iphone person(not really but do you get the frustration here?)
I'm writing this at 5:30 in the morning after being up all night working on this task so if my info is missing somewhere along the line just poke me with stick and i will fill in the blanks as needed.
I couldn't be bothered to get and load screenshots tonight but i will get some up tomorrow after sleep, for now i am going to the graveyard to rest.
Thanks for any responses in advance here.
What error show miflash when you try to flash in edl mode?
balannaer said:
Alright. just to get this out of the way, I used to do tech support for HTC many moons ago. like back when they were *the* name in originating new tech to smart phones. I worked my ass off to get into the R&D team that handled all the new products that got released and to our product recovery team(the idiots that try to put a good light on a bad decision made by corporate). I have rooted and installed custom ROMS and recovery software on several phones from them as well as since then with the latest being my old galaxy S7 loaded up with TWRP and lineagoe OS(although i do not remember which version now)
But i did not do literally *ANY* of that with my Xiaomi MiA1. the phone functioned how i wanted it to out of the box and with the stock ROM, i had no need or desire to do anything with the ROM.
I have all but completely given up on doing this on my own now. I have gone over every guide on the MI forums for xiaomi and i think i may have even exhausted the ones that are available here now too. I am not sure WTH the problem at this point even is but here is the lowdown:
:fingers-crossed:
got the update near the end of December/beginning of January to update my MI A1 to the new android pie version that just came out OTA(i actually have two of these phones, one i have not updated since the first update to oreo, and this one that is hardbricked from after the PIE update)
At first when i got the OTA update, my phone started to act sluggish. simple apps like messenger, or google drive that had always worked flawlessly suddenly were taking ages to load. So like any sensible person, i pulled my info to my SD card, took it out, and then did a system recovery to restore factory defaults and start with a fresh OS again, just like when windows starts behaving poorly.
only this did not fix the problem. It persisted with poor performance after the factory data reset and upon my next reboot, my phone just stopped loading when it got to the MI logo on the screen. i literally let the phone sit on this screen overnight thinking just maybe it was being slow to boot after the reset. No luck and in the morning it remained at this screen.
just to make a note:
-phone was purchased off of amazon, i have reached out to the seller(it was a business)
-phone is in CANADA, so there are no service centers
-i CANNOT enter recovery mode(pwr + volup + voldn), it just freezes at the mi screen
-i CAN enter fastboot, but cannot flash room
-bootloader is locked and i have not yet found a method that will successfully unlock it
-the miflash tool does not work(on any version what-so-ever)
-the mi unlock tool gets to 50% and then fails, cannot unlock
-i have installed minimal adb for fastboot, none of the related commands succeed(yes system sees the phone:
c:\adb>fastboot devices
91c0963c0804 fastboot)
-i cannot unlock bootloader here and cannot install twrp or any other recovery image and it will not allow it even temporarily
I've gotten desperate enough to have even gone to the extreme and tried EDL mode by using test point to enter, computer recognizes the device even as the qualcom 9008, still no luck with any of the tools or ROMs provided on Xiaomi's website.
So be real with me here ladies and gents.... should i take this thing on my next trip up a telecomm tower and biff it as hard as i can at the ground(obviously in a snowless area for the most satisfaction) or can you saintly people actually offer me some support on this to turn my brick paperweight back into a phone again?
it is also worth mentioning that this is my first post here because i have never before had a problem with following any of he guides on here to accomplish any task i've ever set out to do with an android device, but this beastly lil mother is seriously making me consider becoming an iphone person(not really but do you get the frustration here?)
I'm writing this at 5:30 in the morning after being up all night working on this task so if my info is missing somewhere along the line just poke me with stick and i will fill in the blanks as needed.
I couldn't be bothered to get and load screenshots tonight but i will get some up tomorrow after sleep, for now i am going to the graveyard to rest.
Thanks for any responses in advance here.
Click to expand...
Click to collapse
take your sd card off your phone i had similar issues and fixed them that way
ccalixtro said:
What error show miflash when you try to flash in edl mode?
Click to expand...
Click to collapse
it depends on which version of the flash tool is used. the beta version of the flash tool claims that it is successful, but the phone will not load to the Android OS after that is completed and it still will not load into the recovery mode to attempt to factory reset or anything else.
other versions have given errors:
miflash 2017.7.20.0 gives the response after attempting for about 10 seconds of "ACK count don't match!"
miflash 2018.11.15.0 gives the error response of "cannot receive hello packet"
and as stated before the miflash beta goes through the complete flash process with the result stating a "success" response, but the phone will not load to OS, just remains stuck on the MI logo screen when the phone is booting up
i have some screen grabs of all this but i am not yet worthy through XDA to be permitted to share them
thanks for the reply
kuartito said:
take your sd card off your phone i had similar issues and fixed them that way
Click to expand...
Click to collapse
i dismantled the phone manually bro, when you use EDL mode this way the SIM/SD tray is removed you then remove the entire backplate and then disconnect the battery cable from the circuit board and you use the test point method to short two pins that force the system to start in EDL mode when you connect the usb-C cable, so unfortunately that is not the issue :crying:
it never seems to be the simple solutions
Thanks for the reply!
Still dead in the water on this one.
Going to look into getting a replacement, that is a disappointing end to the Xiaomi experience
Facing similar issue. Am able to flash however still stuck when device is rebooted with this message;
Supported API: 3
E: Failed to clear BCB message: failed to FSync/dev/block/bootdevice/by-name/miscperation not permitted.
Hello, Dear XDA-Developers.
I was trying some custom ROMs but when I installed Viper4Android and flashed it using Magisk the phone stucks on boot
However I have another problem, I found out that the internal storage of my phone got too small after upgrading into another version of Android, so I wanted to get back to Android 5 stock firmware completed to format the internal storage and not partitioning it as I thought so I tried to flash it in TWRP recovery but sadly after that I bricked the bootloader and the recovery. Next, I decided to flash a board image ALE-L02&L21&L23_MAA001077_Board_Software_general_05021SJN using IMAGE Download Software - IDTML01Ver1001, Still, the process got interrupted maybe because the phone was restarting itself and now I'm getting a screen that shows error after showing Huawei Ascend logo. Is there any chance to fix this dead phone but consider that my pc is no longer detecting the driver that I used to flash the board image, and I can't even turn off the phone now except if I let the battery dies.
Notice: I don't dare to use test points if there is no other choice how much it usually costs to fix it?
Basically what the title says, Back in September 12, 2021, at 4 AM I had woken up out of nowhere and I thought I'd wanted to give that engineering firmware of my lavender a try, but then I did something bad, after digging in what the issue was and why my phone wasn't booting and was stuck in the splash screen (fastboot wasn't working either), I found out that there was a firmware OEM security certificate mismatch between the UEFI Bootloader (XBL.ELF) and the "Application Bootloader" which in android's case is "Kernel Flinger" (abl.elf), the mismatch between the certificates causes the phone to not load abl.elf and it ends up getting stuck at the splash screen and does nothing.
TL;DR my phone's hard bricked and won't boot up, fastboot won't work either.
I tried to unbrick it through the "Emergency Download Mode", also known as EDL Mode, but to no avail, I keep getting the exact same error I did before the battery this phone originally came from had died.
The error is "TARGET SAID: ERROR: Only nop and sig tag can be received before authentication."
I believe I'm getting stuck at xiaomi's authentication thing but I've tried everything, flashing stock ROM, flashing engineering ROM, trying the patched firehose that was available since a long time, trying the patched firehose that was in xiaomiengs, nothing.
Before the battery had died though, if I remember correctly, when I hadn't connected the battery to the phone and turned in on in a long time, after replugging everything and turning it on, the phone would power on it's battery LED and after getting it in EDL, instead of getting an EDL Authentication error, I was getting some weird write error and it would stop, after resetting the phone back, I'd get the same write error, I'm going to retest the thing where it'd get a write error and get past the EDL auth, but I'll have to wait.
I hope you all can give me some tips on how I can unbrick it and hopefully salvage this phone, then I can have it next to my Poco X3 NFC which I got 1 month ago and 23 days ago.
Oh and also if you were wondering why I was trying to flash the engineering firmware again through EDL even though it supposedly hard bricked my phone, that's not the case at all, what actually hard bricked it was that I had flashed MIUI 10's abl.elf (Application Bootloader/Kernel Flinger) and after rebooting, it didn't boot.
I'll admit that it was very dumb of me to flash just one firmware image out of all of them, but I should mention that I did it out of being afraid over the fact that flashing the engineering firmware might've caused my device to be stuck with it until I flashed the stock/production firmware through EDL Mode, now, I know I could've flashed it through fastboot but there was another problem with fastboot and it was that it would not flash anything due to a "image size mismatch error".
What were my findings after all? Well, Lavender (AKA Redmi Note 7) seems to have encryption stuff built right into it's bootloader which was what forced me to factory reset the device (Wipe out the data partition or "userdata"), I forgot to test whether disabling encryption wouldn't cause the entire encryption to not work (It does the same in stock/production firmware).
Another thing I also found out was that the UEFI Bootloader of the engineering firmware build is that it seemed to not have OEM certificates setup properly so it allowed the booting of MIUI 12.5's Kernel Flinger binary (abl.elf), one thing that confuses me is the fact that it wouldn't boot MIUI 10's Kernel Flinger binary (abl.elf).
Okay, update here, I've been messing around, getting help from some people in Telegram and I've managed to get past EDL Auth, unfortunately for me, it says "Failed to open the SDCC Device slot 0 partition" when attempting to flash.
I tried through Qualcomm's Product Configuration Assistant Tool and I got that error, I tried through QFIL, same error, I tried through Mi Flash and various different versions, still same error.
Does anyone have any idea what the error could mean? I hope it doesn't mean that my phone's eMMC isn't dead, because from what I remember it isn't.