Hi, I have a problem, I made a custom recovery and installed android 13, everything booted up fine, but after I wanted to go back to recovery mode, it start bootlooping and to get back to android I had to use command adb reboot. Does anyone know what I'm doing?
Related
Device: Motorola Droid RAZR HD; unlocked bootloader; android 4.4
Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
The title explains it but I'll go into more depth about what's happening. I am trying to install Cyanogen so I flashed the latest version of Twrp for it using Fastboot and it was no problem, when it was done and it said successful I rebooted my phone with Fastboot but when I start it up in recovery mode it gets stuck on the bootlogo. I tried to flash it again but to no success. The phone works just as it should otherwise, does anyone know how to fix this?
I should probably say that I have already rooted it.
EDIT: Apparently something on my device was interfering with something, after wiping with fastboot -w, I could install TWRP fine and then get LineageOS on the phone.
I've been trying to unlock the bootloader and root my phone ever since Huawei sent out the notification that they would be shutting down their unlock bootloader service. Everything went pretty smooth until I wanted to try to root my phone. I loaded a superSU ZIP onto the internal storage and loaded it in with TWRP, which then led me to booting about halfway and then sending me back to recovery. So I went ahead and factory reset, cleared cache and rebooted, where I got into a boot loop (stock OS was still loaded, but it wasn't loading correctly and rebooting). I went back into recovery and tried wiping my phone again, and that led me to this point. I am able to get into stock fastboot, or bootloop on the splash screen (no OS, I think). Stock fastboot is limited on this phone because it makes you open HiSuite to modify anything but it hasn't put it onto my computer like it normally does. I've tried flashing TWRP on my phone from fastboot but it doesn't seem to work as it still boots into stock fastboot.
I have TWRP, Android SDK, SuperSU and LineageOS for the 5X on my computer, but the issue is loading it onto the phone. Any help is appreciated, and don't be afraid to tell me that my phone is toast because nowadays it's not worth too much.
Thanks!
I have had the Umidigi One Max for almost 3 weeks now. I have rooted, installed TWRP, disabled-Force-Encryption and tried a variety of GSI Roms (see below). I have put back on stock for now, because I have been having a weird issue with the phone. Hopefully it will not start happening now that I have stock back on the phone.
I've had both LineageOS/ResurrectionRemix 9 GSI installed, that ended up with the same issue.
I had ResurrectionRemix on it yesterday. All working fine, all day long. Bluetooth, Android Auto, WiFi Etc. As I'm sitting in bed, all of a sudden the phone popped a warning "Powering down". It reboots, and then boots straight into twrp. I manually reboot it, and again, it boots straight into twrp. I tried doing a full wipe, and restore of my backup in twrp, reboot, and it does the same thing, boots into twrp.
Tried restoring stock via SPflash, when I start the download process in SPflash, power off the phone, and plug it in, instead of starting the transfer, the phone wakes up and boots straight into TWRP!
The only way, I was able to for stock back on was by doing this:
From my Ubuntu Linux machine, issued these commands:
adb reboot bootloader
(All Umidigi stock images)
https://community.umidigi.com/forum.php?mod=forumdisplay&fid=211
1. fastboot flash recovery recovery.img
2. fastboot flash boot boot.img
3. fastboot flash userdata userdata.img
4. fastboot flash system system.img
5. fastboot reboot
At this point the phone boots back into stock, De-Encrypt, Install TWRP, and all is working for now. However, what would cause the phone to power down abruptly, only boot into TWRP, and twrp backups to fail? I also tried to do a full wipe (type yes), and install a new ROM, and that finished, and booted straight into twrp.
Also, I had unlocked the bootloader via fastboot, so I'm not sure if that contributed to this issue. I have since re-locked the bootloader just in case.
Links:
https://twrp.me/umidigi/onemax.html
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
https://androidfilehost.com/?fid=1322778262904004415
Hello! This is my first thread on the forum;
I'm writing because I think I soft bricked my Xiaomi Mi Pad 4 LTE, let me explain from the very beginning.
It's a brand new device, bought today, and with a custom italian ROM which was sold with.
I just wanted to root it, and the bootloader was already unlocked because it was a custom ROM, so I tried to install TWRP (mocha version for Mi Pad) with Fastboot and then I wanted to install Magisk.
The issue is that, when I tried to flash TWRP to recovery with fastboot flash recovery twrp.img, it all went "OK" but then TWRP was not actually flashed and couldn't boot it with key combinations, it just looked like it wasn't there. I also tried to boot it without flashing, with fastboot boot twrp.img but it gave me
"Failed to load/authenticate boot image: 00000050" error
Looking on the web, I found someone who told to try fastboot flash boot twrp.img and so, without even thinking, I did it.
That's the main issue. I rebooted, and found that TWRP started, but now I couldn't boot my device anymore, because the default boot.img file was replaced by twrp.img. So, practically, TWRP replaced my device's default system (I think?).
Then, I tried to find a stock firmware for Mi Pad 4 (Clover) on the web, and I found it, so I flashed the stock firmware boot.img, fastboot flash boot boot.img, but when I rebooted, the device was stuck in the loading screen with three dots loading over a "Powered by Android" logo. I waited 20 minutes, nothing, it looks stuck, so this stock boot.img doesn't seem to work.
I can actually flash TWRP and that stock boot image both whenever I want and switch between them; the first works, the latter doesn't.
So, in poor words: I flashed twrp.img as boot.img and now I can't boot normally, but TWRP starts when turning on my device.
But I just want to get my default boot.img or system, or any other way to reaccess to my device. That's fine even if I have to hard reset or wipe everything, it's fine even if I am going to lose data, but please, just help me.
Can someone help me? I'm just a newbie in this world, please help me unbricking my device.
Thanks in advance.
Try installing twrp again and boot to it
Download custom rom.of your choice ( im using hovac and it been great for a year now )
Move it to your mipad via comouter
Format everything in twrp and install the rom and gapps
--- I just remembered havin same issue u having and if im not mistaking : u should reboot to recovery right after installing twrp ( you dont reboot to system )
Im not really sure about it cause it happened long time ago
@DanielVipx
Sorry, seems you tried that already. Did you try the mi flash tool?
This might help:
https://osdn.net/projects/xiaomifirmwareupdater/storage/Stable/V10/clover/