So my phone is stuck in an endless loop where it keeps going back to TWRP. I tried using the MSM tool, and its not recognizing the image on my phone it says. Not sure where to go from here.
Bildo41383 said:
So my phone is stuck in an endless loop where it keeps going back to TWRP. I tried using the MSM tool, and its not recognizing the image on my phone it says. Not sure where to go from here.
Click to expand...
Click to collapse
How did you get into the loop? Were you flashing something? Might be worth going into TWRP and flashing the full system image.
Pretty sure you are using msmdownloadtool wrong. Completely shut down the phone. Make sure to DISCONNECT the phone form pc. Hold vol up and vol down for 5 sec. And it should unbrick hour phone
Hold power and volume up till the phone shuts off...
Now with the device completely powered off hold both volume buttons down at the same time for about five seconds then while continuing to hold both volume buttons plug USB in from pc to your phone the screen will be black and it's normal.... After this it should be showing up in the MSM tool....
It showed up in the MSM tool, but when i click start it goes for 4 seconds and then tells me that it doesnt recognize the image.
dunjamon said:
How did you get into the loop? Were you flashing something? Might be worth going into TWRP and flashing the full system image.
Click to expand...
Click to collapse
Yes, i was on the NoLimits rom and wanted to stop using it since i felt it was impacting a few things on my phone that i didnt like, but i really enjoyed Viper4Arise. So i was trying to flash V4A and after i was done flashing it wouldnt load past the unlocked bootloader screen, and i was stupid enough to not create a backup before i started because i didnt think V4A would be that harmful. After trying to wipe my phone and start fresh, i got stuck in the recovery loop.
dunjamon said:
How did you get into the loop? Were you flashing something? Might be worth going into TWRP and flashing the full system image.
Click to expand...
Click to collapse
Also, whats a good thread to get the system image?
Bildo41383 said:
Also, whats a good thread to get the system image?
Click to expand...
Click to collapse
If you are booting into recovery, first try formatting your data. In OnePlus's recovery, select English, and somewhere there is an option to "ERASE EVERYTHING." This will format the partition for OOS. On TWRP, go to Wipe--> Format Data. That may fix the bootloop.
If this does not fix it, the MSM download tool is a good option, however, I see it did not work for you. You can download OnePlus's official ROM from here, and for that, you want to flash it in TWRP like any other mod, then reboot. If you are still boot-looping after that, try formatting your data again for good measure.
For the MSM Download tool, you MUST be on Windows, and you must have extracted the archive fully, which can be done by right-clicking on the ZIP and selecting "Extract all." Then, turn the phone completely off, no USB attached. Press and hold Volume Up + Volume Down, and connect the device to the computer. You should then be able to launch the MSM tool, selecting the normal one for the stock variant, and the factory_mcl for the McClaren variant. If your device does not show up, make sure you have installed Qualcomm drivers from here.
Good luck and I hope you get your phone working!
Bildo41383 said:
So my phone is stuck in an endless loop where it keeps going back to TWRP. I tried using the MSM tool, and its not recognizing the image on my phone it says. Not sure where to go from here.
Click to expand...
Click to collapse
That happened to me as well with the 9.0.1.2 version.
What I did is I used an older version 9.0.1.1 works all the time. No matter what Rom you had previously installed, So try an older version.
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
This saved my butt 100 times...whenever I mess with slot A and B and end up booting to recovery mode again n again
Related
I have a Verizon LG G2 I tried to flash my backed up stock recovery with Flashify so I could flash the most recent OTA. After accepting the OTA update my phone restarted, tried to install the update, hung at a black screen but was still turned on. If I power it off and back on it shows the LG logo, some white text, then goes to the same black screen. What appears to be happening is that my backup recovery did not restore properly and it's hanging when it tries to go into recovery. It's almost like my recovery partition is blank.
I've tried to follow the instructions to flash back to stock, but I do not believe I'm actually able to get my phone into download mode. When it is plugged into my windows 7 computer with the LG drivers installed it shows up in device manager as QHSUSB_BULK.
Is there any way for me to push a stock recovery, or even a custom recovery to my phone so I can somehow salvage it, or am I permanently bricked?
toopty said:
I have a Verizon LG G2 I tried to flash my backed up stock recovery with Flashify so I could flash the most recent OTA. After accepting the OTA update my phone restarted, tried to install the update, hung at a black screen but was still turned on. If I power it off and back on it shows the LG logo, some white text, then goes to the same black screen. What appears to be happening is that my backup recovery did not restore properly and it's hanging when it tries to go into recovery. It's almost like my recovery partition is blank.
I've tried to follow the instructions to flash back to stock, but I do not believe I'm actually able to get my phone into download mode. When it is plugged into my windows 7 computer with the LG drivers installed it shows up in device manager as QHSUSB_BULK.
Is there any way for me to push a stock recovery, or even a custom recovery to my phone so I can somehow salvage it, or am I permanently bricked?
Click to expand...
Click to collapse
I have the same exact problem. exactly the same. mine doesnt even show up for download mode. this sucks!
cgillie92 said:
I have the same exact problem. exactly the same. mine doesnt even show up for download mode. this sucks!
Click to expand...
Click to collapse
I'm still trying to find a solution I will post here if i have any luck. I've dug through a lot of forum posts and I think what makes us unique is the fact that we have a corrupt or blank recovery partition.
toopty said:
I'm still trying to find a solution I will post here if i have any luck. I've dug through a lot of forum posts and I think what makes us unique is the fact that we have a corrupt or blank recovery partition.
Click to expand...
Click to collapse
Ive looked through a lot too. and its crazy how that would happen i made sure it was rebooting correctly before i took the ota and then when i did the ota bam! only screens i can get to come up are the hardware key control mode and the factory hard reset which both go to white screens after I do them both. every one else probably has not taken the ota.
cgillie92 said:
Ive looked through a lot too. and its crazy how that would happen i made sure it was rebooting correctly before i took the ota and then when i did the ota bam! only screens i can get to come up are the hardware key control mode and the factory hard reset which both go to white screens after I do them both. every one else probably has not taken the ota.
Click to expand...
Click to collapse
One difference in what mine is doing and what your phone is doing. I go to a solid black screen not a white screen. It's very hard to tell my phone is even turned on. I'm having to look if the back-light to verify if it's on or not. I can hold my power button for 10 seconds through one LG logo cycle and then it turns off.
toopty said:
One difference in what mine is doing and what your phone is doing. I go to a solid black screen not a white screen. It's very hard to tell my phone is even turned on. I'm having to look if the back-light to verify if it's on or not. I can hold my power button for 10 seconds through one LG logo cycle and then it turns off.
Click to expand...
Click to collapse
I hope someone helps us out. I really cant afford a new one because the warranty is void. I was going back to stock because of all of the little bugs that need to be ironed out in roms. cause kit kat is around the corner hopefully and my problem virtually is the same i might have had my brightness on auto or something prior to that.
Foolow this tutorial to get your phone back.
http://forum.xda-developers.com/showthread.php?p=48765620
Partager.info said:
Foolow this tutorial to get your phone back.
http://forum.xda-developers.com/showthread.php?p=48765620
Click to expand...
Click to collapse
Thanks for the link. I'm tryingto follow the instructions,but when I get to the step where i plug in my phone it just showes up as a bunch of failes partitions, and slows my ubuntu to a crawl. I'm a linux noob, is there a command i can run to stop this from happening? I also created a reply asking this question in the link you sent me.
Thanks for the help.
Partager.info said:
Foolow this tutorial to get your phone back.
http://forum.xda-developers.com/showthread.php?p=48765620
Click to expand...
Click to collapse
After following the instructions on the above link i was able to get fastboot status on my phone. It did not fully restore my phone however. I was able to flash twrp via fastboot. I was then able to boot into twrp and run the command at this link via twrp terminal http://forum.xda-developers.com/showthread.php?t=2451696
Thanks to everyone for all your help.
toopty said:
Thanks for the link. I'm tryingto follow the instructions,but when I get to the step where i plug in my phone it just showes up as a bunch of failes partitions, and slows my ubuntu to a crawl. I'm a linux noob, is there a command i can run to stop this from happening? I also created a reply asking this question in the link you sent me.
Thanks for the help.
Click to expand...
Click to collapse
How did you get past the ubuntu slowing down? I cant win for ubuntu freezing due to all of the failed partitions either so close but yet so far =/
cgillie92 said:
How did you get past the ubuntu slowing down? I cant win for ubuntu freezing due to all of the failed partitions either so close but yet so far =/
Click to expand...
Click to collapse
Ignore all the message, unplug you phone get ready to type the command, plug it in and immediately press enter to run the command. it took some trial and error, and i had to use this other post to help me out. I actually got fastboot working first, then used this post to http://forum.xda-developers.com/showthread.php?t=2477595 to get download mode working, and to flash twrp recovery. After that i used this post to run the command line from with twrp. http://forum.xda-developers.com/showthread.php?t=2451696 . I didn't have to flash the factory tot to my phone, but i have that option now because download mode is working. This process will work, there is hope for you getting your phone back. I'm fully recovered. I decided 12B is not worth it in the mean time, but if you want 12B you need to flash the factory tot and then upgrade. There is a way to root 12B, but as of this time you are unable to get Custom Recovery on it.
Good evening everyone,
I will start off by saying that I really didn't do things by the book this time around. I have run out of ideas even as to what to Google to find similar cases to mine.
I wanted to flash Cyanogenmod onto my G2. Since I already had CWM installed, I loaded the ROM and Gapps. After wiping the phone, I went to flash from the zip. The flash failed. I tried again, and it happened again. I wiped the cache and dalvik again, and tried again. Still no flash.
At this point I go for the reboot only to realize that my phone is now stuck in a bootloop that is contantly landing me back into recovery.
I believe I really screwed up from here as I read about a way to exit the cwm bootloop by flashing a new "exitrecovery.zip" file. Since ADP wouldn't push the file for some reason, I used that function where the phone waits the file to be pushed and flashes it. That succeeded.
The phone switched off (after hanging on CWM for a bit) and now won't do anything at all. No boot logo, nothing. Can't get into CWM anymore either.
The computer brings up a bunch off drives which it wants me to format when I plug the phone in. Only one of them has a folder called "image" on it.
The display switches on, but won't do anything there.
Holding power+up reboots it after a few seconds and so does power=down.
I am thinking of just seeing if I can get it assessed by my carrier, hoping they'll have the tools to just reflash it... somehow. Else, is there a way to potentially fix this?
Back to stock
Put the phone in download mode (vol up while plugging in USB) and use the LG Flash Tool to return to stock. Instructions are posted in General section.
Rule number 1.
ALWAYS MAKE A BACKUP.
bodom_hc said:
Rule number 1.
ALWAYS MAKE A BACKUP.
Click to expand...
Click to collapse
I have a backup I made with CWM.
If that helps, please point me into the right direction to restore it. I fail to see how I can do that without even being able to start cwm up.
missiveusa said:
Put the phone in download mode (vol up while plugging in USB) and use the LG Flash Tool to return to stock. Instructions are posted in General section.
Click to expand...
Click to collapse
I will try this, but the screen never shows anything at all
================================
Solution: http://forum.xda-developers.com/one...bootloader-locked-t3212187/page2#post63494201
================================
Hello,
This afternoon, I was preparing to flash Oxygen OS 2.1 through twrp but I wanted to make a backup first. Attempting to load up twrp by holding Vol- and Power, my OPT flashed the starting frame of the boot animation for half a second before turning off. This repeated every 5 seconds. I could still boot OOS normally at this stage.
I decided to reflash twrp so as to make the backups, but on attempting to flash it, I saw that my bootloader was locked. So into fastboot mode I went, but trying to unlock it, it did the same as trying to get into recovery. As soon as I sent the command, "fastboot oem unlock", the screen went dark, flashed the starting frame for the boot animation, and promptly when dark again.
I now can't boot up normally, nor can I enter recovery. I can access fastboot mode, but I can't seem to make any changes.
I've attempted to use this solution as well as several other similar ones with no success.
I've had my OPT since 17th of August with absolutely no signs of trouble until this afternoon.
To me, it seems like it could be a hardware issue, but I'd hope it would last more than 40 days.
Any suggestions?
Thanks.
----
x-post: whirlpool, reddit
The same just happened to me, wtf
Makrilli said:
The same just happened to me, wtf
Click to expand...
Click to collapse
What were you doing before it occurred? Perhaps we can work out the cause.
GusGold said:
What were you doing before it occurred? Perhaps we can work out the cause.
Click to expand...
Click to collapse
I'm not sure what I was doing, I was going to flash different ak kernel as my wifi didn't work.
HOWEVER
I read someone suggesting if you still have bootloop after trying the qualcomm recovery tool, try booting to fastboot and use: fastboot continue
my opt booted nicely to hydrogen os and after I shut it down it no longer bootlooped and I was able to get to recovery.
I'll post this to your reddit thread too, maybe it might help somebody one day, hopefully this works for you too
Makrilli said:
use: fastboot continue
Click to expand...
Click to collapse
Mate! that worked for me too!
However... It only seems to skip the bootloop for that power on. After power off, it returns to the boot loop. I also still can't unlock the bootloader and can't access recovery.
But at least it can boot into OS with fastboot continue!
Thank you.
Weird, after the first successful boot I rebooted and a chinese menu prompted me if I wanted to unlock the bootloader, and I did.
Maybe you should try different recovery packages.
But I'm glad to hear you at least got past the boot loop
Makrilli said:
Maybe you should try different recovery packages.
Click to expand...
Click to collapse
Can't flash a new one since the bootloader won't unlock :/
I guess the phone is in working order at the moment, I just can't let it get turned off without my computer next to me...
GusGold said:
Can't flash a new one since the bootloader won't unlock :/
I guess the phone is in working order at the moment, I just can't let it get turned off without my computer next to me...
Click to expand...
Click to collapse
Nono I mean different qualcomm recovery packages, the ones with MSM8994DownloadTool, I also replaced the stock recovery in the qualcomm package with twrp just in case if that matters
Makrilli said:
Nono I mean different qualcomm recovery packages, the ones with MSM8994DownloadTool, I also replaced the stock recovery in the qualcomm package with twrp just in case if that matters
Click to expand...
Click to collapse
Ahh, do you mind linking me to the one you used?
I think I used this: https://mega.nz/#!EsNQHKab!ifATzg4rxxBniPad0iyxANqlN8cZpUx2MVWaZgEhrD4
but it might have also been this: https://drive.google.com/file/d/0B14IjYN3PtxcSlJ5aGQxX3JERHM/view?usp=sharing
It's also worth mentioning I flashed both a few times before I tried the fastboot continue command so try both a few times and see if that helps, also I replaced the stock recovery with twrp in both recovery packages before flashing.
Edit: And best of luck, I'm rather confident your OPT is going to work properly again.
Boot Loop
I got the same problem.
Phone is rooted and i can't unlock it in cmd, just reboot itself when i try it.
The only way for me to even start the OPT is to (volume+ and power), to get to fastboot mode, then run "fastboot continue" twice in cmd.
If i reboot the phone it get cought in a boot loop where i can see the logo, reboots about every 2 sec.
Is there a solution for this? I've been searching 2 for two days now.
I don't care if i have to reset the entire phone.
p3wb said:
I got the same problem.
Phone is rooted and i can't unlock it in cmd, just reboot itself when i try it.
The only way for me to even start the OPT is to (volume+ and power), to get to fastboot mode, then run "fastboot continue" twice in cmd.
If i reboot the phone it get cought in a boot loop where i can see the logo, reboots about every 2 sec.
Is there a solution for this? I've been searching 2 for two days now.
I don't care if i have to reset the entire phone.
Click to expand...
Click to collapse
And I'm guessing you have tried the qualcomm recovery tool?
And I'm guessing you have tried the qualcomm recovery tool?[/QUOTE]
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.
p3wb said:
And I'm guessing you have tried the qualcomm recovery tool?
Click to expand...
Click to collapse
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.[/QUOTE]
Yeah but the qualcomm recovery tool that we discussed on the first page?
Sent from my OPT
Makrilli said:
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.
Click to expand...
Click to collapse
Yeah but the qualcomm recovery tool that we discussed on the first page?
Sent from my OPT[/QUOTE]
I finally got my OPT working again, tried Qualcomm recovery tool, wasn't able to complete the "MSM8994DownloadTool"
So i downloaded "A2001_14_A.03_150805" in a guide from technobuzz.net/unbrick-oneplus-2/
A similar but it does a entire wipe of the phone, nothing left at all. WARNING!
But i was okey with it.
Well the phone was in Chinese when it was all done but to change language was no problem.
I finally managed to solve it on mine. I had been cautious over the past weeks to not let it run out of battery or get turned off while away from my computer as
Code:
fastboot continue
was the only way I could get past the boot loop.
My core issue to solve was that I couldn't get it recognised as the USB Diagnostic 9006 under Ports in Device Manager. I installed the driver from here manually by right clicking the /qcser/x64/qcser.inf file and selecting install from the context menu. Then, I powered off my OP2. While only holding Vol+ (not power or Vol-), I plugged in my OP2 to the computer and it was finally recognised as the 9006. Then using the recovery tool from the prior link, it installed and rebooted my OP2. The moment of truth was when it rebooted and didn't enter a boot loop!
Then with the Chinese recovery prompt, I selected the top/first option and it brought me to the welcome/first setup screen of OOS.
It wiped the internal memory, and installed OSS 2.0.2 (don't know if coincidence or not as that was my prior OS as well). Now to install twrp and update to the latest OOS hopefully without a hitch.
Happy to finally know it wasn't a hardware issue like a failed eeprom or a dud nand controller as my prior phone (Samsung Note 10.1) died to a failed nand controller as well.
Will update with news of twrp and OOS, but I feel that should go smoothly now. Thanks to the others that helped in this thread too!
Yeap, all good!
Flashed official twrp through fastboot and batch installed OOS2 through 2.1.1 patches and SuperSU. Everything working like new!
Phew.
hi can one of you guys help me out? on teamviewer? mine is stock in the bootloop and i can only get it to boot up via fastboot continue. and i cant figure out how to get it to work. i would like to go back to complete stock and no root
best Martin
gamdiiii said:
hi can one of you guys help me out? on teamviewer? mine is stock in the bootloop and i can only get it to boot up via fastboot continue. and i cant figure out how to get it to work. i would like to go back to complete stock and no root
best Martin
Click to expand...
Click to collapse
Is it recognised as a USB Diagnostic 9006 in your device manager?
Hi GusGold No its 9008
when reinstalling a ROM earlier today, I got an error 7 ... no problem. probably TWRP problems... so, i go to reboot phone to recovery to begin fresh, and now, TWRP boots, but the screen flashes blank every couple seconds, for a second, then the TWRP splash screen comes back up. blank screen, then TWRP splash screen again. never gets further than that. because I dont have an OS installed, i cannot access debugging for adb. because i deleted my OS, i cannot allow fastboot, to flash a new recovery and begin again. ..
I am broke, and cannot afford to pay for a new replacement thru insurance or to just go buy a junker phone and make do with that.
am i ****ed, or is this recoverable...? ive been searching the forums, but cannot seem to find the answer, and im starting to get nervous enough that its sorta beginning to compound my problems more than i can deal with.
edited to add again: .... battery removed + volume dn then insert battery will not enter fastboot. im about to paperweight this ****.
again edited - Sprint LS997 is phone model. no TOT'ing for me.
What about if you remove the battery, put it back in, hold volume down and then plug the usb cable?
XblackdemonX said:
What about if you remove the battery, put it back in, hold volume down and then plug the usb cable?
Click to expand...
Click to collapse
tried this. still a no-go. phone screen does not power on when trying this or any other combo of steps. LAF works, which is vol+ and plug in USB cable. odd that vol- and plug in USB cable does nothing. maybe faulty vol+ button? never had a problem with that button functioning before now. i have access to: LAF (download mode), and TWRP. However, TWRP 'flashes' off n on... i see the splash screen for a second, then screen goes blank, but still powered on. then splash screen again. rinse, and repeat. no response to touch or vol/pwr buttons. tried pulling battery upon TWRP splash hoping this clears cache, but still just same story afterwards.
would having access to fastboot even matter, since I have no OS install with which to give fastboot/adb access anyway?
elijah420 said:
would having access to fastboot even matter, since I have no OS install with which to give fastboot/adb access anyway?
Click to expand...
Click to collapse
From fastboot you can reflash TWRP which from where you can reflash the OS which would unbrick the phone.
elijah420 said:
i have access to: LAF (download mode)
Click to expand...
Click to collapse
If you have access to download mode, can't you reflash your phone using the LGUP with the backup that did in the first place?(you did a backup of the original OS right?)
elijah420 said:
tried this. still a no-go. phone screen does not power on when trying this or any other combo of steps. LAF works, which is vol+ and plug in USB cable. odd that vol- and plug in USB cable does nothing. maybe faulty vol+ button? never had a problem with that button functioning before now. i have access to: LAF (download mode), and TWRP. However, TWRP 'flashes' off n on... i see the splash screen for a second, then screen goes blank, but still powered on. then splash screen again. rinse, and repeat. no response to touch or vol/pwr buttons. tried pulling battery upon TWRP splash hoping this clears cache, but still just same story afterwards.
would having access to fastboot even matter, since I have no OS install with which to give fastboot/adb access anyway?
Click to expand...
Click to collapse
Sounds like empty or bad battery to me. When did your phone start acting up upon ya? Right after root or you had it working with root etc before u ended up into such situation.
Also, as XblackdemonX pointed out, you can still use LGUP to stock.
I'm pretty sure that happened to me. And I fixed my H990DS by flashing kdz file in download mode with LG BRIDGE.
There's a guide about how to unbrick any v20 around here.
@elijah420 What software version were you on before this started? Why does it matter? If you were on ZV7 or earlier, then you can flash a VS995 KDZ in download mode, root it, and then fix your phone. If you were on ZV8 or later, then you still might be able to salvage your phone, but you will have to run firmware from another model since you will not be able to root and flash back to Sprint firmware if you were ARB 1 or later. Better than having a totally busted phone though.
Last possibility is to use the debug firehose that I have, but that is an even bigger unknown than running firmware from another model.
-- Brian
Alright, so I had just installed TWRP and Magisk, made backups of my ROM and EFS, everything is going well. I go to install LuisROM.
I go into TWRP, click install, and click on the LuisROM package. Says it doesn't find a digest file, but installation is continuing, so I figure it's no big deal. Reboot, and I get the Unlocked Bootloader warning that I've just recently began to familiarize myself with, but at the bottom of the screen, say the bottom half inch or so, is crazy static. Completely jumbled nonsense. It's not animated or anything, just randomly colored static pixels. Odd.
Next screen? Black. Nothing. Plugged into the computer and the she makes the familiar beeps that a device has been plugged in. For a time I find myself stuck in a boot loop trying to get back into recovery via power + vol down, but nothing. Seems to instant reboot back into the warning then black screen.
Now: I can't even seem to turn the phone off! If I plug into the laptop, I hear the familiar sounds, but can't do anything about it that I know of. If I hold the power button for 30-60 seconds: nothing.
I saw a few posts on here saying something about a complete power drain and recharge, so that's my next best guess, but I'm hoping someone else has a better idea.
lynxon said:
Alright, so I had just installed TWRP and Magisk, made backups of my ROM and EFS, everything is going well. I go to install LuisROM.
I go into TWRP, click install, and click on the LuisROM package. Says it doesn't find a digest file, but installation is continuing, so I figure it's no big deal. Reboot, and I get the Unlocked Bootloader warning that I've just recently began to familiarize myself with, but at the bottom of the screen, say the bottom half inch or so, is crazy static. Completely jumbled nonsense. It's not animated or anything, just randomly colored static pixels. Odd.
Next screen? Black. Nothing. Plugged into the computer and the she makes the familiar beeps that a device has been plugged in. For a time I find myself stuck in a boot loop trying to get back into recovery via power + vol down, but nothing. Seems to instant reboot back into the warning then black screen.
Now: I can't even seem to turn the phone off! If I plug into the laptop, I hear the familiar sounds, but can't do anything about it that I know of. If I hold the power button for 30-60 seconds: nothing.
I saw a few posts on here saying something about a complete power drain and recharge, so that's my next best guess, but I'm hoping someone else has a better idea.
Click to expand...
Click to collapse
Can you reboot to EDL Mode? Plug in your phone. And hold the power and Volume Up button till it turns off. As soon as the Screen Goes black, let go of Power and Hold both the Volume Buttons. You will hear the Windows Connection Sound from your PC but phone screen will be back. After that, follow the instructions from the MSM Download Tool thread. It's in the Guides Section or you can Google 'MSM Download Tool OP6T"
DarthVader said:
Can you reboot to EDL Mode? Plug in your phone. And hold the power and Volume Up button till it turns off. As soon as the Screen Goes black, let go of Power and Hold both the Volume Buttons. You will hear the Windows Connection Sound from your PC but phone screen will be back. After that, follow the instructions from the MSM Download Tool thread. It's in the Guides Section or you can Google 'MSM Download Tool OP6T"
Click to expand...
Click to collapse
The phone is currently stuck in a state where the screen is black, but is stuck powered on. I cannot seem to power down manually.
That being said, after going to the thread you've directed me to, it does appear in the device manager under the name indicated by the thread! I will report back once I've tried all I can with this lead, thank you very much.
lynxon said:
The phone is currently stuck in a state where the screen is black, but is stuck powered on. I cannot seem to power down manually.
That being said, after going to the thread you've directed me to, it does appear in the device manager under the name indicated by the thread! I will report back once I've tried all I can with this lead, thank you very much.
Click to expand...
Click to collapse
Good Luck.
Alright, so right now I'm getting "Sahara Communication Failed, please try again after power off phone."
So, I guess I'm back to waiting for the phone to run out of battery on its own. I'll try the MSM Download Tool again once that time comes :good:
lynxon said:
Alright, so right now I'm getting "Sahara Communication Failed, please try again after power off phone."
So, I guess I'm back to waiting for the phone to run out of battery on its own. I'll try the MSM Download Tool again once that time comes :good:
Click to expand...
Click to collapse
I think you're forgetting the 3-button-magic of your device. Press power + vol-up + vol-down simultaneously for 10 seconds to make it power down.
Wrapped with delicious Fajita [emoji896]
Timmmmaaahh said:
I think you're forgetting the 3-button-magic of your device. Press power + vol-up + vol-down simultaneously for 10 seconds to make it power down.
Click to expand...
Click to collapse
I did actually try that as well, to no avail.
DarthVader said:
Can you reboot to EDL Mode? Plug in your phone. And hold the power and Volume Up button till it turns off. As soon as the Screen Goes black, let go of Power and Hold both the Volume Buttons. You will hear the Windows Connection Sound from your PC but phone screen will be back. After that, follow the instructions from the MSM Download Tool thread. It's in the Guides Section or you can Google 'MSM Download Tool OP6T"
Click to expand...
Click to collapse
Good news is that this time the MSM Download Tool could recognize the phone, however I received "Images do not match with the phone." I had to download 9.0.12. as it seems that 9.0.13. actually got removed from that server as I was in the middle of downloading it. I found another source for 9.0.13. and am downloading that now. Hopefully that's the correct version...
lynxon said:
I did actually try that as well, to no avail.
Good news is that this time the MSM Download Tool could recognize the phone, however I received "Images do not match with the phone." I had to download 9.0.12. as it seems that 9.0.13. actually got removed from that server as I was in the middle of downloading it. I found another source for 9.0.13. and am downloading that now. Hopefully that's the correct version...
Click to expand...
Click to collapse
Is your phone a T-Mobile Converted
DarthVader said:
Good Luck.
Click to expand...
Click to collapse
And the phone is alive again! Hallelujah! I had to use the T-Mobile version of the MSM Download Tool, which is funny because I had bought the phone used and there was no T-Mobile screen at boot before, but there is now, but she is alive!!!
Thank you again for your help. You're doing great work since returning to the light side, Vader
lynxon said:
And the phone is alive again! Hallelujah! I had to use the T-Mobile version of the MSM Download Tool, which is funny because I had bought the phone used and there was no T-Mobile screen at boot before, but there is now, but she is alive!!!
Thank you again for your help. You're doing great work since returning to the light side, Vader
Click to expand...
Click to collapse
Glad to know you're back up. You bought it off eBay I assume? That would explain the no TMo Splash Screen earlier. Now if you'd like to revert to International again, there is a Guide you can use to convert your TMo into International and then update to latest 10.3 or Flash a Custom ROM as you please. It's in the Guides Section.
May the Force be with You.
DarthVader said:
Glad to know you're back up. You bought it off eBay I assume? That would explain the no TMo Splash Screen earlier. Now if you'd like to revert to International again, there is a Guide you can use to convert your TMo into International and then update to latest 10.3 or Flash a Custom ROM as you please. It's in the Guides Section.
May the Force be with You.
Click to expand...
Click to collapse
Yes! Back up and then immediately down... So, I followed the procedure to remove the T-Mobile info and that worked well, back to stock OxygenOS 9.0.13. Followed the directions here for unlocking the bootloader, running TWRP and Magisk. All good.
Last time I flashed with RR and crashed. This time I flashed with LineageOS 17 and... Exact same crash. Static on the bottom of the screen, bootloop and all. So, now I'm stuck waiting again for the battery to die down before I can reflash to T-Mobile, then to international, then unlock the bootloader.
Any idea what I can do differently this time so I can have a custom ROM?
Not eBay, but I was using OfferUp and found a local shop selling it so I was able to sidestep the middleman.
lynxon said:
Yes! Back up and then immediately down... So, I followed the procedure to remove the T-Mobile info and that worked well, back to stock OxygenOS 9.0.13. Followed the directions here for unlocking the bootloader, running TWRP and Magisk. All good.
Last time I flashed with RR and crashed. This time I flashed with LineageOS 17 and... Exact same crash. Static on the bottom of the screen, bootloop and all. So, now I'm stuck waiting again for the battery to die down before I can reflash to T-Mobile, then to international, then unlock the bootloader.
Any idea what I can do differently this time so I can have a custom ROM?
Not eBay, but I was using OfferUp and found a local shop selling it so I was able to sidestep the middleman.
Click to expand...
Click to collapse
Could you perhaps provide an image of Said Crash? And a couple more things. Which ROM were you trying to Flash. What was your OOS version before trying to Flash the ROM. And what TWRP did you use? Because this sounds like a Crash Dump which is common if you use the wrong Vendor Firmware.
DarthVader said:
Could you perhaps provide an image of Said Crash? And a couple more things. Which ROM were you trying to Flash. What was your OOS version before trying to Flash the ROM. And what TWRP did you use? Because this sounds like a Crash Dump which is common if you use the wrong Vendor Firmware.
Click to expand...
Click to collapse
Well, hopefully I won't crash again as I have to wait a day for the battery to train to fix the crash haha. It happened so far with RR and LineageOS. OxygenOS 9.0.13. And...
Woah. Just now seeing that my TWRP Zip file is 3.2.3-2 and Img file is 3.3.1-1. Perhaps that is the culprit?
EDIT: Nope! Just tried with TWRP 33.1-1, LineageOS 16 official build as of 1/11/2020. Included is a photo of the boot warning page, and apparently I can fastboot right now as well, but there's no particular information on either page that I can imagine is useful.
Boot warning
Fast boot
This time I also tried wiping the Dalvik. I also notice that on the bootloader unlocking directions it says to not update with partial OTAs (under 1GB) as this can cause a soft-brick. All of the ROMs I've been trying to flash are about 500mb. Is this the problem?
lynxon said:
Well, hopefully I won't crash again as I have to wait a day for the battery to train to fix the crash haha. It happened so far with RR and LineageOS. OxygenOS 9.0.13. And...
Woah. Just now seeing that my TWRP Zip file is 3.2.3-2 and Img file is 3.3.1-1. Perhaps that is the culprit?
Click to expand...
Click to collapse
It is. Always use the latest version of TWRP, OOS, Magisk, etc UNLESS said otherwise.
DarthVader said:
It is. Always use the latest version of TWRP, OOS, Magisk, etc UNLESS said otherwise.
Click to expand...
Click to collapse
I seem to have edited my last post without noticing your reply. Updated both copies of TWRP, img and zip, to the latest and still crashed. Though if you look at my last post there is one other potential, though I'm not sure what to do about it, I also uploaded pics.
This magic right here!!
After following the directions in this video, I have achieved a custom rom. RR is loading right now. It would seem the major difference is that I wasn't decrypting my data, which is included in this video.
Thanks again for sticking with me and being so patient. ?
lynxon said:
This magic right here!!
After following the directions in this video, I have achieved a custom rom. RR is loading right now. It would seem the major difference is that I wasn't decrypting my data, which is included in this video.
Thanks again for sticking with me and being so patient. ?
Click to expand...
Click to collapse
Hmm. Glad to know that you're up and running. If you don't mind, could you tell me what you did different when flashing this time? And how were you flashing before that lead to the bricks.
DarthVader said:
Hmm. Glad to know that you're up and running. If you don't mind, could you tell me what you did different when flashing this time? And how were you flashing before that lead to the bricks.
Click to expand...
Click to collapse
Basically it comes down to the directions here, which I used as a base, and the directions in this video.
The unlocking bootloader directions didn't have anything about installing a custom ROM, so I figured that once I had everything else set up: unlocked bootloader, TWRP, root, then all I had to do was go to "install" in TWRP and flash the new ROM, which had led to the crash with static at the bottom of my screen.
But then, when using the video tutorial, this guy did things in a particular way. The very first thing was decrypting the data, which I didn't know was necessary, but probably made the difference. This was done under "wipe" and then "format data" in TWRP. He also instructed on flashing the newest version of OxygenOS and TWRP twice, apparently this installed it under both A/B partitions. After installing the custom ROM he also wiped the "data" and "cache." Lots of steps in the video, I felt as if they didn't need to be done exactly the way he directed, but in this case I trusted his method and I'm glad I did.