Fixed the problem. Updated TWRP, enabled SU and root, re-flashed the boot image and re-installed the ROM. Did a factory reset and now the phone boots. I have a HTC One m8. Have unlocked the bootloader and installed TWRP. Tried installing crDroidAndroid-7.1.2-20170801-m8-v3.6.1. Didn't work out so well. Said it failed - unable to mount system. Then it rebooted and started to load but crashed at the CR Droid splash screen. Tried factory reset, various wipes. Don't know what to do next. Anyone have any ideas? Also, it won't turn off. just reboots.
Related
After rooting, I installed safe trap on my razr 912 CDMA, (no bootstrap).
1. Went to safetrap 1.0 recovery, data wipe, safetrap ENABLED and tried installing GUMMY 1.0.0 and gapps.
Tried rebooting but, after pressing the 'search button' key to start the ROM boot, it doesnt show anything , complete blank screen. rebooted few times, factory reset ,etc, didnt help.
2. Went back and DISABLED safetrap, which restored my initial copy of the stock, rebooted and it worked fine, my intial Stock ROM was up and running.
3. I doubted that this was issue with safetrap and not gummy installation; so to check that, I went to safetrap recovery, ENABLED safetrap. DID NOT INSTALL anything else.
Simply rebooted the phone, hoping the stock ROM to boot up since I did not install anything this time.
Result was the same...nothing on the screen....blank screen.
4. I went back and DISABLED safetrap and all was fine. Now stuck with stock ROM cant install new ROMS.
(I have no intention of trying bootstrap, because i did that on earlier Razr while installing Gummy 1.0.0 and it bricked the phone)
Question: it seems enabling safetrap, i am not able to bootup , no matter what. Any solution to this?
well I was flashing MIUI V5 UNIVERSAL - v. 3.7.12 for the 3vo and it got stuck in a bootloop. to try and fix it I tried to restore a backup and that rom played a little of the boot animation but then gets stuck in a bootloop. I also tried to wipe/format everything but, that didn't work. If a logcat would help i would appreciate a link on how to do that without being able to boot. I can boot to 4ext recovery. The cause could be that while flashing I selected the file to flash, I selected a file that didn't finish downloading. Thanks in advance for any help
Also if it matters my original rom was negalite blurom.
cdog1213 said:
well I was flashing MIUI V5 UNIVERSAL - v. 3.7.12 for the 3vo and it got stuck in a bootloop. to try and fix it I tried to restore a backup and that rom played a little of the boot animation but then gets stuck in a bootloop. I also tried to wipe/format everything but, that didn't work. If a logcat would help i would appreciate a link on how to do that without being able to boot. I can boot to 4ext recovery. The cause could be that while flashing I selected the file to flash, I selected a file that didn't finish downloading. Thanks in advance for any help
Also if it matters my original rom was negalite blurom.
Click to expand...
Click to collapse
I ran into your same problem today.
At the time my phone was on latest sprint firmware, ICS coolrom (latest rom and kernel) with hboot 1.58 unlocked s-off.
The steps I did preparing to install MIUI was
1) wipe data/factory reset from 4EXT
2) format all (except sdcard)
3) Install MIUI > chose mirage kernal
4) rebooted
after reboot it was stuck at the logo, at least I thought it was, let it sit for about 5 minutes.
Pulled the battery and tried steps 1-4 again.
Kept getting bootloop at that point. Boot splash -> logo -> reboot.
Next I tried flashing the latest mirage kernel from 4ext.
No luck, same issue.
Tried repeating steps 1-4 again.
No luck stuck in bootloop.
At that point I tried to run recovery from a backup I knew was working.
Wiped all data and format all -> selected recovery from 4ext.
Result: still boot loop.
At that point I tried changing bootloader to 1.58.58 jbear. and wiping/formatting all and trying recovery again from known working cool ics backup.
Result: still bootloop.
Switched back to 1.58 bootloader and tried fresh install of CoolICS rom. (I always wipe all data and format all before any rom change.)
Result: still bootloop.
At this point I was getting frustrated but I had an idea that the MIUI install when selecting mirage kernel may have messed up the partition size for the kernel since the mirage kernel states it must be flashed from the flash gui app first to resize the boot partition.
Next I downloaded pacman rom and attempted that install.
result: could not install due to wrong bootloader.
Next I downgraded bootloader to 1.50.50 jbear.
Wiped everything and retried pacman rom.
Install success, before starting the reboot from recovery, I received a message that the boot image has changed and will make a backup/format/flash the new boot image.
upon reboot I was able to successfully boot into pacman rom.
At that point I tried to wipe all again and install CoolICS rom again.
result: bootloop, but probably because of bootloader version. Did not fully test it as at this point I just wanted a working phone again and wanted to try out MIUI.
Rebooted to recovery and wiped everything again.
Installed MIUI using stock kernel option. This time on reboot I let it sit at the rom logo without touching anything. I think it restarted once on its own.
Result: Success. Phone working normally now. such a headache I am just leaving it as is for now.
Jeffjb said:
I ran into your same problem today.
At the time my phone was on latest sprint firmware, ICS coolrom (latest rom and kernel) with hboot 1.58 unlocked s-off.
The steps I did preparing to install MIUI was
1) wipe data/factory reset from 4EXT
2) format all (except sdcard)
3) Install MIUI > chose mirage kernal
4) rebooted
after reboot it was stuck at the logo, at least I thought it was, let it sit for about 5 minutes.
Pulled the battery and tried steps 1-4 again.
Kept getting bootloop at that point. Boot splash -> logo -> reboot.
Next I tried flashing the latest mirage kernel from 4ext.
No luck, same issue.
Tried repeating steps 1-4 again.
No luck stuck in bootloop.
At that point I tried to run recovery from a backup I knew was working.
Wiped all data and format all -> selected recovery from 4ext.
Result: still boot loop.
At that point I tried changing bootloader to 1.58.58 jbear. and wiping/formatting all and trying recovery again from known working cool ics backup.
Result: still bootloop.
Switched back to 1.58 bootloader and tried fresh install of CoolICS rom. (I always wipe all data and format all before any rom change.)
Result: still bootloop.
At this point I was getting frustrated but I had an idea that the MIUI install when selecting mirage kernel may have messed up the partition size for the kernel since the mirage kernel states it must be flashed from the flash gui app first to resize the boot partition.
Next I downloaded pacman rom and attempted that install.
result: could not install due to wrong bootloader.
Next I downgraded bootloader to 1.50.50 jbear.
Wiped everything and retried pacman rom.
Install success, before starting the reboot from recovery, I received a message that the boot image has changed and will make a backup/format/flash the new boot image.
upon reboot I was able to successfully boot into pacman rom.
At that point I tried to wipe all again and install CoolICS rom again.
result: bootloop, but probably because of bootloader version. Did not fully test it as at this point I just wanted a working phone again and wanted to try out MIUI.
Rebooted to recovery and wiped everything again.
Installed MIUI using stock kernel option. This time on reboot I let it sit at the rom logo without touching anything. I think it restarted once on its own.
Result: Success. Phone working normally now. such a headache I am just leaving it as is for now.
Click to expand...
Click to collapse
well I went to go try and boot P.A.C. and my phone just booted normally. So thanks for the help
Figured I'd post this here since I didn't get any other replies in the Nexus forum.
I have been trying to wipe my Nexus 7 (2012) clear but the wipe functionality doesn't appear to work.
I've been rooted on stock (using TWRP) but recently sideload 4.4.2 and removed root in the process.
OTA installed and I root was removed but recovery is now showing "no commands".
I have been able to get past that sometimes but not consistently and using the recovery wipe/factory reset doesn't do anything.
I tried to fastboot and do a wipe from the command line but that doesn't seem to be working either.
The device won't boot properly, it crashes after a few seconds once loaded and automatically restarts so I wanted to clean everything up and start fresh.
I tried custom temp recovery (since it's the only option available to boot from fastload) and while I can get into temp TWRP the wipe option doesn't do anything.
I also tried to reinstall the bootloading from the 4.4.2 image but that didn't help.
Any ideas what else I may be able to try?
Does anyone know what is wrong here? I wanted to get back to stock by flashing Amazon's stock .bin (changed to .zip) in twrp. I've done this before and had no issues. In twrp I wiped everything and then flashed the .zip. Then I booted into the Amazon OS and everything appeared fine. I'm on 14.3.2.5. For one, I cannot factory reset. After trying to do so, it reboots to the Kindle logo and just permanently hangs there. If I try to update it manually to 14.4.5.5, once again, it just hangs on the Kindle logo. It appears I have no recovery or something. What I don't understand is that I've done this in the past with no issue. Where I am now is that I am able to boot without issue into 14.3.2.5, but cannot update. What can I do?
edit: http://forum.xda-developers.com/showpost.php?p=55759790&postcount=204 fixed it. It restored my stock recovery and I was able to update and factory reset after doing it.
Hey all, so I decided to go from stock rooted to a custom rom, and see the progress since I last tried it and I encountered the following problem:
I formatted data and factory reset, and then I installed the custom rom, followed by the GAPPS.
Twrp rebooted every time I tried installing Gapps, so I was confused.
The following error occurred when before Aroma started:
"E:Legacy environment property did not initialize successfully. Properties may not be detected"
The next thing I did was I rebooted recovery, no cigar. I tried reinstalling the recovery, no cigar.
I tried formatting data again, and got the error that /data can't be mounted now. This started to worry me lol.
So I tried repairing it and then rebooting, and I tried updating to a newer TWRP but even there, the twrp version won't update. Its still the same number.
I'm too afraid to reboot and see if the rom boots or not, but when trying to flash even a stock rom ZIP it tells me the following:
"This package is for "Joan,h932" devices; this is a ""."
so twrp doesn't know what phone I have?
I am trying right now to restore my TWRP backup but it doesn't want to restore the data, so I'm trying without.
If you can help I would appreciate it very much!!
Here are the screenshots https://imgur.com/a/SLCPdIQ
EDIT: I finally figured it out. Hitting the reboot menu did nothing, because it was for some reason stuck and just rebooted into the same recovery version with the glitch.
I had to do a hard reset, and the finger dance again, and now everything is fixed.