Database Info

Stuck on red M - Dual Core Logo

Hello, i recently bought a xoom (wifi only) and now im in a quite frustrating situation.
When i got it first i flashed CWM recovery and rooted it successfully, it worked all fine for a few days.
yesterday i left the xoom on charger over night and today morning it was stuck on the red M logo saying "Dual Core Technology".
well, my situation is like:
- i can restart the xoom using power + volume up, but every time it stucks on the M logo again
- i can boot into RSD with volume up while starting
- i can boot into fastboot with volume down while starting
- i can NOT boot into recovery, when i try it gets stuck at "Reading ODM fuse: 1"
i reflashed the original ROM from MOTODEV, but the device still behaves the same like before..
normal boot gets stuck at the M logo, recovery gets stuck on Reading ODM fuse: 1, just fastboot working fine (unlocking & flashing works fine)
i also searched for similar problems on the forums, but any promising solution links to filesonic links wich are not working/down
any ideas what i can do now? any help is appreciated
thanks

unlock the bootloader and flash Rogue Recovery v1.3.0
then try to enter cwm
are u on stock? or customrom? and have u tried to lock the bootloader using a customrom? cauz locking the bootloader with customrom = not good

hi, thanks for your reply.
im on stock rom and my bootloader is unlocked. i did relock the bootloader once, but only after flashing the original ROM from MOTODEV to my device, now it is unlocked again.
i first flashed the CWM 3.2.0.0 wich is available as .img via fastboot, but it does not start (Stuck on "Reading ODM Fuse: 1").
now i flashed the recovery.img inside of Rogue Recovery 1.3.0 (since i read in the corresponding thread that it works also this way), but again: Stuck on "Reading ODM Fuse: 1"

Maybe u r 2 quick? Turn on your xoom - if u see the M wait 3 sec then press vol down and then vol up
But as i said wait 3 secs - if u r 2 quick it will stuck at entering recovery

okay, so you flashed a new recovery image (did you verify the images md5-sum?) and without trying to reboot into android you cannot get into recovery? That is really odd.
If so, I suspect that something has really screwed up your internal memory. You might be able to fix it using a factory cable.
Btw: after flashing the recovery image, does the xoom say that it succeeded in writing the recovery image to its memory?

There should be a command to reboot the device to recovery? A function reboot to recovery is possible on eos 1.0 maybe theres a adb or fastboot command 4 that?

llama-power said:
okay, so you flashed a new recovery image (did you verify the images md5-sum?) and without trying to reboot into android you cannot get into recovery? That is really odd.
If so, I suspect that something has really screwed up your internal memory. You might be able to fix it using a factory cable.
Btw: after flashing the recovery image, does the xoom say that it succeeded in writing the recovery image to its memory?
Click to expand...
Click to collapse
after flashing the recovery, i can read
"Flashing StorMgr partition recovery STATUS: done!" on the xoom
the recovery image is fine, and until today i was able to boot into CWM 3.2.0.0
what is the thing with the factory cable?

about the factory cable: seems to be a modified usb-cable with two terminals on the micro-usb end being connected with each other. As far as I read, it should enable you to write to the xooms memory as long as the hardware is still okay, no matter how much you f***ed up your software I haven't had to use yet, though.
@what Unholy said: sure, adb reboot recovery will boot your xoom into recovery, but only if you have a working android running and usb-debugging enabled.
Reading ODM Fuse: 1, according to my information, means that the thing is trying to boot into recovery. Why nothing else shows up: I have no clue.
here is a thread where some us-users had a similar problem. They tried to root their xoom after getting the 4g-upgrade and ended up with the red M-Logo. After some screwing around, they even managed to wreck the fastboot-mode, thus only enabling rsd access. So no help on that side.
What especially bothers me about your problem is that it just appeared on its own. Right before your xoom showed its issues, you weren't flashing anything. Just charging shouldn't cause any of this.
I am beginning to suspect a hardware failure that can naturally be only fixed by motorola. But that's only my current opinion.
If I was you, I would try downloading the files from motorola again, check their md5-sums and then flash those using fastboot using these instructions.
If that still doesn't help, there may be a way to get a .sbf file from motorola for your xoom. That is a file which can be flashed using the windows software rsd-lite, but I haven't used that in a long time and it has been reported to not work really well with the xoom.
Next, I'd research a little on the factory cable thing, but I'd be careful with that.
As a last resort, I'd send the xoom to my dealer. Unluckily, there is a way to determine if you have had your bootloader unlocked, at least as long as fastboot is still working...

About the factory cable - with that cable u can flash your xoom if nothing else is working anymore (adb or cwm)
To build a factory cable u have to tie pin 1 (+) to pin 4 on the micro usb plug
I build one but never used it and hope i will never have to

