Develop Bugs

Bootloader working but can't load recovery mode to restore ROM

Hi all,
Hope someone can help, I have a desire HD that has some issues.
Long story short the phone was acting up and was flashed with a non official ROM. It was working originally but after about a week it started acting up, with apps force closing, phone crashing altogether etc.
I am trying to get the phone back to a state that Vodafone in Australia will be able to warranty the phone in.
The current situation is that when the phone turns on, it'll load straight to the bootloader/hboot. Recovery mode does not work - it dumps you in to fastboot menu and fails to load.
System restore from boot menu does not work either, and there is no rom at all so USB debugging is a no go, and there appears to be no way to flash the ROM.
Any ideas? Any help would be greatly appreciated.
Thanks
Sent from my GT-P7100 using XDA App

Use adb / fastboot to push a new recovery to the phone (I hope you left USB debugging enabled).
Sent from my Ericsson T39m

Sadly no USB debugging doesn't seem to work. Makes the sound that it connects to the computer and that bootloader states its connected by usb however it doesn't seem to phone is connected. Any other ideas?
Sent from my GT-P7100 using XDA App

CrystalCastle said:
Sadly no USB debugging doesn't seem to work. Makes the sound that it connects to the computer and that bootloader states its connected by usb however it doesn't seem to phone is connected. Any other ideas?
Sent from my GT-P7100 using XDA App
Click to expand...
Click to collapse
ooh i tested it in my DHD and don´t works...how can be possible that don´t works adb parameters, but fastboot commander works perfectly??
maybe we have anything that works badly in our PC´s.. i´m in it...
ei crystal!! has you tested with FASTBOOT COMMANDER? if you download it you can flash a new recovery from this tool... its intuitive...
you only must to download the tool
download the recovery (lastest CWM in the DHD android development forum)
put the file in the paragraph that says "RECOVERY:not file set" and then push FLASH IT"".maybe you enjoy...
remember to put your device into boot loader

CrystalCastle said:
Sadly no USB debugging doesn't seem to work. Makes the sound that it connects to the computer and that bootloader states its connected by usb however it doesn't seem to phone is connected. Any other ideas?
Click to expand...
Click to collapse
How did you check to see if adb shell can see the device?

Run an pb98.img from the bootlaoder
Sent from my Motorola Startac running Atari 2600 software!

Mr_JMM said:
How did you check to see if adb shell can see the device?
Click to expand...
Click to collapse
adb get-state
result:
unknown

Code:
adb devices
But this does depend on you having previously ticked USB Debugging option before you had all these problems (no way to check now without being able to boot the phone).
If this fails you may have to try the previous suggestion of putting a PD98IMG on your sdcard then going into fastboot on the phone.

Mr_JMM said:
But this does depend on you having previously ticked USB Debugging option before you had all these problems (no way to check now without being able to boot the phone).
If this fails you may have to try the previous suggestion of putting a PD98IMG on your sdcard then going into fastboot on the phone.
Click to expand...
Click to collapse
Currently there is no Rom on the Phone. Just put PD98IMG.zip on the SD card which seems to be updating. Does it normally take a while to Update all the Sections?

Can take anything from 5 to 20+ minutes.

Seems to be taking ages to even get past [1]. Is that normal? Hasn't done anything. It says "Updating" yet I'm still yet to see it get past "[1] BOOTLOADER"

Just to confirm...
1. Turn phone off
2. Put PD98IMG file onto ROOT of sd card
3. Use vol- and power button to get to Fastboot
4. Scroll and select Bootloader (HBOOT)
(might automatically do last step when you boot phone)
Phone will show a message to say it is looking for the file then unpack it and install.

Mr_JMM said:
Just to confirm...
1. Turn phone off
2. Put PD98IMG file onto ROOT of sd card
3. Use vol- and power button to get to Fastboot
4. Scroll and select Bootloader (HBOOT)
(might automatically do last step when you boot phone)
Phone will show a message to say it is looking for the file then unpack it and install.
Click to expand...
Click to collapse
Confirmed dude. Doesn't seem to be doing much though. It has been stuck on "updating BOOTLOADER". It has trying to update it for more then 30mins now
It has a big list of 12 things it wants to update however it hasn't moved past the first file "BOOTLOADER" in over 30mins.

Did you confirm the MD5HASH of the file before putting it on the card?
Could you put a link to where you got the file from please?

http://forum.xda-developers.com/showthread.php?t=905003

Thank you.
Are you still connected to the PC? If so disconnect and try again.
Did you confirm the MD5HASH?
Have you got another SD card you can try? If not, reformat the current one and put the PD98IMG file on it again and try again.

The Device fails to even turn on now dude. Thanks anyway man

!!!???!!!
Damn. Do you just get the orange flashing light when you try to turn the phone on?
Take out SD Card and try.
If nothing works the bright side is you can send it to HTC and say "I woke up, turned it on and it's dead". Chances are they'll never be able to tell how it happened.
Many people did this when the Clockwork recovery bug bricked loads of phones.
Sorry but stay positive. Always a sliver lining.

Thank you
thanks for your great guidance to get back to recovery. I followed your tips and made it.
thanks a lot once again.
SERGI.3210 said:
ooh i tested it in my DHD and don´t works...how can be possible that don´t works adb parameters, but fastboot commander works perfectly??
maybe we have anything that works badly in our PC´s.. i´m in it...
ei crystal!! has you tested with FASTBOOT COMMANDER? if you download it you can flash a new recovery from this tool... its intuitive...
you only must to download the tool
download the recovery (lastest CWM in the DHD android development forum)
put the file in the paragraph that says "RECOVERY:not file set" and then push FLASH IT"".maybe you enjoy...
remember to put your device into boot loader
Click to expand...
Click to collapse

[Q] I have accidentally wiped system with TWRP and now the phone won't boot... :(

Hi All,
My phone was shutting itself down yesterday for no reason, so I boot into TWRP, thinking I should do something there, maybe restore to a previous backup, or wipe cache, etc...
I was in a hurry to go to the game (GO WARRIORS!), so I was just trying to get the phone ready for the game...
I tried the "Regular" wipe, and when it didn't work, I went into advanced wipe, and chose system wipe and REBOOT the phone (BAD IDEA!)....
so now my phone won't go past the SONY logo, because there is no system to boot into
What can be done here? Flashtool won't recognize my phone, and kept telling me I need to install the correct driver, and I can't boot into recovery.
Any help is much appreciated! Thanks!

