Develop Bugs

[Q] Bricked Galaxy Nexus

So it all started out rather stupidly. I was attempting to flash a new ROM to my phone and I was deleting everything and accidentally deleted the OS by accident (mis-touched in recovery mode). I panicked and I attempted to push a file through adb but it was halting between 4MB - 8MB on a 200MB file. I knew this wasn't right. I ran cmd in administrator mode and tried again and got the same results.
I then moved to ODIN to attempt to flash the ROM. I ran ODIN in administrative mode. Bootloader was unlocked. I attempted to flash the new ROM but it stopped at about 1/8th of the progress (as shown in the download mode). This led to my phone having communication issues with my PC (displayed the phone with a hazard sign on the cord to the PC). I assumed it was bricked after googling around.
I then tried to use OMAPFlash as suggested by other people with the same issue. I did this, followed instructions perfectly, installed certificates. It got to the point where it was attempting to download a file. After 2 hours of waiting, I stopped it stupidly because it was making no progress.
Now my phone is completely black. I have no OS and I am not even sure if I have any files on it. Screen is black, phone not responding to button pushes and it isn't being recognised by my PC. I have tried unplugging it, removing battery and then plugging it in and inserting the battery again and that has failed.
I don't know what else to do. OMAP isn't picking up the phone anymore even though I have followed the instructions perfectly again. The one sign that my phone is still alive is the beeping noise from windows as I insert it meaning something must be happening. This however is soon followed by "Your device is unrecognised".
Can anyone help me on the situation as the phone is in perfect condition (physically) and I can't really afford a new decent phone at the moment.
Here is all the information you may need:
[Before incident]:
ROM: CM11
Rooted: Yes
Bootloader Unlocked: Yes
Ask for anything else.
[Attempted to change to]
ROM: XenonHD
Ask for anything else.

first off, why odin?
its a nexus you can flash back to stock from fastboot. I would suggest you download the factory images for the phone from here:
https://dl.google.com/dl/android/aosp/takju-jwr66y-factory-5104ab1d.tgz
then extract the images into a folder - remove the battery from the phone, put it back in the phone, power up while holding down vol + and vol - to get into fastboot
hopefully you have android sdk installed and fastboot working. use the flash-all script to flash every partition of the phone back to 4.3 stock.
good luck.

Well first thing, did you select the right zip file for your Gnex when flashing XenonHD. Bcz in my case few days ago i stupidly selected the wrong zip file (ROM for Nexus 5) to flash, but luckily i was saved by the CWM via "Status 7 Error".
But your case is more complicated i would suggest you to use Gnex toolkit with Google Factory Images, i hope that it will come for your rescue . Also try this method http://www.androidrootz.com/2012/08/how-to-restore-galaxy-nexus-i9250-to.html maybe it will do some miracle for you. Best of luck.

