Database Users

Possible Bricked Tablet - Please Help!

I think i may have bricked my nexus 10.. I was trying to install the chainfire3d application from the market, and when it rebooted, it wouldnt go past the X logo. waited for a long time, so i tried a hard reset, and still nothing. So i figured i would try using the toolkit to help fix. tried to relock, flash, and re-unlock, and it wouldnt work..after the step where you go into factory reset/wipe, it woudlnt go further. I cant get a custom recovery to install, it wont save the file. tried doing that step separately, and it seems to stick on sending the file over. this seems to be a common issue with anything i try.
The screen says:
"sending TWRP touch recovery..
sending 'recovery' (7246 KB) ...
and is just stuck there. this seems to happen in several places, with a few different things ive tried. When trying to flash the stock image, it will get stuck in similar places, perhaps not with the recovery step, but with a portion of the stock image. Been at this for a couple of hours... any help would be greatly appreciated!.
Also, as of now... it wont boot past the google logo. I can get it into fastboot by holding down the buttons, and I can get it into the stock recovery, but thats it. I don't even think adb is detecting the device. I have a feeling that may be a major roadblock to getting this thing fixed. Does anyone know how I can get the tablet to be detected by adb if i cant even get past the google logo screen at boot?
Update 1:
Still cant unbrick my device. any time i try to transfer or flash files to it... it stalls, and if i disconnect the device, i get this error:
FAILED (data transfer failure (too many links)).
Your Device will now boot into Android and detect ADB mode.
problem is, it doesnt reboot, and even if it did, it wouldnt be able to boot into android, since it wont go past the google logo when the device turns on. in fact, i cant even turn it off. only way to turn it off would be to wait for the battery to drain.
If this helps, here is what it says on the fastboot screen:
Device Information
Product Name: manta
Variant: wifi
H/W version : 8
Bootloader Version: MANTALJ12
Carrier Info: none
Serial Number: *********** (not going to publish that, lol)
LOCK STATE: Unlocked
Reboot Mode Flag: none.
anyone have any ideas at all how I can salvage this thing? Im kindof embarrassed honestly. Ive had 5 android devices prior to this one, and have rooted, flashed, and reflashed each of them countless times, and never, ever ran into this before. I could really use the help.
Quick note:
I just noticed that when i try to flash anything to the tablet, the following appears under the rest of the info i listed above.
FASTBOOT STATUS - DATA00713800 (this text is highlighted in light blue)
Update 2:
ok, so i tried to do the factory restore, and am running into the same wall as always. here is the text from the window, perhaps that may clue you into the problem:
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: put_google_factory_image_here\mantaray-jop40c-factory-0d641789.tg
z
Extracting mantaray-jop40c-factory-0d641789.tar
Everything is Ok
Size: 329369600
Compressed: 326396069
Now extracting flashable Images
7-Zip (A) 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
Processing archive: put_google_factory_image_here\mantaray-jop40c-factory-0d641789.ta
r
Extracting mantaray-jop40c
Extracting mantaray-jop40c\image-mantaray-jop40c.zip
Extracting mantaray-jop40c\flash-base.sh
Extracting mantaray-jop40c\bootloader-manta-mantalj12.img
Extracting mantaray-jop40c\flash-all.sh
Extracting mantaray-jop40c\flash-all.bat
Everything is Ok
Folders: 1
Files: 5
Size: 329358105
Compressed: 329369600
Factory Images extracted. Starting Flash Process.
Now Flashing Bootloader Image..
sending 'bootloader' (1280 KB)... OKAY [ 0.232s]
writing 'bootloader'... OKAY [ 0.113s]
finished. total time: 0.345s
rebooting into bootloader... OKAY [ 0.001s]
finished. total time: 0.001s
Now Flashing Factory Image: Boot, Cache, Recovery, System and Userdata..
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product... OKAY [ 0.001s]
checking version-bootloader... OKAY [ 0.002s]
sending 'boot' (4606 KB)...
Its just stuck on that last part, sending 'boot' (4606 KB)...
and under all the info on the fastboot page, the following appeared while this was happening:
FASTBOOT STATUS - DATA0047f800 (this line is highlighted in light blue)

