Related
How much wiping do you need to do when you are upgrading to a new ROM release? I don't really want to have to go through all of the setup every time a ROM is updated. What does every generally do?
I'm running the G-Harmony ROM.
Use Titanium backup or the like to take a backup of everything if you are upgrading from one version of the rom to a new version. At first I wasn't backing up and spent hours getting everything back to the way it was. Now, in a matter of minutes I'm back running the same way I was before, but on a newer ROM.
Take the backup -> copy the backup folder to your micro sd card or computer -> follow the steps to install the ROM (do what is recommended such as the user data, dalvik, cache) -> once the rom is up and running, copy the backup folder back to your tablet -> download titanium backup, it will see the folder you copied over containing your backup-> restore data, apps, user settings from titanium backup.
I'm not sure how it works if going from ROM to ROM, probably want to search on it.
Cool, that's pretty much what I did. Unfortunately, I hadn't copied off the TitaniumBackup folder, and the new ROM version switched the emmc and SDCard mount locations, so I had to switch them back to be able to get at my backups. I didn't have an external micro SDCard reader with me, so I couldn't easily copy the folder from the internal card to the external. Ah, well. Going through the Titanium restores right now. I really should buy this software to prevent having to approve every restore
chadness,
One of the main things I try to help people here with is boot loops and I spend a
lot of time trying to figure out the cause so we can prevent it.
IT IS MY OPINION that one of the things causing the boot loops and making
people have to re-flash and re-partition -- is the stuff leftover in flash after
flash playing with their tablets.
I'm not sure the Android file system is all that good. I don't believe in tablet formats
because it doesn't work like a hard disk. You can delete a file and go back later and
the file is still there. You can nvflash the tablet and stuff is still let there.
When stuff gets left over it can conflict with the new stuff and BAM -- boot loops.
All of this is to say -- I SAY before every ROM burn you should nvflash to a solid
version -- bekit 1105 (2538) or 3588 -- the repartition to 2048 and 0, Fix Permissions,
Wipe Dalvik Cache, Wipe Cache and Wipe/Reset Factory Data.
I can't prove it yet -- but I bet if people would do that most of the boot loops would stop -- and probably some of the other little stuff too.
This is just my opinion -- but then I have only nvflashed either of my G-Tablets one time in five months now (involuntarily -- because of problems.)
Think about it.
Rev
Interesting! I've been flashing different ROMs this week and haven't run in to any problems as long as I've formatted system and data.
butchconner said:
. . .
All of this is to say -- I SAY before every ROM burn you should nvflash to a solid version -- bekit 1105 (2538) or 3588 -- then repartition to 2048 and 0, Fix Permissions, Wipe Dalvik Cache, Wipe Cache and Wipe/Reset Factory Data.
. . . . Rev
Click to expand...
Click to collapse
Rev, what is your opinion about using 'Calkukin's_Format_All.zip & wiping Dalvik Cache' vs all the above steps ?
Yeah, I just flashed from EB01 SC 292 to ED01 MIUIWiz after full Data, Cache, Dalvik, and voltage double wipes, and restored all my old EB01 user Data and apps over MIUIWiz, all in under 17 minutes.
Edit: adding navenedrob's utility method has cut this down to under 10 minutes, plus navigation and reboot time. See post #5
How? Just followed what the Devs have taught us, plus Nandroid Advanced Restore in CWM.
I have been doing this for every ROM I have flashed since I discovered what a Nandroid backup was.
But this is not just a Nandroid Backup. This is a partial restoration called “Restore data” under “Advanced Restore.” All in CWM recovery.
Here is the method I use:
Charge to 100% (At this point, I started the timer)
Boot to Recovery
Wipe Cache and Dalvik (and Voltage for MIUIWiz) x2
Make a Nandroid backup
Wipe Data x2
Flash the new ROM (of your choice) in CWM
Let it boot
Boot to Recovery
Select “backup and restore”
Select “Advanced Restore”
Select the Nandroid Backup file you wish to restore from (probably your latest one)
Here is where it gets cool, and less scary…
There is yet another page, with options:
Restore boot
Restore system
Restore data
Restore cache
Restore sd-ext
+++++Go Back+++++
So no sweat yet
Select “Restore Data”
Reboot completely
Turn off phone (here is where I stopped the timer at 16.5 minutes)
Charge to 100%
Boot and enjoy.
BAM! All the old data is back. On top of the new ROM. Except for stuff that no longer applies, like maybe in-ROM launchers that no longer exist.
My ROM flashing evolution path has been:
Stock
Odin DXC DB/DO tar
EC01 DB/D0 (zip i think, can't remember)
Full ED01 (Adrynalyne method, not OTA)
ComROM 1.0 zip
Evil Fascination, all variants in sequence. Zip
EB01 SC 2.9.2 zip (Why? To see if it would work. Because it means restoring ED01 Nandroid data over an EB01 ROM. Without compromising the ROM. (Thanks for the assistance with this, Lttlwing16.)
ED01 MIUIWiz
Seems to work flawlessly so far. No forced closes, no hiccups, just sweet functionality. Every time so far. And so quick, I sometimes actually have time to use my phone between flashes.
As I said, I have been doing this for just about as long as I have been flashing through CWM. Your backup may overwrite some ROM theme elements, so that is something to think about.
Any other drawbacks? Not that I have found, but…Not completely sure yet, So… You know the drill…
DO NOT TRY THIS UNLESS YOU ACCEPT FULL RESPONSIBILITY AND ARE PREPARED TO DEAL WITH THE CONSEQUENCES!! YOU MAY LOSE DATA OR FUNCTIONALITY!! YOU MAY EVEN MANAGE TO BRICK THIS THING!
But you just made a complete clean-wiped Nandroid Backup, right? So you can always restore the whole thing. Or worst case, do the Odin recovery method. (or even worse case, Heimdall).
I suspect that there is some reason that this method has not been widely promoted already. It seems unlikely that it has not been experimented with, so maybe someone can help show a newbie the error of his ways. Or we may need someone with a thorough knowledge of Fascinate ROMs to add some warnings, caveats, or guidance around potential problems, etc. But it does seem to work just fine for me, and all of the ROMs I have worked with seem smooth and stable. All my apps always work, and update properly. Unless I get stupid and screw something up.
It does seem that Android should be able to pull this off if sufficient attention is given to file structure and dependencies, and if everything data can be kept where a data only restore would look for files. I suspect that I have been having success because of the good work of all the great ROM builders and developers working to fix the Fascinate, and make our experience all that it is. So if this works for you, they are the ones that really deserve the credit and the thanks. They made it work. I just followed instructions, got curious about Nandroid Advanced Restore, and pushed the right buttons. Oh, and wrote it all down.
Wiping data and dalvik cache is kinda pointless because it gets overwritten and replaced by the restore anyway. Dalvik cache is located in the data partition, not the cache partition, ironically.
Sent from my SCH-I500 using XDA App
Well, I am expecting to learn something from posting this. So thanks. However, it raises more questions for me.
Does it mean that I never have actually needed to wipe data? I could have flashed all those ROMs without wiping data and without issues?
My understanding was that at least the cache would be re-written as needed by the new ROM, rather than trying to work with data created by the old one.
It sounds like it means that if bringing back the old data works, keeping the old data would have worked, too. So even Dalvik could have been left every time?
My thinking was that cleaning the cache and Dalvik before making the backup would mean that when restoring, they would come back blank, and not confuse the new ROM. I was under the impression that something was more likely to go wrong if all that stuff was left in there, and it was safer to bring it in later, after the ROM boots up, and give the new ROM a chance to properly recognize and deal with it.
Is there any logic in that logic? Just asking, because I really don't know. It sounds good.
If not, this thread is for educational purposes only.
But dang, either the Devs are even more awesome than we thought, or I must get lucky a lot. Because I have flashed quite a few ROMs without issues, force closes, etc.
Interested in more feedback on this process.
OK, I did have a couple of FCs of Gmail this last time flashing MIUIWiz, going from EB01 to ED01. It seemed to fix itself after I closed it twice, but I updated Gmail anyway. No repeats.
I have a new preferred method of backing up, cleaning the files, flashing new ROMs and restoring my data. Flashed MIUIWiz 111 over EF 360, the whole process taking about 10 minutes altogether plus navigation and boot time.
(Always create a clean Nandroid Backup (with wiped cache and Dalvik, possibly voltage) 4-5 minute process, not included. This should ensure that the new ROM will create its own compatible cache data after the restore.)
1. Run navenedrob's reformat utility [UTILITY]EXT4/RFS Formatter (CWM3 recovery packages) - xda-developers as a CWM zip from sd card <1 minute process.
2. Flash the new ROM in CWM <1 minute process.
3. Flash new Kernel if needed (before allowing ROM to boot) in CWM <0.5 minute process
4. Allow ROM to boot (3-4 minute process)
5. Nandroid Advanced Restore in CWM (Data only) (3 minute process)(Restores all User Data and apps)
From navenedrob: “Understand that this [format utility] will completely wipe your system, data, datadata (dbdata), and cache. This is a "full" wipe of the device.” But it also puts things back in order if they have gotten screwed up. This could be the solution to issues you are having. Thanks, navenedrob! Very cool.
If there are particularly desirable user setups in the flashed ROM, be advised they may get lost in the restore.
The only issue I seem to have is the need to update/install Gmail. Then all is smooth.
Works for me, but you may totally bork yours. You are responsible for what you decide to do.
times_infinity said:
Wiping data and dalvik cache is kinda pointless because it gets overwritten and replaced by the restore anyway. Dalvik cache is located in the data partition, not the cache partition, ironically.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I think that means wiping data also wipes Dalvik. So Dalvik wipe is redundant when wiping data. Good to know about the partition info. Seems to support the idea that wiping Dalvik before making the backup would ensure that when the restored data is brought back, it brings no Dalvik data with it, avoiding potential issues with the new ROM.
hi,
first off, apologies is this has already been discussed..
i have a sgs2 and have rooted it and installed miui, and then recently installed cyanogen 7.
im having signal problems and my data signal is also poor.
i also find my memory is cluttered with old app data.
i would like to completely remove all data off my phone and install a clean and reliable rom (any recommendations of the best one?). i would also like to update my kernel and firmware to the most reliable one.
can you please advise me on how to do so.
once again apologies if this is already been covered.
thanks
azam
Always use data wipe/factory reset option in CWR.
iv decided i want to go back to stock rom. what is the correct proccess?
Yeah just do data/reset or if u unsure ucan use
Moun then format data cache n system
check the sgs2 forums as there are some guides available and even some odin one-click restores which accomplish the task.
back up any data to pc/external sd and when you do a factory data reset in the rom chose format usb storage as that will clean off any other remnants you may be seeing.
ok so basically i want to find a way to get to 4.3 either rooted or unrooted, my problem is that i have pretty bad ocd and one of my major major problems with that disorder is my tech devices, i will most likely have an anxsiety attack or 2 if i have to set up my phone from scratch and i will spend hours making it look exactly the same. anyway, i want to know:
1:how to update rooted gs3 Gt-i9305t 4g/lte model without loosing data (if possible )
2: update to 4.3 and un root without loosing data (im sure thats impossible )
i would really appreciate the help as i cannot find anyone looking for the same help as me (kinda strange how no one cares about there data at all, but meh)
also on a side note, i have the problem with my s3 where any sd card i put into the machine will eventually kill itself and never work again as far as i know, it has killed 3 32gb sd cards now and its starting to piss me off to the point where i am no longer using an sd card at all. why does the phone do this and is there any way to fix it? either software wise or hard wear wise? thanks !!! :fingers-crossed:
4.3 source code has only just been released. 4.3 roms are not fully functional and have bugs. There are no official releases so they are all "rooted".
You really do need to wipe when making version updates. Theres no way around this.
Stick with what you've got.
that just sucks.
rootSU said:
4.3 source code has only just been released. 4.3 roms are not fully functional and have bugs. There are no official releases so they are all "rooted".
You really do need to wipe when making version updates. Theres no way around this.
Stick with what you've got.
Click to expand...
Click to collapse
that honestly sucks so much, thanks for the info though.
hey another quick question, is there a way to so a full backup, like im talking FULL, like down to the point of where ur apps are placed and all there data, like apple devices have through itunes?? (restore from backup option) cus if so then i dont mind wiping at all, i just hate apple so i will never go back to one of there piece of **** devices again (i like features with my shiny brick) but yeah anything like that? or can kies do that?
i'm using temasek 4.3 preview 3 atm, you should check it out since developer is extremely helpful
and he updates regularly (which is important)
There are a number of ways to keep your data. Including ones that will let you change the ROM and still have your data. Titanium Backup - not sure if it is only Pro version but the one I have lets me create a backup on the extSDcard so I can flash it in a new ROM and restore all my apps and data straight off. SMS Backup and restore and Call Backup and restore both save out your data to the extSDcard so you can bring them back. I used to use My Backup Root as well but it ceased to work on the last update so I nuked it.
Add in a nandroid backup on something like Philz Recovery (where you can do an Advanced Restore from External SDCard and bring back just parts of your current ROM) and you can always get back to your look & feel in any new ROM.
The one thing I ahve NOT found a solution for is replacing my widgets back on the screens they are on - I run 7 screens and it pisses me off a full recovery in something like Titanium doesn't restore my widgets. The only way it happens is a full nandroid restore but that nukes the new ROM I have just installed so that's not an option.
I run Purelook HD as my 1st ROM, GoogyMax kernel and SlimBean as my 2nd ROM. I can nuke either or both and be back to my set up (including widgets) in about 45 minutes.
Journyman16 said:
There are a number of ways to keep your data. Including ones that will let you change the ROM and still have your data. Titanium Backup - not sure if it is only Pro version but the one I have lets me create a backup on the extSDcard so I can flash it in a new ROM and restore all my apps and data straight off. SMS Backup and restore and Call Backup and restore both save out your data to the extSDcard so you can bring them back. I used to use My Backup Root as well but it ceased to work on the last update so I nuked it.
Add in a nandroid backup on something like Philz Recovery (where you can do an Advanced Restore from External SDCard and bring back just parts of your current ROM and you can always get back to your look & feel in any new ROM.
Click to expand...
Click to collapse
Lets dissect this a little.
A Nandroid backup will take a snapshot of your phone. If you flash something wrong, it can be used to restore your data / settings and rom exactly how it was. This will not help restore your data and settings on a new ROM where you had to perform a wipe. (You have to perform a wipe to prevent data and settings incompatibilities with the new ROM that will cause problems.)
Titanium backup is great. However, if you had to perform a wipe, you cannot simply restore everything using Titanium. This is because you will be restoring the incompatabilities (System data) and restoring the problems (negating the point of the wipe in the first place). You can restore user apps and data with titanium but there will be an element of manually setting all your rom settings.
OP - Please read the "Read before rooting" thread in my signature for more info.
**** that
screw it, ill just stay on 4.2.1 i mostly want it cus they (****ING FINALLY ) partially fixed the setting wallpaper problems so you can get at least most of the photo in the screen now, i have it on my nexus 7 but now cant get it on my phone : / screw ocd, it has plagued me since i was little
adex9 said:
screw it, ill just stay on 4.2.1 i mostly want it cus they (****ING FINALLY ) partially fixed the setting wallpaper problems so you can get at least most of the photo in the screen now, i have it on my nexus 7 but now cant get it on my phone : / screw ocd, it has plagued me since i was little
Click to expand...
Click to collapse
We all spend hours making it look exactly the same. It's annoying but essential.
rootSU said:
Lets dissect this a little.
A Nandroid backup will take a snapshot of your phone. If you flash something wrong, it can be used to restore your data / settings and rom exactly how it was. This will not help restore your data and settings on a new ROM where you had to perform a wipe. (You have to perform a wipe to prevent data and settings incompatibilities with the new ROM that will cause problems.)
Titanium backup is great. However, if you had to perform a wipe, you cannot simply restore everything using Titanium. This is because you will be restoring the incompatabilities (System data) and restoring the problems (negating the point of the wipe in the first place). You can restore user apps and data with titanium but there will be an element of manually setting all your rom settings.
Click to expand...
Click to collapse
The Advanced Restore in Philz lets you restore Data. The choices are, Restore Boot, System (+or- reload) Data, Cache and sd ext. The Data restored my latest personal stuff from the BU I tried just before a new ROM experiment. So not all Restores are the same. You don't have to bring it ALL back from a nandroid.
Journyman16 said:
The Advanced Restore in Philz lets you restore Data. The choices are, Restore Boot, System (+or- reload) Data, Cache and sd ext. The Data restored my latest personal stuff from the BU I tried just before a new ROM experiment. So not all Restores are the same. You don't have to bring it ALL back from a nandroid.
Click to expand...
Click to collapse
@Journyman16
You seem to be missing my point.
If you can restore just data via recovery (which you can) then you didn't need to wipe in the first place.
ROM goes in /system. We all know that. Our apps go in /data/app. We all know that. Our data for our apps goes in /data/data but what some may NOT know is that /data/data contains all your system data too. When you set a ring tone or wallpaper, its in /data/data.
If you go from 1 ROM to another, you may not have to wipe. Or you may HAVE to wipe. It depends if there is incompatible system data in /data/data or not.
When you do wipe, you wipe /data/* (includes /data/data). If you nandroid restore /data and your phone works perfectly, you didn't need to wipe. So my point remains.
If you HAD to wipe, you cannot simply restore data via recovery and have a fully working phone.
rootSU said:
@Journyman16
You seem to be missing my point.
If you can restore just data via recovery (which you can) then you didn't need to wipe in the first place.
ROM goes in /system. We all know that. Our apps go in /data/app. We all know that. Our data for our apps goes in /data/data but what some may NOT know is that /data/data contains all your system data too. When you set a ring tone or wallpaper, its in /data/data.
If you go from 1 ROM to another, you may not have to wipe. Or you may HAVE to wipe. It depends if there is incompatible system data in /data/data or not.
When you do wipe, you wipe /data/* (includes /data/data). If you nandroid restore /data and your phone works perfectly, you didn't need to wipe. So my point remains.
If you HAD to wipe, you cannot simply restore data via recovery and have a fully working phone.
Click to expand...
Click to collapse
Thanks for the explanation - that helps me understand better what goes on. Would that explain perhaps why, after some Restores, I had to run Fix Permissions to stop the FC's?
Journyman16 said:
Thanks for the explanation - that helps me understand better what goes on. Would that explain perhaps why, after some Restores, I had to run Fix Permissions to stop the FC's?
Click to expand...
Click to collapse
Yep, it could do.
Any updates (I am facing the same problem)?
BTW, OTA updates seem to be able to keep most if not all settings. How they manage to do this?
moshepupkin said:
Any updates (I am facing the same problem)?
BTW, OTA updates seem to be able to keep most if not all settings. How they manage to do this?
Click to expand...
Click to collapse
Same here. I've been looking for the exact method to do this, but haven't had any luck so far.
I ended up using Kies to update to 4.3 - it does not check root status.
moshepupkin said:
I ended up using Kies to update to 4.3 - it does not check root status.
Click to expand...
Click to collapse
Hmm, it says that my current firmware is the latest version, rather than 4.3. Is there anything special you're supposed to do?
AriaOfSorrow said:
Hmm, it says that my current firmware is the latest version, rather than 4.3. Is there anything special you're supposed to do?
Click to expand...
Click to collapse
Who says there is a 4.3 for your phone ???
JJEgan said:
Who says there is a 4.3 for your phone ???
Click to expand...
Click to collapse
Well, let's see... there's everyone I know that also has this phone. People online that say they have this phone. Web sites saying that this phone has officially received 4.3. The phone itself saying there is an update for the firmware. So, basically everyone/thing except the Kies program.
Who says their is an update for your phone repeat your phone not some other guys phone and as you failed to give any firmware details impossible to check .
Kies/ Samsung says not for your phone yet.
Contact your vendor .
See multiple identical posts .
Flash stock rom through Odin from sammobile .com
JJEgan said:
Who says their is an update for your phone repeat your phone not some other guys phone and as you failed to give any firmware details impossible to check .
Kies/ Samsung says not for your phone yet.
Contact your vendor .
See multiple identical posts .
Flash stock rom through Odin from sammobile .com
Click to expand...
Click to collapse
I already told you who said there is an update for my phone. Unless my phone is disguised as some one of a kind phone, I'm supposed to be able to update to 4.3.
Alright, I hope I have this in the right place. I just recently flashed the TerraSilent Kernel for the Galaxy Player 4.0 US version. The Flash went fine, but my device was running extremely slowly. A re-flash didn't solve it either. I figured that wiping the cache partition might solve the problem - I decided to do this before running a backup, since no important data is stored in the cache (...right?), and since I was worried that backing up while I had this problem could make things worse - so I went ahead into CWM and did just that. Then, it reboots, and I nearly get a heart attack. The stock wallpaper is back, it's using the default launcher again (I had LauncherPro installed), and pretty much only system apps work, all the others have an icon with an SD card on it, and when clicked on, it says something like "application not installed". I did some searching, and it seemed like a reboot might help (although I didn't find anyone with a problem like mine anywhere). The reboot didn't do anything, so now I have it shut down, so that nothing can happen. The odd thing is, it doesn't seem to me like the system messed up and did a full wipe instead, either, because a couple of things I have are still there - for example, some of my bookmarks I made on the homescreen while still using the default launcher are still there. I'm really confused because I have wiped the cache partition before, when I was still on an unmodified stock kernel, and everything stayed the same, the way I thought it was supposed to. And now this happens. What do I do now? I exported my absolute most important data (Astrid Tasks and Calendar) before I installed TerraSilent (but I obviously wasn't able to do a full backup because I wasn't rooted, I figured installing TerraSilent would root it), so my absolute most important data is on my computer. I also did a simple file backup of the internal USB storage and external SD card to another computer before flashing TerraSilent. However, there is still a good deal of data still need, and a lot of data that would just be a pain in the rear to recreate, not to mention my (valuable to me) game data. What did I do wrong - or did something in the system mess up? And - what do I do to get back to where I was before?
It happened to me when I was on gingerbread with terrasilent. It's a known issue with this kernel. In fact, you didn't wipe the data, but the recovery contain a bug wich format the data as soon as you do an operation wich mount the data partition(I think it's this but I can't remind) but it doesn't wipe the system or anythin else, so the icon, setting and everything else stay there but without anything attach to them. I don't remind what was causing it, I only stopped using cwm with this kernel unless I wanted to flash something or to wipe everything. Sorry but I can't help you more as I don't remind everything, it's been a while since I've been on gingerbread.
ti-pich said:
It happened to me when I was on gingerbread with terrasilent. It's a known issue with this kernel. In fact, you didn't wipe the data, but the recovery contain a bug wich format the data as soon as you do an operation wich mount the data partition(I think it's this but I can't remind) but it doesn't wipe the system or anythin else, so the icon, setting and everything else stay there but without anything attach to them. I don't remind what was causing it, I only stopped using cwm with this kernel unless I wanted to flash something or to wipe everything. Sorry but I can't help you more as I don't remind everything, it's been a while since I've been on gingerbread.
Click to expand...
Click to collapse
Wasn't that problem solved with a later version of the kernel though?
And, assuming that's what happened (what you describe sounds pretty much like what happened to me), would that mean that the only way to try and get it back would be by trying to recover the formatted data?
trainman261 said:
Wasn't that problem solved with a later version of the kernel though?
And, assuming that's what happened (what you describe sounds pretty much like what happened to me), would that mean that the only way to try and get it back would be by trying to recover the formatted data?
Click to expand...
Click to collapse
It was said to be resolved, but it happened to some peoples even thought. Maybe you can recover some of your data with your computer and some tools that let you get the erased data, but I can't guarantee the integrity of your data and you would need to replace every bit of data that was there before to get it running nicely. The easiest way would be to try to recover some of your important data, put it on your computer then wipe your player and start from scratch (wipe data/factory reset) and reinstall your apps. Then put back the save, or setting or files that you got back in your apps. Hope this help, I'm not a proffessional with data recovering or where to put it back after you got it, maybe someone else could further help you with this.
And the conclusion...
ti-pich said:
It was said to be resolved, but it happened to some peoples even thought. Maybe you can recover some of your data with your computer and some tools that let you get the erased data, but I can't guarantee the integrity of your data and you would need to replace every bit of data that was there before to get it running nicely. The easiest way would be to try to recover some of your important data, put it on your computer then wipe your player and start from scratch (wipe data/factory reset) and reinstall your apps. Then put back the save, or setting or files that you got back in your apps. Hope this help, I'm not a proffessional with data recovering or where to put it back after you got it, maybe someone else could further help you with this.
Click to expand...
Click to collapse
OK, my reply is late, but thanks for your help. I managed to copy the partition with all the deleted contents over to the computer, and I'll have to study the contents some other time, because I've spent about 24+ hours on this problem in total, and need my device for more important purposes - those for which the data I managed to copy before the custom kernel and everything else. For those of you who have a similar issue, this is how I managed to save (or that is I am 95% sure this will have saved at least some, as I said I haven't studied it yet) what I hope is a good chunk of my data.
Have you tried flashing a different kernel? Terrasilent also gave me some weird in that after a few days my device would boot into recovery by itself then wipe all my data in that only my system apps would remain. So it's a little different than what's happened to you. I ended up using klin's R3 kernel or Steven's kernel that fixed the issue.
Sent from my YP-G1 using xda app-developers app
obscuresword said:
Have you tried flashing a different kernel? Terrasilent also gave me some weird in that after a few days my device would boot into recovery by itself then wipe all my data in that only my system apps would remain. So it's a little different than what's happened to you. I ended up using klin's R3 kernel or Steven's kernel that fixed the issue.
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
I've got huge issue with steve's kernel. You can get into recovery, but once you booted in it will simply bootloop. Then you have to flash back with odin. So if you go with steve's kernel, don't boot into recovery. As for klin's kernel, I've never tried it, and will probably never as we have some really nice jellybean rom that I recommend you.
I never got that issue with steve's kernel.
Sent from my YP-G1 using xda app-developers app
obscuresword said:
Have you tried flashing a different kernel? Terrasilent also gave me some weird in that after a few days my device would boot into recovery by itself then wipe all my data in that only my system apps would remain. So it's a little different than what's happened to you. I ended up using klin's R3 kernel or Steven's kernel that fixed the issue.
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
Actually, with my problem, my system apps did remain, so it's almost the same problem, only my device didn't boot into recovery on its own (seriously, it booted into recovery on its own and wiped the data? ). I only installed the terrasilent kernel to be able to upgrade to JB, so I'm now on JB, running into different problem (the wrong settings are being backed up from google backup, they're restoring from my galaxy mini 2), but thanks anyway. I am really not having any luck at all with this whole update . But ti-pich, I agree with you, that JB rom is awesome
trainman261 said:
Actually, with my problem, my system apps did remain, so it's almost the same problem, only my device didn't boot into recovery on its own (seriously, it booted into recovery on its own and wiped the data? ). I only installed the terrasilent kernel to be able to upgrade to JB, so I'm now on JB, running into different problem (the wrong settings are being backed up from google backup, they're restoring from my galaxy mini 2), but thanks anyway. I am really not having any luck at all with this whole update . But ti-pich, I agree with you, that JB rom is awesome
Click to expand...
Click to collapse
Yes it did, after 1 week. I was like ???. I reflashed it again and it did the same exact thing, and it happened to me while I was at my college too.
I also had that same issue where it was restoring from the wrong device. I just had to reflash the rom, and install stuff manually because it was making my device horribly slow.
obscuresword said:
Yes it did, after 1 week. I was like ???. I reflashed it again and it did the same exact thing, and it happened to me while I was at my college too.
I also had that same issue where it was restoring from the wrong device. I just had to reflash the rom, and install stuff manually because it was making my device horribly slow.
Click to expand...
Click to collapse
Wow that is some scary stuff, now I know why every kernel/ROM/mod has a disclaimer at the beginning ... I'm glad I'm off that now and on a stable JB build now. I found a way to have it restore at least some of the stuff from when it was on gingerbread (mostly apps and appdata, no WiFi passwords or other settings - at least I'm pretty sure, I'm still working on getting all the stuff up and running) - go into a terminal, and type
Code:
bmgr list sets
It will probably have two different sets, one for when it was on GB and one for JB - or that is, if you had the problem, there will probably be a third set for a different device (maybe more). Then, choose the one you want to restore from, and type
Code:
bmgr restore xxxxxxxxxxxxxxxx
and replace xxxxxxxxxxxxxxxx with the apropriate ID from the command before. I'm having to type it several times in order to get it to work - I type it once, it restores some apps, then stops, I type it again, and it restores some more - but I'm hoping it gets as much possible onto the JB build. I guess this won't help you much, I've seen you saying on the ICS and JB threads that you've upgraded a while ago, but I guess if someone else comes along with the same problem, I hope it will help
trainman261 said:
Wow that is some scary stuff, now I know why every kernel/ROM/mod has a disclaimer at the beginning ... I'm glad I'm off that now and on a stable JB build now. I found a way to have it restore at least some of the stuff from when it was on gingerbread (mostly apps and appdata, no WiFi passwords or other settings - at least I'm pretty sure, I'm still working on getting all the stuff up and running) - go into a terminal, and type
Code:
bmgr list sets
It will probably have two different sets, one for when it was on GB and one for JB - or that is, if you had the problem, there will probably be a third set for a different device (maybe more). Then, choose the one you want to restore from, and type
Code:
bmgr restore xxxxxxxxxxxxxxxx
and replace xxxxxxxxxxxxxxxx with the apropriate ID from the command before. I'm having to type it several times in order to get it to work - I type it once, it restores some apps, then stops, I type it again, and it restores some more - but I'm hoping it gets as much possible onto the JB build. I guess this won't help you much, I've seen you saying on the ICS and JB threads that you've upgraded a while ago, but I guess if someone else comes along with the same problem, I hope it will help
Click to expand...
Click to collapse
hmmm. I'm about to try Terrasilent with my YP-G1 (US version) running 2.3.6. This is giving me second thoughts. Does this kernel still cause issues with SGP 4.0s running GB 2.3.6?? Maybe I should try the old Steves Kernel? I just want to use voodoo sound - thats really the only reason I want to root and get these kernels.