[Q] Recovery + Cyanogenmod Somewhat corrupted - Verizon HTC One (M8)

Long story short, CWM is the only recovery that will open but will error saying E: cant open/mount cache/recovery.
Booting up, cyanogenmod will open, but now no wifi, no data, no nothing, every file manager errors out.
At this point, all I want to do it get all my pictures that are stored on the internal memory to the SD card and start from scratch. Is there any way to download the pictures using adb?
Thank you for your help

You can try adb pull if adb recognizes your device in recovery which it should
Sent from my HTC6525LVW using XDA Free mobile app

MotoTurbo said:
You can try adb pull if adb recognizes your device in recovery which it should
Sent from my HTC6525LVW using XDA Free mobile app
Click to expand...
Click to collapse
I tried going to the sdcard through adb it said it couldn't be found. the only time I was able to verify everything was there was through TWRP. I ended up doing a factory reset and flashed a new rom and thankfully the internal memory didnt get deleted. I flashed Viper 3.2.1, got everything set up, then I had to reboot and noticed it would take 2+ mins to boot. the HTC screen would be shown for that time and then the screen would be off, Id turn it on and the rom would be running. Thought it was the rom so I switched to GPE 5.0.1 which recommended i flash a new firmware for 5.0.1 which I did but still has the long boot issue.
This is what I have flashed on it so far
openrecovery-twrp-2.8.0.0-m8_wlv.img (latest 2.8.4.0 wont boot)
0P6BIMG.zip
GPE_5.0.1_MULTI_DH_011415.zip
Any ideas on how to fix the long boot issue?

So far what Im finding the solution to the 5min boot is to go back to your previous ROM which isnt a solution imho.
Im sure I screwed something up to cause this but haven't found a legitimate solution as of yet.

Fixed the 5min boot time by updating the hboot to 3.19

Yea you have to be on newest firmware or you'll experience long boot times
Sent from my HTC6525LVW using XDA Free mobile app

Related

[Q] Bricked Xoom?

So im running 3.1 rooted with the 1.4.4 Tiamat Kernel. I had this weird force closing issue where gapps would force close whenever i tried to connect to wifi. I powered down, turned on, and am now stuck in a boot animation loop. I can hold down the Vol Down button and it says "Starting Fastboot Protocol Support." but nothing changes. Is there anything I can do it fix it/turn it off until i get home to my computer with the SDK? On another note I did install the wpa supplicant (sp?) files to allow it to connect to an adhoc wifi source (eris tether). Please and thank you
EDIT: I have booted into recovery, but I am unable to mount any of the drive locations or wipe them. I did a factory data reset (as much as it could I guess?), but im still at the boot loop.
Hook it up to computer while its in fastboot and open a command prompt from the folder you have fastboot. Type "fastboot reboot-bootloader" and you should get adb to recognize, then push stock images or root images and recovery.
What recovery were you using? Did you flash the one from ROM manager?
I am using the CM from the ROM manager the latest one I think that it is version 4 something. does this make a difference? I have backups from my previous flash but when I tried to recover it won't take them. where can I get the root image? I might have it already since I rooted using adb, I will have to look on my laptop when I get home. Any other info you have will help. Thank you,,,,
razor532 said:
I am using the CM from the ROM manager the latest one I think that it is version 4 something. does this make a difference? I have backups from my previous flash but when I tried to recover it won't take them. where can I get the root image? I might have it already since I rooted using adb, I will have to look on my laptop when I get home. Any other info you have will help. Thank you,,,,
Click to expand...
Click to collapse
You will need to flash a good recovery, I suggest you you use the .img file in this thread through adb when you get to your laptop:
http://forum.xda-developers.com/showthread.php?t=1074979
The recovery version you updated to won't look at your external sdcard, so you can't flash from it until you re-install a good recovery.
Can't we get a pinned warning about this issue?
Thanks everyone, sorry for the delay. I ended up fixing it with a fastboot oem unlock command. However after countless flashes unable to get it to boot again i realized i was flashing the tiamat rom and then a different tiamat kernel boot.img, most likely the culprit in my boot loop. The minute i did a factory reset, updated cwr and only flashed the rom, everything works fine. Thanks for everyones help
Sent from my Eris using XDA App
So glad you were able to fix it!

Can't acces Recovery

Hey guys
I'm trying the whole time to accces recovery on the Moto G, but everytime I try this, the phone always reboots to Android. I tried Flashing CWM and TWRP, then it says in my fastboot flash mode: mismatched partition size. I never can go to recovery because it always reboots when I try to acces s it. And I want to install CWM or TWRP for flashing roms but nothing changes, the problem stays... Could anyone help me or has anyone also experienced this annoying problem?
Cheers
I will write a guide for it tomorrow. I don't have time right now.
Sent from my XT1032 using Tapatalk
When you flash cwm go straight to the recovery if you see a red sign with no command hold pwr+up for 2 secs it should boot into cwm
Sent from my XT1034 using xda app-developers app

[Help]Bricked my device.

