Develop Bugs

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

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

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

also
please pm me if u fixed yours

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

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

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

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

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

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

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

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

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

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

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

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

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

ayuda
ATT ZE500CL/Z00D rom

Recover on from bootloop on H815 EU

Hi guys,
Yesterday I got sweaty hand palms.
My EU 815 G4 is unlocked, the official way, and I had rooted it.
Then I tried to install xposed from twrp and I did something wrong, and ended up in bootloop...
I have just updated to v20b before, and forgot to connect the phone to the PC, and allow the PC debug access before installing xposed, so i could see the phone in ADB mode, but couldn't access it.
Of course I hadn't made a backup before this - I like to cry
Just as a desperate try, when everything else had failed, i thought about using the new tool provided by shakeyabooti LG UP to flash the factory KDZ all over
I put the phone in SW. update mode by:
1. Turning off the phone
2. connecting USB cable to the PC
3. Press and hold vol. up while connecting the USB cable to the phone
Then i downloaded the v20b KDZ file, provided by Autoprime (since this was what i where allready running)
Opened LG UP, loaded the H81520B_00.kdz, marked REFURBISH
Lastly i pressed "Start" and waited for about 15-20 minutes and "TADAAAA"
The phone where up and running again... only things lost where root and TWRP
- Sharing since I'm properly not the only one ending up in this kind of mess :laugh:

Just tried it no luck :/
So just to confirm...unlocking bootloader official way does void warranty and we can not send it in for repairs?

rakinisbat said:
Just tried it no luck :/
So just to confirm...unlocking bootloader official way does void warranty and we can not send it in for repairs?
Click to expand...
Click to collapse
Indeed. Maybe you'll find a cool employee at your vendor who will still do it, but your warranty is definately void and they don't need to do anything. Depends on how acommodating the employee is. If you're stuck in a bootloop @rakinisbat just follow the steps in this thread.
And please keep in mind that there's a way to get out of bootloops 99% of the time (in fact 100% if it's a software related problem), you just have to do a good search on xda. Furthermore there's an uninstaller app for xposed in the official rovo89 thread, which you can flash via recovery and it which undos the xposed installation and your phone will boot fine (if you can access TWRP - just flash it). If you have further questions you can PM me, always happy to help

Follow_and_Feel said:
Indeed. Maybe you'll find a cool employee at your vendor who will still do it, but your warranty is definately void and they don't need to do anything. Depends on how acommodating the employee is. If you're stuck in a bootloop @rakinisbat just follow the steps in this thread.
And please keep in mind that there's a way to get out of bootloops 99% of the time (in fact 100% if it's a software related problem), you just have to do a good search on xda. Furthermore there's an uninstaller app for xposed in the official rovo89 thread, which you can flash via recovery and it which undos the xposed installation and your phone will boot fine (if you can access TWRP - just flash it). If you have further questions you can PM me, always happy to help
Click to expand...
Click to collapse
Thanks Mate, I guess ill have to try my luck with LG,
I have that batch of H815 with the faulty motherboard, unfortunately I'm in that 1% *Sigh* :crying:
Tried literally everything i could with the software, pretty much confirmed it is the motherboard.
It looks like the KDZ is flashing properly, as LGUP shows whichever kdz i put on, but the actual hardware is not capable of booting into the OS.

rakinisbat said:
Thanks Mate, I guess ill have to try my luck with LG,
I have that batch of H815 with the faulty motherboard, unfortunately I'm in that 1% *Sigh* :crying:
Tried literally everything i could with the software, pretty much confirmed it is the motherboard.
It looks like the KDZ is flashing properly, as LGUP shows whichever kdz i put on, but the actual hardware is not capable of booting into the OS.
Click to expand...
Click to collapse
Ugh, okay that's bad luck. Sorry to hear. If it's a motherboard problem I can't help you unfortunately Sorry for that. What is exactly happening when you try to flash via LGUP? Just curious

Follow_and_Feel said:
Ugh, okay that's bad luck. Sorry to hear. If it's a motherboard problem I can't help you unfortunately Sorry for that. What is exactly happening when you try to flash via LGUP? Just curious
Click to expand...
Click to collapse
It flashed perfectly fine, once completed it reboots and just literally sits on the LG logo.....FOREVER or till the battery dies.
So much disappointment in LG

rakinisbat said:
It flashed perfectly fine, once completed it reboots and just literally sits on the LG logo.....FOREVER or till the battery dies.
So much disappointment in LG
Click to expand...
Click to collapse
Oh yeah that really sounds like a hardware problem. Damn it LG! But is your bootloader still locked? You might have a chance to get a new one if it is And if it's a hardware prob you still have your warranty, haven't you?

