Related
Got my new nexus 6 today
updated to android 5.1.1
am from touchwiz most of my life
any apps i sud be using
and how to root this thing?
i mostly used odin all my life guess no use of that here anymore
so any guidance is highly appreciated....
advance thanks
MD0038 said:
Got my new nexus 6 today
updated to android 5.1.1
am from touchwiz most of my life
any apps i sud be using
and how to root this thing?
i mostly used odin all my life guess no use of that here anymore
so any guidance is highly appreciated....
advance thanks
Click to expand...
Click to collapse
http://www.wugfresh.com/nrt/ and download the tool. The tool can be used to root the nexus 6
http://forum.xda-developers.com/showthread.php?t=2948481
Face_Plant said:
http://forum.xda-developers.com/showthread.php?t=2948481
Click to expand...
Click to collapse
will go through thee whole thing and understand if not hope you al help me a bit
XxCyberHackerxX said:
http://www.wugfresh.com/nrt/ and download the tool. The tool can be used to root the nexus 6
Click to expand...
Click to collapse
ok, or you can root your device the right way, within 3-4 minutes. where is the guidance in using a tool kit? considering you learn absolutely zero from it, and toolkits occasionally mess things up as well.
simms22 said:
ok, or you can root your device the right way, within 3-4 minutes. where is the guidance in using a tool kit? cinsidering you learn absolutely zero from it, and toolkits occasionally mess things up as well.
Click to expand...
Click to collapse
Very true. But he indicated he was a novice so the toolkit would guide him through the process
XxCyberHackerxX said:
Very true. But he indicated he was a novice so the toolkit would guide him through the process
Click to expand...
Click to collapse
Toolkit is good but i want to learn all things
XxCyberHackerxX said:
Very true. But he indicated he was a novice so the toolkit would guide him through the process
Click to expand...
Click to collapse
tool kits are not for novices, at all. they do not guide you through anything. toolkits are fine to use, when you know whats going on. but when you dont, you arent taught a single thing.
XxCyberHackerxX said:
http://www.wugfresh.com/nrt/ and download the tool. The tool can be used to root the nexus 6
Click to expand...
Click to collapse
DO NOT use the toolkit till unlocked and know how to use manual fastboot. Will not know why toolkit failed and will not know how to recover as it will take fastboot to recover. I did Odin also. It was a dependable tool. Fastboot is the old tried and true Nexus, HTC tool. Virtually unbrickable. The toolkit can brick you and will require fastboot knowledge to fix. Fastboot update only takes 2-3 minutes once set up and know what you are doing.
Just to echo what everyone else is saying, toolkits are great but only use them if you understand what they're doing. Using fastboot the first time.round is essential for learning.
All.threads are in nexus 6 general > sticky roll-up
Including my adb and fastboot thread,. Which is good for noobs.
HaHaa. I actually had more problems and failed flashes with Odin and "the toolkit". Never had a fail with fastboot.
Toolkits.... Not. Do it manually with all the proven guides posted!
MD0038 said:
and how to root this thing?
Click to expand...
Click to collapse
There are already advices given by real experts.
I humble add some " why's " not to start rooting for the first time with a toolkit.
A. There are so many options; it easy to make a mistake.
B. Toolkits use scripts and once started you are not fast enough to stop the process when you do something wrong.
C. When you know how to use command lines
with adb and fastboot, you will be prepared for toolkits.
D. You will find here complete rooting guidelines in sticky threads. Read them.
Nice rooting!
Thanks everyone for overwhelming support read half of the thread will do rest of the work tomorrow some assignments to do
Sent from my Nexus 6 using Tapatalk
Hey everyone I'm looking here as my last resort before sending my phone back to Motorola.
Bought a Nexus 6 from motorola uk which was delivered yesterday, switched phone on and all the Google apps on the phone updated, then had a notification OTA to download and install android 5.1 which I did, towards the end of the install process I had an error with the green android and a red exclamation mark.
I powered the device off with the power button and it turned back on and ever since it says "Android is starting" "Optimizing app 1 of 125" once it goes through all the apps it gets to the android boot screen then just goes back to the "Android is starting" "Optimizing app 1 of 125" over and over and over. (Infinite bootloop)
Pointers: The phone is not unlocked or rooted as I'm a noob its just fresh out the box, also I never opened/unlocked the developer options.
I have tried various recovery mode fixes, wiping cache and wiping all data and then rebooting the device with no luck.
Is there anyway I can hook my N6 up to my computer and fix this with a tool kit etc? I'm willing to try but I'd need basic instructions and reassurance it wouldn't muck up my warranty if it didn't work as my only other option is to exchange for a new device.
I'm a noob so I need detailed basic step by step instructions.
Any help, advice etc would be hugely appreciated. Thanks
Just send it back, no point messing about with it if it brand new could down to a fault with the hardware itself.
ixon2001 said:
Just send it back, no point messing about with it if it brand new could down to a fault with the hardware itself.
Click to expand...
Click to collapse
Iv'e heard this is a common problem with the N6 whilst trying to update the OTA 5.1 I had no other apps on the phone it was fresh, I did nothing wrong, I know someone who has been through 4 devices with the same bloody issues! In the end he had to sideload 6.0 and I'm not confident in being able to do that.
Well best bet is to download wugfresh toolkit 2.10 i think is the latest version, follow the instructions carefully because first you need to unlock the bootloader then flash 6.0.1 which has just come out.
Using Wugfresh is the best way to go if your new to flashing & you can't really go wrong with it.
ixon2001 said:
Well best bet is to download wugfresh toolkit 2.10 i think is the latest version, follow the instructions carefully because first you need to unlock the bootloader then flash 6.0.1 which has just come out.
Using Wugfresh is the best way to go if your new to flashing & you can't really go wrong with it.
Click to expand...
Click to collapse
I`am sure most xperienced users (me included) will not agree with you The best way to unlock, flash and root is still adb/fastboot. Especialy for lesser xperienced users that are lost is something goes wrong while using the toolkit, wich happens frequently btw. Just check the help threads.
gee2012 said:
I`am sure most xperienced users (me included) will not agree with you The best way to unlock, flash and root is still adb/fastboot. Especialy for lesser xperienced users that are lost is something goes wrong while using the toolkit, wich happens frequently btw. Just check the help threads.
Click to expand...
Click to collapse
Lol it's not rocket science using adb, been doing that way for years but for somebody that never flashed, rooted ect I still think the toolkit best way to go at first because everything is done for you at a click of a button.
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.
ixon2001 said:
Lol it's not rocket science using adb, been doing that way for years but for somebody that never flashed, rooted ect I still think the toolkit best way to go at first because everything is done for you at a click of a button.
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.
Click to expand...
Click to collapse
Lets agree to disagree
OK
ixon2001 said:
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.
Click to expand...
Click to collapse
No, but because toolkits are always behind at least one version with marshmallow. People kept bricking their devices with toolkits when marshmallow came out and they thought they could root it. As 6.0.1 came out they'll do something else wrong.
Toolkits are not help. It's the lazy way if everything is already working and up to date.
Also what can a toolkit do if this phone doesn't even have developer options turned on? If it's in boot loop, as the OP said, then the Enable OEM unlocking was never set, then the only solution is to send it back. Unless there's a toolkit magic we don't know about.
Sent from my Nexus 6 running cyosp using Tapatalk
istperson said:
N
Also what can a toolkit do if this phone doesn't even have developer options turned on? If it's in boot loop, as the OP said, then the Enable OEM unlocking was never set, then the only solution is to send it back. Unless there's a toolkit magic we don't know about.
Click to expand...
Click to collapse
I think op created another thread http://forum.xda-developers.com/nexus-6/help/nexus-6-stuck-bootloop-trying-to-update-t3266100 for this issue - and was somehow able to unlock the bootloader (not sure how that worked if OEM unlock was never set)
jj14 said:
(not sure how that worked if OEM unlock was never set)
Click to expand...
Click to collapse
It was said that some of the first Nexus 6s with the original 5.0 came out with a bootloader that didn't check for this switch.
Hi everyone,
Please forgive any n00b questions.
I got started with rooting / custom ROMs on a Nexus 4, and I didn't realize at the time that this made things really easy and I didn't need to learn very much about how everything worked. Fast forward to last week -- I decided, at long last, that I was tired of using stock MM on my T-Mo G4 / H811. How hard could it be? Probably not much different from playing on my old Nexus 4 right? Lol, maybe not.
So now 72 hours later, my phone is hard bricked and will not enter download mode. and I need some assistance, if anyone would be so kind.
I will try to recount what I did:
To start with, I was using a Mac, so I used Homebrew to install Android platform tools / ADB.
I decided I wanted to try out LineageOS so I went ahead and followed their very clear steps (on LOS wiki) to unlock the bootloader install TWRP. However, TWRP doesn't seem to have an official build for the G4(!) so I had to look up and use one of the betas from this post. Is this where I went off the rails already? [Of course, very stupidly I also failed to make a complete backup of anything before going on ahead. Rookie mistake.]
After unlocking bootloader and flashing my TWRP beta, I was able to boot into TWRP just fine. I followed the normal prescribed steps of doing a Wipe (normal TWRP defaults -- system, cache, etc.?) before flashing the latest LOS nightly (14.1-something) and also the nano-x64 variety of gapps. I rebooted and got stuck with the LOS boot animation. I let this go for 55 minutes, so I am pretty sure it was an actual bootloop, not just the 1st-time-startup and optimization going on.
I rebooted into TWRP and decided to try a different ROM to see if that was the issue. So I wiped again, flashed another ROM (I believe it was a flavor of AOKP 14.1.x), flashed gapps again, and gave it another try. Again got stuck with an endless bootloop (45 minutes).
Since this is my daily driver, I decided to go back to stock. Found this thread, downloaded the MM-debloated zip, pushed to phone, and again Wiped + Flashed. This time, when I hit reboot, my phone was immediately hard-bricked. No startup screen, no nothing. That was quite unexpected. Also, the first time I had ever HARD bricked a device that I was playing with. Yikes!
Since then, I got a hold of a PC, and have been trying to revive the device by flashing an image to the microSD and booting into Download mode, in the form of this thread or this one.
I did get this to work briefly yesterday, or at least I got to Download Mode / Firmware Update screen, and then attempted to run LGUP with the KDZ file. However I ran into an error at about 9%, and couldn't continue -- and then I had to give back my loaner PC for the day. I also noticed that the LG Mobile Support tool was recognizing my phone NOT as an H811 but as something like HX230 or ... whatever it was, it was definitely wrong. Which is worrisome.
Today I'm giving it another try but my phone will not enter Download Mode at all, nor respond in any other way. I'm curious if this is a battery issue? So I am simply charging it for the time being. I also re-formatted the microSD and re-flashed the single .img just to be safe, but still can't get a response out of the phone. On my PC's device manager it is showing up as the common Qualcomm 9008 that a lot of people seem to have seen. No recognition from LG Mobile Support tool, nor from LGUP.
So ... what now?
It's possible that once my battery gets some charge again, maybe I'll be able to enter DL mode. Let's hope so.
However, I am also totally in the dark about which software version I should be using. 20i? 20p? I have no idea what these refer to, and I did not make any prior notes to capture the state that my phone was in before this all began. So IF I get to DL mode I will definitely need further instruction on the CORRECT KDZ FILE to be flashing. Else I will just compound my problems.
ANY tips or suggestions will be appreciated! Thanks so much.
Should have verified being on 20o firmware
Upon further reading, quite obvious, at the top of this thread, I definitely should have followed the Prerequisite steps. I did NOT verify that I was on 20o firmware. "OR RISK BRICKING YOUR DEVICE" is right.
So I bricked my device, in exactly the way I was warned not to do, it seems.
Still, what's the next step? Any thoughts?
freeradical426 said:
Upon further reading, quite obvious, at the top of this thread, I definitely should have followed the Prerequisite steps. I did NOT verify that I was on 20o firmware. "OR RISK BRICKING YOUR DEVICE" is right.
So I bricked my device, in exactly the way I was warned not to do, it seems.
Still, what's the next step? Any thoughts?
Click to expand...
Click to collapse
try search for a fix if not may be @steadfasterX knows how to help you.
Re: searching for unbrick solutions
raptorddd said:
try search for a fix if not may be @steadfasterX knows how to help you.
Click to expand...
Click to collapse
Thanks, I have been looking around for solutions, but can't seem to find anything aside from the unbrick-guides that I've already listed / already attempted.
Will hope for help from @steadfasterX ! Or some other knowledgeable / benevolent party.
freeradical426 said:
Thanks, I have been looking around for solutions, but can't seem to find anything aside from the unbrick-guides that I've already listed / already attempted.
Will hope for help from @steadfasterX ! Or some other knowledgeable / benevolent party.
Click to expand...
Click to collapse
Ok what was the last KDZ file you flashed which had worked? 20o?
As you have hard bricked your device you can try the sdcard method again if it works flash 20o again (of it it was 20o).
If you flash a lower version you will hard brick again.
If the sdcard doesn't work anymore for you you can try to flash with QFIL but beware to use the right one. If you use the wrong one it will convert your device and believe me that's not what you want. I can share the good ones but unfortunately maybe on next week first.
Otherwise search on your own for 9008 unbrick but check the md5sum of the programmer!! Compare it with the Evil one mentioned in my ARB list here: http://tinyurl.com/antirollg4 and DO NOT USE THE EVIL one..
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Ok what was the last KDZ file you flashed which had worked? 20o?
As you have hard bricked your device you can try the sdcard method again if it works flash 20o again (of it it was 20o).
If you flash a lower version you will hard brick again.
If the sdcard doesn't work anymore for you you can try to flash with QFIL but beware to use the right one. If you use the wrong one it will convert your device and believe me that's not what you want. I can share the good ones but unfortunately maybe on next week first.
Otherwise search on your own for 9008 unbrick but check the md5sum of the programmer!! Compare it with the Evil one mentioned in my ARB list here: http://tinyurl.com/antirollg4 and DO NOT USE THE EVIL one..
Click to expand...
Click to collapse
Thanks very much for the guidance! The post that you linked to REALLY helps. Until now I really was not sure what 10n, 20i, 20o, etc. referred to, aside from just various software versions. Having a definition for anti-rollback and further links to explain, really helps! This gives me more information and I might be able to self-resolve from here. I will give it a shot.
As for your question ... unfortunately there was NO instance where I flashed a working KDZ file, and I didn't know (due to my past experience with my Nexus) that I needed to check the STOCK software version of my phone before beginning to play with ROMs. In other words, I have no idea if I was on 20i, 20o, 20p, etc. From what I understand, this makes things a lot more difficult
Having looked at the linked thread just a little bit, it appears that using a 20o KDZ is the best bet -- because I bricked my device using a 20i ROM so I expect it was due to violating the anti-rollback restriction.
I will look into it more closely and come back if I hit another brick wall. Thanks so much!
If anyone cares, here are the ending results of all this ...
#1 Be wary of anti-rollback restrictions before you flash anything to your G4. You WILL brick your phone!
I tried multiple rounds and multiple variations of all the MicroSD card methods that I could find. I could NOT succeed in unbricking my phone.
#2 Luckily ... I was able to convince LG that I was still technically under warranty!
Because I had the stock bootloop issue in May 2017, LG did an in-warranty repair for me, and replaced the motherboard. So last week, I simply told them "my phone is AGAIN unable to charge and will not power on, just like in May". Since it had only been 5-6 months since the first issue, they agreed to replace the motherboard again.
Moral of the story: you can definitely unbrick your phone by having LG replace the mobo XD XD
From here, I think I will just totally avoid doing any rooting or custom ROMs on my totally-stock G4 coming today in the mail. I will cross my fingers and hope we get OEM Nougat in the USA sometime in the next couple of months.
Thanks again for the help everyone!
THIS GUIDE IS NOW OBSOLETE
Links will be added once the new guide using the firehose comes out - No more bricking!
Thanks to everyone who contributed to the firehose!
I just cut and pasted the whole guide into a txt file, which is linked below in case there's ever any purpose of looking at it again.
https://drive.google.com/file/d/1wTRMvweLlsF-3WU9CYlz7X3ZIRE3vtCs/view?usp=sharing
Isn’t Mr. Zhu the author of twrp?
You might want to wait until I get to my computer again as I realized there are a few minor edits that could be helpful. It's not letting me edit it successfully on my phone
Malossi94 said:
Isn’t Mr. Zhu the author of twrp?
Click to expand...
Click to collapse
Yeah but apparently he stopped development, but le Minh sent the Korean fix after that so I'm not entirely sure lmao
antintin said:
Yeah but apparently he stopped development, but le Minh sent the Korean fix after that so I'm not entirely sure lmao
Click to expand...
Click to collapse
Mr. Zhu repaired kor twrp, and my kor skt G8 participated in the repair development:silly:
Malossi94 said:
Mr. Zhu repaired kor twrp, and my kor skt G8 participated in the repair development:silly:
Click to expand...
Click to collapse
Nice! I'll edit as soon as I get on my computer
Hi have followed the guide and got stuck at step 7. I get only the LG V50Thinq powered by android screen and nothing more. It just stays like for the past 30 minutes. I have rebooted several times but the same. i cannot access (or do not know) download mode.
Any help!
So, if your on a korean version that wil be a q version of android vulnerable. Therefore at step 6, you will need a pie kdz to flash those 4 xbl files. Do not make my mistake, you will get bricked ))
Marmalux said:
So, if your on a korean version that wil be a q version of android vulnerable. Therefore at step 6, you will need a pie kdz to flash those 4 xbl files. Do not make my mistake, you will get bricked ))
Click to expand...
Click to collapse
Sorry I'm afraid I don't understand. That's step 4, and you don't need to flash the whole kdz. Only the partitions the guide says to.
antintin said:
Sorry I'm afraid I don't understand. That's step 4, and you don't need to flash the whole kdz. Only the partitions the guide says to.
Click to expand...
Click to collapse
I think he's referring to how its a bit confusing how it says you should use android pie but also implies that you should use latest pre-march firmware, which for korean variant is actually android Q not pie so its little confusing which you should use, i could be wrong though, thanks alot for this guide though!
9RR said:
I think he's referring to how its a bit confusing how it says you should use android pie but also implies that you should use latest pre-march firmware, which for korean variant is actually android Q not pie so its little confusing which you should use, i could be wrong though, thanks alot for this guide though!
Click to expand...
Click to collapse
If someone can't deal with the level of instruction I provided here, I would very much advise against attempting it as it is inherently very risky. Probably not what anyone wants to here, but it is what it is
This is great news. Has anyone Tested using a LOS GSI or AOSP GSI? I am on verizon and have found with another phone that all GSIs on android version 9 and 10 have "No Sim Card" errors and you can not make calls or send texts (strangely you can receive both). This error wasn't seen with other network versions of the phone (palm phone). I am a little hesitant to go through this process to find out if data doesn't work on LOS 17 or AOSP 10. If anyone on verizon tries this out, please report back on how well the GSIs work, or if you find a specific ROM that works on Verizon.
CaptainElwood said:
This is great news. Has anyone Tested using a LOS GSI or AOSP GSI? I am on verizon and have found with another phone that all GSIs on android version 9 and 10 have "No Sim Card" errors and you can not make calls or send texts (strangely you can receive both). This error wasn't seen with other network versions of the phone (palm phone). I am a little hesitant to go through this process to find out if data doesn't work on LOS 17 or AOSP 10. If anyone on verizon tries this out, please report back on how well the GSIs work, or if you find a specific ROM that works on Verizon.
Click to expand...
Click to collapse
I've used a lot of gsis like bless and caos (use those instead of aosp definitely). I haven't had any data issues
antintin said:
I've used a lot of gsis like bless and caos (use those instead of aosp definitely). I haven't had any data issues
Click to expand...
Click to collapse
But I have a sprint model. I'm pretty sure Verizon people have tried it with no issues already though
antintin said:
If someone can't deal with the level of instruction I provided here, I would very much advise against attempting it as it is inherently very risky. Probably not what anyone wants to here, but it is what it is
Click to expand...
Click to collapse
Hi, thank you very much for this tutorial.
It was my mistake and got a permanent brick. It is true that the vulnerable firmware for kor is android Q and i have achieved root after downgrading to a older Q version. My problem was at step 4 because i used the q kdz and i did not download a separate pie kdz for that step.
Now i hope no one else will make my mistake since i really do not see how to get DL mode active or to switch slots without the USB. Only thing i got is the image that precedes the DL mode and the IMEI display. And since the USB is basically dead i think firehose (even if i had it) would not recover my phone.
I have flashed and unlock many phones and this is my first unrecoverable brick. My first LG though and probably the last.
Marmalux said:
Hi, thank you very much for this tutorial.
It was my mistake and got a permanent brick. It is true that the vulnerable firmware for kor is android Q and i have achieved root after downgrading to a older Q version. My problem was at step 4 because i used the q kdz and i did not download a separate pie kdz for that step.
Now i hope no one else will make my mistake since i really do not see how to get DL mode active or to switch slots without the USB. Only thing i got is the image that precedes the DL mode and the IMEI display. And since the USB is basically dead i think firehose (even if i had it) would not recover my phone.
I have flashed and unlock many phones and this is my first unrecoverable brick. My first LG though and probably the last.
Click to expand...
Click to collapse
I'm very sorry to hear that, but the firehose could almost definitely help you unbrick. I tried to clarify more that it has to be a pie kdz now, because before I just wrote "load your pie kdz" and you probably missed that. There should still be a warranty though, so you could try to use that if you'd like. It might say that yours expired on the website, but you can just click past it.
antintin said:
Spoiler
I'm very sorry to hear that, but the firehose could almost definitely help you unbrick. I tried to clarify more that it has to be a pie kdz now, because before I just wrote "load your pie kdz" and you probably missed that. There should still be a warranty though, so you could try to use that if you'd like. It might say that yours expired on the website, but you can just click past it.
Click to expand...
Click to collapse
Thank you antintin for your reply. You bring me some hope. The warranty will not apply because it is stated clearly that any attempt to BL unlock will void it (I got it from a shop in Spain via Ebay).
But the firehose on the other hand.... When do you think it will be available? And how will i ba able to get it?
Thank you very much!
Marmalux said:
Thank you antintin for your reply. You bring me some hope. The warranty will not apply because it is stated clearly that any attempt to BL unlock will void it (I got it from a shop in Spain via Ebay).
But the firehose on the other hand.... When do you think it will be available? And how will i ba able to get it?
Thank you very much!
Click to expand...
Click to collapse
Other people who bricked while different bl unlock methods were tested sent it in for warranty with no issues. The firehose will be available in November at the earliest probably. Proof of purchase from eBay should be enough, but I don't if there's any lg repair centers in Spain that support phones.
antintin said:
Other people who bricked while different bl unlock methods were tested sent it in for warranty with no issues. The firehose will be available in November at the earliest probably. Proof of purchase from eBay should be enough, but I don't if there's any lg repair centers in Spain that support phones.
Click to expand...
Click to collapse
In Spain there are several. But i`m in Ireland, and here is none ))
Successfully rooted korean variant, thanks for the guide! I was wondering if its okay now to update to newest firmware via LGUP upgrade mode? (I really want the system wide accent color customization in newest firmware, among other things) I assume it should be but i really don't wanna have to redo all this so id rather just ask, thanks in advance!
I installed LineageOS, but bluetooth isn't working, and I've had no luck fixing it. I honestly didn't like it more than stock, and I have no desire to fight to make it work.
I just want to go back to stock, but I have had no luck.
Is there some guide to do this that I just cannot find?
I've downloaded what I believe is the most recent full ROM for this device (055f1d0089a2a397bebd5882a9a63bdb779f4834.zip), but trying to flash it using the same tools and method as installing Lineage just is not working. Most recent effort resulted in "Denying OTA because it's SPL downgrade
My brain hurts from searching for answers, and not I just want to give up, but I have a completely factory reset phone in front of me, and I need to get this resolved.
Any help will be much appreciated.
JustinChase said:
I installed LineageOS, but bluetooth isn't working, and I've had no luck fixing it. I honestly didn't like it more than stock, and I have no desire to fight to make it work.
I just want to go back to stock, but I have had no luck.
Is there some guide to do this that I just cannot find?
I've downloaded what I believe is the most recent full ROM for this device (055f1d0089a2a397bebd5882a9a63bdb779f4834.zip), but trying to flash it using the same tools and method as installing Lineage just is not working. Most recent effort resulted in "Denying OTA because it's SPL downgrade
My brain hurts from searching for answers, and not I just want to give up, but I have a completely factory reset phone in front of me, and I need to get this resolved.
Any help will be much appreciated.
Click to expand...
Click to collapse
Have you tried to MSM back to stock yet? Here are the instructions and downloads.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
JustinChase said:
I installed LineageOS, but bluetooth isn't working, and I've had no luck fixing it. I honestly didn't like it more than stock, and I have no desire to fight to make it work.
I just want to go back to stock, but I have had no luck.
Is there some guide to do this that I just cannot find?
I've downloaded what I believe is the most recent full ROM for this device (055f1d0089a2a397bebd5882a9a63bdb779f4834.zip), but trying to flash it using the same tools and method as installing Lineage just is not working. Most recent effort resulted in "Denying OTA because it's SPL downgrade
My brain hurts from searching for answers, and not I just want to give up, but I have a completely factory reset phone in front of me, and I need to get this resolved.
Any help will be much appreciated.
Click to expand...
Click to collapse
Did you follow the MSM guide? I have had to run it a million times so if you need help...
devildogwillbur said:
Did you follow the MSM guide? I have had to run it a million times so if you need help...
Click to expand...
Click to collapse
I did eventually find the download and run it successfully. It was frustrating that I had to update about 5 or 6 times to get up to date, but it did eventually get me back to a fully updated, stock phone.
thank you.
thanks!