Database Users

[Q] flashing problems, stuck on the same rom(Solved!)

Hey Guys, I first tried searching to see if anyone else had the issue but i couldnt find any related threads. I am currently running either turl's or joxersax11's CM9 rom. The problem is when i try to install a different rom (take gingerblur for example). Ive tried installing new roms by both rom manager and directly through CWM (and I have been clearing my data/caches/dalvik) , but upon first boot after the flash, the loading screen is still the CM9 animation (the one with the rainbow tiles flpping over) and when Android loads up, I'm still on CM9. What am I doing wrong? Is there a better way to wipe my phone or flashing roms?
Thanks for your help

Erase system and boot using fastboot commands.
fastboot erase boot
fastboot erase system
fastboot erase userdata

reboot to recovery
wipe dalvik
wipe cache
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
That'll do it!

thanks guys, im waiting for my battery to charge to get into fastboot. How often should i erase these things in fastboot? Every flash? Or just whenever something is broken?

Ubers said:
thanks guys, im waiting for my battery to charge to get into fastboot. How often should i erase these things in fastboot? Every flash? Or just whenever something is broken?
Click to expand...
Click to collapse
When ever you flash a new rom. If you're just updating a never version of the same rom, usually you don't have to fastboot wipe, unless you have a problem.

Long story short... I soft bricked my phone. My phone won't boot past the Motorola dual core screen. I can boot to cwm, fastboot, rsd. The gingerblur rom is flashable from inside cwm, but it doesn't want to boot to boot after flashing. How do I get out of this mess? I'm not very familiar with flashboot or RSS, or sbf files but I'm sure I could use them if I had baby step instructions.

Ubers said:
Long story short... I soft bricked my phone. My phone won't boot past the Motorola dual core screen. I can boot to cwm, fastboot, rsd. The gingerblur rom is flashable from inside cwm, but it doesn't want to boot to boot after flashing. How do I get out of this mess? I'm not very familiar with flashboot or RSS, or sbf files but I'm sure I could use them if I had baby step instructions.
Click to expand...
Click to collapse
Gingerblur... Jesus..... Answers needed below:
- Is your bootloader unlocked?
- What/who's recovery are you using?
- What firmware and/or Android version were you running?
- Do you have a micro/ext. sd card?

- Is your bootloader unlocked?
Yes, when I turn on the phone, unlocked appears in the top left corner
- What/who's recovery are you using?
This is the software I get into when I select "android recovery" from the boot menu right? I'm pretty positive its an up to date version of clockworkmod
- What firmware and/or Android version were you running?
Up until a few days ago I had stock 2.3 gingerbread courtesy of at&t. First i tried jokersax cm9 and then i tried turls cm9 most recently before this brick
- Do you have a micro/ext. sd card?
Nope. And to make matters worse I don't believe the SD slot works
Inside your noob guide there is a section titled
WHAT DO I DO IF MY DEVICE WILL NOT FULLY BOOT??? (i.e. Boot Loop or Soft Brick):
This is my predicament right? There is a subsection:
c) If you can boot into fastboot, you can fastboot flash the "stock" 2.3.4 Gingerbread .img/system files by following the instructions on this page:
http://forum.xda-developers.com/show....php?t=1163342
*Note: The .img files to install via fastboot are located under "Download Gingerbread Stock Images" on the download page
Should I try this method?

Ubers said:
- Is your bootloader unlocked?
Yes, when I turn on the phone, unlocked appears in the top left corner
- What/who's recovery are you using?
This is the software I get into when I select "android recovery" from the boot menu right? I'm pretty positive its an up to date version of clockworkmod
- What firmware and/or Android version were you running?
Up until a few days ago I had stock 2.3 gingerbread courtesy of at&t. First i tried jokersax cm9 and then i tried turls cm9 most recently before this brick
- Do you have a micro/ext. sd card?
Nope. And to make matters worse I don't believe the SD slot works
Inside your noob guide there is a section titled
WHAT DO I DO IF MY DEVICE WILL NOT FULLY BOOT??? (i.e. Boot Loop or Soft Brick):
This is my predicament right? There is a subsection:
c) If you can boot into fastboot, you can fastboot flash the "stock" 2.3.4 Gingerbread .img/system files by following the instructions on this page:
http://forum.xda-developers.com/show....php?t=1163342
*Note: The .img files to install via fastboot are located under "Download Gingerbread Stock Images" on the download page
Should I try this method?
Click to expand...
Click to collapse
Try wiping data first in CWM & see if it will boot.
The reason you can't get it to wok with Gingerblur, is b/c that's was for froyo... you might as well delete that .zip.
If you had a micro SD card, you could just stick a fruitcake on it and then flash that.
You might try fastboot installing Rom Racers recovery (see his OP) then installing whatever CM7 or 9 Rom you were trying to install.
As a last resort, you could try fastboot installing that .img file or sbf flashing 4.5.91 sbf... whatever you do don't flash or install a earlier version of the firmware like 1.2.6 or 1.8.3, or you'll hard brick!!! If you go this way, you'll most likely have to unlock your bootloader again.
Sent from my CM7 Atrix 4G