Try connecting your phone to Sony PC companion it has all the device drivers. It may not recognize your phone when you connect it but proceed to the update/renew tab and follow the on screen prompts.

Nope ,won't connect, it turns on for like 1 second when the cable is plugged in... then it turns off again
is there any other way?

Connect it with fastboot.
To do this, hold the volume up button while connecting it with your PC, the LED will go blue.
Now you can either flash a rom via flashtool, repair it with PC Companion, or emma.
But since you have TWIRP, I would guess PC companion won't help you. You will likely also whipe all your backups stored on the phone by doing this, unless they're on the SD card, but that's better than having no phone at all.

,,,
1) install flash tool by androxyde
2) open the flash tool.
3) click thunder button and select flashmode.
4) connect your phone via usb (if message: device status no found [is ok])
5) press reset button 30 seconds( 1 vibrate and again 3-4 vibrates)
6) and now your phone is connected via flashmode.
7) Download original rom and put in any folder. [PM ME IF NOT HAVE ORIGINAL ROM .ftf]
8) Select "any" folder in source folder firmware selector
8) Press flash and wait.

sasu22 said:
1) install flash tool by androxyde
2) open the flash tool.
3) click thunder button and select flashmode.
4) connect your phone via usb (if message: device status no found [is ok])
5) press reset button 30 seconds( 1 vibrate and again 3-4 vibrates)
6) and now your phone is connected via flashmode.
7) Download original rom and put in any folder. [PM ME IF NOT HAVE ORIGINAL ROM .ftf]
8) Select "any" folder in source folder firmware selector
8) Press flash and wait.
Click to expand...
Click to collapse
I was able to flash "C6506_10.6.A.0.454 R2E_Customized US" to the phone, however ,after the process is done, it still won't get past the SONY screen.
Xperia shows underneath SONY logo this time though, so something was done to the phone.

ohhh
go to service gsm, maybe your motherboard/sd memory is die.

ah_hin said:
Hi All,
My phone was shutting itself down yesterday for no reason, so I boot into TWRP, thinking I should do something there, maybe restore to a previous backup, or wipe cache, etc...
I was in a hurry to go to the game (GO WARRIORS!), so I was just trying to get the phone ready for the game...
I tried the "Regular" wipe, and when it didn't work, I went into advanced wipe, and chose system wipe and REBOOT the phone (BAD IDEA!)....
so now my phone won't go past the SONY logo, because there is no system to boot into
What can be done here? Flashtool won't recognize my phone, and kept telling me I need to install the correct driver, and I can't boot into recovery.
Any help is much appreciated! Thanks!
Click to expand...
Click to collapse
If you use Windows 8, you must disable driver signature before installing flashtool, for this, hold shift key while restart your computer, enter in the proper settings and choose "disable signature driver", after this, install flashtool, then go to its folder and find folder driver and install the Xperia Z family driver. After these processes your phone will be recognized by flashtool
Sent from my Xperia ZL using XDA Free mobile app

sasu22 said:
go to service gsm, maybe your motherboard/sd memory is die.
Click to expand...
Click to collapse
Krllo said:
If you use Windows 8, you must disable driver signature before installing flashtool, for this, hold shift key while restart your computer, enter in the proper settings and choose "disable signature driver", after this, install flashtool, then go to its folder and find folder driver and install the Xperia Z family driver. After these processes your phone will be recognized by flashtool
Sent from my Xperia ZL using XDA Free mobile app
Click to expand...
Click to collapse
Try what @Krllo said if u have windows 8.& if u have 'Bluestack or any other android thing instlled ,unistall it.Install drivers from flashtool folders.Install them via selecting ANYWAY.
Try to reflash Kitkat.& if doesn't work I am afraid you got the issue which @sasu22 said.
I had sasme issue.Stuck @ sony logo.Seems something gets damaged.

dev neo said:
Try what @Krllo said if u have windows 8.& if u have 'Bluestack or any other android thing instlled ,unistall it.Install drivers from flashtool folders.Install them via selecting ANYWAY.
Try to reflash Kitkat.& if doesn't work I am afraid you got the issue which @sasu22 said.
I had sasme issue.Stuck @ sony logo.Seems something gets damaged.
Click to expand...
Click to collapse
My Phone is stuck on Sony Logo and rebooring again and again. With Fastboot I am getting simlock.ta file warning. After that phone is useless as of now. Do you recommend anything?

Krllo said:
If you use Windows 8, you must disable driver signature before installing flashtool, for this, hold shift key while restart your computer, enter in the proper settings and choose "disable signature driver", after this, install flashtool, then go to its folder and find folder driver and install the Xperia Z family driver. After these processes your phone will be recognized by flashtool
Sent from my Xperia ZL using XDA Free mobile app
Click to expand...
Click to collapse
dev neo said:
Try what @Krllo said if u have windows 8.& if u have 'Bluestack or any other android thing instlled ,unistall it.Install drivers from flashtool folders.Install them via selecting ANYWAY.
Try to reflash Kitkat.& if doesn't work I am afraid you got the issue which @sasu22 said.
I had sasme issue.Stuck @ sony logo.Seems something gets damaged.
Click to expand...
Click to collapse
anshumangoyal said:
My Phone is stuck on Sony Logo and rebooring again and again. With Fastboot I am getting simlock.ta file warning. After that phone is useless as of now. Do you recommend anything?
Click to expand...
Click to collapse
I couldn't get it fixed, so I bought a Z3 Compact, great phone, way faster than the ZL.

anshumangoyal said:
My Phone is stuck on Sony Logo and rebooring again and again. With Fastboot I am getting simlock.ta file warning. After that phone is useless as of now. Do you recommend anything?
Click to expand...
Click to collapse
Does your phone start to home screen when you put in AC charging from wall socket?
I think you mean Flashmode...If you didn't try flashmode.Install needed drivers from flashtool folder.Connect you phone in flashmode (volume down+cable into).disconnect it.
load ftf-exclude any .TA files if you r not locked to any carrier.--click on 'No final verification'.
flash and connect when asked when displays .Hope it helps.Keep us updated.
ah_hin said:
I couldn't get it fixed, so I bought a Z3 Compact, great phone, way faster than the ZL.
Click to expand...
Click to collapse
Nicely done.But if i were you i would never go with Sony once again.You will see what i am talking about.