*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)

cuguy said:
*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)
Click to expand...
Click to collapse
can you link it?

cuguy said:
*Bump* That's really unfortunate. I managed to fixed my soft brick after unlocking and flashing TWRP with a factory image. There was no highlighted blue text, everything went smooth. I hope your issue get fixed
P.S. I did not use the toolkit. If you can boot to your bootloader (fastboot), try running the shell/batch scripts included with the factory image? (This is just following Google's instruction on the factory image download page)
Click to expand...
Click to collapse
trying that....
so far so good... dont want to get my hopes up though... below is what ive got so far in the cmd screen:
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.125s]
finished. total time: 0.288s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4606 KB)...
OKAY [ 32.528s]
writing 'boot'...
OKAY [ 0.116s]
sending 'recovery' (5106 KB)...
OKAY [ 56.840s]
writing 'recovery'...
OKAY [ 0.119s]
sending 'system' (528847 KB)...

Its been about 30 minutes now... and its still stuck on "sending 'system' (528847 KB)..." in the cmd window.... not sure what that means... it did take about a minute for the recovery to get sent over, and its about 100x larger in size, so i guess i will leave it connected like this for the next hour or so... and hope that it is just going REALLY slowly. Got my fingers crossed...

Battery died while waiting.... this is the complete text of the CMD screen while i was waiting.. forgot that it doesnt charge while in fastboot. got it plugged into an outlet for faster charging while its off.... hopefully when its charged up, i can try again and ill continue to progress
sending 'bootloader' (1280 KB)...
OKAY [ 0.162s]
writing 'bootloader'...
OKAY [ 0.125s]
finished. total time: 0.288s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ12
Baseband Version.....: no modem
Serial Number........: R32CB01KDWW
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.002s]
sending 'boot' (4606 KB)...
OKAY [ 32.528s]
writing 'boot'...
OKAY [ 0.116s]
sending 'recovery' (5106 KB)...
OKAY [ 56.840s]
writing 'recovery'...
OKAY [ 0.119s]
sending 'system' (528847 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 3941.094s
Press any key to exit...

Did you try to run e2fsck on all partitions (boot, system, userdata) and check whether there are any errors?
You can run it via adb once you boot into TWRP or CWM recovery. Here is more info:
http://forum.xda-developers.com/showthread.php?p=34923662
Ps.
I also bricked my nexus 10 while transferring files on it in windows. Nothing so far helped me. e2fsck doesn't see any partitions
I believe this is something to-do with a corrupted flash memory. Your case looks about the same.

jodvova said:
Did you try to run e2fsck on all partitions (boot, system, userdata) and check whether there are any errors?
You can run it via adb once you boot into TWRP or CWM recovery. Here is more info:
http://forum.xda-developers.com/showthread.php?p=34923662
Ps.
I also bricked my nexus 10 while transferring files on it in windows. Nothing so far helped me. e2fsck doesn't see any partitions
I believe this is something to-do with a corrupted flash memory. Your case looks about the same.
Click to expand...
Click to collapse
I cant get it to load a custom recovery! any advice on how to get that going?

ltracte said:
I cant get it to load a custom recovery! any advice on how to get that going?
Click to expand...
Click to collapse
So, if you run "fastboot boot twrp-image.img" under your current bootloader it doesn't boot it?
Also, If I remember it correctly, you can also boot in to a existing recovery and then run shell commands via adb.

ltracte said:
I cant get it to load a custom recovery! any advice on how to get that going?
Click to expand...
Click to collapse
Dumb question, if using a desktop PC are you using the front or rear USB ports? I had a similar issue where it would just get stuck on the "sending system" message. Switched the USB from front port to back port on my linux box and it solved my problem.
Sent from my Nexus 10 using Tapatalk 2

jodvova said:
So, if you run "fastboot boot twrp-image.img" under your current bootloader it doesn't boot it?
Also, If I remember it correctly, you can also boot in to a existing recovery and then run shell commands via adb.
Click to expand...
Click to collapse
i got twrp to load that way! thanks... what now? i cant get the device to mount so i can put the zip file of a rom on there.

ltracte said:
i got twrp to load that way! thanks... what now? i cant get the device to mount so i can put the zip file of a rom on there.
Click to expand...
Click to collapse
What I meant was, you can now run e2fsck and check all partitions for consistency. Refer to a thread that I posted a few comments back. You can run e2fsck either via a terminal session in TWRP or via adb shell.

jodvova said:
What I meant was, you can now run e2fsck and check all partitions for consistency. Refer to a thread that I posted a few comments back. You can run e2fsck either via a terminal session in TWRP or via adb shell.
Click to expand...
Click to collapse
couldnt get the command to work via adb, so i tried it using terminal inside TWRP, and this what it spit back at me:
/dev/block/platform/dw_mmc.0/by-name/system: clean. 11/51296 files. 6651/204800 blocks
i have no idea what that means, nor what else to do....

Fixed it!!!!

ltracte said:
Fixed it!!!!
Click to expand...
Click to collapse
Glad you fixed your problem. Please post any relevant information that may help people in the same situation.
Mark.

mskip said:
Glad you fixed your problem. Please post any relevant information that may help people in the same situation.
Mark.
Click to expand...
Click to collapse
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!

Whew! So glad you finally had success & thanks for sharing. I'm reading up, research, etc. I received my N10 yesterday. I'm getting ready to unlock/root today.
Sent from my Nexus 7 using Tapatalk 2

ltracte said:
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!
Click to expand...
Click to collapse
Hmm, did you try the flash-all.bat file that comes with the factory image? It does those 3 commands, + erases all partitions automatically.

ltracte said:
well.. i loaded it into the bootloader, unzipped the factory image, and everything inside it into the platform-tools folder in my android sdk directory on my pc so i could use ADB
then i did the following via adb
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader
fastboot -w update image-mantaray-jop40c.zip.
the first time it got stuck pushing the system.img file, i let it run for almost an hour before giving up. then the battery on the tablet died. let it charge for about an hour, plugged it back in, reran the last command from above, and for some reason, the whole thing went through without a hitch. wish i could explain why it worked that time, but I cant. hope this helps someone else that encountered the issue.
thanks again to everyone that offered any input!
Click to expand...
Click to collapse
That's exactly what I did. Just followed the factory image flashing instruction on google's page(where you download the image file for N10). Did you figure out why it wassnt able to transfer the first time?

Bootlooping, ADB not detected, can't enable debugging

So, where do I start?
I bought this device (Nexus 2013 Wi-Fi) in late november and have not updated it since. I attempted to update it today (because I received a notification to do so) to 4.4.2 (I think).
It restarted after the update and I've been stuck in a bootloop at the "4 circles".
I have done the following:
- put the device into the boatloader
- installed the nexus root toolkit and attempted to flash stock + unroot the device to the images: 4.3 (JSS15Q), 4.3 (JSS15R), and (KOT49H)
- this was what my output looked like
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.006s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 08e8df8e
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.003s]
sending 'boot' (7018 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.027s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
​
- And no, I have not tried the force flash.
- I have tried all the drive options and maybe I'm not following the directions properly but that does not seem to work (and it may be the main problem for all I know).
- I'm also not sure if I thoroughly removed all google nexus-related drivers prior to running the nexus root toolkit, so there may be that.
- I've tried some brute-force methods inspired by things I've seen here, as in:
un-packing the factory image files into the platform tools part of the android sdk files and run the following commands in the cmd.exe: fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img​ - My guess is that the problem lies with the fact that I cannot put the device in debugging mode and I cannot have it recognized by adb.
I'm not sure where to go from here and I'm rather frustrated. Please let me know what solutions I should re-try (but perhaps more carefully?) and new ones that I should know of.
I appreciate all your help

rohanjoshi said:
So, where do I start?
I bought this device (Nexus 2013 Wi-Fi) in late november and have not updated it since. I attempted to update it today (because I received a notification to do so) to 4.4.2 (I think).
It restarted after the update and I've been stuck in a bootloop at the "4 circles".
I have done the following:
- put the device into the boatloader
- installed the nexus root toolkit and attempted to flash stock + unroot the device to the images: 4.3 (JSS15Q), 4.3 (JSS15R), and (KOT49H)
- this was what my output looked like
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.006s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 08e8df8e
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.003s]
sending 'boot' (7018 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.027s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
​
- And no, I have not tried the force flash.
- I have tried all the drive options and maybe I'm not following the directions properly but that does not seem to work (and it may be the main problem for all I know).
- I'm also not sure if I thoroughly removed all google nexus-related drivers prior to running the nexus root toolkit, so there may be that.
- I've tried some brute-force methods inspired by things I've seen here, as in:
un-packing the factory image files into the platform tools part of the android sdk files and run the following commands in the cmd.exe: fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img​ - My guess is that the problem lies with the fact that I cannot put the device in debugging mode and I cannot have it recognized by adb.
I'm not sure where to go from here and I'm rather frustrated. Please let me know what solutions I should re-try (but perhaps more carefully?) and new ones that I should know of.
I appreciate all your help
Click to expand...
Click to collapse
Hi, rohanjoshi...
You're actually on the wrong forum... this is the forum for the first generation Nexus 7 (2012). The forum for your second generation Nexus 7 (2013) is located here...
http://forum.xda-developers.com/nexus-7-2013
--------------------------------
However, looking through your output, it seems the failure to flash is due to the bootloader being locked...
rohanjoshi said:
...
sending 'bootloader' (3911 KB)...
FAILED (remote: Bootloader is locked.)
...
Click to expand...
Click to collapse
You need to unlock it with...
Code:
fastboot oem unlock
....or whatever the equivalent is in the toolkit you're using.
Good luck.
Rgrds,
Ged.

GedBlake said:
Hi, rohanjoshi...
You're actually on the wrong forum... this is the forum for the first generation Nexus 7 (2012). The forum for your second generation Nexus 7 (2013) is located here...
http://forum.xda-developers.com/nexus-7-2013
--------------------------------
However, looking through your output, it seems the failure to flash is due to the bootloader being locked...
You need to unlock it with...
Code:
fastboot oem unlock
....or whatever the equivalent is in the toolkit you're using.
Good luck.
Rgrds,
Ged.
Click to expand...
Click to collapse
woops, I'll get on that!

[Q] Definitely [Bricked] Maybe

Hello to everyone,
I'm stuck in a very bad situation with my ZTE open (codename Inari).
I've flashed the phone for upgrading to 1.4 version software, but something goes wrong...
In startup the phone stuck with the splash boot image (the logo with the FirefoxOS text)
Now the phone boot only in a fastboot way (with ROAMER2 codename), and whathever firmware I try to flash into phone give this error:
with fastboot windows version:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 0.922s
with fastboot linux or mac version:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 0.839s
in each way the phone reboot.
I've tried also the NandDL_firefox.exe software, but It seems to be in trouble with the ARMPRG file (that I don't really what it is, and the software come in chinese language)
So, if I press the VolUp+power the phone does nothing (still with the logo described up),
the VolDown+Power the phone does nothing.
Only with the VolUp+VolDown and Power button the phone going into Download Mode (the pc recognized the phone as "ZTE WCDMA Handset Diagnostic Port"...
Maybe this can be the last salvation, this mode is recognized by QPST suite software, but I don't know from where I can start to use this software...
Someone can help me?
Or someone want a bricked phone to hard testing?
Thanks

scari said:
Hello to everyone,
I'm stuck in a very bad situation with my ZTE open (codename Inari).
I've flashed the phone for upgrading to 1.4 version software, but something goes wrong...
In startup the phone stuck with the splash boot image (the logo with the FirefoxOS text)
Now the phone boot only in a fastboot way (with ROAMER2 codename), and whathever firmware I try to flash into phone give this error:
with fastboot windows version:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 0.922s
with fastboot linux or mac version:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 0.839s
in each way the phone reboot.
I've tried also the NandDL_firefox.exe software, but It seems to be in trouble with the ARMPRG file (that I don't really what it is, and the software come in chinese language)
So, if I press the VolUp+power the phone does nothing (still with the logo described up),
the VolDown+Power the phone does nothing.
Only with the VolUp+VolDown and Power button the phone going into Download Mode (the pc recognized the phone as "ZTE WCDMA Handset Diagnostic Port"...
Maybe this can be the last salvation, this mode is recognized by QPST suite software, but I don't know from where I can start to use this software...
Someone can help me?
Or someone want a bricked phone to hard testing?
Thanks
Click to expand...
Click to collapse
have you tried flashing the original firmware from the zte website? and then start all over? From what I remember, you can put the firmware directly on the sd card and flash from the recovery menu.

foxob said:
have you tried flashing the original firmware from the zte website? and then start all over? From what I remember, you can put the firmware directly on the sd card and flash from the recovery menu.
Click to expand...
Click to collapse
There is a little little little problem.
The recovery menu doesn't exist anymore...
I've (maybe bad) flashed the recovery partition, so it's now inaccessible...
Pushing the VOLUP+Power button the devices doesn't start in recovery mode...
Only Download Mode is available, but I don't know what it is really
Thank you

scari said:
There is a little little little problem.
The recovery menu doesn't exist anymore...
I've (maybe bad) flashed the recovery partition, so it's now inaccessible...
Pushing the VOLUP+Power button the devices doesn't start in recovery mode...
Only Download Mode is available, but I don't know what it is really
Thank you
Click to expand...
Click to collapse
so this doesn't work? too bad. that has helped me save my zte open a few times.

foxob said:
so this doesn't work? too bad. that has helped me save my zte open a few times.
Click to expand...
Click to collapse
no, that method doesn't work definitely...
:crying:

are you able to get into fastboot?

hecatae said:
are you able to get into fastboot?
Click to expand...
Click to collapse
the phone stuck in fastboot mode when the power button is pressed.
The only other method to start up the phone is download mode (VolUP+VolDown and power button).

scari said:
the phone stuck in fastboot mode when the power button is pressed.
The only other method to start up the phone is download mode (VolUP+VolDown and power button).
Click to expand...
Click to collapse
cant you flash recovery using ADB ????? i think you might, just find a recovery that does work on your mobile and flash it using adb if it works you can install or flash atleast something to work with.

Arrowblue said:
cant you flash recovery using ADB ????? i think you might, just find a recovery that does work on your mobile and flash it using adb if it works you can install or flash atleast something to work with.
Click to expand...
Click to collapse
when I flash the phone with windows this is the result:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 0.922s
and when I try to flash with ADB under Mac Os this is the result:
Code:
sending 'recovery' (5712 KB)...
OKAY [ 0.523s]
writing 'recovery'...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 0.839s
and I try to flash the original boot image and the modified one,
but without success...

[HELP] Bricked phone while trying to install custom rom

I was trying to install the AOSiP rom and when I I was doing the twrp installation:
fastboot flash boot twrp-mata_11.img
the error pops out:
target reported max download size of 536870912 bytes
sending 'boot_a' (45048 KB)...
OKAY [ 1.196s]
writing 'boot_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.856s
I don't see same errors over the XDA forum. can someone help me?
p.s. screen now is showing fastboot mode
device state - unlocked

Did you unlock critical?
Sent from my ONEPLUS 3T using Tapatalk

seabro01 said:
Did you unlock critical?
Sent from my ONEPLUS 3T using Tapatalk
Click to expand...
Click to collapse
uhh no I did not see that in the tutorial.
I tried: ./fastboot flashing unlock_critical
and looks like it freezes after that command...

ytlei said:
I was trying to install the AOSiP rom and when I I was doing the twrp installation:
fastboot flash boot twrp-mata_11.img
the error pops out:
target reported max download size of 536870912 bytes
sending 'boot_a' (45048 KB)...
OKAY [ 1.196s]
writing 'boot_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.856s
I don't see same errors over the XDA forum. can someone help me?
p.s. screen now is showing fastboot mode
device state - unlocked
Click to expand...
Click to collapse
are you rooted?
have you tried downloading the file again?
and if you can still go to bootloader your phone is not bricked, just download stock boot from essential and flash it

yenkoPR said:
are you rooted?
have you tried downloading the file again?
and if you can still go to bootloader your phone is not bricked, just download stock boot from essential and flash it
Click to expand...
Click to collapse
no not rooted
now im trying to flash back to stock, but when I run flash-all.sh error keeps popping up:
remote: Error flashing partition.
FAILED (remote: Error flashing partition.)
finished. total time: 2.025s
target reported max download size of 536870912 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.735s]
writing 'boot_b'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.782s
target reported max download size of 536870912 bytes
sending 'cmnlib_a' (512 KB)...
OKAY [ 0.103s]
writing 'cmnlib_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 0.169s
target reported max download size of 536870912 bytes
sending 'cmnlib_b' (512 KB)...
OKAY [ 0.101s]
writing 'cmnlib_b'...
FAILED (remote: Error flashing partition.)
finished. total time: 0.188s
...

