Develop Bugs

[Q] Recovering from unusual boot loop

Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.

jenic said:
Let me preface this by saying yes I know there are dozens if not more threads on boot loop problems. I have recovered from boot loops before. This is very different.
I rooted my incredible with unrevokedForever and had cyanogen 6 on it. Everything was fine until yesterday I woke up to it in a boot loop, but not the cyanogen boot animation, the white HTC Incredible screen. I can only get to HBOOT, once I try to enter recovery, use an update.zip, or anything after the HBOOT page it goes into its loop. Should I pursue the RUU and find a windows computer or will that not help me?
I think I may have to bite the bullet and buy a new phone. As obviously they will not replace an S-OFF phone. Any help is appreciated.
Click to expand...
Click to collapse
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.

RMarkwald said:
As long as you can still get into HBOOT and Recovery, you should be okay. Your best bet is to get the RUU and go back to stock/s-on, then re-root/s-off (if you want). I had to do this once, and it's pretty straight forward. Just do a search for Bezerker7's Ultimate Get Back to Stock Thread. It has all the info you'll need on how to do it.
Click to expand...
Click to collapse
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?

jenic said:
The problem is I can only get into HBOOT, not recovery. It would be a fairly simple matter if I had access to recovery features. Would RUU work without access to recovery?
Click to expand...
Click to collapse
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.

RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Your concise post is most appreciated. I will do as you instruct and post results back here when finished.

RMarkwald said:
Looks like you'd need recovery to flash back to s-on first. First you could try flashing a recovery image using fastboot, go here for that information. You'd also need to find a 2.5.x.x recovery image, go here for the 2.5.1.2 image. Don't worry about renaming it, you won't have to do that here like the page says to.
Then, you could go here for instructions on using the RUU to flash back to stock.
Click to expand...
Click to collapse
Hit an unfortunate snag right away. fastboot (nor adb) is detecting the device. Screen is showing XC SHIP S-OFF as it should, it is in FASTBOOT USB mode and my computer detects the USB itself just fine.
dmesg output:
[346853.772041] usb 2-6: new high speed USB device using ehci_hcd and address 17
[346853.922917] usb 2-6: configuration #1 chosen from 1 choice
Click to expand...
Click to collapse
Thank you though that was a great suggestion! (Was very hopeful for a second there

I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.

This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719

RMarkwald said:
I've never used the fastboot command before, but I seem to recall that sometimes my PC's don't report connection from ADB, but I haven't checked recently... Hmmm...
Just checked and it does report a device using ADB. Did you try typing the fastboot command to flash the recovery image file: fastboot flash recovery /path/to/<recovery.img file> anyways to see what happens? I am assuming if it isn't detecting the connection, it may fail...
Click to expand...
Click to collapse
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
RMarkwald said:
EDIT: Did you pull the battery out, put it back in and try to get into recovery again? If you, try doing a user/factory reset + dalvik cache before trying to install a ROM from your SD card.
Click to expand...
Click to collapse
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
cf9182 said:
This may or may not help, but I had a similar issue of not having the phone recognized by fastboot while playing with a friends EVO Shift. I was able to use the program described in this thread to uninstall all HTC drivers. Then, when the phone was recognized and new drivers installed automatically, fastboot worked as expected.
http://forum.xda-developers.com/showthread.php?t=532719
Click to expand...
Click to collapse
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.

jenic said:
My ADB daemon would always recognize it in the past, when the phone was working. Yes I tried the command anyway, even though fastboot devices did not return anything. It hung there waiting for the device to be connected.
Yes, I pulled battery out multiple times, and when installing the rom I factory reset, cleared dalvik and normal cache through Clockwork. Cyanogen was working fine for weeks, this is a freak concurrence that happened without warning. I woke up to find it this way, or rather, it woke me up with its constant rebooting. lol.
I appreciate the help however I am using Linux, and that seems to be a windows issue. I have not had issue detecting the device until this problem arouse. The sentiment is of course appreciated though, please do not feel that I am ungrateful! You have both been very supportive. I think I have just about resigned to dump money on a new phone. This time I will leave it stock for awhile and see if this occurs a third time.
Click to expand...
Click to collapse
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.

jaba14 said:
This happened to me and many other people. It has nothing to do with the fact that you rooted as my replacement from verizon did the same thing even before I rooted. Finally on my 2nd replacement (my 3rd DINC), it has stopped happening.
You're going to have to take it to the store. The guy who looked at my phone looked right at the HBOOT (where it says s-OFF) and then said "we're going to have to send you another one."
So you may get lucky. Your other option (if you're nervous about the store seeing the s-OFF) is just to call Verizon and ask them to send you a replacement. My experience has been that the folks in the Verizon store have no idea what the f they're doing, and you'll probably be just fine taking it in.
Click to expand...
Click to collapse
That was definitely a laugh. Thank you I will see if I can get it replaced! I've been kinda just ignoring the fact that I do not have a phone all this time... Thankfully I had setup the phone to forward calls to google voice. It has been a lifesaver.

[Q] What do I do if I can't get into Recovery?

I was flashing a TrickDroid ROM just now, having had Jellytime 17.1 previously. I did a full backup and full wipe before attempting to flash the TrickDroid ROM.
I got distracted during the process, and when I came back to my phone, it was showing the Jellytime boot animation, but never gets to the UI.
OK, so I figure I can hold the power and volume down button and get into recovery. Nope. When I try to select Recovery from the boot loader, it doesn't do anything at all.
Am I hosed up for good here?

When you get into hboot does it do the normal check? After that it should let you choose.
If that doesn't work try pulling the battery for a few minutes and try again.
If you have adb you can type:
adb reboot recovery
Sent from a dream.

Teichopsia said:
When you get into hboot does it do the normal check? After that it should let you choose.
If that doesn't work try pulling the battery for a few minutes and try again.
If you have adb you can type:
adb reboot recovery
Sent from a dream.
Click to expand...
Click to collapse
It does do the check. When I select "recovery" or "factory reset", it just comes back to the bootloader menu without doing anything.
Mike

TheImpalaKid said:
It does do the check. When I select "recovery" or "factory reset", it just comes back to the bootloader menu without doing anything.
Mike
Click to expand...
Click to collapse
Perhaps you need to re-flash a recovery but let's wait for someone to double check and confirm.
But then you get the same issue with factory reset (which you shouldn't do).
Sent from a dream.

If it goes into the bootanimation then you can use ADB. Connect the phone to pc and let it go into the bootloop and then use "adb reboot recovery" from the command line on your pc.
If it stil doesn't work then you'll need to reflash your recovery. Download a recovery image like ClockWorkMod, go into bootloader while connected to pc. It should show "Fastboot USB" on the bootloader screen. Then use ""fastboot flash recovery [name of the image.img]" to flash a new recovery.
Try going into recovery again and see if it helps.

Teichopsia said:
Perhaps you need to re-flash a recovery but let's wait for someone to double check and confirm.
But then you get the same issue with factory reset (which you shouldn't do).
Sent from a dream.
Click to expand...
Click to collapse
I tried removing the battery for about 10 minutes, and then tried getting into recovery. The same thing happens when I select "recovery".
I let it sit for about 40 minutes with the JellyTime boot animation running, hoping it would complete, but it never did.
I guess AT&T can reflash it but then I'll have to root it again. I guess that's better than losing the whole thing.
Mike

Its strange though.. flashing a ROM doesn't tamper the recovery partition so it shouldn't have happened.
---------- Post added at 11:26 PM ---------- Previous post was at 11:25 PM ----------
TheImpalaKid said:
I tried removing the battery for about 10 minutes, and then tried getting into recovery. The same thing happens when I select "recovery".
I let it sit for about 40 minutes with the JellyTime boot animation running, hoping it would complete, but it never did.
I guess AT&T can reflash it but then I'll have to root it again. I guess that's better than losing the whole thing.
Mike
Click to expand...
Click to collapse
You won't need to give it to AT&T.. just run an RUU and root it again if it comes to it.

Just do what the previous member suggested. You both posted at the same time so you might not have seen it.
Sent from a dream.

Teichopsia said:
Just do what the previous member suggested. You both posted at the same time so you might not have seen it.
Sent from a dream.
Click to expand...
Click to collapse
Thanks, I hadn't seen that other reply.
I have been flashing ROMs for about a year, and had never run across this problem. I've never had anything happen that messed up recovery until now.
I will try this when I get home from work today. Thanks to both of you for the help and suggestions.
Mike

TheImpalaKid said:
Thanks, I hadn't seen that other reply.
I have been flashing ROMs for about a year, and had never run across this problem. I've never had anything happen that messed up recovery until now.
I will try this when I get home from work today. Thanks to both of you for the help and suggestions.
Mike
Click to expand...
Click to collapse
Ofcourse.. and It shouldn't have happened. ROM's don't mess with the recovery. Even if anything happened during flashing the ROM the recovery partition should not be affected. This is a strange situation indeed.. should be brought to attention of the 4ext recovery developer...

if4ct0r said:
Ofcourse.. and It shouldn't have happened. ROM's don't mess with the recovery. Even if anything happened during flashing the ROM the recovery partition should not be affected. This is a strange situation indeed.. should be brought to attention of the 4ext recovery developer...
Click to expand...
Click to collapse
I thought it was pretty weird, too. I've flashed ROMs a ton of times with no problems.
I am using ClockworkModRecovery.
Mike

TheImpalaKid said:
I thought it was pretty weird, too. I've flashed ROMs a ton of times with no problems.
I am using ClockworkModRecovery.
Mike
Click to expand...
Click to collapse
Oh.. my bad. I thought I read that you use 4EXT.. :silly:
In anycase.. All is well and solvable if you can reach the bootanimation Just use ADB.

if4ct0r said:
Oh.. my bad. I thought I read that you use 4EXT.. :silly:
In anycase.. All is well and solvable if you can reach the bootanimation Just use ADB.
Click to expand...
Click to collapse
I guess... I can't get my laptop to recognize the phone or load any drivers for it. So when I try to run adb, I get no devices.
I have a teenage son who I may sic on this problem.
Mike

You have HTC Sync installed? You have ADB as well? Make sure you have it installed. It installs connectivity drivers for your phone.
If you're indeed getting into bootanimation your phone should be recognized by ADB. After installing HTC Sync, try running "adb devices" if it shows no devices try running "adb kill-server" and then "adb devices" again. If all drivers are correctly installed it should recognize your phone.

Tips: You can get adb by running the advanced ace hack kit once

Update
My two sons were able to finally get the phone reset to factory spec sometime last night. :victory: So I'll have to re-root the phone and then I can restore my ROM from the backups.
One weird thing... the speaker/microphone doesn't work now. This is no big deal as I rarely receive or make calls.
I'm probably not your typical Android user in that I'm 55, and I love to try out the different ROMs that are available. Favorites are BlackIce, Trickdroid, and JellyTime.
Most of my peers have some sort of iPhone and really don't care anything about behind-the-scenes or jailbreaking, etc.
Thanks to everyone who's offered help and information.
Mike
TheImpalaKid

HELP! Phone bricked?? Phone keeps rebooting into CWM

So i had lifeless rom on it and everything was perfect and decided to the shutter sound mod to remove the sound when taking the picture. I accidentally changed the permission on the system side, and now the phone froze so turned it off. and turned it back.. When i power it on after 5 sec it'll go into CWM. i tried factory reset, wipe cache, davik etc... I dont have the lifeless rom on the sidecard section
What should I do..??

HelloDominick said:
So i had lifeless rom on it and everything was perfect and decided to the shutter sound mod to remove the sound when taking the picture. I accidentally changed the permission on the system side, and now the phone froze so turned it off. and turned it back.. When i power it on after 5 sec it'll go into CWM. i tried factory reset, wipe cache, davik etc... I dont have the lifeless rom on the sidecard section
What should I do..??
Click to expand...
Click to collapse
ba boop http://forum.xda-developers.com/showthread.php?t=2082084

javskies said:
ba boop http://forum.xda-developers.com/showthread.php?t=2082084
Click to expand...
Click to collapse
Yeah im stuck on this part as well. I downloaded the SDK from the link he provided
Able to run CMD and go to cd/Users/XXXX/Desktop
but when i go into my phone I don't see TWRP or idk how to get into it, all i see is CWM, but i did a section where it says sideload to internal.so i ticked that and got "Now send the package you want to apply to the device with "adb sideload" So im like this might good so far
I go back into the PC and type in the command "adb sideload the filename of "adt-bundle-windows-x86_64.zip" but i get i get "adb" is not a recognized as an internal or external command.
ughh

HelloDominick said:
Yeah im stuck on this part as well. I downloaded the SDK from the link he provided
Able to run CMD and go to cd/Users/XXXX/Desktop
but when i go into my phone I don't see TWRP or idk how to get into it, all i see is CWM, but i did a section where it says sideload to internal.so i ticked that and got "Now send the package you want to apply to the device with "adb sideload" So im like this might good so far
I go back into the PC and type in the command "adb sideload the filename of "adt-bundle-windows-x86_64.zip" but i get i get "adb" is not a recognized as an internal or external command.
ughh
Click to expand...
Click to collapse
i actually never read this guide lol i think youd be better off doing lgnpst. you dont have twrp because you have cwm. do the same thing, different programs. if you want i can pm you the files to lgnpst back to stock and then from there just reroot and unlock again.

javskies said:
i actually never read this guide lol i think youd be better off doing lgnpst. you dont have twrp because you have cwm. do the same thing, different programs. if you want i can pm you the files to lgnpst back to stock and then from there just reroot and unlock again.
Click to expand...
Click to collapse
yess pleaseee trying to get the phone back up for tomorrow.. got like 5 meetins tomorrow stupid me for messing my camera sound permission

HelloDominick said:
yess pleaseee trying to get the phone back up for tomorrow.. got like 5 meetins tomorrow stupid me for messing my camera sound permission
Click to expand...
Click to collapse
pm'd!

For future reference to all, when you've stuck booting into recovery you just need to wipe the first part of your misc. I have a zip in the irc topic for it, ill link when I get home. Or you can just run the following in an adb shell
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc count=1044 bs=1
Sent from my LG-LS970 using xda app-developers app

Solved!
Try this:
All you have to do is revert to an older version of clockworkmod, I used version 6.0.12 I believe.
the file name is: CWM6012-CM9-recovery so it might be that. Yep that's it, now i can finally rest
Thanks Byrkoet
http://forum.xda-developers.com/showthread.php?p=39067132#post39067132

I have the same problem, I keep getting my phone to the clockworkmod recovery every time the reboots. I need my phone in the morning. Can someone please help me to try fix this. I'm really panicked and worried.:crying:

[Q] Need help fixing my Gnex

Hi,
it is the second time my Gnex went into endless reboot loop sessions.
It will boot, load crash after few seconds and reboot again.
I had it unlocked in the store i bought it, and had stock rom (Not sure about the version).
Tried to do factory reset from fastboot, from recovery, and from android. Also tried to flash custom boot loader, Nothing works.
Although fastboot writes it successfuly completed the action so does the factory reset. The phone will work for few seconds but no more.
Also tried using WugFresh, for factory reset and for Flash Stock + unroot in soft-break status
I have no ideas what to do next,
Please help.
Mike

Hi Mike, I think more information is required.
- What action did you take immediately prior to having your phone get stuck in the bootloop? Were you trying to install a Custom Recovery or ROM?
- You mention that this is the second time this has happened. Do you know what caused it to bootloop the first time, and if yes what fixed it?
- When your Gnex is in Fastboot/Bootloader mode, and using a tool like Minimal ADB and Fastboot on your computer, does the tool recognize the Device ID after using the fastboot devices command?
You may also want to read through this thread.

AvidPhisherman said:
Hi Mike, I think more information is required.
- What action did you take immediately prior to having your phone get stuck in the bootloop? Were you trying to install a Custom Recovery or ROM?
- You mention that this is the second time this has happened. Do you know what caused it to bootloop the first time, and if yes what fixed it?
- When your Gnex is in Fastboot/Bootloader mode, and using a tool like Minimal ADB and Fastboot on your computer, does the tool recognize the Device ID after using the fastboot devices command?
You may also want to read through this thread.
Click to expand...
Click to collapse
Hi thanks for the reply, i am a simple user, prior to the bootloop i was using whatsapp, actually the android crashes few seconds after getting a whatsaap message (i recieve notification and it goes down). Previous time also i didn't do anything special. i never installed custom recovery or roms... previous time it was fixed by a lab the phone was on warranty.
And yes the tool recognize the device.

So your device receives a WhatsApp message/notification, restarts, and then gets stuck in a bootloop?
That is very strange, as personally I've only ever encountered bootloops after bad ROM flashes (usually after I accidentally skipped a step somewhere during the process). Bootloops usually don't happen to regular users who are just using their phone purchased as-is from a store/carrier.
If you can get it to boot back into Android, try uninstalling WhatsApp and see if that helps. Hopefully it's still under warranty, as you may have to take it back to the store and have them look at it.

AvidPhisherman said:
So your device receives a WhatsApp message/notification, restarts, and then gets stuck in a bootloop?
That is very strange, as personally I've only ever encountered bootloops after bad ROM flashes (usually after I accidentally skipped a step somewhere during the process). Bootloops usually don't happen to regular users who are just using their phone purchased as-is from a store/carrier.
If you can get it to boot back into Android, try uninstalling WhatsApp and see if that helps. Hopefully it's still under warranty, as you may have to take it back to the store and have them look at it.
Click to expand...
Click to collapse
Tried to uninstall whatsapp but it crashes before i manage to do so.
even managed to access memory via TWRP and delete whatsaap manually but somehow it appears again after restart.
Something is terribly wrong

Have you tried using Odin to repartition and restore to stock? Could be a corrupted partition. Check out this guide

nthnlee said:
Have you tried using Odin to repartition and restore to stock? Could be a corrupted partition. Check out this guide
Click to expand...
Click to collapse
Why???
Just use fastboot, Odin is evil. Nexus aren't Touchwiz crap phones.

beekay201 said:
Why???
Just use fastboot, Odin is evil. Nexus aren't Touchwiz crap phones.
Click to expand...
Click to collapse
When fastboot didn't work. i had to try something else. But, odin didn't work either.

mishkap said:
When fastboot didn't work. i had to try something else. But, odin didn't work either.
Click to expand...
Click to collapse
Let's see then. Be prepared to spend at least 30min reading, and re-reading, until you actually feel comfortable in what you're doing/typing in. If you're not sure about the technical terms and what lies behind them, read this thread's #1 First Post.
What's your device variant? maguro? toro? toroplus? This will tell which factory image you need to flash.
You need to flash latest factory image, which is (for maguro variant) Android Build 4.3 (JWR66Y). Read #1 First Post on this thread. And I mean, READ IT! Do not do anything else to your device until you do.
After you flash the factory image, that first boot will take a while to reach Android. Chill out. Go get yourself a drink. Take your time. It should have booted into Android already when you get back. It should be fine, but if not, you need to enable USB debugging under Settings > Developer Options, to check the system log.
If after 15min, it still has booted yet, pull the battery out, wait a few secs, put it back in.
Use the 3bc (3-button combo) to reach fastboot mode again. Flash a custom recovery. That's done by downloading the latest TWRP or CWM (i'll leave that choice up to you, be mindful that you might wanna try them both in the future), and running on the host (the PC):
Code:
fastboot flash recovery recovery_filename_here.img
Don't reboot the device. Use the volume keys to "Reboot to recovery" straight from fastboot. After a few seconds, you should be seeing the custom recovery you've flashed with the fastboot command above.
Now comes the part where ADB is required. I hope you've already read the answers to questions "Where do I get the driver for my PC?" and "Why do I need to install the driver twice?". If not, read them now. Also, read "What is ADB?". TIP: When a custom recovery is actually running on the device, ADB mode is already active by default, so when hooking up to the pc the device will show as an ADB interface, so installing the driver (if needed/not done yet) is piece of cake.
After you get ADB to recognize your device (like, you see your device's SN on the output of command `adb devices`).. You need to copy a custom ROM to your device, and flash it. That will get you, most likely than not, Android's USB debugging by default (read answer to "What is an insecure boot image?" on the first link), and that will allow you to see the system log, WHILE Android is booting up. Why do we wanna do this? Cos we want to see if any errors show up, something that may tell us what's failing.
When choosing a ROM from the Android Development section, ask around in the thread if the ROM has USB debugging enabled by default.
Read "What are the ADB commands?" in the thread I first linked to. You'll need to learn at least `adb push` for now.
Once you get the ROM in your /sdcard/ or whatever folder you like, disconnect the USB cable, wipe data/factory reset, then install zip from sdcard (that zip you pushed before).. Forget about gapps for now.
Connect the usb cable, reboot, and once you see padlock screen go away, start trying to run `adb devices`. Do you see your SN in the output? Once you see it, good, it already connected to adb on the device. Run `adb logcat` and try to look out for errors. Logcat is the system log.
To know how to grab that output to a text file so that you can share it with us.. Google it, my fingers hurt.

Thanks beekay201,
As a matter a fact. shortly before you posted this answer i gave up and gave my phone to a local lab.
But unfortunately they were useless and didn't manage to do anything claiming they don't have spares for my phone, tried to explain that it is not a hardware issue, but all in vain .
Anyway, ill go over your instructions and ill update the results soon.

Can someone please help me

I was trying to update my phone and something most likely went wrong. Then the update installed and screwed up my phone. When I turned it on it stayed on the startup for so long. I tried to clear cache through the bootloader, but now it shows the android screen of death except it flashes. This occurs even outside the bootloader.
I am rooted with stock os.
Thanks in advance to whoever helps

Flash it with the original firmware

anfalanl said:
Flash it with the original firmware
Click to expand...
Click to collapse
Yup, same thing happened to me, I had to reflash it to stock firmware.

How would i flash
Magister54 said:
Yup, same thing happened to me, I had to reflash it to stock firmware.
Click to expand...
Click to collapse
Hey, thanks for the response.
Could you please elaborate on how I would do this. Because I do not understand how to do this if the bootloader doesn't work.
Thanks, your response and input means alot

Take the firmware from Asus website, for me I took UL-Z00A-WW-2.19.40.22-user.zip
Boot the phone in bootloader and try to go in the recovery screen, it took me a lot of tries to get in it!!!
From here you can select "insall update from ADB"
From your PC you do a "adb sideload UL-Z00A-WW-2.19.40.22-user.zip"

Magister54 said:
Take the firmware from Asus website, for me I took UL-Z00A-WW-2.19.40.22-user.zip
Boot the phone in bootloader and try to go in the recovery screen, it took me a lot of tries to get in it!!!
From here you can select "insall update from ADB"
From your PC you do a "adb sideload UL-Z00A-WW-2.19.40.22-user.zip"
Click to expand...
Click to collapse
When i try to do this, i see the error sign but it is flashing

hudasameer450 said:
When i try to do this, i see the error sign but it is flashing
Click to expand...
Click to collapse
That's normal. When you get the error sign when booting into stock recovery, hold power down and press volume up and quickly release both buttons at the same time. If done correctly recovery menu will pop up and then you can start actually flashing.

Flashing
does this still work if the screen is flashing, because I tried before and it did not work, maybe I pressed it wrong or there is some other issue.
Thanks