The Great Debate! - Captivate General

Alright this is kind of a thread to get a discussion going. And NOO THIS IS NOT WHAT IS THE BEST ROM THREAD!
This is a thread regarding whether or not you flash back to stock when flashing new ROMs.
Personally Ive always flashed back to stock because im a Buiild 1011 and I use this thread which has worked EVERY time so if your a build 1010 this is a great way that is flawless:
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
But the debate here is whether or not you flash back to stock every time and if you dont flash back to stock tell us about your experiences flashing ROMs over each other.
Im doing this because the more I read on threads of ROMs reading and reading I always see a ton of posts arguing saying that they dont even flash stock anymore and I just want to see and hear what y'all have to say.
Would love to see the return on this and since i have Download mode JIG thanks to MobileTechVideos (fantastic!) I may flash a ROM over Darkyy that Im using currently just to see how it works.
Thanks in advance

No. Never. Why would I? I do it only if I want to run stock or once or twice when my partitioning was screwed. Otherwise it's a pointless thing to do.

opcow said:
No. Never. Why would I? I do it only if I want to run stock or once or twice when my partitioning was screwed. Otherwise it's a pointless thing to do.
Click to expand...
Click to collapse
Hm, have you ever run into a problem? And I thought you have to flash back to stock or the ROM will not install if they are a different base.
I.e. Since im on Darkyy 9.3 with the JS5 base, i couldnt just go flash Perception with a JS3 base right?
Im not trying to argue Im just wondering and Im practically unbrickable so I may try that when I get home and if I get in trouble either flash back to Darkyy and finally just use the ole Jig and flash back to stock.

I stopped flashing odin after I had to bring my 1007 phone in for warranty and got a 1008 back. No way I am flashing using odin, 1008's have bad flashing mojo. I have a nandroid of the original OS and can go back to that if I need to to start over. I even bought a jig after I got this one just in case.

Stephenv1971 said:
I stopped flashing after I had to bring my 1007 phone in for warranty and got a 1008 back. No way I am flashing, 1008's have bad flashing mojo. I have a nandroid of the original OS and can go back to that if I need to to start over. I even bought a jig after I got this one just in case.
Click to expand...
Click to collapse
First of all the nandroid WILL NOT restore your old OS because it doesnt restore anything System.
Secondly the build 1008 has a problem with the 3 button fix flash this zip if your 3 button fix gets removed. It works for everyone including me when I lost 3 button combo.
And third smart choice with the Jig I bought one just in case and it has never failed me

Dlev7 said:
Hm, have you ever run into a problem? And I thought you have to flash back to stock or the ROM will not install if they are a different base.
Click to expand...
Click to collapse
No, I have done it dozens of times with many different ROMs and never had a problem.
I.e. Since im on Darkyy 9.3 with the JS5 base, i couldnt just go flash Perception with a JS3 base right?
Click to expand...
Click to collapse
Yes, you could.
Im not trying to argue Im just wondering and Im practically unbrickable so I may try that when I get home and if I get in trouble either flash back to Darkyy and finally just use the ole Jig and flash back to stock.
Click to expand...
Click to collapse
Right. I think you'll find that it works just fine and saves you same hassle and it's safer too since you won't be unnecessarily be writing a new boot.bin and sbl.bin (DG's ROMs do include sbl.bin, however).

Dlev7 said:
Hm, have you ever run into a problem? And I thought you have to flash back to stock or the ROM will not install if they are a different base.
I.e. Since im on Darkyy 9.3 with the JS5 base, i couldnt just go flash Perception with a JS3 base right?
Im not trying to argue Im just wondering and Im practically unbrickable so I may try that when I get home and if I get in trouble either flash back to Darkyy and finally just use the ole Jig and flash back to stock.
Click to expand...
Click to collapse
Just curious why you would think flashing js5 over jf6 would be any more effective than flashing over js3 or jpy. I have yet to see an explanation other than "its recommended" or "because dg said to" so I doubt you will get any real answers from the odin crowd. Personally I haven't done it in forever.

newter55 said:
Just curious why you would think flashing js5 over jf6 would be any more effective than flashing over js3 or jpy. I have yet to see an explanation other than "its recommended" or "because dg said to" so I doubt you will get any real answers from the odin crowd. Personally I haven't done it in forever.
Click to expand...
Click to collapse
Ive never thought of it that way ever before. But the only thing ive ever heard is that Odin does stuff that the install script that these ROMS dont.
Ya and its said to say but thats the only things ive ever heard that its safer and DG said so. But in my defense does the install script on these ROMs really do the same as what Odin does?

Do either of y'all know whether or not the install script on the ROMs do replace it well.
The reason ive never done this is because I always heard that only Odin can flash over things.
But Ive seen a lot of people like y'all say all you have to do is wipe data and cache, and dalvik cache, and flash away but do the instal script in these ROMs rewrite the system?

Dlev7 said:
Do either of y'all know whether or not the install script on the ROMs do replace it well.
The reason ive never done this is because I always heard that only Odin can flash over things.
Click to expand...
Click to collapse
They delete files and format partitions just fine. If they didn't then I wouldn't have been able to go for months trying almost every ROM released without ever launching Odin. I don't know what you mean by "only Odin can flash over things." If that were the case then how would CWM flashing ever work whether you flashed stock first or not? If things are getting left behind then why would having JF6 stuff left behind be preferable?
But Ive seen a lot of people like y'all say all you have to do is wipe data and cache, and dalvik cache, and flash away but do the instal script in these ROMs rewrite the system?
Click to expand...
Click to collapse
You don't have to do that either. Check out this snippit from an install script:
format SYSTEM:
format CACHE:
format DATA:
format DATADATA:
delete_recursive SDCARD:Android
delete_recursive DATADATA:databases/com.android.providers.media
delete_recursive DATADATA:databases/com.cooliris.media
delete_recursive SDCARDCIM/.thumbnails​That takes care of deleting the cache, dalvik cache and more.

