Related
Sorry for dumb question.. as I am really novice for installing custom rom..
I read similar contents from [BIONIX BIUI] but there is no Q&A of [BIONIX BIUI] here so allow me to post here...
I was in Darky Rom and switched to FusionXII direct through CWM qithout any problem and now hope to flash BINIX BIUI...
Do I have to flash UCKL2's stock bootloader first through ODIN then should flash KJ2 based custom rom or can flash direct through CWM ???
Anything should I be careful when switching from one rom to another ??
Thanks, guys...
Pls consider I am learning step by step...
Yes you still have bootloadets
Sent from my SGH-I997 using xda premium
Loaders
Sent from my SGH-I997 using xda premium
You should avoid messing with bootloaders whenever possible.
The only reason EVER to flash a bootloader on Infuse is to transition from Froyo to Gingerbread - once you're on a Gingerbread bootloader, if you're staying with a Gingerbread ROM, keep the bootloader.
Entropy512 said:
You should avoid messing with bootloaders whenever possible.
The only reason EVER to flash a bootloader on Infuse is to transition from Froyo to Gingerbread - once you're on a Gingerbread bootloader, if you're staying with a Gingerbread ROM, keep the bootloader.
Click to expand...
Click to collapse
I had GB running. Last night I flashed Infused 1.6.0 (Froyo), and then came back to GB rom, with no issues. So I think once we are on GB, we can switch back and forth while being careful not to mess with CWM.
Or maybe I was lucky 'cos the the line in Infused 1.6.0 changelog:
"Removed recovery binary to prevent the phone from booting into green CWM"
stick with gingerbread bootloaders after you install them
I'd avoid Bionix for the time being. I've been doing this for a while and I it's taking some work to get back.. flash around with the others for a while and get some experience.. Doesn't mean you don't have good work nopco..
Ok, thanks guys...
Sorry again for novice question again..
I want to "Stick" to GB bootloarder... the problem is "HOW?"
I read through forum and found out there is no way to check whether I am in GB' bootloader or not...
Already flashed with UCKL2 Stock Rom once, so can I consider I have GB bootloader now ???
I flashed other rom such as MaxQ, FusionXII and re-flash to BIONIX without Rainbow problem so this is ok now ?
Thanks again for advice again, duds..
diablo009 said:
I had GB running. Last night I flashed Infused 1.6.0 (Froyo), and then came back to GB rom, with no issues. So I think once we are on GB, we can switch back and forth while being careful not to mess with CWM.
Or maybe I was lucky 'cos the the line in Infused 1.6.0 changelog:
"Removed recovery binary to prevent the phone from booting into green CWM"
Click to expand...
Click to collapse
During switch between one rom to another, my device also booted in "Green Recovery" then I ODIN with community kernel to get Red CWM recovery to re-flash other rom.
Did I do something wrong ??
Paxunion said:
During switch between one rom to another, my device also booted in "Green Recovery" then I ODIN with community kernel to get Red CWM recovery to re-flash other rom.
Did I do something wrong ??
Click to expand...
Click to collapse
Everyone has their way of installing roms. What's weird is I have no idea how everyone is getting different color recovery screens other than red. The only recovery I've ever had has always been red in Cwm. Simple if your on Froyo if you flash the community kernel v8 reboot into recovery, you'll be in red Cwm and can flash any rom you want without issues. You don't need to worry about changing the kernel cause most roms come with a kernel and will erase the community kernel v8. Why is this all so difficult?
Sent from my SAMSUNG-SGH-I997 using xda premium
Yes, I also though as you explained...
I have flashed GB based rom as I believe... never flashed to Froyo Rom.
So there should be no worries about bootloader or kernel.
But when I flashed BOINIX which is based on stock Kernel, things messed up with shown Rainbow affect and this was caused because I was in Froyo Kernel as I read.
Ok, so now I want to make really sure I am in GB bootloader.
Question is,
If flashed successfully to GB based Rom, bootloader is not to be concerned ??
Is there anyway to flash ONLY GB BOOTLOADER with ODIN to make sure I am on GB bootloader ?
Sorry again for dumb question again...
I am really, really newbie not only for Infuse but for ANDROID totally so need help and advice.
Thanks, Axiomkid and all...
Paxunion said:
Yes, I also though as you explained...
I have flashed GB based rom as I believe... never flashed to Froyo Rom.
So there should be no worries about bootloader or kernel.
But when I flashed BOINIX which is based on stock Kernel, things messed up with shown Rainbow affect and this was caused because I was in Froyo Kernel as I read.
Ok, so now I want to make really sure I am in GB bootloader.
Question is,
If flashed successfully to GB based Rom, bootloader is not to be concerned ??
Is there anyway to flash ONLY GB BOOTLOADER with ODIN to make sure I am on GB bootloader ?
Sorry again for dumb question again...
I am really, really newbie not only for Infuse but for ANDROID totally so need help and advice.
Thanks, Axiomkid and all...
Click to expand...
Click to collapse
The bootloader are found within the kernel itself. So if you flashed a gb rom using a gb based kernel you are on gb bootloader and not froyo. Froyo stock based kernels may cause rainbow screens cause it won't work with gb roms this is why you are getting them.
Sent from my SAMSUNG-SGH-I997 using xda premium
Axiomkid said:
The bootloader are found within the kernel itself. So if you flashed a gb rom using a gb based kernel you are on gb bootloader and not froyo. Froyo stock based kernels may cause rainbow screens cause it won't work with gb roms this is why you are getting them.
Edit: community kernel v8 works for both froyo and gb. I flash it using sgs kernel flasher from the market and then I'm able to flash gb roms without getting bootloops and other issues. You can't flash a gb kernel over Froyo cause it will cause bootloops and it won't load and you'll have to gtg to stock again.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I997 using xda premium
@Axiomkid,
Thanks for kind advice, now I know clearly,
1) Bootloader is in the kernel so unnecessary to flash separately.
2) Community kernel V8 works both for Gb and Froyo so it will be ok to flash Community kernel v8 to get Red CWM to re-flash other GB Rom from existing GB Rom.
Another question is,
If I want to flash Froyo Rom from existing GB Rom, what is the right way to do and if flash to Froyo Rom, I am on Froyo Bootloader, right ??
Thanks again & Merry Christmas !
If you wanna go back to Froyo use Odin and flash GTG ultimate unbrick to reformat the phone back to original Froyo.
Sent from my SAMSUNG-SGH-I997 using xda premium
It is very important if you install a rom and you don't like the kernel, sometimes it can be flashed with a different kernel but chances are it will screw your phone up. I tried using a different kernel on someone's rom and I had a tint of yellow on my screen. The Devs give us a kernel that works specifically for their rom and should not be replaced with another kernel unless told otherwise. People get errors cause of this and fill up a lot of forum space asking why their phone is screwed up. You just need to read before installing a rom. Each rom includes each own set of directions.
Most kernels allow overclocking and under volting your phone, and to be honest I don't mess with the settings so I don't end up with a burnt CPU
Sent from my SAMSUNG-SGH-I997 using xda premium
Axiomkid said:
The bootloader are found within the kernel itself. So if you flashed a gb rom using a gb based kernel you are on gb bootloader and not froyo. Froyo stock based kernels may cause rainbow screens cause it won't work with gb roms this is why you are getting them.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
WRONG. DEAD WRONG.
The bootloader is a COMPLETELY different entity than the kernel.
Custom Gingerbread kernels (such as Infusion-GB and Daily Driver) have a workaround that allows operation with Froyo bootloaders.
However, working video acceleration in the latest leaks can only be obtained with a stock kernel from one of those leaks. If you flash a kernel and system image from a leak (such as UCKL2) and you get rainbows, you need to flash new bootloaders. If you don't get rainbows - you don't need new bootloaders and should avoid flashing them if at all possible.
(Basically, don't flash anything with boot.bin or sbl.bin using Heimdall or Odin once you're on GB bootloaders.)
Entropy512 said:
WRONG. DEAD WRONG.
The bootloader is a COMPLETELY different entity than the kernel.
Custom Gingerbread kernels (such as Infusion-GB and Daily Driver) have a workaround that allows operation with Froyo bootloaders.
However, working video acceleration in the latest leaks can only be obtained with a stock kernel from one of those leaks. If you flash a kernel and system image from a leak (such as UCKL2) and you get rainbows, you need to flash new bootloaders. If you don't get rainbows - you don't need new bootloaders and should avoid flashing them if at all possible.
(Basically, don't flash anything with boot.bin or sbl.bin using Heimdall or Odin once you're on GB bootloaders.)
Click to expand...
Click to collapse
Boy, I wish I read this yesterday.
I had struggled with this yesterday trying to install Bionix using heimdall.
Managd to boot loop in 3e blue recovery several times until I flashed bootloaders in heimdall to get back to a working stock.
Paxunion, if I may suggest, if you are on froyo,
I think it'll be easier for you to use Adam outler's heimdall uckj4 return to stock.
Put your phone in the download mode. Flash it once then flash it again with the bootloader checked.
Go to his second post and flash the kernel to get recovery and then you will have gb bootloader and be able to flash the ROM of your choice.
If you did want Bionix, very nice, use the heimdall package that Dani included in the bionix thread. You won't have to flash the kernel step if you use Dani's heimdall package.
Do not check the repartition or partition box with the bionix flash.
qkster said:
Boy, I wish I read this yesterday.
I had struggled with this yesterday trying to install Bionix using heimdall.
Managd to boot loop in 3e blue recovery several times until I flashed bootloaders in heimdall to get back to a working stock.
Paxunion, if I may suggest, if you are on froyo,
I think it'll be easier for you to use Adam outler's heimdall uckj4 return to stock.
Put your phone in the download mode. Flash it once then flash it again with the bootloader checked.
Go to his second post and flash the kernel to get recovery and then you will have gb bootloader and be able to flash the ROM of your choice.
If you did want Bionix, very nice, use the heimdall package that Dani included in the bionix thread. You won't have to flash the kernel step if you use Dani's heimdall package.
Do not check the repartition or partition box with the bionix flash.
Click to expand...
Click to collapse
I was wondering if anyone actually used that...
good to know it worked out. I've wanted to do a rom with stock kernel for a while but nop can do it better. just glad I could help in a way.
Dani897 said:
I was wondering if anyone actually used that...
good to know it worked out. I've wanted to do a rom with stock kernel for a while but nop can do it better. just glad I could help in a way.
Click to expand...
Click to collapse
I ran into some problem due to checking of the repartition box and screwed up everything. Had to reflashed bootloader to get the phone working again.
I found it was easiest to flash adam's uckj4. Then heimdall fronend your package.
Two steps. Simple. If i have some time, i might do a faq step guide thread in the q a
I'm gonna make this short and simple.
I've got a stock Infuse 4G on 2.3.6 and I have no idea how to root it.
To my knowledge, SOC does not work.
How do I go about rooting my phone?
This might have already been answered, but I can't find a thread concerning it. A link would be appreciated, if possible.
with a kernel switcheroo. you need a non secure kernel to root it, fortunately the Rogers 2.3.3 kernels do boot 2.3.6. flash an older custom kernel like the hellraiser kernel through heimdall, I suggest heimdall just because its easier to extract a kernel zimage from an update than to do that but then create a .tar.md5 archive of it. you can use the ever popular entropy DD kernel but if you go back to the 2.3.6 kernel then you will have to change the vold.fstab back to stock.
the kernel flash may root the phone depending on the kernel but its an older su binary and if you update it the kernel will overwrite it on next boot.
if you want to use a custom kernel permanently then use entropy DD because it has had the root script removed allowing updates to su. though it doesn't root it will allow root through adb so soc may work after you flash that kernel. then you can update the binary through superuser
if you are gonna use the stock 2.3.6 kernel then use an old build of entropy or an old hellraiser kernel. then boot up and flash the 2.3.6 kernel back to the phone through heimdall or sgs kernel flasher. (sgs Kernel flash has the ability to find the zimage inside of a .zip or. tar even in subfolders so you can actually put the leak .tar on the SD card and flash the kernel that way if you can't figure out heimdall)
Thanks for the quick response. I'll try it tomorrow since it looks like it may take a while...
andrewpottz said:
I'm gonna make this short and simple.
I've got a stock Infuse 4G on 2.3.6 and I have no idea how to root it.
To my knowledge, SOC does not work.
How do I go about rooting my phone?
Click to expand...
Click to collapse
andrew,
did you bought the phone with stock 2.3.6 installed? what version is it? uckl2?
did you flash it with one of the unofficial GB leaks?
thanks.
ohh almost forgot about voodoo. the custom kernels convert the files system and wont allow you to flash the stock kernel, you'll get bootloops. if you don't intend to keep the custom kernel disable lagfix before you start by creating a folder with the path /sdcard/Voodoo/disable-lagfix
the V in Voodoo is capital. all other letters are lower case.
read the Rogers root thread for more details. its the same process laid out for rogers since that thread was written before soc worked on anything above 2.3.2. actually that kernel will also work on 2.3.6 for att.
Dani897 said:
ohh almost forgot about voodoo. the custom kernels convert the files system and wont allow you to flash the stock kernel, you'll get bootloops. if you don't intend to keep the custom kernel disable lagfix before you start by creating a folder with the path /sdcard/Voodoo/disable-lagfix
the V in Voodoo is capital. all other letters are lower case.
read the Rogers root thread for more details. its the same process laid out for rogers since that thread was written before soc worked on anything above 2.3.2. actually that kernel will also work on 2.3.6 for att.
Click to expand...
Click to collapse
I haven't tried this yet, Dani. Would it be possible for him to use heimdall one click defuse kernel that adam made to obtain red recovery then flash the super user fix to install SU?
andrewpottz said:
I've got a stock Infuse 4G on 2.3.6 and I have no idea how to root it.
Click to expand...
Click to collapse
No you don't... If you're on stock you're on 2.2.x (AT&T) or 2.3.3 (Rogers).
AT&T hasn't released Gingerbread for the Infuse yet.
qkster said:
I haven't tried this yet, Dani. Would it be possible for him to use heimdall one click defuse kernel that adam made to obtain red recovery then flash the super user fix to install SU?
Click to expand...
Click to collapse
yes but if he is already on gingerbread he needs a backup gingerbread kernel, if he uses cwm for the gb kernel it must already be on the SD card.
so it would be
1. download cwm flashable gb kernel to the SD card
2. download heimdall defuse kernel oneclick to PC and install drivers, I haven't done this on windows in a while but the Samsung drivers should work but heimdall also has there own system to recognize the device. forgot what its called....
3 run heimdall from run in windows or terminal in other os and put phone in download mode and connect the data cable
4. flash defuse kernel
5. boot into recovery with 3button. phone wont boot gb on froyo kernel but recovery works.
6. flash root
7.flash gb kernel
8. reboot
9. win
I used to use the mismatched kernels on the captivate. if nothing else was working I'd go back to stock 2.1, flash a froyo kernel with cwm and then flash a froyo or gb rom. 3 easy steps.
Rooting 2.3.6
Simply use the Heimdall Defuse Kernel to flash red cwm then flash the rooted version of the ROM Or a custom rom. it pre-roots your phone for you just click flash
Entropy512 said:
No you don't... If you're on stock you're on 2.2.x (AT&T) or 2.3.3 (Rogers).
AT&T hasn't released Gingerbread for the Infuse yet.
Click to expand...
Click to collapse
that's what I was wondering, Entropy.
I was thinking he meant to say he had installed one of the leaks or bought the phone with one of the later leaks like uckl2, where SOC doesn't work
qkster said:
that's what I was wondering, Entropy.
I was thinking he meant to say he had installed one of the leaks or bought the phone with one of the later leaks like uckl2, where SOC doesn't work
Click to expand...
Click to collapse
Which isn't stock...
qkster said:
that's what I was wondering, Entropy.
I was thinking he meant to say he had installed one of the leaks or bought the phone with one of the later leaks like uckl2, where SOC doesn't work
Click to expand...
Click to collapse
Yeah he clearly stated he was on 2.3.6 STOCK infuse 4g and wanted to know how to ROOT IT. Seems like its not stock to me
Sent from my SAMSUNG-SGH-I727 using xda premium
Like they say until we see pictures its not true
Sent from my SGH-I997 using XDA App
shenanigans!!
Hello!
I just got a pretty good deal on a stock Froyo Infuse 4G, so I bought it.
A little help please! I would love to have the stock ATT rom with the ability to overclock the processor. This is was I have done so far.. plrease don't be so hard on me since this is my first non-HTC device lol.
So the first thing I did was install a "leaked" Gingerbread ATT stock rom using a program called Odin. Then, I root it using that Superoneclick software... I actually clicked a million times instead trying to get it working because I had GingerBread instead of Froyo ... but somehow managed to do it, it is properly rooted and well tested. So! now with my rooted device, I downloaded Rom Manager from the market, flashed it succesfully (at least that's what the screen said)... and when trying to boot into CWM Recovery I got the following errors:
verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
installation aborted.
I tried to flash it via RomManager several times, also did it via SD-Card renaming it to Update.zip and flashing it with the stock recovery.. same error. I searched for more information, someone in the forum said the reason could be an incompatible Kernel, so I flashed the Community V8 Kernel... and my device didn't boot past the Samsung screen... but somehow if I tried manaully to get into CWM recovery, it worked! (just the recovery). Flashed a custom rom that I didn't like... then suddenly I lost the CWM Recovery and cannot then bricked it and was unable to flash it again..
I managed to restore the phone to ATT factory condition using a guide here on Xda (this time the phone kept the leaked GB rom)... then rooted it again and haven't done anything else. Mu question is:
How can I keep this stock rom with the ability to overclock the processor? (flashing different kernels just makes it freeze on boot at Samsung logo).
Thanks for your help!::
here a good start by me:
http://forum.xda-developers.com/showthread.php?t=1437548
Thanks, it is a useful link but I still don't find the answer to my question (or maybe I just don't undertand it).
I am beyond frustration... could anyone please tell me what to do to step by step to flash an overclockable Kernel keeping my GingerBread stock ATT rom? like if you were explaining it to a retarded person?
many thanks...
domenicostorino said:
Thanks, it is a useful link but I still don't find the answer to my question (or maybe I just don't undertand it).
I am beyond frustration... could anyone please tell me what to do to step by step to flash an overclockable Kernel keeping my GingerBread stock ATT rom? like if you were explaining it to a retarded person?
many thanks...
Click to expand...
Click to collapse
1. You need to restore you phone back to stock using gtg's unbrick or heimdall 1 click. (See my post)
2. ATT's GB latest is not rootable thru SOC. You can use odin to flash an insecure kernel (http://forum.xda-developers.com/showthread.php?t=1212485) but you will also need to update superuser binaries and busybox as well. Running the insecure kernel for OC, you will lose the video recorder and video player.
It doesn't sound like you can understand enough yet to do this.
3. If you want a stock att and rooted, go to the dev section:
check out zeus stock 5.2, vagabond or victory. These are GB stock base roms with root already done. There is also dman's deodexed, rooted gb uclb3 already with oc kernel...no video
qkster said:
1. You need to restore you phone back to stock using gtg's unbrick or heimdall 1 click. (See my post)
2. ATT's GB latest is not rootable thru SOC. You can use odin to flash an insecure kernel (http://forum.xda-developers.com/showthread.php?t=1212485) but you will also need to update superuser binaries and busybox as well. Running the insecure kernel for OC, you will lose the video recorder and video player.
It doesn't sound like you can understand enough yet to do this.
3. If you want a stock att and rooted, go to the dev section:
check out zeus stock 5.2, vagabond or victory. These are GB stock base roms with root already done. There is also dman's deodexed, rooted gb uclb3 already with oc kernel...no video
Click to expand...
Click to collapse
Thanks for the info!
The first step has been done, restored the phone using Heimdall one click after bricking it, the phone was restored with a UCKJ4 2.36 GingerBread stock ATT rom (Kernel 2.6.35.7-I997uckj4-cl694350) and I am also rooted using SuperOneClick.
I don't fully understand step two, will try it once I get some more knowledge.
Question about the third step... does HDMI work in any of those custom stock roms? I use HDMI a lot.
domenicostorino said:
Thanks for the info!
The first step has been done, restored the phone using Heimdall one click after bricking it, the phone was restored with a UCKJ4 2.36 GingerBread stock ATT rom (Kernel 2.6.35.7-I997uckj4-cl694350) and I am also rooted using SuperOneClick.
I don't fully understand step two, will try it once I get some more knowledge.
Question about the third step... does HDMI work in any of those custom stock roms? I use HDMI a lot.
Click to expand...
Click to collapse
My Vagabond ROM runs the stock kernel if you follow directions.
HDMI will work. Battery is excellent. Feel free to check it out
qkster said:
My Vagabond ROM runs the stock kernel if you follow directions.
HDMI will work. Battery is excellent. Feel free to check it out
Click to expand...
Click to collapse
Thanks, but is it overclockable?
domenicostorino said:
Thanks, but is it overclockable?
Click to expand...
Click to collapse
you cant have your cake and eat it too.
stock kernel = HDMI. no oc
oc = no HDMI, and currently, no video on some rom
THIS IS NOT A CUSTOM ROM. THIS IS STOCK OFFICIAL ROGERS ICS UXLF3 FIRMWARE. PLEASE DO NOT ASK FOR MODS, I HAVE PROVIDED THIS UPON REQUEST.
INTRODUCTION
Click to expand...
Click to collapse
This is the Stock Official ROGERS/Samsung Released Firmware for the SGH-I727R (Skyrocket) based on Android Platform 4.0.4 aka ICS. It is targeted for:
* Anyone who wants to be on the stock release, doesn't want to use ODIN.
* Wants to build a custom rom, and needs an official base. (see post #2)...
* Or, you just want a baseline.
PACKAGING
Click to expand...
Click to collapse
Well it is Stock, untouched, except for the deodexing and zipaligned. Your kernel and radios will be updated as in the official update. The only thing I have left out is the recovery, and I can provide a flashable one later, if you really really want to be stock for any future OTA update. See the optional flash if you need busybox and su.
- DeOdexed as per my stringent process, no using Kitchen or any other nonsense. Every apk get's what it needs in the classpath.
- zipaligned.
- all ownsership and permissions exactly as in stock install.
- Untouched UXLF5 boot image (i.e kernel + ramdisk).
- Your radio/modem will be updated to UXLF3.
- [OPTIONAL] If you want to flash busybox/su see the ADD-ONS. This will effectively root your install.
- [OPTIONAL] If you want the modified boot.img that enables init.d scripts, bootanimation, insecure boot, then flash the boot.img listed in the add-ons
INSTALLATION
Click to expand...
Click to collapse
Pretty straight forward. The only requirement is you need CWM 5 and above (I have tested with the touch recovery). NOTE: THIS WILL WIPE DATA.
1) Backup, Nandroid preferred.
2) Download and Copy the ROM to your device. (Please make sure you check the MD5SUM, the dowload link has the correct one).
3) Copy any additional add-ons you want to your devices, internal or external sdcard.
4a) Boot into CWM recovery (remember that is the requirement).
4b) In your recovery format /system (in touch recovery it is under: "mounts and storage)
4c) wipe data and cache partition
5) Flash the ROM.
6) [OPTIONAL] If you want busybox and su (binaries only). This will ROOT your phone. Flash it now.
7) [OPTIONAL] If you WANT the modified boot.img (modified ramdisk + stock kernel) flash that.
8) [OPTIONAL] If you want to flash a *different* radio, flash it now.
9) reboot
DOWNLOADS
Click to expand...
Click to collapse
* [15-JUL-2012] CWM 5 Flashable Offifical ROGERS UXLF3 FULL STOCK ROM. PLEASE CHECK THE MD5SUM. THE LINK HAS IT. ROGERS-ICS-UXLF3-cwm5.zip
RECOVERY
Click to expand...
Click to collapse
WARNING I HAVE NOT TESTED THIS. OBVIOUSLY YOU NEED TO BE ON A CWM recovery
* [07-AUG-2012] CWM flashable Stock Recovery, obviously you will lose CWM after this. Download
ADD-ONS
Click to expand...
Click to collapse
* [10-JUL-2012] Busybox and SU binaries ONLY (you can download SuperSu or Superuser from the Play Store). busybox-su-pack-cwm5.zip
* [10-JUL-2012] UXLF3 modified boot image). This is basically the Stock UXLF3 Kernel with modified ramdisk image to support adb root/insecure/bootanimation. kernel-skyrocket-UXLF3-cwm5.zip
* [10-JUL-2012] RADIOS: Instead of listing everything here: my custom rom threads OP in the Radio Section has all the RADIOS, without RIL, so it is safe to flash. Thread Link.
ISSUES
Click to expand...
Click to collapse
Unless there is a flash issue, folks this is as Stock as it gets. This is NOT a CUSTOM ROM, see my other thread on ATT STOCK, I will post some modding guide there.
reserved
reserved
thx. this will come in handy.
+rep
thanks mohan,i can now post this in my post
remember i was talking to u about rooting a short while ago so i could post a tutorial, its done and they made it a sticky.
one question, is there a way to unroot without flashing stock
edit: im guessing that there is no stock recovery in this rom, making it a stockish firmware
edit: i answered my own question about unrooting, just delete su from /bin and /xbin directories
downloading
vincom said:
thanks mohan,i can now post this in my post
remember i was talking to u about rooting a short while ago so i could post a tutorial, its done and they made it a sticky.
one question, is there a way to unroot without flashing stock
edit: im guessing that there is no stock recovery in this rom, making it a stockish firmware
edit: i answered my own question about unrooting, just delete su from /bin and /xbin directories
Click to expand...
Click to collapse
Yup just deleting the binaries is enough to "unroot". I may update the op with the revert script (busybox and su) and the respective stock recovery, when i get chance..
mohan_kr said:
Yup just deleting the binaries is enough to "unroot". I may update the op with the revert script (busybox and su) and the respective stock recovery, when i get chance..
Click to expand...
Click to collapse
oh great, i just finished detailing a newb guide to explain a temporary unroot and permanent unroot methods, a script would of been easier to use, btw that su/bb file works like a charm on any firmware
kinda missed the touchwiz smoothness... too bad there isnt a 14 toggle compatible with this. hopefully one day soon.
NIKEstickER said:
kinda missed the touchwiz smoothness... too bad there isnt a 14 toggle compatible with this. hopefully one day soon.
Click to expand...
Click to collapse
Flashing the UCLF6 toggle zip worked for me.
Very nice work, Maybe I should give it a try lol.
i have installed this on my SGH-i727 ATT handset.
By far this rom gives the best battery and performance...
Thanks op...
But this rom is having shutdown/reboot freeze issue.
Embryo 4.1 is discharging battery than any other roms, otherwise it is also ok.
Can I use Twrp to flash this? Sorry for the noob question
Sent from my SAMSUNG-SGH-I727 using xda premium
i see in your op about providing a flashable stock recovery, can you, this guy fracked up his usb port and cant use odin to return to stock for warranty repairs
vincom said:
i see in your op about providing a flashable stock recovery, can you, this guy fracked up his usb port and cant use odin to return to stock for warranty repairs
Click to expand...
Click to collapse
In the OP...
I would just like to ask if I would lose my root if I flashed this?
Crinkypops said:
I would just like to ask if I would lose my root if I flashed this?
Click to expand...
Click to collapse
YES
One last thing: Will the 15-toggle mod work for this ROM? Because I have heard of success from others and I just wanted to confirm with you, the dev.
Sent from my SGH-I727R using xda premium
Hi mohan,
Is there any way you could do the same for Rogers GB? It would be a great help for me. As ICS is crap I get RR and freezes. It doesn't get the right time zones and etc.
Incredible rom! Just had my skyrocket for 2 weeks, flashed 5-6 jb roms, vincoms the best imo, seanscreamz close behind.
I thought I'd come back to stock for a couple reasons. One, to get a baseline and see how good stock Rogers ics is battery wise, two, I can't seem to get nfc figured out and want to see if stock will do it. A co-worker has a stock ics sgs3, we can transfer apps, web addresses etc., but where he transferred a feature film to a different co-worker with a stock Rogers ics sgs3, via nfc in about 30 seconds, it fails with my skyrocket. I notice that their phones have sbeam in addition to nfc and android beam, maybe that's the difference. But I was wondering if there's issues transferring between ics and jb?
Thanks!
Sent from my SGH-I727R using xda app-developers app
Sorry to double post but I thought this would be as good a place as any to post this. Went in to Rogers today to get my lte SIM card, to my surprise they didn't even charge me! I can't believe these speeds the screen shot shows the speed is double my Wi-Fi speeds at home! And look at the comparison to the 3g or H+ too, that's just sad. I'm expecting to pay for it battery wise but I can live with that for these speeds!
Sent from my SGH-I727R using xda app-developers app
My SGS4G is running on GB 2.3.6. I just re-formatted it because I had it stuck on a bootloop last time I tried to flash this kernel. http://forum.xda-developers.com/showthread.php?t=1080871
I don't want to do it wrong again so could someone tell me simply how to flash the kernel? I followed the installation instructions last time
1. Upload kernel to your sdcard
2. Reboot to CWM
3. Flash the kernel using CWM
Click to expand...
Click to collapse
but it got me stuck on a bootloop. Also, it doesn't mention which file to flash because there's Bali v3.3 and Bali v3.3UV. What's the difference?
Also, what do they mean by
NOTE FOR KD1 based ROM users:
There is a possibility your /system partition doesn't get converted to ext4 due to dirty /system partition from the original KD1 stock ROM. If this happen, please follow the instruction below
Click to expand...
Click to collapse
I don't know what's the KD1 part.
Please help and be very specific because I only know a bit about Odin~ (I'm also asking here because I can't post on the development forums so I can't ask the developer)
Use Eollie's 1 click here http://forum.xda-developers.com/showthread.php?t=1822626 That is an old kernel you're trying to flash and 1 clicks are better and easier to use.
drhonk said:
NOTE: this kernel will work with any 2.2.x based ROM. Also if your screen flickers ... please let me know and I'll release the capped version.
Click to expand...
Click to collapse
It pays to read. Lets hope the one click I have in my sig will fix you up.
Bali kernel is for Froyo (2.2) & you say you are on GB (2.3.6). So flashing it will cause a bootloop due to unexpected bootloaders. I suggest you either flash AntonX's basic with a twist or Bhundven's Blast kernel. Both of them are made for GB and have advanced CWM version where backup & restore work.
sent from me