Hi guys, I have stumbled upon a problem and any help found here is not helping. I have decided to finaly root moto E (I thought I am too old for rooting now, but I am not) and the problem I got is pretty simple.
Bootlocked unlock is ok.
But then I decided not to reflash stock recovery and just to boot into recovery for once to flash superSU to avoid martyrium caused by getting original recovery (since HTC different retarded versions for every country and every retailer, I am very cautious). I have tried 2 versions of TWRP, one CWM, after "fastboot boot recovery.img" phone boots forever, never finishes, but phonw is fully operational still, so no damage done. I have even tried to reflash recovery in the end, none of them worked. Well, command prompt told me OKAY OKAY, but nothing really happened, like while just booting into recovery. I have even tried several USB cables (happened once with desire X that everything was due to broken USB cable).
I am out of ideas, could please someone point me to some direction of what is wrong?
It runs 4.4.4
mindlesSheep said:
Hi guys, I have stumbled upon a problem and any help found here is not helping. I have decided to finaly root moto E (I thought I am too old for rooting now, but I am not) and the problem I got is pretty simple.
Bootlocked unlock is ok.
But then I decided not to reflash stock recovery and just to boot into recovery for once to flash superSU to avoid martyrium caused by getting original recovery (since HTC different retarded versions for every country and every retailer, I am very cautious). I have tried 2 versions of TWRP, one CWM, after "fastboot boot recovery.img" phone boots forever, never finishes, but phonw is fully operational still, so no damage done. I have even tried to reflash recovery in the end, none of them worked. Well, command prompt told me OKAY OKAY, but nothing really happened, like while just booting into recovery. I have even tried several USB cables (happened once with desire X that everything was due to broken USB cable).
I am out of ideas, could please someone point me to some direction of what is wrong?
It runs 4.4.4
Click to expand...
Click to collapse
Please post screenshot of terminal.
Try these steps
1: adb reboot bootloader
2: fastboot devices
3: fastboot flash recovery name-of-the-recovery.img
not at pc atm,but as I said,devices list my device, fastboot flash gives okay twice,same as fastboot boot, and reboot bootloader... I think it would not help me at all, bootloader is accesible
edit: adb reboot recovery does notghing else than manualy booting into recovery (=nothing)
I didn't pay attention to HTC part, recently I faced same problem after flashing recovery and worst part was when I did Factory Reset. It got stuck on forever Boot Loop. Try this Go through Recovery 1. Wipe Dalvik Cache 2. Factory Reset. This worked for me hope same for you. And correct me if I couldn't get your problem.
Related
Hi,
i hope anyone from here can help me i think i have bricked my Phone.
I had a rooted phone with Modaco Rom and wanted to switch to DarchLegend or DarchDroid but i couldnt install one of them, i had only a boot-loop.
so i thought my RA-recovery-image is the problem, so i have installed the one from Darchrom with adb on my sdcard.
But now the recover image isnt working and also my phone have a boot-loop.
the only thing i have is fastboot but i cant do something like "fastboot boot image.img" because i get not allowed: remote.
any suggestions?
You could try flashing an old RUU again and start the rooting process from scratch?Did you do a full wipe before flashign the darchdroid rom?
I KNOW I SHOULD POST THIS IN MY NON-EXISTANT DEVICE FORUM,
but there is like no community there and I figured I would get a faster answer here.
I have an LG Mytouch Q C800 and I accidentally applied an OTA update with CWM installed. Since then I have been in a CWM bootloop, unable to boot into normal android. I dont think I can access fastboot or ADB. I have tried reflashing the stock ROM and everything. Can anyone help?
Yoyomah20 said:
I KNOW I SHOULD POST THIS IN MY NON-EXISTANT DEVICE FORUM,
but there is like no community there and I figured I would get a faster answer here.
I have an LG Mytouch Q C800 and I accidentally applied an OTA update with CWM installed. Since then I have been in a CWM bootloop, unable to boot into normal android. I dont think I can access fastboot or ADB. I have tried reflashing the stock ROM and everything. Can anyone help?
Click to expand...
Click to collapse
man the same thing happende to me, the only way i could partially recover my phone was flashing clockwork mod and from there install Cianogenmod 9, then in recovery mode conected to the pc via cable and typed:
"adb reboot bootloader"
once in Fastboot mode typed:
"fastboot boot boot.img"
where boot.img is the file contained in the cyanogenmod .zip file, doing this i managed to boot the rom and use my phone, the problem is that anytime it restarts it gets stuck in the boot loop again, and i have to repeat the process for it to boot again, i think is a bootloader problem since i have virtually done anything else, i think that the OTA update from tmobile changes something on the bootloader and it forces recovery/update boot always, and since the OTA never was completed it never got back to it's original state, its´s just my theory, i´m looking into it, but for now my phone works!.
Solution
I found a solution for the lg c800 bootloop, se my post: http://forum.xda-developers.com/showpost.php?p=39453347&postcount=10
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/
EDIT:
In my way of trying to apply to warranty and flashing the stock package into the phone and Windows being Windows, I had problems using the batch script, it stopped for long time and didn't do nothing forcing me to restart the phone and restart the batch, until I uninstalled the driver and make Windows reinstall it automatically (manage devices) and it finally flashed it all, actually I flashed the package three times just to be sure lol. So, in the end I wanted to turn off the friggin phone because I was very done with it (what a PITA it has been) and wanted to apply for my warranty so as there is no command in fastboot to shutdown the phone I didn't know how to shut it down so I tried pressing Power button and releasing it the moment the screen goes off but I think I didn't do it right or the phone can't be shutdown that way (this is most probably the answer), well the phone rebooted and by the grace of Zeus it booted for the first time into MIUI and now is waiting for me to configure the phone, none of the times I flashed this packaged into the phone it booted into MIUI, never, and just when I want to turn the phone this thing boots, I don't know if I'm going to venture into flashing anything again being the phone how it is but goddamnit it was a real PITA, I had to use my old Redmi Note 3.
So, tl;dr: Flashed stock package, phone booted finally, all is OK for now.
====================================================================================================
====================================================================================================
Sooo, I was having problems with flashing stuff on this phone but I solved them and I was able to flash HavocOS, it was OK and I could use my phone kinda well (some reboots but nothing serious, or so I thought). So, until 12 hours ago my phone was having problems with the File Manager (I used FX app and also the stock one), it hanged and didn't respond and made the phone reboot itself a couple times, that was weird, actually the whole time I used this ROM I was having problems with my files, it used to took long time to read some files and I was thinking that maybe my SD was bad but apparently it's not. So, after the second reboot I was able to finally open the file manager but navigating through the SDCard was buggy and the app didn't show me any file (it show me an empty list) so I rebooted my phone manually (this time wasn't done by the phone itself) and now is when the phone never passed from the Havoc logo, I waited something close to 30 min and nothing, rebooted and waited 10 min and nothing, it still hanged on the logo, went into recovery to wipe everything and re-flash all and after doing all that and tried to boot to system my phone was booting to recovery and didn't past that, tried installing stock (flash_all script) and then installing recovery and everything again and nothing, it booted to recovery always. So there is when I realized I couldn't change anything in the slot A (at least to what boot refers), I can't install TWRP nor OrangeFox, I can do it in slot B, and even if I boot into recovery on slot B I can flash the zip installer, change the slot and try to boot to recovery from slot A but it boots to the bootloader, and yes, TWRP didn't output any error when flashing the installer.
Yes, the script flashes everything OK, well not everything, system and vendor partitions (A and B) I had to flash them manually because it gave me some errors with the script (reading errors, and yes I compared checksums so it was super weird) but in the end supposedly the stock ROM must have been installed, which I couldn't try because even after flashing everything on the script the phone was booting to bootloader, I didn't give importance to this because before I was able to flash and boot HavocOS I did the same thing because my phone was bootlooping into fastboot: I ran the script, flashed manually those images because it gave me the same errors, tried to boot to system and the phone booted to bootloader, didn't give a sheat, flashed OrangeFox recovery, ROM, recovery installer, GApps, nofde patch and then I was able to boot to HavocOS. But now this time I tried to install TWRP with fastboot command but it didn't worked, fastboot doesn't throw any errors while flashing, it reported:
Sending 'boot_a' (39780 KB) OKAY [ 1.042s]
Writing 'boot_a' OKAY [ 0.208s]
Finished. Total time: 1.263s
But if I try to boot into recovery it sends me to fastboot/bootloader, if I do this in the slot B I can successfully boot into recovery and, as I said, if I flash the installer, change the slot and reboot to recovery, my phone reboots to fastboot.
This has happened to someone else?
Does anybody knows of any solution?
I still have warranty (phone has less than 3 months) so I probably can flash the stock package and lock my bootloader so I can get my phone checked as probably it is a hardware failure, probably and hopefully .
Oh, and also I have to add that the recovery was also lagging sometimes (OrangeFox). Sometimes when I was looking into files on the SD, also when I pressed the "reboot system" button it hanged for half a minute and the it proceeded to reboot, and also once when I was flashing the nofde patch the phone also hanged and rebooted into recovery by itself. So this indicates that maybe is a hardware thing right? Because there is no way that the recovery could have gotten corrupted or something just out of the blue.
Yes. I'm another victim here... And now I can't install recovery on slot b either. Can't figure out what's wrong. This giving me such a hard time...
RthurPendragon said:
Yes. I'm another victim here... And now I can't install recovery on slot b either. Can't figure out what's wrong. This giving me such a hard time...
Click to expand...
Click to collapse
What I ultimately did was wipe everything on slot A, then wipe everything on slot B, then I proceeded to install the ROM on the slot A then re-flash the recovery and reboot to system and that's all. But I did had to wipe both slots A and B. If nothing works you can apply the original ROM (search for it on these forums) and go back to stock.
Jhon_Locke said:
What I ultimately did was wipe everything on slot A, then wipe everything on slot B, then I proceeded to install the ROM on the slot A then re-flash the recovery and reboot to system and that's all. But I did had to wipe both slots A and B. If nothing works you can apply the original ROM (search for it on these forums) and go back to stock.
Click to expand...
Click to collapse
In my case, I wiped system and installed Evolution X ROM (OSS version) with Custom Recovery (SHRP) Then when I want to reboot into recovery again to flash Magisk, There's no recovery... It always opens with fastboot mode. I tried flashing recovery.zip from slot b. Still no result.
Yes. I'm next victim here... And now I can't install recovery on slot b nor slot a. Can't figure out what's wrong. When i flash twrp recovery it flash successfully but when I boot into recovery it stuck in fastboot mode
Change slot and flash again but nothing worked it again stuck in fastboot mode even i flash different version of Twrp(3.2.1) but again it stuck in fastboot mode both a and b slot.
So i flashed stock rom and lock bootloader.
If have any solution how to install custom recovery please help me.
Thanks
Iamdchandan said:
Yes. I'm next victim here... And now I can't install recovery on slot b nor slot a. Can't figure out what's wrong. When i flash twrp recovery it flash successfully but when I boot into recovery it stuck in fastboot mode
Change slot and flash again but nothing worked it again stuck in fastboot mode even i flash different version of Twrp(3.2.1) but again it stuck in fastboot mode both a and b slot.
So i flashed stock rom and lock bootloader.
If have any solution how to install custom recovery please help me.
Thanks
Click to expand...
Click to collapse
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
garylawwd said:
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
Click to expand...
Click to collapse
I have flashed twrp latest 3.4.4 for Android 10 but it is stuck in fastboot mode either slot a or b.
What happened if i downgrade Android 10 to 9 and then flash twrp. Maybe it will successfully flashed.
Iamdchandan said:
I have flashed twrp latest 3.4.4 for Android 10 but it is stuck in fastboot mode either slot a or b.
What happened if i downgrade Android 10 to 9 and then flash twrp. Maybe it will successfully flashed.
Click to expand...
Click to collapse
Don't do it you will mess up your persist partition.
How are you flashing? You must be after typing something wrong
garylawwd said:
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
Click to expand...
Click to collapse
garylawwd said:
Don't do it you will mess up your persist partition.
How are you flashing? You must be after typing something wrong
Click to expand...
Click to collapse
First if all reboot into fastboot mode then connect with pc then type command " fastboot flashing unlock" enter now again forcefully reboot into fastboot mode then type next command "fastboot flashing_critical unlock" now bootloader unlock.
Again reboot into fastboot mode then type command "fastboot getvar current-slot"
Now change current active slot and then type command " fastboot erase boot" . Now finally flashed twrp latest (3.4) for Android 10 with command "fastboot flash boot twrp.img" now it flash successfully then type command "fastboot reboot" and then press volume up then hit enter and it return in fastboot mode then i have again change slot and repeat all process with that slot but it again stuck in fastboot mode. After all i have changed twrp version but again same thing repeat so I flashed stock Android 10 through Mi flash and lock bootloader.
That's all whole process.
If do something wrong please help me to figure out.
Waiting for your reply ?.
Love
try sharp recovery
Sami Devo said:
try sharp recovery
Click to expand...
Click to collapse
I don't know installation process of sharp recovery.
Iamdchandan said:
I don't know installation process of sharp recovery.
Click to expand...
Click to collapse
install on the other slot... dont flash it on running rom slot... if rom running A.. chng it to B. then flash to B.. then goto recovery flash the sharp zip when sharp opens..then again chng slot to A.. running rom slot..
okk ur phn boots.
Hi all, in general I tried to put EliteRom, the phone went into a fastboot loop, I even tried through miflash, still can not get out of the fastboot. I don't know what to do.
It seems to me that this happened because I immediately after unlocking bootloader through MiFlashUnlock went to fastboot and tried to put elitrom through fastboot respectively. There it seemed to go successfully, but stopped at some process (setting to A, I don't remember exactly), it went very long, about 10 minutes nothing happened, I thought that the process had already finished and tried to boot into the system, but got back into the fastboot. Then I tried to install TWRP via adb, everything seemed to work, but I could not boot into the recovery via volume+on/off or the adb command.
Despaired, decided to return everything as it was through miflash, chose the item that the bootloader is not locked, and the installation failed. Then i chose to lock the bootloader and it seems to say it worked.
Yay, but no, the phone is still hanging in the fastboot and won't start up. Please help the fool, I don't want to go to the service, but I really don't know what to do anymore.
And when I try to put EliteRom again, the console at some point just kicks out
Well dunno what will say others but I have been through this shiet too and ended up in Xiaomi service .. but yeah, you'll wait like week or two...btw no worries about warranty problems cause unlocked bootloader,they don't give a crap..
Hi, try to flash a12 twrp(link is in the xda k50gt) throught fastboot (fastboot flash recovery bla-bla.img), then wipe everything in the wipe section. Install recovery miui.zip then flash. I couldn't understand that you flashed twrp via adb command in bootloader mode?