Database Info

Please assist - Unusable Razr HD ( Spent 5-6 hours so far no luck )

Hi team,
Wondering is someone can assist or point me in right direction for fixing my wife's Razr HD. ( Australian Telstra GSM )
Issue - Currently phones starts goes to OS , however all andriod apps / core services are stopping making it unusable, usually phone will start ask for pin and within 30 seconds all apps and core services stop ( with error messages etc ).
So here is what happens and i have tried.
1. Tried uninstalling apps ( eg whatsapp / facebook etc .. ) it uninstalls sometime before the freezing / errors - but once you reboot those apps come back as there never uninstalled :|
2. Erase all data it never works it lets me press the button , but on reboot come back to original problem OS.
So i decided i should root / install custom rom or even stock rom ).
1. Boot Loader - Unlocked ( did that on motorola website no issues )
2. Tried Installing customer recovery in fastboot ( it flashes , however it goes to original recovery dead gread andriod with red traingle with belly open !, after flash i have not let it boot to OS still the same issue) - i think it has original-recovery.p file in system i cant delete it or rename it ..
3, Rooting - tried rooting no luck .. i can connect via ADB however system is read only ( doesnt let SU , busy box etc to copy or execute at all ) - tried motochoppper/ saferoot no luck .. it cant write or copy or exceute SU.
So i tried few other extreme measures as below..
fastboot erase system or -w
fastboot erase data
fastboot erase cache
All successful , however after that still boot to original OS.
Tried installing Stock ROM/Firmware using - RSDLite , it seems to install copied the files on reboot .. same old OS ..
i can goto fastboot , i can run adb shell command ( but its read only system ).
i am really stuck here wondering if you guys help / much appreciated.
rgds.

Have you tried factory reset? Or boot into safe mode?

Zeljko1234 said:
Have you tried factory reset? Or boot into safe mode?
Click to expand...
Click to collapse
Factory reset yes , however after device reboot it does nothing comes back t same faulty OS.
Safe mode?

Safe mode.
You may try to flash rom again but be very careful with unlocked bootloader. It's strange that you cannot boot into custom recovery holding volume down and power after you flashed it.

Zeljko1234 said:
Safe mode.
You may try to flash rom again but be very careful with unlocked bootloader. It's strange that you cannot boot into custom recovery holding volume down and power after you flashed it.
Click to expand...
Click to collapse
Tried flashing , in safe mode no luck either , any other suggestions?
Cheers,

You probably left your USB plugged in after you flashed Recovery and that set you back to Stock Recovery.....unplug the usb....

Hmm sounds like symptons that my dad's old Nook color experienced being stuck in read only mode. Tried everything but it was stuck in that read only state no matter what I did. Hopefully that is not the case for your phone. Have you tried house of moto or other compatible utility to restore back to stock?

this happened a few times on an older faulty version of twrp. until someone can figure out how to remove the write only from fastboot, there is no utility or script that will fix it.
no one was able to figure it out before, unfortunately, your phone is likely toast.

