Related
Ok, so I'm currently using bionix 1.9 with stock kernel. I really want to flash bionix fusion with kingxklicks kernel, from what here this is a great rom.
My question, is there anything I should know about flashing this i.e. going back to stock rom? Is there anything I need to do before flashing this?
If I decide to go back to stock rom can I just flash with odin? Do I have to flash stock kernel before flashing back to a stock rom?
Can anyone just let me know, I would like to be prepared in case anything does go wrong.
Nope, you should be safe to flash directly over your current rom. As a precaution, if you have Ryanza's OCLF, you might consider undoing the lag fix... not saying it is needed but more often than not, most people who have a problem start off with saying " Help, I just tried flashing (xyz rom) and now I am stuck at the bootscreen. I had (abc rom) and OCLF before... what could be wrong?" Any other questions be sure to consult the red text in my sig.
Ok cool, even then I have been stuck on the boot screen a couple of time. Odin fixed that problem.
Sent from my SGH-T959 using XDA App
Other than making a nandroid backup and maybe a titanium backup, you should be good to go ...
Fusion 1.1 is a wipe ROM so may want to backup your apps ....
i want to know if i can keep the stock rom for my epic(Build:sph-d700 eclair.di18, kernel:2.6.29) and add a custom kernel? and which kernel is the best for battery life and speed? tired 2 times and bricked my phone both times. phone is rooted and used the one click root.
juice.ki11z said:
i want to know if i can keep the stock rom for my epic(Build:sph-d700 eclair.di18, kernel:2.6.29) and add a custom kernel? and which kernel is the best for battery life and speed? tired 2 times and bricked my phone both times. phone is rooted and used the one click root.
Click to expand...
Click to collapse
There's a sticky at the top of the forum that lists the custom ROMs and kernels available for the Epic.
I suggest you pick one and try it. If you like it keep it, if not, flash another.
You need to be rooted and you need custom recovery.
Via clockworkmod recovery, you can flash just a kernel to your stock ROM.
hope this helps
has anyone made a video on how to do it the right now on a EPIC? i tried it like 5 times with baby step step2 and it didnt work on DI18
juice.ki11z said:
has anyone made a video on how to do it the right now on a EPIC? i tried it like 5 times with baby step step2 and it didnt work on DI18
Click to expand...
Click to collapse
you need to be rooted. you also need clockwork mod recovery.
then you can flash a different kernel
yeah i have all that and ive watched videos on how to do it on other phones but not on the epic it seems easy but when i do it my phone mess's up! i put the zip in the root of the SD card power the phone off and put into clockworkmod instill the zip and it bricked my phone every time. not sure if im doing it right. thats why im asking if theres a video on how to do.
Do One-click-root, clockwork recovery (both should be done from the computer via USB debug mode) then, power off your epic. Next, Hold Volume Down, Camera Button and Power Button until the clockwork recovery screen pops up(should be green text, not blue which is the stock recovery). If you have the custom kernel already in your SD card, go to Install Zip From Card > Choose Zip from SD Card > (Custom Kernel)
And there you have it.
To flash any rom, you do the same thing
dude i did all that and it doesnt work. it says everything was installed but when i reboot it, it doesnt go pass the samsung.com screen. what kernel works with stock rom DI18??
I've tried both Phoenix Kernel 1.49 as well as Xtreme kernel's 1.0 version. Both work fine. I think you need to flash back to stock rom via Odin and redo the process... you know how to do that right?
i havent changed my rom im using the one the phone comes with i just want a custom kernel thats all! ive reset my phone 5 times in the last 24 hours trying to get this to work! and nothing.
The process is very simple for flashing a new ROM/Kernal, and you seem to have the concept down. You could try restoring to factory, re-rooting through the one-click to ensure it goes through correctly, than try flashing a new kernal then.
Also i know for new roms the first boot takes a while, im not sure how it is for kernals. Also i noticed theres a few different kernals around here, some for 2.1 and some for 2.2. Make sure you are using ones compatible with 2.1 if you are on the stock rom!
yeah i did that i tried babystep and step2 and both didnt work. i dont want to give up! but im over reseting my phone.
Do you get any errors at any point?
Sent from my Android using Tapatalk and Wifi/CDMA
when its installing the zip on other videos i see the yellow bar load till its done but i my phone it starts than big blue letters so up on the screen. and its goes back and it says its done and that it was installed but when o reboot my phone it wont go pass the samsung.com screen
Which kernels have you tried?
Sent from my Android using Tapatalk and Wifi/CDMA
babystep, step 2
I'm sorry but I dont know what babystep and step 2 are. Link?
Sent from my Android using Tapatalk and Wifi/CDMA
http://www.bakedsnackshack.com/source/
Its those kernels. I tried babystep and I too only see the samsung.com splash. Those kernels are probably optimized for baked snack. My guess is they dont play nice with the stock boot animation.
Sent from my Android using Tapatalk and Wifi/CDMA
Try Phoenix 1.49s.
Sent from my Android using Tapatalk and Wifi/CDMA
I'm curretly using xtreme kernal with stock rom, and then setcpu to have it set at 200min 800max... still not getting better battery life though. I think ill try phonex kernal next...
Sent from my SPH-D700 using XDA App
From the Moderator... Please read my Caution in post #27-thanks
First, before flashing the ICS LPY Rom, go back to any STOCK GB according to your liking.
Second, do a full wipe/dalvik/data WHILE YOU'RE ON STOCK GB. Restart/Reboot and start flashing the official ICS LPY Rom on ur device.
Third, since this is not a wipe rom, DONT DO IT. Once booted, RESTORE FACTORY SETTING and WIPE using the ICS OS menu. Not thru RECOVERY or CWMR. As long as u wipe/reset thru the os menu, u should be fine.
Lastly, you'll be greeted with a new device setup wizard and all the premium apps will be installed. It'll take sometime for the premium app to initialize. You'll think u're stuck at the boot screen (samsung logo), but no. Just wait, it could last a good 3 to 4 min before u see the device setup wizard.
For the time being, to avoid bricking, it is not advisable to root or install CWM for this particular release. Some kernel code might have changed making it problematic for CWMR to live side by side.
And if you do decide to root and get CWMR on ur device, DONT WIPE/FACTORY RESET thru stock recovery or CWMR. It is known to mess up ur eMMC. Just DONT.
Hope it helps.
Edit: Shorty66 just posted he bricked his note by doing factory reset from within the os. So far he's the only one at the moment. But numerous members reported bricking their device using CWM recovery & stock recovery. Just to be safe, use the os factory reset rather than recovery. Me myself have used the os factory reset at least 6-7 times as we speak without any issue for the time being.
Nice guide, perhaps you could also add the steps to safely go to a 'safe' kernel/rom if one is already using LPY?
Sent from my GT-N7000 using xda premium
+1
Would also like to know the go back to b/cm9 etc steps
Sent from my GT-N7000 using xda premium
Entropy covered that earlier. But whatever u do if u're on LPY, avoid wiping under CWM or stock recovery. Get any safe GB cf-root kernel and wipe/reset/flash from there. And dont restore nandroid backup from any leaked ics or LPY kernel. As to stock LPY device, u can just flash back to any stock gb and from there to get to any custom roms or rooted gb.
Ashren81 said:
Entropy covered that earlier. But whatever u do if u're on LPY, avoid wiping under CWM or stock recovery. Get any safe GB cf-root kernel and wipe/reset/flash from there. And dont restore nandroid backup from any leaked ics or LPY kernel. As to stock LPY device, u can just flash back to any stock gb and from there get to any custom roms or rooted gb.
Click to expand...
Click to collapse
So just to be clear, as I am currently on rooted LPY ROM + kernel, the safest thing would be to flash CF-Root GB kernel whilst still on LPY? How would this be done? Because obviously CWM functions aren't safe, and flashing a GB kernel (through Mobile Odin) on a ICS build would cause a brick also?
I really hate LPY and I want to get on to CM9 just to be safe, but I'm having trouble figuring a safe way to do so any help would be greatly appreciated.
Sent from my White Galaxy Note using Tapatalk 2
MamaSaidWhat? said:
So just to be clear, as I am currently on rooted LPY ROM + kernel, the safest thing would be to flash CF-Root GB kernel whilst still on LPY? How would this be done? Because obviously CWM functions aren't safe, and flashing a GB kernel (through Mobile Odin) on a ICS build would cause a brick also?
I really hate LPY and I want to get on to CM9 just to be safe, but I'm having trouble figuring a safe way to do so any help would be greatly appreciated.
Sent from my White Galaxy Note using Tapatalk 2
Click to expand...
Click to collapse
flash using pc odin or heimdall. get to recovery and flash/wipe or install gb backup from there. but i advise u to get back to stock gb to get a clean start and move from there.
Ashren81 said:
First, before flashing the ICS LPY Rom, go back to any STOCK GB according to your liking.
Second, do a full wipe/dalvik/data WHILE YOU'RE ON STOCK GB. Restart/Reboot and start flashing the official ICS LPY Rom on ur device.
Third, since this is not a wipe rom, DONT DO IT. Once booted, RESTORE FACTORY SETTING and WIPE using the ICS OS menu. Not thru RECOVERY or CWMR. As long as u wipe/reset thru the os menu, u should be fine.
Lastly, you'll be greeted with a new device setup wizard and all the premium apps will be installed. It'll take sometime for the premium app to initialize. You'll think u're stuck at the boot screen (samsung logo), but no. Just wait, it could last a good 3 to 4 min before u see the device setup wizard.
For the time being, to avoid bricking, it is not advisable to root or install CWM for this particular release. Some kernel code might have changed making it problematic for CWMR to live side by side.
And if you do decide to root and get CWMR on ur device, DONT WIPE/FACTORY RESET thru stock recovery or CWMR. It is known to mess up ur eMMC. Just DONT.
Hope it helps.
Click to expand...
Click to collapse
i agree with u but rooting using this way is safe for all stock changer
http://forum.xda-developers.com/showthread.php?t=1647148
i did that for 3 notes here
and u can change the the default twlancher for the lpy as its laggy with any other launcher
now its all ok for lpy ( ICS + CLEAN+ SMOOTH +ROOT )
i prefer go launcher ex
sehooo said:
i agree with u but rooting using this way is safe for all stock changer
http://forum.xda-developers.com/showthread.php?t=1647148
i did that for 3 notes here
and u can change the the default twlancher for the lpy as its laggy with any other launcher
now its all ok for lpy ( ICS + CLEAN+ SMOOTH +ROOT )
i prefer go launcher ex
Click to expand...
Click to collapse
apex launcher FTW!
nice guide!
Ashren81 said:
Third, since this is not a wipe rom, DONT DO IT. Once booted, RESTORE FACTORY SETTING and WIPE using the ICS OS menu. Not thru RECOVERY or CWMR. As long as u wipe/reset thru the os menu, u should be fine.
Click to expand...
Click to collapse
I question the validity of this, because was a reported issue using the settings factory reset too. As far as I know, settings/factory reset still uses recovery to wipe data. Might want to double check that and update your post accordingly.
The post I referenced: http://forum.xda-developers.com/showthread.php?p=26086599#post26086599
k1ng617 said:
I question the validity of this, because was a reported issue using the settings factory reset too. As far as I know, settings/factory reset still uses recovery to wipe data. Might want to double check that and update your post accordingly.
Click to expand...
Click to collapse
Yeah shorty66 just said he bricked his note using the os factory reset menu. So now we have all method bugged. But I still recommend doing a factory reset from within the os on first boot to clear things out. U wont get the premium apps installed on the first boot if u're coming from any other previous rom because LPY is not a wipe rom. U wont even get the device setup wizard on the first boot. When u do the factory reset, it'll get the premium apps to install upon boot and u get the chance to set the device up using the welcome wizard. I see most people who bricked their device went straight to the recovery and do a wipe from there. Just dont do that, never.
Ashren81 said:
Yeah shorty66 just said he bricked his note using the os factory reset menu. So now we have all method bugged. But I still recommend doing a factory reset from within the os on first boot to clear things out. U wont get the premium apps installed on the first boot if u're coming from any other previous rom because LPY is not a wipe rom. U wont even get the device setup wizard on the first boot. When u do the factory reset, it'll get the premium apps to install upon boot and u get the chance to set the device up using the welcome wizard. I see most people who bricked their device went straight to the recovery and do a wipe from there. Just dont do that, never.
Click to expand...
Click to collapse
This is how i go back to GB from ics
From lpy go to recovery, flash abyss 4.2 redpilltouch, reboot recovery, so now i'm on GB kernel recovery, wipe data, cache, dalvik. DON'T BOOT SYSTEM. Restore any nandroid GB backup, after that reboot system.
Hope it help.
hgberry said:
This is how i go back to GB from ics
From lpy go to recovery, flash abyss 4.2 redpilltouch, reboot recovery, so now i'm on GB kernel recovery, wipe data, cache, dalvik. DON'T BOOT SYSTEM. Restore any nandroid GB backup, after that reboot system.
Hope it help.
Click to expand...
Click to collapse
yes that should be the way like i've post earlier. just use the safe-kernel of ur choice. but dont restore nandroid backup from any previous ics, nandroid from previous gb is fine. nice to see ur note safely back on gb. /thumbsup
I don't understand what's all this fuss about really...
I flashed lpy thru mobile Odin (coming from gingerbread) with root option checked, and all went smooth! No pc was used at all! I was even at University when I did that!
Then 2 days later, I factory reset using stock recovery... And all went fine! I was even in a friend's car!
So what's up with all the bricking all over the forum?!!
Sent from my GT-N7000 using xda premium
Goodm7sn said:
I don't understand what's all this fuss about really...
I flashed lpy thru mobile Odin (coming from gingerbread) with root option checked, and all went smooth! No pc was used at all! I was even at University when I did that!
Then 2 days later, I factory reset using stock recovery... And all went fine! I was even in a friend's car!
So what's up with all the bricking all over the forum?!!
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
It happen randomly due to I/O bug on the kernel. While wiping big chunk of data off the partition, it'll glitch. Maybe after a wipe, 10th wipe, 11th wipe, 50 wipe etc. Maybe ur upcoming wipe will be ur last wipe, u might never know. Wiping thru CWM and stock recovery is known to produce the bricking effect. Only 1 person reported bricking thru the os factory reset.
I have to agree I don't understand how these bricks are happening. I have gone from Darky LC1 to LPY and then flashed Chainfire LPY kernel through mobile odin. I then got bored and flashed ICS stunner 26.1 through CWM. I have then gone back to CWM whilst on Stunner and Flashed Abyss Note Kernel 4.2. Then on the top of that I have flashed Alba V2 repack of LPY after a wipe/data from CWM and still no brick. I understand the risks involved but like I said not bricked yet.
Does anyone think that there maybe a different eMMC chip on some of these notes that have shipped which have bricked. Wounder if there is anyway to tell anyone looked into this. Just a thought as it might not be the software but the chip on certain devices ???
djtiny said:
I have to agree I don't understand how these bricks are happening. I have gone from Darky LC1 to LPY and then flashed Chainfire LPY kernel through mobile odin. I then got bored and flashed ICS stunner 26.1 through CWM. I have then gone back to CWM whilst on Stunner and Flashed Abyss Note Kernel 4.2. Then on the top of that I have flashed Alba V2 repack of LPY after a wipe/data from CWM and still no brick. I understand the risks involved but like I said not bricked yet.
Does anyone think that there maybe a different eMMC chip on some of these notes that have shipped which have bricked. Wounder if there is anyway to tell anyone looked into this. Just a thought as it might not be the software but the chip on certain devices ???
Click to expand...
Click to collapse
hardware conflict with newly kernel source is possible. different chip revision on different batch of notes produced could also lead to the issue. but if that is to be ruled out not to be the case, then its either samsung released a broken/buggy kernel for public usage or they make changes to the kernel source to react to CWM and the rooting community. just like how apple kept changing their baseband kernel every now and then to block jailbreaking on idevices.
to me its more like a buggy kernel. no wonder they kept pushing and delaying the ics release. ever thought of that?
djtiny said:
I have to agree I don't understand how these bricks are happening. I have gone from Darky LC1 to LPY and then flashed Chainfire LPY kernel through mobile odin. I then got bored and flashed ICS stunner 26.1 through CWM. I have then gone back to CWM whilst on Stunner and Flashed Abyss Note Kernel 4.2. Then on the top of that I have flashed Alba V2 repack of LPY after a wipe/data from CWM and still no brick. I understand the risks involved but like I said not bricked yet.
Does anyone think that there maybe a different eMMC chip on some of these notes that have shipped which have bricked. Wounder if there is anyway to tell anyone looked into this. Just a thought as it might not be the software but the chip on certain devices ???
Click to expand...
Click to collapse
You might just be in the lucky position to have a phone which doesn't have the error.
But somebody also suggested that it makes a difference what you have fleshaed before the LPY rom...
I did not have anything else than stock GB befor the official update, but perhaps there is a way to flash a specific rom before going to LPY to be safe.
Do you still know your flash history?
Hi Shorty66,
Sorry to hear about your note. I can remember being on Darky LC1 base rom full root. I downloaded the LPY.tar file flashed this via mobile odin to flash LPY via mobile odin and wiped data/cache from that program. When this was completed I had full root with the premium suit installed. Battery life was naff so I booted into CWM did full wipe along with cache davlik and flashed Stunner 26.1 rom then when this was fully booted I flashed the kernel extracted from. 19 stunner rom via mobile odin. Then when Alba releashed V2 full repack this was flashed via Red Pill 4.2 as I have this on my SD card because of the brick issues. After this was flashed I rebooted into redpill and proceeded with Flashing the Alba V2 full repack zip. This has fully booted with full root and no brick. So I dont quiet understand why my device has never bricked as im a flashaholic I tell you my mrs I always on to me about it.
Sent from my GT-N7000 using xda premium
Yeah I can understand a buggy kernel but why release it as a proper update. I cannot see them delaying it just to add the premium suit. The note and S2 share the same hardware so the building of the rom should have taken the same amount of development time apart from adding the spen into the framework. The emmc chip if im not mistaken is what the rom and the free memory is on for the internal part of storage feel free to correct me. Im just spit balling ideas here but the way the partition are read on ICS is different as somebody developed a way to bind it like on gingerbread roms. What if the way that ics roms are made screws up and when another rom is flashed when wiping takes place it just erases all the partition info on the chip and this causes the brick. If that makes any sense and when it comes to write the info that seems to start bit sticks and there is no partition information of chip info to write to which is why it just hangs.
Sent from my GT-N7000 using xda premium
Hey guys I'm new to Android in general so sorry if these seem like dumb questions. I've searched online for a while now and I can't really seem to get a concrete answer. Anyways so I got CWM 5.5.0.4 running on my 7510 just fine last night. I then did a backup of everything from within CWM 5.5.0.4. Then I went and flashed CM10 Jellybean to see if it worked fine. Went back to CWM and tried restoring back to ICS, to check that too and it worked fine. I want to mention at this point I couldn't get Titanium Backup or ROM Manager working from withint ICS at this point because it kept saying that it couldn't get root access (I rooted my 7510 through the method listed as a guide in the Developers section of this forum), but since I could restore back without a problem to ICS with all my settings intact, I thought I'd give it a try anyways.
I then flashed back to CM10, and upgraded to the newest CWM Touch version 5.8.x.x from within ROM Manager once in CM10. I then decided I wanted to go back to ICS so I tried to restore back to ICS through CWM Touch, and it didn't work. I’ve tried doing an entire normal backup, and then strictly the apps, nothing works. Keeps telling me there’s an error.
What’s the best thing to do? Switch back to 5.5.0.4? Can I do that without turning on USB debug mode? Because I didn’t check this beforehand but I can’t click on Storage in settings and even access USB period, whether it’s to transfer stuff or to turn on USB Debug mode.
Any help would be appreciated! I mainly want to go back because all my apps are setup the way I like in ICS. Unless someone knows away to restore apps properly back without going through CWM, maybe through some app that can read the backup data if that makes any sense?
HeyYoWL said:
Hey guys I'm new to Android in general so sorry if these seem like dumb questions. I've searched online for a while now and I can't really seem to get a concrete answer. Anyways so I got CWM 5.5.0.4 running on my 7510 just fine last night. I then did a backup of everything from within CWM 5.5.0.4. Then I went and flashed CM10 Jellybean to see if it worked fine. Went back to CWM and tried restoring back to ICS, to check that too and it worked fine. I want to mention at this point I couldn't get Titanium Backup or ROM Manager working from withint ICS at this point because it kept saying that it couldn't get root access (I rooted my 7510 through the method listed as a guide in the Developers section of this forum), but since I could restore back without a problem to ICS with all my settings intact, I thought I'd give it a try anyways.
I then flashed back to CM10, and upgraded to the newest CWM Touch version 5.8.x.x from within ROM Manager once in CM10. I then decided I wanted to go back to ICS so I tried to restore back to ICS through CWM Touch, and it didn't work. I’ve tried doing an entire normal backup, and then strictly the apps, nothing works. Keeps telling me there’s an error.
What’s the best thing to do? Switch back to 5.5.0.4? Can I do that without turning on USB debug mode? Because I didn’t check this beforehand but I can’t click on Storage in settings and even access USB period, whether it’s to transfer stuff or to turn on USB Debug mode.
Any help would be appreciated! I mainly want to go back because all my apps are setup the way I like in ICS. Unless someone knows away to restore apps properly back without going through CWM, maybe through some app that can read the backup data if that makes any sense?
Click to expand...
Click to collapse
Easiest way is to go back to the old cwm. The touch ver is a bit uggly according to me. (Personly i run Twrp tocuh recovery. Its nice and sleek. Gives option to compress backupps to. Includes a filemanager to. )
Otherwise if you install clock work mod from gogle play there is an option to restore apps from the backup.
Sent from my GT-P7500, JellyBean rom v6, A1 kernel v1.7 using XDA Premium HD
How exactly do I go back to the old CWM? Do I have to enable USB Debugging mode? As I mentioned I can't even do that because it's greyed out for me in CM10.
I dont know why usb debug is incheckable, i'm not a dev. But don't think it's important if you flash cwm via odin.
Use the same method you got cwm the first time.
Easiest is flashing it through odin. I guess you can follow that root guide you used initialy.
Rom manager can restore apps from backupfile. Just go deeper in menus.
Sent from my GT-P7500, JellyBean rom v6, A1 kernel v1.7 using XDA Premium HD
Hey guys,
atm I have a problem where flashing AOSP based ROMs causes some issues.
Firstly I have no boot animation with any AOSP ROM. Secondly I have no network connection, neither with nor without SIM pin. Thirdly sometimes Camera isn't connecting when opening the Camera app.
I'm using PhilZ touch 5.11.2.
TouchWiz based ROMs work without any problems.
So what can I do now to fix those issues? I have no explination on them.
Boot anmation is because of phiz recovery.
Change the recovery re-flash rom u will see boot animation.
For other 2 probs not sure.
Sent from my GT-I9500 using XDA Premium 4 mobile app
It's the recovery. It doesn't flash the ROM correctly. Use the standard CWM and you'll be good. Philz is a GREAT recovery, but it's just not ready for the S4 yet, IMO.
Just a tip: make a backup of your EFS folder ASAP. You'll find all you need here to do it. You don't want to screw that up, because if you do, you lose your IMEI and network connectivity, and your S4 will be a $600 media player and you'll not be able to make calls on it ever again.
Thanks for the help. I changed to CWM and I'll try flashing the ROM again. I'll do an EFS backup as soon as my system is running again.
Use Philz Recovery 5.10.0
The latest few versions of Philz Recovery are quite buggy. The best one so far is 5.10.0
nah I probably won't go back to PhilZ. The features you get aren't worth the problems I could experience again..
Sent from my flying Galaxy S4 GT-I9505