i did download the original ROM from motodev again, checked the md5, and flashed according to the tutorial posted by llama-power, but the device still wont boot neither the rom nor into recovery.
since its now on 15% battery i think i will let it run out of power and then try to boot again...

The_Revenge said:
i did download the original ROM from motodev again, checked the md5, and flashed according to the tutorial posted by llama-power, but the device still wont boot neither the rom nor into recovery.
since its now on 15% battery i think i will let it run out of power and then try to boot again...
Click to expand...
Click to collapse
does the xoom charge when connected to ac power? I know that other devices (cellphones) wouldn't charge without working os.
However, I do not think that letting the battery run low will help you. Lithium ion batteries should not be low discharged as that will most likely destroy them and lead to a massive risk of explosion upon the next charge. Because of that, devices powered by a lithium ion battery will power down before depleting the battery, the xooms mainboard itself will most likely still be supplied with some power.
If you really want to cut the power supply to the mainboard, you'll have to open the xoom (two screws) and unplug the battery (the connector is held down by another two screws) for a couple of seconds. (here is a teardown of the xoom with pictures)
by the way, if you want to track your battery status without booting android (as that would obviously not work), you can use fastboot getvar battery-status.

well my xoom actually charges when i connect it to power, and the LED also lights up, so (thinking of what you said) it seems like the os and everything still is present, just like the bootloader cant load it or something?! is there maybe any way to update the bootloader itself?
yeah, i can also check the battery status when i'm booting with power and volume up (RSD) =)
well i'm actually thinking about disconnecting the battery, but i'm a bit unsure, i will study that now..

The_Revenge said:
well my xoom actually charges when i connect it to power, and the LED also lights up, so (thinking of what you said) it seems like the os and everything still is present, just like the bootloader cant load it or something?!
Click to expand...
Click to collapse
not neccessarily. Maybe the xoom just doesn't need any software to charge the battery.
The_Revenge said:
is there maybe any way to update the bootloader itself?
Click to expand...
Click to collapse
don't know, but since fastboot works I suspect that the bootloader itself is still fine.
The_Revenge said:
well i'm actually thinking about disconnecting the battery, but i'm a bit unsure, i will study that now..
Click to expand...
Click to collapse
have fun, but I wouldn't get my hopes up too high. I still suspect some sort of a hardware failure... Also, opening the device might leave some traces (botched screws, etc) that could lead motorola to say that you messed with your xoom if you should finally decide to send it in

well thats the same i thought about opening the device..
do you know any way to dump the partitions to the pc (maybe with fastboot?)

The_Revenge said:
do you know any way to dump the partitions to the pc (maybe with fastboot?)
Click to expand...
Click to collapse
nope, not without a working recovery.
fastboot erase partition_name should be able to clear your partitions, though. Replace partition_name with boot, system, userdata, cache or recovery

http://www.xoomforums.com/forum/xoo...ery-stuck-red-m-logo-fastboot-works-help.html
apparently that user seems to have had the same problem, he says he fixed it using 1.35 Everest Bootloader (SBF).
i also had that idea some time earlier and found a thread with the SBF files here on xda, also for the wifi model, but the only links i could find to SBF files were filesonic links wich are not working ._.
i'm now up to googling for SBF files (for the wifi only model), if i cant find anything promising i'll send it back tomorrow.
btw, erasing the partitions does not help, i've already tried that

Have u done the lte update?

UnholyX said:
Have u done the lte update?
Click to expand...
Click to collapse
he's got an wifi-only model (as stated in post #1) and is from germany (at least that's what his location and flag says). LTE upgrade is neither available in germany, nor for wifi-only-xooms. So I'd say no
@OP: that sounds quite promising. .sbf-files still seem to be available on some sites, downloading one for my xoom right now, just in case that site goes down in the future...

Yes he got the wifi version like me but something must happened ,-)
I also charge my xoom and nothing happens. He got wifi version but he maybe flashed a false update or so
There r people flashing stingray instead of the wingray version etc. - just asking what happened before - thats the reason - something must happened before ;-)

it seemed promising, but i cannot find any usable sbf file
i think i'll send the unit back tomorrow

[Q] im in dire need of help please!

Here is the rundown. I have the d 850 LG g3. Was planning on unrooting phone from towel root and rerooting it using towelroot once I found the mod I wanted. I have the latest version of twrp loaded as well. On my way home from work yesterday I was riding my motorcycle and listening to music, all the sudden the music stops so I pull over to see what happened and look to see that my phone has somehow opened twrp. I get home and try to reboot phone and it loads right back into twrp. I did a backup. Restarted phone to same results. I factory reset phone thinking that would work. NOPE. Straight back into twrp so I plug phone into computer to see what's on it. It appears all my games music LG backup etc is still there's why can't I get out of twrp. Could I have accidentally wiped everything while in my pocket? Can I fix this problem or do i now have a $500 paperweight? Please please folks out there in xda land help me out. I've got experience in rooting with my htc m7 so am familiar with this stuff. Any help would be greatly appreciated. Thanks for your time.