Another "Bootlooping"-Problem

My Audio-Jack was brocken, so I replaced it (and with it a new touch/display-unit and a new battery).
After reassembling the sony-logo appears but thats it (the status-led is off but works, as in fastbootmode it turns blue). I came from Resurrection Remix® Lollipop v5.5.9.
I can access flash/fastboot and also tried to (not exactly in this order):
Did a full wipe
Relock bootloader
Do a System-Reset with PCC
Unlock bootloader again
Flash TWRP recovery.img with fastboot
Flash Stock-Rom with flashtool (1.236 custom de, downloaded via xperifirm)
Flash boot.img from CM via fastboot
Access TWRP and install Custom-Rom
...
Nothing helped, sometimes I only had the Sony-Logo, sometimes also the small xperia on bottom.
the phone is still "open", I checked all the connectors inside twice.
Any ideas?

nampill said:
My Audio-Jack was brocken, so I replaced it (and with it a new touch/display-unit and a new battery).
After reassembling the sony-logo appears but thats it (the status-led is off but works, as in fastbootmode it turns blue). I came from Resurrection Remix® Lollipop v5.5.9.
I can access flash/fastboot and also tried to (not exactly in this order):
Did a full wipe
Relock bootloader
Do a System-Reset with PCC
Unlock bootloader again
Flash TWRP recovery.img with fastboot
Flash Stock-Rom with flashtool (1.236 custom de, downloaded via xperifirm)
Flash boot.img from CM via fastboot
Access TWRP and install Custom-Rom
...
Nothing helped, sometimes I only had the Sony-Logo, sometimes also the small xperia on bottom.
the phone is still "open", I checked all the connectors inside twice.
Any ideas?
Click to expand...
Click to collapse
I don't know, but since it happened from opening the phone, I wonder if it might be hard brick. I've seen a tutorial on fixing it with test-point - http://forum.xda-developers.com/showthread.php?t=2682255 If your fastboot works but flashes are not applying, I don't know if anything else is going to work.

levone1 said:
I don't know, but since it happened from opening the phone, I wonder if it might be hard brick. I've seen a tutorial on fixing it with test-point - http://forum.xda-developers.com/showthread.php?t=2682255 If your fastboot works but flashes are not applying, I don't know if anything else is going to work.
Click to expand...
Click to collapse
Ive never "played" with gdisk, so Flashes are applying, the phone just doesnt start. If i flash factory with flashtool, only sony logo appears, led is off. When I flash TWRP sony logo and experia logo appear, the led turns green shortly and the phone vibrates and i can access twrp. if i connect it to pc, i can even see the sony z1 and access the internal storage... strange
Is there any way to access the service menu without the dialer (from recovery, ...)?

nampill said:
Ive never "played" with gdisk, so Flashes are applying, the phone just doesnt start. If i flash factory with flashtool, only sony logo appears, led is off. When I flash TWRP sony logo and experia logo appear, the led turns green shortly and the phone vibrates and i can access twrp. if i connect it to pc, i can even see the sony z1 and access the internal storage... strange
Is there any way to access the service menu without the dialer (from recovery, ...)?
Click to expand...
Click to collapse
Try this if you can get adb shell... http://forum.xda-developers.com/showpost.php?p=41687928&postcount=5
And you said you did try repair with PC Companion, right?

levone1 said:
Try this if you can get adb shell... http://forum.xda-developers.com/showpost.php?p=41687928&postcount=5
And you said you did try repair with PC Companion, right?
Click to expand...
Click to collapse
I cant run the command out of recovery: "Error: device unauthorized. Please check the confirmation dialog on your device."
Yes, I tryed a factory reset with pc companion.

nampill said:
I cant run the command out of recovery: "Error: device unauthorized. Please check the confirmation dialog on your device."
Yes, I tryed a factory reset with pc companion.
Click to expand...
Click to collapse
With an other recovery it worked. now it says : "/sbin/sh: am: not found"

nampill said:
With an other recovery it worked. now it says : "/sbin/sh: am: not found"
Click to expand...
Click to collapse
That's odd. It would seem like adb would recognize the -am- command. Did you confirm that you're in /adb, and device recognized?

What do you mean with "in ADB"?
I flashed twrp with fastboot and entered it
I did a full wipe and flashed a custom rom
Opened cmd in plattformtools and entered the command. --> error
ADB devices -l shows the device
The infernal storage is shown in Windows, but has only one empty folder " twrp". Is that normal?
Another Problem since today: the display has now almost no backgroundlight. Hard to read.
Im suggesting a Hardware Problem in the mainboard (changed display and audiojack to the old ones and had the same problem). Is there any way to check the Hardware outside Android system?

nampill said:
What do you mean with "in ADB"?
I flashed twrp with fastboot and entered it
I did a full wipe and flashed a custom rom
Opened cmd in plattformtools and entered the command. --> error
ADB devices -l shows the device
The infernal storage is shown in Windows, but has only one empty folder " twrp". Is that normal?
Another Problem since today: the display has now almost no backgroundlight. Hard to read.
Im suggesting a Hardware Problem in the mainboard (changed display and audiojack to the old ones and had the same problem). Is there any way to check the Hardware outside Android system?
Click to expand...
Click to collapse
I'm not an expert, so just guessing, but it seems to me that your rom is not being written. I would agree that it seems like hw, especially since it happened after opening the phone.

Arc S stuck on Legacy Xperia boot logo