Dang now its totally bricked after the flashing failure... cannot boot up. what should I do? send it back to Essential?

What do you mean by can't boot up? Do you see boot animation and have you tried to go back to fast boot or recovery?
Sent from my ONEPLUS 3T using Tapatalk

Try different USB ports and cables. When 8.1 came out I had to swap my cable and change the port I was using on my desktop, for some reason the cable I had been using and the port I had been using since I got the phone was no longer adequate. There were a number of other people having the same issue. Some commands would look to complete properly, but following up with the same command (something un-damaging like fastboot --set-active=a | fastboot --set-active=b) would either error again or show that the 'completed' command hadn't actually done anything. I switched cables/ports around (ended up with an Antek USB-A to USB-C cable in a USB3.1 port) and everything worked properly.
If you're trying to flash a stock build image from Essential, you will probably need critical unlocked because those images do contain a bootloader that gets flashed, and that is secured behind critical.

ytlei said:
Dang now its totally bricked after the flashing failure... cannot boot up. what should I do? send it back to Essential?
Click to expand...
Click to collapse
What cable are you using?
Do not use the cable that came with the phone!!!!!

We are screwed mate, I am on the same boat with you. Essential took no responsibility and offered a 200$ replacement device. The phone doesn't power on anymore and no light indicators are working, so hard bricked.