Follow_and_Feel said:
Oh yeah that really sounds like a hardware problem. Damn it LG! But is your bootloader still locked? You might have a chance to get a new one if it is And if it's a hardware prob you still have your warranty, haven't you?
Click to expand...
Click to collapse
Nope, my bootloader is unlocked, im a flash-a-holic, longest i have lasted without rooting or unlocking a bootloader is about 2 weeks. I would have never imagined such a massive hardware issue with a flagship phone. I'll probably get a nexus 6P atleast it has better support than a LG. I'm in Australia, I imported this phone when it was released, so i have to send this phone overseas if i want it repaired, which they will most likely deny.
Sooooo over LG now! There are like hundreds if not thousands that are effected they are not even acknowledging it or providing a viable solution.

rakinisbat said:
Nope, my bootloader is unlocked, im a flash-a-holic, longest i have lasted without rooting or unlocking a bootloader is about 2 weeks. I would have never imagined such a massive hardware issue with a flagship phone. I'll probably get a nexus 6P atleast it has better support than a LG. I'm in Australia, I imported this phone when it was released, so i have to send this phone overseas if i want it repaired, which they will most likely deny.
Sooooo over LG now! There are like hundreds if not thousands that are effected they are not even acknowledging it or providing a viable solution.
Click to expand...
Click to collapse
Haha! I can completely subscribe to the flash-a-holic :laugh: Well ok. So it's even worse than i thought Sorry for ya. At least you live on a continent everyone here desires to go to :laugh: Going to Australia is very popular in germany But sorry that you're experiencing trouble with your LG. Good luck with that nexus - it's an awesome phone, too. Bye bye

I've got the bootloop issue. Phone was turning on or not, just vibrating etc. I've dissassembled it, assembled again and it started working don't know why...Now I've flashed CM I was on Genisis ROM earlier maybe that was the issue

zwodziarz said:
I've got the bootloop issue. Phone was turning on or not, just vibrating etc. I've dissassembled it, assembled again and it started working don't know why...Now I've flashed CM I was on Genisis ROM earlier maybe that was the issue
Click to expand...
Click to collapse
Hi sir
I decide to buy lg g4.
If i flash cm ,bootloop not happend again?
Thank you

It doesn't matter what firmware you have got. Bootloop is happening because of hardware failure.
Odesláno z mého LG-H815 pomocí Tapatalk

Damn...just made a huge mistake. phone bricked?

My son wanted to root his brand new phone. i have rooted 8 phones from different phones before with success..... but this time i f***d up...
Accedently installed this on his phone.
http://wccftech.com/flash-and-root-nexus-5-on-android-6-0-1-mmb29k/
executed flash-all.bat and it flashed the bootloader.
For the wrong phone...
It should have been this one..
http://wccftech.com/flash-and-root-nexus-5x-android-6-0-1/
Missed the X......
Now the phone will not even boot any more at all....cant enter bootloader.......does not power up at all.!!!
Jesus...what have i done.......
It here any chance at all to fix this somehow?

Hello and thank you for using Q/A,
because you can't enter bootloader, you can't do anything. You can try to send the phone to Google. Say: It didn't boot after OTA Update.
Kind regards
Trafalgar Square

Yeah it's most likely a paperweight. Try sending it to Google. Flashing the wrong firmware destroys a phone as you probably already know

well
hopesrequiem said:
Yeah it's most likely a paperweight. Try sending it to Google. Flashing the wrong firmware destroys a phone as you probably already know
Click to expand...
Click to collapse
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....

Only thing I know to use is a riff box to jtag it. Not sure if they have one for 5x.

crowhater said:
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....
Click to expand...
Click to collapse
Your use of the period seems rather condescending. And no, you as the end user cannot fix that. You did one of the few things that is unrecoverable unless you manage to get the bootloader to accept adb commands somehow.

crowhater said:
I am totally aware of that....
but somehow one must be able to flash the bootloader from scratch....
Normally via special software etc.
That´s what i was hoping for....
Click to expand...
Click to collapse
Didn't you say the phone won't turn on? The above scenario is not possible.

Well
bobby janow said:
Didn't you say the phone won't turn on? The above scenario is not possible.
Click to expand...
Click to collapse
Well. the bootloader is flashed into the phone from the beginning aswell during manufacturing. I work with electronics and software and i know there is always a way to reflash the bootloader. All the electronics comes in the beginning with no software at all, one only needs the proper software/hardware. Most probably by jtag....or if they have some other special tool for snapdragon 808.
Stupid of me not to see that the version i flashed was not for nexus 5X...and only for nexus 5
sight...