dcm1200 said:
Here is the rundown. I have the d 850 LG g3. Was planning on unrooting phone from towel root and rerooting it using towelroot once I found the mod I wanted. I have the latest version of twrp loaded as well. On my way home from work yesterday I was riding my motorcycle and listening to music, all the sudden the music stops so I pull over to see what happened and look to see that my phone has somehow opened twrp. I get home and try to reboot phone and it loads right back into twrp. I did a backup. Restarted phone to same results. I factory reset phone thinking that would work. NOPE. Straight back into twrp so I plug phone into computer to see what's on it. It appears all my games music LG backup etc is still there's why can't I get out of twrp. Could I have accidentally wiped everything while in my pocket? Can I fix this problem or do i now have a $500 paperweight? Please please folks out there in xda land help me out. I've got experience in rooting with my htc m7 so am familiar with this stuff. Any help would be greatly appreciated. Thanks for your time.
Click to expand...
Click to collapse
Make backup and try repair your system partition with lg flash tools and tot or if you have twrp. Try flash any rom stock bumped

Try this..
dcm1200 said:
Here is the rundown. I have the d 850 LG g3. Was planning on unrooting phone from towel root and rerooting it using towelroot once I found the mod I wanted. I have the latest version of twrp loaded as well. On my way home from work yesterday I was riding my motorcycle and listening to music, all the sudden the music stops so I pull over to see what happened and look to see that my phone has somehow opened twrp. I get home and try to reboot phone and it loads right back into twrp. I did a backup. Restarted phone to same results. I factory reset phone thinking that would work. NOPE. Straight back into twrp so I plug phone into computer to see what's on it. It appears all my games music LG backup etc is still there's why can't I get out of twrp. Could I have accidentally wiped everything while in my pocket? Can I fix this problem or do i now have a $500 paperweight? Please please folks out there in xda land help me out. I've got experience in rooting with my htc m7 so am familiar with this stuff. Any help would be greatly appreciated. Thanks for your time.
Click to expand...
Click to collapse
Somehow your rom partition/system seems to be corrupted. If you want to try and save your data, Please copy the downloaded version of your current rom and dirty flash (flash without wipe) and try to get back into the system. If you do not have your rom in your internal memory, try adb sideload or try to copy it to your external SD card and install from there.
You can also try to copy your stuff over to the external SD card using the file manager in TWRP and then wipe and install your rom.
If none of these wor, you still can flash factory image by process defined in the this thread: http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827
I believe you can still rescue your phone. Please let us know how it went.

I tried flashing a ROM with gaps and rebooted and it still senT me back into TWRP.

Maybe his phone tried to download and install the OTA? Try this also if the above doesn't work. http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508

harihacker said:
Somehow your rom partition/system seems to be corrupted. If you want to try and save your data, Please copy the downloaded version of your current rom and dirty flash (flash without wipe) and try to get back into the system. If you do not have your rom in your internal memory, try adb sideload or try to copy it to your external SD card and install from there.
You can also try to copy your stuff over to the external SD card using the file manager in TWRP and then wipe and install your rom.
If none of these wor, you still can flash factory image by process defined in the this thread: http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827
I believe you can still rescue your phone. Please let us know how it went.
Click to expand...
Click to collapse
Will do. Going home in a bit to try it out. Will keep u posted and thanks to everyone who has given advice. Ill be happy to get it back to stock and then starting over from scratch with a good custom from and kernel. Quick question, I tried flashing the custom illusion rom with gapps. Is that rom a bmp.img?

No.. A Zip file.
dcm1200 said:
Will do. Going home in a bit to try it out. Will keep u posted and thanks to everyone who has given advice. Ill be happy to get it back to stock and then starting over from scratch with a good custom from and kernel. Quick question, I tried flashing the custom illusion rom with gapps. Is that rom a bmp.img?
Click to expand...
Click to collapse
The rom is normally a zip file.
If you already tried to flash a rom (other than your current one) I suggest you try the "back to stock" thing that was referred in my last post. If you have all the drivers in place and do the process correctly (preferably from a Windows 7 laptop), Your phone will be burst back to life in no time.. Good luck..!!

