Database Info

[Q] Screentouch doesnt work. Software?

Hi,
After a serious software problems (crashed with 4.0.3 OTA update) i managed install a ROM, but my screentouch doesnt respond to my touch. The screen and all buttons function very well but i cant put the pin because touchscreen doenst work.
Could it be Software or is definitely Hardware?

Could be software. Have you tried flashing a new ROM (and appropriately wiping beforehand)?

Have you tried to access to the recovery ? Some recoveries use the touchscreen as the TWRP for example

Harbb said:
Could be software. Have you tried flashing a new ROM (and appropriately wiping beforehand)?
Click to expand...
Click to collapse
I try do clean install a custom rom and 2.3.6 OTA and in both the touch doesnt work.
I install the touch recovery, but after dont work i install a regular one via fastboot.
Clean install (format system, wipe everything, etc) and nothing work.
Will continue try another custom roms

Cyrille28410 said:
Have you tried to access to the recovery ? Some recoveries use the touchscreen as the TWRP for example
Click to expand...
Click to collapse
I can acess to recovery sometimes
When it fails push it in PC via fastboot.

Now i cant enter in recovery and cant connect via usb to flash another recovery

I'm screwed!
I cant get into recovery, when i pressed appears a android toy whith a warning sine.
I cant connect to PC, when in bootloader and connect to PC, in bottom appears "fastboot fails invalid command".
I´ve installed a stock rom 2.3.6 and the touch screen doesn´t work to iniciate the phone. Try to install franco kernell but it´s the same situation.
When i can connect the phone to PC i´ve try´de 3 different custom roms and none works.
Going to warranty.

Looks like your touchscreen may have just given up. Everything else is normal, you probably don't have fastboot/adb setup properly and that warning sign is the stock recovery. I'd sort out fastboot and lock the bootloader before sending it in. Also, if you don't have a backup of your sdcard you can mount it through a custom recovery (use "fastboot boot recovery.img").

Harbb said:
Looks like your touchscreen may have just given up. Everything else is normal, you probably don't have fastboot/adb setup properly and that warning sign is the stock recovery. I'd sort out fastboot and lock the bootloader before sending it in. Also, if you don't have a backup of your sdcard you can mount it through a custom recovery (use "fastboot boot recovery.img").
Click to expand...
Click to collapse
I´ve format SD card and have nothing inside.
"I'd sort out fastboot and lock the bootloader before sending it in"
How can i do that?
Remember that i cant access to recovery or turn on by computer.

Read the rooting guide or check out NexusSHacks.com, all the info you'll need.

How are you "pushing" recoverys via fastboot if you don't have fast boot set up properly?
Anyways. Speaking of fastboot. Get the official fastboot images for your phone and flash them all. If you still have issues with the screen its a hardware problem.

You should make a full backup and then flash the official factory images (ICS 4.0.4), made for your hardware version, through fastboot. You can find the exact version beneath your battery on a sticker.
If the problem persists after this, it's most likely a HW problem.
If the mobile is not recognized in bootloader / fastboot mode, then connect it to a Linux PC, and then post here the output of the following commands (as root):
Code:
tail /var/log/messages
Code:
lsusb

albundy2010 said:
How are you "pushing" recoverys via fastboot if you don't have fast boot set up properly?
Anyways. Speaking of fastboot. Get the official fastboot images for your phone and flash them all. If you still have issues with the screen its a hardware problem.
Click to expand...
Click to collapse
When i was able to connect the phone to pc i push it with code flashboot flash recovery Some.img
Now i cant "push it".
I cant enter in fastboot

I´ve been able to enter in recovery.
Unroot and back to stock.
Now already of screentoch doent work, some buttons dont work.
Going to warranty. Thanks everyone for the effort.

[help] OMG i messed up big time no OS help please