Good luck. Will Google not rma it?

Device State - locked

I know there are other threads regarding this but those included someone having TWRP already flashed and in this case I do not.
I sadly took a chance and bought a Nexus 5X off someone on Kijiji and it looks like I got got scammed.
I've own other Nexus phones in the past but was unaware of the OEM Lock on the latest devices and it is in a locked state and I do not know the google account to unlock it (as it wasn't my phone prior to this)
None of the fastboot/adb commands work as it is locked.
I just wanted to know if there was any other way I could fix this or if I have brick on my hands here. Any assistance would be amazing as this would mean I just blew my money away.
N

sniperIT said:
I know there are other threads regarding this but those included someone having TWRP already flashed and in this case I do not.
I sadly took a chance and bought a Nexus 5X off someone on Kijiji and it looks like I got got scammed.
I've own other Nexus phones in the past but was unaware of the OEM Lock on the latest devices and it is in a locked state and I do not know the google account to unlock it (as it wasn't my phone prior to this)
None of the fastboot/adb commands work as it is locked.
I just wanted to know if there was any other way I could fix this or if I have brick on my hands here. Any assistance would be amazing as this would mean I just blew my money away.
N
Click to expand...
Click to collapse
So you purchased a 5X that wasn't factory reset? Have you tried asking the previous owner for assistance? They might be able to remotely wipe the phone using Android Device Manager.

metpage said:
So you purchased a 5X that wasn't factory reset? Have you tried asking the previous owner for assistance? They might be able to remotely wipe the phone using Android Device Manager.
Click to expand...
Click to collapse
It was reset and required login of the previous account to unlock it. Unfortunately, the previous owner is nowhere to be found...
The build number is MHC19J and I've been told that I am screwed to unlock it.
Nick

sniperIT said:
It was reset and required login of the previous account to unlock it. Unfortunately, the previous owner is nowhere to be found...
The build number is MHC19J and I've been told that I am screwed to unlock it.
Nick
Click to expand...
Click to collapse
I would try and get your money back, chances are you could have brought a stolen phone.

Darke5tShad0w said:
I would try and get your money back, chances are you could have brought a stolen phone.
Click to expand...
Click to collapse
Sadly you may be right, but like any good thief he seems to be unreachable, so I unfortunately can't get the money back. I have checked the IMEI and it is clean so i should be able to activate it.
I just need a way to bypass the FRP (Factory Reset Protection). I've seen posts on this on XDA but they are for patches up to the March 1st Patch. I build I have is the March Patch and I can't seem to find any workarounds for this patch level.
In the event that someone has found a way please let me know as it would save me a lot of grief.
Thank you for your responses.
N

sniperIT said:
Sadly you may be right, but like any good thief he seems to be unreachable, so I unfortunately can't get the money back. I have checked the IMEI and it is clean so i should be able to activate it.
I just need a way to bypass the FRP (Factory Reset Protection). I've seen posts on this on XDA but they are for patches up to the March 1st Patch. I build I have is the March Patch and I can't seem to find any workarounds for this patch level.
In the event that someone has found a way please let me know as it would save me a lot of grief.
Thank you for your responses.
N
Click to expand...
Click to collapse
I don't know if will help, but the N preview may not include or may reset FRP. Usually OTAs only include the changed files but since the N preview was bricking locked phones, Google released full OTAs that contained everything. You could try flashing it with ADB while in the stock recovery.
Sent from my Nexus 5X using Tapatalk

PiousInquisitor said:
I don't know if will help, but the N preview may not include or may reset FRP. Usually OTAs only include the changed files but since the N preview was bricking locked phones, Google released full OTAs that contained everything. You could try flashing it with ADB while in the stock recovery.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I was thinking the same thing but I don't want to make the situation worse than it already is. I have seen vids from RootJunky showing that the N preview is bypassable and it can be done with a reset.
Will the OTA wipe all the data on the device?
Just to be clear are these the OTA's you are referring too? http://developer.android.com/preview/download-ota.html
Thank you for your advice.
N

sniperIT said:
I was thinking the same thing but I don't want to make the situation worse than it already is. I have seen vids from RootJunky showing that the N preview is bypassable and it can be done with a reset.
Will the OTA wipe all the data on the device?
Just to be clear are these the OTA's you are referring too? http://developer.android.com/preview/download-ota.html
Thank you for your advice.
N
Click to expand...
Click to collapse
Those are the files. That is what I would do.
Sent from my Nexus 5X using Tapatalk

PiousInquisitor said:
Those are the files. That is what I would do.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Ok thank you very much I am in the process, will update once it is complete.
N