harihacker said:
The rom is normally a zip file.
If you already tried to flash a rom (other than your current one) I suggest you try the "back to stock" thing that was referred in my last post. If you have all the drivers in place and do the process correctly (preferably from a Windows 7 laptop), Your phone will be burst back to life in no time.. Good luck..!!
Click to expand...
Click to collapse
Following the steps and just to part where I press volume up and plug into USB port and it said download for a second then jumped to firmware update do not unplug until process is complete. Its been a couple of minutes and in still at zero %

Good..
dcm1200 said:
Following the steps and just to part where I press volume up and plug into USB port and it said download for a second then jumped to firmware update do not unplug until process is complete. Its been a couple of minutes and in still at zero %
Click to expand...
Click to collapse
That is exactly what you want. You are now in download mode. So please proceed to next step (i believe the next step is on the laptop).

But the firmware update hasn't even gotten to 1% yet and I don't know how to get back to download mode. I don't know if unplugging device and trying again will mess it up even more. Device manager didn't pop up on computer either

dcm1200 said:
But the firmware update hasn't even gotten to 1% yet and I don't know how to get back to download mode. I don't know if unplugging device and trying again will mess it up even more. Device manager didn't pop up on computer either
Click to expand...
Click to collapse
Device manager wont "pop up".. you need to pull it from control pannel. Once you confirmed/changed the port to 41, i believe you can pull the usb, wait for 5 sec and put in back in. Follow exactly as instructed in the thread and you should be fine.
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
Also firmware update starts after the "usb pull" and re-plug in.

harihacker said:
Device manager wont "pop up".. you need to pull it from control pannel. Once you confirmed/changed the port to 41, i believe you can pull the usb, wait for 5 sec and put in back in. Follow exactly as instructed in the thread and you should be fine.
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
Also firmware update starts after the "usb pull" and re-plug in.
Click to expand...
Click to collapse
I haven't gotten a chance to pull it up. IT goes to download mode and then right into firmware update. I'm looking on control panel for my phone so I can go into port but its not showing up in control panel

dcm1200 said:
I haven't gotten a chance to pull it up. IT goes to download mode and then right into firmware update. I'm looking on control panel for my phone so I can go into port but its not showing up in control panel
Click to expand...
Click to collapse
1) The "firmware update" page is the download mode.
2) Control Panel -> Device Manager -> Ports -> Select LG one -> Port Settings -> Advanced -> look for "Com Port Number" on left hand side.
---------- Post added at 04:32 PM ---------- Previous post was at 04:29 PM ----------
If your device does not show in the Ports section, that means that your drivers are not installed correctly. Did you install the one given in the thread?
---------- Post added at 04:39 PM ---------- Previous post was at 04:32 PM ----------
Try these drivers if you cant find the right one: http://www.koushikdutta.com/post/universal-adb-driver

Yes drivers showed in port. Followed instructions according to LG flashtool and in getting a message saying that lgusb/ parallel lock key is not detected

?
dcm1200 said:
Yes drivers showed in port. Followed instructions according to LG flashtool and in getting a message saying that lgusb/ parallel lock key is not detected
Click to expand...
Click to collapse
At what stage of the process are you getting this error? Please refer to the step number in the "back to stock" thread.

Lg flash tool is saying authentication failed

Re-try.
dcm1200 said:
Lg flash tool is saying authentication failed
Click to expand...
Click to collapse
Again, at what stage did you get the error? Which step?
Did you install the driver i quoted above? If you did in between the process, please pull the battery and try from the beginning if the flash process did not start.

harihacker said:
At what stage of the process are you getting this error? Please refer to the step number in the "back to stock" thread.
Click to expand...
Click to collapse
Step 12 go to LG flash tool and run as administrator.

DLL
dcm1200 said:
Step 12 go to LG flash tool and run as administrator.
Click to expand...
Click to collapse
Did you replace the DLL file in the folder as instructed? Did you give the computer's correct admin password? Are you logged in as an admin in the laptop?

harihacker said:
Did you replace the DLL file in the folder as instructed? Did you give the computer's correct admin password? Are you logged in as an admin in the laptop?
Click to expand...
Click to collapse
I got in

Pixel will not power on after TWRP 3.2.1.2 flash

Pixel not powering on, I flashed TWRP 3.2.1.2 and tried to flash superuser 2.82 SR5. Superuser never installed but the phone seemed to be working fine, I went back into twrp a few times and everything seemed fine. So i was trying to bootback into twrp one more time to try and install supersu from otg usb drive and just after selecting recovery mode it shut down and now it will not power back on?? any help from anyone, I tired plugging it into the wall and it does not seem to power on at all or even charge. Thanks in a advance for any help!

I had an issue like this. Hold down the power button and down volume button at the same time. Keep holding it down. It took 20-30 seconds for me.

