Develop Bugs

Reboot Loop in Fresh 3.0.1.2 Any suggestions?

My phone is just rebooting to the Fresh boot animation over and over again. Here is what I've done.
I did a full wipe (3 times), cleared storage in recovery, wiped dalvik cache, pulled the battery, fastboot, wipe cache partition, wipe data/factory reset in recovery and nothing works. I'm using Clockwork Recovery v2.5.0.1 and I rooted via this method for mac:
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/17766-how-full-root-evo-4g-mac.html
I'm pretty sure half the **** I did was not necessary but I had to try something. Any ideas on what to do next?

Usually clearing cache/dalvik works... And you've wiped everything else... Have you checked the MD5 of your ZIP that you're flashing from? Or tried a different ROM?
Furthermore, have you just let the phone sit for a bit? The first boot after wiping cache can take quite a while.
EDIT: Also, did you do NAND unlock/eng hboot when you rooted?

I never did a nand backup. What would happen if I nand backup while having these problems? How do I check MD5?

I'm a bit confused at what you're trying to do here...but maybe this will help.
Factory reset/data wipe does not wipe your /system/ which is where most/all of the core files are stored for any ROM.
You could trying doing a logcat from adb to maybe get a better idea on what is causing the bootloop.
Or a broader approach would be to just flash Fresh again and it will overwrite anything in /system/ and whatever files, or lack thereof, that are causing the bootloop issue will be added/overwritten.

Well doing a Nandroid backup of a broken ROM won't do you any good.
As for MD5, you should be able to open adb shell, then use the "md5sum" command to get the MD5 of the file. For example:
Code:
adb shell
md5sum /sdcard/some_rom.zip
You can then compare the MD5 it outputs with the MD5 posted by the ROM maker. If they haven't posted an MD5, you might want to re-think about using that ROM, and the competence of its creator. For example, CM6 Nightly has the MD5 posted in a text file in the same directory as all the ROM zip files for flashing. Amon RA Recovery has the MD5 posted in the OP of the thread, etc.

Philosuffer said:
I'm a bit confused at what you're trying to do here...but maybe this will help.
Factory reset/data wipe does not wipe your /system/ which is where most/all of the core files are stored for any ROM.
You could trying doing a logcat from adb to maybe get a better idea on what is causing the bootloop.
Or a broader approach would be to just flash Fresh again and it will overwrite anything in /system/ and whatever files, or lack thereof, that are causing the bootloop issue will be added/overwritten.
Click to expand...
Click to collapse
What I'm trying to do is get my phone to work again. Here's what happened:
I downloaded this Rosie Clear Taskbar zip file that I found in the Themes section and flashed it. It looked horrible and was showing distorted so I figured I'll just reset my whole phone and get rid of it. Well it didn't work and it put me in a boot loop. I have no idea how to do a logcat and I'm pretty much new at this unless you post instructions I can adb with my mac. I need my phone today because it's my daughters birthday and people are going to be calling me left and right for details on the party. My phone just keeps rebooting at the Fresh boot. I can enter recovery just fine:
Is there a command I can do in adb while in recovery to make it ''safe boot''? How do I flash Fresh again?
Is re-flashing the ROM as easy as me taking the downloaded Fresh Rom.zip, placing it on my SD and flashing from recovery? I don't want to experiment and possibly mess everything up. Thanks.

It's that easy
gqstatus0685 said:
...
Is re-flashing the ROM as easy as me taking the downloaded Fresh Rom.zip, placing it on my SD and flashing from recovery? I don't want to experiment and possibly mess everything up. Thanks.
Click to expand...
Click to collapse
Yes, it's that easy.
I'm not a big fan of how Clockwork wipes, I prefer Amon_RA, where you know you are wiping dalvik cache. Still if you are reinstalling Fresh 3.1.0.2 do a complete wipe.
Once you have your phone operating, immedaitley make a nand back up, or in Clockwork a nandriod. You can then always have a working base to go back to if something isn't playing nice.

