[Q] No Custom Recovery Will Load - AT&T HTC One (M7)

I was using CWM 6.0.4.3 to flash Android Revolution 52.0. When I rebooted the device after the install, the CWM would not load and it just bootlooped with the HTC dev screen.
I tried to load TWRP, bootloop.
I tried Philz, bootloop.
I cannot access and recovery to completely wipe the phone and start over. I tried using fastboot command to erase the phone and am getting a remote not allowed. Am I screwed?
Any help is totally welcome.

Solution
I was able to fix the issue.
In CWM, I was able to use the command
fastboot erase cache
When I restarted the recovery, I was able to restore a backup I made just before trying to install AR 52.0.
Also interesting note, I seem to be having an issue with Sense-based ROM's now. AR used to run solid on my device, I had issues with 51.0 having Sense crash and even Viper 5.5 was having problems with the Hub crashing and not responding.
Not sure why but just saying.

Related

Unable to boot Android

This all started when I was wiping in CWM before flashing a ROM and I seemed to have misclicked something. It resized a partition I think I recall it saying, but I proceeded to install the ROM afterwards. The rom didn't boot, but I was still able to access CWM so I flashed a recovery I had made. I was able to boot into it but the touch screen was horribly off and made it unusable. I spent a while wiping then tried a few different roms to start from scratch. The Boot logo had disappeared and a menu had taken it's place.
I eventually pulled up fastboot and wiped everything. Everything on the phone is wiped and it is now unusable, HOWEVER fastboot is working perfectly and I can flash files from there.
What do I do from here to get my phone back into a functional state? I really need some help here...
Taz3rburned said:
This all started when I was wiping in CWM before flashing a ROM and I seemed to have misclicked something. It resized a partition I think I recall it saying, but I proceeded to install the ROM afterwards. The rom didn't boot, but I was still able to access CWM so I flashed a recovery I had made. I was able to boot into it but the touch screen was horribly off and made it unusable. I spent a while wiping then tried a few different roms to start from scratch. The Boot logo had disappeared and a menu had taken it's place.
I eventually pulled up fastboot and wiped everything. Everything on the phone is wiped and it is now unusable, HOWEVER fastboot is working perfectly and I can flash files from there.
What do I do from here to get my phone back into a functional state? I really need some help here...
Click to expand...
Click to collapse
Have u tried these fastboot commands
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
Okay, I've done that and then I flashed CWM Recovery through fastboot. I then booted into CWM and flashed the jokersax's CM9 ROM and rebooted. What I still get is:
No OS detected, going to RSD mode in 5 seconds
Press a key to stop count down
Available Modes are:
1 RSD
2 Fastboot
3 NvFlash
etc. etc.
It isn't detecting an OS still, and I don't get a boot icon just that menu. What would you suggest?
I'm thinking of trying this: http://forum.xda-developers.com/showthread.php?t=1421522
Taz3rburned said:
This all started when I was wiping in CWM before flashing a ROM and I seemed to have misclicked something. It resized a partition I think I recall it saying, but I proceeded to install the ROM afterwards. The rom didn't boot, but I was still able to access CWM so I flashed a recovery I had made. I was able to boot into it but the touch screen was horribly off and made it unusable. I spent a while wiping then tried a few different roms to start from scratch. The Boot logo had disappeared and a menu had taken it's place.
I eventually pulled up fastboot and wiped everything. Everything on the phone is wiped and it is now unusable, HOWEVER fastboot is working perfectly and I can flash files from there.
What do I do from here to get my phone back into a functional state? I really need some help here...
Click to expand...
Click to collapse
1. Re: CWM wipe and spazzed out touch screen: Sounds like you erased your PDS partition. If you made a back up, flash it. Otherwise search for a thread titled PDS Partition Fix (or something similar) here in the Q&A section for an alternative fix.
2. I don't recall if doing the PDS fix will also fix the missing boot logo. If not, you can find a stock replacement in the Themes section. You're looking for logo.bin.
That fixed it, thanks! I did a full wipe of those partitions then restored from my CWM restore. That didn't fix the screen but I tried that fix you suggested and everything is perfect now. Thanks for the help.

[Q] TF201: No ROM works past boot animation