By the way, what version of Android are you on? SuperSU won't work on Android 8.1. You have to use Magisk. You can use the latest Magisk but if you want to use @Chainfire's FlashFire app, you have to use Magisk v14.2.

I think flashing SuperSU is what broke your ****. Try flashing SuperSU uninstaller and then reboot into recovery and flash magisk

KittyRgnarok said:
I think flashing SuperSU is what broke your ****. Try flashing SuperSU uninstaller and then reboot into recovery and flash magisk
Click to expand...
Click to collapse
His phone won't turn on lol

shagbag913 said:
His phone won't turn on lol
Click to expand...
Click to collapse
He didn't give any details as to what he means by won't turn on. To me that means system isn't working and bootloader and recovery are intact. Your phone doesn't need to boot properly to flash a zip

KittyRgnarok said:
He didn't give any details as to what he means by won't turn on. To me that means system isn't working and bootloader and recovery are intact. Your phone doesn't need to boot properly to flash a zip
Click to expand...
Click to collapse
He said his phone will not power on. He also said he plugged it in and It still wouldn't power on. It sounds to me that his phone won't power on lol.

shagbag913 said:
He said his phone will not power on. He also said he plugged it in and It still wouldn't power on. It sounds to me that his phone won't power on lol.
Click to expand...
Click to collapse
Look at you being helpful and contributing to the thread. Would you rather me suggest literally nothing like you or assume that he is under recoverable circumstances and provide a potentially simple fix? He has not indicated whether he has tried to boot fastboot or recovery.

KittyRgnarok said:
Look at you being helpful and contributing to the thread. Would you rather me suggest literally nothing like you or assume that he is under recoverable circumstances and provide a potentially simple fix? He has not indicated whether he has tried to boot fastboot or recovery.
Click to expand...
Click to collapse
"So i was trying to bootback into twrp one more time to try and install supersu from otg usb drive and just after selecting recovery mode it shut down and now it will not power back on??"
---------- Post added at 11:51 PM ---------- Previous post was at 11:47 PM ----------
Aphex^ said:
Pixel not powering on, I flashed TWRP 3.2.1.2 and tried to flash superuser 2.82 SR5. Superuser never installed but the phone seemed to be working fine, I went back into twrp a few times and everything seemed fine. So i was trying to bootback into twrp one more time to try and install supersu from otg usb drive and just after selecting recovery mode it shut down and now it will not power back on?? any help from anyone, I tired plugging it into the wall and it does not seem to power on at all or even charge. Thanks in a advance for any help!
Click to expand...
Click to collapse
I would try holding the power button for a good 5 mins, some say that can turn it back on. If that doesn't work plug it into a PC and look to see what its name is on your PC. If it says "Qualcomm HS-USB QDLoader 9008", unfortunately its hard bricked.

Actually
KittyRgnarok said:
Look at you being helpful and contributing to the thread. Would you rather me suggest literally nothing like you or assume that he is under recoverable circumstances and provide a potentially simple fix? He has not indicated whether he has tried to boot fastboot or recovery.
Click to expand...
Click to collapse
Your actually are talking about the problem I just did a couple of hours ago...I was so mad...Like WTH did I do wrong. THANK YOU FOR YOUR HELP

Hello everyone,
If you are trying to flash TWRP to an android oreo 8.1 google pixel, it will not work, so DON'T ATTEMPT IT! I have tried this before and your best bet as of now is to flash the bootloader back to stock. If you need to use it for whatever reason just fastboot into it.
Also, SuperSU doesn't work with Android 8.1 Oreo, as it isn't compatible. The new method is using Magisk Manager.
If you can't turn on your phone, then this means your bootloader is completely damaged and you will need to replace your phone.

mcbeat257 said:
Hello everyone,
If you are trying to flash TWRP to an android oreo 8.1 google pixel, it will not work, so DON'T ATTEMPT IT! I have tried this before and your best bet as of now is to flash the bootloader back to stock. If you need to use it for whatever reason just fastboot into it.
Also, SuperSU doesn't work with Android 8.1 Oreo, as it isn't compatible. The new method is using Magisk Manager.
If you can't turn on your phone, then this means your bootloader is completely damaged and you will need to replace your phone.
Click to expand...
Click to collapse
You definitely can flash twrp on an 8.1 pixel. I have it right now. Also, most of the time that does mean it is hard bricked, but sometimes these phones can trick you. If you think your phone is bricked because the screen is off and there is no response, hold the power button down for 1 to 2 minutes, SOMETIMES it can come back on.

