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] 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] CM7 RC1 won't restore

so i have been using CM7 RC1 w/ stock kernel for a while now, without any issues. i was reading up and wanted to try the new incredikernel though, for the governor rather than using setcpu/juice defender for increased battery life.
so i did a titanium backup, then in Clockwork did a full backup before i started messing with anything. i then mounted to computer to put the kernel on the SD card. i did this, but was confused where to actually put the .zip file so that CW would see it. SD card or internal memory? i've had this issue before.
anyway, i didn't find the .zip when i booted into recovery, so i went to re-mount to USB to move it over to the other directory, and everything seized up on me. trying to mount USB basically froze my phone. re-booting did not fix, when i try to go into CM settings or try to mount USB same freezing would happen.
OK fine, i just did a nandroid backup so i figured it wasn't a big deal since i haven't actually made any changes yet and so i restored. then it would not boot. got stuck at the CM7 bootloader. ****. so i tried an earlier restore point, from a few months ago. that worked (also CM7-RC1 when i first put it on). i didn't wipe cache/dalvik when i tried the first time, so i wiped now and then tried to restore the most recent backup again. still, no luck.
so i've been living with the older restore trying to get everything how it was before. another note, i had installed a battery meter (RC1 did not come with one), and when trying to flash this, got stuck at the same bootloader screen again. another thing to note is that i have been updating CW to the latest version when it is available, but all versions are 3.xx. the latest i think i went from 3.0.0.5 to 3.0.0.8. just trying to include as much info as possible here...
any ideas? it's frustrating because i haven't actually been installing anything new. at this point i just want my phone the way it was, i.e. getting the latest restore point to work. it won't, but older restore versions will work. did CW mess up the backup, is it corrupt? is this a CM7 issue or CW? help please!
if this is in the wrong forum, apologies, it wouldn't let me post in the dev thread due to lack of posts.

Did you do a complete wipe before trying to restore your backups? In recovery, wipe data/factory reset, wipe cache, wipe dalvik cache, format boot, system, data and cache.
Sent from my ADR6300 using XDA App

k_nivesout said:
Did you do a complete wipe before trying to restore your backups? In recovery, wipe data/factory reset, wipe cache, wipe dalvik cache, format boot, system, data and cache.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
i did not do that before. i just tried though, and same result. stuck in CM7 boot loop.
wtf happened to my backup!

That happened to me once. Try this. Save everything on your sd card to your computer. Reformat card. Then put just the nandroid back on card. It might help.

Yeah sounds like it may be an issue with the SD card or your backup..
Sent from my ADR6300 using XDA App

Random crashes after restoring to backup.

I had flashed Warm TwoPointThree. Didn't really like it so I restored to my nandroid back up. Now the phone randomly crashes for no apparent reason. It is sitting next to me on my desk and just now it crashed, wasn't even touching it. Secondary to the crashes is that after it happen and I try to report the phone is registering no charge and then immediately shuts down till I put it on a charger, regardless of actual battery charge.
Edit
More info. It has never crashed while on the charger. Don't know if that is relevant.

Did you wipe properly prior to restoring your nandroid? Also, what recovery are you using? If it's not Amon-ra, you need to get it! Make sure when doing a nandroid restore you have the appropriate items checked for restore (Assuming you did this when making the nandroid to begin with). Usually Boot, System, Data, and SD ext if partitioned.

Im using Amon-ra and I have an unpartitioned SD card. What do you mean by wipe? I'm a new to the entire rooting thing.

You need to wipe all data factory reset, boot, system, and dalvik cache in recovery three times each. Then restore your nandroid. You can also use a superwipe script but I feel manually wiping them is best.
Sent from my PC36100 using XDA

dieselford said:
You need to wipe all data factory reset, boot, system, and dalvik cache in recovery three times each. Then restore your nandroid. You can also use a superwipe script but I feel manually wiping them is best.
Sent from my PC36100 using XDA
Click to expand...
Click to collapse
Can I use the wipe feature in Amon-ra to do this?

