Hello,i need some help regarding wipe.. I have the Faux kernel and stock Rom.I want to make a fresh install,if i will wipe the phone does the kernel deletes? Thank you
"Wiping" only regards data and cache partitions. It does not interfere with /system or /boot, so no, wiping won't delete the kernel... obviously. Otherwise, your phone wouldn't boot right?
ToastnButter said:
"Wiping" only regards data and cache partitions. It does not interfere with /system or /boot, so no, wiping won't delete the kernel... obviously. Otherwise, your phone wouldn't boot right?
Click to expand...
Click to collapse
So,what i should do now for a new ROM/KERNEL?
Root your phone, get custom recovery and start flashing.
OR, if you want to go back to stock, there's a detailed tutorial somewhere in the forums
ToastnButter said:
Root your phone, get custom recovery and start flashing.
OR, if you want to go back to stock, there's a detailed tutorial somewhere in the forums
Click to expand...
Click to collapse
I have CWM,so i just need to re-flash the new kernel?
Yup.
ToastnButter said:
Yup.
Click to expand...
Click to collapse
I know that Pink kernel needs a custom rom,so now i just flash the new rom and after the new kernel right?
But Faux Kernel says that doesnt support the custom rom,wtf
Well you ALWAYS have to make sure it's compatible. Otherwise your phone won't boot, and you'll loose 10 minutes of your life getting it back on its feet.
Related
I've been playing around with a Nexus S 4G that I have lying around and never used, and I've ran into a few problems, but you've all been helpful. I rooted all my old EVO 4G's without any problem, but the other day I rooted my NS4G using a one click/simple root and downloaded ClockWorkMod etc. But now for some reason It seems like I've almost lost my root? Is that possible? I still have the little unlocked symbol when booting up.
I've searched this forum and Google and haven't found anything, which could possibly be because I don't know what to look for. I've never had this happen :/
Currently running the stock 2.3.7
Nobody? I just need a little help.
Did you flash a superuser.zip after you installed clockworkmod?
SeeNah said:
Did you flash a superuser.zip after you installed clockworkmod?
Click to expand...
Click to collapse
I thought I had... But no lol
Thank you. Sorry for pretty much making a useless thread :/
Its the Q&A forum ask away! Lol
Did flashing it work for you though?
SeeNah said:
Its the Q&A forum ask away! Lol
Did flashing it work for you though?
Click to expand...
Click to collapse
Yes, it did. Thank you!
Now I just need to re figure out how to backup my stock rom on rom manager. I need to do that if I'm going to flash a custom rom onto my NS4G correct? I've never actually gone that far with my phones lol.
Slap-Yourself :) said:
Yes, it did. Thank you!
Now I just need to re figure out how to backup my stock rom on rom manager. I need to do that if I'm going to flash a custom rom onto my NS4G correct? I've never actually gone that far with my phones lol.
Click to expand...
Click to collapse
Okay lol hold on so just go make sure you
1. Unlocked the bootloader right?
2. Flashed a custom recovery (clockworkmod)?
3. Flashed superuser for root access?
4. Now you have a stock rooted ROM?
If you have/did all that then yeah you could backup your stock rooted ROM, you don't need to back it up but its helpful just incase you mess something you could always restore it to start all over
And you could backup any ROM you install incase you didn't know, just remember when you install different ROMS make sure to do a proper full wipe which includes data/factory reset/wiping DALVIK cache, and formatting system and boot in the "mount" option in CWM. And now I think your good lol
SeeNah said:
Okay lol hold on so just go make sure you
1. Unlocked the bootloader right?
2. Flashed a custom recovery (clockworkmod)?
3. Flashed superuser for root access?
4. Now you have a stock rooted ROM?
If you have/did all that then yeah you could backup your stock rooted ROM, you don't need to back it up but its helpful just incase you mess something you could always restore it to start all over
And you could backup any ROM you install incase you didn't know, just remember when you install different ROMS make sure to do a proper full wipe which includes data/factory reset/wiping DALVIK cache, and formatting system and boot in the "mount" option in CWM. And now I think your good lol
Click to expand...
Click to collapse
Unlocked Bootloader? If I boot in fastboot it says Unlocked. Is this what you mean?
I have ClockWorkMod, but I haven't done anything with it.
I have superuser from the root
and I was working with a stock ROM the whole time....
I think I'm ok lol
So I'll back up my ROM, and flash a Nightly CM9? And back that up as well? Just perform a factory data reset before doing so, right?
Slap-Yourself :) said:
Unlocked Bootloader? If I boot in fastboot it says Unlocked. Is this what you mean?
I have ClockWorkMod, but I haven't done anything with it.
I have superuser from the root
and I was working with a stock ROM the whole time....
I think I'm ok lol
So I'll back up my ROM, and flash a Nightly CM9? And back that up as well? Just perform a factory data reset before doing so, right?
Click to expand...
Click to collapse
Yeah if it says unlocked your good to go. The super user.zip you first flashed won't be needed once you flash different ROMS, it was only needed for stock because you didn't install a ROM you just unlocked the boot loader and super user just gave you root access that didn't come with stock.
Yeah backup your stock ROM JUST in case you encounter a boot loop so you can just restore and start over, you don't need to back up CM9 that's completely your choice if you want . Its convenient though if you like CM9 but still like to flash other ROMS that way you can just go back if you miss CM9 without doing the whole setup process.
And a full wipe is
Data/factory reset
Then wipe dalvik under "advanced"
Then wipe system and boot under the "mount" option in CWM
stellar said:
Yeah if it says unlocked your good to go. The super user.zip you first flashed won't be needed once you flash different ROMS, it was only needed for stock because you didn't install a ROM you just unlocked the boot loader and super user just gave you root access that didn't come with stock.
Yeah backup your stock ROM JUST in case you encounter a boot loop so you can just restore and start over, you don't need to back up CM9 that's completely your choice if you want . Its convenient though if you like CM9 but still like to flash other ROMS that way you can just go back if you miss CM9 without doing the whole setup process.
And a full wipe is
Data/factory reset
Then wipe dalvik under "advanced"
Then wipe system and boot under the "mount" option in CWM
Click to expand...
Click to collapse
I'm not sure if I'm supposed to post links to videos or not. But I'm in love with some of the features this guy has on his NS4G
https://www.youtube.com/watch?v=IKdyAm3CgHc
He said it was a nightly etc.
The hidden status bar and bottom menu hidden is amazing. I also like the inverted G-Mail and Facebook. Is this all separate from the Nightly ROM?
Hello,
I recently installed custom Jellywiz rom on my Verizon S3.
My question is if I have new custom rom versions or if I want to switch to a different rom, do I always have to go back to stock firmware and then install the custom rom or can I directly flash over my existing custom rom ?
tomalrocks said:
Hello,
I recently installed custom Jellywiz rom on my Verizon S3.
My question is if I have new custom rom versions or if I want to switch to a different rom, do I always have to go back to stock firmware and then install the custom rom or can I directly flash over my existing custom rom ?
Click to expand...
Click to collapse
New custom rom versions: Unless otherwise stated by the developer you can go ahead and just dirty flash right on top of the current one, but if you experience issues then i'd wipe data and cache and do a clean install.
Switching to a different rom: ALWAYS do a clean install (wipe data, and cache), i can't urge how important that is, while you may not have any issues whatsoever, you definitely could encounter issues because each developer may have different changes, and you don't want stuff to mix and match.
Neverendingxsin said:
New custom rom versions: Unless otherwise stated by the developer you can go ahead and just dirty flash right on top of the current one, but if you experience issues then i'd wipe data and cache and do a clean install.
Switching to a different rom: ALWAYS do a clean install (wipe data, and cache), i can't urge how important that is, while you may not have any issues whatsoever, you definitely could encounter issues because each developer may have different changes, and you don't want stuff to mix and match.
Click to expand...
Click to collapse
Thanks. So just flashing over existing rom after wiping data and cache will work. Will do that. I do not want to go back to stock rom always as that is time consuming.
tomalrocks said:
Thanks. So just flashing over existing rom after wiping data and cache will work. Will do that. I do not want to go back to stock rom always as that is time consuming.
Click to expand...
Click to collapse
Yeah this is fine. The way I've always done it. Also in clockwork, go to advanced >wipe dalvic
Neverendingxsin said:
New custom rom versions: Unless otherwise stated by the developer you can go ahead and just dirty flash right on top of the current one, but if you experience issues then i'd wipe data and cache and do a clean install.
Switching to a different rom: ALWAYS do a clean install (wipe data, and cache), i can't urge how important that is, while you may not have any issues whatsoever, you definitely could encounter issues because each developer may have different changes, and you don't want stuff to mix and match.
Click to expand...
Click to collapse
aypeeootrek said:
Yeah this is fine. The way I've always done it. Also in clockwork, go to advanced >wipe dalvic
Click to expand...
Click to collapse
Thanks :good:
Do you know whether I am use CWMod recovery to flash stock roms or do i need to use ODIN for that?
tomalrocks said:
Thanks :good:
Do you know whether I am use CWMod recovery to flash stock roms or do i need to use ODIN for that?
Click to expand...
Click to collapse
You can flash stock roms in CWM, but be careful if they don't include a kernel. If you go from AOSP to Stock, you might get a boot loop unless you also flash a stock compatible kernel, and vice versa. Boot loop is easily recoverable of course, but it will scare new users
thnx123
yhnk you for
Zalithian said:
You can flash stock roms in CWM, but be careful if they don't include a kernel. If you go from AOSP to Stock, you might get a boot loop unless you also flash a stock compatible kernel, and vice versa. Boot loop is easily recoverable of course, but it will scare new users
Click to expand...
Click to collapse
hehehe I already got that scare after flashing new rom and it was taking a long time to boot during first boot.
Thanks anyways
When I did my wipes flashed I somehow had Air Kernel still, I think? I've been on Matr1x, but I'm not sure how to get back to the stock kernel reliably and without erasing anything.
torchie said:
When I did my wipes flashed I somehow had Air Kernel still, I think? I've been on Matr1x, but I'm not sure how to get back to the stock kernel reliably and without erasing anything.
Click to expand...
Click to collapse
Just wipe cache, dalvik and flash the stock kernel. You can find them here in the forums.
mdean1981 said:
Just wipe cache, dalvik and flash the stock kernel. You can find them here in the forums.
Click to expand...
Click to collapse
I can't find them in the forums. There's just custom kernels.
torchie said:
I can't find them in the forums. There's just custom kernels.
Click to expand...
Click to collapse
flash the stock ROM without wiping.
I have CWM 5.0.2.7. I want to upgrade from 2.3.6 Gingerbread to Android 4(PACMAN ROM preferred). I tried at least 50 - 75 times flashing >5 different ROMS, almost once bricked my phone... I found stable Gingerbread 2.3.6 and I am using it right now. I really want to upgrade to version 4, because I develop apps in Buzztouch and they will now support Android devices with Honeycomb or later. My question now is: how can I really upgrade to Android 4, because every ROM I flash is stuck at the first boot. Any help?
There is absolutely zero possibility of bricking your phone in flashing custom ROMs unless you do it in a wrong way (flashing other phone's ROM ). Same thing goes for bootloop. Wipe data,cache, dalvik cache and even format /system before flashing and also do wipes after flash. This way u can view a new dimension to the android world
swat4samp said:
There is absolutely zero possibility of bricking your phone in flashing custom ROMs unless you do it in a wrong way (flashing other phone's ROM ). Same thing goes for bootloop. Wipe data,cache, dalvik cache and even format /system before flashing and also do wipes after flash. This way u can view a new dimension to the android world
Click to expand...
Click to collapse
I already knew everything you said, even more, but thanks for idea of formatting /system. Maybe that is the main problem. Thank you so much!
UPDATE! Nothing is working. I think I will give up on ROMing.
Lol which baseband are u on? Try to flash latest stock rom ie DXKT7 and then flash a custom rom.
swat4samp said:
Lol which baseband are u on? Try to flash latest stock rom ie DXKT7 and then flash a custom rom.
Click to expand...
Click to collapse
I cannot find any with DXKT7 baseband. I am on XWKTI.
I got the same problem. Flashing from stock 2.3.6 XWKTI to any other cm 10.1 rom is not working. Clearing caches etc. does not help.
Any solution to this?
The latest rom I tried is cm-10.1-20130907-NIGHTLY-beni.zip. No luck so far.
What is wrong here?
Solved. I used the wrong CWM. beni_cwm-5_ext4_v2.tar does the trick.
Junnix said:
Solved. I used the wrong CWM. beni_cwm-5_ext4_v2.tar does the trick.
Click to expand...
Click to collapse
How did you solve the problem?
AleksaSavic said:
How did you solve the problem?
Click to expand...
Click to collapse
Did u ever successfully used ny custom rom b4.. or is this ur 1st chance...??
AleksaSavic said:
How did you solve the problem?
Click to expand...
Click to collapse
The CWM you use might be a one which is not working. At least I used a CWM 5.0.2.7. But it was rfs which is not compatible with the S5670.
So install CWM beni_cwm-5_ext4_v2.tar and you will be able to install any custom rom without problem.
Junnix said:
The CWM you use might be a one which is not working. At least I used a CWM 5.0.2.7. But it was rfs which is not compatible with the S5670.
So install CWM beni_cwm-5_ext4_v2.tar and you will be able to install any custom rom without problem.
Click to expand...
Click to collapse
It is this:
http://forum.xda-developers.com/showthread.php?t=1339640
BRO F U WANT TO UPDATE TO 4.+ THEN FOLLOW THESE STEPS
BOOT TO RECOVERY
WIPE DATA
WIPE CACHE
ADVANCE>>WIPE DALVIK CACHE
MOUNTS AND STORAGE>>FORMAT SYSTEM
INSTALL THE ROM U WANT
WIPE DATA
WIPE CACHE
REBOOT
WAIT FOR 5-10 MINS AS IT TAKS TIME FOR FIRST BOOT
STILL NOT HAPPENING
THEN UR DOWNLOADED FILE MUST BE CORRUPTED SO DOWNLOAD THE FILE AGAIN
Galaxy_Rohit said:
Did u ever successfully used ny custom rom b4.. or is this ur 1st chance...??
Click to expand...
Click to collapse
Flashed custom ROMs at least 75 times. I am not a newbie.
Junnix said:
The CWM you use might be a one which is not working. At least I used a CWM 5.0.2.7. But it was rfs which is not compatible with the S5670.
So install CWM beni_cwm-5_ext4_v2.tar and you will be able to install any custom rom without problem.
Click to expand...
Click to collapse
I already have CWM 5.0.2.7. Can I install it again via Odin or not?
ZmisiS said:
It is this:
http://forum.xda-developers.com/showthread.php?t=1339640
Click to expand...
Click to collapse
I flashed that already(I think).
vinayaksuresh said:
BRO F U WANT TO UPDATE TO 4.+ THEN FOLLOW THESE STEPS
BOOT TO RECOVERY
WIPE DATA
WIPE CACHE
ADVANCE>>WIPE DALVIK CACHE
MOUNTS AND STORAGE>>FORMAT SYSTEM
INSTALL THE ROM U WANT
WIPE DATA
WIPE CACHE
REBOOT
WAIT FOR 5-10 MINS AS IT TAKS TIME FOR FIRST BOOT
STILL NOT HAPPENING
THEN UR DOWNLOADED FILE MUST BE CORRUPTED SO DOWNLOAD THE FILE AGAIN
Click to expand...
Click to collapse
/system - ext4
/data - rfs
/cache - rfs
/db-data - unknown
I am using this apk:
CF-Root-ext4-v1.3-Addon.apk from Chainfire, but it is not made for my phone.
It has options for converting ext4 to rfs and rfs to ext4, but I am scared to do that. How can I manually convert from rfs to ext4? And, will my system even boot after doing that?
Possible solution...
Hi,
I have successfully flashed cm-10.1-20130914-NIGHTLY-beni.zip using ClockWorkMod 6.0.2.7. I initially had problems getting cm 10.1 to boot, it would just stop at the cyanogenmod logo. I got this ROM to work by first flashing ╰☆╮ [ROM][CM7.2] JellyBread v5.0 | SURPRISE! UPLOAD COMPLETE! ╰☆╮. then flashing the nightly.
Good luck:fingers-crossed:.
Regards,
jemail
I wouldn't recommend installing ICS on a Galaxy Fit. The phone doesn't really stand that much of the ROM itself.. I use a rom that'll look exactly alike it, that's basically it. But I tried Lenio vQuattro. it seemed pretty nice If you really need to then try this rom. And it wouldn't be such a bad idea tp update CWM, or try another Recovery.
AleksaSavic said:
/system - ext4
/data - rfs
/cache - rfs
/db-data - unknown
I am using this apk:
CF-Root-ext4-v1.3-Addon.apk from Chainfire, but it is not made for my phone.
It has options for converting ext4 to rfs and rfs to ext4, but I am scared to do that. How can I manually convert from rfs to ext4? And, will my system even boot after doing that?
Click to expand...
Click to collapse
Good question.
I really got no answere to that question. But as far as I know there are CMW for rfs and for ext4/ext3 filesystems.
If you use the wrong CMW than the phone will hang in a boot loop after flashing. That's what I had.
So I suggest you should try different CMW. For rfs and ext4. Better to flash them with Odin. I used Odin_Multi_Downloader_v4.42.exe.
As CWM try: http://forum.xda-developers.com/showpost.php?p=24719114&postcount=1387 or this CWM http://androidlegend.com/dl/beni_cwm-5_ext4_v2.tar
One of these should work for you.
I'm confused about revert back from custom kernel. If I flash some custom kernel that changing the ramdisk or other binaries how do I reset kernel partition before moving back to stock or another kernel without issues?
micens said:
I'm confused about revert back from custom kernel. If I flash some custom kernel that changing the ramdisk or other binaries how do I reset kernel partition before moving back to stock or another kernel without issues?
Click to expand...
Click to collapse
for stock, just flash the stock kernel(zipped or boot.img) or reflash the rom without wiping. for going to another custom kernel, just flash the other kernel over without wiping anything. or you can reflash your rom, then the new kernel, without wiping anything.
Hi,
Just in case for a stock kernel flashable zip: http://forum.xda-developers.com/showthread.php?t=2518816.
Thank you
So, if I flash the stock kernel from recovery it returns everything was changed by custom kernel?
That`s good, and so easy
micens said:
Thank you
So, if I flash the stock kernel from recovery it returns everything was changed by custom kernel?
That`s good, and so easy
Click to expand...
Click to collapse
everything within the kernels range, yes. but a few kernels include system files, it wont change those files. reflashing your rom(without wiping) will get those files back. most kernels dont touch system files, but a very few kernels do.
Ok. Thank`s again :good:
One question more
When I did Full Wipe, everything about custom kernel will gone? Because I don`t understand about changed ramdisk and this staff
micens said:
One question more
When I did Full Wipe, everything about custom kernel will gone? Because I don`t understand about changed ramdisk and this staff
Click to expand...
Click to collapse
no. only your user data will go. kernel/rom stays.
Thank`s,
But, with Full Wipe thing I mean Factory reset + Wipe Cache + Wipe Dalvik Cache + Manual Format /system. Do I need doing "fastboot erase boot" or something like this to full Wipe custom kernel?
micens said:
Thank`s,
But, with Full Wipe thing I mean Factory reset + Wipe Cache + Wipe Dalvik Cache + Manual Format /system. Do I need doing "fastboot erase boot" or something like this to full Wipe custom kernel?
Click to expand...
Click to collapse
all that does is wipe data.
you cant just wipe a kernel away. you need to replace it. you phone can not boot or operate in any way without a kernel. a kernel connects the os to the processor to the battery to the rest of the hardware. if you erase your kernel, you will have a non functional electronic device. you will either have to flash a different kernel, or reflash your rom.
if you erase your kernel, you will have a non functional electronic device. you will either have to flash a different kernel, or reflash your rom.
Click to expand...
Click to collapse
Yes I know this... When erase kernel with "fastboot erase boot" and then flash another kernel that`s it? No data from other kernel like changed ramdisk leave somewhere? That part of this I do not understand about changed ramdisk and other binaries from some kind of custom kernel.
micens said:
Yes I know this... When erase kernel with "fastboot erase boot" and then flash another kernel that`s it? No data from other kernel like changed ramdisk leave somewhere? That part of this I do not understand about changed ramdisk and other binaries from some kind of custom kernel.
Click to expand...
Click to collapse
Just flash another kernel. You can flash kernels over each other with no problem.
Sent from my Nexus 5
micens said:
Yes I know this... When erase kernel with "fastboot erase boot" and then flash another kernel that`s it? No data from other kernel like changed ramdisk leave somewhere? That part of this I do not understand about changed ramdisk and other binaries from some kind of custom kernel.
Click to expand...
Click to collapse
you can do that if you like.
anyways, if a kernel has its own ramdisk, and not an anykernel, then the ramdisk will get replaced every time you flash a kernel. if you are flashing an anykernel, then its best to either reflash your rom first or the roms kernel(stock kernel if stock rom). you can do it your way too, erase than flash
That` s what interested me
Thank you very much