Related
Hi all,
I have a routed DHD and have used the advanced ace hack kit, everything went well and the root was successful.
Now when I'm trying new roms from XDA the problem is that for 1 week the rom work absolutely fine and after that suddenly it is in bootloop and then I have to change the rom.
I have tried the following roms:
1) Core Droid v9.2
2) Lee latest rom v5.1.1
3) virtuoso affinity latest build
4) bindroid
n a lot more but still having the same issue.
Right now I'm on ARHD 6.3.1
Requesting a sincere help from the dev community....!!
Sent from my DHD using XDA App
Look at what mods you do or what you install..must be some kind of trigger maybe..have u updated Rom only not radios kernels etc etc?
Sent from my Desire HD using XDA Premium App
apart from installing the roms i haven't touched on anything....as i'm new to all this.
Try cyanogen for a while..have you flashed any roms without sense?
Sent from my Desire HD using XDA Premium App
Hmm, strange. What about ROM internal modifications or options?
As you tried LeeDrOiD 5.1.1 you seem to have that problem not always after 1 week (cause it's not that old *g*), so what about trying this:
of course make a backup of your data
full wipe your device (you can make sure to do it right by using a full wipe script
install a new rom and fully boot it
keep running it for a day without reinstalling your preferred apps
keep installing the apps step by step and watch the system's behaviour
When installing your new ROM and setting it up again, do you restore any data by using tools like Titanium Backup? If so, do you also restore system data or apps (+ data) only?
PS: maybe edit your topic's title to something better like "Problems with fresh installed custom ROM after a few days" or so.
unhallowedone said:
Hmm, strange. What about ROM internal modifications or options?
As you tried LeeDrOiD 5.1.1 you seem to have that problem not always after 1 week (cause it's not that old *g*), so what about trying this:
of course make a backup of your data
full wipe your device (you can make sure to do it right by using a full wipe script
install a new rom and fully boot it
keep running it for a day without reinstalling your preferred apps
keep installing the apps step by step and watch the system's behaviour
When installing your new ROM and setting it up again, do you restore any data by using tools like Titanium Backup? If so, do you also restore system data or apps (+ data) only?
Click to expand...
Click to collapse
Right now on ARHD 6.3.1...so far so good...!!
Neways...will try to do it ur way...and will check to see which app is creating this issue....!!
whereas read the LeeDroid forum and came across certain post regarding TB giving problem to certain users....!!
For now uninstalled the same... .
arknailed7754 said:
Try cyanogen for a while..have you flashed any roms without sense?
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
Have used MIUI and worked well for at least 1 week...but got bored of it as was really missing sense...!!
But will try this option too...!!
CyanogenMod is a free, community built distribution of Android 4 (Ice Cream Sandwich) which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is the official nightly build of CM9 for the Galaxy S3 on T-Mobile. It's not a final release yet, but it's perfectly fine as a daily driver.
Known issues being worked on:
* LED is a little derpy
* Camera occasionally freezes
Install instructions:
1. Install ClockworkMod Recovery for "d2tmo". Sorry, CM cannot provide support for other recoveries, although they may work fine.
2. Get.CM for "d2tmo"
3. Reboot into recovery and install
(or just use ROM Manager)
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
This build is nearly complete and should make it into the 9.0 final release on time. We are also actively working on CM10 for this device, builds available soon! Enjoy!
Yes !!!
The godfather had landed !
Any chance of you guys including some kind of file explorer ? Pretty please Steve...........
Wondering if Data transfer between Phone and PC is fixed or if just affects everyone differently.
awesome! Cant wait to give this a try. Debating if i should try cm10 first. Either way thanks for hard work and determination for this rom!
All is right in the world again.
Thanks Steve. Flashing the latest nightly now
Sent from my SGH-T999 using Tapatalk 2
FRuiTBoOT said:
Wondering if Data transfer between Phone and PC is fixed or if just affects everyone differently.
Click to expand...
Click to collapse
+1. Only problem thats keeping me from running CM9 right now.
Steve said in the unofficial nightlies thread that he fixed MTP in the 0717 nightly so flash away!
http://cm9log.appspot.com/?device=d2tmo
Its the last entry in the change log at the bottom.
Sent from my SGH-T999 using Tapatalk 2
On my Nexus S, it was always recommended to do all the wipes and flash the ROM and then while still in CWM, flash the gapps. I see different instructions here and there for the S3, like flashing the ROM and then rebooting, then going back into CWM to flash gapps. Any advice for this one? Thanks!
bluecluenj said:
On my Nexus S, it was always recommended to do all the wipes and flash the ROM and then while still in CWM, flash the gapps. I see different instructions here and there for the S3, like flashing the ROM and then rebooting, then going back into CWM to flash gapps. Any advice for this one? Thanks!
Click to expand...
Click to collapse
Flash rom + gapps + kernel(if you want to). Don't need to reboot first and flash gapps.
Sent from my SGH-T999 using Tapatalk 2
I can confirm MTP is fixed in the newest nightly! :good:
im on the latest nightly 20120717 and MTP isn't working for me everything else seems fine tho
MTP is working fine for me.
The only things that are kinda buggy - camera with focusing, the LED light, and the way the phone handles notifications when you are listening to music.
ok so mtp works fine for me when i use my nephews windows computer but when i use my mac it doesnt seem to work
tmobilewinguser said:
ok so mtp works fine for me when i use my nephews windows computer but when i use my mac it doesnt seem to work
Click to expand...
Click to collapse
MTP never worked on my mac. I had to download Android File Transfer and install that on my mac and put the phone on PTP. Idk if PTP works with the newest nightly cause I have yet to hook my phone up to my mac.
djintrigue808 said:
MTP never worked on my mac. I had to download Android File Transfer and install that on my mac and put the phone on PTP. Idk if PTP works with the newest nightly cause I have yet to hook my phone up to my mac.
Click to expand...
Click to collapse
yea i got android file transfer and i have PTP checked but still no go
Wonky CWM?
So, I've been testing out all the ROMs and nothing beats pure google (debloat all you want, touchwiz sucks ass). So I've been testing out the CM9 builds. I noticed that no matter how many times I'd flash gapps (the 20120429 version) it seemed like it wouldn't take. By that I mean that other than Play Store and sometimes Talk, no other Google App would appear. It's not a big deal because I have TB of all the apps I use, so I'd just install them from backups.
BUT, on the newest nightly (coming from a wipe after rerduM), I noticed that my widgets did not show up. Not one of the widgets associated with the apps I had installed from TB were showing up. So, I thought I'd wipe again and try it. Still the same. Has this happened to anyone? Am I missing something here?
Also, is there a way to clean out the /system partition? Doing the factory reset is fine and manually formatting /data too, but is it possible and/or advisable to wipe the /system partition to sort of "start anew" with no artifacts from previous ROMs? Do installer scripts do this automatically? If so, why do I still see some setting from previous installations when I wipe and install the new nightlies?
Are LED notifications working properly yet?
Sent from my SGH-T999 using xda premium
Eh, sorry. I just looked up someone reported they aren't working correctly.
Sent from my SGH-T999 using xda premium
How many of you have gotten your IMEI's deleted after flashing the nightlies?
I'm really tempted to flash (I haven't even rooted my phone yet), but I just want to make sure I wont lose that number.
you won't lose your imei
Bunch of conspiracy theory nonsense. Backup the folder if you are the paranoid type
Sent from my SGH-T999 using xda premium
Hi, this morning I encountered something which I haven't seen before in my 3 years or so of flashing roms on Android phones. The scenario was the standard process: Root with Odin > Install CWM with Odin > Copy Rom / gapps package to sdcard > Wipe & Install rom with CWM.
I rooted my Note II using CF Auto Root, all went fine, I flashed the latest Phil's touch CWM recovery using Odin which was also successful.
I had root access and was able to do a titanium backup of apps and messages/call logs. I successfully did a Nandroid backup of the stock rom.
After wiping data through CWM as per normal, I flashed the latest Utacka ParanoidAndroid and gapps. The flash was successful, but after rebooting, the 'Samsung Note II' splash screen only appeared briefly, then the image sheared and distorted and the screen went black, in less than three seconds.
I restored my nandroid backup and repeated the process, this time also formatting system, and installing CM10.1 nightly instead of PA. Again, I got a distorted splash screen then a black screen when trying to boot.
Can anyone think of a reason why my phone does not seem to be able to boot a custom rom?
Many thanks
I read on the forum someone else had a similar issue with cm as well
Sent from my GT-N7100 using xda app-developers app
koalauk said:
I read on the forum someone else had a similar issue with cm as well
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Really? I've tried searching xda, google and the CM forums and havent found anything relevant.
I had this problem recently and after some nice guys helping me out we conclude that the solution is to flash RedPill kernel as the culprit for this glitch is the stock kernel you previously had.
I had such issue with my Note2 too. I was advised to flash Thor kernel 0.15 too after flashing cm10.1 and gapps. And problem was solved. Now cm10.1 boots normal on my Note2.
Sent from my GT-N7100 using xda premium
Did you do a factor reset.
Sent from my GT-N7100 using xda app-developers app
Hello,
I'm sorry if this is a repost of any sort . I am currently running a 4.1.2 rom and as it turns out any 4.1.2 rom that I run will have a functioning camera for my phone. However whenever I try to flash any 4.2 .2 rom on my phone the camera ceases to run correctly. I'm flashing the rom with clockworkmod touch and I have also tried flashing a camera fix I found on xda. I have even tried using third party camera apps, but those don't work either. Can anyone try to point me in the right direction or even try to help me troubleshoot this thing??
Thanks in advance
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
i'll begin with the question of what did you wipe before you flashed 4.2.2 and what ROM/release have you tried flashing?
Flash to factory stock and if ur camera still doesn't work it must logically be a hardware issue. Please guys correct me if I'm wrong
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
xBeerdroiDx said:
i'll begin with the question of what did you wipe before you flashed 4.2.2 and what ROM/release have you tried flashing?
Click to expand...
Click to collapse
I had just updated cwm to the latest touch version about a month ago. After that I was still on stock TW 4.1.1. Then, I tried flashing a 4.2.2 jellybam v7.6 and the camera stopped working so I flashed back to stock and the camera worked fine. I then tried flashing to the latest realease of CM 10.1 nightly
about 3 weeks ago but the camera didnt work so I flashed to 4.1.2 CSROM v1.4 then 1.5 and the camera worked fine. So I then tried CM10.0 4.1.2 and the camera still worked so last night I flashed to the latest CM nightly and the camera stopped working. Any thoughts?
Cprager said:
Flash to factory stock and if ur camera still doesn't work it must logically be a hardware issue. Please guys correct me if I'm wrong
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I did and it still works. So it can't be a hardware issue. It has to do with how my phone flashes the software because I haven't seen anyone else having the same issues with the ROMS that I have been flashing.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
AaronYoLungz said:
so last night I flashed to the latest CM nightly and the camera stopped working. Any thoughts?
Click to expand...
Click to collapse
if the camera stopped working simply from updating your current ROM to the latest release than a wipe and reflash could possibly have ironed out this issue. this is assuming you dirty flashed the update. we all do that, but in the event things dont funtion properly afterwards, a wipe is required.
xBeerdroiDx said:
if the camera stopped working simply from updating your current ROM to the latest release than a wipe and reflash could possibly have ironed out this issue. this is assuming you dirty flashed the update. we all do that, but in the event things dont funtion properly afterwards, a wipe is required.
Click to expand...
Click to collapse
Well before I flashed any rom I always wiped all user data, I wiped the cache and dalvik cache and in some cases I even formatted the system in advanced settings. In every case the camera never worked.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
If it could help, I can get a report of the crash... The only thing is I would need guidance on going about getting it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
i would back everything up. you have a working nandroid to fall back on?
then i would fully wipe the device and start over. you seem to be having problems with 4.2.2, not specifically aosp. it appears aosp and touchwiz 4.1.1 and 4.1.2 are working for you. correct? when transitioning android versions, its basically required to wipe everything in order to avoid issues. make sure you have the latest gapps for 4.2.2. that may be your problem right there.
in the event you choose to wipe and reflash a 4.2.2 rom,
- backup your files
- have a nandroid, the rom you want and gapps on a micro sd card.
- boot into recovery
- wipe data/factory reset
- wipe cache
- wipe dalvik
- format /system
- format /data + media
- flash rom from external sd card
- flash gapps from external sd card
- reboot and let your phone sit a few minutes then reboot again. check it out.
you wont get any ROM support from devs on your issues until you come from a complete wipe. a hassle to set everything up again but it will likely be your fix. if not, we can go a different direction.
Alright I'll try this now. I will keep you updated
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
AaronYoLungz said:
Alright I'll try this now. I will keep you updated
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
did you make sure you were flashing the correct gapps for your version of android? i'd hate to see you do all this for an incorrect gapps issue. yes, keep me posted
xBeerdroiDx said:
did you make sure you were flashing the correct gapps for your version of android? i'd hate to see you do all this for an incorrect gapps issue. yes, keep me posted
Click to expand...
Click to collapse
Alright I followed all of the above steps and my phone camera still isnt working. For clarification, gallery app works but when I actually try to use the camera I get a "Camera Error - Cannot connect to camera " popup window with an okay button below it.
AaronYoLungz said:
Alright I followed all of the above steps and my phone camera still isnt working. For clarification, gallery app works but when I actually try to use the camera I get a "Camera Error - Cannot connect to camera " popup window with an okay button below it.
Click to expand...
Click to collapse
what ROM and release did you end up flashing?
xBeerdroiDx said:
what ROM and release did you end up flashing?
Click to expand...
Click to collapse
ROM: cm-10.1-20130521-NIGHTLY-d2att
Gapps: gapps-jb-20130301-signed
EDIT: The problem described in the post#11 has always been the case
i would do 1 of 2 things: flash this 4.2 camera zip in recovery and see if that camera and gallery work or flash a different 4.2.2 ROM like tasks. this will help determine if its just cm10.1 thats giving you grief.
if you download and flash the 4.2 camera, just wipe cache, dalvik and flash the zip. in the event you get a freeze up when taking a picture with auto-focus, you have to set the scene to "Action" mode.
hit me back
xBeerdroiDx said:
i would do 1 of 2 things: flash this 4.2 camera zip in recovery and see if that camera and gallery work or flash a different 4.2.2 ROM like tasks. this will help determine if its just cm10.1 thats giving you grief.
if you download and flash the 4.2 camera, just wipe cache, dalvik and flash the zip. in the event you get a freeze up when taking a picture with auto-focus, you have to set the scene to "Action" mode.
hit me back
Click to expand...
Click to collapse
Should I remove Gallery4.apk and Gallery2.apk from /system/app?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
You can use a file Explorer to move those 2 to a different folder so that you can move them back if need be
xBeerdroiDx said:
You can use a file Explorer to move those 2 to a different folder so that you can move them back if need be
Click to expand...
Click to collapse
Alright so I ended moving the gallery, then flashing the new camera app in CWM then wiped the cache and dalvik. No luck, so I tried restarting my phone, fixing permissions, and nothing worked. I then full wiped my phone and flashed Vanilla Rootbox, tested camera and it didnt work. It still said "Camera Error- Can't connect to camera" . . I flashed the camera zip provided followed by a cache and dalvik wipe but I got the same message. Following the above steps I did the exact same thing with AOKP and the exact same thing happened.
Is it possible that my phone just can't support 4.2.2?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Is it possible that an outdated version of Odin could be the problem?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.3.1 (JB), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
WIKI
Click to expand...
Click to collapse
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/w/D710_Info
INSTALLATION
Click to expand...
Click to collapse
First time installing CyanogenMod 10.2 to your Epic 4G Touch, or coming from another ROM:
- Copy GApps and CM 10.2 zip's to your internal SD Card
- Make sure you're NOT RUNNING A KERNEL WITH THE MMC-SUPERBRICK-BUG
- Make sure you're running a proper working ClockworkMod-Recovery
- Make sure you're not running a JB modem
- Boot into recovery
- Flash CM 10.2 zip from internal SD Card
- Flash GApps zip from internal SD Card
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Upgrading from earlier version of CyanogenMod 10.2:
- Copy CM 10.2 zip to your internal SD Card
- Boot into recovery
- Flash CM10.2 zip from internal SD Card
- Reboot
Upgrading from CyanogenMod 9:
- Copy 4.3.1 GApps and CM 10.2 zip's to your SD Card
- Boot into recovery
- Flash CM 10.2 zip from SD Card
- Flash GApps zip from SD Card
- Reboot
DOWNLOAD
Click to expand...
Click to collapse
CM 10.2 official nightly builds:
http://download.cyanogenmod.org/?device=d710
Google Apps:
http://goo.im/gapps
CHANGELOG
Click to expand...
Click to collapse
http://review.cyanogenmod.org/#/q/status:merged+branch:cm-10.2,n,z
http://changelog.bbqdroid.org/#/d710/next
DONATIONS
Click to expand...
Click to collapse
If you want to donate a few bucks for the work:
Thanks to all donators!
Awesome job.oh 1st.lol
Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Click to expand...
Click to collapse
Can someone explain just what is meant by this? "Regular" apps, or "system" apps? And if it's just plain regular apps, why would it cause a problem? If it's a ROM-based app (e.g., text messaging app) or a Google-based app, I left them as is. But my Dolphin browser, for example, was restored with data...
Silentknyght said:
Can someone explain just what is meant by this? "Regular" apps, or "system" apps? And if it's just plain regular apps, why would it cause a problem? If it's a ROM-based app (e.g., text messaging app) or a Google-based app, I left them as is. But my Dolphin browser, for example, was restored with data...
Click to expand...
Click to collapse
Regular apps are installed apps from Google play or a 3rd party app store. System apps are apps that are installed in the system partition (come with the phone.) Restoring data from most system apps can cause problems (I have yet to find an answer is to why.) From installed apps, not so much.
Sent from my SPH-D710 using Tapatalk
Dastin, thanks for your hard work with this Rom/Phone. Also, I know your a busy guy with school and your girlfriend and other phones you develop with. I just wanted to say, you're a blessing to us Epic 4g Touch users. Thanks for pouring so much time and hard work into this phone. Much love to you. I'll make sure to donate to you when I get an income, as I am a Senior taking full time PSEO and never had a job before.
Long story short, I love what you're doing with this phone. I really enjoy your roms you have created! Much love to you bro!
Great job!:good:
My phone keeps trying to locate GPs though I turned gps location off. Any idea how to stop this?
Also, cool rom dastin!
Great ROM, I loaded this weekend and love it. Everything working great so far! Thanks!!!
I have to say thanks for this rom. I just loaded it this morning (along with the blasphemy kernel). So far it's running great. No reboots, lockups or any other issues. As a side note, I have been having trouble with the phantom menu and search presses on other roms including stock, all stock based roms, and every other AOSP based rom I've flashed. I've had to disable the soft keys and enable the navbar on all of them to fix this issue. I don't know what the difference is but this is the first rom I've flashed that actually worked without the phantom key presses. Thanks again. Looks like I've finally found a new daily driver.
Does anyone know if dock audio or speakerphone work with these builds? Prior jelly bean builds lacked functioning dock audio and the mics didn't pick up audio correctly in speakerphone mode such that callers report not being able to hear you loudly enough.
how do i find out if i have the kernel with the MMC-SUPERBRICK-BUG?
i am on stock 4.0.4
Thanks.
4.0.4 has the brick bug, to flash this you need to use a safe kernel
Sent from my SPH-D710 using Tapatalk
can you give me instructions on how to get the safe kernel? do i just flash a kernel on to my phone.
this is what i have:
android version: 4.0.4
kernel: 3.0.15-SPH-D710.FE22-CL612283
[email protected] #3
SMP PREEMPT Web May 23 04:10:44 KST
2012
You have to use mobile Odin to flash the safe kernel, what I use is the el29 direct boot kernel from here : http://www.rwilco12.com/downloads.p...ls/Recovery Kernels/GB/Noobnl Direct Boot/TAR
Sent from my SPH-D710 using Tapatalk
gamepro602 said:
You have to use mobile Odin to flash the safe kernel, what I use is the el29 direct boot kernel from here : http://www.rwilco12.com/downloads.p...ls/Recovery Kernels/GB/Noobnl Direct Boot/TAR
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Does this just replace the kernel? All my apps and data should still be there?
Yes it replaces your current kernel, but you won't be able to boot back into the ROM once you flash this so make sure you have the files ready, another thing is that you need to back up your apps and data because you need to erase your data to flash the ROM, I would invest in titanium backup, if you can't afford it use helium.
Sent from my SPH-D710 using Tapatalk
gamepro602 said:
Yes it replaces your current kernel, but you won't be able to boot back into the ROM once you flash this so make sure you have the files ready, another thing is that you need to back up your apps and data because you need to erase your data to flash the ROM, I would invest in titanium backup, if you can't afford it use helium.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
i am confused. I will be in the current rom to flash the kernel using mobile odin. How is it that I wont be able to boot back into the ROM? Do i need to flash another ROM after flashing the kernel? what ROM did you flash after the kernel?
El29 direct boot kernel is a kernel for just flashing Roms.once you boot into it you have to flash a ROM.if you don't and choose to reboot system it will just reboot back into the el29 kernel.so you have to download the ROM you want and gapps if using a aosp ROM.now using an aosp ROM you need an ICS modem.
Sent from my SPH-D710 using Tapatalk
gamepro602 said:
You have to use mobile Odin to flash the safe kernel, what I use is the el29 direct boot kernel from here : http://www.rwilco12.com/downloads.p...ls/Recovery Kernels/GB/Noobnl Direct Boot/TAR
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
i just downloaded it, but when i use 7zip to test it, said its not a correct archive...
cfli1688c1 said:
i just downloaded it, but when i use 7zip to test it, said its not a correct archive...
Click to expand...
Click to collapse
Don't unzip it. Just use Odin to flash it.
I don't think 7zip can handle tar files.
Sent from my SPH-D710 using XDA Premium 4 mobile app
cfli1688c1 said:
i am confused. I will be in the current rom to flash the kernel using mobile odin. How is it that I wont be able to boot back into the ROM? Do i need to flash another ROM after flashing the kernel? what ROM did you flash after the kernel?
Click to expand...
Click to collapse
Dont take this the wrong way, but you are not ready to be flashing this rom. You really need to check out the other forums on how to correctly flash for this phone. Especially since you are on 4.0.4. One wrong move and you will have an expensive paperweight on your hands.
Go do your homework and ask these questions in Q&A thread. You will get lots of help there.