Yes. That is the way to do it.
Sent from my PC36100 using xda premium

Try fix permissions, I think RA has it under other, or if u have Rom manager there is an option to fix permissions
Sent from my Synergized Aggressive Lionfish Evo using the XDA app

I think I may have found a problem with the backup I was using. For some reason the backup file had 2 copies of every entry.
Under the other tad in RA recovery there was options to fix apk uid mismatches and move recovery.log to SD.
I selected the fix apk uid mismatches. Im hoping that is the fix permissions that the previous poster was talking about. If not then can I get some direction in doing it properly?

SabaBoBaba said:
I think I may have found a problem with the backup I was using. For some reason the backup file had 2 copies of every entry.
Under the other tad in RA recovery there was options to fix apk uid mismatches and move recovery.log to SD.
I selected the fix apk uid mismatches. Im hoping that is the fix permissions that the previous poster was talking about. If not then can I get some direction in doing it properly?
Click to expand...
Click to collapse
Yes that's it.

Well the crashes have started again. They seem to start slow, one crash then like 3 days later another and then just increase in frequency, today it crashed 5 times before noon. I'm at the point that I think perhaps I need to wipe and not attempt to do a restore. My concern is will I lose my root if I do that?

Will I lose root if I do wipe with out restoring afterward?

SabaBoBaba said:
Will I lose root if I do wipe with out restoring afterward?
Click to expand...
Click to collapse
If you wipe without restoring, you won't have a ROM on your device. You'll have to flash one, and as long as it's a custom or rooted stock ROM, you'll be fine.

Well I did a factory reset tonight so we'll see how that goes. Thanks to those people who contributed.

Well I did the factory reset and this morning it crashed again. I'm at a loss. All this started after I installed the Warm 2.3 ROM and then restored back to a backup to get the stock ROM back. Any thoughts on what to try now?

Any further help that anyone can offer on this. I'm at the end of what I can think of to do

SabaBoBaba said:
Any further help that anyone can offer on this. I'm at the end of what I can think of to do
Click to expand...
Click to collapse
Just stop restoring and flash a ROM from scratch. Do a full wipe (everything except SD card), and then flash the ROM (custom or stock) or your choice. It seems that the restore is at the root of your problem, so it may be time to give up on that.
Current ROM (BootManager Slot 5): ICS-Deck-PreBeta20 | Kernel: Mason v0.14 SBC (FSO)

Captain_Throwback said:
Just stop restoring and flash a ROM from scratch. Do a full wipe (everything except SD card), and then flash the ROM (custom or stock) or your choice. It seems that the restore is at the root of your problem, so it may be time to give up on that.
Current ROM (BootManager Slot 5): ICS-Deck-PreBeta20 | Kernel: Mason v0.14 SBC (FSO)
Click to expand...
Click to collapse
Well Im going to flash this http://forum.xda-developers.com/showthread.php?t=1455340&highlight=stock+rom and see if that works. Thanks for the assist.

After wiping last night and loading the rooted version of the latest stock ROM it crashed again today. Next idea?

Try wiping in recovery by flashing Edify_Format_ALL (found on xda). I manually wipe Dalvik, habit... Flash rom from scratch. I use Titanium Backup to back up apps and data just for these situations. Some caches are moved to SD card, maybe delete these folders and let system rebuild them. (ie android_secure).
Hope you get it sorted out.

Grizraz said:
Try wiping in recovery by flashing Edify_Format_ALL (found on xda). I manually wipe Dalvik, habit... Flash rom from scratch. I use Titanium Backup to back up apps and data just for these situations. Some caches are moved to SD card, maybe delete these folders and let system rebuild them. (ie android_secure).
Hope you get it sorted out.
Click to expand...
Click to collapse
Ill give that a shot. I hope I can fix what ever I did to foul this thing up.
Just from searching the forums I really dont understand this edify thing. Can you help be get some clarity on it?