Database Users

N7 (3G, 2012) bricked? Boot mode, no recovery. N Toolkit doesn't flash.

Hello there.
I am writing because I need your help on unbricking my Nexus 7 3G (2012). Yesterday night I was trying to upgrade it from 5.1.0 to 5.1.1 (from the OTA) and I couldn't because I had an error produced by Stickmount. It changed a file on system/bin which I tried to push manually (following some thread's intructions on XDA) and it didn't work, showing error Status 7 (unexpected content on file debuggerd).
Because of that, I decided to flash the 5.1.1 system image using Nexus Toolkit. I set it up so it'd download and install it automatically (using the "Flash stock + Unroot" option). Everything went okay and started the flashing process until the command prop window force closed mid flash, thing that never happened to me before (as I had tried many times flashing from zero my N7 before).
I tried to start the Toolkit again and the command prop window says it flashes bootloader and radio img's successfully, but then a line of code appears and the cmd window force closes again (it says "No se esperaba ( en este momento" or roughly translated as "The ( was not expected at this moment" into English) and my N7 turns off.
Next, I try to turn it on and it shows the Google logo and a green arrow saying "start". I press it and the N7 reboots to the same screen, saying "booting failed" at the top of the screen. If I choose recovery, the same thing happens.
{
"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 just can make it to boot to bootloader mode but I cannot flash the firmw (even when this mode must be selected in order to the Toolkit to start flashing). It shows the same line of unexpected code as above.
I tried pushing the files manually using ADB and I cannot may it work either.
What can I do to solve this? I've read that as long as you can get to bootloader mode you can unbrick a device.
I hope you could help me out. Thanks in advance.

Anyone?

Im not a expert, but so if you in bootloader, fastboot (android sdk) dont see your nexus? For check type - 'fastboot devices', if that return something, you can use it to flash recovery/or whole system.
Im linux user, so I dont know how to check how visible is device in windows - and whether drivers are working properly.
I'm sorry if I say the obvious, I just would like to help as much I can. Good luck!

wombat3 said:
Im not a expert, but so if you in bootloader, fastboot (android sdk) dont see your nexus? For check type - 'fastboot devices', if that return something, you can use it to flash recovery/or whole system.
Im linux user, so I dont know how to check how visible is device in windows - and whether drivers are working properly.
I'm sorry if I say the obvious, I just would like to help as much I can. Good luck!
Click to expand...
Click to collapse
Thanks wombat. Actually, the N7 is listed under adb devices. It starts the flashing process but ends automatically without finishing the installation.

Dead nexus 4?

Hi guys, this is my first time posting problems like these as I've never encountered anything I can't fix by myself or with help from fine developers and the community here, but now I'm desperate so I wanted to give it a shot.
Anyways here's what happened. My battery died, along with my USB port (the latter of physical damage - it's not burned just the port got damaged from usage I guess). Anyways, I got original replacement parts, put them in all good. And now when I plug in the charge cable, the LED briefly flashes green and after that nothing happens. However, I found out that if I hold power and volume down and plug in the USB cable then, bootloader turns on. It's interesting how the bootloader was marked as locked even though I unlocked it ages ago. Anyways, when I try to start it normally it shows the Google logo, and after a second or so, it shuts down completely (after the screen goes off, the green LED flashes again). I tried doing rebooting bootloader and recovery, same thing occurs. I tried using factory images and here's the weird/interesting part. When I manually flash the images from the latest 5.1.1 set, everything passes except when I tried doing fastboot flash data userdata.img . It downloads as it should, but it stops after the write part (it says that it can't flash a filesystem with type ' ' - Same goes for fastboot format and fastboot wipe and fastboot erase). However, when I use flash-all batch, it passes as it should (write phase included - or that's at least what it says), but still, the phone won't turn on. I can't do fastboot boot recovery.img as it gives the same result. I should note that I did try fastboot oem unlock, and it pops up the confirmation screen and all, and when I press yes, it works as it should, unlocks the bootloader (I know since when I booted into bootloader again, it showed that it's unlocked, and on the Google logo it shows the little symbol on the bottom), but shuts down on the Google logo again. Flashing any other custom made image (for example this http://dmitry.gr/index.php?r=06.+Thoughts&proj=02.%20Android%20M%20on%20Nexus4 Android M image) gives the same outcome. I really ran out of ideas and could appreciate any help or at least ideas on what could be broken on it so I can let it rest in peace.
Also might be noteworthy that my Ubuntu didn't recognize anything when I attached it in fastboot. As in nothing happened.
Here are screenshots of the fastboot output if someone's interested (ignore the red marking on the screenshot, it was for a friend ):
{
"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 think you flash the recovery the wrong way.
To flash via fastboot, this is the command:
fastboot flash recovery twrp-2.8.x.x-xxx.img
Source: http://androiding.how/how-to-install-twrp-recovery-via-fastboot/
You tried to flash a recovery in the kernel location.
To flash a kernel via fastboot:
fastboot flash boot boot_name_img

dcop7 said:
I think you flash the recovery the wrong way.
To flash via fastboot, this is the command:
fastboot flash recovery twrp-2.8.x.x-xxx.img
Source: http://androiding.how/how-to-install-twrp-recovery-via-fastboot/
You tried to flash a recovery in the kernel location.
To flash a kernel via fastboot:
fastboot flash boot boot_name_img
Click to expand...
Click to collapse
Yeah sorry those are typos, I came from work and I was tired as hell while I was posting this. If you are referring to the first screenshot, I wasn't flashing the recovery, I was simply trying to boot it off my PC without actually flashing it. Anyways, the recovery flash that I did afterwards was ok, as well as any other except for /data. I think that's the culprit, but it still wouldn't explain why the phone shuts down as soon as it tries to (at least to my understanding) load the kernel. Boot.img is ok, so that can't be the problem.

Hi,
Have you had any luck? I am having the exact same problem with my new battery and charging port replacement which are all genuine parts.
Thanks

Samsung Galaxy A3 (SM-A300FU) file recovery while phone is locked and broken screen

Hello everyone,
I have a problem, i got a Samsung Galaxy A3 (SM-A300FU) wich is fallen on the ground this resulted in a dead lcd and touch screen, the device is locked with a pincode, i allready got a new phone, but i would like to recover the files i got on that phone, is there anny way i could try?
- USB-debugging is DISABLED
- Tried a Delock connection kit 5 in 1 with HDMI (The phone plings as soon as i connect the HDMI to to connection kit, but it doesnt give signal)
- Samsung Kies software reconises the phone, but it cant access it because its locked.
If there is anny way that i could recover the data partically its also fine.
Regards,
Spinner1991

Bumb - Need help :crying:

1. Flash TWRP through download mode. - power down with Power + Volume Down (emulates battery removal), wait a few second, boot in to Download Mode with Power + Home + Volume Down. Odin should show a COMx (x for number) sign and a green color on the slot. MAKE SURE YOU UNTICK AUTO-REBOOT, or else the stock recovery will reflash itself.
2. Access Phone via ADB recovery - After flashing the TWRP, power down again with Power + Volume Down and boot in to Recovery Mode with Power + Home + Volume Up.
You should now be able to "adb pull" files from the phone to the computer.
Minimal ADB & Fastboot
TWRP for A300FU (Odin included)

Please Debrick img For A300F , ?

PlutoDelic said:
1. Flash TWRP through download mode. - power down with Power + Volume Down (emulates battery removal), wait a few second, boot in to Download Mode with Power + Home + Volume Down. Odin should show a COMx (x for number) sign and a green color on the slot. MAKE SURE YOU UNTICK AUTO-REBOOT, or else the stock recovery will reflash itself.
2. Access Phone via ADB recovery - After flashing the TWRP, power down again with Power + Volume Down and boot in to Recovery Mode with Power + Home + Volume Up.
You should now be able to "adb pull" files from the phone to the computer.
Minimal ADB & Fastboot
TWRP for A300FU (Odin included)
Click to expand...
Click to collapse
Thanks, this worked after a few trys!
Regards,
Spinner1991

hi all,
I have done all the steps but the TWRP gives me a message of "unmodified sysetm partition", I can not see well from the broken screen but it seems to me 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"
}
obviously, due to the broken screen, I can not swipe, my pc recognizes and installs the smartphone drivers but if I run the command "adb devices" I do not see any connected any device.
Is it the fault of the swype I can not do? if there is an alternative to the swype to get over this screen?
thanks.
---------- Post added at 06:30 PM ---------- Previous post was at 05:49 PM ----------
Sorry the problem was the pc and a old adb installation, change pc solved the issue

Bricked my A2017G

Hello guys,
I tried to update my phone to Nougat and I guess I totally failed.
First I just tried to flash this rom: https://forum.xda-developers.com/axon-7/development/rom-purefusionos-official-t3670580 and it did not work. So I thought I might have to update the firmware first and installed the A2017UV1.1.0B32 NOUGAT Update from this thread: https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484. I found out I had to flash (with TWRP) the firmware's G version so I took the A2017G_N_Modem.zip from this https://androidfilehost.com/?w=files&flid=148464.
Now I only get the "your device software can't be checked for corruption. Please lock the bootloader".
Can somehow help me and tell me if and how I can get a rom working again?
Thanks in advance.

Check forum. There are topics to unbrick your device.

Yes, I read the forums. My Problem is that I cannot enter the EDL mode for example. When I git Power + Vol Up + Vol down nothing happen except a shot red LED.
EDIT: I cannot get into fastboot aswell.. Always that screen with lock your bootloader. Pretty much the only mode I can enter is recovery with TWRP.

multimill said:
Yes, I read the forums. My Problem is that I cannot enter the EDL mode for example. When I git Power + Vol Up + Vol down nothing happen except a shot red LED.
EDIT: I cannot get into fastboot aswell.. Always that screen with lock your bootloader. Pretty much the only mode I can enter is recovery with TWRP.
Click to expand...
Click to collapse
When led blinked you are on EDL mode. Screen is black on edl mode.

Yeah I got that an now i completely **** up -.-
I made it to go back to stock. I saw yeah got that B10 version now so I tried to flash PureFusionOS and Beans GApps. Now the screen is just black when I start the phone and my computer (and one other I tested) cannot flash the the edl version via Miflash because the phone is not recognized.
When I try to enter EDL the led is not blinking anymore. Its just showing red.

multimill said:
Yeah I got that an now i completely **** up -.-
I made it to go back to stock. I saw yeah got that B10 version now so I tried to flash PureFusionOS and Beans GApps. Now the screen is just black when I start the phone and my computer (and one other I tested) cannot flash the the edl version via Miflash because the phone is not recognized.
When I try to enter EDL the led is not blinking anymore. Its just showing red.
Click to expand...
Click to collapse
Do you see your device on Device Management? If yes, it is on edl mode. go on other steps
BTW, use this guide.

WesTD said:
Do you see your device on Device Management? If yes, it is on edl mode. go on other steps
BTW, use this guide.
Click to expand...
Click to collapse
Where should I see in the device manager?
EDIT: I do hear a sound when connecting. But I dont know where to find it in the device manager. In which category.
EDIT2: Well I see one device here, but neither the Axontool nor Miflash regonize it.
{
"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"
}

multimill said:
Where should I see in the device manager?
EDIT: I do hear a sound when connecting. But I dont know where to find it in the device manager. In which category.
EDIT2: Well I see one device here, but neither the Axontool nor Miflash regonize it.
Click to expand...
Click to collapse
Good luck. Your device on DFU Mode. There another guide about it.

multimill said:
Where should I see in the device manager?
EDIT: I do hear a sound when connecting. But I dont know where to find it in the device manager. In which category.
EDIT2: Well I see one device here, but neither the Axontool nor Miflash regonize it.
Click to expand...
Click to collapse
4th category brick repair manual, google it

Nokia X6 Stuck in Download Mode

Hello, hope you can help.
I have a Nokia X6 (TA 1099) that somehow got stuck in Download Mode (see attached pictures)
I have tried the Vol Down plus Power to exit Download Mode, also tried various other combinations, but no luck.
When I plug the phone into USB it does show up as Fastboot Device and I can use the fastboot cmd with reboot to make it restart, but it stays in Download Mode.
I tried installing the OST LA tool and it made the phone display some more details on screen (see attached picture), however it wouldn't get as far as to attempt loading a new image. (says software tool needs update)
Thanks,
Jake
{
"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"
}
imgur dot com/a/xDSs8BJ
imgur dot com/eM5a8ib

Try this fix

paul89rulez said:
Try this fix
Click to expand...
Click to collapse
Very nice guide, thanks.
Unfortunately I get an error message saying: FAILED (remote: 'Flashing is not allowed in Lock State')
Then I tried the fastboot flashing unlock and unlock_critical but that just resulted in error message: FAILED (remote: 'Flashing Unlock is not allowed')
However after trying a fastboot --set-active=b and rebooting it made the phone come back from the Download Mode brick telling me something is corrupted and asking to restore to factory. I chose to restore to factory and it appears the phone is now unbricked and I just need to install everything again.
Thanks for your helpful suggestions.
Jake

JakeJ42 said:
However after trying a fastboot --set-active=b
Jake
Click to expand...
Click to collapse
You mean --set-active=_b?
You have bt unlocked?

paul89rulez said:
You mean --set-active=_b?
You have bt unlocked?
Click to expand...
Click to collapse
Nah, it's my wife's phone, I'm not sure how she managed to get it stuck in Download Mode, but I suspect maybe the case she was using caused the buttons to get stuck or something.
It was --set-active=b I used.

JakeJ42 said:
Nah, it's my wife's phone, I'm not sure how she managed to get it stuck in Download Mode, but I suspect maybe the case she was using caused the buttons to get stuck or something.
It was --set-active=b I used.
Click to expand...
Click to collapse
Sorry if I insist, your x6 is converted to global rom or it have Chinese stock?

Thanks for this
JakeJ42 said:
Very nice guide, thanks.
Unfortunately I get an error message saying: FAILED (remote: 'Flashing is not allowed in Lock State')
Then I tried the fastboot flashing unlock and unlock_critical but that just resulted in error message: FAILED (remote: 'Flashing Unlock is not allowed')
However after trying a fastboot --set-active=b and rebooting it made the phone come back from the Download Mode brick telling me something is corrupted and asking to restore to factory. I chose to restore to factory and it appears the phone is now unbricked and I just need to install everything again.
Thanks for your helpful suggestions.
Jake
Click to expand...
Click to collapse
I had the same issue with my 6.1 plus (TA 1116) when it suddenly showed me the screen asking for a factory wipe & that my data was corrupt. The phone entered download mode and I let the battery discharge overnight. Today after following the steps Jake took, the phone got out of download mode and I did a factory reset, the phone is working ok now.
Thanks @ Jake!

I had the same issue with my 6.1 plus (TA 1116) when it suddenly showed me the screen asking for a factory wipe & that my data was corrupt. The phone entered download mode and I let the battery discharge overnight. Today after following the steps Jake took, the phone got out of download mode and I did a factory reset, the phone is working ok now.