Progress
So after sleeping on it and spending some time deeply reflecting on the derp that I had made, I successfully managed to use omap to restore my device to the Phone-Exclamation mark sign as posted by another XDA user who ended up sending his phone back. If you search galaxy nexus brick in google images, you will see what I am talking about (can't post image).
I guess the best way to explain it is: [] -- /_\ -- [ ]
Basically it is a phone connected to a yellow exclamation mark sign and then that is connected to a computer.
Is there a way to force my phone into download mode from here. I can't seem to do anything. Some good news is that ODIN is now picking up my device. It is however crashing whenever I attempt to flash the stock ROM (either "odin3 communicator has stopped working" or "odin3 downloader has stopped working").
Any help fixing this?

[Q] Gnex Brick Mount Fastbood Write Fail help :'(

Hi everybody,
ok I will try to make this short
I have an experienced user level ROM, recovery, boot, ..
My phone is BRICKED! Is it?
AT THE MOMENT:
- I get into fastboot mode
- I get into odin downloading mode
- I can't start in recovery mode
- I can't start bootloader mode
- I have a connection with a laptop (win XP, as win8.1 didnt work for me)
- The computer can communicate with the phone in fastboot mode
- The computer cant communicate with the phone in Odin mode (at the moment Odin PC SoftWare doesn't recognize the phone)
- I am sure the drivers are installed correctly now. Thanks to the guide with fully stripped drivers.
- Using different, multiple different, no thousand different methods I tried flashing the stock OS (Yakju 4.3)
- I like SkipSoft Android ToolKit (Although I used fastboot and adb commands, I find the toolkit to do the same thing..)
- I always get an Error, when the process of flashing starts.
> PC says : Error
> Phone (in fastboot mode) says: FAILWrite Fail
INTERESTING:
- While I still was able to get into Recovery, the phone couldnt mount the sdcard (=> the internal drive)
- Some of the methods I use make the phone CRASH
> means the screen stops at its position and slowly turns completely purple
- The phone power button doesnt start the phone, to get the phone doing something at all I have to trick it:
..> I plug it into the wall charger
..> I take the battery out
..> I put the battery back in
..> I wait
..> I can get into 3 routines:
^Normal starting routine (of course stuck at google start up, since no Rom is installed)
^fastboot mode (VOL + & - & Power)
^odin mode (VOL - & Power)
..> Then I can just plug the USB cable into the PC
- 2 days ago I had (every single version) of Odin PC Software recognizing the phone (phone was in Odin mode), but it also failed after trying the recommended and unrecommended settings. Ended with an error message.
HOW:
I left my phone overnight in the car (Temp: -2 deg C), while Im sure spotify and maybe other consuming apps were playing.
Next day, my phone battery was empty and I couldnt start my normal ROM. (I had Slim Rom installed)
It was stuck at the "Google" start up display.
First intentions showed that it might be more than just the Software :/
Many days and so many hours of work, research and reading in forums, I decided to take a shot and ask here.
I appreciate everything xda-members have done for me already. Though I never needed to register for my earlier questions.
Phone data:
Product Name - tuna
Variant - maguro 16gb
HW version - 9
Bootloader Version - primemd04
baseband version -
carrier info - none
serial number - -a3c208 ***
signing - production
lock state- unlocked

BUMP!!! I have absolutely the same problem!! I can access everything, i enter the recovery trying to WIPE every single thing data,system,cache,storage etc.. but it seems it doesnt work. The information stays. I tried to "softbrick unroot & stock" with a nexus kit, everything seems ok, but after it finishes installing, it boots up on GOOGLE and after 10-15 min it starts to BOOT MY OLD CUSTOM ROM THAT I HAD BEFORE, after another 15-20 min it finally boots up and the system is EXTREMELY choppy and unresponsive and after a few minutes it restarts itself. I tried ODIN and I faced the same problem, it goes well to ~45% and then it freezes, and after a short delay odin gives FAILED. I tried several more things that i found on the internet and xda but nothing helps. Probably a corrupted partition or something. THE DAMN STORAGE DOESNT WANT TO DELETE ITSELF FFS!! PLEASE IF YOU KNOW ANY FIX/ALREADY FIXED YOURS PLEASE HELP!!! I need my phone!

can you give us more information about the error message?
valkata1212 said:
Click to expand...
Click to collapse
your issue sounds like this one, can you confirm?

Soulaysahmi said:
can you give us more information about the error message?
your issue sounds like this one, can you confirm?
Click to expand...
Click to collapse
Similar, only difference is with fastboot i can successfully flash system.img but nothing happens. With odin it fails at around 45% and then freezes. Only difference is that i cannot boot to old stock and i dont have this pulpish problem. I simply reboot on my old custom ROM configuration with all my last known icons widgets.. but the phone is choppy and unresponsive as hell.

I only get an error without any further message after flashing any of the images...
Any idea anyone? Isn't it some hardware issue?

Noo man i dont think its hardware problem, for me it all happened when my phone suddenly restarted itself and after that it bootloops forever and i have those problems

Anyone?

does erase work?

yes

can you get into recovery?

oxxomexico said:
AT THE MOMENT:
- I get into fastboot mode
- I get into odin downloading mode
- I can't start in recovery mode
- I can't start bootloader mode
- I have a connection with a laptop (win XP, as win8.1 didnt work for me)
- The computer can communicate with the phone in fastboot mode
- The computer cant communicate with the phone in Odin mode (at the moment Odin PC SoftWare doesn't recognize the phone)
- I am sure the drivers are installed correctly now. Thanks to the guide with fully stripped drivers.
Click to expand...
Click to collapse
ka

how do you know that erase works, I mean that what you erased has really been erased?

One of the erase command in the toolkit was succesful, I guess. But I will recheck every error or successful message later tonight.

still NOT working
2 months have passed and I was too busy with other things.
now back to it. the problem hasnt changed.
i try fastboot flash command:
[fastboot flash bootloader x.img]
- in Computer Terminal: 'FAILED(remote:Write Fail) '
- on phone: ' FASTBOOT STATUS - FAILWriteFail '
any idea, please?

[HELP] - Soft Bricked G3 D852 (Rogers) - No Download Mode. Stuck at FW Update Screen

Hello all,
I've done a lot of googling and searching on these forums and I'm having no luck. Hopefully by asking I can get some headway.
I was attempting to restore to stock rom. At 17% of the process using LGFlashTool 1.8.6 the tool gave me an error 'Unable to Communicate with phone' after about 10 minutes of no progress. I exited the LGFlashTool program and ran it again and now it fails saying 'Cant' change to download mode". If I turn the phone off and then press Vol+ and plug in my cable it just goes to the Firmware Update screen. My phone *IS* detected properly in the device manager as LGE Andriod MTP Device and under ports as LGE Mobile USB Serial Port (COM41). If I go into recovery (Vol- and power) it asks if I want to do the restore - but it doesn't actually do anything once I say yes twice. Just sits at the firmware update screen at 0%.
I looked at this post (http://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091) but it appears to be either for a different phone or different problem (showing in device manager as a bulk device - mine is not doing that). Frankly I don't want to make things worse (if that's possible)
Does anyone have a way that I can restore the download mode for this D852 phone? I'm hoping if I can get download mode to work again I can reflash the stock rom. I don't care about the data on the phone at this point.
I'm willing to send some $$$ via paypal to whomever can get me back up and running! Thanks

Valgore said:
Hello all,
I've done a lot of googling and searching on these forums and I'm having no luck. Hopefully by asking I can get some headway.
I was attempting to restore to stock rom. At 17% of the process using LGFlashTool 1.8.6 the tool gave me an error 'Unable to Communicate with phone' after about 10 minutes of no progress. I exited the LGFlashTool program and ran it again and now it fails saying 'Cant' change to download mode". If I turn the phone off and then press Vol+ and plug in my cable it just goes to the Firmware Update screen. My phone *IS* detected properly in the device manager as LGE Andriod MTP Device and under ports as LGE Mobile USB Serial Port (COM41). If I go into recovery (Vol- and power) it asks if I want to do the restore - but it doesn't actually do anything once I say yes twice. Just sits at the firmware update screen at 0%.
I looked at this post (http://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091) but it appears to be either for a different phone or different problem (showing in device manager as a bulk device - mine is not doing that). Frankly I don't want to make things worse (if that's possible)
Does anyone have a way that I can restore the download mode for this D852 phone? I'm hoping if I can get download mode to work again I can reflash the stock rom. I don't care about the data on the phone at this point.
I'm willing to send some $$$ via paypal to whomever can get me back up and running! Thanks
Click to expand...
Click to collapse
What happens when u just power up the phone ?

Thanks for the reply.
If I shut the phone down (by pulling battery) then plug it back in and just power it on, I get the LG logo then it goes to the firmware update screen with 'USER B84" in the box below the progress bar. Progress bar never moves. I get to this screen whether I start it in recovery (which is just the factory recov - looks like during the initial 17% it wiped out my TWRP), attempt to start it in download mode (I do not get the download mode screen with the blue dots anymore), or regularly by just holding the power button.

ok
Dont plug it into the computer and try to power it up what does ot do?

Same thing.

read this
http://forum.xda-developers.com/lg-g3/help/lg-g3-bricked-tried-everything-experts-t2852962 this might help

pacods61 said:
http://forum.xda-developers.com/lg-g3/help/lg-g3-bricked-tried-everything-experts-t2852962 this might help
Click to expand...
Click to collapse
Ok that didn't work for me but I did try the LGFlashTool using Board DL instead of Upgrade DL and it was moving a bit. Finally got to 10% and failed at 574 sec with the error "We can't communicate with Phone". I am using the cable that came with the phone. It isn't damaged or anything.
Here's what is shows in the LG Flashtool window (this is port 1 (com41)
Code:
PID: BS09S150309001007
IMEI: <myimei>
Model: D852
DLL: D852
BIN: <correct bin file from stock roms>
SWV: LGD852AT-01-V20C-302-720-FEB-04-(cuts off here can't read rest)
SWOV: LGD852AT-00-V20C-RGS-CA-FEB-04(cuts off here can't read rest)
Initializing
USB Connection Established
Start Download
LAF: Bin_User_Mode
PRIMARYGPT
MODEM
LAF:Bin_User_Mode
PRIMARYGPT
LAF:Bin_User_Mode
PRIMARYGPT
MODEM
[14: 7:28) We can't communicate with phone
00000064
On the phone it shows COM41 under the usb icon on under firmware update and 0% progress. In the box below it says:
Code:
F USER 50.0 A50.0 B70 UHS
S U LG-D852 04.4.2 Hrev_10
D85210b
D85210b
That's it. Should I leave the phone connected at this point or unplug it? Device still shown in device manager (have had it up beside the LG Flashtool window the whole time. I do see it refresh from time to time but the contents dont' seem to change at all.

Ok so I left this over night and when I checked the phone this morning it's different but I don't think it's good.
Looks like it proceeded but ended with:
FBOOT Check
FBOOT Complete Time [0s ] 1th try
Factory Reset Flag = 2
Factory Reset Flag Check Fail!!!
And my phone has a blue screen with Factory Reset Status and a big red '2'
Now what do I do?

Some further information.
If I run the LGFlashTool in Board DL action mode, it seems like the process works but I end up with the red 2 on the screen. But I don't get 'can't change to download mode' or 'cannot communicate with phone' errors.
However if I choose Upgrade DL action mode, then I get 'can't change to download mode' or cannot communicate with phone'. ARGH. What gives?
I have tried things like fresh restarts (restarting PC), restarting the LG FlashTool between attempts, not restarting flashtool, etc. I can't seem to find the sweet spot.

here
http://forum.xda-developers.com/sprint-lg-g3/help/fix-bricked-lg-g3-ls990-stuck-fastboot-t3084562 another tutorial to try

Thanks, but no dice.
I don't get fastboot options, and if i download and attempt to use fastboot, it shows no devices.
Also, when following the steps for the BOARD DL option in the lg flashtool, it goes through the process but I get no ATT screen. Nor do I get the option to tap OK or Normal - as soon as my device reboots after the flash, it gives me a MINI OS (iirc) screen with a bunch of vertical bars below it moving up and down then it changes to the Factory Reset screen with the number 2.

last one lol
http://androidforums.com/threads/ho...-2-lg-g3-d855-twn-32-gb-problem-fixed.911271/ i found one more that could help it said to use a jdz not a tot hope it helps if not sry

Thanks - I'm going to give this a try, however I can't finda .kdz file for my phone (canada/rogers D852 LG G3) - the links in that post that link to firmware is for a tot file. Does anyone have a link to the KDZ?

Hi, I'm having the exact same problem now, where the phone only boots to the Firmware Update screen. Did you manage to fix it?

Indeed.
I used the KDZ method pacods61 posted last, but I had trouble actually finding kdz firmware. With some help I finally managed to do so from here: http://devtester.ro/projects/lg-firmwares/country.php?country=Canada
Direct link for D852 Rogers Lolipop 5.0.1: http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FWF448V332CPAKX8CEA4UCE/D85220g_00_1205.kdz

A bit harder than a soft brick

Hello everyone! So... I rooted my ZE551ML when I got it about a month ago and today an update pop-up from Asus shows up. So I said "what could go wrong?" .... How about everything?? Basically, I tried a bunch of different things because I could access via ADB, so I tried to unroot it with a bat file I found with a guide for that, but nothing. Now, I passed from black boot screen with white logo to white boot screen with black logo and I can't connect it with adb nor recovery mode. Is there something I can do to enter recovery? With the normal "volumeUP+power" I get nowhere. Can anybody help?

mikla90 said:
Hello everyone! So... I rooted my ZE551ML when I got it about a month ago and today an update pop-up from Asus shows up. So I said "what could go wrong?" .... How about everything?? Basically, I tried a bunch of different things because I could access via ADB, so I tried to unroot it with a bat file I found with a guide for that, but nothing. Now, I passed from black boot screen with white logo to white boot screen with black logo and I can't connect it with adb nor recovery mode. Is there something I can do to enter recovery? With the normal "volumeUP+power" I get nowhere. Can anybody help?
Click to expand...
Click to collapse
hope you can access fastboot. if yes you can install recovery and ifwi files from fastboot

How do I start fastboot mode? I let it charge all night and my pc does the "device connected/disconnected" sound all of the time, but adb says no device (the drivers are ok, I tried before). I have to say that I tried to flash boot.img, droidboot.img, recovery.img and system.img. Problem is, while I was downloading those files I found 2 other methods for recover it, one was to unroot it and the other to unlock the bootloader.... And I tried. Now, I'm unable to enter recovery.
Edit: I tried this guide http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 and for a short period of time (about a second or 2) I can see another device under the "Intel SOC" in device manager, but xFTSK cannot see the phone, even when it shows up for just a second on device manager.
Edit2: holding power down and plugging in the usb cable allows xFSTK to see my device, I put in the files and begin downloading, everything is going good but then it says
07:24:01 - XFSTK-LOG--Windriver Error: 0xC0000011, HC status: The host controller has set the Transaction Error (XactErr) bit in the transfer descriptor's status field
And from there it just starts all over again until it fails definetly.
Edit3: I'm trying the hell out of this software. I attach 2 logs to this post with relatives configurations. Still waiting for help.

Using xfstk tool
mikla90 said:
How do I start fastboot mode? I let it charge all night and my pc does the "device connected/disconnected" sound all of the time, but adb says no device (the drivers are ok, I tried before). I have to say that I tried to flash boot.img, droidboot.img, recovery.img and system.img. Problem is, while I was downloading those files I found 2 other methods for recover it, one was to unroot it and the other to unlock the bootloader.... And I tried. Now, I'm unable to enter recovery.
Edit: I tried this guide http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 and for a short period of time (about a second or 2) I can see another device under the "Intel SOC" in device manager, but xFTSK cannot see the phone, even when it shows up for just a second on device manager.
Edit2: holding power down and plugging in the usb cable allows xFSTK to see my device, I put in the files and begin downloading, everything is going good but then it says
07:24:01 - XFSTK-LOG--Windriver Error: 0xC0000011, HC status: The host controller has set the Transaction Error (XactErr) bit in the transfer descriptor's status field
And from there it just starts all over again until it fails definetly.
Edit3: I'm trying the hell out of this software. I attach 2 logs to this post with relatives configurations. Still waiting for help.
Click to expand...
Click to collapse
open Xfstk Tool and click Tab -MRD/AO/BO +MOOR Ao+CRC then go to settings under option menu - enable GP Flag Override Option and Enter value - 0x80000807 and save (OK), then choose files -
FW Dnx - dnx_fwr.bin
IFWI - ifwi.bin
OS IMAGE - droidboot_dnx.img.POS_sign.bin
AND connect phone, press begin and Xfstk tool detect the phone and install the required files and you will able to get Normal Fastboot mode and install the firmware by fastboot / Asus Flash tool / or -SDUPDATE Zip file.
-------------------
Press Thanks Button, If i am helped you
-------------------

In the end, after about 20 times, XFSTK did flash what should have. Now, I'm back in business. I changed nothing, just kept trying.

Samsung GT-N5110 - Stuck in Boot Loop, Can't flash Due To "Write Error!!"

I have a Samsung Note 8 GT-N5110 (WiFi only) that is stuck at the Samsung logo.
This started after there was an attempt to flash a non-stock firmware and the device powered off before it was done.
When I attempt to enter Recovery Mode (Volume Up + Home + Power) it displays "Write Fail!" in upper left of the screen.
I am able to enter "Download Mode", so I've tried flashing a stock firmware using Odin.
I've tried both a One-Click recovery based on ODIN3 v1.81 and also tried Odin3 v3.12.10.
Each time, Odin fails, with a message:
write fail!!
SW REV. CHECK FAIL. DEVICE:2, BINARY:1
I've tried various versions of firmware, and nothing seems to work.
I've tried disconnecting the battery for a minute or so, and it still fails.
Any ideas what else I can try?
I have screen shots and detailed logs of what I've been getting, if that helps.
Thanks!

Believe it or not, I still have this device, and have not been able to get it to work!
So, I'll just revive this zombie post more than 2 years later, and see if anyone has any idea on what to do.
I'm in the fourth (fifth? sixth?) week of corona-quarrantine, so plenty of time to look into this!

The tablet needs more power than the computer's USB port can deliver. Thus, it will slowly drain the battery while connected to the computer and working via ADB, Odin or Heimdall. Seems like that has been the case in your earlier attempt, resulting in a corrupt flash memory. I can't tell if it's really defective or just corrupt and in need of formatting.
I'd try to:
1) Charge the battery
2) Copy LineageOS to the MicroSD card
3) Boot into download mode and install TWRP only via Odin or Heimdall. If this works,
4) Boot into Recovery (TWRP, not the stock one!), connect the charger to keep it powered and go from there (wipe and repair the internal flash, install LineageOS)
If this doesn't work, try if you can find any service functions in Odin or Heimdall to wipe and repair the internal flash.
Good Luck!
Ektus.

Hi Ektus,
Thanks for your help!
I will try as you suggested, and see what happens.
I'll let you know how I do.
Thanks!

I had similar problem. What I did is just change the USB cable to new.