tried putting custom rom on my ZE552kl and now it just boots to TWRP.
It installs the rom but just boots back to recovery.
I think I forgot to enable debugging in dev options before I started all this.
Any way to get the thing working again?
Closed at OP request.
Related
Hey guys, I'm a longtime XDA browser but hardly ever post. I have the MXPE rooted with the newest TWRP build and has been running great since I got it. last night flashed the Deodexed 6.0 build from AICPs 5.1.1. I had some issues with the SD card being mounted as internal storage and erasing something so I tried to flash back to stock as my nandroids weren't seen as usable.
Long story short when I flashed back to stock, the recovery would never take. I've flashed the stock recovery and twrp to no avail. For some reason it wont actually stick. Everything else is back to stock but that. When I used the win toolkit and tried to flash twrp again it said something about the folder locations so I'm wondering if I messed something in the partitions.
Question is, have you guys ran into this issue or have any insight on where to go from here? I've looked around but I couldn't find a post that the same as this issue. As a side note, I can get into the bootloader just fine.
I appreciate any info that someone can provide.
Flash twrp. Reboot back to recovery from recovery. Reboot system.
Hopefully it's that easy. Stock os flashes stock recovery on boot. Rebooting recovery from recovery prevents that from happening.
From TWRP:
"Note many devices will replace your custom recovery automatically during first boot.... Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
mxpe 6.0
Thanks for the info ffejy462. What happens when I try to flash TWRP and it doesnt stick? I know for a fact that I can boot into it temporarily with fastboot boot and the recovery file. Should I just flash it from there?
THEFILLTER said:
Thanks for the info ffejy462. What happens when I try to flash TWRP and it doesnt stick? I know for a fact that I can boot into it temporarily with fastboot boot and the recovery file. Should I just flash it from there?
Click to expand...
Click to collapse
I'm sorry I didn't see this sooner. Flash recovery with fastboot. Boot into recovery. From reboot menu in recovery, select reboot recovery. Twrp will patch so recovery isn't lost again.
mxpe 6.0
That did it. thanks alot ffejy462!
i loaded the TWRP but when it boot to TWRP i cannot swipe or not responding. now i rebooted the system and reset the phone. it went back to TWRP.
what are my options?
The TWRP build is in alpha stages and currently has no touch and encryption support. Were you trying to root? If so, the instructions do not require you to actually do anything from within TWRP phone-side. Also, if your device isn't booting, you may find it helpful to reflash the stock boot image for your build, which can be acquired from the factory images posted in the development section.
Hi guys,
I hope you will be able to help me with getting back to stock. I wanted to root my phone, so I unlocked BL installed TWRP to A partition, installed TWRP to both partitions via TWRP , set boot partition back but was unable to boot to the system. TWRP was launched on A even B partition. So I installed custom zip rom from TWRP. The ROM booted but I lost touch screen. I wanted to go back to stock but even adb sideload (error:adb sideload footer is wrong) even flashing stock rom via "eraseall" option doesn´t work (the cmd window force close after few seconds and phone is booted again to custom rom). I read almost whole discussion tried some things but without success. I tried different cables and both USB ports on the laptop and still the problem persists.
Thank you in advance for your advice!
eldeecko said:
Hi guys,
I hope you will be able to help me with getting back to stock. I wanted to root my phone, so I unlocked BL installed TWRP to A partition, installed TWRP to both partitions via TWRP , set boot partition back but was unable to boot to the system. TWRP was launched on A even B partition. So I installed custom zip rom from TWRP. The ROM booted but I lost touch screen. I wanted to go back to stock but even adb sideload (error:adb sideload footer is wrong) even flashing stock rom via "eraseall" option doesn´t work (the cmd window force close after few seconds and phone is booted again to custom rom). I read almost whole discussion tried some things but without success. I tried different cables and both USB ports on the laptop and still the problem persists.
Thank you in advance for your advice!
Click to expand...
Click to collapse
I was lucky one with August firmware. Problem solved, can be closed.
So I flashed LineageOS 18.1 and tried it a bit. I wanted OPlauncher in LineageOS but placed it in wrong root folder and now it won't boot.
I decided to just flash back stock OS because I like it more anyway. But when I flashed it in the recovery, i rebooted and it didn't work. It still shows the LineageOS boot animation and reboots after a while and goes back to lineage fastboot.
Then I flashed TWRP to install the stock OS through internal storage, that didn't work either.
Tried flashing on both A and B slot. No success.
In the end I only have TWRP and a boot animation from LineageOS.
Can someone tell me what to do to go back to complete stock?
Thank you!
bokkoman said:
Can someone tell me what to do to go back to complete stock?
Click to expand...
Click to collapse
Boot to TWRP, backup your data if you haven't done so already. (It will get wiped when you go back to OOS, and will need to be wiped to boot)
Option 1 (To stay, the route I always try first as it doesn't relock the bootloader):
- Fastboot Rom
- Fastboot Rom Thread
- I also cover this in my Installing LOS Guide.
- You might also see this post from that thread. You can create your own fastboot ROMs, as that thread as not been updated in a while.
Option 2 (This requires Windows, and will relock the bootloader)
- MSM Tool Thread. This will make your phone exactly as it was out of the box. Make sure you have the correct drivers installed.
OhioYJ said:
Boot to TWRP, backup your data if you haven't done so already. (It will get wiped when you go back to OOS, and will need to be wiped to boot)
Option 1 (To stay, the route I always try first as it doesn't relock the bootloader):
- Fastboot Rom
- Fastboot Rom Thread
- I also cover this in my Installing LOS Guide.
- You might also see this post from that thread. You can create your own fastboot ROMs, as that thread as not been updated in a while.
Option 2 (This requires Windows, and will relock the bootloader)
- MSM Tool Thread. This will make your phone exactly as it was out of the box. Make sure you have the correct drivers installed.
Click to expand...
Click to collapse
Thank you!
I went with the MSM tool, and with some struggle in the beginning with connecting (sahara error), it finally succeeded.
Device is back to normal.
Hey, I'm new here when it comes to writing forum posts, so bare with me.
I've had this tablet for a few years now and I had flashed it with one of Magendanz roms (Nexus Stock) and I wanted to change to the LineageOS rom he had. I downloaded the .zip file and copied it to my sdcard and tried to get into TWRP to flash it. I did restart to recovery in the OS and once it restarted, it's been doing a boot loop ever since. I have tried using Odin to flash the rom that way, but for some reason it'll keep doing a boot loop after it's done flashing and restart. I can try going back to the stock firmware if it's a final option to get this tablet working again, but I would love to see if I can get LineageOS to work.
DengekiMatsuko said:
I did restart to recovery in the OS and once it restarted, it's been doing a boot loop ever since.
Click to expand...
Click to collapse
I had a similar issue once. It turned out that after flashing, not all the partitions mounted properly.
Are you still using TWRP? Boot to recovery, and go into "Mount". Make sure the system and other partitions are actually ticked. That solved the problem for me, and I was able to successfully boot to the system.
Hopefully your issue is that simple!
I managed to brick my Tab A 10.1 (2019) last year by dirty flashing ROMs I shouldn't have. I properly munted it, I couldn't even get into recovery. But I could still get into download mode with a USB cable plugged in to my laptop (it needed to be plugged in for download mode to come up). I flashed the stock ROM, which made it bootable again, which then allowed me to re-flash TWRP and then Magendanz' LOS18.1 ROM.
If you completely break your tablet, reflashing the latest stock ROM for your region is a great way to get back to a familiar starting point. You can then follow people's guides online to get where you want to be.