Jim M said:
Yes, it's that easy.
I'm not a big fan of how Clockwork wipes, I prefer Amon_RA, where you know you are wiping dalvik cache. Still if you are reinstalling Fresh 3.1.0.2 do a complete wipe.
Once you have your phone operating, immedaitley make a nand back up, or in Clockwork a nandriod. You can then always have a working base to go back to if something isn't playing nice.
Click to expand...
Click to collapse
When Clockwork wipes data it deletes the entire folder, which happens to contain the cache and dalvik folders. There's absolutely nothing wrong with that.
And OP, you might want to wait for Fresh 3.2. Just came out for donators today. I'm using it right now.

Apparently in my case it isn't as easy as flashing from the zip. I downloaded the ROM from geekme and put it on my SD card. Flashed it and even though it was successful I still get boot loop. Could it be because I accidentally did a nand backup of the problem?
What else could I do. I'm using Clockwork but is there a way to flash the other recovery through ADB even though my phone won't boot.
I can't take this to Sprint as it's rooted and showing the Fresh boot screen.

I had the same problem. Turns out I had the wrong kernel flashed from a previous rom. I had constant reboots, couldnt access my sd card, and the usb quit working. I had to ship it back to Asurion. Just got my new one back.
Bottom line:
MAKE SURE YOU HAVE THE RIGHT KERNEL BEFORE YOU FLASH A NEW ROM!!

SD Card
Do you have another memory card that you could use? Try putting a copy of a rooted stock ROM on it and try to install that.
http://forum.xda-developers.com/showthread.php?t=743352

As others have mentioned clockwork does not always work well with Fresh, try Amon RA's recovery

TheBiles said:
When Clockwork wipes data it deletes the entire folder, which happens to contain the cache and dalvik folders. There's absolutely nothing wrong with that.
And OP, you might want to wait for Fresh 3.2. Just came out for donators today. I'm using it right now.
Click to expand...
Click to collapse
The dalvik cache is under /data but the android cache has it's own partition.

[Q] Having BIG problem, need help!

Okay, so earlier today I rooted my evo and flashed the CM6 ROM. A little later I tried to install Google apps.
I followed a tutorial on youtube on how to install gapps using rom manager.
Now my Evo is stuck in the Clockworkmod recovery screen and when I click reboot system now it reboots and goes back to the clockworkmod screen. I tried wiping data/factory reset and then re-installing the CM6 ROM, it did not work.
I really need some help here, I'm not too experienced and I don't want to brick my Evo. How do i fix this?? I am freaking out. Thank you!

I use AmonRA recovery personally and flash everything through recovery. I had too many problems when I tried flashing things through Rom Manager app. Do you have a nandroid backup? If so install the backup and then boot into recovery and reinstall CM6 and gapps back to back in the same recovery session. If no backup, download PC36IMG that corresponds with your hboot version and put it on the root of your sd card. Boot into bootloader by holding volume down and power at the same time. It will scan the sd card for PC36IMG and then verify it. It will then ask you if you want to update. Select yes and let it do its thing and then when it asks if you want to reboot select yes. This will put you back to stock and may unroot, so you may have to do the root procedure again. Then install CM6 and gapps in same recovery session.
Before all this try wiping cache and davlick cache and reboot. If that doesn't work try powering off phone through clockwork and then boot into bootloader. It will scan for PC36IMG and not find it then you will have options to boot into different things. Select recovery, and it will boot into Clockwork. Wipe cache and davlick cache and reboot. See if this works. If not you will have to nandroid or go back to stock probably unless someone that has had this problem and comes along to help you fix it. Always wipe cache and davlick when installing something new like gapps or kernels and full wipe when installing a new Rom, unless you are updating a Rom then just Davlick and Cache.
As long as the phone turns on it is not bricked.

housry23 said:
I use AmonRA recovery personally and flash everything through recovery. I had too many problems when I tried flashing things through Rom Manager app. Do you have a nandroid backup? If so install the backup and then boot into recovery and reinstall CM6 and gapps back to back in the same recovery session. If no backup, download PC36IMG that corresponds with your hboot version and put it on the root of your sd card. Boot into bootloader by holding volume down and power at the same time. It will scan the sd card for PC36IMG and then verify it. It will then ask you if you want to update. Select yes and let it do its thing and then when it asks if you want to reboot select yes. This will put you back to stock and may unroot, so you may have to do the root procedure again. Then install CM6 and gapps in same recovery session.
Before all this try wiping cache and davlick cache and reboot. If that doesn't work try powering off phone through clockwork and then boot into bootloader. It will scan for PC36IMG and not find it then you will have options to boot into different things. Select recovery, and it will boot into Clockwork. Wipe cache and davlick cache and reboot. See if this works. If not you will have to nandroid or go back to stock probably unless someone that has had this problem and comes along to help you fix it. Always wipe cache and davlick when installing something new like gapps or kernels and full wipe when installing a new Rom, unless you are updating a Rom then just Davlick and Cache.
As long as the phone turns on it is not bricked.
Click to expand...
Click to collapse
Where can I download the pc36img? Also, it seems that when I try to wipe dalvik cache, it doesn't do anything.

