Develop Bugs

Recovered a bricked Zenphone 2 Z008 after 2 years...

Backstory
2 years ago, I installed nougat into my marshmallow zenphone. A few days later there was a problem with 3g and wifi, so after some searching, I found out I needed to flash modem.zip, after doing so, the phone no longer boot, bootloader is good, recovery is gone and fastboot is gone. Spent about 20+ hours trying to recover... but to no success. The main problem was using the XFSTK method, it did boot to fastboot, but the damn phone product code becomes a Z00A, so flashing a z008 rom led to fastboot refusing to flash. Flashing a z00a rom led to bootloop...
Since I wasted too much damn time trying to recover, and I needed a phone quickly, I bought a 32GB mi max for $120 and never looked back.... until today 03 March 2018.
Recovering the hardbricked Asus phone easily
1) Install the intel usb soc http://drive.google.com/file/d/0B2oMRhweQ4CHbURUNk1ZTHI2Mjg/view?usp=sharing
2) Disable driver verification in Windows 8/10 by rebooting into advanced menu
3) Install intel usb soc above
4) Download and install Download xFSTK Downloader v1.7 https://drive.google.com/file/d/0B2oMRhweQ4CHbDNQdy1jVUJFcEE/view
5) Download the files for xFSTK and unzip
ZE550ML http://drive.google.com/file/d/0B2oMRhweQ4CHcHg4WXJQckFGOTA/view? Usp = sharing
ZE551ML http://drive.google.com/file/d/0B2oMRhweQ4CHR21YaDdXdUNlOGs/view? Usp = sharing
6) Open xFSTK,
go settings, tick enable GP flag override and use the number 0x800000807
link the dnx fwr, ifwi and droidboot from step 5 as follows: https://i.imgur.com/mKZoUdi.png
7) Make sure your phone is off, click begin download then plug in phone, it will start flashing
Sometimes it fails while flashing firmware, sometimes it fails while flashing OS. Doesn't matter keep retrying. Pressing volume button while plugging in phone MAY help.
8) Once successful, you will see 4 color background, then usb cable image, then fastboot mode. If you fail halfway in flashing you will stop at either one of the images. Keep retrying until you reach fastboot.
9) At fastboot, you are safe. Go charge your phone for 1 hour. If your screen dies, do not press power button, press volume button it will remain in fastboot mode.
10) While your phone is charging, install asus flash tool https://drive.google.com/open?id=0B4uMV7GwfDAEYm5RWTFydXZWOTQ
Download the raw file https://drive.google.com/drive/folders/13In6163G8S9BbjiNlEOF-fOXhVIC0z9r?usp=sharing
11) With phone charged, plug in your phone and open the flash tool. Your phone should appear. If not replug usb cable/change usb cable/port, restart the flash tool and leave it plugged in and wait UNTIL the flash tool recognizes it. It will recognize... eventually.
12) select correct model, tick erase data, and locate the firmware. Once recognized, highlight it and click START
13) After 20 minutes, it will be stuck because of the change in serial number. plug out usb cable, restart program, plug back in.
14) Wait for the program to recognize the NEW serial number, then reflash the phone, this time IT WILL BE SUCCESSFUL and will boot into Android marshmallow.
Miscellaneous steps after unbricking
Unlock bootloader, flash recovery, flash custom firmware, root, gapps

Good of you to share. Thanks.

Bricked my own yesterday got it up and running after 6 hrs of looking at guides nice phone good spec but probably be selling on as it not getting any security updates any more I could live with marshmallow but bit wary of no security updates

Bricked my LGG3

Hello everyone,
so here's my problem:
Wednesday morning i took my phone out of my pocket and had a blackscreen. I tried to restart it and took out the batterie but i always got stuck in the LG Logo or a bootloop. Since i had TWRP and lineage OS installed, i tried to go into the twrp menu with the factory mode (power button + volume down) but after the "double yes" i always got a blackscreen.
So i went into the internet to fix it myself. I tried the "LG Flash Tool 2014" with the kdz. reset & the other Flash tool with the tot. reset. Both didnt recognize my phone. At this point, the only thing that worked was the download mode BUT not the recovery mode that usually comes after it. It just showed the download mode for some seconds and then a black screen. Later i noticed that my phone showed as a "qualcomm device" in the device manager, and the internet said that this was bad. So i used "Board diag" and "Smart boot diag" to fix it, but at the point where the device should have restarted, and the download mode should have worked WITH the recovery mode, i always ONLY had the 6 second download mode. After messing a bit with "Board Diag" i even got it to show up as LGE AndroidNet USB Serial Port in the device manager, which apparently was even more bad and only way to go back to qualcomm was to shorten the pins which i did. And it worked BUT now i was back with the qualcomm stuff.
So as you can see, i've prety much run i circles since wednesday... Iam now at a point where 3 different thingscan happen when I try to put my LG into download mode (volume up + usb cable):
1. Its recognized as a unknown device which is constantly connecting and diconnecting, so iam assuming my phone is bootlooping with a black screen.
2. The download mode icon shows on my phone and disappears after some seconds but my pc fails to recognize it.
3. Nothing happens and the screen stays black
When i only connect the usb cable, it shows a stuck charging icon for some seconds and then goes black. Connecting without a battery shows the "missing battery icon". I tried with 2 pc's, both having the LG mobile driver 4.2 and the qualcomm driver installed AND beeing in testmode. Both don't recognize the device. I also tried 2 batteries on my phone but it changes nothing.
I have a D855. And i know that my situation is pretty f*cked but maybe someone i able to help me anyway. Thanks alot.

