I don't know it it has been discussed previously, but after I did full wipe + format/system, reboot started working.
I am on CM Nightly
Mine took 3. But it worked. Don't know why.
Sent from my LG-P999 using XDA Premium App
What build? Mine worked on like build 7 then no more. Maybe I did a full wipe plus system between flashes. I do them occasionally but still no reboots. It just stays off
I got CM #31 with faux123 kernel (ext4)
Reboot is flawless
Edit: fortgot to mention that I'm on ext4 Recovery
Related
So, I tried to root this phone and I used SuperOneClick and successfuly rooted it.
Afterwards, I downloaded ROM Manager and installed the nightly 53 from Cyanogenmod 7.
I checked Wipe Data & Cache, Wipe Dalvik Cache;
Afterwards, it went to the clockwork recovery; (the orange screen) installed it successfully from the SD card;
Afterwards, Cyanogenmod didn't boot correctly and got looped so i had to pull the battery; then restarted;
it loaded correctly but welcomed me with a series of force closes;
THE PROBLEM:
1. wi-fi doesnt work; when it restarts, it resets all the accounts and settings i've worked on;
2. the orange clockwork recovery mode won't start; instead, it goes to android system recovery <3e>; at that; there are four options that i can go up and down to wipe data/factory reset and all those options
but cannot click on the option; the power button doesn't do anything; the home button makes it disappear;
3. when i go to the terminal; su doesn't work; it goes permission denied;
rom manager won't restart into flash recovery to install new nightly;
so what have i done? what do i do?
I would just like to go back to stock;
Why don't you try posting this in the nightly thread or read a little. Your posting in the wrong place.
Sent from my Nexus S using Tapatalk
I'm guessing you won't be able to, but try turning on the phone by holding the power button and volume down. There's a chance this will take you to recovery, at which point you can wipe and re-flash.
Technically, rom manager only does a "fake" flash of cwm, so that's why it probably will not.
Otherwise, you can probably use adb somehow, but that's outside of my knowledge.
Had the same issues, but you shouldn't use nigh builds as your main rom. if you do use build 105
cm 7 gone wrong
Did you do nandroid backup? If so boot into cwm recovery and restore it ,if you didn't go here http://forum.xda-developers.com/showthread.php?t=1048274 follow the directions if you still have issues you can pm me.
If you can access ROM manager try flashing recovery
If I helped in anyway feel free to thank me
Did you install cwm using nvFlash or rom manager? If you didn't install cwm using nvFlash you will need to do that first. Using rom manager is only a "fake flash" for our phone and the recovery is only temporarily installed.
Sent from my LG-P999 using XDA Premium App
Read the nightly thread from around when 53 came out. Several people had this issue, myself included.
Solution is to just flash a different nightly on top of 53.
Sent from my LG-P999 using XDA Premium App
dnichols4 said:
Read the nightly thread from around when 53 came out. Several people had this issue, myself included.
Solution is to just flash a different nightly on top of 53.
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
But first u MUST install cwm with nvFlash
Sent from my LG-P999 using XDA Premium App
Got to use NV flash that will fix your problem
Sent from my LG-P999 using XDA Premium App
yuppp that nvflash is the first step, never use rom manager to flash cwm, im my opinion rom manager is garbageeee, i never use it
Thread moved to proper forum.
I'm having a bit of trouble flashing val black. I was running val final by white. i followed the op. i wiped cache. did a factory data reset. wiped dalvek cache. formatted /cache formatted /data and i formatted /system. in order to format /system i had to use a newer version of bh's kernal with cwm 5.x. anyway after i switched kernals it allowed me to format /system. when i tried before i changed kernals i would get an error saying unable to unmount /system. Anyway i mounted ummu. then did install zip from sd card. i chose val black i got the new touch cwm ui aroma thing and it said it installed it successfully. i think i clicked a finish button it took me back into cwm then i went back to reboot system now. the phone rebooted and when it came back on all i got was the first splash screen that says galaxy 4g exclusively by tmobile screen. and normally the white letters will get brighter after a second or two but they didn't. it just stayed there. so i let it sit about 10 minutes and it never did anything. can someone tell me where i may have went wrong?
I just used bh's one click package to go back to stock gb with his 2d kernal. If anyone has any ideas let me know. I haven't been able to flash val black ever since it got mixed with cyanogen hybrid. idk whats up.
well I'm not sure I understand the steps you did in order to flash.(its really messy)
If you want others to help you Please format your message with clear details,in a clean format:
1)what did you try to do?(going to,going from)
2)what are the steps you did exactly?
3) what was the result?
4)if you can - attach recovery log in order for us to try and analyze what went wrong?you can do that by adb(during recovery) or with CWM if you are using the latest version(5.0.*)
Good luck
Alon
P.S - if eventually you feel like the problem is sloved(probably by accomplish a good flash) please edit the OP title by adding [SOLVED] to it
10x
Did you reboot the phone after you ran the one click and let it set for 10 minutes or so? Which version of vahalla black did you flash?
Ok. Ill break it down in steps.
First of all i used bhs one click to go to stock gingerbread with his 2d kernal.
Second i flashed whitehawks val final. Everything working great. Been running it for a couple weeks
Third i downloaded ravers final version of val black.
Fourth i switched kernals to bhs latest so i could format /system
Fifth i went into cwm wiped cache partition and dalvik cache.
Sixth i did a factory data reset from cwm
Seventh i went to mounts and formatted /system /cache /data
Eight i made sure it was set to ummu
Nine went to install zip from sd card and chose ravers rom
10 it took me to aroma installer and i did typical and custom. (ive tried it twice). With custom i checked off the wipe boxes.
11 installaton seemed a success so i clicked next
12 it took me back into cwm so i clickd go back then restart phone
13 phone boots to the very fist splash screen where is says galaxy s 4g but nothing more. Also while its hung up there the white letters dont get brighter like normal and the only thing i can do is get into download mode.
I do have voodoo lagfix on with ext4 does that matter? i didnt see that mentioned anywhere.
Sent from my SGH-T959V using XDA App
Same thing happened to me except I came from BlackEdition.zip ( the releases before final ) and everything flashed fine then I got a error after aroma finished but it allowed me to go back to recovery then I rebooted system and now stuck on the T-Mo screen. Fixing to Odin and try again.
Good be that you guys got a bad DL. I and a lot of others flashed it with no issues. Seems like you're doing the right steps. So re-DL and try again. I was on ext4 and it was not an issue. Also I didn't wipe or set mounts. Just did it through the installer(thanks again FB). Painless.
Yeah it didnt give me an error tho. Lol and i couldnt get into cwm. Ive tried the releases before ravers final and it did the same thing. Except i did flash black edition once but that was before the hybrid.
Sent from my SGH-T959V using XDA App
I was experiencing the same problem with the Valhalla Black Final w/ Aroma installer. After the installer finished I flashed Bhundven's kernel again before I performed a reboot and that seems to have done the trick! I will work with it a little more in order to be sure of what is causing the problem.
---------- Post added at 02:33 PM ---------- Previous post was at 01:52 PM ----------
I tested it out, it really seems it might be an issue with the kernel installing from the Aroma installer. Here is what I did in order to install Valhalla Black Final (Final.zip) fresh from scratch.
1. Flash SMS KJ6 (beta2d) Kernel Stock Rom with Bootloaders by Bhundven.
2. Wait 10 minutes after reboot, and then shut down the device.
3. Boot into CWM, flash Bhundven's Subtly Modified Stock with CWM5 - Beta 3.1 RC.
4. Reboot phone, let it sit for a bit, and then shut down the device again.
5. Boot into CWM, wipe cache/dalvik cache, set mounts as UMMU and format /cache, /system and /data.
6. Set mounts and UMMU once again as formatting changed them, and select Final.zip for flashing.
7. Choose Custom install. Deselect the Install Kernel option. Everything else I selected, even to wipe the /cache, /system and /data again. Modem too.
8. Flash, then reboot.
I wrote this out while waiting 10 minutes for the cache to build, so I'm going to check it out now. I hope this may have helped.
/end first post ever
did you enable Lagfix first?
Sent from my SGH-T959V using xda premium
I did not touch the Voodoo Lagfix setting whatsoever during the install that froze on the boot screen, nor the install which I outlined above. Those were my precise steps, nothing omitted or added to it. When I performed the beta2d Kernel Stock Rom in Heimdall the partitions were indeed converted to ext4, and I verify this by typing 'mount' in terminal. Voodoo lagfix in CWM is listed as Disabled, but I hear that it is a bug with that version of CWM? Of course, correct me if I am wrong.
The -only- thing I changed between a frozen install and working install was deselecting the option to install the kernel in the Aroma installer.
Holocene said:
I did not touch the Voodoo Lagfix setting whatsoever during the install that froze on the boot screen, nor the install which I outlined above. Those were my precise steps, nothing omitted or added to it. When I performed the beta2d Kernel Stock Rom in Heimdall the partitions were indeed converted to ext4, and I verify this by typing 'mount' in terminal. Voodoo lagfix in CWM is listed as Disabled, but I hear that it is a bug with that version of CWM? Of course, correct me if I am wrong.
The -only- thing I changed between a frozen install and working install was deselecting the option to install the kernel in the Aroma installer.
Click to expand...
Click to collapse
If you try the install again at the end of the installation you're given an option to save a log. Please save it and send it to me as I'm trying to debug this. Thank you.
my advice is to start from scratch
install gb stock using heimdall one click collection
install bhudven kernel using SGS flasher from market
flash rom (valhalla black)
and waaalaaaahhh!!
Sent from my SGH-T959V using xda premium
goddi2010 said:
Seventh i went to mounts and formatted /system /cache /data
Eight i made sure it was set to ummu
Click to expand...
Click to collapse
If I remember correctly, from the original OP these are out of order. Change mounts to UMMU THEN format /system /cache /data and don't look at mounts again, they will change after the formats.
redownload the black edition and just install in cwm
no wipes
no mounts
just directly install zip from SD card
and aroma installer will open up and just follow the instructions
Sent from my SGH-T959V using xda premium
Ill try again this time ill save the log
Sent from my SGH-T959V using XDA App
OK so I'm confirming the method of installing without flashing the kernal worked for me
Sent from my SGH-T959V using XDA App
goddi2010 said:
OK so I'm confirming the method of installing without flashing the kernal worked for me
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
What rom were you coming from? What kernel were you using?
I was on VAL final by whitehawk. With bh's rc1 kernal, the newest one on his thread in Dev section.
Sent from my SGH-T959V using XDA App
Running cm10 official 9-13 with latest ktkernal. Had the problem last few flashes of official nightlys. Happened with both clean and dirty flashes. Reflashed gapps doing cache ans dalvik wipes after and before when one didnt work. Any idea?
Have you made sure you flashed the correct version of Gapps for your device and Rom?
Yes using cm10 so flashed signed gapps-jb-7/26
Sent from my SCH-I535 using xda app-developers app
What I'm thinking, is maybe the latest nightly has a bug in which it force closes the app. In which case, you'd have to report it to the developer.
Unless I'm missing something.
I've been tinkering with androids for well over a year now and have rooted unlocked and s-off'ed amongst other things many different devices. For some reason I'm having trouble flashing kernels to my s3. Yes I'm unlocked and yes I'm flashing aosp kernels to aosp roms and touchwiz kernels to touchwiz roms. The problem seems most persistent on aosp roms and yes I've also checked that they both had the same cm10 commits. The only kernel I could get to boot was clean kernel on beans custom. Other than that no other kernels will work. The device will boot then the screen will start glitching up and then eventually bootloop. I've also made sure to wipe dalvik and cache plus fix permissions. I've also tried just flashing the kernel after doing a full wipe and starting with a new rom and have root 66ed back to stock and re unlocked. Is there something I'm missing here? I'm getting frustrated as I love custom kernels. Oh and the latest combo I tried was liquid smooth rc3 and lean kernel 1.0. Thanks guys.
Sent from my SCH-I535 using xda app-developers app
did you try wiping cach, davik cach, and fix permissions AFTER flashing then reboot?
Ofc wipe cach and dalvik cache before also.
My usual process goes something like this
*Wipe Cache
*Wipe Dalvik
*Flash Kernel
*Wipe Cache & Dalvik again
*Fix Permissions
Works like a charm every time.
Samsung Galaxy S3
i have had the same trouble once...fixed it by flashing back to a stock kernel first.
try this:
wipe cache & dalvik
flash stock kernel.zip- http://db.tt/ceeDTAfz
flash custom kernel
reboot
Is that the stock cm10 kernel or touchwiz? Also yes I've tried wiping before and after and fixing permissions. So weird and its driving me nuts. I miss having awesome battery life
Sent from my SCH-I535 using xda developers app
sumredhed567 said:
Is that the stock cm10 kernel or touchwiz? Also yes I've tried wiping before and after and fixing permissions. So weird and its driving me nuts. I miss having awesome battery life
Sent from my SCH-I535 using xda developers app
Click to expand...
Click to collapse
stock kernel = stock TW kernel
Sent from my SCH-I535 using xda app-developers app
Tried flashing the stock kernel still same thing. It's so weird. It will begin to boot and then boot animation will start flickering or flashing then glitch up. With every kernel it's the same result.
Sent from my SCH-I535 using xda app-developers app
sumredhed567 said:
Tried flashing the stock kernel still same thing. It's so weird. It will begin to boot and then boot animation will start flickering or flashing then glitch up. With every kernel it's the same result.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
another thing you might try is formatting system in cwm.
droidstyle said:
another thing you might try is formatting system in cwm.
Click to expand...
Click to collapse
I've tried that a few times when doing a fresh rom install. I mean root66ing through odin should completely wipe everything. I just don't see what I'm missing. I've even tried using a different recovery and still the same. Could it just be something specific to my phone? I'm so freaking stumped!!
sumredhed567 said:
I've tried that a few times when doing a fresh rom install. I mean root66ing through odin should completely wipe everything. I just don't see what I'm missing. I've even tried using a different recovery and still the same. Could it just be something specific to my phone? I'm so freaking stumped!!
Click to expand...
Click to collapse
now when you odin back to stock, your booting into stock recovery after flashing the rom(root66) and doing a data wipe/factory reset correct? you said full wipe, but just want to be clear. it may be corrupted internal memory and might need to be reformatted.
I actually don't think I was wiping after I used Odin. I'll try that as soon as I get home. Though I have done plenty of factory data resets and system wipes, just not right after I odined. And you mentioned formatting how would I go about doing that?
Sent from my SCH-I535 using xda app-developers app
sumredhed567 said:
I actually don't think I was wiping after I used Odin. I'll try that as soon as I get home. Though I have done plenty of factory data resets and system wipes, just not right after I odined. And you mentioned formatting how would I go about doing that?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
follow section 6 of my guide...link in sig!
Always perform a full/mega wipe as:
1) Wipe data/factory reset
2) Wipe cache partition
3) Wipe dalvik cache
4) In mounts/storage section wipe /system
5) wipe /data
6) wipe /cache
7) wipe /preload
Then flash new ROM.
For flashing a kernel, please perform steps 2 and 3.
I have couple of question and need some help. With the new AOKP nightlies being release every 3 days or so, I would like to stay updated on them. So when I download them and proceed to update and flash over the old nightly. (Wipe Cache, Wipe Dalvik Cache) Upon reboot everything is gone icluding Gapps and seems that it instead of just updating the rom and keeping everything, It updates everything and wipes clean as if it was a fresh flash instead of a update flash ("Dirty flash"). Does anybody know why this happens? Is it that with the AOKP nightlies, you just have to always do a clean install and flash?
MichaelDrakeMS said:
I have couple of question and need some help. With the new AOKP nightlies being release every 3 days or so, I would like to stay updated on them. So when I download them and proceed to update and flash over the old nightly. (Wipe Cache, Wipe Dalvik Cache) Upon reboot everything is gone icluding Gapps and seems that it instead of just updating the rom and keeping everything, It updates everything and wipes clean as if it was a fresh flash instead of a update flash ("Dirty flash"). Does anybody know why this happens? Is it that with the AOKP nightlies, you just have to always do a clean install and flash?
Click to expand...
Click to collapse
When I do this it causes my keyboard to f/c but my apps are still there
Sent from my Galaxy Nexus using xda app-developers app
dustinhayes93 said:
When I do this it causes my keyboard to f/c but my apps are still there
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I can see why the keyboard won't work. That might be due to having to re install Gapps. But I don't understand why every time I update to the new nightlies, all my stuff is gone and it's like a full wipe fresh install/flash. Does anybody know how to avoid this from happening? Or is it that AOKP nightlies won't allow these types of updates.
I don't think there is a way around this. I've been using aokp for awhile and i just keep all my apps backed up so i can restore them after install.
Okay. Thank you for the help.
Sent from my One X using xda app-developers app