Hey guys, so my Xperia Z's screen broke and the touch is unresponsive, so I took out my old Arc S out of the box and decided to boot it up, apparently I had gotten a new phone because this one had a booting problem.
Things I know:
It's been rooted, bootloader is unlocked, current ROM is Legacy Xperia, can't go into CWM recovery, connecting phone to PC and trying to flash new kernel won't work because flashtool doesn't recognize the device.
In device manager the phone comes up as an unknown device, downloaded the drivers from Sony's site, no luck, get error message saying "this file is not compatible with your version of Windows" or something.
I'm on W10 64bit.
So basically I'm kinda stuck, tried Google and other forums and nothing, I can't seem to get anywhere.
Could you guys help me out?
EDIT: Tried installing Android Studio, launching cmd from /appdata/roaming/android/sdk/platform-tools but when I enter the command line it says "waiting for device".
So I'm thinking this has to do with my PC not detecting my phone in fastboot mode or anyother mode.

This seems like a corrupted /system partition. First off, try another cable. Your current one might not be working (happened to me, kept reporting that it "did not recognize the device"). If that does not work, let's start with the basic troubleshooting steps. Does your phone boot info fastboot (turn off your phone, disconnect USB cable, hold menu button, reconnect USB while holding)? If it does, run "fastboot erase system" (I'm assuming you have the fastboot drivers installed and fastboot.exe in the working directory), and try booting into the recovery.
If not, let's try flashmode (turn off phone, disconnect USB, hold back button, reconnect while holding). If that works, just start up Flashtool (Download), wait for it to do its thing (sync), download the latest 4.1.B.0.587 ICS .ftf file from here. Once done, exit Flashtool, and go to the "drivers" folder. Install the flashmode drivers. Go back to Flashtool now.
In Flashtool, click the flash icon in the top-right of the program, and on the top you will find the working directory. Click the button on the right to it and select the directory where you downloaded the .ftf file. A new entry will show up in the menu on the left side. Click on it. Flashtool will prepare the file for flashing and instruct you how to connect your phone in flashmode. Be patient, this process may take a while. Once done (Flashtool will tell you), disconnect the phone, take the battery out for 5 seconds and put it back in, and then boot up the phone. The "SONY" logo should show up, followed by the "XPERIA" logo.
Set your phone up, and have fun flashing!
P.S. If you have any problems with your PC not recognizing your device while in USB Debugging (ADB says no devices), this worked for me.

bsevcenk said:
This seems like a corrupted /system partition. First off, try another cable. Your current one might not be working (happened to me, kept reporting that it "did not recognize the device"). If that does not work, let's start with the basic troubleshooting steps. Does your phone boot info fastboot (turn off your phone, disconnect USB cable, hold menu button, reconnect USB while holding)? If it does, run "fastboot erase system" (I'm assuming you have the fastboot drivers installed and fastboot.exe in the working directory), and try booting into the recovery.
If not, let's try flashmode (turn off phone, disconnect USB, hold back button, reconnect while holding). If that works, just start up Flashtool (Download), wait for it to do its thing (sync), download the latest 4.1.B.0.587 ICS .ftf file from here. Once done, exit Flashtool, and go to the "drivers" folder. Install the flashmode drivers. Go back to Flashtool now.
In Flashtool, click the flash icon in the top-right of the program, and on the top you will find the working directory. Click the button on the right to it and select the directory where you downloaded the .ftf file. A new entry will show up in the menu on the left side. Click on it. Flashtool will prepare the file for flashing and instruct you how to connect your phone in flashmode. Be patient, this process may take a while. Once done (Flashtool will tell you), disconnect the phone, take the battery out for 5 seconds and put it back in, and then boot up the phone. The "SONY" logo should show up, followed by the "XPERIA" logo.
Set your phone up, and have fun flashing!
P.S. If you have any problems with your PC not recognizing your device while in USB Debugging (ADB says no devices), this worked for me.
Click to expand...
Click to collapse
Hey man thank you so much for replying to the thread.
So I feel like a dumbass, multiple times I've read about changing cables, guess what, that's all it took.
So basically I changed the cable and instead of "unrecognized device" I got "S1 fastboot device", after that I installed the adb drivers for the Xperia Arc and voilà, it recognized as an adb device.
Onto platform-tools folder, cmd, flashed the kernel for Cyanogen 10, finally got into recovery and now after a full system wipe I'm flashing CM.
I'll let you know how it turns out.
Thanks a bunch!

Wolfarm141 said:
Hey man thank you so much for replying to the thread.
So I feel like a dumbass, multiple times I've read about changing cables, guess what, that's all it took.
So basically I changed the cable and instead of "unrecognized device" I got "S1 fastboot device", after that I installed the adb drivers for the Xperia Arc and voilà, it recognized as an adb device.
Onto platform-tools folder, cmd, flashed the kernel for Cyanogen 10, finally got into recovery and now after a full system wipe I'm flashing CM.
I'll let you know how it turns out.
Thanks a bunch!
Click to expand...
Click to collapse
Glad to know I helped!

Everything works fine now! Thanks sooo much!

[help] ZE551ML crashes, TWRP freezes, no connection in xfstk downloader

Hello all,
I'm stuck in different guides on what to do next.
Problem: Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13.
Also had charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
Tried:
- Factory reset in TWRP -> didn't work (the occasion I did get into CM13 it showed the setup again, so the reset actually went through, but loops still exist).
- When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
- When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
- Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC.
-> Problem: Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
- Another problem: When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.
So now im a bit stuck on what to try next to solve everything and get myself back into CM13. CM13 has ran since Feb '16 and have been a happy user since then until now.
Thanks for reading!

The simplest solution may be to flash back to stock and start over. If the phone doesn't behave properly on a stock ROM, there could be a hardware problem.

Hi there , in TWRP select reboot then power off .
Enter bootloader via buttons after 10 seconds being off !
Enter bootloader - power and vol + , when in bootloader if on LP -- flash raw with AFT (asus flash tool )
If any probs with above , you might have to fastboot flash stock recovery and boot to recovery if/and a , try raw if on LP with AFT or b, sideload stock firmware you flashed stock recovery for.