Qq
opcow said:
They delete files and format partitions just fine. If they didn't then I wouldn't have been able to go for months trying almost every ROM released without ever launching Odin. I don't know what you mean by "only Odin can flash over things." If that were the case then how would CWM flashing ever work whether you flashed stock first or not? If things are getting left behind then why would having JF6 stuff left behind be preferable?
You don't have to do that either. Check out this snippit from an install script:
format SYSTEM:
format CACHE:
format DATA:
format DATADATA:
delete_recursive SDCARD:Android
delete_recursive DATADATA:databases/com.android.providers.media
delete_recursive DATADATA:databases/com.cooliris.media
delete_recursive SDCARDCIM/.thumbnails​That takes care of deleting the cache, dalvik cache and more.
Click to expand...
Click to collapse
So technically its Is aactually safer because you don't lose 3 buttons. And since I'm a build 1011 I have to do a 30 minute procedure just to get to JH7.
So you may be right its actually safer.
Sent from my SGH-I897 using XDA App

Related

Flashing To 2.1(stock) from Cognition w/vodoo WILL CAUSE BRICK!

Hey everyone, I have desided to create a FYI post to anyone considering flashing back to stock 2.1(Eclair) using Odin if you are currently running Cognition(Froyo) roms. I have attempted flash back to stock on 4 phones(Samsung Captivate) with the same result(failing during the restoing of factoryrfs); causing the imfamous orange dump screen. This is a very serious issue which should be looked at by the devs. I am not trying to start a war or anything but the results from flashing back to 2.1 can almost always be reproduced(a bricked phone)
Atheistnofaith said:
Hey everyone, I have desided to create a FYI post to anyone considering flashing back to stock 2.1(Eclair) using Odin if you are currently running Cognition(Froyo) roms. I have attempted flash back to stock on 4 phones(Samsung Captivate) with the same result(failing during the restoing of factoryrfs); causing the imfamous orange dump screen. This is a very serious issue which should be looked at by the devs. I am not trying to start a war or anything but the results from flashing back to 2.1 can almost always be reproduced(a bricked phone)
Click to expand...
Click to collapse
thats funny. i have run every froyo rom available to us, i9000 w/voodo, ulf, cognition with voodoo, and i have yet to brick my phone. i flash to stock between EVERY new rom.
there is something you are not doing right. did you disable voodoo before attempting to flash stock?
Atheistnofaith said:
Hey everyone, I have desided to create a FYI post to anyone considering flashing back to stock 2.1(Eclair) using Odin if you are currently running Cognition(Froyo) roms. I have attempted flash back to stock on 4 phones(Samsung Captivate) with the same result(failing during the restoing of factoryrfs); causing the imfamous orange dump screen. This is a very serious issue which should be looked at by the devs. I am not trying to start a war or anything but the results from flashing back to 2.1 can almost always be reproduced(a bricked phone)
Click to expand...
Click to collapse
I always flash back to JF6 via Odin 1 click before going to any new rom. It does not matter for whether voodoo is disabled or not because Odin 1 click repartitions everything to RFS. Also, the orange screen is not that big a deal. Reflashing JF6 via Odin once more is the solution.
If you continually have these problems when flashing to JF6:
1. Try re-downloading Odin 1 click.
2. Follow correct procedure for Odin flashing (Read OP's)
3. Try other USB ports
4. Uninstall and install fresh drivers that match your operating system (eg. 32bit/64bit)
Further, this post is not for the development section, but belongs in General or Q&A.
I think even without voodoo disabled, flashing back to stock will break voodoo and it wont be functional anymore. I personally never disable voodoo when flashing back to stock. You need to Master Clear after flashing back to stock.
Never bricked my phone flashing all the time.
I do it all the time! Never bricked my phone... EVER! The closest I came was when I tried flashing to another rom with CVM with voodoo still enabled. got stuck in loop, but to rectify the situation I "flashed back to stock with one click ODIN" and all was well.
i9000 is not the captivate argh different kernel
Odin gave me Blue, Light Blue, Orange, White and Black Screens of Death, no matters if i had Voodoo or not..
I think it sometimes hangs without any reason, but the drivers/program itself..
Thanks God my phone doesn't have the Bootloader's 3 Button issue..
Atheistnofaith said:
i9000 is not the captivate argh different kernel
Click to expand...
Click to collapse
I believe he was referring to i9000 roms. I have never had any issues flashing back to stock from any rom. It has to be something you are doing. Might be the answer you want but probably going to be the most common answer you will get. Check your steps.
Atheistnofaith said:
i9000 is not the captivate argh different kernel
Click to expand...
Click to collapse
i never said i am running an i9000 HARDWARE, i said ROMS
like everyone else has said. its something YOU are doing wrong. please dont spread FUD
This thread needs to be deleted. It's patently false.
Sent from my Captivate.
Sometimes its not the arrow....
its the Indian. The majority of the people who flash follow the same procedure with no issues. While its nice of you to try to caution folks, maybe you need to look at what you're doing instead of jumping to conclusions.
MikeyMike01 said:
This thread needs to be deleted. It's patently false.
Sent from my Captivate.
Click to expand...
Click to collapse
Agreed 10char
MikeyMike01 said:
This thread needs to be deleted. It's patently false.
Sent from my Captivate.
Click to expand...
Click to collapse
AGREED!
one person has problems with multiple devices=look for the common denominator.
if not deleted then at least OP change the title because its misleading.
i wouldn't be so fast to poopoo the post. I had similar issues with two of my previous captivates. Both times Odin froze on factory and bricked me to an unrecognizable state and both times I had some kind of lagfix I didn't disable. Right now I just write it off as coincidence as both times i didn't necessarily do things in the right order but there may be some legs to flashing some phones to stock with lagfixes. It's possible but the best thing to do is before flashing to stock remove and disable any lagfixes and you'll never have the problem
and is this a general thread or dev?
Atheistnofaith said:
Hey everyone, I have desided to create a FYI post to anyone considering flashing back to stock 2.1(Eclair) using Odin if you are currently running Cognition(Froyo) roms. I have attempted flash back to stock on 4 phones(Samsung Captivate) with the same result(failing during the restoing of factoryrfs); causing the imfamous orange dump screen. This is a very serious issue which should be looked at by the devs. I am not trying to start a war or anything but the results from flashing back to 2.1 can almost always be reproduced(a bricked phone)
Click to expand...
Click to collapse
I have flashed i9000 roms, kernels, modems, themes, and anyting else imaginable, with and without voodoo, with and without master clear, and have NEVER gotten the orange death screen before, during, or after Odin flashing back to stock. I've flashed just about every iteration of the Cognition FroYo roms and have never had an issue.
Re-download odin, maybe? But it's not an issue with Cognition.
Belaflek said:
i wouldn't be so fast to poopoo the post. I had similar issues with two of my previous captivates. Both times Odin froze on factory and bricked me to an unrecognizable state and both times I had some kind of lagfix I didn't disable. Right now I just write it off as coincidence as both times i didn't necessarily do things in the right order but there may be some legs to flashing some phones to stock with lagfixes. It's possible but the best thing to do is before flashing to stock remove and disable any lagfixes and you'll never have the problem
and is this a general thread or dev?
Click to expand...
Click to collapse
Yo only need to disable voodoo when you are upgrading from one version to another but when you are flashing back to stock it will repartition everything for you back to RFS.
I've run all the Froyo kernels, ROMs, even i9000 Froyo ROMs on the Froyo reoriented kernel, with or without voodoo, it doesn't matter, and I flash back to stock all the time. Odin wipes everything out, it doesn't matter what you are running.
the "factoryfs.rfs" screen-o-death is a well known problem. fortunately, factoryfs.rfs doesn't really matter (it's only the /system partition), your phone just won't boot. Likely you'll hit the phone--!--PC screen, but as long as you have 3 button recovery working, you're safe.
this issue crops up when you have a bad USB connection to your phone. I'm willing to bet 90% of the people with this problem are running outdated hardware (made before 2006 or so) that can't keep up with ODIN's pace or are using a desktop and not plugging the USB into a port connected to the motherboard (you should be using one on the back of the tower)
MikeyMike01 said:
This thread needs to be deleted. It's patently false.
Sent from my Captivate.
Click to expand...
Click to collapse
posts like this... littering the dev forum

