Hi - first time trying to root. I successfully rooted, installed Entropy's Kernel, and I thought successfully installed TurkbeyRom (I don't think this is a question specific to this rom, so I"m posting here...).
After booting back up, I get this message: " The process com.android.phone has stopped unexpectedly". This takes out my wireless signal, and keeps popping up with the error even when clear that screen out.
I realized that I didn't do any sort of data wipe before installing this rom...could that be the issue? I was under the impression that when installing them, it asked if you would like to wipe data, and it didn't.
My question is - if I wipe the data now, how much will I lose? Obviously I don't care about apps/contacts/etc..I'm wondering how far it'll set me back in the rooting process. Meaning if I wipe, will it completely wipe out my kernel...etc.
Thanks!
Boot into cwm and wipe data factory reset...then see if it fixes the issue. It wont go backwards in the root process
Sent from my SGH-I777 using xda premium
Please read before posting. Check the FAQ question [21].
- ROM install doesn't ask you to wipe, you have to do it yourself. (FAQ [21] has steps how to do it in CWM. For that, it is assumed that you followed this guide all the way through.
- any type of wipe will NOT remove your kernel. Wiping will remove stuff like your apps/contacts/etc
Wipe data/factory reset will remove any user installed applications and personal settings that have been set since the flash. It will not make any changes to the kernel or system partition, so the rom will be just like if you wiped first and then flashed the rom. That should solve any issues, but if there are still problems after the wipe, then try flashing the rom again.
Most roms here don't do an automatic wipe, afaik. You must do the wipe first, usually from ClockworkMod Recovery. It is always recommended to wipe when changing from one rom to another, from stock to any rom, etc. You can usually get by without a wipe when doing a minor upgrade of the same rom, assuming there is not change of base within the rom.
Thanks guys. It works perfectly now after wiping.
Sorry about not seeing that in the FAQs. I did look there, but I must have had a different "question" in mind than "[21] Install Custom ROM from CWM" and glanced past that one.
Related
When I perform a Wipe / data factory reset from CW on boot mode if I boot into the OS directly after that it boots into a very old version of CM7. I have been running aokp for a while now and have went through may different builds over time.
Here is my concern. When I do a wipe if CW is installing some old ROM is this a valid wipe, or am I putting config files on that could be messing with the next ROM installation. I guess I would expect to see something close to a stock rom. If my thoughts here are correct how would I fix CW to install the right ROM on wipe?
This is on a Samsung Galaxy Tab 10.1 (7500) (code name p4).
I don't consider myself a newb with this stuff, this one just baffles me and when try to google it I just get tons of basic rooting information.
PS: I am hoping I posted to the correct location (I took a guess on that).
I don't know exactly what caused the issue. Maybe some recent apps since that was all that I had installed. I was running the latest AOKP ICS 4-28-12 and Siyah 3.1x. I forget the exact kernal number but it wasn't the version that I read about phone bricking (R6?).
So I wake up this morning and unlock my screen and there are popups for everything force closing. Not just foreground running apps but everything including background running apps. Every time an app autorestarts in the background the force close error msg pops up again. It was running fine just 6 hours prior since I was using it before bed.
Reboot. Same issue. CMW Recovery. Wipe cache/dalvik. Reflash AOKP and GApps. Reboot. Same force closing issue. WTF. Attach USB to comp and try to move a different ROM to my Internal SD but no dice. Comp isnt recognizing phone now. [email protected]#K! Reboot into download mode. All the ROMS I downloaded are ZIP format instead of TAR format. So this time my dumb self uses Odin to reflash the TAR file I used to root my phone. After this I realize "that TAR doesn't have a ROM attached to it."
So now I can only boot into download mode. Can't load CMW. Sadly I had to leave for work and I'm without my phone until I get home at midnight. I FEEL SO DISCONNECTED! ='(
Will a simple file conversion program be sufficient to convert ZIP to TAR so I can use ODIN to flash them later? Or will I have to follow the unbrick instructions to return to stock and then start over? And after reading about that one version of Siyah bricking phones I think I'm going to leave the NEAK kernal that comes with AOKP.
Thanks for your assistance!
No, you can't build a tar from a zip.
I don't and have never used aokp or cm9 or miui, but in my experience, when you start getting massive force closes, and if a fix permissions in recovery doesn't fix it, then you're best off starting over from scratch. If you have a working nandroid backup, use that. Otherwise, flash back to stock, wipe data/factory reset, and reinstall your rom from scratch.
There are plenty of tar and one-click downloaders available. See links in my signature.
I found this on the i9100 forums, instructive. Instead of installing a stock samsung firmware and kernel, just download a rooted package (maybe go back to Gingerbread for i777) then go from there.
http://forum.xda-developers.com/showthread.php?t=1457458
I'm interested to know how this recovery works for you, keep us posted! Best luck!
Any idea what would randomly cause the issue of mass force closures so I can prevent this from occuring again?
Did you do a Full Wipe when you first installed AOKP? I have ran into issues before with Rom Control by just wiping cache and dalvik and under the OP of AOKP Task even states coming from aokp or cm9 you Should be good but more likely than not, I would do a complete wipe *Factory Reset under CWM*. And when you restore your data with TiBu just restore missing apps and their data. Do not restore system data as that will be a major cause of mass FC... So first things first, I would use Odin to go back to UCKH7 *hopefully with CWM and Root* and than go back to Aokp since in my opinion is the best rom for our phones now.
HTH,
Charlie
dmnall said:
Did you do a Full Wipe when you first installed AOKP? I have ran into issues before with Rom Control by just wiping cache and dalvik and under the OP of AOKP Task even states coming from aokp or cm9 you Should be good but more likely than not, I would do a complete wipe *Factory Reset under CWM*. And when you restore your data with TiBu just restore missing apps and their data. Do not restore system data as that will be a major cause of mass FC... So first things first, I would use Odin to go back to UCKH7 *hopefully with CWM and Root* and than go back to Aokp since in my opinion is the best rom for our phones now.
HTH,
Charlie
Click to expand...
Click to collapse
I didn't do a factory wipe. I'm thinking I'll just do a factory wipe for any new rom installs. It's a little more work but if it helps prevent this sort of error I'll do it. And after reading about the bricking with that one version of Siyah I'm going to wait a couple weeks before any new installs to make sure other people have tested it first.
creepyncrawly said:
No, you can't build a tar from a zip.
I don't and have never used aokp or cm9 or miui, but in my experience, when you start getting massive force closes, and if a fix permissions in recovery doesn't fix it, then you're best off starting over from scratch. If you have a working nandroid backup, use that. Otherwise, flash back to stock, wipe data/factory reset, and reinstall your rom from scratch.
There are plenty of tar and one-click downloaders available. See links in my signature.
Click to expand...
Click to collapse
Well the first attempt didnt work using kernel + rooted UCKH7. Odin did everything it was supposed to but the phone locks at the initial Galaxy S II I-9100 ! screen. =(
Second attempt using I777_UCKH7_OCD_Root_No_BL and I'm able to get past the Galaxy S II I-9100 screen and the original AT&T boot animation shows but after the boot animation it just continuously reboots. ='(
Third attempt I tried Kernel + cache + rooted UCKK6 and after the reboot it actually rebooted into recovery mode. I thought that was a good sign so I reboot the phone normally and same issue as above. I try to reboot into recovery mode (Vol + - and pwr) again but it doesn't come up now. ='(
Forth attempt I tried Kernel + cache + rooted UCKK6 again. It reboots into recovery mode and I select the Factory Wipe option and reboot. There's a long delay after the AT&T boot animation and finally my phone starts up as if it was stock.
What a freakin nightmare! I was so worried my phone was a goner. None of the other ROMs I tried gave the option of booting into recovery mode which would have saved me so much time. Only the stock one did. The factory wipe was the key. So I'm definitely saving that file for safe keeping.
Thank you all for your suggestions and assistance. It's much appreciated.
This entire thread could have been avoided. By wiping completely. What is a complete wipe? Well, its the /system , /cache, /data, and /dalvik partition. Each of which are easily wiped in cwm in under 30 seconds. Flashing the kernel cleaning script doesn't hurt. Keep in mind these are your phones people it wouldn't hurt to do some research.
Sent from my SGH-I777 using Tapatalk 2
Installed king kang rom on my i717 4.0.4 from the development page and got a boot loop. wtf I'm so sick of boot loops. luckily i made a backup, restoring now.
This happen to anyone else? how can one fix that?
Boot loops are of course common. but can generally be blamed on the device not being clean when flashing a new build.
Wiping the old data is critical before flashing new roms.
Wipe cache
Dalvik cache
Data
System
Kernels, and other images being flashed to the device before or after the ROM can also give you problems.
Review the OP in the ROM thread carefully that you intend to flash, as it often contains information that will prevent such an occurence.
1000's of users are running this ROM without any boot loops, so it must be a dirty device, or the wrong data being left, or placed during the flash.
And always verify the MD5 sum of the build with your downloaded copy, to verify a good file has been copied......g
gregsarg said:
Boot loops are of course common. but can generally be blamed on the device not being clean when flashing a new build.
Wiping the old data is critical before flashing new roms.
Wipe cache
Dalvik cache
Data
System
Kernels, and other images being flashed to the device before or after the ROM can also give you problems.
Review the OP in the ROM thread carefully that you intend to flash, as it often contains information that will prevent such an occurence.
1000's of users are running this ROM without any boot loops, so it must be a dirty device, or the wrong data being left, or placed during the flash.
And always verify the MD5 sum of the build with your downloaded copy, to verify a good file has been copied......g
Click to expand...
Click to collapse
Hmmm okay i'll try the MD5 thing. Though I get the links for the downloads right off the developer's threads and they don't always have it.
All That wiping is redundant... if you look at the log in recovery you'll see Wiping data as in a factory reset also wipes /cache
And dalvik is on the data partition so it's also wiped.
And any dev who's Rom is worthy of flashing will have the script format /system.
All I do is wipe data/factory rest(same option on recovery not separate choices) then flash Rom.
I'd lean more toward corrupted download over anything else, improperly wiping would more likely cause instability in a Rom than cause it to bootloop completely, from my experience anyhow.
Whereas corruption in the Rom zip could easily do it... just one .apk or .jar in the the /system/framework folder for example.
If no md5 is available, go ahead and download the Rom again fresh.
And as Greg said.. if you're flashing anything after the Rom, consult the op for compatibility.
Or better yet, just flash the Rom and let it settle... then once you see its working correctly and only then, flash anything else.
thanks for the tips...i reset and reinstalled and its working great now! had a few bugs but fixed them by searching the forums here. this rom is friggin powerful. im gonna finish setting it up and make a nandroid backup!
Yeah I realize this is probably a noob question, but I'm proud (kinda anyway) to admit I am one.
Before jumping head first into flashing a different ROM (currently rooted w/ CWM & ViperXL) I want to make sure I don't end up with a paperweight or at least hours of unexpected work. My reason is just because I want to check out what other Roms have to offer. So its more than possible I may end up back on Viper at some point. Having read some semi-related threads it sounds like this is as simple backing up (nandroid, apps, system data) then flashing from recovery followed with a restore of apps and sys data.
Is there anything I'm missing? Do you need to do a cache and Dalvik wipe? Do I need to load a new boot.img, kernel or anything else? Am I thinking too much and making it seem harder than it really is?
Sent from my HTC EVARE_UL using xda app-developers app
It's pretty simple, just back everything up, wipe system, data, and the cache + dalvik-cache. Then install the ROM, and flash the kernel. Then, you can restore data if you want.
Sent from my One X+ using xda premium
Just to be clear in CWM its the following wipes ONLY!
Main screen
- wipe data/factory reset
- wipe cache partition
Advanced menu >
- wipe dalvik cache
remember (and please someone correct me if I'm wrong) flash the kernel first then jump to recovery.
Oh and ALWAYS have a rom.zip on your phone even if you dont require it, that way you could always reflash your way out of trouble should you forget to put that new rom on to try
I recently made a backup of every partition with TWRP and forgot to remove screenlock beforehand. So I restored the full backup after messing with custom roms, everything worked perfectly and everything was restored, until I couldnt set a password... I can go to the settings to set up a password but after confirming it, it closes and I have to do it again. Not even custom roms with formatted data can set a password... What can I do?
(The video has black parts which is just the recording hiding me setting up a password)
I've been there... Twice. The only thing that helped was a factory reset by (a) OnePlus (servicepoint).
NOTE: if they reflash stock rom, they should afterwards REBOOT TO STOCK RECOVERY, WHIPE EVERYTHING and reflash the rom once more.
If you ignore this step and a second flash, the question is not IF you will gey problems, but when.
exis_tenz said:
I've been there... Twice. The only thing that helped was a factory reset by (a) OnePlus (servicepoint).
NOTE: if they reflash stock rom, they should afterwards REBOOT TO STOCK RECOVERY, WHIPE EVERYTHING and reflash the rom once more.
If you ignore this step and a second flash, the question is not IF you will gey problems, but when.
Click to expand...
Click to collapse
So, if I bring it to a oneplus service point and they fix it, I should format data and flash stock rom again after? Where do I find the stock rom to flash?
No! They should re-flash stock (that's what they'll do anyway). But YOU need to tell them, to (after the flash) reboot to stock recovery, wipe all, and then re-re-flash the stock rom.
If they don't do that, they'll see you again, soon.
For some reason I don't know, one flash keeps residu of former 'playing around'. Your service point will probably NOT know this.