[Q] Help -Fully Rooted and Can't Flash Custom Rom - EVO 4G Q&A, Help & Troubleshooting

I've been rooted since summer and when I flashed from Frost to VaelPak, it wouldn't go. I couldn't restore a nand backup either. It just stayed in a bootloop. I've also tried Fresh and Ava-Froyo. I've had all these working in the past. The only think I can flash is myn-OTA_Supersonic_3.29.651.5-DEODEXED. I've unrooted and re-rooted twice with no change in behavior. I have full root with nandroid. Anyone with a clue? I've been searching for similar problems without any luck.

Are you clearing system data and all caches between flashes? Also, questions should go in the appropriate forum.

Wrong thread. This belongs in Q & A.

System, cache and dalvik caches are being wiped each time. Mods - move this as needed if this is not the right forum.

Related

CM7 Stuck in Bootloop

Edit: Still not fixed. Any help would be appreciated.
Hi all. I'm currently using MIUI and want to swith to CM7 for 2.3 and 4G. I've been on the Cyanogen forums but to no avail. I have so far tried the following...
1. Flash from MIUI to CM7 #8 through rommanager with wipe.
2. Flash from MIUI to CM7 nightly 8, 12, 17 through Clockwork with full data and cache wipe.
3. Flash from MIUI to CM6 to CM7 through clockwork w/ full wipe.
4. Flash Amons recovery in rommanager and flash from MIUI to CM7 nightly 17 w/ full wipe.
I am currently at a loss. Please throw any suggestions my way.
- Nick
What exactly are you wiping when you say full wipe?
Try flashing calkulin's format_all.zip, then cyanogenmod, then gapps, all within one recovery session (no rebooting/restarting between flashing each one)
Sent from my hand with XDA Premium installed
Try a full wipe, cache, dalvik, and data. Then reflash the rom.
By full wipe I mean data/factory reset, then wipe cache, then dalvik.
Trying Calkulin now. On Cyanogen forum someone suggested a different kernel. I've never flashed only just a kernel. Would I use the same method as flashing other zips?
That's correct, just wipe dalvik and cache before doing so.
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
I use amon RA recovery and when I was stuck in a boot loop I would wipe data/factory reset, cache, dalvik cache, as well as wipe the system. That did the trick for me. Best of luck!
PS. Not sure of you can wipe system via clockwork mod, I used it briefly before I got aggravated and flashed a better recovery img IMO.
hTC Evo CM7-n17
You can do a full wipe in clockwork:
factory/data reset, and wipe cache from the main screen, then navigate to advanced and then wipe dalvik cache.
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
deaconzero said:
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
Click to expand...
Click to collapse
Well amon_ra isn't the answer. I've used clockwork and had ZERO problems, and still use it. But if you think titanium is your issue, go into it, and click problems, and it'll download the busybox and correct itself. And if you think the kernel may be the problem, it could be, so go for it. Just make sure to use an aosp kernel on an aosp rom, and the same for sense; don't mix them.
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
deaconzero said:
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
Click to expand...
Click to collapse
Well I would try the a froyo savaged zen kernel. They all play nice from what I hear.
No fix yet even after switching kernels. I found this link when I was looking up more info http://www.shahz.net/android/what-is-dalvik-cache.html and this section interested me.
"This dalvik cache can grow immensely huge as more applications are installed on your phone. It is safe to wipe dalvik-cache. It will be rebuilt again when the phone boots. This also explains why your phone takes ages to start up for the first time. As for my Nexus One, having about 145 applications installed, it takes about 13 minutes to build the cache"
Could this be what's going on? Is the dalvik cache being rebuilt and I'm not actually getting a bootloop? Do I need to let the blue arrow circle around the skating android for 15 minutes?
Still not working. Tried the kernel switch and the above idea of letting the boot screen run for over 20 minutes. Nothing.
Anyone w/ any thoughts?? Thanks.
Are you flashing the new kernel the same time you flash the rom. What you should do is wipe everything, factory/data, cahe, dalvik cache, then flash the rom. Give it a couple of minutes to boot up. After it eventually boots up, back it up, then flash the new kernel, just wipe the cache and dalvik before you do so.
deaconzero said:
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
Click to expand...
Click to collapse
Restoring system data through Titanium Backup is almost a certain recipe for disaster - especially when switching between different ROMs. Use TB only to restore user apps, and the data associated with only those apps.
The other thing you may want to try is to repartition/format your SD card. Make sure you back it up to your computer first, then use whatever recovery (I know Amon Ra will do it, think CWM will too) to partition and format the SD card. This helped me out when I was getting bootloops...
Good luck!
BigJohn