I had a similar issue where the phone would not turn on after I was loading TWRP via Fastboot. I went to sleep that night thinking I had bricked it. Held every button down for at least 90 seconds and every combination of buttons. Woke up in the morning to try it one more time before I gave up and it easily booted up but only had 1% battery. I had charged it fully before trying to load TWRP. I plugged it in and charged it and was good to go including Fastboot booting into TWRP and then flashing SuperSu and the Xposed framework. Both work fine. Rooted and using Xposed modules.
I came here to see if I could flash TWRP to the phone. Apparently I can, but would love to know what the steps are so as not to screw anything up or mess up which partition, etc.

What the freak did I just read. Seems to me the issue is not twrp but whatever people are trying to flash using twrp. @mcbeat257 TWRP works just fine. Been running the latest for several months now. Works on 8.1 both stock and custom roms, even on Android P DP2. So If you can't make it work while several others users have then I would say you're not eligible to give advice as to say "do not attempt it!". You must be doing something wrong. Please stop spreading false information. I'd be happy to help you out if you describe the procedure you've been going about to flash it to make it work.
As to the OP, try as shagbag913 told you to do. Press the power button for some minutes. Or try power-button+volume down (See if you manage to get into the bootloader menu). If it doesn't work then connect your device to your computer and see if it's recognized. If it's flat dead and won't turn on then motherboard might be toast. If it's recognized as shagbag913 said as a Qualcomm HS-USB QDLoader 9008 then it's hardbricked.
---------- Post added at 01:59 PM ---------- Previous post was at 01:39 PM ----------
724A said:
I had a similar issue where the phone would not turn on after I was loading TWRP via Fastboot. I went to sleep that night thinking I had bricked it. Held every button down for at least 90 seconds and every combination of buttons. Woke up in the morning to try it one more time before I gave up and it easily booted up but only had 1% battery. I had charged it fully before trying to load TWRP. I plugged it in and charged it and was good to go including Fastboot booting into TWRP and then flashing SuperSu and the Xposed framework. Both work fine. Rooted and using Xposed modules.
I came here to see if I could flash TWRP to the phone. Apparently I can, but would love to know what the steps are so as not to screw anything up or mess up which partition, etc.
Click to expand...
Click to collapse
There is an entire thread for twrp and how to flash: https://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314

[Help] Super Hard Brick - Stuck in EDL and no button response at all + SHA256 fail

Hi everyone,
I'm having an issue with my 7 pro (1911). This is my 1st Oneplus as I used a Mi 5 before, the flash procedure was much easier without this A/B mess.
So I somehow messed up a new install of pixel experience with blu_spark kernel and twrp and found myself with the qualcomm crash error. Trying to get back into fastboot with the button combination (was able to save it once in it) the phone restarts and got stuck in edl mode. I noticed it's recognized as 9008 in the PC so I said okey this is nothing I'll just use the MSMTool to get it back on again.
Went through the xda Mega thead procedure, had no problem getting the phone to connect to the tool, however, first unexpected thing I encounter is the fact it stops with a SHA256 doesn't match error, and fails to send op2.img. I verified the ops file to make sure it has no errors and it was good. I then checked "disable sha256" box and it goes normally with the flash this time. Except in the end instead of restarting into the system it restarts into edl mode again and if the cable is still attached starts flashing again. This loop keeps going on forever.
I checked everywhere the only other thing I found that hints at a possible solution was doing an SMT download (based on this thread from OP6). Having an EFS backup already in one of my TWRP backups I went ahead with the procedure. Everything goes normally with the sha256 box disabled. it takes longer than upgrade mode (it flashes also to b slot), it finishes fine till the end. I disconnect the phone to boot it but it's still stuck in EDL mode!!! pressing any combination of button only keeps restarting the phone in EDL; when connected to the pc you see it going off then on in device manager.
The only idea I have left is waiting for battery to die, which could take forever and I have no idea if that'll work
Things I tried/used :
Qualcomm drivers are the latest from microsoft server v2.1.2.2. Tried some other ones but no change.
Pressing any combination of buttons (up + down + power, up + power, down + power) for multiple minutes doesn't change anything (it only hurts your fingers lol)
Before the issue the phone was at around 40%, I don't think the problem was battery charge, but I still tried connecting to official charger for some time but no boot.
I tried using multiple cables, ports (usb 3 and 2 from front of pc), tried on a laptop with both usb 2 and 3, all give me the same results, sha256 fails, without the check it flashes but no boot or response.
I redownloaded the MSMTool multiple times from both the Mega thread and newer one with oos 10 images, even the chinese image, all of them give the exact same issue. The only one that didn't work was the TMobile image, saying it's the wrong image (tried it just to be sure my phone wasn't originally a TMO converted, as it's 2nd hand).
Tried starting a normal flash in MSMTool and leaving it on that loop (flash, finish, restart again in EDL, flash...) all night but still found it flashing in the morning, never booted to system.
I found some people in the forums having the same symptomes (but quite rare compared to others), only 2 said they found a solution:
OP7P (this guy fixed the issue by charging his phone) https://forum.xda-developers.com/showpost.php?p=80329855&postcount=83
OP6T (this guy discharged his phone completely then connected it and it booted) https://forum.xda-developers.com/showpost.php?p=79079192&postcount=5
OP7 https://forum.xda-developers.com/showpost.php?p=81183765&postcount=41
OP7 https://forum.xda-developers.com/showpost.php?p=81185793&postcount=43
OP6 https://forum.xda-developers.com/showpost.php?p=81308571&postcount=88
OP6 https://forum.xda-developers.com/showpost.php?p=79445923&postcount=203
I'm making this thread maybe someone who had the same issue can show me how he solved it, or if not and my last resort works (complete battery discharge) hopefully stays as a helpful history to someone else.
Thanks.

Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.

Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
EDIT: Sorry for the accidental double post

