XT1625 ATHENE_RETUS_CUST non-Amazon - System partition having issues (soft brick) - Moto G4 Questions & Answers

EDITED:
Basically it was soft bricked, now it's not but TWRP is gone because android removed it, android isn't installed correctly because the wifi doesn't work and it restarts randomly. And I can't flash TWRP now, just like when I first screwed this up.

Related

Need Help fixing my N4 :(

So I bricked my N4 somehow (I don't know if it is soft or hardbricked).
I was running latest N5X AOSP 6.0 Lollipop and everything was fine, when i decided to try the AICP 0.1 experimental LP. I made a clean install but it the first boot ended in a black screen. Then i rebooted into recovery and made a factory reset and since then Im stuck in an infinite bootloop.
So here is what i tried so far:
Flashed newest Factory Image via Fastboot and ADB. Result: Bootloop
(Flashed with flash-all.bat and every img by myself, i even tried without flashing cache.img and userdata.img, but everytime i ended in a bootloop that goes longer than 30 minutes)
I tried several Toolkits but nothing helps everytime I reboot its a bootloop.
But somehow when i flash the N5X AOSP 6.0 and let it boot for some minutes and then just shut it down and boot again i can see its optimizing my apps but when it comes to start them i just stays there...
I also tried to format my /cache with TWRP into FAT and back to Ext4 (that was one solution i found) but that doesnt seem to work too..
I am very frustrated and hope someone can help me

Boot loop after flashing latest Android 7 image

While on a developer preview of Android N with my unlocked rooted phone and TWRP 3.0.2-1, I accidentally ran the September OTA. The OTA failed, but left a mess behind with the phone rebooting 4-5 times a day.
Today, I decided to fix the problem, so I flashed the latest official image (NRD90U). Complete wipe, but since I have backups, I considered it to be no big deal. Turns out it was
The phone is now a boot loop (corrupt warning -> google logo -> corrupt warning -> google logo...). Reflashing changes nothing. Trying to boot (fastboot boot) TWRP (any version) does not work (it just goes into the boot loop). Tried to downgrade back to 6, same problem. Nothing seems to work.
Somehow, something is still ****ed up on the phone, but I have no idea what. This seems to be very similar to this thread (http://forum.xda-developers.com/nexus-6p/help/help-help-help-hard-bricked-6p-t3428225/page3), but there does not seem to be a solution.
Is it definitely bricked or is there anything I can do from fastboot to try and fix this? I am unlocked. I just need a stupid TWRP so I can restore my backup and hopefully get back to a working state from there.
PS: I'm sure I downloaded the right image and flashed it properly.

Missing White Recovery Prompt Screen

I was testing messi2050's arm64 TWRP and LOS. i was using it a while, then decided to restore a old backup with arm64 twrp. restored fine, but i locked myself out when my pattern was unrecognized. I pulled battery and attempted to boot into twrp using hard key method. I was unable to do so, each time it would boot back to system. It seems that the white screen prompting to factory reset has dissapeared entirely. The volume keys work fine, so I don't think that's it. I've flashed stock with LG Bridge and LGUP. I've locked and unlocked bootloader. Interestingly, when i flashed stock with LGUP, it didn't factory reset or remove my apps.

[Help] Bootloop after updating, usb debugging not enabled.

Using the miflash tool I flashed stock firmware (some version of android 8) after previously having a custom ROM installed. Everything worked fine until I rebooted after updating to the latest version using OTA.
My phone never got past the android one screen where it would freeze part way through, and after removing my sim card I could get to the pin unlock screen before the lock screen but after inputting the correct pin it would reboot and ask me for it again and again. I can get into fastboot fine but since usb debugging wasn't enabled and my bootloader is locked I can't reflash.
Booting into recovery also only brings me to a screen where the android mascot has a red triangle with an exclamation mark and a message saying "No command", so I can't factory reset.
Is there anything I can do to unlock the bootloader in this state or factory reset? (all flash tools and fastbooting into TWRP require the bootloader to be unlocked which in turn requires usb debugging to be activated)
Thanks for your time.
Update: I messed around with stuff on the cli based tissot tool and used option 2 to boot me into TWRP. It didn't do that but brought me into android where a system process kept repeatedly closing until a random factory reset happened.
I then got into normal android for a bit before I had to reboot (did remember to unlock the bootloader this time). I can now install twrp fine but every time I install the stock rom using miflash or try to install resurrection remix through twrp I get the same bootloop issue.
For some reason also my internal storage is completely empty no matter what i do so i need to sideload roms via sd card. And sometimes twrp gives me the error "failed to mount /system"
Trying the latest version of LineageOS next.
Update 2: if you have the same issue I had, the only working fix I've found is this restore point for twrp. Have not tried to update yet in case it breaks again but will make a final update with how that goes.
[SOLVED] Mi A1 BOOTLOOP
THIS PROBLEM IS VERY ANNOYING!! (The reason is because i didn't backup EFS before i flash Custom ROM) And I would like to share how to RESOLVE it. **your phone must be Unlocked Bootloader. Search Google how to do it. (Quick tip: in Fastboot...
forum.xda-developers.com

Data partition not recognized. TWRP does not boot.

Hello guys,
I broke my Suez - I need some help.
I went through all the pain of opening up and unbricking it with amonet-suez-v1.1.2.zip from https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/.
Then I was in TWRP, I think 3.2.sth.
I tried to adb sideload the latest lineage for my device from this thread: https://forum.xda-developers.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/
The installation finished with a red error message like /data partition not found.
I restarted the tablet, which is now stuck in a lineage os bootloop.
I thought the problem might be not having the most recent TWRP. So I brought the tablet into hacked-fastboot, and flashed TWRP 3.6.1.2, from https://forum.xda-developers.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/, which succeeded.
Not I can not even access my recovery anymore. When I try to with volume and pwr, the screen stays black and the tablet resets, ending in the TWRP bootloop.
A) why is the lineage in a bootloop
B) What about the /data partition missing error
C) How to get my TWRP to work again?
I can redo the unbricking stuff, but I would lang in the exact same situation. Where should I try different stuff?
I could think of replacing the old TWRP of amonet-suez with the most recent version, and then do the unbrick procedure with shorting again.
Push. I need help.

Categories

Resources