I was using Mahdi rom , I have backup off all my roms ( cm11s stock 38r, Mahdi backup, pa rom backup). I also multirom with 3 secondary rom.
Ok, I swap my Mahdi rom with liquid smooth rom, so liquid smooth is my primary, didn't like it so I backup, restore cm11s 38r used it. Until now I reboot into recovery and swap 38r with Mahdi rom what I started in the beginning. Reboot it was stuck at the oneplus logo to a long time. Happen before to me and usually just hold the volume down and power it would be fine, when I did it this time it didn't work and it would end back in the oneplus logo. So I boot in to recovery then I notice everything is gone. No OS, no multirom, nothing in my restore. How do I get my phone running again. I know it's a long shot but my data like photo are gone or can I get them back? Haha
Don't know what to do, please thanks you.

if you can get into fastboot then it can be saved. simply boot recovery twrp and mount your phone as a drive. Then copy over your rom files and flash them.

Geo411m said:
if you can get into fastboot then it can be saved. simply boot recovery twrp and mount your phone as a drive. Then copy over your rom files and flash them.
Click to expand...
Click to collapse
how do i mount my phone as a drive in twrp? i cant seem to find it.
i could get in to fastboot mode, but dont know what to do from there. i see a few but are different from each other, so i didnt want to take the risk trying it.

chailee said:
how do i mount my phone as a drive in twrp? i cant seem to find it.
i could get in to fastboot mode, but dont know what to do from there. i see a few but are different from each other, so i didnt want to take the risk trying it.
Click to expand...
Click to collapse
Once you're in TWRP go to mounts and at the bottom right you'll see enable MTP. Click it and it should put your phone in USB mode. Now you should be able to copy your files to your phone to flash them without losing data.

This is what I did
chailee said:
I was using Mahdi rom , I have backup off all my roms ( cm11s stock 38r, Mahdi backup, pa rom backup). I also multirom with 3 secondary rom.
Ok, I swap my Mahdi rom with liquid smooth rom, so liquid smooth is my primary, didn't like it so I backup, restore cm11s 38r used it. Until now I reboot into recovery and swap 38r with Mahdi rom what I started in the beginning. Reboot it was stuck at the oneplus logo to a long time. Happen before to me and usually just hold the volume down and power it would be fine, when I did it this time it didn't work and it would end back in the oneplus logo. So I boot in to recovery then I notice everything is gone. No OS, no multirom, nothing in my restore. How do I get my phone running again. I know it's a long shot but my data like photo are gone or can I get them back? Haha
Don't know what to do, please thanks you.
Click to expand...
Click to collapse
I had a similar issue with a OPO I purchased from a “non-technical” person on CL. I looked high and low for the answer but nobody had the exact same problem. Your issue sounds almost exactly like mines. Here are the specifics…..
Issue: The phone’s OS was gone and it would just sit at the OPO logo splash screen.
Note: I was able to get into fast boot mode. I was also able to get into TWRP. I was not able to unlock the bootloader. The phone wouldn’t let me make system chances because the bootloader was locked. The OEM unlock command never worked for me.
Fix:
-I downloaded the drivers for the oneplus one. If you don’t already have them, you’ll find various links on XDA to point you in right direction.
-I downloaded the stock cyanogen 11 image from the OPO website.
-I downloaded the a file called "OnePlusOne-BootUnlocker.zip”
-I booted the phone into TWRP and used the command line to push the "OnePlusOne-BootUnlocker.zip" to the phone…….
adb push OnePlusOne-BootUnlocker.zip
-Once I did this, the file showed up in TWRP. I selected the file and ran it. This unlocked my bootloader. Once the bootloader is unlocked, you can actually push the stock image back to the phone.
-I downloaded the image file called cm-11.0-XNPH33R-bacon-signed-fastboot_64GB.zip (i have the 64gb model)
-I booted the phone into TWRP and pushed the stock image to the phone (i used the same push command I used to push the bootunlocker file) The file appeared in TWRP and I ran it. It installed the stock image on the phone.
NOTE: I am not a developer. I’m just an IT guy who played around for a day or so and fixed it myself. I didn’t see anyone with the exact same problem as me so I took bits and pieces from other solutions and created my own. I’m sure there’s a developer looking at this like WTF but this is what worked for me.