Charnet3D said:
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
EDIT: Sorry for the accidental double post
Click to expand...
Click to collapse
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.

ANY NEWS>?
i also have an OP6T
used MsmDownloadTool V4.0_factory_mcl_op1_patched
with
rev_OverSeas_181226_1920_release_disable_OTA-BLOCK_Signed_fp1812260627_cve2018-12-01_ufs_9.0.11
and
fajita_41_O.18_181226.ops
phone was stock.
Proceeded to flash custom rom etc.
Now since then i decided i wanted stock again to try new custom rom etc. and,
i booted twrp and just wiped everything like a mad man.
i have had this happen before.
Currently, it will and can boot into any mode such as fastboot recovery(TWRP) edl and device state/secureboot are both unlocked/enabled
TRY TO LET IT DIE AND PUT RUBBERBANDS OLONG THE PHONE SO THE VOLUME AND POWER BUTTONS ARE HELD DOWN GOOD AND LET IT SIT FOR A DAY TO DIE.
After you do that let it sit for a bit and its dead. take off the bands and let it sit for another half a day and redo the bands to make sure its been reset and is indeed complete dead. repeat, whatever.
when its surely dead and been reset, THE ONLY thing you can try is
plug it in and almost at the same time (not simultaneously, but sequentially)
YOU NEED TO HOLD VOLUME UP+DOWN at the same time RIGHT AFTER YOU PLUG IT IN LITTERALLY. And, it should display the 1plus logo briefly and boot into fastboot mode.(i had to do this after wiping rom etc via twrp an became stuck in edl mode)
from there i booted twrp
(was my reccovery still)
mind that i wiped everything like a mad man and i lost my ADB AND FASTBOOT AND AS WELL AS MY EDL MODE PRIVILEGES(2 PCs, a couple cables tried and the phone is still not being recognized in any of the mentioned modes ), and after doing what i mention if you can get into fastboot mode you may be in luck, however if you can get back into any other mode.(Or fastboot flash a stock rom, adb sideload etc)
im still here waiting my usb otg type c because the usb wont recognize with the adapter to micro usb. Now ive never had a usb otg type c adapter before, but i know i could never get the micro usb (universal) to adapt my otg with a, "type C" type adapter and see the storage device(usb) being recognized by android. So i will reply when it arrives and i can attempt to flash stock again via otg twrp with oos zip. (THIS HAS TO BE AN A10 ISSUE WITH TWRP BEING FAIRLY RECENT IN RELEASES AND CAUSING IT TO NOT BE RECOGNIZED AFTER PERFORMING A, "FULL WIPE")
hopefully the otg for usb c is going to be recognized by twrp still.
if all else fails and your still under contract warranty, just light the **** on fire and run it over and pay the $40 deductable and take it as a $40 lesson and have them send you a new one(or upgrade depending on eligibility etc.)
---------- Post added at 10:06 PM ---------- Previous post was at 10:00 PM ----------
billyt1 said:
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
Click to expand...
Click to collapse
agree
im using a tmoblie variant with msm from above
---------- Post added at 10:27 PM ---------- Previous post was at 10:06 PM ----------
https://twitter.com/NTAuthority/status/1115496145051164672

