So I updated my rooted 6t to Android 10 using Magisk, and everything went as expected prior to rebooting. I hit uninstall and restored images via Magisk, downloaded and installed the Android 10 update package to the inactive slot, downloaded the TWRP A/B partition module then finally installed Magisk to the inactive slot as well. Finally, from there I rebooted and it seemed to boot normally, hung a bit longer on the animation than normal but no more than 30 second or so.. it then skipped the lock screen and went straight to my wallpaper (the same one i has set, not default) BUT the system doesn't start. No icons. Can't pull up the app drawer, can't pull down the notification menu. No notification bar... Nothing.
The only thing I can do is restart the phone by holding PWR button but that just brings me right back to the same deal. I tried fastboot>TWRP recovery and was able to determine that all the system data is in fact present anyway but rebooting from TWRP also lead to the same situation.
I'm asking for advice BC the last time I messed around without knowing fully what I was doing, I hard bricked it. I'm using Blu_Spark TWRP if that makes any difference at all...
It's possible that I just need to wait longer, I read a number of reports of pixel users needing to wait hours after OTA updates but they were stock on the boot logo/animation. I'm beyond that point, only it skips the lock screen, goes straight to my wallpaper and that's it. I can't do anything at all from there.
PLEASE HELP?
Thanks!
QNE
Use MSM tool.
Download MSM tool. Unzip it on PC desktop. ConnectUSB typC cable to PC. Shutdown your OnePlus 6. Open msm download too. Click start. Press volume up and dn key simultaneously(don't touch power button). Now connect cable to phone. Progress bar of MSM download too will be active. Let it completed. Phone will boot to os. Now upgrade to Android 10. That's it.
I ended up factory resetting prior to your response, but thanks just the same. Fortunately, I didn't lose root which was my main concern anyway so no harm done. Thanks again!
Related
Hey, so I have had my phone rooted for a long time. I have a Galaxy S5 6.0.1 Marshmallow.
I decided I wanted to get Framework installed so I downloaded the right files and flashed it in TWRP.
My phone took way longer than 10 min to reboot into system so I thought I was stuck in a bootloop and decided to run my phone through TWRP again.
I tried rebooting but that didn't work. I have my phone's backup saved onto a micro SD so I did a factory reset and then tried rebooting.
I got past the rebooting logo and actually got to my lock screen where it asks for my password.
From there, I've been getting spammed with 3 different messages, one saying that IMS service is down, com.sec.vsimservice is down, and WfcService is down.
After I press ok to all 3 of the messages, my phone is still in the lock screen asking for my password but the phone doesn't recognize that im touching the screen to type. After letting the phone stay like that for a few minutes, the lock screen that asks for my password goes away and all I can see is my wallpaper background (no notification panel either) but now the phone recognizes me touching the screen ( I know that because the LED lights up for the windows button and back button )
So basically I decided to go into TWRP and flash my recovery that I had saved on the microSD.
After that didn't work, I've just been going through a series of factory resetting my phone and wiping Dalvik files and then flashing my recovery. My phone is getting unrealistically hot too.
Btw I never downloaded the Exposed Uninstaller from the forum so I tried downloading it onto my pc and then sending the file over to my phone through download mode using Odin so that I could flash the uninstaller through my TWRP but that didn't work because the PDA in Odin does not recognize the uninstaller file.
Please, I really need help and thanks to anyone who tries, it would mean a lot if someone could figure out what I can do. Thanks.
Since you've tried restoring your backup and everything seems to have failed (it sucks, I know) you should try to install a completely stock firmware which you can download from here: http://live.samsung-updates.com/index.php?device=SM-G900I Just make sure you select your exact phone model from the dropdown menu at the top right side as you didn't mentioned which of the 40 S5s you have lol. And after you flash stock firmware and successfully boot up try to restore your backup. If it's still bugged - flash stock again and start off fresh. Let me know how it turns out. I'll help with installing xposed later as well, first let's get your phone running again
Hello, it is my first time trying to write a post on xda so excuse me if I do something wrong.
I've been playing with Roms a lot of time, installing, uninstalling, bricking and unbricking phones. so have a pretty good idea of how it works but now I just don't know what I did wrong and my phone is just ... in a black screen after boot image.
I was currently on DP5 android 9 by @joeyhuab and everything worked perfectly. Today was released android Pie and I just want to try it. So, I made the steps for DP5 to PR1 and everything runs well until I reboot from TWRP to the system. Now when I turn the phone on. it just appears the boot logo and later a black screen.
I can't restart the phone pressing the power button after some seconds but it goes to the boot image and later the black image screen (of the dead) appears.
1. I can't go to TWRP. (power+ Vol+)
2. I can't go to Fastboot. (power+ Vol-)
3. Charge Image is not displaying.
Windows sounds when i connected on the black screen state but fastboot don't.
This is my first time dealing with this kind of problem. I just don't know what would be the next step to try, Mi A1 is one of the best phones and I don't want to lose it.
Thank you for reading XDA, You are the best
hiddengoka said:
Hello, it is my first time trying to write a post on xda so excuse me if I do something wrong.
I've been playing with Roms a lot of time, installing, uninstalling, bricking and unbricking phones. so have a pretty good idea of how it works but now I just don't know what I did wrong and my phone is just ... in a black screen after boot image.
I was currently on DP5 android 9 by @joeyhuab and everything worked perfectly. Today was released android Pie and I just want to try it. So, I made the steps for DP5 to PR1 and everything runs well until I reboot from TWRP to the system. Now when I turn the phone on. it just appears the boot logo and later a black screen.
I can't restart the phone pressing the power button after some seconds but it goes to the boot image and later the black image screen (of the dead) appears.
1. I can't go to TWRP. (power+ Vol+)
2. I can't go to Fastboot. (power+ Vol-)
3. Charge Image is not displaying.
Windows sounds when i connected on the black screen state but fastboot don't.
This is my first time dealing with this kind of problem. I just don't know what would be the next step to try, Mi A1 is one of the best phones and I don't want to lose it.
Thank you for reading XDA, You are the best
Click to expand...
Click to collapse
Press vol+ vol- + power at the same time until phone vibrates
Sent from Mi A1 with Tapatalk Pro
hiddengoka said:
Hello, it is my first time trying to write a post on xda so excuse me if I do something wrong.
I've been playing with Roms a lot of time, installing, uninstalling, bricking and unbricking phones. so have a pretty good idea of how it works but now I just don't know what I did wrong and my phone is just ... in a black screen after boot image.
I was currently on DP5 android 9 by @joeyhuab and everything worked perfectly. Today was released android Pie and I just want to try it. So, I made the steps for DP5 to PR1 and everything runs well until I reboot from TWRP to the system. Now when I turn the phone on. it just appears the boot logo and later a black screen.
I can't restart the phone pressing the power button after some seconds but it goes to the boot image and later the black image screen (of the dead) appears.
1. I can't go to TWRP. (power+ Vol+)
2. I can't go to Fastboot. (power+ Vol-)
3. Charge Image is not displaying.
Windows sounds when i connected on the black screen state but fastboot don't.
This is my first time dealing with this kind of problem. I just don't know what would be the next step to try, Mi A1 is one of the best phones and I don't want to lose it.
Thank you for reading XDA, You are the best
Click to expand...
Click to collapse
I also had this issue I think it is because of any xposed modules or magisk modules.
When I flashed xposed uninstaller, the phone revived
hiddengoka said:
Hello, it is my first time trying to write a post on xda so excuse me if I do something wrong.
I've been playing with Roms a lot of time, installing, uninstalling, bricking and unbricking phones. so have a pretty good idea of how it works but now I just don't know what I did wrong and my phone is just ... in a black screen after boot image.
I was currently on DP5 android 9 by @joeyhuab and everything worked perfectly. Today was released android Pie and I just want to try it. So, I made the steps for DP5 to PR1 and everything runs well until I reboot from TWRP to the system. Now when I turn the phone on. it just appears the boot logo and later a black screen.
I can't restart the phone pressing the power button after some seconds but it goes to the boot image and later the black image screen (of the dead) appears.
1. I can't go to TWRP. (power+ Vol+)
2. I can't go to Fastboot. (power+ Vol-)
3. Charge Image is not displaying.
Windows sounds when i connected on the black screen state but fastboot don't.
This is my first time dealing with this kind of problem. I just don't know what would be the next step to try, Mi A1 is one of the best phones and I don't want to lose it.
Thank you for reading XDA, You are the best
Click to expand...
Click to collapse
I have the same problem, my Mi A1 dont boot and i cant open fastboot mode (and screen dont turn on when charging), how you solved it?
Stuck on black screen
i was on aex 6.1 flashed this build and stuck on black screen.and i am unable to go to twrp .. steps i used to flash this
-->clean wipe(system,dalvik,data)
-->flashed aex6.2
-->flashed twrp installer
-->reboot to recovery
but it didnt reboot to recovery.
i think it boots but it shows only black screen as when i am taking screenshots its making sound.
ideepeshtiwari said:
i was on aex 6.1 flashed this build and stuck on black screen.and i am unable to go to twrp .. steps i used to flash this
-->clean wipe(system,dalvik,data)
-->flashed aex6.2
-->flashed twrp installer
-->reboot to recovery
but it didnt reboot to recovery.
i think it boots but it shows only black screen as when i am taking screenshots its making sound.
Click to expand...
Click to collapse
im also having the same issue. while flashing aex v6.2 on my mi a1
help me out from the same problem
This morning i have flashed havoc 2.0 after that flashed TWRP recovery and then i reboot to recovery mobile gets rebooted and after the boot page the screen went black. I have rebooted the mobile so many times same issue facing i am receiving calls means mobile is ringing but i cant see anything on screen. Plz help me out
khadar709 said:
This morning i have flashed havoc 2.0 after that flashed TWRP recovery and then i reboot to recovery mobile gets rebooted and after the boot page the screen went black. I have rebooted the mobile so many times same issue facing i am receiving calls means mobile is ringing but i cant see anything on screen. Plz help me out
Click to expand...
Click to collapse
Flash the previous rom and everything will be back to normal.
Shilldas said:
Flash the previous rom and everything will be back to normal.
Click to expand...
Click to collapse
I am not able to do that I can't go to twrp mode here also same black black screen.I can go to fastboot mode but I am not enabled usb debugging mode and system is not recognising mobile.
Help me how can I solve this..
Thanks in advance. ?
Install 'scrcpy' in your PC. Try to flash twrp from PC using fastboot and adb method. (I hope fastboot shows up on your phone) if u can boot to twrp via PC then go ahead and install any other rom. If u can't then connect your phone to PC and open scrcpy.exe here you can control your screen. (Most custom roms come with usb debugging enabled, if not try " AEX V.6.1 rom)
Usb debugging is compulsory. Thanks a lot for the information I will try this.
So i had this exact same issue. It was booting to twrp but screen was just blank.
i was trying to root the devive so i flashed the zip file by following command through adb
adb shell twrp install /sdcard/Magisk-v23.0.zip
it flashed the magisk and it was done. Similarly you can flash any zip file. If zip file is not copied to internal memory you can copy it using following command
adb push Magisk-v23.0.zip /sdcard/
I hope it helps someone in need.
Thanks.
Hi similar problem. Phone was locked in bootloop. I use reset pin and flash latest fw, flash successful in 220sec. Then screen stays black. Holding any combination will power up phone with black screen... wonder if it burn resistor or it is a flash issue. Trying to reflash again, however it stays 1000sec and still flashing.
Hi have mine FIXED.
Tried again to flash with android 9. Not able to finish flash in 4hrs. Then disconnect. Screen show battery 100%, then again only black screen but powered. Also 3 buttons are lighting. So I start pushing them and the screen, got some feedback and sound from touching the screen. Then the phone restart, screen ON. Show the normal white screen and ENCRYPTING storage screen that should come after flash. Then again reboot itself and start installing android (just taking a lot of time). Now all work on android 9, not giving option for OEM update to android 10, however afraid to flash again... good enough for my son (either way will break it in an year).
p.s
Im Samsung S class user for 10 years, so it is quite unfriendly phone... (need debugging on to connect to PC, for file transfer )
At last I found a way to run TWRP on tissot correctly without black screen.
Just install oreo 3.2.1-2 on Mi A1 (tissot).
This file (recovery-3.2.1-2-oreo.img) is working well.
Download it from this site:
https://androidfilehost.com/?fid=818070582850498337
Reference:
https://forum.xda-developers.com/t/...2-1-2-oreo-touch-recovery-2018-03-06.3688472/
Download Android 13.00 unofficial ROM for Mi A1 and install it easily by TWRP oreo 3.2.1-2:
https://sourceforge.net/projects/lafactorial-tissot/files/
Good luck,
Sed
Releases · zignas/twrp_device_xiaomi_tissot_treble
android 9.0 Device tree for TWRP 3.5.2 with Tissot manager - zignas/twrp_device_xiaomi_tissot_treble
github.com
also working fiine
Not sure I am posting in the right spot, but pretty sure the people that can answer are in this section.
After putting it off for months, I upgraded my 6T T Mobile converted to international to OOS 10.3.3 with the ElemetalX kernel, and xxxNoLimits 10.2. Did this several days ago, no problems. Great battery, smooth performance. Even getting 2 days with my VPN on and mock location set to "always".
I went into app ops and noticed almost every app now has "access location from media" and started going through and denying that permission for almost, if not all, the apps. I remember a couple of system apps I did that to. Google play framework being one of them, and, I think, google play services. There may have been 1 or 2 more system apps I did this with also.
I do not have a google account on my phone. I don't want to make it any easier for my pocket tracking device to track me than I have to.
I added an open source mock location app a day or so ago, not problems.
About 5 or so minutes after finishing up in app opps, I went to get the kiddo some food and looked down and noticed my phone rebooting. Now, it is in an endless boot loop.
I can hold power + up volume and get it to power down, but can't get back into TWRP recovery. Figured a quick reflash puts me back to zero and I can start over.....more carefully....but the phone is not cooperating.
I should be able to use adb and flash TWRP that way and use adb to reboot to recovery ( going to have to brush up on the how to before I start though.).
Any thoughts as to WHAT I have done and WHY I am now stuck on endless boot( w XXX animation )??
Is there an easy fix I am overlooking?
Thanks in advance,
JC
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool
Can you get into fastboot? Then you might be able to boot TWRP again temporarily?
Thanks, that gets my into TWRP, unfortunately, my dumb ass deleted the last OTA update after I flashed it. Should be able to side load it onto the phone, then flash it via TWRP.
Well, things just took a turn for the worse. I forgot to flash twrp after sideloading the os. Now it is keeps booting into Oneplus recovery. Still shows bootloader is unlocked though. I have done everything except a total wipe. Maybe I can still get TWRP back........
PattayaGlock said:
Well, things just took a turn for the worse. I forgot to flash twrp after sideloading the os. Now it is keeps booting into Oneplus recovery. Still shows bootloader is unlocked though. I have done everything except a total wipe. Maybe I can still get TWRP back........
Click to expand...
Click to collapse
Flash twrp recovery via adb commands, you'll find tutorials on several XDA forums or YouTube
I saw it pop up on the stable channel. I waited a few days, checked here and saw nobody complaining so I went for it. Recovery saved it, so no big deal, but still killed about 20 min. 20.4 has been working fine for me.
similar result, updated and just made the phone crash at boot; restored and I guess no more updating for the meanwhile
21.3 still has the same crash.
tdusen said:
21.3 still has the same crash.
Click to expand...
Click to collapse
I confirm - crashed on boot. But I am not sure that the reason is Magisk itself, may be the Magisk Manager is the reason ....
21.0 works all after do not.
Bricked my V20 VS995 this morning trying to update to 21.4. Notification had been nagging me for a week and I finally gave in, now my device has a gray screen with very small text, and at the top it says "LGE Crash Handler: Crash on the LK!". I cannot get into TWRP, and a factory reset has no effect. Still no boot into Android.
I was just talking to my girlfriend yesterday about how it was getting time to upgrade. Careful what you wish for, I guess.
that's why I finally turned off the update notification.
Have you tried booting into recovery by the holding keys method?
Assuming you have TWRP installed
hold vol down and power.
when the LG appears, release power the press and release power (one time) while still holding vol down.
you boot to the factory reset screen. select Yes twice
that will boot into twrp
Same here, updated Magisk and bricked my V20 H910.
Then I've used TWRP to try to queue install the following zip :
1 - H910_20h_Oreo_full_rooted
2 - H910_v2.2-mk2000
3 - Magisk-v19.3
4 - Hide_warning-att
Back to Oreo setup, all good even if datas are lost. Then again I've updated Magisk (was not really sure it was because of that, should have read here first!) and same problem, the unfamous "Crash on the LK!". Magisk killed my phone, again.
So I was ready for another run (but the magisk update of course). Stupid me.
I know can't even acess the recovery tool, ok for the Down/Power then Power to get the first recovery prompt and then the confirmation but no TWRP but the crashed multi-colored messy pixel screen and boot again to Crash LK screen.
I have no clue of how to get out of here, guys any help is more than welcome!
Anyone install 23 yet?
I don't see 23 on the Beta channel, nor on the stable channel.
I have 22.0 installed and running fine.
Does anyone have 22.1 installed? Is it fine?
i had an app update waiting for me 23 installed fine on note 3 and on my v20
Ok, so... this is gonna be quite long to tell, but I need to explain the situation as carefully as possible because the problem I have seems to be very specific and potentially solutionless.
So, a week ago my Samung Galaxy Tab S6 Lite (SM-P610, CSC: ITV, which is the Italian Country Code and it's for unbranded devices, since my model is Wi-Fi only), suddenly started to restart itself and it's been stuck for days in a bootloop (i.e. it's stuck on the logo and if I hard restart it with Volume Down + Power, it gets stuck there again). Yesterday I found out that it's most likely a software problem, so re-installing the Android version should fix everything up... right? Well, I did just that but the device is still stuck on the bootloop.
Here I want to be more detailed: firstly, I'm 100% positive that the problem I have is NOT due to a virus, as I've never done ANYTHING that could potentially lead me to taking a virus (such as downloading apps outisde Google Play, visiting risky sites etc.); secondly, I followed a procedure that was supposed to repair my device without losing data. That's because I've stupidly never made a backup and I can't afford to make a factory reset. The procedure I followed consisted in finding the Android update I needed with Frija, and then downloading everything in the tablet with Odin. Also, I'm 100% positive that I made NO mistakes during the installation procedure. The only step that I did differently is HOW I installed the update: I did it with Download Mode, not with fastboot, because when I go into Recovery Mode and reboot the device into bootloader, the PC doesn't recognize my Tab, even if the PC does recognize that it's connected, as it makes the typical sound of when you plug something in a USB port (I have the USB drivers installed in my PC, I think it doesn't work because I never unlocked bootloader). What I get when I reboot into bootloader is "entering fastboot..." stuck screen and the PC and Odin aren't able to recognize it.
My questions are therefore these:
Is there a way to make a backup of the data of my device if I can't boot it (maybe via Download Mode)?
Is there a way to make fastboot work if I can't boot my device?
Is there some other way to repair my tablet that I can try?
Thank you for any help, this is my last hope to find a solution for my problem.
neo4458232 said:
When your device is stuck on an Android boot loop issue then you can fix it by simply doing a soft reset. Turn off your device and the problem will be resolved.
Here are the steps to follow:
First, switch off your device and take out your battery from the phone.
If your battery is non-removable then turn off the phone for 3 to 5 minutes and again turn it on.
This method works effectively to fix the error of the boot loop issue. But if a soft reset does not work for you to fix Android phones stuck in the boot loop issue then you should follow the next method.
Method 3: Reboot System in Recovery ModeRebooting a phone in the Recovery Mode is known for fixing several errors and issues on your Android phone. So, if you are unable to start your phone in normal mode or your Android is stuck in a reboot loop, then restart your phone in Recovery Mode.
Method 4: Remove and Reinsert SD CardYou may also try to remove the SD card to fix the boot loop in Android. According to several user reports, this trick worked for them. So, you should try this.
First, turn off your phone > remove the SD card > turn on your phone normally, and check if your phone is out from the boot loop or not.
If it is still stuck in the boot loop, then go for the other solution.
Method 5: Reboot the Phone in Safe ModeThis problem may also occur due to problematic 3rd party apps. If you have recently installed an app on your phone and then you started facing this issue, then remove it from your device.
Or, if you are not sure which app is responsible, then try rebooting your phone in safe mode. Doing this will disable all the third-party apps on your Android phone and then you can easily find out if this is the reason behind this issue or not.
To do this, you need to follow these steps:
Start rebooting your phone.
When the device logo appears on the screen, long-press the volume-down button at the same time.
Now, your phone will automatically switch to Safe mode.
If your phone is no more getting into the boot loop, then it means one of the third-party apps installed on the device was causing this issue.
Now, find out the problematic app and uninstall it to fix the Android boot loop without losing data.
Method 6: Use Custom Recovery ModeWhen you find your Android is stuck on the startup screen due to the boot loop issue, then you must try to restart the phone in the Custom Recovery mode. Here is the guide to do so:
To enter into the Custom Recovery mode press the Power + Volume down buttons simultaneously.
Select the “Advanced” option in the Custom Recovery menu.
Next, choose “Wipe Dalvik Cache”. Choose “Yes” when prompted for confirmation.
Move to the “Mounts and Storage” option and choose “format/cache”. It will clear the cache files completely.
Restart your device.
Method 7: Fix Android Bootloop Error Via CWM Recovery [For Rooted Phone]Maybe you are not aware of this method but it’s a useful way to fix the boot loop issue on Android after the update. Remember that this method is only for rooted phones. Here CWM means ClockworkMod and if your phone is stuck on the Android boot loop then it must be downloaded and installed on phone. Read me
Click to expand...
Click to collapse
Thanks for replying but I already tried every method listed here.
At this point it sounds like you need to bring it in to a local repair shop & see if they have a fix.
The solution is to wait on the turned on screen until the battery dies completely. Then put it to charge and after a bit using the reset combo (pwr+volume down) once the circular battery charging indicator with the green border comes. (It's a matter of luck, this keeps happening to my tablet and even the official samsung store can't fix it even though they took money to do the same)