Well i tried it and im back up and running again. Thank goodness for your comprehensive noob guide! It took me a while to track down moto-fastboot but when i found it, it was all smooth sailing!
thanks again

Ubers said:
Well i tried it and im back up and running again. Thank goodness for your comprehensive noob guide! It took me a while to track down moto-fastboot but when i found it, it was all smooth sailing!
thanks again
Click to expand...
Click to collapse
Good to hear!
Sent from my CM7 Atrix 4G

CaelanT said:
reboot to recovery
wipe dalvik
wipe cache
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
That'll do it!
Click to expand...
Click to collapse
I'm not an expert at this but doesn't "fastboot erase boot/system/etc" delete the clockworkmod recovery ? I have flashed cm7 roms before with only wiping the data/cache/dalvik and never had a problem, why is it different now when flashing cm9 ?
Thanks in advanced.

Problem with Partition Table

Hi guys,
I'm experiencing a very big problem with a friend of mine's nexus 4. I've done the same thing in the same order with my phone (nexus 4 too) five minutes before and it worked.
We installed 4.4 stock rom downloaded from official google website via fastboot and all went well on my device. The problem was that we repeated the same identical procedure on my friend's nexus 4 and it went well except for the fact that the phone only had 5gbs available after the flash, so we red on the internet that we had to repeat the procedure using "fastboot -w update" instead of flashing every single file contained in the zip folder.
So it's now that borns the real problem. We've erased all partitions (fastboot erase cache, userdata, system, bla bla) and reflashed all. But from this point it stucks on android 4.4 loading logo.
We've tryied to repeat the operation and we've noticed that "fastboot erase bootloader" command answers with "Failed (remote: bootloader partition does not exist)". So we tryied to install cwm recovery and flash from sideload, it works and loads cyanogenmod logo but stucks on it again, tryied to flash everything possible and it works but after don't start.
The strange thing is that the bootloader appears to not exist but if i do the command: fastboot flash bootloader C:\...\bootloader.img it works and says "writing... OK" so i really don't know what could be the problem.
Please guys help us, my friend is on the point to sell his phone but we both are SURE that if it still can enter on recovery and on bootloader it could be restored!!! But we don't know why! Tryied every possible solution on the web, and nothing worked for now...
Thanks to all in advance!

Install the latest twrp recovery, enter it and go to the wipe menu, chose the format data option. Then give a rom a try.

meangreenie said:
Install the latest twrp recovery, enter it and go to the wipe menu, chose the format data option. Then give a rom a try.
Click to expand...
Click to collapse
Hi, thanks for the answer. Fortunately i've just resolved the problem. It worked after I wiped data from the STOCK recovery (it was the first thing i've done with the cwm several times but unsuccessfully). Now it works perfectly. Thanks again :victory:

fdm91xda said:
Hi, thanks for the answer. Fortunately i've just resolved the problem. It worked after I wiped data from the STOCK recovery (it was the first thing i've done with the cwm several times but unsuccessfully). Now it works perfectly. Thanks again :victory:
Click to expand...
Click to collapse
For future references. Most likely the reason why your phone didn't boot up is because you 'erase' a partition and left it unformatted. The 'erase' command wipe out the partition so no data is there and it can't access it. If you erase userdata, then there would be no accessible internal storage and the phone cannot boot.
Which is why after you erase it, you need to either flash something over it or format the partition to make it blank: fastboot format userdata (this is what Format DATA option in TWRP is).

Help help help with a hard bricked 6P

Hello guys,
I had my phone rooted with latest twrp. I flashed stock+ rom with Franco Kernel 25r and the A.R.I.S.E file for better sound. I've done the same set up minus the ARISE file and never had an issue.
well to my luck it kept bootlooping and I wasn't able to get back into my custom recovery. When I got home and got my hands on a pc I did a factory reset by manually flashing stock google img . I even used a couple tools since I ran out of ideas and still no luck.
I'm able to do anything through fastboot but I can't seem to get into my recovery at all.
Any ideas or tips of where I should go next?