[Q] Camera flash not working with Synergy RC1

I'm sorry if this has been asked before but I tried searching multiple times and couldn't find anything about this. I just recently flashed my phone following the directions from the developer and the only major issue that I know of is the camera flash will not work when taking a picture in low light. I also tried the "flashlight" app and that also won't turn on the light either. Before I try re-flashing the ROM, is there anything I can try before? Thanks for the help...
I can assure you that it is NOT the rom, unless, of course, you have a corrupt download. My camera flashes like it is suppose to and my flashlight turns on and i am currently using the Synergy RC-1 rom. You can try rebooting into recovery, wipe cache & dalvik and then re-flash Synergy atop your current install.
posting & replying via my EVO 4G
Thanks for your help. I hate to re-flash after configuring the layout the way I like but if that's what it takes then I'll do that.
mexag05 said:
Thanks for your help. I hate to re-flash after configuring the layout the way I like but if that's what it takes then I'll do that.
Click to expand...
Click to collapse
If you're going to reflash the same Synergy rom then go into recovery, wipe cache & dalvik and then make a nandroid backup of only your data as well as android.secure & sdext partitions. (If you do not have any apps saved on the android.secure [usually paid apps] and/or the sdext partition then disregard including them in the backup). Afterwards, flash the Synergy rom, boot to your homescreen, and then clear all of the default widgets from your homescreens. When you're finished, reboot into recovery, wipe cache & dalvik then restore the backup that you made of your data, android.secure & sdext, if applicable. Whe the restore it complete, boot to your homescreen. You will find them as they were in the previous installation of the rom.

[Q] Flashing a ROM help.