audit13 said:
The simplest solution may be to flash back to stock and start over. If the phone doesn't behave properly on a stock ROM, there could be a hardware problem.
Click to expand...
Click to collapse
timbernot said:
Hi there , in TWRP select reboot then power off .
Enter bootloader via buttons after 10 seconds being off !
Enter bootloader - power and vol + , when in bootloader if on LP -- flash raw with AFT (asus flash tool )
If any probs with above , you might have to fastboot flash stock recovery and boot to recovery if/and a , try raw if on LP with AFT or b, sideload stock firmware you flashed stock recovery for.
Click to expand...
Click to collapse
Thank you for your answers! Last hours been trying to flash the stock ROM back. However, when getting into bootloader, adb devices and fastboot devices don't show the device. Or it even freezes and gets into reboot loops again. So this is why I'm stuck, nothing seems to be working from all the guides and things I'm reading.
So precisely:
- Power off bootlooping device by holding power button
- Power on by holding PWR + VOL UP
- When vibrating: release PWR keep holding VOL UP
- Now i'm in bootloader?
- Connect USB cable to computer
- type adb devices, shows nothing.
So what can I try to make connection?

- Now i'm in bootloader?
- Connect USB cable to computer
- type adb devices, shows nothing.
@j4y_ha .................in bootloader
Type >
................................................. fastboot devices
What ifwi version number in bootloader ?

