Savaged-zen(mod) reboots - EVO 4G General

Anyone else having random reboots in the savaged-zen roms? I've tryed flashing it a couple times used a few different versions of their kernels and I still get random reboots. It also reboots whenever trying to install any apps. If anyone else is experiencing these problems or has a fix. Feel free to comment
Sent from my CyanoEVO 7 using XDA App

you fix permissions?

NewZJ said:
you fix permissions?
Click to expand...
Click to collapse
yeah it didn't help at all.

someone posted this fix in another thread but i have no clue how to do it myself...
"I did a full wipe with Calk's Format All script and installed the RC3 with the SZ gapps from the first post (after a reboot, per an earlier post).
Couldn't install anything from the market or via File Manager. It would download, then hot restart the phone. Found out that the permissions/owner of /data/app (and/or data/app-private) were incorrect. Changed perms to 771 and owner to system.system and now all is well with the world again."

Had the same issue on my buddy's evo, after fixing permissions/owner I then used every option in ra recovery (2.3) in the wipe menu except " wipe sdcard" and " wipe boot", include android.secure and all other wipes. Flash rom then reboot phone, let the phone start up, then reboot back to recovery and flash gapps
Sent from my Evo using the XDA app

detcup4evr said:
Had the same issue on my buddy's evo, after fixing permissions/owner I then used every option in ra recovery (2.3) in the wipe menu except " wipe sdcard" and " wipe boot", include android.secure and all other wipes. Flash rom then reboot phone, let the phone start up, then reboot back to recovery and flash gapps
Sent from my Evo using the XDA app
Click to expand...
Click to collapse
The problem with that is that it wont boot with out the gapps being flashed. Ill try again doing what you said when I get home tho. Do you think its leftover files from other roms messing it up? Because when I first rooted I was what you would call a flashaholic haha and there is a few folders from other roms on my SD "miui, etc"
Sent from my PC36100 using XDA App

That is what I thought also, but it was a last ditch attempt before giving up and going back to his old nandroid, but the phone booted fine, and I was even able to make calls without gapps.
Sent from my Evo using the XDA app

ive had this issue with cm7...if i flash rom...then flash gapps...and then flast titanium backup
if i dont flash titanium back up it works fine.

Related

[POLL]Amon Ra or Clockwork

