Hello all before I describe my issue lemme tell you how I got there.
First of all, new phone, couldn't install pixelexperience and flashing stock android was being a pain with all methods (read not working), only managed to install stock android with pitch black recovery.
After a while it auto updated to android 9 and I started having wifi issues that people told me were android's fault so I waited for an update. Update came but android was unable to install it, giving errors after errors every time it downloaded the update.
My solution to all of this was to flash another rom, either stock or custom, and pray it works. It was scheduled to happen in 2 days, when I had free time.
Today, when trying to change the permission for a text file for an app from read only to write, some random process crashed, and it triggered a crashing cascade, including the settings app, homescreen launcher, etc until the phone restarted and got stuck in TWRP logo screen.
No key press, combination, resets, etc would fix it. So I got into fastboot and tried a few things with no luck. Flash stock rom again and phone seemed to be working.
Magisk manager couldn't install magisk and root the phone so I went into stock recovery/twrp and every time I did it I got a black screen message saying something like this:
"Your phone/system is corrupt and won't boot ever again *evil laugh*. Oh btw, go to this link in another device to cry more"
and the link redirects to a google page with some non-useful info.
So here I am, unable to root, unable to go into recovery, phone boots though. I force-stoped updates for a while, as android 9 wifi issues were terrible, and I don't know how to proceed.
Do I flash a stock image again, a custom one, try another rooting method?
I don't want to brick a 6month old phone, really sucks.
Btw, is there a reliable way to back up everything in the phone ?(not only google stuff, but app configs and files/folders) Long time ago I read something about Titanium backup but never looked into it further and now with this crash that lost me everything I wanna prepare for the future.
Thanks for all the help and for reading my boring story.
Even I am facing same problem.. In my case my phone is rooted and I cnt flash TWRP and I cnt get into fastboot mode.. I alwys endup with black screen..
Related
Im sure ill get flamed but i have searched and couldnt find an answer.
I have a z2 odexed stock with root. Just updated new firmware via pc companion to 17.1.2.a.0.314.
i downloaded the xposed installer and that went well. Then downloaded the serajrs xposed module so i can get different themes to work, extended power menu etc. everything seemed to install fine however now after rebooting i get this error.
it boots up but stays on the home screen and i can do is keep hitting ok to acknowledge the problem but i cant do anything else.
It was the stock rom so i dont have any custom recovery to go into to restore a nandroid or flash another rom (which i didnt want to do).
All i have is my titanium backup but i cant get past the error, any help would be greatly appreciated
* the error appeared about every 2 seconds so each time i hit ok, i was able to go 1 step each time. Basically was able to get into settings and do a factory reset which managed to do the trick. restored via TB so minimal setup time again. Would still like to know where i went wrong though but grateful didnt brick it lol (yes i can laugh about it now)
For next time: check the FAQ and stuck threads for info on how to temporarily disable Xposed (with or without a recovery).
The FC was likely caused by a module, so you should ask in the module's thread instead.
EDIT: Wish I could delete this. Just found a post about how to fix this...but it involves opening the phone and messing with the hardware. Wish someone could walk me through it :s
So, I hope I didn't, but here is the scenario:
Wanted to install Lollipop ROM from KitKat...tried, failed, found out I needed to have a downgraded radio. Okay...use LG Flash Tool to give myself another try. Load up Jellybean...couldn't figure out how to flash custom recovery in Jellybean as all tutorials are outdated or just didn't work when I tried them, so I thought the best way to do it was to get the Kitkat OTA from Verizon and let it install, then flash a custom recovery (since I figured out how to do that with Kitkat...Autorec), then flash the old radio then the Lollipop ROM and voilà. However, when waiting for the download for Verizon OTA, I tried again to install a custom recovery, and when tried to load it, I just got a black screen. So I just decided to go back into the Android OS and install the OTA once it finished downloading...
The OTA finished downloading and I clicked install, my phone then rebooted...and stupid me didn't even realise what I have just done. The OTA tried going to recovery mode to install...but there's nothing there. Now I am stuck at a black screen that is trying to start recovery mode and when trying to reboot and get into download mode, it won't let me and just goes to the broken recovery mode.
So...can't really think of any other options for me. What can I do? When I plug it into my computer, it connects my phone as like 20 different drive letters that all say they need to be formatted.
So my question is...what can I do?
I have a Moto G XT1072. I had unlocked the bootloader, installed TWRP and rooted it a while ago. I did not install any custom rom.
I was completely unaware of TWRP's lack of support for OTA upgrades, so when my phone notified me that there was an update available, I was like "oh, cool, okay" and downloaded it.
a) The download finished, the phone rebooted and TWRP recovery popped up.
b)"Mh, I guess I have to find the update file and flash it, probably"
c) Of course I didn't find it, so I googled and found out that if I want to install an OTA update I have to flash back the stock recovery and I might lose root. "Not worth it, thanks, maybe when 6.0 comes out"
d) So I rebooted the phone. Boot screen with motorola logo shows up, phone boots normally, I insert my sim card pin, set the alarm for tomorrow morning (6:00 am, fml) and *poof*, phone shuts down and reboots in TWRP.
e) back to point d.
Recap: I downloaded the update but I didn't install it, phone boots normally (I can even go in settings), but after 30 seconds it shuts down and reboots in TWRP. I do not care about the update, I just hope I can avoid re-rooting or even wiping.
I've got the exact same problem as you. Stupid to not have thought this could've happened with TWRP installed. Additional problem is, I have removed everything ''root-related'' (adb, fastboot), because I thought I wouldn't need it anymore. TWRP is obviously still on my mobile, but that's about it. I have already made a backup in TWRP (don't think it will help, because I'm afraid it will backup as boot trap), but who knows if it may help.
Back to the point, I'm a noob with rooting, I don't even know how I've managed to root it in the first place, but I'm stuck with the same problem as you are but without the required tools (at least, that's what I think)...
UPDATE: So my phone finished the backup, I turned it off to charge my battery, I fired it back up after an hour (normal way, not TWRP way), and it all of the sudden works again. It doesn't boot trap anymore and it seems like I'm able to use every function properly again. After those 30 seconds (where it usually rebooted), I now got the message that the installation had failed and that I should try again later. I don't know if there's any logical explanation for this or if this is pure luck, but I'm glad it's working again! I don't know if this will help for you as well ricvail, but I think it's at least worth a shot!
Hi Guys,
I recently flashed to OOS 4.0.1, I wiped the phone with fastboot -w and followed instructions on here to flash the full ROM file, anyway so that went fine, by the end of that I had a functional, rooted phone on OOS 4.0.1,
But then I went to download Snapchat, everytime I tried to log in, it says it had temporarily failed, so I went through some troubleshooting steps and decided to wipe my phone, re install OOS 4.0.1 without root, and try again, that has worked, my friend said he had the same issue and that he had to root after installing and logging into Snapchat, so I have gone to root again, sideloaded fine in TWRP recovery like i have done in the past, but now my phone is stuck on the OnePlus logo where you have the red dot with two spinning white dots going round, been like this for 10 minutes now, I know the boot can take longer but it has never taken this long, I've got it plugged and will just wait for an answer as this is doing my head in!!
Cheers guys,
Daggerzz said:
Hi Guys,
I recently flashed to OOS 4.0.1, I wiped the phone with fastboot -w and followed instructions on here to flash the full ROM file, anyway so that went fine, by the end of that I had a functional, rooted phone on OOS 4.0.1,
But then I went to download Snapchat, everytime I tried to log in, it says it had temporarily failed, so I went through some troubleshooting steps and decided to wipe my phone, re install OOS 4.0.1 without root, and try again, that has worked, my friend said he had the same issue and that he had to root after installing and logging into Snapchat, so I have gone to root again, sideloaded fine in TWRP recovery like i have done in the past, but now my phone is stuck on the OnePlus logo where you have the red dot with two spinning white dots going round, been like this for 10 minutes now, I know the boot can take longer but it has never taken this long, I've got it plugged and will just wait for an answer as this is doing my head in!!
Cheers guys,
Click to expand...
Click to collapse
I've run into the same problem, how did you end up fixing it?
This is odd? My suggestion would be to just flash stock 4.0.1 again or w/e it is and then install Magisk from the app store and install the root from there. That should do the trick .
i'm in desperate need for guide please,
so i first off i had some questions (excuse my stupidity but i really couldn't find any answers around)
1) can an never-rooted android device's build number change or is it always the same? like with stock/official updates only?
2) my recovery mode (stock/system recovery) aborts every single installation file (official rom from the Asus website) without even opening the package, it's like i press 'install update from sd card' then as i press the zip file, it immediately says 'installation aborted' without even typing any other significations/steps, and the same happened for the kernals zip files too. so does that mean my recovery mode is corrupted or something is wrong with it?
3) i noticed some slight changes in my recovery since the last bootloop i had and had to use it back then, for example the dead android screen appearing after choosing the recovery mode, at first it used to say 'no command' under the dead android, but this time it doesn't say anything, just the dead android image only until i press power button and volume up to get the recovery options. so does that mean my firmware version changes since last time or my recovery is corrupted or it just means nothing?
4) is there aNYWAY to know my build number of a phone in bootloop (not rooted but bootloader unlocked)
so my initial problem is; i had my asus zenfone go zc500tg on march 2016. it was working so fine actually (using it like a default user not actually knowing anything about roms/flashing/recovery etc) until july of 2017 when i noticed my phone was a bit slow (out of the ordinary) and it used to get SO hot while using it normally and battery drained pretty faster than before, but i didn't know what to do tbh so i just kind of ignored something was off. but not long after these symptoms, the booting of my phone got slower and slower, until it reached its max by staying more than three hours just doing the 'optimizing apps' on the booting screen until it booted, so i thought it was a virus that would go away after a factory reset, and after the reset, it got worse, until it stopped booting and got into a bootloop. I panicked then because i didn't have the slightest idea what was happening until some internet searching guided me into the world of bootloops and custom roms and recovery. so i eventually managed to fix the bootloop and it worked fine for several months until it started to lag again and boot slowly and got the second bootloop, and that i fixed like the first one by installing the rom from the asus website then putting it on the sd card sand flashing it through recovery,
the third bootloop was quite the same, except that i did something additional in recovery mode, i pressed "backup user data" and that did a nandroid backup then i restored it smoothly after flashing the rom.
the fourth bootloop was a bit different, i as always downloaded the same firmware as the times before and flashed it and backed up user data too, but the odd thing that happened was me getting a message box that won't go away that said "unfortunately, the process com.android.phone has stopped" the phone worked but the sim cards weren't recognized and the message box was coming and going every second, so i noticed that the message box went away (nearly) when i got my sd card out, but still the phone app and the sim cards were corrupted,i thought the issue was from my sd card at first but i eventually, (coincidentally tbh) managed to fix it by doing the OTA update that was due, (that bootloop was fixed on the date of January 13th 2018)
then my phone was working so fine and everything was alright.
then shortly after (january 20th 2018) i was on whatsapp normally then suddenly ALL the things on my phone came crashing in front of me : TONS of endless message boxes saying things like "unfortunately, the process com.(any app on my phone) has stopped"
that i literally panicked and tears welled up in my eyes, so i rebooted the phone and while rebooting it did a (relatively quick) "optimizing apps" but as it booted everything was the dreaded same, all the apps crashing, then with the second rebooting was the current bootloop. i thought it was the same as before and just downloaded the usual zip file i use everytime but while flashing it (it did the same as mentioned in question 2 above) but it aborted instantly so i went and downloaded every rom there but it was the same so i went and tried the kernal zips too but always the same (i can't read my build number through the system recovery because it is like not fitting well in the screen si half the number isn't there that's why i asked question number 4)
so can anyone help me please? i'm in desperate need for help, i'm literally crying while typing this because i can't afford another phone and i'm so scared.
also is there a way to install custom recovery to not rooted device while in bootloop?
or if the system recovery was actually corrupted what do i do? :crying: