Ok, so I have rooted my x10 mini pro, and installed CWM recovery. I now have a ROM that I have decided on, but would like some clarification on something. According to install instructions, I just need to factory reset full wipe. However some devs tell you to also do a dalvik cache wipe and/or a cache partition wipe as well. Is it a rule of thumb that all 3 are done, or do you just settle for a factory reset full wipe, as per the dev's instructions? I really don't want to make a mess of my first attempt and get stuck in a boot loop or something even more disastrous. I currently have 2.1 stock, that I will be upgrading from. Thanks for any help.
cleggs said:
Ok, so I have rooted my x10 mini pro, and installed CWM recovery. I now have a ROM that I have decided on, but would like some clarification on something. According to install instructions, I just need to factory reset full wipe. However some devs tell you to also do a dalvik cache wipe and/or a cache partition wipe as well. Is it a rule of thumb that all 3 are done, or do you just settle for a factory reset full wipe, as per the dev's instructions? I really don't want to make a mess of my first attempt and get stuck in a boot loop or something even more disastrous. I currently have 2.1 stock, that I will be upgrading from. Thanks for any help.
Click to expand...
Click to collapse
I would make the three wipes to avoid any issue, but the most important is to make the backup from CWM before wiping anything.
KuSkUS_68 said:
I would make the three wipes to avoid any issue, but the most important is to make the backup from CWM before wiping anything.
Click to expand...
Click to collapse
Thank you for the reply. Yes, I'm aware about backing up my data. I probably will make 3 wipes, just to cover myself. I am a little concerned about things going badly, and not being able to start CWM to revert back to stock, if things don't turn out well, but that's just my nature to worry about such matters. lol. I will make a backup and then do the 3 wipes discussed, and then flash the new ROM. I will keep everything crossed, just in case. Thank you for taking the time to reply, much appreciated.
Don't worry too much
Got a x10 mini pro myself which I messed up real bad, a little tweaking here and some tweaking there and I got it running again. As long as you don't mess up the hardware, which is relatively not likely, you shouldn't having too much problems restoring it to working state
Well, that was very painless really. I did a factory reset, cache partition and dalvik cache wipes before and after applying the new Rom, and everything went very smoothly. Expecting a long first boot, as seems to be normal for this process, it booted so quickly, I thought I must have done something wrong lol. See! There's nothing to worry about after all....I told you so.
cleggs said:
Well, that was very painless really. I did a factory reset, cache partition and dalvik cache wipes before and after applying the new Rom, and everything went very smoothly. Expecting a long first boot, as seems to be normal for this process, it booted so quickly, I thought I must have done something wrong lol. See! There's nothing to worry about after all....I told you so.
Click to expand...
Click to collapse
Glad to know. You were absolutely right....
BTW which ROM have you tried?
KuSkUS_68 said:
Glad to know. You were absolutely right....
BTW which ROM have you tried?
Click to expand...
Click to collapse
I went for this one http://forum.xda-developers.com/showthread.php?t=1151499 I'm still playing around with it, but it seems very stable. Very nice work by paul-xxx
cleggs said:
I went for this one http://forum.xda-developers.com/showthread.php?t=1151499 I'm still playing around with it, but it seems very stable. Very nice work by paul-xxx
Click to expand...
Click to collapse
Mmmm... I installed the other ROM made by paul-xxx, MiniCM7Pro http://forum.xda-developers.com/showthread.php?t=1201116
It also works fine for me (although latest releases are showing some bugs), but I like that "Sony style". Probably I'll give it a try
KuSkUS_68 said:
Mmmm... I installed the other ROM made by paul-xxx, MiniCM7Pro http://forum.xda-developers.com/showthread.php?t=1201116
It also works fine for me (although latest releases are showing some bugs), but I like that "Sony style". Probably I'll give it a try
Click to expand...
Click to collapse
Only annoying thing I have found so far, is my virtual keyboard. When hitting the backspace or space keys, sometimes it's unresponsive which can be a little irritable. This is using the touchpal keyboard, but I did notice similar on the stock keyboard too. But everything else is very stable. Wifi works no problems at all, as does bluetooth (well, it starts up on demand, but I haven't actually used it yet lol) Notifications for new sms works well too (this can sometimes be temperamental on some phones) I've yet to test GPS but I know it starts well enough. And I've yet to have any FC's. It would be interesting to hear your comparison of the two versions, if you do decide to give it a try.
EDIT: oh, and radio works well too lol :-D
I remember my first ROM install... d*mn it went as wrong as anything could. Somehow i managed to install a ROM for the X10 on my X10 mini pro.
It froze at the bootanimation.
PC Companion fixed it.
Since then I have bricked my phone many times, experimenting with custom kernals and home-modding, PC Companion never failed me
[TUT] un-brick for n00bs
Emperor.dk said:
I remember my first ROM install... d*mn it went as wrong as anything could. Somehow i managed to install a ROM for the X10 on my X10 mini pro.
It froze at the bootanimation.
PC Companion fixed it.
Since then I have bricked my phone many times, experimenting with custom kernals and home-modding, PC Companion never failed me
[TUT] un-brick for n00bs
Click to expand...
Click to collapse
I must have had beginners luck.
I do like your tutorials, always concise and the screen shots are always very helpful for noobs like myself. Thank you Emperor.dk
Related
OK i have to say i m not a noob anymore. And i m pretty confident.
Having said I am coming from Vegan 5.1 and tried many times to download the new Vegan Ginger. But each time I got stuck at the "birds" screen.
And yea I do all the same steps for when i was ROMing to Vegan 5.1
So my questions are: why isn't it working this time?
Do i have to be on Stock Rom for it to work?
Any suggestion?
Thank you
Its always a good idea to start from stock and then going to custom rom. I suggest you use nvFlash to go back to stock, then flash cwm .8 and then try to follow your steps to install it.
enjoy
Best way to flash a new rom is to fully wipe data cache dalvik ect ect do that in cwm then install zip from disk. Works every time and usely it take like ten minites to fully install. If you need help just look around or ask.
Good luck
Awessssoooommmee
You guys are awesome
I just Nvflash and Install the ginger edition easily
Thank youuuuu
I'm having the exact same problem. Even fully wipe data, cache and davik does not help.
I noticed that, when ClockworkMod Recovery showed that it was installing update, the progress bar stayed grey, not changing or moving at all.
Guess I'll have to try nvflash.
Yeah do that
ww9rivers said:
I'm having the exact same problem. Even fully wipe data, cache and davik does not help.
I noticed that, when ClockworkMod Recovery showed that it was installing update, the progress bar stayed grey, not changing or moving at all.
Guess I'll have to try nvflash.
Click to expand...
Click to collapse
Yea do that, cause it looks like this ONLY works on stock rom. And after that just do your usual process, and you should be good.
Everything went so well that my first boot took less than a minute
I have been messing with my GS2 and tried out the BETA ICS roms. They are nice but too many reboots. I have flashed 2.3.6 back to my GS2 but when the phone starts up, I just get loads of errors like "The application Google Services Framework (process com.google.process.gapps) has stopped unexpectedly.
When I force close, I get other error messages for other services. I cannot get any further than where it says touch the green android to begin.
I have flashed a few times but always the same. Is there anything I can do to get past this?
Are you restoring a nandroid backup or is it a fresh install?
If you are flashing a fresh install, try wiping everything, Wipe Data, Cache, Dalvick, format system?
Hi, thanks for quick reply.
It would be a fresh install. How do I wipe/format? Can u point me to a link, I have never done it before. I am using Odin.
gareth824 said:
Hi, thanks for quick reply.
It would be a fresh install. How do I wipe/format? Can u point me to a link, I have never done it before. I am using Odin.
Click to expand...
Click to collapse
Turn off phone
Press Home+Power+Vol up button u will boot into inbuild recovery
Wipe Data
Thanks.
I'm back on and back to Gingerbread. Think I'll stop tinkering and do more reading first.
Thanks for your help guys.
gareth824 said:
Thanks.
I'm back on and back to Gingerbread. Think I'll stop tinkering and do more reading first.
Thanks for your help guys.
Click to expand...
Click to collapse
From next time when ever u downgrade wipe data like this and then downgrade
And post questions in Q/A section
Not being funny but if you didnt know how to wipe when you loaded ICS then you didnt install ICS properly, and therefore that will be the reason why your having all the reboots.
Ive had ICS installed for over 2 weeks now and not had 1 reboot.
Id suggest giving ICS another go, but make sure you do full set of wipes before installing
Ah, I followed the instructions on here and don't remember it showing that. I might give it another go now I know how to do it. It was very slick but mine was crashing ever few minutes.
KP8 ICS ROM is unstable with or without wipe, especially watching video through browser. I had reboots and various crashes. Not worth it right now.
If you are going to use ICS you have to flash the ICS bootloaders, then make sure you reflash the GB bootloaders when you move back, when you find out its basically an unstable alpha with none of the mods we are used to with GB.
Greetings
As the tittle points outs, I flashed the latest Androwook Rom(2.1) and it always stucks at the Intro Crawl. I re-downloaded it, flashed it again, but had had no success.
The Prime has been unlocked since May, and it was running the Cyanogen Nightly Rom, before I tried the Wook one. I wiped Cache and Delvik, and tried an older build as well with no success. I use the latest TWRP, 2.1.3. I also tried all availlable kernels and options during the installation with no success.
Can anyone give me a hint as to what is the problem? I can always go back to CM Rom, but I would feel like I accepted defeat.
Also, why does the installation always wipe my internal sd card , when no such option is selected?
drsane1984 said:
Greetings
As the tittle points outs, I flashed the latest Androwook Rom(2.1) and it always stucks at the Intro Crawl. I re-downloaded it, flashed it again, but had had no success.
The Prime has been unlocked since May, and it was running the Cyanogen Nightly Rom, before I tried the Wook one. I wiped Cache and Delvik, and tried an older build as well with no success. I use the latest TWRP, 2.1.3. I also tried all availlable kernels and options during the installation with no success.
Can anyone give me a hint as to what is the problem? I can always go back to CM Rom, but I would feel like I accepted defeat.
Also, why does the installation always wipe my internal sd card , when no such option is selected?
Click to expand...
Click to collapse
jumping from one rom to another needs a full wipe i guess... when you said wiping your internal sd card, that's the reason why you're stuck into crawling? so i guess you use adb to push the ROM, then flash again?
in my case, when i had a bootlop, i push fullwipe.zip first, flash it, then push Androwook.zip, then flash it... it all came back alive..
First of all, thank you for your reply!
Now, to adress each step
jumping from one rom to another needs a full wipe i guess.
Click to expand...
Click to collapse
Yup, did one (factory reset+system wipe) before trying to flash AW Rom.
when you said wiping your internal sd card, that's the reason why you're stuck into crawling? so i guess you use adb to push the ROM, then flash again?
Click to expand...
Click to collapse
After the first three unsuccessfull attempt to flash the ROM did I wipe my internal SD, so it isn't the crawling looping intro's problem. And yes, I push ROMs via Adb, and trying flashing.
in my case, when i had a bootlop, i push fullwipe.zip first, flash it, then push Androwook.zip, then flash it... it all came back alive..
Click to expand...
Click to collapse
That was actually the last step I tried before asking for help. Even after I typed this post, I did it again. Flashed it, pushed AW, and flashed again. No success.
*Edit: I have forgotten a primary Troubleshooting technique. Downloading AW2.1 from a different source, will update.
sorry but im not much of a help i can see... hope somebody could. don't lose hope though...
Intentions matter
Thanks for your time anyway!
After two more failed flashes, I got it to boot!
Apparently the starting animation was causing some kind of problem, which I cannot ever imagine. After I checked the option to have the uggly original boot animation, the rom booted normally and I am now using it.
I am quite happy to get it to work, but if anyone has any solution to the boot problem, I would be really glad to hear him!
drsane1984 said:
Intentions matter
Thanks for your time anyway!
After two more failed flashes, I got it to boot!
Apparently the starting animation was causing some kind of problem, which I cannot ever imagine. After I checked the option to have the uggly original boot animation, the rom booted normally and I am now using it.
I am quite happy to get it to work, but if anyone has any solution to the boot problem, I would be really glad to hear him!
Click to expand...
Click to collapse
Hello Everybody! Guys, sorry for my english!!!!!
First of all, I have to present myself, my name is Marco, I'm italian, 25 years old and I'm in the Android world since about 12 Years.
I started whit a Galaxy S2, and after I bought an Asus Transformer Prime.
After just two week, I decided to put in a Custom ROM, on my devices, and I understood how the system work better instead of a Stock ROM!
And after, I understood, how the XDA Developers Forum is important for me, and expecially for all the people who like to learn about the Android World.
So, I just want to Thanks with all of you for the support that i receive EVERY DAY to solve my problems!
One of these was with flashing the Androwook, weeks ago I flashed the Team EOS 2.0, that was really amazing, but after a While, I found some slowdowns in some action on the system, so i decided to try a rom based on the stock rom, but with improvement and tweaks, so what's better then the Androwook?
The problem was, the same explained on this post, after all wipes, the prime was not boot, and stuck in bootanimation!
I solved, checking the box "Install custom ROM" as drsane1984 have done, and now the ROM is booted perfectly!!
Thanks another time! I'am convinced that if you are able to seach, you'll find for sure the solution to your problems! If not, just ask!
Bye!
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Thanks for the reply!
I didn't check the MD5 last night but I did just now and it matches.
I did a cache wipe the first time but not a system wipe. Then I started getting more desperate and tried reinstalling w/ system wipes and factory resets, but it didn't change anything.
No, I didn't change the ROM. Doing the Bootloader unlock exploit was about the absolute maximum of my technical abilities! The only thing I know I did wrong was that I didn't downgrade to the old boot version the first time (mainly because the wifi thing sounded inconsequential and I didn't want to learn the procedure if I didn't have to).
Anyway, I just tried Ultimate KangBang and it seems to work--no error messages so far. I don't know what I did wrong, but hopefully this keeps working!
IceDragon59 said:
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
Click to expand...
Click to collapse
andybones said:
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Click to expand...
Click to collapse
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
franklin411 said:
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
Click to expand...
Click to collapse
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
in the future it is always good practice to backup(nandroid) your current ROM. I have been burned too many times, always do a nandroid before you do anything in recovery.
your photos are normally saved to the SD, flashing ROMs or wiping the system will not delete them
andybones said:
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
Click to expand...
Click to collapse
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
franklin411 said:
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
Click to expand...
Click to collapse
na the name has nothing to do with it. it can be named whatever.
im guessing the wipe worked.
franklin411 said:
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Click to expand...
Click to collapse
weird, i was having the same problem with the same processes stopped working. i wiped cache dalvik and system but not factory reset. once i factory reset, it worked fine. i figured a system wipe would have been enough....
Hello everyone,
Well might as well say hi. I'm Ryukouki. I use this handle on a lot of forums, so if this is familiar you most likely know me elsewhere. So, anywho! I purchased a VZW Samsung Galaxy S4 two weeks ago, and I'm really curious. I rooted my phone, installed Clockwork Mod and backed up my data (I THINK) and I'm looking into ROMs for the Galaxy S4. What is the best mod for speed and performance, with good ease of use, and does not require a data wipe on installation? And is there a tutorial to go about doing this? I'm kind of new to the whole smartphone thing (used a feature phone for seven years!!), but I'm not too afraid to try new things out.
Ryukouki said:
Hello everyone,
Well might as well say hi. I'm Ryukouki. I use this handle on a lot of forums, so if this is familiar you most likely know me elsewhere. So, anywho! I purchased a VZW Samsung Galaxy S4 two weeks ago, and I'm really curious. I rooted my phone, installed Clockwork Mod and backed up my data (I THINK) and I'm looking into ROMs for the Galaxy S4. What is the best mod for speed and performance, with good ease of use, and does not require a data wipe on installation? And is there a tutorial to go about doing this? I'm kind of new to the whole smartphone thing (used a feature phone for seven years!!), but I'm not too afraid to try new things out.
Click to expand...
Click to collapse
No ROMs 'require' a data wipe per se. You may, however, run into problems with any ROM if you don't completely wipe data when installing (especially the first time you go from stock to a ROM).
Why are you so afraid of wiping data? You could very easily download a few backup apps and have everything back up and running in 20 minutes.
trebb said:
No ROMs 'require' a data wipe per se. You may, however, run into problems with any ROM if you don't completely wipe data when installing (especially the first time you go from stock to a ROM).
Why are you so afraid of wiping data? You could very easily download a few backup apps and have everything back up and running in 20 minutes.
Click to expand...
Click to collapse
I assume that this requires backup to my SD card though? And can you explain how I go about doing this? Do I just pick up things like App Restore and Backup (I think it's the other way around...) and then backup and restore? I don't want to screw this up, because I have a few apps where I've dumped a couple hundred dollars into and if I delete it or wipe it, I lose all the data, and I for sure as hell don't wanna do that!
You are rooted, so grab Titanium Backup, and use it. Just don't backup up system data. App data is fine (at least it always has been on AT&T).
I haven't seen a ROM yet that is stable enough to flash, IMHO. Give it a couple of weeks. I ran AOKP on my GS2 for a long time, and am looking forward to it here.
Sent from my SCH-I545 using xda premium
If I was you man , I wouldnt never install a rom without a full wipe. That will keep you from running into problems. I know that from experience. Like Sbreen say, no wipe , no gripe
DroidHead214 said:
If I was you man , I wouldnt never install a rom without a full wipe. That will keep you from running into problems. I know that from experience. Like Sbreen say, no wipe , no gripe
Click to expand...
Click to collapse
Very well then, I guess a wipe it is.
Now, let me get this straight. I rooted my phone. I have TWRP Custom Recovery on my phone, and I have backed up the thing in the recovery menu to my micro SD card. I also Titanium Backup'd my system with apps and whatnot. So when I decide to flash my phone to a new ROM, I'd first wipe the data, factory reset, and wipe the dalvik cache, then flash it, do the setup garbage, and then from there, redownload Titanium Backup and restore whatever I want to restore, correct?
Ryukouki said:
Very well then, I guess a wipe it is.
Now, let me get this straight. I rooted my phone. I have TWRP Custom Recovery on my phone, and I have backed up the thing in the recovery menu to my micro SD card. I also Titanium Backup'd my system with apps and whatnot. So when I decide to flash my phone to a new ROM, I'd first wipe the data, factory reset, and wipe the dalvik cache, then flash it, do the setup garbage, and then from there, redownload Titanium Backup and restore whatever I want to restore, correct?
Click to expand...
Click to collapse
You got it! However the "factory reset" option in TWRP actually wipes data/cache/dalvik, I believe. (It tells you at the top of the screen what its going to wipe) Once you got your new rom you're all set to start restoring your apps with TB and enjoy the smoothness. After the setup process when your phone goes to the home screen, it's a good idea to let it sit for 5 to 10 minutes. (some developers advise this)
whiskerz said:
You got it! However, the "factory reset" option in TWRP actually wipes data/cache/dalvik I believe. (It tells you at the top of the screen what its going to wipe) Once you got your new rom you're all set to start restoring your apps with TB and enjoying the smoothness
Click to expand...
Click to collapse
I'll try it either tomorrow...or, later in the week if my courage decides to run away. Now, in the worst case scenario, let's say I completely screw up and get stuck with a bootloop or, I just completely hate the ROM itself. To restore to my current configuration do I just go back to TWRP and hit restore, and it basically reverts itself? I'm so sorry if I'm asking really stupid questions, I just REALLY want to do it right, and not have any hassles whatsoever. I am extremely careful and I really want to feel comfortable doing this.
Some guides I see mentioned backing up the IMEI information on the phone. Do I really need to do that, or is that all automated and I shouldn't run into issues? And is there a GApps.zip file thingy that I need to download for the "stock" applications? But wait a second, TB should take care of all of that correct?
Ryukouki said:
I'll try it either tomorrow...or, later in the week if my courage decides to run away. Now, in the worst case scenario, let's say I completely screw up and get stuck with a bootloop or, I just completely hate the ROM itself. To restore to my current configuration do I just go back to TWRP and hit restore, and it basically reverts itself? I'm so sorry if I'm asking really stupid questions, I just REALLY want to do it right, and not have any hassles whatsoever. I am extremely careful and I really want to feel comfortable doing this.
Some guides I see mentioned backing up the IMEI information on the phone. Do I really need to do that, or is that all automated and I shouldn't run into issues? And is there a GApps.zip file thingy that I need to download for the "stock" applications? But wait a second, TB should take care of all of that correct?
Click to expand...
Click to collapse
Yes, if your phone goes into a bootloop or you absolutely hate the rom, then pull the battery and boot into recovery. (If you just hate the rom no need to pull battery just power off)Make sure you have a backup of your system created within TWRP with the "backup" option. If you have a backup in TWRP you would just hit the "Restore" button and find your system backup and wait for it to restore. I've never heard anything about backing up IMEI info, you will probably not run into any issues. I've flashed tons and tons of roms on numerous devices and have NEVER had to do any of that. Gapps (google apps) are ONLY needed when you're going to run an AOSP rom. That means when the rom doesn't have the touchwiz skin over top of it. AOSP roms are pure vanilla android and have zero touchwiz features. You can find the touchwiz based roms in the "Android development" section while the AOSP roms are found in the "Original development" section. Also, it's fine to ask questions. That's how you learn!
whiskerz said:
Yes, if your phone goes into a bootloop or you absolutely hate the rom, then pull the battery and boot into recovery. (If you just hate the rom no need to pull battery just power off)Make sure you have a backup of your system created within TWRP with the "backup" option. If you have a backup in TWRP you would just hit the "Restore" button and find your system backup and wait for it to restore. I've never heard anything about backing up IMEI info, you will probably not run into any issues. I've flashed tons and tons of roms on numerous devices and have NEVER had to do any of that. Gapps (google apps) are ONLY needed when you're going to run an AOSP rom. That means when the rom doesn't have the touchwiz skin over top of it. AOSP roms are pure vanilla android and have zero touchwiz features. You can find the touchwiz based roms in the "Android development" section while the AOSP roms are found in the "Original development" section. Also, it's fine to ask questions. That's how you learn!
Click to expand...
Click to collapse
Awesome. Phew, I was like what why do I need to backup my IMEI information? I'm planning on installing Hyperdrive, is that a touchwiz based rom by any chance? And hah, yeah I know, I usually have really meticulous instructions for myself when I flash video game consoles, so I know the routine like the back of my hand.
Ryukouki said:
Awesome. Phew, I was like what why do I need to backup my IMEI information? I'm planning on installing Hyperdrive, is that a touchwiz based rom by any chance? And hah, yeah I know, I usually have really meticulous instructions for myself when I flash video game consoles, so I know the routine like the back of my hand.
Click to expand...
Click to collapse
Yes, Hyperdrive is a touchwiz based rom! The file is going to be a little over a 1gig, and already includes all of the apps you'll need.(Don't flash Gaaps) I'm heading off XDA for the night if you have anymore questions/concerns feel free to PM me and I'll try to help
whiskerz said:
Yes, Hyperdrive is a touchwiz based rom! The file is going to be a little over a 1gig, and already includes all of the apps you'll need.(Don't flash Gaaps) I'm heading off XDA for the night if you have anymore questions/concerns feel free to PM me and I'll try to help
Click to expand...
Click to collapse
Oh good! And at least my internet is reasonable now, so 1GB shouldn't be too bad. ;D I should head off too, its a bit late over here. Thanks for your help, you've answered a lot of my concerns!
Please read forum rules before posting
Questions and help issues go in Q&A and help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
All ROMs are the best and data wipes are always recommended