I am not new to this, I have experience with rooting htc and samsung devices. I have also searched, and searched, and searched with no luck on this.
However, I am stumped on this phone. I am using ODIN to flash the S/U script, I can gain root, install CWM and install it. I can load a ROM but one of 2 things happen: when I boot it up I get stuck in a boot loop, or it won't even install in the recovery.
I have a few questions / statements:
WHY am I getting stuck in this boot loop?
I am wiping cache/dalvik before I install the new ROM.
I am installing the ROM on the SD card vs the internal memory, is that why?
I got stuck 3 times in the boot loop, and I have had to use ODIN to flash my phone back to stock to start over.
Thanks in advance for the help.
If you have searched, and searched, and searched you would have realized that this is not development related.
for someone who's been around then, you should first off know that this belongs in q&a, not development.
that being said, which recovery are you using? i don't think that's your problem but a little more info would be helpful. also, which rom are you trying to use? when you're wiping, try using this, it'll wipe everything necessary. you only mentioned wiping your cache's so maybe that's it? in any case, flash the file i linked, then your rom. check the md5 on it and make sure it's a match. after you reboot, let your phone sit for 10 minutes and hopefully all will be well.
http://www.youtube.com/watch?v=JmvCpR45LKA
Mercuri82 said:
I am not new to this, I have experience with rooting htc and samsung devices. I have also searched, and searched, and searched with no luck on this.
However, I am stumped on this phone. I am using ODIN to flash the S/U script, I can gain root, install CWM and install it. I can load a ROM but one of 2 things happen: when I boot it up I get stuck in a boot loop, or it won't even install in the recovery.
I have a few questions / statements:
WHY am I getting stuck in this boot loop?
I am wiping cache/dalvik before I install the new ROM.
I am installing the ROM on the SD card vs the internal memory, is that why?
I got stuck 3 times in the boot loop, and I have had to use ODIN to flash my phone back to stock to start over.
Thanks in advance for the help.
Click to expand...
Click to collapse
If you look in the darkside rom thread, and some of the other rom threads, you will see three recommended wipes: darkside super, kernel and darkside cache. I would suggest you do all three.
Sent from my SGH-T989 using xda premium
Here is a big problem as well. You wipe cache and dalvik AFTER you flash the rom. I usually do it before as well but always after. That's like wiping before you **** and not cleaning up after
Sent from my SGH-T989 using XDA
odin version
jabberbox said:
http://www.youtube.com/watch?v=JmvCpR45LKA
Click to expand...
Click to collapse
I used an old version I couldn't get the latest one to work. But it wouldn't even load for me. It been a min sence ive used odin. But my replacement phone is at the house I'll pm you the steps I'll take. Everyone else try to be nice even if you think the question is stupid. Try to show some love
sorry i read wrong. i thought you couldnt gain root. as far as boot loops follow darksides wipe method it work. as far as my replacement phone rooted after first boot. my usb port is broke on my old phone
anyone know how to get back to stock with out it?
sence we are asking crazy ass questions?
dam auto correct
Questions go in the Q&A section
To those of you who helped by answering my question, thank you.
To those of you who told me I posted in the wrong sub section, get over yourself. Especially the guy with 13 posts.
I am wiping cache/dalvik before and after.
I am using CWM from the market, so it should be the newest version.
Ill check out the darkside thread.
You really don't need to wipe dalvik cache after a fresh rom install, unless you didn't delete the data partition (wipe data). And you certainly don't need to do it before and after.
Wiping cache and dalvik cache is really only useful if you make changes to the system but don't want to format the data. This includes flashing themes, and other enhancements, because most of them are replacing system files. On your first boot the dalvik cache gets built. (This is why a lot of devs recommend letting it sit for a bit before using it, it's giving it time to build the cache.)
The reason they tell you to wipe dalvik cache is let's say you're installing a theme, and it replaces systemui.apk and framework-res.apk, located in the system partition. The dalvik cache is already built for these files, so in some cases if you don't wipe the cache you'll boot loop. When you wipe dalvik, you are letting it be rebuilt with the current files.
Also, while we're on the subject, another misconception I see alot of, you don't need to wipe the dalvik cache after you wipe data. Dalvik cache is located on the data partition, it's a folder there. If you wipe the data partition, you've already removed it. (Not to be confused with cache partition, which is used for different purposes. That is it's own partition.)

[Q] Cant mount data, unable to restore

First time to post here, but have gotten a lot of useful info from you guys. I'm kind of a noob at all this, but here it goes. I've been flashing the CM nightlies and haven't had one issue. I flashed to the new version yesterday, and everything seemed to be going ok. I went it and attempted some kernel tweaks via Pimp my Rom, and things went crazy. I started getting Process.acor. errors, and a multitude of others, then it shut down. I rebooted into recovery and wiped cache, davlik, factory reset, and wiped system..flashed my twrp restore and waited...it restored the system files, but did not restore the data or boot files...I assume that somehow the data partition has been changed to read only...How do i change that back to RW?

[Q] Help with People's ROM v3.1 on Sprint GS3

Hello, all,
Apologies if this is a noob-ish question, but I could really use some assistance here. After installing kennyglass123's People's ROM v3.1 without incident, upon reboot, I get stuck in the boot screen (in this case, the black and white spiral). Only solution--that I know of--is to restore from nandroid backup to get back to previous ROM.
Is there some sort of app conflict that I'm coming up against? I ask because I had previously, successfully installed it back in early Feb, and it worked great, and then after a reboot after some app updates, it got stuck.
Love the ROM...want to get it to work again!
Appreciate it,
For faster help, you should post this queation in the peoples rom thread.. For now if you want to try and fix it do this.. I wipe cache, delvik cache, factory reset, and system. Flash rom agin, wipe cache again, reboot.. Remember it can take a while for the system to fully boot..
Yes, as said above, make sure you are wiping EVERYTHING. The system can take long to boot as well depending on how large the OS you flashed is. Additionally, multiple wipes dont hurt either, especially if you are flashing a different android version (ICS to JB)
Make sure to always format system, clear data (might say factory restore), clear cache, and clear dalvik cache (rinse and repeat to be safer), then flash your rom of choice
Sent from my PG06100
As everyone above stated, make sure your doing a complete clean install. TPR uses Aroma Installer and make sure you make all the right selections, and choose a kernel during the whole process.
Transmitted with a portable device using Xparent Blue Tapatalk 2
peajul said:
Hello, all,
Apologies if this is a noob-ish question, but I could really use some assistance here. After installing kennyglass123's People's ROM v3.1 without incident, upon reboot, I get stuck in the boot screen (in this case, the black and white spiral). Only solution--that I know of--is to restore from nandroid backup to get back to previous ROM.
Is there some sort of app conflict that I'm coming up against? I ask because I had previously, successfully installed it back in early Feb, and it worked great, and then after a reboot after some app updates, it got stuck.
Love the ROM...want to get it to work again!
Appreciate it,
Click to expand...
Click to collapse
Been running TPR since the OG days.. As with flashing ANY rom, Do a Full data wipe, cache clear, dalvik clear (couple times if you prefer) make sure you select a kernel in the Aroma process. Should be back in business. Always can post in the TPR thread for most help available tho, The People are always ready and willing to help out where we can! Let us know if there is anything else that happens.

Categories

Resources