Phone Not Entering DA mode.

So Here are the steps
1. My bootloader got unlocked.
2. I Installed factory preloader and lk images.
3. Rebooted to Fasboot and flashed TWRP 3.3.1-0924 by wzsx150 (the only Android 9 recovery that didn't get removed immediately after flashing and rebooting for 1st time to get to recovery).
4. Formatted Data, Closed AVB 2.0 and Signed TWRP.
5. Rebooted to Fastboot and flashed stock EEA Android 9 (11.0.3.0) from Global (11.0.6.0) and reflashed factory preloader and lk.
6. Rebooted to recovery, Formatted Data, Closed AVB 2.0 and Signed TWRP.
7. Using ADB sideload from Twrp Installed EEA Android 10 (11.0.2.0).
8. Rebooted into fastboot Installed Updated TWRP-3.3.1-1210 (by wzsx150).
9. Rebooted into fastboot and flashed misc.bin from same zip (according to bat file inside it should get flashed after recovery but I forgot.)
10. BRICKED. Booted to Redmi logo for 3 seconds and rebooted infinitely.
This type of brick in 4pda.ru according to google translate can be mitigated by letting battery drain and then enter DA download mode using SP Flash Tool.
I've Used the tool several time so I thought Okay no big deal.
So This is what I tried:
11. Pressed download button
12. Connected USB Cable to phone.
13. Device pauses a second (Probably for SP Flash Tool to respond) then doesn't enter DA (Unlike previous times) and screen brighten for a second or two but then turns off and repeats this process forever.
I've been using Drivers provided by Microsoft Update Catalogue but tried all the drivers on 'MTK Usb Driver v1.0.8' and 'Mediatek_Driver_Auto_Installer_1.1352.00' after disabling Driver Signature Enforcement. but even though drivers are installed they don't get loaded and after force installing them in add legacy drivers they are their but have yellow triangles and their Location lists as 'Unknown' and status as 'This device cannot start. (Code 10)'. Tried Removing them after adding them as a site suggested but that didn't work either.

I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical

wang1chung said:
I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical
Click to expand...
Click to collapse
So I tried Ubuntu. Problem isn't from Drivers. It's because my Windows or linux didn't ever got a chance to enter fastboot so they can load preload drivers properly.
In Windows, Mediatek USB Port is the only driver that get loaded, and that for only an instant then it disappears in Device Manager.
In Linux according to this Tutorial everything is fine but SP Flash Tool gives me a " ERROR : STATUS_ERR (-1073676287) , MSP ERROE CODE : 0x00. "
Based on this chinese site I should find my Vendor Id and Product Id specific to my system (or is it my chipset?) and then change some files but how do I get linux to recognize mediatek usb device first when It needs to enter fastboot for that to happen.
Is there any way to manually add it?
EDIT: So After some reading I realized that I have to get my phone to fastboot first to get the drivers recognized. In windows as far as I know there is no way for manually adding 'Location' to Drivers. what about Linux?

I think you're talking about a soft-brick and I'm talking about a hard-brick. If you can get to fastboot, it's a soft-brick.
Hold the volume down and power buttons simultaneously for 1min and see if your screen changes.
Don't worry about the Linux drivers, if your phone is in the correct mode, it'll work.

I don't think it's a Soft-Brick (unless Hard-Brick means even the display not turning up at all), Holding them for a minute with battery charged doesn't do anything. As soon as it boots back up it starts getting caught in Booting until Redmi logo and staying there for 2-3 seconds then reboots. I tried to hold Volume Down + Power for 3 minutes while caught in this bootloop but no fastboot. I'll retry when battery discharges again. first without usb cable attached then with.
Thanks for taking time to work this through with me. Nowadays with all service centers being closed it's really a nightmare to have something you need on internal storage and not being able to access it. First thing I'll do after this is to buy a 128GB SD card to store the important stuff.
By the way should I just use the Live Ubuntu or Install it to see if the problem is from being a live image.

When I hard bricked my phone, I didn't have anything but that white led when I plugged it in. If you have the redmi logo, should mean there is hope. I've only ever entered DA mode when I had a hard brick.
This might be one of those situations where letting the battery drop to 0% would allow you to access fastboot. MiFlash only works in fastboot and DA mode I believe. What happens when you hold volume up and power for a minute while plugged in to your computer? Run "ADB devices" to start the adb service first
I doubt it would make a difference live to installed, but it's your call if you have the time.

With Phone in Bootloop mode Holding Either Vl+ and Power or Vl- and Power doesn't make a difference.
With Phone Off and USB detached It's the same.
With USB attached Vol+ and Power for over 3 Mins result in Device Manger listing 'Mediatek USB Port' for as long as display remains 'dark but bright' (for 2-3 seconds then shuts down and turns itself back on). removing it when phone suddenly shuts down. when USB is detached phone remains shutdown.
With USB attached Vol- and Power for over 3 Mins result in Phone's Display Brightening for 5 seconds no device listing in Device Manager nor entering fastboot or being recognized by adb or fastboot (set on a permanent re-checking by a cmd script). then phone shuts itself down and back on.
LED situation:
With Vol+ and Power with USB attached LED when phone is Off is Fullbright. When Display Brightens It turns off.
With Vol- and Power with USB attached LED when Phone is Off Blinks Once Fullbright and then remains Semi-bright whether phone is on until shutdown and the Blinks Fullbright again.

I Live in Iran and with sanctions there is no way to pay anyone overseas. Unless they're willing to risk accepting cryptocurrencies from an Iranian , my only chance if I can't work it out is to wait till unofficial service centers here open.

Your phone only being detected for 5 seconds is supposed to happen. It checks for a signal from so flash and if it doesn't see it, drops off.
I'm not sure paying someone to remotely flash your phone will work if SP Flash isn't even trying or detecting your phone. With mine, it would detect and try to flash (red bar sitting at 100%) before throwing an error.
Try letting your battery die, if that doesn't work, maybe the test point mod will work. Otherwise, I think your only option is a service center.

LG G8s Bootloop after rooting with Magisk

Today I installed magisk with the help of this guide https://forum.xda-developers.com/lg-g8/how-to/rooting-g8s-guide-t4044193 . It worked and I had root access. After some hours I restarted my phone and now it's in bootloop. It can't shutdown and it's restarting endlessly (pressing the power button for 20 seconds shut it down but it immediatly restart). I can only enter the hard reset menu (by holding volume down and power button, is there a combination for recovery mode with volume up?)
I know I need a way to enter fastboot mode to reflash the normal boot partition from the original kdz or the entire kdz but I can't. neither adb devices or fastboot devices finds the phone and the phone it's not in recognized by the PC so no COM port assigned. Tried to follow this https://www.mylgphones.com/lg-g8-th...nbrick-restore-lg-g8-thinq-back-to-stock.html
Update: I entered the fastboot mode. I plugged the usb-c cable while clicking the volume down button while the phone was off. Now I will try to flash the boot_a.image from the original kdz file
Flashing the original boot_a.image worked. I will now try to understand why this happened

Cannot boot into download mode

Hi everybody, yesterday I was playing with my old Galaxy A50 trying to install a custom rom unsuccessfully.
I repeated the procedure three times installing TWRP and then Havoc OS but every time I tried to reboot from TWRP to OS I was stuck at the warning screen saying that the phone bootloader was unlocked and booting into download mode to reflash TWRP was blocked as it showed "only official binaries can be installed" (yes I installed Samsung disabler but still).
Still I was able to get the phone into download mode and reinstall the stock firmware as it seemed to be the only way to install and boot TWRP.
But at 4th time repeating the process I got frustrated, shut down the computer and left the phone on the warning screen still connected to computer usb cable.
Then I got back and noticed the phone was off as the battery died.
Indeed the battery died, so I put the phone in charging and after it reached 100% I tried to boot into download mode again to reflash stock firmware.
But here's the strange thing, I cannot boot into download mode anymore as pressing vol up+vol down while connecting usb cable, shows the lightning charge logo for 5 secs and then reboots infinitely with the same pattern.
If I force reboot by pressing vol down+power it shows the Samsung logo with the warning below it, then skips to another screen with another warning suggesting to press power button to continue (which does nothing) and after a while reboots to samsung logo.
So it doesn't seem it is bricked, it looks more like a battery controller fault, so I tried to detach the battery flex from the board, hoping it would reset the controller but it's still the same.
Also I tried with the flex detached and still no download mode is possible.
Was the download mode somehow erased? (if it's even possible considering it's the motherboard firmware)
If you need photos, videos or even a call on zoom, Skype, webex I would be glad to show you

same i got the same problem i can't find nothing for this when i press volume up and down and put the otg cable its simply charges but it gets stuck on the logo image there's no way to fix this but the only way is to open the phone,change the emmc and put one from samsung,close the phone flash a custom rom and you are done.

If you can enter recovery, do it. As soon as your phone gets into it, select the power off variant and then try to enter the download mode.
It seems like you did not unlock the bootloader, did you?

The bootloader Is unlocked i can't enter in the recovery because the phone locks on charging logo and its fully charged but when i try without charger It doesn't start.