Alright, about a couple of weeks ago my phone started randomly rebooting/shutting off. Was on meanrom 3.x woth stock kernal. Tried superwipe, reflash. No luck. Tried one of the many miui roms, tried aosp roms, tried android revolution, zr3d. Multiple different kernals. Still no dice....anyone have an idea. Hboot 1.4 downgraded, newest radio, ext 4 recovery.....almost bought a nexus last weekend, driving me nuts!
Sent from my PG86100 using XDA
Gonna try updating the recovery..dpnt think thats it but what the hell. Also generally it happens with screen off and unplugged. Never happened with screen on yet
Sent from my PG86100 using XDA
What software are you on the 2.08 or 2.17? Also what recovery? Also are you do you always wipe all the way prior to flashing...
2.17... On mean rom from 3.0 and up I'd just flash over... But since I've been having these issues been using superwipe.. Now I'm been flashing roms since I had a blackberry 8310. But I've never used a superwipe script to delete the rom data... This may be a dumb question since it wipes everything but do I have to select factorywipe too after executing the superwipe script..
1. 0.0.5 rc3 I think.. Just updated it. I think I tried your rom too!
armdavid2 said:
2.17... On mean rom from 3.0 and up I'd just flash over... But since I've been having these issues been using superwipe.. Now I'm been flashing roms since I had a blackberry 8310. But I've never used a superwipe script to delete the rom data... This may be a dumb question since it wipes everything but do I have to select factorywipe too after executing the superwipe script..
1. 0.0.5 rc3 I think.. Just updated it. I think I tried your rom too!
Click to expand...
Click to collapse
I use CWM 4.0 as a recovery.. I never user superwipe just a factory wipe also cache and dav cache.. Everything runs smooth...
I would try a normal wipe then run that script..
Related
I don't know if you guys are aware of this but evertime I flash something its been with Rom manager. I got very sick of killing WiFi so I started all over again with BAMF beta 5 and flashed the few fixes and a new kernel. Same as I always did but this time I only used recovery and it worked. Haven't killed WiFi at all. Tried a bunch of times and still good to go. Also this only applies to GINGERBREAD ROMS!
Sent from a cellular telephone
You mean flash in recovery?
I had a similar experience but I think it was a coincidence.
Sent from my ADR6400L using XDA App
You should always flash through recovery... ROM manager likes to break things. Glad you got it working though.
yeah. Flash in recovery.. and I don't think its a coincidence. But who knows. Been working great this way
Sent from a cellular telephone
bking_soda said:
You should always flash through recovery... ROM manager likes to break things. Glad you got it working though.
Click to expand...
Click to collapse
Yeah. Ha. I guess so. I'm never using Rom manager again. Lol
Sent from a cellular telephone
I usually flash in recovery because my old OG Droid didn't like rebooting into recovery from ROM Manager. My T-bolt doesn't seem to have that issue and any time I have used Rom Manager to flash several zips at once, usually multiple patches or whatnot, I haven't had any issues. I have yet to flash an entire ROM in ROM Manager though.
So are you saying that ROM Manager is good for nothing but flashing the recovery image and getting CM7 Nightlies when they come out?
I knew I shouldn't have paid for it!
I flashed the bamf2 beta 5 update with ROM manager and my WiFi got messed up. I read this thread, rebooted into recovery, wiped cache and reflashed bamf2 beta 5. Wifi now works
Sent from my ADR6400L using XDA App
Uh ok lol
Sent from my ADR6400L using XDA Premium App
So has anyone let Koush know so he could look into this issue?
rom manager = junk for gingerbread roms i guess. it was amazing on froyo though, maybe they will update
RM updated to 4.2.2.0
CWR updated to 3.1.0.1
Had the same problem with flashing from rom manager. I do not use it anymore
ROM Manager
I was addicted to ROM Manager on my D1, even with Gingerbread ROMS (CM7). I haven't really used it for ROM installation on the Thunderbolt though. I paid for it on the Android Market and have absolutely no regrets, and as the ROMS mature for the Thunderbolt, so will the means for installing them.
Flash away I say.
Used it to flash BAMF 1.6.3 Remix, worked great.
i used it for das bamf 1.6.3 remix and had issues through rom manager. When i flashed through recovery everything went smoothe as butter. This time things were debloated.
tegan_ca said:
Used it to flash BAMF 1.6.3 Remix, worked great.
Click to expand...
Click to collapse
I had problems using it to flash remix, had to use recovery to get it to work correctly. It seemed like it wasn't fully wiping the cache/data before the flash, whereas recovery did.
Newb here, is it possible to download through RM but not trigger the auto-flash-sequence? Every time I d/l something through RM it tries to flash immediately after downloading.
tegan_ca said:
Used it to flash BAMF 1.6.3 Remix, worked great.
Click to expand...
Click to collapse
I had problems using it to flash remix, had to use recovery to get it to work correctly. It seemed like it wasn't fully wiping the cache/data before the flash, whereas recovery did.
My D1 never did like RM or CWM. And its nands were huge. I haven't rooted my Bolt yet... need to get around to that, I desperately miss Titanium and Root Explorer.
Alright, we will start with a story - I am a fairly experienced root user. I had a fascinate, droid x, and now I have a thunderbolt. I had all three rooted and never had problems until now.
I have root access as well as a custom ROM on my thunderbolt. (I am currently using liquid 3.2).
The problem is that when I try to flash any other rom (I tried two: CM7.2 by ThunderShed and Infected by Virus) they do not work at all. I flash data, davik, and all that stuff. Infected gets stuck on HTC logo and CM7 gets further but freezes on startup after initial setup shows up.
My friend recomended flashing all different radios and I did that, but still having an issue. (I have 1.48.... and 0.0178... on now).
A few things.....check the md5 when you download. Wiping........wipe data/factory reset, then wipe cache, then go advanced and wipe dalvik cache, then go format/mount and format /system. Then install the .zip. If that doesn't do it, I have no idea, never had a problem flashing ROMs, only have problems once I start messing with them on my own.
I had to change to different recovery
Sent from my ADR6400L using xda premium
First, the roms do flash - just not boot up after. Both go through the process fairly well. Like I said - the only that actually works is Liquid 3.2, both Infected and CM 7.2 flash just get stuck at a different stage when booting up.
I'm going to download yet another rom and see whether that does it.
The recovery that I have is 5.0.2.1. I was going to install touch recovery and see if that was more reliable. I'll post later and see whether it was just the two roms possibly being bad (both downloaded from RootzWiki and not XDA).
Run superwipe after you wipe everything, then flash your rom.
Sent from my ADR6400L using XDA
Try flashing a stock kernel first.
I also had the droid, droidX, droidx2, incredible2, thunderbolt, and now the galaxy tab. Also fairly familiar with rooting and flashing, and I had the same problem and couldn't figure it out. My clockwork was out of date. Updated, and everything was right in the world again. Check your Recovery. I didn't think if the update during flash took that it was my recovery but I was wrong.
flashing problem...
did you make sure usb debugging is on, and allow mock locations and non market downloads, and try deleting the current infected rom and re-download it just to make sure it was a clean download...i love the infected roms, especially eternity with darkhorsetheme. if that doesn't do it idk man. best of luck and try to get a hold of a developer maybe
Thank you guys!
Alright, so first off - I made sure my recovery was up to date.
I did wipe format /system and that caused infected to load, but after about an hour of using it - it froze and then when I pulled the battery, it wouldn't go past HTC logo.
I did load CM 7.1 and that works well.
I'll keep digging at it and see if I can figure it out. Thank you everyone!
Did you ever find a solution? I am having the same problem. I have tried 3 roms. It starts the boot screen and then after a minute it reboots into recovery.
It's the recovery folks.
Cwm = fail
4ext = win
donnyp1 said:
Run superwipe after you wipe everything, then flash your rom.
Sent from my ADR6400L using XDA
Click to expand...
Click to collapse
Using super wipe fixed this issue for me. Even after triple wiping dalvik didn't work, super wipe did. :good:
Hi to all.. I have been mentioning this in several ROM's threads, but none answerd.
I'm writing this to find if anybody else experiencing the same issue...
Since I have been flashing ICS ROMs, my front facing camera stopped working..
Before that on GB, even with Amaze camera it worked perfectly, now it just freezes the camera app, and nothing happens...
I'm missing it because of video calls.
Can anybody suggest any solution?
gosh do u know why we have "Q&A section" as a subforum?
Sorry, if anybody can move it, do it...
But it's just ROM development related issue, so placing it here is not such a nonsense...
I've read somewhere, that it can be kernel - based issue, but one of my friends who has also EVO has no problems with that...
Jonage said:
Sorry, if anybody can move it, do it...
But it's just ROM development related issue, so placing it here is not such a nonsense...
I've read somewhere, that it can be kernel - based issue, but one of my friends who has also EVO has no problems with that...
Click to expand...
Click to collapse
no, this is your issue, it has nothing to do with rom development. You probably just forgot to wipe cache and ended up using parts of an old kernel.
You can either start a thread in Q&A section, or ask the question in the thread of the ROM you are using
shirioko said:
no, this is your issue, it has nothing to do with rom development. You probably just forgot to wipe cache and ended up using parts of an old kernel.
Click to expand...
Click to collapse
That's not possible, cache wiping won't remove kernel modules...
Did you try to run fix permissions? full wipe? do that, then it might work.
I did full wipe almost everytime before flash...
Now I did fix permissions and no change..
Any other ideas? What about full format?
Maybe It's a physical problem did you flash a gb Rom and see if it works then ?
Sent from my HTC EVO 3D X515m
vipirius said:
Maybe It's a physical problem did you flash a gb Rom and see if it works then ?
Sent from my HTC EVO 3D X515m
Click to expand...
Click to collapse
+1 to this. As a test, I suggest you do a full super wipe and then flash a GB Rom like Mean Rom 4.2. If it works then, then rewipe and flash a sense based ics Rom and test again. You will then have your answer as to if it is ics or not.
Sent from my PG86100
What about the baseband? Should I revert the older firmware too???
Ive allready done that, reverted back to the MikRunny, it did not function...
But there was the Anthrax kernel, so might will try the Mean Rom...
I have flashed many ics roms fully wiping each time and have no issues with ffc
Sent from my PG86100 using XDA
Always:
List your HBOOT version and "S" status. If you did, ok. But, I didn't catch it.
Also, list what steps you have taken.
VERY first thing:
1) Wipe cache, dalvik, factory reset, and flash modified superwipe (I've done this and in doing so have had no flashing issues. All my issues were because of something I missed or messed up).
2) Have you tried going back to a GB ROM? If so, how? Did you do a restore or a clean wipe and flash?
3) If you did a restore, did you do a complete wipe as stated in #1?
4) After flashing an ICS ROM, were you trying to restore any data from a previous ROM, whether GB or ICS?
5) If trying to restore data from a GB ROM, it will bork your ICS like it did for me, regardless of the ICS ROM.
6) If trying to restore data from an ODEX ROM to a DEODEX ROM, or vice versa, it will bork stuff.
Just let us know what was done and that will eliminate a lot of repeated suggestions.
EDIT: I'm running Booster Shot ICS with no issues or force closes. I've easily flashed my phone to different things over 50 times. Completely wiping everything like I stated in #1 has always worked for me and prevented issues in coming from a different ROM. Sometimes if you skip a wipe, it will leave remnants of the previous ROM (from what I was told and it has seemed to prove true in my cases).
wipe
sounds like a wipe issue. I've used several ICS roms with no issues.. Try SuperWipe by mikey and see if that helps. Also, not all recoveries will propperly install all ROMs, I'm using 4ext right now and seems to work well
Gotta Learn the proper wiping techniques.... Only fold it twice...
Sent from my PG86100 using Tapatalk 2
i was using Saurom ROM at 1st and it worked perfectly for my galaxy note i717(this was my 1st attempt to root my phone and install a new rom), and i saw a better ics rom ("Onlyone" ics rom) at rootmygalaxynote.com, i flashed the new ics rom into my phone and it stuck at the samsung logo. i tried to re-install the ics rom again and same thing happened. So, i go back to re-install my old Saurom ROM. But when the phone get into the main screen, it is extremely laggy and eventually freeze, most of the cases, the phone reboot itself. i m so scare that the phone is not able to read any rom now. and i am new to smart phone, can any Brother and Sister in this Forum can me get through this. i m so
You are wiping data cache and dalvik before each flash right?
Sent from my SGH-I717R using XDA
TJBunch1228 said:
You are wiping data cache and dalvik before each flash right?
Sent from my SGH-I717R using XDA
Click to expand...
Click to collapse
^This.
Sounds like you're not wiping properly between flashings.
And don't worry OP. XDA can help you through just about anything!
When flashing a new rom you should being doing the factory reset/data wipe, then wipe cache, wipe dalvik cache. Then flash the rom zip. I would only download roms from the xda post, and the dev usually posts instructions on how to flash it.
To flash the Only1 ICS rom...you must be coming from an earlier ICS build (UCLD3 or UCLC5). If not then this is what you need to do. Flash the UCLE2 leak thru ODIN first. Let it reboot and let it settle for about 5-10 mins. Then Flash CWM via ODIN again. Once that is done...you are ok to flash the Only1 ICS Rom.
You don't have to be coming from ICS to flash OnlyOne. Truth is most Devs have some sort of wipe built in for their ROMs. OnlyOne Dev does not. All you have to do is wipe data/factory reset and then install the OnlyOne ROM. Unless I am wrong, wiping data also wipes cache. Simple as that.
sounds like paranoid anticipation not letting your dv cache and system files build. Since you said both times Samsung logo... I don't think you waited long enough... Plus use flapps first. Then if you wanna have problems to fix, try other roms... In my opinion.
Btw.. Use our development section to get the original content... Not some link from another website redirecting eventually to us anyway.
Sent from my SAMSUNG-SGH-I717 using XDA
I am having some problems with ROM's. I can install them just fine, but everything except Fresh is buggy as heck. I am fully rooted with S-Off now but the ROM dates back to when I had S-On. I have tried Viper and a few from OMJ but everything end up being buggy. I even did the stock 4.1 that OMJ posted and the same thing. I've even been considering doing an RUU but keeping S-Off to see if that would help things. I would really like to upgrade to 4.1 but it just drives me nuts with how buggy and slow things become. Using Google Now on the ROM was painful because everything just took so long to open but when i disabled Google Now it was still slow just only slightly faster. I've upgraded to this phone about three months ago so it's fairly new still.
Can anyone help me with this?
TejasEric said:
I am having some problems with ROM's. I can install them just fine, but everything except Fresh is buggy as heck. I am fully rooted with S-Off now but the ROM dates back to when I had S-On. I have tried Viper and a few from OMJ but everything end up being buggy. I even did the stock 4.1 that OMJ posted and the same thing. I've even been considering doing an RUU but keeping S-Off to see if that would help things. I would really like to upgrade to 4.1 but it just drives me nuts with how buggy and slow things become. Using Google Now on the ROM was painful because everything just took so long to open but when i disabled Google Now it was still slow just only slightly faster. I've upgraded to this phone about three months ago so it's fairly new still.
Can anyone help me with this?
Click to expand...
Click to collapse
In recovery what is your wiping process?
Sent from my EVO using Tapatalk 2
thicklizard said:
In recovery what is your wiping process?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Recovery: Team Win Recovery Project v. 2.3.1.0
Wipe Cache, Davlik Cache, Factory Reset (figured it couldn't hurt?) System, and even wiped Android Secure (to see if it helped this situation)
What is your baseband? Have you updated firmware? If not that can be the culprit...and also how do you restore,? Use tibu for apps only or are you restoring system data?
Sent from my EVO using xda premium
I forgot to update those things I'll try that. Thanks. I use titanium only for apps not system data.
Appears to have worked. Thank you for reminding me of that. I always did that on my OG Evo but forgot on this phone.
Sent from my EVO
Upgrade your twrp also through goomanager
Sent from my EVO using xda premium