Was wondering which recovery everyone likes and why. Been using Ra since my G1 and I love it. (searched around for one of these and didnt see it. Mods delete if there was already one of these polls)
Amon all the way
Sent from my EVO using the Earths core to power my death ray
So...since this brought up...I see that some ROMs don't work with some recoveries? Is that correct? I swear it seems some ROMs only work with clockwork...but then I read all over that clockwork is buggy...or doesn't seem to work for everyone...or something.
I was thinking Amon Ra was the way to go.
I'll follow the answers to this one as well.
sablesurfer said:
So...since this brought up...I see that some ROMs don't work with some recoveries? Is that correct? I swear it seems some ROMs only work with clockwork...but then I read all over that clockwork is buggy...or doesn't seem to work for everyone...or something.
I was thinking Amon Ra was the way to go.
I'll follow the answers to this one as well.
Click to expand...
Click to collapse
Thats true. As far as I know, there have been issues with Clockwork not wiping correctly(I know someone like that)and causing bootloops after flashing. I dont know of any roms that dont work with Ra, but I believe Rom Manager will only work with Clockwork.
Clockwork since it is compatible with ROM Manager.
Clockwork since it has a back option in the menus. It's also updated frequently.
I've been running clock on the evo. I tried putting amon in but I guess I'm too stupid cause when I tried following the directions, I borked the phone good and it took me awhile to get everything back into working order. I could flash it now with rom manager but I'm kinda afraid after the last fiasco.
Sent from my PC36100 using XDA App
I've found that using both have worked for me the best. If I'm running Fresh Rom I will use Amon Ra's but I'll use clockwork for cm6. Its so easy to jump back and forth between recoveries using rom manager its never really an issue. Either way both developers are awesome and their recoveries both have good things to offer
anyway to switch back to Amon? not feelin the Clockwork im too use to it...
seriousblack25 said:
anyway to switch back to Amon? not feelin the Clockwork im too use to it...
Click to expand...
Click to collapse
Use ROM Manager to "flash alternate recovery."
another poll
dglowe343 said:
Was wondering which recovery everyone likes and why.
Click to expand...
Click to collapse
i was wondering the same thing exactly!! So a few days ago i asked the question on the Cyanogen forums... I got a lot of good responses and summarized the comments on the first post... check it out here: http://forum.cyanogenmod.com/topic/2562-best-recovery-for-evo-to-use-with-cm6/
I haven't had one single problem with clockwork recovery.
I like the recovery originally included with toastcfl's root found here. it's very similar to Armon's (don't know if things have to be signed or not), but you use the power button to go back instead of the double-press volume (which I find annoying to do).
I just don't like clockwork as much as the other two, that's just the way it is.
Using Amon Ra because I think it's the only recovery fully compatible with DamageControl.
Not sure of the actual "differences" between it and Clockwork - can anyone clarify?
oblivion0 said:
Using Amon Ra because I think it's the only recovery fully compatible with DamageControl.
Not sure of the actual "differences" between it and Clockwork - can anyone clarify?
Click to expand...
Click to collapse
I'm using clockwork with Damage Control I've had zero problems so far.
I hate Amon recovery... always have to move my ROM downloads to the root of the SD card... forget it 90% of the time and have to reboot to fix it... and that doesn't work so well if I borked my ROM.
I use Clockwork and have zero issues unless I'm trying to autoflash theme updates and such so I have to do those manually. Otherwise no complaints. And no signing issues with Clockwork either.
Amon_RA's recovery FTW!
Well, since rooting 24 hours ago, I've been using Clockwork via recovery boot (not through ROM Manager) and it's worked flawlessly so far. Backed up my rooted stock setup, flashed Fresh, DC, CM6, and then back to Fresh, wiped between every flash, and I've had no problems. Even flashed some Fresh Tweaks in the recovery boot. I actually flashed Amon Ra to see how I liked it . . . and I didn't. Mostly just navigating was a pain with the volume up+down thing, everything else seems like a wash. My only question is whether the Dalvik cache is really being wiped by Clockwork, since it takes half a second to complete when I select the option. I'm going to test it in a few minutes here.
Going to give Baked Snack a run for a while, we'll see how that holds up.
I have wondered that for awhile, silver. It may sound stupid but at least a confirmation in the log messages below would be nice.
Sent from my PC36100 using XDA App
herbthehammer said:
I have wondered that for awhile, silver. It may sound stupid but at least a confirmation in the log messages below would be nice.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Okay, I decided to test. Fired up ADB and booted into recovery from Android. Mounted /data and looked inside /data/dalvik-cache. There was a long list of .dex files. Then I unmounted /data and used the Clockwork menu to wipe the Dalvik-cache (this option is located under the "advanced" menu, NOT just the "wipe cache" option). Re-mounted /data and looked inside . . . and the dalvik-cache directory was gone. It took *slightly* longer than normal when I actually hit the button to wipe it (more like .7 seconds instead of .5), but it does appear that my Clockwork v2.5.0.1 is wiping dalvik just fine. And, of course, when I rebooted back into Android (rooted .6 stock at the moment) it took a long time to boot at the 4G screen, as the cache was being rebuilt. Once I was back in, I checked the /data directory again and dalvik-cache was back and full of .dex files again.
So there. No more speculating, just science.
And if you're ever worried about it, you can just use ADB to wipe the dalvik-cache yourself:
Code:
adb shell
mount /data
rm -rf /data/dalvik-cache/*
Then you can use the Clockwork menu to wipe everything else and flash your ROM. These three commands actually just delete everything inside the dalvik-cache directory, whereas Clockwork appears to remove the directory entirely. Doesn't really matter either way, the system will replace the directory if it gets deleted.
Mmm . . . terminal code.

Installed ClockworkMod...

Hi guys,
I've tried using unrevoked 3.3 on my wildfire, with android 2.1, didn't work - so I tried 3.2 and I got the ClockworkMod Recovery v2.5.0.1 on there, I can boot into that now,
But still not knowing how to root it,
Can someone give me some advice from here, I get the "Internal error" message and can't go any further, but I assume you can manually do it, since I've got the clockworkmod recovery on there,
Toby =)
Soulquarian33 said:
Hi guys,
I've tried using unrevoked 3.3 on my wildfire, with android 2.1, didn't work - so I tried 3.2 and I got the ClockworkMod Recovery v2.5.0.1 on there, I can boot into that now,
But still not knowing how to root it,
Can someone give me some advice from here, I get the "Internal error" message and can't go any further, but I assume you can manually do it, since I've got the clockworkmod recovery on there,
Toby =)
Click to expand...
Click to collapse
if you have clockworkmod recovery then that means you rooted it, just put a custom rom onto your sd card, boot into recovery and install zip from sd card. do a nandroid backup of your rom first.
When I try using Titanium Backup, I get a failed message...
Sent from my HTC Wildfire using XDA App
Okay, I installed busy box and it says it rooted, does the clockworkmod matter what version you have?
Sent from my HTC Wildfire using XDA App
Soulquarian33 said:
Okay, I installed busy box and it says it rooted, does the clockworkmod matter what version you have?
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
Nope, you should be fine.
Thank you, I'll let you know how it goes, is Wildpuzzle rom trustworthy? It's been around for awhile right? =)
Yeah wildpuzzle is good, I used to use it.
I had abit of a freak out, I wiped my phone then couldn't load any custom rom =( But now its loading, hoping it works...
I don't know if the rom is loading or not, the screen with the android symbol coming out of the box showed up now and white backgroud with the "HTC quietly brilliant" animation seems to be sitting there forever,
I installed the SUnAaBh v1.1** rom from sc card,
Does this seem right?
First boot takes 10 to 15 min.
You should have done a nandroid backup of your stock rom first, oh well.
If it doesn't boot, do a full wipe, wipe data/factory reset and wipe cache in recovery and flash again.
After like 2 or 3 minutes, the screen goes black then the HTC logo screen comes back on and loads again, makes me think its in a loop and no installed right =\
Do a full wipe and try flash again. If it doesn't work, try a different rom.
Yeah, I did a back up with nandroid then moved the files to my computer incase, they was in a folder called orangeworkmod folder?,
Wipe cache?
Soulquarian33 said:
Yeah, I did a back up with nandroid then moved the files to my computer incase, they was in a folder called orangeworkmod folder?,
Wipe cache?
Click to expand...
Click to collapse
Yes, you should wipe data and cache before installing a new rom. They are all there in recovery.
Okay, yeah - its all good, was just taking time, does wildpuzzle rom have overclocking feature, or is that a application?

[Q] Trouble Installing Liberty 1.5 ROM

So I'm not an Android expert, but I do have experience rooting and installing ROMs and I'm stuck.
I've followed the instructions from this forum for loading Liberty 1.5 on my DX, which are copied and pasted below:
-boot into recovery via clockworks bootstrap
-select "wipe data/factory reset"
-select "Yes -- delete all data"
-go back "powerbutton"
-select "install zip from sdcard"
-select "choose zip from sdcard"
-find and select LibertyX/2-X.X.zip
-reboot
When bootstrapper tried to flash the Liberty zip from the sd card I get an "installation aborted" error. I deleted and re-downloaded the file numerous times from various sources, but I get the same error.
Any ideas?
Did you download multiple times from multiple sources on your phone? If so try downloading with a PC. I had issues a couple of times downloading from my phone until I noticed that the zip file wasn't downloading correctly.
I downloaded 3 times from different forums through my macbook, then transferred the files both via awesome drop and via usb. Got the installation aborted error every combination. I rooted using the Z4 app if that makes any difference.
So you tried dling on your macbook... did you try downloading directly to your phone? I never use a computer to download roms.
Sent from my DROIDX using XDA App
What you need to do is wipe your data and cache, go to advanced, wipe dalvik cache, wipe battery stats, go to mounts and storage, mount system and data, and then install it
I've installed liberty 1.5 on two phones now, mine and for a friend of mine. I was really super careful on mine and it took a couple tries to get it to go, but if you dont clear the cache and wipe everything it gives you lots of problems. It's a must.
Finally got it to work. My download was getting terminated from xda (at least that's what my computer was telling me) and I was only getting partial downloads. I downloaded via the ftp link and it loaded somewhat ok. was stuck in a boot loop for awhile, but a couple recovery reboots fixed that. Running smooth now, thanks for the assistance.
Nice. How do you like it?
Sent from my Droid X running Liberty 1.5 custom using xda premium app
Help!!
I'm brand new to installing custom ROMs and I think I made a big mistake. I installed Apex just fine and then I thought I would try to install Liberty. I went through the process but after it rebooted it is just staying on the Liberty logo and not doing anything else. I figured it might take a few minutes but it's been over 30mins!
Thinking back to when I installed the ROM, I might have forgot to wipe the old ROM.
I need help. Is there anything I can do or is my phone now bricked??
Not a big fan. A little too buggy for me. Installed darkslider and I love it!
Sent from my DROIDX using XDA App
tsibs7 said:
I'm brand new to installing custom ROMs and I think I made a big mistake. I installed Apex just fine and then I thought I would try to install Liberty. I went through the process but after it rebooted it is just staying on the Liberty logo and not doing anything else. I figured it might take a few minutes but it's been over 30mins!
Thinking back to when I installed the ROM, I might have forgot to wipe the old ROM.
I need help. Is there anything I can do or is my phone now bricked??
Click to expand...
Click to collapse
I ran into the same issue the first time around. While my friend didn't recommend it, I did a battery pull and restarted; after that, everything went well. I can't say that this will work on yours.
You can also try the Darkslide ROM as recommended by jrdecat. I didn't run this one for long, but it was stable.

[Q] Flashed cm7 & getting lots of force closes??

Im on mytouch 4g permrooted s=off,gfree method,i searched through the forums and couldnt find anyone with this issue?? Wiped data,cache,& delvik flashed cm7 and jt wrked fine for about 10 min then everything wss forcd closing,i couldnt open no apps or anything so I pulled the battery out & rebooted then everything happened again so I just flashed back iced glacier anyone had this issue??
I had an issue like that when I first got started, I found that all I needed to fix that was to fix permissions.
Sent from my HTC Glacier using XDA App
Did that then rebooted wrked for a lil bit and did the same forceclosing,i dnt knw whts wrng... Tried last night & then after it did the forceclosing I had to pull the battery then went to clockwork and got all errors couldnt mount cache or data,phone went crazy,but managed to keep playing with it & got it running again on iced glacier,i also have clockwork 3.0.0.6 forgot to put it out there lol..
I know this problem. There is an issue about the permission problem.
1)You turn your phone off
2) hold VOLUME DOWN and POWER switch to go to the bootloader
3) go to RECOVERY (to the clockworkmod recovery)
4) in the cwm recovery, go to the ADVANCED
5) in ADVANCED go to the FIX PERMISSIONS
6) wait until it is finished
7 ) restart your phone and nothing bothers you with crashing.
Did you flash gapps with the cm7 rom? You supposed to flash gapps every time you flash a cm rom. Also, did you do a full wipe? Not just cache and dalvik but a full full data wipe since you're coming from a different rom than cm.
Sent from my CM7 Glacier using XDA App
Yeah I forgot to say that also,i did install gapps also,did the full full wipe,@fosunite ill try that when I get off wrk & let u knw how that goes,thanks to all for the quick replies...
Am I the only one with this issue?????
wiped data,cache,delvik,formatted boot & system,flashed cm7 again,installed gapps,then fixed permissions,then rebooted everything booted fine then went to put my account info,phone started forceclosing everything again and at that point i cant press any apps or anything,always have to pull battery out then wipe everything and flash another rom.... i would really love to use this rom!
That s wierd, did you try without using gapps ? maybe it could be that you downloaded the wrong gapps version which is not compatible for 2.3...
i used that one which was provided with the cm7 download link.
Try this:
When you first boot after installing cm and gapps, let it sit at the google sign in screen. Don't sign in and don't hit skip. Just let it sit for two full minutes while the dalvik is rebuilt. Then reboot from the sign in screen by holding down the power button. Once rebooted, let it sit again at the sign in screen. Then SKIP sign in so you go to your home screen. Let the phone chill again. You shouldn't have any more fcs after that. Sign in to google by opening the market app.
Sent from my HTC Glacier

have i bricked it??

hi, i have been reading up alot today on how to root and install a rom on my xoom, i rooted it fine then i went to the ics thread and downloaded the latest build, v17... put the zip on the sd card and went into recovery mode, choose to install zip from sd and installed it, then went to reboot device and it rebooted but came to a black screen that says android across the middle, its been on that screen for 20 mins now, help please lol
sorry... sorted problem, im guessing its bcos i wasnt installing google apps from zip too, sorry again
Honestly I have run into the same issues...hold down the volume up button + power...your Xoom should reboot.
Then you see the red Motorola logo wait 3 seconds and hit volume down...you should see "Android Recovery Mode" in the upper left corner.
Hit volume up to select....your device should enter recovery mode.
From here wipe data factory reset...wipe cache partition...then go to advanced...and wipe dalvik cache.
Then go to install zip from SD card and reinstall the ROM and Gapps and you should be fine, the first boot can take up to 10 minutes so don't panic...
XOOM Running Team EOS latest ICS build v.17 OC'd @ 1.5Ghz
Sent from my DROIDX using xda premium
Haha never mind...glad you got it working...disregard my previous post ; )
Sent from my DROIDX using xda premium
Boarder277 said:
Haha never mind...glad you got it working...disregard my previous post ; )
Sent from my DROIDX using xda premium
Click to expand...
Click to collapse
No, don't be sorry. That was a great explanation.
I know you got it fixed but I will say this:
Always do a full wipe when flashing a new rom. In this case, the ICS build was a new ROM and you should have wiped.
Usually you do not need to do a full wipe if you are just flashing a new build of the same ROM (if you go to a new nightly for instance). Just need to clear cache/delvik and reinstall gapps.

Categories

Resources