So, I was able to successfully unlock my bootloader, got TWRP 2.6 on it, and put a few different ROMs on my machine; however, I have yet been able to install a ROM and get it to move past the boot animation.
I have tried the latest nightly ROMs for CyanogenMod 10.1 and 10.2 for my TF201, both of which get stuck in CM's boot animation. I just tried the same with the newest Baked ROM, only to be stuck in its boot animation as well.
I'm trying to figure out if there was something I forgot to do. I have been able to revert to a backup of my stock Jellybean 4.1.1 that I stored using TWRP, but haven't been able to use anything else.
Are there any thoughts on this? Have I missed something? I was able to use the unlocker utility and each boot offers the confirmation in the top-left that my bootloader is unlocked. I am able to enter TWRP from the recovery mode. Shouldn't it be as simple as selecting a ROM's zip archive and installing it from TWRP?
Have you done a full wipe before installing, including cache and dalvik cache partitions?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Try installing twrp 2.5. AS I just read in another thread there are problems with 2.6..
Sent from my MB526 using xda app-developers app
Factory reset
After flashing CM 10.1 nightly last night i had the same issue. I booted into my recovery console (flatline cwm) and performed a factory reset. This seemed to clear whatever issue was bothering the tablet. Still sat there for about five minutes on the animation after the reset but then progressed into setup.
Doubt if it makes a difference but mine was connected to the dock too.
If you're still stuck the method that worked for me yesterday was:
Used Flatline CWM as the recovery, installed using fastboot
Used an external memory card to copy the relevant zip files to my sdcard, recovery couldnt find them otherwise using adb push
Installed from zip using Flatline CWM
Installed gapps using Flatline CWM
Booted, got the issue you had
Booted into recovery, performed a factory reset
Told recovery to restart the machine
Booted into setup screen after loading for a few minutes

[Q] issues wiping Nexus 7

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?

can't do anything with the recovery

My sisters DNA is running a sense rom of some sort. She wants to go back to completely stock BUT can't flash stock rom because twrp won't mount cache, dalvic, or data to be able to wipe anything. says unable to mount... Forrmat data doesn't work. nothing. I think mounting system and wiping it works but when you reboot the phone the system is still there. I tried flashing the rom on top but it gets few seconds in and it reboots the phone. Can't RUU because when program says waiting for bootloader, it tries to boot into bootloader but actually reboots the phone. Then RUU says connection failed. Adbing or fastbooting into bootloader or recovery just reboots the phone. Can't flash new recovery neither. It says flashing the recovery was successful but recovery or version of it doesn't change. Also for some reason Twrp is a bit laggy.
I'm running out of ideas here. The current rom she's running is lagging and causes issues after months of using it. How can I get back to stock?
Can anyone help please?
Ndaoud360 said:
Can anyone help please?
Click to expand...
Click to collapse
If its rebooting the phone and not into bootloader, the first things to check are: Make sure you're using the HTC cable, try a different usb port, and make sure you have all the correct drivers installed. Easiest way is to install htc sync, and then uninstall, It will leave the drivers behind and remove the sync software.

Xiaomi Mi 9t wont load any custom rom or restore backup

hey guys just looking for some help. ive been modding and flashing phones from 2014, but its always gone really smoothly, so my diagnostic ability is lacking.
it started with flashing twrp. my bootloader is unlocked, usb debugging on, device is showing in adb and fastboot, and i can flash twrp without any issues. hoowever when i go to boot twrp, only the stock recovery boots. i tried to flash twrp using the XiaoMiTool v2, but the same thing happened. i eventually got around this by just booting twrp instead of trying to flash it. so i got in, took a full back-up and started installing a custom rom.
the first one i tried was ParanoidAndroid Quartz. i wiped cache, dalvik and storage then transferred it to my phone, tried to flash and got "zip verification failed". so i turn off zip verification and tried again. it flashed perfectly with zero errors. however, when i reboot the phone it would only boot to stock recovery and not twrp (expected) or the new rom. i tried that a few times, then tried LineageOS, and MSM Xtended 10. all of them had the same issue, the flashed without a hitch, then wouldnt boot.
i also tried flashing a new fw-vendor and it just straight up failed. Then i decided to cut my losses and restore my twrp backup, and that came back with the error, "extractTarFork() process ended with error: 255"
Software before i began these attempts was completely stock, so i dont know what is going wrong, but as of now, my phone is bricked, i cant install a new rom or restore my back-up.
any help is appreciated guys. thanks
You can figure out this problem with
1 Copy backup folder to computer
2- Format Data - Yes , Wipe Everything
3- Install ROM that you have installed before and boot
4- Go to TWRP, format data yes reboot recovery
5- Paste backup folder to internal storage and restore

Categories

Resources