try here
http://forum.xda-developers.com/showthread.php?t=884060&highlight=unroot
If you are having issues getting the img on your SD card, if you have a card reader handy just use that to transfer it over

Tower1972 said:
try here
http://forum.xda-developers.com/showthread.php?t=884060&highlight=unroot
If you are having issues getting the img on your SD card, if you have a card reader handy just use that to transfer it over
Click to expand...
Click to collapse
I did find the correct one for my hboot version, but another question I have is do I need to flash unrevoked-forever-son.zip since I rooted using unrevoked 3.32? Or do I just put the PC36IMG on the sd card and flash it? Thanks.

Okay, I seem to have gotten it back to stock. Thank god, thought I lost my evo for a minute! Thanks to those who helped me out, its 4:45 in the morning and now I can finally go to bed! ;]

LOL glad ya got it back.. Yeah thats where I was heading before I seen your post..Its 5:46 am and Im not sure how many Evo people are actually on at this time so...anyway nite

I stayed on to help as long as I could, but had to go to work. Sorry I couldn't be here to help with more questions. Funny I was just getting up for work and you guys were just going to bed.
Glad you got it fixed for now. Remember to flash CM6 from recovery and not Rom Manager. Also, flash Gapps from recovery and not Rom Manager app. Flash CM then gapps and reboot. Make sure you do a full wipe first though. You could also look for Calkulin's tools thread in Dev section of EVO forum and find his wipe all zip. You just flash it like any other zip but it formats data, cache, boot and system partitions so that when you flash a new ROM nothing is left over from old one. Good luck my friend and happy flashing.
PS. I don't think the stock rom would give you s-on since you already had s-off, so you should be good to go. I could be wrong, but as long as you still have a custom recovery and s-off you should be good to flash any Rom.

evo camera
ok i have a root evo but my camara dosent work ... can some body help me to fx that problem

What rom are you using? Do they list camera issues or camera not working in the initial post with the rom?

Camera
Lets talk about the camera not working here:
http://forum.xda-developers.com/showthread.php?p=10983385

[Q] Tips for re-flashing Installed ROM?

I've got a general question that I haven't really found an answer for - although I know the information is there, I'm just not 100% sure how to piece it together. I'm hoping all you experts out there can help provide some guidance.
Using my EVO as an example, I currently have Fresh 3.5.0.1 flashed and have been very happy with it. But, I've been dinkin' around with Titanium Backup and uninstalled a few things (i.e. LiveWallpaper) and generally (probably) made a mess of things.
Everything is still working fine, I'd just like to get a fresh start with Fresh 3.5.0.1 but I'm not exactly sure what I should do to ensure a totally clean device.
I have ROM Manager installed... is it as simple as creating a NANDROID backup, downloading the ROM again and flashing? Or, should I boot into recovery and clear caches, wipe data/factory reset? I'm not sure if a "wipe data/factory reset" from the CM recovery (3.0.0.5) is the right thing to do.
Guidance would be very helpful and much appreciated. Hopefully, others could use any information provided to do the same with their device if they're unsure how to do the same thing with other ROM's.

i usually like using amon ra recovery instead of clockwork recovery which is the one use by rom manager, if you want to try it rom manager has an option at the bottom that says flash different recovery and says amon ra, if you click it your recovery will become amon ra which i like better for wiping. but to answer your question, yes for a fresh start on a new rom you need to boot into recovery, then NANDROID BACKUP, then wipe 1.cache 2. dalvik cache 3. data and then flash your new rom and you are good to go

If you want to start fresh on the current 'Fresh' ROM then, yes, wipe fully and reflash.
sent from my

