Related
Hey guys, I just flashed my first rom and I wanted to let everyone know especially the dev but since I can't post yet in the dev section I made a thread so hopefully he will be able to read it
I flashed miui pimpmaneaton's custom rom and so far i love the looks of it!!, thanks for the rom pimp!
Congrats, soon enough you'll be flashing like two or three a day.
sshede said:
Congrats, soon enough you'll be flashing like two or three a day.
Click to expand...
Click to collapse
lol I have read that a few times already, looks like you guys are all right!!!
I just flashed mine for the first time a couple days ago as well. And i know just enough to be dangerous. I'm still not sure about the backup process and what each one does.
What does Nandroid Backup do? When should it be done? And when can it be skipped?
What does Titanium Backup do? When should it be done? And when can it be skipped?
For instance, there's a minor update to the ARHD 3.6.9 -> 3.6.10. When i flash this, i assume i should make a Nandroid backup. What about Titanium? What will happen to all my installed apps? Will they be wiped out?
If i install a different ROM all together and don't like it, can i just pull out the Nandroid backup and go back to where i was with the old ROM and all apps still installed?
Also what does Super Wipe do? Does it delete my apps/app data?
wicketr said:
I just flashed mine for the first time a couple days ago as well. And i know just enough to be dangerous. I'm still not sure about the backup process and what each one does.
What does Nandroid Backup do? When should it be done? And when can it be skipped?
What does Titanium Backup do? When should it be done? And when can it be skipped?
For instance, there's a minor update to the ARHD 3.6.9 -> 3.6.10. When i flash this, i assume i should make a Nandroid backup. What about Titanium? What will happen to all my installed apps? Will they be wiped out?
If i install a different ROM all together and don't like it, can i just pull out the Nandroid backup and go back to where i was with the old ROM and all apps still installed?
Also what does Super Wipe do? Does it delete my apps/app data?
Click to expand...
Click to collapse
Well I wish I could help you but I am not sure if I have all the right answers to your questions, like I said I just flashed my first rom last night and i have not restored anything yet.
Now I understand that a nandroid backup should be done before you flash a new rom if you want to restore that same rom at a later time, for example I did a nadroid backup of my stock rom but if I flash another rom I wont do a nandroid of this miui rom.
I did a titanium back of a few saved games but I have not restored anything yet.
Regarding ARHD rom I can't really tell you anything, maybe someone will help you faster if you post in their rom thread.
SuperWipe from what I have read wipes all your data, cache, dalvik with just one click instead of going one by one but in the end it will make the same effect if you wipe data, cache, dalvik one by one.
Lets wait if someone chimes in and correct me so we both can learn more
A nandroid backup is a bit for bit copy of your current Android set up. It'll back up your rom, applications, application data like text messages, playlists, bookmarks. Everything. If you ever want to go back to it, just restore the backup and you'll be up and running in 3 to 5 minutes.
Titanium backup lets you back up individual applications to be restored at a later time. For example, if I download Opera Mobile and set up all my speed dial bookmarks, I'll perform a titanium back up of the application so that if I change roms at a later time, I can restore the back up of Opera Mobile and not have to re-set anything up.
Hope this clears the air. Neither of which have to be done, mind you, but they are incredibly convenient.
A nandroid backup should be done always before flashing a new rom. even if your updating a rom you should still do a nandroid backup just in case something goes wrong. Sometimes devs forget something in updates and it could mess up your set up so always backup for safe keeping.
Thank you both for clarifying it for us
I have recently rooted and s off but may I ask what is a kernel ? I want to install a stock ics Rom (I think its pixel or something like that ) and they talk about kernels a lot . Can I just flash it like normal ?
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
ihearthapple96 said:
I have recently rooted and s off but may I ask what is a kernel ? I want to install a stock ics Rom (I think its pixel or something like that ) and they talk about kernels a lot . Can I just flash it like normal ?
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
You can read here what a kernel is: http://forum.xda-developers.com/showthread.php?p=20768687
In the rom's thread should be the install notes on how to flash that to your phone, basically it is wipe data/factory reset, wipe cache, wipe dalvik and then flash rom.
Congratulations all who flashed their first Rom soon u all people will flashing new Rom every day. That's all possible due to great talented devs of XDA.
Sent from my HTC Sensation Z710e using xda premium
Well I guess you guys are all right, I just flashed my second rom today lol and I think that I will stay with this one for a while , for those wondering I flashed senseay rom
Congratz on your first rom flash
An actual functioning Rom without Errors.
Flashed Android 4.0.1 ICS w/ Android Revolution HD 5.02 yesterday..... It
's still not a brick!
n0ferz said:
Well I guess you guys are all right, I just flashed my second rom today lol and I think that I will stay with this one for a while , for those wondering I flashed senseay rom
Click to expand...
Click to collapse
You may notice diminishing battery life with rom flashes. If this is the case, download Battery Calibration from the market. Charge your phone up to 100% and fire this application up. It'll likely ask for root access upon being started (but it might not). Once you're at 100%, click the giant Battery Calibration button. It may ask for root access a second time, just grant it access and it'll wipe the battery stats file. Then, fully discharge the phone (or atleast within 2 to 5%) and charge it back up to 100%. You should notice an immediate improvement in battery life.
Concrats! Now your grown up! I did my first rom yesterday... Now i feel like a big girl... I was scared ass hell that i would ****ed this up... but it works! So i`m proud!
sshede said:
You may notice diminishing battery life with rom flashes. If this is the case, download Battery Calibration from the market. Charge your phone up to 100% and fire this application up. It'll likely ask for root access upon being started (but it might not). Once you're at 100%, click the giant Battery Calibration button. It may ask for root access a second time, just grant it access and it'll wipe the battery stats file. Then, fully discharge the phone (or atleast within 2 to 5%) and charge it back up to 100%. You should notice an immediate improvement in battery life.
Click to expand...
Click to collapse
Hey thanks for the tip, I will try this today and I hope to get an improvement in my battery life!!
swesjes said:
Concrats! Now your grown up! I did my first rom yesterday... Now i feel like a big girl... I was scared ass hell that i would ****ed this up... but it works! So i`m proud!
Click to expand...
Click to collapse
gratz to you as well
Lol. Nice to see so much excitement.Your Sennys are not virgins anymore. Soon enough they'll become whores, just like many others
sshede said:
Congrats, soon enough you'll be flashing like two or three a day.
Click to expand...
Click to collapse
And there will be alot of bricking in procces.lol.just joking.
Sent from my HTC EVO 3D X515m using xda premium
Once you flashed, you will keep on flashing
Hello,
Thank you for taking the time to read this. I'm currently on Beans' Build five (love it of course). About an hour ago, I went to switch out batteries, and when I turned my S3 back on, I got the normal Pink Samsung stuff exclusive to Beans' rom, then, instead of going to the boot animation of falling jars of Jelly Beans, the screen turns completely black, and vibrates very softly and quickly every seven seconds. I can boot into Clockwork Recovery. I tried wiping cache, dalvik cache, factory reset (3 times), unsuccessful in each attempt. I have no idea what to try next, and was hoping to avoid the whole replacement route. Also, not sure if this is relevant or not, but prior to my latest boot, I installed some automatic Google Wallet Installer app, ran it, and didn't get past the emulator page of the process. I assume it failed. Wasn't too sure if that could have tweaked something with the system, or if it was just a coincidence. Any and all help is appreciated.
Thank you,
Matt
You should reflash your ROM or restore a backup.
Sent from my SCH-I535
kintwofan said:
You should reflash your ROM or restore a backup.
Sent from my SCH-I535
Click to expand...
Click to collapse
That was my initial plan, until I navigated to my extSD and immediately remembered that I had just deleted my backups AND the actual rom itself. So I had to download it on the world's SLOWEST computer in the history of mankind. Anyways, after flashing it, I read your response literally at the exact same time as the jars of JBs began to fall. Thankfully, because I didn't want to lose the 32gigs of internal memory worth of music/videos. Thank you for your quick response, you were right.
Matt
Glad you got it! Bet you keep a backup at all time now.
Sent from my SCH-I535
kintwofan said:
Glad you got it! Bet you keep a backup at all time now.
Sent from my SCH-I535
Click to expand...
Click to collapse
DEFINITELY! That extra space of memory seems less important now. Thanks again.
Sent from my SCH-I535 using Tapatalk 2
Hi
Was running CM10 nightly from 12 Dec. Bluetooth froze while in car. I rebooted phone. It never came back up after booting, just looping Cyanogenmod logo.
Went into recovery, did a Nandroid, restored my previous backup from the 11th. Still looping Cyanogenmod logo.
Got home. Reflashed stock kernel. Went into recovery and flashed CM10 stable after wiping. Comes up with HTC logo, then black.
Tried to go back into recovery. Comes up with HTC logo, then goes black.
Now it lets me into fastboot, and into the bootloader menu, but recovery does not work. Neither does booting normally. Tried reflashing kernel AND recovery (stable TWRP). It just keeps looping the HTC logo.
HBOOT is 1.14.
Help, please. I'm going to destroy this piece of ****.
If all else fails, run a RUU and skip the thread.
yea, just ruu. i ruu'd a few days ago for kicks.
some car chargers and even wall chargers can make ur phone go wonky, my old moto backflip would randomly press buttons if i used a non-motorola charger.
on a side note, i never used the word "wonky" until this forum.
try running "fastboot erase cache"
also try a clean install instead of restoring nandroid, im assuming your also fastbooting the boot.img from all your nandroid backups. if not they probably wont boot.
strange...
I would say ruu and retry as well.. Sometimes accessories can make a phone go haywire.. Besides the phone is not a piece of crap.Roms can never give you complete stability while stock unrooted can.
Yep. Thanks. Had to start from scratch with Sense again. Now on CM10 stable (and stable CM10 kernel). Hopefully it doesn't lose its mind again, I'm going overseas soon. Sigh.
For anyone who has a similar catastrophe - Titanium recovered most (but not all) of my apps from my TWRP backup. I guess my data partition was slightly corrupt. AppExtractor restored my SMS database from the backup too.
I hate phones.
Passa91 said:
Yep. Thanks. Had to start from scratch with Sense again. Now on CM10 stable (and stable CM10 kernel). Hopefully it doesn't lose its mind again, I'm going overseas soon. Sigh.
For anyone who has a similar catastrophe - Titanium recovered most (but not all) of my apps from my TWRP backup. I guess my data partition was slightly corrupt. AppExtractor restored my SMS database from the backup too.
I hate phones.
Click to expand...
Click to collapse
I always export my contact list to /sdcard if a change is made and then backup to google just in case
Passa91 said:
Yep. Thanks. Had to start from scratch with Sense again. Now on CM10 stable (and stable CM10 kernel). Hopefully it doesn't lose its mind again, I'm going overseas soon. Sigh.
For anyone who has a similar catastrophe - Titanium recovered most (but not all) of my apps from my TWRP backup. I guess my data partition was slightly corrupt. AppExtractor restored my SMS database from the backup too.
I hate phones.
Click to expand...
Click to collapse
I'd suggest keeping a boot.IMG and a stock ROM on the SD card along with adb drivers so you can fix it with a computer without downloading anything.
Sent from my Nexus 4 using xda premium
I have a possibly simple yes or no question in the case there is no alternative. So, I am currently running 4.2.2 PAC-Man Rom and I want to update to the 4.3 version of it. Technically, speaking, I have no issues in updating the ROM itself. The problem is when I try to keep my app data moving from 4.2.2 to 4.3. Whenever I try to restore data via Titanium Backup, the phone will allow it, but upon the next shutdown, will not boot again. Likewise, I have also tried to flash 4.3 and then do an advanced restore via CWM and only restore data. This has the same results as the previous option in that I can boot the phone, but if I shut it off, it won't restart. Basically, I can keep and install the original app apks, but the moment I try to restore any form of app data from the previous iteration of the ROM, my phone will refuse to restart. This predicament is met on any 4.3 ROM I have tried. I have never had this problem before, as I have been able to move from 4.1.2 to 4.2.1 to 4.2.2 (I suppose 4.3 is different?). This brings me to my question, is it possible to keep app data moving from 4.2 to 4.3? I fear I already know the answer. In any case, thank you for your time.
Tl;DR
When moving to 4.3, restoring app data from previous rom (PAC-man 4.2.2) causes the phone to lose the inability to boot. Is there any way to keep app data, or is it a lost cause? Thank you for your time.
One thing that comes to mind is are you restoring any system data? That causes problems.
Other than that I would download and install all my apps through the app store and reboot.
Then make a restore image to fall back on so you don't have to repeat these steps.
Now start restoring you app data SELECTIVELY. And restore app data ONLY. And do it one by one and reboot. This is the only way I know that can pin point the problem or the one restore data piece causing you problem.
Identifying it is the hardest part, any better ideas are welcomed.
Once identified just avoid that one app as your migration casualty.
Good luck,
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
verissimus said:
I have a possibly simple yes or no question in the case there is no alternative. So, I am currently running 4.2.2 PAC-Man Rom and I want to update to the 4.3 version of it. Technically, speaking, I have no issues in updating the ROM itself. The problem is when I try to keep my app data moving from 4.2.2 to 4.3. Whenever I try to restore data via Titanium Backup, the phone will allow it, but upon the next shutdown, will not boot again. Likewise, I have also tried to flash 4.3 and then do an advanced restore via CWM and only restore data. This has the same results as the previous option in that I can boot the phone, but if I shut it off, it won't restart. Basically, I can keep and install the original app apks, but the moment I try to restore any form of app data from the previous iteration of the ROM, my phone will refuse to restart. This predicament is met on any 4.3 ROM I have tried. I have never had this problem before, as I have been able to move from 4.1.2 to 4.2.1 to 4.2.2 (I suppose 4.3 is different?). This brings me to my question, is it possible to keep app data moving from 4.2 to 4.3? I fear I already know the answer. In any case, thank you for your time.
Tl;DR
When moving to 4.3, restoring app data from previous rom (PAC-man 4.2.2) causes the phone to lose the inability to boot. Is there any way to keep app data, or is it a lost cause? Thank you for your time.
Click to expand...
Click to collapse
What recovery are you using? If it's not TWRP 2.6.0.3 or newer, or the custom CWM provided by Team Chopsticks, you will continue to have this problem. Also, it has absolutely nothing to do with restoring data.
Fixed XD
Okay, so I have been doing nandroid backups the whole time, so I haven't really lost anything. I did try to install apps using Google Play and it would cause the same problem that restoring data only via cwm would. That said, I got bored and just left the phone boot looping and slept for 5 hours. Interestingly enough, upon checking on it later, it had in fact booted and it did function. Naturally, I reverted back to 4.2 and tried to upgrade again, this time timing it. Over all, it took about 1 hour for the phone to stop bootlooping and actually boot up. I don't really know what is wrong, but hey, it works. Nevertheless, I would like to thank you guys for your input. Sorry that my problem wasn't actually what I thought it was. :/ Good day.
verissimus said:
Okay, so I have been doing nandroid backups the whole time, so I haven't really lost anything. I did try to install apps using Google Play and it would cause the same problem that restoring data only via cwm would. That said, I got bored and just left the phone boot looping and slept for 5 hours. Interestingly enough, upon checking on it later, it had in fact booted and it did function. Naturally, I reverted back to 4.2 and tried to upgrade again, this time timing it. Over all, it took about 1 hour for the phone to stop bootlooping and actually boot up. I don't really know what is wrong, but hey, it works. Nevertheless, I would like to thank you guys for your input. Sorry that my problem wasn't actually what I thought it was. :/ Good day.
Click to expand...
Click to collapse
This is due to the recovery version you are on as the guy before your last post indicated. It has nothing to do with your restoration of data, but rather the recovery used to flash the rom and the way it's handling the partitions.
Long story short, update your recovery to one of the ones indicated two posts above mine and you should be good to go.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
bps119 said:
This is due to the recovery version you are on as the guy before your last post indicated. It has nothing to do with your restoration of data, but rather the recovery used to flash the rom and the way it's handling the partitions.
Long story short, update your recovery to one of the ones indicated two posts above mine and you should be good to go.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Ah, okay, that makes a great deal of sense. Thank you for elucidating, I shall do just that.
Last night I was out and my battery drained and phone shut off. When I got to the car and put it to charge the phone got stuck in the loading screen for a long time. I power cycled and nothing. I booted up to TWRP and wiped cache and the phone booted and got to the updating apps part and at the end it got stuck in the starting app part and never finished booting.
I'm on stock 4.4.2 and rooted. I was using faux's mainline kernel and had been running the latest version for a few days already.
I've tried a few things to try to get it working. I flashed the stock kernel back again and that didn't work. I also flashed the stock system image but nothing. I've been searching al morning for a fix. If possible, I would like to fix it without having to lose all my data.
Here is a logcat as well. http://pastebin.com/UYn9Z3Ja
This might sound too simple, but have you tried holding the power button for 30 seconds and letting it boot
Sent from my Nexus 5
Yea. I've power cycled it a few times and just let it sit there for long periods of time to see if it boots and it doesn't go past the boot animation. Only time it goes past it is when I wipe cache and after that it get stuck on starting apps.
I'm afraid your going to have to factory reset it. This is kind of a pita, but in recovery adb pull your /sdcard to your pc. Then afterwards adb push it back. That'll save your data. You'll probably have to flash the factory image and then reinstall twrp too.
Sent from my Nexus 5
I was afraid that it may come to that. In regards to my data. I made a TWRP backup earlier. Can I restore any of it after I do the factory reset?,
JayBachatero said:
I was afraid that it may come to that. In regards to my data. I made a TWRP backup earlier. Can I restore any of it after I do the factory reset?,
Click to expand...
Click to collapse
Sure but only users apps and data, no system apps.
JayBachatero said:
I was afraid that it may come to that. In regards to my data. I made a TWRP backup earlier. Can I restore any of it after I do the factory reset?,
Click to expand...
Click to collapse
You can but maybe the cause of the ''not booting issue'' will be in that already
JayBachatero said:
I was afraid that it may come to that. In regards to my data. I made a TWRP backup earlier. Can I restore any of it after I do the factory reset?,
Click to expand...
Click to collapse
You can restore one of your nandroids afterwards no problem
Sent from my SAMSUNG-SGH-I727
Thanks for the responses. I'll give this a try and report back later.
JayBachatero said:
Thanks for the responses. I'll give this a try and report back later.
Click to expand...
Click to collapse
Pulling and pushing the sd card will take along time. Probably 30 minutes each way or longer depending on how much stuff you have on it
Sent from my SAMSUNG-SGH-I727
Oh that I know. Part of the reason why I was avoiding the full wipe. I have the about 24gigs to pull/push
JayBachatero said:
Oh that I know. Part of the reason why I was avoiding the full wipe. I have the about 24gigs to pull/push
Click to expand...
Click to collapse
Grab a beer and get comfortable
Sent from my SAMSUNG-SGH-I727