Just saw this thread and it sounds exactly like what just started happening to my phone yesterday. I was unlocked, and rooted, with stock VZW (US) ROM. All was fine. Then started getting app error popups like you state and tried using TWRP recovery to install a backup I had made and it appears to work only if I DO NOT check the 'data' box. When I try and wipe data, it errors out as well. I am worried something caused it to get stuck in read only mode like one of the last comments in this thread and the phone is toast, but not just.
If you find anything or figure it out please let me know, I'll do the same....
desitunez said:
Hi team,
Wondering is someone can assist or point me in right direction for fixing my wife's Razr HD. ( Australian Telstra GSM )
Issue - Currently phones starts goes to OS , however all andriod apps / core services are stopping making it unusable, usually phone will start ask for pin and within 30 seconds all apps and core services stop ( with error messages etc ).
So here is what happens and i have tried.
1. Tried uninstalling apps ( eg whatsapp / facebook etc .. ) it uninstalls sometime before the freezing / errors - but once you reboot those apps come back as there never uninstalled :|
2. Erase all data it never works it lets me press the button , but on reboot come back to original problem OS.
So i decided i should root / install custom rom or even stock rom ).
1. Boot Loader - Unlocked ( did that on motorola website no issues )
2. Tried Installing customer recovery in fastboot ( it flashes , however it goes to original recovery dead gread andriod with red traingle with belly open !, after flash i have not let it boot to OS still the same issue) - i think it has original-recovery.p file in system i cant delete it or rename it ..
3, Rooting - tried rooting no luck .. i can connect via ADB however system is read only ( doesnt let SU , busy box etc to copy or execute at all ) - tried motochoppper/ saferoot no luck .. it cant write or copy or exceute SU.
So i tried few other extreme measures as below..
fastboot erase system or -w
fastboot erase data
fastboot erase cache
All successful , however after that still boot to original OS.
Tried installing Stock ROM/Firmware using - RSDLite , it seems to install copied the files on reboot .. same old OS ..
i can goto fastboot , i can run adb shell command ( but its read only system ).
i am really stuck here wondering if you guys help / much appreciated.
rgds.
Click to expand...
Click to collapse
---------- Post added at 03:02 PM ---------- Previous post was at 02:52 PM ----------
I am guessing this might be the issue and I am experiencing it as well. However, I have no idea how that could have happened in the first place. I never tried to do anything with TWRP until after the phone began acting funny with all apps crashing (pop ups stating that) and the phone essentially becoming unusable.
When I am in TWRP and do wipes (factory reset, or advanced wipes) it seems to wipe everything fine, even the data partition. However, when I try and write to that partition it fails (i.e. restoring a backup including the data partition). If I don't include the data partition the restore works, but the phone is still crap.
Does this sound like the issue you mention below (data is stuck on read only and there is no way around it)?? If so, anyone in the market for a decent looking paperweight??
bweN diorD said:
this happened a few times on an older faulty version of twrp. until someone can figure out how to remove the write only from fastboot, there is no utility or script that will fix it.
no one was able to figure it out before, unfortunately, your phone is likely toast.
Click to expand...
Click to collapse

surfmly said:
Just saw this thread and it sounds exactly like what just started happening to my phone yesterday. I was unlocked, and rooted, with stock VZW (US) ROM. All was fine. Then started getting app error popups like you state and tried using TWRP recovery to install a backup I had made and it appears to work only if I DO NOT check the 'data' box. When I try and wipe data, it errors out as well. I am worried something caused it to get stuck in read only mode like one of the last comments in this thread and the phone is toast, but not just.
If you find anything or figure it out please let me know, I'll do the same....
---------- Post added at 03:02 PM ---------- Previous post was at 02:52 PM ----------
I am guessing this might be the issue and I am experiencing it as well. However, I have no idea how that could have happened in the first place. I never tried to do anything with TWRP until after the phone began acting funny with all apps crashing (pop ups stating that) and the phone essentially becoming unusable.
When I am in TWRP and do wipes (factory reset, or advanced wipes) it seems to wipe everything fine, even the data partition. However, when I try and write to that partition it fails (i.e. restoring a backup including the data partition). If I don't include the data partition the restore works, but the phone is still crap.
Does this sound like the issue you mention below (data is stuck on read only and there is no way around it)?? If so, anyone in the market for a decent looking paperweight??
Click to expand...
Click to collapse
if your phone goes to read only because of that faulty version of twrp, its toast. i am sorry for your loss

He can try to flash correct twrp...

Zeljko1234 said:
He can try to flash correct twrp...
Click to expand...
Click to collapse
that may work in some rare cases.
i hope this poster is one of them!!! that it works.
if the entire phone goes to read only. i havent seen a solution on any forum.

bweN diorD said:
that may work in some rare cases.
i hope this poster is one of them!!! that it works.
if the entire phone goes to read only. i havent seen a solution on any forum.
Click to expand...
Click to collapse
Well it looks like I was able to get through some of it. I followed the instructions here: http://www.droidrzr.com/index.php/topic/49699-1834614xt926-ota/. I did the extra step of going to stock 183 (unrooted) and then flashed the update in that and the phone is working fine. I am already unlocked (have been for long time), but not rooted at the moment. I believe I can root now (being that I am unlocked) but haven't tackled that yet. At the very least I have a phone that works for my upcoming business trip.....
BTW - the TWRP I had installed has been used on my phone for a long time (8-12 months??) so not sure why that version all of a sudden would have caused the issue, but at this point it doesn't appear to have been that issue (with data locked in read only mode).

