Hoping someone here can help me fix this problem without having to RUU and start all over...
I'm S-On with 2.09 HBOOT.
I had been running MeanBean for the last 6 months or so, but decided to finally give an AOKP ROM a try because I wanted to check out HALO. First, I did a Nandroid backup of MeanBean using TWRP. Then I downloaded the latest DirtyUnicorns build, placed it in on my SD card and flashed through TWRP (2.3.1), inlcuding the attached GApps and the CM10.2 data fix. It wouldn't boot at first, and I realized that my old kernel for MeanBean was Sense-based, so wasn't compatible with AOKP. I extracted the boot.img file from the ROM and flashed using fastboot. After that I was able to boot up and was up and running with Dirty Unicorns on Mazda's supplied kernel.
DU is pretty awesome and there is so much to do in the ROM, plus HALO is awesome. I wish that was incorporated into every ROM. But my battery life the first couple of days left much to be desired. Even using Kernel Tuner to underclock with screen off and Llama to turn stuff off when I didn't need it, I was approaching 30% by lunchtime. So in an effort to try and fix this, I tried to flash the latest Haunted HC kernel (DU thread says people have flashed this and it runs) through Flash Image GUI since I am S-On. Unfortunately, the phone went into a boot loop after this and wouldn't get past the HTC screen. When I got home I reflashed the DU kernel through Fastboot, but then my WiFi wasn't functional.
After trying to flash a few times and it not working (WiFi still broken), I decided to just go back to MeanBean using the Nandroid. Used TWRP to do this, but then the phone wouldn't boot past the HTC screen after this. Was stuck at my girlfriend's and didn't have fastboot available, so I reflashed DU off of my SD card and it booted up and runs, but now I can't access my internal storage. This means I can't use Swiftkey and the Gallery app isn't functional either. When I try to mount internal storage in TWRP to reformat it, it just says internal storage cannot be mounted. Does anybody know how to fix this??? Everything I could find on here says that I should be able to mount using TWRP at least, but I can't even get that to work.
TLDR - Been flashing ROM's/kernels and now can't mount internal storage.
FIXED - Was able to use Rumrunner to obtain S-Off (had attempted while on MeanBean and would not work), then updated recovery to the latest TWRP and used the Advanced Wipe feature to reformat the internal storage. After that, I just reflashed DU and was up and running. Only issue I had was phone lost connectivity to Sprint, so I had to go back to MeanBean just to update my profile.
Related
I've been running Gingeritis for ages and decided to upgrade. My first choice was CM7, so I download it, throw it on my SD Card, boot into recovery, wipe everything then attempt to flash. I get no error message but when I go to reboot it stays locked on the HTC screen.
I've updated to the newest radio and am now running, or at least I think it flashed correctly, IMOSEYON (AOSP) leanKernel.
I've tried other ROMS and my phone won't take anything, it just stays on the HTC screen after giving me no errors during flashing.
Any help? I'm pulling my hair out over here.
Attempted a factory reset and wiped everything on the phone and nothing. It won't boot at all and there's nothing I can recover to now. Wonderful, am I screwed now?
Do u have a backup you can revert back to?
Not anymore. I cleared everything hoping to go back to stock, I think all I have left is a blank slate.
Update your recovery version.
How would I go about doing that?
What recovery are you using now? Then I will search for your latest version. The recovery can be in a PG05IMG.zip. Installation is the same as when you flashed the updated radios.
I'm on clockwork recovery, could that really be the problem not allowing it to fully flash the ROM?
Also, when I'm in recovery and trying to install these new ROMS they "finish" in less than 20 seconds...I know that's not normal.
OK. Thank you for letting me know your recovery. Latest version of clockwork is 5.0.2.1
ClockworkMod Recovery flashable from bootloader - xda-developers http://bit.ly/w0BGFZ
Phone: EVO 3D hboot 1.5
What happened: I've been running and liking ScottsROM's CleanRom Reborn. Today I decided to try a few things. I used the Flash Image GUI app to flash TWRP 2.0 recovery. All seemed well with that. I was able to boot into recovery and reboot back to normal with ease and no issues. So I decided to try one of the Kushdeck's ICS Alpha roms just to see what it was like (knowing I was going to go right back to CleanRom since the camera still doesn't work in the Alpha ICS roms). So I boot into TWRP Recovery and perform a backup. Once it's done I reboot and open the Flash Image GUI app and install (as per joeykrim's instructions on using this app) the Kernal from the new ICS Deck Rom then boot into TWRP recovery to install the rest of the rom. I'm up and playing with ICS in a few minutes and all is smooth. After playing in ICS for a while I decide to go back to my CleanRom (the one I backed up before starting any of this), so I reboot back into TWRP recovery and clear all my caches and dalviks and also perform a wipe. After that's complete I then chose the restore option and let it do its thing. Once that finishes (no errors reported when it finished) I rebooted. Usually when booting up on CleanRom it goes straight into the CleanRom Boot animation screen. However here's where my problem begins (continue below):
Problem: Instead of getting the CleanRom Boot Animation I get the white HTC screen/Green HTC logo and after that clears the screen goes black(but still backlit) and the capacitive buttons at the bottom stay all lit up but that's it. Nothing else happens. Tried going back into recovery and clearing all caches again and re-restoring again but it just did the same thing...
Any advice or suggestions as to what I should do next? I'm currently redownloading CleanRom Reborn (since I'm at work) and was going to just try reinstalling the rom again.
phone wont load after restoring a back up
this happen to me when i was running lee's rom and i decided to flash warm's rom and i used the g u i flash tool to flash the kernal and every thing when well then boot into recovery and to flash the rom and the flash went well also and it booted up and played around with it and decided i didnt like it and i went back to lee's rom and what do you know im stuck in a boot loop and then i found out that some how i lost my boot.img so im willing to bet you have lost your's aswell so what you have to do is what ever rom you flashed i hop you have a back up copy of the zip of that rom on your laptop or desktop and extract the contence of that zip folder and it will create another folder now with in that folder you will see a boot.img this is what you need to to get your evo to boot up you will need to copy the boot.img file into the folder that you used to root your evo should be on your c drive then open up camand promt and typ fastboot flash boot boot.img and press enter and you have your evo 3d back enjoy
I installed TWRP on my phone, and went into Bootloader an hit RECOVERY so I can get to the program (the first time I did this it brought me to the TMRWP program). THIS time, it completely wiped my friggin' phone... after I sat there like 4 hours re-setting up everything PERFECTLY how I wanted it.
What's weird is it kept ALL my apps that I converted to SYSTEM APPS, but all my user stuff is gone.
Lesson learned... Don't click recovery from Bootloader.
That has yet to happen to me with any recovery and 3 devices currently with twrp. Might be a step missed with the install or maybe you left a bootloader update zip and ran it when you rebooted? Or it can be a bug as going to recovery from bootloader via a cold start is how to get there traditionally. I would email teamwin and try to sort it out or redo the recovery install, making sure to check the md5 of the file after you download it.
Sent from my Transformer TF101 using Tapatalk 2
Your supposed to click recovery at bootloader. Thats where you do backup, restore and flash new roms.
HTC Sensation z710e
ICS 4.0.3
Sense version 4.0
Software Sense-o-maniac v1.3
Kernel. 3.0.30 Bricked
Radio 11.68.3504
That's what I thought too. If I'm not mistaking, I flashed the new firmware after I did the TWRP, so maybe that screwed it up somehow. I take it TWRP must be the LAST image you flash? Only flashes I remember doing were:
Customize bootloader screen
TWRP.
firmware update
Do I need to re-flash the new firmware before re-flashing TWRP, or is the firmware going to remain no matter what I do from this point on?
Just adb flash recovery. Put the recovery image in your platform tools folder. Adb reboot bootloader. when you are rebooted adb flash recovery recovery.img.
Or use one of the many tools made to do that on our forums
Sent from my ADR6425LVW using xda premium
Well I went ahead and used the GOO Manager to flash TWRP again, and this time it worked fine. I'm going to re-setup my phone again then before I customize it back like I had it, going to try to get to recovery and see if it works.
With it now being installed, does that mean I can't flash anything directly from SD Card or modify the bootloader anymore without it causing problems?
What I mean, moreso, is... if I ever put factory reset. will it reload the factory rom + keep the newest firmware I installed (etc.) or do I nee to back up the phone with TWRP and recover from that when I want to load it back?
Factory reset just puts things back to the way they were without the stuff in the data partition or any user apps or settings. This means that say you flash a custom rom, it will reset to as if that custom rom was freshly installed since the custom rom has replaced the factory rom in the /system/ parition and anything else related to it.
With that said it is usually a good practice after rooting a fresh device to do the nandroid and then transfer it to a computer before you do anything else. Note that while you probably won't be switching recoveries a lot, that nandroid backups generally work only with the recovery that generated them so don't get them mixed up.
I have CWM Touch recovery and Tachyon 1.1 installed. I decided to flash TWRP recovery by downloading the .zip from Flyhalf's thread (TWRP_2.6.3.0_Vigor_PH98IMG) and putting it on my internal SD as PH98IMG.zip (yeah, I know -- stupid idea).
Now when I reboot, the HTC screen comes up for a moment, the phone vibrates once and then powers down. At that point, I have to pull the battery if I want to try again. I can (after pulling battery) boot to bootloader from which I can still reboot to my CWM recovery, but I can't boot the phone normally. I assume this is because of the PH98IMG.zip on my internal storage?
What do I need to do to remove that file so that I can get back to "normal". I do not have a backup (because I was expecting to flash TWRP which doesn't use the CWM format for backups). I would rather not factory reset/re-format my internal SD unless that is my only option.
What are my options?
I've learned not to panic when I "think" I've done something terrible, but I am really starting to panic this time.
In CWM, when I go to Mounts & Storage, I am unable to mount anything except the /sdcard. I can NOT mount /cache, /data, /system, or /emmc. When I boot to HBOOT, I am unable to communicate with phone from PC.
Assuming I find a way to mount my SD card on my PC, could I copy a ROM to the external card, wipe/partition everything other than my card and re-flash the ROM to force re-formatting of all my partitions? Or should I begin trying to decide between the HTC One, Moto X and LG G2??
esmith818 said:
I've learned not to panic when I "think" I've done something terrible, but I am really starting to panic this time.
In CWM, when I go to Mounts & Storage, I am unable to mount anything except the /sdcard. I can NOT mount /cache, /data, /system, or /emmc. When I boot to HBOOT, I am unable to communicate with phone from PC.
Assuming I find a way to mount my SD card on my PC, could I copy a ROM to the external card, wipe/partition everything other than my card and re-flash the ROM to force re-formatting of all my partitions? Or should I begin trying to decide between the HTC One, Moto X and LG G2??
Click to expand...
Click to collapse
If you're now able to get into recovery, just copy a new rom over to the SD Card and install it. Worst case, if you're s-off, RUU your phone back to stock and start over with re-installing your recovery, restoring your rom.
The PH98IMG being on any internal or exteternal is not causing any problems for you on boot and would only be cumbersome when booting into hboot. It sounds to me that you should boot into recovery and clean flash a rom again. Even in recovery, you can mount either internal or external sd as usb storage and access it via your pc where you can remove or delete any file in them.
esmith818 said:
I've learned not to panic when I "think" I've done something terrible, but I am really starting to panic this time.
In CWM, when I go to Mounts & Storage, I am unable to mount anything except the /sdcard. I can NOT mount /cache, /data, /system, or /emmc. When I boot to HBOOT, I am unable to communicate with phone from PC.
Assuming I find a way to mount my SD card on my PC, could I copy a ROM to the external card, wipe/partition everything other than my card and re-flash the ROM to force re-formatting of all my partitions? Or should I begin trying to decide between the HTC One, Moto X and LG G2??
Click to expand...
Click to collapse
Get a rom on your sd card, whether external or internal and clean flash in recovery. fastboot flash the boot.img if you're s-on via rebooting to bootloader and doing it through fastboot
Thank you both for your responses. I tried to flash a new ROM from recovery but it didn't work; presumably because it could not write to /system, etc. Instead, I installed a RUU by following these instructions and flashed TWRP recovery as an img file with fastboot (extracted from here). As a result, I have a working phone, although it is ICS and Sense 3.6 -- blech!
My next question is: How do I upgrade to the latest HBOOT and radios? Although the CM 10.2 FAQ suggests following the above process to get the latest and greatest, the links provides HBOOT = 2.27.0000 and radios = 2.22.10.0801r; 2.22.10.0803r.
Second question: once I update HBOOT and radios, can I just reboot into recovery (via HBOOT) and flash Tachyon 1.1.5 or do I first need to partition/format mount points to prepare them for a 4.3 ROM?
I bungled my way through all these steps so long ago that I don't remember what hoops I had to jump through to get back to my "comfort zone" with Tachyon.
esmith818 said:
Thank you both for your responses. I tried to flash a new ROM from recovery but it didn't work; presumably because it could not write to /system, etc. Instead, I installed a RUU by following these instructions and flashed TWRP recovery as an img file with fastboot (extracted from here). As a result, I have a working phone, although it is ICS and Sense 3.6 -- blech!
My next question is: How do I upgrade to the latest HBOOT and radios? Although the CM 10.2 FAQ suggests following the above process to get the latest and greatest, the links provides HBOOT = 2.27.0000 and radios = 2.22.10.0801r; 2.22.10.0803r.
Second question: once I update HBOOT and radios, can I just reboot into recovery (via HBOOT) and flash Tachyon 1.1.5 or do I first need to partition/format mount points to prepare them for a 4.3 ROM?
I bungled my way through all these steps so long ago that I don't remember what hoops I had to jump through to get back to my "comfort zone" with Tachyon.
Click to expand...
Click to collapse
newest hboot and radios http://d-h.st/BIj ...place it in the main area of your external sd card and rename it and make sure it looks like PH98IMG.zip bot to bootloader by holding power and volume down after a battery pull to boot to it....this is the same method to get to a custom recovery to flash a rom bud...if s-on dont forget to flash boot.img outta the rom you are flashing
---------- Post added at 05:37 PM ---------- Previous post was at 05:30 PM ----------
also after you flash a 4.3 rom you have to format, partition and wipe internal sdcard and emmc
Thanks for the linkREV3NT3CH!! I scoured the web and found another link on XDA but it was broken.
I was able to flash the firmware update and install Tachyon 1.1.5 finally and now everything is back to "normal". Hope work doesn't mind that nothing got done today and I'll be stopping home to buy a microSD card reader for my computer after borrowing a co-worker's -- life saver!
I just booted up on the new ROM in time to hear the HORRIBLE low battery alarm. Not cool Neo; not cool at all.
esmith818 said:
Thanks for the linkREV3NT3CH!! I scoured the web and found another link on XDA but it was broken.
I was able to flash the firmware update and install Tachyon 1.1.5 finally and now everything is back to "normal". Hope work doesn't mind that nothing got done today and I'll be stopping home to buy a microSD card reader for my computer after borrowing a co-worker's -- life saver!
I just booted up on the new ROM in time to hear the HORRIBLE low battery alarm. Not cool Neo; not cool at all.
Click to expand...
Click to collapse
lol glad you got it working bud....once its charged tachyon has great battery life fyi
So, my phone ran out of power last night. I charged it up, but upon removing the charger, and booting into my main ROM (Stock-based, .200 or .232 I believe. AndroPlus' Advanced Stock Kernel with MultiROM support) the device bootlooped on the purple Xperia animation.
I left it on charge overnight, booting, and when I woke up, it was still on the same animation. I have MultiROM installed, through TWRP. I flashed a ROM (CM-based, 5.1.1 with the included kernel), and booted. It worked! But, if the Files app was opened, it would display nothing, internal or external SD. Sideloading ES File Explorer yielded similar results. Thinking it was a problem with the ROM, I flashed CarbonROM (CM-based too, I believe. Same version.) and similar things happened. However, TWRP can access both internal and my SD Card. I believe that no hardware damage has occurred.
So. Is it possible to fix my main ROM, or back up the data from it and migrate it to a new stock-based ROM? Thanks.
EDIT: I should mention that under available storage, both ROMs listed the correct amount of storage space, as did TWRP.
nothing broken in hardware, something is wrong with multiROM. Try to reflash kernel. If it won't work flash ftf rom via flashtool