Bootlooped after installing xPosed ontop of CM12.1 Beta - T-Mobile LG G4

So since I didn't read anything of xposed being "BAD" for the new CM beta, i figured i'd give it a shot.
The current gist is this:
Powers on, can't get into TWRP, if I get into the Download Mode and go to "Send_Command.exe \\.\COM4" and do "#id" it just comes back with "#" or it may take a long time, then it'll just come back with "#". Fastboot devices, shows nothing. ADB Devices same thing. I'd love to do a HardReset, or anything that could be done, but the only button config that works is Pressing Up when plugging the phone in.
Any ideas?
Yes I've seen others are having bootloops, noone seems to be having them due to what I've done (xposed + CM).
UPDATE: Problem solved. http://forum.xda-developers.com/showpost.php?p=63674157&postcount=3

Got a bit further thanks (i'll probably regret that word) to the LG Flash Tool.
Followed the instructions, flashed the KDZ, then I guess the flash tool error'd out because the Download Mode still showed 0% but the tool had a **** ton of ????? ??????
Needless to say, TWRP is booting up now!....but "unable to mount '/system'.
Attempted the H81110N Bootstack and Image, but that didn't work. due to the /system.

Retrying again with the LGTool, this time choosing English -_-
Looks like im at 52%, that error message i received i guess should have ben ignored.
\
Edit: wasn't looking good with LGTool crashing. but I've successfully gotten the phone back to stock it looks like. Just going through some reboots. I did get a glimpse of the LG setup screen

Related

[Q] Urgent: Nexus failing to boot

Hi all,
I have had my N1 for 1year and two weeks now (yes, warranty just expired). I was charging the device and it seemed to overheat and reboot. I unplugged it, took the battery out, let it rest for a bit and tried to boot it again. The phone now gets stuck on the X logo (not moving) and never boots.
I'm currently abroad (in the UK) and can't have it sent back for repair (I'd have to pay the repair too).
Will rooting the phone and installing an alternate OS fix my phone?
Is there any way to get HTC to honor the warranty after two weeks of expiration (I've been getting this problem for a while now, but that was only an issue if I made extensive use of the device while charging, which I almost never do so I didn't bother.)
Is there any way to fix this issue without messing with rooting? I'm abroad right now and all I want is my phone to work.
Any suggestions are welcome.
Try booting into bootloader from power off (vol- pwr) if that doesn't work then try the 3 figure salute (pwr vol- tb) your phone should boot into fastboot then just select bootloader.
If either of these work the your good you can get the static x fixed all you need to do is passimg (search wiki if you don't know what it is) as for the charging problem passimg will factory reset the phone so if that doesn't fix it then no you'll need to try rooting or it might be hardware.
Yes, I'm able to go into the bootloader.
I tried clearing the storage, choosing fastboot, etc. The phone seems to be working, just won't boot past the static X.
From your last reply, you're saying passimg has good chances to fix my phone. What does that involve? Do you have a link to a how-to that I could follow (it would really be a bad time for me to brick my phone, a good how-to would be really appreciated).
Cheers!
Yes passimg is used for many things it just reflashes a shipment ROM to the phone through bootloader. Like I said you can visit the wiki to have a how to here is a link http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_%26_Tutorials scroll down to "Unroot / Restore your Nexus" then follow the instructions. This should restore you to frg33 then you just need to update back to 2.3.4.
NOTE: this will wipe your data.
Ahh there's a way to unroot the nexus one now!
I had no idea! This is good to know (last time I checked was in December I think).
I will give that passimg a try as soon as I get home.
Can anyone confirm that this ("Attention: Latest stock ROMs don't flash using PASSIMG.ZIP method. Use the provided latest Froyo PASSIMG, and upgrade it after flashing.") means I can still reflash using this if I have the latest ROM (2.3.4) but will simply have to update again after (which I might not do given the issues I'm facing).
Cheers!
Confirmed - Dude is giving you good info... xD
Just to verify, unrooting is not the same as relocking. If you unlocked your bootloader (have a little lock symbol under the X screen), there is no way to relock it.
But the passimg is a good option. It will take you back to an older version of Android, and then you just let the system update itself.
Since you are out of your warranty, I can highly suggest looking into custom firmwares. These give you a lot more features and in many cases, perform better. CyanogenMod is probably the most popular one. These will fully replace your Android OS. CyanogenMod really doesn't even differ in look from stock all that much. Most people probably wouldn't even have a clue they are running something different, except for the stability and performance increases.
You can read up about this stuff in the wiki as well.
Oh, I see, thanks for the info.
I'm actually trying to get the FRG83 passimg file but the link is dead. Does anyone have an alternate one?
Use the FRG33 image
Alright,
I unlocked the device, used fastboot to write the recovery "Amon_Ra's Recovery".
Then I rebooted, went to the bootloader (trackball + power), went to "recovery" but the phone still gets stucked on the X (with the unlocked padlock logo).
Any advices?
Try the passimg, but it's possible that you are looking at hardware failure...
ldiamond2 said:
Alright,
I unlocked the device, used fastboot to write the recovery "Amon_Ra's Recovery".
Then I rebooted, went to the bootloader (trackball + power), went to "recovery" but the phone still gets stucked on the X (with the unlocked padlock logo).
Any advices?
Click to expand...
Click to collapse
If you are still running stock Android, you can't reboot between installing the recovery and getting into it. Stock Android will replace it. Try to go back to the bootloader and select recovery then, or fastboot to load the recovery, and then use fastboot to boot off of it.
Code:
fastboot flash recovery "c:\location to\recovery.img"
fastboot boot recovery "c:\location to\recovery.img"
Hopefully this will get you into Amon_RA so you can try again.
But the passimg method is used in the bootloader, not in recovery. You don't need a custom recovery to use the passimg method.
Amazing, thanks for pointing out my mistake, that give me a little bit of hope now . (I was at the point where I'd open the thing and look for a broken solder joint.)
I will try this as soon as I get home!
**Edit** I actually am not sure if I really rebooted or went straight to recovery. I'll update this thread tonight.
According to some other people, this would be a common issue with the internal memory dieing.
Is there a utility I can use to check the state of the memory?
None that I know of. Our phone internal memory uses the yaffs2 (Yet Another Flash File System v2) file system. I haven't heard of any programs that can check it.
Same situation
Hello, all. I haven't signed in on here in ages just because I've been so happy with how my Nexus has been running.
I ran into the same problem as OP stated.
I think I have some sort of hardware issue because my phone used to randomly freeze and couldn't be restarted unless I pulled the battery. Now it's at the point where I can't even turn it on because nothing happens when I press the power button or if I try to boot into recovery. This is really frustrating.
Is there any way to check for hardware damage? My warranty is over as well so I'd have to pay for any repairs to my phone if I sent it in.
If it's running, you can try to pull a log, and see what error reports you get?
andythefan said:
Now it's at the point where I can't even turn it on because nothing happens when I press the power button or if I try to boot into recovery. This is really frustrating.
Click to expand...
Click to collapse
Your power button might just be dead. Try having the phone plugged into a power source and removing and reinserting the battery. While you are doing that, hold the Volume Down button. This will get you into the bootloader which would allow a passimg to be performed. Hopefully your reboots aren't a hardware problem.
So , after pulling my battery, pulling the sim and the sd card, it finally turned on and went to recovery without freezing. I was able to wipe and reflash cyan 7. It's working well for now, but I'm really afraid this is going to happen again because this isn't the first time that it's just froze repeatedly.
Does anyone know what the problem could be?
Alright,
I did "fastboot flash recovery MYIMG" then "fastboot boot MYIMG", didn't work.
Then I tried "fastboot flash recovery MYIMG" then go to bootloader (without rebooting) and selected recovery.
Still no luck.
It always freezes on the static X logo. What else can I do? Will using passimg be any different (I don't have any way to put the file on the micro SD card but I can manage to do it if it's worth the shot).
Thanks

[Q] Boot lopp w/ AP, Plz help.

Droid 4 running Stock Jb 4.1.2, Safestrap 3.11, Liquid smooth 2.9, CM (last stable)
Everything working fine for a number of months, installed Liquid smooth via -> delete romslot 3, create romslot 3, install Liquid 2.8.
It ran for a number of days no problems. Restarted fine, all features worked great, even the annoying random restart from 2.4 went away.
6 - 10 days in, im surfin' the news sites at work, put it down, screen goes black, i pick it up. Hit the power button cause i realize its off and it just boot loops... so bad i had to vol-/+ pwr, go to flash mode and THEN turn it off b/c it just kept trying to restart, hang on logo.
I got home and decided to AP flash the latest:
9.8.2O-72_VZW-18-2
Blur_Version.98.72.182.XT894.Verizon.en.US for the maserati.
Boot looped a few times, i was able to get it to go into recovery mode, after that it loaded up the stock JB system. First boot it crashed and restarted, second boot it loaded but only the keyboard worked, not the touch screen. Went to the in OS option of factory reset mode + delete storage.
Rebooted, worked. Checked it a few boots, everything is fine. I use Druid 4 Utility Xt894 JB version and apply the root. Works great. Install safestrap, Create new partition, install liquid smooth 2.9. Works for an afternoon... at work today the touch screen stops responding, i restart it a few times. I try to enter recovery mode. Now im in boot loop again...
I've tried re flashing it again, a few times. I tried even going down to the previous release of JB for the phone. STILL 4.1.2!!!! But nothing.... it just boot loops... what did i do wrong? It was running great. No tweaks or anything done to it prior to it having its melt down.
Help please.. ive provided as much information as possible and though i only joined XDA now to post for help, i have read it for a long time as my main source for my phone and have donated to both CM and Liquidsmooth teams previously..
help!!!
I can't see where you are doing anything wrong. You have obviously done your research and have a good idea of what you are doing. I see, after you fastbooted, you went back to Liquid. I think I would try running CM10.1 or even stock for a few days and see if you have the issue there as well. If you do than it sounds to me like it might be a hardware issue. If not, maybe try re-downloading Liquid. Perhaps your zip got corrupted somehow.
I would love too. In fact i would be willing to run it on the stock crappy 4.1.2 if i could get it out of boot loop this time...
It just keeps boot looping on the logo. AP Fashboot flash and BP flash work but recovery and normal boot/reboot mode just goes into M logo boot loop.
I've re downloaded the 4.1.2 jb SBFs from 2 different sources to ensure its not a corrupt file, tried 18_1 and 18_2 software versions...
Is there a way to use the abd shell to get into the filesystem and check whats going on? Is the SBF the last call? or is there another route to see whats going on or just flash EVERYTHING? Like completely back to stock?
I can find my way around a PC file system but im not familiar with linux. Please help me understand, Is it like having CMOS and BIOS settings or equivalent to damaged CMOS firmware? What am i not replacing/reverting by SBF and HOW can i replace/revert BEYOND the basic sbf...
If ya point me in a direction or to someone who can help me out i can do all the foot work just point me in the right direction?
Is this applicable? I found a site talking about using CWM in a ADB shell file push to possibly get access to more features?
The article also goes into reading the busybox / ADB command screen? (sorry for not proper jargin) and see what its doing during the boot loop before it restarts?
Id add the link but i need more posts....
Update: Flashed 18_2 again with a "factory cable" i made, let it boot loop a series of times before it started up into the stock system again.
At first, again the touch screen wouldn't work, random lockups and restarts, etc. Since i just got it into the main system again and i had to leave for the weekend for a trip(no wifi or network), i couldn't mess with it all weekend but i left it on the whole time and kept checking its functionality... gradually its come back to full function. Touch screen works and is accurate, no more lockups, no more restarting, even stopped boot looping when i restart and enter recovery..
Im not sure and i couldn't find any forum converstations or write ups to support to idea but i think after a major crash and you flash new or reflash your SBF, it seems the phone needs time to recalibrate and index? Not sure, but just an FYI. Gonna try loading SS and liquid again.

Massive problem with the tablet

I have spent about 10 hours sitting here, with over 200 tab open trying to find a solution to my problems but I could not find one. My last option is to post here and hope someone can help me out.
I recently bought the tf701t which came with Android 4.2.2. Everything worked fine. A few days ago, I got pushed an update to android 4.3 but it was .1.7 not .1.18 (the newest apparently). With that update, my problems came. When I light up the device by pressing the power button, the lock screen was unresponsive. I pressed my pin numbers in but there was no response and it was as if the touchscreen was broken. However, the home and back button were all working fine. I had to randomly keep pressing until it finally started becoming responsive. When I got in, the quick management window (the one you get by swiping down), kept popping up the moment i press the screen. Because of this, I couldnt do anything. I couldn't even turn off the tablet as the power off option was unable to be pressed by me (When i did press, the window came up again).
After a while, i managed to get around this by again randomly pressing stuff. I got really frustrated and decided maybe if I install a custom rom, this problem might be fixed.
I read around a bit and found that the CROMix rom required firmware 1.18, which I did not have. Because of this, i decided to try install 1.18. First i used the asus unlock tool. Next I tried booting into recovery but here I met my problem. I have guides telling me to first boot using power button + volume down key. This worked. It then told me to choose the RCK option and press the volume up key. This however, did not work. When I selected the RCK option, the android figure appeared lying down with a red triangle and exclamation mark over it.
Unsure of what to do in this situation, i read one of the guides on this forum which said simply place the 1.18 zip file (yes i unziped the zip file from the file i downloaded), in the root folder then reboot and it would automatically update. This didnt happen.
I then tried using the adb thing but it said no devices were connected even when my tf701t was connected to the PC. I guessed that I needed to be in the recovery mode that I could not get into, before it would work.
I then read around and they said I had to first get Rom manager + the CMR recovery thing but Rom Manager said it needed root access. In order to get root access, I needed to get into the recovery mode yet again.
So now I am stuck. Whenever I try the RCK option, the error pops up and I can't get any further.
WIll someone please help me? I have no idea what to do anymore except throw the tablet out.
zhuang281 said:
I have spent about 10 hours sitting here, with over 200 tab open trying to find a solution to my problems but I could not find one. My last option is to post here and hope someone can help me out.
I recently bought the tf701t which came with Android 4.2.2. Everything worked fine. A few days ago, I got pushed an update to android 4.3 but it was .1.7 not .1.18 (the newest apparently). With that update, my problems came. When I light up the device by pressing the power button, the lock screen was unresponsive. I pressed my pin numbers in but there was no response and it was as if the touchscreen was broken. However, the home and back button were all working fine. I had to randomly keep pressing until it finally started becoming responsive. When I got in, the quick management window (the one you get by swiping down), kept popping up the moment i press the screen. Because of this, I couldnt do anything. I couldn't even turn off the tablet as the power off option was unable to be pressed by me (When i did press, the window came up again).
After a while, i managed to get around this by again randomly pressing stuff. I got really frustrated and decided maybe if I install a custom rom, this problem might be fixed.
I read around a bit and found that the CROMix rom required firmware 1.18, which I did not have. Because of this, i decided to try install 1.18. First i used the asus unlock tool. Next I tried booting into recovery but here I met my problem. I have guides telling me to first boot using power button + volume down key. This worked. It then told me to choose the RCK option and press the volume up key. This however, did not work. When I selected the RCK option, the android figure appeared lying down with a red triangle and exclamation mark over it.
Unsure of what to do in this situation, i read one of the guides on this forum which said simply place the 1.18 zip file (yes i unziped the zip file from the file i downloaded), in the root folder then reboot and it would automatically update. This didnt happen.
I then tried using the adb thing but it said no devices were connected even when my tf701t was connected to the PC. I guessed that I needed to be in the recovery mode that I could not get into, before it would work.
I then read around and they said I had to first get Rom manager + the CMR recovery thing but Rom Manager said it needed root access. In order to get root access, I needed to get into the recovery mode yet again.
So now I am stuck. Whenever I try the RCK option, the error pops up and I can't get any further.
WIll someone please help me? I have no idea what to do anymore except throw the tablet out.
Click to expand...
Click to collapse
Did you try to put the update on the external sd card? Not sure if that would make a difference but i remember i used to put it there...
You could also flash a custom recovery and flash the update that way. You can find more info in this thread:
http://forum.xda-developers.com/showthread.php?t=2636093
You should safely be able to update your factory firmware first by putting it at /sdcard location.. Then just reboot. It automatic. I Thought there was also an update available in settings after that. Don't unlock til you are at 4.3.
To unlock with Asus unlock tool make sure Google 2 Step verification is disabled.
Then I used fastboot to flash CWM recovery from a computer. I think you flash with fastboot from the newly unlocked bootloader. Power + Vol DOWN.
After you have flash recovery then you can enter it. No scary man lying down.
YayYouFixedIt said:
You should safely be able to update your factory firmware first by putting it at /sdcard location.. Then just reboot. It automatic. I Thought there was also an update available in settings after that. Don't unlock til you are at 4.3.
Click to expand...
Click to collapse
I forgot to mention one thing at the start. I don't actually have on hand a external microSD card. Which I think might be why placing the zip file in the root of the internal storage did not work.
Should it work? Is there any way to get around it? I've been trying to use sideload with cwm (finally got cwm working), but it comes up with "failed to write data protocol fault no status"
EDIT: Through cwm, I chose "choose zip from /sdcard" then select the "0" file directory then i found my zip at the location. I selected it and confirmed install. However, it then comes up with "Error in data/media/0/(name of update here).zip status 6"
Thanks for the help so far but anyone have an idea about this?
Not sure. After googling I see this
http://forum.xda-developers.com/showthread.php?t=1535546
---------- Post added at 09:54 AM ---------- Previous post was at 09:45 AM ----------
You can put the zips anywhere when your recovery is installed.
Okay so I finally managed to get the custom rom installed and working. However, this did not fix my problem with the touchscreen. I think it is because it only changed the firmware but not the android version (still 4.3).
Is there any place I could find android 4.2.2 rom? This was the one the tablet was on before the update that screwed everything up. If I could downgrade to that version, it may work again.
Thanks
I gave up and just put on the android 4.3 ota from droidbasement. Now the tablet randomly restarts and is stick in reboot loop. It wont even allow me to boot into cwm recovery to delete the cache. But i accept that I now have a $600 piece of **** on my hands. Going to bed. Night.
Ya i dont like the whole void your warranty for "using it" idea. If it responds to fastboot you might be ok.
You should be able to download a 4.2.2 rom from Asus' website (.47 was the last build for 4.2.2). You can use fastboot to install it.
Alta1r said:
You should be able to download a 4.2.2 rom from Asus' website (.47 was the last build for 4.2.2). You can use fastboot to install it.
Click to expand...
Click to collapse
I tried that before but it stated "update aborted" immediately after i pressed confirm, in CWM.
But all that is in the past now. I am pretty sure that the tablet is hard bricked since it no longer even opens bootloader. I accidentally pressed the wipe data option and I read that irreversibly damages the tablet. When I hold pwr+vl down, nothing happens anymore, it keeps on its reboot loop.

Unable to mount /data, fastboot doesn't seem to be able to write

Hi everyone, I'm having a lot of problems with my phone: last night, after it dropped to 0% battery life, it wouldn't charge. So i waited a while and ifinally managed to turn it on, but It wouldn't go past the Cyanogenmod logo. So i tried few things,first wiping cache, then factory reset from TWRP and I even tried the "Factory" option in the fastboot screen. Nothing worked, and it even got worse I think, TWRP says it's unable to mount /data partition and /storage partition. I don't know what caused it, and i don't remember the precise moment it became "unmountable" for the first time (since I've been trying to fix this thing for like 24 hours now).
Since i couldn't fix it via recovery, I tried looking for people who had the same problem on the internet, and I tried everything i could find. (like this: http://forum.xda-developers.com/showthread.php?t=2683787).
I then tried to go back to stock rom via adb and fastboot, but without success.
The main problem with fastboot is the fact that it doesn't change anything in my phone, it gives no errors when i try to flash the stock rom, but when i reboot my phone, nothing changes, or at least this is my opinion, since I still get the cyanogenmod logo, and TWRP doesn't get replaced (while it should go away, since when in the whole process of flashing the rom, i also flash recovery.img, which shouldn't be TWRP).
I tried a whole lot of other commands too, like "fastboot erase recovery", but TWRP is still there, and so is the cyanogenmod logo.
This is why i think fastboot is unable to write in my phone, but if that's the case, it should at least give errors.
So, wrapping up, my data partition seems to be corrupted, and flashing the stock rom still gets my into a bootloop (with the logo from the previous rom and TWRP still there).
Do you have any advice?
P.S: my phone is a xt1068
Are you able to pull logcat?
Logcat command works, i don't get errors in the terminal, but in the text file there's only this line : "/sbin/sh: exec: line 1: logcat: not found"
Dmesg works though, I don't know if it's helpful
"
dagrot said:
I then tried to go back to stock rom via adb and fastboot, but without success.
The main problem with fastboot is the fact that it doesn't change anything in my phone, it gives no errors when i try to flash the stock rom, but when i reboot my phone, nothing changes, or at least this is my opinion, since I still get the cyanogenmod logo, and TWRP doesn't get replaced (while it should go away, since when in the whole process of flashing the rom, i also flash recovery.img, which shouldn't be TWRP).
I tried a whole lot of other commands too, like "fastboot erase recovery", but TWRP is still there, and so is the cyanogenmod logo.
This is why i think fastboot is unable to write in my phone, but if that's the case, it should at least give errors.
So, wrapping up, my data partition seems to be corrupted, and flashing the stock rom still gets my into a bootloop (with the logo from the previous rom and TWRP still there).
Do you have any advice?
P.S: my phone is a xt1068
Click to expand...
Click to collapse
I have same phone, you mentioned you also tried to flash stock rom without success, did you flash the partition file aswell before flashing system and the rest of files ? Check the flashfile.xml file into the stock firmware folder to make sure you not missing anything.
Code:
fastboot flash partition gpt.bin
Good luck.
i'm on the same boat. It seems it's a NAND issue, but how come it happens randomly?
It seems to happen (its a bit rare, so don't get worried) when you let your battery drop to 0% and the phone suddently turn off, like what happened to the OP.
Sent from my XT1063 using XDA Free mobile app
Lynse said:
It seems to happen (its a bit rare, so don't get worried) when you let your battery drop to 0% and the phone suddently turn off, like what happened to the OP.
Sent from my XT1063 using XDA Free mobile app
Click to expand...
Click to collapse
If it's a bit rare, how come there are a rather interesting quantity of posts regarding that matter? I'd like to know WHY I can't write even with fastboot. There should be a way of unlocking the NAND / partitions. Even if I try to hard brick it, it's impossible.
PS: can we someone a look at this? http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
Possibly if we can force the way to QHSUSB mode, phone can be saved.
jhonnyx said:
PS: can we someone a look at this? http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
Possibly if we can force the way to QHSUSB mode, phone can be saved.
Click to expand...
Click to collapse
Unfortunately I didn't quite understand what that is about, if you happen to try it out let us know.
Anyway, if we don't manage to fix it, I guess I'm going to try and take it back to the store, since it is a common problem. Only problem is I'm on a custom rom and I can't even go back to stock and relock the bootloader, so I don't think they are going to replace it, but it's worth a try.
You can try by helping me to look for a circuit PDF from the board or trying it yourself.
I could try and disassemble it, but you're gonna have to wait a few days, I'm not at home and I'm gonna be back on the weekend.
As for the circuit pdf, I was only able to find videos and guides on how to disassemble it, unfortunately
Dude, no worries. Ive took the back out with all the screws, but I have nothng to make shorts with.... I'll come up with something. Take your time and keep me posted.
any news concerning this problem? i have tried searching for a manual but I did not succeed.
Anyways after finding the manual, we can short circuit the 2 capacitors there and the phone will be in qhsusb mode.
And after that ?
gbb14 said:
any news concerning this problem? i have tried searching for a manual but I did not succeed.
Anyways after finding the manual, we can short circuit the 2 capacitors there and the phone will be in qhsusb mode.
And after that ?
Click to expand...
Click to collapse
After that.... well.... after some research, we'll be needing singleimage.bin to use the blankflash utility for lollipop phones (mbm-ci 5.0 lollipop) so somebody can generate the singleimage.bin for us.
Once we have that, we can try to flash the phone at lowlevel to see what happens.
I will search the internets in hoping to find the schematics of this phone.
Keep me informed if you find it faster .
Cheers mate
we can connect through hangouts / etc.
look up for my user at gmail

Recovery mode and Root issues after stock flash

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..

Categories

Resources