Not a Hardbrick
As long as you can get to the bootloader mode, you haven't hard bricked your device. Hardbricking is a point where you cant boot your device and in to bootloader so there is no way to flash your device to a useable state.
Now as you can boot to the bootloader, just fastboot boot twrp.img and if you have a factory image zip, copy it in your device internal storage and flash it. Its that simple, provided you are already using an unencrypted boot.img in your current setup. Or else the next step is to flash an decrypted boot.img(you will loose all your userdata and internal storage data.). There are ways to mount the the encrypted filesystem if you are using a pin or password combo with your fingerprint. But without it its a bit more trickier so just for ease and if you dont have any inseparable data in your device now just flash a decrypted boot.img and then you can easily mount your internal storage to your pc and copy the factory image and the rest you already know..

At this point, I'd recommend a full reset.
Flash all the images in the latest Android M factory image (don't flash DP5 or similar N based ROMs): Recovery, Boot, System, Bootloader, Radio, everything.
Once you get stabilized and back into a working phone, then start rooting and messing around with kernels and what not.
To be completely honest, I've flashed nearly every ROM for the 6p, as well as my other Nexus devices, Galaxy phones, Sony phones, and no-name brands and none of those ultra modified kernels did any noticeable change. I tried the F2FS, NTFS, etc file system changes, tweaks to the governors and IO's, all of that, and found the stock kernel was the best. If a kernel with a different IO Scheduler worked even 10% better than the current implementation, and was just as stable, don't you think the Google/Android Engineers would've pushed that to live?
Currently running Pure Nexus July 23rd Update, everything stock that comes with it, Systemless Root/XPosed, and Viper4Android and have never had a performance or stability issue. I'd recommend you do the same.

leninmon said:
As long as you can get to the bootloader mode, you haven't hard bricked your device. Hardbricking is a point where you cant boot your device and in to bootloader so there is no way to flash your device to a useable state.
Now as you can boot to the bootloader, just fastboot boot twrp.img and if you have a factory image zip, copy it in your device internal storage and flash it. Its that simple, provided you are already using an unencrypted boot.img in your current setup. Or else the next step is to flash an decrypted boot.img(you will loose all your userdata and internal storage data.). There are ways to mount the the encrypted filesystem if you are using a pin or password combo with your fingerprint. But without it its a bit more trickier so just for ease and if you dont have any inseparable data in your device now just flash a decrypted boot.img and then you can easily mount your internal storage to your pc and copy the factory image and the rest you already know..
Click to expand...
Click to collapse
First of all thank you for the response.
I've tried flashing the most current twrp and it seems to go through fine on fast boot but when I actually try to get into recovery from the device it will boot loop and just keep doing that.
How can I get into the phones storage through fastboot?
Where can I get the factory zip?
it feels as if everything seems to go good through fastboot but when I actually try to boot the phone nothing seems to work.

Wiltron said:
At this point, I'd recommend a full reset.
Flash all the images in the latest Android M factory image (don't flash DP5 or similar N based ROMs): Recovery, Boot, System, Bootloader, Radio, everything.
Once you get stabilized and back into a working phone, then start rooting and messing around with kernels and what not.
To be completely honest, I've flashed nearly every ROM for the 6p, as well as my other Nexus devices, Galaxy phones, Sony phones, and no-name brands and none of those ultra modified kernels did any noticeable change. I tried the F2FS, NTFS, etc file system changes, tweaks to the governors and IO's, all of that, and found the stock kernel was the best. If a kernel with a different IO Scheduler worked even 10% better than the current implementation, and was just as stable, don't you think the Google/Android Engineers would've pushed that to live?
Currently running Pure Nexus July 23rd Update, everything stock that comes with it, Systemless Root/XPosed, and Viper4Android and have never had a performance or stability issue. I'd recommend you do the same.
Click to expand...
Click to collapse
Thanks for the reply.
I've done the manual flashing already and flashed everything single item the most current factory image. Everything seemed to have gone through okay but when I rebooted the phone it was back to 0.
I'm actually considering getting rid of the phone now since it is my daily =/

Format each partition before flashing.
fastboot format <partition>
wait until it's done, then
fastboot flash <partition> <image>
Some partitions can't be formatted, which there are ways around, but try this first.

Just get to bootloader mode and try booting the twrp.img
fastboot boot twrp.img
From the twrp ui, go to advanced wipe and format your storage.
To mount the internal storage on your PC, enable mtp from twrp screen.
If U are using a decrypted boot.img, it will easily mount ur internal storage. Or try flashing a decrypted boot.img
fastboot flash boot boot.img
Then try the above again..

leninmon said:
Just get to bootloader mode and try booting the twrp.img
fastboot boot twrp.img
From the twrp ui, go to advanced wipe and format your storage.
To mount the internal storage on your PC, enable mtp from twrp screen.
If U are using a decrypted boot.img, it will easily mount ur internal storage. Or try flashing a decrypted boot.img
fastboot flash boot boot.img
Then try the above again..
Click to expand...
Click to collapse
I flashed the twrp.img and it went through successfully at least on the computer it did but when the phone actually tries to get into recovery (twrp) it will start to boot loop and keep on doing that. I tried both an encrypted and decrypted boot img but it still made no difference.
I'm really going crazy over this

Wiltron said:
Format each partition before flashing.
fastboot format <partition>
wait until it's done, then
fastboot flash <partition> <image>
Some partitions can't be formatted, which there are ways around, but try this first.
Click to expand...
Click to collapse
I just tried this and had no luck =/....the phone wont get past the google boot screen

You need to explain more on what you actually tried here.
Just download the latest factory image and try to flash the latest bootloader using fastboot.
Then boot to the bootloader and try formating the device. Not wiping
Then you have to
fastboot boot twrp.img
I believe you have only tried wiping not formating. I faced similar issue before. But once I flashed a decrypted boot.img, it cleared the user data and then I was able to get to twrp.
Maybe your twrp img is corrupted if this didn't work.

leninmon said:
You need to explain more on what you actually tried here.
Just download the latest factory image and try to flash the latest bootloader using fastboot.
Then boot to the bootloader and try formating the device. Not wiping
Then you have to
fastboot boot twrp.img
I believe you have only tried wiping not formating. I faced similar issue before. But once I flashed a decrypted boot.img, it cleared the user data and then I was able to get to twrp.
Maybe your twrp img is corrupted if this didn't work.
Click to expand...
Click to collapse
i just flashed the latest bootloader from the most recent factory image and i did the command format user data and then tried the fastboot boot twrp and the phone will then try to get into recovery, the google logo comes up lasts a couple seconds and boot loops all over to where is says my phone cant be check for corruption
By now i should have been able to get into recovery and it wont go through

edgarted said:
i just flashed the latest bootloader from the most recent factory image and i did the command format user data and then tried the fastboot boot twrp and the phone will then try to get into recovery, the google logo comes up lasts a couple seconds and boot loops all over to where is says my phone cant be check for corruption
By now i should have been able to get into recovery and it wont go through
Click to expand...
Click to collapse
download a factory image and run the flash all file...... it should reboot your phone after 5 minutes and the issue should be resolved.. a hard brick would be a device that does nothing.... in this case i believe that you just didnt do something right.

Then download the latest factory image and extract it
fastboot flash radio.img
fastboot flash bootloader.img
& do a fastboot update the rest archive file as it is
This will flash the rom via fastboot& U don't have to rely on TWRP or CWM

i42o said:
download a factory image and run the flash all file...... it should reboot your phone after 5 minutes and the issue should be resolved.. a hard brick would be a device that does nothing.... in this case i believe that you just didnt do something right.
Click to expand...
Click to collapse
I was really really hoping this would help. I erase/formated everything before flashing anything. I then ran the flash-all file and it took a couple of minutes and it said finished on the command box and my phone restarted and went into the white google logo and rebooted again with a bootloop. I waited around 15 minutes hoping it would start but it didn't.
It honestly feels as if the phone is not processing the full commands but on the pc it seems to go through successfully
is there a way to force an install of a rom and see if maybe a dirty flash over the stock one will allow it to start up?

leninmon said:
Then download the latest factory image and extract it
fastboot flash radio.img
fastboot flash bootloader.img
& do a fastboot update the rest archive file as it is
This will flash the rom via fastboot& U don't have to rely on TWRP or CWM
Click to expand...
Click to collapse
i know how to flash the radio and bootloader but how do i do a fastboot update?

edgarted said:
i know how to flash the radio and bootloader but how do i do a fastboot update?
Click to expand...
Click to collapse
Just unzip the factory image and there U can see the flash shell script files too. Open them in a text editor & U could see the exact command. In a factory img, they also do the same thing via script files. Flashing the radio & bootloader & updating the rest archive

so this is what I've done
I've manually flashed every file needed for the factory image from google.
I also tried wugfresh tool kit which is great but didn't help me much. I flashed stock recovery and treid to boot into to and nothing. I flashed a customer recovery and nothing.
It always does the same thing
the screen that says my phone can't be checked for corruption and then the google sign comes up stays on for a couple seconds and then it bootloops to the can't be checked for corruption.
I try to get into recovery using fastboot commands and the phone does the same exact thing.
I was even able to lock and relock the bootloader and I was able to successfully flash everything at least that is what it showed on the computer
so ive read almost every thread that had to do with bricking and I feel like an expert now but im starting to think it is done =/

edgarted said:
so this is what I've done
I've manually flashed every file needed for the factory image from google.
I also tried wugfresh tool kit which is great but didn't help me much. I flashed stock recovery and treid to boot into to and nothing. I flashed a customer recovery and nothing.
It always does the same thing
the screen that says my phone can't be checked for corruption and then the google sign comes up stays on for a couple seconds and then it bootloops to the can't be checked for corruption.
I try to get into recovery using fastboot commands and the phone does the same exact thing.
I was even able to lock and relock the bootloader and I was able to successfully flash everything at least that is what it showed on the computer
so ive read almost every thread that had to do with bricking and I feel like an expert now but im starting to think it is done =/
Click to expand...
Click to collapse
Hey there. First off make sure to unlock again your bootloader. Then you may follow post # 10 of @Heisenberg 's flashing guide for our device.
First images to flash would be bootloader and radio. First flash bootloader, then make sure to issue the command adb reboot-bootloader. Then afterwards once the phone has rebooted back to bootloader, flash radio, then again do the adb reboot-bootloader again.
Once the phone is again back to bootloader flash the rest of the images except userdata. For the boot.img and recovery.img, flash the stock ones-don't use the decrypted boot.img and don't flash the twrp.img yet. Once all necessary images have been flashed issue the reboot-booloater command one more time, then on the bootloader screen choose the reboot option. Wait anywhere from 3-10 minutes for the phone to load. Let us know how it goes for you.

blitzkriegger said:
Hey there. First off make sure to unlock again your bootloader. Then you may follow post # 10 of @Heisenberg 's flashing guide for our device.
First images to flash would be bootloader and radio. First flash bootloader, then make sure to issue the command adb reboot-bootloader. Then afterwards once the phone has rebooted back to bootloader, flash radio, then again do the adb reboot-bootloader again.
Once the phone is again back to bootloader flash the rest of the images except userdata. For the boot.img and recovery.img, flash the stock ones-don't use the decrypted boot.img and don't flash the twrp.img yet. Once all necessary images have been flashed issue the reboot-booloater command one more time, then on the bootloader screen choose the reboot option. Wait anywhere from 3-10 minutes for the phone to load. Let us know how it goes for you.
Click to expand...
Click to collapse
Hello and thank you for helping.
I tried this method a couple of minutes ago. I flashed them this same way
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
It does the same exact thing it will try and restart the phone, the message that says it can't be checked for corruption the google logo comes up and it repeats it self non stop.
This is what doesn't make sense to me.
This is the file that I had flashed through twrp when it was working fine
Leviticus 1.3 - http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709

edgarted said:
Hello and thank you for helping.
I tried this method a couple of minutes ago. I flashed them this same way
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
It does the same exact thing it will try and restart the phone, the message that says it can't be checked for corruption the google logo comes up and it repeats it self non stop.
This is what doesn't make sense to me.
This is the file that I had flashed through twrp when it was working fine
Leviticus 1.3 - http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
Click to expand...
Click to collapse
This is weird. What version of the stock factory images did you flash? I've been using leviticus 1.3 since it came out and when i was still on stock rom. I switched over to cm builds and have been flashing every nightly since the 7/24th build, and in the process repeatesly reflashing the aound mod along, and i've had zero issues with the phone booting afterwards.

Help Z00T stuck on bootloop

Help im stuck on bootloop i can get into fastboot and recovery but recovery automatically reboots. I read that there are other .img you need to fix it but i cant find any of them only boot.img.
Is there anything i can do or is it completely ****ed.
its unlocked not rooted bricked while trying. tried sideloading, tried running
fastboot erase cache
fastboot erase userdata
fastboot erase system

whould writing it to an sd card work?

Still can't access fastboot while holding volume up + power button?

I can get into fastboot fine but after 1 min or so it reboots

Since you have unlocked BL flash latest twrp fast. Rename it something short so it will be easy to type

Okay i did that it got into the opening screen for twrp then it rebooted automatically.
FIXED: okay i tried again and it sdidnt reboot what would i do next?

nice that you can now reboot to recovery, all you have to do is flash a custom ROM and gapps. Were you on stock LL or MM ROM before you bootloop? Sorry with the late reply, Im busy with work. Quote my reply so I can receive notification.

24imelqui said:
nice that you can now reboot to recovery, all you have to do is flash a custom ROM and gapps. Were you on stock LL or MM ROM before you bootloop? Sorry with the late reply, Im busy with work. Quote my reply so I can receive notification.
Click to expand...
Click to collapse
I was on stock MM (Marshmellow). Thank you, you've been so much help.

You can flash CM13/14 base ROM without a problem since you were on stock MM. If you decided to wipe system in TWRP, manually power off first in TWRP, wait for the phone to turned off then reboot back to TWRP and flash your new ROM and GAPPS. Do not reboot to system if you wipe system cause you might lose your recovery.
Edit: I only do this when I also wipe Internal Storage.

[ZE551KL] Stuck in bootloop, need complete rebuild. Help!

OK, 3 days ago I rebooted my ZE551KL and it went into a bootloop. I was completely 100% stock. No root. Locked bootloader. Spent the better part of the weekend trying to troubleshoot it, and I have made almost zero progress.
I've tried a bunch of things, but here is my current status.
Can get into fastboot mode no problem.
POWER + DOWN VOL gets me into stock recovery, but at some point I flashed an older version. I tried flashing TWRP, but after install could never seem to get into it (is that because I'm unrooted and locked?)
Current recovery version: Android system recovery <3e> LRX22G.WW_user_1.16.40.763_20151201
I've tried flashing to a couple different firmware versions from the ASUS website both via ADB and via the SD Card.
Current firmware: UL-z00T-WW-1.17.40.1531-user.zip
Still in bootloop.
Any advice on rebuilding this thing from scratch? I dont care whether I just get stock back, or if I need to root/unlock, install TWRP and a custom ROM. Dont care, just want a functioing phone!
Thanks in advance.

ACFH said:
I dont get it. Did you factory reset your phone? With stock rom, factory work most of the time.
You said that you tried flashing TWRP. If you see successfull message after flash, type "fastboot reboot" and hold volume down button right after hit Enter. If you did right, you can get into twrp, then choses Wipe > format, it more powerfull than factory reset.
Click to expand...
Click to collapse
1. Factory reset from within the phone's OS? No, I cant get that far. Just constant bootloop on ASUS logo.
2. I've used the fastboot erase command to wipe everything, and used the wipe data/factory reset option in the stock recovery. Still bootloop.
3. I've tried flashing TWRP 3.0.0.0 and the newest version of TWRP. I hold down the VOL DOWN key before hitting enter on "fastboot reboot"; it just goes into a faster bootloop, like every half-second. When I release the VOL DOWN key, it goes into the same, slower original bootloop.

ACFH said:
Ok. You can format through fastboot
Code:
fastboot format userdata
fastboot format cache
If it still stuck in bootloop, try reflash boot and recovery, fastboot wipe system. Then copy update.zip to sdcard. Boot into recovery > install update from external sd.
Click to expand...
Click to collapse
Awesome. I'll give that a try and report the results.
I just downloaded the .img with the same date as my recovery version from here. https://asus.kremowka.xyz/categories/show/2
Its been hung at "Verifying update package...." for about 10 mins now. Once this is finished (and probably fails ); I'll give your format commands a try.

ACFH said:
Ok. You can format through fastboot
Code:
fastboot format userdata
fastboot format cache
If it still stuck in bootloop, try reflash boot and recovery, fastboot wipe system. Then copy update.zip to sdcard. Boot into recovery > install update from external sd.
Click to expand...
Click to collapse
Ugh. Didn't work. Here is what I did:
fastboot format userdata
fastboot format cache
fastboot erase system
fastboot format system
Reboot to recovery
install UL-z00T-WW-1.17.40.1531-user.zip from SD card.''
Installation successful.
Reboot.
In a bootloop that shows ASUS logo for 10-15 seconds, flashes a blue screen really quick, then reboots.
What can I try next?