So here's my story. I have a Moto X4 phone that I recently rooted and installed LineageOS 15.1 on from this page:
https://download.lineageos.org/payton
I followed the linked installation instructions and everything worked great for a couple days. This morning the 10/23 update came through and I went ahead and installed it. It seemed to take a long time and I had to go to work, but on my way to work I noticed it gave the prompt to reboot which I did. Once at work I found it was completely dead. No lights. Nothing when attempting to charge. Buttons don't do anything. Nothing. I tried plugging into my laptop at home tonight to try adb and nothing there either.
Any ideas on what could have happened to it? I'd think it'd at least light up or show some kind of intro screen. The only thing I can think of is that the thumbprint/pattern protection was on (my work requires it for email access) before installing the update. I know TWRP seems to have issues with this when booting into recovery.
After installing the LineageOS ROM, I also installed GAPPS and the arm64 LineageOS su add-on.
How easy is it to try disconnecting the reconnecting the battery? Or is that not worth a try at this point?
Thanks.
Hi!
Ota update is currently broken on this device. check link bellow for a fix:
https://forum.xda-developers.com/showpost.php?p=77905869&postcount=635
Hope it helps!
assmist said:
Hi!
Ota update is currently broken on this device. check link bellow for a fix:
https://forum.xda-developers.com/showpost.php?p=77905869&postcount=635
Hope it helps!
Click to expand...
Click to collapse
It did! Thanks! This is actually the post with blank flash zip file download that solved it for me. It booted right to the bootloader which I then selected recovery. It jumped to the LineageOS recovery screen. I then just chose to start LineageOS.
https://forum.xda-developers.com/showpost.php?p=76942904&postcount=30
Related
Hello,
I flashed a CustomROM and gapps, tried to reboot into system, but my phone does not react anymore since that attempt. The screen is black.
ROM: http://forum.xda-developers.com/mi-max/development/rom-cm13-unoficial-2016-06-14-universal-t3473016
Gapps: core package from 07-16-16 (arm)
Is there a way to recover it?
Tsd560ti said:
Hello,
I flashed a CustomROM and gapps, tried to reboot into system, but my phone does not react anymore since that attempt. The screen is black.
ROM: http://forum.xda-developers.com/mi-max/development/rom-cm13-unoficial-2016-06-14-universal-t3473016
Gapps: core package from 07-16-16 (arm)
Is there a way to recover it?
Click to expand...
Click to collapse
You have hydrogen or helium?
Which TWRP image did you install exactly?
My device is a Helium 64-3GB bought in China (June/16)
Recovery was flashed using Flasher Toolkit from "en.miui.com" -> /thread-301971-1-1.html
(Link not allowed)
file name: "twrp-3.0.2-2-hydrogen"
I remember that I might have seen Hydrogen in the text box during installation, if you aim on the detection during the installation.
Tsd560ti said:
My device is a Helium 64-3GB bought in China (June/16)
Recovery was flashed using Flasher Toolkit from "en.miui.com" -> /thread-301971-1-1.html
(Link not allowed)
file name: "twrp-3.0.2-2-hydrogen"
I remember that I might have seen Hydrogen in the text box during installation, if you aim on the detection during the installation.
Click to expand...
Click to collapse
Yeah... Wrong recovery and the install detected your helium as hydrogen leaving you a brick.
My bad... I just added the warning about that in the thread after seeing your question... Should of thought about this scenario but since we have helium twrp for a long time now I I assumed nobody is isuing hidrogen... I knew what you did just wanted to make sure.
Never been in a brick myself but read this thread and you should be back booting in no time
http://forum.xda-developers.com/mi-max/how-to/guide-install-global-miui8-root-t3435594
And install proper twrp, please... or you won't be able to install any helium rom.
The device gets recognized in MiFlash, but after flashing the twrp and the stock rom, the device still does not boot.
Any proposes on my mistake?
EDIT: I just started the procedure again, unplugged the battery, connected the "jumper" and the phone booted properly.
After some failed reboots, it randomly booted into TWRP (now the right one, at least i hope so. gonna check this later) and I installed the latest RR (love the design).
So now, its just the ugly 3G-bug left and a little OC would be nice
Tsd560ti said:
The device gets recognized in MiFlash, but after flashing the twrp and the stock rom, the device still does not boot.
Any proposes on my mistake?
EDIT: I just started the procedure again, unplugged the battery, connected the "jumper" and the phone booted properly.
After some failed reboots, it randomly booted into TWRP (now the right one, at least i hope so. gonna check this later) and I installed the latest RR (love the design).
So now, its just the ugly 3G-bug left and a little OC would be nice
Click to expand...
Click to collapse
Great job:good:
Not 100% sure of best place to post this, but I'm getting desperate now...
I'm pretty worried I've killed my device. After following the guide on how to root with Magisk, my phone is stuck on the white "loading" screen with a G logo. I've since tried to restart, but I can either go into fastboot mode or get the white screen when attempting to boot into android.
Tried to flash the latest factory image to fix it, but that couldn't get that to work. Now the phone isn't showing up on adb devices either. panicking a little bit here.
Does anyone know what to do?
ADB won't work unless the phone is booted into Android or in stock recovery for a sideload.
Does your computer recognize the device when you are in Fastboot mode and type "fastboot devices"? Try flashing the factory image again but make sure you have the most up to date platform tools from Google. Old versions are a common cause of issues.
Did you flash TWRP recovery or just boot to it to root? If you still have stock recovery you can try a factory reset from there but any modified images you installed might be the issue.
like Fury said, your platform tools need to be updated, same thing happened to me.
What didn't work when you flashed the factory image? Do you have the latest sdk tools version of fastboot and adb?
Sent from my [device_name] using XDA-Developers Legacy app
fury683 said:
ADB won't work unless the phone is booted into Android or in stock recovery for a sideload.
Does your computer recognize the device when you are in Fastboot mode and type "fastboot devices"? Try flashing the factory image again but make sure you have the most up to date platform tools from Google. Old versions are a common cause of issues.
Did you flash TWRP recovery or just boot to it to root? If you still have stock recovery you can try a factory reset from there but any modified images you installed might be the issue.
Click to expand...
Click to collapse
Thanks so much, this is where I was going wrong. Have gone into recovery and rescued it.
Tried the process again to get Magisk working, but ended up the same although this time the white screen only went on for a while before I got an error saying my data was corrupted. Tbh, after all the stress I'm just going to give up on this and live with the phone in stock. All my drivers and adb were installed and setup today, so everything is up to date.
edit...
Not out of the woods yet. After restarting the phone and going through the setup, it's not detecting the SIM card or any wifi networks. I've installed the OTA and wiped data once more after having this problem, still not resolved.
Nick676 said:
Thanks so much, this is where I was going wrong. Have gone into recovery and rescued it.
Tried the process again to get Magisk working, but ended up the same although this time the white screen only went on for a while before I got an error saying my data was corrupted. Tbh, after all the stress I'm just going to give up on this and live with the phone in stock. All my drivers and adb were installed and setup today, so everything is up to date.
Thanks again for helping.
Click to expand...
Click to collapse
It sounds like you are trying to install Magisk v17.1 like I tried. If so you need to use v17.3 beta. If you follow this thread you should be fine. It even tells you what to do for your original problem, just takes some reading and patience.
Misterxtc said:
It sounds like you are trying to install Magisk v17.1 like I tried. If so you need to use v17.3 beta. If you follow this thread you should be fine. It even tells you what to do for your original problem, just takes some reading and patience.
Click to expand...
Click to collapse
I tried it with both 17.1 and 17.3, so not sure what the issue is. Seem to have finally booted up properly with wifi and signal working, so hopefully it's all good now. Gonna give up on rooting.
Nick676 said:
Not 100% sure of best place to post this, but I'm getting desperate now...
I'm pretty worried I've killed my device. After following the guide on how to root with Magisk, my phone is stuck on the white "loading" screen with a G logo. I've since tried to restart, but I can either go into fastboot mode or get the white screen when attempting to boot into android.
Tried to flash the latest factory image to fix it, but that couldn't get that to work. Now the phone isn't showing up on adb devices either. panicking a little bit here.
Does anyone know what to do?
Click to expand...
Click to collapse
you may want to try to totally uninstalling Magisk frist with the official latest Magisk uninstaller and reboot and then do a complete factory reset. this has helped me in the past.
my new pixel 3XL will be the first Android phone that I owned that will not be rooted.
Hey all; first post and 100% green with rooting. This is my first attempt and i'm hitting a stumbling block.
First off, I've been using the guide on "theandroidsoul"(can't post a link due to post count, but a quick google search should bring you to the exact one)
I have successfully setup ADB, unlocked the bootloader, flashed TWRP 3.2.3-1 and have been able to boot into it using ADB.
However on step 10 of the guide i'm using, it's not too clear if i should skip formatting the device memory or go ahead and do it. I did it. I suspect this might be where i went wrong.
Regardless, i'm able to move Magisk onto the internal storage and TWRP is able to install it successfully.
Once i try to reboot, the "bootloader unlocked" warning screen shows, then the oneplus boot screen appears. It shuts down and reboots like this a second time, then the screen goes black and the front LED illuminates white and nothing happens. I can shut down the phone by holding the power button, then boot into fastboot manual using power + volume up. However if i try to boot the phone normally or boot into recovery mode, it repeats the same symptoms.
I'm unaware if I've soft or hard bricked the device. Like i mentioned i'm able to boot it into fastboot just fine and can get TWRP to come up with a boot command via ADB. But no matter how many times i try to install Magisk(I tried both v18 the guide mentions and the latest v19 from their site) i can't get it to boot.
I'm aware i also used an outdated version of TWRP(the one the guide mentions). i tried to flash twrp-3.3.0-1(latest version for dumpling) but cannot. I believe because a version of TWRP is already flashed on the device?
Can anyone help me out?
Hi all,
I'm facing the same issues as Josh and came seeking help, as well, so any help would be greatly appreciated! This is my first foray into Android coming from Windows 10 Mobile, which I'm still using two weeks after purchasing the 5T because of these issues. No matter what I do, I cannot get it to work and am now stuck in the same loop as mentioned above.
I'm attempting to install LineageOS and followed the instructions on its official site to a T, but have never been able to get it to boot into the OS. The only difference from the original poster's issue is that I'm not trying to root the device.
Thanks again for any help!
Josh Hex said:
....
I'm unaware if I've soft or hard bricked the device. Like i mentioned i'm able to boot it into fastboot just fine and can get TWRP to come up with a boot command via ADB.
....
i tried to flash twrp-3.3.0-1(latest version for dumpling) but cannot. I believe because a version of TWRP is already flashed on the device?
Can anyone help me out?
Click to expand...
Click to collapse
Hi, on my search how to flash TWRP revovery ROM I stumbled upon your post. With my first attempts, I did not even manage to get the official TWRP to run on my op5T - got always blue led - basically the same symptoms without trying to root. Meanwhile LOS works fine on my OP5T (I updated to the latest OOS then flashed and booted twrp-3.3.0-0-20190427-codeworkx-dumpling.img.).
ANYWAY my solution to unbrick and reinstall OxygenOS again was the...
... official unbrick tool - can be found in this forum when searching after (still cannot post links): OnePlus 5T Unbricking Tool
There is also another page here on the forum collecting different unbricking tools - although I am not aware how they are - since I used another source by googling for "How to Unbrick OnePlus 5T with OnePlus 5T Unbrick Tool (Unroot/Fix bootloop)".
Hope you get it running again, like I did.
Amix73 said:
Hi, on my search how to flash TWRP revovery ROM I stumbled upon your post. With my first attempts, I did not even manage to get the official TWRP to run on my op5T - got always blue led - basically the same symptoms without trying to root. Meanwhile LOS works fine on my OP5T (I updated to the latest OOS then flashed and booted twrp-3.3.0-0-20190427-codeworkx-dumpling.img.).
ANYWAY my solution to unbrick and reinstall OxygenOS again was the...
... official unbrick tool - can be found in this forum when searching after (still cannot post links): OnePlus 5T Unbricking Tool
There is also another page here on the forum collecting different unbricking tools - although I am not aware how they are - since I used another source by googling for "How to Unbrick OnePlus 5T with OnePlus 5T Unbrick Tool (Unroot/Fix bootloop)".
Hope you get it running again, like I did.
Click to expand...
Click to collapse
Thank you. I'll give it a shot and will let you guys know how it works out!
I need to install Lineage OS on this phone.
After multiple tries several months apart, I am still not in success.
Followed all internet tutorials and sites.
I don't want to install any G apps or any special root-things like magdisk..
I only want pure Lineage OS without any extra applications.
Way I tried and probably ended up like before:
Get newest official samsung ROM installed, update, enable usb debigging and oem, go download mode and go factory reset, get back in, sign in to wifi again, again enable develop. settings and usb debugging, go into download mode, take odin and install through the AP option the TWRP now that the phone is in download mode a 3rd time, supposed to be possible now with OEM unlock.
Most of the names on the way I don't understand, just follow tutorials.
I need to get to TWRP to then finally, as used to always, install Lineage from zip.
But I never get rebooted into TWRP recovery, just forver the samsung one, even when firmware is no longer there - after flashing in ap option the twrp tar again it never boots into TWRP afterwards.
Is there something else i must do? is not getting into oem unlock and flashing TWRP enough to get there?
And after, will the zip install finaly get me to have lineage installed?
Did you try the official guide?
https://wiki.lineageos.org/devices/beyond0lte/
I hope I picked the right phones, otherwise check devices overview.
Alternatively, perhaps this helps:
https://forum.xda-developers.com/t/...-a-graphical-installer-for-lineageos.4509995/
PS: Usually LOS doesn't do TWRP anymore but comes with its own recovery (a/b)
Why they don't do TWRP now?
I saw TWRP tuorial fot s10 on tutorials and it worked
Do I have to give up on TWRP way and od it with the adb commands from PC
frustrateduser118 said:
Why
Click to expand...
Click to collapse
It's because of this new double recovery scheme:
https://forum.xda-developers.com/t/help-understanding-a-b-partitions.3748003/post-75545902
https://source.android.com/docs/core/ota/ab
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
EOD: It's safer, updating happens in the background, then just a quick reboot et voila.
frustrateduser118 said:
I saw TWRP tuorial
Click to expand...
Click to collapse
Yes, it's still there but perhaps you post a link to your guide (or ask there). To me it seems you had TWRP just in your RAM but not your phone?
As for me, I finally gave up on TWRP and use the "crappy" LOS recovery Have way more important things to waste my time on...
PS: Sorry to bring such "bad" news, wasn't too happy with that change myself
Great, I finaly made it work.
I followed the site with turotial on installation and did not try TWRP
First I had to install samsung ROM again
It turned out to still stay unlocked so went straight to download mode and this time flashed Lineage recovery sucesfuly with heimdall
Then it booted up and a half samsung sreen made it seem like there is trouble
but Lineage recovery launched
The adb load from PC did not work so i chose to instal zip from SD even there
Now Lineage is installed
Still don't know how much is randomness, luck and so on
But it's done and hopefuly repeatable
frustrateduser118 said:
hopefuly repeatable
Click to expand...
Click to collapse
I am afraid it is
Well, most of times: Far too often I forget some little prerequisite, too... so started a little text file with steps/reminders.
anyway glad for support sigmund
you re my friend now
So previous to yesterday I had a fully working Galaxy S9 G960F, running the latest version of crDroid 11 (from 2021 heh), and something like TWRP 3.5.1? A fairly old version anyway, since I'd been running the same OS for the past year. I recently noticed someone had gotten 13 working on the S9, so I downloaded it and installed it like I'd done every other time installing a custom OS before, rebooted, and then the phone starts automatically going to recovery on boot, but gets stuck on the TWRP splash screen each time.
So I figured maybe the version of TWRP was too old for Android 13, and grab the latest (3.7.0), flash that with Odin, start the phone and I can at least get into recovery this time. So I try installing crDroid again. Same deal, just instantly boots straight back into recovery. So, figuring I'd best just go back to what I was using before, I reinstalled the previous crDroid 11 I had been using, and.. for some reason with that installed it only boots into Download mode unless I force it into Recovery. I try wiping everything and trying again, same deal. I even tried installing a different rom (Evolution X) and that just straight reboot looped.
If I go back to 3.5.1 TWRP it gets stuck on the splash screen btw. I am not sure what to do from here. Can I go back to stock and start over? Is there something else I should be doing? I've changed roms a bunch of times in the past and this is the first time 'just reinstall what worked before' hasn't worked, heh.
(For clarification, with crDroid 13: Phone turns on, shows Samsung Galaxy S9 boot screen, then goes straight into TWRP. With crDroid 11: Phone turns on, Galaxy S9 boot screen, straight into Downloading. With Evolution X: Phone turns on, Galaxy S9 boot screen, shut down and reboot. Buttons don't seem to be pressed in.)
DeiwosN said:
..... Can I go back to stock and start over? Is there something else I should be doing? I've changed roms a bunch of times in the past and this is the first time 'just reinstall what worked before' hasn't worked, heh.
....
Click to expand...
Click to collapse
Similar thing happened to me on a different Samsung device.
I did:
Used at that time SamFirm_Reborn_0.3.6.2 to get latest stock from samsung servers directly after inserting correct device designation and csc code.
Checked "binary nature" to get the full multiple part stock rom.
Flashed that with Odin.
Started from scratch.
Thank you so much! That fixed it.
DeiwosN said:
Thank you so much! That fixed it.
Click to expand...
Click to collapse
Glad I could help.
Perhaps useful for other users that you mark this thread as solved.