running latest cyanogen 5. I installed rom manager and flashed the clockwork recovery, which wouldn't work. I then tried to roll back to RA in the terminal, and no matter what i do, i get an out of memory error. I've cleared every cache, and deleted every file i'm comfortable with deleting in the system folder. I cannot get into any recovery console at all, so i can't even restore or flash another rom. What the hell do i do? I can't even hard reset. In addition to that, the drivers error out no matter what on my computer, so i can't fastboot usb.
I had a similar problem with Clockwork not working. However I was able to easily reflash RA recovery in fastboot. Perhaps try reinstalling your drivers and try fastboot again.
If you still have problems, you could always try another computer?
Same thing happened to me. Fastboot fixed it. Perhaps a second reason to not trust clockwork.
Bradart said:
running latest cyanogen 5. I installed rom manager and flashed the clockwork recovery, which wouldn't work. I then tried to roll back to RA in the terminal, and no matter what i do, i get an out of memory error. I've cleared every cache, and deleted every file i'm comfortable with deleting in the system folder. I cannot get into any recovery console at all, so i can't even restore or flash another rom. What the hell do i do? I can't even hard reset. In addition to that, the drivers error out no matter what on my computer, so i can't fastboot usb.
Click to expand...
Click to collapse
There is no need to open a new thread for something you can post in the CM5 thread.
firstly, wrong section - this belongs in QnA
secondly, in rom manager, at the bottom there is an option to install an "alternate" recovery image - Amon_RA 1.6.2
this takes a bit of time, so be patient
i had the same issue when i tried clockwork a week ago and couldnt get fastboot to work (no matter how hard i tried) when it had been working fine before that
moved to Q&A, best
If you want to remove rom manager and clockwork, try using the fastboot and use the command.
Fastboot erase recovery
and try to reflash the RA recovery.
Fastbot recovery nameofrecovery.
and see if it help's.
Related
I am running ClockworkMod Recovery, and when I updated to version 2.0.1.0 through Koush's ClockworkMod Rom Manager, my phone won't boot into recovery.
When I plug it in to my computer to run adb logcat, it says "FASTBOOT USB" in red at the top of the screen. When I type fastboot reboot, it says "rebooting..." but doesn't reboot. Any ideas?
IDK. Haven't tried that recovery. Have you tried to download from your computer and flash it on the phone. You might also want to try flashing Amon RA or Godspeed.
I went into ROM Manager and flashed an old version of ClockworkMod. That fixed it.
Have you tried Amon-RA? If so what's the difference?
&RoidRage said:
Have you tried Amon-RA? If so what's the difference?
Click to expand...
Click to collapse
ClockworkMod has a nice app that you use in Android to name your backups, flash things in folders other than root of sd, ecetera.
Like an idiot I wiped my System inside TWRP. Using TWRP 2.6.0.2
Earlier tonight my phone starting rebooting. I was inside GooManager and tapped reboot to recovery. When I did that, for some reason my phone lost root. Meaning when I went to reboot inside TWRP it stated that it looks as if my phone is not rooted. I rebooted anyway without installing SuperSU through TWRP. I was already rooted. Afterwards, it would boot up fine but kept constantly rebooting only after a minute or two.
I went back into TWRP and clicked through dalvik wipe and cache wipe. Still got reboots. I was planning on flashing CyanogenMod anyways so I thought I'd go on and wipe everything. I went in to advance wipe and check everything. As I swiped the slider to wipe I realized I checked System too, but it was too late.
Now my phone won't boot past the HTC logo with the red text underneath. I can boot into TWRP however so I hope all is not lost. I am currently at work so I have no way to try anything on the phone at the moment but was hoping for some advice on what to try later when I get home.
I'm thinking maybe I'll be able to use the "Mount" tab in TWRP to load a ROM on and flash and everything will be well again. Would I mistaken to think that? If not, I'll purchase an USB OTG cable and use a USB stick but I really need this up an running as quickly as possible.
Also, does anyone think it would be best just to go back to stock at this point (if I can) and start from scratch?
Much thanks for your help and advice,
dgb1891
So, oddly enough I did the same thing, How I managed to recover it so you can adb sideload a rom from TWRP and have access to a "working" phone again was to find your stock recovery.img, then flash it via fastboot, and then from the hboot menu, choose factory reset and let the stock recovery do it's thing, then reflash TWRP (I honestly like CWM doe) and adb sideload a rom (presumably what you were using before). It SHOULD fix your problem and you'll be able to mount files again.
hayame said:
So, oddly enough I did the same thing, How I managed to recover it so you can adb sideload a rom from TWRP and have access to a "working" phone again was to find your stock recovery.img, then flash it via fastboot, and then from the hboot menu, choose factory reset and let the stock recovery do it's thing, then reflash TWRP (I honestly like CWM doe) and adb sideload a rom (presumably what you were using before). It SHOULD fix your problem and you'll be able to mount files again.
Click to expand...
Click to collapse
By stock recovery.img you mean a stock HTC image? - or do you mean a recovery like TWRP or CWM?
dgb1891 said:
By stock recovery.img you mean a stock HTC image? - or do you mean a recovery like TWRP or CWM?
Click to expand...
Click to collapse
Literally stock recovery.img, not TWRP or CWM.
hayame said:
Literally stock recovery.img, not TWRP or CWM.
Click to expand...
Click to collapse
K. Thanks. I have a feeling this is going to be a bit more complicated than I first thought...
I followed what you suggested and got the phone back up and working. Thanks again.
I'm what you'd call a super noob at this stuff and I've got my poor little SP in a crazy bootloop... I've tried LITERALLY EVERYTHING the internet has told me to try; wiping every cache out there, flashing custom roms, stock roms, you name it. It began when I just got CWM (don't ask me why it happened then, I have no clue why) and this is even BEFORE I put a ROM on! (I was all ready to put a ROM after getting CWM but bootloop happened).
Note: I have CWM recovery, I think I have lost my stock recovery, if I try some ROMS (ex. CM 12) they give me this error 7, once I found certain ROMS (PACMAN ROM, unofficial stock ROM) that would flash and install, they did but still left me with a bootloop, I have tried wiping so many caches it's not even funny, I've tried flashing the original firmware, nothing works... so I'm here for help.
I have looked at every google link and every method possible in trying to fix this thing! I really can't afford a new phone and I just love this one too much... please help!
farahtasnim said:
I'm what you'd call a super noob at this stuff and I've got my poor little SP in a crazy bootloop... I've tried LITERALLY EVERYTHING the internet has told me to try; wiping every cache out there, flashing custom roms, stock roms, you name it. It began when I just got CWM (don't ask me why it happened then, I have no clue why) and this is even BEFORE I put a ROM on! (I was all ready to put a ROM after getting CWM but bootloop happened).
Note: I have CWM recovery, I think I have lost my stock recovery, if I try some ROMS (ex. CM 12) they give me this error 7, once I found certain ROMS (PACMAN ROM, unofficial stock ROM) that would flash and install, they did but still left me with a bootloop, I have tried wiping so many caches it's not even funny, I've tried flashing the original firmware, nothing works... so I'm here for help.
I have looked at every google link and every method possible in trying to fix this thing! I really can't afford a new phone and I just love this one too much... please help!
Click to expand...
Click to collapse
please state your current bootloader status. Is it unlocked or still locked?
TechnoSparks said:
please state your current bootloader status. Is it unlocked or still locked?
Click to expand...
Click to collapse
I have unlocked my bootloader. Thank you for replying!
farahtasnim said:
I have unlocked my bootloader. Thank you for replying!
Click to expand...
Click to collapse
Splendid! Knowing that your BL state is unlocked, this will make the whole process A LOT easier!
http://forum.xda-developers.com/xperia-sp/development/ubl-twrp-f2fs-support-xperia-sp-huashan-t3150230
Please go to the above link to get TWRP. Also, please keep in mind that TWRP is now the only still supported recovery around. CWM and PhilZ are both really outdated and no longer maintained due to the introduction of Cyanogen Recovery which is very minimal in features.
Once you get yourself the download, extract the files from the zip and get the twrp.img file. We will need this to flash into the boot partition of Xperia SP, granting you a direct boot into recovery once it is flashed. Please then copy the original zip to your sd card, as we will be flashing the original zip via TWRP later to give you access to TWRP in the future.
Using your preferred tool, flash the twrp.img file into the boot partition.
Connect your Xperia SP via fastboot. Make sure SP is shut down, hold volume up key and connect the SP with your computer.
If you're using a fastboot tool via command prompt, the command would be
fastboot flash boot twrp.img
If you're using flashtool, hit the lightning icon in the toolbar, select fastboot mode. Then select "Select kernel to flash". Make sure the file type is "img" else you won't able to find your TWRP img file. Navigate to mentioned img file and select it.
Afterwards, when flashing complete, you may insert sdcard and start the device. It will boot directly into TWRP as we flashed a recovery to the boot partition.
Clean wipe data, cache, dalvik cache, system. You may leave internal storage.
Flash the ROM zip you acquired (make sure file integrity is checked beforehand!) then the TWRP zip earlier. Flashing the TWRP zip grants you a persisting recovery, as explained in the linked thread.
You may now reboot and enjoy
Hey
I have got a kinda big problem. I wanted to factory reset my phone, because apps were not responding, force closing and I had a lot of apps installed (I am on B135), so I went in my TWRP 2.8.1.0 recovery and factory resetted. cache was unable to mount, so I only wiped data and rebooted. The same problem now occurs only worse.
I thought about the cache that might be causing this, but all attemts to wipe it (recovery, apps) failed.
I also thought I could flash the stock recovery again and force update the phone, but the 3 button method isnt working and (of course) I need the stock recovery
Someone please help
EdrichVerburg said:
Hey
I have got a kinda big problem. I wanted to factory reset my phone, because apps were not responding, force closing and I had a lot of apps installed (I am on B135), so I went in my TWRP 2.8.1.0 recovery and factory resetted. cache was unable to mount, so I only wiped data and rebooted. The same problem now occurs only worse.
I thought about the cache that might be causing this, but all attemts to wipe it (recovery, apps) failed.
I also thought I could flash the stock recovery again and force update the phone, but the 3 button method isnt working and (of course) I need the stock recovery
Someone please help
Click to expand...
Click to collapse
I would suggest that you install the latest twrp with flashify and then update your phone, because the newest twrp has the emui updater already built in, so you don't have to re-flash recoveries all the time.
Thanks Sproker,
One problem though. The lastest twrp does not seem to work because it is EMUI 3.0 and I am on EMUI 2.3?? I recently fixed it finally, but I still want to upgrade to EMUI 3.0... Is it worth it? And if it is, what am I to do?
Download the update.app (B135)
And extract the recovery.img
Now download ADB/Fastboot and the latest driver (HISiute).
Connect your phone with the computer and boot your phone into recovery mode.
Now boot into bootloader mode and search the device with "fastboot devices" if it is correctly connected, it should be displayed.
Now flash (first move the recovery.img into the ADB /Fastboot folder) the recovery.img you extracted before.
"fastboot flash recovery recovery.img"
Now you should have the stock recovery back on your phone.
But if twrp didn't work (erasing cache) the stock will also not work.
Try to erase cache via fastboot. But I don't know the code...
Hello, I've been trying to bring back to life this old XT1068.
In the past years, I had installed several ROMs until one day the phone stopped working (probably I made some mistakes like flashing something not supposed to be flashed on this device, probably) and since that moment if I turn it on it remains stuck on the boot animation (the coloured google dots moving...).
I tried everything. I have TWRP 3.1 installed, I tried to wipe everything, I tried factory reset, I tried to erase the internal storage, I tried to install new ROM, including a stock ROM and the stock recovery. The result is always the same: no errors at all in TWRP, but it's like nothing changes. It does not boot and if I go to TWRP I can still see files that I put in the phone years ago, after I tried every possible wipe. Imagine that I still see the WhatsApp folder of years ago.
As I already mentioned, I also tried to flash a stock recovery: the process finishes without errors but if I reboot to recovery, I always end up in TWRP.
The only thing I can do is to reboot into recovery or fastboot.
The phone is recognized by the computer ("adb devices" / "fastboot devices").
Does anyone of you guys ever experienced something like this?
Thanks in advance.
I have exactly the same issue. Did you find a solution?
I never got that problem, is pretty strange, i think some zip you flashed before is still installed automatically, for example, there is some option on supersu called survival mode, if you enabled that, i think an supersu uninstaller zip could work, also you can try to install any rom, install supersu and check on supersu settings
---------- Post added at 07:15 PM ---------- Previous post was at 07:14 PM ----------
Also probably some partition got damaged or anything, i recommend to flash an stock rom that flashes many things except for nvdata and nvram partitions because it could make you can't get signal if those partitions are from another zone
Get your device into fastboot mode and flash the stock IMG.
https://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
My device is also bricked of you are able to revive, can you extract mmcblk0.img of your device and share please
eagledipesh said:
Get your device into fastboot mode and flash the stock IMG.
https://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
My device is also bricked of you are able to revive, can you extract mmcblk0.img of your device and share please
Click to expand...
Click to collapse
Hello!
I`ve done the process to install via mfastboot the stock IMG, no errors at all. When the phone reboots it goes into the previous installed rom boot animation and stays there at bootloop.
I even tryed to install an updated TWRP recovery (3.4) via fastboot. Is shows "OK" but when it loads it is still the previous version.
It looks like the phone is "write pretected".
Any further suggestion?
Thanks in advance.
Allisson
Same problem here. I can accces the fastboot menu via "VOLUME DOWN + POWER" but whatever I try, the red error message comes up. I can boot into twrp via USB/PC but i cannot install it. I cannot factory reset.
when I reboot from TWRP I come to lineageOS boot loop.
ANY IDEAS?