timbernot said:
- Now i'm in bootloader?
- Connect USB cable to computer
- type adb devices, shows nothing.
@j4y_ha .................in bootloader
Type >
................................................. fastboot devices
What ifwi version number in bootloader ?
Click to expand...
Click to collapse
The bootloader in shows the following:
IFWI version: 0094.0173
SERIAL_NUMBER = F8AZFG0152** (couldn't read the last 2 digits as the device rebooted again). Also sometimes the SN shows 012345689ABCDEF.
I've much trouble keeping the device in bootloader. Last tryings it keeps shutting down after couple of seconds in the menu.
EDIT:
So far the device seems to stay in bootloader mode now. I can cycle through the options normal boot, recovery etc. Below the screen it shows Continue the fastboot process in blue text. I've inserted the USB cable but have been unable to get "fastboot devices" to show any device. ASUS Flashtool also doesn't do anything.
I'm going to try to find a micro SD adapter so I can try flashing stock rom in TWRP from the phone itself (would that be something that could work or is this phone fubar?)

@j4y_ha
Do not attempt to flash stock rom in TWRP ! You will brick !
Flash a custom rom in TWRP only- not one with a mm bl version
You have LP
PLEASE
Follow my first reply to you

timbernot said:
@j4y_ha
Do not attempt to flash stock rom in TWRP ! You will brick !
Flash a custom rom in TWRP only- not one with a mm bl version
You have LP
PLEASE
Follow my first reply to you
Click to expand...
Click to collapse
Thank you for your support! Will try again.
I have MM not LP.
I don't understand your reply correctly I think so here is what I think you say?:
I should obtain LP rom for ZE551ML
Next, enter bootloader via buttons PWR & VOL UP after 10 seconds being off !
When in the bootloader, - power and vol + (short press or long?) , when in bootloader ->
I connect USB to computer, flash the file using AFT if I make connection. -- flash raw (raw = LP ROM from ASUS) with AFT (asus flash tool )
Thanks again for your help

j4y_ha said:
Thank you for your support! Will try again.
I have MM not LP.
Thanks again for your help
Click to expand...
Click to collapse
IFWI version: 0094.0173 is LP, NOT M
follow my first reply:good:
---------- Post added at 06:39 PM ---------- Previous post was at 06:37 PM ----------
No1
Hi there , in TWRP select reboot then power off .
---------- Post added at 06:40 PM ---------- Previous post was at 06:39 PM ----------
no2
Enter bootloader via buttons after 10 seconds being off !
no3
When in bootloader you are on LP -- flash raw with AFT (asus flash tool )

@timbernot I'm unable to make connection. Fastboot also most of the times freezes and goes to black screen. What could I possibly try now?
Sorry I thought CM13 was MM but then I'm on LP still haha :good:

j4y_ha said:
@timbernot I'm unable to make connection. Fastboot also most of the times freezes and goes to black screen. What could I possibly try now?
Sorry I thought CM13 was MM but then I'm on LP still haha :good:
Click to expand...
Click to collapse
I'm taking wild guess here that you got wrong TWRP recovery installed somehow or something from M causing all these problems , when you get into bootloader again..Scroll to and select reboot bootloader and fastboot flash stock recovery for LP version you was on .
Then , I guess your problems will be over , where you will be able to flash raw in bootloader or in stock recovery , adb side load the firmware

Thanks for your quick anwer. Will try to get through it haha :good:

DUDEE
that's not a problem.. THAT's like 20 different problems... I bricked the living crap out of my zen the day I bought it (because me = smartypants did not know that the MM boot unlocker is nonexistent so I just tried to root and update from my head using older techniques) and... the XTS tool thingy fixed it..
Don't get me wrong, i want to help but this is the problem that I feel little frustrated with..
Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13. ## (but it boots sometimes and goes into TWRP, so you have an easy fix to just revert to stock lollipop... why haven't you done that? You sound like you know what most of this stuff does...
Charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
## how do you connect this battery issue to your occasional bootloop? Check hardware or firmware and definitely use different threads.. there's no way these are all part of the "same problem"...
When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
## Same answer as above - this is unrelated to #2 and unrelated to #1 - is your TWRP the correct one? I mean... did you just maybe flash TWRP version 4000 Modified Alpha for Google Glass??? LOL
When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
## Is D2W there? "DoubleTap2Wake" ? Are you sure you have a good touch? (this maybe 20% sounds related to your TWRP touch going crazy..)
Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
## There's this awesome invention called DRIVERS... and we're lucky in this case (cuz I bricked an hour after I bought it) because Intel PC + Intel Phone = Yay... There is even.... a very specific "INTEL ASUS WINDOWS DRIVER" file... from the INTEL AND ASUS WEBSITE... or maybe your USB CABLE is f**? My point is... another unrelated issue where it sounds like you've not even tried it properly before complaining.. I like helping people. I don't like when people refuse to try or they skip the actual study-notes to do it... I used the EXACT same guide to unbrick and it worked in 2 mins... I'm on a 2007 Laptop which overheats if I use 4 tabs... how am I able to follow the exact same guide on a brand new "FULLY BRICKED" phone... it literally would vibrate after trying power button for 5 mins and be stuck in a "blank black screen" for hours and hours... No twrp no nothing.. and I did it - why didn't you? Same guide man...
When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.)
## Try again. Sometimes people accidentally hit power to early.. or whatever.. It's not a MK2 Fatality.. don't force yourself to get it exact.. Let the menu pop up... just wait a second and scroll up/down just to see if that works... then scroll to Boot-Recov and gently hit power+vUp.. should be fine.. otherwise just .. literally try 10 times.. it WILL work.
Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC
## Nope.. TWRP is like Bret Hart. It isn't unstable. Not for LP not MM not for N. Not for Stock Not for CM Not for AOSP. You *wanted* to do what you should have done right at the beginning but you didn't get that done properly (see below)
Essentially you have 8 different unrelated issues (and the biggest one is not reading guides, not trying hard enough and just thinking that people like me sit around and get paid for this)... and want ans in one place w/o just doing the simple thing of going back to everything stock...?? *it's just annoying cuz people who want to help will feel like.... others don't even try simply because we exist and have desire to help...* - I am not trying to offend you but I hope you get my pov.
Do This EXACTLY
#Buy a cable. Borrow a cable. Whatever you do be 1000000% sure the USB Cable is fine
#Install Intel Asus Android drivers from official EXE (google it... don't add new post for that link)
AND THEN
Follow the same Unbrick guide word for word *but* just pay close attention to these:-
IntelSeC Driver + device detected even if OFF (start>devman>showall>intelsec
In the official unbrick utility make sure you're on the second tab at the bottom
In settings check that your device flag is 0x08..... whatever instead of the default 0x000
Back in the *second tab at the bottom* (i don't remember exact name but it's in the guide) -- put the right files (mentioned in guide) in the right boxes.. (mentioned in guide) and remember you ONLY need the DVFWthingy... + TOKENthingy + IFWthingy
Plug the Zen in... hear the "da-dumm" sound... keep looking at the Unbrick tool.. and the moment you see Device Detected = 1 you hit install/start...
AFTER that is fully done *(and if you fail don't post just repeat from scratch)... I don't personally recommend Asus Flash tool it was acting dodgy for me but instead grab the RAW Stock... Rename it to zip.. open it and grab the img files and fastboot flash the fastboot droidboot.img + splashscreen splash.img + boot boot.img + recovery recovery.img
If you've followed all that from the guide and double checked what I've put up there.. you should be fine if you just fastboot reboot bootloader... and go into stock recovery... install zip/update and put your stock OS in there..
Done.
Just please take my advice and don't skim through guides, don't think you don't need to read something, don't click stuff without double checking every line from guide, print it out on PAPER if you need to.... but please don't post like this... and don't use different guides or you will be stuck (as your heading stated..)
Forget everything you knew. Close all other tabs and use this guide thoroughly for Reference:-
https://forum.xda-developers.com/zenfone2/general/guide-fix-bricked-ze550ml-ze551ml-usb-t3405840
j4y_ha said:
Hello all,
I'm stuck in different guides on what to do next.
Problem: Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13.
Also had charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
Tried:
- Factory reset in TWRP -> didn't work (the occasion I did get into CM13 it showed the setup again, so the reset actually went through, but loops still exist).
- When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
- When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
- Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC.
-> Problem: Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
- Another problem: When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.
So now im a bit stuck on what to try next to solve everything and get myself back into CM13. CM13 has ran since Feb '16 and have been a happy user since then until now.
Thanks for reading!
Click to expand...
Click to collapse

Wow @ryankabir
one step at a time hey
xFSTK is used to bring temp bootloader to hard bricked devices .
He has stock LP bootloader and all avenues to repair should be explored first
If anyone needs to unbrick , there is a thread in my signature below ,shows how to go from complete brick , to restoring serial number and into system within 15mins

Thank you for your thourough answer Ryankabir! Much appreciated. My answers are below. I will try your suggestions soon.
ryankabir said:
DUDEE
that's not a problem.. THAT's like 20 different problems... I bricked the living crap out of my zen the day I bought it (because me = smartypants did not know that the MM boot unlocker is nonexistent so I just tried to root and update from my head using older techniques) and... the XTS tool thingy fixed it..
Don't get me wrong, i want to help but this is the problem that I feel little frustrated with..
Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13. ## (but it boots sometimes and goes into TWRP, so you have an easy fix to just revert to stock lollipop... why haven't you done that? You sound like you know what most of this stuff does...
Click to expand...
Click to collapse
Yes I do know what I can do with it, but it just so complicating as there are different factors like the loops, not being able to get connections with USB. I mean, it is not totally bricked since sometimes I can get into TWRP or bootloader.
ryankabir said:
Charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
## how do you connect this battery issue to your occasional bootloop? Check hardware or firmware and definitely use different threads.. there's no way these are all part of the "same problem"...
Click to expand...
Click to collapse
Well, since the phone worked fine before the battery issue, there is some sort of link between the issues I would think. Maybe I've broken some hardware during the battery removal or did the booting into charging mode and on/off continously corrupt some memory leaving me with weird crashes & loops.
ryankabir said:
When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
## Same answer as above - this is unrelated to #2 and unrelated to #1 - is your TWRP the correct one? I mean... did you just maybe flash TWRP version 4000 Modified Alpha for Google Glass??? LOL
Click to expand...
Click to collapse
Although I'm not sure if I have the correct TWRP, it did flash CM13 correctly back in FEB 2016 and haven't found a need to update it ever since as it worked fine during the occasional update...
ryankabir said:
When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
## Is D2W there? "DoubleTap2Wake" ? Are you sure you have a good touch? (this maybe 20% sounds related to your TWRP touch going crazy..)
Click to expand...
Click to collapse
No, D2W is not there. The phone is totally unresponsive to the power button as well as D2W. When in TWRP the touchscreen functions fine until it freezes at some random moment.
ryankabir said:
Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
## There's this awesome invention called DRIVERS... and we're lucky in this case (cuz I bricked an hour after I bought it) because Intel PC + Intel Phone = Yay... There is even.... a very specific "INTEL ASUS WINDOWS DRIVER" file... from the INTEL AND ASUS WEBSITE... or maybe your USB CABLE is f**? My point is... another unrelated issue where it sounds like you've not even tried it properly before complaining.. I like helping people. I don't like when people refuse to try or they skip the actual study-notes to do it... I used the EXACT same guide to unbrick and it worked in 2 mins... I'm on a 2007 Laptop which overheats if I use 4 tabs... how am I able to follow the exact same guide on a brand new "FULLY BRICKED" phone... it literally would vibrate after trying power button for 5 mins and be stuck in a "blank black screen" for hours and hours... No twrp no nothing.. and I did it - why didn't you? Same guide man...
Click to expand...
Click to collapse
Yes I know what drivers are :good: - I've tried IntelSoc, Intel ASUS etc... all drivers that are somewhere mentioned I have installed. Before the charging problem I was able to connect the phone and access files fine as well.
ryankabir said:
When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.)
## Try again. Sometimes people accidentally hit power to early.. or whatever.. It's not a MK2 Fatality.. don't force yourself to get it exact.. Let the menu pop up... just wait a second and scroll up/down just to see if that works... then scroll to Boot-Recov and gently hit power+vUp.. should be fine.. otherwise just .. literally try 10 times.. it WILL work.
Click to expand...
Click to collapse
Thanks, will try more!
ryankabir said:
Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC
## Nope.. TWRP is like Bret Hart. It isn't unstable. Not for LP not MM not for N. Not for Stock Not for CM Not for AOSP. You *wanted* to do what you should have done right at the beginning but you didn't get that done properly (see below)
Click to expand...
Click to collapse
TWRP is indeed fine and stable! However, it freezes and reboots my phone so in my particular situation it is currently not stable. Therefore the need to completely wipe the phone and start from fresh.
ryankabir said:
Essentially you have 8 different unrelated issues (and the biggest one is not reading guides, not trying hard enough and just thinking that people like me sit around and get paid for this)... and want ans in one place w/o just doing the simple thing of going back to everything stock...?? *it's just annoying cuz people who want to help will feel like.... others don't even try simply because we exist and have desire to help...* - I am not trying to offend you but I hope you get my pov.
Click to expand...
Click to collapse
Appreciate your POV. I know how it feels like if people ask for help for something they could have read easily somewhere. I'm thankfull for all the guides that people have written on here! I'm asking for help because in my situation the guides are not working and would like to have a full clean wipe of my phone and fix all possible software issues before trowing away the phone because of hardware fault.
ryankabir said:
Do This EXACTLY
#Buy a cable. Borrow a cable. Whatever you do be 1000000% sure the USB Cable is fine
#Install Intel Asus Android drivers from official EXE (google it... don't add new post for that link)
AND THEN
Follow the same Unbrick guide word for word *but* just pay close attention to these:-
IntelSeC Driver + device detected even if OFF (start>devman>showall>intelsec
In the official unbrick utility make sure you're on the second tab at the bottom
In settings check that your device flag is 0x08..... whatever instead of the default 0x000
Back in the *second tab at the bottom* (i don't remember exact name but it's in the guide) -- put the right files (mentioned in guide) in the right boxes.. (mentioned in guide) and remember you ONLY need the DVFWthingy... + TOKENthingy + IFWthingy
Plug the Zen in... hear the "da-dumm" sound... keep looking at the Unbrick tool.. and the moment you see Device Detected = 1 you hit install/start...
AFTER that is fully done *(and if you fail don't post just repeat from scratch)... I don't personally recommend Asus Flash tool it was acting dodgy for me but instead grab the RAW Stock... Rename it to zip.. open it and grab the img files and fastboot flash the fastboot droidboot.img + splashscreen splash.img + boot boot.img + recovery recovery.img
If you've followed all that from the guide and double checked what I've put up there.. you should be fine if you just fastboot reboot bootloader... and go into stock recovery... install zip/update and put your stock OS in there..
Done.
Just please take my advice and don't skim through guides, don't think you don't need to read something, don't click stuff without double checking every line from guide, print it out on PAPER if you need to.... but please don't post like this... and don't use different guides or you will be stuck (as your heading stated..)
Forget everything you knew. Close all other tabs and use this guide thoroughly for Reference:-
https://forum.xda-developers.com/zenfone2/general/guide-fix-bricked-ze550ml-ze551ml-usb-t3405840
Click to expand...
Click to collapse
Thanks for the suggestion and will try this!
timbernot said:
Wow @ryankabir
one step at a time hey
xFSTK is used to bring temp bootloader to hard bricked devices .
He has stock LP bootloader and all avenues to repair should be explored first
If anyone needs to unbrick , there is a thread in my signature below ,shows how to go from complete brick , to restoring serial number and into system within 15mins
Click to expand...
Click to collapse
I've tried your guide but I still have been unable to get a connection with ASUS Flashtool. The phone does keep itself relatively stable in bootloader (don't know what fixed it) - I am able to cycle through normalboot, recovery options etc without it crashing. The bootloader shows "Continue the fastboot process". I have tried different drivers, while rebooting between install/uninstall of drivers.
Thanks again all for the help

@j4y_ha
Goodluck

timbernot said:
@j4y_ha
Goodluck
Click to expand...
Click to collapse
Right m8 , we gonna fix your phone .
Do not stray from this guide.
Stick to it and you will be more the wiser when you have finished .
1 boot to boot loader ...scroll to 'power off ' and select it.
2 Connect your phone to wall charger ...let it charge till full.
When that's done , we ready for next step

timbernot said:
Wow @ryankabir
one step at a time hey
xFSTK is used to bring temp bootloader to hard bricked devices .
He has stock LP bootloader and all avenues to repair should be explored first
If anyone needs to unbrick , there is a thread in my signature below ,shows how to go from complete brick , to restoring serial number and into system within 15mins
Click to expand...
Click to collapse
Just a bit curious what the smileys in line 1 and 2 actually meant.. any hidden snarkasm these?
As for the LP stock BL he has.. after reading through the various (and really insane bugs)... I do not agree with your suggestion to explore all avenues to repair... - and my reasoning for that is... because he got stuck and paralleled different guides... i can understand the urge to have one full fix instead of going all from empty... but i'm basically thinking that if he has put in CM13 then that guide has one Unblock BL (via MMBL) - we can't be sure which one he used (downgrade to LP, unlock then upgrade etc)... + tinkering with TWRP again was it the same twrp thats with CM13.. no way to be certain
So essentially he could be fixing it al but we often totally overlook TX " RR... becausee his type has ben Mania
Cons:
Cant really tell what v BL he has.. and maybe you can try all fixes menrion
£ not a nassuve breakast
I'll try a pros/cons thing...
Pro
Th XT tool as we both said phenoenal (including prerequisites), I am assuming your footer contains the same line I pasted?
Also with his touch screen and semi-sleep state etc - could cause someone to get a permanent bootloop
There could be other mods / zips which simply outwrite each other ldurng etcs.. Now the way you're suggesting... lets say I do that.. how which one touches which sys etc would just
Con
There is defin

Mmbl came about around July 16, he run cm 13 Feb 16.
.173 or .177 is unlocked or locked LP Boot loader.
xFSTK is to gain temp Boot loader.
He gets recognised in fastboot.
He can flash stock recovery .
He can sideload .
.
.
But
Can he ?
That's not sn ide btw

Well I'm not gonna dig too deep into the twrp touch issues (there could be conflicting drivers or even something weird i noticed in twrp302 anything below 20% batt (or if batstats corrupt) then the touch goes craycray.. so lets ignore that..
this thread is getting too heavy i won't have time - so - you can always backup ur data partition so no worries there.. nothing to lose..
one problem at a time.. as I said in first post my phone was bricked much worse i had mismatched fastdroidboot and bootimg and after pressing power on maybe 4-5 times.. it would only turn on once.. sometimes on and immediately off... sometimes on stuck on logo.. sometimes on and no logo but screen is black (corrupt splash)..
so lets just try to go baaaaaack to the futureeeeeee ... Ok I found the script I made (after 8 hours of trying EVERY combination from different guides I just took individual components and made my own.. ) -
I'm writing this in a hurry so please use my first reply to get the XFTS Ubrick Guide for the Files + get the LOLLIPOP One Click BL Unlock + Lollipop Raw image... Their Guide wants you to use Asus Flash but that program failed me every time... so I have got a differnt way to do it..
I'm copying this directly from my own script (so you can change if any paths/names different)... but do not change the order or sequence
Using OneClick (keep the unlock1234 files saved separately for later use)...
If you have these unlocked I just say do it again anyway - no harm...
Unlock Bootloader for LP Stock (even if you have MM you must downgrade by this same method)
Code:
#flash old droidboot for LP stock Bootloader
fastboot flash fastboot droidboot_2_20_40_197.img
fastboot reboot-bootloader
# must run reboot bootloader once with this droidboot before continuing - dn't skip this
# unlock bootloader (use files provided inside oneclick tool but instead of using their script, manually do it - more reliable)
fastboot oem start_partitioning
fastboot flash /tmp/start.sh tools/unlock1
fastboot flash /tmp/recovery.launcher tools/unlock2
fastboot flash /system/bin/logcat tools/unlock3
fastboot flash /tmp/unlock tools/unlock4
fastboot oem stop_partitioning
#if you get failed/error at oem stop - reboot to Bootloader (VOLUP+Power long press -
Release power at Asus Logo or long vibration) and re-do the last step
#if all done so far
fastboot reboot-bootloader
#white Asus logo means unlocked loader
fastboot flash recovery twrp3.img
reboot-bootloader
#toggle Up to choose Recovery - quick tap VOLUP+Power
#twrp will start
install Custom_MM_Rom.zip
#likely it will fail giving IFW 7 error - (intentionally did NOT put MM BL here), so
install Asus_MM_WW_420_184.zip (stock on stock only)
#let it be fully done, verify working MM stock OS
#check if it works - *sign* test your touch screen quickly and in dev tools Keep Debugging ENabled
#then power off - or if you have more options directly choose reboot
#during reboot vibration hit VOLUP+P to Fastboot
####RE-DO Entire first half again
fastboot flash fastboot droidboot_2_20_40_184.img
fastboot reboot-bootloader
# must run once with this droidboot before continuing
# unlock bootloader
fastboot oem start_partitioning
fastboot flash /tmp/start.sh tools/unlock1
fastboot flash /tmp/recovery.launcher tools/unlock2
fastboot flash /system/bin/logcat tools/unlock3
fastboot flash /tmp/unlock tools/unlock4
fastboot oem stop_partitioning
fastboot reboot-bootloader
#now only flash certain MM files (the rest should already be there from stock upgrade) - if you have different MM Img (if they release new one in future - all readers just need to ensure the TOKEN DNX IfW matching)
${FASTBOOTBINARY} flash splashscreen tools/splashscreen_551.img
fastboot flash token tools/bom-token_ze551ml_4_21_40_134.bin
fastboot flash dnx dnx_ze551ml_4_21_40_134.bin
fastboot flash ifwi ifwi_ze551ml_4_21_40_134.bin
fastboot flash fastboot droidboot_4_21_40_134.img
fastboot reboot-bootloader
#should now see black splashscreen + little red error msg for 2 seconds
#entering twrp again by toggling Recovery-> VOLUP+P
install superuser.zip
wipe cache + data
install yourcustomROM.zip
ryankabir said:
Just a bit curious what the smileys in line 1 and 2 actually meant.. any hidden snarkasm these?
As for the LP stock BL he has.. after reading through the various (and really insane bugs)... I do not agree with your suggestion to explore all avenues to repair... - and my reasoning for that is... because he got stuck and paralleled different guides... i can understand the urge to have one full fix instead of going all from empty... but i'm basically thinking that if he has put in CM13 then that guide has one Unblock BL (via MMBL) - we can't be sure which one he used (downgrade to LP, unlock then upgrade etc)... + tinkering with TWRP again was it the same twrp thats with CM13.. no way to be certain
So essentially he could be fixing it al but we often totally overlook TX " RR... becausee his type has ben Mania
Cons:
Cant really tell what v BL he has.. and maybe you can try all fixes menrion
£ not a nassuve breakast
I'll try a pros/cons thing...
Pro
Th XT tool as we both said phenoenal (including prerequisites), I am assuming your footer contains the same line I pasted?
Also with his touch screen and semi-sleep state etc - could cause someone to get a permanent bootloop
There could be other mods / zips which simply outwrite each other ldurng etcs.. Now the way you're suggesting... lets say I do that.. how which one touches which sys etc would just
Con
There is defin
Click to expand...
Click to collapse