Geo411m said:
Once you're in TWRP go to mounts and at the bottom right you'll see enable MTP. Click it and it should put your phone in USB mode. Now you should be able to copy your files to your phone to flash them without losing data.
Click to expand...
Click to collapse
when i click enable mtp, doesnt work.

Jokool_7777 said:
I had a similar issue with a OPO I purchased from a “non-technical” person on CL. I looked high and low for the answer but nobody had the exact same problem. Your issue sounds almost exactly like mines. Here are the specifics…..
Issue: The phone’s OS was gone and it would just sit at the OPO logo splash screen.
Note: I was able to get into fast boot mode. I was also able to get into TWRP. I was not able to unlock the bootloader. The phone wouldn’t let me make system chances because the bootloader was locked. The OEM unlock command never worked for me.
Fix:
-I downloaded the drivers for the oneplus one. If you don’t already have them, you’ll find various links on XDA to point you in right direction.
-I downloaded the stock cyanogen 11 image from the OPO website.
-I downloaded the a file called "OnePlusOne-BootUnlocker.zip”
-I booted the phone into TWRP and used the command line to push the "OnePlusOne-BootUnlocker.zip" to the phone…….
adb push OnePlusOne-BootUnlocker.zip
-Once I did this, the file showed up in TWRP. I selected the file and ran it. This unlocked my bootloader. Once the bootloader is unlocked, you can actually push the stock image back to the phone.
-I downloaded the image file called cm-11.0-XNPH33R-bacon-signed-fastboot_64GB.zip (i have the 64gb model)
-I booted the phone into TWRP and pushed the stock image to the phone (i used the same push command I used to push the bootunlocker file) The file appeared in TWRP and I ran it. It installed the stock image on the phone.
NOTE: I am not a developer. I’m just an IT guy who played around for a day or so and fixed it myself. I didn’t see anyone with the exact same problem as me so I took bits and pieces from other solutions and created my own. I’m sure there’s a developer looking at this like WTF but this is what worked for me.
Click to expand...
Click to collapse
doesnt work for me, when i boot my phone into twrp, i cant push anything to phone. i pretty sure i got all the files need.
instead of going through twrp, can i do everything in fastboot? and flash the zip file?

Hope this will do it......
chailee said:
doesnt work for me, when i boot my phone into twrp, i cant push anything to phone. i pretty sure i got all the files need.
instead of going through twrp, can i do everything in fastboot? and flash the zip file?
Click to expand...
Click to collapse
NOTE: I apologize, I dont think I specified that it should be pushed to the SD Card. This should be done FIRST for the bootunlocker file and then the Stock Cyanogen file.
Try it like this.........
Turn the phone off then boot into recovery mode by holding volume down + power. Leave the phone at the main screen of the custom recovery for now.
Open a command prompt window and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools (This location will be specific to your pc and will change depending on where the file is located and how you have it named)
Code:
adb push ***INSERT FILE HERE*** /sdcard/

Completely stock OnePlus One stuck in bootloop after latest CM OTA update