flashing back & forth between gb & froyo

i just wanted this all in one place.i wanted my daily driver to be torch or fusion cause of call quality but also want to play around on gb roms.i found a safe way to go back and forth.if something happens to your phone i'm not responsible this is what works for me.
1.flash gb stock just like it says here:http://forum.xda-developers.com/showthread.php?t=1045734
2.i wanted mosaic on to play around with so i flashed mosaic.now from mosaic( I have only tried mosaic so far) you can flash back to 2.2 or 2.1 rom that has NO secondary bootloaders(this is very important).and you have to be on http://forum.xda-developers.com/showthread.php?t=1042543 the kernel from here in order for this to work cause it uses cwm 2.5 still.
3.make sure you wipe data/factory reset and also wipe cache partition and dalvik cache in between flashing roms.
4.if on talon kernel you cant flash from 2.3 to 2.2 cause it uses cwm 3.0.so you need to get kernel flasher from market and the this file http://etc.muteheadlight.net/android/I9000_reoriented_vG.1.1_novoo.tar and flash it from kernel flasher it will put you back on cwm 2.5 and you can go back to 2.2 from there.
this has worked for me several times today i wanted to make sure it worked go and thank all the devs on there respected paged.they work hard on all this development show some appreciation.
again dont mix boot loaders make sure the rom you are flashing does not flash boot loaders.just stay on gb boot loaders.as it is stated you will brick your phone mixing boot loaders.
I hope this helps some people out and explains it good enough.
I just use odin one click to flash back to stock then flash by froyo rom of choice.
To Gingerbread from 2.1 bootloaders:
odin flash bootloader and reorient kernel package HERE (7mb)
odin flash talon or other kernel with CWM3 built in
boot into CWM3
CWM3 flash GB wipe rom!
Back to Eclair/Froyo: (keeping GB booties)
Odin flash a Kernel with CWM2.5 built in (onix)
boot into CWM2
CWM2 flash 2.1 or 2.2 wipe rom.
------AVOID ROMS WITH SBL (secondary boot loader) LIKE A PLAGUE!!! or built-in 3 button fix!----- YOU WILL BRICK!!
****To not worry about mixing Bootloaders or the SBL on Eclair/Froyo roms flash odin-one-click to get stock booties before Odin flashing a Cwm2.5 kernel.
Easy Peasy Lemon Squeezy
i also use odin one-click to get back to stock
Fezz102 you have successfully flashed between GB and Froyo and only used odin to flash the initial boot loaders and rom after that you just swapped kernels with sgs kernel flasher and haven't had a single issue? And you haven't used odin again?
Sent from my SAMSUNG-SGH-I897
Why is everyone so afraid of odin? AS LONG AS IT DOESN'T HANG ON BOOT.BIN OR SBL.BIN YOU CANNOT BRICK. PERIOD.
Kernels don't have bootloaders AT ALL using odin to flash a kernel is recommended by all the kernel devs, they have stated the app is actually more likely to cause improper writes than odin.
studacris said:
Why is everyone so afraid of odin? AS LONG AS IT DOESN'T HANG ON BOOT.BIN OR SBL.BIN YOU CANNOT BRICK. PERIOD.
Kernels don't have bootloaders AT ALL using odin to flash a kernel is recommended by all the kernel devs, they have stated the app is actually more likely to cause improper writes than odin.
Click to expand...
Click to collapse
I'm on a mac I have a pc around but I swear if you saw it you'd be a little nervous to it's a cheap old lap top running xp it doesn't even have a battery, I'd be fine with odin if I had faith in my pc. That being said don't mention heimdall it doesn't recognize 2.1 bootloaders so in order to move up I still need odin.
Sent from my SAMSUNG-SGH-I897
heimdall doesnt recognize 2.1 bootloaders? really?
how was it created with 2.1 bootloaders before the 2.3 ones ever existed??
thats news to me.... learn somethin new every day...
*sarcasm*
This an interesting post from the guys that wrote heimdall the first is a list of confirmed devices that work with heimdall the eighth post is a list of confirmed working bootloaders and osx compatability i9000 this should give you an idea of what I'm talking about. Out of ten only two support osx. As far as the i897 is concerned if you ever flashed your phone with odin 1click and I have the boot loaders included do not support osx. THAT'D be a fact . *touchee*
Sent from my SAMSUNG-SGH-I897
Here's the linkhttp://forum.xda-developers.com/showthread.php?t=891518
Sent from my SAMSUNG-SGH-I897
1tontomato said:
Fezz102 you have successfully flashed between GB and Froyo and only used odin to flash the initial boot loaders and rom after that you just swapped kernels with sgs kernel flasher and haven't had a single issue? And you haven't used odin again?
Sent from my SAMSUNG-SGH-I897
Click to expand...
Click to collapse
no problems so far.just wipe everything and factory reset clear data in recovery the key there is to be in cwm2.5 and not 3.0. and to never flash anything with secondary bootloaders.
Hey if Im currently on a JVH ROM, and want to try out the Galaxy Sense i9000, but the whole deal about the bootloaders is a little irrating. And its even trickier for me to go back to stock considering I have a build 1010, thus One Click soft bricks my phone (*I have a jig*). But it really isnt a big deal because I use the JH2 method and iCezars method for flashing back without risk, without replacing the bootloaders. Those are the two methods I have had to flash back to stock while on a Gingerbread ROM.
But my question lies in whether I can flash back to stock using one of the two methods I stated above which DO NOT FLASH BOOTLOADERS and follow the instructions in the Sense i9000 thread (This isnt a how to, to flash, because from December--February all I did was flash MIUI and CM7), but rather do you know if I could flash with GB bootloaders or would it be too big of a mess?
And if I cant can someone point me into a direction of a .tar file that contains BOTH BOOTLOADERS such as Odin One Click but I have to use Odin 3 and manually put it in and flash.
Thanks!
Just use odin one click, yes it will soft brick you, no it's not s big deal you have a jig, after that soft brick use your jig, and icezar's packages liked you usually do. Bam stock with original bootloaders. That is your only option. Nothing else contains both bootloaders.
studacris said:
Just use odin one click, yes it will soft brick you, no it's not s big deal you have a jig, after that soft brick use your jig, and icezar's packages liked you usually do. Bam stock with original bootloaders. That is your only option. Nothing else contains both bootloaders.
Click to expand...
Click to collapse
Hmm.. I was seriously thinking that but I was worried that it would completely brick the phone because it does flash both bootloaders thus completely bricking the phone.
If I knew I could just Jig it back like ive had to do twice when I used Odin One Click Id use the JH2 package or Cezars and be good.
But since im playing with bootloaders Im worried that it will completely brick cause One Click doesnt even work on my phone.
it only completly bricks the phone if it DOESN'T flash both boot loaders!
what happens when you use one click? a soft brick right? if you get ANY activity out of you phone at all your bootloaders are intact. and your jig will work for download mode after that then you can fix the soft brick by using the .tar package you usually use.
nothing but odin one click will flash both stock bootloaders
studacris said:
it only completly bricks the phone if it DOESN'T flash both boot loaders!
what happens when you use one click? a soft brick right? if you get ANY activity out of you phone at all your bootloaders are intact. and your jig will work for download mode after that then you can fix the soft brick by using the .tar package you usually use.
nothing but odin one click will flash both stock bootloaders
Click to expand...
Click to collapse
yes I know that im not trying to argue you with you... hahah
Im just saying that I dont know Im just a little hesitant as I havent used Odin One Click in a while, plus the fact that it'll be twice the nerve racking coming from Gingerbread Bootloaders.
That is the one thing that is a little scary, but I know if anything flashes on to the screen im good to go, but just a little nervous, but am seriously considering just using the Odin One Click, and just praying that it at least flashes the AT&T screen then off like it normally does.
But I dont know if it'll work the same with GB, I know its mostly in my head but hahahaha
EDIT: I havent used One Click in a while should I wipe my phone before? And secondly I assume disabling lagfix?
FLASHED ONE CLICK.... Going now I will keep it posted when I get back to stock.
the bootloaders though flash went well so I think im in the clear. Lets hope : D
UPDATE: It soft bricked, Jig--> now on Stock.
THANKS SO MUCH!
No problem man.
TRUST THE ZOMBIE!!
Well, you started the topic, so...
I have gone back and forth one cycle now. GR-10, then Odin one-click to ancient stock, (no master clear), reboot recovery by reinstalling packages (update.zip still there), flash Serendipity 6 (rom cwm still on the phone), then restore from my Nandroid backup, and update calls, texts, and some apps. Takes maybe 30 minutes. On continuum now, since it's the only JVH rom.
I'm wondering if I can skip a step. They say the GB bootloaders are fine with Froyo. If so, I should be able to go download mode, flash Onix in Odin (no auto reboot - since the kernel and rom will be incompatible), then pull the battery, boot to recovery by holding volume-up/power, and simply load the old nandroid backup (since I would have the same kernel - Onix - and same modem - JQ1 - as I had when I created the backup). The backup contains the Dalvik cache, IIRC, so I wouldn't even have to clear that. That's about 5 minutes, plus the time it takes to restore newer messages, apps, etc - maybe 15 minutes total.
Does anyone know why this wouldn't work in theory?
Soccer_Dad said:
Well, you started the topic, so...
I have gone back and forth one cycle now. GR-10, then Odin one-click to ancient stock, (no master clear), reboot recovery by reinstalling packages (update.zip still there), flash Serendipity 6 (rom cwm still on the phone), then restore from my Nandroid backup, and update calls, texts, and some apps. Takes maybe 30 minutes. On continuum now, since it's the only JVH rom.
I'm wondering if I can skip a step. They say the GB bootloaders are fine with Froyo. If so, I should be able to go download mode, flash Onix in Odin (no auto reboot - since the kernel and rom will be incompatible), then pull the battery, boot to recovery by holding volume-up/power, and simply load the old nandroid backup (since I would have the same kernel - Onix - and same modem - JQ1 - as I had when I created the backup). The backup contains the Dalvik cache, IIRC, so I wouldn't even have to clear that. That's about 5 minutes, plus the time it takes to restore newer messages, apps, etc - maybe 15 minutes total.
Does anyone know why this wouldn't work in theory?
Click to expand...
Click to collapse
please read post 3
i wrote it. i know its there..

