Develop Bugs

i747 Hard Bricked: QHSUSB - DLOAD : Needing a debrick.img

SGH-I747 (4.1.2 i747's please)/ SGH-i747m( If you have a official 4.3 i747m, please post a debrick.img) only:
Hi, I recently hard bricked my phone into QHSUSB DLOAD and I am going to attempt repairing it through the SD Card boot method.
http://forum.xda-developers.com/editpost.php?do=editpost&p=47431259
I need a debrick.img to flash to the SD card in a Linux OS.
I would have gotten it myself but my phone is obviously dead. I found one before on XDA, but it did not work on my device and it gave me an error in the Linux terminal when it should not have.
-snip-
The end of the 3rd boot-loader stage in mmcblk0 is at 77.3 megabytes. If you are going to help out using your device, try to refrain from uploading an image with a different ROM other than root.
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/backup.img bs=2m count=81054925
The count is the amount of bytes. I am not sure if it is meant to be 1000 bytes=kilobyte or 1024 bytes=kilobyte. The count above is for 1024.
I need someone to install the Galaxy S III unified toolkit, and pull the first 7 partitions from mmcblk0 ,which is where the third bootloader stage ends.(Don't upload a heavily modified device please) http://www.skipsoft.net/?page_id=213 Once you get the files, PM me.
If anyone has a link to a working one, please post that. If you want to get your own image to help me, go ahead.
Thanks guys.

Sorry for the bump... I just need the device running again since the state it's in, it CAN be unbricked.

99ytrewq9111 said:
Sorry for the bump... I just need the device running again since the state it's in, it CAN be unbricked.
Click to expand...
Click to collapse
what happened?

winosxbuntu said:
what happened?
Click to expand...
Click to collapse
I tried to unlock what I thought was a locked bootloader(I could only enter bootloader through ADB)
I found an article that says ezunlock works on all S III's.
It corrupted my bootloader,and my phone gives off no signs of life except "Device QHSUSB-DLOAD not recognized" when plugged in.
This means the motherboard/processor wasn't able to boot from the hard disk, so then it tries the SDcard if it matches the phone close enough.
I need someone to use their rooted i747 to dump the first 77.3 megabytes of "mmcblk0". That contains the firmware and bootloaders. With that, i can burn it to an sdcard in a linux operating system and plug it into my phone.

99ytrewq9111 said:
Sorry for the bump... I just need the device running again since the state it's in, it CAN be unbricked.
Click to expand...
Click to collapse
99ytrewq9111 said:
I tried to unlock what I thought was a locked bootloader(I could only enter bootloader through ADB)
I found an article that says ezunlock works on all S III's.
It corrupted my bootloader,and my phone gives off no signs of life except "Device QHSUSB-DLOAD not recognized" when plugged in.
This means the motherboard/processor wasn't able to boot from the hard disk, so then it tries the SDcard if it matches the phone close enough.
I need someone to use their rooted i747 to dump the first 77.3 megabytes of "mmcblk0". That contains the firmware and bootloaders. With that, i can burn it to an sdcard in a linux operating system and plug it into my phone.
Click to expand...
Click to collapse
find a download link for this http://forum.xda-developers.com/showthread.php?t=1746665 (samsung galaxy s3 toolkit) which can help you fix your phone
if that does not help take it to mobiletechvideos.com and they will fix it for you REASONABLE PRICE
its XDA you will get the help you deserve PLUS i have never encounted that kind of problem HOPE TO GOD IDONT but again am sure an SD-CARD that can write firmware/system IS VALUABLE/USEFULL compared to nothing and that means there is hope left to fix bad code :laugh:

winosxbuntu said:
find a download link for this http://forum.xda-developers.com/showthread.php?t=1746665 (samsung galaxy s3 toolkit) which can help you fix your phone
if that does not help take it to mobiletechvideos.com and they will fix it for you REASONABLE PRICE
its XDA you will get the help you deserve PLUS i have never encounted that kind of problem HOPE TO GOD IDONT but again am sure an SD-CARD that can write firmware/system IS VALUABLE/USEFULL compared to nothing and that means there is hope left to fix bad code :laugh:
Click to expand...
Click to collapse
Thanks for that link! It looks very promising, and I can probably find a stock boot.IMG in there. I will work on tomorrow. If I succeed, I'll edit the OP and make a debrick guide for this drvice forum. A word of advice, try not to mess with your bootloader or you end up like me

winosxbuntu said:
find a download link for this http://forum.xda-developers.com/showthread.php?t=1746665 (samsung galaxy s3 toolkit) which can help you fix your phone
if that does not help take it to mobiletechvideos.com and they will fix it for you REASONABLE PRICE
its XDA you will get the help you deserve PLUS i have never encounted that kind of problem HOPE TO GOD IDONT but again am sure an SD-CARD that can write firmware/system IS VALUABLE/USEFULL compared to nothing and that means there is hope left to fix bad code :laugh:
Click to expand...
Click to collapse
Hi, the toolkit didn't fix my phone, but its defiantly a step up. Since I'm assuming you have the toolkit installed that you suggested it, could you do me a favor?
It will be a bit easier using the toolkit to extract the partition files. If you could pull the first 7 partitions from "mmcblk0" of your device through the toolkit, it will probably set the next step to fix my phone. (Assuming you have a 16g i747... I don't really know)
You don't have to do this of course.
Thanks man.

Bump. Can anyone help out? All I need is the first 7 partitions.
Sent from my GT-I9300 using xda app-developers app

99ytrewq9111 said:
Bump. Can anyone help out? All I need is the first 7 partitions.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
either try using this link http://forum.xda-developers.com/showpost.php?p=27239761 am pretty sure it works for all S3 models, either way on the I747 forum it has been removed, the download link does not work........ so use this
it will work, it may not work but for the time being use this toolkit and also search forums or Google on how to fix this without, i think i found some answers after i had an emmc brick with my S2 but i did not have an SD card to re-write firmware to work again on my phone so i bought the S3 and its awesome

winosxbuntu said:
either try using this link http://forum.xda-developers.com/showpost.php?p=27239761 am pretty sure it works for all S3 models, either way on the I747 forum it has been removed, the download link does not work........ so use this
it will work, it may not work but for the time being use this toolkit and also search forums or Google on how to fix this without, i think i found some answers after i had an emmc brick with my S2 but i did not have an SD card to re-write firmware to work again on my phone so i bought the S3 and its awesome
Click to expand...
Click to collapse
The problem is I need a working phone to pull the partitions. :/ I tried to use the boot image, but it had an error writing while in the linux.

99ytrewq9111 said:
The problem is I need a working phone to pull the partitions. :/ I tried to use the boot image, but it had an error writing while in the linux.
Click to expand...
Click to collapse
This one worked for me http://forum.xda-developers.com/showpost.php?p=46258374&postcount=172

I have a similar problem Hard Bricked after update to 4.3 tried to flash my phone Backup 4.1.2 and died can not log in or recovery nor danlold.Is there any solution.

Bradkirk said:
This one worked for me http://forum.xda-developers.com/showpost.php?p=46258374&postcount=172
Click to expand...
Click to collapse
Did you use an i747 or a i747m device?
If a i747m image works on an i747, it will basically fix all of my problems.

spensa said:
I have a similar problem Hard Bricked after update to 4.3 tried to flash my phone Backup 4.1.2 and died can not log in or recovery nor danlold.Is there any solution.
Click to expand...
Click to collapse
What message appears on your computer when you plug it in?
If it says QHSUSB-DLOAD, you are in faint light.
It stands for Qualcomm High Speed USD Download Mode.
What is means that your processor(qualcomm), is trying to boot, but it cannot find proper drivers for the hardware.
It will then look for something to boot from in the SDcard.
Here is a thread on how some other people were able to do it : http://forum.xda-developers.com/showthread.php?t=2439367

I have an I747M technically. I went for an actual I747M image just in case there was a slight difference. in the thread that one came from though there should be one for the actual att device if you look through it.
and just to confirm, yes the phone was blank and unresponsive. showing up as QHSUSB-DLOAD before i loaded that img onto my external SDcard. and I am using the same phone currently.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Bradkirk said:
I have an I747M technically. I went for an actual I747M image just in case there was a slight difference. in the thread that one came from though there should be one for the actual att device if you look through it.
and just to confirm, yes the phone was blank and unresponsive. showing up as QHSUSB-DLOAD before i loaded that img onto my external SDcard. and I am using the same phone currently.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Unfortunately that's the download I found that didn't work.
Thanks for trying though

damn! the only other help I can offer then, is that there is a pretty good thread on this over in the d2tmo section. someone there wrote a little tool to easily download the relevant data. might help you on your quest. or at least make it so you could ask someone that doesnt know ADB. best of luck!
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

99ytrewq9111 said:
What message appears on your computer when you plug it in?
If it says QHSUSB-DLOAD, you are in faint light.
It stands for Qualcomm High Speed USD Download Mode.
What is means that your processor(qualcomm), is trying to boot, but it cannot find proper drivers for the hardware.
It will then look for something to boot from in the SDcard.
Here is a thread on how some other people were able to do it : http://forum.xda-developers.com/showthread.php?t=2439367
Click to expand...
Click to collapse
when connected to the computer written QHSUSB-DLOAD,

spensa said:
when connected to the computer written QHSUSB-DLOAD,
Click to expand...
Click to collapse
OK , take out your battery and tell me your model number(Behind battery). And what phone company do you use?
Did you possibly save a NANDROID on a computer?
( if you have i747m, you can fix your phone, but its hard to do( I havnt done it yet)
Download this image http://forum.xda-developers.com/showpost.php?p=46258374&postcount=172 (thanks to @Bradkirk )
Follow these directions using that image above^^^ http://forum.xda-developers.com/showthread.php?t=2439367
You need to install a Linux operating system (Ubuntu works) to run the commands.
Edit:! According to the T-Mobile thread, you might need a debrick.IMG from a phone on 4.3
Once I know your phones model number, I can edit the main post and ask for you phone model's images.

99ytrewq9111 said:
OK , take out your battery and tell me your model number(Behind battery). And what phone company do you use?
Did you possibly save a NANDROID on a computer?
( if you have i747m, you can fix your phone, but its hard to do( I havnt done it yet)
Download this image http://forum.xda-developers.com/showpost.php?p=46258374&postcount=172 (thanks to @Bradkirk )
Follow these directions using that image above^^^ http://forum.xda-developers.com/showthread.php?t=2439367
You need to install a Linux operating system (Ubuntu works) to run the commands.
Edit:! According to the T-Mobile thread, you might need a debrick.IMG from a phone on 4.3
Once I know your phones model number, I can edit the main post and ask for you phone model's images.
Click to expand...
Click to collapse
I took it to a service to repair

[TOT] Sprint LS980 ZVC 4.4.2

The Sprint ZVC 4.4.2 .TOT is now available on the Codefire servers. TOT is used along with a .dll in LG Flash to install the stock firmware. Running this WILL erase your data including whatever is on the internal SD card.
I had to pay for this.. so donations are welcomed :highfive:
TOT (ZVC zip.. unzip it FOOL!) and .DLL can be found HERE.
Guide to use this can be found HERE. Yes, it's for Verizon but it can be loosely followed.. just replace the verizon stuff with the Sprint files.

Autoprime first rooting with your ioroot 25 now this your such a help for Sprint and others
Sent from my LG-LS980 using XDA Premium 4 mobile app
---------- Post added at 11:50 AM ---------- Previous post was at 11:36 AM ----------
So wait I just go thought on LG flash tool
Sent from my LG-LS980 using XDA Premium 4 mobile app

Donation Details - Confirmation number: 6CP664455L4491501
Thanks for all the support.

Noob question: If I use this TOT to upgrade my ZV7 to ZVC, can I downgrade it back to ZV7 using ZV7 TOT? Asking since I use the permanent unlock and if it does not work on ZVC, I will have to downgrade it.

Pat123 said:
Noob question: If I use this TOT to upgrade my ZV7 to ZVC, can I downgrade it back to ZV7 using ZV7 TOT? Asking since I use the permanent unlock and if it does not work on ZVC, I will have to downgrade it.
Click to expand...
Click to collapse
I have not done it, but I believe others have confirmed you can still downgrade.

Permanent GSM unlock will be erased if you use flash tool.
I took the OTA without root with stock recovery without GSM unlock.
Managed to root using ioroot25, flashed CDMA on NV got data for CDMA, then tried the unlock for GSM. Did not work. Now after messing around I managed to unlock GSM with data. Also found that it's either GSM or CDMA. Both for now will not work together like before.
Sent from my LG-LS980 using Tapatalk

Unrelated to the update by phone decided to brick itself while doing a backup.
I decided to go ahead and do the upgrade while I am restoring. I can get into download mode, but my computer can no see it. Installed Drivers already, just does not show up in device manager.
Anyone have any ideas on how I can get this going?

Is there a version that won't wipe all data from the phone? i made a backup but forgot to drop box it so now i need to save that if possible and then restore the firmware

pvinodnayak said:
Unrelated to the update by phone decided to brick itself while doing a backup.
I decided to go ahead and do the upgrade while I am restoring. I can get into download mode, but my computer can no see it. Installed Drivers already, just does not show up in device manager.
Anyone have any ideas on how I can get this going?
Click to expand...
Click to collapse
Change the port number for the device in the Microsoft device manager...I can't remember if it is port 41 or port 43. Give both a try!

keezy1986 said:
Change the port number for the device in the Microsoft device manager...I can't remember if it is port 41 or port 43. Give both a try!
Click to expand...
Click to collapse
It is port 41, but I can not change it as Windows doesn't recognize that a device has been plugged in at all.

New to TOT and LG in general, would I be able to use this to come from ZV8? I assume that TOT's completely redo everything so it doesn't matter (to a degree) what's on it before (except in the case of downgrading). Thanks!

lil_jimmy_norton said:
It is port 41, but I can not change it as Windows doesn't recognize that a device has been plugged in at all.
Click to expand...
Click to collapse
Try different drivers. I had to use the TOT method found here and it worked for me with no issues. http://forum.xda-developers.com/showthread.php?t=2432476

This worked where the modified OTA failed. I did need to unplug and re-attach the phone after the driver sorted itself out.
Thank you!

Hope someone makes a flashable pre rooted ROM.zip from this.

lil_jimmy_norton said:
Unrelated to the update by phone decided to brick itself while doing a backup.
I decided to go ahead and do the upgrade while I am restoring. I can get into download mode, but my computer can no see it. Installed Drivers already, just does not show up in device manager.
Anyone have any ideas on how I can get this going?
Click to expand...
Click to collapse
Try a diff computer.
Sent from my LG-LS980 using Tapatalk

pvinodnayak said:
Permanent GSM unlock will be erased if you use flash tool.
I took the OTA without root with stock recovery without GSM unlock.
Managed to root using ioroot25, flashed CDMA on NV got data for CDMA, then tried the unlock for GSM. Did not work. Now after messing around I managed to unlock GSM with data. Also found that it's either GSM or CDMA. Both for now will not work together like before.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
so if I flash to zvc, knowing the unlock will be erased, then root the phone using ioroot 25, follow the steps of permanent unlock, will it work on GSM again?

Gsm unlock
obie992 said:
so if I flash to zvc, knowing the unlock will be erased, then root the phone using ioroot 25, follow the steps of permanent unlock, will it work on GSM again?
Click to expand...
Click to collapse
Give it a shot. must work!!

can someone upload it to a torrent, i have a slow internet here, just failed @ 50% progress

autoprime said:
The Sprint ZVC 4.4.2 .TOT is now available on the Codefire servers. TOT is used along with a .dll in LG Flash to install the stock firmware. Running this WILL erase your data including whatever is on the internal SD card.
I had to pay for this.. so donations are welcomed :highfive:
TOT (zvc .zip.. unzip it fool!) and .dll can be found HERE.
Guide to use this can be found HERE. Yes, it's for Verizon but it can be loosely followed.. just replace the verizon stuff with the Sprint files.
Click to expand...
Click to collapse
what's the MD5/SHA1 sum for the TOT so I can be sure my download is good?

Wonder if this happened to anyone else. First I installed the LGFlashTool 1.8, then set my clock to 4/1/2012 and opened LGFlashTool. It says something about LG FLASH TOOL ERROR LG USB/PARELLEL. went ahead anyway and selected the .dll and .tot files and changed all the ports per instructions. Long story short, the files flashed but showed failed at 94% but phone had booted to accessibility settings and was talking to me in the weird robotic voice. I went ahead and disconnected and set up phone then rooted with ioroot25. all seems to ok but I wonder if the fail is going to be a problem somewhere down the line. I have not noticed any problems. Any suggestions?

[Q] Did I also brick my phone?

I tired to install twrp, but something went wrong and now my screen doesnt turn on. However when I connect it to the PC it dings and shows up as a modem. imgur..com/UuNaZV2 remove a dot and link should work, I dont have ten post so xda wont let me post outside links yet.

epicsnat said:
I tired to install twrp, but something went wrong and now my screen doesnt turn on. However when I connect it to the PC it dings and shows up as a modem. imgur..com/UuNaZV2 remove a dot and link should work, I dont have ten post so xda wont let me post outside links yet.
Click to expand...
Click to collapse
What did you do before this happened?

itsbighead said:
What did you do before this happened?
Click to expand...
Click to collapse
I tired to install TWRP Recovery with a guild on xda, http://forum.xda-developers.com/lg-g2/development-d802/tools-how-to-install-twrp-bump-d80230a-t3072186 I didnt notice it was for the g2 until this problem accrued. I then tired to turn it on but my computer read it as a modem.

epicsnat said:
I tired to install TWRP Recovery with a guild on xda, http://forum.xda-developers.com/lg-g2/development-d802/tools-how-to-install-twrp-bump-d80230a-t3072186 I didnt notice it was for the g2 until this problem accrued. I then tired to turn it on but my computer read it as a modem.
Click to expand...
Click to collapse
I think i know how you hardbricked your G3
Its because you wrote the G2 versions of the android bootloader, kernel and download mode partition
Its because of these commands below. It would have copied these partitions to your phone and then written them to your device
adb.exe push aboot.img /data/local/tmp/aboot.img
adb.exe push laf.img /data/local/tmp/laf.img
adb.exe push boot.img /data/local/tmp/boot.img
adb.exe push recovery.img /data/local/tmp/recovery.img
You can follow this guide instead with the D855 TOT+DLL but im doubtful it will work. This methods seems to be hit and miss http://forum.xda-developers.com/showthread.php?t=2772199
If it also wrote the System Bootlooder your phone would have automatically kicked into QHUSB_DLOAD and that is alot easier to fix than this

itsbighead said:
I think i know how you hardbricked your G3
Its because you wrote the G2 versions of the android bootloader, kernel and download mode partition
Its because of these commands below. It would have copied these partitions to your phone and then written them to your device
adb.exe push aboot.img /data/local/tmp/aboot.img
adb.exe push laf.img /data/local/tmp/laf.img
adb.exe push boot.img /data/local/tmp/boot.img
adb.exe push recovery.img /data/local/tmp/recovery.img
You can follow this guide instead with the D855 TOT+DLL but im doubtful it will work. This methods seems to be hit and miss http://forum.xda-developers.com/showthread.php?t=2772199
If it also wrote the System Bootlooder your phone would have automatically kicked into QHUSB_DLOAD and that is alot easier to fix than this
Click to expand...
Click to collapse
I already tired to flash my device back to 4.4.4 and it didn't work, guess I have to go to store and get a replacement. Thanks for the help, but if you want to see what the flashtool gave me then here is a screenshot imgur..com/FTSv55L (just remove one dot like before)

epicsnat said:
I already tired to flash my device back to 4.4.4 and it didn't work, guess I have to go to store and get a replacement. Thanks for the help, but if you want to see what the flashtool gave me then here is a screenshot imgur..com/FTSv55L (just remove one dot like before)
Click to expand...
Click to collapse
Just to be clear, what variant do you have?

itsbighead said:
Just to be clear, what variant do you have?
Click to expand...
Click to collapse
I have the At&t variant(D850)but I ordered my replacement already. Although if you still want to help me, and figure this out it would be a great learning experience for me.

I think I bricked my girls D851

Hey guys, long story short I can't use LG Flash Tool, or Odin as it won't even pick it up. All that happens when I press power is that it goes right to TWRP and I can't even restore a backup because it says the partitions don't exist. What should I do??? Thanks
Someone PLEASE HELP ME!!!
Eric

I had the same issue on my n7. Took me a week to fix. Had to end up restoring stock image. Then start from scratch and reroot.
Sent from my LG-D851 using Tapatalk

The Apostle said:
I had the same issue on my n7. Took me a week to fix. Had to end up restoring stock image. Then start from scratch and reroot.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Can you elaborate on how to do it exactly please?

The process will be different depending on your device. You need to get the stock image for your particular variant of the G3 and flash it.
Google either "unbrick LG G3" or "flash LG G3 stock image" or "TWRP, partition does not exist LG G3".
The process I used on the N7 will be different than the one on this device. I actually had to use ADB and CMD command prompts for the N7.
ADB is Android Debugging Bridge. You may need to Google that as well and watch some YouTube videos. Some if them can be very helpful.

The Apostle said:
The process will be different depending on your device. You need to get the stock image for your particular variant of the G3 and flash it.
Google either "unbrick LG G3" or "flash LG G3 stock image" or "TWRP, partition does not exist LG G3".
The process I used on the N7 will be different than the one on this device. I actually had to use ADB and CMD command prompts for the N7.
ADB is Android Debugging Bridge. You may need to Google that as well and watch some YouTube videos. Some if them can be very helpful.
Click to expand...
Click to collapse
Thanks bro but its all good now thanks to @1619415. He went wayyyy out of his way to help me get this resolved.

djerick3 said:
Thanks bro but its all good now thanks to @1619415. He went wayyyy out of his way to help me get this resolved.
Click to expand...
Click to collapse
NP, bro glad I could help also thanks for the shout out

^^^^ proof XDA isn't full of aye holios. LOL.

[Q] ATT ZE500CL/Z00D Bricked After OTA Update - HELP (ZenFone 2E)

I have an ATT ZenFone 2E that I rooted successfully with this guide (http://forum.xda-developers.com/showthread.php?t=3116531). Due to an error on my part(fat finger) I accidentally started the OTA update. Now when I try to boot the phone all I get is the AT&T logo/splash screen. I can get it to go into recovery mode and it also will connect via ADB. I have tried flashing the UL-ASUS_Z00D-WW-12.16.5.30-user.zip firmware via ADB fastboot but I get an error saying firmware is wrong carrier ATT (WW). Am I using the wrong firmware for AT&T? I have searched all over and cannot find any ZenFone 2 firmware other than WW, TW, and CN. Any help or suggestions much appreciated.

JRSouth said:
I have an ATT ZenFone 2E that I rooted successfully with this guide (http://forum.xda-developers.com/showthread.php?t=3116531). Due to an error on my part(fat finger) I accidentally started the OTA update. Now when I try to boot the phone all I get is the AT&T logo/splash screen. I can get it to go into recovery mode and it also will connect via ADB. I have tried flashing the UL-ASUS_Z00D-WW-12.16.5.30-user.zip firmware via ADB fastboot but I get an error saying firmware is wrong carrier ATT (WW). Am I using the wrong firmware for AT&T? I have searched all over and cannot find any ZenFone 2 firmware other than WW, TW, and CN. Any help or suggestions much appreciated.
Click to expand...
Click to collapse
i have the exact problem since saturday, you have to use the ATT firmware but i couldnt find it anywhere

also
please pm me if u fixed yours

Lactaid said:
please pm me if u fixed yours
Click to expand...
Click to collapse
Still no luck. I'm sure if we could find the AT&T firmware we would be able to recover. Unfortunately it appears it is not available on ASUS support and AT&T doesn't even provide firmware. Our only hope may be from a backup of another device that isn't bricked.
Does anybody know if we could possibly use the temporary CWM recovery used in the root method to flash to another ROM that is compatible with this device? Any input would be greatly appreciated.

Are there any details I can provide that would be helpful in finding a solution to recover this device? I've seen a few other people are having the same issue as I am and I would like to help them as well if I can get mine fixed. Thanks

JRSouth said:
Are there any details I can provide that would be helpful in finding a solution to recover this device? I've seen a few other people are having the same issue as I am and I would like to help them as well if I can get mine fixed. Thanks
Click to expand...
Click to collapse
ive literally tried everything, my device has been bricked for like 3 weeks now

Lactaid said:
ive literally tried everything, my device has been bricked for like 3 weeks now
Click to expand...
Click to collapse
Just out of curiosity have you tried running the xoa_unroot.bat while your device is in recovery/fastboot mode? Im not sure if it will help but I've found in other threads that to avoid soft bricking your device you must run the unroot prior to applying the OTA update. I'm sure it's probably too late but maybe worth a shot. I'm going to try it when I get home from work today.

JRSouth said:
Just out of curiosity have you tried running the xoa_unroot.bat while your device is in recovery/fastboot mode? Im not sure if it will help but I've found in other threads that to avoid soft bricking your device you must run the unroot prior to applying the OTA update. I'm sure it's probably too late but maybe worth a shot. I'm going to try it when I get home from work today.
Click to expand...
Click to collapse
i havent tried it yet, do you have a tutorial of it?

The truth hurts, your screwd. This is a budget phone. At&t will not support it. Throw away device my their standards.

http://forum.xda-developers.com/attachment.php?attachmentid=3505774&d=1444776691 here the system image for the file maybe try to flash it to see if it helps

http://forum.xda-developers.com/showpost.php?p=63323103&postcount=118
^^^This worked for me successfully!
Make sure to only restore system and disable MD5 Checksum Verification.

I have the same problem, what do I do with that file? How do I apply it through the SD, so I can apply update from SD? I forgot pin code to phone so i need to restore

need help
Lactaid said:
http://forum.xda-developers.com/attachment.php?attachmentid=3505774&d=1444776691 here the system image for the file maybe try to flash it to see if it helps
Click to expand...
Click to collapse
how do I flash this?

Hola, alguien lo consiguió hacer..???

Lactaid said:
http://forum.xda-developers.com/attachment.php?attachmentid=3505774&d=1444776691 here the system image for the file maybe try to flash it to see if it helps
Click to expand...
Click to collapse
Im getting an error that day footer is wrong :/

m1chb3ltr3 said:
Im getting an error that day footer is wrong :/
Click to expand...
Click to collapse
Wait, are you bricked and tried using that as the fix? I cant post links but Check out Asus, They have Firmware, Kernel (havent checked but read it earlier today), and Boot Unlock that you can get right from (assuming you have an account) My Products.
Also... Has anyone used that method recently?
Cathaterfish said:
Sorry I will give credit to DavePmer for his guide in minute, but qouting him for some reason wouldnt let me post, even when I removed the links? anyways I'll edit and give credit I promise
So my phone is stuck on the Asus Logo, I downloaded all of this and followed the instructions all the way up to:
11) now the fun part. open your microsd card and check the folder TWRP\BACKUPS see if it has a folder named
01234567890123456789 if it does great if not, not a problem just copy all the system files from the folder
you extracted TWRP-zf2e-ATT_12.16.10.7 to your microsd card TWRP\BACKUP\01234567890123456789\ whatever folder you have next\ in other words, replace your system.ext4.win000 files with my system.ext4.win000 file.
Replace your system.ext4.win001 with mine, and replace system.ext4.win00.md5 with mine as well as system.ext4.win001.md5 when done safely dismount the microsd card.
It then occurred to me that i should be more careful this time around... This was from October and although I ran across links saying for the most part that this was a good shot for fixing my ZE500CL, Z00D or whatever. But things have changed since then and I was wondering if this is still the best/easiest/safe route. I learned pretty quick that over looking things like OTA/Root or in my case Making assumptions is a fast path to really doing a number on your phone. (Honestly I just started even giving thought to rooting my phone, just considered them back ups I kept in a box). I now have the itch to do this right so hoping to fix this and go about this the right way.
Thanks for any input.
Currently DLing RussaiNBeaR, went and bought a card reader/writer. I was going to Download the firmware, kernel and boot unlock tool but currently staying at a place where im getting 160kbs on my DL's. So if I can get away with davepmer's guide that would be great, or something other or smaller than downloading 4gbs on this Internet Connection.
EDIT: Forgot to add that I haven't completed this step yet because the wording kind of tripped me up. And I want to do this right. When he says "in other words replace your system.ext4.win000 files with my system.ext4.win000 file." and then goes on and 3 more to the list. Does that mean only copy and replace those 4? or does that include all system.(whatever).(extension) files? Im sure it sounds really dumb or noobish but the fact that the next step is using twrp to restore using system only makes me afraid to do this part wrong.
Click to expand...
Click to collapse

ayuda
ATT ZE500CL/Z00D rom