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
Related
Ok so im new and I flashed my SGS4G using these directions to a T!
i would start with krylon final cwm. his directions are pretty straightforward. i used root explorer to move the file where it needed to be.
http://forum.xda-developers.com/show....php?t=1099374
i am assuming you downloaded the rom already from the CWM rom section in the bible. its up to you. im biased towards bionix frost, but black ice is just as amazing.
i would also dl the ext converter and bali 3.1 kernel as well. (http://forum.xda-developers.com/show....php?t=1123039) (http://forum.xda-developers.com/show....php?t=1080871). place all of the zip files you download into the root of your sd card....which means that if you connect your phone to the computer and open it using windows explorer, it is that first window, which lists all of the folders. dont put these files in folders or anything.
once that is done, i restarted my phone in recovery shutting down fully and pressing the power+volume up+volume down. once there, i went to reinstall packages to get into cwm.
then when this loads, i wiped the system/factory reset and wiped the cache. then i went to mounts and storage and mounted my system. (the final mounting output should be: unmount, mount, mount, unmount). i then scrolled to "go back"
i choose install zip file from sd card. choose zip file, which should be the second option if my memory serves me right. scroll of ext converter and install that one. then when that is done, go back to install file from sd card, choose black ice or frost (i LOVE frost) and install that one. then when that is done, i flash my bali 3.1 uv kernel. when that is flashed, i click go back and choose reboot system. once that is done, you will see the galaxy s screen for like 5 min or so followed by the team whiskey logo. once you see this, it will take another minute or so to load up. once you see that the rom loads up...LET THE PHONE SIT FOR 10 minutes. i know it seems long, but just let it sit.
after 10 min or so, i would go into your about phone options and check and see that you have bali3.1 and that the rom is correct.
do these tweaks as well
fugu (http://forum.xda-developers.com/show....php?t=1127069)
init.d (http://forum.xda-developers.com/show...ghlight=init.d)
you can flash a modem too (http://forum.xda-developers.com/show....php?t=1117331) using the same process as flashing any other zip file.
remember, the first option in choosing a zip file is update.zip from krylons final cwm. do not flash this after the rom/ext/whatever. im not sure if this has been addressed (im still a noob), but everytime i did that, i bricked my phone. lol. so just to answer your question before you wonder...cause i always wondered whether i should flash that or not. lol.
But after all this I get stuck at the galaxy S screen for more than 5minutes although it will let me back into recovery mode. Its called the "CwM voodoo lagfix recovery v3.0.2.8x" and then gives me a list of options. WHAT SHOULD I DO???
I would ODIN back to KD1 and redo it, but really make sure you have the mounts correct (I know you checked this already, but check it again.) If it still does not work, then I would still go back to KD1 and then try it again by re-downloading all the zip files again. That's what I had to do.
Those were my directions! Was my fault. Ext4 needs a supported kernel. You have one now. Go back into cwm and retry everything starting from wiping the cache and system. sorry about that.
Check your mounts after the ext4 converter just to be safe.
Sent from my SGH-T959V using XDA Premium App
Also, don't worry, we've all soft bricked at one point.
Sent from my SGH-T959V using XDA Premium App
ok i restored my phone back to factory settings last night.. So what do i need to download that i didnt last night so this darn thing works???
Yeah haha well im just gld i was able to fix it without odin. thats sounds like a pain... Any Jager555 i noticed youre running Bali 3.1 UV voodoo I downloaded the bail v3.1 voodoo is that why it didnt work?
jager555 said:
Also, don't worry, we've all soft bricked at one point.
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
No, it didn't work cause you were coming off of stock. The ext4 converter needs a compatible kernel...which you didn't have. Now that you have that red cwm, you are running a compatible kernel. So everything should work now. Reflash everything like I started before after you wipe everything. It should work ok. Like I said it was my fault for not mentioning that, not something you did.
Sent from my SGH-T959V using XDA Premium App
If you are no longer on the bali kernel, flash bionix, so you have bali 2.1, and then flash everything according to my directions. Ext4 will only work if you have the compatible kernel.
Sent from my SGH-T959V using XDA Premium App
Ok so I went into recovery mode and it brought me to the red voodoo screen now should i go into mounts and storage and change that stuff again or what should i do first???
jager555 said:
If you are no longer on the bali kernel, flash bionix, so you have bali 2.1, and then flash everything according to my directions. Ext4 will only work if you have the compatible kernel.
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
wipe the data and cache. check mounts. flash ext4. check mounts. flash bionix. flash 3.1. go back. reboot system from cwm. wait. let me know how it goes. i'll be online.
Ok i just followed your directions again. But should i flash Bali 3.1 again if i removed it?
archerpro12 said:
Ok so I went into recovery mode and it brought me to the red voodoo screen now should i go into mounts and storage and change that stuff again or what should i do first???
Click to expand...
Click to collapse
once you flash bionx, it replaces the kernel with 2.1, so yes. reflash 3.1
crossing my fingers...hoping it works...
any updates??
my phone is now flashed with bionix frost! thanks a million jager555 team whiskey drhonk and anyone else involved!
jager555 said:
once you flash bionx, it replaces the kernel with 2.1, so yes. reflash 3.1
crossing my fingers...hoping it works...
Click to expand...
Click to collapse
remember to leave it for about 10 minutes (i know its hard to do that)
check out my first post and look into the fugu and init.d tweaks.
glad to help. this community is awesome.
I get a viibration of FC's but its on the bootloop of the android dude popping out... i checked my mounts its UMMU... and i wiped, mounted, odind back....so confusinG
Odin to kc1 and reflash.
Sent from my SGH-T959V using XDA Premium App
Its not confusing I flash different roms about 50 times a day and I never bootloop, try flashing the ext4.converter before the rom or enable voodoo, also make sure you havent flashed whitehawkx kd1
sent from my sgs4g 2.3.3, finally
did you fix the bootloop? i hope you tried again with icbinb because it is really smooth.
Flash the ext4 converter, then icbinb, then try. If that doesnt work, do same steps then flash bali 3.3 uv kernel afterwards
Sent from my SGH-T959V using XDA Premium App
mine's doing the same thing.. here's what I did
ODIN'd back to KC1 with root to start fresh (had whitehawx KD1), and pushed the CWM recovery file to system/bin.
quick booted to recovery, wiped system and data, checked mounts (UMMU), and flashed the final.5 from the zip. Everything seemed to go okay and it said flash was successful.
Rebooted phone, and it got stuck on the green android boot animation. during this time, the phone would buzz, then a few seconds later, do 3 quick buzzes, like something force-closed.
So I rebooted back to recovery (now RED CWM), enabled voodoo lag fix, checked mounts (UMMU), and rebooted. This time, the Linda voice came on and said some stuff and a bit later I believe she said "lagfix enabled", then it proceeded to the green android boot animation, where it's doing the same loop+buzzing thing for the last 10 mins.
where did I go wrong?
Click to expand...
Click to collapse
Alright thanks guys!! Imma try it out!!
Sent from my SGH-T959V using XDA App
i literally just reflashed to icbinb. i odined to kc1. let that load. got cwm final and then i flashed bali 3.3 and rebooted the phone normally. once that loaded up, i went back into recovery, factory reset, wiped cache, checked mounts and flashed the ext4 converter. then i flashed icbinb.5. then i rebooted into recovery to make sure lagfix was enabled (it was for me because of the ext4...this is just to make sure it flashed properly) and then went back into the menu and i rebooted normally.
It worked!!!!!!! Thanks jager!!!! :d dsexton the ext4 converter worked <3333333 so sexy!
trying your steps right now and after flashing kc1 i go to recovery with cwm and hit reinstall pckgs,it doesnt load cwm.what do i do??
you dont have krylons final cwm. look for it under the mod section of the bible. once you put the recovery file in the bin folder and the update.zip in the root of the sd, try going to reinstall packages again.
BROKEN!!
i finally got this rom installed and now im getting constant messaging.mms fc's and google framework services,and NON STOP!!
Wipe cache, dalvik cache, and fix permissions. See if that helps
Sent from my SGH-T959V using XDA Premium App
jager555 said:
i literally just reflashed to icbinb. i odined to kc1. let that load. got cwm final and then i flashed bali 3.3 and rebooted the phone normally. once that loaded up, i went back into recovery, factory reset, wiped cache, checked mounts and flashed the ext4 converter. then i flashed icbinb.5. then i rebooted into recovery to make sure lagfix was enabled (it was for me because of the ext4...this is just to make sure it flashed properly) and then went back into the menu and i rebooted normally.
Click to expand...
Click to collapse
wonderful instructions!! thanks alot! this really helped stop the vibration crashes i keep having.. just as soon as i think things are about to stabilize
I followed jagers instructions exactly and I'm stuck on the Galaxy S 4G screen (white text) with the Samsung logo at the bottom. I heard Linda after I did my reboot and now I'm stuck on this. I started with KC1 and followed all of the steps. Not sure what else to do here.
Ok, I wiped cache/davlik cache/fixed permissions and I have the green android dude. I might be up again...
Edit: Nope, starting over again with those exact instructions...
Finally booted...man, these Samsung phones are ridiculous compared to HTC!
Is everything running ok now?
Sent from my SGH-T959V using XDA Premium App
jager555 said:
Is everything running ok now?
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
Yep, thanks again! I really like the rom a lot...definitely worth the work now that it's running and I restored all of my apps through Titanium.
One question about TW4.5, how can I swap out the 4 default icons on the bottom of the home screen? Or do I need to grab another launcher?
push the CWM recovery file to system/bin?
okay i odin to kc1 but how do push the CWM recovery file to system/bin.
Download root explorer and move the file
Sent from my SGH-T959V using XDA Premium App
thanks i got now lets try and flash this baby
is anyone else having issue on flashing clock work on the sidekick 4g? it keeps saying that it flashed but when i boot into recovery still stock recovery. is there any other way i could flash a rom thanks
david1985 said:
is anyone else having issue on flashing clock work on the sidekick 4g? it keeps saying that it flashed but when i boot into recovery still stock recovery. is there any other way i could flash a rom thanks
Click to expand...
Click to collapse
this question should definitely go in the General section or in the Clockwork Recovery thread, just so you know
if you are in stock recovery, you can get into Clockwork by choosing 'reinstall packages', provided that you have followed the instructions in the CWM thread and: 1) replaced the recovery in system/bin with the modified recovery binary from the thread, and 2) placed the update.zip from the thread on the root of your sdcard.
or u can follow sduvick mod on krylon thread
nice! I didn't know he made a script for flashing CWM.
Can someone tell me why every time I try to flash a new rom on my daughters sk4g in recovery it goes straight to the screen with reinstall packages so I pick it and it errors out and can't go further???
Sent from my Sensation using XDA App
What rom are you flashing, and how are you flashing it?
Sent from my SGH-T839 using xda premium
ksnexusone said:
Can someone tell me why every time I try to flash a new rom on my daughters sk4g in recovery it goes straight to the screen with reinstall packages so I pick it and it errors out and can't go further???
Sent from my Sensation using XDA App
Click to expand...
Click to collapse
You probably need to visit the Recovery CWM thread and either manually replace the recovery in system/bin with the modified one and put the update.zip(clockworkmod) on the root of you sdcard... Or use sduvick's script in the thread to do those 2 things for you. Then when you reinstall packages it will take you to Clockwork Recovery.
I cant get passed the WipeData/factoryreset.
replaced recovery in System/Bin
Update.zip in root of SD.
this is what i get
--Wiping data...
Formatting /data...
Formatting /cache...
Formatting /sd-ext...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
Formatting /sdcard/.android_secure...
then thats where it freezes then i gotta restore using ODIN.
any help would be greatly appreciated
HECTOR-ZERONI said:
I cant get passed the WipeData/factoryreset.
replaced recovery in System/Bin
Update.zip in root of SD.
this is what i get
--Wiping data...
Formatting /data...
Formatting /cache...
Formatting /sd-ext...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
Formatting /sdcard/.android_secure...
then thats where it freezes then i gotta restore using ODIN.
any help would be greatly appreciated
Click to expand...
Click to collapse
are you wiping data in the blue stock recovery, or in the orange ClockworkMod recovery?
yogi2010 said:
are you wiping data in the blue stock recovery, or in the orange ClockworkMod recovery?
Click to expand...
Click to collapse
In orange CWM
Sent from my SGH-T839 using XDA Premium App
HECTOR-ZERONI said:
In orange CWM
Sent from my SGH-T839 using XDA Premium App
Click to expand...
Click to collapse
hmm, that's weird. and you are getting into orange CWM by doing 'reinstall packages' in the blue stock recovery? if so, I'm not sure why that would be happening...
Yeah I guess I'm S.O.L
Sent from my SGH-T839 using XDA Premium App
Try to odin back to kd1 or kg2, Then use the recovery from krylons thread. This part is important, do not use rom manager to update your recovery, the version on rm is either corrupt or unstable. This happened to me a couple of time when I first tried it too. The problem was rom managers recovery.
Sent from my SGH-T839 using xda premium
Should I completely delete CWM on my SD card then, and then repeat the process on krylons thread?
Sent from my SGH-T839 using XDA Premium App
Yes, do exactly that, delete all cwm files you have on your computer and sdcard, and start all over, using krylons thread.
Ok Just need to confirm this
When I rebooot to recovery. I get the original. screen with two errors. However when I click reinstall packages. It shoots me to CWM. IT does that every time.
Am I safe to Flash? Or did I mess up some where
---------- Post added at 01:45 AM ---------- Previous post was at 01:39 AM ----------
[/COLOR]
david1985 said:
is anyone else having issue on flashing clock work on the sidekick 4g? it keeps saying that it flashed but when i boot into recovery still stock recovery. is there any other way i could flash a rom thanks
Click to expand...
Click to collapse
I am having the same problem with clockworks recovery mod but if I go to recovery from rom maniger app I got from the market it gose right into the clockworks recvery if I use any other app for rcovery it go into stock recovery and thin I have to reinstall pacage and thin it works but that's what I know about it and I fallowed the thread to the letter
if you installed rom manager, then you didnt follow the thread. go to settings/applications/manage applications and under 3rd party, select rom manager. when that comes up, select clear data and uninstall. do NOT reinstall rom manager. next, go to the root of your sd card and look for a folder named clockworkmod. if you find it, delete it. next, go back to the cwm thread and in the first post, look for a link to a file called update.zip. download it and place it on the root of your sd card. to get into cwm, boot into stock recovery and select reinstall packages. you should then boot into cwm. there is no other way to boot into clockworkmod recovery unless you flash a rom that comes with it. the version of clockworkmod that flashes through rom manager does not work right. also, once you have booted into cwm recovery after installing it the proper way, scroll down through your recovery menu and select advanced. then select fix permissions. it will say "fixing permissions...." and will sit for a minute or two. let it sit till it says "done!" then hit the back button and select reboot system now. running fix permissions should stop your random reboots. it did for me. it wont solve the screen lag, but you shouldnt have any more random reboots.
ok i did that. now the cwm do you have to reinstall it evry time you go to recovery or will it stay and the rom manager i got it after i flashed cwm becous it sead it had cwm built in
you have to reinstall packages every time. rom manager isnt gonna do crap for you on this phone. you can flash roms through clockworkmod just fine as long as you do it right, but if you try to start flashing a rom through rom manager, its gonna brick your phone. you can recover from a brick in several ways, but its a pain in the chops.
Hi!I just can figure whats wrong with the phone.I am very sorry to have to post this but this is what i have done until now:
-it was original t-mobile sgs4g soft 2.3.6
1. i downgraded to froyo
2. tried to apply the froyo cwm recovery
3. didnt worked (dunno why)
4. installed another version with odin http://forum.xda-developers.com/showthread.php?t=1193751 the cwm worked but it kept having cant mount sd card
5. installed the new cwm with kernel ..didnt worked same thing
6.installled again the froyo with odin
7. finnaly worked installed the octane
8. octane froze at sgs4g screen ,not boot animation , kept reseting
9. 3 flashes and froyo and bla bla after i installed the black valhalla
10. valhalla works but i cant recieve calls sms or mms...
11. Need help!
Don't flash GB stuff on froyo boot loaders. Don't flash froyo stuff on GB boot loaders. If don't know how to repartition with a pit don't flash boot loaders as boot loader flashes may hard brick your device. If your unsure about what your flashing matching your boot loaders don't flash it. Finally all your mixing and matching incorrectly probably got you some weird gremlins so learn how to"one click" back to stock (I wrote a noob guide in general section) and start over. This will ensure GB boot loaders are flashed correctly good luck
Sent from my SGH-T959V using XDA App
I agree one click is probably your best bet. I do however wonder if you somehow managed to wipe your imei? Check to make sure.
ok so i downloaded the T959V-UVKJ6-One-Click tommorow i will do it bcoz its not my phone...question how do i install custom recovery to install the Octane-V3.0 XPLOD NO CIQ EDITION
and will i get rid of the call and sms not being recieved?
hechoen said:
I agree one click is probably your best bet. I do however wonder if you somehow managed to wipe your imei? Check to make sure.
Click to expand...
Click to collapse
Did you check this? Don't post it just make sure it is not a string of 0s. It is very important...
charris said:
ok so i downloaded the T959V-UVKJ6-One-Click tommorow i will do it bcoz its not my phone...question how do i install custom recovery to install the Octane-V3.0 XPLOD NO CIQ EDITION
Click to expand...
Click to collapse
If you get the "kj6 beta 2d" package it includes a custom kernel with cwm recovery
Sent from my SGH-T959V using XDA App
sorry forgot to mention this i can make calls or send txt and i remember it having an imei as i scrolled down in about phone> status
I was having some problems with little things in octane also, but what fixed mine was wiping the cache, dalvik cache, flashing, ( mounts UMMU), reboot, check functionality, reboot into cwm, fix permissions, reboot, enjoy.
Sent from my Octane powered, Thunderbolt tweaked SGH-T959V using xda premium
ty problem solved u can close it or erase it ty very much
No matter what custom rom I try to load on my G2X, it will go through, install the rom, and then when it reboots past the LG screen, it gets to whatever custom boot screen in on the rom, and just locks up. The only way I can get it to boot after that point is to NVFlash back to stock.
Tried searching through this site and google, but can't find a solution.
You need to say what the process is that you attempted to do. Wipes and what not.
Sent from my SGH-T999 using xda premium
mt3g said:
You need to say what the process is that you attempted to do. Wipes and what not.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Rooted phone, added Clockwork, booted into CW recovery, did data and cache wipes, installed CM7 from SD card, rebooted, phone froze at custom boot screen. Reboot, still frozen. Would not boot at all.
Used NVFlash to reinstall stock image on phone, rooted phone, CW recovery, data and cache wipes, installed a different rom for my phone model, same result. Back to stock using same process, tried a third rom using same process, same result, frozen phone that won't go beyond boot screen.
Using this same process on my old T-Mobile Samsung Vibrant, it worked perfectly on several different roms.
It sounds like you may have a ROM for a different model phone. Can you send a link to the ROM that you downloaded for us to see?
Also, is your phone a T-Mobile G2x or an LG Optimus 2x (O2x).
cyansky_1 said:
It sounds like you may have a ROM for a different model phone. Can you send a link to the ROM that you downloaded for us to see?
Also, is your phone a T-Mobile G2x or an LG Optimus 2x (O2x).
Click to expand...
Click to collapse
It is a T-mobile G2X, LG-P999DW.
The CM7 link was straight from the CM7 site, it wasn't an experimental mod or anything, it was the stable one listed under the G2X.
http://www.cyanogenmod.com/devices/t-mobile-g2x
ParanoidAndroid via this thread on here: http://forum.xda-developers.com/showthread.php?t=1762647
Domination via this thread: http://forum.xda-developers.com/showthread.php?t=1570017&highlight=domination
Considering cm roms are supposed to wipe system prior to flash, I couldn't imagine what is going on. Try wiping system just in case and after that, try installing from internal as well. Other options would be download other ways, like on PC or from phone transfer the files differently. Other then that can't really help you.
Sent from my SGH-T999 using xda premium
mt3g said:
Considering cm roms are supposed to wipe system prior to flash, I couldn't imagine what is going on. Try wiping system just in case and after that, try installing from internal as well. Other options would be download other ways, like on PC or from phone transfer the files differently. Other then that can't really help you.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
The last time I pulled it directly on my phone, the other times I downloaded via my PC and then copied the file. Had been via external so I tried internal that last time too. I'm close to madness, but I'm also too stubborn to give up.
I was thinking maybe I need to replace the kernel, but I'm not sure whether that's the problem or which Kernel to try if I did need to.
I had a similar issue on a tablet of mine. What version of CWM are you using? Are you using the touch version? The touch version has had some boot problems. Did you try partition the SDCard in the advanced settings? I forget which I used on my phone. Has anyone else partitioned theirs?
Well, not knowing which peice is broken let me just recap my process for you and see how it works:
1. Use OneClick NVFlash from http://forum.xda-developers.com/showthread.php?t=1056847 and select Flash CWM 5.0.2.0
2. Boot to CWM
3. format cache
4. format data
5. format system
6. format Dalvik cache
7. flash ROM from external/internal memory
8. flash kernel (optional, not required unless doing kernel testing)
9. flash gapps-package
10. fix permissions
11. reboot
I have not had this process screw up once for me so far. If this process does not work for you then you leave me really be scratching my skull...
Sooper1138 said:
Rooted phone, added Clockwork, booted into CW recovery, did data and cache wipes, installed CM7 from SD card, rebooted, phone froze at custom boot screen. Reboot, still frozen. Would not boot at all.
Used NVFlash to reinstall stock image on phone, rooted phone, CW recovery, data and cache wipes, installed a different rom for my phone model, same result. Back to stock using same process, tried a third rom using same process, same result, frozen phone that won't go beyond boot screen.
Using this same process on my old T-Mobile Samsung Vibrant, it worked perfectly on several different roms.
Click to expand...
Click to collapse
don't root and then try. mostly roms come with super user access so try without rooting it manually.
Sent from my LG-P999
cyansky_1 said:
Well, not knowing which peice is broken let me just recap my process for you and see how it works:
1. Use OneClick NVFlash from http://forum.xda-developers.com/showthread.php?t=1056847 and select Flash CWM 5.0.2.0
2. Boot to CWM
3. format cache
4. format data
5. format system
6. format Dalvik cache
7. flash ROM from external/internal memory
8. flash kernel (optional, not required unless doing kernel testing)
9. flash gapps-package
10. fix permissions
11. reboot
I have not had this process screw up once for me so far. If this process does not work for you then you leave me really be scratching my skull...
Click to expand...
Click to collapse
Using this method in exactly this order worked perfectly. Thank you very much.
Sooper1138 said:
Using this method in exactly this order worked perfectly. Thank you very much.
Click to expand...
Click to collapse
Did you notice what he didn't do.
Sent from my LG-P999