Lock Pattern Screen

Hi I have flashed my phone with a few roms and now that I have flashed any new rom and even whipped out and reformatted my sd card etc. I get the screen unlock pattern all the time.... even though all I have to do is swipe anywhere and not input a pattern unlock its really annoying!
Can anyone direct me on how I should go about this?
I currently flashed :
[Heimdall][One-Click][UVKJ6] The KJ6 Heimdall One-Click Collection [12/11/2011]
But I want to clean it out completely and start all over without the worry of this unlock pattern!
Lvnlegendinc said:
Hi I have flashed my phone with a few roms and now that I have flashed any new rom and even whipped out and reformatted my sd card etc. I get the screen unlock pattern all the time.... even though all I have to do is swipe anywhere and not input a pattern unlock its really annoying!
Can anyone direct me on how I should go about this?
I currently flashed :
[Heimdall][One-Click][UVKJ6] The KJ6 Heimdall One-Click Collection [12/11/2011]
But I want to clean it out completely and start all over without the worry of this unlock pattern!
Click to expand...
Click to collapse
Do a backup, perform a factory data reset, and you should be good to go. It's possible that clearing the cache & Davlik cache might work, but I'm not sure.
stephen_w said:
Do a backup, perform a factory data reset, and you should be good to go. It's possible that clearing the cache & Davlik cache might work, but I'm not sure.
Click to expand...
Click to collapse
Thanks Steven.... I actually backed up everything.... performed a data reset and even reset the sd card and it still happened, I dont think I have CWM with the One-Click I installed
Lvnlegendinc said:
Thanks Steven.... I actually backed up everything.... performed a data reset and even reset the sd card and it still happened, I dont think I have CWM with the One-Click I installed
Click to expand...
Click to collapse
Weird. I had an issue like that after installing the initial Octane release. I think I might've flashed chadster's KG4 via ODIN afterward to clean it out as it flashes 4 different files (PIT, PDA, CSC, Phone).
stephen_w said:
Weird. I had an issue like that after installing the initial Octane release. I think I might've flashed chadster's KG4 via ODIN afterward to clean it out as it flashes 4 different files (PIT, PDA, CSC, Phone).
Click to expand...
Click to collapse
this one:
[ROM-Leak][ODIN] Gingerbread 2.3.4 T959VUVKG4
I flashed that one too the first time also... so u think I should flash that then what is the best current 2.36 rom.... or what would u do?
Lvnlegendinc said:
this one:
[ROM-Leak][ODIN] Gingerbread 2.3.4 T959VUVKG4
I flashed that one too the first time also... so u think I should flash that then what is the best current 2.36 rom.... or what would u do?
Click to expand...
Click to collapse
Yeah, that's the one I personally always go back to that one to get a clean start. So far it's worked well for me.
As for what ROM, man, that's subjective I just read that Whitehawkx relased Valhalla Final. As for me I currently have Octane. I'd probably go to KG4, then stock KJ6, and maybe go to something custom from there. Others may have different ideas, though.
stephen_w said:
Yeah, that's the one I personally always go back to that one to get a clean start. So far it's worked well for me.
As for what ROM, man, that's subjective I just read that Whitehawkx relased Valhalla Final. As for me I currently have Octane. I'd probably go to KG4, then stock KJ6, and maybe go to something custom from there. Others may have different ideas, though.
Click to expand...
Click to collapse
Ya thats what ill do... I like KJ6 2.3.6, I just want my phone to be bloat free and fast with no issues lol
Lvnlegendinc said:
Ya thats what ill do... I like KJ6 2.3.6, I just want my phone to be bloat free and fast with no issues lol
Click to expand...
Click to collapse
I hear ya! Check the Dev section; I think FB just posted a debloater of some kind.
Try backing up your sd card and wiping it. Or use a different sdcard.
Everything on the phone gets reflashed. I have tested all three one clicks and have not experienced what you are saying.
Sent from my SGH-T959V using xda premium
To be fair, the one clicks, nor do any other method we tried (odin flashing, cwm falshing), reset EVERYTHING. The thread regarding incorrect time zones required a "hard reset" to get everything right again. Not sure if this should apply to this thread, but worth mentioning.
bhundven said:
Try backing up your sd card and wiping it. Or use a different sdcard.
Everything on the phone gets reflashed. I have tested all three one clicks and have not experienced what you are saying.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
In no way shape or form am I saying that its ur roms fault... im just trying to get an answer or hoping someone has had that happen to them... thats all.... im still going to reflash using the one-click u created it was easy and quick lol
iamperson347 said:
To be fair, the one clicks, nor do any other method we tried (odin flashing, cwm falshing), reset EVERYTHING. The thread regarding incorrect time zones required a "hard reset" to get everything right again. Not sure if this should apply to this thread, but worth mentioning.
Click to expand...
Click to collapse
Im not 100% on anything im doing but i have never done a Hard Reset... I have whipped and reformatted my sd card and started from fresh and still have the lock screen pop up.
Lvnlegendinc said:
Im not 100% on anything im doing but i have never done a Hard Reset... I have whipped and reformatted my sd card and started from fresh and still have the lock screen pop up.
Click to expand...
Click to collapse
It involves downloading "GPS Aids" from the market. In that tool is a place to do a hard reset. I can't remember the exact menu option, I think it's under "Tools" or something.
stephen_w said:
It involves downloading "GPS Aids" from the market. In that tool is a place to do a hard reset. I can't remember the exact menu option, I think it's under "Tools" or something.
Click to expand...
Click to collapse
I think ill roll back to KG4 then go from step to step there
Lvnlegendinc said:
In no way shape or form am I saying that its ur roms fault... im just trying to get an answer or hoping someone has had that happen to them... thats all.... im still going to reflash using the one-click u created it was easy and quick lol
Click to expand...
Click to collapse
Its not my ROM... they are all kj6 stock with different kernels. Read the op.
I was saying that there are files stored on your sdcard that Android uses. If you can isolate those files, it might help you figure out the problem you are having.
Sent from my SGH-T959V using xda premium
bhundven said:
Its not my ROM... they are all kj6 stock with different kernels. Read the op.
I was saying that there are files stored on your sdcard that Android uses. If you can isolate those files, it might help you figure out the problem you are having.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
I pretty much deleted everything on the sd card and started ur 1Click hoping the problem would go away.... no worries, im sure ill go back and figure out what may help.
Thanks!
Also, maybe I missed something.
Do you mean that you see the lockscreen when booting for the first time after oneclick? It looks like a crappy low res lockscreen? If so, just enter your old pin/password. It wont ask again... Until you setup protected lockscreen again.
If not, and what you are trying now doesnt work, then could you rephrase the problem?
Sent from my SGH-T959V using xda premium