Hi everyone,
I'm hoping you can help me. I've had a OnePlus One since August 2014, completely stock. Never modded it, never 'flashed' anything, never installed anything outside of the Google Play Store. Always installed the official OTA updates as they pop up on the phone itself. Basically a reeeeealllly boring android user!
So Thursday morning (09/06/2016) I got a notification that a system update was downloaded and ready to install. Clicked install, the process began, phone rebooted as per usual. However, on the install progress screen (the green android with the spinning cogs), about one third of the way through the phone freezes. About 20 seconds later the phone reboots itself and then tries to install the update again. Freezes. Reboots. Tries to install. Freezes. Reboots. Tries to install.... I think you get the idea. It was doing this for a couple of hours before I checked it.
I'm moderately tech-savvy but never really got involved with android modding, rooting or flashing. So I'm a bit confused as to why my completely stock phone is stuck in a bootloop after installing an official CyanogenMod OTA update. The current status of my phone is that I can only boot into Fastboot mode via VolUp + Power. I can get my computer to detect my phone in Fastboot mode, however it informs me that my bootloader is locked. Attempting to boot into recovery mode via VolDown + Power just starts the update install and enters the bootloop.
I've done some research in to flashing a recovery image or manually applying the OTA update. One problem I've noticed is that I have absolutely NO idea what version of Android / CM my device was at before the update, and I have NO idea what version it was trying to update to. I do know that it was some version of Marshmallow before it broke. I've had no issues with the phone before this, aside the occasional self-reboot.
I REALLY want to keep all my data (pictures, contacts etc.) and am very nervous about actually doing anything because I have very little idea as to what I'm really doing.
Can anyone offer any advice on how to get my phone to boot/update/recover through Fastboot with a locked bootloader and without losing any data?
Thanks,
Stormin'
AKA the "HOW DO I PLAY BOOM BEACH NOW?!" guy
Edit: I solved my issue. It might work for you too, permalink to my post (#9) below: http://forum.xda-developers.com/showpost.php?p=67278091&postcount=9

Are you able to get into recovery mode? If so, you should be able to just flash a new ROM. Sideload one using the adb push command, wipe your data (this will clear settings, apps, etc. DO NOT SELECT SD CARD - that will wipe your personal files including your photos). Then install. Hopefully it should all work fine.
If you can't access the recovery can you access the bootloader sceen (the one with the big green bugdroid)? Then I'd suggest using Fastboot to install a new recovery. Then try the above.
If you can't even get to that stage you're screwed, just like me (unless anyone has any ideas). I've had soft bricks many times before but today I can't even get to the bootloader screen. ADB says the phone is offline. The screen is back and flickers on for a split second every now and then. Bloody CM Updater.

As IBM9001 has said, if you can get into recovery - even being stock - you can still clear your cache - don't do a full factory reset, just the cache, this may help, but even if it doesn't it still rules out one option.

I can't access recovery mode, using the key combo it just boots straight into the installer.
I've got a support ticket open with OnePlus and a scheduled remote assistance tomorrow. However from the preparational email it looks like they are going to factory reset the phone and then clean install CM. They've instructed me to make sure that all my files are backed up... I assume this means I will lose them.
Is there ANY way just to access or pull the photos off my phone? That's the most important bit. Dropbox hit its storage limit at the beginning of 2015 and I refused to pay, so now I have 18 months worth of pictures that I have no other copies of on death row
The only thing I can access is Fastboot...
Edit:
ibm9001 said:
If you can't access the recovery can you access the bootloader sceen (the one with the big green bugdroid)? Then I'd suggest using Fastboot to install a new recovery.
Click to expand...
Click to collapse
I can boot into Fastboot mode, and plugging my phone into my PC works i.e. it is recognised. I have the fastboot .exe and USB drivers, and can issue commands to my phone through cmd such as
Code:
fastboot reboot-bootloader
which works.
How do I use a recovery .img through Fastboot? or can I pull the contents of the sd card through Fastboot?

Hey mate i had same problem with my friends phone. But in that case i was able to open recovery mode.. So if you can do that just download any full zip of opo.. Like cm12.1 or cm13. Then flash it without clearing data.. So will not loose amything not even a single application..
I did that by using adb sideload just google it how to use it. And for that download full android sdk toollit and then download only fastboot and adb domt download whole studio. Because somete old version of adb and minifastboot will not work on adb sideload... So good luck with that..

Hi guys,
I have the same issue!
If I flash a new recovery from fast boot will I lose my data on sdcard?
Thanks.
Sent from my iPad using Tapatalk

masterjigar said:
Hey mate i had same problem with my friends phone. But in that case i was able to open recovery mode.. So if you can do that just download any full zip of opo.. Like cm12.1 or cm13. Then flash it without clearing data.. So will not loose amything not even a single application..
I did that by using adb sideload just google it how to use it. And for that download full android sdk toollit and then download only fastboot and adb domt download whole studio. Because somete old version of adb and minifastboot will not work on adb sideload... So good luck with that..
Click to expand...
Click to collapse
I cannot boot into recovery mode, unfortunately

masterjigar said:
Hey mate i had same problem with my friends phone. But in that case i was able to open recovery mode.. So if you can do that just download any full zip of opo.. Like cm12.1 or cm13. Then flash it without clearing data.. So will not loose amything not even a single application..
I did that by using adb sideload just google it how to use it. And for that download full android sdk toollit and then download only fastboot and adb domt download whole studio. Because somete old version of adb and minifastboot will not work on adb sideload... So good luck with that..
Click to expand...
Click to collapse
I'm currently having a very similar issue, but my phone completed the update. It's just stuck in a reboot/"optimizing apps" loop. I can boot into recovery and I tried to clear cache, but It's still just optimizing apps then rebooting and optimizing again over and over. Do you think your suggestion would help me too?

Wooooo, I've fixed it! I don't know why what I did fixed the issue (probably bypassed something) but my phone is up and running again! First thing I'm doing is making a freakin' backup!
So I was just trying everything in desperation. So that others can attempt to fix the same problem, here's what I did:
1. State of phone was either boots normally and crashes when installing update, or boots into fastboot. Would NOT boot into recovery!
2. Booted into fastboot using key combo (hold Volume Up, then Power Button)
3. Attached phone to computer via data usb lead
4. Started up cmd console, used command "fastboot devices" to check that device was recognised (note you need the fastboot files and USB drivers etc., Google it if you're not sure)
5. Used command "fastboot continue" to continue with 'autoboot'. This rebooted my phone but skipped the installer and went to the 'optimising apps' stage. Left phone alone for a couple of hours but it got stuck in another bootloop optimising apps, rebooting, optimising apps and so on.
6. Turned phone off, then booted normally with just the power button. This started the update install again except it didn't crash, and completed the update install. Then it optimised the apps again (albeit with a different total app count) and once finished, phone starts up normally.
Thanks for all the suggestions everyone! Happy to have my phone back. Now to go through the half-dozen or so voicemails I've collected over these last few days... great.

Hi guys,
@stormin, congrats!
@masterjigar, so you didn't lose the data like photos etc. doing so?
I can boot to recovery, but can't connect by PC to it.
In fast boot mode my PC sees it as well as in dab sideload mode.
I haven't the boot loader unlocked then I have to do it first, right?
But cyanogen site says that unlocking the boot loader will wipe all the device data.
Is there any way get the photos and other files back?
Thanks.

From the FAQ:
Q4a: Can I flash ROMs or SuperSU or anything else with the stock recovery?
No, the stock recovery can only flash zips that are signed by CM, this means official updates only. You need a custom recovery to flash anything else.​
Click to expand...
Click to collapse
Does it mean I can flash an official CM firmware without unlocking the boot loader?
Thanks.

hibernick said:
Hi guys,
@stormin, congrats!
@masterjigar, so you didn't lose the data like photos etc. doing so?
I can boot to recovery, but can't connect by PC to it.
In fast boot mode my PC sees it as well as in dab sideload mode.
I haven't the boot loader unlocked then I have to do it first, right?
But cyanogen site says that unlocking the boot loader will wipe all the device data.
Is there any way get the photos and other files back?
Thanks.
Click to expand...
Click to collapse
That's what adb sideload is all about. It will give you temporary adb access (which is always after unlocking bootloader and root). So you can also flash xip via sideload. Without losing data and media..

Same problem, Also PC not detecting my phone
Hey Guys, I am Stuck at the same thing at Bootloop. But to do anything further I need to connect my phone to the PC. I haven't been able to connect my phone to PC since the time I have got the phone. I tried all available drivers and even tried different cables. I dont know what has been left out to try.
If any one has a working driver pls share the link. Its been three days now that my phone is dead.
Pls help!!
Thanks in advance.

masterjigar said:
That's what adb sideload is all about. It will give you temporary adb access (which is always after unlocking bootloader and root). So you can also flash xip via sideload. Without losing data and media..
Click to expand...
Click to collapse
can I flash this cm-13.1-ZNH2KAS1KN-bacon-boot-debuggable-b19ebe021f.img with the sideload and get adb working over usb?
Thanks

hibernick said:
can I flash this cm-13.1-ZNH2KAS1KN-bacon-boot-debuggable-b19ebe021f.img with the sideload and get adb working over usb?
Thanks
Click to expand...
Click to collapse
You can't adb sideload .img or a partition.
You have to use fastboot.
Code:
fastboot flash boot boot_img_name.img
or
Code:
fastboot boot boot_img_name.img

saurav007 said:
You can't adb sideload .img or a partition. You have to use fastboot.
Click to expand...
Click to collapse
Yes but then I have to unlock my bootloader first. And unlocking bootloader erase all the user files....
Is there other way to to run cm-13.1-ZNH2KAS1KN-bacon-boot-debuggable-b19ebe021f.img on the devise?

[Q] Google OG Pixel problems soft bricked

Hello everyone,
I have an OG Pixel 5'', the stock Android was 7.1.2 and I updated it to Android 8.1 Oreo. Bootloader is unlocked, and I am able to install a TWRP 3.2.1-0 no problems. Phone at the time worked well. Now I have tried to flash an ElementalX Kernel on my device. This worked and I managed to boot. However, a message "There is an internal problem with your device, please contact the manufacturer". There is a thread to fix this and I should have done my research better.
Anyway, I went into TWRP and did a complete wipe of the phone, thinking that I could have just boot into TWRP again and copy the stock flashable zips to reflash the ROM.
It turns out that:
a) TWRP doesnt work. I.e when I got into fastboot mode (Power + Volume Down) and selected Recovery, the phone flashed to screen with Google image and then flashed back into the one with the green Android.
b) I managed to boot twrp via fastboot from my computer. So I booted into fastboot mode, and then on my computer, did: fastboot boot <twrp3.2.1.zip>. This worked and I managed to get into TWRP again. However, I cannot transfer file to flash. I.e when the phone showed up on my computer in TWRP, I cannot drag and drop anything into mounted folder.
I have tried the following to get stock ROM from this website: https://developers.google.com/android/images
a) I decided to look at ADB Sideload. So from the above website, I downloaded the zip files under Full OTA Images and then in TWRP, I went into Advance and chose ADB SIdeload. On my computer, I did "adb sideload name_of_zip_file_downloaded". The process started but ended very quickly, the finished time was 0.00 second, which means that nothing happened. Clearly, TWRP console showed that it is unable to mount /data and other folders. I guess the reason is that I am running a "live" TWRP? I checked by going back to TWRP mainscreen and tried to mount. However, all hard drives show 0MB (OTA USB and the main drive).
b) I used factory images approach by downloading zip from the same website, but this time under Factory Images. For this one, I unzip the files to a separate folder. Then I did flash-all.sh script but it said that my fastboot is too old.
So... to fix fastboot, I tried: (I am on Ubuntu 16.04.02)
a) Remove whole android fastboot with sudo apt-get remove, then reinstalled => Did not work. Still fastboot is too old
b) Download entire Android SDK from here: https://developer.android.com/studio/install.html. Fastboot still didnt work
c) From the Android Studio website, I tried to download just the command line tools. However, I could not find the folder with fastboot in it. A Google search shows that the fastboot and adb should be in platform-tools folder. Couldnt find any
Once again, I apologize for a very very long thread (It's 5am and I am trying to figure this thing out). Please, let me know if you guys can offer any help. Any help is greatly appreciated. FYI, I am coming from a Moto Z Play, and if things happen I would just boot into TWRP and copy the zip over. Clearly, this is not the case. This is my 1st Pixel as well.
Please let me know and thank you very very much.

Installing ex messes with the boot.IMG you need to reflash twrp after. Also don't manually flash stock zips that doesn't even make any sense. Download the latest android sdk or base platform tools then get the latest factory image and extract it into platform tools. Then go into fastboot and manually flash the official factory image

To use fastboot on ubuntu you have to put sudo infront of the command: sudo fastboot ........, Because of a permissions thing.
Sent from my Google Pixel using XDA Labs

Thank you everyone. I have managed to reflash the OS. Gonna stay with stock kernel

maxwell0312 said:
Thank you everyone. I have managed to reflash the OS. Gonna stay with stock kernel
Click to expand...
Click to collapse
I personally recommend using a custom kernel just make sure to follow the OP exactly. As the kernel and twrp are usually stored in the boot.img together and the kernel overwrites the boot.img the problem was likely that you just did things in the wrong order which would cause twrp to be removed. Typically the order of installing custom stuff from stock goes this way: flash_all to restore stock boot.img, boot twrp, factory wipe, flash rom, flash twrp, boot rom, reboot into recovery, flash kernel, flash twrp, reboot system, reboot recovery, flash magisk. Some rooms vary as they may require you to do things like flash a vendor img or delete the vendor overlay folder(always follow OP).

Pixel 2 Magisk Bug won't take pin

Pixel 2 XL is soft bricked at the moment and I can't for the life of me think of what I need to do to recover it. I unlocked my bootloader and rooted when I switched to Pie, (I saw people we're already able to use Android pay on a rooted device again and I just couldn't help myself.) I installed twrp accidentally tried to flash TWRP not realizing I needed to temporary boot it and pushing the zip over erasing the recovery I proceeded to just fastboot it and carry on with the normal procedure with my phone. after getting Magisk installed I had my phone all set up until the next time I turned it on and back off again It said I forgot my PIN which I know I didn't I think this was because a glitch with smartlock I just setup so I go to my recovery and wipe the Dalvik cache, cache, Internal storage, and data and low and behold my phone bootloops never making past the final stage before it gets to the lockscreen. I go to Fastboot screen on my phone and my mac can't list my phone as a device in adb and now I am having issues getting back into recovery which I think might be because I am on the stock kernel my Fastboot screen on my phone says Product Name - Taimen, Variant - MSM USF:SAMSUNG(64gig) DDR:SAMSUNG, Bootloader version - TM220j, Baseband version - g899800253-1805232234, my Serial number, Serure boot - Yes, Device status - Unlocked, Vart console - Disabled, HW version - rev_10
I can't get it to stop bootlooping and just turn off.

bump

xda Zed said:
bump
Click to expand...
Click to collapse
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.

robocuff said:
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.
Click to expand...
Click to collapse
I stopped my endless bootloop! Now it says my device is corrupt and cannot be trusted and may not work properly when I tried to start it I couldn't get past the google screen. When I plug it into charge now it doesn't automatically going into a bootloop that can only be stoped by going into the fastboot mode or running out of battery, but the the charging symbol on the screen won't go away. I might have wiped system when I was in TWRP when I couldn't boot back after the first wipe. And I accidentally tried fastbooting Telstra img first. Anyway to get past this white Google screen? Also when I trey to go to recovery now it's the android laying on it's back with a red triangle and it says no command. Should I execute the flash-all script?

Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now

xda Zed said:
Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now
Click to expand...
Click to collapse
Glad to hear you got it working again. As for the recovery screen that say no command, that't the way it works with the stock recovery. When you see that screen, press and hold power and volume up. That will get you into recovery. If you happen to try rooting again and get stuck in a bootloop or some such thing, just flash the stock boot image.. That should get you going again.