I had a Asoip screw up(did not disable password) and was only able to get fastboot. Had to see what slot was active and flashed to that slot that was active boot.img,twrp,Asoip and was back up and running. My bootloader was unlocked. I read through all the posts and peoples screw ups and was able to get it up and running again in a day. I never posted as I wanted to learn it on my own. Good luck.........

ytlei said:
I was trying to install the AOSiP rom and when I I was doing the twrp installation:
fastboot flash boot twrp-mata_11.img
the error pops out:
target reported max download size of 536870912 bytes
sending 'boot_a' (45048 KB)...
OKAY [ 1.196s]
writing 'boot_a'...
FAILED (remote: Error flashing partition.)
finished. total time: 1.856s
I don't see same errors over the XDA forum. can someone help me?
p.s. screen now is showing fastboot mode
device state - unlocked
Click to expand...
Click to collapse
What cable did you use while connecting to your computer?
And what is the status now? Are you able to turn it on at all by volume and power key combination?

same here. The phone doesn't power on anymore. btw I used the usb-c TDB cable came with my MacBook pro.
I sent email to essential and they say they can't help me since I tried to flash custom rom...

ytlei said:
same here. The phone doesn't power on anymore. btw I used the usb-c TDB cable came with my MacBook pro.
I sent email to essential and they say they can't help me since I tried to flash custom rom...
Click to expand...
Click to collapse
and pressing the volume down key + power key at the same time doesn't work?.. what happens when you plug your phone into the charger? does it vibrate?