sniperIT said:
Ok thank you very much I am in the process, will update once it is complete.
N
Click to expand...
Click to collapse
Looks like it is still a no go. The FRP seems to still be in place and the reset idea didn't work.
I may need to see if i can get this phone completely blanked.
N

sniperIT said:
Looks like it is still a no go. The FRP seems to still be in place and the reset idea didn't work.
I may need to see if i can get this phone completely blanked.
N
Click to expand...
Click to collapse
I've got on last idea. Is it a 32 gig model?
Sent from my Nexus 5X using Tapatalk

PiousInquisitor said:
I've got on last idea. Is it a 32 gig model?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
16GB unfortunately.

sniperIT said:
16GB unfortunately.
Click to expand...
Click to collapse
Bummer. I was going to suggest THIS. But there isnt a 16 TOT file.
So you were able to successfully flash N from the stock recovery? And you simply couldnt get past the login screen? FRP is a *****. I had no idea what it was when I sold my Moto X Pure Edition last year. I ended up giving the guy I sold it to my password so he could unlock it. That was after about a day of searching for a workaround. Then my sis bought a G4 and when it arrived it was locked with FRP. We ended up finding a tool to wipe it out. Such a pain. Lol. Good luck finding a solution. Let us know if you get it working some other way.
---------- Post added at 10:41 PM ---------- Previous post was at 10:30 PM ----------
sniperIT said:
16GB unfortunately.
Click to expand...
Click to collapse
Have you tried this? EDIT: Looks like its been patched already...
https://www.youtube.com/watch?v=ocC7ruFCqOI

PiousInquisitor said:
Bummer. I was going to suggest THIS. But there isnt a 16 TOT file.
So you were able to successfully flash N from the stock recovery? And you simply couldnt get past the login screen? FRP is a *****. I had no idea what it was when I sold my Moto X Pure Edition last year. I ended up giving the guy I sold it to my password so he could unlock it. That was after about a day of searching for a workaround. Then my sis bought a G4 and when it arrived it was locked with FRP. We ended up finding a tool to wipe it out. Such a pain. Lol. Good luck finding a solution. Let us know if you get it working some other way.
---------- Post added at 10:41 PM ---------- Previous post was at 10:30 PM ----------
Have you tried this? EDIT: Looks like its been patched already...
https://www.youtube.com/watch?v=ocC7ruFCqOI
Click to expand...
Click to collapse
Man is it ever. The last thing I was thinking was that they say there is a 72 hour lock on this and I only first started the phone on Sat night. maybe I need to wait until tomorrow and see what happens.
I will check out the Youtube video.
Thank you for all your help once again.
N

sniperIT said:
Man is it ever. The last thing I was thinking was that they say there is a 72 hour lock on this and I only first started the phone on Sat night. maybe I need to wait until tomorrow and see what happens.
I will check out the Youtube video.
Thank you for all your help once again.
N
Click to expand...
Click to collapse
So were you able to reset the phone on N, like in the rootjunky video?
https://www.youtube.com/watch?v=nOymYg3lswI

PiousInquisitor said:
So were you able to reset the phone on N, like in the rootjunky video?
https://www.youtube.com/watch?v=nOymYg3lswI
Click to expand...
Click to collapse
I unfortunately don't have a sim to test with. The one in my current is a micro not a nano. I am going to contact a repair store tomorrow to see if they can assist and I will try it out.
Sorry yes I did exactly as he suggested and it didn't work.
It gives me the option during setup to setup like it was a new phone but then as soon as I connect to my WiFi it performs a check and states the same reset message.
Which is why I might be thinking that it is the 72 hour lock on and maybe it will go away once it is complete.
N

sniperIT said:
I unfortunately don't have a sim to test with. The one in my current is a micro not a nano. I am going to contact a repair store tomorrow to see if they can assist and I will try it out.
Sorry yes I did exactly as he suggested and it didn't work.
It gives me the option during setup to setup like it was a new phone but then as soon as I connect to my WiFi it performs a check and states the same reset message.
Which is why I might be thinking that it is the 72 hour lock on and maybe it will go away once it is complete.
N
Click to expand...
Click to collapse
I would try it again. If you factory reset from within android, it should disable FRP, including the need to wait 72 hrs.
I wouldn't bother with the repair shop. The latest and greatest info is going to be on the internet and probably from rootjunky.

PiousInquisitor said:
I would try it again. If you factory reset from within android, it should disable FRP, including the need to wait 72 hrs.
I wouldn't bother with the repair shop. The latest and greatest info is going to be on the internet and probably from rootjunky.
Click to expand...
Click to collapse
I tried several times with no luck.
It just seems like once it phones home to Google it blocks me.
I'm going to try to contact rootjunky directly