I'm really glad that you found solution for you and for all of us who may have the same problem in the future. Thx.

[GUIDE] How to recover from OnePlus soft bricked?

I decided to write a guide on how to recover from a bricked OnePlus One. This is my first guide.
About me: I am a newbie on Android.However, the XDA community has taught me a lot about my Android phone for the first month of using it. That's right! I have only been using Android for less than one month so take this guide with a grain of salt. But if you happen to soft brick your One, this is the guide to turn to. I have created two mind-bending/heartbreaking/frightening scenarios that I have experienced. Though, resolved thanks to this community.
Note: This will wipe your phone!
Scenario 1:
Soft bricked, (CM gear keeps spinning but won't boot to lock screen)
Scenario 2: Updated kernel on a non-compatible firmware.
Soft bricked, screen on 1+ logo and won't boot to lock screen.
Solution:
1. Download the toolbox from: (Make sure you download your version)
http://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987
2. Install the file.
3. Disconnect your OnePlus One from computer and power off your phone.
4. Go into Fastboot Mode (Volume Up + Power button) wait on vibrate
5. Plug in your OnePlus One.
6. Locate and open the OPO Toolbox.
7. Click Flash CM XNPH22R.
8. You should see command prompt open, just wait until it finishes doing it's thing.
9. Unplug and power off your phone.
10. Power ON your phone and wait until it prompts you re-setup your phone.
Congrats you have just fixed your phone from a soft brick. Simply follow the video from the link provided on step 1 to re-root your phone.
Note: If you have unlocked your bootloader, you do not need to unlock it again.
How to find out if you have unlocked bootloader:
1. Locate the folder where you installed the OPO Toolbox.
2. Hold Shift and right click on ANY white area within the folder.
3. Left click 'Open command window here'
4. Type:
fastboot oem device-info
If it returns True on tampered. Then you have unlocked your bootloader.
I hope this guide helps solve your soft-bricked problem. Good luck!

I suggest that a mod moves this to the General section

pandasa123 said:
I suggest that a mod moves this to the General section
Click to expand...
Click to collapse
Report the thread if you think its necessary.

Well I got this FAILED in the command line, and afterwards didnt got a re- setup...
what am I doing wrong here?:crying:

Digital Arm said:
Well I got this FAILED in the command line, and afterwards didnt got a re- setup...
what am I doing wrong here?:crying:
Click to expand...
Click to collapse
You don't have an unlocked bootloader.
Transmitted via Bacon

timmaaa said:
You don't have an unlocked bootloader.
Transmitted via Bacon
Click to expand...
Click to collapse
Thx got it:cyclops:

Scenario 2: Updated kernel on a non-compatible firmware.
Soft bricked, screen on 1+ logo and won't boot to lock screen.
Solution:
1. Download the toolbox from: (Make sure you download your version)
http://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987
2. Install the file.
3. Disconnect your OnePlus One from computer and power off your phone.
4. Go into Fastboot Mode (Volume Up + Power button) wait on vibrate
5. Plug in your OnePlus One.
6. Locate and open the OPO Toolbox.
7. Click Flash CM XNPH22R.
8. You should see command prompt open, just wait until it finishes doing it's thing.
9. Unplug and power off your phone.
10. Power ON your phone and wait until it prompts you re-setup your phone.
Congrats you have just fixed your phone from a soft brick. Simply follow the video from the link provided on step 1 to re-root your phone.
Note: If you have unlocked your bootloader, you do not need to unlock it again.
Hi i am stuck in scenario 2...I did all a u said but i cant flash CM XNPH22R ...where do i find this file...i cant find it on my phone either ..pls help ??

Thank god for this thread omg, saved my life

Locked Bootloader
This didn't work...
My phone is Soft Bricked (oneplus logo freeze) locked bootoader and usb debuging is not enabled.
What can I do to fix it??

RiccoSuave said:
This didn't work...
My phone is Soft Bricked (oneplus logo freeze) locked bootoader and usb debuging is not enabled.
What can I do to fix it??
Click to expand...
Click to collapse
But why happened this ? Whats the last actions attempted to do with the phone before the brick?
Tecleado desde mi 1+1.

Champi12301 said:
But why happened this ? Whats the last actions attempted to do with the phone before the brick?
Tecleado desde mi 1+1.
Click to expand...
Click to collapse
I did an ota update and it went in to a boot-loop, so I went into fast-boot and accidentally locked the boot-loader.
I think I have to try to hard-brick it and try the hard-brick solution with the qualcom drivers.

RiccoSuave said:
I did an ota update and it went in to a boot-loop, so I went into fast-boot and accidentally locked the boot-loader.
I think I have to try to hard-brick it and try the hard-brick solution with the qualcom drivers.
Click to expand...
Click to collapse
Then first you need to unlock the bootloader via fastboot,but that action erases all data. I assume,if you modified the boot via fastboot, USB DEBUGGING is working,so after try to do the softbrick tutorial of the thread.
Tecleado desde mi 1+1.

how do i know which tool box version is mine ?
---------- Post added at 07:42 PM ---------- Previous post was at 07:26 PM ----------
i tried the fastboot method, i successfully run alll the commands but still stuck in the bootloop.
i even tried adb, but i cant go into recovery mode for my computer to detect it. The weird thing is i can easily go into the fastboot mode but for some reason i can go into recovery mode. i tried turning of the phone by holding power button too long and then vol down + power button, still no luck, now im stuck with 2 options,
1. the toolkit solution
2. the qualcom thingy. It's been two days without my opo, and i feel so lost ! PLS if anyone sees my comments plss respond to me PLS! i willl forever be grateful to you!

deanwinchester370 said:
how do i know which tool box version is mine ?
---------- Post added at 07:42 PM ---------- Previous post was at 07:26 PM ----------
i tried the fastboot method, i successfully run alll the commands but still stuck in the bootloop.
i even tried adb, but i cant go into recovery mode for my computer to detect it. The weird thing is i can easily go into the fastboot mode but for some reason i can go into recovery mode. i tried turning of the phone by holding power button too long and then vol down + power button, still no luck, now im stuck with 2 options,
1. the toolkit solution
2. the qualcom thingy. It's been two days without my opo, and i feel so lost ! PLS if anyone sees my comments plss respond to me PLS! i willl forever be grateful to you!
Click to expand...
Click to collapse
Did you find a solution ?
I'm facing the exact same issue on my OPO.
>> bootloader locked
>> no recovery
>> impossible to unlock the bootloader
>> OPO stuck at 1+ logo and keep rebooting agin and again and again...
....i think my OPO is dead T_T
Is it a way to force the bootloader unlock ?
Please HELP !!!

Didn't work for me
I'll give the background first as it might help. I long while back I did a manual upgrade to CM12s using the guide in this video "How to Install CM12S on OnePlus One - No Root or TWRP Required, No Data LOSS" from the oneplus exclusive Youtube channel.
It worked great no problems.
I recently I got the OTA update to CM13. There were several features I didn't like so I decided to go back. I repeated the process shown in the video but now my phone gets stuck on the CM logo screen and won't go past. I tried again but the same result. Then (I can see heads shaking, sorry) I tried a factory reset from the recovery screen, still the same goes past the 1+ logo but gets stuck at the CM logo. Then I found this guide, downloaded the toolbox but when I try to plash it says "fastboot is not recognized as an internal or external command.
Any ideas?
Found a link on one of the threads here that said a guide on Reddit was useful, that didn't work as well. I am trying.

All done
davmeva said:
I'll give the background first as it might help. I long while back I did a manual upgrade to CM12s using the guide in this video "How to Install CM12S on OnePlus One - No Root or TWRP Required, No Data LOSS" from the oneplus exclusive Youtube channel.
It worked great no problems.
I recently I got the OTA update to CM13. There were several features I didn't like so I decided to go back. I repeated the process shown in the video but now my phone gets stuck on the CM logo screen and won't go past. I tried again but the same result. Then (I can see heads shaking, sorry) I tried a factory reset from the recovery screen, still the same goes past the 1+ logo but gets stuck at the CM logo. Then I found this guide, downloaded the toolbox but when I try to plash it says "fastboot is not recognized as an internal or external command.
Any ideas?
Found a link on one of the threads here that said a guide on Reddit was useful, that didn't work as well. I am trying.
Click to expand...
Click to collapse
No one replied to this but never mind, took me two days but I now have a working phone. So you can call in the dogs, cheers

hi davmeva
did you fixed your oneplus one till now or not because i have also same situation here and no success till now .
i did by mistake all this stuff and now nothing work still same condition
if you got any solution please share it

OnePlus One Screen Problems

So I have OnePlus One screen problems. First I dropped it and the screen cracked, so I had it replaced. After it got replaced I now have it back, but before screen worked and touch didn't, and now touch works and screen doesn't. The screen doesn't turn on at all, but when it is plugged in I know it is turned on and I can browse through the filesystem of the OnePlus One via my computer and also when I swipe I can hear the unlocking sound. However, data, WiFi and ADB is disabled so I can't get into there. However, saying Ok Google I can hear the response it gives me so I tried calling a friend but the call never went through. It's running CyanogenMod 12S with TWRP and Xposed flashed if that helps any. I did try following the guide using ColorOS to restore it as if it's hard bricked, but since it never seems to boot into fastboot (spamming fastboot devices in cmd never shows anything) I can't seem to do anything. I tried this on both of my computers running Windows 7, and it never shows up in fastboot, so I don't know which COM port it is to finish the guide, because it wouldn't show up abnormally. Can anyone help me figure out how to get the phone into fastboot? Thank you all so much! Also I don't really have any pictures or videos because I don't have another phone/camera to take them with. Sorry!

Update: I was able to get it into fastboot by getting it into recovery and then typing adb reboot bootloader, but that's about the extent of it. I have Bacon Root Toolkit and stuff and I'm willing to wipe my phone (because there isn't anything that I don't have a backup of) but all I really want is a solution to fix it. It did show up a few times as QHSUSB_BULK (twice, actually) but it also seems to be working, because if I take a screenshot, then reboot to recovery, I can pull the screenshot from the memory to my computer. For some reason the phone isn't showing up at all except in fastboot and recovery now.

I had the same issue with my OPO on Exodus, what I did was I pressed the power button to open the screen then unlocked the screen like usual and then brought the notification bar down and change the brightness by pressing on auto brightness button multiple times and in this whole process my screen was black then I successfully turned on my phone's screen. It also work if you just reboot the phone.
---------- Post added at 03:40 PM ---------- Previous post was at 03:38 PM ----------
Also this issue was in the ROM itself and it was fixed in an update.

Phone does not boot/Screen blacks out.

So I have a recent issue that I have not seemed to resolve. Today, under normal use, my pixel's screen went black and I have not been able to power it back on. I was using the pixel dust rom when the issue happened. I have booted into twrp and tried to factory reset but the screen even went black during the wipe. After that, I booted into the bootloader and attempted to flash google's factory image. The phone actually stays on during the bootloader session. It seemed that I was able to flash the factory rom but once I tried to reboot, the same thing happens. The boot animation will play but that's as far as it gets until the screen goes black once again.
If anyone has had this issue or if anyone has an idea on how to resolve this issue, please respond quickly.
Much Appreciated!

After the screen goes black, are you still able to communicate with the device over adb/fastboot? Have you tried reflashing the factory image (make sure the checksum is correct!)? If you put the phone in the refrigerator for a bit, will it last longer before going black (i.e., bad solder)?

post-mortem said:
After the screen goes black, are you still able to communicate with the device over adb/fastboot? Have you tried reflashing the factory image (make sure the checksum is correct!)? If you put the phone in the refrigerator for a bit, will it last longer before going black (i.e., bad solder)?
Click to expand...
Click to collapse
So during fastboot, the screen actually doesn't go black. I am still able to remain communication and That is when I tried flashing the factory image. How do you make sure that the checksum is correct? I didn't receive any errors during the flash indicating that it didn't flash properly.

If you're using Windows, Hashtab is a good, free checksum program with a GUI.
Download
Info/Review
On Google's image download page, copy the SHA-256 listed, and compare it to what you have locally (which you used to flash onto your phone).

how to boot into twrp? almost the same issue to you, adb cant find my phone.
jcd173339 said:
So I have a recent issue that I have not seemed to resolve. Today, under normal use, my pixel's screen went black and I have not been able to power it back on. I was using the pixel dust rom when the issue happened. I have booted into twrp and tried to factory reset but the screen even went black during the wipe. After that, I booted into the bootloader and attempted to flash google's factory image. The phone actually stays on during the bootloader session. It seemed that I was able to flash the factory rom but once I tried to reboot, the same thing happens. The boot animation will play but that's as far as it gets until the screen goes black once again.
If anyone has had this issue or if anyone has an idea on how to resolve this issue, please respond quickly.
Much Appreciated!
Click to expand...
Click to collapse

bush911 said:
how to boot into twrp? almost the same issue to you, adb cant find my phone.
Click to expand...
Click to collapse
If adb cant detect your phone, it looks like the only way that you're going to boot into twrp is through the bootloader mode (if you had it previously installed). Holding down volume down and power will get you into bootloader and then using the volume buttons, you can cycle through the options until you find "recovery". Pressing the power button will select that option.

post-mortem said:
After the screen goes black, are you still able to communicate with the device over adb/fastboot? Have you tried reflashing the factory image (make sure the checksum is correct!)? If you put the phone in the refrigerator for a bit, will it last longer before going black (i.e., bad solder)?
Click to expand...
Click to collapse
It looks like your freezer method works. Putting it in the freezer actually gets the phone to boot completely into google's factory image. its usuable for about a minute until the problem of freezing and turning off reoccurs. It feels like the phone warms up while running so maybe i have a hardware problem rather than software.

I seem to have the exact same problem with my pixel 32gb, my device was not rooted, nor did I had any custom recovery but the bootloader was unlocked. The issue happened one day while I was browsing the device went black right infront of me. It was not like I did a dirty flash/mod or something. I'm able to detect my pixel via fastboot, able to flash the factory image no problem, but does not boot up after successful completion of the flashing, it just goes black after "google" logo. Anyone found a solution yet??

thank you sir, I have twrp installed previously. but the screen doesnt turn on so I can't choose the recovery model. and try to hold the power button for a while the phone will become warm. no other response:crying:
jcd173339 said:
If adb cant detect your phone, it looks like the only way that you're going to boot into twrp is through the bootloader mode (if you had it previously installed). Holding down volume down and power will get you into bootloader and then using the volume buttons, you can cycle through the options until you find "recovery". Pressing the power button will select that option.
Click to expand...
Click to collapse

Thufail19 said:
I seem to have the exact same problem with my pixel 32gb, my device was not rooted, nor did I had any custom recovery but the bootloader was unlocked. The issue happened one day while I was browsing the device went black right infront of me. It was not like I did a dirty flash/mod or something. I'm able to detect my pixel via fastboot, able to flash the factory image no problem, but does not boot up after successful completion of the flashing, it just goes black after "google" logo. Anyone found a solution yet??
Click to expand...
Click to collapse
Maybe try locking the bootloader? I might try to do that since you and i both are experiencing the same problem with an unlocked bootloader. But i can't see why that would impact anything.

Phone completely black screen, how to successfully save the brick

The phone is now completely blank, and it’s useless to press any button, and you can’t enter fastboot. Use 9008 to perform steps 5 and 6 (5. Power off your phone by pressing Voice Down + Power Buttons) (6. Start update_image_EDL.bat script-it will recreate all of the partitions) The script window flashed and exited without any prompts, how can I solve it?

Same here...
I was trying to flash BlissRom 12.8 on a clean Q stock rom and when it finished flashing, I wanted to reboot recovery to slot B. Then it went black.
No button or combination works, no charging, no recognition by Windows, adb, fastboot.
The QDLoader 9008 fix (update_image_EDL.bat) returns that variable _COM is not defined.
Can anyone help?
Edit: So I can see the screen flashing very faintly every second, there seems to be some logo but I cannot identify it...
Edit2: was able to fix it with the QDLoader, but only by bridging two contacts inside the device...

got exact same situation. Booted into twrp (twrp-3.4.0-1-I01WD, no install)
installed asus rom from there (UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user) from sdcard
rebooted to bootloader (adb reboot bootloader)
I can see a faint powered by android logo every second
Maybe it's a bad idea to install stock rom from twrp.

abprie said:
Same here...
I was trying to flash BlissRom 12.8 on a clean Q stock rom and when it finished flashing, I wanted to reboot recovery to slot B. Then it went black.
No button or combination works, no charging, no recognition by Windows, adb, fastboot.
The QDLoader 9008 fix (update_image_EDL.bat) returns that variable _COM is not defined.
Can anyone help?
Edit: So I can see the screen flashing very faintly every second, there seems to be some logo but I cannot identify it...
Edit2: was able to fix it with the QDLoader, but only by bridging two contacts inside the device...
Click to expand...
Click to collapse
how did you do the bridging also is there any alternate way unless opening the device and did you wiped the vendor??

23598685 said:
got exact same situation. Booted into twrp (twrp-3.4.0-1-I01WD, no install)
installed asus rom from there (UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user) from sdcard
rebooted to bootloader (adb reboot bootloader)
I can see a faint powered by android logo every second
Maybe it's a bad idea to install stock rom from twrp.
Click to expand...
Click to collapse
I flash stock roms via unofficial TWRP regularly and so far I've never had any problem. My steps:
-flash new ROM
-flash TWRP Installer
*Reboot to recovery, slot changes
-flash kernel
-flash twrp (it may not be necessary, I do it though)
-flash magisk
And then I'm good to go.

ronak123456 said:
how did you do the bridging also is there any alternate way unless opening the device and did you wiped the vendor??
Click to expand...
Click to collapse
Bridging was easily done with a metal paper clip, but any thing similar out of conductive metal will do.
If you get your device registered as a COM device, you probably can run the script without bridging.
I don't remember wiping vendor, probably not. I had several custom ROMs installed before, but have to admit that I never really got the hang of it with those two slots and getting it finally to work felt like I did something by chance that made it work.
Maybe one additional hint: when I had the device opened, I restored the stock ROM, updated to 10, rooted, installed TWRP 3.4, and flashed BlissRom once again to see if 3.4 was the culprid and it was indeed!

abprie said:
Bridging was easily done with a metal paper clip, but any thing similar out of conductive metal will do.
If you get your device registered as a COM device, you probably can run the script without bridging.
I don't remember wiping vendor, probably not. I had several custom ROMs installed before, but have to admit that I never really got the hang of it with those two slots and getting it finally to work felt like I did something by chance that made it work.
Maybe one additional hint: when I had the device opened, I restored the stock ROM, updated to 10, rooted, installed TWRP 3.4, and flashed BlissRom once again to see if 3.4 was the culprid and it was indeed!
Click to expand...
Click to collapse
bridging with a metal paper clip without opening the phone?
my device is not recognized by the device manager no matter what i do.

any complete solution for this issue yet?
i made huge mistake that wipe vendor this time
it was been too long time to forgot about flashing from last try

ronak123456 said:
bridging with a metal paper clip without opening the phone?
my device is not recognized by the device manager no matter what i do.
Click to expand...
Click to collapse
No, of course not without opening the phone.
If you don't get the phone recognized and see a faint flickering of something like a boot image every second (I could only see this in complete darkness), then you might have the same problem as I had.
---------- Post added at 05:12 PM ---------- Previous post was at 05:11 PM ----------
chocosobo said:
any complete solution for this issue yet?
i made huge mistake that wipe vendor this time
it was been too long time to forgot about flashing from last try
Click to expand...
Click to collapse
I did what was explained here and got it working again: https://piunikaweb.com/2019/10/24/unbrick-asus-zenfone-6-asus-6z/

abprie said:
I did what was explained here and got it working again: https://piunikaweb.com/2019/10/24/unbrick-asus-zenfone-6-asus-6z/
Click to expand...
Click to collapse
is that means short that 2 pin make my phone to 9008 state from issue?
my issue is only displaying 'powered by android' at lowest brightness (barely see) for 1 sec and looping until battery out

chocosobo said:
is that means short that 2 pin make my phone to 9008 state from issue?
my issue is only displaying 'powered by android' at lowest brightness (barely see) for 1 sec and looping until battery out
Click to expand...
Click to collapse
As far as I can judge it from the distance, it sounds like the issue I had. Shorting the two pins solved it for me. But if you have warranty on the device, you may want to try returning it. Don't blame me if something goes wrong when you open your phone... If you do: take good care about the cable for the buttons not to cut it (happened to me). See this video for someone who already warned about this:
Edit: by "solved it for me" I meant that the phone was then recognized by Windows and I could run the script to reset it to stock.

Stupid me replied twice to the post...