ive had fastboot command problems previously myself with this device and found that the usb port can play a pretty large factor. Swapping usb ports and reattempting to run the commands (as others recommended may be useful) make sure you are using latest version of adb/fastboot and have up to date drivers installed for the phone.
Look at the rooting tutorial there is information in there about swapping active slots (the essential has both a and b paritions) if you set the other slot as the active slot you may be able to regain some communication within fastboot (i would suggest you verify with fastboot devices prior to attempting to flash to partitions).
Additionally you should be able to still recover back to stock without custom recovery using the default recovery partition. I would think that if you are able to access the bootloader you should be able to access the default essential recovery partition. If you can access the standard recovery you should be able to factory reset the phone and sideload a new rom (id suggest the default factory image from essential until you can get back to square one)

I'm in the same boat. Tried to flash twrp after upgrading to 8.1 and got the same Error flashing partition, and now I'm stuck on the bootloader.
I've found that if I lock/unlock and lock/unlock critical it will let me flash the stock 8.1 boot and every other partition except for system and vendor, but gives a flash write error for those. I'm still unable to get past the bootloader.
Essential basically said I'm SOL. $200 out of warranty replacement assuming I live in the US, which I don't.

Mine was doing this too, but it was only a few days old so I returned it. I'm pretty sure it's defective flash memory.