billyt1 said:
Did you say you was able to get to fastboot mode if so jus boot twrp image then flash twrp image.zip from the xda. Then do a full wipe then download download a ota zip from xda and flash it. That's how I got out of edl mode.
Click to expand...
Click to collapse
No still stuck in EDL mode.
Johndoesmoked said:
TRY TO LET IT DIE AND PUT RUBBERBANDS OLONG THE PHONE SO THE VOLUME AND POWER BUTTONS ARE HELD DOWN GOOD AND LET IT SIT FOR A DAY TO DIE.
After you do that let it sit for a bit and its dead. take off the bands and let it sit for another half a day and redo the bands to make sure its been reset and is indeed complete dead. repeat, whatever.
when its surely dead and been reset, THE ONLY thing you can try is
plug it in and almost at the same time (not simultaneously, but sequentially)
YOU NEED TO HOLD VOLUME UP+DOWN at the same time RIGHT AFTER YOU PLUG IT IN LITTERALLY. And, it should display the 1plus logo briefly and boot into fastboot mode.(i had to do this after wiping rom etc via twrp an became stuck in edl mode)
Click to expand...
Click to collapse
I don't know if you saw my last comment but I had even opened the phone up to disconnect the battery ribbon, hoping that would get it out of EDL but it didn't. However I didn't do the trick with the buttons when connecting it, I'll try this after disconnecting the battery. Also if that didn't work I'll leave it on rubber bands like you said, nothing to lose anyway. Thanks for the tips. I'll let you know what's up.
How did you know when the phone was dead while on rubber bands, do you verify if it still gets detected on the PC ?

Yeah i had did the rubberbands for a lil more than couple days and like i said i let it sit for about a day without the bands on after i had a good 20+ hours with em on then reapplied bands for about 20 hours.my phone was completely discharged during that process( OP6T).
Upon doing this i lost access to my recovery img.
Phone only boots fastboot (even if i choose recovery, it was previously working)
So now i still cant recognize in fastboot or edl.
GOT my OTG type c and put oos on usb, but as i said now my twrp isnt booting, so i shouldnt have depleted the battery as now i have no possible recovery access modes . Aside from that, im trying to figure out more info on the device and will reply in a day with what i may come to find out.
My phone did get detected because it started up as soon as i plugged into pc.
battery seems un-accessible but may have to take this apart.
I am figuring this out and i will get back to you. I need more tech assistance from a friend in the repair industry to disassemble without destroying it tomorrow or sometime friday.
This is going to have to be some sort of an intricate process to diagnose this supposed "HARD BRICK"
:Have to correct myself
talked to my brody at tmobile to see wassup with the warrenty etc.
basically its not covered under warrenty when you mess with software, blah blah i figured anyway, and he basically advises (OR more so "i didnt tell you anything like that!"- laughing) to literally run it over with your car or just smash the screen, and file the claim without issue...
BUT THE ISSUE IS ITS GONN COST YOU $99 to get a new OP6T via Assurant
your device might be the same, or even more costly,
i would prefer to avoid all costs, spending more money, not trying to..

Charnet3D said:
Hi again,
Updating my thread with what I could do lately:
I opened the phone up, anxious to try disconnecting the battery and seeing if it makes any difference. To my surprise that also did no change at all.
After some time working with NerdgOd56 from the Reddit Discord we tried many things, among them reading back the memory using MSM Tool. There was also a python script that enabled reading a provision xml file that's used by the tool to flash everything. This file mentions where in the OPS file each image is. So after some fiddeling with the OPS using a hex editor, I found that there are quite some differences with the images I read from the phone, this hints at a possible flash memory corruption. Though this needs to be confirmed by someone who has a clean phone, whether the images are supposed to be exactly the same or probably they're encrypted when transfered to the phone.
So right now I'm starting a search for a motherboard locally, hoping to find something.
Thanks to all the guys from discord who gave their time to my cause NerdgOd56, DarkPhoenix and the others on the OP7 channel.
Click to expand...
Click to collapse
I wonder if you've managed to solve your problem. I have the same error SHA256 on Oneplus 7 Pro

Lefren said:
I wonder if you've managed to solve your problem. I have the same error SHA256 on Oneplus 7 Pro
Click to expand...
Click to collapse
facing same issue with oneplus 7 pro 1910, tf is wrong with this cursed series lol

thedeadfish59 said:
facing same issue with oneplus 7 pro 1910, tf is wrong with this cursed series lol
Click to expand...
Click to collapse
Yeah so sad, probably the internal memory has a slight % chance it gets corrupted or something...
Since my story in the OP I bought a used 1913 that's a bit cheaper coz of external scratches and took its motherboard for my cleaner original phone. It's been working like a charm since.

hi everyone last night i plug my phone for charging after a while i came back and see crash dump mode i switch off the and try to unbrick via msm tool 1st attempt everything fine auto reboot after progress complete it stuck in oneplus logo after that i tried to redo all thing now i faced this error on MSM TOOL PLEASE HELP ME I CHANGED THE CABLE USB PORTS DRIVER REINSTALL BUT STUCK AT THIS POINT. when i uncheck sha256 downloading start but it does not stop again and phone did not auto reboot help please

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...