Stuck in reboot loop

I just installed CWM via odin and all seemed well then I tried installing two different ICS based roms and both resulted in being stuck in a reboot loop. Could I have done something wrong? I have tried some fixes I saw posted around but nothing fixed the issue.
make sure u use darksidr before every flash. Also make sure u wipe dalvik cache. Did u install the uclca4 radio before u tried those roms?
icenight89 said:
make sure u use darksidr before every flash. Also make sure u wipe dalvik cache. Did u install the uclca4 radio before u tried those roms?
Click to expand...
Click to collapse
1. What's darksidr? I backed it up so I can go back... I just want ICS
2. I did dalvik twice
3. No, one ICS rom said you needed to install radio but the other didn't and on the first step of installing the rom it looked like the radio may have been packaged with the rom. Where can I find the radio download?
Got the radio and no luck =/
flash superlite 5.1, it does all the work for u
I flashed superlite 5.0, where is 5.1?
but 5.0 did it all for me too and didn't work =/
loom for darkside wipe and flash it. Superlite 5.1 just got posted, try it. If that doesn't work, odin back stock, reflash cwm, and flash superlite again.
Go to the top of rom page and read read read then Google Google Google. You guys are making the skyrocket forum look like crap. 1 INSTALL ODIN ICS FOR A START. INSTALL CWM. FIND A ROM. FOLLOW THEIR INSTRUCTIONS! You should have it. SHOULD
SkyRocket [ICS Rom]
WhatzinyourphonE said:
Who the hell let this noob post. We really should limit people to ten 5 threads a day. And 50 posts a month.
SkyRocket [ICS Rom]
Click to expand...
Click to collapse
WhatzinyourphonE said:
Go to the top of rom page and read read read then Google Google Google. You guys are making the skyrocket forum look like crap. 1 INSTALL ODIN ICS FOR A START. INSTALL CWM. FIND A ROM. FOLLOW THEIR INSTRUCTIONS! You should have it. SHOULD
SkyRocket [ICS Rom]
Click to expand...
Click to collapse
Jeez, go easy son. A careful reminder about the search feature is usually enough.
WhatzinyourphonE said:
Go to the top of rom page and read read read then Google Google Google. You guys are making the skyrocket forum look like crap. 1 INSTALL ODIN ICS FOR A START. INSTALL CWM. FIND A ROM. FOLLOW THEIR INSTRUCTIONS! You should have it. SHOULD
SkyRocket [ICS Rom]
Click to expand...
Click to collapse
I did everything you mentioned. I installed odin, installed CWM, found a rom, did everything the developer instructed me to do, the developer was aware of the problem and none of his fixes worked for me so I was advised to ask elsewhere. Yeah, I don't flash roms every week like I used to with my HD2 and this is my first time really messing with radios so I asked for help. That's what the forums are for. I'm sure I've invested more money in this community than you have and I think I completely deserve to make a few retarded posts once every 10 months. Thanks for all your help with your troll posts
iLiberate said:
I did everything you mentioned. I installed odin, installed CWM, found a rom, did everything the developer instructed me to do, the developer was aware of the problem and none of his fixes worked for me so I was advised to ask elsewhere. Yeah, I don't flash roms every week like I used to with my HD2 and this is my first time really messing with radios so I asked for help. That's what the forums are for. I'm sure I've invested more money in this community than you have and I think I completely deserve to make a few retarded posts once every 10 months. Thanks for all your help with your troll posts
Click to expand...
Click to collapse
After Odin, did u boot into the phone and let it cycle and then install Odin cwm? Give that a try. Also, most of the updated ROMs already have the proper radio, no need to flash. Let us know how it goes.
Run the: ics odin one click. Then odin cwm recovery. Then flash ics rom. Or just flash this rom and you'll be good to go
http://forum.xda-developers.com/showthread.php?t=1585290
In cwm its also very important to format /system before you flash the new rom. You didn't really mention if you did that or not, so I'm just saying, just in case
Sent from my SAMSUNG-SGH-I727 using xda premium
The rom in that link i posted formats the system and cache for you. So you do not neex to wipe anything
iLiberate said:
I did everything you mentioned. I installed odin, installed CWM, found a rom, did everything the developer instructed me to do, the developer was aware of the problem and none of his fixes worked for me so I was advised to ask elsewhere. Yeah, I don't flash roms every week like I used to with my HD2 and this is my first time really messing with radios so I asked for help. That's what the forums are for. I'm sure I've invested more money in this community than you have and I think I completely deserve to make a few retarded posts once every 10 months. Thanks for all your help with your troll posts
Click to expand...
Click to collapse
If you cant figure out how to make it happen go with Silvers rom, he's got the hookup with an easy as pie flash. Plus he makes some damn good stuff
http://forum.xda-developers.com/showthread.php?t=1585290
silver03wrx said:
The rom in that link i posted formats the system and cache for you. So you do not neex to wipe anything
Click to expand...
Click to collapse
I know lol. That comment was directed to iLiberate.
My apologies, forgot to quote
Sent from my SAMSUNG-SGH-I727 using xda premium
xcrazydx said:
If you cant figure out how to make it happen go with Silvers rom, he's got the hookup with an easy as pie flash. Plus he makes some damn good stuff
http://forum.xda-developers.com/showthread.php?t=1585290
Click to expand...
Click to collapse
Downloading now
Everyone else, I have done everything mentioned, trying this rom and if it doesn't work I'll just load my backup for now. Thanks for all your help
silver03wrx said:
The rom in that link i posted formats the system and cache for you. So you do not neex to wipe anything
Click to expand...
Click to collapse
No luck with yours either =/
iLiberate said:
No luck with yours either =/
Click to expand...
Click to collapse
I don't know what you've done to your phone. Perhaps if you make a very detailed list of what your setup is and what you've done so far we can help get you going. Be specific
Afternoon iLiberate,
What carrier are you with?
~PsyCl0ne
EDIT: Actually you know what come over to [RoM] ~[4.0.3.]~TEAM PERFECTION~REVAMPING
Now a couple of things before you start.
I am using http://forum.xda-developers.com/showthread.php?t=1472954 for my recovery. I have had issues with a newer version but this one has helped me through a ton of issues I have had.
(Flash this with ODIN first)
I also recommend getting a wiping script DARKSIDE Super wipe. http://forum.xda-developers.com/showthread.php?t=1487706
(Give props to the guy that put this script together. Keep the zip file some where easy to access, you will be moving it to your phones external SD card along with the rom zip and kernel files.)
When you go into the TeamPerfection thread it is gonna be kind of confusing looking at all the links. Basically you will see 3 Themes (AOSP ICE, KOBALT, Phone Candy) then a link to a rom that is already themed, and finally the stock rom which you will need if you want to flash any of the three themes I listed earlier. For now I would just go for the Sense release we can always change what it looks like later.
Also you will need a kernel.
If you're with AT&T I would suggest getting Mohan's kernel. If you're with a Canadian carrier I would suggest Romracer's kernel.
From here you can basically follow the guide in post number 3. It is really simple just need a little patience and it will go through. Also if you have any titanium backups from Gingerbread, please don't restore those apps when your phone comes back up. Just scribble down a list of apps you currently are running, make backups of SMS/MMS if you wish and then manually download them one by one from the market. Then you can make a Tibu of the apps so if you want to change what your phone looks like you can just restore all the apps in one go.
If you need any more help please feel free to PM me, I honestly don't mind or even post back here. Gonna be doing some work around the house but I'll check back periodically.
~PsyCl0ne