Everything is still working fine, I'd just like to get a fresh start with Fresh 3.5.0.1 but I'm not exactly sure what I should do to ensure a totally clean device.
Click to expand...
Click to collapse
Just do exactly what you did when you flashed it for the first time. Place zip on sd card, nandroid backup, wipe everything, flash rom.

[Q] Custom Rom Question

Alright so i installed my first ROM on my evo last night. seems like it worked fine everything still works and the ROM is awesome.
http://forum.xda-developers.com/showthread.php?t=1012918
One questions i did have is, if i want to install another one how would i go about that?
Do i just install it like i did the first or do i need to remove the current one and install the new one?
Im sure this is posted somewhere but i wasent able to find the answer im looking for.
Thanks for any input

The tried-and-true and overall preferred method, as I've observed, of XDA forum members is to do the following when changing to a new ROM, or for the first time:
Place the ROM in the root of your SD card.
Boot into Recovery by holding vol+down and Power (most custom ROMs will let you reboot into Recovery specifically instead of having to turn off the phone and back on).
Make a nandroid backup.
Wipe data/factory reset.
Wipe cache.
Go into Advanced, wipe Dalvik cache.
"Go Back."
Install zip from SD card.
Choose applicable .zip.
Wait for installation.
Reboot.
Enjoy.
Furthermore, if going to an AOSP ROM, be sure to flash GApps right after you flash your ROM.
As far as kernels go, some people say to do it after you flash your ROM, some day to reboot and then go back into Recovery and do it, some say either way.

Load the new rom zip on your sd card from your pc. Boot to Recovery, make a nandroid backup of your current rom. Then factory reset the phone in Recovery and wipe data, cache and dalvik cache. Wiping them each 2-3x for optimal results.
Then flash the zip for your new rom. Reboot and there it is. If your gonna change kernels or task bars etc, I recommend booting between each zip flashed. Just seems I have less problems this way.
Also get a sms backup app if they are important to you. I use sms backup+. It's free and works great, backs up msgs to gmail. Then u can restore with the app when the new rom is loaded.
Sent from my Warm Z EVO

totalanonymity said:
The tried-and-true and overall preferred method, as I've observed, of XDA forum members is to do the following when changing to a new ROM, or for the first time:
Place the ROM in the root of your SD card.
Boot into Recovery by holding vol+down and Power (most custom ROMs will let you reboot into Recovery specifically instead of having to turn off the phone and back on).
Make a nandroid backup.
Wipe data/factory reset.
Wipe cache.
Go into Advanced, wipe Dalvik cache.
"Go Back."
Install zip from SD card.
Choose applicable .zip.
Wait for installation.
Reboot.
Enjoy.
Click to expand...
Click to collapse
Awesome thank you very much. Sounds pretty much just like how you install one.
Thanks again

yes do that ^^ nandroid and you can leave the rom on your card if you have enough space and in case you want to reinstall it clean again.

one more question
im thinking about installing another rom and it has multiple downloads some are themes and some widgets and the main ROM. Do I install them 1 at a time or can i do them one after another.

Honestly, preference, with those, I think. As stated before, some people's phones are fine with flashing tons of things at once and some people's phones like to take it nice and slow and have a reboot in between.
Also, make sure the themes you are installing are in flashable zips. There are some out there that aren't and require manually placing them in the SD card or using adb.

http://forum.xda-developers.com/showthread.php?t=841311
this is the one i was thinking about

dahlinc said:
http://forum.xda-developers.com/showthread.php?t=841311
this is the one i was thinking about
Click to expand...
Click to collapse
ROMs are flashed in recovery just the same as any other ROM.
All add-ons in his first post are flashable via Recovery, as well.
Get into a habit of wiping cache and Dalvik cache before every flash of anything. (Data/factory when flashing between ROMs, though.)
Also, a nandroid backup before you flash anything would be wise. I stopped doing them as often because they take up quite a bit of memory when you start flashing things left and right! But, it is wise to do so before flashing anything. If anything goes wrong flashing a particular item, you can always restore a backup and start again from a very recent point (i.e. not losing much of what you did) from when there were no issues.
I personally also copy my files to my computer for safekeeping, should something occur with the SD card.

Thats all i need know thank you again!!!!

[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.)