So here's the story..
Everything was running beautifully, I got bootloader unlocked, TWRP installed and rooted with Magisk, even a few modules and of course my favorite Viper4android... All without having to ask any questions. Super silky smooth thanks to all the amazing devs here that made it so easy ?
... The problem, I'm not incredibly familiar with Magisk hide and everything was going phenomenally but low and behold the play store had to show up with an warning notification that Viper could be harmful... It wouldn't allow me to dismiss it, so like the amazing genius I am I remember that Magisk hide is used to hide things from the store...Rrrright?
Not sure if this matters but Viper was a system app at the time and yeah I TRIED to hide it ??
... thought everything was cool for about 30 seconds
... phone shut down, booted to recovery
.... So I thought, ehhh no big deal I'll just do A WIPE and restore my back up
restored the back up.... Seemed to anyhow, went through the complete process.
I went to reboot system and NADA just boots back to TWRP for a moment anyhow...
So then I'm thinking oh well I'll just go back in to restore my backup AGAIN... NOTHING'S THERE!
I go to SDcard and it's nothing but a bunch of folders with jumbled alphanumerics
Fuhhh...
At some point it stopped letting me reboot TWRP, not sure how to differentiate when, but it just loops straight back to Fastboot now Everytime and I can see my device in the computer but I try fastboot boot twrp.img and it says something like failed can't recognize boot.
Edit: (I guess this has to be in the form of a question)... What do I do?
Causical said:
So here's the story..
Everything was running beautifully, I got bootloader unlocked, TWRP installed and rooted with Magisk, even a few modules and of course my favorite Viper4android... All without having to ask any questions. Super silky smooth thanks to all the amazing devs here that made it so easy
... The problem, I'm not incredibly familiar with Magisk hide and everything was going phenomenally but low and behold the play store had to show up with an warning notification that Viper could be harmful... It wouldn't allow me to dismiss it, so like the amazing genius I am I remember that Magisk hide is used to hide things from the store...Rrrright?
Not sure if this matters but Viper was a system app at the time and yeah I TRIED to hide it
... thought everything was cool for about 30 seconds
... phone shut down, booted to recovery
.... So I thought, ehhh no big deal I'll just do A WIPE and restore my back up
restored the back up.... Seemed to anyhow, went through the complete process.
I went to reboot system and NADA just boots back to TWRP for a moment anyhow...
So then I'm thinking oh well I'll just go back in to restore my backup AGAIN... NOTHING'S THERE!
I go to SDcard and it's nothing but a bunch of folders with jumbled alphanumerics
Fuhhh...
At some point it stopped letting me reboot TWRP, not sure how to differentiate when, but it just loops straight back to Fastboot now Everytime and I can see my device in the computer but I try fastboot boot twrp.img and it says something like failed can't recognize boot.
Edit: (I guess this has to be in the form of a question)... What do I do?
Click to expand...
Click to collapse
Hi there. So the warning from the play store was actually from "play protect" which you can disable IN the play store in the left pull out menu. Not something you need Magisk hide for. Now the folders with jumbled characters are because of encryption. When you restored your backup, the device's encryption went wack on you, which happens with this device if you install or restore anything with a previous security patch than you currently have. It's annoying, but you either have to format your data entirely, or (what I recommend) use the MSM Download tool that can be found here in the guide section of this forum. Use the T-Mobile version of the tool if you have a T-Mobile variant of the device, and the global version if you have the global version of the device. What you could try to back up your important stuff, boot TWRP with fastboot using "fastboot boot [TWRPfilename]" and you might be able to plug in your device to a PC to save stuff first. But yeah, MSM tool is your best bet, that has happened to me before, and the play protect option in the play store is what you should have disabled instead of using Magisk for it.
H4X0R46 said:
Hi there. So the warning from the play store was actually from "play protect" which you can disable IN the play store in the left pull out menu. Not something you need Magisk hide for. Now the folders with jumbled characters are because of encryption. When you restored your backup, the device's encryption went wack on you, which happens with this device if you install or restore anything with a previous security patch than you currently have. It's annoying, but you either have to format your data entirely, or (what I recommend) use the MSM Download tool that can be found here in the guide section of this forum. Use the T-Mobile version of the tool if you have a T-Mobile variant of the device, and the global version if you have the global version of the device. What you could try to back up your important stuff, boot TWRP with fastboot using "fastboot boot [TWRPfilename]" and you might be able to plug in your device to a PC to save stuff first. But yeah, MSM tool is your best bet, that has happened to me before, and the play protect option in the play store is what you should have disabled instead of using Magisk for it.
Click to expand...
Click to collapse
Dang I was kind of afraid of that MSM tool thing, I'm going to have to do a little reading on that. That's one thing I've never done on an Android for sure.
Thank you
... On another note conveniently my Laptop keys ZXCVM just stopped working WTF! Not cool timing, I just bought it.
Causical said:
So here's the story..
Everything was running beautifully, I got bootloader unlocked, TWRP installed and rooted with Magisk, even a few modules and of course my favorite Viper4android... All without having to ask any questions. Super silky smooth thanks to all the amazing devs here that made it so easy ?
... The problem, I'm not incredibly familiar with Magisk hide and everything was going phenomenally but low and behold the play store had to show up with an warning notification that Viper could be harmful... It wouldn't allow me to dismiss it, so like the amazing genius I am I remember that Magisk hide is used to hide things from the store...Rrrright?
Not sure if this matters but Viper was a system app at the time and yeah I TRIED to hide it ??
... thought everything was cool for about 30 seconds
... phone shut down, booted to recovery
.... So I thought, ehhh no big deal I'll just do A WIPE and restore my back up
restored the back up.... Seemed to anyhow, went through the complete process.
I went to reboot system and NADA just boots back to TWRP for a moment anyhow...
So then I'm thinking oh well I'll just go back in to restore my backup AGAIN... NOTHING'S THERE!
I go to SDcard and it's nothing but a bunch of folders with jumbled alphanumerics
Fuhhh...
At some point it stopped letting me reboot TWRP, not sure how to differentiate when, but it just loops straight back to Fastboot now Everytime and I can see my device in the computer but I try fastboot boot twrp.img and it says something like failed can't recognize boot.
Edit: (I guess this has to be in the form of a question)... What do I do?
Click to expand...
Click to collapse
have something similar like you and my phone every time go to fastboot so what I have done is installed rom from fastboot and it worked like a charm my phone was up and running. Little notice if you going to install rom via fastboot you will get some error message but just ignore it and wait till phone reboot and it will erase all data on the phone.
Here is the link if you chose to try just read all before on page one
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Sipi1302 said:
have something similar like you and my phone every time go to fastboot so what I have done is installed rom from fastboot and it worked like a charm my phone was up and running. Little notice if you going to install rom via fastboot you will get some error message but just ignore it and wait till phone reboot and it will erase all data on the phone.
Here is the link if you chose to try just read all before on page one
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Click to expand...
Click to collapse
thank you all for your replies, however I'm beginning to get really frustrated. I'm trying to use the MSM tool and how do I frickin run an .exe when the damn thing is a .rar format, the instructions under that thread are not particularly descriptive. Do I extract it? do I have to run something in a window somewhere? if my device is in EDL and the port shows Qualcomm HS-USB QDLoader 9008 (COM6) is that good?
OMG!
Causical said:
OMG!
Click to expand...
Click to collapse
MSM tool isn't too bad really. You're issue there is most likely a corrupted download. Redownload the entire tool and try to extract it again. Let me know what happens!
H4X0R46 said:
MSM tool isn't too bad really. You're issue there is most likely a corrupted download. Redownload the entire tool and try to extract it again. Let me know what happens!
Click to expand...
Click to collapse
I redownloaded that same one at least twice now... Am I doing right by using WinRAR? I just downloaded from official site the trial version.
This has got me wanting to repeatedly dropkick myself in the larynx.
....#slowassWiFi
Causical said:
I redownloaded that same one at least twice now... Am I doing right by using WinRAR? I just downloaded from official site the trial version.
Click to expand...
Click to collapse
Yes, you are doing it right.
I would use 7zip but winRAR is fine. Dont know why someone would be using that in this day and age... but hey, it works...
I have also read other random threads that says that the file is corrupt. If you cant get a good download let me know and I will upload my collection of files. Send me a PM if you need me to upload. It wont be for a couple hours though...
Apparently they're all corrupt. I just downloaded 9.0.11 after doing .12 first and I'm getting the same errors in WinRAR
Yeah good call on 7-zip, I uninstalled winrar... complete garbage, all changing my folder icons without my consent and stuff.
Causical said:
Yeah good call on 7-zip, I uninstalled winrar... complete garbage, all changing my folder icons without my consent and stuff.
Click to expand...
Click to collapse
Was it Ok with 7Zip?
Scott said:
Was it Ok with 7Zip?
Click to expand...
Click to collapse
No lol, but it's a little more clear that the file is corrupt I suppose ?
Edit: Hey I'm going to try the recommendation of the other guy ^^up there with the fastboot ROM, I don't think it will work because I don't think fastboot is recognizing my boot, but guess we'll see... I'm just curious do you recommend doing the flash-all-partitions-fastboot.bat? Or the "Big One" flash-all-partitions.bat...I feel like I'm on the verge of really slipping deeper into the abyss here.
Here I go... Hope you reply within next 30 seconds lol
Edit: Ho-Ly poop I think that was the single most terrifying event of my life... IT WORKED! I used Mauro's fastboot ROM technique....uuggghhh
I think I used flash all bat and that work for me but phone was reset to factory settings after that
---------- Post added at 03:29 AM ---------- Previous post was at 03:23 AM ----------
Causical said:
Here I go... Hope you reply within next 30 seconds lol
Edit: Ho-Ly poop I think that was the single most terrifying event of my life... IT WORKED! I used Mauro's fastboot ROM technique....uuggghhh
Click to expand...
Click to collapse
im glad it worked, have the same filing as you when I brick phone and then make him work again.
Sipi1302 said:
I think I used flash all bat and that work for me but phone was reset to factory settings after that
Click to expand...
Click to collapse
That's alright, I'll reset everything. Thanks A Bunch dude, that was scary.
Remember kids, Magisk hide is bad mmmkay, don't do Magisk hide!
... All this because I didn't want a pesky warning notification gyollee dude, that allowed me to get absolutely nothing else done on my day off work lol.
Causical said:
That's alright, I'll reset everything. Thanks A Bunch dude, that was scary.
Remember kids, Magisk hide is bad mmmkay, don't do Magisk hide!
Click to expand...
Click to collapse
you welcome, Im glad I could help.Now you will know for the next time hehe:laugh:
I think MSM tool would still be valuable to know how it works, but let's hope I don't need it.
At least you are up and running!
But yeah, the MSM tool is pretty easy to use. If you ever used ODIN on a Samsung phone it would be familiar.
Related
Hello my fellow XDA Members. I am stuck in a tight spot and after reading and re-reading some things the situation doesn't look very promising. I hope this is the moment that Karma shows up and I can get some help on this. Here it goes.
Specs - LG G2 D801 Variant > TWRP V2.8.3.1 > NO OS Currently
I was running Cloudy G3 Rom smoothly and got bored and decided to flash that new rom that is a 5.0 Rom all variants. Did the usual back ups and flashed it. Something happened when I flashed the rom. It went through the Aroma installer and then said "successful" but stuck in a bootloop. I tried it again and nothing happened. Then I tried to wipe everything again and started getting an E: Cannot mount (data or system I forget which as that error went away after I completely formatted data, wiped everything and reflashed Cloudy Stock. )
> Cloudy stock bootlooped and nothing is happening in TWRP. I Am using the USB OTG method of getting files on the phone and getting it charged but anytime I try to do anything (flash a rom, an older version of TWRP) it just immediately restarts TWRP and thats that. I have No OS at all.
> I tried to use one of the methods to get into download mode and flash a stock KDZ but the phone acts like it is going into DL mode (shows the little blue transition screen) but never gets into the ACTUAL download mode where the PC or flash tool can recognize it.
So in a nutshell > No OS > I can get into TWRP but it does nothing > No Download Mode > Don't want a new phone > Don't want to take it apart and try to short circuit anything if possible. LOL.
I am totally stuck here. I am done alot of work and even helped friends and family out with their devices over the years. I am just not sure if I need to consider it a done deal and get a new phone or maybe one of you guys know of something easy and obvious (please let it be the latter) I am missing. Thanks for any help you can offer. I Will be standing by.
Have you tried to reflash bootloader? If not, do that and reflash cloudy right away
wisefreakz said:
Have you tried to reflash bootloader? If not, do that and reflash cloudy right away
Click to expand...
Click to collapse
I haven't thought about flashing a bootloader. How would I flash the bootloader if I can not the phone into either DL mode and or TWRP doesn't do anything either? Is a bootloader file just a flashable file like any other .zip file?
jcnbama said:
I haven't thought about flashing a bootloader. How would I flash the bootloader if I can not the phone into either DL mode and or TWRP doesn't do anything either? Is a bootloader file just a flashable file like any other .zip file?
Click to expand...
Click to collapse
@jcnbama
Have you tried this or this?
euphoria360 said:
@jcnbama
Have you tried this or this?
Click to expand...
Click to collapse
The first one I can not do as I do not have any knowledge at all of Ubuntu, Linux, or any of that. It would take forever to get a working knowledge of that software in order to get things going again. I would probably just have to either take it to a cellphone repair shop or get another phone before I could do the first link.
I have not tried the second one but it is a viable option. I was looking at it online and trying to talk myself down from having to do that. I would reallllllllly rather not have to take my phone apart if I can keep from so that's kind of what this post is all about. Just trying to see if anyone knows of ANYTHING else before I go taking apart my phone.
Can you describe more about "twrp doesnt do anything"?
Does twrp boot up?
Can u see/wipe partitions?
Can u install any rom in twrp? Does it finish?
euphoria360 said:
Can you describe more about "twrp doesnt do anything"?
Does twrp boot up?
Can u see/wipe partitions?
Can u install any rom in twrp? Does it finish?
Click to expand...
Click to collapse
TWRP boots and I can go into wipe, advanced wipe, and format data and it says it's successful. I can use file manager and move items back and forth from USB OTG. If I try to flash anything it just reboots TWRP immediately so I can't install any .zip files at all.
My guess is that your bootloader is damaged.
The only option i can see for you is that Ubuntu thing i shared with you. So, lets stop acting lazy and do what needs to be done. Dont scare since there is nothing to loose. LG G2 is unbrikable
Booting up ubuntu or any other linux os is so easy. And there is nothing much to learn. Trust me.
Go to ubuntu website and download their newest iso file. Burn it on dvd and boot it up. You dont have to install it, just choose "live mode" and it boots up. Just like that. Then yiu can proceed with tutorial mentioned above and it shouldnt take more than an hour from you. Its all typing some commands in terminal (remember CMD in windows!).
Just make sure to download the files mentioned in that tutorial before proceeding.
euphoria360 said:
My guess is that your bootloader is damaged.
The only option i can see for you is that Ubuntu thing i shared with you. So, lets stop acting lazy and do what needs to be done. Dont scare since there is nothing to loose. LG G2 is unbrikable
Booting up ubuntu or any other linux os is so easy. And there is nothing much to learn. Trust me.
Go to ubuntu website and download their newest iso file. Burn it on dvd and boot it up. You dont have to install it, just choose "live mode" and it boots up. Just like that. Then yiu can proceed with tutorial mentioned above and it shouldnt take more than an hour from you. Its all typing some commands in terminal (remember CMD in windows!).
Just make sure to download the files mentioned in that tutorial before proceeding.
Click to expand...
Click to collapse
First of all calling people lazy is not nice. I'm not lazy I am trying to play it safe. I wouldn't want to brick it to the point to where I don't even have recovery and it can not even be charged any longer. I have Ubuntu on my desktop upstairs. I have used it a little. It's not that I am completely ignorant to Ubuntu I am just a total novice. Also the issue described in that post doesn't exactly match my situation. I am not in a black screen. It's more like a bootloop that I can not get out of because TWRP is not doing what it needs to do and I can not flash TWRP a ROM or get into DL mode at all. Also that post says,
"VERY IMPORTANT!!!!!!! You must use the img files that correspond to the ROM you have installed before getting the problem to avoid breaking your phone."
I don't have a rom on my phone soooo...
You didn't answer my question well. If on TWRP you can finish installing rom without any error, and you keep coming to twrp after restarts, that's another situation. Try this:
http://forum.xda-developers.com/showthread.php?t=2451696
But if you cant even finish install in twrp (twrp gives you errors or just restarts before giving you "successful", either you have problem in rom you try to flash or you need to build everything up from start.
That lazy thing was for encouraging you to do it.
And you cant brick your device. There is always a way on G2.
For img files: find them from last stock rom that was working on your phone.
Deleted
Credit goes to dbgr for finding this:
https://forum.xda-developers.com/idol-4s/how-to/6055u-root-method-t3598947
Link to download .rar:
https://mega.nz/#!U24zwYbQ!MwbIX_D01OyHHldd8c_9iCmht6wzcw1duNpGO-PRyWI
This is just a simpler, more detailed guide on how to root this phone.
Forgive me for the lack of pictures, its pretty straightforward anyways. I have included a .rar with this post that has all the essential files you will need.
(I only compressed the .rar, everything else credit goes to the creators)
1. Download the rootpackage.rar i have included, and decompress to somewhere safe.
2. Install SugarQct and install the drivers that came with it. (In the SugarQct installer, not the usb driver folder)
3. After that has finished, open the usb driver folder and run the setup.vbs script there. It should only take a second or two to run.
4. Plug phone into pc.
5. Place supersu.zip onto phone. You can put this anywhere, doesn't really matter.
6. Turn phone off and place into download mode. (Phone must be plugged in to allow download mode)
4. Open sugar with phone plugged in. Be sure to upgrade sugar if you can't see the 6055u in the list.
Set to 6055u, go to options, select save user data. Now press upgrade.
5. While sugar is downloading overwrite the r*****.mbn in bin/6055-*****. This folder appears once you start to download to the phone. You must rename the twrp_recovery_idol4_6055.img to the name of the r*****.mbn.
6. Overwrite again while files are being written. Do this as many times as you please. I only overwrote it more than once as a safety precaution.
7. Before sugar has completed fully, but after files are written, this should be around the time when it starts to download more files. As long as the writing completes you are good to go.
8. Turn phone on and enter recovery mode (power + volume up).
9. In the custom recover menu tap install and install the supersu.zip from the directory you placed it in.
10. Give it a couple of seconds (mine took 30 or so)
11. Allow phone to be rebooted and its now rooted!
Now I've had some interest in using magisk instead of supersu, but i haven't been able to install it after supersu. Choose your rom to flash wisely, as its a pain in the ass to go back from.
Please enjoy your newly rooted Alcatel Idol 4!
Thanks all!
P.S. If someone can dump their standard rom before they flash supersu.zip onto their phone, i'd like to try and find a way to get a custom rom goin and that would help.
I'm not seeing the download for the .RAR file. Am I missing something?
SeanMcCarte said:
I'm not seeing the download for the .RAR file. Am I missing something?
Click to expand...
Click to collapse
I thought i attached it to the thread, give me a second and i'll try again.
Edit:
It seems my rar is too large, i'm headed to work now, but i'll try and get something uploaded in a bit.
Thank you. Much appreciated. Also,can I unplug the phone before rebooting to recovery,or does it have to be plugged in!
SeanMcCarte said:
Thank you. Much appreciated. Also,can I unplug the phone before rebooting to recovery,or does it have to be plugged in!
Click to expand...
Click to collapse
As far as i know it doesn't have to be, but when i was successful i believe i had the phone plugged in. I did try to do somethings earlier today and unplugged the phone, and it was not successful. I do not know if it was because i unplugged the phone or if it was because i had failed to rewrite the recovery flash.
Thank you. I actually didn't want to wait for .rar so I just pieced the files from the forum here. Thank you anyway,at least somebody else will get the RAR. Also,my phone was plugged in when it worked.
I got magisk working for me I unistalled super super went into twrp and installed magisk ( I needed magisk to play fire emblem heroes lol) I'm not sure if I did something else but that's what I remember doing
Is this guide working for all the idol 4 variants or just for the cricket one? I've got the 6055k and I'm wondering if this guide works for my phone too.
scofield119 said:
Is this guide working for all the idol 4 variants or just for the cricket one? I've got the 6055k and I'm wondering if this guide works for my phone too.
Click to expand...
Click to collapse
Theres another guide for the 6055k, i'm not sure if this will work for that one. I know it works for the cricket version and i see no reason why it wouldn't work for the 6055k, but it is a better idea to follow the guide made for the 6055k.
link22534 said:
I got magisk working for me I unistalled super super went into twrp and installed magisk ( I needed magisk to play fire emblem heroes lol) I'm not sure if I did something else but that's what I remember doing
Click to expand...
Click to collapse
Would you mind checking if snapchat works on magisk? I know it doesn't work on supersu, and i've unrooted my phone because i was having troubles getting it installed after supersu.
NeonWhitey said:
Would you mind checking if snapchat works on magisk? I know it doesn't work on supersu, and i've unrooted my phone because i was having troubles getting it installed after supersu.
Click to expand...
Click to collapse
Yep it works I had to change a setting to get magisk hied working it was magisk core only mode and I pass the netsaftey check
link22534 said:
Yep it works I had to change a setting to get magisk hied working it was magisk core only mode and I pass the netsaftey check
Click to expand...
Click to collapse
Thanks for the info, but funnily enough i'm having difficulties getting the damn thing rooted again.
Thanks for the write up, I've flashed and reflashed many times... you have to be carefully about when you interrupt the process. Also know that a newer version is out. Cheers mate.
I'm not sure if it's the latest version of Sugar, but I've been trying so many times, but to no avail. Has anyone had any luck on the new version?
SUGAR QCT_SP V11.3.0
I've gotten to the point that when I start the upgrade with Sugar, it says my phone is already rooted. However, when I try to access Recovery, there is no option to install TWRP. It looks like it just loaded the same old recovery...no matter how fast and how many times I replace the Rxxxxxx.mbn file.
Cheers,
Wickster
6055p
is there any guide to root 6055p model
no luck getting this to work guys, could really use some help
Having the same problems as PizzaG - tried all the timing tips no TWRP
Having the same situation as PizzaG - same Cricket version, using the newer version of Sugar QCT 11.1.3. I've tried starting right after it reaches the last written file (4095M), Ive even tried waiting until you get the vibrate and Alcatel logo (which happens at the very end of the download, but was someone's tip), same story, boots into Android recovery. Any other tips?
Possible Solution to Rooting Troubles
I was having the same troubles as the above posters. What seemed to be the problem was that I had set a pin code to unlock my device, which made it encrypted. Unfortunately, the only way to remove a pin is to do a factory reset. Anyway, I did a factory reset and ran sugar immediately after - making sure to start the phone before sugar finished - and it worked! Perhaps there is something simpler to do and I didn't have to do a factory reset, but I don't know what that is, and this worked.
Someone have try with the 6055A?
hmm, im noticing mine says encrypted as well but i never set anything for security. just the swipe. @ ThisEndsInTears did you do a factory reset from stock recovery or from withing the phone settings? Thanks much, hopefully one step closer to getting this rooted. Y has nobody developed cm for 6.0.1 for this? cm13 im pretty sure it is
Script to fix the Nexus 5X / Nexus 6P Bootloop problem
Credits
99% credit goes to @squabbi for teaching how to patch files yourself and @XCnathan32 for discovering the fix itself.
1% for me for making the script .
DISCLAIMER
THIS PROCESS WIPES ALL YOUR DATA (unless your bootloader is already unlocked) AND PROBABLY YOUR WARRANTY TOO! USE WITH CAUTION! I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE!
THIS PROCESS WILL MAKE YOUR PHONE SLOWER (6P 2 times slower, 5X 1.5 times slower)! PLEASE USE ONLY AS A LAST RESORT!
PLEASE CONTACT YOUR WARRANTY TO TRY AND GET A REPLACEMENT BEFORE PROCEEDING!
What does the fix do?
The problem with those phones are the cores of the Cortex A57, and they need to be disabled.
What should you do?
Before proceeding, make sure you have OEM Unlocking enabled on your device, or the flashing won't work!
1. Download the zip below
2. Extract the zip
3. Extract the boot.img from the image you've downloaded (the script explains how to do it if you don't know how) to the folder you've downloaded
4. Open "Script.bat"
You should also download a factory image from this link (unless you live in Japan, don't download the Softbank versions, and unless you live in Australia, don't download the Telstra versions):
6P - https://developers.google.com/android/images#angler
5X - https://developers.google.com/android/images#bullhead
The script itself was not tested, but the method did work on my 5X so it should work.
If you have any requests, you can comment them here, and maybe I'll add them. One day.
I do plan on adding TWRP, Elemental X and Magisk patching one day, and if there will be many requests that day will come earlier.
Links to original posts and videos
https://forum.xda-developers.com/nexus-6p/general/guide-tutorial-nexus-6p-bootloop-death-t3716330
https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279
https://youtu.be/PhObuifEp3Y
I get error of adbwinapi...What can I do? (N5X)
Mehr_DaD said:
I get error of adbwinapi...What can I do? (N5X)
Click to expand...
Click to collapse
Hey! I've changed the post and the script a bit, so please follow the new steps and download the new script, but can you please explain more of what and when happened?
EDIT: I think I know what happened, but please try the steps above, and if they don't work tell me and I'll try and fix it
R3tro7 said:
Hey! I've changed the post and the script a bit, so please follow the new steps and download the new script, but can you please explain more of what and when happened?
EDIT: I think I know what happened, but please try the steps above, and if they don't work tell me and I'll try and fix it
Click to expand...
Click to collapse
Thanks, I did the new script and it's kinda getting too long on that boot (circle things) screen. I hope it gets to "android" thing in the end
So I flashed the March rom, It stuck on those circle things. Turned it off to cool down a bit and will power on in an hour. Let's see what happens next.
Yea, it did that for me too and then booted
Mehr_DaD said:
Thanks, I did the new script and it's kinda getting too long on that boot (circle things) screen. I hope it gets to "android" thing in the end
So I flashed the March rom, It stuck on those circle things. Turned it off to cool down a bit and will power on in an hour. Let's see what happens next.
Click to expand...
Click to collapse
For my 5x, it booted, but then I've tried to update, but it started bootlooping again, so I've flashed it again and again with no luck. Then I've turned the phone off for some time to cool down, and after that when I've powered it on it just magically worked, and is working since.
R3tro7 said:
For my 5x, it booted, but then I've tried to update, but it started bootlooping again, so I've flashed it again and again with no luck. Then I've turned the phone off for some time to cool down, and after that when I've powered it on it just magically worked, and is working since.
Click to expand...
Click to collapse
That's a good news! Mine just loaded to Homescreen and I don't want to mess with it this time, Turned on Wifi and it didn't restarted, inserted sim and didn't restarted. I hope it never freezes again. Thanks again. By the way did you flashed any recovery, kernel, BLOD "workaround" patch or just your fix script?
Update: Again, As soon as I login my Google account and went to Play Store to turn auto update thing off, the phone froze!
Mehr_DaD said:
That's a good news! Mine just loaded to Homescreen and I don't want to mess with it this time, Turned on Wifi and it didn't restarted, inserted sim and didn't restarted. I hope it never freezes again. Thanks again. By the way did you flashed any recovery, kernel, BLOD "workaround" patch or just your fix script?
Click to expand...
Click to collapse
I'm glad to hear! If you could please "Thank" the post, it will be much appreciated. For your question, I haven't used my script on my phone, I've just followed the steps in @squabbi 's video, and then I've decided to create an automated script (which is the script in this thread) to patch it automatically. Which basically means, yes, I have flashed a BLOD "workaround" patch.
Mehr_DaD said:
That's a good news! Mine just loaded to Homescreen and I don't want to mess with it this time, Turned on Wifi and it didn't restarted, inserted sim and didn't restarted. I hope it never freezes again. Thanks again. By the way did you flashed any recovery, kernel, BLOD "workaround" patch or just your fix script?
Update: Again, As soon as I login my Google account and went to Play Store to turn auto update thing off, the phone froze!
Click to expand...
Click to collapse
Still frozen?
R3tro7 said:
Still frozen?
Click to expand...
Click to collapse
Did system wipe from recovery and after some time (Cooling down process!) it boots again and this time I didn't entered my google account. However it freezes time to time even though I've only installed Telegram & Instagram. Is it ok?
Mehr_DaD said:
Did system wipe from recovery and after some time (Cooling down process!) it boots again and this time I didn't entered my google account. However it freezes time to time even though I've only installed Telegram & Instagram. Is it ok?
Click to expand...
Click to collapse
When you say freezes do you mean that it lags?
I guess that's ok, as you've disabled the cores, it should get slower. And please (I don't know if you've done that, but I'll still say) NEVER disable oem unlocking on this phone, because maybe it will happen again.
And by the way, I'm a newbie. I've just made a script that automates the patching process but I don't really understand that much about it. I would recommend you (and that's what I've done) to download the newest image, open the flash-all.bat file to flash it onto your phone (this will wipe everything, and install the newest version), power your phone on (it should start bootlooping again) once, and then do what you would do (boot to bootloader, run the script). Maybe the problem is that you've downloaded a wrong version of the boot.img (that means that you haven't downloaded your version, but the newest one. What I just said insures that you flash the right one). To check the right version, go to about > build number, and where you download your image, search for the exact build number. If the problems continue, maybe it's the script. I'll patch the files myself and send them to you. And if all of the above doesn't work, I will redirect you to @XCnathan32 or @squabbi, they will probably help you more.
R3tro7 said:
When you say freezes do you mean that it lags?
I guess that's ok, as you've disabled the cores, it should get slower. And please (I don't know if you've done that, but I'll still say) NEVER disable oem unlocking on this phone, because maybe it will happen again.
And by the way, I'm a newbie. I've just made a script that automates the patching process but I don't really understand that much about it. I would recommend you (and that's what I've done) to download the newest image, open the flash-all.bat file to flash it onto your phone (this will wipe everything, and install the newest version), power your phone on (it should start bootlooping again) once, and then do what you would do (boot to bootloader, run the script). Maybe the problem is that you've downloaded a wrong version of the boot.img (that means that you haven't downloaded your version, but the newest one. What I just said insures that you flash the right one). To check the right version, go to about > build number, and where you download your image, search for the exact build number. If the problems continue, maybe it's the script. I'll patch the files myself and send them to you. And if all of the above doesn't work, I will redirect you to @XCnathan32 or @squabbi, they will probably help you more.
Click to expand...
Click to collapse
No it just freezes for 3 to 5 seconds and then the phone restarts. But the boot image is also from march update...
Mehr_DaD said:
No it just freezes for 3 to 5 seconds and then the phone restarts. But the boot image is also from march update...
Click to expand...
Click to collapse
Please try to do what I've said
R3tro7 said:
Please try to do what I've said
Click to expand...
Click to collapse
Flashed the March ROM again. Used the script and it successfully installed. On the first boot it stuck on those 4 circles. Sounds like cooling down is the only answer. I can't use my phone constantly :/
Mehr_DaD said:
I get error of adbwinapi...What can I do? (N5X)
Click to expand...
Click to collapse
Same here, I get an error
After selecting that I am unlocked...
The pop up is fastboot.exe - syetem error
The code execution cannot proceed because AdbWinApi.dll was not found. Reinstalling the program may fix this problem.
It does pop up a second time after you click ok...
and then your script says it's done.. but it's not.
=====
I added the dll whicih can be found in the adb tools, I don't get the pop up but then your script says "waiting for any device" so there is something wrong somewhere as my phone is plugged in, and ready.
theBeachBoy said:
Same here, I get an error
After selecting that I am unlocked...
The pop up is fastboot.exe - syetem error
The code execution cannot proceed because AdbWinApi.dll was not found. Reinstalling the program may fix this problem.
It does pop up a second time after you click ok...
and then your script says it's done.. but it's not.
=====
I added the dll whicih can be found in the adb tools, I don't get the pop up but then your script says "waiting for any device" so there is something wrong somewhere as my phone is plugged in, and ready.
Click to expand...
Click to collapse
I fixed the AdbWinApi.dll error, download the script again and tell me what happens. Maybe the original fastboot.exe in my zip was a different version of the AdbWinApi.dll that you added and that's why it didn't work.
R3tro7 said:
I fixed the AdbWinApi.dll error, download the script again and tell me what happens. Maybe the original fastboot.exe in my zip was a different version of the AdbWinApi.dll that you added and that's why it didn't work.
Click to expand...
Click to collapse
the script worked.
Now should I flash TWRP 4 core recovery (edit seems so) and use the AK injector or not needed?
What is Elemental X?
p.s. Thanks!
theBeachBoy said:
the script worked.
Now should I flash TWRP 4 core recovery and use the AK injector or not needed?
p.s. Thanks!
Click to expand...
Click to collapse
I'm glad it worked. There is no need to flash TWRP and use the AK injector as you've already flashed a 4 core boot image. If you want, you can flash 4 core TWRP, but that's optional.
Last question hopefully.
I have tried sooo many things to fix this phone, unblod thing, flashing various files and the boot-safe.img, twrp 4 core, AK injector, factory image, in various order and multiple times. None of them worked, well unblod worked but no WiFi and when I fixed WiFi, BLOD restarted...
Is there a way the phone needs to be for the script to work? Factory image I guess?
Your script worked, but now at the Google logo stuck there. Not sure I should force reboot or wait. I't not in bootloop but doesn't move past the Google logo.
theBeachBoy said:
Last question hopefully.
I have tried sooo many things to fix this phone, unblod thing, flashing various files and the boot-safe.img, twrp 4 core, AK injector, factory image, in various order and multiple times. None of them worked, well unblod worked but no WiFi and when I fixed WiFi, BLOD restarted...
Is there a way the phone needs to be for the script to work? Factory image I guess?
Your script worked, but now at the Google logo stuck there. Not sure I should force reboot or wait. I't not in bootloop but doesn't move past the Google logo.
Click to expand...
Click to collapse
I did a quick search and some website said try resetting the phone. If that doesn't work, try to flash a factory image to make it bootloop again, and try the script. If all of that doesn't work I suggest asking @XCnathan32 or @squabbi because they probably understand it better than me.
Edit: My phone is miraculously recovered, see last post for details. Big thanks to everyone throwing in suggestions! :highfive::good:
Edit 2: Here we go again... Had my phone set up for a day and after installing the "App Systemizer" Magisk module, the restart upon booting is back. Please help, is magisk causing this??
So, I'm reaching out because I'm now at a loss. I have no other ideas as to how I could fix my phone.
Background:
A few days ago, I was setting my alarm for work in the morning and I noticed the UI was extremely sluggish. I then locked my phone with the lock button and a notification saying "Powering down..." came up and proceeded to shut off. At this point, I knew I should re-flash my ROM/boot.img first. Didn't help, every boot up ended in the same "Powering down..." message and shutting down within 15 seconds of unlocking the device. At this point, I think to fully wipe and revert to stock. Now, I try to install the latest stock OOS via fastboot. Same result as before when I booted after the fastboot install. And this is where it ended... I tried to use the MSM tool and the device went BLACK with no response after that.
What I've tried:
- fastboot
-MSM Tool
- randomly pressing/holding all physical buttons in every order
- leaving the device plugged in to charge overnight
Conclusion:
Any suggestions other than what I've tried would greatly be appreciated. If, by some chance, my phone is truly bricked... would anyone know about whether T-Mobile would replace the device for me if I act clueless as to what happened to my device? lol, I'm on the Jump! plan, so this phone isn't even paid off yet.
Thanks!
Only time I saw this "powering down" issue was when I updated my phone without disabling my Magisk modules. That time I just removed the module using TWRP and the phone booted.
When you used the MSM tool did it complete successfully? It should take around 5 minutes to restore. Mine took 302 seconds on the dot. That should clear out any and all software issues. If the problem still persists after a successful MSM restore then my thoughts would be hardware damage.
I assume your battery is still working (?), and you can't reach TWRP either?
Have you tried this https://www.getdroidtips.com/oneplus-6t-black-screen-death-issue/ ?
When my 6T didn't respond at all. It would stay black no matter what but I knew it was charged. All I did was hold volume up and the power button for a good 15 to 30 seconds. Then it booted up
Sent from my [device_name] using XDA-Developers Legacy app
Car Transport in mumbai
Car Transport In Mumbai[/URL]
Hey u...I also had the same issue...SHUTTING DOWN...in every boot....and I had fixed it....anyways if u have fixed it ...m glad....if not whatsapp or telegram me on +918898340211
Jager said:
Only time I saw this "powering down" issue was when I updated my phone without disabling my Magisk modules. That time I just removed the module using TWRP and the phone booted.
When you used the MSM tool did it complete successfully? It should take around 5 minutes to restore. Mine took 302 seconds on the dot. That should clear out any and all software issues. If the problem still persists after a successful MSM restore then my thoughts would be hardware damage.
Click to expand...
Click to collapse
MSM didn't even pick up my device... it said something along the lines of "No communication"
F5:ed said:
I assume your battery is still working (?), and you can't reach TWRP either?
Have you tried this https://www.getdroidtips.com/oneplus-6t-black-screen-death-issue/ ?
Click to expand...
Click to collapse
Thanks for the suggestion! Unfortunately, all steps were tried before seeing this post and didn't help.
i7vSa7vi7y said:
When my 6T didn't respond at all. It would stay black no matter what but I knew it was charged. All I did was hold volume up and the power button for a good 15 to 30 seconds. Then it booted up
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
This is important... but did not help me... initially.
sanjeev7 said:
Hey u...I also had the same issue...SHUTTING DOWN...in every boot....and I had fixed it....anyways if u have fixed it ...m glad....if not whatsapp or telegram me on +918898340211
Click to expand...
Click to collapse
Well boys, she's up and running again!
Here's what happened:
- I left my phone on the stock charger (wall-block and cord) to make sure the battery wasn't just dead. This resulted in nothing, still no response from the device.
- Early in the morning, while getting ready for work, I continued to press all physical buttons in any and every order as well as holding different combinations of the buttons. Nothing.
- Gave up, took it off the charger, and tossed the damned thing to the side. I took my iPhone X to work and hated every minute of it lmao.
- I then get off work and decide to mash the physical buttons in a half fit-of-rage and half last-ditch-effort.. and BOOM! The screen flashes with a screen saying the battery is dead in a few different languages.
(I never plugged a device in to charge so fast... lol)
At this point, I decided to fastboot the latest stock OOS (.13) to both A/B partitions and she's like brand new!!!! I spent the day rooting and reinstalling everything today and I'm honestly relieved. :victory: All of my data is lost... pics of my baby sister after just being born and of my fiance But order has been restored.
tl;dr - My phone is fixed, don't ever underestimate the power of button mashing! :good:
..Cory.. said:
MSM didn't even pick up my device... it said something along the lines of "No communication"
Click to expand...
Click to collapse
I suggest you re-read the thread on the MSM tool. It will always work unless there is physical damage to your device. The reason you got the "No communication" error is because you were not in the Qualcom bootloader mode or whatever, not fastboot and not TWRP, there is a third mode accessible by holding certain buttons while plugging in your phone to the computer, in this mode the screen does not light up or anything. Read the thread, the steps are in there. I guarantee that if you can get the MSM tool to restore your phone everything will be working on it.
I even tested the MSM tool once. I wiped all partitions on the phone including the boot partition. The MSM tool can always fix a Software issue.
Edit: Didn't see that you said it was fixed already. My message here is still valid though. Some day you will have to use the MSM tool so it's a good idea to get familiar with it.
Jager said:
I suggest you re-read the thread on the MSM tool. It will always work unless there is physical damage to your device. The reason you got the "No communication" error is because you were not in the Qualcom bootloader mode or whatever, not fastboot and not TWRP, there is a third mode accessible by holding certain buttons while plugging in your phone to the computer, in this mode the screen does not light up or anything. Read the thread, the steps are in there. I guarantee that if you can get the MSM tool to restore your phone everything will be working on it.
I even tested the MSM tool once. I wiped all partitions on the phone including the boot partition. The MSM tool can always fix a Software issue.
Edit: Didn't see that you said it was fixed already. My message here is still valid though. Some day you will have to use the MSM tool so it's a good idea to get familiar with it.
Click to expand...
Click to collapse
Well, like I said... I couldn't just change modes at will... I was legit stuck with the screen completely off and no response to any physical button being pressed. So as long as switching modes was impossible... so was the MSM tool. I read a F*CK-TON of threads before I posted this, I haven't seen anyone else post about being in my situation of not being able to boot into ANY kind of a mode... at all lol.
Bumping to ask for help again...
I had my phone all set up, stable OOS (.13) on both partitions. I installed the "App Systemizer" Magisk module in order to move an app to the system. When I rebooted after the module installation, the "Phone is rebooting..." message comes up after a few seconds post-boot and go straight to recovery every time.
I'm lost at this point. :/
You'd probably be better off seeking support in the mod thread.
..Cory.. said:
Bumping to ask for help again...
I had my phone all set up, stable OOS (.13) on both partitions. I installed the "App Systemizer" Magisk module in order to move an app to the system. When I rebooted after the module installation, the "Phone is rebooting..." message comes up after a few seconds post-boot and go straight to recovery every time.
I'm lost at this point. :/
Click to expand...
Click to collapse
Go to TWRP
go to file manager
Delete /data/adb/ *all files related to Magisk*
This will work
..Cory.. said:
Bumping to ask for help again...
I had my phone all set up, stable OOS (.13) on both partitions. I installed the "App Systemizer" Magisk module in order to move an app to the system. When I rebooted after the module installation, the "Phone is rebooting..." message comes up after a few seconds post-boot and go straight to recovery every time.
I'm lost at this point. :/
Click to expand...
Click to collapse
I have never read about a really bricked OP6T, there is always a solution (and use MsmDownloadTool if nothing else work....).
Now, when you already have "bricked" your phone once and fixed it, you are asking the community for help again... It's obvious to me that you are fiddling around with your device without any clue, and creates a mess for yourself. Why?
Stay outside what you do not understand, and stick to stock version only in the future.
To try to help you, I suggest you use MsmDownloadTool.
WOOOOOOOW.
So this whole time it was Magisk. I never knew about Magisk Manager for recovery. That thing is a MUST HAVE.
So what happened was the new Magisk update broke a few modules I use daily. After using MM to disable every module one-by-one, I found the culprit.
The thing that always gets me is the A/B partition BS. But I guess Magisk was really the pain in my ass!
Closing thread for good, thanks to everyone giving suggestions!!! :good:
Cablespider said:
You'd probably be better off seeking support in the mod thread.
Click to expand...
Click to collapse
Right, thank you! I just feel as if this section is less intrusive for noob questions haha
sanjeev7 said:
Go to TWRP
go to file manager
Delete /data/adb/ *all files related to Magisk*
This will work
Click to expand...
Click to collapse
Thank you! Used this to clean some of the files up when reinstalling the new stable update.
F5:ed said:
I have never read about a really bricked OP6T, there is always a solution (and use MsmDownloadTool if nothing else work....).
Now, when you already have "bricked" your phone once and fixed it, you are asking the community for help again... It's obvious to me that you are fiddling around with your device without any clue, and creates a mess for yourself. Why?
Stay outside what you do not understand, and stick to stock version only in the future.
To try to help you, I suggest you use MsmDownloadTool.
Click to expand...
Click to collapse
If you don't think I deserve help, move on to another thread! :good: No problems here though; I took advice I found helpful and I fixed my phone :victory:
I'm far from a noob though, this is just my first A/B parition device. I had an iPhone for years and was last active on XDA before Magisk was even released.We all need to brush up on the basics every once in a while, though!
..Cory.. said:
Right, thank you! I just feel as if this section is less intrusive for noob questions haha
Thank you! Used this to clean some of the files up when reinstalling the new stable update.
If you don't think I deserve help, move on to another thread! :good: No problems here though; I took advice I found helpful and I fixed my phone :victory:
I'm far from a noob though, this is just my first A/B parition device. I had an iPhone for years and was last active on XDA before Magisk was even released.We all need to brush up on the basics every once in a while, though!
Click to expand...
Click to collapse
Thank you for the arrogance.
I have already tried to help you (twice, in this your own thread). Your arrogant answer tells me that the iPhone-comfort zone suite you best.
In short: you act as an imbecile (since I have experience of you, and have "discussed" with you, before outside this thread).
So, sell your OP6t and buy an iPhone - problem solved.
F5:ed said:
Thank you for the arrogance.
I have already tried to help you (twice, in this your own thread). Your arrogant answer tells me that the iPhone-comfort zone suite you best.
In short: you act as an imbecile (since I have experience of you, and have "discussed" with you, before outside this thread).
So, sell your OP6t and buy an iPhone - problem solved.
Click to expand...
Click to collapse
That systemize tool is not very stable in my experience. There is two location's of system apps in my experience which is most always only about at least half correct a little less than half the time. Is that if you use something like MiXplorer and move the apk into either system apps or priv apps then reboot it is much easier to do than rely on scripts that may not be setup for the device you are using. It shouldn't take any longer than 25.89 seconds to manually move an app.
..Cory.. said:
WOOOOOOOW.
So this whole time it was Magisk. I never knew about Magisk Manager for recovery. That thing is a MUST HAVE.
So what happened was the new Magisk update broke a few modules I use daily. After using MM to disable every module one-by-one, I found the culprit.
The thing that always gets me is the A/B partition BS. But I guess Magisk was really the pain in my ass!
Closing thread for good, thanks to everyone giving suggestions!!! :good:
Click to expand...
Click to collapse
Download the magisk uninstaller zip , put it on your internal storage
So when magisk modules messing up with your boot
Go to twrp, flash the uninstaller zip , reboot to twrp, reflash magisk and then you're be able to boot again to your rom ..
F5:ed said:
Thank you for the arrogance.
I have already tried to help you (twice, in this your own thread). Your arrogant answer tells me that the iPhone-comfort zone suite you best.
In short: you act as an imbecile (since I have experience of you, and have "discussed" with you, before outside this thread).
So, sell your OP6t and buy an iPhone - problem solved.
Click to expand...
Click to collapse
Sorry, I forgot ur the internet law enforcement. Yes, sir! Please dont shoot! :HandsUp: :ShakingInFear: :Terrified: :NotReally: :WatchOut_InternetBadAss:
Jager said:
I suggest you re-read the thread on the MSM tool. It will always work unless there is physical damage to your device. The reason you got the "No communication" error is because you were not in the Qualcom bootloader mode or whatever, not fastboot and not TWRP, there is a third mode accessible by holding certain buttons while plugging in your phone to the computer, in this mode the screen does not light up or anything. Read the thread, the steps are in there. I guarantee that if you can get the MSM tool to restore your phone everything will be working on it.
I even tested the MSM tool once. I wiped all partitions on the phone including the boot partition. The MSM tool can always fix a Software issue.
Edit: Didn't see that you said it was fixed already. My message here is still valid though. Some day you will have to use the MSM tool so it's a good idea to get familiar with it.
Click to expand...
Click to collapse
The MSM Tool does not fix everything. The 6T I have is brand new was working fine until I installed LOS on A & B and deleted the persist partition. I have flashed the original stock rom as well as 3 other OOS roms. MSM Tool completes the flash no problem with no errors, but on every rom it only makes it to the boot screen and hangs. If the MSM Tool is supposed to fix this, then why isn't it getting fixed? I don't know what else to try to fix? Usually it fixes most problems for me, but on this occasion it is not.
So I just picked up a clean used International 6T. Was going through the root and update (I did the Android 10 update through Oxygen Updater) process and all that, things were going great, then out of nowhere they weren't and I had a complete black screen. I've literally been up all night trying to fix this thing, then again out of nowhere it actually boots, and I was able to use the MSM tool to restore it to that earlier version, then proceeded to get back up and running again.
Thought, phew, dodged a bullet. Nope, after getting rooted and TWRP installed, transferring a bunch of files over from my old SD card and restoring apps through Titanium (again, everything was going great again), and yet now all of a sudden I'm back where it all started earlier, stuck at the 'The boot loader is unlocked and ....' boot screen, it just hangs there, I can reboot into recovery just fine, but no operating system.
I'm literally about to pull my freaking hair out and try and sell this thing if it's going to keep doing this, I've never had a phone act like this one has (prior phone was a Nokia 8, headache). I have friends/family who haven't heard from me in a couple days now because I'm out of a phone and I need to get this thing working stable.
Can anyone help or shed some light on why this has happened again? I didn't update to 10, left it on the last stable Pie (begrudgingly), didn't flash any custom rom or anything, it was restoring most of the titanium apps just fine (some just hang there, not sure what that's about) and now I can't reboot into the os. To say the least I'm beyond pissed and annoyed at how much time I've lost on this thing.
Please please please help if you can, I'm not a newb to rooting (already rooted this one twice) but I don't know what to do at this point.
Thank you in advance, let me know what/if any info is needed.
Edit: I think I know/understand partially that magisk is to blame for this and reinstalling it fixes it, though I just did that through TWRP and it's still stuck on the boot screen.
Edit: Yup, right back where I was, device now shows as HS-USB QDloader..... in device manager. What gives? I have to use the MSM tool again? Why? Why is this happening...I've never had this much trouble with a phone
Try a clean install. Don't root and don't restore the titanium apps. Install them fresh. If your problem persists then it may just be hardware. But something you are restoring may be causing the crash due to the way it is trying to restore the app data.
I had similar problems. For me it was my self-created magisk module that ran without problems under Android 9. As it seems, there are also problems with modules from the magisk repo.Could be the case with you.
Clean install of the apps, after doing another MSM restore? And trust me, I won't be installing ANY other magisk files other than just the magisk.
Is there any way to save all the work I just did though without having to start over again via MSM? I'm guessing not....sigh
Grrrr...ok before the MSM tool worked, the phone was just unresponsive. It's back at that stage where the MSM tool times out and doesn't do a darn thing to save the phone.
I swear this thing is all over the place, now I'm in the bootloader, yay. I guess I'll try a wipe in TWRP and start over.
One thing I forgot to ask, is magisk the ONLY option available for root?
The question would be, how did you root.
TWRP is not working when you don't follow the instructions which involves OldKeysFlasher.zip.
Otherwise you have to flash Magisk with a patched boot image, be sure uyou have one for OOS 10 Stable.
The correct comands are here: https://forum.xda-developers.com/showpost.php?p=80638253&postcount=2853
jgro1976 said:
(...)
I'm literally about to pull my freaking hair out and try and sell this thing if it's going to keep doing this, I've never had a phone act like this one has (prior phone was a Nokia 8, headache). I have friends/family who haven't heard from me in a couple days now because I'm out of a phone and I need to get this thing working stable. (...)
Click to expand...
Click to collapse
I hope that anger is directed towards yourself because you can't hold the device or its manufacturer responsible when you get into the flashing game.
If you had done some reading, you'd know that TWRP doesn't play well with Android 10 and upgrading from 9 takes a very specific procedure. There's a dedicated thread for it even. Happy searching. You may also want to take a peek at my posting history for some pointers.
One more thing, are you absolutely sure it's an international device and not a converted T-Mobile version? Because that can cause a major amount of troubles.
Wrapped with delicious Fajita [emoji896]
I'm well aware it's my own doing, part of the frustration is having too many sources of information all claiming they fix a 'thing'. There's the "fix it with fastboot" camp who doesn't like MSM, and there's the MSM camp that helped me the first time. Phone is currently dead/black screen, going to try MSM again, and will check out the info you provided.
And I'm sure, double sim tray, does not flash a pink tmobile screen and/or no branding of any kind on the phone related to tmobile.
jgro1976 said:
And I'm sure, double sim tray, does not flash a pink tmobile screen and/or no branding of any kind on the phone related to tmobile.
Click to expand...
Click to collapse
Just remember that dual SIM trays are easy to get and if it's been converted from TMO to international version there will be no indicators till n you try to flash A10. Best bet would be to treat it as a converted TMO, if it is the info in recovering and flashing a TMO device will work and if it's truly an international version it will work too. Best of both worlds.
I'm 99% certain, by the label on the box, etc. Regardless, I'm to the point now that I can't even get it to boot to TWRP after 'fastboot flash boot twrp.img', it just does nothing and when I try to boot to recovery it bounces right back to bootloader. I've been trying all afternoon to fix it with no luck.
Was android 8/oreo good on these phones? That was my sweet spot and I'm just gonna downgrade if possible, there's too many things I don't like about 9 and 10.