God I'm stupid.
So I flashed a 4.4.3 theme on a 4.4.4 ROM, and I was stuck at the boot animation.
I went to recovery, found out I don't have any ROM's on my phone, so I figured I should flash through fastboot.
I downloaded the stock 4.4.4 image, tried to do the flash-all.bat, got an error.
I extracted the RAR inside it, manually flashed recovery, system, boot etc.
I can now only enter fastboot. Whenever I try to go to recovery or start the phone the screen just goes black, and all I can do is hold down the power button and restart to fastboot.
I sure hope you guys can help me, I don't have the money to buy a new phone
Drunkbag said:
God I'm stupid.
So I flashed a 4.4.3 theme on a 4.4.4 ROM, and I was stuck at the boot animation.
I went to recovery, found out I don't have any ROM's on my phone, so I figured I should flash through fastboot.
I downloaded the stock 4.4.4 image, tried to do the flash-all.bat, got an error.
I extracted the RAR inside it, manually flashed recovery, system, boot etc.
I can now only enter fastboot. Whenever I try to go to recovery or start the phone the screen just goes black, and all I can do is hold down the power button and restart to fastboot.
I sure hope you guys can help me, I don't have the money to buy a new phone
Click to expand...
Click to collapse
Do you know what error you got when you did the flash-all?
Sent from my Nexus 5 using XDA Free mobile app
Have you tried flashing stock 4.4.3 or even 4.4.2 completely in fastboot? Including recovery again??
jd1639 said:
Do you know what error you got when you did the flash-all?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I don't remember really, something about missing .sig files I think
KJ said:
Have you tried flashing stock 4.4.3 or even 4.4.2 completely in fastboot? Including recovery again??
Click to expand...
Click to collapse
I'm trying the Nexus Root Toolkit, and before that I managed to install TWRP 2.7.1.1 and boot to recovery.
However, I can't boot to the system.
I also downloaded 4.4.3 and going to attempt to flash it.
The missing Sig error is normal and nothing to worry about
Sent from my Nexus 5 using XDA Free mobile app
It's all fine.
Luckily a friend called me on Skype and I told him about my bricked device, he suggested to use NRT.
Thanks for the help guys!

Stucked in BooLoader

By mistake due to some problems I've accidentily deleted internal storage in the bootloader mode. Meaning that I can't get into android and I can't install any ROM (since i've deleted the storage). How does one fix this problem? How do I connect it to the computer and upload rom?
Ty
Moose321 said:
By mistake due to some problems I've accidentily deleted internal storage in the bootloader mode. Meaning that I can't get into android and I can't install any ROM (since i've deleted the storage). How does one fix this problem? How do I connect it to the computer and upload rom?
Ty
Click to expand...
Click to collapse
You can either push a rom to your device through a custom recovery using adb or flash the factory image. You also might be able to see your device when booted into recovery and copy and paste a rom to it.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You can either push a rom to your device through a custom recovery using adb or flash the factory image. You also might be able to see your device when booted into recovery and copy and paste a rom to it.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
More details pls :/ I cant just plug it into computer and upload it, it doesnt go into the system and it has that SD card issue :/
Well I’ve managed to make every turn possible with my hammerhead. I’ll just explain these turns as much as I can.
1. Unlocked the device
2. Installed ROM, everything was OK.
3. Applied different ROM, started having problems with SD card. Installed TWRP manager, problem fixed. Though there were some space issues (backup 6 gb and so on)
4. Made the worst turn, bootloader mode, deleted internal storage, wiped.
5. In turns on, goes into cataclysm rom, but the system doesnt show and Back buttons or minimize or Home (those 3 buttons at the foot of the phone), wallpaper is black. IF u connect it to the computer, the internal system is just EMPTY. Can’t transfer any rom to the phone. Cant go to the store and install TWRP manager. All kinds of crazy ****.
6. Tried Force flashing it with nexus root toolkit while in bootloader mode. Failed. Doesnt recognize the device, bootloader on the phone freezes.

Phone Keeps Getting Stuck In Recovery

My phone is rooted and still running 4.4.2 with bloat removed. The other day I decided to install TWRP Manager and upon opening it up, it gave me an option to install TWRP v2.8.5.0. So I installed it and my phone would not boot back up, just stuck in TWRP. So I found this zip file LG_G3_Flash2FixStuckRecovery.zip on XDA that allowed my phone to boot back up. But now at least once a day it reverts back to TWRP and is stuck there until I install the zip again. Anyone know how to stop it from doing this?
Ive been having similar issues with my d852 and find it helps bigtime to stay away from the newest versions of twrp until they are bug free. I installed 2.8.6 yesterday and my Phone would not restart at all or it would do what yours is doing. I'm not saying that it is definitly a TWRP issue, but I am saying that once I installed 2. 8.4 the issue was gone completely. If you try going back a couple updates to an older version and it helps let me know as I'm kind of curious
HOW did you get into recovery. I got 2.8.6.1 & I do the power + vol down button thing and it doesn't take me to recovery.
Sent from my LG-D850 using xda premium

Categories

Resources