My phone was doing this exact thing. Botched factory installs rendered my phone hardbricked.
Tried a thousand+ things to get it to turn on to no avail. LUCKILY I bought it second hand and have no warranty D:
I want to cry

Did I brick my phone by not renaming the twrp image to recovery.img?

I was following the steps from miui.blog/redmi-7/flash-twrp-redmi-7a-pine and I got to the "fastboot flash recovery" step, but I didn't rename the file to "recovery.img" because I didn't believe the step could be important. (It's an image, what does the filename matter?) Flashing finished successfully:
Code:
$ fastboot flash recovery twrp-3.3.1-0-pine.img
target reported max download size of 535822336 bytes
erasing 'recovery'...
OKAY [ 0.009s]
sending 'recovery' (28588 KB)...
OKAY [ 0.914s]
writing 'recovery'...
OKAY [ 0.392s]
finished. total time: 1.315s
but afterwards my phone would no longer boot or enter fastboot no matter what keys I held.
Did I brick it? Is there any way to recover?
edit: Should I try to go for EDL mode?
edit: Got the back cover off, but I literally don't have a sufficiently small screwdriver to remove the inner covers. Tomorrow!
edit: Maybe it was just the wrong version of TWRP. Will see tomorrow.
edit: Update: I have it in EDL mode. Not sure what the next step is under Linux.
edit: Can't figure out how to find the right programmer file for it.
edit: Now it gets up to "only nop and sig tag can be recevied before authentication." I may be stuck here. :/
edit: Currently waiting for xiaomitool.net to come back online.

>It's an image, what does the filename matter?
It doesn't. fastboot boot %anyname%.img work as well as "boot recovery.img". With flash it's work same. For further - use boot check recovery before flashing.
>Now it gets up to "only nop and sig tag can be recevied before authentication."
For flash via edl you need xiaomi service authentication or firehose which doesn't need authentication for flashing.