Related
So there I was, using Cloudy 3.3 on my G2 international model (d802) when I thought to myself: Why wouldn't I change the ROM. I guess I got bored of it and while in the past year I tried almost EVERY ROM (at least every 5.1 lollipop ROM and these new marshmallow ROMs) I wanted something different this time. I remembered that Flyme OS system and wanted to give it a go. I found one here on xda site, I think it was Flyme 4.1 or 4.0 or something like that but I decided to go for a ,,newer" version of the system.
I found Flyme OS on this site: http://www.flyme.cn/firmwarelist-14.html
And as you can see the entire site is in Chinese but I managed somehow and downloaded it. I had TWRP 3.0 installed and I think I know the thing or two about flashing ROMs on this device. The whole installer is AROMA based and even though it was in Chinese I managed to flash the system. And that's when I knew I f****d up. After I installed it and it booted up, I figured that I'm not really into the whole Flyme interface and wanted to revert to stock. But I couldn't!
1. I no longer have download mode, when I stick USB cable and hold volume up it shows me an animation of ,,download mode'' but then in upper left corner appears a message saying ,,boot secure error'' or something like that and then it shows me a black screen.
2. I no longer have my TWRP recovery installed.
- I can't use 3rd party apps to restart my phone into recovery because this OS is NOT rooted! And I can't even root it because there's no method for it. I tried the default rooting method for MEIZU phones which include you logging in to your Flyme account and all of a sudden ,,root permissions'' option appears in your settings - DIDN'T HAPPEN. I also tried other different methods but to no avail. It just can't be rooted. - Even when I turn the phone off and try to do the hard reset thing with simultaneously holding power + volume down button - it won't show me the LG's default ,,factory reset'' screen which could potentially lead me into TWRP. It just boots normally!
So, the conclusion:
I flashed an unknown Flyme OS system for LG G2 from a Chinese site and it works decently good but when it installed - it turned my G2 completely to a MEIZU phone. I have no clue on how to revert it and PLEASE I would appreciate any help given. Before giving your opinions in the comments, do read every sentence I wrote above.
Thanks in advanced.
duff105 said:
So there I was, using Cloudy 3.3 on my G2 international model (d802) when I thought to myself: Why wouldn't I change the ROM. I guess I got bored of it and while in the past year I tried almost EVERY ROM (at least every 5.1 lollipop ROM and these new marshmallow ROMs) I wanted something different this time. I remembered that Flyme OS system and wanted to give it a go. I found one here on xda site, I think it was Flyme 4.1 or 4.0 or something like that but I decided to go for a ,,newer" version of the system.
I found Flyme OS on this site: http://www.flyme.cn/firmwarelist-14.html
And as you can see the entire site is in Chinese but I managed somehow and downloaded it. I had TWRP 3.0 installed and I think I know the thing or two about flashing ROMs on this device. The whole installer is AROMA based and even though it was in Chinese I managed to flash the system. And that's when I knew I f****d up. After I installed it and it booted up, I figured that I'm not really into the whole Flyme interface and wanted to revert to stock. But I couldn't!
1. I no longer have download mode, when I stick USB cable and hold volume up it shows me an animation of ,,download mode'' but then in upper left corner appears a message saying ,,boot secure error'' or something like that and then it shows me a black screen.
2. I no longer have my TWRP recovery installed.
- I can't use 3rd party apps to restart my phone into recovery because this OS is NOT rooted! And I can't even root it because there's no method for it. I tried the default rooting method for MEIZU phones which include you logging in to your Flyme account and all of a sudden ,,root permissions'' option appears in your settings - DIDN'T HAPPEN. I also tried other different methods but to no avail. It just can't be rooted. - Even when I turn the phone off and try to do the hard reset thing with simultaneously holding power + volume down button - it won't show me the LG's default ,,factory reset'' screen which could potentially lead me into TWRP. It just boots normally!
So, the conclusion:
I flashed an unknown Flyme OS system for LG G2 from a Chinese site and it works decently good but when it installed - it turned my G2 completely to a MEIZU phone. I have no clue on how to revert it and PLEASE I would appreciate any help given. Before giving your opinions in the comments, do read every sentence I wrote above.
Thanks in advanced.
Click to expand...
Click to collapse
Bump.
C'mon guys, there has to be someone who could possibly try to help
duff105 said:
C'mon guys, there has to be someone who could possibly try to help
Click to expand...
Click to collapse
Did you tried going to recovery mode by completely shutting off your phone and then pressing volume down + power button simultaneously. If goes into recovery mode as you said you have no twrp installed. What does it shows and also what happens when you connect your phone to pc in recovery mode?.
P.S i recovered from a similar issue like you on my sprint g2
qasim799 said:
Did you tried going to recovery mode by completely shutting off your phone and then pressing volume down + power button simultaneously. If goes into recovery mode as you said you have no twrp installed. What does it shows and also what happens when you connect your phone to pc in recovery mode?.
P.S i recovered from a similar issue like you on my sprint g2
Click to expand...
Click to collapse
I tried going to recovery with my phone being completely shut down, however, it simply turns the phone on. No button combination gets me into recovery anymore. As if it simply vanished from my phone (the recovery, of course). It doesn't show the default ,,Factory data reset" option when I hold volume down + power button whilst turning the phone on. No options whatsoever. So I didn't even get the chance to connect it to the PC while in recovery, since there's no recovery installed on my phone.
duff105 said:
I tried going to recovery with my phone being completely shut down, however, it simply turns the phone on. No button combination gets me into recovery anymore. As if it simply vanished from my phone (the recovery, of course). It doesn't show the default ,,Factory data reset" option when I hold volume down + power button whilst turning the phone on. No options whatsoever. So I didn't even get the chance to connect it to the PC while in recovery, since there's no recovery installed on my phone.
Click to expand...
Click to collapse
install quick boot. and try to access to recovery. maybe it will help.
otherwise... kingroot ... if your phone is not rooted. google for autorec for your model phone. it will install the recovery again
I downgraded from LineageOS back to stock 6.0 using the files from Prazaar.de and all worked fine. i was able to configure the phone back to my gmail account and calling and everything worked.
to upgrade back to 7.0 i downloaded the blur files from prazaar. i then booted into recovery and sideloaded the first blur file with adb as i have done a few times before. only this time when it was finished, the phone rebooted and the screen stayed black. no matter how often or how long i press the powerbutton with or without volume buttons, nothing happens. when i plug it into windows with a cable though, windows sees a new device Qualcomm HS USB QDloader9008. so it's not all dead.
all guides that talk about unbricking the device at some point need to boot into recovery or at least the bootmenu to start fastboot flashing. but my screen is black and no matter at what point i do a 'fastboot devices' with powerbutton-pressing, it will never show up as a fastboot device.
is there any way to recover from this error or is this phone beyond recovery? how can a phone be this dead after a software update? any help would really really be appreciated as i do still like this phone and am not ready to throw it away yet
If you'd done a little searching you would've found this amazing thread.
https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860
Instructions are for the Moto X Style XT1572, but work for the XT1575 too as long as you flash the correct firmware. The issue is caused by updating to Nougat, then downgrading to MM and performing an OTA.
parker.stephens said:
If you'd done a little searching you would've found this amazing thread.
https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860
Instructions are for the Moto X Style XT1572, but work for the XT1575 too as long as you flash the correct firmware. The issue is caused by updating to Nougat, then downgrading to MM and performing an OTA.
Click to expand...
Click to collapse
thanks, i've seen that thread, but at the point where i put the sd card in the phone with the loader.img on it and hold the powerbutton, i'm not getting a fastboot screen.. maybe i'm close to getting it to work but so far i dont see anything. any pointers would really be appreciated!
It's really finicky to use. For me, I flashed the loader.img on Windows 7 32-bit and it take multiple (like over a dozen) tries to get it to work. I got really frustrated with it, but after a while it worked. Just make sure that when you are powering on you either need to hold down volume down or volume down and power.
EDIT: Thankfully I could resolve this issue on my own fairly easily. My battery drained relatively quickly, and the issue didn't repeat when I tried booting again.
Hi XDA developers community,
Using some of the guides on this fantastic website I flashed LineageOS on my A2017G a few months ago. Now I tried reverting back to stock by flashing the B03 Oreo zip file in EDL mode (this guide).
The first reboot was already successful: I powered the phone on via the power button, then went through "can't be checked for corruption" screen, then got into the screen with Tux (Linux penguin), pressed volume up to go to recovery just to be sure, and rebooted from there into Android.
Although instead of starting the setup process Android dropped my right into the lock screen. I assumed that was because I hadn't factory reset yet and my data partition still had garbage data (that was step 18 of the guide btw). So, I powered off, from Android, and tried booting into recovery mode again to do the factory reset. However, now, after the Android corruption warning screen, the Linux Tux screen just stays there. Recovery mode doesn't appear, neither did it boot into Android. I can't even force power off by pressing the button (I pressed 80 seconds straight, no effect). No combination of volume and power buttons does anything, even pressing and holding it.
Right now I plan to let the battery drain on its own to get the device to power off. That's probably gonna take some days because the battery is completely charged. Is there some other possibility to make it go faster? Maybe heat the battery up from the outside with a hair dryer? I would rather not open the phone up and take the battery out, because I don't have a heat gun and I'm also worried I'm gonna leave scratch marks or something (the process seems quite rough).
And also, when the battery is drained, is there any recommendation on what I should do? Simply try again, going into recovery mode? Flash the EDL file again?
Thank you for reading all this, and I'd be so glad for any help.
I'm having this screen too, I'm trying to gsi, but none works, only lineage 16, but it gives error and closes the system at 16, and at lineage 15 the battery is being drained very quickly
Any rom stock I try to flash via edl gets in bootloop on the penguin screen, I can do the flash via edl from a los rom with 15.1 with oki twrp, some bugs, but would like to return to stock, can anyone help us?
same issue
Hello there
I have the same issue, can you please help ?
Thank you in advance
prasnel
kangalioo said:
EDIT: Thankfully I could resolve this issue on my own fairly easily. My battery drained relatively quickly, and the issue didn't repeat when I tried booting again.
Hi XDA developers community,
Using some of the guides on this fantastic website I flashed LineageOS on my A2017G a few months ago. Now I tried reverting back to stock by flashing the B03 Oreo zip file in EDL mode (this guide).
The first reboot was already successful: I powered the phone on via the power button, then went through "can't be checked for corruption" screen, then got into the screen with Tux (Linux penguin), pressed volume up to go to recovery just to be sure, and rebooted from there into Android.
Although instead of starting the setup process Android dropped my right into the lock screen. I assumed that was because I hadn't factory reset yet and my data partition still had garbage data (that was step 18 of the guide btw). So, I powered off, from Android, and tried booting into recovery mode again to do the factory reset. However, now, after the Android corruption warning screen, the Linux Tux screen just stays there. Recovery mode doesn't appear, neither did it boot into Android. I can't even force power off by pressing the button (I pressed 80 seconds straight, no effect). No combination of volume and power buttons does anything, even pressing and holding it.
Right now I plan to let the battery drain on its own to get the device to power off. That's probably gonna take some days because the battery is completely charged. Is there some other possibility to make it go faster? Maybe heat the battery up from the outside with a hair dryer? I would rather not open the phone up and take the battery out, because I don't have a heat gun and I'm also worried I'm gonna leave scratch marks or something (the process seems quite rough).
And also, when the battery is drained, is there any recommendation on what I should do? Simply try again, going into recovery mode? Flash the EDL file again?
Thank you for reading all this, and I'd be so glad for any help.
Click to expand...
Click to collapse
My phone is like u "zte axon 7 a2017g " version oreo b03 please tell me the guide that u used to install lineage os and the tools please !!!
i just want to install unloack my bootloader , flash twrp , install lineage os so on ; please give me just the guide that u use !
afef said:
My phone is like u "zte axon 7 a2017g " version oreo b03 please tell me the guide that u used to install lineage os and the tools please !!!
i just want to install unloack my bootloader , flash twrp , install lineage os so on ; please give me just the guide that u use !
Click to expand...
Click to collapse
Sorry, I don't remember
kangalioo said:
Sorry, I don't remember
Click to expand...
Click to collapse
u don't remember if the guide is for marshmallow or naugat a 2017 g or i can use guide for a2017 u !
afef said:
u don't remember if the guide is for marshmallow or naugat a 2017 g or i can use guide for a2017 u !
Click to expand...
Click to collapse
what
kangalioo said:
EDIT: Thankfully I could resolve this issue on my own fairly easily. My battery drained relatively quickly, and the issue didn't repeat when I tried booting again.
Click to expand...
Click to collapse
Mine didn’t reboot at all after completely draining the battery several times. Same result, blocked on penguin screen, no way to get into a menu to flash anything ?
kangalioo said:
what
Click to expand...
Click to collapse
My phone is "zte axon 7 a2017g" version oreo b03 , i want to find guide make me unloack bootloader , flash twrp , install lineage os ; i just want for if u can remember if what can proch me i can use because the only guides exist are for a2017u or a 2017 g marshmallow or naugat
or if u can tell me if i can downgrading from oreo to marshmallow without unloack bootloader to use the guide exist for marshmallow !
afef said:
My phone is "zte axon 7 a2017g" version oreo b03 , i want to find guide make me unloack bootloader , flash twrp , install lineage os ; i just want for if u can remember if what can proch me i can use because the only guides exist are for a2017u or a 2017 g marshmallow or naugat
or if u can tell me if i can downgrading from oreo to marshmallow without unloack bootloader to use the guide exist for marshmallow !
Click to expand...
Click to collapse
As I said, I don't remember. I'm using a different phone altogether since half a year.
So because only a Tux logo appeared on the screen, my guess as to what happened is that while the Android Bootloader, also called "aboot" was booting the Linux kernel that Android runs off of, before the kernel could display the splash screen that appears when you power on the device, it encountered a critical error that either aborted the boot process, or caused the kernel to go into a kernel panic. Now as to why it displayed the Tux logo, it probably did that because when it crashed, it tried mapping the framebuffer to the display instead of keeping in hidden by default to show you the kernel buffer logs for you to troubleshoot the problem but instead, it shows the iconic Linux penguin that is usually hidden when the kernel boots.
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.
Ok so before I started writing this I had only one problem now I'm worried my problem has gone from bad to worse.
I updated my 6T to 10.3.2 from the latest Beta after the process it prompted for a restart, upon restarting it got stuck in the boot animation. I tried going into Recovery and Download mode unsuccessfully so I went through the forums a bit and saw that someone who had the same problem successfully entered Recovery mode by pressing VOLUME UP+DOWN+POWER buttons simultaneously, I tried to do the same and my phone turned off and now it doesn't turn on! :crying:
Has anyone experienced this or know how to fix this? Any help will be much appreciated. Tia!
theDUD3 said:
Recovery mode by pressing VOLUME UP+DOWN+POWER buttons simultaneously, I tried to do the same and my phone turned off and now it doesn't turn on!
Click to expand...
Click to collapse
These should be clarified:
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool.
Turn the phone off, let it sit. Then try turn it back on. Any response?
try to shutdown phone ...hold vol+ and power button for like 15 sec and restart your phone if this didnt work then u can try MSM tool
Thanks guys, got it working using MSM Tool!
regarding oneplus 6 got stuck on logo screen and recovery mode not working
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!
frankynehemimah said:
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!
Click to expand...
Click to collapse
You are likely going to lose your data. Know that going in if its not already backed up.
If you have the fastboot menu you can use the fastboot roms.
Or my least favorite option or what I would try last, MSM Tool (Tmobile 6Ts use a different tool).
IMPORTANT if you want to try and recover and data off your phone first, go to fastboot, and try and "boot" the TWRP img (not the installed one, one from your PC using the fastboot command). If that works you might be able to recover data. If that does worm, try dirty flashing the last ROM you were running and see if it boots.
No worries!
frankynehemimah said:
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!
Click to expand...
Click to collapse
Hello, I am sorry to hear of you having this issue, I just went through 3 1/2 days (off and on) of recovering my T-Mobile OnePlus 6t which I found a way to get my unlock code within 2 weeks of having it, so I rooted it and put a custom kernel on it, stuck on 9.0 never let me update as I was not familiar with A/B partitioning, yet! The answers I saw to your questions were spot on, I just had a little to add to it and I'm sure I am not alone. Real quick let me list what has gone wrong on the rare occasion it hit the fan with the 6t...
- When I would accidentally and rarely let my battery die it seemed like it took forever to get it to reboot, I mean it sat on my desk of DOA devices for 2 weeks!
- It often seems like the buttons do not always respond properly and never have when I needed them to. Been through this before, I've bricked and unbricked and flashed and re-flashed and wiped all weekend and I like Android 10 and all but seems everything is different for every build, and everything seems to have to go in the right order with the exact right file or you wind up in a jam, period..
- That said, the previous person that answered your question has likely encountered similar, I've heard of right down to the buttons not physically working, but I have been a Smart Device Master III Technician for over 5 years, i know my buttons were not broken.
- Most likely culprit that I just handled and worked, i did have to use the MSM tool, several times - and re-unlock the BL, several times I would not even get the chance to get to fastboot, just a screen saying Build and Hardware not a match"" in yellow letters and it just bootlooped. No fastboot is no good, but when you said the tool would show some signs of working but then not, I have 2 solutions that I needed on diffrent occcasions.
1 - As mentioned fully try other USB cables, and ports, if you pull the usb-c out of the port and hold <power + vol up + vol down> eventually it will do something, very picky, sometimes gotta move your fingers to different spots on the buttons and also after 15-20sec let go of power and hit and hold it again... after a few seconds before it vibrates stick the cable in connected to your PC and the screen will be black (obv) but the msm tool will pick up on it. I know about the cables because I take good care of my phones and cables and charging ports, however on my final fix today it showed in msm tool it was connected but waiting for device.... Fed up i put the phone down and moved the usb cable a little bit and it picked up on it and did its thing! That part was just the cable, getting into qualcomm mode or w.e. is a bit tricky sometimes.
- Also someone said set it down for a while and come back to it.. THAT WORKS!! Let it fully charge and often just plugging in charger turns it on, bootloop soft brick or however have you, very simiilar to an Apple device and their DFU (don't f up mode cause screen is black..)
I hope that helps you get in touch with your family and friends.. Whatever you do, don't give up bc if you have not got it yet, you will! One other note, there are a few different msm tools available and they look the same some same size, but the one that supposed to work on my phone didn't and one that they say only a fool would attempt to try actually saved me, so if all else fails, use a different msm tool/usb cable and you will get it! I don't think I can post links yet I am on here very rarely, but plan on more! I have received so much help from XDA throughout the years on thousands of phones with just software issues alone, aas well as guides to my own phones. I would be honored to give back as I also have some extensive knowledge on many devices but I am a noob in comparison to many! Stay safe, good luck and please update and let us/ me know how it worked out for you. If i can help further I will, I have every firmware file for the OP6t, recovery, tools, software, this is not new to me but I feel your frustration!