WARNING WARNING please read before rooting!!!

I know this isn't technically the right section for this but I put it here in hopes more people would see it. This is very important for anyone rooting using the dirtysanta method and perhaps other methods as well. It would be nice if this could get a sticky because people need to see this or this problem is going to keep occurring. I'm seeing it all over the threads.
DO NOT FACTORY RESET FROM INSIDE THE ROM. DO NOT USE LG's BUILT IN FACTORY RESET IN THE PHONE OR YOU WILL GET STUCK IN RECOVERY. Use the factory reset option inside of TWRP if you want to do a factory reset.
There have been many people (myself included even though I knew better and told myself not to do it before I did) who have got stuck in recovery because of this and it's not common sense to get out of it. I've been rooting and messing with this stuff for over 5 years and for 2 hours tried every trick I knew and nothing worked. What did finally end up working for me personally is this:
*restore your full stock backup (if you have one)
*after the backup is restored, in TWRP, go to mount, and mount the system. Check the box and press the mount USB storage button
*power off device
*use the button combo to boot into TWRP. It's volume down + power (hold them down), as soon as you see the LG logo let go of power for a brief moment and continue to press and hold both buttons until a white screen comes up. Choose yes for the next two options. This will bring you back into TWRP.
*now go back to mount and check system, and press the mount storage button, and reboot system.
lol this is only because it give you your stock boot.img. So if you factory reset, you have to flash SuperSU, no need to freak out.
If you format /system, you will need to flash a ROM, if the ROM does not flash SuperSU, you will h ave to flash it.
That's all folks!
That said, who wants a VZW Custom ROM and Kernel? Making the thread now. Identical to my H918 5.1 MOD ROM
Tilde88 said:
lol this is only because it give you your stock boot.img. So if you factory reset, you have to flash SuperSU, no need to freak out.
If you format /system, you will need to flash a ROM, if the ROM does not flash SuperSU, you will h ave to flash it.
That's all folks!
That said, who wants a VZW Custom ROM and Kernel? Making the thread now. Identical to my H918 5.1 MOD ROM
Click to expand...
Click to collapse
I tried flashing supersu.zip but that wouldn't work either. I challenge you to factory reset in the rom and then once stuck in recovery flash a new rom and the supersu zip and see if that works. I did this several times and it wouldn't work. I tried it with flashing a rom, and after restoring a backup. What appears to be happening is the system isn't mounting and it doesn't recognise that you have a ROM installed.
Not freaking out either, just trying to let people know not to factory reset inside the rom but use TWRP. There have been many people with this issue.
imucarmen said:
I tried flashing supersu.zip but that wouldn't work either. I challenge you to factory reset in the rom and then once stuck in recovery flash a new rom and the supersu zip and see if that works. I did this several times and it wouldn't work. I tried it with flashing a rom, and after restoring a backup. What appears to be happening is the system isn't mounting and it doesn't recognise that you have a ROM installed.
Not freaking out either, just trying to let people know not to factory reset inside the rom but use TWRP. There have been many people with this issue.
Click to expand...
Click to collapse
Oh, sorry. I overlooked something. That you had in huge bold caps the words IN THE ROM lol, my bad. I've never factory reset from within the ROM.
But my post stands when factory resetting from TWRP.
Tilde88 said:
Oh, sorry. I overlooked something. That you had in huge bold caps the words IN THE ROM lol, my bad. I've never factory reset from within the ROM.
But my post stands when factory resetting from TWRP.
Click to expand...
Click to collapse
Yea I knew better too, that's the bad part. In 5+ years I've never factory reset while in a rom when I have root and TWRP installed. Before I did it I even told myself it was probably a bad idea and I should just use TWRP. But my lazy conscience said "ahhh what the heck! just do it, it's too much trouble to boot into TWRP and besides, it might work ok" I hate my lazy consicence :'(
Exactly what I did and exactly what happened.
Gonna try this in the AM. One question...
If I'm able to flash back to "stock" using a deoxed stock rom, how can I then get rid of the boot warning so I can return this device to T-Mobile?
mrbigdrawsz said:
Exactly what I did and exactly what happened.
Gonna try this in the AM. One question...
If I'm able to flash back to "stock" using a deoxed stock rom, how can I then get rid of the boot warning so I can return this device to T-Mobile?
Click to expand...
Click to collapse
You'll need to return to full stock. I can't verify it works but this thread here claims to have a method for returning to stock.
imucarmen said:
You'll need to return to full stock. I can't verify it works but this thread here claims to have a method for returning to stock.
Click to expand...
Click to collapse
Well pray for me. Downloading now and will try first thing tomorrow.
mrbigdrawsz said:
Well pray for me. Downloading now and will try first thing tomorrow.
Click to expand...
Click to collapse
Did it work for you? Also since there is no t mobile rom there what did you use?
thegameksk said:
Did it work for you? Also since there is no t mobile rom there what did you use?
Click to expand...
Click to collapse
I used this guide https://goo.gl/ZHZPfO and it worked perfectly. Had a little stress when attempting to flash the stock recovery, but after installing two again, I was able to revert back to stock. Locked bootloader and it's as if I never did anything but boot up the stock OS.
Returning to T-Mobile today and just waiting on my Oneplus 3T to ship (granted I'm pissed off because the 128gb version is out of stock).
mrbigdrawsz said:
I used this guide https://goo.gl/ZHZPfO and it worked perfectly. Had a little stress when attempting to flash the stock recovery, but after installing two again, I was able to revert back to stock. Locked bootloader and it's as if I never did anything but boot up the stock OS.
Returning to T-Mobile today and just waiting on my Oneplus 3T to ship (granted I'm pissed off because the 128gb version is out of stock).
Click to expand...
Click to collapse
Glad you got it fixed.
Just for the record, this thread isn't for helping people get back to stock, its main focus is to warn people not to factory reset inside the rom. Then I just shared the method that worked for me to get out of being stuck in TWRP. Not saying you implied any different, I'm just clarifying for anyone that may read in the future. It's awesome return to stock methods are now popping up which are usually good for fixing all sorts of issues.
Enjoy your OnePlus 3T

Categories

Resources