sniperIT said:
I tried several times with no luck.
It just seems like once it phones home to Google it blocks me.
I'm going to try to contact rootjunky directly
Click to expand...
Click to collapse
Bummer. Im out of ideas.

What message do you exactly get when trying to execute something via fastboot?

Question Anyone bricked/EDL/9008 their ROG 6?

Follow and complain here.
Let ASUS know their bootloader implementation is VERY NOT FRIENDLY to us. I've been modding my Android devices since the Android 2 era and this is the first time I encountered an UNOFFICIALLY UNRECOVERABLE state which is a HORRIBLE experience.
Me? Have played with
Samsung(S5 to S9 and Tab/Odin is a good thing)
XiaomiRedmiPoco(Main device for me today, very modder friendly and robust)
Huawei(Remember when they allow applying for BL unlock?)
Apple(LOL jailbreak from A4 SoC until iPhone X(meantime Samsung S8 looks gorgeous) lost my interest)
And various small brands or exited market big brands(honorable mention Lenovo LePhone C101. My first smart device/Android and received big community support at the good old time)
ASUS. Fix your buggy BL. Fix your policy. Release everything we need to fix OUR DEVICES of OURSELVES. Just ONE step closer to perfect.

Just imagine how stupid is this:
Everytime you want to update you operating system, your UEFI/BIOS firmware might break.
And worse, that you don't have free official resources to fix it?
And can it be worse? Yes! Your Warranty is maybe void because you may unlocked bootloader, now supposedly only ASUS service center have the file to fix it.
Ha now it's interesting. That's the era of ANTITRUST. Even Apple won't do it(Worst case DFU, easily fixable using OFFICIAL iTunes).
WT*?

yeah dude i'm bricked up rn

Paid here, paid there.
Yeah sure.
Exploit people.

Perhaps instead of ranting about asus, you could tell us what you have done exactly to brick your device, and someone might be able to help you ? can you get into fastboot at all?

EDIT: quoted content removed.
Never use this firmware, because it has not been modified, 100% of fingerprints and IMEI will be lost after use. You need to modify the firmware before you can flash it.

mahdibassam said:
Perhaps instead of ranting about asus, you could tell us what you have done exactly to brick your device, and someone might be able to help you ? can you get into fastboot at all?
Click to expand...
Click to collapse
Trying to flash img unpacked from update zip. Which you should NOT do. Because Android 12 dynamic partition.

iMoc said:
Trying to flash img unpacked from update zip. Which you should NOT do. Because Android 12 dynamic partition.
Click to expand...
Click to collapse
Ok, yes you definitely should not do that
So just wondering, you went and grabbed some img files and made the decision to flash them, why is this any fault of asus?

mahdibassam said:
Ok, yes you definitely should not do that
So just wondering, you went and grabbed some img files and made the decision to flash them, why is this any fault of asus?
Click to expand...
Click to collapse
1\ The fastboot code in their bootloader have bugs, any CORRECT command you type can easily break bootloader then stuck you in 9008.
2\ The normal update method failed because THEIR UPDATER did do things wrong.
3\ They refuse to provide official ROM to let yourself fix it. SEND IT TO ME TO FIX IT, AND I MIGHT CHARGE YOU SOME.
....\
N\ You go talk to Apple about it because they are experts about saying YOU USED IT WRONG.

Anyone asked for help gets it for free so far.
All devs on my chat group agree at least fastboot flashable should be available on the official download page.
MOD EDIT: off topic content removed

Did you manage to unbrick your phone?
I managed to semi hard brick my phone. Can get into fastboot but unable to start recovery mode from fast boot and phone doesn't show up from adb devices.
I guess I'll start a new thread but any tips?

insideoft said:
Did you manage to unbrick your phone?
I managed to semi hard brick my phone. Can get into fastboot but unable to start recovery mode from fast boot and phone doesn't show up from adb devices.
I guess I'll start a new thread but any tips?
Click to expand...
Click to collapse
If you can boot into fastboot you can just flash the RAW ROM file available a few days ago. It's not bricked in this case.

Moderator Information
Hello everyone,
I have cleaned the thread from off topic contents and posts. Please focus on problem solving related discussion, not finger pointing or flaming each other. We all come here to solve the issues and learn some new stuffs.
Thanks.

iMoc said:
If you can boot into fastboot you can just flash the RAW ROM file available a few days ago. It's not bricked in this case.
Click to expand...
Click to collapse
Sorry long time ago since I was into this stuff previosly.
That fixed it, thanks for the help!

same here