Related
I know this is not a development thread but I must insist we have something like this in this area. I would ask a mod to keep this sticky or maybe link to it from another sticky thread. I feel it's important to all development for accurate results and debug information.
I see this all the time. People think they are fully wiping when a developer asks for it. I believe that some people still don't understand what a full wipe is because there is no such single option in ClockWorkMod Recovery. Most likely the reason for that is because Koush didn't want too many posts about "I'm stuck on Google logo" or "my phone won't boot". So here is a test you can do yourself: Backup your ROM of course, and then do a full wipe. Then don't install anything and just reboot. If you end up pass the Google logo and onto the boot loop screen, then what you think is a full wipe is incorrect. If you are stuck on the Google logo and nothing is happening however, then congratulations... you know what you're doing
For the rest of you, here are proper steps to fully wipe without leaving any trace of ROM on your phone:
wipe data/factory reset
format /system
format /boot
Now most people think that the first option is enough. That may often be the case but because the developer can drastically change the contents of the /system folder, things can get messed up if you don't format it. And guess what, that first option will not do it. Wipe data/factory reset only wipes the /data folder which contains your personal settings and all the apps you installed. The ROM is then left blank as if you just flashed it and you can start over. FYI, the format of boot partition simply wipes the boot animation and you can restore it using the advance option in recovery from ROM to another.
I've seen some zip files which do this automatically so that's fine but at least you know what needs to be done to fully wipe.
There you go. I hope this clears some things. Now lets flash some ROMs!
Thank you
Sent from my Nexus S 4G using XDA App
Sticky please!
I follow the above wipe method for my Epic Touch 4G,SGSII, with the exception of flashing Calkulins Format All.zip at the very end and i havent experienced any issues yet. Hope i didnt just jinx myself...
Simple, yet I'm sure beginners miss it. I also vote for a sticky.
Isn't the dalvik cache stored in the /data partition?
Hence, factory reset necessarily wipes dalvik but wipe dalvik only wipes the dalvik portion of the data partition?
Sent from my Sammy Nexus 4G using XDA App
all we need is a zip that does all of that and were good!!
Sent from my Nexus S 4G using XDA App
no need to wipe when restoring?
Or use amonRA. Best recovery yet.
Sent from my Nexus S using Tapatalk
donsh00tmesanta said:
no need to wipe when restoring?
Click to expand...
Click to collapse
Nope, restoring will format each partition before it restores it.
+1 for sticky
This is one reason I like the cwm mods...all the wipe options are in one place
kdepro said:
Isn't the dalvik cache stored in the /data partition?
Hence, factory reset necessarily wipes dalvik but wipe dalvik only wipes the dalvik portion of the data partition?
Sent from my Sammy Nexus 4G using XDA App
Click to expand...
Click to collapse
Yeah. Forgot that its the case. Op edited. Only 3 steps now.
Hi I really like your thread!
Can I post a similar thread on the Vibrant forum? I'll give you credit!
Sent from my Surround.
Does anyone know the edify syntax off the top of their head to properly accomplish this? most of my attempts haven't seemed to work. would they all be formatted EMMC, even SDcard and system?
Or switch to a better recovery.
http://rzdroid.com/ftp/recovery/gingerbread/2.1.4/RZR-2.1.4-download.html
Sent from my Nexus S 4G using Tapatalk
VeryCoolAlan said:
Hi I really like your thread!
Can I post a similar thread on the Vibrant forum? I'll give you credit!
Sent from my Surround.
Click to expand...
Click to collapse
No problem go ahead. The more people know the better.
pfer10 said:
Or switch to a better recovery.
http://rzdroid.com/ftp/recovery/gingerbread/2.1.4/RZR-2.1.4-download.html
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
I prefer kush's recovery. And this is a feature as far as I'm concerned. I usually don't do system format but when doing beta or alfa testing this is a must.
really2 good post man.. i've flash rom with full wipe as u said.. thanks a lot dude..
oICSv43 - *Matri1x* v13.0
Thanks. I never realized i should format the /boot. I have never done that.
Evo_Shift said:
Thanks. I never realized i should format the /boot. I have never done that.
Click to expand...
Click to collapse
Well technically you shouldn't have to but this thread is about a full wipe so to wipe any traces you need to wipe it.
Hi guys,
The question is as above. How do I update my paranoid android rom through goo manager?
I downloaded the new rom files but I ain't sure what to do under the flahs rom section. Do i have to do a factory reset or do i have to wipe the cache?
I tried updating once without any of these options. In the end, i lost my google apps. When I reinstore it, the expanded desktop function went missing. So I am hoping that someone can tell me the proper way of flashing it to avoid this problem in the future. Thank you!
Go read the first post of the paranoid android rom under android original development. Don't flash things until you read the instructions. Cache is wiped by the rom, and you need gapps with a new install.
Sent from my Nexus 7 using xda app-developers app
delonicdevil said:
Hi guys,
The question is as above. How do I update my paranoid android rom through goo manager?
I downloaded the new rom files but I ain't sure what to do under the flahs rom section. Do i have to do a factory reset or do i have to wipe the cache?
I tried updating once without any of these options. In the end, i lost my google apps. When I reinstore it, the expanded desktop function went missing. So I am hoping that someone can tell me the proper way of flashing it to avoid this problem in the future. Thank you!
Click to expand...
Click to collapse
as mentioned, you should always read the ROM thread completely before you flash.
the correct procedure is to download the updated zip, optionally check the md5 sum to make sure it did not get corrupted in transit [but if it got corrupted, I think CWM will tell you, and fail to even try to flash the zip], then flash the rom, and then flash gapps before rebooting. [if you reboot before flashing gapps, you will have to re-login, and re-authenticate apps like Google Voice, etc].
mvmacd said:
as mentioned, you should always read the ROM thread completely before you flash.
the correct procedure is to download the updated zip, optionally check the md5 sum to make sure it did not get corrupted in transit [but if it got corrupted, I think CWM will tell you, and fail to even try to flash the zip], then flash the rom, and then flash gapps before rebooting. [if you reboot before flashing gapps, you will have to re-login, and re-authenticate apps like Google Voice, etc].
Click to expand...
Click to collapse
and one more thing, flash a new kernel ONLY after the first reboot.
Billchen0014 said:
and one more thing, flash a new kernel ONLY after the first reboot.
Click to expand...
Click to collapse
thanks alot!
Billchen0014 said:
and one more thing, flash a new kernel ONLY after the first reboot.
Click to expand...
Click to collapse
OH..I didn't knew it. Thanks!
I am not getting on how to do that
Hi,
Can any one post link to forum?
I am using paranoid android and in goomanager its showing new update available..!
after downloading zip what to do next?
If any one can put screenshot or list step it would be much helpful..
Thanks in advance...
Balaji_NEXUS said:
OH..I didn't knew it. Thanks!
Click to expand...
Click to collapse
Billchen0014 said:
and one more thing, flash a new kernel ONLY after the first reboot.
Click to expand...
Click to collapse
This actually makes no difference, aside from making the process more time consuming. The few and far between anecdotes that led to this practice are a cum hoc ergo propter hoc fallacy. Without a doubt, it does not hurt anything, but it also yields no real benefit over flashing in the same recovery session.
Billchen0014 said:
and one more thing, flash a new kernel ONLY after the first reboot.
Click to expand...
Click to collapse
This doesn't really matter, apart from making you have to "Android is Upgrading" 2x.
The process I follow which never fails me is (there may be a quicker way, but I know this will always work):
1 - Download ROM / Kernel / GAPPS etc
2 - Move all downloaded files to a single folder named "Flashing" or something
3 - Reboot to Recovery
4 - Wipe Cache and Dalvik Cache
5 - Flash ROM
6 - Flash GAPPS
7 - Flash Kernel
8 - Wipe Cache / Dalvik
That is the process for updating Paranoid android
Updating to a completely different ROM would require a Factory reset and Format
Wilks3y said:
This doesn't really matter, apart from making you have to "Android is Upgrading" 2x.
The process I follow which never fails me is (there may be a quicker way, but I know this will always work):
1 - Download ROM / Kernel / GAPPS etc
2 - Move all downloaded files to a single folder named "Flashing" or something
3 - Reboot to Recovery
4 - Wipe Cache and Dalvik Cache
5 - Flash ROM
6 - Flash GAPPS
7 - Flash Kernel
8 - Wipe Cache / Dalvik
That is the process for updating Paranoid android
Updating to a completely different ROM would require a Factory reset and Format
Click to expand...
Click to collapse
You can safely leave off steps 2, 4, & 8
Anything you download using goo goes into a folder called goo manager. Just flash from there.
Wiping cache and dalvik is an old wives tale so to speak. You aren't doing a damn bit of good doing that. You can skip it
Sent from my Galaxy Nexus
Pirateghost said:
You can safely leave off steps 2, 4, & 8
Anything you download using goo goes into a folder called goo manager. Just flash from there.
Wiping cache and dalvik is an old wives tale so to speak. You aren't doing a damn bit of good doing that. You can skip it
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I know about the Goo Folder, however I like to keep all my stuff in the same place, and I download my Kernels from browser so I made my own for Flashing
Why is it a wives tale?
Thanks
Wilks3y said:
I know about the Goo Folder, however I like to keep all my stuff in the same place, and I download my Kernels from browser so I made my own for Flashing
Why is it a wives tale?
Thanks
Click to expand...
Click to collapse
Because when you flash a new ROM to /system, it has to rebuild the dalvik for the signature on the new ROM. Android handles this on its own. I haven't checked but I bet the updater-script wipes cache for you also. I have never manually wiped cache and dalvik for a ROM update on my nexus devices.
Sent from my Galaxy Nexus
Pirateghost said:
Because when you flash a new ROM to /system, it has to rebuild the dalvik for the signature on the new ROM. Android handles this on its own. I haven't checked but I bet the updater-script wipes cache for you also. I have never manually wiped cache and dalvik for a ROM update on my nexus devices.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Thanks for the advice bud
I'm guessing its still necessary if going to a whole new ROM?
Wilks3y said:
Thanks for the advice bud
I'm guessing its still necessary if going to a whole new ROM?
Click to expand...
Click to collapse
When going from one rom to another the only thing that you should do is run factory reset in recovery
Sent from my Galaxy Nexus
Pirateghost said:
When going from one rom to another the only thing that you should do is run factory reset in recovery
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Ok great.
Appreciate that
I thought we could benefit from having a stupid questions thread here in the S4 Q&A section. This thread is for those who have what they may feel is a stupid or very simple question. Please read through the forum threads and use the search first. Lets all work together to give answers where we can without speculating. If you don't know, don't answer. If you do, let's get these stupid questions out there and answered!
Remember, the only stupid questions are the ones you don't ask.
Any flaming will be reported. All XDA rules apply so read up.
Props to @lumin30 and @ShadyAce80 for setting this up in the S 4G and S3 forums where I first found them. Cheers!
First stupid question, why do we have a stupid question thread? We are all genius's here. Nah, just kidding
It is alway good to have a "no flame" "safe" thread. Thanks for starting it--:good:
The only stupid question is the one that never got asked!
I am giving a thanks also.
I've been lurking here for a couple years, having had a Galaxy Nexus up until now and just used the toolkit cuz I was scared of the more complicated stuff.
Got an S4 this week and really wanted to get an AOSP rom on it, so the last two days I've spent reading and reading and finally getting the guts to flash CM 10.1. Its working fine, just a couple small things I've noticed, but I have a dumb question....
The first time I attempted to flash CM, I ran a backup and then tried a zipped backup in CWM. So when I flashed CM and loaded it, it said I had like 3GB left. So I deleted ALL data/caches and deleted backups in CWM, thinking it would clear everything off, but now I still only have 6ish GBs of storage left. With the stock ROM I have just over 9GB I think.
Is there anywhere else I should be checking to clear out useless data on the internal memory? I would've thought clearing everything in CWM would've got it, but it doesn't seem to have.
Jashyk said:
I've been lurking here for a couple years, having had a Galaxy Nexus up until now and just used the toolkit cuz I was scared of the more complicated stuff.
Got an S4 this week and really wanted to get an AOSP rom on it, so the last two days I've spent reading and reading and finally getting the guts to flash CM 10.1. Its working fine, just a couple small things I've noticed, but I have a dumb question....
The first time I attempted to flash CM, I ran a backup and then tried a zipped backup in CWM. So when I flashed CM and loaded it, it said I had like 3GB left. So I deleted ALL data/caches and deleted backups in CWM, thinking it would clear everything off, but now I still only have 6ish GBs of storage left. With the stock ROM I have just over 9GB I think.
Is there anywhere else I should be checking to clear out useless data on the internal memory? I would've thought clearing everything in CWM would've got it, but it doesn't seem to have.
Click to expand...
Click to collapse
Did u wipe/format system ?
sent from my SGH - leet ( i337) using Tapatalk 4 beta
oddspec said:
Did u wipe/format system ?
sent from my SGH - leet ( i337) using Tapatalk 4 beta
Click to expand...
Click to collapse
This is where I show my inexperience.
With cwm 6.0.3.2 I did from the menu:
Wipe data/factory reset
Wipe cache partition
Wipe dalvik cache
That first one should be the format, right? Or is there another one I missed?
Jashyk said:
This is where I show my inexperience.
With cwm 6.0.3.2 I did from the menu:
Wipe data/factory reset
Wipe cache partition
Wipe dalvik cache
That first one should be the format, right? Or is there another one I missed?
Click to expand...
Click to collapse
first, make sure you have a backup and your rom/gapps on a micro sd card. thats my soapbox
wipe data, wipe cache, wipe dalvik, format system, format /data.
flash rom/gapps, reboot.
I will send many to this thread...
xBeerdroiDx said:
first, make sure you have a backup and your rom/gapps on a micro sd card. thats my soapbox
wipe data, wipe cache, wipe dalvik, format system, format /data.
flash rom/gapps, reboot.
Click to expand...
Click to collapse
Dang, those formatting steps are what I missed. Will definitely have to do more reading. Thanks for the help guys!
I have a question about trying to get this Recovery rom on my phone. Also I'm posting all this here because for whatever reason I'm not allowed to post in the development forum.
http://forum.xda-developers.com/showthread.php?t=2291956
I already put CASUAL on my phone by following this;
http://forum.xda-developers.com/showthread.php?t=2297900
So anyways, my question is, I've downloaded all 3 files and parts of the directions really confuse me. namely direction #2;
2) using a root file manager remove /system/etc/install-recovery.sh
What root file manager? CASUAL? do I do it right now before flashing this recovery? meaning is the file it wants me to remove is already on my phone?
next step;
3) extract the zip
What zip? I downloaded 3...
next step;
4) use the following adb shell/terminal commands:
Code:
adb push recovery.lok /data/local/tmp/
adb push loki_flash /data/local/tmp/
adb shell
su
chmod 755 /data/local/tmp/loki_flash
/data/local/tmp/loki_flash recovery /data/local/tmp/recovery.lok
I just don't understand this at all, where do I do this?
In short, I'm eventually trying to flash CleanROM;
http://forum.xda-developers.com/showthread.php?t=2317772
I just hope I'm heading at least in the right direction. Thanks.
scott14719 said:
I will send many to this thread...
Click to expand...
Click to collapse
You got that right..and you're just the man to do it...I have no doubt.
TheAxman said:
You got that right..and you're just the man to do it...I have no doubt.
Click to expand...
Click to collapse
I am completely serious about this to the point I vote that this thread get stickied! :good:.
baseband question
Hello all!
I have a question regarding basebands ... many of the roms say you must be MDL baseband. My canadian I337M is MVLUAMDJ baseband. However in a post in the devellopment section it says the only canadian one is MUMUAMDJ. Why is mine different? Did I do something wrong when I rooted my device. Others in the modem form said they are running this baseband as well. I was gonna post there but I cant cause im a noob. I would like to try some of the custom roms but do not know if it is safe to do so. Thanks in advance for your help!!!
scott14719 said:
I am completely serious about this to the point I vote that this thread get stickied! :good:.
Click to expand...
Click to collapse
+1, you da man, and they should create a xda position, message police, and when they see ya coming, they best get to running
Here is a stupid question, I have us att device, I have canadian att people asking me how to do this and that, where the hell are their kernels and such? By the looks of things, don't they just use att standard (us) kernels? Don't they use a completely different modem also? Its obvious they can't find it....so LET ME find it...sheez...
someone please! Look at the post above this one....COMPLETELY LOST.
Update: nevermind I found the Canadian kernels. Took a whole 2min.
Why Ax, are you getting involved, it doesn't concern you...are ya stupid?
Is this the thread were they hold your hand? I heard about this new thing they are trying here.
unclegrandpa said:
I have a question about trying to get this Recovery rom on my phone. Also I'm posting all this here because for whatever reason I'm not allowed to post in the development forum.
http://forum.xda-developers.com/showthread.php?t=2291956
I already put CASUAL on my phone by following this;
I just hope I'm heading at least in the right direction. Thanks.
Click to expand...
Click to collapse
If you used the casual root method then you already have a recovery (twrp) on your device. Check out the I337 link in my signature for information on continuing.
TheAxman said:
Update: nevermind I found the Canadian kernels. Took a whole 2min.
Click to expand...
Click to collapse
excellent job, sir. :good:
is there a way to add USB Mass Storage option to the S4?
Noob here How do you guys get those awesome banners those things are sick?:thumbup:
Sent from my SAMSUNG-SGH-I337 using xda premium
IEndz said:
Noob here How do you guys get those awesome banners those things are sick?:thumbup:
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
some developers post them on their ROM threads. some users just make their own.
Cool thanks
Sent from my SAMSUNG-SGH-I337 using xda premium
Im not rich or I would have got a newer version tablet by now, but if anyone who helps has a donate button I have no issue donating a couple dollars to the person who helps me get this done, Thanks. Or just a couple dollar PP gift. better than nothing I guess.
I just want to be sure I dont mess anything up here. I have a nexus 7 wifi model.
I used NRT to unlock and root and all seems fine. Am I correct in this:
I use nandroid backup to backup first
Put ROM file on device (where do I put it?)
Wipe (is this done via nexus root toolkit or is ok do do in the custom recovery?)
Then what, boot into recovery and find the ROM and install it via recovery install button?
Then do I do the same with a kernal? Where do I put it?
Then done?
I know there are guides around but for a complete newbie I need to be sure cause I dont always see a complete fully explained step by step. Just like when I was stock not getting SU to work after rooting via nrt, I did read to flash SuperSU.zip, but had no idea how, then when I found the file and thought maybe install from recovery meant same as flash, I didnt know the message about messing the device up was normal so I was afraid at first.
THANKS to any replies,
Been unsure for days now trying to make sure my ducks are in a row before i commit to a ROM/Kernal. I want to CPU control for both under and overclocking etc. Mainly overclock just a little. I must say I love root already, got stuff to work I couldn't before
1. Create nandroid- there's a free app called something like nandroid on line - very simple to use
1a. I'd also recommend backing up with titanium backup app. It means you can keep your app data (e.g. game progress) when switching between ROMs, unlike a nandroid which is just a backup of your device as a restorable image
2. Put ROM file on device - ROM will be a .zip file, out it wherever you want, as long as you remember where it is
3. Put kernel anywhere on device - easiest to find a kernel with .zip format (recommend M-kernel)
4. Wipe - from custom recovery
5. Hit install in your custom recovery, I always flash kernel and then ROM, but I don't think it really matters
Install from recovery and flash are the same thing.
I'd recommend only flashing ROM or kernel and sticking with that set up for a few days, then flashing the other desired element. That way, if anything goes wrong then it's easier to pinpoint.
Good luck!!
Sent from my HTC Desire C using xda app-developers app
THANKS! Don't see a donate button, did you want anything?
No, of course not! God luck!
Sent from my Nexus 7 using xda app-developers app
butler0607 said:
5. Hit install in your custom recovery, I always flash kernel and then ROM, but I don't think it really matters
Click to expand...
Click to collapse
Actually that completely matters. Flashing a kernel before rom is worthless because the rom contains a kernel that will replace whatever you have just flashed.
If you want to run a custom kernel on a rom it is recommended to boot into the rom first before flashing the kernel.
Pirateghost said:
Actually that completely matters. Flashing a kernel before rom is worthless because the rom contains a kernel that will replace whatever you have just flashed.
If you want to run a custom kernel on a rom it is recommended to boot into the rom first before flashing the kernel.
Click to expand...
Click to collapse
If I just want root access and overclock should i just flash kernal and forget a rom?
can i revert back to stock kernal if need to? ask cause need to find a kernal that has V4L enabled for a usb camera app i use currently to use an inspection camera via usb on my tablet. I guess i need to read what various roms and kernals add. do i need to do both. Hard to know what to pick out of them, lol.
Thanks for advice.
Anyone know of a list to show ROMs with V4L enabled? None seem to mention it?
I have read and see different suggestions around on various sites. What all do I wipe? I have read cache, dalvik cache, plus other stuff. What all must I wipe before flashing a rom or kernel? I did a nandroid backup already.
PirateGhost, Ill donate a couple dollars if you help, thanks.
Thanks.
When going from one rom to a different one all you need to do in custom recovery is select factory reset.
This wipes out your currently installed apps, their settings, but doesn't touch your 'sdcard'
Wiping dalvik is pointless as it's automatically handled in the rom process, and cache is wiped in factory reset.
When switching kernels follow the instructions provided by the dev. If no instructions are provided, it's safe to assume you just flash without wiping anything.
When doing this, I'd recommend titanium backup too. When you do a factory reset, all apps are lost, but some data is kept (not sure on the details). Basically Titanium allows you to restore all your apps with data when you change ROMs.
Sent from my Nexus 7 using xda app-developers app
Pirateghost said:
When going from one rom to a different one all you need to do in custom recovery is select factory reset.
This wipes out your currently installed apps, their settings, but doesn't touch your 'sdcard'
Wiping dalvik is pointless as it's automatically handled in the rom process, and cache is wiped in factory reset.
When switching kernels follow the instructions provided by the dev. If no instructions are provided, it's safe to assume you just flash without wiping anything.
Click to expand...
Click to collapse
Thanks! Ill donate a couple dollars later today when I get back from the doctor.
I have not put any customs ROM(s) on yet, so is it the same still? All I have done so far is unlock/root with custom recovery and nandroid backup....
butler0607 said:
When doing this, I'd recommend titanium backup too.
Click to expand...
Click to collapse
Yeah I backed up the one app I needed to via TB, I just recently unlocked and rooted so lost most app data anyway and have only added one back so far. Thanks.
butler0607 said:
When doing this, I'd recommend titanium backup too. When you do a factory reset, all apps are lost, but some data is kept (not sure on the details). Basically Titanium allows you to restore all your apps with data when you change ROMs.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
No data is kept except what's on the sdcard. Mostly only game saves and some basic stuff. Apps databases are wiped during factory reset.
Pirateghost said:
No data is kept except what's on the sdcard. Mostly only game saves and some basic stuff. Apps databases are wiped during factory reset.
Click to expand...
Click to collapse
Thanks, Ill donate a couple bucks. had bad day yesterday so wasn't on much.
Is it normal for the donate link to be missing the regular PayPal security info on the browser?
eBandit078 said:
Is it normal for the donate link to be missing the regular PayPal security info on the browser?
Click to expand...
Click to collapse
I have no idea what this means.
Pirateghost said:
I have no idea what this means.
Click to expand...
Click to collapse
Maybe Ill just do it and change my password when finished. Thanks. Sorry not replied yet have been in a lot of pain Only a couple dollars but better than nothing I guess. Thanks for your help. Ill be back online tonight to do it.
eBandit078 said:
Maybe Ill just do it and change my password when finished. Thanks. Sorry not replied yet have been in a lot of pain Only a couple dollars but better than nothing I guess. Thanks for your help. Ill be back online tonight to do it.
Click to expand...
Click to collapse
Not forgot about you, had family issues, holiday etc, well did forget but I'll look into why it does that and figure it out. Sorry for delay.
This a simple guide I made for the note 3. Seeing these 2 questions being asked alot here so posting it here. Will need to edit it a bit so currently it's a WIP.
NOTE- First thing you should do before flashing roms/kernels for the first time is backup EFS.
How to flash CLEAN flash roms -*This is how I flash roms(even updates of the same rom) and the method i recommend to users. It is better to take 10 mins to set your phone again rahter than wasting more time to fix issues that could have been avoided by a clean flash.
NOTE- This is a MUST when changing roms.
1. Make a nandroid backup in recovery
3. Wipe data/factory reset
4. Wipe system
5. Wipe cache
6. Wipe dalvik
7. Flash ROM
8. Flash gapps
9. Flash kernel(optional)
10. Reboot
11. Wait 10 mins, then do another reboot
12. Enjoy
How to DIRTY flash roms -*This method is used by users when flashing a update of the same rom.*
NOTE- Some users follow this and some just flash the rom without wiping anything.
Note- If you flash rom that has aroma installer you will need to edit the updater script to make sure the aroma doesn't wipe system before flashing rom.
1. Make a nandroid backup in recovery
3. Wipe cache
4. Wipe dalvik
5. Flash ROM
6. Flash gapps
7. Flash AK kernel(optional)
8. Reboot
9. Wait 10 mins, then do another reboot
10. Enjoy
How to SUPER CLEAN flash roms -*This is the method that I recommend to your that have weird issues, even after clean flashing.
Will be adding this method. Need to edit it a bit.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
How to flash flash kernels -*Many users say to wipe cache/dalvik but it's useless as neither if their partitions are affected when flashing a kernel.
1. Boot into recovery*
2. Flash kernel*
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
@Khizar welcome back man, good to see you're writing guides again. Get that RC title again!
Sent from my OnePlus One using Tapatalk VIP
nicholaschum said:
@Khizar welcome back man, good to see you're writing guides again. Get that RC title again!
Sent from my OnePlus One using Tapatalk VIP
Click to expand...
Click to collapse
Yeah let's hope ppl actually read and my time editing see stuff to make it for OPO isn't wasted.. These forums seem to be worse than the note 3 ones.. Man saw this guy today who apparently couldn't find the link to gapps that was posted in the OP.. SMH
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Khizar said:
This a simple guide I made for the note 3. Seeing these 2 questions being asked alot here so posting it here.
Click to expand...
Click to collapse
While this is true, it's because people are too lazy to use the search feature or at least look at the stickies. But the information is out there already.
[GUIDES][Q&A]How-To Guides For Beginners + Q&A
CafeKampuchia said:
While this is true, it's because people are too lazy to use the search feature or at least look at the stickies. But the information is out there already.
[GUIDES][Q&A]How-To Guides For Beginners + Q&A
Click to expand...
Click to collapse
I've seen that thread, it's pretty useful bit I wouldn't say "the information is out there already. If you read the thread his instructions are just telling users how to wipe and flash roms.
The point of my thread was, or still is, to list all the different ways to flash roms. Clean, dirty, super clean. Most new users don't know the difference.
With that being said I am not saying anything negative about the guide nor am I comparing the 2 guides. Think that I should add that, on the Internet things are usually misinterpreted.
I am simply making a bit know detailed and specify guide just for flashing roms.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Amazing as usual! You're a treasure, my friend! So happy to see you back on xda!
Plus... do you really want me to tell you how we "dirty flashers" flash roms? love you man, you're perfect!
NOTE- This is a MUST when changing roms.
1. Backup EFS -Not necessary every time you flash a ROM.
2. Make a nandroid backup in recovery -Not necessary every time you flash a ROM.
3. Wipe data/factory reset
4. Wipe system
5. Wipe cache
6. Wipe dalvik
7. Flash ROM
8. Flash gapps
9. Flash AK kernel(optional) -There are many kernels available for our device, not just AK.
10. Reboot
11. Wait 10 mins, then do another reboot -Not necessary.
12. Enjoy
Transmitted via Bacon
daxgirl said:
Amazing as usual! You're a treasure, my friend! So happy to see you back on xda!
Plus... do you really want me to tell you how we "dirty flashers" flash roms? love you man, you're perfect!
Click to expand...
Click to collapse
Haha no comments... ?
timmaaa said:
NOTE- This is a MUST when changing roms.
1. Backup EFS -Not necessary every time you flash a ROM.
2. Make a nandroid backup in recovery -Not necessary every time you flash a ROM.
3. Wipe data/factory reset
4. Wipe system
5. Wipe cache
6. Wipe dalvik
7. Flash ROM
8. Flash gapps
9. Flash AK kernel(optional) -There are many kernels available for our device, not just AK.
10. Reboot
11. Wait 10 mins, then do another reboot -Not necessary.
12. Enjoy
Transmitted via Bacon
Click to expand...
Click to collapse
Did you read the first few sentence of the OP? Like I said it's a WIP and I need to edit stuff.
But after seeing your edits, the only thing I agree I need to edit out is doing an EFS backup every time you flash a rom. Nandroid is a must IMO, you never know when you'll be unlucky.
As for the "there are many kernels avaliable".. It says optional next to it for a reason.
And about waiting 10 after a rom/kernel and rebooting not being necessary, from my experience it helps let the rom/kernel settle. There was a time when devs used to recommend that. I still do that and recommend it.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Khizar said:
Haha no comments... ?
Did you read the first few sentence of the OP? Like I said it's a WIP and I need to edit stuff.
But after seeing your edits, the only thing I agree I need to edit out is doing an EFS backup every time you flash a rom. Nandroid is a must IMO, you never know when you'll be unlucky.
As for the "there are many men kernels avaliable".. It says optional next to it for a reason.
And about waiting 10 after a rom/kernel and rebooting not being necessary, from my experience it helps let the rom/kernel settle. There was a time when devs used to recommend that. I still do that and recommend.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Click to expand...
Click to collapse
Yeah I did read it and that's why I was putting forth my constructive criticism. The nandroid isn't an absolute must every time you flash though, if you have at least one nandroid on your phone at all times you have insurance against the unknown, whether or not you do that with every flash is purely optional (as opposed to describing it as essential, because it just isn't).
There's a reason devs don't recommend to reboot a second time after a ROM flash anymore, because it isn't essential either.
I only mentioned the kernel because it might seen as favouritism, and it's always best to remain objective in a guide thread.
I'm detecting animosity in your reply. Don't get me wrong, I'm all for having resources, I'm about to add your thread to my index thread so folks can find it easier. I'm just pointing out things that aren't actually essential every time a ROM is flashed, trying to save the user unnecessary time and effort.
Transmitted via Bacon
---------- Post added at 07:45 PM ---------- Previous post was at 07:38 PM ----------
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
timmaaa said:
Yeah I did read it and that's why I was putting forth my constructive criticism. The nandroid isn't an absolute must every time you flash though, if you have at least one nandroid on your phone at all times you have insurance against the unknown, whether or not you do that with every flash is purely optional (as opposed to describing it as essential, because it just isn't).
OK. I agree with this, I'll change it to optional and have a bold warning that you should have atleast one nandroid just in case at all times.
There's a reason devs don't recommend to reboot a second time after a ROM flash anymore, because it isn't essential either.
OK this one I am kinda biased about, have had the same discussion with many others. I've always experienced that if I use a rom/kernel right after I flash everything is a bit laggy. If I wait 10 mins and reboot, everything is a lot smoother.
I only mentioned the kernel because it might seen as favouritism, and it's always best to remain objective in a guide thread.
Hmm.. You do have a point, I'll edit that bit.
I'm detecting animosity in your reply. Don't get me wrong, I'm all for having resources, I'm about to add your thread to my index thread so folks can find it easier. I'm just pointing out things that aren't actually essential every time a ROM is flashed, trying to save the user unnecessary time and effort.
Feedback is always welcome. I appreciate you taking the time and commenting here.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks for adding the thread to the index. :good:
Khizar said:
Thanks for adding the thread to the index. :good:
Click to expand...
Click to collapse
No worries mate. All good, and well done on the thread!
Transmitted via Bacon
Khizar said:
Yeah let's hope ppl actually read and my time editing see stuff to make it for OPO isn't wasted.. These forums seem to be worse than the note 3 ones.. Man saw this guy today who apparently couldn't find the link to gapps that was posted in the OP.. SMH
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Click to expand...
Click to collapse
CafeKampuchia said:
While this is true, it's because people are too lazy to use the search feature or at least look at the stickies. But the information is out there already.
[GUIDES][Q&A]How-To Guides For Beginners + Q&A
Click to expand...
Click to collapse
Nice job and I agree it was getting a little crazy in here as well with the how do I flash this rom crap. I thought this was self explanatory but it seems to be a lot of first timers in here.
I know you said your instructions are a WIP but simply remember when you are ready to put out the finished product you must think as they do the super duper noobs and try and make it as flashing for dummies as possible. They will hold on to your every letter.
I agree that a recent nandroid is needed and honestly I keep 2 at least on my phone because I have been burnt with a corrupted backup before. Also who wants to restore a rom from 2 months ago.... :good:
Nice work
If I may I would like to make some suggestions ??? may I? And no... not as a dirty flasher... if is OK with you, I will...
playya said:
Nice job and I agree it was getting a little crazy in here as well with the how do I flash this rom crap. I thought this was self explanatory but it seems to be a lot of first timers in here.
I know you said your instructions are a WIP but simply remember when you are ready to put out the finished product you must think as they do the super duper noobs and try and make it as flashing for dummies as possible. They will hold on to your every letter.
I agree that a recent nandroid is needed and honestly I keep 2 at least on my phone because I have been burnt with a corrupted backup before. Also who wants to restore a rom from 2 months ago.... :good:
Nice work
Click to expand...
Click to collapse
Yes I think I'll try to make it simpler and more easier for new users to understand, a dummy proof version as you said. Thanks for your feedback.
daxgirl said:
If I may I would like to make some suggestions ??? may I? And no... not as a dirty flasher... if is OK with you, I will...
Click to expand...
Click to collapse
Since when have you needed to ask for permission Anna..? Anyways all suggestions are welcome.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Khizar said:
Yes I think I'll try to make it simpler and more easier for new users to understand, a dummy proof version as you said. Thanks for your feedback.
Since when have you needed to ask for permission Anna..? Anyways all suggestions are welcome.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Click to expand...
Click to collapse
Well we already know that I am a polite non xda material
Sooooooo here we go...
1. When you wipe data in any recovery, it includes AT LEAST 3 things: a. Format data partition b. Eliminate dalvik exec files along with that (since dalvik cache sits on data partition) c. Format cache
So after wiping data, there is not reason to wipe cache and dalvik cache, since they have already been cleaned as a whistle.
2. During rom installation, new framework jars are being pushed over /system/framework. It's enough for just android.policy.jar to be replaced, the android will rebuild all dalvik upon boot (hence the "Android is upgrading. Optimizing xx app out of xxx"). All the major jars upon replacement will wipe dalvik and rebuild it. It's enough to have 1 byte of difference.
So I guess that summorizes the need for wiping dalvik cache.
3. As for wiping system. Well things are a bit more controversial here. Since any normal rom updater script has as first command "mount /system" and as second command "delete recursive /system", it seems like there is no need as well. BUT!!!
There seems to be a discussion whether formatting system (which is done when it's unmounted) the way recovery does it in "mounts and storage " is more "thorough and effective" then recursively deleting it (when it's mounted) by the updater script.
So I can see the point in formatting system! Well, a little...
Hey, don't get me wrong, I admire this guide and I think it's super helpful! I just always feel the need to set things straight with this "triple wipe" that everyone keeps recommending.
Imo, wipe data is simply enough that is IF you're not a dirty flasher. ..
Now to the last part! You guys all have pretty uh the same sqlite vs in all those aosp/cm/aokp roms.
All I am saying: sometimes you can try to flash without wipe, if there is a problem, which in most cases there won't be, some individual data/data databases can be deleted and rebuilt. Maybe we should write a guide on dirty flashing I am certainly good at THAT
daxgirl said:
Well we already know that I am a polite non xda material
Sooooooo here we go...
1. When you wipe data in any recovery, it includes AT LEAST 3 things: a. Format data partition b. Eliminate dalvik exec files along with that (since dalvik cache sits on data partition) c. Format cache
So after wiping data, there is not reason to wipe cache and dalvik cache, since they have already been cleaned as a whistle.
2. During rom installation, new framework jars are being pushed over /system/framework. It's enough for just android.policy.jar to be replaced, the android will rebuild all dalvik upon boot (hence the "Android is upgrading. Optimizing xx app out of xxx"). All the major jars upon replacement will wipe dalvik and rebuild it. It's enough to have 1 byte of difference.
So I guess that summorizes the need for wiping dalvik cache.
3. As for wiping system. Well things are a bit more controversial here. Since any normal rom updater script has as first command "mount /system" and as second command "delete recursive /system", it seems like there is no need as well. BUT!!!
There seems to be a discussion whether formatting system (which is done when it's unmounted) the way recovery does it in "mounts and storage " is more "thorough and effective" then recursively deleting it (when it's mounted) by the updater script.
So I can see the point in formatting system! Well, a little...
Hey, don't get me wrong, I admire this guide and I think it's super helpful! I just always feel the need to set things straight with this "triple wipe" that everyone keeps recommending.
Imo, wipe data is simply enough that is IF you're not a dirty flasher. ..
Now to the last part! You guys all have pretty uh the same sqlite vs in all those aosp/cm/aokp roms.
All I am saying: sometimes you can try to flash without wipe, if there is a problem, which in most cases there won't be, some individual data/data databases can be deleted and rebuilt. Maybe we should write a guide on dirty flashing I am certainly good at THAT
Click to expand...
Click to collapse
1. I get what you're saying with the wiping being a little excessive, again this comes down to experience. My guide is made from what I have personally experienced.
Factory reset does wipe cache and dalvik but I am a believer in "better safe than sorry". Same thing with wiping system even though, like you said, most updater scripts wipe system. Also the bigger reason WHY I am firm in saying atleast wipe data and system is cuz I have noticed in sometimes that when I wipe system as opposed to only wiping data, the experience is better so I have come to the conclusion that the recoveries manual wiping options are to be trusted more.
2. You're right about the dirty flashing, you'll be happy to hear I've been flashing dirty since I got the phone. Now dirty flashing different roms is a bit tricky but I have had success, however even if it gets messy I always have a backup.
Sent From My One A0001 With AK Awesomeness To All You Wonder Nobodies!!
Khizar said:
9. Wait 10 mins, then do another reboot
Click to expand...
Click to collapse
I can not understand this step? After the first reboot the new OS booted UP, you must set in and installing the Google APPS update if it available. After the first bootup, why should the users rebooting the device?
Criton30 said:
I can not understand this step? After the first reboot the new OS booted UP, you must set in and installing the Google APPS update if it available. After the first bootup, why should the users rebooting the device?
Click to expand...
Click to collapse
After the first boot up, Java has to create it's working areas for the OS to function well, and it configures the kernel and miscellaneous trash handling (if dirty flashed). Rebooting will clear the supposedly terminates "completed services" after they were used to configure Android on first boot, hence things like kernel will be set on next boot, and on the next boot, you will have a clean Daily Driver configuration.
Also, it's like "why do you reboot your computer after a new install of a big program?", well, for it to settle, and to reinitiate the program. In this case, Android was setting up all your working directories on your internal storage, clearing out junk it may have had, and also rebuilding of the VM. That's a lot of work. Why not reboot to make sure everything that has been sitting on idle after making all these folders, would be terminated completely so just to make sure everything goes right.
nicholaschum said:
After the first boot up, Java has to create it's working areas for the OS to function well, and it configures the kernel and miscellaneous trash handling (if dirty flashed). Rebooting will clear the supposedly terminates "completed services" after they were used to configure Android on first boot, hence things like kernel will be set on next boot, and on the next boot, you will have a clean Daily Driver configuration.
Also, it's like "why do you reboot your computer after a new install of a big program?", well, for it to settle, and to reinitiate the program. In this case, Android was setting up all your working directories on your internal storage, clearing out junk it may have had, and also rebuilding of the VM. That's a lot of work. Why not reboot to make sure everything that has been sitting on idle after making all these folders, would be terminated completely so just to make sure everything goes right.
Click to expand...
Click to collapse
so if I understand you correctyl, after the first bootup after the OS installation I must reboot the phone before setting up the google account and soo on?